Re: Packaging Python Pyvault Style (was Re: python 2.3 for RH7.3)

--===============2404315243686691638==
Content-Disposition: inline
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ahZICQ7iXVM/oLYH"


--ahZICQ7iXVM/oLYH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 22, 2004 at 10:44:13AM +0800, Jeff Pitman wrote:
> On Wednesday 22 December 2004 09:56, Axel Thimm wrote:
> > Does Paul Nasrat's
> > example demonstrate any further rpm regression?
>=20
> Nope.  The purpose of provider is to just play with a stock spec=20
> template and see how upgrades, obsoletes, provides all interact with=20
> each other.  It doesn't provide an example, per se.  But, I already=20
> have a set of specs here that provide a clear, boiled-down sampling:
>=20
> http://symbiont.mn.sabren.com/sandbox/rpm/
>=20
> See this for additional background and research on the issue:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D130352

Thanks, I was already on this bug's Cc. Seems to be forgotten
though. Packagers of all repos, unite against rpm's "features" and add
your comments to this bug ;)
--=20
Axel.Thimm at ATrpms.net

--ahZICQ7iXVM/oLYH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFByOZQQBVS1GOamfERAop0AJ9OOc6hFSPmHXBLafXSx4IxoWDoMgCdEfPE
q4z0TtZJDxCH+5j/d5LyXj8=
=eoca
-----END PGP SIGNATURE-----

--ahZICQ7iXVM/oLYH--


--===============2404315243686691638==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
repo-coord mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/repo-coord

--===============2404315243686691638==--