Bug#787258: FTBFS on mipsel: test-suite failures

[Michael Biebl]

Am 02.06.2015 um 11:16 schrieb James Cowgill:
> I tried building systemd on a few different machines and couldn't get it
> to fail on any of them. Then I looked at what packages were installed on
> the buildds. On the machines it fails on, sysvinit-core is installed and
> on mipsel-aql-01 (which passed the tests) systemd-sysv is installed.
> 
> I then found this:
> https://bitbucket.org/Tarnyko/uselessd/issue/7/uselessd-7-test-strv-fails-on-slackware
> 
> Presumably systemd has never been installed within the mipsel-manda-01
> buildd chroot and so no machine-id has ever been generated for it (which
> the tests rely on).

If that's the root cause, then the work-around to ignore test-suite
failures on mipsel is not really sufficient. After all, we could have
build chroots on other archs as well without /etc/machine-id.

Maybe we should simply revert d2446397043931d22a3411025c8102d8140f813c.
The presence of the init metapackage doesn't guarantee that we have
/etc/machine-id.

The alternative is, to poke all buildd maintainers and have their build
chroots updated to use systemd-sysv instead of sysvinit-core.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150602/262ee69b/attachment-0002.sig>