date:20190307

Bug#923889: google-compute-image-packages - DoS via serial console write

2019-03-07 Thread Thomas Goirand

On 3/7/19 11:25 PM, Ross Vandegrift wrote:
> On Wed, Mar 06, 2019 at 07:49:38PM +0100, Bastian Blank wrote:
>> This package instructs journald to duplicate everything sent to the
>> journal to the serial console.  The serial console is a pretty rate
>> limited log output device and blocking there will make all software with
>> any log output block.
> 
> This doesn't seem to affect all software - I tried to reproduce with
> logger, but it doesn't block.  Maybe this only affects some logging
> transports?
> 
> I agree it's a problematic default - GCE serial console data is
> currently stored unencrypted.  That could be an unpleasent surprise.
> 
> Ross

Ross,

Bastian is right that what's been done is a very bad idea. I would
suggest that you the issue is taken seriously, and the change be
reverted. In many situation, the serial port wont be fast enough.

Cheers,

Thomas Goirand (zigo)

Bug#923990: marked as done (Failure: TypeError: str() argument 2 must be str, not None)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Fri, 08 Mar 2019 07:49:53 +
with message-id 
and subject line Bug#923990: fixed in dh-python 3.20190308
has caused the Debian Bug report #923990,
regarding Failure: TypeError: str() argument 2 must be str, not None
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.)


-- 
923990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-python
Version: 3.20180927
Severity: critical

(severity it's because it breaks other packages)

i just uploaded python-dmidecode, and it fails on the buildds with:

I: dh_python2 fs:343: renaming dmidecodemod.so to 
dmidecodemod.aarch64-linux-gnu.so
Traceback (most recent call last):
  File "/usr/share/dh-python/dh_python2", line 545, in 
main()
  File "/usr/share/dh-python/dh_python2", line 430, in main
stats = Scanner(interpreter, package, private_dir, options).result
  File "/usr/share/dh-python/dhpython/fs.py", line 230, in __init__
ver = self.handle_ext(fpath)
  File "/usr/share/dh-python/dh_python2", line 57, in handle_ext
so_version = so2pyver(fpath)
  File "/usr/share/dh-python/dhpython/tools.py", line 139, in so2pyver
match = SHAREDLIB_RE.search(str(process.stdout.read(), encoding=encoding))
TypeError: str() argument 2 must be str, not None
make: *** [debian/rules:11: binary-arch] Error 1

logs at 
https://buildd.debian.org/status/fetch.php?pkg=python-dmidecode=arm64=3.12.2-8=1552005709=0
shows it's using version 3.20190307, which was just uploaded today.

could you have a look please?

thanks,
Sandro

-- 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.14.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dh-python depends on:
ii  python33.7.1-3
ii  python3-distutils  3.7.1-1

dh-python recommends no packages.

Versions of packages dh-python suggests:
ii  dpkg-dev  1.19.0.4
ii  libdpkg-perl  1.19.0.4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 3.20190308

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated dh-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Mar 2019 08:23:50 +0100
Source: dh-python
Binary: dh-python
Architecture: source all
Version: 3.20190308
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Description:
 dh-python  - Debian helper tools for packaging Python libraries and applicatio
Closes: 923990
Changes:
 dh-python (3.20190308) unstable; urgency=medium
 .
   * so2pyver: add a fallback to UTF-8 if locale.getdefaultlocale() returns None
 closes: 923990
Checksums-Sha1:
 0d2486a6d04dab92ae06eccd9fd5c01293723ff7 1877 dh-python_3.20190308.dsc
 ebcf864e09285fd613e60aae298f854b9e8a6963 100408 dh-python_3.20190308.tar.xz
 40db71a651cdbf2defee16ae36c621b05044057e 99328 dh-python_3.20190308_all.deb
 48592fd157fdbf1e06f7d024f6189a91886d07bf 6281 
dh-python_3.20190308_amd64.buildinfo
Checksums-Sha256:
 9dd28d53140f65158409094894df97ce439d16232b07347ba8b37fcf96f33418 1877 
dh-python_3.20190308.dsc
 1243512e4d82811baf769e848e86586cf0bb3f3ae15a171b8495ddb33856f0c6 100408 
dh-python_3.20190308.tar.xz
 e649e5f2652123695e3579e6ee7f46d42126ea04bd1d0b3f7c10b8f79c39f188 99328 
dh-python_3.20190308_all.deb
 61c3b9a7de0cd8fea767a543d80d36277ef36782ab2009f1b2fcc401a4807aab 6281 
dh-python_3.20190308_amd64.buildinfo
Files:
 f597fd23cdc7d18714773440f0abe021 1877 python optional

Bug#923226: Compiling shader doesn't work - game doesn't work

2019-03-07 Thread Julien Puydt


Hi,

Le 07/03/2019 à 18:39, Simon McVittie a écrit :

On Thu, 07 Mar 2019 at 13:30:57 +0100, Julien Puydt wrote:

Just changing the ioquake3 binary package (which makes dpkg complain about
ioquake3-server, but it's normal):
1.36+u20181017.09166ba~dfsg-2 works
1.36+u20181222.e5da13f~dfsg-1 fails


What graphics stack are you using, in particular your kernel and Mesa
driver? Running `reportbug --template ioquake3` will summarize the most
relevant packages.

It looks as though the problem might be that your driver only provides
GLSL 1.20 (either on your hardware or in general), whereas the hitCube()
function introduced between 09166ba and e5da13f assumes GLSL 1.30
or later.



To give more information about the GL stack here, here are exerpts from 
running glxinfo:


direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4

client glx vendor string: Mesa Project and SGI
client glx version string: 1.4

GLX version: 1.4

Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Ironlake Mobile  (0x46)
Version: 18.3.4
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 18.3.4
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.3.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16


Hope that helps,

jpuydt on irc.debian.org

Bug#923226: Compiling shader doesn't work - game doesn't work

2019-03-07 Thread Julien Puydt





Le 07/03/2019 à 18:39, Simon McVittie a écrit :

On Thu, 07 Mar 2019 at 13:30:57 +0100, Julien Puydt wrote:

Just changing the ioquake3 binary package (which makes dpkg complain about
ioquake3-server, but it's normal):
1.36+u20181017.09166ba~dfsg-2 works
1.36+u20181222.e5da13f~dfsg-1 fails


What graphics stack are you using, in particular your kernel and Mesa
driver? Running `reportbug --template ioquake3` will summarize the most
relevant packages.

>

It looks as though the problem might be that your driver only provides
GLSL 1.20 (either on your hardware or in general), whereas the hitCube()
function introduced between 09166ba and e5da13f assumes GLSL 1.30
or later.


Here is what seems relevant in reportbug:

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) 


Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ioquake3 depends on:
ii  ioquake3-server  1.36+u20181222.e5da13f~dfsg-1
ii  libc62.28-8
ii  libcurl3-gnutls  7.64.0-2
ii  libgl1   1.1.0-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libogg0  1.3.2-1+b1
ii  libopenal1   1:1.19.1-1
ii  libopus0 1.3-1
ii  libopusfile0 0.9+20170913-1
ii  libsdl2-2.0-02.0.9+dfsg1-1
ii  libvorbis0a  1.3.6-2
ii  libvorbisfile3   1.3.6-2
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages ioquake3 recommends:
ii  x11-utils  7.7+4
ii  zenity 3.30.0-2

ioquake3 suggests no packages.

Versions of packages ioquake3 is related to:
ii  libgl1-mesa-dri  18.3.4-2


The following should also tell more about the graphics hardware:
# lspci -s  00:02.0 -vvv
00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])

Subsystem: Dell Latitude E6410
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 26
Region 0: Memory at f000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at e000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 70b0 [size=8]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee01004  Data: 4023
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)

Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
Kernel modules: i915


Hope that helps,

jpuydt on irc.debian.org

Bug#923541: [debian-mysql] Bug#923541: libdbd-mysql-perl: FTBFS against mariadb-10.3 1:10.3.13-1

2019-03-07 Thread Otto Kekäläinen

Thanks!

Bug#923466: marked as done (lammps: FTBFS (dh_auto_configure fails))

2019-03-07 Thread Debian Bug Tracking System

Your message dated Fri, 08 Mar 2019 07:19:50 +
with message-id 
and subject line Bug#923466: fixed in lammps 0~20181211.gitad1b1897d+dfsg1-2
has caused the Debian Bug report #923466,
regarding lammps: FTBFS (dh_auto_configure fails)
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.)


-- 
923466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lammps
Version: 0~20181211.gitad1b1897d+dfsg1-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 --sourcedirectory=cmake 
--builddirectory=/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build
   dh_update_autotools_config -i -O--sourcedirectory=cmake 
-O--builddirectory=/<>/lammps-0\~20181211.gitad1b1897d\+dfsg1/debian/build
   dh_autoreconf -i -O--sourcedirectory=cmake 
-O--builddirectory=/<>/lammps-0\~20181211.gitad1b1897d\+dfsg1/debian/build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1'
dh_auto_configure -- \
-DPKG_ASPHERE=ON \
-DPKG_BODY=ON \
-DPKG_CLASS2=ON \
-DPKG_COLLOID=ON \
-DPKG_COMPRESS=ON \
-DPKG_CORESHELL=ON \
-DPKG_DIPOLE=ON \

[... snipped ...]


Run Build Command:"/usr/bin/make" "cmTC_341b1/fast"
make[2]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_341b1.dir/build.make 
CMakeFiles/cmTC_341b1.dir/build
make[3]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_341b1.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c99 -o CMakeFiles/cmTC_341b1.dir/feature_tests.c.o  
 -c 
"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/feature_tests.c"
Linking C executable cmTC_341b1
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_341b1.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_341b1.dir/feature_tests.c.o  -o cmTC_341b1 
make[3]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:1c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record: C_FEATURE:1c_variadic_macros


Detecting C [-std=c90] compiler features compiled with the following output:
Change Dir: 
/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_2dfd2/fast"
make[2]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_2dfd2.dir/build.make 
CMakeFiles/cmTC_2dfd2.dir/build
make[3]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c90 -o CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o  
 -c 
"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/feature_tests.c"
Linking C executable cmTC_2dfd2
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2dfd2.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o  -o cmTC_2dfd2 
make[3]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:0c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record:

Bug#923457: test_likelihood_nh (Failed)

2019-03-07 Thread Andreas Tille

Hi Julien,

after fixing bug #923457 I realised that the package does not
build on all architectures[1]. S390x fails with[2]

 4/14 Test  #5: test_likelihood_nh ...***Failed2.44 sec

/ 1
- 2
\ 3
- 4
/ 5
- 6
\ 7
- 8
/ 9
- 10
\ 11 nodes loaded.
Theta0 set to 0.444785
Theta1 set to 0.137341
Theta2 set to 0.219281
Theta3 set to 0.759382
Theta4 set to 0.549516
Theta5 set to 0.925583
Theta6 set to 0.527333
Theta7 set to 0.891561
Theta8 set to 0.331932
Theta9 set to 0.523327
Initializing data structure: Done.
Number of distinct sites...: 363
Initializing data structure: Done.
Number of distinct sites...: 363

Optimizing... / 1
Optimizing... - 2
Optimizing... \ 3
Optimizing... - 4
Optimizing... / 5
Optimizing... - 6
Optimizing... \ 7
Optimizing... - 8
Optimizing... / 9
Optimizing... - 10
Optimizing... \ 11
Optimizing... - 12
Optimizing... / 13
Optimizing... - 14


Optimizing... / 1
Optimizing... - 2
Optimizing... \ 3
Optimizing... - 4
Optimizing... / 5
Optimizing... - 6
Optimizing... \ 7
Optimizing... - 8
Optimizing... / 9
Optimizing... - 10
Optimizing... \ 11
Optimizing... - 12
Optimizing... / 13
Optimizing... - 14

15: 5347.92 15: 5347.92
0.516673 0.516673
0.184681 0.184681
0.209158 0.209158
0.795359 0.795359
0.489372 0.489372
0.918414 0.918414
0.489537 0.489537
0.913968 0.913968
0.180359 0.180359
0.797456 0.797456
Initializing data structure: Done.
Number of distinct sites...: 365
Initializing data structure: Done.
Number of distinct sites...: 365

Optimizing... / 1
Optimizing... - 2
Optimizing... \ 3
Optimizing... - 4
Optimizing... / 5
Optimizing... - 6
Optimizing... \ 7
Optimizing... - 8
Optimizing... / 9
Optimizing... - 10
Optimizing... \ 11
Optimizing... - 12
Optimizing... / 13
Optimizing... - 14
Optimizing... \ 15
Optimizing... - 16
Optimizing... / 17


Optimizing... / 1
Optimizing... - 2
Optimizing... \ 3
Optimizing... - 4
Optimizing... / 5
Optimizing... - 6
Optimizing... \ 7
Optimizing... - 8
Optimizing... / 9
Optimizing... - 10
Optimizing... \ 11
Optimizing... - 12
Optimizing... / 13
Optimizing... - 14
Optimizing... \ 15
Optimizing... - 16
Optimizing... / 17

18: 5391.43 18: 5391.43
0.60777 0.60777
0.127151 0.127151
0.189039 0.189039
0.788612 0.788612
0.564763 0.564763
0.941319 0.941319
0.565297 0.565297
0.844854 0.844854
0.357532 0.357532
0.717998 0.717998
Initializing data structure: Done.
Number of distinct sites...: 375
Initializing data structure: Done.
Number of distinct sites...: 375

Optimizing... / 1
Optimizing... - 2
Optimizing... \ 3
Optimizing... - 4
Optimizing... / 5
Optimizing... - 6
Optimizing... \ 7
Optimizing... - 8
Optimizing... / 9
Optimizing... - 10
Optimizing... \ 11
Optimizing... - 12
Optimizing... / 13
Optimizing... - 14


Optimizing... / 1
Optimizing... - 2
Optimizing... \ 3
Optimizing... - 4
Optimizing... / 5
Optimizing... - 6
Optimizing... \ 7
Optimizing... - 8
Optimizing... / 9
Optimizing... - 10
Optimizing... \ 11
Optimizing... - 12
Optimizing... / 13
Optimizing... - 14

15: 5401.83 15: 5401.83
0.419181 0.419181
0.140299 0.140299
0.295 0.295
0.900203 0.900203
0.411605 0.411605
0.919716 0.919716
0.563041 0.563041
0.813833 0.813833
0.194868 0.194868
0.801315 0.801315
0.444785 0.514541 0.514541
0.137341 0.15071 0.15071
0.219281 0.231066 0.231066
0.759382 0.828058 0.828058
0.549516 0.48858 0.48858
0.925583 0.926483 0.926483
0.527333 0.539292 0.539292
0.891561 0.857552 0.857552
0.331932 0.244253 0.244253
0.523327 0.772256 0.772256


...

93% tests passed, 1 tests failed out of 14

Total Test time (real) =  31.15 sec

The following tests FAILED:
   5 - test_likelihood_nh (Failed)


I remember that I once had even a test failure on my local amd64 - so
this test might be a bit undetermined.  Please confirm this and I'd be
happy if you could send an *as simple as possible* patch or simply
deactivate the patch.  We are in deep freeze and need to find a quick
and also simple solution.

Kind regards

   Andreas.


[1] https://buildd.debian.org/status/package.php?p=libbpp-phyl
[2] 
https://buildd.debian.org/status/fetch.php?pkg=libbpp-phyl=s390x=2.4.1-2=1551477555=0

-- 
http://fam-tille.de

Processed: [bts-link] source package src:kubernetes

2019-03-07 Thread Debian Bug Tracking System

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

> #
> # bts-link upstream status pull for source package src:kubernetes
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #923686 (http://bugs.debian.org/923686)
> # Bug title: kubernetes: CVE-2019-1002100: kube-apiserver: DoS with crafted 
> patch of type json-patch
> #  * https://github.com/kubernetes/kubernetes/issues/74534
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 923686 + fixed-upstream
Bug #923686 [src:kubernetes] kubernetes: CVE-2019-1002100: kube-apiserver: DoS 
with crafted patch of type json-patch
Added tag(s) fixed-upstream.
> usertags 923686 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#923990: Failure: TypeError: str() argument 2 must be str, not None

2019-03-07 Thread Sandro Tosi

Package: dh-python
Version: 3.20180927
Severity: critical

(severity it's because it breaks other packages)

i just uploaded python-dmidecode, and it fails on the buildds with:

I: dh_python2 fs:343: renaming dmidecodemod.so to 
dmidecodemod.aarch64-linux-gnu.so
Traceback (most recent call last):
  File "/usr/share/dh-python/dh_python2", line 545, in 
main()
  File "/usr/share/dh-python/dh_python2", line 430, in main
stats = Scanner(interpreter, package, private_dir, options).result
  File "/usr/share/dh-python/dhpython/fs.py", line 230, in __init__
ver = self.handle_ext(fpath)
  File "/usr/share/dh-python/dh_python2", line 57, in handle_ext
so_version = so2pyver(fpath)
  File "/usr/share/dh-python/dhpython/tools.py", line 139, in so2pyver
match = SHAREDLIB_RE.search(str(process.stdout.read(), encoding=encoding))
TypeError: str() argument 2 must be str, not None
make: *** [debian/rules:11: binary-arch] Error 1

logs at 
https://buildd.debian.org/status/fetch.php?pkg=python-dmidecode=arm64=3.12.2-8=1552005709=0
shows it's using version 3.20190307, which was just uploaded today.

could you have a look please?

thanks,
Sandro

-- 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.14.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dh-python depends on:
ii  python33.7.1-3
ii  python3-distutils  3.7.1-1

dh-python recommends no packages.

Versions of packages dh-python suggests:
ii  dpkg-dev  1.19.0.4
ii  libdpkg-perl  1.19.0.4

-- no debconf information

Bug#923970: marked as done (libkres-dev: cannot build anything meaningful against libkres-dev)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Fri, 08 Mar 2019 00:34:31 +
with message-id 
and subject line Bug#923970: fixed in knot-resolver 3.2.1-2
has caused the Debian Bug report #923970,
regarding libkres-dev: cannot build anything meaningful against libkres-dev
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.)


-- 
923970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkres-dev
Version: 3.2.1-1
Severity: grave
Justification: renders package unusable

A little over half of the header files shipped in libkres-dev contain
an #include line that refers to other files in "lib/…", for example:

#include "lib/defines.h"

You can see these with:

grep -n 'include "lib' /usr/include/libkres/*.h

This breaks anything that tries to #include these files directly, with
errors like this:

gcc -o kres-test kres-test.c -lkres
In file included from kres-test.c:1:
/usr/include/libkres/module.h:23:10: fatal error: lib/defines.h: No such 
file or directory
 #include "lib/defines.h"
  ^~~
compilation terminated.
make: *** [Makefile:4: kres-test] Error 1


Of the files that don't include such a broken #include, they are
either not particularly useful on their own
(e.g. /usr/include/libkres/defines.h) or they refer to functions not
actually exported by libkres.so
(e.g. /usr/include/libkres/signature.h, which exposes a C header for
kr_authenticate_referral, which is not in libkres.so).

So libkres-dev doesn't really work at all right now, and the
distributed shared object libkres.so.* itself doesn't seem to be
useful for anything other than knot-resolver.

Upstream is planning to eventually produce some sort of functional
library, but they're not clear on what it looks like:

https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/770

So i think my earlier attempt at splitting out libkres was overly
optimistic, and will probably roll it back so that we're not shipping
a useless package.  When libkres matures, i'm sure we'll be able to
split it out again!

  --dkg



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

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

Versions of packages libkres-dev depends on:
ii  libkres9  3.2.1-1

libkres-dev recommends no packages.

libkres-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: knot-resolver
Source-Version: 3.2.1-2

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated knot-resolver 
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: Thu, 07 Mar 2019 16:23:16 -0500
Source: knot-resolver
Architecture: source
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: knot-resolver packagers 
Changed-By: Daniel Kahn Gillmor 
Closes: 923970
Changes:
 knot-resolver (3.2.1-2) unstable; urgency=medium
 .
   * Standards-Version: move to 4.3.0 (no changes needed)
   * move to debhelper 12
   * Avoid breakage when built against knot-dns 2.8.0
   * d/tests/control: wrap-and-sort
   * Drop libkres9 and libkres-dev packages (Closes: #923970)
   * avoid clobbering CXXFLAGS when compiling lua-aho-corasick
   * missing-sources: updated dygraph-combined.js to match minified version
   * avoid shipping pre-built glyphicons-halflings-regular.woff2
Checksums-Sha1:
 eaea88d95bbe9c9d435c4e3b1ec227d612156207 2297 knot-resolver_3.2.1-2.dsc
 1ea6725b36cd052acddf3dda020c1603fcccec02 833 
knot-resolver_3.2.1.orig.tar.xz.asc

Bug#919442: marked as done (python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Fri, 08 Mar 2019 00:34:43 +
with message-id 
and subject line Bug#919442: fixed in python-dmidecode 3.12.2-8
has caused the Debian Bug report #919442,
regarding python-dmidecode-dbg: unhandled symlink to directory conversion: 
/usr/share/doc/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.)


-- 
919442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-dmidecode-dbg
Version: 3.12.2-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m37.0s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-dmidecode-dbg/AUTHORS (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/AUTHORS (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/AUTHORS.upstream (python-dmidecode-dbg) 
!= /usr/share/doc/python-dmidecode/AUTHORS.upstream (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/README (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/README (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/README.types (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/README.types (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/README.upstream.gz (python-dmidecode-dbg) 
!= /usr/share/doc/python-dmidecode/README.upstream.gz (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/changelog.Debian.gz 
(python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/changelog.Debian.gz 
(python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/changelog.gz (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/changelog.gz (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/copyright (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/copyright (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode


cheers,

Andreas


python-dmidecode-dbg_3.12.2-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-dmidecode
Source-Version: 3.12.2-8

We believe that the bug you reported is fixed in the latest version of
python-dmidecode, 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.
Sandro Tosi  (supplier of updated python-dmidecode package)

(This message was generated automatically at their request; if you
believe that there is a

Processed: Reassign javadoc RC bugs to javahelper

2019-03-07 Thread Debian Bug Tracking System

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

> reassign 923748 javahelper
Bug #923748 [src:colorpicker] colorpicker: FTBFS in buster/sid
Bug reassigned from package 'src:colorpicker' to 'javahelper'.
No longer marked as found in versions colorpicker/1.0.0-3.
Ignoring request to alter fixed versions of bug #923748 to the same values 
previously set
> reassign 923751 javahelper
Bug #923751 [src:gentlyweb-utils] gentlyweb-utils: FTBFS in buster/sid
Bug reassigned from package 'src:gentlyweb-utils' to 'javahelper'.
No longer marked as found in versions gentlyweb-utils/1.5-2.
Ignoring request to alter fixed versions of bug #923751 to the same values 
previously set
> reassign 923753 javahelper
Bug #923753 [src:jcm] jcm: FTBFS in buster/sid
Bug reassigned from package 'src:jcm' to 'javahelper'.
No longer marked as found in versions jcm/1.0-1.
Ignoring request to alter fixed versions of bug #923753 to the same values 
previously set
> reassign 923754 javahelper
Bug #923754 [src:jesd] jesd: FTBFS in buster/sid
Bug reassigned from package 'src:jesd' to 'javahelper'.
No longer marked as found in versions jesd/0.0.7-4.
Ignoring request to alter fixed versions of bug #923754 to the same values 
previously set
> reassign 923755 javahelper
Bug #923755 [src:libcsv-java] libcsv-java: FTBFS in buster/sid
Bug reassigned from package 'src:libcsv-java' to 'javahelper'.
No longer marked as found in versions libcsv-java/2.1-1.
Ignoring request to alter fixed versions of bug #923755 to the same values 
previously set
> reassign 923756 javahelper
Bug #923756 [javahelper] javahelper: javadoc: error - The code being documented 
uses packages in the unnamed module
Ignoring request to reassign bug #923756 to the same package
> reassign 923757 javahelper
Bug #923757 [src:libirclib-java] libirclib-java: FTBFS in buster/sid
Bug reassigned from package 'src:libirclib-java' to 'javahelper'.
No longer marked as found in versions libirclib-java/1.10-3.
Ignoring request to alter fixed versions of bug #923757 to the same values 
previously set
> reassign 923758 javahelper
Bug #923758 [src:libnanoxml2-java] libnanoxml2-java: FTBFS in buster/sid
Bug reassigned from package 'src:libnanoxml2-java' to 'javahelper'.
No longer marked as found in versions libnanoxml2-java/2.2.3.dfsg-6.
Ignoring request to alter fixed versions of bug #923758 to the same values 
previously set
> forcemerge 923756 923748 923751 923753 923754 923755 923756 923757
Bug #923756 [javahelper] javahelper: javadoc: error - The code being documented 
uses packages in the unnamed module
Bug #923756 [javahelper] javahelper: javadoc: error - The code being documented 
uses packages in the unnamed module
Added tag(s) sid and buster.
Bug #923748 [javahelper] colorpicker: FTBFS in buster/sid
Marked as found in versions javatools/0.72.2.
Added tag(s) sid and buster.
Bug #923754 [javahelper] jesd: FTBFS in buster/sid
Marked as found in versions javatools/0.72.2.
Bug #923755 [javahelper] libcsv-java: FTBFS in buster/sid
Marked as found in versions javatools/0.72.2.
Bug #923753 [javahelper] jcm: FTBFS in buster/sid
Marked as found in versions javatools/0.72.2.
Bug #923751 [javahelper] gentlyweb-utils: FTBFS in buster/sid
Marked as found in versions javatools/0.72.2.
Added tag(s) buster and sid.
Bug #923757 [javahelper] libirclib-java: FTBFS in buster/sid
Marked as found in versions javatools/0.72.2.
Merged 923748 923751 923753 923754 923755 923756 923757
> forcemerge 923756 923758
Bug #923756 [javahelper] javahelper: javadoc: error - The code being documented 
uses packages in the unnamed module
Bug #923748 [javahelper] colorpicker: FTBFS in buster/sid
Bug #923751 [javahelper] gentlyweb-utils: FTBFS in buster/sid
Bug #923753 [javahelper] jcm: FTBFS in buster/sid
Bug #923754 [javahelper] jesd: FTBFS in buster/sid
Bug #923755 [javahelper] libcsv-java: FTBFS in buster/sid
Bug #923757 [javahelper] libirclib-java: FTBFS in buster/sid
Bug #923758 [javahelper] libnanoxml2-java: FTBFS in buster/sid
Marked as found in versions javatools/0.72.2.
Added tag(s) buster and sid.
Bug #923748 [javahelper] colorpicker: FTBFS in buster/sid
Bug #923751 [javahelper] gentlyweb-utils: FTBFS in buster/sid
Bug #923753 [javahelper] jcm: FTBFS in buster/sid
Bug #923754 [javahelper] jesd: FTBFS in buster/sid
Bug #923755 [javahelper] libcsv-java: FTBFS in buster/sid
Bug #923757 [javahelper] libirclib-java: FTBFS in buster/sid
Merged 923748 923751 923753 923754 923755 923756 923757 923758
> affects 923756 src:colorpicker src:gentlyweb-utils src:jcm src:jesd
Bug #923756 [javahelper] javahelper: javadoc: error - The code being documented 
uses packages in the unnamed module
Bug #923748 [javahelper] colorpicker: FTBFS in buster/sid
Bug #923751 [javahelper] gentlyweb-utils: FTBFS in buster/sid
Bug #923753 [javahelper] jcm: FTBFS in buster/sid
Bug #923754 [javahelper] jesd: FTBFS in buster/sid
Bug #923755 [javahelper] libcsv-java: FTBFS in buster/sid
Bug #923757 [javahelper] libirclib-java: FTBFS in buster/sid
Bug

Processed: Bug #919442 in python-dmidecode marked as pending

2019-03-07 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #919442 [python-dmidecode-dbg] python-dmidecode-dbg: unhandled symlink to 
directory conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.

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

Bug#919442: Bug #919442 in python-dmidecode marked as pending

2019-03-07 Thread Sandro Tosi

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-dmidecode/commit/521a05ae70143756f23210769cf26455aa4ab793


remove doc/ directories, to actually use dir_to_symlink; Closes: #919442


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919442

Bug#923986: ruby-pygments.rb: FTBFS randomly (failing tests)

2019-03-07 Thread Santiago Vila

Package: src:ruby-pygments.rb
Version: 1.2.0-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 --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
   dh_ruby --build
# build documention
rdoc lib
Parsing sources...
 20% [ 1/ 5]  lib/pygments.rb
 40% [ 2/ 5]  lib/pygments/lexer.rb
 60% [ 3/ 5]  lib/pygments/mentos.py
 80% [ 4/ 5]  lib/pygments/popen.rb
100% [ 5/ 5]  lib/pygments/version.rb

Generating Darkfish format into /<>/doc...


  Files:   5

  Classes: 3 (2 undocumented)
  Modules: 1 (0 undocumented)
  Constants:   1 (1 undocumented)
  Attributes:  0 (0 undocumented)
  Methods:27 (5 undocumented)

  Total:  32 (8 undocumented)
   75.00% documented

  Elapsed: 0.5s

make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install
dh_ruby --install /<>/debian/ruby-pygments.rb
   dh_ruby --install

ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Install files   
 â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ

install -d /<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby
install -D -m644 /<>/lib/pygments.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments.rb
install -D -m644 /<>/lib/pygments/version.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/version.rb
install -D -m644 /<>/lib/pygments/mentos.py 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/mentos.py
install -D -m644 /<>/lib/pygments/lexer.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/lexer.rb
install -D -m644 /<>/lib/pygments/popen.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/popen.rb
dh_installchangelogs -pruby-pygments.rb /<>/CHANGELOG.md upstream

ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Install Rubygems integration metadata   
 â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ

generating gemspec at 
/<>/debian/ruby-pygments.rb/usr/share/rubygems-integration/all/specifications/pygments.rb-1.2.0.gemspec
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Checking Rubygems dependency resolution on ruby2.5  
 â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ

GEM_PATH=debian/ruby-pygments.rb/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"pygments.rb\"

ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Run tests for ruby2.5 from debian/ruby-tests.rb 
 â

Bug#923889: google-compute-image-packages - DoS via serial console write

2019-03-07 Thread Ross Vandegrift

On Wed, Mar 06, 2019 at 07:49:38PM +0100, Bastian Blank wrote:
> This package instructs journald to duplicate everything sent to the
> journal to the serial console.  The serial console is a pretty rate
> limited log output device and blocking there will make all software with
> any log output block.

This doesn't seem to affect all software - I tried to reproduce with
logger, but it doesn't block.  Maybe this only affects some logging
transports?

I agree it's a problematic default - GCE serial console data is
currently stored unencrypted.  That could be an unpleasent surprise.

Ross

Bug#923719: marked as done (celery: FTBFS ("Download error", probably because of missing build-depends))

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 22:04:28 +
with message-id 
and subject line Bug#923719: fixed in celery 4.2.1-3
has caused the Debian Bug report #923719,
regarding celery: FTBFS ("Download error", probably because of missing 
build-depends)
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.)


-- 
923719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:celery
Version: 4.2.1-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 python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/_state.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/beat.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/exceptions.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/__main__.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/schedules.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/five.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/states.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/local.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/__init__.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/bootsteps.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/result.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/signals.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/platforms.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
copying celery/canvas.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery
creating /<>/.pybuild/cpython2_2.7_celery/build/celery/fixups
copying celery/fixups/__init__.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/fixups
copying celery/fixups/django.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/fixups
creating /<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/nodenames.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/serialization.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/abstract.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/iso8601.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/sysinfo.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/timer2.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/time.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/imports.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/collections.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/functional.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/debug.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/deprecated.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/log.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/__init__.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/threads.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/saferepr.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/encoding.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/graph.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/objects.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/term.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
copying celery/utils/text.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/utils
creating /<>/.pybuild/cpython2_2.7_celery/build/celery/backends
copying celery/backends/amqp.py -> 
/<>/.pybuild/cpython2_2.7_celery/build/celery/backends

Bug#923959: marked as done (afflib: FTBFS (dh_makeshlibs fails))

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 22:04:10 +
with message-id 
and subject line Bug#923959: fixed in afflib 3.7.17-5
has caused the Debian Bug report #923959,
regarding afflib: FTBFS (dh_makeshlibs fails)
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.)


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

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with autoreconf
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:20: installing './compile'
configure.ac:26: installing './config.guess'

[... snipped ...]

make[2]: Leaving directory '/<>'
chrpath -d debian/tmp/usr/bin/*
set -e; for file in `ls debian/tmp/usr/lib/*/*.la`; do \
sed -i "/dependency_libs/ s/'.*'/''/" $file ; \
done
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installman -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_strip -a
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/<>'
dh_makeshlibs -- -v3.7.17
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/libafflib0v5/DEBIAN/symbols doesn't match 
completely debian/libafflib0v5.symbols
--- debian/libafflib0v5.symbols (libafflib0v5_3.7.17_amd64)
+++ dpkg-gensymbolsSIEKs1   2019-03-07 14:37:18.703845582 +
@@ -373,9 +373,13 @@
  
(optional)_ZNSt6vectorIPN2s36BucketESaIS2_EE19_M_emplace_back_auxIJS2_EEEvDpOT_@Base
 3.7.17
  
_ZNSt6vectorIPN2s38ContentsESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.7.16
  
(optional)_ZNSt6vectorIPN2s38ContentsESaIS2_EE19_M_emplace_back_auxIJS2_EEEvDpOT_@Base
 3.7.17
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueIS5_EESt4pairISt17_Rb_tree_iteratorIS5_EbEOT_@Base
 3.7.16
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 3.7.17
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 3.7.17
+#MISSING: 3.7.17# 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueIS5_EESt4pairISt17_Rb_tree_iteratorIS5_EbEOT_@Base
 3.7.16
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 3.7.16
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSG_PSt13_Rb_tree_nodeIS8_E@Base
 3.7.16
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOS5_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 3.7.17
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 3.7.17
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 3.7.16
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 3.7.16

Bug#903698: marked as done (sphinxbase: build appears broken for multiple python3 versions)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 21:49:39 +
with message-id 
and subject line Bug#903698: fixed in dh-python 3.20190307
has caused the Debian Bug report #903698,
regarding sphinxbase: build appears broken for multiple python3 versions
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.)


-- 
903698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxbase
Version: 0.8+5prealpha+1-2
Severity: serious

Hi all,

sphinxbase is currently involved in the python3.7 "transition"¹. I
noticed that sphinxbase was rebuild, but that is was still listed in the
"bad" category. I took a look at the amd64 build log² and spotted the
following some oddities in python3-sphinxbase.

1) it has only has the 3.6 dependencies (hence listed as bad)
2) it only has 3.7 site-packages files
3) _sphinxbase.cpython-37m-x86_64-linux-gnu.so points to a non-exitent
file. The file is in the 3.7 site-packages directory.
4) python3 versions in the build are first 3.7 and then 3.6, they seem
to be using the same build directory.

I think this is caused by the fact that we loop over $pyver in the
d/rules file, but apparently that is broken for multiple python3 versions.

I think the package is probably not working currently hence I file this
bug. (I don't know how to fix it properly yet, maybe Samuel has ideas?).

Paul

¹ https://release.debian.org/transitions/html/python3.7.html
²
https://buildd.debian.org/status/fetch.php?pkg=sphinxbase=amd64=0.8%2B5prealpha%2B1-2%2Bb1=1530298945=0



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 3.20190307

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated dh-python 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: Thu, 07 Mar 2019 22:00:17 +0100
Source: dh-python
Binary: dh-python
Architecture: source all
Version: 3.20190307
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Description:
 dh-python  - Debian helper tools for packaging Python libraries and applicatio
Closes: 901000 901759 903698 912892 912909 913338 914998 915408 920899 923048
Changes:
 dh-python (3.20190307) unstable; urgency=medium
 .
   [ Antoine Beaupré ]
   * Ignore tilde version numbers which crash setuptools-scm (closes: 915408)
 .
   [ Agustin Henze ]
   * Use current locale for encoding the output process while checking
 libpython's version extension file is linked to (closes: 901000, 912909)
 .
 Thanks also to Zack Weinberg for different patch solving this issue
 in 912909!
 .
   [ Helmut Grohne ]
   * pybuild:
 - make it easier to cross-build Python 2 extensions (closes: 901759)
 - use DEB_HOST_ARCH{,_OS} instead of DEB_TARGET_ARCH{,_OS} (closes: 912892)
 .
 Thanks also to Dima Kogan for patches, including the one adding more
 debug info.
 .
   [ Samuel Thibault ]
   * Fix handling broken symlinks while renaming extension files
 (closes: 903698).
 .
   [ Nicolas Dandrimont ]
   * Support "Compatible release" version specifiers ("~=") in the requires
 parser (closes: 913338).
 .
   [ Piotr Ożarowski ]
   * pybuild.pm: follow python3-tox → tox (unfortunate) rename
   * dh-python now provides dh-sequence-python3, dh-sequence-python2
 and dh-sequence-pypy packages (to be used in debhelper >= 12)
   * Update tests to use 3.7 as default/supported Python 3.X (closes: 914998)
   * dh_pypy: add namespace support: new options: --namespace, 
--ignore-namespace
 and parsing namespace_packages.txt by default (closes: 920899)
   * dh_python3: move files from /usr/include/python3.X/ to
 /usr/include/python3.Xm/ for Python 3.X >= 3.3 (closes: 923048)
   * Standards-Version is 4.3.0 now (no changes needed)
Checksums-Sha1:
 8b0e2020917259d63de592bc51b063f28af8783a 1877 dh-python_3.20190307.dsc

Processed: Bumping severities of python-gdata bugs

2019-03-07 Thread Debian Bug Tracking System

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

> # python-gdata is buggy and should not be shipped with Buster
> severity 899007 serious
Bug #899007 [bauble] bauble: Depends on unmaintained python-gdata
Severity set to 'serious' from 'important'
> severity 899010 serious
Bug #899010 [python-ckanclient] python-ckanclient: Depends on unmaintained 
python-gdata
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#923719: Bug #923719 in celery marked as pending

2019-03-07 Thread Michael Fladischer

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/celery/commit/cda5d90d4d30dd1a26a337875a7f23c50140ec04


Add patch to relax version requirements on billiard (Closes: #923719).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923719

Processed: Bug #923719 in celery marked as pending

2019-03-07 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #923719 [src:celery] celery: FTBFS ("Download error", probably because of 
missing build-depends)
Added tag(s) pending.

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

Bug#921232: mono: Internal compiler error building libsbml on s390x

2019-03-07 Thread Jo Shields

Neale, can you try building libsbml (http://sbml.org/Software/libSBML)
on s390x against a Mono revision you trust? It could be something bad in
out 5.18 s390x backports, or it could be unrelated to that.

On 07/03/2019 16:16, Petter Reinholdtsen wrote:
> [Adrian Bunk]
>> We dn't have any kind of CI coverage on s390x,
>> it is therefore not obvious whether this is
>> a problem confined to one package or whether
>> Mono is completely broken on s390x.
> I guess that is just another way to say that no-one know if anyone is using
> mono on s390x?  Perhaps it is best to drop mono from s390x until it can
> be confimed to be working there, instead of risking mono to be dropped from
> buster on all the working architectures?

Bug#923926: Acknowledgement (proftpd-basic: proftpd 1.3.5b has memory leaks, allows Denial-Of-Service attack)

2019-03-07 Thread esbeeb

Great, OpenMediaVault has the "unattended-upgrades" package installed by 
default, so your security update should apply itself automatically, once it's 
published.
I'll try my OpenMediaVault proftpd upload again once the security fix arrives, 
and watch the RAM usage, with htop.  I'll let you know if any memory leak 
remains.  If any memory leak remains (albeit a slower leak), then this DOS 
still exisits...

-- 
Cheers,
Subharo Bhikkhu
https://bhikkhu.ca



Mar 7, 2019, 6:30 PM by ow...@bugs.debian.org:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 923926: > 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923926 
> > .
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>  > esb...@tuta.io > , Debian Security Team <> 
> t...@security.debian.org > >
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  ProFTPD Maintainance Team <> pkg-proftpd-maintain...@alioth-lists.debian.net 
> > >
>
> If you wish to submit further information on this problem, please
> send it to > 923...@bugs.debian.org > .
>
> Please do not send mail to > ow...@bugs.debian.org 
> >  unless you wish
> to report a problem with the Bug-tracking system.
>
> -- 
> 923926: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923926 
> 
> Debian Bug Tracking System
> Contact > ow...@bugs.debian.org >  with problems
>

Bug#921232: mono: Internal compiler error building libsbml on s390x

2019-03-07 Thread Petter Reinholdtsen

[Adrian Bunk]
> We dn't have any kind of CI coverage on s390x,
> it is therefore not obvious whether this is
> a problem confined to one package or whether
> Mono is completely broken on s390x.

I guess that is just another way to say that no-one know if anyone is using
mono on s390x?  Perhaps it is best to drop mono from s390x until it can
be confimed to be working there, instead of risking mono to be dropped from
buster on all the working architectures?
-- 
Happy hacking
Petter Reinholdtsen

Bug#923541: marked as done (libdbd-mysql-perl: FTBFS against mariadb-10.3 1:10.3.13-1)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 21:05:07 +
with message-id 
and subject line Bug#923541: fixed in libdbd-mysql-perl 4.050-2
has caused the Debian Bug report #923541,
regarding libdbd-mysql-perl: FTBFS against mariadb-10.3 1:10.3.13-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.)


-- 
923541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbd-mysql-perl
Version: 4.050-1
Severity: serious
Tags: upstream ftbfs sid
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This is already discussed in
https://lists.debian.org/debian-perl/2019/02/msg00026.html
but filing it as a bug:

libdbd-mysql-perl fails its tests with

t/rt118977-zerofill.t ... 
1..8
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
not ok 8
#   Failed test at t/rt118977-zerofill.t line 22.
#  got: '1'
# expected: '1'
# Looks like you failed 1 test of 8.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/8 subtests 

when built against mariadb-10.3 1:10.3.13-1.

This looks like #917303 which was fixed in 4.050-1 and this fix
worked with mariadb-10.3 1:10.3.12-2. Seems that there is a change in
mariadb between 10.3.12 and 10.3.13 which breaks the test again.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlx5bDpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgb5UA/6A9nE1Lc053by+8vO/bTPqbCWfUR+3J4ECcK0zzu1sZ89xoRP07LRpr/r
LFL5H38YIhEwxqvgzq1wtLo0y16nNvGZ/qMhpJNTulbMfCzI78IP9ipjzyhg8eS+
/Fc/QubSFCy/c8rkvoINi2aRo53icn8nnBuwlamQyBydzEN4Pi+ysCFmmJiJ2CFf
1aeL+NCX8d9E+aQrkvqjLvmaQ2SscZgNr18xBSWl3UywPiUhidrAOjme85G8OPLN
5jCvC/LxcPk54bxToLMlxvS+NJ1BmjTGLpWnnCXmo9ZMoLGaY0UU8XnG4FJgJUgB
O8rHgKBrqvOpVbi8/3vz7A6kkteMpaVnNDUG+sjBKdYc5mD8cZv8Oa+7/kFloOlJ
UWDUYL8I8qjvUuCBz5mDVs7bz5bXZfEdsKy08QVoh7cRXTgkTT/2fZ9xfyGa6ZJe
JiG6LtlH47gDJf6IDOE9MX4abh1nAF2P+ZCGoAAz+J7kSCFxb5e5604RY4u8fhYJ
3xRliHFH4467RK979VOXKZWGYsVOC7YGGdTBMhRPrb2aNeBGC4j+/q5PJ3gmEoB7
vPXaawAi5jKEjRi9N9KCedztL65GEKrChY7/Y8JnXiSi3S8cpUWfuMghP7zSz7IL
BFo790+5FDCayDTIHLfTpsI1dg8t8cIrX1UyGFqmyD5uLquExZk=
=6lnQ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libdbd-mysql-perl
Source-Version: 4.050-2

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libdbd-mysql-perl 
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: Thu,  7 Mar 2019 21:53:56 CET
Source: libdbd-mysql-perl
Binary: 
Architecture: source
Version: 4.050-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
Closes: 923541
Changes:
 libdbd-mysql-perl (4.050-2) unstable; urgency=medium
 .
   * Add patch from upstream Git to fix zerofill breakage with
 MariaDB 10.3.13.
 Thanks to Daniël van Eeden for the fix. (Closes: #923541)
Checksums-Sha256: 
 13bdb26f3ef6deeca1a171f711a34e699f11d4c27b5b26c9da61e44368da6a35 2513 
libdbd-mysql-perl_4.050-2.dsc
 ae0ce7d2c03116539a01a37fa633f9cd6c284fe93982c73aa8e4c0c650073a78 12656 
libdbd-mysql-perl_4.050-2.debian.tar.xz
 890f22c1fabc2312858dfc1cdd53b4f6c0ecc756803ee97ebc8335a7e10967c5 7533 
libdbd-mysql-perl_4.050-2_sourceonly.buildinfo
Checksums-Sha1: 
 37bf35cedcdb4f00a2c7e53fa76acc83d3912697 2513 libdbd-mysql-perl_4.050-2.dsc
 9dce3240974d03d39f3202fec7f72f8b2f49d1e1 12656 
libdbd-mysql-perl_4.050-2.debian.tar.xz
 131c21144c74255a7a2837f324d309d45e76bb4c 7533 
libdbd-mysql-perl_4.050-2_sourceonly.buildinfo
Files: 
 062b562e99a09a60a04100f9e5d73830 2513 perl optional 
libdbd-mysql-perl_4.050-2.dsc
 1f0ce73a6b7fc04fee95833aa668034a 12656 perl optional 
libdbd-mysql-perl_4.050-2.debian.tar.xz
 fea7ba3312b1597da7df48e6ded2cbe3 7533 - - 
libdbd-mysql-perl_4.050-2_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

Bug#923541: libdbd-mysql-perl: FTBFS against mariadb-10.3 1:10.3.13-1

2019-03-07 Thread gregor herrmann

On Thu, 07 Mar 2019 16:28:15 +0100, gregor herrmann wrote:

> I've pushed this to salsa but I'd like to wait a day or two and see
> of the PR gets merged and/or if other solutions arise (there's a
> second patch around, and also a MariaDB bug report:
> https://jira.mariadb.org/browse/MDEV-18823 )

Uploaded now as per request of the release team in order to unblock
MariaDB. We still can improve the fix in case newer developments
happen upstream.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: U2: Zooropa


signature.asc
Description: Digital Signature

Bug#923891: Root cause

2019-03-07 Thread Soren Stoutner

This bug appears to be caused by the packaging switch in the JQuery 
library as described by this line in the 4.0.1-1 changelog.


"Use system jquery libs instead of source-less embedded aggregated file."

--
Soren Stoutner
623-262-6169
so...@stoutner.com

Bug#923955: marked as done (libncl: FTBFS (dh_makeshlibs fails))

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 18:34:33 +
with message-id 
and subject line Bug#923955: fixed in libncl 2.1.21+git20180827.c71b264-2
has caused the Debian Bug report #923955,
regarding libncl: FTBFS (dh_makeshlibs fails)
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.)


-- 
923955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libncl
Version: 2.1.21+git20180827.c71b264-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'
libtoolize: copying file 'config/ltsugar.m4'
libtoolize: copying file 'config/ltversion.m4'
libtoolize: copying file 'config/lt~obsolete.m4'
configure.ac:28: installing 'config/compile'
configure.ac:21: installing 'config/missing'

[... snipped ...]

+#MISSING: 2.1.21+git20180827.c71b264-1# 
_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE17_M_insert_unique_IRKS0_NS6_11_Alloc_nodeEEESt17_Rb_tree_iteratorIS0_ESt23_Rb_tree_const_iteratorIS0_EOT_RT0_@Base
 2.1.21+git20171002.4becff7
  
_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE24_M_get_insert_unique_posERKS0_@Base
 2.1.18
  
(optional)_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS0_ERKS0_@Base
 2.1.21+git20171002.4becff7
  
_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE8_M_eraseEPSt13_Rb_tree_nodeIS0_E@Base
 2.1.18
@@ -1122,7 +1126,7 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 2.1.18
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EEaSERKSB_@Base
 2.1.18
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE11equal_rangeERS7_@Base
 2.1.21+git20171002.4becff7
- 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base
 2.1.18
+#MISSING: 2.1.21+git20180827.c71b264-1# 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base
 2.1.18
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE17_M_emplace_uniqueIJS6_IS5_S8_S6_ISt17_Rb_tree_iteratorIS9_EbEDpOT_@Base
 2.1.21+git20171002.4becff7
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE4findERS7_@Base
 2.1.21+git20171002.4becff7
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE5eraseERS7_@Base
 2.1.18
@@ -1130,7 +1134,7 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE8_M_eraseEPSt13_Rb_tree_nodeIS9_E@Base
 2.1.18
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EEaSERKSF_@Base
 2.1.21+git20171002.4becff7
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE11equal_rangeERS7_@Base
 2.1.21+git20171002.4becff7
- 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base
 2.1.18
+#MISSING: 2.1.21+git20180827.c71b264-1#

Bug#923970: libkres-dev: cannot build anything meaningful against libkres-dev

2019-03-07 Thread Daniel Kahn Gillmor

Package: libkres-dev
Version: 3.2.1-1
Severity: grave
Justification: renders package unusable

A little over half of the header files shipped in libkres-dev contain
an #include line that refers to other files in "lib/…", for example:

#include "lib/defines.h"

You can see these with:

grep -n 'include "lib' /usr/include/libkres/*.h

This breaks anything that tries to #include these files directly, with
errors like this:

gcc -o kres-test kres-test.c -lkres
In file included from kres-test.c:1:
/usr/include/libkres/module.h:23:10: fatal error: lib/defines.h: No such 
file or directory
 #include "lib/defines.h"
  ^~~
compilation terminated.
make: *** [Makefile:4: kres-test] Error 1


Of the files that don't include such a broken #include, they are
either not particularly useful on their own
(e.g. /usr/include/libkres/defines.h) or they refer to functions not
actually exported by libkres.so
(e.g. /usr/include/libkres/signature.h, which exposes a C header for
kr_authenticate_referral, which is not in libkres.so).

So libkres-dev doesn't really work at all right now, and the
distributed shared object libkres.so.* itself doesn't seem to be
useful for anything other than knot-resolver.

Upstream is planning to eventually produce some sort of functional
library, but they're not clear on what it looks like:

https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/770

So i think my earlier attempt at splitting out libkres was overly
optimistic, and will probably roll it back so that we're not shipping
a useless package.  When libkres matures, i'm sure we'll be able to
split it out again!

  --dkg



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

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

Versions of packages libkres-dev depends on:
ii  libkres9  3.2.1-1

libkres-dev recommends no packages.

libkres-dev suggests no packages.

-- no debconf information

Bug#923954: marked as done (libbpp-seq: FTBFS (dh_makeshlibs fails))

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 18:19:29 +
with message-id 
and subject line Bug#923954: fixed in libbpp-seq 2.4.1-3
has caused the Debian Bug report #923954,
regarding libbpp-seq: FTBFS (dh_makeshlibs fails)
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.)


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

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- bpp-core 4.1.0 found:

[... snipped ...]

  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base
 2.4.1
@@ -1851,6 +1853,7 @@
  
_ZNSt8_Rb_treeIcSt4pairIKcdESt10_Select1stIS2_ESt4lessIcESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIcSt4pairIKcdESt10_Select1stIS2_ESt4lessIcESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIcSt4pairIKcdESt10_Select1stIS2_ESt4lessIcESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base
 2.4.1-2
  
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
@@ -1873,6 +1876,7 @@
  
_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSA_PSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base
 2.4.1-2
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
@@ -1884,10 +1888,11 @@
  
_ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 2.4.1

Bug#923226: Compiling shader doesn't work - game doesn't work

2019-03-07 Thread Simon McVittie

On Thu, 07 Mar 2019 at 13:30:57 +0100, Julien Puydt wrote:
> Just changing the ioquake3 binary package (which makes dpkg complain about
> ioquake3-server, but it's normal):
> 1.36+u20181017.09166ba~dfsg-2 works
> 1.36+u20181222.e5da13f~dfsg-1 fails

What graphics stack are you using, in particular your kernel and Mesa
driver? Running `reportbug --template ioquake3` will summarize the most
relevant packages.

It looks as though the problem might be that your driver only provides
GLSL 1.20 (either on your hardware or in general), whereas the hitCube()
function introduced between 09166ba and e5da13f assumes GLSL 1.30
or later.

Thanks,
smcv

Processed: bug 923905 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=128529, tagging 923905

2019-03-07 Thread Debian Bug Tracking System

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

> forwarded 923905 https://rt.cpan.org/Public/Bug/Display.html?id=128529
Bug #923905 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS (failing tests)
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=128529'.
> tags 923905 + upstream confirmed
Bug #923905 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS (failing tests)
Added tag(s) confirmed and upstream.
> thanks
Stopping processing here.

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

Bug#910729: marked as done (imexan: FTBFS on s390x: test failures)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 17:34:51 +
with message-id 
and subject line Bug#906198: fixed in python-scipy 1.1.0-3
has caused the Debian Bug report #906198,
regarding imexan: FTBFS on s390x: test failures
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.)


-- 
906198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imexam
Version: 0.8.0-2
Severity: serious

On a rebuild with python3.7 as a supported python3 interpreter, your package
failed to build on s390x:

imexam/tests/test_imexamine.py::test_column_plot PASSED  [ 10%]
imexam/tests/test_imexamine.py::test_line_plot PASSED[ 20%]
imexam/tests/test_imexamine.py::test_aper_phot SKIPPED   [ 30%]
imexam/tests/test_imexamine.py::test_line_fit FAILED [ 40%]
imexam/tests/test_imexamine.py::test_column_fit FAILED   [ 50%]
imexam/tests/test_imexamine.py::test_gauss_center FAILED [ 60%]
imexam/tests/test_imexamine.py::test_radial_profile PASSED   [ 70%]
imexam/tests/test_imexamine.py::test_radial_profile_background SKIPPED   [ 80%]
imexam/tests/test_imexamine.py::test_radial_profile_pixels FAILED[ 90%]
imexam/tests/test_imexamine.py::test_curve_of_growth SKIPPED [100%]

Full logs available from
https://buildd.debian.org/status/logs.php?pkg=imexam=s390x

Emilio
--- End Message ---
--- Begin Message ---
Source: python-scipy
Source-Version: 1.1.0-3

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated python-scipy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Mar 2019 00:31:29 +0800
Source: python-scipy
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Drew Parsons 
Closes: 906198 915738
Changes:
 python-scipy (1.1.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Debian patch ignore_DeprecationWarning_diff1.2.patch applies diff
 of pytest.ini between scipy 1.1 and 1.2 to ignore
 DeprecationWarnings from numpy 1.16. Addresses Bug#919929.
   * Use default gfortran-8 on s390x. unroll-loops was fixed in
 gcc-8 8.2.0-18. Closes: #906198, #915738.
Checksums-Sha1:
 644c3c6dbd9e228962157d56b844c41fd36f2da5 3191 python-scipy_1.1.0-3.dsc
 53e53efad76d0cc1326a238fba343fe463f66ff8 16436 
python-scipy_1.1.0-3.debian.tar.xz
Checksums-Sha256:
 489e05f8180818de18c152b26cd5423fbf8cc9da002a59da549b8180cc7094b8 3191 
python-scipy_1.1.0-3.dsc
 ef5dc35f349dae5d2b9e9d9a893372c2b1ad76d3c8337be8a96f56428902ea47 16436 
python-scipy_1.1.0-3.debian.tar.xz
Files:
 56e177823bea944113ef594cdc83d9fe 3191 python optional python-scipy_1.1.0-3.dsc
 5ebab4bfe5c9fd21589eecbf8a2182f1 16436 python optional 
python-scipy_1.1.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAlyBURwACgkQVz7x5L1a
AfoCXhAAs/BocZzwKZtLfrUK8G2onHAZNsgnyUoPlFMK2jy3XRYPX05/OqvBa6cs
6osHzYLMSRH9lRVKf8psJBTX0dzZoxSKzHxYXBg17OoBJ6O2Nr/sA5Sc2XtblTKG
u+7I8VsGVc05l1M40t/DacQpyzY7UJHOqyl1S44CLZHVfYql4OzRZo6I8FOROKrw
XVIAQV5cGUrvp/Uc0vAEN0+Z2AdQ9wwxRDgbZ184pqgt5koXAJWNmPdjD3r5BIzh
EvtKint+BYrRs1hfd2V745bDXNlx051gL0CLzjMGI8S3ghmTCo7LktoQLga6cxd7
I36Jcfv/vvR5+P2Ju6a0Oc9MxzMm/sxjx+LM0NQwaqWzXss3VZaRZuMEJ3AWMm4+
G3lVpygfv4zzhTcglT1JJy7I+O7cgXzii1bkqV1jN2dK3NdsAXhOoXOrbQbQZmg3
IjvUQclKBj8rYcRBI+m53zUV6zKaK3i5cSypmfcZ4DXc850l5n+dWf6eUpJVPNYI
YZNhPEm6XeFchyp/TD9wj/2LEHRmXOU+c6wYfddt4tIoCA2Cow13qowBOOGzf9A+
Q93Qco2+ZM8wkSNIe70b0hAga+Mbi8K7guwpa4fJqfz/xDHaFGxdb520s3Al1T+t
CbQf/Xbzb1+FcSMsYlRKd011ilLa0jPhWrvLDl+O9sm6gbdT8VE=
=CdTQ
-END PGP SIGNATURE End Message ---

Bug#910781: marked as done (imexam: FTBFS on s390x)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 17:34:51 +
with message-id 
and subject line Bug#906198: fixed in python-scipy 1.1.0-3
has caused the Debian Bug report #906198,
regarding imexam: FTBFS on s390x
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.)


-- 
906198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imexam
Version: 0.8.0-2
Severity: serious
Tags: ftbfs

Hi Maintainer

Recent binNMUs of imexam have FTBFS on s390x[1].
>From the logs, all of the failed attempts were after the upload of
python-scipy 1.1.0-1.

In Ubuntu, there are similar autopkgtest failures on s390x[2].

Regards
Graham


[1] https://buildd.debian.org/status/logs.php?pkg=imexam=s390x
[2] http://autopkgtest.ubuntu.com/packages/i/imexam/cosmic/s390x
--- End Message ---
--- Begin Message ---
Source: python-scipy
Source-Version: 1.1.0-3

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated python-scipy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Mar 2019 00:31:29 +0800
Source: python-scipy
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Drew Parsons 
Closes: 906198 915738
Changes:
 python-scipy (1.1.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Debian patch ignore_DeprecationWarning_diff1.2.patch applies diff
 of pytest.ini between scipy 1.1 and 1.2 to ignore
 DeprecationWarnings from numpy 1.16. Addresses Bug#919929.
   * Use default gfortran-8 on s390x. unroll-loops was fixed in
 gcc-8 8.2.0-18. Closes: #906198, #915738.
Checksums-Sha1:
 644c3c6dbd9e228962157d56b844c41fd36f2da5 3191 python-scipy_1.1.0-3.dsc
 53e53efad76d0cc1326a238fba343fe463f66ff8 16436 
python-scipy_1.1.0-3.debian.tar.xz
Checksums-Sha256:
 489e05f8180818de18c152b26cd5423fbf8cc9da002a59da549b8180cc7094b8 3191 
python-scipy_1.1.0-3.dsc
 ef5dc35f349dae5d2b9e9d9a893372c2b1ad76d3c8337be8a96f56428902ea47 16436 
python-scipy_1.1.0-3.debian.tar.xz
Files:
 56e177823bea944113ef594cdc83d9fe 3191 python optional python-scipy_1.1.0-3.dsc
 5ebab4bfe5c9fd21589eecbf8a2182f1 16436 python optional 
python-scipy_1.1.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAlyBURwACgkQVz7x5L1a
AfoCXhAAs/BocZzwKZtLfrUK8G2onHAZNsgnyUoPlFMK2jy3XRYPX05/OqvBa6cs
6osHzYLMSRH9lRVKf8psJBTX0dzZoxSKzHxYXBg17OoBJ6O2Nr/sA5Sc2XtblTKG
u+7I8VsGVc05l1M40t/DacQpyzY7UJHOqyl1S44CLZHVfYql4OzRZo6I8FOROKrw
XVIAQV5cGUrvp/Uc0vAEN0+Z2AdQ9wwxRDgbZ184pqgt5koXAJWNmPdjD3r5BIzh
EvtKint+BYrRs1hfd2V745bDXNlx051gL0CLzjMGI8S3ghmTCo7LktoQLga6cxd7
I36Jcfv/vvR5+P2Ju6a0Oc9MxzMm/sxjx+LM0NQwaqWzXss3VZaRZuMEJ3AWMm4+
G3lVpygfv4zzhTcglT1JJy7I+O7cgXzii1bkqV1jN2dK3NdsAXhOoXOrbQbQZmg3
IjvUQclKBj8rYcRBI+m53zUV6zKaK3i5cSypmfcZ4DXc850l5n+dWf6eUpJVPNYI
YZNhPEm6XeFchyp/TD9wj/2LEHRmXOU+c6wYfddt4tIoCA2Cow13qowBOOGzf9A+
Q93Qco2+ZM8wkSNIe70b0hAga+Mbi8K7guwpa4fJqfz/xDHaFGxdb520s3Al1T+t
CbQf/Xbzb1+FcSMsYlRKd011ilLa0jPhWrvLDl+O9sm6gbdT8VE=
=CdTQ
-END PGP SIGNATURE End Message ---

Bug#906198: marked as done ([python-scipy] causes FTBFS on of imexam: scipy.optimize.leastsq fails on S390x)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 17:34:51 +
with message-id 
and subject line Bug#906198: fixed in python-scipy 1.1.0-3
has caused the Debian Bug report #906198,
regarding [python-scipy] causes FTBFS on of imexam: scipy.optimize.leastsq 
fails on S390x
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.)


-- 
906198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-scipy
Version: 1.1.0-1+b1
Severity: serious
Affects: python3-astropy, python-astropy, python-imexam, python3-imexam

Dear maintainer,

The following simple test fails on s390x:

---8<--
import numpy as np
from scipy.optimize import leastsq

y = np.array([0., 1., 1., 2., 1., 1., 0.])
x = np.arange(len(y))

def func(par):
return par[2] * np.exp(-(x - par[0])**2/par[1]) - y

print(leastsq(func, [0,1,0]))
---8<--

The expected result is

(array([3., 4.42280548, 1.67210345]), 1)

while on S390x, one gets

(array([0., 1., 0.34027645]), 3)

This caused FTBFS of astropy [1], where I had to disable
the failing tests in astropy. Note that the original version
(1.1.0-1) did not have this problem [2] (the other problems are
irrelevant here).

Currently that issue causes an FTBFS on imexam [3], which is
the reason for the severity.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=astropy=s390x=3.0.3-4=1533023784=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=astropy=s390x=3.0.3-3%2Bb1=1532416286=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=imexam=s390x=0.8.0-2%2Bb1=1534266846=0

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: python-scipy
Source-Version: 1.1.0-3

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated python-scipy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Mar 2019 00:31:29 +0800
Source: python-scipy
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Drew Parsons 
Closes: 906198 915738
Changes:
 python-scipy (1.1.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Debian patch ignore_DeprecationWarning_diff1.2.patch applies diff
 of pytest.ini between scipy 1.1 and 1.2 to ignore
 DeprecationWarnings from numpy 1.16. Addresses Bug#919929.
   * Use default gfortran-8 on s390x. unroll-loops was fixed in
 gcc-8 8.2.0-18. Closes: #906198, #915738.
Checksums-Sha1:
 644c3c6dbd9e228962157d56b844c41fd36f2da5 3191 python-scipy_1.1.0-3.dsc
 53e53efad76d0cc1326a238fba343fe463f66ff8 16436 
python-scipy_1.1.0-3.debian.tar.xz
Checksums-Sha256:
 489e05f8180818de18c152b26cd5423fbf8cc9da002a59da549b8180cc7094b8 3191 
python-scipy_1.1.0-3.dsc
 ef5dc35f349dae5d2b9e9d9a893372c2b1ad76d3c8337be8a96f56428902ea47 16436 
python-scipy_1.1.0-3.debian.tar.xz
Files:
 56e177823bea944113ef594cdc83d9fe 3191 python optional python-scipy_1.1.0-3.dsc
 5ebab4bfe5c9fd21589eecbf8a2182f1 16436 python optional 
python-scipy_1.1.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAlyBURwACgkQVz7x5L1a
AfoCXhAAs/BocZzwKZtLfrUK8G2onHAZNsgnyUoPlFMK2jy3XRYPX05/OqvBa6cs
6osHzYLMSRH9lRVKf8psJBTX0dzZoxSKzHxYXBg17OoBJ6O2Nr/sA5Sc2XtblTKG
u+7I8VsGVc05l1M40t/DacQpyzY7UJHOqyl1S44CLZHVfYql4OzRZo6I8FOROKrw
XVIAQV5cGUrvp/Uc0vAEN0+Z2AdQ9wwxRDgbZ184pqgt5koXAJWNmPdjD3r5BIzh
EvtKint+BYrRs1hfd2V745bDXNlx051gL0CLzjMGI8S3ghmTCo7LktoQLga6cxd7
I36Jcfv/vvR5+P2Ju6a0Oc9MxzMm/sxjx+LM0NQwaqWzXss3VZaRZuMEJ3AWMm4+
G3lVpygfv4zzhTcglT1JJy7I+O7cgXzii1bkqV1jN2dK3NdsAXhOoXOrbQbQZmg3
IjvUQclKBj8rYcRBI+m53zUV6zKaK3i5cSypmfcZ4DXc850l5n+dWf6eUpJVPNYI
YZNhPEm6XeFchyp/TD9wj/2LEHRmXOU+c6wYfddt4tIoCA2Cow13qowBOOGzf9A+
Q93Qco2+ZM8wkSNIe70b0hAga+Mbi8K7guwpa4fJqfz/xDHaFGxdb520s3Al1T+t
CbQf/Xbzb1+FcSMsYlRKd011ilLa0jPhWrvLDl+O9sm6gbdT8VE=
=CdTQ
-END PGP

Bug#912150: marked as done (imexam: FTBFS in s390x: AssertionError during tests)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 17:34:51 +
with message-id 
and subject line Bug#906198: fixed in python-scipy 1.1.0-3
has caused the Debian Bug report #906198,
regarding imexam: FTBFS in s390x: AssertionError during tests
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.)


-- 
906198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imexam
Version: 0.8.0-2
Severity: serious
Tags: ftbfs

Dear maintainer,

your package FTBFSed in unstable in s390x during the python3.7 rebuilds.

Full log at:
https://buildd.debian.org/status/fetch.php?pkg=imexam=s390x=0.8.0-2%2Bb1=1539160229=0

= test session starts ==
platform linux2 -- Python 2.7.15+, pytest-3.6.4, py-1.6.0, pluggy-0.6.0 -- 
/usr/bin/python2.7
cachedir: .

Running tests with imexam version 0.8.0.
Running tests in imexam docs.

Date: 2018-10-10T08:30:18

Platform: Linux-4.9.0-8-s390x-s390x-with-debian-buster-sid

Executable: /usr/bin/python2.7

Full Python Version:
2.7.15+ (default, Aug 31 2018, 11:56:52)
[GCC 8.2.0]

encodings: sys: ascii, locale: ANSI_X3.4-1968, filesystem: ANSI_X3.4-1968, 
unicode bits: 20
byteorder: big
float info: dig: 15, mant_dig: 15

Numpy: 1.14.5
Scipy: 1.1.0
Matplotlib: 2.2.2
Astropy: 2.0.8
astropy_helpers: 2.0.7
Using Astropy options: remote_data: none.

rootdir: /tmp/imexam-test-bHM9cC/lib/python2.7/site-packages, inifile: setup.cfg
collecting ... collected 10 items

imexam/tests/test_imexamine.py::test_column_plot PASSED  [ 10%]
imexam/tests/test_imexamine.py::test_line_plot PASSED[ 20%]
imexam/tests/test_imexamine.py::test_aper_phot SKIPPED   [ 30%]
imexam/tests/test_imexamine.py::test_line_fit FAILED [ 40%]
imexam/tests/test_imexamine.py::test_column_fit FAILED   [ 50%]
imexam/tests/test_imexamine.py::test_gauss_center FAILED [ 60%]
imexam/tests/test_imexamine.py::test_radial_profile PASSED   [ 70%]
imexam/tests/test_imexamine.py::test_radial_profile_background SKIPPED   [ 80%]
imexam/tests/test_imexamine.py::test_radial_profile_pixels FAILED[ 90%]
imexam/tests/test_imexamine.py::test_curve_of_growth SKIPPED [100%]

=== FAILURES ===
 test_line_fit _

def test_line_fit():
"""Fit a Gaussian1D line to the data."""
plots = Imexamine()
plots.set_data(test_data)
fit = plots.line_fit(50, 50, form='Gaussian1D', genplot=False)
amp = 2.8152269683542137
mean = 49.45671107821953
stddev = 13.051081779478146

>   assert_allclose(amp, fit.amplitude, 1e-6)
E   AssertionError:
E   Not equal to tolerance rtol=1e-06, atol=0
E
E   (mismatch 100.0%)
Ex: array(2.815227)
Ey: array(1.018721)

imexam/tests/test_imexamine.py:80: AssertionError
- Captured stdout call -
using model: 
Name: Gaussian1D
Inputs: (u'x',)
Outputs: (u'y',)
Fittable parameters: ('amplitude', 'mean', 'stddev')
xc=49.402184yc=49.402184
-- Captured log call ---
imexamine.py   625 INFO using model: 
Name: Gaussian1D
Inputs: (u'x',)
Outputs: (u'y',)
Fittable parameters: ('amplitude', 'mean', 'stddev')
imexamine.py   946 INFO xc=49.402184yc=49.402184
___ test_column_fit 

def test_column_fit():
"""Fit a Gaussian1D column to the data."""
plots = Imexamine()
plots.set_data(test_data)
fit = plots.column_fit(50, 50, form='Gaussian1D', genplot=False)
amp = 2.8285560281694115
mean = 49.42625526973088
stddev = 12.791137635400535

>   assert_allclose(amp, fit.amplitude, 1e-6)
E   AssertionError:
E   Not equal to tolerance rtol=1e-06, atol=0
E
E   (mismatch 100.0%)
Ex: array(2.828556)
Ey: array(1.009302)

imexam/tests/test_imexamine.py:94: AssertionError
- Captured stdout call -
using model: 
Name: Gaussian1D
Inputs: (u'x',)
Outputs: (u'y',)
Fittable parameters: ('amplitude', 'mean', 'stddev')
xc=49.402214yc=49.402214
-- Captured log call ---
imexamine.py   785 INFO using

Bug#915738: marked as done (python-scipy should use the default gfortran on s390x)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 17:34:51 +
with message-id 
and subject line Bug#915738: fixed in python-scipy 1.1.0-3
has caused the Debian Bug report #915738,
regarding python-scipy should use the default gfortran on s390x
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.)


-- 
915738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-scipy
Version: 1.1.0-2
Severity: serious
Tags: sid buster

Please use the default GCC for the package so that we can remove GCC 7 for the
buster release.
--- End Message ---
--- Begin Message ---
Source: python-scipy
Source-Version: 1.1.0-3

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated python-scipy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Mar 2019 00:31:29 +0800
Source: python-scipy
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Drew Parsons 
Closes: 906198 915738
Changes:
 python-scipy (1.1.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Debian patch ignore_DeprecationWarning_diff1.2.patch applies diff
 of pytest.ini between scipy 1.1 and 1.2 to ignore
 DeprecationWarnings from numpy 1.16. Addresses Bug#919929.
   * Use default gfortran-8 on s390x. unroll-loops was fixed in
 gcc-8 8.2.0-18. Closes: #906198, #915738.
Checksums-Sha1:
 644c3c6dbd9e228962157d56b844c41fd36f2da5 3191 python-scipy_1.1.0-3.dsc
 53e53efad76d0cc1326a238fba343fe463f66ff8 16436 
python-scipy_1.1.0-3.debian.tar.xz
Checksums-Sha256:
 489e05f8180818de18c152b26cd5423fbf8cc9da002a59da549b8180cc7094b8 3191 
python-scipy_1.1.0-3.dsc
 ef5dc35f349dae5d2b9e9d9a893372c2b1ad76d3c8337be8a96f56428902ea47 16436 
python-scipy_1.1.0-3.debian.tar.xz
Files:
 56e177823bea944113ef594cdc83d9fe 3191 python optional python-scipy_1.1.0-3.dsc
 5ebab4bfe5c9fd21589eecbf8a2182f1 16436 python optional 
python-scipy_1.1.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAlyBURwACgkQVz7x5L1a
AfoCXhAAs/BocZzwKZtLfrUK8G2onHAZNsgnyUoPlFMK2jy3XRYPX05/OqvBa6cs
6osHzYLMSRH9lRVKf8psJBTX0dzZoxSKzHxYXBg17OoBJ6O2Nr/sA5Sc2XtblTKG
u+7I8VsGVc05l1M40t/DacQpyzY7UJHOqyl1S44CLZHVfYql4OzRZo6I8FOROKrw
XVIAQV5cGUrvp/Uc0vAEN0+Z2AdQ9wwxRDgbZ184pqgt5koXAJWNmPdjD3r5BIzh
EvtKint+BYrRs1hfd2V745bDXNlx051gL0CLzjMGI8S3ghmTCo7LktoQLga6cxd7
I36Jcfv/vvR5+P2Ju6a0Oc9MxzMm/sxjx+LM0NQwaqWzXss3VZaRZuMEJ3AWMm4+
G3lVpygfv4zzhTcglT1JJy7I+O7cgXzii1bkqV1jN2dK3NdsAXhOoXOrbQbQZmg3
IjvUQclKBj8rYcRBI+m53zUV6zKaK3i5cSypmfcZ4DXc850l5n+dWf6eUpJVPNYI
YZNhPEm6XeFchyp/TD9wj/2LEHRmXOU+c6wYfddt4tIoCA2Cow13qowBOOGzf9A+
Q93Qco2+ZM8wkSNIe70b0hAga+Mbi8K7guwpa4fJqfz/xDHaFGxdb520s3Al1T+t
CbQf/Xbzb1+FcSMsYlRKd011ilLa0jPhWrvLDl+O9sm6gbdT8VE=
=CdTQ
-END PGP SIGNATURE End Message ---

Bug#923926: found 923926 in 1.3.5b-1, closing 923926

2019-03-07 Thread Salvatore Bonaccorso

found 923926 1.3.5b-1
close 923926 1.3.5d-1
thanks

Processed: tagging 923926

2019-03-07 Thread Debian Bug Tracking System

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

> tags 923926 + upstream fixed-upstream
Bug #923926 {Done: Salvatore Bonaccorso } [proftpd-basic] 
proftpd-basic: proftpd 1.3.5b has memory leaks, allows Denial-Of-Service attack
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Processed: found 923926 in 1.3.5b-1, closing 923926

2019-03-07 Thread Debian Bug Tracking System

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

> found 923926 1.3.5b-1
Bug #923926 [proftpd-basic] proftpd-basic: proftpd 1.3.5b has memory leaks, 
allows Denial-Of-Service attack
Marked as found in versions proftpd-dfsg/1.3.5b-1.
> close 923926 1.3.5d-1
Bug #923926 [proftpd-basic] proftpd-basic: proftpd 1.3.5b has memory leaks, 
allows Denial-Of-Service attack
Marked as fixed in versions proftpd-dfsg/1.3.5d-1.
Bug #923926 [proftpd-basic] proftpd-basic: proftpd 1.3.5b has memory leaks, 
allows Denial-Of-Service attack
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#923959: afflib: FTBFS (dh_makeshlibs fails)

2019-03-07 Thread Santiago Vila

Package: src:afflib
Version: 3.7.17-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with autoreconf
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:20: installing './compile'
configure.ac:26: installing './config.guess'

[... snipped ...]

make[2]: Leaving directory '/<>'
chrpath -d debian/tmp/usr/bin/*
set -e; for file in `ls debian/tmp/usr/lib/*/*.la`; do \
sed -i "/dependency_libs/ s/'.*'/''/" $file ; \
done
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installman -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_strip -a
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/<>'
dh_makeshlibs -- -v3.7.17
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/libafflib0v5/DEBIAN/symbols doesn't match 
completely debian/libafflib0v5.symbols
--- debian/libafflib0v5.symbols (libafflib0v5_3.7.17_amd64)
+++ dpkg-gensymbolsSIEKs1   2019-03-07 14:37:18.703845582 +
@@ -373,9 +373,13 @@
  
(optional)_ZNSt6vectorIPN2s36BucketESaIS2_EE19_M_emplace_back_auxIJS2_EEEvDpOT_@Base
 3.7.17
  
_ZNSt6vectorIPN2s38ContentsESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.7.16
  
(optional)_ZNSt6vectorIPN2s38ContentsESaIS2_EE19_M_emplace_back_auxIJS2_EEEvDpOT_@Base
 3.7.17
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueIS5_EESt4pairISt17_Rb_tree_iteratorIS5_EbEOT_@Base
 3.7.16
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 3.7.17
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 3.7.17
+#MISSING: 3.7.17# 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueIS5_EESt4pairISt17_Rb_tree_iteratorIS5_EbEOT_@Base
 3.7.16
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 3.7.16
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSG_PSt13_Rb_tree_nodeIS8_E@Base
 3.7.16
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOS5_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 3.7.17
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 3.7.17
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 3.7.16
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 3.7.16
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 3.7.16
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:27: override_dh_makeshlibs] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/afflib.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

Bug#923743: marked as done (pcre3: FTBFS (dh_makeshlibs fails))

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 16:21:44 +
with message-id 
and subject line Bug#923743: fixed in pcre3 2:8.39-12
has caused the Debian Bug report #923743,
regarding pcre3: FTBFS (dh_makeshlibs fails)
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.)


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

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
debian/jit-test.c:9:4: warning: #warning JIT enabled [-Wcpp]
   #warning JIT enabled
^~~
debian/jit-test.c:9:4: warning: #warning JIT enabled [-Wcpp]
   #warning JIT enabled
^~~
dh_testdir
# Add here commands to configure the package.
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'

[... snipped ...]

dh_testroot -a
dh_install -a
# This man page is in the main package, don't want it in -dev
rm debian/libpcre3-dev/usr/share/man/man3/pcrepattern.3
# Move actual library to /lib
mkdir -p debian/libpcre3/lib/x86_64-linux-gnu
mv debian/libpcre3/usr/lib/x86_64-linux-gnu/libpcre.so.* 
debian/libpcre3/lib/x86_64-linux-gnu
ln -sf /lib/x86_64-linux-gnu/libpcre.so.3 
debian/libpcre3-dev/usr/lib/x86_64-linux-gnu/libpcre.so
# we never need to reference the library path in pcre-config on
# Debian, so clip it out so that the script will be multiarch-safe.
sed -i -e"s,/x86_64-linux-gnu,,g" debian/libpcre3-dev/usr/bin/pcre-config
dh_link -a
dh_installdocs -a
dh_installexamples -a
dh_installman -a
dh_installinfo -a
dh_installchangelogs -a ChangeLog
dh_strip -a --dbg-package=libpcre3-dbg
dh_compress -a
dh_fixperms -a
sed -e 's/JIT//' debian/libpcre3.symbols.in > debian/libpcre3.symbols
sed -e 's/JIT//' debian/libpcre16-3.symbols.in > debian/libpcre16-3.symbols
sed -e 's/JIT//' debian/libpcre32-3.symbols.in > debian/libpcre32-3.symbols
dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
--- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
+++ dpkg-gensymbolsV2Wi2n   2019-03-04 12:36:00.103243818 +
@@ -80,9 +80,9 @@
  (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
-#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
+#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  (c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
-#MISSING: 2:8.39-9# (c++|optional=STL)"void std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
+#MISSING: 2:8.39-11# (c++|optional=STL)"void std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  (c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
  (c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
- (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
+#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:116: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

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

Bug#923957: /lib/runit/run_sysv_scripts shouldn't use 'sh -e'

2019-03-07 Thread Andras Korn

Package: runit-init
Version: 2.1.2-22
Severity: critical

Hi,

The supplied "/etc/runit/1" calls "/lib/runit/run_sysv_scripts /etc/rcS.d"
during boot.

/lib/runit/run_sysv_scripts runs under "sh -eu", which has the effect that
if any initscript exits unsuccesfully, all subsequent scripts are skipped.

This can lead to, for example, the "networking" initscript not being
started, which then results in no connectivity for the box and thus no way
to log in remotely. (This is my justification for the 'critical' severity:
"breaks the entire system".)

I think runit-init should do what /etc/init.d/rc does: log failures and
continue.

Thanks,

András

-- 
  It's not enough to have no opinion. You must also be unable to express it.

Bug#923955: libncl: FTBFS (dh_makeshlibs fails)

2019-03-07 Thread Santiago Vila

Package: src:libncl
Version: 2.1.21+git20180827.c71b264-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'
libtoolize: copying file 'config/ltsugar.m4'
libtoolize: copying file 'config/ltversion.m4'
libtoolize: copying file 'config/lt~obsolete.m4'
configure.ac:28: installing 'config/compile'
configure.ac:21: installing 'config/missing'

[... snipped ...]

+#MISSING: 2.1.21+git20180827.c71b264-1# 
_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE17_M_insert_unique_IRKS0_NS6_11_Alloc_nodeEEESt17_Rb_tree_iteratorIS0_ESt23_Rb_tree_const_iteratorIS0_EOT_RT0_@Base
 2.1.21+git20171002.4becff7
  
_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE24_M_get_insert_unique_posERKS0_@Base
 2.1.18
  
(optional)_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS0_ERKS0_@Base
 2.1.21+git20171002.4becff7
  
_ZNSt8_Rb_treeI19NxsCharacterPatternS0_St9_IdentityIS0_ESt4lessIS0_ESaIS0_EE8_M_eraseEPSt13_Rb_tree_nodeIS0_E@Base
 2.1.18
@@ -1122,7 +1126,7 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 2.1.18
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EEaSERKSB_@Base
 2.1.18
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE11equal_rangeERS7_@Base
 2.1.21+git20171002.4becff7
- 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base
 2.1.18
+#MISSING: 2.1.21+git20180827.c71b264-1# 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base
 2.1.18
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE17_M_emplace_uniqueIJS6_IS5_S8_S6_ISt17_Rb_tree_iteratorIS9_EbEDpOT_@Base
 2.1.21+git20171002.4becff7
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE4findERS7_@Base
 2.1.21+git20171002.4becff7
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE5eraseERS7_@Base
 2.1.18
@@ -1130,7 +1134,7 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE8_M_eraseEPSt13_Rb_tree_nodeIS9_E@Base
 2.1.18
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EEaSERKSF_@Base
 2.1.21+git20171002.4becff7
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE11equal_rangeERS7_@Base
 2.1.21+git20171002.4becff7
- 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base
 2.1.18
+#MISSING: 2.1.21+git20180827.c71b264-1# 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base
 2.1.18
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE17_M_emplace_uniqueIJS6_IS5_S8_S6_ISt17_Rb_tree_iteratorIS9_EbEDpOT_@Base
 2.1.21+git20171002.4becff7
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE4findERS7_@Base
 2.1.21+git20171002.4becff7
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE5eraseERS7_@Base
 2.1.18
@@ -1203,8 +1207,8 @@

Bug#923954: libbpp-seq: FTBFS (dh_makeshlibs fails)

2019-03-07 Thread Santiago Vila

Package: src:libbpp-seq
Version: 2.4.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- bpp-core 4.1.0 found:

[... snipped ...]

  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base
 2.4.1
@@ -1851,6 +1853,7 @@
  
_ZNSt8_Rb_treeIcSt4pairIKcdESt10_Select1stIS2_ESt4lessIcESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIcSt4pairIKcdESt10_Select1stIS2_ESt4lessIcESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIcSt4pairIKcdESt10_Select1stIS2_ESt4lessIcESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base
 2.4.1-2
  
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIdSt4pairIKdmESt10_Select1stIS2_ESt4lessIdESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
@@ -1873,6 +1876,7 @@
  
_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSA_PSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base
 2.4.1-2
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
@@ -1884,10 +1888,11 @@
  
_ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 2.4.1
  
_ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSA_PSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
+ 
_ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOmEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base
 2.4.1-2
  
_ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
- 
_ZSt11__remove_ifIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops16_Iter_equals_valIKiEEET_SB_SB_T0_@Base
 2.4.1
+#MISSING: 2.4.1-2#

Bug#885240: marked as done (libmsnumpress: FTBFS: dot and qhelpgenerator not found)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 15:49:31 +
with message-id 
and subject line Bug#885240: fixed in libmsnumpress 1.0.0-3
has caused the Debian Bug report #885240,
regarding libmsnumpress: FTBFS: dot and qhelpgenerator not found
to be marked as done.

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

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


-- 
885240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmsnumpress
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of libmsnumpress in minimal environments (as on the
autobuilders) have been failing:

  mkdir -p debian/build && doxygen debian/Doxyfile
  warning: the dot tool could not be found at /usr/bin/dot
  [...]
  sh: 1: dot: not found
  [...]
  error: problems opening map file 
/<>/debian/build/doxygen/html/MSNumpress_8cpp__incl.map for 
inclusion in the docs!
  If you installed Graphviz/dot after a previous failing run, 
  try deleting the output directory and rerun doxygen.
  [...]
  sh: 1: /usr/bin/qhelpgenerator: not found
  error: failed to run qhelpgenerator on index.qhp
  [...]
  find debian/build/doxygen/html -name "*.md5" | xargs rm
  find debian/build/doxygen/html -name "*.map" | xargs rm
  rm: missing operand
  Try 'rm --help' for more information.
  debian/rules:30: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 123
  make[1]: Leaving directory '/<>'
  debian/rules:12: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

Given that the docs have their own binary package anyway, I'd suggest
splitting override_dh_auto_build into -arch and -indep variants and
splitting out a Build-Depends Indep for doxygen, libjs-jquery, and
anything else you need when building documentation but left out
earlier.

Thanks!

FTR, I'm filing this bug as a regression because it would affect any
needed binary-only rebuilds for amd64.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: libmsnumpress
Source-Version: 1.0.0-3

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

Debian distribution maintenance software
pp.
Filippo Rusconi  (supplier of updated libmsnumpress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Mar 2019 16:16:13 +0100
Source: libmsnumpress
Binary: libmsnumpress-dev libmsnumpress-dev-doc libmsnumpress1 
libmsnumpress1-dbgsym
Architecture: source all amd64
Version: 1.0.0-3
Distribution: unstable
Urgency: low
Maintainer: The Debichem Group 
Changed-By: Filippo Rusconi 
Description:
 libmsnumpress-dev - Numeric data compression for mass spectrometry (devel 
files)
 libmsnumpress-dev-doc - set of programs to perform proteomics data analyses 
(doc)
 libmsnumpress1 - Numeric data compression for mass spectrometry (runtime)
Closes: 885240
Changes:
 libmsnumpress (1.0.0-3) unstable; urgency=low
 .
   * Standards-Version: 4.3.0.
   * d/copyright: fix order of stanzas.
 .
   * Add qttools5-dev-tools and qtchooser for qhelpgenerator.
   * Add graphviz for dot binary.
   * Closes: #885240 (thanks to "Aaron M. Ucko" ).
Checksums-Sha1:
 aa8285dae19171c8ec9242ac3accbf1689126d04 2228 libmsnumpress_1.0.0-3.dsc
 18437ed085b3f061bc004ba8b5d237132038836b 23556 
libmsnumpress_1.0.0-3.debian.tar.xz
 4df7e52f04d9df8afcc19b49c59f7a2d666db519 1215756 
libmsnumpress-dev-doc_1.0.0-3_all.deb
 7134ffae6efefb9f815e239e11a6460e7da7ce2b 4940 
libmsnumpress-dev_1.0.0-3_amd64.deb
 75808730b62127d51fd72c905f7074272c304663 41288 
libmsnumpress1-dbgsym_1.0.0-3_amd64.deb
 7bf93b3cef980de1c91aaf5ac58011547f233dad 10596 libmsnumpress1_1.0.0-3_amd64.deb
 64d32debb349d1b631eefe7b3f6b14b0abf07e01 11258 
libmsnumpress_1.0.0-3_amd64.buildinfo
Checksums-Sha256:
 863de53067ece32c3efa110d5a1233ec8291d97406bdc392c4d67edbeb74efa3 2228 
libmsnumpress_1.0.0-3.dsc

Bug#923541: libdbd-mysql-perl: FTBFS against mariadb-10.3 1:10.3.13-1

2019-03-07 Thread gregor herrmann

On Fri, 01 Mar 2019 18:30:34 +0100, gregor herrmann wrote:

> libdbd-mysql-perl fails its tests with
> 
> t/rt118977-zerofill.t ... 
> 1..8
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> not ok 8
> #   Failed test at t/rt118977-zerofill.t line 22.
> #  got: '1'
> # expected: '1'
> # Looks like you failed 1 test of 8.
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/8 subtests 
> 
> when built against mariadb-10.3 1:10.3.13-1.

Good news: There's a preliminary patch in the upstream issue:
https://github.com/perl5-dbi/DBD-mysql/issues/304
https://github.com/perl5-dbi/DBD-mysql/pull/308
which seems to work for the Debian package.

I've pushed this to salsa but I'd like to wait a day or two and see
of the PR gets merged and/or if other solutions arise (there's a
second patch around, and also a MariaDB bug report:
https://jira.mariadb.org/browse/MDEV-18823 )


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: U2: Zooropa


signature.asc
Description: Digital Signature

Bug#849308: state of wireguard mainline inclusion?

2019-03-07 Thread Michael Prokop

* Antoine Beaupré [Wed Sep 26, 2018 at 08:26:07PM -0400]:

> I still think this bug should be closed and we should let wireguard
> migrate in testing. I'm sure the relteam would be mooore than happy to
> remove it at a moment's notice before or during the freeze if we need
> to.

> In other words, I feel this bug was filed prematurely. :)

So sadly wireguard didn't make it into buster. :(
Are there any plans for providing backports for stretch and/or buster?

regards,
-mika-


signature.asc
Description: Digital signature

Processed: severity of 922399 is serious, closing 922399

2019-03-07 Thread Debian Bug Tracking System

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

> # -march is RC regarless of FTBFS
> severity 922399 serious
Bug #922399 [isospec] isospec : FTBS - -march=native parameter invalid
Severity set to 'serious' from 'important'
> # already fixed…
> close 922399
Bug #922399 [isospec] isospec : FTBS - -march=native parameter invalid
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#923609: Binary incompatibility in libgdbm6

2019-03-07 Thread Dmitry Bogatov



[2019-03-05 17:44] Sergey Poznyakoff 
> Hello,
>
> Investigation of the attached file has shown that it has been created
> by gdbm 1.8.3 compiled without large file support (sizeof(off_t) == 4).
> In contrast, gdbm 1.18.1 was compiled with large file support enabled,
> which naturally lead to the observed behavior. Recompile it with the
> --disable-largefile flag and it will be able to read the file.

Thank you, Sergey. Does incompatibility goes other way too, that version
without LFS support is incapable of reading file, created with LFS
version?

I consider providing statically-linked, LFS-disabled version of
gdbm_{load,dump,tool}, so user with database, created on stretch could
do `gdbm_dump old.gdbm | gdbm_load new.gdbm'. Opinions?

Oh, we may need to ask release team, for we are too close to hard-freeze.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#919373: marked as done (libmariadb-dev-compat: lacks MYSQL_SERVER_VERSION causing FTBFS)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 7 Mar 2019 14:34:43 +0100
with message-id 
and subject line Re: libmariadb-dev-compat: lacks MYSQL_SERVER_VERSION causing 
FTBFS
has caused the Debian Bug report #919373,
regarding libmariadb-dev-compat: lacks MYSQL_SERVER_VERSION causing FTBFS
to be marked as done.

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

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


-- 
919373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kannel
Version: 1.4.5-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

kannel FTBFS against mariadb-10.3:

gcc -D_REENTRANT=1 -I. -Igw -g -O2 -fdebug-prefix-map=/build/kannel-1.4.5=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_XOPEN_SOURCE=600 
-D_BSD_SOURCE -D_DEFAULT_SOURCE -D_FILE_OFFSET_BITS=64 -D_
LARGE_FILES= -I/usr/include/libxml2  -Wall -Wmissing-prototypes 
-Wmissing-declarations -Wnested-externs -Winline -Wformat -Wformat-security 
-Wmissing-format-attribute -I/usr/include -I/usr/include/mariadb -I/usr/
include/mariadb/mysql -I/usr/include/postgresql -I/usr/include/hiredis 
-I/usr/include -o gwlib/utils.o -c gwlib/utils.c
In file included from gwlib/utils.c:98:
/usr/include/mariadb/mysql_version.h:3:2: warning: #warning This file should 
not be included by clients, include only  [-Wcpp]
 #warning This file should not be included by clients, include only 
  ^~~
gwlib/utils.c: In function 'version_report_string':
gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared (first use in 
this function); did you mean 'MYSQL_PS_CONVERSION'?
  MYSQL_SERVER_VERSION, mysql_get_client_info(),
  ^~~~
  MYSQL_PS_CONVERSION
gwlib/utils.c:602:14: note: each undeclared identifier is reported only once 
for each function it appears in
gwlib/utils.c:622:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
make[1]: *** [Makefile:226: gwlib/utils.o] Error 1


Cheers,

Andreas


kannel_1.4.5-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1:10.3.13-1

On Tue, 5 Mar 2019 10:10:48 +0100 Sergei Golubchik  wrote:
> 
> Already fixed in 10.3.13
> (libmariadb v3.0.9)

So, let's tell the bts. (done so with this e-mail to -done@b.d.o)

Paul



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#853016: here is more polite libpam0g dialog

2019-03-07 Thread 積丹尼 Dan Jacobson

See how this other package takes a more cautions approach:

──┤ Configuring libpam0g:amd64 ├───
   │ Most services that use PAM need to be restarted to use modules built for 
this new version of libpam.  Please review the following space-separated   │
   │ list of init.d scripts for services to be restarted now, and correct it if 
needed.  │
   │
 │
   │ Services to restart for PAM library upgrade:   
 │
   │
 │
   │ exim4 cron 
atd_
 │
   │
 │
   │   


Just remove all the restart code, please.

Bug#923226: Compiling shader doesn't work - game doesn't work

2019-03-07 Thread Julien Puydt


Hi,

Le 07/03/2019 à 09:51, Simon McVittie a écrit :

On Tue, 26 Feb 2019 at 07:51:27 +, Simon McVittie wrote:

Does the opengl1 renderer work? (See /usr/share/doc/ioquake3/NEWS.Debian.gz)

If not, does an older version of ioquake3 from snapshot.debian.org work?


Please could you try this on your affected hardware?

If opengl1 works, I can change the default renderer back to opengl1
for buster, but I'm not going to do that without confirmation that it
solves the problem.


Just changing the ioquake3 binary package (which makes dpkg complain 
about ioquake3-server, but it's normal):

1.36+u20181017.09166ba~dfsg-2 works
1.36+u20181222.e5da13f~dfsg-1 fails

Running (with 1.36+u20181222.e5da13f~dfsg-1):
  openarena +seta cl_renderer opengl1
works too.

Indeed the opengl1 renderer looks like the more failsafe default.

JP

Processed: Re: Bug#923009: seafile: CVE-2013-7469

2019-03-07 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 important
Bug #923009 [src:seafile] seafile: CVE-2013-7469
Severity set to 'important' from 'grave'
> tags -1 - buster-ignore
Bug #923009 [src:seafile] seafile: CVE-2013-7469
Removed tag(s) buster-ignore.

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

Bug#923009: seafile: CVE-2013-7469

2019-03-07 Thread Salvatore Bonaccorso

Control: severity -1 important
Control: tags -1 - buster-ignore

Hi Christoph,

On Thu, Mar 07, 2019 at 10:16:46AM +0100, Christoph Martin wrote:
> Hi Salvatore,
> 
> Am 06.03.19 um 23:15 schrieb Salvatore Bonaccorso:
> > Hi Christoph,
> > 
> > On Tue, Mar 05, 2019 at 12:12:31PM +0100, Christoph Martin wrote:
> > 
> > Yes I think we can agree on that!
> > 
> 
> So, I'd like to lower the severity to important,
> 
> > Quick note on the buster-ignore tag addition, keep in mind that this
> > is technically only to be used/added by release managers themself, but
> > maintainers can obviously suggest that to the release managers, cf.
> > https://www.debian.org/Bugs/Developer#tags
> 
> Sorry for that. Is it ok to leave the tag or is a severity change to
> important better? The autoremove flag is still active.

Yes that sounds good and just doing so now, and as well removing the
tag buster-ignore as raised by Ivo on IRC.

Btw, the autoremove flag should have disaperared otherwise next.

Regards,
Salvatore

Bug#923930: FTBFS: FAIL test_chain (exit status: 1)

2019-03-07 Thread Ritesh Raj Sarraf

Source: heimdal
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

heimdal fails to build from source, both in Buster and Sid. It is
failing in one of the tests. Relevant snippet below and full build log
is accessible at:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/heimdal_7.5.0+dfsg-2.1.rbuild.log.gz

=
   Heimdal 7.5.0: lib/hx509/test-suite.log
=

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

.. contents:: :depth: 2

FAIL: test_chain


cert -> root
cert -> root
cert -> root
sub-cert -> root
sub-cert -> sub-ca -> root
sub-cert -> sub-ca
sub-cert -> sub-ca -> root
sub-cert -> sub-ca -> root
sub-cert -> sub-ca -> root
max depth 2 (ok)
max depth 1 (fail)
ocsp non-ca responder
ocsp ca responder
ocsp no-ca responder, missing cert
ocsp no-ca responder, missing cert, in pool
ocsp no-ca responder, keyHash
ocsp revoked cert
ocsp print reply resp1-ocsp-no-cert
ocsp print reply resp1-ca
ocsp print reply resp1-keyhash
ocsp print reply resp2
ocsp verify exists
ocsp verify not exists
ocsp verify revoked
crl non-revoked cert
FAIL test_chain (exit status: 1)

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

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

Bug#923698: gcc-mingw-w64 miscompiles PARI

2019-03-07 Thread Bill Allombert

On Thu, Mar 07, 2019 at 09:07:15AM +0100, Stephen Kitt wrote:
> Hi Bill,
> 
> On Mon, 4 Mar 2019 00:39:00 +0100, Bill Allombert  wrote:
> > Since the upgrade to 8.2.0-17, gcc-mingw-w64-x86-64 miscompiles PARI/GP.
> > 
> > 
> > The native linux version is fine though.
> > The bug is caused by longjmp causing wine to crash with
> > 
> > 0198:err:seh:setup_exception stack overflow 320 bytes in thread 0198 eip
> > 7bc9a41c esp 001314d0 stack 0x13-0x131000-0x33
> > 
> > when called in a function doing an unrelated setjmp _after_ the longjmp
> > (in other functions longjmp work fine), and it does not occurs with the
> > debug build.
> > 
> > One of the logs for the broken version is at
> > 
> > (the test-suite fails under wine).
> > I use the following kit to crossbuild:
> > https://pari.math.u-bordeaux.fr/pub/pari/windows/paricrossmingwkit.tgz
> > 
> > So if you have a suggestion...
> 
> I don’t have any practical suggestion right now, but given that there’s a
> test suite I’ll bisect to identify the source of the problem.

Thanks!
I tried __builtin_setjmp/__builtin_longjmp and while it seems to work
__builtin_longjmp only allows val to be 1, which would require to change
the code.

Cheers,
-- 
Bill. 

Imagine a large red swirl here.

Bug#923926: proftpd-basic: proftpd 1.3.5b has memory leaks, allows Denial-Of-Service attack

2019-03-07 Thread Subharo Bhikkhu

Package: proftpd-basic
Version: 1.3.5b-4
Severity: grave
Tags: security
Justification: renders package unusable

Dear Maintainer,

Debian Security has been notified.

The proftpd in Debian stable has memory leaks in it.  A malicious user, who has 
a valid username and password into the SSL-enabled proftpd server (even if just 
an anonymous user, if allowed), merely needs to upload a "Calibre Library" 
folder, containing a bunch of small ebooks, large to cause the server to a 
freeze.  In my case, with 512MB RAM, my Calibre Library folder needed to be 
only 13GB in size to cause the server to have a total hardware freeze.
The package proftpd-mod-vroot 0.9.4-1 might also have memory leaks in it, which 
I also have installed.

These memory leaks have been known about for a long time, but it seems I'm the 
first one to point out that it constitutes a DOS attack.

I believe these memory leaks got fixed in proftpd 1.3.5d:
https://github.com/proftpd/proftpd/issues/330#issuecomment-276891713
...however the version of proftpd in Debian stable is currently 1.3.5b-4.

Please also see here for more details, which is where this DOS attack was first 
discovered and announced publicly by me:
https://forum.armbian.com/topic/9692-nanopi-neo-2-memory-leak-in-proftpd-even-worse-if-ssl-encrypted/?do=findComment=73069

Note: downstream of proftpd is the OpenMediaVault project.  I'm an 
OpenMediaVault user, that's how I ran into this being a DOS.

-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

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

Versions of packages proftpd-basic depends on:
ii  adduser3.115
ii  debianutils4.8.1.1
ii  libacl12.2.52-3+b1
ii  libc6  2.24-11+deb9u4
ii  libcap21:2.25-1
ii  libmemcached11 1.0.18-4.1
ii  libmemcachedutil2  1.0.18-4.1
ii  libncurses56.0+20161126-1+deb9u2
ii  libpam-runtime 1.1.8-3.6
ii  libpam0g   1.1.8-3.6
ii  libpcre3   2:8.39-3
ii  libssl1.0.21.0.2q-1~deb9u1
ii  libtinfo5  6.0+20161126-1+deb9u2
ii  libwrap0   7.6.q-26
ii  lsb-base   9.20161125
ii  netbase5.4
ii  sed4.4-1
ii  ucf3.0036
ii  zlib1g 1:1.2.8.dfsg-5

proftpd-basic recommends no packages.

Versions of packages proftpd-basic suggests:
pn  openbsd-inetd | inet-superserver  
ii  openssl   1.1.0j-1~deb9u1
pn  proftpd-doc   
pn  proftpd-mod-geoip 
pn  proftpd-mod-ldap  
pn  proftpd-mod-mysql 
pn  proftpd-mod-odbc  
pn  proftpd-mod-pgsql 
pn  proftpd-mod-sqlite

-- no debconf information

Bug#905929: sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile

2019-03-07 Thread Michael Prokop

* Adrian Bunk [Sat Aug 11, 2018 at 11:33:28PM +0300]:
> Source: sysdig
> Version: 0.22.0-1
> Severity: serious

> https://buildd.debian.org/status/package.php?p=sysdig

> ...
> cd /<>/obj-aarch64-linux-gnu/userspace/libscap && /usr/bin/cc 
> -DHAS_CAPTURE -DK8S_DISABLE_THREAD -DPLATFORM_NAME=\"Linux\" 
> -I/<>/common  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -ggdb   -o 
> CMakeFiles/scap.dir/__/__/driver/fillers_table.c.o   -c 
> /<>/driver/fillers_table.c
> /<>/driver/syscall_table.c:54:3: error: '__NR_open' undeclared 
> here (not in a function); did you mean 'f_sys_open_x'?
>   [__NR_open - SYSCALL_TABLE_ID0] =   {UF_USED | 
> UF_NEVER_DROP, PPME_SYSCALL_OPEN_E, PPME_SYSCALL_OPEN_X},
>^

There's a patch available (found via
https://github.com/draios/sysdig/issues/1203) that's supposed to
address this:

  
https://github.com/sforshee/sysdig/commit/3248bf70d677abe6f60bb9f8275a774600ed77e8

regards,
-mika-


signature.asc
Description: Digital signature

Bug#923898: marked as done (giada: FTBFS with JUCE-5.4.1: not linking against libcurl)

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 10:19:18 +
with message-id 
and subject line Bug#923898: fixed in giada 0.15.2+ds1-2
has caused the Debian Bug report #923898,
regarding giada: FTBFS with JUCE-5.4.1: not linking against libcurl
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.)


-- 
923898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: giada
Version: 0.15.2+ds1-1
Severity: serious
Justification: ftbfs

Dear Maintainer,

even with a fixed JUCE-5.4.1 (providing all the required opcodes for building a
plugin host), giada FTBFS with a number of unresolved symbols related to curl.

Either new JUCE requires to link against libcurl, or the curl dependency was
pulled by other dependencies in the prior builds.

The fix is pretty simple: add "libcurl" to the 'pkg-config --libs' args.

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

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

Versions of packages giada depends on:
ii  libasound21.1.8-1
ii  libc6 2.28-8
ii  libfltk1.31.3.4-9
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.3.0-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2
ii  libjansson4   2.12-1
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  libpng16-16   1.6.36-5
ii  librtmidi43.0.0~ds1-2
ii  libsamplerate00.1.9-2
ii  libsndfile1   1.0.28-5
ii  libstdc++68.3.0-2
ii  libx11-6  2:1.6.7-1
ii  libxext6  2:1.3.3-1+b2
ii  libxpm4   1:3.5.12-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages giada recommends:
ii  jackd  5+nmu1

giada suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: giada
Source-Version: 0.15.2+ds1-2

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
giada 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: Wed, 06 Mar 2019 23:08:53 +0100
Source: giada
Architecture: source
Version: 0.15.2+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 923898
Changes:
 giada (0.15.2+ds1-2) unstable; urgency=medium
 .
   * B-D and link against libcurl (Closes: #923898)
Checksums-Sha1:
 db41c3817495144921852fd28896e8e6db5e5ffe 2224 giada_0.15.2+ds1-2.dsc
 7fbb36bd0f057bed09c4ffe626e74a75d3d9f9e5 81588 giada_0.15.2+ds1-2.debian.tar.xz
 c36fb40ac7239ea7327fa2975fb69a9704d73297 16579 
giada_0.15.2+ds1-2_amd64.buildinfo
Checksums-Sha256:
 01085dca55c1befe879a66e7f2bc0b59a900f1f5197b840b67201b9217c6cc2f 2224 
giada_0.15.2+ds1-2.dsc
 b84fdc3846a9eec1f14548cde292e792f19ee85fa418ee70c5d926a0b557558b 81588 
giada_0.15.2+ds1-2.debian.tar.xz
 c778ad87452b2adf87d4e47a6a86591182a65e4b06697fdeab6c6e42ffe3ffca 16579 
giada_0.15.2+ds1-2_amd64.buildinfo
Files:
 14d6e8a5a3c6c446f55e2999dc84905a 2224 sound optional giada_0.15.2+ds1-2.dsc
 263a10e9c1aa06c30085b0d5f748c843 81588 sound optional 
giada_0.15.2+ds1-2.debian.tar.xz
 485f252506d1cbdcf1ec263fee294988 16579 sound optional 
giada_0.15.2+ds1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAlyA62cACgkQtlAZxH96

Bug#923898: Bug #923898 in giada marked as pending

2019-03-07 Thread IOhannes zmölnig

Control: tag -1 pending

Hello,

Bug #923898 in giada 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/multimedia-team/giada/commit/66fb8e79713e7632ba42777e3736ae6da3b14c09


B-D and link against libcurl

Closes: #923898


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923898

Processed: Bug #923898 in giada marked as pending

2019-03-07 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #923898 [giada] giada: FTBFS with JUCE-5.4.1: not linking against libcurl
Added tag(s) pending.

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

Bug#923009: seafile: CVE-2013-7469

2019-03-07 Thread Christoph Martin

Hi Salvatore,

Am 06.03.19 um 23:15 schrieb Salvatore Bonaccorso:
> Hi Christoph,
> 
> On Tue, Mar 05, 2019 at 12:12:31PM +0100, Christoph Martin wrote:
> 
> Yes I think we can agree on that!
> 

So, I'd like to lower the severity to important,

> Quick note on the buster-ignore tag addition, keep in mind that this
> is technically only to be used/added by release managers themself, but
> maintainers can obviously suggest that to the release managers, cf.
> https://www.debian.org/Bugs/Developer#tags

Sorry for that. Is it ok to leave the tag or is a severity change to
important better? The autoremove flag is still active.

Christoph




signature.asc
Description: OpenPGP digital signature

Bug#916310: Unstable?

2019-03-07 Thread Olaf van der Spek

Should it be in unstable?

-- 
Olaf

Processed: Re: Bug#923607: openblas: FTBFS if CPU is not detected

2019-03-07 Thread Debian Bug Tracking System

Processing control commands:

> forwarded -1 https://github.com/xianyi/OpenBLAS/issues/2048
Bug #923607 [src:openblas] openblas: FTBFS if CPU is not detected
Set Bug forwarded-to-address to 
'https://github.com/xianyi/OpenBLAS/issues/2048'.
> tags -1 + upstream
Bug #923607 [src:openblas] openblas: FTBFS if CPU is not detected
Added tag(s) upstream.
> severity -1 important
Bug #923607 [src:openblas] openblas: FTBFS if CPU is not detected
Severity set to 'important' from 'serious'

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

Bug#923607: openblas: FTBFS if CPU is not detected

2019-03-07 Thread Sébastien Villemot

Control: forwarded -1 https://github.com/xianyi/OpenBLAS/issues/2048
Control: tags -1 + upstream
Control: severity -1 important

Le samedi 02 mars 2019 à 21:28 +0100, Santiago Vila a écrit :
> > Still there seems to be an issue with your specific build environment,
> > and of course this is a bug (but maybe not an RC one, since you are the
> > first to report such a build failure after many years). Could you give
> > more details about the hardware you are using?
> 
> I'm currently using Scaleway 1-XS and 1-S instances. On both types of
> instances the package always fail to build. I didn't find a way to
> move the "unbuildability property" to a non-failing machine (for
> example, by taking /proc/cpuinfo in the failing machine and using
> bind-mount on the non-failing machine), so I decided to report it anyway
> without a "recipe to reproduce it" but with an offer to ssh into a failing
> machine instead.

I've tried to fix the issue by myself on the host you provided me
access to, but without success so far. Hence I have forwarded it
upstream.

I am also downgrading the severity, since the FTBFS is specific to a
seemingly small subset of machines (and in particular it never occurred
on buildds).

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#923226: Compiling shader doesn't work - game doesn't work

2019-03-07 Thread Simon McVittie

On Tue, 26 Feb 2019 at 07:51:27 +, Simon McVittie wrote:
> Does the opengl1 renderer work? (See /usr/share/doc/ioquake3/NEWS.Debian.gz)
> 
> If not, does an older version of ioquake3 from snapshot.debian.org work?

Please could you try this on your affected hardware?

If opengl1 works, I can change the default renderer back to opengl1
for buster, but I'm not going to do that without confirmation that it
solves the problem.

Thanks,
Simon

Bug#923295: marked as done (src:jruby-joni: tests fail with invalid character property name )

2019-03-07 Thread Debian Bug Tracking System

Your message dated Thu, 07 Mar 2019 08:36:21 +
with message-id 
and subject line Bug#923295: fixed in jruby-joni 2.1.26-1
has caused the Debian Bug report #923295,
regarding src:jruby-joni: tests fail with invalid character property name 

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.)


-- 
923295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jruby-joni
Version: 2.1.25-1
Severity: normal
Tags: upstream ftbfs
Forwarded: https://github.com/jruby/joni/issues/40

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

As you already know, jruby-joni fails build-time tests in the current
unstable:

SEVERE ERROR: invalid character property name 

Pattern: [/\A\X\z/] Str: [" ??"] Encoding: [UTF-8] Option: [] Syntax: [TEST]
org.jcodings.exception.CharacterPropertyException: invalid character 
property name 
at 
org.jruby.jcodings/org.jcodings.unicode.UnicodeEncoding.propertyNameToCType(UnicodeEncoding.java:99)
at 
org.jruby.joni/org.joni.Parser$GraphemeNames.nameToCtype(Parser.java:954)
at 
org.jruby.joni/org.joni.Parser.parseExtendedGraphemeCluster(Parser.java:1082)
at org.jruby.joni/org.joni.Parser.parseExp(Parser.java:792)
at org.jruby.joni/org.joni.Parser.parseBranch(Parser.java:1529)
at org.jruby.joni/org.joni.Parser.parseSubExp(Parser.java:1546)
at org.jruby.joni/org.joni.Parser.parseRegexp(Parser.java:1579)
at org.jruby.joni/org.joni.Analyser.compile(Analyser.java:78)
at org.jruby.joni/org.joni.Regex.(Regex.java:155)
at org.jruby.joni/org.joni.Regex.(Regex.java:134)
at org.jruby.joni/org.joni.test.Test.xx(Test.java:113)
at org.jruby.joni/org.joni.test.Test.xx(Test.java:99)
at org.jruby.joni/org.joni.test.Test.x2(Test.java:185)
at org.jruby.joni/org.joni.test.TestU8.test(TestU8.java:139)
at org.jruby.joni/org.joni.test.Test.testRegexp(Test.java:256)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

This bug has already been reported upstream, but I though it would be
good to track it in Debian too.

- -- 
Cheers,
  Andrej

-BEGIN PGP SIGNATURE-

iQFIBAEBCAAyFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlx0buAUHGFuZHJld3No
QGRlYmlhbi5vcmcACgkQXkCM2RzYOdKfRwf9Hvf7jFWyZ112COLnHuLjLoyQtHr2

Bug#923698: gcc-mingw-w64 miscompiles PARI

2019-03-07 Thread Stephen Kitt

Hi Bill,

On Mon, 4 Mar 2019 00:39:00 +0100, Bill Allombert  wrote:
> Since the upgrade to 8.2.0-17, gcc-mingw-w64-x86-64 miscompiles PARI/GP.
> 
> 
> The native linux version is fine though.
> The bug is caused by longjmp causing wine to crash with
> 
> 0198:err:seh:setup_exception stack overflow 320 bytes in thread 0198 eip
> 7bc9a41c esp 001314d0 stack 0x13-0x131000-0x33
> 
> when called in a function doing an unrelated setjmp _after_ the longjmp
> (in other functions longjmp work fine), and it does not occurs with the
> debug build.
> 
> One of the logs for the broken version is at
> 
> (the test-suite fails under wine).
> I use the following kit to crossbuild:
> https://pari.math.u-bordeaux.fr/pub/pari/windows/paricrossmingwkit.tgz
> 
> So if you have a suggestion...

I don’t have any practical suggestion right now, but given that there’s a
test suite I’ll bisect to identify the source of the problem.

Regards,

Stephen


pgplhV1ZvMYn6.pgp
Description: OpenPGP digital signature

Processed: severity of 923214 is serious, tagging 923214, severity of 923698 is serious

2019-03-07 Thread Debian Bug Tracking System

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

> severity 923214 serious
Bug #923214 [g++-mingw-w64] g++-mingw-w64: Internal compiler error when include 
qfloat16.h, Qt5.12.
Severity set to 'serious' from 'important'
> tags 923214 + pending
Bug #923214 [g++-mingw-w64] g++-mingw-w64: Internal compiler error when include 
qfloat16.h, Qt5.12.
Added tag(s) pending.
> severity 923698 serious
Bug #923698 [gcc-mingw-w64-x86-64] gcc-mingw-w64 miscompiles PARI
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

71 matches

Mail list logo