date:20221202

This bug was fixed in the package alsa-utils - 1.2.8-1ubuntu1

---
alsa-utils (1.2.8-1ubuntu1) lunar; urgency=medium

  * Merge from Debian unstable (LP: #1997569). Remaining changes:
- add 4 patches unset_pulse_internal.patch,
  add_extra_volume_defaults.patch, vmware_audio_volume.patch,
  create_run_alsa.patch

alsa-utils (1.2.8-1) unstable; urgency=medium

  * New upstream release.
  * Apply patch from Jörg-Volker Peetz to properly initialise and
use $ALSACTLRUNTIME in the init script (closes: #1004150).

alsa-utils (1.2.7-1) unstable; urgency=medium

  * New upstream release.
  * Update Standards-Version to 4.6.1 (no changes needed).
  * Install new alsa-topology modules.
  * Remove *.la files from build in override_dh_install.

 -- Nathan Pratta Teodosio   Wed, 23 Nov
2022 10:42:37 -0300

** Changed in: alsa-utils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Merge alsa-utils 1.2.7 from Debian unstable

Status in alsa-utils package in Ubuntu:
  Fix Released

Bug description:
  Please merge alsa-utils 1.2.7 from Debian unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+subscriptions


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

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

[Expired for python-apt (Ubuntu) because there has been no activity for
60 days.]

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

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

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

Status in python-apt package in Ubuntu:
  Expired

Bug description:
  System locked up

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

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


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

[Touch-packages] [Bug 1991427] Re: ssh doesn't offer identity files in the right order

[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ssh doesn't offer identity files in the right order

Status in openssh package in Ubuntu:
  Expired

Bug description:
  "man ssh_config" claims that the "IdentityFile"s will be tried in
  sequence:

  IdentityFile
  Specifies a file from which the user's DSA, ECDSA, 
authenticator-hosted ECDSA, Ed25519, authenticator-hosted Ed25519 or RSA au‐
  thentication identity is read.  The default is ~/.ssh/id_rsa, 
~/.ssh/id_ecdsa, ~/.ssh/id_ecdsa_sk, ~/.ssh/id_ed25519,
  ~/.ssh/id_ed25519_sk and ~/.ssh/id_dsa.  Additionally, any identities 
represented by the authentication agent will be used for
  authentication unless IdentitiesOnly is set.  If no certificates have 
been explicitly specified by CertificateFile, ssh(1) will
  try to load certificate information from the filename obtained by 
appending -cert.pub to the path of a specified IdentityFile.

  Arguments to IdentityFile may use the tilde syntax to refer to a 
user's home directory or the tokens described in the TOKENS sec‐
  tion.

  It is possible to have multiple identity files specified in 
configuration files; all these identities will be tried in sequence.
  Multiple IdentityFile directives will add to the list of identities 
tried (this behaviour differs from that of other configura‐
  tion directives).

  IdentityFile may be used in conjunction with IdentitiesOnly to select 
which identities in an agent are offered during authentica‐
  tion.  IdentityFile may also be used in conjunction with 
CertificateFile in order to provide any certificate also needed for au‐
  thentication with the identity.

  Yet it doesn't try them in the order specified ("id_ed25519-postfix"
  comes before "id_ed25519" in my "~/.ssh/config"):

  debug1: Connection established.
  debug1: identity file /home/user/.ssh/id_ed25519-postfix type 3
  debug1: identity file /home/user/.ssh/id_ed25519-postfix-cert type -1
  debug1: identity file /home/user/.ssh/id_ed25519 type 3
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3
  ...
  debug1: Will attempt key: /home/user/.ssh/id_ed25519 ED25519 
SHA256: explicit agent
  debug1: Will attempt key: /home/user/.ssh/id_ed25519-postfix ED25519 
SHA256: explicit agent

  This causes the wrong key to be used for log in.  This is especially
  problematic when using Git over SSH, which causes the server to report
  repository doesn't exist as the username are the same and the key
  dictates the account being logged in, and instead of getting a
  permission denied the server would give out a more confusing message,
  misleading the direction the user goes to debug.

  Ubuntu 22.04.1 with openssh-client 1:8.9p1-3

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


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

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

[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Expired

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

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

Status in initramfs-tools package in Ubuntu:
  Expired

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

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

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


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

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

2022-12-02 Thread Ilya Leoshkevich

I ran tests 1-3 with Frank's 1:1.2.13.dfsg-1ubuntu3. They all pass; the
performance improvement is also measurable.

Test 4 turned out to be meaningless: Ubuntu requires at least z13.

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

Title:
  Fix for zlib CRC32 optimization for s390x

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

Bug description:
  SRU Justification:
  --

  [ Impact ]

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

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

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

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

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

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

  [ Test Plan ]

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

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

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

   * Test will be done by IBM.

  [ Where problems could occur ]

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

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

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

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

  [ Other Info ]

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

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

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

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

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

  I've attached the updated patch.

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


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

[Touch-packages] [Bug 1998001] Re: Missing tests from libdrm-tests

>From what I can tell an old version of the package did provide kms-
universal-planes but the new version does not. In
http://archive.ubuntu.com/ubuntu/dists/kinetic/universe/cnf/Commands-
amd64.xz we can see:

25486 name: libdrm-tests
25487 version: 2.4.110-1ubuntu1
25488 commands: 
amdgpu_stress,drmdevice,kms-steal-crtc,kms-universal-planes,modeprint,modetest,proptest,vbltest

The date of the file is from 2022-06-27 which is well before the Kinetic
release so this could be an issue with the server providing the cnf
data.

** Changed in: command-not-found (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Missing tests from libdrm-tests

Status in command-not-found package in Ubuntu:
  Confirmed
Status in libdrm package in Ubuntu:
  Confirmed

Bug description:
  It is advertised by the OS that kms-universal-planes can be installed
  via libdrm-tests but this is false:

  $ kms-universal-planes
  Command 'kms-universal-planes' not found, but can be installed with:
  sudo apt install libdrm-tests

  $ sudo apt install libdrm-tests
  [sudo] password for stolk: 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
libdrm-tests
  0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
  Need to get 47.5 kB of archives.
  After this operation, 193 kB of additional disk space will be used.
  Get:1 http://ca.archive.ubuntu.com/ubuntu kinetic/universe amd64 libdrm-tests 
amd64 2.4.113-2 [47.5 kB]
  Fetched 47.5 kB in 0s (142 kB/s)  
  Selecting previously unselected package libdrm-tests.
  (Reading database ... 308766 files and directories currently installed.)
  Preparing to unpack .../libdrm-tests_2.4.113-2_amd64.deb ...
  Unpacking libdrm-tests (2.4.113-2) ...
  Setting up libdrm-tests (2.4.113-2) ...

  $ kms-universal-planes
  Command 'kms-universal-planes' not found, but can be installed with:
  sudo apt install libdrm-tests

  OS: Ubuntu 22.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1998001/+subscriptions


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

[Touch-packages] [Bug 1986521] Re: ssh client spins if output fd closed

2022-12-02 Thread Bryce Harrington

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

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

Title:
  ssh client spins if output fd closed

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Jammy:
  In Progress

Bug description:
  [Impact]
  In certain edge cases where the terminal goes away while an ssh process is 
running, ssh can be left consuming 100% CPU.  This increases processing costs 
for cloud users and wastes energy.  While this is an uncommon error, googling 
indicates many people have run into it in several different ways.   It seems 
important to get this fixed in stable releases.

  This is a regression in jammy presumably due to change from select()
  to poll() (see OpennSSH 8.9 Release Announcement [1] ), fixed by
  upstream commit d6556de1db0822c76ba2745cf5c097d9472adf7c "upstream:
  fix poll() spin when a channel's output fd closes..." [2].

  1: https://lwn.net/Articles/885886/
  2. 
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c

  [Test Case]
  $ lxc launch ubuntu-daily:jammy ssh-cpu
  $ lxc shell ssh-cpu

  # passwd -d root
  # ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa

  # cat << EOF >>/etc/ssh/ssh_config
  StrictHostKeyChecking accept-new
  EOF

  # sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/' 
/etc/ssh/sshd_config
  # cat << EOF >>/etc/ssh/sshd_config
  PermitRootLogin yes
  PubkeyAuthentication yes
  PermitEmptyPasswords yes
  PasswordAuthentication yes
  ChallengeResponseAuthentication no
  UsePAM no
  EOF

  # systemctl restart sshd

  # ssh localhost 2> >({exec 1>&2})

  You can shell into the container from a second terminal and use "htop"
  to verify that ssh is using 100% of one of the CPU cores:

  $ lxc shell ssh-cpu
  # htop

  This should show one CPU pegged at 100% due to the 'ssh localhost'
  process

  Next, return to the first terminal, exit out of the sub-ssh session and
  install the fix:

  # logout
  # add-apt-repository -yus ppa:bryce/openssh-sru-lp1986521
  # apt-get full-upgrade -y

  Now repeat the test in the first terminal window, while viewing htop in
  the second terminal:

  # ssh localhost 2> >({exec 1>&2})

  [Where Problems Could Occur]

  While the patch in question is well tested upstream, it has a
  relatively high line count and as such is difficult to assure
  correctness by visual code checking.  However, it's not clear that the
  line count could be significantly reduced without risking loss of
  correctness.  Thus this relies more on testing to assure robustness,
  than on code review.

  The code involves polling behavior, so issues to watch for would more
  likely involve process handling, i.e. problems with socket polling.

  Beyond that, the usual generic issues to watch for - build issues,
  dependency issues during build or on upgrade, and service restarting.

  [Original Report]
  The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the 
bug described at
  https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and 
https://bugzilla.mindrot.org/show_bug.cgi?id=3405

  A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
  an xterm, ask for whatever authentication is needed, close the xterm,
  and leave the ssh client spinning consuming CPU time for 60 seconds
  before it exits. It should leave the ssh client idle for 60 seconds.
  Many uses of ssh to launch graphical applications will be caught by
  this bug.

  This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its
  release notes at https://www.openssh.com/txt/release-9.0

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


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

[Touch-packages] [Bug 1998321] Re: tzdata 2022g release

This bug was fixed in the package tzdata - 2022g-0ubuntu2

---
tzdata (2022g-0ubuntu2) lunar; urgency=medium

  * Update the ICU timezone data to 2022g (LP: #1998321)
  * Point Vcs-Browser/Git to Launchpad

 -- Benjamin Drung   Thu, 01 Dec 2022 13:30:43 +0100

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

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

Title:
  tzdata 2022g release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  The 2022g release contains the following changes:

  * The northern edge of Chihuahua changes to US timekeeping.
  * Much of Greenland stops changing clocks after March 2023.
  * Fix some pre-1996 timestamps in northern Canada.
  * C89 is now deprecated; please use C99 or later.
  * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
  * In C code, use more C23 features if available.
  * C23 timegm now supported by default
  * Fixes for unlikely integer overflows

  Changes to future timestamps:

  In the Mexican state of Chihuahua, the border strip near the US will
  change to agree with nearby US locations on 2022-11-30. The strip's
  western part, represented by Ciudad Juárez, switches from -06 all year
  to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
  represented by Ojinaga, will observe US DST next year, like Presidio,
  TX.  (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
  splits from America/Ojinaga.

  Much of Greenland, represented by America/Nuuk, stops observing winter
  time after March 2023, so its daylight saving time becomes standard
  time.  (Thanks to Jonas Nyrup and Jürgen Appel.)

  ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
  CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [ Test Case for all releases ]
  1) dpkg -s tzdata | grep ^Version
  2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
    -> should have output, last dates should be in 2499

  
  [Test case for releases >= 20.04 LTS]

  from datetime import datetime, timedelta
  from icu import ICUtzinfo, TimeZone
  tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
  assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

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


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

[Touch-packages] [Bug 1998265] Re: OverFlow error when using cnf-extractor

I removed the try / except OverflowError handling in the production
command-not-found-extractor and was able to run the job successfully
with the new version of python-apt.

ubuntu@juju-8cacac-prod-cnf-extractor-0:/srv/cnf-extractor$ apt-cache policy 
python3-apt
python3-apt:
  Installed: 1.6.6
  Candidate: 1.6.6
  Version table:
 *** 1.6.6 500
500 http://prodstack-zone-1.clouds.archive.ubuntu.com/ubuntu 
bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1.6.5ubuntu0.7 500
500 http://prodstack-zone-1.clouds.archive.ubuntu.com/ubuntu 
bionic-updates/main amd64 Packages
 1.6.5ubuntu0.5 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 1.6.0 500
500 http://prodstack-zone-1.clouds.archive.ubuntu.com/ubuntu 
bionic/main amd64 Packages


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

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

Title:
  OverFlow error when using cnf-extractor

Status in python-apt package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Focal:
  Fix Committed
Status in python-apt source package in Jammy:
  Fix Committed
Status in python-apt source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  Large files can't be downloaded as we use a 32-bit integer in AcquireFile 
constructor, this breaks e.g. command-not-found generator:

  I'm trying to update the command-not-found indexes (bin/cnf-extract.py
  $MIRROR $suite $component $arch) on the production cnf extractor
  system (running bionic) and have encountered Tracebacks when
  generating them for Jammy and Lunar. This is causing the command not
  found indexes to be out of date for all(?) releases of Ubuntu.

  The lunar failure:

  Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB]
  Fetched 79.1 MB in 0s (0 B/s)
  Traceback (most recent call last):64... 7%
    File "./bin/cnf-extract.py", line 54, in 
  mirror_root, suite, component, arch)
    File "/srv/cnf-extractor/extractor/extractor.py", line 174, in 
command_not_found_extract
  debpath = pkg.candidate.fetch_binary(destdir=tmpdir)
    File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in 
fetch_binary
  self.size, base, destfile=destfile)
  OverflowError: signed integer is greater than maximum

  I'll get more context for the Jammy failure but it wouldn't surprise
  me if it was the same package.

  [Test plan]
  I have included a test for the AcquireFile constructor to accept a large file 
size, and then a test that ensures it can read the file size.

  Run the autopkgtest suite.

  [Where problems could occur]
  It could fail in other places now.

  For kinetic, the package was copied in from lunar without changes.
  This upload is actually built in kinetic and hence there is additional
  regression potential from toolchain changes.

  [Other info]
  Also including some auxiliary changes as we move back to proper upstream 
releases to enable testing, mostly around

  d/gbp.conf, .gitlab-ci.yml - being updated to point at right places
  d/t/control - adding a missing test dependency
  data/ - updated mirror lists

  The mirror lists are standard updates; the debian/tests/control change
  is needed to enable testing on more minimal autopkgtest images (our images
  accidentally include binutils); the other changes have zero impact on the 
Ubuntu infra or end user side as they only run during development.

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


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

[Touch-packages] [Bug 1998646] [NEW] package linux-image-5.15.0-56-generic 5.15.0-56.62 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-12-02 Thread jerry

Public bug reported:

non

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-56-generic 5.15.0-56.62
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  linux 11829 F pulseaudio
 /dev/snd/controlC0:  linux 11829 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Dec  2 21:38:18 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-11-21 (10 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 81VS
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic 
root=UUID=6f662067-919a-4e3a-80c0-94f1d664aeaf ro recovery nomodeset 
dis_ucode_ldr
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu7
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-56-generic 5.15.0-56.62 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2019
dmi.bios.release: 1.13
dmi.bios.vendor: LENOVO
dmi.bios.version: CWCN13WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76445 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Slim 1-14AST-05
dmi.ec.firmware.release: 1.10
dmi.modalias: 
dmi:bvnLENOVO:bvrCWCN13WW:bd08/29/2019:br1.13:efr1.10:svnLENOVO:pn81VS:pvrLenovoIdeaPadSlim1-14AST-05:rvnLENOVO:rnLNVNB161216:rvrSDK0T76445WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadSlim1-14AST-05:skuLENOVO_MT_81VS_BU_idea_FM_IdeaPadSlim1-14AST-05:
dmi.product.family: IdeaPad Slim 1-14AST-05
dmi.product.name: 81VS
dmi.product.sku: LENOVO_MT_81VS_BU_idea_FM_IdeaPad Slim 1-14AST-05
dmi.product.version: Lenovo IdeaPad Slim 1-14AST-05
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  non

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-56-generic 5.15.0-56.62
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  linux 11829 F pulseaudio
   /dev/snd/controlC0:  linux 11829 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Dec  2 21:38:18 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-11-21 (10 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 81VS
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic 
root=UUID=6f662067-919a-4e3a-80c0-94f1d664aeaf ro recovery nomodeset 
dis_ucode_ldr
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-56-generic 5.15.0-56.62 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2019
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CWCN13WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76445 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Slim 1-14AST-05
  dmi.ec.firmware.release: 1.10
  dmi.modalias:

[Touch-packages] [Bug 1997201] Re: BlueZ 5.66 release

This bug was fixed in the package bluez - 5.66-0ubuntu1

---
bluez (5.66-0ubuntu1) lunar; urgency=medium

  * New upstream release 5.66 (LP: #1997201):
- Fix issue with A2DP and transport connection collisions.
- Fix issue with allowing application specific error codes.
- Fix issue with not setting initiator flag correctly.
- Fix issue with HoG Report MAP size handling.
- Add initial support for Basic Audio Profile.
- Add initial support for Volume Control Profile.
  * Refreshed patches:
- raspi-bcm43xx-load-firmware.patch

 -- Daniel van Vugt   Wed, 30 Nov 2022
16:31:09 +0800

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

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

Title:
  BlueZ 5.66 release

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release to Lunar:

  http://www.bluez.org/release-of-bluez-5-66/

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


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

[Touch-packages] [Bug 1998265] Please test proposed package

Hello Brian, or anyone else affected,

Accepted python-apt into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-apt/2.0.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

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

** Changed in: python-apt (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  OverFlow error when using cnf-extractor

Status in python-apt package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Focal:
  Fix Committed
Status in python-apt source package in Jammy:
  Fix Committed
Status in python-apt source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  Large files can't be downloaded as we use a 32-bit integer in AcquireFile 
constructor, this breaks e.g. command-not-found generator:

  I'm trying to update the command-not-found indexes (bin/cnf-extract.py
  $MIRROR $suite $component $arch) on the production cnf extractor
  system (running bionic) and have encountered Tracebacks when
  generating them for Jammy and Lunar. This is causing the command not
  found indexes to be out of date for all(?) releases of Ubuntu.

  The lunar failure:

  Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB]
  Fetched 79.1 MB in 0s (0 B/s)
  Traceback (most recent call last):64... 7%
    File "./bin/cnf-extract.py", line 54, in 
  mirror_root, suite, component, arch)
    File "/srv/cnf-extractor/extractor/extractor.py", line 174, in 
command_not_found_extract
  debpath = pkg.candidate.fetch_binary(destdir=tmpdir)
    File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in 
fetch_binary
  self.size, base, destfile=destfile)
  OverflowError: signed integer is greater than maximum

  I'll get more context for the Jammy failure but it wouldn't surprise
  me if it was the same package.

  [Test plan]
  I have included a test for the AcquireFile constructor to accept a large file 
size, and then a test that ensures it can read the file size.

  Run the autopkgtest suite.

  [Where problems could occur]
  It could fail in other places now.

  For kinetic, the package was copied in from lunar without changes.
  This upload is actually built in kinetic and hence there is additional
  regression potential from toolchain changes.

  [Other info]
  Also including some auxiliary changes as we move back to proper upstream 
releases to enable testing, mostly around

  d/gbp.conf, .gitlab-ci.yml - being updated to point at right places
  d/t/control - adding a missing test dependency
  data/ - updated mirror lists

  The mirror lists are standard updates; the debian/tests/control change
  is needed to enable testing on more minimal autopkgtest images (our images
  accidentally include binutils); the other changes have zero impact on the 
Ubuntu infra or end user side as they only run during development.

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


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

[Touch-packages] [Bug 1998265] Please test proposed package

Hello Brian, or anyone else affected,

Accepted python-apt into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-apt/1.6.6 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

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

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

Title:
  OverFlow error when using cnf-extractor

Status in python-apt package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Focal:
  Fix Committed
Status in python-apt source package in Jammy:
  Fix Committed
Status in python-apt source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  Large files can't be downloaded as we use a 32-bit integer in AcquireFile 
constructor, this breaks e.g. command-not-found generator:

  I'm trying to update the command-not-found indexes (bin/cnf-extract.py
  $MIRROR $suite $component $arch) on the production cnf extractor
  system (running bionic) and have encountered Tracebacks when
  generating them for Jammy and Lunar. This is causing the command not
  found indexes to be out of date for all(?) releases of Ubuntu.

  The lunar failure:

  Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB]
  Fetched 79.1 MB in 0s (0 B/s)
  Traceback (most recent call last):64... 7%
    File "./bin/cnf-extract.py", line 54, in 
  mirror_root, suite, component, arch)
    File "/srv/cnf-extractor/extractor/extractor.py", line 174, in 
command_not_found_extract
  debpath = pkg.candidate.fetch_binary(destdir=tmpdir)
    File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in 
fetch_binary
  self.size, base, destfile=destfile)
  OverflowError: signed integer is greater than maximum

  I'll get more context for the Jammy failure but it wouldn't surprise
  me if it was the same package.

  [Test plan]
  I have included a test for the AcquireFile constructor to accept a large file 
size, and then a test that ensures it can read the file size.

  Run the autopkgtest suite.

  [Where problems could occur]
  It could fail in other places now.

  For kinetic, the package was copied in from lunar without changes.
  This upload is actually built in kinetic and hence there is additional
  regression potential from toolchain changes.

  [Other info]
  Also including some auxiliary changes as we move back to proper upstream 
releases to enable testing, mostly around

  d/gbp.conf, .gitlab-ci.yml - being updated to point at right places
  d/t/control - adding a missing test dependency
  data/ - updated mirror lists

  The mirror lists are standard updates; the debian/tests/control change
  is needed to enable testing on more minimal autopkgtest images (our images
  accidentally include binutils); the other changes have zero impact on the 
Ubuntu infra or end user side as they only run during development.

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


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

[Touch-packages] [Bug 1998265] Re: OverFlow error when using cnf-extractor

Hello Brian, or anyone else affected,

Accepted python-apt into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-apt/2.4.0 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

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

** Changed in: python-apt (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed-jammy

** Changed in: python-apt (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  OverFlow error when using cnf-extractor

Status in python-apt package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Focal:
  Fix Committed
Status in python-apt source package in Jammy:
  Fix Committed
Status in python-apt source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  Large files can't be downloaded as we use a 32-bit integer in AcquireFile 
constructor, this breaks e.g. command-not-found generator:

  I'm trying to update the command-not-found indexes (bin/cnf-extract.py
  $MIRROR $suite $component $arch) on the production cnf extractor
  system (running bionic) and have encountered Tracebacks when
  generating them for Jammy and Lunar. This is causing the command not
  found indexes to be out of date for all(?) releases of Ubuntu.

  The lunar failure:

  Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB]
  Fetched 79.1 MB in 0s (0 B/s)
  Traceback (most recent call last):64... 7%
    File "./bin/cnf-extract.py", line 54, in 
  mirror_root, suite, component, arch)
    File "/srv/cnf-extractor/extractor/extractor.py", line 174, in 
command_not_found_extract
  debpath = pkg.candidate.fetch_binary(destdir=tmpdir)
    File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in 
fetch_binary
  self.size, base, destfile=destfile)
  OverflowError: signed integer is greater than maximum

  I'll get more context for the Jammy failure but it wouldn't surprise
  me if it was the same package.

  [Test plan]
  I have included a test for the AcquireFile constructor to accept a large file 
size, and then a test that ensures it can read the file size.

  Run the autopkgtest suite.

  [Where problems could occur]
  It could fail in other places now.

  For kinetic, the package was copied in from lunar without changes.
  This upload is actually built in kinetic and hence there is additional
  regression potential from toolchain changes.

  [Other info]
  Also including some auxiliary changes as we move back to proper upstream 
releases to enable testing, mostly around

  d/gbp.conf, .gitlab-ci.yml - being updated to point at right places
  d/t/control - adding a missing test dependency
  data/ - updated mirror lists

  The mirror lists are standard updates; the debian/tests/control change
  is needed to enable testing on more minimal autopkgtest images (our images
  accidentally include binutils); the other changes have zero impact on the 
Ubuntu infra or end user side as they only run during development.

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


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

[Touch-packages] [Bug 1998488] Re: Wrong type annotation in apt.progress.text.AcquireProgress

Hello Julian, or anyone else affected,

Accepted python-apt into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-apt/2.4.0 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

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

** Changed in: python-apt (Ubuntu Jammy)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  Wrong type annotation in apt.progress.text.AcquireProgress

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Jammy:
  Fix Committed
Status in python-apt source package in Kinetic:
  Fix Committed
Status in python-apt source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Type checking fails in CI

  [Test plan]
  Have CI type check successfully

  [Where problems could occur]
  It's only a comment *inside* the function, so not really anywhere.

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


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

[Touch-packages] [Bug 1998265] Re: OverFlow error when using cnf-extractor

Hello Brian, or anyone else affected,

Accepted python-apt into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
apt/2.4.0+22.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

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

** Changed in: python-apt (Ubuntu Kinetic)
   Status: New => Fix Committed

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

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

Title:
  OverFlow error when using cnf-extractor

Status in python-apt package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  In Progress
Status in python-apt source package in Focal:
  In Progress
Status in python-apt source package in Jammy:
  Fix Committed
Status in python-apt source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  Large files can't be downloaded as we use a 32-bit integer in AcquireFile 
constructor, this breaks e.g. command-not-found generator:

  I'm trying to update the command-not-found indexes (bin/cnf-extract.py
  $MIRROR $suite $component $arch) on the production cnf extractor
  system (running bionic) and have encountered Tracebacks when
  generating them for Jammy and Lunar. This is causing the command not
  found indexes to be out of date for all(?) releases of Ubuntu.

  The lunar failure:

  Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB]
  Fetched 79.1 MB in 0s (0 B/s)
  Traceback (most recent call last):64... 7%
    File "./bin/cnf-extract.py", line 54, in 
  mirror_root, suite, component, arch)
    File "/srv/cnf-extractor/extractor/extractor.py", line 174, in 
command_not_found_extract
  debpath = pkg.candidate.fetch_binary(destdir=tmpdir)
    File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in 
fetch_binary
  self.size, base, destfile=destfile)
  OverflowError: signed integer is greater than maximum

  I'll get more context for the Jammy failure but it wouldn't surprise
  me if it was the same package.

  [Test plan]
  I have included a test for the AcquireFile constructor to accept a large file 
size, and then a test that ensures it can read the file size.

  Run the autopkgtest suite.

  [Where problems could occur]
  It could fail in other places now.

  For kinetic, the package was copied in from lunar without changes.
  This upload is actually built in kinetic and hence there is additional
  regression potential from toolchain changes.

  [Other info]
  Also including some auxiliary changes as we move back to proper upstream 
releases to enable testing, mostly around

  d/gbp.conf, .gitlab-ci.yml - being updated to point at right places
  d/t/control - adding a missing test dependency
  data/ - updated mirror lists

  The mirror lists are standard updates; the debian/tests/control change
  is needed to enable testing on more minimal autopkgtest images (our images
  accidentally include binutils); the other changes have zero impact on the 
Ubuntu infra or end user side as they only run during development.

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


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

[Touch-packages] [Bug 1998408] Re: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with lib

2022-12-02 Thread Hans Joachim Desserud

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

** This bug has been marked a duplicate of bug 1998407
   package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package 
libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not 
co-installable with libnih-dbus1 which has multiple installed instances

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

Title:
  package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package
  libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not
  co-installable with libnih-dbus1 which has multiple installed
  instances

Status in libnih package in Ubuntu:
  New

Bug description:
  Did not install

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libnih-dbus1 1.0.3-6ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_48_54_generic_90
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Nov 16 16:41:22 2022
  DuplicateSignature:
   package:libnih-dbus1:1.0.3-6ubuntu2
   Unpacking libnfsidmap1:amd64 (1:2.6.1-1ubuntu1.1) over (1:2.6.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-5AFDRm/154-libnih-dbus1_1.0.3-12build1_amd64.deb 
(--unpack):
package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is 
not co-installable with libnih-dbus1 which has multiple installed instances
  ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 
'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple 
installed instances
  InstallationDate: Installed on 2014-09-14 (2999 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: libnih
  Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package 
libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not 
co-installable with libnih-dbus1 which has multiple installed instances
  UpgradeStatus: Upgraded to jammy on 2022-08-23 (99 days ago)

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


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

[Touch-packages] [Bug 1998488] Re: Wrong type annotation in apt.progress.text.AcquireProgress

Hello Julian, or anyone else affected,

Accepted python-apt into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
apt/2.4.0+22.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

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

** Changed in: python-apt (Ubuntu Kinetic)
   Status: Triaged => Fix Committed

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

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

Title:
  Wrong type annotation in apt.progress.text.AcquireProgress

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Jammy:
  Fix Committed
Status in python-apt source package in Kinetic:
  Fix Committed
Status in python-apt source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Type checking fails in CI

  [Test plan]
  Have CI type check successfully

  [Where problems could occur]
  It's only a comment *inside* the function, so not really anywhere.

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


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

[Touch-packages] [Bug 1997124] Re: Netplan/Systemd/Cloud-init/Dbus Race

2022-12-02 Thread James Falcon

** Changed in: cloud-init
   Status: New => Triaged

** Changed in: cloud-init
   Importance: Undecided => High

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

Title:
  Netplan/Systemd/Cloud-init/Dbus Race

Status in cloud-init:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  Cloud-init is seeing intermittent failures while running `netplan
  apply`, which appears to be caused by a missing resource at the time
  of call.

  The symptom in cloud-init logs looks like:

  Running ['netplan', 'apply'] resulted in stderr output: Failed to
  connect system bus: No such file or directory

  I think that this error[1] is likely caused by cloud-init running
  netplan apply too early in boot process (before dbus is active).

  Today I stumbled upon this error which was hit in MAAS[2]. We have
  also hit it intermittently during tests (we didn't have a reproducer).

  Realizing that this may not be a cloud-init error, but possibly a
  dependency bug between dbus/systemd we decided to file this bug for
  broader visibility to other projects.

  I will follow up this initial report with some comments from our
  discussion earlier.

  [1] https://github.com/canonical/netplan/blob/main/src/dbus.c#L801
  [2] 
https://discourse.maas.io/t/latest-ubuntu-20-04-image-causing-netplan-error/5970

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1997124/+subscriptions


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

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

2022-12-02 Thread EML

Another datapoint. Just upgraded a laptop from 20.04 to 22.04.

1 - the laptop itself has no problem running Chromium or Firefox. When
run from a terminal, DBUS_SESSION_BUS_ADDRESS is
'unix:path=/run/user/1000/bus'

2 - When connecting over vnc, using the 'normal' xstartup (which must
have been on the net for 15-odd years), I see exactly this problem, but
for 'session-5.scope'. DBUS_SESSION_BUS_ADDRESS is
'unix:abstract=/tmp/dbus-
joEHty7pAj,guid=64e54e1c9ccf659527b095906389fcc0'. This xstartup is
shown as config (1) below

3 - I'm using tigervnc. If I don't have a ~/.vnc/xstartup it defaults to
/etc/X11/Xtigervnc-session (see /etc/tigervnc/vncserver-config-
defaults). This is shown as config (2) below. When using this default,
Chromium and Firefox work Ok, with the 'correct'
DBUS_SESSION_BUS_ADDRESS

Ergo this is just one more problem with vnc/remote desktop setup, which
is almost entirely unsupported on Ubuntu, Debian, and RedHat. Clearly
the people running on bare metal have a slightly different issue, but I
bet it has the same root cause. With config (1), I also get a pop-up
saying that 'The application IBus Preferences has closed unexpectedly'.
Note also, while I'm complaining, that this is the second snap issue
that I've had to deal with today to get 22.04 running (see
https://github.com/snapcore/snapd-desktop-
integration/issues/23#issuecomment-1335072721). I also do a server image
for 22.04.1, which has snap completely removed (because it is, in more
ways than one, a waste of space), but Canonical seem to be going out of
their way to make this impossible on desktop (ironic, since snap was
meant to be for servers).

Config 1:

#!/bin/sh
# Start up the standard system desktop
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS

#/usr/bin/startxfce4
/usr/bin/gnome-session

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
x-window-manager &

Config 2:

#! /bin/sh

test x"$SHELL" = x"" && SHELL=/bin/bash
test x"$1" = x"" && set -- default

if test -r /etc/default/keyboard &&
   test -x /usr/bin/setxkbmap; then
  . /etc/default/keyboard
  /usr/bin/setxkbmap \
-model   "${XKBMODEL}" \
-layout  "${XKBLAYOUT}" \
-variant "${XKBVARIANT}" \
"${XKBOPTIONS}"
fi

tigervncconfig -iconic &
"$SHELL" -l

[Touch-packages] [Bug 1996937] Re: "install vim failed"package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller ava

2022-12-02 Thread gueye-mary boudier

my probleme is solved by this following action

RESOLUTION
reinstaller le TZDATA =>

faire une purge des elements inutiles des precedentes installation

sudo apt purge ~c
sudo apt install --reinstall tzdata

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

Title:
  "install vim failed"package tzdata 2022f-0ubuntu0.22.04.1 failed to
  install/upgrade: le paquet est dans un état vraiment incohérent; vous
  devriez  le réinstaller avant de tenter de le configurer.

Status in tzdata package in Ubuntu:
  New

Bug description:
  trying to install vim but i occured an error

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: tzdata 2022f-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   vim-runtime:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Nov 17 20:00:11 2022
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2022-11-12 (4 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: tzdata
  Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result

2022-12-02 Thread Adrien Nader

** Changed in: openssl (Ubuntu Jammy)
 Assignee: (unassigned) => Adrien Nader (adrien-n)

** Changed in: openssl (Ubuntu Kinetic)
 Assignee: (unassigned) => Adrien Nader (adrien-n)

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Adrien Nader (adrien-n)

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

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

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

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Incomplete
Status in openssl source package in Jammy:
  Incomplete
Status in openssl source package in Kinetic:
  Incomplete

Bug description:
  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code
  
  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.
  
  This patch handles the SMIME_crlf_copy return code in all occurrences.
  
  Signed-off-by: Alon Bar-Lev 
  
  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

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


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

[Touch-packages] [Bug 1998415] Re: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install)

2022-12-02 Thread Nick Rosbrook

Ah yeah, this would do it:

E: Release file for 
http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease is not valid 
yet (invalid for another 10h 24min 10s). Updates for this repository will not 
be applied.
E: Release file for 
http://in.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease is not valid 
yet (invalid for another 10h 24min 28s). Updates for this repository will not 
be applied.
E: Release file for 
http://in.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease is not 
valid yet (invalid for another 10h 24min 59s). Updates for this repository will 
not be applied.

Glad it's resolved now.

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

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

Title:
  jammy libsystemd-dev has wrong dependency version to libsystemd0 (and
  fails to install)

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  jammy libsystemd-dev has wrong dependency version to libsystemd0 (and
  fails to install)

  libsystemd-dev wants libsystemd0 = 249.11-0ubuntu3 but
  249.11-0ubuntu3.6 is installed.

  installation currently fails:
  intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt-get install libsystemd-dev
  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:
   libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.6 is to be installed
  E: Unable to correct problems, you have held broken packages.

  FYI,

  intel@intel-Raptor-Lake-Client-Platform:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.1 LTS Customized image
  Release:22.04
  Codename:   jammy

  
  intel@intel-Raptor-Lake-Client-Platform:~$ dpkg -l libsystemd0
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version   Architecture Description
  
+++-=-=--=
  ii  libsystemd0:amd64 249.11-0ubuntu3.6 amd64systemd utility library
  intel@intel-Raptor-Lake-Client-Platform:~$

  intel@intel-Raptor-Lake-Client-Platform:~$ apt-cache madison libsystemd0
  libsystemd0 | 249.11-0ubuntu3 | http://in.archive.ubuntu.com/ubuntu 
jammy/main amd64 Packages

  intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt search libsystemd
  Sorting... Done
  Full Text Search... Done
  librust-libsystemd-dev/jammy,now 0.2.1-2build1 amd64 [installed]
    Pure-Rust client library to interact with systemd - Rust source code

  libsystemd-dev/jammy 249.11-0ubuntu3 amd64
    systemd utility library - development files

  libsystemd0/jammy 249.11-0ubuntu3 i386
    systemd utility library

  lua-systemd/jammy,now 0~git20160517-2 amd64 [installed]
    Systemd bindings for Lua

  python3-systemd/jammy,now 234-3ubuntu2 amd64 [installed,automatic]
    Python 3 bindings for systemd

  intel@intel-Raptor-Lake-Client-Platform:~$

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


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

[Touch-packages] [Bug 1998604] [NEW] bug on xsd validation with emojii and/or unicode characters

2022-12-02 Thread dariocaruso

Public bug reported:

using libxml2 to validate a field with a maxLength of characters does
not work, because it does not count unicode emojii characters.

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

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

Title:
  bug on xsd validation with emojii and/or unicode characters

Status in libxml2 package in Ubuntu:
  New

Bug description:
  using libxml2 to validate a field with a maxLength of characters does
  not work, because it does not count unicode emojii characters.

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


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

[Touch-packages] [Bug 1998058] Re: dpkg error libflac8_1.3.2-1ubuntu0.1_i386.deb

2022-12-02 Thread Camila Camargo de Matos

Hello Hector,

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug, as I was unable to reproduce the
issue.

We will proceed with investigations, but meanwhile, since there have
been reports of similar bugs in the past (such as LP#1784065) , maybe
one of the following could be attempted in order to fix your issue:

- Run "dpkg --configure -a" and "apt-get -f install" in your system and
then try the upgrade once again.

- Execute the steps in this Wiki page
https://wiki.ubuntu.com/DebuggingInstallationIssues#triggers_ci_file_contains_unknown_directive_syntax
and then run the upgrade command once again.

Please let us know if any of the above solutions help in any way, and
please feel free to report any other bugs you may find.

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

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

Title:
  dpkg error libflac8_1.3.2-1ubuntu0.1_i386.deb

Status in flac package in Ubuntu:
  Incomplete

Bug description:
  Hi the Recent security patch for libflac8 is not installing :

  Preparing to unpack .../libflac8_1.3.2-1ubuntu0.1_i386.deb ...
  dpkg: error processing archive 
/var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb (--unpack):
   triggers ci file contains unknown directive 'libcrypto'
  Errors were encountered while processing:
   /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  I am running : 

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04
  Codename: bionic

  4.15.0-191-generic

  libflac8:
Installed: 1.3.2-1
Candidate: 1.3.2-1ubuntu0.1
Version table:
   1.3.2-1ubuntu0.1 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic-security/main i386 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
   *** 1.3.2-1 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  Thank you

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


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

[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe

2022-12-02 Thread Alfonso Sanchez-Beato

It turns out that this actually regressed some qualcomm modems because
modem-manager started to use some special netlink sockets that were not
enabled in the 5.4 kernel.

To have that we need (see LP: #1998194):

CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m

in the 5.4 kernel. However, this might not be easy according to some
discussion I had. Would it be possible to revisit this backport?

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Focal:
  Fix Released
Status in libqmi source package in Focal:
  Fix Released
Status in modemmanager source package in Focal:
  Fix Released

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2022-12-02 Thread Neoon

"Fix" as suggested by the dev's would be upgrading to 5.x LTS with:

"snap refresh lxd --channel=5.0/stable"

Same error, however doesn't seem to affect anything anymore.

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


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

[Touch-packages] [Bug 1998592] Re: in specific situations, nano can eat characters

2022-12-02 Thread Benno Schulenberg

(I've updated the description because Launchpad shrinks double blanks
into a single blank, breaking the original recipe.  The original report
is in https://savannah.gnu.org/bugs/?63407.)

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

Title:
  in specific situations, nano can eat characters

Status in nano package in Ubuntu:
  New

Bug description:
  Reproduction recipe:

  printf "two words\n second line\n"  >words

  nano --ignore --auto --break  +,2 words

  Then press Enter.  See how "t" from the first word has *disappeared*.
  This is wrong.  And what is worse: M-U does not bring the eaten letter
  back.

  Attached patch has been applied upstream to fix the issue.  Please
  consider applying it to nano-6.2 in Jammy (22.04), and maybe also to
  nano-4.8 in Focal (20.04).

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


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

[Touch-packages] [Bug 1998592] [NEW] in specific situations, nano can eat characters

2022-12-02 Thread Benno Schulenberg

Public bug reported:

Reproduction recipe:

printf "two words\n second line\n" >words

nano --ignore --auto --break +,2 words

Then press Enter. See how "t" from the first word has *disappeared*.
This is wrong. And what is worse: M-U does not bring the eaten letter
back.

Attached patch has been applied upstream to fix the issue. Please
consider applying it to nano-6.2 in Jammy (22.04), and maybe also to
nano-4.8 in Focal (20.04).

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

** Tags: patch-accepted-upstream

** Attachment added: "prevent from eating non-blanks"

https://bugs.launchpad.net/bugs/1998592/+attachment/5633931/+files/0001-text-upon-Enter-eat-only-lefthand-blanks-not-any-oth.patch

** Description changed:

Reproduction recipe:

- printf "two words\n second line\n" >words
+ printf "two words\n second line\n" >words

- src/nano --ignore --auto --break +,3 words
+ nano --ignore --auto --break +,3 words

Then press Enter. See how "tw" from the first word has *disappeared*.
This is wrong. And what is worse: M-U does not bring the eaten letters
back.

Attached patch has been applied upstream to fix the issue. Please
consider applying it to nano-6.2 in Jammy (22.04), and maybe also to
nano-4.8 in Focal (20.04).

** Description changed:

Reproduction recipe:

- printf "two words\n second line\n" >words
+ printf "two words\n second line\n" >words

- nano --ignore --auto --break +,3 words
+ nano --ignore --auto --break +,2 words

- Then press Enter. See how "tw" from the first word has *disappeared*.
- This is wrong. And what is worse: M-U does not bring the eaten letters
+ Then press Enter. See how "t" from the first word has *disappeared*. This
is wrong. And what is worse: M-U does not bring the eaten letter
back.

Attached patch has been applied upstream to fix the issue. Please
consider applying it to nano-6.2 in Jammy (22.04), and maybe also to
nano-4.8 in Focal (20.04).

** Description changed:

Reproduction recipe:

printf "two words\n second line\n" >words

nano --ignore --auto --break +,2 words

- Then press Enter. See how "t" from the first word has *disappeared*. This
is wrong. And what is worse: M-U does not bring the eaten letter
+ Then press Enter. See how "t" from the first word has *disappeared*.
+ This is wrong. And what is worse: M-U does not bring the eaten letter
back.

Attached patch has been applied upstream to fix the issue. Please
consider applying it to nano-6.2 in Jammy (22.04), and maybe also to
nano-4.8 in Focal (20.04).

** Bug watch added: GNU Savannah Bug Tracker #63407
http://savannah.gnu.org/bugs/?63407

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

Title:
in specific situations, nano can eat characters

Status in nano package in Ubuntu:
New

Bug description:
Reproduction recipe:

printf "two words\n second line\n" >words

nano --ignore --auto --break +,2 words

Then press Enter. See how "t" from the first word has *disappeared*.
This is wrong. And what is worse: M-U does not bring the eaten letter
back.

Attached patch has been applied upstream to fix the issue. Please
consider applying it to nano-6.2 in Jammy (22.04), and maybe also to
nano-4.8 in Focal (20.04).

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

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

[Touch-packages] [Bug 1998058] Re: dpkg error libflac8_1.3.2-1ubuntu0.1_i386.deb

2022-12-02 Thread Camila Camargo de Matos

** Changed in: flac (Ubuntu)
 Assignee: (unassigned) => Camila Camargo de Matos (ccdm94)

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

Title:
  dpkg error libflac8_1.3.2-1ubuntu0.1_i386.deb

Status in flac package in Ubuntu:
  New

Bug description:
  Hi the Recent security patch for libflac8 is not installing :

  Preparing to unpack .../libflac8_1.3.2-1ubuntu0.1_i386.deb ...
  dpkg: error processing archive 
/var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb (--unpack):
   triggers ci file contains unknown directive 'libcrypto'
  Errors were encountered while processing:
   /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  I am running : 

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04
  Codename: bionic

  4.15.0-191-generic

  libflac8:
Installed: 1.3.2-1
Candidate: 1.3.2-1ubuntu0.1
Version table:
   1.3.2-1ubuntu0.1 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic-security/main i386 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
   *** 1.3.2-1 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  Thank you

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


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

[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

Could someone perhaps try to report the problem on
https://github.com/fontforge/fontforge/issues ?

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

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


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

[Touch-packages] [Bug 1844897] Re: wifi icon has question mark in it even though network is fine

There was some issues with the connectivity server returning
inconsistent statuses, that has been fixed now, could you check if that
resolves the flaky indicator issue for you maybe?

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

Title:
  wifi icon has question mark in it even though network is fine

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After experiencing some "turbulence" in my wifi (I rebooted my primary
  wifi router, which caused my laptop to fallback onto a secondary
  access point which didn't have full connectivity until the primary
  router finished rebooting, then I rebooted the primary router a second
  time), the wifi icon in my top bar stayed as the question-mark icon
  (i.e., the icon that shows when Network Manager doesn't think you have
  full connectivity) even after everything was back up and in fact my
  connectivity was fine.

  Turning wifi off and back on did not cause the question mark to go
  away. Restarting Network Manager did not cause the question mark to go
  away. Switching to a different wifi network and then back to the
  previous one didn't cause the question mark to go away. I had to
  reboot my laptop to get the question mark to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 21 18:35:48 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844897/+subscriptions


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

[Touch-packages] [Bug 1998415] Re: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install)

2022-12-02 Thread vasudevanM

Hi Nick,
I could install libsystemd-dev, after updating proper time zone.
Thanks for your support.
You can close this ticket.

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

Title:
  jammy libsystemd-dev has wrong dependency version to libsystemd0 (and
  fails to install)

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  jammy libsystemd-dev has wrong dependency version to libsystemd0 (and
  fails to install)

  libsystemd-dev wants libsystemd0 = 249.11-0ubuntu3 but
  249.11-0ubuntu3.6 is installed.

  installation currently fails:
  intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt-get install libsystemd-dev
  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:
   libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.6 is to be installed
  E: Unable to correct problems, you have held broken packages.

  FYI,

  intel@intel-Raptor-Lake-Client-Platform:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.1 LTS Customized image
  Release:22.04
  Codename:   jammy

  
  intel@intel-Raptor-Lake-Client-Platform:~$ dpkg -l libsystemd0
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version   Architecture Description
  
+++-=-=--=
  ii  libsystemd0:amd64 249.11-0ubuntu3.6 amd64systemd utility library
  intel@intel-Raptor-Lake-Client-Platform:~$

  intel@intel-Raptor-Lake-Client-Platform:~$ apt-cache madison libsystemd0
  libsystemd0 | 249.11-0ubuntu3 | http://in.archive.ubuntu.com/ubuntu 
jammy/main amd64 Packages

  intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt search libsystemd
  Sorting... Done
  Full Text Search... Done
  librust-libsystemd-dev/jammy,now 0.2.1-2build1 amd64 [installed]
    Pure-Rust client library to interact with systemd - Rust source code

  libsystemd-dev/jammy 249.11-0ubuntu3 amd64
    systemd utility library - development files

  libsystemd0/jammy 249.11-0ubuntu3 i386
    systemd utility library

  lua-systemd/jammy,now 0~git20160517-2 amd64 [installed]
    Systemd bindings for Lua

  python3-systemd/jammy,now 234-3ubuntu2 amd64 [installed,automatic]
    Python 3 bindings for systemd

  intel@intel-Raptor-Lake-Client-Platform:~$

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


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

[Touch-packages] [Bug 1997569] Re: Merge alsa-utils 1.2.7 from Debian unstable

Thanks Nathan, I've uploaded now (rebased on 1.2.8 which was uploaded to
Debian while that request was waiting for review)

** Changed in: alsa-utils (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Merge alsa-utils 1.2.7 from Debian unstable

Status in alsa-utils package in Ubuntu:
  Fix Committed

Bug description:
  Please merge alsa-utils 1.2.7 from Debian unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+subscriptions


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

[Touch-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format