Processed: affects 963035
Processing commands for cont...@bugs.debian.org: > # This doesn't affect building chromium but running chromium, so it affects > the binary and not the source package > affects 963035 - src:chromium + chromium Bug #963035 [ffmpeg] ffmpeg: 4.3 breaks chromium Removed indication that 963035 affects src:chromium > thanks Stopping processing here. Please contact me if you need assistance. -- 963035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859926: Hello dear
*Dear,I hope my email finds you in good health.Finally, i made it to success with another partner after you couldn't complete the transaction with me. But i did not forget your effort then, it was part of my success still. So i left a bank cheque with the Catholic Reverend sister whom i told you about sometime ago as my trusted Secretary.Contact her at this below email immediately, introduce yourself as the cashier cheque recipient and demand for your cheque release process.Send email to: Reverend sister Angela HelpeEmail:helperange...@gmail.com Tel: +228 98766629*
Bug#859926: Hello dear
*Dear,I hope my email finds you in good health.Finally, i made it to success with another partner after you couldn't complete the transaction with me. But i did not forget your effort then, it was part of my success still. So i left a bank cheque with the Catholic Reverend sister whom i told you about sometime ago as my trusted Secretary.Contact her at this below email immediately, introduce yourself as the cashier cheque recipient and demand for your cheque release process.Send email to: Reverend sister Angela HelpeEmail:helperange...@gmail.com Tel: +228 98766629*
Bug#859926: Hello dear
*Dear,I hope my email finds you in good health.Finally, i made it to success with another partner after you couldn't complete the transaction with me. But i did not forget your effort then, it was part of my success still. So i left a bank cheque with the Catholic Reverend sister whom i told you about sometime ago as my trusted Secretary.Contact her at this below email immediately, introduce yourself as the cashier cheque recipient and demand for your cheque release process.Send email to: Reverend sister Angela HelpeEmail:helperange...@gmail.com Tel: +228 98766629*
Bug#859926: Hello dear
*Dear,I hope my email finds you in good health.Finally, i made it to success with another partner after you couldn't complete the transaction with me. But i did not forget your effort then, it was part of my success still. So i left a bank cheque with the Catholic Reverend sister whom i told you about sometime ago as my trusted Secretary.Contact her at this below email immediately, introduce yourself as the cashier cheque recipient and demand for your cheque release process.Send email to: Reverend sister Angela HelpeEmail:helperange...@gmail.com Tel: +228 98766629*
Bug#932749: marked as done (Debian packaging of EclipseLink is missing essential classes)
Your message dated Mon, 22 Jun 2020 23:33:37 + with message-id and subject line Bug#932749: fixed in eclipselink 2.6.9-1 has caused the Debian Bug report #932749, regarding Debian packaging of EclipseLink is missing essential classes 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.) -- 932749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libeclipselink-java Version: 2.6.6-1 Severity: grave When running a very simple test application, or indeed any production application I have at hand, using the Debian-packaged version of EclipseLink, I run into the following error when calling javax.persistence.Persistence.createEntityManagerFactory: [...] Caused by: java.lang.ClassNotFoundException: org.eclipse.persistence.internal.libraries.asm.ClassVisitor at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 9 more Indeed eclipselink-2.6.6/debian/excludesfiles/build contains the following line: org/eclipse/persistence/internal/libraries/** I conclude that the Debian packaging of EclipseLink is unusable at the moment, hence the severity setting. (The same applications work fine with upstream's eclipselink.jar. I'm not sure why this library is packaged in Debian, as nothing in buster seems to depend on it.)--- End Message --- --- Begin Message --- Source: eclipselink Source-Version: 2.6.9-1 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of eclipselink, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated eclipselink 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 16:34:09 +0200 Source: eclipselink Architecture: source Version: 2.6.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 932746 932749 Changes: eclipselink (2.6.9-1) unstable; urgency=medium . * Team upload. * New upstream release (Closes: #932746) - Updated the Maven poms * Include the embedded libraries in eclipselink.jar (Closes: #932749) * Depend on libgeronimo-jta-1.2-spec-java instead of libgeronimo-jta-1.1-spec-java * Removed the -doc package * Standards-Version updated to 4.5.0 * Switch to debhelper level 12 Checksums-Sha1: cae5f0c6ba3b403b253d4f42335b99cec423725d 2365 eclipselink_2.6.9-1.dsc d274c6d096a5d0d32248de59b10e836d235314b1 3448940 eclipselink_2.6.9.orig.tar.xz 954ac2568e064b3cd5eccfddbba8c00d3172f445 15592 eclipselink_2.6.9-1.debian.tar.xz 1fceb823d5bc85c4a7e035bd70d72be071995689 13746 eclipselink_2.6.9-1_source.buildinfo Checksums-Sha256: aa73a8b8871e7313fc29e08abcd7b7a293213d170fd2e6b9af6ab5906d894464 2365 eclipselink_2.6.9-1.dsc 96cf7f5c9f9a7362fb6fb38df55a94538ba4e8420c6cb7503b4f93f4da44298f 3448940 eclipselink_2.6.9.orig.tar.xz 4283acf10810e0df994fa61d8b84c374dbaf7ef5aa617ef449d83d4f73adc1b2 15592 eclipselink_2.6.9-1.debian.tar.xz e02debe378baca62d343ed4ad666d331661e3ededebe4fea51b6a95fb1845089 13746 eclipselink_2.6.9-1_source.buildinfo Files: eca1e6fe09d24794c8f492a77a7e0ba4 2365 java optional eclipselink_2.6.9-1.dsc 96f246934b5804d4e449f17da537b76d 3448940 java optional eclipselink_2.6.9.orig.tar.xz 57c15ecacdecfd472399c589758dcfef 15592 java optional eclipselink_2.6.9-1.debian.tar.xz 9ce720f0a6844db00adbff436bed0ee3 13746 java optional eclipselink_2.6.9-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl7xPH4SHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs/uMP/1vtj4GcT4Su3v2HC2Kr/dFzhBa9kDp/ kiJJlEW7l+kKtTvjT0IN2ARFSzhnWMgJFQdN1px4hfwhyeHpHZOuFxuFlFltBZXO 5MHMRw3zsDgKidBp/coI4RNw+BSfVgYtxKYUamtOSmMqrjW9RpjwVth4A1/8meeD WT6Il1Bn34Ke2h/yTL7YFb7FwVwaygkYhqMbY4VirfOuaShV/zFizPSKl5STFKvQ
Processed: Bug#932749 marked as pending in eclipselink
Processing control commands: > tag -1 pending Bug #932749 [libeclipselink-java] Debian packaging of EclipseLink is missing essential classes Added tag(s) pending. -- 932749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963387: [request-tracker-maintainers] Bug#963387: Bug#963387: request-tracker4: FTBFS: CORE missing dependencies: Plack::Handler::Starlet ...MISSING
On Mon, Jun 22, 2020 at 11:44:13PM +0100, Dominic Hargreaves wrote:
> Control: retitle -1 request-tracker4: FTBFS with newer libmojolicious-perl:
> t/web/ticket_owner.t
> Control: tags -1 + confirmed
>
> On Sun, Jun 21, 2020 at 10:34:37PM +0200, Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> > Relevant part (hopefully):
>
> ...
> > > SOME DEPENDENCIES WERE MISSING.
> > > MAILGATE missing dependencies:
> > > Mozilla::CA ...MISSING
> > > CORE missing dependencies:
> > > Plack::Handler::Starlet ...MISSING
> > >
> > > Perl library path for /usr/bin/perl:
> > > /etc/perl
> > > /usr/local/lib/x86_64-linux-gnu/perl/5.30.3
> > > /usr/local/share/perl/5.30.3
> > > /usr/lib/x86_64-linux-gnu/perl5/5.30
> > > /usr/share/perl5
> > > /usr/lib/x86_64-linux-gnu/perl-base
> > > /usr/lib/x86_64-linux-gnu/perl/5.30
> > > /usr/share/perl/5.30
> > > /usr/local/lib/site_perl
> > > make[1]: *** [Makefile:272: testdeps] Error 1
>
> This was not the problem (the immediately following lines are):
>
> make[1]: Leaving directory '/<>'
> make: [debian/rules:38: build-stamp] Error 2 (ignored)
>
> > The full build log is available from:
> >
> > http://qa-logs.debian.net/2020/06/20/request-tracker4_4.4.4-1_unstable.log
>
> The actual error is:
>
> Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm line 237.
> Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm line 237.
>
> # Failed test 'no warnings'
> # at /usr/share/perl/5.30/Test/Builder.pm line 152.
> # There were 1 warning(s)
> # Previous test 95 'Ticket -> Reply'
> # Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm line 237.
> # at /usr/share/perl5/Log/Dispatch/Perl.pm line 86.
> # Log::Dispatch::Perl::__ANON__("Not an ARRAY reference at
> /usr/share/perl5/Mojo/DOM/CSS.pm li"...) called at
> /usr/share/perl5/Log/Dispatch/Output.pm line 64
> #
> Log::Dispatch::Output::_log_with_num(Log::Dispatch::Perl=HASH(0x55e04f914d00),
> 5, "message", "Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm
> li"..., "level", "critical") called at /usr/share/perl5/Log/Dispatch.pm line
> 170
> # Log::Dispatch::_log_with_num(Log::Dispatch=HASH(0x55e04f8d43b8), 5,
> "level", "critical", "message", "Not an ARRAY reference at
> /usr/share/perl5/Mojo/DOM/CSS.pm li"...) called at
> /usr/share/perl5/Log/Dispatch.pm line 25
> # Log::Dispatch::__ANON__(Log::Dispatch=HASH(0x55e04f8d43b8), "Not an ARRAY
> reference at /usr/share/perl5/Mojo/DOM/CSS.pm li"...) called at
> /<>/lib/RT.pm line 408
> # RT::__ANON__("Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm
> li"...) called at /usr/share/perl5/Mojo/DOM/CSS.pm line 237
> # Mojo::DOM::CSS::_pc(qr((?:^|:)class$)u,
> qr((?:^|\s+)transaction(?:\s+|$))u, ARRAY(0x55e050a066e0),
> ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0)) called at
> /usr/share/perl5/Mojo/DOM/CSS.pm line 291
> # Mojo::DOM::CSS::_selector(ARRAY(0x55e0510b0c78), ARRAY(0x55e050a066e0),
> ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0)) called at
> /usr/share/perl5/Mojo/DOM/CSS.pm line 61
> # Mojo::DOM::CSS::_combinator(ARRAY(0x55e0510b2a70), ARRAY(0x55e050a066e0),
> ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0), 2) called at
> /usr/share/perl5/Mojo/DOM/CSS.pm line 34
> # Mojo::DOM::CSS::_ancestor(ARRAY(0x55e0510b2a70), ARRAY(0x55e0510a9cc0),
> ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0), 0, 2) called at
> /usr/share/perl5/Mojo/DOM/CSS.pm line 75
> # Mojo::DOM::CSS::_combinator(ARRAY(0x55e0510b2a70), ARRAY(0x55e0510a9cc0),
> ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0), 0) called at
> /usr/share/perl5/Mojo/DOM/CSS.pm line 172
> # Mojo::DOM::CSS::_match(ARRAY(0x55e0510b2038), ARRAY(0x55e0510a9cc0),
> ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0)) called at
> /usr/share/perl5/Mojo/DOM/CSS.pm line 266
> # Mojo::DOM::CSS::_select(1, ARRAY(0x55e050a066e0), ARRAY(0x55e0510b2038))
> called at /usr/share/perl5/Mojo/DOM/CSS.pm line 26
> # Mojo::DOM::CSS::select_one(Mojo::DOM::CSS=HASH(0x55e0510b0c00),
> ".transaction.people .description") called at /usr/share/perl5/Mojo/DOM.pm
> line 27
> # Mojo::DOM::at(Mojo::DOM=REF(0x55e050aab360), ".transaction.people
> .description") called at t/web/ticket_owner.t line 393
> #
> # Some tests failed or we bailed out, tmp directory
> '/<>/t/tmp/web-ticket_owner.t-pLaG9Zs3' is not cleaned
> # Tests were run but no plan was declared and done_testing() was not seen.
> # Looks like your test exited with 255 just after 98.
> t/web/ticket_owner.t ...
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 1/98 subtests
>
> Almost certainly triggered by the recent uploads of libmojolicious-perl.
> It happens with both 8.55+dfsg-1 (sid) and 8.54+dfsg-1 (bullseye).
Confirmed it doesn't happen with 8.53. Forwarded upstream.
Processed: bug 963387 is forwarded to https://rt.bestpractical.com/Ticket/Display.html?id=36426
Processing commands for cont...@bugs.debian.org: > forwarded 963387 https://rt.bestpractical.com/Ticket/Display.html?id=36426 Bug #963387 [src:request-tracker4] request-tracker4: FTBFS with newer libmojolicious-perl: t/web/ticket_owner.t Set Bug forwarded-to-address to 'https://rt.bestpractical.com/Ticket/Display.html?id=36426'. > thanks Stopping processing here. Please contact me if you need assistance. -- 963387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932749: marked as pending in eclipselink
Control: tag -1 pending Hello, Bug #932749 in eclipselink reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/eclipselink/-/commit/4e33fe7d9d6504251a9d9cf713e93da0856cff40 Include the embedded libraries in eclipselink.jar (Closes: #932749) (this message was generated automatically) -- Greetings https://bugs.debian.org/932749
Bug#938605: marked as done (svgtune: Python2 removal in sid/bullseye)
Your message dated Mon, 22 Jun 2020 22:48:37 + with message-id and subject line Bug#938605: fixed in svgtune 0.3.0-2 has caused the Debian Bug report #938605, regarding svgtune: Python2 removal in sid/bullseye 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.) -- 938605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:svgtune Version: 0.2.0-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:svgtune If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: svgtune Source-Version: 0.3.0-2 Done: Yaroslav Halchenko We believe that the bug you reported is fixed in the latest version of svgtune, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yaroslav Halchenko (supplier of updated svgtune 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, 22 Jun 2020 11:05:03 -0400 Source: svgtune Architecture: source Version: 0.3.0-2 Distribution: unstable Urgency: medium Maintainer: Yaroslav Halchenko Changed-By: Yaroslav Halchenko Closes: 938605 Changes: svgtune (0.3.0-2) unstable; urgency=medium . * Completely remove mentioning of python (not python3) in debian/control (Closes: #938605) Checksums-Sha1: c1f49fb0af0d99e8236d6372847ca6011d325d99 1829 svgtune_0.3.0-2.dsc b52ba69a7ab3feb1791d216bb1bf00943b5b377a 1965 svgtune_0.3.0-2.diff.gz f36c46823af93adad473737617b19f48b987 5914 svgtune_0.3.0-2_source.buildinfo Checksums-Sha256: c008fcf6f51b72a9ebfc8f73017b5a91898842079dcbb800b688b72b9d7fb86d 1829 svgtune_0.3.0-2.dsc 3be801f1c546c1e9fcee1895a37daabb024db9f051c2861ef79d0fe728c77d66 1965 svgtune_0.3.0-2.diff.gz 423bdcd4d9f828a7ea9c884a14d67c395fc29fd6d7be7328ed45119a43d0731f 5914 svgtune_0.3.0-2_source.buildinfo Files: d1a6657c2d327a74abd67e5834b463b5 1829
Processed: Re: [request-tracker-maintainers] Bug#963387: request-tracker4: FTBFS: CORE missing dependencies: Plack::Handler::Starlet ...MISSING
Processing control commands: > retitle -1 request-tracker4: FTBFS with newer libmojolicious-perl: > t/web/ticket_owner.t Bug #963387 [src:request-tracker4] request-tracker4: FTBFS: CORE missing dependencies: Plack::Handler::Starlet ...MISSING Changed Bug title to 'request-tracker4: FTBFS with newer libmojolicious-perl: t/web/ticket_owner.t' from 'request-tracker4: FTBFS: CORE missing dependencies: Plack::Handler::Starlet ...MISSING'. > tags -1 + confirmed Bug #963387 [src:request-tracker4] request-tracker4: FTBFS with newer libmojolicious-perl: t/web/ticket_owner.t Added tag(s) confirmed. -- 963387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963387: [request-tracker-maintainers] Bug#963387: request-tracker4: FTBFS: CORE missing dependencies: Plack::Handler::Starlet ...MISSING
Control: retitle -1 request-tracker4: FTBFS with newer libmojolicious-perl:
t/web/ticket_owner.t
Control: tags -1 + confirmed
On Sun, Jun 21, 2020 at 10:34:37PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
...
> > SOME DEPENDENCIES WERE MISSING.
> > MAILGATE missing dependencies:
> > Mozilla::CA ...MISSING
> > CORE missing dependencies:
> > Plack::Handler::Starlet ...MISSING
> >
> > Perl library path for /usr/bin/perl:
> > /etc/perl
> > /usr/local/lib/x86_64-linux-gnu/perl/5.30.3
> > /usr/local/share/perl/5.30.3
> > /usr/lib/x86_64-linux-gnu/perl5/5.30
> > /usr/share/perl5
> > /usr/lib/x86_64-linux-gnu/perl-base
> > /usr/lib/x86_64-linux-gnu/perl/5.30
> > /usr/share/perl/5.30
> > /usr/local/lib/site_perl
> > make[1]: *** [Makefile:272: testdeps] Error 1
This was not the problem (the immediately following lines are):
make[1]: Leaving directory '/<>'
make: [debian/rules:38: build-stamp] Error 2 (ignored)
> The full build log is available from:
>http://qa-logs.debian.net/2020/06/20/request-tracker4_4.4.4-1_unstable.log
The actual error is:
Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm line 237.
Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm line 237.
# Failed test 'no warnings'
# at /usr/share/perl/5.30/Test/Builder.pm line 152.
# There were 1 warning(s)
# Previous test 95 'Ticket -> Reply'
# Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm line 237.
# at /usr/share/perl5/Log/Dispatch/Perl.pm line 86.
# Log::Dispatch::Perl::__ANON__("Not an ARRAY reference at
/usr/share/perl5/Mojo/DOM/CSS.pm li"...) called at
/usr/share/perl5/Log/Dispatch/Output.pm line 64
#
Log::Dispatch::Output::_log_with_num(Log::Dispatch::Perl=HASH(0x55e04f914d00),
5, "message", "Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm
li"..., "level", "critical") called at /usr/share/perl5/Log/Dispatch.pm line 170
# Log::Dispatch::_log_with_num(Log::Dispatch=HASH(0x55e04f8d43b8), 5,
"level", "critical", "message", "Not an ARRAY reference at
/usr/share/perl5/Mojo/DOM/CSS.pm li"...) called at
/usr/share/perl5/Log/Dispatch.pm line 25
# Log::Dispatch::__ANON__(Log::Dispatch=HASH(0x55e04f8d43b8), "Not an ARRAY
reference at /usr/share/perl5/Mojo/DOM/CSS.pm li"...) called at
/<>/lib/RT.pm line 408
# RT::__ANON__("Not an ARRAY reference at /usr/share/perl5/Mojo/DOM/CSS.pm
li"...) called at /usr/share/perl5/Mojo/DOM/CSS.pm line 237
# Mojo::DOM::CSS::_pc(qr((?:^|:)class$)u, qr((?:^|\s+)transaction(?:\s+|$))u,
ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0)) called at
/usr/share/perl5/Mojo/DOM/CSS.pm line 291
# Mojo::DOM::CSS::_selector(ARRAY(0x55e0510b0c78), ARRAY(0x55e050a066e0),
ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0)) called at
/usr/share/perl5/Mojo/DOM/CSS.pm line 61
# Mojo::DOM::CSS::_combinator(ARRAY(0x55e0510b2a70), ARRAY(0x55e050a066e0),
ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0), 2) called at
/usr/share/perl5/Mojo/DOM/CSS.pm line 34
# Mojo::DOM::CSS::_ancestor(ARRAY(0x55e0510b2a70), ARRAY(0x55e0510a9cc0),
ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0), 0, 2) called at
/usr/share/perl5/Mojo/DOM/CSS.pm line 75
# Mojo::DOM::CSS::_combinator(ARRAY(0x55e0510b2a70), ARRAY(0x55e0510a9cc0),
ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0), 0) called at
/usr/share/perl5/Mojo/DOM/CSS.pm line 172
# Mojo::DOM::CSS::_match(ARRAY(0x55e0510b2038), ARRAY(0x55e0510a9cc0),
ARRAY(0x55e050a066e0), ARRAY(0x55e050a066e0)) called at
/usr/share/perl5/Mojo/DOM/CSS.pm line 266
# Mojo::DOM::CSS::_select(1, ARRAY(0x55e050a066e0), ARRAY(0x55e0510b2038))
called at /usr/share/perl5/Mojo/DOM/CSS.pm line 26
# Mojo::DOM::CSS::select_one(Mojo::DOM::CSS=HASH(0x55e0510b0c00),
".transaction.people .description") called at /usr/share/perl5/Mojo/DOM.pm line
27
# Mojo::DOM::at(Mojo::DOM=REF(0x55e050aab360), ".transaction.people
.description") called at t/web/ticket_owner.t line 393
#
# Some tests failed or we bailed out, tmp directory
'/<>/t/tmp/web-ticket_owner.t-pLaG9Zs3' is not cleaned
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 98.
t/web/ticket_owner.t ...
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 1/98 subtests
Almost certainly triggered by the recent uploads of libmojolicious-perl.
It happens with both 8.55+dfsg-1 (sid) and 8.54+dfsg-1 (bullseye).
Processed: affects 963353
Processing commands for cont...@bugs.debian.org:
> affects 963353 = src:mcl
Bug #963353 {Done: Alastair McKinstry } [mcl]
bsdmainutils must depend on bsdextrautils
Removed indication that 963353 affects src:mp3info, src:calc, src:ocp,
src:sendmail, src:apcupsd, src:glhack, src:slashem, src:latex2rtf, src:ding,
src:zsh, src:console-setup, src:re2c, src:loadlin, src:xcolorsel, src:libdap,
src:vmem, src:wiki2beamer, src:conky, src:libstorj, src:hub, src:pbuilder,
src:xterm, and src:man-db
Added indication that 963353 affects src:mcl
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#949196: libzypp: diff for NMU version 17.7.0-1.1
Hi, Am Montag, 22. Juni 2020 schrieb Giovanni Mascellani: > Hi, > > Il 20/06/20 19:01, Mike Gabriel ha scritto: > > Thanks for patching libzypp. Your NMU is ok, I will include your > > .debdiff on its VCS. In fact, I am considering orphaning libzypp and > > zypper in Debian. Do you have interest in taking over? > > Ugh, I just realized I stupidly embedded the amd64 architecture in my > patch, leading to obvious FTBFS on the other archs. It is ok for you if > I directly NMU libzypp replacing x86_64-linux-gnu with > $(DEB_HOST_MULTIARCH)? yes, please. Mike -- Gesendet von meinem Fairphone (powered by SailfishOS)
Processed (with 1 error): affects 963349, affects 966353, affects 963427
Processing commands for cont...@bugs.debian.org:
> affects 963349 - src:latex2rtf
Bug #963349 {Done: Michael Meskes } [libdap] bsdmainutils
must depend on bsdextrautils
Removed indication that 963349 affects src:latex2rtf
> affects 966353 - src:latex2rtf
Failed to mark 966353 as affecting package(s): Unable to read any bugs
successfully.
> affects 963427 - src:latex2rtf
Bug #963427 {Done: Roland Rosenfeld } [ding] bsdmainutils
must depend on bsdextrautils
Removed indication that 963427 affects src:latex2rtf
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349
963427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#963414: marked as done (latex2rtf: FTBFS: man: can't execute col: No such file or directory)
Your message dated Mon, 22 Jun 2020 16:58:17 -0400
with message-id <20200622205817.ga811...@home.cnlawrence.com>
and subject line Ugh
has caused the Debian Bug report #963414,
regarding latex2rtf: FTBFS: man: can't execute col: No such file or directory
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: latex2rtf
Version: 2.3.16-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> makeinfo latex2rtf
> chmod 644 latex2rtf.info
> texi2pdf latex2rtf.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.)
> [1{/var/lib/texmf/fonts/map/pdftex/updmap
> /pdftex.map}] [2] Chapter 1
> Cross reference values unknown; you must run TeX again.
> Writing index file latex2rtf.cp
> Chapter 2 [1] [2] [3] [4] [5] [6] Chapter 3 [7] [8] [9] [10] [11] [12] [13]
> Chapter 4 [14] [15] [16] [17] [18] Chapter 5 [19] [20] [21] [22] [23]
> Chapter 6 [24] Chapter 7 [25] [26] Chapter 8 [27] [28] [29]
> Writing index file latex2rtf.fn
> [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44]
> [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] Chapter 9 [56]
> No file latex2rtf.fns.
> Chapter 10 [57] [58]
> No file latex2rtf.cps.
> [59] [60] (/<>/doc/latex2rtf.toc [-1])
> [-2] (/<>/doc/latex2rtf.toc)
> (/<>/doc/latex2rtf.toc) ) ve/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> mf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> st/fonts/type1/public/amsfonts/cm/cmmi10.pfb> ts/type1/public/amsfonts/cm/cmmi12.pfb> e1/public/amsfonts/cm/cmmi7.pfb> ic/amsfonts/cm/cmr10.pfb> onts/cm/cmr9.pfb> cmsy10.pfb> .pfb>
> Output written on latex2rtf.pdf (64 pages, 221371 bytes).
> Transcript written on latex2rtf.log.
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.)
> [1{/var/lib/texmf/fonts/map/pdftex/updmap
> /pdftex.map}] [2] Chapter 1
> (/<>/doc/latex2rtf.aux)
> Writing index file latex2rtf.cp
> Chapter 2 [1] [2] [3] [4] [5] [6] Chapter 3 [7] [8] [9] [10] [11] [12] [13]
> Chapter 4 [14] [15] [16] [17] [18] Chapter 5 [19] [20] [21] [22] [23]
> Chapter 6 [24] Chapter 7 [25] [26] Chapter 8 [27] [28] [29]
> Writing index file latex2rtf.fn
> [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44]
> [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] Chapter 9 [56]
> (/<>/doc/latex2rtf.fns [57] [58] [59]
> [60] [61] [62] [63]) Chapter 10 [64]
> (/<>/doc/latex2rtf.cps) [65] [66]
> (/<>/doc/latex2rtf.toc [-1]) [-2]
> (/<>/doc/latex2rtf.toc)
> (/<>/doc/latex2rtf.toc) ) ve/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> mf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> st/fonts/type1/public/amsfonts/cm/cmmi10.pfb> ts/type1/public/amsfonts/cm/cmmi12.pfb> e1/public/amsfonts/cm/cmmi7.pfb> ic/amsfonts/cm/cmmi9.pfb> onts/cm/cmr10.pfb> /cmr9.pfb> pfb> usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmtt12.pfb> are/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmtt9.pfb>
> Output written on latex2rtf.pdf (70 pages, 307880 bytes).
> Transcript written on latex2rtf.log.
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references,
Processed: affects 963414, reassign 963414 to latex2rtf
Processing commands for cont...@bugs.debian.org: > affects 963414 = latex2rtf Bug #963414 [bsdmainutils] latex2rtf: FTBFS: man: can't execute col: No such file or directory Removed indication that 963414 affects src:latex2rtf, src:hub, src:libstorj, src:mcl, src:ocp, src:console-setup, src:conky, src:loadlin, src:slashem, src:calc, src:mp3info, src:apcupsd, src:re2c, src:xcolorsel, src:pbuilder, src:zsh, src:ding, src:man-db, src:glhack, src:libdap, src:sendmail, src:vmem, src:wiki2beamer, and src:xterm Added indication that 963414 affects latex2rtf > reassign 963414 latex2rtf Bug #963414 [bsdmainutils] latex2rtf: FTBFS: man: can't execute col: No such file or directory Bug reassigned from package 'bsdmainutils' to 'latex2rtf'. No longer marked as found in versions bsdmainutils/12.1.1. No longer marked as fixed in versions 2.3.18-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
On Mon, Jun 22, 2020 at 09:18:59PM +0100, Colin Watson wrote: > I'm going to upload man-db with a dependency on bsdextrautils | > bsdmainutils (<< 12.1.1~) shortly. (There's been a bit of a delay > because of some unrelated po4a-induced breakage that I had to stop and > fix upstream first.) Done (man-db 2.9.3-1). -- Colin Watson (he/him) [cjwat...@debian.org]
Processed: unblock 963158 with 963414
Processing commands for cont...@bugs.debian.org: > unblock 963158 with 963414 Bug #963158 [src:re2c] re2c: CVE-2020-11958 963158 was blocked by: 963372 963327 963377 963376 963383 963448 963395 963349 963378 963361 963365 963359 963375 963355 963306 963451 963442 963414 963413 963403 963350 963158 was not blocking any bugs. Removed blocking bug(s) of 963158: 963414 > thanks Stopping processing here. Please contact me if you need assistance. -- 963158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963441: marked as done (capstats: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2)
Your message dated Mon, 22 Jun 2020 21:04:39 + with message-id and subject line Bug#963441: fixed in capstats 0.28-3 has caused the Debian Bug report #963441, regarding capstats: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 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.) -- 963441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: capstats Version: 0.28-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > debian/rules:7: *** missing separator. Stop. > dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned > exit status 2 > > Build finished at 2020-06-21T07:28:29Z The full build log is available from: http://qa-logs.debian.net/2020/06/20/capstats_0.28-2_unstable.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: capstats Source-Version: 0.28-3 Done: Hilko Bengen We believe that the bug you reported is fixed in the latest version of capstats, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated capstats 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, 22 Jun 2020 22:42:49 +0200 Source: capstats Architecture: source Version: 0.28-3 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Closes: 963441 Changes: capstats (0.28-3) unstable; urgency=medium . * Remove git merge artifacts from debian/rules (Closes: #963441) Checksums-Sha1: a99f3eee8323d0a1f10e7eb6f136167c2fe9dc5b 2108 capstats_0.28-3.dsc 25147c6cff377de661414dc50218af485d2b8c4c 13244 capstats_0.28-3.debian.tar.xz 6bc1a39a06660bd5364287891f0d650193515a9d 6657 capstats_0.28-3_source.buildinfo Checksums-Sha256: 90b84bc1532c1a6bc0b2da697310fcb6ae09a8319ac2f72c396823d12f44e5ba 2108 capstats_0.28-3.dsc 695182f78cc3fd77b6cd856deb576a2bea42b6eecc2317f7f4cd50d070abce6d 13244 capstats_0.28-3.debian.tar.xz 69b3c12689fe8a48f10fce6ac579e79fb3ffd0d2acc76c7a1b234b832a16636a 6657 capstats_0.28-3_source.buildinfo Files: cd4c6d751e2458942f6d680a851fe51b 2108 net optional capstats_0.28-3.dsc 29d17a25b946abba1971806d8059fbb4 13244 net optional capstats_0.28-3.debian.tar.xz ec4b3b1ae7d6b09066db0a3a7abdccb9 6657 net optional capstats_0.28-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl7xGEISHGJlbmdlbkBk ZWJpYW4ub3JnAAoJEHW3EGNcITp+5EcP/1U3nuWqX27LhPwWUPWLoymdHMTXD6h6 7tmApTj9crX7b48R0mPxM/GF/zYcUqDSTfsd+98+WBFgmCN83ZezI0TqlGUJI1F6 cR9jOOwZqSCUlnJ9PjsiwKP/jYPgprrsssUrVuRlEGQhDs4Z6JdR/XJskGRLxyGJ P+2Aj0C/hS77EFijEl2ok11sKLiW5fNFc1UC3FXYpq02gnTEORw/mzQuLPyAb/FT pqTzSveI7iApcNNxGFdeaLFLraLlKqv7ueyhlJfhB7nCGPwiiVIm7hB+8LibzB15 rioOQLu04vmOT7o6Tiiny687PuHyE1RaipTgfVIu+4C8cjAAeZBHq6yOHS5+/Vfe GJdzPNPxKc9vIxfVg+ELm0E0J5E3zgkOV7/xjcu7OB1UWeOYrQH3RoVEoZUQjWWS BKFTBJdfFDRVi5l7gd3Ww73EK9PME0pY7Td0m2sJFrZWByYe6Tgm3UIUxhld2frl BGsnbDaUTTBtsDfWwjmPRPv7P8oRGWy8LdC61Q525drW0m4Nv29upVWktQLY7C1x OTxxicXqBJuUHqML+v3FVR0qFektbpIao5hgkHUpLLCW4grKP7b1y7S/FABUoDw5 Rdfq/K9ev+p8axYcrX66iDIPuj2jYxfkYRx+NDpf/6yYKjU5l/QWPpEi1ktoAlQy MgkPt65Gs3z3 =g63Y -END PGP SIGNATURE End Message ---
Bug#941557: marked as done (gri: texi file need @documentencoding)
Your message dated Mon, 22 Jun 2020 21:00:09 + with message-id and subject line Bug#941557: fixed in gri 2.12.26-6 has caused the Debian Bug report #941557, regarding gri: texi file need @documentencoding 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.) -- 941557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gri Version: 2.12.26-1 Severity: serious Justification: FTBFS User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan Hi Peter, The gri package appears to fail to build from source in unstable: [...] cd tst_suite ; make make[2]: Entering directory '/tmp/gri-2.12.26/doc/tst_suite' perl ./../gri2html tst_IO.gri tst_IO.html perl ./../gri2html tst_control.gri tst_control.html perl ./../gri2html tst_rpn.gri tst_rpn.html perl ./../gri2html tst_var_syn.gri tst_var_syn.html make[2]: Leaving directory '/tmp/gri-2.12.26/doc/tst_suite' makeinfo -I. gri.texi utf8 "\xF3" does not map to Unicode at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796, line 19280. Malformed UTF-8 character: \xf3\x70\x65\x7a (unexpected non-continuation byte 0x70, immediately after start byte 0xf3; need 4 bytes, got 1) in pattern match (m//) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. make[1]: *** [Makefile:975: html] Error 25 make[1]: Leaving directory '/tmp/gri-2.12.26/doc' make: *** [debian/rules:83: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -b failed [...] -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: gri Source-Version: 2.12.26-6 Done: Peter S Galbraith We believe that the bug you reported is fixed in the latest version of gri, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter S Galbraith (supplier of updated gri 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: SHA512 Format: 1.8 Date: Fri, 19 Jun 2020 15:13:49 -0400 Source: gri Binary: gri gri-dbgsym gri-el gri-html-doc gri-pdf-doc Architecture: source amd64 all Version: 2.12.26-6 Distribution: unstable Urgency: medium Maintainer: Peter S Galbraith Changed-By: Peter S Galbraith Description: gri- a language for scientific illustration gri-el - Emacs major-mode for gri, a language for scientific graphics gri-html-doc - HTML manual for gri, a language for scientific graphics gri-pdf-doc - PostScript manual for gri, a language for scientific graphics Closes: 901179 932949 941557 Changes: gri (2.12.26-6) unstable; urgency=medium . * Apologies for having being MIA. * Bug fix: gri build-depends on cruft package, thanks to peter green for reporting and to Steve Langasek for the patch (Closes: #932949) * Bug fix: Encoding must now be specified in texinfo source, thanks to Steve Langasek for reporting and to Sebastiaan Couwenberg for the patch (Closes: #941557) * Bug fix: FTCBFS: Let dh_auto_configure pass --host to ./configure, thanks to Helmut Grohne for reporting and for the patch (Closes: #901179) * Deleted debian/compat and replace debhelper (>= 7) with debhelper-compat (= 12) in Build-Depends. * debian/rules: added dh_autoreconf and dh_autoreconf_clean implemented at Standards-Versions 4.0.0 * debian/control: Standards-Version: 4.5.0 * debian/copyright: updated to GPL-3. Can't believe I had to wait a month in the NEW queue to get rejected for this. :-( Checksums-Sha1: e471d173585d17ac3a7afc50cd5d57f66433f530 1984 gri_2.12.26-6.dsc 74ce0894e0831d5a6efc4aec3ab317206fe0 22420
Bug#932949: marked as done (gri build-depends on cruft package.)
Your message dated Mon, 22 Jun 2020 21:00:09 + with message-id and subject line Bug#932949: fixed in gri 2.12.26-6 has caused the Debian Bug report #932949, regarding gri build-depends on cruft package. 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.) -- 932949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gri Version: 3.5.2-1 Tags: bullseye, sid, patch Severity: serious gri build-depends on texlive-generic-reccomended which is no longer built by the texlive-base source package. Please build-depend on texlive-plain-generic instead. --- End Message --- --- Begin Message --- Source: gri Source-Version: 2.12.26-6 Done: Peter S Galbraith We believe that the bug you reported is fixed in the latest version of gri, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter S Galbraith (supplier of updated gri 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: SHA512 Format: 1.8 Date: Fri, 19 Jun 2020 15:13:49 -0400 Source: gri Binary: gri gri-dbgsym gri-el gri-html-doc gri-pdf-doc Architecture: source amd64 all Version: 2.12.26-6 Distribution: unstable Urgency: medium Maintainer: Peter S Galbraith Changed-By: Peter S Galbraith Description: gri- a language for scientific illustration gri-el - Emacs major-mode for gri, a language for scientific graphics gri-html-doc - HTML manual for gri, a language for scientific graphics gri-pdf-doc - PostScript manual for gri, a language for scientific graphics Closes: 901179 932949 941557 Changes: gri (2.12.26-6) unstable; urgency=medium . * Apologies for having being MIA. * Bug fix: gri build-depends on cruft package, thanks to peter green for reporting and to Steve Langasek for the patch (Closes: #932949) * Bug fix: Encoding must now be specified in texinfo source, thanks to Steve Langasek for reporting and to Sebastiaan Couwenberg for the patch (Closes: #941557) * Bug fix: FTCBFS: Let dh_auto_configure pass --host to ./configure, thanks to Helmut Grohne for reporting and for the patch (Closes: #901179) * Deleted debian/compat and replace debhelper (>= 7) with debhelper-compat (= 12) in Build-Depends. * debian/rules: added dh_autoreconf and dh_autoreconf_clean implemented at Standards-Versions 4.0.0 * debian/control: Standards-Version: 4.5.0 * debian/copyright: updated to GPL-3. Can't believe I had to wait a month in the NEW queue to get rejected for this. :-( Checksums-Sha1: e471d173585d17ac3a7afc50cd5d57f66433f530 1984 gri_2.12.26-6.dsc 74ce0894e0831d5a6efc4aec3ab317206fe0 22420 gri_2.12.26-6.debian.tar.xz eab0c5098e24082cac5685d0150c2f366c7b8fde 36516 gri-dbgsym_2.12.26-6_amd64.deb 1a4d3b971a14698976a45c00d9a2e654cc58cf83 65056 gri-el_2.12.26-6_all.deb 94e9360d4865d3a6aaf48c30588f34c9f665dd86 956852 gri-html-doc_2.12.26-6_all.deb 07bd783d362d7dc3eaae7e15759711b7e7a48de1 1620572 gri-pdf-doc_2.12.26-6_all.deb 1db40cf1d3cd740b08e5866e74b7f9c1aa3db9c4 10554 gri_2.12.26-6_amd64.buildinfo b356ce5b3aed58aa338fb11ed705e3dd52688a16 642000 gri_2.12.26-6_amd64.deb Checksums-Sha256: 8be653b8124eead2a5976fd52d113f61bfd9816a77b054fbd15ed1ab278a0b95 1984 gri_2.12.26-6.dsc 0d4e33d7d17303658dbc82d61f1c62fe95f8e9a3d819069c08a687be39303404 22420 gri_2.12.26-6.debian.tar.xz 91c8b472e69ab1120ff32e5b89a0ce4031b22149580b555a0fa9a2b93db77d5d 36516 gri-dbgsym_2.12.26-6_amd64.deb 3f6d4a5daeb9fd59c616efad4fddd0358a435d36750ef248f89249009272b79c 65056 gri-el_2.12.26-6_all.deb b59a2e39ac29301c94cb15e456838253b967d94cce3a291c979a2fd6c828e854 956852 gri-html-doc_2.12.26-6_all.deb 1b3d701b3689eb807296de6a00b596d02aa88dc46976f155785d5b16689399f2 1620572 gri-pdf-doc_2.12.26-6_all.deb 37ac797265bebb3f9986a4137dab3f309db3618ba7e9835fe1909edcb2423ec1 10554 gri_2.12.26-6_amd64.buildinfo 628d014cba70e20d8b24cafe18ec26255abe1e41d36da0750fab6e57e2d1aa58 642000 gri_2.12.26-6_amd64.deb Files: e2eccfd003415ddb27c600ca4706491e 1984 science optional gri_2.12.26-6.dsc
Bug#949150: marked as done (gri: texi file need @documentencoding)
Your message dated Mon, 22 Jun 2020 21:00:09 + with message-id and subject line Bug#941557: fixed in gri 2.12.26-6 has caused the Debian Bug report #941557, regarding gri: texi file need @documentencoding 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.) -- 941557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gri Version: 2.12.26-1 Severity: serious Tags: ftbfs Justification: makes the package in question unusable or mostly so Dear Maintainer, In preparation of the netcdf transition as test rebuild of your package was done which FTBFS: makeinfo -I. gri.texi utf8 "\xF3" does not map to Unicode at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796, line 19280. Malformed UTF-8 character: \xf3\x70\x65\x7a (unexpected non-continuation byte 0x70, immediately after start byte 0xf3; need 4 bytes, got 1) in pattern match (m//) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. make[1]: *** [Makefile:975: html] Error 25 Kind Regards, Bas --- End Message --- --- Begin Message --- Source: gri Source-Version: 2.12.26-6 Done: Peter S Galbraith We believe that the bug you reported is fixed in the latest version of gri, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter S Galbraith (supplier of updated gri 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: SHA512 Format: 1.8 Date: Fri, 19 Jun 2020 15:13:49 -0400 Source: gri Binary: gri gri-dbgsym gri-el gri-html-doc gri-pdf-doc Architecture: source amd64 all Version: 2.12.26-6 Distribution: unstable Urgency: medium Maintainer: Peter S Galbraith Changed-By: Peter S Galbraith Description: gri- a language for scientific illustration gri-el - Emacs major-mode for gri, a language for scientific graphics gri-html-doc - HTML manual for gri, a language for scientific graphics gri-pdf-doc - PostScript manual for gri, a language for scientific graphics Closes: 901179 932949 941557 Changes: gri (2.12.26-6) unstable; urgency=medium . * Apologies for having being MIA. * Bug fix: gri build-depends on cruft package, thanks to peter green for reporting and to Steve Langasek for the patch (Closes: #932949) * Bug fix: Encoding must now be specified in texinfo source, thanks to Steve Langasek for reporting and to Sebastiaan Couwenberg for the patch (Closes: #941557) * Bug fix: FTCBFS: Let dh_auto_configure pass --host to ./configure, thanks to Helmut Grohne for reporting and for the patch (Closes: #901179) * Deleted debian/compat and replace debhelper (>= 7) with debhelper-compat (= 12) in Build-Depends. * debian/rules: added dh_autoreconf and dh_autoreconf_clean implemented at Standards-Versions 4.0.0 * debian/control: Standards-Version: 4.5.0 * debian/copyright: updated to GPL-3. Can't believe I had to wait a month in the NEW queue to get rejected for this. :-( Checksums-Sha1: e471d173585d17ac3a7afc50cd5d57f66433f530 1984 gri_2.12.26-6.dsc 74ce0894e0831d5a6efc4aec3ab317206fe0 22420 gri_2.12.26-6.debian.tar.xz eab0c5098e24082cac5685d0150c2f366c7b8fde 36516 gri-dbgsym_2.12.26-6_amd64.deb 1a4d3b971a14698976a45c00d9a2e654cc58cf83 65056 gri-el_2.12.26-6_all.deb 94e9360d4865d3a6aaf48c30588f34c9f665dd86 956852 gri-html-doc_2.12.26-6_all.deb 07bd783d362d7dc3eaae7e15759711b7e7a48de1 1620572 gri-pdf-doc_2.12.26-6_all.deb 1db40cf1d3cd740b08e5866e74b7f9c1aa3db9c4 10554 gri_2.12.26-6_amd64.buildinfo b356ce5b3aed58aa338fb11ed705e3dd52688a16 642000 gri_2.12.26-6_amd64.deb Checksums-Sha256: 8be653b8124eead2a5976fd52d113f61bfd9816a77b054fbd15ed1ab278a0b95 1984 gri_2.12.26-6.dsc 0d4e33d7d17303658dbc82d61f1c62fe95f8e9a3d819069c08a687be39303404 22420 gri_2.12.26-6.debian.tar.xz 91c8b472e69ab1120ff32e5b89a0ce4031b22149580b555a0fa9a2b93db77d5d 36516 gri-dbgsym_2.12.26-6_amd64.deb 3f6d4a5daeb9fd59c616efad4fddd0358a435d36750ef248f89249009272b79c 65056 gri-el_2.12.26-6_all.deb
Processed: fixed 963414 in 2.3.18-1
Processing commands for cont...@bugs.debian.org: > fixed 963414 2.3.18-1 Bug #963414 [bsdmainutils] latex2rtf: FTBFS: man: can't execute col: No such file or directory There is no source info for the package 'bsdmainutils' at version '2.3.18-1' with architecture '' Unable to make a source version for version '2.3.18-1' Marked as fixed in versions 2.3.18-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 963306
Processing commands for cont...@bugs.debian.org: > affects 963306 - src:latex2rtf Bug #963306 [bsdmainutils] re2c: FTBFS: src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token Bug #963327 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963350 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963355 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963359 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963361 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963365 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963372 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963375 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963376 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963377 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963378 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963383 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963403 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963413 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963442 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963448 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963451 [bsdmainutils] bsdmainutils must depend on bsdextrautils Removed indication that 963306 affects src:latex2rtf Removed indication that 963327 affects src:latex2rtf Removed indication that 963350 affects src:latex2rtf Removed indication that 963355 affects src:latex2rtf Removed indication that 963359 affects src:latex2rtf Removed indication that 963361 affects src:latex2rtf Removed indication that 963365 affects src:latex2rtf Removed indication that 963372 affects src:latex2rtf Removed indication that 963375 affects src:latex2rtf Removed indication that 963376 affects src:latex2rtf Removed indication that 963377 affects src:latex2rtf Removed indication that 963378 affects src:latex2rtf Removed indication that 963383 affects src:latex2rtf Removed indication that 963395 affects src:latex2rtf Removed indication that 963403 affects src:latex2rtf Removed indication that 963413 affects src:latex2rtf Removed indication that 963442 affects src:latex2rtf Removed indication that 963448 affects src:latex2rtf Removed indication that 963451 affects src:latex2rtf > thanks Stopping processing here. Please contact me if you need assistance. -- 963306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963306 963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327 963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350 963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355 963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359 963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361 963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375 963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376 963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377 963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378 963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383 963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395 963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403 963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413 963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442 963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 963414 to latex2rtf: FTBFS: man: can't execute col: No such file or directory
Processing commands for cont...@bugs.debian.org: > retitle 963414 latex2rtf: FTBFS: man: can't execute col: No such file or > directory Bug #963414 [bsdmainutils] bsdmainutils must depend on bsdextrautils Changed Bug title to 'latex2rtf: FTBFS: man: can't execute col: No such file or directory' from 'bsdmainutils must depend on bsdextrautils'. > thanks Stopping processing here. Please contact me if you need assistance. -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unmerging 963414
Processing commands for cont...@bugs.debian.org: > unmerge 963414 Bug #963414 [bsdmainutils] bsdmainutils must depend on bsdextrautils Ignoring request to unmerge a bug which is not merged with any others. > thanks Stopping processing here. Please contact me if you need assistance. -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unmerging 963414
Processing commands for cont...@bugs.debian.org: > unmerge 963414 Bug #963414 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963306 [bsdmainutils] re2c: FTBFS: src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token Bug #963327 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963350 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963355 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963359 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963361 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963365 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963372 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963375 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963376 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963377 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963378 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963383 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963403 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963413 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963442 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963448 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963451 [bsdmainutils] bsdmainutils must depend on bsdextrautils Disconnected #963414 from all other report(s). > thanks Stopping processing here. Please contact me if you need assistance. -- 963306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963306 963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327 963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350 963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355 963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359 963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361 963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375 963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376 963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377 963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378 963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383 963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395 963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403 963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442 963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopening 963451
Processing commands for cont...@bugs.debian.org:
> reopen 963451
Bug #963451 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963306 {Done: Chris Lawrence } [bsdmainutils] re2c:
FTBFS: src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token
Bug #963327 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963350 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963355 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963359 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963361 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963365 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963372 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963375 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963376 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963377 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963378 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963383 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963395 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963403 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963413 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963414 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963442 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug #963448 {Done: Chris Lawrence } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
No longer marked as fixed in versions latex2rtf/2.3.18-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963306
963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327
963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350
963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355
963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359
963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361
963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375
963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376
963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377
963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378
963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383
963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395
963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403
963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442
963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448
963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#963365: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sendmail Version: 8.15.2-19 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc/op' > rm -f op.txt > Note: see README file in case of errors. > pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt > /bin/sh: 1: ul: not found > make[2]: *** [Makefile:30: op.txt] Error 127 The full build log is available from: http://qa-logs.debian.net/2020/06/20/sendmail_8.15.2-19_unstable.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: latex2rtf Source-Version: 2.3.18-1 Done: Chris Lawrence We believe that the bug you reported is fixed in the latest version of latex2rtf, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence (supplier of updated latex2rtf 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 14:31:47 -0400 Source: latex2rtf Architecture: source Version: 2.3.18-1 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence Changed-By: Chris Lawrence Closes: 963414 Changes: latex2rtf (2.3.18-1) unstable; urgency=medium . * New upstream release. * Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414) * Upstream includes the test directory, so we can now drop patches that ignored it. Checksums-Sha1: 6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc 331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz 896ce7750df6ff7d99279ac0c1f9a0817908f640 9621 latex2rtf_2.3.18-1_source.buildinfo Checksums-Sha256: 9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961 latex2rtf_2.3.18-1.dsc c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156 latex2rtf_2.3.18.orig.tar.gz 33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044 latex2rtf_2.3.18-1.debian.tar.xz f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621 latex2rtf_2.3.18-1_source.buildinfo Files: 701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc 4f0110e57de941b9bf67972971e98118 2484156 tex optional latex2rtf_2.3.18.orig.tar.gz b930516bad7ced76a80b0c058f6b030c 27044 tex optional latex2rtf_2.3.18-1.debian.tar.xz 36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional latex2rtf_2.3.18-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM Zs/0GA//Us+7rEr4LaIziCsMLxnbBhU0+3GwGnEfZpXFhSlC/HpYQrHrdS74T9lL cRFjDlQsxc1/Q1+sJ227F55AoPw4ZzXt6D+SCpteRLPEx0YGvcKgZJgrBOu1lm5L 7n+5f2q9t9xboLK6UZfuOTlafNGBApfJ3ZYQmlmCO91RGuLbLjoQU6oP2DcF3uzU 4tGzn20xwodQ0qhBrbmediFfHJMqh+oaR8JNQBJXJfPVGNGFS47ZgtPN7MiQLAXX 2wVR7ywY5Ntxf7E9kRVmXsKlykJyFpmEym6ZMRckt8ZqLUjFvXhorPBG91vTdTwP 0E6Sbib8Hwa5yDKvT1t0Q4j37eKiyGCnoQhxZmTot+ZSVWlZYPKffGQdAalZSkcu f9SA74X2vpp1qd5hsf+XNps3DhmdoC6unYhRoEQhvu7M4LOR4TJNMYTOKOlD7kdM YRSK1sHuIJbYHDH1bA0YhDJQpUK+2IIJZeBnECCoLIqo0RPxO6U1Ut+btct1JIqX c56AtH+PZorvPaSIvbnU3H1H7kyqLkhqphI8EPbX6Im/pgpliDqvyZo5AINkv1Z2 3aIOjoL0OLwf//5WZ9GsU1fFvPbbYrdWQwKHu+0deMIaYmCJuD/XX/KzBEWdty3+
Bug#963395: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: man-db
Version: 2.9.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[6]: Entering directory '/<>/debian/build/src/tests'
> PASS: lexgrog-multiple-whatis
> PASS: lexgrog-backslash-dash-rhs
> PASS: lexgrog-basic
> FAIL: man-deleted-directory
> FAIL: man-executable-page-on-path
> PASS: man-exact-section-matches
> PASS: man-invalid-db-entry
> FAIL: man-language-specific-requests
> FAIL: man-missing-locales
> PASS: man-override-dir
> PASS: man-recode-in-place
> PASS: man-recode-suffix
> PASS: man-symlinks-with-matching-names
> PASS: man-suffixed-extension
> FAIL: man-so-links-same-section
> PASS: manconv-guess-from-encoding
> PASS: manconv-coding-tags
> PASS: manconv-incomplete-char-at-eof
> PASS: mandb-basic
> PASS: mandb-bogus-symlink
> PASS: mandb-cachedir-tag
> PASS: mandb-empty-page
> PASS: manconv-odd-combinations
> PASS: man-mandatory-manpath
> PASS: mandb-symlink-beats-whatis-ref
> PASS: mandb-regular-file-symlink-changes
> FAIL: zsoelim-so-includes
> PASS: mandb-whatis-broken-link-changes
> PASS: whatis-path-to-executable
>
>man-db 2.9.2: src/tests/test-suite.log
>
>
> # TOTAL: 29
> # PASS: 23
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 6
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: man-deleted-directory
> ===
>
> shell-init: error retrieving current directory: getcwd: cannot access parent
> directories: No such file or directory
> chdir: error retrieving current directory: getcwd: cannot access parent
> directories: No such file or directory
> chdir: error retrieving current directory: getcwd: cannot access parent
> directories: No such file or directory
> shell-init: error retrieving current directory: getcwd: cannot access parent
> directories: No such file or directory
> chdir: error retrieving current directory: getcwd: cannot access parent
> directories: No such file or directory
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> FAIL: run from deleted directory
> FAIL man-deleted-directory (exit status: 1)
>
> FAIL: man-executable-page-on-path
> =
>
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> FAIL: executable page on path
> FAIL man-executable-page-on-path (exit status: 1)
>
> FAIL: man-language-specific-requests
>
>
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> --- /tmp/tmp.5jMrP1vAPn/1.exp 2020-06-21 07:28:39.916012778 +
> +++ /tmp/tmp.5jMrP1vAPn/1.out 2020-06-21 07:28:39.928012937 +
> @@ -1,3 +0,0 @@
> -.mso xyzzy.tmac
> -.hla xyzzy
> -test \- xyzzy language page for test
> FAIL: language-specific requests for localized man page
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> --- /tmp/tmp.5jMrP1vAPn/2.exp 2020-06-21 07:28:39.920012831 +
> +++ /tmp/tmp.5jMrP1vAPn/2.out 2020-06-21 07:28:40.208016647 +
> @@ -1,2 +0,0 @@
> -.TH xyz 1
> -test \- top-level xyz page
> FAIL: no language-specific requests for top-level man page
> FAIL man-language-specific-requests (exit status: 1)
>
> FAIL: man-missing-locales
> =
>
> man: can't execute col: No such file or directory
> man: command exited with status 127: LC_CTYPE=C.UTF-8 col -b -p -x | sed -e
> '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> FAIL: missing locales
> FAIL man-missing-locales (exit status: 1)
>
> FAIL: man-so-links-same-section
> ===
>
>
Bug#963378: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xcolorsel Version: 1.1a-22 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall > -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO > -DHELPFILE=\"/usr/lib/X11/xcolorsel/Xcolorsel.help\" -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o RgbText.o RgbText.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from RgbText.c:77: > /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > RgbText.c: In function ‘printfile’: > RgbText.c:549:7: warning: unused variable ‘fd’ [-Wunused-variable] > 549 | FILE *fd; > | ^~ > RgbText.c:545:21: warning: unused variable ‘ptn’ [-Wunused-variable] > 545 | register char *ptr,*ptn; > | ^~~ > RgbText.c: In function ‘query_geometry’: > RgbText.c:883:16: warning: unused variable ‘requested’ [-Wunused-variable] > 883 | XtGeometryMask requested; > |^ > RgbText.c: In function ‘grab_color’: > RgbText.c:1135:8: warning: unused variable ‘mycolor’ [-Wunused-variable] > 1135 | XColor mycolor; > |^~~ > gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall > -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO > -DHELPFILE=\"/usr/lib/X11/xcolorsel/Xcolorsel.help\" -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o RgbSink.o RgbSink.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrinsic.h:53, > from /usr/include/X11/IntrinsicP.h:51, > from RgbSink.c:82: > /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > RgbSink.c: In function ‘mydisp’: > RgbSink.c:191:5: warning: unused variable ‘tile’ [-Wunused-variable] > 191 | int tile,linum; > | ^~~~ > gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall > -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO > -DHELPFILE=\"/usr/lib/X11/xcolorsel/Xcolorsel.help\" -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o RgbSrc.o RgbSrc.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrinsic.h:53, > from /usr/include/X11/IntrinsicP.h:51, > from RgbSrc.c:82: > /usr/include/features.h:185:3:
Bug#963327: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libstorj Version: 1.0.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for hexdump... no > configure: error: hexdump is required for tests > make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2020/06/20/libstorj_1.0.3-1_unstable.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: latex2rtf Source-Version: 2.3.18-1 Done: Chris Lawrence We believe that the bug you reported is fixed in the latest version of latex2rtf, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence (supplier of updated latex2rtf 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 14:31:47 -0400 Source: latex2rtf Architecture: source Version: 2.3.18-1 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence Changed-By: Chris Lawrence Closes: 963414 Changes: latex2rtf (2.3.18-1) unstable; urgency=medium . * New upstream release. * Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414) * Upstream includes the test directory, so we can now drop patches that ignored it. Checksums-Sha1: 6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc 331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz 896ce7750df6ff7d99279ac0c1f9a0817908f640 9621 latex2rtf_2.3.18-1_source.buildinfo Checksums-Sha256: 9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961 latex2rtf_2.3.18-1.dsc c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156 latex2rtf_2.3.18.orig.tar.gz 33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044 latex2rtf_2.3.18-1.debian.tar.xz f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621 latex2rtf_2.3.18-1_source.buildinfo Files: 701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc 4f0110e57de941b9bf67972971e98118 2484156 tex optional latex2rtf_2.3.18.orig.tar.gz b930516bad7ced76a80b0c058f6b030c 27044 tex optional latex2rtf_2.3.18-1.debian.tar.xz 36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional latex2rtf_2.3.18-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM Zs/0GA//Us+7rEr4LaIziCsMLxnbBhU0+3GwGnEfZpXFhSlC/HpYQrHrdS74T9lL cRFjDlQsxc1/Q1+sJ227F55AoPw4ZzXt6D+SCpteRLPEx0YGvcKgZJgrBOu1lm5L 7n+5f2q9t9xboLK6UZfuOTlafNGBApfJ3ZYQmlmCO91RGuLbLjoQU6oP2DcF3uzU 4tGzn20xwodQ0qhBrbmediFfHJMqh+oaR8JNQBJXJfPVGNGFS47ZgtPN7MiQLAXX 2wVR7ywY5Ntxf7E9kRVmXsKlykJyFpmEym6ZMRckt8ZqLUjFvXhorPBG91vTdTwP 0E6Sbib8Hwa5yDKvT1t0Q4j37eKiyGCnoQhxZmTot+ZSVWlZYPKffGQdAalZSkcu f9SA74X2vpp1qd5hsf+XNps3DhmdoC6unYhRoEQhvu7M4LOR4TJNMYTOKOlD7kdM YRSK1sHuIJbYHDH1bA0YhDJQpUK+2IIJZeBnECCoLIqo0RPxO6U1Ut+btct1JIqX
Bug#963355: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocp
Version: 1:0.2.2+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/playsid'
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall -I.././
> sidptype.c -o sidptype.o -c
> sidptype.c: In function ‘sidReadMemInfo’:
> sidptype.c:109:23: warning: passing argument 2 of ‘latin1’ makes integer from
> pointer without a cast [-Wint-conversion]
> 109 | latin1(m->modname, m->modname, strlen(m->modname));
> | ~^
> | |
> | char *
> sidptype.c:52:35: note: expected ‘int’ but argument is of type ‘char *’
>52 | static void latin1(char *dst, int dstlen, char *src)
> | ^~
> sidptype.c:109:34: warning: passing argument 3 of ‘latin1’ makes pointer from
> integer without a cast [-Wint-conversion]
> 109 | latin1(m->modname, m->modname, strlen(m->modname));
> | ^~
> | |
> | size_t {aka long unsigned int}
> sidptype.c:52:49: note: expected ‘char *’ but argument is of type ‘size_t’
> {aka ‘long unsigned int’}
>52 | static void latin1(char *dst, int dstlen, char *src)
> | ~~^~~
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall -I.././ -shared
> -Wl,-z,relro -o sidtype.so sidptype.o
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -fPIC -fPIC -Wall -I.././ cpiinfo.cpp -o
> cpiinfo.o -c
> g++ -std=c++11 -DHAVE_CONFIG_H=1 -DSIDTUNE_NO_STDIN_LOADER=1
> -DPACKAGE_NAME=\"sidplayfp\" -DVERSION=\"2.0.1\"
> -DPACKAGE_VERSION=\"2.0.1-1\" -DPACKAGE_URL=\"\" -I.. -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -fPIC -I./sidplayfp-config
> -I./sidplayfp-git/libsidplayfp/src sidplay.cpp -o sidplay.o -c
> sidplay.cpp:690:2: warning: #warning We can probably REMOVE mixClipAlt2 soon
> globally [-Wcpp]
> 690 | #warning We can probably REMOVE mixClipAlt2 soon globally
> | ^~~
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -fPIC -fPIC -Wall -I.././ -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -fPIC -I./sidplayfp-config
> -I./sidplayfp-git/libsidplayfp/src sidpplay.cpp -o sidpplay.o -c
> sidpplay.cpp:260:2: warning: #warning FIXME, frequency does not take VIC-II
> model / cpu-freqency into account [-Wcpp]
> 260 | #warning FIXME, frequency does not take VIC-II model / cpu-freqency
> into account
> | ^~~
> sidpplay.cpp: In function ‘int sidOpenFile(uint32_t, moduleinfostruct*,
> FILE*)’:
> sidpplay.cpp:734:9: warning: ‘char* strncpy(char*, const char*, size_t)’
> output may be truncated copying 8 bytes from a string of length 11
> [-Wstringop-truncation]
> 734 | strncpy(currentmodname, info->name, _MAX_FNAME);
> | ~~~^~~~
> g++ -std=c++11 -DHAVE_CONFIG_H=1 -DSIDTUNE_NO_STDIN_LOADER=1
> -DPACKAGE_NAME=\"sidplayfp\" -DVERSION=\"2.0.1\"
> -DPACKAGE_VERSION=\"2.0.1-1\" -DPACKAGE_URL=\"\" -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -fPIC -I./sidplayfp-config
> -I./sidplayfp-git/libsidplayfp/src -o
> libsidplayfp-builders-resid-builder-resid-builder.o
> sidplayfp-git/libsidplayfp/src/builders/resid-builder/resid-builder.cpp -c
> g++ -std=c++11 -DHAVE_CONFIG_H=1 -DSIDTUNE_NO_STDIN_LOADER=1
> -DPACKAGE_NAME=\"sidplayfp\" -DVERSION=\"2.0.1\"
> -DPACKAGE_VERSION=\"2.0.1-1\" -DPACKAGE_URL=\"\" -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -fPIC
Bug#963377: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xterm Version: 356-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 > -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False > -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\" > -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 > -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 > -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual > -Wdeclaration-after-statement -Wextra -Winline -Wmissing-declarations > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow > -Wstrict-prototypes -Wundef -Wno-inline -Wignored-qualifiers -Wlogical-op > -Wvarargs -Wdeclaration-after-statement -Wextra -Wno-unknown-pragmas > -Wswitch-enum -Wno-cast-qual -c ../button.c > gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 > -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False > -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\" > -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 > -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 > -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual > -Wdeclaration-after-statement -Wextra -Winline -Wmissing-declarations > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow > -Wstrict-prototypes -Wundef -Wno-inline -Wignored-qualifiers -Wlogical-op > -Wvarargs -Wdeclaration-after-statement -Wextra -Wno-unknown-pragmas > -Wswitch-enum -Wno-cast-qual -c ../cachedGCs.c > gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 > -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False > -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\" > -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 > -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 > -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual > -Wdeclaration-after-statement -Wextra -Winline -Wmissing-declarations > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow > -Wstrict-prototypes -Wundef -Wno-inline -Wignored-qualifiers -Wlogical-op > -Wvarargs -Wdeclaration-after-statement -Wextra -Wno-unknown-pragmas > -Wswitch-enum -Wno-cast-qual -c ../charsets.c > making VTparse.hin from ../VTparse.def > gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 > -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False > -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\" > -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 > -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 > -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual > -Wdeclaration-after-statement -Wextra
Bug#963451: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: loadlin Version: 1.6f-7 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/src/srclinux' > gcc -m32 -traditional -c loadlinh.S > gcc -m32 -D__KERNEL__ -march=i386 -Os -DSTDC_HEADERS -fomit-frame-pointer > -fno-strength-reduce -fPIC -ffreestanding -fno-stack-protector -c pgadjust.c > -o pgadjust.o > ld -m elf_i386 -Ttext 0x95010 -N -e startup_32 -o pgadjust loadlinh.o > pgadjust.o > objcopy -O binary pgadjust pgadjust.out > echo "; 32-bit code, linkaddress: 0x95010" >pgadjust.as > hexdump -v -e '" DD " 8/4 "0%Xh," 1/4 "0%Xh\n"' pgadjust.out >>pgadjust.as > /bin/sh: 1: hexdump: not found > make[2]: *** [Makefile:19: ../pgadjust.asm] Error 127 The full build log is available from: http://qa-logs.debian.net/2020/06/20/loadlin_1.6f-7_unstable.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: latex2rtf Source-Version: 2.3.18-1 Done: Chris Lawrence We believe that the bug you reported is fixed in the latest version of latex2rtf, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence (supplier of updated latex2rtf 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 14:31:47 -0400 Source: latex2rtf Architecture: source Version: 2.3.18-1 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence Changed-By: Chris Lawrence Closes: 963414 Changes: latex2rtf (2.3.18-1) unstable; urgency=medium . * New upstream release. * Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414) * Upstream includes the test directory, so we can now drop patches that ignored it. Checksums-Sha1: 6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc 331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz 896ce7750df6ff7d99279ac0c1f9a0817908f640 9621 latex2rtf_2.3.18-1_source.buildinfo Checksums-Sha256: 9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961 latex2rtf_2.3.18-1.dsc c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156 latex2rtf_2.3.18.orig.tar.gz 33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044 latex2rtf_2.3.18-1.debian.tar.xz f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621 latex2rtf_2.3.18-1_source.buildinfo Files: 701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc 4f0110e57de941b9bf67972971e98118 2484156 tex optional latex2rtf_2.3.18.orig.tar.gz b930516bad7ced76a80b0c058f6b030c 27044 tex optional latex2rtf_2.3.18-1.debian.tar.xz 36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional latex2rtf_2.3.18-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM Zs/0GA//Us+7rEr4LaIziCsMLxnbBhU0+3GwGnEfZpXFhSlC/HpYQrHrdS74T9lL cRFjDlQsxc1/Q1+sJ227F55AoPw4ZzXt6D+SCpteRLPEx0YGvcKgZJgrBOu1lm5L 7n+5f2q9t9xboLK6UZfuOTlafNGBApfJ3ZYQmlmCO91RGuLbLjoQU6oP2DcF3uzU 4tGzn20xwodQ0qhBrbmediFfHJMqh+oaR8JNQBJXJfPVGNGFS47ZgtPN7MiQLAXX
Bug#963350: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slashem Version: 0.0.7E7F3-9 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/src' > make[4]: '../include/date.h' is up to date. > make[4]: Leaving directory '/<>/src' > cc -DDEBIAN_GTK -g -O2 -fomit-frame-pointer -fstack-protector > --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o recover.o recover.c > recover.c: In function ‘main’: > recover.c:114:10: warning: ignoring return value of ‘setgid’, declared with > attribute warn_unused_result [-Wunused-result] > 114 | (void) setgid(getgid()); > | ^~~~ > recover.c:115:10: warning: ignoring return value of ‘setuid’, declared with > attribute warn_unused_result [-Wunused-result] > 115 | (void) setuid(getuid()); > | ^~~~ > recover.c: In function ‘restore_savefile’: > recover.c:308:5: warning: ignoring return value of ‘write’, declared with > attribute warn_unused_result [-Wunused-result] > 308 | write(sfd, (genericptr_t) , sizeof(levc)); > | ^~ > cc -L/usr/X11R6/lib -Wl,-z,relro -o recover recover.o > make[3]: Leaving directory '/<>/util' > ( cd doc ; /usr/bin/make Guidebook ) > make[3]: Entering directory '/<>/doc' > tbl tmac.n Guidebook.mn | nroff | col -bx > Guidebook > /bin/sh: 1: col: not found > make[3]: *** [Makefile:40: Guidebook] Error 127 The full build log is available from: http://qa-logs.debian.net/2020/06/20/slashem_0.0.7E7F3-9_unstable.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: latex2rtf Source-Version: 2.3.18-1 Done: Chris Lawrence We believe that the bug you reported is fixed in the latest version of latex2rtf, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence (supplier of updated latex2rtf 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 14:31:47 -0400 Source: latex2rtf Architecture: source Version: 2.3.18-1 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence Changed-By: Chris Lawrence Closes: 963414 Changes: latex2rtf (2.3.18-1) unstable; urgency=medium . * New upstream release. * Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414) * Upstream includes the test directory, so we can now drop patches that ignored it. Checksums-Sha1: 6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc 331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz 896ce7750df6ff7d99279ac0c1f9a0817908f640 9621 latex2rtf_2.3.18-1_source.buildinfo Checksums-Sha256: 9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961 latex2rtf_2.3.18-1.dsc c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156 latex2rtf_2.3.18.orig.tar.gz 33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044 latex2rtf_2.3.18-1.debian.tar.xz f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621 latex2rtf_2.3.18-1_source.buildinfo
Bug#963442: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pbuilder
Version: 0.230.4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # syntax check.
> bash -n bash_completion.d/pbuilder
> bash -n pbuilderrc
> bash -n pbuilderrc
> bash -n debuild-pbuilder
> bash -n pdebuild
> bash -n pbuilder-apt-config
> bash -n pbuilder-buildpackage
> bash -n pbuilder-buildpackage-funcs
> bash -n pbuilder-checkparams
> bash -n pbuilder-createbuildenv
> bash -n pbuilder-loadconfig
> bash -n pbuilder-modules
> bash -n pbuilder-runhooks
> bash -n pbuilder-satisfydepends-apt
> bash -n pbuilder-satisfydepends-aptitude
> bash -n pbuilder-satisfydepends-checkparams
> bash -n pbuilder-satisfydepends-classic
> bash -n pbuilder-satisfydepends-experimental
> bash -n pbuilder-satisfydepends-funcs
> bash -n pbuilder-satisfydepends-gdebi
> bash -n pbuilder-unshare-wrapper
> bash -n pbuilder-updatebuildenv
> bash -n pdebuild-checkparams
> bash -n pdebuild-internal
> bash -n pbuilder
> bash -n examples/B90lintian
> bash -n examples/B91dpkg-i
> bash -n examples/B92test-pkg
> bash -n examples/C10shell
> bash -n examples/C11screen
> bash -n examples/D10tmp
> bash -n examples/D20addnonfree
> bash -n examples/D65various-compiler-support
> bash -n examples/D80no-man-db-rebuild
> bash -n examples/D90chrootmemo
> bash -n examples/F90chrootmemo
> bash -n examples/B90list-missing
> bash -n examples/B91debc
> bash -n examples/B20autopkgtest
> bash -n examples/execute_installtest.sh
> bash -n examples/execute_paramtest.sh
> bash -n examples/pbuilder-distribution.sh
> bash -n examples/lvmpbuilder/lvmbuilder
> bash -n examples/lvmpbuilder/lib/lvmbuilder-checkparams
> bash -n examples/lvmpbuilder/lib/lvmbuilder-modules
> bash -n examples/lvmpbuilder/lib/lvmbuilder-unimplemented
> bash -n examples/pbuilder-test/000_prepinstall
> bash -n examples/pbuilder-test/001_apprun
> bash -n examples/pbuilder-test/002_libfile
> bash -n examples/pbuilder-test/003_makecheck
> bash -n examples/pbuilder-test/004_ldd
> bash -n examples/rebuild/buildall
> bash -n examples/rebuild/getlist
> LANG=C MANWIDTH=80 man --warnings -l debuild-pbuilder.1 >/dev/null
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[1]: *** [Makefile:163: check] Error 3
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/pbuilder_0.230.4_unstable.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: latex2rtf
Source-Version: 2.3.18-1
Done: Chris Lawrence
We believe that the bug you reported is fixed in the latest version of
latex2rtf, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lawrence (supplier of updated latex2rtf 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: SHA512
Format: 1.8
Date: Mon, 22 Jun 2020 14:31:47 -0400
Source: latex2rtf
Architecture: source
Version: 2.3.18-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lawrence
Changed-By: Chris Lawrence
Closes: 963414
Changes:
latex2rtf
Bug#963372: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: console-setup Version: 1.195 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf > >/<>/Fonts/bdf/legacy16a-double.bdf > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx > >/<>/man/bdf2psf.1.txt > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf > >/<>/Fonts/bdf/legacy16b-double.bdf > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx > >/<>/man/console-setup.5.txt > /bin/sh: 1: col: not found > /bin/sh: 1: col: not found > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf > >/<>/Fonts/bdf/legacy16c-double.bdf > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf > >/<>/Fonts/bdf/legacy16d-double.bdf > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf > >/<>/Fonts/bdf/legacy16e-double.bdf > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf > >/<>/Fonts/bdf/legacy16f-double.bdf > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error > 127 The full build log is available from: http://qa-logs.debian.net/2020/06/20/console-setup_1.195_unstable.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: latex2rtf Source-Version: 2.3.18-1 Done: Chris Lawrence We believe that the bug you reported is fixed in the latest version of latex2rtf, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence (supplier of updated latex2rtf 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 14:31:47 -0400 Source: latex2rtf Architecture: source Version: 2.3.18-1 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence Changed-By: Chris Lawrence Closes: 963414 Changes: latex2rtf (2.3.18-1) unstable; urgency=medium . * New upstream release. * Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414) * Upstream includes the test directory, so we can now drop patches that ignored it. Checksums-Sha1: 6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc 331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz 896ce7750df6ff7d99279ac0c1f9a0817908f640 9621 latex2rtf_2.3.18-1_source.buildinfo Checksums-Sha256: 9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961 latex2rtf_2.3.18-1.dsc c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156 latex2rtf_2.3.18.orig.tar.gz 33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044 latex2rtf_2.3.18-1.debian.tar.xz f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621 latex2rtf_2.3.18-1_source.buildinfo Files: 701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc 4f0110e57de941b9bf67972971e98118 2484156 tex optional latex2rtf_2.3.18.orig.tar.gz b930516bad7ced76a80b0c058f6b030c 27044 tex optional latex2rtf_2.3.18-1.debian.tar.xz 36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional latex2rtf_2.3.18-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM
Bug#963359: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glhack Version: 1.2-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/src' > make[4]: '../include/date.h' is up to date. > make[4]: Leaving directory '/<>/src' > cc -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -O -I../include > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o recover.o recover.c > recover.c: In function ‘restore_savefile’: > recover.c:308:5: warning: ignoring return value of ‘write’, declared with > attribute warn_unused_result [-Wunused-result] > 308 | write(sfd, (genericptr_t) , sizeof(levc)); > | ^~ > cc -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -o > recover_glhack recover.o > make[3]: Leaving directory '/<>/util' > ( cd doc ; make Guidebook ) > make[3]: Entering directory '/<>/doc' > tbl tmac.n Guidebook.mn | nroff -Tascii | col -bx > Guidebook > /bin/sh: 1: col: not found > make[3]: *** [Makefile:27: Guidebook] Error 127 The full build log is available from: http://qa-logs.debian.net/2020/06/20/glhack_1.2-4_unstable.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: latex2rtf Source-Version: 2.3.18-1 Done: Chris Lawrence We believe that the bug you reported is fixed in the latest version of latex2rtf, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence (supplier of updated latex2rtf 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 14:31:47 -0400 Source: latex2rtf Architecture: source Version: 2.3.18-1 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence Changed-By: Chris Lawrence Closes: 963414 Changes: latex2rtf (2.3.18-1) unstable; urgency=medium . * New upstream release. * Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414) * Upstream includes the test directory, so we can now drop patches that ignored it. Checksums-Sha1: 6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc 331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz 896ce7750df6ff7d99279ac0c1f9a0817908f640 9621 latex2rtf_2.3.18-1_source.buildinfo Checksums-Sha256: 9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961 latex2rtf_2.3.18-1.dsc c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156 latex2rtf_2.3.18.orig.tar.gz 33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044 latex2rtf_2.3.18-1.debian.tar.xz f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621 latex2rtf_2.3.18-1_source.buildinfo Files: 701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc 4f0110e57de941b9bf67972971e98118 2484156 tex optional latex2rtf_2.3.18.orig.tar.gz b930516bad7ced76a80b0c058f6b030c 27044 tex optional
Bug#963376: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apcupsd
Version: 3.14.14-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[5]: Entering directory '/<>/src/lib'
> CXX src/lib/apcconfig.c
> g++ -x c++ -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include
> -I/<>/src/libusbhid -I/<>/include -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fno-exceptions -fno-rtti -Wall -Wno-unused-result
> -c -o .obj/apcconfig.o apcconfig.c
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[4]: *** [Makefile:10: apcupsd.man.txt] Error 127
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/apcupsd_3.14.14-3_unstable.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: latex2rtf
Source-Version: 2.3.18-1
Done: Chris Lawrence
We believe that the bug you reported is fixed in the latest version of
latex2rtf, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lawrence (supplier of updated latex2rtf 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: SHA512
Format: 1.8
Date: Mon, 22 Jun 2020 14:31:47 -0400
Source: latex2rtf
Architecture: source
Version: 2.3.18-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lawrence
Changed-By: Chris Lawrence
Closes: 963414
Changes:
latex2rtf (2.3.18-1) unstable; urgency=medium
.
* New upstream release.
* Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414)
* Upstream includes the test directory, so we can now drop patches that
ignored it.
Checksums-Sha1:
6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc
331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz
ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz
896ce7750df6ff7d99279ac0c1f9a0817908f640 9621
latex2rtf_2.3.18-1_source.buildinfo
Checksums-Sha256:
9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961
latex2rtf_2.3.18-1.dsc
c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156
latex2rtf_2.3.18.orig.tar.gz
33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044
latex2rtf_2.3.18-1.debian.tar.xz
f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621
latex2rtf_2.3.18-1_source.buildinfo
Files:
701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc
4f0110e57de941b9bf67972971e98118 2484156 tex optional
latex2rtf_2.3.18.orig.tar.gz
b930516bad7ced76a80b0c058f6b030c 27044 tex optional
latex2rtf_2.3.18-1.debian.tar.xz
36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional
latex2rtf_2.3.18-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM
Zs/0GA//Us+7rEr4LaIziCsMLxnbBhU0+3GwGnEfZpXFhSlC/HpYQrHrdS74T9lL
cRFjDlQsxc1/Q1+sJ227F55AoPw4ZzXt6D+SCpteRLPEx0YGvcKgZJgrBOu1lm5L
7n+5f2q9t9xboLK6UZfuOTlafNGBApfJ3ZYQmlmCO91RGuLbLjoQU6oP2DcF3uzU
4tGzn20xwodQ0qhBrbmediFfHJMqh+oaR8JNQBJXJfPVGNGFS47ZgtPN7MiQLAXX
2wVR7ywY5Ntxf7E9kRVmXsKlykJyFpmEym6ZMRckt8ZqLUjFvXhorPBG91vTdTwP
Bug#963306: marked as done (re2c: FTBFS: src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding re2c: FTBFS: src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: re2c Version: 1.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++98 -W > -Wall -Wextra -Weffc++ -pedantic -Wformat=2 -Wredundant-decls > -Wsuggest-attribute=format -Wconversion -Wsign-conversion > -Werror=return-type -O2 -DRE2C_STDLIB_DIR='"/usr/share/re2c/stdlib/"' -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o src/parse/parser.o src/parse/parser.cc > src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token > 3 | ; > | ^ > make[2]: *** [Makefile:2232: src/msg/help.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/re2c_1.3-1_unstable.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: latex2rtf Source-Version: 2.3.18-1 Done: Chris Lawrence We believe that the bug you reported is fixed in the latest version of latex2rtf, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence (supplier of updated latex2rtf 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 14:31:47 -0400 Source: latex2rtf Architecture: source Version: 2.3.18-1 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence Changed-By: Chris Lawrence Closes: 963414 Changes: latex2rtf (2.3.18-1) unstable; urgency=medium . * New upstream release. * Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414) * Upstream includes the test directory, so we can now drop patches that ignored it. Checksums-Sha1: 6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc 331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz 896ce7750df6ff7d99279ac0c1f9a0817908f640 9621 latex2rtf_2.3.18-1_source.buildinfo Checksums-Sha256: 9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961 latex2rtf_2.3.18-1.dsc c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156 latex2rtf_2.3.18.orig.tar.gz 33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044 latex2rtf_2.3.18-1.debian.tar.xz f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621 latex2rtf_2.3.18-1_source.buildinfo Files: 701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc 4f0110e57de941b9bf67972971e98118 2484156 tex optional latex2rtf_2.3.18.orig.tar.gz b930516bad7ced76a80b0c058f6b030c 27044 tex optional latex2rtf_2.3.18-1.debian.tar.xz 36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional latex2rtf_2.3.18-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM Zs/0GA//Us+7rEr4LaIziCsMLxnbBhU0+3GwGnEfZpXFhSlC/HpYQrHrdS74T9lL cRFjDlQsxc1/Q1+sJ227F55AoPw4ZzXt6D+SCpteRLPEx0YGvcKgZJgrBOu1lm5L 7n+5f2q9t9xboLK6UZfuOTlafNGBApfJ3ZYQmlmCO91RGuLbLjoQU6oP2DcF3uzU 4tGzn20xwodQ0qhBrbmediFfHJMqh+oaR8JNQBJXJfPVGNGFS47ZgtPN7MiQLAXX
Bug#963361: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hub Version: 2.7.0~ds1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > hub help hub-alias --plain-text | script/format-ronn hub-alias > share/man/man1/hub-alias.1.ronn > hub help hub-browse --plain-text | script/format-ronn hub-browse > share/man/man1/hub-browse.1.ronn > hub help hub-ci-status --plain-text | script/format-ronn hub-ci-status > share/man/man1/hub-ci-status.1.ronn > hub help hub-compare --plain-text | script/format-ronn hub-compare > share/man/man1/hub-compare.1.ronn > hub help hub-create --plain-text | script/format-ronn hub-create > share/man/man1/hub-create.1.ronn > hub help hub-delete --plain-text | script/format-ronn hub-delete > share/man/man1/hub-delete.1.ronn > hub help hub-fork --plain-text | script/format-ronn hub-fork > share/man/man1/hub-fork.1.ronn > hub help hub-pr --plain-text | script/format-ronn hub-pr > share/man/man1/hub-pr.1.ronn > hub help hub-pull-request --plain-text | script/format-ronn hub-pull-request > share/man/man1/hub-pull-request.1.ronn > hub help hub-release --plain-text | script/format-ronn hub-release > share/man/man1/hub-release.1.ronn > hub help hub-issue --plain-text | script/format-ronn hub-issue > share/man/man1/hub-issue.1.ronn > hub help hub-sync --plain-text | script/format-ronn hub-sync > share/man/man1/hub-sync.1.ronn > hub help hub-am --plain-text | script/format-ronn hub-am > share/man/man1/hub-am.1.ronn > hub help hub-apply --plain-text | script/format-ronn hub-apply > share/man/man1/hub-apply.1.ronn > hub help hub-checkout --plain-text | script/format-ronn hub-checkout > share/man/man1/hub-checkout.1.ronn > hub help hub-cherry-pick --plain-text | script/format-ronn hub-cherry-pick > share/man/man1/hub-cherry-pick.1.ronn > hub help hub-clone --plain-text | script/format-ronn hub-clone > share/man/man1/hub-clone.1.ronn > hub help hub-fetch --plain-text | script/format-ronn hub-fetch > share/man/man1/hub-fetch.1.ronn > hub help hub-help --plain-text | script/format-ronn hub-help > share/man/man1/hub-help.1.ronn > hub help hub-init --plain-text | script/format-ronn hub-init > share/man/man1/hub-init.1.ronn > hub help hub-merge --plain-text | script/format-ronn hub-merge > share/man/man1/hub-merge.1.ronn > hub help hub-push --plain-text | script/format-ronn hub-push > share/man/man1/hub-push.1.ronn > hub help hub-remote --plain-text | script/format-ronn hub-remote > share/man/man1/hub-remote.1.ronn > hub help hub-submodule --plain-text | script/format-ronn hub-submodule > share/man/man1/hub-submodule.1.ronn > ronn --organization=GITHUB --manual="Hub Manual" share/man/man1/*.ronn > roff: share/man/man1/hub-alias.1 > html: share/man/man1/hub-alias.1.html +man > roff: share/man/man1/hub-am.1 > html: share/man/man1/hub-am.1.html +man > roff: share/man/man1/hub-apply.1 > html: share/man/man1/hub-apply.1.html +man > roff: share/man/man1/hub-browse.1 > tbl::9: unrecognised format '\' > tbl::9: giving up on this table > html: share/man/man1/hub-browse.1.html +man > roff: share/man/man1/hub-checkout.1 > html: share/man/man1/hub-checkout.1.html+man > roff: share/man/man1/hub-cherry-pick.1 > html: share/man/man1/hub-cherry-pick.1.html +man > roff: share/man/man1/hub-ci-status.1 > html: share/man/man1/hub-ci-status.1.html +man > roff: share/man/man1/hub-clone.1 > html: share/man/man1/hub-clone.1.html +man > roff: share/man/man1/hub-compare.1 > html: share/man/man1/hub-compare.1.html +man > roff: share/man/man1/hub-create.1 > html: share/man/man1/hub-create.1.html +man
Bug#963383: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: calc Version: 2.12.7.2-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/custom' > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. -c -o custtbl.o custtbl.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. -c -o c_argv.o c_argv.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. -c -o c_devnull.o c_devnull.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. -c -o c_help.o c_help.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. c_sysinfo.c -c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. -c -o c_pzasusb8.o c_pzasusb8.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. -c -o c_pmodm127.o c_pmodm127.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -I.. -c -o c_register.o c_register.c > rm -f libcustcalc.a > ar qc libcustcalc.a custtbl.o c_argv.o c_devnull.o c_help.o c_sysinfo.o > c_pzasusb8.o c_pmodm127.o c_register.o > ranlib libcustcalc.a > chmod 0644 libcustcalc.a > echo '=-=-=-=-= custom/Makefile start of Makefile.simple rule =-=-=-=-=' > =-=-=-=-= custom/Makefile start of Makefile.simple rule =-=-=-=-= > echo '=-=-=-=-= custom/Makefile end of Makefile.simple rule =-=-=-=-=' > =-=-=-=-= custom/Makefile end of Makefile.simple rule =-=-=-=-= > rm -f .all > touch .all > make[2]: Leaving directory '/<>/custom' > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o addop.o addop.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o assocfunc.o assocfunc.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o blkcpy.o blkcpy.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o block.o block.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o byteswap.o byteswap.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o calcerr.o calcerr.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o codegen.o codegen.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -g3 -c -o comfunc.o comfunc.c > gcc -DCALC_SRC -DCUSTOM -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat
Bug#963403: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 + with message-id and subject line Bug#963414: fixed in latex2rtf 2.3.18-1 has caused the Debian Bug report #963414, regarding bsdmainutils must depend on bsdextrautils 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.) -- 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mp3info Version: 0.8.5a-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o mp3info.o mp3info.c > gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o textfunc.o textfunc.c > gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o mp3curs.o mp3curs.c > gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o mp3tech.o mp3tech.c > mp3info.c: In function ‘main’: > mp3info.c:287:3: warning: ignoring return value of ‘truncate’, declared with > attribute warn_unused_result [-Wunused-result] > 287 | truncate(mp3.filename,mp3.datasize); > | ^~~ > mp3tech.c: In function ‘get_id3’: > mp3tech.c:306:5: warning: ignoring return value of ‘fread’, declared with > attribute warn_unused_result [-Wunused-result] > 306 | fread(fbuf,1,3,mp3->file); fbuf[3] = '\0'; > | ^ > mp3tech.c:316:15: warning: ignoring return value of ‘fread’, declared with > attribute warn_unused_result [-Wunused-result] > 316 | fread(mp3->id3.title,1,30,mp3->file); > mp3->id3.title[30] = '\0'; > | ^~~~ > mp3tech.c:317:15: warning: ignoring return value of ‘fread’, declared with > attribute warn_unused_result [-Wunused-result] > 317 | fread(mp3->id3.artist,1,30,mp3->file); > mp3->id3.artist[30] = '\0'; > | ^ > mp3tech.c:318:15: warning: ignoring return value of ‘fread’, declared with > attribute warn_unused_result [-Wunused-result] > 318 | fread(mp3->id3.album,1,30,mp3->file); > mp3->id3.album[30] = '\0'; > | ^~~~ > mp3tech.c:319:15: warning: ignoring return value of ‘fread’, declared with > attribute warn_unused_result [-Wunused-result] > 319 | fread(mp3->id3.year,1,4,mp3->file); mp3->id3.year[4] = > '\0'; > | ^~ > mp3tech.c:320:15: warning: ignoring return value of ‘fread’, declared with > attribute warn_unused_result [-Wunused-result] > 320 | fread(mp3->id3.comment,1,30,mp3->file); > mp3->id3.comment[30] = '\0'; > | ^~ > mp3tech.c:324:15: warning: ignoring return value of ‘fread’, declared with > attribute warn_unused_result [-Wunused-result] > 324 | fread(mp3->id3.genre,1,1,mp3->file); > | ^~~ > In file included from /usr/include/string.h:495, > from mp3info.h:31, > from mp3curs.c:27: > In function ‘strncpy’, > inlined from ‘tagedit_curs’ at mp3curs.c:111:4: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: > ‘__builtin___strncpy_chk’ output truncated before terminating nul copying as > many bytes from a string as its length [-Wstringop-truncation] > 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos > (__dest)); > | > ^~ > mp3curs.c: In function ‘tagedit_curs’: > mp3curs.c:111:4: note: length computed here > 111 |strncpy(tag->title,line,strlen(line)); > |^ > In file included from /usr/include/string.h:495, > from mp3info.h:31, > from mp3curs.c:27: > In function ‘strncpy’, > inlined from ‘tagedit_curs’ at mp3curs.c:113:4: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: > ‘__builtin___strncpy_chk’ output truncated before terminating nul copying as > many bytes from a string as its length [-Wstringop-truncation] > 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos > (__dest)); > | > ^~ > mp3curs.c: In function
Bug#963375: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conky
Version: 1.10.8-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/build-std'
> [ 7%] Proccessing man page for docs
> cd /<>/build-std/doc && /usr/bin/xsltproc
> http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
> /<>/doc/docs.xml > /<>/doc/docs.html
> cd /<>/build-std/doc && /usr/bin/db2x_xsltproc -s man
> /<>/doc/docs.xml -o docs.mxml
> cd /<>/build-std/doc && /usr/bin/db2x_manxml --encoding=utf-8
> docs.mxml --output-dir /<>/doc
> cd /<>/build-std/doc && /usr/bin/xsltproc
> http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
> /<>/doc/docs.xml > /<>/doc/docs.html
> cd /<>/build-std/doc && /usr/bin/man -P '/usr/bin/less -is'
> /<>/doc/conky.1 > /<>/README
> /usr/bin/man: can't execute col: No such file or directory
> /usr/bin/man: command exited with status 127: col -b -p -x | sed -e
> '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[4]: *** [doc/CMakeFiles/docs.dir/build.make:68: ../doc/docs.html] Error 3
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/conky_1.10.8-1.1_unstable.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: latex2rtf
Source-Version: 2.3.18-1
Done: Chris Lawrence
We believe that the bug you reported is fixed in the latest version of
latex2rtf, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lawrence (supplier of updated latex2rtf 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: SHA512
Format: 1.8
Date: Mon, 22 Jun 2020 14:31:47 -0400
Source: latex2rtf
Architecture: source
Version: 2.3.18-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lawrence
Changed-By: Chris Lawrence
Closes: 963414
Changes:
latex2rtf (2.3.18-1) unstable; urgency=medium
.
* New upstream release.
* Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414)
* Upstream includes the test directory, so we can now drop patches that
ignored it.
Checksums-Sha1:
6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc
331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz
ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz
896ce7750df6ff7d99279ac0c1f9a0817908f640 9621
latex2rtf_2.3.18-1_source.buildinfo
Checksums-Sha256:
9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961
latex2rtf_2.3.18-1.dsc
c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156
latex2rtf_2.3.18.orig.tar.gz
33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044
latex2rtf_2.3.18-1.debian.tar.xz
f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621
latex2rtf_2.3.18-1_source.buildinfo
Files:
701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc
4f0110e57de941b9bf67972971e98118 2484156 tex optional
latex2rtf_2.3.18.orig.tar.gz
b930516bad7ced76a80b0c058f6b030c 27044 tex optional
latex2rtf_2.3.18-1.debian.tar.xz
36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional
latex2rtf_2.3.18-1_source.buildinfo
-BEGIN PGP SIGNATURE-
Bug#963413: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vmem
Version: 1.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> ../utils/md2man.sh libvmem/libvmem.7.md default.man generated/libvmem.7;
> ../utils/md2man.sh libvmmalloc/libvmmalloc.7.md default.man
> generated/libvmmalloc.7;
> ../utils/md2man.sh libvmem/vmem_create.3.md default.man
> generated/vmem_create.3; ../utils/md2man.sh libvmem/vmem_malloc.3.md
> default.man generated/vmem_malloc.3;
> man ./generated/libvmem.7 > generated/libvmem.7.txt
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[3]: *** [Makefile:103: generated/libvmem.7.txt] Error 3
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/vmem_1.8-1_unstable.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: latex2rtf
Source-Version: 2.3.18-1
Done: Chris Lawrence
We believe that the bug you reported is fixed in the latest version of
latex2rtf, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lawrence (supplier of updated latex2rtf 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: SHA512
Format: 1.8
Date: Mon, 22 Jun 2020 14:31:47 -0400
Source: latex2rtf
Architecture: source
Version: 2.3.18-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lawrence
Changed-By: Chris Lawrence
Closes: 963414
Changes:
latex2rtf (2.3.18-1) unstable; urgency=medium
.
* New upstream release.
* Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414)
* Upstream includes the test directory, so we can now drop patches that
ignored it.
Checksums-Sha1:
6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc
331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz
ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz
896ce7750df6ff7d99279ac0c1f9a0817908f640 9621
latex2rtf_2.3.18-1_source.buildinfo
Checksums-Sha256:
9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961
latex2rtf_2.3.18-1.dsc
c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156
latex2rtf_2.3.18.orig.tar.gz
33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044
latex2rtf_2.3.18-1.debian.tar.xz
f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621
latex2rtf_2.3.18-1_source.buildinfo
Files:
701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc
4f0110e57de941b9bf67972971e98118 2484156 tex optional
latex2rtf_2.3.18.orig.tar.gz
b930516bad7ced76a80b0c058f6b030c 27044 tex optional
latex2rtf_2.3.18-1.debian.tar.xz
36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional
latex2rtf_2.3.18-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM
Zs/0GA//Us+7rEr4LaIziCsMLxnbBhU0+3GwGnEfZpXFhSlC/HpYQrHrdS74T9lL
cRFjDlQsxc1/Q1+sJ227F55AoPw4ZzXt6D+SCpteRLPEx0YGvcKgZJgrBOu1lm5L
7n+5f2q9t9xboLK6UZfuOTlafNGBApfJ3ZYQmlmCO91RGuLbLjoQU6oP2DcF3uzU
4tGzn20xwodQ0qhBrbmediFfHJMqh+oaR8JNQBJXJfPVGNGFS47ZgtPN7MiQLAXX
Bug#963448: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wiki2beamer
Version: 0.10.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>debian/rules execute_after_dh_auto_build
> make[1]: Entering directory '/<>'
> /usr/bin/make -C /<>/doc/man/
> make[2]: Entering directory '/<>/doc/man'
> mkdir man1
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[2]: *** [Makefile:9: man] Error 3
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/wiki2beamer_0.10.0-1_unstable.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: latex2rtf
Source-Version: 2.3.18-1
Done: Chris Lawrence
We believe that the bug you reported is fixed in the latest version of
latex2rtf, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lawrence (supplier of updated latex2rtf 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: SHA512
Format: 1.8
Date: Mon, 22 Jun 2020 14:31:47 -0400
Source: latex2rtf
Architecture: source
Version: 2.3.18-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lawrence
Changed-By: Chris Lawrence
Closes: 963414
Changes:
latex2rtf (2.3.18-1) unstable; urgency=medium
.
* New upstream release.
* Fix FTBFS by now build-depending on bsdextrautils. (Closes: #963414)
* Upstream includes the test directory, so we can now drop patches that
ignored it.
Checksums-Sha1:
6c85bc694a19c34f78b650d966da00b81066af42 1961 latex2rtf_2.3.18-1.dsc
331c7f6a17268b51591b0f88b1e217b7bf87c332 2484156 latex2rtf_2.3.18.orig.tar.gz
ae3bdef5829567eee46630b807228cc8870fa958 27044 latex2rtf_2.3.18-1.debian.tar.xz
896ce7750df6ff7d99279ac0c1f9a0817908f640 9621
latex2rtf_2.3.18-1_source.buildinfo
Checksums-Sha256:
9977ce1fcb29dd4dc0a7af05c51e9821a7eb35eb6599b8c0c3e50addb466230b 1961
latex2rtf_2.3.18-1.dsc
c0b6a9f5877b3b24b1571c5f2c42afd22f0db5448448d4de7379e67d284ca0b1 2484156
latex2rtf_2.3.18.orig.tar.gz
33393e46f41efad54f4f66387e5e8e716df99a4cf039a85566e84f5f974e752d 27044
latex2rtf_2.3.18-1.debian.tar.xz
f1087f2c4a08617bb369c8f40d031125e46c2e336f23cd58448d692653033164 9621
latex2rtf_2.3.18-1_source.buildinfo
Files:
701ee9cbf869bbba7a70b3e1bf3b1957 1961 tex optional latex2rtf_2.3.18-1.dsc
4f0110e57de941b9bf67972971e98118 2484156 tex optional
latex2rtf_2.3.18.orig.tar.gz
b930516bad7ced76a80b0c058f6b030c 27044 tex optional
latex2rtf_2.3.18-1.debian.tar.xz
36e358624dbc9e6fd4f7abe47a81347c 9621 tex optional
latex2rtf_2.3.18-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEaVikEA0YMJeLPay2yfxBuPmMZs8FAl7xD00ACgkQyfxBuPmM
Zs/0GA//Us+7rEr4LaIziCsMLxnbBhU0+3GwGnEfZpXFhSlC/HpYQrHrdS74T9lL
cRFjDlQsxc1/Q1+sJ227F55AoPw4ZzXt6D+SCpteRLPEx0YGvcKgZJgrBOu1lm5L
7n+5f2q9t9xboLK6UZfuOTlafNGBApfJ3ZYQmlmCO91RGuLbLjoQU6oP2DcF3uzU
4tGzn20xwodQ0qhBrbmediFfHJMqh+oaR8JNQBJXJfPVGNGFS47ZgtPN7MiQLAXX
2wVR7ywY5Ntxf7E9kRVmXsKlykJyFpmEym6ZMRckt8ZqLUjFvXhorPBG91vTdTwP
0E6Sbib8Hwa5yDKvT1t0Q4j37eKiyGCnoQhxZmTot+ZSVWlZYPKffGQdAalZSkcu
Bug#963414: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Mon, 22 Jun 2020 20:34:45 +
with message-id
and subject line Bug#963414: fixed in latex2rtf 2.3.18-1
has caused the Debian Bug report #963414,
regarding bsdmainutils must depend on bsdextrautils
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.)
--
963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: latex2rtf
Version: 2.3.16-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> makeinfo latex2rtf
> chmod 644 latex2rtf.info
> texi2pdf latex2rtf.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.)
> [1{/var/lib/texmf/fonts/map/pdftex/updmap
> /pdftex.map}] [2] Chapter 1
> Cross reference values unknown; you must run TeX again.
> Writing index file latex2rtf.cp
> Chapter 2 [1] [2] [3] [4] [5] [6] Chapter 3 [7] [8] [9] [10] [11] [12] [13]
> Chapter 4 [14] [15] [16] [17] [18] Chapter 5 [19] [20] [21] [22] [23]
> Chapter 6 [24] Chapter 7 [25] [26] Chapter 8 [27] [28] [29]
> Writing index file latex2rtf.fn
> [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44]
> [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] Chapter 9 [56]
> No file latex2rtf.fns.
> Chapter 10 [57] [58]
> No file latex2rtf.cps.
> [59] [60] (/<>/doc/latex2rtf.toc [-1])
> [-2] (/<>/doc/latex2rtf.toc)
> (/<>/doc/latex2rtf.toc) ) ve/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> mf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> st/fonts/type1/public/amsfonts/cm/cmmi10.pfb> ts/type1/public/amsfonts/cm/cmmi12.pfb> e1/public/amsfonts/cm/cmmi7.pfb> ic/amsfonts/cm/cmr10.pfb> onts/cm/cmr9.pfb> cmsy10.pfb> .pfb>
> Output written on latex2rtf.pdf (64 pages, 221371 bytes).
> Transcript written on latex2rtf.log.
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.)
> [1{/var/lib/texmf/fonts/map/pdftex/updmap
> /pdftex.map}] [2] Chapter 1
> (/<>/doc/latex2rtf.aux)
> Writing index file latex2rtf.cp
> Chapter 2 [1] [2] [3] [4] [5] [6] Chapter 3 [7] [8] [9] [10] [11] [12] [13]
> Chapter 4 [14] [15] [16] [17] [18] Chapter 5 [19] [20] [21] [22] [23]
> Chapter 6 [24] Chapter 7 [25] [26] Chapter 8 [27] [28] [29]
> Writing index file latex2rtf.fn
> [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44]
> [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] Chapter 9 [56]
> (/<>/doc/latex2rtf.fns [57] [58] [59]
> [60] [61] [62] [63]) Chapter 10 [64]
> (/<>/doc/latex2rtf.cps) [65] [66]
> (/<>/doc/latex2rtf.toc [-1]) [-2]
> (/<>/doc/latex2rtf.toc)
> (/<>/doc/latex2rtf.toc) ) ve/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> mf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> st/fonts/type1/public/amsfonts/cm/cmmi10.pfb> ts/type1/public/amsfonts/cm/cmmi12.pfb> e1/public/amsfonts/cm/cmmi7.pfb> ic/amsfonts/cm/cmmi9.pfb> onts/cm/cmr10.pfb> /cmr9.pfb> pfb> usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmtt12.pfb> are/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmtt9.pfb>
> Output written on latex2rtf.pdf (70 pages, 307880 bytes).
> Transcript written on latex2rtf.log.
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
>
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
On Mon, Jun 22, 2020 at 09:56:13PM +0200, Lucas Nussbaum wrote: > On 22/06/20 at 21:35 +0200, Michael Meskes wrote: > > The reason for this move is moving from the old and heavily patched BSD > > source to the more up-to-date GNU version. > > I did a partial archive rebuild reverting to the version of bsdmainutils > with 'col' and others. It seems that the list of affected packages from > #963327 is complete with the exception of 'notmuch'. > > A good plan would probably be to fix man-db, and look at what are the > remaining failures after that. I'm going to upload man-db with a dependency on bsdextrautils | bsdmainutils (<< 12.1.1~) shortly. (There's been a bit of a delay because of some unrelated po4a-induced breakage that I had to stop and fix upstream first.) However, in order to make buster → bullseye upgrades work properly, I think it's necessary to have bsdmainutils depend on bsdextrautils for at least one release cycle. Otherwise there may be a point during the upgrade where col isn't installed and so man will be broken; it's worth putting some effort into avoiding that because if the upgrade happens to break then users may need to consult man pages to work out what to do. The only reliable way I can think of to avoid this kind of problem is to have a hard dependency for a while as a transitional measure. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#931566:
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
On 22/06/20 at 21:35 +0200, Michael Meskes wrote: > On Mon, 2020-06-22 at 20:57 +0200, Julien Cristau wrote: > > On Mon, Jun 22, 2020 at 19:46:21 +0200, Michael Meskes wrote: > > > > > > Depending on bsdmainutils to get col et al seems entirely right, > > > > it's > > > > been right forever, there doesn't seem to be a reason to break > > > > that > > > > both > > > > for dependent packages and for end users. Especially not without > > > > notice. > > > > > > There is no point arguing against your "do not change anything" > > > attitude. > > > > > I'm not saying don't change anything, I'm saying don't break stuff > > for > > users for no reason. > > You are saying the reason is "it's been right forever". > > The reason for this move is moving from the old and heavily patched BSD > source to the more up-to-date GNU version. I did a partial archive rebuild reverting to the version of bsdmainutils with 'col' and others. It seems that the list of affected packages from #963327 is complete with the exception of 'notmuch'. A good plan would probably be to fix man-db, and look at what are the remaining failures after that. Lucas
Bug#963211: marked as done (libmu-dbm6: Tries to overwrite `libmu_dbm.so.6.0.0` from `libmailutils6`)
Your message dated Mon, 22 Jun 2020 19:48:58 + with message-id and subject line Bug#963211: fixed in mailutils 1:3.9-3 has caused the Debian Bug report #963211, regarding libmu-dbm6: Tries to overwrite `libmu_dbm.so.6.0.0` from `libmailutils6` 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.) -- 963211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmu-dbm6 Version: 1:3.9-2 Dear Debian folks, Trying to update my Debian Sid/unstable system, `apt full-upgrade` failed with the messages below. dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-9C7NlK/00-libmu-dbm6_1%3a3.9-2_i386.deb (--unpack): Versuch, »/usr/lib/i386-linux-gnu/libmu_dbm.so.6.0.0« zu überschreiben, welches auch in Paket libmailutils6:i386 1:3.7-2.1 ist dpkg-deb: Fehler: »einfügen«-Unterprozess wurde durch Signal (Datenübergabe unterbrochen (broken pipe)) getötet It looks like some conflict needs to be added? Kind regards, Paul --- End Message --- --- Begin Message --- Source: mailutils Source-Version: 1:3.9-3 Done: Jordi Mallach We believe that the bug you reported is fixed in the latest version of mailutils, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jordi Mallach (supplier of updated mailutils 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 21:09:21 +0200 Source: mailutils Architecture: source Version: 1:3.9-3 Distribution: unstable Urgency: medium Maintainer: Jordi Mallach Changed-By: Jordi Mallach Closes: 963211 Changes: mailutils (1:3.9-3) unstable; urgency=medium . * Bump Breaks/Replaces for libmu-dbm6 to 1:3.7-2.1 (closes: #963211). Checksums-Sha1: 1c06513712dd46a74434c0df5988de3d67bbc0ff 3187 mailutils_3.9-3.dsc 8a7413a16aa270e4873011892bbb1f3d543cde4a 29964 mailutils_3.9-3.debian.tar.xz 01fd330103cdcd186bc4053c7a86b7b2094b525c 14895 mailutils_3.9-3_amd64.buildinfo Checksums-Sha256: 509e20b104f513c03e191601c252d384cda20e23b1e3ffcadf8056586f20f78b 3187 mailutils_3.9-3.dsc a54e78b7a1bc751e0d4aba8196ead39b7635ed69151d05db237d1d156a237591 29964 mailutils_3.9-3.debian.tar.xz 8f9d0a6d57e119c06bb1b84db0b4df997beae32f8fb1790dca59b5e8b9dceb21 14895 mailutils_3.9-3_amd64.buildinfo Files: 86abb6957a1bc9d4a48f6c7b38aec8ec 3187 mail optional mailutils_3.9-3.dsc bdb47a6084117ba71edb64bf3f751fa7 29964 mail optional mailutils_3.9-3.debian.tar.xz e5ae13536f116d12e2b6a8f3e7b010a8 14895 mail optional mailutils_3.9-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAl7xBaQACgkQJVAvb8vj ywQw2g//RygM8K/0uyrHo5ZvWaMdOJ6AD4LVJ459jSLgZ5exhqdyReYp1WG0HEoc 33+4GB9VITVyeUU/PAyt7ziG9/BYx7RbnGwS89sPTQSFdWp7K42CasrlnWqplFGr Km1XeLZ1ARrlnAWu4QO6lsh9btw7XObS4KmN1O27TtPEi3eFmS5qj4yX/mYhLNb/ qsR/qfcwON0Snhc/Au9G3DtcRoFaTrXr4+E8E6/HbRQwq7nZXrVO5TFshEUrR+dX bTPuCJwasurFQXq7qB5Om6mEq3n6aL/9xCOSnxL1q49XZT/9iEP5YVs2WQOCy0xU AifcE6MjO/eUpXK8NUWJm78z2CynEduvRO6HjyHKiqw6KgRA1LiMP5HYftE66VEQ UGS5T0t/lUL+SF2QdQWpHBj0O/YQkNhbNydxDkG5VtulmLX+FiDFwilwUIS9961T C/4ft/4hV/kJk1g3eWNlWGRFEhLT55aFL1V/hjxTntITybx80pynVc40hg1jGv9+ RfR/rk8M8ookoHfWNmvHRQ9E7krctEMKKYWZ1CDpJ/OU7awJ21BUdwn+ki5it0XJ QNuDFuouV1kJvP/1UQZWRC6MZxw28WaJAVdCyPHCgGr/uFHBOHM7JLJmqqsgFnty WmaI5O+EFFe3eNv/CtVoVpwnOztpe0OQjFKYSP4SGrXeEDpyhH4= =u8Ch -END PGP SIGNATURE End Message ---
Processed: closing 963349
Processing commands for cont...@bugs.debian.org:
> close 963349
Bug #963349 {Done: Michael Meskes } [libdap] bsdmainutils
must depend on bsdextrautils
Bug 963349 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 963427
Processing commands for cont...@bugs.debian.org:
> close 963427
Bug #963427 {Done: Roland Rosenfeld } [ding] bsdmainutils
must depend on bsdextrautils
Bug 963427 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 963353
Processing commands for cont...@bugs.debian.org:
> close 963353
Bug #963353 {Done: Alastair McKinstry } [mcl]
bsdmainutils must depend on bsdextrautils
Bug 963353 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 963349 to libdap
Processing commands for cont...@bugs.debian.org:
> reassign 963349 libdap
Bug #963349 {Done: Michael Meskes } [libldap] bsdmainutils
must depend on bsdextrautils
Warning: Unknown package 'libldap'
Bug reassigned from package 'libldap' to 'libdap'.
Ignoring request to alter found versions of bug #963349 to the same values
previously set
Ignoring request to alter fixed versions of bug #963349 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 963349
Processing commands for cont...@bugs.debian.org: > close 963349 Bug #963349 [libldap] bsdmainutils must depend on bsdextrautils Warning: Unknown package 'libldap' Marked Bug as done Warning: Unknown package 'libldap' > thanks Stopping processing here. Please contact me if you need assistance. -- 963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
On Mon, 2020-06-22 at 20:57 +0200, Julien Cristau wrote: > On Mon, Jun 22, 2020 at 19:46:21 +0200, Michael Meskes wrote: > > > > Depending on bsdmainutils to get col et al seems entirely right, > > > it's > > > been right forever, there doesn't seem to be a reason to break > > > that > > > both > > > for dependent packages and for end users. Especially not without > > > notice. > > > > There is no point arguing against your "do not change anything" > > attitude. > > > I'm not saying don't change anything, I'm saying don't break stuff > for > users for no reason. You are saying the reason is "it's been right forever". The reason for this move is moving from the old and heavily patched BSD source to the more up-to-date GNU version. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
Processed: reassign 963349 to libldap
Processing commands for cont...@bugs.debian.org: > reassign 963349 libldap Bug #963349 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug reassigned from package 'bsdmainutils' to 'libldap'. Warning: Unknown package 'libldap' Warning: Unknown package 'libldap' No longer marked as found in versions bsdmainutils/12.1.1. Warning: Unknown package 'libldap' Warning: Unknown package 'libldap' Ignoring request to alter fixed versions of bug #963349 to the same values previously set Warning: Unknown package 'libldap' > thanks Stopping processing here. Please contact me if you need assistance. -- 963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 963427 to ding
Processing commands for cont...@bugs.debian.org:
> reassign 963427 ding
Bug #963427 {Done: Roland Rosenfeld } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug reassigned from package 'bsdmainutils' to 'ding'.
No longer marked as found in versions bsdmainutils/12.1.1.
No longer marked as fixed in versions ding/1.8.1-9.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 963353 to mcl
Processing commands for cont...@bugs.debian.org:
> reassign 963353 mcl
Bug #963353 {Done: Alastair McKinstry } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Bug reassigned from package 'bsdmainutils' to 'mcl'.
No longer marked as found in versions bsdmainutils/12.1.1.
No longer marked as fixed in versions libdap/3.20.6-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#962827: [pkg-php-pear] Bug#962827: Fix uploaded to DELAYED/5: libphp-phpmailer: CVE-2020-13625
Hi Paul, Thank you for your fix. Le 22/06/2020 à 09:02, Paul Gevers a écrit : > As announced I've prepared an upload for libphp-phpmailer (versioned as > 6.1.6-1) and uploaded it to DELAYED/5. If anybody objects against me > adding myself as uploader, please tell me and I'll cancel the upload. On the contrary, welcome to the team, feel free to reschedule the upload to DELAYED/0! > By the way, if anybody has a copy of the old git archive (I couldn't > find it on alioth-archive.debian.org) I would like to get one too. It’s there: https://alioth-archive.debian.org/git/pkg-php/libphp-phpmailer.git.tar.xz Regards David
Bug#963154: nmapsi4: Must not be arch:any
Em sáb., 20 de jun. de 2020 às 10:00, Adrian Bunk escreveu: > > There are plenty of packages in the archive whose build dependencies > cannot be fulfilled on all release architectures. > > This is not a problem. Ok, thanks Adrian. I fixed forensics-all, affected by this change. Regards, Eriberto
Bug#963408: pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
On Sun, Jun 21, 2020 at 11:35:22PM +0200, gregor herrmann wrote: > On Sun, 21 Jun 2020 22:11:05 +0200, Lucas Nussbaum wrote: > > > # 'pod2text: unable to format > > > /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm > Interesting bug, and not found in cpantesters. > > I note that /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm (from > perl-base) indeed has no POD, but /usr/share/perl/5.30.3/Carp.pm > (from perl-modules-5.30) does. And bin/pman finds the first one. > > I wonder why this pops up now? Can this be related to the recent > changes of @INC in src:perl? Yes. The .pm files in perl-base have their POD documentation stripped away (see debian/stripdoc in src:perl). Those are now first on @INC even when libperl5.30 are perl-modules-5.30 are installed (see #962138). Looks like /usr/bin/perldoc finds the second Carp.pm when the first doesn't contain any POD documentation, but the pmtools build can't. Not sure what to do about this bug. As an isolated corner case we can patch around it, but the fact is we're slightly more visibly deviated from upstream than we used to be. We'll see if more things like these crop up. We could also stop stripping the docs in perl-base. Statistics about how much space it's saving now would be useful if we want to consider that. Copying perl@pdo as a heads up. -- Niko
Bug#962827: Fix uploaded to DELAYED/5: libphp-phpmailer: CVE-2020-13625
Package: libphp-phpmailer Version: 6.1.5-0.1 Tags: patch pending Dear maintainer, As announced I've prepared an upload for libphp-phpmailer (versioned as 6.1.6-1) and uploaded it to DELAYED/5. If anybody objects against me adding myself as uploader, please tell me and I'll cancel the upload. By the way, if anybody has a copy of the old git archive (I couldn't find it on alioth-archive.debian.org) I would like to get one too. Regards. Paul diff -Nru libphp-phpmailer-6.1.5/debian/changelog libphp-phpmailer-6.1.6/debian/changelog --- libphp-phpmailer-6.1.5/debian/changelog 2020-04-22 22:11:37.0 +0200 +++ libphp-phpmailer-6.1.6/debian/changelog 2020-06-22 20:31:41.0 +0200 @@ -1,3 +1,16 @@ +libphp-phpmailer (6.1.6-1) unstable; urgency=medium + + * New upstream version 6.1.6 +- CVE-2020-13625 an output escaping bug when the name of a file + attachment contains a double quote character. This can result in + the file type being misinterpreted by the receiver or any mail + relay processing the message (Closes: #962827) + * Add myself as uploader + * Drop Kevin Coyner as uploader (Closes: #929548) + * Point Vcs-* fields to the dgit server for now as Alioth is gone + + -- Paul Gevers Mon, 22 Jun 2020 20:31:41 +0200 + libphp-phpmailer (6.1.5-0.1) unstable; urgency=medium * Non-maintainer upload diff -Nru libphp-phpmailer-6.1.5/debian/control libphp-phpmailer-6.1.6/debian/control --- libphp-phpmailer-6.1.5/debian/control 2020-04-22 22:11:37.0 +0200 +++ libphp-phpmailer-6.1.6/debian/control 2020-06-22 20:31:41.0 +0200 @@ -2,12 +2,12 @@ Section: php Priority: optional Maintainer: Debian PHP PEAR Maintainers -Uploaders: Kevin Coyner +Uploaders: Paul Gevers Build-Depends: debhelper (>= 7.4~), phpab, pkg-php-tools (>= 1.7~) Standards-Version: 3.9.7 Homepage: https://github.com/PHPMailer/PHPMailer -Vcs-Git: git://anonscm.debian.org/pkg-php/libphp-phpmailer.git -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-php/libphp-phpmailer.git +Vcs-Git: https://git.dgit.debian.org/libphp-phpmailer.git +Vcs-Browser: https://browse.dgit.debian.org/libphp-phpmailer.git Package: libphp-phpmailer Architecture: all signature.asc Description: OpenPGP digital signature
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
On Mon, Jun 22, 2020 at 19:46:21 +0200, Michael Meskes wrote: > > Depending on bsdmainutils to get col et al seems entirely right, it's > > been right forever, there doesn't seem to be a reason to break that > > both > > for dependent packages and for end users. Especially not without > > notice. > > There is no point arguing against your "do not change anything" > attitude. > I'm not saying don't change anything, I'm saying don't break stuff for users for no reason. Cheers, Julien
Processed: block 947551 with 963509
Processing commands for cont...@bugs.debian.org: > block 947551 with 963509 Bug #947551 [prospector] prospector: please, tighten the dependency of prospector on python3-pep8-naming 947551 was not blocked by any bugs. 947551 was not blocking any bugs. Added blocking bug(s) of 947551: 963509 > thanks Stopping processing here. Please contact me if you need assistance. -- 947551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962781: marked as done (containernetworking-plugins: may need Breaks+Replaces: rkt (<< ???))
Your message dated Mon, 22 Jun 2020 18:33:39 + with message-id and subject line Bug#962781: fixed in golang-github-containernetworking-plugins 0.8.6-2 has caused the Debian Bug report #962781, regarding containernetworking-plugins: may need Breaks+Replaces: rkt (<< ???) 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.) -- 962781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: containernetworking-plugins Version: 0.8.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../containernetworking-plugins_0.8.6-1_amd64.deb ... Unpacking containernetworking-plugins (0.8.6-1) ... dpkg: error processing archive /var/cache/apt/archives/containernetworking-plugins_0.8.6-1_amd64.deb (--unpack): trying to overwrite '/lib/systemd/system/cni-dhcp.service', which is also in package rkt 1.30.0+dfsg1-9 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/containernetworking-plugins_0.8.6-1_amd64.deb cheers, Andreas rkt=1.30.0+dfsg1-9_containernetworking-plugins=0.8.6-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: golang-github-containernetworking-plugins Source-Version: 0.8.6-2 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of golang-github-containernetworking-plugins, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated golang-github-containernetworking-plugins 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: Tue, 23 Jun 2020 01:29:55 +0800 Source: golang-github-containernetworking-plugins Architecture: source Version: 0.8.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Shengjing Zhu Closes: 962781 Changes: golang-github-containernetworking-plugins (0.8.6-2) unstable; urgency=medium . * Team upload. * Remove main package from -dev package. These packages can not be imported by others. * Stop building echosvr which is a test utility * Conflicts rkt (Closes: #962781) Both have cni-dhcp.service file * Bump debhelper-compat to 13 * Add autopkgtest which runs in isolation container * Fix package description format * Fix calling dh_installsystemd twice * Replace golang-ginkgo-dev with golang-github-onsi-ginkgo-dev golang-ginkgo-dev is transition package Checksums-Sha1: f030ba6bbb10534f765fab37fa6ebdd1c200581e 2617 golang-github-containernetworking-plugins_0.8.6-2.dsc 0a8d3694892e081a7dec18f2cb383706e43f26f0 4592 golang-github-containernetworking-plugins_0.8.6-2.debian.tar.xz 8378413dfdbee0a44b6d3dd27db1646573d969a9 7317 golang-github-containernetworking-plugins_0.8.6-2_amd64.buildinfo Checksums-Sha256: e5878e3e5cabfde2190abf5382ee6bcd4ad9332f4874938566ed39a633edc7cb 2617 golang-github-containernetworking-plugins_0.8.6-2.dsc f6dea0d47a32a8878277ec7a2b919a9608cb8fb024ee1257f744a18c6d3d3314 4592 golang-github-containernetworking-plugins_0.8.6-2.debian.tar.xz edf15b76e6229e06d0e9d8ff3723564df89c978bf47549a20e79f6f229c711e5 7317 golang-github-containernetworking-plugins_0.8.6-2_amd64.buildinfo Files: c18a563f28150364f1123d6bfdcce975 2617 devel optional golang-github-containernetworking-plugins_0.8.6-2.dsc 7e952ea802d876c08d2295258d17fd69 4592 devel optional golang-github-containernetworking-plugins_0.8.6-2.debian.tar.xz 97ac34832982c0e20dd7d1b7844b9734 7317 devel optional golang-github-containernetworking-plugins_0.8.6-2_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#963489: marked as done (dgit mirror ssh wrapper breaks due to rsync update)
Your message dated Mon, 22 Jun 2020 18:33:28 +
with message-id
and subject line Bug#963489: fixed in dgit 9.11
has caused the Debian Bug report #963489,
regarding dgit mirror ssh wrapper breaks due to rsync update
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.)
--
963489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dgit
Version: 9.10
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
Affects: rsync
Hi. Hello in particular to the rsync maintainers.
src:dgit contains a wrapper script which is intended for use in an ssh
restricted command invoked by rsync, as part of a mirroring setup.
Unfortunately there didn't seem to be better way of doing this than
having the wrapper script know what arguments the invoking rsync
likes to pass through ssh, and check that they are expected:
https://browse.dgit.debian.org/dgit.git/tree/infra/dgit-mirror-ssh-wrap
This means that when rsync changes, this script breaks. Most
recently (c from ci.debian.net logs):
unexpected command rsync --server -lHtre.iLsfxCIv --timeout=900 --delete
--safe-links .
/tmp/autopkgtest-lxc.osslg7ck/downtmp/autopkgtest_tmp/git-mirror/example.git
It was expecting something that matched this perl regexp:
m{^rsync --server -lHtre\.iLsfxC --timeout=\d+ --delete --safe-links \. $d$}
This situation is currently blocking migration of the new rsync (as is
to be expected, given that this wrapper is covered by the src:dgit's
autopkgtests).
This whole situation is not very good but it seemed the least bad
option to me. If the rsync maintainers have better suggestions I'm
all ears! (Whatever better solution is adopted would have to be
reviewed by DSA since it is part of the defence of a DSA-managed
machine.)
But for now, I am going to add this new set of options to the script
as a permitted pattern. I hope to make that upload today and that
should minimise the delay to rsync's migration.
Sorry for the inconvenience.
I have filed this bug as RC against dgit because that seems
appropriate under the circumstances. I doubt this will have any
practical effect because it is easy to fix and we (the dgit
maintainers) will fix it promptly. But it seems the proper conduct to
me.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 9.11
Done: Ian Jackson
We believe that the bug you reported is fixed in the latest version of
dgit, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ian Jackson (supplier of updated dgit 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, 22 Jun 2020 19:09:17 +0100
Source: dgit
Architecture: source
Version: 9.11
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson
Changed-By: Ian Jackson
Closes: 961682 961683 963489
Changes:
dgit (9.11) unstable; urgency=medium
.
Bugfixes:
* git-debrebase, git-debpush: fail when looking for upstream tag if
there is more than one candidate. Closes:#961682. [Sean Whitton]
* git-debrebase: Fix error message for wrong use of -i
* git-debrebase: new-upstream: Do not treat late options as version
.
Documentation:
* dgit-maint-debrebase(7): Drop some bad advice about the upstream/ tag
case. Closes:#961683. [Sean Whitton]
* git-debrebase(1): Fix new-upstream -i docs
.
dgit-infrastructure:
* dgit-mirror-ssh-wrap: Cope with new rsync rune. Closes:#963489.
* dgit-mirror-ssh-wrap: Clarify the error message
.
* Cope with buster & eatmydata (ie, work around #963508)
* Provide navigation banner in log when exiting nonzero
* Print pwd in failure trap to help with diagnosis
Checksums-Sha1:
5f53d87b7dac89ccae65693de30217a8f5481bd6 1846 dgit_9.11.dsc
9346b1c58293cbb3c5c1c8e1a7a14f67e95c7a55 694816 dgit_9.11.tar.gz
Checksums-Sha256:
Bug#963497: affects 963497
control: affects 963497 certbot thanks
Processed: affects 963497
Processing control commands: > affects 963497 certbot Bug #963497 [selinux-policy-default] selinux-policy-default: Let's Encrypt certbot tools crashed into Segmentation fault with SELinux Enforcing mode Added indication that 963497 affects certbot -- 963497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 947551 is grave
Processing commands for cont...@bugs.debian.org: > severity 947551 grave Bug #947551 [prospector] prospector: please, tighten the dependency of prospector on python3-pep8-naming Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 947551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unmerging 963353
Processing commands for cont...@bugs.debian.org:
> unmerge 963353
Bug #963353 {Done: Alastair McKinstry } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Ignoring request to unmerge a bug which is not merged with any others.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unmerging 963427
Processing commands for cont...@bugs.debian.org:
> unmerge 963427
Bug #963427 {Done: Roland Rosenfeld } [bsdmainutils]
bsdmainutils must depend on bsdextrautils
Ignoring request to unmerge a bug which is not merged with any others.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unmerging 963349
Processing commands for cont...@bugs.debian.org: > unmerge 963349 Bug #963349 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963306 [bsdmainutils] re2c: FTBFS: src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token Bug #963327 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963350 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963355 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963359 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963361 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963365 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963372 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963375 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963376 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963377 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963378 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963383 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963403 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963413 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963414 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963442 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963448 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963451 [bsdmainutils] bsdmainutils must depend on bsdextrautils Disconnected #963349 from all other report(s). > thanks Stopping processing here. Please contact me if you need assistance. -- 963306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963306 963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327 963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349 963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350 963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355 963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359 963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361 963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375 963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376 963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377 963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378 963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383 963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395 963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403 963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442 963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963495: affects 963495
control: affects 963495 reportbug thanks
Processed: affects 963495
Processing control commands: > affects 963495 reportbug Bug #963495 [selinux-policy-default] selinux-policy-default: reportbug Segmentation faulted when Selinux is in Enforcing mode Added indication that 963495 affects reportbug -- 963495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962827: libphp-phpmailer: CVE-2020-13625
Control: owner -1 ! Dear Debian PHP PEAR Maintainers, On Sun, 14 Jun 2020 21:23:30 +0200 Salvatore Bonaccorso wrote: > Source: libphp-phpmailer > Version: 6.1.5-0.1 > Severity: grave As it seems the team doesn't really care about libphp-phpmailer a lot, I intend to work on fixing this issue *and* adding myself as uploader. Unless somebody objects of course. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: libphp-phpmailer: CVE-2020-13625
Processing control commands: > owner -1 ! Bug #962827 [src:libphp-phpmailer] libphp-phpmailer: CVE-2020-13625 Owner recorded as Paul Gevers . -- 962827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960379: FTBFS again
Quoting Giovanni Mascellani (2020-06-22 18:40:50) > Bitcoin is FTBFSing again because of a missing dependency on > bsdextrautils (from which hexdump is used). Therefore I am uploading > another NMU fixing this. I am not delaying it, since I had no objections > on the first NMU and I believe this one to be uncontroversial. Thanks for your help! If you are interested, you are welcome to join the team and help maintain Bitcoin and related packages in general. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
> Depending on bsdmainutils to get col et al seems entirely right, it's > been right forever, there doesn't seem to be a reason to break that > both > for dependent packages and for end users. Especially not without > notice. There is no point arguing against your "do not change anything" attitude. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
Processed: [bts-link] source package src:haskell-http-conduit
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:haskell-http-conduit > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #962913 (http://bugs.debian.org/962913) > # Bug title: haskell-http-conduit: FTBFS on IPv6-only host > # * https://github.com/snoyberg/http-client/issues/400 > # * remote status changed: (?) -> closed > # * closed upstream > tags 962913 + fixed-upstream Bug #962913 [src:haskell-http-conduit] haskell-http-conduit: FTBFS on IPv6-only host Added tag(s) fixed-upstream. > usertags 962913 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 962913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963285: marked as done (libfreehand: FTBFS: libfreehand_utils.cpp:166:5: error: expected ‘;’ before ‘unsigned’)
Your message dated Mon, 22 Jun 2020 17:18:49 + with message-id and subject line Bug#963285: fixed in libfreehand 0.1.2-3 has caused the Debian Bug report #963285, regarding libfreehand: FTBFS: libfreehand_utils.cpp:166:5: error: expected ‘;’ before ‘unsigned’ 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.) -- 963285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libfreehand Version: 0.1.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. > -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -DLIBFREEHAND_BUILD=1 -I../../inc > -I/usr/include/librevenge-0.0-DNDEBUG -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -DUCHAR_TYPE=uint16_t -fvisibility=hidden > -DLIBFREEHAND_VISIBILITY -Wall -Wextra -Wshadow -pedantic -c -o > libfreehand_utils.lo libfreehand_utils.cpp > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -DLIBFREEHAND_BUILD=1 -I../../inc > -I/usr/include/librevenge-0.0 -DNDEBUG -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -DUCHAR_TYPE=uint16_t -fvisibility=hidden > -DLIBFREEHAND_VISIBILITY -Wall -Wextra -Wshadow -pedantic -c > libfreehand_utils.cpp -fPIC -DPIC -o .libs/libfreehand_utils.o > libfreehand_utils.cpp: In function ‘void > libfreehand::_appendUTF16(librevenge::RVNGString&, std::vector int>&)’: > libfreehand_utils.cpp:166:5: error: expected ‘;’ before ‘unsigned’ > 166 | unsigned char outbuf[U8_MAX_LENGTH+1]; > | ^~~~ > make[5]: *** [Makefile:583: libfreehand_utils.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/libfreehand_0.1.2-2_unstable.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: libfreehand Source-Version: 0.1.2-3 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of libfreehand, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated libfreehand 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 18:46:32 +0200 Source: libfreehand Architecture: source Version: 0.1.2-3 Distribution: unstable Urgency: medium Maintainer: Debian LibreOffice Maintainers Changed-By: Rene Engelhard Closes: 963285 Changes: libfreehand (0.1.2-3) unstable; urgency=medium . * debian/patches/icu-65-api-macros-with-semicolon.patch.1: import from LO master, fix build with ICU >= 65 (closes: #963285) Checksums-Sha1: 74a16f507c3b4050f3a91e01e1856444909020cf 2064 libfreehand_0.1.2-3.dsc 2dd4c0d76b1a5de436a300e9094484881db63eba 13488 libfreehand_0.1.2-3.debian.tar.xz 088040992d962fed8689909be845c9873e834770 6058 libfreehand_0.1.2-3_source.buildinfo Checksums-Sha256: b1894483d24c7551e1b2569bb3203863139c3941004de5565dd66f0de0c40adf 2064 libfreehand_0.1.2-3.dsc c54b337919ad5f0e748d1e21710d8cd310becef1ce4be4d04bd406f956435bb6 13488 libfreehand_0.1.2-3.debian.tar.xz b216d88b8ff388adf844f8250f8ac114ec71c6066a19785fea2174a50a7d99a3 6058 libfreehand_0.1.2-3_source.buildinfo Files: 623677b85414d72d1118407ec47b0d00 2064 libs optional libfreehand_0.1.2-3.dsc df7d14263cba37b1c54320aaef968f71 13488 libs optional libfreehand_0.1.2-3.debian.tar.xz 855e351afa1b9da198c2c05774f857d1 6058 libs optional libfreehand_0.1.2-3_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
On Mon, Jun 22, 2020 at 19:04:49 +0200, Michael Meskes wrote: > > I think it's probably best at this point to have bsdmainutils depend > > on > > bsdextrautils. That gets rid of the breakage in the place where it > > originated, and doesn't leave things without a transition path. > > I beg to disagree, there is a transition plan, namely depending on the > right package. Things change, that's what unstable is for. Depending on > bsdmainutils to get bsdextrautils does not sound right to me. > Depending on bsdmainutils to get col et al seems entirely right, it's been right forever, there doesn't seem to be a reason to break that both for dependent packages and for end users. Especially not without notice. Cheers, Julien
Bug#963377: xterm: FTBFS: /bin/sh: 1: col: not found
On 2020-06-21 17:11 -0400, Thomas Dickey wrote: > On Sun, Jun 21, 2020 at 10:13:41PM +0200, Lucas Nussbaum wrote: >> Source: xterm >> Version: 356-1 >> Severity: serious >> Justification: FTBFS on amd64 >> Tags: bullseye sid ftbfs >> Usertags: ftbfs-20200620 ftbfs-bullseye >> >> Hi, >> >> During a rebuild of all packages in sid, your package failed to build >> on amd64. > > col's in bsdmainutils It used to be there, but has recently been moved to bsdextrautils. This has caused a lot of breakage, so bsdmainutils ought to depend on bsdextrautils for the time being to fix that. However… >> > GROFF_NO_SGR=stupid /bin/sh -c "tbl ../ctlseqs.ms | groff -Tascii -ms | >> > col -bx" >../ctlseqs.txt >> > /bin/sh: 1: col: not found >> > make[2]: *** [Makefile:180: ../ctlseqs.txt] Error 127 > > refer to > > xterm (332-1) unstable; urgency=medium > > * Regenerate ctlseqs.txt from ctlseqs.ms (Closes: #848818). > > - Add groff to Buils-Depends. …I should also have added a build dependency on bsdmainutils there. That package is already pulled in via debhelper → man-db → bsdmainutils, so I overlooked it. I have just uploaded xterm 356-2 with bsdextrautils | bsdmainutils (<< 12.1.1~) added to Build-Depends. Cheers, Sven
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
> I think it's probably best at this point to have bsdmainutils depend > on > bsdextrautils. That gets rid of the breakage in the place where it > originated, and doesn't leave things without a transition path. I beg to disagree, there is a transition plan, namely depending on the right package. Things change, that's what unstable is for. Depending on bsdmainutils to get bsdextrautils does not sound right to me. We have to make the change eventually. And keep in mind that there may be other breakages as we changed sources for col et al. I am not aware of any, and I assume Chris isn't either, but there still may be some incompatibilities. I don't see the point of postponing the switch. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
> I don't know what Julien had in mind, presumably worried about other > breakage to surface. Note that obvious fix to man-db will all > debhelper > using packages transitively build-depending on bsdextrautils. Instead of bsdmainutils, yes. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
Processed: 963158
Processing commands for cont...@bugs.debian.org: > block 963158 with 963327 Bug #963158 [src:re2c] re2c: CVE-2020-11958 963158 was not blocked by any bugs. 963158 was not blocking any bugs. Added blocking bug(s) of 963158: 963350, 963403, 963413, 963414, 963442, 963306, 963451, 963375, 963355, 963359, 963365, 963378, 963361, 963349, 963395, 963448, 963383, 963376, 963377, 963327, and 963372 > End of message, stopping processing here. Please contact me if you need assistance. -- 963158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
On Mon, Jun 22, 2020 at 13:37:56 -0300, David Bremner wrote: > Michael Meskes writes: > > > On Mon, 2020-06-22 at 11:37 -0300, David Bremner wrote: > >> Michael Meskes writes: > >> > >> > > IMO the move of col needs to be rolled back ASAP. And, if it is > >> > > to > >> > > >> > Why? Care to give a reason? > >> > > >> > >> The change broke man-db, as I explained in a previous message. > > > > Oh, that I understand and I'm sorry I didn't notice that issue before, > > but why is rolling back preferable over fixing man-db? > > I don't know what Julien had in mind, presumably worried about other > breakage to surface. Note that obvious fix to man-db will all debhelper > using packages transitively build-depending on bsdextrautils. > I think it's probably best at this point to have bsdmainutils depend on bsdextrautils. That gets rid of the breakage in the place where it originated, and doesn't leave things without a transition path. Cheers, Julien
Bug#960379: FTBFS again
Bitcoin is FTBFSing again because of a missing dependency on bsdextrautils (from which hexdump is used). Therefore I am uploading another NMU fixing this. I am not delaying it, since I had no objections on the first NMU and I believe this one to be uncontroversial. Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature
Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error
Michael Meskes writes: > On Mon, 2020-06-22 at 11:37 -0300, David Bremner wrote: >> Michael Meskes writes: >> >> > > IMO the move of col needs to be rolled back ASAP. And, if it is >> > > to >> > >> > Why? Care to give a reason? >> > >> >> The change broke man-db, as I explained in a previous message. > > Oh, that I understand and I'm sorry I didn't notice that issue before, > but why is rolling back preferable over fixing man-db? I don't know what Julien had in mind, presumably worried about other breakage to surface. Note that obvious fix to man-db will all debhelper using packages transitively build-depending on bsdextrautils. d
Bug#949196: libzypp: diff for NMU version 17.7.0-1.1
Hi, Il 20/06/20 19:01, Mike Gabriel ha scritto: > Thanks for patching libzypp. Your NMU is ok, I will include your > .debdiff on its VCS. In fact, I am considering orphaning libzypp and > zypper in Debian. Do you have interest in taking over? Ugh, I just realized I stupidly embedded the amd64 architecture in my patch, leading to obvious FTBFS on the other archs. It is ok for you if I directly NMU libzypp replacing x86_64-linux-gnu with $(DEB_HOST_MULTIARCH)? Thanks, Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature
Processed: Re: libmu-dbm6: Tries to overwrite `libmu_dbm.so.6.0.0` from `libmailutils6`
Processing control commands: > severity -1 serious Bug #963211 [libmu-dbm6] libmu-dbm6: Tries to overwrite `libmu_dbm.so.6.0.0` from `libmailutils6` Severity set to 'serious' from 'normal' -- 963211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963481: marked as done (FTBFS: Missing symbols on buster-backports/amd64)
Your message dated Mon, 22 Jun 2020 15:49:58 + with message-id and subject line Bug#963481: fixed in spdlog 1:1.5.0+ds-5 has caused the Debian Bug report #963481, regarding FTBFS: Missing symbols on buster-backports/amd64 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.) -- 963481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spdlog Version: 1.5.0+ds-4 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Dear colleagues, Trying to perform a no-change rebuild of spdlog 1.5.0+ds-3 and -4 for buster-backports, I encountered the FTBFS on missing symbols. I opened a MR on Salsa against -3 fixing the build but it was somehow overlooked, maybe because I did not file the accompanying bug. Now I rebased the MR against med-team/spdlog master and I want to have it reviewed and merged. After the fixed build hits testing, I also would like to ask the maintainers to upload the backport for buster. This is required for Kodi package I am working on. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-106-generic (SMP w/6 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Regards, Vasyl --- End Message --- --- Begin Message --- Source: spdlog Source-Version: 1:1.5.0+ds-5 Done: cru...@debian.org (Michael R. Crusoe) We believe that the bug you reported is fixed in the latest version of spdlog, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated spdlog 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: SHA512 Format: 1.8 Date: Mon, 22 Jun 2020 17:20:18 +0200 Source: spdlog Architecture: source Version: 1:1.5.0+ds-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 961134 962089 963481 Changes: spdlog (1:1.5.0+ds-5) unstable; urgency=medium . [ Matthias Klose ] * Mark one more symbol as optional for ppc64 when building with -O3. Closes: #961134 . [ Michael R. Crusoe ] * Move libfmt-dev dependency from libspdlog1 to libspdlog-dev. Closes: #962089 * Adjust libspdlog1 symbols for buster-bpo/amd64. Closes: #963481 * Rules-Requires-Root: no (routine-update) * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. Checksums-Sha1: 077565bd876734dfbb29f442da54b4be65bb3258 2114 spdlog_1.5.0+ds-5.dsc 3a38f0eac6ea1877934167545731e7bbfe642da7 16348 spdlog_1.5.0+ds-5.debian.tar.xz fe4e533efd87f307d986961d1fc3aca7d301fbeb 7517 spdlog_1.5.0+ds-5_source.buildinfo Checksums-Sha256: 38cba76a5def41752a47d92ba7f32f5e4c96e9f2a1d1eaf58a41af9ff15933ab 2114 spdlog_1.5.0+ds-5.dsc 3b4f9da59a1a91469a0e8d9b4ffc390f6a99dbe9e4856fa2c2810936d031ea55 16348 spdlog_1.5.0+ds-5.debian.tar.xz 74671e61695adc4437c64320ac43519e67eefdafaebf4404ee1c0147d5689ac9 7517 spdlog_1.5.0+ds-5_source.buildinfo Files: 071ef0ffd69b9be4492ed08c5a7f92c2 2114 libdevel optional spdlog_1.5.0+ds-5.dsc b08471c574cad422b95ae4bb3a41f6cc 16348 libdevel optional spdlog_1.5.0+ds-5.debian.tar.xz 92305e9b41e9aa7e70c2790de7147273 7517 libdevel optional spdlog_1.5.0+ds-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl7wzEsACgkQPCZ2P2xn 5uICEw/+MoyL8QQMMV2DDf+TmGHmtVsfzEdBho+gzEvNsMGsaUKUMTFMPrBEn1bj BAaI49wUxNsmeNlWYtbdwB4QyazTUIR+l+O7Iqttb6FfzlTRhz9Y8zH1U0I4lg0e o/5zc2emjWbHoEynahUIcCf+5ttSsg5bkY32bdxYhaV2CVEXIZm1FE4PCNMPQu8F 8p9vOtCQ1YAOxsTEYjtSBEUYVs7B2HHbUgcD0HWpIUjPB7bmRpZOtxRQeCYgd9mG oBFX+1EhTv4zD5etIjYzihY09OaKcPVN3pTBt8795hN469JqH5BNB7SrDJy1BxqK 8RgtH6So5q3Zq9O1yYKA+oFaJ8UOA5x0Jh2gmy/O7/op/AwOPv6/kfmP6KR3ASsg
Bug#963430: Any volunteer to spent some time on the new version of artemis (Was: Bug#963430: artemis: FTBFS: /bin/sh: 1: /usr/share/java/j2ssh-core.jar: Permission denied)
Hi Emmanuel, Le 22/06/2020 à 16:30, Andreas Tille a écrit : > Hi Emmanuel, > > On Mon, Jun 22, 2020 at 10:57:15AM -0300, Emmanuel Arias wrote: >> I would be happy to help on artemis. Obviously I will need >> a more experienced developer helping me. :) > > I'll try hard to answer any question you might rise here on > this list (no matter how basic it might be) if you volunteer > to work on Artemis (or any other package). > > Thanks a lot for your commitment > > Andreas. > If you need it, I will be very happy to try to help you, based on my recent Java packaging tasks. All the best, Pierre
Bug#963501: haskell-wl-pprint-terminfo: Removal notice: broken and unmaintained
Source: haskell-wl-pprint-terminfo Version: 3.7.1.4-7 Severity: grave Justification: renders package unusable This package seems to be unmaintained (last upstream upload in 2016). It depends on the (broken) haskell-wl-pprint-extras, is not part of Stackage and has no rev dependencies. I intend to remove this package. -- Ilias
Bug#963499: haskell-wl-pprint-extras: Removal notice: broken and unmaintained
Source: haskell-wl-pprint-extras Version: 3.5.0.5-9 Severity: grave Justification: renders package unusable This package seems to be unmaintained (last upstream upload in 2015). Does not build with GHC 8.8 and is not part of Stackage. Its only rev-dep (haskell-wl-pprint-terminfo) is also unmaintained and should be removed. I intend to remove this package. -- Ilias
Bug#949196: marked as done (libzypp: FTBFS: cmake can't locate LibSolv)
Your message dated Mon, 22 Jun 2020 15:36:19 + with message-id and subject line Bug#949196: fixed in libzypp 17.7.0-1.1 has caused the Debian Bug report #949196, regarding libzypp: FTBFS: cmake can't locate LibSolv 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.) -- 949196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libzypp Version: 17.7.0-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid/amd64 chroot. Attached is the full build log, hopefully relevant excerpt follows: CMake Error at CMakeLists.txt:160 (FIND_PACKAGE): By not providing "FindLibSolv.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "LibSolv", but CMake did not find one. Could not find a package configuration file provided by "LibSolv" with any of the following names: LibSolvConfig.cmake libsolv-config.cmake Add the installation prefix of "LibSolv" to CMAKE_PREFIX_PATH or set "LibSolv_DIR" to a directory containing one of the above files. If "LibSolv" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! See also "/build/libzypp-17.7.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". See also "/build/libzypp-17.7.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log". make: *** [/usr/share/cdbs/1/class/cmake.mk:75: obj-x86_64-linux-gnu/CMakeCache.txt] Error 1 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- [0mI: Using pkgname logfile[0m [0mI: Current time: Fri Jan 17 22:15:24 UTC 2020[0m [0mI: pbuilder-time-stamp: 1579299324[0m [0mI: Obtaining the cached apt archive contents[0m [0mI: Copying source file[0m [0mI: copying [pkgs/libzypp_17.7.0-1.dsc][0m [0mI: copying [pkgs/libzypp_17.7.0.orig.tar.gz][0m [0mI: copying [pkgs/libzypp_17.7.0-1.debian.tar.xz][0m [0mI: Extracting source[0m gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error gpgv: Signature made Mon Sep 17 11:31:21 2018 UTC gpgv:using RSA key 9BFBAEE86C0AA5FFBF2207829AF46B3025771B31 gpgv:issuer "sunwea...@debian.org" gpgv: Can't check signature: No public key dpkg-source: warning: failed to verify signature on ./libzypp_17.7.0-1.dsc dpkg-source: info: extracting libzypp in libzypp-17.7.0 dpkg-source: info: unpacking libzypp_17.7.0.orig.tar.gz dpkg-source: info: unpacking libzypp_17.7.0-1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying 1002_cmake-module-path-fix.patch dpkg-source: info: applying 1003_various-typo-fixes.patch [0mI: using fakeroot in build.[0m [0mI: Installing the build-deps[0m [0mI: -> Attempting to satisfy build-dependencies[0m Note, using file '/build/libzypp_17.7.0-1.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: asciidoctor autoconf automake autopoint autotools-dev bsdmainutils ca-certificates cdbs cmake cmake-data debhelper dejagnu dh-autoreconf dh-strip-nondeterminism dirmngr doxygen dwz expect file fontconfig fontconfig-config fonts-dejavu-core gettext gettext-base gnupg gnupg-l10n gnupg-utils gnupg2 gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm graphviz groff-base icu-devtools intltool-debian libann0 libarchive-zip-perl libarchive13 libassuan-dev libassuan0 libboost-atomic1.67-dev libboost-atomic1.67.0 libboost-chrono1.67-dev libboost-chrono1.67.0 libboost-date-time1.67-dev libboost-date-time1.67.0 libboost-dev libboost-program-options-dev libboost-program-options1.67-dev libboost-program-options1.67.0 libboost-serialization1.67-dev libboost-serialization1.67.0 libboost-system1.67-dev libboost-system1.67.0 libboost-test-dev libboost-test1.67-dev libboost-test1.67.0 libboost-thread-dev libboost-thread1.67-dev libboost-thread1.67.0 libboost1.67-dev libbrotli1 libbsd0 libbz2-dev libcairo2 libcap2 libcdt5 libcgraph6 libclang1-9 libcroco3 libcurl4 libcurl4-openssl-dev
