On Wed, Aug 05, 2015 at 02:14:24PM +0200, Martin Pitt wrote: > Hello, > > Matthias Klose [2015-08-04 19:44 +0200]: > > Package: libvbp1 > > Version: 4.2.59-1 > > Severity: serious > > Tags: sid stretch > > > > the man page is part of both libvbp0 and libvbp1.
sigh, I knew something was going to bite me if I raced this out, but I had a small window between other urgent things, and figured I'd get it out of the gcc-5 blocker list. oh well. > It's not just that, it's much worse -- the library contains udev > rules, binaries, /etc/modprobe.d/blunt-axe.conf. None of this belongs > into a library, but into some vpb-something binary, presumably > vpb-utils? (Also: Please don't make the lib depend on that). Yeah, the API was solidly stable before this got uploaded to Debian, so having a separate -common or whatever package seemed like overkill since we were never planning to bump SONAME and need a transition that had them co-installable. vpb-utils isn't really the right place for it all (or it would already be in there), some of it is necessary for setting up the environment for the library to operate (so the lib package will need to depend on it), and some of it, like the udev rules, more properly belongs with the kernel module package, but that one *is* co-installable for different kernel versions which is why this became the common package for that. The stuff in vpb-utils are 'application level' utilities and test programs, so they really are optional to have installed. Arguably, I could just make this package conflict with libvpb0 ... it's not like any real user is actually going to need them coinstalled, either you'll update it, or you won't. There's a kind of natural limit to how many things can be controlling your phone lines at the same time. I know it's not "by the book" for a lib package (I knew that when I did it) - but I weighed that up against bloating the archive with a separate package for ~1kB of support files and the reality of being committed to never breaking the existing ABI. > While you are at fixing this, would you mind dropping the > /etc/modprobe.d/blunt-axe.conf conffile and adding an > /usr/lib/modules-load.d/ snippet instead? hmm, I didn't even know that directory existed. When was it first added and how widely is it supported? (I'd like to keep this all as easily portable as possible, since there are users on lots of different distro releases still). Debian actually dropped the netjet module from its kernel builds quite a long time ago due to its retardedness, so largely this is for people who build it on ubuntu and other distros that haven't - but I also keep it as insurance in case one day someone goes "hey let's add this back". I know moving things out of /etc is something of a current craze, but is it doing any real harm there? Aside from possibly having to move a conffile to another package if I don't just add the Conflicts, it does reasonably fit with my idea of why conffiles are actually Good if the local admin does want to override it for some reason. Does anyone have a good practical argument for why I shouldn't just make this conflict with libvpb0? (I know all the reasons why this is *normally* not a good idea for library packages, so no need to repeat those - but in this specific case, for this specific package, it might still be the Lesser Evil here). Cheers, Ron -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
