> Updates seem to have been pushed out now, thanks!. > > But I see a different problem with my update. Taskotron failure which > I don't understand: > > not ok - depcheck for Bodhi update systemd-216-20.fc21 # FAIL > --- > arch: x86_64 > details: > output: |- > Build systemd-216-20.fc21 failed depcheck > package libgudev1-216-20.fc21.i686 requires systemd = 216-20.fc21, but > none of the providers can be installed > systemd-216-20.fc21.i686 has inferior architecture > systemd-216-20.fc21.i686 has inferior architecture > package systemd-python-216-20.fc21.i686 requires systemd = 216-20.fc21, > but none of the providers can be installed > systemd-216-20.fc21.i686 has inferior architecture > systemd-216-20.fc21.i686 has inferior architecture > package systemd-compat-libs-216-20.fc21.i686 requires systemd-libs = > 216-20.fc21, but none of the providers can be installed > systemd-libs-216-20.fc21.i686 has inferior architecture > systemd-libs-216-20.fc21.i686 has inferior architecture > package systemd-216-20.fc21.i686 requires systemd-libs = 216-20.fc21, > but none of the providers can be installed > systemd-libs-216-20.fc21.i686 has inferior architecture > systemd-libs-216-20.fc21.i686 has inferior architecture > package libgudev1-devel-216-20.fc21.i686 requires libgudev1 = > 216-20.fc21, but none of the providers can be installed > libgudev1-216-20.fc21.i686 has inferior architecture > libgudev1-216-20.fc21.i686 has inferior architecture > package systemd-devel-216-20.fc21.i686 requires systemd = 216-20.fc21, > but none of the providers can be installed > systemd-216-20.fc21.i686 has inferior architecture > systemd-216-20.fc21.i686 has inferior architecture > item: systemd-216-20.fc21 > outcome: FAILED > summary: systemd-216-20.fc21 into F21 stable > type: bodhi_update > ... > > > I agree i686 is inferior, but I thought we still allow it :) Please see my answer to Orion Poplawski, this is the same issue. > > A related problem is that I don't see any way to override this > taskotron failure (let's say that I was certain that this is not an > issue). Status is 'testing', Requested 'stable', but the message says > that the automatic push was disabled, so the update seems to be stuck > in a limbo. > > [1] > https://admin.fedoraproject.org/updates/FEDORA-2015-1793/systemd-216-20.fc21 IIUIC, the autopush was disabled too late (it had already requested push to stable by that time), so it had no effect - your package got pushed stable the usual way. This might be confusing, I'd expect the stable request to be canceled when disabling autopush. But it's probably not worth requesting changes in Bodhi right now, because Bodhi2 should be almost ready for deployment. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
