[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Intent to backport pyinstaller and pyinstaller-hooks-contrib



Hi Soren,

On 30.08.25 21:40, Soren Stoutner wrote:
I intend to backport pyinstaller and pyinstaller-hooks-contrib.  pyinstaller
is in trixie.  pyinstaller-hooks-contrib did not clear NEW quickly enough to
make it into trixie, but it is now in testing.  Because pyinstaller is a
package that moves quickly upstream, and because of how pyinstaller needs to
be updated to correctly interact with other packages, trixie users of
pyinstaller will usually want to be running a current version from backports.

https://tracker.debian.org/pkg/pyinstaller

https://tracker.debian.org/pkg/pyinstaller-hooks-contrib

As the current version of pyinstaller now depends on pyinstaller-hooks-
contrib, I intend to backport pyinstaller-hooks-contrib first and then, once
it is in trixie-backports, backport the current version of pyinstaller.

Thanks for sharing your intent to backport in advance. This helps me reviewing the NEW queue.

What's your assessment on the impact of this backport? Will Python packages built using the new pyinstaller remain compatible with Python packages built using the stable pyinstaller and vice versa?

Best regards,
Micha


Reply to: