Bug#865706: marked as done (haskell-http-link-header: FTBFS everywhere (except all))

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 03:49:35 +
with message-id 
and subject line Bug#865706: fixed in haskell-http-link-header 1.0.3-2
has caused the Debian Bug report #865706,
regarding haskell-http-link-header: FTBFS everywhere (except all)
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.)


-- 
865706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-http-link-header
Version: 1.0.3-1
Severity: serious

Hi,
haskell-http-link-header FTBFS on every architecture (other than all):

> Network.HTTP.Link
>   writeLinkHeader tests: : commitBuffer: invalid argument (invalid 
> character)
> Test suite tests: FAIL

Regards,
James
--- End Message ---
--- Begin Message ---
Source: haskell-http-link-header
Source-Version: 1.0.3-2

We believe that the bug you reported is fixed in the latest version of
haskell-http-link-header, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-http-link-header 
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, 23 Jun 2017 23:32:08 -0400
Source: haskell-http-link-header
Binary: libghc-http-link-header-dev libghc-http-link-header-prof 
libghc-http-link-header-doc
Architecture: source
Version: 1.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 libghc-http-link-header-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-http-link-header-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-http-link-header-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 865706
Changes:
 haskell-http-link-header (1.0.3-2) unstable; urgency=medium
 .
   * Run tests under C.UTF-8.  closes: #865706.
Checksums-Sha1:
 3e0c43067dc366a4de9be0820bf7725c38c8 3086 
haskell-http-link-header_1.0.3-2.dsc
 0f9ae3a3f96546edc62e625c81cec90a50898a9c 6250 
haskell-http-link-header_1.0.3.orig.tar.gz
 773c0028be57a8521900ad23259dc62210f99514 2660 
haskell-http-link-header_1.0.3-2.debian.tar.xz
 64bd988b2229df0bae9303d2d4b3163aaff7201f 8961 
haskell-http-link-header_1.0.3-2_source.buildinfo
Checksums-Sha256:
 b21d300175d5c10d309b347d7fc0bc6f2609e0c4516c70dea8f01d09a041c1cd 3086 
haskell-http-link-header_1.0.3-2.dsc
 59bd2db4e7d14b6f7ce86848af5e38b4bd2e9963e9ffe5068c7b1a710dbdd7fe 6250 
haskell-http-link-header_1.0.3.orig.tar.gz
 cb44cb08cd2b0af475824a68903f39ba5f51d93fd9186fa648022d31be33bc1f 2660 
haskell-http-link-header_1.0.3-2.debian.tar.xz
 154badf038d36040fdc89238c8124233d0f1e6cbeae9bb4b66c25a6ea06ea73c 8961 
haskell-http-link-header_1.0.3-2_source.buildinfo
Files:
 3c20c2828d4ab5caa9bf1aa9964a7406 3086 haskell extra 
haskell-http-link-header_1.0.3-2.dsc
 7b55652cf2b72593ef29a0b5b66a33f0 6250 haskell extra 
haskell-http-link-header_1.0.3.orig.tar.gz
 aaa784c96d1d391f6a33de01be59ab19 2660 haskell extra 
haskell-http-link-header_1.0.3-2.debian.tar.xz
 df7c509f57b35f0d9d5042fc3ab04ef3 8961 haskell extra 
haskell-http-link-header_1.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian!

iQKlBAEBCgCPFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAllN3ttfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1
ODFFQzg3NDA1M0U2QzgwNzc5MUI5QjU1OTIzMzFFMTk5RDM4QTgRHGNsaW50QGRl
Ymlhbi5vcmcACgkQVZIzHhmdOKiRVw/+NaOJx9XKYtEO7VYfpMo0bw0cPbhZrzYw
2jA5IQk6mP3Id6fzxa2T9Th2I5JsO1BU3RKo+0eH+thW+YQ1yOVmtD3iVdSWu30H
bqhicdprdlfu+BWOp6xFel1uFcrEtmVgy3e+jDQpc7hhlTJ1+eZEwKn9SPa85l6q
F8pU+gJd/Rh4VQw/BN9OPwA6eoiLWFHa+pk3moS4dviNZpx17X+Ri0KA/5dDbAXL
njviY8I3grkyOXcuapzPIU9DlVP2PyeNf29XtvUNqstH9fMh2B361BLjFz2GVjad
zfxq264y+FVa3y6iyf7PUWPC5f6zHUlVra/qjaU4NeYCYUg7IXZ+rLeSJt1TmbuS
rQI/c2GZC+gGBC9iUwwTZesb1YsYz+Llb/rqEMUBa0iUzbxl3HERYcY3bB6uibwZ
DUXPALnWUfkJBEaQ4OVDgUXr0dTiytX3o2YKcTXthbISEPK0OcSHVxbvvIO0lREG
fLNhYvVKws4+ig9hkQag1zbfsZNGTvhASzKR2oC7kqcAzqrOyGaUDhQm6zwlGr8Z
5ku+XleJifpq9X/K7uc26J+NiDyfvxrt0KfPRpmzbmVciA1QQHooS6zUu7Cl1kD1
S87u8t0bFC/0i6m6WdzJhss5O/SwJmcEzyVZyv5JR2UOax2w01CNHodk3GUtVihw
zE9GvJhW7NM=
=pzZF
-END PGP SIGNATURE

Bug#865712: ocaml: CVE-2017-9772: local privilege escalation issue with ocaml binaries

[Salvatore Bonaccorso]

Source: ocaml
Version: 4.04.0-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://caml.inria.fr/mantis/view.php?id=7557

Hi,

the following vulnerability was published for ocaml.

CVE-2017-9772[0]:
| Insufficient sanitisation in the OCaml compiler versions 4.04.0 and
| 4.04.1 allows external code to be executed with raised privilege in
| binaries marked as setuid, by setting the CAML_CPLUGINS,
| CAML_NATIVE_CPLUGINS, or CAML_BYTE_CPLUGINS environment variable.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-9772
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9772
[1] https://caml.inria.fr/mantis/view.php?id=7557

Regards,
Salvatore

Bug#865711: haskell-yaml: FTBFS everywhere (except all)

[James Clarke]

Source: haskell-yaml
Version: 0.8.23-2
Severity: serious

Hi,
haskell-yaml FTBFS on every architecture (except all) due to testsuite
failures:

> Failures:
>
>   test/Data/YamlSpec.hs:440:
>   1) Data.Yaml.Data.Yaml encode invalid numbers
>expected: ".\n"
> but got: ".\n...\n"
>
>   test/Data/YamlSpec.hs:458:
>   2) Data.Yaml.numbers integers have no decimals
>expected: "1\n"
> but got: "1\n...\n"
>
> Randomized with seed 1628861893

Regards,
James

Bug#865667: ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.

[Antonio Terceiro]

Control: tag -1 + unreproducible
Control: severity -1 important

On Fri, Jun 23, 2017 at 06:36:37PM +0300, Adrian Bunk wrote:
> Source: ruby-prof
> Version: 0.16.2+dfsg-2
> Severity: serious
> Tags: buster sid
> 
> Some recent change in unstable makes ruby-prof FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/ruby-prof.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-prof.html
> 
> ...

I just tried 10 times in a row here with sbuild, and all of them built
succesfully. can you try again?


signature.asc
Description: PGP signature

Processed: Re: Bug#865667: ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible
Bug #865667 [src:ruby-prof] ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.
Added tag(s) unreproducible.
> severity -1 important
Bug #865667 [src:ruby-prof] ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.
Severity set to 'important' from 'serious'

-- 
865667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#865675: yaml: breaks reverse-dependencies testsuites, and please move to github maintained repo.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #865675 [src:libyaml] yaml: breaks reverse-dependencies testsuites, and 
please move to github maintained repo.
Severity set to 'important' from 'serious'

-- 
865675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865675: yaml: breaks reverse-dependencies testsuites, and please move to github maintained repo.

[Gianfranco Costamagna]

control: severity -1 important
>I understand it's inconvenient, but it's not RC.  As long as you file another 
>bug, it won't get lost.


done :)
>Not so fast.
>
>Apparently all you looked at were autopkgtests.  Pyyaml runs the test suite 
>during build (although failures are non-fatal - I should probably change 
>that).
>
>Looking at the i386 build logs (common architecture with logs available for 
>both your PPA[1] and Debian[2]), I see zero test failures in Debian and four 
>in your PPA.  I don't think we're good on reverse-dependencies.
>
>I think this needs more investigation before you go ahead.


my assumption was that a failing testsuite makes the package FTBFS, I didn't 
check
build logs.

I opened an upstream ticket for this, thanks
https://github.com/yaml/libyaml/issues/60

I might end up in disabling the testsuite for the haskell package, in case the 
regression can't
be traced
(can you please ping maybe your upstream? it might be something that needs 
changed in pyyaml...)

G.

Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)

[gregor herrmann]

On Sun, 05 Feb 2017 10:24:24 +0800, Tommy Wu wrote:

> After upgrade to 1.05-1, sendxmpp program can't send message to googole 
> hangouts.
> 
> XML::Stream: SetCallBacks: tag(node) func(CODE(0x5567d6c2aa20))
> XMPP::Conn: xmppCallbackInit: start
> XMPP::Conn: SetCallBacks: tag(message) func(CODE(0x5567d6c2aaf8))
> XMPP::Conn: SetCallBacks: tag(presence) func(CODE(0x5567d6b19538))
> XMPP::Conn: SetCallBacks: tag(iq) func(CODE(0x5567d5bc4b68))
> XMPP::Conn: SetPresenceCallBacks: type(subscribe) func(CODE(0x5567d6c2a798))
> XMPP::Conn: SetPresenceCallBacks: type(unsubscribe) func(CODE(0x5567d6c2a720))
> XMPP::Conn: SetPresenceCallBacks: type(unsubscribed) 
> func(CODE(0x5567d6c2b068))
> XMPP::Conn: SetPresenceCallBacks: type(subscribed) func(CODE(0x5567d6c2b1d0))
> XMPP::Conn: SetDirectXPathCallBacks: 
> xpath(/[@xmlns="urn:ietf:params:xml:ns:xmpp-tls"]) func(CODE(0x5567d6bd6a48))
> XMPP::Conn: SetDirectXPathCallBacks: 
> xpath(/[@xmlns="urn:ietf:params:xml:ns:xmpp-sasl"]) func(CODE(0x5567d6c2aea0))
> XMPP::Conn: xmppCallbackInit: stop
> sendxmpp: ssl_verify: 1
> sendxmpp: tls_ca_path:

^^

> XMPP::Conn: Connect: host(talk.google.com:5222) namespace(jabber:client)
> XMPP::Conn: Connect: timeout(10)
> XML::Stream: Connect: srv requested
> XML::Stream: Connect: srv query failed
> XML::Stream: Connect: type(tcpip)
> Invalid or unreadable path specified for ssl_ca_path. at 
> /usr/share/perl5/XML/Stream.pm line 641.

^^
 
Looks like the path to the SSL cert(s) is empty.
I gues either sendxmpp should set it, or XML::Stream should use a
sane default.

For the latter see /usr/share/perl5/XML/Stream.pm:
223$self->{SIDS}->{default}->{ssl_ca_path} = '';  

Changing this value to '/etc/ssl/certs' might help.


I doubt that libnet-xmpp-perl is the problem here; the change between
1.02 and 1.05 is that it passes a defined ssl_ca_path on to
XML::Stream.


Ah, sendxmpp has an option tls-ca-path which is set to an empty
string if not passed on the command line. [0] In that case probably the
empty string somehow propagates down ...


Could one of the sendxmpp please try to call it with something like
--tls-ca-path="/etc/ssl/certs"
and see if this helps?
And/or change the above mentioned line in
/usr/share/perl5/XML/Stream.pm?
And/or change the line in sendxmpp mentioned in [0]?


If this is successful we still have to think where we should make
changes.


Cheers,
gregor


[0]
287'tls-ca-path' => ($tls_ca_path or ''),   

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Joint Venture: Er muß uns jetzt was singen


signature.asc
Description: Digital Signature

Bug#865706: haskell-http-link-header: FTBFS everywhere (except all)

[James Clarke]

Source: haskell-http-link-header
Version: 1.0.3-1
Severity: serious

Hi,
haskell-http-link-header FTBFS on every architecture (other than all):

> Network.HTTP.Link
>   writeLinkHeader tests: : commitBuffer: invalid argument (invalid 
> character)
> Test suite tests: FAIL

Regards,
James

Bug#865207: marked as done (texlive-latex-extra: File conflict due to missing Breaks/Replaces: trying to overwrite '/usr/share/texlive/texmf-dist/tex/latex/leipzig/leipzig.sty', which is also in packa

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 23:29:16 +
with message-id 
and subject line Bug#865207: fixed in texlive-extra 2017.20170623-1
has caused the Debian Bug report #865207,
regarding texlive-latex-extra: File conflict due to missing Breaks/Replaces: 
trying to overwrite 
'/usr/share/texlive/texmf-dist/tex/latex/leipzig/leipzig.sty', which is also in 
package texlive-humanities 2016.20170123-5
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.)


-- 
865207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-extra
Version: 2017.20170619-1
Severity: serious

Hi,

upgrading texlive-latex-extra fails as follows due to missing
Breaks/Replaces relation against texlive-humanities/2016.20170123-5:

Unpacking texlive-latex-extra (2017.20170619-1) over (2016.20170123-5) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-kJ66FC/23-texlive-latex-extra_2017.20170619-1_all.deb 
(--unpack):
 trying to overwrite 
'/usr/share/texlive/texmf-dist/tex/latex/leipzig/leipzig.sty', which is also in 
package texlive-humanities 2016.20170123-5
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages texlive-latex-extra depends on:
ii  preview-latex-style11.90-1
ii  tex-common 6.06
ih  texlive-base   2016.20170123-5
iu  texlive-binaries   2017.20170613.44572-2
iu  texlive-latex-recommended  2017.20170619-1
iu  texlive-pictures   2017.20170619-1

Versions of packages texlive-latex-extra recommends:
iu  texlive-fonts-recommended  2017.20170619-1
iu  texlive-generic-extra  2017.20170619-1
pn  texlive-latex-extra-doc

Versions of packages texlive-latex-extra suggests:
ii  libfile-which-perl  1.21-1
ii  libspreadsheet-parseexcel-perl  0.6500-1
ii  python-pygments 2.2.0+dfsg-1

Versions of packages tex-common depends on:
ii  dpkg  1.18.24
ii  ucf   3.0036

Versions of packages tex-common suggests:
ii  debhelper  10.2.5

Versions of packages texlive-latex-extra is related to:
ii  tex-common6.06
iu  texlive-binaries  2017.20170613.44572-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2017.20170623-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
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, 23 Jun 2017 23:00:30 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-plain-generic texlive-latex-extra 
texlive-fonts-extra texlive-music texlive-games texlive-pstricks 
texlive-publishers texlive-humanities texlive-science texlive-fonts-extra-doc 
texlive-humanities-doc texlive-latex-extra-doc texlive-science-doc 
texlive-pstricks-doc texlive-publishers-doc
Architecture: source all
Version: 2017.20170623-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting

Bug#864750: marked as done (texlive-base: dvipdfmx.def is broken)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 23:22:45 +
with message-id 
and subject line Bug#864750: fixed in texlive-base 2017.20170623-1
has caused the Debian Bug report #864750,
regarding texlive-base: dvipdfmx.def is broken
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.)


-- 
864750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base
Version: 2017.20170613-1
Severity: serious
Justification: broken


dvipdfmx.def is missing a }, so dvipdmfx is broken for now in experimental.
This is already fixed upstream, we need new packages.
--- End Message ---
--- Begin Message ---
Source: texlive-base
Source-Version: 2017.20170623-1

We believe that the bug you reported is fixed in the latest version of
texlive-base, 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 864...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-base 
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, 23 Jun 2017 22:59:24 +0900
Source: texlive-base
Binary: texlive-base texlive-latex-base texlive-latex-recommended 
texlive-fonts-recommended texlive-pictures texlive-luatex texlive-metapost 
texlive-xetex texlive-lang-african texlive-lang-indic 
texlive-generic-recommended texlive-generic-extra texlive-plain-extra 
texlive-htmlxml texlive-omega luasseq texlive texlive-full 
texlive-fonts-recommended-doc texlive-latex-base-doc 
texlive-latex-recommended-doc texlive-metapost-doc texlive-pictures-doc
Architecture: source all
Version: 2017.20170623-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 luasseq- TeX Live: transitional dummy package
 texlive- TeX Live: A decent selection of the TeX Live packages
 texlive-base - TeX Live: Essential programs and files
 texlive-fonts-recommended - TeX Live: Recommended fonts
 texlive-fonts-recommended-doc - TeX Live: Documentation files for 
texlive-fonts-recommended
 texlive-full - TeX Live: metapackage pulling in all components of TeX Live
 texlive-generic-extra - TeX Live: transitional dummy package
 texlive-generic-recommended - TeX Live: transitional dummy package
 texlive-htmlxml - TeX Live: transitional dummy package
 texlive-lang-african - TeX Live: transitional dummy package
 texlive-lang-indic - TeX Live: transitional dummy package
 texlive-latex-base - TeX Live: LaTeX fundamental packages
 texlive-latex-base-doc - TeX Live: Documentation files for texlive-latex-base
 texlive-latex-recommended - TeX Live: LaTeX recommended packages
 texlive-latex-recommended-doc - TeX Live: Documentation files for 
texlive-latex-recommended
 texlive-luatex - TeX Live: LuaTeX packages
 texlive-metapost - TeX Live: MetaPost and Metafont packages
 texlive-metapost-doc - TeX Live: Documentation files for texlive-metapost
 texlive-omega - TeX Live: transitional dummy package
 texlive-pictures - TeX Live: Graphics, pictures, diagrams
 texlive-pictures-doc - TeX Live: Documentation files for texlive-pictures
 texlive-plain-extra - TeX Live: transitional dummy package
 texlive-xetex - TeX Live: XeTeX and packages
Closes: 864750 865323
Changes:
 texlive-base (2017.20170623-1) unstable; urgency=medium
 .
   * new upstream checkout
 - graphics driver file use private version of space (Closes: #865323)
 - already closed long time ago, but not mentioned (Closes: #864750)
Checksums-Sha1:
 21a1b41281d2ff1519c4127a3a772c2cd4c90657 3095 texlive-base_2017.20170623-1.dsc
 c3fb0cbbb4f0bf3cd8336711c29cd016676f8c5d 294516196 
texlive-base_2017.20170623.orig.tar.xz
 e350f8c620c4bc9f9ffe68c0276771407032590f 13397360 
texlive-base_2017.20170623-1.debian.tar.xz
 31e08291cfa9c41659d9512666fe5d197d44fc7c 30428 luasseq_2017.20170623-1_all.deb
 1f43f793f04617be4022ae9758e1f3626f562b30 18690926 
texlive-base_2017.20170623-1_all.deb
 63cfe4c7eb2ffbf2b0fca15cc2f889584a1abdbc 12516 
texlive-base_2017.20170623-1_amd64.buildinfo
 cee0aaddd8fe1d5bad9b15a009ae437f8a600df2 2659466 
texlive-fonts-recommended-doc_2017.20170623-1_all.deb
 ad995e

Bug#865704: quiterss: Segfault at start

[Manolo Díaz]

Package: quiterss
Version: 0.18.4+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

quiterss has stopped working today with segfault. This is the backtrace:

GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
[...]
Reading symbols from quiterss...Reading symbols
from 
/usr/lib/debug/.build-id/f8/56a91f703d221d6dff53a307012d8aba8409be.debug...done.
done. (gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/quiterss 
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe427b700
(LWP 28117)]

Thread 1 "quiterss" received signal SIGSEGV, Segmentation fault.
QtPrivate::RefCount::ref (this=0x5571de80 )
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:61
61  /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h: No such
file or directory. (gdb) bt #0  QtPrivate::RefCount::ref
(this=0x5571de80 )
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:61 #1
QString::QString (other=..., this=0x7fffdf10,
this@entry=0x77debbdc )
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:901 #2
MainApplication::dataDir (this=0x7fffe650) at
src/application/mainapplication.cpp:337 #3  0x556586d8 in
LogFile::msgHandler (type=QtWarningMsg, msg=...) at
src/application/logfile.cpp:37 #4  0x7429b9d8 in ?? ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5  0x7429c86c in
QMessageLogger::warning(char const*, ...) const ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6  0x7fffe626091f in ??
() from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #7  0x7fffe6235015
in QXcbIntegration::createPlatformSessionManager(QString const&,
QString const&) const () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x749b5821 in
QSessionManager::QSessionManager(QGuiApplication*, QString&, QString&)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #9  0x749be655 in
QGuiApplicationPrivate::init() ()
from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x773c4879 in
QApplicationPrivate::init() ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x556e23c1 in
QtSingleApplication::QtSingleApplication (this=0x7fffe650,
argc=, argv=, GUIenabled=)
at 3rdparty/qtsingleapplication/qtsingleapplication.cpp:155 #12
0x55657594 in MainApplication::MainApplication
(this=0x7fffe650, argc=@0x7fffe64c: 1, argv=) at
src/application/mainapplication.cpp:41 #13 0x5559e924 in main
(argc=, argv=0x7fffe818) at src/main/main.cpp:33
(gdb)


And this is the list of package previously installed/upgraded in my PC:

Install:
gcc-7-base:amd64 (7.1.0-7, automatic)
libhunspell-1.6-0:amd64 (1.6.1-2, automatic)

Upgrade:
borgbackup-doc:amd64 (1.0.9-1, 1.0.10-3)
borgbackup:amd64 (1.0.9-1, 1.0.10-3)
enchant:amd64 (1.6.0-11+b1, 1.6.0-11+b2)
hunspell:amd64 (1.4.1-2+b2, 1.6.1-2)
libatomic1:amd64 (6.3.0-18, 7.1.0-7)
libcc1-0:amd64 (6.3.0-18, 7.1.0-7)
libcilkrts5:amd64 (6.3.0-18, 7.1.0-7)
libdiscid0:amd64 (0.6.1-6, 0.6.2-2)
libdvbpsi10:amd64 (1.3.0-5, 1.3.1-2)
libenchant1c2a:amd64 (1.6.0-11+b1, 1.6.0-11+b2)
libgcc1-dbg:amd64 (1:6.3.0-18, 1:7.1.0-7)
libgcc1:amd64 (1:6.3.0-18, 1:7.1.0-7)
libgcrypt20:amd64 (1.7.6-2, 1.7.7-2)
libglpk40:amd64 (4.61-1, 4.62-1)
libgomp1:amd64 (6.3.0-18, 7.1.0-7)
libitm1:amd64 (6.3.0-18, 7.1.0-7)
liblsan0:amd64 (6.3.0-18, 7.1.0-7)
libmpg123-0:amd64 (1.23.8-1+b1, 1.25.0-1)
libmpx2:amd64 (6.3.0-18, 7.1.0-7)
libnspr4:amd64 (2:4.12-6, 2:4.15-1)
libnss3:amd64 (2:3.26.2-1.1, 2:3.31-1)
libpcsclite1:amd64 (1.8.20-1, 1.8.22-1)
libpng16-16:amd64 (1.6.28-1, 1.6.29-3)
libquadmath0:amd64 (6.3.0-18, 7.1.0-7)
libsnappy1v5:amd64 (1.1.3-3, 1.1.4-2)
libstdc++6:amd64 (6.3.0-18, 7.1.0-7)
libtasn1-6:amd64 (4.10-1.1, 4.12-2)
libtsan0:amd64 (6.3.0-18, 7.1.0-7)
libubsan0:amd64 (6.3.0-18, 7.1.0-7)
libwavpack1:amd64 (5.0.0-2, 5.1.0-1)
netcat-openbsd:amd64 (1.130-3, 1.178-1)
openssh-client:amd64 (1:7.4p1-10, 1:7.5p1-5)
pcscd:amd64 (1.8.20-1, 1.8.22-1)
postfix-sqlite:amd64 (3.1.4-7, 3.2.2-1)
postfix:amd64 (3.1.4-7, 3.2.2-1)
python3-prompt-toolkit:amd64 (1.0.9-1, 1.0.14-1)
qt5-style-plugins:amd64 (5.0.0+git16.g7aa4764-1, 5.0.0+git23.g335dbec-1)
wavpack:amd64 (5.0.0-2, 5.1.0-1)




-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.6 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked
to /usr/bin/dash Init: systemd (via /run/systemd/system)

Versions of packages quiterss depends on:
ii  libc6 2.24-12
ii  libgcc1   1:7.1.0-7
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5multimedia5 5.7.1~20161021-2
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite  

Processed: Re: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)

[Debian Bug Tracking System]

Processing control commands:

> severity 854210 serious
Bug #854210 [libnet-xmpp-perl] libnet-xmpp-perl: sendxmpp can't send message to 
hangouts (work fine for 1.02-5)
Severity set to 'serious' from 'important'

-- 
854210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: merge

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 850033 865702
Bug #850033 [libepoxy0] libepoxy0: Segmentation fault, fixed upstream
Bug #865702 [libepoxy0] libepoxy: Patch causing serious issues on amdgpu-pro
Severity set to 'important' from 'critical'
Marked as found in versions libepoxy/1.3.1-1.
Added tag(s) patch.
Bug #850033 [libepoxy0] libepoxy0: Segmentation fault, fixed upstream
Marked as found in versions libepoxy/1.3.1-2.
Merged 850033 865702
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
850033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850033
865702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865702: libepoxy: Patch causing serious issues on amdgpu-pro

[Jérémy Lal]

Package: libepoxy0
Version: 1.3.1-2
Severity: critical
File: libepoxy
Justification: breaks the whole system

2017-06-23 23:54 GMT+02:00 Gianfranco Costamagna :
Hello, just FYI, a patch you included in the Debian packaging is causing some 
serious issues on amdgpu-pro
devices
https://github.com/anholt/libepoxy/issues/130
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1698233


please consider reverting it, something I'm doing right now for Ubuntu builds


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (1001, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libepoxy0:amd64 depends on:
ii  libc6  2.24-12

libepoxy0:amd64 recommends no packages.

libepoxy0:amd64 suggests no packages.

-- no debconf information

Bug#865692: sprng hides build failures

[Dirk Eddelbuettel]

On 23 June 2017 at 22:37, Helmut Grohne wrote:
| Source: sprng
| Version: 2.0a-2
| Severity: serious
| Justification: policy 4.6
| User: helm...@debian.org
| Usertags: rebootstrap
| 
| sprng's build system hides build failures. It's Makefile uses
| constructs such as:
| 
| (cd $somewhere; $(MAKE); cd ..)
| 
| If there is a failure in the submake, it is not propagated and the build
| continues. This violates Debian Policy section 4.6. For chaining shell
| commands, "set -e" should be used. In this case however, "$(MAKE) -C
| $somedir" would be even better.

Uh-oh. Guilty as charged.

It's a super-old package I needed way back when we had no other parallel RNG.
And it had a horrid build system I needed to wrestle with back then when.

In short: can you take a closer look and maybe suggest a patch?

Tschoe,  Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#865675: yaml: breaks reverse-dependencies testsuites, and please move to github maintained repo.

[Scott Kitterman]

On Friday, June 23, 2017 08:18:44 PM Gianfranco Costamagna wrote:
> Hello Scott!
> 
> >I'm not the maintainer, just an interest maintainer of a reverse
> >dependency.
> thanks for your caring (help and feedbacks are appreciated a lot!) :)
> 
> >First, all the home page changes are inappropriate for an NMU.  I would
> >recommend you file a separate, normal priority, bug about those issues.
> 
> well, since I spent almost a day trying to understand where upstream did
> take the patches (because haskell builds with the embedded haskell-yaml
> package), I prefer to make sure nobody else looses his time :)
> (I also bothered upstream to change the repo location from the wiki BTW)

I understand it's inconvenient, but it's not RC.  As long as you file another 
bug, it won't get lost.

> >Second, have you checked if this breaks anything else?
> 
> right now, reverse-deps testsuites are not affected by this upload
...
> >I'm particularly concerned you  don't break pyyaml (since I maintain that
> >one).  Before NMUing, I think you should make sure you aren't trading one
> >broken package for another.
> 
> actually the fix has been originally intended to unbreak the python binding
> of yaml (some of them has a testsuite broken, maybe not pyyaml, or maybe not
> right now, but some python binding should be broken without this patch,
> aswell as the haskell one)
> 
> 
> I did a test rebuild in a ppa (most of the versions are in sync with
> Debian), and I didn't get any build failures.
> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfr
> anco-ppa/+packages
> 
> so, I can say that we should be good with this one, at least if
> reverse-dependencies testsuites are good enough :p

Not so fast.

Apparently all you looked at were autopkgtests.  Pyyaml runs the test suite 
during build (although failures are non-fatal - I should probably change 
that).

Looking at the i386 build logs (common architecture with logs available for 
both your PPA[1] and Debian[2]), I see zero test failures in Debian and four 
in your PPA.  I don't think we're good on reverse-dependencies.

I think this needs more investigation before you go ahead.

Scott K

[1] 
https://launchpadlibrarian.net/325269141/buildlog_ubuntu-artful-i386.pyyaml_3.12-1build2_BUILDING.txt.gz
[2] 
https://buildd.debian.org/status/fetch.php?pkg=pyyaml&arch=i386&ver=3.12-1&stamp=1472969660&raw=0

Processed: affects 865563

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 865563 src:libcatmandu-sru-perl
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Added indication that 865563 affects src:libcatmandu-sru-perl
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865563: libcatmandu-sru-perl FTBFS: test failures

[gregor herrmann]

Control: reassign -1 libmodule-build-perl 0.422400-1
Control: forwarded -1 
https://github.com/Perl-Toolchain-Gang/Module-Build/issues/77
Control: affects src:libcatmandu-sru-perl

On Fri, 23 Jun 2017 21:19:43 +0100, Dominic Hargreaves wrote:

> On Fri, Jun 23, 2017 at 07:43:52PM +0200, gregor herrmann wrote:

> > I didn't have any success when playing with the new $dot_in_inc_code
> > string, seems like the condition is never met. (And to be honest, I
> > don't understand the logic ...) [0]
[..]

> > [0]
> > my $dot_in_inc_code = $INC[-1] eq '.' ? <<'END' : '';
> > if ($INC[-1] ne '.') {
> > push @INC, '.';
> > }
> > END
> > 
> > What also works is reverting the logic:
> > 
> > --- /usr/share/perl5/Module/Build/Base.pm~  2017-06-19 17:25:18.0 
> > +
> > +++ /usr/share/perl5/Module/Build/Base.pm   2017-06-23 17:42:01.820466942 
> > +
> > @@ -1824,7 +1824,7 @@
> >my $shebang = $self->_startperl;
> >my $magic_number = $self->magic_number;
> >  
> > -my $dot_in_inc_code = $INC[-1] eq '.' ? <<'END' : '';
> > +my $dot_in_inc_code = $INC[-1] ne '.' ? <<'END' : '';
> >  if ($INC[-1] ne '.') {
> >  push @INC, '.';
> >  }
> > 
> > 
> > Then PERL_USE_UNSAFE_INC is not needed. But testing $INC[-1] ne '.'
> > two times make as little sense to me as first testing eq '.' and then ne '.'
> > ...
> 
> It does rather look like a mistaken attempt to solve this problem, and
> I agree that the logic is a bit odd, but this seems like the patch
> likely to get accepted upstream; can you send this patch to the module
> author?

Done. Cf. the GH issue URL at the top.
 
> I feel like we should try and not diverge further from upstream; that
> seems almost guaranteed to end up with similar issues later.

Ack.

Thanks for looking into this!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Neal Casal: Raining Straight Down


signature.asc
Description: Digital Signature

Processed (with 1 error): Re: Bug#865563: libcatmandu-sru-perl FTBFS: test failures

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libmodule-build-perl 0.422400-1
Bug #865563 [src:libcatmandu-sru-perl] libcatmandu-sru-perl FTBFS: test failures
Bug reassigned from package 'src:libcatmandu-sru-perl' to 
'libmodule-build-perl'.
No longer marked as found in versions libcatmandu-sru-perl/0.039-1.
Ignoring request to alter fixed versions of bug #865563 to the same values 
previously set
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Marked as found in versions libmodule-build-perl/0.422400-1.
> forwarded -1 https://github.com/Perl-Toolchain-Gang/Module-Build/issues/77
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Set Bug forwarded-to-address to 
'https://github.com/Perl-Toolchain-Gang/Module-Build/issues/77'.
> affects src:libcatmandu-sru-perl
Unknown command or malformed arguments to command.


-- 
865563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865692: sprng hides build failures

[Helmut Grohne]

Source: sprng
Version: 2.0a-2
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

sprng's build system hides build failures. It's Makefile uses
constructs such as:

(cd $somewhere; $(MAKE); cd ..)

If there is a failure in the submake, it is not propagated and the build
continues. This violates Debian Policy section 4.6. For chaining shell
commands, "set -e" should be used. In this case however, "$(MAKE) -C
$somedir" would be even better.

Helmut

Bug#865675: yaml: breaks reverse-dependencies testsuites, and please move to github maintained repo.

[Gianfranco Costamagna]

Hello Scott!


>I'm not the maintainer, just an interest maintainer of a reverse dependency.


thanks for your caring (help and feedbacks are appreciated a lot!) :)
>First, all the home page changes are inappropriate for an NMU.  I would 
>recommend you file a separate, normal priority, bug about those issues.


well, since I spent almost a day trying to understand where upstream did take
the patches (because haskell builds with the embedded haskell-yaml package),
I prefer to make sure nobody else looses his time :)
(I also bothered upstream to change the repo location from the wiki BTW)

>Second, have you checked if this breaks anything else?


right now, reverse-deps testsuites are not affected by this upload
autopkgtest for appstream/0.10.6-2: amd64: Pass, armhf: Pass, i386: Pass, 
ppc64el: Pass, s390x: Pass
autopkgtest for choreonoid/1.5.0+dfsg-0.1build2: amd64: Always failed, i386: 
Always failed, ppc64el: Always failed, s390x: Always failed
autopkgtest for haskell-yesod-bin/1.4.18.7-3: amd64: Always failed, armhf: Test 
in progress (always failed), i386: Always failed, ppc64el: Always failed, 
s390x: Always failed
autopkgtest for nplan/0.24: amd64: Pass, armhf: Pass, i386: Test in progress, 
ppc64el: Test in progress, s390x: Pass
autopkgtest for pyyaml/3.12-1build1: amd64: Pass, armhf: Pass, i386: Pass, 
ppc64el: Pass, s390x: Pass
autopkgtest for ruby2.3/2.3.3-1ubuntu1: amd64: Test in progress (always 
failed), armhf: Test in progress, i386: Always failed, ppc64el: Always failed, 
s390x: Pass
autopkgtest for suricata/3.2-2ubuntu2: amd64: Pass, armhf: Pass, i386: Pass, 
ppc64el: Pass, s390x: Pass 
>* appstream
>* appstream-glib
>* choreonoid
>* dvbstreamer
>* erlang-p1-yaml
>* flvmeta
>* haskell-yaml
>* hhvm
>* hkl
>* liblouis
>* limba
>* lua-yaml
>* nutcracker
>* php-yaml
>* pyyaml
>* r-cran-yaml
>* ruby2.3
>* suricata
>* tarantool
>* uwsgi
>* v-sim
>* vboot-utils

>I'm particularly concerned you  don't break pyyaml (since I maintain that 
>one).  Before NMUing, I think you should make sure you aren't trading one 
>broken package for another.


actually the fix has been originally intended to unbreak the python binding
of yaml (some of them has a testsuite broken, maybe not pyyaml, or maybe not 
right now,
but some python binding should be broken without this patch, aswell as the 
haskell
one)


I did a test rebuild in a ppa (most of the versions are in sync with Debian),
and I didn't get any build failures.
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa/+packages

so, I can say that we should be good with this one, at least if 
reverse-dependencies
testsuites are good enough :p

thanks!


G.


signature.asc
Description: PGP signature

Bug#865563: libcatmandu-sru-perl FTBFS: test failures

[Dominic Hargreaves]

On Fri, Jun 23, 2017 at 07:43:52PM +0200, gregor herrmann wrote:
> On Fri, 23 Jun 2017 17:22:52 +0200, gregor herrmann wrote:
> 
> > > So what is not there anymore is PERL_USE_UNSAFE_INC=1.
> > 
> > Dom, I think you're our expert on dot-in-inc; do you think my hunch
> > is correct that we need to add PERL_USE_UNSAFE_INC back?
> > (And if yes, where would be the best place - in the $dot_in_inc_code,
> > and if yes within the if(); or after $dot_in_inc_code is output in
> > the second hunk of the above diff?
> 
> So this seems to work (as in: libcatmandu-sru-perl builds again, if I
> change /usr/share/perl5/Module/Build/Base.pm in the chroot):
> 
> --- a/lib/Module/Build/Base.pm
> +++ b/lib/Module/Build/Base.pm
> @@ -1866,6 +1866,7 @@ BEGIN {
>  $quoted_INC
>  );
>  $dot_in_inc_code
> +\$ENV{"PERL_USE_UNSAFE_INC"} = 1;
>  }
> 
>  close(*DATA) unless eof(*DATA); # ensure no open handles to this script
> 
> 
> I didn't have any success when playing with the new $dot_in_inc_code
> string, seems like the condition is never met. (And to be honest, I
> don't understand the logic ...) [0]
> 
> So it looks like we really need PERL_USE_UNSAFE_INC, and we might
> want to insert it unconditionally manually where we did prior to the
> accidental removal in the last upload.
> 
> 
> Cheers,
> gregor
> 
> [0]
> my $dot_in_inc_code = $INC[-1] eq '.' ? <<'END' : '';
> if ($INC[-1] ne '.') {
> push @INC, '.';
> }
> END
> 
> What also works is reverting the logic:
> 
> --- /usr/share/perl5/Module/Build/Base.pm~2017-06-19 17:25:18.0 
> +
> +++ /usr/share/perl5/Module/Build/Base.pm 2017-06-23 17:42:01.820466942 
> +
> @@ -1824,7 +1824,7 @@
>my $shebang = $self->_startperl;
>my $magic_number = $self->magic_number;
>  
> -my $dot_in_inc_code = $INC[-1] eq '.' ? <<'END' : '';
> +my $dot_in_inc_code = $INC[-1] ne '.' ? <<'END' : '';
>  if ($INC[-1] ne '.') {
>  push @INC, '.';
>  }
> 
> 
> Then PERL_USE_UNSAFE_INC is not needed. But testing $INC[-1] ne '.'
> two times make as little sense to me as first testing eq '.' and then ne '.'
> ...

It does rather look like a mistaken attempt to solve this problem, and
I agree that the logic is a bit odd, but this seems like the patch
likely to get accepted upstream; can you send this patch to the module
author?

I feel like we should try and not diverge further from upstream; that
seems almost guaranteed to end up with similar issues later.

Cheers,
Dominic.

Bug#865552: libbpp-phyl FTBFS with test failures

[Andreas Tille]

Hi Julien,

On Fri, Jun 23, 2017 at 09:02:30PM +0200, Julien Yann Dutheil wrote:
> This is most strange indeed. The errors are all "time out" errors on unit
> tests which take the longest time (several min or so). Looks like some
> issues with the default value for the timeout setting in CTest... I would
> suggest to simply skip the unit tests by running "cmake
> -DBUILD_TESTING=FALSE ." .  Does this solve the problem?

Hmmm, this would most probably lead to successfully built packages but I
would prefer spending some additional thoughts on this.  It would
explain the issue why the package has built before but does not any more
without any visible change on "weak" architectures.  I could imagine
that after stretch release the run on the build servers increased and
that possibly parallel builds are happening which lead to performance
loss for single packages.
 
Do you see any chance to increase the timeout settings by one order of
magnitude to test this hypothesis?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#865552: libbpp-phyl FTBFS with test failures

[Julien Yann Dutheil]

Dear Andreas, Adrian,

This is most strange indeed. The errors are all "time out" errors on unit
tests which take the longest time (several min or so). Looks like some
issues with the default value for the timeout setting in CTest... I would
suggest to simply skip the unit tests by running "cmake
-DBUILD_TESTING=FALSE ." .  Does this solve the problem?

Best regards,

Julien.

On Fri, Jun 23, 2017 at 1:38 PM, Andreas Tille  wrote:

> Hi Adrian,
>
> thanks a lot for your continuous QA effort (I have the feeling that 90%
> of the Debian Med bugs were issued by you ;-) ).
>
> Julien, do you have some explanation for the issue?  I made sure that
> cmake files were found also on i386 so the issue now concerns
>Version: 2.3.1-3
> but bpp-phyl seems to have issues for non-Intel architectures which
> should be dealt by upstream.  I admit that I have not checked version
> 2.3.1-1 but according to Git the diff is
>
>
> $ git diff debian/2.3.1-1..debian/2.3.1-2
> diff --git a/debian/changelog b/debian/changelog
> index 0bfd365..28fd024 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,9 @@
> +libbpp-phyl (2.3.1-2) unstable; urgency=medium
> +
> +  * Make sure cmake files will be installed also on i386
> +
> + -- Andreas Tille   Thu, 22 Jun 2017 08:03:24 +0200
> +
>  libbpp-phyl (2.3.1-1) unstable; urgency=medium
>
>* New upstream version
> diff --git a/debian/rules b/debian/rules
> index 9d1fe92..3a46afc 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -15,5 +15,5 @@ override_dh_install:
> --override 
> 's/libbpp-\([-a-z]\+\)[0-9]\+-dev/libbpp-\1-dev/'
> \
> --exclude-la \
>  --movedev debian/tmp/usr/include/* usr/include \
> ---movedev debian/tmp/usr/lib/$(DEB_HOST_GNU_TYPE)/cmake
> usr/lib/$(DEB_HOST_GNU_TYPE) \
> +--movedev debian/tmp/usr/lib/*/cmake
> usr/lib/$(DEB_HOST_GNU_TYPE) \
>  debian/tmp/usr/lib/*/*.so
>
>
> So I can not see any explanation for the test failures since the test is
> run before dh_install anyway.  I suspect some deeper issue here.
>
> Kind regards
>
>   Andreas.
>
> On Thu, Jun 22, 2017 at 08:13:02PM +0300, Adrian Bunk wrote:
> > Source: libbpp-phyl
> > Version: 2.3.1-2
> > Severity: serious
> >
> > https://buildd.debian.org/status/package.php?p=libbpp-phyl&suite=sid
> >
> > I do not see any obvious reason why 2.3.1-2 fails on so many
> > architectures where 2.3.1-1 built just a few hours earlier.
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#865522: scilab: Segmentation fault at lauch

[Sylvestre Ledru]

I forwarded the bug to upstream. I think they will work on this very soon.

S


Le 23/06/2017 à 20:58, Marcio Bezerra a écrit :
> Looks like this bug was introduced in the latest kernel libraries
> update. Scilab was working just fine less than 24 hours ago.
> Scilab-cli is working but is very limited. Does anyone know of a
> workaround for this kind of problem? How long does it usually take for
> them to release a patch?
>
> I have downloaded Octave but it's not the same.
>
> Much appreciated.
>
> Marcio 
>
> On Fri, Jun 23, 2017 at 3:24 PM, trb  > wrote:
>
> I have the same bug on Debian 9 with KDE Plasma.
> I had the same problem on Arch, maybe this is related to the
> kernel ? (
> https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1699892
>  )
>
> Best regards,
> Piotr
>
>
>
>
> -- 
>
> Márcio B. D. Bezerra

Bug#865522: scilab: Segmentation fault at lauch

[Marcio Bezerra]

Looks like this bug was introduced in the latest kernel libraries update.
Scilab was working just fine less than 24 hours ago. Scilab-cli is working
but is very limited. Does anyone know of a workaround for this kind of
problem? How long does it usually take for them to release a patch?

I have downloaded Octave but it's not the same.

Much appreciated.

Marcio

On Fri, Jun 23, 2017 at 3:24 PM, trb  wrote:

> I have the same bug on Debian 9 with KDE Plasma.
> I had the same problem on Arch, maybe this is related to the kernel ? (
> https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1699892 )
>
> Best regards,
> Piotr
>



-- 

Márcio B. D. Bezerra

Bug#865317: marked as done (miller FTBFS on mips: FAIL run (exit status: 1))

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 18:35:18 +
with message-id 
and subject line Bug#865317: fixed in miller 5.2.1-3
has caused the Debian Bug report #865317,
regarding miller FTBFS on mips: FAIL run (exit status: 1)
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.)


-- 
865317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: miller
Version: 5.2.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=miller&suite=sid

...
Tests completed: 2713
FAIL run (exit status: 1)


Testsuite summary for mlr 5.2.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See c/reg_test/test-suite.log

Makefile:665: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1
...


The same build failure on powerpc is an indication that it
could be a 32bit big endian problem.
--- End Message ---
--- Begin Message ---
Source: miller
Source-Version: 5.2.1-3

We believe that the bug you reported is fixed in the latest version of
miller, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated miller 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, 23 Jun 2017 20:11:47 +0200
Source: miller
Binary: miller
Architecture: source
Version: 5.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 miller - name-indexed data processing tool
Closes: 865317
Changes:
 miller (5.2.1-3) unstable; urgency=medium
 .
   * Add a further upstream fix for the %d integer size issue.
 Closes: #865317.
Checksums-Sha1:
 4129eed7c412131d81016e334ff5a094645fd16b 1830 miller_5.2.1-3.dsc
 2e69f59bbebbc92d870fee689189695fd8f26f00 5136 miller_5.2.1-3.debian.tar.xz
 750dec9115ae78be4067fd4dc2c8dd6da18ad722 5748 miller_5.2.1-3_source.buildinfo
Checksums-Sha256:
 55ecfe0bb6e00a5458b97194dc271e2fde7363b9c3462bfb8fb23b067f042ff3 1830 
miller_5.2.1-3.dsc
 20c05fe8f3a8451abd815a0fa3d457e0efcbc6b16ef6ac2969061d7447fd05dc 5136 
miller_5.2.1-3.debian.tar.xz
 90993e8ae5dc62fff78591fb50da8b61cd2c3a8c34d74052a879f427d39c195e 5748 
miller_5.2.1-3_source.buildinfo
Files:
 78bf0aa366c2ebf407d31807ae99f167 1830 utils optional miller_5.2.1-3.dsc
 8d7ca54360baea7d956f072b1d52871f 5136 utils optional 
miller_5.2.1-3.debian.tar.xz
 c15c70080eccb4b29dc039a3fccb0d6b 5748 utils optional 
miller_5.2.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAllNWfkACgkQgNMC9Yht
g5wJtw//U3TpgWRX/CAbGGmaujqXYuXbiF8iAtYx9rwKHFcmez0DuxSNX/l18fS+
SPAw/KnDVwQR8tyDowP9hokMpN+NYk2Y+6oxNvUWcFhLheNGhRYTCAeCK6r4E3Ug
Fr9VTaaQ9X62bwklQs5sBD7siwiXHIspqYwxKhv2rFeFmUm56IijUQYjPvbQ0bhv
rhJ/09sLTK7XLMBWZoijXfTlYCKiAhUaamYvnBvmaj5zO8SPTKbSm6Jntw1jeA5H
th8nwIAuM1wgq4q/sBaRigSDVNt+4/7oEG9553gYiq/1d385PR1vKXjV9IRmUNJ8
DjAzG4W1n+gu9oOt7yBQse+YdJ/EXwzmgv6PEL5xfHelL9m9d1hcs0EDp1BlBCY7
KxKTnYqwRkQth3NT0xqpyhG2q2fFCfK9HejqWaP3njeVIZ3HGrdCLufuEzz8jj6x
oe5m43qouSSe4tab0PaBQ1UKNnW4/Py3lpBA+VxPVYpiAK1UofM9NBZ4Jz2U8oNC
ZOxZ1sGwW2Fa63HO1TUAwxiM/XbgfM9Gi5lJuvEtbFfH5p3QuYV0KrvcBpvNLHh5
u4sYHV/gZ7TXpIn6EZihY9MM/zB5CY2ADVwFyg6wD8IYtj5Ewzfq6hNRxghM/7CF
CvExXjk7NTl7Mp52sh26kvF0eGnSD4xx9xwisp8lu0ucqVWbVow=
=zOUH
-END PGP SIGNATURE End Message ---

Bug#854346: tails-installer: Should not be part of Stretch

[intrigeri]

Hi,

u:
> I'm opening this RC bug in order to prevent tails-installer from
> migrating to testing.

Let's close this bug once there's a new upstream release that fixes
https://labs.riseup.net/code/issues/12696, so Tails Installer migrates
to testing (and then Ulrike can upload it to stretch-backports, so
that the Tails installation doc for Debian users is put back into
working shape). Rationale: I'd rather not expose users to that
regression introduced in 4.4.16.

Then, by the end of the year, or early in 2018, I'm hopeful we will
have a long-term plan wrt. the future of Tails' on-disk format and
installation methods, and hence wrt. the future of this package: this
will allow us to determine how suitable this package is for Buster.

Cheers,
-- 
intrigeri

Bug#865684: josm-plugins: Obsolete, causes issues with user installed plugins

[Bas Couwenberg]

Source: josm-plugins
Version: 0.0.svn33112+ds-1
Severity: serious
Tags: upstream
Justification: makes the package unsuitable for release

josm-plugins will be removed from Debian because it doesn't play well
with user installed plugins. See:

 https://josm.openstreetmap.de/ticket/7483

RM bugs have been filed to remove the package from unstable &
experimental:

 https://bugs.debian.org/864976 (unstable)
 https://bugs.debian.org/864975 (experimental)

This RC bugs serves to get josm-plugins removed from testing to allow
josm (>= 0.0.svn12275+dfsg-1) to migrate to testing.

Bug#865522: scilab: Segmentation fault at lauch

[trb]

I have the same bug on Debian 9 with KDE Plasma.
I had the same problem on Arch, maybe this is related to the kernel ? (
https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1699892 )

Best regards,
Piotr

Bug#865675: yaml: breaks reverse-dependencies testsuites, and please move to github maintained repo.

[Scott Kitterman]

On Friday, June 23, 2017 06:42:46 PM Gianfranco Costamagna wrote:
> control: tags -1 patch
> control: severity -1 serious
> 
> > debdiff will follow once the bug is opened
> 
> and here we are!
> 
> I have uploaded in Ubuntu a few seconds ago

I'm not the maintainer, just an interest maintainer of a reverse dependency.

First, all the home page changes are inappropriate for an NMU.  I would 
recommend you file a separate, normal priority, bug about those issues.

Second, have you checked if this breaks anything else?

Reverse-Build-Depends
=
* appstream
* appstream-glib
* choreonoid
* dvbstreamer
* erlang-p1-yaml
* flvmeta
* haskell-yaml
* hhvm
* hkl
* liblouis
* limba
* lua-yaml
* nutcracker
* php-yaml
* pyyaml
* r-cran-yaml
* ruby2.3
* suricata
* tarantool
* uwsgi
* v-sim
* vboot-utils

I'm particularly concerned you  don't break pyyaml (since I maintain that 
one).  Before NMUing, I think you should make sure you aren't trading one 
broken package for another.

Scott K

signature.asc
Description: This is a digitally signed message part.

Bug#865563: libcatmandu-sru-perl FTBFS: test failures

[gregor herrmann]

On Fri, 23 Jun 2017 17:22:52 +0200, gregor herrmann wrote:

> > So what is not there anymore is PERL_USE_UNSAFE_INC=1.
> 
> Dom, I think you're our expert on dot-in-inc; do you think my hunch
> is correct that we need to add PERL_USE_UNSAFE_INC back?
> (And if yes, where would be the best place - in the $dot_in_inc_code,
> and if yes within the if(); or after $dot_in_inc_code is output in
> the second hunk of the above diff?

So this seems to work (as in: libcatmandu-sru-perl builds again, if I
change /usr/share/perl5/Module/Build/Base.pm in the chroot):

--- a/lib/Module/Build/Base.pm
+++ b/lib/Module/Build/Base.pm
@@ -1866,6 +1866,7 @@ BEGIN {
 $quoted_INC
 );
 $dot_in_inc_code
+\$ENV{"PERL_USE_UNSAFE_INC"} = 1;
 }

 close(*DATA) unless eof(*DATA); # ensure no open handles to this script


I didn't have any success when playing with the new $dot_in_inc_code
string, seems like the condition is never met. (And to be honest, I
don't understand the logic ...) [0]

So it looks like we really need PERL_USE_UNSAFE_INC, and we might
want to insert it unconditionally manually where we did prior to the
accidental removal in the last upload.


Cheers,
gregor

[0]
my $dot_in_inc_code = $INC[-1] eq '.' ? <<'END' : '';
if ($INC[-1] ne '.') {
push @INC, '.';
}
END

What also works is reverting the logic:

--- /usr/share/perl5/Module/Build/Base.pm~  2017-06-19 17:25:18.0 
+
+++ /usr/share/perl5/Module/Build/Base.pm   2017-06-23 17:42:01.820466942 
+
@@ -1824,7 +1824,7 @@
   my $shebang = $self->_startperl;
   my $magic_number = $self->magic_number;
 
-my $dot_in_inc_code = $INC[-1] eq '.' ? <<'END' : '';
+my $dot_in_inc_code = $INC[-1] ne '.' ? <<'END' : '';
 if ($INC[-1] ne '.') {
 push @INC, '.';
 }


Then PERL_USE_UNSAFE_INC is not needed. But testing $INC[-1] ne '.'
two times make as little sense to me as first testing eq '.' and then ne '.'
...

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Diana Krall: Love Me Like A Man


signature.asc
Description: Digital Signature

Processed: Where is the build log for django-tables2?

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 855829 normal
Bug #855829 [python-django-tables2] python-django-tables2 FTBFS with Django 1.11
Severity set to 'normal' from 'serious'
> retitle 855829 New upstream release needed in experimental for testing with 
> django 1.11
Bug #855829 [python-django-tables2] python-django-tables2 FTBFS with Django 1.11
Changed Bug title to 'New upstream release needed in experimental for testing 
with django 1.11' from 'python-django-tables2 FTBFS with Django 1.11'.
> tag 855829 - buster
Bug #855829 [python-django-tables2] New upstream release needed in experimental 
for testing with django 1.11
Removed tag(s) buster.
> tag 855829 - sid
Bug #855829 [python-django-tables2] New upstream release needed in experimental 
for testing with django 1.11
Removed tag(s) sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855829: Where is the build log for django-tables2?

[Neil Williams]

severity 855829 normal
retitle 855829 New upstream release needed in experimental for testing with 
django 1.11
tag 855829 - buster
tag 855829 - sid
thanks

Adrian - where is the FTBFS build log to justify increasing the
severity of 855829 to RC?

I reported a different bug, nothing at all to do with building the package.

Please file a FTBFS bug explicitly and don't co-opt a different bug
which relates to runtime issues, not build time.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpSaPBcb9fNs.pgp
Description: OpenPGP digital signature

Processed: knot: Improper TSIG validity period check can allow TSIG forgery

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.5.1-1
Bug #865678 [src:knot] knot: Improper TSIG validity period check can allow TSIG 
forgery
Marked as found in versions knot/2.5.1-1.

-- 
865678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865678: knot: Improper TSIG validity period check can allow TSIG forgery

[Salvatore Bonaccorso]

Source: knot
Version: 2.4.3-1
Severity: grave
Tags: security upstream patch
Control: found -1 2.5.1-1

Hi

See
https://lists.nic.cz/pipermail/knot-dns-users/2017-June/001144.html
and
http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
and filling a bug in BTS to have a reference, afaik there is no CVE
yet assigned.

[16:19] < KGB-1> Yves-Alexis Perez 52846  /data/CVE/list add temporary entry 
for knot
[16:21] < Corsac> ondrej: I guess you know about it?

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 865522 865659
Bug #865522 [scilab] scilab: Segmentation fault at lauch
Bug #865659 [scilab] scilab: Segmentation fault at launch. It was working 
before an upgrade performed on 21 June.
Severity set to 'grave' from 'important'
Marked as found in versions scilab/5.5.2-4.
Bug #865522 [scilab] scilab: Segmentation fault at lauch
Marked as found in versions scilab/5.5.1-7.
Merged 865522 865659
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865522
865659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: yaml: breaks reverse-dependencies testsuites, and please move to github maintained repo.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #865675 [src:libyaml] yaml: breaks reverse-dependencies testsuites, and 
please move to github maintained repo.
Added tag(s) patch.
> severity -1 serious
Bug #865675 [src:libyaml] yaml: breaks reverse-dependencies testsuites, and 
please move to github maintained repo.
Severity set to 'serious' from 'normal'

-- 
865675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865671: scotch hides build failures

[Helmut Grohne]

Source: scotch
Version: 5.1.12b.dfsg-2
Severity: serious
Justification: policy 4.6
Tags: jessie stretch buster sid
User: helm...@debian.org
Usertags: rebootstrap

When some part of scotch's build fails (e.g. mpicc), the build continues
and may produce a broken package. This violates Debian Policy section
4.6. The cause is the use of an embedded makefile script without the
recommended "set -e".

Helmut

Bug#865650: marked as done (firefox-esr FTBFS: tries to use system nspr but has no build dependency)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 15:53:17 +
with message-id 
and subject line Bug#865650: fixed in firefox-esr 52.2.0esr-2
has caused the Debian Bug report #865650,
regarding firefox-esr FTBFS: tries to use system nspr but has no build 
dependency
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.)


-- 
865650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firefox-esr
Version: 52.2.0esr-1
Severity: serious

https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid

...
checking for valloc in malloc.h... yes
checking for valloc in unistd.h... no
checking NSPR selection... system
checking for nspr-config... no
checking for NSPR - version >= 4.13.1... no
configure: error: you do not have NSPR installed or your version is older than 
4.13.1.
...
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 52.2.0esr-2

We believe that the bug you reported is fixed in the latest version of
firefox-esr, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr 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: Sat, 24 Jun 2017 00:23:03 +0900
Source: firefox-esr
Binary: firefox-esr iceweasel firefox-esr-dev iceweasel-dev 
firefox-esr-l10n-all iceweasel-l10n-all firefox-esr-l10n-ach iceweasel-l10n-ach 
firefox-esr-l10n-af iceweasel-l10n-af firefox-esr-l10n-an iceweasel-l10n-an 
firefox-esr-l10n-ar iceweasel-l10n-ar firefox-esr-l10n-as iceweasel-l10n-as 
firefox-esr-l10n-ast iceweasel-l10n-ast firefox-esr-l10n-az iceweasel-l10n-az 
firefox-esr-l10n-bg iceweasel-l10n-bg firefox-esr-l10n-bn-bd 
iceweasel-l10n-bn-bd firefox-esr-l10n-bn-in iceweasel-l10n-bn-in 
firefox-esr-l10n-br iceweasel-l10n-br firefox-esr-l10n-bs iceweasel-l10n-bs 
firefox-esr-l10n-ca iceweasel-l10n-ca firefox-esr-l10n-cak iceweasel-l10n-cak 
firefox-esr-l10n-cs iceweasel-l10n-cs firefox-esr-l10n-cy iceweasel-l10n-cy 
firefox-esr-l10n-da iceweasel-l10n-da firefox-esr-l10n-de iceweasel-l10n-de 
firefox-esr-l10n-dsb iceweasel-l10n-dsb firefox-esr-l10n-el iceweasel-l10n-el 
firefox-esr-l10n-en-gb iceweasel-l10n-en-gb firefox-esr-l10n-en-za 
iceweasel-l10n-en-za firefox-esr-l10n-eo
 iceweasel-l10n-eo firefox-esr-l10n-es-ar iceweasel-l10n-es-ar 
firefox-esr-l10n-es-cl iceweasel-l10n-es-cl firefox-esr-l10n-es-es 
iceweasel-l10n-es-es firefox-esr-l10n-es-mx iceweasel-l10n-es-mx 
firefox-esr-l10n-et iceweasel-l10n-et firefox-esr-l10n-eu iceweasel-l10n-eu 
firefox-esr-l10n-fa iceweasel-l10n-fa firefox-esr-l10n-ff iceweasel-l10n-ff 
firefox-esr-l10n-fi iceweasel-l10n-fi firefox-esr-l10n-fr iceweasel-l10n-fr 
firefox-esr-l10n-fy-nl iceweasel-l10n-fy-nl firefox-esr-l10n-ga-ie 
iceweasel-l10n-ga-ie firefox-esr-l10n-gd iceweasel-l10n-gd firefox-esr-l10n-gl 
iceweasel-l10n-gl firefox-esr-l10n-gn iceweasel-l10n-gn firefox-esr-l10n-gu-in 
iceweasel-l10n-gu-in firefox-esr-l10n-he iceweasel-l10n-he 
firefox-esr-l10n-hi-in iceweasel-l10n-hi-in firefox-esr-l10n-hr 
iceweasel-l10n-hr firefox-esr-l10n-hsb iceweasel-l10n-hsb firefox-esr-l10n-hu 
iceweasel-l10n-hu firefox-esr-l10n-hy-am iceweasel-l10n-hy-am 
firefox-esr-l10n-id iceweasel-l10n-id firefox-esr-l10n-is
 iceweasel-l10n-is firefox-esr-l10n-it iceweasel-l10n-it firefox-esr-l10n-ja 
iceweasel-l10n-ja firefox-esr-l10n-ka iceweasel-l10n-ka firefox-esr-l10n-kab 
iceweasel-l10n-kab firefox-esr-l10n-kk iceweasel-l10n-kk firefox-esr-l10n-km 
iceweasel-l10n-km firefox-esr-l10n-kn iceweasel-l10n-kn firefox-esr-l10n-ko 
iceweasel-l10n-ko firefox-esr-l10n-lij iceweasel-l10n-lij firefox-esr-l10n-lt 
iceweasel-l10n-lt firefox-esr-l10n-lv iceweasel-l10n-lv firefox-esr-l10n-mai 
iceweasel-l10n-mai firefox-esr-l10n-mk iceweasel-l10n-mk firefox-esr-l10n-ml 
iceweasel-l10n-ml firefox-esr-l10n-mr iceweasel-l10n-mr firefox-esr-l10n-ms 
iceweasel-l10n-ms firefox-esr-l10n-nb-no iceweasel-l10n-nb-no 
firefox-esr-l10n-nl iceweasel-l10n-nl firefox-esr-l10n-nn-no 
iceweasel-l10n-nn-no firefox-esr-l10n-or iceweasel-l10n-or 
firefox-esr-l10n-pa-in ic

Bug#865667: ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.

[Adrian Bunk]

Source: ruby-prof
Version: 0.16.2+dfsg-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes ruby-prof FTBFS:

https://tests.reproducible-builds.org/debian/history/ruby-prof.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-prof.html

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0:/build/1st/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-prof/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 -I"test"  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/aggregate_test.rb" "test/basic_test.rb" "test/block_test.rb" 
"test/call_info_test.rb" "test/call_info_visitor_test.rb" 
"test/duplicate_names_test.rb" "test/dynamic_method_test.rb" 
"test/enumerable_test.rb" "test/exceptions_test.rb" 
"test/exclude_threads_test.rb" "test/fiber_test.rb" "test/issue137_test.rb" 
"test/line_number_test.rb" "test/measure_allocations_test.rb" 
"test/measure_cpu_time_test.rb" "test/measure_gc_runs_test.rb" 
"test/measure_gc_time_test.rb" "test/measure_memory_test.rb" 
"test/measure_process_time_test.rb" "test/measure_wall_time_test.rb" 
"test/method_elimination_test.rb" "test/module_test.rb" 
"test/no_method_class_test.rb" "test/pause_resume_test.rb" 
"test/printing_recursive_graph_test.rb" "test/rack_test.rb" 
"test/singleton_test.rb" "test/stack_test.rb" "test/start_stop_test.rb" 
"test/thread_test.rb" "test/unique_call_path_test.rb" "test/yarv_test.rb" -v
Run options: -v --seed 26693

# Running:

DynamicMethodTest#test_dynamic_method = 1.01 s = .
MeasureCpuTimeTest#test_cpu_time_enabled_defined = 0.00 s = .
MeasureCpuTimeTest#test_module_instance_methods = 0.30 s = F
MeasureCpuTimeTest#test_class_methods = 0.10 s = F
MeasureCpuTimeTest#test_sleeping_does_not_accumulate_significant_cpu_time = 
0.10 s = .
MeasureCpuTimeTest#test_waiting_for_threads_does_accumulate_wall_time = 0.12 s 
= F
MeasureCpuTimeTest#test_mode = 0.00 s = .
MeasureCpuTimeTest#test_instance_methods = 0.20 s = F
MeasureCpuTimeTest#test_module_methods = 0.30 s = F
MeasureCpuTimeTest#test_singleton = 0.00 s = .
MeasureCpuTimeTest#test_sleeping_does_accumulate_wall_time = 0.10 s = .
MeasureCpuTimeTest#test_waiting_for_threads_does_not_accumulate_cpu_time = 0.12 
s = .
MeasureWallTimeTest#test_wall_time_enabled_defined = 0.00 s = .
MeasureWallTimeTest#test_instance_methods = 0.20 s = .
MeasureWallTimeTest#test_module_methods = 0.30 s = .
MeasureWallTimeTest#test_singleton = 0.00 s = .
MeasureWallTimeTest#test_mode = 0.00 s = .
MeasureWallTimeTest#test_class_methods = 0.10 s = .
MeasureWallTimeTest#test_module_instance_methods = 0.30 s = .
PrintingRecursiveGraphTest#test_printing_rescursive_graph = 2.05 s = .
CallInfoTest#test_merge = 0.21 s = .
MeasureGCRunsTest#test_gc_runs_mode = 0.00 s = .
MeasureGCRunsTest#test_gc_runs_enabled_defined = 0.00 s = .
MeasureGCRunsTest#test_gc_runs = 0.02 s = .
MeasureProcessTimeTest#test_primes = 1.10 s = .
MeasureProcessTimeTest#test_process_time_enabled_defined = 0.00 s = .
MeasureProcessTimeTest#test_mode = 0.00 s = .
StartStopTest#test_extra_stop_should_raise = 0.00 s = .
StartStopTest#test_different_methods = 2.00 s = .
FiberTest#test_merged_fibers = 0.31 s = .
FiberTest#test_fibers = 0.31 s = .
BlockMethodTest#test_block = 0.20 s = .
MeasureMemoryTest#test_memory_mode = 0.00 s = .
MeasureMemoryTest#test_memory_enabled_defined = 0.00 s = .
BugsTest#test_array_push_optimized = 0.00 s = .
BugsTest#test_array_push_unoptimized = 0.00 s = .
RecursiveChildrenTest#test_simple = 1.36 s = .
MeasureAllocationsTest#test_allocations_enabled_defined = 0.00 s = .
MeasureAllocationsTest#test_allocations = 0.00 s = .
MeasureAllocationsTest#test_allocations_mode = 0.00 s = .
CallInfoVisitorTest#test_visit = 0.10 s = .
RackTest#test_create_print_path = 0.02 s = .
RackTest#test_allows_lazy_filename_setting = 0.01 s = .
RackTest#test_only_paths = 0.01 s = .
RackTest#test_create_profile_reports = 0.01 s = .
RackTest#test_skip_paths = 0.00 s = .
ExceptionsTest#test_profile = 0.00 s = .
MethodEliminationTest#test_methods_can_be_eliminated = 0.52 s = .
MethodEliminationTest#test_setting_parent = 0.00 s = .
BasicTest#test_leave_method_2 = 0.31 s = .
BasicTest#test_no_block = 0.00 s = .
BasicTest#test_double_profile = 0.00 s = .
BasicTest#test_leave_method = 0.25 s = .
BasicTest#test_running = 0.00 s = .
BasicTest#test_traceback = 0.00 s = .
AggregateTest#test_aggregates_parents = 3.01 s = .
AggregateTest#test_all_call_infos_are_not_recursive = 3.01 s = .
Aggreg

Bug#865563: libcatmandu-sru-perl FTBFS: test failures

[gregor herrmann]

On Thu, 22 Jun 2017 21:33:27 +0200, gregor herrmann wrote:

> Basically the diff between 0.422000-1 (with our changes) and 0.422400-1
> (with a different fix and without our patch) is:
> 
> 
> @@ -1824,6 +1824,11 @@ sub print_build_script {
>my $shebang = $self->_startperl;
>my $magic_number = $self->magic_number;
> 
> +my $dot_in_inc_code = $INC[-1] eq '.' ? <<'END' : '';
> +if ($INC[-1] ne '.') {
> +push @INC, '.';
> +}
> +END
>print $fh <  $shebang
> 
> @@ -1860,8 +1865,7 @@ BEGIN {
>  (
>  $quoted_INC
>  );
> -  push \@INC, "." unless grep { \$_ eq "." } \@INC; # Force my process to 
> include . in \@INC.
> -  \$ENV{"PERL_USE_UNSAFE_INC"} = 1; # Force all child processes to include . 
> in \@INC.
> +$dot_in_inc_code
>  }
> 
>  close(*DATA) unless eof(*DATA); # ensure no open handles to this script
> 
> 
> So what is not there anymore is PERL_USE_UNSAFE_INC=1.

Dom, I think you're our expert on dot-in-inc; do you think my hunch
is correct that we need to add PERL_USE_UNSAFE_INC back?
(And if yes, where would be the best place - in the $dot_in_inc_code,
and if yes within the if(); or after $dot_in_inc_code is output in
the second hunk of the above diff?
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Joan Baez: Gracias a la vida


signature.asc
Description: Digital Signature

Bug#865664: golang-github-microcosm-cc-bluemonday FTBFS: dh_auto_test fails

[Adrian Bunk]

Source: golang-github-microcosm-cc-bluemonday
Version: 0.0~git20161012.0.f77f16f-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-microcosm-cc-bluemonday 
FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-microcosm-cc-bluemonday.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-microcosm-cc-bluemonday.html

...
   dh_auto_test -O--buildsystem=golang
go test -v -p 1 github.com/microcosm-cc/bluemonday 
github.com/microcosm-cc/bluemonday/cmd/sanitise_html_email 
github.com/microcosm-cc/bluemonday/cmd/sanitise_ugc
=== RUN   TestRegexpVars
--- PASS: TestRegexpVars (0.00s)
=== RUN   TestAllowDataURIImages
--- PASS: TestAllowDataURIImages (0.00s)
=== RUN   TestStrictPolicy
--- PASS: TestStrictPolicy (0.00s)
=== RUN   TestUGCPolicy
--- PASS: TestUGCPolicy (0.00s)
=== RUN   TestAllowElementsContent
--- PASS: TestAllowElementsContent (0.00s)
=== RUN   TestEmpty
--- PASS: TestEmpty (0.00s)
=== RUN   TestSignatureBehaviour
--- PASS: TestSignatureBehaviour (0.00s)
=== RUN   TestAllowDocType
--- PASS: TestAllowDocType (0.00s)
=== RUN   TestLinks
--- PASS: TestLinks (0.00s)
=== RUN   TestLinkTargets
--- PASS: TestLinkTargets (0.00s)
=== RUN   TestStyling
--- PASS: TestStyling (0.01s)
=== RUN   TestEmptyAttributes
--- PASS: TestEmptyAttributes (0.00s)
=== RUN   TestDataUri
--- PASS: TestDataUri (0.00s)
=== RUN   TestAntiSamy
--- PASS: TestAntiSamy (0.00s)
=== RUN   TestXSS
--- FAIL: TestXSS (0.00s)
sanitize_test.go:1138: test 61 failed;
input   : 
output  : 
expected: 
sanitize_test.go:1138: test 74 failed;
input   : 
output  : 
expected: 
=== RUN   TestIssue3
--- PASS: TestIssue3 (0.00s)
=== RUN   TestIssue9
--- PASS: TestIssue9 (0.00s)
=== RUN   TestIssue18
--- PASS: TestIssue18 (0.00s)
=== RUN   TestIssue23
--- PASS: TestIssue23 (0.00s)
=== RUN   TestAllowNoAttrs
--- PASS: TestAllowNoAttrs (0.00s)
=== RUN   TestSkipElementsContent
--- PASS: TestSkipElementsContent (0.00s)
=== RUN   TestTagSkipClosingTagNested
--- PASS: TestTagSkipClosingTagNested (0.00s)
=== RUN   TestAddSpaces
--- PASS: TestAddSpaces (0.00s)
=== RUN   TestTargetBlankNoOpener
--- PASS: TestTargetBlankNoOpener (0.00s)
=== RUN   ExampleNewPolicy
--- PASS: ExampleNewPolicy (0.00s)
=== RUN   ExampleStrictPolicy
--- PASS: ExampleStrictPolicy (0.00s)
=== RUN   ExampleUGCPolicy
--- PASS: ExampleUGCPolicy (0.00s)
=== RUN   ExamplePolicy_Sanitize
--- PASS: ExamplePolicy_Sanitize (0.00s)
=== RUN   ExamplePolicy_SanitizeBytes
--- PASS: ExamplePolicy_SanitizeBytes (0.00s)
=== RUN   ExamplePolicy_SanitizeReader
--- PASS: ExamplePolicy_SanitizeReader (0.00s)
FAIL
exit status 1
FAILgithub.com/microcosm-cc/bluemonday  0.060s
?   github.com/microcosm-cc/bluemonday/cmd/sanitise_html_email  [no 
test files]
?   github.com/microcosm-cc/bluemonday/cmd/sanitise_ugc [no test files]
dh_auto_test: go test -v -p 1 github.com/microcosm-cc/bluemonday 
github.com/microcosm-cc/bluemonday/cmd/sanitise_html_email 
github.com/microcosm-cc/bluemonday/cmd/sanitise_ugc returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1

Bug#865663: flask-restful FTBFS: dh_auto_test fails

[Adrian Bunk]

Source: flask-restful
Version: 0.3.5-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes flask-restful FTBFS:

https://tests.reproducible-builds.org/debian/history/flask-restful.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flask-restful.html

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/flask-restful-0.3.5/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
tests
...[2017-06-23 02:43:46,629] ERROR in app: Exception on / [GET]
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/flask/app.py", line 1612, in 
full_dispatch_request
rv = self.dispatch_request()
  File "/usr/lib/python2.7/dist-packages/flask/app.py", line 1598, in 
dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
  File "flask_restful/__init__.py", line 481, in wrapper
return self.make_response(data, code, headers=headers)
  File "flask_restful/__init__.py", line 518, in make_response
raise InternalServerError()
InternalServerError: 500 Internal Server Error: The server encountered an 
internal error and was unable to complete your request.  Either the server is 
overloaded or there is an error in the application.
[2017-06-23 02:43:46,630] ERROR in app: Exception on / [GET]
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/flask/app.py", line 1982, in wsgi_app
response = self.full_dispatch_request()
  File "/usr/lib/python2.7/dist-packages/flask/app.py", line 1614, in 
full_dispatch_request
rv = self.handle_user_exception(e)
  File "flask_restful/__init__.py", line 271, in error_router
return original_handler(e)
  File "/usr/lib/python2.7/dist-packages/flask/app.py", line 1504, in 
handle_user_exception
assert exc_value is e
AssertionError
[2017-06-23 02:43:46,631] ERROR in app: Exception on / [GET]
Traceback (most recent call last):
  File "flask_restful/__init__.py", line 268, in error_router
return self.handle_error(e)
  File "flask_restful/__init__.py", line 357, in handle_error
resp = self.make_response(data, code, headers)
  File "flask_restful/__init__.py", line 518, in make_response
raise InternalServerError()
InternalServerError: 500 Internal Server Error: The server encountered an 
internal error and was unable to complete your request.  Either the server is 
overloaded or there is an error in the application.
[2017-06-23 02:43:46,674] ERROR in app: Exception on 
/foo [GET]
E..[2017-06-23 02:43:46,709] ERROR in app: Exception on /foo [GET]
..[2017-06-23 02:43:46,715] ERROR in app: Exception on /foo [GET]

==
ERROR: Test that HTTPException's headers are extended properly
--
Traceback (most recent call last):
  File 
"/build/1st/flask-restful-0.3.5/.pybuild/pythonX.Y_2.7/build/tests/test_api.py",
 line 811, in test_exception_header_forwarded
flask_abort.mapping.update({304: NotModified})
AttributeError: 'function' object has no attribute 'mapping'

--
Ran 384 tests in 0.379s

FAILED (errors=1)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/flask-restful-0.3.5/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25

Processed: Add the buster sid tags I forgot

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 865662 buster sid
Bug #865662 [src:libcatmandu-perl] libcatmandu-perl FTBFS: 
Catmandu-Fix-perlcode.t failed
Added tag(s) sid and buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865662: libcatmandu-perl FTBFS: Catmandu-Fix-perlcode.t failed

[Adrian Bunk]

Source: libcatmandu-perl
Version: 1.0304-2
Severity: serious

Some recent change in unstable makes libcatmandu-perl FTBFS:

https://tests.reproducible-builds.org/debian/history/libcatmandu-perl.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcatmandu-perl.html

...
t/Catmandu-Fix-perlcode.t  
Dubious, test returned 255 (wstat 65280, 0xff00)
No subtests run
...
Test Summary Report
---
t/Catmandu-Fix-perlcode.t  (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=150, Tests=1853, 128 wallclock secs ( 0.68 usr  0.62 sys + 62.70 cusr  
5.87 csys = 69.87 CPU)
Result: FAIL
Failed 1/150 test programs. 0/1853 subtests failed.
/usr/share/cdbs/1/class/perl-build.mk:84: recipe for target 
'debian/stamp-perl-check' failed
make: *** [debian/stamp-perl-check] Error 255

Bug#865606: marked as done (orthanc FTBFS with libdcmtk-dev 3.6.1~20170228-2)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 15:09:50 +
with message-id 
and subject line Bug#865606: fixed in orthanc 1.2.0+dfsg-2
has caused the Debian Bug report #865606,
regarding orthanc FTBFS with libdcmtk-dev 3.6.1~20170228-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.)


-- 
865606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc
Version: 1.2.0+dfsg-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orthanc.html

...
Path to the Debian Google Test includes: /usr/include/gtest
-- Boost version: 1.62.0
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Boost version: 1.62.0
-- Found the following Boost libraries:
--   filesystem
--   thread
--   system
--   date_time
--   regex
--   locale
--   chrono
--   atomic
-- Trying to find DCMTK expecting DCMTKConfig.cmake
-- Trying to find DCMTK expecting DCMTKConfig.cmake - ok
CMake Error at Resources/CMake/DcmtkConfiguration.cmake:274 (message):
  Please install libdcmtk*-dev
Call Stack (most recent call first):
  CMakeLists.txt:310 (include)


-- Configuring incomplete, errors occurred!
...
--- End Message ---
--- Begin Message ---
Source: orthanc
Source-Version: 1.2.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
orthanc, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Jodogne  (supplier of updated orthanc 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: Fri, 23 Jun 2017 10:25:41 +0200
Source: orthanc
Binary: orthanc orthanc-doc orthanc-dev
Architecture: source amd64 all
Version: 1.2.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Description:
 orthanc- Lightweight, RESTful DICOM server for medical imaging
 orthanc-dev - Orthanc development files
 orthanc-doc - Documentation of Orthanc
Closes: 865606
Changes:
 orthanc (1.2.0+dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS with libdcmtk-dev 3.6.1~20170228-2. Closes: #865606
Checksums-Sha1:
 ce4ce22f39e1d9cd80c574d7a7c384c8f43329b4 2415 orthanc_1.2.0+dfsg-2.dsc
 1e97f4fdbacd621322a9dc942afb116ae657a419 1794404 
orthanc_1.2.0+dfsg-2.debian.tar.xz
 f5917c6a753e166a34f590d1b4be85de1c803d06 19934592 
orthanc-dbgsym_1.2.0+dfsg-2_amd64.deb
 d03047b18e3489010c67f7e791af5a88b0182882 51982 
orthanc-dev_1.2.0+dfsg-2_amd64.deb
 2331f36d7bbba748b2a175350df42c87dc7ca45f 189138 
orthanc-doc_1.2.0+dfsg-2_all.deb
 8a8c7fa03db86bb8e4b730be3d39f66387e1a250 14890 
orthanc_1.2.0+dfsg-2_amd64.buildinfo
 8b3af72bebdf7954f8d922b7112093463e1c83ed 900536 orthanc_1.2.0+dfsg-2_amd64.deb
Checksums-Sha256:
 251ccb10b63d169dc61cf1ffc236a5f678cba1de853fcce0287887f6aa36627f 2415 
orthanc_1.2.0+dfsg-2.dsc
 1e052c5d62010dd03468f820a9ca46f42d1ab908b2d6f538ad6f0beae8382a78 1794404 
orthanc_1.2.0+dfsg-2.debian.tar.xz
 ad3307735aea589051e50f961995e23cb8b7679574bf014b63972c7e33ca39e3 19934592 
orthanc-dbgsym_1.2.0+dfsg-2_amd64.deb
 5cbda2e48d774a1e244ce7aa0bc4caf747923660d077790df7dfdd89158aa591 51982 
orthanc-dev_1.2.0+dfsg-2_amd64.deb
 08bc49b2a10b3acd24975bc8d97d8e41c24e31544c3bc481f349a76012eb12e1 189138 
orthanc-doc_1.2.0+dfsg-2_all.deb
 46657ddaf73d72c01b197c5541b775c5fa65f84a28708694312c571727c22061 14890 
orthanc_1.2.0+dfsg-2_amd64.buildinfo
 1fbc908710c2b451c55d3d38ac5bb1b3e436e61c2d9ed4a51893d7be990ed058 900536 
orthanc_1.2.0+dfsg-2_amd64.deb
Files:
 dd8a85c4814c4d7da7215ee410d526c2 2415 science optional orthanc_1.2.0+dfsg-2.dsc
 800f0d9128c937dd04a14db07cec99ad 1794404 science optional 
orthanc_1.2.0+dfsg-2.debian.tar.xz
 49794333adc5167400c7090bb44ddd87 19934592 debug extra 
orthanc-dbgsym_1.2.0+dfsg-2_amd64.deb
 fd2299f7708ff38ebafb86cda3f3ef6a 51982 libdevel 

Bug#865650: firefox-esr FTBFS: tries to use system nspr but has no build dependency

[Mike Hommey]

On Fri, Jun 23, 2017 at 11:56:45PM +0900, Mike Hommey wrote:
> On Fri, Jun 23, 2017 at 04:53:19PM +0300, Adrian Bunk wrote:
> > Source: firefox-esr
> > Version: 52.2.0esr-1
> > Severity: serious
> > 
> > https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid
> > 
> > ...
> > checking for valloc in malloc.h... yes
> > checking for valloc in unistd.h... no
> > checking NSPR selection... system
> > checking for nspr-config... no
> > checking for NSPR - version >= 4.13.1... no
> > configure: error: you do not have NSPR installed or your version is older 
> > than 4.13.1.
> > ...
> 
> Whatever created the binnmu borked debian/control, but the build itself
> preprocessed it with the right flags (-DUSE_SYSTEM_NSPR="1"), but that's
> too late for the dependencies installer.
> 
> How does one get a hand on the .diff.xz?

Forget it, I figured out what's wrong, and indeed, the dependency is
missing, but that was on purpose. The bug is actually that it still
tries to build against system nspr, considering the contents, because
the distribution mentioned in debian/changelog for the binnmu is "sid",
while the scripts only know what to do for "unstable".

I also need to resync with firefox, to use the system nspr and nss.

Mike

Bug#865650: firefox-esr FTBFS: tries to use system nspr but has no build dependency

[Adrian Bunk]

On Fri, Jun 23, 2017 at 11:56:45PM +0900, Mike Hommey wrote:
> On Fri, Jun 23, 2017 at 04:53:19PM +0300, Adrian Bunk wrote:
> > Source: firefox-esr
> > Version: 52.2.0esr-1
> > Severity: serious
> > 
> > https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid
> > 
> > ...
> > checking for valloc in malloc.h... yes
> > checking for valloc in unistd.h... no
> > checking NSPR selection... system
> > checking for nspr-config... no
> > checking for NSPR - version >= 4.13.1... no
> > configure: error: you do not have NSPR installed or your version is older 
> > than 4.13.1.
> > ...
> 
> Whatever created the binnmu borked debian/control, but the build itself
> preprocessed it with the right flags (-DUSE_SYSTEM_NSPR="1"), but that's
> too late for the dependencies installer.
> 
> How does one get a hand on the .diff.xz?

A binNMU always uses the .diff.xz from the original upload.

> Mike

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#865661: django-compat FTBFS with Django 1.11

[Adrian Bunk]

Source: django-compat
Version: 1.0.13-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-compat.html

...
Normal module existence can be tested ... ok
test_json_response_custom_encoder (compat.tests.test_compat.JsonResponseTests) 
... ok
test_json_response_list (compat.tests.test_compat.JsonResponseTests) ... ok
test_json_response_non_ascii (compat.tests.test_compat.JsonResponseTests) ... ok
test_json_response_passing_arguments_to_json_dumps 
(compat.tests.test_compat.JsonResponseTests) ... ok
test_json_response_raises_type_error_with_default_setting 
(compat.tests.test_compat.JsonResponseTests) ... ok
test_json_response_text (compat.tests.test_compat.JsonResponseTests) ... ok
test_json_response_uuid (compat.tests.test_compat.JsonResponseTests) ... ok

==
FAIL: test_get_template_loaders (compat.tests.test_compat.CompatTests)
--
Traceback (most recent call last):
  File "/build/1st/django-compat-1.0.13/compat/tests/test_compat.py", line 247, 
in test_get_template_loaders
self.assertEqual(len(template_loaders), 2)
AssertionError: 1 != 2

--
Ran 34 tests in 0.030s

FAILED (failures=1)
 OK
Destroying test database for alias 'default' (':memory:')...
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#865650: firefox-esr FTBFS: tries to use system nspr but has no build dependency

[Mike Hommey]

On Fri, Jun 23, 2017 at 04:53:19PM +0300, Adrian Bunk wrote:
> Source: firefox-esr
> Version: 52.2.0esr-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid
> 
> ...
> checking for valloc in malloc.h... yes
> checking for valloc in unistd.h... no
> checking NSPR selection... system
> checking for nspr-config... no
> checking for NSPR - version >= 4.13.1... no
> configure: error: you do not have NSPR installed or your version is older 
> than 4.13.1.
> ...

Whatever created the binnmu borked debian/control, but the build itself
preprocessed it with the right flags (-DUSE_SYSTEM_NSPR="1"), but that's
too late for the dependencies installer.

How does one get a hand on the .diff.xz?

Mike

Bug#865653: xrdp: X server timeout

[Stanislav Sinyagin]

Now I upgraded xrdp and xorgxrdp to experimental, and the problem
still persists:

# dpkg -l | grep xrdp
ii  xorgxrdp0.9.2~20170325-1~exp1
amd64Remote Desktop Protocol (RDP) modules for X.org
ii  xrdp0.9.2~20170325-1~exp1
amd64Remote Desktop Protocol (RDP) server

Bug#865653: xrdp: X server timeout

[Stanislav Sinyagin]

Package: xrdp
Version: 0.9.1-9
Severity: grave
Justification: renders package unusable

Dear Maintainer,

xrdp 0.9.1-9 was running fine while the machine was under Debian Testing. 
After upgrading to Stretch, I cannot start the RDP session any more. 

The problem is reproduced on a fresh Debian 9.0 machine, by installing xrdp and 
creating a user. I'm using the Windows 8.1 RDP client.

After logging in, the screen is blank blue background for 10 seconds, and then a
window with "Connection problem, giving up" appears. The following is the 
content of 
/var/log/xrdp-sesman.log:

[20170623-13:48:27] [DEBUG] libscp initialized
[20170623-13:48:27] [INFO ] starting xrdp-sesman with pid 13780
[20170623-13:48:27] [INFO ] listening to port 3350 on 127.0.0.1
[20170623-13:50:49] [INFO ] A connection received from ::1 port 44638
[20170623-13:50:49] [INFO ] ++ created session (access granted): username 
ssinyagin, ip 0.0.0.0:62500 - socket: 12
[20170623-13:50:49] [INFO ] starting Xorg session...
[20170623-13:50:49] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20170623-13:50:49] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20170623-13:50:49] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20170623-13:50:49] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20170623-13:50:49] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20170623-13:50:49] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf 
-noreset -nolisten tcp  
[20170623-13:50:59] [ERROR] X server for display 10 startup timeout
[20170623-13:50:59] [INFO ] starting xrdp-sessvc - xpid=16987 - wmpid=16986
[20170623-13:50:59] [ERROR] X server for display 10 startup timeout
[20170623-13:50:59] [ERROR] another Xserver might already be active on display 
10 - see log
[20170623-13:50:59] [DEBUG] aborting connection...
[20170623-13:50:59] [INFO ] ++ terminated session:  username ssinyagin, display 
:10.0, session_pid 16985, ip 0.0.0.0:62500 - socket: 12

 

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xrdp depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-11
ii  libfuse2 2.9.7-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libopus0 1.2~alpha2-1
ii  libpam0g 1.1.8-3.6
ii  libssl1.11.1.0f-3
ii  libx11-6 2:1.6.4-3
ii  libxfixes3   1:5.0.3-1
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 9.20161125
ii  ssl-cert 1.0.39

Versions of packages xrdp recommends:
ii  fuse  2.9.7-1
ii  xorgxrdp  0.9.1-9

Versions of packages xrdp suggests:
pn  guacamole  

Versions of packages xorgxrdp depends on:
ii  libc6  2.24-11
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-23]  2:1.19.2-1

Versions of packages xorgxrdp recommends:
ii  xorg  1:7.7+19

Versions of packages xrdp is related to:
pn  vnc-server   
ii  xserver-xorg-legacy  2:1.19.2-1

-- no debconf information

Bug#864750: marked as done (texlive-base: dvipdfmx.def is broken)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 22:58:02 +0900
with message-id <20170623135802.sxkoq2nd5psc5...@bulldog.preining.info>
and subject line closing bug
has caused the Debian Bug report #864750,
regarding texlive-base: dvipdfmx.def is broken
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.)


-- 
864750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base
Version: 2017.20170613-1
Severity: serious
Justification: broken


dvipdfmx.def is missing a }, so dvipdmfx is broken for now in experimental.
This is already fixed upstream, we need new packages.
--- End Message ---
--- Begin Message ---
Version: 2017.20170619-1

Closing bug that is not closed in unstable but only experimental

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---

Bug#865650: firefox-esr FTBFS: tries to use system nspr but has no build dependency

[Adrian Bunk]

Source: firefox-esr
Version: 52.2.0esr-1
Severity: serious

https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid

...
checking for valloc in malloc.h... yes
checking for valloc in unistd.h... no
checking NSPR selection... system
checking for nspr-config... no
checking for NSPR - version >= 4.13.1... no
configure: error: you do not have NSPR installed or your version is older than 
4.13.1.
...

Bug#865648: Does not include security sources for all releases

[Steve McIntyre]

Package: openstack-debian-images
Version: 1.19
Severity: serious
Tags: patch

The code is currently *only* adding security sources into
apt/sources.list when building for wheezy or jessie. This is clearly
wrong. I've just had to rebuild our stretch images again (9.0.1 to
9.0.2) to get expected updates in.

Trivial fix is to *always* include security:

diff --git a/build-openstack-debian-image b/build-openstack-debian-image
index 3a8d7d6..e0e670a 100755
--- a/build-openstack-debian-image
+++ b/build-openstack-debian-image
@@ -484,13 +484,11 @@ echo "debian.example.com" >${MOUNT_DIR}/etc/hostname
 echo "deb ${SOURCE_LIST_MIRROR} ${RELEASE} main
 deb-src ${SOURCE_LIST_MIRROR} ${RELEASE} main" 
>${MOUNT_DIR}/etc/apt/sources.list
 
-if [ "${RELEASE}" = "wheezy" ] || [ "${RELEASE}" = "jessie" ] ; then
-   echo "deb ${SOURCE_LIST_MIRROR} ${RELEASE}-updates main
+echo "deb ${SOURCE_LIST_MIRROR} ${RELEASE}-updates main
 deb-src ${SOURCE_LIST_MIRROR} ${RELEASE}-updates main
 deb http://security.debian.org/ ${RELEASE}/updates main
 deb-src http://security.debian.org/ ${RELEASE}/updates main
 " >>${MOUNT_DIR}/etc/apt/sources.list
-fi
 
 if [ "${RELEASE}" = "wheezy" ] ; then
echo "deb ${SOURCE_LIST_MIRROR} wheezy-backports main


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openstack-debian-images depends on:
ii  debootstrap  1.0.89
ii  dosfstools   4.1-1
ii  extlinux 3:6.03+dfsg-14.1
ii  initramfs-tools  0.130
ii  kpartx   0.6.4-5
ii  mbr  1.1.11-5.1
ii  parted   3.2-17
ii  qemu-utils   1:2.8+dfsg-6

openstack-debian-images recommends no packages.

openstack-debian-images suggests no packages.

-- no debconf information

Bug#865589: marked as done (Ships a tmpfile in /usr and /etc, one overriding the other)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 13:20:35 +
with message-id 
and subject line Bug#865589: fixed in openvpn 2.4.3-2
has caused the Debian Bug report #865589,
regarding Ships a tmpfile in /usr and /etc, one overriding the other
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.)


-- 
865589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvpn
Version: 2.4.3-1
Severity: serious

Hi,

I just noticed that the latest openvpn update now ships a tmpfile in /etc:
/etc/tmpfiles.d/openvpn.conf

This is odd, since the package also ships:
/usr/lib/tmpfiles.d/openvpn.conf

tmpfiles in /etc/tmpfiles.d are reserved to the local administrator and
override a tmpfile with the same name from /usr/lib/tmpfiles.d

Marking as RC, as something is clearly broken here, and
/usr/lib/tmpfiles.d/openvpn.conf being overriddden means that
/run/openvpn is no longer created.

Michael

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  iproute2   4.9.0-1
ii  libc6  2.24-12
ii  liblz4-1   0.0~r131-2+b1
ii  liblzo2-2  2.08-1.2+b2
ii  libpam0g   1.1.8-3.6
ii  libpkcs11-helper1  1.21-1
ii  libssl1.0.21.0.2l-2
ii  libsystemd0233-9
ii  lsb-base   9.20161125

Versions of packages openvpn recommends:
pn  easy-rsa  

Versions of packages openvpn suggests:
ii  openssl 1.1.0f-3
pn  resolvconf  

-- Configuration Files:
/etc/default/openvpn changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: openvpn
Source-Version: 2.4.3-2

We believe that the bug you reported is fixed in the latest version of
openvpn, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alberto Gonzalez Iniesta  (supplier of updated openvpn 
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: Fri, 23 Jun 2017 11:43:50 +0200
Source: openvpn
Binary: openvpn
Architecture: source amd64
Version: 2.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Alberto Gonzalez Iniesta 
Changed-By: Alberto Gonzalez Iniesta 
Description:
 openvpn- virtual private network daemon
Closes: 865589
Changes:
 openvpn (2.4.3-2) unstable; urgency=medium
 .
   * The "Bye bye OpenVPN" revenge release
   * Put upstream tmpfiles conf in the right place and merge with Debian's.
 (Closes: #865589)
Checksums-Sha1:
 f9a0bdfbdf9d3e3e4f602dafe9b7c4f9db9f82fd 2092 openvpn_2.4.3-2.dsc
 938c6fd2668e25fee478300d7b9956b94c6b8b35 51128 openvpn_2.4.3-2.debian.tar.xz
 4fe3f40f1cc7859f9d082265c2d62da2780716b6 1384478 
openvpn-dbgsym_2.4.3-2_amd64.deb
 7792707dbd7ff43c69bb69f61fe8ac2176e878e1 6512 openvpn_2.4.3-2_amd64.buildinfo
 5c9557da7bd3dcb745a631a82a86d61004fd507d 479030 openvpn_2.4.3-2_amd64.deb
Checksums-Sha256:
 c934904c5f4e9f42b039f07145dbca9f24e257d77010c732b9ebaeff3a075fa4 2092 
openvpn_2.4.3-2.dsc
 d6c1b4843403cb284432cae64478b779a6b6006f7e729011c7e4553bfbbf5dd1 51128 
openvpn_2.4.3-2.debian.tar.xz
 854204c8b2ff5291c07ef2355f1a3589f17ce5c53aca89785dc8f0f5df192dd8 1384478 
openvpn-dbgsym_2.4.3-2_amd64.deb
 153139c98b5199b3a7c3bc09a46dcc3d15c19149867eaf1820b00cad3b42d15e 6512 
openvpn_2.4.3-2_amd64.buildinfo
 3415801cdc4fa9a383fdc9628efea40ade009eaa28db33744cb560a16568643c 479030 
openvpn_2.4.3-2_amd64.deb
Files:
 3c9e6b66fd7c98362d491578a6c6f721 2092 net optional openvpn_2.4.3-2.dsc
 bc49c8a86077d46f679154fa75bc1a88 51128 net optional 
openvpn_2.4.3-2.debian.tar.xz
 c5a1a9d9ab08166efa4b619f5341acbc 1384478 debug extra 
openvpn-dbgsym_2.4.3-2_amd64.deb
 ed56557accdc9ec52

Bug#865511: marked as done (haskell-tls: FTBFS, missing quickcheck dependency?)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 13:35:19 +
with message-id 
and subject line Bug#865511: fixed in haskell-tls 1.3.10-2
has caused the Debian Bug report #865511,
regarding haskell-tls: FTBFS, missing quickcheck dependency?
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.)


-- 
865511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-tls
Version: 1.3.10-1
Severity: normal

Hello,

haskell-tls FTBFS:

hlibrary.setup: Encountered missing dependencies:
QuickCheck -any, tasty -any, tasty-quickcheck -any

I guess a missing build-dependency?

Samuel

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), 
(1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
  sl  -  display animations aimed to correct users who accidentally enter
sl instead of ls.
--- End Message ---
--- Begin Message ---
Source: haskell-tls
Source-Version: 1.3.10-2

We believe that the bug you reported is fixed in the latest version of
haskell-tls, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
haskell-tls 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: Fri, 23 Jun 2017 15:02:21 +0200
Source: haskell-tls
Binary: libghc-tls-dev libghc-tls-prof libghc-tls-doc
Architecture: source
Version: 1.3.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Gianfranco Costamagna 
Description:
 libghc-tls-dev - native Haskell implementation of TLS/SSL 
protocol${haskell:ShortB
 libghc-tls-doc - native Haskell implementation of TLS/SSL 
protocol${haskell:ShortB
 libghc-tls-prof - native Haskell implementation of TLS/SSL 
protocol${haskell:ShortB
Closes: 865511
Changes:
 haskell-tls (1.3.10-2) unstable; urgency=medium
 .
   * Team upload.
   * Add quickcheck and tasty build-dependencies
 (thanks Samuel Thibault! Closes: #865511)
Checksums-Sha1:
 6dee93280428f2101b4e751c404dc5de95096805 3286 haskell-tls_1.3.10-2.dsc
 353f9f80677f4e6d6c6f284fb84ef8cec718a4e9 3600 
haskell-tls_1.3.10-2.debian.tar.xz
Checksums-Sha256:
 154af73ea62d715c8f89fa0a6ec6061b79eb2d37236a54d3a8aa4c28b1f3ba09 3286 
haskell-tls_1.3.10-2.dsc
 dcedaa9ae6612caacf058c58bd41d7b376caeb9d315e9d4406bdf1d11ebbd0f5 3600 
haskell-tls_1.3.10-2.debian.tar.xz
Files:
 bbc29f3d1e786677ddae3518a8b153c6 3286 haskell extra haskell-tls_1.3.10-2.dsc
 4da588db6c3cc8b56c712572688ebff3 3600 haskell extra 
haskell-tls_1.3.10-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZTRQKAAoJEPNPCXROn13ZI4sP/01zXe4KZO4zyOH02Ve9xXTm
g+keZbS1tJzfYlDX4QfrG4fFOx3JUF/EqRyjXj/Uic71Stz5oaEu0ILbCmh/EnlK
e9hOb4yfGZNZlTqgKqkKGVeZJMwgOCYkVqGUwk19s06saFrDGqsq0BTlM2iZzStM
d1y//WwUnSWaF05Xpo7cpM6/PkMNYSIv/z2AOG0FySWLr+WlNyVSFzMQUTnwslWu
FirvWuYcKXrvrIQkCyYSTNm4ppd5ORU1bfwnmgGCw/4nkEn0kiR/80QEOOPOjgDa
HjXPoKY11JPgoYdZAiGFEzRIbjnZwCyamJrP0s46bjQ/4XBmFsMo9JdhlCrz558l
jnseC9Kd8LN7HiZzleL5CP2o9fkQ6cFHXmPttwa8uXVJDx/fqhZsItkC6kRpHI5k
JvEg3wOomS3/1vd9fqB9trRAtQM8zO6TWhO95icvXbOo/JVWhOdZqEAO38futLR5
0hBKEyxfLaZAHnBU9OGghZ4Z+N8orzFx7jhybCky/Q+fcbJEuljGmLArkNZRrd4j
xXX+o40ybqASykshehhwCaR4rxqDbhKTo6ZDJK1sZg+dpVCSPSfTDJNhR6gdmbsE
NaOgW+pcHxtezjQ4jSyKaywF2y6FLVrmDqoF5mFmU0KwuRmZBrCdli3P+gw8pA8U
riRzTNqGhvrT5K496/Xz
=EaGp
-END PGP SIGNATURE End Message ---

Processed: severity of 863659 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 863659 serious
Bug #863659 [libgpg-error0] debian/copyright puts LGPL-2.1+ text in GPL-2.1+ 
license block
Severity set to 'serious' from 'minor'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
863659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#827665: marked as done (systemd goes into timeout while waiting for local-fs.target)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 12:36:11 +
with message-id 
and subject line Bug#827665: fixed in live-config 5.20170623
has caused the Debian Bug report #827665,
regarding systemd goes into timeout while waiting for local-fs.target
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.)


-- 
827665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-config-systemd
Version: 5.20160608
Tags: patch

Hello,

The After=local-fs.target rule introduced in commit 63ab809 made systemd
go in timeout while waiting for the local-fs target to be reached.

This is due to the fact that the Before= rule in the live-config unit
prevents the startup of udev.

I'm not raising severity on this one because I suspect this only happens
on installed environments, where live-config-systemd is largely useless.
But still, it shouldn't break the boot process in this way.

I'm attaching a small patch that resolves the problem for me, also
available as a git commit at [1].

I unfortunately haven't had the time to test it in a live environment.


Regards,
Eugenio

[1]
https://github.com/semplice/live-config/commit/672fb6274a74a40880c9fc737accd8d5a3d557f5
-- 
Eugenio Paolantonio - Semplice Linux lead developer

Website: me.medesimo.eu
Twitter: @eugenio_g7

«The UNIX philosophy basically involves giving you enough rope to
hang yourself.  And then a couple of feet more, just to be sure.»
From 672fb6274a74a40880c9fc737accd8d5a3d557f5 Mon Sep 17 00:00:00 2001
From: "Eugenio Paolantonio (g7)" 
Date: Wed, 15 Jun 2016 08:51:56 +0200
Subject: [PATCH] [backend] systemd: do not try to launch live-config before
 udev

The After= rule introduced in 63ab809 made things go in timeout
as udev won't be started before the local-fs target.

Signed-off-by: Eugenio Paolantonio (g7) 
---
 backend/systemd/live-config.systemd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/backend/systemd/live-config.systemd b/backend/systemd/live-config.systemd
index ed7069b..2b82f45 100644
--- a/backend/systemd/live-config.systemd
+++ b/backend/systemd/live-config.systemd
@@ -9,7 +9,7 @@
 [Unit]
 Description=live-config contains the components that configure a live system during the boot process (late userspace).
 Documentation=man:live-config
-Before=basic.target udev.service
+Before=basic.target
 After=local-fs.target
 DefaultDependencies=no
 ConditionPathExists=/bin/live-config


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: live-config
Source-Version: 5.20170623

We believe that the bug you reported is fixed in the latest version of
live-config, 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 827...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated live-config 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, 23 Jun 2017 14:15:17 +0200
Source: live-config
Binary: live-config live-config-doc live-config-systemd live-config-sysvinit
Architecture: source
Version: 5.20170623
Distribution: unstable
Urgency: medium
Maintainer: Live Systems Maintainers 
Changed-By: Raphaël Hertzog 
Description:
 live-config - Live System Configuration Components
 live-config-doc - Live System Configuration Components (documentation)
 live-config-systemd - Live System Configuration Components (systemd backend)
 live-config-sysvinit - Live System Configuration Components (sysvinit backend)
Closes: 827665 855085 858013
Changes:
 live-config (5.20170623) unstable; urgency=medium
 .
   * Drop "Before=udev.service" in live-config-systemd.service as it
 breaks the boot process when you have multiple partitions mounted
 as part of local-fs.target. Closes: #827665, #855085
   * Move Setup_network definition to a shared file and include it
 where it is needed. Closes: #858013
Checksums-Sha1:
 53bb6164047034e2f382a2fe29dd50c53d2ad052 1674 live-config_5.20170623.dsc
 aa71b9627b4380a95031ca33194f6f36f65bca1d 75220 live-config_5.20170623.tar.xz
 75275884affc4a5071db55d66250eadea3978a9c 5357 
live-config_5.2

Bug#865417: efibootmgr: grub-install dummy failed in Stretch installation

[sasha]

ok, I have stretch installed, looking how to boot it (configure grub 
manually)



SH0x@OFTC #debian-boot


On 06/22/2017 10:31 PM, jared.doming...@dell.com wrote:


*Dell Customer Communication

*

I’m saying you can manually add a boot entry if the installer doing it 
fails. That way you’ll be able to boot into stretch and help debug.


*From:*sasha [mailto:sasha.shoko...@gmail.com]
*Sent:* Thursday, June 22, 2017 6:26 AM
*To:* Dominguez, Jared 
*Cc:* 865...@bugs.debian.org; debian-...@lists.debian.org
*Subject:* Re: Bug#865417: efibootmgr: grub-install dummy failed in 
Stretch installation


Oh, sorry, I just didn't see there are more recipients.

Well, If I understand correctly, you are saying to add boot entry 
manually in bios, but its there already ("debian (hdd details)"), and 
when I enter into, I am in grub without any entries, only cli of grub, 
so it seems I should load/configure grub manually (somehow).


/Saulius

On 06/22/2017 12:08 AM, jared.doming...@dell.com 
 wrote:


It depends on your email client, but typically there is a
reply-to-all option.

You could try installing stretch (I assume that was your goal) and
then manually adding a boot entry from your system’s BIOS setup.
As is the typical warning in this sort of scenario, please make
sure you have backups of your data.

--Jared

*From:*sasha [mailto:sasha.shoko...@gmail.com]
*Sent:* Wednesday, June 21, 2017 4:02 PM
*To:* Dominguez, Jared 

*Subject:* Re: Bug#865417: efibootmgr: grub-install dummy failed
in Stretch installation

How did I managed to drop bug tracker? Please explane

How can I install packages from stretch into jessie? or if I'll
try to install stretch to parallel disk how can i get debug info
besides those logs I have sent already?

On 06/21/2017 05:53 PM, jared.doming...@dell.com
 wrote:

I noticed you dropped the bug tracker. Please always include
it as otherwise I cannot usefully track and share this bug
report with others.

Since it seems like you’re actually running Jessie right now,
could you install the versions of efibootmgr and libefivar
from stretch to reproduce (or otherwise provide me debug
information from those versions of those packages)? I don’t
have your motherboard so can’t reproduce myself.

--Jared

*From:*sasha [mailto:sasha.shoko...@gmail.com]
*Sent:* Wednesday, June 21, 2017 9:37 AM
*To:* Dominguez, Jared 

*Subject:* Re: Bug#865417: efibootmgr: grub-install dummy
failed in Stretch installation

Reportbug was run on Jessie and efibootmgr's log was from
jessie as well, but files attached in previews email were from
stretch installation, all logs were from the same hardware. So
now its running Jessie and I could provide logs related
hardware useing Jessie.

$ sudo dmidecode -t bios
# dmidecode 2.12
# SMBIOS entry point at 0x000f05e0
SMBIOS 3.0 present.
# SMBIOS implementations newer than version 2.8 are not
# fully supported by this version of dmidecode.

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 1.60
Release Date: 12/16/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 16384 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.11



$ sudo efibootmgr -V
version 0.11.0

libefivar 0.15-3




On 06/21/2017 05:22 PM, jared.doming...@dell.com
 wrote:

I don't see much in the limited logs you give:

Jun 20 21:17:42 grub-installer: info: Installing grub on
'dummy'

Jun 20 21:17:43 grub-installer: info: grub-install do

Bug#865494: marked as done (logidee-tools: Don't depend on NBS pgf)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 12:20:45 +
with message-id 
and subject line Bug#865494: fixed in logidee-tools 1.2.17
has caused the Debian Bug report #865494,
regarding logidee-tools: Don't depend on NBS pgf
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.)


-- 
865494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: logidee-tools
Version: 1.2.16
Severity: serious
Tags: buster

logidee-tools Build-Depends and Depends on pgf but that is no longer
built in Debian unstable. Please switch the dependency to
texlive-pictures instead.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: logidee-tools
Source-Version: 1.2.17

We believe that the bug you reported is fixed in the latest version of
logidee-tools, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated logidee-tools 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, 23 Jun 2017 13:43:24 +0200
Source: logidee-tools
Binary: logidee-tools
Architecture: source all
Version: 1.2.17
Distribution: unstable
Urgency: medium
Maintainer: Raphaël Hertzog 
Changed-By: Raphaël Hertzog 
Description:
 logidee-tools - Tools to write courses in XML and export them to various 
formats
Closes: 865494
Changes:
 logidee-tools (1.2.17) unstable; urgency=medium
 .
   * Replace "pgf" with "texlive-pictures" in dependencies and build
 dependencies. Closes: #865494 Thanks to Jeremy Bicha for the report.
   * Update VCS URLs as I switched from SVN to git.
   * Drop useless dependency on libxml2 (implicit via xsltproc).
   * Update debhelper compat to 10 and switch to Standards-Version 4.0.0.
   * Update copyright file to machine-readable format.
   * Add autopkgtest tests to ensure setup-logidee-tools works and
 that we can run some of the expected make commands.
   * Add libxml2-utils to Recommends for xmllint used by make check.
Checksums-Sha1:
 d3176de0a23f9484be4e430c21229b3129ea6b50 1544 logidee-tools_1.2.17.dsc
 15984e70a0834c8cbd8df2d950aaac7357d0ef3a 79080 logidee-tools_1.2.17.tar.xz
 7b2da49f64186d8b508227beeb9d8115c3441f53 782052 logidee-tools_1.2.17_all.deb
 250c1ed770b91c9a3cded54e9f8468bd107fd3d9 8087 
logidee-tools_1.2.17_amd64.buildinfo
Checksums-Sha256:
 2ec5b44e925ee8e3c1f42f49532bd762a0b58a8e064bae8b0212f0811126e94d 1544 
logidee-tools_1.2.17.dsc
 f603a1633f60dccaa05df17a37b6eeea37d4d4a701c977298420a4fd6a2d9d25 79080 
logidee-tools_1.2.17.tar.xz
 aac7d49e8366b455f5a5e727af71891742e644cbc8cfdc88c62edcd3b5fd288b 782052 
logidee-tools_1.2.17_all.deb
 10e79e03393dd5f12cd0d2df33b1abf74ec1317cf2ed4d96220fc182a427927a 8087 
logidee-tools_1.2.17_amd64.buildinfo
Files:
 2b72be54b4a3176a5beebe16ce6e2716 1544 text optional logidee-tools_1.2.17.dsc
 ceecea8e47db2b43052ba994043c8c82 79080 text optional 
logidee-tools_1.2.17.tar.xz
 3f8ec668317c890669186038de441696 782052 text optional 
logidee-tools_1.2.17_all.deb
 f8d207a7a39e4b48c8cc07cf750425ac 8087 text optional 
logidee-tools_1.2.17_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAllNASoACgkQA4gdq+vC
mrk3DwgAgafkCjbQD4jT3kpWmpiLpFGegu4PeXpXvShgXPbfY4S17kgzi3XIvGZ1
au83kb3gZt8zypELsVcR1tvargcdP/e2f5viPsrrCFVL8+2ZA8i5DryMYXgDq3+D
VxBIpwRelGPYVeSEUdqfFlRIHmfzR4ZLbmecviSCdi2Xo+oaczEqlGCaRYsRVqMx
XDGHbPQJMS/AcLPxTpFL9EDTq61VBt26yVZYz8ZoftHTPL06Zawtx8IrwYgE243d
ph6/lf5G8IIQOqKI6QmyRO/uYA2T0LAF7olBZ6kWKajtp4FW507NIwxfYQHwHBeO
1BXqmMHekyBIgiBJU+++JXWAh2H7MQ==
=COvM
-END PGP SIGNATURE End Message ---

Bug#865633: [Pkg-libvirt-maintainers] Bug#865633: can't drag windows or click "Activities" in GNOME 3 guest

[Guido Günther]

On Fri, Jun 23, 2017 at 01:20:02PM +0200, Daniel Pocock wrote:
> Package: virt-viewer
> Version: 5.0-1
> Severity: serious
> 
> 
> I recently updated a Debian system, here are the new and old versions of
> each package from dpkg.log
> 
> upgrade virt-viewer:amd64 1.0-1 5.0-1
> upgrade virt-manager:all 1:1.0.1-5 1:1.4.0-5
> upgrade spice-client-gtk:amd64 0.25-1+b1 0.33-3.3
> upgrade libspice-client-glib-2.0-8:amd64 0.25-1+b1 0.33-3.3
> upgrade libspice-server1:amd64 0.12.5-1+deb8u4 0.12.8-2.1
> 
> 
> I connected to an existing session where GNOME 3 is running in a guest
> and I found that I can't drag and drop the windows any more and I can't
> click the "Activities" control.  Clicking other things on the top-bar
> (e.g. the clock) behaves normally.
> 
> I am connecting over ssh
> 
> Is this a known problem?
> 
> I had another system running stretch since about 6 months ago.  It was
> actually working fine on that system last time I checked (about a month
> ago).  That system was fully upgraded yesterday and I notice today it
> has the same bug too.
> 
> I also tried the spicy client instead of virt-viewer, it has the bug too.

If spicy has the same issue I'd start looking in
libspice-client-{gtk,glib}. The virt-* end did not change since quite
some time.
 -- Guido

Bug#865633: [Pkg-libvirt-maintainers] Bug#865633: can't drag windows or click "Activities" in GNOME 3 guest

[Daniel Pocock]

On 23/06/17 13:45, Guido Günther wrote:
> On Fri, Jun 23, 2017 at 01:20:02PM +0200, Daniel Pocock wrote:
>> Package: virt-viewer
>> Version: 5.0-1
>> Severity: serious
>>
>>
>> I recently updated a Debian system, here are the new and old versions of
>> each package from dpkg.log
>>
>> upgrade virt-viewer:amd64 1.0-1 5.0-1
>> upgrade virt-manager:all 1:1.0.1-5 1:1.4.0-5
>> upgrade spice-client-gtk:amd64 0.25-1+b1 0.33-3.3
>> upgrade libspice-client-glib-2.0-8:amd64 0.25-1+b1 0.33-3.3
>> upgrade libspice-server1:amd64 0.12.5-1+deb8u4 0.12.8-2.1
>>
>>
>> I connected to an existing session where GNOME 3 is running in a guest
>> and I found that I can't drag and drop the windows any more and I can't
>> click the "Activities" control.  Clicking other things on the top-bar
>> (e.g. the clock) behaves normally.
>>
>> I am connecting over ssh
>>
>> Is this a known problem?
>>
>> I had another system running stretch since about 6 months ago.  It was
>> actually working fine on that system last time I checked (about a month
>> ago).  That system was fully upgraded yesterday and I notice today it
>> has the same bug too.
>>
>> I also tried the spicy client instead of virt-viewer, it has the bug too.
> 
> If spicy has the same issue I'd start looking in
> libspice-client-{gtk,glib}. The virt-* end did not change since quite
> some time.

Could it need to be rebuilt?

Does anybody else see the same problem?

The guest is Debian jessie / default GNOME 3 desktop and the client is
Debian stretch / default GNOME 3 desktop.

I also raised it upstream[1], they suggested Wayland could be a problem
(stretch default) but I disabled Wayland and I still have the problem.

Regards,

Daniel


1. https://lists.freedesktop.org/archives/spice-devel/2017-June/038386.html

Bug#865552: libbpp-phyl FTBFS with test failures

[Andreas Tille]

Hi Adrian,

thanks a lot for your continuous QA effort (I have the feeling that 90%
of the Debian Med bugs were issued by you ;-) ).

Julien, do you have some explanation for the issue?  I made sure that
cmake files were found also on i386 so the issue now concerns
   Version: 2.3.1-3
but bpp-phyl seems to have issues for non-Intel architectures which
should be dealt by upstream.  I admit that I have not checked version
2.3.1-1 but according to Git the diff is


$ git diff debian/2.3.1-1..debian/2.3.1-2
diff --git a/debian/changelog b/debian/changelog
index 0bfd365..28fd024 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libbpp-phyl (2.3.1-2) unstable; urgency=medium
+
+  * Make sure cmake files will be installed also on i386
+
+ -- Andreas Tille   Thu, 22 Jun 2017 08:03:24 +0200
+
 libbpp-phyl (2.3.1-1) unstable; urgency=medium
 
   * New upstream version
diff --git a/debian/rules b/debian/rules
index 9d1fe92..3a46afc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -15,5 +15,5 @@ override_dh_install:
--override 
's/libbpp-\([-a-z]\+\)[0-9]\+-dev/libbpp-\1-dev/' \
--exclude-la \
 --movedev debian/tmp/usr/include/* usr/include \
---movedev debian/tmp/usr/lib/$(DEB_HOST_GNU_TYPE)/cmake 
usr/lib/$(DEB_HOST_GNU_TYPE) \
+--movedev debian/tmp/usr/lib/*/cmake 
usr/lib/$(DEB_HOST_GNU_TYPE) \
 debian/tmp/usr/lib/*/*.so


So I can not see any explanation for the test failures since the test is
run before dh_install anyway.  I suspect some deeper issue here.

Kind regards

  Andreas.

On Thu, Jun 22, 2017 at 08:13:02PM +0300, Adrian Bunk wrote:
> Source: libbpp-phyl
> Version: 2.3.1-2
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=libbpp-phyl&suite=sid
> 
> I do not see any obvious reason why 2.3.1-2 fails on so many
> architectures where 2.3.1-1 built just a few hours earlier.

-- 
http://fam-tille.de

Bug#863801: grub-coreboot: fails to upgrade from jessie to stretch if init-select was installed

[Colin Watson]

On Wed, May 31, 2017 at 01:42:34PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Setting up grub-coreboot (2.02~beta3-5) ...
>   Installing new version of config file /etc/kernel/postinst.d/zz-update-grub 
> ...
>   Installing new version of config file /etc/kernel/postrm.d/zz-update-grub 
> ...
>   /var/lib/dpkg/info/grub-coreboot.config: 1: 
> /etc/default/grub.d/init-select.cfg: /usr/lib/init-select/get-init: not found
>   dpkg: error processing package grub-coreboot (--configure):
>subprocess installed post-installation script returned error exit status 
> 127
> 
> 
> This is most likely a bug in init-select, but since that package
> does not exist in stretch any more (and it will be removed during the
> upgrade from jessie to stretch due to dependencies/conflicts),
> grub-coreboot will have to work around the bug.

This is a tricky bug, so CCing debian-devel for comments.  (Note that
this applies to all grub- binary packages, not just
grub-coreboot.)

The basic problem in init-select is of course the good old favourite of
a conffile not behaving correctly when the package has been removed but
not purged.  This is probably worth fixing in unstable as follows, since
init-select is still there:

--- a/init-select.cfg
+++ b/init-select.cfg
@@ -1,1 +1,1 @@
-GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
$(/usr/lib/init-select/get-init)"
+GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT $([ ! -x 
/usr/lib/init-select/get-init ] || /usr/lib/init-select/get-init)"

I propose to NMU init-select with this change after a bit of testing and
the usual delay, since it would generally make life easier if there were
a non-broken version around somewhere.  We might also want to think
about putting that into jessie-proposed-updates.

However, I take Andreas's point that we need to work around this
somehow, probably in a stretch point release now, and that's where I
need feedback.  One possible approach would be to change grub-mkconfig
to do something like this:

  for x in ${sysconfdir}/default/grub.d/*.cfg ; do
if [ "$(basename "$x")" = init-select.cfg ] && [ ! -x 
/usr/lib/init-select/get-init ]; then
  # work around #863801
  continue
fi
if [ -e "${x}" ]; then
  . "${x}"
fi
  done

But that lumbers me with having to maintain a workaround patch forever,
since there's no guarantee that init-select would ever be purged from
affected systems.  I appreciate that it's only a few lines, but these
things pile up over time.  I also don't think that ignoring errors from
/etc/default/grub.d/*.cfg scripts is a good idea: they might actually be
important to booting the system, even though they aren't in this case.

I'd rather do something like checking in the postinst whether these
conditions hold:

 * init-select is removed but not purged
 * /etc/default/grub.d/init-select.cfg contents match the buggy contents
   shown above

... and if so, replace /etc/default/grub.d/init-select.cfg with the
corrected version, coordinated with the NMU above.  This ought to mean
that if a fixed version of init-select is installed in the future, then
there'll be no conffile prompt because the new version is already in
place.  It would open the possibility of a potential conffile prompt in
future if the conffile in question is changed further, but it doesn't
seem to me that init-select has a sufficiently long likely future
lifespan for this to be very probable.  Replacing the file with a
corrected version is better than removing it, moving it aside, or
commenting out the offending line, since none of those would have the
desired behaviour in the event that a fixed version of init-select is
installed.

The benefit of this approach, even though it's a bit more complicated,
is that I could eventually drop it once users can be expected to have
upgraded through a grub-* package containing this workaround.  That
means that I don't have to carry a permanent patch just because some
other package made use of my package's extension facilities and got it
wrong.

I fully appreciate that this is skating along the edge of policy's
requirements regarding conffiles, and arguably violates at least 10.7.4
"The maintainer scripts must not alter a conffile of any package,
including the one the scripts belong to".  However, I think that this is
a reasonable case of self-defence, and could be tolerable with
sufficient commentary and care.  I doubt I would be contemplating it if
init-select hadn't been removed from stretch.

Thoughts?  Can anyone think of a better solution than either of the two
I've outlined here?

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#865633: can't drag windows or click "Activities" in GNOME 3 guest

[Daniel Pocock]

Package: virt-viewer
Version: 5.0-1
Severity: serious


I recently updated a Debian system, here are the new and old versions of
each package from dpkg.log

upgrade virt-viewer:amd64 1.0-1 5.0-1
upgrade virt-manager:all 1:1.0.1-5 1:1.4.0-5
upgrade spice-client-gtk:amd64 0.25-1+b1 0.33-3.3
upgrade libspice-client-glib-2.0-8:amd64 0.25-1+b1 0.33-3.3
upgrade libspice-server1:amd64 0.12.5-1+deb8u4 0.12.8-2.1


I connected to an existing session where GNOME 3 is running in a guest
and I found that I can't drag and drop the windows any more and I can't
click the "Activities" control.  Clicking other things on the top-bar
(e.g. the clock) behaves normally.

I am connecting over ssh

Is this a known problem?

I had another system running stretch since about 6 months ago.  It was
actually working fine on that system last time I checked (about a month
ago).  That system was fully upgraded yesterday and I notice today it
has the same bug too.

I also tried the spicy client instead of virt-viewer, it has the bug too.

Processed: severity of 865511 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 865511 serious
Bug #865511 [src:haskell-tls] haskell-tls: FTBFS, missing quickcheck dependency?
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865575: marked as done (miaviewit FTBFS with mia 2.4.4-1)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 10:51:08 +
with message-id 
and subject line Bug#865575: fixed in miaviewit 1.0.5-1
has caused the Debian Bug report #865575,
regarding miaviewit FTBFS with mia 2.4.4-1
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.)


-- 
865575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: miaviewit
Version: 1.0.4-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/miaviewit.html

...
In file included from /usr/include/mia-2.4/mia/3d/fullcost.hh:24:0,
 from /usr/include/mia-2.4/mia/3d.hh:30,
 from /usr/include/mia-2.4/mia.hh:26,
 from ../viewit/glvector.hh:32,
 from glvector.cc:23:
/usr/include/mia-2.4/mia/3d/transform.hh:324:21: note: declared here
  virtual C3DFVector apply(const C3DFVector& x) const  
__attribute__((deprecated));
 ^
camera.cc:35:15: error: 'mia::CWatch::CWatch()' is protected within this context
 static CWatch watch;
   ^
In file included from /usr/include/mia-2.4/mia/core.hh:39:0,
 from /usr/include/mia-2.4/mia.hh:24,
 from ../viewit/camera.hh:30,
 from camera.cc:23:
/usr/include/mia-2.4/mia/core/watch.hh:45:2: note: declared protected here
  CWatch();
  ^~
camera.cc:35:15: error: cannot declare variable 'watch' to be of abstract type 
'mia::CWatch'
 static CWatch watch;
   ^
...
--- End Message ---
--- Begin Message ---
Source: miaviewit
Source-Version: 1.0.5-1

We believe that the bug you reported is fixed in the latest version of
miaviewit, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated miaviewit 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: Fri, 23 Jun 2017 10:03:31 +
Source: miaviewit
Binary: libmiaviewit0 libmiaviewit-dev mia-viewit
Architecture: source
Version: 1.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 libmiaviewit-dev - development files for the 3D visualization library
 libmiaviewit0 - MIA addon library for 3D visualization
 mia-viewit - Viewer program for 3D data sets created by using MIA
Closes: 865575
Changes:
 miaviewit (1.0.5-1) unstable; urgency=medium
 .
   * New upstream version 1.0.5, Closes: #865575
   * d/control: update standards version to 4.0.0
   * d/control: correct my uploader e-mail address
Checksums-Sha1:
 c900d8b9a3bb0181719183759346fbd9c011a98c 1864 miaviewit_1.0.5-1.dsc
 e0415b180d7e496144f592785221c34ad32b8b3f 633404 miaviewit_1.0.5.orig.tar.gz
 01640ea2be69a1aca9978d54fae15e9995373454 3416 miaviewit_1.0.5-1.debian.tar.xz
 3c3ec550722b3de886847a3abf02342dca0cfbb7 17452 
miaviewit_1.0.5-1_source.buildinfo
Checksums-Sha256:
 1327709c87614b6a190c596dce873998620814ddb32e48de50cfc37174eab38c 1864 
miaviewit_1.0.5-1.dsc
 db35cdd67623d04319ed250532efe35fb44092be6e9b35a2ded0008a4ca204c6 633404 
miaviewit_1.0.5.orig.tar.gz
 4dc08e86e09fa0d3af736b067d7c965f21daefc8002762fc96069e0d0c0c1fea 3416 
miaviewit_1.0.5-1.debian.tar.xz
 e9347a813056267a85704f8d01b291cd86e85327ea2775e7cc0b718c8a603b84 17452 
miaviewit_1.0.5-1_source.buildinfo
Files:
 b77c9318c0801c713cb5aefe11341290 1864 science optional miaviewit_1.0.5-1.dsc
 05d4c5fd9bdffbfa242b5bc15d2888c0 633404 science optional 
miaviewit_1.0.5.orig.tar.gz
 490f22aaefcaebf3e2dcd7aac27fcfbd 3416 science optional 
miaviewit_1.0.5-1.debian.tar.xz
 ef94e17671dc4fc91c78ce938dadc57c 17452 science optional 
miaviewit_1.0.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEENGr+2YOvnEff6Rr7+B42i5smq5gFAllM6xMACgkQ+B42i5sm
q5iuVQgAlU8aTRu8CrCBspXle09691fnIFJVN9Mw3XP31QLYUQrGnnM8KnyH2vHv
YsAtuCg++pHZsW1rhDbq6CZhtg11e5UONG4WjokAZp18ZH8VOW6s+wuphBrtTX/v
UJKtZrQAZvjvOgpyc4jz4sDAkSQm7seSN4nfu/yxxdTKz1PVrD6dYiAqElvwzPd4
84FXY/eRfdtYEj2+DJCOa27jH17tQJ/XtJVhMe8wq5dv0FWRPaSoCgQMTBDF/dZJ
tYpjEuFLDQsnrBbWb+dJ6AYRY90B7zHAydzDkizq

Processed: severity of 856951 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 856951 grave
Bug #856951 [runc] runc: does not work with systemd hybrid cgroup hierarchy
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
856951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865465: marked as done (openmpi FTBFS on s390x: undefined reference to opal_atomic_*)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 09:38:15 +
with message-id 
and subject line Bug#865465: fixed in openmpi 2.1.1-6
has caused the Debian Bug report #865465,
regarding openmpi FTBFS on s390x: undefined reference to opal_atomic_*
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.)


-- 
865465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmpi
Version: 2.1.1-4
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=openmpi&arch=s390x&ver=2.1.1-4&stamp=1498044812&raw=0

...
  CCLD opal_wrapper
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_add_32'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_swap_32'
../../../opal/.libs/libopen-pal.so: undefined reference to 
`opal_atomic_cmpset_ptr'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_sub_32'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_mb'
../../../opal/.libs/libopen-pal.so: undefined reference to 
`opal_atomic_swap_ptr'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_lock'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_wmb'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_unlock'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_init'
collect2: error: ld returned 1 exit status
Makefile:1785: recipe for target 'opal_wrapper' failed
make[3]: *** [opal_wrapper] Error 1
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 2.1.1-6

We believe that the bug you reported is fixed in the latest version of
openmpi, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi 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: Thu, 22 Jun 2017 22:46:24 +0100
Source: openmpi
Binary: openmpi-bin libopenmpi-dev libopenmpi2 openmpi-common openmpi-doc
Architecture: source amd64 all
Version: 2.1.1-6
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi2 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 openmpi-common - high performance message passing library -- common files
 openmpi-doc - high performance message passing library -- man pages
Closes: 865465
Changes:
 openmpi (2.1.1-6) unstable; urgency=medium
 .
   * Use --enable-builtin-atomics on s390x. Delete test patch Closes: #865465
Checksums-Sha1:
 03cb26541d0747ef37b833de92cbb05524906049 2705 openmpi_2.1.1-6.dsc
 4dd5f75ecccd860b3977f16e0ec14a06dd68e699 59744 openmpi_2.1.1-6.debian.tar.xz
 50422a42baefe861fa0d0e0e9c302820a3075d20 18990 
libopenmpi-dev-dbgsym_2.1.1-6_amd64.deb
 eb7ecf42a6abc6f9e4e4b6c41785278e6981fe44 1025590 
libopenmpi-dev_2.1.1-6_amd64.deb
 dff49861248ffb6a6462953c7124bd98bb526cda 20805112 
libopenmpi2-dbgsym_2.1.1-6_amd64.deb
 5ea851092c73feb938f215782b63f7335c54f148 2062212 libopenmpi2_2.1.1-6_amd64.deb
 9efd293b0aaf82e8585ae995beecda12eddd4d7c 203652 
openmpi-bin-dbgsym_2.1.1-6_amd64.deb
 22e02f7a4bb106c1935d8362977925ef82552086 192566 openmpi-bin_2.1.1-6_amd64.deb
 c97d81fa88877e86c725bd12e90408a2eecc4c76 154076 openmpi-common_2.1.1-6_all.deb
 914f8c8d5219956c77c399937376a6b6d78eec4e 713184 openmpi-doc_2.1.1-6_all.deb
 85e4c67b654519af3ccf25796ad851bdb37c8a65 12442 openmpi_2.1.1-6_amd64.buildinfo
Checksums-Sha256:
 ea52e7ac7c5b41379c6b6847a84a4ee0418250441e1e8a6d1d3cd5c4e200be83 2705 
openmpi_2.1.1-6.dsc
 15c1216785d955383cfdf52d28914d6dbecdcf96ae1640d02fb6e6315c577fa7 59744 
openmpi_2.1.1-6.debian.tar.xz
 d76bf88fe49511c14a4bba998b1d712b69ff9d3c23510e01863d15677c6903b5 18990 
libopenmpi-dev-dbgsym_2.1.1-6_amd64.deb
 66655c40da2103a09d2b3ad5f1d884c18bd15540e3c656018032e31a41a39d12 1025590 
libopenmpi-dev_2.1.1-6_amd64.deb
 10222b1a6d69b5772a511384cb12d56b4dbbc5c1f86551b102481fb6a3

Processed: reopening 865317

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 865317
Bug #865317 {Done: Stephen Kitt } [src:miller] miller FTBFS 
on mips: FAIL run (exit status: 1)
'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 miller/5.2.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865615: marked as done (mia: Reduce build-time memory usage on mips/mipsel to fix FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 09:24:08 +
with message-id 
and subject line Bug#865615: fixed in mia 2.4.4-2
has caused the Debian Bug report #865615,
regarding mia: Reduce build-time memory usage on mips/mipsel to fix FTBFS
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.)


-- 
865615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mia
Version: 2.4.4-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/package.php?p=mia&suite=sid

...
virtual memory exhausted: Cannot allocate memory
mia/2d/maskedcost/CMakeFiles/2dimage-maskedcost-ncc-common.dir/build.make:65: 
recipe for target 
'mia/2d/maskedcost/CMakeFiles/2dimage-maskedcost-ncc-common.dir/ncc.cc.o' failed
...


On mips/mipsel only 2 GB address space are available for userspace.

The following change addresses this by reducing the amount of
debug info generated to what is required for backtraces:

--- debian/rules.old2017-06-22 21:09:04.0 +
+++ debian/rules2017-06-22 21:39:05.0 +
@@ -1,10 +1,18 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed -fvisibility=hidden
 
+# reduce debug info to fix FTBFS on archs with few address space
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+  export DEB_CFLAGS_MAINT_APPEND = -g1
+  export DEB_CXXFLAGS_MAINT_APPEND = -g1
+endif
+
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
--- End Message ---
--- Begin Message ---
Source: mia
Source-Version: 2.4.4-2

We believe that the bug you reported is fixed in the latest version of
mia, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated mia 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: Fri, 23 Jun 2017 08:07:43 +
Source: mia
Binary: libmia-2.4-4 libmia-2.4-dev libmia-2.4-doc mia-tools mia-doctools 
mia-tools-doc
Architecture: source
Version: 2.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 libmia-2.4-4 - library for 2D and 3D gray scale image processing
 libmia-2.4-dev - library for 2D and 3D gray scale image processing, 
development fi
 libmia-2.4-doc - library for 2D and 3D gray scale image processing, 
documentation
 mia-doctools - Helper scripts for run-time document creation
 mia-tools  - Command line tools for gray scale image processing
 mia-tools-doc - Cross-referenced documentation of the MIA command line tools
Closes: 865615
Changes:
 mia (2.4.4-2) unstable; urgency=medium
 .
   * d/rules: Reduce build-time memory usage on mips/mipsel to fix FTBFS
 Thanks: Adrian Bunk, Closes: #865615
   * d/control: Update standards version to 4.0.0
Checksums-Sha1:
 14bb1078a8cf0e4d1f06443b557a2972ca6f24f6 2254 mia_2.4.4-2.dsc
 a36c67a39e64978650e774daed628c91876f66be 11276 mia_2.4.4-2.debian.tar.xz
 916df6b2e8d96409d00523a4de048f95a7d7888d 20350 mia_2.4.4-2_source.buildinfo
Checksums-Sha256:
 9adc7a8dfe949c04a1f93dbe83c170d99ed32a26189b84a64716feaa87c2e109 2254 
mia_2.4.4-2.dsc
 7e36c0dc23de509cf52bb3ef87995f2050f2f6e47a58124e2a0469c95cb0f739 11276 
mia_2.4.4-2.debian.tar.xz
 2fd067363d2cd40b9a674d71485063570e9dc395057c9676e3ee4bff580f812f 20350 
mia_2.4.4-2_source.buildinfo
Files:
 1fbb6e3e0f4fdc1834e32f242ccd21bb 2254 science optional mia_2.4.4-2.dsc
 a28f21b981405dbbe2b295101a4b5f3e 11276 science optional 
mia_2.4.4-2.debian.tar.xz
 d99035af3d01ffa72dd7c9f9bbceb598 20350 science optional 
mia_2.4.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEENGr+2YOvnEff6Rr7+B42i5smq5gFAllM2rUACgkQ+B42i5sm
q5hUbAf+M7sgaBHBhb7BD0T6rsBc7LrpzslOxraGaZsinEPSQEzWTXeIUp0Dr+pN
JRrZ5SSR6t5q2uRCceJwd9rJeyvtiU+cJu1dYD/mFIScEtjLT6hjtVZ+FoJV7W40
SjmGzlzGNEMUh3bAzC4wgP6TZgw2OOqnHtoPyFrHAUK+/tqUk9u+pddI1o2G4YAv
hnZW/FfZQ3KkrehX4Om+hHTypXL0/a+sbfcaJJ+0//NwqvkvJ2Q9NtcH8fckkNRr
8ndWZ+lBoGlA+c3/sToBMUt/dIaIBRrpUX5

Bug#865461: unrar: VMSF_DELTA filter in unrar allows arbitrary memory write

[Felix Geyer]

On 23.06.2017 10:26, Raphael Hertzog wrote:
> Hello Felix,
>
> On Thu, 22 Jun 2017, Felix Geyer wrote:
>> I've prepared a backported patch of the relevant changes from 5.5.5 for 
>> jessie and stretch.
> How did you identify the relevant changes from 5.5.5 given that we
> don't have any git repository and that we don't have access to the
> previous release (5.5.4?) either AFAIK?

You can still download version 5.5.4:
http://www.rarlab.com/rar/unrarsrc-5.5.4.tar.gz

The 5.5.4 -> 5.5.5 diff contains some changes regarding input validation.
Those aren't directly related to this issue and are more difficult to backport 
so I've skipped them.

Felix

Bug#865233: marked as done (auto-multiple-choice-common: depends on non-existing package latex-xcolor)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 08:50:36 +
with message-id 
and subject line Bug#865233: fixed in auto-multiple-choice 1.3.0-3
has caused the Debian Bug report #865233,
regarding auto-multiple-choice-common: depends on non-existing package 
latex-xcolor
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.)


-- 
865233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: auto-multiple-choice-common
Version: 1.3.0-2
Severity: serious
Justification: unfulfillable dependency

Dear maintainer,

latex-xcolor has been a dummy transitional package now since 2 releases
(since oldstable), and has been dropped in current unstable.

Please update your dependencies to texlive-latex-recommended.

Thanks

Norbert

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-rc4+ (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages auto-multiple-choice-common depends on:
ii  ghostscript9.20~dfsg-3.2
ii  imagemagick8:6.9.7.4+dfsg-11
ii  imagemagick-6.q16 [imagemagick]8:6.9.7.4+dfsg-11
pn  latex-xcolor   
ii  libarchive-zip-perl1.59-1
pn  libdbd-sqlite3-perl
ii  libdbi-perl1.636-1+b1
ii  libfile-mimeinfo-perl  0.27-1
pn  libglib-object-introspection-perl  
pn  libgraphics-magick-perl
ii  libgtk2-perl   2:1.2499-1
ii  liblocale-gettext-perl 1.07-3+b1
ii  libperl5.24 [libio-compress-perl]  5.24.1-3
ii  librsvg2-common2.40.16-1+b1
ii  libtext-csv-perl   1.33-2
ii  libxml-simple-perl 2.22-1
ii  libxml-writer-perl 0.625-1
ii  netpbm 2:10.0-15.3+b2
ii  perl   5.24.1-3
ii  poppler-utils  0.48.0-2
ii  tex-common 6.06
ii  texlive-fonts-extra2017.20170619-2
ii  texlive-fonts-recommended  2017.20170619-1
ii  texlive-generic-recommended2017.20170619-1
ii  texlive-latex-base 2017.20170619-1
ii  texlive-latex-extra2017.20170619-2
ii  unzip  6.0-21

Versions of packages auto-multiple-choice-common recommends:
ii  fonts-linuxlibertine [ttf-linux-libertine]  5.3.0-2
pn  libemail-mime-perl  
pn  libemail-sender-perl
pn  libgtk2-notify-perl 
pn  libnet-cups-perl
pn  libopenoffice-oodoc-perl
pn  libsys-cpu-perl 
ii  texlive-xetex   2017.20170619-1

auto-multiple-choice-common suggests no packages.
--- End Message ---
--- Begin Message ---
Source: auto-multiple-choice
Source-Version: 1.3.0-3

We believe that the bug you reported is fixed in the latest version of
auto-multiple-choice, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexis Bienvenüe  (supplier of updated auto-multiple-choice 
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, 20 Jun 2017 23:18:05 +0200
Source: auto-multiple-choice
Binary: auto-multiple-choice auto-multiple-choice-common 
auto-multiple-choice-doc auto-multiple-choice-doc-pdf
Architecture: source all amd64
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Alexis Bienvenüe 
Changed-By: Alexis Bienvenüe 
Description:
 auto-multiple-choice - Auto Multiple Choice - multiple choice papers management
 auto-multiple-choice-common - Auto Multiple Choice - architecture independent 
files
 auto-multiple-choice-doc - Auto Multiple Choice - HTML documentation
 auto-multiple-choice

Bug#865461: unrar: VMSF_DELTA filter in unrar allows arbitrary memory write

[Raphael Hertzog]

Hello Felix,

On Thu, 22 Jun 2017, Felix Geyer wrote:
> I've prepared a backported patch of the relevant changes from 5.5.5 for 
> jessie and stretch.

How did you identify the relevant changes from 5.5.5 given that we
don't have any git repository and that we don't have access to the
previous release (5.5.4?) either AFAIK?

> Review and testing is welcome of course :)
> I haven't checked if the patch applies to wheezy as well but it should be at 
> least a starting point.

Certainly, thanks for your work.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#865549: linux-image-3.16.0-4: stackguard fix incorrect

[Moritz Bechler]

Hi,

Fyi, the original patch also breaks openjdk (SEGV from JNI_CreateJavaVM)
when the VM is launched on the main thread (which is not the case for
the normal java launcher, but embedded uses - e.g. browser plugin <
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772>,
commons-daemon, ...).


Can confirm that the updated patch fixes the problem (amd64).


regards

Moritz

Processed: Re: django-sekizai FTBFS with Django 1.11: TypeError: context must be a dict rather than SekizaiContext

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 865590 django-sekizai FTBFS with Django 1.11: TypeError: context must 
> be a dict rather than SekizaiContext
Bug #865590 [src:django-sekizai] django-sekizai FTBFS with Django 1.11
Changed Bug title to 'django-sekizai FTBFS with Django 1.11: TypeError: context 
must be a dict rather than SekizaiContext' from 'django-sekizai FTBFS with 
Django 1.11'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: [Pkg-rust-maintainers] Processed (with 1 error): Re: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 865416 src:linux
Bug #865416 [cargo] cargo: segfaults some of the time on ppc64el, can't 
reproduce in gdb
Bug reassigned from package 'cargo' to 'src:linux'.
No longer marked as found in versions cargo/0.17.0-2.
Ignoring request to alter fixed versions of bug #865416 to the same values 
previously set
> forcemerge 865549 865416
Bug #865549 [src:linux] linux: stack-guard fix for CVE-2017-1000364 incorrect
Bug #865416 [src:linux] cargo: segfaults some of the time on ppc64el, can't 
reproduce in gdb
Severity set to 'critical' from 'grave'
Added indication that 865416 affects cargo
Marked as found in versions linux/4.9.30-2+deb9u1 and linux/3.16.43-2+deb8u1.
Added tag(s) moreinfo.
Merged 865416 865549
> affects 865549 + cargo
Bug #865549 [src:linux] linux: stack-guard fix for CVE-2017-1000364 incorrect
Bug #865416 [src:linux] cargo: segfaults some of the time on ppc64el, can't 
reproduce in gdb
Ignoring request to set affects of bug 865549 to the same value previously set
Ignoring request to set affects of bug 865416 to the same value previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865416
865549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 865571 in mingw-w64/5.0.2-1, notfound 865571 in mingw-w64-tools/5.0.2-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 865571 mingw-w64/5.0.2-1
Bug #865571 {Done: Stephen Kitt } [mingw-w64-tools] alliance 
and mingw-w64-tools: error when trying to install together
Marked as found in versions mingw-w64/5.0.2-1.
> notfound 865571 mingw-w64-tools/5.0.2-1
Bug #865571 {Done: Stephen Kitt } [mingw-w64-tools] alliance 
and mingw-w64-tools: error when trying to install together
The source mingw-w64-tools and version 5.0.2-1 do not appear to match any 
binary packages
No longer marked as found in versions mingw-w64-tools/5.0.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865317: marked as done (miller FTBFS on mips: FAIL run (exit status: 1))

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2017 07:20:39 +
with message-id 
and subject line Bug#865317: fixed in miller 5.2.1-2
has caused the Debian Bug report #865317,
regarding miller FTBFS on mips: FAIL run (exit status: 1)
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.)


-- 
865317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: miller
Version: 5.2.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=miller&suite=sid

...
Tests completed: 2713
FAIL run (exit status: 1)


Testsuite summary for mlr 5.2.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See c/reg_test/test-suite.log

Makefile:665: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1
...


The same build failure on powerpc is an indication that it
could be a 32bit big endian problem.
--- End Message ---
--- Begin Message ---
Source: miller
Source-Version: 5.2.1-2

We believe that the bug you reported is fixed in the latest version of
miller, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated miller 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, 23 Jun 2017 09:04:14 +0200
Source: miller
Binary: miller
Architecture: source
Version: 5.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 miller - name-indexed data processing tool
Closes: 865317
Changes:
 miller (5.2.1-2) unstable; urgency=medium
 .
   * Add upstream fix for %d integer size issue. Closes: #865317; thanks to
 James Cowgill for the detailed analysis!
Checksums-Sha1:
 1e3882f01106520a27ecfea46cabd2ff92579fd5 1830 miller_5.2.1-2.dsc
 9bc5a606d2873498122d6fd7cbe1d1d859c39957 4964 miller_5.2.1-2.debian.tar.xz
 706111b2ec74835d423caba1ff02ead6a6da9635 5748 miller_5.2.1-2_source.buildinfo
Checksums-Sha256:
 5890319b1cbde31989ddfbe01f178a23786292a5ed6ff7ec0a4115d3f36d133b 1830 
miller_5.2.1-2.dsc
 9092a1365ea7a491349b53a723617d7fbf62c6f28e0306e20d06f2c3022f84b6 4964 
miller_5.2.1-2.debian.tar.xz
 71a9df0785c79de5998dd0773dd2bf70c6ca8756d1b712e276b9fc5b1026eb40 5748 
miller_5.2.1-2_source.buildinfo
Files:
 a0699808e0f7ecb992dfa8ea56904330 1830 utils optional miller_5.2.1-2.dsc
 fa0a743f4c0599ce122dd83d9f582b25 4964 utils optional 
miller_5.2.1-2.debian.tar.xz
 06a48a1ba21d2c474a4cc1df17ce89ef 5748 utils optional 
miller_5.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAllMvY8ACgkQgNMC9Yht
g5zz3A/9Fbq2k38UvxPu25Ccxc0b/jOgIop0pBvousHUfesBEDZ6f+W8sf0kBtJd
2D2kvPvaMrAeM8CKxG40vpsNw7VoXLYGCIwJosC6ZGX3tb5xQ+yFH4XhkEMIUcvZ
N0zyxdySowvhAlDRnkVPmXF2tIN/4dsjgLFa0UNuN/Iy5ZFH+MH0z0s+ZNQFG0D6
s41wHyH9NrEMYQ8WNvXOhK9cLQ5KIQSCu8x7CMv0VJx8KI9ZNCXu8kkswRi8cc9s
1rnxVOJfM+kWhRr1GKg4EaPn/PFnL4I+pBDnkI7ahAOpg411afo3kYTlGn/yBRzL
AvLfXLu2mKjn9+IFabn/D/EinD6U1zjzp9v9pO4iY37SqkHWIjvS3rVCZaKfF3S4
QyXxuBNifmib0m1BkXwGYL7QvhaLsjv6JGVfVQ2079uHP4hXAU56hhtKOY94fcFc
3ZjLU69OtZ9UhIVD7V6gXbHyDyPcUdrjevM4CJqiiGUi7WzVfAbLLHh8ayS/6yLQ
4xTEE19HboW29hZLB6Lx6QuGatteUoWaB+vEhDehDf10E03KzyRRrtUewq8LsksV
ntUHV0HsF/95d/FTTGmzpK7LdCSVTE3bc8zUP1kidbeuv+5gA83pjVtc1RQE8uHM
+27pCaZWGIcIWKDdEQR6JZDcMqbjpa+TZ0Aw7sgoD9poSGoVCaA=
=Ag9s
-END PGP SIGNATURE End Message ---

Processed: found 865571 in mingw-w64-tools/5.0.2-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 865571 mingw-w64-tools/5.0.2-1
Bug #865571 {Done: Stephen Kitt } [mingw-w64-tools] alliance 
and mingw-w64-tools: error when trying to install together
The source mingw-w64-tools and version 5.0.2-1 do not appear to match any 
binary packages
Marked as found in versions mingw-w64-tools/5.0.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 865416
Bug #865549 [src:linux] linux: stack-guard fix for CVE-2017-1000364 incorrect
Unable to merge bugs because:
package of #865416 is 'cargo' not 'src:linux'
Failed to forcibly merge 865549: Did not alter merged bugs.


-- 
865416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865416
865549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865549: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el

[Ximin Luo]

Control: forcemerge -1 865416

It's fixed by the kernel you linked:

$ uname -a
Linux page 3.16.0-4-powerpc64le #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-21) 
ppc64le GNU/Linux
$ for i in {1..10}; do cargo/bin/cargo -V; done
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)

Thanks!

Ximin Luo:
> jrtc27 graciously lent me access to a VM so I'm building it now and will test 
> it some time tomorrow.
> 
> X
> 
> Ximin Luo:
>> Hi, unfortunately I don't have root access to any ppc64el machines to be 
>> able to install a new kernel, I only have access to plummer.debian.org. 
>> (Also you didn't build them for ppc64el yet.)
>>
>> There are some things different about what we're seeing in cargo, vs the 
>> provided C code that segfaults. However the timing is too coincidental so 
>> I'm still inclined to think it's caused by this bug. But unfortunately I 
>> don't know how I can test this myself.
>>
>> Could you release this to stable so that I can ask the buildd people to 
>> install this on plummer, so I can test it?
>>
>> Or, if anyone else is able to test it, you can download and extract this: 
>> https://static.rust-lang.org/dist/rust-1.18.0-powerpc64le-unknown-linux-gnu.tar.gz
>>  then run `for i in {1..10}; do 
>> rust-1.18.0-powerpc64le-unknown-linux-gnu/cargo/bin/cargo -V; done` and see 
>> if it segfaults.
>>
>> X
>>
>> Ben Hutchings:
>>> Control: tag -1 moreinfo
>>>
>>> On Thu, 22 Jun 2017 19:02:26 +0200 Ximin Luo 
>>> wrote:
 Package: linux-image-3.16.0-4-powerpc64le
 Version: 3.16.43-2+deb8u1
 Severity: critical
 Justification: breaks unrelated software
  
 Dear Maintainer,
  
 I have been getting segfaults trying to build cargo on ppc64el
  
 https://github.com/rust-lang/cargo/issues/4197
  
 The signs point to the recent stack guard fix as being the culprit, I can
 confirm that the test program given here:
  
 http://www.openwall.com/lists/oss-security/2017/06/22/6
  
 indicates the presence of the bug on plummer.debian.org. I'm not very 
 familiar
 with kernel development so I don't know where the proper fix is, but 
 subsequent
 discussion on that thread suggests that mainline has the "correct fix" 
 whereas
 some distros applied an incorrect one.
>>>
>>> Can you please test with this candidate fix?
>>> https://people.debian.org/~benh/packages/CVE-2017-1000364/
>>>
>>> Ben.
>>>
>>
>>
> 
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#865615: mia: Reduce build-time memory usage on mips/mipsel to fix FTBFS

[Adrian Bunk]

Source: mia
Version: 2.4.4-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/package.php?p=mia&suite=sid

...
virtual memory exhausted: Cannot allocate memory
mia/2d/maskedcost/CMakeFiles/2dimage-maskedcost-ncc-common.dir/build.make:65: 
recipe for target 
'mia/2d/maskedcost/CMakeFiles/2dimage-maskedcost-ncc-common.dir/ncc.cc.o' failed
...


On mips/mipsel only 2 GB address space are available for userspace.

The following change addresses this by reducing the amount of
debug info generated to what is required for backtraces:

--- debian/rules.old2017-06-22 21:09:04.0 +
+++ debian/rules2017-06-22 21:39:05.0 +
@@ -1,10 +1,18 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed -fvisibility=hidden
 
+# reduce debug info to fix FTBFS on archs with few address space
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+  export DEB_CFLAGS_MAINT_APPEND = -g1
+  export DEB_CXXFLAGS_MAINT_APPEND = -g1
+endif
+
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1