date:20180104

Your message dated Fri, 05 Jan 2018 05:40:58 +
with message-id 
and subject line Bug#886374: fixed in texlive-extra 2017.20180103-2
has caused the Debian Bug report #886374,
regarding texlive-latex-extra and emboss: error when trying to install together
to be marked as done.

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

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


-- 
886374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emboss,texlive-latex-extra
Version: emboss/6.6.0+dfsg-6+b1
Version: texlive-latex-extra/2017.20180103-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2018-01-04
Architecture: amd64
Distribution: sid

Hi,

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


Unpacking texlive-base (2017.20180103-1) ...
Selecting previously unselected package texlive-latex-base.
Preparing to unpack .../texlive-latex-base_2017.20180103-1_all.deb ...
Unpacking texlive-latex-base (2017.20180103-1) ...
Selecting previously unselected package texlive-latex-recommended.
Preparing to unpack .../texlive-latex-recommended_2017.20180103-1_all.deb ...
Unpacking texlive-latex-recommended (2017.20180103-1) ...
Selecting previously unselected package texlive-pictures.
Preparing to unpack .../texlive-pictures_2017.20180103-1_all.deb ...
Unpacking texlive-pictures (2017.20180103-1) ...
Selecting previously unselected package texlive-latex-extra.
Preparing to unpack .../texlive-latex-extra_2017.20180103-1_all.deb ...
Unpacking texlive-latex-extra (2017.20180103-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/texlive-latex-extra_2017.20180103-1_all.deb (--unpack):
 trying to overwrite '/usr/bin/wordcount', which is also in package emboss 
6.6.0+dfsg-6+b1
Processing triggers for libc-bin (2.26-1) ...
Processing triggers for man-db (2.7.6.1-4) ...
Processing triggers for install-info (6.5.0.dfsg.1-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/texlive-latex-extra_2017.20180103-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/bin/wordcount

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

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2017.20180103-2

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
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, 05 Jan 2018 12:30:50 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-plain-generic texlive-latex-extra 
texlive-fonts-extra texlive-music

Bug#886361: marked as done (apertium: frequent parallel FTBFS)

Your message dated Fri, 05 Jan 2018 05:04:06 +
with message-id 
and subject line Bug#886361: fixed in apertium 3.4.2~r68466-4
has caused the Debian Bug report #886361,
regarding apertium: frequent parallel FTBFS
to be marked as done.

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

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


-- 
886361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium
Version: 3.4.2~r68466-3
Severity: serious
Tags: patch

https://tests.reproducible-builds.org/debian/history/apertium.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium.html
https://buildd.debian.org/status/package.php?p=apertium=sid

...
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -Wall -Wextra -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -o apertium-filter-ambiguity 
apertium_filter_ambiguity.o -llttoolbox3 -lxml2 -lpcre -lapertium3 -lpcreposix 
-lpcre -lpcrecpp -llttoolbox3 -lxml2 -lpcre
libtool: link: g++ -Wall -Wextra -g -O2 "-fdebug-prefix-map=/<>=." 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o apertium-filter-ambiguity apertium_filter_ambiguity.o  
-lapertium3 -lpcreposix -lpcrecpp -llttoolbox3 -lxml2 -lpcre
/usr/bin/ld: cannot find -lapertium3
collect2: error: ld returned 1 exit status
Makefile:1056: recipe for target 'apertium-filter-ambiguity' failed
make[3]: *** [apertium-filter-ambiguity] Error 1


This was triggered by dh comat >= 10 defaulting to parallel building.

Fix attached.
Description: Fix parallel FTBFS
 Tell automake that libapertium3 is a self-built library
 so that proper dependencies are added.
Author: Adrian Bunk 

--- apertium-3.4.2~r68466.orig/apertium/Makefile.am
+++ apertium-3.4.2~r68466/apertium/Makefile.am
@@ -226,7 +226,7 @@ apertium_DATA = deformat.xsl reformat.xs
 
 apertium_pretransfer_SOURCES = apertium_pretransfer.cc
 apertium_multiple_translations_SOURCES = apertium-multiple-translations.cc
-apertium_multiple_translations_LDADD = $(APERTIUM_LIBS) 
-lapertium$(GENERIC_MAJOR_VERSION)
+apertium_multiple_translations_LDADD = $(APERTIUM_LIBS) libapertium3.la
 apertium_destxt_SOURCES = apertium_destxt.cc
 apertium_retxt_SOURCES = apertium_retxt.cc
 apertium_deshtml_SOURCES = apertium_deshtml.cc
@@ -249,55 +249,55 @@ apertium_repptx_SOURCES = apertium_reppt
 apertium_desmediawiki_SOURCES = apertium_desmediawiki.cc
 apertium_remediawiki_SOURCES = apertium_remediawiki.cc
 apertium_prelatex_SOURCES = apertium_prelatex.cc
-apertium_prelatex_LDADD= $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_prelatex_LDADD= $(APERTIUM_LIBS) libapertium3.la
 apertium_postlatex_SOURCES = apertium_postlatex.cc
-apertium_postlatex_LDADD= $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_postlatex_LDADD= $(APERTIUM_LIBS) libapertium3.la
 apertium_postlatex_raw_SOURCES = apertium_postlatex_raw.cc
-apertium_postlatex_raw_LDADD= $(APERTIUM_LIBS) 
-lapertium$(GENERIC_MAJOR_VERSION)
+apertium_postlatex_raw_LDADD= $(APERTIUM_LIBS) libapertium3.la
 
 apertium_tagger_SOURCES = apertium_tagger.cc
-apertium_tagger_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_tagger_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_tmxbuild_SOURCES = apertium_tmxbuild.cc
-apertium_tmxbuild_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_tmxbuild_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_preprocess_transfer_SOURCES = transferpp.cc
 apertium_preprocess_transfer_LDADD = $(APERTIUM_LIBS) \
- -lapertium$(GENERIC_MAJOR_VERSION)
+ libapertium3.la
 
 apertium_filter_ambiguity_SOURCES = apertium_filter_ambiguity.cc
 apertium_filter_ambiguity_LDADD = $(APERTIUM_LIBS) \
-  -lapertium$(GENERIC_MAJOR_VERSION)
+  libapertium3.la
 
 apertium_transfer_SOURCES = apertium_transfer.cc
-apertium_transfer_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_transfer_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_interchunk_SOURCES = apertium_interchunk.cc
-apertium_interchunk_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_interchunk_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_postchunk_SOURCES = apertium_postchunk.cc
-apertium_postchunk_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_postchunk_LDADD = $(APERTIUM_LIBS) libapertium3.la

Bug#884230: texlive-base: cmbcsc10 moved to texlive-fonts-extra

2018-01-04 Thread Norbert Preining

> Oh dear:

> Need to get 336 MB/343 MB of archives.
> After this operation, 960 MB of additional disk space will be used.

I know. The problem is old and known, namely that many TeX documents
search fonts not via fontconfig but via file name, and thus the fonts
have to be in the texmf tree (at least as links to the actual files).
THis *has* losts of advantages because fontconfig often messes up font
selection when large sets of fonts (osc, expert, ...) are available.

I am contemplating a different solution now (separate package
texlive-fontlinks that ships the links and dependencies, but is not
automatically installed).

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#882247:

2018-01-04 Thread Marco d'Itri

On Jan 05, Mike Hommey  wrote:

> There is something wrong with the default locale. Try installing a
> locale package (even firefox-l10n-en-gb) or downgrade to 57.
Confirmed, this fixes it.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#882247:

2018-01-04 Thread Mike Hommey

There is something wrong with the default locale. Try installing a
locale package (even firefox-l10n-en-gb) or downgrade to 57.

Mike

Bug#886367: marked as done (intel-microcode: coming updates for meltdown/spectre)

Your message dated Fri, 05 Jan 2018 03:35:31 +
with message-id 
and subject line Bug#886367: fixed in intel-microcode 3.20171215.1
has caused the Debian Bug report #886367,
regarding intel-microcode: coming updates for meltdown/spectre
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.)


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

Package: intel-microcode
Version: 3.20171117.1
Severity: grave

It's been rumored that Intel will be releasing microcode updates to 
(partially?) mitigate some of the effects of meltdown and spectre. It 
appears that the latest version on the website is still 20171117.


Any news of what this will be and when it will happen?

Thanks,

--
Matt Taggart
tagg...@debian.org
--- End Message ---
--- Begin Message ---
Source: intel-microcode
Source-Version: 3.20171215.1

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

Debian distribution maintenance software
pp.
Henrique de Moraes Holschuh  (supplier of updated 
intel-microcode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Jan 2018 23:04:38 -0200
Source: intel-microcode
Binary: intel-microcode
Architecture: source amd64
Version: 3.20171215.1
Distribution: unstable
Urgency: high
Maintainer: Henrique de Moraes Holschuh 
Changed-By: Henrique de Moraes Holschuh 
Description:
 intel-microcode - Processor microcode firmware for Intel CPUs
Closes: 886367
Changes:
 intel-microcode (3.20171215.1) unstable; urgency=high
 .
   * Add supplementary-ucode-CVE-2017-5715.d/: (closes: #886367)
 New upstream microcodes to partially address CVE-2017-5715
 + Updated Microcodes:
   sig 0x000306c3, pf_mask 0x32, 2017-11-20, rev 0x0023, size 23552
   sig 0x000306d4, pf_mask 0xc0, 2017-11-17, rev 0x0028, size 18432
   sig 0x000306f2, pf_mask 0x6f, 2017-11-17, rev 0x003b, size 33792
   sig 0x00040651, pf_mask 0x72, 2017-11-20, rev 0x0021, size 22528
   sig 0x000406e3, pf_mask 0xc0, 2017-11-16, rev 0x00c2, size 99328
   sig 0x000406f1, pf_mask 0xef, 2017-11-18, rev 0xb25, size 27648
   sig 0x00050654, pf_mask 0xb7, 2017-11-21, rev 0x23a, size 27648
   sig 0x000506c9, pf_mask 0x03, 2017-11-22, rev 0x002e, size 16384
   sig 0x000806e9, pf_mask 0xc0, 2017-12-03, rev 0x007c, size 98304
   sig 0x000906e9, pf_mask 0x2a, 2017-12-03, rev 0x007c, size 98304
   * Implements IBRS and IBPB support via new MSR (Spectre variant 2
 mitigation, indirect branches).  Support is exposed through cpuid(7).EDX.
   * LFENCE terminates all previous instructions (Spectre variant 2
 mitigation, conditional branches).
Checksums-Sha1:
 c474a75e175c04553cf6cf4a5f1164789117f4ff 1797 intel-microcode_3.20171215.1.dsc
 02ef58073ad7e3adbb841e8acd98610aa6d5cb5e 2177512 
intel-microcode_3.20171215.1.tar.xz
 d7d6f83f656fa33b05cf017132aded03f1e9d7b9 5522 
intel-microcode_3.20171215.1_amd64.buildinfo
 e4380986b6fb7e023684d4c206229bf852482148 1279728 
intel-microcode_3.20171215.1_amd64.deb
Checksums-Sha256:
 055a7f5f01644d6793c595f6b90875344ee79a0d4ab1078b7a1aec5c358e59d7 1797 
intel-microcode_3.20171215.1.dsc
 eca8efc0a6dc456a8723204477e229577c1079fa5c1a10b6ba95d11e261ffa4d 2177512 
intel-microcode_3.20171215.1.tar.xz
 ffc513983adc997cc938fd30685b8ee56c4257bdce2dd94fa92866cedc3e8017 5522 
intel-microcode_3.20171215.1_amd64.buildinfo
 78929ffb1de5db97468d0cb9d7bab8e3642e69af1c4c099056faadd9d419f68a 1279728 
intel-microcode_3.20171215.1_amd64.deb
Files:
 26745f6401d7fe5f63d398793676d5f3 1797 non-free/admin standard 
intel-microcode_3.20171215.1.dsc
 67c3e15bacf2171245243ee0cfde6f1c 2177512 non-free/admin standard 
intel-microcode_3.20171215.1.tar.xz
 869872d5035d458122f325f4318b61eb 5522 non-free/admin standard 
intel-microcode_3.20171215.1_amd64.buildinfo
 9dfc25b786ece3adb849ee570fc14636 1279728 non-free/admin standard 
intel-microcode_3.20171215.1_amd64.deb

Bug#883698: marked as done (freetype: incorrect shlibs file generation)

Your message dated Fri, 05 Jan 2018 03:35:05 +
with message-id 
and subject line Bug#883698: fixed in freetype 2.8.1-1
has caused the Debian Bug report #883698,
regarding freetype: incorrect shlibs file generation
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.)


-- 
883698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freetype
Version: 2.8.1-0.1
Severity: serious

(Please keep debian-b...@lists.debian.org in copy of your replies.)

Hi,

While preparing the release announcement for Buster Alpha 2, I've
stumbled upon the symbols addition in your last upload. Checking the
dependency for the udeb, it seems to be stuck at 2.6, while it should be
at the maximum version (udebs don't use symbols files):
| libfreetype 6 libfreetype6 (>= 2.6)
| udeb: libfreetype 6 libfreetype6-udeb (>= 2.6)

This is due to:
| dependency = $(libpkg) (>= 2.6)
| […]
| override_dh_makeshlibs:
| dh_makeshlibs -V '$(dependency)' --add-udeb '$(udebpkg)'


KiBi.
--- End Message ---
--- Begin Message ---
Source: freetype
Source-Version: 2.8.1-1

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

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated freetype 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, 05 Jan 2018 00:42:36 +
Source: freetype
Binary: libfreetype6 libfreetype6-dev freetype2-demos libfreetype6-udeb
Architecture: source amd64
Version: 2.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Steve Langasek 
Changed-By: Steve Langasek 
Description:
 freetype2-demos - FreeType 2 demonstration programs
 libfreetype6 - FreeType 2 font engine, shared library files
 libfreetype6-dev - FreeType 2 font engine, development files
 libfreetype6-udeb - FreeType 2 font engine for the debian-installer (udeb)
Closes: 642354 857439 863623 870618 871470 883698 885324
Changes:
 freetype (2.8.1-1) unstable; urgency=medium
 .
   * Acknowledge NMUs; thanks to Laurent for the uploads.
 Closes: #857439, #863623.
   * debian/control:
 - Add pkg-config to the Build-Depends list (Closes: #885324).
 - Mark libfreetype6-dev Multi-Arch: same (Closes: #642354).
 - Remove the deprecated Priority: extra field from libfreetype6-udeb.
   * debian/patches/patches-*: Refresh existing patches.
   * debian/patches/patches-freetype/freetype-config-multi-arch.patch:
 - Remove the arch-dependent output of `freetype-config --libs`.
   Closes: #871470, #870618.
 - Exit with an error if freetype-config is called with --libtool.
   * debian/rules:
 - Include /usr/share/dpkg/architecture.mk.
 - Dynamically generate the shlibs dependency version (Closes: #883698).
 - Replace the autoconf definition of SIZEOF_LONG with the compile-time
   constant __SIZEOF_LONG__ to make libfreetype6-dev multi-arch compatible.
   * Thanks to Hugh McMaster  for preparing these
 changes.
Checksums-Sha1:
 b39558bb99446bac4ca0e628642387a3eba51d04 2169 freetype_2.8.1-1.dsc
 16b71c399c01af13c12d3557ad48d0569e9b77d4 38084 freetype_2.8.1-1.diff.gz
 af7ecb933a2c655ca337bddf7748674262eea6ae 713812 
freetype2-demos-dbgsym_2.8.1-1_amd64.deb
 54991c352bdb0f845fe592eb92d61c39675808e8 122724 
freetype2-demos_2.8.1-1_amd64.deb
 b77fa624e6e827b6da373934f9bad6bb79b64388 7237 freetype_2.8.1-1_amd64.buildinfo
 a6a7a5090a3042b03c2d679e4ab286e3b0f53714 986492 
libfreetype6-dbgsym_2.8.1-1_amd64.deb
 18c62b67ee3eb1f41f6509691cf8a920d7bedc53 2656312 
libfreetype6-dev_2.8.1-1_amd64.deb
 8c6031e93653e7262240c5226dd1bf9144d226e1 315584 
libfreetype6-udeb_2.8.1-1_amd64.udeb
 89293e6942e9c2966fc97fc922b760cc27770856 460896 libfreetype6_2.8.1-1_amd64.deb
Checksums-Sha256:
 fce83b951da237e6cdd121c073453f12a3334f28dd2929c0ffd522f3b7c39c37 2169 
freetype_2.8.1-1.dsc
 29c8352fb95549f7c3c5994ccd032bb0346eca5c1abe29bb0890238a922f61f6 38084

Bug#882247:

2018-01-04 Thread Tom Marble

Mike:

There is something wrong with the default locale. Try installing a
> locale package (even firefox-l10n-en-gb) or downgrade to 57.


Turns out I can't install that from unstable (depends on firefox <<
57.0.3-1),
however I installed it from experimental (58.0~b4-1) and now firefox
works!!!

Thank you!

--Tom

Bug#886374: texlive-latex-extra and emboss: error when trying to install together

2018-01-04 Thread Ralf Treinen

Package: emboss,texlive-latex-extra
Version: emboss/6.6.0+dfsg-6+b1
Version: texlive-latex-extra/2017.20180103-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2018-01-04
Architecture: amd64
Distribution: sid

Hi,

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


Unpacking texlive-base (2017.20180103-1) ...
Selecting previously unselected package texlive-latex-base.
Preparing to unpack .../texlive-latex-base_2017.20180103-1_all.deb ...
Unpacking texlive-latex-base (2017.20180103-1) ...
Selecting previously unselected package texlive-latex-recommended.
Preparing to unpack .../texlive-latex-recommended_2017.20180103-1_all.deb ...
Unpacking texlive-latex-recommended (2017.20180103-1) ...
Selecting previously unselected package texlive-pictures.
Preparing to unpack .../texlive-pictures_2017.20180103-1_all.deb ...
Unpacking texlive-pictures (2017.20180103-1) ...
Selecting previously unselected package texlive-latex-extra.
Preparing to unpack .../texlive-latex-extra_2017.20180103-1_all.deb ...
Unpacking texlive-latex-extra (2017.20180103-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/texlive-latex-extra_2017.20180103-1_all.deb (--unpack):
 trying to overwrite '/usr/bin/wordcount', which is also in package emboss 
6.6.0+dfsg-6+b1
Processing triggers for libc-bin (2.26-1) ...
Processing triggers for man-db (2.7.6.1-4) ...
Processing triggers for install-info (6.5.0.dfsg.1-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/texlive-latex-extra_2017.20180103-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/bin/wordcount

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

-Ralf.

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

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: better log output

2018-01-04 Thread russell


On 2017-12-28 15:31, Michael Biebl wrote:

Control: tags -1 + moreinfo

Please install dbgsym packages for at least libnm0, libnma0 and
network-manager-gnome to get a more useful backtrace.
https://wiki.debian.org/HowToGetABacktrace



This is the output of gdb after installing a bunch of -dbgsym packages 
(including glib2.0-0). Let me know if I can get more info.


(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/bin/nm-applet
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

[New Thread 0x7fffeb8e0700 (LWP 5086)]
[New Thread 0x7fffeb0df700 (LWP 5087)]
[New Thread 0x7fffea037700 (LWP 5088)]
[New Thread 0x7fffe955f700 (LWP 5089)]
double free or corruption (out)

Thread 1 "nm-applet" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:51

#1  0x74afecf7 in __GI_abort () at abort.c:90
#2  0x74b3ff87 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x74c45bd8 "%s\n") at 
../sysdeps/posix/libc_fatal.c:181

#3  0x74b4627a in malloc_printerr (
str=str@entry=0x74c47828 "double free or corruption (out)") at 
malloc.c:5354

#4  0x74b47fd0 in _int_free (av=0x74e79c20 ,
p=0x74e79cf0 , have_lock=) at 
malloc.c:4278

#5  0x75108449 in g_strfreev (str_array=0x55926b10)
at ../../../../glib/gstrfuncs.c:2497
#6  0x750cb45b in g_datalist_clear (datalist=)
at ../../../../glib/gdataset.c:273
#7  0x753c5ea2 in g_object_unref (_object=0x5587e280)
at ../../../../gobject/gobject.c:3330
#8  0x750d5e41 in g_hash_table_foreach_remove_or_steal 
(hash_table=0x557ee360,
func=func@entry=0x76347010 <_setting_release>, 
user_data=0x55976720,

notify=notify@entry=1) at ../../../../glib/ghash.c:1500
#9  0x750d6cec in g_hash_table_foreach_remove 
(hash_table=,
func=func@entry=0x76347010 <_setting_release>, 
user_data=)

at ../../../../glib/ghash.c:1544
#10 0x76347187 in nm_connection_private_free 
(priv=0x559758e0)

at libnm-core/nm-connection.c:2711
#11 0x750cb45b in g_datalist_clear (datalist=)
at ../../../../glib/gdataset.c:273
#12 0x753c5ea2 in g_object_unref (_object=0x55976720)
at ../../../../gobject/gobject.c:3330
#13 0x5556a29c in applet_secrets_request_free 
(req=req@entry=0x559dab80)

at src/applet.c:2852
#14 0x5556d8fc in child_finished_cb (
pid=,
status=, 
user_data=0x559dab80,
user_data@entry=out>)

at src/applet-vpn-request.c:117
#15 0x750e4724 in g_child_watch_dispatch 
(source=source@entry=0x55bc93a0,
callback=, user_data=) at 
../../../../glib/gmain.c:5282

#16 0x750e7e15 in g_main_dispatch (context=0x5580ba20)
at ../../../../glib/gmain.c:3148
#17 g_main_context_dispatch (context=context@entry=0x5580ba20)
at ../../../../glib/gmain.c:3813
#18 0x750e81e0 in g_main_context_iterate 
(context=context@entry=0x5580ba20,
block=block@entry=1, dispatch=dispatch@entry=1, self=out>)

at ../../../../glib/gmain.c:3886
#19 0x750e826c in g_main_context_iteration 
(context=context@entry=0x5580ba20,

may_block=may_block@entry=1) at ../../../../glib/gmain.c:3947
#20 0x756a5bed in g_application_run (application=0x557f02b0,
---Type  to continue, or q  to quit---
argc=, argv=) at 
../../../../gio/gapplication.c:2401
#21 0x555641b1 in main (argc=, argv=out>) at src/main.c:81

Bug#750732: Pending fixes for bugs in the libanyevent-perl package

2018-01-04 Thread pkg-perl-maintainers

tag 750732 + pending
thanks

Some bugs in the libanyevent-perl package are closed in revision
b8e06b0cb8fe01a4451564a05dfec86db120b7d0 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libanyevent-perl.git/commit/?id=b8e06b0

Commit message:

Skip t/66_ioasync_03_child.t during build and autopkgtest

as it seems to suffer from a race condition.

Closes: #750732

Processed: Pending fixes for bugs in the libanyevent-perl package

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

> tag 750732 + pending
Bug #750732 [src:libanyevent-perl] libanyevent-perl: Intermittent build 
failures on various architectures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#750732: libanyevent-perl: Intermittent build failures on various architectures

2018-01-04 Thread gregor herrmann

On Mon, 01 Jan 2018 18:56:52 +0200, Niko Tyni wrote:

> The issue seems mostly specific to armel and hurd, although
> tests.reproducible-builds.org does have some failures on i386 (but no
> logs so those could be just testbed glitches or transient sid issues.)
> I don't know what happened in Ubuntu but it clearly built later.

Yup, it seems a bit undeterministic.

> Currently we have a build failure on armel that's blocking testing
> migration of this package. Given the number of reverse dependencies,
> I suppose we need to solve this one way or other.

Ack.

> Disregarding hurd-i386, the problematic test seems to be
> t/66_ioasync_03_signals.t, 

t/66_ioasync_02_signals.t or t/66_ioasync_03_child.t?
Anyway, IIRC we've seen failures in different tests over time.

> which is using AnyEvent::Impl::IOAsync
> which uses IO::Async. 

Ack, that's the whole t/66_ioasync_*.t block.

> I see the AnyEvent::Impl::IOAsync docs have some
> reservations about IO::Async, this in particular:

That, and more comments in the code and documentation about IO::Async.

> I'm not sure what to make of this. Maybe disarm this particular test somehow
> for now and see how it fares otherwise?

Which one exactly? :)
I tend to disable the whole t/66_ioasync_*.t group.
Or maybe not:

And, lo and behold, I could reproduce a test failure, on one of my
raspis, running Raspbian Buster (and under some load). There the test
suite was just hanging here:

t/66_ioasync_03_child.t 
1..50
ok 1
ok 2 # child 15124
ok 3 # 15124 == 15124
ok 4 # 3 == 768 >> 8 (768)
ok 5 # 15126 == 15126
ok 6 # 7 == 1792 >> 8 (1792)
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12 # child 15127

Of course this only happened once over the time I run the tests in a
loop so far ...

On 
https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.140-1=1505267718=0
it was

t/66_ioasync_02_signals.t .. 
1..5
ok 1
ok 2
ok 3
ok 4
ok 5
ok
Bailout called.  Further testing stopped:  No child exit detected. This is 
either a bug in AnyEvent or a bug in your Perl (mostly some windows 
distributions suffer from that): child watchers might not work properly on this 
platform. You can force installation of this module if you do not rely on child 
watchers, or you could upgrade to a working version of Perl for your platform.

(Does this mean that t/66_ioasync_02_signals.t failed or the
following t/66_ioasync_03_child.t ?)

Some other failures:
https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.120-1%2Bb1=1474787791=0
https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.120-1%2Bb1=1474805578=0
same as above

https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=sparc64=7.130-1=1476943760=0
t/66_ioasync_02_signals.t .. 
1..5
ok 1
ok 2
ok 3
ok 4
ok 5
ok
E: Caught signal ‘Terminated’: terminating immediatelydebian/rules:13: recipe 
for target 'override_dh_auto_test' failed

So basically the same.

https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=x32=7.070-3=1411189350=0
t/66_ioasync_02_signals.t .. ok
Bailout called.  Further testing stopped:  No child exit detected. This is 
either a bug in AnyEvent or a bug in your Perl (mostly some windows 
distributions suffer from that): child watchers might not work properly on this 
platform. You can force installation of this module if you do not rely on child 
watchers, or you could upgrade to a working version of Perl for your platform.

Same again.

Looks like t/66_ioasync_03_child.t is our candidate, if I'm
interpreting this correctly.

Oh, and I have another hang on my Raspi:

t/66_ioasync_03_child.t  
1..50
ok 1
ok 2 # child 22400
ok 3 # 22400 == 22400
ok 4 # 3 == 768 >> 8 (768)
ok 5 # 22401 == 22401
ok 6 # 7 == 1792 >> 8 (1792)
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12 # child 22402
ok 13 # 22402 == 22402
ok 14 # 3 == 768 >> 8 (768)
ok 15 # 22403 == 22403
ok 16 # 7 == 1792 >> 8 (1792)
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22 # child 22404
ok 23 # 22404 == 22404
ok 24 # 3 == 768 >> 8 (768)
ok 25 # 22405 == 22405
ok 26 # 7 == 1792 >> 8 (1792)
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32 # child 22406
ok 33 # 22406 == 22406
ok 34 # 3 == 768 >> 8 (768)
ok 35 # 22407 == 22407
ok 36 # 7 == 1792 >> 8 (1792)
ok 37
ok 38
ok 39
ok 40
ok 41
ok 42 # child 22408

Commit pushed to alioth, feedback welcome before I upload.

Cheers,
gregor

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

signature.asc
Description: Digital Signature

Bug#886367: partial fix uploaded

2018-01-04 Thread Henrique de Moraes Holschuh

Intel has released several updates already, but not all of them AFAIK.

These microcode updates are of little impact until the kernel changes to
activate the new MSRs are deployed.  But they do mess with conditional
jumps and LFENCE.

Anyway, uploading a partial, unofficial set of updates to unstable to
close the bug.  Several processors are still missing.  I expect an
official release from Intel soon, hopefully with updates for everything.

Everyone should look for firmware updates, the usual good vendors
already have them out, or will have them out by the end of the next
week.

-- 
  Henrique Holschuh

Processed: tagging 886367

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

> tags 886367 + pending
Bug #886367 [intel-microcode] intel-microcode: coming updates for 
meltdown/spectre
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#886367: intel-microcode: more meltdown/spectre info

2018-01-04 Thread Matt Taggart


I read that RHEL is already issuing microcode updates for RHEL7.
I read it second hand at
https://lists.bufferbloat.net/pipermail/cerowrt-devel/2018-January/08.html

But maybe there is an official URL somewhere?
I found the following pages
https://access.redhat.com/security/vulnerabilities/speculativeexecution
https://access.redhat.com/articles/3311301

But I couldn't find any reference to microcode versions.

--
Matt Taggart
tagg...@debian.org

Bug#886367: intel-microcode: coming updates for meltdown/spectre

2018-01-04 Thread Matt Taggart


Package: intel-microcode
Version: 3.20171117.1
Severity: grave

It's been rumored that Intel will be releasing microcode updates to 
(partially?) mitigate some of the effects of meltdown and spectre. It 
appears that the latest version on the website is still 20171117.


Any news of what this will be and when it will happen?

Thanks,

--
Matt Taggart
tagg...@debian.org

Bug#886359: marked as done (infinipath-psm FTBFS on i386: missing symbol ipath_dwordcpy_safe)

Your message dated Thu, 04 Jan 2018 22:20:57 +
with message-id 
and subject line Bug#886359: fixed in infinipath-psm 3.3+20.604758e7-4
has caused the Debian Bug report #886359,
regarding infinipath-psm FTBFS on i386: missing symbol ipath_dwordcpy_safe
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.)


-- 
886359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: infinipath-psm
Version: 3.3+20.604758e7-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=infinipath-psm=i386=3.3%2B20.604758e7-3=1515071279=0

...
   dh_makeshlibs -a -O--parallel
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: no debian/symbols file used as basis for generating 
debian/libpsm-infinipath1/DEBIAN/symbols
--- new_symbol_file (libpsm-infinipath1_3.3+20.604758e7-3_i386)
+++ dpkg-gensymbolscQjnKE   2018-01-04 13:07:52.434415479 +
@@ -32,7 +32,7 @@
  ipath_context_open@Base 3.3+7.gec1d6d2
  ipath_disarm_bufs@Base 3.3+7.gec1d6d2
  ipath_dwordcpy@Base 3.3+7.gec1d6d2
- ipath_dwordcpy_safe@Base 3.3+7.gec1d6d2
+#MISSING: 3.3+20.604758e7-3# ipath_dwordcpy_safe@Base 3.3+7.gec1d6d2
  ipath_event_ack@Base 3.3+7.gec1d6d2
  ipath_flash_csum@Base 3.3+7.gec1d6d2
  ipath_flush_egr_bufs@Base 3.3+7.gec1d6d2
dh_makeshlibs: failing due to earlier errors
debian/rules:15: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: infinipath-psm
Source-Version: 3.3+20.604758e7-4

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

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated infinipath-psm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Jan 2018 22:43:15 +0100
Source: infinipath-psm
Binary: libpsm-infinipath1 libpsm-infinipath1-dev libpsm-infinipath1-dbg
Architecture: source amd64
Version: 3.3+20.604758e7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Mehdi Dogguy 
Description:
 libpsm-infinipath1 - PSM Messaging library for Intel Truescale adapters
 libpsm-infinipath1-dbg - Debugging symbols for libpsm-infinipath1
 libpsm-infinipath1-dev - Development files for libpsm-infinipath1
Closes: 886359
Changes:
 infinipath-psm (3.3+20.604758e7-4) unstable; urgency=medium
 .
   * Add myself to Uploaders
   * Run wrap-and-sort
   * Mark symbol ipath_dwordcpy_safe@Base as amd64 specific (Closes: #886359)
   * Provide libpsm_infinipath.so.1 as an alternative
Checksums-Sha1:
 991ba7af7ce6ee16c775abf04c26c95a5532bb6d 2284 
infinipath-psm_3.3+20.604758e7-4.dsc
 772d9abeeb062988bb4e5ef0c7926f781a1b6eda 9164 
infinipath-psm_3.3+20.604758e7-4.debian.tar.xz
 b0a6329e8a7967467bc759103d9c91e6f2300044 6364 
infinipath-psm_3.3+20.604758e7-4_amd64.buildinfo
 ab63003b9e803f9de3921dd3b98953ce94519562 804120 
libpsm-infinipath1-dbg_3.3+20.604758e7-4_amd64.deb
 d45158ca01c25c7e25375721f9cd836ee07f6fc2 19668 
libpsm-infinipath1-dev_3.3+20.604758e7-4_amd64.deb
 519fc34520007bcc938f35ba0692b57954476811 172564 
libpsm-infinipath1_3.3+20.604758e7-4_amd64.deb
Checksums-Sha256:
 0dc41b3edfae769fc4f02720182c9824e1c5424619c5d8a32b37baab4f1edd45 2284 
infinipath-psm_3.3+20.604758e7-4.dsc
 501b51d9313ae0fde51b0778d427e7d694ac5cc449a0510604f6f22babda71e7 9164 
infinipath-psm_3.3+20.604758e7-4.debian.tar.xz
 cd69ac430b937fd7b08ec8f96555b92b97d7a8aef4af294db29c6cfcb0519143 6364 
infinipath-psm_3.3+20.604758e7-4_amd64.buildinfo
 1d3476efc6198cfaf6bdd9aefcc1290f9c2f9811df97845ebcb447df8056bf3e 804120 
libpsm-infinipath1-dbg_3.3+20.604758e7-4_amd64.deb
 de8b3e2086731cdc881fda67bfb8105ba6715032ffdb42caa3b1c38f1f56d8e5 19668 
libpsm-infinipath1-dev_3.3+20.604758e7-4_amd64.deb
 181ac3fcac4835349f3677c8c247920053759ac179e6c9f5475099782797db47 172564

Processed: limit source to infinipath-psm, tagging 886359

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

> limit source infinipath-psm
Limiting to bugs with field 'source' containing at least one of 'infinipath-psm'
Limit currently set to 'source':'infinipath-psm'

> tags 886359 + pending
Bug #886359 [src:infinipath-psm] infinipath-psm FTBFS on i386: missing symbol 
ipath_dwordcpy_safe
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#886355: marked as done (libpar-packer-perl: frequent parallel FTBFS)

Your message dated Thu, 04 Jan 2018 22:04:33 +
with message-id 
and subject line Bug#886355: fixed in libpar-packer-perl 1.041-2
has caused the Debian Bug report #886355,
regarding libpar-packer-perl: frequent parallel FTBFS
to be marked as done.

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

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


-- 
886355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpar-packer-perl
Version: 1.041-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libpar-packer-perl=sid

...
dh_auto_build
make -j6
make[2]: Entering directory '/<>'
cp script/par.pl blib/script/par.pl
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/par.pl
make[3]: Entering directory '/<>/myldr'
Makefile:855: warning: overriding recipe for target '.c.o'
Makefile:336: warning: ignoring old recipe for target '.c.o'
cp script/pp blib/script/pp
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/pp
cp script/tkpp blib/script/tkpp
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/tkpp
"/usr/bin/perl" par_pl2c.pl my_par_pl < ../script/par.pl > my_par_pl.c 
"/usr/bin/perl" sha1.c.PL
Can't locate PAR/Filter/PodStrip.pm in @INC (you may need to install the 
PAR::Filter::PodStrip module) (@INC contains: 
/<>/myldr/../blib/arch /<>/myldr/../blib/lib 
/etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/aarch64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/aarch64-linux-gnu/perl-base .) at par_pl2c.pl 
line 7.
BEGIN failed--compilation aborted at par_pl2c.pl line 7.
Makefile:879: recipe for target 'my_par_pl.c' failed
make[3]: *** [my_par_pl.c] Error 2


This is due to dh compat 10 defaulting to parallel building.

Ideally the build should be fixed to work with parallel building,
but if that's not easily possible the following patch to go back
to non-parallel building is sufficient to fix the bug:

--- debian/rules.old2018-01-04 20:32:58.184625753 +
+++ debian/rules2018-01-04 20:33:08.360625656 +
@@ -10,7 +10,7 @@
 ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
 
 %:
-   dh $@
+   dh $@ --no-parallel
 
 override_dh_auto_build:
dh_auto_build
--- End Message ---
--- Begin Message ---
Source: libpar-packer-perl
Source-Version: 1.041-2

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libpar-packer-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Jan 2018 22:36:26 +0100
Source: libpar-packer-perl
Binary: libpar-packer-perl
Architecture: source
Version: 1.041-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 886355
Description: 
 libpar-packer-perl - utility for creating PAR archives and stand-alone 
executables
Changes:
 libpar-packer-perl (1.041-2) unstable; urgency=medium
 .
   * debian/rules: disable parallel building.
 Thanks to Adrian Bunk for the bug report and the patch.
 (Closes: #886355)
Checksums-Sha1: 
 536a500ab257d72b4263823de09a5ae78ae227b9 2429 libpar-packer-perl_1.041-2.dsc
 6bad53f0507f0f97033c50e3133ba7c0782d807d 9524 
libpar-packer-perl_1.041-2.debian.tar.xz
Checksums-Sha256: 
 8425dfa53d687b1b6897177ab6e82b7aa1a7745d3ca03eedda1724397df4eb0f 2429 
libpar-packer-perl_1.041-2.dsc
 e4e3c48bc46e35ad7edd1e226a25bed3b9248f306be8a9f7906a901a48da2c4f 9524 
libpar-packer-perl_1.041-2.debian.tar.xz
Files: 
 83e9b8308f580e918f8ef462790a5e58 2429 perl optional 
libpar-packer-perl_1.041-2.dsc
 d6f11e33fd9d706d100d730f8cefea2f 9524 perl optional 
libpar-packer-perl_1.041-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#873006: libgtk3-webkit2-perl: autopkgtest failures

2018-01-04 Thread gregor herrmann

On Mon, 01 Jan 2018 13:24:34 +0200, Niko Tyni wrote:

> > libgtk3-webkit2-perl fails autopkgtest-pkg-perl's use.t:
> 
> > # Typelib file for namespace 'WebKit2', version '4.0' not found at 
> > /usr/lib/x86_64-linux-gnu/perl5/5.26/Glib/Object/Introspection.pm line 108.
> > # BEGIN failed--compilation aborted.
> > not ok 1 -  /usr/bin/perl -w -M"Gtk3::WebKit2" -e 1 2>&1 exited successfully
> 
> > Not sure if this is an indication of an even more serious (sic!)
> > problem in the package ...
> 
> strace shows
> 
> 7243  open("/usr/lib/girepository-1.0/WebKit2-4.0.typelib", O_RDONLY) = -1 
> ENOENT (No such file or directory)
> 
> The file is found in the gir1.2-webkit2-4.0 package. Looks like the
> module is unusable without that, so raising the severity.
> 
> The build time tests pass because of the build-dep on
> libwebkit2gtk-4.0-dev (which pulls in gir1.2-webkit2-4.0); perhaps that's
> the right thing to do for runtime as well?

Yeah, worth a try.

Unfortunately trying in git is not so easy, as the repo has the wrong
contents in the pristine-tar branch [0] and no tags.

Mike, could you (fix and/or) push please?


Cheers,
gregor

[0]

gbp:info: Tarballs 'libgtk3-webkit2-perl_0.06.orig.tar.gz' not found at 
'../tarballs/'
gbp:info: Creating 
/home/gregoa/src/git-pkg-perl/meta/packages/build-area/libgtk3-webkit2-perl_0.06.orig.tar.gz
gbp:error: Error creating libgtk3-webkit2-perl_0.06.orig.tar.gz: Pristine-tar 
couldn't checkout "libgtk3-webkit2-perl_0.06.orig.tar.gz": fatal: Path 
'libgtk3-webkit2-perl_0.06.orig.tar.gz.delta' does not exist in 
'refs/heads/pristine-tar'
pristine-tar: git show 
refs/heads/pristine-tar:libgtk3-webkit2-perl_0.06.orig.tar.gz.delta failed


And the existant files are:
libgtk3-webkit-perl_0.06.orig.tar.gz.delta  
libgtk3-webkit-perl_0.06.orig.tar.gz.id


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


signature.asc
Description: Digital Signature

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: Bug#885525: better log output

2018-01-04 Thread Sean DuBois

And here is the patch!

Feel free to change anything, but I rebuilt locally and everything seems
to be working 100% for me. This is the exact code upstream is using, but
should be good enough until they release a new version.

thanks
From: Sean DuBois 
Date: Thu, 04 Jan 2018 15:42:41 +0600
Subject: Fix segfault on VPN connect

Refactor in VPN applet introduced double free, this was fixed
upstream with
a52ccb2fe170558fc0aab4dd1d15ba8808b10951

Closes: #815313

Index: network-manager-applet-1.8.10/shared/nm-utils/nm-compat.c
===
--- network-manager-applet-1.8.10.orig/shared/nm-utils/nm-compat.c
+++ network-manager-applet-1.8.10/shared/nm-utils/nm-compat.c
@@ -40,30 +40,37 @@ _get_keys (NMSettingVpn *setting,
 {
 	guint len;
 	const char **keys = NULL;
-	gs_unref_ptrarray GPtrArray *a = NULL;
+	GPtrArray *a;

 	nm_assert (NM_IS_SETTING_VPN (setting));

-	a = g_ptr_array_new ();
+	if (is_secrets)
+		len = nm_setting_vpn_get_num_secrets (setting);
+	else
+		len = nm_setting_vpn_get_num_data_items (setting);
+
+	a = g_ptr_array_sized_new (len + 1);
+
 	if (is_secrets)
 		nm_setting_vpn_foreach_secret (setting, _get_keys_cb, a);
 	else
 		nm_setting_vpn_foreach_data_item (setting, _get_keys_cb, a);
-	len = a->len;

-	if (a->len) {
+	len = a->len;
+	if (len) {
 		g_ptr_array_sort (a, nm_strcmp_p);
 		g_ptr_array_add (a, NULL);
-		keys = (const char **) g_ptr_array_free (g_steal_pointer (), FALSE);
+		keys = g_memdup (a->pdata, a->len * sizeof (gpointer));

 		/* we need to cache the keys *somewhere*. */
 		g_object_set_qdata_full (G_OBJECT (setting),
 		 is_secrets
 		 ? NM_CACHED_QUARK ("libnm._nm_setting_vpn_get_secret_keys")
 		 : NM_CACHED_QUARK ("libnm._nm_setting_vpn_get_data_keys"),
-		 keys,
+		 g_ptr_array_free (a, FALSE),
 		 (GDestroyNotify) g_strfreev);
-	}
+	} else
+		g_ptr_array_free (a, TRUE);

 	NM_SET_OUT (out_length, len);
 	return keys;

Bug#884158: marked as done (FTBFS with libical 3.0)

Your message dated Thu, 04 Jan 2018 21:49:25 +
with message-id 
and subject line Bug#884158: fixed in syncevolution 1.5.2-3
has caused the Debian Bug report #884158,
regarding FTBFS with libical 3.0
to be marked as done.

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

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


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

Source: syncevolution
Version: 1.5.2-2
Severity: serious
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=104220

Hi,

syncevolition FTBFS with libical 3.0 that has recently been introduced
in debian:

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I/<>/src 
-I./test -I/usr/include -I/usr/include/ -I/usr/include//KDE 
-I/usr/include/qt4 -I/usr/include/qt4/QtCore -pthread 
-I/usr/include/evolution-data-server -I/usr/include/nss 
-I/usr/include/nspr -I/usr/include/libsecret-1 
-I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-pthread -I/usr/include/evolution-data-server -I/usr/include/nss 
-I/usr/include/nspr -I/usr/include/libsecret-1 
-I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-pthread -I/usr/include/evolution-data-server -I/usr/include/nss 
-I/usr/include/nspr -I/usr/include/libsecret-1 
-I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/neon -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/neon -Wall 
-Wno-unknown-pragmas -Wno-deprecated-declarations -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c src/backends/webdav/NeonCXX.cpp  -fPIC -DPIC 
-o src/backends/webdav/.libs/src_backends_webdav_syncdav_la-NeonCXX.o
src/backends/webdav/CalDAVSource.cpp: In member function 'virtual 
SyncEvo::SubSyncSource::SubItemResult 
SyncEvo::CalDAVSource::insertSubItem(const string&, const string&, const 
string&)':
src/backends/webdav/CalDAVSource.cpp:724:31: error: 
'icaltime_from_timet' was not declared in this scope
 lastmodtime = icaltime_from_timet(event.m_lastmodtime, 
false);

   ^~~
src/backends/webdav/CalDAVSource.cpp:724:31: note: suggested 
alternative: 'icaltime_as_timet'
 lastmodtime = icaltime_from_timet(event.m_lastmodtime, 
false);

   ^~~
   icaltime_as_timet
src/backends/webdav/CalDAVSource.cpp:725:29: error: 'struct 
icaltimetype' has no member named 'is_utc'; did you mean 'is_date'?

 lastmodtime.is_utc = 1;
 ^~
 is_date


Kind regards,

Laurent Bigonville
--- End Message ---
--- Begin Message ---
Source: syncevolution
Source-Version: 1.5.2-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Jan 2018 12:24:58 +0100
Source: syncevolution
Binary: syncevolution sync-ui syncevolution-common syncevolution-libs 
syncevolution-libs-gnome syncevolution-libs-kde syncevolution-dbus 
syncevolution-http libsyncevolution0 libsyncevo-dbus0 libgdbussyncevo0
Architecture: source amd64 all
Version: 1.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Tino Mettler 
Changed-By: Tino Mettler 
Description:
 libgdbussyncevo0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s
 libsyncevo-dbus0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s

Bug#871284: marked as done (libsyncevolution0: requires rebuild against GCC 7 and symbols/shlibs bump)

Your message dated Thu, 04 Jan 2018 21:49:25 +
with message-id 
and subject line Bug#871284: fixed in syncevolution 1.5.2-3
has caused the Debian Bug report #871284,
regarding libsyncevolution0: requires rebuild against GCC 7 and symbols/shlibs 
bump
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.)


-- 
871284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsyncevolution0
Version: 1.5.2-2
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: syncevolution
Source-Version: 1.5.2-3

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

Debian distribution maintenance software
pp.
Tino Mettler  (supplier of updated syncevolution package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Jan 2018 12:24:58 +0100
Source: syncevolution
Binary: syncevolution sync-ui syncevolution-common syncevolution-libs 
syncevolution-libs-gnome syncevolution-libs-kde syncevolution-dbus 
syncevolution-http libsyncevolution0 libsyncevo-dbus0 libgdbussyncevo0
Architecture: source amd64 all
Version: 1.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Tino Mettler 
Changed-By: Tino Mettler 
Description:
 libgdbussyncevo0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s
 libsyncevo-dbus0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s
 libsyncevolution0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s
 sync-ui- Sync personal information data using SyncML and CalDAV/CardDAV (G
 syncevolution - Sync personal information data using SyncML and CalDAV/CardDAV 
(C
 syncevolution-common - Sync personal information data using SyncML and 
CalDAV/CardDAV (c
 syncevolution-dbus - Sync

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: Bug#885525: better log output

2018-01-04 Thread Sean DuBois

On Wed, 3 Jan 2018 20:49:01 +0100 Michael Biebl  wrote:
> Control: tags -1 + fixed-upstream patch
> 
> Am 03.01.2018 um 20:29 schrieb Sean DuBois:
> > Hey Michael,
> > 
> > This is fixed upstream
> > https://git.gnome.org/browse/network-manager-applet/commit/?id=a52ccb2fe170558fc0aab4dd1d15ba8808b10951
> 
> Thanks you, Sean!
> 
> I've marked the bug accordingly
> 
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>

Bug#886355: Pending fixes for bugs in the libpar-packer-perl package

2018-01-04 Thread pkg-perl-maintainers

tag 886355 + pending
thanks

Some bugs in the libpar-packer-perl package are closed in revision
c8b6951552e57ae9e090344577c6b0b00ea5e01d in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libpar-packer-perl.git/commit/?id=c8b6951

Commit message:

debian/rules: disable parallel building.

Thanks: Adrian Bunk for the bug report and the patch.
Closes: #886355

Processed: Pending fixes for bugs in the libpar-packer-perl package

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

> tag 886355 + pending
Bug #886355 [src:libpar-packer-perl] libpar-packer-perl: frequent parallel FTBFS
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#886361: apertium: frequent parallel FTBFS

Source: apertium
Version: 3.4.2~r68466-3
Severity: serious
Tags: patch

https://tests.reproducible-builds.org/debian/history/apertium.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium.html
https://buildd.debian.org/status/package.php?p=apertium=sid

...
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -Wall -Wextra -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -o apertium-filter-ambiguity 
apertium_filter_ambiguity.o -llttoolbox3 -lxml2 -lpcre -lapertium3 -lpcreposix 
-lpcre -lpcrecpp -llttoolbox3 -lxml2 -lpcre
libtool: link: g++ -Wall -Wextra -g -O2 "-fdebug-prefix-map=/<>=." 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o apertium-filter-ambiguity apertium_filter_ambiguity.o  
-lapertium3 -lpcreposix -lpcrecpp -llttoolbox3 -lxml2 -lpcre
/usr/bin/ld: cannot find -lapertium3
collect2: error: ld returned 1 exit status
Makefile:1056: recipe for target 'apertium-filter-ambiguity' failed
make[3]: *** [apertium-filter-ambiguity] Error 1


This was triggered by dh comat >= 10 defaulting to parallel building.

Fix attached.
Description: Fix parallel FTBFS
 Tell automake that libapertium3 is a self-built library
 so that proper dependencies are added.
Author: Adrian Bunk 

--- apertium-3.4.2~r68466.orig/apertium/Makefile.am
+++ apertium-3.4.2~r68466/apertium/Makefile.am
@@ -226,7 +226,7 @@ apertium_DATA = deformat.xsl reformat.xs
 
 apertium_pretransfer_SOURCES = apertium_pretransfer.cc
 apertium_multiple_translations_SOURCES = apertium-multiple-translations.cc
-apertium_multiple_translations_LDADD = $(APERTIUM_LIBS) 
-lapertium$(GENERIC_MAJOR_VERSION)
+apertium_multiple_translations_LDADD = $(APERTIUM_LIBS) libapertium3.la
 apertium_destxt_SOURCES = apertium_destxt.cc
 apertium_retxt_SOURCES = apertium_retxt.cc
 apertium_deshtml_SOURCES = apertium_deshtml.cc
@@ -249,55 +249,55 @@ apertium_repptx_SOURCES = apertium_reppt
 apertium_desmediawiki_SOURCES = apertium_desmediawiki.cc
 apertium_remediawiki_SOURCES = apertium_remediawiki.cc
 apertium_prelatex_SOURCES = apertium_prelatex.cc
-apertium_prelatex_LDADD= $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_prelatex_LDADD= $(APERTIUM_LIBS) libapertium3.la
 apertium_postlatex_SOURCES = apertium_postlatex.cc
-apertium_postlatex_LDADD= $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_postlatex_LDADD= $(APERTIUM_LIBS) libapertium3.la
 apertium_postlatex_raw_SOURCES = apertium_postlatex_raw.cc
-apertium_postlatex_raw_LDADD= $(APERTIUM_LIBS) 
-lapertium$(GENERIC_MAJOR_VERSION)
+apertium_postlatex_raw_LDADD= $(APERTIUM_LIBS) libapertium3.la
 
 apertium_tagger_SOURCES = apertium_tagger.cc
-apertium_tagger_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_tagger_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_tmxbuild_SOURCES = apertium_tmxbuild.cc
-apertium_tmxbuild_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_tmxbuild_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_preprocess_transfer_SOURCES = transferpp.cc
 apertium_preprocess_transfer_LDADD = $(APERTIUM_LIBS) \
- -lapertium$(GENERIC_MAJOR_VERSION)
+ libapertium3.la
 
 apertium_filter_ambiguity_SOURCES = apertium_filter_ambiguity.cc
 apertium_filter_ambiguity_LDADD = $(APERTIUM_LIBS) \
-  -lapertium$(GENERIC_MAJOR_VERSION)
+  libapertium3.la
 
 apertium_transfer_SOURCES = apertium_transfer.cc
-apertium_transfer_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_transfer_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_interchunk_SOURCES = apertium_interchunk.cc
-apertium_interchunk_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_interchunk_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_postchunk_SOURCES = apertium_postchunk.cc
-apertium_postchunk_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+apertium_postchunk_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 ###apertium_lextor_SOURCES = apertium_lextor.cc
-###apertium_lextor_LDADD = $(APERTIUM_LIBS) -lapertium$(GENERIC_MAJOR_VERSION)
+###apertium_lextor_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 #apertium_lextor_eval_SOURCES = apertium-lextor-eval.C
-#apertium_lextor_eval_LDADD = $(APERTIUM_LIBS) 
-lapertium$(GENERIC_MAJOR_VERSION)
+#apertium_lextor_eval_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_tagger_apply_new_rules_SOURCES = apertium_tagger_apply_new_rules.cc
-apertium_tagger_apply_new_rules_LDADD = $(APERTIUM_LIBS) 
-lapertium$(GENERIC_MAJOR_VERSION)
+apertium_tagger_apply_new_rules_LDADD = $(APERTIUM_LIBS) libapertium3.la
 
 apertium_tagger_readwords_SOURCES = apertium_tagger_readwords.cc
-apertium_tagger_readwords_LDADD = $(APERTIUM_LIBS) 
-lapertium$(GENERIC_MAJOR_VERSION)
+apertium_tagger_readwords_LDADD =

Processed: bug 886355 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=124014

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

> forwarded 886355 https://rt.cpan.org/Ticket/Display.html?id=124014
Bug #886355 [src:libpar-packer-perl] libpar-packer-perl: frequent parallel FTBFS
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=124014'.
> thanks
Stopping processing here.

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

Processed: Add the patch tag I forgot

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

> tags 886355 patch
Bug #886355 [src:libpar-packer-perl] libpar-packer-perl: frequent parallel FTBFS
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#886359: infinipath-psm FTBFS on i386: missing symbol ipath_dwordcpy_safe

Source: infinipath-psm
Version: 3.3+20.604758e7-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=infinipath-psm=i386=3.3%2B20.604758e7-3=1515071279=0

...
   dh_makeshlibs -a -O--parallel
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: no debian/symbols file used as basis for generating 
debian/libpsm-infinipath1/DEBIAN/symbols
--- new_symbol_file (libpsm-infinipath1_3.3+20.604758e7-3_i386)
+++ dpkg-gensymbolscQjnKE   2018-01-04 13:07:52.434415479 +
@@ -32,7 +32,7 @@
  ipath_context_open@Base 3.3+7.gec1d6d2
  ipath_disarm_bufs@Base 3.3+7.gec1d6d2
  ipath_dwordcpy@Base 3.3+7.gec1d6d2
- ipath_dwordcpy_safe@Base 3.3+7.gec1d6d2
+#MISSING: 3.3+20.604758e7-3# ipath_dwordcpy_safe@Base 3.3+7.gec1d6d2
  ipath_event_ack@Base 3.3+7.gec1d6d2
  ipath_flash_csum@Base 3.3+7.gec1d6d2
  ipath_flush_egr_bufs@Base 3.3+7.gec1d6d2
dh_makeshlibs: failing due to earlier errors
debian/rules:15: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2

Processed: forcibly merging 885525 886152, severity of 885525 is serious

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

> forcemerge 885525 886152
Bug #885525 [network-manager-gnome] /usr/bin/nm-applet: nm-applet crashes when 
connecting to VPN
Bug #886152 [network-manager-gnome] nm-applet crashes when trying to start a 
VPN connection
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=792037'.
Severity set to 'important' from 'serious'
Added tag(s) fixed-upstream and patch.
Merged 885525 886152
> severity 885525 serious
Bug #885525 [network-manager-gnome] /usr/bin/nm-applet: nm-applet crashes when 
connecting to VPN
Bug #886152 [network-manager-gnome] nm-applet crashes when trying to start a 
VPN connection
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 886152 is serious

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

> severity 886152 serious
Bug #886152 [network-manager-gnome] nm-applet crashes when trying to start a 
VPN connection
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#876537: marked as done (otags FTBFS with OCaml 4.05.0)

Your message dated Thu, 4 Jan 2018 21:53:42 +0100
with message-id 
and subject line Re: Bug#876537: otags FTBFS with OCaml 4.05.0
has caused the Debian Bug report #876537,
regarding otags FTBFS with OCaml 4.05.0
to be marked as done.

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

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

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

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

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure --prefix /usr
ocamlc version 4.05.0 found.
This version of otags needs 4.02.x.
Aborting.
debian/rules:21: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
Version: 4.05.1-1

On 23/09/2017 14:10, Adrian Bunk wrote:
> Source: otags
> Version: 4.02.2-2
> Severity: serious
> Tags: buster sid
> 
> https://buildd.debian.org/status/package.php?p=otags=sid
> 
> ...
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> ./configure --prefix /usr
> ocamlc version 4.05.0 found.
> This version of otags needs 4.02.x.
> Aborting.
> debian/rules:21: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 1
> 

This bug has been fixed in 4.05.1-1 a while ago.

-- 
Mehdi--- End Message ---

Bug#885967: #885967: FTBFS: FAILED test of gethostid ENOENT

2018-01-04 Thread Adam Borowski

} PATH=`pwd`/bin:$PATH /bin/sh test/07/t0705a.sh
} 2,3c2,3
} < (ENOENT) because there is no "hostid" regular file in the pathname "/etc"
} < directory; did you mean the "hosts" regular file instead?
} ---
} > (ENOENT) because there is no "hostid" regular file in the pathname
} > "/etc" directory
} FAILED test of gethostid ENOENT

Adrian Bunk wrote:
> /etc/hosts is created in the postinst of the netbase package,
> so "missing build dependency on netbase" would be another way
> to describe the problem.

Not sure if this is the best way to fix the failure, although it _would_
make the error message find /etc/hosts there so it can be suggested.

This test is fragile, though -- if you have a file named /etc/hosting or
such, it'll be picked instead of "hosts".

The root cause, though, is that libexplain knows about gethostid, thus it
can rule out an user making a typo -- the function looks for /etc/hostid and
hothing else.

Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#885963: FTBFS: failed to open /etc/hosts

2018-01-04 Thread Adam Borowski

On Thu, Jan 04, 2018 at 08:14:31PM +0200, Adrian Bunk wrote:
> On Mon, Jan 01, 2018 at 01:13:57AM +0100, Adam Borowski wrote:
> >...
> > And indeed, in a chroot created with debootstrap --variant=buildd there is
> > no such file anymore.  But, I see that the package doesn't actually need
> > /etc/hosts but just the testsuite uses it as a random file it -thinks- will
> > be always there.  Thanks to our efforts to unbloat the default install, this
> > is no longer true.  Thus, you'd need to pick something else.
> >...
> 
> /etc/hosts is created in the postinst of the netbase package,
> so "missing build dependency on netbase" would be another way
> to describe the problem.

For a generic lack of /etc/hosts, yeah, it'd be the best solution.
In this case, though, I'd rather patch "random text file that's always
present" to something else.


Thanks for enlightening us about /etc/hosts coming from netbase, though!
There's more than just these two bugs where its lack appears.


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#886355: libpar-packer-perl: frequent parallel FTBFS

Source: libpar-packer-perl
Version: 1.041-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libpar-packer-perl=sid

...
dh_auto_build
make -j6
make[2]: Entering directory '/<>'
cp script/par.pl blib/script/par.pl
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/par.pl
make[3]: Entering directory '/<>/myldr'
Makefile:855: warning: overriding recipe for target '.c.o'
Makefile:336: warning: ignoring old recipe for target '.c.o'
cp script/pp blib/script/pp
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/pp
cp script/tkpp blib/script/tkpp
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/tkpp
"/usr/bin/perl" par_pl2c.pl my_par_pl < ../script/par.pl > my_par_pl.c 
"/usr/bin/perl" sha1.c.PL
Can't locate PAR/Filter/PodStrip.pm in @INC (you may need to install the 
PAR::Filter::PodStrip module) (@INC contains: 
/<>/myldr/../blib/arch /<>/myldr/../blib/lib 
/etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/aarch64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/aarch64-linux-gnu/perl-base .) at par_pl2c.pl 
line 7.
BEGIN failed--compilation aborted at par_pl2c.pl line 7.
Makefile:879: recipe for target 'my_par_pl.c' failed
make[3]: *** [my_par_pl.c] Error 2


This is due to dh compat 10 defaulting to parallel building.

Ideally the build should be fixed to work with parallel building,
but if that's not easily possible the following patch to go back
to non-parallel building is sufficient to fix the bug:

--- debian/rules.old2018-01-04 20:32:58.184625753 +
+++ debian/rules2018-01-04 20:33:08.360625656 +
@@ -10,7 +10,7 @@
 ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
 
 %:
-   dh $@
+   dh $@ --no-parallel
 
 override_dh_auto_build:
dh_auto_build

Bug#884116: linux-image-4.9.0-3-amd64: screen artifacts then crash without anyway to revert to console

2018-01-04 Thread Mathias Bavay

Package: src:linux
Followup-For: Bug #884116

Dear Maintainer,

Since sometimes between mid-November and mid-December, my whole system crashes 
within 
a few minutes after boot (90% of the time after less than 2 minutes). The screen
gets various artifacts and the whole system is gone. There is no way to ssh
to the system or switch to a console. No logs are written out (either as
kernel logs, dmesg or Xorg.log). I've tried (binary) linux-image-4.9.0-3-amd64
as well as linux-image-4.9.0-4-amd64, this makes no difference. I've tried
updating the cpu microcode, forcing re-install of the (binary) kernels,
reinstalling mesa, nothing has changed. However, using an older Debian stretch 
live image
on a usb stick worked fine. I'm now using the linux-image-4.14.0 backport and
this works perfectly fine. 

I am using Kde with a theme that relies heavily on transparency and I guess this
makes things worse (I had in the past every now and then warnings that
the driver could not support the proper functions and it would automatically
tunr transparency effects off, a reboot would be enough to fix it). Enabling 
a theme with less transparency effects makes the system work longer before 
crashing.

Finally, I turned off the OpenGL rendering in Kde's settings (switching to
Xrender), but this did not change anything (still crashing as fast).

Feel free to ask me for more informations / tests if needed,
Regards,
Mathias Bavay

-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/dorfberg--vg-root ro quiet 
initcall_debug apic=debug

** Not tainted

** Kernel log:
[   10.813637] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   10.821546] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[   10.821728] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
[   10.821784] [drm] Initialized i915 1.6.0 20160919 for :00:02.0 on minor 0
[   10.821830] initcall i915_init+0x0/0x54 [i915] returned 0 after 71551 usecs
[   10.821893] IOAPIC[0]: Set routing entry (2-22 -> 0x52 -> IRQ 22 Mode:1 
Active:1 Dest:15)
[   10.821919] initcall azx_driver_init+0x0/0xfd8 [snd_hda_intel] returned 0 
after 70228 usecs
[   10.822802] initcall intel_uncore_init+0x0/0xeac [intel_uncore] returned 0 
after 66742 usecs
[   10.823511] calling  cstate_pmu_init+0x0/0xf56 [intel_cstate] @ 346
[   10.824717] initcall cstate_pmu_init+0x0/0xf56 [intel_cstate] returned 0 
after 1173 usecs
[   10.825062] fbcon: inteldrmfb (fb0) is primary device
[   10.834876] calling  generic_driver_init+0x0/0x1000 [snd_hda_codec_generic] 
@ 404
[   10.834893] initcall generic_driver_init+0x0/0x1000 [snd_hda_codec_generic] 
returned 0 after 13 usecs
[   10.835442] calling  vmx_init+0x0/0x3c3 [kvm_intel] @ 343
[   10.835694] initcall vmx_init+0x0/0x3c3 [kvm_intel] returned 0 after 240 
usecs
[   10.836310] calling  realtek_driver_init+0x0/0x1000 [snd_hda_codec_realtek] 
@ 404
[   10.836968] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VB: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   10.836969] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   10.836970] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   10.836970] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   10.836970] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   10.836971] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x19
[   10.836972] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
[   10.837527] calling  coretemp_init+0x0/0x1000 [coretemp] @ 334
[   10.837613] initcall coretemp_init+0x0/0x1000 [coretemp] returned 0 after 80 
usecs
[   10.838057] calling  powerclamp_init+0x0/0x1000 [intel_powerclamp] @ 334
[   10.838087] initcall powerclamp_init+0x0/0x1000 [intel_powerclamp] returned 
0 after 26 usecs
[   10.838583] calling  pkg_temp_thermal_init+0x0/0x1000 [x86_pkg_temp_thermal] 
@ 346
[   10.838624] initcall pkg_temp_thermal_init+0x0/0x1000 [x86_pkg_temp_thermal] 
returned 0 after 37 usecs
[   10.838825] calling  acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] @ 346
[   10.838827] initcall acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] returned 
-17 after 0 usecs
[   10.839555] calling  rapl_init+0x0/0x1000 [intel_rapl] @ 341
[   10.839557] intel_rapl: Found RAPL domain package
[   10.839558] intel_rapl: Found RAPL domain core
[   10.839559] intel_rapl: Found RAPL domain uncore
[   10.839561] intel_rapl: Found RAPL domain dram
[   10.839564] intel_rapl: RAPL package 0 domain package locked by BIOS
[   10.839572] intel_rapl: RAPL package 0 domain dram locked by BIOS
[   10.839728] initcall rapl_init+0x0/0x1000 [intel_rapl] returned 0 after 166 
usecs
[   10.845882] initcall realtek_driver_init+0x0/0x1000 [snd_hda_codec_realtek]

Bug#801331: jdresolve: diff for NMU version 0.6.1-5.1

2018-01-04 Thread Frederic Peters

Hi,

> I've prepared an NMU for jdresolve (versioned as 0.6.1-5.1) and uploaded 
> it to DELAYED/5. Please feel free to tell me if I should cancel it.

It's totally fine; thank you.


Fred

Processed: Not a problem in stretch

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

> tags 885626 buster sid
Bug #885626 {Done: Scott Kitterman } [src:sonic-pi] 
src:sonic-pi: Will FTBFS with new qscintilla2
Added tag(s) sid and buster.
> tags 885643 buster sid
Bug #885643 {Done: Scott Kitterman } [src:tora] src:tora: 
Will FTBFS with qscintilla2 in experimental
Added tag(s) buster and sid.
> tags 885647 buster sid
Bug #885647 {Done: Scott Kitterman } 
[src:universalindentgui] src:universalindentgui: Will FTBFS with new 
qscintilla2 in experimental
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: Merge duplicates

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

> reassign 879035 src:gourmet
Bug #879035 [gourmet] gourmet: port to gir1.2-poppler-0.18
Bug reassigned from package 'gourmet' to 'src:gourmet'.
No longer marked as found in versions gourmet/0.17.4-4.
Ignoring request to alter fixed versions of bug #879035 to the same values 
previously set
> forcemerge 886275 879035
Bug #886275 [src:gourmet] gourmet: Don't depend on python-poppler
Bug #879035 [src:gourmet] gourmet: port to gir1.2-poppler-0.18
Marked as found in versions gourmet/0.17.4-4.
Added tag(s) pending and patch.
Merged 879035 886275
> thanks
Stopping processing here.

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

Processed: Merging python-wxgtk3.0/pyspread bugs

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

> reassign 883741 python-wxgtk3.0
Bug #883741 [pyspread] pyspread: Spreadsheet canvas won't show with newest 
update
Bug reassigned from package 'pyspread' to 'python-wxgtk3.0'.
No longer marked as found in versions pyspread/1.1-1.
Ignoring request to alter fixed versions of bug #883741 to the same values 
previously set
> severity 884411 grave
Bug #884411 {Done: Scott Talbert } [python-wxgtk3.0] 
python-wxgtk3.0: Cairo widgets fail after apt upgrade
Severity set to 'grave' from 'important'
> forcemerge 884411 883741
Bug #884411 {Done: Scott Talbert } [python-wxgtk3.0] 
python-wxgtk3.0: Cairo widgets fail after apt upgrade
Bug #883741 [python-wxgtk3.0] pyspread: Spreadsheet canvas won't show with 
newest update
Marked Bug as done
Marked as fixed in versions wxpython3.0/3.0.2.0+dfsg-6.
Marked as found in versions wxpython3.0/3.0.2.0+dfsg-5.
Merged 883741 884411
> affects 884411 pyspread
Bug #884411 {Done: Scott Talbert } [python-wxgtk3.0] 
python-wxgtk3.0: Cairo widgets fail after apt upgrade
Bug #883741 {Done: Scott Talbert } [python-wxgtk3.0] pyspread: 
Spreadsheet canvas won't show with newest update
Added indication that 884411 affects pyspread
Added indication that 883741 affects pyspread
> thanks
Stopping processing here.

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

Bug#801331: jdresolve: diff for NMU version 0.6.1-5.1

Control: tags 801331 + pending

Dear maintainer,

I've prepared an NMU for jdresolve (versioned as 0.6.1-5.1) and uploaded 
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -u jdresolve-0.6.1/debian/changelog jdresolve-0.6.1/debian/changelog
--- jdresolve-0.6.1/debian/changelog
+++ jdresolve-0.6.1/debian/changelog
@@ -1,3 +1,12 @@
+jdresolve (0.6.1-5.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix breakage with libnet-dns-perl in jessie and later,
+thanks to Klaus Rein for reporting the bug and
+Matt Johnston for forwarding the fix. (Closes: #801331)
+
+ -- Adrian Bunk   Thu, 04 Jan 2018 20:21:09 +0200
+
 jdresolve (0.6.1-5) unstable; urgency=medium
 
   * debian/: merge packaging changes from Ubuntu. (Thanks Logan Rosen)
diff -u jdresolve-0.6.1/jdresolve jdresolve-0.6.1/jdresolve
--- jdresolve-0.6.1/jdresolve
+++ jdresolve-0.6.1/jdresolve
@@ -857,7 +857,12 @@
 # For each DNS answer, check the data received
 if ($type eq 'H') {
 	if (defined $_->{ptrdname}) {
+		if ($_->isa('Net::DNS::RR::PTR')) { 
+			# Fix for a new version of Net::DNS 
+			$hosts{$query}{NAME} = $_->rdatastr();
+		} else {
 		$hosts{$query}{NAME} = $_->{ptrdname};
+		}
 		$hosts{$query}{RESOLVED} = 'N';
 
 		$resolved = 1;

Processed: jdresolve: diff for NMU version 0.6.1-5.1

Processing control commands:

> tags 801331 + pending
Bug #801331 [jdresolve] jdresolve: malformed output in jessie
Added tag(s) pending.

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

Bug#886330: sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No such file or directory

2018-01-04 Thread Sergio Durigan Junior

On Thursday, January 04 2018, Andreas Tille wrote:

> Hi,
>
> just a quick note (I'm quite busy with real life):  The issue seems to
> be caused by the fact that libquazip5-headers which is pulled in due
> to dependencies provides
>
> /usr/include/quazip5/quazip.h
>
> the file
>
> /usr/include/quazip/quazip.h
>
> exists in libquazip-headers.  I admit I have no real idea what the
> correct fix is since I'm not a Qt expert.

Thanks, Chris and Andreas.

I'll take a look later today.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Bug#886325: dbus daemon does not start with error "undefined symbol: XML_SetHashSalt"

2018-01-04 Thread Simon McVittie

On Thu, 04 Jan 2018 at 14:37:53 +0100, Alberto Brosich wrote:
> dbus-daemon[1350]: /usr/bin/dbus-daemon: symbol lookup error:
> /usr/bin/dbus-daemon: undefined symbol: XML_SetHashSalt
...
> ii  libexpat1:amd642.2.0-2+deb9u1

According to /var/lib/dpkg/info/libexpat1:amd64.symbols on my stable
system, libexpat1 has provided that symbol since version 2.1~beta3, which
is older than oldoldstable. Do you have an outdated copy of libexpat.so.1
in /usr/local/lib or some similar location?

smcv

Bug#885963: FTBFS: failed to open /etc/hosts

On Mon, Jan 01, 2018 at 01:13:57AM +0100, Adam Borowski wrote:
>...
> And indeed, in a chroot created with debootstrap --variant=buildd there is
> no such file anymore.  But, I see that the package doesn't actually need
> /etc/hosts but just the testsuite uses it as a random file it -thinks- will
> be always there.  Thanks to our efforts to unbloat the default install, this
> is no longer true.  Thus, you'd need to pick something else.
>...

/etc/hosts is created in the postinst of the netbase package,
so "missing build dependency on netbase" would be another way
to describe the problem.

> Meow!

cu
Adrian

-- 

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

Bug#886340: FTBFS: Could not connect to display :0 during doc build

Package: src:ovito
Version: 2.9.0+dfsg1-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Here is the end of the build log:

[ 99%] Built target Ovito
make -f CMakeFiles/scripting_documentation.dir/build.make 
CMakeFiles/scripting_documentation.dir/depend
make[3]: Entering directory '/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu'
cd /home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /home/ovito-2.9.0+dfsg1 /home/ovito-2.9.0+dfsg1 
/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu 
/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu 
/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/scripting_documentation.dir/DependInfo.cmake
 --color=
Scanning dependencies of target scripting_documentation
make[3]: Leaving directory '/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu'
make -f CMakeFiles/scripting_documentation.dir/build.make 
CMakeFiles/scripting_documentation.dir/build
make[3]: Entering directory '/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu'
[100%] Generating scripting documentation
cd /home/ovito-2.9.0+dfsg1/doc/python && 
/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu/bin/ovitos /usr/bin/sphinx-build 
-b html -a -E -D version=2.9 -D release=2.9.0 . 
/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu/share/ovito/doc/manual/html/python/
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
No protocol specified
qt.qpa.screen: QXcbConnection: Could not connect to display :0
Could not connect to any X display.
CMakeFiles/scripting_documentation.dir/build.make:60: recipe for target 
'CMakeFiles/scripting_documentation' failed
make[3]: *** [CMakeFiles/scripting_documentation] Error 1
make[3]: Leaving directory '/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:71: recipe for target 
'CMakeFiles/scripting_documentation.dir/all' failed
make[2]: *** [CMakeFiles/scripting_documentation.dir/all] Error 2
make[2]: Leaving directory '/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu'
Makefile:165: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/ovito-2.9.0+dfsg1/obj-x86_64-linux-gnu'
dh_auto_build: cd obj-x86_64-linux-gnu && make -j4 returned exit code 2
debian/rules:5: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Note that this is after applying the fix for qscintilla2 library detection in
#885644 (which seems very unlrelated - I can reproduce this with the old
qscintilla2 as well).

This is the last package blocking completion of the current qscintilla2
transition, so your near-term attention to this would be appreciated.

The failures are all from builds inside a pbuilder chroot, so I suppose there
is some chance this is a pbuilder/sbuild thing, but I don't plan on heaving
a source only upload at the buildds to see what happens.

Scott K

Processed: Not a problem in stretch

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

> tags 886018 buster sid
Bug #886018 [fastd] fastd: FTBFS with libsodium-dev >= 1.0.15
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: Merge duplicates

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

> reassign 886204 src:android-platform-system-core
Bug #886204 [src:android-platform-build] FTBFS: Vector.h:251:64: error: no 
matching function for call
Bug reassigned from package 'src:android-platform-build' to 
'src:android-platform-system-core'.
No longer marked as found in versions android-platform-build/1:7.0.0+r33-1.
Ignoring request to alter fixed versions of bug #886204 to the same values 
previously set
> forcemerge 853310 886204
Bug #853310 [src:android-platform-system-core] android-platform-build: ftbfs 
with GCC-7
Bug #853311 [src:android-platform-system-core] 
android-platform-frameworks-base: ftbfs with GCC-7
Bug #853312 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-7
Bug #886122 [src:android-platform-system-core] FTBFS: .../Vector.h:251:64: 
error: no matching function for call
Bug #886204 [src:android-platform-system-core] FTBFS: Vector.h:251:64: error: 
no matching function for call
Added indication that 886204 affects 
src:android-platform-build,src:android-platform-frameworks-base
Marked as found in versions android-platform-system-core/1:7.0.0+r1-2.
Added tag(s) sid and buster.
Bug #853311 [src:android-platform-system-core] 
android-platform-frameworks-base: ftbfs with GCC-7
Bug #853312 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-7
Bug #886122 [src:android-platform-system-core] FTBFS: .../Vector.h:251:64: 
error: no matching function for call
Merged 853310 853311 853312 886122 886204
> thanks
Stopping processing here.

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

Processed: Merge duplicates

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

> reassign 886122 src:android-platform-system-core
Bug #886122 [src:android-platform-frameworks-base] FTBFS: .../Vector.h:251:64: 
error: no matching function for call
Bug reassigned from package 'src:android-platform-frameworks-base' to 
'src:android-platform-system-core'.
No longer marked as found in versions 
android-platform-frameworks-base/1:7.0.0+r33-1.
Ignoring request to alter fixed versions of bug #886122 to the same values 
previously set
> forcemerge 853310 886122
Bug #853310 [src:android-platform-system-core] android-platform-build: ftbfs 
with GCC-7
Bug #853311 [src:android-platform-system-core] 
android-platform-frameworks-base: ftbfs with GCC-7
Bug #853312 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-7
Bug #853311 [src:android-platform-system-core] 
android-platform-frameworks-base: ftbfs with GCC-7
Removed indication that 853311 affects src:android-platform-frameworks-base and 
src:android-platform-build
Added indication that 853311 affects 
src:android-platform-build,src:android-platform-frameworks-base
Removed indication that 853310 affects src:android-platform-build and 
src:android-platform-frameworks-base
Added indication that 853310 affects 
src:android-platform-build,src:android-platform-frameworks-base
Removed indication that 853312 affects src:android-platform-build and 
src:android-platform-frameworks-base
Added indication that 853312 affects 
src:android-platform-build,src:android-platform-frameworks-base
Bug #886122 [src:android-platform-system-core] FTBFS: .../Vector.h:251:64: 
error: no matching function for call
Added indication that 886122 affects 
src:android-platform-build,src:android-platform-frameworks-base
Marked as found in versions android-platform-system-core/1:7.0.0+r1-2.
Added tag(s) buster and sid.
Bug #853312 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-7
Merged 853310 853311 853312 886122
> thanks
Stopping processing here.

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

Processed: Re: Bug#859544: opensmtpd: Please migrate to openssl1.1 in buster

Processing control commands:

> tag -1 + help
Bug #859544 [src:opensmtpd] opensmtpd: Please migrate to openssl1.1 in buster
Added tag(s) help.

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

Bug#859544: opensmtpd: Please migrate to openssl1.1 in buster

2018-01-04 Thread Ryan Kavanagh

Control: tag -1 + help

Hi Sebastian,

Sorry for dropping the ball on this.

On Fri, Oct 13, 2017 at 10:07:54PM +0200, Sebastian Andrzej Siewior wrote:
> Could you retry with the following patch?

I've applied the patch, and it successfully builds with libssl 1.0.2n, but FTBFS
with 1.1.0g (logs attached). Unfortunately, libssl is outside my realm of
expertise and AFAICT upstream hasn't made any progress towards a port to 1.1.
Any suggestions on how to fix the SSL-related build issue?

Best wishes,
Ryan

-- 
|_)|_/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
| \| \  https://ryanak.ca/ |  BD95 8F7B F8FC 4A11 C97A
sbuild (Debian sbuild) 0.73.0 (23 Dec 2016) on zeta.ryanak.ca

+==+
| opensmtpd 6.0.2p1-2 (amd64)  Wed, 03 Jan 2018 16:39:07 + |
+==+

Package: opensmtpd
Version: 6.0.2p1-2
Source Version: 6.0.2p1-2
Distribution: experimenal
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

E: 60append-apt-sources: Checking for auxiliary apt sources in 
/etc/schroot/sources.list.d/sid-snap.sources.list
E: 60append-apt-sources: Checking for apt preferences in 
/etc/schroot/sources.list.d/sid-snap.preferences
E: 80append-apt-sources: Get:1 http://localhost:3142/debian sid InRelease [240 
kB]
E: 80append-apt-sources: Get:2 http://localhost:3142/debian sid/main 
Sources.diff/Index [27.9 kB]
E: 80append-apt-sources: Get:3 http://localhost:3142/debian sid/main amd64 
Packages.diff/Index [27.9 kB]
E: 80append-apt-sources: Get:4 http://localhost:3142/debian sid/main Sources 
2018-01-02-2020.59.pdiff [16.4 kB]
E: 80append-apt-sources: Get:5 http://localhost:3142/debian sid/main Sources 
2018-01-03-0225.05.pdiff [10.1 kB]
E: 80append-apt-sources: Get:6 http://localhost:3142/debian sid/main Sources 
2018-01-03-0826.10.pdiff [2218 B]
E: 80append-apt-sources: Get:7 http://localhost:3142/debian sid/main Sources 
2018-01-03-1421.25.pdiff [14.1 kB]
E: 80append-apt-sources: Get:8 http://localhost:3142/debian sid/main amd64 
Packages 2018-01-02-2020.59.pdiff [10.9 kB]
E: 80append-apt-sources: Get:9 http://localhost:3142/debian sid/main amd64 
Packages 2018-01-03-0225.05.pdiff [11.6 kB]
E: 80append-apt-sources: Get:10 http://localhost:3142/debian sid/main amd64 
Packages 2018-01-03-0826.10.pdiff [1432 B]
E: 80append-apt-sources: Get:11 http://localhost:3142/debian sid/main amd64 
Packages 2018-01-03-1421.25.pdiff [16.4 kB]
E: 80append-apt-sources: Get:7 http://localhost:3142/debian sid/main Sources 
2018-01-03-1421.25.pdiff [14.1 kB]
E: 80append-apt-sources: Get:11 http://localhost:3142/debian sid/main amd64 
Packages 2018-01-03-1421.25.pdiff [16.4 kB]
E: 80append-apt-sources: Get:12 http://localhost:3142/debian sid/main 
Translation-en [5931 kB]
E: 80append-apt-sources: Fetched 6310 kB in 5s (1153 kB/s)
I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-snap-d120cfe2-d0ea-4691-ba5b-c7ab00433bc9' with 
'<>'

+--+
| Update chroot|
+--+

Hit:1 http://localhost:3142/debian sid InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Local sources
-

/tmp/opensmtpd_6.0.2p1-2.dsc exists in /tmp; copying to chroot
I: NOTICE: Log filtering will replace 
'build/opensmtpd-3pEn6P/opensmtpd-6.0.2p1' with '<>'
I: NOTICE: Log filtering will replace 'build/opensmtpd-3pEn6P' with 
'<>'

+--+
| Install build-essential  |
+--+


Setup apt archive
-

Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in 
'/<>/resolver-EpZHeW/apt_archive/sbuild-build-depends-core-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy
dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
Ign:1 copy:/<>/resolver-EpZHeW/apt_archive ./ InRelease
Get:2 copy:/<>/resolver-EpZHeW/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/resolver-EpZHeW/apt_archive ./ Release.gpg
Get:4

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2018-01-04 Thread Mattia Rizzolo

Control: fixed -1 8.9.3~dfsg-1

On Mon, Dec 18, 2017 at 09:55:37PM +0100, Jérémy Lal wrote:
> Good news: i don't get this segfault using nodejs 8.9.3 that i just
> uploaded to experimental.

Tweaking metadata to say so, then.

This bug should probably also be closed at some point.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#859297: marked as done (nodejs: Please migrate to openssl1.1 in buster)

Your message dated Thu, 4 Jan 2018 16:58:17 +0100
with message-id <20180104155814.ga23...@mapreri.org>
and subject line Re: Bug#859297: nodejs: Please migrate to openssl1.1 in buster
has caused the Debian Bug report #859297,
regarding nodejs: Please migrate to openssl1.1 in buster
to be marked as done.

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

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

--
859297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 4.4.3~dfsg-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
OpenSSL this package fail to build. A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/nodejs_4.4.3~dfsg-1_amd64-20160529-1457

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail. There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.

Kurt
--- End Message ---
--- Begin Message ---
Version: 8.9.3~dfsg-1

On Tue, Dec 26, 2017 at 10:28:36AM +0100, Jérémy Lal wrote:
> This is fixed in nodejs 8.9.3~dfsg-1 in experimental, soon to be
> transitioned.

So let's close this bug (you could have done so in the changelog).

--
regards,
Mattia Rizzolo

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

signature.asc
Description: PGP signature
--- End Message ---

Bug#886325: [Pkg-utopia-maintainers] Bug#886325: dbus daemon does not start with error "undefined symbol: XML_SetHashSalt"

2018-01-04 Thread Michael Biebl

Am 04.01.2018 um 14:37 schrieb Alberto Brosich:
> Package: dbus
> Version: 1.10.24-0+deb9u1
> Severity: grave
> Justification: renders package unusable
> 
> I'm working on Debian stable.
> 
> After a small update and a reboot, dbus daemon does not start with the
> following message:
> 
> systemd[1]: Started D-Bus System Message Bus.
> dbus-daemon[1350]: /usr/bin/dbus-daemon: symbol lookup error:
> /usr/bin/dbus-daemon: undefined symbol: XML_SetHashSalt
> amaltea systemd[1]: dbus.service: Main process exited, code=exited,
> status=127/n/a
> amaltea systemd[1]: dbus.service: Unit entered failed state.
> amaltea systemd[1]: dbus.service: Failed with result 'exit-code'
> 
> Starting manually same result:
> # DBUS_VERBOSE=1 dbus-daemon --session --print-address
> dbus-daemon: symbol lookup error: dbus-daemon: undefined symbol:
> XML_SetHashSalt
> 
> Other services depend on it, therefore the machine is unusable.
> 
> I tried to upgrade expat and libexpat1 packages from testing. libexpat1
> depends on libc6 >= 2.25, no upgrade possible.

Can you please provide the output of
ldd /usr/bin/dbus-daemon


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

Processing control commands:

> fixed -1 8.9.3~dfsg-1
Bug #878674 [nodejs] nodejs segfaults when building d3-* with webpack
There is no source info for the package 'nodejs' at version '8.9.3~dfsg-1' with 
architecture ''
Unable to make a source version for version '8.9.3~dfsg-1'
Marked as fixed in versions 8.9.3~dfsg-1.

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

Bug#886330: sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No such file or directory

2018-01-04 Thread Andreas Tille

Hi,

just a quick note (I'm quite busy with real life):  The issue seems to
be caused by the fact that libquazip5-headers which is pulled in due
to dependencies provides

/usr/include/quazip5/quazip.h

the file

/usr/include/quazip/quazip.h

exists in libquazip-headers.  I admit I have no real idea what the
correct fix is since I'm not a Qt expert.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#859829: bump

2018-01-04 Thread Ferenc Wágner

I'd like to keep the current Shibboleth stack in testing at least until
I manage to upload the last backports.
-- 
Feri

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

2018-01-04 Thread Eric Valette


On 01/04/2018 03:13 PM, Pino Toscano wrote:

Firrst thanks for taking time to respond to my questions...


No, there are parts of kdelibs4support that use OpenSSL, but because of
its obnoxious license then it is not common for code using OpenSSL to
link directly to it.


It do not follow the idea behind link vs package dependency (except due 
to automatic dependency creating tools). Maybe via dlopen then but this 
should have a dependency nevertheless or the dlopen will fail and if 
package expects it... So If this is the case some dependencies are 
missing because removing libkf5kdelibs4support-dev enable to remove 
libsll1.0-dev and then dependency on libsll1.0.2 should be explicit...



There is no such "libssl1.0.0" in Debian, so you indeed get almost no
packages depending on it.  The library for libssl1.0-dev is
libssl1.0.2, and you can verify there are still many packages depending
on it.



OK I goofed because I still have an old one on my system (or it comes 
via oracle virtualbox) and should have done the rdepend on libssl1.0.2:



dpkg -l libssl*
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   Architecture 
Description

+++-=-=-=-
ii  libssl-dev:amd64  1.1.0g-2  amd64 Secure 
Sockets Layer toolkit - development files
ii  libssl-doc1.1.0g-2  all   Secure 
Sockets Layer toolkit - development documentation
un  libssl1.0-dev (no 
description available)
ii  libssl1.0.0:amd64 1.0.2d-1  amd64 Secure 
Sockets Layer toolkit - shared libraries
ii  libssl1.0.2:amd64 1.0.2n-1  amd64 Secure 
Sockets Layer toolkit - shared libraries
ii  libssl1.1:amd64   1.1.0g-2  amd64 Secure 
Sockets Layer toolkit - shared libraries


But:

apt-rdepends -r libssl1.0.2 | more
Reading package lists... Done
Building dependency tree
Reading state information... Done
libssl1.0.2
  Reverse Depends: android-tools-adb (>= 5.1.1.r29-2)
  Reverse Depends: aolserver4-nsopenssl (>= 3.0beta26-6)
  Reverse Depends: bip (>= 0.8.9-1.1)
  Reverse Depends: boxbackup-client (>= 0.12~gitcf52058f-3)
  Reverse Depends: boxbackup-server (>= 0.12~gitcf52058f-3)
  Reverse Depends: cfengine2 (>= 2.2.10-7)
  Reverse Depends: ckermit (>= 302-5.3)
  Reverse Depends: cl-plus-ssl (20170630-1)
  Reverse Depends: conserver-client (>= 8.2.1-1+b1)
  Reverse Depends: conserver-server (>= 8.2.1-1+b1)
  Reverse Depends: cqrlog (2.0.5-3)
  Reverse Depends: freerdp-x11 (>= 1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: ftp-ssl (>= 0.17.34+0.2-4)
  Reverse Depends: gnugk (>= 2:3.6-1+b4)
  Reverse Depends: groestlcoin-qt (>= 2.13.3~dfsg-3)
  Reverse Depends: groestlcoin-tx (>= 2.13.3~dfsg-3)
  Reverse Depends: groestlcoind (>= 2.13.3~dfsg-3)
  Reverse Depends: gvpe (>= 3.0-1)
  Reverse Depends: hhvm (>= 3.21.0+dfsg-2+b1)
  Reverse Depends: httest (>= 2.4.18-1.1)
  Reverse Depends: hydra (>= 8.6-1)
  Reverse Depends: idecrypt (>= 3.0.19.ds1-8)
  Reverse Depends: ifstat (>= 1.1-8.1)
  Reverse Depends: ike (>= 2.2.1+dfsg-6)
  Reverse Depends: ike-qtgui (>= 2.2.1+dfsg-6)
  Reverse Depends: ipsec-tools (>= 1:0.8.2+20140711-10)
  Reverse Depends: isakmpd (>= 20041012-7.4)
  Reverse Depends: jabberd2 (>= 2.6.1-1+b1)
  Reverse Depends: kannel (>= 1.4.4-5)
  Reverse Depends: kannel-extras (>= 1.4.4-5)
  Reverse Depends: kannel-sqlbox (>= 0.7.2-4+b1)
  Reverse Depends: karlyriceditor (>= 2.2-dmo1)
  Reverse Depends: kopete (>= 4:16.08.1-3)
  Reverse Depends: kore (>= 2.0.0-2+b1)
  Reverse Depends: lastpass-cli (>= 1.0.0-1.2)
  Reverse Depends: libapache2-mod-auth-cas (>= 1.1-2.1)
  Reverse Depends: libapache2-mod-authn-webid (>= 0~20110301-5)
  Reverse Depends: libcurl3 (>= 7.57.0-1)
  Reverse Depends: libdcmtk8 (>= 3.6.1~20160216-4)
  Reverse Depends: libdigidoc-tools (>= 3.10.1.1208+ds1-2.1)
  Reverse Depends: libdigidoc2 (>= 3.10.1.1208+ds1-2.1)
  Reverse Depends: libfreerdp-cache1.1 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-client1.1 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-codec1.1 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-common1.1.0 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-core1.1 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-crypto1.1 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-gdi1.1 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-locale1.1 (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse Depends: libfreerdp-plugins-standard (>= 
1.1.0~git20140921.1.440916e+dfsg1-15)
  Reverse

Processed: Re: Bug#883100: ksudoku FTBFS on armel/armhf: error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr'

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

> severity 883100 important
Bug #883100 [src:ksudoku] ksudoku FTBFS on armel/armhf: error: conflicting 
declaration 'typedef ptrdiff_t GLsizeiptr'
Severity set to 'important' from 'serious'
> tag 883100 - patch
Bug #883100 [src:ksudoku] ksudoku FTBFS on armel/armhf: error: conflicting 
declaration 'typedef ptrdiff_t GLsizeiptr'
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Re: Bug#883626: kubrick FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

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

> severity 883626 important
Bug #883626 [src:kubrick] kubrick FTBFS on armel/armhf: error: conflicting 
declaration 'typedef khronos_ssize_t GLsizeiptr'
Severity set to 'important' from 'serious'
> tag 883626 - patch
Bug #883626 [src:kubrick] kubrick FTBFS on armel/armhf: error: conflicting 
declaration 'typedef khronos_ssize_t GLsizeiptr'
Ignoring request to alter tags of bug #883626 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#883626: kubrick FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

severity 883626 important
tag 883626 - patch
thanks

Since kubrick was removed from unstable (and soon testing), this is no
more a blocking issue.

-- 
Pino Toscano

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

Bug#883100: ksudoku FTBFS on armel/armhf: error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr'

severity 883100 important
tag 883100 - patch
thanks

Since ksudoku was removed from unstable (and soon testing), this is no
more a blocking issue.

-- 
Pino Toscano

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

Bug#886330: sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No such file or directory

2018-01-04 Thread Chris Lamb

Source: sleepyhead
Version: 1.0.0-beta-2+dfsg-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

sleepyhead fails to build from source in unstable/amd64:

  […]

  g++ -c -pipe -g -O2 -fdebug-prefix-map=«BUILDDIR»=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W 
-D_REENTRANT -fPIC -DLOCK_RESMED_SESSIONS -DGIT_BRANCH=\"UNKNOWN\" 
-DGIT_REVISION=\"UNKNOWN\" -DBETA_BUILD -D_TTY_POSIX_ -DQT_NO_DEBUG 
-DQT_PRINTSUPPORT_LIB -DQT_WEBKITWIDGETS_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB 
-DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SERIALPORT_LIB 
-DQT_CORE_LIB -I../../sleepyhead -I. -isystem /usr/include/x86_64-linux-gnu/qt5 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSerialPort -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o UpdaterWindow.o 
../../sleepyhead/UpdaterWindow.cpp
  ../../sleepyhead/UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No 
such file or directory
   #include 
^
  compilation terminated.
  Makefile:1449: recipe for target 'UpdaterWindow.o' failed

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


sleepyhead.1.0.0-beta-2+dfsg-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On giovedì 4 gennaio 2018 15:03:38 CET Eric Valette wrote:
> On 01/04/2018 02:25 PM, Pino Toscano wrote:
> > On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote:
> >>> this is a duplicate of bug #850888, since the dependency in the -dev
> >>> package depends on which libssl was used for the build.  When
> >>> kdelibs4support is ported to libssl1.1, then the dependency in the -dev
> >>> package will be updated.
> >> But if the kdelibs4supportpackage was build using libsll1.0-dev, then
> >> some  kdelibs4support generated packages should depend on libsll1.0.0
> >> which is not the case.
> > 
> > kdelibs4support is built against libssl1.0.  There are few publich
> > headers of it that include libssl headers, so that warrants the
> > dependency in the -dev package -- but they are not used a lot, so it
> > will not cause a dependency on that on the majority (if not all) of
> > packages that build using kdelibs4support (also almost all the
> > kde-related packages are built using --as-needed).
> > 
> > So, what you said is not true, and partially does not make any sense.
> 
> Sorry to be stupid but:
> 
> If I understand, the include exported libkf5kdelibs4support-dev by 
> require the sll headers because some of them are included but are not 
> used by the packages itself. Right?

No, there are parts of kdelibs4support that use OpenSSL, but because of
its obnoxious license then it is not common for code using OpenSSL to
link directly to it.

> But then other packages build using kdelibs4supportpackage-dev should 
> then depend on libsll1.0.0 if they really use the headers requiring ssl 
> includes and sll API and not only macros

As I wrote above, the usage of the SSL-using parts in kdelibs4support
is not common; indeed, if anything links to kdelibs4support and uses
those parts, then it must use libssl1.0-dev (same as kdelibs4support
to avoid API mismatches), which is a dependency in our -dev.

> which is not the case as shown via apt-rdepends in original report.

There is no such "libssl1.0.0" in Debian, so you indeed get almost no
packages depending on it.  The library for libssl1.0-dev is
libssl1.0.2, and you can verify there are still many packages depending
on it.

-- 
Pino Toscano

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

Bug#885635: QScintilla2 Transition Started

2018-01-04 Thread Arto Jantunen

Scott Kitterman  writes:
> In the interests of moving the transition along, not having heard back, I'm 
> preparing an NMU and plan to upload shortly.

Thanks for the NMU, I've had a busy week..

-- 
Arto Jantunen

Bug#881856: marked as done (opensaml2: CVE-2017-16853: Dynamic MetadataProvider fails to install security filters (CPPOST-105))

Your message dated Thu, 04 Jan 2018 15:02:40 +0100
with message-id <87po6pafi7@lant.ki.iif.hu>
and subject line These have already been fixed in all relevant distributions
has caused the Debian Bug report #881856,
regarding opensaml2: CVE-2017-16853: Dynamic MetadataProvider fails to install 
security filters (CPPOST-105)
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.)


-- 
881856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensaml2
Version: 2.5.3-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Control: clone -1 -2
Control: reassign -2 shibboleth-sp2 2.5.3+dfsg-2
Control: retitle -2 shibboleth-sp2: Dynamic MetadataProvider fails to install 
security filters (SSCPP-763)

Hi

As per https://shibboleth.net/community/advisories/secadv_20171115.txt
an issue affecting opensaml2 and shibboleth-sp2:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Shibboleth Service Provider Security Advisory [15 November 2017]

An updated version of the Shibboleth Service Provider software
is available which corrects a critical security issue in the
"Dynamic" metadata provider plugin.

Deployers making use of the affected feature should apply the
relevant update at the soonest possible moment.

NOTE: CVEs for this issue are forthcoming from the Debian Project
and this advisory will be updated if and when they are obtained.

Dynamic MetadataProvider fails to install security filters

The Shibboleth Service Provider software includes a MetadataProvider
plugin with the plugin type "Dynamic" to obtain metadata on demand
from a query server, in place of the more typical mode of downloading
aggregates separately containing all of the metadata to load.

All the plugin types rely on MetadataFilter plugins to perform critical
security checks such as signature verification, enforcement of validity
periods, and other checks specific to deployments.

Due to a coding error, the "Dynamic" plugin fails to configure itself
with the filters provided to it and thus omits whatever checks they are
intended to perform, which will typically leave deployments vulnerable
to active attacks involving the substitution of metadata if the network
path to the query service is compromised.

Affected Systems
==
All versions of the Service Provider software prior to V2.6.1 contain
this vulnerability.

There are no known mitigations to prevent this attack apart from
applying this update. Deployers should take immediate steps, and
may wish to disable the use of this feature until the upgrade is done.

Service Provider Deployer Recommendations
===
Upgrade to V2.6.1 or later of the Service Provider and restart the
shibd service/daemon.

Sites relying on official RPM packages or Macports can update via the
yum and port commands respectively.

For those using platforms unsupported by the project team directly,
refer to your vendor or package source directly for information on
obtaining the fixed version. If the update from your vendor lags,
you may consider building from source for your own use as an interim
step.

The patch commit that corrects this issue can be found at [1].

Additional Recommendations for Federation Operators
=
Operators of metadata query services in support of this feature may
wish to consider implementing security checks after a suitable upgrade
window has elapsed to prevent use of affected versions or follow up
with deployers. The User Agent string in requests to the service
will contain the version of the software.

Note Regarding OpenSAML Library
=
An identical issue exists in the DynamicMetadataProvider class in
the OpenSAML-C library in all versions prior to V2.6.1. Applications
making direct use of this library must be independently updated to
correct this vulnerability, but this fix does not correct the issue
with respect to the use of the Shibboleth SP.

The patch commit that corrects the OpenSAML issue can be found at [2].

Credits
=
Rod Widdowson, Steading System Software LLP

[1] https://git.shibboleth.net/view/?p=cpp-sp.git;a=commit;
h=b66cceb0e992c351ad5e2c665229ede82f261b16

[2] https://git.shibboleth.net/view/?p=cpp-opensaml.git;a=commit;
h=6182b0acf2df670e75423c2ed7afe6950ef11c9d

URL for this Security Advisory:
https://shibboleth.net/community/advisories/secadv_20171115.txt

-BEGIN PGP

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

2018-01-04 Thread Eric Valette


On 01/04/2018 02:25 PM, Pino Toscano wrote:

On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote:

this is a duplicate of bug #850888, since the dependency in the -dev
package depends on which libssl was used for the build.  When
kdelibs4support is ported to libssl1.1, then the dependency in the -dev
package will be updated.

But if the kdelibs4supportpackage was build using libsll1.0-dev, then
some  kdelibs4support generated packages should depend on libsll1.0.0
which is not the case.


kdelibs4support is built against libssl1.0.  There are few publich
headers of it that include libssl headers, so that warrants the
dependency in the -dev package -- but they are not used a lot, so it
will not cause a dependency on that on the majority (if not all) of
packages that build using kdelibs4support (also almost all the
kde-related packages are built using --as-needed).

So, what you said is not true, and partially does not make any sense.


Sorry to be stupid but:

If I understand, the include exported libkf5kdelibs4support-dev by 
require the sll headers because some of them are included but are not 
used by the packages itself. Right?


But then other packages build using kdelibs4supportpackage-dev should 
then depend on libsll1.0.0 if they really use the headers requiring ssl 
includes and sll API and not only macros which is not the case as shown 
via apt-rdepends in original report.


So I still wonder if this should be libsll1.0-dev or libssl-dev. And in 
any case this should be reworked for the ssl 1.1 transition as mentioned 
already. Nevermind


-- eric

Bug#881857: marked as done (shibboleth-sp2: CVE-2017-16852: Dynamic MetadataProvider fails to install security filters (SSCPP-763))

Your message dated Thu, 04 Jan 2018 15:02:40 +0100
with message-id <87po6pafi7@lant.ki.iif.hu>
and subject line These have already been fixed in all relevant distributions
has caused the Debian Bug report #881857,
regarding shibboleth-sp2: CVE-2017-16852: Dynamic MetadataProvider fails to 
install security filters (SSCPP-763)
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.)


-- 
881857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensaml2
Version: 2.5.3-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Control: clone -1 -2
Control: reassign -2 shibboleth-sp2 2.5.3+dfsg-2
Control: retitle -2 shibboleth-sp2: Dynamic MetadataProvider fails to install 
security filters (SSCPP-763)

Hi

As per https://shibboleth.net/community/advisories/secadv_20171115.txt
an issue affecting opensaml2 and shibboleth-sp2:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Shibboleth Service Provider Security Advisory [15 November 2017]

An updated version of the Shibboleth Service Provider software
is available which corrects a critical security issue in the
"Dynamic" metadata provider plugin.

Deployers making use of the affected feature should apply the
relevant update at the soonest possible moment.

NOTE: CVEs for this issue are forthcoming from the Debian Project
and this advisory will be updated if and when they are obtained.

Dynamic MetadataProvider fails to install security filters

The Shibboleth Service Provider software includes a MetadataProvider
plugin with the plugin type "Dynamic" to obtain metadata on demand
from a query server, in place of the more typical mode of downloading
aggregates separately containing all of the metadata to load.

All the plugin types rely on MetadataFilter plugins to perform critical
security checks such as signature verification, enforcement of validity
periods, and other checks specific to deployments.

Due to a coding error, the "Dynamic" plugin fails to configure itself
with the filters provided to it and thus omits whatever checks they are
intended to perform, which will typically leave deployments vulnerable
to active attacks involving the substitution of metadata if the network
path to the query service is compromised.

Affected Systems
==
All versions of the Service Provider software prior to V2.6.1 contain
this vulnerability.

There are no known mitigations to prevent this attack apart from
applying this update. Deployers should take immediate steps, and
may wish to disable the use of this feature until the upgrade is done.

Service Provider Deployer Recommendations
===
Upgrade to V2.6.1 or later of the Service Provider and restart the
shibd service/daemon.

Sites relying on official RPM packages or Macports can update via the
yum and port commands respectively.

For those using platforms unsupported by the project team directly,
refer to your vendor or package source directly for information on
obtaining the fixed version. If the update from your vendor lags,
you may consider building from source for your own use as an interim
step.

The patch commit that corrects this issue can be found at [1].

Additional Recommendations for Federation Operators
=
Operators of metadata query services in support of this feature may
wish to consider implementing security checks after a suitable upgrade
window has elapsed to prevent use of affected versions or follow up
with deployers. The User Agent string in requests to the service
will contain the version of the software.

Note Regarding OpenSAML Library
=
An identical issue exists in the DynamicMetadataProvider class in
the OpenSAML-C library in all versions prior to V2.6.1. Applications
making direct use of this library must be independently updated to
correct this vulnerability, but this fix does not correct the issue
with respect to the use of the Shibboleth SP.

The patch commit that corrects the OpenSAML issue can be found at [2].

Credits
=
Rod Widdowson, Steading System Software LLP

[1] https://git.shibboleth.net/view/?p=cpp-sp.git;a=commit;
h=b66cceb0e992c351ad5e2c665229ede82f261b16

[2] https://git.shibboleth.net/view/?p=cpp-opensaml.git;a=commit;
h=6182b0acf2df670e75423c2ed7afe6950ef11c9d

URL for this Security Advisory:
https://shibboleth.net/community/advisories/secadv_20171115.txt

-BEGIN PGP

Bug#886325: dbus daemon does not start with error "undefined symbol: XML_SetHashSalt"

2018-01-04 Thread Alberto Brosich

Package: dbus
Version: 1.10.24-0+deb9u1
Severity: grave
Justification: renders package unusable

I'm working on Debian stable.

After a small update and a reboot, dbus daemon does not start with the
following message:

systemd[1]: Started D-Bus System Message Bus.
dbus-daemon[1350]: /usr/bin/dbus-daemon: symbol lookup error:
/usr/bin/dbus-daemon: undefined symbol: XML_SetHashSalt
amaltea systemd[1]: dbus.service: Main process exited, code=exited,
status=127/n/a
amaltea systemd[1]: dbus.service: Unit entered failed state.
amaltea systemd[1]: dbus.service: Failed with result 'exit-code'

Starting manually same result:
# DBUS_VERBOSE=1 dbus-daemon --session --print-address
dbus-daemon: symbol lookup error: dbus-daemon: undefined symbol:
XML_SetHashSalt

Other services depend on it, therefore the machine is unusable.

I tried to upgrade expat and libexpat1 packages from testing. libexpat1
depends on libc6 >= 2.25, no upgrade possible.

The versions of packages are:

ii  dbus   1.10.24-0+deb9u1
ii  expat  2.2.5-3 (was 2.2.0)
ii  libexpat1:amd642.2.0-2+deb9u1

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

Kernel: Linux 4.9.0-4-amd64 (SMP w/24 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)

Versions of packages dbus depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libapparmor1 2.11.0-3
ii  libaudit11:2.6.7-2
ii  libc62.24-11+deb9u1
ii  libcap-ng0   0.7.7-3+b1
ii  libdbus-1-3  1.10.24-0+deb9u1
ii  libexpat12.2.0-2+deb9u1
ii  libselinux1  2.6-3+b3
ii  libsystemd0  232-25+deb9u1
ii  lsb-base 9.20161125

dbus recommends no packages.

Versions of packages dbus suggests:
pn  default-dbus-session-bus | dbus-session-bus  

Versions of packages dbus is related to:
pn  dbus-x11  
ii  systemd   232-25+deb9u1
ii  systemd-sysv  232-25+deb9u1

-- no debconf information

Bug#885035: aeskulap: Please don't (build)-depend on gconfmm2.6

2018-01-04 Thread Gert Wollny

On 23.12.2017 13:55, Simon McVittie wrote:

> On Sat, 23 Dec 2017 at 07:10:49 +0100, Andreas Tille wrote:
>> When droping libgconfmm-2.6-dev from Build-Depends I get
>>
>> configure.ac:43: error: possibly undefined macro: AM_GCONF_SOURCE_2
>>
>> What package provides this macro?
>
> (
> will eventually have a longer list of requests to stop using GConf)
>
> Stopping using GConf is a change to upstream source code. The modern
> replacement is GSettings, part of GIO; for C++ code that should be
> available via glibmm, although I don't know which specific APIs are
> involved.
>
I'll look into this as son as I get the time for it.

Best,
Gert

Bug#882247:

2018-01-04 Thread Tom Marble

Package: firefox
Version: 58.0~b4-1
Followup-For: Bug #882247

I also have this bug... adding reportbug details...

   * What led up to the situation?

Just starting firefox.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Tried on a new user account with no ~/.mozilla settings -- same result.

   * What was the outcome of this action?

Blank window showing 

-- no debconf information

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

2018-01-04 Thread Eric Valette


On 01/04/2018 02:13 PM, Pino Toscano wrote:

reassign 886322 kdelibs4support/5.37.0-2
forcemerge 850888 886322
thanks

Hi,

this is a duplicate of bug #850888, since the dependency in the -dev
package depends on which libssl was used for the build.  When
kdelibs4support is ported to libssl1.1, then the dependency in the -dev
package will be updated.
But if the kdelibs4supportpackage was build using libsll1.0-dev, then 
some  kdelibs4support generated packages should depend on libsll1.0.0 
which is not the case.


-- eric

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote:
> > this is a duplicate of bug #850888, since the dependency in the -dev
> > package depends on which libssl was used for the build.  When
> > kdelibs4support is ported to libssl1.1, then the dependency in the -dev
> > package will be updated.
> But if the kdelibs4supportpackage was build using libsll1.0-dev, then 
> some  kdelibs4support generated packages should depend on libsll1.0.0 
> which is not the case.

kdelibs4support is built against libssl1.0.  There are few publich
headers of it that include libssl headers, so that warrants the
dependency in the -dev package -- but they are not used a lot, so it
will not cause a dependency on that on the majority (if not all) of
packages that build using kdelibs4support (also almost all the
kde-related packages are built using --as-needed).

So, what you said is not true, and partially does not make any sense.

-- 
Pino Toscano

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

Processed: lower severity to keep tryton in testing for now

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

> severity 885468 important
Bug #885468 [src:pycha] pycha: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Processed: reassign 886322 to src:kdelibs4support, forcibly merging 850888 886322

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

> reassign 886322 src:kdelibs4support kdelibs4support/5.37.0-2
Bug #886322 [libkf5kdelibs4support-dev] libkf5kdelibs4support-dev: Should 
libkf5kdelibs4support-dev still depend on libssl1.0-dev
Bug reassigned from package 'libkf5kdelibs4support-dev' to 
'src:kdelibs4support'.
No longer marked as found in versions kdelibs4support/5.37.0-2.
Ignoring request to alter fixed versions of bug #886322 to the same values 
previously set
Bug #886322 [src:kdelibs4support] libkf5kdelibs4support-dev: Should 
libkf5kdelibs4support-dev still depend on libssl1.0-dev
Marked as found in versions kdelibs4support/5.37.0-2.
> forcemerge 850888 886322
Bug #850888 [src:kdelibs4support] kdelibs4support: Please migrate to openssl1.1 
in buster
Bug #850888 [src:kdelibs4support] kdelibs4support: Please migrate to openssl1.1 
in buster
Marked as found in versions kdelibs4support/5.37.0-2.
Bug #886322 [src:kdelibs4support] libkf5kdelibs4support-dev: Should 
libkf5kdelibs4support-dev still depend on libssl1.0-dev
Severity set to 'serious' from 'normal'
871056 was blocked by: 851080 859831 859557 873647 858936 859055 859718 873574 
859053 859671 859226 844303 858989 859673 859785 851084 859050 858937 851070 
859228 859717 828522 859551 847611 859052 835801 870775 851094 859782 850897 
858930 859720 828483 859740 851081 858993 828420 859222 859146 859555 858398 
828557 859829 851090 882549 858828 858857 867140 859540 828471 859544 828481 
859552 828449 850886 828329 828441 859750 858935 858939 848680 859553 851054 
828475 859716 851091 858386 851074 859545 858992 859742 858938 859674 851424 
828572 859297 871939 858991 870778 870779 859852 851087 859556 859719 853778 
827076 859543 851073 850898 850890 858927 851077 859790 828520 851069 850895 
859230 859791 883450 859367 859542 850888 828429 828451 859554 863568 859826 
859675 859783 859225 872885 859558 859145 882562 859416 828477 859834 854583 
859784 859054 858928 858929 859786 859224 882615 858990 851086 875349 859229 
859548 859232 858435 851078 859840 859853 859844 851085 859721 851079 874699 
853782 828413 851076 859789 858436 859550 828503 859546 859838 882561 859851 
851093 859715 858931 859669 859841
871056 was not blocking any bugs.
Added blocking bug(s) of 871056: 886322
Marked as found in versions kdelibs4support/5.22.0-1.
Added tag(s) buster and sid.
Merged 850888 886322
> thanks
Stopping processing here.

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

Processed (with 2 errors): Re: Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

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

> reassign 886322 kdelibs4support/5.37.0-2
Unknown command or malformed arguments to command.
> forcemerge 850888 886322
Bug #850888 [src:kdelibs4support] kdelibs4support: Please migrate to openssl1.1 
in buster
Unable to merge bugs because:
package of #886322 is 'libkf5kdelibs4support-dev' not 'src:kdelibs4support'
Failed to forcibly merge 850888: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#885647: marked as done (src:universalindentgui: Will FTBFS with new qscintilla2 in experimental)

Your message dated Thu, 04 Jan 2018 12:34:45 +
with message-id 
and subject line Bug#885647: fixed in universalindentgui 1.2.0-1.1
has caused the Debian Bug report #885647,
regarding src:universalindentgui: Will FTBFS with new qscintilla2 in 
experimental
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.)


-- 
885647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:universalindentgui
Version: 1.2.0-1
Severity: wishlist
Tags: patch

Dear Maintainer,

The qscintilla2 package in experimental contains a number of changes in
library naming to match upstream's changes.  As a result, universalindentgui
will FTBFS with this version due to a link failure.  I've attached a patch for
an eventual NMU (when the transition starts).  If you would prefer to handle
the upload yourself, please let me know.

Scott K
diff -Nru universalindentgui-1.2.0/debian/changelog universalindentgui-1.2.0/debian/changelog
--- universalindentgui-1.2.0/debian/changelog	2012-05-22 06:28:00.0 +
+++ universalindentgui-1.2.0/debian/changelog	2017-12-28 20:15:09.0 +
@@ -1,3 +1,10 @@
+universalindentgui (1.2.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for new qscintilla2 library names
+
+ -- Scott Kitterman   Thu, 28 Dec 2017 20:15:09 +
+
 universalindentgui (1.2.0-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru universalindentgui-1.2.0/debian/control universalindentgui-1.2.0/debian/control
--- universalindentgui-1.2.0/debian/control	2012-05-22 05:52:32.0 +
+++ universalindentgui-1.2.0/debian/control	2017-12-28 20:15:04.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Thomas Schweitzer 
 Uploaders: Fathi Boudra 
-Build-Depends: debhelper (>= 9), libqscintilla2-dev, libqt4-dev
+Build-Depends: debhelper (>= 9), libqscintilla2-qt4-dev, libqt4-dev
 Standards-Version: 3.9.3
 Homepage: http://universalindent.sourceforge.net
 
diff -Nru universalindentgui-1.2.0/debian/patches/qsci_rename.patch universalindentgui-1.2.0/debian/patches/qsci_rename.patch
--- universalindentgui-1.2.0/debian/patches/qsci_rename.patch	1970-01-01 00:00:00.0 +
+++ universalindentgui-1.2.0/debian/patches/qsci_rename.patch	2017-12-28 20:15:09.0 +
@@ -0,0 +1,40 @@
+--- universalindentgui-1.2.0.orig/UniversalIndentGUI.pro
 universalindentgui-1.2.0/UniversalIndentGUI.pro
+@@ -23,7 +23,7 @@ macx {
+  ICON = resources/UniversalIndentGUI.icns
+ }
+ else {
+- LIBS += -lqscintilla2
++ LIBS += -lqscintilla2_qt4
+ }
+ 
+ CONFIG(release, debug|release) {
+--- universalindentgui-1.2.0.orig/UniversalIndentGUI.xcodeproj/project.pbxproj
 universalindentgui-1.2.0/UniversalIndentGUI.xcodeproj/project.pbxproj
+@@ -571,7 +571,7 @@
+ );
+ OTHER_LDFLAGS = (
+ 	"-headerpad_max_install_names",
+-	"-lqscintilla2",
++	"-lqscintilla2_qt4",
+ 	"-L/opt/local/lib",
+ );
+ OTHER_REZFLAGS = "";
+@@ -637,7 +637,7 @@
+ );
+ OTHER_LDFLAGS = (
+ 	"-headerpad_max_install_names",
+-	"-lqscintilla2",
++	"-lqscintilla2_qt4",
+ 	"-L/opt/local/lib",
+ );
+ OTHER_REZFLAGS = "";
+@@ -701,7 +701,7 @@
+ );
+ OTHER_LDFLAGS = (
+ 	"-headerpad_max_install_names",
+-	"-lqscintilla2",
++	"-lqscintilla2_qt4",
+ 	"-L/opt/local/lib",
+ );
+ OTHER_REZFLAGS = "";
diff -Nru universalindentgui-1.2.0/debian/patches/series universalindentgui-1.2.0/debian/patches/series
--- universalindentgui-1.2.0/debian/patches/series	2012-05-22 06:30:31.0 +
+++ universalindentgui-1.2.0/debian/patches/series	2017-12-28 20:15:09.0 +
@@ -1 +1,2 @@
 disable_check_for_update.patch
+qsci_rename.patch
--- End Message ---
--- Begin Message ---
Source: universalindentgui
Source-Version: 1.2.0-1.1

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated universalindentgui 
package)

(This message was generated automatically at their request; if you
believe

Bug#885635: marked as done (src:sqlitebrowser: Will FTBFS with new qscintilla2)

Your message dated Thu, 04 Jan 2018 12:34:36 +
with message-id 
and subject line Bug#885635: fixed in sqlitebrowser 3.10.1-1.1
has caused the Debian Bug report #885635,
regarding src:sqlitebrowser: Will FTBFS with new qscintilla2
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.)


-- 
885635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sqlitebrowser
Version: 3.10.1-1
Severity: wishlist
Tags: patch

Dear Maintainer,

The qscintilla2 package in experimental contains a number of changes in
library naming to match upstream's changes.  As a result, sqlitebrowser will
FTBFS with this version due to a link failure.  I've attached a patch for an
eventual NMU (when the transition starts).  If you would prefer to handle the
upload yourself, please let me know.

Scott K
diff -Nru sqlitebrowser-3.10.1/debian/changelog sqlitebrowser-3.10.1/debian/changelog
--- sqlitebrowser-3.10.1/debian/changelog	2017-11-04 07:55:35.0 -0400
+++ sqlitebrowser-3.10.1/debian/changelog	2017-12-28 13:25:34.0 -0500
@@ -1,3 +1,10 @@
+sqlitebrowser (3.10.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for new qscintilla2 library names
+
+ -- Scott Kitterman   Thu, 28 Dec 2017 13:25:18 -0500
+
 sqlitebrowser (3.10.1-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru sqlitebrowser-3.10.1/debian/control sqlitebrowser-3.10.1/debian/control
--- sqlitebrowser-3.10.1/debian/control	2017-11-04 07:55:35.0 -0400
+++ sqlitebrowser-3.10.1/debian/control	2017-12-28 13:26:01.0 -0500
@@ -2,7 +2,7 @@
 Section: database
 Priority: optional
 Maintainer: Arto Jantunen 
-Build-Depends: debhelper (>= 10), qtbase5-dev, libsqlite3-dev, cmake, libantlr-dev, qttools5-dev, qttools5-dev-tools, libqt5scintilla2-dev
+Build-Depends: debhelper (>= 10), qtbase5-dev, libsqlite3-dev, cmake, libantlr-dev, qttools5-dev, qttools5-dev-tools, libqscintilla2-qt5-dev
 Standards-Version: 4.1.1
 Homepage: http://sqlitebrowser.org/
 Vcs-Browser: https://anonscm.debian.org/gitweb/?p=collab-maint/sqlitebrowser.git
diff -Nru sqlitebrowser-3.10.1/debian/patches/0001-Use-system-qscintilla2.patch sqlitebrowser-3.10.1/debian/patches/0001-Use-system-qscintilla2.patch
--- sqlitebrowser-3.10.1/debian/patches/0001-Use-system-qscintilla2.patch	2017-11-04 07:55:35.0 -0400
+++ sqlitebrowser-3.10.1/debian/patches/0001-Use-system-qscintilla2.patch	2017-12-28 13:25:02.0 -0500
@@ -17,7 +17,7 @@
  
  find_library ( QSCINTILLA_LIBRARY
 -  NAMES qscintilla qscintilla2 libqscintilla2
-+  NAMES qscintilla qscintilla2 libqscintilla2 qt5scintilla2
++  NAMES qscintilla qscintilla2 libqscintilla2 qscintilla2_qt5
HINTS ${QT_LIBRARY_DIR}
  )
  
@@ -30,7 +30,7 @@
  UI_DIR = .ui
  INCLUDEPATH += $$PWD/../libs/antlr-2.7.7 $$PWD/../libs/qhexedit $$PWD/../libs/qcustomplot-source $$PWD/../libs/qscintilla/Qt4Qt5 $$PWD/..
 -LIBS += -L$$LIBPATH_QHEXEDIT -L$$LIBPATH_ANTLR -L$$LIBPATH_QCUSTOMPLOT -L$$LIBPATH_QSCINTILLA -lantlr -lqhexedit -lqcustomplot -lqscintilla2
-+LIBS += -L$$LIBPATH_QHEXEDIT -L$$LIBPATH_ANTLR -L$$LIBPATH_QCUSTOMPLOT -L$$LIBPATH_QSCINTILLA -lantlr -lqhexedit -lqcustomplot -lqt5scintilla2
++LIBS += -L$$LIBPATH_QHEXEDIT -L$$LIBPATH_ANTLR -L$$LIBPATH_QCUSTOMPLOT -L$$LIBPATH_QSCINTILLA -lantlr -lqhexedit -lqcustomplot -lqscintilla2_qt5
  DEPENDPATH += $$PWD/../libs/antlr-2.7.7 $$PWD/../libs/qhexedit $$PWD/../libs/qcustomplot-source $$PWD/../libs/qscintilla/Qt4Qt5
  
  unix {
@@ -44,8 +44,8 @@
  link_directories("${CMAKE_CURRENT_BINARY_DIR}/${QSCINTILLA_DIR}")
 -add_dependencies(test-sqlobjects qscintilla2)
 -target_link_libraries(test-sqlobjects qscintilla2)
-+add_dependencies(test-sqlobjects qt5scintilla2)
-+target_link_libraries(test-sqlobjects qt5scintilla2)
++add_dependencies(test-sqlobjects qscintilla2_qt5)
++target_link_libraries(test-sqlobjects qscintilla2_qt5)
  add_test(test-sqlobjects test-sqlobjects)
  
  # test-import
@@ -55,6 +55,6 @@
  link_directories("${CMAKE_CURRENT_BINARY_DIR}/${QSCINTILLA_DIR}")
 -add_dependencies(test-regex qscintilla2)
 -target_link_libraries(test-regex qscintilla2)
-+add_dependencies(test-regex qt5scintilla2)
-+target_link_libraries(test-regex qt5scintilla2)
++add_dependencies(test-regex qscintilla2_qt5)
++target_link_libraries(test-regex qscintilla2_qt5)
  add_test(test-regex test-regex)
--- End Message ---
--- Begin Message ---
Source: sqlitebrowser
Source-Version: 3.10.1-1.1

We believe that the bug you

Bug#877198: marked as done (monkeystudio FTBFS: fatal error: pluginmanager_p.h: No such file or directory)

Your message dated Thu, 04 Jan 2018 12:32:35 +
with message-id 
and subject line Bug#886298: Removed package(s) from unstable
has caused the Debian Bug report #877198,
regarding monkeystudio FTBFS: fatal error: pluginmanager_p.h: 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.)


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

Some recent change in unstable makes monkeystudio FTBFS:

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

...
src/QtDesignerManager.cpp:50:10: fatal error: pluginmanager_p.h: No such file 
or directory
 #include "pluginmanager_p.h"
  ^~~
compilation terminated.
Makefile:792: recipe for target 
'../../../build/plugins/Linux-x86_64/debug/obj/QtDesignerManager.o' failed
make[4]: *** 
[../../../build/plugins/Linux-x86_64/debug/obj/QtDesignerManager.o] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.9.0.4+git20161218-1+rm

Dear submitter,

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

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

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

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

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

Bug#810671: marked as done (ifupdown-scripts-zg2: fails to install in chroot: ERR: missing /etc/network/run. Is ifupdown configured?)

Your message dated Thu, 04 Jan 2018 12:30:49 +
with message-id 
and subject line Bug#886220: Removed package(s) from unstable
has caused the Debian Bug report #810671,
regarding ifupdown-scripts-zg2: fails to install in chroot: ERR: missing 
/etc/network/run. Is ifupdown configured?
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.)


-- 
810671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifupdown-scripts-zg2
Version: 0.6-1
Severity: serious
Tags: sid stretch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package ifupdown-scripts-zg2.
  (Reading database ... 
(Reading database ... 7466 files and directories currently installed.)
  Preparing to unpack .../ifupdown-scripts-zg2_0.6-1_all.deb ...
  Unpacking ifupdown-scripts-zg2 (0.6-1) ...
  Processing triggers for systemd (228-3) ...
  Setting up ifupdown-scripts-zg2 (0.6-1) ...
  ERR: missing /etc/network/run. Is ifupdown configured?
  dpkg: error processing package ifupdown-scripts-zg2 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (228-3) ...
  Errors were encountered while processing:
   ifupdown-scripts-zg2

I don't know whether this is specific to the piuparts test in a
chroot (no services being started there) or whether it happens in real
sid/stretch installations, too. Anyway, it must install in a chroot.

cheers,

Andreas


ifupdown-scripts-zg2_0.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.6-1+rm

Dear submitter,

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

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

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

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

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

Bug#796621: marked as done (ifupdown-scripts-zg2: Has init script in runlevel S but no matching service file)

Your message dated Thu, 04 Jan 2018 12:30:49 +
with message-id 
and subject line Bug#886220: Removed package(s) from unstable
has caused the Debian Bug report #796621,
regarding ifupdown-scripts-zg2: Has init script in runlevel S but no matching 
service file
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.)


-- 
796621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifupdown-scripts-zg2
Severity: important
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: init-rcs-service

Hi,

Your package ifupdown-scripts-zg2 has an initscript that is enabled
in runlevel S, but it does not provide a corresponding systemd
service unit.

Systemd generates units for all sysv init scripts that do not have a
corresponding systemd unit. By default, it sets
DefaultDependencies=yes, which means they get ordered after early
boot has finished.

The problem is that to preserve the runlevel S semantics, systemd in
debian is currently[1] ordering all S services Before=sysinit.target.
This target is particularly early in the boot sequence, which means
that it is most of the time too strict. In turn, this means it is
fairly easy to end up with dependency cycles. For an example, see bug
[763315]. Do note that the cycle still exists with sysvinit, it is
just that systemd complains more loudly.

Please add a systemd unit for the given service with the appropriate
dependencies, which most of the time will be less strict than
Before=sysinit.target. In other cases, the script is simply not
applicable in systemd, in which case the package should ship a
symlink to /dev/null as /lib/systemd/system/.service.

We have prepared a transition wiki page[2] explaining the issue in
more detail, and outlining some general guidance. Please refer to it
as it will have useful information.

If you have any other doubts, feel free to ask in
pkg-systemd-maintain...@lists.alioth.debian.org
-- 

[1] 
http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/
[763315] https://bugs.debian.org/763315
[2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration
--- End Message ---
--- Begin Message ---
Version: 0.6-1+rm

Dear submitter,

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

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

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

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

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

Bug#885626: marked as done (src:sonic-pi: Will FTBFS with new qscintilla2)

Your message dated Thu, 04 Jan 2018 12:19:48 +
with message-id 
and subject line Bug#885626: fixed in sonic-pi 2.10.0~repack-2.1
has caused the Debian Bug report #885626,
regarding src:sonic-pi: Will FTBFS with new qscintilla2
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.)


-- 
885626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sonic-pi
Version: 2.10.0~repack-2
Severity: wishlist
Tags: patch

Dear Maintainer,

The qscintilla2 package in experimental contains a number of changes in
library naming to match upstream's changes.  As a result, sonic-pi will FTBFS
with this version due to a link failure.  I've attached a patch for an
eventual NMU (when the transition starts).  If you would prefer to handle the
upload yourself, please let me know.

Scott K
diff -Nru sonic-pi-2.10.0~repack/debian/changelog sonic-pi-2.10.0~repack/debian/changelog
--- sonic-pi-2.10.0~repack/debian/changelog	2016-05-17 18:16:53.0 +
+++ sonic-pi-2.10.0~repack/debian/changelog	2017-12-28 17:33:51.0 +
@@ -1,3 +1,10 @@
+sonic-pi (2.10.0~repack-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for new QScintilla2 library names
+
+ -- Scott Kitterman   Thu, 28 Dec 2017 17:33:51 +
+
 sonic-pi (2.10.0~repack-2) unstable; urgency=medium
 
   [ Hanno Zulla ]
diff -Nru sonic-pi-2.10.0~repack/debian/control sonic-pi-2.10.0~repack/debian/control
--- sonic-pi-2.10.0~repack/debian/control	2016-05-17 11:43:40.0 +
+++ sonic-pi-2.10.0~repack/debian/control	2017-12-28 17:33:43.0 +
@@ -14,7 +14,7 @@
  qtbase5-dev,
  qttools5-dev,
  qttools5-dev-tools,
- libqt5scintilla2-dev,
+ libqscintilla2-qt5-dev,
  sc3-plugins-server,
  ruby,
  ruby-activesupport,
diff -Nru sonic-pi-2.10.0~repack/debian/patches/qsci_rename.patch sonic-pi-2.10.0~repack/debian/patches/qsci_rename.patch
--- sonic-pi-2.10.0~repack/debian/patches/qsci_rename.patch	1970-01-01 00:00:00.0 +
+++ sonic-pi-2.10.0~repack/debian/patches/qsci_rename.patch	2017-12-28 17:33:51.0 +
@@ -0,0 +1,14 @@
+--- sonic-pi-2.10.0~repack.orig/app/gui/qt/SonicPi.pro
 sonic-pi-2.10.0~repack/app/gui/qt/SonicPi.pro
+@@ -34,9 +34,9 @@ greaterThan(QT_MAJOR_VERSION, 4) {
+ # Linux only
+ unix:!macx {
+   lessThan(QT_MAJOR_VERSION, 5) {
+-LIBS += -lqscintilla2
++LIBS += -lqscintilla2_qt4
+   } else {
+-LIBS += -lqt5scintilla2
++LIBS += -lqscintilla2_qt5
+   }
+   QMAKE_CXXFLAGS += -Wall -Werror -Wextra
+ }
diff -Nru sonic-pi-2.10.0~repack/debian/patches/series sonic-pi-2.10.0~repack/debian/patches/series
--- sonic-pi-2.10.0~repack/debian/patches/series	2016-05-17 11:43:40.0 +
+++ sonic-pi-2.10.0~repack/debian/patches/series	2017-12-28 17:33:51.0 +
@@ -5,3 +5,4 @@
 05-doc-base-index.patch
 06-paths.patch
 07-examples-path.patch
+qsci_rename.patch
--- End Message ---
--- Begin Message ---
Source: sonic-pi
Source-Version: 2.10.0~repack-2.1

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated sonic-pi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Jan 2018 06:57:23 -0500
Source: sonic-pi
Binary: sonic-pi sonic-pi-server sonic-pi-server-doc sonic-pi-samples
Architecture: source amd64 all
Version: 2.10.0~repack-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Team 

Changed-By: Scott Kitterman 
Description:
 sonic-pi   - Live Coding for Everyone
 sonic-pi-samples - Audio samples for Sonic Pi
 sonic-pi-server - Backend server for Sonic Pi
 sonic-pi-server-doc - Documentation for Sonic Pi
Closes: 885626
Changes:
 sonic-pi (2.10.0~repack-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update for new QScintilla2 library names (Closes:

Bug#855251: Remove mentioned OGG support from package description

2018-01-04 Thread Bruno Kleinert

Am Mittwoch, den 03.01.2018, 16:50 + schrieb James Cowgill:
> Control: clone -1 -2
> Control: notfound -2 2.4.3-1
> Control: found -2 2.4.3-2
> Control: severity -2 normal
> Control: tags -2 - pending
> Control: retitle -2 easytag: re-enable ogg after corruption bug is
> fixed
> 
> Hi,
> 
> On 16/02/17 01:02, Samuele Battarra wrote:
> > Package: easytag
> > Version: 2.4.3-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > I have a ogg file encoded from a live cd, I split it to single
> > tracks with oggsplt and then tag the tracks with easytag.
> > When I play the files I hear a click at file change.
> > The click is not present in files before the tagging and if I tag
> > with kid3.
> 
> As you might have noticed, I have decided that the best way to fix
> this
> is to disable support for OGG and related media types in easytag for
> the
> time being. Solving this bug is apparently quite complex and while
> the
> upstream bug has been open for over a year, there has not been much
> progress on it. I think it is better to have some version in buster
> (which does not mangle your media files) than nothing at all.
> 
> I have cloned this bug to remind me to re-enable ogg support once the
> corruption bug is fixed.
> 
> Thanks,
> James

Hi James,

I suggest to remove the mentioned OGG support from the description of
the package for the time being, and suggest alternative packages to
users instead. Feel free to use and adapt the attached patch!

Cheers - Fuddldiff --git a/debian/changelog b/debian/changelog
index a8df5e1..4cae9d8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+easytag (2.4.3-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not mention OGG support in package description. Instead, suggest
+alternative packages to edit OGG file tags.
+
+ -- Bruno "Fuddl" Kleinert   Thu, 04 Jan 2018 12:52:46 +0100
+
 easytag (2.4.3-2) unstable; urgency=medium
 
   * debian/control:
diff --git a/debian/control b/debian/control
index 6e53796..36cabb6 100644
--- a/debian/control
+++ b/debian/control
@@ -49,9 +49,8 @@ Description: GTK+ editor for audio file tags
  .
  Currently EasyTAG supports the following:
   - View, edit, write tags of MP3, MP2 files (ID3 tag), FLAC files (FLAC Vorbis
-tag), Ogg Opus, Ogg Speex and Ogg Vorbis files (Ogg Vorbis tag),
-MP4/M4A/AAC files (MPEG-4 Part 10 tag), and MusePack, Monkey's Audio files
-(APE tag);
+tag), MP4/M4A/AAC files (MPEG-4 Part 10 tag), and MusePack, Monkey's Audio
+files (APE tag);
   - Auto tagging: parse file and directory names using masks to automatically
 fill in tag fields;
   - Cover art support for all formats;
@@ -71,6 +70,10 @@ Description: GTK+ editor for audio file tags
   - A playlist generator window;
   - A file searching window;
   - Simple and explicit interface.
+ .
+ OGG support is currently disabled in this package because of a data corruption
+ bug. To edit tags in OGG files you may consider one of these packages: exfalso,
+ puddletag, kid3-qt, entagged.
 
 Package: easytag-nautilus
 Architecture: any


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

Bug#885647: QScintilla2 Transition Started

On Tue, 02 Jan 2018 22:59:51 -0500 Scott Kitterman  
wrote:
> Now that qscintilla2 2.10.2 is in unstable, your package no longer builds, 
so 
> I've just raised the bug to severity serious.  If you haven't already, 
please 
> let me know if you intend to upload, otherwise I'll NMU in the next few 
days.
> 
> Scott K

Not having heard back, in the interests of moving the transition forward 
expeditiously, I'm going to go ahead and prepare/upload the NMU shortly.

Scott K

Bug#885635: QScintilla2 Transition Started

On Tue, 02 Jan 2018 22:59:51 -0500 Scott Kitterman  
wrote:
> Now that qscintilla2 2.10.2 is in unstable, your package no longer builds, 
so 
> I've just raised the bug to severity serious.  If you haven't already, 
please 
> let me know if you intend to upload, otherwise I'll NMU in the next few 
days.
> 
> Scott K

In the interests of moving the transition along, not having heard back, I'm 
preparing an NMU and plan to upload shortly.

Scott K

Bug#884406: marked as done (golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer)

Your message dated Thu, 04 Jan 2018 12:04:26 +
with message-id 
and subject line Bug#884406: fixed in golang-google-cloud 0.9.0-3
has caused the Debian Bug report #884406,
regarding golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does 
not implement spanner.SpannerServer
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.)


-- 
884406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-google-cloud
Version: 0.9.0-2
Severity: serious

https://ci.debian.net/packages/g/golang-google-cloud/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-google-cloud.html

...
# cloud.google.com/go/spanner/internal/testutil
src/cloud.google.com/go/spanner/internal/testutil/mockserver.go:238:30: cannot 
use m (type *MockCloudSpanner) as type spanner.SpannerServer in argument to 
spanner.RegisterSpannerServer:
*MockCloudSpanner does not implement spanner.SpannerServer (missing 
ListSessions method)
...
make[1]: *** [override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: golang-google-cloud
Source-Version: 0.9.0-3

We believe that the bug you reported is fixed in the latest version of
golang-google-cloud, 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.
Martín Ferrari  (supplier of updated golang-google-cloud 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Jan 2018 11:49:56 +
Source: golang-google-cloud
Binary: golang-google-cloud-dev golang-google-cloud-compute-metadata-dev
Architecture: source
Version: 0.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only 
cloud/compute/metadata)
 golang-google-cloud-dev - Google Cloud Platform APIs
Closes: 884406
Changes:
 golang-google-cloud (0.9.0-3) unstable; urgency=medium
 .
   * Stop using pristine-tar.
   * Backport fix to protobuf changes in golang-google-genproto-dev.
 Closes: 884406.
Checksums-Sha1:
 89570fab7903099d4736dd8dbf1c580a58fdd0c3 2709 golang-google-cloud_0.9.0-3.dsc
 e69b1a00c968604541f106b206efb4e225f89415 6388 
golang-google-cloud_0.9.0-3.debian.tar.xz
 adf1e73d20b8cb2cc7a51ad426fcae3d4462bcac 6953 
golang-google-cloud_0.9.0-3_amd64.buildinfo
Checksums-Sha256:
 ea2998357299a1fb6ee74c467962f6ea6ae8cb8ecb8da29cc0b2f847fc2165af 2709 
golang-google-cloud_0.9.0-3.dsc
 d620b41ff293861c2146d2617e5e99469d07b09763e680bfcf689fce833d7315 6388 
golang-google-cloud_0.9.0-3.debian.tar.xz
 7f6720bb3efe794ec567837343d3e995844923fb55b74064854c6bf06fce3b30 6953 
golang-google-cloud_0.9.0-3_amd64.buildinfo
Files:
 2bf8a969e94eb3e3ed5471bbfb51f59d 2709 devel optional 
golang-google-cloud_0.9.0-3.dsc
 c7ddd470ee8f46c9bbf2683abb006c18 6388 devel optional 
golang-google-cloud_0.9.0-3.debian.tar.xz
 a55fec2d0ea5b8c5040a8763cf32d245 6953 devel optional 
golang-google-cloud_0.9.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlpOFXkACgkQXdjgv5Gj
09o6MA//eEs8nvV5piu8Jaxz900pHyVwGX2LSK1cXIWlKIQpiEdpes3RI3R4J8r/
uZGj+qmJkP+Rj6rRJmRbgeqPn4HHNUwSrmMBTaxJ4JBq6WU9YkToUnLTd2Lyx58v
88M6iBmuz+/Nc+Jff/ceMKkLTg3uApanacMFF03ATEyWLiY48AF14lXnvHnF6fmf
R7/c/imSoy3Dm+cm2Mwpcn1FO37JgUOGQ5oLFNb9PGbkpdkGVDTOILRE2GzW4cu9
15wCVMHtApODewErgRTFUG2pPyyNQohNCod8KGhcRECocCSquJYrwwSSphzY0BNf
3jOarnHpDE5/9usK4+BWeptKSB1nVRIts3XA3EBQ38cRxbNOQUwx/T3IZKusYdtk
2QHIwhF8+8x+c1GcHbJHFSQyTMuVi4kEGhEN35f6IS/ika135S8rx0oabTExsZSb
uTA/uR4GUa2Ipqkb4xf5v3oYmhtp8AtN8DnN6UzoYaG1cwVbtPBPo2gAXfVuE9TV
9xvW85bPmBL1JQJuWPuDeyzaoS7lFimFDLH1Q37eZ1Olw0brAEk228svFt2JR7Ly
vfbDqCMAntJaGP31hAoFqJ1yNAPrZYO9TtTvnvauu7epUtB+NIhzcobEKJP9JHSo
Kd4Y87vhYoioJjTHSWGFd/TZ4//JnzYY3WbVP3CEhZFgslkMzh8=
=6zso
-END PGP SIGNATURE End Message ---

Bug#885626: QScintilla2 Transition Started

On Tue, 02 Jan 2018 22:59:51 -0500 Scott Kitterman  
wrote:
> Now that qscintilla2 2.10.2 is in unstable, your package no longer builds, 
so 
> I've just raised the bug to severity serious.  If you haven't already, 
please 
> let me know if you intend to upload, otherwise I'll NMU in the next few 
days.
> 
> Scott K

Not having heard back, I'm preparing an NMU and will upload shortly.

Scott K

Bug#884406: [pkg-go] Bug#884406: golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer

2018-01-04 Thread Martín Ferrari

It seems that updating to v0.16.0 fixes this issue but that pulls new
dependencies, so I am just going to backport the fix for this.

On 04/01/18 11:49, Martín Ferrari wrote:
> On 14/12/17 22:48, Adrian Bunk wrote:
> 
>> # cloud.google.com/go/spanner/internal/testutil
>> src/cloud.google.com/go/spanner/internal/testutil/mockserver.go:238:30: 
>> cannot use m (type *MockCloudSpanner) as type spanner.SpannerServer in 
>> argument to spanner.RegisterSpannerServer:
>>  *MockCloudSpanner does not implement spanner.SpannerServer (missing 
>> ListSessions method)
>> ...
> 
> It seems the latest upload to golang-google-genproto broke the API. Will
> have to investigate...
> 
> 


-- 
Martín Ferrari (Tincho)

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

2018-01-04 Thread Chris Boot

On 30/12/17 23:24, Chris Boot wrote:
> What makes me suspicious that these are related is that neither happens
> with a 4.13 kernel, but I get both of these cgroup-related problems with
> 4.14.
> 
> I wouldn't mind trying to bisect this, but I haven't done that for many
> years. Is there a nice way to do this with the Debian packaging or am I
> better off seeing if I can reproduce with vanilla upstream kernels and
> bisecting that? Or shall I give 4.15~rc5 from experimental a whirl instead?

I tried with linux-image-4.15.0-rc5-amd64_4.15~rc5-1~exp1 and my cgroup
issues no longer happen, so I think this is likely fixed in 4.15.

Unfortunately I'm now running into a KVM instability that feels like
#885166, so I'm going to go back to 4.13 shortly.

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org

GPG: 8467 53CB 1921 3142 C56D  C918 F5C8 3C05 D9CE

Bug#884406: [pkg-go] Bug#884406: golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer

2018-01-04 Thread Martín Ferrari

On 14/12/17 22:48, Adrian Bunk wrote:

> # cloud.google.com/go/spanner/internal/testutil
> src/cloud.google.com/go/spanner/internal/testutil/mockserver.go:238:30: 
> cannot use m (type *MockCloudSpanner) as type spanner.SpannerServer in 
> argument to spanner.RegisterSpannerServer:
>   *MockCloudSpanner does not implement spanner.SpannerServer (missing 
> ListSessions method)
> ...

It seems the latest upload to golang-google-genproto broke the API. Will
have to investigate...


-- 
Martín Ferrari (Tincho)

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

2018-01-04 Thread 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 that case, could you consider requesting those two packages be
> removed instead of orphaning them?

Sure. For reference:
https://groups.yahoo.com/neo/groups/gallery3/conversations/messages/555

Pietro

Processed: tagging 886224