Control: reassign -1 release.debian.org
Control: retitle -1 nmu:  libsigc++-2.0_2.4.1-2

Am 12.08.2015 um 18:57 schrieb Edmund Grimley Evans:
> Source: libsigc++-2.0
> Version: 2.4.1-2
> 
> Looking at the build logs at
> https://buildd.debian.org/status/package.php?p=libsigc%2B%2B-2.0&suite=sid
> I note that on arm64 this package was built with build-essential_11.7
> and g++-4.9, unlike on the other architectures, which used g++-5. Is
> this deliberate, or an accident resulting from some kind of lagginess?
> If it's the latter, is there an easy way of detecting which other
> packages might be affected?
> 
> (This isn't really a bug in the source package, but I can see that
> this package is being actively maintained so thought this would be a
> good way to contact someone who can get this fixed, if it is a
> problem. I've already written to ar...@buildd.debian.org about a
> similar possible problem with cairomm. If this is all being
> automatically monitored and will be fixed in due course, then sorry
> for the noise.)

Re-assigning to the release team. Please schedule a binNMU of
libsigc++-2.0_2.4.1-2 on arm64

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

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to