- Package:
- src:libpaper
- Source:
- libpaper
- Submitter:
- Reuben Thomas
- Date:
- 2023-04-07 14:09:07 UTC
- Severity:
- important
As per #1010647, I, the upstream maintainer of the a new version of libpaper, and a Debian Maintainer, offer to take on co-maintainership of libpaper in order to update it. I see no activity of any kind on the package for the past 6 months. I have provided a proposed debdiff as part of #1010647. The new version of libpaper is API-compatible with the current version, while improving the user interface for configuring paper sizes. In particular, it uses the locale paper size provided by glibc, meaning that most users will not need to configure a size; it allows users to add their own per-user custom paper sizes; and it provided a more user-friendly “paper” program to get information about the current configuration and paper sizes. It fixes many of the currently open bugs, and I am keen to fix all of them.
Hi Reuben, I would like to sponsor sour work. Are you still interested to update libpaper in Debian? But please have an extra git Branch for the package. I can also create https://salsa.debian.org/debian/libpaper so that collaboration is easier for Debian folks. Thanks, Bastian
That's great! I am still interested to update libpaper in Debian. from upstream.
https://salsa.debian.org/debian/libpaper created and salsa user rrt invited.
Thanks, I have the invitation. I'll look into this as soon as I can. I presume initially I would just import the upstream git repo, which includes the packaging? It does not however include the Debian history, and I am not sure where Giuseppe Sacco keeps his history of the package, as mine starts with an import of the 1.1.24+nmu2 sources, and goes from there (though I have integrated all the changes to the Debian package since 1.1.24+nmu2). And finally, I guess we should see if Giuseppe can help with locating the history (if you think it's important to have).
Am 18.10.22 um 13:51 schrieb Reuben Thomas: I can import it from the Debian archive. Do you intend to use gbp for packaging? If so, I would prefer one import commits each release on an upstream branch. Then we do not have a problem with the history.
I have not used gbp before, but it seems like a sensible option, so I'm happy to use it for libpaper. If you can import the history from the Debian archive that would be great.
I am closing the ITS for now as there has been a recent maintainer upload. I would have liked to import Reuben's version of libpaper very much but it failed. Reuben, if the maintainer becomes unresponsive again, you may try to file a new one; the package effort is still available in git and won't be lost.