[Touch-packages] [Bug 1983730] Re: opt out of phased updates - still shown

2022-08-05 Thread Julian Andres Klode
Will have a look at the normal hold situation, but would like to know
where you see the disagreement in numbers - is it apt update and apt
full-upgrade?

What does motd / update-notifier say?

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

Title:
  opt out of phased updates - still shown

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  when opting out of phased updates, apt still tells me that there are
  updates.

  Expected behaviour: should hide those updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1983730/+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 1983730] Re: opt out of phased updates - still shown

2022-08-05 Thread Julian Andres Klode
I assume this is for the new implementation in 2.4.6. This is
unfortunately not feasible as the code works the same way as upgrades
held back for other reasons.

Some hacks could be added that improve this in most situations but that
also requires significant refactoring and does not solve all the cases.

The key take away is that there is a difference between how many
packages are upgradable themselves and how many packages can actually be
upgraded.

We can make the former more correct, if that is also implemented for
other holds, I don't know, but there can always be a difference that you
see n available upgrades, but only k are actually upgradable.

** Changed in: apt (Ubuntu)
   Status: New => Won't Fix

** Changed in: apt (Ubuntu)
   Status: Won't Fix => Triaged

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

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

Title:
  opt out of phased updates - still shown

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  when opting out of phased updates, apt still tells me that there are
  updates.

  Expected behaviour: should hide those updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1983730/+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 1982198] Re: apt update: Can not add an empty (zero-length) key to the cache

2022-08-05 Thread Julian Andres Klode
This string does not exist in apt or any of the other Ubuntu code I have
checked out. If you can reproduce it, do check where it is coming from
and reassign it there.

** Package changed: apt (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  apt update: Can not add an empty (zero-length) key to the cache

Status in Ubuntu:
  Incomplete

Bug description:
  When running sudo apt update, I get the following warning after the
  "Fetched" message:

  Can not add an empty (zero-length) key to the cache

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.9
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 19 16:44:36 2022
  InstallationDate: Installed on 2022-04-26 (84 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1982198/+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 1976233] Re: "File has unexpected size" error on Focal ddebs repository

2022-08-04 Thread Julian Andres Klode
** Package changed: apt (Ubuntu) => ddeb-retriever

** Changed in: ddeb-retriever
   Status: Invalid => Confirmed

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

Title:
  "File has unexpected size" error on Focal ddebs repository

Status in ddeb-retriever:
  Confirmed

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865
  but affecting Ubuntu 20.04 "Focal"

  
  Steps to reproduce:

  1. Configure the debug repositories, like how it is explained in
  https://wiki.ubuntu.com/Debug%20Symbol%20Packages

  I ran these commands on a newly created Docker container (docker run
  --pull always --rm -ti ubuntu:20.04), but a typical bare metal
  installation should present the same issue:

  apt-get update ; apt-get install --yes gnupg

  apt-key adv \
  --keyserver keyserver.ubuntu.com \
  --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622

  source /etc/lsb-release

  tee /etc/apt/sources.list.d/ddebs.list >/dev/null 

[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository

2022-08-04 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  "File has unexpected size" error on Focal ddebs repository

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865
  but affecting Ubuntu 20.04 "Focal"

  
  Steps to reproduce:

  1. Configure the debug repositories, like how it is explained in
  https://wiki.ubuntu.com/Debug%20Symbol%20Packages

  I ran these commands on a newly created Docker container (docker run
  --pull always --rm -ti ubuntu:20.04), but a typical bare metal
  installation should present the same issue:

  apt-get update ; apt-get install --yes gnupg

  apt-key adv \
  --keyserver keyserver.ubuntu.com \
  --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622

  source /etc/lsb-release

  tee /etc/apt/sources.list.d/ddebs.list >/dev/null 

[Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

2022-08-03 Thread Julian Andres Klode
To make it clear, my suggestion for a workaround for jammy would be to
have

_config->CndSet("APT::Get::Phase-Policy", true);

somewhere in the aptitude code. It is unclear to me if aptitude will
break then as phased versions get their pin limited to 1, apt certainly
does if there's a mismatch as in bug 1979244

Anyone doing the SRU will have to analyse that regression potential.

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

Title:
  phased updates API and client for aptitude

Status in apt package in Ubuntu:
  Triaged
Status in aptitude package in Ubuntu:
  Triaged

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: phased updates API and client for aptitude

2022-08-03 Thread Julian Andres Klode
I have added an aptitude task and set the tasks accordingly to indicate
that this is a feature request for aptitude. The needed API will surface
at some point in APT due to some refactoring, likely in the 23.04 cycle.

aptitude could then consume that API in its resolver and make choices to
keep back phased upgrades, however, that is up to the aptitude
maintainers upstream. Do note that aptitude is mostly unmaintained these
days.

Alternatively, aptitude can also enable the policy based variant as that
likely works for its solver. That could be SRUed into jammy if somebody
wants to provide a patch for that, do the SRU paperwork, and get it
sponsored and then work on getting it released. Do note that this option
is experimental and may disappear in a future release as we finalize the
correct approach.

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

Title:
  phased updates API and client for aptitude

Status in apt package in Ubuntu:
  Triaged
Status in aptitude package in Ubuntu:
  Triaged

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: apt phased out broken code, missing documentation to opt out

2022-08-03 Thread Julian Andres Klode
I recall/see again a mention of aptitude:

aptitude and aptitude-robot are not supported components. They are
packages provided by the community as part of the universe repository.

While the implementation of phased updates in apt versions prior to
2.4.6 would work there, the current version does not. Implementing
phased updates in aptitude for the current algorithm is out of scope, as
aptitude does not use the apt resolver where the keep-back is
implemented, and a generic API to handle phasing is not yet exposed in
apt.

Switching to the policy based pinning as documented before should make
aptitude respect pinning more, however, aptitude is not a reliable tool
that respects your choices like that (its solver will happily suggest
solutions violating your wishes; it also generally is too happy to
remove packages), so you do not want to use it in an automated setting.

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

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

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

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

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

** Summary changed:

- apt phased out broken code, missing documentation to opt out
+ phased updates API and client for aptitude

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

Title:
  phased updates API and client for aptitude

Status in apt package in Ubuntu:
  Triaged
Status in aptitude package in Ubuntu:
  Triaged

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: apt phased out broken code, missing documentation to opt out

2022-08-03 Thread Julian Andres Klode
It's documented in the discourse thread (Discourse is where Ubuntu
documentation lives) You have not provided evidence that it does not
work for you. APT itself has test cases that proof that *it does* work.

Note that newer apt versions (2.4.6, 2.5.1) will install more phased
updates

- as phasing only applies to upgrades, not to new installs, so if you `apt 
install phased`, you'll get the phased version, regardless of your setting,
- or if there is a phased=1 security update and a phased=2 update, you'll get 
phased=2 even if it's phasing at 0. 

You can restore previous behavior by setting APT::Get::Phase-Policy to
true; but note that this can cause the `apt install` command to fail to
install packages, see bug 1979244 for more details.

All other phased updates should show as being kept back in the upgrade
output.

If you want to move this further you'll have to provide one of the
following:

- A reproducer
- A log that shows a phased update being installed that should not be, 
including the command that installed the update and any debug output

Either must be accompanied by a tarball containing:

- /etc/apt
- /var/lib/dpkg/status
- /var/lib/apt

You also want to check yourself that

- `apt-config dump` shows `APT::Get::Never-Include-Phased-Updates "false";`
- `apt-config dump` shows no entry, or a negative one, for 
`APT::Get::Always-Include-Phased-Updates`

If you use update-manager it's not entirely clear how this interacts
with the new phasing code in 2.4.6, so you might also/instead have to
set

`Update-Manager::Never-Include-Phased-Updates "false";`

As documented in the discourse post.

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: apt phased out broken code, missing documentation to opt out

2022-08-03 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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


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

2022-08-03 Thread Julian Andres Klode
Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.

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

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

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

Bug description:
  [Impact]

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

   * Some real cases from OEM projects:

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

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

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

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

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

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

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

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

  [Test Plan]

   * detailed instructions how to reproduce the bug:

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

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

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

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

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

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

  And then update-initramfs

   * After applying my patches, the issue is gone.

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

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

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

  All working well.

  [Where problems could occur]

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

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

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

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

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

  [Other Info]

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

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

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

   * Test source code: 

[Touch-packages] [Bug 1982652] Re: ddebs.ubuntu.com is intermittently down

2022-08-01 Thread Julian Andres Klode
Overloaded server is not a bug in apt. There are no mirrors for ddebs,
so the overload is not very surprising. You should not have any need to
download ddebs, and you certainly don't want to abuse the resources with
automatic repeated downloads.

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

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

Title:
  ddebs.ubuntu.com is intermittently down

Status in apt package in Ubuntu:
  Invalid

Bug description:
  When running apt-get update (a few days ago and a few minutes ago),
  ddebs.ubuntu.com is sometimes down, responding with HTTP 503:

  W: Failed to fetch http://ddebs.ubuntu.com/dists/focal/InRelease  503  
Service Unavailable [IP: 185.125.190.18 80]
  W: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/InRelease  503 
 Service Unavailable [IP: 185.125.190.18 80]
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  This is an intermittent issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.9
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 23 07:54:35 2022
  InstallationDate: Installed on 2022-04-26 (87 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1982652/+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 1983171] Re: apt-get install can fail for language-pack-XX due to phased updates

2022-07-30 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1979244 ***
https://bugs.launchpad.net/bugs/1979244

As you can see in your output a newer version of apt is available. It
fixes this bug.

** This bug has been marked a duplicate of bug 1979244
   libssl-dev : Depends: libssl3 (= 3.0.2-0ubuntu1.1) but 3.0.2-0ubuntu1.2 is 
to be installed

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

Title:
  apt-get install can fail for language-pack-XX due to phased updates

Status in apt package in Ubuntu:
  New

Bug description:
  Language packs in Ubuntu are packaged as a package language-pack-XX
  which depends on language-pack-XX-base. Currently, language-pack-sv
  and language-pack-sv-base are both on a phased update. Due to how
  these packages depend on each other, apt-get install language-pack-sv
  may fail (depending on machine-id and apt config) if a machine gets
  the most recent package of language-pack-sv, but is held back due to
  phasing for language-pack-sv-base.

  ```
  root@1232eabd9c61:/etc/apt# apt policy language-pack-sv language-pack-sv-base
  language-pack-sv:
Installed: (none)
Candidate: 1:22.04+20220721
Version table:
   1:22.04+20220721 500 (phased 70%)
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
   1:22.04+20220415 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  language-pack-sv-base:
Installed: (none)
Candidate: 1:22.04+20220415
Version table:
   1:22.04+20220721 1 (phased 70%)
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
   1:22.04+20220415 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  root@1232eabd9c61:/# apt-get install language-pack-sv
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... 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:
   language-pack-sv : Depends: language-pack-sv-base (>= 1:22.04+20220721) but 
1:22.04+20220415 is to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  Setting `APT::Get::Always-Include-Phased-Updates true;` in a file
  /etc/apt/apt.conf.d/98-no-phased works around the issue.

  N.B., This happened for us in CI, I was able to reproduce on a docker
  image, but was not able to run ubuntu-bug on that machine, so ubuntu-
  bug was run on a different machine. Sorry for the inconvenience.

  Version information from the machine where I reproduced the error:
  ```
  root@1232eabd9c61:/etc/apt# lsb_release  -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04
  root@1232eabd9c61:/etc/apt# apt-cache policy apt
  apt:
Installed: 2.4.5
Candidate: 2.4.6
Version table:
   2.4.6 500 (phased 80%)
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
   *** 2.4.5 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.6
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Regolith:GNOME-Flashback:GNOME
  Date: Sat Jul 30 13:16:04 2022
  InstallationDate: Installed on 2022-07-08 (22 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1983171/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

2022-07-28 Thread Julian Andres Klode
Please note that this is not the test plan documented in the bug. But
glad this worked for you, I was not sure it was still reproducible,
hence why there's a solver dump based test case in the regression test
suite.

But your test is valid too, the test suite still needs to pass, but
failure to pass would block SRU either way, so I'll keep the tags as
done.

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

2022-07-28 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  In Progress
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

2022-07-28 Thread Julian Andres Klode
** No longer affects: apt (Ubuntu Impish)

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Negative pins are overridden by a pin of 1 if the package is phasing and "not 
for us", which suddenly makes packages installable that were effectively 
blocklisted by the negative pin, overriding user settings

  [Test plan]
  Integration tests covers the fix for this. The fix is not enabled by default 
as the implementation was changed for bug 1979244, however the new 
implementation also tests that.

  These tests are run during autopkgtest.

  To test with the new implementation, create an update that pulls in a
  phasing package that is pinned -1 and make sure it's not being
  installed. I did not add a test for that case as the new
  implementation only works by keeping back packages, so it by
  definition can't suddenly cause a package to be allowed.

  [Where problems could occur]
  This specific bit is not enabled anymore, but for the sake of it, it is 
implemented as a ceiling for the pin, so any other pin will be limited to 1 if 
the package is considered a "not-for-us" phasing package. So problems could 
occur there.

  For the new phasing implementation, see bug 1979244.

  [Original bug report]
  Did some upgrades on a new box on 22.04, and had previously removed snapd and 
BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd

  This has never worked on any package, ever...

  I have:
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
    Installed: 2.4.5
    Candidate: 2.4.5
    Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

2022-07-28 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Description changed:

- On an Ubuntu 22.04 desktop system created using the current installation
- image without enabling package updates over the network, installing the
- package libudev1 results in a large number of critical packages being
- removed and rendering the system essentially unusable.
+ [Impact]
+ On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.
+ 
+ [Test plan]
+ Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.
+ 
+ [Where problems could occur]
+ We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.
+ 
+ [Other info]
  
  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in
  
  The following packages will be REMOVED:
-   libnss-systemd libpam-systemd systemd-timesyncd udev
+   libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
-   libudev1
+   libudev1
  
- 
- This is completely prevented by ensuring that updates are installed from the 
jammy-updates repository before installing any additional packages and that is 
almost certainly the correct thing to do. But this is a punishing result for 
such a mistake.
+ This is completely prevented by ensuring that updates are installed from
+ the jammy-updates repository before installing any additional packages
+ and that is almost certainly the correct thing to do. But this is a
+ punishing result for such a mistake.
  
  I would expect the installation to either force the upgrade of the other
  systemd packages or refuse to install libudev1 at the incorrect version
  relative to the other systemd packages until the system is upgraded.
  
  We found this out via a user report for ROS 2 Humble which is releasing
  on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  In Progress
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1981672] Re: apt phased out broken code, missing documentation to opt out

2022-07-26 Thread Julian Andres Klode
In your libmysqlclient21 example everything seems to be working
correctly so I don't understand why you post that.

- you are eligible for 8.0.29-0ubuntu0.22.04.3
- you force downgrade to 8.0.29-0ubuntu0.22.04.2
- you upgrade once again to 8.0.29-0ubuntu0.22.04.3
- no higher version available in final dist-upgrade run

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: apt phased out broken code, missing documentation to opt out

2022-07-14 Thread Julian Andres Klode
For concrete details:

1) Which command would install these updates
2) Please attached `apt policy ...names of affected packages...` output
3) Attach your sources.list and sources.list.d files
4) Attach your preferences and preferences.d files

Maybe just throw all the files into a tarball.

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: apt phased out broken code, missing documentation to opt out

2022-07-14 Thread Julian Andres Klode
The apt update is from kinetic, the development release. What are you
doing?

The question is what installs them. Certainly it's not apt itself doing
that unless you have very weird pinning in place.

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: apt phased out broken code, missing documentation to opt out

2022-07-14 Thread Julian Andres Klode
I do not believe there is a bug in apt here. APT literally is too strict
now, it fails to install packages. It will get more relaxed in the
coming weeks.

Anyway, if you find out where those get upgraded, please reopen the bug
and reassign to the correct package.

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

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1970449] Re: GPG keys are not shown in Software and Updates

2022-07-11 Thread Julian Andres Klode
** Tags added: rls-jj-incoming

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Canonical livepatch icon doesn't appear on the title bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  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: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

2022-07-11 Thread Julian Andres Klode
For impish, please remove the update, it is not necessary to release an
SRU 3 days before EOL that improves the situation for further SRUs.

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Impish:
  Fix Committed
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Negative pins are overridden by a pin of 1 if the package is phasing and "not 
for us", which suddenly makes packages installable that were effectively 
blocklisted by the negative pin, overriding user settings

  [Test plan]
  Integration tests covers the fix for this. The fix is not enabled by default 
as the implementation was changed for bug 1979244, however the new 
implementation also tests that.

  These tests are run during autopkgtest.

  To test with the new implementation, create an update that pulls in a
  phasing package that is pinned -1 and make sure it's not being
  installed. I did not add a test for that case as the new
  implementation only works by keeping back packages, so it by
  definition can't suddenly cause a package to be allowed.

  [Where problems could occur]
  This specific bit is not enabled anymore, but for the sake of it, it is 
implemented as a ceiling for the pin, so any other pin will be limited to 1 if 
the package is considered a "not-for-us" phasing package. So problems could 
occur there.

  For the new phasing implementation, see bug 1979244.

  [Original bug report]
  Did some upgrades on a new box on 22.04, and had previously removed snapd and 
BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd

  This has never worked on any package, ever...

  I have:
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
    Installed: 2.4.5
    Candidate: 2.4.5
    Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

2022-07-11 Thread Julian Andres Klode
Verified. I hacked around the Packages files locally to simulate the
situation:

0. Pinned snapd to -1 and removed it
1. Modified packages file to add Depends: snapd to an update in proposed 
(netplan.io), and set
   Phased-Update-Percentage: 0 on snapd

Before:

root@jammy:~# apt policy snapd
snapd:
  Installed: (none)
  Candidate: 2.55.5+22.04
  Version table:
 2.55.5+22.04 1 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 2.55.3+22.04 -1
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@jammy:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
  snapd
The following packages will be upgraded:
  apt libapt-pkg6.0 libgstreamer1.0-0 libicu70 libnetplan0 libnss3 netplan.io 
python3-gi
8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 standard security update
Need to get 34.8 MB/37.1 MB of archives.
After this operation, 89.3 MB of additional disk space will be used.
Do you want to continue? [Y/n] ^C
root@jammy:~# apt install snapd -s  
  
Reading package lists... Done   
  
Building dependency tree... Done
  
Reading state information... Done   
  
The following package was automatically installed and is no longer required:
  
  libfreetype6  
  
Use 'apt autoremove' to remove it.  
  
Suggested packages: 
  
  zenity | kdialog  
  
The following NEW packages will be installed:   
  
  snapd 
  
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.  
  
Inst snapd (2.55.5+22.04 Ubuntu:22.04/jammy-updates [amd64])
  
Conf snapd (2.55.5+22.04 Ubuntu:22.04/jammy-updates [amd64])  


After upgrading apt to 2.4.6:

root@jammy:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libfreetype6 squashfs-tools
Use 'apt autoremove' to remove them.
The following packages have been kept back:
  libnetplan0 netplan.io
The following packages will be upgraded:
  libgstreamer1.0-0 libicu70 libnss3 python3-gi
4 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 standard security update
Need to get 13.1 MB of archives.
After this operation, 2048 B of additional disk space will be used.
Do you want to continue? [Y/n] 
root@jammy:~# apt install snapd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package snapd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'snapd' has no installation candidate


** Tags removed: verification-needed verification-needed-impish 
verification-needed-jammy
** Tags added: verification-done verification-done-jammy 
verification-failed-impish

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Impish:
  Fix Committed
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Negative pins are overridden by a pin of 1 if the package is 

[Touch-packages] [Bug 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

2022-07-08 Thread Julian Andres Klode
This is being fixed in https://salsa.debian.org/apt-
team/apt/-/merge_requests/248

** Package changed: systemd (Ubuntu) => apt (Ubuntu)

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

** Also affects: apt (Ubuntu Kinetic)
   Importance: Undecided
 Assignee: Julian Andres Klode (juliank)
   Status: In Progress

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  New
Status in apt source package in Kinetic:
  In Progress

Bug description:
  On an Ubuntu 22.04 desktop system created using the current
  installation image without enabling package updates over the network,
  installing the package libudev1 results in a large number of critical
  packages being removed and rendering the system essentially unusable.

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
libudev1

  
  This is completely prevented by ensuring that updates are installed from the 
jammy-updates repository before installing any additional packages and that is 
almost certainly the correct thing to do. But this is a punishing result for 
such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1979139] Re: apt-get update fails inside docker container

2022-06-20 Thread Julian Andres Klode
You also do not have the latest docker installed. Be aware that if the
host system is older than the guest, various things can fail due to
seccomp issues, the latest docker should always be used.

So please check with all updates installed in the host, the official
ubuntu:jammy image, and using a chroot.

I'm reasonably sure that you are just missing updates to docker and runc
or whatever that allowlist the syscalls used by jammy glibc.

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

Title:
  apt-get update fails inside docker container

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  A docker image built with "debootstrap jammy" fails when running "apt-
  get update".

  1) lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04

  2)
  # apt-cache policy docker.io
  docker.io:
Installed: 19.03.8-0ubuntu1.20.04.1
Candidate: 20.10.7-0ubuntu5~20.04.2
Version table:
   20.10.7-0ubuntu5~20.04.2 500
  500 http://mirror.localnet:8055/ubuntu-security 
focal-security/universe amd64 Packages
   *** 19.03.8-0ubuntu1.20.04.1 100
  100 /var/lib/dpkg/status
   19.03.8-0ubuntu1 500
  500 http://mirror.localnet:8055/ubuntu focal/universe amd64 Packages

  # docker run --rm -ti ubuntu:jammy apt-cache policy apt
  apt:
Installed: 2.4.5
Candidate: 2.4.5
Version table:
   *** 2.4.5 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  3) I would expect, that "apt-get update" updates the package lists, as
  in

  # docker run --rm -ti ubuntu:focal apt-get update
  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Get:2 http://archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB]
  Fetched 506 kB in 1s (464 kB/s) 
  Reading package lists... Done

  4) Instead, it fails with

  # docker run --rm -ti ubuntu:jammy apt-get update
  Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
  Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 871920D1991BC93C
  Reading package lists... Done
  W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the 
keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as 
the file is not readable by user '_apt' executing apt-key.
  W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the 
keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as 
the file is not readable by user '_apt' executing apt-key.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
871920D1991BC93C
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease  
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 871920D1991BC93C
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  5) To reproduce:

  # mkdir jammy-jellyfish
  # debootstrap jammy jammy-jellyfish
  ...
  # tar -C jammy-jellyfish -c . | docker import - ubuntu:jammy
  # docker run --rm -ti ubuntu:jammy apt-get update

  Doing the same with focal, works as expected:

  # mkdir focal-fossa
  # debootstrap focal focal-fossa
  ...
  # tar -C focal-fossa -c . | docker import - ubuntu:focal
  # docker run --rm -ti ubuntu:focal apt-get update
  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Get:2 http://archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB]
  Fetched 506 kB in 1s (963 kB/s)
  Reading package lists... Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1979139/+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 1979139] Re: apt-get update fails inside docker container

2022-06-20 Thread Julian Andres Klode
Please actually follow the error message and check that the keyring
permissions are correct.

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

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

Title:
  apt-get update fails inside docker container

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  A docker image built with "debootstrap jammy" fails when running "apt-
  get update".

  1) lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04

  2)
  # apt-cache policy docker.io
  docker.io:
Installed: 19.03.8-0ubuntu1.20.04.1
Candidate: 20.10.7-0ubuntu5~20.04.2
Version table:
   20.10.7-0ubuntu5~20.04.2 500
  500 http://mirror.localnet:8055/ubuntu-security 
focal-security/universe amd64 Packages
   *** 19.03.8-0ubuntu1.20.04.1 100
  100 /var/lib/dpkg/status
   19.03.8-0ubuntu1 500
  500 http://mirror.localnet:8055/ubuntu focal/universe amd64 Packages

  # docker run --rm -ti ubuntu:jammy apt-cache policy apt
  apt:
Installed: 2.4.5
Candidate: 2.4.5
Version table:
   *** 2.4.5 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  3) I would expect, that "apt-get update" updates the package lists, as
  in

  # docker run --rm -ti ubuntu:focal apt-get update
  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Get:2 http://archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB]
  Fetched 506 kB in 1s (464 kB/s) 
  Reading package lists... Done

  4) Instead, it fails with

  # docker run --rm -ti ubuntu:jammy apt-get update
  Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
  Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 871920D1991BC93C
  Reading package lists... Done
  W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the 
keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as 
the file is not readable by user '_apt' executing apt-key.
  W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the 
keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as 
the file is not readable by user '_apt' executing apt-key.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
871920D1991BC93C
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease  
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 871920D1991BC93C
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  5) To reproduce:

  # mkdir jammy-jellyfish
  # debootstrap jammy jammy-jellyfish
  ...
  # tar -C jammy-jellyfish -c . | docker import - ubuntu:jammy
  # docker run --rm -ti ubuntu:jammy apt-get update

  Doing the same with focal, works as expected:

  # mkdir focal-fossa
  # debootstrap focal focal-fossa
  ...
  # tar -C focal-fossa -c . | docker import - ubuntu:focal
  # docker run --rm -ti ubuntu:focal apt-get update
  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Get:2 http://archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB]
  Fetched 506 kB in 1s (963 kB/s)
  Reading package lists... Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1979139/+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 1940097] Re: A forgotten "space"

2022-06-18 Thread Julian Andres Klode
** Changed in: python-apt (Ubuntu)
 Assignee: Akbarkhon Variskhanov (kbar) => (unassigned)

** Changed in: python-apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  A forgotten "space"

Status in python-apt package in Ubuntu:
  In Progress

Bug description:
  Hi
  A "space" character has been forgotten in the "apt/package.py" file and line 
"592".
  I found this error while translating.
  
https://translations.launchpad.net/ubuntu/impish/+source/python-apt/+pots/python-apt/fa/36/+translate

  if not dsc:
  return _("Missing description for '%s'." <===
  "Please report.") % (self.package.name)

  This line should be like this

  if not dsc:
  return _("Missing description for '%s'. " <===
  "Please report.") % (self.package.name)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1940097/+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 1978871] Re: apt package missing apt-auto-removal

2022-06-16 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  apt package missing apt-auto-removal

Status in apt package in Ubuntu:
  Invalid

Bug description:
  #> lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  #> apt-cache policy apt
  apt:
Installed: 2.0.9
Candidate: 2.0.9
Version table:
   *** 2.0.9 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.2ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   2.0.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  The /etc/kernel/postinst.d/apt-auto-removal file is supposed to be
  included in the apt package...

  #> apt-file find apt-auto-removal
  apt: /etc/kernel/postinst.d/apt-auto-removal
  open-infrastructure-system-build: 
/usr/share/live/build/hooks/normal/0196-remote-apt-auto-removal.hook.chroot

  But versions 2.0.8 and 2.0.9 do not include it...

  #> dpkg -L apt | fgrep -i post
  /etc/kernel/postinst.d

  #> ls /etc/kernel/postinst.d/
  ./  ../  initramfs-tools*  xx-update-initrd-links*  zz-update-grub*

  Can you please rebuild this package to include the missing file?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978871/+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 1978871] Re: apt package missing apt-auto-removal

2022-06-15 Thread Julian Andres Klode
Well you figured out the versions we stopped shipping it, so you could
have just read the changelog to find out why that happened.

But anyway, we no longer protect the last installed kernel.

** Changed in: apt (Ubuntu)
   Status: New => Invalid

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

Title:
  apt package missing apt-auto-removal

Status in apt package in Ubuntu:
  Invalid

Bug description:
  #> lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  #> apt-cache policy apt
  apt:
Installed: 2.0.9
Candidate: 2.0.9
Version table:
   *** 2.0.9 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.2ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   2.0.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  The /etc/kernel/postinst.d/apt-auto-removal file is supposed to be
  included in the apt package...

  #> apt-file find apt-auto-removal
  apt: /etc/kernel/postinst.d/apt-auto-removal
  open-infrastructure-system-build: 
/usr/share/live/build/hooks/normal/0196-remote-apt-auto-removal.hook.chroot

  But versions 2.0.8 and 2.0.9 do not include it...

  #> dpkg -L apt | fgrep -i post
  /etc/kernel/postinst.d

  #> ls /etc/kernel/postinst.d/
  ./  ../  initramfs-tools*  xx-update-initrd-links*  zz-update-grub*

  Can you please rebuild this package to include the missing file?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978871/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-06-14 Thread Julian Andres Klode
Set the verification done tags based on my the confirmation in #11 and
#12 of what I see in my pre-upload testing, and also double checked as
described - with mmdebstrap with proposed enabled, it installed apt
2.0.9 successfully

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-06-14 Thread Julian Andres Klode
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

2022-06-09 Thread Julian Andres Klode
What happens here is that that version of snapd is not phased for you,
and it hence pins it down to 1. But you already had it pinned to -1 and
that got overridden, sorry. It should only downgrade pin priority to 1
if it's phased as not for you.

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Did some upgrades on a new box on 22.04, and had previously removed
  snapd and BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd 

  This has never worked on any package, ever...

  
  I have: 
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
Installed: 2.4.5
Candidate: 2.4.5
Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

2022-06-09 Thread Julian Andres Klode
Thanks. I think this is a corner case I did not handle correctly in the
phased updates support.

https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345

I think if you set

APT::Get::Never-Include-Phased-Updates

In the meantime, this should workaround the issue.

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

** Changed in: apt (Ubuntu)
   Status: In Progress => Triaged

** Tags added: rls-jj-incoming

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Did some upgrades on a new box on 22.04, and had previously removed
  snapd and BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd 

  This has never worked on any package, ever...

  
  I have: 
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
Installed: 2.4.5
Candidate: 2.4.5
Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

2022-06-09 Thread Julian Andres Klode
There is no specific handling in apt for this, so where are you seeing
this? Is it possible you see this in a graphical update tool like
update-manager?

Your apt-get log looks correct.

What does apt-cache policy snapd say?


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

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Did some upgrades on a new box on 22.04, and had previously removed
  snapd and BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd 

  This has never worked on any package, ever...

  
  I have: 
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
Installed: 2.4.5
Candidate: 2.4.5
Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1862764] Re: add-apt-repository should use signed-by

2022-06-05 Thread Julian Andres Klode
My goal would be to switch to deb822 sources for this with the key
embedded in the .sources file.

We're still missing the ability to edit those files graphically however,
that needs to be implemented first.

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

Title:
  add-apt-repository should use signed-by

Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties package in Debian:
  New

Bug description:
  add-apt-repository should use signed-by

  apt sources.list syntax supports limiting which keys are used to sign
  a given repo.

  It would be nice for add-apt-repository to import the key somewhere
  else but trusted.gpg.d and then specify path to it, using the "signed-
  by" field.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-common 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8
  Uname: Linux 5.4.0-1002-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 11 12:01:49 2020
  InstallationDate: Installed on 2016-01-26 (1477 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-06-01 Thread Julian Andres Klode
Hi Gary,

how do you invoke debootstrap so it uses packages from the the updates
pocket? I wasn't able to with --extra-suites=focal-updates, but I might
have missed something.

But then I guess we should actually release that fix too.

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-05-23 Thread Julian Andres Klode
It might, I just might miss the right setting, I don't really know.

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Confirmed

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-05-23 Thread Julian Andres Klode
@David I was able to reproduce this with mmdebstrap as it uses -updates
pocket, but not with debootstrap as it only uses the release pockets.
Which tool were you using to bootstrap your system?

It's possible we might just want keep the fix in -proposed and not
release it to updates if it does not affect the supported bootstrapping
tools.

** Description changed:

+ [Impact]
+ bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.
+ 
+ This is not a problem on updates, only on new installs, so impact is
+ limited to bootstrapping tools that enable -updates, such as mmdebstrap.
+ 
+ [Test case]
+ 
+ bootstrapping with -updates enabled can easily be tested with
+ mmdebstrap:
+ 
+ mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal
+ 
+ for example, on focal:
+ 
+ Setting up apt (2.0.8) ...
+ /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
+ dpkg: error processing package apt (--configure):
+  installed apt package post-installation script subprocess returned error 
exit status 127
+ 
+ [Regression potential]
+ We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.
+ 
+ [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0
  
  ...but `apt.postinst` still tries to run it:
  
- # create kernel autoremoval blacklist on update
- if dpkg --compare-versions "$2" lt 0.9.9.3; then
- /etc/kernel/postinst.d/apt-auto-removal
- fi
+ # create kernel autoremoval blacklist on update
+ if dpkg --compare-versions "$2" lt 0.9.9.3; then
+ /etc/kernel/postinst.d/apt-auto-removal
+ fi
  
  If I understand correctly, "$2" is the most-recently-configured-version,
  and if it's empty `dpkg --compare-versions lt` will evaluate to true.
  
  This fails when I'm building a focal (20.04) userspace from scratch:
  
- $ dpkg --configure -a
- [...]
- Setting up apt (2.0.8) ...
- /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
- dpkg: error processing package apt (--configure):
-  installed apt package post-installation script subprocess returned error 
exit status 127
+ $ dpkg --configure -a
+ [...]
+ Setting up apt (2.0.8) ...
+ /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
+ dpkg: error processing package apt (--configure):
+  installed apt package post-installation script subprocess returned error 
exit status 127
  
  It works with apt 2.0.6.

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Confirmed

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed 

[Touch-packages] [Bug 1974456] Re: regression: apt.postint fails if never previously configured

2022-05-20 Thread Julian Andres Klode
Yup I'm going to push updated bionic and focal SRUs for this next week

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  New
Status in apt source package in Bionic:
  New
Status in apt source package in Focal:
  New

Bug description:
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-05-20 Thread Julian Andres Klode
** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  New
Status in apt source package in Bionic:
  New
Status in apt source package in Focal:
  New

Bug description:
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1968154] Re: Only keep 2 kernels

2022-05-20 Thread Julian Andres Klode
Please create a new bug for that regression, thanks for noticing!

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

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

2022-05-20 Thread Julian Andres Klode
I ran the tests in lxd, I'm not sure that's sufficient, but:

on bionic:

upgrade-all-security FAIL non-zero exit status 1

focal failed to build for me in autopkgtest:

2022-05-20 10:04:12,150 ERROR Exception happened during upgrade.
Traceback (most recent call last):
  File "/tmp/autopkgtest.7B08MG/build.ZME/src/test/unattended_upgrade.py", line 
863, in cache_commit
res = cache.commit(install_progress=iprogress)
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 686, in commit
raise SystemError("installArchives() failed")
SystemError: installArchives() failed
2022-05-20 10:04:12,157 ERROR Auto-removing the packages failed!
2022-05-20 10:04:12,158 ERROR Error message: installArchives() failed
2022-05-20 10:04:12,159 ERROR dpkg returned an error! See 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log for 
details
2022-05-20 10:04:12,159 DEBUG InstCount=0 DelCount=0 BrokenCount=0
2022-05-20 10:04:12,161 DEBUG Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2022-05-20 10:04:10

-- 
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:
  New
Status in unattended-upgrades source package in Focal:
  New
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

2022-05-20 Thread Julian Andres Klode
looking

** Also affects: unattended-upgrades (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => 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/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:
  New
Status in unattended-upgrades source package in Focal:
  New
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 1973149] Re: system uses merged-usr-via-aliased-dirs, going behind dpkg's back, breaking its core assumptions

2022-05-12 Thread Julian Andres Klode
Also you probably don't want to run devel proposed, that's a recipe for
disaster.

** Tags added: rls-kk-incoming

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

Title:
  system uses merged-usr-via-aliased-dirs, going behind dpkg's  back,
  breaking its core assumptions

Status in dpkg package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Got this warning on Kinetic, Mate flavor:

  Paramétrage de dpkg (1.21.7ubuntu3) ...
  dpkg: warning:

   This system uses merged-usr-via-aliased-dirs, going behind dpkg's
  back, breaking its core assumptions. This can cause silent file
  overwrites and disappearances, and its general tools misbehavior.

   See .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  Package: dpkg 1.21.7ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Tags: kinetic package-from-proposed third-party-packages
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1973149/+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 1973149] Re: system uses merged-usr-via-aliased-dirs, going behind dpkg's back, breaking its core assumptions

2022-05-12 Thread Julian Andres Klode
I thought we patched that warning out. Do not read it :D

Notably this is the only supported layout.

** Changed in: dpkg (Ubuntu)
   Status: New => Won't Fix

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

** Changed in: dpkg (Ubuntu)
   Status: Won't Fix => Triaged

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

Title:
  system uses merged-usr-via-aliased-dirs, going behind dpkg's  back,
  breaking its core assumptions

Status in dpkg package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Got this warning on Kinetic, Mate flavor:

  Paramétrage de dpkg (1.21.7ubuntu3) ...
  dpkg: warning:

   This system uses merged-usr-via-aliased-dirs, going behind dpkg's
  back, breaking its core assumptions. This can cause silent file
  overwrites and disappearances, and its general tools misbehavior.

   See .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  Package: dpkg 1.21.7ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Tags: kinetic package-from-proposed third-party-packages
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1973149/+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 1968154] Re: Only keep 2 kernels

2022-05-11 Thread Julian Andres Klode
Verified impish 2.3.9ubuntu0.1

Log:
1. (in 1016) started with 5.13.0-1016-kvm; installed 5.13.0-1022-kvm
2. (in 1016) no kernels to autoremove
3. (in 1016) installed linux-image-5.13.0-1011-kvm 
linux-modules-5.13.0-1011-kvm, and marked auto
4. (in 1016) SUCCESS: autoremove would remove 1011
5. (in 1011) SUCCESS: After reboot into 1011, 1016 is autoremovable (*1)
7. (in 1022) SUCCESS: After reboot into 1022, both 1011 and 1022 are kept


(*1) There is a bug in the image used by lxd: The 1016 kernel that was 
preinstalled on the image was marked as manually installed, this was corrected 
with apt-mark auto linux-.*-5.13.0-1016-kvm


** Tags removed: verification-needed-impish
** Tags added: verification-done-impish

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Re: Only keep 2 kernels

2022-05-11 Thread Julian Andres Klode
** No longer affects: unattended-upgrades (Ubuntu Impish)

** No longer affects: unattended-upgrades (Ubuntu Focal)

** No longer affects: unattended-upgrades (Ubuntu Bionic)

** No longer affects: unattended-upgrades (Ubuntu)

** Description changed:

  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.
  
  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable
- 
- unattended-upgrades may need changes to its test suite to accommodate
- this.
  
  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.
  
  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as we
  had 3 hard requirements so far:
  
  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed
  
  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.
  
  During normal system lifetime, the most recently installed kernel is the
  same as the highest version, so 2==3, and there are no changes to
  behavior.
  
  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.
  
  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1971763] Re: www-browser is not satisfied by the default Firefox snap

2022-05-06 Thread Julian Andres Klode
The gimp-help-* packages have a dependency on only virtual packages rather than 
firefox-esr | firefox | chromium | x-www-browser 
 or something which is a bug. as it will pick a random one. Also I'm not sure 
why it would depend on the non-graphical browser virtual package (www-browser) 
instead of a graphical browser (x-www-browser).

There's no way for repositories to declare the default provider of a
virtual package, unfortunately. An approach would be default-x-www-
browser | x-www-browser but it's also suboptimal.

** Package changed: apt (Ubuntu) => gimp-help (Ubuntu)

** Changed in: gimp-help (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  www-browser is not satisfied by the default Firefox snap

Status in gimp-help package in Ubuntu:
  Triaged

Bug description:
  When installing a package that has the virtual-package www-browser as
  a dependency, the Firefox snap is not taken into account.

  This leads to wslu being installed on Ubuntu 22.04 Desktop (notably
  when installing the GIMP translation packages), which breaks the ding
  desktop behaviour:
  https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp-help/+bug/1971763/+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 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software

2022-05-05 Thread Julian Andres Klode
The mirror list is shipped in python-apt and updated with each python-
apt update, and with each Ubuntu point release based on the launchpad
mirror feed https://launchpad.net/ubuntu/+archivemirrors-rss.

Additional updates to just the mirror list are not made.

The mirror method is supported using the official
mirror://mirrors.ubuntu.com/mirrors.txt url. Additional urls are custom
modifications and not recognized by aptsources as Ubuntu mirrors.

It might be possible to make aptsources look at Origin field in the
Release file if you have downloaded them, however that's prone to
breakage if you switch releases, so it's not optimal. In any case this
is not a bug in software-properties. Please open a bug against python-
apt if you believe we have reasonable means of supporting unofficial
mirrors like official ones.

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

Title:
  software-properties-gtk does not recognize https mirrors under Ubuntu
  Software

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:

  1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt 
update"
  2. Run software-properties-gtk
  3. Go to "Ubuntu Software" tab

  What happens:

  The tab "Ubuntu Software" does not list https mirrors. The
  corresponding boxes are not checked, the correct "Download from" entry
  is not selected and falls back to "Main server". The correct sources
  are just listed under "Other Software".

  What should happen:

  The tab "Ubuntu Software" should recognize the https mirrors from apt
  and tick the corresponding boxes and select the correct server in the
  "Download from" list.

  Ubuntu 18.04
  software-properties-gtk 0.96.24.32.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1814072/+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 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software

2022-05-05 Thread Julian Andres Klode
** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  software-properties-gtk does not recognize https mirrors under Ubuntu
  Software

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:

  1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt 
update"
  2. Run software-properties-gtk
  3. Go to "Ubuntu Software" tab

  What happens:

  The tab "Ubuntu Software" does not list https mirrors. The
  corresponding boxes are not checked, the correct "Download from" entry
  is not selected and falls back to "Main server". The correct sources
  are just listed under "Other Software".

  What should happen:

  The tab "Ubuntu Software" should recognize the https mirrors from apt
  and tick the corresponding boxes and select the correct server in the
  "Download from" list.

  Ubuntu 18.04
  software-properties-gtk 0.96.24.32.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1814072/+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 1964483] Re: Update supported mirror protocol according to official archive mirrors list

2022-05-05 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1814072 ***
https://bugs.launchpad.net/bugs/1814072

charite did not support https at the time the mirror list in python-apt
was created. The mirror list is updated with each python-apt update, and
with each Ubuntu point release.

With the next update, only https will be supported on the charite mirror
as advertised by the launchpad mirror feed
https://launchpad.net/ubuntu/+archivemirrors-rss

** This bug has been marked a duplicate of bug 1814072
   software-properties-gtk does not recognize https mirrors under Ubuntu 
Software

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

Title:
  Update supported mirror protocol according to official archive mirrors
  list

Status in software-properties package in Ubuntu:
  New

Bug description:
  While mirrors listed on https://launchpad.net/ubuntu/+archivemirrors
  support https, this is not reflected in software-properties-gtk ->
  Download from -> other dialogue. Example: Charite Berlin supports
  https, but only http is available from the "Protocol" dialogue.

  Editing /etc/apt/sources.list mitigates the issue, though
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1814072 is still unresolved.

  lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  apt-cache policy software-properties-gtk
  software-properties-gtk:
  Installed: 0.99.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1964483/+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 1968154] Re: Only keep 2 kernels

2022-04-25 Thread Julian Andres Klode
@sil2100 Added that to regression potential. It was used to keep the
third kernel. There was some misunderstanding how that affects the set
calculated.

I noticed that 2.0.7 and 2.3.9ubuntu0.1 had the wrong version in
maintainer scripts, so I will have to upload a fixed 2.0.8 for the
former (it has proper upstream release, and possibly other downstreams),
and replace 2.3.9ubuntu0.1 with a newer one.

** Description changed:

  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.
  
  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable
  
  unattended-upgrades may need changes to its test suite to accommodate
  this.
  
  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.
+ 
+ We remove the requirement to keep the most recently installed version,
+ previously recorded in APT::LastInstalledKernel, to achieve this, as we
+ had 3 hard requirements so far:
+ 
+ 1. keep booted kernel
+ 2. keep highest version
+ 3. keep most recently installed
+ 
+ 1 can't be removed as it would break running systems, 2 is what you
+ definitely want to keep.
+ 
+ During normal system lifetime, the most recently installed kernel is the
+ same as the highest version, so 2==3, and there are no changes to
+ behavior.
+ 
+ Likewise, if you most recently installed an older kernel manually for
+ debugging, it would be manually installed and not subject to removal,
+ even if the rule is dropped.
+ 
+ The behavior really only changes if you install an older kernel, and
+ then mark it auto - that older kernel becomes automatically removable
+ immediately after it is marked as auto.

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in unattended-upgrades source package in Focal:
  New
Status in apt source package in Impish:
  In Progress
Status in unattended-upgrades source package in Impish:
  New

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  unattended-upgrades may need changes to its test suite to accommodate
  this.

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Re: Only keep 2 kernels

2022-04-22 Thread Julian Andres Klode
** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: apt (Ubuntu Impish)
   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/1968154

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in unattended-upgrades source package in Focal:
  New
Status in apt source package in Impish:
  In Progress
Status in unattended-upgrades source package in Impish:
  New

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  unattended-upgrades may need changes to its test suite to accommodate
  this.

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968461] Re: sudo apt install crashes computer

2022-04-19 Thread Julian Andres Klode
Not an apt bug in either case if it crashes your system

** Package changed: apt (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Fix Released

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

Title:
  sudo apt install crashes computer

Status in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 22.04, when installing software, especially when it hits
  snap, it will crash the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 10 02:31:17 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset 
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-04-07 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1968461/+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 1968154] Re: Only keep 2 kernels

2022-04-19 Thread Julian Andres Klode
unattended-upgrades in jammy did not need a change, we'll see if SRUs
will need changes, hence keeping the task so we can add them later on
without having to reset to launchpad API shenanigans.

** Description changed:

  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.
  
  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable
  
- unattended-upgrades needs changes to its test suite to accommodate this.
+ unattended-upgrades may need changes to its test suite to accommodate
+ this.
  
  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

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

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  unattended-upgrades may need changes to its test suite to accommodate
  this.

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] [NEW] Only keep 2 kernels

2022-04-07 Thread Julian Andres Klode
Public bug reported:

[Impact]
APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is 
sized for a steady state of 2 kernels + 1 new one being unpacked, hence users 
run out of space and new kernels fail to install, upgrade runs might abort in 
the middle. It's not nice.

[Test plan]
1. Have two kernels installed (let's call them version 3, 2)
2. Check that both kernels are not autoremovable
3. Install an old kernel (let's call it 1), and mark it automatic
4. Check that 1 will be autoremovable (apt autoremove -s)
5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
6. Actually remove 2
7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

unattended-upgrades needs changes to its test suite to accommodate this.

[Where problems could occur]
We could keep the wrong kernels installed that the user did not expect.

** Affects: apt (Ubuntu)
 Importance: High
 Assignee: Julian Andres Klode (juliank)
 Status: In Progress

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: fr-2155

** Description changed:

  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.
  
  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now still not autoremovable
  
  [Where problems could occur]
- We could keep the wrong kernels installed that the user did not expect.
+ We could keep the wrong kernels installed that the user did not expect

** Description changed:

  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.
  
  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
- 7. Reboot into 3 and check that both 1 and 3 are now still not autoremovable
+ 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable
  
  [Where problems could occur]
- We could keep the wrong kernels installed that the user did not expect
+ We could keep the wrong kernels installed that the user did not expect.

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

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Tags added: fr-2155

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.
  
  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable
  
+ unattended-upgrades needs changes to its test suite to accommodate this.
+ 
  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not auto

[Touch-packages] [Bug 1968135] Re: BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy beta

2022-04-07 Thread Julian Andres Klode
The ro flag is correct, the / filesystem is remounted rw after a
filesystem check, I don't know where precisely, I'm gonna reassign this
to systemd

** Package changed: grub2 (Ubuntu) => systemd (Ubuntu)

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

Title:
  BTRFS root subvolume @ mounted always as readonly (... ro
  rootflags=subvol=@ ...) on Jammy beta

Status in systemd package in Ubuntu:
  New

Bug description:
  = Description =
  On Ubuntu Jammy Jellyfish (beta 220330) where root (/) is installed on single 
BTRFS formated partition (no LVM, no separate /boot), then root subvolume 
(subvol=@) is always mounted as read only. There is a kernel flag (ro) appended 
to GRUB configuration file /boot/grub/grub.cfg created by script 
/usr/sbin/update-grub during every kernel update. Only home subvolume (@home) 
remains mounted as rw according to fstab which is correct. Read-only mounted 
root (/) leads to many issues.
  Image: Jammy Beta (220330)

  = Steps to Reproduce =
  1. Install Jammy Beta (220330) on EFI PC x86_64 GPT partitioning and select 
FS root (/) to one single BTRFS partition (where subvolumes @ and @home are 
created). There are only 3 partitions EFI system partition (/dev/sda1), one 
swap (sda2), and one BTRFS formated (/dev/sda3) for FS root (/).
  2. Launch the kernel via the default grub entry (or look for kernel boot 
parameters pressing ) - root subvolume (@) is mounted as readonly.

  = Expected Results =
  root / should be mounted as rw (mount -v | grep @), there should be no (ro) 
flag in /proc/cmdline for FS root. It is possible to temporarily avoid this 
behaviour in /etc/defaul/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="rw quiet splash"
  Then there still remains "ro" kernel parameter which is followed by "rw quiet 
splash" at the end.
   
  = Actual Results =
  in grub.cfg:
  linux /@/boot/vmlinuz-5.15.0-23-generic root=UUID=--... 
rootflags=subvol=@ ro quiet splash $vt_handoff
  in /proc/cmdline:
  BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic 
root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1968135/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-04-01 Thread Julian Andres Klode
** Tags added: fr-2162

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Triaged
Status in dbus source package in Jammy:
  Triaged

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-04-01 Thread Julian Andres Klode
** Changed in: dbus (Ubuntu)
Milestone: None => ubuntu-22.04

** Changed in: dbus (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: dbus (Ubuntu Jammy)
   Importance: Critical
   Status: Triaged

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Triaged
Status in dbus source package in Jammy:
  Triaged

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1965960] Re: apt installs snap packages

2022-03-23 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: New => Invalid

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

Title:
  apt installs snap packages

Status in apt package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  $ apt-cache policy apt
  apt:
Installed: 2.4.1
Candidate: 2.4.1
Version table:
   *** 2.4.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) I expected to dist-upgrade my system, running apt-get dist-upgrade

  4) apt tried to install firefox from snap. I naturally aborted the upgrade, 
if I want a snap package I install it with snap, I use apt to install 
debian/apt packages.
  Aborting the install essentially broke my system. Trying to repair it, and 
installing firefox using apt again, hence getting force-fed the snap of 
firefox, broke my install, too, as the snap cannot access my firefox 
configuration files (for good reasons).
  It took me half a day to repair the system and switch to a PPA to keep the 
system (and Ubuntu with its intended processes - apt for deb, snap for snap, 
probably flatpaks and whatever for other stuff  - for that matter) running.

  In summary: We know you love snap. We use snap for certain purposes, and apt 
for others. Please don't force your love for snap on us, snaps constantly break 
long-running systems and require careful introduction.
   
  The proper solution could have been to stop supporting firefox from apt, so 
we have to consciously deal with the situation - without getting our systems 
broken.

  Thanks ❤️

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Mar 22 16:26:47 2022
  InstallationDate: Installed on 2022-03-07 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1965960/+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 1965121] Re: "archive.ubuntu.com" was missing in "/etc/apt/sources.list"

2022-03-16 Thread Julian Andres Klode
Thanks for your bug report.

I am reassigning this to the installer, but it seems more likely that
this is a result of user error, given that there have not been any
relevant changes in focal's installer. For user support, please use
askubuntu, discourse, the ubuntu-user mailing lists, or the #ubuntu IRC
channel on Libera.

If you believe this to be an installer bug, to collect additional data
for the bug report, run `apport-collect 1965121` in a terminal and
follow the instructions. This will provide us the installer log. Also
please attach the incomplete sources.list that was supposedly generated
by the installer.

** Package changed: apt (Ubuntu) => ubiquity (Ubuntu)

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

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

Title:
  "archive.ubuntu.com" was missing in "/etc/apt/sources.list"

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Right after clean install, "archive.ubuntu.com" was missing in
  "/etc/apt/sources.list" as summary.

  So, apt checked too small amount of servers for "apt update" or "apt install",
  and all the fundamental and basic dev packages like libgtk-dev or 
gnome-builder were not available to download.

  Platform : Ubuntu 20.04.4 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.6
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 16 20:18:20 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965121/+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 1958148] Re: mkinitramfs is too slow

2022-03-15 Thread Julian Andres Klode
I have uploaded the agreed changes (attached) to jammy.

** Patch added: "initramfs-tools_0.140ubuntu13.diff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+attachment/5569316/+files/initramfs-tools_0.140ubuntu13.diff

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists

2022-03-03 Thread Julian Andres Klode
I wonder if you need to install gnome-software Deb maybe.

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

Title:
  Ubuntu reboots instead of powering off if a software updates exists

Status in gnome-shell package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New

Bug description:
  When I want to turn off a computer, I got a checkbox "Install deferred
  updates" (see screenshot, I'm not sure if my back-translation is
  correct).

  If the checkbox is checked, Ubuntu box reboots instead of powering
  off. It is not "rebopot to install updates". It just reboots to
  desktop again. If I uncheck the box, it powers off normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 00:05:44 2022
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists

2022-03-01 Thread Julian Andres Klode
Though on the other hand I don't really want flavours to do offline
upgrades, but I don't think we have a clear-cut policy on that. Either
way, removing the feature inside PackageKit might break some flavours,
so seeing as we are past feature freeze, fixing that in the frontend
would be less invasive.

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

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

Title:
  Ubuntu reboots instead of powering off if a software updates exists

Status in gnome-shell package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New

Bug description:
  When I want to turn off a computer, I got a checkbox "Install deferred
  updates" (see screenshot, I'm not sure if my back-translation is
  correct).

  If the checkbox is checked, Ubuntu box reboots instead of powering
  off. It is not "rebopot to install updates". It just reboots to
  desktop again. If I uncheck the box, it powers off normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 00:05:44 2022
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists

2022-03-01 Thread Julian Andres Klode
This is *not* a packagekit issue. There are flavours upgrading using
packagekit, not everyone uses update-manager. It's either gnome-shell or
gnome-session or something that should not be reacting to this.

** Package changed: packagekit (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Ubuntu reboots instead of powering off if a software updates exists

Status in gnome-shell package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New

Bug description:
  When I want to turn off a computer, I got a checkbox "Install deferred
  updates" (see screenshot, I'm not sure if my back-translation is
  correct).

  If the checkbox is checked, Ubuntu box reboots instead of powering
  off. It is not "rebopot to install updates". It just reboots to
  desktop again. If I uncheck the box, it powers off normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 00:05:44 2022
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-02-24 Thread Julian Andres Klode
Removing the duplicate, because while the other bugs focus on the
crashes, this one focuses on dbus stopping. I don't think the crashes
matter, fwiw, dbus should not be stopping in the first place, there's no
way to gracefully recover from that.

** This bug is no longer a duplicate of bug 1961910
   Ubuntu 22 crash when updating, broken network manager and cannot report bug

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-02-23 Thread Julian Andres Klode
I did not find interesting journalctl, maybe someone else is luckier.

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+attachment/5563112/+files/journal.log

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  New

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-02-23 Thread Julian Andres Klode
The attached /var/log/apt/term.log does not show anything suspicious

** Attachment added: "apt-term.log"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+attachment/5563111/+files/apt-term.log

** Description changed:

+ Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
+ Had to hard reset.
+ 
  Today's jammy upgrade stopped dbus at 19:46:27
  
  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...
  
  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  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 dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1962036

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  New

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-02-23 Thread Julian Andres Klode
dpkg.log from that run

** Attachment added: "dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+attachment/5563110/+files/dpkg.log

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  New

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] [NEW] dbus was stopped during today's jammy update, breaking desktop

2022-02-23 Thread Julian Andres Klode
Public bug reported:

Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
Had to hard reset.

Today's jammy upgrade stopped dbus at 19:46:27

Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
Bus...

This should not happen. I don't know which package caused this, but
presumably dbus should not be stoppable in the first place.


ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dbus 1.12.20-2ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Feb 23 20:03:41 2022
InstallationDate: Installed on 2018-03-14 (1442 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  New

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1961833] Re: openssh 8.8 breaks login to Canonical servers

2022-02-22 Thread Julian Andres Klode
We generally expect programs to print a depreciation notice to stderr
and not just hide them in release notes, that we, as downstream users
don't read :)

If it doesn't warn during use, it's not properly deprecated.

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

Title:
  openssh 8.8 breaks login to Canonical servers

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  With 8.7p1-4 connecting to wendigo

  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent
  debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

  With 8.8p1-1

  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

 
  debug1: send_pubkey_test: no mutual signature algorithm   

  
  Needs further investigation, but blocks people a bit right now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades

2022-02-22 Thread Julian Andres Klode
Matthias, could this be a result of allowing PK to switch versions?

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

Title:
  PackageKit 1.2.5 unable to perform upgrades

Status in packagekit package in Ubuntu:
  New

Bug description:
  After being notified of upgrades available in Plasma Discover, I
  attempted to do an upgrade of all available packages. Unfortunately,
  it would not but also wouldn't show an error.

  I attempted to run 'pkcon update' which showed no available upgrades,
  whereas 'apt update' showed several packages available for upgrade.

  Expected behavior: 'pkcon update' would have performed the upgrade.
  Actual behavior: 'pkcon update' did nothing, saying no packages were 
available to upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: packagekit 1.2.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12
  Uname: Linux 5.15.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Feb 22 11:33:52 2022
  InstallationDate: Installed on 2021-03-20 (338 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+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 1961833] Re: openssh 8.8 breaks login to canonical servers

2022-02-22 Thread Julian Andres Klode
Question we have to ask: Is breaking support for old servers without a
deprecation notice in the LTS release the best cause of action?

** Summary changed:

- openssh 8.8 breaks login to canonical servers
+ openssh 8.8 breaks login to Canonical servers

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

Title:
  openssh 8.8 breaks login to Canonical servers

Status in openssh package in Ubuntu:
  New

Bug description:
  With 8.7p1-4 connecting to wendigo

  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent
  debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

  With 8.8p1-1

  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

 
  debug1: send_pubkey_test: no mutual signature algorithm   

  
  Needs further investigation, but blocks people a bit right now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961833] Re: openssh 8.8 breaks login to canonical servers

2022-02-22 Thread Julian Andres Klode
It says

Incompatibility is more likely when connecting to older SSH
implementations that have not been upgraded or have not closely tracked
improvements in the SSH protocol. For these cases, it may be necessary
to selectively re-enable RSA/SHA1 to allow connection and/or user
authentication via the HostkeyAlgorithms and PubkeyAcceptedAlgorithms
options. For example, the following stanza in ~/.ssh/config will enable
RSA/SHA1 for host and user authentication for a single destination host:

Host old-host
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa

So this may be a server too old issue; and we can fix this in internal
tooling.

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

Title:
  openssh 8.8 breaks login to Canonical servers

Status in openssh package in Ubuntu:
  New

Bug description:
  With 8.7p1-4 connecting to wendigo

  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent
  debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

  With 8.8p1-1

  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

 
  debug1: send_pubkey_test: no mutual signature algorithm   

  
  Needs further investigation, but blocks people a bit right now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961833] [NEW] openssh 8.8 breaks login to Canonical servers

2022-02-22 Thread Julian Andres Klode
Public bug reported:

With 8.7p1-4 connecting to wendigo

debug1: Next authentication method: publickey
debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent
debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

With 8.8p1-1

debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

 
debug1: send_pubkey_test: no mutual signature algorithm   


Needs further investigation, but blocks people a bit right now

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

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

Title:
  openssh 8.8 breaks login to Canonical servers

Status in openssh package in Ubuntu:
  New

Bug description:
  With 8.7p1-4 connecting to wendigo

  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent
  debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

  With 8.8p1-1

  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

 
  debug1: send_pubkey_test: no mutual signature algorithm   

  
  Needs further investigation, but blocks people a bit right now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup

2022-02-21 Thread Julian Andres Klode
We'll continue/start working on the SRUs mid May, if no regressions are
reported until then. That gives it a month or so in stable jammy which
seems reasonable for the scope of changes and very little testing being
done so far.

** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: discover (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: packagekit (Ubuntu Focal)
   Importance: Undecided
   Status: New

** No longer affects: unattended-upgrades (Ubuntu)

** No longer affects: unattended-upgrades (Ubuntu Focal)

** No longer affects: unattended-upgrades (Ubuntu Jammy)

** No longer affects: apt (Ubuntu Jammy)

** No longer affects: apt (Ubuntu Focal)

** No longer affects: apt (Ubuntu)

** No longer affects: discover (Ubuntu)

** No longer affects: discover (Ubuntu Focal)

** No longer affects: discover (Ubuntu Jammy)

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

Title:
  Kernel updates marked as "manually installed", prevents old kernels
  cleanup

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Focal:
  New
Status in packagekit source package in Jammy:
  Fix Released

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1914278/+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 1958148] Re: mkinitramfs is too slow

2022-02-21 Thread Julian Andres Klode
Unsubscribed ubuntu-sponsors as the default compression level is still
an ongoing discussion.

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

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup

2022-02-21 Thread Julian Andres Klode
** Changed in: packagekit (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Kernel updates marked as "manually installed", prevents old kernels
  cleanup

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  Invalid
Status in packagekit package in Ubuntu:
  Fix Committed
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Jammy:
  Invalid
Status in discover source package in Jammy:
  Invalid
Status in packagekit source package in Jammy:
  Fix Committed
Status in unattended-upgrades source package in Jammy:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+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 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup

2022-02-17 Thread Julian Andres Klode
1.2.5 is out now, I'll go grab that directly rather than try to
reconstruct the correct ugit tarball for the git snapshot :)

** Changed in: packagekit (Ubuntu Jammy)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  Kernel updates marked as "manually installed", prevents old kernels
  cleanup

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  Invalid
Status in packagekit package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Jammy:
  Invalid
Status in discover source package in Jammy:
  Invalid
Status in packagekit source package in Jammy:
  In Progress
Status in unattended-upgrades source package in Jammy:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+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 1960404] Re: merge python-debian 0.1.43 from Debian sid

2022-02-16 Thread Julian Andres Klode
** Changed in: python-debian (Ubuntu)
   Status: New => Fix Committed

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

Title:
  merge python-debian 0.1.43 from Debian sid

Status in python-debian package in Ubuntu:
  Fix Committed

Bug description:
  Please merge the latest Debian version of this package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+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 989961] Re: Provide a gmake symlink

2022-02-16 Thread Julian Andres Klode
Superseded by a no-change rebuild -4.1build1; it turns out the delta was
not needed anymore.

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

Title:
  Provide a gmake symlink

Status in make-dfsg package in Ubuntu:
  Fix Committed

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/989961/+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 1939973] Re: make 4.3-4.1 triggers build failures

2022-02-16 Thread Julian Andres Klode
I rebuilt make-dfsg 4.1 without changes and cross-toolchain-base mostly
finished building against it in the same bileto ppa, so this issue seems
resolved, probably some toolchain bug?

https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4783/+packages

** Changed in: make-dfsg (Ubuntu)
   Status: Confirmed => Fix Committed

** No longer affects: make-dfsg (Ubuntu Impish)

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

Title:
  make 4.3-4.1 triggers build failures

Status in make-dfsg package in Ubuntu:
  Fix Committed

Bug description:
  trying to rebuild cross-toolchain-base from
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages

  triggers a build failure:

  [...]
  START stamp-dir/init-binutils
  tar -x -f  /usr/src/binutils/binutils-2.37.tar.xz
  set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n 
"$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then 
QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc 
/dev/null  push -a; fi; rm -rf .pc
  cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf 
armel  powerpc" debian/rules stamps/control
  make: dpkg-architecture: No such file or directory
  make: lsb_release: No such file or directory
  make: lsb_release: No such file or directory
  make: pwd: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  debian/rules:163: *** unexpected source package name: .  Stop.
  make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2
  dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit 
status 2

  
  working around by omitting the -i option to env, or by setting PATH 
explicitly. Reverting to the version in the release pocket lets the c-t-b- 
build succeed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1939973/+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 989961] Re: Provide a gmake symlink

2022-02-15 Thread Julian Andres Klode
Note that gmake is shipped in make-guile, not the normal make package,
but currently broken, which this will address

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

Title:
  Provide a gmake symlink

Status in make-dfsg package in Ubuntu:
  In Progress

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/989961/+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 989961] Re: Provide a gmake symlink

2022-02-15 Thread Julian Andres Klode
** Changed in: make-dfsg (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: make-dfsg (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Provide a gmake symlink

Status in make-dfsg package in Ubuntu:
  In Progress

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/989961/+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 1960264] Re: 503 errors for Jammy PPAs

2022-02-14 Thread Julian Andres Klode
I don't know if anyone looks at apt-cacher-ng bug reports, but reassigning it 
there for further analysis.
The log says that this is apt-cacher-ng failing to talk to launchpad.

I generally recommend avoiding apt-cacher-ng due to bugs in the
interaction with apt (which then go in endless circles of blame between
both sides, but not resolved) and using squid instead if a proxy is
needed.

** Package changed: apt (Ubuntu) => apt-cacher-ng (Ubuntu)

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

Title:
  503 errors for Jammy PPAs

Status in apt-cacher-ng package in Ubuntu:
  New

Bug description:
  For Jammy - all PPAs seem to fail - the main archive is ok

   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1
    503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:6 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-rotation-lock-applet all 
1.3.0+202202062047~ubuntu22.04.1
    503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Fetched 114 kB in 7s (15.8 kB/s)
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-quicknote-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-recentlyused-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]

  ppa:ubuntubudgie-dev/budgie-extras-daily

  The same PPA for impish & focal work just fine

  Thoughts?

  

  Continually running repeatedly sudo apt update && sudo apt dist-
  upgrade -y eventually forces the downloads to occur ok and the
  upgrades can then be installed ok

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.3.15
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb  7 18:47:47 2022
  InstallationDate: Installed on 2022-01-29 (8 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220129)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1960264/+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 1960582] Re: [critical] dpkg error while processing - can't install nor upgrade

2022-02-14 Thread Julian Andres Klode
I tried to reproduce the issue in a podman container, but was unable to
do so. This makes sense: After do-release-upgrade -d, obviously apt
upgrade will not have any pending upgrades.

Marking this as incomplete, as we'd need to see a clean reproducer to
get anywhere.

Looking at the postinst, it fails because the dpkg database in
/var/lib/dpkg contains an unexpected "dpkg" directory. Please
investigate how this directory was created / what it contains, it should
not be there.

** No longer affects: apt (Ubuntu)

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

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

Title:
  [critical] dpkg error while processing - can't install nor upgrade

Status in dpkg package in Ubuntu:
  Incomplete

Bug description:
  My current ubuntu version : 
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy

  Issue : 
  when `sudo apt update` is ok, all newest package is downloaded
  but `sudo apt ugprade` show current error : ]

  sudo apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
librygel-renderer-2.6-2 librygel-server-2.6-2 rygel
  The following packages will be upgraded:
bolt code deja-dup enchant-2 fwupd gdm3 gir1.2-gdm-1.0 
gir1.2-gst-plugins-base-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0
gir1.2-upowerglib-1.0 gjs gstreamer1.0-alsa gstreamer1.0-gl 
gstreamer1.0-gtk3 gstreamer1.0-plugins-base
gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good 
gstreamer1.0-pulseaudio gstreamer1.0-x initramfs-tools
initramfs-tools-bin initramfs-tools-core iputils-ping iputils-tracepath 
language-pack-en language-pack-gnome-en
libenchant-2-2 libfwupd2 libfwupdplugin5 libgdm1 libgjs0g 
libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0
libgstreamer-plugins-good1.0-0 libnl-3-200 libnl-genl-3-200 
libnl-route-3-200 libnm0 libnma-common libnma0
libpkcs11-helper1 libseccomp2 libunistring2 libunistring2:i386 
libupower-glib3 media-types nano network-manager
network-manager-config-connectivity-ubuntu python3-paramiko 
python3-software-properties simple-scan
software-properties-common software-properties-gtk upower
  56 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  10 not fully installed or removed.
  Need to get 0 B/94,6 MB of archives.
  After this operation, 1.928 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  Setting up dpkg (1.21.1ubuntu1) ...
  head: error reading 'dpkg': Is a directory
  dpkg: error processing package dpkg (--configure):
   installed dpkg package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   dpkg
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  i have to resintall all of the package in cache with `sudo dpkg -i 
/var/cache/apt/archives/*.deb
  `, but the cache sometimes is not the newest packages 
  and when i rerun `sudo apt upgrade`, there is still not the newest package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960582/+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 1960264] Re: 503 errors for Jammy PPAs

2022-02-13 Thread Julian Andres Klode
It seems you use apt-cacher-ng, please try if the issue reproduces
without it, and if so, if it happens with a known good proxy like squid
(e.g. using deb-squid-proxy).

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

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

Title:
  503 errors for Jammy PPAs

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  For Jammy - all PPAs seem to fail - the main archive is ok

   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1
    503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:6 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-rotation-lock-applet all 
1.3.0+202202062047~ubuntu22.04.1
    503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Fetched 114 kB in 7s (15.8 kB/s)
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-quicknote-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-recentlyused-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]

  ppa:ubuntubudgie-dev/budgie-extras-daily

  The same PPA for impish & focal work just fine

  Thoughts?

  

  Continually running repeatedly sudo apt update && sudo apt dist-
  upgrade -y eventually forces the downloads to occur ok and the
  upgrades can then be installed ok

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.3.15
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb  7 18:47:47 2022
  InstallationDate: Installed on 2022-01-29 (8 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220129)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960264/+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 1960727] Re: When apt holds back updates, it fails to inform the user of the reason

2022-02-13 Thread Julian Andres Klode
Marking as Opinion as David explained why that is not a thing we can
reasonably determine.

** Changed in: apt (Ubuntu)
   Status: New => Opinion

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

Title:
  When apt holds back updates, it fails to inform the user of the reason

Status in apt package in Ubuntu:
  Opinion

Bug description:
  In the case where apt refuses to install and holds back certain
  packages, only the following output is produced:

  root@system:/home/admin# apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
[ List of packages ]
  0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.

  
  Missing is any explanation about which package is responsible for apt 
refusing to perform its job, or even what is the reason for that package being 
uninstallable.

  This bug leads users to believe that official Ubuntu packages are
  routinely misconstructed, corrupt, or otherwise junk.

  Fix: Instead of apt simply responding "No Dave, I'm Afraid I Can't Do
  that", correct the output to include the specific package that has a
  missing or unresolved dependency, so the user a) has confidence that
  the process works correctly and b) can proceed with fixing the
  problem.

  
  This bug is longstanding, so I don't think version details are required, but 
they follow anyway:

  1) Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  2) # apt --version
  apt 2.0.6 (amd64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+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 1960583] Re: dpkg error while processing - can't install nor upgrade

2022-02-11 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1960582 ***
https://bugs.launchpad.net/bugs/1960582

** This bug has been marked a duplicate of bug 1960582
   [critical] dpkg error while processing - can't install nor upgrade

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

Title:
  dpkg error while processing - can't install nor upgrade

Status in apt package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  New

Bug description:
  My current ubuntu version :
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Jammy Jellyfish (development branch)
  Release: 22.04
  Codename: jammy

  Issue :
  when `sudo apt update` is ok, all newest package is downloaded
  but `sudo apt ugprade` show current error : ]

  sudo apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
librygel-renderer-2.6-2 librygel-server-2.6-2 rygel
  The following packages will be upgraded:
bolt code deja-dup enchant-2 fwupd gdm3 gir1.2-gdm-1.0 
gir1.2-gst-plugins-base-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0
gir1.2-upowerglib-1.0 gjs gstreamer1.0-alsa gstreamer1.0-gl 
gstreamer1.0-gtk3 gstreamer1.0-plugins-base
gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good 
gstreamer1.0-pulseaudio gstreamer1.0-x initramfs-tools
initramfs-tools-bin initramfs-tools-core iputils-ping iputils-tracepath 
language-pack-en language-pack-gnome-en
libenchant-2-2 libfwupd2 libfwupdplugin5 libgdm1 libgjs0g 
libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0
libgstreamer-plugins-good1.0-0 libnl-3-200 libnl-genl-3-200 
libnl-route-3-200 libnm0 libnma-common libnma0
libpkcs11-helper1 libseccomp2 libunistring2 libunistring2:i386 
libupower-glib3 media-types nano network-manager
network-manager-config-connectivity-ubuntu python3-paramiko 
python3-software-properties simple-scan
software-properties-common software-properties-gtk upower
  56 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  10 not fully installed or removed.
  Need to get 0 B/94,6 MB of archives.
  After this operation, 1.928 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  Setting up dpkg (1.21.1ubuntu1) ...
  head: error reading 'dpkg': Is a directory
  dpkg: error processing package dpkg (--configure):
   installed dpkg package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   dpkg
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  i have to resintall all of the package in cache with `sudo dpkg -i 
/var/cache/apt/archives/*.deb
  `, but the cache sometimes is not the newest packages
  and when i rerun `sudo apt upgrade`, there is still not the newest package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960583/+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 1960226] Re: Ubuntu Jammy Desktop fails to boot after install

2022-02-07 Thread Julian Andres Klode
You have already left grub at this point and the kernel also started.

Reassigning to systemd in the meantime to debug this further as a
userspace boot issue. This might need further reassing.

You'll have to boot this verbosely, it's no use with a splash screen
enabled.

** Package changed: grub2 (Ubuntu) => systemd (Ubuntu)

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

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

Title:
  Ubuntu Jammy Desktop fails to boot after install

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Jammy Desktop fails to boot after install

  Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

  After installing the OS and selecting reboot the system reboot fails -

  The vendors logo appears with the Ubuntu logo and fails to boot - I
  have tried this with 2 barebone machines and 1 in VirtualBox - will
  attach syslogs and images in a separate comment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960226/+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 1959748] Re: package information could not be initialized

2022-02-02 Thread Julian Andres Klode
Please sudo chmod 644
/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_focal-
backports_InRelease to fix this.

If you can reproduce this reliably, please let me know. Otherwise,
there's nothing we can do to fix the underlying bug, as we can't analyse
it further, so I'm going to be closing the bug. We get about 3-4 such
reports per year I think.

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

** Changed in: apt (Ubuntu)
   Status: New => Invalid

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

Title:
  package information could not be initialized

Status in apt package in Ubuntu:
  Invalid

Bug description:
  (title translated from German: "Packetinformationen konnten nicht 
initialisiert werden")
  I got this message on boot-up and it says i should include the following into 
this report:
  E:can not open 
/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_focal-backports_InRelease 
- fopen (13: Keine Berechtigung), E:Die Paketliste oder die Statusdatei konnte 
nicht eingelesen oder geöffnet werden.

  "Keine Berechtigung" = Access denied
  "Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet 
werden." = The packagelist or statusfile could not be read or opened.

  I am using this ubuntu version: Ubuntu 20.04.3 LTS
  I did not want to perform a distribution upgrade

  As to 3) and 4)
  i did not expect anything, as i just started the computer and got the error 
described above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1959748/+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 1958642] Re: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

2022-01-25 Thread Julian Andres Klode
** Bug watch added: Debian Bug tracker #1004272
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004272

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

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

Title:
  New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

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

Bug description:
  Building libxcrypt with the new binutils upload
  2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE
  LOAD header instead of two LOAD headers (one RE, one RW); causing it
  to fail to load in services that use MemoryDenyWriteExecute=yes, thus
  breaking a ton of systemd services.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1958642/+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 1958811] Re: If apt installs snap package, then show size of it

2022-01-24 Thread Julian Andres Klode
Arguably people could hack in an override for Installed-Size when
building the deb somehow to give a rough estimate, but might not be
worth the effort.

** Changed in: apt (Ubuntu)
   Status: New => Won't Fix

** Changed in: apt (Ubuntu)
   Status: Won't Fix => Invalid

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

Title:
  If apt installs snap package, then show size of it

Status in apt package in Ubuntu:
  Invalid
Status in chromium-browser package in Ubuntu:
  New
Status in snap package in Ubuntu:
  New

Bug description:
  If apt installs snap package, then show size of it

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DRM.card0-Virtual-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050 
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768 
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
  Date: Mon Jan 24 03:36:26 2022
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/xvda3 ext411G  8,3G  1,5G  86% /
   tmpfs  tmpfs  1,9G  6,6M  1,9G   1% /dev/shm
   /dev/xvda3 ext411G  8,3G  1,5G  86% /
  InstallationDate: Installed on 2022-01-21 (2 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: Xen HVM domU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   4Done2022-01-24T03:33:37+02:00  2022-01-24T03:34:29+02:00  Install 
"chromium" snap
  Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99 
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
  Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2022
  dmi.bios.release: 4.14
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.14.3
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.14.3
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958811/+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 1958810] Re: Apt installing snap package if got some error why didnt finish, thinks apt is installed, but snap cant be removed

2022-01-24 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: New => Invalid

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

Title:
  Apt installing snap package if got some error why didnt finish, thinks
  apt is installed, but snap cant be removed

Status in apt package in Ubuntu:
  Invalid
Status in chromium-browser package in Ubuntu:
  New
Status in snap package in Ubuntu:
  New

Bug description:
  Apt installing snap package if got some error why didnt finish, thinks
  apt is installed, but snap cant be removed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DRM.card0-Virtual-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050 
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768 
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
  Date: Mon Jan 24 03:37:18 2022
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/xvda3 ext411G  8,3G  1,4G  86% /
   tmpfs  tmpfs  1,9G  6,6M  1,9G   1% /dev/shm
   /dev/xvda3 ext411G  8,3G  1,4G  86% /
  InstallationDate: Installed on 2022-01-21 (2 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: Xen HVM domU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   4Done2022-01-24T03:33:37+02:00  2022-01-24T03:34:29+02:00  Install 
"chromium" snap
  Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99 
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
  Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2022
  dmi.bios.release: 4.14
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.14.3
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.14.3
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958810/+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 1958812] Re: If apt installs snap package, then warn, because maybe i dont want snap package.

2022-01-24 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: New => Won't Fix

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

Title:
  If apt installs snap package, then warn, because maybe i dont want
  snap package.

Status in apt package in Ubuntu:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  New
Status in snap package in Ubuntu:
  New

Bug description:
  If apt installs snap package, then warn, because maybe i dont want
  snap package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DRM.card0-Virtual-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050 
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768 
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
  Date: Mon Jan 24 03:35:44 2022
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/xvda3 ext411G  8,3G  1,5G  86% /
   tmpfs  tmpfs  1,9G  9,1M  1,9G   1% /dev/shm
   /dev/xvda3 ext411G  8,3G  1,5G  86% /
  InstallationDate: Installed on 2022-01-21 (2 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: Xen HVM domU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   4Done2022-01-24T03:33:37+02:00  2022-01-24T03:34:29+02:00  Install 
"chromium" snap
  Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99 
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
  Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2022
  dmi.bios.release: 4.14
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.14.3
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.14.3
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958812/+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 1958642] Re: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

2022-01-21 Thread Julian Andres Klode
Further data points:

- The first build with new binutils was

  s390x build of soci 4.0.1-5ubuntu1 in ubuntu jammy PROPOSED

- Investigation on Debian shows that it was not affected, and that the
bug is caused by LTO - if you enable LTO on Debian, it starts building
the broken library as well.

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

Title:
  New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

Status in binutils package in Ubuntu:
  New

Bug description:
  Building libxcrypt with the new binutils upload
  2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE
  LOAD header instead of two LOAD headers (one RE, one RW); causing it
  to fail to load in services that use MemoryDenyWriteExecute=yes, thus
  breaking a ton of systemd services.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1958642/+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 1958642] Re: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

2022-01-21 Thread Julian Andres Klode
Technically this was critical while it was in proposed, I set it to high
as we removed it; but it's a blocker to fix this for a future binutils
upload.

** Tags added: rls-jj-incoming

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

Title:
  New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

Status in binutils package in Ubuntu:
  New

Bug description:
  Building libxcrypt with the new binutils upload
  2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE
  LOAD header instead of two LOAD headers (one RE, one RW); causing it
  to fail to load in services that use MemoryDenyWriteExecute=yes, thus
  breaking a ton of systemd services.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1958642/+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 1958642] [NEW] New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

2022-01-21 Thread Julian Andres Klode
Public bug reported:

Building libxcrypt with the new binutils upload
2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE
LOAD header instead of two LOAD headers (one RE, one RW); causing it to
fail to load in services that use MemoryDenyWriteExecute=yes, thus
breaking a ton of systemd services.

** Affects: binutils (Ubuntu)
 Importance: High
 Status: New

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

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

Title:
  New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x

Status in binutils package in Ubuntu:
  New

Bug description:
  Building libxcrypt with the new binutils upload
  2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE
  LOAD header instead of two LOAD headers (one RE, one RW); causing it
  to fail to load in services that use MemoryDenyWriteExecute=yes, thus
  breaking a ton of systemd services.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1958642/+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 1668944] Re: The _apt user ignores group membership.

2022-01-20 Thread Julian Andres Klode
You can of course use ACLs to grant permissions to _apt to individual
files.

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

Title:
  The _apt user ignores group membership.

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Actually I had the same problem described in 
http://askubuntu.com/questions/773955/apt-get-ssl-client-certificate-not-working-on-16-04-error-while-reading-file
  I want to use client certificates with apt. But I don't want to make them 
world readable in order to make apt working. So I created a group 'ssl-cert' 
and changed the group ownership of the ssl cert files to match this group. I 
also added the _apt user to the ssl-cert group.

  Then I tried to open these files as user '_apt' in bash (su -s
  /bin/bash _apt) which works well.

  But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get 
the following error:
  * error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading 
file.)
  * Closing connection 26

  So my guess is that apt somehow ignores the ssl-cert membership.

  Possible workarounds:
  - make ssl client cert world readable
  - change owner ssl client cert to _apt
  - change main group of _apt user from 'nogroup' to 'ssl-cert'
  - set APT::Sandbox::User "root"; in apt.conf.d

  Neither of them is pretty. 
  Maybe this is a wanted behavior, then just suggest how to fix the issue in 
nice way.

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


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


  1   2   3   4   5   6   7   8   9   10   >