--- Begin Message ---
Thanks for replying ...
"Also sprach Adam D. Barratt:"
> # Merge duplicate filed bugs
> merge 361234 361237
> thanks
>
> On Friday, April 07, 2006 11:21 AM, Peter T. Breuer <ptb@lab.it.uc3m.es>
> wrote:
>
> > Package: apt
> > Version: 0.5.4
> > Severity: important
> >
> >
> > -- System Information
> > Debian Release: 2.2
> > Kernel Version: Linux betty.it.uc3m.es 2.6.15.4 #11 PREEMPT Fri Mar
> > 31 18:52:16 CEST 2006 i686 GNU/Linux
> >
> > Versions of the packages apt depends on:
> > hi libc6 2.1.3-25 GNU C Library: Shared libraries and
> > Timezone data
> > ii libstdc++2.10 2.95.4-22 The GNU stdc++ library
>
> Are those versions really correct? You're running apt from the now
I believe so.
> "oldstable" woody distribution, together with a libc that's even older than
> that, a fortnight old kernel and a Sources file for unstable?
Probably. This is originally potato. I thought apt was relatively
uptodate here, but I've since compiled and installed 0.6.43.3 and the
bug has indeed gone away, so perhaps I've neglected to upgrade apt in
some months - it was fine until yesterday. I didn't notice that you'd
moved apt on.
betty:/usr/oboe/ptb% dpkg -l apt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii apt 0.6.43.3 Advanced front-end for dpkg
I fired the report before noticing that you'd moved on to 0.6.x from
0.5.x, which would probably break some things. But the fact is that
nothing has broken until now, so it's probably as well to let you know
that you are passing the parse limits in older apts now.
> > E: Unable to parse package file
> >
> /var/lib/apt/lists/www.uk.debian.org_debian_dists_unstable_main_source_Sourc
> es
> > (1)
> > E: Tried to dequeue a fetching object
> > E: Tried to dequeue a fetching object
> > E: Tried to dequeue a fetching object
> > betty:/tmp%
> >
> >
> > The culprit is the huge line about 89700 lines into the file:
> >
> > Package: linux-2.6
> > Binary: linux-image-2.6-k7 .... (masses and masses) ....
> > Version: 2.6.16-5
>
> With all due respect I'm not really surprised it doesn't work. Your apt
> version is nearly five years old
I'm sure it's not that old! It's only 0.1 or thereabouts behind your
latest!
> and although I can't see anything obvious
> in the changelog it's entirely likely that whatever caused this issue was
> fixed long ago. Is there any chance you could possibly test it with a more
> up-to-date apt?
Sure - I compiled and installed the most uptodate and it's gone away.
betty:/tmp% apt-get -V
apt 0.6.43.3 for linux i386 compiled on Apr 7 2006 16:12:55
Usage: apt-get [options] command
...
May I say that debian rules files and procedures are getting almost
comically impossible to understand. The latest apt won't compile
straight off in ftparchive/ because it wants a dbm for c++ that seems to
be way ahead of my poor installation, and the libdb4.3 won't compile for
love nor money out of deb sources, because it wants a half dozen things
like java and the like that are just too much trouble. However ..
libdb4.3 compiles just fine from the .orig.tgz file and it's no trouble
to make the apt ftpwhatever executable link statically against a
libdb_cxx-4.3.a in /usr/local, thus getting a good compile and install
of the most recent apt package. And as far as I could tell, nothing
short of gcc 4.0 would compile apt, and the debian/rules didn't seem to
pass my CC and CXX and LD environment variables into the compilation
(went fine into the ./configure) or let /usr/local/bin into the path.
All in all, a real fight just to parse long lines! It would have been
simpler to add a post-update procedure that edited long lines down a
bit :(.
But it's done now. Are you sure you are going the right way with these
increasingly complicated make procedures? That libdb4.3 compiles just
hunky-dory out of the original package but won't sit still and be
bathed out of the deb source no matter how hard I hit it seems to
me to say you're going beyond the sane in some wise.
Peter
--- End Message ---