Hi,
Am Sonntag, den 04.01.2015, 15:29 +0100 schrieb Alexander Kurtz: > On Sat, 2014-11-22 at 16:40 +0100, Joachim Breitner wrote: > > It would be nice to find out what was causing this and, if there is a > > risk that this will happen again, use some mechanism to avoid this. > > But again, there are likely more important things to do. > > after reading this blog post > > > https://people.debian.org/~lunar/blog/posts/reproducible_builds_against_rc_bugs/ > > I'd like to send this to cont...@bugs.debian.org: > > reassign 769874 libical1 > forcemerge 773916 766454 769874 > thanks > > Do you agree? Well, 773916 is closed, so if you want to merge them, does that mean that all problems are solved for jessie? Looking at my evolution calendar at the moment, I see the bug: libecal-1.2-16 3.12.9~git20141128.5242b0-2 libical1 1.0-1.2 Maybe it is just a matter of binNMUs, but someone really needs to make sure that we ship jessie with a working combination. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
