The verification of the Stable Release Update for unity 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 don't see how your updated "Where problems could occur" addresses my
comment 22 at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946096
Title:
Support manual firmware upgrading for Foxconn
Mailing list thread here: https://lists.ubuntu.com/archives/ubuntu-
release/2021-October/005278.html
This SRU is blocked until a decision is made.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This SRU upload is missing SRU information. Please follow
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. Thanks!
** Changed in: mesa (Ubuntu Focal)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for filing this! I've just got to triaging it today, but looks
like Gianfranco also noticed this potential sync a few hours ago and has
synced it already, so I'm marking this bug Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It looks like the fix for this in Focal landed together with the
security update in 2.4.7-1ubuntu2.20.04.2 (2.4.7-1ubuntu2.20.04.1
doesn't look like it ever got copied to focal-updates). I confirmed the
patch is still present in the current version in Focal
(2.4.7-1ubuntu2.20.04.3).
** Changed
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
Specifically it looks like you have a misconfigured /etc/mysql/my.cnf.
If
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu. Specifically it looks like you have manually deleted parts of
your openssh installation, so therefore this package can be expected to
be broken.
You can find pointers to get help for this sort
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949287
Title:
Sync blinker 1.4+dfsg1-0.4 (main) from Debian unstable (main)
To manage notifications about this bug go to:
> Where problems could occur
I think another area where things could go wrong is in regressing
clients that use older protocol versions that are currently working.
Could you add something to the Test Plan to do a smoke test in this area
please? I'm not sure how to do this comprehensively, but at
Hello Michael, or anyone else affected,
Accepted pure-ftpd into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/pure-
ftpd/1.0.46-1ubuntu18.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
OK, so you currently have nothing in your Test Plan to verify this part
of the changes you're proposing? Please either fix the Test Plan, or if
testing this is impractical for some reason then we can discuss that and
decide what mitigation might be appropriate, but in this case the
omission and
Hello Jorge, or anyone else affected,
Accepted corosync into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/corosync/2.4.3-0ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I'm stealing this to work on with Lena.
** Changed in: python-django (Ubuntu)
Assignee: Athos Ribeiro (athos-ribeiro) => Lena Voytek (lvoytek)
** Changed in: python-django (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1949465 ***
https://bugs.launchpad.net/bugs/1949465
I'm following the requestsync workflow with Miriam as an exercise for
this task, which involved deliberately filing a duplicate bug for the
sake of this exercise on my request. So I'm marking this bug as a
and Debian testing
-- Otto Kekäläinen Sat, 05 Dec 2020 18:35:44 +0200
mysql-defaults (1.0.5ubuntu1) eoan; urgency=medium
* Bump MySQL to 8.0.
-- Robie Basak Mon, 12 Aug 2019 02:29:20
+0100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks Miriam!
I have verified with Miriam that the built debs are identical against
the debs currently in Jammy (both the set of debs produced and their
content), apart from the version number. So this is good to sync.
Thanks also to Andreas Beckmann in Debian for incorporating the Ubuntu
delta
Ubuntu focuses on netplan with systemd-networkd or Network Manager, and
ifupdown isn't really supported any more except for edge cases not
supported by netplan. Since vlan is supported by netplan, I'm therefore
marking this Won't Fix for the Ubuntu development release.
Note that ifupdown in
We're catching up on old bugs. I see that this one is marked Invalid for
MAAS, but I don't see any steps to reproduce specifically for tgt on its
own. Does anyone know if this bug still exists in tgt in Jammy, and if
so, please could you provide steps to reproduce?
Marking Incomplete as it looks
We've seen this pattern being requested in many packages: normally a
network service dependency isn't needed because a service by default
doesn't bind to a specific address. If a user configures a service to
bind on a specific address, then often they also need to add the network
dependency
It looks like the current behaviour is by design: you won't get any
notification by default if you just install smartmontools unless you
also install a working mail system where you will receive emails to
root@ (eg. by following the Suggests metadata). smart-notifier is a
separate package which
Hello Niclas, or anyone else affected,
Accepted clevis into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/clevis/12-1ubuntu2.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Niclas, or anyone else affected,
Accepted clevis into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/clevis/16-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948598
Title:
Can't unlock multiple devices in initramfs
To manage notifications about this bug go to:
Unsubscribing sponsors as I think there is nothing left to sponsor.
** Changed in: clevis (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Dario, or anyone else affected,
Accepted unity into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/unity/7.5.1+20.04.20211026.1-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Dario, or anyone else affected,
Accepted unity into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/unity/7.5.1+21.10.20211026-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Rolf, or anyone else affected,
Accepted squid-deb-proxy into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/squid-deb-
proxy/0.8.14ubuntu0.18.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Rolf, or anyone else affected,
Accepted squid-deb-proxy into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/squid-deb-
proxy/0.8.15ubuntu0.21.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Rolf, or anyone else affected,
Accepted squid-deb-proxy into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/squid-deb-
proxy/0.8.15ubuntu0.20.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Following discussion, I'm adjusting the Bionic package version string
from 0.8.14ubuntu1 to 0.8.14ubuntu0.18.04.1 to avoid any potential
conflict with a future ESM update to this package in Xenial.
** Changed in: squid-deb-proxy (Ubuntu Hirsute)
Status: In Progress => Fix Committed
**
Hello Rolf, or anyone else affected,
Accepted libsignon-glib into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libsignon-
glib/2.1-3ubuntu0.21.04 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
11:45 vorlon: could you take a look at bug 1916250 for me
please? I'm not sure it's right, but nor am I sure it's wrong.
14:29 rbasak: gir1.2-signon-2.0 exists in hirsute and later;
gir1.2-signon-1.0 exists in focal; we support upgrades from the LTS to
either the next LTS, or to the next
Hello Rolf, or anyone else affected,
Accepted libsignon-glib into impish-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/libsignon-
glib/2.1-3ubuntu0.21.10 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
The fix for this has been uploaded to jammy-proposed.
** Changed in: unity (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904337
Title:
Desktop
> Please reupload from Ubuntu
Specifically regenerate the changes file on Ubuntu I mean. Just re-dput
won't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948598
Title:
Can't unlock multiple
The uploads are missing Launchpad-Bugs-Fixed headers in the changes
files, which breaks our SRU workflow tooling. Please reupload from
Ubuntu (or set the vendor to Ubuntu on Debian, etc).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The livecd-rootfs SRU for Bionic, Focal and Hirsute is currently blocked
by another SRU in progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917920
Title:
magic-proxy broke with iptables
The livecd-rootfs SRU for Bionic, Focal and Hirsute is currently blocked
by another SRU in progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944906
Title:
MagicProxy broken when
How do you intend to verify that (3) has worked correctly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946096
Title:
Support manual firmware upgrading for Foxconn and Quectel modems.
To manage
> 3) Add a bunch of mappings from SIM->Carrier
> Assuming (3) is not expected to change existing behaviour this looks
like it would be acceptable under the hardware-enablement SRU policy.
Agreed, but I would expect SRU information against every change being
made, that would then receive
I'm surprised to see Replaces without a Breaks, and further for the
Replaces to be unversioned. This doesn't match one of the cases listed
at https://wiki.debian.org/PackageTransition, and
https://www.debian.org/doc/debian-policy/ch-relationships.html#id11
explains why usually a Breaks is also
Thanks Dariusz.
Are you intending to fix gnome-shell-extension-desktop-icons in Focal
also then, to restore the behaviour? If so, then shouldn't these be
uploaded together with a Breaks clause to make sure users get both at
the same time?
--
You received this bug notification because you are a
> These patches haven't been applied to upstream ethtool and the API
they are using has not been accepted in upstream Linux yet.
Thank you for flagging this.
It might nevertheless be appropriate to carry patches in Ubuntu in
advance of them landing upstream if there are Ubuntu development teams
An upload of gdebi to impish-proposed has been rejected from the upload
queue for the following reason: "Missing SRU information. This looks
like it wasn't intended for SRU, and the changes are now in Jammy?".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
An upload of gdebi to impish-proposed has been rejected from the upload
queue for the following reason: "Missing SRU information. This looks
like it wasn't intended for SRU, and the changes are now in Jammy?".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
According to the upstream bug, the change was necessary to work
correctly with the desktop shell extension. Won't reverting the change
risk integration issues with extensions, including the ones we ship by
default? Shouldn't this be detailed in "Where problems could occur", and
mitigation
Hello Peter, or anyone else affected,
Accepted gnome-shell-extension-desktop-icons into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/20.04.0-3~ubuntu20.04.4 in a few hours, and then in the -proposed
There's also an upload for Focal in the queue, but this bug is missing
SRU information. If you intend to complete that then please let us know.
Otherwise we'll reject the upload from the queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
There's an upload for Focal in the queue, but this bug is missing SRU
information. If you intend to complete that then please let us know.
Otherwise we'll reject the upload from the queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
SRU review
I don't see any explanation of what this is fixing, or why this is
needed, so cannot review if the proposed changes qualify for an SRU
under Ubuntu's policies.
Specifically I need an explanation of actual user impact, not just "fix
some problems". Further, note that the procedure says
Hello Jason, or anyone else affected,
Accepted livecd-rootfs into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.525.56 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Unsubscribing sponsors since there's no action to take unless my
question above is answered. Once done, please resubscribe ~ubuntu-
sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472288
** Tags added: network-online-ordering
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814193
Title:
systemd unit starts too soon - conflicts with openvpn
To manage notifications about this bug go
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733388
Title:
py.test-3 test discovery hangs when importing
This problem still exists.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1199751
Title:
[check-mir] does not use -proposed
This upload seems to drop a Breaks but this isn't mentioned anywhere. Is
this intentional?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677684
Title:
/usr/bin/corosync-blackbox: 34:
Using an alternate init system isn't supported on Ubuntu. We support
systemd only. Therefore I'm not sure this bug qualifies for an SRU.
Is there any case where a user using systemd would be affected by this
bug?
Given the triviality of the fix, maybe we can accept it anyway given
it's already
Hello Steve, or anyone else affected,
Accepted dnsmasq into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dnsmasq/2.79-1ubuntu0.5 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 nova into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nova/2:17.0.13-0ubuntu4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
It looks like the patch being applied here is applied in Ubuntu Impish,
so would "Fix Released" for the Ubuntu development release task be more
accurate? Either way, this looks good from an SRU perspective, so
accepting - thanks.
** Changed in: nova (Ubuntu Bionic)
Status: Triaged => Fix
Hello Matthias, or anyone else affected,
Accepted augeas into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/augeas/1.10.1-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Larry, or anyone else affected,
Accepted augeas into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/augeas/1.10.1-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I can reproduce this issue with this snap:
installed: 93.0-1 (631) 157MB -
In my case, it's standby/resume that triggers it. However Ctrl+Alt+F3
then Ctrl+Alt+F2 does also. I suggest that the broken standby/resume use
case makes this issue much more significant from a
** Tags added: bionic-openssl-1.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798367
Title:
[SRU] nodejs should use openssl1.0 in testing as well
To manage notifications about this bug go to:
Thank you for looking after this package in Ubuntu!
On Sun, Oct 10, 2021 at 01:57:45PM -, Nicholas Guriev wrote:
> In the next few weeks, Telegram will migrate from 32-bit user
> identifiers to 64-bit ones. Version 3.1 is the minimal that supports
> UIDs over 2 ³¹ - 1. Older version may stop
Hello Christian, or anyone else affected,
Accepted qemu into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg-1ubuntu7.38 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Christian, or anyone else affected,
Accepted qemu into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.18
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Christian, or anyone else affected,
Accepted qemu into hirsute-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/qemu/1:5.2+dfsg-9ubuntu3.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Christian, or anyone else affected,
Accepted qemu into hirsute-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/qemu/1:5.2+dfsg-9ubuntu3.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
> I'll monitor the "-backports" discussion and let's see from there.
Looks like the backports pocket will be available again. I added bionic-
backports so that this request can be found from that end, since it
looks like backports was something being considered. I don't intend to
imply any
** Merge proposal linked:
https://code.launchpad.net/~orndorffgrant/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/409097
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It might also be worth fixing debconf to reject any password that MySQL
will reject. But that can only be done if upstream have clear
documentation so that the debconf script can accurately predict that, so
this needs Sergio's point above addressed first before any progress can
be made in
The SRU team discussed this between themselves on 9 September. We don't
think that "new features" are appropriate in telegram-desktop in stable
Ubuntu releases, and so this is not sufficient justification for an SRU
in itself. Users generally don't expect new features to appear in stable
Ubuntu
Unsubscribing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929790
Title:
Request to backport fix for endianness issue in TigerVNC vncviewer
To manage notifications about this bug go
Hello bugproxy, or anyone else affected,
Accepted tigervnc into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/tigervnc/1.11.0+dfsg-2ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Please can you explain why you're backporting rather than cherry-picking
specific fixes here? If the diff is otherwise equivalent, why aren't you
still intending to individually verify the specific fixes you need, as
would be normal SRU process?
If you don't intend to verify each fix
Hello Artur, or anyone else affected,
Accepted blueman into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/blueman/2.1.2-1ubuntu0.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Michał, or anyone else affected,
Accepted pyroute2 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pyroute2/0.4.21-0.1ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thank you Seth for raising this.
For clarity on the current status of this, the decision-making part of
what is appropriate to do in Ubuntu here has been delegated by the
Technical Board to the Ubuntu Security Team:
https://irclogs.ubuntu.com/2021/09/14/%23ubuntu-meeting.html#t19:17
--
You
things
because I am not processing SRUs this week.
** Changed in: openssl (Ubuntu Focal)
Assignee: Robie Basak (racb) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940656
Ti
One thought. From a quick test, it looks like I can mount a directory
tmpfs over and over again, building up the list of mounts. So if there's
some other reason the script can't execute in /run/qemu, every time the
postinst runs, we'd mount over it again. So maybe we should additionally
not mount
I discussed this in realtime with Christian earlier, from an SRU review
perspective.
My opinion on what we should do follows. I'd like to be clear though
that this isn't necessarily a final decision. If there's a flaw in this
plan, please point it out so that we can reconsider. And if there are
SRU review
I don't see any explanation anywhere of what exactly is wrong in
readline in Bionic or how it is being fixed. Normally I would expect to
see such an explanation in both the SRU template and in the upstream
patch description that is being cherry-picked. But in this case neither
are
Shouldn't these go into the security pocket? At the least I'd like an
explicit nak from the security team please.
** Changed in: openssl (Ubuntu Focal)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
An upload of curl to focal-proposed has been rejected from the upload
queue for the following reason: "Quilt patch missing in series file".
** Changed in: curl (Ubuntu Focal)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ah, sorry. I saw "disable-regex" and thought that was a description of
the resolution to the failing stack-overflow test!
If updating grep to 3.7 is the easiest way to fix the problem then we
can consider that. But since we're in Feature Freeze for Impish, this
needs an assessment for feature
Thank you for working on getting this pulled into Debian!
What's your plan for Ubuntu? Are you holding on to see if Debian uploads
soon so that Ubuntu can sync it? Or do you want your fix uploaded into
Ubuntu ahead of Debian, pending it being fixed in Debian?
I would normally expect the latter
** Changed in: youtube-dl (Ubuntu Bionic)
Status: New => Triaged
** Changed in: youtube-dl (Ubuntu Focal)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529647
Note that if a volunteer chooses to update to something higher than
2021.04.07 to resolve this bug, then Hirsute is also required to be
updated to avoid users regressing when upgrading up to it. In this case,
the Hirsute task should be reopened.
--
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On behalf of the Ubuntu SRU team, please consider this request approved
in principle. Specifically, our policy already allows for youtube-dl
updates in stable releases as required in order to keep it working. See
Upstream bug: https://github.com/liske/needrestart/issues/129
Upstream PR (wontfix): https://github.com/liske/needrestart/pull/168
Cherry-picked by xnox in 3.5-4ubuntu2:
https://git.launchpad.net/~usd-import-team/ubuntu/+source/needrestart/commit/?id=66c0350190f01ee471cf0f74ed07686fd3df196d
**
Your suggestion will work for the noninteractive case but not for any
other case where debconf is being adjusted - for example when requesting
critical prompts only and that kind of thing.
I wonder if it's possible to use debconf itself for the prompt so that
it will automatically comply with
SRU +1 for the current upload in Focal unapproved also, but this is
currently blocked on the 20.04.3 freeze.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940629
Title:
Support Jasper Lake
To
Unsubscribing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940629
Title:
Support Jasper Lake
To manage notifications about this bug go to:
Hello Andy, or anyone else affected,
Accepted thermald into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/thermald/2.4.3-1ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Junien, or anyone else affected,
Accepted update-notifier into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.192.1.12 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Ah. This is already fixed in 5.1.7-1ubuntu1 but the FTBFS report isn't
updated.
** Changed in: autofs (Ubuntu)
Status: Triaged => Invalid
** Changed in: autofs (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
From https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#ubuntu-server, all architectures:
https://launchpadlibrarian.net/552670698/buildlog_ubuntu-impish-
amd64.autofs_5.1.7-1build1_BUILDING.txt.gz
> automount.c:84:37: error:
401 - 500 of 12207 matches
Mail list logo
