On 06-05-2023 19:26, Globe Trotter via devel wrote:
The reason stapler was published as pdf-stapler was that there was
then a package called stapler on Fedora, so it was suggested to me
that I use pdf-stapler, which is any case better because it
emphasizes that the software is for pdfs. However,
On Sat May 6, 2023 at 16:38 +0200, Sandro wrote:
> On 06-05-2023 16:29, Globe Trotter via devel wrote:
> > sudo fedrq whatrequires python-PyPDF2
> >
> > does not list pdf-stapler as a reverse dependency, however it does
> > include python3-staplelib which is part of the pdf-stapler
> > packaging.
Thanks, Sandro!
The reason stapler was published as pdf-stapler was that there was then a
package called stapler on Fedora, so it was suggested to me that I use
pdf-stapler, which is any case better because it emphasizes that the software
is for pdfs. However, the name stapler itself is quite
On 06-05-2023 18:48, Ben Beasley wrote:
I don’t think the PyPI parity rule needs to apply to the base package name,
since this is primarily an application package and thus falls under the general
naming guidelines[1]. You could make a case for renaming the python3-staplelib
subpackage to
On Sat, May 6, 2023, at 10:58 AM, Sandro wrote:
> Moreover, pdf-stapler package itself should probably be renamed to
> python-stapler to comply with the PyPI parity requirements [2] of the
> packaging guidelines. The package is published on PyPI as 'stapler'.
>
> [1]
On 06-05-2023 16:44, Globe Trotter via devel wrote:
Right, but not pdf-stapler. I would have thought that that might be
included too. Anyway, I am the maintainer for pdf-stapler so I can
make myself aware, but I hope I will not be missing others.
Well, looking at the spec file of pdf-stapler
Right, but not pdf-stapler. I would have thought that that might be included
too. Anyway, I am the maintainer for pdf-stapler so I can make myself aware,
but I hope I will not be missing others.
On Saturday, May 6, 2023 at 09:38:32 AM CDT, Sandro
wrote:
On 06-05-2023 16:29, Globe
On 06-05-2023 16:41, Sandro wrote:
On 06-05-2023 16:38, Sandro wrote:
sudo fedrq whatrequires python-PyPDF2
does not list pdf-stapler as a reverse dependency, however it does
include python3-staplelib which is part of the pdf-stapler
packaging.
It lists python3-staplelib for me:
fedrq wr
On 06-05-2023 16:38, Sandro wrote:
sudo fedrq whatrequires python-PyPDF2
does not list pdf-stapler as a reverse dependency, however it does
include python3-staplelib which is part of the pdf-stapler
packaging.
It lists python3-staplelib for me:
fedrq wr python3-PyPDF2
On 06-05-2023 16:29, Globe Trotter via devel wrote:
sudo fedrq whatrequires python-PyPDF2
does not list pdf-stapler as a reverse dependency, however it does
include python3-staplelib which is part of the pdf-stapler
packaging.
It lists python3-staplelib for me:
fedrq wr python3-PyPDF2
Strange that
sudo fedrq whatrequires python-PyPDF2
does not list pdf-stapler as a reverse dependency, however it does include
python3-staplelib which is part of the pdf-stapler packaging.
But how do I inform all the other maintainers about this change in a package
name? I guess my concern is
On 06-05-2023 15:36, Globe Trotter via devel wrote:
Is there an easy way to find out the reverse dependencies of a
package (PyPDF2)? Should I contact the maintainers of these reverse
dependencies to inform them? PyPDF2 has been renamed back to pypdf.
It is unclear to me why renames in either
On Saturday, May 6, 2023 at 01:13:18 AM CDT, Paweł Marciniak
wrote:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages
Thanks!
Is there an easy way to find out the reverse dependencies of a package
(PyPDF2)? Should I contact the maintainers
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
I am a co-maintainer (I think at least, I used to be co-) of PyPDF2 at least
for a while) or maintainer and I have noticed that the name has changed back to
pypdf (upstream). Is there an easy way to update the name of the package (in
the rpm) and importantly to make sure that the new pypdf rpm
15 matches
Mail list logo
