Looking at the logs, this bug seems rather to be in
/usr/share/perl5/Debconf/Db.pm, which is in debconf. Reassigning it
there.

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

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

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

Title:
  package libc6 2.35-0ubuntu3 failed to install/upgrade: new libc6:amd64
  package pre-installation script subprocess returned error exit status
  255

Status in debconf package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Invalid

Bug description:
  I have an error there.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libc6 2.35-0ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jul 31 11:39:05 2022
  ErrorMessage: new libc6:amd64 package pre-installation script subprocess 
returned error exit status 255
  InstallationDate: Installed on 2022-07-29 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.6
  SourcePackage: glibc
  Title: package libc6 2.35-0ubuntu3 failed to install/upgrade: new libc6:amd64 
package pre-installation script subprocess returned error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Reply via email to