afflib package - bug #645915
christophe.monniez at fccu.be
Mon Jan 9 07:10:18 UTC 2012
Le samedi 07 janvier 2012 à 17:10 +0100, Julien Valroff a écrit :
> Le mardi 27 déc. 2011 à 10:06:38 (+0100 CET), Christophe Monniez a écrit :
> > Hi,
> > I worked on this bug  to try to solve it.
> > I did a build in a clean environment and found that it was not linked
> > against libreadline.
> I've just requested a binNMU for i386 to fix the current situation. Once
> done, we will be able to at least lower the severity of the bug. I leave it
> up to you if you consider it should be closed or not.
Thanks Julien, I will see once the package will be uploaded.
> The situation comes from an uploader build made in an unclean environment
> (the last upload was an NMU, hence independent on our work).
> I have also worked somehow on the package in git but not fixed all the
> lintian warnings (nor tested it all).
I'm working on the other lintian warnings (man pages).
> BTW, is there any good reason you use git-dch? I find it very hard to follow
> the work because of it (but may be due to the fact I am not used to using
Well, I have no good reason to use it. We really should update our
workflow to see who works on what.
It was once said that it's up to the uploader to maintain the changelog
because it's automatically generated by git (I suppose git-dch).
So, when I work on a package, I don't update the changelog, to not
interfere with the uploader work.
Am I wrong ? What is the "good" way of doing it ?
Christophe Monniez <christophe.monniez at fccu.be>
More information about the forensics-devel