Re: apt-get upgrade doesn't honor my rebuilded packages
Hi Koos Vriezen, *, Koos Vriezen wrote: This is probably a stupid question, but I did a search on this list with 'apt-get source dpkg -i upgrade' and there was no answer, so here it is. I've upgraded gcc from 3.3 to 3.4 and, since I always build KDE from CVS, I needed to recompile some c++ dependent packages like fam. So, I got fam with 'apt-get source libfam0c102 libfam-dev', builded the packages and installed it with 'dpkg -i libfam0c102_2.7.0-5_i386.deb libfam-dev_2.7.0-5_i386.deb'. I did the same for expat (turned out not c++, but anyways, so I build it but didn't install it). Now if I do 'apt-get -s upgrade', I get # apt-get -s upgrade Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De volgende pakketten zullen opgewaardeerd worden: libfam-dev libfam0c102 2 pakketten opgewaardeerd, 0 nieuwe paketten geïnstalleerd, 0 verwijderen en 0 niet opgewaardeerd. Inst libfam0c102 [2.7.0-5] (2.7.0-5 Debian:testing) Inst libfam-dev [2.7.0-5] (2.7.0-5 Debian:testing) Conf libfam0c102 (2.7.0-5 Debian:testing) Conf libfam-dev (2.7.0-5 Debian:testing) so it wants to replace it again what I just build. How can I prevent this? What's puzzling me most is that this seems so a common thing to do, jet I can't find this issue in the apt-howto document. I tried the local repository method, adding 'deb file:/usr/src/debian debs' in sources.list, doing a 'apt-get update'. But now I get: # apt-get -s upgrade Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De volgende pakketten zullen opgewaardeerd worden: libexpat1 libexpat1-dev 2 pakketten opgewaardeerd, 0 nieuwe paketten geïnstalleerd, 0 verwijderen en 0 niet opgewaardeerd. Inst libexpat1 [1.95.6-8] (1.95.6-8 Debian:testing) Inst libexpat1-dev [1.95.6-8] (1.95.6-8 Debian:testing) Conf libexpat1 (1.95.6-8 Debian:testing) Conf libexpat1-dev (1.95.6-8 Debian:testing) W/o the -s, it downloads the expat pkgs instead of using the local ones. So this didn't fix it. A local archive is a good idea. Check out what is going on with apt-cache policy pkg. There you can see the preferences used by apt. Maybee you can tune /etc/apt/preferences and pin your packages in the local archive with a pin priority over 1000. Therefor you need a Release file in your local archive. See man apt_preferences Kind regards Martin Theiß -- Martin Theiß [EMAIL PROTECTED] GPG-Fingerprint: EC80 53A2 F0A2 6E6C 74D2 CB6E 002A F6D3 E78B 7F45 The box said 'Requires Windows 95 or better', so I installed Linux - TKK 5 signature.asc Description: Digital signature
apt-get upgrade doesn't honor my rebuilded packages
Hi, This is probably a stupid question, but I did a search on this list with 'apt-get source dpkg -i upgrade' and there was no answer, so here it is. I've upgraded gcc from 3.3 to 3.4 and, since I always build KDE from CVS, I needed to recompile some c++ dependent packages like fam. So, I got fam with 'apt-get source libfam0c102 libfam-dev', builded the packages and installed it with 'dpkg -i libfam0c102_2.7.0-5_i386.deb libfam-dev_2.7.0-5_i386.deb'. I did the same for expat (turned out not c++, but anyways, so I build it but didn't install it). Now if I do 'apt-get -s upgrade', I get # apt-get -s upgrade Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De volgende pakketten zullen opgewaardeerd worden: libfam-dev libfam0c102 2 pakketten opgewaardeerd, 0 nieuwe paketten geïnstalleerd, 0 verwijderen en 0 niet opgewaardeerd. Inst libfam0c102 [2.7.0-5] (2.7.0-5 Debian:testing) Inst libfam-dev [2.7.0-5] (2.7.0-5 Debian:testing) Conf libfam0c102 (2.7.0-5 Debian:testing) Conf libfam-dev (2.7.0-5 Debian:testing) so it wants to replace it again what I just build. How can I prevent this? What's puzzling me most is that this seems so a common thing to do, jet I can't find this issue in the apt-howto document. I tried the local repository method, adding 'deb file:/usr/src/debian debs' in sources.list, doing a 'apt-get update'. But now I get: # apt-get -s upgrade Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De volgende pakketten zullen opgewaardeerd worden: libexpat1 libexpat1-dev 2 pakketten opgewaardeerd, 0 nieuwe paketten geïnstalleerd, 0 verwijderen en 0 niet opgewaardeerd. Inst libexpat1 [1.95.6-8] (1.95.6-8 Debian:testing) Inst libexpat1-dev [1.95.6-8] (1.95.6-8 Debian:testing) Conf libexpat1 (1.95.6-8 Debian:testing) Conf libexpat1-dev (1.95.6-8 Debian:testing) W/o the -s, it downloads the expat pkgs instead of using the local ones. So this didn't fix it. Regards, Koos Vriezen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get upgrade doesn't honor my rebuilded packages
On Sun, 15 Aug 2004 16:23:05 +0200, Koos Vriezen wrote: ... CVS, I needed to recompile some c++ dependent packages like fam. ... Now if I do 'apt-get -s upgrade', I get ... so it wants to replace it again what I just build. How can I prevent this? What's puzzling me most is that this seems so a common thing to do, jet I can't find this issue in the apt-howto document. FYI, I used to get this same problem while compiling sources in RH. I just circumvented it by increasing the version number a bit, e.g., Current version of emacs is: emacs21_21.3+1-5 I'll make it emacs21_21.3+1-5.1 which was done easily with a script. I can't tell you how to do it in debian yet, because I'm new to Debian, and haven't been able to compile emacs (without modification) yet. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get upgrade doesn't honor my rebuilded packages
Tong wrote: On Sun, 15 Aug 2004 16:23:05 +0200, Koos Vriezen wrote: ... CVS, I needed to recompile some c++ dependent packages like fam. ... Now if I do 'apt-get -s upgrade', I get ... so it wants to replace it again what I just build. How can I prevent this? What's puzzling me most is that this seems so a common thing to do, jet I can't find this issue in the apt-howto document. FYI, I used to get this same problem while compiling sources in RH. I just circumvented it by increasing the version number a bit, e.g., Current version of emacs is: emacs21_21.3+1-5 I'll make it emacs21_21.3+1-5.1 which was done easily with a script. I can't tell you how to do it in debian yet, because I'm new to Debian, and haven't been able to compile emacs (without modification) yet. The easiest way is to do 'dch -i comment'/'dch -v new-version comment' from the source directory[ie the directory that contains a debian subdirectory]. dch is from package devscripts. Alternatively, the package tools don't seem to mind if you just fudge the newest entry in debian/changelog's version up a little bit with any text editor. signature.asc Description: OpenPGP digital signature
