Bug#892656: even more tests fail with version 2.0.2

[Paolo Greppi]

Il 13/01/19 16:52, Paul Gevers ha scritto:
> user debian-rele...@lists.debian.org
> usertags 884543 bsp-2019-01-nl-venlo
> thanks
> 
> On Mon, 23 Apr 2018 14:36:00 +0200 Paolo Greppi 
> wrote:
>> So I'd propose we go straight for option #3 (downgrade node-is-descriptor to 
>> 1.0).
>> Can you do that please ?
> 
> Is this what needs to happen? Should this be packaged:
> https://github.com/jonschlinkert/is-descriptor/archive/1.0.2.tar.gz ?
> 
> Paul
> Sent from the BSP in Venlo

Hi Paul, seems like npm registry now has is-descriptor 3.0.0:
https://www.npmjs.com/package/is-descriptor

but even define-property 2.0.2 still wants is-descriptor 1.0.2:
https://github.com/jonschlinkert/define-property/blob/master/package.json#L27

Now that we consider acceptable to embed tiny node modules (and is-descriptor 
certainly is tiny) we have two options:
1. (old #3) downgrade node-is-descriptor to 1.0.2
2. remove node-is-descriptor 2.0.0 and embed is-descriptor 1.0.2 into 
node-define-property

Paolo

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

[Axel Beckert]

Package: dnssec-trigger
Version: 0.17+repack-1
Severity: serious

Setting up dnssec-trigger (0.17+repack-1) ...
Job for dnssec-triggerd.service failed because the control process exited with 
error code.
See "systemctl status dnssec-triggerd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dnssec-triggerd, action "restart" failed.
# dnssec-triggerd.service - Reconfigure local DNSSEC resolver on connectivity 
changes
   Loaded: loaded (/lib/systemd/system/dnssec-triggerd.service; enabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2019-01-14 
07:20:18 CET; 16ms ago
  Process: 29431 ExecStartPre=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--prepare (code=exited, status=0/SUCCESS)
  Process: 29438 ExecStart=/usr/sbin/dnssec-triggerd -d (code=exited, 
status=1/FAILURE)
  Process: 29439 ExecStartPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--update_all (code=exited, status=0/SUCCESS)
  Process: 29443 ExecStopPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--cleanup (code=exited, status=1/FAILURE)
 Main PID: 29438 (code=exited, status=1/FAILURE)
dpkg: error processing package dnssec-trigger (--configure):
 installed dnssec-trigger package post-installation script subprocess returned 
error exit status 1
Processing triggers for libc-bin (2.28-5) ...
Errors were encountered while processing:
 dnssec-trigger

I said "no" to the new dnssec-trigger.conf, but except comments the only
difference is the search domain setting:

$ diff /etc/dnssec-trigger/dnssec-trigger.conf 
/etc/dnssec-trigger/dnssec-trigger.conf.dpkg-dist 
28c28
< search: "deuxchevaux.org noone.org ethz.ch debian.org"
---
> # search: ""
51c51
< # check-updates: 
---
> # check-updates: no
65a66
> # These relay incoming DNS traffic on the other port numbers to the usual DNS
76a78,86
> 
> # Use VPN servers for all traffic
> # use-vpn-forwarders: no
> 
> # Forward RFC 1918 private addresses to global forwarders
> # use-private-addresses: yes
> 
> # Add domains provided by VPN connections into Unbound forward zones
> # add-wifi-provided-zones: no

The syslog shows again this:

Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59 
dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file crypto 
error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small

So maybe https://bugs.debian.org/898969 is not fully fixed yet?

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

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

Versions of packages dnssec-trigger depends on:
ii  gir1.2-nm-1.0   1.14.4-4
ii  libc6   2.28-5
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-7
ii  libglib2.0-02.58.2-3
ii  libgtk2.0-0 2.24.32-3
ii  libldns21.7.0-3.1+b1
ii  libssl1.1   1.1.1a-1
ii  python3 3.7.1-3
ii  python3-gi  3.30.4-1
ii  python3-lockfile1:0.12.2-2
ii  sensible-utils  0.0.12
ii  unbound 1.8.1-1+b1

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- Configuration Files:
/etc/dnssec-trigger/dnssec-trigger.conf changed:
search: "deuxchevaux.org noone.org ethz.ch debian.org"
url: "http://ster.nlnetlabs.nl/hotspot.txt OK"
url: "http://fedoraproject.org/static/hotspot.txt OK"
tcp80: 185.49.140.67
tcp80: 2a04:b900::10:0:0:67
ssl443: 185.49.140.67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF
ssl443: 2a04:b900::10:0:0:67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF


-- no debconf information

Processed: closing 919223

[Debian Bug Tracking System]

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

> close 919223
Bug #919223 [ruby-rack] ruby-haml-contrib: missing build dependency on 
ruby-temple
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: reassign 919223 to ruby-rack

[Debian Bug Tracking System]

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

> reassign 919223 ruby-rack
Bug #919223 [src:ruby-haml-contrib] ruby-haml-contrib: missing build dependency 
on ruby-temple
Bug reassigned from package 'src:ruby-haml-contrib' to 'ruby-rack'.
No longer marked as found in versions ruby-haml-contrib/1.0.0.1-2.
Ignoring request to alter fixed versions of bug #919223 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#919223: closing 919223

[Cédric Boutillier]

close 919223 
thanks

Fixed with the 5.0.4-2 of ruby-haml.

Processed: fixed 919223 in ruby-rack/5.0.4-2

[Debian Bug Tracking System]

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

> fixed 919223 ruby-rack/5.0.4-2
Bug #919223 [ruby-rack] ruby-haml-contrib: missing build dependency on 
ruby-temple
The source ruby-rack and version 5.0.4-2 do not appear to match any binary 
packages
Marked as fixed in versions ruby-rack/5.0.4-2.
> thanks
Stopping processing here.

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

Bug#919255: gnucap-python: please stop build-depending on python3.6

[Mattia Rizzolo]

Source: gnucap-python
Version: 0.0.2-1
Severity: serious
Control: block 916817 by -1

Deaer maintainer,

We would like to remove python3.6 from buster, so please drop the
build-depends on gnucap-python.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: gnucap-python: please stop build-depending on python3.6

[Debian Bug Tracking System]

Processing control commands:

> block 916817 by -1
Bug #916817 [release.debian.org] transition: remove python3.6
916817 was blocked by: 917369 917628 917626 916820 914147 917781
916817 was not blocking any bugs.
Added blocking bug(s) of 916817: 919255

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

Bug#905674: Citation notice FAQ

[Ole Tange]

Hi Kurt Fitzner

You question whether software should be cited and if so how?

These links suggest: Yes, you should cite software, and if the author
suggests a way of citing use that.

* 
https://blog.apastyle.org/apastyle/2015/01/how-to-cite-software-in-apa-style.html
* https://libguides.mit.edu/c.php?g=551454=3900280
* https://www.software.ac.uk/how-cite-software
* https://aut.ac.nz.libguides.com/APA6th/software
* https://libguides.rgu.ac.uk/c.php?g=380081=2983956
* https://journals.aas.org/policy-statement-on-software/
* https://guides.lib.monash.edu/c.php?g=219786=1454293
* https://www.maxqda.com/how-to-cite-maxqda

If you feel the benefit from using GNU Parallel is too small to
warrant a citation, then prove that by simply using another tool.

Here are other examples of software showing how to cite. Some of these
refer to peer-reviewed articles - others do not:

* https://www.scipy.org/citing.html
* https://octave.org/doc/interpreter/Citing-Octave-in-Publications.html
  (Octave has citation for individual packages, too)
* https://stat.ethz.ch/pipermail/r-help/2008-May/161481.html
* https://stat.ethz.ch/R-manual/R-devel/library/utils/html/citation.html
  (R has citation for individual packages, too)
* http://www.partek.com/citing-partek-software-in-a-publication/
* http://www.fluortools.com/misc/cite
* https://www.maxqda.com/how-to-cite-maxqda
* https://www.open-mpi.org/papers/
* https://www.tensorflow.org/about/bib
* http://www.fon.hum.uva.nl/paul/praat.html

I would think that most people, who appreciate GNU Parallel, would be
happy to help funding the development even if it is simply by making a
citation.

So what really puzzles me is: If you feel very strongly against
helping to fund future development of GNU Parallel, why not use an
alternative tool? No one forces you to use GNU Parallel. Here is a
list of alternatives to help you choose:
https://www.gnu.org/software/parallel/parallel_alternatives.html


You also pose it might be bad if more software asked for citations.

Let us make one thing abundantly clear: The reason for the citing
notice in GNU Parallel is _funding_ - not prestige of being cited in
an academic journal, as you hint. It has never been a secret and has
been explained from the start:
https://lists.gnu.org/archive/html/parallel/2013-11/msg6.html

If you find another way to pay my salary, so I can continue to devote
time to develop GNU Parallel, then I will have no objections to
removing the notice. So please help solve that problem. Not only will
it please me, but if you find a general solution, many other free
software developers will thank you for it.

Focusing on how we can get more free software funded is constructive.
Focusing on how we can remove funding for existing free software is
not.

It is unclear to me why you think that funding through citations
suddenly will be the prevailing way of funding, if Debian affirms GNU
Parallel's version of an 'OK. Do not show this again'-message (just
like the GUI-messages this message can be silenced in less than 10
seconds, and if you do not save more than 10 seconds by using GNU
Parallel, maybe you should not be using it anyway).

First of all, I think that is unrealistic that this sudden change will
happen (most other software is financed in different ways). But even
if it _did_ happen, then you would be free to use different tools (or
develop your own), if you prefer not to cite.

To me your email could be summarized as: "I do not want to help fund
the development, but I want to reap all the benefits - even if that
means killing the long term development."

To me it seems it is you whom Nadia Eghbal addresses in
https://www.slideshare.net/NadiaEghbal/consider-the-maintainer:

"Is it alright to compromise, or even deliberately ignore, the
happiness of maintainers so we that can enjoy free and open source
software?"


== Citation notice FAQ ==

> Why does GNU Parallel show a citation notice?

GNU Parallel is indirectly funded through citations. It is therefore
important for the long term survival of GNU Parallel that it is cited.
The citation notice makes users aware of this.

See also: https://lists.gnu.org/archive/html/parallel/2013-11/msg6.html


> Is the citation notice compatible with GPLv3?

Yes. The wording has been cleared by Richard M. Stallman to be
compatible with GPLv3. This is because the citation notice is not part
of the license, but part of academic tradition.

Therefore the notice is not adding a term that would require citation
as mentioned on:
https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation


> Do automated scripts break if the notice is not silenced?

No. Not a single time has that happened. This is due to the notice
only being printed, if the output is to the screen - not if the output
is to a file or a pipe.


> How do I silence the citation notice?

Run this once:

  parallel --citation

It takes less than 10 seconds to do and is thus comparable to an 'OK.
Do not show this again'-dialog 

Bug#917500: liggghts: FTBFS (style_atom.h: No such file or directory)

[Anton Gladky]

Hello Santiago,

thanks for the reporting it. Unfortunately I am not able
to reproduce the described error. It builds just fine and the
recent upload into Debian did not identified the problems
with the package [1].

Please give some more information, how can it be reproduced.

Thanks

[1] https://buildd.debian.org/status/package.php?p=liggghts

Anton

Am Fr., 28. Dez. 2018 um 00:57 Uhr schrieb Santiago Vila :
>
> Package: src:liggghts
> Version: 3.8.0+repack1-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 --buildsystem=cmake 
> --builddirectory=/<>/liggghts-3.8.0+repack1/debian/build
>dh_update_autotools_config -i -O--buildsystem=cmake 
> -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
>dh_autoreconf -i -O--buildsystem=cmake 
> -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
>dh_auto_configure -i -O--buildsystem=cmake 
> -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
> cd debian/build && 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 C compiler identification is GNU 8.2.0
> -- The CXX compiler identification is GNU 8.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
>
> [... snipped ...]
>
> CMAKE_EXPORT_NO_PACKAGE_REGISTRY
>
>
> -- Build files have been written to: 
> /<>/liggghts-3.8.0+repack1/debian/build
>dh_auto_build -i -O--buildsystem=cmake 
> -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
> cd debian/build && make -j1 "INSTALL=install --strip-program=true"
> make[1]: Entering directory 
> '/<>/liggghts-3.8.0+repack1/debian/build'
> /usr/bin/cmake -S/<>/liggghts-3.8.0+repack1 
> -B/<>/liggghts-3.8.0+repack1/debian/build --check-build-system 
> CMakeFiles/Makefile.cmake 0
> /usr/bin/cmake -E cmake_progress_start 
> /<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles 
> /<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles/progress.marks
> make -f CMakeFiles/Makefile2 all
> make[2]: Entering directory 
> '/<>/liggghts-3.8.0+repack1/debian/build'
> make -f src/CMakeFiles/libliggghts.dir/build.make 
> src/CMakeFiles/libliggghts.dir/depend
> make[3]: Entering directory 
> '/<>/liggghts-3.8.0+repack1/debian/build'
> cd /<>/liggghts-3.8.0+repack1/debian/build && /usr/bin/cmake -E 
> cmake_depends "Unix Makefiles" /<>/liggghts-3.8.0+repack1 
> /<>/liggghts-3.8.0+repack1/src 
> /<>/liggghts-3.8.0+repack1/debian/build 
> /<>/liggghts-3.8.0+repack1/debian/build/src 
> /<>/liggghts-3.8.0+repack1/debian/build/src/CMakeFiles/libliggghts.dir/DependInfo.cmake
>  --color=
> Scanning dependencies of target libliggghts
> make[3]: Leaving directory '/<>/liggghts-3.8.0+repack1/debian/build'
> make -f src/CMakeFiles/libliggghts.dir/build.make 
> src/CMakeFiles/libliggghts.dir/build
> make[3]: Entering directory 
> '/<>/liggghts-3.8.0+repack1/debian/build'
> [  0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle.cpp.o
> cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx  
> -Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
> -DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
> -DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
>  -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/jsoncpp 
> -I/usr/include/eigen3 -I/<>/liggghts-3.8.0+repack1 
> -I/<>/liggghts-3.8.0+repack1/src  -g -O2 
> -fdebug-prefix-map=/<>/liggghts-3.8.0+repack1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG 
> -fPIC   -o CMakeFiles/libliggghts.dir/angle.cpp.o -c 
> /<>/liggghts-3.8.0+repack1/src/angle.cpp
> [  0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o
> cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx  
> -Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
> -DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
> -DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
>  -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi 
> 

Bug#919246: oss4-dkms: module FTBFS for Linux 4.19

[Andreas Beckmann]

Package: oss4-dkms
Version: 4.2-build2017-1
Severity: serious
Justification: fails to build from source
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

the oss4-dkms kernel module fails to build for Linux 4.19:

DKMS make.log for oss4-4.2-build2017 for kernel 4.19.0-1-amd64 (x86_64)
Mon Jan 14 04:22:16 UTC 2019
make: Entering directory '/usr/src/linux-headers-4.19.0-1-amd64'
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/os_linux.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_ac97.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_audio_core.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_audiofmt.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_grc3.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_spdif.o
/var/lib/dkms/oss4/4.2-build2017/build/core/os_linux.c: In function 
'osdev_create_201502111816':
/var/lib/dkms/oss4/4.2-build2017/build/core/os_linux.c:162:10: warning: 
assignment discards 'const' qualifier from pointer target type 
[-Wdiscarded-qualifiers]
  devpath = oss_pci_read_devpath (osdev->dip);
  ^
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_default_timer.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_midi_core.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_midi_mapper.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_midi_parser.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_midi_queue.o
/var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.c: In function 
'oss_get_uid':
/var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.c:479:23: error: 
dereferencing pointer to incomplete type 'const struct cred'
   return current->cred->uid.val;
   ^~
/var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.c: In function 
'oss_timeout':
/var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.c:570:3: error: implicit 
declaration of function 'init_timer'; did you mean 'init_timers'? 
[-Werror=implicit-function-declaration]
   init_timer (>timer);
   ^~
   init_timers
/var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.c:572:15: error: 'struct 
timer_list' has no member named 'data'
   tmout->timer.data = id | (timeout_random & ~0xff);
   ^
/var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.c:573:25: error: 
assignment to 'void (*)(struct timer_list *)' from incompatible pointer type 
'void (*)(long unsigned int)' [-Werror=incompatible-pointer-types]
   tmout->timer.function = oss_timer_callback;
 ^
  CC [M]  /var/lib/dkms/oss4/4.2-build2017/build/core/oss_midi_timers.o
cc1: some warnings being treated as errors
make[3]: *** 
[/usr/src/linux-headers-4.19.0-1-common/scripts/Makefile.build:308: 
/var/lib/dkms/oss4/4.2-build2017/build/core/oss_core.o] Error 1
make[3]: *** Waiting for unfinished jobs
make[2]: *** [/usr/src/linux-headers-4.19.0-1-common/Makefile:1532: 
_module_/var/lib/dkms/oss4/4.2-build2017/build/core] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.19.0-1-amd64'


Andreas

Bug#918502: golang-github-opencontainers-runtime-tools: autopkgtest needs update for new version of golang-github-hashicorp-go-multierror

[Arnaud Rebillout]

I pushed some changes to Salsa:


  * New upstream version 0.8.0+dfsg
  * Update patches
  * Add patch to build against hashicorp-multierror 1.0

Can someone upload this package, as I'm just DM and I don't have
permission for that?

I CC Dmitry as he's the original author of the package, but really, any
DD from the Go team should feel free to tag a release and upload.

For more context:

There was very little changes upstream between 0.7 to 0.8, and no
changes at all in the vendor tree, so the update was rather trivial.
Additionally, we actually don't use this package (yet) to build any
other package, so nothing can possibly break.

Thanks,

  Arnaud

Bug#919060: same problem here...

[Pirate Praveen]

On 2019, ജനുവരി 13 11:26:54 PM IST, Dragos Jarca 
 wrote:
>after apt-get update and apt-get dist-upgrade...
>
>now gitlab cannot be used...

This is a different issue, please open a new bug.

>cannot upgrade to experimental to...
>
>root@omv:/usr/share/gitlab# apt-get install ruby-gitaly=1.5.0+dfsg-1 
>ruby-responders ruby-default-value-for=3.1.1-1 ruby-devise 
>ruby-doorkeeper ruby-doorkeeper-openid-connect ruby-recaptcha 
>ruby-devise-two-factor ruby-browser ruby-graphiql-rails 
>ruby-acts-as-taggable-on ruby-redis-rails ruby-asana=0.8.1-1 
>ruby-kubeclient=4.2.0-1 ruby-webpack-rails ruby-sass-rails 
>ruby-font-awesome-rails ruby-premailer-rails ruby-rails-i18n=5.1.2-1 
>ruby-peek ruby-peek-gc ruby-peek-pg ruby-peek-rblineprof
>ruby-peek-redis 
>ruby-lograge ruby-actionmailer=2:5.2.2+dfsg-1 
>ruby-actionpack=2:5.2.2+dfsg-1 ruby-actionview=2:5.2.2+dfsg-1 
>ruby-activemodel=2:5.2.2+dfsg-1 ruby-activerecord=2:5.2.2+dfsg-1 
>ruby-activesupport=2:5.2.2+dfsg-1 ruby-activestorage ruby-actioncable 
>ruby-activejob=2:5.2.2+dfsg-1 ruby-railties=2:5.2.2+dfsg-1 
>ruby-sprockets-rails ruby-rack=2.0.6-3 ruby-rails=2:5.2.2+dfsg-1 
>gitlab-common=11.6.0+dfsg-1 ruby-rails-dom-testing=2.0.3-3 
>ruby-arel=9.0.0-2 ruby-http=3.3.0-1 ruby-http-form-data=2.1.0-1 
>rails=2:5.2.2+dfsg-1 gitlab=11.6.0+dfsg-1 gitaly=1.12.0+debian-1 
>ruby-actionpack-xml-parser=2.0.1-1 redmine
>ruby-protected-attributes=1.1.4-2
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>ruby-sprockets-rails is already the newest version (2.3.2-1).
>ruby-sprockets-rails set to manually installed.
>ruby-graphiql-rails is already the newest version (1.4.10-1).
>ruby-graphiql-rails set to manually installed.
>redmine is already the newest version (3.4.6-1).
>ruby-acts-as-taggable-on is already the newest version (5.0.0-2).
>ruby-acts-as-taggable-on set to manually installed.
>ruby-browser is already the newest version (2.5.3-1).
>ruby-browser set to manually installed.
>ruby-devise is already the newest version (4.5.0-1).
>ruby-devise set to manually installed.
>ruby-devise-two-factor is already the newest version (3.0.3-1).
>ruby-devise-two-factor set to manually installed.
>ruby-doorkeeper is already the newest version (4.4.2-1).
>ruby-doorkeeper set to manually installed.
>ruby-doorkeeper-openid-connect is already the newest version (1.5.2-1).
>ruby-doorkeeper-openid-connect set to manually installed.
>ruby-font-awesome-rails is already the newest version (4.7.0.4-1).
>ruby-font-awesome-rails set to manually installed.
>ruby-lograge is already the newest version (0.10.0-1).
>ruby-lograge set to manually installed.
>ruby-peek is already the newest version (1.0.1-1).
>ruby-peek set to manually installed.
>ruby-peek-gc is already the newest version (0.0.2-1).
>ruby-peek-gc set to manually installed.
>ruby-peek-pg is already the newest version (1.3.0-1).
>ruby-peek-pg set to manually installed.
>ruby-peek-rblineprof is already the newest version (0.2.0-1).
>ruby-peek-rblineprof set to manually installed.
>ruby-peek-redis is already the newest version (1.2.0-1).
>ruby-peek-redis set to manually installed.
>ruby-premailer-rails is already the newest version (1.9.7-1).
>ruby-premailer-rails set to manually installed.
>ruby-protected-attributes is already the newest version (1.1.4-2).
>ruby-protected-attributes set to manually installed.
>ruby-recaptcha is already the newest version (4.11.1-1).
>ruby-recaptcha set to manually installed.
>ruby-redis-rails is already the newest version (5.0.2-3).
>ruby-redis-rails set to manually installed.
>ruby-responders is already the newest version (2.4.0-3).
>ruby-responders set to manually installed.
>ruby-sass-rails is already the newest version (5.0.6-2).
>ruby-sass-rails set to manually installed.
>ruby-webpack-rails is already the newest version (0.9.11+git-1).
>ruby-webpack-rails set to manually installed.
>Some packages could not be installed. This may mean that you have
>requested an impossible situation or if you are using the unstable
>distribution that some required packages have not yet been created
>or been moved out of Incoming.
>The following information may help to resolve the situation:
>
>The following packages have unmet dependencies:
>  ruby-protected-attributes : Depends: ruby-activemodel (< 2:5.0) but 
>2:5.2.2+dfsg-1 is to be installed
>E: Unable to correct problems, you have held broken packages.
>root@omv:/usr/share/gitlab#
>
>Seems that is a incopatibility between gitlab and redmine...
>
>I try to use in production and now my team cannot commit changes.

This is because we could not get gitlab working with rails 5.2 in time for 
uploading rails 5.2 to unstable. Since transitions freeze was approaching, we 
did not have a choice to wait for gitlab, as gitlab will not be in buster 
anyway.

Rails 5.2 support is in progress by upstream, and as soon as it is complete we 
will upload it to unstable.

unstable is expected to have such temporary breakages from time 

Bug#918502: golang-github-opencontainers-runtime-tools: autopkgtest needs update for new version of golang-github-hashicorp-go-multierror

[Arnaud Rebillout]

Thanks for the report,

I'm looking into that. The FTBFS is not fixed by updating
opencontainers-runtime-tools to the latest version (0.8).

Actually, the issue is that opencontainers-runtime-tools is using an
outdated vendored copy of hashicorp-go-multierror. It doesn't build out
of the box against the latest version of multierror. I'm cooking a
little patch for that to work.

Bug#919086: marked as done (lrslib: FTBFS on 32-bit architectures)

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 02:56:50 +
with message-id 
and subject line Bug#919086: fixed in lrslib 0.70-3
has caused the Debian Bug report #919086,
regarding lrslib: FTBFS on 32-bit architectures
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.)


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

Hi,

lrslib/experimental FTBFS on all 32-bit architectures. This is a
regression from sid.

https://buildd.debian.org/status/package.php?p=lrslib=experimental


Andreas
--- End Message ---
--- Begin Message ---
Source: lrslib
Source-Version: 0.70-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Jan 2019 22:12:46 -0400
Source: lrslib
Binary: lrslib liblrs0 liblrs-dev
Architecture: source
Version: 0.70-3
Distribution: unstable
Urgency: medium
Maintainer: David Bremner 
Changed-By: David Bremner 
Description:
 liblrs-dev - package to enumerate vertices and extreme rays (development file)
 liblrs0- package to enumerate vertices and extreme rays (shared libraries)
 lrslib - package to enumerate vertices and extreme rays of a convex polyhe
Closes: 919086
Changes:
 lrslib (0.70-3) unstable; urgency=medium
 .
   * upload to unstable
   * pass CFLAGS from dpkg-buildflags to make (fix generation of dbgsym
 packages)
 .
 lrslib (0.70-2) experimental; urgency=medium
 .
   * Drop build of 128 bit arithmetic on 32 bit arches.  (Closes: #919086).
 .
 lrslib (0.70-1) experimental; urgency=medium
 .
   * Major new upstream release.
   * Replace arithmetic specific libraries liblrsgmp{1,-dev} with
 liblrs{0,-dev}. This is a severe ABI break, all clients will need to
 be recompiled.
   * New adaptive arithmetic feature restarts with wider arithmetic when
 there is potential overflow
Checksums-Sha1:
 b62f55063c8af02a59030f6e38d3e82f29d4b9f1 1902 lrslib_0.70-3.dsc
 661bd6c87286b9ef540728b6b2f6e750d80654c4 11980 lrslib_0.70-3.debian.tar.xz
Checksums-Sha256:
 0d91ad26bde968e3d820f7636825da839aaf7483e6e1830433649068ab02233c 1902 
lrslib_0.70-3.dsc
 03be5c1f89ee1e26a18dc48af7f16f351a7eeaaadfcd9421fea389d4fe234fd0 11980 
lrslib_0.70-3.debian.tar.xz
Files:
 db4ca2e8e81d2f90eda6ebdb46aadde7 1902 math optional lrslib_0.70-3.dsc
 c4dbd5619c4ad8d063789a938f19e0ec 11980 math optional 
lrslib_0.70-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlw78xsACgkQ8gKXHaSn
niza/Av5ARJ9Vt68Wc5fRgGUm7jUIOmE+rK6HFrHNDcKo/qVi/c3D4nVW2siqtxt
Lbc90CVf7DU9a13bN4DoZT8A/NAQ8JgmoeyoiJLTbjzS2VZHUa7qj4mD3hFLXpDI
WQoTIiCR3F9lWhFEVpd7Bm3MQcYv0POyvM9BwOdRpjh0Q6FEaqm+3jeFyeAhfQ7Z
ONDygaQw02aUX6CMzPqBupYZMUSXvM6uffE/KPVLk2ABqFp+A/goiEGI8p+mlroB
P47OirP7ObFsF+bcYAdnjTURkW1r1R5mLNqZ7X5hQzZYNGuqEKxnRbDeslbeYjB4
Cw0LhhbHuO9TKS/vd3yu6n1Qg3L/634riRVoTglFk/FT51HD2TvW/6DpD/lmFON0
zfWahh0zTvGSZMGuq4Ormh3uY+VH8BeM75Kl/VbNHBsV9JidF8pKm6PU86Lh7hxM
eDi7eyx0ZoeVZznXtvzWURam8hxPCWaAZJ4CV1ChAW/3IFtlA8ecLVFZ7Y562SYT
BLI2XF3g
=5iQd
-END PGP SIGNATURE End Message ---

Bug#919237: marked as done (node-jsonld: FTBFS in sid (Error: Can't resolve 'rdf-canonize'))

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 02:57:25 +
with message-id 
and subject line Bug#919237: fixed in node-jsonld 1.4.0-3
has caused the Debian Bug report #919237,
regarding node-jsonld: FTBFS in sid (Error: Can't resolve 'rdf-canonize')
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.)


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

Hello Jonas.

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
BROWSERSLIST='node 6' babeljs \
--no-babelrc --presets=env \
--out-dir dist/node6/lib \
-- lib
lib/ActiveContextCache.js -> dist/node6/lib/ActiveContextCache.js
lib/DocumentCache.js -> dist/node6/lib/DocumentCache.js
lib/JsonLdError.js -> dist/node6/lib/JsonLdError.js
lib/JsonLdProcessor.js -> dist/node6/lib/JsonLdProcessor.js
lib/NQuads.js -> dist/node6/lib/NQuads.js

[... snipped ...]

 [239] /usr/lib/nodejs/core-js/fn/symbol/index.js 254 bytes {0} [built]
 [247] ./lib/jsonld.js 54.6 kB {0} [built]
 [281] ./lib/flatten.js 1.06 kB {0} [built]
 [282] ./lib/fromRdf.js 17.3 kB {0} [built]
 [283] ./lib/toRdf.js 10.3 kB {0} [built]
+ 277 hidden modules

WARNING in jsonld.min.js from UglifyJs
Side effects in initialization of unused variable _expandIri 
[./lib/jsonld.js:66,13]
Condition always false 
[./usr/lib/nodejs/regenerator-runtime/runtime.js:21,17]
Dropping side-effect-free statement [./lib/frame.js:91,23]
Side effects in initialization of unused variable _ret 
[./lib/frame.js:91,23]
Dropping side-effect-free statement [./lib/compact.js:165,40]
Side effects in initialization of unused variable _ret 
[./lib/compact.js:165,40]

ERROR in ./lib/jsonld.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/jsonld.js 60:15-38
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js

ERROR in ./lib/NQuads.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/NQuads.js 8:17-40
 @ ./lib/jsonld.js
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js

ERROR in ./lib/util.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/util.js 39:23-46
 @ ./lib/jsonld.js
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js
make[1]: *** [debian/rules:8: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ends in my autobuilder, but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-jsonld.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.
--- End Message ---
--- Begin Message ---
Source: node-jsonld
Source-Version: 1.4.0-3

We believe that the bug you reported is fixed in the latest version of
node-jsonld, 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.
Jonas Smedegaard  (supplier of updated node-jsonld 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

Bug#831281: marked as done (plasma-widget-yawp: FTBFS: build-dependency not installable: kdebase-workspace-dev)

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 02:44:59 +
with message-id 
and subject line Bug#919149: Removed package(s) from unstable
has caused the Debian Bug report #831281,
regarding plasma-widget-yawp: FTBFS: build-dependency not installable: 
kdebase-workspace-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.)


-- 
831281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-widget-yawp
Version: 0.4.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> ┌──┐
> │ Install plasma-widget-yawp build dependencies (apt-based resolver)  
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-plasma-widget-yawp-dummy : Depends: 
> kdebase-workspace-dev but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/plasma-widget-yawp_0.4.2-1_unstable_gcc5.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.4.2-1+rm

Dear submitter,

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

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

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

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

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

Bug#906730: marked as done (calendar-exchange-provider: Add-on is not compatible with Thunderbird 60.0)

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 02:46:41 +
with message-id 
and subject line Bug#919157: Removed package(s) from unstable
has caused the Debian Bug report #906730,
regarding calendar-exchange-provider: Add-on is not compatible with Thunderbird 
60.0
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.)


-- 
906730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: calendar-exchange-provider
Version: 4.0.0~beta5-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

after updating Thunderbird to version 1:60.0-1, an error message is
shown stating that this add-on is not compatible with the current
Thunderbird version. This problem is also reported upstream [1] and I
saw that you already commented on this issue. But recently, some work
started on porting the add-on to Thunderbird 60 [2, 3]. If a new
add-on version will be published, please consider packaging it again.

Thank you for your work and kind regards
Benjamin Eikel

[1] https://github.com/ExchangeCalendar/exchangecalendar/issues/178
[2] https://github.com/ExchangeCalendar/exchangecalendar/pull/188
[3] https://github.com/ExchangeCalendar/exchangecalendar/pull/189

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

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

Versions of packages calendar-exchange-provider depends on:
ii  lightning1:60.0-1
ii  thunderbird  1:60.0-1

calendar-exchange-provider recommends no packages.

calendar-exchange-provider suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.0.0~alpha2-1+rm

Dear submitter,

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

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

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

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

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

Bug#904592: marked as done (predict-gsat: No executable is included)

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 02:47:23 +
with message-id 
and subject line Bug#919159: Removed package(s) from unstable
has caused the Debian Bug report #904592,
regarding predict-gsat: No executable is included
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.)


-- 
904592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: predict-gsat
Version: 2.2.5+dfsg.1-1
Severity: normal

Dear Maintainer,

This is the content of the predict-gsat 2.2.5+dfsg.1-1 package:

/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/predict-gsat
/usr/share/doc/predict-gsat/AUTHORS
/usr/share/doc/predict-gsat/NEWS.gz
/usr/share/doc/predict-gsat/Plugin_API
/usr/share/doc/predict-gsat/README
/usr/share/doc/predict-gsat/changelog.Debian.gz
/usr/share/doc/predict-gsat/changelog.gz
/usr/share/doc/predict-gsat/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/gsat.1.gz

No gsat executable is included

Best regards,
-- 
Manolo Díaz
--- End Message ---
--- Begin Message ---
Version: 2.2.5+dfsg.1-1+rm

Dear submitter,

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

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

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

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

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

Bug#912712: marked as done (vibe.d FTBFS with ldc)

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 02:45:58 +
with message-id 
and subject line Bug#912712: fixed in dlang-libevent 2.0.16.1~really2.0.2-0.1
has caused the Debian Bug report #912712,
regarding vibe.d FTBFS with ldc
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.)


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

Package: vibe.d
Version: 0.8.4-1
Severity: serious

Vibe.d fails to build with the following error. Presumablly this was triggered 
by the upgrade to ldc 1.12.0.

https://buildd.debian.org/status/fetch.php?pkg=vibe.d=amd64=0.8.4-1%2Bb1=1540811095=0


/usr/include/d/common/deimos/event2/util.d(183): Error: instead of C-style 
syntax, use D-style `evutil_socket_t[2] sv`
/usr/include/d/common/deimos/event2/bufferevent.d(578): Error: instead of 
C-style syntax, use D-style `bufferevent*[2] pair`


--- End Message ---
--- Begin Message ---
Source: dlang-libevent
Source-Version: 2.0.16.1~really2.0.2-0.1

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated dlang-libevent 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, 10 Jan 2019 10:08:40 +0100
Source: dlang-libevent
Binary: dlang-libevent
Architecture: source all
Version: 2.0.16.1~really2.0.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Konstantinos Margaritis 
Changed-By: Matthias Klumpp 
Description:
 dlang-libevent - D version of the C headers for libevent
Closes: 912712
Changes:
 dlang-libevent (2.0.16.1~really2.0.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release:
 - Fixes FTBFS due to language deprecations (Closes: #912712)
   * Depend/recommend default-d-compiler instead of individual D compilers
   * Update homepage URL to the new location
   * Switch to dh compat level 12
   * Bump standards version to 4.3.0 (no changes needed)
   * Depend on libevent-dev
Checksums-Sha1:
 1842b001fcbfb5ab78ce32a439442a77f90a530d 1960 
dlang-libevent_2.0.16.1~really2.0.2-0.1.dsc
 b63867966e1fcbd481caf5b1a99a3cf4080006f7 130540 
dlang-libevent_2.0.16.1~really2.0.2.orig.tar.gz
 5c5a75aa340b1259afe350051534669802b51d93 2388 
dlang-libevent_2.0.16.1~really2.0.2-0.1.debian.tar.xz
 a54ebf73a1316655ceba2470ce387feb09ade551 54080 
dlang-libevent_2.0.16.1~really2.0.2-0.1_all.deb
 2be11515155dfc8153dc85e8a8645e6c3b8d5cda 6064 
dlang-libevent_2.0.16.1~really2.0.2-0.1_amd64.buildinfo
Checksums-Sha256:
 2cf5ac1aacb5d688a2a1c6070a4bdedc42f86362a1c571016ad5ec92a29d17f1 1960 
dlang-libevent_2.0.16.1~really2.0.2-0.1.dsc
 1297a32b2be96a7fcaf55ca50f4e8dd2ed0d6e11ef23860d1e74d3439144b6f7 130540 
dlang-libevent_2.0.16.1~really2.0.2.orig.tar.gz
 1f6606932bd295bc3a62dfe6ebfaefdf77c752dfb05ba994fcd71394716f 2388 
dlang-libevent_2.0.16.1~really2.0.2-0.1.debian.tar.xz
 cc4de6a43053afb8dfb9977ef5c7ae8b98fe4d250e9ed1ea61d462c2085303a0 54080 
dlang-libevent_2.0.16.1~really2.0.2-0.1_all.deb
 419878ef700e2fbf1322c1afd4cbc51ab7d7053c4bde84b405f1cbc702977704 6064 
dlang-libevent_2.0.16.1~really2.0.2-0.1_amd64.buildinfo
Files:
 d90ce335013bbaf9877acfcd945accff 1960 devel optional 
dlang-libevent_2.0.16.1~really2.0.2-0.1.dsc
 ce79718b91b786c79e2d652f087e64ad 130540 devel optional 
dlang-libevent_2.0.16.1~really2.0.2.orig.tar.gz
 026bd925ec5e9b87780899f2e4e784b4 2388 devel optional 
dlang-libevent_2.0.16.1~really2.0.2-0.1.debian.tar.xz
 7e1518bc218b511c27d152a2589012ef 54080 devel optional 
dlang-libevent_2.0.16.1~really2.0.2-0.1_all.deb
 0f9fe5fd18a4f5130c6219eff2e0270a 6064 devel optional 
dlang-libevent_2.0.16.1~really2.0.2-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAlw2njIPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/Tezrl7IP/0Z5Iuj4CP65XRngNo69Guq7n+lMVaiktZ6l
cVzNq0N+opWfwDFqP9iXUxW4XscXHTfAo+axYnoq/cRIhP5vP/wwvaknf3q6wgx9
y1dAf9XKPIW8+PfyzvmNE5TK0FrQPH9eOfZ1usuldnjWylPTlHG/F1xUwy5IxdqW

Bug#797121: marked as done (plasma-widget-yawp: Not usable anymore in Plasma5)

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 02:44:59 +
with message-id 
and subject line Bug#919149: Removed package(s) from unstable
has caused the Debian Bug report #797121,
regarding plasma-widget-yawp: Not usable anymore in Plasma5
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.)


-- 
797121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-widget-yawp
Version: 0.4.2-1
Severity: serious
Tags: stretch sid
Justification: Not usable anymore

Hi! Plasma 5 has arrived to testing a few weeks ago and so all Plasma 4
widgets have become unusable.

Please consider either porting this widget to Plasma5 or asking for it's
removal from the archive.

Thanks,
Felix
--- End Message ---
--- Begin Message ---
Version: 0.4.2-1+rm

Dear submitter,

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

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

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

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

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

Processed (with 1 error): severity of 919242 is wishlist

[Debian Bug Tracking System]

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

> severity 919242 wishlist
Bug #919242 [quassel-core] quassel-core: fails to start, permission errors
Severity set to 'wishlist' from 'grave'
> tag -1 wontfix
Failed to alter tags of Bug -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_tag did not pass regex check
.

> thanks
Stopping processing here.

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

Bug#919242: update

[martian]

Seems to work when i run

$ aa-disable quassel-core

Seems the AppArmor profile is insufficient when quassel-core is ran by a 
regular user.

Bug#919242: quassel-core: fails to start, permission errors

[martian67]

Seems to work when i run

$ aa-disable quassel-core

Seems the AppArmor profile is insufficient when quassel-core is ran by a 
regular user.

Bug#919242: quassel-core: fails to start, permission errors

[martian]

Package: quassel-core
Version: 1:0.13.0-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When attempting to start quassel-core as a regular user,
it is unable to start, errors below (note occurs without any config files
present. Permissions on the .config directory are drwxr-xr-x  martian:martian
so this is not the issue.

2019-01-13 18:31:03 [Error] Unable to create Quassel config directory: 
/home/martian/.config/quassel-irc.org
2019-01-13 18:31:03 [Warn ] SslServer: Certificate file quasselCert.pem does 
not exist 
2019-01-13 18:31:03 [Warn ] SslServer: Unable to set certificate file
   Quassel Core will still work, but cannot provide SSL for client 
connections.
   Please see https://quassel-irc.org/faq/cert to learn how to enable 
SSL support. 
2019-01-13 18:31:03 [Error] Unable to create Quassel config directory: 
/home/martian/.config/quassel-irc.org
2019-01-13 18:31:03 [Warn ] SslServer: Certificate file quasselCert.pem does 
not exist 
2019-01-13 18:31:03 [Error] Unable to create Quassel config directory: 
/home/martian/.config/quassel-irc.org
2019-01-13 18:31:03 [Warn ] PostgreSQL driver plugin not available for Qt. 
Installed drivers: QSQLITE 
2019-01-13 18:31:03 [Error] Unable to create Quassel config directory: 
/home/martian/.config/quassel-irc.org
2019-01-13 18:31:03 [Error] Unable to create Quassel config directory: 
/home/martian/.config/quassel-irc.org
2019-01-13 18:31:03 [Error] Unable to create Quassel config directory: 
/home/martian/.config/quassel-irc.org
2019-01-13 18:31:03 [Warn ] No storage backend selected! 
2019-01-13 18:31:03 [Error] "Cannot write quasselcore configuration; probably a 
permission problem."

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)

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

Versions of packages quassel-core depends on:
ii  adduser3.118
ii  libc6  2.28-4
ii  libgcc11:8.2.0-14
ii  libqca-qt5-2   2.1.3-2
ii  libqt5core5a   5.11.3+dfsg-2
ii  libqt5network5 5.11.3+dfsg-2
ii  libqt5script5  5.11.3+dfsg-2
ii  libqt5sql5 5.11.3+dfsg-2
ii  libqt5sql5-sqlite  5.11.3+dfsg-2
ii  libstdc++6 8.2.0-14
ii  lsb-base   10.2018112800
ii  openssl1.1.1a-1
ii  zlib1g 1:1.2.11.dfsg-1

quassel-core recommends no packages.

Versions of packages quassel-core suggests:
pn  libqt5sql5-psql  

-- no debconf information

Processed: closing 893190 (afterburner.fx FTBFS with openjdk-9)

[Debian Bug Tracking System]

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

> close 893190 1.7.0-2
Bug #893190 [src:afterburner.fx] afterburner.fx FTBFS with openjdk-9
Bug #910042 [src:afterburner.fx] afterburnr.fx FTBFS: compilation error
Marked as fixed in versions afterburner.fx/1.7.0-2.
Marked as fixed in versions afterburner.fx/1.7.0-2.
Bug #893190 [src:afterburner.fx] afterburner.fx FTBFS with openjdk-9
Bug #910042 [src:afterburner.fx] afterburnr.fx FTBFS: compilation error
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#917503: marked as done (prometheus-alertmanager: FTBFS (cannot use *logLevel as type *promlog.Config))

[Debian Bug Tracking System]

Your message dated Mon, 14 Jan 2019 01:05:54 +
with message-id 
and subject line Bug#917503: fixed in prometheus-alertmanager 0.15.3+ds-1
has caused the Debian Bug report #917503,
regarding prometheus-alertmanager: FTBFS (cannot use *logLevel as type 
*promlog.Config)
to be marked as done.

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

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


-- 
917503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:prometheus-alertmanager
Version: 0.15.1+ds-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 --buildsystem=golang --with=golang,bash-completion \
--builddirectory=build
   dh_update_autotools_config -i -O--buildsystem=golang -O--builddirectory=build
   dh_autoreconf -i -O--buildsystem=golang -O--builddirectory=build
   dh_auto_configure -i -O--buildsystem=golang -O--builddirectory=build
install -d build
Copy silence/silence_test.go -> 
build/src/github.com/prometheus/alertmanager/silence/silence_test.go
Copy silence/silence.go -> 
build/src/github.com/prometheus/alertmanager/silence/silence.go
Copy silence/silencepb/silence.proto -> 
build/src/github.com/prometheus/alertmanager/silence/silencepb/silence.proto
Copy silence/silencepb/silence.pb.go -> 
build/src/github.com/prometheus/alertmanager/silence/silencepb/silence.pb.go
Copy cli/root.go -> 
build/src/github.com/prometheus/alertmanager/cli/root.go
Copy cli/check_config_test.go -> 
build/src/github.com/prometheus/alertmanager/cli/check_config_test.go
Copy cli/config.go -> 
build/src/github.com/prometheus/alertmanager/cli/config.go

[... snipped ...]

github.com/prometheus/alertmanager/silence
github.com/prometheus/alertmanager/template
github.com/prometheus/common/version
golang.org/x/net/context/ctxhttp
net/mail
net/smtp
github.com/prometheus/alertmanager/notify
github.com/prometheus/alertmanager/provider
github.com/prometheus/alertmanager/vendor/github.com/prometheus/prometheus/pkg/labels
github.com/prometheus/alertmanager/dispatch
github.com/prometheus/alertmanager/pkg/parse
github.com/julienschmidt/httprouter
github.com/prometheus/common/route
github.com/prometheus/alertmanager/api
github.com/alecthomas/units
go/token
go/scanner
go/ast
go/doc
gopkg.in/alecthomas/kingpin.v2
github.com/prometheus/alertmanager/cli/config
github.com/prometheus/client_golang/api
github.com/prometheus/alertmanager/client
github.com/prometheus/alertmanager/cli/format
os/user
github.com/prometheus/alertmanager/cli
github.com/prometheus/alertmanager/vendor/github.com/oklog/oklog/pkg/group
github.com/prometheus/alertmanager/inhibit
github.com/prometheus/alertmanager/provider/mem
github.com/prometheus/client_golang/prometheus/promhttp
runtime/pprof
runtime/trace
net/http/pprof
github.com/prometheus/alertmanager/ui
github.com/prometheus/common/promlog
github.com/prometheus/alertmanager/cmd/alertmanager
# github.com/prometheus/alertmanager/cmd/alertmanager
src/github.com/prometheus/alertmanager/cmd/alertmanager/main.go:173:24: cannot 
use *logLevel (type promlog.AllowedLevel) as type *promlog.Config in argument 
to promlog.New
github.com/prometheus/alertmanager/cmd/amtool
flag
testing
github.com/prometheus/alertmanager/test
dh_auto_build: cd build && go install 
-gcflags=all=\"-trimpath=/<>/prometheus-alertmanager-0.15.1\+ds/build/src\"
 
-asmflags=all=\"-trimpath=/<>/prometheus-alertmanager-0.15.1\+ds/build/src\"
 -v -p 1 -ldflags " -X github.com/prometheus/common/version.Version=0.15.1+ds 
-X github.com/prometheus/common/version.Revision=0.15.1+ds-1 -X 
github.com/prometheus/common/version.Branch=debian/sid -X 
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
 -X github.com/prometheus/common/version.BuildDate=20180805-18:58:17 -X 
github.com/prometheus/common/version.GoVersion=go1.10.7" 
github.com/prometheus/alertmanager/api github.com/prometheus/alertmanager/cli 
github.com/prometheus/alertmanager/cli/config 
github.com/prometheus/alertmanager/cli/format 
github.com/prometheus/alertmanager/client 
github.com/prometheus/alertmanager/cluster 
github.com/prometheus/alertmanager/cluster/clusterpb 
github.com/prometheus/alertmanager/cmd/alertmanager github.com
 /prometheus/alertmanager/cmd/amtool github.com/prometheus/alertmanager/config 
github.com/prometheus/alertmanager/dispatch 
github.com/prometheus/alertmanager/inhibit 

Bug#918418: django-prometheus FTBFS: test failures

[Martín Ferrari]

Hi,

On 05/01/2019 22:06, Adrian Bunk wrote:
> Source: django-prometheus

> Some recent change in unstable makes django-prometheus FTBFS:

This is due to the changes in the Prometheus Python client library. This
is discussed in https://github.com/korfuri/django-prometheus/issues/83
and there is a PR pending to fix this, but it is not yet complete...

-- 
Martín Ferrari (Tincho)

Bug#919239: ball: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:ball
Version: 1.5.0+git20180813.37fc53c-2
Severity: serious
Tags: ftbfs

Hello Andreas. Just in case this went unnoticed:

This package fails to build with "dpkg-buildpackage -A". From my build log:


[...]
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=cmake --builddirectory=build --with python2
   dh_testroot -i -O--buildsystem=cmake -O--builddirectory=build
   dh_prep -i -O--buildsystem=cmake -O--builddirectory=build
rm -f -- debian/libball1.5-data.substvars 
debian/libball1.5-doc.substvars
rm -fr -- debian/.debhelper/generated/libball1.5-data/ 
debian/libball1.5-data/ debian/tmp/ debian/.debhelper/generated/libball1.5-doc/ 
debian/libball1.5-doc/
   debian/rules override_dh_auto_install-indep
make[1]: Entering directory '/<>/ball-1.5.0+git20180813.37fc53c'
mkdir -p debian/libball1.5-doc/usr/share/doc/libball1.5/html \
debian/libball1.5-data/usr/share/BALL-1.5/doc \
debian/libball1.5-doc/usr/share/doc/libball1.5/html/BALL
cpbuild/usr/share/doc/BALL/TUTORIAL/tutorial.pdf
debian/libball1.5-doc/usr/share/doc/libball1.5/
# we need the BALLView documentation in the data path as well... sorry for that
cp -r build/usr/share/doc/BALL/EXAMPLES/PYTHON/BALLView 
debian/libball1.5-data/usr/share/BALL-1.5/doc
cp -r build/usr/share/doc/BALL/html/*   
debian/libball1.5-doc/usr/share/doc/libball1.5/html/BALL
cp -r build/usr/share/BALL/*debian/libball1.5-data/usr/share/BALL-1.5
make[1]: Leaving directory '/<>/ball-1.5.0+git20180813.37fc53c'
   debian/rules override_dh_install
make[1]: Entering directory '/<>/ball-1.5.0+git20180813.37fc53c'
dh_install
install -d debian/.debhelper/generated/libball1.5-data
install -d debian/.debhelper/generated/libball1.5
install -d debian/.debhelper/generated/libball1.5-dev
install -d debian/.debhelper/generated/libballview1.5
install -d debian/.debhelper/generated/libballview1.5-dev
install -d debian/.debhelper/generated/python-ball
install -d debian/.debhelper/generated/ballview
install -d debian/.debhelper/generated/libball1.5-doc
dh_sip
(grep -a -s -v sip:Depends debian/libball1.5-data.substvars; echo 
sip:Depends=sip-api-12.5) > debian/libball1.5-data.substvars.new
mv debian/libball1.5-data.substvars.new debian/libball1.5-data.substvars
(grep -a -s -v sip:Depends debian/libball1.5-doc.substvars; echo 
sip:Depends=sip-api-12.5) > debian/libball1.5-doc.substvars.new
mv debian/libball1.5-doc.substvars.new debian/libball1.5-doc.substvars
find debian/python-ball/usr/lib/python*/dist-packages/ -name BALLPyMacros.h 
-delete
find: 'debian/python-ball/usr/lib/python*/dist-packages/': No such file or 
directory
make[1]: *** [debian/rules:158: override_dh_install] Error 1
make[1]: Leaving directory '/<>/ball-1.5.0+git20180813.37fc53c'
make: *** [debian/rules:16: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The usual recipe in cases like this is to split override_dh_install
into override_dh_install-arch and override_dh_install-indep.

Thanks.

Processed: fixed 918605 in ruby-rspec-rails/3.8.1-2

[Debian Bug Tracking System]

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

> fixed 918605 ruby-rspec-rails/3.8.1-2
Bug #918605 {Done: Cédric Boutillier } 
[src:ruby-rspec-rails] ruby-rspec-rails FTBFS with rails 5.2
Marked as fixed in versions ruby-rspec-rails/3.8.1-2.
> thanks
Stopping processing here.

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

Bug#918588: libtool: generated libtool script is broken, affecting build on AIX

[Vincent Lefevre]

Hi,

On 2019-01-12 14:33:06 +, Alastair McKinstry wrote:
> I've disabled patch
> 0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch, which includes the
> 'func_quote' code in the diff, which should revert back to previous working
> behavior, but I've no AIX system to debug or test.
> Can you test with 2.4.6-7 , just uploaded ?

Thanks. This solves the problem.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#898969: Possible solution released

[Trout, Diane E.]

Hi,

I wasn't able to figure out how to test the trigger solution suggested
by Paul Wise. I did end up taking so long to fix this that OpenSSL
1.1.1 was released, and I tried to set an installation dependency so
the updated version of openssl would be installed first.

It does check to see if the too small keys are installed, deletes them
and then regenerates the keys. (With an autopkgtest)

Diane


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

Bug#898969: marked as done (dnssec-trigger: fails with OpenSSL 1.1.1 due to too-small key and unknown ca)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 22:49:22 +
with message-id 
and subject line Bug#898969: fixed in dnssec-trigger 0.17+repack-1
has caused the Debian Bug report #898969,
regarding dnssec-trigger: fails with OpenSSL 1.1.1 due to too-small key and 
unknown ca
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.)


-- 
898969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-trigger
Version: 0.15+repack-1
Severity: important

I have two existing installations of dnssec-trigger that have 1536-bit
client and server keys.  I'm using the OpenSSL from experimental, which
rejects keys of less than 2048 bits in size, as they are presently
considered too weak.  Consequently, dnssec-trigger fails to start:

May 18 01:16:15 genre dnssec-triggerd[721856]: May 18 01:16:15 
dnssec-triggerd[721856] error: Error for server-cert-file: 
/etc/dnssec-trigger/dnssec_trigger_server.pem
May 18 01:16:15 genre dnssec-triggerd[721856]: May 18 01:16:15 
dnssec-triggerd[721856] error: Error in SSL_CTX use_certificate_file crypto 
error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
May 18 01:16:15 genre dnssec-triggerd[721856]: May 18 01:16:15 
dnssec-triggerd[721856] error: cannot setup SSL context
May 18 01:16:15 genre dnssec-triggerd[721856]: May 18 01:16:15 
dnssec-triggerd[721856] fatal error: could not init server

I noticed the current version of dnssec-trigger uses 3072 bit keys.  To
ensure upgrades continue to work, dnssec-trigger probably needs to
regenerate the keys if they are too small.

As a potentially relevant note, I noticed the
dnssec-triggerd-keygen.service creates the keys in /etc, not
/etc/dnssec-trigger.

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

Kernel: Linux 4.15.0-3-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)
LSM: AppArmor: enabled

Versions of packages dnssec-trigger depends on:
ii  gir1.2-nm-1.0   1.10.8-1
ii  libc6   2.27-3
ii  libgdk-pixbuf2.0-0  2.36.11-2
ii  libglib2.0-02.56.1-2
ii  libgtk2.0-0 2.24.32-1
ii  libldns21.7.0-3+b1
ii  libssl1.1   1.1.1~~pre6-2
ii  python3 3.6.5-3
ii  python3-gi  3.28.2-1
ii  python3-lockfile1:0.12.2-2
ii  unbound 1.6.7-1

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- Configuration Files:
/etc/dnssec-trigger/dnssec-trigger.conf changed:
url: "http://fedoraproject.org/static/hotspot.txt OK"
url: "http://ster.nlnetlabs.nl/hotspot.txt OK"
tcp80: 185.49.140.67
tcp80: 2a04:b900::10:0:0:67
ssl443: 185.49.140.67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF
ssl443: 2a04:b900::10:0:0:67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF


-- no debconf information

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: dnssec-trigger
Source-Version: 0.17+repack-1

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated dnssec-trigger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Jan 2019 13:10:28 -0800
Source: dnssec-trigger
Binary: dnssec-trigger
Architecture: source
Version: 0.17+repack-1
Distribution: unstable
Urgency: medium
Maintainer: dnssec-trigger packagers 
Changed-By: Diane Trout 
Description:
 dnssec-trigger - reconfiguration tool to make DNSSEC work
Closes: 898969
Changes:
 dnssec-trigger (0.17+repack-1) 

Bug#919237: node-jsonld: FTBFS in sid (Error: Can't resolve 'rdf-canonize')

[Santiago Vila]

Package: src:node-jsonld
Version: 1.4.0-2
Severity: serious
Tags: ftbfs

Hello Jonas.

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
BROWSERSLIST='node 6' babeljs \
--no-babelrc --presets=env \
--out-dir dist/node6/lib \
-- lib
lib/ActiveContextCache.js -> dist/node6/lib/ActiveContextCache.js
lib/DocumentCache.js -> dist/node6/lib/DocumentCache.js
lib/JsonLdError.js -> dist/node6/lib/JsonLdError.js
lib/JsonLdProcessor.js -> dist/node6/lib/JsonLdProcessor.js
lib/NQuads.js -> dist/node6/lib/NQuads.js

[... snipped ...]

 [239] /usr/lib/nodejs/core-js/fn/symbol/index.js 254 bytes {0} [built]
 [247] ./lib/jsonld.js 54.6 kB {0} [built]
 [281] ./lib/flatten.js 1.06 kB {0} [built]
 [282] ./lib/fromRdf.js 17.3 kB {0} [built]
 [283] ./lib/toRdf.js 10.3 kB {0} [built]
+ 277 hidden modules

WARNING in jsonld.min.js from UglifyJs
Side effects in initialization of unused variable _expandIri 
[./lib/jsonld.js:66,13]
Condition always false 
[./usr/lib/nodejs/regenerator-runtime/runtime.js:21,17]
Dropping side-effect-free statement [./lib/frame.js:91,23]
Side effects in initialization of unused variable _ret 
[./lib/frame.js:91,23]
Dropping side-effect-free statement [./lib/compact.js:165,40]
Side effects in initialization of unused variable _ret 
[./lib/compact.js:165,40]

ERROR in ./lib/jsonld.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/jsonld.js 60:15-38
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js

ERROR in ./lib/NQuads.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/NQuads.js 8:17-40
 @ ./lib/jsonld.js
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js

ERROR in ./lib/util.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/util.js 39:23-46
 @ ./lib/jsonld.js
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js
make[1]: *** [debian/rules:8: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ends in my autobuilder, but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-jsonld.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#919235: abcm2ps: FTBFS because debhelper uses ninja build system instead of autoconf

[Nicolas Boulenguez]

Package: abcm2ps
Version: 8.14.2-0.1
Severity: serious
Tags: patch
Justification: failure to build from scratch

Hello.

My NMU fails to build because debhelper uses ./build.ninja instead of
./configure and ./Makefile.in.  This is quite surprising, and I cannot
reproduce the issue in my chroot.

However, the attached patch selects an explicit build system and most
probably fixes the issue. It upgrades to debhelper 12 as well.

Do you want to upload the fix?
May I prepare another NMU?
Shall I set a shorter delay?
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+abcm2ps (8.14.2-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Debhelper 12.
+  * Fix the build with an explicit debhelper build system.
+
+ -- Nicolas Boulenguez   Sun, 13 Jan 2019 18:10:08 +0100
+
 abcm2ps (8.14.2-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
--- a/debian/compat
+++ /dev/null
@@ -1,1 +0,0 @@
-11
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: text
 Priority: optional
 Maintainer: Anselm Lingnau 
 Build-Depends:
- debhelper (>= 11),
+ debhelper-compat (= 12),
  libfreetype6-dev,
  libpango1.0-dev,
  pkg-config,
--- a/debian/rules
+++ b/debian/rules
@@ -4,4 +4,4 @@ export DEB_BUILD_MAINT_OPTIONS := hardening=+all
 export DEB_LDFLAGS_MAINT_APPEND := -Wl,--as-needed
 
 %:
-	dh $@
+	dh $@ --buildsystem=autoconf

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

[Aryan Duggal]

I was able to solve the problem by temporarily compiling it from
https://git.zx2c4.com/WireGuard and installing it

On Mon, 14 Jan 2019, 03:37 Aryan Duggal  DKMS make.log for wireguard-0.0.20181218 for kernel 5.0.0-rc1+ (x86_64)
> Sun Jan 13 21:52:56 GMT 2019
> make: Entering directory '/usr/src/linux-headers-5.0.0-rc1+'
>   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/main.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/noise.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/device.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/peer.o
> /var/lib/dkms/wireguard/0.0.20181218/build/noise.c: In function
> ‘tai64n_now’:
> /var/lib/dkms/wireguard/0.0.20181218/build/noise.c:453:2: error: implicit
> declaration of function ‘getnstimeofday64’; did you mean ‘getnstimeofday’?
> [-Werror=implicit-function-declaration]
>   getnstimeofday64();
>   ^~~~
>   getnstimeofday
>   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/timers.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/queueing.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/send.o
> cc1: some warnings being treated as errors
> make[1]: *** [scripts/Makefile.build:277:
> /var/lib/dkms/wireguard/0.0.20181218/build/noise.o] Error 1
> make[1]: *** Waiting for unfinished jobs
> make: *** [Makefile:1554:
> _module_/var/lib/dkms/wireguard/0.0.20181218/build] Error 2
> make: Leaving directory '/usr/src/linux-headers-5.0.0-rc1+'
>
> On Mon, 14 Jan 2019, 03:36 anupritaisno1 
>> Package: wireguard-dkms
>> Version: 0.0.20181218-1
>> Severity: grave
>> Justification: renders package unusable
>>
>>
>>
>> -- System Information:
>> Debian Release: buster/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386, i686
>>
>> Kernel: Linux 5.0.0-rc1+ (SMP w/4 CPU cores)
>> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
>> (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>>
>> Versions of packages wireguard-dkms depends on:
>> ii  dkms  2.6.1-3
>>
>> Versions of packages wireguard-dkms recommends:
>> ii  wireguard-tools  0.0.20181218-1
>>
>> wireguard-dkms suggests no packages.
>>
>> -- no debconf information
>>
>

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

[Aryan Duggal]

DKMS make.log for wireguard-0.0.20181218 for kernel 5.0.0-rc1+ (x86_64)
Sun Jan 13 21:52:56 GMT 2019
make: Entering directory '/usr/src/linux-headers-5.0.0-rc1+'
  CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/main.o
  CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/noise.o
  CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/device.o
  CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/peer.o
/var/lib/dkms/wireguard/0.0.20181218/build/noise.c: In function
‘tai64n_now’:
/var/lib/dkms/wireguard/0.0.20181218/build/noise.c:453:2: error: implicit
declaration of function ‘getnstimeofday64’; did you mean ‘getnstimeofday’?
[-Werror=implicit-function-declaration]
  getnstimeofday64();
  ^~~~
  getnstimeofday
  CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/timers.o
  CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/queueing.o
  CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/send.o
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:277:
/var/lib/dkms/wireguard/0.0.20181218/build/noise.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:1554:
_module_/var/lib/dkms/wireguard/0.0.20181218/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.0.0-rc1+'

On Mon, 14 Jan 2019, 03:36 anupritaisno1  Package: wireguard-dkms
> Version: 0.0.20181218-1
> Severity: grave
> Justification: renders package unusable
>
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, i686
>
> Kernel: Linux 5.0.0-rc1+ (SMP w/4 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages wireguard-dkms depends on:
> ii  dkms  2.6.1-3
>
> Versions of packages wireguard-dkms recommends:
> ii  wireguard-tools  0.0.20181218-1
>
> wireguard-dkms suggests no packages.
>
> -- no debconf information
>

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

[anupritaisno1]

Package: wireguard-dkms
Version: 0.0.20181218-1
Severity: grave
Justification: renders package unusable



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

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

Versions of packages wireguard-dkms depends on:
ii  dkms  2.6.1-3

Versions of packages wireguard-dkms recommends:
ii  wireguard-tools  0.0.20181218-1

wireguard-dkms suggests no packages.

-- no debconf information

Bug#919213: irqbalance: endless loop during configure, system reaches maximum of open files

[Ben Caradoc-Davies]

Not seen when upgrading irqbalance (1.5.0-0.1 => 1.5.0-2) on sid amd64:

# apt-get dist-upgrade -V
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
   irqbalance (1.5.0-0.1 => 1.5.0-2)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/52.6 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of irqbalance (1.5.0-0.1 -> 1.5.0-2) 
 b1 - #919213 - irqbalance: endless loop during configure, system 
reaches maximum of open files

Summary:
 irqbalance(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 243868 files and directories currently installed.)
Preparing to unpack .../irqbalance_1.5.0-2_amd64.deb ...
Unpacking irqbalance (1.5.0-2) over (1.5.0-0.1) ...
Processing triggers for systemd (240-4) ...
Processing triggers for man-db (2.8.5-1) ...
Setting up irqbalance (1.5.0-2) ...
[completes normally]

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: severity of 918088 is important

[Debian Bug Tracking System]

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

> severity 918088 important
Bug #918088 [libkrb5-3] autofs-ldap: automount dies with SIGABRT after 
libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)"
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

[Pavel Kreuzt]

It's emacspeak-47.0+dfsg-6

On Sun, Jan 13, 2019 at 8:10 PM Paul Gevers  wrote:

> On Sun, 13 Jan 2019 13:25:24 -0600 Rob Browning 
> wrote:
> > > Tried to uninstall emacspeak package only and the problems appears
> again,
> > > so you're right. I'm not able to uninstall it anyway. Should I report
> the
> > > bug to them?
> >
> > Hmm, suppose it may make sense to reassign this bug there for now, so
> > I've done that (above).  We can always reassign it to emacs if that
> > turns out to to be appropriate.
>
> Indeed.
>
> Which version of emacspeak are we talking about here?
>
> Paul
>
>

Bug#917607: marked as done (udev 240 Makes System Unbootable; rootfs Not Found)

[gregor herrmann]

On Sat, 12 Jan 2019 23:18:05 +, Debian Bug Tracking System wrote:

>* sd-device-monitor: Fix ordering of setting buffer size.
>  Fixes an issue with uevents not being processed properly during coldplug
>  stage and some kernel modules not being loaded via "udevadm trigger".
>  (Closes: #917607)

Hi Michael,

thanks alot for the immense amount of effort you've put into fixing
this bug over the last weeks, much appreciated!


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: Dire Straits: Once Upon A Time In The West


signature.asc
Description: Digital Signature

Bug#919228: wrong Recommends:

[Thorsten Alteholz]

Package: toil
Version: 3.18.0-1
Severity: serious
thanks

Package toil Recommends: python3-futures which is not available. So this 
package might not be installable on some systems.

Did you mean python3-future?

  Thorsten

Processed: found 919193 in 1.5.1+dfsg-1

[Debian Bug Tracking System]

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

> found 919193 1.5.1+dfsg-1
Bug #919193 [src:orthanc] orthanc: FTBFS with dcmtk-3.6.4
Marked as found in versions orthanc/1.5.1+dfsg-1.
> thanks
Stopping processing here.

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

Processed: notfound 919193 in 1.5.1+dfgs-1

[Debian Bug Tracking System]

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

> notfound 919193 1.5.1+dfgs-1
Bug #919193 [src:orthanc] orthanc: FTBFS with dcmtk-3.6.4
The source 'orthanc' and version '1.5.1+dfgs-1' do not appear to match any 
binary packages
No longer marked as found in versions orthanc/1.5.1+dfgs-1.
> thanks
Stopping processing here.

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

Processed: fixed 919216 in 0.70-2

[Debian Bug Tracking System]

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

> fixed 919216 0.70-2
Bug #919216 [lrslib] lrslib: Tree truncated at depth -1 on i386
Marked as fixed in versions lrslib/0.70-2.
> thanks
Stopping processing here.

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

Processed: retitle 919223 to ruby-haml-contrib: missing build dependency on ruby-temple

[Debian Bug Tracking System]

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

> retitle 919223 ruby-haml-contrib: missing build dependency on ruby-temple
Bug #919223 [src:ruby-haml-contrib] ruby-haml-contrib FTBFS with ruby-haml 
5.0.4-1
Changed Bug title to 'ruby-haml-contrib: missing build dependency on 
ruby-temple' from 'ruby-haml-contrib FTBFS with ruby-haml 5.0.4-1'.
> thanks
Stopping processing here.

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

Bug#911948: marked as done ([src:pion] FTBFS with boost1.67)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 20:59:24 +
with message-id 
and subject line Bug#911948: fixed in pion 5.0.7+dfsg-5
has caused the Debian Bug report #911948,
regarding [src:pion] FTBFS with boost1.67
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.)


-- 
911948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pion
Version: 5.0.7+dfsg-4
Severity: wishlist
Tags: patch
User: team+bo...@tracker.debian.org
Usertags: boost1.67

Dear Maintainer,

your package fails to build with boost1.67. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.67 dependencies can be found
adding this line to your sources.list file:

  deb https://people.debian.org/~gio/reprepro unstable main

This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.67 of Boost is promoted to default.

More specifically, your package fails building because there were some
slight API changes in boost::asio and boost::unit_test. The attached
patch should fix this issue.

Please consider applying the attached patch as soon as boost1.67 is made
default in order to avoid FTBFS.

Thanks and all the best, Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles
From: Giovanni Mascellani 
Date: Tue, 23 Oct 2018 08:44:14 +0200
Subject: Fix build with Boost 1.67.

ssl::context constructor does not accept anymore the io_service&
argument and boost::unit_test::unit_test_log_formatter added
log_level arguments to a couple of callbacks.
---
 include/pion/tcp/connection.hpp | 6 +++---
 include/pion/test/unit_test.hpp | 4 ++--
 src/tcp_server.cpp  | 8 
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/include/pion/tcp/connection.hpp b/include/pion/tcp/connection.hpp
index ac2593e..ec56fef 100644
--- a/include/pion/tcp/connection.hpp
+++ b/include/pion/tcp/connection.hpp
@@ -109,7 +109,7 @@ public:
 explicit connection(boost::asio::io_service& io_service, const bool ssl_flag = false)
 :
 #ifdef PION_HAVE_SSL
-m_ssl_context(io_service, boost::asio::ssl::context::sslv23),
+m_ssl_context(boost::asio::ssl::context::sslv23),
 m_ssl_socket(io_service, m_ssl_context),
 m_ssl_flag(ssl_flag),
 #else
@@ -131,7 +131,7 @@ public:
 connection(boost::asio::io_service& io_service, ssl_context_type& ssl_context)
 :
 #ifdef PION_HAVE_SSL
-m_ssl_context(io_service, boost::asio::ssl::context::sslv23),
+m_ssl_context(boost::asio::ssl::context::sslv23),
 m_ssl_socket(io_service, ssl_context), m_ssl_flag(true),
 #else
 m_ssl_context(0),
@@ -692,7 +692,7 @@ protected:
   connection_handler finished_handler)
 :
 #ifdef PION_HAVE_SSL
-m_ssl_context(io_service, boost::asio::ssl::context::sslv23),
+m_ssl_context(boost::asio::ssl::context::sslv23),
 m_ssl_socket(io_service, ssl_context), m_ssl_flag(ssl_flag),
 #else
 m_ssl_context(0),
diff --git a/include/pion/test/unit_test.hpp b/include/pion/test/unit_test.hpp
index 8ff196a..97e5d50 100644
--- a/include/pion/test/unit_test.hpp
+++ b/include/pion/test/unit_test.hpp
@@ -193,12 +193,12 @@ namespace test {// begin namespace test
 os << "" << std::endl;
 }
 
-virtual void entry_context_finish( std::ostream& os )
+virtual void entry_context_finish( std::ostream& os, boost::unit_test::log_level )
 {
 os << "" << std::endl;
 }
 
-virtual void log_entry_context( std::ostream& os, boost::unit_test::const_string value )
+virtual void log_entry_context( std::ostream& os, boost::unit_test::log_level, boost::unit_test::const_string value )
 {
 log_entry_value(os, value);
 }
diff --git a/src/tcp_server.cpp b/src/tcp_server.cpp
index a3e2965..5750ae6 100644
--- a/src/tcp_server.cpp
+++ b/src/tcp_server.cpp
@@ -25,7 +25,7 @@ server::server(scheduler& sched, const unsigned int tcp_port)
 m_active_scheduler(sched),
 m_tcp_acceptor(m_active_scheduler.get_io_service()),
 #ifdef PION_HAVE_SSL
-m_ssl_context(m_active_scheduler.get_io_service(), boost::asio::ssl::context::sslv23),
+m_ssl_context(boost::asio::ssl::context::sslv23),
 #else
 m_ssl_context(0),
 #endif
@@ -37,7 +37,7 @@ server::server(scheduler& sched, const boost::asio::ip::tcp::endpoint& endpoint)
 m_active_scheduler(sched),
 

Bug#919225: libballview1.5-dev: missing Breaks+Replaces: libballview1.4-dev

[Andreas Beckmann]

Package: libballview1.5-dev
Version: 1.5.0+git20180813.37fc53c-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack 
.../libballview1.5-dev_1.5.0+git20180813.37fc53c-1_amd64.deb ...
  Unpacking libballview1.5-dev (1.5.0+git20180813.37fc53c-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libballview1.5-dev_1.5.0+git20180813.37fc53c-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/include/BALL/VIEW/DATATYPE/colorExtensions.h', 
which is also in package libballview1.4-dev 1.4.3~beta1-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/var/cache/apt/archives/libballview1.5-dev_1.5.0+git20180813.37fc53c-1_amd64.deb


cheers,

Andreas


libballview1.4-dev=1.4.3~beta1-3_libballview1.5-dev=1.5.0+git20180813.37fc53c-1.log.gz
Description: application/gzip

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

[Pavel Kreuzt]

Tried to uninstall emacspeak package only and the problems appears again,
so you're right. I'm not able to uninstall it anyway. Should I report the
bug to them?

On Sat, Jan 12, 2019 at 6:43 PM Rob Browning  wrote:

> Pavel Kreuzt  writes:
>
> > Package: emacs-gtk
> > Version: 1:25.2+1-11
> > Severity: important
> >
> > Dear Maintainer,
> >
> > when trying to upgrade emacs to 1.26.1+1-3, some installation script
> fails with following error:
>
> I think it's very likely that this isn't a bug in emacs, but rather one
> of the add-on packages, perhaps emacspeak, judging from the placement.
>
> > Remove emacspeak for emacs
> > remove/emacspeak: purging byte-compiled files for emacs
> > rm: missing operand
> > Try 'rm --help' for more information.
> > ERROR: remove script from emacspeak package failed
> > dpkg: warning: old emacs-gtk package pre-removal script subprocess
> returned error exit status 1
> > dpkg: trying script from the new package instead ...
>
> --
> Rob Browning
> rlb @defaultvalue.org and @debian.org
> GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
> GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
>

Processed: Re: Bug#907997: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 emacs/1:26.1+1-1
Bug #907997 [emacs-lucid] emacs-lucid: trying to overwrite 
'/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2
Marked as fixed in versions emacs/1:26.1+1-1.

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

Bug#907997: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2

[Rob Browning]

Control: fixed -1 emacs/1:26.1+1-1

I think this bug may now be "fixed" by the switch of the emacs package
to upstream 26.1, which should avoid including any of the conflicting
paths.

While we may also consider simplifying the control dependencies now, I
think this problem is likely resolved.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#919223: ruby-haml-contrib FTBFS with ruby-haml 5.0.4-1

[Adrian Bunk]

Source: ruby-haml-contrib
Version: 1.0.0.1-2
Severity: serious
Tags: ftbfs buster sid

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

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

RUBYLIB=/build/1st/ruby-haml-contrib-1.0.0.1/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-haml-contrib/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 debian/ruby-tests.rb
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- temple (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/haml/temple_engine.rb:2:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/haml/engine.rb:11:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/haml.rb:23:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/1st/ruby-haml-contrib-1.0.0.1/test/test_helper.rb:1:in 
`'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/1st/ruby-haml-contrib-1.0.0.1/test/php_filter_test.rb:1:in 
`'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from debian/ruby-tests.rb:2:in `block in '
from debian/ruby-tests.rb:2:in `each'
from debian/ruby-tests.rb:2:in `'
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-haml-contrib-1.0.0.1/debian/ruby-haml-contrib returned exit 
code 1
make: *** [debian/rules:4: binary] Error 1

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

[Paul Gevers]

On Sun, 13 Jan 2019 13:25:24 -0600 Rob Browning 
wrote:
> > Tried to uninstall emacspeak package only and the problems appears again,
> > so you're right. I'm not able to uninstall it anyway. Should I report the
> > bug to them?
> 
> Hmm, suppose it may make sense to reassign this bug there for now, so
> I've done that (above).  We can always reassign it to emacs if that
> turns out to to be appropriate.

Indeed.

Which version of emacspeak are we talking about here?

Paul



signature.asc
Description: OpenPGP digital signature

Processed: tagging 917761, tagging 919048, fixed 917761 in 2.0.0~beta1-1

[Debian Bug Tracking System]

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

> tags 917761 + experimental
Bug #917761 {Done: David Prévot } [src:php-monolog] 
php-monolog: FTBFS: PHP Fatal error:  Uncaught Error: Class 
'PHPUnit_Framework_TestCase' not found in 
/<>/tests/Monolog/ErrorHandlerTest.php:16
Added tag(s) experimental.
> tags 919048 + sid buster
Bug #919048 [ruby-haml-rails] ruby-haml-rails: Depends: ruby-haml (< 5.0) but 
5.0.4-1 is to be installed
Added tag(s) sid and buster.
> fixed 917761 2.0.0~beta1-1
Bug #917761 {Done: David Prévot } [src:php-monolog] 
php-monolog: FTBFS: PHP Fatal error:  Uncaught Error: Class 
'PHPUnit_Framework_TestCase' not found in 
/<>/tests/Monolog/ErrorHandlerTest.php:16
Marked as fixed in versions php-monolog/2.0.0~beta1-1.
> thanks
Stopping processing here.

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

Bug#919060: same problem here...

[Dragos Jarca]

after apt-get update and apt-get dist-upgrade...

now gitlab cannot be used...

cannot upgrade to experimental to...

root@omv:/usr/share/gitlab# apt-get install ruby-gitaly=1.5.0+dfsg-1 
ruby-responders ruby-default-value-for=3.1.1-1 ruby-devise 
ruby-doorkeeper ruby-doorkeeper-openid-connect ruby-recaptcha 
ruby-devise-two-factor ruby-browser ruby-graphiql-rails 
ruby-acts-as-taggable-on ruby-redis-rails ruby-asana=0.8.1-1 
ruby-kubeclient=4.2.0-1 ruby-webpack-rails ruby-sass-rails 
ruby-font-awesome-rails ruby-premailer-rails ruby-rails-i18n=5.1.2-1 
ruby-peek ruby-peek-gc ruby-peek-pg ruby-peek-rblineprof ruby-peek-redis 
ruby-lograge ruby-actionmailer=2:5.2.2+dfsg-1 
ruby-actionpack=2:5.2.2+dfsg-1 ruby-actionview=2:5.2.2+dfsg-1 
ruby-activemodel=2:5.2.2+dfsg-1 ruby-activerecord=2:5.2.2+dfsg-1 
ruby-activesupport=2:5.2.2+dfsg-1 ruby-activestorage ruby-actioncable 
ruby-activejob=2:5.2.2+dfsg-1 ruby-railties=2:5.2.2+dfsg-1 
ruby-sprockets-rails ruby-rack=2.0.6-3 ruby-rails=2:5.2.2+dfsg-1 
gitlab-common=11.6.0+dfsg-1 ruby-rails-dom-testing=2.0.3-3 
ruby-arel=9.0.0-2 ruby-http=3.3.0-1 ruby-http-form-data=2.1.0-1 
rails=2:5.2.2+dfsg-1 gitlab=11.6.0+dfsg-1 gitaly=1.12.0+debian-1 
ruby-actionpack-xml-parser=2.0.1-1 redmine ruby-protected-attributes=1.1.4-2

Reading package lists... Done
Building dependency tree
Reading state information... Done
ruby-sprockets-rails is already the newest version (2.3.2-1).
ruby-sprockets-rails set to manually installed.
ruby-graphiql-rails is already the newest version (1.4.10-1).
ruby-graphiql-rails set to manually installed.
redmine is already the newest version (3.4.6-1).
ruby-acts-as-taggable-on is already the newest version (5.0.0-2).
ruby-acts-as-taggable-on set to manually installed.
ruby-browser is already the newest version (2.5.3-1).
ruby-browser set to manually installed.
ruby-devise is already the newest version (4.5.0-1).
ruby-devise set to manually installed.
ruby-devise-two-factor is already the newest version (3.0.3-1).
ruby-devise-two-factor set to manually installed.
ruby-doorkeeper is already the newest version (4.4.2-1).
ruby-doorkeeper set to manually installed.
ruby-doorkeeper-openid-connect is already the newest version (1.5.2-1).
ruby-doorkeeper-openid-connect set to manually installed.
ruby-font-awesome-rails is already the newest version (4.7.0.4-1).
ruby-font-awesome-rails set to manually installed.
ruby-lograge is already the newest version (0.10.0-1).
ruby-lograge set to manually installed.
ruby-peek is already the newest version (1.0.1-1).
ruby-peek set to manually installed.
ruby-peek-gc is already the newest version (0.0.2-1).
ruby-peek-gc set to manually installed.
ruby-peek-pg is already the newest version (1.3.0-1).
ruby-peek-pg set to manually installed.
ruby-peek-rblineprof is already the newest version (0.2.0-1).
ruby-peek-rblineprof set to manually installed.
ruby-peek-redis is already the newest version (1.2.0-1).
ruby-peek-redis set to manually installed.
ruby-premailer-rails is already the newest version (1.9.7-1).
ruby-premailer-rails set to manually installed.
ruby-protected-attributes is already the newest version (1.1.4-2).
ruby-protected-attributes set to manually installed.
ruby-recaptcha is already the newest version (4.11.1-1).
ruby-recaptcha set to manually installed.
ruby-redis-rails is already the newest version (5.0.2-3).
ruby-redis-rails set to manually installed.
ruby-responders is already the newest version (2.4.0-3).
ruby-responders set to manually installed.
ruby-sass-rails is already the newest version (5.0.6-2).
ruby-sass-rails set to manually installed.
ruby-webpack-rails is already the newest version (0.9.11+git-1).
ruby-webpack-rails set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ruby-protected-attributes : Depends: ruby-activemodel (< 2:5.0) but 
2:5.2.2+dfsg-1 is to be installed

E: Unable to correct problems, you have held broken packages.
root@omv:/usr/share/gitlab#

Seems that is a incopatibility between gitlab and redmine...

I try to use in production and now my team cannot commit changes.

--
Cu respect,
Dragos Jarca
Owner
Dynamic Puzzle S.R.L.
www.dynamicpuzzle.ro

Bug#919217: Missing dependency on devscripts

[Jeroen Dekkers]

Package: lintian-brush
Version: 0.10
Severity: serious

Lintian-brush must depend on devscripts because it calls dch to update
the changelog.

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

Kernel: Linux 4.9.0-8-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)

Bug#919216: lrslib: Tree truncated at depth -1 on i386

[David Bremner]

Package: lrslib
Version: 0.62-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: fixed -1 0.70-2

On i386, I tried 3 or for sample ine files from the source and each
one terminated after reporting a single basis. Sample run follows.


(unstable-i386-sbuild)bremner@convex:~/lrslib/ine/cocoa13$ lrs bv8.ine 

*lrs:lrslib v.6.2 2016.3.28(64bit,lrsgmp.h gmp v.6.1)
*Copyright (C) 1995,2016, David Avis   a...@cs.mcgill.ca 
*Input taken from file bv8.ine
V-representation
begin
* 73 rational
 1  0  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0  0  
0  0  0  1  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0 
 0  0  0  0  1  0  0  0  0  0  0  0  1  2  3  4  5  6  7  8 
V#1 R#0 B#1 h=0 facets  24 25 26 27 28 29 32 33 34 35 36 39 40 41 42 43 46 47 
48 49 50 53 54 55 56 57 60 61 62 63 64 67 68 69 70 71 74 75 76 77 78 79 81 82 
83 84 85 86 87 I#56 det= 1  in_det= 1  z= 0 
end
*Tree truncated at depth -1
*Totals: vertices=1 rays=0 bases=1 integer_vertices=1 
*Dictionary Cache: max size= 1 misses= 1/1   Tree Depth= 0
*lrs:lrslib v.6.2 2016.3.28(64bit,lrsgmp.h)
*0.017u 0.000s 1692Kb 0 flts 0 swaps 32 blks-in 0 blks-out 

I'm not sure this is really worth debugging, as it seems fixed in the
version in experimental.


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

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

Versions of packages lrslib depends on:
ii  libc6 2.28-2
ii  libgmp10  2:6.1.2+dfsg-4
ii  liblrs0   0.70-1

lrslib recommends no packages.

lrslib suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlw7Z+oACgkQ8gKXHaSn
niy2GAwAkfkrEq2++ySRFA82ydX6vvvLSexbCpn/h+UFwdxOZYtV4kgDwZDBrHww
0W5PZrbKTvMNiVQCDW7lqdKlgEofiiaTRCQunosM2biSQYhpoX+fDjf5SkrDArUL
nuwbnr1ue9af0HvVXHiKpRuNONiJ/6JeIwxhceXS89AM1SJrjhMrePIkVtnjvtkL
r+npIlckY5ToGWpuXay5BJ6wTpZGuoWQkSffGPbRB84efQTfayd76xDRSPOhv2SA
wl9aye1mxESVztZZYXDsNasuBpKpHdqM9TQsMG8uTpLin1p6CNvLhwITfyaUgooG
zzDY/cSu2+huzvLvLjmoaqevw5v09n1/HjIrk1a0Qf6seFN++apogXt25B1i1Wg+
kSKvFC0h9QUcYzpI5mn6Rf91RsQD/N4a5q+MqaHG9HLy2r/FnroFAYwxnqVEJXGl
ctHQPVT7QAvBjzhuomJG3IDoVW2xCFROf0S/tP1M7eU8B1Dn6HWcb2qCyHJxRZla
qkhPA1eg
=wiBa
-END PGP SIGNATURE-

Bug#914632: uw-imap: CVE-2018-19518

[Magnus Holmgren]

söndag 13 januari 2019 kl. 08:31:28 CET skrev  Salvatore Bonaccorso:
> On Fri, Dec 28, 2018 at 10:22:53AM +0100, Moritz Mühlenhoff wrote:
> > On Wed, Dec 26, 2018 at 05:20:40PM +0100, Magnus Holmgren wrote:
> > > I'm wondering if anyone would complain if I'd disable RSH (SSH)
> > > connections
> > > altogether.
> > 
> > Full ack, that seems like the most sensible fix.
> 
> Any news on this approach, or did you spot any problem with that way?

Here's my plan. Removing the RSHPATH define should disable the insecure code, 
I reckon. I just haven't been able to make gbp use my long PGP key id...

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer --- a/src/osdep/unix/Makefile
+++ b/src/osdep/unix/Makefile
@@ -985,7 +985,7 @@ onceenv:
 	 -DMD5ENABLE=\"$(MD5PWD)\" -DMAILSPOOL=\"$(MAILSPOOL)\" \
 	 -DANONYMOUSHOME=\"$(MAILSPOOL)/anonymous\" \
 	 -DACTIVEFILE=\"$(ACTIVEFILE)\" -DNEWSSPOOL=\"$(NEWSSPOOL)\" \
-	 -DRSHPATH=\"$(RSHPATH)\" -DLOCKPGM=\"$(LOCKPGM)\" \
+	 -DLOCKPGM=\"$(LOCKPGM)\" \
 	 -DLOCKPGM1=\"$(LOCKPGM1)\" -DLOCKPGM2=\"$(LOCKPGM2)\" \
 	 -DLOCKPGM3=\"$(LOCKPGM3)\" > OSCFLAGS
 	echo $(BASELDFLAGS) $(EXTRALDFLAGS) > LDFLAGS


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

Bug#919213: irqbalance: endless loop during configure, system reaches maximum of open files

[Axel Beckert]

Package: irqbalance
Version: 1.5.0-2
Severity: serious

On one of my systems (not the one I'm writing the report on), a
Raspberry Pi 2 with Debian Sid armhf and sysvinit, the terminal which I
ran the upgrade in, looked like this (excerpt):

Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults

htop looked like this (excerpt):

 root   20   0  179M  1576  1404 S  0.3  0.2  3:10.99 | +- aptitude -u
 root   20   0 10336 0 0 S  0.0  0.0  0:00.71 |+- dpkg 
--status-fd 70 --configure --pending
 root   20   0 17832   748   140 S  0.0  0.1  0:17.01 ||  +- perl 
-w /usr/share/debconf/frontend /var/lib/dpkg/info/irqbalance.postinst configure 
1.5.0-0.1
 root   20   0  1468 0 0 S  0.0  0.0  0:00.01 ||  |  +- sh 
/var/lib/dpkg/info/irqbalance.postinst configure 1.5.0-0.1
 root   20   0  7136 4 0 S  0.0  0.0  0:00.06 ||  | +- 
perl /usr/sbin/update-rc.d irqbalance enable
 root   20   0  5296 0 0 S  0.0  0.0  0:00.00 ||  |
+- systemctl --quiet enable irqbalance
 root   20   0  7136 4 0 S  0.0  0.0  0:00.06 ||  | 
  +- perl /usr/sbin/update-rc.d irqbalance enable
 root   20   0  5296 0 0 S  0.0  0.0  0:00.00 ||  | 
 +- systemctl --quiet enable irqbalance
 root   20   0  7136 4 0 S  0.0  0.0  0:00.06 ||  | 
+- perl /usr/sbin/update-rc.d irqbalance enable
 root   20   0  5296 0 0 S  0.0  0.0  0:00.00 ||  | 
   +- systemctl --quiet enable irqbalance
 root   20   0  7136 4 0 S  0.0  0.0  0:00.06 ||  | 
  +- perl /usr/sbin/update-rc.d irqbalance enable
 root   20   0  5296 0 0 S  0.0  0.0  0:00.00 ||  | 
 +- systemctl --quiet enable irqbalance
 root   20   0  7136 4 0 S  0.0  0.0  0:00.06 ||  | 
+- perl /usr/sbin/update-rc.d irqbalance enable
 root   20 

Bug#918848: Plans for stretch-backports wrt. CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866?

[intrigeri]

intrigeri:
> Michael Biebl:
>> Please let us know about the results of those tests.

> Will do!

All green from the perspective of Tails' integration test suite :)

I'll let you know if the reviewer for this Tails proposed change (most
likely lamby) finds issues relevant to Debian.

The backport was totally trivial (start from your stretch backports
branch, merge the newest sid packaging tag, boom):
https://salsa.debian.org/tails-team/systemd/

Cheers,
-- 
intrigeri

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

[Rob Browning]

Control: reassign -1 emacspeak
Control: retitle -1 emacspeak: fails to upgrade with emacs 1.26.1+1-3

Pavel Kreuzt  writes:

> Tried to uninstall emacspeak package only and the problems appears again,
> so you're right. I'm not able to uninstall it anyway. Should I report the
> bug to them?

Hmm, suppose it may make sense to reassign this bug there for now, so
I've done that (above).  We can always reassign it to emacs if that
turns out to to be appropriate.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Processed: Re: Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 emacspeak
Bug #919001 [emacs-gtk] emacs-gtk: fails to upgrade to 1.26.1+1-3
Bug reassigned from package 'emacs-gtk' to 'emacspeak'.
No longer marked as found in versions emacs/1:25.2+1-11.
Ignoring request to alter fixed versions of bug #919001 to the same values 
previously set
> retitle -1 emacspeak: fails to upgrade with emacs 1.26.1+1-3
Bug #919001 [emacspeak] emacs-gtk: fails to upgrade to 1.26.1+1-3
Changed Bug title to 'emacspeak: fails to upgrade with emacs 1.26.1+1-3' from 
'emacs-gtk: fails to upgrade to 1.26.1+1-3'.

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

Bug#913014: marked as done (e3 (all binaries): immediate segmentation fault)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 18:04:43 +
with message-id 
and subject line Bug#913014: fixed in e3 1:2.71-2
has caused the Debian Bug report #913014,
regarding e3 (all binaries): immediate segmentation fault
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.)


-- 
913014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e3
Version: 1:2.71-1
Severity: grave


Dear maintainer,

I'm unable to run e3 and related binaries (e3em, e3ne, e3pi, e3vi and e3ws):

 $ e3
 Segmentation fault

 $ gdb e3
 [...]
 Reading symbols from e3...(no debugging symbols found)...done.
 (gdb) run
 Starting program: /usr/bin/e3
 During startup program terminated with signal SIGSEGV, Segmentation fault.
 (gdb) bt
 No stack.

A little bit more infos after executing the same command on tty1:

 $ e3
 3938 (e3): Uhuuh, elf segment at 0804b000 requested but the memory is
mapped already
 Segmentation fault

On a virtualized Debian Stretch this problem doesn't occurs.

Kind regards.


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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: e3
Source-Version: 1:2.71-2

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

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated e3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Jan 2019 17:46:12 +
Source: e3
Binary: e3
Architecture: source
Version: 1:2.71-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Dmitry Bogatov 
Description:
 e3 - very small text editor
Closes: 913014
Changes:
 e3 (1:2.71-2) unstable; urgency=medium
 .
   * QA upload.
   * Set Maintainer field to QA group
   * wrap-and-sort -sta
   * Fix whitespace errors in following files:
 + debian/changelog
 + debian/postinst
   * Update standards version to 4.3.0 (no changes needed)
   * Update debhelper compat to 11
   * Build-depend on `debhelper-compat' (obsoletes `debian/compat')
   * Update Vcs-* fields in `debian/control'
   * Convert source format to 3.0 (quilt), unapplied
   * Simplify `debian/rules'
   * Apply patch to avoid segmentation faults (Closes: #913014)
 + Thanks: Bernhard Übelacker 
   * Improve wording and formatting of package description
   * Update lintian-overrides file
Checksums-Sha1:
 55a1afc73636775ff63b9f632c4cf320a6adf7a3 1977 e3_2.71-2.dsc
 61a001dcb779f1d50cc77e9d4c273bc4a2f19e71 4884 e3_2.71-2.debian.tar.xz
Checksums-Sha256:
 0c344d6031b893f93989597770aca7fa4cc9496eb2419c3df890d9f517e70620 1977 
e3_2.71-2.dsc
 f60f6c49cb331d388aff775b5a7898528e4864cc731bd2db5c2a4b4cc845a20c 4884 
e3_2.71-2.debian.tar.xz
Files:
 b10e272f9392ac1d7a706b64736cfd9d 1977 editors optional e3_2.71-2.dsc
 b3d7bec8c95144eebe5e9ee4ccd746a2 4884 editors optional e3_2.71-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAlw7em0THGthY3Rpb25A
ZGViaWFuLm9yZwAKCRBIEtjeqCYR5jRHD/kBiIGCvYx+12n22P9ya808mqmuRu10
eRDs0cHf8UlhTjt2d2m40NDTXqU91Vvps1dCQ4IquHdPn9Mn/kAvviMol/nPxHK0
9aun55alQM6NNZ6XQNlubOeBkyV8Zzbe8wbFm8BXoYnEG7dx3VMm2YZhNmTNuP0u
WaGX2O7x0qd6BIr/iyBUdBUXL3VrzHmWtI5dw1tE3sy1dRGFwml7zBqeH+R8J/Rr
sKMKTmXFZ4mt89LJuuFue5fJYeIsysLHjnF5+Q8i5oVHVQie9SqZu4M1H8piSxqy
bo40H/KjEFOxdRe0Xh/NMbf69IOOvndFZRsIoLjAEcGpOxvV25vn3YH77FOXAEGx
HSpHhKwU0sQhehZ9DfMFRS+wXrzAMPl8gcEoIaJidyLJuOi/kLM9gDvun7fU7kEe
3ZXxvi9ZkVHMKSXQFjprRrFFH1PzFbUSo9ehvt7NKjDGzQlL4GFtZHRVnvodDkSA
98ccvToHJoxcrVQCEa58TshGfE06vMb9qp99AGu1KVrPOG80Lv16cvUuup/2GohH
5s51dbSvyLFDv+aZX61omdGs6elXSfiAzE9dehwQz/d+XFKdy9frISs9HyyNVkoF
t6cC4nsMu91M+wfBe0cQn0dsc6rR/zOgC5u+BqxXZv6xDsYlkwdb9c7kSiJyhYwD
p9+Tu/a7VEyVqg==
=01GK

Bug#918447: marked as done (pelican: fails to build: wrong dependency?)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 18:20:34 +
with message-id 
and subject line Bug#918447: fixed in pelican 4.0.1+dfsg-1
has caused the Debian Bug report #918447,
regarding pelican: fails to build: wrong dependency?
to be marked as done.

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

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


-- 
918447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pelican
Version: 3.7.1+dfsg-2
Severity: serious
Tags: ftbfs
X-Debbugs-CC: stapp...@debian.org

pelican fails to build. I notice that a dependency on
python3-feedparser was added, but pelican appears to be a Python2
package.

Build log

https://launchpad.net/ubuntu/+source/pelican/3.7.1+dfsg-2/+build/16238504

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: pelican
Source-Version: 4.0.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
pelican, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Geert Stappers  (supplier of updated pelican package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Jan 2019 18:46:23 +0100
Source: pelican
Binary: pelican pelican-doc python-pelican
Architecture: source all
Version: 4.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Applications Team 

Changed-By: Geert Stappers 
Description:
 pelican- blog aware, static website generator
 pelican-doc - blog aware, static website generator (documentation)
 python-pelican - transitional dummy package
Closes: 875255 913875 918447
Changes:
 pelican (4.0.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #913875)
   * Python3. (Closes: #875255)
   * That fixed a FTBFS (Closes: #918447)
   * Added 'pristine-tar = True', related to #918360
   * Removed a debian patch, upstream file not more present
   * Added myself to Uploaders.
Checksums-Sha1:
 8f8e341148374b2b7f908357f5eab00fae4248b1 2391 pelican_4.0.1+dfsg-1.dsc
 eca937f1a038884d4677917acbff6fb17bb5c62d 479500 pelican_4.0.1+dfsg.orig.tar.xz
 07bbd60c3ce5371fc98eb93c11b3a78873f8e732 17268 
pelican_4.0.1+dfsg-1.debian.tar.xz
 56db416b92fc0997b063baea78ae2a2f1cddd182 185024 
pelican-doc_4.0.1+dfsg-1_all.deb
 be2734826018a7856298f5bd9d75e95c6687fb8e 94368 pelican_4.0.1+dfsg-1_all.deb
 03b27831db13f8be109fa8431ead4e833b25a155 7590 
pelican_4.0.1+dfsg-1_amd64.buildinfo
 3b33a4996711d12dffc930823484e7fa4d51e7bc 20416 
python-pelican_4.0.1+dfsg-1_all.deb
Checksums-Sha256:
 d98f9f23d34b93246acadd52f6ca11ef1cc694fc5d3949b31a1d84e9e1a67c8c 2391 
pelican_4.0.1+dfsg-1.dsc
 8570e63e4b2e49ee7496d823ee0c5f17165ed20fa43c88f878f5beb66bfcbacb 479500 
pelican_4.0.1+dfsg.orig.tar.xz
 6e9c3de3f3cd778082d0b2ec37ada689e9612a59c417d97af5b6b18945dbfab2 17268 
pelican_4.0.1+dfsg-1.debian.tar.xz
 b55774944b647e27b82a34638544e50d1d0cd2e201cb88c0bd741edd6fac44c1 185024 
pelican-doc_4.0.1+dfsg-1_all.deb
 c2b975846f4d52139a841fabfc6463b107bf5bdc5b9355a4920bec512f71fc3c 94368 
pelican_4.0.1+dfsg-1_all.deb
 5550094a55c337ca0f6eb32105fc7dc7044019dbcb363cda670adda26c621d9a 7590 
pelican_4.0.1+dfsg-1_amd64.buildinfo
 b1da8eb7e027e4e973defdf4b6945433d5976f4f92616d0ea513789ab11440f9 20416 
python-pelican_4.0.1+dfsg-1_all.deb
Files:
 00d54211773bed94388b2492ab5025cd 2391 web optional pelican_4.0.1+dfsg-1.dsc
 03e6c42b3e1c52ed284eab6f116251f1 479500 web optional 
pelican_4.0.1+dfsg.orig.tar.xz
 1c7ad5dd5a972ea2756719fdbd0a0373 17268 web optional 
pelican_4.0.1+dfsg-1.debian.tar.xz
 0d8999e86c795d25e3c7a5b403c681eb 185024 doc optional 
pelican-doc_4.0.1+dfsg-1_all.deb
 4b49ef1fc04d15eef730db081a95072f 94368 web optional 
pelican_4.0.1+dfsg-1_all.deb
 00f27db469976b6768701f39b226380c 7590 web optional 
pelican_4.0.1+dfsg-1_amd64.buildinfo
 600567af2185012a40cf98973da72a6e 20416 oldlibs optional 
python-pelican_4.0.1+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEin8gjG2ecykWV0FNITXRI9jBm+wFAlw7fSEACgkQITXRI9jB
m+zNWA/8DKsLrVovdPM4XF3LwbojyEXV+jRRg/fdsiqsIvzw77irArj8AN9Pt/sE
QpPG88p73kKE7FLxw55K3p4T4tklTn7kJuFFqkNd6d3zyXwFL9ryWGIXD14dicpU

Bug#919205: ruby-html2haml: missing build dependency on ruby-temple

[Adrian Bunk]

Source: ruby-html2haml
Version: 2.2.0-1
Severity: serious
Tags: ftbfs buster sid

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

...
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:310:in `to_specs': Could not find 
'temple' (>= 0.8.0) among 37 total gem(s) (Gem::MissingSpecError)
...

Bug#919193: [Debian-med-packaging] Bug#919193: orthanc: FTBFS with dcmtk-3.6.4

[Sébastien Jodogne]

Hello,

Thanks for the report! This is now fixed in the upstream mainline by
the two following changesets:
https://bitbucket.org/sjodogne/orthanc/commits/c8b75e207a82179a3f99a8bc
60b43626f8f3c34b
https://bitbucket.org/sjodogne/orthanc/commits/8849677c2cbcf0b5ac990e83
8c72ace6453b059b

Orthanc 1.5.2 will soon be released, and the fix will be included in
the updated Debian package. Will close this issue by that time.

Regards,
Sébastien-


On dim, 2019-01-13 at 16:40 +0100, Gert Wollny wrote:
> Source: orthanc
> Version: 1.5.1+dfgs-1
> Severity: serious
> Justification: 4 FTBFS but build before
> 
> Dear Maintainer,
> 
> The package FTBFS with dcmtk-3.6.4. The main issues: 
> 
> - unlock() now needs to be replaced by rdunlock() or wrunlock() 
>   depending on which *lock() method was called
> 
> - Various functions that take strings now also take a size parameter
> for each string
> 
> - DIMSE_findUser now takes an additional parameter 
> 
> Best, 
> Gert

Bug#919203: wrong term in License:-block

[Thorsten Alteholz]

Package: puppet-module-antonlindstrom-powerdns
Version: 0.0.5-2
Severity: serious
thanks

Hi Thomas,

please also remove the term "or (at your option) any later version" from 
your GPL-2 license block in debian/copyright.


Thanks!
  Thorsten

Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

[Adrian Bunk]

On Sun, Jan 13, 2019 at 05:22:18PM +0100, Raphael Hertzog wrote:
> Hi,
> 
> On Sat, 12 Jan 2019, Adrian Bunk wrote:
> > pyside2 is now built without patchelf on mips64el.
> > 
> > Doing the same for mips and mipsel should fix the problem for pivy.
> 
> Yeah, but this is not going in the right direction. This means that
> pyside will be built with the embedded patchelf. The embedded patchelf is
> outdated. But it will build and do its work...
> 
> Really, if the test suite failure can't be fixed quickly, it would be
> better to ignore the failure on the broken architectures and let the
> package build anyway. It's unlikely that the tool is entirely broken...

Test cases that passed in patchelf 0.8 fail since 0.9,
and segmentation fault on things like setting rpath
might be close enough to "entirely broken".

> and it's just a pity to ask pyside to deal with a varying set of
> architectures for patchelf.

No disagreement on that, but unfortunately it seems to be the best
available short-term fix.

> Cheers,

cu
Adrian

-- 

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

Bug#919071: Bug #919071 in libdbd-mariadb-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #919071 in libdbd-mariadb-perl 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/perl-team/modules/packages/libdbd-mariadb-perl/commit/7ac88e754d70b56755a81745df10dc7923969302


Add patch to temporarily make a test failure non-fatal

which is caused by a change in MariaDB 10.3.12's output.

This patch can be removed once the test is fixed upstream.

Closes: #919071


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919071

Bug#919196: gloox: FTBFS (autobuilder hangs)

[Santiago Vila]

Package: src:gloox
Version: 1.0.20-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


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

[... snipped ...]

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


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

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

The hang also happens here:

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

so it seems to be a general problem.

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

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Processed: Bug #919071 in libdbd-mariadb-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919071 {Done: gregor herrmann } 
[src:libdbd-mariadb-perl] FTBFS: t/55utf8.t fails with MariaDB 10.3.12
Added tag(s) pending.

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

Bug#873576: ruby-rest-client: diff for NMU version 2.0.2-3.1

[Paul Gevers]

tags 873576 + patch
tags 873576 + pending
user debian-rele...@lists.debian.org
usertags 873576 bsp-2019-01-nl-venlo
thanks

Dear maintainer,

I've prepared an NMU for ruby-rest-client (versioned as 2.0.2-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I should delay
it longer.

Regards.

Paul
Sent from the BSP in Venlo
diff -Nru ruby-rest-client-2.0.2/debian/changelog 
ruby-rest-client-2.0.2/debian/changelog
--- ruby-rest-client-2.0.2/debian/changelog 2017-10-31 11:21:55.0 
+0100
+++ ruby-rest-client-2.0.2/debian/changelog 2019-01-13 18:31:39.0 
+0100
@@ -1,3 +1,10 @@
+ruby-rest-client (2.0.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable more network-dependent tests (Closes: #873576)
+
+ -- Paul Gevers   Sun, 13 Jan 2019 18:31:39 +0100
+
 ruby-rest-client (2.0.2-3) unstable; urgency=medium
 
   * Add patches from Steve Langasek  to fix
diff -Nru ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch 
ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch
--- ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch   
2017-10-31 11:21:55.0 +0100
+++ ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch   
2019-01-13 18:31:39.0 +0100
@@ -1,13 +1,16 @@
 From: Matthias Klose 
 From: Steve Langasek 
-Last-Update: 2017-08-29
+From: Paul Gevers 
+Last-Update: 2019-01-13
 Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818459
 Bug-Debian: https://bugs.debian.org/873576
 Forwarded: no
 
 a/spec/integration/request_spec.rb
-+++ b/spec/integration/request_spec.rb
-@@ -10,96 +10,7 @@ describe RestClient::Request do
+Index: ruby-rest-client/spec/integration/request_spec.rb
+===
+--- ruby-rest-client.orig/spec/integration/request_spec.rb
 ruby-rest-client/spec/integration/request_spec.rb
+@@ -10,118 +10,11 @@ describe RestClient::Request do
end
  
describe "ssl verification" do
@@ -105,10 +108,16 @@
end
  
describe "timeouts" do
-@@ -113,15 +24,6 @@ describe RestClient::Request do
- raise_error(RestClient::Exceptions::OpenTimeout))
- end
- 
+-it "raises OpenTimeout when it hits an open timeout" do
+-  request = RestClient::Request.new(
+-:method => :get,
+-:url => 'http://www.mozilla.org',
+-:open_timeout => 1e-10,
+-  )
+-  expect { request.execute }.to(
+-raise_error(RestClient::Exceptions::OpenTimeout))
+-end
+-
 -it "raises ReadTimeout when it hits a read timeout via :read_timeout" do
 -  request = RestClient::Request.new(
 -:method => :get,
@@ -118,11 +127,14 @@
 -  expect { request.execute }.to(
 -raise_error(RestClient::Exceptions::ReadTimeout))
 -end
++# all removed; accessing the network
end
  
  end
 a/spec/integration/httpbin_spec.rb
-+++ b/spec/integration/httpbin_spec.rb
+Index: ruby-rest-client/spec/integration/httpbin_spec.rb
+===
+--- ruby-rest-client.orig/spec/integration/httpbin_spec.rb
 ruby-rest-client/spec/integration/httpbin_spec.rb
 @@ -40,48 +40,6 @@ describe RestClient::Request do
end
  


signature.asc
Description: OpenPGP digital signature

Processed: ruby-rest-client: diff for NMU version 2.0.2-3.1

[Debian Bug Tracking System]

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

> tags 873576 + patch
Bug #873576 [src:ruby-rest-client] ruby-rest-client: FTBFS without network 
access
Added tag(s) patch.
> tags 873576 + pending
Bug #873576 [src:ruby-rest-client] ruby-rest-client: FTBFS without network 
access
Added tag(s) pending.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was elb...@debian.org).
> usertags 873576 bsp-2019-01-nl-venlo
There were no usertags set.
Usertags are now: bsp-2019-01-nl-venlo.
> thanks
Stopping processing here.

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

Bug#919071: marked as done (FTBFS: t/55utf8.t fails with MariaDB 10.3.12)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 17:34:24 +
with message-id 
and subject line Bug#919071: fixed in libdbd-mariadb-perl 1.11-2
has caused the Debian Bug report #919071,
regarding FTBFS: t/55utf8.t fails with MariaDB 10.3.12
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As noticed by Otto in #917303, the MariaDB update from 10.3.11 to
10.3.12 causes a test failure in libdbd-mariadb-perl:

#   Failed test 'warning is correct'
#   at t/55utf8.t line 83.
#   'Incorrect string value: '\xC4\x80dam' for column 
`testdb`.`dbd_mysql_t55utf8`.`ascii` at row 1'
# doesn't match '(?^:^(?:Incorrect string value: '\\xC4\\x80dam'|Data 
truncated) for column 'ascii' at row 1$)'
#   Failed test 'warning is correct'
#   at t/55utf8.t line 83.
#   'Incorrect string value: '\xC4\x80dam' for column 
`testdb`.`dbd_mysql_t55utf8`.`ascii` at row 1'
# doesn't match '(?^:^(?:Incorrect string value: '\\xC4\\x80dam'|Data 
truncated) for column 'ascii' at row 1$)'
# Looks like you failed 2 tests of 84.
t/55utf8.t ..
1..84
ok 1
ok 2
ok 3 - testing quoting of utf 8 string
ok 4 - testing quoting of blob
ok 5 - SET SQL_MODE=''
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15 - got warning for INSERT
not ok 16 - warning is correct
ok 17
ok 18 - got data
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24
ok 25
ok 26 - compare Ä<80>dam eq Ä<80>dam
ok 27
ok 28 - SET character_set_results='latin1'
ok 29 - got data
ok 30 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 31 - blob is unchanged when @@character_set_results is latin1
ok 32 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 33 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 34 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 35 - latin1 data are returned as latin1 when @@character_set_results is 
latin1
ok 36 - latin1 data are returned as latin1 when @@character_set_results is 
latin1
ok 37
ok 38
ok 39 -
ok 40 - SET character_set_results='utf8mb4'
ok 41
ok 42
ok 43
ok 44
ok 45 - testing quoting of utf 8 string
ok 46 - testing quoting of blob
ok 47 - SET SQL_MODE=''
ok 48
ok 49
ok 50
ok 51
ok 52
ok 53
ok 54
ok 55
ok 56
ok 57 - got warning for INSERT
not ok 58 - warning is correct
ok 59
ok 60 - got data
ok 61
ok 62
ok 63
ok 64
ok 65
ok 66
ok 67
ok 68 - compare Ä<80>dam eq Ä<80>dam
ok 69
ok 70 - SET character_set_results='latin1'
ok 71 - got data
ok 72 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 73 - blob is unchanged when @@character_set_results is latin1
ok 74 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 75 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 76 - utf8 data are returned as latin1 when @@character_set_results is latin1
ok 77 - latin1 data are returned as latin1 when @@character_set_results is 
latin1
ok 78 - latin1 data are returned as latin1 when @@character_set_results is 
latin1
ok 79
ok 80
ok 81 -
ok 82 - SET character_set_results='utf8mb4'
ok 83
ok 84
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/84 subtests
[…]
Test Summary Report
- ---
t/55utf8.t(Wstat: 512 Tests: 84 Failed: 2)
  Failed tests:  16, 58
  Non-zero exit status: 2
Files=89, Tests=3262, 39 wallclock secs ( 0.64 usr  0.13 sys +  8.42 cusr  1.11 
csys = 10.30 CPU)
Result: FAIL
Failed 1/89 test programs. 2/3262 subtests failed.



-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlw56IJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZ8BxAAjTMWleXBRtmNVdeTo4L3qbr86thuRKMT0wauDoUY1fMPYgRSfziwLN7b
+7+8/MCb9ESOTGkacZulH3bPmRELV/LkDJN3XbAL1KcrQT0eMb2s4q2VXLybgoE8
q8pupqfwaEI2G7DGCOBralbMYtZ3UWyy2bJsQIBY+JcZk95yl1ulHoI+n1m//ETs
UpKlHrQPB01wGqDm+K95Cpxv5Zvym3a9n1Bzw2WCNIFf9NX85R+lKlKn7my+J9+j
Bllr80/BCcCUmjG/fIMxI2SiEmOgeTJwoLpQ14cpN1BlS3nWW+AXCHDX+G1MHGDS
9Lc4sh0b58MyBBfLnPvW+SUHhDX3R1ZZmKh3JLPH2tSKTeWDsEBBNih7D1hkB2hV
xiqqlQ0Y2SpUSVhvRUsKJ7Hdoqx4ko5X/9xG/kXC2ke6EYnKJzJ5JKwvogZ3AnDz

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

[Different55]

Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After 
the upgrade finished, NetworkManager popped up saying that the connection to my 
home Wifi failed. I was able to connect to my phone's hotspot still. I attached 
a relevant bit of a log from journalctl.

I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," that 
had the same issue. I didn't have this issue after downgrading to 2.6. 
According to lshw, my wireless adapter is an Intel Wireless 3165.

Let me know if there's anything else I can do to help!

Thanks,
Diff

PS. Re-sending this as plaintext because it returned to sender initially, 
apologies if it gets sent twice anywhere because of that.
Jan 12 20:15:43 Empanada NetworkManager[548]:   [1547345743.8558] device (wls8): supplicant interface state: disconnected -> scanning
Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
Jan 12 20:15:44 Empanada kernel: wls8: authenticate with xx:xx:xx:xx:xx:xx
Jan 12 20:15:44 Empanada kernel: wls8: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
Jan 12 20:15:44 Empanada NetworkManager[548]:   [1547345744.7171] device (wls8): supplicant interface state: scanning -> authenticating
Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
Jan 12 20:15:44 Empanada kernel: wls8: authenticated
Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 1/3)
Jan 12 20:15:44 Empanada NetworkManager[548]:   [1547345744.7263] device (wls8): supplicant interface state: authenticating -> associating
Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9)
Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms)
Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 2/3)
Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9)
Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms)
Jan 12 20:15:45 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 3/3)
Jan 12 20:15:45 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9)
Jan 12 20:15:45 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms)
Jan 12 20:15:45 Empanada kernel: wls8: association with xx:xx:xx:xx:xx:xx timed out
Jan 12 20:15:45 Empanada NetworkManager[548]:   [1547345745.3751] device (wls8): supplicant interface state: associating -> disconnected
Jan 12 20:15:46 Empanada NetworkManager[548]:   [1547345746.3754] device (wls8): supplicant interface state: disconnected -> scanning
Jan 12 20:15:46 Empanada NetworkManager[548]:   [1547345746.6710] dhcp4 (wls8): request timed out
Jan 12 20:15:46 Empanada NetworkManager[548]:   [1547345746.6711] dhcp4 (wls8): state changed unknown -> timeout
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0861] dhcp4 (wls8): canceled DHCP transaction, DHCP client pid 30637
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0862] dhcp4 (wls8): state changed timeout -> done
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0870] device (wls8): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0889] manager: NetworkManager state is now DISCONNECTED
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0911] device (wls8): Activation: failed for connection 'Depeche Modem'
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0914] device (wls8): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 12 20:15:47 Empanada avahi-daemon[552]: Withdrawing address record for fe80::86ef:18ff:fe19:6f68 on wls8.
Jan 12 20:15:47 Empanada avahi-daemon[552]: Leaving mDNS multicast group on interface wls8.IPv6 with address fe80::86ef:18ff:fe19:6f68.
Jan 12 20:15:47 Empanada avahi-daemon[552]: Interface wls8.IPv6 no longer relevant for mDNS.
Jan 12 20:15:47 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0949] device (wls8): set-hw-addr: set MAC address to 12:98:12:6B:66:5C (scanning)
Jan 12 20:15:47 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready

Bug#919198: manpages-de: missing Breaks+Replaces: login (<< 1:4.5-1.1)

[Andreas Beckmann]

Package: manpages-de
Version: 2.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../manpages-de_2.10-1_all.deb ...
  Unpacking manpages-de (2.10-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-de_2.10-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/de/man1/su.1.gz', which is also in 
package login 1:4.4-4.1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-de_2.10-1_all.deb


cheers,

Andreas


login=1:4.4-4.1_manpages-de=2.10-1.log.gz
Description: application/gzip

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

[Different55]

Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After 
the upgrade finished, NetworkManager popped up saying that the connection to my 
home Wifi failed. I was able to connect to my phone's hotspot still. I attached 
a relevant bit of a log from journalctl.

I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," that 
had the same issue. I didn't have this issue after downgrading to 2.6. 
According to lshw, my wireless adapter is an Intel Wireless 3165.

Let me know if there's anything else I can do to help!

Thanks,
Diff

Processed: Bug #919103 in libreoffice marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919103 [libreoffice-kde5] libreoffice-kde5: failure to upgrade from 
stretch: soffice.odg also in libreoffice-kde
Ignoring request to alter tags of bug #919103 to the same tags previously set

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

Bug#919138: wpasupplicant 2.7 fails to connect to some Wifi networks

[Different55]

Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After 
the upgrade finished, NetworkManager popped up saying that the connection to my 
home Wifi failed. I was able to connect to my phone's hotspot still. I attached 
a relevant bit of a log from journalctl.

I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," that 
had the same issue. I didn't have this issue after downgrading to 2.6. 
According to lshw, my wireless adapter is an Intel Wireless 3165.

Let me know if there's anything else I can do to help!

Thanks,
DiffJan 12 20:15:43 Empanada NetworkManager[548]:   [1547345743.8558] device (wls8): supplicant interface state: disconnected -> scanning
Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
Jan 12 20:15:44 Empanada kernel: wls8: authenticate with xx:xx:xx:xx:xx:xx
Jan 12 20:15:44 Empanada kernel: wls8: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
Jan 12 20:15:44 Empanada NetworkManager[548]:   [1547345744.7171] device (wls8): supplicant interface state: scanning -> authenticating
Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
Jan 12 20:15:44 Empanada kernel: wls8: authenticated
Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 1/3)
Jan 12 20:15:44 Empanada NetworkManager[548]:   [1547345744.7263] device (wls8): supplicant interface state: authenticating -> associating
Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9)
Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms)
Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 2/3)
Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9)
Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms)
Jan 12 20:15:45 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 3/3)
Jan 12 20:15:45 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9)
Jan 12 20:15:45 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms)
Jan 12 20:15:45 Empanada kernel: wls8: association with xx:xx:xx:xx:xx:xx timed out
Jan 12 20:15:45 Empanada NetworkManager[548]:   [1547345745.3751] device (wls8): supplicant interface state: associating -> disconnected
Jan 12 20:15:46 Empanada NetworkManager[548]:   [1547345746.3754] device (wls8): supplicant interface state: disconnected -> scanning
Jan 12 20:15:46 Empanada NetworkManager[548]:   [1547345746.6710] dhcp4 (wls8): request timed out
Jan 12 20:15:46 Empanada NetworkManager[548]:   [1547345746.6711] dhcp4 (wls8): state changed unknown -> timeout
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0861] dhcp4 (wls8): canceled DHCP transaction, DHCP client pid 30637
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0862] dhcp4 (wls8): state changed timeout -> done
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0870] device (wls8): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0889] manager: NetworkManager state is now DISCONNECTED
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0911] device (wls8): Activation: failed for connection 'Depeche Modem'
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0914] device (wls8): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 12 20:15:47 Empanada avahi-daemon[552]: Withdrawing address record for fe80::86ef:18ff:fe19:6f68 on wls8.
Jan 12 20:15:47 Empanada avahi-daemon[552]: Leaving mDNS multicast group on interface wls8.IPv6 with address fe80::86ef:18ff:fe19:6f68.
Jan 12 20:15:47 Empanada avahi-daemon[552]: Interface wls8.IPv6 no longer relevant for mDNS.
Jan 12 20:15:47 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready
Jan 12 20:15:47 Empanada NetworkManager[548]:   [1547345747.0949] device (wls8): set-hw-addr: set MAC address to 12:98:12:6B:66:5C (scanning)
Jan 12 20:15:47 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready

Bug#919103: Bug #919103 in libreoffice marked as pending

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #919103 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/commit/462630fbb685595d134ada5dde5e3b5c7f85d6e7


debian/control.kde*.in: Replaces: libreoffice-kde (<< 1:6.1.0~alpha1-1) 
(closes: #919103)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919103

Bug#919090: marked as done (Please remove (build-)dependency on mongodb for buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 17:19:41 +
with message-id 
and subject line Bug#919090: fixed in libmongodb-perl 2.0.2-2
has caused the Debian Bug report #919090,
regarding Please remove (build-)dependency on mongodb for buster
to be marked as done.

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

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


-- 
919090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongodb
Version: 1:3.4.15-1
Severity: serious
Justification: Cannot be properly supported

MongoDB should not be part of (at least) Buster for the following 
reasons:

 - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it 
   to be included in Buster.

 - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch 
   to SSPLv1 complicates matters. As discussed in #915537, we will not 
   be distributing any SSPL-licensed software, and keeping the last 
   AGPL-licensed version (3.6.8 or 4.0.3) without the ability to 
   cherry-pick upstream fixes is not a viable option. (I am currently 
   not considering distributing mongodb in non-free.)

I will not request removal immediately, to allow other packages time to 
adjust their dependencies, but eventually auto-removal will kick in.  

That said, MongoDB 3.4 will probably remain in sid for as long as it is 
AGPL-licensed and supported upstream.

Apollon

[1] https://www.mongodb.com/support-policy
--- End Message ---
--- Begin Message ---
Source: libmongodb-perl
Source-Version: 2.0.2-2

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libmongodb-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: Sun, 13 Jan 2019 18:02:34 CET
Source: libmongodb-perl
Binary: libmongodb-perl
Architecture: source
Version: 2.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
 libmongodb-perl - Mongo Driver for Perl
Closes: 919090
Changes:
 libmongodb-perl (2.0.2-2) unstable; urgency=medium
 .
   * Disable build dependency on mongodb-server which won't be in buster.
 (Closes: #919090)
   * Drop unneeded version constraints from (build) dependencies.
   * Update (build) dependencies on dual-lifed modules.
   * Bump debhelper compatibility level to 11.
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.3.0.
Checksums-Sha256: 
 26ad1d84685c4e36fe489eccdfb1844f70ec0dbc0446eac4a2d0f8821d15d410 2821 
libmongodb-perl_2.0.2-2.dsc
 43e0d77890b5b4778cd63e17b8a707c03adb0eadb2a8f2a76a1dac697dd1d26a 6724 
libmongodb-perl_2.0.2-2.debian.tar.xz
 b218dffddf69dee069485cd662070340d50099ce465ba7a402a7933deabd6d26 7229 
libmongodb-perl_2.0.2-2_sourceonly.buildinfo
Checksums-Sha1: 
 f14b51d6aa92df3011827365ba547382f95cb644 2821 libmongodb-perl_2.0.2-2.dsc
 863432398723466053db5cee287b6f17623fc64f 6724 
libmongodb-perl_2.0.2-2.debian.tar.xz
 0f05f1082a5a16744f7a6b5e1ac562712eca6b81 7229 
libmongodb-perl_2.0.2-2_sourceonly.buildinfo
Files: 
 e7c95a2da4ac625ac930691c69f26e29 2821 perl optional libmongodb-perl_2.0.2-2.dsc
 0da0ce8d5cfd32c8581c2b949d7bf41d 6724 perl optional 
libmongodb-perl_2.0.2-2.debian.tar.xz
 beaa29f5de1ca13c7e8812ebcd8de76f 7229 - - 
libmongodb-perl_2.0.2-2_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlw7bzBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgb9GA/+I//OgIZrU0lWCSHF/c8mIs8yYYyqcJGnRRc+bj+kyb6lRiCEyVbOqgcV
T38th5nZpfJPYL+3Cpp032GoYX/NMkrvz6kydhZPLNBuMWE8Qdwehc/fPMiS3xBB
7R+H1Up9d6hrwyt0S4PSDIfTBTzPxRjaUrET/UZ0dAdjo1FnbRNB4RlSiztm9RlM
OUNd5PXCpW/5Rzv7MYL9fmefq3p5jfWiKcN/+JC4V3lWF2Hg354P15XuN4sN4GsJ
8JRS/UL9zy3XzUSdqdKFB7dQ1Zjtc99Umc5aKRbiAWQTJstFLkNvlaKe9W/475L5
C4CjbZFadVJxNNDinOMVZXBP1dvLdBySt1IlskyOFEyyU5gHqfuK/AMh/3os/IDr
3im++sHa6o70xsXZehh30rwWnQcoKEWDETU1+xZ3SL6IfWgM3TkISCC1gkv8J6pV

Bug#918281: marked as done (openscenegraph-3.4 build depends on cruft package libcoin80-dev)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 16:37:23 +
with message-id 
and subject line Bug#918281: fixed in openscenegraph-3.4 3.4.1+dfsg1-5
has caused the Debian Bug report #918281,
regarding openscenegraph-3.4 build depends on cruft package libcoin80-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.)


-- 
918281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openscenegraph-3.4
Version: 3.4.1+dfsg1-4
Severity: serious
Tags: ftbfs

openscenegraph-3.4 build depends on libcoin80-dev
that is no longer built by src:coin3.
--- End Message ---
--- Begin Message ---
Source: openscenegraph-3.4
Source-Version: 3.4.1+dfsg1-5

We believe that the bug you reported is fixed in the latest version of
openscenegraph-3.4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alberto Luaces Fernández  (supplier of updated 
openscenegraph-3.4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Jan 2019 18:35:11 +0100
Source: openscenegraph-3.4
Binary: libopenscenegraph-3.4-dev libopenscenegraph-3.4-131 
openscenegraph-3.4-doc openscenegraph-3.4 openscenegraph-3.4-examples
Architecture: source
Version: 3.4.1+dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Alberto Luaces Fernández 
Changed-By: Alberto Luaces Fernández 
Description:
 libopenscenegraph-3.4-131 - 3D scene graph, shared libs
 libopenscenegraph-3.4-dev - 3D scene graph, development files
 openscenegraph-3.4 - 3D scene graph, utilities and examples (binaries)
 openscenegraph-3.4-doc - 3D scene graph, documentation
 openscenegraph-3.4-examples - 3D scene graph, examples (sources)
Closes: 912867 918281
Changes:
 openscenegraph-3.4 (3.4.1+dfsg1-5) unstable; urgency=medium
 .
   * Upgraded to latest coin library (Closes: #918281, #912867).
Checksums-Sha1:
 dbcd9f19abafd8a712de253b20c93e09ea858c8a 3009 
openscenegraph-3.4_3.4.1+dfsg1-5.dsc
 3c748019778874de311313743c8fedea4fe3fcf9 25140 
openscenegraph-3.4_3.4.1+dfsg1-5.debian.tar.xz
 0cb348a4fd19ea7fbdf4cb36254329be2a4d1e92 22092 
openscenegraph-3.4_3.4.1+dfsg1-5_amd64.buildinfo
Checksums-Sha256:
 92f7540007c920e55b43f159d7798179307d1c54cc37388899f9b804875908eb 3009 
openscenegraph-3.4_3.4.1+dfsg1-5.dsc
 41a81d7ff3860060c873d16d1c700b3c17137769709fabb8b1872bae3ddd3f90 25140 
openscenegraph-3.4_3.4.1+dfsg1-5.debian.tar.xz
 f1bcf334b160ff209bda88f8f5c1128c79737d4642d963e905632d525ca58c19 22092 
openscenegraph-3.4_3.4.1+dfsg1-5_amd64.buildinfo
Files:
 2dd508ef5e988843b87a3b4ae8d9d724 3009 devel optional 
openscenegraph-3.4_3.4.1+dfsg1-5.dsc
 fe62c8747414d160aab3ba96349c58dd 25140 devel optional 
openscenegraph-3.4_3.4.1+dfsg1-5.debian.tar.xz
 ede7798911bf2a9c0295ebb76536f63e 22092 devel optional 
openscenegraph-3.4_3.4.1+dfsg1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEESH/NBQiVEF9DwgYImy5rgnUtsDsFAlw7ZjAPHGFsdWFjZXNA
dWRjLmVzAAoJEJsua4J1LbA7Lw0P/iROVVz9NDQlJVlNqD326NZMsxOWov8TL7H/
5OVFynIMCTBC/dA+F1PFIevYN8zAQjHeNm1+mWM+dyD9jM/67glv93ETd3Ey0cmr
AE29s+LsYYkX0q5R3PHJKG26mT99urUSLZ4XmKz/gd5Zsld6+vqfG46gLurUeVMS
3ZlFOH0bGXUv6bXccytyXBOitS7/M2sIre8Zde74f2e1QKANKo/YcH7SkZNH2Gsj
oPiZ+B0RkbdY1jiQwc3A3uqsKI89th3tYckMICPIbRHZRdixwQsYzRn9WJinR+d2
kCD6mcnOV/MwR8zgtIjlKiCgu5sDKcUVtUtJHo5lhHI1gj6tECxTyaUyKj+VDgIK
d/buE3QZDzHZY72AhhpfZPvj81P2yGj5O4LtryLbydtxjk0DKD803epR8AeiS5fe
X6/M36Fqpe1KpySq7YoIVgEJJMdNN6fISkm/tdrTXYdTDELNEkCTWUN/CAjyXNLh
ZLdr67ond1KSu+7mljTJf35DiDQ90NzPnx+E0k1j2lrMmoqbPpROpG16fsi+mXAb
gY6FUt/NcNK6juTdlyKNsrMpUBLoqCR1KK2n52VK/3PpDF78hadAY6vibUSx/E4x
4NdmZn+XGake7fCviD5U0PZYCCaMIEVGVosXZpNGt72ZWc0N2KnUy78h9kx2etm5
H9I6k0Ah
=Be/A
-END PGP SIGNATURE End Message ---

Bug#916002: marked as done (xnbd FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 17:07:26 +
with message-id 
and subject line Bug#916002: fixed in xnbd 0.3.0-3
has caused the Debian Bug report #916002,
regarding xnbd FTBFS with glibc 2.28
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.)


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

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

...
io.c: In function 'get_disksize':
io.c:155:7: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
   if (major(st.st_rdev) == 259)
   ^
...
/bin/bash ./libtool  --tag=CC   --mode=link gcc  -g -O2 
-ffile-prefix-map=/build/1st/xnbd-0.3.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wformat=2 -Wcast-align -Wwrite-strings -Wfloat-equal -Wpointer-arith 
-Wswitch-enum -fstack-protector -fstack-check -lgthread-2.0 -pthread -lglib-2.0 
-Wl,-z,relro -o xnbd-cachestatdump xnbd_cachestatdump.o libxnbd_internal.la 
libtool: link: gcc -g -O2 -ffile-prefix-map=/build/1st/xnbd-0.3.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Wformat=2 -Wcast-align -Wwrite-strings 
-Wfloat-equal -Wpointer-arith -Wswitch-enum -fstack-protector -fstack-check 
-pthread -Wl,-z -Wl,relro -o .libs/xnbd-cachestatdump xnbd_cachestatdump.o  
-lgthread-2.0 -lglib-2.0 ./.libs/libxnbd_internal.so -pthread -Wl,-rpath 
-Wl,/usr/lib/xnbd
/usr/bin/ld: ./.libs/libxnbd_internal.so: undefined reference to `major'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:639: xnbd-cachestatdump] Error 1
--- End Message ---
--- Begin Message ---
Source: xnbd
Source-Version: 0.3.0-3

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated xnbd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Jan 2019 17:41:58 +0100
Source: xnbd
Binary: xnbd-server xnbd-client xnbd-common
Architecture: source
Version: 0.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 xnbd-client - Network Block Device client with support for live migration
 xnbd-common - Network Block Device - common files
 xnbd-server - Network Block Device server with support for live migration
Closes: 916002
Changes:
 xnbd (0.3.0-3) unstable; urgency=medium
 .
   * QA upload.
   * Moved GIT repository to salsa.debian.org.
   * Fix build with glibc 2.28, thanks to Logan Rosen.  (Closes: #916002)
   * Fix d/copyright.
   * Use dpkg makefile snippets instead of manual changelog parsing.
Checksums-Sha1:
 01e00d4fed5ecdc8ed47d13b6a08ee6bbd47318b 2054 xnbd_0.3.0-3.dsc
 f7a2153d00270d507332213cacceba5666ee2cec 6428 xnbd_0.3.0-3.debian.tar.xz
 ddf46b56f44799f4cf4d1eb3982d7d5af7856625 7184 xnbd_0.3.0-3_source.buildinfo
Checksums-Sha256:
 29213df72d87b22bba257f888bae9b2726c2d56ceb7e3415e8c7fcc3e1de1806 2054 
xnbd_0.3.0-3.dsc
 b5eb4c8f6b674cb26f0fcb4ff4e65370440305848146fe8cfc1181d0791be49d 6428 
xnbd_0.3.0-3.debian.tar.xz
 5d0a97ddf8dcfcdf18f8ec83b75ae8ff9425fed37d6a2c440ef54d86f5477232 7184 
xnbd_0.3.0-3_source.buildinfo
Files:
 bdedbaff646a0889adf09920734b8eb0 2054 admin extra xnbd_0.3.0-3.dsc
 1bd7a9703f1848f2a76eca08b8b92cbf 6428 admin extra xnbd_0.3.0-3.debian.tar.xz
 d5d7ec9f892c00e21b68e4ea98a79f3d 7184 admin extra xnbd_0.3.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlw7a2QQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCE0CD/0SXA1YVpAPwe+s8OdU8PwaGgyCg+cly5CT
lGw1VQvQTyxAWQDBJ/84l2J0/AzTG/2lkEPEwz3dAwQX++Jyh2HcWsCoLXJCmN0U
rML/ZetxeBS1idTDnsPXOgSwwDoF+LVkhcj1RO2vWRGR+aHc+CDCQ4uq6iZNj6pF
ticvLmySPpInWZNbDkMYY6WZB8IhUKNjpMF3tstThMpyNGUJtSk0rnjxZtg0NcfG
0lLnvjXboe7YnuE7sY8GSVCszQQaL4Rxt5hrjVBZAqC9NwyoJGqzYbbOPAf+/9SS

Bug#919189: marked as done (probabel FTBFS on arm64, likely due to Eigen 3 NEON code)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 16:53:52 +
with message-id 
and subject line Bug#919189: fixed in probabel 0.5.0+dfsg-2
has caused the Debian Bug report #919189,
regarding probabel FTBFS on arm64, likely due to Eigen 3 NEON code
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.)


-- 
919189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: probabel
Version: 0.5.0+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=probabel=arm64=0.5.0%2Bdfsg-1=1538603399=0

...
FAIL: test_bt
=

Analysing BT...
BT check: dose vs. dose_fv OK
BT check (add model): prob vs. prob_fv OK
BT check (domin model): prob vs. prob_fv   OK
BT check (over_domin model): prob vs. prob_fv  OK
BT check (recess model): prob vs. prob_fv  OK
2c2
< rs7247199 GAC A 0.5847 0.415 0.9299 0.8666 200 0.333517 19 204938 544.518 
437.583 -567.387 435.04 1.75239
---
> rs7247199 GAC A 0.5847 0.415 0.9299 0.8666 200 0.333517 19 204938 544.518 
> 437.583 -567.388 435.04 1.75239
BT check (2df model): prob vs. prob_fv FAILED
FAIL test_bt.sh (exit status: 1)


Testsuite summary for ProbABEL 0.5.0

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

See checks/test-suite.log
Please report to genabel-de...@r-forge.wu-wien.ac.at

make[4]: *** [Makefile:713: test-suite.log] Error 1


I suspect this might be a problem with the NEON code in Eigen 3,
and the fact that this can be fixed with the following workaround
makes that even more probable:

--- debian/rules.old2019-01-09 15:07:11.950823327 +
+++ debian/rules2019-01-09 15:17:23.280539016 +
@@ -6,6 +6,10 @@
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
+ifeq ($(DEB_HOST_ARCH),arm64)
+  export DEB_CXXFLAGS_MAINT_APPEND = -march=armv8-a+nosimd
+endif
+
 include /usr/share/dpkg/default.mk
 
 # Location of the example files, will be converted to the
--- End Message ---
--- Begin Message ---
Source: probabel
Source-Version: 0.5.0+dfsg-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Jan 2019 17:10:41 +0100
Source: probabel
Binary: probabel probabel-examples
Architecture: source
Version: 0.5.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 probabel   - Toolset for Genome-Wide Association Analysis
 probabel-examples - Example files for ProbABEL
Closes: 919189
Changes:
 probabel (0.5.0+dfsg-2) unstable; urgency=medium
 .
   * Work around a problem with the NEON code in Eigen 3 for arm64 architecture
 (Thanks for the patch to Adrian Bunk )
 CLoses: #919189
   * debhelper 12
   * Standards-Version: 4.3.0
   * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target
Checksums-Sha1:
 b6304a1c09712b0524c5979137679d06f24295b2 2175 probabel_0.5.0+dfsg-2.dsc
 134f6882d84a7f6334f324b952fa9f3ab7d07804 4992 
probabel_0.5.0+dfsg-2.debian.tar.xz
 51e9c6d6d6230f2fe1a4f61dc273db374661267e 9097 
probabel_0.5.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 c7920924254ca7d744292f7d2a1da02e1715a92de223e5ed738c535f1d0955eb 2175 
probabel_0.5.0+dfsg-2.dsc
 8023d74f8505eadf753294f171994f7169b775e4cf7fcf29c58cc185dafeebe3 4992 
probabel_0.5.0+dfsg-2.debian.tar.xz
 5a69c83b6b2192618065e30b25fe39f67891467bd5b86ba67f7669fb60c2d160 9097 

Bug#919090: Bug #919090 in libmongodb-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #919090 in libmongodb-perl 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/perl-team/modules/packages/libmongodb-perl/commit/125941a30ca5fb5524020c83998094129d58dfe1


Disable build dependency on mongodb-server which won't be in buster.

Closes: #919090


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919090

Processed: Bug #919090 in libmongodb-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919090 [libmongodb-perl] Please remove (build-)dependency on mongodb for 
buster
Added tag(s) pending.

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

Bug#892784: marked as done (zaqar FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 16:55:20 +
with message-id 
and subject line Bug#892784: fixed in zaqar 7.0.0-1
has caused the Debian Bug report #892784,
regarding zaqar FTBFS: 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.)


-- 
892784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zaqar
Version: 6.0.0-1
Severity: serious

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

...
==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_2___
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_2___
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_4__fail_
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_4__fail_
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_get_claim_nonexistent_queue
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_get_claim_nonexistent_queue
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_3__
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_3__
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_messages.MessagesBaseTest.test_post_invalid_ttl

Bug#919094: marked as done (Please remove (build-)dependency on mongodb for buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 16:55:20 +
with message-id 
and subject line Bug#919094: fixed in zaqar 7.0.0-1
has caused the Debian Bug report #919094,
regarding Please remove (build-)dependency on mongodb for buster
to be marked as done.

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

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


-- 
919094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongodb
Version: 1:3.4.15-1
Severity: serious
Justification: Cannot be properly supported

MongoDB should not be part of (at least) Buster for the following 
reasons:

 - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it 
   to be included in Buster.

 - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch 
   to SSPLv1 complicates matters. As discussed in #915537, we will not 
   be distributing any SSPL-licensed software, and keeping the last 
   AGPL-licensed version (3.6.8 or 4.0.3) without the ability to 
   cherry-pick upstream fixes is not a viable option. (I am currently 
   not considering distributing mongodb in non-free.)

I will not request removal immediately, to allow other packages time to 
adjust their dependencies, but eventually auto-removal will kick in.  

That said, MongoDB 3.4 will probably remain in sid for as long as it is 
AGPL-licensed and supported upstream.

Apollon

[1] https://www.mongodb.com/support-policy
--- End Message ---
--- Begin Message ---
Source: zaqar
Source-Version: 7.0.0-1

We believe that the bug you reported is fixed in the latest version of
zaqar, 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.
Thomas Goirand  (supplier of updated zaqar 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, 30 Aug 2018 09:25:29 +0200
Source: zaqar
Binary: python3-zaqar zaqar-common zaqar-server
Architecture: source all
Version: 7.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python3-zaqar - OpenStack Queueing as a Service - Python libraries
 zaqar-common - OpenStack Queueing as a Service - common files
 zaqar-server - OpenStack Queueing as a Service - API server
Closes: 892784 919094
Changes:
 zaqar (7.0.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Uploading to unstable:
 - Fixes FTBFS (Closes: #892784).
   * Wait 10 seconds instead of parsing mongodb output.
   * Add Rules-Requires-Root: binary-targets.
   * Remove build-depends on mongodb, and do not test with it (Closes: #919094).
Checksums-Sha1:
 8dd038317738a4b939d740e7f48f80d4aa2b6cb9 3536 zaqar_7.0.0-1.dsc
 59eaac9cd511a7ac24b8923bd7aca20d6499872a 358692 zaqar_7.0.0.orig.tar.xz
 23b33a681387ef0aed93dc875971374884f24bd8 7584 zaqar_7.0.0-1.debian.tar.xz
 a3b42e9e7cf4b1df4e340b8b82e7890d0a040838 203068 python3-zaqar_7.0.0-1_all.deb
 4bb16bb6c10e1c4bbb68c4c2d022d8ffc23d86c4 34360 zaqar-common_7.0.0-1_all.deb
 f403808b6ef005dce0e8caf87494ef3dab503806 21596 zaqar-server_7.0.0-1_all.deb
 859107e81875aeadc66e259a7b0d4a7a29c39629 15656 zaqar_7.0.0-1_amd64.buildinfo
Checksums-Sha256:
 eaa8638fc7c18856a16cc0fe57067db15b87de344a326e08a44f7f36a943580d 3536 
zaqar_7.0.0-1.dsc
 9b7e395b76bb25bdf279f5cfa672a2eadc209dea0a506c2f46c3820d94c42816 358692 
zaqar_7.0.0.orig.tar.xz
 7f73a112bf899b1e369e053cb66e27afcc61f5e8531c084e99a46f6969732ca8 7584 
zaqar_7.0.0-1.debian.tar.xz
 fdcee87625488842f65d80577b8e44030bc38bfc097071a1b797da86ca1c1075 203068 
python3-zaqar_7.0.0-1_all.deb
 99fa01440441bda2f5facdac77d74b83b66c786615823b04ce431fd8c10219d7 34360 
zaqar-common_7.0.0-1_all.deb
 a89bf778c6b82e7c3ada26f8b585a80989de75c9a2bef900af34c29e40bbd17b 21596 
zaqar-server_7.0.0-1_all.deb
 a1de3f48702106a38f543695ce46debd7e6eb6c2a1538a09f07a4fc7cfe298ff 15656 
zaqar_7.0.0-1_amd64.buildinfo
Files:
 58f96b214a74ce15b24410c6d14e08aa 3536 net optional zaqar_7.0.0-1.dsc
 eefe0f79386b1c9e41fbf6a1c1388204 358692 net optional zaqar_7.0.0.orig.tar.xz
 00fd6d2c951c966302f063bb483db3cc 7584 net optional zaqar_7.0.0-1.debian.tar.xz
 04ac64e54c41ec9f0db1d9d9c0d9a892 203068 python 

Bug#917082: marked as done (openscenegraph depends and build-depends on cruft packages)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 16:53:28 +
with message-id 
and subject line Bug#917082: fixed in openscenegraph 3.2.3+dfsg1-3
has caused the Debian Bug report #917082,
regarding openscenegraph depends and build-depends on cruft packages
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.)


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

package: openscenegraph
version: 3.2.2+dfsg1-2
severity: serious

libopenscenegraph100v5 depends on libcoin80-5 and the openscenegraph source 
package bulid-depends on libcoin80-dev. These packages are no longer built by 
the coin3 source package. They appear to have been replaced by libcoin80c and 
libcoin-dev
--- End Message ---
--- Begin Message ---
Source: openscenegraph
Source-Version: 3.2.3+dfsg1-3

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

Debian distribution maintenance software
pp.
Alberto Luaces Fernández  (supplier of updated openscenegraph 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Jan 2019 11:52:00 +0100
Source: openscenegraph
Binary: libopenthreads-dev libopenthreads20 libopenscenegraph-dev 
libopenscenegraph100v5 openscenegraph-doc openscenegraph openscenegraph-examples
Architecture: source amd64 all
Version: 3.2.3+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Loic Dachary (OuoU) 
Changed-By: Alberto Luaces Fernández 
Description:
 libopenscenegraph-dev - 3D scene graph, development files
 libopenscenegraph100v5 - 3D scene graph, shared libs
 libopenthreads-dev - Object-Oriented (OO) thread interface for C++, 
development files
 libopenthreads20 - Object-Oriented (OO) thread interface for C++, shared libs
 openscenegraph - 3D scene graph, utilities and examples (binaries)
 openscenegraph-doc - 3D scene graph, documentation
 openscenegraph-examples - 3D scene graph, examples (sources)
Closes: 912866 917082
Changes:
 openscenegraph (3.2.3+dfsg1-3) unstable; urgency=medium
 .
   * Use the new version of libcoin (Closes: #917082, #912866).
Checksums-Sha1:
 ac1cfc40668d9c3fdeb705946b3c2f868170a1e6 2922 openscenegraph_3.2.3+dfsg1-3.dsc
 308fde82ba252b66ee6180038e55b3d40332ba6f 25280 
openscenegraph_3.2.3+dfsg1-3.debian.tar.xz
 ba996d7346b89b9464af68ebfad1a7125316704a 453468 
libopenscenegraph-dev_3.2.3+dfsg1-3_amd64.deb
 6548026e6eaf9dd3f2b33b463030b482ed9d09a1 185522728 
libopenscenegraph100v5-dbgsym_3.2.3+dfsg1-3_amd64.deb
 83dcdf8b160514f82e2194931deba7a1552a521b 590 
libopenscenegraph100v5_3.2.3+dfsg1-3_amd64.deb
 ef01c704a0dc38d2fae7c371d67dbfbb6f847bec 25888 
libopenthreads-dev_3.2.3+dfsg1-3_amd64.deb
 6e3f6b2850ab9275c78adb951aff8f507c80d6af 48268 
libopenthreads20-dbgsym_3.2.3+dfsg1-3_amd64.deb
 618278ccae78b25ae4b0b5e80701034c5ae5149f 26924 
libopenthreads20_3.2.3+dfsg1-3_amd64.deb
 b385dbd7be7f54a33db09ec91232854203fb48dc 49219216 
openscenegraph-dbgsym_3.2.3+dfsg1-3_amd64.deb
 a0ec272196aa9b5f8ef6aab184d2d15e68a93d6e 5147996 
openscenegraph-doc_3.2.3+dfsg1-3_all.deb
 b4a6240dd28d7283d89ffb7c20c89dda3ac8366c 469132 
openscenegraph-examples_3.2.3+dfsg1-3_all.deb
 2fa707dc32ca3ae219b2b3caf1c82253282c5523 21942 
openscenegraph_3.2.3+dfsg1-3_amd64.buildinfo
 d70faba982450f6d0200b86603604376044e2b8b 1780848 
openscenegraph_3.2.3+dfsg1-3_amd64.deb
Checksums-Sha256:
 4867b00d8a1fa6205b443ea04a6d72bd44a1bf32304b5b2778b2661c0ed0aec9 2922 
openscenegraph_3.2.3+dfsg1-3.dsc
 575d199cf030b7b7efe4fec87b8b7ba868d21dc576d2118497f08732532e527b 25280 
openscenegraph_3.2.3+dfsg1-3.debian.tar.xz
 efdb5eda40365b65c0f7596565ff472ef35fea0d7678356f93ac06e56e4e627e 453468 
libopenscenegraph-dev_3.2.3+dfsg1-3_amd64.deb
 40aff4e546064b1733210b53c9539074d715f2a5547399749cf43c68f88babb9 185522728 
libopenscenegraph100v5-dbgsym_3.2.3+dfsg1-3_amd64.deb
 9d8d81f917703913b073257320fbd1be0f6bb97ffe12ee694f7c654a5f01e87c 590 
libopenscenegraph100v5_3.2.3+dfsg1-3_amd64.deb
 e61994d321d159987aed5e72757b7eb7cffe29299204cfee9d7a821dac1e12e0 25888 

Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

[Raphael Hertzog]

Hi,

On Sat, 12 Jan 2019, Adrian Bunk wrote:
> pyside2 is now built without patchelf on mips64el.
> 
> Doing the same for mips and mipsel should fix the problem for pivy.

Yeah, but this is not going in the right direction. This means that
pyside will be built with the embedded patchelf. The embedded patchelf is
outdated. But it will build and do its work...

Really, if the test suite failure can't be fixed quickly, it would be
better to ignore the failure on the broken architectures and let the
package build anyway. It's unlikely that the tool is entirely broken...
and it's just a pity to ask pyside to deal with a varying set of
architectures for patchelf.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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

Processed: Bug #919094 in zaqar marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919094 [zaqar] Please remove (build-)dependency on mongodb for buster
Added tag(s) pending.

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

Bug#919094: Bug #919094 in zaqar marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #919094 in zaqar 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/openstack-team/services/zaqar/commit/80ad7d77b278e2d5e45730f6df4431b4c6fe36cc


Remove build-depends on mongodb, and do not test with it (Closes: #919094).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919094

Processed: add blocking info

[Debian Bug Tracking System]

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

> block 897156 by 887497
Bug #897156 [src:node-cache-base] node-cache-base: FTBFS and Debci failure with 
node-is-extendable 1.0.1-1
897156 was not blocked by any bugs.
897156 was not blocking any bugs.
Added blocking bug(s) of 897156: 887497
> thanks
Stopping processing here.

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

Bug#918848: Plans for stretch-backports wrt. CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866?

[intrigeri]

Hi Michael!

Thanks for the quick answer.

Michael Biebl:
> Am 13.01.19 um 10:46 schrieb intrigeri:
>> What's your plan wrt. stretch-backports? 

> I do think we nailed the worst regressions by now, so my plan was to
> wait until 240-4 has migrated to testing and then upload that to
> stretch-backports, for the simple reason that this means less effort for
> me.

This is reassuring.

> If someone want's to backport the fixes to 239-12~bpo9+1, that would
> obviously ok with me as well.

*If* we decide to fall back to this option for Tails, I'll happily
share the Git branch (and even upload to stretch-backports after
someone reviews it). But I do hope we won't have to go that way.

>> FWIW, on the Tails side I'll build a custom backport of 240-4 and will
>> run it through the Tails integration test suite, because we have other
>> incentives to upgrade (getting the fixes for
>> https://github.com/systemd/systemd/issues/9461) and I'd rather do this
>> upgrade now in a controlled, relaxed way, than at the last minute
>> before our freeze (if v240 is uploaded to stretch-backports on
>> Jan 17-18).

> Please let us know about the results of those tests.
> If 240-4 fails horribly, we could revisit the decision to upload this
> version to stretch-backports.

Will do!

Cheers,
-- 
intrigeri

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

[Andrej Shadura]

Hi,

I'm currently afk, but could you please summarise all information you've
got and send to hos...@lists.infradead.org adding this bug and myself to
Cc:?

Thanks!

-- 
Cheers,
  Andrej

On Sun, 13 Jan 2019, 16:33 Different55 
> On Sunday, January 13, 2019 5:21 AM, Andrej Shadura 
> wrote:
>
> > Is that a Broadcom card? "Setting a MAC" in the logs looks suspicious,
> > AFAIK Broadcom driver's don’t support that correctly.
> >
> > By the way, it would be great if you also tested the snapshot
> > currently in experimental.
> >
> > --
> >
> > Cheers,
> > Andrej
>
> Just tested out the package in experimental (2:2.7+git20190108+11ce7a1-1)
> and I'm seeing the same issue.
>
> According to lshw it seems to be an Intel card.
>
> $ sudo lshw -C network
>   *-network
>description: Wireless interface
>product: Wireless 3165
>vendor: Intel Corporation
>physical id: 0
>bus info: pci@:01:00.0
>logical name: wls8
>version: 79
>serial: xx:xx:xx:xx:xx:xx
>width: 64 bits
>clock: 33MHz
>capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
>configuration: broadcast=yes driver=iwlwifi
> driverversion=4.19.0-1-amd64 firmware=29.1044073957.0 ip=192.168.1.9
> latency=0 link=yes multicast=yes wireless=IEEE 802.11
>resources: irq:138 memory:d100-d1001fff
>

Bug#919095: Bug#919092: fixed in mongo-java-driver 3.6.3-2

[tony mancill]

On Sun, Jan 13, 2019 at 01:51:17PM +0100, Emmanuel Bourg wrote:
> Le 12/01/2019 à 21:31, tony mancill a écrit :
> 
> > Should I revert 
> > https://salsa.debian.org/java-team/apache-log4j2/commit/4d8cf4493ad9f63a8cf8d24ae463bd18a12ed1a1
> >  and restore support for that logging adapter?
> 
> You can revert the commit but don't bother uploading again now, this can
> wait the next package update. I don't think the mongodb module is
> actually used.

Done.  Thank you for weighing in.
tony


signature.asc
Description: PGP signature

Bug#918628: node-stream-splicer FTBFS with nodejs 10.15.0

[Bastien Roucariès]

Package: node-stream-splicer
Version: 2.0.0
Followup-For: Bug #918628

control: forwarded -1 https://github.com/browserify/stream-splicer/issues/11
control: tags -1 + upstream



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 node-stream-splicer depends on:
ii  node-inherits  2.0.3-1
ii  nodejs 10.15.0~dfsg-8

node-stream-splicer recommends no packages.

node-stream-splicer suggests no packages.

Bug#784451: marked as done ([ball] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 16:04:25 +
with message-id 
and subject line Bug#784451: fixed in ball 1.5.0+git20180813.37fc53c-2
has caused the Debian Bug report #784451,
regarding [ball] Qt4's WebKit removal
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.)


-- 
784451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ball
Version: 1.4.2+20140406-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Med Packaging Team ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: ball
Source-Version: 1.5.0+git20180813.37fc53c-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ball package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Jan 2019 15:49:01 +0100
Source: ball
Binary: libball1.5-data libball1.5 libball1.5-dev libballview1.5 
libballview1.5-dev python-ball ballview libball1.5-doc
Architecture: source
Version: 1.5.0+git20180813.37fc53c-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 ballview   - free molecular modeling and molecular graphics tool
 libball1.5 - Biochemical Algorithms Library
 libball1.5-data - Biochemical Algorithms Library (data files)
 libball1.5-dev - Header files for the Biochemical Algorithms Library
 libball1.5-doc - documentation for the BALL library
 libballview1.5 - Biochemical Algorithms Library, VIEW framework
 libballview1.5-dev - Header files for the VIEW part of the Biochemical 
Algorithms Libr
 python-ball - Python bindings for the Biochemical Algorithms Library
Closes: 784451 919172
Changes:
 ball (1.5.0+git20180813.37fc53c-2) unstable; urgency=medium
 .
   * Fix Build-Depends (Thanks for the hints to Adrian Bunk
 )
 Closes: #784451
   * Fix FTBFS on architectures where char is unsigned
 (Thanks for the fix to Adrian Bunk )
 Closes: #919172
Checksums-Sha1:
 86deaedbe497f07ece3e417f91ce6bb211efa50c 3045 
ball_1.5.0+git20180813.37fc53c-2.dsc
 84917dd92f6c0c2284d6803c5f12124b6732e592 12472 
ball_1.5.0+git20180813.37fc53c-2.debian.tar.xz
 

Bug#919172: marked as done (ball FTBFS on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 16:04:26 +
with message-id 
and subject line Bug#919172: fixed in ball 1.5.0+git20180813.37fc53c-2
has caused the Debian Bug report #919172,
regarding ball FTBFS on architectures where char is unsigned
to be marked as done.

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

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


-- 
919172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ball
Version: 1.5.0+git20180813.37fc53c-1
Severity: serious
Tags: patch ftbfs

https://buildd.debian.org/status/package.php?p=ball=sid

...
[  9%] Building CXX object CMakeFiles/BALL.dir/source/DATATYPE/hashGrid.C.o
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
   };
   ^
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ball-1.5.0+git20180813.37fc53c/source/DATATYPE/hashGrid.C:23:3: 
error: narrowing conversion of '-1' from 'int' to 'char'