Hi,
1. GNOME 3.24 prerelease broke builds just in time for the mass rebuild,
2. upstream took a few days to come up with fixed support for GNOME 3.24,
3. I built fixed packages and they have been in rawhide and f27-updates-testing for some time now,
4. but I can't push them to stable because of the beta freeze that went into effect.
Now I get daily, angry automated e-mails that tell me to fix my sh!t ASAP because of broken deps in the F27 tree.
I haven't yet had to deal with a problem like this ever before, what's the right course of action?
Just sitting on my hands (and on broken packages) until the beta freeze is lifted doesn't feel like the right thing to do.
I've got two packages (gala, wingpanel) that have broken dependencies in F27 because of unfortunate timing:
1. GNOME 3.24 prerelease broke builds just in time for the mass rebuild,
2. upstream took a few days to come up with fixed support for GNOME 3.24,
3. I built fixed packages and they have been in rawhide and f27-updates-testing for some time now,
4. but I can't push them to stable because of the beta freeze that went into effect.
Now I get daily, angry automated e-mails that tell me to fix my sh!t ASAP because of broken deps in the F27 tree.
I haven't yet had to deal with a problem like this ever before, what's the right course of action?
Just sitting on my hands (and on broken packages) until the beta freeze is lifted doesn't feel like the right thing to do.
Thanks, Fabio
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
