xulrunner and silent breakage of downstream apps

Michel Salim michel.sylvan at gmail.com
Fri Jun 20 08:52:11 UTC 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Denis Leroy wrote:
> Michel Salim wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> The recent push of xulrunner-1.9 and Firefox 3 broke Miro and devhelp
>> (https://admin.fedoraproject.org/updates/F9/pending/devhelp-0.19.1-2.fc9)
>> again.
>>
>> Is there a way to declare these kinds of dependencies that we are not
>> using right now? Should Miro and devhelp specifically require xulrunner
>> = %{version}-%{release} -- or perhaps a more administrative solution;
>> block a non-security release of xulrunner for at least one day and
>> automatically notify the maintainers of its dependents?
> 
> It broke galeon as well, but this has to be a bug in xulrunner which
> didn't maintain binary compatibility when it was supposed to, no ?
> 
It is indeed, but since it happens rather frequently (arguably, most of
the recent breakages have been because we're tracking an unstable
target, so hopefully things get better from now on), perhaps there ought
to be a mechanism to handle similar situations.

One cool way would be if two package maintainers independently find a
silent API breakage due to the same dependency, an automatic rebuild is
triggered on all other dependents of that library*

* or rather, all dependents who are opted in for auto-updating

- --
Michel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkhbb7oACgkQWt0J3fd+7ZAzcgCeP/dFLKCA9RD2QCnJ/LgxPZL4
qiUAn079LLOYnIfXVJJuZKczp1szyKkP
=5aE/
-----END PGP SIGNATURE-----




More information about the fedora-devel-list mailing list