Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/arm64/u/udisks2/20200901_174238_f13fc@/log.gz
...
==
ERROR: test_loop_ro
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
groovy/groovy/s390x/t/taptempo/20200901_172536_70cc1@/log.gz
autopkgtest [17:25:11]: test tempo: [---
spawn taptempo
Hit enter key for each beat (q to
Public bug reported:
tests fail on arm64 armhf and ppc64el
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/arm64/d/dune-
grid/20200901_173612_ccce9@/log.gz
...
Checking vector for codim 0
0: load balancing with data was
https://salsa.debian.org/go-team/compiler/golang/-/merge_requests/2
** Also affects: golang (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/1893640
** 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/1893675
Title:
Autopkgtest failure on latest version of initramfs-tools - lack of
partprobe
To manage notifications
The bug is not present in Xenial.
The fix is in groovy-proposed, getting closer and closer to the release
pocket.
I could not reproduce the issue without setting LDCONFIG_TRIGGER_DEBUG,
but considering that this is a small fix and helps at least in debugging
IMO backporting it is the right
Public bug reported:
coreutils 32's stat uses statx, see Debian bug.
** Affects: fakeroot (Ubuntu)
Importance: Undecided
Status: New
** Affects: fakeroot (Debian)
Importance: Unknown
Status: Unknown
** Tags: update-excuse
** Bug watch added: Debian Bug tracker
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/m/mrbayes/20200805_172841_18a79@/log.gz
...
: CommandLine Error: Option 'polly' registered more than once!
LLVM ERROR: inconsistency in registered
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/g/golang-gopkg-square-go-jose.v2/20200706_025803_f@/log.gz
...
=== RUN TestOpaqueKeyRoundtripJWE
panic: test timed out after 10m0s
goroutine 22
We have a few options to fix the issue. The one I'd prefer would be
switching to systemd to depend on chrony as the preferred time-daemon
because timesynd turns back time and that can cause issues like this
one.
An other option is disabling systemd-timesyncd in the test VMs, that
would make the
** Branch linked: lp:~rbalint/britney/hints-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893452
Title:
i386 autopkgtest fails in cross-testing
To manage notifications about this bug go
Public bug reported:
Hence it can't migrate to the release pocket.
** Affects: dicompyler (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1891336
Title:
gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel
To manage notifications about this
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/i386/d/double-
conversion/20200828_151955_cc9fa@/log.gz
...
autopkgtest [15:19:43]: test command1: [---
-- The CXX compiler identification
The file is at the path which is not searched:
/usr/lib/i386-linux-gnu/cmake/double-conversion/double-conversionConfig.cmake
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893452
Title:
i386
Systemd 246.2-1ubuntu1 may have fixed the DNS issue. Do yo still observe
the problem?
** Changed in: friendly-recovery (Ubuntu Groovy)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've also seen occasional segfaults in other builds, glibc maybe? @laney
Do those binaries segfault on local systems or on the test
infrastructure?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Selected experimental ZFS otion and install in QEMU/KVM and crashed
+ Selected experimental ZFS option and install in QEMU/KVM and crashed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@xnox This would be too much divergence from upstream and timeout issues
related to this package already caused complications in the past.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892728
Title:
Thank you for the explaining the reasons. I understand the complexity of
having to support several distros with less advanced ability to handle
configuration files. This was the reason for me to switch to Debian, way
before Ubuntu was born. :-)
Since as you described the configuration file does
Who owned /var?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891394
Title:
systemd breaks upgrade with useless error if /var is
*** This bug is a duplicate of bug 1892358 ***
https://bugs.launchpad.net/bugs/1892358
** This bug has been marked a duplicate of bug 1892358
autopkgtest success rate dropped inhibiting proposed migration
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@juliank As I understand the definition of the needs-internet
restriction Ubuntu's CI does not provide that and still running those
small number of potentially tests is worse than loosing the result by
not executing them.
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README
The SRU is being pre-tested in https://bileto.ubuntu.com/#/ticket/4217 .
There are a low number of test failures which could indicate regressions, those
are being checked and fixed if needed before the upload to the archive.
Additional testing is welcome.
--
You received this bug notification
@sil2100 Thanks! IMO this is still an issue with the test infra.
** Changed in: libreswan (Ubuntu)
Status: New => Fix Released
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Regarding the splitting of the packages GCE OS Config needs more time to
be ready for releasing it because the required version of the Go
packages was higher than the version they existed in the archive with
and the updates started a chain reaction requiring upgrading several
other packages.
The
** Branch linked: lp:~rbalint/britney/hints-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892903
Title:
autopkgtest with needs-internet restriction fails
To manage notifications about this
Thank you for the review! I've fixed the copyright in
20200617.00-0ubuntu3. I'm continuing with the MIRs of the dependencies,
I indeed missed this golang-specific requirement.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
>From libreswan debian/tests/control:
Tests: opportunistic
Restrictions: needs-root, isolation-machine, needs-internet, skippable
Depends:
...
Is there a particular reason for not wanting to mark this configuration file as
a configuration file? UCF_FORCE_CONFFOLD and UCF_FORCE_CONFFMISS provide the
exact behaviour you described and if used only in non interactive mode the
users would even have a chance to review changes.
Without
Previously created files should also be updated to work with newer
kernels.
** Changed in: ec2-hibinit-agent (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@paelzer The fstab bug is LP: #1877078, I'm waiting for @vorlon's
comment's about what his plan is after his revert.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892358
Title:
autopkgtest success
@vorlon What is your plan regarding this fix? The revert may have helped
MAAS, but broke all LXD instances. IMO if MAAS relied on having a broken
fstab then MAAS should be fixed and not LXD images should be broken, so
I'd prefer having this fix in again. Maybe with /etc/fstab as an empty
file
LP: #1877078 fix got reverted and the sqashfs and LXD images ship with
invalid fstab again booting into degraded mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890803
Title:
Groovy amd64 /
This change got reverted in livecd-rootfs and now breaks systemd
autopkgtest.
livecd-rootfs (2.683) groovy; urgency=medium
* Revert the removal of fstab from squashfs images, which has had knock-on
effects and breaks MAAS (ref bug #1890803)
-- Steve Langasek Wed, 12 Aug 2020
11:31:12
Tests-in-lxd fails because LXD images ship invalid /etc/fstab again making
systemd-remount-fs.service fail.
I'm marking systemd-fsckd test as flaky to not block others' work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm testing the fix in Bileto and will upload it if the tests found no
regression:
https://bileto.ubuntu.com/#/ticket/3801
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Since this affects only upgrades from pre-246 versions the severity
should be High only. I'm testing the fix in Bileto and will upload it if
the tests found no regression:
https://bileto.ubuntu.com/#/ticket/3801
** Changed in: systemd (Ubuntu)
Importance: Critical => High
--
You received
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/101
** Bug watch added: Debian Bug tracker #968589
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968589
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968589
Importance: Unknown
** Changed in: systemd (Ubuntu)
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/1891716
Title:
Networking broken after systemd update
To manage notifications about
*** This bug is a duplicate of bug 1770480 ***
https://bugs.launchpad.net/bugs/1770480
** This bug has been marked a duplicate of bug 1770480
preadv2 test does not consider new flag from linux 4.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790205
Title:
systemd journals take up a lot of space, and it's not obvious how
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891215
Title:
systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: systemd (Ubuntu)
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.ne
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Description changed:
- WIP, I'm seeking for approval to subscribe Foundations to the package
-
[Availability]
Google-guest-agent is in universe and only depends on packages provided in
main or by the source package itself. The package is new in Groovy, but it
replaces part of old
Public bug reported:
WIP, the package is in -proposed only yet
[Availability]
Google-osconfig-agent is in universe and only depends on packages provided in
main or by the source package itself. The package is new in Groovy. The package
builds for all architectures.
[Rationale]
This package is
Public bug reported:
WIP, I'm seeking for approval to subscribe Foundations to the package
[Availability]
Google-guest-agent is in universe and only depends on packages provided in main
or by the source package itself. The package is new in Groovy, but it replaces
part of old
The fstab was removed in LP: #1877078, because it was invalid. The empty
fstab is equivalent to not having an fstab and missing /etc/fstab is
valid, at least I found no source (like FHS) saying that it must exist
even if it would be empty.
--
You received this bug notification because you are a
** Package changed: systemd (Ubuntu) => zsys (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891867
Title:
zfs not correctly imported at boot
To manage notifications about this bug go to:
Public bug reported:
Many dependencies are missing on i386 and the package is not in the set
of packages to be maintained for i386.
** Affects: rust-gtk (Ubuntu)
Importance: Undecided
Status: New
** Tags: groovy
--
You received this bug notification because you are a member of
The other well established method is the one used extensively with
systemd units, where file in /lib/systemd/system can be overridden by a
file with the same name in /etc/systemd/systemd .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The standard self-descriptive way of doing that is using ucf. Do you
mean openssh-server by SSHD? It uses ucf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870314
Title:
[needs-packaging]
Public bug reported:
reason for rust-cookie's removal:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948642
** Affects: rust-cookie-store (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
--
You received this bug notification because you are a member of
https://launchpadlibrarian.net/493472305/buildlog_ubuntu-groovy-riscv64.rust-onig-sys_69.2.0-1build1_BUILDING.txt.gz
...
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code
101
...
** Description changed:
Please see latest build log.
+
+ I propose fixing this class
Public bug reported:
Please see latest build log.
I propose fixing this class of bugs by disabling tests on riscv64 for
now: LP: #1891686.
** Affects: rust-onig-sys (Ubuntu)
Importance: Undecided
Status: New
** Tags: udpate-excuse
** Tags added: udpate-excuse
--
You received
There are many similar bugs filed against dpkg, is this an APT issue
running dpkg wrong?
** Package changed: dpkg (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891663
Public bug reported:
The builders use more cores than on other architectures to speed up
builds but running riscv64 tests are still very slow in the current
emulated enviromnent and they can also be flaky blocking packages from
migration via the missing builds.
** Affects: dpkg (Ubuntu)
Public bug reported:
Same in Debian.
** Affects: rust-tokio-core (Ubuntu)
Importance: Undecided
Status: New
** Affects: rust-tokio-core (Debian)
Importance: Unknown
Status: Unknown
** Tags: update-excuse
** Bug watch added: Debian Bug tracker #952137
Since lightdm works OK there is most likely something that GDM could do
differently.
I think this is a duplicate of LP: #1745664 . Does installing ncsd
resolve the issue with gdm3, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: gdm3 (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/1882034
Title:
cannot start X session with NIS account
To manage
Seems like the debconf GTK frontend could not find an icon, needs more
investigation.
** Package changed: unattended-upgrades (Ubuntu) => debconf (Ubuntu)
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for the review. I'm fixing the config file location typo in
the next upload.
Ubuntu's package installation ensures that modified local configuration files
are not overwritten without consent.
Having an old file in /etc/... triggers the following question which is better
than silently
Systemd since then migrated and probably we don't want to have the
kernel migrated as well to trigger the issue, thus I've added the block-
proposed tag.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: systemd (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/1886886
Title:
Plymouth 0.9.5 release
To manage notifications about this bug go to:
Unattended-upgrades may handle this exception by exiting with failure
and not re-raising it to the top.
** Changed in: unattended-upgrades (Ubuntu)
Status: Opinion => Triaged
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => Low
--
You received this bug
*** This bug is a duplicate of bug 1871145 ***
https://bugs.launchpad.net/bugs/1871145
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
unattended-upgrades. This problem was most recently seen with package version
2.3ubuntu0.1, the
I have this PPA build log: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4017/+build/19810464
I had other failures, just retried them.
I _think_ I have seen it in autopkgtest as well, but I may be wrong and only
builders are affected.
I started looking this up in autopkgtest logs
Ah, launchpad-buildd is already affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891403
Title:
glibc tst-getrandom test needs more entropy causing test failures
To manage notifications
** Changed in: strace (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: strace (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@juliank As I read autopkgtest package's changelog haveged used to be installed
but it was dropped in 5.11.
I used haveged in local tests and it seems to fix the test as expected and I
think the scalingstack install needs adjusting. I suspect there is enough
entropy for most of the things, the
** Summary changed:
- glibc tests needs more entropy causing tst-getrandom failures
+ glibc tst-getrandom test needs more entropy causing test failures
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
* Builds and autpkgtests frequently fail due to failing tst-getrandom
probably due to insufficient source of entropy on Launchpad. This causes
extra work by requiring retriggering failing builds and autopkgtests.
[Test Case]
* Observe tst-getrandom tests being
Fastboot is known to cause issues on older CPUs:
https://wiki.archlinux.org/index.php/intel_graphics#Fastboot
If the i915.fastboot=1 option was _not_ set by you manually then please
reopen the bug by settint status to New.
** Changed in: systemd (Ubuntu)
Importance: High => Undecided
**
** Tags added: block-proposed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890913
Title:
init is using 100% of processor
To
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889069
Title:
glibc FTBFS with gcc-10 10.2.0-3ubuntu1
To manage notifications about this
This commit is already present in Focal and later releases.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
**
Is there a reliable way I can reproduce the problem? (I don't face it on my
laptops.)
Is this happening on any Ubuntu-certified model? This could let our
certification team to investigate the issue.
How can the systemd help? killing plymouth earlier?
** Changed in: systemd (Ubuntu)
** Description changed:
[Impact]
pwd/test-getpw test fails in autopkgtest
- Fixing this makes the arm64 autopkgtest usable again for the lifetime of the
20.04 LTS release.
+ Fixing this makes the arm64 and armhf autopkgtests usable again for the
lifetime of the 20.04 LTS release.
** Description changed:
[Impact]
Programs previously using nanosleep syscall and with glibc 31's update
being switched to use clock_nanosleep broke due to clock_nanosleep using
CLOCK_REALTIME returns EINVAL in wsl1.
[Test Case]
Run sleep in WSL1 on Windows 10 2004 or older
This is happening on armhf as well so I extend the patch to cover armhf,
too.
root@gg-libc-test:~# /lib/ld-linux-armhf.so.3 ./getauxval
0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869364
Title:
** Description changed:
[Impact]
After ubuntu-glibc maintainers changed "math-vector-fortran.h" install
directory (LP#1861353), gfortran can no longer use it.
[Test Case]
This the old (good) behavior Ubuntu 19.10 gcc-9.2.1 glibc 2.30
$ gfortran -O3 -mavx2 vect_test.f90 -o
** Summary changed:
- Consistent autopkgtest failures on ppc64el/s390x
+ (In)consistent autopkgtest failures on ppc64el/s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851663
Title:
Public bug reported:
https://autopkgtest.ubuntu.com/packages/p/prometheus-process-
exporter/groovy/amd64
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/p/prometheus-process-exporter/20200804_163925_0556b@/log.gz
...
#
Public bug reported:
https://autopkgtest.ubuntu.com/packages/p/polyml/groovy/amd64
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/p/polyml/20200804_163843_f2ccb@/log.gz
...
autopkgtest [16:38:10]: test upstream-polyc:
Public bug reported:
https://autopkgtest.ubuntu.com/packages/c/chiark-tcl/groovy/amd64
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/c/chiark-tcl/20200804_165906_84cff@/log.gz
...
crypto--def FAIL badpkg
blame:
Public bug reported:
https://autopkgtest.ubuntu.com/packages/c/cfitsio/groovy/amd64
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
groovy/groovy/amd64/c/cfitsio/20200804_160906_a6ead@/log.gz:
...
autopkgtest [16:08:52]: test testprog:
** Description changed:
[Impact]
Programs previously using nanosleep syscall and with glibc 31's update
being switched to use clock_nanosleep broke due to clock_nanosleep using
CLOCK_REALTIME returns EINVAL in wsl1.
[Test Case]
Run sleep in WSL1 on Windows 10 2004 or older
The failing systemd-fscks autopkgtest is a test bug and should be fixed
in systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886886
Title:
Plymouth 0.9.5 release
To manage notifications
Public bug reported:
https://autopkgtest.ubuntu.com/packages/libx/libxmlb/groovy/amd64
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
groovy/groovy/amd64/libx/libxmlb/20200803_212158_ebe4f@/log.gz :
...
** Changed in: dogtag-pki (Ubuntu)
Status: New => Fix Released
** Changed in: dogtag-pki (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/a/apache2/20200803_224820_a4672@/log.gz
...
# Failed test 17 in t/apache/expr_string.t at line 87
t/apache/expr_string.t ..
Failed 1/29
** Description changed:
+ [Impact]
+
+ Programs previously using nanosleep syscall and with glibc 31's update
+ being switched to use clock_nanosleep broke due to clock_nanosleep using
+ CLOCK_REALTIME returns EINVAL in wsl1.
+
+ [Test Case]
+
+ Run sleep in WSL1 on Windows 10 2004 or older
** Description changed:
+ [Impact]
+
+ pwd/test-getpw test fails in autopkgtest
+ Fixing this makes the arm64 autopkgtest usable again for the lifetime of the
20.04 LTS release.
+
+ [Test Case]
+
+ Observe autopkgetest tests passing, including pwd/test-getpw being
+ marked as XFAIL.
+
+
** Changed in: glibc (Ubuntu)
Status: Invalid => 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/1871129
Title:
htop is blank when using in focal in wsl1
To manage notifications
** Description changed:
[Impact]
- * Upgrade from Bionic to Focal may break
- * The upload really forces
+ * Upgrade from Bionic to Focal may break if LDCONFIG_TRIGGER_DEBUG is set
+ * The upload really forces
[Test Case]
$ lxc launch ubuntu:bionic bb-glibc-upgrade
- $ lxc
** Description changed:
+ [Impact]
+
After ubuntu-glibc maintainers changed "math-vector-fortran.h" install
directory (LP#1861353), gfortran can no longer use it.
- This the old behavior Ubuntu 19.10 gcc-9.2.1 glibc 2.30
+ [Test Case]
+
+ This the old (good) behavior Ubuntu 19.10
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
** This bug has been marked a duplicate of bug 1805183
systemd-resolved constantly restarts on Bionic upgraded from Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
** This bug is no longer a duplicate of bug 1832050
chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr)
** This bug has been marked a duplicate of bug 1805183
systemd-resolved
I've added the OEM Solutions Group team for awareness. I'm not sure what
the final fix will be since servers' and desktops'/laptops' ideal
default seem to be different, but most likely the certification tests
should be adjusted if we don't end up restoring the previous behaviour
of the
901 - 1000 of 3233 matches
Mail list logo
