On Wed, 2 Dec 2015, Ross Gammon wrote:
According to the oss-compat package, it is better to use osspd. Osspd
provides oss-compat as a virtual package, and therefore if osspd is
installed and providing oss-compat, then oss-compat should not be
installed at the same time.
Blacklisting oss-compat is probably the right thing, but then osspd will
not be installed unless it is manually installed or something else
requires it specifically.
So if osspd is installed first then oss-compat will think it is already
installed?
Is it possible to add osspd specifically to the install?
Yes, not a problem at all. I can do that but can't remake the metas. That
is I can change the seeds.
I'm going to assume we don't need oss-compat for anything, and we can
just blacklist it. So, I'm doing that, and uploading a new meta today.
If the new meta was uploaded that day, it didn't work. Ahh, the one was
blacklisted, but it is a depend of something. I think we need to include
osspd. I think it needs to be included in the ffmpeg-common because that
is included before any audio package (even the desktop comes after) this
was done to make sure libavcodec-ffmpeg-extra56 gets pulled before
libavcodec-ffmpeg56 which conflicts. Maybe that meta should be called
pre-desktop rather than ffmpeg-common... but that might be a pain to get
figgured out. Putting it there may even make blacklisting oss-compat
unneeded.
--
Len Ovens
www.ovenwerks.net
--
ubuntu-studio-devel mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
