Re: swup errors with nexxus repository

Christian Haugan Toldnes <[email protected]> Wed, 16 Jul 2003 16:31:14 +0200
Newsgroups gmane.linux.trustix.swup
Message-ID <[email protected]>
--KsGdsel6WgEHnImy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


(Jul 16 2003 10:32) Olaf Trygve Berglihn wrote:
>=20
> This looks like a bug in the creation of a transactions object.  As far
> as I recall, these objects should be dictionaries.  I suspect that a
> package without dependencies make swup interpret the rdfs in such a way
> that a None-object is created instead of an empty dictionary.  The
> interpreter then throws an exception with trying to access the values
> attribute which a None-object do not have.
>=20
> Have no time to fix, but a change in the resolver code to create an
> empty dict instead of None when no dependencies might solve the problem.
>=20
> If I recall incorrectly and the above is wrong, check with the rpm
> interface in swup and try to debug the use of rpm-transactions.

This might also be the case:=20

Since the package _has_ requirements but none resolved, due to the fact
that Morten did not use the additional official repository, the
requirement dictionary has one 'None' element.

like this:=20

"req
bag=20
/bag=20
/req"=20

instead of=20

"req /req"

which should be accounted for already.

In earlier versions of rdfgen, we had rdfgen exit on first error, but
this proved to be a bad scheme, since we now use rdfgen automaticly on a
rpm tree, with different contributors that may or may not build packages
on an up to date system. To make the rest of the rdfs usable, we decided
to not exit on first error, but generate all rdfs, even if some would
not be usable.

You might still be correct though. :)



c

--=20
Christian H. Toldnes
TSL Developer

Before you ask technical questions, please read this:
<URL: http://www.catb.org/~esr/faqs/smart-questions.html>

--KsGdsel6WgEHnImy
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/FWGyCjsfFF7l57ARAiEhAJ9Q2wN70CgJCiYzHnjcKsKPh13dXQCcDlcG
BE2ifcnqtn615bp+ZlqktDI=
=+mWl
-----END PGP SIGNATURE-----

--KsGdsel6WgEHnImy--