apt-get insists updating gnupg with same version
After Werner Koch posted a small security patch for GnuPG 1.0.4 in gnupg-announce I decided it's time to compile gnupg from sources. Using Potato, I already had version 1.0.4 in use. Using apt-get source gnupg I fetched the most current sources, applied the patch and built gnupg_1.0.4-1_i386.deb, which I then installed. Everything seemed to work fine until I - a few days later - told apt-get to upgrade my packages. For some reason, it decided I needed the newest gnupg, gnupg_1.0.4-1_i386.deb and installed it. After I noticed what had happenes, I - again - installed the .deb I had compiled and now apt-get wants to upgrade it again. What I don't understand, is how come this happens even though package names are exactly the same. I assume that I could have used some other name for the package I compiled - like I do with --revision when compiling kernel -, is this correct? Suonpää...
Re: apt-get insists updating gnupg with same version
Samuli Suonpaa [EMAIL PROTECTED] wrote: After Werner Koch posted a small security patch for GnuPG 1.0.4 in gnupg-announce I decided it's time to compile gnupg from sources. Using Potato, I already had version 1.0.4 in use. Using apt-get source gnupg I fetched the most current sources, applied the patch and built gnupg_1.0.4-1_i386.deb, which I then installed. Everything seemed to work fine until I - a few days later - told apt-get to upgrade my packages. For some reason, it decided I needed the newest gnupg, gnupg_1.0.4-1_i386.deb and installed it. After I noticed what had happenes, I - again - installed the .deb I had compiled and now apt-get wants to upgrade it again. Yep, apt does magic to discourage accidents from happening (e.g. if you file a bug against a package with some of your own patches then it really should have a different version number, or else the maintainer doesn't know that you've made your own changes [1]). When you make changes yourself, edit debian/changelog and add a new entry at the top with a slightly higher version number, but not too much higher so that you still get real upgrades: in your case, usually something like 1.0.4-1.1 or 1.0.4-1.0.1 is a good idea. [1] At least, that's one plausible rationale that I can think of. -- Colin Watson [EMAIL PROTECTED]
apt-get not updating
Looking at the debian security page, I see the cron utility has been upgrade to fix a security problem. This was in august. When I run apt-get update it appears to run correctly. When I run apt-get dist-upgrade, nothing happens. Here is the /etc/apt/sources.list file: deb http://http.us.debian.org/debian stable main contrib non-free deb http://non-us.debian.org/debian-non-US stable non-US Should I have other paths? -paul - Double E Solutions Attn: Paul McHale 4912 Effingham Dayton, Ohio 45431 [EMAIL PROTECTED] Work: 937-253-7610 Mobile: 937-371-2828 Fax:413-215-3232 Home: 937-253-6260 (anytime) -
Re: apt-get not updating
On Thu, 28 Oct 1999, Paul McHale wrote: Looking at the debian security page, I see the cron utility has been upgrade to fix a security problem. This was in august. When I run apt-get update it appears to run correctly. When I run apt-get dist-upgrade, nothing happens. Here is the /etc/apt/sources.list file: deb http://http.us.debian.org/debian stable main contrib non-free deb http://non-us.debian.org/debian-non-US stable non-US Should I have other paths? deb http://http.us.debian.org/debian dists/proposed-updates/ -dave -- | oOOooO / --|oOobodoO/ [EMAIL PROTECTED] --| ooOoOo / | II / The wise man tells you where you have fallen | II / and where you may fall - Invaluable secrets.
RE: apt-get not updating
Thanks for the help. I was surprised it didn't upgrade cron as I expected, but it did upgrade several other packages :) Cron must somehow be upgraded or the patched cron must still be considered unstable... -paul -Original Message- From: Dave Baker [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 1999 8:13 AM To: Paul McHale Cc: Debian-User Subject: Re: apt-get not updating On Thu, 28 Oct 1999, Paul McHale wrote: Looking at the debian security page, I see the cron utility has been upgrade to fix a security problem. This was in august. When I run apt-get update it appears to run correctly. When I run apt-get dist-upgrade, nothing happens. Here is the /etc/apt/sources.list file: deb http://http.us.debian.org/debian stable main contrib non-free deb http://non-us.debian.org/debian-non-US stable non-US Should I have other paths? deb http://http.us.debian.org/debian dists/proposed-updates/ -dave -- | oOOooO / --|oOobodoO/ [EMAIL PROTECTED] --| ooOoOo / | II / The wise man tells you where you have fallen | II / and where you may fall - Invaluable secrets.
