sean finney <seanius@seanius.net> writes: > On Tue, Mar 18, 2003 at 12:46:13PM -0500, Shawn Lamson wrote: >> > On Mon, Mar 17, 2003 at 11:04:45AM -0500, sean finney wrote: >> > > has a discussion it looks like. anyone have an idea when a fix is >> > > going to go in? there's all kinds of packages i can't install from >> > > my fresh unstable install because of this. >> > >> > Look upthread for a URL pointing you to the packages likely to go into >> > sid to solve this. They work for me. >> >> They work for me too, however, won't updated packages overwrite >> (replace) the supplemental ones I installed from that site: >> http://people.debian.org/~pyro/libvorbis >> ? >> > if this fix is as trivial as it seems, why hasn't it been uploaded yet? > i don't mean to be getting cranky, but i can't install at least half a > dozen packages because of this... > > so... is this happening any time soon, or should i put in some testing > lines (the package is still in testing, right?) to fix this on my box? It won't be uploaded soon because, at the moment, the maintainer doesn't have access to a computer. Also, the fix unfortunately isn't so trivial. Previously, the libvorbis0 package contained 3 libraries: libvorbis, libvorbisfile, and libvorbisenc. Unfortunately, the soname of libvorbisfile and libvorbisenc (but not libvorbis) changed, thus requiring a rebuild of any application linking to those. In order to prevent this in the future, the package was split into 3 separate packages. The reason my debs mostly work right is because most apps only link against libvorbis (which still has the same soname), and not libvorbisfile nor libvorbisenc. However, for my proposal to be foolproof, someone needs to check the 50 or so remaining packages that depend on libvorbis0 to see which ones actually link against the old libvorbisenc and libvorbisfile libs. Then, a libvorbis0 meta-package can be uploaded that depends on libvorbis0a, and conflicts with any package that linked against the old libvorbisenc and libvorbisfile libs. The feasibility of this fix is dependent on how many packages are actually conflicting. Confusing, eh? -- I had no feelings about it. It was aloof and licked itself too much. Like my cat Mr. Trotsky.
Attachment:
pgp3A0xqiaNZm.pgp
Description: PGP signature