The net is full of suggestions e.g.
https://unix.stackexchange.com/questions/26676/how-to-check-if-a-shell-is-login-interactive-batch
With that:
[[ $- == *i* ]] && echo 'Interactive' || echo 'Not interactive' >>
/tmp/update-motd-test
shopt -q login_shell && echo 'Login shell' || echo 'Not
I found this bug while searching for cases forgotten for too long - sorry to
all of you.
And after reading into the case I feel even worse that it was forgotten so long
:-/
I know it is just a config file and one could just remove some of the
/etc/update-motd.d files to adapt. Also pam config
I must re-state that agree one might expect (I did) that on non-interactive
shells these motd content would not execute at all.
... but it does ... why?
Nowadays this is all from libpam which has pam_mount (man page) and is
enabled by default here:
root@j:~# grep -Hrn motd /etc/pam*
Slow operations are recommended in motd to use caching and here I think
this should be done as well.
Just like other operations using slow calls or network they should cache
it and only run every few seconds. That will already cut down any
mistaken "run on non-interactive" by an order of
Hi,
the new issue you found is known and being worked on here:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1964923
For what is left here about the off profile-rc.d it seems you no more can
reproduce it.
If you happen to see/reproduce it again continue to help us solving the
FYI - This also seems to affect all Ubuntu Desktop installs on VMware
where we got a few reports. I'll redirect people here ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964923
Title:
*** This bug is a duplicate of bug 1964923 ***
https://bugs.launchpad.net/bugs/1964923
This is already discussed in bug 1964923 and seems to be worked on by
foundations there.
Marking this one as a duplicate.
** This bug has been marked a duplicate of bug 1964923
list-oem-metapackages
NG.txt.gz
** Changed in: ldns (Ubuntu Impish)
Status: Confirmed => In Progress
** Changed in: ldns (Ubuntu Impish)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Description changed:
[Impact]
- * When ldns is compiled with gcc11 without a fix for
-strict
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962843
Title:
Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to
adding 'shutdown.target' in file
Uploaded to Jammy, once in we can re-check dns-root-data and if all is
fine we can consider if/how/when to SRU this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966237
Title:
ldnsutils emits
Ubuntu Jammy)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966237
Title:
ldnsutils emits wrong sha256 hashes
To manage notifications ab
Build instructions:
git clean -xdf
git checkout .
git submodule update --init
libtoolize -ci
autoreconf -fi
./configure --disable-rpath --with-examples --with-drill --enable-ed25519
--disable-ldns-config --build=x86_64-linux-gnu --prefix=/usr
--includedir=/usr/include --mandir=/usr/share/man
That llvm v14 is rather recent - we were lucky that llvm-13 worked fine.
Officially the most recent postgresql-release just added llvm-12 support [1].
In jammy we have:
llvm-13 | 1:13.0.1-2ubuntu2 | jammy/universe | amd64, arm64, armhf, i386,
ppc64el, riscv64, s390x
llvm-14 |
Thanks a lot Martin!
For the sake of helping your look into this, the old fix in Ubuntu was [1] part
of [2].
The two things one might assume to fail are
a) the conditional checks we didn't have before
b) the switch from usermod to adduser
Let me know what you find and if you need help.
[1]:
Most likely change:
"2020-08-24 Use EVP_sha256 instead of HMAC_Update (for openssl-3.0.0)"
From
https://github.com/NLnetLabs/ldns/commit/12ab6f7a408cd99e9b43b7db86724c2ee66bc36e
That is the latest ssl3 toleration they have upstream (merged in 1.8.0,
no updates in 1.8.1), but it seems something
Subscribed Simon who added the openssl3 delta, he might have more
context from having worked on so many of these changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966237
Title:
ldnsutils
Public bug reported:
Hi,
originally this started by a finding of an FTFBS issue of dns-root-data [1] as
reported in the most recent archive rebuild [2]
But comparing those I've found that it is actually ldns that is broken,
as it seems most likely by openssl3.0 changes.
Separating this from
This is still present in jammy as
debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch
If we want to keep this as long as there could be an 18.04 that is like 2028 at
least.
So AFAIU this bug is actually asking LXD to consider a backport (if
possible) to
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966201
Title:
ruby3.0 probably needs a provides ruby-rexml
To manage notifications about this bug go to:
Public bug reported:
Hi,
the archive rebuild [1] identified a bunch of ruby dependency issues.
The majority seems to be about ruby-rexml.
For example:
https://launchpad.net/ubuntu/+archive/test-rebuild-20220317-jammy/+build/23342118
"Missing build dependencies: ruby-rexml"
This particular
Ok, summarizing the change
Required:
#1 embedded source
=> Done: security said that is ok for them
#2 symbols tracking
=> Done: resolved and improved via bug 1965464
Recommended:
#3 some vague security concerns
=> Done: did not come up in the security review
#4 does not have a test suite that
https://launchpad.net/ubuntu/+source/nftables/1.0.2-1ubuntu2 migrated to
Jammy-release
And in additon the Debian PR was merged.
LGTM, let us focus on what is left in the MIR bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Thomas,
on one hand let me ask a few questions (below) as the report as-is can't really
be acted on.
on the other hand - even then - this is a topic that does not sound like an
Ubuntu specific problem or fix and therefore more likely will be successful if
deiscussed upstream
Backports to Ubuntu releases started for Jammy at
https://github.com/canonical/cloud-init/pull/1350
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966085
Title:
cloud-init status --wait never
** Tags added: server-todo
** Changed in: apache2 (Ubuntu)
Status: New => In Progress
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI the requested security fixes (see above), the apparmor hardening
(bug 1950631) and the update to 0.6.3 to stabilize all just migrated to
jammy-release (=>
https://launchpad.net/ubuntu/+source/swtpm/0.6.3-0ubuntu1).
We should be back to "just" waiting for the security review and
hopefully no
FYI:
new version started to build in Jammy
https://launchpad.net/ubuntu/+source/nftables/1.0.2-1ubuntu2
Updated the Debian bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007888
Provided a matching salsa PR for Debian
Thanks for the feedback, uploaded to Jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965464
Title:
add debian symbols tracking for libnftables1 package
To manage notifications about this bug
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964686
Title:
Command "host non-existent-host-name"
** Tags removed: server-triage-discuss
** 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/1965521
Title:
named.service starts too early: Unable to fetch DNSKEY set
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Steve
After Seth asked me to have a look (see above comments) I tried to help as much
as possible, therefore there now is:
- a MR
https://code.launchpad.net/~paelzer/ubuntu/+source/nftables/+git/nftables/+merge/417523
- PPA https://launchpad.net/~ci-train-ppa-
Applying both changes seems to work fine for me and does not break due to LTO.
I'll polish this for you to consider a follow-on upload ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965464
Title:
Reminder: Please do continue trying to get mini-buildd fixed in a way to
work in Jammy and get it uploaded before release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965973
Title:
Remove
I think this request is reasonable and added a few more details to the
description.
After checking with Doko to be sure I agree and will remove this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing packages from jammy:
mini-buildd 1.1.19 in jammy
mini-buildd 1.1.19 in jammy amd64
mini-buildd 1.1.19 in jammy arm64
mini-buildd 1.1.19 in jammy armhf
mini-buildd 1.1.19 in jammy i386
mini-buildd
** Description changed:
The Django 3.2 transition is currently being blocked in proposed by
mini-buildd because it is severely outdated. mini-buildd's current
version in Jammy is 1.1.19, which is an old experimental version. The
two options to fix this would either be to move it back to
** Description changed:
The Django 3.2 transition is currently being blocked in proposed by
mini-buildd because it is severely outdated. mini-buildd's current
version in Jammy is 1.1.19, which is an old experimental version. The
two options to fix this would either be to move it back to
At the moment you are kind of getting around the "wrong symbols" by not using
the map (missing 1d507ce7f1d) and thereby not using the wrong symbols
(nft_set_optimize/nft_get_optimize).
But that explains (as you already know and said above) why it is all @base.
--
You received this bug
@Steve - don't you also need
http://git.netfilter.org/nftables/commit/?id=e98a9b83cd52c7c75bedb3dad46539b197ed17ba
?
And then an updated symbols file for it?
As well as
http://git.netfilter.org/nftables/commit/?id=1d507ce7f1d3c12481ee24bd1dcac2fc1984ee9f
actually. You said you tried, but what
FYI - Fixup uploaded as part of 0.6.3-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950631
Title:
[FFe] wrap swtpm in an apparmor profile
To manage notifications about this bug go to:
FYI - I got positive feedback for my MR and in general from Foundations,
I'll upload this to Jammy now. This will address bug 1950631, the
security request by sarnold and a general stabilization update. =>
0.6.3-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Got a Team ack on MM, uploading this now ...
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading needrestart_3.5-5ubuntu2.dsc: done.
Uploading needrestart_3.5-5ubuntu2.debian.tar.xz: done.
Uploading needrestart_3.5-5ubuntu2_source.buildinfo: done.
Uploading
** Changed in: gnome-bluetooth3 (Ubuntu)
Assignee: Ioanna Alifieraki (joalif) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964600
Title:
[MIR] gnome-bluetooth3
To manage
Thanks for outlining your steps in detail.
In my former tests I did use "minimal" instead of "normal" and did not yet
purge+install open-vm-tools.
Let me try exactly yours to be closer to your case...
1. I get the ISO from
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-amd64.iso
Re-ping again, this is breaking all (well there aren't too many) 486
compiles.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940029
Title:
Default of fcf-protection should only be enabled where it
Just to state it also here and not just in meetings and calls, this is
urgent and important for Jammy, so as much asap as you can manage to
complete this is appreciated :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It is all ready for review and tested in
https://code.launchpad.net/~paelzer/ubuntu/+source/swtpm/+git/swtpm/+merge/417221
already.
No need to act other than reviewing this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have prepared the changes requested by Seth, stable fixes and an
apparmor/test fix.
Can be reviewed here:
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/swtpm/+git/swtpm/+merge/417221
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Now things pass locally, running the same on infra over lunch to see if
it is good there as well.
Testsuite summary for swtpm 0.6.3
# TOTAL:
Same error with kernel 5.13.0-37
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
Boot Failure - linux-image-5.13.0-28-generic | regression
To manage notifications about this bug go
Test stuck here:
4 0 356 1 20 0 2888 1716 - Ss hvc1 0:00 /bin/sh
1 03081 356 20 0 2888 140 - S+ hvc1 0:00 \_
/bin/sh
4 030823081 20 0 10192 4268 - S+ hvc1 0:00
\_ su -s /bin/bash ubuntu -c set
FYI this is blocked in proposed failing its autopkgtests.
This is reproducible in Ubuntu infra as well as locally in VM.
I'll try to extend the rules as needed and will let you know what i
found eventually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the confirmation, sorry for it to happen in the first place.
Would I have been aware of the backport of the broken debhelper it could have
been prevented.
I'll drop the delta on next major merge after rechecking if debhelper is fixed
then.
Until then I'm marking this fix released.
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4809
The former test-hang that affects current proposed migration is still present.
I'll debug that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "showing vmware player install without the reported issue"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1964285/+attachment/5571721/+files/vm-jammy-no-policyrc.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Yuhua, so the file is there - but NOT owned by a package.
Which triggers the obvious question where did it come from?
Thanks for sharing the exact link you use to get your image - that will
avoid misunderstandings.
I unpacked the ISO and on there is no mentioning of policy-rc.d.
$ grep
List of these fix-only changes:
version 0.6.3:
- swtpm:
- Do not chdir(/) when using --daemon
- swtpm-localca:
- Re-implement variable resolution for swtpm-localca.conf
- tests:
- Use ${WORKDIR} in config files to test env. var replacement
- man:
- Add missing .config
Thanks for the ping Seth
The fix for that is in:
commit 0f75b4baf272fd08e39d636e6c1f37585d752e1e
Author: Stefan Berger
Date: Wed Feb 16 11:17:47 2022 -0500
swtpm: Check header size indicator against expected size (CID
375869)
But in fact swtpm has stable branches and 0.6.3 seems to be a
> @paelzer, assuming rustc gets to main, do we need to downgrade the Recommends:
> cargo into a Suggests?
Yes if Cargo isn't ready for promotion to main yet you can't promote
anything that has a Recommends/Depends onto it.
--
You received this bug notification because you are a member of Ubuntu
MP approved, tests good, upstream ok with the change (some CI issues,
but nothing really stopping it) => uploaded the fix for Jammy.
** Changed in: spice (Ubuntu)
Assignee: Lena Voytek (lvoytek) => Christian Ehrhardt (paelzer)
--
You received this bug notification becau
I have built a fixed libvirt in server-backports mitigating the issue until
debhelper is fixed.
=> 7.6.0-0ubuntu1.1~backport20.04-202203211319~ubuntu20.04.1
=> 7.6.0-0ubuntu1.1~backport18.04-202203211344~ubuntu18.04.1
I'll keep the bug open as I want to drop this change as soon as
debhelper is
Hi Brian, that is very unfortunate - I've seen and worked on that in the
most recent release (22.04) and there we fixed it interim-wise in
libvirt and then finally in debhelper.
For some context see:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1959054
But that was due to a change in
See bug 1965758 this also breaks focal-backports - please upload the fix
there as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked
Subscribing Dave Jones who looked at this for Jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965758
Title:
[BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal
To manage notifications
@Yuhua,
hello this is really odd.
Until one can hopefully reproduce this soon on our side could you also run this
in the failing environment?
dpkg -S /usr/sbin/policy-rc.d
Because as far as I can see in the archive all that could exist is this
list:
root@j:~# apt-file search policy-rc.d
Thanks for the ping on this old case Alexander!
Can you confirm that this is what you see on 22.04 with the there recent
2:11.3.5-1ubuntu4 version of open-vm-tools?
I have subscribed John Wolfe who looks after open-vm-tools from VMwares
side and might have more details.
Further I added a bug
** Changed in: needrestart (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965090
Title:
[FFe] updated needrestart (form git) for Jammy
To manage
I did some more case analysis on this - this is complex and I might be
wrong - but for now it seems to me that a revert of the offending commit
is the best short term option. I've updated the upstream issue and
submitted a PR:
- https://gitlab.freedesktop.org/spice/spice/-/issues/64
-
** Changed in: needrestart (Ubuntu)
Status: New => 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/1965090
Title:
[FFe] updated needrestart (form git) for Jammy
To manage
Right now to me it seems we need to choose between pain, pain and more
pain:
- do a python3 transition with mini-buildd 1.0.49
+ that seems to be the reason we had 1.1.19 in Focal, and 1.0.49
isn't ready yet
+ Back in Apr 2021 v2.0 was called 2 weeks away, still not released
today
Public bug reported:
Hi,
we know that the new python-django
python-django | 2:3.2.12-2| jammy-proposed | source
is blocked by mini-buildd
The problem is that in mini-buildd in focal someone went ahead and since then
we are on
the bleeding edge track.
mini-buildd | 1.0.49
Public bug reported:
When creating a VPNC account, entering the second letter in the "Group
name" field disables the "Add" button. The VPNC account cannot be
created.
Ubuntu Jammy Jellyfish (development branch)
Release:22.04
network-manager-vpnc version 1.2.8-2
I think the FFE and upload is prepared, time to ask Foundations (as
package owners and for the release team members there) to have a look at
the bug and MR to ack if they are ok with it.
** Changed in: needrestart (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
4. detecting VMs
4a) no outdated ones
root@j-needrestart:~# needrestart
Scanning processes...
No services need to be
3. Tail of a log updating various packages showing (the new) needrestart
as invoked by apt
...
Processing triggers for install-info (6.8-4build1) ...
Processing triggers for libc-bin (2.35-0ubuntu3) ...
Processing triggers for rsyslog (8.2112.0-2ubuntu2) ...
Processing triggers for
2. Upgrade log (current to new version)
root@j-needrestart:~/testnr# apt install needrestart
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
libfreetype6
Use 'apt
1. Install log (of the new version):
root@j-needrestart:~/testnr# apt install needrestart
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
libfreetype6
Use 'apt
Public bug reported:
Hi,
I've seen this while looking for NBS and saw
intel-opencl-icd holding in the old libigdgmm11
I checked if there was no rebuild, but there was one that would pick up
libigdgmm12 but it is an FTBFS
Subscription was added by James (thanks) now it was ready:
Override component to main
python-cheroot 8.5.2+ds1-1ubuntu3 in jammy: universe/misc -> main
python3-cheroot 8.5.2+ds1-1ubuntu3 in jammy amd64:
universe/python/optional/100% -> main
python3-cheroot 8.5.2+ds1-1ubuntu3 in jammy arm64:
Hi Sven,
as tom said on IRC - to some extend it is that Bionic didn't have a Rome chip
definition yet, so the changes to add it to Rome do not 100% make sense there.
You have as part of similar fixes there already:
1. all kind of intel chips which were faster to provide that for 2.11 (in the
The Team that needs to be subscribed is actually
https://launchpad.net/~ubuntu-openstack but other than that my
assessment above is still correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930111
Thanks for those two fixes Corey!
That leaves:
$ reverse-depends --release jammy src:python-ceilometerclient
Reverse-Depends
* vitrage-tempest-plugin(for python3-ceilometerclient)
Let me add a bug task for this as it either needs a similar fix or needs to be
removed together with
FYI - Right now it seems this is all good, but waits for openstack-
ubuntu-packagers to subscribe to the package. I've pinged #openstack
about this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In progress as part of bug 1965090, MP linked to this bug as well
(https://code.launchpad.net/~paelzer/ubuntu/+source/needrestart/+git/needrestart/+merge/417078)
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/needrestart/+git/needrestart/+merge/417078
** Changed
Thank you all,
to summarize we are now:
- MIR Ack
- Security Ack
=> Can be promoted to main from this POV
Currently we have:
python-cheroot | 8.5.2+ds1-1ubuntu2 | jammy/universe | source
python-cheroot | 8.5.2+ds1-1ubuntu3 | jammy-proposed/universe | source
That ubuntu3 version is
FYI https://launchpad.net/ubuntu/+source/python-
cheroot/8.5.2+ds1-1ubuntu3 is in -proposed trying to fix this
** Changed in: python-cheroot (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the info Steve, glad to see progress on that.
If I might ask - what about the security review? I assume you have kind
of done that already before trying to suggest to promote it, but
formally security should state somewhere here that you have done your
usual checks.
Oh and finally
Thank you Steve!
Re-reviewed and sponsored to Jammy
@Lena - do not forget to try to upstream it so that at some point we can drop
the Delta.
** Changed in: swtpm (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964093
Title:
nfsver=3,udp not working anymore
To manage notifications about this bug go to:
** Changed in: containerd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960449
Title:
Backport container stack in Jammy
To
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960824
Title:
[MIR]: nfs-utils (regex plugin)
To manage notifications about this bug go to:
** Changed in: needrestart (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965090
Title:
[FFe] updated needrestart (form
** Tags removed: server-triage-discuss
** Changed in: spice (Ubuntu)
Assignee: (unassigned) => Lena Voytek (lvoytek)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964777
Title:
In terms of annoyance this is "Critical", but since it correctly
initializes just a bit later and then works fine I can't consider it
worse than "Medium" at the moment.
** Tags added: server-todo server-triage-discuss
** Changed in: spice (Ubuntu)
Importance: Undecided => Medium
--
You
New build in PPA fixing this ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965090
Title:
[FFe] updated needrestart (form git) for Jammy
To manage notifications about this bug go to:
Testing is still ongoing (if only the time I can dedicate wouldn't be so
scarce).
Right now I see this on install:
Error parsing /etc/needrestart/needrestart.conf: Can't modify anonymous hash
({}) in scalar assignment at (eval 14) line 111, near "0,"
Unmatched right curly bracket at (eval 14)
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965090
Title:
[FFe] updated needrestart (form git) for Jammy
To manage notifications about this bug go to:
Thanks for the status update Athos, to be clear those two are waiting
for the SRU team in bionic/focal-unapproved since 2022-02-24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961127
Title:
New
** Description changed:
+ [Rationale]
+
Hi,
there was no new version tagged for about two years now.
But plenty of fixes that are IMHO important for Jammy have piled up.
Especially since needrestart is installed and enabled by default I'd think
this makes sense to not have too many
401 - 500 of 23066 matches
Mail list logo
