-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/11/2010 08:30 AM, Matej Cepl wrote: > Stephen Gallagher, Mon, 11 Oct 2010 08:20:08 -0400: >> Being that it's a different upstream project now, you need to create a >> new package in Fedora. Once that's reviewed and included in the >> packageset, you should raise the question of default inclusion with >> FESCo. > > Sure, no problem. Just I don't understand what I do need FESCO for? For > obsoleting the old package? Sorry, I think I was confusing daapd with another (system-critical) component. You probably need to contact the maintainer of the original mt-daapd and make sure they're on-board with switching to this new forked version, as well as trying to identify any applications that depend on mt-daapd and work with them to ensure that forked-daapd either won't break their packages or they can at least release updates simultaneously. If you are in fact the maintainer of mt-daapd, the first part should be easy. :) - -- Stephen Gallagher RHCE 804006346421761 Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkyzBEoACgkQeiVVYja6o6Pq3QCgmUoXbevx+LPHRqZzqjaVDyZK LpQAoIYKeRwAtz8k5JqTmPmb6OB1Thve =TJyQ -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
