[OM Cooker] systemd and kaninah
Colin Close
itchka at compuserve.com
Tue Feb 7 10:02:32 EST 2017
It was probably me. But others need to consider those who do the testing. I
suspect that what has happened here is that somebody has published a package
directly to the repo and the maintainer has not marked the one in Kahinah
either already published or superseded. In this case its not obvious to the
tester that the one he installs for testing is not the version in kahinah and
thus if it installs and works and has expired there is no reason not to
publish. Kahinah does not check for a later release because no packages should
be pushed directly to a released repository. I realise that sometimes it's
necessary to push packages in an emergency and in this case a QA maintainer
will do this if asked. It's also possible to push a package to kahinah and to
the main repo and to the testing repo if the one in kahinah is marked "already
published" then this serves as a signal to the tester that such an action has
been taken. crisb does this and we have no problems.
I will ask Robert Xu if he can modify kahinah to check for for supercession
but because kahinah periodically polls abf this will not be guaranteed to
catch every instance.
Best,
Colin
On Tuesday, 7 February 2017 16:27:30 GMT Alexander Stefanov-Khryukin wrote:
> Someone published outdated systemd to 3.0
> https://abf.openmandriva.org/build_lists/95096
> and now we got https://abf.openmandriva.org/build_lists/95707
>
> If it is kaninah again i will block it on abf
More information about the OM-Cooker
mailing list