Your message dated Tue, 06 May 2025 18:00:10 +0000
with message-id <[email protected]>
and subject line Bug#1103905: fixed in pyenv 2.5.5-1
has caused the Debian Bug report #1103905,
regarding pyenv: please build two binary packages, to split off the runtime
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1103905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103905
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pyenv
Version: 2.5.4-1
Severity: wishlist
X-Debbugs-Cc: [email protected]

Hello,
thanks for maintaining pyenv in Debian: it seems to work for me.

However, I see that Debian binary package 'pyenv' (the only binary
package built from Debian source package 'pyenv') has a long list of
(direct and indirect) dependencies, mainly compilers/toolchains
and library development packages, needed when running commands like

  $ pyenv install <something>

On the other hand, once you have installed whatever you need in
your $PYENV_ROOT (under your home directory), all those dependencies
are not used to run commands like "pyenv init" and "pyenv versions",
and to make the shims work properly and select the desired version
of Python (also depending on the current working directory, possibly
configured with "pyenv local").


So consider the following scenario: the '/home' partition is shared
among a management host and a number of work hosts (for instance,
this happens on many HPC clusters, where the compute nodes mount
/home through an appropriate network filesystem, such as NFS or
something similar, from the storage node).
Users may want to run "pyenv install" and "pyenv local" on the
management host, but then may want to use the shims to select
the desired Python version on the work hosts.

It would be great, if the sysadmin could install Debian binary
package 'pyenv' with all the dependencies on the management host,
but only install a minimal Debian binary package (without all
the dependencies) on the work hosts.

I tried to imagine a way to achieve this.
I think I found it.


Debian source package 'pyenv' could be improved in the following
manner. Instead of building a single Debian binary package, Debian
source package 'pyenv' could build two distinct Debian binary
packages:

 * 'pyenv-runtime' (almost without dependencies) only shipping
   the following files

     /usr/bin/pyenv (a symlink to ../share/pyenv/libexec/pyenv )
     /usr/share/pyenv/libexec/pyenv
     /usr/share/pyenv/libexec/pyenv-init
     /usr/share/pyenv/libexec/pyenv-commands
     /usr/share/pyenv/libexec/pyenv-rehash
     /usr/share/pyenv/libexec/pyenv-versions
     /usr/share/pyenv/libexec/pyenv-version-name
     /usr/share/pyenv/libexec/pyenv-version-file
     /usr/share/pyenv/libexec/pyenv-version-file-read
     /usr/share/pyenv/libexec/pyenv-hooks
     /usr/share/pyenv/libexec/pyenv-help
     /usr/share/pyenv/libexec/pyenv-exec
     /usr/share/pyenv/libexec/pyenv-shims
     /usr/share/pyenv/libexec/pyenv-which
     /usr/share/pyenv/libexec/pyenv-whence
     /usr/share/pyenv/libexec/pyenv-version-origin
     /usr/share/pyenv/libexec/pyenv-prefix
     /usr/share/pyenv/libexec/pyenv-latest

 * 'pyenv' shipping all the rest and depending on pyenv-runtime and
   on all the other dependencies

This way, the sysadmin could install 'pyenv' on the management
host and only 'pyenv-runtime' on the work hosts.

Please consider doing this split.
It would be very useful in the above-described scenario.

Thanks for your time and dedication!


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.21-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (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 pyenv depends on:
ii  build-essential             12.12
ii  curl                        8.13.0-1
ii  expat                       2.7.1-1
ii  libauthen-sasl-perl         2.1700-1
ii  libbz2-dev                  1.0.8-6
ii  libcgi-pm-perl              4.68-1
ii  liberror-perl               0.17030-1
ii  libffi-dev                  3.4.7-1
ii  libio-socket-ssl-perl       2.089-1
ii  liblwp-protocol-https-perl  6.14-1
ii  liblzma-dev                 5.8.1-1
ii  libmediawiki-api-perl       0.52-2
ii  libncurses-dev              6.5+20250216-2
ii  libreadline-dev             8.2-6
ii  libsqlite3-dev              3.46.1-3
ii  libssl-dev                  3.5.0-1
ii  libterm-readkey-perl        2.38-2+b4
ii  libwww-perl                 6.78-1
ii  libxml2-dev                 2.12.7+dfsg+really2.9.14-0.4
ii  libxmlsec1-dev              1.2.41-1+b1
ii  llvm                        1:19.0-63
ii  make                        4.4.1-2
ii  pcre2-utils                 10.45-1
ii  python3                     3.13.2-2
ii  tk-dev                      8.6.16
ii  wget                        1.25.0-2
ii  xz-utils                    5.8.1-1
ii  zlib1g-dev                  1:1.3.dfsg+really1.3.1-1+b1

pyenv recommends no packages.

Versions of packages pyenv suggests:
ii  git               1:2.47.2-0.1
pn  libsecret-1-dev   <none>
pn  python3-openssl   <none>
ii  python3-requests  2.32.3+dfsg-5
pn  python3-tk-dbg    <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: pyenv
Source-Version: 2.5.5-1
Done: Josenilson Ferreira da Silva <[email protected]>

We believe that the bug you reported is fixed in the latest version of
pyenv, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josenilson Ferreira da Silva <[email protected]> (supplier of updated 
pyenv package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 02 May 2025 21:05:39 -0300
Source: pyenv
Binary: pyenv pyenv-runtime
Architecture: source all
Version: 2.5.5-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Josenilson Ferreira da Silva <[email protected]>
Description:
 pyenv      - Simple Python version management
 pyenv-runtime - Simple Python version management (runtime components)
Closes: 1102884 1103905
Changes:
 pyenv (2.5.5-1) experimental; urgency=medium
 .
   * New upstream version 2.5.5
   * debian/control:
      - Added binary with simple components for runtime (Closes: #1103905)
      - Added Breaks/Replaces for pyenv-runtime
      - Updated list of required dependencies
   * debian/copyright:
      - Updated GPL2 license terms
   * debian/patches:
      - 004.fixed-line-break.patch: Removed pyenv.1 file
      - 006.change-shell-to-fix-test.patch: Fixed hunk issue
      - 007.fixed-command-manpage.patch: Fix command  bashrc (Closes: #1102884)
      - 008.added-pyenv-runtime-information.patch: Add information pyenv-runtime
   * debian/pyenv.install:
      - Specified pyenv binary package files
   * debian/pyenv.links:
      - Removed pyenv binary link
   * debian/pyenv.manpages:
      - Removed pyenv manpage
   * debian/pyenv-runtime.instal:
      - Added components to pyenv-runtime binary
   * debian/pyenv-runtime.links:
      - Created pyenv symbolic link
   * debian/pyenv-runtime.manpages:
      - Linked pyenv manpage to pyenv-runtime binary
   * debian/pyenv.sh:
      - Removed unnecessary wrapper
   * debian/rules:
      - Adjustments for correct construction of binaries
      - Fixed variable declaration
Checksums-Sha1:
 0b6000e92ab49547b84cb955ac80e6eba6658027 2118 pyenv_2.5.5-1.dsc
 34bd01d71cf2855c0431d63237851900678ef588 1339960 pyenv_2.5.5.orig.tar.gz
 e39ba5ac2a090e59dafb289987a86e8476fa155b 11068 pyenv_2.5.5-1.debian.tar.xz
 3d5f9d67e64f76bb48436b079578d639aa5581c8 40884 pyenv-runtime_2.5.5-1_all.deb
 39163f1efb7b5a16dc95b466ce6c6c7a6512146e 309440 pyenv_2.5.5-1_all.deb
 d37694c19095c33483eef1d3175fc6eabeec6b96 8840 pyenv_2.5.5-1_amd64.buildinfo
Checksums-Sha256:
 19f0d8faf288a1baa15544b18ec0a13c610e1471166f308c420dbdd2ce894c0d 2118 
pyenv_2.5.5-1.dsc
 f1992bb226b4b258ff1ce3168c0470f87a1affa5f796d820f5dfc3d20bd82008 1339960 
pyenv_2.5.5.orig.tar.gz
 1ef2723a341977c31ea2f460f3872740f154f49b7c11cdb61d78d3faed390079 11068 
pyenv_2.5.5-1.debian.tar.xz
 1ab567b78b365ade4acad5b2687ba80808a8d9570865dea05c29d3ae7d6322dd 40884 
pyenv-runtime_2.5.5-1_all.deb
 bd1e211463be8ed7f57167f41771c3ee8c7eae2964ae890b877dd4b7768566e8 309440 
pyenv_2.5.5-1_all.deb
 6f4e1b72d001416f83472f569ac3d93e242b9b75f57eaf0ddbc4eb895d2e6fdb 8840 
pyenv_2.5.5-1_amd64.buildinfo
Files:
 d37367d09ffe4b5ba3d6533d77339d64 2118 python optional pyenv_2.5.5-1.dsc
 57164da57f5db45e646edcf34e39203d 1339960 python optional 
pyenv_2.5.5.orig.tar.gz
 3477954b4bd704482a964c791c98c082 11068 python optional 
pyenv_2.5.5-1.debian.tar.xz
 6b0a46aa0a701e8442ad167d70094923 40884 python optional 
pyenv-runtime_2.5.5-1_all.deb
 28fc0c10466ad4da363334e52ef009b8 309440 python optional pyenv_2.5.5-1_all.deb
 e1cac7b63affd4693f1e43dbae9eaab6 8840 python optional 
pyenv_2.5.5-1_amd64.buildinfo


-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmgaAnwSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHJj8QAKQP6C+SoRqmPPZvHsaexYbAAT3lrvrv
8/uxl3JrNO6eXo5BR+5z1cElx6plvGX3cevoPxr8Bc41hBU1T9OreqkO3Quq9X7p
ksJswawfJ2A5luGaLlFituNKTkETqftuNy9GMHiEH14urEi8PdixHhjnfpUcTUKl
+ouAPuOnjX0GIToAmWqy1zBCNnHDkbK48UBger2Y9G+C2EW3i1Zx8XQtyxM6oWsc
G43nP2Ln8IfQktqU/5GrEKY2+7aJAFg4yQJF/YZH1CX5z1NZL5btEbOpGaJkriqZ
ytrmR/5vL+V5oEh7HttiEH9ddT3vP3MtaCKK668JVR2/poWgzHXFhV6ze4E3+m5p
Kz+focFQ0lvt30mWcbQxlwpZuhZvYSQTTd6x1YkQ0cILKhT24NB5wP6IUsC1w+ea
ZGfWgroRrjGqdsySq9Pb0c98z++lR9l6gZmQeEeHZu17YQpqdJOc8JAR9DGuMn+5
oHa5fZEw6D28kby+yRuObhDRiS63a8RAxienLPEGFep2WcH0uyq0vc2wYGS7ue0i
AZsDegycLTOJUIoAFPXsrfe5oXkZoAg1smvvbrbfaax0ZoktryxLcN8SQCS3PfqS
wUP6mWs6qtFIWLTLxm0e552HN5rPLk2dhaTdVRhuBrLnlqBqY+ch6VqzqGgK8ZbI
ZHbHhC2KG2PN
=l1Y7
-----END PGP SIGNATURE-----

Attachment: pgpc4HdVXIddI.pgp
Description: PGP signature


--- End Message ---

Reply via email to