That's because it's using the wrong scriplets, it's using Fedora ones.

It should use the Mageia ones, as documented here:
https://wiki.mageia.org/en/System_Service_policy

Assignee: bugsquad => bruno

Cauldron updated

Status: NEW => ASSIGNED

Update made to 5 and advisory proposed

Assignee: bruno => qa-bugs

(In reply to Bruno Cornec from comment #3)
> Update made to 5 and advisory proposed

I don't see the advisory nor the list or RPMs :)

Actually the advisory was uploaded directly to SVN. Please post it also in the bug report next time Bruno, so that QA testers know what they are supposed to test.

Here it is:

Advisory
========
Updated docker-registry package fixes bad macros usage

Fix macro usage by moving fedora ones to mageia ones

SRPM:
=====
docker-registry-0.9.1-1.1.mga5

RPMS:
=====
docker-registry-0.9.1-1.1.mga5.noarch

(In reply to Rémi Verschelde from comment #5)
> Updated docker-registry package fixes bad macros usage

This is good for a commit message, but for an advisory it should tell what the issue was in the first place (a post-installation script that failed and what consequences).

Mageia 5 64.

Summary: seems fine, but there are warnings.

I can confirm that the update package no longer gives errors during installation and removal. And I looked at the spec file and the only change concerns those scripts.

I haven't tested the program in itself, but unless something was broken during the build, there's no reason a regression would have been introduced by the changes.

Note that users will still see a failure during the update because the uninstall scriplet of the old package fails.

docker-registry service starts fine. Logs contain warnings though, altough I don't think they need blocking the update. If there's something to fix, though, then it would be great to fix it in the same update to avoid to have twice the amount of download for users.

Logs:

juil. 27 14:16:50 localhost gunicorn[11381]: 27/Jul/2015:14:16:50 +0000 WARNING: LRU cache disabled!
juil. 27 14:16:50 localhost gunicorn[11381]: 27/Jul/2015:14:16:50 +0000 WARNING: LRU cache disabled!
juil. 27 14:16:50 localhost gunicorn[11381]: 27/Jul/2015:14:16:50 +0000 DEBUG: Will return docker-registry.drivers.file.Storage
juil. 27 14:16:50 localhost gunicorn[11381]: 27/Jul/2015:14:16:50 +0000 DEBUG: Will return docker-registry.drivers.file.Storage
juil. 27 14:16:50 localhost gunicorn[11381]: 27/Jul/2015:14:16:50 +0000 WARNING: Cache storage disabled!
juil. 27 14:16:50 localhost gunicorn[11381]: 27/Jul/2015:14:16:50 +0000 WARNING: LRU cache disabled!
juil. 27 14:16:50 localhost gunicorn[11381]: 27/Jul/2015:14:16:50 +0000 DEBUG: Will return docker-registry.drivers.file.Storage
juil. 27 14:16:51 localhost gunicorn[11381]: 27/Jul/2015:14:16:51 +0000 WARNING: Cache storage disabled!
juil. 27 14:16:51 localhost gunicorn[11381]: 27/Jul/2015:14:16:51 +0000 WARNING: LRU cache disabled!
juil. 27 14:16:51 localhost gunicorn[11381]: 27/Jul/2015:14:16:51 +0000 DEBUG: Will return docker-registry.drivers.file.Storage

Bruno, can you answer that so that we can reach a decision?

Whiteboard: advisory => advisory MGA4-64-OK

Sorry, missed your comment Samuel.

As said in this post:
https://github.com/docker/docker-registry/issues/595

These are just warnings, not errors. I think we're good to upload.

Validating from Stormi's comment 7. Advisory amended as per comment 5.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0128.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED