In raspbian stretch devscripts is failing with.
testFileExclusion
uscan: uscan (version 2.15.10) See uscan(1) for help
uscan: Scan watch files in .
127.0.0.1 - - [17/Jan/2016 14:24:39] "GET / HTTP/1.1" 200 -
uscan: ./debian/changelog sets package="foo" version="0+dfsg1"
127.0.0.1 - - [17/Jan/2016 14:24:39] "GET /foo-1.tar.gz HTTP/1.1" 200 -
127.0.0.1 - - [17/Jan/2016 14:24:39] code 404, message File not found
127.0.0.1 - - [17/Jan/2016 14:24:39] "HEAD /foo-1.tar.gz.asc HTTP/1.1" 404 -
127.0.0.1 - - [17/Jan/2016 14:24:39] code 404, message File not found
127.0.0.1 - - [17/Jan/2016 14:24:39] "HEAD /foo-1.tar.gz.gpg HTTP/1.1" 404 -
127.0.0.1 - - [17/Jan/2016 14:24:39] code 404, message File not found
127.0.0.1 - - [17/Jan/2016 14:24:39] "HEAD /foo-1.tar.gz.pgp HTTP/1.1" 404 -
127.0.0.1 - - [17/Jan/2016 14:24:39] code 404, message File not found
127.0.0.1 - - [17/Jan/2016 14:24:39] "HEAD /foo-1.tar.gz.sig HTTP/1.1" 404 -
uscan: Newest version on remote site is 1, local version is 0+dfsg1
(mangled local version is 0)
uscan: => Newer package available
uscan: Downloading upstream package: foo-1.tar.gz
uscan: Start checking for common possible upstream OpenPGP signature files
uscan: End checking for common possible upstream OpenPGP signature files
uscan: Successfully downloaded package foo-1.tar.gz
uscan: Successfully repacked ../foo-1.tar.gz as ../foo_1+dfsg1.orig.tar.gz,
deleting 8 files from it.
uscan: Executing user specified script:
uupdate --no-symlink --upstream-version 1+dfsg1 ../foo_1+dfsg1.orig.tar.gz
uupdate: New Release will be 1+dfsg1-0raspbian1.
uupdate: Untarring the new sourcecode archive ../foo_1+dfsg1.orig.tar.gz
uupdate: debian/source/format is "3.0 (quilt)".
uupdate: Auto-generating foo_0+dfsg1-1.debian.tar.xz
uupdate: Unpacking the debian/ directory from version 0+dfsg1-1 worked fine.
uupdate: Remember: Your current directory is the OLD sourcearchive!
uupdate: Do a "cd ../foo-1+dfsg1" to see the new package
ASSERT:uscan: Version should be 1+dfsg1-1 but 1+dfsg1-0raspbian1
expected:<1+dfsg1-0raspbian1> but was:<1+dfsg1-1>
It seems that the program itself and it's testsuite are making different
assumptions about what the version numbering should be. I have no idea
where to start on fixing this though.
_______________________________________________
devscripts-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel
