Hey Tong, On Fri, Dec 10, 2021 at 05:05:03PM -0500, Tong Sun wrote: > dbab moving to contrib is because of this Bug#1001009. I personally have no > idea, but as requested by Andrey. > > I guess it is about this line that is called from the postinst script > https://salsa.debian.org/debian/dbab/-/blob/master/bin/dbab-get-list#L21 > > Here is the recap of what he had said in this thread before: > > If the package cannot function without this or similar unpackaged file, it > > should be moved to contrib. If it can, the downloading should be done by > > the > > user/administrator.
OK, it looks like because of this line: https://salsa.debian.org/debian/dbab/-/blob/master/bin/dbab-get-list#L21 It tries to curl something. Now, two questions+suggestions. Agreeing with wrar on this point 1: 1. Is the data non-free? - If so, is it a hard requirement to download that data for package to function? Can sys admins not manually get this? -> If it is a hard-bound need, then it should be moved to contrib -> If not a hard-bound need, just mention downloading this in d/NEWS to inform the sys admin. This was it can continue to stay in free section (major benefit) * Is the data free software? - If so, is it a hard-bound/necessary need? -> Now, if so, you can do something like this: instead of pulling it in postinst, you could download it locally, and put it in, say a debian/resources directory, Simply install it to the needed locations with a d/install. This could serve as an example for you[1]. Only demerit is that you might need to update it when you do a new version, but it gives the benfit of keeping it in main rather than contrib. -> If not, same thingy, add a d/NEWS and ask sys admin. [1]: https://salsa.debian.org/go-team/packages/golang-mvdan-editorconfig/-/commit/edf2d06b904bc45296080bed4acf2631dc2e9ece So, in a nutshell if the data is non-free and it is needed for the package to function, we need to go ahead with contrib. Otherwise there are workarounds. Please let me know if that's the case, and it really needs to go to contrib? > I've asked some follow-up questions and his answer is enclosed *below*. > > > Also, I would suggest to add the reasoning in d/README.Debian instead of > the copyright > > for making it easier to review for ftp masters. > > > > Additionally, have you checked with piuparts that the upgrade from buster > indeed goes smooth? > > Hmm, no. This is the first time I heard of piuparts > > I did some search, but I got two 404 for the two most important thing that > I need to read: > > > 1. piuparts itself has a README > <https://piuparts.debian.org/doc/README.html> > *from* > > https://wiki.debian.org/piuparts?action=fullsearch&context=180&value=dbab&titlesearch=Titles We should probably report this to Holger. You can refer these links meanwhile https://wiki.debian.org/piuparts/HowTos https://salsa.debian.org/debian/piuparts/-/tree/develop/docs > 2. A package I'm interested in is in an untestable state. How can I find > out if it would pass the piuparts test? > > A) Run piuparts manually > > <https://piuparts.debian.org/doc/README.html#_how_to_use_piuparts_in_5_minutes>, > as described in that README. > > *from* https://wiki.debian.org/piuparts/FAQ Yeah. Or maybe try to manually upgrade in a buster chroot, and see what happens. > Is it a done-online thing or I need to download something and try to learn > how to use it? Sorry, I don't what that's supposed to mean. > > > Do you need me to upload to mentor first, you can totally take care of > > > it from salsa? > > > > I will manage from salsa. > > Thanks, I'll add the reasoning into d/README.Debian once things are settled. Sure. Regards, Nilesh
signature.asc
Description: PGP signature
