Processed: severity of 902314 is normal

[Debian Bug Tracking System]

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

> severity 902314 normal
Bug #902314 [libudev1] libudev1: Installing libudev1 239-1 removes 48 critical 
packages
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#902317: disruptor: FTBFS with openjdk-10-jdk - package sun.misc does not exist

[tony mancill]

Source: disruptor
Version: 3.3.11-1
Severity: serious

The disruptor package fails build in unstable.

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/Sequence.java:[18,16] 
package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/Sequence.java:[49,26] 
cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.Sequence
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/RingBuffer.java:[19,16]
 package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/RingBuffer.java:[34,26]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.RingBufferFields
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[24,16] 
package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[94,26] 
cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[124,19]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/MultiProducerSequencer.java:[20,16]
 package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/MultiProducerSequencer.java:[35,26]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.MultiProducerSequencer
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[100,45]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[100,92]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[102,24]
 cannot find symbol
  symbol: class Unsafe
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[104,39]
 cannot find symbol
  symbol: class Unsafe
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[106,29]
 cannot find symbol
  symbol: class Unsafe
[INFO] 14 errors 
...

Bug#894423: mlbviewer: No longer works starting in 2018

[Andreas Beckmann]

On Fri, 30 Mar 2018 08:41:38 +0200 Sebastien Delafond 
wrote:
> mlbviewer no longer works, starting in 2018[0]. A new implementation is
> in the works[1], with corresponding instructions[2]. It will be packaged
> later, but in the meantime I've filed #894422 to remove mlbviewer from
> unstable.

Should the unusable package be removed from stable as well?


Andreas

Bug#893386: marked as done (librime 1.2.10+dfsg2-1 makes brise FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 25 Jun 2018 10:21:18 +0800
with message-id <2718097.EfDKXMK01j@hosiet-mi>
and subject line Explicitly mark Bug 893386 as closed by librime/1.3.1+dfsg1-1
has caused the Debian Bug report #893386,
regarding librime 1.2.10+dfsg2-1 makes brise FTBFS
to be marked as done.

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

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


-- 
893386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librime-bin
Version: 1.2.10+dfsg2-1
Severity: serious
Control: affects -1 src:brise

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/brise-0.35'
# create a default.custom.yaml here, and use it
# to build all the schemas
echo "patch:"  > default.custom.yaml
echo "  schema_list:" >> default.custom.yaml
find -name '*.schema.yaml' \
| xargs -l1 basename -s .schema.yaml \
| perl -pe 's/^/- schema: /' \
| sort | uniq >> default.custom.yaml
mkdir -p data
cp -v default.custom.yaml data
'default.custom.yaml' -> 'data/default.custom.yaml'
cp -v extra/*.yaml data
'extra/array30.dict.yaml' -> 'data/array30.dict.yaml'
'extra/array30.schema.yaml' -> 'data/array30.schema.yaml'
'extra/scj6.dict.yaml' -> 'data/scj6.dict.yaml'
'extra/scj6.schema.yaml' -> 'data/scj6.schema.yaml'
'extra/stenotype.schema.yaml' -> 'data/stenotype.schema.yaml'
'extra/wubi_trad.schema.yaml' -> 'data/wubi_trad.schema.yaml'
dh_auto_build
make -j1
make[2]: Entering directory '/build/1st/brise-0.35'
building rime data.
rime_deployer --build  /build/1st/brise-0.35/data
make[2]: Leaving directory '/build/1st/brise-0.35'
# restore the original copy of default.yaml
cp -v default.yaml data
'default.yaml' -> 'data/default.yaml'
rm -fv data/default.custom.yaml
removed 'data/default.custom.yaml'
make[1]: Leaving directory '/build/1st/brise-0.35'
   dh_auto_test
 fakeroot debian/rules binary
dh binary
   dh_testroot
   dh_prep
   dh_auto_install
make -j1 install DESTDIR=/build/1st/brise-0.35/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/build/1st/brise-0.35'
installing rime data into 
'/build/1st/brise-0.35/debian/tmp/usr/share/rime-data'.
install: omitting directory '/build/1st/brise-0.35/data/build'
make[1]: *** [Makefile:32: install] Error 1
make[1]: Leaving directory '/build/1st/brise-0.35'
dh_auto_install: make -j1 install DESTDIR=/build/1st/brise-0.35/debian/tmp 
AM_UPDATE_INFO_DIR=no returned exit code 2
make: *** [debian/rules:5: binary] Error 2


The failure is caused by a data/build directory created
when building brise with librime 1.2.10+dfsg2-1.

I do not know which of the packages needs fixing,
please reassign if I reported against the wrong one.
--- End Message ---
--- Begin Message ---
Source: librime
Source-Version: 1.3.1+dfsg1-1

--
Regards,
Boyuan Yang

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

Processed: forcibly merging 901148 902330 ...

[Debian Bug Tracking System]

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

> forcemerge 901148 902330
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound in KDE plasma
Bug #902330 [timidity] timidity: daemon excludes pulseaudio daemon from using 
audio cards
Severity set to 'important' from 'critical'
Marked as found in versions timidity/2.14.0-2.
Merged 901148 902330
> retitle 901148 timidity: upgrading to 2.14.0-2 broke sound via pulseaudio
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound in KDE plasma
Bug #902330 [timidity] timidity: daemon excludes pulseaudio daemon from using 
audio cards
Changed Bug title to 'timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio' from 'timidity: upgrading to 2.14.0-2 broke sound in KDE plasma'.
Changed Bug title to 'timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio' from 'timidity: daemon excludes pulseaudio daemon from using audio 
cards'.
> thanks
Stopping processing here.

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

Bug#902317: marked as done (disruptor: FTBFS with openjdk-10-jdk - package sun.misc does not exist)

[Debian Bug Tracking System]

Your message dated Mon, 25 Jun 2018 05:33:51 +
with message-id 
and subject line Bug#902317: fixed in disruptor 3.4.2-1
has caused the Debian Bug report #902317,
regarding disruptor: FTBFS with openjdk-10-jdk - package sun.misc does not exist
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.)


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

The disruptor package fails build in unstable.

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/Sequence.java:[18,16] 
package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/Sequence.java:[49,26] 
cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.Sequence
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/RingBuffer.java:[19,16]
 package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/RingBuffer.java:[34,26]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.RingBufferFields
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[24,16] 
package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[94,26] 
cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[124,19]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/MultiProducerSequencer.java:[20,16]
 package sun.misc does not exist
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/MultiProducerSequencer.java:[35,26]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.MultiProducerSequencer
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[100,45]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[100,92]
 cannot find symbol
  symbol:   class Unsafe
  location: class com.lmax.disruptor.util.Util
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[102,24]
 cannot find symbol
  symbol: class Unsafe
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[104,39]
 cannot find symbol
  symbol: class Unsafe
[ERROR] 
/build/disruptor-3.3.11/src/main/java/com/lmax/disruptor/util/Util.java:[106,29]
 cannot find symbol
  symbol: class Unsafe
[INFO] 14 errors 
...
--- End Message ---
--- Begin Message ---
Source: disruptor
Source-Version: 3.4.2-1

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated disruptor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jun 2018 22:13:04 -0700
Source: disruptor
Binary: libdisruptor-java
Architecture: source
Version: 3.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 libdisruptor-java - Disruptor - High Performance Inter-Thread Messaging 
Library for J
Closes: 902317
Changes:
 disruptor (3.4.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 3.4.2
 - Fix race condition in BatchEventProcessor with 3 or more
   starting/halting concurrently.
 - Fix race between run() and halt() on BatchEventProcessor.
 - Drop support for JDK6, support JDK7 and above only.
 - Add ThreadHints.onSpinWait to all busy spins within Disruptor.
 - Increase default sleep time for LockSupport.parkNanos 

Bug#900248: nvidia-driver:update to 390.59 breaks direct rendering

[Andreas Beckmann]

On 2018-06-24 16:55, Dean Loros wrote:
> I let things sit overnight so I could come at this again from a fresh
> angle...right now my main & backup systems are down. For some reason, when
> I rebooted after the edit to the config file, I lost the link to
> /etc/alternatives, not sure why. Taking a break to do work around home -
> then I will re-establish all the links & try again.

this should help you:

dpkg-reconfigure nvidia-alternative


Andreas

Bug#900485: python-pbcore: FTBFS and Debci failure with NumPy 1.14

[Graham Inggs]

Control: tags -1 + patch

Hi Sandro

I have cherry-picked the attached patch from pbcore upstream which
fixes the problems with NumPy 1.14.
However, with this patch in place, pbcore will need a build-dependency
on python-numpy (>= 1:1.14~) and its autopkgtests will fail with NumPy
1.13.

I thought the latter could be dealt with by dh_numpy, but after
reading /usr/share/doc/python-numpy/README.DebianMaints, it seems it
is only useful for arch:any packages, and python-pbcore is arch:all.
Did I miss something?  Do you have any suggestions on how to deal with
this?  python-pydap is similarly affected (#900486)

Regards
Graham
Description: Fix FTBFS with NumPy 1.14
Bug-Debian: https://bugs.debian.org/900485
Origin: upstream, https://github.com/PacificBiosciences/pbcore/commit/b7ef4238b6388f984a264b8a912450b652177dbf
Author: David Seifert 
Last-Update: 2018-01-10

--- a/tests/test_pbdataset.py
+++ b/tests/test_pbdataset.py
@@ -1405,7 +1405,7 @@
 self.assertEqual(
 str(readers[0].referenceInfo('E.faecalis.1')),
 "(27, 27, 'E.faecalis.1', 'E.faecalis.1', 1482, "
-"'a1a59c267ac1341e5a12bce7a7d37bcb', 0L, 0L)")
+"'a1a59c267ac1341e5a12bce7a7d37bcb', 0, 0)")
 # TODO: add a bam with a different referenceInfoTable to check merging
 # and id remapping:
 #self.assertEqual(
@@ -1748,7 +1748,7 @@
 self.assertEqual(
 str(aln.referenceInfoTable),
 ("[ (1, 1, 'lambda_NEB3011', 'lambda_NEB3011', "
- "48502, 'a1319ff90e994c8190a4fe6569d0822a', 0L, 338113L)]"))
+ "48502, 'a1319ff90e994c8190a4fe6569d0822a', 0, 338113)]"))
 self.assertEqual(set(aln.tId), {1})
 # + 1, because bounds are inclusive, rather than exclusive
 self.assertEqual(len3, (aln.referenceInfoTable[0].EndRow -
@@ -1775,9 +1775,9 @@
 self.assertEqual(
 str(aln.referenceInfoTable),
 ("[ (0, 0, 'ecoliK12_pbi_March2013', 'ecoliK12_pbi_March2013', "
- "4642522, '52cd7c5fa92877152fa487906ae484c5', 0L, 57034L)\n"
+ "4642522, '52cd7c5fa92877152fa487906ae484c5', 0, 57034)\n"
  " (1, 1, 'lambda_NEB3011', 'lambda_NEB3011', 48502, "
- "'a1319ff90e994c8190a4fe6569d0822a', 57035L, 57146L)]"))
+ "'a1319ff90e994c8190a4fe6569d0822a', 57035, 57146)]"))
 self.assertEqual(set(aln.tId), {0, 1})
 # + 1, because bounds are inclusive, rather than exclusive
 self.assertEqual(len1, (aln.referenceInfoTable[1].EndRow -
@@ -1810,7 +1810,7 @@
 self.assertEqual(
 str(aln.referenceInfoTable),
 ("[ (0, 0, 'ecoliK12_pbi_March2013', 'ecoliK12_pbi_March2013', "
- "4642522, '52cd7c5fa92877152fa487906ae484c5', 0L, 0L)]"))
+ "4642522, '52cd7c5fa92877152fa487906ae484c5', 0, 0)]"))
 self.assertEqual(set(aln.tId), {0})
 self.assertEqual(aln.referenceInfo('ecoliK12_pbi_March2013'),
  aln.referenceInfo(0))
@@ -1835,7 +1835,7 @@
 self.assertEqual(
 str(aln.referenceInfoTable),
 ("[ (0, 0, 'ecoliK12_pbi_March2013', 'ecoliK12_pbi_March2013', "
- "4642522, '52cd7c5fa92877152fa487906ae484c5', 0L, 0L)]"))
+ "4642522, '52cd7c5fa92877152fa487906ae484c5', 0, 0)]"))
 self.assertEqual(set(aln.tId), {0})
 self.assertEqual(aln.referenceInfo('ecoliK12_pbi_March2013'),
  aln.referenceInfo(0))
@@ -1860,9 +1860,9 @@
 self.assertEqual(
 str(aln.referenceInfoTable),
 ("[ (0, 0, 'ecoliK12_pbi_March2013', 'ecoliK12_pbi_March2013', "
- "4642522, '52cd7c5fa92877152fa487906ae484c5', 0L, 0L)\n"
+ "4642522, '52cd7c5fa92877152fa487906ae484c5', 0, 0)\n"
  " (1, 1, 'lambda_NEB3011', 'lambda_NEB3011', 48502, "
- "'a1319ff90e994c8190a4fe6569d0822a', 0L, 0L)]"))
+ "'a1319ff90e994c8190a4fe6569d0822a', 0, 0)]"))
 self.assertEqual(set(aln.tId), {0, 1})
 self.assertEqual(aln.referenceInfo('ecoliK12_pbi_March2013'),
  aln.referenceInfo(0))
@@ -1894,9 +1894,9 @@
 self.assertEqual(
 str(aln.referenceInfoTable),
 ("[ (0, 0, 'ecoliK12_pbi_March2013', 'ecoliK12_pbi_March2013', "
- "4642522, '52cd7c5fa92877152fa487906ae484c5', 0L, 0L)\n"
+ "4642522, '52cd7c5fa92877152fa487906ae484c5', 0, 0)\n"
  " (1, 1, 'lambda_NEB3011', 'lambda_NEB3011', 48502, "
- "'a1319ff90e994c8190a4fe6569d0822a', 0L, 0L)]"))
+ "'a1319ff90e994c8190a4fe6569d0822a', 0, 0)]"))
 self.assertEqual(set(aln.tId), {0, 1})
 self.assertEqual(aln.referenceInfo('ecoliK12_pbi_March2013'),
  aln.referenceInfo(0))

Processed: Re: Bug#900485: python-pbcore: FTBFS and Debci failure with NumPy 1.14

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #900485 [src:python-pbcore] python-pbcore: FTBFS and Debci failure with 
NumPy 1.14
Added tag(s) patch.

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

Bug#901327: tigervnc: FTBFS: Hunk #1 FAILED

[Clint Adams]

On Mon, Jun 11, 2018 at 05:21:00PM +0300, Niko Tyni wrote:
>   touch debian/stamp-patched
>   /usr/bin/make -f debian/rules update-config
>   make[1]: Entering directory '/<>/tigervnc-1.7.0+dfsg'
>   make[1]: 'update-config' is up to date.
>   make[1]: Leaving directory '/<>/tigervnc-1.7.0+dfsg'
>   cd ./unix/xserver && \
> { tar --strip-components 1 -xvJf /usr/src/xorg-server.tar.xz | \
> sed -e 's@^[^/]*/@@' > .apply-patches-unify-xorg-and-vnc-tree.files; 
> } && \
> touch .apply-patches-unify-xorg-and-vnc-tree.stamp
>   cd ./unix/xserver && { \
>   patch --no-backup-if-mismatch -p1 < 
> /<>/tigervnc-1.7.0+dfsg/debian/xserver119.patch && \
>   touch .apply-patches-vnc-patch-xorg.stamp; \
>   }
>   patching file configure.ac
>   Hunk #2 succeeded at 1778 (offset -86 lines).
>   Hunk #3 succeeded at 1817 (offset -86 lines).
>   Hunk #4 succeeded at 2036 (offset -87 lines).
>   Hunk #5 succeeded at 2571 (offset -126 lines).
>   patching file hw/Makefile.am
>   patching file mi/miinitext.c
>   Hunk #1 FAILED at 114.
>   Hunk #2 succeeded at 109 (offset -129 lines).
>   1 out of 2 hunks FAILED -- saving rejects to file mi/miinitext.c.rej
>   patching file include/os.h
>   Hunk #1 succeeded at 633 (offset 12 lines).
>   make: *** [debian/rules:129: 
> unix/xserver/.apply-patches-vnc-patch-xorg.stamp] Error 1

Why is patchsys-quilt.mk being used with a 3.0 (quilt) source package?

Processed: found 900974 in 3.14-5-1, notfixed 900974 in 4.1-1-2

[Debian Bug Tracking System]

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

> found 900974 3.14-5-1
Bug #900974 {Done: Dirk Eddelbuettel } [r-cran-hmisc] 
r-cran-hmisc: Missing Depends: r-cran-foreign, r-cran-nnet
Marked as found in versions hmisc/3.14-5-1.
> notfixed 900974 4.1-1-2
Bug #900974 {Done: Dirk Eddelbuettel } [r-cran-hmisc] 
r-cran-hmisc: Missing Depends: r-cran-foreign, r-cran-nnet
No longer marked as fixed in versions hmisc/4.1-1-2.
> thanks
Stopping processing here.

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

Processed: tagging 880233

[Debian Bug Tracking System]

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

> tags 880233 - buster sid stretch
Bug #880233 [src:openbsc] openbsc: FTBFS: | ./openbsc/conftest.c:22: undefined 
reference to `dlopen'
Removed tag(s) buster, sid, and stretch.
> thanks
Stopping processing here.

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

Bug#896298: python-cluster: cluster fails to import

[Andreas Beckmann]

Followup-For: Bug #896298
Control: tag -1 pending

stretch-pu request: https://bugs.debian.org/902294


Andreas

Processed: Re: python-cluster: cluster fails to import

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896298 {Done: Adrian Bunk } [python-cluster] 
python-cluster: cluster fails to import
Added tag(s) pending.

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

Bug#896253: visionegg is marked for autoremoval from testing

[Andreas Beckmann]

On Fri, 18 May 2018 07:54:41 +0200 Andreas Tille 
wrote:
> There is an old issue opened upstream[1] which is not answered by
> the authors.  Seems this project is dead and may be we need to
> drop the package from Debian.

Given that this looks pretty much unfixable in stretch, should the
package be removed from stretch?


Andreas

Bug#901495: marked as done (redis: multiple security issues in Lua scripting (CVE-2018-11218 CVE-2018-11219))

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 16:20:13 +
with message-id 
and subject line Bug#901495: fixed in redis 3:3.2.6-3+deb9u2
has caused the Debian Bug report #901495,
regarding redis: multiple security issues in Lua scripting (CVE-2018-11218 
CVE-2018-11219)
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.)


-- 
901495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redis
Version: 3:3.2.6-1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

>From https://github.com/antirez/redis/issues/5017:

> The Apple Security Team, together with Alibaba and myself,
> identified several security issues in the Lua script engine. The full
> report is here: 

No CVE has (yet) been assigned:

  https://github.com/antirez/redis/issues/5017#issuecomment-397038992

Version tagged >= 3:3.2.6-1 due to stretch having Lua support but
wheezy (2.8.17) does not.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 3:3.2.6-3+deb9u2

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated redis 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, 18 Jun 2018 19:12:58 +0200
Source: redis
Binary: redis-server redis-tools redis-sentinel
Built-For-Profiles: nocheck
Architecture: source amd64
Version: 3:3.2.6-3+deb9u2
Distribution: stretch
Urgency: high
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 redis-sentinel - Persistent key-value database with network interface 
(monitoring)
 redis-server - Persistent key-value database with network interface
 redis-tools - Persistent key-value database with network interface (client)
Closes: 850534 880474 901495
Changes:
 redis (3:3.2.6-3+deb9u2) stretch; urgency=medium
 .
   * Correct RunTimeDirectory -> RuntimeDirectory typo in systemd .service
 files. (Closes: #850534, #880474)
 .
 redis (3:3.2.6-3+deb9u1) stretch-security; urgency=high
 .
   * CVE-2018-11218, CVE-2018-11219: Backport patches to fix multiple heap
 corruption and integer overflow vulnerabilities. (Closes: #901495)
Checksums-Sha1:
 f2ff97c5aca201e7121e045467346703e22578ad 2013 redis_3.2.6-3+deb9u2.dsc
 0c7bc5c751bdbc6fabed178db9cdbdd948915d1b 1544806 redis_3.2.6.orig.tar.gz
 05dc32ad1687b5cbf63f6991c87dac0617c5bcea 38952 
redis_3.2.6-3+deb9u2.debian.tar.xz
 a7f99638c2153d735413c1881ddb22e38ef95a20 18520 
redis-sentinel_3.2.6-3+deb9u2_amd64.deb
 924866e7270d9124ac0cd4915cd9394e933c657e 1038240 
redis-server-dbgsym_3.2.6-3+deb9u2_amd64.deb
 2be0ad58c1f791fd4478e1db04a96e3e5d4ca878 412640 
redis-server_3.2.6-3+deb9u2_amd64.deb
 016c4fe02b025c8cc42751e7f9f7c2865d05f3a0 1255814 
redis-tools-dbgsym_3.2.6-3+deb9u2_amd64.deb
 db5c19e572a644779772f4e749c947024aa2b152 462686 
redis-tools_3.2.6-3+deb9u2_amd64.deb
 af8e619f6a4b507f27efef23ac4f2835edfeed25 7210 
redis_3.2.6-3+deb9u2_amd64.buildinfo
Checksums-Sha256:
 4edd6de71bdb0c409723ef6d4d808dc84f5615ce897e4cc958527280d1f8174b 2013 
redis_3.2.6-3+deb9u2.dsc
 2e1831c5a315e400d72bda4beaa98c0cfbe3f4eb8b20c269371634390cf729fa 1544806 
redis_3.2.6.orig.tar.gz
 f1f9a05c90e72a7c0f8e343ebec93ce43cc0fafae54379d78941f1b2e13487f5 38952 
redis_3.2.6-3+deb9u2.debian.tar.xz
 d7f29e2f0b6c11ea9ff663070a5f4c1e62d89a2be67885913bc9351d1da738bc 18520 
redis-sentinel_3.2.6-3+deb9u2_amd64.deb
 5adbdfd9e1514f2f428121bf5e9de11bf3090a1e6efa2213e5c1390ff1b42b47 1038240 
redis-server-dbgsym_3.2.6-3+deb9u2_amd64.deb
 097ecb62420b47deb78629cf00b15ebba6216078006f3a88a21bf55a5d1e9154 412640 
redis-server_3.2.6-3+deb9u2_amd64.deb
 467a4f69f9258aba1b487955a3c507ad788a23140be1d2a4856911026a608244 1255814 
redis-tools-dbgsym_3.2.6-3+deb9u2_amd64.deb
 061da861c506626b54ab648f6120e96818ff423faa08c469ee8e44aaca87d2e5 462686 
redis-tools_3.2.6-3+deb9u2_amd64.deb
 

Bug#901495: marked as done (redis: multiple security issues in Lua scripting (CVE-2018-11218 CVE-2018-11219))

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 16:20:06 +
with message-id 
and subject line Bug#901495: fixed in redis 3:3.2.6-3+deb9u1
has caused the Debian Bug report #901495,
regarding redis: multiple security issues in Lua scripting (CVE-2018-11218 
CVE-2018-11219)
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.)


-- 
901495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redis
Version: 3:3.2.6-1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

>From https://github.com/antirez/redis/issues/5017:

> The Apple Security Team, together with Alibaba and myself,
> identified several security issues in the Lua script engine. The full
> report is here: 

No CVE has (yet) been assigned:

  https://github.com/antirez/redis/issues/5017#issuecomment-397038992

Version tagged >= 3:3.2.6-1 due to stretch having Lua support but
wheezy (2.8.17) does not.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 3:3.2.6-3+deb9u1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated redis 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, 14 Jun 2018 15:08:27 +0200
Source: redis
Binary: redis-server redis-tools redis-sentinel
Architecture: source amd64
Version: 3:3.2.6-3+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 redis-sentinel - Persistent key-value database with network interface 
(monitoring)
 redis-server - Persistent key-value database with network interface
 redis-tools - Persistent key-value database with network interface (client)
Closes: 901495
Changes:
 redis (3:3.2.6-3+deb9u1) stretch-security; urgency=high
 .
   * CVE-2018-11218, CVE-2018-11219: Backport patches to fix multiple heap
 corruption and integer overflow vulnerabilities. (Closes: #901495)
Checksums-Sha1:
 2c6d029f541e0f6eb15491f9d3c3566b1f37522f 2013 redis_3.2.6-3+deb9u1.dsc
 0c7bc5c751bdbc6fabed178db9cdbdd948915d1b 1544806 redis_3.2.6.orig.tar.gz
 5ca7378156cac0d842c80fc76c86a1f0c62d39e7 38904 
redis_3.2.6-3+deb9u1.debian.tar.xz
 96a8f2ee6ab578c5eef69f85eb1e9b732a10fcb1 18476 
redis-sentinel_3.2.6-3+deb9u1_amd64.deb
 24275d0221edce2baa1529ac28e55972caf0209b 1038238 
redis-server-dbgsym_3.2.6-3+deb9u1_amd64.deb
 eb69917194d7263b91f27f69e51c450a78f43205 412890 
redis-server_3.2.6-3+deb9u1_amd64.deb
 f3c7d7700e6c40222bf4d1046b66eb03139aa0cf 1255818 
redis-tools-dbgsym_3.2.6-3+deb9u1_amd64.deb
 08fa7f1fa66f554370f9f044e780fdeb26043b34 462498 
redis-tools_3.2.6-3+deb9u1_amd64.deb
 f4209192b39afc65d17775bc9a5241d1e28b6ab9 7195 
redis_3.2.6-3+deb9u1_amd64.buildinfo
Checksums-Sha256:
 80da262658515878816bc54a91025a19dc908e19e900c20edc05105a5a082762 2013 
redis_3.2.6-3+deb9u1.dsc
 2e1831c5a315e400d72bda4beaa98c0cfbe3f4eb8b20c269371634390cf729fa 1544806 
redis_3.2.6.orig.tar.gz
 4dd8b850f189a14f506ab2dbd9ec9825ed1d125390281cd4e51dd3a23047a239 38904 
redis_3.2.6-3+deb9u1.debian.tar.xz
 bdc22af158b230cd4766f73f227eda22a1cfbc0cdcbce370e6e2bca35a68c264 18476 
redis-sentinel_3.2.6-3+deb9u1_amd64.deb
 1bd65e89e6af090127f8046b5628d7bf174d5a02b1a0c2b24877353072bc7583 1038238 
redis-server-dbgsym_3.2.6-3+deb9u1_amd64.deb
 6e698e1511719caa5c868e04d7b84f6bb0478c5d79d5660935feace484f123cb 412890 
redis-server_3.2.6-3+deb9u1_amd64.deb
 366b7b25147ef54a91f379444b9d55030999f747bd02c66d493ecb1f33d77c62 1255818 
redis-tools-dbgsym_3.2.6-3+deb9u1_amd64.deb
 e836f6c21a7d0c9285fd6f6eb5c04cd4f9242ce36370a3665009cf6ccd114fe0 462498 
redis-tools_3.2.6-3+deb9u1_amd64.deb
 1be8c36b74ed80ac3dabb5c940dcba0be77c84e7bffa84adc23deb7e9f51116d 7195 
redis_3.2.6-3+deb9u1_amd64.buildinfo
Files:
 46211e7014c90c56ef19a874429c73c6 2013 database optional 
redis_3.2.6-3+deb9u1.dsc
 

Bug#896403: marked as done (python-fake-factory: faker fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 16:17:10 +
with message-id 
and subject line Bug#896403: fixed in faker 0.7.7-2.1~deb9u1
has caused the Debian Bug report #896403,
regarding python-fake-factory: faker fails to import
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.)


-- 
896403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-fake-factory
Version: 0.7.7-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-fake-factory importing the module faker
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/faker/__init__.py", line 4, in 
from faker.factory import Factory
  File "/usr/lib/python2.7/dist-packages/faker/factory.py", line 10, in 
from faker.config import DEFAULT_LOCALE, PROVIDERS, AVAILABLE_LOCALES
  File "/usr/lib/python2.7/dist-packages/faker/config.py", line 13, in 
AVAILABLE_LOCALES = find_available_locales(PROVIDERS)
  File "/usr/lib/python2.7/dist-packages/faker/utils/loading.py", line 19, in 
find_available_locales
provider_module = import_module(provider_path)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/usr/lib/python2.7/dist-packages/faker/providers/internet/__init__.py", 
line 5, in 
from ipaddress import ip_address, ip_network, IPV4LENGTH, IPV6LENGTH
ImportError: No module named ipaddress

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: faker
Source-Version: 0.7.7-2.1~deb9u1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 14:55:55 +0200
Source: faker
Binary: python-fake-factory python3-fake-factory faker
Architecture: source
Version: 0.7.7-2.1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andreas Beckmann 
Description:
 faker  - Python program that generates fake data
 python-fake-factory - Faker is a Python library that generates fake data 
(Python 2)
 python3-fake-factory - Faker is a Python library that generates fake data 
(Python 3)
Closes: 896403
Changes:
 faker (0.7.7-2.1~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 faker (0.7.7-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * python-fake-factory: Add the missing dependency
 on python-ipaddress. (Closes: #896403)
Checksums-Sha1:
 a56e7751e786a6ca1a098cec553820d091335545 2317 faker_0.7.7-2.1~deb9u1.dsc
 576471490c320c2d43b422eeb5692c119d1624ee 3672 
faker_0.7.7-2.1~deb9u1.debian.tar.xz
 9b886b63f793a570f9bbe10657d9d48946e6fcdc 6816 
faker_0.7.7-2.1~deb9u1_source.buildinfo
Checksums-Sha256:
 c74c6d1eed6fbb0f07e286f33b0f3e22a6dba4fdc78c5af2d3ecbae11eb01e4e 2317 
faker_0.7.7-2.1~deb9u1.dsc
 cfbd509002252861f4afb42e887da24d5797d7d711153679076e53822e0942f6 3672 
faker_0.7.7-2.1~deb9u1.debian.tar.xz
 9a47867a24091e34e93ee783c34234da35e0e0177891e2fb3987fc5cf6c66699 6816 
faker_0.7.7-2.1~deb9u1_source.buildinfo
Files:
 20e9d61e57eeb448d5c3f7f958098988 2317 python optional 
faker_0.7.7-2.1~deb9u1.dsc
 95b23c255e1d4d7bd421995669e6fe92 3672 python optional 
faker_0.7.7-2.1~deb9u1.debian.tar.xz
 b6f125d8d55d637b05eee9ecf0644964 6816 python optional 
faker_0.7.7-2.1~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#896374: marked as done (python3-scruffy: scruffy fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 16:20:04 +
with message-id 
and subject line Bug#896374: fixed in python-scruffy 0.3.3-1.1~deb9u1
has caused the Debian Bug report #896374,
regarding python3-scruffy: scruffy fails to import
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.)


-- 
896374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-scruffy
Version: 0.3.3-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-scruffy importing the module scruffy
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/scruffy/__init__.py", line 1, in 
from .env import Environment
  File "/usr/lib/python3/dist-packages/scruffy/env.py", line 8, in 
from .file import Directory
  File "/usr/lib/python3/dist-packages/scruffy/file.py", line 7, in 
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-scruffy
Source-Version: 0.3.3-1.1~deb9u1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-scruffy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 15:17:36 +0200
Source: python-scruffy
Binary: python-scruffy python3-scruffy
Architecture: source
Version: 0.3.3-1.1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andreas Beckmann 
Description:
 python-scruffy - framework for taking care of a bunch of boilerplate in 
Python2 ap
 python3-scruffy - framework for taking care of a bunch of boilerplate in 
Python3 ap
Closes: 896207 896374
Changes:
 python-scruffy (0.3.3-1.1~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 python-scruffy (0.3.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the missing dependencies on python{,3}-pkg-resources.
 (Closes: #896207, #896374)
Checksums-Sha1:
 5566a373bb5582a1ff46ad5dfacdd83defd88b46 2272 
python-scruffy_0.3.3-1.1~deb9u1.dsc
 5747764df6bcdc7dd5841dfe5a6844bb33dbe841 2520 
python-scruffy_0.3.3-1.1~deb9u1.debian.tar.xz
 05bf403c7813ce4998f1966e6e2f4fca2d1e907e 6604 
python-scruffy_0.3.3-1.1~deb9u1_source.buildinfo
Checksums-Sha256:
 2b1eaad652214d2fdc5aac63ec0a7b593911210a81283b5d5b49d32a04e38a52 2272 
python-scruffy_0.3.3-1.1~deb9u1.dsc
 b74c381aadeb79a809bb285012f1ef4e4c3e6e86bfbd2eb47efb3dee9f0c7f00 2520 
python-scruffy_0.3.3-1.1~deb9u1.debian.tar.xz
 f8214ab756c66b1e99219bf958a9d321b7a266c8e0109a0826a73ee823207ae9 6604 
python-scruffy_0.3.3-1.1~deb9u1_source.buildinfo
Files:
 23ebd31828be8e0e79d765e76b646b58 2272 python optional 
python-scruffy_0.3.3-1.1~deb9u1.dsc
 1042ad67a31e03e62486d5a5091ee354 2520 python optional 
python-scruffy_0.3.3-1.1~deb9u1.debian.tar.xz
 13d31b90903c85528e37723e9e29bea7 6604 python optional 
python-scruffy_0.3.3-1.1~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlsvoB0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCN8kD/92lbVHEBEPXOWW5dzK6U0n6z4pu3WP1Cav
yXIsTk9cmcOAt8p+28Yx/HDz97BdH7nH38WpAdkD/vfPZ38WV9NWXewxv4Y/lHi2
fpoMfeFY05imxnwp99pGZRota3OTb3lNkCMsfKKrsIerfwbwl60C+w0JdIcMM80u
KAjYsna4fu3TUx8ABwn+gz4OtbQ86RVDtPeFT8PaoYpxliaeLI5Jum+QCnxDHPTC
qD/xWAiM1stu6sLyP73FNx8TGfElTtj3bcQ1VTEm1IsHscf/gQfPr1IYyG29rMb4

Bug#896207: marked as done (python-scruffy: scruffy fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 16:20:04 +
with message-id 
and subject line Bug#896207: fixed in python-scruffy 0.3.3-1.1~deb9u1
has caused the Debian Bug report #896207,
regarding python-scruffy: scruffy fails to import
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.)


-- 
896207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-scruffy
Version: 0.3.3-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-scruffy importing the module scruffy
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scruffy/__init__.py", line 1, in 

from .env import Environment
  File "/usr/lib/python2.7/dist-packages/scruffy/env.py", line 8, in 
from .file import Directory
  File "/usr/lib/python2.7/dist-packages/scruffy/file.py", line 7, in 
import pkg_resources
ImportError: No module named pkg_resources

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-scruffy
Source-Version: 0.3.3-1.1~deb9u1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-scruffy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 15:17:36 +0200
Source: python-scruffy
Binary: python-scruffy python3-scruffy
Architecture: source
Version: 0.3.3-1.1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andreas Beckmann 
Description:
 python-scruffy - framework for taking care of a bunch of boilerplate in 
Python2 ap
 python3-scruffy - framework for taking care of a bunch of boilerplate in 
Python3 ap
Closes: 896207 896374
Changes:
 python-scruffy (0.3.3-1.1~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 python-scruffy (0.3.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the missing dependencies on python{,3}-pkg-resources.
 (Closes: #896207, #896374)
Checksums-Sha1:
 5566a373bb5582a1ff46ad5dfacdd83defd88b46 2272 
python-scruffy_0.3.3-1.1~deb9u1.dsc
 5747764df6bcdc7dd5841dfe5a6844bb33dbe841 2520 
python-scruffy_0.3.3-1.1~deb9u1.debian.tar.xz
 05bf403c7813ce4998f1966e6e2f4fca2d1e907e 6604 
python-scruffy_0.3.3-1.1~deb9u1_source.buildinfo
Checksums-Sha256:
 2b1eaad652214d2fdc5aac63ec0a7b593911210a81283b5d5b49d32a04e38a52 2272 
python-scruffy_0.3.3-1.1~deb9u1.dsc
 b74c381aadeb79a809bb285012f1ef4e4c3e6e86bfbd2eb47efb3dee9f0c7f00 2520 
python-scruffy_0.3.3-1.1~deb9u1.debian.tar.xz
 f8214ab756c66b1e99219bf958a9d321b7a266c8e0109a0826a73ee823207ae9 6604 
python-scruffy_0.3.3-1.1~deb9u1_source.buildinfo
Files:
 23ebd31828be8e0e79d765e76b646b58 2272 python optional 
python-scruffy_0.3.3-1.1~deb9u1.dsc
 1042ad67a31e03e62486d5a5091ee354 2520 python optional 
python-scruffy_0.3.3-1.1~deb9u1.debian.tar.xz
 13d31b90903c85528e37723e9e29bea7 6604 python optional 
python-scruffy_0.3.3-1.1~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlsvoB0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCN8kD/92lbVHEBEPXOWW5dzK6U0n6z4pu3WP1Cav
yXIsTk9cmcOAt8p+28Yx/HDz97BdH7nH38WpAdkD/vfPZ38WV9NWXewxv4Y/lHi2
fpoMfeFY05imxnwp99pGZRota3OTb3lNkCMsfKKrsIerfwbwl60C+w0JdIcMM80u
KAjYsna4fu3TUx8ABwn+gz4OtbQ86RVDtPeFT8PaoYpxliaeLI5Jum+QCnxDHPTC
qD/xWAiM1stu6sLyP73FNx8TGfElTtj3bcQ1VTEm1IsHscf/gQfPr1IYyG29rMb4

Bug#900843: marked as done (bouncycastle: CVE-2018-1000180)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 16:17:10 +
with message-id 
and subject line Bug#900843: fixed in bouncycastle 1.56-1+deb9u2
has caused the Debian Bug report #900843,
regarding bouncycastle: CVE-2018-1000180
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.)


-- 
900843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bouncycastle
Version: 1.54-1
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://www.bouncycastle.org/jira/browse/BJA-694

Hi,

The following vulnerability was published for bouncycastle.

CVE-2018-1000180[0]:
| Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier
| have a flaw in the Low-level interface to RSA key pair generator,
| specifically RSA Key Pairs generated in low-level API with added
| certainty may have less M-R tests than expected. This appears to be
| fixed in versions BC 1.60 beta 4 and later, BC-FJA 1.0.2 and later.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000180
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000180
[1] https://www.bouncycastle.org/jira/browse/BJA-694

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bouncycastle
Source-Version: 1.56-1+deb9u2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated bouncycastle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 13 Jun 2018 00:25:10 +0200
Source: bouncycastle
Binary: libbcprov-java libbcprov-java-doc libbcmail-java libbcmail-java-doc 
libbcpkix-java libbcpkix-java-doc libbcpg-java libbcpg-java-doc
Architecture: source all
Version: 1.56-1+deb9u2
Distribution: stretch-security
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libbcmail-java - Bouncy Castle generators/processors for S/MIME and CMS
 libbcmail-java-doc - Bouncy Castle generators/processors for S/MIME and CMS 
(Documenta
 libbcpg-java - Bouncy Castle generators/processors for OpenPGP
 libbcpg-java-doc - Bouncy Castle generators/processors for OpenPGP 
(Documentation)
 libbcpkix-java - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS, OCSP, 
CMP,
 libbcpkix-java-doc - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS... 
(Document
 libbcprov-java - Bouncy Castle Java Cryptographic Service Provider
 libbcprov-java-doc - Bouncy Castle Java Cryptographic Service Provider 
(Documentation)
Closes: 900843
Changes:
 bouncycastle (1.56-1+deb9u2) stretch-security; urgency=high
 .
   * Team upload.
   * Fix CVE-2018-1000180. (Closes: #900843)
Checksums-Sha1:
 9dd3d448f48681b4f4185c91a0940dda3d5aae75 2717 bouncycastle_1.56-1+deb9u2.dsc
 dbbf5e0838df8ec09283c660f87085a41a3ffc8e 6 
bouncycastle_1.56-1+deb9u2.debian.tar.xz
 375f5e273c7a1f465c6f24093f3cb92d460d8f94 13341 
bouncycastle_1.56-1+deb9u2_amd64.buildinfo
 e3a0c95cf01b025b34edeee3f17cc6a46ca9253b 97576 
libbcmail-java-doc_1.56-1+deb9u2_all.deb
 8981ac328cc8803d5315af0960108d26cbf36f84 152204 
libbcmail-java_1.56-1+deb9u2_all.deb
 6c702f40025f244d1b97a014a120e3948b4a6aa2 186052 
libbcpg-java-doc_1.56-1+deb9u2_all.deb
 3c1e54ef88003db94a7173137b3210050940c0c9 351418 
libbcpg-java_1.56-1+deb9u2_all.deb
 c69aef85789d5064c9ce6a9d0d80923221adb890 338980 
libbcpkix-java-doc_1.56-1+deb9u2_all.deb
 93448a45941e6af7a3a31598749c8a58f8e909ed 714420 
libbcpkix-java_1.56-1+deb9u2_all.deb
 81b10686b2a8e3d25a0080a2b40b2c3ab588ba3c 1934500 
libbcprov-java-doc_1.56-1+deb9u2_all.deb
 f79f4eb6eb8fad72f785ef926472649341af4d03 3636712 
libbcprov-java_1.56-1+deb9u2_all.deb
Checksums-Sha256:
 06d1564827028cf629d249a54e0072238f48217a7e8f174fc59b2a9aa3cf10fc 2717 
bouncycastle_1.56-1+deb9u2.dsc
 

Processed: severity of 834712 is serious

[Debian Bug Tracking System]

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

> severity 834712 serious
Bug #834712 [freelan] freelan binary is installed to a location different to 
where the sysvinit script expects it
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#898780: marked as done (coffeescript-doc: [RC] embedded code copy of node-normalize.css)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 17:34:06 +
with message-id 
and subject line Bug#898780: fixed in coffeescript 1.12.8~dfsg-1
has caused the Debian Bug report #898780,
regarding coffeescript-doc: [RC] embedded code copy of node-normalize.css
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.)


-- 
898780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:coffeescript-doc
Version: 1.12.7~dfsg-3
Severity: serious
Justification: Policy 4.13

The files:
coffeescript-doc: /usr/share/doc/coffeescript/html/annotated-source/public/
stylesheets/normalize.css
Are embedded copy of node-normalize.css.

Please use the package (maybe using suggest) instead to use local copy

Thanks 

Bastien



signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: coffeescript
Source-Version: 1.12.8~dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated coffeescript package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jun 2018 19:27:14 +0200
Source: coffeescript
Binary: coffeescript libjs-coffeescript coffeescript-doc
Architecture: source all
Version: 1.12.8~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 coffeescript - interpreter and compiler for the CoffeeScript language
 coffeescript-doc - documentation for the CoffeeScript language
 libjs-coffeescript - client-side interpreter for the CoffeeScript language
Closes: 898780
Changes:
 coffeescript (1.12.8~dfsg-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 .
   [ Jonas Smedegaard ]
   * Update Vcs-* fields: Source moved to Salsa.
   * Use https protocol in homepage URL.
   * Update copyright info: Strip needless copyright signs.
   * Update watch file:
 + Use substitution strings.
 + Tighten dversionmangle.
 + Fix typo in watch file usage comment.
   * Strip unused code copies of normalize.css from repackaged source.
 Closes: Bug#898780. Thanks to Bastien ROUCARIÈS.
   * Use package priority optional (not obsolete extra).
   * Declare compliance with Debian Policy 4.1.4.
   * Unfuzz patches.
Checksums-Sha1:
 a3c4e2c5be3c9fb41615c1d82e00d38341418314 2265 coffeescript_1.12.8~dfsg-1.dsc
 5696b34fc47892c5f5059108a50c5c5314a356df 555327 
coffeescript_1.12.8~dfsg.orig.tar.gz
 be62eff15620ff5d051603806d3d498dca54f5d0 13124 
coffeescript_1.12.8~dfsg-1.debian.tar.xz
 fd882b01ae2df59734eef3ceadf3ddcac16f1ec8 201116 
coffeescript-doc_1.12.8~dfsg-1_all.deb
 279566224516e0b099fce6a6b39affdc34fd4acd 141808 
coffeescript_1.12.8~dfsg-1_all.deb
 8af347cc3843200c161e4e14ffc0b7cff55f8ab8 8701 
coffeescript_1.12.8~dfsg-1_amd64.buildinfo
 bbebff302adf59cdc1234f8f805e0ec6fc9eef81 99424 
libjs-coffeescript_1.12.8~dfsg-1_all.deb
Checksums-Sha256:
 4774e6f14fb53ec66e961c475985d372c9c9c351048f45565e79c341fc21f31f 2265 
coffeescript_1.12.8~dfsg-1.dsc
 242b6ccb52d022b034fb9017ca741dd3f24c2ea940cb96540b9bc1fb9d997aab 555327 
coffeescript_1.12.8~dfsg.orig.tar.gz
 fca509261cc9c38d1ef40e23839d5cea75a09138fdd3ee658e74490a94d8ad11 13124 
coffeescript_1.12.8~dfsg-1.debian.tar.xz
 8f10382cfc694e15088b3935d1d1604b7e771cbcd620ca8cb37e104099bacf0f 201116 
coffeescript-doc_1.12.8~dfsg-1_all.deb
 8179e01c78ca391a2c03714bedcc5bafa1b5a75aafecf2bbcccbe8527b54ba0b 141808 
coffeescript_1.12.8~dfsg-1_all.deb
 5ba2f710a47ac4595edd81ed184314886a7415eb7a251b8562552d054180d75f 8701 
coffeescript_1.12.8~dfsg-1_amd64.buildinfo
 32aec24acc8df28b0350e63bf5c894e2784e6127b7cfd159fc7488ea35765de9 99424 
libjs-coffeescript_1.12.8~dfsg-1_all.deb
Files:
 d761530011408bbf69b6a5bcd1bf2f54 2265 devel optional 
coffeescript_1.12.8~dfsg-1.dsc
 18d8308f47ccfe80757d5d3f520fa362 555327 devel optional 
coffeescript_1.12.8~dfsg.orig.tar.gz
 91d8a2a460540574f36a6aa0fadfe12b 13124 devel optional 

Processed: Revert incorrect merge

[Debian Bug Tracking System]

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

> unmerge 57
Bug #57 [src:planner] planner - missing on buster
Bug #876577 [src:planner] planner FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl 
is no longer available
Disconnected #57 from all other report(s).
> severity 57 normal
Bug #57 [src:planner] planner - missing on buster
Severity set to 'normal' from 'serious'
> tags 57 - ftbfs
Bug #57 [src:planner] planner - missing on buster
Removed tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#896253: visionegg is marked for autoremoval from testing

[Andreas Tille]

On Sun, Jun 24, 2018 at 06:19:34PM +0200, Andreas Beckmann wrote:
> 
> Given that this looks pretty much unfixable in stretch, should the
> package be removed from stretch?

ACK - I see no better chance for this.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#888095: marked as done (mariadb-connector-c: ships libmariadb3 version 3.0.3-1, which is lower than the one in mariadb-10.[23])

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 19:51:48 +
with message-id 
and subject line Bug#888095: fixed in mariadb-connector-c 1:3.0.3-2
has caused the Debian Bug report #888095,
regarding mariadb-connector-c: ships libmariadb3 version 3.0.3-1, which is 
lower than the one in mariadb-10.[23]
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.)


-- 
888095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-connector-c
Version: 3.0.3-1
Severity: serious

Hi,

Since 3.0.3-1, mariadb-connector-c ships libmariadb3 at version 3.0.3-1.
However, src:mariadb-10.2 ships libmariadb3_10.2.7-1, and src:mariadb-10.3
(in experimental) ships libmariadb3_10.3.0-0+exp2. Since there's a package
with a higher version in the same suite, mariadb-connector-c is failing
to get installed in the archive, see:

https://buildd.debian.org/status/package.php?p=mariadb-connector-c

Note that it worked on a bunch of architectures, especifically in those
were mariadb-10.2 doesn't ship libmariadb3.

Possible solutions here are:
- Stop shipping libmariadb3 from this source, and let mariadb-10.* ship it
- Ship it here with a higher version (e.g. by incrementing the epoch) and
  stop shipping it from mariadb-10.*

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: mariadb-connector-c
Source-Version: 1:3.0.3-2

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

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-connector-c 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jun 2018 22:18:30 +0300
Source: mariadb-connector-c
Binary: libmariadb-dev libmariadb3 libmariadb-dev-compat
Architecture: source
Version: 1:3.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadb-dev - MariaDB Connector/C, development files
 libmariadb-dev-compat - MariaDB Connector/C, compatibility symlinks
 libmariadb3 - MariaDB Connector/C
Closes: 888095
Changes:
 mariadb-connector-c (1:3.0.3-2) unstable; urgency=medium
 .
   [ Pirate Praveen ]
   * Add epoch to fix "mariadb-connector-c: ships libmariadb3 version 3.0.3-1,
 which is lower than the one in mariadb-10.[23]" (Closes: #888095)
 .
   [ Otto Kekäläinen ]
   * Add upstream signing key
   * Replace all instances of Priority: extra with Priority: optional
   * Use secure https in all urls
Checksums-Sha1:
 5266f24062617798f0c6042e9677452b712b9c01 2224 mariadb-connector-c_3.0.3-2.dsc
 121cadf13b00b97faee9b6e86724f51678d21b51 22612 
mariadb-connector-c_3.0.3-2.debian.tar.xz
 bfb37ffcb607e29feba3b60ceff41695bd32d73c 7655 
mariadb-connector-c_3.0.3-2_source.buildinfo
Checksums-Sha256:
 f7126260ce0fbb4e26e13e875532a28d28f29007e5fb34abc8a05b4816d819fa 2224 
mariadb-connector-c_3.0.3-2.dsc
 e2098e4d48e486e5f3a085b4fe80346eebe28529d9e65da6021261ab356c34a8 22612 
mariadb-connector-c_3.0.3-2.debian.tar.xz
 7ec7692df6b4fa46a79ae0ae24a0386f5e1aa2a9475a200f3e3399c01b74b487 7655 
mariadb-connector-c_3.0.3-2_source.buildinfo
Files:
 08b27011ff6d327f55318e7d5cbcaa89 2224 libs optional 
mariadb-connector-c_3.0.3-2.dsc
 6c07f6ed718529ca3a6d1305615e5cb7 22612 libs optional 
mariadb-connector-c_3.0.3-2.debian.tar.xz
 38ca8a4739e0d5f87f3387ca0f9aa4fd 7655 libs optional 
mariadb-connector-c_3.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAlsv70oACgkQvthEn87o
2og0jw//esVjsl8Fc13r2kGO6GsBouOPzT3S5XyFpb0eRio9bPl3bdx4MAgaHRmr
dNdaHkE3kb1yLXab6lZhgu+1JHwq1ob58vBfn5CcFcWrfHnoV1AupmzzczFuQECI
iI9nYXKIH8xXUmBd4uXTfzKE2kNfYKPproTcZwNzgRR5WgQ29SqEPuGIT81v5jQo
6sb5xB1jufXHBB/KHquGlXjCSS9AboSjBV0CsYMw5wg/YnTviZSXpJ7AYzUPhJxy
x5IzsbEoBC51VoqR9YR3yS0H1PRyRO8GWbpo5MrSuk15GgPWPjpt71egMBkz0zvS
q+SglnB/EKbLm6mSn5EB4H7C9s6VOwaf/15eT31iFPqcSuZWVpR6HQfseJtgKX7O
73wy8XPVNtvXpnluXCA2bvNmI8jhJ9xPOLv0DGwl1t1MZsTA/mm+Lo1uq+Fohqs8
ArJM/iXmOPUQjw++hMzpUfaF2a2FWYv10JnMIa3mnkXOGyXwFSTJcDRZ3D9nO2uB

Bug#902302: connectome-workbench FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

[Yaroslav Halchenko]

Thank you Adrian

Yes, we will proceed the RM way, will deal with it tomorrow

Cheers

On June 24, 2018 2:30:35 PM EDT, Adrian Bunk  wrote:
>Source: connectome-workbench
>Version: 1.3.1-1
>Severity: serious
>
>https://buildd.debian.org/status/package.php?p=connectome-workbench=sid
>
>...
>In file included from
>/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105:0,
>   from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:45,
>from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:38,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
>/usr/include/GLES3/gl32.h:77:25: error: conflicting declaration
>'typedef khronos_ssize_t GLsizeiptr'
> typedef khronos_ssize_t GLsizeiptr;
> ^~
>In file included from /usr/include/GL/gl.h:2055:0,
>from /<>/src/Graphics/CaretOpenGLInclude.h:63,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:33,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
>/usr/include/GL/glext.h:468:19: note: previous declaration as 'typedef
>ptrdiff_t GLsizeiptr'
> typedef ptrdiff_t GLsizeiptr;
>   ^~
>In file included from
>/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105:0,
>   from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:45,
>from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:38,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
>/usr/include/GLES3/gl32.h:78:26: error: conflicting declaration
>'typedef khronos_intptr_t GLintptr'
> typedef khronos_intptr_t GLintptr;
>  ^~~~
>In file included from /usr/include/GL/gl.h:2055:0,
>from /<>/src/Graphics/CaretOpenGLInclude.h:63,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:33,
>from
>/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
>/usr/include/GL/glext.h:469:19: note: previous declaration as 'typedef
>ptrdiff_t GLintptr'
> typedef ptrdiff_t GLintptr;
>   ^~~~
>GuiQt/CMakeFiles/GuiQt.dir/build.make:1423: recipe for target
>'GuiQt/CMakeFiles/GuiQt.dir/moc_BrainOpenGLWidget.cpp.o' failed
>make[3]: *** [GuiQt/CMakeFiles/GuiQt.dir/moc_BrainOpenGLWidget.cpp.o]
>Error 1
>
>
>The problem is that on armel and armhf Qt in Debian uses
>OpenGL ES instead of full OpenGL.
>
>Ideally, connectome-workbench should be fixed to also work with OpenGL
>ES.
>
>If this is not easily possible, then:
>- change the build dependency from libqt5opengl5-dev
>  to libqt5opengl5-desktop-dev, and
>- submit an RM bug against ftp.debian.org asking for
>  the removal of the old armel+armhf binaries

-- 
Sent from a phone which beats iPhone.

Bug#902314: libudev1: Installing libudev1 239-1 removes 48 critical packages

[Jean-Francois Pirus]

Package: libudev1
Version: 239-1
Severity: critical
Tags: d-i
Justification: breaks unrelated software

Dear Maintainer,

Running
apt dist-upgrade
when the only thing being upgraded is
libudev-dev libudev1 libudev1:i386

Removed the following packages, leaving X unuseable, not network, not
mouse,
keyboard etc...
  gvfs-fuse initramfs-tools initramfs-tools-core kpartx libblockdev-
mdraid2
libguestfs-hfsplus libguestfs-perl libguestfs-reiserfs libguestfs-tools
  libguestfs-xfs libguestfs0 linux-image-4.16.0-2-amd64 mdadm nautilus
network-
manager network-manager-gnome network-manager-openvpn
  network-manager-openvpn-gnome pulseaudio-module-bluetooth tlp-rdw
udev
udisks2 upower xfce4-power-manager xfce4-power-manager-plugins
  xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
xserver-
xorg-input-libinput xserver-xorg-input-mouse
  xserver-xorg-input-synaptics xserver-xorg-input-wacom xserver-xorg-
video-
amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev
  xserver-xorg-video-intel xserver-xorg-video-radeon

Also "apt autoremove" was run just before doing this. 

ie:
root@Tosh:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
  bluez-obexd cryptsetup-bin cryptsetup-run db-util easy-rsa extlinux
gdisk
gir1.2-appindicator3-0.1 gvfs-libs hfsplus iputils-arping irqbalance
  klibc-utils ldmtool libafflib0v5 libatasmart4 libbfio1 libblockdev-
crypto2
libblockdev-fs2 libblockdev-loop2 libblockdev-part-err2
  libblockdev-part2 libblockdev-swap2 libblockdev-utils2 libblockdev2
libbytesize1 libconfig9 libdate-manip-perl libegl1-mesa libewf2
libexempi3
  libhfsp0 libhivex0 libintl-perl libintl-xs-perl libklibc libldm-1.0-0 
libndp0
libnfs11 libnm0 libnma0 libpkcs11-helper1 libpython3.6
  libsys-virt-perl libteamdctl0 libtracker-sparql-2.0-0 libtsk13
libudisks2-0
libvolume-key1 libwin-hivex-perl libxfont2 libxml-xpath-perl libyara3
  linux-base lsscsi mobile-broadband-provider-info nautilus-data opensc
opensc-
pkcs11 openvpn scrub sleuthkit supermin udftools
  xfce4-power-manager-data xfonts-100dpi xfonts-75dpi xfonts-base
xfonts-
scalable xserver-common zerofree
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  blueman bluetooth bluez cockpit-networkmanager cockpit-storaged
cryptsetup
cryptsetup-initramfs gnome-disk-utility gvfs gvfs-backends gvfs-daemons
  gvfs-fuse initramfs-tools initramfs-tools-core kpartx libblockdev-
mdraid2
libguestfs-hfsplus libguestfs-perl libguestfs-reiserfs libguestfs-tools
  libguestfs-xfs libguestfs0 linux-image-4.16.0-2-amd64 mdadm nautilus
network-
manager network-manager-gnome network-manager-openvpn
  network-manager-openvpn-gnome pulseaudio-module-bluetooth tlp-rdw
udev
udisks2 upower xfce4-power-manager xfce4-power-manager-plugins
  xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
xserver-
xorg-input-libinput xserver-xorg-input-mouse
  xserver-xorg-input-synaptics xserver-xorg-input-wacom xserver-xorg-
video-
amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev
  xserver-xorg-video-intel xserver-xorg-video-radeon
The following NEW packages will be installed:
  makedev
The following packages will be upgraded:
  libudev-dev libudev1 libudev1:i386
3 upgraded, 1 newly installed, 48 to remove and 0 not upgraded.
Need to get 405 kB of archives.
After this operation, 373 MB disk space will be freed.
Do you want to continue? [Y/n]



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

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

Bug#902279: youtube-dl: FTBFS in buster/sid (No module named 'setuptools')

[Clint Adams]

On Sun, Jun 24, 2018 at 01:59:02PM +0200, Santiago Vila wrote:
>   File "setup.py", line 11, in 
> from setuptools import setup, Command
> ModuleNotFoundError: No module named 'setuptools'

Attached fix uploaded to DELAYED/3-day as part of today's BSP.
diff --git a/debian/changelog b/debian/changelog
index a43539f..6db3181 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+youtube-dl (2018.06.18-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing python3-setuptools build dependency.  closes: #902279.
+
+ -- Clint Adams   Sun, 24 Jun 2018 16:54:30 -0400
+
 youtube-dl (2018.06.18-1) unstable; urgency=medium
 
   * New upstream version 2018.06.18 (Closes: #900642)
diff --git a/debian/control b/debian/control
index 037371e..9bd52ab 100644
--- a/debian/control
+++ b/debian/control
@@ -9,6 +9,7 @@ Build-Depends:
  dh-python,
  pandoc,
  python3-pkg-resources,
+ python3-setuptools,
  zip
 Build-Depends-Indep:
  python3

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 57 src:planner
Bug #57 [planner] planner - missing on buster
Bug reassigned from package 'planner' to 'src:planner'.
No longer marked as found in versions planner/0.14.6-5.
Ignoring request to alter fixed versions of bug #57 to the same values 
previously set
> forcemerge 876577 57
Bug #876577 [src:planner] planner FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl 
is no longer available
Bug #57 [src:planner] planner - missing on buster
Severity set to 'serious' from 'normal'
Marked as found in versions planner/0.14.6-5.
Added tag(s) buster, sid, and ftbfs.
Merged 876577 57
> affects 876577 planner
Bug #876577 [src:planner] planner FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl 
is no longer available
Bug #57 [src:planner] planner - missing on buster
Added indication that 876577 affects planner
Added indication that 57 affects planner
> thanks
Stopping processing here.

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

Processed: cloning 896253, reassign -1 to release.debian.org, severity of -1 is normal, tagging -1 ...

[Debian Bug Tracking System]

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

> clone 896253 -1
Bug #896253 [python-visionegg] python-visionegg: VisionEgg fails to import
Bug 896253 cloned as bug 902310
> reassign -1 release.debian.org
Bug #902310 [python-visionegg] python-visionegg: VisionEgg fails to import
Bug reassigned from package 'python-visionegg' to 'release.debian.org'.
No longer marked as found in versions visionegg/1.2.1-2 and visionegg/1.2.1-4.
Ignoring request to alter fixed versions of bug #902310 to the same values 
previously set
> severity -1 normal
Bug #902310 [release.debian.org] python-visionegg: VisionEgg fails to import
Severity set to 'normal' from 'serious'
> tags -1 = stretch
Bug #902310 [release.debian.org] python-visionegg: VisionEgg fails to import
Removed tag(s) help, upstream, buster, and sid.
> retitle -1 RM: visionegg -- RoQA; unusable; requires no longer available 
> numpy.oldnumeric
Bug #902310 [release.debian.org] python-visionegg: VisionEgg fails to import
Changed Bug title to 'RM: visionegg -- RoQA; unusable; requires no longer 
available numpy.oldnumeric' from 'python-visionegg: VisionEgg fails to import'.
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was a...@debian.org).
> usertags -1 rm
There were no usertags set.
Usertags are now: rm.
> thanks
Stopping processing here.

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

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

[Alexis Murzeau]

Hi,

Le 23/06/2018 à 08:11, Vasudev Kamath a écrit :
> Hi Alexis, Thomas,
> 
> First of all I apologise for not replying in time. I'm bit occupied by
> family work so not getting enough time to deal with package.

That's fine no worries :)
I actually asked you directly because I don't want changes to happen on
your package without your consent or even be unaware of it, that would
be bad.

> 
> Alexis Murzeau  writes:
> 
>>>
>>> I also would like to highlight that what you're describing here is the
>>> workflow of a transition, which is what Debian has been doing for
>>> *years*. Not only this is natural in Debian, but it is also very much
>>> recommended when breakage occurs.
>>>
>>> I'm by the way a bit frustrated that this process is taking so long.
>>> This has a huge impact in the maintenance of a big dozen of my packages,
>>> since Horizon can't be installed. Reverting is really not a lot of work.
>>> Can we get this done soon, as it seems to be the consensus? If the
>>> current font-awesome maintainer is busy, maybe someone else (me?) can do
>>> the work?
> 
> Yes I agree that I should have followed usual transition process but I
> did not imagine a font package breaking things in this manner. Of course
> its not an excuse but I should have been careful, but what is done is
> done now.
> 
>>
>> @Vasudev, what do you think about this ?
>>
>> (As far as I'm concerned, I'm ok with this and Thomas said it shouldn't
>> be a lot of work to do.)
> 
> I've created basic package at ¹. If you or Thomas can adjust the package
> as needed and upload it to archive it would be great. Also please
> consider adding yourself as uploader as I might not have energy to
> maintain additional package.
> 
> ¹ https://salsa.debian.org/fonts-team/fonts-font-awesomev4

Thanks. I think I can help maintaining these packages (v4 and v5) as
streamlink uses them but I'm not a DM (nor a DD).
I think the best is to keep the old source and binary package name
fonts-font-awesome for the old version (v4) and use a new one
fonts-font-awesome-5 for the new version.

So following best practice [0] for what would be a "backward
incompatible ABI change which prevents old programs from working with
the new library" for a library.
So changing the font path to include "-5" and the package name accordingly.

So this would mean:
- revert the fonts-font-awesome package in unstable to 4.7.0~dfsg-3
- either:
  - Clone fonts-font-awesome to fonts-font-awesomev4 then reverting all
branches and tags to v4.7.0~dfsg-3 in fonts-font-awesomev4
  - Or clone fonts-font-awesome to another repository
fonts-font-awesome-5 (to match the source package name) and reset
branches and tags in the fonts-font-awesome repository to v4.7.0~dfsg-3.

My personal thought on repository naming is that its better to have
fonts-font-awesome (4.7.0~dfsg-3) and fonts-font-awesome-5 (5.0.10-4) to
match source package names.

The debian/watch file for fonts-font-awesome (v4) then need to change to
".*/v(4\.\d.*)"[...] to stick with v4.
I've made change in forks at [1] and [2].
Also, I think some changes can be reverted to remove support of v4 in v5
package.

Possibly, reopen bugs that were closed since fonts-font-awesome v5 and
reassign newer ones applying to v5 to the new package fonts-font-awesome-5.

As a side node, I see that font awesome 5 upstream git is in fact the
build result, not the sources (see [4]). But its still free, using CC BY
4.0 for icons, SIL OFL 1.1 for fonts and MIT for anything else (see [3]).
The DFSG requires to have the source code.
Does this mean fonts-font-awesome-5 cannot be handled the same way as
before, ie outside of main ? Not sure as this is not strictly
compiled-only and there are scss, less and non minified js files.


[0] https://wiki.debian.org/TransitionBestPractices
[1] https://salsa.debian.org/amurzeau-guest/fonts-font-awesome-4
[2] https://salsa.debian.org/amurzeau-guest/fonts-font-awesome-5
[3] https://fontawesome.com/license
[4]
https://github.com/FortAwesome/Font-Awesome/issues/12199#issuecomment-363168281

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F





signature.asc
Description: OpenPGP digital signature

Processed: Bug #902306 in libxml-libxml-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902306 [libxml-libxml-perl] FTBFS: xml2-config is gone from libxml2-dev 
from version 2.9.7+dfsg-1
Added tag(s) pending.

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

Bug#902306: Bug #902306 in libxml-libxml-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libxml-libxml-perl/commit/28e5ec206088dd2c0baa05069ea08eeb7cbcac76


Use pkg-config to find xml2 flags instead of xml2-config

which is gone in libxml2-dev 2.9.7.

Thanks: Gerardo Esteban Malazdrewicz for the bug report.
Closes: #902306



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902306

Processed: reassign 898780 to src:coffeescript

[Debian Bug Tracking System]

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

> reassign 898780 src:coffeescript 1.12.7~dfsg-3
Bug #898780 [src:coffeescript-doc] coffeescript-doc: [RC] embedded code copy of 
node-normalize.css
Warning: Unknown package 'src:coffeescript-doc'
Bug reassigned from package 'src:coffeescript-doc' to 'src:coffeescript'.
No longer marked as found in versions coffeescript-doc/1.12.7~dfsg-3.
Ignoring request to alter fixed versions of bug #898780 to the same values 
previously set
Bug #898780 [src:coffeescript] coffeescript-doc: [RC] embedded code copy of 
node-normalize.css
Marked as found in versions coffeescript/1.12.7~dfsg-3.
> thanks
Stopping processing here.

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

Processed: ncftp: diff for NMU version 2:3.2.5-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 874261 + patch
Bug #874261 [src:ncftp] ncftp: ./configure cannot be regenerated from source
Added tag(s) patch.
> tags 874261 + pending
Bug #874261 [src:ncftp] ncftp: ./configure cannot be regenerated from source
Added tag(s) pending.

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

Bug#874261: ncftp: diff for NMU version 2:3.2.5-2.1

[Adrian Bunk]

Control: tags 874261 + patch
Control: tags 874261 + pending

Dear maintainer,

I've prepared an NMU for ncftp (versioned as 2:3.2.5-2.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru ncftp-3.2.5/debian/changelog ncftp-3.2.5/debian/changelog
--- ncftp-3.2.5/debian/changelog	2016-07-02 14:31:26.0 +0300
+++ ncftp-3.2.5/debian/changelog	2018-06-24 17:41:59.0 +0300
@@ -1,3 +1,11 @@
+ncftp (2:3.2.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix sh/autoconfall.sh, based on a fix from Helmut Grohne.
+(Closes: #874261)
+
+ -- Adrian Bunk   Sun, 24 Jun 2018 17:41:59 +0300
+
 ncftp (2:3.2.5-2) unstable; urgency=medium
 
   * acknowledge the NMU: Thanks Jakub and Lucas! closes: #666352
diff -Nru ncftp-3.2.5/debian/patches/autoreconf.patch ncftp-3.2.5/debian/patches/autoreconf.patch
--- ncftp-3.2.5/debian/patches/autoreconf.patch	1970-01-01 02:00:00.0 +0200
+++ ncftp-3.2.5/debian/patches/autoreconf.patch	2018-06-24 17:41:59.0 +0300
@@ -0,0 +1,47 @@
+Description: Fix sh/autoconfall.sh
+Author: Helmut Grohne 
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/874261
+
+--- ncftp-3.2.5.orig/sh/autoconfall.sh
 ncftp-3.2.5/sh/autoconfall.sh
+@@ -1,13 +1,5 @@
+ #!/bin/sh
+ 
+-PROJECT_HOME="$HOME/src/ncftp/current"
+-AUTOCONF_BIN="/usr/local/autoconf-2.13/bin"
+-if [ ! -d "$PROJECT_HOME" ] ; then
+-	/bin/ls -ld "$PROJECT_HOME"
+-	exit 1
+-fi
+-cd "$PROJECT_HOME"
+-
+ a=`pwd`
+ first=yes
+ didone=no
+@@ -16,7 +8,6 @@ for f in \
+ 	sio/configure.in \
+ 	Strn/configure.in \
+ 	libncftp/configure.in \
+-	"$HOME"/src/libncftp/current/libncftp/configure.in \
+ ; do
+ 	abs=no
+ 	case "$f" in
+@@ -32,7 +23,7 @@ for f in \
+ 		is_diff=no
+ 
+ 		/bin/mv config.h.in config.h.in.orig 2>/dev/null
+-		"$AUTOCONF_BIN"/autoheader 2>&1 | fgrep -v AC_TRY_RUN
++		autoheader2.13 2>&1 | fgrep -v AC_TRY_RUN
+ 		if [ ! -f config.h.in ] ; then
+ 			echo "* Warning: config.h.in not generated"
+ 			if [ -f config.h.in.orig ] ; then
+@@ -51,7 +42,7 @@ for f in \
+ 		fi
+ 
+ 		/bin/mv configure configure.orig 2>/dev/null
+-		"$AUTOCONF_BIN"/autoconf 2>&1 | fgrep -v AC_TRY_RUN
++		autoconf2.13 -l autoconf_local 2>&1 | fgrep -v AC_TRY_RUN
+ 		if [ ! -f configure ] ; then
+ 			echo "* Warning: configure not generated"
+ 			if [ -f configure.orig ] ; then
diff -Nru ncftp-3.2.5/debian/patches/series ncftp-3.2.5/debian/patches/series
--- ncftp-3.2.5/debian/patches/series	2016-07-01 20:42:48.0 +0300
+++ ncftp-3.2.5/debian/patches/series	2018-06-24 17:40:13.0 +0300
@@ -1,2 +1,3 @@
 ncftp-352425.patch
 ncftp-reproducible.patch
+autoreconf.patch

Bug#875267: [Debichem-devel] Bug#875267: FTBFS: dpkg-source fails due to changes in upstream source

[Michael Banck]

Hi Drew,

On Sun, Sep 10, 2017 at 01:48:09PM +0800, Drew Parsons wrote:
> nwchem cannot build on its own, since changes are made to some
> upstream files outside of the debian/patches system.
> 
> This is caught during dh_clean in dh_auto_clean built on a pbuilder chroot
> (pdebuild).
> 
> A build log reports:
>   dh_auto_clean
>   make[1]: Leaving directory '/home/drew/projects/scalapack-deps/build/nwchem'
>  dh_autoreconf_clean
>  dh_autotools-dev_restoreconfig
>  dh_clean
>   dpkg-source: info: using source format '3.0 (quilt)'
>   dpkg-source: info: building nwchem using existing 
> ./nwchem_6.6+r27746.orig.tar.bz2
>   dpkg-source: warning: ignoring deletion of file 
> src/nwpw/nwpwlib/D3dB/hilbert.c.bak, use --include-removal to override
>   dpkg-source: warning: ignoring deletion of file 
> src/nwpw/nwpwlib/utilities/paw_utilities/nwpw_gaunt.F.bak, use 
> --include-removal to override
>   dpkg-source: warning: ignoring deletion of file 
> src/nwpw/libraryps/HGH_LDA/C.bak, use --include-removal to override
>   dpkg-source: warning: ignoring deletion of file 
> src/nwpw/libraryps/paw_default/Al.bak, use --include-removal to override
>   dpkg-source: warning: ignoring deletion of file src/atomscf/src.orig, use 
> --include-removal to override
>   dpkg-source: warning: ignoring deletion of file 
> src/tools/ga-5-4/gfutex/examples/scf/twoel.C.orig, use --include-removal to 
> override
>   dpkg-source: warning: ignoring deletion of file 
> src/tools/ga-5-4/comex/src-dmapp/dmapp.h.bak, use --include-removal to 
> override
>   dpkg-source: warning: ignoring deletion of file 
> web/doc/user.4.6/user.html.bak, use --include-removal to override
>   dpkg-source: info: local changes detected, the modified files are:
>nwchem/src/config/NWCHEM_CONFIG
>nwchem/src/config/nwchem_config.h

So I guess all it would take is rm those two files in
dh_override_auto_clean, after the dh_auto_clean?

I have pushed such a change to master now if you would like to test it.
I think I don't see it cause I hacked my dpkg-buildpackage -S to no look
at upstream, bad me.


Michael

Processed: Bug #875267 in nwchem marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #875267 [nwchem] FTBFS: dpkg-source fails due to changes in upstream source
Added tag(s) pending.

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

Bug#875267: Bug #875267 in nwchem marked as pending

[Michael Banck]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debichem-team/nwchem/commit/e21f7b1cedaf5d2c1705aa0f29ffd6ad51842a7d


  * debian/rules (override_dh_auto_clean): Remove
src/config/{NWCHEM_CONFIG,nwchem_config.h} after dh_auto_clean ran
(Closes: #875267).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/875267

Processed: Looks pretty RC to me

[Debian Bug Tracking System]

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

> severity 885918 grave
Bug #885918 [kasumi] Fail to start with UTF-8 anthy dict
Severity set to 'grave' from 'important'
> tags 885918 buster sid
Bug #885918 [kasumi] Fail to start with UTF-8 anthy dict
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#853682: [Debichem-devel] Bug#853682: tiledarray: diff for NMU version 0.6.0-5.2

[Adrian Bunk]

On Sun, Jun 24, 2018 at 06:27:18PM +0200, Graham Inggs wrote:
> Hi Adrian

Hi Graham,

> On 24 June 2018 at 17:44, Adrian Bunk  wrote:
> > I've prepared an NMU for tiledarray (versioned as 0.6.0-5.2) and
> > uploaded it to DELAYED/10. Please feel free to tell me if I should
> > cancel it.
> 
> Thanks for your work on this.  Please upload directly to avoid the
> delay if you wish.

thanks, done.

> Regards
> Graham

cu
Adrian

-- 

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

Bug#902302: connectome-workbench FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

[Adrian Bunk]

Source: connectome-workbench
Version: 1.3.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=connectome-workbench=sid

...
In file included from 
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:45,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:38,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
/usr/include/GLES3/gl32.h:77:25: error: conflicting declaration 'typedef 
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
 ^~
In file included from /usr/include/GL/gl.h:2055:0,
 from /<>/src/Graphics/CaretOpenGLInclude.h:63,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:33,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
/usr/include/GL/glext.h:468:19: note: previous declaration as 'typedef 
ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
   ^~
In file included from 
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:45,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:38,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
/usr/include/GLES3/gl32.h:78:26: error: conflicting declaration 'typedef 
khronos_intptr_t GLintptr'
 typedef khronos_intptr_t GLintptr;
  ^~~~
In file included from /usr/include/GL/gl.h:2055:0,
 from /<>/src/Graphics/CaretOpenGLInclude.h:63,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/../../src/GuiQt/BrainOpenGLWidget.h:33,
 from 
/<>/obj-arm-linux-gnueabihf/GuiQt/moc_BrainOpenGLWidget.cpp:9:
/usr/include/GL/glext.h:469:19: note: previous declaration as 'typedef 
ptrdiff_t GLintptr'
 typedef ptrdiff_t GLintptr;
   ^~~~
GuiQt/CMakeFiles/GuiQt.dir/build.make:1423: recipe for target 
'GuiQt/CMakeFiles/GuiQt.dir/moc_BrainOpenGLWidget.cpp.o' failed
make[3]: *** [GuiQt/CMakeFiles/GuiQt.dir/moc_BrainOpenGLWidget.cpp.o] Error 1


The problem is that on armel and armhf Qt in Debian uses
OpenGL ES instead of full OpenGL.

Ideally, connectome-workbench should be fixed to also work with OpenGL ES.

If this is not easily possible, then:
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev, and
- submit an RM bug against ftp.debian.org asking for
  the removal of the old armel+armhf binaries

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

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 20:53:45 +
with message-id 
and subject line Bug#874004: fixed in ssvnc 1.0.29-4
has caused the Debian Bug report #874004,
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.)


-- 
874004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ssvnc
Version: 1.0.29
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[2]: Entering directory '/build/ssvnc-1.0.29/ultraftp'
javac -target 1.4 -source 1.4 AuthPanel.java ButtonPanel.java 
ClipboardFrame.java DH.java DesCipher.java FTPFrame.java OptionsFrame.java 
RecordingFrame.java RfbProto.java SSLSocketToMe.java SessionRecorder.java 
VncCanvas.java VncViewer.java
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.
Makefile:11: recipe for target 'AuthPanel.class' failed
make[2]: *** [AuthPanel.class] Error 2
make[2]: Leaving directory '/build/ssvnc-1.0.29/ultraftp'

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: ssvnc
Source-Version: 1.0.29-4

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

Debian distribution maintenance software
pp.
Magnus Holmgren  (supplier of updated ssvnc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 19:39:53 +0200
Source: ssvnc
Binary: ssvnc
Architecture: source amd64
Version: 1.0.29-4
Distribution: unstable
Urgency: low
Maintainer: Magnus Holmgren 
Changed-By: Magnus Holmgren 
Description:
 ssvnc  - Enhanced TightVNC viewer with SSL/SSH tunnel helper
Closes: 874004
Changes:
 ssvnc (1.0.29-4) unstable; urgency=low
 .
   * default-jdk-headless is enough to build.
   * Compile java with -source 1.7 -target 1.7 (Closes: #874004).
   * Replace priority extra with optional.
   * Switch to Debhelper compat level 10.
Checksums-Sha1:
 5eff31e802d868f1262205422fd4f4503d71d626 1902 ssvnc_1.0.29-4.dsc
 81bcae27c441c1441555d7cb1b7f959f4c9788d0 11964 ssvnc_1.0.29-4.debian.tar.xz
 907b0cf08c2a8198244244f0f48cb88b9ebeb793 384212 ssvnc-dbgsym_1.0.29-4_amd64.deb
 f8e2115f5a47cf10002b7a8d6894e6eb8a21ed9e 8380 ssvnc_1.0.29-4_amd64.buildinfo
 80648ce7c6a6add17b4cec194a8f48dc69c7f7d7 441300 ssvnc_1.0.29-4_amd64.deb
Checksums-Sha256:
 32569f032ded118ec7d2cfbc28276eb35b1ad74184d5326405533285553c9227 1902 
ssvnc_1.0.29-4.dsc
 22484f66773abf69b4fe984eda0d25e4d998d59ad07c3577bfba5e20a4833ca8 11964 
ssvnc_1.0.29-4.debian.tar.xz
 3d6b43b367656c9b9dbbcff9b8b0a7136b6dacecf203fb187683a97ff2b30178 384212 
ssvnc-dbgsym_1.0.29-4_amd64.deb
 a442e57b316fa6e4ecba42706a1330b5667964f34db3a94c7821b53abeae5a73 8380 
ssvnc_1.0.29-4_amd64.buildinfo
 2237ade6699d488fd41f0b7daa313d340871c51cc3e537152becd771a6899654 441300 
ssvnc_1.0.29-4_amd64.deb
Files:
 55b746afa3c6094e51c223eb539d8a9c 1902 net optional ssvnc_1.0.29-4.dsc
 116b766788e154c4ef0ea2c7c8169ea7 11964 net optional 
ssvnc_1.0.29-4.debian.tar.xz
 daa8e7f147946c0df1ab04436f85942d 384212 debug optional 
ssvnc-dbgsym_1.0.29-4_amd64.deb
 5223bc3d0316fb6b3ce44aef4b9ba734 8380 net optional 
ssvnc_1.0.29-4_amd64.buildinfo
 4c73557cc1387f2a68e8570167af3bd2 441300 net optional 

Bug#902306: marked as done (FTBFS: xml2-config is gone from libxml2-dev from version 2.9.7+dfsg-1)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 21:49:27 +
with message-id 
and subject line Bug#902306: fixed in libxml-libxml-perl 2.0132+dfsg-2
has caused the Debian Bug report #902306,
regarding FTBFS: xml2-config is gone from libxml2-dev from version 2.9.7+dfsg-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.)


-- 
902306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxml-libxml-perl
Version: 2.0132+dfsg-1+b0.01
Severity: grave
Tags: patch upstream

When running debian/rules build:

-
gerardo@alienware:~/apt-src/libxml-libxml-perl-2.0132+dfsg$ ./debian/rules
build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: se entra en el directorio '/home/gerardo/apt-src/libxml-libxml-
perl-2.0132+dfsg'
SKIP_SAX_INSTALL=1 dh_auto_configure
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-
prefix-map=/home/gerardo/apt-src/libxml-libxml-perl-2.0132+dfsg=. -fstack-
protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-
map=/home/gerardo/apt-src/libxml-libxml-perl-2.0132+dfsg=. -fstack-protector-
strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now"
enable native perl UTF8
running xml2-config...didn't manage to get libxml2 config, guessing
options:
  LIBS='-L/usr/local/lib -L/usr/lib -lxml2 -lm'
  INC='-I/usr/local/include -I/usr/include'
If this is wrong, Re-run as:
  $ /usr/bin/perl Makefile.PL LIBS='-L/path/to/lib' INC='-I/path/to/include'

Checking for ability to link against xml2...no
Checking for ability to link against libxml2...libxml2, zlib, and/or the Math
library (-lm) have not been found.
Try setting LIBS and INC values on the command line
Or get libxml2 from
  http://xmlsoft.org/
If you install via RPMs, make sure you also install the -devel
RPMs, as this is where the headers (.h files) are.

Also, you may try to run perl Makefile.PL with the DEBUG=1 parameter
to see the exact reason why the detection of libxml2 installation
failed or why Makefile.PL was not able to compile a test program.
-

The guesses are wrong.

The alternative using pkg-config is available since at least wheezy, so the
attached patch would work in all recent Debian versions.


This patch will be needed until upstream switches to use pkg-config instead of
(now gone) xml2-config.

Thanks,
Gerardo



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

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

Versions of packages libxml-libxml-perl depends on:
ii  libc6 2.27-3
ii  libxml-namespacesupport-perl  1.12-1
ii  libxml-sax-perl   1.00+dfsg-1+b0.01
ii  libxml2   2.9.7+dfsg-1
ii  perl  5.28.0~rc2-1
ii  perl-base [perlapi-5.28.0]5.28.0~rc2-1
ii  zlib1g1:1.2.11.dfsg-1

libxml-libxml-perl recommends no packages.

libxml-libxml-perl suggests no packages.

-- no debconf information
diff -ruN libxml-libxml-perl-2.0132+dfsg/debian/rules 
libxml-libxml-perl-2.0132+dfsg.good/debian/rules
--- libxml-libxml-perl-2.0132+dfsg/debian/rules 2018-06-23 16:57:04.0 
-0300
+++ libxml-libxml-perl-2.0132+dfsg.good/debian/rules2018-06-24 
15:38:12.931247836 -0300
@@ -10,7 +10,9 @@
dh $@
 
 override_dh_auto_configure:
-   SKIP_SAX_INSTALL=1 dh_auto_configure
+   SKIP_SAX_INSTALL=1 dh_auto_configure -- \
+INC=$(shell pkg-config --cflags libxml-2.0) \
+LIBS=$(shell pkg-config --libs libxml-2.0)
 
 override_dh_auto_test:
dh_auto_test -- TEST_FILES="$(TEST_FILES)"
--- End Message ---
--- Begin Message ---
Source: libxml-libxml-perl
Source-Version: 2.0132+dfsg-2

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

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

Thank you for reporting the bug, which will now be closed.  If 

Bug#902218: marked as done (ostree: FTBFS on 64-bit big-endian: test failures: g_str_has_prefix: assertion 'str != NULL' failed)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 15:38:32 +
with message-id 
and subject line Bug#902209: fixed in ostree 2018.6-3
has caused the Debian Bug report #902209,
regarding ostree: FTBFS on 64-bit big-endian: test failures: g_str_has_prefix: 
assertion 'str != NULL' failed
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.)


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

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

...
ERROR: tests/test-find-remotes.sh
=

# testlabel.txt: security.selinux: No such attribute
++ BUILT_WITH_ASAN=
++ test -n ''
++ test -z ''
++ test -z ''
++ CMD_PREFIX='env LD_PRELOAD=/<>/tests/libreaddir-rand.so'
++ test -n /<>
++ OSTREE_HTTPD=/<>/ostree-trivial-httpd
++ _have_user_xattrs=
++ _have_strace_fault_injection=
+ echo 1..1
+ cd /var/tmp/tap-test.U3hurR
+ mkdir apps-collection
+ ostree_repo_init apps-collection --collection-id org.example.AppsCollection
+ repo=apps-collection
+ shift
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=apps-collection init --collection-id org.example.AppsCollection
+ test -n 1
+ echo -e 'disable-xattrs=true\n'
+ mkdir -p files
+ pushd files
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=../apps-collection commit -s 'Test apps-collection commit 1' -b app1 
--gpg-homedir=/var/tmp/tap-test.U3hurR/gpghome --gpg-sign=472CDAFA
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=../apps-collection commit -s 'Test apps-collection commit 2' -b app2 
--gpg-homedir=/var/tmp/tap-test.U3hurR/gpghome --gpg-sign=472CDAFA
+ popd
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=apps-collection summary --update 
--gpg-homedir=/var/tmp/tap-test.U3hurR/gpghome --gpg-sign=472CDAFA
+ mkdir os-collection
+ ostree_repo_init os-collection --collection-id org.example.OsCollection
+ repo=os-collection
+ shift
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=os-collection init --collection-id org.example.OsCollection
+ test -n 1
+ echo -e 'disable-xattrs=true\n'
+ mkdir -p files
+ pushd files
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=../os-collection commit -s 'Test os-collection commit 1' -b 
os/amd64/master --gpg-homedir=/var/tmp/tap-test.U3hurR/gpghome 
--gpg-sign=CA950D41
+ popd
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=os-collection summary --update 
--gpg-homedir=/var/tmp/tap-test.U3hurR/gpghome --gpg-sign=CA950D41
+ mkdir local
+ ostree_repo_init local
+ repo=local
+ shift
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
init
+ test -n 1
+ echo -e 'disable-xattrs=true\n'
++ pwd
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
remote add apps-remote file:///var/tmp/tap-test.U3hurR/apps-collection 
--collection-id org.example.AppsCollection 
--gpg-import=/var/tmp/tap-test.U3hurR/gpghome/key1.asc
++ pwd
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
remote add os-remote file:///var/tmp/tap-test.U3hurR/os-collection 
--collection-id org.example.OsCollection 
--gpg-import=/var/tmp/tap-test.U3hurR/gpghome/key2.asc
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
pull apps-remote app1
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
pull os-remote os/amd64/master
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
refs
+ assert_file_has_content refs '^apps-remote:app1$'
+ fpath=refs
+ shift
+ for re in "$@"
+ grep -q -e '^apps-remote:app1$' refs
+ assert_file_has_content refs '^os-remote:os/amd64/master$'
+ fpath=refs
+ shift
+ for re in "$@"
+ grep -q -e '^os-remote:os/amd64/master$' refs
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
refs --collections
+ cat refs
+ wc -l
+ assert_file_has_content refs '^(org.example.AppsCollection, app1)$'
+ fpath=refs
+ shift
+ for re in "$@"
+ grep -q -e '^(org.example.AppsCollection, app1)$' refs
+ assert_file_has_content refs '^(org.example.OsCollection, os/amd64/master)$'
+ fpath=refs
+ shift
+ for re in "$@"
+ grep -q -e '^(org.example.OsCollection, os/amd64/master)$' refs
+ assert_file_has_content refscount '^2$'
+ fpath=refscount
+ shift
+ for re in "$@"
+ grep -q -e '^2$' refscount
+ mkdir local-mirror
+ ostree_repo_init local-mirror
+ repo=local-mirror
+ shift
+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree 
--repo=local-mirror init
+ test -n 1
+ echo -e 'disable-xattrs=true\n'
++ pwd
+ env 

Bug#902209: marked as done (ostree: FTBFS on 64-bit big-endian: test failures: g_str_has_prefix: assertion 'str != NULL' failed)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 15:38:32 +
with message-id 
and subject line Bug#902209: fixed in ostree 2018.6-3
has caused the Debian Bug report #902209,
regarding ostree: FTBFS on 64-bit big-endian: test failures: g_str_has_prefix: 
assertion 'str != NULL' failed
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.)


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

ostree 2018.6 has test failures on s390x and some ports architectures.
s390x is a representative example:

8<
PASS: tests/test-repo-finder-config 1 /repo-finder-config/init
PASS: tests/test-repo-finder-config 2 /repo-finder-config/no-configs
ERROR: tests/test-repo-finder-config - Bail out! GLib-FATAL-CRITICAL: 
g_str_has_prefix: assertion 'str != NULL' failed

# OSTree-DEBUG: ostree_repo_finder_resolve_all_async: Resolving refs 
[(org.example.Collection0, exampleos/x86_64/ref0), (org.example.Collection0, 
exampleos/x86_64/ref1), (org.example.Collection1, exampleos/x86_64/ref1), 
(org.example.Collection1, exampleos/x86_64/ref2), (org.example.Collection2, 
exampleos/x86_64/ref3)] with finders [OstreeRepoFinderConfig]
# OSTree-DEBUG: ostree_repo_finder_config_resolve_async: Checking 21474836480 
remotes
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref0) 
to remote ?remote0?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref1) 
to remote ?remote0?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref0) 
to remote ?remote0-copy?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref1) 
to remote ?remote0-copy?.
# OSTree-DEBUG: Resolved ref (org.example.Collection1, exampleos/x86_64/ref2) 
to remote ?remote1?.
# OSTree-DEBUG: Ignoring remote ?remote1-bad-copy? due to it not advertising 
any of the requested refs.
# OSTree-DEBUG: Ignoring remote ?remote2? due to no valid collection ID being 
configured for it: Invalid collection ID (null)
Bail out! GLib-FATAL-CRITICAL: g_str_has_prefix: assertion 'str != NULL' failed
ERROR: tests/test-repo-finder-config - Bail out! GLib-FATAL-CRITICAL: 
g_str_has_prefix: assertion 'str != NULL' failed
8<

8<
ERROR: tests/test-find-remotes.sh - too few tests run (expected 1, got 0)
ERROR: tests/test-find-remotes.sh - exited with status 133 (terminated by 
signal 5?)

+ env LD_PRELOAD=/<>/tests/libreaddir-rand.so ostree --repo=local 
find-remotes --finders=config org.example.AppsCollection app1

(ostree find-remotes:20691): GLib-CRITICAL **: 23:37:14.198: g_str_has_prefix: 
assertion 'str != NULL' failed
/<>/tests/test-find-remotes.sh: line 89: 20691 Trace/breakpoint 
trap   ${CMD_PREFIX} ostree --repo=$repo find-remotes --finders=config 
org.example.AppsCollection app1 > find
8<

I've prepared an upload to fix #902194, which will give us a better
picture of which architectures have this test failure. Right now we have:


  little-endian big-endian

32-bitarmel armhf i386 mipsel   mips powerpc(spe) sparc64:
  sh4 x32:  FTBFS: #902194
  FTBFS: #902194

64-bitamd64 arm64 mips64el ppc64el  s390x hppa ppc64:
  alpha ia64 riscv64:   FTBFS: this bug
  successful

which looks suspiciously like correlation with big-endian architectures.
If that theory is correct, arm* i386 mipsel sh4 and x32 will succeed
after #902194 is fixed, but mips powerpc(spe) and sparc64 will continue
to FTBFS due to this bug.

smcv
--- End Message ---
--- Begin Message ---
Source: ostree
Source-Version: 2018.6-3

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated ostree package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 13:04:09 +0100
Source: ostree
Binary: 

Processed: tagging 896896

[Debian Bug Tracking System]

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

> tags 896896 - jessie stretch
Bug #896896 [pidgin-sipe] pidgin-sipe: all buddies are shown "offline"
Removed tag(s) jessie and stretch.
> thanks
Stopping processing here.

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

Processed: gcc-6: internal compiler error in convert_move on arm

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:chromium-browser
Bug #902293 [src:gcc-6] gcc-6: internal compiler error in convert_move on arm
Added indication that 902293 affects src:chromium-browser

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

Bug#853682: [Debichem-devel] Bug#853682: tiledarray: diff for NMU version 0.6.0-5.2

[Graham Inggs]

Hi Adrian

On 24 June 2018 at 17:44, Adrian Bunk  wrote:
> I've prepared an NMU for tiledarray (versioned as 0.6.0-5.2) and
> uploaded it to DELAYED/10. Please feel free to tell me if I should
> cancel it.

Thanks for your work on this.  Please upload directly to avoid the
delay if you wish.

Regards
Graham

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> unarchive 800305
Bug #800305 {Done: Mark Brown } [nis] nis: Please migrate a 
supported debhelper compat level
Bug #831342 {Done: Mark Brown } [nis] nis: FTBFS due 
lacking debhelper compat file
Unarchived Bug 800305
Unarchived Bug 831342
> forcemerge 800305 828750
Bug #800305 {Done: Mark Brown } [nis] nis: Please migrate a 
supported debhelper compat level
Bug #831342 {Done: Mark Brown } [nis] nis: FTBFS due 
lacking debhelper compat file
Bug #828750 [nis] nis: FTBFS
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as fixed in versions nis/3.17-35.
Marked as found in versions nis/3.17-34.
Added tag(s) sid, stretch, and patch.
Bug #831342 {Done: Mark Brown } [nis] nis: FTBFS due 
lacking debhelper compat file
Merged 800305 828750 831342
> thanks
Stopping processing here.

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

Processed: bug 888164 is forwarded to https://github.com/SciRuby/packable/issues/4

[Debian Bug Tracking System]

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

> forwarded 888164 https://github.com/SciRuby/packable/issues/4
Bug #888164 [src:ruby-packable] ruby-packable: FTBFS on ruby2.5: Illegal seek @ 
rb_io_tell
Set Bug forwarded-to-address to 'https://github.com/SciRuby/packable/issues/4'.
> thanks
Stopping processing here.

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

Bug#902227: Krita lead developer has requested Debian cease distributing his software.

[Pino Toscano]

tag 902227 + moreinfo
thanks

Hi anonymous user,

In data sabato 23 giugno 2018 17:13:11 CEST, anondeb...@1337.no ha scritto:
> As per the reddit thread 
> https://www.reddit.com/r/linux/comments/8t2zgc/maintainers_matter_the_case_against_upstream/
>  
> (https://www.reddit.com/r/linux/comments/8t2zgc/maintainers_matter_the_case_against_upstream/),
>  the lead developer of Krita has made it very clear that they want Debian and 
> other distributions to cease packaging Krita unless they can always package 
> the latest version. As this is the wish of upstream, I feel that Debian 
> should immediately honor their wishes and stop packaging Krita, so we can get 
> the vastly superior version that is packaged in their appimage/flatpak, what 
> have you.

I do not see any explicit request in that forum thread.

Boudewijn Rempt knowns already who does most of the packaging work for
Debian (which is me), and how to contact me.  Hence, if he thinks there
are issues with the way Krita is packaged and shipped in Debian, he is
very well welcome to contact the Qt/KDE packaging team and/or me
directly.

I will not do changed based on random interpretations of comments in
some random forum on the Internet made by some random/anonymous nick.

-- 
Pino Toscano

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

Processed: Re: Krita lead developer has requested Debian cease distributing his software.

[Debian Bug Tracking System]

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

> tag 902227 + moreinfo
Bug #902227 [krita] Krita lead developer has requested Debian cease 
distributing his software.
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#902268: debhelper: skips multilib packages when building ncurses

[Niels Thykier]

Niels Thykier:
> Sven Joachim:
>> Package: debhelper
>> Version: 11.3.3
>> Severity: serious
>>
> 
> Hi Sven,
> 
> Are you certain it is introduced in 11.3.3?  The messages / control
> check you highlight is much older than 11.3.3.
> 
>>[...]

Nvm, I reproduced it and I believe the attached patch fixes it.

Thanks,
~Niels

>From 6b8c47d9507381a9813f18aeb9a3ce7b6c07f05f Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sun, 24 Jun 2018 08:20:31 +
Subject: [PATCH] Dh_Lib: Correct assignment of $build_profiles

Signed-off-by: Niels Thykier 
---
 debian/changelog   | 8 
 lib/Debian/Debhelper/Dh_Lib.pm | 2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 3aed2fc1..0671f395 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+debhelper (11.3.4) UNRELEASED; urgency=medium
+
+  * Dh_Lib.pm: Fix bug that made the parser assign the wrong
+value from the Build-Profiles field.  Thanks to Sven Joachim
+for reporting the bug.  (Closes: #902268)
+
+ -- Niels Thykier   Sun, 24 Jun 2018 08:19:16 +
+
 debhelper (11.3.3) unstable; urgency=medium
 
   [ Niels Thykier ]
diff --git a/lib/Debian/Debhelper/Dh_Lib.pm b/lib/Debian/Debhelper/Dh_Lib.pm
index 1bc6c10b..7d4b0115 100644
--- a/lib/Debian/Debhelper/Dh_Lib.pm
+++ b/lib/Debian/Debhelper/Dh_Lib.pm
@@ -1718,7 +1718,7 @@ sub getpackages {
 # because if we work on a package with a Build-Profiles
 # field, then a high enough version of dpkg-dev is needed
 # anyways
-my $build_profiles=$1;
+my $build_profiles = $value;
 eval {
 	require Dpkg::BuildProfiles;
 	my @restrictions=Dpkg::BuildProfiles::parse_build_profiles($build_profiles);
-- 
2.18.0

Processed: notfound 902181 in 11.1-5, found 902181 in 12.0-1

[Debian Bug Tracking System]

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

> notfound 902181 11.1-5
Bug #902181 [pulseaudio] pulseaudio: new pulseaudio update try to remove kde 
stuff
No longer marked as found in versions pulseaudio/11.1-5.
> found 902181 12.0-1
Bug #902181 [pulseaudio] pulseaudio: new pulseaudio update try to remove kde 
stuff
Marked as found in versions pulseaudio/12.0-1.
> thanks
Stopping processing here.

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

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[floris]

What about the following 
/etc/nvidia/current/nvidia-drm-outputclass.conf


---
Section "Files"
ModulePath "/usr/lib/xorg/modules/linux"
ModulePath "/usr/lib/xorg/modules"
EndSection

Section "OutputClass"
Identifier "nvidia"
MatchDriver"nvidia-drm"
Driver "nvidia"
EndSection
---

That seems to work for stable ... what about sid?


Andreas


Hmmm, this should work, but the NVidia glx module will always be loaded 
for all screens by the xserver. This will break a multiseat system with 
multiple gpu vendors and maybe other glvnd dispatch goodness.


Is the following situation a possibility?

Stable -> nvidia-driver (up to version 390.xx in backports), compatible 
with all versions of the xserver
 This version is shipped with a separate Files section in 
nvidia-drm-outputclass.conf
 If xserver 1.20 is in backports, this version can be upgraded to match 
the new Testing/Sid version


Testing and Sid -> nvidia-legacy-390xx-driver, xserver > 1.20
-> nvidia-driver (version > 396.xx), xserver > 1.20
 These versions will have the ModulePath option in the OutputClass 
section. (and we can drop the glx-alternative system)

---
Floris

Bug#902268: marked as done (debhelper: skips multilib packages when building ncurses)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 10:03:55 +
with message-id 
and subject line Bug#902268: fixed in debhelper 11.3.4
has caused the Debian Bug report #902268,
regarding debhelper: skips multilib packages when building ncurses
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.)


-- 
902268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.3.3
Severity: serious

Doing a test build of ncurses, I noticed that the dh_* tools skipped the
multilib packages, resulting in an incomplete build.  This is
reproducible on both i386 and amd64.

,
| $ grep -B1 "All requested packages have been excluded" 
ncurses_6.1+20180210-4_amd64.build
| dh_installdocs -plib32tinfo6
| dh_installdocs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| --
|--link-doc=lib32tinfo6
| dh_installdocs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| --
| dh_makeshlibs -plib32tinfo6 -V "lib32tinfo6 (>= 6.1)" -- -c4
| dh_makeshlibs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| dh_makeshlibs -plib32ncurses6 -V "lib32ncurses6 (>= 6.1)" -- -c4
| dh_makeshlibs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| dh_makeshlibs -plib32ncursesw6 -V "lib32ncursesw6 (>= 6.1)" -- -c4
| dh_makeshlibs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
`

,
| $ grep "in control file but not in files list" 
ncurses_6.1+20180210-4_amd64.build
| dpkg-genchanges: warning: package lib32tinfo6 in control file but not in 
files list
| dpkg-genchanges: warning: package lib32ncurses6 in control file but not in 
files list
| dpkg-genchanges: warning: package lib32ncursesw6 in control file but not in 
files list
| dpkg-genchanges: warning: package lib32ncurses-dev in control file but not in 
files list
`


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf19
ii  dh-strip-nondeterminism  0.042-1
ii  dpkg 1.19.1
ii  dpkg-dev 1.19.1
ii  dwz  0.12-2
ii  file 1:5.33-3
ii  libdpkg-perl 1.19.1
ii  man-db   2.8.3-2
ii  perl 5.26.2-6
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201801

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.3.4

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 09:46:35 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.3.4
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 902268
Changes:
 debhelper (11.3.4) unstable; urgency=medium
 .
   * Dh_Lib.pm: Fix bug that made the parser assign the wrong
 value from the Build-Profiles field.  Thanks to Sven Joachim
 for reporting the bug.  (Closes: #902268)
   * debhelper.pod: Rewrite 

Bug#902268: debhelper: skips multilib packages when building ncurses

[Sven Joachim]

Package: debhelper
Version: 11.3.3
Severity: serious

Doing a test build of ncurses, I noticed that the dh_* tools skipped the
multilib packages, resulting in an incomplete build.  This is
reproducible on both i386 and amd64.

,
| $ grep -B1 "All requested packages have been excluded" 
ncurses_6.1+20180210-4_amd64.build
| dh_installdocs -plib32tinfo6
| dh_installdocs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| --
|--link-doc=lib32tinfo6
| dh_installdocs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| --
| dh_makeshlibs -plib32tinfo6 -V "lib32tinfo6 (>= 6.1)" -- -c4
| dh_makeshlibs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| dh_makeshlibs -plib32ncurses6 -V "lib32ncurses6 (>= 6.1)" -- -c4
| dh_makeshlibs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
| dh_makeshlibs -plib32ncursesw6 -V "lib32ncursesw6 (>= 6.1)" -- -c4
| dh_makeshlibs: All requested packages have been excluded (e.g. via a 
Build-Profile or due to architecture restrictions).
`

,
| $ grep "in control file but not in files list" 
ncurses_6.1+20180210-4_amd64.build
| dpkg-genchanges: warning: package lib32tinfo6 in control file but not in 
files list
| dpkg-genchanges: warning: package lib32ncurses6 in control file but not in 
files list
| dpkg-genchanges: warning: package lib32ncursesw6 in control file but not in 
files list
| dpkg-genchanges: warning: package lib32ncurses-dev in control file but not in 
files list
`


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf19
ii  dh-strip-nondeterminism  0.042-1
ii  dpkg 1.19.1
ii  dpkg-dev 1.19.1
ii  dwz  0.12-2
ii  file 1:5.33-3
ii  libdpkg-perl 1.19.1
ii  man-db   2.8.3-2
ii  perl 5.26.2-6
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201801

-- no debconf information

Bug#902028: libstax2-api-java: FTBFS: The POM for stax:stax-api:jar:debian is missing

[Giovanni Mascellani]

Hi,

thanks for the bug report.

On Thu, 21 Jun 2018 19:43:30 +0200 Andreas Beckmann  wrote:
> Source: libstax2-api-java
> Version: 4.0.0-1
> Severity: serious
> Justification: fails to build from source
> 
> Hi,
> 
> libstax2-api-java/experimental recently started to FTBFS:

Under which environment did you try? I just uploaded a new version to
unstable, and it seems that it is compiling fine on both my computer
(inside an sbuild chroot) and on the official buildd:

 https://buildd.debian.org/status/package.php?p=libstax2-api-java=sid

Could you please confirm if the bug is still there or not?

Thanks, Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles



signature.asc
Description: OpenPGP digital signature

Bug#902268: debhelper: skips multilib packages when building ncurses

[Niels Thykier]

Sven Joachim:
> Package: debhelper
> Version: 11.3.3
> Severity: serious
> 

Hi Sven,

Are you certain it is introduced in 11.3.3?  The messages / control
check you highlight is much older than 11.3.3.

> Doing a test build of ncurses, I noticed that the dh_* tools skipped the
> multilib packages, resulting in an incomplete build.  This is
> reproducible on both i386 and amd64.
> 
> ,
> | $ grep -B1 "All requested packages have been excluded" 
> ncurses_6.1+20180210-4_amd64.build
> | dh_installdocs -plib32tinfo6
> | dh_installdocs: All requested packages have been excluded (e.g. via a 
> Build-Profile or due to architecture restrictions).
> | --
> |--link-doc=lib32tinfo6
> | dh_installdocs: All requested packages have been excluded (e.g. via a 
> Build-Profile or due to architecture restrictions).
> | --
> | dh_makeshlibs -plib32tinfo6 -V "lib32tinfo6 (>= 6.1)" -- -c4
> | dh_makeshlibs: All requested packages have been excluded (e.g. via a 
> Build-Profile or due to architecture restrictions).
> | dh_makeshlibs -plib32ncurses6 -V "lib32ncurses6 (>= 6.1)" -- -c4
> | dh_makeshlibs: All requested packages have been excluded (e.g. via a 
> Build-Profile or due to architecture restrictions).
> | dh_makeshlibs -plib32ncursesw6 -V "lib32ncursesw6 (>= 6.1)" -- -c4
> | dh_makeshlibs: All requested packages have been excluded (e.g. via a 
> Build-Profile or due to architecture restrictions).
> `
> 
> ,
> | $ grep "in control file but not in files list" 
> ncurses_6.1+20180210-4_amd64.build
> | dpkg-genchanges: warning: package lib32tinfo6 in control file but not in 
> files list
> | dpkg-genchanges: warning: package lib32ncurses6 in control file but not in 
> files list
> | dpkg-genchanges: warning: package lib32ncursesw6 in control file but not in 
> files list
> | dpkg-genchanges: warning: package lib32ncurses-dev in control file but not 
> in files list
> `
> 
> 
> [...]
Thanks,
~Niels

Processed: bug control information for src:fetchmail

[Debian Bug Tracking System]

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

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

> found 768843 6.3.21-4
Bug #768843 {Done: Laszlo Boszormenyi (GCS) } [fetchmail] 
fetchmail: Improved TLS support
Marked as found in versions fetchmail/6.3.21-4.
> found 768843 6.3.26-1
Bug #768843 {Done: Laszlo Boszormenyi (GCS) } [fetchmail] 
fetchmail: Improved TLS support
Marked as found in versions fetchmail/6.3.26-1.
> fixed 798803 6.4.0~beta4-1
Bug #798803 [fetchmail] fetchmail: Slowness when .fetchids file grows large
Marked as fixed in versions fetchmail/6.4.0~beta4-1.
>
End of message, stopping processing here.

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

Bug#902264: marked as done (dictd: post-installation fails)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 08:34:08 +
with message-id 
and subject line Bug#902264: fixed in dictd 1.12.1+dfsg-6
has caused the Debian Bug report #902264,
regarding dictd: post-installation fails
to be marked as done.

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

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


-- 
902264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dictd
Version: 1.12.1+dfsg-5
Severity: grave
Justification: renders package unusable

I got the following error during the installation:

E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up dictd (1.12.1+dfsg-5) ...
insserv: warning: current stop runlevel(s) (1) of script `dictd' overrides LSB 
defaults (0 1 6).
Job for dictd.service failed because the control process exited with error code.
See "systemctl status dictd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dictd, action "restart" failed.
● dictd.service - LSB: Start and stop dictionary server daemon
   Loaded: loaded (/etc/init.d/dictd; generated)
   Active: failed (Result: exit-code) since Sun 2018-06-24 00:14:29 EDT; 5ms ago
 Docs: man:systemd-sysv-generator(8)
  Process: 27093 ExecStart=/etc/init.d/dictd start (code=exited, 
status=1/FAILURE)

Jun 24 00:14:29 zira systemd[1]: Starting LSB: Start and stop dictionary server 
daemon...
Jun 24 00:14:29 zira dictd[27093]: Starting dictionary server: dictd failed!
Jun 24 00:14:29 zira systemd[1]: dictd.service: Control process exited, 
code=exited status=1
Jun 24 00:14:29 zira systemd[1]: dictd.service: Failed with result 'exit-code'.
Jun 24 00:14:29 zira systemd[1]: Failed to start LSB: Start and stop dictionary 
server daemon.
dpkg: error processing package dictd (--configure):
 installed dictd package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 dictd

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

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

Versions of packages dictd depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.67
ii  dictzip1.12.1+dfsg-5
ii  libc6  2.27-3
ii  libmaa41.4.2-1
ii  lsb-base   9.20170808
ii  netbase5.4
ii  ucf3.0038
ii  update-inetd   4.45
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages dictd recommends:
ii  dict [dict-client]  1.12.1+dfsg-5

Versions of packages dictd suggests:
ii  dict-foldoc [dictd-dictionary]20170105-1
ii  dict-freedict-eng-fra [dictd-dictionary]  2016.12.12-1
ii  dict-freedict-fra-eng [dictd-dictionary]  2016.12.12-1
ii  dict-gcide [dictd-dictionary] 0.48.4
ii  dict-jargon [dictd-dictionary]4.4.7-3
ii  dict-vera [dictd-dictionary]  1:1.23-1
ii  dict-wn [dictd-dictionary]1:3.0-35

-- debconf information:
  dictd/run_mode: daemon
--- End Message ---
--- Begin Message ---
Source: dictd
Source-Version: 1.12.1+dfsg-6

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

Debian distribution maintenance software
pp.
Robert Luberda  (supplier of updated dictd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 10:19:13 +0200
Source: dictd
Binary: dictd dict dictzip dictfmt
Architecture: source amd64
Version: 1.12.1+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda 
Changed-By: Robert Luberda 
Description:
 dict   - dictionary client
 dictd  - dictionary server
 dictfmt- utility to format a file for use by a dictd server
 dictzip- compression utility 

Bug#902268: debhelper: skips multilib packages when building ncurses

[Sven Joachim]

On 2018-06-24 08:22 +, Niels Thykier wrote:

> Niels Thykier:
>> Sven Joachim:
>>> Package: debhelper
>>> Version: 11.3.3
>>> Severity: serious
>>>
>> 
>> Hi Sven,
>> 
>> Are you certain it is introduced in 11.3.3?  The messages / control
>> check you highlight is much older than 11.3.3.
>> 
>>>[...]
>
> Nvm, I reproduced it and I believe the attached patch fixes it.

Yes, that works. :-)

Cheers,
   Sven

Bug#902318: monkeysphere: testsuite ssh config contains invalid option

[Clint Adams]

Package: monkeysphere
Version: 0.41-1
Severity: serious
Tags: patch

RSAAuthentication has been removed from OpenSSH, and therefore using it
tests/home/testuser/.ssh/config contributes to testsuite failure
>From 91ffa734a9d3ce695c85b24d0f418ce3939ed592 Mon Sep 17 00:00:00 2001
From: Clint Adams 
Date: Sun, 24 Jun 2018 19:02:07 -0400
Subject: [PATCH] Remove RSAAuthentication from test ssh config

---
 tests/home/testuser/.ssh/config | 1 -
 1 file changed, 1 deletion(-)

diff --git a/tests/home/testuser/.ssh/config b/tests/home/testuser/.ssh/config
index ab1efa6..8c1e9bb 100644
--- a/tests/home/testuser/.ssh/config
+++ b/tests/home/testuser/.ssh/config
@@ -3,7 +3,6 @@ Host *
 ChallengeResponseAuthentication no
 PasswordAuthentication no
 KbdInteractiveAuthentication no
-RSAAuthentication no
 GSSAPIAuthentication no
 StrictHostKeyChecking yes
 LogLevel DEBUG
-- 
2.18.0

Processed: owner 902317

[Debian Bug Tracking System]

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

> owner 902317 tmanc...@debian.org
Bug #902317 [src:disruptor] disruptor: FTBFS with openjdk-10-jdk - package 
sun.misc does not exist
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Processed: Re: python-surfer: surfer fails to import

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896208 {Done: Adrian Bunk } [python-surfer] 
python-surfer: surfer fails to import
Added tag(s) pending.

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

Bug#896208: python-surfer: surfer fails to import

[Andreas Beckmann]

Followup-For: Bug #896208
Control: tag -1 pending

stretch-pu request: https://bugs.debian.org/902325


Andreas

Bug#899060: FTBFS: even if tests pass, dh_auto_test fails

[Adam Borowski]

On Mon, Jun 25, 2018 at 12:55:29AM +, Clint Adams wrote:
> On Fri, May 18, 2018 at 08:40:56PM +0200, Adam Borowski wrote:
> > ##
> >  Monkeysphere basic tests completed successfully!
> > ##
> > ### removing temp dir...
> > make[1]: Leaving directory '/<>'
> > dh_auto_test: make -j2 -Oline test returned exit code 2
> 
> Does it happen without -j2?

You can't just remove that, as in absence of any parallelism settings,
modern dh level take the number of available CPUs.  So you need explicit
DEB_BUILD_OPTIONS=parallel=1 to get -j1.

With such a single-threaded build, the test suite fails much sooner; in
every case it dies on the first test it does.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ There's an easy way to tell toy operating systems from real ones.
⣾⠁⢰⠒⠀⣿⡁ Just look at how their shipped fonts display U+1F52B, this makes
⢿⡄⠘⠷⠚⠋⠀ the intended audience obvious.  It's also interesting to see OSes
⠈⠳⣄ go back and forth wrt their intended target.

Processed: Re: python-fastkml: fastkml fails to import

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896393 {Done: Sandro Tosi } [python-fastkml] 
python-fastkml: fastkml fails to import
Added tag(s) pending.
> tag 896232 pending
Bug #896232 {Done: Sandro Tosi } [python3-fastkml] 
python3-fastkml: fastkml fails to import
Added tag(s) pending.

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

Bug#896393: python-fastkml: fastkml fails to import

[Andreas Beckmann]

Followup-For: Bug #896393
Control: tag -1 pending
Control: tag 896232 pending

stretch-pu request: https://bugs.debian.org/902326


Andreas

Processed: found 896358 in 0.2.0-1, found 896385 in 0.2.0-1, tagging 867914, unarchiving 867439 ...

[Debian Bug Tracking System]

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

> found 896358 0.2.0-1
Bug #896358 [python3-flask-rdf] python3-flask-rdf: flask_rdf fails to import
Marked as found in versions python-flask-rdf/0.2.0-1.
> found 896385 0.2.0-1
Bug #896385 [python-flask-rdf] python-flask-rdf: flask_rdf fails to import
Marked as found in versions python-flask-rdf/0.2.0-1.
> tags 867914 + pending
Bug #867914 {Done: Adrian Bunk } [psad] psad: should depend on 
net-tools and iproute2
Added tag(s) pending.
> unarchive 867439
Bug #867439 {Done: Andreas Beckmann } [python3-mimeparse] 
python3-mimeparse: missing dependencies
Unarchived Bug 867439
> fixed 867439 0.1.4-1+deb8u1
Bug #867439 {Done: Andreas Beckmann } [python3-mimeparse] 
python3-mimeparse: missing dependencies
Marked as fixed in versions python-mimeparse/0.1.4-1+deb8u1.
> thanks
Stopping processing here.

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

Bug#867413: python3-pylint-django: incorrect dependencies

[Andreas Beckmann]

Followup-For: Bug #867413
Control: tag -1 pending

stretch-pu request: https://bugs.debian.org893543


Andreas

Processed: Re: python3-pylint-django: incorrect dependencies

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #867413 {Done: Joseph Herlant } [python3-pylint-django] 
python3-pylint-django: incorrect dependencies
Added tag(s) pending.

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

Bug#902330: timidity: daemon excludes pulseaudio daemon from using audio cards

[Ivan Vilata i Balaguer]

Package: timidity
Version: 2.14.0-3
Severity: critical
Justification: breaks unrelated software

Hi there!  After the last update and reboot of my Sid system, I could no
longer hear sound output from any application.  I'm running per-user
PulseAudio, and ``pavucontrol`` said that no audio cards were being detected,
showing only a fake sink device.  The card was reported in ``dmesg``,
``lspi``, ``lsmod`` and ``alsamixer`` though.

Running ``fuser /dev/snd/*`` showed only the Timidity daemon having
``/dev/snd/controlC0`` open.  Stopping the Timidity daemon seemed to fix the
issue and running ``pavucontrol`` again reported the physical card.  Actually
I was then able to start the Timidity daemon again successfully without
breaking things.

Restarting the system made the Timidity daemon hold the card again until it
was stopped, so I stopped and disabled the daemon as a temporary workaround.

As I mentioned, this happened after a recent update and reboot, so the issue
may have been introduced by some update during June 2018.

Thank you very much!

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

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

Versions of packages timidity depends on:
ii  libasound21.1.6-1
ii  libaudio2 1.9.4-6
ii  libc6 2.27-3
ii  libflac8  1.3.2-3
ii  libice6   2:1.0.9-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2
ii  libncurses6   6.1+20180210-4
ii  libogg0   1.3.2-1+b1
ii  libpng16-16   1.6.34-1
ii  libsm62:1.2.2-1+b3
ii  libspeex1 1.2~rc1.2-1+b2
ii  libtinfo6 6.1+20180210-4
ii  libvorbis0a   1.3.6-1
ii  libvorbisenc2 1.3.6-1
ii  libx11-6  2:1.6.5-1
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  lsb-base  9.20170808
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages timidity recommends:
ii  fluid-soundfont-gm  3.1-5.1
ii  timidity-daemon 2.14.0-3

Versions of packages timidity suggests:
ii  fluid-soundfont-gs  3.1-5.1
ii  freepats20060219-1
ii  pmidi   1.7.1-1

-- no debconf information

Bug#842393: thefuck: Missing dependency on python-pkg-resources

[Andreas Beckmann]

Followup-For: Bug #842393
Control: tag -1 pending

stretch-pu request: https://bugs.debian.org/902319


Andreas

Bug#872039: why the severity?

[Cameron Norman]

On Fri, 12 Jan 2018 03:56:42 +0100 Adam Borowski 
wrote:
> On Wed, Jan 10, 2018 at 08:38:39PM +0100, John Paul Adrian Glaubitz wrote:
> > > Please tell me why this would be serious: any filesystem from this
millenium
> > > can handle unclean shutdown fine -- especially if there's a sync
before
> > > reboot/poweroff.
> >
> > That's hardly an argument. There is still very much the possibility that
> > this bug causes data-loss, so the severity is definitely justified.
>
> Technically, yes.  If your filesystem is ext2, and there's a process that
> hasn't been killed, and continues to write after the final sync.
>
> But if you use ext2 for anything, you made the decision yourself.
>

Not necessarily, an admin could just have to use ext2 for internal company
policy reasons.

Let's not punish people for being stuck in a bad situation.

/usr is already mounted ro. Can we not remount other filesystems ro like
/var at the same time?

> > On the other hand, only a very small minority are still using sysvinit
on
> > Debian, so this I think it's ok to have the severity set to serious.
>
> According to my last data, 14% of unstable users; less on stable as those
> tend to be non-technical users.  Not a "very small minority".

Ignore him. He trolls non-systemd inits and actively roots for their exit
from Debian.

Regards,
--
Cameron nemo

Bug#853682: tiledarray: diff for NMU version 0.6.0-5.2

[Adrian Bunk]

Dear maintainer,

I've prepared an NMU for tiledarray (versioned as 0.6.0-5.2) and 
uploaded it to DELAYED/10. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

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

diff -Nru tiledarray-0.6.0/debian/changelog tiledarray-0.6.0/debian/changelog
--- tiledarray-0.6.0/debian/changelog	2018-04-20 23:20:04.0 +0300
+++ tiledarray-0.6.0/debian/changelog	2018-06-24 13:38:23.0 +0300
@@ -1,3 +1,15 @@
+tiledarray (0.6.0-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with less debug info on 32bit to workaround
+the virtual address space limitation.
+  * Fix the accidental disabling of compiler optimization
+on mips* in 0.6.0-2.
+  * Remove flags from the pkg-config Cflags/Libs that don't
+belong there.
+
+ -- Adrian Bunk   Sun, 24 Jun 2018 13:38:23 +0300
+
 tiledarray (0.6.0-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru tiledarray-0.6.0/debian/patches/pkgconfig-flags.patch tiledarray-0.6.0/debian/patches/pkgconfig-flags.patch
--- tiledarray-0.6.0/debian/patches/pkgconfig-flags.patch	1970-01-01 02:00:00.0 +0200
+++ tiledarray-0.6.0/debian/patches/pkgconfig-flags.patch	2018-06-24 13:38:23.0 +0300
@@ -0,0 +1,13 @@
+Description: Remove flags from the pkg-config file that don't belong there
+Author: Adrian Bunk 
+
+--- tiledarray-0.6.0.orig/tiledarray.pc.in
 tiledarray-0.6.0/tiledarray.pc.in
+@@ -2,5 +2,5 @@ Name: tiledarray
+ Description: A modern C++ library for block-sparse tensor computation
+ Version: @TILEDARRAY_VERSION@
+ URL: https://github.com/ValeevGroup/tiledarray
+-Cflags: -I@CMAKE_INSTALL_PREFIX@/include @CMAKE_CXX_FLAGS@ @TiledArray_PC_CFLAGS@
+-Libs: -L@CMAKE_INSTALL_PREFIX@/lib @CMAKE_EXE_LINKER_FLAGS@  @TiledArray_PC_LIBS@
++Cflags: -I@CMAKE_INSTALL_PREFIX@/include @TiledArray_PC_CFLAGS@
++Libs: -L@CMAKE_INSTALL_PREFIX@/lib @TiledArray_PC_LIBS@
diff -Nru tiledarray-0.6.0/debian/patches/series tiledarray-0.6.0/debian/patches/series
--- tiledarray-0.6.0/debian/patches/series	2018-04-20 23:11:11.0 +0300
+++ tiledarray-0.6.0/debian/patches/series	2018-06-24 13:38:23.0 +0300
@@ -1 +1,2 @@
 specialization-after-instantiation.patch
+pkgconfig-flags.patch
diff -Nru tiledarray-0.6.0/debian/rules tiledarray-0.6.0/debian/rules
--- tiledarray-0.6.0/debian/rules	2017-01-14 00:37:27.0 +0200
+++ tiledarray-0.6.0/debian/rules	2018-06-24 13:38:23.0 +0300
@@ -19,9 +19,13 @@
 include /usr/share/dpkg/architecture.mk
 
 ifneq (,$(findstring mips,$(DEB_TARGET_ARCH)))
-  CXX_FLAGS="$(shell pkg-config --cflags-only-I mpi) -mxgot"
+  CXXFLAGS+=$(shell pkg-config --cflags-only-I mpi) -g0 -mxgot
 else
-  CXX_FLAGS="$(shell pkg-config --cflags-only-I mpi)"
+  ifeq (32,$(DEB_HOST_ARCH_BITS))
+CXXFLAGS+=$(shell pkg-config --cflags-only-I mpi) -g1
+  else
+CXXFLAGS+=$(shell pkg-config --cflags-only-I mpi)
+  endif
 endif
 EXE_LINKER_FLAGS="$(shell pkg-config --libs-only-l mpi)"
 ifneq (,$(filter $(DEB_TARGET_ARCH),mips64el))
@@ -41,7 +45,7 @@
 		-DTA_BUILD_UNITTEST=ON\
 		-DTA_ERROR="throw"\
 		-DENABLE_SHARED_LIBRARIES=OFF			\
-		-DCMAKE_CXX_FLAGS=${CXX_FLAGS}			\
+		-DCMAKE_CXX_FLAGS="${CXXFLAGS}"			\
 		-DCMAKE_EXE_LINKER_FLAGS=${EXE_LINKER_FLAGS}
 
 override_dh_auto_build:

Bug#902293: gcc-6: internal compiler error in convert_move on arm

[Michael Gilbert]

package: src:gcc-6
version: 6.4.0-18
severity: grave
control: affects -1 src:chromium-browser
forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86166

This was marked as a duplicate upstream and closed, but it seems like
it should be considered a separate issue.

The latest chromium upload now fails because of this [0] (using gcc
6.4.0-18, which includes the fix for #901290).

Best wishes,
Mike

[0]https://buildd.debian.org/status/fetch.php?pkg=chromium-browser=arm64=68.0.3440.17-1=1529836062=0

Bug#902281: libgsl23: ABI breakage due to removed symbols

[Dirk Eddelbuettel]

On 24 June 2018 at 08:51, Dirk Eddelbuettel wrote:
| 
| On 24 June 2018 at 08:38, Dirk Eddelbuettel wrote:
| | 
| | But nomatter what I do, I end up with
| | 
| |   W: libgsl24: package-name-doesnt-match-sonames libgsl23 
| | 
| | ie the library built by upstream is built as libgsl.so.23.1.0 -- even though
| | upstream configure.ac has a long comment header ending in 
| | 
| |   dnl gsl-2.5libgsl 24:0:1   libgslcblas 0:0:0 
| | 
| | as well as
| | 
| |   GSL_CURRENT=24
| |   GSL_REVISION=0
| |   GSL_AGE=1
| | 
| |   [...]
| | 
| |   GSL_LT_VERSION="${GSL_CURRENT}:${GSL_REVISION}:${GSL_AGE}"
| |   AC_SUBST(GSL_LT_VERSION)
| | 
| | I am stumped.  Why does the '24' version not get through?
| 
| Looks like upstream builds as libgsl.23.1.0 based on a quick build in Docker:
| 
| root@fcae44906b06:/tmp/gsl/gsl-2.5# ls -ltr /usr/local/lib/   
   
| total 35064 
| -rwxr-xr-x 1 root root  1097936 Jun 24 13:45 libgslcblas.so.0.0.0 
   
| lrwxrwxrwx 1 root root   20 Jun 24 13:45 libgslcblas.so.0 -> 
libgslcblas.so.0.0.0
| lrwxrwxrwx 1 root root   20 Jun 24 13:45 libgslcblas.so -> 
libgslcblas.so.0.0.0  
| -rwxr-xr-x 1 root root  949 Jun 24 13:45 libgslcblas.la   
   
| -rw-r--r-- 1 root root  1884714 Jun 24 13:45 libgslcblas.a
   
| -rwxr-xr-x 1 root root 12038200 Jun 24 13:45 libgsl.so.23.1.0 
   
| lrwxrwxrwx 1 root root   16 Jun 24 13:45 libgsl.so.23 -> libgsl.so.23.1.0 
   
| lrwxrwxrwx 1 root root   16 Jun 24 13:45 libgsl.so -> libgsl.so.23.1.0
   
| -rwxr-xr-x 1 root root  918 Jun 24 13:45 libgsl.la
   
| -rw-r--r-- 1 root root 20858130 Jun 24 13:45 libgsl.a 
   
| drwxr-xr-x 2 root root 4096 Jun 24 13:45 pkgconfig
   
| root@fcae44906b06:/tmp/gsl/gsl-2.5#   
| 
| What should we do here? We can't stay at 23 as that was an issue which lead
| to your original bug report.  We probably should not use 24 which may come
| next. Shall we do libgsl23-1 ?

I emailed upstream, but the mail seems lost or stuck as it does not yet
appear in their list archives at https://cygwin.com/ml/gsl-discuss/2018-q2/

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#875268: marked as done (nwchem: update BLACS configuration for scalapack 2)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 18:21:40 +
with message-id 
and subject line Bug#875268: fixed in nwchem 6.8+47+gitdf6c956-2
has caused the Debian Bug report #875268,
regarding nwchem: update BLACS configuration for scalapack 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.)


-- 
875268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nwchem
Version: 6.6+r27746-4
Severity: normal

scalapack 2 is now available in unstable. It includes BLACS, so
libblacs-mpi-dev is now deprecated and must be removed from
Build-Depends.

Please update nwchem:

debian/control:
Build-Depends: autotools-dev (>> 20100122.1~),
   csh,
   debhelper (>= 7.0.50~),
   gfortran,
   libblas-dev,
   liblapack-dev,
   libscalapack-mpi-dev (>= 2),
   mpi-default-bin,
   mpi-default-dev,
   openssh-client,
   pkg-config,
   python-dev (>= 2.6.6-3~),
   texlive-latex-base,
   zlib1g-dev

debian/rules:
export BLACS=-lscalapack-$(ARCH_DEFAULT_MPI_IMPL)


(I can't upload an nmu because of bug#875267, sorry!)


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

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

Versions of packages nwchem depends on:
ii  libatlas3-base [liblapack.so.3]3.10.3-4
ii  libblas3 [libblas.so.3]3.7.1-3
ii  libc6  2.24-17
ii  libgcc11:7.2.0-4
ii  libgfortran3   6.4.0-5
ii  liblapack3 [liblapack.so.3]3.7.1-3
ii  libopenblas-base [liblapack.so.3]  0.2.20+ds-3
ii  libopenmpi22.1.1-6+b1
ii  libpython2.7   2.7.13-4
ii  libquadmath0   7.2.0-4
ii  mpi-default-bin1.9
ii  nwchem-data6.6+r27746-4
ii  zlib1g 1:1.2.8.dfsg-5

nwchem recommends no packages.

nwchem suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nwchem
Source-Version: 6.8+47+gitdf6c956-2

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated nwchem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 20:04:18 +0200
Source: nwchem
Binary: nwchem nwchem-data
Architecture: source
Version: 6.8+47+gitdf6c956-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 nwchem - High-performance computational chemistry software
 nwchem-data - High-performance computational chemistry software (data files)
Closes: 722511 875267 875268
Changes:
 nwchem (6.8+47+gitdf6c956-2) unstable; urgency=medium
 .
   [ Drew Parsons ]
   * Remove Build-Depends: libblacs-mpi-dev, instead use versioned
 Build-Depends: libscalapack-mpi-dev (>= 2).
 BLACS is now included in SCALAPACK 2. Closes: #875268.
 .
   [ Michael Banck ]
   * debian/rules (DEB_HOST_GNU_TYPE): New variable.
   * debian/rules (MPI_INCLUDE): update MPI include path with
 $DEB_HOST_GNU_TYPE.
   * debian/rules (NWCHEM_LONG_PATHS): New variable, should allow for longer
 paths (Closes: #722511).
   * debian/rules (override_dh_auto_clean): Remove
 src/config/{NWCHEM_CONFIG,nwchem_config.h} after dh_auto_clean ran
 (Closes: #875267).
Checksums-Sha1:
 3aa6f9fc5ab68e0af630157b4777d6fec0b5cc1c 2234 nwchem_6.8+47+gitdf6c956-2.dsc
 5984c421666c2f06f2f4886965cb27044da30178 20412 
nwchem_6.8+47+gitdf6c956-2.debian.tar.xz
 485ee3f74f5455b52b63461acf77cba5eb9dd2f7 7786 

Bug#875267: marked as done (FTBFS: dpkg-source fails due to changes in upstream source)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 18:21:40 +
with message-id 
and subject line Bug#875267: fixed in nwchem 6.8+47+gitdf6c956-2
has caused the Debian Bug report #875267,
regarding FTBFS: dpkg-source fails due to changes in upstream source
to be marked as done.

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

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


-- 
875267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nwchem
Version: 6.6+r27746-4
Severity: normal

nwchem cannot build on its own, since changes are made to some
upstream files outside of the debian/patches system.

This is caught during dh_clean in dh_auto_clean built on a pbuilder chroot
(pdebuild).

A build log reports:
  dh_auto_clean
  make[1]: Leaving directory '/home/drew/projects/scalapack-deps/build/nwchem'
 dh_autoreconf_clean
 dh_autotools-dev_restoreconfig
 dh_clean
  dpkg-source: info: using source format '3.0 (quilt)'
  dpkg-source: info: building nwchem using existing 
./nwchem_6.6+r27746.orig.tar.bz2
  dpkg-source: warning: ignoring deletion of file 
src/nwpw/nwpwlib/D3dB/hilbert.c.bak, use --include-removal to override
  dpkg-source: warning: ignoring deletion of file 
src/nwpw/nwpwlib/utilities/paw_utilities/nwpw_gaunt.F.bak, use 
--include-removal to override
  dpkg-source: warning: ignoring deletion of file 
src/nwpw/libraryps/HGH_LDA/C.bak, use --include-removal to override
  dpkg-source: warning: ignoring deletion of file 
src/nwpw/libraryps/paw_default/Al.bak, use --include-removal to override
  dpkg-source: warning: ignoring deletion of file src/atomscf/src.orig, use 
--include-removal to override
  dpkg-source: warning: ignoring deletion of file 
src/tools/ga-5-4/gfutex/examples/scf/twoel.C.orig, use --include-removal to 
override
  dpkg-source: warning: ignoring deletion of file 
src/tools/ga-5-4/comex/src-dmapp/dmapp.h.bak, use --include-removal to override
  dpkg-source: warning: ignoring deletion of file 
web/doc/user.4.6/user.html.bak, use --include-removal to override
  dpkg-source: info: local changes detected, the modified files are:
   nwchem/src/config/NWCHEM_CONFIG
   nwchem/src/config/nwchem_config.h
  dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/nwchem_6.6+r27746-4.1.diff.peJn2P
  dpkg-source: info: you can integrate the local changes with dpkg-source 
--commit

I tested after setting debian/compat to 10, so this new FTBFS may be a
consequence of debhelper 10.


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

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

Versions of packages nwchem depends on:
ii  libatlas3-base [liblapack.so.3]3.10.3-4
ii  libblas3 [libblas.so.3]3.7.1-3
ii  libc6  2.24-17
ii  libgcc11:7.2.0-4
ii  libgfortran3   6.4.0-5
ii  liblapack3 [liblapack.so.3]3.7.1-3
ii  libopenblas-base [liblapack.so.3]  0.2.20+ds-3
ii  libopenmpi22.1.1-6+b1
ii  libpython2.7   2.7.13-4
ii  libquadmath0   7.2.0-4
ii  mpi-default-bin1.9
ii  nwchem-data6.6+r27746-4
ii  zlib1g 1:1.2.8.dfsg-5

nwchem recommends no packages.

nwchem suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nwchem
Source-Version: 6.8+47+gitdf6c956-2

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated nwchem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jun 2018 20:04:18 +0200
Source: nwchem
Binary: nwchem nwchem-data
Architecture: 

Bug#876577: marked as done (planner FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 18:34:32 +
with message-id 
and subject line Bug#876577: fixed in planner 0.14.6-6
has caused the Debian Bug report #876577,
regarding planner FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


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

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

...
*** Rebuilding template files ***
cd . && gtkdoc-mktmpl --module=libplanner
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:632: recipe for target 'tmpl-build.stamp' failed
make[4]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: planner
Source-Version: 0.14.6-6

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated planner package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jun 2018 21:00:35 +0300
Source: planner
Binary: planner planner-dev planner-doc planner-data
Architecture: source
Version: 0.14.6-6
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 planner- project management application
 planner-data - Data files for planner
 planner-dev - Planner development library
 planner-doc - Documentation for planner
Closes: 876577
Changes:
 planner (0.14.6-6) unstable; urgency=high
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #892919)
   * Fix the build with gtk-doc-tools >= 1.26. (Closes: #876577)
   * Add the missing build dependency on dh-python.
Checksums-Sha1:
 290e8ffd3d036738cff8363c121b5f3598d5b278 2360 planner_0.14.6-6.dsc
 b37f0ae8895ea0403145f2a34f3af320f7e0f703 17820 planner_0.14.6-6.debian.tar.xz
Checksums-Sha256:
 4e0631a549a91a5753e518d29b9b3f5758ae1c5f746ebdc763d73e2f16b8b47e 2360 
planner_0.14.6-6.dsc
 a5c2e404cff5899c21a13e02795f39adfed9e9a468d90e5e1c2c9941d8312ffb 17820 
planner_0.14.6-6.debian.tar.xz
Files:
 9d9cce8e18646885be0b4b791dc6f6d0 2360 gnome optional planner_0.14.6-6.dsc
 6fb37e0d81317af44ea440dffad9f68d 17820 gnome optional 
planner_0.14.6-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlsv3pUACgkQiNJCh6LY
mLHL2g//fpni5VYrUx4j6fgaiwnUo6VeX+I1ET69e5FUOcHweZZOUZdPipeCZkS9
osHbZEhYXp9dIU7S+a/cibqbiwwyYMu841OPQz/gClpPhyynl7k8VbQnPhWqAIj8
2YbOFTGQLK3+b1NUEwKlAryZCkV1zp2fLOJhtaEZ1PE2b/7MSARgn1KwK6RgRDR9
1VLwP7w6/PIqm6yqMrEYqAFsA2sJSF/FkI1WfbNBT4jNCVs74SfCOabzXl3Kf6DF
D+8eisuaBE5JOLAgqzrzghka3BCDgiU00rDTP5dGYD29nOx8KFgq3Kv5J9bnEz3Y
BT7Gmaj0kBQ5BlGvLBrUdqGmrp2pZl0fY8Ijlp7LsPOZ8v4japN0uT9qsT2U1ZRN
qTJ9wHoQwexTad6K/FEuJdEzbgWzgH0UU2caY3zaIBQ6GXCt21dLDGbQk7W1rNEy
18oCMeJJs9G6dDn1vnf1nLmLsOA0r54+20PHktR6YCt6LeGzVla1o1vl1gmUdgP3
YLTxgHI9d4msh/6DSkDZ3IdY3iGa/KFxGbsp3MeP6RyRifcPBx6xzQDupP9Mg0AO
KvT1SkkIV7Fw1IhhF2jCzMBBhkn4ZelWUxbXkDnUeOTcHwA7S6OZuv4BDWSE1C0b
STMDXCKzAGI4uFbnvkjhsjw1ROAvjROOPlOEMhikCbUZKWqI1eE=
=P6xb
-END PGP SIGNATURE End Message ---

Processed: tagging 902302

[Debian Bug Tracking System]

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

> tags 902302 + ftbfs
Bug #902302 [src:connectome-workbench] connectome-workbench FTBFS on 
armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#902306: FTBFS: xml2-config is gone from libxml2-dev from version 2.9.7+dfsg-1

[Gerardo Esteban Malazdrewicz]

Package: libxml-libxml-perl
Version: 2.0132+dfsg-1+b0.01
Severity: grave
Tags: patch upstream

When running debian/rules build:

-
gerardo@alienware:~/apt-src/libxml-libxml-perl-2.0132+dfsg$ ./debian/rules
build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: se entra en el directorio '/home/gerardo/apt-src/libxml-libxml-
perl-2.0132+dfsg'
SKIP_SAX_INSTALL=1 dh_auto_configure
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-
prefix-map=/home/gerardo/apt-src/libxml-libxml-perl-2.0132+dfsg=. -fstack-
protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-
map=/home/gerardo/apt-src/libxml-libxml-perl-2.0132+dfsg=. -fstack-protector-
strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now"
enable native perl UTF8
running xml2-config...didn't manage to get libxml2 config, guessing
options:
  LIBS='-L/usr/local/lib -L/usr/lib -lxml2 -lm'
  INC='-I/usr/local/include -I/usr/include'
If this is wrong, Re-run as:
  $ /usr/bin/perl Makefile.PL LIBS='-L/path/to/lib' INC='-I/path/to/include'

Checking for ability to link against xml2...no
Checking for ability to link against libxml2...libxml2, zlib, and/or the Math
library (-lm) have not been found.
Try setting LIBS and INC values on the command line
Or get libxml2 from
  http://xmlsoft.org/
If you install via RPMs, make sure you also install the -devel
RPMs, as this is where the headers (.h files) are.

Also, you may try to run perl Makefile.PL with the DEBUG=1 parameter
to see the exact reason why the detection of libxml2 installation
failed or why Makefile.PL was not able to compile a test program.
-

The guesses are wrong.

The alternative using pkg-config is available since at least wheezy, so the
attached patch would work in all recent Debian versions.


This patch will be needed until upstream switches to use pkg-config instead of
(now gone) xml2-config.

Thanks,
Gerardo



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

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

Versions of packages libxml-libxml-perl depends on:
ii  libc6 2.27-3
ii  libxml-namespacesupport-perl  1.12-1
ii  libxml-sax-perl   1.00+dfsg-1+b0.01
ii  libxml2   2.9.7+dfsg-1
ii  perl  5.28.0~rc2-1
ii  perl-base [perlapi-5.28.0]5.28.0~rc2-1
ii  zlib1g1:1.2.11.dfsg-1

libxml-libxml-perl recommends no packages.

libxml-libxml-perl suggests no packages.

-- no debconf information
diff -ruN libxml-libxml-perl-2.0132+dfsg/debian/rules 
libxml-libxml-perl-2.0132+dfsg.good/debian/rules
--- libxml-libxml-perl-2.0132+dfsg/debian/rules 2018-06-23 16:57:04.0 
-0300
+++ libxml-libxml-perl-2.0132+dfsg.good/debian/rules2018-06-24 
15:38:12.931247836 -0300
@@ -10,7 +10,9 @@
dh $@
 
 override_dh_auto_configure:
-   SKIP_SAX_INSTALL=1 dh_auto_configure
+   SKIP_SAX_INSTALL=1 dh_auto_configure -- \
+INC=$(shell pkg-config --cflags libxml-2.0) \
+LIBS=$(shell pkg-config --libs libxml-2.0)
 
 override_dh_auto_test:
dh_auto_test -- TEST_FILES="$(TEST_FILES)"

Bug#893386: marked as done (librime 1.2.10+dfsg2-1 makes brise FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jun 2018 19:34:16 +
with message-id 
and subject line Bug#893386: fixed in brise 0.38.20180515-1
has caused the Debian Bug report #893386,
regarding librime 1.2.10+dfsg2-1 makes brise FTBFS
to be marked as done.

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

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


-- 
893386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librime-bin
Version: 1.2.10+dfsg2-1
Severity: serious
Control: affects -1 src:brise

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/brise-0.35'
# create a default.custom.yaml here, and use it
# to build all the schemas
echo "patch:"  > default.custom.yaml
echo "  schema_list:" >> default.custom.yaml
find -name '*.schema.yaml' \
| xargs -l1 basename -s .schema.yaml \
| perl -pe 's/^/- schema: /' \
| sort | uniq >> default.custom.yaml
mkdir -p data
cp -v default.custom.yaml data
'default.custom.yaml' -> 'data/default.custom.yaml'
cp -v extra/*.yaml data
'extra/array30.dict.yaml' -> 'data/array30.dict.yaml'
'extra/array30.schema.yaml' -> 'data/array30.schema.yaml'
'extra/scj6.dict.yaml' -> 'data/scj6.dict.yaml'
'extra/scj6.schema.yaml' -> 'data/scj6.schema.yaml'
'extra/stenotype.schema.yaml' -> 'data/stenotype.schema.yaml'
'extra/wubi_trad.schema.yaml' -> 'data/wubi_trad.schema.yaml'
dh_auto_build
make -j1
make[2]: Entering directory '/build/1st/brise-0.35'
building rime data.
rime_deployer --build  /build/1st/brise-0.35/data
make[2]: Leaving directory '/build/1st/brise-0.35'
# restore the original copy of default.yaml
cp -v default.yaml data
'default.yaml' -> 'data/default.yaml'
rm -fv data/default.custom.yaml
removed 'data/default.custom.yaml'
make[1]: Leaving directory '/build/1st/brise-0.35'
   dh_auto_test
 fakeroot debian/rules binary
dh binary
   dh_testroot
   dh_prep
   dh_auto_install
make -j1 install DESTDIR=/build/1st/brise-0.35/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/build/1st/brise-0.35'
installing rime data into 
'/build/1st/brise-0.35/debian/tmp/usr/share/rime-data'.
install: omitting directory '/build/1st/brise-0.35/data/build'
make[1]: *** [Makefile:32: install] Error 1
make[1]: Leaving directory '/build/1st/brise-0.35'
dh_auto_install: make -j1 install DESTDIR=/build/1st/brise-0.35/debian/tmp 
AM_UPDATE_INFO_DIR=no returned exit code 2
make: *** [debian/rules:5: binary] Error 2


The failure is caused by a data/build directory created
when building brise with librime 1.2.10+dfsg2-1.

I do not know which of the packages needs fixing,
please reassign if I reported against the wrong one.
--- End Message ---
--- Begin Message ---
Source: brise
Source-Version: 0.38.20180515-1

We believe that the bug you reported is fixed in the latest version of
brise, 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.
Boyuan Yang <073p...@gmail.com> (supplier of updated brise package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Jun 2018 09:51:24 +0800
Source: brise
Binary: librime-data librime-data-array30 librime-data-bopomofo 
librime-data-cangjie5 librime-data-combo-pinyin librime-data-double-pinyin 
librime-data-emoji librime-data-ipa-xsampa librime-data-jyutping 
librime-data-luna-pinyin librime-data-pinyin-simp librime-data-quick5 
librime-data-sampheng librime-data-scj6 librime-data-soutzoe 
librime-data-stenotype librime-data-stroke librime-data-terra-pinyin 
librime-data-wubi librime-data-wugniu librime-data-zyenpheng
Architecture: source
Version: 0.38.20180515-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 librime-data - Rime Input Method Engine, the schema data
 librime-data-array30 - RIME schema data - array30
 librime-data-bopomofo - RIME schema data - Bopomofo (a.k.a Zhu Yin)
 librime-data-cangjie5 - RIME schema data - Cangjie5
 librime-data-combo-pinyin - RIME schema data - Combo 

Processed: found 902306 in 2.0132+dfsg-1, notfound 902306 in 2.0132+dfsg-1+b0.01

[Debian Bug Tracking System]

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

> found 902306 2.0132+dfsg-1
Bug #902306 [libxml-libxml-perl] FTBFS: xml2-config is gone from libxml2-dev 
from version 2.9.7+dfsg-1
Marked as found in versions libxml-libxml-perl/2.0132+dfsg-1.
> notfound 902306 2.0132+dfsg-1+b0.01
Bug #902306 [libxml-libxml-perl] FTBFS: xml2-config is gone from libxml2-dev 
from version 2.9.7+dfsg-1
There is no source info for the package 'libxml-libxml-perl' at version 
'2.0132+dfsg-1+b0.01' with architecture ''
Unable to make a source version for version '2.0132+dfsg-1+b0.01'
No longer marked as found in versions 2.0132+dfsg-1+b0.01.
> thanks
Stopping processing here.

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

Bug#886048: plasma-pa: Depends on gconf

[Scott Kitterman]

On Sunday, June 24, 2018 02:45:31 PM Boyuan Yang wrote:
> On Mon, 01 Jan 2018 17:31:55 -0500 Jeremy Bicha  wrote:
> > Source: plasma-pa
> > Version: 4:5.10.5-2
> > Severity: important
> > User: pkg-gnome-maintain...@lists.alioth.debian.org
> > Usertags: oldlibs gconf
> > Tags: sid buster
> > 
> > Your package depends or build-depends on gconf, but gconf will be
> > removed from Debian soon.
> > 
> > gconf's last release was about 5 years ago. It has been replaced by
> > gsettings (provided in Debian by source glib2.0 )
> > 
> > I assume this depends on pulseaudio.
> > 
> > References
> > --
> > https://developer.gnome.org/gio/stable/ch34.html
> > https://developer.gnome.org/gio/stable/GSettings.html
> > 
> > On behalf of the Debian GNOME team,
> > Jeremy Bicha
> 
> Dear Debian KDE Developers,
> 
> With Debian's pulseaudio 12.0 upload, pulseaudio has removed pulseaudio-
> module-gconf in favour of pulseaudio-module-gsettings, which would break
> current plasma-pa.
> 
> (See also pulseaudio's bug https://bugs.debian.org/902181)
> 
> This raises the urgency of dealing with the bug in plasma-pa to remove gconf
> dependency. Please look into this issue (Debian Bug #886048) again and
> solve it ASAP.

I checked and the newest release (not in Debian yet) still uses gconf.

Scott K

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

Processed: tagging 886048

[Debian Bug Tracking System]

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

> tags 886048 + upstream
Bug #886048 [src:plasma-pa] plasma-pa: Depends on gconf
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#886048: plasma-pa: Depends on gconf

[Boyuan Yang]

On Mon, 01 Jan 2018 17:31:55 -0500 Jeremy Bicha  wrote:
> Source: plasma-pa
> Version: 4:5.10.5-2
> Severity: important
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs gconf
> Tags: sid buster
> 
> Your package depends or build-depends on gconf, but gconf will be
> removed from Debian soon.
> 
> gconf's last release was about 5 years ago. It has been replaced by
> gsettings (provided in Debian by source glib2.0 )
> 
> I assume this depends on pulseaudio.
> 
> References
> --
> https://developer.gnome.org/gio/stable/ch34.html
> https://developer.gnome.org/gio/stable/GSettings.html
> 
> On behalf of the Debian GNOME team,
> Jeremy Bicha

Dear Debian KDE Developers,

With Debian's pulseaudio 12.0 upload, pulseaudio has removed pulseaudio-
module-gconf in favour of pulseaudio-module-gsettings, which would break 
current plasma-pa.

(See also pulseaudio's bug https://bugs.debian.org/902181)

This raises the urgency of dealing with the bug in plasma-pa to remove gconf 
dependency. Please look into this issue (Debian Bug #886048) again and solve 
it ASAP.

--
Regards,
Boyuan Yang


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

Processed: notfound 902227 in 4.0.4

[Debian Bug Tracking System]

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

> notfound 902227 4.0.4
Bug #902227 [krita] Krita lead developer has requested Debian cease 
distributing his software.
There is no source info for the package 'krita' at version '4.0.4' with 
architecture ''
Unable to make a source version for version '4.0.4'
No longer marked as found in versions 4.0.4.
> thanks
Stopping processing here.

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

Processed: tagging 902314

[Debian Bug Tracking System]

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

> tags 902314 - d-i
Bug #902314 [libudev1] libudev1: Installing libudev1 239-1 removes 48 critical 
packages
Removed tag(s) d-i.
> thanks
Stopping processing here.

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

Processed: Re: thefuck: Missing dependency on python-pkg-resources

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #842393 {Done: Adrian Bunk } [thefuck] thefuck: Missing 
dependency on python-pkg-resources
Added tag(s) pending.

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

Bug#900485: python-pbcore: FTBFS and Debci failure with NumPy 1.14

[Sandro Tosi]

> Do you have any suggestions on how to deal with this?

i think you can either add the explicit versioned depends in
debian/control or instruct dh_python2 to add such a dependency.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#902322: martian-modem: FTBFS with dpkg-buildpackage -B

[Andreas Beckmann]

Source: martian-modem
Version: 20080625-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

martian-modem cannot perform a binary-only build since the binary-arch
target is missing:

 debian/rules build-arch
dh_testdir
touch configure-stamp
dh_testdir
touch build-arch-stamp
 fakeroot debian/rules binary-arch
make: *** No rule to make target 'binary-arch'.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2


Andreas


martian-modem_20080625-2_arch.log.gz
Description: application/gzip

Bug#899060: FTBFS: even if tests pass, dh_auto_test fails

[Clint Adams]

On Fri, May 18, 2018 at 08:40:56PM +0200, Adam Borowski wrote:
> ##
>  Monkeysphere basic tests completed successfully!
> ##
> ### removing temp dir...
> make[1]: Leaving directory '/<>'
> dh_auto_test: make -j2 -Oline test returned exit code 2

Does it happen without -j2?

Bug#891670: pymssql FTBFS with freetds-dev 1.00.82-2

[Geoffrey Thomas]

Upstream is being slow to put out a new release, there's some blocker 
involving the new freetds. I asked if that was resolved yet:


https://github.com/pymssql/pymssql/issues/528

At some point (probably in a month or two, honestly...) I'll cherry-pick 
the relevant patches if there's no release, but I'd prefer to see upstream 
be confident about the new freetds version.


--
Geoffrey Thomas
https://ldpreload.com
geo...@ldpreload.com

Bug#902327: isort: missing dependency on python-pkg-resources

[Andreas Beckmann]

Package: isort
Version: 4.2.5+ds1-2
Severity: serious

sid $ isort
Traceback (most recent call last):
  File "/usr/bin/isort", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

stretch $ isort
Traceback (most recent call last):
  File "/usr/bin/isort", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named 'pkg_resources'


Andreas

Processed: bug 902031 is forwarded to https://github.com/liske/needrestart/issues/121

[Debian Bug Tracking System]

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

> forwarded 902031 https://github.com/liske/needrestart/issues/121
Bug #902031 [needrestart] needrestart: ignores configuration file
Set Bug forwarded-to-address to 
'https://github.com/liske/needrestart/issues/121'.
> thanks
Stopping processing here.

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

Bug#902279: youtube-dl: FTBFS in buster/sid (No module named 'setuptools')

[Santiago Vila]

Package: src:youtube-dl
Version: 2018.06.18-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


dpkg-buildpackage: info: source package youtube-dl
dpkg-buildpackage: info: source version 2018.06.18-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Rogério Brito 
 dpkg-source --before-build youtube-dl-2018.06.18
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild --with bash-completion
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 11, 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 14, in 
from distutils.core import setup, Command
ModuleNotFoundError: No module named 'distutils.core'
E: pybuild pybuild:336: 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
debian/rules:8: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


This is from my own autobuilder, but there are full build logs available here:

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/youtube-dl.html

Seems like a missing Build-Depends somewhere.

To avoid this kind of bugs propagating to testing, please consider
uploding in source only form (dpkg-buildpackage -S).

Thanks.