<p dir="ltr"><br>
On Sep 19, 2013 12:53 PM, "Michael Schwendt" <<a href="mailto:mschwendt@gmail.com">mschwendt@gmail.com</a>> wrote:<br>
><br>
> On Fri, 13 Sep 2013 13:51:28 +0200, Sandro Mani wrote:<br>
><br>
> ><br>
> > On 13.09.2013 11:48, Michael Schwendt wrote:<br>
> > > On Fri, 13 Sep 2013 09:54:49 +0200, Florian Weimer wrote:<br>
> > ><br>
> > >> On 09/12/2013 10:40 PM, Sandro Mani wrote:<br>
> > >><br>
> > >>> I just posted a review for avl (the Aerodynamic and flight-dynamic<br>
> > >>> analysis of rigid aircrafts package) [1], and the reviewer noticed that<br>
> > >>> it conflicts with the retired avl package (the AVL tree manipulation<br>
> > >>> library). How should one proceed in such situations? Does the old<br>
> > >>> repository needs to be deleted before the new one is created?<br>
> > >> Please do not reuse package names for unrelated software. It is quite<br>
> > >> confusing and can interfere with all kinds of tracking/package mapping<br>
> > >> efforts.<br>
> > > That could be documented.<br>
> > ><br>
> > > It would be wrong for an old retired (!) "avl" to block that component<br>
> > > name forever. What if that project has been abandoned or renamed?<br>
> > ><br>
> > > I can't reach the old <a href="http://git.fruit.je/avl">git.fruit.je/avl</a> currently, but the README in the<br>
> > > old F14 package calls it "AVLTREE", "AVLTree" and "AVL-Tree library",<br>
> > > and the Fedora src.rpm uses the libavl source tarball from Debian.<br>
> > ><br>
> > > => It could (should?) have been named "libavl" or "avltree".<br>
> > I would definitely prefer this option. Should I file a rel-eng ticket or<br>
> > what would the procedure be?<br>
><br>
> A few years ago, there would have been a helpful answer from the admins<br>
> who would/wouldn't process such requests. I don't know whether it's possible<br>
> to not only rename a git repo but also the stuff within pkgdb and koji.</p>
<p dir="ltr">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.</p>
<p dir="ltr">-Toshio</p>