Your message dated Mon, 31 Oct 2016 23:48:40 +0000
with message-id <e1c1mjk-0000ai...@fasolo.debian.org>
and subject line Bug#830423: fixed in connect-proxy 1.105-1
has caused the Debian Bug report #830423,
regarding connect-proxy: FTBFS: dpkg-buildpackage: error: dpkg-genchanges gave
error exit status 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
830423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: connect-proxy
Version: 1.101-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> mkdir -p /«PKGBUILDDIR»/debian/connect-proxy/usr/bin/
> install connect-proxy /«PKGBUILDDIR»/debian/connect-proxy/usr/bin/
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> dh_testdir
> dh_testroot
> dh_installchangelogs
> dh_installdocs
> dh_installman
> dh_link
> dh_strip
> dh_compress
> dh_fixperms
> dh_installdeb
> dh_shlibdeps
> dh_gencontrol
> dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is
> not NFS-safe
> dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is
> not NFS-safe
> dh_md5sums
> dh_builddeb
> dpkg-deb: building package 'connect-proxy-dbgsym' in
> '../connect-proxy-dbgsym_1.101-1_amd64.deb'.
> dpkg-deb: building package 'connect-proxy' in
> '../connect-proxy_1.101-1_amd64.deb'.
> dpkg-genchanges -sa >../connect-proxy_1.101-1_amd64.changes
> dpkg-genchanges: warning: debian/changelog(l17): invalid abbreviated
> month name 'Sept'
> LINE: -- Philippe Coval <r...@users.sf.net> Wed, 20 Sept 2007 23:59:42 +0200
> dpkg-genchanges: warning: debian/changelog(l17): cannot parse
> non-comformant date '20 Sept 2007 23:59:42 +0200'
> LINE: -- Philippe Coval <r...@users.sf.net> Wed, 20 Sept 2007 23:59:42 +0200
> Can't call method "epoch" on an undefined value at
> /usr/share/perl5/Dpkg/Changelog.pm line 498.
> dpkg-buildpackage: error: dpkg-genchanges gave error exit status 25
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20160706-2140
The full build log is available from:
http://people.debian.org/~lucas/logs/2016/07/07/connect-proxy_1.101-1_unstable_reb.normal.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: connect-proxy
Source-Version: 1.105-1
We believe that the bug you reported is fixed in the latest version of
connect-proxy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christian Bayle <ba...@debian.org> (supplier of updated connect-proxy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 31 Oct 2016 21:03:15 +0100
Source: connect-proxy
Binary: connect-proxy
Architecture: source amd64
Version: 1.105-1
Distribution: unstable
Urgency: medium
Maintainer: Philippe Coval <r...@gna.org>
Changed-By: Christian Bayle <ba...@debian.org>
Description:
connect-proxy - Establish TCP connection using SOCKS4/5 or HTTP tunnel
Closes: 689051 830423
Changes:
connect-proxy (1.105-1) unstable; urgency=medium
.
* New upstream release (rebuilt tarball)
* Removed quilt, created a Makefile, switched to dh7
* Fix non-comformant date in debian/changelog (Closes: #830423)
* Removed patch (Closes: #689051)
Checksums-Sha1:
cd91c29e318868a65eb9c67649a8263765e17723 1791 connect-proxy_1.105-1.dsc
44bd57b22d45c8e57c35cc2e7ec68b9a18150ab0 24809 connect-proxy_1.105.orig.tar.gz
10125a922614151aafb3e777e9f0440606683b7c 5048
connect-proxy_1.105-1.debian.tar.xz
dde39f67469b5f2514d9d2de0a570b196124dffe 4104
connect-proxy-dbgsym_1.105-1_amd64.deb
743babc24e6d73423808633889a7f91154fc49a5 18830 connect-proxy_1.105-1_amd64.deb
Checksums-Sha256:
54003f69f230819708d15c0a319860ff09d65a0310c7c0b6d811bf13d5c1e68b 1791
connect-proxy_1.105-1.dsc
235a2099df7a8569852d59cbc00e968d458c4e5a603f948b75e2f407a7603698 24809
connect-proxy_1.105.orig.tar.gz
1211f7350b48abdb632e509283d8deb0582a6bb65e65388d15eff3eaaec81f28 5048
connect-proxy_1.105-1.debian.tar.xz
a95779329875fb19de239ee317ae7e4a8e8aea5629ced7d35fd14f3d734ec991 4104
connect-proxy-dbgsym_1.105-1_amd64.deb
e4e48108020d41c52a7a4aa89195ed9db753d5ec6aa94d5fe967b31b5fedc736 18830
connect-proxy_1.105-1_amd64.deb
Files:
67b23e42d18f0dffd036bcf306a8a308 1791 net optional connect-proxy_1.105-1.dsc
599b7448c791eed90a9902ea7122c8ca 24809 net optional
connect-proxy_1.105.orig.tar.gz
f46f02701013ed84c9ddbae02d7f9311 5048 net optional
connect-proxy_1.105-1.debian.tar.xz
143715211bc3e5f8f45b6ccf454af173 4104 debug extra
connect-proxy-dbgsym_1.105-1_amd64.deb
06bafb53842276daf2a9e5fb282a0879 18830 net optional
connect-proxy_1.105-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJYF9NRAAoJEGuYLeu/6RwpaVYP/j6yvqxuCX9WXn9kIzMoO3xU
FHQM5cg8A6Y6LqyH3WuVjrE6t1QtFynYzxetCFSRaccTPx2mL6yhzLDfe4DNnFdM
+6xYzdtMmAXOQmh2zswD1iFDHfPGwtCxKeAhExEzX/YvaSref35B0CfFWcYEklQN
+3J9WY7wXYtmAManjTAt6iWrC31l8sO1qvwHvOzUC7EK/UdR8c/lKh6Rsru7x7E9
u7V/31chatWVfF1DEHHbOd7Zkn1vDGZ7negn18Ff4HHJp5+8f7AXIfTYEeaWn6v7
8eThEAX8K0a6hjg8NbahPLJUMFgT+iHAKG5CK7LN7tRTjW67mZaAxLPz0cvX6TNQ
km/j0EkDKI7w9lZ8HLA933thxQyqwfvtUDWNXwGTREbVYSf2HtCusA7jL1TjAYVe
4BFGPKrS14rlhEajadzJES0dZockGlVT38KgR/F8/wgDcyw1tQdOzbxwN2Zv7v3V
Ou6kUBK7N1XGfeIwapJfNhjm97Dzg5eoKybGqMKCbOCsiRILeFkU4BEQ4SvWm3w4
l1xM6LqARtF7fZiDeWTtX0AWdw2/wzvsZnToVrNjmO78gOX2Gg4iRYUEVGHadjiM
BtiOxzGn4j9PBE3ao2xheErLXm5AtoJvkdb6GxUG6useI8IxZuxRlID8EOsg1ICB
RpTtYIX5EGKLcQVUaRYV
=PPGf
-----END PGP SIGNATURE-----
--- End Message ---
