-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El Thu, 19 Sep 2013 13:00:43 -0700
Toshio Kuratomi <a.badger(a)gmail.com> escribió:
On Sep 19, 2013 12:53 PM, "Michael Schwendt"
<mschwendt(a)gmail.com>
wrote:
>
> On Fri, 13 Sep 2013 13:51:28 +0200, Sandro Mani wrote:
>
> >
> > On 13.09.2013 11:48, Michael Schwendt wrote:
> > > On Fri, 13 Sep 2013 09:54:49 +0200, Florian Weimer wrote:
> > >
> > >> On 09/12/2013 10:40 PM, Sandro Mani wrote:
> > >>
> > >>> I just posted a review for avl (the Aerodynamic and
> > >>> flight-dynamic analysis of rigid aircrafts package) [1], and
> > >>> the reviewer noticed
that
> > >>> it conflicts with the retired avl package (the AVL tree
> > >>> manipulation library). How should one proceed in such
> > >>> situations? Does the old repository needs to be deleted
> > >>> before the new one is created?
> > >> Please do not reuse package names for unrelated software. It
> > >> is
quite
> > >> confusing and can interfere with all kinds of tracking/package
mapping
> > >> efforts.
> > > That could be documented.
> > >
> > > It would be wrong for an old retired (!) "avl" to block that
> > > component name forever. What if that project has been abandoned
> > > or renamed?
> > >
> > > I can't reach the old git.fruit.je/avl currently, but the
> > > README in
the
> > > old F14 package calls it "AVLTREE", "AVLTree" and
"AVL-Tree
> > > library", and the Fedora src.rpm uses the libavl source tarball
> > > from Debian.
> > >
> > > => It could (should?) have been named "libavl" or
"avltree".
> > I would definitely prefer this option. Should I file a rel-eng
> > ticket or what would the procedure be?
>
> A few years ago, there would have been a helpful answer from the
> admins who would/wouldn't process such requests. I don't know
> whether it's
possible
> to not only rename a git repo but also the stuff within pkgdb and
> koji.
Cc'd Dennis to see if this can happen in koji. If it can't I would
not be opposed to the new package unretiring the name and having the
pkgdb entry updated to the new package. The git history would have
both the old package's commits and the new one's.
-Toshio
We have no ability to rename a package in koji. im not opposed to
reusing the name. Just need some way to ensure its very clear the old
and new are different. Likely need to add a conflicts with the old one.
hopefully versions allow for upgrade okay, if not an epoch will need to
be added.
Dennis
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
iEYEARECAAYFAlI7eKoACgkQkSxm47BaWffdbgCcCzGPA2cUeZjlFMZWguJzICG5
FxYAnRHWbPFzMgK52Ggee7sSGHmGnCJk
=fkEd
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
iEYEARECAAYFAlI7edMACgkQkSxm47BaWfeCRwCbB34BhlPiGXhtj03JB1Uhyvtj
PxkAoIDDs+sDZfSgpT5cVSjiEXkTEkIj
=rLFW
-----END PGP SIGNATURE-----