Mailing List Archive

Problem with glsa-check after updating to new .51 portage
Any ideas?

server hackeron # glsa-check -f 200410-22
WARNING: This tool is completely new and not very tested, so it should not be
used on production systems. It's mainly a test tool for the new GLSA release
and distribution system, it's functionality will later be merged into emerge
and equery.
Please read http://www.gentoo.org/proj/en/portage/glsa-integration.xml
before using this tool AND before reporting a bug.

fixing 200410-22
auxdb exception: [/usr/portage::dev-db/mysql-3.23.56]: u'No key
provided. key: mysql-3.23.56'
Traceback (most recent call last):
File "/usr/bin/glsa-check", line 162, in ?
mergelist = myglsa.getMergeList()
File "/usr/lib/gentoolkit/pym/glsa.py", line 565, in getMergeList
self.packages[pkg]["unaff_atoms"])
File "/usr/lib/gentoolkit/pym/glsa.py", line 324, in getMinUpgrade
mylist = portage.db["/"]["porttree"].dbapi.match(u)
File "/usr/lib/portage/pym/portage.py", line 5359, in match
return self.xmatch("match-visible",mydep)
File "/usr/lib/portage/pym/portage.py", line 5346, in xmatch
myval=match_from_list(mydep,self.xmatch("list-visible",None,mydep=mydep,mykey=mykey))
File "/usr/lib/portage/pym/portage.py", line 5332, in xmatch
myval=self.gvisible(self.visible(self.cp_list(mykey)))
File "/usr/lib/portage/pym/portage.py", line 5430, in gvisible
myaux=db["/"]["porttree"].dbapi.aux_get(mycpv, ["KEYWORDS"])
File "/usr/lib/portage/pym/portage.py", line 5090, in aux_get
self.auxdb[mylocation][cat].del_key(pkg)
File "/usr/lib/portage/pym/portage_db_flat.py", line 98, in del_key
mylock = portage_locks.lockfile(self.fullpath+key, wantnewlockfile=1)
File "/usr/lib/portage/pym/portage_locks.py", line 83, in lockfile
raise ValueError, "Unknown type passed in '%s': '%s'" %
(type(mypath),mypath)
ValueError: Unknown type passed in '<type 'unicode'>':
'/var/cache/edb/dep//usr/portage/dev-db/mysql-3.23.56'

--
gentoo-dev@gentoo.org mailing list
Re: Problem with glsa-check after updating to new .51 portage [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Try searching http://bugs.gentoo.org/

If you can't find anything resembling your bug, please submit one.

Cheers
- --
"Microsoft technology" -- isn't that an oxymoron?

~ -- Gareth Barnard

Aaron Walker - Gentoo Developer [ Gentoo/BSD / cron / shell-tools ]
ka0ttic@gentoo.org http://dev.gentoo.org/~ka0ttic/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBfQ31C3poscuANHARAp5iAJwO0uDG5Fy3nGPpsNKaMse3HdIdfwCfeuGS
DIwRywGxH9r+K4cMq8OdwIw=
=+hjR
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list
Re: Problem with glsa-check after updating to new .51 portage [ In reply to ]
ok, reported bug: http://bugs.gentoo.org/show_bug.cgi?id=68836

On Mon, 25 Oct 2004 10:30:14 -0400, Aaron Walker <ka0ttic@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Try searching http://bugs.gentoo.org/
>
> If you can't find anything resembling your bug, please submit one.
>
> Cheers
> - --
> "Microsoft technology" -- isn't that an oxymoron?
>
> ~ -- Gareth Barnard
>
> Aaron Walker - Gentoo Developer [ Gentoo/BSD / cron / shell-tools ]
> ka0ttic@gentoo.org http://dev.gentoo.org/~ka0ttic/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBfQ31C3poscuANHARAp5iAJwO0uDG5Fy3nGPpsNKaMse3HdIdfwCfeuGS
> DIwRywGxH9r+K4cMq8OdwIw=
> =+hjR
> -----END PGP SIGNATURE-----
>
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
>

--
gentoo-dev@gentoo.org mailing list