Public bug reported:
Historically on Debian and Ubuntu, before systemd, the default handling
of /tmp was to periodically, and at boot, remove all files/directories
older than 30 days; and leave other contents alone.
With the move to systemd, the "default" (really, hard-coded in
** Package changed: ubiquity (Ubuntu) => cups (Ubuntu)
** Tags removed: ubiquity-22.10.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2018538
Title:
All PDFs when
Reuploaded with fixed autopkgtest and ready for re-review.
--
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/2011458
Title:
ssh fails to rebind when it is killed with -HUP
I do not see what this change was supposed to solve. I disagree with
the *existing* version check in germinate, and do not want to see more
of these - it imposes needless barriers for updating the metapackages.
--
You received this bug notification because you are a member of Ubuntu
Touch
Nick, note that it's safe to stop the primary ssh service despite there
being an open connection, as open connections are left running. So
maybe that's an easier approach.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
The documentation about how to roll back socket activation of sshd
became inaccurate after version 1:9.0p1-1ubuntu4 when we started using a
drop-in file to finalize activation rather than this being configured
statically in ssh.service. The drop-in file
The refactor of apport-gtk in the jammy queue includes this change:
-if not isinstance(text, bytes):
-text = text.encode('UTF-8')
This code is not included in the refactored function. Why is it safe to
drop this code?
** Changed in: apport (Ubuntu Jammy)
Hello Jeremy, or anyone else affected,
Accepted evolution-data-server into lunar-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/evolution-data-
server/3.48.1-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing
This bug report is lacking required information for an SRU.
** Changed in: ayatana-indicator-messages (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
** Changed in: openssh (Ubuntu Kinetic)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Please make sure to forward this to Debian as well.
--
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/2011458
Title:
ssh fails to rebind when it is killed with -HUP
Status
The session did eventually exit:
Active: failed (Result: timeout) since Fri 2023-04-21 11:24:31 PDT;
2min 48s ago
However, the time while the system was suspended didn't count towards
the session limit.
This kind of makes sense, but is also at odds with my goal of also using
pam_time to
ok, reproduced the failure - if the system is suspended at the session
expiry, the session apparently is never closed.
Active: active (running) since Fri 2023-04-21 11:13:02 PDT; 7min
ago
RuntimeMaxUSec=5min
--
You received this bug notification because you are a member of Ubuntu
Touch
Ah, now, rechecking, it appears the gdm session is mostly dead:
$ systemctl status session-35.scope --no-pager -l | sed -e's/User .*/User foo/'
× session-35.scope - Session 35 of User foo
Loaded: loaded (/run/systemd/transient/session-35.scope; transient)
Transient: yes
Active: failed
sion-35.scope
RuntimeMaxUSec=5min
#
# date
Fri Apr 21 10:52:23 PDT 2023
#
Still running past the limit.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer
On Mon, Apr 17, 2023 at 01:30:11PM -, Nick Rosbrook wrote:
> Odd. Does `systemctl show --propoerty=RuntimeMaxUSec session-2.scope`
> show the same thing, or something different?
For a current session, which is session-93.scope, I see in the file:
RuntimeMaxSec=1h 38min 56s
And from
Public bug reported:
/usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h in qtbase5-dev
cannot compile:
/usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h:8:10: fatal error:
QtDbus/qtdbusglobal.h: No such file or directory
8 | #include
| ^~~
Although this was working with the ppa package, enforcement is failing
again.
# apt policy systemd
systemd:
Installed: 249.11-0ubuntu3.10~debug1
Candidate: 249.11-0ubuntu3.10~debug1
Version table:
*** 249.11-0ubuntu3.10~debug1 500
500
Hello Gerard, or anyone else affected,
Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Thomas, or anyone else affected,
Accepted krb5 into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/krb5/1.19.2-2ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks, I've confirmed the fix on jammy here.
--
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/2015126
Title:
systemd doesn't successfully enforce RuntimeMaxSec for gnome
For reference, populating RuntimeMaxSec is done via
https://github.com/vorlonofportland/pam_session_timelimit; there is no
existing support for this in Ubuntu today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Public bug reported:
On Jammy, I have configured systemd to set RuntimeMaxSec on certain user
sessions:
# cat /run/systemd/transient/session-43.scope
# This is a transient unit file, created programmatically via the systemd API.
Do not edit.
[Scope]
Slice=user-1000.slice
[Unit]
"broken pipe" means the maintainer script died because the debconf
frontend exited abnormally (this is the only pipe we wait for). This
isn't a bug in pam, it can't proceed with configuration if it doesn't
get sane answers for debconf. What was the context in which you were
running the package
FFe granted.
** Changed in: software-properties (Ubuntu)
Status: New => Triaged
--
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/2011697
Title:
[FFe]
ubuntu-release-upgrader 1:22.04.13 and later in Ubuntu 22.04 includes a
check to detect pam_tally's presence in /etc/pam.d and abort the upgrade
to let the user fix up their config beforehand.
If you are getting failures from libpam-modules during do-release-
upgrade, then this check is not
Hello Jaap, or anyone else affected,
Accepted libidn into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libidn/1.38-4ubuntu1
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 openldap into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openldap/2.5.14+dfsg-0ubuntu0.22.10.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello errors.ubuntu.com, or anyone else affected,
Accepted apport into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.23.1-0ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello errors.ubuntu.com, or anyone else affected,
Accepted apport into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.23.1-0ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Mingun, or anyone else affected,
Accepted apport into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.23.1-0ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: fr-3673
--
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/2011458
Title:
ssh fails to rebind when it is killed with -HUP
Status in openssh package in Ubuntu:
To proceed with this SRU, I would like to have some analysis of what
makes this an armhf-only failure. Is it to do with the fact that armhf
autopkgtests run in a container and others do not? If so, it seems to
me that a more correct fix for the test is to detect that we're running
in a container
Hello Craig, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Nick, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Tuetuopay, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Pedro, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Nick, or anyone else affected,
Accepted systemd into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Tuetuopay, or anyone else affected,
Accepted systemd into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
resolvconf has been removed from Ubuntu in 22.10 and later in favor of
the systemd-resolved implementation, so this bug is fixed for later
releases.
Installing resolvconf in 22.04 is also discouraged.
** Changed in: resolvconf (Ubuntu)
Status: Triaged => Fix Released
--
You received
Hello Sergio, 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.14+dfsg-0ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Sergio, or anyone else affected,
Accepted openldap into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openldap/2.5.14+dfsg-0ubuntu0.22.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:15.99.1+dfsg1-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into kinetic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-1ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
I'd like to understand better exactly how it happened that the user got
this crash. Is it a matter of a corrupted .crash file on input, or is
it that the user tried to feed in a file that was not intended to be
input for apport-unpack? I see that the command line that triggered
this appears to
Hello Andreas, or anyone else affected,
Accepted apparmor into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.7-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Project changed: ubuntu-cdimage => initramfs-tools (Ubuntu)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
initramfs-tools-ubuntu-core is a package specific to the boot of Ubuntu
Core, so unrelated to your issue.
Reassigning to initramfs-tools, which is at least a package that you
have installed.
Why does your bug report title mention the use of zstd?
** Package changed: initramfs-tools-ubuntu-core
this is an incorrect interpretation of the update_excuses output while
the new source package had not yet been built. These binaries get
removed via the NBS process if and when they no longer have reverse-
dependencies in the release pocket - which is *after* the new procps
migrates from
FWIW this is less interesting to me personally now, as I found the right
switches to abi-compliance-checker to deal with C++ keywords as C
variable names. And also it turns out there are a lot of C headers that
have this problem. So while it's probably still interesting to someone
to be able to
> rescue-ssh.target is a disabled or a static unit not running, not
starting it.
Not really a complaint, just informational.
> But I think the underlying issue is that ssh is already on, and I'm logged in
> via it.
> And that makes the service restart of the ssh socket which was added break.
I
Public bug reported:
aalogparse.h cannot be included from C++ code because it uses
'namespace' and 'class' as variable names, and these are reserved
keywords in C++.
/usr/include/aalogparse/aalogparse.h:137:15: error: expected unqualified-id
before ‘namespace’
137 | char *namespace;
There is no reason to expect this to be fixed in the daily jammy image.
Progress on fixing this was blocked for months for lack of a test case.
A prospective fix has been uploaded to the queue. Daily server images
won't include the fix until it has been reviewed by the SRU team,
accepted into
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660
Title:
networkx incompatible with
> systemd-journald now uses GID 999
Ummm where is this coming from? Debian Policy states:
9.2.2. UID and GID classes
--
[...]
100-999:
Dynamically allocated system users and groups. Packages which need
a user or group, but can have this user or group allocated
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: apport (Ubuntu)
Status: Triaged => Invalid
** Changed in: apport (Ubuntu Focal)
Status: Triaged => Invalid
** Changed in: gtk+3.0 (Ubuntu Focal)
Status: Confirmed => Triaged
** Changed in:
** No longer affects: pam (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1977493
Title:
Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
then this must be a bug in the init-system-helpers package providing the
deb-systemd-invoke command; reassigning.
** Package changed: krb5 (Ubuntu) => init-system-helpers (Ubuntu)
** Changed in: init-system-helpers (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
systemctl is a non-optional component of an Ubuntu 22.04 system. What
does `which systemctl` return for you? What does `systemctl` return
when you run it?
** Changed in: krb5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
On Mon, Jan 23, 2023 at 11:19:56AM -, Dimitri John Ledkov wrote:
> UEFI specifications in general ignore signing time.
> IMHO we should remove / not include signing timestamp in the UEFI
> signatures to avoid this.
Doesn't this suggest it's actually a kernel bug for enforcing something here
Hello Sebastien, or anyone else affected,
Accepted software-properties into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.19
in a few hours, and then in the -proposed repository.
Please help us by testing this
After discussion with Seb, have confirmed that the language pack gets
updated strings injected from the package build, so does not need an
updated .pot file in the source tarball.
I noticed in the review that there is a change to debian/control,
dropping references to gir1.2-snapd-1. Normally we
** Also affects: software-properties (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: software-properties (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Removing packages:
tbb 2020.3-2.1ubuntu1 in lunar
libtbb2 2020.3-2.1ubuntu1 in lunar amd64
libtbb2 2020.3-2.1ubuntu1 in lunar arm64
libtbb2 2020.3-2.1ubuntu1 in lunar armhf
libtbb2 2020.3-2.1ubuntu1 in lunar i386
An upload of software-properties to focal-proposed has been rejected
from the upload queue for the following reason: "SRU updates
translatable strings but pot file update is missing in the source".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
An upload of software-properties to jammy-proposed has been rejected
from the upload queue for the following reason: "SRU updates
translatable strings but pot file update is missing in the source".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Removing packages from lunar:
flexbar 1:3.5.0-4ubuntu1 in lunar
flexbar 1:3.5.0-4ubuntu1 in lunar amd64
flexbar 1:3.5.0-4ubuntu1 in lunar arm64
flexbar 1:3.5.0-4ubuntu1 in lunar armhf
flexbar 1:3.5.0-4ubuntu1 in lunar ppc64el
$ reverse-depends src:flexbar
$ reverse-depends src:flexbar -a source
No reverse dependencies found
$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tbb in Ubuntu.
https://bugs.launchpad.net/bugs/2003263
Title:
please RM
$ reverse-depends -a source libtbb2-dev
Reverse-Testsuite-Triggers
* intel-mkl
Reverse-Build-Depends
* flexbar
* open3d
* openvdb
$
open3d and openvdb are fixed in lunar-proposed, and don't have a runtime
dependency on libtbb2 (so why do they have the build-dep?), so this is
ok.
--
You
** Changed in: networkx (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660
Title:
networkx incompatible with
pypy removed 30Dec:
(From Debian) RoQA; py2 leftover; no rdeps; Debian bug #937511
** Changed in: pypy (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Have you forwarded this patch to Debian? Debian doesn't *currently*
have any flavors that are a substring of another, but that is not a
policy in Debian, so the patch is also applicable there.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Fix Committed
--
You received this
** Package changed: cryptsetup (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2002187
Title:
package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed
** Changed in: zlib (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1998470
Title:
re-add s390x vectorized crc32 support to
** Changed in: openssh (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openssh (Ubuntu)
Assignee: api.ng (hektve) => (unassigned)
** Changed in: indicator-network (PLD Linux)
Status: Confirmed => Invalid
** Package changed: indicator-network (PLD Linux) =>
Uploaded. One fix, you commented in debian/changelog about removing
--crc32-vx from debian/rules, but didn't actually do so. So I made that
change before uploading. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: foundations-todo fr-2592 verification-needed
verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981109
Title:
server image pulls
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1988418
Title:
Please merge
> I think Debian does include it, just in a slightly different position?
> At least, I can see cdc-phonet.ko added after "can" in the following
> diff:
Ah, slightly different sorting rules and string-blindness.
We concur now wrt what should be uploaded. I'll look at sponsoring
this.
--
You
My standard way of reviewing a merge is to do the merge myself and see
what comes up different. Here are my observations:
conf/initramfs.conf: the commented COMPRESSLEVEL setting should match
the default, which for us is 1, not 3.
debian/control: upstream has Recommends: ${busybox:Recommends},
The issue here was a locally installed libep11 package that depended on
old OpenSSL. The problem was reported the first time apt was run after
installing libep11. The old libssl dependency had nothing to do with
systemd-coredump.
--
You received this bug notification because you are a member
Ok. The Ubuntu position is that ubuntu-minimal is the package that
defines the smallest system considered Ubuntu. If you don't have
ubuntu-minimal installed, you have a pile of packages, but not an Ubuntu
system that we can provide support for.
It's impressive that you had a system that has
> The message queue rules support could cause issues for AppArmor
> policies that were developed before there was support for mqueues,
Please explain in more detail why this is a risk. reading the
'mqueue1-' patch, the documentation reads to me as the default being
full access allowed:
sascha, are you able to provide information about a reproducer
environment for this? I'd like to see this fixed but we need to have a
way to make sure the change actually fixes things.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
> The fixes are each limited to one line, hence there are not many
issues to expect
Except that one of these one-line changes is stated to enable a new
optimization path in the shared library which was accidentally not
enabled before. Since almost everything in Ubuntu uses the shared
library and
Hello Jeremy, or anyone else affected,
Accepted evolution-data-server into kinetic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/evolution-data-
server/3.46.1-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing
What should have happened on upgrade from 20.04 to 22.04 is:
- upgrade of ubuntu-minimal pulls in usrmerge as a Recommended package
- usrmerge converts your system so that /bin is a symlink to /usr/bin, /sbin is
a symlink to /usr/sbin, etc.
- resolving run-parts as either /bin/run-parts or
Are you missing the ubuntu-minimal package on your system?
Non-usrmerged systems are not supported in 22.04 and later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debianutils in Ubuntu.
** Changed in: openssh (Ubuntu)
Status: Fix Released => Fix Committed
--
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/1993478
Title:
package openssh-server
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
On Tue, Nov 01, 2022 at 03:48:54PM -, Jeremy Bicha wrote:
> Public bug reported:
> There is a new suggested field to the os-release file: SUPPORT_END=-
> MM-DD
> If it is set, systemd 252 apparently sets a "support-ended" taint flag
> once that date has been reached.
"support" is a
An upload of openssh to kinetic-proposed has been rejected from the
upload queue for the following reason: "patch to be revised".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
+if dpkg --compare-versions "$2" lt-nl 1:9.0p1-1ubuntu8~ && [ -n
"$NO_SOCKET_MIGRATION" ]; then
I'm going to ask that we be ultra-conservative here. It is very
difficult in general to un-do in a maintainer script something that we
think we did previously, because the admin may have done
nor why you
get a configuration error on upgrade in the absence of this file.
> I'll try to do a 22.04 -> 22.10 upgrade on my local machine later
today.
Thanks. At the moment this is unreproducible and there is no further action
for us to take.
--
Steve Langasek Give me a lever l
On Tue, Oct 25, 2022 at 01:55:53AM -, Chris M. wrote:
> [Unit]
> After=ssh.socket
> Requires=ssh.socket
>
> ** Attachment added: "00-socket.conf"
This appears to be the contents of
/etc/systemd/system/ssh.service.d/00-socket.conf. I am looking for the
contents of the
The error in your (Machine-1) log is:
> Setting up openssh-server (1:9.0p1-1ubuntu7) ...
> Replacing config file /etc/ssh/sshd_config with new version
> Synchronizing state of ssh.service with SysV service script with
> /lib/systemd/systemd-sysv-install.
> Executing:
On Fri, Oct 21, 2022 at 02:06:33PM -, Christophe M. wrote:
> Hellow, same issue here. SSHD failed during the do-release-upgrade
> process on one of my machines, and now it refuses to change the port to
> anything else than 22 on both of my machines. If I start the sshd daemon
> using systemd
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => Medium
** Changed in: fontconfig (Ubuntu)
Importance: Undecided => Medium
** Changed in: fontconfig (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: libreoffice (Ubuntu)
Status: Confirmed => Incomplete
--
** Changed in: openssh (Ubuntu)
Status: Incomplete => Triaged
--
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/1993478
Title:
package openssh-server 1:9.0p1-1ubuntu7
Based on what you quote of the contents of your sshd_config, my
expectation would be that we NOT migrate to socket activation on
upgrade.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Critical
** Tags added: foundations-todo
--
You received this bug notification because you are a
301 - 400 of 3336 matches
Mail list logo
