Processed: no patch...

[Debian Bug Tracking System]

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

> tags 919831 -patch
Bug #919831 [src:libcds-moc-java] libcds-moc-java: FTBFS (The code being 
documented uses packages in the unnamed module)
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#920793: libxml-security-java FTBFS: error: package javax.xml.bind does not exist

[Adrian Bunk]

Source: libxml-security-java
Version: 2.0.10-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libxml-security-java.html

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default) on project 
xmlsec: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/1st/libxml-security-java-2.0.10/src/main/java/org/apache/xml/security/stax/ext/XMLSecurityConstants.java:24:
 error: package javax.xml.bind does not exist
[ERROR] import javax.xml.bind.JAXBContext;
[ERROR]  ^
[ERROR] 
/build/1st/libxml-security-java-2.0.10/src/main/java/org/apache/xml/security/stax/ext/XMLSecurityConstants.java:25:
 error: package javax.xml.bind does not exist
[ERROR] import javax.xml.bind.JAXBException;
[ERROR]  ^
[ERROR] 
/build/1st/libxml-security-java-2.0.10/src/main/java/org/apache/xml/security/stax/ext/XMLSecurityConstants.java:26:
 error: package javax.xml.bind does not exist
[ERROR] import javax.xml.bind.Unmarshaller;
[ERROR]  ^
...

Bug#920795: weupnp FTBFS with recent OpenJDK

[Adrian Bunk]

Source: weupnp
Version: 0.1.4-1
Severity: serious
Tags: ftbfs buster sid

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

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default-cli) on 
project weupnp: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules 
but the packages defined in https://docs.oracle.com/javase/1.5.0/docs/api/ are 
in the unnamed module.


For background see
https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=919798#125

Bug#920794: localizer FTBFS with recent OpenJDK

[Adrian Bunk]

Source: localizer
Version: 1.13-3
Severity: serious
Tags: ftbfs

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

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default-cli) on 
project localizer: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules 
but the packages defined in https://docs.oracle.com/javase/1.5.0/docs/api/ are 
in the unnamed module.


For background see
https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=919798#125

Processed: Re: Bug#920609: lynkeos.app: Does not start; assertion failure

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #920609 [lynkeos.app] lynkeos.app: Does not start; assertion failure
Added tag(s) pending.

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

Bug#920609: lynkeos.app: Does not start; assertion failure

[Yavor Doganov]

Control: tags -1 + pending

On Sun, 27 Jan 2019 14:11:06 +0200,
Yavor Doganov wrote:
> Package: lynkeos.app
> Version: 2.10+dfsg1-3+b2
> Severity: grave
> 
> $ Lynkeos
> Lynkeos: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && 
> old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse 
> (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.

I fixed this but there's a new upstream release which ideally I'd like
to get in buster.  If I'm unable to complete the porting work in time
for the soft freeze I'll upload 2.10+dfsg1-4 fixing this bug.

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Andrej Shadura]

(Sending this again since the first submission’s got delayed by a filter.)

On Wed, 16 Jan 2019 at 21:51, Different55  wrote:
>
> Alright, not entirely sure if I did this right but I followed Debian's 
> Building Tutorial to download and build wpa_supplicant with the changes you 
> linked. One exception, I use wpa_supplicant through NetworkManager and could 
> not work out where I needed to create a wpa_supplicant.conf, so I changed the 
> one line in config.c to:
>
> { INT(no_oper_classes_ie), 1 },
>
> which I'm hoping makes the default "on" instead of "off." Sadly doesn't 
> appear to have made a difference, although it didn't make anything worse 
> either.
>
> Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my 
> desktop this morning and had the same problems with a Qualcomm Atheros AR9462 
> Wireless Adapter.

Forwarding Different55’s message from the Debian bug here:

Sure thing! Sadly doesn't seem to make a difference. I've included
another log, this time starting from the time wpa_supplicant was
brought back up to a little bit after I got the popup that the
connection had failed.

Thanks,
Diff


-- 
Cheers,
  Andrej


NetworkManager 2.log
Description: Binary data

Bug#897945: #897945 still present/breaks with Java 8

[Per Lundberg]

FWIW, version 1.4.2-1 works correctly with openjdk-11-jdk version 
11.0.2+7-1, but it _does not_ work correct any more with Java 8 
(openjdk-8-jdk version 8u191-b12-2)

This worked correctly with 1.3.9-1 after downgrading the libnb-*-java 
packages as suggested by Ben - visualvm worked fine on Java 8 with this 
combination of packages.

So, we should either:

- Reopen the bug and fix the problem (likely by compiling visualvm with 
openjdk-8, which should make it work on newer JDK versions also)

- Accept the breakage and indicate this somehow, preferably in the 
package metadata. (I don't know if we can use dpkg dependencies in this 
case? It's perfectly legal to have both OpenJDK 11 and 8 _installed_ on 
a machine; it's just that the latter is unusable with visualvm from now on.)

Because the resolution here is not perfectly clear, I will refrain from 
just reopening the bug until it has been discussed a bit more.

Best regards,
--
Per

Bug#920749: [Pkg-javascript-devel] Bug#920749: popper.js: contains generated code uncertain if fully included as source

[Xavier]

Le 29/01/2019 à 07:41, Xavier a écrit :
> Le 28/01/2019 à 18:45, Jonas Smedegaard a écrit :
>> Source: popper.js
>> Version: 1.14.6+ds-1
>> Severity: serious
>> Justification: Policy 2.1
>>
>> Source package contains several files (seemingly all of them) below
>>  which does not exist in upstream version tracking and therefore
>> are not in the form preferred upstream, and more importantly may include
>> other code than the actual source below .
>>
>>  - Jonas
> 
> Upstream author does provide dist/* files in release commits (example:
> https://github.com/FezVrasta/popper.js/commit/b1144cdbcb5b5ab20d281a6083ecdce475a54af1)
> and remove them from master at next commit. This generated files are
> readable javascript files, unminified and well commented (a sort of
> webpack of packages/* files).
> 
> To reproduce build, many dependencies are needed. So the choices are:
>  - doing nothing, twitter-bootstrap4 will be removed from buster with
>all its reverse dependencies
>  - package many new modules (I've no time to do this)
>  - decrease this severity issue
> 
> NB: upstream build can be reproduce only using yarnpkg, failed with npm:
>   $ yarnpkg install
>   $ yarnpkg build
> 
> Cheers,
> Xavier

kapouer found a way to fix this, many thanks !

WIP

Bug#897945: #897945 still present/breaks with Java 8

[Emmanuel Bourg]

Le 29/01/2019 à 10:40, Per Lundberg a écrit :
> FWIW, version 1.4.2-1 works correctly with openjdk-11-jdk version 
> 11.0.2+7-1, but it _does not_ work correct any more with Java 8 
> (openjdk-8-jdk version 8u191-b12-2)

Thank you for the feedback Per. What issue did you see when using
visualvm with Java 8? You tried running visualvm with Java 8 or you
tried attaching visualvm to a Java 8 VM?

Emmanuel Bourg

Processed: Bug #920749 in popper.js marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #920749 [src:popper.js] popper.js: contains generated code uncertain if 
fully included as source
Added tag(s) pending.

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

Bug#920749: Bug #920749 in popper.js marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #920749 in popper.js reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/popper.js/commit/4f9dfb64a27f33ded2de4188f15327c367f5777e


Replace lerna build by rollup. Thanks to kapouer!

Closes: #920749


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/920749

Bug#920799: src:olive - Hijacked name of unrelated package

[Bastian Blank]

Package: src:olive
Version: 20181223-1
Severity: serious

You hijacked the name of an unrelated package:

| Description: console RSS reader
|  Olive is a console mode RSS newsreader. It provides a chronological
|  rather than site-oriented view of news stories and tries to stay out
|  of your way as much as possible.

Bastian

-- 
Bastian Blank
Berater
Telefon: +49 2166 9901-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz

Processed: Bug #919658 in camomile marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919658 [src:camomile] ocaml-gettext ftbfs (comomile module not found)
Added tag(s) pending.

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

Processed: Bug #918562 in camomile marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918562 [src:camomile] camomile FTBFS on ocaml bytecode architectures: 
Fatal error: exception Stack overflow
Ignoring request to alter tags of bug #918562 to the same tags previously set

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

Bug#918563: Bug #918563 in camomile marked as pending

[Kyle Robbertze]

Control: tag -1 pending

Hello,

Bug #918563 in camomile reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ocaml-team/camomile/commit/f9857552bb9a0ba3de27a8cd13bc998f62f1a53a


Drop zh__PINYIN locale (Closes: #918562, #918563)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918563

Bug#919658: Bug #919658 in camomile marked as pending

[Kyle Robbertze]

Control: tag -1 pending

Hello,

Bug #919658 in camomile reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ocaml-team/camomile/commit/aebe7bfe4596dbbda28e9c12485ff5a8e5154f50


Install files in the correct location (Closes: #919658)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919658

Processed: Bug #918563 in camomile marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918563 [src:camomile] camomile FTBFS on ppc64{,el}: camomilelocaledef got 
signal SEGV
Bug #919472 [src:camomile] camomile ftbfs on ppc64el
Ignoring request to alter tags of bug #918563 to the same tags previously set
Ignoring request to alter tags of bug #919472 to the same tags previously set

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

Bug#918562: Bug #918562 in camomile marked as pending

[Kyle Robbertze]

Control: tag -1 pending

Hello,

Bug #918562 in camomile reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ocaml-team/camomile/commit/f9857552bb9a0ba3de27a8cd13bc998f62f1a53a


Drop zh__PINYIN locale (Closes: #918562, #918563)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918562

Bug#897945: #897945 still present/breaks with Java 8

[Markus Koschany]

Am 29.01.19 um 10:58 schrieb Emmanuel Bourg:
> Le 29/01/2019 à 10:40, Per Lundberg a écrit :
>> FWIW, version 1.4.2-1 works correctly with openjdk-11-jdk version 
>> 11.0.2+7-1, but it _does not_ work correct any more with Java 8 
>> (openjdk-8-jdk version 8u191-b12-2)
> 
> Thank you for the feedback Per. What issue did you see when using
> visualvm with Java 8? You tried running visualvm with Java 8 or you
> tried attaching visualvm to a Java 8 VM?
> 
> Emmanuel Bourg


I am sorry but OpenJDK 8 will not be supported at runtime in Buster. If
it works with OpenJDK 11, which it does, then we should spend the
remaining time before the release on more urgent issues.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#897945: #897945 still present/breaks with Java 8

[Markus Koschany]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am 29.01.19 um 12:06 schrieb Markus Koschany:

> I am sorry but OpenJDK 8 will not be supported at runtime in
> Buster. If it works with OpenJDK 11, which it does, then we should
> spend the remaining time before the release on more urgent issues.

I should have added that we compile for Java 9 bytecode with the
- -Dpermit.jdk9.builds=true switch in visualvm and in
libnb-platform18-java. No surprises here that it won't work with
OpenJDK 8. What we can and probably should do is to force OpenJDK 11
by using a stricter dependency on default-jdk (>= 2:1.11) | java11-sdk
and by also updating the 03-launcher.patch and remove the alternative
search paths for OpenJDK 7 and OpenJDK 8. The result is that visualvm
simply will not start anymore and quit with "No jdkhome found" if
someone uses an unsupported JDK.
-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlxQOa9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQACgkQ2a0UuVE7
UeRmiw/+Nxkz+4R+Uk6qgYyFtkTnM6zLvOOrb8QD+jrKpsomm6qstnAJuj0sPogG
Rz0q/NUjYT4YYzR7pROjXI6287E3G0fmYyVGep7lQWyEPCWMsKAHpN+Ya7S81mpD
PI6c2CQ3MvkdG38v5E+Jt0ILzFGmzE7eNtpnXBPVDrMi7+hLsxULQe+NR5GOdL15
c2kADaexqvxwgoRD75OeWtFapboAaMzm5Lj16q6wC3mygU8d0uBHuAbhMfW8AFIH
nHOLoGYj7Dxkhb7dILMCuTqL208oGGhQT/d5sX8xXRLV/WYH7bHCvTlABPMAgjlB
IqAXGfSZ70GY2hp1gN3iElAyS8vRjXrlAyTzar4ulx38WqD79qeKtan90+rcL3eA
mxZjtrHQtvjDW6JaPuEDkfRbT7gUOa1AldzxjprK/p7DwTpqLWAIGax+xnvWgWC0
V6w5/iCYprDzVSJQhQXDt5VyMOGgDkNyZ/0J2yJAADQ/4uFnsuSnrAw4YO/rlm4k
+fYXoBEdGqYHGe3l0BmTdvSOX279n6YzZCQUWX6IbuMeW0kNLtYD8CI355gS/2cG
CBNVE50YQZ95+h84tlmaL5Ce+xmEpxy14PNyKoFVfQwQA10ZR2eTvU8SODUtzkRs
yed/BEwbFZShUH42d98I/lJj86gmNE2hA2vwjuQQHZEqzKktxDU=
=p+tq
-END PGP SIGNATURE-

Bug#918149: terminator in buster

[Markus Frosch]

Hey Julian,
thanks for responding.

Since testing the Python 3 patch by Emilio, I would love to push this to
buster as well.

I requested to join PAPT, and am waiting for an response on that.

If you all agree, I will take care of that and join the maintainer team.

Regards
Markus

P.S. If one of you can add me to PAPT, I would appreciate some help :)

Am 28.01.19 um 21:55 schrieb Julián Moreno Patiño:
> Hello Markus,
> 
> This package is team maintained, you are welcome at board.
> 
> At the moment I am a little bit busy. Just go ahead with your NMU to
> fix the RC bug.
> 
> Kind regards,
> 
> El dom., 27 ene. 2019 a las 7:00, Markus Frosch
> () escribió:
>>
>> Hey all,
>> is anyone taking care about the RC bug [2] in terminator[1] for upcoming
>> buster?
>>
>> I plan to do an NMU over the next days, if no one says stop.
>>
>> I've seen that Emilio did some Python 3 work in experimental, is that
>> ready for unstable? What's the upstream work on this?
>>
>> Maybe I'm going to adopt the package as well, since I'm using
>> terminator. Anyone opposes that?
>>
>> Cheers
>> Markus Frosch
>>
>> [1] https://tracker.debian.org/pkg/terminator
>> [2] https://bugs.debian.org/918149
>>
>> --
>> mar...@lazyfrosch.de / lazyfro...@debian.org
>> https://lazyfrosch.de
>>
> 
> 

-- 
mar...@lazyfrosch.de / lazyfro...@debian.org
https://lazyfrosch.de



signature.asc
Description: OpenPGP digital signature

Bug#918149: terminator in buster

[Emilio Pozuelo Monfort]

On 29/01/2019 12:55, Markus Frosch wrote:
> Hey Julian,
> thanks for responding.
> 
> Since testing the Python 3 patch by Emilio, I would love to push this to
> buster as well.
> 
> I requested to join PAPT, and am waiting for an response on that.
> 
> If you all agree, I will take care of that and join the maintainer team.

That would be great! I can also push the fix for the missing dependency, but
I'll now gladly wait for your contributions :-)

I was hesitant about pushing the Python 3 changes to buster due to the lack of
feedback by upstream. But if it's also working well for you, we could see about
uploading that.

Cheers,
Emilio

Bug#919976: marked as done (ibus-keyman: fails to install: ibus-keyman.postinst: ps: not found)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 06:32:12 -0600
with message-id 

and subject line Re: ibus-keyman: fails to install: ibus-keyman.postinst: ps: 
not found
has caused the Debian Bug report #919976,
regarding ibus-keyman: fails to install: ibus-keyman.postinst: ps: not found
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.)


-- 
919976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibus-keyman
Version: 11.0.103-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ibus-keyman.
  (Reading database ... 
(Reading database ... 19508 files and directories currently installed.)
  Preparing to unpack .../ibus-keyman_11.0.103-1_i386.deb ...
  Unpacking ibus-keyman (11.0.103-1) ...
  Setting up ibus-keyman (11.0.103-1) ...
  /var/lib/dpkg/info/ibus-keyman.postinst: 1: 
/var/lib/dpkg/info/ibus-keyman.postinst: ps: not found
  dpkg: error processing package ibus-keyman (--configure):
   installed ibus-keyman package post-installation script subprocess returned 
error exit status 127
  Errors were encountered while processing:
   ibus-keyman


cheers,

Andreas


ibus-keyman_11.0.103-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 11.0.103-4

The postinst/rm scripts now check that sudo and ps are installed
otherwise they won't attempt to restart ibus

Confirmed that piuparts now completes successfully.

Thanks,
Daniel--- End Message ---

Bug#897945: #897945 still present/breaks with Java 8

[Per Lundberg]

On 1/29/19 1:32 PM, Markus Koschany wrote:

Hi Markus and Emmanuel,

Emmanuel - the problem is that VisualVM will display its splash screen, 
then die with an error in the log about java.lang.NoSuchMethodError: 
java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;

>> I am sorry but OpenJDK 8 will not be supported at runtime in
>> Buster. If it works with OpenJDK 11, which it does, then we should
>> spend the remaining time before the release on more urgent issues.
> 
> I should have added that we compile for Java 9 bytecode with the
> - -Dpermit.jdk9.builds=true switch in visualvm and in
> libnb-platform18-java. No surprises here that it won't work with
> OpenJDK 8.

I am fine with this; we should just try to make the user experience a 
bit smoother.

> What we can and probably should do is to force OpenJDK 11
> by using a stricter dependency on default-jdk (>= 2:1.11) | java11-sdk
> and by also updating the 03-launcher.patch and remove the alternative
> search paths for OpenJDK 7 and OpenJDK 8. The result is that visualvm
> simply will not start anymore and quit with "No jdkhome found" if
> someone uses an unsupported JDK.

That sounds like a reasonable path: the effort should not be huge, and 
the user experience will be improved. The problem right now (with Java 
8) is that it just "dies" as described above, no error message printed. 
You have to more or less _know_ that you should go digging in 
~/.visualvm/1.4/var/log/messages.log for it. This is not so great.

But, the approach you suggest is fine. Markus, will you reopen this bug 
or should we file a new one about it, what do you prefer?
--
Best regards,
Per

Bug#919002: marked as done (CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 13:02:18 +
with message-id 
and subject line Bug#918841: fixed in systemd 232-25+deb9u7
has caused the Debian Bug report #918841,
regarding CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and 
CVE-2018-16866
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.)


-- 
918841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 240-3
Severity: normal

Dear all,
Saw this on zdnet today -

https://www.zdnet.com/article/new-linux-systemd-security-holes-uncovered/

I did the cursory thing of seeing maybe if the CVE's had been
mentioned in the changelog -

/usr/share/doc/systemd$ zless changelog.Debian.gz | grep CVE
(CVE-2018-15686, Closes: #912005)
(CVE-2018-15688, LP: #1795921, Closes: #912008)
(CVE-2018-15687, LP: #1796692, Closes: #912007)
  non-terminal path components. (CVE-2018-6954, Closes: #890779)
(CVE-2017-15908, Closes: #880026, LP: #1725351)
CVE-2017-9445 (Closes: #866147, LP: #1695546)
Fixes: CVE-2017-9217 (Closes: #863277)
by avoiding a race condition in scraping /proc (CVE-2013-4327).
  Fixes CVE-2012-1174, closes: #664364
- Fixes local DoS (CVE-2012-1101).  Closes: #662029

I did also look at systemd --version if GCC's -fstack-clash-protection
is mentioned therein in the version command but couldn't find it.

It is very much possible that you may be working on it, in any case,
look forward to the fixes.

-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.13.2-3
ii  libaudit11:2.8.4-2
ii  libblkid12.33-0.2
ii  libc62.28-2
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.6-1
ii  libgcrypt20  1.8.4-4
ii  libgnutls30  3.6.5-2
ii  libgpg-error01.33-3
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-3
ii  libkmod2 25-2
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.2-1.3
ii  libmount12.33-0.2
ii  libpam0g 1.1.8-3.8
ii  libseccomp2  2.3.3-3
ii  libselinux1  2.8-1+b1
ii  libsystemd0  240-3
ii  mount2.33-0.2
ii  util-linux   2.33-0.2

Versions of packages systemd recommends:
ii  dbus1.12.12-1
ii  libpam-systemd  240-3

Versions of packages systemd suggests:
ii  policykit-10.105-23
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.132
ii  udev 240-2

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-25+deb9u7

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated systemd 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: Sat, 12 Jan 2019 09:38:38 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-25+deb9u7
Distribution: stretch-security
Ur

Bug#918848: marked as done (systemd: CVE-2018-16865)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 13:02:18 +
with message-id 
and subject line Bug#918848: fixed in systemd 232-25+deb9u7
has caused the Debian Bug report #918848,
regarding systemd: CVE-2018-16865
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.)


-- 
918848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 43-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 232-25+deb9u6
Control: found -1 240-2

Hi,

The following vulnerability was published for systemd, opening
tracking bug.

CVE-2018-16865[0]:
memory corruption

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-2018-16865
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16865
[1] https://www.openwall.com/lists/oss-security/2019/01/09/3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-25+deb9u7

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated systemd 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: Sat, 12 Jan 2019 09:38:38 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-25+deb9u7
Distribution: stretch-security
Urgency: high
Maintainer: Debian systemd Maintainers 

Changed-By: Salvatore Bonaccorso 
Closes: 918841 918848
Description: 
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (232-25+deb9u7) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * journald: do not store the iovec entry for process commandline on stack
 (CVE-2018-16864) (Closes: #918841)
   * journald: set a limit on the number of fields (1k) (CVE-2018-16865)
 (Closes: #918848)
   * journal-remote: set a limit on the number of fields in a message
 (CVE-2018-16865) (Closes: #918848)
   * journal: fix syslog_parse_identifier() (CVE-2018-16866)
   * journal: do not remove multiple spaces after identifier in syslog message
 (CVE-2018-16866)
Package-Type: udeb
Checksums-Sha1: 
 b4ca041a73cb8775c90bbcc92c080cd7ac58dfe4 4952 systemd_232-25+deb9u7.dsc
 74178b96d631058236cf79f5b0cc3953382f12b5 4529048 systemd_232.orig.tar.gz
 4b7fbdd4005aa0340dca1cc37603cbd520343e31 214680 
systemd_232-25+deb9u7.debian.tar.xz
Checksums-Sha256: 
 1dea5088456636c50c3135ae5cd00f92ee8559360c907a22e1ed05a3e0016646 4952 
systemd_232-25+deb9u7.dsc
 1172c7c7d5d72fbded53186e7599d5272231f04cc8b72f9a0fb2c5c20dfc4880 4529048 
systemd_232.orig.tar.gz
 653cf8bb0b33b01c08484a3a3c8de4de1bb875b56f869ef389b17760442a8e7f 214680 
systemd_232-25+deb

Bug#918841: marked as done (systemd: CVE-2018-16864)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 13:02:18 +
with message-id 
and subject line Bug#918841: fixed in systemd 232-25+deb9u7
has caused the Debian Bug report #918841,
regarding systemd: CVE-2018-16864
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.)


-- 
918841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 204-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 232-25+deb9u6
Control: found -1 240-2

Hi,

The following vulnerability was published for systemd.

CVE-2018-16864[0]:
memory corruption

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-2018-16864
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16864
[1] https://www.openwall.com/lists/oss-security/2019/01/09/3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-25+deb9u7

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated systemd 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: Sat, 12 Jan 2019 09:38:38 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-25+deb9u7
Distribution: stretch-security
Urgency: high
Maintainer: Debian systemd Maintainers 

Changed-By: Salvatore Bonaccorso 
Closes: 918841 918848
Description: 
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (232-25+deb9u7) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * journald: do not store the iovec entry for process commandline on stack
 (CVE-2018-16864) (Closes: #918841)
   * journald: set a limit on the number of fields (1k) (CVE-2018-16865)
 (Closes: #918848)
   * journal-remote: set a limit on the number of fields in a message
 (CVE-2018-16865) (Closes: #918848)
   * journal: fix syslog_parse_identifier() (CVE-2018-16866)
   * journal: do not remove multiple spaces after identifier in syslog message
 (CVE-2018-16866)
Package-Type: udeb
Checksums-Sha1: 
 b4ca041a73cb8775c90bbcc92c080cd7ac58dfe4 4952 systemd_232-25+deb9u7.dsc
 74178b96d631058236cf79f5b0cc3953382f12b5 4529048 systemd_232.orig.tar.gz
 4b7fbdd4005aa0340dca1cc37603cbd520343e31 214680 
systemd_232-25+deb9u7.debian.tar.xz
Checksums-Sha256: 
 1dea5088456636c50c3135ae5cd00f92ee8559360c907a22e1ed05a3e0016646 4952 
systemd_232-25+deb9u7.dsc
 1172c7c7d5d72fbded53186e7599d5272231f04cc8b72f9a0fb2c5c20dfc4880 4529048 
systemd_232.orig.tar.gz
 653cf8bb0b33b01c08484a3a3c8de4de1bb875b56f869ef389b17760442a8e7f 214680 
systemd_232-25+deb9u7.debian.tar.xz
Fil

Bug#918230: marked as done (python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 13:02:16 +
with message-id 
and subject line Bug#918230: fixed in python-django 1:1.10.7-2+deb9u4
has caused the Debian Bug report #918230,
regarding python-django: CVE-2019-3498: Content spoofing possibility in the 
default 404 page
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.)


-- 
918230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.11.17-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Control: found -1 2:2.1.4-2

Hi,

The following vulnerability was published for python-django.

CVE-2019-3498[0]:
Content spoofing possibility in the default 404 page

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-2019-3498
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3498
[1] https://www.djangoproject.com/weblog/2019/jan/04/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 1:1.10.7-2+deb9u4

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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: Sun, 06 Jan 2019 09:35:11 +0100
Source: python-django
Binary: python-django python3-django python-django-common python-django-doc
Architecture: source all
Version: 1:1.10.7-2+deb9u4
Distribution: stretch-security
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 918230
Changes:
 python-django (1:1.10.7-2+deb9u4) stretch-security; urgency=high
 .
   * CVE-2019-3498: Prevent a content-spoofing vulnerability in the default
 404 page. (Closes: #918230)
Checksums-Sha1:
 5efaeaca83b3a50a1a7ec625754de098699167e1 2804 python-django_1.10.7-2+deb9u4.dsc
 5edd13a642460c33cdaf8e8166eccf6b2a2555df 7737654 
python-django_1.10.7.orig.tar.gz
 e01359592fda6efd3190c089c116656e3f757b07 37644 
python-django_1.10.7-2+deb9u4.debian.tar.xz
 fe1b2e76cafe244b60191437c3b0f9f0f0f93e38 1514142 
python-django-common_1.10.7-2+deb9u4_all.deb
 db37122f7bd1f91089d7aa2a873f39e870a98660 2535672 
python-django-doc_1.10.7-2+deb9u4_all.deb
 bffd8fe13bb80f0f531bec564ef0caf864a84334 903582 
python-django_1.10.7-2+deb9u4_all.deb
 95eaf30ff4a2879349d0dc0105587a6f0ac29a96 9306 
python-django_1.10.7-2+deb9u4_amd64.buildinfo
 ebd316e1b60275c3718ee034b2779070d5f9d5f0 885312 
python3-django_1.10.7-2+deb9u4_all.deb
Checksums-Sha256:
 5580bf9ca6d79a6adde05a8b5d302ef92ca8cc5d58f32234de5fa53d2a0be73d 2804 
python-django_1.10.7-2+deb9u4.dsc
 593d779dbc2350a245c4f76d26bdcad58a39895e87304fe6d725bbdf84b5b0b8 7737654 
python-django_1.10.7.orig.tar.gz
 88e3bf0c7f30c6fcbee6269b107cfa23e23f799d747dab2900ec8886e0606fac 37644 
python-django_1.10.7-2+deb9u4.debian.tar.xz
 30867f974673e8476e0be00a385642b789bf556a2aa2a3784f2928f8fc90f73c 1514142 
python-django-common_1.10.7-2+deb9u4_all.deb
 89d8e2891242665c410bfcc9a9d7bbcecb82173cccd831244dc14527deac9041 2535672 
python-django-doc_1.10.7-2+deb9u4_all.deb
 ce7fb9dc817ffb285193f5f9b5eaffb20a5a4bb55f2e0eb5bc0d803604f2720c 903582 
python-django_1.10.7-2+deb9u4_all.deb
 1952f40cdbcf336562d88dd908a672a70aa0dd2728e506dc61544f5df4aac81a 9306 
python-django_1.10.7-2+deb9u4_amd64.buildinfo
 d45a6993b629ee6a098407058b3e52b4a2715ae0abc276af6ddefadb55975c97 885312 
python3-django_1.10.7-2+deb9u4_all.deb
Files:
 d92baefb611435ceb

Bug#920700: marked as done (python3-adios: fails to upgrade from 'testing': update-alternatives: error: alternative python-py37-adios-x86_64-linux-gnu can't be master: it is a slave of python-py36-adi

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 13:07:53 +
with message-id 
and subject line Bug#920700: fixed in adios 1.13.1-16
has caused the Debian Bug report #920700,
regarding python3-adios: fails to upgrade from 'testing': update-alternatives: 
error: alternative python-py37-adios-x86_64-linux-gnu can't be master: it is a 
slave of python-py36-adios-x86_64-linux-gnu
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.)


-- 
920700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-adios
Version: 1.13.1-14
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.

>From the attached log (scroll to the bottom...):

  Setting up python3-adios (1.13.1-14) ...
  update-alternatives: error: alternative python-py37-adios-x86_64-linux-gnu 
can't be master: it is a slave of python-py36-adios-x86_64-linux-gnu
  dpkg: error processing package python3-adios (--configure):
   installed python3-adios package post-installation script subprocess returned 
error exit status 2
  Processing triggers for libc-bin (2.28-5) ...
  Errors were encountered while processing:
   python3-adios


cheers,

Andreas


python3-adios_1.13.1-14.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: adios
Source-Version: 1.13.1-16

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated adios 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, 29 Jan 2019 09:23:59 +
Source: adios
Binary: libadios-dev libadios-openmpi-dev libadios-mpich-dev libadios-examples 
libadios-bin python-adios python3-adios
Architecture: source amd64 all
Version: 1.13.1-16
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libadios-bin - ADIOS Adaptable IO system for simulations - binaries
 libadios-dev - ADIOS Adaptable IO system for simulations
 libadios-examples - Examples for the ADIOS Adaptable IO system
 libadios-mpich-dev - ADIOS Adaptable IO system (MPICH development files)
 libadios-openmpi-dev - ADIOS Adaptable IO system (OpenMPI development files)
 python-adios - Python interface to the ADIOS IO system
 python3-adios - Python3 interface to the ADIOS IO system
Closes: 920700
Changes:
 adios (1.13.1-16) unstable; urgency=medium
 .
   * Check full path of link for /etc/alternatives in python3-adios.postinst
 and delete obsolete link if present. Closes: #920700
Checksums-Sha1:
 33651e111073b8a2487fe8932ec6dbd4cdcd3e07 3111 adios_1.13.1-16.dsc
 239561954fc56232a05da37b110c8205cec53612 25724 adios_1.13.1-16.debian.tar.xz
 df76da63c18832f695a4ff9656e8fe8e68678ddf 12790 adios_1.13.1-16_amd64.buildinfo
 11bc0c158fd60024fdf65815cb1182442f341106 7433936 
libadios-bin-dbgsym_1.13.1-16_amd64.deb
 c02b41b939eb9fb1b6a2e3f8f59fa51ce1860e3c 566876 
libadios-bin_1.13.1-16_amd64.deb
 62902bc16432c108772196eeed1c1a29e2a8364a 403940 
libadios-dev_1.13.1-16_amd64.deb
 fd13cb0ead5a914a876cd290a65af57f92a1337a 349000 
libadios-examples_1.13.1-16_all.deb
 6ddc565e4af431bb94f5fe7e83766f8357320293 354856 
libadios-mpich-dev_1.13.1-16_amd64.deb
 955bb990a4bc67cbfe8a0e3944e2838289392200 356812 
libadios-openmpi-dev_1.13.1-16_amd64.deb
 709b1255a5e05395eabb0ea95993dda9b6982062 5112640 
python-adios-dbgsym_1.13.1-16_amd64.deb
 d86580cfc800882e4ad490135b2f608c59fca450 837428 
python-adios_1.13.1-16_amd64.deb
 c79c89b6d54673a232a9121836f8d5dc80a1997e 5571956 
python3-adios-dbgsym_1.13.1-16_amd64.deb
 7849ede07ef105969fc99942f244ace04d7447d4 858084 
python3-adios_1.13.1-16_amd64.deb
Checksums-Sha256:
 277f570b27ee3b9b90c9ccf36ecf2e405625fbe0e5b38c0d0f6f4396be95a9c4 3111 
adios_1.13.1-16.dsc
 e25f7163e8749931884f7fe46b2e01fc4611639a5f06d8def2657d67a79a9afd 25724 
adios_1.13.1-16.debian.t

Bug#920537: marked as done (python3-q-text-as-data: SyntaxError: invalid syntax (ships Python 2 script as Python 3 script))

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 13:15:16 +
with message-id 
and subject line Bug#920537: fixed in q-text-as-data 
1.7.4+2018.12.21+git+28f776ed46-1
has caused the Debian Bug report #920537,
regarding python3-q-text-as-data: SyntaxError: invalid syntax (ships Python 2 
script as Python 3 script)
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.)


-- 
920537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-q-text-as-data
Version: 1.4.0-2
Severity: grave

q, if installed via its python3-q-text-as-data package, bails out with a
syntax error:

→ python3-q-text-as-data
  File "/usr/bin/python3-q-text-as-data", line 201
print sql, " params: " + str(params)
^
SyntaxError: invalid syntax
→ q
  File "/usr/bin/q", line 201
print sql, " params: " + str(params)
^
SyntaxError: invalid syntax

The amount or type of parameters doesn't seem to be relevant. Taking an
example from the upstream website yields the same error:

→ ps -ef | q -H "SELECT UID,COUNT(*) cnt FROM - GROUP BY UID ORDER BY cnt DESC 
LIMIT 3"
  File "/usr/bin/q", line 201
print sql, " params: " + str(params)
^
SyntaxError: invalid syntax

On a first glance this looks like Python 2.x syntax in a Python 3.x
package.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-q-text-as-data depends on:
ii  python3  3.7.2-1
ii  sqlite3  3.26.0+fossilbc891ac6b-2

python3-q-text-as-data recommends no packages.

python3-q-text-as-data suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: q-text-as-data
Source-Version: 1.7.4+2018.12.21+git+28f776ed46-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated q-text-as-data 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: Sun, 27 Jan 2019 00:10:07 +0100
Source: q-text-as-data
Binary: python-q-text-as-data python3-q-text-as-data
Architecture: source all
Version: 1.7.4+2018.12.21+git+28f776ed46-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-q-text-as-data - performs SQL-like statements on tabular text data - 
Python 2.x
 python3-q-text-as-data - performs SQL-like statements on tabular text data - 
Python 3.x
Closes: 888688 920537
Changes:
 q-text-as-data (1.7.4+2018.12.21+git+28f776ed46-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * Running wrap-and-sort -bast
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles
   * d/control: Use team+openst...@tracker.debian.org as maintainer
 .
   [ Thomas Goirand ]
   * New upstream release (Closes: #888688):
 - Fixes Python 3 compat (Closes: #920537).
 - Add python{3,}-six as (build-)depends.
Checksums-Sha1:
 180960caca3b9c163ff8a6a1dc242e7eb48b0476 2373 
q-text-as-data_1.7.4+2018.12.21+git+28f776ed46-1.dsc
 e366d16408aac9b9e3b15a4bd97779bb83aecce2 60604 
q-text-as-data_1.7.4+2018.12.21+git+28f776ed46.orig.tar.xz
 20a9b9d7ea4278a15a6db71bc948a2421266c9a1 2964 
q-text-as-data_1.7.4+2018.12.21+git+28f776ed46-1.debian.tar.xz
 661aa2d2abcd602a9273d59d6d1aca65ec050aba 26320 
python-q-text-as-data_1.7.4+2018.12.21+git+28f776ed46-1_all.deb
 bf470cb30e175639103a00658730761657c090e2 20456 
python3-q-text-as-data_1.7.4+2018.12.21+git+28f776ed46-1_all.deb
 c2c6ee561c31f79bd3aa9daccb

Bug#920749: marked as done (popper.js: contains generated code uncertain if fully included as source)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 13:14:35 +
with message-id 
and subject line Bug#920749: fixed in popper.js 1.14.6+ds2-1
has caused the Debian Bug report #920749,
regarding popper.js: contains generated code uncertain if fully included as 
source
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.)


-- 
920749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: popper.js
Version: 1.14.6+ds-1
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Source package contains several files (seemingly all of them) below
 which does not excist in upstream version tracking and therefore
are not in the form preferred upstream, and more importantly may include
other code than the actual source below .

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxPP8IACgkQLHwxRsGg
ASFK1hAAriXMDCIrGsMdyAicI0pRWZ5nWGeeQa0Sn5WLev+PFE9GcuykxDVQtdv5
0tVfziLSg9l66YNjc0nzxsPMChX0emu2LmJXXJltpX816NkrmwZUBg0xuJleZ3zl
2DTTBmmE3rvS9WJ+qjtcTM8r/YtosWwXXqooTe+MVaKaD9mQWC63iak8NYUc27pW
rduq11FOzalZHW4jOcLorYA1PrfaUr67JGNWNPZCkcKm9KPAN0Z9sjhofmkEqKXP
A+06IwxVgfK9PiijScSSWKzQSVfCi1RF5nMJciDWMJmUePDu7+9vSyxaJJcsQcBt
aWau9Hy/Akb0J/SRdMV6fS8mhTo2xF5SDEDjxxp7X3AZ8vn9EdnQFvdFrbsIoj5d
4TinMiZfgexMy8Asve2tGRUOszDsyVEMziNopI40yslSIq3RYXrlSAu/Mh0mt/l4
fmdZXcqlsnS8XtT5iNHBxjQ+e/wliIxATz7qztBhjoV1uHkUmO8YvzJyFJu38aVv
AEu2LXHf2vpGHcwUKaqXnen+PDeCOGg+j5OsAI6g/NfSlaxTid6ZUojZUK+mVCw9
2v1rQyR3BHGatNabaE31tXnRSZO5EOFG4nTs5rQDgxQIpWFgwWgwPFSysPBNE8Fh
OwDSFkfX/gfCXebygXRTbQP2MQ+M9WrDxkZ5JJfIybgGhNXu6j8=
=Ndgg
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: popper.js
Source-Version: 1.14.6+ds2-1

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated popper.js 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: Tue, 29 Jan 2019 13:31:49 +0100
Source: popper.js
Binary: libjs-popper.js
Architecture: source
Version: 1.14.6+ds2-1
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 920749
Description: 
 libjs-popper.js - Javascript library to position poppers in web applications
Changes:
 popper.js (1.14.6+ds2-1) unstable; urgency=medium
 .
   * Replace lerna build by rollup. Thanks to kapouer! (Closes: #920749)
   * Exclude dist/ from upstream and repack
   * Add test based on pkg-js-tools
Checksums-Sha1: 
 3471f974c363f8a798717fd4296966e43866f97a 1988 popper.js_1.14.6+ds2-1.dsc
 bc9d2414fcb4ba7790ad3e15c5b4e9054831464d 203012 
popper.js_1.14.6+ds2.orig.tar.xz
 832875dbf993a0376799b2a950c65ce21ab92af6 4248 
popper.js_1.14.6+ds2-1.debian.tar.xz
Checksums-Sha256: 
 3cde43a8cdc9ddeff0239e964d48ed9906823a0d1e70945107e4324db43196af 1988 
popper.js_1.14.6+ds2-1.dsc
 1b801a9167ac0b25571604ae406c1167c28f7acd318209a224a1e9c7b7729544 203012 
popper.js_1.14.6+ds2.orig.tar.xz
 1fcd806525afa6065244126f20d46f04a6d2fa26a4ebed90e998c6f090d6e3d6 4248 
popper.js_1.14.6+ds2-1.debian.tar.xz
Files: 
 090630225e96b91b816e336bc1a45159 1988 javascript optional 
popper.js_1.14.6+ds2-1.dsc
 0ef1d444557563e7d2b0c248ad4f0f10 203012 javascript optional 
popper.js_1.14.6+ds2.orig.tar.xz
 171009d1729c74b2b5f0d33ec5c7bfc4 4248 javascript optional 
popper.js_1.14.6+ds2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxQSHcACgkQ9tdMp8mZ
7ulwKw//eX+Ivau6WeSb/9goHtwixO4iWya875GegLRK5nS+sNKysqLlaRb/6SV5
FVkC2ERDETNQuOgI24NYX8S0qFbVM8fhwYNcNbwTWGXsH/1BSspIDHEyFI1DKpad
q7l/BN+eH7lzODbddP6iEmVVp6ybSkM0NRPlw3rJwBhcWfGp2thSsaKmnxLbVS3V
9zNYIEM07M4QJWWOQE+mo7AbtesnEAN0qUCfiml5+r+ba9zlDO77la+RChLhjgE5
o3zS6gX6+0lPRLIqcxxdQk1suQnHiW3yJvs2/GaPyUwntwtofdj3lDTSS0x8OK8x
YGeM4q8Gji1novR3vDjQUAkxDA4ToIEX+I+UQtNhMW8tA0pH7TOBeMOyOnaHOBrT
pxNJmz6+ocMhuUeBsGIXKxo5eDnWM7/GAfvsK7X2ENreuETvdpmGFgt3iP6lsroR
LlCROvpHeHctQmQAeOFm1s2W5IMs/kiyaKtTOzZ7GYnQksX4iwRHKS/GDq+3kMgq
6Q0ButbDOKIO2CLIKcG5QsU

Bug#897945: #897945 still present/breaks with Java 8

[Per Lundberg]

Hi Markus,

On 1/29/19 1:32 PM, Markus Koschany wrote:
> 
>> I am sorry but OpenJDK 8 will not be supported at runtime in
>> Buster.
Another question: if this is the case, should the openjdk-8-jdk package 
(and friends) be removed altogether in sid? I looked briefly but 
couldn't find any bugs mentioning this.

Bug#897945: #897945 still present/breaks with Java 8

[Markus Koschany]

Am 29.01.19 um 13:54 schrieb Per Lundberg:
[...]
> But, the approach you suggest is fine. Markus, will you reopen this bug 
> or should we file a new one about it, what do you prefer?

I think we don't need a new bug report for that. I will change that
later today.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#897945: #897945 still present/breaks with Java 8

[Emmanuel Bourg]

Le 29/01/2019 à 14:19, Per Lundberg a écrit :

> Another question: if this is the case, should the openjdk-8-jdk package 
> (and friends) be removed altogether in sid?

We can't remove openjdk-8 yet, it's still required to build some
convoluted packages. But Buster will only support OpenJDK 11, this will
be documented in the release notes.

Emmanuel Bourg

Bug#897945: #897945 still present/breaks with Java 8

[Markus Koschany]

Am 29.01.19 um 14:19 schrieb Per Lundberg:
> Hi Markus,
> 
> On 1/29/19 1:32 PM, Markus Koschany wrote:
>>
>>> I am sorry but OpenJDK 8 will not be supported at runtime in
>>> Buster.
> Another question: if this is the case, should the openjdk-8-jdk package 
> (and friends) be removed altogether in sid? I looked briefly but 
> couldn't find any bugs mentioning this.

This is Debian bug:

https://bugs.debian.org/920037

We usually ship only with one JDK per release because of security
support. OpenJDK 8 will be EOL before the end of the Debian 10 release
cycle. We still have a couple of packages that will not compile with
OpenJDK 11 hence we also thought about shipping OpenJDK 8 for building
those packages but declaring it as unsupported at runtime. However, as
this bug report shows, people tend to assume that OpenJDK 8 is supported
as well. So we either end up without OpenJDK 8 in Buster at all and with
less packages, that are only there to build other packages, or we
declare OpenJDK 8 as unsupported at runtime in our release notes which
carries the risk of nobody reading them.



signature.asc
Description: OpenPGP digital signature

Processed: Bug #891670 in pymssql marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #891670 [src:pymssql] pymssql FTBFS with freetds-dev 1.00.82-2
Added tag(s) pending.

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

Bug#891670: Bug #891670 in pymssql marked as pending

[Sophie Brun]

Control: tag -1 pending

Hello,

Bug #891670 in pymssql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/pymssql/commit/57f0c91a2592f3bc9e448f70ac9579f348973930


Update build-depends for latest upstream release

Now build with freetds >= 0.95 (Closes: #891670)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/891670

Bug#750141: marked as done (libqt4-xml: vulnerable to billion laughs attack (CVE-2013-4549))

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 14:45:19 +0100
with message-id <82c43972-8d2e-7200-08c5-e6c41f92a...@debian.org>
and subject line Re: Bug#750141: libqt4-xml: vulnerable to billion laughs attack
has caused the Debian Bug report #750141,
regarding libqt4-xml: vulnerable to billion laughs attack (CVE-2013-4549)
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.)


-- 
750141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt4-xml
Severity: serious
Tags: security
Justification: security

Qt 4.8.6 has a fix for a denial of service attack due to XML entity
expansion ("billion laughs attack"). This fix doesn't seem to be in the
wheezy packages yet.

http://blog.qt.digia.com/blog/2014/04/24/qt-4-8-6-released/

Ubuntu patched their 4.8.4;

https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1259577



Hamish


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

Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 4:4.8.5+git192-g085f851+dfsg-1

On Mon, 9 Jun 2014 07:17:04 +0200 Salvatore Bonaccorso  
wrote:
> Hi,
> 
> On Sun, Jun 01, 2014 at 11:30:15PM -0300, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > tag 750141 moreinfo
> > thanks
> > 
> > On Monday 02 June 2014 11:19:05 Hamish Moffatt wrote:
> > > Package: libqt4-xml
> > > Severity: serious
> > > Tags: security
> > > Justification: security
> > > 
> > > Qt 4.8.6 has a fix for a denial of service attack due to XML entity
> > > expansion ("billion laughs attack"). This fix doesn't seem to be in the
> > > wheezy packages yet.
> > > 
> > > http://blog.qt.digia.com/blog/2014/04/24/qt-4-8-6-released/
> > > 
> > > Ubuntu patched their 4.8.4;
> > > 
> > > https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1259577
> > 
> > Hi Hamish! I patched Qt4 for jessie at that time but IIRC (I might be 
> > mixing 
> > CVEs here) when I asked someone from the security team over IRC (or maybe 
> > by 
> > mail, I don't remember now) they told me it wasn't too important to get an 
> > update in stable.
> 
> Yep, perl mail It was on 2013-12-06, where Moritz had written:
> 
> Hi Lisandro,
> this doesn't warrant a DSA. It can be fixed through a point update, though
> or we can line it up for a future QT DSA.
> 
> Cheers,
> Moritz
> 
> For the BTS, I think this was fixed in 4:4.8.5+git192-g085f851+dfsg-1.

Closing as this is fixed in unstable. Also wheezy is EOL so there's no point in
keeping this bug open anymore.

Emilio--- End Message ---

Bug#917742: ca-cacert: FTBFS: tests failed

[Axel Beckert]

Hi Dmitry,

ca-cacert just fell out of testing because of this issue.

Lucas Nussbaum wrote:
> > make[1]: Entering directory '/<>'
> > #find . -maxdepth 1 -type f -name "*.crt" -exec openssl verify "{}" \;
> > certtool --verify --load-ca-certificate root.crt --infile class3.crt
> > Loaded CAs (1 available)
> > Subject: CN=CAcert Class 3 Root,OU=http://www.CAcert.org,O=CAcert Inc.
> > Issuer: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> > Authority,OU=http://www.cacert.org,O=Root CA
> > Checked against: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> > Authority,OU=http://www.cacert.org,O=Root CA
> > Signature algorithm: RSA-SHA256
> > Output: Verified. The certificate is trusted. 
> > 
> > Chain verification output: Verified. The certificate is trusted. 
> > 
> > certtool --verify --load-ca-certificate root.crt --infile root.crt
> > Loaded CAs (1 available)
> > Subject: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> > Authority,OU=http://www.cacert.org,O=Root CA
> > Issuer: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> > Authority,OU=http://www.cacert.org,O=Root CA
> > Checked against: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> > Authority,OU=http://www.cacert.org,O=Root CA
> > Signature algorithm: RSA-MD5
 ^^^
> > Output: Not verified. The certificate is NOT trusted. 
> > 
> > Chain verification output: Not verified. The certificate is NOT trusted. 

Reason for this test suite failure is likely that certtool stopped to
accept the MD5 hashing algorithm.

The man page says:

   --verify-allow-broken
  Allow broken algorithms, such as MD5 for verification.

  This can be combined with --p7-verify, --verify or
  --verify-chain.

This could be fixed to change

  certtool --verify --load-ca-certificate root.crt --infile root.crt

to

  certtool --verify --verify-allow-broken --load-ca-certificate root.crt 
--infile root.crt

As far as I see understand that seems to be only the self-signature of
root.crt (which AFAICT should be neglectable) while the (AFAICT
relevant) signature on class3.crt uses SHA256 which is ok.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#920749: [Pkg-javascript-devel] Bug#920749: popper.js: contains generated code uncertain if fully included as source

[Jonas Smedegaard]

Quoting Xavier (2019-01-29 07:41:40)
> Le 28/01/2019 à 18:45, Jonas Smedegaard a écrit :
> > Source: popper.js
> > Version: 1.14.6+ds-1
> > Severity: serious
> > Justification: Policy 2.1
> > 
> > Source package contains several files (seemingly all of them) below
> >  which does not exist in upstream version tracking and therefore
> > are not in the form preferred upstream, and more importantly may include
> > other code than the actual source below .
> > 
> >  - Jonas
> 
> Upstream author does provide dist/* files in release commits (example: 
> https://github.com/FezVrasta/popper.js/commit/b1144cdbcb5b5ab20d281a6083ecdce475a54af1)
>  
> and remove them from master at next commit.

Yes, upstream ships pre-generated code.

Sorry that I was sloppy and my initial email could be read as "this bug 
is that upstream did not at all commit those files to git" - what I 
meant to say is "this bug is that upstream seems to not intend for those 
files to be their preferred form for their own source editing".


> This generated files are readable javascript files, unminified and 
> well commented (a sort of webpack of packages/* files).

Yes, pre-generated code is readable (a.k.a. beautified not minified).

Readability of pre-generated code is irrelevant for this bug.  What is 
relevant is that source is provided for everything we distribute.

Simplest way to ensure that is to not include pre-generated code with 
source.

There are other ways too, but looking for loopholes is _more_ complex 
and _easier to do wrong.


> To reproduce build, many dependencies are needed. So the choices are:
>  - doing nothing, twitter-bootstrap4 will be removed from buster with
>all its reverse dependencies
>  - package many new modules (I've no time to do this)
>  - decrease this severity issue

Yes, reproducing upstream build is likely too complex.

There are other options, however:

 - stitch things together in a creative new way
 - roll back to an earlier release with less complex build routines


> NB: upstream build can be reproduce only using yarnpkg, failed with npm:
>   $ yarnpkg install
>   $ yarnpkg build

I fail to see how it is relevant for this bug: We use deb _instead_ of 
either of those packaging systems!

(a _helper_ tool like npm2deb might have been handy and might fail here, 
but that is unrelated to this bug)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#920749: [Pkg-javascript-devel] Bug#920749: popper.js: contains generated code uncertain if fully included as source

[Xavier]

Le 29/01/2019 à 15:23, Jonas Smedegaard a écrit :
> Quoting Xavier (2019-01-29 07:41:40)
>> Le 28/01/2019 à 18:45, Jonas Smedegaard a écrit :
>>> Source: popper.js
>>> Version: 1.14.6+ds-1
>>> Severity: serious
>>> Justification: Policy 2.1
>>>
>>> Source package contains several files (seemingly all of them) below
>>>  which does not exist in upstream version tracking and therefore
>>> are not in the form preferred upstream, and more importantly may include
>>> other code than the actual source below .
>>>
>>>  - Jonas
>>
>> Upstream author does provide dist/* files in release commits (example: 
>> https://github.com/FezVrasta/popper.js/commit/b1144cdbcb5b5ab20d281a6083ecdce475a54af1)
>>  
>> and remove them from master at next commit.
> 
> Yes, upstream ships pre-generated code.
> 
> Sorry that I was sloppy and my initial email could be read as "this bug 
> is that upstream did not at all commit those files to git" - what I 
> meant to say is "this bug is that upstream seems to not intend for those 
> files to be their preferred form for their own source editing".
> 
> 
>> This generated files are readable javascript files, unminified and 
>> well commented (a sort of webpack of packages/* files).
> 
> Yes, pre-generated code is readable (a.k.a. beautified not minified).
> 
> Readability of pre-generated code is irrelevant for this bug.  What is 
> relevant is that source is provided for everything we distribute.
> 
> Simplest way to ensure that is to not include pre-generated code with 
> source.
> 
> There are other ways too, but looking for loopholes is _more_ complex 
> and _easier to do wrong.
> 
> 
>> To reproduce build, many dependencies are needed. So the choices are:
>>  - doing nothing, twitter-bootstrap4 will be removed from buster with
>>all its reverse dependencies
>>  - package many new modules (I've no time to do this)
>>  - decrease this severity issue
> 
> Yes, reproducing upstream build is likely too complex.
> 
> There are other options, however:
> 
>  - stitch things together in a creative new way
>  - roll back to an earlier release with less complex build routines
> 
> 
>> NB: upstream build can be reproduce only using yarnpkg, failed with npm:
>>   $ yarnpkg install
>>   $ yarnpkg build
> 
> I fail to see how it is relevant for this bug: We use deb _instead_ of 
> either of those packaging systems!
> 
> (a _helper_ tool like npm2deb might have been handy and might fail here, 
> but that is unrelated to this bug)

Hello,

kapouer found a way to fix this (built with node-buble). Closed now.
Could you review twitter-bootstrap4 now ?

Cheers,
Xavier

Bug#920811: wfrog: Depends on removed pygooglechart

[Scott Kitterman]

Package: wfrog
Version: 0.8.2+svn973-1
Severity: grave
Justification: renders package unusable

wfrog is currently uninstallable due to the removal of pygooglechart (See
http://bugs.debian.org/920779 for details).

Scott K

Processed: Bug #920209 in galera-3 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #920209 [src:galera-3] galera-3: FTBFS on mipsel
Added tag(s) pending.

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

Bug#920209: Bug #920209 in galera-3 marked as pending

[Otto Kekäläinen]

Control: tag -1 pending

Hello,

Bug #920209 in galera-3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/mariadb-team/galera-3/commit/43d6848d75f50d7f19ac762fe260dda47f4d1862


Hopefully fix FTBFS on mipsel (closes: #920209).

It might be necessary to further raise the multiplier if
this one (2) is insufficient.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/920209

Bug#912110: Test in question excluded in latest upload

[Andreas Tille]

Control: severity -1 important

Hi,

in the last upload (0.7.0-8) that fixes some other issues the test in
question was skipped and thus the packages does not FTBFS any more.
Since the problem itself persists and the test keeps on failing the
bug is not closed but the severity is set to important instead.

Any help would be welcome anyway

  Andreas.


-- 
http://fam-tille.de

Processed: Test in question excluded in latest upload

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #912110 [src:opensurgsim] opensurgsim FTBFS: test failures
Severity set to 'important' from 'serious'

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

Processed: severity of 917615 is serious

[Debian Bug Tracking System]

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

> severity 917615 serious
Bug #917615 [ruby-zoom] ruby-zoom: Please Build-Depend on libyaz-dev
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#920817: Should this package be removed?

[Moritz Muehlenhoff]

Package: fsgateway
Severity: serious

Should fsgateway be removed? Already missed stretch, seems dead upstream,
dropped from testing since two years and last upload was in 2015.

Cheers,
Moritz

Bug#920818: Should this package be removed?

[Moritz Muehlenhoff]

Source: mysql-connector-net
Severity: serious

Last upload three years ago and removed from testing for a year.

Cheers,
Moritz

Bug#884155: show be fixed in unstable & testing

[Paolo Greppi]

chai 4.2 has landed in testing, and all tests pass.
can this be closed now ?

Paolo

Bug#917730: marked as done (caffeine: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 15:49:25 +
with message-id 
and subject line Bug#917730: fixed in caffeine 2.9.4-2
has caused the Debian Bug report #917730,
regarding caffeine: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
917730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caffeine
Version: 2.9.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,bash-completion --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py clean 
> Compiling for Locale: bg
> Compiling for Locale: ro
> Compiling for Locale: pl
> Compiling for Locale: en_GB
> Compiling for Locale: ru
> Compiling for Locale: gl
> Compiling for Locale: fr
> Compiling for Locale: it
> Compiling for Locale: nl
> Compiling for Locale: lt
> Compiling for Locale: pt
> Compiling for Locale: sv
> Compiling for Locale: da
> Compiling for Locale: ms
> Compiling for Locale: he
> Compiling for Locale: no
> Compiling for Locale: ar
> Compiling for Locale: pt_BR
> Compiling for Locale: eu
> Compiling for Locale: xh
> Compiling for Locale: eo
> Compiling for Locale: tr
> Compiling for Locale: bs
> Compiling for Locale: fi
> Compiling for Locale: vi
> Compiling for Locale: uk
> Compiling for Locale: sk
> Compiling for Locale: es
> Compiling for Locale: de
> Compiling for Locale: zh_TW
> Compiling for Locale: el
> Compiling for Locale: th
> Compiling for Locale: ja
> Compiling for Locale: hu
> Compiling for Locale: ca
> Compiling for Locale: cs
> running clean
> removing '/<>/.pybuild/cpython3_3.7_caffeine/build' (and 
> everything under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.7' does not exist -- can't clean it
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building caffeine using existing 
> ./caffeine_2.9.4.orig.tar.gz
> dpkg-source: warning: ignoring deletion of file 
> translations/caffeine-indicator.pot, use --include-removal to override
> dpkg-source: error: cannot represent change to 
> share/locale/ar/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/ar/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/bg/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/bg/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/bs/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/bs/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/ca/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/ca/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/cs/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/cs/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/da/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/da/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/de/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/de/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the

Bug#884155: show be fixed in unstable & testing

[Santiago Vila]

On Tue, Jan 29, 2019 at 04:42:09PM +0100, Paolo Greppi wrote:
> chai 4.2 has landed in testing, and all tests pass.
> can this be closed now ?

AFAIK, yes (unless there is yet another different version in
experimental of either this package or a build-dependency, which I
have not tested).

Thanks.

Bug#918741: marked as done (Build-Depends on deprecated libjemalloc SONAME directly)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 16:04:24 +
with message-id 
and subject line Bug#918741: fixed in fakechroot 2.19-3.2
has caused the Debian Bug report #918741,
regarding Build-Depends on deprecated libjemalloc SONAME directly
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.)


-- 
918741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fakechroot
Version: 2.19-3
Severity: serious

Hi,

I uploaded jemalloc 5.1.0-2 to unstable the other day. It involves a new
ABI and SONAME and thus a transition from libjemalloc1 -> libjemalloc2.

I noticed that your package Build-Depends directly on libjemalloc1, and
thus this package will start FTBFSing once libjemalloc1 gets removed
from the archive.

It seems like the B-D is there because the test suite includes a test
for jemalloc (which is great!), and specifically the binary library
which it's LD_PRELOADing, hence the dependency on the binary package.

Rather than s/libjemalloc1/libjemalloc2/, I would recommend to B-D on
"libjemalloc-dev" like a regular source package, and then modify the
test suite to search for the symlink "libjemalloc.so" (e.g.
/usr/lib/x86_64-linux-gnu/libjemalloc.so). This would make it future
proof for future ABI/SONAME bumps.

Apologies for filing this after the transition has already started -- as
a B-D on the binary package is unsual, it didn't occur to me to
grep-dctrl for that beforehand.

Regards,
Faidon
--- End Message ---
--- Begin Message ---
Source: fakechroot
Source-Version: 2.19-3.2

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

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer  (supplier of updated fakechroot 
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: Sun, 27 Jan 2019 16:34:19 +0100
Source: fakechroot
Architecture: source
Version: 2.19-3.2
Distribution: unstable
Urgency: medium
Maintainer: Piotr Roszatycki 
Changed-By: Johannes 'josch' Schauer 
Closes: 918741 918742
Changes:
 fakechroot (2.19-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-Depends on libjemalloc-dev instead of libjemalloc1 (closes: #918741)
   * Disable jemalloc test because since libjemalloc2, fakechroot is
 incompatible with jemalloc. They must not be preloaded at the same time.
 (closes: #918742)
Checksums-Sha1:
 03052cac09e1f5ac4e32f5d1c5a690915d395884 2010 fakechroot_2.19-3.2.dsc
 237d21e9a9c0d2da0d89917922fde7e0f6df9de8 10384 
fakechroot_2.19-3.2.debian.tar.xz
 a2168043afc2b5cd21ce4e255ee1010475e4d13f 5647 
fakechroot_2.19-3.2_amd64.buildinfo
Checksums-Sha256:
 9ac5d4cb6d4c2b105531bf3095cc4477e9d46d77ba734b16454cf2bf39c48134 2010 
fakechroot_2.19-3.2.dsc
 4db2790de6a191d5475faa81d5b1b1b0b8157abd7249b9906ee4c27a0567bd83 10384 
fakechroot_2.19-3.2.debian.tar.xz
 77393f62e512e531cb293e751a5d9089047c648dbda7e96a7a1a581b5487b851 5647 
fakechroot_2.19-3.2_amd64.buildinfo
Files:
 8a7dc01da0134176fbe50e1002cc8f04 2010 utils optional fakechroot_2.19-3.2.dsc
 ff6cb95db74140ef959f91744473df53 10384 utils optional 
fakechroot_2.19-3.2.debian.tar.xz
 87574c9608aa5a4936a99d9c7b6b6b36 5647 utils optional 
fakechroot_2.19-3.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAlxN0HgACgkQ8sulx4+9
g+ESjg//Univ20tp7tePl3DcTbqmdX4Zn4+l3NQ2kOlPckVCZDrJekI+hZGtv4SZ
Hq3+GeUmLAmc1NZwPu41qcKylkamA2jEff8fc2ZjTR1fWqQUQljWTUfvUG7/fDrQ
SwuoAv4wZhCUmlG/M1bxRGMlYz9Am+6YSWFeb7pTR+Sl5qv0rHGN/LRjFMFPoD9e
XJcQA+a2GSNA1QX5fMm9CMYnqj922uGGEYrpLgvnNghnGpRMupHtdjfTWrv8cLlb
EWY5r43SNLMn6lDG++zIpeKCNmL1lNaVVwANXKXgqAjYa2q6FIj4EsE9m98ejDmM
XlkeGLczIp9PrDV5VpTrnE7vLpIsSoOEjHhHH9OyoOW4aPROyRAToYxV4M3sMwAK
6wyJW2uBk0uKqAm0ghv4IbsgLjCouC9aOT+BgXI3i5eLL26HvyyS4q3Hail9DcKE
5KUBZr3q9AXGjzYQVmoOtp7J0rJyOvrQNRNnBtF4WrpCgaldKNBl8hy0VaAdvXbS
d6i7DJUQSMolsuhejbnTPOvGhzPTwcOCgTcfJgfD2JCOIVM0kkG6F7PcSy8AA14z
yYOxyThBxVSISp0a8o0pmZHC0jh8Nm0WrDqgKyqGRdFGxwB5DI9hOGsBZXH5wxaQ
zzQ32vBIt1YnRB55YKKfd4Ucx8rkF13nIz+d/z0v/Sn26EcDlxo=
=s+TC
-END PG

Bug#918742: marked as done (Initialization loop/deadlock when used with jemalloc)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 16:04:24 +
with message-id 
and subject line Bug#918742: fixed in fakechroot 2.19-3.2
has caused the Debian Bug report #918742,
regarding Initialization loop/deadlock when used with jemalloc
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.)


-- 
918742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fakechroot
Version: 2.19-3
Severity: serious

Hi again,

So jemalloc 5.1.0-2 was recently uploaded to unstable. The build
currently fails due to the explicit dependency on libjemalloc1 (cf.
#918741), but as soon as this gets fixed, another issue is uncovered:

While building this package, the jemalloc test deadlocks, and the build
hangs. This can be easily reproduced as follows:
  apt install libfakechroot libjemalloc2
  LD_PRELOAD="libjemalloc.so.2 libfakechroot.so" /bin/true
  

The test isn't spurious but an actual issue. One could do:
  fakechroot 
...and still hit this bug.

The bug is effectively the same as #872669, which I had previously
resolved by disabling jemalloc's --enable-prof. This option was
re-enabled in 5.x (I forgot about that bug :/) and...  I'd like to keep
it that way, so I tried to troubleshoot this further.

It looks like there's a preloading loop between those libraries that
results in deadlocking. Effectively, during its initialization
(malloc_init) jemalloc tries to initialize libgcc's unwind code
(_Unwind_Backtrace), which in turn calls dl_iterate_phdr, which is
captured by libfakechroot, which calls dlsym()/dlerror(), which tries to
allocate memory back again, which deadlocks jemalloc.

The backtrace is (note how #6 and #20 are the same):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
#1  0x7fd764008704 in __GI___pthread_mutex_lock (mutex=0x7fd7647a0500 
) at ../nptl/pthread_mutex_lock.c:80
#2  0x7fd76475f0dc in malloc_mutex_lock_final (mutex=0x7fd7647a04c0 
) at include/jemalloc/internal/mutex.h:141
#3  je_malloc_mutex_lock_slow (mutex=mutex@entry=0x7fd7647a04c0 ) at 
src/mutex.c:84
#4  0x7fd76470e244 in malloc_mutex_lock (mutex=0x7fd7647a04c0 , 
tsdn=0x0) at include/jemalloc/internal/mutex.h:205
#5  malloc_init_hard () at src/jemalloc.c:1506
#6  0x7fd76471524d in malloc_init () at src/jemalloc.c:217
#7  imalloc (dopts=, sopts=) at 
src/jemalloc.c:1986
#8  calloc (num=num@entry=1, size=size@entry=32) at src/jemalloc.c:2138
#9  0x7fd763ff8a25 in _dlerror_run (operate=operate@entry=0x7fd763ff8390 
, args=args@entry=0x7ffdd14ddfa0) at dlerror.c:141
#10 0x7fd763ff840f in __dlsym (handle=, name=) at dlsym.c:70
#11 0x7fd7644f49b4 in ?? () from 
/usr/lib/x86_64-linux-gnu/fakechroot/libfakechroot.so
#12 0x7fd7644edffc in dl_iterate_phdr () from 
/usr/lib/x86_64-linux-gnu/fakechroot/libfakechroot.so
#13 0x7fd763ff02a1 in _Unwind_Find_FDE (pc=0x7fd763fee867 
<_Unwind_Backtrace+55>, bases=bases@entry=0x7ffdd14de368) at 
../../../src/libgcc/unwind-dw2-fde-dip.c:469
#14 0x7fd763fec983 in uw_frame_state_for 
(context=context@entry=0x7ffdd14de2c0, fs=fs@entry=0x7ffdd14de110) at 
../../../src/libgcc/unwind-dw2.c:1257
#15 0x7fd763fedb60 in uw_init_context_1 (context=0x7ffdd14de2c0, 
outer_cfa=0x7ffdd14de570, outer_ra=0x7fd76476a878 )
at ../../../src/libgcc/unwind-dw2.c:1586
#16 0x7fd763fee868 in _Unwind_Backtrace (trace=trace@entry=0x7fd76475fdb0 
, trace_argument=trace_argument@entry=0x0)
at ../../../src/libgcc/unwind.inc:295
#17 0x7fd76476a878 in je_prof_boot2 (tsd=tsd@entry=0x7fd763fd7740) at 
src/prof.c:2392
#18 0x7fd76470e308 in malloc_init_hard () at src/jemalloc.c:1538
#19 malloc_init_hard () at src/jemalloc.c:1500
#20 0x7fd764710a85 in malloc_init () at src/jemalloc.c:217

I don't think it's a bug on either library per se. I was wondering if
you had any insight on how we could address this in fakechroot somehow
rather than in jemalloc, as that doesn't look to be easy without
disabling the profiling feature.

Regards,
Faidon
--- End Message ---
--- Begin Message ---
Source: fakechroot
Source-Version: 2.19-3.2

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

Debian distribution maintenance software
pp.
Joh

Bug#918264: marked as done (ruby-activerecord-session-store: cannot fulfill the dependencies in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 16:09:52 +
with message-id 
and subject line Bug#920816: Removed package(s) from unstable
has caused the Debian Bug report #918264,
regarding ruby-activerecord-session-store: cannot fulfill the dependencies in 
unstable
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.)


-- 
918264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-activerecord-session-store
Version: 1.0.0-2
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 ruby-activerecord-session-store : Depends: ruby-actionpack (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed
   Depends: ruby-activerecord (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed
   Depends: ruby-railties (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed
--- End Message ---
--- Begin Message ---
Version: 1.0.0-2+rm

Dear submitter,

as the package ruby-activerecord-session-store has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/920816

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#918263: marked as done (ruby-cucumber-rails: Depends: ruby-railties (< 2:5) but 2:5.2.0+dfsg-2 is to be installed)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 16:08:42 +
with message-id 
and subject line Bug#920812: Removed package(s) from unstable
has caused the Debian Bug report #918263,
regarding ruby-cucumber-rails: Depends: ruby-railties (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed
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.)


-- 
918263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-cucumber-rails
Version: 1.4.3-2
Severity: serious

The following packages have unmet dependencies:
 ruby-cucumber-rails : Depends: ruby-railties (< 2:5) but 2:5.2.0+dfsg-2 is to 
be installed
--- End Message ---
--- Begin Message ---
Version: 1.4.3-2+rm

Dear submitter,

as the package ruby-cucumber-rails has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/920812

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#920821: gcc-8: regression: ICE while compiling Trilinos

[Graham Inggs]

Source: gcc-8
Version: 8.2.0-15
Severity: serious
Affects: src:trilinos
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88995

Hi Maintainer

Trilinos FTBFS with an ICE with gcc-8 8.2.0-15 (8.2.0-14 was fine).

Confirmed on reproducible builds [1].

In file included from 
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/serial/TestSerial_SharedAlloc.cpp:45:
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/TestSharedAlloc.hpp: 
In instantiation of 'void Test::test_shared_alloc() [with MemorySpace = 
Kokkos::HostSpace; ExecutionSpace = Kokkos::Serial]':
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/serial/TestSerial_SharedAlloc.cpp:52:58: 
  required from here
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/TestSharedAlloc.hpp:129:57: 
internal compiler error: in lookup_template_class_1, at cp/pt.c:9459
   RecordFull * rec = RecordFull::allocate( s, name, size * ( i + 1 
) );

 ^~~~
Matthias suggested this looks like upstream #88995.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/trilinos.html

Bug#902007: marked as done (igor: missing B-D on some blas-dev package)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 17:16:05 +0100
with message-id <20190129161605.wwegb4kslby4a...@an3as.eu>
and subject line Closing this bug since Build-Depends was added
has caused the Debian Bug report #902007,
regarding igor: missing B-D on some blas-dev package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
902007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: igor
Version: 1.2.0+dfsg-1
Severity: serious
Justification: fails to build from source

Hi,

igor FTBFS:
https://buildd.debian.org/status/package.php?p=igor&suite=experimental

/bin/bash ../libtool  --tag=CXX   --mode=link g++ -I/usr/include/jemalloc 
-I/usr/include/gsl -fopenmp -DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 
-fdebug-prefix-map=/<>/igor-1.2.0+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wl,-z,relro -Wl,--as-needed -o igor 
igor-Aligner.o igor-Bestscenarioscounter.o igor-Counter.o 
igor-Coverageerrcounter.o igor-Deletion.o igor-Dinuclmarkov.o 
igor-Errorscounter.o igor-Errorrate.o igor-Genechoice.o igor-GenModel.o 
igor-HypermutationfullNmererrorrate.o igor-Hypermutationglobalerrorrate.o 
igor-Insertion.o igor-IntStr.o igor-main.o igor-Model_marginals.o 
igor-Model_Parms.o igor-Pgencounter.o igor-Rec_Event.o igor-Singleerrorrate.o 
igor-Utils.o -lgsl -lcblas -ljemalloc -lpthread -ldl  
libtool: link: g++ -I/usr/include/jemalloc -I/usr/include/gsl -fopenmp 
-DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 
-fdebug-prefix-map=/<>/igor-1.2.0+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,--as-needed -o igor 
igor-Aligner.o igor-Bestscenarioscounter.o igor-Counter.o 
igor-Coverageerrcounter.o igor-Deletion.o igor-Dinuclmarkov.o 
igor-Errorscounter.o igor-Errorrate.o igor-Genechoice.o igor-GenModel.o 
igor-HypermutationfullNmererrorrate.o igor-Hypermutationglobalerrorrate.o 
igor-Insertion.o igor-IntStr.o igor-main.o igor-Model_marginals.o 
igor-Model_Parms.o igor-Pgencounter.o igor-Rec_Event.o igor-Singleerrorrate.o 
igor-Utils.o  -lgsl -lcblas -ljemalloc -lpthread -ldl -fopenmp
/usr/bin/ld: cannot find -lcblas
collect2: error: ld returned 1 exit status
Makefile:426: recipe for target 'igor' failed


Andreas
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4791--- End Message ---

Processed: gcc-8: regression: ICE while compiling Trilinos

[Debian Bug Tracking System]

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

> affects 920821 + src:trilinos
Bug #920821 [src:gcc-8] gcc-8: regression: ICE while compiling Trilinos
Added indication that 920821 affects src:trilinos
> thanks
Stopping processing here.

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

Bug#920822: phpmyadmin: CVE-2019-6798: PMASA-2019-2

[Salvatore Bonaccorso]

Source: phpmyadmin
Version: 4:4.6.6-5
Severity: grave
Tags: security upstream
Control: found -1 4:4.6.6-4

Hi,

The following vulnerability was published for phpmyadmin.

CVE-2019-6798[0]:
| An issue was discovered in phpMyAdmin before 4.8.5. A vulnerability was
| reported where a specially crafted username can be used to trigger a
| SQL injection attack through the designer feature.

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-2019-6798
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6798
[1] https://www.phpmyadmin.net/security/PMASA-2019-2/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: phpmyadmin: CVE-2019-6798: PMASA-2019-2

[Debian Bug Tracking System]

Processing control commands:

> found -1 4:4.6.6-4
Bug #920822 [src:phpmyadmin] phpmyadmin: CVE-2019-6798: PMASA-2019-2
Marked as found in versions phpmyadmin/4:4.6.6-4.

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

Bug#920823: phpmyadmin: CVE-2019-6799: PMASA-2019-1

[Salvatore Bonaccorso]

Source: phpmyadmin
Version: 4:4.6.6-5
Severity: grave
Tags: security upstream
Control: found -1 4:4.6.6-4

Hi,

The following vulnerability was published for phpmyadmin.

CVE-2019-6799[0]:
| An issue was discovered in phpMyAdmin before 4.8.5. When the
| AllowArbitraryServer configuration setting is set to true, with the use
| of a rogue MySQL server, an attacker can read any file on the server
| that the web server's user can access. This is related to the
| mysql.allow_local_infile PHP configuration, and the inadvertent
| ignoring of "options(MYSQLI_OPT_LOCAL_INFILE" calls.

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-2019-6799
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6799
[1] https://www.phpmyadmin.net/security/PMASA-2019-1/

Regards,
Salvatore

Processed: phpmyadmin: CVE-2019-6799: PMASA-2019-1

[Debian Bug Tracking System]

Processing control commands:

> found -1 4:4.6.6-4
Bug #920823 [src:phpmyadmin] phpmyadmin: CVE-2019-6799: PMASA-2019-1
Marked as found in versions phpmyadmin/4:4.6.6-4.

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

Processed: fixed 919623 in rssh/2.3.4-9

[Debian Bug Tracking System]

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

> fixed 919623 rssh/2.3.4-9
Bug #919623 [rssh] rssh: CVE-2019-118: Remote code execution in scp support
Marked as fixed in versions rssh/2.3.4-9.
> thanks
Stopping processing here.

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

Bug#920828: elpa-lsp-ui: fails to install: ERROR: install script from elpa-lsp-ui package failed

[Andreas Beckmann]

Package: elpa-lsp-ui
Version: 6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up emacs-gtk (1:26.1+1-3) ...
  update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs 
(emacs) in auto mode
  update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) 
in auto mode
  tsort: -: input contains a loop:
  tsort: elpa-dash
  tsort: emacsen-common
  tsort: -: input contains a loop:
  tsort: elpa-s
  tsort: emacsen-common
  Install elpa-dash for emacs
  install/dash-2.14.1: Handling install of emacsen flavor emacs
  install/dash-2.14.1: byte-compiling for emacs
  Install elpa-s for emacs
  install/s-1.12.0: Handling install of emacsen flavor emacs
  install/s-1.12.0: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-spinner for emacs
  install/spinner-1.7.3: Handling install of emacsen flavor emacs
  install/spinner-1.7.3: byte-compiling for emacs
  Install elpa-f for emacs
  install/f-0.20.0: Handling install of emacsen flavor emacs
  install/f-0.20.0: byte-compiling for emacs
  Install elpa-ht for emacs
  install/ht-2.2: Handling install of emacsen flavor emacs
  install/ht-2.2: byte-compiling for emacs
  Install elpa-dash-functional for emacs
  install/dash-functional-1.2.0: Handling install of emacsen flavor emacs
  install/dash-functional-1.2.0: byte-compiling for emacs
  Install elpa-lsp-mode for emacs
  install/lsp-mode-6.0: Handling install of emacsen flavor emacs
  install/lsp-mode-6.0: byte-compiling for emacs
  Setting up emacs (1:26.1+1-3) ...
  Setting up elpa-markdown-mode (2.3+154-2) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-markdown-mode for emacs
  install/markdown-mode-2.3snapshot154: Handling install of emacsen flavor emacs
  install/markdown-mode-2.3snapshot154: byte-compiling for emacs
  Setting up elpa-lsp-ui (6.0-1) ...
  Install elpa-f for emacs
  install/f-0.20.0: Handling install of emacsen flavor emacs
  install/f-0.20.0: byte-compiling for emacs
  Install elpa-ht for emacs
  install/ht-2.2: Handling install of emacsen flavor emacs
  install/ht-2.2: byte-compiling for emacs
  Install elpa-spinner for emacs
  install/spinner-1.7.3: Handling install of emacsen flavor emacs
  install/spinner-1.7.3: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-markdown-mode for emacs
  install/markdown-mode-2.3snapshot154: Handling install of emacsen flavor emacs
  install/markdown-mode-2.3snapshot154: byte-compiling for emacs
  Install elpa-dash for emacs
  install/dash-2.14.1: Handling install of emacsen flavor emacs
  install/dash-2.14.1: byte-compiling for emacs
  Install elpa-dash-functional for emacs
  install/dash-functional-1.2.0: Handling install of emacsen flavor emacs
  install/dash-functional-1.2.0: byte-compiling for emacs
  Install elpa-lsp-mode for emacs
  install/lsp-mode-6.0: Handling install of emacsen flavor emacs
  install/lsp-mode-6.0: byte-compiling for emacs
  Install elpa-lsp-ui for emacs
  install/lsp-ui-6.0: Handling install of emacsen flavor emacs
  install/lsp-ui-6.0: byte-compiling for emacs
  
  In toplevel form:
  lsp-ui-doc.el:179:1:Warning: Unused lexical argument `include-deleted-frame'
  
  In toplevel form:
  lsp-ui-flycheck.el:30:1:Error: Cannot open load file: No such file or 
directory, flycheck
  
  In lsp-ui-sideline-mode:
  lsp-ui-sideline.el:493:29:Warning: assignment to free variable
  `flycheck-display-errors-function'
  
  In end of data:
  lsp-ui-sideline.el:501:1:Warning: the following functions are not known to be
  defined: flycheck-overlay-errors-in, flycheck-error-format-message-and-id,
  flycheck-error-level
  ERROR: install script from elpa-lsp-ui package failed
  dpkg: error processing package elpa-lsp-ui (--configure):
   installed elpa-lsp-ui package post-installation script subprocess returned 
error exit status 1
  Processing triggers for systemd (240-4) ...
  Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
  Processing triggers for libc-bin (2.28-5) ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.0+dfsg-7) ...
  Errors were encountered while processing:
   elpa-lsp-ui


cheers,

Andreas


elpa-lsp-ui_6.0-1.log.gz
Description: application/gzip

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Ben Greear]

On 1/29/19 1:32 AM, Andrej Shadura wrote:

(Sending this again since the first submission’s got delayed by a filter.)

On Wed, 16 Jan 2019 at 21:51, Different55  wrote:


Alright, not entirely sure if I did this right but I followed Debian's Building 
Tutorial to download and build wpa_supplicant with the changes you linked. One 
exception, I use wpa_supplicant through NetworkManager and could not work out 
where I needed to create a wpa_supplicant.conf, so I changed the one line in 
config.c to:

 { INT(no_oper_classes_ie), 1 },

which I'm hoping makes the default "on" instead of "off." Sadly doesn't appear 
to have made a difference, although it didn't make anything worse either.

Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my 
desktop this morning and had the same problems with a Qualcomm Atheros AR9462 
Wireless Adapter.


Forwarding Different55’s message from the Debian bug here:

Sure thing! Sadly doesn't seem to make a difference. I've included
another log, this time starting from the time wpa_supplicant was
brought back up to a little bit after I got the popup that the
connection had failed.


That was the only idea I had, so not sure why it is not working.

You could bisect the hostapd project until you find the problem commit
and report it on the hostap mailing list.

Thanks,
Ben


--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com

Bug#920829: agg FTBFS on 32bit: symbol differences

[Adrian Bunk]

Source: agg
Version: 1:2.6.0-r132+dfsg1-1
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libagg2/DEBIAN/symbols doesn't match 
completely debian/libagg2.symbols
--- debian/libagg2.symbols (libagg2_1:2.6.0-r132+dfsg1-1_i386)
+++ dpkg-gensymbols4cR8ER   2019-01-28 11:13:56.908372200 +
@@ -34,7 +34,7 @@
  
_ZN3agg11math_strokeINS_11pod_bvectorINS_10point_baseIdEELj68calc_arcERS4_dd@Base
 2.6.0
  
_ZN3agg11math_strokeINS_11pod_bvectorINS_10point_baseIdEELj68calc_capERS4_RKNS_11vertex_distES9_d@Base
 2.6.0
  
_ZN3agg11math_strokeINS_11pod_bvectorINS_10point_baseIdEELj69calc_joinERS4_RKNS_11vertex_distES9_S9_dd@Base
 2.6.0
- _ZN3agg11pod_bvectorINS_10point_baseIdEELj6EE14allocate_blockEj@Base 2.6.0
+#MISSING: 1:2.6.0-r132+dfsg1-1# 
_ZN3agg11pod_bvectorINS_10point_baseIdEELj6EE14allocate_blockEj@Base 2.6.0
  _ZN3agg11pod_bvectorINS_10point_baseIdEELj6EED1Ev@Base 2.6.0
  _ZN3agg11pod_bvectorINS_10point_baseIdEELj6EED2Ev@Base 2.6.0
  _ZN3agg11pod_bvectorINS_11vertex_distELj6EED1Ev@Base 2.6.0
@@ -239,7 +239,7 @@
  _ZN3agg16spline_ctrl_implD0Ev@Base 2.6.0
  _ZN3agg16spline_ctrl_implD1Ev@Base 2.6.0
  _ZN3agg16spline_ctrl_implD2Ev@Base 2.6.0
- _ZN3agg17clip_line_segmentIdEEjPT_S2_S2_S2_RKNS_9rect_baseIS1_EE@Base 2.6.0
+#MISSING: 1:2.6.0-r132+dfsg1-1# 
_ZN3agg17clip_line_segmentIdEEjPT_S2_S2_S2_RKNS_9rect_baseIS1_EE@Base 2.6.0
  _ZN3agg17g_elder_bit_tableE@Base 2.6.0
  _ZN3agg17mcs7x12_mono_highE@Base 2.6.0
  _ZN3agg17polygon_ctrl_impl13on_arrow_keysE@Base 2.6.0
@@ -275,7 +275,7 @@
  
(optional)_ZN3agg18conv_adaptor_vcgenINS_6curve4ENS_12vcgen_strokeENS_12null_markersEE6vertexEPdS5_@Base
 2.6.0
  
_ZN3agg18conv_adaptor_vcgenINS_7ellipseENS_12vcgen_strokeENS_12null_markersEE6vertexEPdS5_@Base
 2.6.0
  
_ZN3agg18conv_adaptor_vcgenINS_8gsv_textENS_12vcgen_strokeENS_12null_markersEE6vertexEPdS5_@Base
 2.6.0
- 
(optional)_ZN3agg18conv_adaptor_vcgenINS_9path_baseINS_20vertex_block_storageIdLj8ELj256ENS_12vcgen_strokeENS_12null_markersEE6vertexEPdS8_@Base
 2.6.0
+#MISSING: 1:2.6.0-r132+dfsg1-1# 
(optional)_ZN3agg18conv_adaptor_vcgenINS_9path_baseINS_20vertex_block_storageIdLj8ELj256ENS_12vcgen_strokeENS_12null_markersEE6vertexEPdS8_@Base
 2.6.0
  _ZN3agg18vcgen_markers_term10add_vertexEddj@Base 2.6.0
  _ZN3agg18vcgen_markers_term10remove_allEv@Base 2.6.0
  _ZN3agg18vcgen_markers_term6rewindEj@Base 2.6.0
@@ -338,6 +338,8 @@
  _ZN3agg8gsv_text9load_fontEPKc@Base 2.6.0
  _ZN3agg8gsv_textC1Ev@Base 2.6.0
  _ZN3agg8gsv_textC2Ev@Base 2.6.0
+ _ZN3agg8sRGB_lutIfEC1Ev@Base 1:2.6.0-r132+dfsg1-1
+ _ZN3agg8sRGB_lutIfEC2Ev@Base 1:2.6.0-r132+dfsg1-1
  _ZN3agg8sRGB_lutItEC1Ev@Base 2.6.0
  _ZN3agg8sRGB_lutItEC2Ev@Base 2.6.0
  _ZN3agg9arrowhead6rewindEj@Base 2.6.0
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:45: binary-arch] Error 2

Processed: fixed 917694 in 0.6.1+ds-1

[Debian Bug Tracking System]

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

> fixed 917694 0.6.1+ds-1
Bug #917694 {Done: Kay Hayen } [src:nuitka] nuitka: FTBFS: 
build-dependency not installable: python-imaging
The source 'nuitka' and version '0.6.1+ds-1' do not appear to match any binary 
packages
Marked as fixed in versions nuitka/0.6.1+ds-1.
> thanks
Stopping processing here.

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

Processed: affects 920791

[Debian Bug Tracking System]

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

> affects 920791 src:freedink
Bug #920791 [libglm-dev] New libglm-dev
Added indication that 920791 affects src:freedink
> thanks
Stopping processing here.

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

Processed: affects 919658

[Debian Bug Tracking System]

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

> affects 919658 src:ocaml-gettext
Bug #919658 [src:camomile] ocaml-gettext ftbfs (comomile module not found)
Added indication that 919658 affects src:ocaml-gettext
> thanks
Stopping processing here.

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

Bug#920524: Fix by setting RUNPATH

[Adrian Bunk]

On Sat, Jan 26, 2019 at 06:08:01PM +0100, Hilko Bengen wrote:
> control: tag -1 patch fixed-upstream
> 
> This can be fixed by setting a RUNPATH for the valabind binary, see
> also: https://github.com/radare/valabind/pull/49
> 
> This is something Lintian will yell about, but there seems to be no
> other way at this stage.

It looks so wrong - either valac should provide this as a proper library 
with so-name or valabind shouldn't be using it.

Note that the RUNPATH alone is not sufficient as ugly workaround hack,
additionally this would require a strict dependency on the exact version
of valac, something like Depends: valac (>= 0.42), valac (<< 0.43).

> Cheers,
> -Hilko

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#920835: mlucas FTBFS on !amd64: test failures

[Adrian Bunk]

Source: mlucas
Version: 17.1-1
Severity: serious
Tags: ftbfs

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

...
FAIL: tests/spot-check
==

./tests/..//mlucas: 149: exec: ./tests/../: Permission denied
FAIL tests/spot-check (exit status: 126)

FAIL: tests/self-test
=

./tests/..//mlucas: 149: exec: ./tests/../: Permission denied
FAIL tests/self-test (exit status: 126)

FAIL: tests/fermat-test
===

./tests/..//mlucas: 149: exec: ./tests/../: Permission denied
FAIL tests/fermat-test (exit status: 126)


Testsuite summary for Mlucas 17.1

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

See ./test-suite.log
Please report to ewma...@aol.com

make[3]: *** [Makefile:12510: test-suite.log] Error 1

Bug#920834: mlucas: FTBFS and baseline vioiation on i386

[Adrian Bunk]

Source: mlucas
Version: 17.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0

...
gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize -floop-nest-optimize 
-fomit-frame-pointer -g -g3 -fstack-protector-strong -fstack-clash-protection 
-mmitigate-rop -fwrapv -m32 -msse2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,-z,now -o mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o 
src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o 
src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o 
src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o 
src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o 
src/mlucas_sse2-get_fp_rnd_const.o src/mlucas_sse2-get_preferred_fft_radix.o 
src/mlucas_sse2-imul_macro.o src/mlucas_sse2-mers_mod_square.o 
src/mlucas_sse2-mi64.o src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o 
src/mlucas_sse2-radix1008_ditN_cy_dif1.o 
src/mlucas_sse2-radix1024_ditN_cy_dif1.o 
src/mlucas_sse2-radix104_ditN_cy_dif1.o src/mlucas_sse2-radix10_ditN_cy_dif1.o 
src/mlucas_sse2-radix112_ditN_cy_dif1.o src/mlucas_sse2-radix11_ditN_cy_dif1.o 
src/mlucas_sse2-radix120_ditN_cy_dif1.o src/mlucas_sse2-radix128_ditN_cy_dif1.o 
src/mlucas_sse2-radix12_ditN_cy_dif1.o src/mlucas_sse2-radix13_ditN_cy_dif1.o 
src/mlucas_sse2-radix144_ditN_cy_dif1.o src/mlucas_sse2-radix14_ditN_cy_dif1.o 
src/mlucas_sse2-radix15_ditN_cy_dif1.o src/mlucas_sse2-radix160_ditN_cy_dif1.o 
src/mlucas_sse2-radix16_dif_dit_pass.o src/mlucas_sse2-radix16_ditN_cy_dif1.o 
src/mlucas_sse2-radix16_dyadic_square.o src/mlucas_sse2-radix16_pairFFT_mul.o 
src/mlucas_sse2-radix16_wrapper_ini.o src/mlucas_sse2-radix16_wrapper_square.o 
src/mlucas_sse2-radix176_ditN_cy_dif1.o src/mlucas_sse2-radix18_ditN_cy_dif1.o 
src/mlucas_sse2-radix192_ditN_cy_dif1.o src/mlucas_sse2-radix208_ditN_cy_dif1.o 
src/mlucas_sse2-radix20_ditN_cy_dif1.o src/mlucas_sse2-radix224_ditN_cy_dif1.o 
src/mlucas_sse2-radix22_ditN_cy_dif1.o src/mlucas_sse2-radix240_ditN_cy_dif1.o 
src/mlucas_sse2-radix24_ditN_cy_dif1.o src/mlucas_sse2-radix256_ditN_cy_dif1.o 
src/mlucas_sse2-radix26_ditN_cy_dif1.o src/mlucas_sse2-radix288_ditN_cy_dif1.o 
src/mlucas_sse2-radix28_ditN_cy_dif1.o src/mlucas_sse2-radix30_ditN_cy_dif1.o 
src/mlucas_sse2-radix31_ditN_cy_dif1.o src/mlucas_sse2-radix32_dif_dit_pass.o 
src/mlucas_sse2-radix32_ditN_cy_dif1.o src/mlucas_sse2-radix32_dyadic_square.o 
src/mlucas_sse2-radix32_wrapper_ini.o src/mlucas_sse2-radix32_wrapper_square.o 
src/mlucas_sse2-radix36_ditN_cy_dif1.o src/mlucas_sse2-radix4032_ditN_cy_dif1.o 
src/mlucas_sse2-radix40_ditN_cy_dif1.o src/mlucas_sse2-radix44_ditN_cy_dif1.o 
src/mlucas_sse2-radix48_ditN_cy_dif1.o src/mlucas_sse2-radix512_ditN_cy_dif1.o 
src/mlucas_sse2-radix52_ditN_cy_dif1.o src/mlucas_sse2-radix56_ditN_cy_dif1.o 
src/mlucas_sse2-radix5_ditN_cy_dif1.o src/mlucas_sse2-radix60_ditN_cy_dif1.o 
src/mlucas_sse2-radix63_ditN_cy_dif1.o src/mlucas_sse2-radix64_ditN_cy_dif1.o 
src/mlucas_sse2-radix6_ditN_cy_dif1.o src/mlucas_sse2-radix72_ditN_cy_dif1.o 
src/mlucas_sse2-radix768_ditN_cy_dif1.o src/mlucas_sse2-radix7_ditN_cy_dif1.o 
src/mlucas_sse2-radix80_ditN_cy_dif1.o src/mlucas_sse2-radix88_ditN_cy_dif1.o 
src/mlucas_sse2-radix8_dif_dit_pass.o src/mlucas_sse2-radix8_ditN_cy_dif1.o 
src/mlucas_sse2-radix960_ditN_cy_dif1.o src/mlucas_sse2-radix96_ditN_cy_dif1.o 
src/mlucas_sse2-radix992_ditN_cy_dif1.o src/mlucas_sse2-radix9_ditN_cy_dif1.o 
src/mlucas_sse2-rng_isaac.o src/mlucas_sse2-test_fft_radix.o 
src/mlucas_sse2-threadpool.o src/mlucas_sse2-twopmodq.o 
src/mlucas_sse2-twopmodq100.o src/mlucas_sse2-twopmodq128.o 
src/mlucas_sse2-twopmodq128_96.o src/mlucas_sse2-twopmodq160.o 
src/mlucas_sse2-twopmodq192.o src/mlucas_sse2-twopmodq256.o 
src/mlucas_sse2-twopmodq64_test.o src/mlucas_sse2-twopmodq80.o 
src/mlucas_sse2-twopmodq96.o src/mlucas_sse2-types.o src/mlucas_sse2-util.o  
-lm 
/usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 222
/tmp/ccxqWoW9.ltrans26.ltrans.o: in function `radix16_dyadic_square':
:(.text+0x1213e): undefined reference to 
`SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:3685: mlucas-sse2] Error 1


SSE i  not part of the i386 baseline.

Bug#920837: netdata: binary-any FTBFS

[Adrian Bunk]

Source: netdata
Version: 1.11.1+dfsg-5
Severity: serious
Tags: ftbfs

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

...
# Move architecture dependent plugins
mkdir -p 
/<>/netdata-1.11.1+dfsg/debian/netdata-core/usr/lib/netdata/plugins.d
for plugin in cgroup-network apps.plugin freeipmi.plugin; \
do \
mv 
/<>/netdata-1.11.1+dfsg/debian/netdata-plugins-bash/usr/lib/netdata/plugins.d/${plugin}
 \
   
/<>/netdata-1.11.1+dfsg/debian/netdata-core/usr/lib/netdata/plugins.d;
 \
done
mv: cannot stat 
'/<>/netdata-1.11.1+dfsg/debian/netdata-plugins-bash/usr/lib/netdata/plugins.d/cgroup-network':
 No such file or directory
mv: cannot stat 
'/<>/netdata-1.11.1+dfsg/debian/netdata-plugins-bash/usr/lib/netdata/plugins.d/apps.plugin':
 No such file or directory
mv: cannot stat 
'/<>/netdata-1.11.1+dfsg/debian/netdata-plugins-bash/usr/lib/netdata/plugins.d/freeipmi.plugin':
 No such file or directory
make[1]: *** [debian/rules:91: override_dh_install] Error 1


The bug exists also in amd64 with
  dpkg-buildpackage -B

Bug#920838: libredberry-pipe-java: pom generates unfulfillable dependency

[Adrian Bunk]

Package: libredberry-pipe-java
Version: 1.0.0~alpha0-1
Severity: serious

The following packages have unmet dependencies:
 libmilib-java : Depends: libredberry-pipe-java (>= 1.0.0-alpha0) but 
1.0.0~alpha0-1 is to be installed


1.0.0~alpha0 < 1.0.0-alpha0

Processed: libmilib-java is uninstallable and will need rebuild with fixed libredberry-pipe-java

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 920838
Bug #920839 [libmilib-java] libmilib-java is uninstallable and will need 
rebuild with fixed libredberry-pipe-java
920839 was not blocked by any bugs.
920839 was not blocking any bugs.
Added blocking bug(s) of 920839: 920838

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

Bug#920839: libmilib-java is uninstallable and will need rebuild with fixed libredberry-pipe-java

[Adrian Bunk]

Package: libmilib-java
Version: 1.9-1
Severity: serious
Control: block -1 by 920838

Since binNMUs are not possible for binary-all
this will require a maintainer upload.

Bug#920227: Bug #920227 in sbuild marked as pending

[Johannes 'josch' Schauer]

Control: tag -1 pending

Hello,

Bug #920227 in sbuild reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/sbuild/commit/97030b80674f723d227f46510dab7d5ef36d2735


fix syntax of generated Sources.gz files (Closes: #920227)

The rewrite of dpkg-scan* performed to fix #909847 introduced a
problem in 18f423619c176471d2adaafb7742cb204951a10c: Sources.gz
entries are not correctly separated by a newline. Furthermore, they
have Source: entries instead of Package:

This confuses older version of APT (previous to jessie) which have
extra sanity checks on the contents of those files, which breaks
building in older chroots.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/920227

Processed: Bug #920227 in sbuild marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #920227 [sbuild] invalid file format generated for dependencies
Added tag(s) pending.

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

Processed: node-react-audio-player build depends on node-react that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 914462
Bug #920844 [src:node-react-audio-player] node-react-audio-player build depends 
on node-react that is currently not in buster
920844 was not blocked by any bugs.
920844 was not blocking any bugs.
Added blocking bug(s) of 920844: 914462

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

Bug#920844: node-react-audio-player build depends on node-react that is currently not in buster

[Adrian Bunk]

Source: node-react-audio-player
Version: 0.11.0-1
Severity: serious
Tags: ftbfs
Control: block -1 by 914462

node-react-audio-player build depends on node-react
that is currently not in buster due to #914462.

Bug#919291: marked as done (crash: invalid kernel virtual address / crash: cannot allocate any more memory!)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 19:49:11 +
with message-id 
and subject line Bug#919291: fixed in crash 7.2.5-1
has caused the Debian Bug report #919291,
regarding crash: invalid kernel virtual address / crash: cannot allocate any 
more memory!
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.)


-- 
919291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: crash
Version: 7.2.3+real-2
Severity: normal
Tags: upstream

Dear Maintainer,

I experienced a crash with kdump-tools installed and wanted to
report that crash (#919290).
I tried to have a look at the collected core and found that crash
gives an error message and exits (see below).

This seems to be caused by recent changes in the current 4.19 series.
As it looks like this may get the next stable kernel it would
be nice if crash could analyze cores from that kernel.

Upstream seem to have some fixes for 4.19 kernels [1].

I made a local build with [2] and [3] applied,
and it did not fail anymore.

Kind regards,
Bernhard


[1] https://people.redhat.com/anderson/crash.changelog.html
[2] 
https://github.com/crash-utility/crash/commit/d7eec45d4c2cdd836ce48a81b0ae688a7d2879ba
[3] 
https://github.com/crash-utility/crash/commit/001f77a05585c15ebd14bb72d5fde314a63c06fe


Output of failing "crash":

$ crash /usr/lib/debug/lib/modules/4.19.0-1-amd64/vmlinux 
/var/crash/201901141532/dump.201901141532

crash 7.2.3
Copyright (C) 2002-2017  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.

GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...

WARNING: kernel relocated [126MB]: patching 81344 gdb minimal_symbol values

please wait... (gathering module symbol data)  
crash: invalid kernel virtual address: 68fb10  type: "module symbol 
strings"
buf_1K_used: 466
buf_2K_used: 1
buf_4K_used: 1
buf_8K_used: 0
buf_32K_used: 3
buf_1K_ovf: 0
buf_2K_ovf: 0
buf_4K_ovf: 0
buf_8K_ovf: 0
buf_32K_ovf: 0
buf_1K_maxuse:  2 of 10
buf_2K_maxuse:  1 of 10
buf_4K_maxuse:  1 of 5
buf_8K_maxuse:  0 of 5
buf_32K_maxuse:  1 of 1
buf_inuse[5]: [3][0][0][0][0]
smallest: 32
largest: 7483468619598196139
embedded: 3
max_embedded: 3
mallocs: 2
frees: 2
reqs/total: 474/7483468636778302464
average size: 15787908516409920

crash: cannot allocate any more memory!



Local rebuild:

mkdir /tmp/source/crash/orig -p
cd/tmp/source/crash/orig
apt source crash
cd


cd /tmp/source/crash
cp orig try1 -a
cd try1/crash-7.2.3+real/
wget 
https://github.com/crash-utility/crash/commit/d7eec45d4c2cdd836ce48a81b0ae688a7d2879ba.patch
 -O debian/patches/d7eec45d4c2cdd836ce48a81b0ae688a7d2879ba.patch
wget 
https://github.com/crash-utility/crash/commit/001f77a05585c15ebd14bb72d5fde314a63c06fe.patch
 -O debian/patches/001f77a05585c15ebd14bb72d5fde314a63c06fe.patch
echo d7eec45d4c2cdd836ce48a81b0ae688a7d2879ba.patch >> debian/patches/series
echo 001f77a05585c15ebd14bb72d5fde314a63c06fe.patch >> debian/patches/series
quilt push -f
# d7eec45d4c2cdd836ce48a81b0ae688a7d2879ba.patch does not apply cleanly ...
quilt refresh
quilt push
quilt refresh
dch --local bernhard "+4.19-fixes"

export PKG="binutils-dev liblzo2-dev libsnappy-dev"; apt install $PKG; 
apt-mark auto $PKG

dpkg-buildpackage


dpkg -i crash_7.2.3+real-2bernhard1_amd64.deb




-- System Information:
Deb

Processed: severity of 920720 is serious

[Debian Bug Tracking System]

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

> severity 920720 serious
Bug #920720 [amavisd-new] Regession: Fix unescaped left brace in regex makes 
amavid-new unusable
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 920811

[Debian Bug Tracking System]

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

> tags 920811 + buster sid
Bug #920811 [wfrog] wfrog: Depends on removed pygooglechart
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 917615

[Debian Bug Tracking System]

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

> tags 917615 + buster sid
Bug #917615 [ruby-zoom] ruby-zoom: Please Build-Depend on libyaz-dev
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#920849: libsbml5-dev: broken symlink: /usr/lib/libsbml.so -> libsbml.so.5

[Andreas Beckmann]

Package: libsbml5-dev
Version: 5.17.2+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m27.4s ERROR: FAIL: Broken symlinks:
  /usr/lib/libsbml.so -> libsbml.so.5 (libsbml5-dev)


Has the package been multiarchified recently?


cheers,

Andreas


libsbml5-dev_5.17.2+dfsg-2.log.gz
Description: application/gzip

Processed: user debian...@lists.debian.org, usertagging 849574, tagging 896197, usertagging 913253 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 849574 piuparts
There were no usertags set.
Usertags are now: piuparts.
> tags 896197 + jessie stretch buster sid
Bug #896197 {Done: Debian FTP Masters } 
[python-formalchemy] python-formalchemy: formalchemy fails to import
Added tag(s) sid, stretch, buster, and jessie.
> usertags 913253 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 913253 + libgap-sage-4
Bug #913253 [src:libgap-sage] libgap-sage build depends on gap (< 4r8p9) but 
4r9p3-2 is to be installed
Added indication that 913253 affects libgap-sage-4
> usertags 888321 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 888321 + libguac-client-rdp0
Bug #888321 [src:guacamole-server] guacamole-server: migrate to freerdp2
Bug #900447 [src:guacamole-server] Build against freerdp2
Added indication that 888321 affects libguac-client-rdp0
Added indication that 900447 affects libguac-client-rdp0
> usertags 889557 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 917754 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 917754 0.9.0-1
Bug #917754 [src:statsmodels] statsmodels: FTBFS: Could not import extension 
matplotlib.sphinxext.only_directives (exception: No module named 
'matplotlib.sphinxext.only_directives')
Marked as found in versions statsmodels/0.9.0-1.
> found 919085 1.3~pre2019019-g8f7e128-1~exp2
Bug #919085 [src:ruby-eventmachine] ruby-eventmachine: FTBFS with testsuite 
failures
Marked as found in versions ruby-eventmachine/1.3~pre2019019-g8f7e128-1~exp2.
> found 857680 1:8~+rc1-1~exp1
Bug #857680 [llvm-6.0-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
There is no source info for the package 'llvm-6.0-examples' at version 
'1:8~+rc1-1~exp1' with architecture ''
Unable to make a source version for version '1:8~+rc1-1~exp1'
Marked as found in versions 1:8~+rc1-1~exp1.
> usertags 906730 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 920571 6.0.10-4
Bug #920571 [src:zorp] Should this package be removed?
Marked as found in versions zorp/6.0.10-4.
> found 919973 1.11.1+dfsg-2~bpo9+1
Bug #919973 {Done: Daniel Baumann } 
[netdata] netdata: fails to install: useradd: group netdata exists - if you 
want to add this user to that group, use -g.
Marked as found in versions netdata/1.11.1+dfsg-2~bpo9+1.
> found 919973 1.11.1+dfsg-2
Bug #919973 {Done: Daniel Baumann } 
[netdata] netdata: fails to install: useradd: group netdata exists - if you 
want to add this user to that group, use -g.
Marked as found in versions netdata/1.11.1+dfsg-2.
> usertags 917905 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 919805 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 919805 + redmine-pgsql
Bug #919805 [src:redmine] redmine: FTBFS (Could not find gem mail)
Added indication that 919805 affects redmine-pgsql
> usertags 919028 piuparts
There were no usertags set.
Usertags are now: piuparts.
> severity 919028 serious
Bug #919028 [chrome-gnome-shell] chrome-gnome-shell: postinst fails on 
reconfigure or if json already exists
Severity set to 'serious' from 'normal'
> found 852125 0.13-3
Bug #852125 [nodm] nodm: purging leaves leaves dangling 
/etc/systemd/system/display-manager.service symlink
Marked as found in versions nodm/0.13-3.
> found 905516 17
Bug #905516 [openstack-cluster-installer-poc] openstack-cluster-installer-poc: 
unowned directories after purge: 
/var/lib/openstack-cluster-installer-poc/{runtime,templates}/
Marked as found in versions openstack-cluster-installer/17.
> usertags 920606 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 907489 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 920697 1.11.1+dfsg-4
Bug #920697 [netdata] netdata: logrotate exits with error after package removal
Marked as found in versions netdata/1.11.1+dfsg-4.
> usertags 909344 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 857954 2:1.02.155-1
Bug #857954 [libdevmapper-dev] libdevmapper-dev: broken symlink: 
/usr/lib//libdevmapper-event-lvm2.so -> 
/lib//libdevmapper-event-lvm2.so.2.02
Ignoring request to alter found versions of bug #857954 to the same values 
previously set
> found 857776 1:0.9.3.1-1
Bug #857776 [libgtkdatabox-dev] libgtkdatabox-dev: broken symlink: 
/usr/share/gtk-doc/html/gtkdatabox -> ../../doc/libgtkdatabox-dev/html
Marked as found in versions libgtkdatabox/1:0.9.3.1-1.
> found 857653 liblld-6.0/1:6.0.1-10
Bug #857653 [liblld-6.0] liblld-4.0: missing liblld-4.0.so.1
The source liblld-6.0 and version 1:6.0.1-10 do not appear to match any binary 
packages
Marked as found in versions liblld-6.0/1:6.0.1-10.
> found 857518 3.4-1
Bug #857518 [carbon-c-relay] carbon-c-r

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 920408 src:mate-utils
Bug #920408 [mate-utils] mate-utils: Dependency problem
Bug reassigned from package 'mate-utils' to 'src:mate-utils'.
No longer marked as found in versions mate-utils/1.20.2-2.
Ignoring request to alter fixed versions of bug #920408 to the same values 
previously set
> forcemerge 919058 920408
Bug #919058 [src:mate-utils] mate-utils: frequent parallel FTBFS
Bug #920408 [src:mate-utils] mate-utils: Dependency problem
Set Bug forwarded-to-address to 
'https://github.com/mate-desktop/mate-utils/issues/211'.
Severity set to 'serious' from 'important'
Marked as found in versions mate-utils/1.20.2-1.
Added tag(s) ftbfs.
Merged 919058 920408
> affects 919058 mate-utils
Bug #919058 [src:mate-utils] mate-utils: frequent parallel FTBFS
Bug #920408 [src:mate-utils] mate-utils: Dependency problem
Added indication that 919058 affects mate-utils
Added indication that 920408 affects mate-utils
> thanks
Stopping processing here.

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

Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

[Gilles Filippini]

Hi,

Gilles Filippini a écrit le 21/01/2019 à 16:58 :
> Hi,
> 
> On Sun, 20 Jan 2019 13:28:57 +0800 "Ying-Chun Liu (PaulLiu)"
>  wrote:
>> Santiago Vila 於 2019/1/20 上午1:35 寫道:
>>> Package: src:libjstun-java
>>> Version: 0.7.3+dfsg-1
>>> Severity: serious
>>> Tags: ftbfs
>>>
>>> Dear maintainer:
>>>
>>> I tried to build this package in buster but it failed:
>>>
>>> 
>>> [...]
>>>  debian/rules build-indep
>>> dh build-indep --with javahelper
>>>dh_update_autotools_config -i
>>>jh_linkjars -i
>>>jh_build -i
>>> find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
>>> /usr/lib/jvm/default-java/bin/javac -g -cp 
>>> /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
>>>  -d debian/_jh_build.libjstun-java -source 1.7 -target 1.7 -encoding 
>>> ISO8859-1
>>> warning: [options] bootstrap class path not set in conjunction with -source 
>>> 7
>>> Note: src/de/javawi/jstun/test/demo/ice/ICENegociator.java uses unchecked 
>>> or unsafe operations.
>>> Note: Recompile with -Xlint:unchecked for details.
>>> 1 warning
>>> find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
>>> /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
>>> /usr/share/doc/default-jdk-doc/api -link 
>>> /usr/share/doc/default-jre-headless/api -classpath 
>>> /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
>>>  -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
>>> -source 1.7
>>> Creating destination directory: "debian/_jh_build.javadoc/api/"
>>> javadoc: error - The code being documented uses packages in the unnamed 
>>> module, but the packages defined in /usr/share/doc/default-jdk-doc/api/ are 
>>> in named modules.
>>> javadoc: error - The code being documented uses packages in the unnamed 
>>> module, but the packages defined in 
>>> /usr/share/doc/default-jre-headless/api/ are in named modules.
>>> 2 errors
>>> make: *** [debian/rules:11: build-indep] Error 123
>>> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
>>> status 2
>>> 
>>>
>>> (The above is just how the builds ends and not necessarily the most 
>>> relevant part)
>>>
>>> The build was made in my autobuilder with "dpkg-buildpackage -A"
>>> and it also fails here:
>>>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjstun-java.html
>>>
>>> where you can get a full build log if you need it.
>>>
>>> If this is really a bug in one of the build-depends, please use reassign 
>>> and affects,
>>> so that this is still visible in the BTS web page for this package.
>>>
>>> Thanks.
>>>
>>
>> Hi Santiago,
>>
>> It seems to me that this line causes the problem.
>> find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0
>> /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link
>> /usr/share/doc/default-jdk-doc/api -link
>> /usr/share/doc/default-jre-headless/api -classpath
>> /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
>> -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp
>> -source 1.7
>>
>> But if remove "-link /usr/share/doc/default-jdk-doc/api -link
>> /usr/share/doc/default-jre-headless/api", then it will pass.
>>
>> I'm wondering if javahelper needs to call javadoc in different way.
> 
> I've got the very same result for #919803 affecting src:mac-widgets.

Looking at the jh_build code, the list of -link javadoc options is constructed 
from this snippet:
   CLASSPATHDOCS="`for i in $(grep-dctrl --no-field-names --show-field 
Build-Depends,Build-Depends-Indep -F source "$pkg" debian/control | tr , ' ' | 
sed 's/([^)]*)//g') ; do dpkg -L $i 2>/dev/null | grep /usr/share/doc/.*/api$; 
done | sed 's/^/-link /' | xargs`"

Then dropping default-jdk-doc from Build-Depends did the trick!

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Processed: tagging 917742

[Debian Bug Tracking System]

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

> tags 917742 + ftbfs
Bug #917742 [src:ca-cacert] ca-cacert: FTBFS: tests failed
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#920854: mariadb-10.1: FTBFS on s390x (test failure)

[Julien Cristau]

Source: mariadb-10.1
Version: 10.1.37-0+deb9u1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: affects -1 + release.debian.org security.debian.org

The mariadb-10.1 package on security.d.o doesn't build on s390x, one test fails:

> CURRENT_TEST: unit.pcre_test
> 
> PCRE C library tests using test data from /<>/pcre/testdata
> PCRE version 8.42 2018-03-20
> 
>  Testing 8-bit library 
> 
> Test 1: Main functionality (Compatible with Perl >= 5.10)
>   OK
>   OK with study
> Test 2: API, errors, internals, and non-Perl stuff (not UTF-8)
> Segmentation fault
>  
> ** Test 2 requires a lot of stack. If it has crashed with a
> ** segmentation fault, it may be that you do not have enough
> ** stack available by default. Please see the 'pcrestack' man
> ** page for a discussion of PCRE's stack usage.
> 
>  - saving '/<>/builddir/mysql-test/var/1/log/unit.pcre_test/' to 
> '/<>/builddir/mysql-test/var/log/unit.pcre_test/'
> 
> Retrying test unit.pcre_test, attempt(2/3)...
> 
> unit.pcre_test   w1 [ retry-fail ]
> Test ended at 2018-11-15 12:08:22
> 
> CURRENT_TEST: unit.pcre_test
> 
> PCRE C library tests using test data from /<>/pcre/testdata
> PCRE version 8.42 2018-03-20
> 
>  Testing 8-bit library 
> 
> Test 1: Main functionality (Compatible with Perl >= 5.10)
>   OK
>   OK with study
> Test 2: API, errors, internals, and non-Perl stuff (not UTF-8)
> Segmentation fault
>  
> ** Test 2 requires a lot of stack. If it has crashed with a
> ** segmentation fault, it may be that you do not have enough
> ** stack available by default. Please see the 'pcrestack' man
> ** page for a discussion of PCRE's stack usage.
> 
>  - saving '/<>/builddir/mysql-test/var/1/log/unit.pcre_test/' to 
> '/<>/builddir/mysql-test/var/log/unit.pcre_test/'
> 
> Test unit.pcre_test has failed 2 times, no more retries!

Apparently such failures are somehow expected, can we disable that test if not
fix it?

Cheers,
Julien

Processed: mariadb-10.1: FTBFS on s390x (test failure)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + release.debian.org security.debian.org
Bug #920854 [src:mariadb-10.1] mariadb-10.1: FTBFS on s390x (test failure)
Added indication that 920854 affects release.debian.org and security.debian.org

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

Bug#920855: mariadb-10.1: FTBFS on mips{,{,64}el}: linker failures

[Julien Cristau]

Source: mariadb-10.1
Version: 10.1.37-0+deb9u1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: affects -1 + release.debian.org security.debian.org

Hi,

The mariadb-10.1 on security.debian.org fails to build on all mipsen, with 
similar errors:

> [ 99%] Linking CXX executable explain_filename-t
> cd /<>/builddir/unittest/sql && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/explain_filename-t.dir/link.txt --verbose=1
> /usr/bin/mips-linux-gnu-g++   -g -O2 -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -pie -fPIC -Wl,-z,relro,-z,now -fstack-protector 
> --param=ssp-buffer-size=4 -DWITH_INNODB_DISALLOW_WRITES -fno-exceptions 
> -fno-rtti -O3 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing 
> -Wno-uninitialized -D_FORTIFY_SOURCE=2 -DDBUG_OFF  
> -specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now 
> CMakeFiles/explain_filename-t.dir/explain_filename-t.cc.o  -o 
> explain_filename-t  -lpthread ../../sql/libsql.a ../mytap/libmytap.a 
> ../../storage/csv/libcsv.a ../../storage/heap/libheap.a 
> ../../storage/maria/libaria.a ../../storage/myisam/libmyisam.a 
> ../../storage/myisammrg/libmyisammrg.a 
> ../../storage/perfschema/libperfschema.a ../../storage/sequence/libsequence.a 
> ../../storage/xtradb/libxtradb.a -laio 
> ../../plugin/auth_socket/libauth_socket.a ../../plugin/feedback/libfeedback.a 
> ../../plugin/userstat/libuserstat.a ../../sql/libpartition.a 
> ../../mysys/libmysys.a ../../mysys_ssl/libmysys_ssl.a ../../dbug/libdbug.a 
> ../../mysys/libmysys.a ../../mysys_ssl/libmysys_ssl.a ../../dbug/libdbug.a 
> -lz -lm ../../extra/yassl/libyassl.a ../../extra/yassl/taocrypt/libtaocrypt.a 
> ../../strings/libstrings.a ../../vio/libvio.a ../../pcre/libpcre.a -lcrypt 
> -ldl ../../wsrep/libwsrep.a -lsystemd -latomic -lpthread 
> /usr/bin/ld: ../../mysys/libmysys.a(stacktrace.c.o): undefined reference to 
> symbol '__bss_start'
> //lib/mips-linux-gnu/libselinux.so.1: error adding symbols: DSO missing from 
> command line
> collect2: error: ld returned 1 exit status

Cheers,
Julien

Processed: mariadb-10.1: FTBFS on mips{,{,64}el}: linker failures

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + release.debian.org security.debian.org
Bug #920855 [src:mariadb-10.1] mariadb-10.1: FTBFS on mips{,{,64}el}: linker 
failures
Added indication that 920855 affects release.debian.org and security.debian.org

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

Bug#920791: New libglm-dev

[Guus Sliepen]

retitle 920791 FTBFS on all non-SIMD architectures
forwarded 920791 https://github.com/g-truc/glm/issues/865
thanks

On Tue, Jan 29, 2019 at 07:50:44AM +0100, Guus Sliepen wrote:

> I cannot reproduce it either, but according to the logs it looks like it
> might be some #defines not working properly on some architectures.

The issue is that the new version of GLM conditionally adds constexpr to
some member functions where that would cause a compiler error. It so
happens that constexpr is not used on any architecture with SIMD
instructions supported by GLM, which are amd64 and arm64 as far as I can
tell.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature

Bug#920858: twitter-bootstrap4: contains generated code not included as source

[Jonas Smedegaard]

Source: twitter-bootstrap4
Version: 4.2.1+dfsg1-1
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Source package contains below  several files embedding code from
external project fileOverview Kickass, without source included.

Thanks to Xavier for noticing (although only as comment in copyright
file).


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxQws0ACgkQLHwxRsGg
ASHW+A//ZeD9o9J69NnfOMBYLDRmX7LLSFrzcBpN9UUjIpjL0gcUuvzYBBVftXea
LQKrAYwspymsSOaA9yUImVB3U812zsuZOLcB7wXOJcuMAEIRs1NM8+vkQM0n28Sp
xu1WmADBmUKOoWpwstlwYwiTAr2T82Fb1zUSDgiw/zUiOZnVZZIGBN6ei9HJBKpx
QwICTAuIVO1vovpGnrFNas4kbi0xvEQOUW5tFxo28R9gXSukEOEJWrU6EXjD4njb
xc8mxH49774VL8lmKpo/vA+aWQ29xrw4uMT1uuSIY/0LP6nU/cpYh5OBSbSrDZxo
BqLMpZIfx+sVhomP/sbCalKGJ8fsyl2bNn+nGXioXp5gTG1CUrDtHc8TT/3EI7z+
YN2tL5hnMeUvsI+sxeY0/SXB0Q5vHHPrR2FOmULdFVf52yAVivTjvyzrwOkAnTeR
RTi+K866ayM9A6bkV3n5yVaOqa9DO/WIa20LApRCZ7QDz5IpkBNKvcz92ZlaZzpG
iTy7pdxop+ynjp2bme493gdW4pxzuOw7M0OhK2h+8VX7gD9Yr9GcCozJoccHp28T
SMTS6L4NgOEWAPWYicxWwYdRRAmE90PZx7QrJWmCna0OlZJIHhv70rfxGNIHdxkK
j6uzLVcMq4X12klIh5BQlIXkGYMFJdn07Gi7AdO6KTT80Vyv8BM=
=7bXE
-END PGP SIGNATURE-

Processed: Re: Bug#920791: New libglm-dev

[Debian Bug Tracking System]

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

> retitle 920791 FTBFS on all non-SIMD architectures
Bug #920791 [libglm-dev] New libglm-dev
Changed Bug title to 'FTBFS on all non-SIMD architectures' from 'New 
libglm-dev'.
> forwarded 920791 https://github.com/g-truc/glm/issues/865
Bug #920791 [libglm-dev] FTBFS on all non-SIMD architectures
Set Bug forwarded-to-address to 'https://github.com/g-truc/glm/issues/865'.
> thanks
Stopping processing here.

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

Bug#920835: mlucas FTBFS on !amd64: test failures

[Alex Vong]

Hello Adrian Bunk,

The test log is not useful at all. I want to add a patch to enable
verbose test log and let it build again to identify the issues.

Is it possible for me to get access to porter machine or should I upload
to experimental and let buildd to build it?

Thanks for your great work in Debian!

Cheers,
Alex

Adrian Bunk  writes:

> Source: mlucas
> Version: 17.1-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/package.php?p=mlucas&suite=sid
>
> ...
> FAIL: tests/spot-check
> ==
>
> ./tests/..//mlucas: 149: exec: ./tests/../: Permission denied
> FAIL tests/spot-check (exit status: 126)
>
> FAIL: tests/self-test
> =
>
> ./tests/..//mlucas: 149: exec: ./tests/../: Permission denied
> FAIL tests/self-test (exit status: 126)
>
> FAIL: tests/fermat-test
> ===
>
> ./tests/..//mlucas: 149: exec: ./tests/../: Permission denied
> FAIL tests/fermat-test (exit status: 126)
>
> 
> Testsuite summary for Mlucas 17.1
> 
> # TOTAL: 3
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  3
> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> Please report to ewma...@aol.com
> 
> make[3]: *** [Makefile:12510: test-suite.log] Error 1


signature.asc
Description: PGP signature

Bug#920834: mlucas: FTBFS and baseline vioiation on i386

[Alex Vong]

Dear Adrian Bunk,

Regarding FTBFS, I've commented it at .

Regarding baseline vioiation on i386, the autotool build system builds 2
versions of the binary: generic-c and SSE2, and install it to
libexecdir. Then the wrapper script selects the right binary at
run-time. Does this approach satifies the current policy?

Cheers,
Alex

Adrian Bunk  writes:

> Source: mlucas
> Version: 17.1-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0
>
> ...
> gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize
> -floop-nest-optimize -fomit-frame-pointer -g -g3
> -fstack-protector-strong -fstack-clash-protection -mmitigate-rop
> -fwrapv -m32 -msse2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o
> mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o
> src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o
> src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o
> src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o
> src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o
> src/mlucas_sse2-get_fp_rnd_const.o
> src/mlucas_sse2-get_preferred_fft_radix.o src/mlucas_sse2-imul_macro.o
> src/mlucas_sse2-mers_mod_square.o src/mlucas_sse2-mi64.o
> src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o
> src/mlucas_sse2-radix1008_ditN_cy_dif1.o
> src/mlucas_sse2-radix1024_ditN_cy_dif1.o
> src/mlucas_sse2-radix104_ditN_cy_dif1.o
> src/mlucas_sse2-radix10_ditN_cy_dif1.o
> src/mlucas_sse2-radix112_ditN_cy_dif1.o
> src/mlucas_sse2-radix11_ditN_cy_dif1.o
> src/mlucas_sse2-radix120_ditN_cy_dif1.o
> src/mlucas_sse2-radix128_ditN_cy_dif1.o
> src/mlucas_sse2-radix12_ditN_cy_dif1.o
> src/mlucas_sse2-radix13_ditN_cy_dif1.o
> src/mlucas_sse2-radix144_ditN_cy_dif1.o
> src/mlucas_sse2-radix14_ditN_cy_dif1.o
> src/mlucas_sse2-radix15_ditN_cy_dif1.o
> src/mlucas_sse2-radix160_ditN_cy_dif1.o
> src/mlucas_sse2-radix16_dif_dit_pass.o
> src/mlucas_sse2-radix16_ditN_cy_dif1.o
> src/mlucas_sse2-radix16_dyadic_square.o
> src/mlucas_sse2-radix16_pairFFT_mul.o
> src/mlucas_sse2-radix16_wrapper_ini.o
> src/mlucas_sse2-radix16_wrapper_square.o
> src/mlucas_sse2-radix176_ditN_cy_dif1.o
> src/mlucas_sse2-radix18_ditN_cy_dif1.o
> src/mlucas_sse2-radix192_ditN_cy_dif1.o
> src/mlucas_sse2-radix208_ditN_cy_dif1.o
> src/mlucas_sse2-radix20_ditN_cy_dif1.o
> src/mlucas_sse2-radix224_ditN_cy_dif1.o
> src/mlucas_sse2-radix22_ditN_cy_dif1.o
> src/mlucas_sse2-radix240_ditN_cy_dif1.o
> src/mlucas_sse2-radix24_ditN_cy_dif1.o
> src/mlucas_sse2-radix256_ditN_cy_dif1.o
> src/mlucas_sse2-radix26_ditN_cy_dif1.o
> src/mlucas_sse2-radix288_ditN_cy_dif1.o
> src/mlucas_sse2-radix28_ditN_cy_dif1.o
> src/mlucas_sse2-radix30_ditN_cy_dif1.o
> src/mlucas_sse2-radix31_ditN_cy_dif1.o
> src/mlucas_sse2-radix32_dif_dit_pass.o
> src/mlucas_sse2-radix32_ditN_cy_dif1.o
> src/mlucas_sse2-radix32_dyadic_square.o
> src/mlucas_sse2-radix32_wrapper_ini.o
> src/mlucas_sse2-radix32_wrapper_square.o
> src/mlucas_sse2-radix36_ditN_cy_dif1.o
> src/mlucas_sse2-radix4032_ditN_cy_dif1.o
> src/mlucas_sse2-radix40_ditN_cy_dif1.o
> src/mlucas_sse2-radix44_ditN_cy_dif1.o
> src/mlucas_sse2-radix48_ditN_cy_dif1.o
> src/mlucas_sse2-radix512_ditN_cy_dif1.o
> src/mlucas_sse2-radix52_ditN_cy_dif1.o
> src/mlucas_sse2-radix56_ditN_cy_dif1.o
> src/mlucas_sse2-radix5_ditN_cy_dif1.o
> src/mlucas_sse2-radix60_ditN_cy_dif1.o
> src/mlucas_sse2-radix63_ditN_cy_dif1.o
> src/mlucas_sse2-radix64_ditN_cy_dif1.o
> src/mlucas_sse2-radix6_ditN_cy_dif1.o
> src/mlucas_sse2-radix72_ditN_cy_dif1.o
> src/mlucas_sse2-radix768_ditN_cy_dif1.o
> src/mlucas_sse2-radix7_ditN_cy_dif1.o
> src/mlucas_sse2-radix80_ditN_cy_dif1.o
> src/mlucas_sse2-radix88_ditN_cy_dif1.o
> src/mlucas_sse2-radix8_dif_dit_pass.o
> src/mlucas_sse2-radix8_ditN_cy_dif1.o
> src/mlucas_sse2-radix960_ditN_cy_dif1.o
> src/mlucas_sse2-radix96_ditN_cy_dif1.o
> src/mlucas_sse2-radix992_ditN_cy_dif1.o
> src/mlucas_sse2-radix9_ditN_cy_dif1.o src/mlucas_sse2-rng_isaac.o
> src/mlucas_sse2-test_fft_radix.o src/mlucas_sse2-threadpool.o
> src/mlucas_sse2-twopmodq.o src/mlucas_sse2-twopmodq100.o
> src/mlucas_sse2-twopmodq128.o src/mlucas_sse2-twopmodq128_96.o
> src/mlucas_sse2-twopmodq160.o src/mlucas_sse2-twopmodq192.o
> src/mlucas_sse2-twopmodq256.o src/mlucas_sse2-twopmodq64_test.o
> src/mlucas_sse2-twopmodq80.o src/mlucas_sse2-twopmodq96.o
> src/mlucas_sse2-types.o src/mlucas_sse2-util.o -lm
> /usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 222
> /tmp/ccxqWoW9.ltrans26.ltrans.o: in function `radix16_dyadic_square':
> :(.text+0x1213e): undefined reference to
> `SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:3685: mlucas-sse2] Error 1
>
>
> SSE i  not part of the i386 baseline.


signature.asc
Description: PGP signature