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
It's not clear to me if a simple "ssh -Snone localhost" is covered by
the autopkgtests, so I did that manually, testing without -proposed
first, and ensuring to run "sudo systemctl restart ssh" after upgrading
to -proposed to ensure that I'm definitely hitting the daemon from
-proposed.
Success
** Tags added: reboot-required
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
Status in
** Tags added: reboot-required
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/2017401
Title:
Unexpected / unwanted unattended-upgrades behaviour after kernel
** Tags added: regression-update
--
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/2055776
Title:
After updating ubuntu, the network to which the subnet address is
This sounds like exactly the behaviour that I explained in 2013 here:
https://askubuntu.com/a/332421/7808
ifconfig still exists but is deprecated and no longer shipped by
default. Users should use its replacement "ip" instead.
However it is true that ifconfig does not display the additional
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
I'm flagging this as Critical. It sounds like everyone agrees that the
distro patch we're carrying is bad. I think it's possible that it's bad
in quite a serious way, so we should investigate immediately without
delay until we've understood the severity of this, especially because by
carrying the
Hello Mekaniserad, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mekaniserad, or anyone else affected,
Accepted apt into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Andy, or anyone else affected,
Accepted apt into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Andy, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I'm retrying these failing autopkgtests with migration-reference/0 since
if they fail anyway they shouldn't hold things up.
In the meantime, could you please also verify that behaviour on 4K page
size hasn't regressed? It looks like this was implied in the Test Plan
but hasn't been verified.
The verification of the Stable Release Update for dnsmasq 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 dnsmasq 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
Thank you for preparing the SRU and for testing!
The Test Plan agreed in the bug description included two cases but it
looks like you only did the first one? Given that a different SRU team
member did the review and agreed the fully stated plan, I don't feel
that I'm in a position to then release
"Where problems could occur" says "...in [Other Info] section I included
some query examples for well-known domains, so we can be more confident
with this change", but I don't see these carried out as part of the SRU
verification.
Admittedly they weren't documented as part of the Test Plan, but
Thank you for the clarification! I'll remove the regression-update tag
then, since this is the intended behaviour of the security update, so it
shouldn't count towards regression statistics.
** Tags removed: regression-update
--
You received this bug notification because you are a member of
Hello Steve, or anyone else affected,
Accepted ubuntu-settings into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ubuntu-
settings/23.10.5.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
> It is unlikely but possible that the removal of the raspi binary
package from this source package will have inadvertently modified the
contents of the other remaining binary packages.
It might be worth running a binary debdiff for SRU verification then,
against the binary packages built in
** Also affects: base-passwd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058500
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
I don't have time to provide a fully researched answer, but I hope this
will help.
If you're not already familiar, I suggest you start at
https://www.debian.org/doc/debian-policy/ch-opersys.html#users-and-
groups. Ubuntu cannot allocate these without potential future collision
with Debian. So you
Looks like this is a reported regression in the security pocket.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Reopening because a PIN of is not reported to work (and even if it
did, that would still be a regression in a stable release).
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: bluez (Ubuntu)
Importance: Undecided => Critical
--
You received this bug
Further to a conversation in #ubuntu-devel I'm setting the Lunar task to
Won't Fix. Further details:
https://irclogs.ubuntu.com/2023/11/15/%23ubuntu-devel.html
** Changed in: e2fsprogs (Ubuntu Lunar)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a
Also, given that this is the second time this kind of thing has
happened, perhaps it is appropriate to add a dep8 test to ensure that
the compatibility "level" of the default has not regressed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
(in the development release)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2025339
Title:
FDE image fails to run e2fsck
Status in e2fsprogs package in Ubuntu:
Fix
> So if we disable this by default, I think it should only impact
performances of generated filesystems and probably not break anything
else.
This sounds like it could be insignificant, or a major performance
regression in some use cases. It's not clear which. Presumably
orphan_file was
Hello Nathan, or anyone else affected,
Accepted software-properties into xenial-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/software-properties/0.96.20.11 in a
few hours, and then in the -proposed repository.
Please help us by testing this new
Note related bug 2029089 that needs releasing at the same time.
--
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 Xenial
OK, thanks all!
In that case, Aleksandr (or someone) please could you start by preparing
a debdiff for noble to fix the issue there and add an appropriate
autopkgtest as Stéphane recommends? While noble isn't open the SRU isn't
strictly blocked on this, but we should at least have the upload
Sorry, I just hit send on a reply by accident on a reply before I was
ready - I intended to postpone it instead. I need to go now but I will
get back to this later and fix my reply.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
On Mon, Oct 23, 2023 at 04:27:16PM -, Aleksandr Mikhalitsyn wrote:
> >Has this been fixed in the development release, and if so, how?
>
> LXC_DEVEL is 1 in the development release:
> https://github.com/lxc/lxc/blob/main/meson.build#L36
>
> But LXC_DEVEL is 0 in *any* stable tag:
>
Thank you for working on this.
Has this been fixed in the development release, and if so, how?
It's not clear to me that making this change is the appropriate thing to
do in an SRU. How is LXC_DEVEL used in practice? Have you analysed known
reverse dependencies to understand the impact of making
Could we have a justification for why this is important for SRU, please?
As written, the Impact statement describes a bug, but doesn't present
any explanation of why it is important for Ubuntu to fix it in its
stable releases. If it is just that the output might be wrong and we'd
like it to be
(unsubscribing ~ubuntu-sponsors as given my previous comment there is
now nothing remaining to sponsor)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2035061
Title:
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Ye, or anyone else affected,
Accepted rsync into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/rsync/3.1.3-8ubuntu0.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: bridge-utils (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2018060
Title:
Merge bridge-utils from
** Changed in: libmnl (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/2018079
Title:
Merge libmnl from Debian unstable for
** Changed in: libseccomp (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/2018081
Title:
Merge libseccomp from Debian
Public bug reported:
tests/integration/test_packaging_apt_dpkg.py::test_get_file_package_diversion
fails if it doesn't detect any dpkg diversions. Apparently something
(possibly dash?) stopped diverting something, so now there are no
diversions in the autopkgtest environment and therefore this
Public bug reported:
Rebuilding apport in mantic today FTBFS because of a pylint complaint.
We discussed this in #ubuntu-devel today. I don't think that failing the
build on a lint failure is appropriate in distribution packaging in a
production build since otherwise the build regresses for no
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/2017401
Title:
Unexpected / unwanted unattended-upgrades behaviour after
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
Miriam, if you could preserve the state of the system please if you
still have it for debugging, then that would be helpful.
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/2028170
Title:
curl 7.81.0-1ubuntu1.11 fails verifying proper ssl cert w/ subj-alt-
name
> Users have talked about upgrading via the command line to 22.10, but I
figured that Lunar was about to EOL
You mean Kinetic? Lunar has a while left to go. Does that mean that
users can upgrade from 22.04 to 23.04 still?
--
You received this bug notification because you are a member of Ubuntu
It doesn't look like this is fixed in the current stable release (Lunar)
and I don't see an SRU upload for this either. What are your plans for
Lunar? Please see:
https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases
If Lunar isn't relevant for WSL and therefore nobody could hit the bug
I discussed this with Sergio elsewhere and we concluded that we don't
want to change behaviour in Jammy to opt users in to start automatically
reaching debuginfod.ubuntu.com without further discussion. So for this
bug, we'll consider the issue to be simply that if the user configures a
server in
> This results in DEBUGINFOD_URLS not being set for non-root users.
Should the Test Plan not then check that DEBUGINFOD_URLS is actually set
correctly, and that debuginfod functionality actually works?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I was about to ask *why* Ubuntu users need this change before I read
Steve's comment. It might be helpful to expand on that, because without
a full explanation, we (SRU team) are only really _speculating_ on the
actual user impact.
--
You received this bug notification because you are a member
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
The verification of the Stable Release Update for systemd 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
What's the status of keepalived in Mantic on this bug?
** Tags added: server-triage-discuss
--
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/1815101
Title:
[master]
This looks good to me, but the process to land this seems a bit
complicated because gdebi seems to be abandoned at its nominated
upstream, and has a slew of NMUs. I'm not sure what the etiquette is
here. Utkarsh said he'd take a look in the next few days.
** Changed in: gdebi (Ubuntu)
Thank you for the analysis! This all seem reasonable so we can land
this.
But first I need to get the report clean. I ran fwupd/armhf on Focal
against migration-reference/0 which failed as expected. That should
cause fwupd to no longer flag as a regression when the report is
regenerated (I
This is blocked from release - please see comment 8.
--
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/2012943
Title:
systemd-resolved crashes due to use-after-free bug
The verification of the Stable Release Update for software-properties
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
Normally testing that the bug is fixed would verify that the package
still works, but it isn't clear to me that this is the case for this
(very narrow) test plan.
Has there been any testing done that verifies that iptables still
basically works, please? I looked at the build logs (for Bionic as
** Changed in: tzdata (Ubuntu Lunar)
Status: New => Incomplete
--
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/2017999
Title:
tzdata 2023c-0ubuntu0.22.04.1 might
This upload proposes to remove some of the options in
debian/tzdata.templates. So what happens if a user has configured
deployment automation to use particular debconf options that will now
disappear? The changelog says "It removes following time zones from
debconf and updates them on upgrades
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
Thanks Lena!
--
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/2012298
Title:
PasswordAuthenticaion in sshd_config.d
Status in portable OpenSSH:
Unknown
Status in openssh
The verification of the Stable Release Update for krb5 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
Please could someone verify that with openssh-server 1:8.2p1-4ubuntu0.7
installed in its default configuration, ssh works as expected? If you
could detail the exact steps you performed to verify this and copy and
paste the output of eg. "dpkg -l|grep openssh" so there is no doubt as
to what was
Any chance of a dep8 test for this please? I think it would be valuable
as we're carrying this feature in a distro patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.9.12 in a few hours, and then in the -proposed
repository.
Please help us by testing
> bug added by the previous revision
Tagging regression-update then, FTR, for future regression risk
analysis.
> That fix isn't relevant for releases after Focal; The necessary API
exists for Jammy onwards.
OK thanks. Then the correct bug task status for Jammy onwards is Invalid
or maybe Fix
In the meantime, please could you confirm what [sorry, that's ambiguous;
I mean *how*] you tested?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
glib not
Thanks. I agree and I've added a hint. This should hopefully clear the
flag on the next (Jammy) britney run.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
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
Hello Dariusz, or anyone else affected,
Accepted tzdata into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.18.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
13:51 bdrung: tzdata in Bionic has quite a bit of churn in
debian/tzdata.templates, including the removal of Pacific-New from
tzdata/Zones/US. I didn't see any removals in the later series. Do we
have anything that demonstrates that this is safe? Shouldn't the choice
be preserved somehow?
14:53
I've set the bug statuses to Incomplete for the benefit of future SRU
reviewers; please reset to their correct statuses once you've answered.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
Could you please confirm that this fix isn't relevant for releases after
Focal - ie. that the necessary API exists in Jammy onwards? It may be
that you implied this already, but the bug status isn't set separately
and I can't find anything that states this unambiguously so I want to
make sure it
Hello Dariusz, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.20.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dariusz, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.22.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dariusz, or anyone else affected,
Accepted tzdata into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.22.10.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
FTR, we discussed this further in #ubuntu-release earlier. IMHO, while
there may be a good reason for the changes, they should be described in
SRU bugs so that their impact can be considered by the SRU team, and QA
can be tracked if accepted. I asked for either these changes to be
removed, or a
Review of Kinetic:
This looks much better. Thanks!
> * Test convert_timezone for consistency and fix inconsistencies:
The fixing of inconsistencies are still potential functional changes in
an SRU that need their own justification please. Generally we'll only
make changes that affect real
Is bionic-proposed sufficient (ie. block-proposed-bionic then) or do you
specifically need it in bionic-updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1848587
Title:
Summary: there are too many apparently SRU-inappropriate changes bundled
into this upload; please remove them and supply the minimal necessary
changes only.
Full review:
This bug has had some unavoidable churn in -proposed due to external
factors resulting in multiple releases of tzdata upstream
** Bug watch added: Debian Bug tracker #1033597
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033597
** Also affects: isc-dhcp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033597
Importance: Unknown
Status: Unknown
--
You received this bug notification
I wondered if this needed an FFe, but then I considered that we're
fixing an Apparmor profile to do what the command would allow anyway,
and I think that fixing Apparmor profiles is not something that
generally would violate feature freeze. So I'm not bothering the release
team with this one and
Thank you for your report. I agree.
When I wrote the TOTP/HOTP section in
https://ubuntu.com/server/docs/service-openssh, I wanted to use
sshd_config.d/ but was unable to instruct readers without also changing
sshd_config directly, so I gave up on the former to keep the
instructions simpler.
Since the SRU team -approved Test Plan was to rely on autopkgtest, and
autopkgtests are showing all passed, we can consider this bug verified
for those releases.
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-kinetic
** Tags added:
Since the SRU team -approved Test Plan was to rely on autopkgtest, and
autopkgtests are showing all passed, we can consider this bug verified
for those releases.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done
The verification of the Stable Release Update for python-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
Hello Aurora, or anyone else affected,
Accepted language-selector into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.22.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Aurora, or anyone else affected,
Accepted language-selector into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Thank you for the updates! It looks like you responded appropriately to
all of my points, but I'd like to clarify one thing about version
numbers and Kinetic.
> If a user with an updated jammy (including this fix) upgrades to
kinetic, they will still have version 0.219.1 of the
Thank you for working on this!
What's the plan for Kinetic? Please see:
https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases
If the goal is to make Sinhala text more readable on Ubuntu, please
could you make that an additional part of the Test Plan, instead of only
checking the order of
Hello Julian, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.9 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for cyrus-sasl2 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
The verification of the Stable Release Update for cyrus-sasl2 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
** Tags removed: server-next
** Tags added: server-todo
--
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/2000817
Title:
Wrong SHA256-value computed on kinetic
Status in
Thank you for your report.
I was unable to reproduce this on Ubuntu. Installing libudev-dev
249.11-0ubuntu3.6 seems to work just fine. I tried both an Ubuntu cloud
image in a container, and a fresh desktop image in a VM. Log attached.
Your "Proof that is not Mint's fault" doesn't demonstrate
Thank you for taking the time to file this report and helping to make
Ubuntu better.
I think you're probably affected by this:
https://askubuntu.com/questions/1409105/ubuntu-22-04-ssh-the-rsa-key-
isnt-working-since-upgrading-from-20-04
Since it seems likely to me that this is a local
Thank you for contributing this fix!
This looks fine; just one comment. Upstream adds a test. But it looks to
me like it won't run because the quilt patch can't handle the executable
bit. Looks like there's a workaround in debian/tests/control for another
case of the same issue. Please could you
1 - 100 of 1200 matches
Mail list logo
