Re: have I messed up package management?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/25/07 18:46, Steve Kleene wrote:
> References: <[🔎] 200702252114.QAA20605@syrano.acb.uc.edu> <[🔎] 20070225215152.GD11378@santiago.connexer.com> <[🔎] 45E2072D.80704@cox.net>
>
> On Sun Feb 25 16:15:46 2007, I wrote:
>
>> What I did was to put in alsa-base 1.0.14-rc1 from Debian experimental and
>> alsa-lib and alsa-driver 1.0.14rc2 from source. I made deb files of these
>> two but couldn't install them that way because of conflicts. I tried
>> checkinstall from unstable as well as dpkg -i.
>> ...
>> Am I likely to have a mess on my hands upgrading any of the packages
>> involved? Thanks.
>
> On Sun Feb 25 16:20:22 2007, Roberto C. Sanchez replied:
>
>> That depends. If you provide the exact error messages from dpkg when
>> you try to install with 'dpkg -i', then we can probably suggest how to
>> rebuild your .debs so that they will work with your setup.
>
> and on Sun Feb 25 16:27:56 2007, Ron Johnson said:
>
>> Getting your packages installed will/should solve that, though.
>>
>> What error messages were you getting?
>
> Here are the only errors I got with the deb files I made:
>
> dpkg -i alsa-lib_1.0.14rc2-1_i386.deb ->
> dpkg: error processing alsa-lib_1.0.14rc2-1_i386.deb (--install): trying to
> overwrite `/usr/bin/nm', which is also in package binutils
> dpkg -i alsa-driver_1.0.14rc2-1_i386.deb ->
> dpkg: error processing alsa-driver_1.0.14rc2-1_i386.deb (--install):
> trying to overwrite `/lib/modules/2.6.18-3-686/modules.isapnpmap', which
> is also in package linux-image-2.6.18-3-686
>
> However, I also listed all the files my deb files would install (with
> dpkg-deb --contents *.deb). For lib, there were 80 files that already had
> versions installed, most but not all from libasound2. For driver, there were
> 13 files that already had versions installed, all from
> linux-image-2.6.18-3-686. As I said, I ran "make install" anyway but now
> wonder what will happen if I try to upgrade libasound2, for example.
One way to find out... :\
Note that in any "install your own s/w" situation, there will always
be issues when you upgrade conflicting packages. You've just got to
reinstall.
For example, I manually installed the nvidia binary driver, so
whenever apt upgrades xorg, it installs it's own libglx.so into
/usr/lib/xorg/modules/extensions, so I have to manually recreate a
symlink from libglx.so.1.0.NNNN to libglx.so.
BTW, why wouldn't alsa-source 1.0.14~rc1-1 from experimental solve
your problem?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF4jrAS9HxQb37XmcRAgmqAJ9YYsd0YVaDMkOALmdxicRoztR41wCg2JNY
XYBx9b/2+xxjF6dADjb0emc=
=xmA8
-----END PGP SIGNATURE-----
Reply to: