Re: Package name conflict with retired package
On Sep 19, 2013 12:53 PM, Michael Schwendt mschwe...@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 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
On Thu, Sep 19, 2013 at 01:00:43PM -0700, Toshio Kuratomi wrote: 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. This did already happen, but there is no idea what to do with the EPEL branches. The old package does have some, where the package is orphaned, but the new package maintainer does not intend to maintain the new package in EPEL. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
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 I hope I did not move to fast, but after discussing on irc with rdieter, I went forward and took over the repo of the retired package, updating the description. See [1] for the irc conversation. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1007541#c4 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
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. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El Thu, 19 Sep 2013 13:00:43 -0700 Toshio Kuratomi a.bad...@gmail.com escribió: On Sep 19, 2013 12:53 PM, Michael Schwendt mschwe...@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- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
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 The last build of the old was for f17. The new avl is only available for f19 and newer. Should I add a Conflicts: avl 3.32-1 regardless? The version numbers allow for upgrades (i.e. old avl stopped at 0.3.5, new avl starts at 3.32). One question which remains though is what to do with the EPEL branhces. Just keep them retired? Thanks, Sandro -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
On Thu, Sep 19, 2013 at 3:35 PM, Sandro Mani manisan...@gmail.com wrote: 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 The last build of the old was for f17. The new avl is only available for f19 and newer. Should I add a Conflicts: avl 3.32-1 regardless? The version numbers allow for upgrades (i.e. old avl stopped at 0.3.5, new avl starts at 3.32). I think so and a comment in the spec file about why it's there. One question which remains though is what to do with the EPEL branhces. Just keep them retired? yeah, I'd leave them orphaned/retired in EPEL if there's no intention to maintain the new package there at the moment. It would be nice to let people know that the old EPEL packages are unmaintained and that the bugzilla/pkgdb description/etc are no longer for that package but I can't figure out a way to do that other than sending a message to the epel mailing list and hope anyone who cares reads that. -Toshio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
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. -- Florian Weimer / Red Hat Product Security Team -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
Also, I guess it would be nice to have a package name that gives some indication of what it is about (unless ofcourse the name itself is well and widely known ) On Fri, Sep 13, 2013 at 1:24 PM, Florian Weimer fwei...@redhat.com 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. -- Florian Weimer / Red Hat Product Security Team -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.**org/mailman/listinfo/develhttps://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-**of-conducthttp://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
On 13.09.2013 09:54, 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. Ok, I guess I'll go with avl-analysis or something similar. It would probably be more user friendly to rename the the existing avl to libavl, but I take that again interferes with package mapping efforts? Thanks, Sandro -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
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. Again related to the General Naming Guidelines, FPC ticket #336. If the AVL-Tree project were still alive, what would happen in a new package review request at Fedora? Would a different pair of submitter and reviewer approve the same avl as libavl? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Package name conflict with retired package
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? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
