Hello, I'm sorry for the chaos caused by my upload of src:python-nvchecker, I didn't notice src:nvchecker until it was too late.
I wanted to get python-nvchecker into trixie so that I can use it as
a dependency eventually but that project didn't materialize so I don't
really have much incentive to maintain the package.
If you are interested, please do take over src:python-nvchecker and
fix the situation as you see fit.
Let me know if I can help.
I've used nvchecker as a library, thus the package naming, but it's
primarily a CLI tool, so src:nvchecker with nvchecker package makes
sense too, possibly with
Provides: python3-nvchecker
Similarly, if src:python-nvchecker with python3-nvchecker is chosen, I
think it should
Provides: nvchecker
So that
apt-get install nvchecker
nvchecker
works as expected by users.
There is also an option to have the python module in python3-nvchecker and
nvchecker minimal package only containing the executable nvchecker
script with dependency on python3-nvchecker.
I didn't find definitive answer on this.
Cheers,
Jakub Ružička
On 25-08-30 03:08, Tianyu Chen wrote:
> Dear Helmut and nvchecker maintainer,
>
> On Mon, 21 Apr 2025 09:29:59 +0200 Helmut Grohne wrote:
>
> > Package: python3-nvchecker
> > Version: 2.12-2
> > Severity: important
> > Control: affects -1 + nvchecker
> > X-Debbugs-C: [email protected], [email protected]
> >
> > Hi,
> >
> > I spent a deeper look at these two packages after reporting the
> > undeclared file conflicts earlier and observe more problems here.
> >
> > It seems to me that src:nvchecker originally packaged this and later
> > src:python-nvchecker duplicated it. In theory, we should have removed
> > the duplicate and rescued the existing package. Instead, both got
> > maintained concurrently. Eventually I reported the file conflict and
> > that resulted in python3-nvchecker to declare Breaks+Replaces+Provides
> > nvchecker. This effectively is a package takeover. Is it coordinated in
> > any way? Is it authorized by the present src:nvchecker maintainers?
> >
> > Now given that src:nvchecker has received its last maintainer upload in
> > 2021 and lacked behind upstream by several versions, we can certainly
> > say it wasn't in its best shape. From a wider perspective, handing over
> > maintenance to a more active maintainer can be beneficial. At this
> > point, it would most probably make sense to simply remove src:nvchecker
> > from unstable after figuring out what good aspects (e.g. an example
> > file) can be rescued into src:python-nvchecker.
> >
> > Last but not least, Provides is not a proper package transition. apt
> > will not move an existing installation of nvchecker over to
> > python3-nvchecker by itself. src:nvchecker should temporarily include a
> > real, transitional nvchecker binary package to finish the transition.
> > Introducing a new binary package requires a freeze exception, but this
> > seems like one of those cases where I expect it to be granted.
>
> As src:nvchecker is not in bullseye, bookworm, nor trixie, and
> src:python-nvchecker is in trixie, I intend to maintain binary package
> nvchecker in src:python-nvchecker, under Debian Python Team's umbrella.
>
> I plan to add a transitional nvchecker binary package in
> src:python-nvchecker, to allow a smooth transition.
>
> Currently, I've done the changes in:
>
> https://salsa.debian.org/python-team/packages/python-nvchecker
>
> As moving the nvchecker binary package to src:python-nvchecker will cause
> the removal of src:nvchecker, I consider delaying the upload a bit would be
> better to get your thoughts.
>
> I plan to upload this after 21 days. If you consider the changes
> inappropriate, let me know your thoughts, and I will hold the upload.
>
> Best regards,
>
> Tianyu Chen
signature.asc
Description: PGP signature
