Thanks Rbalint for fixing that.
Since a triggering change in qemu is in at least >=Bionic and was reported to
even affect continuous unattended upgrades there would you considering SRUing
your changes as needed?
I added tasks for all releases, but set >=Bionic to high to to that being an
issue i
root@d-upgr:~# apt remove multipath-tools -s
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
ibverbs-providers kpartx libaio1 libfreetype6 libibverbs1 libnl-3-200
libnl
Change introduced in Ubuntu-meta in 1.431 [1]
But since that usually only reflects the seeds that must be from there somehow.
[1]: https://launchpad.net/ubuntu/+source/ubuntu-meta/1.431
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
Germinate [2] clearly points at the seeds.
bin:multipath-tools src:multipath-tools why:Ubuntu.Disco server seed
bin:multipath-tools-boot src:multipath-tools why:Ubuntu.Disco
server-ship-live seed
The second I saw before in the seeds [1], but where exactly is the first
line listed here within
Yep, once checking the right and up to date branches it seems clear.
I found [1], subscribing xnox here as well.
This change was on late February, there was no ubuntu-meta update since
then so the issue wasn't triggered.
I think we'd want to undo the seed change, but in a fashion so that what
xno
Now that we know that we can drop all bug ubuntu-meta task, marking the
others invalid.
** Changed in: multipath-tools (Ubuntu)
Status: New => Invalid
** Changed in: multipath-tools (Ubuntu)
Status: Invalid => Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 1823093 ***
https://bugs.launchpad.net/bugs/1823093
This was initially triggered by:
https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu-seeds/+merge/363541
Which was matching cleanups we did earlier this year and again in Malta.
But that there was fa
On s390x it only uses sysinfo for systemd-detect-virt,
src/basic/virt.c:306:r = get_proc_field("/proc/sysinfo", "VM00
Control Program",
WHITESPACE, &t);
but there also the Host UUID is exposed:
$ cat /proc/sysinfo
VM00 UUID:0804001f-c45f-4345-994f-9fec048e822e
There
Apparmor is disabled in LXD containers now !?!
Compare aa-status after spawning a new container.
root@d-testapparmor:~# aa-status
apparmor module is loaded.
15 profiles are loaded.
15 profiles are in enforce mode.
/snap/core/6673/usr/lib/snapd/snap-confine
/snap/core/6673/usr/lib/snapd/snap
In that container that has no profiles at all I can explicitly load them.
$ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd
$ systemctl restart libvirtd
makes it show up correctly
1 processes are in enforce mode.
/usr/sbin/libvirtd (1146)
But why is it missing in the first place
Since I started seeing this in libvirt There might be reasons that is done that
way but this affects me and probably other use cases e.g. if I install libvirt:
$ apt install libvirt-daemon-system
$ aa-status | grep libvirt
On my test systems the containers do not get any profile loaded:
$ aa-
In Cosmic /lib/systemd/system/apparmor.service pointed to "/etc/init.d/apparmor
start"
This had some code, but it was not triggered:
if [ -x /usr/bin/systemd-detect-virt ] && \
systemd-detect-virt --quiet --container && \
! is_container_with_in
Adding set -x and calling this directly:
Cosmic:
. /lib/apparmor/functions
is_container_with_internal_policy
+ local ns_stacked_path=/sys/kernel/security/apparmor/.ns_stacked
+ local ns_name_path=/sys/kernel/security/apparmor/.ns_name
+ local ns_stacked
+ local ns_name
+ '[' -f /sys/kernel/securit
Yep, adding
Environment=SFS_MOUNTPOINT=/sys/kernel/security/apparmor/
to
/lib/systemd/system/apparmor.service
Fixes the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs
I checked case (B) that I added.
First I created a new setup as described (to make sure no old modifications
influence the verification)
That worked, I saw the wait line on boot:
[*** ] A start job is running for Wait for… to be Configured (29s / no limit)
After boot I had the wait time in the
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1823474
Title:
package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
Hi,
I'm not at all an dconf expert.
But after identifying that even base dconf-editor does not let you save things
I think we can eliminate virt-manager from the equation.
I have added a task to this bug for d-conf to get maintainers of that package
to take a look.
They might know where to look
FYI:
I was affected by the issue, but there must be another way to trigger than the
(re)install of console-setup and/or keyboard-configuration as those actions
were not triggering the issue for me after I rebooted.
OTOH the time it started to happen perfectly matches a background update to
those
I only have a testcase for Bionic, I hope rbalint has one for the other
releases.
root@b:~# apt list --upgradable
Listing... Done
qemu-guest-agent/bionic-updates,bionic-security 1:2.11+dfsg-1ubuntu7.12 amd64
[upgradable from: 1:2.11+dfsg-1ubuntu7]
N: There is 1 additional version. Please use the
I can indeed trigger it in cosmic with an upgrade from 1:2.12+dfsg-
3ubuntu8 -> 1:2.12+dfsg-3ubuntu8.6
But forcing the same (by enabling cosmics sources) in Disco does not trigger
the bug (1.10ubuntu5).
You will need an equiv trick to verify Disco as well I think.
Here he logs of the cosmic veri
With some more trickery I created this situation in Disco:
root@d:~# apt-cache policy qemu-guest-agent unattended-upgrades
qemu-guest-agent:
Installed: 1:2.12+dfsg-3ubuntu8
Candidate: 1:2.12+dfsg-3ubuntu8.6
unattended-upgrades:
Installed: 1.10ubuntu5
Candidate: 1.10ubuntu5
But in that cas
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
Title:
[apparmor] missing 'mr' on binary for usage on containers
Status in rsyslog packa
I have not seen/triggered the kernel issue mentioned in here (identified by
jdstrand).
But on request I'll try it at least.
Testing on Disco with Host Having:
5.0.0-13-generic
# Create container and trigger the issue:
lxc launch ubuntu-daily:d d-testapparmor
# update the container to not have th
Ordering was important:
$ modprobe shiftfs
$ sudo snap set lxd shiftfs.enable=true
$ sudo systemctl restart snap.lxd.daemon
Now it is enabled:
$ lxc info | grep shiftfs
shiftfs: "true"
$ lxc exec d-te
** Tags added: server-next server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1749774
Title:
include fwupd packages in Server Seed
Status in ubuntu-
** Tags added: server-next server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1748956
Title:
replace uses of net-tools with iproute2
Status in byobu
Thanks Steve for the ping for awareness!
It still all is in main, and I checked the old MIR bug 1536871 for any
extra context that might have been mentioned there.
It already is in desktop-common (and due to that in all desktop tasks).
It is there as recommends which I appreciate for the rare cas
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Canonical Server Team (canonical-server)
** Changed in: ubuntu-release-notes
Assignee: Canonical Server Team (canonical-server) => Ubuntu Serve
TBH that is just showing that [1], fell through the cracks :-/
We are early in Eoan - lets do this now - worst case slightly break it and
resolve details afterwards.
I made it part of another seed/meta change Eoan to do both in one [2].
Further I have added a release-note task to mention it in Eo
MP prepared in [1]
[1]: https://code.launchpad.net/~paelzer/ubuntu-
seeds/+git/ubuntu/+merge/367238
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1749774
Title:
incl
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/ubuntu/+merge/367238
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.
** Changed in: openldap (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: openldap (Ubuntu Trusty)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
FYI: The tests were already retried (thanks seb128) and are good now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1876320
Title:
Port parameter sshd_config is 22 AND wha
Public bug reported:
Hi,
DPDK has run into some issues in the past
https://bugs.dpdk.org/show_bug.cgi?id=97
https://bugs.dpdk.org/show_bug.cgi?id=249
Eventually the issues got resolved in binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=23465
After binutils is fixed people rebuild
Retest as-is:
root@f:~# dpkg -l openssh-server
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==
Added an SRU Teamplate entry in the description, thanks Bruce for the
test.
The changes build fine, all self tests on build are good [1].
The dep8 sniff tests have just started at [2] and will later be available there.
The changes are rather small as seen on [3]
But while all that shall help by b
Tested in Bionic Container:
no PPA:
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
avx.o | grep vmovaps
0: 62 f1 7c 48 28 04 05vmovaps 0x1(,%rax,1),%zmm0
with PPA:
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
avx.o | grep
A few dep8 tests failed in the sniff, but all of them are existing known
overrides in Bionic:
ubuntu-release:9:force-badtest dh-ada-library/6.12
ubuntu-release:18:force-badtest lintian/2.5.81ubuntu1
pitti:2:force-badtest rpmlint/1.9-6
ubuntu-sru:17:force-badtest snapcraft/2.43.1+18.04/amd64
snapc
od as well.
I uploaded to bionic-unapproved for consideration by the SRU Team.
** Changed in: binutils (Ubuntu Bionic)
Status: New => In Progress
** Changed in: binutils (Ubuntu Bionic)
Assignee: Matthias Klose (doko) => Christian Ehrhardt (paelzer)
** Tags added: server-ne
I want to look at this again ...
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
Ti
Let us kill the SRU - given what happened last time and that this is a
a) disabled by default profile
and
b) user fixable by editing a conffile
If it is ok with you I'd better focus on merging the latest version +
your improvement in
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git
: Undecided
Assignee: Christian Ehrhardt (paelzer)
Status: In Progress
** Changed in: rsyslog (Ubuntu)
Status: New => In Progress
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because y
upload/8.2001.0-1ubuntu1 has the former delta already split
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1885125
Title:
merge 8.2006.0-1 and include apparmor fixes
Stat
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/386381
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1885125
Ti
Yeah I have considered it as nice drive-by improvement unrelated to this bug -
and thanks for doing so.
I just had sorted out some lose ends on rsyslog and they both where part of it.
Since this didn't work last time it is not closed yet, but open at low prio.
As explained TBH I think we won't do
Hi Yuri,
there was no recent change in regard to lvm handling in libvirt or lvm itself
that would obviously be related. Which Ubuntu release are you on - and between
which package versions did you upgrade?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
FIY uploaded to groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1885125
Title:
merge 8.2006.0-1 and include apparmor fixes
Status in rsyslog package in Ubuntu:
In
Hi Harry,
the real action/verification will be needed ocne the SRU team has accepted that
into proposed [1].
If you want to test the PPA the following will enable it on your system:
$ sudo add-apt-repository ppa:ci-train-ppa-service/4105
The PPA tells you that on its front page [2] as well, I j
in: openssh (Ubuntu)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
This is server-next as soon as 8.4 is in groovy, I tagged it already to
not forget it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1885990
Title:
server: Match has no e
On first check by the SRU team I got:
[18:34] cpaelzer: ok, looking at the binutils SRU, so you talked to
do_ko about it, right? Was he +1 on the change?
He was in a private IRC, I now asked him to state it here as well so
that it is visible to the SRU team. And he already did so - thanks!
[18:
To have a bileto PPA with security only (thanks Sil2100 for stopping it to
reconfigure itself) look at:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4151
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils
Note: overall bugs with this tag
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=writable-etc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1849560
Title:
Please revise
Hmm,
are we sure anyone still cares about this.
Sadly Matthieu isn't around anymore and we had no one else from UC20 speak up
at all since then.
If someone really still depends on this please speak up here!
IMHO "whishlist" + "server-next" are almost kind of mutually exclusive.
Further I can th
Hi Joi,
thanks for the extra data, I still can't think of a case to create this.
Looking forward to what you find checking this in more detail.
When in the error case could you look around which seccomp the system still has
around?
For example via:
$ ls -laF /lib/x86_64-linux-gnu/libseccomp*
/us
with:
2.30-21ubuntu1~18.04.3
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
avx.o | grep vmovaps
0: 62 f1 7c 48 28 04 05vmovaps 0x1(,%rax,1),%zmm0
with:
2.30-21ubuntu1~18.04.4
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
Autopkgtest issues resolved, all good now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1883880
Title:
fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
** Bug watch added: Debian Bug tracker #963702
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963702
** Also affects: binutils (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963702
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
The last two updates went smooth for me, not triggering it.
I'm still too afraid to "just update while working" as I did in the past since
it could drag things down thou :-/
I was feeling like this could be solved, but reading that Steve is also
affected I'm worried that I might just not hit the
Fixed in 1:8.2p1-1 and
openssh | 1:8.2p1-4 | focal| source
openssh | 1:8.2p1-4ubuntu0.1 | focal-updates| source
openssh | 1:8.3p1-1 | groovy | source
So this should be fix released, btu wasn't updated.
** Changed in: openssh (Ubuntu)
Status
Hi Cliff and thank you for the report.
Hmm, neither the later 3.2.2 nor the yet unreleased 3.2.3 mention any fix in
that regard.
https://download.samba.org/pub/rsync/NEWS#3.2.2
I guess we'd be down to bisecting for the offending change or something like it.
As-is I'm not seeing the issue when rs
Thanks, with that config (or a subset thereof) how do you run your
server (if it is anything more than sshd or such) and your client (the
actual rsync call)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
htt
@Cliff
- if you run the above simplified case does it work for you?
- if it does, could you try making it closer and closer to your setup until
you've identified what
makes it break?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
Thanks Cliff!
Note: the server question you wondered would have been the details how exactly
(commands&config( you do "syncd is enabled and started at boot with the
rsyncd.conf". Because in that might lay the details we need.
I was setting up a server on my own aligned to your config.
The follow
Maybe permission differences of the path to /home/cliff/Bin vs
/mnt/testrsync
Did you start the daemon like I did as root or under a different user?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bug
This won't auto-sync as there is Delta.
This MP is up to merge the latest version from Debian.
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/rsync/+git/rsync/+merge/388554
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
@Malek - hi, chances that you have a different bug that just seems to be
similar are very very high.
I recommend reporting a new bug so that your logs are automatically attached.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Hi Seb, as far as I understood Cliff it only started to occur with version
3.2.1 in Groovy.
And after we found the root cause that is now confirmed, 3.2.1 has:
ProtectSystem=full
ProtectHome=on
PrivateDevices=on
NoNewPrivileges=on
But the version in Focal doesn't have that and thereby is fine with
Hi Toby,
It seems that is an ongoing topic for years, I've found this discussed
from the KRB POV [1] and on openssh [2]. Especially following [1] it
seems things aren't too easy but there are a few workarounds/hints that
might or might not help your use case.
In general having this configurable i
Due to that hint with SciLinux I have fetched
http://ftp.scientificlinux.org/linux/scientific/7.8/SRPMS/vendor/openssh-7.4p1-21.el7.src.rpm
I can't see it but that is https://bugzilla.redhat.com/show_bug.cgi?id=991186
I can see follow on issues referring to it
https://bugzilla.redhat.com/show_bug
The new code now handles sockets and services differently from libvirt
packaging.
There might also have been changes to the various debhelpers, but the TL;DR is
that I no more see this issue with libvirt 6.6.
I'll mark the bug as closed with that, but please report back if you
happen to find a c
Public bug reported:
The builds for riscv64 on e.g.
https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6build1
hang eventually.
All other architectures work fine.
Build log tail will be like:
...
symlinking changelog.Debian.gz in dee-tools to file in libdee-1.0-4
pkgstripfiles: Run
If you catch the log at the right time there is a related test failure:
** (dbus-test-runner:1577514): WARNING **: 12:15:11.723: Timing out at maximum
wait of 60 seconds.
(dbus-test-runner:1577514): libdbustest-CRITICAL **: 12:15:11.736:
dbus_test_service_run: assertion 'all_tasks(service, all_t
FYI - I'm driving soem debugging enabled test builds at
https://launchpad.net/~paelzer/+archive/ubuntu/dee-groovy-hang/+packages
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4192/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Good case:
task-0: Shutting down
DBus daemon: Shutdown
make[4]: Leaving directory '/<>/dee-1.2.7+17.10.20170616/tests'
Bad case:
task-0: /ModelTags/SharedModel/TwoTags: OK
** (dbus-test-runner:2028709): WARNING **: 12:41:16.457: Timing out at
maximum wait of 60 seconds.
(dbus-test-runner:20287
When lowering the timeout to trigger the same on x86 (to see if the hang
occurs there as well) I can see that the test breaks as it does on
riscv64, but the hang does not happen.
task-0: /Model/Transaction/Target2ChangeRemoveAppend:
OK
** (dbus-test-runner:15767): WARNING **: 11:26:03.671: Timi
>From IRC:
[13:34] Laney: ha - timeout = 1 on x86 triggers the same
warnings/erorrs, but NOT the hang of the builder
[13:34]
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4200/+build/19818311
is an example
[13:34] interesting
[13:35] perhaps riscv64 does process reaping differe
It turned out that this has happened in the past and then resolved, so this is
a comeback.
For "dee" we can bump the timeout or skip the test on riscv64 for the immediate
problem
But the "dbus-test-runner timeout makes riscv64 builds" hang is a problem on
its own.
Therefore I added a bug task t
Bumping the timeout isn't enough :-/
It still gets into the hang and breaks build.
Chances are we are not actually facing a timeout issue, but something around
/var/log/launchpad-buildd/default.log-20200812:2020-08-11 12:45:42+ [-]
Build log: (dbus-test-runner:1807632): libdbustest-CRITICAL
When running the build in a local groovy qemu riscv64 guest the test
left no dbus-test-runner processes for debugging around :-/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dee in Ubuntu.
https://bugs.launchpad.net/bugs/18
still build-depends on python-evdev - we will have to remove autopilot-
gtk as it didn't build for two releases now (F+G).
Fixable with a new upload that resolves the dependency issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
Hmm thanks Raphaël.
So files were still around that were unowned, that really should not happen.
Thanks for the exact file names.
The files you had in your case were part of libseccomp2 2.3.1-2.1ubuntu4 which
is what Ubuntu had in Bionic-release.
libseccomp2 | 2.3.1-2.1ubuntu4 | bion
[17:48] rbalint: I was checking the systemd autopkgtests which were
flaky retries and which were real issues
[17:48] rbalint: and it seems all were flaky (most resolved now and
src:audit in the queue to be tested)
[17:49] rbalint: but one remained - plymouth - that seemed to be a
genuine issu
FYI - the original bug would be tackled once
https://launchpad.net/ubuntu/+source/plymouth/0.9.5-0ubuntu2 migrates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1886886
Tit
https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6ubuntu1 build
fine now.
It depends on ICU, but otherwise is ready to go now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dee in Ubuntu.
https://bugs.launchpad
The problem is Ubuntu only, as [1] is good.
And the real fix should be in dbus-test-runner, but without repro it will be
unclear if anyone gets to that or if we just hope it resolves itslef (again).
But due to the above it makes no sense to submit the fix to Debian - as
for them it would reduce t
** Summary changed:
- Kernel panic booting after 18.04 to 20.04 upgrade
+ systemd breaks due to old libsecomp libs left on the system
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpa
Adding slapd task since it is mentioned to break there.
Seems to be a regression from 18.04 -> 20.04 as far as a I read it,
tagging as such for now.
@Andreas - any chance to recreate this on your side?
** Also affects: openldap (Ubuntu)
Importance: Undecided
Status: New
--
You receiv
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/389531
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1869796
Ti
Public bug reported:
Hi,
we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130
is about the same as well. There were more but I didn't want to search for all
of them - what I checked is that there are no open ones clearly pointing out
the recent further drop in already
Thank you Rbalint.
Thanks to xnox I already found 1891716 and 1886886 which are sort of
remotely related (to the next upload), I guess this bug will serve for
the "marking systemd-fsckd test as flaky" task then.
Can we do something about this bad fstab in LXD or is there a bug to
track?
Essentia
Adding update-excuse tag so that one can find this issue from update-excuses
page.
To show up at the packages that fail I also add an qemu and kbd task (more
might pile up)
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Also affects: kbd (Ubuntu)
Importance: Undecided
Added another two packages that are blocked by this so they are
marked/linked in update excuses :-/
** Also affects: iputils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iputils (Ubuntu)
Status: New => Confirmed
** Also affects: ntpsec (Ubuntu)
Importance: Undeci
Adding glib2.0 as it had a rebuild for libffi and will be blocke dby
this as well.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubun
This no more affects libvirt, marking it as such to not show up in
excuses.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
** Changed in: libselinux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1892455
Title:
[MIR] libselinux1
Status in libselinu
[16:34] seb128, cpaelzer ahasenack sorry, i was out and apparently
forgot setting that in my email. the last systemd upload should fix everything
except for the livecd-rootfs revert that made fstab in lxd images invalide
[16:45] rbalint: " the last systemd upload" means groovy I guess,
what ab
What is left is the similar situation in Focal (as mentioned before).
I have updated the tasks to reflect that properly and get update-excuse tagging
there.
In Focal it is currently blocking qemu and build-essential SRUs and I
wanted to ask if the plan is to do the same upload+test-reset there or
901 - 1000 of 1238 matches
Mail list logo
