Bug#798749: pu: package monit/1:5.9-1+jessie1
Please don't use -quiet@ when replying to release.debian.org bugs.
There's no good reason for the reply not to be sent to debian-release;
in fact, not doing so is actively harmful.
On Sat, 2015-09-12 at 18:48 +0300, Sergey B Kirpichev wrote:
> On Sat, Sep 12, 2015 at 02:14:04PM +0100, Adam D. Barratt wrote:
> > Control: tags -1 + moreinfo
> >
> > On Sat, 2015-09-12 at 12:32 +0300, Sergey B Kirpichev wrote:
> > > I would like to make an upload to stable in order to fix bug
> > > #796989 (umask bug) in the monit package.
> >
> > +monit (1:5.9-1+jessie1) unstable; urgency=medium
> >
> > That should be 1:5.9-1+deb8u1, with an upload target of
> > "jessie" (uploading a stable update to unstable seems unhelpful :)
>
> Oh, "unstable" is my fault. Fixed.
>
> > > The full patch between this new package version and the version
> > > 1:5.9-1 currently in Jessie is attached (mostly it's come from
> > > upstream, tokens.h and y.tab.c are automatically updated with yacc).
> >
> > I'm confused here. The patch has
> >
> > +Origin: https://bitbucket.org/tildeslash/monit/commits/4e68a4
> >
> > but the diff presented there does not touch tokens.h nor y.tab.c.
>
> Please see the bug's comment: "tokens.h and y.tab.c are automatically
> updated with yacc". I mean, they touched with the yacc tool, not by hand.
> (The exact sequence of commands is at the end of Makefile.am)
I read that, and I know what "automatically updated with yacc" means,
thank you. You appear to have ignored my pointing out that the package
doesn't build-depend on anything providing yacc or bison, and that
builds on the buildds _don't_ perform such updates due to the packages
not being installed in the build environment.
How are the updates managing to get performed in your uploads when a
clean build won't have yacc available?
Regards,
Adam
Reply to: