On Thu, May 04, 2006 at 08:05:55PM +0200, Markus Neubauer wrote: > Justin Pryzby <[EMAIL PROTECTED]> schrieb: > >On Thu, May 04, 2006 at 09:01:37AM +0200, Markus Neubauer wrote: > >> > Justin Pryzby schrieb: > >>> > > On Wed, May 03, 2006 at 09:43:53AM +0200, Markus Neubauer wrote: > >>> > > > >>>> > >> Package: lynx > >>>> > >> Version: 2.8.5-2sarge1 > >>>> > >> Severity: minor > >>>> > >> > >>>> > >> -- System Information: > >>>> > >> Debian Release: 3.1 > >>>> > >> APT prefers testing > >>>> > >> APT policy: (500, 'testing') > >>>> > >> Architecture: amd64 (x86_64) > >>>> > >> Kernel: Linux 2.6.15-amd64-smp-vs > >>>> > >> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > >>>> > >> > >>>> > >> $ apt-get dist-upgrade > >>>> > >> Reading Package Lists... Done > >>>> > >> Building Dependency Tree... Done > >>>> > >> Calculating Upgrade... Done > >>>> > >> The following packages will be upgraded: > >>>> > >> lynx > >>>> > >> 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > >>>> > >> Need to get 0B/1882kB of archives. > >>>> > >> After unpacking 0B of additional disk space will be used. > >>>> > >> Do you want to continue? [Y/n] Y > >>>> > >> Preparing to replace lynx 2.8.5-2sarge1 (using > >>>> > >> .../lynx_2.8.5-2sarge1_amd64.deb) ... > >>>> > >> Setting up lynx (2.8.5-2sarge1) ... > >>>> > >> > >>>> > >> $ apt-get dist-upgrade > >>>> > >> Reading Package Lists... Done > >>>> > >> Building Dependency Tree... Done > >>>> > >> Calculating Upgrade... Done > >>>> > >> The following packages will be upgraded: > >>>> > >> lynx > >>>> > >> 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > >>>> > >> Need to get 0B/1882kB of archives. > >>>> > >> After unpacking 0B of additional disk space will be used. > >>>> > >> Do you want to continue? [Y/n] n > >>>> > >> Abort. > >>>> > >> > >>> > > This sounds like apt bug #363385. Is there an 0 epoch hiding > >>> > > somewhere? Where was your binary package downloaded from? > >>> > > > >> > You are right, that looks like apt bug #363385. > >> > > >> > Downloaded from deb http://amd64.debian.net/debian-amd64/ stable main > >> > the archive is lynx_2.8.5-2sarge1_amd64.deb. > >> > > >> > I do not kwow where is the epoche, it looks like the installation > >> > process sees a difference between "lynx_2.8.5-2sarge1_amd64" > >> > and "lynx_2.8.5-2sarge1". > >I can't see an epoch there, but this seems to be a common-ish problem > >with amd64 security support .. see #332675: "security.debian.org: > >libapr0 update for amd64 is installed but apt-get thinks it still > >needs updating". > > > >I don't know what to tell you :/ > > > >Why aren't you using the official amd64 debs now? > > Simply because I dont know - I do not know everything about Debian,
> What are the official amd64 debs? It was the hope and intent of the amd64 porting team to be included as an officially supported architecture for sarge; unfortunately, this didn't happen until recently, when the mirror split was implemented. To be sure, I don't understand why this was necessary, since the existing mirror script already implemented architecture inclusions/exclusions. Anyway, amd64 is (recently) an official arch (though I think security support has existed for some time now), and i386 and amd64 are now the only archs with new packages available on ftp.debian.org. (You are encouraged to use a mirror of that site, however). > I'll be at the Linustag tomorrow an dtry get more information on how > things work. Lucky :) Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
