I am failing to reliably reproduce this issue.
At first I have experienced this too. When I tried to bisect it and install
multiple kernel abis they are all booting fine.
So I was able to fail booting 1014 1015 1016 abis. And then they started
to boot fine.
I wonder if there is some
** Package changed: ubuntu => linux-riscv-5.11 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934548
Title:
RISC-V: Illegal instruction
To manage notifications about this bug go to:
Public bug reported:
linux-riscv-5.11 1015 panics on unmatched
[0.00] SBI specification v0.2 detected
[0.00] SBI implementation ID=0x1 Version=0x9
[0.00] SBI v0.2 TIME extension detected
[0.00] SBI v0.2 IPI extension detected
[0.00] SBI v0.2 RFENCE
insecure W+X mapping is fixed in v5.13 series and in impish.
the changes to fix those will not be backported to hirsute, hence marking this
bug as fix released.
The kernel panics that is shown in the pastebin is unrelated to the
insecure W+X mapping.
** Changed in: linux-riscv (Ubuntu)
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
** Patch removed: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
** Patch added: "chmod-reference.patch"
** Patch added: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: bash (Ubuntu)
Status: New => Invalid
** Changed in: dash (Ubuntu)
Status: New => Invalid
** Changed in: debhelper (Ubuntu)
Status: New => Triaged
** Changed in: debugedit (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New
The cat trick does not preserve setuid when building with Rules-
Requires-Root:no.
Not sure why though.
Either we need to fix for this to work with Rules-Requires-Root:no or
bail out in such a scenario.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Based on https://elixir.bootlin.com/linux/latest/source/fs/inode.c#L1928
it seems that setuid and capabilities will be stipped, thus currently
our implementation of dh_strip causes to loose setuid and capabilities.
No idea why this is working with fakeroot when Rules-Requires-Root is set to
Public bug reported:
gnutls library can be configured using /etc/gnutls/config for example to
allow small keys and TLS versions below v1.2
however, if application is confined and has an apparmor profile and uses
gnutls it will ignore such file, if it is not allowed to read it.
For example:
[
separately I'm not sure who/what/why stips setuid bits on file creation
through redirect.
is it like some kind of a CVE in bash/dash? kernel protection?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
- objcopy/strip changed in 2.36.1, not keeping file attributes of the
original file. Work around that in dh_strip to write to a temporary
file and cat'ing this to the original file to keep the original
attributes.
which is broken for setuid files.
** Also affects: dash (Ubuntu)
dh_strip does
strip --remove-section=.comment --remove-section=.note --strip-unneeded -o
/tmp/OdGxqpWWsW/stripeIrB_j debian/virtualbox/usr/lib/virtualbox/VBoxSDL.so
cat '/tmp/OdGxqpWWsW/stripeIrB_j' >
'debian/virtualbox/usr/lib/virtualbox/VBoxSDL.so'
which behaves differently under root and
With debugedit v5.0 things are still the same
https://launchpadlibrarian.net/551609214/buildlog_ubuntu-impish-
amd64.virtualbox_6.1.26-dfsg-2ubuntu1_BUILDING.txt.gz
the setuid bit is lost.
I guess we need to dig deeper into dh_strip activities, to see
what/where/how it is lost. Maybe it is lost
ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL
-rwsr-sr-x 1 buildd buildd 406824 Aug 4 15:51
debian/virtualbox/usr/lib/virtualbox/VBoxSDL
dh_strip --dbgsym-migration='virtualbox-dbg'
ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL
-rwxr-xr-x 1 buildd buildd 166208 Aug 4 15:52
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Public bug reported:
Over at https://launchpadlibrarian.net/550715513/buildlog_ubuntu-
hirsute-amd64.virtualbox_6.1.22-dfsg-2~ubuntu1.21.04.2_BUILDING.txt.gz
I have rebuilt an earlier version of virtualbox, that sets Rules-
Requires-Root: no and added extra ls statements to find where/when/why
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
** 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 +
`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
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
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
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)
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
$ 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),
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
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
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
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
>
** 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
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:
** 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
** 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: 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 be
** 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: 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: 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: 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.
** 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.
** 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.
** 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.
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
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
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
** 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
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:
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
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
**
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
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 =>
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/
@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
I see that these uploads are broken:
https://launchpad.net/ubuntu/impish/+queue?queue_state=2_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/1937237
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-
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
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
** 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
** 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.
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
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:
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.
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
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
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
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:
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
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
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
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
$ 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
** 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
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,
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
> 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
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
/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
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
** 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
--
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.
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
** 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:
** 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
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
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
@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
`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.
@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
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
[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
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
** 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
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.
Public bug reported:
[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 to
Opened https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1936344 to
make dkms autopkgtest smarter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932158
Title:
Building initial module for 5.4.0-77-generic
Error! The
/var/lib/dkms/backport-iwlwifi/8324/5.4.0-77-generic/aarch64/dkms.conf for
module backport-iwlwifi includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch. This indicates that it should not be built.
Skipped.
Processing
Public bug reported:
Over at https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/1932158
you can observe that it was chosen to skip the dkms module for a given
kernel, and dkms-autopkgtest did not manage to handle it well.
** Affects: dkms (Ubuntu)
Importance: Undecided
(bionic-amd64)root@ottawa:/tmp# dpkg-query -W initramfs-tools liblz4-tool zstd
initramfs-tools 0.130ubuntu3.13
liblz4-tool 0.0~r131-2ubuntu3.1
zstd1.3.3+dfsg-2ubuntu1.2
(bionic-amd64)root@ottawa:/tmp# mkinitramfs -c zstd -o zstd-initrd.img
4.15.0-150-generic
** Description changed:
[Impact]
BTF is an extremely useful tool for BPF developers. Enabling BTF support
in the HWE kernel requires pahole from dwarves-dfsg 1.21 or later, but
in focal we have only 1.15. The simplest path for us to get a
sufficiently updated version of pahole is to
501 - 600 of 9162 matches
Mail list logo
