NB! postinst must be executable
** Patch added: "impish.debdiff"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1936370/+attachment/5511152/+files/impish.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Description changed:
[Impact]
- * u-boot-sifive package currently does not upgrade bootloader on
loader1/loader2 partitions.
-
- * there have now been bugs identified, meaning that upgrading u-boot is
required to upgrade from v5.8 kernel to v5.11 (i.e. either in-focal, or from
focal
Testing out of ppa:
$ sudo strings /dev/disk/by-partlabel/loader* | grep 202 | grep U-Boot
U-Boot SPL 2021.01+dfsg-3ubuntu0~20.04.1 (Jun 25 2021 - 18:21:47 +)
U-Boot 2021.01+dfsg-3ubuntu0~20.04.1 (Jun 25 2021 - 18:21:47 +)
$ sudo apt install u-boot-sifive
Preparing to unpack .../u-boot-
[10044.522610] reboot: Restarting�
U-Boot SPL 2021.01+dfsg-4ubuntu3 (Jul 15 2021 - 12:01:50 +)
Trying to boot from MMC1
U-Boot 2021.01+dfsg-4ubuntu3 (Jul 15 2021 - 12:01:50 +)
all is good
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ubuntu@ubuntu:~$ sudo systemctl is-system-running
running
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.11.0-1014-generic #14~20.04.1-Ubuntu SMP Thu Jul 1 13:56:47 UTC
2021 riscv64 riscv64 riscv64 GNU/Linux
it came up fine.
--
You received this bug notification because you are a member of Ubuntu
B
@everyone
Can each one of you please open a new bug reports, using `ubuntu-bug`
tool with full apt output logs. Each error that happens may need unique
solutions.
Also I really need to know where from you are upgrading, and when/how
the system was last installed. As that matters a lot for usrmerg
`Unpack base-files (11ubuntu18) on (11ubuntu14) ..`
Looks very odd, because it is an upgrade between groovy-release and
development version of hirsute, not the one we released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@everyone
Can you please also specify when and how you installed your systems?
i.e. attach your /var/log/installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924850
Title:
package usrmerge 24ub
Also it is brand new installation of usrmerge package, and yet the
system looks like usrmerged already, i think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924850
Title:
package usrmerge 24ubunt
The attached implementation checks for what one has booted as.
But does not check what was on the partitions before, or if they were
used at all or not.
I guess I could do:
```
$ sudo dtc -I dtb -O dts /dev/disk/by-partlabel/loader2 | dtc -I dts -O yaml |
grep hifive-unleashed-a00
descrip
** Changed in: u-boot (Ubuntu Impish)
Status: New => In Progress
** Changed in: u-boot (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936370
** Changed in: grub2 (Ubuntu)
Status: New => In Progress
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929860
Title:
initr
grub2-signed and grub2-unsigned are source package names.
You are searching for binary package names binary package name is
grub-efi-amd64-signed
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Not sure it needs to do that. because I thought the tooling i.e. grub-
mount is built out of src:grub2 not out of src:grub2-unsigned. And we
don't copy back src:grub2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Also affects: grub2-unsigned (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2-signed (Ubuntu)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu)
Status: New => In Progress
** Changed in: grub2 (Ubuntu)
Status: New => In Progress
--
Yo
we currently do chain grub.cfg from ESP to boot partition, can the
password be set in that grub.cfg file instead? which today is outside of
the scope of grub-mkconfig management.
And that grub is protected with restrictive mount options of ESP, see
/boot/efi/EFI/ubuntu/grub.cfg
--
You received t
/boot/grub/grub.cfg is a generated file that must not be modified by
hand. Instead one is supposed to modify things like /etc/default/grub
/etc/default/grub.d/* /etc/grub.d/*
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a membe
sshd_config is user modifyable and maintained. Some options can be
changed using dpkg-reconfigure openssh-server but otherwise changes to
it should be preserved.
Can you please provide steps to reproduce changes to sshd_config getting
lost?
--
You received this bug notification because you are a
> The place to flash U-Boot SPL (sector 34) is hard coded in the boot
ROM.
I don't believe that is true. It is specified by GPT partition type UUID
in FSBL, and it doesn't have to be at sector 34. As per sifive manuals.
Furthermore I don't have access to read jumpers, thus I don't know if
the sys
Is this debhelper or binary-package-mangler bug then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934936
Title:
package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
trying to
In i386 build log I see
Searching for duplicated docs in dependency libroken18-heimdal...
symlinking changelog.Debian.gz in libwind0-heimdal to file in
libroken18-heimdal
I don't see something similar in adm64.
As if the trimming of the changelog entries got done before doing
symlinks, instea
** Changed in: heimdal (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934936
Title:
package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upg
$ dpkg-query -W u-boot-qemu
u-boot-qemu 2021.01+dfsg-3ubuntu9.1
$ qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel
/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
device,netdev=eth0 -netdev user,id
Trying to see if impish u-boot is also broken at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug
Impish is not affected, as it still skips fdtdir under qemu completely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications abou
Oh https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu9.1
is an orphan, as it did not make it into impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fa
What the patch was supposed to do is to list
Default Dependencies from
https://www.freedesktop.org/software/systemd/man/systemd.socket.html#
But drop/negate shutdown related ones.
Thus it should have been
1) Before= dependency on sockets.target
2) After= and Wants= dependency on sysinit.target
i.e. basic.target is too much there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936948
Title:
Dependency loop via sockets.target
To manage notifications about this bug go to:
https://bugs.launc
in later releases grub-install has stopped forking to call efibootmgr in
favor of using an EFI library.
Does it return non-zero error code? because it should be ignoring
failure to call efibootmgr. And otherwise grub installation was
completed.
efibootmgr recommends has been added back in Debian,
Fixed in
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.32
[ Dimitri John Ledkov ]
* Cherrypick 2.02+dfsg1-5 patch for x86-64: Treat R_X86_64_PLT32 as
R_X86_64_PC32 to allow processing 2.04 grub modules built with newer
binutils.
** Changed in: shim-signed (Ubuntu
Fixed in https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.23
[ Dimitri John Ledkov ]
* Cherrypick 2.02+dfsg1-5 patch for x86-64: Treat R_X86_64_PLT32 as
R_X86_64_PC32 to allow processing 2.04 grub modules built with newer
binutils.
--
You received this bug notification
Changelog entries in the #3 debdiff are in the wrong order.
The 2.12.2-1ubuntu1~20.04* entreis should be just above the other 2.12.2
entries.
Such that when build is done with -v2.12.5-1ubuntu1~20.04.2 all
changelog entries since 2.12.2 are included, i.e. all the v2.12.5 from
impish and etc.
Wil
Sponsored evdi_1.9.1-1ubuntu4_source.changes to impish.
** Changed in: evdi (Ubuntu Focal)
Status: Fix Committed => Confirmed
** Changed in: evdi (Ubuntu Focal)
Assignee: Thadeu Lima de Souza Cascardo (cascardo) => (unassigned)
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: Fi
evdi debdiff is good, but it must go into other series too.
https://autopkgtest.ubuntu.com/packages/evdi
Looks like that change is needed in impish, hirsute and focal.
One cannot introduce brand new change in a focal SRU with a version
number higher than all future series.
** Changed in: evdi (
** Patch added: "corrected.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5512590/+files/corrected.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment added: "lttng-modules_2.12.5-1ubuntu1~20.04.2_source.changes"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5512591/+files/lttng-modules_2.12.5-1ubuntu1~20.04.2_source.changes
--
You received this bug notification because you are a member of Ub
Please provide SRU paperwork as per
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932165
Title:
lttng-modules/2.12.2-1ubuntu1~20.04.2 A
Changes in #15 are not suitable to go into Focal yet. As they should
first be present in impish as well. Otherwise, whilst Focal switches to
dkms package provider testing harness, the Impish package did not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
https://launchpad.net/ubuntu/impish/+upload/26439022/+files/debian-
installer-images_20101020ubuntu628_amd64.tar.gz
contents does not match what's unpacked in the archive, i.e.
http://archive.ubuntu.com/ubuntu/dists/impish/main/installer-
amd64/20101020ubuntu628/legacy-image
I see that these uploads are broken:
https://launchpad.net/ubuntu/impish/+queue?queue_state=2&queue_text=debian-
installer
Can AA please reject them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/193
@vicamo sponsoring #15 to impish. Please apply the debdiff from here to
impish packaging git.
** Patch added: "impish.diff"
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1932158/+attachment/5512861/+files/impish.diff
--
You received this bug notification because you ar
i386 publication looks a lot better now.
However, amd64 latest somehow published as empty. but the one before
is fine
http://archive.ubuntu.com/ubuntu/dists/impish/main/installer-amd64/20101020ubuntu627/legacy-images/
http://archive.ubuntu.com/ubuntu/dists/impish/main/installer-amd64/20101020
The proposed change fails in ADT in impish, please investigate
https://autopkgtest.ubuntu.com/packages/b/backport-iwlwifi-dkms
** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
Status: Fix Committed => Incomplete
** Changed in: backport-iwlwifi-dkms (Ubuntu)
Status: Invalid => In
1.9.1-1ubuntu4~21.04.1 supersedes 1.9.1-1ubuntu3~21.04.1 to fix adt
failure on s390x.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932163
Title:
evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure w
We must not have broken squashfs-tools. So we should find what/when got
changed or fixed and backport those fixes.
** Also affects: squashfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: squashfs-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** A
After removing the queue items. And building 20101020ubuntu629 it
published correctly on all arches. All is good, and d-i can be removed
fully now.
** Changed in: launchpad
Status: New => Fix Released
** Changed in: debian-installer (Ubuntu)
Status: New => Fix Released
--
You rece
Public bug reported:
u-boot in impish has unstable mac address
Somehow the board that is usually SiFive mac address range of
70:b3:d5:92:f4:40 has become a6:d4:5b:7a:a0:a7
Ideally mac address should be stable, and in the range from the
manufacturer.
** Affects: u-boot (Ubuntu)
Importance:
** Description changed:
u-boot in impish has unstable mac address
Somehow the board that is usually SiFive mac address range of
70:b3:d5:92:f4:40 has become a6:d4:5b:7a:a0:a7
Ideally mac address should be stable, and in the range from the
manufacturer.
+
+ 70:B3:D5:92:F0:00/36 SiF
I am quite surprised by this behaviour.
Especially since, `quilt push -a; debuild -S` works find, unpacks fine,
applies fine etc.
Quite a weird limitation imho. Do you think this warrants an upstream
dpkg bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The timing of the bug report matches the rebuild of cd-boot-images-amd64
against shim-signed 1.50
** Also affects: cd-boot-images-amd64 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
shim-signed 1.50 chainloads windows 10 correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936640
Title:
Download signed version from versioned URL
To manage notifications about this bug go t
** Changed in: xtables-addons (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: xtables-addons (Ubuntu Focal)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: rtl8812au (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: rtl8812au (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: broadcom-sta (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: broadcom-sta (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: bcmwl (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: bcmwl (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932159
** Changed in: xtables-addons (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932173
Title:
xtables-addons/
** Changed in: rtl8812au (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932169
Title:
rtl881
** Changed in: lttng-modules (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: lttng-modules (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: lttng-modules (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received
** Changed in: evdi (Ubuntu Focal)
Importance: Medium => Critical
** Changed in: evdi (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: evdi (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because
** Changed in: broadcom-sta (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932160
Title:
broadcom-sta/6.30.223.
** Changed in: bcmwl (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932159
Title:
bcmwl/6.30.223.271+bd
whould be fixed by 2021.07+dfsg-0ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937376
Title:
u-boot in impish has unstable mac address
To manage notifications about this bug go to:
https:/
** Changed in: virtualbox-hwe (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: virtualbox (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: virtualbox (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: virtu
On Tue, 27 Jul 2021, 05:45 Brian Murray, <1923...@bugs.launchpad.net>
wrote:
> I'm sorry to be a bother here but I don't understand how u-boot failed
> verification for hirsute but passed for focal when what are presumably
> the same patches exist in both versions of the package. How could this
>
New images look fine.
** Changed in: u-boot (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937376
Title:
u-boot in impish has unstable mac address
To ma
It's pure datafiles arch:all package without any runtime deps, thus it
is safe to copy to -security as is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936255
Title:
New upstream release 2021.07.1
I wonder if we should really just do binary copies of it, just like we
do with shim. If we set it to be compressed with xz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936255
Title:
New upstream
$ dpkg-query -W wireless-regdb
wireless-regdb 2021.07.14-0ubuntu1~18.04.1
$ sudo iw reg set 00
$ sudo iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/
That's not enough. The json file I'm asking for in this bug report would
not only load generic opensbi but would also load our location for
uboot.
A second json file would load opensbi and edk2 firmware with various
options.
See the json files that we provide on x86 and arm64, that not only setup
unmatched images look fine.
unleashed still fail to boot in CI lab, suspecting lack of stable mac
address as well. Or something else. It seems like meta-sifive upstream
have dropped all unleashed patches, but it seems like we are regressing
in functionality.
** Changed in: u-boot (Ubuntu)
But the things mentioned in systemd issue were supposedly resolved, and
https://github.com/systemd/systemd/commit/d84af414180a4a8a7dd8772fc9d5302b5f9f28c9
is in focal already.. so is there something else not working in
focal?
--
You received this bug notification because you are a member of U
lttng-modules 2.12.5-1ubuntu2~21.04.1 in hirsute-proposed unapproved
queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932165
Title:
lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with li
`login = *` would work and ask ssh for the username.
If a different launchpad nick is needed from the local address, one
should then configure that in ~/.ssh/config which will then work for
bzr, git, dput access to launchpad.
--
You received this bug notification because you are a member of Ubun
** Changed in: dput (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/632041
Title:
Provide commented-out method of using SFTP to upload to Ubuntu + PPAs
Note that focal's virtualbox is built correctly with correct
permissions.
So I wonder if something else is broken in hirsute that breaks
permissions. I.e. dh_dwz srip or some such.
We should monitor when the setuid gets dropped and by whom.
However focal is now verified by kernel team, thus read
** Description changed:
unbreak ubuntu:desktop-preinstalled images without subarch
Prior to groovy, ubuntu:desktop-preinstalled images for hyperv used to
build fine.
Introduction of ubuntu:desktop-preinstalled for raspi subarch, did not
take into account the hyperv images, and thus
** Changed in: livecd-rootfs (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893898
Title:
open-vm-tools status is toolsNotInstalled after deploy clo
Public bug reported:
[Impact]
* Add support to build risc-v 64 cpc & buildd images for LXD, cloud-
images, and buildd targets.
[Test Case]
* Execute a riscv64 livefs build for the buildd subproject of ubuntu-
base
* Execute a riscv64 livefs build for the ubuntu-cpc project
* Build should
** Description changed:
- with groovy-server-cloudimg-amd64.ova daily build, when only deploy OVA and
don't power on VM, the VMTools status is "toolsNotInstalled"
+
+ [Impact]
+
+ * with groovy-server-cloudimg-amd64.ova daily build, when only deploy OVA
and don't power on VM, the VMTools stat
eui64 being identical sounds like a violation of NVMe spec!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offered as a multipath device
To manage notific
It might help to ensure that release upgrader is started with a _clean_
path; and then append anything it needs from the tarball.
probably ubuntu-release-upgrader should run by #!/usr/bin/python3 -E
and then append path of the tarball.
--
You received this bug notification because you are a mem
maybe we should run debsums as part of the build then.
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902260
Title:
systemd
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898342
Title:
Bootloader install failed
To manage notifications about th
Barry M Tannenbaum, btw you can also raise issues via /intel project.
You could also join ~intel-team to work together with others that
escalate and work on Intel enablement via typical channels.
Is this bugfix on the 2.34 branch?
After full archive rebuild we are planning to SRU binutils from th
When both drives connected could you please paste the output of
$ cat /sys/block/nvme[0-9]n[0-9]/{nguid,eui}
https://nvmexpress.org/wp-content/uploads/NVM-Express-
1_4b-2020.09.21-Ratified.pdf
As per ratified NVMe 1.4b specification, in figure 249 Identity
Namespace Data Structure the nguid and/
based on multipath & installer logs things look okish.
nvme0n1 & nvme2n1 is multipathed Force MP600 NVMe drive
eui.6479a73730830210, which is assembled into mpatha drive (also dm-0)
nvme1n1 is another NVMe drive Seagate FireCuda 520 SSD ZP2000GM30002
eui.0024cf01540022a8
sdc is the usb stick wit
Public bug reported:
python-cassandra-driver doesn't work with TLSv1.2+ on 20.04
probably needs a cherrypick of https://github.com/datastax/python-
driver/commit/88a86356eecae40a198120e4f07dc40a069bc0ad#diff-
720620a471260ebbb075778d2542cd146d3421b86cb781f41f4934c3bdf7346f
as otherwise ssl conte
started with xenial install.
grub2 is at 2.02~beta2-36ubuntu3.28
put apparmor profile in place, and upgrading non-interactively
upgrade to 2.02-2ubuntu8.19 fails as expected with grub-install saying
that error cannot open /dev/vda permission denied.
grub-pc package remains in iF state.
in /boot/
installed grub2 2.02-2ubuntu8.18 and configured debconf & /boot to
reproduce the issue (touched the core.img, as well as enxsured that
install_devices_empty & install_devices are marked as seen, and set to
true and empty respectively).
dpkg-reconfigure -u grub-pc exits zero as expected.
upgraded
Public bug reported:
RM sambamba FTBFS removed from testing
** Affects: sambamba (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: sambamba (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #966914
https://bugs.debian.org
Public bug reported:
RM python2 removed from testing
** Affects: crossfire (Ubuntu)
Importance: High
Status: Triaged
** Affects: crossfire (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #936344
https://bugs.debian.org/cgi-bin/b
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766209
Title:
set -e & debconf are not safe together
To manage notifications about this b
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766214
Title:
shared-secret should not be asked about in postinst
To manage notifications
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766211
Title:
cannot force not installing dbconfig managed postgresql
To manage notificat
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766218
Title:
invoke.rc-d --force should not be used
To manage notifications about this b
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764991
Title:
Ability to delay maas-*-controller configuration, until after install
To ma
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766241
Title:
default url / ip based url / admin user not setup on reconfigure
To manage
Public bug reported:
olive-editor on arm64 fails with
dh_dwz -a
install -d debian/olive-editor/usr/lib/debug/.dwz/aarch64-linux-gnu
dwz
-mdebian/olive-editor/usr/lib/debug/.dwz/aarch64-linux-gnu/olive-editor.debug
-M/usr/lib/debug/.dwz/aarch64-linux-gnu/olive-editor.debug --
Gunnar Hjalmarsson (gunnarhj) we no longer ship any web-browsers that
can actually use this plugin. It is innert.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871471
Title:
flash end of life soon,
the build I locally tested in a chroot in the end, was not the changes
file that i did dput on. sigh.
the intended fix is now there, so that's good =) thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
301 - 400 of 9094 matches
Mail list logo
