[Touch-packages] [Bug 1988418] Re: Please merge initramfs-tools 0.142 from Debian unstable.

2022-11-28 Thread Steve Langasek
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}, zstd,
but you only have Recommends: zstd.  Why?

debian/rules: you caught that there were build-time tests added by us
that should be retained even though upstream dropped their override;
good (I missed this).

hook-functions: upstream landed the change to exclude modems from the
net usb drivers, but we had cdc-phonet.ko in our list but Debian does
not.  I do not know why Debian did not include it; I think we should
include it in the merge and forward to Debian for consideration.

+   elif [ -n "${DEVICE}" ] || [ -n "${DEVICE6}" ]; then

FWIW I would write this as elif [ -n "$DEVICE$DEVICE6" ]; then

Otherwise, this looks good to me.

-- 
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 initramfs-tools 0.142 from Debian unstable.

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Please merge initramfs-tools 0.142 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997579] Re: [Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

2022-11-24 Thread Steve Langasek
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 of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1997579

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993037] Re: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course

2022-11-19 Thread Steve Langasek
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 been working continuously
without ubuntu-minimal since 2008, I'm glad it's worked for you so far.
But the resolution of this bug is that you should install the ubuntu-
minimal package.

We will not add additional dependencies on the usrmerge package in an
already-released LTS.

Also, if when you say "upgrade from Debian to Ubuntu" you mean cross-
grading an existing Debian system, this is not a supported Ubuntu
installation path, but if you happen to know whether you followed a
cross-grading guide somewhere that fails to mention you should install
ubuntu-minimal, I would try to get that guide updated so other users
don't trip on such problems.

** Changed in: debianutils (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: systemd-cron (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debianutils in Ubuntu.
https://bugs.launchpad.net/bugs/1993037

Title:
  Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking
  systemd-cron in the course

Status in debianutils package in Ubuntu:
  Won't Fix
Status in systemd-cron package in Ubuntu:
  Won't Fix

Bug description:
  (Found in Ubuntu 22.04 LTS)
  package debianutils keeps run-parts executable in /usr/bin/
  while package systemd-cron tries to find it in /bin/

  $ which run-parts
  /usr/bin/run-parts

  $ dpkg -S `which run-parts`
  debianutils: /usr/bin/run-parts

  $ grep =/bin/run /lib/systemd/system/cron*
  /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report 
/etc/cron.daily
  /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report 
/etc/cron.hourly
  /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report 
/etc/cron.monthly
  /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report 
/etc/cron.weekly

  Because of that, cron-daily.serice gets info "failed" state soon after
  system reboot.

  Please resolve the problem to make systemd-cron more usable.
  Thanks in advance for your help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1994146] Re: [SRU] apparmor - Focal, Jammy

2022-11-18 Thread Steve Langasek
> 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:

  AppArmor Message Queue permissions are implied when a rule does not explicitly
  state an access list. By default, all Message Queue permissions are implied.

Is that not what this means, or is mqueue access actually denied by
default and this refers only to how an unqualified 'mqueue' rule is
interpreted?

> Jammy already has the abi pinned for a kernel
> that does not have support for mqueue mediation.

In that case how does introducing mqueue support in apparmor benefit
users of jammy?

** Changed in: apparmor (Ubuntu Jammy)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1994146

Title:
  [SRU] apparmor - Focal, Jammy

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  In Progress
Status in apparmor source package in Jammy:
  Incomplete

Bug description:
  [ Impact ]

  This is a SRU proposal for apparmor in Focal and Jammy.
  For focal, we want to SRU fixes for Bug 1964636 which introduces the
  capability upstream patches. We are also fixing Bug 1728130 and
  Bug 1993353 which are introducing full backport of abi from
  apparmor-3.0 and support for POSIX message queue rules, which are both
  a request from Honeywell.

  Note that specifically for message queue rules, we are overriding the
  abi behavior.
  Message queue mediation is not a part of the 2.13 abi we are
  pinning. Honeywell has a kernel that has message queue mediation,
  but their policy does not contain an abi specified, so when we pin the
  abi for a kernel that does not mediate message queue, it will break
  Honeywell's AppArmor policies. So we are making an exception: when abi
  is not specified in the policy, and the policy contain mqueue rules,
  we are enforcing mqueue rules. When the policy does not contain mqueue
  rules, then they are not being enforced. This is so we do not break
  Honeywell policies and we also are not breaking policies that were
  developed when there was no mqueue or abi support.

  For jammy, we are SRUing fixes for Bug 1993353 which adds message
  queue rules support. 

  
  [ Test Plan ]

  This has been extensively tested by using QA Regression Tests[1] for
  AppArmor. All tests have passed and demonstrated AppArmor to be
  working as expected. We are also adding regression tests for message
  queue rules[2] which guarantees it is working as expected.

  [1] 
https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py
  [2] https://gitlab.com/apparmor/apparmor/-/merge_requests/858

  [ Where problems could occur ]

  The message queue rules support could cause issues for AppArmor
  policies that were developed before there was support for mqueues,
  that's why we are also backporting abi support and pinning the abi on
  parser.conf on focal. Jammy already has the abi pinned for a kernel
  that does not have support for mqueue mediation.

  [ Other Info ]

  The patches for both focal and jammy can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249

2022-11-18 Thread Steve Langasek
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 subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1937110

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Jammy:
  Incomplete

Bug description:
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  
  His DHCP response looks like this:

  
  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
ac1f0101 ..

  
  Im booting the subiquity process with an patched ipxe 
(https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  
  Would be awesome if this could be fixed.. maybe just a simple busybox compile 
option?

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937110/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982583] Re: Fix for zlib CRC32 optimization for s390x

2022-11-18 Thread Steve Langasek
> 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 not the static library, this code is basically untested in
Ubuntu up until now, and this is a core library with many reverse-
dependencies!

The code was originally introduced in impish, and the related bug LP:
#1932010 doesn't show anything in the way of a test plan.

I am holding this SRU until the change a) has landed in the devel
series, b) there is a more comprehensive test plan to check for
regressions (including on non-z15 hardware) than a small test program.

** Changed in: zlib (Ubuntu Kinetic)
   Status: New => Incomplete

** Changed in: zlib (Ubuntu Jammy)
   Status: New => Incomplete

-- 
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/1982583

Title:
  Fix for zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Jammy:
  Incomplete
Status in zlib source package in Kinetic:
  Incomplete

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * There were two issues identified in the current
     zlib CRC32 optimization for s390x implementation:

   * 1) s390_crc32_vx() signature mismatch
    which causes a warning

   * 2) '-DS390_CRC32_VX' was not added to SFLAGS
    which results in vectorization being enabled only in the static library.

   * The fixes are quite small and affect each only one line:

   * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx
  declaration

   * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"'

  [ Test Plan ]

   * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed
     on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
     of a small test program (in C) that checks for
     s390_crc32_vx() signature mismatches.

   * The bug reporter has a set of s390x-specific tests that will be
  executed.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The fixes are each limited to one line, hence there are
     not many issues to expect, other than:

   * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS,

   * in case the changed data type in s390_crc32_vx is causing issues
     inside of s390_crc32_vx or in other parts of the code.

   * Structural and syntactical issues can be identified with a test build
     that was done for all affected Ubuntu releases and for all major archs:
     https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379+lp1982583

  [ Other Info ]

   * This bug (LP#1982583) is solved in combination with LP#1990379,
     so that only one package update is needed.
     However, LP#1990379 also affects Focal, but this bug only Jammy and 
Kinetic.

   * To fix LP#1990379 also for focal the debdiff mentioned there is needed, 
too.
  __

  'zlib CRC32 optimization for s390x works only in a static library'

  I've discovered two issues in lp1932010-ibm-z-add-vectorized-
  crc32-implementation.patch:

  1) s390_crc32_vx() signature mismatch, resulting in a warning.
  2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being 
enabled only in the static library.

  I've attached the updated patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982583/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993834] Re: Update evolution-data-server to 3.46.1

2022-11-18 Thread Steve Langasek
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 this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: evolution-data-server (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1993834

Title:
  Update evolution-data-server to 3.46.1

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  This is a new stable release in the 3.46 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.46.1/NEWS

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1993834/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993037] Re: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course

2022-11-17 Thread Steve Langasek
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 /usr/bin/run-parts on the 
filesystem just works.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debianutils in Ubuntu.
https://bugs.launchpad.net/bugs/1993037

Title:
  Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking
  systemd-cron in the course

Status in debianutils package in Ubuntu:
  Incomplete
Status in systemd-cron package in Ubuntu:
  New

Bug description:
  (Found in Ubuntu 22.04 LTS)
  package debianutils keeps run-parts executable in /usr/bin/
  while package systemd-cron tries to find it in /bin/

  $ which run-parts
  /usr/bin/run-parts

  $ dpkg -S `which run-parts`
  debianutils: /usr/bin/run-parts

  $ grep =/bin/run /lib/systemd/system/cron*
  /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report 
/etc/cron.daily
  /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report 
/etc/cron.hourly
  /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report 
/etc/cron.monthly
  /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report 
/etc/cron.weekly

  Because of that, cron-daily.serice gets info "failed" state soon after
  system reboot.

  Please resolve the problem to make systemd-cron more usable.
  Thanks in advance for your help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993037] Re: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course

2022-11-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1993037

Title:
  Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking
  systemd-cron in the course

Status in debianutils package in Ubuntu:
  Incomplete
Status in systemd-cron package in Ubuntu:
  New

Bug description:
  (Found in Ubuntu 22.04 LTS)
  package debianutils keeps run-parts executable in /usr/bin/
  while package systemd-cron tries to find it in /bin/

  $ which run-parts
  /usr/bin/run-parts

  $ dpkg -S `which run-parts`
  debianutils: /usr/bin/run-parts

  $ grep =/bin/run /lib/systemd/system/cron*
  /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report 
/etc/cron.daily
  /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report 
/etc/cron.hourly
  /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report 
/etc/cron.monthly
  /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report 
/etc/cron.weekly

  Because of that, cron-daily.serice gets info "failed" state soon after
  system reboot.

  Please resolve the problem to make systemd-cron more usable.
  Thanks in advance for your help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-11-12 Thread Steve Langasek
** 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 1:9.0p1-1ubuntu7 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Fix Committed
Status in openssh source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Users with /etc/ssh/sshd_config's that contain ListenAddress entries
  with the port specified will not be migrated to socket-activated ssh
  correctly, or may be migrated when they should not be (e.g. if
  ListenAddress, with a port number, is specified more than once). This
  leaves users with a broken sshd configuration.

  [Test Plan]

  There are 4 tests that should be used to verify the fix:

  1. Upgrade to Kinetic with just one ListenAddress entry, which
  specifies port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, 
and then running apt dist-upgrade (-proposed is disabled when using 
ubuntu-release-upgrader).
  * On an affected system, ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, ssh.socket will be active/listening, and
  /etc/systemd/system/ssh.socket.d/addresses.conf will contain the
  following:

  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  2. Upgrade to Kinetic with multiple ListenAddress entries, each
  specifying port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, 
and then running apt dist-upgrade (-proposed is disabled when using 
ubuntu-release-upgrader).
  * On an affected system, migration will be attempted despite the multiple 
ListenAddress options, and ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, the ListenAddress option will be parsed
  correctly, and migration will not be attempted.

  3. On a Kinetic system which was migrated, but with errors (e.g. test
  case #1, prior to being patched), installing the new package should
  correct the ssh.socket configuration.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.

  * The ssh.socket configuration should be fixed, and 
/etc/systemd/system/ssh.socket.d/addresses.conf should contain:
  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  4. On a Kinetic system which was incorrectly migrated to ssh socket
  activation (e.g. test case #2, prior to being patched), installing the
  new package reverts to the previous behavior.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.
  * The socket-activated ssh migration should be reverted, and ssh.service 
should be running as 

[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-11-07 Thread Steve Langasek
** 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.
https://bugs.launchpad.net/bugs/1993478

Title:
  package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Fix Committed
Status in openssh source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Users with /etc/ssh/sshd_config's that contain ListenAddress entries
  with the port specified will not be migrated to socket-activated ssh
  correctly, or may be migrated when they should not be (e.g. if
  ListenAddress, with a port number, is specified more than once). This
  leaves users with a broken sshd configuration.

  [Test Plan]

  There are 4 tests that should be used to verify the fix:

  1. Upgrade to Kinetic with just one ListenAddress entry, which
  specifies port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, 
and then running apt dist-upgrade (-proposed is disabled when using 
ubuntu-release-upgrader).
  * On an affected system, ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, ssh.socket will be active/listening, and
  /etc/systemd/system/ssh.socket.d/addresses.conf will contain the
  following:

  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  2. Upgrade to Kinetic with multiple ListenAddress entries, each
  specifying port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, 
and then running apt dist-upgrade (-proposed is disabled when using 
ubuntu-release-upgrader).
  * On an affected system, migration will be attempted despite the multiple 
ListenAddress options, and ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, the ListenAddress option will be parsed
  correctly, and migration will not be attempted.

  3. On a Kinetic system which was migrated, but with errors (e.g. test
  case #1, prior to being patched), installing the new package should
  correct the ssh.socket configuration.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.

  * The ssh.socket configuration should be fixed, and 
/etc/systemd/system/ssh.socket.d/addresses.conf should contain:
  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  4. On a Kinetic system which was incorrectly migrated to ssh socket
  activation (e.g. test case #2, prior to being patched), installing the
  new package reverts to the previous behavior.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.
  * The socket-activated ssh 

Re: [Touch-packages] [Bug 1995405] [NEW] Add SUPPORT_END to os-release

2022-11-01 Thread Steve Langasek
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 property of the product committments made around the OS, that
cannot definitively be known at the time of the GA release.  Encoding it in
a file in the OS therefore carries an implicit obligation to update that
file whenever changes are made to the support committments.  This does not
sound like something we want (in addition to already having to update
distro-info-data).

Why is it valuable for systemd to set this taint flag?  We already have
Ubuntu-native mechanisms for notifying users they are out of support.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1995405

Title:
  Add SUPPORT_END to os-release

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  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.

  https://manpages.debian.org/unstable/os-release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1995405/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993478] Proposed package upload rejected

2022-11-01 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1993478

Title:
  package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Kinetic:
  Triaged

Bug description:
  [Impact]

  Users with /etc/ssh/sshd_config's that contain ListenAddress entries
  with the port specified will not be migrated to socket-activated ssh
  correctly, or may be migrated when they should not be (e.g. if
  ListenAddress, with a port number, is specified more than once). This
  leaves users with a broken sshd configuration.

  [Test Plan]

  There are 4 tests that should be used to verify the fix:

  1. Upgrade to Kinetic with just one ListenAddress entry, which
  specifies port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * On an affected system, ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, ssh.socket will be active/listening, and
  /etc/systemd/system/ssh.socket.d/addresses.conf will contain the
  following:

  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  2. Upgrade to Kinetic with multiple ListenAddress entries, each
  specifying port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * On an affected system, migration will be attempted despite the multiple 
ListenAddress options, and ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, the ListenAddress option will be parsed
  correctly, and migration will not be attempted.

  3. On a Kinetic system which was migrated, but with errors (e.g. test
  case #1, prior to being patched), installing the new package should
  correct the ssh.socket configuration.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.

  * The ssh.socket configuration should be fixed, and 
/etc/systemd/system/ssh.socket.d/addresses.conf should contain:
  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  4. On a Kinetic system which was incorrectly migrated to ssh socket
  activation (e.g. test case #2, prior to being patched), installing the
  new package reverts to the previous behavior.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.
  * The socket-activated ssh migration should be reverted, and ssh.service 
should be running as before upgrade to Kinetic.

  [Where problems could 

[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-11-01 Thread Steve Langasek
+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 who-knows-what
in between and we may be undoing things that weren't actually ours.  So
whenever it's possible to detect that it wasn't us that did a thing, we
should avoid trying to undo it.

In the case of this particular failure, the state of the system of a user hit 
by this bug will be:
 - /etc/systemd/system/ssh.service.d/00-socket.conf and 
/etc/systemd/system/ssh.socket.d/addresses.conf both exist
- $2 argument to postinst will be LESS than 1:9.0p1-1ubuntu8~ because the 
release version of openssh-server will have failed to configure

So I suggest the following instead:

if dpkg --compare-versions "$2" lt-nl 1:9.0p1-1ubuntu7~ \
   && [ -e /etc/systemd/system/ssh.socket.d/addresses.conf ] \
   && [ -e /etc/systemd/system/ssh.service.d/00-socket.conf ] \
   && [ -n "$NO_SOCKET_MIGRATION" ]; then

This ensures that if, for any other reason the user has enabled the
ssh.socket unit but our script says NO_SOCKET_MIGRATION, we don't mangle
the systemd units to disable socket activation that might not have been
enabled by us in the first place.

(As a bonus, it will simplify and shorten the de-migration code
overall.)

-- 
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 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Kinetic:
  Triaged

Bug description:
  [NOTE FOR SRU TEAM]

  I would prefer that vorlon review the attached patch before the upload
  is accepted. I will remove this note when that has happened.

  [Impact]

  Users with /etc/ssh/sshd_config's that contain ListenAddress entries
  with the port specified will not be migrated to socket-activated ssh
  correctly, or may be migrated when they should not be (e.g. if
  ListenAddress, with a port number, is specified more than once). This
  leaves users with a broken sshd configuration.

  [Test Plan]

  There are 4 tests that should be used to verify the fix:

  1. Upgrade to Kinetic with just one ListenAddress entry, which
  specifies port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * On an affected system, ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, ssh.socket will be active/listening, and
  /etc/systemd/system/ssh.socket.d/addresses.conf will contain the
  following:

  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  2. Upgrade to Kinetic with multiple ListenAddress entries, each
  specifying port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * On an affected system, migration will be attempted despite the multiple 
ListenAddress options, and ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, the ListenAddress option will be parsed
  correctly, and migration will not be attempted.

  3. On a Kinetic system which was migrated, but with errors (e.g. test
  case #1, prior to being patched), installing the new package should
  correct the ssh.socket configuration.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that 

Re: [Touch-packages] [Bug 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04

2022-10-24 Thread Steve Langasek
On Tue, Oct 25, 2022 at 03:12:55AM -, Chris M. wrote:
> The machine that returned an openssh-server error and left me with a
> partially installed openssh-server package (dpkg IF flag) at the end of
> the upgrade process didn't have anything in ssh.socket.d, nor it had a
> ssh.socket.d folder in /etc/systemd/system/.

Then I do not have an explanation for the upgrade failing with the error
message in the log.

> Failed to restart ssh.socket: Unit ssh.socket has a bad unit file
setting.

The ssh.socket unit as shipped in the package does not have syntax errors. 
The maintainer script does, on upgrade, create a config snippet under
/etc/systemd/system/ssh.socket.d if there are Port or ListenAddress settings
in sshd_config, which could, if we have bugs, have syntax errors.  And the
sshd_config you provided does specify both Port and ListenAddress, and with
that config installed locally, an upgrade does create
/etc/systemd/system/ssh.socket.d/addresses.conf for me (without syntax
errors).  But you assert that this file does not exist after upgrade.  So I
can neither explain why you don't have
/etc/systemd/system/ssh.socket.d/addresses.conf after upgrade, 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 long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

-- 
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/1993869

Title:
  openssh-server cannot listen or bind to anything other than :::2 after
  upgrading to 22.10 from 22.04

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  This is a bug report to separate the second issue that was reported in this 
bug report:
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478

  There's an issue after upgrading to 22.10 from 22.04 that prevents
  opensshd from listening to anything other than :::2. I already
  commented in the bug report I linked, so I'll just copy/paste and add
  some details. I guess.

  The issue is that after upgrading, sshd doesn't use the Listen port or
  ListenAddress config from the sshd_config file or any custom config
  file that was in the sshd_config.d drop in folder anymore.

  Other drop in settings from sshd.config.d seem to be applied normally,
  the issue seem to be only for IP binding and custom ports.

  If I change Accept=no by Accept=yes in ssh.socket and reloads the
  socket unit, I can start sshd on a different port and I can also bind
  the IP to something else than ::

  There's an issue still, an instance of sshd is still listening to
  :::22 that is not started by SSHD but by init.

  root@ubuntulocal:~# netstat -antp
  Active Internet connections (servers and established)
  Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
  tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd
  tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin
  tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts
  tcp6 0 0 :::22 :::* LISTEN 1/init

  If I reboot after changing this no to yes in ssh.socket does not survive a 
reboot and fails to load sshd with a "Failed to queue service startup job" 
error.
  Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service 
startup job (Maybe the service file is missing or not a template unit?): 
Invalid argument
  Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 
'resources'.

  I had to mask/stop the sshd.socket unit and create a custom sshd
  service in /etc/systemd/system to be able start sshd on a custom port
  and IP.


  chris@ubuntulocal:~$ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago
Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
Tasks: 0 (limit: 18899)
   Memory: 4.0K
  CPU: 418us
   CGroup: /system.slice/ssh.socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Touch-packages] [Bug 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04

2022-10-24 Thread Steve Langasek
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 /etc/systemd/system/ssh.socket.d directory.  There should be
a file named /etc/systemd/system/ssh.socket.d/addresses.conf there, which is
what I'm looking for (along with anything else that might be there).

I have done a jammy->kinetic upgrade using the Machine-1 sshd config that
you provided, and I do NOT see the errors that were shown in your apt term
log.  I get an addresses.conf as follows:

# cat /etc/systemd/system/ssh.socket.d/addresses.conf 
[Socket]
ListenStream=
ListenStream=0.0.0.0:623
#

And the ssh socket activation works as expected.

-- 
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/1993869

Title:
  openssh-server cannot listen or bind to anything other than :::2 after
  upgrading to 22.10 from 22.04

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  This is a bug report to separate the second issue that was reported in this 
bug report:
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478

  There's an issue after upgrading to 22.10 from 22.04 that prevents
  opensshd from listening to anything other than :::2. I already
  commented in the bug report I linked, so I'll just copy/paste and add
  some details. I guess.

  The issue is that after upgrading, sshd doesn't use the Listen port or
  ListenAddress config from the sshd_config file or any custom config
  file that was in the sshd_config.d drop in folder anymore.

  Other drop in settings from sshd.config.d seem to be applied normally,
  the issue seem to be only for IP binding and custom ports.

  If I change Accept=no by Accept=yes in ssh.socket and reloads the
  socket unit, I can start sshd on a different port and I can also bind
  the IP to something else than ::

  There's an issue still, an instance of sshd is still listening to
  :::22 that is not started by SSHD but by init.

  root@ubuntulocal:~# netstat -antp
  Active Internet connections (servers and established)
  Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
  tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd
  tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin
  tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts
  tcp6 0 0 :::22 :::* LISTEN 1/init

  If I reboot after changing this no to yes in ssh.socket does not survive a 
reboot and fails to load sshd with a "Failed to queue service startup job" 
error.
  Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service 
startup job (Maybe the service file is missing or not a template unit?): 
Invalid argument
  Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 
'resources'.

  I had to mask/stop the sshd.socket unit and create a custom sshd
  service in /etc/systemd/system to be able start sshd on a custom port
  and IP.


  chris@ubuntulocal:~$ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago
Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
Tasks: 0 (limit: 18899)
   Memory: 4.0K
  CPU: 418us
   CGroup: /system.slice/ssh.socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04

2022-10-24 Thread Steve Langasek
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: /lib/systemd/systemd-sysv-install disable ssh
> Removed "/etc/systemd/system/sshd.service".
> Removed "/etc/systemd/system/multi-user.target.wants/ssh.service".
> Created symlink /etc/systemd/system/sockets.target.wants/ssh.socket → 
> /lib/systemd/system/ssh.socket.
> rescue-ssh.target is a disabled or a static unit not running, not starting it.
> Failed to restart ssh.socket: Unit ssh.socket has a bad unit file setting.
> See system logs and 'systemctl status ssh.socket' for details.
> Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
> dpkg: error processing package openssh-server (--configure):
>  installed openssh-server package post-installation script subprocess 
> returned error exit status 1

I will try to reproduce this here, but please also attach the contents
of /etc/systemd/system/ssh.socket.d from the affected system.

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Critical

** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

-- 
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/1993869

Title:
  openssh-server cannot listen or bind to anything other than :::2 after
  upgrading to 22.10 from 22.04

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  This is a bug report to separate the second issue that was reported in this 
bug report:
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478

  There's an issue after upgrading to 22.10 from 22.04 that prevents
  opensshd from listening to anything other than :::2. I already
  commented in the bug report I linked, so I'll just copy/paste and add
  some details. I guess.

  The issue is that after upgrading, sshd doesn't use the Listen port or
  ListenAddress config from the sshd_config file or any custom config
  file that was in the sshd_config.d drop in folder anymore.

  Other drop in settings from sshd.config.d seem to be applied normally,
  the issue seem to be only for IP binding and custom ports.

  If I change Accept=no by Accept=yes in ssh.socket and reloads the
  socket unit, I can start sshd on a different port and I can also bind
  the IP to something else than ::

  There's an issue still, an instance of sshd is still listening to
  :::22 that is not started by SSHD but by init.

  root@ubuntulocal:~# netstat -antp
  Active Internet connections (servers and established)
  Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
  tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd
  tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin
  tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts
  tcp6 0 0 :::22 :::* LISTEN 1/init

  If I reboot after changing this no to yes in ssh.socket does not survive a 
reboot and fails to load sshd with a "Failed to queue service startup job" 
error.
  Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service 
startup job (Maybe the service file is missing or not a template unit?): 
Invalid argument
  Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 
'resources'.

  I had to mask/stop the sshd.socket unit and create a custom sshd
  service in /etc/systemd/system to be able start sshd on a custom port
  and IP.


  chris@ubuntulocal:~$ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago
Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
Tasks: 0 (limit: 18899)
   Memory: 4.0K
  CPU: 418us
   CGroup: /system.slice/ssh.socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-10-21 Thread Steve Langasek
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 service -> systemctl start ssh.service

Please file a separate bug report for your upgrade issue, including upgrade
logs.  It is not clear that what you are describing is the "same issue".

-- 
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 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  update failed...

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 
xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat 
xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp 
nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc 
nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 
pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr 
ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables 
autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor 
raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm 
drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds 
fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi 
mac_hid
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Oct 19 08:41:28 2022
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2019-08-13 (1162 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: 
»installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1969709] Re: libreoffice font selection unusably slow

2022-10-21 Thread Steve Langasek
** 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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1969709

Title:
  libreoffice font selection unusably slow

Status in fontconfig package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-10-20 Thread Steve Langasek
** 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 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  update failed...

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 
xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat 
xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp 
nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc 
nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 
pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr 
ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables 
autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor 
raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm 
drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds 
fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi 
mac_hid
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Oct 19 08:41:28 2022
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2019-08-13 (1162 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: 
»installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-10-19 Thread Steve Langasek
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 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 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  update failed...

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 
xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat 
xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp 
nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc 
nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 
pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr 
ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables 
autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor 
raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm 
drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds 
fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi 
mac_hid
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Oct 19 08:41:28 2022
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2019-08-13 (1162 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: 
»installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-10-19 Thread Steve Langasek
> sshdconfig.txt actually does NOT contain a line with Port 22 (it is
commented out)

Why do you mention this? I don't see anything in the log file that
mentions Port settings.

Your dpkg log shows:

> Failed to restart ssh.socket: Unit ssh.socket has a bad unit file setting.
> See system logs and 'systemctl status ssh.socket' for details.
> Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
> dpkg: Fehler beim Bearbeiten des Paketes openssh-server (--configure):
>  »installiertes post-installation-Skript des Paketes 
> openssh-server«-Unterprozess gab den > Fehlerwert 1 zurück

Can you run this 'systemctl status ssh.socket' command and attach the
output?

For developer reference, the logs show this is an upgrade from the jammy
version of openssh-server package to 1:9.0p1-1ubuntu7 in kinetic.

** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

-- 
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 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  update failed...

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 
xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat 
xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp 
nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc 
nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 
pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr 
ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables 
autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor 
raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm 
drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds 
fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi 
mac_hid
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Oct 19 08:41:28 2022
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2019-08-13 (1162 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: 
»installiertes post-installation-Skript des Paketes 
openssh-server«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes

2022-10-18 Thread Steve Langasek
** Summary changed:

- ZFS + Encryption installations of Ubuntu Desktop suffer various severe 
problems related to the package manager
+ ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on 
first boot, systemd unmounts many of the zfs volumes

-- 
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/1993318

Title:
  ZFS + Encryption installations of Ubuntu Desktop do not come up
  correctly on first boot, systemd unmounts many of the zfs volumes

Status in snapd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  New
Status in zsys package in Ubuntu:
  Invalid

Bug description:
  This is *probably* the wrong package, but it's the best I can figure
  for this, so here goes.

  Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core
  i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM,
  50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO.

  Steps to reproduce:

  1. Boot the Ubuntu desktop ISO.
  2. Select "Install Ubuntu" and proceed with the installation process.
  3. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
  4. Proceed with the rest of the installation as normal.
  5. Reboot into the newly installed system.
  6. Log in.
  7. Run "sudo apt update" in a terminal.

  Expected result: The package database should be updated normally.

  Actual result: You are presented with the following errors at the end
  of the apt output:

  Reading package lists... Error!
  E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or 
directory)
  E: Could not open file  - open (2: No such file or directory)
  E: Problem opening 
  E: The package lists or status file could not be parsed or opened.

  
  Notes: Switching to a TTY will print a crash error message related to the 
same missing /var/lib/dpkg/status file. Running "sudo touch 
/var/lib/dpkg/status" will allow "sudo apt update" to function and fix the 
crashed process in the TTY.

  Once you log in, you'll notice that Firefox is missing (bug #1993279),
  and you will likely be presented with a ton of error messages and
  other scary junk. At least one of those error messages was related to
  update-manager in my experience, and another one was from "check-new-
  release-gtk".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 18 09:55:27 2022
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1993318/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993084] Re: libkrb5-dev: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

2022-10-17 Thread Steve Langasek
*** This bug is a duplicate of bug 1980494 ***
https://bugs.launchpad.net/bugs/1980494

thanks for the update.  That makes this a duplicate of bug #1980494.

** This bug has been marked a duplicate of bug 1980494
   krb5-multidev is not multi-arch installable due to differences in 
/usr/bin/krb5-config.mit

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1993084

Title:
  libkrb5-dev:  dpkg-deb: error: paste subprocess was killed by signal
  (Broken pipe)

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

  Installation fails with this message:

  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  I had tried to install this package as a dependency of building Wine
  from source:

  configure: libkrb5 32-bit/64-bit development files not found (or too
  old), Kerberos won't be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1993084/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993084] Re: libkrb5-dev: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

2022-10-17 Thread Steve Langasek
Also this appears to be hand-transcribed from the actual error message
(there is no such thing as a "paste subprocess").  Please copy and paste
error messages to avoid introducing such mistakes.

What is normally useful here is to attach /var/log/apt/term.log from the
affected system.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1993084

Title:
  libkrb5-dev:  dpkg-deb: error: paste subprocess was killed by signal
  (Broken pipe)

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

  Installation fails with this message:

  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  I had tried to install this package as a dependency of building Wine
  from source:

  configure: libkrb5 32-bit/64-bit development files not found (or too
  old), Kerberos won't be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1993084/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2022-10-17 Thread Steve Langasek
** Changed in: fetchmail (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: freedombox-setup (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: open-iscsi (Ubuntu)
   Status: Triaged => Invalid

** Changed in: openvpn (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: pppconfig (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: pump (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: unbound (Ubuntu)
   Status: Triaged => Invalid

** Changed in: whereami (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1713803

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Invalid
Status in avahi package in Ubuntu:
  Invalid
Status in bind9 package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Invalid
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Invalid
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Invalid
Status in freedombox-setup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Invalid
Status in openvpn package in Ubuntu:
  Invalid
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Invalid
Status in pump package in Ubuntu:
  Invalid
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Invalid
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Invalid

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2022-10-16 Thread Steve Langasek
** Changed in: dnscrypt-proxy (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1713803

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Invalid
Status in avahi package in Ubuntu:
  Invalid
Status in bind9 package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Invalid
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Invalid
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Invalid
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Triaged
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2022-10-16 Thread Steve Langasek
The resolvconf interface is now implemented in the systemd-resolved
package and integrates correctly with systemd.  There is no longer a
need for packages to port away from this interface.

** Changed in: android-androresolvd (Ubuntu)
   Status: Triaged => Invalid

** Changed in: avahi (Ubuntu)
   Status: Triaged => Invalid

** Changed in: bind9 (Ubuntu)
   Status: Triaged => Invalid

** Changed in: dhcpcd5 (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1713803

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Invalid
Status in avahi package in Ubuntu:
  Invalid
Status in bind9 package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Invalid
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Triaged
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

2022-10-16 Thread Steve Langasek
Upon further inspection, it turns out that systemd-resolved now
implements the resolvconf interface.  We should drop resolvconf and
openresolv now from the archive, and users requesting resolvconf will be
directed to systemd-resolved.  Packages which depend/recommend systemd-
resolved will also get the supported implementation going forward.

Using this bug for the removal of resolvconf and openresolv.

** Changed in: resolvconf (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: resolvconf (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- resolvconf install fails upgrading from Jammy to Kinetic
+ RM: resolvconf, openresolv (and blacklist)

** Description changed:

+ systemd-resolved now implements the resolvconf interface, and Conflicts:
+ with other implementations of resolvconf.  Installing these other
+ implementations on a full system or container will wrongly result in
+ removal of the systemd-resolved package.  We should drop resolvconf and
+ openresolv now from the archive (and blacklist them).  Users requesting
+ resolvconf will be directed to systemd-resolved. Packages which
+ depend/recommend systemd-resolved will also get the supported
+ implementation going forward.
+ 
+ [Original description]
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
-  installed resolvconf package post-installation script subprocess returned 
error exit status 1
+  installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
-  resolvconf
+  resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
- $ ls -l /etc/resolvconf/resolv.conf.d/original 
+ $ ls -l /etc/resolvconf/resolv.conf.d/original
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

** Also affects: openresolv (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1990743

Title:
  RM: resolvconf, openresolv (and blacklist)

Status in openresolv package in Ubuntu:
  Fix Released
Status in resolvconf package in Ubuntu:
  Fix Released

Bug description:
  systemd-resolved now implements the resolvconf interface, and
  Conflicts: with other implementations of resolvconf.  Installing these
  other implementations on a full system or container will wrongly
  result in removal of the systemd-resolved package.  We should drop
  resolvconf and openresolv now from the archive (and blacklist them).
  Users requesting resolvconf will be directed to systemd-resolved.
  Packages which depend/recommend systemd-resolved will also get the
  supported implementation going forward.

  [Original description]
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  

[Touch-packages] [Bug 1990743] Re: RM: resolvconf, openresolv (and blacklist)

2022-10-16 Thread Steve Langasek
Removing packages from kinetic:
openresolv 3.12.0-2 in kinetic
openresolv 3.12.0-2 in kinetic amd64
openresolv 3.12.0-2 in kinetic arm64
openresolv 3.12.0-2 in kinetic armhf
openresolv 3.12.0-2 in kinetic i386
openresolv 3.12.0-2 in kinetic ppc64el
openresolv 3.12.0-2 in kinetic riscv64
openresolv 3.12.0-2 in kinetic s390x
resolvconf 1.91ubuntu1 in kinetic
resolvconf 1.91ubuntu1 in kinetic amd64
resolvconf 1.91ubuntu1 in kinetic arm64
resolvconf 1.91ubuntu1 in kinetic armhf
resolvconf 1.91ubuntu1 in kinetic i386
resolvconf 1.91ubuntu1 in kinetic ppc64el
resolvconf 1.91ubuntu1 in kinetic riscv64
resolvconf 1.91ubuntu1 in kinetic s390x
Comment: Conflicts with systemd-resolved, which is now the preferred 
implementation as of kinetic; LP: #1990743
2 packages successfully removed.


** Changed in: resolvconf (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: openresolv (Ubuntu)
   Status: New => Fix Released

** Changed in: openresolv (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1990743

Title:
  RM: resolvconf, openresolv (and blacklist)

Status in openresolv package in Ubuntu:
  Fix Released
Status in resolvconf package in Ubuntu:
  Fix Released

Bug description:
  systemd-resolved now implements the resolvconf interface, and
  Conflicts: with other implementations of resolvconf.  Installing these
  other implementations on a full system or container will wrongly
  result in removal of the systemd-resolved package.  We should drop
  resolvconf and openresolv now from the archive (and blacklist them).
  Users requesting resolvconf will be directed to systemd-resolved.
  Packages which depend/recommend systemd-resolved will also get the
  supported implementation going forward.

  [Original description]
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openresolv/+bug/1990743/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

2022-10-11 Thread Steve Langasek
> It's no skin off my nose—if it's deprecated I'll
> find something else to use—but it seems to me that
> if you're going to keep the package in the repository
> you should fix bugs in it.

Can you provide a full upgrade log for the affected system?  systemd in
kinetic Recommends: systemd-resolved, which Conflicts: with resolvconf.
So the expected effect on upgrade is that resolvconf be removed in favor
of systemd-resolved.

So, the preferred way to handle bugs in the resolvconf package is to
remove it.  It just hasn't been removed from the archive yet because
there are reverse-dependencies inherited from Debian to be sorted
through.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1990743

Title:
  resolvconf install fails upgrading from Jammy to Kinetic

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original 
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

2022-10-11 Thread Steve Langasek
** Tags added: foundations-triage-discuss

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1990743

Title:
  resolvconf install fails upgrading from Jammy to Kinetic

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original 
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991771] Re: [FFe] Update to 3.0.6

2022-10-07 Thread Steve Langasek
Given the late glibc change now in flight, I do not think we have the
capacity to take an openssl change this late in the release cycle
without significantly taxing the team to make the release happen.
Especially since the security fixes are low impact and the upstream
release is not security-fix-only, I definitely do not think we can grant
a freeze exception at this point, and think the chances of granting one
on Tuesday when the upstream release has happened are low.  I would
advise that you work with the Security Team to work out what a zero-day
security update of this package should look like.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1991771

Title:
  [FFe] Update to 3.0.6

Status in openssl package in Ubuntu:
  New

Bug description:
  There's an upcoming security release for OpenSSL according to
  https://mta.openssl.org/pipermail/openssl-
  users/2022-October/015477.html

  The timing is somewhat unfortunate given our own release schedule.

  The current version of openssl in kinetic, 3.0.5-2ubuntu1, is actually
  a snapshot of the 3.0 branch ahead of 3.0.5 (inherited from Debian
  during the last merge).

  Sadly, they don't have a proper changelog (even partial) for the
  upcoming release yet, but I'll attach the diff and shortlog between
  our current version and the current state of the branch to get an idea
  of what's to come. As usual for their 3.0 point releases, it's not
  just security fixes but general bugfixes as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1991771/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

2022-10-06 Thread Steve Langasek
On Thu, Oct 06, 2022 at 07:32:54AM -, msaxl wrote:
> I think the biggest issue is the automatic upgrade from "classic" to
> systemd.socket

> It is very hard to consistently migrate every configuration.

> I was hit by this issue because I had set
> /proc/sys/net/ipv6/bindv6only=1, so ipv4 was disabled

Please file a separate bug explaining exactly what problem you encountered
on upgrade.  Setting /proc/sys/net/ipv6/bindv6only=1 (which is not something
I consider a sensible deviation from the Ubuntu defaults) should not have
caused you to experience upgrade issues, and is independent from the
question of using a generator.

-- 
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/1991592

Title:
  openssh-server should ship a systemd generator to generate ssh socket
  port configuration from sshd_config

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  A criticism of the existing sshd socket activation implementation is
  that Port/ListenAddress options are migrated on a one-time basis at
  package upgrade time, and afterwards users get the surprising behavior
  that Port/ListenAddress settings added to sshd_config are ignored.

  A systemd generator could be used to change the ssh socket unit
  configuration on boot, and on each change of /etc/ssh/sshd_config.
  Sample implementation from Dimitri:

  ssh.socket:
  [Unit]
  Wants=sshd-config.path

  #
  # Note the below defaults are cleared and overriden by
  #/lib/systemd/system-generators/sshd-generator
  # based on the sshd config from the sshd -T output
  #
  ListenStream=[::]:22
  ListenStream=0.0.0.0:22

  diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path
  new file mode 100644
  index 0..cfa9674a3
  --- /dev/null
  +++ b/systemd/sshd-config.path
  @@ -0,0 +1,4 @@
  +[Unit]
  +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
  +[Path]
  +PathChanged=/etc/ssh/sshd_config
  diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service
  new file mode 100644
  index 0..b009ea52c
  --- /dev/null
  +++ b/systemd/sshd-config.service
  @@ -0,0 +1,5 @@
  +[Unit]
  +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in
  +
  +[Service]
  +ExecStart=/bin/systemctl daemon-reload
  diff --git a/systemd/sshd-generator b/systemd/sshd-generator
  new file mode 100755
  index 0..72c6aac04
  --- /dev/null
  +++ b/systemd/sshd-generator
  @@ -0,0 +1,10 @@
  +#!/bin/sh
  +set -eu
  +mkdir -p /run/sshd
  +sshd -t
  +mkdir -p $1/ssh.socket.d
  +target="$1/ssh.socket.d/ssh-listen.conf"
  +echo '[Socket]' > $target
  +echo 'ListenStream=' >> $target
  +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target
  +rmdir --ignore-fail-on-non-empty /run/sshd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

2022-10-06 Thread Steve Langasek
On Thu, Oct 06, 2022 at 02:34:40PM -, Corey Reichle wrote:
> Nowhere was it documented that sshd now needs two configuration files,
> just to tell it to listen on a port, and address it was already told to
> do.

False.  It is documented in the manpage, in the default sshd_config file
shipped in the package, and in the kinetic release notes.

-- 
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/1991592

Title:
  openssh-server should ship a systemd generator to generate ssh socket
  port configuration from sshd_config

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  A criticism of the existing sshd socket activation implementation is
  that Port/ListenAddress options are migrated on a one-time basis at
  package upgrade time, and afterwards users get the surprising behavior
  that Port/ListenAddress settings added to sshd_config are ignored.

  A systemd generator could be used to change the ssh socket unit
  configuration on boot, and on each change of /etc/ssh/sshd_config.
  Sample implementation from Dimitri:

  ssh.socket:
  [Unit]
  Wants=sshd-config.path

  #
  # Note the below defaults are cleared and overriden by
  #/lib/systemd/system-generators/sshd-generator
  # based on the sshd config from the sshd -T output
  #
  ListenStream=[::]:22
  ListenStream=0.0.0.0:22

  diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path
  new file mode 100644
  index 0..cfa9674a3
  --- /dev/null
  +++ b/systemd/sshd-config.path
  @@ -0,0 +1,4 @@
  +[Unit]
  +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
  +[Path]
  +PathChanged=/etc/ssh/sshd_config
  diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service
  new file mode 100644
  index 0..b009ea52c
  --- /dev/null
  +++ b/systemd/sshd-config.service
  @@ -0,0 +1,5 @@
  +[Unit]
  +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in
  +
  +[Service]
  +ExecStart=/bin/systemctl daemon-reload
  diff --git a/systemd/sshd-generator b/systemd/sshd-generator
  new file mode 100755
  index 0..72c6aac04
  --- /dev/null
  +++ b/systemd/sshd-generator
  @@ -0,0 +1,10 @@
  +#!/bin/sh
  +set -eu
  +mkdir -p /run/sshd
  +sshd -t
  +mkdir -p $1/ssh.socket.d
  +target="$1/ssh.socket.d/ssh-listen.conf"
  +echo '[Socket]' > $target
  +echo 'ListenStream=' >> $target
  +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target
  +rmdir --ignore-fail-on-non-empty /run/sshd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

2022-10-06 Thread Steve Langasek
** Tags removed: rls-kk-incoming
** Tags added: rls-kk-notfix

** Tags removed: rls-kk-notfix
** Tags added: rls-kk-notfixing

-- 
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/1795278

Title:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Focal:
  Triaged
Status in software-properties source package in Jammy:
  Triaged
Status in software-properties source package in Kinetic:
  Triaged

Bug description:
  Release: Kubuntu 18.04
  Version: 0.96.24.32.1

  When clicking the "Import Key" button in the "Authentication" section
  of the panel it throws this error:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
 line 667, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  While this doesn't crash the program it causes nothing to happen when
  clicking the button. Running the program in a terminal reveals the
  error being printed to stderr.

  After debugging it appears KUrl doesn't exist anywhere and I'm not
  sure if's a python module that has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1971901] Re: dlltool uses non-unique temp filenames

2022-10-05 Thread Steve Langasek
** Changed in: binutils-mingw-w64 (Ubuntu)
   Status: Fix Released => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1971901

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils-mingw-w64 package in Ubuntu:
  Triaged
Status in binutils source package in Jammy:
  Fix Committed
Status in binutils-mingw-w64 source package in Jammy:
  Triaged

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

  /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec
  Assembler messages:
  Error: can't open winmm_dll_t.s for reading: No such file or directory
  /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited 
with status 1
  /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
  winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
  make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
  make: *** Waiting for unfinished jobs
  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec

  Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for
  it's temp file - these are not unique when building libwinmm.delay.a
  and libwinmm.cross.a in parallel. (This can of course affect any dll
  wine is building import libs for, winmm is just the one I happaned to
  get caught on).

  This is regression newly introduced in binutils 2.38 vs older versions
  which used getpid() as the basis of their temp name. We just
  encountered it as part of updating our CI for a winelib application
  from focal to jammy, but it seems to have been discovered by others
  already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885

  There is an upstream fix on master (2.39) which is already backported
  to the binutils-2_38 branch:
  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just
  be a matter of cherry-picking. Hopefully the fact it's a regression
  from impish->jammy and that upstream already backported it to 2.38
  might make this a candidate for jammy-updates?

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991661] Re: systemd mounts /run without noexec

2022-10-04 Thread Steve Langasek
The initramfs-tools behavior is longstanding and deliberate; the systemd
behavior is the buggy deviation.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Tags added: foundations-todo

-- 
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/1991661

Title:
  systemd mounts /run without noexec

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  initramfs-tools in Bionic+, when mounting the filesystem, mounts /run
  with noexec

  Cloud images run without initramfs and rely on systemd for the mounts.
  systemd, however, mounts /run without noexec. Snip from mount-setup.c
  (either in src/core/mount-setup.c < 248 or src/shared/mount-setup.c in
  >= 248 )

  ```
  #if ENABLE_SMACK
  { "tmpfs",   "/run",  "tmpfs",  
"mode=755,smackfsroot=*" TMPFS_LIMITS_RUN, MS_NOSUID|MS_NODEV|MS_STRICTATIME,
mac_smack_use, MNT_FATAL  },
  #endif
  { "tmpfs",   "/run",  "tmpfs",  
"mode=755" TMPFS_LIMITS_RUN,   MS_NOSUID|MS_NODEV|MS_STRICTATIME,
NULL,  MNT_FATAL|MNT_IN_CONTAINER },
  ```

  Originally raised in an askubuntu forum: 
  https://askubuntu.com/questions/1432383/mounting-run-as-noexec/1433208

  CPC hasn't received word from any partners yet, but it does constitute
  a possible regression from how the system was mounted in Bionic and
  Focal before moving to optimized boots in 2020/2021.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991661/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991491] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert

2022-10-03 Thread Steve Langasek
This bug report shows that you were doing a release upgrade from 20.04
to 22.04 on a system which has a separate /boot partition, 461MiB in
size with 81MiB free space; and the system ran out of room while trying
to write out the initramfs for the new kernel.

461MiB is unfortunately on the small size now for /boot partitions given
the size of recent kernels / initramfses.

Were you using update-manager (the recommended interface, on desktop
systems) to do the upgrade?  It includes checks to ensure /boot is large
enough before committing to the upgrade, so we would want to know if
those checks were inadequate here.

** Package changed: initramfs-tools (Ubuntu) => ubuntu-release-upgrader
(Ubuntu)

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Incomplete

-- 
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/1991491

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  »installiertes initramfs-tools-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  I undated from 20.04.5 to 22.04.1 and this is what the update ended
  with.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
  Uname: Linux 5.4.0-126-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Oct  2 19:06:19 2022
  ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2017-06-03 (1946 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1991491/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991566] Re: Package creates a socket file for all addresses of all families, even when bind to a single address

2022-10-03 Thread Steve Langasek
*** This bug is a duplicate of bug 1991592 ***
https://bugs.launchpad.net/bugs/1991592

** This bug has been marked a duplicate of bug 1991592
   openssh-server should ship a systemd generator to generate ssh socket port 
configuration from sshd_config

-- 
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/1991566

Title:
  Package creates a socket file for all addresses of all families, even
  when bind to a single address

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am configuring OpenSSH to listen only on ipv4 and only on one
  interface and one address, with nginx listening on 22 on the other
  interface, and families.

  In order to make this happen, I had to "break" the socket file
  installed by the package at:

  /etc/systemd/system/sockets.target.wants/ssh.socket

  To read as follows:

  [Unit]
  Description=OpenBSD Secure Shell server socket
  Before=ssh.service
  Conflicts=ssh.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  #[Socket]
  #ListenStream=22
  #Accept=yes

  #[Install]
  #WantedBy=sockets.target

  (Commented out the lines that installed the socket)

  Then a daemon-reload, and restart of ngxinx, and all components of the
  solution are working as required.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-server 1:8.9p1-3 [modified: lib/systemd/system/ssh.socket]
  ProcVersionSignature:
   
  Uname: Linux 5.15.53-1-pve x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct  3 16:36:37 2022
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991566/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991477] Re: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-10-03 Thread Steve Langasek
The error in your log is:

Processing triggers for linux-image-5.15.0-48-generic (5.15.0-48.54) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-5.15.0-48-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

This is not a bug in initramfs-tools, per se; initramfs-tools can't make
your root partition larger than it is.  And you do not have a separate
/boot partition, so this is not a bug of an installer setting up /boot
to be an inappropriate size.  The only thing that can be done in this
circumstance is for you to free up some space on your root partition and
try to resume the upgrade with 'apt -f install'.

Were you running apt dist-upgrade manually to go from focal to jammy, or
were you using do-release-upgrade, the recommended tool?  The release
upgrader includes some checks to ensure sufficient free space before
committing to the upgrade, so we would want to know if those are
inadequate.

** Package changed: initramfs-tools (Ubuntu) => ubuntu-release-upgrader
(Ubuntu)

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Incomplete

-- 
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/1991477

Title:
  package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  Trying to upgrade to the latest image.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-48-generic 5.15.0-48.54
  ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
  Uname: Linux 5.4.0-126-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  2 01:45 seq
   crw-rw 1 root audio 116, 33 Oct  2 01:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sun Oct  2 01:51:16 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: DigitalOcean Droplet
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic 
root=UUID=db153994-91fe-426f-bd88-f751e07f97f2 ro console=tty1 console=ttyS0
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1991477/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991436] Re: "invalid argument" error from logger command when passing messages via STDIN

2022-10-03 Thread Steve Langasek
I cannot reproduce this on jammy.

$ echo "some message" | logger -p auth.info --id="$$"
$ echo $?
0
$

(using auth.info instead of local0.info because I have the former logged
to a log file and the latter not).

** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991436

Title:
  "invalid argument" error from logger command when passing messages via
  STDIN

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  When invoking the `logger` command on Ubuntu Jammy (bsdutils 2.37.2)
  with explicit PID and passing messages via STDIN

  ```
  echo "some message" | logger -p local0.info --id="$$"
  ```

  the command produces the following error instead of sending the
  message to syslog:

  > logger: send message failed: Invalid argument

  The error does not appear when the message is passed as an argument:

  ```
  logger -p local0.info --id="$$" "some message"  # this works!
  ```

  When using process substitution the error only appears for the first
  log message:

  ```
  exec > >(logger -p local0.info --id="$$")
  echo "first message"   # throws error, message not logged
  echo "second message"  # no error, message logged correctly
  ```

  The issue does not exist in older versions (e.g. Ubuntu Xenial,
  bsdutils 2.27.1).

  Workaround: Omit `--id` and include the PID in a tag.

  ```
  echo "some message" | logger -p local0.info -t "foo[$$]"
  ```

  Expected Behavior
  -

  All messages passed via STDIN should be sent to syslog without
  throwing an error.

  OS Release
  --

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  Package Version
  ---

  bsdutils:
    Installed: 2.37.2-4ubuntu3
    Candidate: 2.37.2-4ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1991436/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991324] Re: Initramfs-tools: iSCSI boot resulting in error message about not finding executables

2022-10-03 Thread Steve Langasek
Also, as this is an rpi4, is this running the armhf port or the arm64
port? (32 or 64 bit)

-- 
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/1991324

Title:
  Initramfs-tools: iSCSI boot resulting in error message about not
  finding executables

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  My RPi4's are having their rootvg on iSCSI and boot from them. The
  kernel modules etc are in the initramfs. However since 22.04 the
  initramfs is not generated corrected and while booting from it it
  results in error messages stating various binaries/scripts are not
  locatable.

  E.g. modprobe, systemd-udev, mdadm etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991324] Re: Initramfs-tools: iSCSI boot resulting in modprobe not found error message

2022-10-03 Thread Steve Langasek
> Loading, please wait...
> /scripts/init-top/udev: line 24: /lib/systemd/systemd-udevd: not found
> Begin: Loading essential drivers ... /init: line 150: modprobe: not found
> /init: line 150: modprobe: not found

So basically, none of the binaries are in the initramfs, or else they're
in the initramfs but not on the PATH.  How was this initramfs generated?
Please attach to this bug report.

** Summary changed:

- Initramfs-tools: iSCSI boot resulting in modprobe not found error message
+ Initramfs-tools: iSCSI boot resulting in error message about not finding 
executables

-- 
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/1991324

Title:
  Initramfs-tools: iSCSI boot resulting in error message about not
  finding executables

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  My RPi4's are having their rootvg on iSCSI and boot from them. The
  kernel modules etc are in the initramfs. However since 22.04 the
  initramfs is not generated corrected and while booting from it it
  results in error messages stating various binaries/scripts are not
  locatable.

  E.g. modprobe, systemd-udev, mdadm etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991283] Re: "sshd -i" breaks due to socket activation

2022-10-03 Thread Steve Langasek
** 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.
https://bugs.launchpad.net/bugs/1991283

Title:
  "sshd -i" breaks due to socket activation

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  On Jammy and earlier, simply running "sshd -i" worked.

  Now, it fails silently, and running it with "-d" gives me:

  Missing privilege separation directory: /run/sshd

  This directory is normally created with "RuntimeDirectory=sshd" as
  defined in /lib/systemd/system/ssh.service. In Jammy, this directory
  got created by the ssh service starting at boot, so "sshd -i" worked.

  Now, with socket activation, it no longer does that, so "sshd -i"
  fails unless someone has actually connected on TCP port 22 (which they
  often won't have, since that's the point of "sshd -i").

  systemd will then remove /run/sshd when the ssh service is stopped. I
  think maybe this won't interfere with an existing "sshd -i", but it's
  not really clean. Further, the privilege separation directory doesn't
  appear to be configurable - at least I couldn't find any mention in
  sshd_config(5).

  The workaround is to "mkdir -p /run/sshd && sshd -i" instead.

  Given that "sshd -i"'s use of /run/sshd isn't really related to the
  systemd service, maybe we should move the creation of that directory
  into tmpfiles.d instead?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991283/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1971901] Re: dlltool uses non-unique temp filenames

2022-10-03 Thread Steve Langasek
** Changed in: binutils-mingw-w64 (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: binutils-mingw-w64 (Ubuntu)
   Importance: Undecided => Low

** Changed in: binutils (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: binutils-mingw-w64 (Ubuntu)
   Status: Triaged => Fix Released

** Also affects: binutils (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: binutils-mingw-w64 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: binutils (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: binutils (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: binutils-mingw-w64 (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: binutils-mingw-w64 (Ubuntu Jammy)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1971901

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils-mingw-w64 package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  Fix Committed
Status in binutils-mingw-w64 source package in Jammy:
  Triaged

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

  /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec
  Assembler messages:
  Error: can't open winmm_dll_t.s for reading: No such file or directory
  /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited 
with status 1
  /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
  winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
  make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
  make: *** Waiting for unfinished jobs
  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec

  Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for
  it's temp file - these are not unique when building libwinmm.delay.a
  and libwinmm.cross.a in parallel. (This can of course affect any dll
  wine is building import libs for, winmm is just the one I happaned to
  get caught on).

  This is regression newly introduced in binutils 2.38 vs older versions
  which used getpid() as the basis of their temp name. We just
  encountered it as part of updating our CI for a winelib application
  from focal to jammy, but it seems to have been discovered by others
  already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885

  There is an upstream fix on master (2.39) which is already backported
  to the binutils-2_38 branch:
  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just
  be a matter of cherry-picking. Hopefully the fact it's a regression
  from impish->jammy and that upstream already backported it to 2.38
  might make this a candidate for jammy-updates?

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

2022-10-03 Thread Steve Langasek
** Tags added: foundations-todo

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1973470

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged
Status in xdg-utils package in Ubuntu:
  Invalid

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1973470/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871392] Re: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup'

2022-10-03 Thread Steve Langasek
And the bug report shows this crash happened with python3-apt 1.9.10,
which was a prerelease version of python3-apt before Ubuntu 20.04 LTS
came out.  So I'm surprised another user has just marked this bug as
affecting them, causing the report to bubble up to the top.  We would
need some concrete evidence that this failure happens with released
versions of the software to take further action here.

** Changed in: python-apt (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1871392

Title:
  update-manager crashed with AttributeError in _records(): 'NoneType'
  object has no attribute 'lookup'

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  System locked up

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: update-manager 1:20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Aptdaemon:
   
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 09:16:14 2020
  ExecutablePath: /usr/bin/update-manager
  InstallationDate: Installed on 2020-03-01 (36 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']
  PythonDetails: N/A
  SourcePackage: update-manager
  Title: update-manager crashed with AttributeError in _records(): 'NoneType' 
object has no attribute 'lookup'
  UpgradeStatus: Upgraded to focal on 2020-03-25 (12 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871392/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871392] Re: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup'

2022-10-03 Thread Steve Langasek
The stacktrace points to:

  File "/usr/lib/python3/dist-packages/apt/package.py", line 541, in _records
if not self.package._pcache._records.lookup(self._cand.file_list[0]):
AttributeError: 'NoneType' object has no attribute 'lookup'

So, reassigning.

** Package changed: update-manager (Ubuntu) => python-apt (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1871392

Title:
  update-manager crashed with AttributeError in _records(): 'NoneType'
  object has no attribute 'lookup'

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  System locked up

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: update-manager 1:20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Aptdaemon:
   
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 09:16:14 2020
  ExecutablePath: /usr/bin/update-manager
  InstallationDate: Installed on 2020-03-01 (36 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']
  PythonDetails: N/A
  SourcePackage: update-manager
  Title: update-manager crashed with AttributeError in _records(): 'NoneType' 
object has no attribute 'lookup'
  UpgradeStatus: Upgraded to focal on 2020-03-25 (12 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871392/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-10-03 Thread Steve Langasek
** Changed in: grub2-signed (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my 

[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic

2022-10-03 Thread Steve Langasek
** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991199

Title:
  sshd port migration is missing two config lines from jammy to kinetic

Status in openssh package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The automatic migration script from jammy to kinetic generates a
  invalid file for sshd that systemd refuses to read. Manual addition of
  two lines is required for a functional sshd with a custom port.

  This bug can be considered the opposite of
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They
  want to have sshd keep managing the socket while I want to try letting
  systemd do that.

  $ lsb_release -rd
  Description:Ubuntu Kinetic Kudu (development branch)
  Release:22.10

  $ apt-cache policy openssh-server
  openssh-server:
    Installed: 1:9.0p1-1ubuntu6
    Candidate: 1:9.0p1-1ubuntu6
    Version table:
   *** 1:9.0p1-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy systemd
  systemd:
    Installed: 251.4-1ubuntu6
    Candidate: 251.4-1ubuntu6
    Version table:
   *** 251.4-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  # Instructions

  - Configure /etc/ssh/sshd_config to port  in 22.04
  - Upgrade to 22.10 with sudo do-release-upgrade -d
  - Accept overwriting /etc/ssh/sshd_config with the new version
  - Attempt to ssh into the machine

  # Expected behavior

  systemd should listen on port  and start sshd.

  $ cat /etc/systemd/system/ssh.socket.d/addresses.conf
  [Socket]
  ListenStream=
  ListenStream=

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago
    Until: Thu 2022-09-29 02:08:56 EDT; 9min ago
     Triggers: ● ssh.service
   Listen: [::]: (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 923us
   CGroup: /system.slice/ssh.socket

  Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD
  Secure Shell server socket.

  # Actual behavior

  Port  refuses any connection. Systemd fails to parse the
  automatically generated file:

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago
    Until: Thu 2022-09-29 01:51:57 EDT; 16min ago
     Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 982us
   CGroup: /system.slice/ssh.socket

  Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell 
server socket.
  Sep 29 01:56:23 daniel-desktop2 systemd[1]: 
/etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of 
section. Ignoring.

  $ cat /etc/systemd/system/ssh.socket.d/override.conf
  ListenStream=

  # Analysis

  The migration script must be missing the `[Socket]` line and the next one. 
sshd works after I added those two lines manually. Either the migration script 
never worked or systemd changed the syntax in the meantime.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6
  Package: systemd 251.4-1ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic 
root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off 
resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8
  Tags:  kinetic
  Uname: Linux 6.0.0-06rc7-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K30BF_M32BF_A_F_K31BF_6
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

2022-10-03 Thread Steve Langasek
** Changed in: openssh (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: openssh (Ubuntu)
   Importance: Undecided => High

-- 
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/1991592

Title:
  openssh-server should ship a systemd generator to generate ssh socket
  port configuration from sshd_config

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  A criticism of the existing sshd socket activation implementation is
  that Port/ListenAddress options are migrated on a one-time basis at
  package upgrade time, and afterwards users get the surprising behavior
  that Port/ListenAddress settings added to sshd_config are ignored.

  A systemd generator could be used to change the ssh socket unit
  configuration on boot, and on each change of /etc/ssh/sshd_config.
  Sample implementation from Dimitri:

  ssh.socket:
  [Unit]
  Wants=sshd-config.path

  #
  # Note the below defaults are cleared and overriden by
  #/lib/systemd/system-generators/sshd-generator
  # based on the sshd config from the sshd -T output
  #
  ListenStream=[::]:22
  ListenStream=0.0.0.0:22

  diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path
  new file mode 100644
  index 0..cfa9674a3
  --- /dev/null
  +++ b/systemd/sshd-config.path
  @@ -0,0 +1,4 @@
  +[Unit]
  +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
  +[Path]
  +PathChanged=/etc/ssh/sshd_config
  diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service
  new file mode 100644
  index 0..b009ea52c
  --- /dev/null
  +++ b/systemd/sshd-config.service
  @@ -0,0 +1,5 @@
  +[Unit]
  +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in
  +
  +[Service]
  +ExecStart=/bin/systemctl daemon-reload
  diff --git a/systemd/sshd-generator b/systemd/sshd-generator
  new file mode 100755
  index 0..72c6aac04
  --- /dev/null
  +++ b/systemd/sshd-generator
  @@ -0,0 +1,10 @@
  +#!/bin/sh
  +set -eu
  +mkdir -p /run/sshd
  +sshd -t
  +mkdir -p $1/ssh.socket.d
  +target="$1/ssh.socket.d/ssh-listen.conf"
  +echo '[Socket]' > $target
  +echo 'ListenStream=' >> $target
  +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target
  +rmdir --ignore-fail-on-non-empty /run/sshd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990863] Re: conversion from sshd service to socket is too bumpy

2022-10-03 Thread Steve Langasek
*** This bug is a duplicate of bug 1991592 ***
https://bugs.launchpad.net/bugs/1991592

** This bug has been marked a duplicate of bug 1991592
   openssh-server should ship a systemd generator to generate ssh socket port 
configuration from sshd_config

-- 
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/1990863

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

Bug description:
  During upgrade from Jammy to Kinetic, I get asked what to do because
  my sshd_config has been modified. I say to do a 3-way merge. It says
  3-way merge fails. I shrug, figure I'll just restore my customizations
  with Ansible after the upgrade like I always do, and tell it to use
  the vendor version of the file. This removes my custom Port settings,
  so they are not migrated over to the ssh.socket settings like
  https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
  ubuntu-22-10-and-later/30189 says they would be. I subsequently run my
  Ansible which restores the customizations and enables the ssh service,
  but now ssh.service and ssh.socket are enabled at the same time, sshd
  isn't listening on my specified ports, and everything is a mess. I've
  never used socket-based activation before and have no idea how to
  configure it so now I have to go reading man pages, Googling all over
  the place, and generally struggle to figure out what the heck is going
  wrong.

  I don't know what the right answer is here, but I really feel like
  some effort needs to be put into figuring out a smoother transition
  for people who are upgrading to Kinetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 11:41:58 2022
  InstallationDate: Installed on 2019-08-16 (1136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991592] [NEW] openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

2022-10-03 Thread Steve Langasek
Public bug reported:

A criticism of the existing sshd socket activation implementation is
that Port/ListenAddress options are migrated on a one-time basis at
package upgrade time, and afterwards users get the surprising behavior
that Port/ListenAddress settings added to sshd_config are ignored.

A systemd generator could be used to change the ssh socket unit
configuration on boot, and on each change of /etc/ssh/sshd_config.
Sample implementation from Dimitri:

ssh.socket:
[Unit]
Wants=sshd-config.path

#
# Note the below defaults are cleared and overriden by
#/lib/systemd/system-generators/sshd-generator
# based on the sshd config from the sshd -T output
#
ListenStream=[::]:22
ListenStream=0.0.0.0:22

diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path
new file mode 100644
index 0..cfa9674a3
--- /dev/null
+++ b/systemd/sshd-config.path
@@ -0,0 +1,4 @@
+[Unit]
+ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
+[Path]
+PathChanged=/etc/ssh/sshd_config
diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service
new file mode 100644
index 0..b009ea52c
--- /dev/null
+++ b/systemd/sshd-config.service
@@ -0,0 +1,5 @@
+[Unit]
+Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in
+
+[Service]
+ExecStart=/bin/systemctl daemon-reload
diff --git a/systemd/sshd-generator b/systemd/sshd-generator
new file mode 100755
index 0..72c6aac04
--- /dev/null
+++ b/systemd/sshd-generator
@@ -0,0 +1,10 @@
+#!/bin/sh
+set -eu
+mkdir -p /run/sshd
+sshd -t
+mkdir -p $1/ssh.socket.d
+target="$1/ssh.socket.d/ssh-listen.conf"
+echo '[Socket]' > $target
+echo 'ListenStream=' >> $target
+sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target
+rmdir --ignore-fail-on-non-empty /run/sshd

** Affects: openssh (Ubuntu)
 Importance: High
 Status: 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/1991592

Title:
  openssh-server should ship a systemd generator to generate ssh socket
  port configuration from sshd_config

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  A criticism of the existing sshd socket activation implementation is
  that Port/ListenAddress options are migrated on a one-time basis at
  package upgrade time, and afterwards users get the surprising behavior
  that Port/ListenAddress settings added to sshd_config are ignored.

  A systemd generator could be used to change the ssh socket unit
  configuration on boot, and on each change of /etc/ssh/sshd_config.
  Sample implementation from Dimitri:

  ssh.socket:
  [Unit]
  Wants=sshd-config.path

  #
  # Note the below defaults are cleared and overriden by
  #/lib/systemd/system-generators/sshd-generator
  # based on the sshd config from the sshd -T output
  #
  ListenStream=[::]:22
  ListenStream=0.0.0.0:22

  diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path
  new file mode 100644
  index 0..cfa9674a3
  --- /dev/null
  +++ b/systemd/sshd-config.path
  @@ -0,0 +1,4 @@
  +[Unit]
  +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
  +[Path]
  +PathChanged=/etc/ssh/sshd_config
  diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service
  new file mode 100644
  index 0..b009ea52c
  --- /dev/null
  +++ b/systemd/sshd-config.service
  @@ -0,0 +1,5 @@
  +[Unit]
  +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in
  +
  +[Service]
  +ExecStart=/bin/systemctl daemon-reload
  diff --git a/systemd/sshd-generator b/systemd/sshd-generator
  new file mode 100755
  index 0..72c6aac04
  --- /dev/null
  +++ b/systemd/sshd-generator
  @@ -0,0 +1,10 @@
  +#!/bin/sh
  +set -eu
  +mkdir -p /run/sshd
  +sshd -t
  +mkdir -p $1/ssh.socket.d
  +target="$1/ssh.socket.d/ssh-listen.conf"
  +echo '[Socket]' > $target
  +echo 'ListenStream=' >> $target
  +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target
  +rmdir --ignore-fail-on-non-empty /run/sshd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991566] Re: Package creates a socket file for all addresses of all families, even when bind to a single address

2022-10-03 Thread Steve Langasek
Your bug report is against jammy, but socket activation is a default for
ssh only in kinetic.  Were you using ubuntu-bug from a different machine
than the one affected?

> In order to make this happen, I had to "break" the socket file
installed by the package at:

> /etc/systemd/system/sockets.target.wants/ssh.socket

So first of all, this is a symlink to a file under /lib; your changes
will be overwritten on package upgrade.

Secondly, listening on all interfaces is a default for openssh, both before and 
after the move to socket-based activation.  To configure the systemd socket 
unit to listen on a particular interface, you need only drop an override file 
in /etc/systemd/system/ssh.socket.d/ with the contents:
[Socket]
ListenStream=
ListenStream=$address:22

** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

-- 
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/1991566

Title:
  Package creates a socket file for all addresses of all families, even
  when bind to a single address

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am configuring OpenSSH to listen only on ipv4 and only on one
  interface and one address, with nginx listening on 22 on the other
  interface, and families.

  In order to make this happen, I had to "break" the socket file
  installed by the package at:

  /etc/systemd/system/sockets.target.wants/ssh.socket

  To read as follows:

  [Unit]
  Description=OpenBSD Secure Shell server socket
  Before=ssh.service
  Conflicts=ssh.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  #[Socket]
  #ListenStream=22
  #Accept=yes

  #[Install]
  #WantedBy=sockets.target

  (Commented out the lines that installed the socket)

  Then a daemon-reload, and restart of ngxinx, and all components of the
  solution are working as required.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-server 1:8.9p1-3 [modified: lib/systemd/system/ssh.socket]
  ProcVersionSignature:
   
  Uname: Linux 5.15.53-1-pve x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct  3 16:36:37 2022
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991566/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990863] Re: conversion from sshd service to socket is too bumpy

2022-10-01 Thread Steve Langasek
I don't have a complete solution to this, but I do have several points.

- debconf prompts on upgrade are not, in general, good UX.  It disrupts
the flow of the upgrade.  Sometimes it's necessary, but if all it's
doing is telling the user they *may* have a broken config after
upgrading, well, if every package for which that's true did that
upgrades would be very slow indeed.  And for users upgrading a large
number of systems, that becomes one more nuisance.  So no, I don't think
we should add a prompt on upgrade for this.  (There's also the practical
problem that if we introduced such a prompt at this point in the release
cycle, it would not realistically get translated, reducing accessibility
for our users vs communicating this in other ways that could be
localized out-of-band.)

- As Robie pointed out in comment #4, there is no guarantee that ansible 
playbooks work consistently across releases.  Regardless of whether we made 
changes that would have allowed the migration of settings in your case, if you 
had had to reinstall kinetic instead of upgrading from jammy, those changes in 
the openssh-server maintainer scripts would not have taken effect.  Your 
ansible playbook is therefore buggy wrt kinetic, and should be fixed, which is 
out of scope for Ubuntu and the bug tracker.  But the following contents in a 
file named /etc/systemd/system/ssh.socket.d/addresses.conf should set you on 
the right path:
  [Socket]
  ListenStream=
  ListenStream=$portnum

- I have long been displeased with ucf's three-way-merge support.  In
particular, when identical content exists both in the user's version and
in the new version but not in the base version, ucf will treat this as a
merge conflict.  This is awful, and specifically caused problems for
upgrades from all cloud images when the user had not modified the sshd
config at all (LP: #1990863).  I've applied a workaround for this in
openssh 1ubuntu7 (currently in the unapproved queue) that's specific to
the cloud image case and ensures clean upgrades without prompting for
users that have not modified sshd_config.  I could generalize this to
all users with modified configs, resulting in two prompts on upgrade but
a better chance of successful three-way merging.  Do you think that
would be an improvement over the status quo?

- Finally, there is some code I'm evaluating landing that would add a
systemd generator for the listenstream settings.  This would only take
effect at boot, but would make it possible for users to continue
managing their port/listenaddress settings in sshd.conf as before.
However, we would not land this in time for the kinetic release, but
would instead consider it for the next release to improve our LTS-to-LTS
compatibility.

-- 
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/1990863

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

Bug description:
  During upgrade from Jammy to Kinetic, I get asked what to do because
  my sshd_config has been modified. I say to do a 3-way merge. It says
  3-way merge fails. I shrug, figure I'll just restore my customizations
  with Ansible after the upgrade like I always do, and tell it to use
  the vendor version of the file. This removes my custom Port settings,
  so they are not migrated over to the ssh.socket settings like
  https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
  ubuntu-22-10-and-later/30189 says they would be. I subsequently run my
  Ansible which restores the customizations and enables the ssh service,
  but now ssh.service and ssh.socket are enabled at the same time, sshd
  isn't listening on my specified ports, and everything is a mess. I've
  never used socket-based activation before and have no idea how to
  configure it so now I have to go reading man pages, Googling all over
  the place, and generally struggle to figure out what the heck is going
  wrong.

  I don't know what the right answer is here, but I really feel like
  some effort needs to be put into figuring out a smoother transition
  for people who are upgrading to Kinetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 11:41:58 2022
  InstallationDate: Installed on 2019-08-16 (1136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic

2022-10-01 Thread Steve Langasek
** Changed in: openssh (Ubuntu)
   Importance: Medium => High

-- 
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/1991199

Title:
  sshd port migration is missing two config lines from jammy to kinetic

Status in openssh package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The automatic migration script from jammy to kinetic generates a
  invalid file for sshd that systemd refuses to read. Manual addition of
  two lines is required for a functional sshd with a custom port.

  This bug can be considered the opposite of
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They
  want to have sshd keep managing the socket while I want to try letting
  systemd do that.

  $ lsb_release -rd
  Description:Ubuntu Kinetic Kudu (development branch)
  Release:22.10

  $ apt-cache policy openssh-server
  openssh-server:
    Installed: 1:9.0p1-1ubuntu6
    Candidate: 1:9.0p1-1ubuntu6
    Version table:
   *** 1:9.0p1-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy systemd
  systemd:
    Installed: 251.4-1ubuntu6
    Candidate: 251.4-1ubuntu6
    Version table:
   *** 251.4-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  # Instructions

  - Configure /etc/ssh/sshd_config to port  in 22.04
  - Upgrade to 22.10 with sudo do-release-upgrade -d
  - Accept overwriting /etc/ssh/sshd_config with the new version
  - Attempt to ssh into the machine

  # Expected behavior

  systemd should listen on port  and start sshd.

  $ cat /etc/systemd/system/ssh.socket.d/addresses.conf
  [Socket]
  ListenStream=
  ListenStream=

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago
    Until: Thu 2022-09-29 02:08:56 EDT; 9min ago
     Triggers: ● ssh.service
   Listen: [::]: (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 923us
   CGroup: /system.slice/ssh.socket

  Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD
  Secure Shell server socket.

  # Actual behavior

  Port  refuses any connection. Systemd fails to parse the
  automatically generated file:

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago
    Until: Thu 2022-09-29 01:51:57 EDT; 16min ago
     Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 982us
   CGroup: /system.slice/ssh.socket

  Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell 
server socket.
  Sep 29 01:56:23 daniel-desktop2 systemd[1]: 
/etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of 
section. Ignoring.

  $ cat /etc/systemd/system/ssh.socket.d/override.conf
  ListenStream=

  # Analysis

  The migration script must be missing the `[Socket]` line and the next one. 
sshd works after I added those two lines manually. Either the migration script 
never worked or systemd changed the syntax in the meantime.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6
  Package: systemd 251.4-1ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic 
root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off 
resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8
  Tags:  kinetic
  Uname: Linux 6.0.0-06rc7-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K30BF_M32BF_A_F_K31BF_6
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1991283] Re: "sshd -i" breaks due to socket activation

2022-10-01 Thread Steve Langasek
** Changed in: openssh (Ubuntu)
   Importance: Undecided => Low

** Changed in: openssh (Ubuntu)
   Status: New => In Progress

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
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/1991283

Title:
  "sshd -i" breaks due to socket activation

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  On Jammy and earlier, simply running "sshd -i" worked.

  Now, it fails silently, and running it with "-d" gives me:

  Missing privilege separation directory: /run/sshd

  This directory is normally created with "RuntimeDirectory=sshd" as
  defined in /lib/systemd/system/ssh.service. In Jammy, this directory
  got created by the ssh service starting at boot, so "sshd -i" worked.

  Now, with socket activation, it no longer does that, so "sshd -i"
  fails unless someone has actually connected on TCP port 22 (which they
  often won't have, since that's the point of "sshd -i").

  systemd will then remove /run/sshd when the ssh service is stopped. I
  think maybe this won't interfere with an existing "sshd -i", but it's
  not really clean. Further, the privilege separation directory doesn't
  appear to be configurable - at least I couldn't find any mention in
  sshd_config(5).

  The workaround is to "mkdir -p /run/sshd && sshd -i" instead.

  Given that "sshd -i"'s use of /run/sshd isn't really related to the
  systemd service, maybe we should move the creation of that directory
  into tmpfiles.d instead?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991283/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic

2022-09-30 Thread Steve Langasek
I see on review that your patch does fix any broken override files, by
virtue of replaying the same upgrade code if upgrading from 1ubuntu6.
There are some corner cases where that might not be desirable, but as
these are all pre-release versions I think it's ok to ignore these in
favor of landing the fix more quickly.

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991199

Title:
  sshd port migration is missing two config lines from jammy to kinetic

Status in openssh package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The automatic migration script from jammy to kinetic generates a
  invalid file for sshd that systemd refuses to read. Manual addition of
  two lines is required for a functional sshd with a custom port.

  This bug can be considered the opposite of
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They
  want to have sshd keep managing the socket while I want to try letting
  systemd do that.

  $ lsb_release -rd
  Description:Ubuntu Kinetic Kudu (development branch)
  Release:22.10

  $ apt-cache policy openssh-server
  openssh-server:
    Installed: 1:9.0p1-1ubuntu6
    Candidate: 1:9.0p1-1ubuntu6
    Version table:
   *** 1:9.0p1-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy systemd
  systemd:
    Installed: 251.4-1ubuntu6
    Candidate: 251.4-1ubuntu6
    Version table:
   *** 251.4-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  # Instructions

  - Configure /etc/ssh/sshd_config to port  in 22.04
  - Upgrade to 22.10 with sudo do-release-upgrade -d
  - Accept overwriting /etc/ssh/sshd_config with the new version
  - Attempt to ssh into the machine

  # Expected behavior

  systemd should listen on port  and start sshd.

  $ cat /etc/systemd/system/ssh.socket.d/addresses.conf
  [Socket]
  ListenStream=
  ListenStream=

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago
    Until: Thu 2022-09-29 02:08:56 EDT; 9min ago
     Triggers: ● ssh.service
   Listen: [::]: (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 923us
   CGroup: /system.slice/ssh.socket

  Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD
  Secure Shell server socket.

  # Actual behavior

  Port  refuses any connection. Systemd fails to parse the
  automatically generated file:

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago
    Until: Thu 2022-09-29 01:51:57 EDT; 16min ago
     Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 982us
   CGroup: /system.slice/ssh.socket

  Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell 
server socket.
  Sep 29 01:56:23 daniel-desktop2 systemd[1]: 
/etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of 
section. Ignoring.

  $ cat /etc/systemd/system/ssh.socket.d/override.conf
  ListenStream=

  # Analysis

  The migration script must be missing the `[Socket]` line and the next one. 
sshd works after I added those two lines manually. Either the migration script 
never worked or systemd changed the syntax in the meantime.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6
  Package: systemd 251.4-1ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic 
root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off 
resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8
  Tags:  kinetic
  Uname: Linux 6.0.0-06rc7-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K30BF_M32BF_A_F_K31BF_6
  dmi.board.vendor: ASUSTeK 

[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic

2022-09-30 Thread Steve Langasek
Thanks for the patch, Nick.  We should also make sure that for users
that had 1ubuntu6 unpacked, we fix up any broken override file as well.

I have some other changes for openssh in progress and will intend to
pick up this fix as part of my next upload.

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
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/1991199

Title:
  sshd port migration is missing two config lines from jammy to kinetic

Status in openssh package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The automatic migration script from jammy to kinetic generates a
  invalid file for sshd that systemd refuses to read. Manual addition of
  two lines is required for a functional sshd with a custom port.

  This bug can be considered the opposite of
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They
  want to have sshd keep managing the socket while I want to try letting
  systemd do that.

  $ lsb_release -rd
  Description:Ubuntu Kinetic Kudu (development branch)
  Release:22.10

  $ apt-cache policy openssh-server
  openssh-server:
    Installed: 1:9.0p1-1ubuntu6
    Candidate: 1:9.0p1-1ubuntu6
    Version table:
   *** 1:9.0p1-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy systemd
  systemd:
    Installed: 251.4-1ubuntu6
    Candidate: 251.4-1ubuntu6
    Version table:
   *** 251.4-1ubuntu6 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  # Instructions

  - Configure /etc/ssh/sshd_config to port  in 22.04
  - Upgrade to 22.10 with sudo do-release-upgrade -d
  - Accept overwriting /etc/ssh/sshd_config with the new version
  - Attempt to ssh into the machine

  # Expected behavior

  systemd should listen on port  and start sshd.

  $ cat /etc/systemd/system/ssh.socket.d/addresses.conf
  [Socket]
  ListenStream=
  ListenStream=

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago
    Until: Thu 2022-09-29 02:08:56 EDT; 9min ago
     Triggers: ● ssh.service
   Listen: [::]: (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 923us
   CGroup: /system.slice/ssh.socket

  Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD
  Secure Shell server socket.

  # Actual behavior

  Port  refuses any connection. Systemd fails to parse the
  automatically generated file:

  $ systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   └─addresses.conf
   Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago
    Until: Thu 2022-09-29 01:51:57 EDT; 16min ago
     Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
    Tasks: 0 (limit: 19047)
   Memory: 8.0K
  CPU: 982us
   CGroup: /system.slice/ssh.socket

  Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell 
server socket.
  Sep 29 01:56:23 daniel-desktop2 systemd[1]: 
/etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of 
section. Ignoring.

  $ cat /etc/systemd/system/ssh.socket.d/override.conf
  ListenStream=

  # Analysis

  The migration script must be missing the `[Socket]` line and the next one. 
sshd works after I added those two lines manually. Either the migration script 
never worked or systemd changed the syntax in the meantime.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6
  Package: systemd 251.4-1ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic 
root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off 
resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8
  Tags:  kinetic
  Uname: Linux 6.0.0-06rc7-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K30BF_M32BF_A_F_K31BF_6
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X

[Touch-packages] [Bug 1971901] Re: dlltool uses non-unique temp filenames

2022-09-30 Thread Steve Langasek
** Tags removed: foundations-todo

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1971901

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  Confirmed
Status in binutils-mingw-w64 package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

  /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec
  Assembler messages:
  Error: can't open winmm_dll_t.s for reading: No such file or directory
  /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited 
with status 1
  /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
  winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
  make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
  make: *** Waiting for unfinished jobs
  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec

  Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for
  it's temp file - these are not unique when building libwinmm.delay.a
  and libwinmm.cross.a in parallel. (This can of course affect any dll
  wine is building import libs for, winmm is just the one I happaned to
  get caught on).

  This is regression newly introduced in binutils 2.38 vs older versions
  which used getpid() as the basis of their temp name. We just
  encountered it as part of updating our CI for a winelib application
  from focal to jammy, but it seems to have been discovered by others
  already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885

  There is an upstream fix on master (2.39) which is already backported
  to the binutils-2_38 branch:
  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just
  be a matter of cherry-picking. Hopefully the fact it's a regression
  from impish->jammy and that upstream already backported it to 2.38
  might make this a candidate for jammy-updates?

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

2022-09-24 Thread Steve Langasek
resolvconf has not been installed by default in Ubuntu since before
18.04 LTS and is considered deprecated and should not be used.  Is there
a reason that you have the package installed?

** Changed in: resolvconf (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1990743

Title:
  resolvconf install fails upgrading from Jammy to Kinetic

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original 
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed

2022-09-23 Thread Steve Langasek
This is a bug in how apt handles phased updates across multiple source
packages currently.  The grub SRU has been rolled back to jammy-proposed
now, and an apt fix is in progress, expected to be uploaded early next
week.

** Also affects: apt (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2-signed (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: apt (Ubuntu)
   Importance: Undecided => Critical

-- 
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/1990684

Title:
  grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but
  2.06-2ubuntu10 is to be installed

Status in apt package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  Fix Released

Bug description:
  # apt clean

  # apt update
  Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease
  Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates 
InRelease
  Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports 
InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  24 packages can be upgraded. Run 'apt list --upgradable' to see them.

  # apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 
2.06-2ubuntu10 is to be installed
  E: Broken packages

  # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:"
  Version: 2.06-2ubuntu10
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports 
jammy-updates/main arm64 Packages
  Version: 2.06-2ubuntu7
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main 
arm64 Packages

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu7)

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu10)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-arm64-signed 1.180+2.06-2ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Sep 23 13:12:07 2022
  Ec2AMI: ami-092d30890417a55e5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ca-central-1d
  Ec2InstanceType: t4g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: grub2-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990684/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades

2022-09-22 Thread Steve Langasek
python3{.10,-defaults,-stdlib-extensions} have all had their phasing set
to 100% now to avoid this issue.

** Changed in: python3-defaults (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: python3-stdlib-extensions (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: python3-stdlib-extensions (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: python3.10 (Ubuntu)
   Status: Triaged => Fix Released

-- 
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/1990586

Title:
  22.04: python3* mismatched phasing breaks dist-upgrades

Status in apt package in Ubuntu:
  Incomplete
Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python3.10 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  --
  Users who manually run sudo apt dist-upgrade without paying attention can 
remove essential parts of their system

  Test Case
  -
  This test case won't work as well if phasing is set to 0% or 100%

  Create /etc/apt/apt.conf.d/phasing and set its contents to
  APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c;

  Then run

  sudo apt update
  sudo apt dist-upgrade

  Workaround In Advance
  -
  Don't run sudo apt dist-upgrade. Just run sudo apt upgrade
  Or use Update Manager or the Ubuntu Store to apply updates

  Workaround Afterwards
  -
  Fortunately, apt phasing is ignored for new package installs. So to get your 
Ubuntu Desktop back, just run

  sudo apt install ubuntu-desktop

  Other Info
  --
  These 3 updates were published today:
  python3-stdlib-extensions
  python3-defaults
  python3.10

  Suggested Fix
  -
  Fully phase those 3 source packages to 100%

  Apt Output
  --
  The following packages were automatically installed and are no longer 
required:
    apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info 
gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0
    gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 
gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 
gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0
    gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces 
gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 
libbabeltrace1 libboost-regex1.74.0
    libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 
libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 
libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3
    libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 
libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 
librygel-db-2.6-2 librygel-renderer-2.6-2
    librygel-server-2.6-2 libsane-hpaio libsgutils2-2 
libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 
libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1
    libxvmc1 mobile-broadband-provider-info network-manager-gnome patch 
printer-driver-hpcups printer-driver-postscript-hp python-apt-common 
python3-blinker python3-certifi python3-cffi-backend
    python3-chardet python3-click python3-colorama python3-cryptography 
python3-dateutil python3-debconf python3-debian python3-defer 
python3-distro-info python3-fasteners python3-future
    python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney 
python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient 
python3-lazr.uri python3-lockfile
    python3-louis python3-monotonic python3-more-itertools python3-oauthlib 
python3-olefile python3-pexpect python3-pkg-resources python3-problem-report 
python3-ptyprocess python3-pyparsing
    python3-requests python3-rfc3339 python3-secretstorage python3-six 
python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel 
whoopsie-preferences x11-apps x11-session-utils
    xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core 
xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom 
xserver-xorg-video-all
    xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev 
xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl 
xserver-xorg-video-radeon
    xserver-xorg-video-vesa xserver-xorg-video-vmware
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
    apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup 
duplicity gedit gnome-control-center gnome-online-accounts gnome-software 
gnome-software-plugin-snap gnome-terminal
    hplip ibus ibus-table language-selector-common language-selector-gnome 
nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher 
orca python3-apport python3-apt
 

[Touch-packages] [Bug 1980494] Re: krb5-multidev is not multi-arch installable due to differences in /usr/bin/krb5-config.mit

2022-09-22 Thread Steve Langasek
I think the right fix here is to strip the output of dpkg-buildflags
from the config script output.  We've definitely had problems before
where leaking dpkg-buildflags into other build tools made it effectively
impossible for dependent packages to work around toolchain issues.

** Changed in: krb5 (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1980494

Title:
  krb5-multidev is not multi-arch installable due to differences in
  /usr/bin/krb5-config.mit

Status in krb5 package in Ubuntu:
  New

Bug description:
  I am trying to build wine in a wow64 configuration and need to install
  the i386 and amd64 version of the krb5-multidev package on Ubuntu
  22.04.  The two version are not co-installable due to differences in
  the /usr/bin/krb5-config.mit file between the two version of the
  package.

  The diff between the two files is:

  --- krb5-config.mit-i386  2022-06-18 21:32:44.034889873 -0400
  +++ krb5-config.mit-amd64 2022-06-18 21:31:37.302149522 -0400
  @@ -40,7 +40,7 @@
   libdir=/usr/lib/${tripple}/mit-krb5
   CC_LINK='$(CC) $(PROG_LIBPATH) $(PROG_RPATH_FLAGS) $(CFLAGS) $(LDFLAGS)'
   KDB5_DB_LIB=
  -LDFLAGS='-Wl,-Bsymbolic-functions -Wl,-z,relro'
  +LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto 
-Wl,-z,relro'
   RPATH_FLAG=''
   PROG_RPATH_FLAGS=''
   PTHREAD_CFLAGS='-pthread'

  The krb5-multidev package is co-installable on Debian. It appears that
  Ubuntu uses different default linker flags for the i386 and amd64
  platforms and Debian does not.

  This bug is related to
  https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1970979

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1980494/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990429] [NEW] software-properties uses deprecated apt-key

2022-09-21 Thread Steve Langasek
Public bug reported:

software-properties still references apt-key, which is deprecated
upstream (https://blog.jak-linux.org/2021/06/20/migrating-away-apt-
key/):

$ grep -r apt-key
tests/test_dbus.py:# test apt-key update
tests/test_aptauth.py:"/usr/bin/apt-key",
tests/test_aptauth.py:stderr="Warning: apt-key is deprecated.\n",
debian/changelog:   - thus, add-apt-key for PPAs observes https_proxy for key 
retrieval
debian/changelog:   - stop using apt-key for installing keys
debian/changelog:  * Port AptAuth.py from gpg command parsing to apt-key command
debian/changelog:- fix incorrect call call to apt-key for the fingerprint, 
thanks
softwareproperties/SoftwareProperties.py:# apt-key stuff
softwareproperties/SoftwareProperties.py:""" Run apt-key update """
softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"adv", "--with-colons", "--batch", "--fixed-list-mode", "--list-keys"]
softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"--fakeroot", "add", filename]
softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"--fakeroot", "update"]
softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"--fakeroot", "rm", key]
$

apt-key will eventually go away, and software-properties needs to adapt.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rls-kk-incoming

** Tags added: rls-kk-incoming

-- 
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/1990429

Title:
  software-properties uses deprecated apt-key

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties still references apt-key, which is deprecated
  upstream (https://blog.jak-linux.org/2021/06/20/migrating-away-apt-
  key/):

  $ grep -r apt-key
  tests/test_dbus.py:# test apt-key update
  tests/test_aptauth.py:"/usr/bin/apt-key",
  tests/test_aptauth.py:stderr="Warning: apt-key is deprecated.\n",
  debian/changelog:   - thus, add-apt-key for PPAs observes https_proxy for key 
retrieval
  debian/changelog:   - stop using apt-key for installing keys
  debian/changelog:  * Port AptAuth.py from gpg command parsing to apt-key 
command
  debian/changelog:- fix incorrect call call to apt-key for the 
fingerprint, thanks
  softwareproperties/SoftwareProperties.py:# apt-key stuff
  softwareproperties/SoftwareProperties.py:""" Run apt-key update """
  softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"adv", "--with-colons", "--batch", "--fixed-list-mode", "--list-keys"]
  softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"--fakeroot", "add", filename]
  softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"--fakeroot", "update"]
  softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", 
"--fakeroot", "rm", key]
  $

  apt-key will eventually go away, and software-properties needs to
  adapt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990429/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990315] Re: cannot link against libudev

2022-09-20 Thread Steve Langasek
For the record, showing only the errors, without showing the linker
command that produced them, is not an actionable bug report.

These symbols are certainly present in libudev.so.1 in kinetic so this
is likely not a bug in the Ubuntu systemd package.

-- 
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/1990315

Title:
  cannot link against libudev

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When building Mesa vulkan drivers I get a lot of those error messages
  and the build fails:

  ```
  error: undefined symbol: udev_new
  error: undefined symbol: udev_monitor_get_fd
  error: undefined symbol: udev_monitor_new_from_netlink
  error: undefined symbol: udev_monitor_receive_device
  error: undefined symbol: udev_monitor_unref
  error: undefined symbol: udev_unref
  error: undefined symbol: udev_device_unref
  error: undefined symbol: udev_device_get_property_value
  error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
  error: undefined symbol: udev_monitor_enable_receiving
  ```

  It worked on Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990315/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990187] [NEW] systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

2022-09-19 Thread Steve Langasek
Public bug reported:

In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling it
into the ubuntu-minimal seed.

In the past we briefly had libnss-resolve seeded (between xenial and
bionic LTSes but not in any LTS) but it was removed because:

 - it was redundant; /etc/resolv.conf was consistent and correct.
 - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

This new recommends was noticed specifically because of some broken
kinetic container images where /etc/resolv.conf was broken (empty) and
*some* applications still worked via nss but others failed by trying to
use the DNS protocol directly.  (I.e.: 2nd point above)

I believe systemd-resolved should drop its recommends on libnss-resolve
for Ubuntu.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1990187

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  New

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1988772] Re: kinetic livefs builds are failing on dns errors

2022-09-09 Thread Steve Langasek
Images building successfully now.

** Changed in: live-build (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1988772

Title:
  kinetic livefs builds are failing on dns errors

Status in live-build package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  the livefs kinetic builds are still failing, every job failed for a
  week

  https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu

  >'Temporary failure resolving 'ftpmaster.internal'

  Colin poked at it and wrote

  > livecd-rootfs initially sets up a correct /etc/resolv.conf inside its build 
chroot; but then
  > systemd-resolved.postinst moves that aside in favour of a symlink to 
/run/systemd/resolve/stub-
  > resolv.conf, but systemd-resolved itself isn't running because 
livecd-rootfs builds in a chroot, 
  > not a container

  he also suggested that it could be perhaps handled from live-build
  scripts/build/lb_chroot_resolv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1988772/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1988772] Re: kinetic livefs builds are failing on dns errors

2022-09-05 Thread Steve Langasek
If the systemd-resolved postinst doesn't work correctly in a chroot, I
think the problem needs to be fixed there, not worked around in the live
build system

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1988772

Title:
  kinetic livefs builds are failing on dns errors

Status in live-build package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  the livefs kinetic builds are still failing, every job failed for a
  week

  https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu

  >'Temporary failure resolving 'ftpmaster.internal'

  Colin poked at it and wrote

  > livecd-rootfs initially sets up a correct /etc/resolv.conf inside its build 
chroot; but then
  > systemd-resolved.postinst moves that aside in favour of a symlink to 
/run/systemd/resolve/stub-
  > resolv.conf, but systemd-resolved itself isn't running because 
livecd-rootfs builds in a chroot, 
  > not a container

  he also suggested that it could be perhaps handled from live-build
  scripts/build/lb_chroot_resolv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1988772/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

2022-09-02 Thread Steve Langasek
Hello msaxl, or anyone else affected,

Accepted qtbase-opensource-src into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/qtbase-opensource-
src/5.15.3+dfsg-2ubuntu0.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: qtbase-opensource-src (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
  less secure protocols.

  [Test Plan]

  1. Create test.cpp with the following contents:

  #include 
  #include 
  #include 
  #include 

  int main(int argc, char **argv) {
  QCoreApplication app(argc, argv);
  QSslSocket s;
  QSslConfiguration cfg = s.sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s.setSslConfiguration(cfg);
  s.connectToHostEncrypted("www.ubuntu.com", 443);
  s.waitForConnected();
  qDebug() << s.sessionProtocol();
  return 0;
  }

  2. Create test.pro with the following contents:

  CONFIG += debug warn_all
  QT = core network
  SOURCES = test.cpp

  3. Install qtbase5-dev package.

  4. Compile using `qmake && make`.

  5. Run the generated ./test executable. It should print 15, not -1.

  [Where problems could occur]

  It is unlikely to cause issues on 64-bit platforms because long and
  uint64_t are both 64 bits long. On armhf potential problems may be
  related to availability of other protocols.

  [Original Description]

  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1988608] Re: [FFe] Sync version 0.187-2 from Debian unstable

2022-09-02 Thread Steve Langasek
Not sure of the utility of getting a change like this into kinetic, but
it's certainly low risk based on the description, so approved.

** Changed in: elfutils (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1988608

Title:
  [FFe] Sync version 0.187-2 from Debian unstable

Status in elfutils package in Ubuntu:
  Fix Committed

Bug description:
  With the upcoming release of a debuginfod service for Ubuntu (see
  https://blog.sergiodj.net/2022/08/14/debuginfod-is-coming-to-
  ubuntu.html), we need to adjust our tooling to offer users the
  possibility of using the service out-of-the-box, without too much
  configuration.

  I have recently uploaded elfutils to Debian unstable in order to
  improve the way it handles the debuginfod shell profiles, and also to
  preemptively implement support for Ubuntu's debuginfod server.  Now, I
  would like to request a feature freeze exception to bring these
  updates to Ubuntu Kinetic.

  The package builds fine on Debian
  (https://buildd.debian.org/status/package.php?p=elfutils), and also on
  Kinetic.  elfutils doesn't have autopkgtests associated with it, but I
  have tested installing/uninstalling/upgrading/purging the package
  inside a container to make sure that these operations are still OK.

  There is a new debconf question that will be introduced by this sync.
  I marked it as high priority because I believe this is an important
  feature and users will initially not be aware of it.  We can consider
  lowering the priority later.

  elfutils generates many binary packages, and as such it has many
  reverse dependencies.  They should not be affected by this sync,
  though, because all modifications were focused on debuginfod-related
  maintainer scripts in the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1988608/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1780767] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1780767

Title:
  Some tests are flaky due to timeout

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
  http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
  It's blocking randomly on different tests.

  All tests that are stucked, implements closing a request via a timeout
  (and then, executing "run"). The bet is that the timeout is short
  enough (1s) so that, when autopkgtests infra is busy, time to execute
  the bash subcommand is taking more than a second, and so "dismissing"
  is ran before execution happens and the whole testsuite hangs.

  There are few instances of setting this timeout function:
  $ grep eout_add_sec test/*
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)

  Short term solution could be to increase the timeout. Long term would
  be to eliminate this potential race implementing cancelling
  differently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1947425] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1947425

Title:
  Use of deprecated 'imp' module

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  New

Bug description:
  Impact
  --

  The deprecation warning is just a warning, but it clutters the output
  and can lead to misattributions in case something does not work as
  expected.

  Test Case
  -

  1. Execute following command:
  python3 -Wonce -c "import apport.report"
  2. There should be no output.

  Where problems could occur
  --

  Except for changes to the test cases, _check_interpreted is the only
  consumer for the changed code. Breakage in this code paths can lead to
  wrongly assume that the crashing Python code is an interpreted script
  or not. This can lead to reports that have only ExecutablePath set
  (and not InterpreterPath).

  Original Description
  

  Code using apport/report.py will see the following warning:

  $ python3 -Wonce -c "import apport.report"
  /usr/lib/python3/dist-packages/apport/report.py:13
    /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the 
imp module is deprecated in favour of importlib; see the module's documentation 
for alternative uses
  import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat

  The 'imp' module is slated for removal in Python 3.12.
  https://github.com/python/cpython/blob/main/Lib/imp.py#L31

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1947425/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1979211] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1979211

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Won't Fix
Status in apport source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --

  As it can be seen in
  https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
  there are thousands of crashes of this type (and multiple duplicate
  bug reports for it). Instead of apport logging a failure in
  /var/log/apport.log, it crashes. Fixing this bug also fixes the issue
  with logging failures in the socket path (for handling crashes in
  containers).

  Test Case
  -

  There should be no instances of
  https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
  for the fixed version.

  Where problems could occur
  --

  The apport binary is called by the kernel when a process crashes.
  Worst case scenarios include breaking the apport binary and no problem
  report is generated any more (or apport uses too much resources).
  Since all the desired logs are now logged, it could increase the
  amount of logs that are written (apport has some flood detection in
  case a process dies constantly).

  Original Description
  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu82.1, the problem page at 
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 531, in 
  options = parse_arguments()
    File "/usr/share/apport/apport", line 463, in parse_arguments
  parser.print_usage()
    File "/usr/lib/python3.10/argparse.py", line 2562, in print_usage
  self._print_message(self.format_usage(), file)
    File "/usr/lib/python3.10/argparse.py", line 2573, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

  This bug can be reproduced by configuring the previously supported
  parameters to Apport and then let a process crash (e.g. call divide-
  by-zero):

  ```
  echo "|/usr/share/apport/apport %p %s %c %d %P %E" | sudo tee 
/proc/sys/kernel/core_pattern
  ```

  So this bug is a regression of commit c320e910a516 ("Switch to using
  non-positional arguments") which is a fix for CVE-2022-28658 and
  CVE-2021-3899.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1979211/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962454] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1962454

Title:
  Oops pages show wrong time window in JournalErrors

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  Incomplete

Bug description:
  [Impact]

  Oops pages show wrong time window in JournalErrors. For example, I
  just experienced a crash at:

    Feb 28 17:31:12

  And the JournalErrors entries are:

    Feb 28 17:31:30 - Feb 28 17:31:41

  So don't relate to the crash.

  [Test Plan]

  1. Find a recent crash report from a relevant Ubuntu release on
  https://errors.ubuntu.com/ If you're looking at
  https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick
  a relevant instance from the Occurrences list.

  2. Now you're on a page starting with https://errors.ubuntu.com/oops/
  look at ApportVersion and verify that apport is a recent enough
  version to contain the proposed fix. If not then go to step 1.

  3. Verify the Date field falls within the time range of the
  JournalErrors entries.

  Step 3 might fail in the case of there being no system log entries
  from around the time of the crash. That does not necessarily mean the
  test plan has failed. Go to step 1 and pick a different crash.

  Prior to the fix you would almost never find oops pages that would
  pass the test. After the fix you should find many/most oops pages do
  pass the test.

  [Where problems could occur]

  Worst case - in any part of the bug reporting/collection procedure,
  since that is what's changing.

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1962454/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1977954] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1977954

Title:
  apport_python_hook: Crashes if os.getcwd() throws FileNotFoundError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  New

Bug description:
  Impact
  --

  The Apport Python hook should be transparent to the user (which is
  normally the case). Bugs and crashes inside the hook lead to an
  exception inside the exception which clutters the output and confuse
  the user. User/Developer need to understand this Python hook and look
  into the encapsulated stack trace only.

  Test Case
  -

  1. Create /tmp/getcwd.py with following content:
  ```
  #!/usr/bin/python3

  import os
  import tempfile

  tempdir = tempfile.mkdtemp()
  os.chdir(tempdir)
  os.rmdir(tempdir)
  os.getcwd()
  ```
  2. Make it executable and execute it.

  It should produce following output:

  ```
  Traceback (most recent call last):
    File "/tmp/getcwd.py", line 9, in 
  os.getcwd()
  FileNotFoundError: [Errno 2] No such file or directory
  ```

  instead of:

  ```
  $ /tmp/getcwd.py
  Traceback (most recent call last):
    File "/tmp/getcwd.py", line 9, in 
  os.getcwd()
  FileNotFoundError: [Errno 2] No such file or directory
  Error in sys.excepthook:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in 
apport_excepthook
  binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))
  FileNotFoundError: [Errno 2] No such file or directory

  Original exception was:
  Traceback (most recent call last):
    File "/tmp/getcwd.py", line 9, in 
  os.getcwd()
  FileNotFoundError: [Errno 2] No such file or directory
  ```

  Another related issue: bug #1979637

  Regression Potential
  

  There might be a regression that causes capturing Python exception
  fail. Then reporting them as bugs to Launchpad or the error tracker
  would not be possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1977954/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978301] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1978301

Title:
  Broken contact URL in German translation

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  New

Bug description:
  Impact
  --

  All German users (and all translations that use "%s." in their
  translation template) will get a broken URL link for bug reports
  against snaps (e.g. Firefox).

  Test Case
  -

  1. Execute following command: LANGUAGE=de ubuntu-bug firefox
  2. Click on the URL
  3. A browser window should open and not display a 404 page

  Regression Potential
  

  Since there was no test case for converting text to HTML before this
  fix, there might be some URLs that will become broken by this fix.

  Original Description
  

  "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying:

  firefox wird durch einen von mozilla veröffentlichten Snap
  bereitgestellt. Für Hilfe gehen Sie über
  https://support.mozilla.org/kb/file-bug-report-or-feature-request-
  mozilla.

  The dot at the end is included in the URL link. The dot makes the URL
  link broken. The regular expression in gtk/apport-gtk for http URLs
  should become smarter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1978301/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1964828] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1964828

Title:
  /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError:
  'CasperMD5json'

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  If the user reports a bug and rejects to enter the root password for
  collecting information (like the CasperMD5json), the Ubuntu add_info
  hook will fail with a stack trace. The remaining code for collecting
  more information is not executed. So the resulting bug reports will be
  less helpful. The check_for_disk_error call is not reached and
  therefore skipped.

  [Test Plan]

  1. Launch the Ubuntu installer (i.e. ubuntu-22.04-desktop-amd64.iso)
  2. Select "Try Ubuntu"
  3. Open a terminal
  4. Run: ubuntu-bug -f
  5. Select "installer" and click on OK
  6. Click on "abort" when ask for the password
  7. The terminal should not show a stacktrace

  [Where problems could occur]

  The changed code is the Ubuntu add_info hook. So this hook could fail
  due to a regression or reveal bugs in the later code path. The later
  code path could cause more more load on the users machine (but only
  when the user wants to report the issue). Apport will catch failing
  add_info hooks and store the failure in the report.

  [Orinial report]

  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
    File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info
  apport.hookutils.attach_casper_md5check(report,
    File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in 
attach_casper_md5check
  check = json.loads(report['CasperMD5json'])
    File "/usr/lib/python3.10/collections/__init__.py", line 1102, in 
__getitem__
  raise KeyError(key)
  KeyError: 'CasperMD5json'
  kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module 
"colorreload-gtk-module"
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 22.04.7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperVersion: 1.467
  CurrentDesktop: KDE
  Date: Mon Mar 14 21:22:23 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1979637] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1979637

Title:
  apport_python_hook: FileNotFoundError if cwd was deleted

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  Confirmed

Bug description:
  Impact
  --

  The Apport Python hook should be transparent to the user (which is
  normally the case). Bugs and crashes inside the hook lead to an
  exception inside the exception which clutters the output and confuse
  the user. User/Developer need to understand this Python hook and look
  into the encapsulated stack trace only.

  Test Case
  -

  Run following shell script:

  ```sh
  echo "raise ValueError()" > /tmp/failure.py
  mkdir /tmp/foo
  cd /tmp/foo/
  rmdir /tmp/foo/
  python3 ../failure.py
  ```

  It should only print following stacktrace:

  ```
  Traceback (most recent call last):
    File "../failure.py", line 1, in 
  raise ValueError()
  ValueError
  ```

  Regression Potential
  

  There might be a regression that causes capturing Python exception
  fail. Then reporting them as bugs to Launchpad or the error tracker
  would not be possible.

  Original Description
  

  The script should only show a ValueError, but apport_python_hook.py
  crashes:

  ```
  Traceback (most recent call last):
    File "../failure.py", line 1, in 
  raise ValueError()
  ValueError
  Error in sys.excepthook:
  Traceback (most recent call last):
    File "", line 1372, in 
_path_importer_cache
  KeyError: '..'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 55, in 
apport_excepthook
  import apt_pkg
    File "", line 1027, in _find_and_load
    File "", line 1002, in _find_and_load_unlocked
    File "", line 945, in _find_spec
    File "", line 1439, in find_spec
    File "", line 1408, in _get_spec
    File "", line 1374, in 
_path_importer_cache
    File "", line 1350, in _path_hooks
    File "", line 1632, in 
path_hook_for_FileFinder
    File "", line 1505, in __init__
  FileNotFoundError: [Errno 2] No such file or directory

  Original exception was:
  Traceback (most recent call last):
    File "../failure.py", line 1, in 
  raise ValueError()
  ValueError
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1979637/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982487] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1982487

Title:
  apport fails with PermissionError for dump mode 2 in containers

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  New
Status in apport source package in Jammy:
  New

Bug description:
  [Impact]

  Apport will fail for processes with dump mode 2 inside of containers.

  [Test plan]

  Run following testcase script inside a LXC container:

  ```
  #!/bin/sh
  sudo rm -rf /var/crash/* /var/log/apport.log

  sudo -u mail sh -c "ping 127.0.0.1 > /dev/null" &
  sleep 0.3
  killall -11 ping

  sleep 0.3
  cat /var/log/apport.log
  ```

  apport.log for the affected version:

  ```
  ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: called for pid 6449, 
signal 11, core limit 0, dump mode 2
  ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: Unhandled exception:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 681, in 
add_proc_info
  self["ExecutablePath"] = _read_proc_link(
    File "/usr/lib/python3/dist-packages/apport/report.py", line 92, in 
_read_proc_link
  return os.readlink(path, dir_fd=dir_fd)
  PermissionError: [Errno 13] Permission denied: 'exe'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 862, in 
  info.add_proc_info(proc_pid_fd=proc_pid_fd)
    File "/usr/lib/python3/dist-packages/apport/report.py", line 686, in 
add_proc_info
  raise ValueError("not accessible")
  ValueError: not accessible
  ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: pid: 6452, uid: 0, gid: 0, 
euid: 8, egid: 8
  ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: environment: 
environ({'LANG': 'C.UTF-8', 'PATH': 
'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin', 
'LISTEN_PID': '6452', 'LISTEN_FDS': '1', 'LISTEN_FDNAMES': 'connection', 
'INVOCATION_ID': '1352c67b4a21480a9b35db8012dafb42', 'JOURNAL_STREAM': 
'8:29587491', 'SYSTEMD_EXEC_PID': '6452'})
  ```

  The apport log should not show a Traceback.

  [Where problems could occur]

  The apport binary is called by the kernel when a process crashes.
  Worst case scenarios include breaking the apport binary and no problem
  report is generated any more (or apport uses too much resources).
  Users will see problems reports inside the container which cause
  additional load or disk usage. The fix is accompanied by a test case
  (run in autopkgtest).

  [Other Info]

  The autopkgtest for armhf are run inside a LXC container and some test
  cases like test_crash_setuid_drop trigger this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1982487/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982555] Proposed package upload rejected

2022-09-02 Thread Steve Langasek
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1982555

Title:
  core dump file empty inside container

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Confirmed
Status in apport source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  Apport will write an empty core dump file inside of containers.

  [Test plan]

  Run following testcase script inside a LXC container:

  ```
  rm -f /var/lib/apport/coredump/*
  ulimit -c 100
  sleep 86400 &
  killall -3 sleep
  ```

  Apport will write a core dump into /var/lib/apport/coredump, but this
  core dump is empty:

  ```
  $ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
    File: 
/var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
    Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: fd00h/64768d  Inode: 120848663   Links: 1
  Access: (0400/-r)  Uid: (0/root)   Gid: (0/root)
  Access: 2022-07-22 07:54:48.838682067 +
  Modify: 2022-07-22 07:54:48.838682067 +
  Change: 2022-07-22 07:54:48.838682067 +
   Birth: 2022-07-22 07:54:48.838682067 +
  ```

  This file should not be empty.

  [Where problems could occur]

  The apport binary is called by the kernel when a process crashes.
  Worst case scenarios include breaking the apport binary and no problem
  report is generated any more (or apport uses too much resources).
  Users will see problems reports inside the container which cause
  additional load or disk usage. The fix is accompanied by a test case.

  [Other Info]

  The autopkgtest for armhf are run inside a LXC container and the test
  case test_core_dump_packaged_sigquit triggers this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1982555/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian

2022-08-26 Thread Steve Langasek
Removing packages from kinetic:
wpewebkit 2.36.6-1 in kinetic
libwpewebkit-1.0-doc 2.36.6-1 in kinetic amd64
libwpewebkit-1.0-doc 2.36.6-1 in kinetic arm64
libwpewebkit-1.0-doc 2.36.6-1 in kinetic armhf
libwpewebkit-1.0-doc 2.36.6-1 in kinetic i386
libwpewebkit-1.0-doc 2.36.6-1 in kinetic ppc64el
libwpewebkit-1.0-doc 2.36.6-1 in kinetic riscv64
libwpewebkit-1.0-doc 2.36.6-1 in kinetic s390x
libwpewebkit-1.1-0 2.36.6-1 in kinetic amd64
libwpewebkit-1.1-0 2.36.6-1 in kinetic arm64
libwpewebkit-1.1-0 2.36.6-1 in kinetic armhf
libwpewebkit-1.1-0 2.36.6-1 in kinetic ppc64el
libwpewebkit-1.1-0 2.36.6-1 in kinetic riscv64
libwpewebkit-1.1-0 2.36.6-1 in kinetic s390x
libwpewebkit-1.1-dev 2.36.6-1 in kinetic amd64
libwpewebkit-1.1-dev 2.36.6-1 in kinetic arm64
libwpewebkit-1.1-dev 2.36.6-1 in kinetic armhf
libwpewebkit-1.1-dev 2.36.6-1 in kinetic ppc64el
libwpewebkit-1.1-dev 2.36.6-1 in kinetic riscv64
libwpewebkit-1.1-dev 2.36.6-1 in kinetic s390x
wpewebkit-driver 2.36.6-1 in kinetic amd64
wpewebkit-driver 2.36.6-1 in kinetic arm64
wpewebkit-driver 2.36.6-1 in kinetic armhf
wpewebkit-driver 2.36.6-1 in kinetic ppc64el
wpewebkit-driver 2.36.6-1 in kinetic riscv64
wpewebkit-driver 2.36.6-1 in kinetic s390x
Comment: Unmaintained web engine, security concerns; LP: #1981592
1 package successfully removed.


** Changed in: wpewebkit (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1981592

Title:
  Please remove wpewebkit and block syncs from Debian

Status in cog package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in wpewebkit package in Ubuntu:
  Fix Released

Bug description:
  The wpewebkit package contains a whole webkit browser engine. It is
  currently not used by anything of substance in Ubuntu:

  $ reverse-depends src:wpewebkit
  Reverse-Depends
  * cog   (for libwpewebkit-1.1-0)
  * gstreamer1.0-wpe  (for libwpewebkit-1.1-0)

  
  cog is a single-window browser for embedded devices that is not used by 
anything else in the archive.
  gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything 
else in the archive.

  Using this browser engine on the Internet is very risky as it it not
  currently maintained and contains hundreds of security flaws, and
  maintaining it requires a tremendous amount of work.

  As such, I don't believe this package is suitable for the Ubuntu
  archive.

  I recommend we disable the build in gstreamer and remove both cog and
  wpewebkit, and put on block on syncs from Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian

2022-08-26 Thread Steve Langasek
(and blacklisted)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1981592

Title:
  Please remove wpewebkit and block syncs from Debian

Status in cog package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in wpewebkit package in Ubuntu:
  Fix Released

Bug description:
  The wpewebkit package contains a whole webkit browser engine. It is
  currently not used by anything of substance in Ubuntu:

  $ reverse-depends src:wpewebkit
  Reverse-Depends
  * cog   (for libwpewebkit-1.1-0)
  * gstreamer1.0-wpe  (for libwpewebkit-1.1-0)

  
  cog is a single-window browser for embedded devices that is not used by 
anything else in the archive.
  gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything 
else in the archive.

  Using this browser engine on the Internet is very risky as it it not
  currently maintained and contains hundreds of security flaws, and
  maintaining it requires a tremendous amount of work.

  As such, I don't believe this package is suitable for the Ubuntu
  archive.

  I recommend we disable the build in gstreamer and remove both cog and
  wpewebkit, and put on block on syncs from Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian

2022-08-26 Thread Steve Langasek
Removing packages from kinetic:
cog 0.14.0-1 in kinetic
cog 0.14.0-1 in kinetic amd64
cog 0.14.0-1 in kinetic arm64
cog 0.14.0-1 in kinetic armhf
cog 0.14.0-1 in kinetic ppc64el
cog 0.14.0-1 in kinetic riscv64
cog 0.14.0-1 in kinetic s390x
Comment: Depends on wpewebkit which is a security concern; no 
reverse-dependencies. LP: #1981592
1 package successfully removed.


** Changed in: cog (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1981592

Title:
  Please remove wpewebkit and block syncs from Debian

Status in cog package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in wpewebkit package in Ubuntu:
  Fix Released

Bug description:
  The wpewebkit package contains a whole webkit browser engine. It is
  currently not used by anything of substance in Ubuntu:

  $ reverse-depends src:wpewebkit
  Reverse-Depends
  * cog   (for libwpewebkit-1.1-0)
  * gstreamer1.0-wpe  (for libwpewebkit-1.1-0)

  
  cog is a single-window browser for embedded devices that is not used by 
anything else in the archive.
  gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything 
else in the archive.

  Using this browser engine on the Internet is very risky as it it not
  currently maintained and contains hundreds of security flaws, and
  maintaining it requires a tremendous amount of work.

  As such, I don't believe this package is suitable for the Ubuntu
  archive.

  I recommend we disable the build in gstreamer and remove both cog and
  wpewebkit, and put on block on syncs from Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

2022-08-25 Thread Steve Langasek
No, this is only about removing it from container and cloud images.

-- 
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 in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in fwupd source package in Jammy:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Triaged
Status in modemmanager source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1937110] Proposed package upload rejected

2022-08-19 Thread Steve Langasek
An upload of isc-dhcp to jammy-proposed has been rejected from the
upload queue for the following reason: "reuploading with the correct fix
from kinetic".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1937110

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Jammy:
  Incomplete

Bug description:
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  
  His DHCP response looks like this:

  
  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
ac1f0101 ..

  
  Im booting the subiquity process with an patched ipxe 
(https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  
  Would be awesome if this could be fixed.. maybe just a simple busybox compile 
option?

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937110/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1840375] Proposed package removed from archive

2022-08-19 Thread Steve Langasek
The version of shadow in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Won't Fix
Status in shadow source package in Bionic:
  Fix Released
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1840375] Re: groupdel doesn't support extrausers

2022-08-19 Thread Steve Langasek
The version of shadow in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Tags removed: verification-needed-xenial

** Changed in: shadow (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Won't Fix
Status in shadow source package in Bionic:
  Fix Released
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1840375] Proposed package removed from archive

2022-08-19 Thread Steve Langasek
The version of shadow in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Won't Fix
Status in shadow source package in Bionic:
  Fix Released
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1840375] Proposed package removed from archive

2022-08-19 Thread Steve Langasek
The version of shadow in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Won't Fix
Status in shadow source package in Bionic:
  Fix Released
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1983618] Re: New upstream microrelease 2.5.13

2022-08-19 Thread Steve Langasek
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.13+dfsg-0ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: openldap (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
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/1983618

Title:
  New upstream microrelease 2.5.13

Status in openldap package in Ubuntu:
  Invalid
Status in openldap source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4504

   * Upstream "call for testing":
  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been
  performed and completed successfully: https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/4887/+build/24250107

   * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4895

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1983618/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1980545] Re: Update evolution-data-server to 3.44.4

2022-08-19 Thread Steve Langasek
Hello Jeremy, or anyone else affected,

Accepted evolution-data-server into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/evolution-data-
server/3.44.4-0ubuntu1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: evolution-data-server (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1980545

Title:
  Update evolution-data-server to 3.44.4

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.4/NEWS

  The current version in Ubuntu 22.04 LTS is 3.44.2.

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)

2022-08-19 Thread Steve Langasek
This bug report lacks the 'Where problems could occur' section of the
SRU bug template.

** Changed in: sudo (Ubuntu Jammy)
   Status: Fix Committed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1958055

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Jammy:
  Incomplete

Bug description:
  [Impact]

  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot). This
  applies to all Qt applications.

  [Test Plan]

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  On other other hand, sudo preserves the DISPLAY environment variable:

  $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)'
  XAUTHORITY=/run/user/1000/gdm/Xauthority
  DISPLAY=:0
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  HOME=/root
  SHELL=/bin/bash

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  [Other Info]

  This changes was accepted upstream: https://github.com/sudo-
  project/sudo/pull/165

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1986860] Re: [MIR] krb5 (bin:krb5-user)

2022-08-17 Thread Steve Langasek
I don't believe MIR is required for binary packages unless they have
been excluded from main for a reason as part of a prior MIR.  You should
only need to seed it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1986860

Title:
  [MIR] krb5 (bin:krb5-user)

Status in krb5 package in Ubuntu:
  New

Bug description:
  Placeholder bug to MIR bin:krb5-user (src:krb5 is in main already).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1986860/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian

2022-08-16 Thread Steve Langasek
Someone needs to update gst-plugins-bad1.0 to not depend on this before
the removal can proceed.

** Also affects: cog (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: wpewebkit (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1981592

Title:
  Please remove wpewebkit and block syncs from Debian

Status in cog package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in wpewebkit package in Ubuntu:
  Incomplete

Bug description:
  The wpewebkit package contains a whole webkit browser engine. It is
  currently not used by anything of substance in Ubuntu:

  $ reverse-depends src:wpewebkit
  Reverse-Depends
  * cog   (for libwpewebkit-1.1-0)
  * gstreamer1.0-wpe  (for libwpewebkit-1.1-0)

  
  cog is a single-window browser for embedded devices that is not used by 
anything else in the archive.
  gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything 
else in the archive.

  Using this browser engine on the Internet is very risky as it it not
  currently maintained and contains hundreds of security flaws, and
  maintaining it requires a tremendous amount of work.

  As such, I don't believe this package is suitable for the Ubuntu
  archive.

  I recommend we disable the build in gstreamer and remove both cog and
  wpewebkit, and put on block on syncs from Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1986705] Re: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2022-08-16 Thread Steve Langasek
This does not look like an Ubuntu bug.  You have the most recent jammy
version of dpkg installed on your system according to your bug report,
however the upgrade failure shows an internal error when trying to
invoke 'dpkg --valiate-version' from dpkg-maintscript-helper.

What does `which dpkg` return on your system?

** Package changed: base-files (Ubuntu) => dpkg (Ubuntu)

** Changed in: dpkg (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1986705

Title:
  package base-files 12ubuntu4.1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in dpkg package in Ubuntu:
  Incomplete

Bug description:
  error with dpkg and base-files..12ubuntu.amd64.deb

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: base-files 12ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   base-files:amd64: Install
   base-files:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Aug 16 13:20:40 2022
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2022-05-09 (99 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, unpackaged
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: base-files
  Title: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1986705/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-08-12 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted zlib into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/zlib/1:1.2.11.dfsg-2ubuntu9.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: zlib (Ubuntu Jammy)
   Status: In Progress => 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/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Committed
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Committed
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  Fix Committed
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-08-12 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted bedtools into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bedtools/2.30.0+dfsg-2ubuntu0.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: bedtools (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed-jammy

-- 
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/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Committed
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Committed
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  Fix Committed
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    

[Touch-packages] [Bug 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy

2022-08-12 Thread Steve Langasek
The question regarding partner usage of dhclient is in progress
elsewhere and does not block this SRU.

** Changed in: isc-dhcp (Ubuntu Jammy)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1972029

Title:
  dhclient overriding stub-resolv.conf file on Jammy

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Jammy:
  Fix Committed
Status in isc-dhcp source package in Kinetic:
  Fix Released

Bug description:
  [Issue]
  On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten 
if dhclient is executed.

  While debugging this, I found the reference on LP#1889068 [0] of the
  move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit-
  hooks.d/, and this new hook [2] has no reference of make_resolv_conf()
  being called.

  [Reproducer]
  -
  I used a cloud-image based Jammy installation (uvt-kvm).  Once in:

  $ cat /run/system/resolve/stub-resolv.conf

  And one will see:

  nameserver 127.0.0.53
  options edns0 trust-ad
  search .

  Then:

  $ sudo dhclient
  $ cat /run/system/resolve/stub-resolv.conf

  You'll see the definition of the nameserver(s) in, and the stub IP
  address no longer there.  To revert this, a `systemctl restart
  systemd-resolved` is needed.

  [Impact]

  This is an improper way to keep nameserver(s) in *resolv* files; the
  override of the file should never happen in these circumstances.

  [Extra]
  -
  As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from 
a Focal installation to a Jammy one, and the problem _does not happen_ when 
such hook is in place.

  [ . . . ]

  Let me know if further clarification is needed to proceed.  Thank you.

  BR,
  pprincipeza

  [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068
  [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/
  [2] https://paste.ubuntu.com/p/YQdG6z4WS7/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   3   4   5   6   7   8   9   10   >