Attached is a patch to SRU groovy.
** Patch added: "lp1913476_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+attachment/5457474/+files/lp1913476_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
[Impact]
* With update-manager versions 1:20.04.10.3 or 1:20.10.2, update-manager would
crash
while processing the apt cache.
[Test Case]
* Look at the Error Tracker issues and make sure the versions 1:20.04.11 and
1:20.10.3 do not
cause this same error.
[Where problems could occur]
Attached is an SRU for focal.
** Patch added: "lp1901043_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901043/+attachment/5457510/+files/lp1901043_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
[Impact]
* When booting to "Safe Graphics" mode the system startup sound would
sometimes not be played
* This is an accessibility issue as the system startup sound is meant to
indicate that Ubiquity is ready
[Test Case]
* Boot an installer image to Safe Graphics mode and listen for th
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains
** Description changed:
I was using friendly-recovery as my Ubuntu desktop session was not
starting after an upgrade to Groovy Gorilla. When I chose to "Enable
networking" in the friendly-recovery menu I noticed that no dns servers
could be reached and come to find out it was because syste
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
update-manager. This problem was most recently seen with package version
1:20.04.10.3, the problem page at
https://errors.ubuntu.com/problem/b4e18d21aa7526e3a98130b1556e4d38ffaff9e0
contain
This SRU for focal resolves the issue of being unable to connect to the
system bus in schroot environments.
** Patch added: "lp1901043_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901043/+attachment/5457899/+files/lp1901043_focal.debdiff
--
You received this bug no
** Description changed:
== Comment: #0 - Heinz-Werner Seeck -
2020-07-31 03:28:30 ==
On z13 we have that vector alignment hints are already accepted. This
backport enables GAS to accept such hints not only for target z14 but also for
z13. Since GCCs default target on Ubuntu is z13 for s390
Attached is an SRU for groovy.
** Patch added: "lp1901043_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901043/+attachment/5457915/+files/lp1901043_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This focal SRU adds more specific exception handling.
** Patch added: "lp1901043_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901043/+attachment/5458091/+files/lp1901043_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
This groovy SRU adds more specific exception checking for attempts to
connect to the system bus.
** Patch added: "lp1901043_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901043/+attachment/5458097/+files/lp1901043_groovy.debdiff
--
You received this bug notificatio
** Patch removed: "lp1901043_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901043/+attachment/5458097/+files/lp1901043_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: packagekit (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: packagekit (Ubuntu Eoan)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: packagekit (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (j
** Changed in: procps (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: procps (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: procps (Ubuntu Hirsute)
Assignee: (unassigned) => William Wilson (j
Attached is a patch to fix the issue in hirsute. Assuming this is
approved, I have also prepared the SRUs for focal and groovy.
** Patch added: "Hirsute debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5480543/+files/lp1874824_hirsute.debdiff
--
You received
** Description changed:
+ [Impact]
+
+ - Users who have ulimit set high would see either slow
+ or failed pgrep and pkill commands
+ - Users who have ulimit set to unlimited would see
+ failed pgrep and pkill commands
+ - This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
** Patch added: "segfault patch"
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1921919/+attachment/5482408/+files/lp1921919.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921919
T
Public bug reported:
The version of urfkill in -proposed has a possible segmentation fault if
the call to get_dmi_info fails. After this there is an attempt to free
an uninitialized variable. This was blocking the migration from
-proposed.
kernel: urfkilld[46754]: segfault (11) at 0 nip 955592940
** Patch added: "Patch with corrected LP reference"
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1921919/+attachment/5482409/+files/lp1921919.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
The test sessions/integration_test.go is consistently failing
autopkgtests and therefore this package cannot migrate.
** Affects: golang-github-bugsnag-bugsnag-go (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Attachment added: "Patch to increase sleep"
https://bugs.launchpad.net/ubuntu/+source/golang-github-bugsnag-bugsnag-go/+bug/1921952/+attachment/5482453/+files/lp1921952
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
The kernel has added a byte to the rfkill event struct to account for a
possible reason field. See:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=14486c82612a177cb910980c70ba900827ca0894
urfkill is checking to make sure the rfkill event is exac
** Patch added: "Fix RFKILL_EVENT_SIZE_V1 check"
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1922117/+attachment/5482869/+files/lp1922117.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Patch added: "Groovy SRU"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484328/+files/lp1874824_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874824
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484329/+files/lp1874824_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874824
T
Public bug reported:
In the case of upgrading bluez on certain raspberry pi devices, a reboot
may be required to apply the changes. We should add a check for this
scenario in the postinst script.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Robie,
pgrep and pkill are sharing the same code. Essentially pkill runs pgrep
and then issues a kill signal to the resulting pid. Therefore this fix
applies to both pkill and pgrep. Additionally, the source of the problem
comes from the behavior of `sysconf(_SC_ARG_MAX)` changing in newer
kernels
Attached is a patch for Hirsute. If this is accepted I will SRU to focal
and groovy.
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Patch added: "Hirsute Patch"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+attac
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Attached is a patch to add the hwcap metric to ubuntu-report.
** Patch added: "lp1922712.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+attachment/5485728/+files/lp1922712.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Seb,
A reboot is needed in this case because the bluetooth device on the
raspberry pi has to be initialized at boot time. Restarting the service
will not cause the device to be brought up.
The hardcoded addresses are the approach used in the pi-bluetooth
package, and recommended by waveform.
As
The verification passed for focal:
jawn-smith@focal-vm:~$ apt-cache policy procps
procps:
Installed: 2:3.3.16-1ubuntu2
Candidate: 2:3.3.16-1ubuntu2.1
Version table:
2:3.3.16-1ubuntu2.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
*** 2:3.3.16-
Seb, I have made a PR in the github repo. This PR also pulls in the
changes in version 1.6.3, which were previously not present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metr
** Changed in: pi-bluetooth (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: pi-bluetooth (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Description changed:
- In the case of upgrading bluez on certain raspberry pi devices, a reboot
- may be required to apply the changes. We should add a check for this
- scenario in the postinst script.
+ In the case of upgrading or installing bluez for the first time on
+ certain raspberry pi d
I have submitted a Debian bug report with the patch suggested, and
updated the bug description.
bluez is pre-installed on the desktop images, but not the server images.
This warning would be very useful for server users that want to install
bluez for the first time.
--
You received this bug noti
** Changed in: gsasl (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972866
Title:
[MIR] gsasl
To manage notifications about t
Public bug reported:
TBD by foundations
** Affects: libntlm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libntlm (Ubuntu)
Milestone: None => ubuntu-22.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gsasl (Ubuntu)
Milestone: None => ubuntu-22.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972866
Title:
[MIR] gsasl
To manage notifications about this bug go to:
https://bugs
** Description changed:
- TDB by foundations
+ [Summary]
+ * Everything seems in order with this package, but it should
+ be reviewed by the security team due to the nature of the package.
+ * Build log:
https://launchpadlibrarian.net/564514219/buildlog_ubuntu-jammy-amd64.gsasl_1.10.0-5_BUILDING.
** Description changed:
- TBD by foundations
+ [Summary]
+ * Due to the nature of the package (an authentication library) it should
+ be reviewed by the security team before promotion
+ * build log:
https://launchpad.net/ubuntu/+source/libntlm/1.6-4/+build/22298428
+
+ [Availability]
+ * The pac
** Changed in: gsasl (Ubuntu)
Assignee: William Wilson (jawn-smith) => (unassigned)
** Changed in: gsasl (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972866
Title:
[MIR] gsasl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsasl/+
** Also affects: mutt (Ubuntu)
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/1972866
Title:
[MIR] gsasl
To manage notifications about this bug go to:
htt
Public bug reported:
There is a redirect in go.mod and in vendor/modules.txt to redirect
containerd to an empty module. This is not compatible with Go 1.18 and
should therefore be removed. Removal has not caused any problems with Go
1.17.
** Affects: containerd (Ubuntu)
Importance: Undecided
** Patch added: "lp1965157.debdiff"
https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1965157/+attachment/5569713/+files/lp1965157.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965
Successful build against Go 1.18 in my PPA: https://launchpad.net/~jawn-
smith/+archive/ubuntu/golang-118-released-rebuilds/+build/23247900
Successful build against Go 1.17 in my PPA: https://launchpad.net/~jawn-
smith/+archive/ubuntu/golang-base-rebuilds/+build/23247918
--
You received this bug
Go 1.18 has released and test rebuilds have been completed.
Go 1.18 has made the decision to deny SHA1 certificates by default. Per
the release notes: "crypto/x509 will now reject certificates signed with
the SHA-1 hash function. This doesn't apply to self-signed root
certificates. Practical attac
I have a fix for golang-golang-x-tools in a PPA, but it builds a new
binary with 1.18, so the upload can't be done until golang-defaults 1.18
is uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
We have a plan to fix some of the SHA1 packages by allowing SHA1
certificates in the test cases only. This will allow the tests to fail
without changing the behavior of the compiled binaries. It will be
accomplished using the GODEBUG=x509sha1=1 environment variable in
override_dh_auto_test
--
You
I have created a PR to fix telegraf upstream, and have it scheduled to
build in my PPAs as well.
https://github.com/influxdata/telegraf/pull/10847
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964270
Prometheus and telegraf are now successfully building in my PPAs. I will
upload them to the archive shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964270
Title:
Feature Freeze Exception: Up
** Project changed: ubuntu-image => ubuntu-image (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965585
Title:
FFE request: Add support for piboot to ubuntu-image
To manage notifications ab
Lucas,
Changing go.mod to rely on Go 1.17 does actually cause it to FTBFS. The
errors are related to vendored modules not being explicitly required in
go.mod. Is this something we should tackle now?
Here is a full failed build log:
https://launchpadlibrarian.net/592301054/buildlog_ubuntu-jammy-
a
Lucas, this is working great! golang-defaults has now migrated. Would
you like me to sponsor this or would you rather do the upload?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965157
Title:
cont
I have a tiny nitpick here. The existing patches for this package are in
the form of -.patch, but the patch added here is missing
the . Can you rename the patch and upload a new debdiff?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: softhsm2 (Ubuntu)
Status: New => 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/1961189
Title:
softhsm2: FTBFS against OpenSSL 3.0 (test suite)
To manage notifica
** Changed in: softhsm2 (Ubuntu)
Status: Fix Committed => 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/1961189
Title:
softhsm2: FTBFS against OpenSSL 3.0 (test suite)
To manage
@juergh with this new kernel I no longer see the flip_done timed out
message, but HDMI still dies and the boot process hangs right after
plymouth starts up.
```
ext4
Thu Jan 1 00:00:09 UTC 1970
writable: recovering journal
writable: clean, 159978/929200 files, 1595477/3751163 blocks
-.mount
blk-a
@diddledani the patch in comment 2 doesn't apply cleanly in bionic.
Would you be able to redo the patch for bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873565
Title:
issue with TLS 1.2 se
@profzoom could you update the SRU template [Test Case] section with
information on what a successful run after updating the package would
look like? I applied your patch but I still see "Sorry, this program
doesn't support digraphs yet."
--
You received this bug notification because you are a me
** Tags added: verification-needed verification-needed-focal
** Description changed:
- Ghostscript 9.50 exhibits
- https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co
- options) which causes (eg) ocrfeeder to fail to load PDF files: an input
- file specified using the "... --
** Patch added: "lp1913656.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+attachment/5532989/+files/lp1913656.debdiff
** Changed in: ghostscript (Ubuntu Focal)
Assignee: Till Kamppeter (till-kamppeter) => William Wilson (jawn-smith)
It seems changing the power supply (along with the test kernel provided
by juergh) has resolved my issues as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946368
Title:
HDMI output freezes un
I have confirmed that the kernel 5.13.0-20 in impish-proposed solves
this problem for me.
To confirm this, I performed the following steps:
On a ZFS installation:
1) boot from kernel 5.13.0-19.19
a) observe the boot failed with PANIC at zfs_node.c: 339:zfs_znode_sa_init
2) install kernel 5.13
This bug is currently not present in The focal HWE kernel 5.11, but now
that the kernel team PPA has a 5.13 HWE kernel available I will try to
recreate this bug and SRU it if successful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug will not exist in hwe kernels 5.11 or 5.13. Both of those
kernels use a separate rfkill_event and rfkill_event_ext struct with the
following explanation:
/**
* DOC: Extensibility
*
* Originally, we had planned to allow backward and forward compatible
* changes by just adding fields at
** Patch added: "Bionic debdiff"
https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1923352/+attachment/5536541/+files/lp1923352_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923352
Title:
speedtest-cli crashed with ValueError in get_config(): invalid literal
for int() with base 10
This actually appears to have been fixed by a patch in sfcgal 1.3.7-4,
which is in focal as of Dec 2019. If you are still experiencing this
issue with the latest version of sfcgal in focal, are you able to share
the code that is causing the issue?
--
You received this bug notification because you
The long term solution for this is probably to get the desktop images
built with ubuntu-image so that the hooks feature of u-i can be used for
customization.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
@paelzer I would be happy to work on the merge if you would like.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939751
Title:
openssh FTBFS with glibc >= 2.34
To manage notifications about this bu
I tested this on the regular gnome ubuntu 20.04.3 and did not see the
same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917062
Title:
Decryption passphrase prompt not displayed until escape
Public bug reported:
This merge is needed because there are changes in Ubuntu that are not
present in Debian.
** Affects: openssh (Ubuntu)
Importance: Undecided
Assignee: William Wilson (jawn-smith)
Status: In Progress
** Changed in: openssh (Ubuntu)
Assignee
Public bug reported:
Aspectc++ is currently FTBFS with glibc 2.34. The package is fairly
active upstream, so when it is fixed we should be able to re-upload it.
jawn-smith@desktop:~$ reverse-depends -b src:aspectc++
No reverse dependencies found
jawn-smith@desktop:~$ reverse-depends src:aspectc++
** Patch added: "Diff from 1:8.4p1-5ubuntu2"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+attachment/5521261/+files/lp1941799-ubuntu-ubuntu.debdiff
** Changed in: openssh (Ubuntu)
Assignee: William Wilson (jawn-smith) => (unassigned)
** Changed in: op
paelzer: I worked the merge under
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939751
Title:
openssh FTBFS with glibc >= 2.34
To man
This diff from Debian still includes the seccomp fixes pulled in for
glibc 2.33, as they are still relevant with glibc 2.34. These are in
upstream openssh version 8.5, so when Debian gets to 8.5 we can sync and
drop the diff.
** Patch added: "Diff from Debian"
https://bugs.launchpad.net/ubuntu
Public bug reported:
Due to changes in the valid separators accepted by net/url, this package
FTBFS with go 1.17. For more information see
https://golang.org/doc/go1.17#semicolons
** Affects: golang-github-ajg-form (Ubuntu)
Importance: Undecided
Status: New
--
You received this bu
This patch replaces the use of ';' with '&' which is still valid
** Changed in: golang-github-ajg-form (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Patch added: "lp1942131.debdiff"
https://bugs.launchpad.net/ubuntu/+sourc
** Bug watch added: Debian Bug tracker #993327
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993327
** Also affects: golang-github-ajg-form (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993327
Importance: Unknown
Status: Unknown
--
You received this bug notif
Public bug reported:
With Go 1.17 this package FTBFS. It appears to be due to the fact that
on armhf systems the syscalls for getting system time are returning 32
bit integers rather than 64. Before fixing this we should think about
whether people will ever do Android development on armhf.
** Aff
Public bug reported:
This package currently FTBFS with Go >= 1.16. Both Debian and Ubuntu are
on version 2.0.4 of this package, while upstream it is on version 4. I
have tested v4 from the upstream and verified that it does build and the
tests succeed with go 1.16 and 1.17.
** Affects: golang-git
Public bug reported:
As of Go 1.17 the flag package will panic if given a syntactically
invalid flag. See https://golang.org/doc/go1.17#flag for more detail.
There is a test in this package that tries to test an invalid usage
scenario by passing a syntactically invalid flag. This causes the build
Public bug reported:
As of Go 1.17 the flag package will panic if given a syntactically
invalid flag. See https://golang.org/doc/go1.17#flag for more detail.
There is a test in this package that tries to test an invalid usage
scenario by passing a syntactically invalid flag. This causes the build
** Changed in: u-boot (Ubuntu Hirsute)
Status: Confirmed => 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/1923162
Title:
riscv64 images fail to boot in qemu
To manage notificati
** Also affects: golang-github-urfave-cli (Ubuntu)
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/1942255
Title:
FTBFS with Go 1.17
To manage notification
-urfave-cli (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: golang-github-urfave-cli-v2 (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Bug watch added: Debian Bug tracker #993483
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
** Patch added: "golang-github-urfave-cli-v2.debdiff"
https://bugs.launchpad.net/debian/+source/golang-github-urfave-cli-v2/+bug/1942255/+attachment/5522393/+files/lp1942255_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I've installed the edge kernel on my Pi 4 Rev 1.4 2GB board and haven't
been able to recreate the issue:
jawn-smith@localhost:~$ snap info pi-kernel | egrep "installed|18-pi/edge"
tracking: 18-pi/edge
18-pi/edge: 5.4.0-1043.47~18.04.1 2021-08-25 (343) 193MB -
installed: 5.4.0-10
This was fixed under LP: 1942255
** Changed in: golang-github-urfave-cli (Ubuntu)
Status: New => Fix Released
** Changed in: golang-github-urfave-cli (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This was fixed under LP: #1942255
** Changed in: golang-github-urfave-cli (Ubuntu)
Status: Fix Committed => 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/1942254
Title:
FTBFS wi
I had to revert this change as it was causing failures in autopkgtests.
Can you look into a method for fixing this that doesn't cause
autopkgtest failures?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
This bug was fixed in the package erlang - 1:24.2+dfsg-1
---
erlang (1:24.2+dfsg-1) unstable; urgency=medium
* New upstream release.
* Refresh patches.
-- Sergei Golovan Wed, 15 Dec 2021 19:39:20
+0300
erlang (1:24.1.7+dfsg-1) unstable; urgency=medium
* New upstream releas
I'm seeing this issue with the arm64 server image as well.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943097
Title:
Kernel 5.13 broke my Ub
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943
My logs over serial: https://paste.ubuntu.com/p/Wp4YdqyjJy/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943097
Title:
Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb
To manage notifications about
If I wait long enough I see:
mdadm: No devices listed in conf file were found.
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! LABEL=writa
Jose, the real issue in these logs is that the system is failing to find
the root file system to boot to. That's what is causing the "Gave up
waiting for root file system device" log and causing the system to drop
to an initramfs shell.
--
You received this bug notification because you are a memb
201 - 300 of 450 matches
Mail list logo
