Here is a better test case in my opinion. If you (reporter, or uploader,
or Eric) agree, could you please update the test plan in the
description?
To reproduce the bug:
# download sample midi file from wikiepdia:
wget https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid
# play
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/458373
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2042587
Test script
** Description changed:
[ Impact ]
When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
stopped working in an environment where a DHCP relay is in use. Instead
of the expected client IP address, the script gets the _relay_ IP
address as an argument.
-
Test script
** Description changed:
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this
Reproduced the problem and verified the fix.
@timotunk, if you would like to give the fix a try, it's available in
this PPA for jammy:
https://launchpad.net/~ahasenack/+archive/ubuntu/dnsmasq-
relay-2042587/+packages
I'll in the meantime prepare the SRU paperwork and merge proposal for
review.
I believe this to be the fix:
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=1c8855ed10d3923a9a4fd8a89f1c95439d4c8827
>From 1c8855ed10d3923a9a4fd8a89f1c95439d4c8827 Mon Sep 17 00:00:00 2001
From: Simon Kelley
Date: Sun, 26 Dec 2021 16:35:54 +
Subject: [PATCH] Fix wrong client
Uploaded to jammy unapproved, waiting on SRU team now.
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/457905
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hello Lucas, or anyone else affected,
Accepted base-files into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/9.4ubuntu4.14 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Lucas, or anyone else affected,
Accepted base-files into lunar-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/12.3ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Lucas, or anyone else affected,
Accepted base-files into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/12ubuntu4.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Lucas, or anyone else affected,
Accepted base-files into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/11ubuntu5.8 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Lucas, or anyone else affected,
Accepted base-files into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/10.1ubuntu2.12 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Lucas, or anyone else affected,
Accepted base-files into mantic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/13ubuntu2.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Yep, false alarm, the patch works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2045570
Title:
dnsmasq crash when no servers in resolv.conf
Status in dnsmasq package
Ah, never mind, I built the package incorrectly. It's not a quilt
package... :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2045570
Title:
dnsmasq crash when no
So with the upstream patch, I see no crash, but dnsmasq starts spinning
CPU at 100%. This is not a good enough fix.
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there were no
"nameserver" declarations in the updated file, dnsmasq can crash.
Here is a log of a reproducer:
$ dig
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there were no
"nameserver" declarations in the updated file, dnsmasq can crash.
Here is a log of a reproducer:
$ dig
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there were no
"nameserver" declarations in the updated file, dnsmasq can crash.
Here is a log of a reproducer:
$ dig
** Description changed:
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [
dal-clients. Closes: #213316, #751203
[ Sam Hartman ]
* Enable build-time tests, Thanks Andreas Hasenack, Closes: #1017763
* Work around doxygen change that breaks doc build, Thanks Greg
Hudson, Closes: #1051523
-- Sam Hartman Mon, 11 Sep 2023 11:06:57 -0600
krb5 (1.20.
nks Andreas Hasenack, Closes: #1017763
* Work around doxygen change that breaks doc build, Thanks Greg
Hudson, Closes: #1051523
-- Sam Hartman Mon, 11 Sep 2023 11:06:57 -0600
krb5 (1.20.1-3) unstable; urgency=high
* Fixes CVE-2023-36054: a remote authenticated attacker can ca
Focal verification
# Reproducing the bug
ubuntu@f-ping-1964506:~$ apt-cache policy iputils-ping
iputils-ping:
Installed: 3:20190709-3
Candidate: 3:20190709-3
Version table:
*** 3:20190709-3 500
500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100
** Changed in: dnsmasq (Ubuntu Jammy)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I was able to reproduce this after a few attempts. Good enough for a
test plan/case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2045570
Title:
dnsmasq crash when no
** Changed in: dnsmasq (Ubuntu Jammy)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2045570
Title:
dnsm
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
Adrien, we do have openssl-ibmca in the archive, for the s390x arch:
$ rmadison openssl-ibmca
openssl-ibmca | 1.3.0-0ubuntu2 | xenial/universe | source,
s390x
openssl-ibmca | 1.3.0-0ubuntu2.16.04.2 | xenial-updates/universe | source,
s390x
openssl-ibmca | 1.4.1-0ubuntu1
There are two changes here:
a) The original bug: CMS_final() was not taking into account the result
of CMS_dataFinal() when returning its return code. It might be that
CMS_dataFinal() failed, in which case an error would even be raised, but
the return code of CMS_final() would be that of
Kinetic is EOL.
** Changed in: apparmor (Ubuntu Kinetic)
Status: Fix Committed => Won't Fix
--
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/1993572
Title:
samba
I prepared a ppa with the fix here:
https://launchpad.net/~ahasenack/+archive/ubuntu/wget-2029930
Packages are still building as I write this, and should be published in
an hour or so.
@halfgaar, would you be able to test it? I can easily upload to noble,
but for an SRU, we would require a bit
** Also affects: wget (Ubuntu Noble)
Importance: Low
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wget in Ubuntu.
https://bugs.launchpad.net/bugs/2029930
Title:
wget crash when printing
No update since Oct 27th, unsubscribing sponsors. Please subscribe again
if there is an update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP
This is stuck in noble migration, armhf test failures which I wasn't
able to reproduce neither locally, nor in the infrastructure with a ppa.
The actual infrastructure is having issues with armhf anyway, so a retry
there also didn't do anything yet. I'll keep an eye on it. Unsubscribing
sponsors,
Hello Ravi, or anyone else affected,
Accepted apparmor into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/2.13.3-7ubuntu5.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Bug watch added: Debian Bug tracker #1055316
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055316
** Also affects: heimdal (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055316
Importance: Unknown
Status: Unknown
--
You received this bug notification
I agree that a merge from debian would be better, since we are quite
behind:
iproute2 | 6.5.0-4 | testing
But we have been at 6.1.0 since at least lunar, so I don't know how long
that would take. I think we can take these patches for noble.
I would ask that you also add this one,
Checklist:
- preserved delta as needed
- correct ubuntu versioning and changelog entries (I updated the release name
to noble)
- debian changes are ok
- upstream changes are ok
- upstream gpg signature checks out
- test build failed at first locally in a noble lxd, but worked in a launchpad
ppa
Hello Philip, or anyone else affected,
Accepted systemd into mantic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/253.5-1ubuntu6.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks for the replies.
I note that the resolved defaults are also baked in in the default
config file /etc/systemd/resolved.conf, which on mantic currently states
"#MulticastDNS=resolve". With the new build, that shall change to "=no".
Unless users changed that file, this update should NOT
** Changed in: heimdal (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2040384
Title:
Merge heim
** Changed in: krb5 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/2040386
Title:
Merge krb5 from Deb
Hi Philip,
I have some questions here:
a) You state that some policy says that no ports other than 22 should be
open, which policy is that? Does it apply only to cloud images, or is it
an Ubuntu policy in general?
b) This is in mantic release at the moment, and switching that option
back to
Hi Georgia, is this still pending an evince fix? Your PPA has an updated
evince package, but I don't think it was uploaded to unapproved yet,
without the recommends.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Hi @enr0n, could you please comment on Chris's remark above about the
state of this SRU?
--
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/2036358
Title:
systemd wait-online
I'm seeing this problem with a few snaps on a bionic lxd, where lunar is
the host:
classic snaps:
$ git ubuntu merge --help
internal error, please report: running "git-ubuntu" failed: transient scope
could not be started, job /org/freedesktop/systemd1/job/29 finished with result
failed
$
The DEP8 tests are green now, but we still need verification on this
bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1964506
Title:
Ping: checks payloads incorrectly,
Time calculations can be so tricky!
The patch is also changing the non-human-readable case (without -p), if
I understood it correctly. I think this also needs to be tested.
I think it would be beneficial to include the upcoming fix for the other
corner case you found, when uptime is exactly 60s,
Public bug reported:
See ubuntu-devel thread[1] and mantic rebuild report[2].
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match
completely
The verification of the Stable Release Update for openssh has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
All autopkgtests have been cleared after retries (both lunar and jammy
ones).
--
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/2031942
Title:
AuthorizedPrincipalsCommand is
Hello Matthew, or anyone else affected,
Accepted openssh into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.9p1-3ubuntu0.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matthew, or anyone else affected,
Accepted openssh into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu8.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
- * User of openssh reported an issue that affects Lunar and Jammy.
+ User of openssh reported an issue that affects Lunar and Jammy.
- * This crash is caused by the wrong pointer manipulation in the if
- statement. The fix is to change the code to check
3.1.3-8ubuntu0.7 was just uploaded to focal unapproved with the
documentation additions and an appropriate .changes file:
Changes:
rsync (3.1.3-8ubuntu0.7) focal; urgency=medium
.
* d/p/add-trust-sender-option-docs.patch: Add manpage and help documentation
for the --trust-sender option
I'm a bit reluctant to release this because the update is not
documenting the new option, and I can't find out why. The original MP[1]
review implies that documentation was present, both in -h output, and in
the manpage, but I don't see it in the package in proposed. This makes
it very hard for
** Merge proposal linked:
https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/447986
--
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/2028935
> The livecd-rootfs/2.765.20 regression is not caused by distro-info:
gzip: stdout: No space left on device
I triggered a migation-reference/0 and it failed too, so the error should clear
soon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Apparmor in jammy-proposed has the necessary changes, we just need a new
evince upload to jammy without the recommends then.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
The verification of the Stable Release Update for pcsc-lite has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This is missing a lunar verification before jammy (already verified) can
be released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title:
pcscd.socket is
Kinetic is EOL.
** Changed in: pcsc-lite (Ubuntu Kinetic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title:
7.8.git20221117.28daf24+dfsg-3ubuntu1. Marking fix released.
** Changed in: heimdal (Ubuntu)
Status: New => Fix Released
** Changed in: heimdal (Ubuntu)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of
7.8.git20221117.28daf24+dfsg-3 was already merged, nothing new for now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2018074
Title:
Merge heimdal from Debian unstable
Public bug reported:
The gnutls library has an optional configuration file in
/etc/gnutls/config. This file is not shipped by the Ubuntu packaging,
but it can be created by an user wanting to configure certain aspects of
gnutls.
When the file exists, gnutls functions might trigger an access to
I'm seeing something that looks just like this in a dep8 mantic test
run, where openssh-server is upgraded while preparing the testbed and
postinst fails[1]:
977s Preparing to unpack .../openssh-sftp-server_1%3a9.3p1-1ubuntu1_amd64.deb
...
977s Unpacking openssh-sftp-server (1:9.3p1-1ubuntu1)
The verification of the Stable Release Update for cloud-init has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Till, could you please clarify if kinetic and lunar are fixed?
It seems only cups 2.4.3[1] fixed the issue, and kinetic and lunar have
2.4.2. I checked the code in the packages with patches applied and I
don't see the fix there (in kinetic and lunar).
1.
The verification of the Stable Release Update for dput has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
An upload of elfutils to jammy-proposed has been rejected from the
upload queue for the following reason: "Requested by sergiodj on IRC and
"in person" in a google meet.".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hello wieczyk, or anyone else affected,
Accepted dput into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dput/1.0.3ubuntu1.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Looks like we get this if evince is update, apparmor is not, and a link
in a pdf is clicked:
Jul 06 18:36:59 j-evince kernel: audit: type=1400
audit(1688668619.304:78): apparmor="DENIED" operation="exec"
info="profile transition not found" error=-13 profile="/usr/bin/evince"
name="/usr/bin/snap"
> Do we need evince to be reuploaded for jammy there since the previous
upload was rejected by Steve?
I'm trying to see what type of error we get if we load a profile with
such a rule and the target profile does not exist:
/{,snap/core/[0-9]*/,snap/snapd/[0-9]*/}usr/bin/snap mrCx ->
The verification of the Stable Release Update for apparmor has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Hello wieczyk, or anyone else affected,
Accepted dput into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dput/1.1.0ubuntu2.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello wieczyk, or anyone else affected,
Accepted dput into kinetic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dput/1.1.2ubuntu2.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello wieczyk, or anyone else affected,
Accepted dput into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dput/1.1.3ubuntu2.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
So far, we have these implementations:
(a) python-debian and dput other than the lunar one (seems the more
robust implementation?):
1.2.3ubuntu4~ppa1 -> 1.2.3+ubuntu4.ppa1
(b) lunar's dput:
1.2.3ubuntu4~ppa1 -> 1.2.3.post4~ppa1
(c) distro-info:
1.2.3ubuntu4~ppa1 -> 1.2.3+ubuntu4~ppa1
How
The change in lunar also produces different version strings, could this
become a problem for someone release upgrading through lunar?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
For the dput upload: kinetic, jammy and focal have the same change as
the current devel release (mantic), but not the same one as in lunar. Do
you plan to adapt the lunar change as well? The mantic change (adopted
in f, j, k) explicitly calls out SRUs:
dput (1.1.3ubuntu3) mantic; urgency=medium
Hello Robert, or anyone else affected,
Accepted cloud-init into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2.1-0ubuntu0~20.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Robert, or anyone else affected,
Accepted cloud-init into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2.1-0ubuntu0~22.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Robert, or anyone else affected,
Accepted cloud-init into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2.1-0ubuntu0~22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Sorry, I'm having a hard time understanding how the dput check shows
that distro-info and python-debian are fixed. I'm guessing dput ends up
importing the other two?
Shouldn't python-debian be a block-proposed-kinetic update, since it's
currently unaffected due to its version being still fine
I triggered a migration-reference/0 run for devscripts. If I understood
it correctly, it will also fail, and that will clear the autopkgtests
for python-debian.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in
Thanks for the verification. This looks good to release, except due to a
current breakage in jammy's DEP8 reporting[1], I can't easily verify if
the autopkgtests are green. I can check the test from initramfs-tools[2]
itself pretty easily, but not the DEP8 results of the other tests
triggered by
evince and apparmor for lunar should be released together to fix this
bug, but there is still a DEP8 failure that needs clearing under
apparmor: libreoffice/armhf
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/lunar/update_excuses.html#apparmor
It was retried a few times already, but
What's up with the lunar task that is still open? Lunar didn't have a
mesa update yet, so it can't have regressed. I understand if we want to
avoid future regressions in lunar too, of course, but the fix ("set
VERSION so that it also includes the packaging version") should be
bundled together with
Public bug reported:
Some of the cyrus-sasl2 dep8 tests have never passed on ppc64el or
s390x.
s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/s390x/c/cyrus-sasl2/20230606_065455_398c1@/log.gz
saslauthdFAIL non-zero exit status 253
shared-secret-mechs FAIL
This was fixed in debian and synced to ubuntu in
https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg1-1.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I have a fix for this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2021505
Title:
Flaky DEP8 test: saslauthd
Status in cyrus-sasl2 package in Ubuntu:
In
** Changed in: cyrus-sasl2 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
It looks like the saslauthd test is a bit flaky, and more so in
platforms like arm64[1]:
autopkgtest [15:14:52]: test saslauthd: [---
Setting up saslauthd with mecanism sasldb
Authentication of user user1887 with correct password should succeed... FAIL
The verification of the Stable Release Update for curl has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I just checked and a rebuild of the test app is not necessary, which is
good, otherwise we would have to chase down anything in the archive that
linked with the libcurl3-nss library package and rebuild those.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
iptables in excuses triggers tests in other packages. The excuses report
doesn't show the fully green results anymore, so it's easy to miss them.
I think we can consider the ufw dep8 tests as sufficient for the case of
"normal iptables usage hasn't regressed".
I ran the ufw
I'll check the current status
--
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/1979879
Title:
Apparmor profile in 22.04 jammy - fails to start when printing enabled
These new DEP8 failures are now also cleared.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1992454
Title:
iptables: segfault when renaming a chain
Status in iptables
This is still needing a kinetic verification.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in
The verification of the Stable Release Update for evolution-data-server
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
101 - 200 of 1175 matches
Mail list logo
