On Sat, Dec 11, 2021 at 12:39 AM Nilesh Patra wrote: > > *from* https://wiki.debian.org/piuparts/FAQ > > Yeah. Or maybe try to manually upgrade in a buster chroot, and see what > happens.
The dbab can upgrade from oldstable (Buster) just fine, but I had some problem removing the outdated conffile files, as we had discussed in the other thread. So, As I know that the people that will be upgrading from buster can be counted using a single hand, so I decided to put a note in d/README.Debian instead. See https://salsa.debian.org/debian/dbab/-/commit/a8fe8295cafa7506ad87b7f8a726325d45a3a335 > 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? Thank you Nilesh for such detailed explanation. Weighted on all the options, I decided it still needs to go to contrib and have put a note in d/README.Debian -- https://salsa.debian.org/debian/dbab/-/commit/fa771322e1342c532637e17baa863cca8ac80488 copied below: ------------------------------ Moving to contrib ================= dbab moving to contrib is because of the Bug#1001009, first spotted by wrar then consented by nilesh, as it needs to download external files in postinst, which is not fit for main. The data is free software, however it's a living and breathing one, thus using a local copy (in package) means that - it will almost always be outdated, and - it will complicate the simple program & solution, and - it will make the core content more than doubled in size (9828 + 130499) The problem is initially spotted in 1.5.7-1 and get fixed in 1.5.7-2. Only changing to contrib section is made in d/control file, nothing else is changed, and the program behaves exactly as before. ------------------------------ Now everything is updated on salsa for the final release. Please double check, and let me know if I need to do anything else. Thanks a lot for all your help!
