[Touch-packages] [Bug 2002819] Re: dh-python: Deps guarded by (python3 << 3.X) break python-3.(X-1) use

2023-09-02 Thread Stefano Rivera 
Sorry, didn't close this in the changelog, but this was fixed in
6.20230813

** Changed in: dh-python (Ubuntu)
   Status: New => Fix Released

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

Title:
  dh-python: Deps guarded by (python3 << 3.X) break python-3.(X-1) use

Status in dh-python package in Ubuntu:
  Fix Released
Status in dh-python package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1028603:

  Package: dh-python
  Version: 5.20221001
  Severity: normal
  X-Debbugs-Cc: scho...@ubuntu.com

  For instance, pylint has "tomli>=1.1.0;python_version<'3.11'" in its
  pyproject.toml, which is translated as "python3-tomli (>= 1.1.0) |
  python3 (>= 3.11)".

  This means that if we have python == 3.11 but still have python3.10 in
  the archive, any code that iterates over all supported archive risks
  failing simply due to the tomli module missing.

  This is currently happening in the distro-info autopkgtests for the
  python3-defaults migration from unstable to testing (and also in
  Ubuntu). I'll probably be adding tomli as a test dependency in Ubuntu as
  a stopgap, but I figured someone might think of a better long-term
  solution to the issue.

  -- System Information:
  Debian Release: bookworm/sid
APT prefers kinetic-updates
APT policy: (500, 'kinetic-updates'), (500, 'kinetic-security'), (500, 
'kinetic'), (400, 'kinetic-proposed'), (100, 'kinetic-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.19.0-29-generic (SMP w/24 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages dh-python depends on:
  ii  python33.10.6-1
  ii  python3-distutils  3.10.7-1

  dh-python recommends no packages.

  Versions of packages dh-python suggests:
  ii  dpkg-dev   1.21.9ubuntu1
  pn  flit   
  ii  libdpkg-perl   1.21.9ubuntu1
  pn  python3-build  
  pn  python3-installer  
  ii  python3-tomli  2.0.1-1

  -- no debconf information

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


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

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-06-10 Thread Stefano Rivera 
The scenario I can think of is that you want to install some Python
thing in a virtualenv, that depends on both recent setuptools, and some
library that Debian provides but isn't trivially installed in a
virtualenv. It's not a common scenario, but I can imagine it.

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Incomplete
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-06-04 Thread Stefano Rivera 
> I do think the test case given in the bug report seems contrived. A
number of packages are necessarily installed using apt to set up the
environment; but then setuptools is specifically pulled from pip instead
of from the Ubuntu archive? Why? Is there a test case that can be used
to demonstrate the problem without what seems an unnatural mix of apt
and pip?

I think a more common scenario where this would come up is:

$ virtualenv --system-site-packages foo
$ foo/bin/python -m pip install -U setuptools
$ foo/bin/python -c "import pkg_resources; pkg_resources.require('distro-info')"

It's pretty common to upgrade setuptools inside a virtualenv to the latest 
version. And possibly required to install newer packages in a virtualenv.
virtualenv downloads the latest setuptools by default, upstream. But we adjust 
it to prefer the bundled wheels in the archive.

We worked hard to ensure that our Python packages support a wide range
of setuptools versions by including _distutils_system_mod that has code
paths for all the versions we think are plausible to use (including the
latest version).

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Incomplete
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File

[Touch-packages] [Bug 2006925] Re: python architecture-dependant packages installed incorrectly

2023-05-10 Thread Stefano Rivera 
I assume you mean commit cde02a32cd1b51cf7d07828edca0be61458e0eee.

dh-python 20211016 means jammy or later.

Python 3.3 predates Ubuntu 14.04, so that doesn't seem to be too much of
an issue.

Python 2.7 was removed after 22.10, so this bug would only really
relevant to jammy. Does this cause any known issues in jammy?

** Summary changed:

- python architecture-dependant packages installed incorrectly
+ jammy: python2 architecture-dependant packages installed incorrectly

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

Title:
  jammy: python2 architecture-dependant packages installed incorrectly

Status in dh-python package in Ubuntu:
  New

Bug description:
  postinst script in python2 packages generates __init__.py files for namespace 
packages.
  Since version 5.20211016 (commit 08ab39dfd34accb9220a087832b121279bbd9d98) 
arch is appended to package name to postinst script. However pycompile can't 
find namespace file with such package name -> namespace packages cannot be used 
in python2 (and python << 3.3).

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


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

[Touch-packages] [Bug 2012551] Re: Please build python >= 3.10 with --with-ssl-default-suites=openssl

2023-03-23 Thread Stefano Rivera 
** Package changed: python3-defaults (Ubuntu) => python3.10 (Ubuntu)

** Also affects: python3.10 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: python3.10 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: python3.10 (Ubuntu)
   Status: New => Invalid

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

Title:
  Please build python >= 3.10 with --with-ssl-default-suites=openssl

Status in python3.10 package in Ubuntu:
  Invalid
Status in python3.10 source package in Jammy:
  New
Status in python3.10 source package in Kinetic:
  New

Bug description:
  Hello,

  Starting in python3.10, python comes with it's own cipher list and TLS
  version requirements.  As a result, changing the security leve in
  openssl.cnf is not effective for python apps.

  This was addressed for Debian in https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1026802 - --with-ssl-default-suites=openssl was
  added in 3.11.2-2.  It'd be nice to have the same change in Ubuntu -
  and to backport it for python 3.10 in 22.04LTS.

  Thanks,
  Ross

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/2012551/+subscriptions


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

[Touch-packages] [Bug 2003644] Re: Cannot install python3-venv (broken dependence)

2023-01-25 Thread Stefano Rivera 
Sounds like a mirror issue.

** Changed in: python3-defaults (Ubuntu)
   Status: New => Invalid

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

Title:
  Cannot install python3-venv (broken dependence)

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  When running `sudo apt-get install python3-venv`

  I get an error

  The following packages have unmet dependencies:
   python3.10-venv : Depends: python3.10 (= 3.10.6-1~22.04) but 
3.10.6-1~22.04.2 is to be installed
  E: Unable to correct problems, you have held broken packages.

  The output of `apt policy python3.10` is below. My OS is Ubuntu
  22.04.1 LTS.

  python3.10:
Installed: 3.10.6-1~22.04.2
Candidate: 3.10.6-1~22.04.2
Version table:
   *** 3.10.6-1~22.04.2 100
  100 /var/lib/dpkg/status
   3.10.6-1~22.04 500
  500 http://ubuntu.mirror.su.se/ubuntu jammy-updates/main amd64 
Packages
   3.10.4-3ubuntu0.1 500
  500 http://ubuntu.mirror.su.se/ubuntu jammy-security/main amd64 
Packages
   3.10.4-3 500
  500 http://ubuntu.mirror.su.se/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: python3-venv (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 13:13:33 2023
  InstallationDate: Installed on 2022-11-26 (56 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2003644/+subscriptions


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

[Touch-packages] [Bug 1990562] Re: attempting to diff static library files raises UnicodeDecodeError

2022-09-24 Thread Stefano Rivera 
This bug was fixed in the package dh-python - 5.20220923

---
dh-python (5.20220923) unstable; urgency=medium

  [ Stefano Rivera ]
  * Run Python test suite with nose2. (closes: 1018338)
  * Don't attempt to diff static libs (.a), thanks Nick Rosbrook.
(closes: 1020528)

  [ Debian Janitor ]
  * Bump debhelper from old 12 to 13.
+ Drop check for DEB_BUILD_OPTIONS containing "nocheck", since debhelper now
  does this.
  * Remove constraints unnecessary since buster (oldstable):
+ dh-python: Drop versioned constraint on python3 in Replaces.

  [ Stuart Prescott ]
  * pyproject plugin: Make the package's entry points available in the PATH
when running the package's test suite, so that tests using the entry
points can be run.

 -- Stefano Rivera   Fri, 23 Sep 2022 09:47:57
+0200

** Changed in: dh-python (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  attempting to diff static library files raises UnicodeDecodeError

Status in dh-python package in Ubuntu:
  Fix Released
Status in numpy package in Ubuntu:
  New
Status in dh-python package in Debian:
  Fix Released

Bug description:
  In verbose mode, if files differ in share_files(), dhpython will try
  to show a diff of the files. When these files are static libraries,
  this raises a UnicodeDecodeError. For example, from a recent numpy
  build on arm64[1]:

  W: dh_python3 fs:146: Paths differ: 
debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a
 and 
debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a
  Traceback (most recent call last):
File "/usr/bin/dh_python3", line 284, in 
  main()
File "/usr/bin/dh_python3", line 210, in main
  fix_locations(package, interpreter, SUPPORTED, options)
File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations
  share_files(srcdir, dstdir, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files
  share_files(fpath1, fpath2, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files
  share_files(fpath1, fpath2, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files
  share_files(fpath1, fpath2, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files
  fromlines = fp1.readlines()
File "/usr/lib/python3.10/codecs.py", line 322, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: 
invalid start byte
  make[1]: *** [debian/rules:46: override_dh_python3] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:15: binary-arch] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2

  There is already logic to skip this diff for .so files, so the same
  should be done for .a files.

  [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic-
  arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz

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


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

[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

2022-09-17 Thread Stefano Rivera 
Seeing exactly the same symptoms on a machine upgraded to 22.04, with
wayland. Definitely seems suspend-related, but I haven't figured out
what the problem is, yet.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

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

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1

[Touch-packages] [Bug 1967620] Re: [FFe] LXC 5.0 LTS

2022-04-04 Thread Stefano Rivera 
LGTM, approved.

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

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

Title:
  [FFe] LXC 5.0 LTS

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  LXC 5.0 LTS will very soon be released.
  The upstream release has been held up due to an incomplete port to meson (and 
deprecation of autotools), it's otherwise been ready to go for a few months.

  As far as LXC releases go, it's a very light one. Comparing it to
  current 4.0.12, we have:

   - No liblxc API changes at all (no new symbols or changes to headers)
   - Addition of a few configuration keys:
 - lxc.cgroup.dir.monitor.pivot
 - lxc.cgroup.dir.monitor
 - lxc.cgroup.dir.container.inner
 - lxc.cgroup.dir.container
 - lxc.time.offset.boot
 - lxc.time.offset.monotonic
 - veth.n_rxqueues
 - veth.n_txqueues
 - veth.vlan.id
 - veth.vlan.tagged.id
   - Port to meson (replacing autotools)

  Diffstat:
  ```
  stgraber@dakara:~/data/code/lxc/lxc (lxc/master)$ git diff lxc-4.0.12.. . | 
diffstat
   .gitignore |1 
   config/init/systemd/Makefile.am|   10 +
   config/init/systemd/lxc-net.service.in |1 
   configure.ac   |5 
   doc/api-extensions.md  |9 +
   doc/ja/lxc.container.conf.sgml.in  |  129 -
   doc/lxc.container.conf.sgml.in |   98 
   lxc.spec.in|1 
   meson.build|4 
   src/lxc/api_extensions.h   |3 
   src/lxc/cgroups/cgfsng.c   |   93 +++
   src/lxc/cmd/lxc-checkconfig.in |6 -
   src/lxc/cmd/lxc_monitord.c |   59 +
   src/lxc/cmd/lxc_user_nic.c |2 
   src/lxc/conf.c |   11 +
   src/lxc/confile.c  |  664 
+---
   src/lxc/network.c  |   18 ++-
   src/lxc/network.h  |4 
   src/lxc/terminal.c |1 
   src/lxc/terminal.h |3 
   src/lxc/tools/lxc_autostart.c  |8 +
   src/lxc/utils.c|3 
   src/tests/aa.c |2 
   src/tests/config_jump_table.c  |2 
   src/tests/containertests.c |2 
   src/tests/get_item.c   |   90 ++-
   src/tests/getkeys.c|2 
   src/tests/locktests.c  |2 
   src/tests/lxc-test-utils.c |   16 +-
   src/tests/meson.build  |  534 
++
   src/tests/mount_injection.c|2 
   src/tests/parse_config_file.c  |   17 ++
   src/tests/reboot.c |2 
   src/tests/share_ns.c   |4 
   src/tests/snapshot.c   |2 
   35 files changed, 1676 insertions(+), 134 deletions(-)
  ```

  LXC 4.0.12 which we released on Feb 1st has all the bugfixes and other
  non-feature changes from LXC 5.0, making this quite a small and
  generally safe delta.

  The new features can be roughly categorized as:
   - Improve flexibility in cgroup configuration (make naming of /sys/fs/cgroup 
directories configurable)
   - Add support for the time namespace (clock offset)
   - Add support for configuring (basic sysctl) the number of veth queues
   - Add support for bridge VLAN filtering on veth devices

  
  LXC 5.0 will be an upstream LTS with a support duration matching that of 
Ubuntu 22.04 or until June 2027. Jammy currently ships LXC 4.0.12 which is only 
supported until June 2025 and will not see new bugfix releases after LXC 5.0 
comes out (only security).

  LXC is unseeded and in universe these days. The main goal of putting
  the new LTS in the release is to reduce the maintenance cost for the
  Ubuntu LTS and to satisfy some of Canonical's customers that are
  directly using those packages and would expect a consistent set of LTS
  releases.

  LXCFS 5.0 is already in jammy and LXD 5.0 has similarly been released,
  though that one ships exclusively as a snap.


  If we can get general agreement that getting this LXC release in
  Ubuntu 22.04 is fine, what I can do to fast track things a bit is
  upload a 5.0~git-hash version which still relies on autotools, get
  that do clear autopkgtest and CI and then follow that up with the
  final 5.0 with the meson port as soon as it's complete on our side
  (expecting about a week, just got two directories to port).

  As a reminder, this is all unseeded and in universe, so overall impact
  should be quite low.

[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

2022-03-06 Thread Stefano Rivera 
pip was fixed by fixing python3.10 and dh-python.

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

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in automake-1.16 package in Ubuntu:
  Fix Released
Status in dh-python package in Ubuntu:
  Fix Released
Status in python-pip package in Ubuntu:
  Fix Released
Status in python3.10 package in Ubuntu:
  Fix Released

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/automake-1.16/+bug/1960608/+subscriptions


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

[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

2022-03-06 Thread Stefano Rivera 
python3.10 was fixed in 3.10.2-4, which is in the release pocket.

** Changed in: python3.10 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: python-pip (Ubuntu)
   Status: New => Fix Released

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

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in automake-1.16 package in Ubuntu:
  Fix Released
Status in dh-python package in Ubuntu:
  Fix Released
Status in python-pip package in Ubuntu:
  Fix Released
Status in python3.10 package in Ubuntu:
  Fix Released

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/automake-1.16/+bug/1960608/+subscriptions


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

[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

2022-02-17 Thread Stefano Rivera 
Yes, it's required. My fix was resolving the python-pip FTBFS you
reported with that patch.

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

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in dh-python package in Ubuntu:
  Fix Released
Status in python-pip package in Ubuntu:
  New
Status in python3.10 package in Ubuntu:
  Confirmed

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

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


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

[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

2022-02-15 Thread Stefano Rivera 
OK, that seems to be caused by the default scheme changing from
posix_prefix to posix_local, dh-python was making silly assumptions,
there.

Your updated sysconfig patch looks good.

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

** Changed in: dh-python (Ubuntu)
   Status: New => In Progress

** Changed in: dh-python (Ubuntu)
 Assignee: (unassigned) => Stefano Rivera (stefanor)

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

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in dh-python package in Ubuntu:
  In Progress
Status in python-pip package in Ubuntu:
  New
Status in python3.10 package in Ubuntu:
  Confirmed

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

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


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

[Touch-packages] [Bug 1958266] Re: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2022-01-19 Thread Stefano Rivera 
Given the inconsistency, marking as invalid. Unless that was caused by
something in the archive, there's not much we can do here.

** Changed in: python3-defaults (Ubuntu)
   Status: New => Invalid

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

Title:
  package python3 3.9.7-4 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  Upgraded to jammy and this crash showed up.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3 3.9.7-4
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 18 23:57:23 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2021-10-05 (105 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  Python3Details: /usr/bin/python3.9, Python 3.9.9, python3-minimal, 3.9.7-4
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu3
   apt  2.3.14
  SourcePackage: python3-defaults
  Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1958266/+subscriptions


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

[Touch-packages] [Bug 1958266] Re: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2022-01-19 Thread Stefano Rivera 
What was the dpkg state of ibus-hangul?

It sounds like it wasn't installed, but the rtupdate file still existed
on disk.

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

Title:
  package python3 3.9.7-4 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Upgraded to jammy and this crash showed up.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3 3.9.7-4
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 18 23:57:23 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2021-10-05 (105 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  Python3Details: /usr/bin/python3.9, Python 3.9.9, python3-minimal, 3.9.7-4
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu3
   apt  2.3.14
  SourcePackage: python3-defaults
  Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1958266/+subscriptions


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

[Touch-packages] [Bug 1957199] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2022-01-13 Thread Stefano Rivera 
I'm afraid I can't walk you through resolving a broken upgrade in a bug
report, it's just not the best medium for the job. Nor can I see a
troubleshooting guide that I can recommend.

The process is that you need to complete the apt upgrade. Usually this
involves something like:

# dpkg --configure -a
# apt-get -f install
# apt-get upgrade
# apt-get dist-upgrade

And fix any issues a long the way, until you can get things to complete.
In the example above, removing or upgrading eric would probably allow
python 3.8 to configure.

If you're out of your depth, I'd recommend taking a backup and re-
installing.

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

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

Bug description:
  failure when trying to upgrade to Ubuntu 20

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan 12 11:28:01 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2015-08-26 (2330 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2022-01-12 (0 days ago)

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


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

[Touch-packages] [Bug 1957199] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2022-01-12 Thread Stefano Rivera 
eric should have been upgraded before python3.8 configured

The old eric was not compatible with python3.8.

Either way, the failed byte-compilation of that file shouldn't have
crashed the postinst.

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

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

Bug description:
  failure when trying to upgrade to Ubuntu 20

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan 12 11:28:01 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2015-08-26 (2330 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2022-01-12 (0 days ago)

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


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

[Touch-packages] [Bug 1957199] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2022-01-12 Thread Stefano Rivera 
** Also affects: eric (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

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

Bug description:
  failure when trying to upgrade to Ubuntu 20

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan 12 11:28:01 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2015-08-26 (2330 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2022-01-12 (0 days ago)

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


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

[Touch-packages] [Bug 1389283] Re: dh-python 1.20141026-1ubuntu1 incorrectly handles gi package names

2021-10-19 Thread Stefano Rivera 
I'd argue that the issue here is that "Requires: gi.repository.GLib" is
incorrect. There is no such package on PyPI, so the requirement will
never be satisfied.

Using pydist overrides, as you've done in pasaffe, seems reasonable.

** Changed in: dh-python (Ubuntu)
   Status: New => Invalid

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

Title:
  dh-python 1.20141026-1ubuntu1 incorrectly handles gi package names

Status in dh-python package in Ubuntu:
  Invalid

Bug description:
  1.20141026-1ubuntu1 introduced support for guessing dependencies from
  the egginfo file:

  * Add support for guessing dependencies from egg-info files (closes:
  756378)

  But this is mishandling gi.introspection dependencies. The pasaffe
  package, which compiles fine on Utopic, is now adding bogus
  dependencies to the vivid package:

  From the egg-info file:

  Requires: gi.repository.GLib
  Requires: gi.repository.GObject
  Requires: gi.repository.Gdk
  Requires: gi.repository.Gio
  Requires: gi.repository.Gtk
  Requires: gi.repository.Pango

  From the build log:

 dh_python3 -O--buildsystem=pybuild
  I: dh_python3 pydist:183: Cannot find installed package that provides 
gi.repository.glib. Using python3-gi.repository.glib as package name. Please 
add "gi.repository.glib correct_package_name" line to debian/py3dist-overrides 
to override it IF this is incorrect.
  I: dh_python3 pydist:183: Cannot find installed package that provides 
gi.repository.gobject. Using python3-gi.repository.gobject as package name. 
Please add "gi.repository.gobject correct_package_name" line to 
debian/py3dist-overrides to override it IF this is incorrect.
  I: dh_python3 pydist:183: Cannot find installed package that provides 
gi.repository.gdk. Using python3-gi.repository.gdk as package name. Please add 
"gi.repository.gdk correct_package_name" line to debian/py3dist-overrides to 
override it IF this is incorrect.
  I: dh_python3 pydist:183: Cannot find installed package that provides 
gi.repository.gio. Using python3-gi.repository.gio as package name. Please add 
"gi.repository.gio correct_package_name" line to debian/py3dist-overrides to 
override it IF this is incorrect.
  I: dh_python3 pydist:183: Cannot find installed package that provides 
gi.repository.gtk. Using python3-gi.repository.gtk as package name. Please add 
"gi.repository.gtk correct_package_name" line to debian/py3dist-overrides to 
override it IF this is incorrect.
  I: dh_python3 pydist:183: Cannot find installed package that provides 
gi.repository.pango. Using python3-gi.repository.pango as package name. Please 
add "gi.repository.pango correct_package_name" line to debian/py3dist-overrides 
to override it IF this is incorrect.

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


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

[Touch-packages] [Bug 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache

2021-10-19 Thread Stefano Rivera 
Fixed in dh-python in 3.20180927.

** Changed in: dh-python (Ubuntu)
   Status: New => Fix Released

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

Title:
  python packages should not ship colliding /usr/lib/python3/dist-
  packages/.pytest_cache

Status in alembic package in Ubuntu:
  Fix Released
Status in astroid package in Ubuntu:
  Invalid
Status in dh-python package in Ubuntu:
  Fix Released
Status in Debian:
  Fix Released
Status in alembic package in Debian:
  Fix Released

Bug description:
  Python packages should not ship /usr/lib/python3/dist-
  packages/.pytest_cache

  Recently, two packages python3-alembic and python3-astroid both
  shipped these files which collided on package install

  dh-python has been improved upstream to stream all hidden "dot"
  directories in Debian #907871

  This change should be imported and both alembic and astroid should be
  rebuilt (plus any other packages shipping this file)


  Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ...
  Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also 
in package python3-alembic 1.0.0-1ubuntu1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

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


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

[Touch-packages] [Bug 1902022] Re: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127

2021-10-19 Thread Stefano Rivera 
Hrm, not sure how that happened, the prerm script says:

if which py3clean >/dev/null 2>&1; then
py3clean -p dh-python 
else
dpkg -L dh-python | perl -ne 's,/([^/]*)\.py$,/__pycache__/\1.*, or 
next; unlink $_ or die $! foreach glob($_)'
find /usr/lib/python3/dist-packages/ -type d -name __pycache__ -empty 
-print0 | xargs --null --no-run-if-empty rmdir
fi


So, if py3clean isn't on PATH it should have used the second branch. Maybe 
/usr/bin/python3 was broken?

** Changed in: dh-python (Ubuntu)
   Status: New => Incomplete

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

Title:
  package dh-python 4.20191017ubuntu7 failed to install/upgrade:
  installed dh-python package pre-removal script subprocess returned
  error exit status 127

Status in dh-python package in Ubuntu:
  Incomplete

Bug description:
  This error occured after my attempts to correct the inability to
  import pygame into PyCharm-Environment (it works in Python2.7 and
  Python3.6 and 3.8). A package distutils.utils is requested, which I
  cannot find anywhere and should be superseeded by setuptools.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: dh-python 4.20191017ubuntu7
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct 28 20:55:00 2020
  DuplicateSignature:
   package:dh-python:4.20191017ubuntu7
   Removing dh-python (4.20191017ubuntu7) ...
   /var/lib/dpkg/info/dh-python.prerm: 7: py3clean: not found
   dpkg: error processing package dh-python (--remove):
installed dh-python package pre-removal script subprocess returned error 
exit status 127
  ErrorMessage: installed dh-python package pre-removal script subprocess 
returned error exit status 127
  InstallationDate: Installed on 2020-04-07 (205 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: dh-python
  Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: 
installed dh-python package pre-removal script subprocess returned error exit 
status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1863195] Re: py3compile should not emit python runtime warnings during dist-upgrade

2021-10-19 Thread Stefano Rivera 
> Or maybe set PYTHONWARNINGS=ignore in the environment during the
upgrade?

That sounds more like it. Wouldn't we want to see these in other
situations?

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

Title:
  py3compile should not emit python runtime warnings during dist-upgrade

Status in dh-python package in Ubuntu:
  Confirmed
Status in dh-python source package in Focal:
  Confirmed

Bug description:
  py3compile should compile without emitting python runtime warnings

  on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are
  emitted during apt upgrade, due to buffering=1 being deprecated.

  We will not fix all the packages, and these warnings are not helpful
  to the users, as they cannot and shouldn't need to do anything about
  them, as they come from packages that are maintained by the distro.

  Imho py3compile should execute python interpreter with -W ignore

  Or maybe set PYTHONWARNINGS=ignore in the environment during the
  upgrade?

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


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

[Touch-packages] [Bug 1648820] Re: package dh-python 1.20140128-1ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2021-10-19 Thread Stefano Rivera 
Sounds like python3.4 was uninstalled.

** Changed in: dh-python (Ubuntu)
   Status: New => Incomplete

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

Title:
  package dh-python 1.20140128-1ubuntu8.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in dh-python package in Ubuntu:
  Incomplete

Bug description:
  I have wrongly delete the dependence python2.7, and then the
  softwarecenter dose not work. Any of the software could not be
  installed. How should i re-install the software.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: dh-python 1.20140128-1ubuntu8.2
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Dec  9 21:37:56 2016
  Dependencies:
   
  DuplicateSignature: package:dh-python:1.20140128-1ubuntu8.2:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-25 (350 days ago)
  InstallationMedia: Ubuntu-Kylin 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150806)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.11
  SourcePackage: dh-python
  Title: package dh-python 1.20140128-1ubuntu8.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1758142] Re: Recursive follow of symlinks

2021-10-19 Thread Stefano Rivera 
Please can you describe how to reproduce this bug?

** Changed in: dh-python (Ubuntu)
   Status: New => Incomplete

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

Title:
  Recursive follow of symlinks

Status in dh-python package in Ubuntu:
  Incomplete

Bug description:
  This was not a problem with the previous dh-python, this is what we see with 
the version reported here:
  E: pybuild pybuild:330: test: plugin distutils failed with: 
[('/<>/snapcraft-2.40+18.04.2/tests/integration/snaps/old-part-src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src',
 
'/<>/snapcraft-2.40+18.04.2/.pybuild/cpython3_3.6/build/tests/integration/snaps/old-part-src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src',
 "[Errno 40] Too many levels of symbolic links: 
'/<>/snapcraft-2.40+18.04.2/tests/integration/snaps/old-part-src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src'")]
  dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

  Looks like there is new copy logic in
  https://launchpadlibrarian.net/361622412/dh-
  python_2.20170125_3.20180318.diff.gz (not mentioned on the changelog)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dh-python 3.20180318
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.2
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar 22 19:29:00 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: dh-python
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10

2021-10-19 Thread Stefano Rivera 
This is resolved in dh-python 5.20211016.

** Changed in: dh-python (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Python3 can't co-exist with Oracle's VirtualBox on 20.10

Status in dh-python package in Ubuntu:
  Fix Released
Status in what-is-python package in Ubuntu:
  Incomplete

Bug description:
  Sorry I couldn't file this bug against the correct packages. The form
  told me there are no such packages as python-is-python3 and dh-python
  in Ubuntu...

  Release: Groovy Gorilla (Ubuntu 20.10).

  Package versions: 
  python-is-python3 3.8.2-4
  dh-python 4.20200925

  The release of Ubuntu 20.10 is less than two weeks out, so I'd like to
  draw attention to a problem I've run into. It seems that 20.10
  defaults to python3 and wants to install python-is-python3, which
  pulls in the latest version of dh-python, which in turn can't co-exist
  with Oracle's Virtualbox-6.1 and wants to uninstall it.

  I don't mind having _both_ python2 (apparently a requirement of
  VirtualBox) and python3 installed. But as of right now I can have
  either python-is-python3, and not be able to do a complete upgrade
  since virtualbox-6.1 will be uninstalled, or python-is-python2, in
  which case I cripple 20.10's python3 install, since I won't get dh-
  python and python-six.

  Ia there something the python packagers do about this?

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


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

[Touch-packages] [Bug 1877626] Re: new upstream version

2021-10-19 Thread Stefano Rivera 
** Changed in: dh-python (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 dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1877626

Title:
  new upstream version

Status in dh-python package in Ubuntu:
  Fix Released

Bug description:
  Debian's dh-python is now in version 4.20200315, which fixed a number
  of bugs, as can be seen on its changelog[1]. Please sync with the
  latest version.

  [1] https://metadata.ftp-master.debian.org/changelogs//main/d/dh-
  python/dh-python_4.20200315_changelog

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


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

[Touch-packages] [Bug 1608030] Re: package dh-python 2.20151103ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

2021-10-19 Thread Stefano Rivera 
I can't tell what happened from this bug, but let's assume it was
resolved.

** Changed in: dh-python (Ubuntu)
   Status: New => Incomplete

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

Title:
  package dh-python 2.20151103ubuntu1.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dh-python package in Ubuntu:
  Incomplete

Bug description:
  after fresh install, I'm having problems to install updates. First I
  tried using Software Center, but updates couldn't be installed (no
  error was shown, but updates remained uninstall). After rebooting, I
  tried upgrading from console ($ sudo apt-get update; sudo apt-get
  upgrade), and then I got dh-python error.

  ...
  Removing obsolete conffile /etc/ld.so.conf.d/snappy.conf ...
  Setting up thermald (1.5-2ubuntu2) ...
  Setting up upower (0.99.4-2ubuntu0.3) ...
  Setting up xinit (1.3.4-3ubuntu0.1) ...
  Setting up libruby2.3:amd64 (2.3.1-2~16.04) ...
  Setting up ruby2.3 (2.3.1-2~16.04) ...
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Errors were encountered while processing:
   dh-python
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dh-python 2.20151103ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-lowlatency 4.4.13
  Uname: Linux 4.4.0-31-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 30 10:59:32 2016
  Dependencies:
   
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-07-24 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: dh-python
  Title: package dh-python 2.20151103ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1940405] Re: Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main)

2021-10-19 Thread Stefano Rivera 
** Changed in: dh-python (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main)

Status in dh-python package in Ubuntu:
  Fix Released

Bug description:
  Please sync dh-python 4.20201102+nmu1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Disable the nosetests autopkg test. Unmaintained.
* Disable the nosetests autopkg test. Unmaintained.
* Fix DocTest.
  -> Those have been fixed by the NMU

* Don't run test t301.

  -> I don't really understand the rationale for disabling this test.
  While the test case specifies a python version << 3.9 which wouldn't make
  it fit for current versions of Ubuntu, I believe what is being tested is the
  ability to specify the version bounds properly, which shouldn't be affected by
  the default version on the system.

  Changelog entries since current impish version 4.20201102ubuntu4:

  dh-python (4.20201102+nmu1) unstable; urgency=medium

* Non-maintainer upload
* Don't fail tests just because the default python gets hardcoded
  (Closes: #975536)

   -- Paul Gevers   Sat, 27 Feb 2021 19:51:37 +0100

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


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

[Touch-packages] [Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild

2021-02-01 Thread Stefano Rivera 
** Changed in: python-cffi (Ubuntu Groovy)
   Status: New => Incomplete

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

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

Title:
  [SRU] python-cffi and libffi in Groovy need a no-change rebuild

Status in libffi package in Ubuntu:
  Fix Released
Status in python-cffi package in Ubuntu:
  Fix Released
Status in libffi source package in Groovy:
  Incomplete
Status in python-cffi source package in Groovy:
  Incomplete
Status in libffi source package in Hirsute:
  Fix Released
Status in python-cffi source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43

   * Per the bug report, the following error is being thrown:
  SystemError: ffi_prep_closure(): bad user_data (it seems that the
  version of the libffi library seen at runtime is different from the
  'ffi.h' file seen at compile-time)

   * Based on this error, and based on the build time of python-cffi and
  libffi in relation to cffi, it appears as though python-cffi and
  libffi were built on an older version of cffi. This explains the
  error.

  [Test Case]

   * A certain number of users have reported that simply running studio-
  controls causes this error.

  [Where problems could occur]

   * Since this is a no-change rebuild being requested, the possibility
  of breakage is slim to none. We are introducing no new changes here,
  but rather, resolving a regression that happened as a result of a
  newer version of cffi being introduced without a rebuild of
  dependencies.

   * If any problems happen, it would be a result of applications using
  python-cffi and expecting this bug with built-in workarounds. I can't
  imagine such a case exists, so this is just a stretch.

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

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

[Touch-packages] [Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild

2021-01-29 Thread Stefano Rivera 
I'd suspect a local python-cffi more than a local jack. The jack module
doesn't involve any built bits.

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

Title:
  [SRU] python-cffi and libffi in Groovy need a no-change rebuild

Status in libffi package in Ubuntu:
  Fix Released
Status in python-cffi package in Ubuntu:
  Fix Released
Status in libffi source package in Groovy:
  New
Status in python-cffi source package in Groovy:
  New
Status in libffi source package in Hirsute:
  Fix Released
Status in python-cffi source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43

   * Per the bug report, the following error is being thrown:
  SystemError: ffi_prep_closure(): bad user_data (it seems that the
  version of the libffi library seen at runtime is different from the
  'ffi.h' file seen at compile-time)

   * Based on this error, and based on the build time of python-cffi and
  libffi in relation to cffi, it appears as though python-cffi and
  libffi were built on an older version of cffi. This explains the
  error.

  [Test Case]

   * A certain number of users have reported that simply running studio-
  controls causes this error.

  [Where problems could occur]

   * Since this is a no-change rebuild being requested, the possibility
  of breakage is slim to none. We are introducing no new changes here,
  but rather, resolving a regression that happened as a result of a
  newer version of cffi being introduced without a rebuild of
  dependencies.

   * If any problems happen, it would be a result of applications using
  python-cffi and expecting this bug with built-in workarounds. I can't
  imagine such a case exists, so this is just a stretch.

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

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

[Touch-packages] [Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild

2021-01-29 Thread Stefano Rivera 
Dug around on errors.ubuntu.com and found some examples:

https://errors.ubuntu.com/problem/2927dbb958eff4c58515acaca3ed657506e33ed8
This is a user who installed the jack library by hand into 
.local/lib/python3.8/site-packages
So, I think we can ignore that one.

https://errors.ubuntu.com/problem/6302e7add4138a8cd7c396ba878f3c5292628bea
This looks more helpful, but I can't reproduce it.

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

Title:
  [SRU] python-cffi and libffi in Groovy need a no-change rebuild

Status in libffi package in Ubuntu:
  Fix Released
Status in python-cffi package in Ubuntu:
  Fix Released
Status in libffi source package in Groovy:
  New
Status in python-cffi source package in Groovy:
  New
Status in libffi source package in Hirsute:
  Fix Released
Status in python-cffi source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43

   * Per the bug report, the following error is being thrown:
  SystemError: ffi_prep_closure(): bad user_data (it seems that the
  version of the libffi library seen at runtime is different from the
  'ffi.h' file seen at compile-time)

   * Based on this error, and based on the build time of python-cffi and
  libffi in relation to cffi, it appears as though python-cffi and
  libffi were built on an older version of cffi. This explains the
  error.

  [Test Case]

   * A certain number of users have reported that simply running studio-
  controls causes this error.

  [Where problems could occur]

   * Since this is a no-change rebuild being requested, the possibility
  of breakage is slim to none. We are introducing no new changes here,
  but rather, resolving a regression that happened as a result of a
  newer version of cffi being introduced without a rebuild of
  dependencies.

   * If any problems happen, it would be a result of applications using
  python-cffi and expecting this bug with built-in workarounds. I can't
  imagine such a case exists, so this is just a stretch.

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

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

[Touch-packages] [Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild

2021-01-27 Thread Stefano Rivera 
First: How do we reproduce the error? That'd be the best way to dig
deeper.

Second: libffi doesn't build against cffi.

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

Title:
  [SRU] python-cffi and libffi in Groovy need a no-change rebuild

Status in libffi package in Ubuntu:
  Fix Released
Status in python-cffi package in Ubuntu:
  Fix Released
Status in libffi source package in Groovy:
  New
Status in python-cffi source package in Groovy:
  New
Status in libffi source package in Hirsute:
  Fix Released
Status in python-cffi source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43

   * Per the bug report, the following error is being thrown:
  SystemError: ffi_prep_closure(): bad user_data (it seems that the
  version of the libffi library seen at runtime is different from the
  'ffi.h' file seen at compile-time)

   * Based on this error, and based on the build time of python-cffi and
  libffi in relation to cffi, it appears as though python-cffi and
  libffi were built on an older version of cffi. This explains the
  error.

  [Test Case]

   * A certain number of users have reported that simply running studio-
  controls causes this error.

  [Where problems could occur]

   * Since this is a no-change rebuild being requested, the possibility
  of breakage is slim to none. We are introducing no new changes here,
  but rather, resolving a regression that happened as a result of a
  newer version of cffi being introduced without a rebuild of
  dependencies.

   * If any problems happen, it would be a result of applications using
  python-cffi and expecting this bug with built-in workarounds. I can't
  imagine such a case exists, so this is just a stretch.

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

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