[gentoo-user] What's broken with portage now?

[gentoo-user] What's broken with portage now?

[Mick]

As it tries to update its cache after an emerge --sync it comes up
with a load of errors like so:
======================
Literal data: 5903578 bytes
Matched data: 0 bytes
File list size: 3297486
Total bytes written: 36921
Total bytes read: 5388275

wrote 36921 bytes  read 5388275 bytes  37544.61 bytes/sec
total size is 126887824  speedup is 23.39

>>> Updating Portage cache:
Failed cache update: app-accessibility/at-poke-0.2.2 "Corruption
detected when reading key 'at-poke-0.2.2': dictionary update sequence
element #0 has length 1; 2 is required"

Failed cache update: app-accessibility/dasher-3.2.18 "Corruption
detected when reading key 'dasher-3.2.18': dictionary update sequence
element #0 has length 1; 2 is required"
======================
. . . and so on until the end of the packages.

I resynced twice, same error.  Anyone else had it?
--
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What's broken with portage now?

[Mark Knecht]

I run eix-sync instead. I just ran it with no problems here.

Hope this helps,
Mark

On 4/23/06, Mick <michaelkintzios@gmail.com> wrote:
> As it tries to update its cache after an emerge --sync it comes up
> with a load of errors like so:
> ======================
> Literal data: 5903578 bytes
> Matched data: 0 bytes
> File list size: 3297486
> Total bytes written: 36921
> Total bytes read: 5388275
>
> wrote 36921 bytes  read 5388275 bytes  37544.61 bytes/sec
> total size is 126887824  speedup is 23.39
>
> >>> Updating Portage cache:
> Failed cache update: app-accessibility/at-poke-0.2.2 "Corruption
> detected when reading key 'at-poke-0.2.2': dictionary update sequence
> element #0 has length 1; 2 is required"
>
> Failed cache update: app-accessibility/dasher-3.2.18 "Corruption
> detected when reading key 'dasher-3.2.18': dictionary update sequence
> element #0 has length 1; 2 is required"
> ======================
> . . . and so on until the end of the packages.
>
> I resynced twice, same error.  Anyone else had it?
> --
> Regards,
> Mick
>
> --
> gentoo-user@gentoo.org mailing list
>
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What's broken with portage now?

[Glenn Enright]

[-- Attachment #1: Type: text/plain, Size: 269 bytes --]

On Monday 24 April 2006 9:11 am, Mick wrote:
>
> If I were to delete something it has to be the lot.  Which directory
> am I supposed to rm?

Before you do that try emerge metadata or emerge sync


-- 
Chemistry professors never die, they just fail to react.

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] What's broken with portage now?

[Mick]

On 23/04/06, Mark Knecht <markknecht@gmail.com> wrote:
> I run eix-sync instead. I just ran it with no problems here.
>
> Hope this helps,
> Mark

Sorry, I should have said, I ran eix-sync -v first and after a little
while I also tried to run emerge --sync.  I got the same errors on
both occasions.

Just tried again for a third time now with the same result!

What do such errors indicate:
=========================
Failed cache update: gnome-extra/zenity-2.10.1 "Corruption detected
when reading key 'zenity-2.10.1': dictionary update sequence element
#0 has length 1; 2 is required"

Failed cache update: gnome-extra/zenity-2.14.0 "Corruption detected
when reading key 'zenity-2.14.0': dictionary update sequence element
#0 has length 1; 2 is required"
=========================

I've got my portage on an xfs partition on this laptop . . . could it
be related to this?
--
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What's broken with portage now?

[lordsauronthegreat]

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

On Sunday 23 April 2006 01:08 pm, Mick wrote:
> On 23/04/06, Mark Knecht <markknecht@gmail.com> wrote:
> > I run eix-sync instead. I just ran it with no problems here.
> >
> > Hope this helps,
> > Mark
>
> Sorry, I should have said, I ran eix-sync -v first and after a little
> while I also tried to run emerge --sync.  I got the same errors on
> both occasions.
>
> Just tried again for a third time now with the same result!
>
> What do such errors indicate:
> =========================
> Failed cache update: gnome-extra/zenity-2.10.1 "Corruption detected
> when reading key 'zenity-2.10.1': dictionary update sequence element
> #0 has length 1; 2 is required"
>
> Failed cache update: gnome-extra/zenity-2.14.0 "Corruption detected
> when reading key 'zenity-2.14.0': dictionary update sequence element
> #0 has length 1; 2 is required"
> =========================
>
> I've got my portage on an xfs partition on this laptop . . . could it
> be related to this?

To me that doesn't look like filesystem stuff.  I think something murdered 
your portage cache.  I'd try and axe the whole thing (if possible) and 
rebuild it all.  Could take a long time, but it could work.

Also, if those two packages aren't installed right now, it looks like all it's 
complaining about is the absence of one line.  You could possibly find a way 
to hand-write the missing data, and see if that shuts it up.

I'm no expert, but that's my first impression.

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] What's broken with portage now?

[Mick]

On 23/04/06, lordsauronthegreat@gmail.com <lordsauronthegreat@gmail.com> wrote:

> To me that doesn't look like filesystem stuff.  I think something murdered
> your portage cache.  I'd try and axe the whole thing (if possible) and
> rebuild it all.  Could take a long time, but it could work.
>
> Also, if those two packages aren't installed right now, it looks like all it's
> complaining about is the absence of one line.  You could possibly find a way
> to hand-write the missing data, and see if that shuts it up.

Unfortunately, its not just those two packages which I've quoted here
as an example . . . it is every single package!

If I were to delete something it has to be the lot.  Which directory
am I supposed to rm?

Is it /var/cache/edb/dep/usr/portage perhaps?
--
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What's broken with portage now?

[Maurice Johnson]

ok,

I have seen this befor. Try rebuilding the existing portage tree on
your system...

# emerge meta-data

Make note of ant errors.

ciao

On 4/23/06, Mick <michaelkintzios@gmail.com> wrote:
> On 23/04/06, lordsauronthegreat@gmail.com <lordsauronthegreat@gmail.com> wrote:
>
> > To me that doesn't look like filesystem stuff.  I think something murdered
> > your portage cache.  I'd try and axe the whole thing (if possible) and
> > rebuild it all.  Could take a long time, but it could work.
> >
> > Also, if those two packages aren't installed right now, it looks like all it's
> > complaining about is the absence of one line.  You could possibly find a way
> > to hand-write the missing data, and see if that shuts it up.
>
> Unfortunately, its not just those two packages which I've quoted here
> as an example . . . it is every single package!
>
> If I were to delete something it has to be the lot.  Which directory
> am I supposed to rm?
>
> Is it /var/cache/edb/dep/usr/portage perhaps?
> --
> Regards,
> Mick
>
> --
> gentoo-user@gentoo.org mailing list
>
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What's broken with portage now?

[Mick]

On 23/04/06, Glenn Enright <elinar@ihug.co.nz> wrote:
> On Monday 24 April 2006 9:11 am, Mick wrote:
> >
> > If I were to delete something it has to be the lot.  Which directory
> > am I supposed to rm?
>
> Before you do that try emerge metadata or emerge sync

Thanks guys.  Emerge metadata creates multiple errors (here's an extract):
=========================
Failed cache update: dev-libs/gmime-2.1.14-r1 "Corruption detected
when reading key 'gmime-2.1.14-r1': dictionary update sequence element
#0 has length 1; 2 is required"

Failed cache update: dev-libs/gmime-2.1.9-r3 "Corruption detected when
reading key 'gmime-2.1.9-r3': dictionary update sequence element #0
has length 1; 2 is required"
=========================

What now?  Shall I delete /var/cache/edb/dep/usr/portage, or some
other file/directory too?
--
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What's broken with portage now?

[lordsauronthegreat]

[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]

On Monday 24 April 2006 05:01 am, Mick wrote:
> On 23/04/06, Glenn Enright <elinar@ihug.co.nz> wrote:
> > On Monday 24 April 2006 9:11 am, Mick wrote:
> > > If I were to delete something it has to be the lot.  Which directory
> > > am I supposed to rm?
> >
> > Before you do that try emerge metadata or emerge sync
>
> Thanks guys.  Emerge metadata creates multiple errors (here's an extract):
> =========================
> Failed cache update: dev-libs/gmime-2.1.14-r1 "Corruption detected
> when reading key 'gmime-2.1.14-r1': dictionary update sequence element
> #0 has length 1; 2 is required"
>
> Failed cache update: dev-libs/gmime-2.1.9-r3 "Corruption detected when
> reading key 'gmime-2.1.9-r3': dictionary update sequence element #0
> has length 1; 2 is required"
> =========================
>
> What now?  Shall I delete /var/cache/edb/dep/usr/portage, or some
> other file/directory too?

Because I said I think it might (major emphasis on might) help is no reason to 
start deleting things.  DO NOT delete anything without knowing what you're 
doing.  I just said I thought it might force a rebuild-from-scratch of the 
cache, however, I have really no idea.  If I built the software, that's 
what'd happen, but I didn't so that's where it is.  I said it mainly in hopes 
that it might help someone more knowledgeable come to a real solution.

If you still want to delete it, just let me ask you one thing: is this a toy, 
or a critical machine?  Is this your linux box that works as a learning 
environment, or is this thing really part of a system that needs to be on?  
If it's just your playground, back everything important (of YOUR data, not OS 
settings and crap like that) to another computer and delete to your hearts 
content.  You will most likely learn something.  If you're like me, and 
really depend on the system, don't try such a step.

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]