Re: lintian question - no-debian-changes
On Thu, Oct 29, 2020 at 10:42 PM Lajos Veres wrote: > Interestingly when I try to use lintian locally on a temp package, it does > not say anything about the issues listed on the website: > https://lintian.debian.org/sources/misspell-fixer/0.3-1.html It is possible that the website used a different version of lintian to you. > Can I test my local package somehow? Install the latest version of lintian from unstable and run lintian on the .changes file, which allows it to check the .deb as well as the .dsc. > $ lintian misspell-fixer_0.4-1.dsc --verbose -i --pedantic -o I tend to just call lintian from the source directory rather than passing it any files, this means that lintian will automatically find the right files to check. I also tend to enable the options in the config instead of the command-line: $ cat ~/.lintianrc info=yes display-info=yes display-experimental=yes pedantic=yes show-overrides=yes color=auto verbose=yes -- bye, pabs https://wiki.debian.org/PaulWise
Bug#973402: RFS: zope.schema/6.0.0-1 [QA] -- zope.interface extension for defining data schemas
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "zope.schema": * Package name: zope.schema Version : 6.0.0-1 Upstream Author : Zope Foundation and Contributors * URL : https://pypi.python.org/pypi/zope.schema * License : Zope-2.1 Section : zope It builds those binary packages: python3-zope.schema - zope.interface extension for defining data schemas To access further information about this package, please visit the following URL: https://mentors.debian.net/package/zope.schema/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/z/zope.schema/zope.schema_6.0.0-1.dsc Changes since the last upload: zope.schema (6.0.0-1) unstable; urgency=medium . * QA upload. * New upstream release. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse * d/control: - Update Standards-Version to 4.5.0 - Bump debhelper to 13 - Set minimum version on python3-zope.interface Regards, H??vard
Re: lintian question - no-debian-changes
On Thu, 29 Oct 2020, Paul Wise wrote: [...] > > If you decide to split the debian/ dir, you could also keep it on > github but not in the orig.tar.gz, either by filtering the tarball > created by github using the Files-Excluded feature of > uscan/mk-origtargz, or by storing the debian/ dir on a separate branch > or separate repo. Otherwise, Salsa is a popular place for storing > Debian package git repos: > > https://wiki.debian.org/Salsa Thank you! Following the principle of uscan's files-excluded, I have a found an export-ignore feature in .gitattributes which seems to be quite straight-forward solution. Interestingly when I try to use lintian locally on a temp package, it does not say anything about the issues listed on the website: https://lintian.debian.org/sources/misspell-fixer/0.3-1.html Can I test my local package somehow? I tried this way: $ lintian misspell-fixer_0.4-1.dsc --verbose -i --pedantic -o N: Using profile debian/main. N: Starting on group misspell-fixer/0.4-1 N: Finished processing group misspell-fixer/0.4-1 Thank you! Best regards, Lajos -- Lajos Veres vlajos+deb...@gmail.com
Bug#973371: RFS: pytest-dependency/0.5.1-1 [ITP] -- Manages dependencies of pytest test cases
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "pytest-dependency": * Package name: pytest-dependency Version : 0.5.1-1 Upstream Author : Rolf Krahl * URL : https://github.com/RKrahl/pytest-dependency * License : Apache-2.0 Section : python * Vcs: https://salsa.debian.org/python-team/packages/pytest-dependency It builds those binary packages: python-pytest-dependency-doc - Manages dependencies of pytest test cases (common documentation) python3-pytest-dependency - Manages dependencies of pytest test cases (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pytest-dependency/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pytest-dependency/pytest-dependency_0.5.1-1.dsc Changes for the initial release: pytest-dependency (0.5.1-1) unstable; urgency=medium . * Initial release (Closes: #972718) Regards, Bastian
Re: Verify the library transition
On Wed, Oct 28, 2020 at 03:23:41PM -0400, Tong Sun wrote: > > (it installed the -dev package from sid because you didn't add a version > > constraint to require the version from experimental) > > Ok, to add a version constraint, is it OK that I use the following to > replace all libgit2 dependents from above, to make sure they require > the version from experimental (v1.0.0)? You don't need to replace anything. Look at the wiki link again, it suggests passing --add-depends to sbuild. > > > PS, here are all libgit2 related packages installed in my system, and > > > their versions: > > > > > > libgit2-1.0:amd64_1.0.0+dfsg.1-1 > > > libgit2-28:amd64_0.28.5+dfsg.1-1 > > > libgit2-build-deps_1.0.0+dfsg.1-1 > > > libgit2-dev:amd64_0.28.5+dfsg.1-1 > > > libgit2-glib-1.0-0:amd64_0.28.0.1-2 > > > libgit2-glib-1.0-dev:amd64_0.28.0.1-2 > > Moverover, give my specific case, > > - single lib upgrade, and > - I've already installed the latest libgit2-1.0 into my sid > > would it matter any more if I build in my sid host? I know building > with sbuild + experimental build-dep is ideal, but I can't think of > any reason why I can't do build in my sid host now, if I am to update > the dependent version constraints to all that package I'm building. Yes, you can build on the host system if you installed the experimental packages there. -- WBR, wRAR signature.asc Description: PGP signature
Re: request for upload of new version of library following soname change
Tobias Frost left as an exercise for the reader: > IMHO, probably best would be to put it on mentors (as a bonus mentors > does already a few checks which are useful for the reviewer) > and open up an RFS bug for better visibility. > (e.g it's my policy only to sponsor from there, as I believe other people > will also learn/benefit from the process) I will go ahead and recut targeting experimental, and upload it to mentors. I had no idea that snd-nox had picked up the package as a dep--how delightful! I'll take a look at that package and ensure it's going to work with the new ABI, and if not, send over some patches. Thanks for the sound advice, everyone. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe. signature.asc Description: PGP signature
Bug#973340: RFS: guerillabackup/0.0.2-1 [ITP] -- resilient, distributed backup and archiving solution
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "guerillabackup": * Package name: guerillabackup Version : 0.0.2-1 Upstream Author : m...@halfdog.net * URL : https://github.com/halfdog/guerillabackup * License : LGPL-3.0+ * Vcs : https://salsa.debian.org/halfdog-guest/guerillabackup Section : misc It builds those binary packages: guerillabackup - resilient, distributed backup and archiving solution To access further information about this package, please visit the following URL: https://mentors.debian.net/package/guerillabackup/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/guerillabackup/guerillabackup_0.0.2-1.dsc Changes for the initial release: guerillabackup (0.0.2-1) unstable; urgency=medium . * Initial packaging of guerillabackup (Closes: #849714) Regards, hd PS: I tried to address the hints from previous RFS for older version (see https://bugs.debian.org/849754) or from private mails, e.g. Miroslav Kravec (documentation improvements needed), various comments on mentors list/irc (regarding salsa, gbp use, debian-file changes).
