On Sun, Jun 5, 2016 at 10:47 AM, TheSin <the...@southofheaven.org> wrote:
> our version of dpkg is FAR too old to report upstream, not to mention I’m
> sure it is fixed upstream by now. Check the patch in my PR see if it’s
> still needed. I haven’t had a chance but i’m gonna try it. I’m pretty
> sure I have a test case already in dpkg 1.15.x for gnu vs bad tar at the
> very least.
> ---
>
This appears to be a new regression introduced in the 1.29 release of tar.
A quick and dirty test of a fink build against a symlinked /sw/bin/tar
pointing at the MacPorts /opt/local/bin/gnutar 1.28 package doesn't produce
the root level DEBIAN directory. So we definitely should try to create a
test case for reporting back upstream.
Jack
> TS
> http://www.southofheaven.org/
> Life begins and ends with chaos, live between the chaos!
>
> > On Jun 5, 2016, at 8:35 AM, Jack Howarth <howarth.at.f...@gmail.com>
> wrote:
> >
> > The new tar 1.29 release (which is available on fink tracker at
> https://sourceforge.net/p/fink/package-submissions/4664/) passes its test
> suite cleanly on x86_64-apple-darwin15 but causes fink to exhibit broken
> behavior when installed. The problem is that, when a package is built under
> the new tar 1.29 release, the creation of the build-lock misplaces the
> DEBIAN control directory at the root level. This creates debs that
> incorrectly have the DEBIAN control directory placed at root as well and
> thus all conflict with each other.
> > We should try to puzzle out if the tar hacks used in dpkg.patch
> really valid and, if so, try to create a stand-alone test case to report
> back upstream to the bug-tar mailing list (as this glitch isn't being
> captured by their current test suite).
> > Jack
> > ps The main changes I see here are...
> >
> > - execlp(TAR,"tar","-cf", "-", "-T", "-", "--null", "--no-recursion",
> (char*)0);
> > + execlp(TAR,"tar","-cf", "-", "--null", "-T", "-", "--no-recursion",
> (char*)0);
> >
> >
> > for dpkg-1.10.21/dpkg-deb/build.c.
> >
> >
> >
> ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols
> are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > planning reports.
> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_______________________________________________
> > Fink-devel mailing list
> > Fink-devel@lists.sourceforge.net
> > List archive:
> > http://news.gmane.org/gmane.os.apple.fink.devel
> > Subscription management:
> > https://lists.sourceforge.net/lists/listinfo/fink-devel
>
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
