On Sat, 3 Aug 2013 16:05:11 +0200, Simone Caronni wrote: > can someone please tell me if I understood correctly the packaging > guidelines regarding packages being retired after a rename [1]? > > Upstream has changed between minor releases how the source code is > packaged. Instead of multiple source tarballs there is only one tarball > that is used to generate the same packages as before; so the update is for > all branches. What has happened to guacamole-common-javadoc.noarch guacamole-ext-javadoc.noarch ? Those are not built anymore, but nothing obsoletes them. > Should I run "fedpkg retire <explanation>" in each branch that is going to > be obsolete by the new packages AFTER the new packages [2] hit stable, > right? Before or after, doesn't matter. Most important is that the new packages have been reviewed and approved. Remember, the old packages have been published already and are still available in the repositories. Activities in package git, pkgdb and koji don't affect the repository users. (And I assume you've published the new builds for Rawhide already, too, so the koji blocking request will only result in removing packages that have been obsoleted by the newer builds anyway.) > > [1] http://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > [2] > https://admin.fedoraproject.org/updates/FEDORA-2013-13687/guacamole-client-0.8.2-2.fc19,guacamole-server-0.8.2-2.fc19 > -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
