Control: severity -1 wishlist

Hi again!

On Wed, 2013-08-07 at 17:47:03 +0200, Guillem Jover wrote:
> Control: severity -1 normal

> On Wed, 2013-08-07 at 14:42:05 +0200, Frederic Van Espen wrote:
> > Package: dpkg-dev
> > Version: 1.16.10
> > Severity: serious
> > Justification: fails to build from source (but built successfully in the 
> > past)
> 
> I've just tested, and dpkg-source 1.15.x shows the same behavior.
> Not saying it's desirable, just that I don't see how this breaks
> stuff that used to work in the past?

I tested now with 1.14.x just to confirm my suspicion, and there it
does not work either, so I don't really see how this has ever worked
for you. Lowering to wishlist.

> > I have a package that has the following content in the
> > debian/source/include-binaries
> > 
> > debian/extra/foo.so
> > 
> > However, when running dpkg-source this file is not added to the source
> > package. dpkg-source --help tells me that a default set of -I options is
> > added when no such option is used:
> >   -I[<pattern>]            filter out files when building tarballs
> >                                (defaults to: -I*.a -I*.la -I*.o -I*.so
> >                                -I.*.sw? -I*~ -I,,* -I.[#~]* -I.arch-ids
> >                                -I.arch-inventory -I.be -I.bzr
> >                                -I.bzr.backup -I.bzr.tags -I.bzrignore
> >                                -I.cvsignore -I.deps -I.git -I.gitignore
> >                                -I.hg -I.hgignore -I.hgtags -I.shelf
> >                                -I.svn -ICVS -IDEADJOE -IRCS -I_MTN
> >                                -I_darcs -I{arch}).
> > 
> > Altough I understand the default set of excludes, when I specifically
> > request files to be added through the include-binaries file, the should
> > not be excluded.
> 
> Yes, I agree, and I'll fix this for either 1.17.2 or 1.17.3.

The problem is that this is slightly more involved, as the problem
comes from the --exclude option being passed to tar. I'm now reworking
the code to overcome this limitation. But you'll need to workaround it
on older dpkg-source, by for example resetting the tar-ignore option
and removing -I*.so from it, because this is only going to get fixed
in the 1.17.x series.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to