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#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=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=i386=17.1-1=1548777459=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#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

Bug#919803: marked as done (mac-widgets: FTBFS (The code being documented uses packages in the unnamed module))

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 21:47:35 +
with message-id 
and subject line Bug#919803: fixed in mac-widgets 0.10.0+svn416-dfsg1-3
has caused the Debian Bug report #919803,
regarding mac-widgets: FTBFS (The code being documented uses packages in the 
unnamed module)
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.)


-- 
919803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mac-widgets
Version: 0.10.0+svn416-dfsg1-2
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: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>/mac-widgets-0.10.0+svn416-dfsg1'
ln -s source/com com
ln -s 
/<>/mac-widgets-0.10.0+svn416-dfsg1/demo/com/explodingpixels/macwidgets/icons
 com/explodingpixels/macwidgets/icons
JAVA_HOME=/usr/lib/jvm/default-java \
CLASSPATH=/usr/share/java/forms.jar \
JH_JAR_EXTRA="com/explodingpixels/macwidgets/images 
com/explodingpixels/widgets/images com/explodingpixels/macwidgets/icons" \
jh_build mac_widgets.jar source demo
find source demo -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/forms.jar:debian/_jh_build.mac_widgets -d 
debian/_jh_build.mac_widgets -source 1.7 -target 1.7 -encoding ISO8859-1

[... snipped ...]

source/com/explodingpixels/macwidgets/WidgetColorScheme.java:28: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:37: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:19: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:28: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:37: warning - Tag 
@link: reference not found: Painter
javadoc: warning - Tag @link: reference not found: Painter
javadoc: warning - Tag @link: reference not found: Painter
javadoc: warning - Tag @link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:19: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:28: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:37: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetStandardColorScheme.java:14: 
warning - Tag @link: reference not found: Painter
javadoc: warning - Tag @link: reference not found: Painter
javadoc: warning - Tag @link: reference not found: Painter
javadoc: warning - Tag @link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:19: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:28: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/WidgetColorScheme.java:37: warning - Tag 
@link: reference not found: Painter
source/com/explodingpixels/macwidgets/plaf/HudCheckBoxUI.java:32: warning - Tag 
@link: reference not found: javax.swing.plaf.CheckBoxUI
source/com/explodingpixels/macwidgets/plaf/HudCheckBoxUI.java:40: warning - Tag 
@link: reference not found: javax.swing.plaf.CheckBoxUI
source/com/explodingpixels/macwidgets/plaf/HudCheckBoxUI.java:32: warning - Tag 
@link: reference not found: javax.swing.plaf.CheckBoxUI
source/com/explodingpixels/macwidgets/plaf/HudCheckBoxUI.java:40: warning - Tag 
@link: reference not found: javax.swing.plaf.CheckBoxUI
source/com/explodingpixels/macwidgets/plaf/HudPaintingUtils.java:156: warning - 
invalid usage of tag {@link Graphics2D) if the given
 {@link Component
source/com/explodingpixels/macwidgets/plaf/HudPaintingUtils.java:156: warning - 
invalid usage of tag {@link Graphics2D) if the given
 {@link Component
source/com/explodingpixels/macwidgets/ActivePanel.java:13: warning - Tag @link: 
reference not found: com.explodingpixels.WidgetColorScheme
source/com/explodingpixels/macwidgets/WidgetStandardColorScheme.java:14: 
warning - Tag @link: reference not found: Painter
source/com/explodingpixels/macwidgets/ActivePanel.java:13: 

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#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

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

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.

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#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:

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] 

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

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

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#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=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

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

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

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#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

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

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#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

[Santiago Vila]

On Tue, Jan 29, 2019 at 09:44:40PM +0100, Gilles Filippini wrote:

> 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!

Please note that if the package does not build when default-jdk-doc is
present, then (imo) you should probably use build-conflicts against it and
any similar package which we know makes the package to FTBFS, not just
remove it from build-depends.

(At least this is what build-conflicts was invented for).

Thanks.

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#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=i386=17.1-1=1548777459=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

Bug#896971: ghc-mod

[Clint Adams]

It appears as though ghc-mod has been deprecated in favor
of haskell-ide-engine.

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

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#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-

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=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#920862: xorg: Input doesn't work on LTSP clients while X is running, works otherwise

[Lasse Flygenring-Harrsen]

Package: xorg
Version: 1:7.7+19
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I have been running a Fat-client LTSP (pxe network booted clients getting their 
software from NBD on a server) system at the school were i work
for a couple of months, however recently input stopped working an all
physical hardware, the system boots fine and the Displaymanager (LDM in
my case) works fine except for the fact that keyboard and mouse input
doesn't work. I have managed to get to a shell on the machines and in
text mode TTY's keyboard input works fine and i have confirmed that
both mouse and keyboard is being detected with lsusb. I also tried
starting KDE with startkde, and X seems to work fine there as well except
for the lack of keyboard input, same with xinit and xterm. I have also tried 
PS/2 input on the
machines with the same results. The weirdest
thing however is that virtual machines that boot from the same server do
work, both with KVM and VirtualBox that are configured to simulate USB inputs. 
I have
included the contents of /var/log/Xorg.0.log from one of the affected
physical computers below. The problem seems to affect both the stable
and testing branch, I have tried reinstallintg with both. With the same
results.  
i

 /var/log/Xorg.0.log 
[  1356.849] 
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[  1356.849] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[  1356.849] Current Operating System: Linux ltsp982 4.18.0-1-amd64 #1 SMP 
Debian 4.18.6-1 (2018-09-06) x86_64
[  1356.849] Kernel command line: BOOT_IMAGE=vmlinuz-4.18.0-1-amd64 ro 
initrd=initrd.img-4.18.0-1-amd64 init=/sbin/init-ltsp quiet root=/dev/nbd0 
BOOTIF=01-2c-fd-a1-e2-9f-70
[  1356.849] Build Date: 25 October 2018  06:15:23PM
[  1356.849] xorg-server 2:1.20.3-1 (https://www.debian.org/support) 
[  1356.849] Current version of pixman: 0.36.0
[  1356.849]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1356.849] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1356.849] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 29 19:31:33 
2019
[  1356.849] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1356.850] (==) No Layout section.  Using the first Screen section.
[  1356.850] (==) No screen section available. Using defaults.
[  1356.850] (**) |-->Screen "Default Screen Section" (0)
[  1356.850] (**) |   |-->Monitor ""
[  1356.850] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  1356.850] (==) Automatically adding devices
[  1356.850] (==) Automatically enabling devices
[  1356.850] (==) Automatically adding GPU devices
[  1356.850] (==) Max clients allowed: 256, resource mask: 0x1f
[  1356.850] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  1356.850]Entry deleted from font path.
[  1356.850] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  1356.850] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1356.850] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  1356.850] (II) Loader magic: 0x55d74ed61e20
[  1356.850] (II) Module ABI versions:
[  1356.850]X.Org ANSI C Emulation: 0.4
[  1356.850]X.Org Video Driver: 24.0
[  1356.850]X.Org XInput driver : 24.1
[  1356.850]X.Org Server Extension : 10.0
[  1356.851] (--) using VT number 2

[  1356.851] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[  1356.853] (--) PCI:*(9@0:0:0) 1002:15dd:1002:15dd rev 198, Mem @ 
0xe000/268435456, 0xf000/2097152, 0xfe50/524288, I/O @ 
0xe000/256, BIOS @ 0x/131072
[  1356.853] (II) LoadModule: "glx"
[  1356.853] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1356.854] (II) Module glx: vendor="X.Org Foundation"
[  1356.854]compiled for 1.20.3, module version = 1.0.0
[  1356.854]ABI class: X.Org Server Extension, version 10.0
[  1356.854] (==) Matched ati as autoconfigured driver 0
[  1356.854] (==) Matched modesetting as autoconfigured driver 1
[  1356.854] (==) Matched fbdev as autoconfigured driver 2
[  1356.854] (==) Matched vesa as autoconfigured driver 3
[  1356.854] (==) Assigned the driver to the xf86ConfigLayout
[  1356.854] (II) LoadModule: "ati"
[  1356.854] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[  1356.854] (II) Module ati: vendor="X.Org Foundation"
[  1356.854]compiled for 1.20.1, 

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

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#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=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

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

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

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#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 

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.

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=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 ---

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#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

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 
> 

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.

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

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

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

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

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

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#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#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

[Santiago Vila]

On Tue, Jan 29, 2019 at 11:00:25PM +0100, Gilles Filippini wrote:

> No, this is a misunderstanding: the code snippet above scans
> Build-Depends* fields from debian/control. If default-jdk-doc is
> installed but not referenced in Build-Depends*, then the package will
> build fine. I've tested this configuration.

Ah, yes, I see it now.

Simple question: Is this solution (dropping default-jdk-doc from
build-depends) valid in general for all the packages failing in a
similar way? (Do other packages have the same construct which scans
debian/control?).

(I started to report them, then I stopped when I was told there was a
common cause, then I was told each package was to be fixed separately,
and I suspect there are still a bunch of packages to be reported).

Thanks a lot.

Bug#918972: marked as done (/var/lib/libtss2-udev/tss: No such file or directory.)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 23:49:53 +
with message-id 
and subject line Bug#918972: fixed in tpm2-tss 2.1.0-4
has caused the Debian Bug report #918972,
regarding /var/lib/libtss2-udev/tss: No such file or directory.
to be marked as done.

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

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


-- 
918972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtss2-udev
Version: 2.1.0-3
Severity: serious

Hi,

On upgrade, I get the following warning:

Attention ! Impossible d'accéder au répertoire personnel que vous avez indiqué 
(/var/lib/libtss2-udev/tss) : No such file or directory.

Apparently the home directory is not existing

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages libtss2-udev depends on:
ii  adduser  3.118

libtss2-udev recommends no packages.

libtss2-udev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tpm2-tss
Source-Version: 2.1.0-4

We believe that the bug you reported is fixed in the latest version of
tpm2-tss, 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.
Ying-Chun Liu (PaulLiu)  (supplier of updated tpm2-tss 
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: Wed, 30 Jan 2019 07:22:12 +0800
Source: tpm2-tss
Binary: libtss2-dev libtss2-esys0 libtss2-esys0-dbgsym libtss2-udev
Architecture: source amd64 all
Version: 2.1.0-4
Distribution: unstable
Urgency: low
Maintainer: Mathieu Trudel-Lapierre 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 libtss2-dev - TPM2 Software stack library - development files
 libtss2-esys0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-udev - TPM2 Software stack library - udev files
Closes: 918972
Changes:
 tpm2-tss (2.1.0-4) unstable; urgency=low
 .
   * Change tss user home directory to /var/lib/tpm.
 - Tries to comply with trousers mentioned in #918979
   * Add empty var/lib/tpm directory (Closes: #918972)
Checksums-Sha1:
 ce1cdee8f1c6ae92fe587778f261076a3d6d 2076 tpm2-tss_2.1.0-4.dsc
 53f5fe6efe5b96e4b7befe4c5d4c9dbd918077e1 8372 tpm2-tss_2.1.0-4.debian.tar.xz
 75c88e6b0d89ebe14fb51666cc367930e23e0b07 55912 libtss2-dev_2.1.0-4_amd64.deb
 f074fabc8b14deb34de266ee7283c3499e86cb7e 1039136 
libtss2-esys0-dbgsym_2.1.0-4_amd64.deb
 9ac99a79f3cf393d8f9bf29426961ae5c3d05d1d 229976 libtss2-esys0_2.1.0-4_amd64.deb
 c99f9f5f34ac45e5bfb6d48f7ebf8d1290f1af65 16712 libtss2-udev_2.1.0-4_all.deb
 b4dfad86623836a7a1f5dfc5741b312dcf3a4345 6986 tpm2-tss_2.1.0-4_amd64.buildinfo
Checksums-Sha256:
 aa6c0e341da65271dc33770336861ea7dc38e7196bfa48378eea2cb814161f1e 2076 
tpm2-tss_2.1.0-4.dsc
 c19254100daf0e1f27cc6ad73dea995b475536df6161db3e9f6a6fbafc533a4c 8372 
tpm2-tss_2.1.0-4.debian.tar.xz
 85989069f9ba7aaadec3803ec565a1ebcde3b18c4c6989bbc9ea7fd657cb504f 55912 
libtss2-dev_2.1.0-4_amd64.deb
 214eda76fff8f9ed1739bc4a697e3649642006c2ed1187c1a2f826e781c7fa03 1039136 
libtss2-esys0-dbgsym_2.1.0-4_amd64.deb
 f4913c712cf046df7c19b68e6eb3b01b8398823129f22c88d663a5e56f1ea13e 229976 
libtss2-esys0_2.1.0-4_amd64.deb
 ff01bacc20f8c2620639896e6ea202753e41897d0af91ed82facff66d10264fa 16712 
libtss2-udev_2.1.0-4_all.deb
 4cb7bf99b021f09b63ee409fa0b74514853f01d1529a46e7beed0b7e3aad004c 6986 
tpm2-tss_2.1.0-4_amd64.buildinfo
Files:
 f29be633dd63ca44d0aa8220778e68c0 2076 libs optional tpm2-tss_2.1.0-4.dsc
 4225aed0d0500e53717e891299ec7b2b 8372 libs optional 
tpm2-tss_2.1.0-4.debian.tar.xz
 f83c8529237749a25c3c2f3664e30b3a 55912 libdevel optional 

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

[Markus Koschany]

Am 29.01.19 um 23:09 schrieb Santiago Vila:
> On Tue, Jan 29, 2019 at 11:00:25PM +0100, Gilles Filippini wrote:
> 
>> No, this is a misunderstanding: the code snippet above scans
>> Build-Depends* fields from debian/control. If default-jdk-doc is
>> installed but not referenced in Build-Depends*, then the package will
>> build fine. I've tested this configuration.
> 
> Ah, yes, I see it now.
> 
> Simple question: Is this solution (dropping default-jdk-doc from
> build-depends) valid in general for all the packages failing in a
> similar way? (Do other packages have the same construct which scans
> debian/control?).
> 
> (I started to report them, then I stopped when I was told there was a
> common cause, then I was told each package was to be fixed separately,
> and I suspect there are still a bunch of packages to be reported).
> 
> Thanks a lot.

I think this is a Debian Java toolchain issue and we should not fix this
at the package level. The latest OpenJDK 11 release introduced a change
that broke javadoc generation. We should discuss this on
debian-j...@lists.debian.org. Tony Mancill already provided some hints
for Maven based packages. [1] Javahelper based packaged could be
salvaged as well. Please do not try to fix this individually but engage
in a general solution.

Regards,

Markus

[1] https://lists.debian.org/debian-java/2019/01/msg00049.html



signature.asc
Description: OpenPGP digital signature

Processed: severity of 917160 is grave

[Debian Bug Tracking System]

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

> severity 917160 grave
Bug #917160 [src:nagios4] nagios4: CVE-2018-13441 CVE-2018-13457 CVE-2018-13458
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#919196: marked as done (gloox: FTBFS (autobuilder hangs))

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 23:05:08 +
with message-id 
and subject line Bug#919196: fixed in gloox 1.0.22-0.1
has caused the Debian Bug report #919196,
regarding gloox: FTBFS (autobuilder hangs)
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.)


-- 
919196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gloox
Version: 1.0.20-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but at the end my autobuilder hangs:


[...]
 debian/rules build-indep
dh build-indep 
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
libtoolize: 'AC_PROG_RANLIB' is rendered obsolete by 'LT_INIT'
configure.ac:7: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are 
deprecated.  For more info, see:
configure.ac:7: 
https://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.ac:21: installing './compile'
configure.ac:7: installing './missing'

[... snipped ...]

InBandBytestream: OK
IOData: OK
IQ: OK
JID: OK
Jingle::ICEUDP: OK
Jingle::Session: OK
Jingle::Session::Jingle: OK
Jingle::SessionManager: OK
LastActivity: OK
LastActivity::Query: OK
MD5: OK
Message: OK
MessageEventFilter: OK
MUCRoom::MUC: OK
MUCRoom::MUCAdmin: OK
MUCRoom::MUCOwner: OK
MUCRoom::MUCUser: OK
Nickname: OK
NonSaslAuth::Query: OK
NonSaslAuth: OK
OOB: OK
Parser: OK
Prep: OK
Presence: OK
PrivacyManager: OK
InBandBytestream::IBB: OK
PrivateXML: OK
PubSub::Manager::PubSub: OK
PubSub::Manager: OK
PubSub::Event: OK
Receipt: OK
Registration::Query: OK
Registration: OK
RosterManager::Query: OK
RosterManager: OK
Search::Query: OK
Search: OK
SHA: OK
SHIM: OK
SIManager: OK
SIManager::SI: OK
StanzaExtensionFactory: OK
Subscription: OK
Tag: OK
GnuTLS error: One of the involved algorithms has insufficient security level.
test 'anon client/server handshake test' failed
E: Build killed with signal TERM after 60 minutes of inactivity


This is just how the build ends. Full log here:

https://people.debian.org/~sanvila/build-logs/gloox/

The hang also happens here:

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

so it seems to be a general problem.

In case it helps, this started to happen in buster somewhere between 2018-12-26 
and 2019-01-12
according to my own build history:

Status: successful  gloox_1.0.20-2_amd64-20181226T092208.290Z
Status: failed  gloox_1.0.20-2_amd64-20190112T150338.760Z

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.
--- End Message ---
--- Begin Message ---
Source: gloox
Source-Version: 1.0.22-0.1

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated gloox 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, 22 Jan 2019 02:32:21 +0100
Source: gloox
Binary: libgloox-dev libgloox17 libgloox-dbg libgloox-doc
Architecture: source amd64 all
Version: 1.0.22-0.1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Cheng 
Changed-By: Pierre-Elliott Bécue 
Description:
 libgloox-dbg - C++ jabber/xmpp library (debug symbols)
 libgloox-dev - C++ jabber/xmpp library (devel)
 libgloox-doc - C++ jabber/xmpp library (API documentation)
 libgloox17 - C++ jabber/xmpp library
Closes: 919196
Changes:
 gloox (1.0.22-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Pierre-Elliott Bécue ]
   * New upstream 

Processed: tagging 917754, tagging 919802, tagging 785990, found 920817 in 0.1.1-5, found 920818 in 6.4.3-4 ...

[Debian Bug Tracking System]

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

> tags 917754 + experimental
Bug #917754 [src:statsmodels] statsmodels: FTBFS: Could not import extension 
matplotlib.sphinxext.only_directives (exception: No module named 
'matplotlib.sphinxext.only_directives')
Added tag(s) experimental.
> tags 919802 + sid buster
Bug #919802 [src:libjstun-java] libjstun-java: FTBFS (The code being documented 
uses packages in the unnamed module)
Added tag(s) buster and sid.
> tags 785990 + stretch buster sid
Bug #785990 {Done: Andreas Beckmann } [src:distcc] distcc: 
deprecation of python-support
Added tag(s) sid, stretch, and buster.
> found 920817 0.1.1-5
Bug #920817 [fsgateway] Should this package be removed?
Marked as found in versions fsgateway/0.1.1-5.
> found 920818 6.4.3-4
Bug #920818 [src:mysql-connector-net] Should this package be removed?
Marked as found in versions mysql-connector-net/6.4.3-4.
> tags 920818 + sid buster
Bug #920818 [src:mysql-connector-net] Should this package be removed?
Added tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
785990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785990
917754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917754
919802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919802
920817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920817
920818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920818
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]

Santiago Vila a écrit le 29/01/2019 à 22:55 :
> On Tue, Jan 29, 2019 at 09:44:40PM +0100, Gilles Filippini wrote:
> 
>> 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!
> 
> Please note that if the package does not build when default-jdk-doc is
> present, then (imo) you should probably use build-conflicts against it and
> any similar package which we know makes the package to FTBFS, not just
> remove it from build-depends.
> 
> (At least this is what build-conflicts was invented for).

No, this is a misunderstanding: the code snippet above scans
Build-Depends* fields from debian/control. If default-jdk-doc is
installed but not referenced in Build-Depends*, then the package will
build fine. I've tested this configuration.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#920220: marked as done (apache2: CVE-2019-0190: mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 23:19:31 +
with message-id 
and subject line Bug#920220: fixed in apache2 2.4.38-1
has caused the Debian Bug report #920220,
regarding apache2: CVE-2019-0190: mod_ssl 2.4.37 remote DoS when used with 
OpenSSL 1.1.1
to be marked as done.

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

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


-- 
920220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apache2
Version: 2.4.37-1
Severity: grave
Tags: patch security upstream

Hi (Stefan),

I agree the severity is not the best choosen one for this issue, it is
more to ensure we could release buster with an appropriate fix already
before the release. If you disagree, please do downgrade.

The following vulnerability was published for apache2.

CVE-2019-0190[0]:
mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1

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-0190
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0190
[1] https://marc.info/?l=oss-security=154817901921421=2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.38-1

We believe that the bug you reported is fixed in the latest version of
apache2, 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 apache2 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 23:49:49 +0100
Source: apache2
Binary: apache2 apache2-bin apache2-bin-dbgsym apache2-data apache2-dev 
apache2-doc apache2-ssl-dev apache2-suexec-custom apache2-suexec-custom-dbgsym 
apache2-suexec-pristine apache2-suexec-pristine-dbgsym apache2-utils 
apache2-utils-dbgsym libapache2-mod-md libapache2-mod-proxy-uwsgi
Architecture: source
Version: 2.4.38-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Xavier Guimard 
Closes: 880993 920220 920302 920303
Description: 
 apache2- Apache HTTP Server
 apache2-bin - Apache HTTP Server (modules and other binary files)
 apache2-data - Apache HTTP Server (common files)
 apache2-dev - Apache HTTP Server (development headers)
 apache2-doc - Apache HTTP Server (on-site documentation)
 apache2-ssl-dev - Apache HTTP Server (mod_ssl development headers)
 apache2-suexec-custom - Apache HTTP Server configurable suexec program for 
mod_suexec
 apache2-suexec-pristine - Apache HTTP Server standard suexec program for 
mod_suexec
 apache2-utils - Apache HTTP Server (utility programs for web servers)
 libapache2-mod-md - transitional package
 libapache2-mod-proxy-uwsgi - transitional package
Changes:
 apache2 (2.4.38-1) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Reverted for now: Transition to automatic debug package (from: apache2-dbg)
   * Trim trailing whitespace
   * Use secure copyright file specification URI
 .
   [ Niels Thykier ]
   * Add Rules-Requires-Root: binary-targets
 .
   [ Xavier Guimard ]
   * Convert signing-key.pgp into signing-key.asc
   * Add http2.conf (Closes: #880993)
   * Remove unnecessary greater-than versioned dependency to dpkg-dev,
 libbrotli-dev and libapache2-mod-md
   * Declare compliance with policy 4.2.1
   * Add spelling errors patch (reported)
   * Fix some spelling errors in debian files
   * Add myself to uploaders
   * Refresh patches
   * Bump debhelper compatibility level to 10
   * debian/rules:
 - Remove unnecessary dh argument --parallel
 - use /usr/share/dpkg/pkg-info.mk instead of dpkg-parsechangelog
   * Add upstream/metadata
   * Replace MIT by Expat in debian/copyright
   * debian/watch: use https url
   * Add documentation links in systemd service files
   * Team upload
 .
   [ Cyrille Bollu ]
   * Put HTTP2 configuration within  tags as
 it gets automatically de-activated upon apache 'startup when using
 mpm_prefork.
  

Bug#896025: marked as done (python-mne FTBFS with python-matplotlib 2.2.2-1)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2019 23:01:26 +0100
with message-id <20190129220126.aove2hpvn3h2n...@an3as.eu>
and subject line Forgot to mention bug in d/changelog
has caused the Debian Bug report #896025,
regarding python-mne FTBFS with python-matplotlib 2.2.2-1
to be marked as done.

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

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


-- 
896025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mne
Version: 0.15.2+dfsg-2
Severity: serious

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

...
=== FAILURES ===
___ [doctest] mne.viz.misc.plot_ideal_filter ___
840 .. versionadded:: 0.14
841 
842 Examples
843 
844 Plot a simple ideal band-pass filter::
845 
846 >>> from mne.viz import plot_ideal_filter
847 >>> freq = [0, 1, 40, 50]
848 >>> gain = [0, 1, 1, 0]
849 >>> plot_ideal_filter(freq, gain, flim=(0.1, 100))  #doctest: 
+ELLIPSIS
Expected:

Got:


/build/1st/python-mne-0.15.2+dfsg/mne/viz/misc.py:849: DocTestFailure
 test_plot_connectivity_circle _

def test_plot_connectivity_circle():
"""Test plotting connectivity circle
"""
import matplotlib.pyplot as plt
node_order = ['frontalpole-lh', 'parsorbitalis-lh',
  'lateralorbitofrontal-lh', 'rostralmiddlefrontal-lh',
  'medialorbitofrontal-lh', 'parstriangularis-lh',
  'rostralanteriorcingulate-lh', 'temporalpole-lh',
  'parsopercularis-lh', 'caudalanteriorcingulate-lh',
  'entorhinal-lh', 'superiorfrontal-lh', 'insula-lh',
  'caudalmiddlefrontal-lh', 'superiortemporal-lh',
  'parahippocampal-lh', 'middletemporal-lh',
  'inferiortemporal-lh', 'precentral-lh',
  'transversetemporal-lh', 'posteriorcingulate-lh',
  'fusiform-lh', 'postcentral-lh', 'bankssts-lh',
  'supramarginal-lh', 'isthmuscingulate-lh', 
'paracentral-lh',
  'lingual-lh', 'precuneus-lh', 'inferiorparietal-lh',
  'superiorparietal-lh', 'pericalcarine-lh',
  'lateraloccipital-lh', 'cuneus-lh', 'cuneus-rh',
  'lateraloccipital-rh', 'pericalcarine-rh',
  'superiorparietal-rh', 'inferiorparietal-rh', 
'precuneus-rh',
  'lingual-rh', 'paracentral-rh', 'isthmuscingulate-rh',
  'supramarginal-rh', 'bankssts-rh', 'postcentral-rh',
  'fusiform-rh', 'posteriorcingulate-rh',
  'transversetemporal-rh', 'precentral-rh',
  'inferiortemporal-rh', 'middletemporal-rh',
  'parahippocampal-rh', 'superiortemporal-rh',
  'caudalmiddlefrontal-rh', 'insula-rh', 
'superiorfrontal-rh',
  'entorhinal-rh', 'caudalanteriorcingulate-rh',
  'parsopercularis-rh', 'temporalpole-rh',
  'rostralanteriorcingulate-rh', 'parstriangularis-rh',
  'medialorbitofrontal-rh', 'rostralmiddlefrontal-rh',
  'lateralorbitofrontal-rh', 'parsorbitalis-rh',
  'frontalpole-rh']
label_names = ['bankssts-lh', 'bankssts-rh', 
'caudalanteriorcingulate-lh',
   'caudalanteriorcingulate-rh', 'caudalmiddlefrontal-lh',
   'caudalmiddlefrontal-rh', 'cuneus-lh', 'cuneus-rh',
   'entorhinal-lh', 'entorhinal-rh', 'frontalpole-lh',
   'frontalpole-rh', 'fusiform-lh', 'fusiform-rh',
   'inferiorparietal-lh', 'inferiorparietal-rh',
   'inferiortemporal-lh', 'inferiortemporal-rh', 
'insula-lh',
   'insula-rh', 'isthmuscingulate-lh', 
'isthmuscingulate-rh',
   'lateraloccipital-lh', 'lateraloccipital-rh',
   'lateralorbitofrontal-lh', 'lateralorbitofrontal-rh',
   'lingual-lh', 'lingual-rh', 'medialorbitofrontal-lh',
   'medialorbitofrontal-rh', 'middletemporal-lh',
   'middletemporal-rh', 'paracentral-lh', 'paracentral-rh',
   'parahippocampal-lh', 'parahippocampal-rh',
   

Processed: found 919139 in 0.9+nmu2

[Debian Bug Tracking System]

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

> found 919139 0.9+nmu2
Bug #919139 [cli-common] cli-common: Invalid maintainer email address
Marked as found in versions cli-common/0.9+nmu2.
> thanks
Stopping processing here.

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

Bug#920882: libpmix2: unable to open mca_pmix_ext2x: libpmix.so.2: No such file or directory

[Drew Parsons]

Package: libpmix2
Version: 3.1.2-1
Severity: grave
Justification: renders package unusable

The new version of libpmix2 is confusing client packages,
breaking CI tests in many packages, e.g. for petsc:

  run SNES testex19
  Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI 
process
  See http://www.mcs.anl.gov/petsc/documentation/faq.html
  [ci-1548795660:12338] mca_base_component_repository_open: unable to open 
mca_pmix_ext2x: libpmix.so.2: cannot open shared object file: No such file or 
directory (ignored)
  [ci-1548795660:12338] [[65452,0],0] ORTE_ERROR_LOG: Not found in file 
ess_hnp_module.c at line 325

The error references mca_pmix_ext2x which I presume means
mca_pmix_ext2x.so from libopenmpi3. Does it simply mean that openmpi
needs to be rebuilt against the new pmix?  Please reassign this bug to
libopenmpi3 if needed.

Drew

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

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

Versions of packages libpmix2 depends on:
ii  libc62.28-5
ii  libevent-2.1-6   2.1.8-stable-4
ii  libevent-pthreads-2.1-6  2.1.8-stable-4
ii  libhwloc-plugins 2.0.0-1
ii  zlib1g   1:1.2.11.dfsg-1

libpmix2 recommends no packages.

libpmix2 suggests no packages.

-- no debconf information

Processed: severity of 907297 is serious

[Debian Bug Tracking System]

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

> severity 907297 serious
Bug #907297 [breeze-gtk-theme] breeze-gtk-theme: Breaks xfce4-notes (invalid 
string constant in "/usr/share/themes/Breeze/gtk-2.0/widgets/styles")
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#920456: marked as done (i2p: modifies conffiles (policy 10.7.3): /etc/i2p/wrapper.config)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 04:50:11 +
with message-id 
and subject line Bug#920456: fixed in i2p 0.9.38-2
has caused the Debian Bug report #920456,
regarding i2p: modifies conffiles (policy 10.7.3): /etc/i2p/wrapper.config
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.)


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

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/i2p/wrapper.config


cheers,

Andreas


i2p_0.9.38-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: i2p
Source-Version: 0.9.38-2

We believe that the bug you reported is fixed in the latest version of
i2p, 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.
Masayuki Hatta  (supplier of updated i2p 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: Wed, 30 Jan 2019 13:24:34 +0900
Source: i2p
Binary: i2p i2p-doc i2p-router libjbigi-jni libjbigi-jni-dbgsym
Architecture: source all amd64
Version: 0.9.38-2
Distribution: unstable
Urgency: medium
Maintainer: Masayuki Hatta 
Changed-By: Masayuki Hatta 
Description:
 i2p- Invisible Internet Project (I2P) - anonymous network
 i2p-doc- Invisible Internet Project (I2P) - developer documentation
 i2p-router - Invisible Internet Project (I2P) - router
 libjbigi-jni - Invisible Internet Project (I2P) - libjbigi library
Closes: 920456
Changes:
 i2p (0.9.38-2) unstable; urgency=medium
 .
   * Now uses ucf for handling /etc/i2p/wrapper.config - closes: #920456
Checksums-Sha1:
 083afa4ce85708ccda4655b6c5578f243677f6b1 2194 i2p_0.9.38-2.dsc
 386476e4e801c9f4b45e70e80e7d52edf33e537e 57388 i2p_0.9.38-2.debian.tar.xz
 9b048a6d9fc7b70bd8c60024bd1c54268f310fde 3414296 i2p-doc_0.9.38-2_all.deb
 1adbf0540d679d6f03843e08845734364825e82e 9558124 i2p-router_0.9.38-2_all.deb
 226f06dc7a59ae28cc60a6b670f5fffe51215a5e 66056 i2p_0.9.38-2_all.deb
 becd5061d342a51b35fdac340b13bd6249866ade 11789 i2p_0.9.38-2_amd64.buildinfo
 4b7b466e5dcca91fb0652506c384da51f668426b 13992 
libjbigi-jni-dbgsym_0.9.38-2_amd64.deb
 dabfd7a587410e2bc64c851fc3844f7c47343a06 5100 libjbigi-jni_0.9.38-2_amd64.deb
Checksums-Sha256:
 694717e6a3adb806867cd63dcf308a9c911a82984568918e2e64a24c618efc05 2194 
i2p_0.9.38-2.dsc
 1e56e11c63f9c54042e404c120e59d1632f3d2b1a8ceb63fdbcd9fbee5a441e4 57388 
i2p_0.9.38-2.debian.tar.xz
 4381ca30ac5c7d17e2c86c6dddb8369e6d153d7c82bb81cb23bad529bcebcd0e 3414296 
i2p-doc_0.9.38-2_all.deb
 

Bug#920881: webext-debianbuttons should list firefox-esr as first dependency alternative

[Adrian Bunk]

Package: webext-debianbuttons
Version: 2.2-1
Severity: serious

* Migration status: Blocked. Can't migrate due to a non-migratable dependency. 
Check status below.
* Blocked by: firefox

The problem is:
  Depends: firefox (>= 50) | firefox-esr (>= 50)

The first alternative is special, since it is preferred
by package managers. It should therefore be the package
that is in releases.

While the practical relevance is likely close to zero
(who would install this package without already having
firefox installed?) it is easy to fix by changing the
order of the dependency alternatives.

Bug#920882: libpmix2 and Open MPI

[Ron Lovell]

The libpmix2 update causes my MPI programs compiled with
gcc/gfortran/clang  to fail at runtime with the same messages.
-- 
James Ronald Lovell 

Processed: found 917063 in 2.0.6-1

[Debian Bug Tracking System]

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

> found 917063 2.0.6-1
Bug #917063 [src:golang-gopkg-cheggaaa-pb.v2] golang-gopkg-cheggaaa-pb.v2 
FTBFS: FAIL: TestElementBar
Marked as found in versions golang-gopkg-cheggaaa-pb.v2/2.0.6-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#919818: ruby-net-ssh breaks test-kitchen autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #919818 [src:ruby-net-ssh, src:test-kitchen] ruby-net-ssh breaks 
test-kitchen autopkgtest
Severity set to 'serious' from 'normal'

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

Bug#920726: marked as done (openrocket: Depends on openjdk-8-jre which will not be in buster)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 04:04:43 +
with message-id 
and subject line Bug#920726: fixed in openrocket 15.03.5
has caused the Debian Bug report #920726,
regarding openrocket: Depends on openjdk-8-jre which will not be in buster
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.)


-- 
920726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openrocket
Version: 15.03.4
Severity: serious
Control: block 920037 with -1

Hi,

buster will ship with openjdk-11 only.


Andreas
--- End Message ---
--- Begin Message ---
Source: openrocket
Source-Version: 15.03.5

We believe that the bug you reported is fixed in the latest version of
openrocket, 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.
Bdale Garbee  (supplier of updated openrocket 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 20:36:36 -0700
Source: openrocket
Binary: openrocket
Architecture: source all
Version: 15.03.5
Distribution: unstable
Urgency: medium
Maintainer: Bdale Garbee 
Changed-By: Bdale Garbee 
Description:
 openrocket - Model Rocket Simulator
Closes: 920726
Changes:
 openrocket (15.03.5) unstable; urgency=medium
 .
   * change dependency to default-jre, closes: #920726
Checksums-Sha1:
 f9bddf2bf82cde16949309e101a809964fa183c0 1559 openrocket_15.03.5.dsc
 5d36e69b1307d0d07d2b0c5cab74704f94898bfc 9004 openrocket_15.03.5.tar.xz
 98ec0b2c5d54b4797c17c1648aab89722e49cbee 9872 openrocket_15.03.5_all.deb
 30aaa0302e14683117101c6c2da4abfd382af52f 5385 
openrocket_15.03.5_amd64.buildinfo
Checksums-Sha256:
 1d9e1a7d198009d1f71d88ce4e4ae5baa962a728cb4c0bd343b580eab9edc55d 1559 
openrocket_15.03.5.dsc
 f614bcef619ec7d133b2cc6c62e498fc4dabb32ea705e187c0fc580537b1d6ba 9004 
openrocket_15.03.5.tar.xz
 30c59b2d29efcb712321c3785e45c3febe43062d94eccbba4fbd1eb6241727fe 9872 
openrocket_15.03.5_all.deb
 1cc3e9dcc5c4db2d5974090c974282ce9d28467208012b072409033a17e91abf 5385 
openrocket_15.03.5_amd64.buildinfo
Files:
 bef036f0ce627640eb033c54494b5bb7 1559 contrib/science optional 
openrocket_15.03.5.dsc
 4741ac42a559127724ee497476063f5b 9004 contrib/science optional 
openrocket_15.03.5.tar.xz
 a4b20de03f97c26cee405ab3bc222ea9 9872 contrib/science optional 
openrocket_15.03.5_all.deb
 a567ab4ea08b8e6fe01e7907710a0dd8 5385 contrib/science optional 
openrocket_15.03.5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEhHDyCwYlkhh8unuzOpNhlsCV2UEFAlxRHGkACgkQOpNhlsCV
2UGjBRAAwfEUSWFP2YALkFfLgwcED5m/0FC+Au7/9k4eJ2BWHAn3+4rPlfd7qTRO
O/BZHltXVmy8PmEvGQ+bNvokH5WyguFKpalz1Rcqr6DKFh/T8bt82gmtEA5Qxcrw
kGn4tf1U6i9kz2sJ+v3DbjUhMo2C9o/ZcgR91wpJ8l/hk5mnHkNGBHHSJx5M3peV
ceCsVN/34+MwyN1wh/fOMZlCEdY+EmXQreALY99QMzxXuUTYb8YJdg7Z3iBaoKAn
G4WkI5fb5GBpaZ6vuI96VtbRkp7PVtGdcty26rXkxGL2dVor17yfNjrCNGb3+uXI
kkPfbSBOvweoR9YetvLxLg1szRJrRxnSyissWWcr1SvRSv7k2VCkqpN6GFznBJkN
kWx8DwXm8tFZ7T6X5kC3ApneH0HMdLyA0k05tHqsemrQxxwfQy8EaTKMiuPXuCzQ
NWsCpMUU3fXfovmDj4ZR6vI5ulQbyM+14/wxn8CYI57+gyoAzXVazCme+7QmVyM1
Cb+ZGU1SyTjPMNZF6VSJ2f8dcr9graLFA2rvgXwB4GHzerU+LdW4vFj4k+mJDBjD
BD4Dvy/YMCq2ZI/yVBunyWNTzSOtZWlWswA8JsHB6CNXXVnbjnU0ohyu0/sDxyNd
O9I/pyFAiYvpc86kPcM2Fx3sX0wMgnIa8UgjCJJBpLb/kxEmuVc=
=WLmp
-END PGP SIGNATURE End Message ---

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=919798#125

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#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]  ^
...

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

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#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=919798#125

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#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

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#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

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

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#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

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