Re: Why fixes of broken dependencies are not automatically tagged into F17

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 10, 2012 at 08:15:14 +0200,
  Vít Ondruch <vondruch@xxxxxxxxxx> wrote:

Actually the reason why I am asking is that there is a lot of broken dependencies, because of Ruby update. Some of them are already fixed, but not accepted due to freeze. Proposing all this fixes as NTH would be nightmare for me as well as for the blocker review meeting. I'd love to see this process simplified/automated.

If they aren't breaking things in the default install or the 4 desktop
live images they aren't going to be accepted as NTH since they don't
affect the compose and they can easily be fixed with updates.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux