Re: Binary rebuild of lbdb (#536481)

2010-04-03 Thread martin f krafft
also sprach Andreas Barth a...@not.so.argh.org [2010.04.03.0957 +0200]: Can we please have the full information in order to schedule the necessary binNMUs? Thanks. After further investigation, it seems that the problem was specific to the NMU package, which was never uploaded. I don't remember

Re: Binary rebuild of lbdb (#536481)

2010-04-03 Thread Andreas Barth
* martin f krafft (madd...@madduck.net) [100403 10:06]: also sprach Andreas Barth a...@not.so.argh.org [2010.04.03.0957 +0200]: Can we please have the full information in order to schedule the necessary binNMUs? Thanks. After further investigation, it seems that the problem was specific

Binary rebuild of lbdb (#536481)

2010-03-31 Thread martin f krafft
Dear release team, Can you please trigger a rebuild of lbdb, due to #536481? Thanks, -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `-

Re: Binary rebuild of lbdb (#536481)

2010-03-31 Thread Andreas Barth
Hi, * martin f krafft (madd...@debian.org) [100331 11:09]: Can you please trigger a rebuild of lbdb, due to #536481? why does the binnmu fix the problem? was something changed in a dependency? The bugreport unfortunatly doesn't say anything. Andi -- To UNSUBSCRIBE, email to

Re: Binary rebuild of lbdb (#536481)

2010-03-31 Thread martin f krafft
also sprach Andreas Barth a...@not.so.argh.org [2010.03.31.1134 +0200]: * martin f krafft (madd...@debian.org) [100331 11:09]: Can you please trigger a rebuild of lbdb, due to #536481? why does the binnmu fix the problem? was something changed in a dependency? The bugreport unfortunatly

Re: Binary rebuild of lbdb (#536481)

2010-03-31 Thread Andreas Barth
* martin f krafft (madd...@madduck.net) [100331 13:52]: also sprach Andreas Barth a...@not.so.argh.org [2010.03.31.1134 +0200]: * martin f krafft (madd...@debian.org) [100331 11:09]: Can you please trigger a rebuild of lbdb, due to #536481? why does the binnmu fix the problem? was