Bug#796045: nmu: leveldb_1.18.3

2015-08-28 Thread GCS
On Tue, Aug 18, 2015 at 9:52 PM, Gaudenz Steinlin gaud...@debian.org wrote: Usertags: binnmu nmu leveldb_1.18.3 . ALL . unstable . -m Rebuild for libsnappy transition leveldb has already been uploaded for it's own transition before the upload of snappy for it's transition. So leveldb needs

Bug#796045: nmu: leveldb_1.18.3

2015-08-25 Thread Gaudenz Steinlin
Julien Cristau jcris...@debian.org writes: On Tue, Aug 18, 2015 at 21:52:08 +0200, Gaudenz Steinlin wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu leveldb_1.18.3 . ALL . unstable . -m Rebuild for libsnappy transition

Bug#796045: nmu: leveldb_1.18.3

2015-08-25 Thread GCS
On Tue, Aug 25, 2015 at 10:27 AM, Gaudenz Steinlin gaud...@debian.org wrote: Julien Cristau jcris...@debian.org writes: We don't really want individual requests for binNMUs for g++5 followup transitions. This will be taken care of in due time. That's fine for me as long as it get's

Bug#796045: nmu: leveldb_1.18.3

2015-08-18 Thread Gaudenz Steinlin
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu leveldb_1.18.3 . ALL . unstable . -m Rebuild for libsnappy transition leveldb has already been uploaded for it's own transition before the upload of snappy for it's transition. So