-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Ralf,
On Sat, 22 Jun 2013 14:03:01 +0200, Ralf Jung <p...@ralfj.de> wrote: > > I saw the conflicts/provides; that's what prompted me to update > > oss-compat and start preparing an upgrade path to osspd (as far as > > I'm concerned osspd is the correct upgrade path for oss-compat on > > platforms where it's available). > > > > With the blacklist, and the changes to oss-compat 3, you shouldn't > > need to conflit with oss-compat, > Unfortunately, this is not the case. I updated osspd accordingly > (/etc/modprobe.d/osspd.conf is installed) and upgraded to oss-compat > 3, but the oss modules are still loaded: On Sat, 22 Jun 2013 18:56:42 +0200, Ralf Jung <p...@ralfj.de> wrote: > Judging from the "modprobe.d" manpage, this is actually to be > expected: "blacklist" just prevents the module from being loaded > automatically for some hardware (the PCI-ID-aliases etc. are removed). > It does *not* prevent the module from being loaded when it is > explicitly referenced unless "--use-blacklist" is specified - and it > seems that flag is not set when processing the softdep entries added > by oss-compat. That'll teach me not to test stuff properly... This makes moving to osspd a bit more difficult than it should be, since a conflicting package will be removed but not purged: users with oss-compat installed will still have the oss-compat.conf file around when the install osspd, even though oss-compat is gone. Perhaps if I add a "deconfigure" handler to oss-compat the upgrades will work. On Sat, 22 Jun 2013 14:03:01 +0200, Ralf Jung <p...@ralfj.de> wrote: > > so osspd could just "provide" oss-compat and I could actually have > > oss-compat depend on osspd, which would ensure users actually got > > pushed to osspd. That would make a whole lot of Ubuntu users happy, > > and I dare say a few Debian ones as well... Strictly speaking osspd > > needs to declare "Conflicts: oss-compat (<= 2)" to avoid breakages > > related to oss-compat 2's incorrect modules configuration. > > > > So if you change osspd to Provides: oss-compat Conflits: oss-compat > > (<= 2) I'll happily change oss-compat to Depends: osspd > > [linux-any] > I am not sure if "Depends" is really such a good idea, maybe some > people really want to use OSS directly. Also, osspd uses PulseAudio > per default, and the ALSA backend is in bad shape - I am not sure if > everybody wanting OSS in Debian is ready to install PulseAudio ;-) . > If you leave it a Recommends, Ubuntu users will still get it usually > (I doubt most of them disable installation of recommends) while > leaving the possibility to opt-out. > In the end, of course that's your decision. Ah OK, I've been using the Alsa backend with pretty good results for now, I was hoping it would be good enough ;-). Incidentally I wondered about getting osspd to auto-configure itself for Alsa or PulseAudio depending on what the user uses, but that seems rather hard to do properly. Regarding Ubuntu I'd need to check how Recommends are handled on upgrades; aptitude and apt-get don't install them by default on upgrades unless I'm mistaken, just when installing initially. But Ubuntu has an upgrade tool so things might be different... And even for Debian I don't know whether the jessie kernel will still provide OSS modules! Regards, Stephen -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQIcBAEBCAAGBQJRywf5AAoJEHWXeKmja0lPZDQQAKqX2rwxBA2na+pENmy9UPcD wkdLT9IBlBiWc3FwdBXJqK9vsoKKjxriqFMaqJnjmX1PcttPz6z4ALfU9qvMdIX+ nhwCeJGQxxTah+qzXrE3fu8TfCYMfHGOrZMV7+Uqkk/5da+zpy9/r3i7Ss1v7+VK o/aL7zy/f3YZF8Z449hBnNsHSyM7MP7o/4ZaN9C5QVryfqTxZm09mkQ5vH9D6HMv wQALNEoU3BKd0h8cP/3Ynl9PSAXVYykDOfpWVyA3hPoonsK2NhQ/eSNc91qHPQs8 8YODxmOqGWN38IEyJX9t2cdJiJA5cURbSOswk6mLiwLGNx11y50+kE1Hm2ZZDiaB W0lVeAMOhj0QxrxqlrQIauc4CWTxfQQ+9COSPNbzLRfjuGmxIDobjulKnGJPWlrC s4MIVAN+qSSYIMtdGDufH7HiDoYOzSrRFLqBPaoY6OEv2Gx8LMfTmf7n9FVFuJG3 HvVgAQnimv7kgT2J58aEW7QEkoYsZsKVVJQMR7lhbzIM3F/eBWnGXR9Qt31y7m6q PD9UJcJ6C9yKIzoypIOXVWGyLExKbqfK4B2egA8A4av0JMNLqO03GQxkpMY3E2yX PotsKgKNOEtiGkKvR73uKF0RmAC/8HHyTccy4vxAEESs5p2BJAB5OntPlCNm8bak 3PX7E0CeLidR5+NRC0k2 =A1eH -----END PGP SIGNATURE-----
