Processed: Also add the src: to affects

[Debian Bug Tracking System]

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

> affects 888697 src:castle-game-engine
Bug #888697 [fp-units-rtl-3.0.4] fp-units-rtl-3.0.4: [armel] fpmake could not 
find unit directory for dependency package "rtl"
Added indication that 888697 affects src:castle-game-engine
> thanks
Stopping processing here.

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

Bug#888721: sanlock uninstallable due to ordering of user handling in postinst

[Christian Ehrhardt]

Package: sanlock
Version: 3.6.0-1
Severity: grave

Hi,
since the following change in the last upload:
  * Add `sanlock' user to `disk' group, thanks to Charlie Smurthwaite;
closes: #888102.
sanlock became uninstallable.

What happens is:
# apt install sanlock
[...]
Setting up sanlock (3.6.0-1) ...
addgroup: The user `sanlock' does not exist.
dpkg: error processing package sanlock (--configure):

The error itself is rather trivial, it is the ordering of actions in
the postinst:
It is atm (simplified)
1. addgroup sanlock disk
2. adduser sanlock

And of these #1 fails since only after #2 the sanlock user would be around.
This might have been missed since on an upgrade things are fine with
the user already existing, but the issue makes sanlock effectively
uninstallable - therefore grave severity.

Fix was tested by repackaging:

  apt-get download sanlock
  dpkg-deb -x sanlock_3.6.0-1_amd64.deb sanlock
  dpkg-deb -e sanlock_3.6.0-1_amd64.deb sanlock/DEBIAN
  vim sanlock/DEBIAN/postinst
Change order of user creation and adding to the group.
  dpkg-deb -b sanlock sanlock_3.6.0-2_amd64.deb
  dpkg -i sanlock_3.6.0-2_amd64.deb

Note, by being uninstallable it also breaks dependent packages like
e.g. atm the build of a new libvirt.

The required change is just to move the addgroup below the useradd like:


Author: Christian Ehrhardt 
Date:   Mon Jan 29 07:10:59 2018 +0100

d/sanlock.postinst: run addgroup after creating the user

Signed-off-by: Christian Ehrhardt 

diff --git a/debian/sanlock.postinst b/debian/sanlock.postinst
index ccbf821..3c1895a 100755
--- a/debian/sanlock.postinst
+++ b/debian/sanlock.postinst
@@ -40,9 +40,6 @@ case "$1" in
if ! getent group sanlock >/dev/null; then
addgroup --quiet --system sanlock
fi
-   if ! { getent group disk | grep --quiet '\'; }; then
-   addgroup --quiet sanlock disk
-   fi

if ! getent passwd sanlock >/dev/null; then
adduser --quiet \
@@ -56,6 +53,9 @@ case "$1" in
--gecos "sanlock" \
sanlock
fi
+   if ! { getent group disk | grep --quiet '\'; }; then
+   addgroup --quiet sanlock disk
+   fi

;;

Processed: tagging 888236

[Debian Bug Tracking System]

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

> tags 888236 + fixed-upstream
Bug #888236 [torbrowser-launcher] torbrowser-launcher: broken by Tor Browser 
7.5: No such file or directory: '.../Docs/sources/versions'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#886816: RM: zap -- RoM; not used + duplicate package

[Alexandre Viau]

Package: ftp.debian.org
Severity: normal

This package is a duplicate of golang-go.uber-zap.

After discussion in #886816, we decided to remove src:zap.

Marking this as RoM because:
 - I am a member of the team
 - It was discussed with src:zap's original uploader

It has no reverse dependencies.

Please remove it from the archive.

Cheers,
-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#888606: marked as done (cysignals: FTBFS with debhelper/11.1 due to empty build target)

[Debian Bug Tracking System]

Your message dated Mon, 29 Jan 2018 05:19:57 +
with message-id 
and subject line Bug#888606: fixed in cysignals 1.6.6+ds-3
has caused the Debian Bug report #888606,
regarding cysignals: FTBFS with debhelper/11.1 due to empty build target
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.)


-- 
888606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cysignals
Version: 1.6.5+ds-2
Severity: serious
Tags: patch

Hi,

The cysignals package FTBFS with debhelper/11.1 as it has an empty
build target.  This is caused by debhelper had a bug in its handling
of "explicitly defined rules targets" that has now been fixed.

Previously, this happened to work because dpkg-buildpackage would
invoke "debian/rules build" (which would be a no-op) followed by
"fakeroot debian/rules binary".  During the binary target, dh's
suboptimal handling would run the build commands.


The solution is trivial but less pretty; explicitly define "build"
with the same content as the "%:" target (or rename the "build" folder
and drop the ".PHONY" target).  I have attached a patch for this.


More details can be found in:
 * #886901 comment #35
 * #887688 comment #37
 * #880840

Apologies for the inconvenience.

Thanks,
~Niels
>From 3a57538b93ca415f235feb04b19395a576dfc60f Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sat, 27 Jan 2018 17:43:04 +
Subject: [PATCH] Avoid empty build target

The dh sequencer as of debhelper/11.1 is stricter with this in order
to solve #880840 (where debhelper would fail to handle such targets
correctly).

Signed-off-by: Niels Thykier 
---
 debian/rules | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/debian/rules b/debian/rules
index 4872a50..bfd28fb 100755
--- a/debian/rules
+++ b/debian/rules
@@ -18,6 +18,12 @@ default:
 %:
dh $@ --with autoreconf --with python2  --with sphinxdoc 
--buildsystem=pybuild
 
+# The build target must not be empty.  Sadly because of how make
+# works, we have do duplicate the target in this case.
+build:
+   dh $@ --with autoreconf --with python2  --with sphinxdoc 
--buildsystem=pybuild
+
+
 override_dh_auto_configure-arch:
$(call adhoc_dh_auto_configure_do,bare)
$(call adhoc_dh_auto_configure_do,pari)
-- 
2.15.1

--- End Message ---
--- Begin Message ---
Source: cysignals
Source-Version: 1.6.6+ds-3

We believe that the bug you reported is fixed in the latest version of
cysignals, 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.
Jerome Benoit  (supplier of updated cysignals 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, 28 Jan 2018 17:05:11 +
Source: cysignals
Binary: python-cysignals-pari python3-cysignals-pari python-cysignals-bare 
python3-cysignals-bare cysignals-tools python-cysignals-doc
Architecture: source
Version: 1.6.6+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Jerome Benoit 
Changed-By: Jerome Benoit 
Description:
 cysignals-tools - interrupt and signal handling for Cython -- tools
 python-cysignals-bare - interrupt and signal handling for Cython -- Python - 
bare
 python-cysignals-doc - interrupt and signal handling for Cython -- doc
 python-cysignals-pari - interrupt and signal handling for Cython -- Python - 
PARI/GP
 python3-cysignals-bare - interrupt and signal handling for Cython -- Python 3 
- bare
 python3-cysignals-pari - interrupt and signal handling for Cython -- Python 3 
- PARI/GP
Closes: 888606
Changes:
 cysignals (1.6.6+ds-3) unstable; urgency=medium
 .
   * Upload to unstable (Closes: #888606).
Checksums-Sha1:
 b9826363b1bb3d58978b62900378679076e8a41b 3568 cysignals_1.6.6+ds-3.dsc
 a548048a37f7f00842aecf6b627fe7d0c7cb831e 12956 
cysignals_1.6.6+ds-3.debian.tar.xz
 65300c1de9fbba1f38e75ff5e7ee515df03d76f0 8158 
cysignals_1.6.6+ds-3_source.buildinfo
Checksums-Sha256:
 

Processed: Bug#888606 marked as pending

[Debian Bug Tracking System]

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

> tag 888606 pending
Bug #888606 [src:cysignals] cysignals: FTBFS with debhelper/11.1 due to empty 
build target
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#888606: marked as pending

[Jerome Benoit]

tag 888606 pending
thanks

Hello,

Bug #888606 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/cysignals.git/commit/?id=393c0ef

---
commit 393c0efc81d9bac3738190f28c784427659da9b1
Author: Jerome Benoit 
Date:   Mon Jan 29 08:52:48 2018 +0400

Debian patch 1.6.6+ds-3

diff --git a/debian/changelog b/debian/changelog
index 6c09f61..9c51b49 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cysignals (1.6.6+ds-3) unstable; urgency=medium
+
+  * Upload to unstable (Closes: #888606).
+
+ -- Jerome Benoit   Sun, 28 Jan 2018 17:05:11 +
+
 cysignals (1.6.6+ds-2) experimental; urgency=medium
 
   * Debianization:

Bug#886816: Removing golang-go.uber-zap or zap

[Pirate Praveen]

On 2018, ജനുവരി 29 9:00:58 AM IST, Alexandre Viau  wrote:
>Hello,
>
>I have uploaded a duplicate of src:zap as src:golang-go.uber-zap.
>
>I don't know why I missed src:zap. Probably because it didn't follow
>the
>pkg-go naming guidelines, but even then, dh-make-golang should have
>told
>me because it uses XS-Go-Import-Path.
>
>Anyways. We should remove one of the two packages.
>
>The next version of influxdb will require zap.
>
>We should open a RM bug to ftpmasters.
>
>Which one do you suggest removing?
>
>Since src:golang-go.uber-zap follows pkg-go naming guidelines, I
>suggest
>that we remove src:zap.
>
>Do you have any objections?
>
>I will open a bug as soon as you confirm.

I'm okay with, we should update all reverse build dependencies accordingly.

>Cheers,

Bug#886816: Removing golang-go.uber-zap or zap

[Alexandre Viau]

Hello,

I have uploaded a duplicate of src:zap as src:golang-go.uber-zap.

I don't know why I missed src:zap. Probably because it didn't follow the
pkg-go naming guidelines, but even then, dh-make-golang should have told
me because it uses XS-Go-Import-Path.

Anyways. We should remove one of the two packages.

The next version of influxdb will require zap.

We should open a RM bug to ftpmasters.

Which one do you suggest removing?

Since src:golang-go.uber-zap follows pkg-go naming guidelines, I suggest
that we remove src:zap.

Do you have any objections?

I will open a bug as soon as you confirm.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#887738: marked as done (nspr FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Mon, 29 Jan 2018 03:21:29 +
with message-id 
and subject line Bug#887738: fixed in nspr 2:4.18-1
has caused the Debian Bug report #887738,
regarding nspr FTBFS with glibc 2.26
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.)


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

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

...
prfz.c: In function 'main':
prfz.c:24:31: error: 'SIZE_MAX' undeclared (first use in this function); did 
you mean 'SSIZE_MAX'?
 size_t  unsigned_max= SIZE_MAX;
   ^~~~
   SSIZE_MAX
--- End Message ---
--- Begin Message ---
Source: nspr
Source-Version: 2:4.18-1

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated nspr 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, 29 Jan 2018 10:39:52 +0900
Source: nspr
Binary: libnspr4 libnspr4-dev libnspr4-dbg
Architecture: source
Version: 2:4.18-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 libnspr4   - NetScape Portable Runtime Library
 libnspr4-dbg - Debugging symbols for the NetScape Portable Runtime library
 libnspr4-dev - Development files for the NetScape Portable Runtime library
Closes: 887738
Changes:
 nspr (2:4.18-1) unstable; urgency=medium
 .
   * New upstream release.
   * nspr/pr/tests/prfz.c: Add missing include for SIZE_MAX. bz#1432638.
 Closes: #887738. Thanks Jason Duerstock.
Checksums-Sha1:
 dbfa31486cebe4194908ed2f9a6881537c09fc83 2061 nspr_4.18-1.dsc
 3d6af705576c53aa9b126925d984419869070120 1139663 nspr_4.18.orig.tar.gz
 6eab1b1161ab446c0dfe3b3e09918db80219c4a9 15516 nspr_4.18-1.debian.tar.xz
 1e9c177d74e96ae8e5b62cfb791b3ad2bd01717b 5926 nspr_4.18-1_source.buildinfo
Checksums-Sha256:
 63a3147c30b2375127d18effa9d4342c3d125773e0ab9718168d75717a33e048 2061 
nspr_4.18-1.dsc
 b89657c09bf88707d06ac238b8930d3ae08de68cb3edccfdc2e3dc97f9c8fb34 1139663 
nspr_4.18.orig.tar.gz
 b1809c2da989dea5a010ca826ef48a37b29b3b59d1ec7a277cb6feb9814d4277 15516 
nspr_4.18-1.debian.tar.xz
 d41ecd9e7ff62d6b77a1e4cbd780d4752f3aa466bd5c3a727848afe03e6be3e0 5926 
nspr_4.18-1_source.buildinfo
Files:
 4d0330d781753c7706359e8b9ca461a3 2061 libs optional nspr_4.18-1.dsc
 2a558f9aeb109bfb16d78bdc42033a1e 1139663 libs optional nspr_4.18.orig.tar.gz
 0ccae59e71c2bfe99d56de8a25669272 15516 libs optional nspr_4.18-1.debian.tar.xz
 cf405a577b48c01f384d8b107317259f 5926 libs optional 
nspr_4.18-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEGC4WHREwufzNfbFn5CqgT6aqjHIFAlpue4gACgkQ5CqgT6aq
jHKj4g/9FVWxBBaXMYEwD78CpVO56lxeLtE66bbByybviw9Rc8rpc2xcMBh46EIO
m1HxpDA7vZRCoKITdAc5xVgp3/urFeBwQeubXeCZcuqOhiVko7a9DitUveIURE4X
ej2+GifgEvNtikAhdpyl+50seu5Ncp3fPS1BO6oxqmPISku8bdv0MUt/ESDuW/nL
/GSkuJihaPgxDVAOaJVcjjD49lspZK405WW+ajMccOF3QKdo8HLRbwPBXuiwnKUk
qsgiZkQtn1G2VxF2GZqqy0mKZY5py5uclhghcjlHJbPCurZ7zEv4bvHq/Sy6efv2
1vk3YJMkLhVe8kJmShLLQBu2VFCTSgw85dqRdVrFV6tsMCwDCgqsPCcSuC6eWCMo
JZ8Ko07FDLLHAfqEUwG5GbjYnMNy+JAfXv/8nF+ht+TZUqs8LmbSv6rN51K85E9l
esNBIKzS1SWnUCRue1uh1Wz45w8nR/oo82xwxS1L9oS8Ze2sBj0sYJMzzzwK/yVM
+yAFSvk+vFmiSvU5WOOnsBqGfYLpDCwvVARxG9/v5amQ7nhwp9aD+tPkaMSqPgXd
06TpHBbnHDrJQH1UoAR1XZc0hWxOCkiM+QQ8e8ZBW1GFQIE3dMMoy3ccJX4cFaTh
+D1x8BQXqy5j4Z6vs8x6YrTz8BqZ6GJW+RHhQkRs8ukl2Yr3KfM=
=Nfq0
-END PGP SIGNATURE End Message ---

Bug#886202: marked as done (FTBFS: chown: cannot access '.../fcoll_8cpp__incl.dot': No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 29 Jan 2018 01:19:06 +0100
with message-id <20180129001906.qvzvdqobtnvdn...@angband.pl>
and subject line seems to work now
has caused the Debian Bug report #886202,
regarding FTBFS: chown: cannot access '.../fcoll_8cpp__incl.dot': No such file 
or directory
to be marked as done.

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

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


-- 
886202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zipios++
Version: 0.1.5.9+cvs.2007.04.28-10
Severity: serious
Justification: fails to build from source

Hi!
I'm afraid your package fails to build on current unstable:

   dh_fixperms
chown: cannot access 
'debian/libzipios++-doc/usr/share/doc/libzipios++-doc/html/fcoll_8cpp__incl.dot':
 No such file or directory
dh_fixperms: find debian/libzipios++-doc -true -print0 2>/dev/null | xargs -0r 
chown --no-dereference 0:0 returned exit code 123
dh_fixperms: Aborting due to earlier error

Tried on armhf amd64.  Log attached.


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

Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Looks like this was some toolchain (debhelper?) problem.  It's not
reproducible anymore; let's close.

-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?--- End Message ---

Bug#888297: marked as done (p7zip: CVE-2017-17969: ZIP Shrink: Heap Buffer Overflow)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 23:05:22 +
with message-id 
and subject line Bug#888297: fixed in p7zip 16.02+dfsg-5
has caused the Debian Bug report #888297,
regarding p7zip: CVE-2017-17969: ZIP Shrink: Heap Buffer Overflow
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.)


-- 
888297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: p7zip
Version: 16.02+dfsg-4
Severity: grave
Tags: upstream newcomer security
Justification: user security hole

Dear Maintainer,

p7zip, p7zip-full and the non-free component p7zip-rar are affected by two
vulnerabilities:
https://landave.io/2018/01/7-zip-multiple-memory-corruptions-via-rar-and-
zip/?hn

In particular, the RAR3 and LZW algorithm implementations are susceptible to
memory corruption and may compromise a system through specially crafted
archives.

These issues have already been fixed upstream, and a new version of p7zip
(18.0) is available.

Please update all p7zip* packages to their latest versions as soon as possible.

Thank you.



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

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

Versions of packages p7zip depends on:
ii  libc6   2.26-2
ii  libgcc1 1:7.2.0-19
ii  libstdc++6  7.2.0-19

p7zip recommends no packages.

Versions of packages p7zip suggests:
ii  p7zip-full  16.02+dfsg-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: p7zip
Source-Version: 16.02+dfsg-5

We believe that the bug you reported is fixed in the latest version of
p7zip, 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.
Robert Luberda  (supplier of updated p7zip 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, 28 Jan 2018 23:32:37 +0100
Source: p7zip
Binary: p7zip p7zip-full
Architecture: source amd64
Version: 16.02+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda 
Changed-By: Robert Luberda 
Description:
 p7zip  - 7zr file archiver with high compression ratio
 p7zip-full - 7z and 7za file archivers with high compression ratio
Closes: 873943 888297
Changes:
 p7zip (16.02+dfsg-5) unstable; urgency=medium
 .
   * Hopefully fix ZIP Shrink: Heap Buffer Overflow (CVE-2017-17969). Thanks
 to Antoine Beaupré for the initial patch, based on upstream changes in
 7Zip 18.00.beta (closes: #888297).
   * Fix `deprecated use of operator++ on bool variable' g++ warning.
   * Fix a typo in man page introduced in 09-man-update.patch
 (closes: #873943).
   * Bump debhelper's compat level to 11.
   * Use 'https' URL in debian/watch (lintian).
   * Standards-Version: 4.1.3.
Checksums-Sha1:
 95f55ff57950d40b5dd190d76f83d68539383204 1928 p7zip_16.02+dfsg-5.dsc
 54ae48c522799c4d484b00866758cc14e26f6c99 21384 p7zip_16.02+dfsg-5.debian.tar.xz
 f6b0d83695d1912a268403754b0ba00aeb6306ca 2437776 
p7zip-dbgsym_16.02+dfsg-5_amd64.deb
 e13cdcf5f9b3e47f7ac1485fed529ac2774e9106 11096596 
p7zip-full-dbgsym_16.02+dfsg-5_amd64.deb
 584a16945fd49aecabce11a3998074153a8efa5d 1164032 
p7zip-full_16.02+dfsg-5_amd64.deb
 816c802a2d9d447ab2aaad720a423ad02e56e01f 6272 
p7zip_16.02+dfsg-5_amd64.buildinfo
 25f3bd3a251e3eb37098d1daff091c7c6bd7 376188 p7zip_16.02+dfsg-5_amd64.deb
Checksums-Sha256:
 c9b63380c9d3dba46e0bdf9633c7dd45f486e21e6dae2375ff98551dd1c5e4d5 1928 
p7zip_16.02+dfsg-5.dsc
 b5a0775fa2fe2e95dd0f3264b92bfc0b67e8f264fb813a53d4f36a0709c14227 21384 
p7zip_16.02+dfsg-5.debian.tar.xz
 

Bug#872490: marked as done (vdr-plugin-osdteletext FTBFS with vdr 2.3.8)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 22:36:59 +
with message-id 
and subject line Bug#872490: fixed in vdr-plugin-osdteletext 0.9.6-1
has caused the Debian Bug report #872490,
regarding vdr-plugin-osdteletext FTBFS with vdr 2.3.8
to be marked as done.

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

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


-- 
872490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-osdteletext
Version: 0.9.5-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-osdteletext.html

...
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-DPLUGIN_NAME_I18N='"osdteletext"'  -o menu.o menu.c
In file included from display.h:19:0,
 from menu.c:18:
displaybase.h: In member function 'int 
cDisplay::GetColorIndex(enumTeletextColor, int)':
displaybase.h:145:40: error: 'cBitmap* cOsd::GetBitmap(int)' is protected 
within this context
 cBitmap *bm=osd->GetBitmap(Area);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from /usr/include/vdr/interface.h:15,
 from menu.c:14:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
In file included from display.h:19:0,
 from menu.c:18:
displaybase.h: In member function 'int 
cDisplay::GetColorIndexAlternate(enumTeletextColor, int)':
displaybase.h:153:40: error: 'cBitmap* cOsd::GetBitmap(int)' is protected 
within this context
 cBitmap *bm=osd->GetBitmap(Area);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from /usr/include/vdr/interface.h:15,
 from menu.c:14:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
menu.c: In member function 'bool TeletextBrowser::CheckIsValidChannel(int)':
menu.c:76:12: error: 'Channels' was not declared in this scope
return (Channels.GetByNumber(number) != 0);
^~~~
menu.c:76:12: note: suggested alternative: 'cChannels'
return (Channels.GetByNumber(number) != 0);
^~~~
cChannels
menu.c: In static member function 'static void 
TeletextBrowser::ChannelSwitched(int)':
menu.c:80:19: error: 'Channels' was not declared in this scope
cChannel *chan=Channels.GetByNumber(ChannelNumber);
   ^~~~
menu.c:80:19: note: suggested alternative: 'cChannels'
cChannel *chan=Channels.GetByNumber(ChannelNumber);
   ^~~~
   cChannels
Makefile:64: recipe for target 'menu.o' failed
make[1]: *** [menu.o] Error 1
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-osdteletext
Source-Version: 0.9.6-1

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

Debian distribution maintenance software
pp.
Tobias Grimm  (supplier of updated vdr-plugin-osdteletext 
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, 28 Jan 2018 23:19:23 +0100
Source: vdr-plugin-osdteletext
Binary: vdr-plugin-osdteletext
Architecture: source amd64
Version: 0.9.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Tobias Grimm 
Description:
 vdr-plugin-osdteletext - Teletext plugin for VDR
Closes: 872490
Changes:
 vdr-plugin-osdteletext (0.9.6-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #872490(
   * Standards-Version: 4.1.2
   * Replaced priority extra with optional
Checksums-Sha1:
 f7453ece90a87ac3e5fd6ba510624d30c4dcfa5d 2193 
vdr-plugin-osdteletext_0.9.6-1.dsc
 

Bug#888573:

[Fake Fur]

thank you

you can close this if you wish to as the work-around seems to mitigate the 
problem

plus sorry for reporting this on the wrong package

Bug#888484: marked as done (clamav: Security release 0.99.3 available (CVE-2017-12374 CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 CVE-2017-12380))

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 22:03:13 +
with message-id 
and subject line Bug#888484: fixed in clamav 0.99.2+dfsg-0+deb8u3
has caused the Debian Bug report #888484,
regarding clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12380)
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.)


-- 
888484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav
Version: 0.99.2+dfsg-0+deb8u2
Severity: important

0.99.3 has been released, see 
http://blog.clamav.net/2018/01/clamav-0993-has-been-released.html.

This fixed a number of overflow bugs, each of which has assigned CVE numbers
due to the potential for denial of service.

We've have started seeing unexpected clamd crashes on a high-traffic mail
system today, though I've been unable to isolate a test case. It's seems like
too much of a coincidence that these crashes start happening the day after a
security release was announced. We've implemented mitigations but an updated
package would be even better.

Cheers!
Rob N.


-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
LogFile = "/var/log/clamav/clamav.log"
StatsHostID = "auto"
StatsEnabled disabled
StatsPEDisabled = "yes"
StatsTimeout = "10"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "5"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
AllowSupplementaryGroups disabled
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
AlgorithmicDetection = "yes"
ScanPE = "yes"
ScanELF = "yes"
DetectBrokenExecutables disabled
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
PhishingAlwaysBlockCloak disabled
PhishingAlwaysBlockSSLMismatch disabled
PartitionIntersection disabled
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
OLE2BlockMacros disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ArchiveBlockEncrypted disabled
ForceToDisk disabled
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
ScanOnAccess disabled
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeUID disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled

Config file: freshclam.conf
---
StatsHostID disabled
StatsEnabled disabled
StatsTimeout disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
PidFile disabled
DatabaseDirectory = "/var/lib/clamav"
Foreground disabled
Debug disabled
AllowSupplementaryGroups disabled
UpdateLogFile = "/var/log/clamav/freshclam.log"
DatabaseOwner = "clamav"
Checks = "24"

Bug#888484: marked as done (clamav: Security release 0.99.3 available (CVE-2017-12374 CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 CVE-2017-12380))

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 22:02:24 +
with message-id 
and subject line Bug#888484: fixed in clamav 0.99.2+dfsg-6+deb9u1
has caused the Debian Bug report #888484,
regarding clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12380)
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.)


-- 
888484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav
Version: 0.99.2+dfsg-0+deb8u2
Severity: important

0.99.3 has been released, see 
http://blog.clamav.net/2018/01/clamav-0993-has-been-released.html.

This fixed a number of overflow bugs, each of which has assigned CVE numbers
due to the potential for denial of service.

We've have started seeing unexpected clamd crashes on a high-traffic mail
system today, though I've been unable to isolate a test case. It's seems like
too much of a coincidence that these crashes start happening the day after a
security release was announced. We've implemented mitigations but an updated
package would be even better.

Cheers!
Rob N.


-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
LogFile = "/var/log/clamav/clamav.log"
StatsHostID = "auto"
StatsEnabled disabled
StatsPEDisabled = "yes"
StatsTimeout = "10"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "5"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
AllowSupplementaryGroups disabled
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
AlgorithmicDetection = "yes"
ScanPE = "yes"
ScanELF = "yes"
DetectBrokenExecutables disabled
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
PhishingAlwaysBlockCloak disabled
PhishingAlwaysBlockSSLMismatch disabled
PartitionIntersection disabled
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
OLE2BlockMacros disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ArchiveBlockEncrypted disabled
ForceToDisk disabled
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
ScanOnAccess disabled
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeUID disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled

Config file: freshclam.conf
---
StatsHostID disabled
StatsEnabled disabled
StatsTimeout disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
PidFile disabled
DatabaseDirectory = "/var/lib/clamav"
Foreground disabled
Debug disabled
AllowSupplementaryGroups disabled
UpdateLogFile = "/var/log/clamav/freshclam.log"
DatabaseOwner = "clamav"
Checks = "24"

Bug#888697: fp-units-rtl-3.0.4: [armel] fpmake could not find unit directory for dependency package "rtl"

[Paul Gevers]

> My recent upload of castle-game-engine FTBFS¹ on armel because fpmake can't
> find the rtl units, while it built in the past (albeit with FPCDIR set). The
> error is this:

Turns out that the armhf build fails for the same reason.²

Paul

²
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=armhf=6.2%2Bdfsg1-3=1517170309=log



signature.asc
Description: OpenPGP digital signature

Bug#888020: Package conflict between primus and nvidia 384.111-3 drivers

[Luca Boccassi]

On Fri, 2018-01-26 at 17:46 +, Luca Boccassi wrote:
> On Wed, 2018-01-24 at 07:49 +0100, Andreas Beckmann wrote:
> > On 2018-01-22 21:10, Andreas Beckmann wrote:
> > > I think we may have to update some documentation for this recent
> > > change
> > > (nvidia-driver.README.Debian),
> > 
> > Luca,
> > 
> > can you update the instructions to use the
> > nvidia-driver-libs{,-nonglvnd} metapackages? With tested commands
> > :-)
> > I did a lot of tests installing, switching and upgrading in chroots
> > (with apt-get). More testing, especially if more package become
> > available in backports would be welcome.
> > 
> > Maybe also mention that primus/optimus users will need the nonglvnd
> > variant.
> > 
> > Thanks
> > 
> > 
> > Andreas
> 
> Sure will look at that during the week-end.
> 
> What do you think about adding a dependency to nvidia-libs-nonglvnd
> in
> bumblebee-nvidia? It already depends on nvidia-driver

Still can't switch using apt, it chokes.

With aptitude these work:

  aptitude install nvidia-driver-libs nvidia-vulkan-common 
nvidia-driver-libs-nonglvnd- nvidia-nonglvnd-vulkan-common-

  aptitude install nvidia-driver-libs-nonglvnd nvidia-nonglvnd-vulkan-common 
nvidia-driver-libs- nvidia-vulkan-common-

So I'll just mention these in the README.

-- 
Kind regards,
Luca Boccassi

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

Bug#888663: libtemplate-perl: FTBFS with debhelper/11.1

[Benj. Mako Hill]

> In the concrete case, it is appears to be relaitively simple to
> convert libtemplate-perl to use override targets rather than the
> deprecated manual sequence control parameters.  I have attached
> a patch for this.

Thanks for the patch! I'll test this and upload it if it looks
alright.

Later,
Mako


-- 
Benjamin Mako Hill
http://mako.cc/

Creativity can be a social contribution, but only in so far
as society is free to use the results. --GNU Manifesto


signature.asc
Description: PGP signature

Processed: fp-units-rtl-3.0.4: [armel] fpmake could not find unit directory for dependency package "rtl"

[Debian Bug Tracking System]

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

> affects 888697 castle-game-engine
Bug #888697 [fp-units-rtl-3.0.4] fp-units-rtl-3.0.4: [armel] fpmake could not 
find unit directory for dependency package "rtl"
Added indication that 888697 affects castle-game-engine
> thanks
Stopping processing here.

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

Bug#888697: fp-units-rtl-3.0.4: [armel] fpmake could not find unit directory for dependency package "rtl"

[Paul Gevers]

Package: fp-units-rtl-3.0.4
Version: 3.0.4+dfsg-14
Severity: serious
Justification: Prevents build of castle-game-engine on armel
Control: affects castle-game-engine

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

My recent upload of castle-game-engine FTBFS¹ on armel because fpmake can't
find the rtl units, while it built in the past (albeit with FPCDIR set). The
error is this:

if [ '(' -n "" ')' -a \
 '(' 3.0.4 '!=' '2.6.4' ')' -a \
 '(' 3.0.4 '!=' '2.6.2' ')' ]; then \
   ./fpmake --globalunitdir="" -v -o -Ur; \
else \
   ./fpmake -v -o -Ur; \
fi
The installer encountered the following error:
Could not find unit directory for dependency package "rtl"
Makefile:60: recipe for target 'build-using-fpmake' failed

Although one could argue that I can set FPCDIR in the debian/rules file, I
believe fpc should be made such that that is unneeded. Indeed, setting FPCDIR
in the previous version of the debian/rules file actually caused cge to FTBFS
with the latest changes in fpc regarding Multi-Arch.

¹ 
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=armel=6.2%2Bdfsg1-2=1517164194=0

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

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

fp-units-rtl-3.0.4 depends on no packages.

Versions of packages fp-units-rtl-3.0.4 recommends:
ii  fp-compiler-3.0.4  3.0.4+dfsg-14

fp-units-rtl-3.0.4 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlpuI+MACgkQnFyZ6wW9
dQo0Vgf/YnAJeKSj62WWA0fV87pIpzaCy7SyrZG99axPwN3UOA8by/neQrZ/ID9V
PQNljXL8r2K0hFo4cDyBM2D9Orv+YkoHvj5nuhrWot/cuD1Taz7VulnFGZn/22Qu
jqSNLZP3DYGsLmUfYsovWMnzjF6aDhoWl5RQKtl1VA03YdFLuhIOP3fK/p4LO37B
x8C4SDf9D7PwLPv7Wr64Ju787T4Ejdn14SzT8xzotvHG39RdcvJBQfIDRtPpYPRK
m/YBuMP2cxCMoS6+9i8MDVKIjroxptJSUK2dfFr8eTZbyyJiSQwnnhwqgXxzC8ik
9V5H6Yr4BQ0n9/dPa5d0R2woLpmtFw==
=kFf3
-END PGP SIGNATURE-

Bug#888236: Fixed upstream

[Micah Lee]

This bug has been fixed upstream in the torbrowser-launcher 0.2.9 release:

https://github.com/micahflee/torbrowser-launcher/releases/tag/v0.2.9

Bug#888661: "configure: error: glm/glm.hpp not found. install glm" although libglm-dev is installed

[Rene Engelhard]

Hi,

On Sun, Jan 28, 2018 at 05:39:03PM +0100, Guus Sliepen wrote:
> On Sun, Jan 28, 2018 at 03:31:08PM +0100, Rene Engelhard wrote:
> 
> > >configure: WARNING: glm/glm.hpp: present but cannot be compiled
> [...]
> > /usr/include/glm/detail/setup.hpp:456:100: note: #pragma message: GLM: GCC 
> > older than 4.6 has a bug presenting the use of rgba and stpq components
> >  # pragma message("GLM: GCC older than 4.6 has a bug presenting the use of 
> > rgba and stpq components")
> [...]
> > Guus, any idea?
> 
> This seems to be a duplicate of 888550. So it's a bug in GLM.

Ah, thanks. And thanks for the quick upload.

This fixes the configure check, but needs LO adaptions, though it seems:

In file included from /usr/include/glm/gtx/norm.hpp:18:0,
 from /data/rene/git/LibreOffice/master/vcl/inc/opengl/VertexUti
ls.hxx:16,
 from /data/rene/git/LibreOffice/master/vcl/inc/opengl/LineRende
rUtils.hxx:14,
 from /data/rene/git/LibreOffice/master/vcl/opengl/LineRenderUti
ls.cxx:11:
/usr/include/glm/gtx/quaternion.hpp:23:3: error: #error "GLM: GLM_GTX_quaternion
 is an experimental extension and may change in the future. Use #define 
GLM_ENABLE_EXPERIMENTAL before including it, if you really want to use it."
 # error "GLM: GLM_GTX_quaternion is an experimental extension and may change 
in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you 
really want to use it."
   ^

But no big deal: :)

+ifeq ($(SYSTEM_GLM),TRUE)
+$(eval $(call gb_Library_add_defs,vcl,\
+-DGLM_ENABLE_EXPERIMENTAL \
+))
+endif

etc.

Regards,

Rene

Bug#888573: gnome-desktop: insertion & removal of USB thumb drive causes user to be logged out

[Juan Rafael Fernández García]

Fixed: disable gnome-shell-extension-places-menu

See Extension cause Gnome-shell to crash
https://gitlab.gnome.org/GNOME/gnome-shell-extensions/issues/49

By the way, gnome-desktop is no longer a package in Testing. It should
be a gnome-shell-extensions bug.

Bug#888236: [torbrowser-launcher] Other workaround

[Valerio Passini]

Package: torbrowser-launcher
Version: 0.2.8-6

--- Please enter the report below this line. ---
I have removed and tried to reinstall torbrowser but the installation process 
was 
similarly failing given this message:
exceptions.IOError: [Errno 2] File o directory non esistente: 
'/home/valerio/.local/
share/torbrowser/tbb/x86_64/tor-browser_it/Browser/TorBrowser/Docs/sources/
versions'So I tried to create the folder and the file manually and filling the 
latter 
with the text content from the relative file inside 
tor-browser-linux64-7.0.11_it.tar.xz 
package. It worked. Now torbrowser updates and launches.

--- System information. ---
Architecture: 
Kernel:   Linux 4.14.15

Debian Release: buster/sid
  990 unstableftp.uk.debian.org 
  990 unstabledebian.fastweb.it 
  500 wheezy  activsoftware.co.uk 
  500 testing mi.mirror.garr.it 
  500 testing ftp.uk.debian.org 
  500 stable-updates  mi.mirror.garr.it 
  500 stable  security.debian.org 
  500 stable  mi.mirror.garr.it 
  500 precise activsoftware.co.uk 
1 experimentalftp.uk.debian.org 
1 experimentaldebian.fastweb.it 

--- Package information. ---
Depends  (Version) | Installed
==-+-==
python:any(<< 2.8) | 
python:any   (>= 2.7.5-5~) | 
ca-certificates| 20170717
gnupg  | 2.2.4-1
libdbus-glib-1-2   | 0.108-3
python-gtk2| 2.24.0-5.1+b1
python-lzma| 0.5.3-3
python-parsley(>= 1.2) | 1.2-1
python-psutil  | 5.4.2-1
python-twisted | 17.9.0-1
python-txsocksx  (>= 1.13.0.1) | 1.15.0.2-1


Recommends  (Version) | Installed
=-+-===
tor   | 0.3.2.9-1


Suggests   (Version) | Installed
-+-===
apparmor | 2.12-2
python-pygame| 1.9.3+dfsg-2+b1





-- 
Valerio

Bug#888661: marked as done (FTBFS: glm/glm.hpp: present but cannot be compiled)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 17:50:10 +
with message-id 
and subject line Bug#888550: fixed in glm 0.9.9~a2-1
has caused the Debian Bug report #888550,
regarding FTBFS: glm/glm.hpp: present but cannot be compiled
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.)


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

Building libreoffice in a sid chroot with:
debuild -i -I --no-sign --build=binary -j1

leads to:
checking glm/glm.hpp usability... no
checking glm/glm.hpp presence... yes
configure: WARNING: glm/glm.hpp: present but cannot be compiled
configure: WARNING: glm/glm.hpp: check for missing prerequisite headers?
configure: WARNING: glm/glm.hpp: see the Autoconf documentation
configure: WARNING: glm/glm.hpp: section "Present But Cannot Be
Compiled"
configure: WARNING: glm/glm.hpp: proceeding with the compiler's result
checking for glm/glm.hpp... no
configure: error: glm/glm.hpp not found. install glm
Error running configure at ./autogen.sh line 293.
/home/actionmystique/src/LibreOffice/libreoffice-5.4.4-1/debian/rules:1963:
recipe for target 'debian/stampdir/build-arch' failed
make[1]: *** [debian/stampdir/build-arch] Error 25
make[1]: Leaving directory
'/home/actionmystique/src/LibreOffice/libreoffice-5.4.4-1'
debian/rules:1956: recipe for target 'build' failed
make: *** [build] Error 2

Although:
# apt-cache policy libglm-dev
libglm-dev:
  Installed: 0.9.8.4-1.1

Full build log is attached.

-- 
Jean-Christophe Manciot


libreoffice_5.4.4-1_amd64.build
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: glm
Source-Version: 0.9.9~a2-1

We believe that the bug you reported is fixed in the latest version of
glm, 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.
Guus Sliepen  (supplier of updated glm 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, 28 Jan 2018 18:37:59 +0100
Source: glm
Binary: libglm-dev libglm-doc
Architecture: source all
Version: 0.9.9~a2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Guus Sliepen 
Description:
 libglm-dev - C++ library for OpenGL GLSL type-based mathematics
 libglm-doc - documentation for the OpenGL Mathematics (GLM) library
Closes: 879517 888550 888661
Changes:
 glm (0.9.9~a2-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes FTBTS with GCC 7.3. Closes: #888550, #888661
   * Remove the fix-infiloop patch.
   * Rebuild the reference manual using Doxygen. Closes: #879517
   * Bump Standards-Version.
   * Add Rules-Requires-Root: no.
Checksums-Sha1:
 34a074dabccbac6d3375cbeff2d06fda16698292 2063 glm_0.9.9~a2-1.dsc
 bdd8c1bf2eace94daa6daac0fe584312461207cb 1614200 glm_0.9.9~a2.orig.tar.gz
 dabce7a925d705a63c161ecbc2243cdff1d476cb 5432 glm_0.9.9~a2-1.debian.tar.xz
 584e6a4cd64c55a82810d47b1ed51ac995f25e60 7639 glm_0.9.9~a2-1_amd64.buildinfo
 f8dec2699e40d21342a5a15f63dfc01c2bec866a 163864 libglm-dev_0.9.9~a2-1_all.deb
 eb6363c640619f39309fa5f720e393d6d6f84a62 442880 libglm-doc_0.9.9~a2-1_all.deb
Checksums-Sha256:
 acece1e44eed3c43f127025407a204a5577c3eff2ccdf6437a0a0079bf0ed8e4 2063 
glm_0.9.9~a2-1.dsc
 8262bbe6700c6c15dc1f5725eacf601da2d862ffdb659104f02e21344b21aa94 1614200 
glm_0.9.9~a2.orig.tar.gz
 dfc5cac964ca76d6e972beab7d394deb9872916fbff68b7bc8eb5df8d2305498 5432 
glm_0.9.9~a2-1.debian.tar.xz
 93b781c2c405ae9d59af12b875443605015eea0eba0e5fb7526ff31edee383d2 7639 
glm_0.9.9~a2-1_amd64.buildinfo
 dc92c1fe34609c28df541c68a16001d4c68a44aeffd524593376a796267cd61d 163864 
libglm-dev_0.9.9~a2-1_all.deb
 9f0ddad921b6056210954faa4ef78ca138a6327904b0e236d2c695399178a68a 442880 
libglm-doc_0.9.9~a2-1_all.deb
Files:
 ddce2d5ba7e64f716ac03a1e73f6c34a 2063 libs optional glm_0.9.9~a2-1.dsc
 4a8d3eb25cf6f4acefddc34c72e9870e 1614200 libs optional glm_0.9.9~a2.orig.tar.gz
 

Bug#888661: marked as done (FTBFS: glm/glm.hpp: present but cannot be compiled)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 17:50:10 +
with message-id 
and subject line Bug#888661: fixed in glm 0.9.9~a2-1
has caused the Debian Bug report #888661,
regarding FTBFS: glm/glm.hpp: present but cannot be compiled
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.)


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

Building libreoffice in a sid chroot with:
debuild -i -I --no-sign --build=binary -j1

leads to:
checking glm/glm.hpp usability... no
checking glm/glm.hpp presence... yes
configure: WARNING: glm/glm.hpp: present but cannot be compiled
configure: WARNING: glm/glm.hpp: check for missing prerequisite headers?
configure: WARNING: glm/glm.hpp: see the Autoconf documentation
configure: WARNING: glm/glm.hpp: section "Present But Cannot Be
Compiled"
configure: WARNING: glm/glm.hpp: proceeding with the compiler's result
checking for glm/glm.hpp... no
configure: error: glm/glm.hpp not found. install glm
Error running configure at ./autogen.sh line 293.
/home/actionmystique/src/LibreOffice/libreoffice-5.4.4-1/debian/rules:1963:
recipe for target 'debian/stampdir/build-arch' failed
make[1]: *** [debian/stampdir/build-arch] Error 25
make[1]: Leaving directory
'/home/actionmystique/src/LibreOffice/libreoffice-5.4.4-1'
debian/rules:1956: recipe for target 'build' failed
make: *** [build] Error 2

Although:
# apt-cache policy libglm-dev
libglm-dev:
  Installed: 0.9.8.4-1.1

Full build log is attached.

-- 
Jean-Christophe Manciot


libreoffice_5.4.4-1_amd64.build
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: glm
Source-Version: 0.9.9~a2-1

We believe that the bug you reported is fixed in the latest version of
glm, 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.
Guus Sliepen  (supplier of updated glm 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, 28 Jan 2018 18:37:59 +0100
Source: glm
Binary: libglm-dev libglm-doc
Architecture: source all
Version: 0.9.9~a2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Guus Sliepen 
Description:
 libglm-dev - C++ library for OpenGL GLSL type-based mathematics
 libglm-doc - documentation for the OpenGL Mathematics (GLM) library
Closes: 879517 888550 888661
Changes:
 glm (0.9.9~a2-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes FTBTS with GCC 7.3. Closes: #888550, #888661
   * Remove the fix-infiloop patch.
   * Rebuild the reference manual using Doxygen. Closes: #879517
   * Bump Standards-Version.
   * Add Rules-Requires-Root: no.
Checksums-Sha1:
 34a074dabccbac6d3375cbeff2d06fda16698292 2063 glm_0.9.9~a2-1.dsc
 bdd8c1bf2eace94daa6daac0fe584312461207cb 1614200 glm_0.9.9~a2.orig.tar.gz
 dabce7a925d705a63c161ecbc2243cdff1d476cb 5432 glm_0.9.9~a2-1.debian.tar.xz
 584e6a4cd64c55a82810d47b1ed51ac995f25e60 7639 glm_0.9.9~a2-1_amd64.buildinfo
 f8dec2699e40d21342a5a15f63dfc01c2bec866a 163864 libglm-dev_0.9.9~a2-1_all.deb
 eb6363c640619f39309fa5f720e393d6d6f84a62 442880 libglm-doc_0.9.9~a2-1_all.deb
Checksums-Sha256:
 acece1e44eed3c43f127025407a204a5577c3eff2ccdf6437a0a0079bf0ed8e4 2063 
glm_0.9.9~a2-1.dsc
 8262bbe6700c6c15dc1f5725eacf601da2d862ffdb659104f02e21344b21aa94 1614200 
glm_0.9.9~a2.orig.tar.gz
 dfc5cac964ca76d6e972beab7d394deb9872916fbff68b7bc8eb5df8d2305498 5432 
glm_0.9.9~a2-1.debian.tar.xz
 93b781c2c405ae9d59af12b875443605015eea0eba0e5fb7526ff31edee383d2 7639 
glm_0.9.9~a2-1_amd64.buildinfo
 dc92c1fe34609c28df541c68a16001d4c68a44aeffd524593376a796267cd61d 163864 
libglm-dev_0.9.9~a2-1_all.deb
 9f0ddad921b6056210954faa4ef78ca138a6327904b0e236d2c695399178a68a 442880 
libglm-doc_0.9.9~a2-1_all.deb
Files:
 ddce2d5ba7e64f716ac03a1e73f6c34a 2063 libs optional glm_0.9.9~a2-1.dsc
 4a8d3eb25cf6f4acefddc34c72e9870e 1614200 libs optional glm_0.9.9~a2.orig.tar.gz
 

Bug#888550: marked as done (glm has some silly GCC version checks, removed upstream)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 17:50:10 +
with message-id 
and subject line Bug#888661: fixed in glm 0.9.9~a2-1
has caused the Debian Bug report #888661,
regarding glm has some silly GCC version checks, removed upstream
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.)


-- 
888661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glm
Version: 0.9.8.4-1.1
Severity: serious
Tags: sid buster patch

glm has some silly GCC version checks, removed upstream

see https://launchpad.net/bugs/1745685

patch at
http://launchpadlibrarian.net/354819354/glm_0.9.8.4-1.1_0.9.8.4-1.1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: glm
Source-Version: 0.9.9~a2-1

We believe that the bug you reported is fixed in the latest version of
glm, 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.
Guus Sliepen  (supplier of updated glm 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, 28 Jan 2018 18:37:59 +0100
Source: glm
Binary: libglm-dev libglm-doc
Architecture: source all
Version: 0.9.9~a2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Guus Sliepen 
Description:
 libglm-dev - C++ library for OpenGL GLSL type-based mathematics
 libglm-doc - documentation for the OpenGL Mathematics (GLM) library
Closes: 879517 888550 888661
Changes:
 glm (0.9.9~a2-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes FTBTS with GCC 7.3. Closes: #888550, #888661
   * Remove the fix-infiloop patch.
   * Rebuild the reference manual using Doxygen. Closes: #879517
   * Bump Standards-Version.
   * Add Rules-Requires-Root: no.
Checksums-Sha1:
 34a074dabccbac6d3375cbeff2d06fda16698292 2063 glm_0.9.9~a2-1.dsc
 bdd8c1bf2eace94daa6daac0fe584312461207cb 1614200 glm_0.9.9~a2.orig.tar.gz
 dabce7a925d705a63c161ecbc2243cdff1d476cb 5432 glm_0.9.9~a2-1.debian.tar.xz
 584e6a4cd64c55a82810d47b1ed51ac995f25e60 7639 glm_0.9.9~a2-1_amd64.buildinfo
 f8dec2699e40d21342a5a15f63dfc01c2bec866a 163864 libglm-dev_0.9.9~a2-1_all.deb
 eb6363c640619f39309fa5f720e393d6d6f84a62 442880 libglm-doc_0.9.9~a2-1_all.deb
Checksums-Sha256:
 acece1e44eed3c43f127025407a204a5577c3eff2ccdf6437a0a0079bf0ed8e4 2063 
glm_0.9.9~a2-1.dsc
 8262bbe6700c6c15dc1f5725eacf601da2d862ffdb659104f02e21344b21aa94 1614200 
glm_0.9.9~a2.orig.tar.gz
 dfc5cac964ca76d6e972beab7d394deb9872916fbff68b7bc8eb5df8d2305498 5432 
glm_0.9.9~a2-1.debian.tar.xz
 93b781c2c405ae9d59af12b875443605015eea0eba0e5fb7526ff31edee383d2 7639 
glm_0.9.9~a2-1_amd64.buildinfo
 dc92c1fe34609c28df541c68a16001d4c68a44aeffd524593376a796267cd61d 163864 
libglm-dev_0.9.9~a2-1_all.deb
 9f0ddad921b6056210954faa4ef78ca138a6327904b0e236d2c695399178a68a 442880 
libglm-doc_0.9.9~a2-1_all.deb
Files:
 ddce2d5ba7e64f716ac03a1e73f6c34a 2063 libs optional glm_0.9.9~a2-1.dsc
 4a8d3eb25cf6f4acefddc34c72e9870e 1614200 libs optional glm_0.9.9~a2.orig.tar.gz
 a2bc246e24df18cf8a8a23a6469299d5 5432 libs optional 
glm_0.9.9~a2-1.debian.tar.xz
 ad2a761e74a53b201254289002c774df 7639 libs optional 
glm_0.9.9~a2-1_amd64.buildinfo
 1a52c5d36f60fbc642f48ad2ec7b7175 163864 libdevel optional 
libglm-dev_0.9.9~a2-1_all.deb
 21c2d9e94cb3bdeba021d9ce7d463530 442880 doc optional 
libglm-doc_0.9.9~a2-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETRt3lsA+CDGZG91CP0kN64ce+foFAlpuCqMACgkQP0kN64ce
+foBHxAAgB8eZYna5vzMo8X6rJu3og9er4NgT1RfzJJ8uIlJpwwcc+2y884CDB9x
CI4KW/xhoBblC30s5AFPX6y/XH+CMjg4U/lh5fOWuT8iEkMkG0yUPuIADNnf/Uhe
E6YuH9Pwn+O/7Td21krrJ6zDzGWI35Lg3hdJgV5QTfuhjDvJ8a9IuW0eoPgP0808
SeBZ7rxRyCt9iuFflXeQ3sr6QpsSuQxY/ESGESORGZBUVQxlkFSwGkt+8xpMN/Wl
S4b+Rb7XG3EbRtSUXd6ECaMw4YU1qgmmfZ8NJVOGyAwXplxawwVVYElVOk+2g4vc
n86ERdoMry9Otj/YIDsdD28RjxyFizTxo+wsdwhy0qF/+9uppqNp1tlgzyEbK3Yz
TdOnEnEFUqmMLKlGFuwtpALC+j3lA3+3OU2RMMi8MCOvOPkmKimxjotZXDDogXZS
jiLGjk468dWRDxWRVLSg13TC/tKpQ1ROxWi5PTxOX0sr2adl9cb6tDS5PDwkf8n0

Bug#888550: marked as done (glm has some silly GCC version checks, removed upstream)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 17:50:10 +
with message-id 
and subject line Bug#888550: fixed in glm 0.9.9~a2-1
has caused the Debian Bug report #888550,
regarding glm has some silly GCC version checks, removed upstream
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.)


-- 
888550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glm
Version: 0.9.8.4-1.1
Severity: serious
Tags: sid buster patch

glm has some silly GCC version checks, removed upstream

see https://launchpad.net/bugs/1745685

patch at
http://launchpadlibrarian.net/354819354/glm_0.9.8.4-1.1_0.9.8.4-1.1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: glm
Source-Version: 0.9.9~a2-1

We believe that the bug you reported is fixed in the latest version of
glm, 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.
Guus Sliepen  (supplier of updated glm 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, 28 Jan 2018 18:37:59 +0100
Source: glm
Binary: libglm-dev libglm-doc
Architecture: source all
Version: 0.9.9~a2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Guus Sliepen 
Description:
 libglm-dev - C++ library for OpenGL GLSL type-based mathematics
 libglm-doc - documentation for the OpenGL Mathematics (GLM) library
Closes: 879517 888550 888661
Changes:
 glm (0.9.9~a2-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes FTBTS with GCC 7.3. Closes: #888550, #888661
   * Remove the fix-infiloop patch.
   * Rebuild the reference manual using Doxygen. Closes: #879517
   * Bump Standards-Version.
   * Add Rules-Requires-Root: no.
Checksums-Sha1:
 34a074dabccbac6d3375cbeff2d06fda16698292 2063 glm_0.9.9~a2-1.dsc
 bdd8c1bf2eace94daa6daac0fe584312461207cb 1614200 glm_0.9.9~a2.orig.tar.gz
 dabce7a925d705a63c161ecbc2243cdff1d476cb 5432 glm_0.9.9~a2-1.debian.tar.xz
 584e6a4cd64c55a82810d47b1ed51ac995f25e60 7639 glm_0.9.9~a2-1_amd64.buildinfo
 f8dec2699e40d21342a5a15f63dfc01c2bec866a 163864 libglm-dev_0.9.9~a2-1_all.deb
 eb6363c640619f39309fa5f720e393d6d6f84a62 442880 libglm-doc_0.9.9~a2-1_all.deb
Checksums-Sha256:
 acece1e44eed3c43f127025407a204a5577c3eff2ccdf6437a0a0079bf0ed8e4 2063 
glm_0.9.9~a2-1.dsc
 8262bbe6700c6c15dc1f5725eacf601da2d862ffdb659104f02e21344b21aa94 1614200 
glm_0.9.9~a2.orig.tar.gz
 dfc5cac964ca76d6e972beab7d394deb9872916fbff68b7bc8eb5df8d2305498 5432 
glm_0.9.9~a2-1.debian.tar.xz
 93b781c2c405ae9d59af12b875443605015eea0eba0e5fb7526ff31edee383d2 7639 
glm_0.9.9~a2-1_amd64.buildinfo
 dc92c1fe34609c28df541c68a16001d4c68a44aeffd524593376a796267cd61d 163864 
libglm-dev_0.9.9~a2-1_all.deb
 9f0ddad921b6056210954faa4ef78ca138a6327904b0e236d2c695399178a68a 442880 
libglm-doc_0.9.9~a2-1_all.deb
Files:
 ddce2d5ba7e64f716ac03a1e73f6c34a 2063 libs optional glm_0.9.9~a2-1.dsc
 4a8d3eb25cf6f4acefddc34c72e9870e 1614200 libs optional glm_0.9.9~a2.orig.tar.gz
 a2bc246e24df18cf8a8a23a6469299d5 5432 libs optional 
glm_0.9.9~a2-1.debian.tar.xz
 ad2a761e74a53b201254289002c774df 7639 libs optional 
glm_0.9.9~a2-1_amd64.buildinfo
 1a52c5d36f60fbc642f48ad2ec7b7175 163864 libdevel optional 
libglm-dev_0.9.9~a2-1_all.deb
 21c2d9e94cb3bdeba021d9ce7d463530 442880 doc optional 
libglm-doc_0.9.9~a2-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETRt3lsA+CDGZG91CP0kN64ce+foFAlpuCqMACgkQP0kN64ce
+foBHxAAgB8eZYna5vzMo8X6rJu3og9er4NgT1RfzJJ8uIlJpwwcc+2y884CDB9x
CI4KW/xhoBblC30s5AFPX6y/XH+CMjg4U/lh5fOWuT8iEkMkG0yUPuIADNnf/Uhe
E6YuH9Pwn+O/7Td21krrJ6zDzGWI35Lg3hdJgV5QTfuhjDvJ8a9IuW0eoPgP0808
SeBZ7rxRyCt9iuFflXeQ3sr6QpsSuQxY/ESGESORGZBUVQxlkFSwGkt+8xpMN/Wl
S4b+Rb7XG3EbRtSUXd6ECaMw4YU1qgmmfZ8NJVOGyAwXplxawwVVYElVOk+2g4vc
n86ERdoMry9Otj/YIDsdD28RjxyFizTxo+wsdwhy0qF/+9uppqNp1tlgzyEbK3Yz
TdOnEnEFUqmMLKlGFuwtpALC+j3lA3+3OU2RMMi8MCOvOPkmKimxjotZXDDogXZS
jiLGjk468dWRDxWRVLSg13TC/tKpQ1ROxWi5PTxOX0sr2adl9cb6tDS5PDwkf8n0

Bug#888661: "configure: error: glm/glm.hpp not found. install glm" although libglm-dev is installed

[Guus Sliepen]

reassign 888661 src:glm
forcemerge 888550 888661
thanks

On Sun, Jan 28, 2018 at 03:31:08PM +0100, Rene Engelhard wrote:

> >configure: WARNING: glm/glm.hpp: present but cannot be compiled
[...]
> /usr/include/glm/detail/setup.hpp:456:100: note: #pragma message: GLM: GCC 
> older than 4.6 has a bug presenting the use of rgba and stpq components
>  # pragma message("GLM: GCC older than 4.6 has a bug presenting the use of 
> rgba and stpq components")
[...]
> Guus, any idea?

This seems to be a duplicate of 888550. So it's a bug in GLM.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature

Processed: Re: Bug#888661: "configure: error: glm/glm.hpp not found. install glm" although libglm-dev is installed

[Debian Bug Tracking System]

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

> reassign 888661 src:glm
Bug #888661 {Done: r...@rene-engelhard.de (Rene Engelhard)} [src:libreoffice] 
FTBFS: glm/glm.hpp: present but cannot be compiled
Bug reassigned from package 'src:libreoffice' to 'src:glm'.
No longer marked as found in versions libreoffice/1:6.0.0~rc2-1 and 
libreoffice/1:5.4.4-1.
No longer marked as fixed in versions libreoffice/1:6.0.0~rc3-1.
> forcemerge 888550 888661
Bug #888550 [src:glm] glm has some silly GCC version checks, removed upstream
Bug #888661 {Done: r...@rene-engelhard.de (Rene Engelhard)} [src:glm] FTBFS: 
glm/glm.hpp: present but cannot be compiled
Bug reopened
Ignoring request to alter fixed versions of bug #888661 to the same values 
previously set
Marked as found in versions glm/0.9.8.4-1.1.
Added tag(s) sid, buster, and patch.
Merged 888550 888661
> thanks
Stopping processing here.

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

Bug#884039: marked as done (linuxtv-dvb-apps FTBFS with linux-libc-dev 4.14.2-1)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 16:22:57 +
with message-id 
and subject line Bug#884039: fixed in linuxtv-dvb-apps 1.1.1+rev1500-1.2
has caused the Debian Bug report #884039,
regarding linuxtv-dvb-apps FTBFS with linux-libc-dev 4.14.2-1
to be marked as done.

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

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


-- 
884039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linuxtv-dvb-apps
Version: 1.1.1+rev1500-1.1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/linuxtv-dvb-apps.html

...
dst_test.c: In function 'dst_set_pid':
dst_test.c:116:19: error: 'CA_SET_PID' undeclared (first use in this function); 
did you mean 'CA_GET_CAP'?
  if ((ioctl(cafd, CA_SET_PID)) < 0) {
   ^~
   CA_GET_CAP


CA_SET_PID never did more than returning -EOPNOTSUPP,
and was therefore removed from the kernel.
--- End Message ---
--- Begin Message ---
Source: linuxtv-dvb-apps
Source-Version: 1.1.1+rev1500-1.2

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated linuxtv-dvb-apps package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 23 Jan 2018 19:52:14 +0200
Source: linuxtv-dvb-apps
Binary: dvb-apps
Architecture: source
Version: 1.1.1+rev1500-1.2
Distribution: unstable
Urgency: low
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Description:
 dvb-apps   - Digital Video Broadcasting (DVB) applications
Closes: 884039
Changes:
 linuxtv-dvb-apps (1.1.1+rev1500-1.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Remove "dst_test -p", the functionality was never actually
 implemented in the kernel and now caused a FTBFS. (Closes: #884039)
Checksums-Sha1:
 a2e183bbcf4cce7746169f0a689fdf08c893d6fc 2190 
linuxtv-dvb-apps_1.1.1+rev1500-1.2.dsc
 43381f9a77cd1002475ae6f16f1a0ed571900b6e 18672 
linuxtv-dvb-apps_1.1.1+rev1500-1.2.debian.tar.xz
Checksums-Sha256:
 f596c2f55dc64ebb5bbc61edb9e3a573885bdf56829bc91a25154eae3d4a62d1 2190 
linuxtv-dvb-apps_1.1.1+rev1500-1.2.dsc
 6d931d0b2eb966fa1357c9caf53abd38c1365468ed93c62b2ab4437fbc77de11 18672 
linuxtv-dvb-apps_1.1.1+rev1500-1.2.debian.tar.xz
Files:
 39e6d48c31ed8e418404abcfdd92bef5 2190 video extra 
linuxtv-dvb-apps_1.1.1+rev1500-1.2.dsc
 73515262c3f03338250f512fd65e1139 18672 video extra 
linuxtv-dvb-apps_1.1.1+rev1500-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlpndwUACgkQiNJCh6LY
mLGnthAAulo09Q+UwVnh10ekIZHiPphsvj8du56+5dHNBTZSCdv4PUSqaaVHb9Q9
s/mjfG8cY2aVYy3X+VV6z4dVJvxJLKdhb5UrgbQ0aHVEj42GhTESFEa9z9DJ7ekp
sbofptciAPTcbuwQpkL2MNgcX9v1oelRGLyHAJVCglYzSSUJjwZYccYiGcVAdIzd
AdDuWpdHcJNO0q2DaQeHjWGf8OmrBrLOd6ygxn0nwzYl5GswYCpdZvOGb21gF+HP
VsZyf4leGkl6/ptxEvIDL/G6hLANBjvNBrRwOICoQdjk2/qziM6zsaHHsNUjsFCV
D+Jv+2QIKKP0PvuzAWhc4u2orbGWcoFVmZeYdCaVu3nAr9wYqnzwaC/G51+RmvTP
vo6KBtoEtr2hPlwkeXAo2tflDDBvtaBNfFSJujCQQ1xlx3sosrUyOgIFAZTCaJT3
n41uuITpmu+0E5GhmPh50QIDNC9haH9U/QEGIuJq0VdHOnLzmOllCBq0T04gnAcO
ms6p/iQVMIt/fP/d9tyNh2RwYTcy+x2TripwPf4FsMo3c6HuJTOjaNNZ9SR9x9zo
ym4OXA+0WWobBYCo3jdNYZV2WIRsfEfbqWWVwirV57BMH4rz0cAg50NNUlsCWMy6
FxUhPQ75K3P6JwGnlX0VptyN+lgJb6754+K2l2mD2oihPjx8caA=
=oth4
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 16:23:13 +
with message-id 
and subject line Bug#876573: fixed in shishi 1.0.2-6.1
has caused the Debian Bug report #876573,
regarding shishi 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.)


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

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

...
Making all in reference
make[4]: Entering directory '/build/1st/shishi-1.0.2/doc/reference'
  DOC   Scanning header files
  DOC   Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:1550: recipe for target 'tmpl-build.stamp' failed
make[4]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: shishi
Source-Version: 1.0.2-6.1

We believe that the bug you reported is fixed in the latest version of
shishi, 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 shishi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 19 Jan 2018 16:47:40 +0200
Source: shishi
Binary: libshishi0 libshisa0 shishi shishi-common shishi-doc shishi-dbg 
libshishi-dev shisa libshisa-dev shishi-kdc libpam-shishi
Architecture: source
Version: 1.0.2-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Shishi Team 
Changed-By: Adrian Bunk 
Description:
 libpam-shishi - PAM module for Shishi Kerberos v5
 libshisa-dev - Development files for the Shishi Kerberos v5 KDC database 
library
 libshisa0  - Library for the Shishi Kerberos v5 KDC database
 libshishi-dev - Development files for the Shishi Kerberos v5 library
 libshishi0 - Library for the Shishi Kerberos v5 implementation
 shisa  - Administration utility for the Shishi Kerberos v5 KDC database
 shishi - Command line client for the Shishi Kerberos v5 implementation
 shishi-common - Platform independent files for Shishi
 shishi-dbg - Debugging symbols for Shishi
 shishi-doc - Documentation for Shishi
 shishi-kdc - Kerberos v5 Key Distribution Center (KDC) Shishi server daemon
Closes: 864133 876573
Changes:
 shishi (1.0.2-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update files from gtk-doc-tools 1.27 to fix FTBFS
 with gtk-doc-tools >= 1.26. (Closes: #876573)
   * Update the build dependency from libgcrypt11-dev
 to libgcrypt-dev. (Closes: #864133)
Checksums-Sha1:
 697cae5406566354656eb27914cb9bf011844f63 2595 shishi_1.0.2-6.1.dsc
 8af6b02b24ae3ec3984b7d52d1e1cae1cb144130 69844 shishi_1.0.2-6.1.debian.tar.xz
Checksums-Sha256:
 de57be9ef9a7af075587a433e856470fb59d07145712683f01dcbccd1ada8f84 2595 
shishi_1.0.2-6.1.dsc
 d7c7e0df55ea77f4c8a8a3fa4a8b2c24b2d44005fb953e13ec3ba064383b1132 69844 
shishi_1.0.2-6.1.debian.tar.xz
Files:
 ac7ec43d46b8bd520ff52972b3f1f742 2595 net extra shishi_1.0.2-6.1.dsc
 ddd9ef00e7f1ab1d91dbd3841f2dc08f 69844 net extra shishi_1.0.2-6.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlpiEbIACgkQiNJCh6LY
mLHMxQ/+MqY1dVe1MV4bckH39p2owIJ8GqFUhQ0pq0iFacnlffcIclVYXs0DDdIt
0zgI29WV6PRuQdnQksb4dTOsdy45Cl9a4ka/ZbFBlHGZ4JZ6SWuFhWtG2ZPwI+l4
DfifIV4vB3iI3pqWOQKVfzVdWktOtZpmFmFcVQ6iDWhOadWIp9mCDnXGyCvaYTmg
k5QHaBUAgLJFsBEO2ueMk31aHnEo8aQupQz4OSjEgLo678yhMQV3QV8sRNyEmvWQ
NEMxd2bTQFjMOWMDvk1LtrlVYymmQZj1HibFzrXsbZ+3OWFjFgL5Z5ulOk9hw08/
SEzx4s4sOzv3VnOv7EDXn3J57Dv2Cw83iefUvCjM6zYKEATNvC4h5x77UqJguLlt
xbSFwzAp5q3rrRsj1hypqQ3VXvs/D24LbU5MLAGO1j6xslRTtHrXpRVOgt0G0vvm
ewZxkPHwW48LcKxhMmobb0xZoARQxloQpl0JaD0ixVVhKl68pxs72ue2qACf1sII
G5p34gGYkCrc1IcvfHvF6XvrzrZ3u342TPREXN34yRPjl/hOFJDAIDdjQVDj2xRI
1W10w4w4Xz4f9c3wFh3KUmXf4MKEthGWGeAh5ApC3O5ToBshKGYqYXJ+RFvVtc5i
v7qqSHW3YuWItmKTczsBi9dTL9dkwAxci+Hc31uJSIt3p9jcrJ0=
=RPpg
-END PGP SIGNATURE End Message ---

Processed: fastnetmon FTBFS with libndpi-dev 2.2-1

[Debian Bug Tracking System]

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

> forwarded 887623 https://github.com/pavel-odintsov/fastnetmon/issues/699
Bug #887623 [src:fastnetmon] fastnetmon FTBFS with libndpi-dev 2.2-1
Set Bug forwarded-to-address to 
'https://github.com/pavel-odintsov/fastnetmon/issues/699'.
> thanks
Stopping processing here.

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

Bug#872494: marked as done (vdr-plugin-skinenigmang FTBFS with vdr 2.3.8)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 16:23:36 +
with message-id 
and subject line Bug#872494: fixed in vdr-plugin-skinenigmang 
0.1.2+git20180128-1
has caused the Debian Bug report #872494,
regarding vdr-plugin-skinenigmang FTBFS with vdr 2.3.8
to be marked as done.

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

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


-- 
872494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-skinenigmang
Version: 0.1.2+git20150212-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-skinenigmang.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='"skinenigmang"' -DUSE_PLUGIN_EPGSEARCH 
-DUSE_PLUGIN_MAILBOX -DUSE_PLUGIN_AVARDS -DHAVE_IMAGEMAGICK 
-DRECORDING_COVER='"Cover-Enigma"' -I/usr/include/vdr/include -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/freetype2 enigma.c
In file included from enigma.c:36:0:
services/epgsearch.h:164:12: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
   std::auto_ptr handler;
^~~~
In file included from /usr/include/c++/7/bits/locale_conv.h:41:0,
 from /usr/include/c++/7/locale:43,
 from /usr/include/c++/7/iomanip:43,
 from enigma.c:18:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
enigma.c: In member function 'void cSkinEnigmaDisplayChannel::DrawSymbols(const 
cChannel*)':
enigma.c:566:5: error: 'cSchedulesLock' was not declared in this scope
 cSchedulesLock SchedulesLock;
 ^~
enigma.c:566:5: note: suggested alternative: 'cSchedules_Lock'
 cSchedulesLock SchedulesLock;
 ^~
 cSchedules_Lock
enigma.c:567:47: error: 'Schedules' is not a member of 'cSchedules'
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
   ^
enigma.c:567:57: error: 'SchedulesLock' was not declared in this scope
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
 ^
enigma.c:567:57: note: suggested alternative: 'cSchedules_Lock'
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
 ^
 cSchedules_Lock
enigma.c: In constructor 'cSkinEnigmaDisplayMenu::cSkinEnigmaDisplayMenu()':
enigma.c:1379:16: error: 'min' was not declared in this scope
   nMarkerGap = min(MarkerGap, lineHeight / 2 - 1); //lineHeight - 2 * MarkerGap
^~~
enigma.c:1379:16: note: suggested alternative:
In file included from /usr/include/c++/7/bits/char_traits.h:39:0,
 from /usr/include/c++/7/string:40,
 from common.h:11,
 from enigma.c:8:
/usr/include/c++/7/bits/stl_algobase.h:243:5: note:   'std::min'
 min(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
enigma.c: In member function 'void cSkinEnigmaDisplayMenu::SetColors()':
enigma.c:1417:23: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   if (osd->GetBitmap(1) == NULL) { //single area
   ^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
enigma.c:1421:37: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   cBitmap *bitmap = osd->GetBitmap(0);
 ^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:

Bug#876592: gconf: diff for NMU version 3.2.6-4.1

[Simon McVittie]

On Sun, 28 Jan 2018 at 17:35:05 +0200, Adrian Bunk wrote:
> On Sun, Jan 28, 2018 at 02:20:19PM +, Simon McVittie wrote:
> > I think the canonical way to
> > fix this class of bug is to ensure that dh-autoreconf runs gtkdocize,
> > either by running upstream's autogen.sh (if it's in the tarball):
> > 
> > https://salsa.debian.org/gnome-team/gtk3/commit/490e3220dfc976d181aab3e89c34e7a75080d94a
> > 
> > or by providing a simplified version ourselves:
> > 
> > https://salsa.debian.org/debian/flatpak/commit/d8004c50ffb6c99e20a77873e8cf48967afddfe8
> > https://salsa.debian.org/debian/flatpak/commit/8686daaf43a6d5674d1d545435f19b89773790b4
> > 
> > That doesn't seem like something that would justify a re-upload, though.
> 
> Without testing it, all this looks as if it would break
>   dpkg-buildpackage && dpkg-buildpackage

dh_autoreconf avoids that by hooking dh_autoreconf_clean into
the clean target, which is the same way that it avoids breaking the
build-twice-in-a-row use-case with its changes to Makefile.in, configure,
or other Autotools-generated files in the orig tarball.

There have been bugs in this in the past, some of which were fixed as
recently as dh-autoreconf/16, but in general it works. In particular,
I've checked that flatpak can build twice in a row on today's unstable.

smcv

Bug#872486: marked as done (vdr-plugin-epgsync FTBFS with vdr 2.3.8)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 15:50:18 +
with message-id 
and subject line Bug#872486: fixed in vdr-plugin-epgsync 1.0.1-3
has caused the Debian Bug report #872486,
regarding vdr-plugin-epgsync FTBFS with vdr 2.3.8
to be marked as done.

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

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


-- 
872486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-epgsync
Version: 1.0.1-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-epgsync.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"epgsync"'  -o thread.o thread.c
thread.c: In function 'cChannel* GetChannelByName(const char*, const cChannel*, 
eChannelTypes)':
thread.c:47:27: error: 'Channels' was not declared in this scope
  for (cChannel *channel = Channels.First(); channel; channel = 
Channels.Next(channel)) {
   ^~~~
thread.c:47:27: note: suggested alternative: 'kChannels'
  for (cChannel *channel = Channels.First(); channel; channel = 
Channels.Next(channel)) {
   ^~~~
   kChannels
thread.c: In member function 'virtual void cEpgSyncThread::Action()':
thread.c:98:4: error: 'cSchedulesLock' was not declared in this scope
cSchedulesLock *lock = NULL;
^~
thread.c:98:4: note: suggested alternative: 'cSchedules_Lock'
cSchedulesLock *lock = NULL;
^~
cSchedules_Lock
thread.c:98:20: error: 'lock' was not declared in this scope
cSchedulesLock *lock = NULL;
^~~~
thread.c:98:20: note: suggested alternative: 'Lock'
cSchedulesLock *lock = NULL;
^~~~
Lock
thread.c:99:29: error: 'Channels' was not declared in this scope
for (cChannel *channel = Channels.First(); channel && Running();
 ^~~~
thread.c:99:29: note: suggested alternative: 'kChannels'
for (cChannel *channel = Channels.First(); channel && Running();
 ^~~~
 kChannels
thread.c:102:17: error: expected type-specifier before 'cSchedulesLock'
  lock = new cSchedulesLock();
 ^~
thread.c:103:21: error: 'Schedules' is not a member of 'cSchedules'
 if (cSchedules::Schedules(*lock)->GetSchedule(channel)) {
 ^
thread.c: In member function 'bool cEpgSyncThread::CmdLSTE(FILE*, const char*)':
thread.c:185:18: error: 'Channels' was not declared in this scope
cChannel *c = Channels.GetByChannelID(tChannelID::FromString(p));
  ^~~~
thread.c:185:18: note: suggested alternative: 'kChannels'
cChannel *c = Channels.GetByChannelID(tChannelID::FromString(p));
  ^~~~
  kChannels
Makefile:65: recipe for target 'thread.o' failed
make[1]: *** [thread.o] Error 1
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-epgsync
Source-Version: 1.0.1-3

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

Debian distribution maintenance software
pp.
Tobias Grimm  (supplier of updated vdr-plugin-epgsync 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, 28 Jan 2018 16:17:06 +0100
Source: vdr-plugin-epgsync
Binary: vdr-plugin-epgsync
Architecture: source amd64
Version: 1.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Tobias Grimm 
Description:
 vdr-plugin-epgsync - VDR plugin for EPG synchronization between VDR systems
Closes: 872486
Changes:
 vdr-plugin-epgsync (1.0.1-3) unstable; urgency=medium
 .
   * Added VDR 2.3.2 compatibility patch 

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

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 15:49:42 +
with message-id 
and subject line Bug#876592: fixed in gconf 3.2.6-4.1
has caused the Debian Bug report #876592,
regarding gconf 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.)


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

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

...
Making all in gconf
make[4]: Entering directory '/build/1st/gconf-3.2.6/doc/gconf'
if test "/build/1st/gconf-3.2.6/doc/gconf" != 
"/build/1st/gconf-3.2.6/doc/gconf" ; then \
files=`echo  gconf-docs.sgml gconf-sections.txt gconf-overrides.txt  
gconf.types`; \
if test "x$files" != "x" ; then \
for file in $files ; do \
test -f /build/1st/gconf-3.2.6/doc/gconf/$file && \
cp -pu /build/1st/gconf-3.2.6/doc/gconf/$file 
/build/1st/gconf-3.2.6/doc/gconf/ || true; \
done; \
fi; \
test -d /build/1st/gconf-3.2.6/doc/gconf/tmpl && \
{ cp -rp /build/1st/gconf-3.2.6/doc/gconf/tmpl 
/build/1st/gconf-3.2.6/doc/gconf/; \
chmod -R u+w /build/1st/gconf-3.2.6/doc/gconf/tmpl; } \
fi
touch setup-build.stamp
_source_dir='' ; \
for i in ../../gconf ; do \
_source_dir="${_source_dir} --source-dir=$i" ; \
done ; \
gtkdoc-scan --module=gconf --ignore-headers="" ${_source_dir} 
--deprecated-guards="GCONF_ENABLE_BROKEN|GCONF_DISABLE_DEPRECATED" 
if grep -l '^..*$' gconf.types > /dev/null 2>&1 ; then \
scanobj_options=""; \
gtkdoc-scangobj 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
if test "../../gconf/gconf-listeners.h ../../gconf/gconf-schema.h 
../../gconf/gconf-enum-types.h ../../gconf/gconf-value.h 
../../gconf/gconf-backend.h ../../gconf/gconfmarshal.h 
../../gconf/gconf-error.h ../../gconf/gconf-sources.h 
../../gconf/gconf-internals.h ../../gconf/gconf-database-dbus.h 
../../gconf/gconfd-dbus.h ../../gconf/gconfd.h ../../gconf/gconf-dbus-utils.h 
../../gconf/gconf-database.h ../../gconf/gconf.h ../../gconf/gconf-changeset.h 
../../gconf/gconf-locale.h ../../gconf/gconf-client.h 
../../gconf/gconf-engine.h ../../gconf/gconfmarshal.c ../../gconf/gconfd.c 
../../gconf/gconf-client.c ../../gconf/gconf-enum-types.c ../../gconf/dllmain.c 
../../gconf/gconf-database.c ../../gconf/gconf-dbus.c 
../../gconf/gconf-backend.c ../../gconf/gconf-sources.c 
../../gconf/gconf-internals.c ../../gconf/gconf-schema.c 
../../gconf/gconfd-dbus.c ../../gconf/gconf-locale.c ../../gconf/gconf-value.c 
../../gconf/gconf-dbus-utils.c ../../gconf/gconftool.c 
../../gconf/gconf-changeset.c .
 ./../gconf/gconf-listeners.c ../../gconf/gconf-database-dbus.c 
../../gconf/gconf-error.c ../../gconf/gconf.c" = "0"; then \
if test "x" = "x1"; then \
scanobj_options="--verbose"; \
fi; \
fi; \
CC="/bin/bash ../../libtool --tag=CC --mode=compile gcc  
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall" LD="/bin/bash ../../libtool --tag=CC --mode=link 
gcc -lgobject-2.0 -lglib-2.0  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall  -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed" 
RUN="/bin/bash ../../libtool --mode=execute" CFLAGS="-I../.. -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall" 
LDFLAGS="-Wl,-z,relro -Wl,-z,defs -Wl,--as-needed -lgio-2.0 -lgthread-2.0 
-pthread -Wl,--export-dynamic -lgmodule-2.0 -pthread -lgobject-2.0 -lglib-2.0 
../../gconf/libgconf-2.la -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed" \
gtkdoc-scangobj  $scanobj_options --module=gconf; \
else \
for i in gconf.args gconf.hierarchy gconf.interfaces gconf.prerequisites 
gconf.signals ; do \
test -f $i || touch $i ; \
done \
fi
touch scan-build.stamp
gtkdoc-mktmpl --module=gconf 
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:705: recipe for target 'tmpl-build.stamp' failed
make[4]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: gconf
Source-Version: 3.2.6-4.1

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

Bug#880238: marked as done (gconf: FTBFS: gconf.c:833: Error: GConf: encountered multiple return value parameters or tags for "gconf_engine_notify_add".)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 15:49:42 +
with message-id 
and subject line Bug#876592: fixed in gconf 3.2.6-4.1
has caused the Debian Bug report #876592,
regarding gconf: FTBFS: gconf.c:833: Error: GConf: encountered multiple return 
value parameters or tags for "gconf_engine_notify_add".
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.)


-- 
876592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf
Version: 3.2.6-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g-ir-scanner: link: /bin/bash ../libtool --mode=link --tag=CC gcc -o 
> /<>/gconf/tmp-introspect5_s0jjuj/GConf-2.0 -export-dynamic 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> /<>/gconf/tmp-introspect5_s0jjuj/GConf-2.0.o -L. libgconf-2.la 
> -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread 
> -lglib-2.0 -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed
> libtool: link: gcc -o 
> /<>/gconf/tmp-introspect5_s0jjuj/.libs/GConf-2.0 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> /<>/gconf/tmp-introspect5_s0jjuj/GConf-2.0.o 
> -Wl,--export-dynamic -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,defs 
> -Wl,--as-needed -Wl,--export-dynamic  -L. ./.libs/libgconf-2.so -lgio-2.0 
> -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -pthread
> gconf.c:833: Error: GConf: encountered multiple return value parameters or 
> tags for "gconf_engine_notify_add".
> gconf.c:3343: Error: GConf: encountered multiple return value parameters or 
> tags for "gconf_engine_get_schema".
> gconf-dbus.c:1590: Warning: GConf: multiple comment blocks documenting 
> 'gconf_engine_recursive_unset:' identifier (already seen at gconf.c:1457).
> gconf-dbus.c:2408: Warning: GConf: multiple comment blocks documenting 
> 'gconf_debug_shutdown:' identifier (already seen at gconf.c:2407).
> gconf-dbus.c:2410: Warning: GConf: gconf_debug_shutdown: unknown parameter 
> 'void' in documentation comment
> gconf-value.h:107: Warning: GConf: gconf_value_set_list_nocopy: argument 
> list: Missing (element-type) annotation
> gconf-value.h:109: Warning: GConf: gconf_value_set_list: argument list: 
> Missing (element-type) annotation
> gconf-changeset.h:119: Warning: GConf: gconf_change_set_set_list: argument 
> list: Missing (element-type) annotation
> gconf-client.h:334: Warning: GConf: gconf_client_set_list: argument list: 
> Missing (element-type) annotation
> sed -e 's,[@]libexecdir[@],/usr/lib/x86_64-linux-gnu/gconf,g' \
>   <./org.gnome.GConf.service.in >org.gnome.GConf.service
> /usr/bin/g-ir-compiler --includedir=. --includedir=. GConf-2.0.gir -o 
> GConf-2.0.typelib
> make[4]: Leaving directory '/<>/gconf'
> make[3]: Leaving directory '/<>/gconf'
> Making all in backends
> make[3]: Entering directory '/<>/backends'
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
> -I.. -I.. -I../gconf -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2  
> -DGCONF_ENABLE_INTERNALS=1 -DG_LOG_DOMAIN=\"GConf-Backends\"  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
> markup-backend.lo markup-backend.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../gconf -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/libxml2 -DGCONF_ENABLE_INTERNALS=1 
> -DG_LOG_DOMAIN=\"GConf-Backends\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -c markup-backend.c  -fPIC -DPIC -o 
> .libs/markup-backend.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../gconf -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/libxml2 -DGCONF_ENABLE_INTERNALS=1 
> -DG_LOG_DOMAIN=\"GConf-Backends\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -c markup-backend.c -o markup-backend.o 
> >/dev/null 2>&1
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 

Bug#876592: gconf: diff for NMU version 3.2.6-4.1

[Adrian Bunk]

On Sun, Jan 28, 2018 at 02:20:19PM +, Simon McVittie wrote:
> On Sun, 28 Jan 2018 at 06:29:19 +0200, Adrian Bunk wrote:
> > I've prepared an NMU for gconf (versioned as 3.2.6-4.1) and uploaded
> > it to DELAYED/5.
> ...
> > +  * Update gtk-doc.make from gtk-doc-tools 1.27-1,
> > +fixing a FTBFS with gtk-doc-tools >= 1.26. (Closes: #876592)
> 
> This seems a reasonable solution. Feel free to reschedule to DELAYED/0.

Thanks, done.

> gconf has been dead upstream since about 2010, and is one of the obsolete
> packages that the GNOME team are trying to avoid including in buster,
> so GNOME maintainers are unlikely to be uploading it any time soon.

Buster or not, such FTBFS are creating problems for surprisingly many 
people right now.

Bootstrapping new ports (currently ia64, soon RISC-V) needs stuff 
building.
And this is not only gconf, libgnomecanvas was another example
of a library that still has huge reverse dependencies.[1]

Similar problems also exist for Debian derivatives that are based on
testing or unstable, and that need to be able to (re)build the binaries
they ship.
Ubuntu 18.04 would be an obvious example for that.

>...
> FYI, for packages with a sufficiently recent/sane Autotools setup to
> be compatible with an autoreconf with current Autotools (which I was
> surprised to see seems to include gconf), I think the canonical way to
> fix this class of bug is to ensure that dh-autoreconf runs gtkdocize,
> either by running upstream's autogen.sh (if it's in the tarball):
> 
> https://salsa.debian.org/gnome-team/gtk3/commit/490e3220dfc976d181aab3e89c34e7a75080d94a
> 
> or by providing a simplified version ourselves:
> 
> https://salsa.debian.org/debian/flatpak/commit/d8004c50ffb6c99e20a77873e8cf48967afddfe8
> https://salsa.debian.org/debian/flatpak/commit/8686daaf43a6d5674d1d545435f19b89773790b4
> 
> That doesn't seem like something that would justify a re-upload, though.

Without testing it, all this looks as if it would break
  dpkg-buildpackage && dpkg-buildpackage

Is there anything in plce to ensure that dpkg won't error our due
to these modified files when rebuilding the source package?

> Thanks,
> smcv

cu
Adrian

[1] due to #887673

-- 

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

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 888663 buster sid
Bug #888663 [libtemplate-perl] libtemplate-perl: FTBFS with debhelper/11.1
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: is-glob-related upstream issues

[Debian Bug Tracking System]

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

> forwarded 884543 
> https://github.com/micromatch/glob-base/pull/5#issuecomment-338461887
Bug #884543 [src:node-glob-base] node-glob-base: FTBFS and Debci failure with 
node-is-glob 4.0.0-1
Set Bug forwarded-to-address to 
'https://github.com/micromatch/glob-base/pull/5#issuecomment-338461887'.
> forwarded 884544 https://github.com/es128/glob-parent/issues/16
Bug #884544 [src:node-glob-parent] node-glob-parent: FTBFS and Debci failure 
with node-is-glob 4.0.0-1
Set Bug forwarded-to-address to 
'https://github.com/es128/glob-parent/issues/16'.
> forwarded 884545 https://github.com/micromatch/parse-glob/issues/3
Bug #884545 [src:node-parse-glob] node-parse-glob: FTBFS and Debci failure with 
node-is-glob 4.0.0-1
Set Bug forwarded-to-address to 
'https://github.com/micromatch/parse-glob/issues/3'.
> thanks
Stopping processing here.

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

Bug#888661: "configure: error: glm/glm.hpp not found. install glm" although libglm-dev is installed

[Rene Engelhard]

severity 888661 serious
retitle 888661 FTBFS: glm/glm.hpp: present but cannot be compiled
found 888661 1:6.0.0~rc2-1
close 888661 1:6.0.0~rc3-1
thanks

Hi,

On Sun, Jan 28, 2018 at 03:09:25PM +0100, jean-christophe manciot wrote:
>checking glm/glm.hpp usability... no
>checking glm/glm.hpp presence... yes
>configure: WARNING: glm/glm.hpp: present but cannot be compiled
  ^^

That already makes it more clear.

>configure: WARNING: glm/glm.hpp:     check for missing prerequisite
>headers?
>configure: WARNING: glm/glm.hpp: see the Autoconf documentation
>configure: WARNING: glm/glm.hpp:     section "Present But Cannot Be
>Compiled"
>configure: WARNING: glm/glm.hpp: proceeding with the compiler's result
>checking for glm/glm.hpp... no
>configure: error: glm/glm.hpp not found. install glm

Yeah, I know. Happens since gcc 7.3

>Full build log is attached.

Is not really helpful. The root cause is (see config.log):

configure:28374: checking glm/glm.hpp usability
configure:28374: /usr/bin/ccache x86_64-linux-gnu-g++ -c -g -O2 
-fdebug-prefix-map=/data/rene/git/LibreOffice/master=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 conftest.cpp 
>&5
In file included from /usr/include/glm/detail/type_int.hpp:6:0,
 from /usr/include/glm/fwd.hpp:6,
 from /usr/include/glm/glm.hpp:61,
 from conftest.cpp:140:
/usr/include/glm/detail/setup.hpp:456:100: note: #pragma message: GLM: GCC 
older than 4.6 has a bug presenting the use of rgba and stpq components
 # pragma message("GLM: GCC older than 4.6 has a bug presenting the use of rgba 
and stpq components")

^
In file included from /usr/include/glm/detail/type_vec4.inl:968:0,
 from /usr/include/glm/detail/type_vec4.hpp:453,
 from /usr/include/glm/vec4.hpp:6,
 from /usr/include/glm/glm.hpp:70,
 from conftest.cpp:140:
/usr/include/glm/detail/type_vec4_simd.inl: In static member function 'static 
glm::tvec4 glm::detail::compute_vec4_div::call(const glm::tvec4&, 
const glm::tvec4&)':
/usr/include/glm/detail/type_vec4_simd.inl:156:11: error: 'struct 
glm::tvec4' has no member named 'data'
Result.data = _mm_mul_ps(a.data, _mm_rcp_ps(b.data));
   ^~~~
[...]

Maybe I need to include an additonal header (as the real code does)? The 
configure check above just does

AC_LANG_PUSH([C++])
AC_CHECK_HEADER([glm/glm.hpp], [],
   [AC_MSG_ERROR([glm/glm.hpp not found. install glm])], [])
AC_LANG_POP([C++])

Judging from the above error message it _does_ see the other headers, though.

Anyways, this was worked around in the recent upload of LO 6.0.0 rc3:

libreoffice (1:6.0.0~rc3-1) experimental; urgency=medium

  * New upstream release candidate

  * debian/patches/apparmor-fixes.diff: add patch from master with syntax
fixes. Also include X abstractions and allow .mozilla/firefox/** reading
  * debian/patches/apparmor-updates.diff: more gpg stuff: gpg(sm), .gnupg/*
  (both together closes: #887593)
  * debian/rules, debian/source/include-binaries: temporarily use internal glm;
configure check fails since the gcc 7.3 upload

 -- Rene Engelhard   Sat, 27 Jan 2018 11:36:59 +0100

Guus, any idea?

Regards,

Rene

Processed: reassign 888661 to src:libreoffice, found 888661 in 1:5.4.4-1, found 888661 in 1:6.0.0~rc2-1 ...

[Debian Bug Tracking System]

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

> reassign 888661 src:libreoffice
Bug #888661 {Done: Rene Engelhard } [libreoffice] FTBFS: 
glm/glm.hpp: present but cannot be compiled
Bug reassigned from package 'libreoffice' to 'src:libreoffice'.
No longer marked as found in versions libreoffice/1:5.4.4-1 and 
libreoffice/1:6.0.0~rc2-1.
No longer marked as fixed in versions libreoffice/1:6.0.0~rc3-1.
> found 888661 1:5.4.4-1
Bug #888661 {Done: Rene Engelhard } [src:libreoffice] FTBFS: 
glm/glm.hpp: present but cannot be compiled
Marked as found in versions libreoffice/1:5.4.4-1 and reopened.
> found 888661 1:6.0.0~rc2-1
Bug #888661 [src:libreoffice] FTBFS: glm/glm.hpp: present but cannot be compiled
Marked as found in versions libreoffice/1:6.0.0~rc2-1.
> close 888661 1:6.0.0~rc3-1
Bug #888661 [src:libreoffice] FTBFS: glm/glm.hpp: present but cannot be compiled
Marked as fixed in versions libreoffice/1:6.0.0~rc3-1.
Bug #888661 [src:libreoffice] FTBFS: glm/glm.hpp: present but cannot be compiled
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#888663: libtemplate-perl: FTBFS with debhelper/11.1

[Niels Thykier]

Package: libtemplate-perl
Version: 2.24-1.2
Severity: serious
Tags: patch


Hi,

The libtemplate-perl package FTBFS with debhelper/11.1 as its build
target is not safe to run multiple times. However, since
debhelper/11.1 this is occurs becase we had to fix a bug in
debhelper's handling of "explicitly defined rules targets".

In the concrete case, it is appears to be relaitively simple to
convert libtemplate-perl to use override targets rather than the
deprecated manual sequence control parameters.  I have attached
a patch for this.

More details can be found in:
 * #886901 comment #35
 * #887688 comment #37
 * #880840

Apologies for the inconvenience.

Thanks,
~Niels
>From cf111ede34f6b34ecad12531e826e523c54b4a55 Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sun, 28 Jan 2018 14:26:30 +
Subject: [PATCH] Rewrite d/rules to avoid deprecated dh sequence ctrl
 parameters

Signed-off-by: Niels Thykier 
---
 debian/rules | 10 --
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/debian/rules b/debian/rules
index db25e51..8480199 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,18 +2,16 @@
 %:
dh $@
 
-build:
-   dh build --before dh_auto_configure
+override_dh_auto_configre:
[ ! -f $(CURDIR)/lib/Template/Config.pm.orig ] && cp 
$(CURDIR)/lib/Template/Config.pm $(CURDIR)/lib/Template/Config.pm.orig
-   dh build --remaining
+   dh_auto_configure
 
 override_dh_installdocs:
dh_installdocs -X.svn/
 
-clean:
-   dh clean --until dh_auto_clean
+override_dh_auto_clean:
+   dh_auto_clean
rm -f $(CURDIR)/.defaults.cfg
rm -f $(CURDIR)/t/test/src/divisionbyzero.ttc
rm -rf $(CURDIR)/t/test/tmp/cache/*
[ ! -f $(CURDIR)/lib/Template/Config.pm.orig ] || mv -f 
$(CURDIR)/lib/Template/Config.pm.orig $(CURDIR)/lib/Template/Config.pm
-   dh clean --remaining
-- 
2.15.1

Processed: Re: Bug#888661: "configure: error: glm/glm.hpp not found. install glm" although libglm-dev is installed

[Debian Bug Tracking System]

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

> severity 888661 serious
Bug #888661 [libreoffice] "configure: error: glm/glm.hpp not found. install 
glm" although libglm-dev is installed
Severity set to 'serious' from 'normal'
> retitle 888661 FTBFS: glm/glm.hpp: present but cannot be compiled
Bug #888661 [libreoffice] "configure: error: glm/glm.hpp not found. install 
glm" although libglm-dev is installed
Changed Bug title to 'FTBFS: glm/glm.hpp: present but cannot be compiled' from 
'"configure: error: glm/glm.hpp not found. install glm" although libglm-dev is 
installed'.
> found 888661 1:6.0.0~rc2-1
Bug #888661 [libreoffice] FTBFS: glm/glm.hpp: present but cannot be compiled
Marked as found in versions libreoffice/1:6.0.0~rc2-1.
> close 888661 1:6.0.0~rc3-1
Bug #888661 [libreoffice] FTBFS: glm/glm.hpp: present but cannot be compiled
Marked as fixed in versions libreoffice/1:6.0.0~rc3-1.
Bug #888661 [libreoffice] FTBFS: glm/glm.hpp: present but cannot be compiled
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#876592: gconf: diff for NMU version 3.2.6-4.1

[Simon McVittie]

On Sun, 28 Jan 2018 at 06:29:19 +0200, Adrian Bunk wrote:
> I've prepared an NMU for gconf (versioned as 3.2.6-4.1) and uploaded
> it to DELAYED/5.
...
> +  * Update gtk-doc.make from gtk-doc-tools 1.27-1,
> +fixing a FTBFS with gtk-doc-tools >= 1.26. (Closes: #876592)

This seems a reasonable solution. Feel free to reschedule to DELAYED/0.
gconf has been dead upstream since about 2010, and is one of the obsolete
packages that the GNOME team are trying to avoid including in buster,
so GNOME maintainers are unlikely to be uploading it any time soon.

Since this is an obsolete package, the solution proposed by John Paul
Adrian Glaubitz (not building the documentation at all) would also have
been reasonable: there is less need for documentation for libraries that
we actively don't want people to be developing against.

FYI, for packages with a sufficiently recent/sane Autotools setup to
be compatible with an autoreconf with current Autotools (which I was
surprised to see seems to include gconf), I think the canonical way to
fix this class of bug is to ensure that dh-autoreconf runs gtkdocize,
either by running upstream's autogen.sh (if it's in the tarball):

https://salsa.debian.org/gnome-team/gtk3/commit/490e3220dfc976d181aab3e89c34e7a75080d94a

or by providing a simplified version ourselves:

https://salsa.debian.org/debian/flatpak/commit/d8004c50ffb6c99e20a77873e8cf48967afddfe8
https://salsa.debian.org/debian/flatpak/commit/8686daaf43a6d5674d1d545435f19b89773790b4

That doesn't seem like something that would justify a re-upload, though.

Thanks,
smcv

Bug#886116: marked as done (FTBFS: chown: cannot access '.../t.so': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 15:12:06 +0100
with message-id <20180128141206.ej5zutntnizsl...@angband.pl>
and subject line Re: FTBFS: chown: cannot access '.../t.so': No such file or 
directory
has caused the Debian Bug report #886116,
regarding FTBFS: chown: cannot access '.../t.so': No such file or directory
to be marked as done.

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

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


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

Hi!
I'm afraid your package fails to build:

   dh_fixperms
chown: cannot access 'debian/xppaut/usr/share/doc/xppaut/examples/ode/t.so': No 
such file or directory
chown: cannot access 
'debian/xppaut/usr/share/doc/xppaut/examples/ode/testbd.ps': No such file or 
directory
dh_fixperms: find debian/xppaut -true -print0 2>/dev/null | xargs -0r chown 
--no-dereference 0:0 returned exit cod
e 123
dh_fixperms: Aborting due to earlier error

Tested on armhf and amd64.  Log attached.


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

Kernel: Linux 4.15.0-rc6-00272-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


xppaut_armhf.build
Description: inode/symlink
--- End Message ---
--- Begin Message ---
On Sun, Jan 28, 2018 at 04:30:01AM +0100, Andreas Beckmann wrote:
> Control: tag -1 moreinfo
> On Tue, 02 Jan 2018 14:32:03 +0100 Adam Borowski  wrote:
> >dh_fixperms
> > chown: cannot access 
> > 'debian/xppaut/usr/share/doc/xppaut/examples/ode/t.so': No such file or 
> > directory
> > chown: cannot access 
> > 'debian/xppaut/usr/share/doc/xppaut/examples/ode/testbd.ps': No such file 
> > or directory
> > dh_fixperms: find debian/xppaut -true -print0 2>/dev/null | xargs -0r chown 
> > --no-dereference 0:0 returned exit cod
> > e 123
> > dh_fixperms: Aborting due to earlier error
> 
> I cannot reproduce this failure in pbuilder (amd64, i386,
> armhf in qemubuilder on amd64).
> Can you still reproduce it with current debhelper?

I can't!

And in December and early January I could, on multiple different machines
(also arm64, another amd64).

Closing, as no one unpays us for bug archaeology.  If it was debhelper or
some other piece of the toolchain, whatever was the cause should be ok.  If,
instead, there's a hash of phase of the moon somewhere, the bug will return
and only then it'd be worth looking into.

> Two things I noticed in your log:
> 
> * dh_compress did not emit the compat level deprecation warning:
>   "dh_compress: Compatibility levels before 9 are deprecated (level 7 in use)"
> 
> Is this a pristine dh_compress? The error sounds like a file system race
> between dh_compress and dh_fixperms (s.t. find sees the uncompressed files
> but chown only sees the compressed ones), but these two shouldn't run in
> parallel ...

Pristine.

> * the disk space calculation failed:
> 
> /usr/bin/du: cannot access 
> '/<>/xppaut-6.11b+1.dfsg/debian/xppaut/usr/share/doc/xppaut/examples/ode/t.so':
>  No such file or directory
> /usr/bin/du: cannot access 
> '/<>/xppaut-6.11b+1.dfsg/debian/xppaut/usr/share/doc/xppaut/examples/ode/testbd.ps':
>  No such file or directory
> E: read_command failed to execute du
> E: Cannot determine space needed for /<>/xppaut-6.11b+1.dfsg (du 
> failed)
> 
> That sounds fishy ... kind of a filesystem problem?

Shouldn't be -- I tried multiple machines, multiple filesystems, multiple
architectures.

Multiple filesystems rule out
https://github.com/torvalds/linux/commit/e4fd493c0541d36953f7b9d3bfced67a1321792f
which would look like a likely cause had I tested btrfs only.

On the other hand, no machine had a kernel older than 4.14 (official buildds
all run 4.9 and 3.16 AFAIK), so kernel issue can't be ruled out.  I had
since upgraded to newer 4.14 point / 4.15 rc releases, and assuming the
FTBFS doesn't return, downgrading would be a waste of time.

I'll instead recheck other packages which had similar issues -- machine time
is cheap, human time can be better spent fighting beers than bugs.  Which
I also recommend to you. :)


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What 

Processed: Raise severity now that gnome-python was removed from Testing

[Debian Bug Tracking System]

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

> severity 884997 serious
Bug #884997 [lottanzb] lottanzb: Please don't recommend python-gnome2
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#888654: mpv: CVE-2018-6360

[Salvatore Bonaccorso]

Source: mpv
Version: 0.23.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/mpv-player/mpv/issues/5456

Hi,

the following vulnerability was published for mpv.

CVE-2018-6360[0]:
| mpv through 0.28.0 allows remote attackers to execute arbitrary code
| via a crafted web site, because it reads HTML documents containing
| VIDEO elements, and accepts arbitrary URLs in a src attribute without a
| protocol whitelist in player/lua/ytdl_hook.lua. For example, an
| av://lavfi:ladspa=file= URL signifies that the product should call
| dlopen on a shared object file located at an arbitrary local pathname.
| The issue exists because the product does not consider that youtube-dl
| can provide a potentially unsafe URL.

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-6360
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6360
[1] https://github.com/mpv-player/mpv/issues/5456

Regards,
Salvatore

Bug#887575: marked as done (castle-game-engine FTBFS with fpc 3.0.4)

[Debian Bug Tracking System]

Your message dated Sun, 28 Jan 2018 12:50:26 +
with message-id 
and subject line Bug#887575: fixed in castle-game-engine 6.2+dfsg1-2
has caused the Debian Bug report #887575,
regarding castle-game-engine FTBFS with fpc 3.0.4
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.)


-- 
887575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: castle-game-engine
Version: 6.2+dfsg1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/castle-game-engine.html

...
--- Building
dh_testdir
# Build the real engine
/usr/bin/make all
make[1]: Entering directory '/build/1st/castle-game-engine-6.2+dfsg1'
/usr/bin/make --no-print-directory build-using-fpmake
fpc fpmake.pp
Free Pascal Compiler version 3.0.4+dfsg-13 [2018/01/12] for x86_64
Copyright (c) 1993-2017 by Florian Klaempfl and others
Target OS: Linux for x86-64
Compiling fpmake.pp
Linking fpmake
/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
351 lines compiled, 0.4 sec
Running fpmake. If this fails saying that "rtl" is not found, remember to set 
FPCDIR environment variable, see http://wiki.freepascal.org/FPMake .
if [ '(' -n "/usr/lib/fpc/3.0.4" ')' -a \
 '(' 3.0.4 '!=' '2.6.4' ')' -a \
 '(' 3.0.4 '!=' '2.6.2' ')' ]; then \
   ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4" -v -o -Ur; \
else \
   ./fpmake -v -o -Ur; \
fi
The installer encountered the following error:
Could not find unit directory for dependency package "rtl"
Makefile:60: recipe for target 'build-using-fpmake' failed
make[2]: *** [build-using-fpmake] Error 1
--- End Message ---
--- Begin Message ---
Source: castle-game-engine
Source-Version: 6.2+dfsg1-2

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated castle-game-engine 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, 28 Jan 2018 13:09:54 +0100
Source: castle-game-engine
Binary: fp-units-castle-game-engine castle-game-engine-doc 
castle-game-engine-src
Architecture: source
Version: 6.2+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Paul Gevers 
Description:
 castle-game-engine-doc - Castle Game Engine - Developer's Documentation
 castle-game-engine-src - Castle Game Engine - Source code for Lazarus 
integration
 fp-units-castle-game-engine - Castle Game Engine - 3D game engine for 
FreePascal / Lazarus
Closes: 868790 887575
Changes:
 castle-game-engine (6.2+dfsg1-2) unstable; urgency=medium
 .
   * Don't set FPCDIR in d/rules (Closes: #887575)
   * Add patch for reproducible builds (Closes: #868790) Thanks Lamby.
   * Bump dephelper compat level to 11 and set Rules-Requires-Root to no
Checksums-Sha1:
 7d826b22697674692267615aae84e1c48b0a499d 2312 
castle-game-engine_6.2+dfsg1-2.dsc
 a434cc1fb63fa75f072347925e48510af1635b84 23312 
castle-game-engine_6.2+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 8f19d6d46120b559611db7bf34042c74d6970bb58f3b57fa2d7d0a710ff2435b 2312 
castle-game-engine_6.2+dfsg1-2.dsc
 7d3b7e83f6c353e7b1fc726c64db5a9a13098ce48da2170611054a5edbd8d5b8 23312 
castle-game-engine_6.2+dfsg1-2.debian.tar.xz
Files:
 5437d05c7ee415deb02a050b2a4ae4cc 2312 misc optional 
castle-game-engine_6.2+dfsg1-2.dsc
 9c5c089c55846e755c87d2053d865a1e 23312 misc optional 
castle-game-engine_6.2+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlptviYACgkQnFyZ6wW9
dQq0yAgAzZpd1xZuNqrjOdbAQvDnBT1If37VwgHg6N/iu5St9a4xeEbotA4bUd+d
DTotVLFVxkpv+aOV1Jf+houF1QeZ0FlLIrVw6RBgWsEuRxxNqiWtSLcPjdKU3mGG
HsSgBHV9QHsX4J2fGA5Qc9Zqtl9TpEfctTWJUeJtDHeXUat9QVaID4HtgPfjnuhq
/B8q10Aqbb/xLr03hm8Z8szp5evAZP8PuuFnvn0G2zp2Rb5MZ99Vjwgg4PKJnH1T
WU1FuSyQVYx4LTB+sEvq/9Sp7j3nkRMlaG5wjh/k/UnsmHV09RmX1fsfBJnBxnc8
Ur63Il9MAmhHJvOQ9mcjIz7Bbo8JEQ==
=DEnX

Bug#888199: Fwd: Bug#888199: gnome-shell crashes at different circumstances (not usable anymore)

[Thomas Renard]

Oups, no Cc: to the bug list...


 Weitergeleitete Nachricht 
Betreff: Re: Bug#888199: gnome-shell crashes at different circumstances
(not usable anymore)
Datum: Sat, 27 Jan 2018 20:19:13 +0100
Von: Thomas Renard 
An: Simon McVittie 



Am 26.01.2018 um 18:09 schrieb Simon McVittie:
> Control: tags -1 + moreinfo

>> Would you be able to install systemd-coredump, upgrade libgjs0g to the
>> broken version, let gnome-shell crash a few times, downgrade back to
>> 1.50.2-2 so you can get back into a working GUI, and report what was
>> logged about the crashes?
> 

I am sorry, I did not have the time till now to make this analyzing
stuff. If you still need it I will try in the next days (1.50.2-3 was
not stable too...)

> I've uploaded version 1.50.3-2 which reverts some of the upstream changes
> that were brought in with 1.50.2-3. When it has built and propagated to
> your mirror, please could you try that version and report whether it's
> stable for you? This would be useful information in working out how to
> fix this properly. Be prepared to downgrade back to 1.50.2-2 if that
> doesn't work.
> 

Ok, version 1.50.3-2 seems to work. I enabled notifications again and
some extensions and everything looks fine by now. No crash till now.

But as we know: this version now is as "buggy" (bug overlay...) as
1.50.2-2 so are there any efforts to debug the problem further (e. g.
via #887082 or #881301) - then I would try to help in the next days.

Thomas

Bug#888606: [Debian-science-sagemath] Fwd: Bug#888606: cysignals: FTBFS with debhelper/11.1 due to empty build target

[Ximin Luo]

I saw some issue, I forgot where, that pointed out both mpfr4 and mpfr6 were 
getting pulled into certain builds. You could check your sbuild logs to see if 
both are getting installed.

X

Tobias Hansen:
> Hi,
> 
> yes, I think you can update cysignals in unstable. I applied upstream patches 
> for new mpfr and matplotlib versions to sagemath and built it with both 
> versions of cysignals yesterday and got the same problems:
> 
> sage -t --long src/sage/rings/number_field/number_field.py  # Bad exit: 1
> sage -t --long src/sage/rings/polynomial/plural.pyx  # Killed due to 
> segmentation fault
> sage -t --long src/sage/structure/factorization_integer.py  # Killed due to 
> kill signal
> sage -t --long src/sage/structure/sage_object.pyx  # Killed due to abort
> 
> I have had the failure with number_field.py on my computer for a while, but 
> it doesn't happen on buildds. The others are new, but I don't even know if 
> the libmpfr6 transition is finished...
> 
> Best,
> Tobias
> 
> 
> On 01/28/2018 06:11 AM, Jerome BENOIT wrote:
>> Hello,
>>
>> this issue was fixed in 1.6.6+ds-2 which is current in experimental:
>> can we migrate cysingals 1.6.6+ds-2 to unstable ?
>>
>> Thanks,
>> Jerome
>>
>>
>>  Forwarded Message 
>> Subject: Bug#888606: cysignals: FTBFS with debhelper/11.1 due to empty build 
>> target
>> Resent-Date: Sat, 27 Jan 2018 17:51:02 +
>> Resent-From: Niels Thykier 
>> Resent-To: debian-bugs-d...@lists.debian.org
>> Resent-CC: Jerome Benoit 
>> Date: Sat, 27 Jan 2018 18:44:34 +0100
>> From: Niels Thykier 
>> Reply-To: Niels Thykier , 888...@bugs.debian.org
>> To: Debian Bug Tracking System 
>>
>> Source: cysignals
>> Version: 1.6.5+ds-2
>> Severity: serious
>> Tags: patch
>>
>> Hi,
>>
>> The cysignals package FTBFS with debhelper/11.1 as it has an empty
>> build target.  This is caused by debhelper had a bug in its handling
>> of "explicitly defined rules targets" that has now been fixed.
>>
>> Previously, this happened to work because dpkg-buildpackage would
>> invoke "debian/rules build" (which would be a no-op) followed by
>> "fakeroot debian/rules binary".  During the binary target, dh's
>> suboptimal handling would run the build commands.
>>
>>
>> The solution is trivial but less pretty; explicitly define "build"
>> with the same content as the "%:" target (or rename the "build" folder
>> and drop the ".PHONY" target).  I have attached a patch for this.
>>
>>
>> More details can be found in:
>>  * #886901 comment #35
>>  * #887688 comment #37
>>  * #880840
>>
>> Apologies for the inconvenience.
>>
>> Thanks,
>> ~Niels
>>
>>
>>
>> ___
>> Debian-science-sagemath mailing list
>> debian-science-sagem...@lists.alioth.debian.org
>> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
> 
> 
> 
> 
> 
> ___
> Debian-science-sagemath mailing list
> debian-science-sagem...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#888606: [Debian-science-sagemath] Fwd: Bug#888606: cysignals: FTBFS with debhelper/11.1 due to empty build target

[Tobias Hansen]

Hi,

yes, I think you can update cysignals in unstable. I applied upstream patches 
for new mpfr and matplotlib versions to sagemath and built it with both 
versions of cysignals yesterday and got the same problems:

sage -t --long src/sage/rings/number_field/number_field.py  # Bad exit: 1
sage -t --long src/sage/rings/polynomial/plural.pyx  # Killed due to 
segmentation fault
sage -t --long src/sage/structure/factorization_integer.py  # Killed due to 
kill signal
sage -t --long src/sage/structure/sage_object.pyx  # Killed due to abort

I have had the failure with number_field.py on my computer for a while, but it 
doesn't happen on buildds. The others are new, but I don't even know if the 
libmpfr6 transition is finished...

Best,
Tobias


On 01/28/2018 06:11 AM, Jerome BENOIT wrote:
> Hello,
>
> this issue was fixed in 1.6.6+ds-2 which is current in experimental:
> can we migrate cysingals 1.6.6+ds-2 to unstable ?
>
> Thanks,
> Jerome
>
>
>  Forwarded Message 
> Subject: Bug#888606: cysignals: FTBFS with debhelper/11.1 due to empty build 
> target
> Resent-Date: Sat, 27 Jan 2018 17:51:02 +
> Resent-From: Niels Thykier 
> Resent-To: debian-bugs-d...@lists.debian.org
> Resent-CC: Jerome Benoit 
> Date: Sat, 27 Jan 2018 18:44:34 +0100
> From: Niels Thykier 
> Reply-To: Niels Thykier , 888...@bugs.debian.org
> To: Debian Bug Tracking System 
>
> Source: cysignals
> Version: 1.6.5+ds-2
> Severity: serious
> Tags: patch
>
> Hi,
>
> The cysignals package FTBFS with debhelper/11.1 as it has an empty
> build target.  This is caused by debhelper had a bug in its handling
> of "explicitly defined rules targets" that has now been fixed.
>
> Previously, this happened to work because dpkg-buildpackage would
> invoke "debian/rules build" (which would be a no-op) followed by
> "fakeroot debian/rules binary".  During the binary target, dh's
> suboptimal handling would run the build commands.
>
>
> The solution is trivial but less pretty; explicitly define "build"
> with the same content as the "%:" target (or rename the "build" folder
> and drop the ".PHONY" target).  I have attached a patch for this.
>
>
> More details can be found in:
>  * #886901 comment #35
>  * #887688 comment #37
>  * #880840
>
> Apologies for the inconvenience.
>
> Thanks,
> ~Niels
>
>
>
> ___
> Debian-science-sagemath mailing list
> debian-science-sagem...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath

Bug#888101: [Pkg-ime-devel] Bug#888101: Bug#888101: libpinyin13-dev ships same files as libpinyin7-dev without Conflicts

[陳昌倬]

On Sun, Jan 28, 2018 at 07:09:15PM +0800, ChangZhuo Chen wrote:
> On Tue, Jan 23, 2018 at 07:08:06AM -0500, Jeremy Bicha wrote:
> > Package: libpinyin13-dev
> > Version: 2.1.0-1~exp3
> > Severity: serious
> > 
> > libpinyin13-dev and libpinyin7-dev both include these files:
> > 
> > /usr/lib/x86_64-linux-gnu/libpinyin.a
> > /usr/lib/x86_64-linux-gnu/libpinyin.so
> > /usr/lib/x86_64-linux-gnu/pkgconfig/
> > /usr/lib/x86_64-linux-gnu/pkgconfig/libpinyin.pc
> > 
> > I think you need to add Conflicts: libpinyin7-dev.
> 
> The Conflicts is set indirectly through libpinyin7 and libpinyin13, but
> I think set it expliticly is also a good idea.

The current control is:

  Package: libpinyin13-dev
  Provides: libpinyin-dev
  Conflicts: libpinyin-dev

And after checking the policy, I think it falls to the following case
described in policy:

  Conflicts should be used
  ..
* in conjunction with Provides when only one package providing a given 
virtual facility may be unpacked at a time (see Virtual packages - Provides),

So I think we don't need to Conflicts libpinyin7-dev.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Processed: retitle 886683 to electrum: CVE-2018-1000022

[Debian Bug Tracking System]

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

> retitle 886683 electrum: CVE-2018-122
Bug #886683 [electrum] electrum: Security vulnerability in electrum
Changed Bug title to 'electrum: CVE-2018-122' from 'electrum: Security 
vulnerability in electrum'.
> thanks
Stopping processing here.

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

Bug#888101: [Pkg-ime-devel] Bug#888101: libpinyin13-dev ships same files as libpinyin7-dev without Conflicts

[陳昌倬]

On Tue, Jan 23, 2018 at 07:08:06AM -0500, Jeremy Bicha wrote:
> Package: libpinyin13-dev
> Version: 2.1.0-1~exp3
> Severity: serious
> 
> libpinyin13-dev and libpinyin7-dev both include these files:
> 
> /usr/lib/x86_64-linux-gnu/libpinyin.a
> /usr/lib/x86_64-linux-gnu/libpinyin.so
> /usr/lib/x86_64-linux-gnu/pkgconfig/
> /usr/lib/x86_64-linux-gnu/pkgconfig/libpinyin.pc
> 
> I think you need to add Conflicts: libpinyin7-dev.

The Conflicts is set indirectly through libpinyin7 and libpinyin13, but
I think set it expliticly is also a good idea.

> See Debian Policy § 7.4
> https://www.debian.org/doc/debian-policy/#conflicting-binary-packages-conflicts
> 
> By the way, why haven't you uploaded the new libpinyin to unstable yet?

Just too busy to do so, I am working on it now.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Processed: GitHub issue for Debian Bug#888157

[Debian Bug Tracking System]

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

> forwarded 888157 https://github.com/landscapeio/pylint-celery/issues/6
Bug #888157 [src:pylint-celery] pylint-celery FTBFS and Debci failure: 
ImportError: cannot import name make_tests
Set Bug forwarded-to-address to 
'https://github.com/landscapeio/pylint-celery/issues/6'.
> thanks
Stopping processing here.

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

Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring

[Pietro Battiston]

Il giorno dom, 31/12/2017 alle 17.13 -0500, Jeremy Bicha ha scritto:
> On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston  .it> wrote:
> > given that gallery is dead upstream since 2014
> > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to
> > orphan
> > this package (which I'm using no more).
> > 
> > In fact, gallery-uploader (and its dependency python-galleryremote)
> > never supported Gallery 3, and hence were officially obsolete since
> > since way before.
> 
> In that case, could you consider requesting those two packages be
> removed instead of orphaning them?

Done: #888645, #888646

Pietro