Michael Biebl <bi...@debian.org> writes: > If 215-8 was working successfully, finding the faulty commit would > indeed be very helpful. If you know how to use git bisect, you could use > that to determine the commit. This will be a lengthy process though and > probably not something you want to do on a live system. > > Unfortunately snapshots.debian.org [1] doesn't seem to have any sparc64 > binaries which would have simplified that process somewhat, as you could > have quickly installed older versions. And we don't have any sparc64 > porter boxes :-/
I think the original bug report refered to sparc, not sparc64. Packages for some versions should be available from snapshot.d.o, but only for versions that could actually be built. Maybe look up versions from https://buildd.debian.org/status/logs.php?pkg=systemd&arch=sparc that built successfully and then try to obtain those from snapshot.d.o? That would also work for sparc64, but the build history looks even worse there: http://buildd.debian-ports.org/status/logs.php?pkg=systemd&arch=sparc64 Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
