On 02/04/2013 09:50 AM, Mathieu Malaterre wrote: > > What's with the renaming (Please add a REAMDE.source for explanation thanks) ? > > $ uscan --verbose --force-download > [...] > Newest version on remote site is 1.4.1, local version is 1.4.1+repack1 > => remote site does not even have current version > -- Scan finished > > $ wget http://stable.hypertriton.com/agar/agar-1.4.1.tar.gz > $ md5sum agar_1.4.1+repack1.orig.tar.gz agar-1.4.1.tar.gz > 3483244d3be644f769f5b79fe4817063 agar_1.4.1+repack1.orig.tar.gz > ce71fb11ad79c926a968a4ed29053820 agar-1.4.1.tar.gz This was because a pre-built Windows binary was included in the upstream source tarball. The complete source for the binary is included. After some discussion, the executable is now being left in and the pristine tarball is being included. I change the package version accordingly and re-uploaded to m.d.n. > And I have not look carefully if this is an issue with private glx > implementation, but package currently FTBFS on my system: > > > dpkg-gensymbols: warning: some symbols or patterns disappeared in the > symbols file: see diff output below > dpkg-gensymbols: warning: debian/libag-gui4/DEBIAN/symbols doesn't > match completely debian/libag-gui4.symbols > --- debian/libag-gui4.symbols (libag-gui4_1.4.1+repack1-1_amd64) > +++ dpkg-gensymbolsXVrKDS 2013-02-04 15:46:19.000000000 +0100 > @@ -931,7 +931,7 @@ > agDefaultFont@Base 1.4.1 > agDirDlgClass@Base 1.4.1 > agDriverClass@Base 1.4.1 > - agDriverGLX@Base 1.4.1 > +#MISSING: 1.4.1+repack1-1# agDriverGLX@Base 1.4.1 > agDriverList@Base 1.4.1 > agDriverListSize@Base 1.4.1 > agDriverMwClass@Base 1.4.1 > @@ -1074,4 +1074,4 @@ > agWindowToFocus@Base 1.4.1 > agnKeySyms@Base 1.4.1 > agnUnitGroups@Base 1.4.1 > - modMasks@Base 1.4.1 > +#MISSING: 1.4.1+repack1-1# modMasks@Base 1.4.1 > dh_makeshlibs: dpkg-gensymbols -plibag-gui4 > -Idebian/libag-gui4.symbols -Pdebian/libag-gui4 > -edebian/libag-gui4/usr/lib/libag_gui.so.4.0.0 > returned exit code 1 > make: *** [binary] Error 1 The package builds as-is in a current sid pbuilder environment. Those symbols are only built when the package configuration can successfully detect the presence of working GLX headers. It would be useful to check the config.log to identify the reason why this was unsuccessful for you. -- Stephen M. Webb <stephen.webb@bregmasoft.ca>
Attachment:
signature.asc
Description: OpenPGP digital signature