From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems with glsa-check
Date: Sun, 05 Dec 2004 23:30:00 -0500 [thread overview]
Message-ID: <41B3E048.1080406@gentoo.org> (raw)
In-Reply-To: <e1c2899a041205132419daae40@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Larsson wrote:
| I run 'glsa-check -l' and get a nice list of security advisories. So I
| try 'glsa-check -f new' and get:
| fixing 200411-13
| auxdb exception:
| [/usr/portage/::app-portage/gentoolkit-0.2.0_pre8-r1]: u'No key
| provided. key: gentoolkit-0.2.0_pre8-r1'
| 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//app-portage/gentoolkit-0.2.0_pre8-r1'
| r
Stuff like this belongs on http://bugs.gentoo.org/.
Please search Bugzilla, and if you cannot find an already open bug that looks
like your problem, please open one.
Cheers
- --
An idea is not responsible for the people who believe in it.
Aaron Walker < ka0ttic@gentoo.org > http://dev.gentoo.org/~ka0ttic/
Gentoo/BSD | cron | shell-tools http://butsugenjitemple.org/~ka0ttic/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFBs+BIC3poscuANHARAmmnAJ4jhgwQogv9uceBvuZ/Fzlm9PzkiACfQLvW
+JLmir5GNDI/n6QMW9tIrRU=
=QmrH
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2004-12-06 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 21:24 [gentoo-user] Problems with glsa-check Martin Larsson
2004-12-06 4:30 ` Aaron Walker [this message]
2004-12-06 21:21 ` Martin Larsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41B3E048.1080406@gentoo.org \
--to=ka0ttic@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox