Technically, the verification from prior comments was performed on
23.2.1-1ubuntu3.1~22.04.1, not 23.2.1-1ubuntu3.1~22.04.2. I think they
need to be done on the mesa package that is in proposed now, which is
.2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Title:
Backport packages for 22.04.4
> Quick question: is pkcs11.txt a default filename used anywhere else?
Where did the filename come from?
¯\_(ツ)_/¯
There is a lot (a lot) of history here, buried deep somewhere in the
internet...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
The migration-reference/0 runs passed, to the dep8 results are still not
good. I retriggered the failing arm64 tests one more time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.ne
mantic is releseable, but I'll wait for the jammy results until the end
of my shift. If they are still red, I can release just mantic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad
Maybe it's just me, but could we please clarify in the test plan exactly
what flag changes are we expecting? Given the change is to honor or not
the "OPT" flags, I was expecting an additional test plan that would set
those, and then show that they are included when the workaround var is
set. That's
Hello Nafees, or anyone else affected,
Accepted python2.7 into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.18-1~20.04.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
You can add something obvious, like -DMITCHELL_WAS_HERE :)
On Thu, 8 Feb 2024, 18:35 Mitchell Dzurick, <2002...@bugs.launchpad.net>
wrote:
> That's a great idea Andreas! It's a little difficult to pinpoint the
> exact OPT flags as they are bunched up with the other compiler flags, so
> I'll add a
Hello Bryce, or anyone else affected,
Accepted openldap into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openldap/2.5.17+dfsg-0ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
The SRU documentation[1] on tzdata describes other, or additional, tests, to be
performed in this package. Is that:
a) assumed, and will be done?
b) autopkgtests cover it?
c) was forgotten, and should be added to the test plan?
1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata
--
You rece
I'm not familiar with this package, so maybe not the best person to
review this SRU, but here is another question. The SRU docs on tzdata
also mention python3-icu, but I don't see an update for that package
here or in the unapproved queue. Is that necessary? Or is it just about
verifying that pytho
Finally, the SRU doc also says this: "Uploads should also be made to any
releases supported via ESM."
Are you going to drive that as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchp
Hello Benjamin, or anyone else affected,
Accepted tzdata into mantic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.23.10 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Benjamin, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.22.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Benjamin, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.20.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
@security, could you please sign off on this tzdata SRU, according to
the SRU procedure[1] for this package?
1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ub
The 7 day aging period will be hit later today. Releasing it now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2052739
Title:
tzdata 2024a release
Status in tzdata packa
The verification of the Stable Release Update for tzdata 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 r
Public bug reported:
A user reported this regression on
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739:
"""
Hello.
After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to
2024a-0ubuntu0.22.04
the previously set EST time zone was automatically changed to "America/Adak" or
Hi Vladimir,
I'm sorry to hear that. What was the previously timezone that you had
set? Just EST?
I filed https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718
about your report, if you could please amend it with more details.
** Tags added: regression-update
--
You received this bug n
I did a quick test in a jammy VM, and didn't observe this change:
ubuntu@j:~$ date
Fri Mar 1 13:29:18 EST 2024
ubuntu@j:~$ dpkg -l tzdata
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Statu
Left comments in the MP.
** Changed in: console-setup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2054681
Title:
Merge
> d/control is used on the official gtk desktops such as budgie.
Excuse my unfamiliarity with desktop packages, but I don't understand the above
statement. Until someone from desktop reviews this, my question would be very
basic: what is the problem this is trying to solve? What is happening, t
Sponsored for noble.
** Changed in: ppa-purge (Ubuntu Noble)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2036761
Titl
That happens also with the current version of tzdata.
Starting with:
$ dpkg -l tzdata|grep tzdata
ii tzdata 2022a-0ubuntu1 all
$ date
Mon Mar 4 12:22:38 UTC 2024
# the current timezone (UTC) was configured via dpkg-reconfigure tzdata
$ sudo apt reinstall tzdata=2022a-0ubuntu1
Reading
Given
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/comments/5,
I don't think it's a regression in the update. Removing the regression-
update tag.
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
** Changed in: tzdata (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Regression after update: timezone changed unexpectedly
+ timezone changed unexpectedly
** Description changed:
A user reported this regression on
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug
I noticed this SRU was prepared without the SRU Template[1] filled in.
While most of the data we want is in the bug description as is (what's
wrong, test plan), it's lacking an analysis of what could go wrong.
That boat has sailed now, and doing an analysis of the patch right now,
basically what c
The verification of the Stable Release Update for cups 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 reg
I grabbed one of the focal failures from comment #49, mercurial:
focal amd64 mercurial 5.3.1-1ubuntu1 4 python2.7/2.7.18-1~20.04.4
That is indeed mostly red in [1], including the recent run with
python2.7 from this SRU.
And it's not showing up as a failure in the excuses[2] report.
But it's hin
> So that would explain it not being flagged for s390x, but not for amd64. I'm
> still puzzled: I didn't find
> another hint.
Ah, it's because of a migration-reference/0 run from last year:
5.3.1-1ubuntu1 migration-reference/0 None2023-06-20 09:25:36 UTC
0h 37m 11s schopin fail
@m
Taking a look at another focal result from the table in comment 49:
focal amd64 pam-python 1.0.7-1ubuntu1 4 python2.7/2.7.18-1~20.04.4
No hints in the hints-ubuntu repository, focal branch.
But there is a migration-reference/0 run that failed that exact same
version:
1.0.7-1ubuntu1 migration
Checking the jammy amd64 autopkgtest runs[1], we can see that the top
most one is the run for this sru. Its log[2] is showing, at the end, a
good run, but if you look more carefully, there are some test failures
that apparently are being ignored.
In particular:
1910s ==
** Changed in: openssh (Ubuntu)
Status: Incomplete => In Progress
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss pa
Checked and focal-fips and bionic-fips are not affected.
Jammy is, as reported here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/2054609
Title:
package ntp Jammy 1:4.2.8p1
https://src.fedoraproject.org/rpms/openssh/c/c04e468b07b38471377fc7a648e1737021ea7148
--
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/2053146
Title:
openssh 8.9p1 for Jammy
** Also affects: openssh (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Noble)
Importance: Critical
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Also affects: openssh (Ubuntu Mantic)
Importance: Undecided
Prepping builds, and I also want to add an autopkgtest for this.
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for
I have an autopkgtest for gssapi, adding one now for keyex.
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssap
Quick test with
https://launchpad.net/~ahasenack/+archive/ubuntu/openssh-
gsskeyex-2053146/+packages on jammy (but there are builds for other
releases too), seems to work:
Mar 13 20:52:58 j-keyex sshd[1638]: Authorized to ubuntu, krb5 principal
andreas@LOWTECH (krb5_kuserok)
Mar 13 20:52:58 j-key
I think you missed the extra arg to userauth_gsskeyex()
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-ke
The verification of the Stable Release Update for openldap 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
The verification of the Stable Release Update for python2.7 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
Version 0.96.20.10 passed in xenial/amd64 about 10 days ago (via an
ubuntu-advantage-tools update), but version 0.96.20.12 failed a few days
before. I triggered another run just in case.
If that new run also fails, then something is going on, and it has to be
sorted out before this update can be r
Queued where? I don't see it in xenial unapproved. If it's just fixing
the autopkgtests, not the software-properties code or anything else in
debian/*, then no need for a new SRU bug. Just make sure to build it
with the appropriate -v parameter to include all changes since
0.96.20.10 (IIRC).
--
Y
Ah, software-properties, sorry, I still had update-manager in my mind.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2029473
Title:
Backport Ubuntu Pro to Xen
I just looked at the changes, and I would prefer to have a new SRU bug
for those, yes please.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2029473
Title:
Bac
** Description changed:
- The Authmethod struct now have 4 entries but the initialization of the
- method_gsskeyex in the debian/patches/gssapi.patch only have 3 entries.
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the
** Description changed:
[ Impact ]
- * An explanation of the effects of the bug on users and
+ The gssapi-keyex authentication mechanism has been inadvertently broken
+ in openssh. It comes from a distro patch[1], and while the patch still
+ applied, it was no longer correct.
- * justifi
> Andreas Hasenack (ahasenack)
** Changed in: openssh (Ubuntu Mantic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
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.n
Importance: High
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
--
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/2058276
Title:
Improve ssh-
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openssh/+git/openssh/+merge/462619
--
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/2058276
The verification of the Stable Release Update for apt 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 regr
The verification of the Stable Release Update for apt 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 regr
I added an sssd task due to the workaround we had to add to it in
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576 (we don't
install faketime). Should faketime be fixed, then we can revert that
change in sssd.
** Also affects: sssd (Ubuntu)
Importance: Undecided
Status: New
-
** Description changed:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently broken
in openssh. It comes from a distro patch[1], and while the patch still
applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
Jammy verification
In all architectures (except i386, which is a known failure everywhere)
the new ssh-gssapi test passed.
Here is the run on amd64[1]:
3438s autopkgtest [16:33:21]: test ssh-gssapi: [---
3438s ## Setting up test environment
3438s ## Creating Kerberos realm EXA
Mantic verification
In all architectures, except i386, the new test passed.
Here is a log from the amd64 run[1]:
4333s autopkgtest [16:47:27]: test ssh-gssapi: [---
4333s ## Setting up test environment
4333s ## Creating Kerberos realm EXAMPLE.FAKE
4333s Initializing database
Fixing this in noble at this time will require a feature freeze
exception, because we would be changing behavior.
The default for user_readenv in pam_env is 0 (off). In the sshd config,
ubuntu/debian ship a pam config that sets it to on (1), therefore
~/.pam_environment will be read if it exists.
Deprecation warning introduced here: https://github.com/linux-pam/linux-
pam/releases/tag/v1.5.0
Release notes for all releases up to 1.6.1 don't mention this again, so
it's still there: https://github.com/linux-pam/linux-pam/releases
--
You received this bug notification because you are a membe
Commit that added the warning to pam_env.c: https://github.com/linux-
pam/linux-pam/commit/ecd526743a27157c5210b0ce9867c43a2fa27784
--
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/
tance: Undecided
Status: New
** Changed in: openssh (Ubuntu)
Milestone: None => later
** Changed in: pam (Ubuntu)
Status: New => In Progress
** Changed in: pam (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: pam (Ubuntu)
M
New pam package uploaded to noble-proposed. It's in the unapproved
queue.
--
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/2059859
Title:
pam_env(sshd:session): deprecated r
At the moment, noble-proposed has
https://launchpad.net/ubuntu/+source/upower/1.90.3-1, uploaded a few
hours ago:
upower (1.90.3-1) unstable; urgency=medium
* New upstream version 1.90.3
* Drop patches, merged upstream
* Bump Build-Depends on meson to (>= 0.60.0) and libglib2.0-dev to (>= 2
And unsubscribing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060335
Title:
upower/1.90.2-8build3 autopkgtest failure on arm64
Status in upower package in Ub
https://launchpad.net/ubuntu/+source/cups/2.4.7-1.2ubuntu6 is in noble-
proposed claiming to fix this bug.
Comment #6 above says there is a missing patch still.
In any case, doesn't look like there is anything to sponsor here, so
unsubscribing ubuntu-sponsors.
--
You received this bug notifica
I'm surprised this wasn't caught by the DEP8 tests. Care to also perhaps
add a simple smoke test, like (note it's not using ssh or any network):
$ rsync -F --delete-after --archive /etc/os-release /tmp/
*** buffer overflow detected ***: terminated
rsync: connection unexpectedly closed (34 bytes re
Public bug reported:
pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there
in the code, but not built by default.
And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2)
does.
This does not prevent console logins, but generates an error in the logs:
Apr 23 20:02:09
Ryan, I think you are experiencing
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197 which
is a regression on focal from a previous update that also tried to
address the version negotiation. There is a new nfs-utils package in
focal-proposed to address that, would you mind trying it
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Status: Fix Released => Confirmed
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you ar
Ok, specifically this log message is fixed in 2.1.28:
DIGEST-MD5 common mech free
Via https://git.launchpad.net/ubuntu/+source/cyrus-
sasl2/tree/debian/patches/0001-plugins-digestmd5-Remove-debug-log-mech-
free.patch
That patch is just in Ubuntu Kinetic for now.
But I still see a lot of DIG
I applied that patch in cyrus-sasl2 2.1.28 from kinetic, and it did get
rid of the other DIGEST-MD5 messages. But I'm having difficulties in
finding a client sasl app where I can set log_level to see if with a
high log_level I can restore that logging, to make sure it's working.
I tried ldapwhoami
Got a reply[1] from upstream, and this is expected.
I'll go ahead and MP this patch.
1. https://github.com/cyrusimap/cyrus-
sasl/commit/cb549ef71c5bb646fe583697ebdcaba93267a237#r74534186
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Status: Confirmed => Triaged
** Changed in: cyrus-sasl2 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You
Public bug reported:
Openldap has an extensive test suite that is run during build. The
sasl/gssapi tests are being skipped because of missing build
dependencies:
> Starting test077-sasl-gssapi for mdb...
running defines.sh
Starting KDC for SASL/GSSAPI tests...
Trying Heimdal
Public bug reported:
The cyrus-sasl2 package in Ubuntu is still lacking the channel binding
support in gssapi, which was/is required by a certain patch level of
Windows Active Directory.
I have an old ppa[1] of when I was working on this, before I was moved
to other projects.
The patches I used
Public bug reported:
> Starting test081-totp for mdb...
running defines.sh
../../../tests/scripts/test081-totp: 31: cannot create
/home/ubuntu/git/packages/openldap/openldap/debian/build/tests/testrun/test.out:
Directory nonexistent
../../../tests/scripts/test081-totp: 31: cannot create
/ho
*** This bug is a duplicate of bug 1912256 ***
https://bugs.launchpad.net/bugs/1912256
** This bug has been marked a duplicate of bug 1912256
Missing channel binding prevents authentication to ActiveDirectory
--
You received this bug notification because you are a member of Ubuntu
Touch s
edium
* [92abdd1] New upstream version 2.13.3
-- Michael Jeanson Fri, 03 Jun 2022 16:37:11
-0400
** Affects: ust (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: New
** Tags: needs-merge
** Changed in: ust (Ubuntu)
Assignee: (unass
Related: https://bugs.launchpad.net/ubuntu/+source/crypto-
policies/+bug/1926664
(I might create a task here for crypto-policies and close the bug above)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubun
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: mariadb-10.6 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mariadb-10.6 (Ubuntu Jammy)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: systemd (Ubuntu Jammy)
Status: New => In Progress
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => High
--
You received this bug notification becaus
Hi Michal, I'm going over the test procedure for this bug and turns out
the scenario where we encountered it is a bit convoluted, specially for
users: you need to be running a 5.4 kernel on a jammy userspace (jammy
itself has 5.15 kernel).
Could you please elaborate on how this bug affects you? Ar
I can't reproduce this bug anymore with the package currently in jammy
(1:10.6.7-2ubuntu1):
lxc launch ubuntu:focal f --vm
lxc shell f
lxd init # just hit enter for all questions
lxc launch ubuntu:jammy j
lxc shell j
ulimit -l # confirm it's less than 256
apt update && apt install mariadb-server -
Ok, a plain jammy rebuild in a launchpad ppa failed:
2022-06-17 14:18:27 0 [Warning] mariadbd: io_uring_queue_init() failed
with ENOMEM: try larger memory locked limit, ulimit -l, or
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under
systemd (262144 bytes required)
The binary packa
I got a report on IRC that the existing jammy package of mariadb does
exhibit this problem:
(link will expire soon)
https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_bd5/839585/23/check/kolla-ansible-ubuntu-source/bd5a051/primary/logs/kolla/mariadb/mariad
Ok, phew, my test was incorrect, the bug is present in jammy. That makes
this SRU simpler. I'll proceed with it, without a block-proposed tag.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.lau
** 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.
+
+ [Test Pl
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ Jammy's MariaDB was built with io_uring support, and it tries to enable
+ it at runtime if it deems it's running on a supported kernel. There is a
+ range of kernel versions it checks, but of interes
** Description changed:
[Impact]
Jammy's MariaDB will fail to build, and also fail to start, if the
underlying kernel is 5.4.x (focal's) and if it's running in an
unprivileged container (lxd, docker). It will also fail to build in
launchpad builders.
Common scenarios where this c
** Changed in: systemd (Ubuntu Jammy)
Status: In Progress => New
** Changed in: systemd (Ubuntu Jammy)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
** Changed in: mariadb-10.6 (Ubuntu Jammy)
Status: Triaged => In Progress
** Description changed:
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=3203
Importance: Unknown
Status: Unknown
--
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
Toby, you are mostly interested in this because you have some sort of
policy, perhaps one that doesn't allow secrets to be stored on disk in
clear text and protected just by filesystem permissions?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
** Changed in: ust (Ubuntu)
Milestone: None => ubuntu-22.07
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
https://bugs.launchpad.net/bugs/1977751
Title:
Merge ust from Debian for 22.10
Status in ust pa
Here is a collection of guides from upstream MIT kerberos:
https://web.mit.edu/kerberos/krb5-latest/doc/admin/enctypes.html#migrating-
away-from-older-encryption-types
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in U
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1912256
Title:
Missing channel binding prevents
I have a build for kinetic which has two changes:
- enable channel binding
- allow setting maxssf=0 when using GSS-SPNEGO
The later might not be needed, as GSSAPI already supports maxssf=0, and
adcli will forcibly select GSSAPI instead of GSS-SPNEGO if ldaps (ssl)
is being used, exactly because no
Ok, the -o SASL_CBINDING command-line parameter seems to work. Against
that window 2016 server the ldapwhoami command only works when I set the
channel binding mode to tls-unique:
ubuntu@k1:~$ ldapwhoami -H ldaps://WIN-KRIET1E5ELO.internal.example.fake -Y
GSSAPI -O maxssf=0 -o SASL_CBINDING=none
I'm concerned about interoperability issues...
https://github.com/cyrusimap/cyrus-imapd/issues/3317
** Bug watch added: github.com/cyrusimap/cyrus-imapd/issues #3317
https://github.com/cyrusimap/cyrus-imapd/issues/3317
--
You received this bug notification because you are a member of Ubuntu
This was fixed in debian and is currently in kinetic-proposed:
https://launchpad.net/ubuntu/+source/krb5/1.20-1
I'm unsure how to approach this from an SRU perspective, given it's a
configuration setting in the default config file that is ship:
--- a/debian/kdc.conf
+++ b/debian/kdc.conf
@@ -10,
1 - 100 of 1630 matches
Mail list logo
