[Touch-packages] [Bug 2067775] Re: subiquity package-hook is outdated

[Olivier Gayot]

While investigating another issue (see bug 2076233), I stumbled upon
this change. The subiquity.py hook (currently in jammy-proposed /
2.20.11-0ubuntu82.6) calls report.add_tags but Report.add_tags() seems
to only be available in more recent versions of apport.

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

Title:
  subiquity package-hook is outdated

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  Fix Committed
Status in apport source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  The Subiquity package hook in Apport has not been updated to collect
  the type of information we are typically interested in (e.g.
  /var/log/installer/\*). This means users who run `ubuntu-bug
  subiquity` from the terminal will not automatically collect relevant
  information to attach to their bug reports. This upload fixes this by
  updating Subiquity's package hook to collect logs and information
  typically used for debugging Subiquity bugs. This fix needs to be SRUd
  to Noble and Jammy so that users performing these installs can run
  `ubuntu-bug subiquity` and collect relevant information.

  [Test Plan]

  The test plan is focused on testing the behavior of apport within the
  live installation environment, where we primarily expect users to
  submit bug reports from. Thus the test plan is split into three
  different test plans: Two for Desktop images and one for Server. For
  Noble, all three test scenarios are relevant. For Jammy, it is only
  necessary to test Server since the Desktop installer for Jammy is not
  Subiquity based.

  Desktop - Manual:
  1) Download the latest Noble Desktop ISO [1].
  2) Begin an installation using the media you downloaded. You may progress the 
install as far as you like, with the following restrictions: (1) At minimum you 
need wait for the first screen to show up and (2) at most you may allow the 
install to finish but do not allow the system to restart (you need to be in the 
live-environment to proceed).
  3) Open a terminal (ctl + alt + t) 
  4) Enable proposed[4] and update apport
  5) Run the following command "APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug 
subiquity"
  6) 4 authorization prompts will display, requesting access to collect 
information from the system. Allow all of them.
  7) Inspect the fields of the report and ensure that none report "permission 
denied" or similar. 
  8) Click "Send" on the resulting dialog to send the report. Firefox will open 
up to finish filling out the bug information on launchpad.
  9) Log in and enter anything as the title and hit continue. Click "No, I need 
to report a new bug" if necessary
  10) Enter anything in the "further information section". Ensure that the 
field below this section, titled "This bug contains information that is", is 
marked "Private" by default.
  11) You can now submit the bug and inspect the automatically filled 
description for further errors in the report. (Errors messages are typically 
short enough to show up in the body of the bug description while larger 
attachments with real information end up as attachments)

  Desktop - Automatic:
  1) Download the latest Noble Desktop ISO [1].
  2) Begin an installation using the media you downloaded. You may progress the 
install as far as you like, with the following restrictions: (1) At minimum you 
need wait for the first screen to show up and (2) at most you may allow the 
install to finish but do not allow the system to restart (you need to be in the 
live-environment to proceed).
  3) Open a terminal (ctl + alt + t) 
  4) Enable proposed[4] and update apport
  5) Create a fake subiquity crash file: sudo printf "Package: 
subiquity\nProblemType: crash\n" > /var/crash/test.crash
  6) authorize the collection of information
  7) Inspect the generated data. Ensure:
- The key LaunchpadPrivate exists
- There are no "permission denied" errors
  - Do NOT submit the report

  
  Server (Jammy or Noble):
  1) Download the latest Server ISO for the release you have chosen to verify 
(Noble[2] or Jammy[3]) 
  2) Begin an installation using the media you downloaded. You may progress the 
install as far as you like, with the following restrictions: (1) At minimum you 
need wait for the first screen to show up and (2) at most you may allow the 
install to finish but do not allow the system to restart (you need to be in the 
live-environment to proceed).
  3) Enter the debug shell (F2 or ctrl+z)
  4) Enable proposed[4] and update apport
  5) Run the following command "sudo APPORT_LAUNCHPAD_INSTANCE=qastaging 
ubuntu-bug subiquity" (sudo is required)
  6) Apport will ask for which matching application you want to report against. 
Select option 2, which should read "subiquity (1234 of snap 
/snap/subiquity/1234 of version $release_ver) deb package"
  7) Now 

[Touch-packages] [Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed

[Olivier Gayot]

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on
  target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme-
  stas,shim-signed

Status in subiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  verison：ubuntu 24.04 subiquity version
  OS:noble-live-server-amd64-0222.iso
  CPU:AMD EPYC 9634 84-Core Processor*1
  MEMORY: M321R2GA3BB6-CQKVG*2
  ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
  UEFI MODE

  lsb_release -rd: Description:Untun Noble Numbat(development branch)
  Release: 24.04

  What you expected to happen:
  Install os on nvme,expected to install succefully.

  What happened instead:
  Install os on nvme, install always failed.
  Before installation, we cleaned up all our nvme disk by dd if=/dev/zero 
of=/dev/sda bs=1M count=5

  The error log:
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on 
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed', 
'nvme-cli', 'nvme-stas', 'shim-signed']
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages: 
FAIL: installing missing packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command 
curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback 
(most recent call last):
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py", 
line 202, in main
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret = 
args.func(args)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1998, in curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
builtin_curthooks(cfg, target, state)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1803, in builtin_curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
install_missing_packages(cfg, target, osfamily=osfamily)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1362, in install_missing_packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
distro.install_packages(to_add, target=target, osfamily=osfamily)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472, 
in install_packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
install_cmd('install', args=pkglist, opts=opts, target=target,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254, 
in run_apt_command
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = 
apt_install(mode, args, opts=opts, env=env, target=target,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302, 
in apt_install
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = 
inchroot.subp(cmd + dl_opts + packages, env=env,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791, 
in subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
subp(*args, **kwargs)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283, 
in subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
_subp(*args, **kwargs)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147, 
in _subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise 
ProcessExecutionError(stdout=out, stderr=err,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
curtin.util.ProcessExecutionError: Unexpected error while running command.
  Mar 15 03:03:05 ubuntu-server 

[Touch-packages] [Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed

[Olivier Gayot]

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu-seeds/+git/ubuntu-seeds/+merge/463200

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

Title:
  ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on
  target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme-
  stas,shim-signed

Status in subiquity package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  verison：ubuntu 24.04 subiquity version
  OS:noble-live-server-amd64-0222.iso
  CPU:AMD EPYC 9634 84-Core Processor*1
  MEMORY: M321R2GA3BB6-CQKVG*2
  ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
  UEFI MODE

  lsb_release -rd: Description:Untun Noble Numbat(development branch)
  Release: 24.04

  What you expected to happen:
  Install os on nvme,expected to install succefully.

  What happened instead:
  Install os on nvme, install always failed.
  Before installation, we cleaned up all our nvme disk by dd if=/dev/zero 
of=/dev/sda bs=1M count=5

  The error log:
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on 
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed', 
'nvme-cli', 'nvme-stas', 'shim-signed']
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages: 
FAIL: installing missing packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command 
curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback 
(most recent call last):
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py", 
line 202, in main
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret = 
args.func(args)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1998, in curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
builtin_curthooks(cfg, target, state)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1803, in builtin_curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
install_missing_packages(cfg, target, osfamily=osfamily)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1362, in install_missing_packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
distro.install_packages(to_add, target=target, osfamily=osfamily)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472, 
in install_packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
install_cmd('install', args=pkglist, opts=opts, target=target,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254, 
in run_apt_command
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = 
apt_install(mode, args, opts=opts, env=env, target=target,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302, 
in apt_install
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = 
inchroot.subp(cmd + dl_opts + packages, env=env,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791, 
in subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
subp(*args, **kwargs)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283, 
in subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
_subp(*args, **kwargs)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147, 
in _subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise 
ProcessExecutionError(stdout=out, stderr=err,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
curtin.util.ProcessExecutionError: Unexpected error while running command.
  Mar 15 03:03:05 

[Touch-packages] [Bug 2055065] Re: Please merge kbd 2.6.4-2 (main) from Debian unstable

[Olivier Gayot]

** Description changed:

- TODO
+ debian:
+ kbd| 2.0.4-4   | oldoldstable   | source, amd64, arm64, armel, 
armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
+ kbd| 2.3.0-3   | oldstable  | source, amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el, s390x
+ kbd| 2.5.1-1   | stable | source
+ kbd| 2.5.1-1+b1| stable | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
+ kbd| 2.6.4-2   | testing| source, amd64, arm64, armel, 
armhf, i386, mips64el, ppc64el, s390x
+ kbd| 2.6.4-2   | unstable   | source, amd64, arm64, armel, 
armhf, i386, mips64el, ppc64el, riscv64, s390x
+ kbd| 2.6.4-2   | unstable-debug | source
+ ubuntu:
+  kbd | 1.15.5-1ubuntu1  | trusty | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el
+  kbd | 1.15.5-1ubuntu4  | xenial | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el, s390x
+  kbd | 1.15.5-1ubuntu5  | xenial-updates | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el, s390x
+  kbd | 2.0.4-2ubuntu1   | bionic | source, amd64, arm64, armhf, 
i386, ppc64el, s390x
+  kbd | 2.0.4-4ubuntu2   | focal  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
+  kbd | 2.3.0-3ubuntu4   | jammy  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
+  kbd | 2.3.0-3ubuntu4.22.04 | jammy-updates  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
+  kbd | 2.5.1-1ubuntu1   | mantic | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
+  kbd | 2.5.1-1ubuntu1   | noble  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x

** Changed in: kbd (Ubuntu)
   Status: New => In Progress

** Changed in: kbd (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

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

Title:
  Please merge kbd 2.6.4-2 (main) from Debian unstable

Status in kbd package in Ubuntu:
  In Progress

Bug description:
  debian:
  kbd| 2.0.4-4   | oldoldstable   | source, amd64, arm64, armel, 
armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  kbd| 2.3.0-3   | oldstable  | source, amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el, s390x
  kbd| 2.5.1-1   | stable | source
  kbd| 2.5.1-1+b1| stable | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
  kbd| 2.6.4-2   | testing| source, amd64, arm64, armel, 
armhf, i386, mips64el, ppc64el, s390x
  kbd| 2.6.4-2   | unstable   | source, amd64, arm64, armel, 
armhf, i386, mips64el, ppc64el, riscv64, s390x
  kbd| 2.6.4-2   | unstable-debug | source
  ubuntu:
   kbd | 1.15.5-1ubuntu1  | trusty | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el
   kbd | 1.15.5-1ubuntu4  | xenial | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el, s390x
   kbd | 1.15.5-1ubuntu5  | xenial-updates | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el, s390x
   kbd | 2.0.4-2ubuntu1   | bionic | source, amd64, arm64, armhf, 
i386, ppc64el, s390x
   kbd | 2.0.4-4ubuntu2   | focal  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
   kbd | 2.3.0-3ubuntu4   | jammy  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
   kbd | 2.3.0-3ubuntu4.22.04 | jammy-updates  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
   kbd | 2.5.1-1ubuntu1   | mantic | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x
   kbd | 2.5.1-1ubuntu1   | noble  | source, amd64, arm64, armhf, 
ppc64el, riscv64, s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2055065] Re: Please merge kbd 2.6.4-2 (main) from Debian unstable

[Olivier Gayot]

** Merge proposal linked:
   https://code.launchpad.net/~ogayot/ubuntu/+source/kbd/+git/kbd/+merge/461345

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

Title:
  Please merge kbd 2.6.4-2 (main) from Debian unstable

Status in kbd package in Ubuntu:
  New

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2055065] Re: Please merge kbd 2.6.4-2 (main) from Debian unstable

[Olivier Gayot]

** Changed in: kbd (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge kbd 2.6.4-2 (main) from Debian unstable

Status in kbd package in Ubuntu:
  New

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2055065] [NEW] Please merge kbd 2.6.4-2 (main) from Debian unstable

[Olivier Gayot]

Public bug reported:

TODO

** Affects: kbd (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please merge kbd 2.6.4-2 (main) from Debian unstable

Status in kbd package in Ubuntu:
  New

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Olivier Gayot]

The last two autopkgtest runs in the infrastructure are green despite
the trigger and they both show:

258s Unpacking wpasupplicant (2:2.10-21) ...

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Olivier Gayot]

After further analysis, it looks like the trigger=wpa/2:2.10-21 highly
increases the likeliness of the error to occur.

At this point, I do not think that there is any regression in wpa
2:2.10-21 compared to 2:2.10-20. The changeset is minimal. OTOH I think
the trigger=wpa/... alters the order of events and somehow consequently
makes the race condition more likely to occur.

FWIW, with a trigger=wpa/..., wpasupplicant gets upgraded before running
the ethernets test:

 96s Unpacking wpasupplicant (2:2.10-21) over (2:2.10-20) ...

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-
proposed//noble/s390x/n/netplan.io/20240109_171235_03058@/log.gz

Whereas. without the trigger, it gets installed:

127s Unpacking wpasupplicant (2:2.10-21) ...

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-
proposed//noble/s390x/n/netplan.io/20240109_162248_f656d@/log.gz

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Olivier Gayot]

Added wpa as affected so this bug can show in the proposed migrations
report.

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

** Tags added: update-excuse

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable

[Olivier Gayot]

** Changed in: dbus (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 dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2045668

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  Fix Committed

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 12 had an undocumented
  opt-out mechanism intended for use on buildds and QA systems targeting
  Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
  to ensure that the upgrade path from Debian 11 to 12 will continue
  to work and continue to undergo automated tests. That opt-out is
  no longer applicable or available in trixie/sid, and was removed in
  usrmerge version 38.
  Since version 1.14.10-2, dbus ships its systemd units in
  /usr/lib/systemd/system, as part of the distro-wide transition
  away from making use of "aliased" paths. This is entirely valid on
  merged-/usr systems, but will no longer work in the unsupported
  filesystem layout with non-merged /usr, because for historical
  reasons, current versions of systemd on non-merged-/usr systems will
  only read units from /lib/systemd/system.
  In the case of dbus, the symptom when this assumption is broken is
  particularly bad (various key system services will not start, with
  long delays during boot, login and shutdown), so let's hold back
  this upgrade on unsupported non-merged-/usr systems until they have
  completed the switch to merged-/usr and can install
  usr-is-merged (>= 38~).
  (Closes: #1054650)

   -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

  1.14.10-2
  Superseded in sid-release on 2023-10-30

  dbus (1.14.10-2) unstable; urgency=low

* Backport packaging changes from experimental:
  - Install systemd system units into /usr/lib/systemd/system.
This was allowed by TC resolution #1053901. The shared library is
still in /lib, for now.
Build-depend on debhelper 13.11.6~ to ensure that the units are still
picked up by dh_installsystemd.
  - Build-depend on pkgconf rather than pkg-config
  - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
environment. These variables are specific to a single login session.
* d/copyright: Drop unused entry for pkg.m4.
  This is no longer included in the upstream source release since 1.14.6.
* d/dbus-tests.lintian-overrides: Drop unused overrides.
  Lintian no longer flags our RUNPATH as problematic.

   -- Simon McVittie   Wed, 25 Oct 2023 15:56:36 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable

[Olivier Gayot]

Thanks vorlon. This makes sense. I'll do go ahead and remove dbus's
dependency on usr-is-merged.

Unsubscribing Ubuntu Package Archive.

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

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 12 had an undocumented
  opt-out mechanism intended for use on buildds and QA systems targeting
  Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
  to ensure that the upgrade path from Debian 11 to 12 will continue
  to work and continue to undergo automated tests. That opt-out is
  no longer applicable or available in trixie/sid, and was removed in
  usrmerge version 38.
  Since version 1.14.10-2, dbus ships its systemd units in
  /usr/lib/systemd/system, as part of the distro-wide transition
  away from making use of "aliased" paths. This is entirely valid on
  merged-/usr systems, but will no longer work in the unsupported
  filesystem layout with non-merged /usr, because for historical
  reasons, current versions of systemd on non-merged-/usr systems will
  only read units from /lib/systemd/system.
  In the case of dbus, the symptom when this assumption is broken is
  particularly bad (various key system services will not start, with
  long delays during boot, login and shutdown), so let's hold back
  this upgrade on unsupported non-merged-/usr systems until they have
  completed the switch to merged-/usr and can install
  usr-is-merged (>= 38~).
  (Closes: #1054650)

   -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

  1.14.10-2
  Superseded in sid-release on 2023-10-30

  dbus (1.14.10-2) unstable; urgency=low

* Backport packaging changes from experimental:
  - Install systemd system units into /usr/lib/systemd/system.
This was allowed by TC resolution #1053901. The shared library is
still in /lib, for now.
Build-depend on debhelper 13.11.6~ to ensure that the units are still
picked up by dh_installsystemd.
  - Build-depend on pkgconf rather than pkg-config
  - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
environment. These variables are specific to a single login session.
* d/copyright: Drop unused entry for pkg.m4.
  This is no longer included in the upstream source release since 1.14.6.
* d/dbus-tests.lintian-overrides: Drop unused overrides.
  Lintian no longer flags our RUNPATH as problematic.

   -- Simon McVittie   Wed, 25 Oct 2023 15:56:36 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable

[Olivier Gayot]

Subscribing Ubuntu Package Archive.

The binary package usr-is-merged is currently in universe whereas its
source package src:usrmerge is in main.

Package: usr-is-merged
Description: Transitional package to assert a merged-/usr system
 This package can be successfully installed only on merged-/usr systems.
 .
 It can be safely removed once no other package depends on it anymore.

DBus 1.14.10-3 adds a new dependency on usrmerge so we would need to
promote usr-is-merged to main.

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

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 12 had an undocumented
  opt-out mechanism intended for use on buildds and QA systems targeting
  Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
  to ensure that the upgrade path from Debian 11 to 12 will continue
  to work and continue to undergo automated tests. That opt-out is
  no longer applicable or available in trixie/sid, and was removed in
  usrmerge version 38.
  Since version 1.14.10-2, dbus ships its systemd units in
  /usr/lib/systemd/system, as part of the distro-wide transition
  away from making use of "aliased" paths. This is entirely valid on
  merged-/usr systems, but will no longer work in the unsupported
  filesystem layout with non-merged /usr, because for historical
  reasons, current versions of systemd on non-merged-/usr systems will
  only read units from /lib/systemd/system.
  In the case of dbus, the symptom when this assumption is broken is
  particularly bad (various key system services will not start, with
  long delays during boot, login and shutdown), so let's hold back
  this upgrade on unsupported non-merged-/usr systems until they have
  completed the switch to merged-/usr and can install
  usr-is-merged (>= 38~).
  (Closes: #1054650)

   -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

  1.14.10-2
  Superseded in sid-release on 2023-10-30

  dbus (1.14.10-2) unstable; urgency=low

* Backport packaging changes from experimental:
  - Install systemd system units into /usr/lib/systemd/system.
This was allowed by TC resolution #1053901. The shared library is
still in /lib, for now.
Build-depend on debhelper 13.11.6~ to ensure that the units are still
picked up by dh_installsystemd.
  - Build-depend on pkgconf rather than pkg-config
  - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
environment. These variables are specific to a single login session.
* d/copyright: Drop unused entry for pkg.m4.
  This is no longer included in the upstream source release since 1.14.6.
* d/dbus-tests.lintian-overrides: Drop unused overrides.
  Lintian no longer flags our RUNPATH as problematic.

   -- Simon McVittie   Wed, 25 Oct 2023 15:56:36 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable

[Olivier Gayot]

Untagging rls-nn-incoming based on insights from the MIR team in
#ubuntu-devel [1]

 schopin: ogayot: usr-is-merged seems to be an empty meta-package. It's 
source package src:usrmerge is already in main
 does that mean we can just ask an AA to promote it, no paperwork?
 so I'd say this doesn't need a MIR, as there is no new code. Maybe this 
new binary was added after the source package got promoted. You should not 
block on this.
 I don't think paperwork would be involved. It might show up as a 
component-mismatch, but should be resolved on the fast-path, by asking an AA.

[1] https://irclogs.ubuntu.com/2023/12/05/%23ubuntu-devel.html

** Tags removed: rls-nn-incoming

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

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 12 had an undocumented
  opt-out mechanism intended for use on buildds and QA systems targeting
  Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
  to ensure that the upgrade path from Debian 11 to 12 will continue
  to work and continue to undergo automated tests. That opt-out is
  no longer applicable or available in trixie/sid, and was removed in
  usrmerge version 38.
  Since version 1.14.10-2, dbus ships its systemd units in
  /usr/lib/systemd/system, as part of the distro-wide transition
  away from making use of "aliased" paths. This is entirely valid on
  merged-/usr systems, but will no longer work in the unsupported
  filesystem layout with non-merged /usr, because for historical
  reasons, current versions of systemd on non-merged-/usr systems will
  only read units from /lib/systemd/system.
  In the case of dbus, the symptom when this assumption is broken is
  particularly bad (various key system services will not start, with
  long delays during boot, login and shutdown), so let's hold back
  this upgrade on unsupported non-merged-/usr systems until they have
  completed the switch to merged-/usr and can install
  usr-is-merged (>= 38~).
  (Closes: #1054650)

   -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

  1.14.10-2
  Superseded in sid-release on 2023-10-30

  dbus (1.14.10-2) unstable; urgency=low

* Backport packaging changes from experimental:
  - Install systemd system units into /usr/lib/systemd/system.
This was allowed by TC resolution #1053901. The shared library is
still in /lib, for now.
Build-depend on debhelper 13.11.6~ to ensure that the units are still
picked up by dh_installsystemd.
  - Build-depend on pkgconf rather than pkg-config
  - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
environment. These variables are specific to a single login session.
* d/copyright: Drop unused entry for pkg.m4.
  This is no longer included in the upstream source release since 1.14.6.
* d/dbus-tests.lintian-overrides: Drop unused overrides.
  Lintian no longer flags our RUNPATH as problematic.

   -- Simon McVittie   Wed, 25 Oct 2023 15:56:36 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable

[Olivier Gayot]

Tagging rls-nn-incoming so that we can discuss the new dependency on
usr-is-merged (>= 38).

While src:usrmerge is in main, usr-is-merged is currently in universe.

 usrmerge | 9 | xenial/universe | source, all
 usrmerge | 17| bionic/universe | source, all
 usrmerge | 23| focal/universe  | source, all
 usrmerge | 25ubuntu2 | jammy   | source, all
 usrmerge | 33ubuntu1 | lunar   | source, all
 usrmerge | 35ubuntu1 | mantic  | source, all
 usrmerge | 35ubuntu1 | noble   | source, all

ubuntu:
 usr-is-merged | 33ubuntu1 | lunar/universe  | all
 usr-is-merged | 35ubuntu1 | mantic/universe | all
 usr-is-merged | 35ubuntu1 | noble/universe  | all


** Tags added: rls-nn-incoming

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

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 12 had an undocumented
  opt-out mechanism intended for use on buildds and QA systems targeting
  Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
  to ensure that the upgrade path from Debian 11 to 12 will continue
  to work and continue to undergo automated tests. That opt-out is
  no longer applicable or available in trixie/sid, and was removed in
  usrmerge version 38.
  Since version 1.14.10-2, dbus ships its systemd units in
  /usr/lib/systemd/system, as part of the distro-wide transition
  away from making use of "aliased" paths. This is entirely valid on
  merged-/usr systems, but will no longer work in the unsupported
  filesystem layout with non-merged /usr, because for historical
  reasons, current versions of systemd on non-merged-/usr systems will
  only read units from /lib/systemd/system.
  In the case of dbus, the symptom when this assumption is broken is
  particularly bad (various key system services will not start, with
  long delays during boot, login and shutdown), so let's hold back
  this upgrade on unsupported non-merged-/usr systems until they have
  completed the switch to merged-/usr and can install
  usr-is-merged (>= 38~).
  (Closes: #1054650)

   -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

  1.14.10-2
  Superseded in sid-release on 2023-10-30

  dbus (1.14.10-2) unstable; urgency=low

* Backport packaging changes from experimental:
  - Install systemd system units into /usr/lib/systemd/system.
This was allowed by TC resolution #1053901. The shared library is
still in /lib, for now.
Build-depend on debhelper 13.11.6~ to ensure that the units are still
picked up by dh_installsystemd.
  - Build-depend on pkgconf rather than pkg-config
  - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
environment. These variables are specific to a single login session.
* d/copyright: Drop unused entry for pkg.m4.
  This is no longer included in the upstream source release since 1.14.6.
* d/dbus-tests.lintian-overrides: Drop unused overrides.
  Lintian no longer flags our RUNPATH as problematic.

   -- Simon McVittie   Wed, 25 Oct 2023 15:56:36 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated

[Olivier Gayot]

** Merge proposal unlinked:
   
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880

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

Title:
  The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method
  is deprecated

Status in Ubuntu Online Accounts API:
  Confirmed
Status in snapd:
  Confirmed
Status in apparmor package in Ubuntu:
  Fix Released
Status in biometryd package in Ubuntu:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in dbus package in Ubuntu:
  Triaged
Status in deepin-notifications package in Ubuntu:
  New
Status in lomiri-download-manager package in Ubuntu:
  In Progress
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  When upstream D-Bus merged the AppArmor mediation patches, they did
  not like the GetConnectionAppArmorSecurityContext() bus method.
  Instead, they decided to expose a peer's AppArmor context using the
  org.freedesktop.DBus.GetConnectionCredentials() bus method. All users
  of the GetConnectionAppArmorSecurityContext() method should switch to
  the GetConnectionCredentials() method as soon as possible so that
  Ubuntu can drop the patch that implements
  GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is
  released.

  In order to switch to the new method, you'll need to depend on
  libapparmor 2.10 or newer.

  I'll be adding example code that illustrates how to switch from
  GetConnectionAppArmorSecurityContext() to GetConnectionCredentials().

  content-hub, media-hub, mediascanner2, signon-apparmor-extension,
  ubuntu-download-manager, and ubuntu-system-settings-online-accounts
  all need to transition to the new method of obtaining the AppArmor
  label.

  The apparmor package should be updated to drop the libapparmor-
  mention-dbus-method-in-getcon-man.patch patch and the dbus package
  should be updated to drop the aa-get-connection-apparmor-security-
  context.patch patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable

[Olivier Gayot]

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880

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

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 12 had an undocumented
  opt-out mechanism intended for use on buildds and QA systems targeting
  Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
  to ensure that the upgrade path from Debian 11 to 12 will continue
  to work and continue to undergo automated tests. That opt-out is
  no longer applicable or available in trixie/sid, and was removed in
  usrmerge version 38.
  Since version 1.14.10-2, dbus ships its systemd units in
  /usr/lib/systemd/system, as part of the distro-wide transition
  away from making use of "aliased" paths. This is entirely valid on
  merged-/usr systems, but will no longer work in the unsupported
  filesystem layout with non-merged /usr, because for historical
  reasons, current versions of systemd on non-merged-/usr systems will
  only read units from /lib/systemd/system.
  In the case of dbus, the symptom when this assumption is broken is
  particularly bad (various key system services will not start, with
  long delays during boot, login and shutdown), so let's hold back
  this upgrade on unsupported non-merged-/usr systems until they have
  completed the switch to merged-/usr and can install
  usr-is-merged (>= 38~).
  (Closes: #1054650)

   -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

  1.14.10-2
  Superseded in sid-release on 2023-10-30

  dbus (1.14.10-2) unstable; urgency=low

* Backport packaging changes from experimental:
  - Install systemd system units into /usr/lib/systemd/system.
This was allowed by TC resolution #1053901. The shared library is
still in /lib, for now.
Build-depend on debhelper 13.11.6~ to ensure that the units are still
picked up by dh_installsystemd.
  - Build-depend on pkgconf rather than pkg-config
  - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
environment. These variables are specific to a single login session.
* d/copyright: Drop unused entry for pkg.m4.
  This is no longer included in the upstream source release since 1.14.6.
* d/dbus-tests.lintian-overrides: Drop unused overrides.
  Lintian no longer flags our RUNPATH as problematic.

   -- Simon McVittie   Wed, 25 Oct 2023 15:56:36 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 2045668] [NEW] Please merge dbus 1.14.10-3 (main) from Debian unstable

[Olivier Gayot]

Public bug reported:

1.14.10-3
Published in sid-release on 2023-10-30

dbus (1.14.10-3) unstable; urgency=medium

  * d/control: dbus Depends on usr-is-merged (>= 38~).
Non-merged /usr has been unsupported since Debian 12, as per Technical
Committee resolutions #978636 and #994388 (please see the Debian 12
release notes for details).
The version of usr-is-merged shipped in Debian 12 had an undocumented
opt-out mechanism intended for use on buildds and QA systems targeting
Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
to ensure that the upgrade path from Debian 11 to 12 will continue
to work and continue to undergo automated tests. That opt-out is
no longer applicable or available in trixie/sid, and was removed in
usrmerge version 38.
Since version 1.14.10-2, dbus ships its systemd units in
/usr/lib/systemd/system, as part of the distro-wide transition
away from making use of "aliased" paths. This is entirely valid on
merged-/usr systems, but will no longer work in the unsupported
filesystem layout with non-merged /usr, because for historical
reasons, current versions of systemd on non-merged-/usr systems will
only read units from /lib/systemd/system.
In the case of dbus, the symptom when this assumption is broken is
particularly bad (various key system services will not start, with
long delays during boot, login and shutdown), so let's hold back
this upgrade on unsupported non-merged-/usr systems until they have
completed the switch to merged-/usr and can install
usr-is-merged (>= 38~).
(Closes: #1054650)

 -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

1.14.10-2
Superseded in sid-release on 2023-10-30

dbus (1.14.10-2) unstable; urgency=low

  * Backport packaging changes from experimental:
- Install systemd system units into /usr/lib/systemd/system.
  This was allowed by TC resolution #1053901. The shared library is
  still in /lib, for now.
  Build-depend on debhelper 13.11.6~ to ensure that the units are still
  picked up by dh_installsystemd.
- Build-depend on pkgconf rather than pkg-config
- dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
  environment. These variables are specific to a single login session.
  * d/copyright: Drop unused entry for pkg.m4.
This is no longer included in the upstream source release since 1.14.6.
  * d/dbus-tests.lintian-overrides: Drop unused overrides.
Lintian no longer flags our RUNPATH as problematic.

 -- Simon McVittie   Wed, 25 Oct 2023 15:56:36 +0100

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Gayot (ogayot)
 Status: In Progress

** Changed in: dbus (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Changed in: dbus (Ubuntu)
   Status: New => In Progress

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

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 12 had an undocumented
  opt-out mechanism intended for use on buildds and QA systems targeting
  Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
  to ensure that the upgrade path from Debian 11 to 12 will continue
  to work and continue to undergo automated tests. That opt-out is
  no longer applicable or available in trixie/sid, and was removed in
  usrmerge version 38.
  Since version 1.14.10-2, dbus ships its systemd units in
  /usr/lib/systemd/system, as part of the distro-wide transition
  away from making use of "aliased" paths. This is entirely valid on
  merged-/usr systems, but will no longer work in the unsupported
  filesystem layout with non-merged /usr, because for historical
  reasons, current versions of systemd on non-merged-/usr systems will
  only read units from /lib/systemd/system.
  In the case of dbus, the symptom when this assumption is broken is
  particularly bad (various key system services will not start, with
  long delays during boot, login and shutdown), so let's hold back
  this upgrade on unsupported non-merged-/usr systems until they have
  completed the switch to merged-/usr and can install
  usr-is-merged (>= 38~).
  (Closes: #1054650)

   -- Simon McVittie   Mon, 30 Oct 2023 11:51:35 +

  1.14.10-2
  S

[Touch-packages] [Bug 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated

[Olivier Gayot]

** Changed in: lomiri-download-manager (Ubuntu)
   Status: New => In Progress

** Changed in: lomiri-download-manager (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

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

Title:
  The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method
  is deprecated

Status in Ubuntu Online Accounts API:
  Confirmed
Status in snapd:
  Confirmed
Status in apparmor package in Ubuntu:
  Fix Released
Status in biometryd package in Ubuntu:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in dbus package in Ubuntu:
  Triaged
Status in deepin-notifications package in Ubuntu:
  New
Status in lomiri-download-manager package in Ubuntu:
  In Progress
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  When upstream D-Bus merged the AppArmor mediation patches, they did
  not like the GetConnectionAppArmorSecurityContext() bus method.
  Instead, they decided to expose a peer's AppArmor context using the
  org.freedesktop.DBus.GetConnectionCredentials() bus method. All users
  of the GetConnectionAppArmorSecurityContext() method should switch to
  the GetConnectionCredentials() method as soon as possible so that
  Ubuntu can drop the patch that implements
  GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is
  released.

  In order to switch to the new method, you'll need to depend on
  libapparmor 2.10 or newer.

  I'll be adding example code that illustrates how to switch from
  GetConnectionAppArmorSecurityContext() to GetConnectionCredentials().

  content-hub, media-hub, mediascanner2, signon-apparmor-extension,
  ubuntu-download-manager, and ubuntu-system-settings-online-accounts
  all need to transition to the new method of obtaining the AppArmor
  label.

  The apparmor package should be updated to drop the libapparmor-
  mention-dbus-method-in-getcon-man.patch patch and the dbus package
  should be updated to drop the aa-get-connection-apparmor-security-
  context.patch patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 2036180] Re: Please merge dbus 1.14.10-1 (main) from debian unstable (main)

[Olivier Gayot]

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/451441

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

Title:
  Please merge dbus 1.14.10-1 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  dbus 1.14.10-1 was released in Debian unstable. It includes a new
  upstream version but which contains only bug fixes. In addition,
  1.14.10-1 also contains a dbus-user-session fix that we want to
  include in Ubuntu.

  dbus (1.14.10-1) unstable; urgency=medium

* New upstream stable release
  - Fix a dbus-daemon crash during policy reload if a connection belongs
to a user account that has been deleted, or if a Name Service Switch
plugin is broken, on kernels not supporting SO_PEERGROUPS
  - Report the error correctly if getting the groups of a uid fails
  - If a connection has a primary group ID but no supplementary groups,
report the primary group ID in GetConnectionCredentials()
UnixGroupIDs field
* dbus-user-session: Copy XDG_CURRENT_DESKTOP to activation environment.
  Previously this was only done if dbus-x11 was installed.
  This is needed by various freedesktop.org specifications, in particular
  for xdg-desktop-portal (>= 1.17) to choose the correct portal backend
  for a desktop session. Some session managers like gnome-session and
  plasma-workspace already upload this into the activation environment,
  but many older or simpler session managers do not.

   -- Simon McVittie   Fri, 01 Sep 2023 15:41:38 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2036180/+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 2036180] [NEW] Please merge dbus 1.14.10-1 (main) from debian unstable (main)

[Olivier Gayot]

Public bug reported:

dbus 1.14.10-1 was released in Debian unstable. It includes a new
upstream version but which contains only bug fixes. In addition,
1.14.10-1 also contains a dbus-user-session fix that we want to include
in Ubuntu.

dbus (1.14.10-1) unstable; urgency=medium

  * New upstream stable release
- Fix a dbus-daemon crash during policy reload if a connection belongs
  to a user account that has been deleted, or if a Name Service Switch
  plugin is broken, on kernels not supporting SO_PEERGROUPS
- Report the error correctly if getting the groups of a uid fails
- If a connection has a primary group ID but no supplementary groups,
  report the primary group ID in GetConnectionCredentials()
  UnixGroupIDs field
  * dbus-user-session: Copy XDG_CURRENT_DESKTOP to activation environment.
Previously this was only done if dbus-x11 was installed.
This is needed by various freedesktop.org specifications, in particular
for xdg-desktop-portal (>= 1.17) to choose the correct portal backend
for a desktop session. Some session managers like gnome-session and
plasma-workspace already upload this into the activation environment,
but many older or simpler session managers do not.

 -- Simon McVittie   Fri, 01 Sep 2023 15:41:38 +0100

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Gayot (ogayot)
 Status: In Progress

** Changed in: dbus (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Changed in: dbus (Ubuntu)
   Status: New => In Progress

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

Title:
  Please merge dbus 1.14.10-1 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  dbus 1.14.10-1 was released in Debian unstable. It includes a new
  upstream version but which contains only bug fixes. In addition,
  1.14.10-1 also contains a dbus-user-session fix that we want to
  include in Ubuntu.

  dbus (1.14.10-1) unstable; urgency=medium

* New upstream stable release
  - Fix a dbus-daemon crash during policy reload if a connection belongs
to a user account that has been deleted, or if a Name Service Switch
plugin is broken, on kernels not supporting SO_PEERGROUPS
  - Report the error correctly if getting the groups of a uid fails
  - If a connection has a primary group ID but no supplementary groups,
report the primary group ID in GetConnectionCredentials()
UnixGroupIDs field
* dbus-user-session: Copy XDG_CURRENT_DESKTOP to activation environment.
  Previously this was only done if dbus-x11 was installed.
  This is needed by various freedesktop.org specifications, in particular
  for xdg-desktop-portal (>= 1.17) to choose the correct portal backend
  for a desktop session. Some session managers like gnome-session and
  plasma-workspace already upload this into the activation environment,
  but many older or simpler session managers do not.

   -- Simon McVittie   Fri, 01 Sep 2023 15:41:38 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2036180/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated

[Olivier Gayot]

** No longer affects: ubuntu-download-manager (Ubuntu)

** No longer affects: media-hub (Ubuntu)

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

Title:
  The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method
  is deprecated

Status in Ubuntu Online Accounts API:
  Confirmed
Status in snapd:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in biometryd package in Ubuntu:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in dbus package in Ubuntu:
  Triaged
Status in deepin-notifications package in Ubuntu:
  New
Status in lomiri-download-manager package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  When upstream D-Bus merged the AppArmor mediation patches, they did
  not like the GetConnectionAppArmorSecurityContext() bus method.
  Instead, they decided to expose a peer's AppArmor context using the
  org.freedesktop.DBus.GetConnectionCredentials() bus method. All users
  of the GetConnectionAppArmorSecurityContext() method should switch to
  the GetConnectionCredentials() method as soon as possible so that
  Ubuntu can drop the patch that implements
  GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is
  released.

  In order to switch to the new method, you'll need to depend on
  libapparmor 2.10 or newer.

  I'll be adding example code that illustrates how to switch from
  GetConnectionAppArmorSecurityContext() to GetConnectionCredentials().

  content-hub, media-hub, mediascanner2, signon-apparmor-extension,
  ubuntu-download-manager, and ubuntu-system-settings-online-accounts
  all need to transition to the new method of obtaining the AppArmor
  label.

  The apparmor package should be updated to drop the libapparmor-
  mention-dbus-method-in-getcon-man.patch patch and the dbus package
  should be updated to drop the aa-get-connection-apparmor-security-
  context.patch patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated

[Olivier Gayot]

Adding a few packages that are still in the archive and that poped up in
Debian code search for GetConnectionAppArmorSecurityContext [1]


[1] 
https://codesearch.debian.net/search?q=GetConnectionAppArmorSecurityContext=1

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

** No longer affects: lomiri (Ubuntu)

** Also affects: lomiri-download-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: snapd
   Importance: Undecided
   Status: New

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

** Also affects: deepin-notifications (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method
  is deprecated

Status in Ubuntu Online Accounts API:
  Confirmed
Status in snapd:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in biometryd package in Ubuntu:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in dbus package in Ubuntu:
  Triaged
Status in deepin-notifications package in Ubuntu:
  New
Status in lomiri-download-manager package in Ubuntu:
  New
Status in media-hub package in Ubuntu:
  Confirmed
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  When upstream D-Bus merged the AppArmor mediation patches, they did
  not like the GetConnectionAppArmorSecurityContext() bus method.
  Instead, they decided to expose a peer's AppArmor context using the
  org.freedesktop.DBus.GetConnectionCredentials() bus method. All users
  of the GetConnectionAppArmorSecurityContext() method should switch to
  the GetConnectionCredentials() method as soon as possible so that
  Ubuntu can drop the patch that implements
  GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is
  released.

  In order to switch to the new method, you'll need to depend on
  libapparmor 2.10 or newer.

  I'll be adding example code that illustrates how to switch from
  GetConnectionAppArmorSecurityContext() to GetConnectionCredentials().

  content-hub, media-hub, mediascanner2, signon-apparmor-extension,
  ubuntu-download-manager, and ubuntu-system-settings-online-accounts
  all need to transition to the new method of obtaining the AppArmor
  label.

  The apparmor package should be updated to drop the libapparmor-
  mention-dbus-method-in-getcon-man.patch patch and the dbus package
  should be updated to drop the aa-get-connection-apparmor-security-
  context.patch patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated

[Olivier Gayot]

Marking Fix Released for apparmor since the patch was removed in xenial
with
https://git.launchpad.net/ubuntu/+source/apparmor/commit/?id=cf2c6b3637ae003bfbbb5eeb2943f7c59fe47bd7


* ubuntu-download-manager is no longer in the archive
* media-hub is no longer in the archive
* Not sure what the status is for Ubuntu Online Accounts API ? 
online-accounts-api is no longer in the archive but does it mean the task can 
be closed?
* content-hub is still affected.


** Changed in: apparmor (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: apparmor (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method
  is deprecated

Status in Ubuntu Online Accounts API:
  Confirmed
Status in apparmor package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  Confirmed
Status in dbus package in Ubuntu:
  Triaged
Status in media-hub package in Ubuntu:
  Confirmed
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  When upstream D-Bus merged the AppArmor mediation patches, they did
  not like the GetConnectionAppArmorSecurityContext() bus method.
  Instead, they decided to expose a peer's AppArmor context using the
  org.freedesktop.DBus.GetConnectionCredentials() bus method. All users
  of the GetConnectionAppArmorSecurityContext() method should switch to
  the GetConnectionCredentials() method as soon as possible so that
  Ubuntu can drop the patch that implements
  GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is
  released.

  In order to switch to the new method, you'll need to depend on
  libapparmor 2.10 or newer.

  I'll be adding example code that illustrates how to switch from
  GetConnectionAppArmorSecurityContext() to GetConnectionCredentials().

  content-hub, media-hub, mediascanner2, signon-apparmor-extension,
  ubuntu-download-manager, and ubuntu-system-settings-online-accounts
  all need to transition to the new method of obtaining the AppArmor
  label.

  The apparmor package should be updated to drop the libapparmor-
  mention-dbus-method-in-getcon-man.patch patch and the dbus package
  should be updated to drop the aa-get-connection-apparmor-security-
  context.patch patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 2027991] Re: Please merge dbus 1.14.8-2 (main) from debian unstable (main)

[Olivier Gayot]

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/447077

** Description changed:

  Debian has dbus 1.14.8-2 in unstable
  Ubuntu has dbus 1.14.6-1ubuntu1 in mantic
+ 
+ The changes upstream and in Debian are minimal. Those are mostly bug
+ fixes and some adjustments to logging. Therefore, our delta does not
+ need to be changed.

** Changed in: dbus (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

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

Title:
   Please merge dbus 1.14.8-2 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  New

Bug description:
  Debian has dbus 1.14.8-2 in unstable
  Ubuntu has dbus 1.14.6-1ubuntu1 in mantic

  The changes upstream and in Debian are minimal. Those are mostly bug
  fixes and some adjustments to logging. Therefore, our delta does not
  need to be changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2027991/+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 2027991] [NEW] Please merge dbus 1.14.8-2 (main) from debian unstable (main)

[Olivier Gayot]

Public bug reported:

Debian has dbus 1.14.8-2 in unstable
Ubuntu has dbus 1.14.6-1ubuntu1 in mantic

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
   Please merge dbus 1.14.8-2 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  New

Bug description:
  Debian has dbus 1.14.8-2 in unstable
  Ubuntu has dbus 1.14.6-1ubuntu1 in mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2027991/+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 2023301] Re: Please merge dbus 1.14.6-1 (main) from debian unstable (main)

[Olivier Gayot]

** Changed in: dbus (Ubuntu)
   Status: In Progress => New

** Changed in: dbus (Ubuntu)
 Assignee: Olivier Gayot (ogayot) => (unassigned)

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

Title:
  Please merge dbus 1.14.6-1 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  New

Bug description:
  Debian has dbus 1.14.6-1 in unstable
  Ubuntu has dbus 1.14.4-1ubuntu1 in mantic

  Two changes from @waveform have been merged upstream and the relevant
  delta can be dropped in Ubuntu.

   - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
 autopkgtest to the apparmor profile in the test
 [merged upstream in 1.14.6]
  - d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
 packages to permit the resolver to use them to satisfy i386 dependencies
 [merged in debian in 1.14.6-1]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2023301/+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 2023301] Re: Please merge dbus 1.14.6-1 (main) from debian unstable (main)

[Olivier Gayot]

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/92

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

Title:
  Please merge dbus 1.14.6-1 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  New

Bug description:
  Debian has dbus 1.14.6-1 in unstable
  Ubuntu has dbus 1.14.4-1ubuntu1 in mantic

  Two changes from @waveform have been merged upstream and the relevant
  delta can be dropped in Ubuntu.

   - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
 autopkgtest to the apparmor profile in the test
 [merged upstream in 1.14.6]
  - d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
 packages to permit the resolver to use them to satisfy i386 dependencies
 [merged in debian in 1.14.6-1]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2023301/+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 2023301] Re: Please merge dbus 1.14.6-1 (main) from debian unstable (main)

[Olivier Gayot]

** Description changed:

- TODO
+ Debian has dbus 1.14.6-1 in unstable
+ Ubuntu has dbus 1.14.4-1ubuntu1 in mantic
+ 
+ Two changes from @waveform have been merged upstream and the relevant
+ delta can be dropped in Ubuntu.
+ 
+  - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
+autopkgtest to the apparmor profile in the test
+[merged upstream in 1.14.6]
+ - d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
+packages to permit the resolver to use them to satisfy i386 dependencies
+[merged in debian in 1.14.6-1]

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

Title:
  Please merge dbus 1.14.6-1 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  Debian has dbus 1.14.6-1 in unstable
  Ubuntu has dbus 1.14.4-1ubuntu1 in mantic

  Two changes from @waveform have been merged upstream and the relevant
  delta can be dropped in Ubuntu.

   - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
 autopkgtest to the apparmor profile in the test
 [merged upstream in 1.14.6]
  - d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
 packages to permit the resolver to use them to satisfy i386 dependencies
 [merged in debian in 1.14.6-1]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2023301/+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 2023301] [NEW] Please merge dbus 1.14.6-1 (main) from debian unstable (main)

[Olivier Gayot]

Public bug reported:

TODO

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Gayot (ogayot)
 Status: In Progress

** Changed in: dbus (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Changed in: dbus (Ubuntu)
   Status: New => In Progress

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

Title:
  Please merge dbus 1.14.6-1 (main) from debian unstable (main)

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2023301/+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 2018425] Re: apt install ubuntu-desktop takes forever

[Olivier Gayot]

Hello and thank you for your bug report,

Marking invalid for subiquity since there is nothing we can do from the
installer's standpoint. Adding ubuntu-meta (which is the source package
for ubuntu-desktop).

Thanks,
Olivier

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: subiquity
   Status: New => Invalid

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

Title:
  apt install ubuntu-desktop takes forever

Status in subiquity:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Install server 23.04 to take advantage of flexible disk
  partitioning/raid. While installing desktop over the installed server
  (apt install ubuntu-desktop) it proceeds normally about 40% of the way
  but after that it slows down tremendously, hanging for minutes in
  between packages. It eventually (after several hours) completes
  without error.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  3 11:41:00 2023
  InstallationDate: Installed on 2023-04-29 (3 days ago)
  InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 
(20230415)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2018425/+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 2018596] Re: Please merge sysvinit 3.06-4 (main) from Debian unstable (main)

[Olivier Gayot]

** Description changed:

- TODO
+ This is a merge of sysvinit 3.06-4.
+ 
+ The ubuntu delta is unaffected.
+ 
+ Please see the relevant merge proposal.

** Changed in: sysvinit (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: sysvinit (Ubuntu)
 Assignee: Olivier Gayot (ogayot) => (unassigned)

** Description changed:

- This is a merge of sysvinit 3.06-4.
+ This is a merge of sysvinit 3.06-4. Please see the relevant merge
+ proposal.
  
- The ubuntu delta is unaffected.
- 
- Please see the relevant merge proposal.
+ The ubuntu delta is unaffected. We should be able to drop one patch when
+ we will merge the next upstream version (i.e., 3.07) which is currently
+ in debian experimental.

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

Title:
  Please merge sysvinit 3.06-4 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  Confirmed

Bug description:
  This is a merge of sysvinit 3.06-4. Please see the relevant merge
  proposal.

  The ubuntu delta is unaffected. We should be able to drop one patch
  when we will merge the next upstream version (i.e., 3.07) which is
  currently in debian experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2018596/+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 2018596] Re: Please merge sysvinit 3.06-4 (main) from Debian unstable (main)

[Olivier Gayot]

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu/+source/sysvinit/+git/sysvinit/+merge/442512

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

Title:
  Please merge sysvinit 3.06-4 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  In Progress

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2018596/+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 2018596] [NEW] Please merge sysvinit 3.06-4 (main) from Debian unstable (main)

[Olivier Gayot]

Public bug reported:

TODO

** Affects: sysvinit (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Gayot (ogayot)
 Status: In Progress

** Changed in: sysvinit (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Changed in: sysvinit (Ubuntu)
   Status: New => In Progress

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

Title:
  Please merge sysvinit 3.06-4 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  In Progress

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2018596/+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 2007421] Re: Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

[Olivier Gayot]

Tried the git-ubuntu way to do this merge but I'm happy to upload
debdiffs here if it helps.

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

Title:
  Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Debian moved from 3.05-7 to new upstream 3.06-2. As usual, we still
  only want to build sysvinit-utils and not the other binary packages.

  https://salsa.debian.org/debian/sysvinit/-/merge_requests/8 has not
  yet been merged so we need to carry the following patch:

  d/rules: fix installation of 50-ubuntu-logging when building on
  Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2007421/+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 2007421] Re: Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

[Olivier Gayot]

** Description changed:

- TODO
+ Debian moved from 3.05-7 to new upstream 3.06-2. As usual, we still only
+ want to build sysvinit-utils and not the other binary packages.
+ 
+ https://salsa.debian.org/debian/sysvinit/-/merge_requests/8 has not yet
+ been merged so we need to carry the following patch:
+ 
+ d/rules: fix installation of 50-ubuntu-logging when building on
+ Ubuntu

** Changed in: sysvinit (Ubuntu)
   Status: In Progress => New

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

Title:
  Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Debian moved from 3.05-7 to new upstream 3.06-2. As usual, we still
  only want to build sysvinit-utils and not the other binary packages.

  https://salsa.debian.org/debian/sysvinit/-/merge_requests/8 has not
  yet been merged so we need to carry the following patch:

  d/rules: fix installation of 50-ubuntu-logging when building on
  Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2007421/+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 2007421] Re: Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

[Olivier Gayot]

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu/+source/sysvinit/+git/sysvinit/+merge/437440

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

Title:
  Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  In Progress

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2007421/+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 2007421] [NEW] Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

[Olivier Gayot]

Public bug reported:

TODO

** Affects: sysvinit (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Gayot (ogayot)
 Status: In Progress

** Changed in: sysvinit (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Changed in: sysvinit (Ubuntu)
   Status: New => In Progress

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

Title:
  Please merge sysvinit 3.06-2 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  In Progress

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2007421/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

[Olivier Gayot]

** Description changed:

  The following file used to be provided by the lsb-base package in Ubuntu
  and it now supposed to be provided by the sysvinit-utils package.
  
- * etc/lsb/init-functions.d/50-ubuntu-logging
+ * lsb/init-functions.d/50-ubuntu-logging
  
  The file is Ubuntu specific but is not included in Ubuntu using a delta
  from Debian. Instead, the debian source tree includes the file but
  conditional statements in debian/rules makes it absent from the binary
  packages in Debian.
  
  Sadly, when moving the file from src:lsb to src:sysvinit, the
  conditional statements are not consistent anymore, resulting in the file
  being absent from the Ubuntu binary package as well.
  
  Affected version: sysvinit-utils 3.05-7ubuntu1

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

Title:
  Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

Status in sysvinit package in Ubuntu:
  In Progress
Status in sysvinit package in Debian:
  New

Bug description:
  The following file used to be provided by the lsb-base package in
  Ubuntu and it now supposed to be provided by the sysvinit-utils
  package.

  * lsb/init-functions.d/50-ubuntu-logging

  The file is Ubuntu specific but is not included in Ubuntu using a
  delta from Debian. Instead, the debian source tree includes the file
  but conditional statements in debian/rules makes it absent from the
  binary packages in Debian.

  Sadly, when moving the file from src:lsb to src:sysvinit, the
  conditional statements are not consistent anymore, resulting in the
  file being absent from the Ubuntu binary package as well.

  Affected version: sysvinit-utils 3.05-7ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

[Olivier Gayot]

Successfully built on PPA:
https://launchpad.net/~ogayot/+archive/ubuntu/lunar-
proposed/+build/25480923

Files included in sysvinit-utils:
[...]
drwxr-xr-x root/root 0 2023-01-13 10:33 ./lib/lsb/
-rw-r--r-- root/root 11329 2022-09-12 19:11 ./lib/lsb/init-functions
drwxr-xr-x root/root 0 2023-01-13 10:33 ./lib/lsb/init-functions.d/
-rw-r--r-- root/root   658 2022-09-14 20:35 
./lib/lsb/init-functions.d/00-verbose
-rw-r--r-- root/root  3752 2022-09-12 19:11 
./lib/lsb/init-functions.d/50-ubuntu-logging
[...]

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

Title:
  Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

Status in sysvinit package in Ubuntu:
  New
Status in sysvinit package in Debian:
  Unknown

Bug description:
  The following file used to be provided by the lsb-base package in
  Ubuntu and it now supposed to be provided by the sysvinit-utils
  package.

  * etc/lsb/init-functions.d/50-ubuntu-logging

  The file is Ubuntu specific but is not included in Ubuntu using a
  delta from Debian. Instead, the debian source tree includes the file
  but conditional statements in debian/rules makes it absent from the
  binary packages in Debian.

  Sadly, when moving the file from src:lsb to src:sysvinit, the
  conditional statements are not consistent anymore, resulting in the
  file being absent from the Ubuntu binary package as well.

  Affected version: sysvinit-utils 3.05-7ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

[Olivier Gayot]

Adding debdiff. The diff was forwarded to Debian.


** Patch added: "1-3.05-7ubuntu1__3.05-7ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+attachment/5641174/+files/1-3.05-7ubuntu1__3.05-7ubuntu2.debdiff

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

Title:
  Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

Status in sysvinit package in Ubuntu:
  New
Status in sysvinit package in Debian:
  Unknown

Bug description:
  The following file used to be provided by the lsb-base package in
  Ubuntu and it now supposed to be provided by the sysvinit-utils
  package.

  * etc/lsb/init-functions.d/50-ubuntu-logging

  The file is Ubuntu specific but is not included in Ubuntu using a
  delta from Debian. Instead, the debian source tree includes the file
  but conditional statements in debian/rules makes it absent from the
  binary packages in Debian.

  Sadly, when moving the file from src:lsb to src:sysvinit, the
  conditional statements are not consistent anymore, resulting in the
  file being absent from the Ubuntu binary package as well.

  Affected version: sysvinit-utils 3.05-7ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

[Olivier Gayot]

** Bug watch added: Debian Bug tracker #1028586
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028586

** Also affects: sysvinit (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028586
   Importance: Unknown
   Status: Unknown

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

Title:
  Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

Status in sysvinit package in Ubuntu:
  New
Status in sysvinit package in Debian:
  Unknown

Bug description:
  The following file used to be provided by the lsb-base package in
  Ubuntu and it now supposed to be provided by the sysvinit-utils
  package.

  * etc/lsb/init-functions.d/50-ubuntu-logging

  The file is Ubuntu specific but is not included in Ubuntu using a
  delta from Debian. Instead, the debian source tree includes the file
  but conditional statements in debian/rules makes it absent from the
  binary packages in Debian.

  Sadly, when moving the file from src:lsb to src:sysvinit, the
  conditional statements are not consistent anymore, resulting in the
  file being absent from the Ubuntu binary package as well.

  Affected version: sysvinit-utils 3.05-7ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 2002789] [NEW] Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

[Olivier Gayot]

Public bug reported:

The following file used to be provided by the lsb-base package in Ubuntu
and it now supposed to be provided by the sysvinit-utils package.

* etc/lsb/init-functions.d/50-ubuntu-logging

The file is Ubuntu specific but is not included in Ubuntu using a delta
from Debian. Instead, the debian source tree includes the file but
conditional statements in debian/rules makes it absent from the binary
packages in Debian.

Sadly, when moving the file from src:lsb to src:sysvinit, the
conditional statements are not consistent anymore, resulting in the file
being absent from the Ubuntu binary package as well.

Affected version: sysvinit-utils 3.05-7ubuntu1

** Affects: sysvinit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  The following file used to be provided by the lsb-base package in
  Ubuntu and it now supposed to be provided by the sysvinit-utils
  package.

  * etc/lsb/init-functions.d/50-ubuntu-logging

  The file is Ubuntu specific but is not included in Ubuntu using a
  delta from Debian. Instead, the debian source tree includes the file
  but conditional statements in debian/rules makes it absent from the
  binary packages in Debian.

  Sadly, when moving the file from src:lsb to src:sysvinit, the
  conditional statements are not consistent anymore, resulting in the
  file being absent from the Ubuntu binary package as well.

  Affected version: sysvinit-utils 3.05-7ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 1998324] Re: Missing changelog.Debian.gz from sysvinit-utils

[Olivier Gayot]

** Changed in: sysvinit (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 sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1998324

Title:
  Missing changelog.Debian.gz from sysvinit-utils

Status in sysvinit package in Ubuntu:
  Fix Committed

Bug description:
  The binary package sysvinit-utils does not include the
  changelog.Debian.gz file.

  Lintian reports it as an error:

  E: sysvinit-utils: no-changelog usr/share/doc/sysvinit-
  utils/changelog.Debian.gz (non-native package)

  I looked in the sysvinit-utils package in all releases of Ubuntu >=
  Bionic [1] and could not file anywhere ; whereas it's present in
  Debian [2]:

  It strongly suggests that our Delta from Debian is faulty.

  [1]
  https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist

  [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

[Olivier Gayot]

** Changed in: sysvinit (Ubuntu)
 Assignee: Olivier Gayot (ogayot) => (unassigned)

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

Title:
  Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Debian moved to a new upstream version 3.04 => 3.05.
  Since bionic, we only build sysvinit-utils because it is the only package 
marked [essential].
  sysvinit-utils will surely gain more reverse depends because scripts that 
used to be provided by lsb-base are now provided by sysvinit-utils.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998324] Re: Missing changelog.Debian.gz from sysvinit-utils

[Olivier Gayot]

I submitted a debdiff that addresses the issue in lunar as part of the
3.05-7 merge:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325

** Changed in: sysvinit (Ubuntu)
   Status: New => In Progress

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

Title:
  Missing changelog.Debian.gz from sysvinit-utils

Status in sysvinit package in Ubuntu:
  In Progress

Bug description:
  The binary package sysvinit-utils does not include the
  changelog.Debian.gz file.

  Lintian reports it as an error:

  E: sysvinit-utils: no-changelog usr/share/doc/sysvinit-
  utils/changelog.Debian.gz (non-native package)

  I looked in the sysvinit-utils package in all releases of Ubuntu >=
  Bionic [1] and could not file anywhere ; whereas it's present in
  Debian [2]:

  It strongly suggests that our Delta from Debian is faulty.

  [1]
  https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist

  [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

[Olivier Gayot]

Adding debdiff from Ubuntu

** Patch added: "1-3.04-1ubuntu1__3.05-7ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+attachment/5633389/+files/1-3.04-1ubuntu1__3.05-7ubuntu1.debdiff

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

Title:
  Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Debian moved to a new upstream version 3.04 => 3.05.
  Since bionic, we only build sysvinit-utils because it is the only package 
marked [essential].
  sysvinit-utils will surely gain more reverse depends because scripts that 
used to be provided by lsb-base are now provided by sysvinit-utils.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

[Olivier Gayot]

Adding debdiff from Debian.

During the merge, I noticed that the changelog.Debian.gz file is absent
from sysvinit-utils in Ubuntu since we introduced our delta from Debian.
I created
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324 and
fixed it as part of the debdiff.

Successful build in PPA on amd64:
https://launchpad.net/~ogayot/+archive/ubuntu/lunar-proposed/+build/24885473

** Description changed:

- TODO
+ Debian moved to a new upstream version 3.04 => 3.05.
+ Since bionic, we only build sysvinit-utils because it is the only package 
marked [essential].
+ sysvinit-utils will surely gain more reverse depends because scripts that 
used to be provided by lsb-base are now provided by sysvinit-utils.

** Patch added: "1-3.05-7__3.05-7ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+attachment/5633388/+files/1-3.05-7__3.05-7ubuntu1.debdiff

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

Title:
  Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Debian moved to a new upstream version 3.04 => 3.05.
  Since bionic, we only build sysvinit-utils because it is the only package 
marked [essential].
  sysvinit-utils will surely gain more reverse depends because scripts that 
used to be provided by lsb-base are now provided by sysvinit-utils.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998325] [NEW] Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

[Olivier Gayot]

Public bug reported:

TODO

** Affects: sysvinit (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Gayot (ogayot)
 Status: New

** Changed in: sysvinit (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

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

Title:
  Please merge sysvinit 3.05-7 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998324] Re: Missing changelog.Debian.gz from sysvinit-utils

[Olivier Gayot]

** Changed in: sysvinit (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

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

Title:
  Missing changelog.Debian.gz from sysvinit-utils

Status in sysvinit package in Ubuntu:
  New

Bug description:
  The binary package sysvinit-utils does not include the
  changelog.Debian.gz file.

  Lintian reports it as an error:

  E: sysvinit-utils: no-changelog usr/share/doc/sysvinit-
  utils/changelog.Debian.gz (non-native package)

  I looked in the sysvinit-utils package in all releases of Ubuntu >=
  Bionic [1] and could not file anywhere ; whereas it's present in
  Debian [2]:

  It strongly suggests that our Delta from Debian is faulty.

  [1]
  https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist

  [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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 1998324] [NEW] Missing changelog.Debian.gz from sysvinit-utils

[Olivier Gayot]

Public bug reported:

The binary package sysvinit-utils does not include the
changelog.Debian.gz file.

Lintian reports it as an error:

E: sysvinit-utils: no-changelog usr/share/doc/sysvinit-
utils/changelog.Debian.gz (non-native package)

I looked in the sysvinit-utils package in all releases of Ubuntu >=
Bionic [1] and could not file anywhere ; whereas it's present in Debian
[2]:

It strongly suggests that our Delta from Debian is faulty.

[1]
https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist
https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist
https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist
https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist

[2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist

** Affects: sysvinit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Missing changelog.Debian.gz from sysvinit-utils

Status in sysvinit package in Ubuntu:
  New

Bug description:
  The binary package sysvinit-utils does not include the
  changelog.Debian.gz file.

  Lintian reports it as an error:

  E: sysvinit-utils: no-changelog usr/share/doc/sysvinit-
  utils/changelog.Debian.gz (non-native package)

  I looked in the sysvinit-utils package in all releases of Ubuntu >=
  Bionic [1] and could not file anywhere ; whereas it's present in
  Debian [2]:

  It strongly suggests that our Delta from Debian is faulty.

  [1]
  https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist
  https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist

  [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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

[Olivier Gayot]

Jurgen, could you please send us the link to the discussion with
LibreOffice upstream? Thanks!

-- 
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:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

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 1993635] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwer

[Olivier Gayot]

Hi,

/dev/nvme0n1p2719936599636  67836   90% /boot

It looks like your boot partition might have been full during the
upgrade.

Maybe you can try to free up some space or resize the partition?

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

** Changed in: initramfs-tools (Ubuntu)
   Status: Invalid => 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/1993635

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

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/vgubuntu-swap_1)
  I: Set the RESUME variable to override this.
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.15.0-52-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: Fehler beim Bearbeiten des Paketes linux-image-5.15.0-52-generic 
(--configure):
   »installiertes linux-image-5.15.0-52-generic-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  Trigger für initramfs-tools (0.136ubuntu6.7) werden verarbeitet ...
  update-initramfs: Generating /boot/initrd.img-5.15.0-52-generic
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/vgubuntu-swap_1)
  I: Set the RESUME variable to override this.
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.15.0-52-generic with 1.
  dpkg: Fehler beim Bearbeiten des Paketes initramfs-tools (--configure):
   »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  Fehler traten auf beim Bearbeiten von:
   linux-firmware
   linux-image-5.15.0-52-generic
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21
  Uname: Linux 5.14.0-1054-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Oct 20 09:59:35 2022
  ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2021-12-08 (315 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1993635/+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 1993723] Re: package mime-support 3.64ubuntu1 failed to install/upgrade: installed mime-support package post-installation script subprocess returned error exit status 137

[Olivier Gayot]

Seems like an infinite recursion (potentially in the
/usr/share/applications/ directory)

[...]
Deep recursion on subroutine "main::RecurseIntoDirectories" at 
/usr/sbin/update-mime line 124.
Deep recursion on subroutine "main::RecurseIntoDirectories" at 
/usr/sbin/update-mime line 124.
Deep recursion on subroutine "main::RecurseIntoDirectories" at 
/usr/sbin/update-mime line 124.
Deep recursion on subroutine "main::RecurseIntoDirectories" at 
/usr/sbin/update-mime line 124.
Killed

@mdmonirul would you mind pasting the output of

ls -lFd /usr/share/applications
ls -lF /usr/share/applications/

Thanks!

** Changed in: mime-support (Ubuntu)
   Status: New => Incomplete

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

Title:
  package mime-support 3.64ubuntu1 failed to install/upgrade: installed
  mime-support package post-installation script subprocess returned
  error exit status 137

Status in mime-support package in Ubuntu:
  Incomplete

Bug description:
  The system gettibng freeze i wanted to update my system to ubuntu
  22.04 lts

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-50.56~20.04.1-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Oct 20 22:47:35 2022
  ErrorMessage: installed mime-support package post-installation script 
subprocess returned error exit status 137
  InstallationDate: Installed on 2022-01-21 (272 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: mime-support
  Title: package mime-support 3.64ubuntu1 failed to install/upgrade: installed 
mime-support package post-installation script subprocess returned error exit 
status 137
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1993723/+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 1993658] Re: package python3 3.10.6-1~22.04 failed to install/upgrade: el subproceso instalado paquete python3 script post-installation devolvió el código de salida de error 4

[Olivier Gayot]

*** This bug is a duplicate of bug 1972076 ***
https://bugs.launchpad.net/bugs/1972076

** This bug has been marked a duplicate of bug 1972076
   package renpy 7.3.5+dfsg-2 failed to install/upgrade: installed renpy 
package post-installation script subprocess returned error exit status 1

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

Title:
  package python3 3.10.6-1~22.04 failed to install/upgrade: el
  subproceso instalado paquete python3 script post-installation devolvió
  el código de salida de error 4

Status in python3-defaults package in Ubuntu:
  New
Status in renpy package in Ubuntu:
  New

Bug description:
  ERROR

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3 3.10.6-1~22.04
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-headers-5.15.0-48-generic:amd64: Remove
   linux-headers-5.15.0-48:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 20 08:11:25 2022
  ErrorMessage: el subproceso instalado paquete python3 script 
post-installation devolvió el código de salida de error 4
  InstallationDate: Installed on 2022-08-02 (78 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: python3-defaults
  Title: package python3 3.10.6-1~22.04 failed to install/upgrade: el 
subproceso instalado paquete python3 script post-installation devolvió el 
código de salida de error 4
  UpgradeStatus: Upgraded to jammy on 2022-08-27 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1993658/+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 1993658] Re: package python3 3.10.6-1~22.04 failed to install/upgrade: el subproceso instalado paquete python3 script post-installation devolvió el código de salida de error 4

[Olivier Gayot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1972076, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

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

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

Title:
  package python3 3.10.6-1~22.04 failed to install/upgrade: el
  subproceso instalado paquete python3 script post-installation devolvió
  el código de salida de error 4

Status in python3-defaults package in Ubuntu:
  New
Status in renpy package in Ubuntu:
  New

Bug description:
  ERROR

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3 3.10.6-1~22.04
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-headers-5.15.0-48-generic:amd64: Remove
   linux-headers-5.15.0-48:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 20 08:11:25 2022
  ErrorMessage: el subproceso instalado paquete python3 script 
post-installation devolvió el código de salida de error 4
  InstallationDate: Installed on 2022-08-02 (78 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: python3-defaults
  Title: package python3 3.10.6-1~22.04 failed to install/upgrade: el 
subproceso instalado paquete python3 script post-installation devolvió el 
código de salida de error 4
  UpgradeStatus: Upgraded to jammy on 2022-08-27 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1993658/+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

[Olivier Gayot]

** Description changed:

  # 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
+  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)
  
+ 
+ [[Workaround]]
+ echo "APT::Get::Never-Include-Phased-Updates: 1;" > 
/etc/apt/apt.conf.d/99phased-updates
+ 
  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)
+  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)

-- 
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:
  In Progress
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 

[Touch-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

[Olivier Gayot]

** Description changed:

  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal
  
  Expected result:
  * pasted command is not highlighted and is not selected
  
  Actual result:
  * pasted command is selected and highlighted
+ 
+ [[Workaround]]
+ 
+ * On 22.04, add 'set enable-bracketed-paste off' to /etc/inputrc
+ * Starting 22.10, add 'set enable-active-region off' to /etc/inputrc
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Invalid
Status in readline package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  [[Workaround]]

  * On 22.04, add 'set enable-bracketed-paste off' to /etc/inputrc
  * Starting 22.10, add 'set enable-active-region off' to /etc/inputrc

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1987257] Re: Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

[Olivier Gayot]

Successful build on PPA:
https://launchpad.net/~ogayot/+archive/ubuntu/kinetic-
proposed/+build/24303282

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

Title:
  Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  base: 3.01-1
  ubuntu: 3.01-1ubuntu1
  debian: 3.04-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+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 1987257] Re: Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

[Olivier Gayot]

Adding .debdiff from earlier Ubuntu version

** Description changed:

- TODO
+ base: 3.01-1
+ ubuntu: 3.01-1ubuntu1
+ debian: 3.04-1

** Patch added: "1-3.01-1__3.04-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+attachment/5610667/+files/1-3.01-1__3.04-1ubuntu1.debdiff

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

Title:
  Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  base: 3.01-1
  ubuntu: 3.01-1ubuntu1
  debian: 3.04-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+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 1987257] Re: Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

[Olivier Gayot]

Adding .debdiff from new Debian version

** Patch added: "1-3.04-1__3.04-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+attachment/5610668/+files/1-3.04-1__3.04-1ubuntu1.debdiff

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

Title:
  Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  base: 3.01-1
  ubuntu: 3.01-1ubuntu1
  debian: 3.04-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+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 1987257] [NEW] Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

[Olivier Gayot]

Public bug reported:

TODO

** Affects: sysvinit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please merge sysvinit 3.04-1 (main) from Debian unstable (main)

Status in sysvinit package in Ubuntu:
  New

Bug description:
  TODO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+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 1987254] [NEW] Please sync keyutils 1.6.3-1 (main) from Debian unstable (main)

[Olivier Gayot]

Public bug reported:

Hello,

This version of keyutils should be synced from Debian:

keyutils (1.6.3-1) unstable; urgency=medium

  * New upstream release. (Closes: #1012606)
- Add Mark-test-requiring-root-as-such.patch
- Drop endianness-and-PIE.patch
- Refresh patches
  * Update d/watch (switch URL)
  * Bump Standards-Version to 4.6.1 (no changes needed)
  * Update autopkgtest

There is a single Ubuntu change in the current version (i.e.,
1.6.1-3ubuntu1):

- d/p/apply-ttl-records.patch: Add patch to apply default TTL to records
  obtained from getaddrinfo(). (LP: #1962453)

The above patched patch can be dropped because it was back-ported from
upstream [1] and is present in upstream versions starting at 1.6.2 [2].

The Ubuntu changes should be overridden.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/commit/?id=75e7568dc516db698093b33ea273e1b4a30b70be
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/commit/?id=454f80f537e5d1aad506599b6776e4cc1cf5f0f2

Thanks,
Olivier

** Affects: keyutils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please sync keyutils 1.6.3-1 (main) from Debian unstable (main)

Status in keyutils package in Ubuntu:
  New

Bug description:
  Hello,

  This version of keyutils should be synced from Debian:

  keyutils (1.6.3-1) unstable; urgency=medium

* New upstream release. (Closes: #1012606)
  - Add Mark-test-requiring-root-as-such.patch
  - Drop endianness-and-PIE.patch
  - Refresh patches
* Update d/watch (switch URL)
* Bump Standards-Version to 4.6.1 (no changes needed)
* Update autopkgtest

  There is a single Ubuntu change in the current version (i.e.,
  1.6.1-3ubuntu1):

  - d/p/apply-ttl-records.patch: Add patch to apply default TTL to records
obtained from getaddrinfo(). (LP: #1962453)

  The above patched patch can be dropped because it was back-ported from
  upstream [1] and is present in upstream versions starting at 1.6.2
  [2].

  The Ubuntu changes should be overridden.

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/commit/?id=75e7568dc516db698093b33ea273e1b4a30b70be
  [2] 
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/commit/?id=454f80f537e5d1aad506599b6776e4cc1cf5f0f2

  Thanks,
  Olivier

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1987254/+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 1983128] Re: linux-lowlatency fails to build on arm64 due to kernel option settings

[Olivier Gayot]

** Summary changed:

- linux-lowlatency fals to build on arm64 due to kernel option settings
+ linux-lowlatency fails to build on arm64 due to kernel option settings

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

Title:
  linux-lowlatency fails to build on arm64 due to kernel option settings

Status in linux-lowlatency package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a 
kinetic-proposed migration process (for zlib) and runs into a 'regression':
  "autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: 
Regression ♻"

  The regression is highly likely not due to zlib itself, but due to NEW kernel 
options, that don't have a default yet and a check-config FAIL, see:
  ...
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config: 
loading config
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations 
loading annotations
  check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
   -, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
  check-config: 11323/11324 checks passed -- exit 1
  ...
  Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
  Error in reading or end of file.
  ...
  Initialize kernel stack variables at function entry
  > 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
    2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
    3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
  choice[1-3?]:
  Error in reading or end of file.
  ...

  Full log is here:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz

  (this might be caused by the recent compiler update)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1983128/+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 1974223] Re: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal

[Olivier Gayot]

Based on my tests, the patch
1-1.1ubuntu1.18.04.14__1.1ubuntu1.18.04.15.debdiff for bionic is still
relevant.

unattended-upgrades FTBFS in bionic ; and the patch fixes it:

https://launchpad.net/~ogayot/+archive/ubuntu/bionic-
proposed/+build/24162373

During autopkgtest run, the error described in comment #9 is not
reproduced in the bionic series so there should be no need for clearing
__pycache__.

https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-ogayot-bionic-
proposed/bionic/amd64/u/unattended-
upgrades/20220712_094142_9df41@/log.gz

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Incomplete => Confirmed

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

Title:
  FTBFS and autopkgtest failure since changes in apt for automatic
  kernel removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Focal:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]
  Since the following changes in apt have landed in focal-updates (and is 
currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest 
on both series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

  [Test plan]
  1. focal:
* run autopkgtest against -updates:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates 
--test-name run-tests -- 
* try to build the package
  2. bionic:
* run autopkgtest against -proposed:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed 
--test-name run-tests -- 
* try to build the package

  [Where problems could occur]
* The fix only affects the test-suite (that runs both at build time & 
autopkgtest time) so the impact should be minimal. Something wrong in the patch 
would make the unattended package FTBFS or fail autopkgtest but it is already 
failing ATM.
* The new tests dependency on apt can trigger more autopkgtest runs. Since 
unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight 
impact on the queues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1974223] Re: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal

[Olivier Gayot]

Hi Robie,

Julian asked the release team to drop the change from focal-proposed because it 
would fail on production autopkgtest (although the upload did fix the FTBFS).
It requires further investigation for focal (I'm trying to free up some time to 
work on it).

I'd like Julian to confirm but my gut feeling is that it can stay in
-proposed for bionic and be uploaded to -updates when another fix must
be delivered. I'm not too familiar with this process myself.

For focal, it's a bit different because unattended-upgrades blocks
another SRU: https://bugs.launchpad.net/ubuntu/focal/+source/unattended-
upgrades/+bug/1747499

I will try to do what's necessary ASAP.

Thanks,
Olivier

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

Title:
  FTBFS and autopkgtest failure since changes in apt for automatic
  kernel removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Incomplete
Status in unattended-upgrades source package in Focal:
  Incomplete
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]
  Since the following changes in apt have landed in focal-updates (and is 
currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest 
on both series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

  [Test plan]
  1. focal:
* run autopkgtest against -updates:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates 
--test-name run-tests -- 
* try to build the package
  2. bionic:
* run autopkgtest against -proposed:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed 
--test-name run-tests -- 
* try to build the package

  [Where problems could occur]
* The fix only affects the test-suite (that runs both at build time & 
autopkgtest time) so the impact should be minimal. Something wrong in the patch 
would make the unattended package FTBFS or fail autopkgtest but it is already 
failing ATM.
* The new tests dependency on apt can trigger more autopkgtest runs. Since 
unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight 
impact on the queues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

[Olivier Gayot]

I forwarded d/p/apply-ttl-to-records.patch to Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012606

** Bug watch added: Debian Bug tracker #1012606
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012606

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

Title:
  Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

Status in keyutils package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu delta contains two patches:

  * d/p/private-priv.patch:
  This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was 
a C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
  The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
  If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and include the C header in C++ code. 
Here is the list of packages that build-depends on libkeyutils-dev:
    * bcachefs-tools
    * ceph
    * cifs-utils
    * ecryptfs-utils
    * gdm3
    * gssproxy
    * ima-evm-utils
    * kafs-client
    * krb5
    * kstart
    * ndctl
    * nfs-utils
    * python-keyutils
    * sssd
    * stress-ng
  All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.

  * d/p/apply-ttl-to-records.patch:
  This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+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 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

[Olivier Gayot]

** Description changed:

  The Ubuntu delta contains two patches:
  
  * d/p/private-priv.patch:
  This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was 
a C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
  The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
- If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and use include the C header in C++ 
code. Here is the list of packages that build-depends on libkeyutils-dev:
-   * bcachefs-tools
-   * ceph
-   * cifs-utils
-   * ecryptfs-utils
-   * gdm3
-   * gssproxy
-   * ima-evm-utils
-   * kafs-client
-   * krb5
-   * kstart
-   * ndctl
-   * nfs-utils
-   * python-keyutils
-   * sssd
-   * stress-ng
+ If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and include the C header in C++ code. 
Here is the list of packages that build-depends on libkeyutils-dev:
+   * bcachefs-tools
+   * ceph
+   * cifs-utils
+   * ecryptfs-utils
+   * gdm3
+   * gssproxy
+   * ima-evm-utils
+   * kafs-client
+   * krb5
+   * kstart
+   * ndctl
+   * nfs-utils
+   * python-keyutils
+   * sssd
+   * stress-ng
  All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.
  
  * d/p/apply-ttl-to-records.patch:
  This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

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

Title:
  Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

Status in keyutils package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu delta contains two patches:

  * d/p/private-priv.patch:
  This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was 
a C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
  The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
  If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and include the C header in C++ code. 
Here is the list of packages that build-depends on libkeyutils-dev:
    * bcachefs-tools
    * ceph
    * cifs-utils
    * ecryptfs-utils
    * gdm3
    * gssproxy
    * ima-evm-utils
    * kafs-client
    * krb5
    * kstart
    * ndctl
    * nfs-utils
    * python-keyutils
    * sssd
    * stress-ng
  All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.

  * d/p/apply-ttl-to-records.patch:
  This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+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 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

[Olivier Gayot]

Debdiff from Ubuntu

** Patch added: "Debdiff from ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+attachment/5595637/+files/1-keyutils_1.6.1-2ubuntu3__1.6.1-3ubuntu1.debdiff

** Changed in: keyutils (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

Status in keyutils package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu delta contains two patches:

  * d/p/private-priv.patch:
  This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was 
a C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
  The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
  If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and use include the C header in C++ 
code. Here is the list of packages that build-depends on libkeyutils-dev:
* bcachefs-tools
* ceph
* cifs-utils
* ecryptfs-utils
* gdm3
* gssproxy
* ima-evm-utils
* kafs-client
* krb5
* kstart
* ndctl
* nfs-utils
* python-keyutils
* sssd
* stress-ng
  All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.

  * d/p/apply-ttl-to-records.patch:
  This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+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 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

[Olivier Gayot]

Adding debdiff from Debian

** Patch added: "Debdiff from debian 1.6.1-3"
   
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+attachment/5595636/+files/1-keyutils_1.6.1-3__1.6.1-3ubuntu1.debdiff

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

Title:
  Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

Status in keyutils package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu delta contains two patches:

  * d/p/private-priv.patch:
  This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was 
a C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
  The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
  If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and use include the C header in C++ 
code. Here is the list of packages that build-depends on libkeyutils-dev:
* bcachefs-tools
* ceph
* cifs-utils
* ecryptfs-utils
* gdm3
* gssproxy
* ima-evm-utils
* kafs-client
* krb5
* kstart
* ndctl
* nfs-utils
* python-keyutils
* sssd
* stress-ng
  All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.

  * d/p/apply-ttl-to-records.patch:
  This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+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 1977982] [NEW] Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

[Olivier Gayot]

Public bug reported:

The Ubuntu delta contains two patches:

* d/p/private-priv.patch:
This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was a 
C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
If we drop this, there is a chance, however, that other packages would FTBFS if 
they build-depends on libkeyutils-dev and use include the C header in C++ code. 
Here is the list of packages that build-depends on libkeyutils-dev:
  * bcachefs-tools
  * ceph
  * cifs-utils
  * ecryptfs-utils
  * gdm3
  * gssproxy
  * ima-evm-utils
  * kafs-client
  * krb5
  * kstart
  * ndctl
  * nfs-utils
  * python-keyutils
  * sssd
  * stress-ng
All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.

* d/p/apply-ttl-to-records.patch:
This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

** Affects: keyutils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

Status in keyutils package in Ubuntu:
  New

Bug description:
  The Ubuntu delta contains two patches:

  * d/p/private-priv.patch:
  This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was 
a C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
  The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
  If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and use include the C header in C++ 
code. Here is the list of packages that build-depends on libkeyutils-dev:
* bcachefs-tools
* ceph
* cifs-utils
* ecryptfs-utils
* gdm3
* gssproxy
* ima-evm-utils
* kafs-client
* krb5
* kstart
* ndctl
* nfs-utils
* python-keyutils
* sssd
* stress-ng
  All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.

  * d/p/apply-ttl-to-records.patch:
  This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+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 1976619] Re: Version 7.81 breaks support for multi-line header

[Olivier Gayot]

** Bug watch added: Debian Bug tracker #1012263
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012263

** Also affects: curl (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012263
   Importance: Unknown
   Status: Unknown

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

Title:
  Version 7.81 breaks support for multi-line header

Status in curl package in Ubuntu:
  Confirmed
Status in python-tornado package in Ubuntu:
  New
Status in curl package in Debian:
  Unknown

Bug description:
  In curl 7.81, the support of multi-line headers is broken.

  
  This causes regressions in python-tornado:

  ```
  self.stop()
  
  timeout_handle = self.add_timeout(self.time() + timeout, 
timeout_callback)
  self.start()
  if timeout is not None:
  self.remove_timeout(timeout_handle)
  assert future_cell[0] is not None
  if future_cell[0].cancelled() or not future_cell[0].done():
  raise TimeoutError("Operation timed out after %s seconds" % 
timeout)
  >   return future_cell[0].result()
  E   tornado.curl_httpclient.CurlError: HTTP 599: Header without colon
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1976619/+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 1976619] Re: Version 7.81 breaks support for multi-line header

[Olivier Gayot]

Adding debdiff (applied upstream patch).
Will forward to Debian.

** Patch added: "1-7.83.1-1__7.83.1-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1976619/+attachment/5594503/+files/1-7.83.1-1__7.83.1-1ubuntu1.debdiff

** Changed in: curl (Ubuntu)
   Status: New => Confirmed

** Tags added: update-excuse

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

Title:
  Version 7.81 breaks support for multi-line header

Status in curl package in Ubuntu:
  Confirmed
Status in python-tornado package in Ubuntu:
  New

Bug description:
  In curl 7.81, the support of multi-line headers is broken.

  
  This causes regressions in python-tornado:

  ```
  self.stop()
  
  timeout_handle = self.add_timeout(self.time() + timeout, 
timeout_callback)
  self.start()
  if timeout is not None:
  self.remove_timeout(timeout_handle)
  assert future_cell[0] is not None
  if future_cell[0].cancelled() or not future_cell[0].done():
  raise TimeoutError("Operation timed out after %s seconds" % 
timeout)
  >   return future_cell[0].result()
  E   tornado.curl_httpclient.CurlError: HTTP 599: Header without colon
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1976619/+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 1976619] Re: Version 7.81 breaks support for multi-line header

[Olivier Gayot]

Bug report in tornado: https://github.com/tornadoweb/tornado/issues/3143
Bug report in curl: https://github.com/curl/curl/issues/8844

A fixed was merged upstream in curl.

** Also affects: python-tornado (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Version 7.81 breaks support for multi-line header

Status in curl package in Ubuntu:
  New
Status in python-tornado package in Ubuntu:
  New

Bug description:
  In curl 7.81, the support of multi-line headers is broken.

  
  This causes regressions in python-tornado:

  ```
  self.stop()
  
  timeout_handle = self.add_timeout(self.time() + timeout, 
timeout_callback)
  self.start()
  if timeout is not None:
  self.remove_timeout(timeout_handle)
  assert future_cell[0] is not None
  if future_cell[0].cancelled() or not future_cell[0].done():
  raise TimeoutError("Operation timed out after %s seconds" % 
timeout)
  >   return future_cell[0].result()
  E   tornado.curl_httpclient.CurlError: HTTP 599: Header without colon
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1976619/+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 1976619] [NEW] Version 7.81 breaks support for multi-line header

[Olivier Gayot]

Public bug reported:

In curl 7.81, the support of multi-line headers is broken.


This causes regressions in python-tornado:

```
self.stop()

timeout_handle = self.add_timeout(self.time() + timeout, 
timeout_callback)
self.start()
if timeout is not None:
self.remove_timeout(timeout_handle)
assert future_cell[0] is not None
if future_cell[0].cancelled() or not future_cell[0].done():
raise TimeoutError("Operation timed out after %s seconds" % timeout)
>   return future_cell[0].result()
E   tornado.curl_httpclient.CurlError: HTTP 599: Header without colon
```

** Affects: curl (Ubuntu)
 Importance: Undecided
     Assignee: Olivier Gayot (ogayot)
 Status: New

** Affects: python-tornado (Ubuntu)
 Importance: Undecided
 Status: New

** Changed in: curl (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Bug watch added: github.com/tornadoweb/tornado/issues #3143
   https://github.com/tornadoweb/tornado/issues/3143

** Bug watch added: github.com/curl/curl/issues #8844
   https://github.com/curl/curl/issues/8844

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

Title:
  Version 7.81 breaks support for multi-line header

Status in curl package in Ubuntu:
  New
Status in python-tornado package in Ubuntu:
  New

Bug description:
  In curl 7.81, the support of multi-line headers is broken.

  
  This causes regressions in python-tornado:

  ```
  self.stop()
  
  timeout_handle = self.add_timeout(self.time() + timeout, 
timeout_callback)
  self.start()
  if timeout is not None:
  self.remove_timeout(timeout_handle)
  assert future_cell[0] is not None
  if future_cell[0].cancelled() or not future_cell[0].done():
  raise TimeoutError("Operation timed out after %s seconds" % 
timeout)
  >   return future_cell[0].result()
  E   tornado.curl_httpclient.CurlError: HTTP 599: Header without colon
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1976619/+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 1974223] Re: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal

[Olivier Gayot]

** Description changed:

- Since the following changes in apt have landed in focal-updates (and is
- currently in bionic-proposed), unattended-upgrades FTBFS on both series:
+ [Impact]
+ Since the following changes in apt have landed in focal-updates (and is 
currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest 
on both series:
  
    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)
  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm
+ 
+ [Test plan]
+ 1. focal:
+   * run autopkgtest against -updates:
+ $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates 
--test-name run-tests -- 
+   * try to build the package
+ 2. bionic:
+   * run autopkgtest against -proposed:
+ $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed 
--test-name run-tests -- 
+   * try to build the package
+ 
+ [Where problems could occur]
+   * The fix only affects the test-suite (that runs both at build time & 
autopkgtest time) so the impact should be minimal. Something wrong in the patch 
would make the unattended package FTBFS or fail autopkgtest but it is already 
failing ATM.
+   * The new tests dependency on apt can trigger more autopkgtest runs. Since 
unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight 
impact on the queues.

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

Title:
  FTBFS and autopkgtest failure since changes in apt for automatic
  kernel removal

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]
  Since the following changes in apt have landed in focal-updates (and is 
currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest 
on both series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

  [Test plan]
  1. focal:
* run autopkgtest against -updates:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates 
--test-name run-tests -- 
* try to build the package
  2. bionic:
* run autopkgtest against -proposed:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed 
--test-name run-tests -- 
* try to build the package

  [Where problems could occur]
* The fix only affects the test-suite (that runs both at build time & 
autopkgtest time) so the impact should be minimal. Something wrong in the patch 
would make the unattended package FTBFS or fail autopkgtest but it is already 
failing ATM.
* The new tests dependency on apt can trigger more autopkgtest runs. Since 
unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight 
impact on the queues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1974223] Re: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal

[Olivier Gayot]

** Summary changed:

- FTBFS since changes in apt for automatic kernel removal
+ FTBFS and autopkgtest failure since changes in apt for automatic kernel 
removal

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

Title:
  FTBFS and autopkgtest failure since changes in apt for automatic
  kernel removal

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  Since the following changes in apt have landed in focal-updates (and
  is currently in bionic-proposed), unattended-upgrades FTBFS on both
  series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1974223] Re: FTBFS since changes in apt for automatic kernel removal

[Olivier Gayot]

** Description changed:

- Since the following changes in apt have landed in focal-updates and
- bionic-updates, unattended-upgrades FTBFS on both series:
+ Since the following changes in apt have landed in focal-updates (and
+ will land in bionic-updates), unattended-upgrades FTBFS on both series:
  
-   * Revert "Protect currently running kernel at run-time"
-   * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
- 2.4.5; including the change to only protect two kernels, not last 
installed
- one (LP: #1968154)
- 
+   * Revert "Protect currently running kernel at run-time"
+   * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
+ 2.4.5; including the change to only protect two kernels, not last 
installed
+ one (LP: #1968154)
  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
-   File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
- haystack))
+   File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
+ haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

** Description changed:

- Since the following changes in apt have landed in focal-updates (and
- will land in bionic-updates), unattended-upgrades FTBFS on both series:
+ Since the following changes in apt have landed in focal-updates (and is
+ currently in bionic-proposed), unattended-upgrades FTBFS on both series:
  
    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)
  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

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

Title:
  FTBFS since changes in apt for automatic kernel removal

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  Since the following changes in apt have landed in focal-updates (and
  is currently in bionic-proposed), unattended-upgrades FTBFS on both
  series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1974223] Re: FTBFS since changes in apt for automatic kernel removal

[Olivier Gayot]

Adding debdiff for bionic

** Patch added: "debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+attachment/5591353/+files/1-1.1ubuntu1.18.04.14__1.1ubuntu1.18.04.15.debdiff

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

Title:
  FTBFS since changes in apt for automatic kernel removal

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  Since the following changes in apt have landed in focal-updates and
  bionic-updates, unattended-upgrades FTBFS on both series:

* Revert "Protect currently running kernel at run-time"
* Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1974223] Re: FTBFS since changes in apt for automatic kernel removal

[Olivier Gayot]

Adding debdiff for focal

** Patch added: "debdiff for focal"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+attachment/5591354/+files/1-2.3ubuntu0.2__2.3ubuntu0.3.debdiff

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => In Progress

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

Title:
  FTBFS since changes in apt for automatic kernel removal

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  Since the following changes in apt have landed in focal-updates and
  bionic-updates, unattended-upgrades FTBFS on both series:

* Revert "Protect currently running kernel at run-time"
* Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1974223] [NEW] FTBFS since changes in apt for automatic kernel removal

[Olivier Gayot]

Public bug reported:

Since the following changes in apt have landed in focal-updates and
bionic-updates, unattended-upgrades FTBFS on both series:

  * Revert "Protect currently running kernel at run-time"
  * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
2.4.5; including the change to only protect two kernels, not last installed
one (LP: #1968154)


==
FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
haystack))
AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
     Assignee: Olivier Gayot (ogayot)
 Status: New

** Affects: unattended-upgrades (Debian)
 Importance: Unknown
 Status: Unknown

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Bug watch added: Debian Bug tracker #980638
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980638

** Also affects: unattended-upgrades (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980638
   Importance: Unknown
   Status: Unknown

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

Title:
  FTBFS since changes in apt for automatic kernel removal

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  Since the following changes in apt have landed in focal-updates and
  bionic-updates, unattended-upgrades FTBFS on both series:

* Revert "Protect currently running kernel at run-time"
* Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

The package FTBFS against -proposed but builds successfully against the
-release pocket.

Based on the error, it seems related to recent changes in how apt
determines kernels that can be autoremoved.

apt (2.0.7) focal; urgency=medium

  * Revert "Protect currently running kernel at run-time"
  * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
2.4.5; including the change to only protect two kernels, not last installed
one (LP: #1968154)

 -- Julian Andres Klode   Mon, 25 Apr 2022 15:58:46
+0200

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Focal:
  Fix Committed
Status in update-notifier source package in Focal:
  Fix Committed

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

Trying to validate this upload but unattended-upgrades failed to build
with:

Applying pinning: PkgFilePin(id=0, priority=-32768)
Applying pin -32768 to package_file: >/test/root.unused-deps/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_lucid-updates_main_binary-amd64_Packages'
  a=lucid-updates,c=main,v=10.04,o=Ubuntu,l=Ubuntu arch='amd64' 
site='archive.ubuntu.com' IndexType='Debian Package Index' Size=106 ID:0>
Using 
(^linux-image-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^.*-modules-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^linux-headers-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$)
 regexp to find kernel packages
Using 
(^linux-image-5\.4\.0\-109\-generic$|^linux-image-5\.4\.0\-109$|^.*-modules-5\.4\.0\-109\-generic$|^.*-modules-5\.4\.0\-109$|^linux-headers-5\.4\.0\-109\-generic$|^linux-headers-5\.4\.0\-109$)
 regexp to find running kernel packages
{'old-unused-dependency', 'any-old-unused-modules'}
Keeping auto-removable test-package-dependency package(s) because it would also 
remove the following packages which should be kept in this step: 
old-unused-dependency
The following packages are marked for installation or upgrade which is not 
allowed when performing autoremovals: forbidden-dependency
.
==
FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 164, in 
test_remove_unused_dependencies_new_unused_only
self.assertTrue(needle_kernel_good in haystack,
AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm
' in '2022-05-10 20:56:21,336 INFO Starting unattended upgrades script

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Focal:
  Fix Committed
Status in update-notifier source package in Focal:
  Fix Committed

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger 

[Touch-packages] [Bug 1971425] Re: The "look" cli dictionary only sees capitalized words

[Olivier Gayot]

There seems to be something wrong with the way the ignore-case option is
handled:

   -f, --ignore-case   fold lower case to upper case characters

The option is enabled by default when running `look ` and the only
way to disable it is to specify the wordlist as the next positional
parameter.

```
$ look accident
> KO (-f is enabled by default)
$ look accident /usr/share/dict/words
accident
accidental
accidentally
accidental's
accidentals
accident's
accidents
> OK (-f is not enabled)
$ look -f accident /usr/share/dict/words
> KO
```

Also, look was provided by bsdmainutils (i.e., src:bsdmainutils) in
focal but bsdextrautils (i.e., src:util-linux) in impish/jammy. This is
a different implemention. I wonder if the assumption on the sorting
order or the dictionary is the same.

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

Title:
  The "look" cli dictionary only sees capitalized words

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04;
  ~ > look accident
  accident
  accident's
  accidental
  accidental's
  accidentally
  accidentals
  accidents
  In Ubuntu 22.04;
  ~ > look accident
  (nothing)
  ~ > look acc
  Accenture
  Accenture's
  Accra
  Accra's
  Digging deeper; the dictionary at /usr/share/dict/words seems OK.
  If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it 
works;
  ~ > ./look accident
  accident
  accidental
  accidentally
  accidental's
  accidentals
  accident's
  accidents

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bsdextrautils 2.37.2-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue May  3 14:19:57 2022
  InstallationDate: Installed on 2018-09-07 (1334 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

Moving the packages to Fix Released since the patches were already in
Jammy:

update-notifier - fixed in 3.192.47:
http://changelogs.ubuntu.com/changelogs/pool/main/u/update-
notifier/update-notifier_3.192.54/changelog

unattended-upgrades - fixed in 2.8ubuntu1:
http://changelogs.ubuntu.com/changelogs/pool/main/u/unattended-
upgrades/unattended-upgrades_2.8ubuntu1/changelog

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: update-notifier (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Focal:
  In Progress
Status in update-notifier source package in Focal:
  In Progress

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

** Tags added: fr-1788

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Focal:
  New
Status in update-notifier source package in Focal:
  New

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

** Description changed:

+ 
+ [Impact]
+ 
+  * If a system is using canonical livepatch, has it enabled, and patches
+ are applied, it could be confusing for a user to receive a "system
+ restart required" messages in the MOTD when logging in.
+ 
+  * Livepatch is available on LTS releases. Thus, the users can be
+ confused following a kernel update on 20.04.
+ 
+  * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
+ Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.
+ 
+ [Test Plan]
+ 
+  * how to reproduce the bug:
+ 
+1. Install and boot a 20.04 server VM
+2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
+3. Enable Livepatch using the following command:
+$ ua attach # replace  by an actual contract token
+4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
+5. Upon logging in again, the motd will show ***System restart required***.
+ 
+  * other testing appropriate to perform before landing this update:
+ 
+   * Making sure that the patch has no impact when livepatch is not enabled.
+   * The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.
+ 
+ [Where problems could occur]
+ 
+  * The change updates a hook script in /etc/kernel/postinst.d/. Scripts
+ in this directory are executing when upgrading / installing a kernel. If
+ somehow the script is broken, it can prevent dpkg for succeeding when
+ upgrading / installing the kernel.
+ 
+  * If the implementation is wrong, we might end up "losing" the
+ ***System restart required*** message when livepatch is disabled
+ 
+ [Original bug description]
+ 
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.
  
  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly used
  in their updated versions. Examples that come to mind are libc and the
  kernel.
  
  There is a secondary file that can be created which says which packages
  requested the reboot. That would be /var/run/reboot-required.pkgs
  
  Ideally that script should not print out the reboot required message if
  a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.
  
  For (a), one can use the command "ubuntu-advantage is-livepatch-enabled"
  and check $?. That is in the ubuntu-advantage-tools package.

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is 

[Touch-packages] [Bug 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

** Patch added: "debdiff for update-notifier (focal)"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5583992/+files/1-update-notifier-3.192.30.10.3.192.30.11.debdiff

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

** Patch added: "debdiff for unattended-upgrades (focal)"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5583991/+files/1-unattended-upgrades-2.3ubuntu0.1-2.3ubuntu1.debdiff

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Olivier Gayot]

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

[Olivier Gayot]

** Changed in: python-testtools (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  Fix Released

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+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 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

[Olivier Gayot]

We agreed to submit this patch to Debian before sponsoring.

I just found out that a pull request by the original author of the patch
in Ubuntu already exists: https://salsa.debian.org/openstack-
team/python/python-testtools/-/merge_requests/5

Thanks,
Olivier

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  Confirmed

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+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 1424768] Re: Consider switching to path based activation

[Olivier Gayot]

** Patch added: "debdiff for whoopsie-preferences"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+attachment/5562562/+files/1-whoopsie-preferences_22build1_23.debdiff

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

Title:
  Consider switching to path based activation

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Bionic:
  Confirmed

Bug description:
  1)  Ubuntu 15.04
  2) 0.2.46
  3) Whoopsie to only run when it is needed.
  4) Instead it runs constantly, using network activity, l
  See bug (there are more..):
  https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481
  also try: sudo fnotifystat -p whoopsie

  Instead whoopsie should use path based activation to only run when
  /var/crash has changed.

  http://www.freedesktop.org/software/systemd/man/systemd.path.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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 1424768] Re: Consider switching to path based activation

[Olivier Gayot]

Adding last debdiff for the whoopsie package.

This is based on
https://code.launchpad.net/~ogayot/whoopsie/whoopsie/+merge/414804 and
adds the actual path-based activation for whoopsie.

Thanks

** Patch added: "debdiff for whoopsie"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+attachment/5562563/+files/1-whoopsie_0.2.76build1_0.2.77.debdiff

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

Title:
  Consider switching to path based activation

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Bionic:
  Confirmed

Bug description:
  1)  Ubuntu 15.04
  2) 0.2.46
  3) Whoopsie to only run when it is needed.
  4) Instead it runs constantly, using network activity, l
  See bug (there are more..):
  https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481
  also try: sudo fnotifystat -p whoopsie

  Instead whoopsie should use path based activation to only run when
  /var/crash has changed.

  http://www.freedesktop.org/software/systemd/man/systemd.path.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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 1424768] Re: Consider switching to path based activation

[Olivier Gayot]

** Patch added: "debdiff for update-notifier"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+attachment/5562561/+files/1-update-notifier_3.192.49_3.192.50.debdiff

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

Title:
  Consider switching to path based activation

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Bionic:
  Confirmed

Bug description:
  1)  Ubuntu 15.04
  2) 0.2.46
  3) Whoopsie to only run when it is needed.
  4) Instead it runs constantly, using network activity, l
  See bug (there are more..):
  https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481
  also try: sudo fnotifystat -p whoopsie

  Instead whoopsie should use path based activation to only run when
  /var/crash has changed.

  http://www.freedesktop.org/software/systemd/man/systemd.path.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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 1424768] Re: Consider switching to path based activation

[Olivier Gayot]

** Patch added: "debdiff for apport"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+attachment/5562560/+files/1-apport_2.20.11_2.20.12.debdiff

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

Title:
  Consider switching to path based activation

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Bionic:
  Confirmed

Bug description:
  1)  Ubuntu 15.04
  2) 0.2.46
  3) Whoopsie to only run when it is needed.
  4) Instead it runs constantly, using network activity, l
  See bug (there are more..):
  https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481
  also try: sudo fnotifystat -p whoopsie

  Instead whoopsie should use path based activation to only run when
  /var/crash has changed.

  http://www.freedesktop.org/software/systemd/man/systemd.path.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

[Olivier Gayot]

** Changed in: python-testtools (Ubuntu)
 Assignee: Olivier Gayot (ogayot) => (unassigned)

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  Confirmed

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+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 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

[Olivier Gayot]

Hello,

In version 2.5.0-2ubuntu1, we had a patch fixing a FTBFS issue with Python 3.10 
and declaring the package as Python 3.10 compatible (including updates to 
setup.cfg and to the list of environments for TOX).
 * debian/patches/add-python-3.10-support.patch
This patch was applied from upstream [1]

In 2.5.0-3, Debian fixed the FTBFS as well with a custom patch [2]. This is the 
only change in this version. Although it fixes the FTBFS, it does not declare 
the package as Python 3.10 compatible.
 * debian/patches/fix-testing-test_syntax_error.patch

Syncing from Debian here would definitely be an option. However, it
would mean we have the package marked compatible with Python 3.10 on
impish (version 2.5.0-2-ubuntu1) but not on jammy (version 2.5.0-2) ;
which would not be great...

Therefore, I decided to go for the merge option and keep our patch while
discarding the one from Debian.

I uploaded the result of the merge (basically a no-op) in a PPA. Build log 
available here:
https://launchpad.net/~ogayot/+archive/ubuntu/jammy-proposed/+build/23142775

Please let me know if a sync would be more sensible. I'll be happy to
turn this into a sync request.

Thanks,
Olivier

[1] 
https://github.com/testing-cabal/testtools/commit/ec9bb7ed026566688a14be9d8d5d1e4c506e71c0
[2] 
https://salsa.debian.org/openstack-team/python/python-testtools/-/commit/fbf2d78b6215f81e8eca29a3ea9fb64fa2e2ab32

** Changed in: python-testtools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  Confirmed

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+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 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

[Olivier Gayot]

** Patch added: "Patch between 2.5.0-2ubuntu1 and 2.5.0-3ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+attachment/5559657/+files/1-2.5.0-2ubuntu1_2.5.0-3ubuntu1.debdiff

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+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 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

[Olivier Gayot]

** Patch added: "Patch between 2.5.0-3 and 2.5.0-3ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+attachment/5559656/+files/1-2.5.0-3_2.5.0-3ubuntu1.debdiff

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+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