Processed: Bug pending

[Debian Bug Tracking System]

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

> tags 882125 pending
Bug #882125 [pidgin-sipe] incompatible with pidgin apparmor profile
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882085: [cowsay] Package includes ASCII representation of Zoophilia

[Tehnic]

Hi,

here are my 2¢:

> Hi,
> you tested it? And you read and understand the description of cowsay-
off
> carefully?
> 
> Explicit: the sheep is not part of the cowsay package - it is part of
> cowsay-off which is described as:

> Ok, it is a little bit tasteless - but no one is forced to install
this
> package.

Unfortunatly cowsay-off is a recommended package of cowsay, this is
definitely questionable (i would consider it to be a bug)!

About the legal issues:

There are countries in which the possession of certain content is
enough to be sentenced, in particular for example child pornography but
also zoophilia. No distribution or "usage" is required.

My suggestion:

Make cowsay-off only suggested and ask for confirmation on install.

Bug#882206: nheko builds with -march=native

[Adrian Bunk]

Source: nheko
Version: 0.0+git20171116.21fdb26-1
Severity: serious

FTBFS on ppc64el:

https://buildd.debian.org/status/fetch.php?pkg=nheko&arch=ppc64el&ver=0.0%2Bgit20171116.21fdb26-1&stamp=1511151504&raw=0

...
c++: error: unrecognized command line option '-march=native'; did you mean 
'-mcpu=native'?


It builds on other architectures but having the program working
only on machines compatible with the build machine is not acceptable.

Please ensure that -march=native is not used.

Bug#882085: [cowsay] Package includes ASCII representation of Zoophilia

[Dominik George]

> In fact, the package was installed since I have turned on install
> suggests. If this was done on purpose or accident is not open for debate.

It is. I'm sorry, but in fact, your concern should be that you are obviously 
unable to control what you install on your system. You can read a handbook on 
this topic - but please leave unrelated maintainers alone - they are not the 
support crew for your personal system's administration.

The fix is to purge the package and look and think next time you install 
packages.

-nik

Bug#882125: marked as done (incompatible with pidgin apparmor profile)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 09:04:55 +
with message-id 
and subject line Bug#882125: fixed in pidgin-sipe 1.23.0-2
has caused the Debian Bug report #882125,
regarding incompatible with pidgin apparmor profile
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

AppArmor is now enabled by default in Debian and pidgin comes with an
AppArmor profile. When pidgin-sipe is installed, we get this error:

/usr/bin/pidgin: line 7: /etc/default/pidgin-sipe: Permission denied
/usr/bin/pidgin: line 10: /usr/bin/pidgin.orig: Permission denied

And the following audit trace:

[24779.428556] audit: type=1400 audit(1511089685.134:32848): apparmor="DENIED" 
operation="open" profile="/usr/bin/pidgin" name="/dev/tty" pid=18727 
comm="pidgin" requested_mask="wr" denied_mask="wr" fsuid=500 ouid=0
[24779.428637] audit: type=1400 audit(1511089685.134:32849): apparmor="DENIED" 
operation="open" profile="/usr/bin/pidgin" name="/dev/pts/1" pid=18727 
comm="pidgin" requested_mask="wr" denied_mask="wr" fsuid=500 ouid=500
[24779.429361] audit: type=1400 audit(1511089685.135:32850): apparmor="DENIED" 
operation="open" profile="/usr/bin/pidgin" name="/etc/default/pidgin-sipe" 
pid=18727 comm="pidgin" requested_mask="r" denied_mask="r" fsuid=500 ouid=0
[24779.429583] audit: type=1400 audit(1511089685.135:32851): apparmor="DENIED" 
operation="exec" profile="/usr/bin/pidgin" name="/usr/bin/pidgin.orig" 
pid=18728 comm="pidgin" requested_mask="x" denied_mask="x" fsuid=500 ouid=0
[24779.429586] audit: type=1400 audit(1511089685.135:32852): apparmor="DENIED" 
operation="open" profile="/usr/bin/pidgin" name="/usr/bin/pidgin.orig" 
pid=18728 comm="pidgin" requested_mask="r" denied_mask="r" fsuid=500 ouid=0


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

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

Versions of packages pidgin-sipe depends on:
ii  libc6   2.25-1
ii  libcomerr2  1.43.7-1
ii  libdbus-1-3 1.12.2-1
ii  libfarstream-0.2-5  0.2.8-2
ii  libglib2.0-02.54.2-1
ii  libgssapi-krb5-21.15.2-2
ii  libgstreamer-plugins-base1.0-0  1.12.3-1
ii  libgstreamer1.0-0   1.12.3-1
ii  libk5crypto31.15.2-2
ii  libkrb5-3   1.15.2-2
ii  libnice10   0.1.14-1
ii  libnspr42:4.16-1
ii  libnss3 2:3.34-1
ii  libpurple0  2.12.0-1+b1
ii  libxml2 2.9.4+dfsg1-5.1

Versions of packages pidgin-sipe recommends:
ii  gstreamer1.0-libav  1.12.3-1
ii  gstreamer1.0-x  1.12.3-1
ii  remmina-plugin-rdp  1.2.0-rcgit.24-3

pidgin-sipe suggests no packages.

- -- Configuration Files:
/etc/default/pidgin-sipe changed:
export NSS_SSL_CBC_RANDOM_IV=0


- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAloRZjcSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX505wQAIkEk+vD1JooOFNdVhcTeNiXd0PxszOT
EFYdV/hrcU1iGkY9Az+PGu9aDwRRknoeAR2XXiE4PsEjz+KE4M/xbFAZmHETJbna
eNW7HT9yZXI2EUb8lyrB96VPO1uT56973BEvw9u7wV+gH74ROe417XMflV/iUw54
NrIsbr04piJiALOipmjTv/vBhNSlQtI7Yz/Xx8PA/IdJiIglYS3WVPWItAL5EZrT
mVmk8srhejNw2zwlnzUXFTJh1um2iSMDRMDGtRSsQT+nXNYRvWzcBOdkfyR/v5rg
/dzrE3kTLNOgk5zFEaoAfj8lzpegvevuiHBgGkNgnXa6D+Vlf8CK9KE280wai7ah
SzyJ6P+i5GJWbhP6ffE4aAGZXmZHX2susd/2ut74yPU83MRcsKgdqlyp8XlZRxmc
WdPGJxbzAQqT1ExoY4W+WVRGTBIMfoAQQYdr8pw+OnEF8IMx1BX/Voxe9qVssfmv
SRhHmvxMk9qr6HIsU3TqLnQLwuLN1Vte1RRgqALPphdwZCUOh4nClCBilctyLt9y
K0k5DRrw+90gHa9I37INdUpPrYmP63oE9g+APZOgWKyfzWzTumtLfE9upuDf4MzS
YvjMM7b/ynl28MjwSJP8T8ZfDRJddjP/SCeMsBRZCeDK1YPmT60TEQs/9o6TJS8l
zqKzbwbMQFiy
=ipen
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: pidgin-sipe
Source-Version: 1.23.0-2

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

A summary of the chan

Bug#882085: [cowsay] Package includes ASCII representation of Zoophilia

[Felicia Hummel]

> Make cowsay-off only suggested and ask for confirmation on install.

I believe this is a reasonable course of action. I also have to
apologize: I was under the impression that the Zoophilia representation
was in cowsay, when in reality it was in cowsay-off.

All the best
Felicia

Bug#877206: new release is available, should fix this

[Brian Warner]

I just released foolscap-0.13.0, which ought to fix this.. let me know
if you see any problems, or if I can help with getting it into
debian/ubuntu before the package gets removed. Thanks!

Bug#828483: Moving

[Hilko Bengen]

Hi,

This message by Stephen Henson looks like it might be the way to deal
with the STACK_OF(ASN1_OCTET_STRING) and
STACK_OF(SpcAttributeTypeAndOptionalValue) types.

https://mta.openssl.org/pipermail/openssl-users/2016-September/004442.html

Meanwhile, here's a patch for the easy bits:

- Dealing with renamed types
- Allocating opaque structures on the heap.

Cheers,
-Hilko
>From 1fe4ce60fadf202299d4c7e86f380c3bf9051cef Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sun, 19 Nov 2017 15:35:04 +0100
Subject: [PATCH] Easy fixes toward OpenSSL 1.1 compatibility

- Rename M_ASN1_* -> ASN1_*
- Allocate EVP_MD_CTX has become opaque, so it needs to be allocated
  on the heap.
---
 osslsigncode.c | 90 +-
 1 file changed, 52 insertions(+), 38 deletions(-)

diff --git a/osslsigncode.c b/osslsigncode.c
index 32e37c8..aea2109 100644
--- a/osslsigncode.c
+++ b/osslsigncode.c
@@ -450,7 +450,7 @@ static SpcSpOpusInfo* createOpus(const char *desc, const char *url)
 	if (desc) {
 		info->programName = SpcString_new();
 		info->programName->type = 1;
-		info->programName->value.ascii = M_ASN1_IA5STRING_new();
+		info->programName->value.ascii = ASN1_IA5STRING_new();
 		ASN1_STRING_set((ASN1_STRING *)info->programName->value.ascii,
 		(const unsigned char*)desc, strlen(desc));
 	}
@@ -458,7 +458,7 @@ static SpcSpOpusInfo* createOpus(const char *desc, const char *url)
 	if (url) {
 		info->moreInfo = SpcLink_new();
 		info->moreInfo->type = 0;
-		info->moreInfo->value.url = M_ASN1_IA5STRING_new();
+		info->moreInfo->value.url = ASN1_IA5STRING_new();
 		ASN1_STRING_set((ASN1_STRING *)info->moreInfo->value.url,
 		(const unsigned char*)url, strlen(url));
 	}
@@ -609,19 +609,20 @@ static int add_timestamp(PKCS7 *sig, char *url, char *proxy, int rfc3161, const
 
 	if (rfc3161) {
 		unsigned char mdbuf[EVP_MAX_MD_SIZE];
-		EVP_MD_CTX mdctx;
+		EVP_MD_CTX* mdctx = EVP_MD_CTX_create();
 
-		EVP_MD_CTX_init(&mdctx);
-		EVP_DigestInit(&mdctx, md);
-		EVP_DigestUpdate(&mdctx, si->enc_digest->data, si->enc_digest->length);
-		EVP_DigestFinal(&mdctx, mdbuf, NULL);
+		EVP_DigestInit(mdctx, md);
+		EVP_DigestUpdate(mdctx, si->enc_digest->data, si->enc_digest->length);
+		EVP_DigestFinal(mdctx, mdbuf, NULL);
+
+		EVP_MD_CTX_destroy(mdctx);
 
 		TimeStampReq *req = TimeStampReq_new();
 		ASN1_INTEGER_set(req->version, 1);
 		req->messageImprint->digestAlgorithm->algorithm = OBJ_nid2obj(EVP_MD_nid(md));
 		req->messageImprint->digestAlgorithm->parameters = ASN1_TYPE_new();
 		req->messageImprint->digestAlgorithm->parameters->type = V_ASN1_NULL;
-		M_ASN1_OCTET_STRING_set(req->messageImprint->digest, mdbuf, EVP_MD_size(md));
+		ASN1_OCTET_STRING_set(req->messageImprint->digest, mdbuf, EVP_MD_size(md));
 		req->certReq = (void*)0x1;
 
 		len = i2d_TimeStampReq(req, NULL);
@@ -924,6 +925,7 @@ static const unsigned char classid_page_hash[] = {
 static unsigned char *calc_page_hash(char *indata, unsigned int peheader, int pe32plus,
 	 unsigned int sigpos, int phtype, unsigned int *phlen);
 
+#if OPENSSL_VERSION_NUMBER < 0x1010
 DECLARE_STACK_OF(ASN1_OCTET_STRING)
 #ifndef sk_ASN1_OCTET_STRING_new_null
 #define sk_ASN1_OCTET_STRING_new_null() SKM_sk_new_null(ASN1_OCTET_STRING)
@@ -931,15 +933,26 @@ DECLARE_STACK_OF(ASN1_OCTET_STRING)
 #define sk_ASN1_OCTET_STRING_push(st, val) SKM_sk_push(ASN1_OCTET_STRING, (st), (val))
 #define i2d_ASN1_SET_OF_ASN1_OCTET_STRING(st, pp, i2d_func, ex_tag, ex_class, is_set) \
 	SKM_ASN1_SET_OF_i2d(ASN1_OCTET_STRING, (st), (pp), (i2d_func), (ex_tag), (ex_class), (is_set))
+#else
+DEFINE_STACK_OF(ASN1_OCTET_STRING)
+#define i2d_sk_ASN1_SET_OF_ASN1_OCTET_STRING(st, pp, i2d_func, ex_tag, ex_class, is_set) \
+	ASN1_SET_OF_i2d(ASN1_OCTET_STRING, (st), (pp), (i2d_func), (ex_tag), (ex_class), (is_set))
+#endif
 #endif
 
+#if OPENSSL_VERSION_NUMBER < 0x1010
 DECLARE_STACK_OF(SpcAttributeTypeAndOptionalValue)
 #ifndef sk_SpcAttributeTypeAndOptionalValue_new_null
 #define sk_SpcAttributeTypeAndOptionalValue_new_null() SKM_sk_new_null(SpcAttributeTypeAndOptionalValue)
 #define sk_SpcAttributeTypeAndOptionalValue_free(st) SKM_sk_free(SpcAttributeTypeAndOptionalValue, (st))
 #define sk_SpcAttributeTypeAndOptionalValue_push(st, val) SKM_sk_push(SpcAttributeTypeAndOptionalValue, (st), (val))
-#define i2d_SpcAttributeTypeAndOptionalValue(st, pp, i2d_func, ex_tag, ex_class, is_set) \
+#define i2d_sk_SpcAttributeTypeAndOptionalValue(st, pp, i2d_func, ex_tag, ex_class, is_set) \
 	SKM_ASN1_SET_OF_i2d(SpcAttributeTypeAndOptionalValue, (st), (pp), (i2d_func), (ex_tag), (ex_class), (is_set))
+#else
+DEFINE_STACK_OF(SpcAttributeTypeAndOptionalValue)
+#define i2d_sk_SpcAttributeTypeAndOptionalValue(st, pp, i2d_func, ex_tag, ex_class, is_set) \
+	ASN1_SET_OF_i2d(SpcAttributeTypeAndOptionalValue, (st), (pp), (i2d_func), (ex_tag), (ex_class), (is_set))
+#endif
 #endif
 
 static SpcLink *get_page_hash_link(int phtype, char *indata, unsigned int peheader, int pe32

Bug#867994: marked as done (libllvm-ocaml-dev: unhandled symlink to directory conversion: /usr/lib/ocaml/llvm)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 10:21:46 +0100
with message-id <1ee5a4bb-1d0f-0782-8d1b-90166c7ad...@debian.org>
and subject line 
has caused the Debian Bug report #867994,
regarding libllvm-ocaml-dev: unhandled symlink to directory conversion: 
/usr/lib/ocaml/llvm
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.)


-- 
867994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libllvm-ocaml-dev
Version: 1:4.0-37~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  sid -> experimental

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

1m5.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/lib/ocaml/llvm/libllvm.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_AArch64.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_AArch64.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_AMDGPU.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_AMDGPU.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_ARM.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_ARM.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_BPF.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_BPF.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_Hexagon.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_Hexagon.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
[...]
  /usr/lib/ocaml/llvm/llvm_vectorize.cma (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cma (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.cmi (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cmi (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.cmx (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cmx (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.cmxa (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cmxa (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.mli (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.mli (?)
/usr/lib/ocaml/llvm -> llvm-3.8


cheers,

Andreas


libllvm-ocaml-dev_1:4.0-37~exp2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
fixed 867994 0.38~exp1
thanks--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 867994 0.38~exp1
Bug #867994 [libllvm-ocaml-dev] libllvm-ocaml-dev: unhandled symlink to 
directory conversion: /usr/lib/ocaml/llvm
There is no source info for the package 'libllvm-ocaml-dev' at version 
'0.38~exp1' with architecture ''
Unable to make a source version for version '0.38~exp1'
Marked as fixed in versions 0.38~exp1.
> thanks
Stopping processing here.

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

Bug#882085: [cowsay] Package includes ASCII representation of Zoophilia

[Sebastian Elisa Pfeifer]

Morning!

> There are countries in which the possession of certain content is
> enough to be sentenced, in particular for example child pornography but
> also zoophilia. No distribution or "usage" is required.

Debian Mirror Operator here. This could bring some legal problems for
some of us, since we do not only possess it, but also distribute the
package.. I know this is highly theoretical, but only because law
enforcement in most countries probably don't know about Debian (<-- as a
figure of speech of course).

All the best
Sebastian

-- 
Sebastian Elisa Pfeifer

Cyber Perikarp - Verein z. Förderung d. Netzkultur
Wassertalweg 56   |   8670 Krieglach   |   AUSTRIA

Vereinsregisternummer:   712531114
Datenverarbeitungsregister:4016968
PGP Key ID: 0x923719A753677B95
EU-Transparenz-Registernummer: 334990728439-25
D-U-N-S® Nummer: 300530810

Phone: +43 3855 289 10
Fax:  +43 3855 289 10 - 10
Mobile: +43 677 623 144 11
Jabber:  deadd...@fsfe.org



signature.asc
Description: OpenPGP digital signature

Bug#881710: marked as pending

[Jonathan Carter]

tag 881710 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/pythonqt.git/commit/?id=157d23d

---
commit 157d23d293d32a9ebc469836be9752893847eac3
Author: Jonathan Carter 
Date:   Mon Nov 20 04:28:56 2017 -0500

Merge bug fixes from Erik Lunde

diff --git a/debian/changelog b/debian/changelog
index c1df5a3..7e9716d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+pythonqt (3.2-4~exp5) experimental; urgency=medium
+
+  * Add Erik Lunde's patch to fix builds on ppc64
+(Closes: #881685)
+  * Add Erik Lunde's patch to fix files shipped in multiple binaries
+(Closes: #881710)
+
+ -- Jonathan Carter   Mon, 20 Nov 2017 10:21:26 +0200
+
 pythonqt (3.2-4~exp4) experimental; urgency=medium
 
   * Fix generator Qt include dir for multiarch

Processed: Bug#881710 marked as pending

[Debian Bug Tracking System]

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

> tag 881710 pending
Bug #881710 [libpythonqt-qt5-common-dev,libpythonqt-qtall-qt5-common-dev] 
libpythonqt-qt5-common-dev,libpythonqt-qtall-qt5-common-dev: both ship 
/usr/include/PythonQt5/moc_predefs.h
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#878216: Bug relating linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm

[Cristiano Casella]

Hi,

thanks for your support.

Can you provide me the different packages to test?


Cordiali Saluti / Best Regards

Cristiano Casella

---

Register.it S.p.A.



Da: Julien Cristau 
Inviato: domenica 19 novembre 2017 15:56
A: Cristiano Casella; 878...@bugs.debian.org
Oggetto: Re: Bug#878216: Bug relating 
linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm

Hi,

On Wed, Oct 11, 2017 at 08:45:14 +, Cristiano Casella wrote:

> Upgrading our vm with Debian 8 (also just installed) to last version of 
> linux-image package (linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb) the 
> virtual machines can't boot anymore.
>
>
> I attached to this email the two kind of error that we can get in the console.
>
>
> Looking at the changelog 
> (https://tracker.debian.org/media/packages/l/linux/changelog-3.16.48-1) I 
> suspect that this changes could be involved in this bug:
tracker.debian.org
tracker.debian.org
linux (3.16.48-1) jessie; urgency=medium * New upstream stable update: 
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.16.44 - [x86] 
drm/i915: relax ...



>
>
> - [x86] scsi: storvsc: use tagged SRB requests if supported by the device
> - [x86] scsi: storvsc: Fix a bug in the handling of SRB status flags
> - [x86] scsi: storvsc: properly handle SRB_ERROR when sense message is
>   present
> - [x86] scsi: storvsc: properly set residual data length on errors
>
> We can provide you all test environments needed or proceede with your support 
> for a kernel bisect to find the specific error.
>
If you could bisect between 3.16.43 and 3.16.48, that would be most
helpful.

Thanks,
Julien

Bug#882085: [cowsay] Package includes ASCII representation of Zoophilia

[Richard Wiedenhöft]

> Look and think next time you install packages

A name like "cowsay-off" doesn't imply it contains obscene content. Executing 
apt-cache show on all packages you install is impractical.

I suggest
* Changing the name of the package to "cowsay-obscene"
* Removing it from suggested packages for cowsay

~Richard

Bug#882085: [cowsay] Package includes ASCII representation of Zoophilia

[Felicia Hummel]

> Debian Mirror Operator here. This could bring some legal problems for
> some of us, since we do not only possess it, but also distribute the
> package.. I know this is highly theoretical, but only because law
> enforcement in most countries probably don't know about Debian (<-- as a
> figure of speech of course).

I agree. Whilst the content of the file in question is debatable, the
file name itself is not. In fact, "sodomized-sheep.cow" leaves no bug
room for interpretation of the ASCII representation itself.

A note to all those who try to troll me or the bug report because they
read about it on fefe: It was created to protect unknowingly of legal
actions, especially mirror operators or those who have install suggests
and recommends on.

If you find that "You're wasting the time of the maintainers", please
refer to the Debian Code of Conduct [1], which includes, but is not
limited to, those sections:

- Be respectful
- Assume good faith
- Be open

All the best
Felicia

[1] https://www.debian.org/code_of_conduct

Bug#882085: [cowsay] Package includes ASCII representation of Zoophilia

[Johannes Schriewer]

On Mon, 20 Nov 2017 09:54:34 +0100 Dominik George wrote:
> > In fact, the package was installed since I have turned on install
> > suggests. If this was done on purpose or accident is not open for debate.
> 
> It is. I'm sorry, but in fact, your concern should be that you are obviously 
> unable to control what you install on your system. You can read a handbook on 
> this topic - but please leave unrelated maintainers alone - they are not the 
> support crew for your personal system's administration.

So what about mirrors in countries, where this is illegal (like germany), that 
get all packages automatically? Is there a way to exclude this illegal package? 
Wouldn’t it be easier to just remove that file and be done with it?

> The fix is to purge the package and look and think next time you install 
> packages.

Will you inform the mirrors in countries that this is illegal?

> 
> -nik

Processed (with 1 error): fix severity and bug title

[Debian Bug Tracking System]

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

> severity 882085 wishlist
Bug #882085 [cowsay] [cowsay] Package includes ASCII representation of Zoophilia
Severity set to 'wishlist' from 'critical'
> title 882085 cowsay: should not recommend cowsay-off
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 880829 1.7.1-7
Bug #880829 [src:plexus-containers] plexus-containers FTBFS: 
ComponentDescriptor.java:[192,44] incompatible types: java.lang.Class cannot be converted to java.lang.Class
Marked as fixed in versions plexus-containers/1.7.1-7.
> close 880829
Bug #880829 [src:plexus-containers] plexus-containers FTBFS: 
ComponentDescriptor.java:[192,44] incompatible types: java.lang.Class cannot be converted to java.lang.Class
Marked Bug as done
>
End of message, stopping processing here.

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

Processed: Re: Bug#882204: bs1770gain: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #882204 [bs1770gain] bs1770gain: FTBFS
Severity set to 'serious' from 'important'
> tags -1 moreinfo
Bug #882204 [bs1770gain] bs1770gain: FTBFS
Added tag(s) moreinfo.
> block 882200 by -1
Bug #882200 [release.debian.org] transition: sox
882200 was not blocked by any bugs.
882200 was not blocking any bugs.
Added blocking bug(s) of 882200: 882204

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

Bug#882215: gupnp: FTBFS on mips* - sends packets to multicast address

[James Cowgill]

Source: gupnp
Version: 1.0.2-1
Severity: serious
Tags: sid buster

Hi,

gupnp FTBFS on mips64el and mipsel with the error:
> FAIL: test-bugs
> ===
> 
> /bugs/696762: 
> ** (/<>/tests/gtest/.libs/test-bugs:26885): WARNING **: Error 
> sending SSDP packet to 239.255.255.250: Error sending message: Operation not 
> permitted
> FAIL test-bugs (exit status: 133)

This happens because sending packets to a multicast address is
blacklisted from all servers in AQL because suspicious multicast packets
trip AQL's protection systems and takes all the Debian servers in AQL
offline.

These tests also likely violate policy 4.9:
"For packages in the main archive, no required targets may attempt
network access."

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#882216: gssdp: FTBFS on mips* - sends packets to multicast address

[James Cowgill]

Source: gssdp
Version: 1.0.2-1
Severity: serious
Tags: sid buster

Hi,

gupnp FTBFS on mips* with the error:
> FAIL: test-bugs
> ===
> 
> /bugs/696762: 
> ** (/<>/tests/gtest/.libs/test-bugs:26885): WARNING **: Error 
> sending SSDP packet to 239.255.255.250: Error sending message: Operation not 
> permitted
> FAIL test-bugs (exit status: 133)

This is the same issue as in #882215. I will quote what I wrote there
for reference:

> This happens because sending packets to a multicast address is
> blacklisted from all servers in AQL because suspicious multicast packets
> trip AQL's protection systems and takes all the Debian servers in AQL
> offline.
> 
> These tests also likely violate policy 4.9:
> "For packages in the main archive, no required targets may attempt
> network access."

Thanks,
James





signature.asc
Description: OpenPGP digital signature

Processed: Bug#868955 marked as pending

[Debian Bug Tracking System]

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

> tag 868955 pending
Bug #868955 [redmine] redmine: buster - broken install, package cannot be 
removed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#868955: marked as pending

[Duck]

tag 868955 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/pkg-ruby-extras/redmine.git/commit/?id=854a82f

---
commit 854a82fd70901defe33f8655dc656352b93bdd1b
Author: Marc Dequènes (Duck) 
Date:   Mon Nov 20 20:08:48 2017 +0900

Do not fail is manual database installation is selected

diff --git a/debian/changelog b/debian/changelog
index cf56df1..93948a7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -16,6 +16,8 @@ redmine (3.4.2-1) UNRELEASED; urgency=medium
   * Pass instance list to postrm to ensure removal works when things are
 broken (found in #868955).
   * Support dbconfig-no-thanks.
+  * Do not fail is manual database installation is selected (Closes:
+#868955).
 
   [ Lucas Kanashiro ]
   * debian/copyright: fix path of redcloth3.rb file

Bug#882222: Document security problems with system.3 and popen.3 (argument injection)

[Bastien ROUCARIES]

Package: manpages-dev
Version: 4.13-3
Severity: grave
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
Justification: more than 20 security bugs filled in other package
control: clone -1 -2
control: reaffect -2 glibc-doc


Please document the implication of system.3 and popen.3, particularly
argument injection.

Please get inspiration from ENV33-C. Do not call system()

Sugest to use execvp and please provide example of secure alternative
for both API

Note that escaping argument is not portable particularly if argument
include control char for a POSIX shell.

https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152177



Use of the system() function can result in exploitable
vulnerabilities, in the worst case allowing execution of arbitrary
system commands. Situations in which calls to system() have high risk
include the following:

When passing an unsanitized or improperly sanitized command string
originating from a tainted source
If a command is specified without a path name and the command
processor path name resolution mechanism is accessible to an attacker
If a relative path to an executable is specified and control over the
current working directory is accessible to an attacker
If the specified executable program can be spoofed by an attacker

Processed (with 1 error): Document security problems with system.3 and popen.3 (argument injection)

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #88 [manpages-dev] Document security problems with system.3 and popen.3 
(argument injection)
Bug 88 cloned as bug 882223
> reaffect -2 glibc-doc
Unknown command or malformed arguments to command.


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

Bug#880235: marked as done (blockdiag: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 11:33:50 +
with message-id 
and subject line Bug#880235: fixed in blockdiag 1.5.3+dfsg-5.1
has caused the Debian Bug report #880235,
regarding blockdiag: FTBFS: dh_auto_test: pybuild --test --test-nose -i 
python{version} -p 2.7 returned exit code 13
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
> dh: Compatibility levels before 9 are deprecated (level 7 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in 
> use)
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.6 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> copying src/blockdiag_sphinxhelper.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build
> creating 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> copying src/blockdiag/metrics.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> copying src/blockdiag/command.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> copying src/blockdiag/elements.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> copying src/blockdiag/__init__.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> copying src/blockdiag/drawer.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> copying src/blockdiag/parser.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> copying src/blockdiag/builder.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag
> creating 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/plugins
> copying src/blockdiag/plugins/autoclass.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/plugins
> copying src/blockdiag/plugins/attributes.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/plugins
> copying src/blockdiag/plugins/__init__.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/plugins
> creating 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/config.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/myitertools.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/logging.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/fontmap.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/uuid.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/images.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/compat.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/__init__.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/urlutil.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> copying src/blockdiag/utils/bootstrap.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/utils
> creating 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/imagedraw
> copying src/blockdiag/imagedraw/textfolder.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/imagedraw
> copying src/blockdiag/imagedraw/simplesvg.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/imagedraw
> copying src/blockdiag/imagedraw/svg.py -> 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build/blockdiag/imagedraw
> copying src/blockdiag/imagedraw/__init__.py -> 
> /<>/block

Processed (with 1 error): forward #882075

[Debian Bug Tracking System]

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

> forward 882075 https://trac.ffmpeg.org/ticket/6848
Unknown command or malformed arguments to command.
> tags 882075 upstream
Bug #882075 [src:ffmpeg] ffmpeg: sometimes FTBFS on i386
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#880566: Sponsorship request

[Teus Benschop]

The newest packaging available from [1] fixes this bug.

I am asking for assistance with reviewing and uploading this packaging.

[1] https://anonscm.debian.org/gitweb/?p=pkg-crosswire/bibletime.git

Bug#882204: bs1770gain: FTBFS

[Jaromír Mikeš]

2017-11-20 11:15 GMT+01:00 James Cowgill :

> Control: severity -1 serious
> Control: tags -1 moreinfo
> Control: block 882200 by -1
>
> Hi,
>
>
> > your package fails to build with following error:
> > /missing: line 81: aclocal-1.14: command not found
> > WARNING: 'aclocal-1.14' is missing on your system.
> >  You should only need it if you modified 'acinclude.m4' or
> >  'configure.ac' or m4 files included by 'configure.ac'.
> >  The 'aclocal' program is part of the GNU Automake package:
> >  
> >  It also requires GNU Autoconf, GNU m4 and Perl in order to run:
> >  
> >  
> >  
> > Makefile:330: recipe for target 'aclocal.m4' failed
>
> I cannot reproduce this failure, although I notice the package doesn't
> use dh-autoreconf which would prevent a bug such as this. Maybe you
> touched some file which caused automake to try to regenerate everything?
> Do you have the full build log?


​I am build outside from chroot to test build with new libsox.
it builds fine inside of chroot with old libsox.

​Can you try please
$ dpkg-buildpackage -us -uc

with orig tar.ball obtained from here:
http://cdn-fastly.deb.debian.org/debian/pool/main/b/bs1770gain/bs1770gain_0.4.12.orig.tar.gz

best regards

mira

Bug#882204: bs1770gain: FTBFS

[James Cowgill]

Hi,

On 20/11/17 12:11, Jaromír Mikeš wrote:
> ​I am build outside from chroot to test build with new libsox.

You should be using sbuild or pbuilder for test builds.

> it builds fine inside of chroot with old libsox.
> 
> ​Can you try please
> $ dpkg-buildpackage -us -uc
> 
> with orig tar.ball obtained from here:
> http://cdn-fastly.deb.debian.org/debian/pool/main/b/bs1770gain/bs1770gain_0.4.12.orig.tar.gz

I did an "apt-get source bs1770gain" and built it outside of a chroot
and it still builds ok.

James



signature.asc
Description: OpenPGP digital signature

Bug#868955: marked as done (redmine: buster - broken install, package cannot be removed)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 12:19:13 +
with message-id 
and subject line Bug#868955: fixed in redmine 3.4.2-1
has caused the Debian Bug report #868955,
regarding redmine: buster - broken install, package cannot be removed
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.)


-- 
868955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redmine
Version: 3.3.1-4
Severity: grave
Justification: renders package unusable

Hello,

I tried installing redmine in buster.  It encountered a configuration error 
when a setup script 
returned a non-zero exit status.  I tried removing the package.  It cannot be 
removed because of an 
error in a cleanup script.

The only weird thing about my setup is that I have ruby-asana=0.4.0-1 installed 
from stretch, because 
of a bug that prevented me from installing Gitlab.

Below, I included the full transcript of my flailing attempts to make this work.

Thanks.  -Mark

==
weirdvibe:~# apt-get install redmine-sqlite redmine 
redmine-plugin-local-avatars redmine-plugin-pretend passenger-doc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  dbconfig-sqlite3 passenger ruby-actionpack-action-caching 
ruby-actionpack-xml-parser ruby-coderay
  ruby-hmac ruby-openid ruby-protected-attributes ruby-rack-openid 
ruby-rails-observers ruby-rbpdf
  ruby-rbpdf-font ruby-rmagick ruby-roadie ruby-roadie-rails
Suggested packages:
  bzr cvs darcs mercurial ruby-fcgi subversion
The following NEW packages will be installed:
  dbconfig-sqlite3 passenger passenger-doc redmine redmine-plugin-local-avatars 
redmine-plugin-pretend
  redmine-sqlite ruby-actionpack-action-caching ruby-actionpack-xml-parser 
ruby-coderay ruby-hmac
  ruby-openid ruby-protected-attributes ruby-rack-openid ruby-rails-observers 
ruby-rbpdf ruby-rbpdf-font
  ruby-rmagick ruby-roadie ruby-roadie-rails
0 upgraded, 20 newly installed, 0 to remove and 1 not upgraded.
Need to get 13.1 MB of archives.
After this operation, 32.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.us.debian.org/debian buster/main i386 dbconfig-sqlite3 all 
2.0.9 [954 B]
Get:2 http://ftp.us.debian.org/debian stretch/main i386 redmine-sqlite all 
3.3.1-4 [86.8 kB]
Get:3 http://ftp.us.debian.org/debian stretch/main i386 
ruby-actionpack-action-caching all 1.1.1-4 [8,606 B]
Get:4 http://ftp.us.debian.org/debian stretch/main i386 
ruby-actionpack-xml-parser all 1.0.2-2 [3,976 B]
Get:5 http://ftp.us.debian.org/debian stretch/main i386 ruby-coderay all 
1.1.1-1 [76.2 kB]
Get:6 http://ftp.us.debian.org/debian stretch/main i386 ruby-hmac all 0.4.0-5 
[7,188 B]
Get:7 http://ftp.us.debian.org/debian stretch/main i386 ruby-openid all 
2.7.0debian-1 [171 kB]
Get:8 http://ftp.us.debian.org/debian stretch/main i386 
ruby-protected-attributes all 1.1.3-2 [14.7 kB]
Get:9 http://ftp.us.debian.org/debian stretch/main i386 ruby-rack-openid all 
1.4.2-1 [7,122 B]
Get:10 http://ftp.us.debian.org/debian stretch/main i386 ruby-rails-observers 
all 0.1.2-1 [11.9 kB]
Get:11 http://ftp.us.debian.org/debian stretch/main i386 ruby-rbpdf-font all 
1.19.0-1 [8,627 kB]
Get:12 http://ftp.us.debian.org/debian stretch/main i386 ruby-rbpdf all 
1.19.0-1 [114 kB]
Get:13 http://ftp.us.debian.org/debian stretch/main i386 ruby-rmagick i386 
2.16.0-2+b1 [185 kB]
Get:14 http://ftp.us.debian.org/debian stretch/main i386 ruby-roadie all 
3.1.1-1 [30.4 kB]
Get:15 http://ftp.us.debian.org/debian stretch/main i386 ruby-roadie-rails all 
1.1.0-1 [11.4 kB]
Get:16 http://ftp.us.debian.org/debian stretch/main i386 redmine all 3.3.1-4 
[1,221 kB]
Get:17 http://ftp.us.debian.org/debian stretch/main i386 passenger i386 
5.0.30-1+b1 [1,386 kB]
Get:18 http://ftp.us.debian.org/debian stretch/main i386 passenger-doc all 
5.0.30-1 [1,081 kB]
Get:19 http://ftp.us.debian.org/debian stretch/main i386 
redmine-plugin-local-avatars all 1.0.1-1 [7,954 B]
Get:20 http://ftp.us.debian.org/debian stretch/main i386 redmine-plugin-pretend 
all 0.0.2+git20130821-4 [5,890 B]
Fetched 13.1 MB in 0s (23.7 MB/s) 
Preconfiguring packages ...
redmine failed to preconfigure, with exit status 10
Selecting previously unselected package dbconfig-sqlite3.
(Reading database ... 110590 files and directories currently installed.)
Preparing to unpack .../00-dbconfig-sqlite3_2.0.9_all.deb ...
Unpacking dbconfig-sqlite3 (2.0.9) ...
Selecting previously unselected pac

Processed: Re: Processed (with 1 error): forward #882075

[Debian Bug Tracking System]

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

> forwarded 882075 https://trac.ffmpeg.org/ticket/6848
Bug #882075 [src:ffmpeg] ffmpeg: sometimes FTBFS on i386
Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/6848'.
> thanks
Stopping processing here.

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

Bug#882223: Reassign

[Bastien ROUCARIES]

control: assign -1 glibc-doc

Bug#882103: python-pkg-resources: crashing with "ImportError: No module named load_entry_point"

[Marc]

Ok, I discovered a little more I thought was worth sharing.

I did an update just before I noticed the problem. There was a Kernel update 
and apparmor was installed to satisfy a recommended dependency.

I removed apparmor and problem goes away, and I installed apparmor again and 
the problem returns.

So for now I am up and running again, but in the future if apparmor becomes a 
strong dependency the problem will return.

Maybe obfsproxy needs it's own apparmor profile, or the python profile has a 
problem?

Regards

Marc

Bug#882204: bs1770gain: FTBFS

[Jaromír Mikeš]

2017-11-20 13:16 GMT+01:00 James Cowgill :

> Hi,
>
> On 20/11/17 12:11, Jaromír Mikeš wrote:
> > ​I am build outside from chroot to test build with new libsox.
>
> You should be using sbuild or pbuilder for test builds.
>
> > it builds fine inside of chroot with old libsox.
> >
> > ​Can you try please
> > $ dpkg-buildpackage -us -uc
> >
> > with orig tar.ball obtained from here:
> > http://cdn-fastly.deb.debian.org/debian/pool/main/b/
> bs1770gain/bs1770gain_0.4.12.orig.tar.gz
>
> I did an "apt-get source bs1770gain" and built it outside of a chroot
> and it still builds ok.


​Hmm interesting ... build fine your way ...

I am going close this bug

best regards

mira​

Processed: your mail

[Debian Bug Tracking System]

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

> close 882204
Bug #882204 [bs1770gain] bs1770gain: FTBFS
Marked Bug as done
> # closing this bug as it was caused by my wrong workflow
> thanks
Stopping processing here.

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

Bug#881876: astromenace: FTBFS on 32-bit arches: dh_install: astromenace missing files: astromenace_64.png

[James Cowgill]

Control: tags -1 moreinfo

Hi,

On 16/11/17 00:47, Andreas Beckmann wrote:
> Source: astromenace
> Version: 1.3.2+repack-4
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi,
> 
> astromenace FTBFS on 32-bit architectures (tried i386 and armhf) while
> it builds fine on amd64.
> 
>debian/rules override_dh_install
> make[1]: Entering directory '/build/astromenace-1.3.2+repack'
> dh_install --exclude=astromenace_64.png
> dh_install: astromenace missing files: astromenace_64.png
> dh_install: missing files, aborting
> debian/rules:28: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 25
> 
> This could be caused by a change in debhelper.

I can't reproduce this with debhelper 10.10.9. Could you try building it
again?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#881876: astromenace: FTBFS on 32-bit arches: dh_install: astromenace missing files: astromenace_64.png

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #881876 [src:astromenace] astromenace: FTBFS on 32-bit arches: dh_install: 
astromenace missing files: astromenace_64.png
Added tag(s) moreinfo.

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

Bug#877923: marked as done (conflicting types for 'FcObjectTypeHash')

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 13:48:59 +
with message-id 
and subject line Bug#869584: fixed in fontconfig 2.12.6-0.1
has caused the Debian Bug report #869584,
regarding conflicting types for 'FcObjectTypeHash'
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.)


-- 
869584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontconfig
Version: 2.12.3-0.2

Building with:
dpkg-buildpackage --no-sign --build=binary

leads to:
...
In file included from fcobjs.c:33:0:
fcobjshash.gperf:28:1: error: conflicting types for 'FcObjectTypeHash'
 "aspect",FC_ASPECT_OBJECT
 ^~~~
fcobjs.c:28:1: note: previous declaration of 'FcObjectTypeHash' was here
 FcObjectTypeHash (register const char *str, register FC_GPERF_SIZE_T len);
 ^~~~
In file included from fcobjs.c:33:0:
fcobjshash.gperf:172:1: error: conflicting types for 'FcObjectTypeLookup'
fcobjs.c:31:1: note: previous declaration of 'FcObjectTypeLookup' was here
 FcObjectTypeLookup (register const char *str, register FC_GPERF_SIZE_T
len);
 ^~
Makefile:638: recipe for target 'fcobjs.lo' failed

Full build log is attached.

-- 
Jean-Christophe


fontconfig.2.12.3-0.2_amd64.build
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.12.6-0.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated fontconfig 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, 09 Nov 2017 16:45:04 +0100
Source: fontconfig
Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev 
libfontconfig1
Architecture: source all amd64
Version: 2.12.6-0.1
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard 
Changed-By: Laurent Bigonville 
Description:
 fontconfig - generic font configuration library - support binaries
 fontconfig-config - generic font configuration library - configuration
 fontconfig-udeb - generic font configuration library - minimal runtime (udeb)
 libfontconfig1 - generic font configuration library - runtime
 libfontconfig1-dev - generic font configuration library - development
Closes: 869584 873121 874277 881278
Changes:
 fontconfig (2.12.6-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #881278, #869584)
 - Drop debian/patches/03_locale_c.utf8.patch and
   debian/patches/06_cross.patch: applied upstream
   * debian/control:
 - Bump Standards-Version to 4.1.1 (no further changes)
 - Use the priority optional instead of extra, the later is deprecated
   * debian/rules: Use ?= instead of = operator to assign DEB_BUILD_GNU_TYPE to
 please lintian
   * debian/po/fr.po: Update French debconf translations (Closes: #873121)
   * debian/po/nl.po: Update Dutch debconf translations (Closes: #874277)
   * debian/watch: Use https:// to watch new upstream releases
Checksums-Sha1:
 241bdf692e318b71206ed2d252a15b0c9ce431e3 1884 fontconfig_2.12.6-0.1.dsc
 cae963814ba4bc41f3c96876604d33fc3abfc572 1624683 fontconfig_2.12.6.orig.tar.bz2
 07ad8a288fecad10fc95f0a8085c1e77d94536dd 49736 
fontconfig_2.12.6-0.1.debian.tar.xz
 85cfb79be25948543e83787847b5e9bb75f56ecb 304296 
fontconfig-config_2.12.6-0.1_all.deb
 e23c93172e35b1710ca67fcbca4c36f0e2cf2809 50284 
fontconfig-dbgsym_2.12.6-0.1_amd64.deb
 7e2626522dc15906d43200115e853deb99344f6f 117208 
fontconfig-udeb_2.12.6-0.1_amd64.udeb
 7e3f2726f4d3c3355c78244b14db725dcdb6cf7e 7183 
fontconfig_2.12.6-0.1_amd64.buildinfo
 a5140f994c8082aa0ee43b5ca8d0326fca8a1753 439084 fontconfig_2.12.6-0.1_amd64.deb
 5bd31225eb6b9da82f6a05e6519afc52b11d59a8 272964 
libfontconfig1-dbgsym_2.12.6-0.1_amd64.deb
 3909c9d26d3a6c018ef3ad998f7c0b705b3b1f78 924216 
libfontconfig1-dev_2.12.6-0.1_amd64.deb
 0c71163aa80c0d54e725e9ada96a29ab77e41864 367852 
libfontconfig1_2.12.6-0.1_amd64.deb
Checksums-Sha256:
 90e466b5836daad14883941573be73dc607840b41af0e30

Bug#869584: marked as done (fontconfig FTBFS: error: conflicting types for 'FcObjectTypeHash')

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 13:48:59 +
with message-id 
and subject line Bug#869584: fixed in fontconfig 2.12.6-0.1
has caused the Debian Bug report #869584,
regarding fontconfig FTBFS: error: conflicting types for 'FcObjectTypeHash'
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.)


-- 
869584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontconfig
Version: 2.12.3-0.2
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

fontconfig FTBFS in sid. Tail of a build log:

| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../src 
-I/usr/include/freetype2 -Wall -Wpointer-arith -Wstrict-prototypes 
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs 
-fno-strict-aliasing -DFC_CACHEDIR=\"/var/cache/fontconfig\" 
-DFONTCONFIG_PATH=\"/etc/fonts\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread -c fcobjs.c  -fPIC -DPIC -o .libs/fcobjs.o
| In file included from fcobjs.c:33:0:
| fcobjshash.gperf:28:1: error: conflicting types for 'FcObjectTypeHash'
|  "aspect",FC_ASPECT_OBJECT
|  ^~~~
| fcobjs.c:28:1: note: previous declaration of 'FcObjectTypeHash' was here
|  FcObjectTypeHash (register const char *str, register FC_GPERF_SIZE_T len);
|  ^~~~
| In file included from fcobjs.c:33:0:
| fcobjshash.gperf:172:1: error: conflicting types for 'FcObjectTypeLookup'
| fcobjs.c:31:1: note: previous declaration of 'FcObjectTypeLookup' was here
|  FcObjectTypeLookup (register const char *str, register FC_GPERF_SIZE_T len);
|  ^~
| Makefile:638: recipe for target 'fcobjs.lo' failed
| make[4]: *** [fcobjs.lo] Error 1
| make[4]: Leaving directory '/<>/src'
| Makefile:499: recipe for target 'all' failed
| make[3]: *** [all] Error 2
| make[3]: Leaving directory '/<>/src'
| Makefile:582: recipe for target 'all-recursive' failed
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| Makefile:466: recipe for target 'all' failed
| make[1]: *** [all] Error 2
| make[1]: Leaving directory '/<>'
| /usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
'debian/stamp-makefile-build' failed
| make: *** [debian/stamp-makefile-build] Error 2
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

There is a certain time-correlation with a certain upload of gperf
3.1-1.

Helmut
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.12.6-0.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated fontconfig 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, 09 Nov 2017 16:45:04 +0100
Source: fontconfig
Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev 
libfontconfig1
Architecture: source all amd64
Version: 2.12.6-0.1
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard 
Changed-By: Laurent Bigonville 
Description:
 fontconfig - generic font configuration library - support binaries
 fontconfig-config - generic font configuration library - configuration
 fontconfig-udeb - generic font configuration library - minimal runtime (udeb)
 libfontconfig1 - generic font configuration library - runtime
 libfontconfig1-dev - generic font configuration library - development
Closes: 869584 873121 874277 881278
Changes:
 fontconfig (2.12.6-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #881278, #869584)
 - Drop debian/patches/03_locale_c.utf8.patch and
   debian/patches/06_cross.patch: applied upstream
   * debian/control:
 - Bump Standards-Version to 4.1.1 (no further changes)
 - Use the priority optional instead of extra, the later is deprecated
   * debian/rules: Use ?= instead of = operator to assign DEB_BUILD_GNU_TYPE to
 please lintian
   * debian/po/fr.po: Update French debconf trans

Bug#879046: marked as done (osm-gps-map: don't build-depend on python-gobject-dev)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 13:49:15 +
with message-id 
and subject line Bug#879046: fixed in osm-gps-map 1.1.0-2
has caused the Debian Bug report #879046,
regarding osm-gps-map: don't build-depend on python-gobject-dev
to be marked as done.

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

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


-- 
879046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osm-gps-map
Version: 1.1.0-1
Severity: important
Tags: patch

Hi,

python-gobject-dev and python-gtk2-dev are obsolete, and not needed
in your package since the gobject-introspection switch. I looked
at it and there are more improvements to be made around the
gir1.2-osmgpsmap-1.0 package, so I have attached a debdiff with
a few of them. Please consider applying and uploading it.

Thanks,
Emilio

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

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru osm-gps-map-1.1.0/debian/changelog osm-gps-map-1.1.0/debian/changelog
--- osm-gps-map-1.1.0/debian/changelog  2015-12-16 12:12:44.0 +0100
+++ osm-gps-map-1.1.0/debian/changelog  2017-10-18 19:42:10.0 +0200
@@ -1,3 +1,15 @@
+osm-gps-map (1.1.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python-gobject-dev and python-gtk2-dev build-dependencies,
+not needed since the switch to gobject-introspection bindings.
+  * Let gir1.2-osmgpsmap-1.0 depend on gir:Depends.
+  * Move .gir file to libosmgpsmap-1.0-dev per the gobject-introspection
+mini-policy.
+  * Don't suggest the dbg package from gir1.2-osmgpsmap-1.0.
+
+ -- Emilio Pozuelo Monfort   Wed, 18 Oct 2017 19:42:10 +0200
+
 osm-gps-map (1.1.0-1) unstable; urgency=medium
 
   [ Ross Gammon ]
diff -Nru osm-gps-map-1.1.0/debian/control osm-gps-map-1.1.0/debian/control
--- osm-gps-map-1.1.0/debian/control2015-12-16 12:12:44.0 +0100
+++ osm-gps-map-1.1.0/debian/control2017-10-18 19:42:10.0 +0200
@@ -14,8 +14,6 @@
libgirepository1.0-dev,
libglib2.0-dev,
libsoup2.4-dev,
-   python-gobject-dev,
-   python-gtk2-dev,
libcairo2-dev,
python-all-dev,
gnome-common,
@@ -33,8 +31,8 @@
  ${misc:Depends},
  libosmgpsmap-1.0-1 (= ${binary:Version}),
  gir1.2-osmgpsmap-1.0
-Conflicts: libosmgpsmap-1.0-0-dev
-Replaces: libosmgpsmap-1.0-0-dev
+Conflicts: libosmgpsmap-1.0-0-dev, gir1.2-osmgpsmap-1.0 (<< 1.1.0-1.1~)
+Replaces: libosmgpsmap-1.0-0-dev, gir1.2-osmgpsmap-1.0 (<< 1.1.0-1.1~)
 Description: GTK+ library to embed OpenStreetMap maps - development files
  libosmgpsmap is a library to embed maps in applications that when given GPS 
  co-ordinates, draws a GPS track, and points of interest on a moving map 
@@ -81,8 +79,8 @@
 Architecture: any
 Section: introspection
 Depends: ${misc:Depends},
+ ${gir:Depends},
  libosmgpsmap-1.0-1 (= ${binary:Version})
-Suggests: libosmgpsmap-1.0-dbg
 Description: GTK+ library to embed OpenStreetMap maps - Python bindings
  libosmgpsmap is a library to embed maps in applications that when given GPS 
  co-ordinates, draws a GPS track, and points of interest on a moving map 
diff -Nru osm-gps-map-1.1.0/debian/gir1.2-osmgpsmap-1.0.install 
osm-gps-map-1.1.0/debian/gir1.2-osmgpsmap-1.0.install
--- osm-gps-map-1.1.0/debian/gir1.2-osmgpsmap-1.0.install   2015-05-23 
01:55:40.0 +0200
+++ osm-gps-map-1.1.0/debian/gir1.2-osmgpsmap-1.0.install   2017-10-18 
19:42:10.0 +0200
@@ -1,2 +1 @@
 usr/lib/*/girepository-*/* usr/lib/girepository-1.0/
-usr/share/gir-*/*
diff -Nru osm-gps-map-1.1.0/debian/libosmgpsmap-1.0-dev.install 
osm-gps-map-1.1.0/debian/libosmgpsmap-1.0-dev.install
--- osm-gps-map-1.1.0/debian/libosmgpsmap-1.0-dev.install   2015-12-16 
12:12:44.0 +0100
+++ osm-gps-map-1.1.0/debian/libosmgpsmap-1.0-dev.install   2017-10-18 
19:42:10.0 +0200
@@ -1,2 +1,3 @@
 debian/tmp/usr/share/gtk-doc/html/libosmgpsmap/*
 usr/lib/*/pkgconfig/*
+usr/share/gir-*/*
--- End Message ---
--- Begin Message ---
Source: osm-gps-map
Source-Version: 1.1.0-2

We believe that the bug you reported is fixed

Bug#882232: python-gudev build depends on the removed python-gobject-dev transitional package

[Adrian Bunk]

Source: python-gudev
Version: 147.2-3
Severity: serious
Tags: buster sid

The transitional python-gobject-dev has been removed,
please update the build dependencies.

Bug#882172: marked as pending

[Raphaël Hertzog]

tag 882172 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/pkg-security/aircrack-ng.git/commit/?id=c7f8001

---
commit c7f8001ca7002daba64f888552a53e546110ba70
Author: Raphaël Hertzog 
Date:   Mon Nov 20 15:27:38 2017 +0100

Prepare for release to unstable

diff --git a/debian/changelog b/debian/changelog
index f1ef805..10e04fe 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,8 @@
-aircrack-ng (1:1.2-0~rc4-4) UNRELEASED; urgency=medium
+aircrack-ng (1:1.2-0~rc4-4) unstable; urgency=medium
 
   * Team upload.
-  * debian/rules: override fix perms only for indep packages
+  * debian/rules: override dh_fixperms only for arch-indep packages.
+Closes: #882172
 
  -- Sophie Brun   Mon, 20 Nov 2017 14:29:58 +0100
 

Processed: Bug#882172 marked as pending

[Debian Bug Tracking System]

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

> tag 882172 pending
Bug #882172 [src:aircrack-ng] aircrack-ng FTBFS: chmod: cannot access 
dump-join: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: LLVM 4.0 is now the default

[Debian Bug Tracking System]

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

> severity 882157 serious
Bug #882157 [src:lightspark] lightspark: Fails to build with llvm 4.0
Severity set to 'serious' from 'important'
> found 882157 0.7.2+git20150512-2.1
Bug #882157 [src:lightspark] lightspark: Fails to build with llvm 4.0
Marked as found in versions lightspark/0.7.2+git20150512-2.1.
> severity 882160 serious
Bug #882160 [src:bpfcc] bpfcc: Fails to build with llvm/clang 4.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#882172: marked as done (aircrack-ng FTBFS: chmod: cannot access dump-join: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 15:18:56 +
with message-id 
and subject line Bug#882172: fixed in aircrack-ng 1:1.2-0~rc4-4
has caused the Debian Bug report #882172,
regarding aircrack-ng FTBFS: chmod: cannot access dump-join: 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.)


-- 
882172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aircrack-ng
Version: 1:1.2-0~rc4-3
Severity: serious

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

...
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chmod 755 /<>/debian/airgraph-ng/usr/share/airgraph-ng/dump-join
chmod: cannot access 
'/<>/debian/airgraph-ng/usr/share/airgraph-ng/dump-join': No such 
file or directory
debian/rules:25: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
--- End Message ---
--- Begin Message ---
Source: aircrack-ng
Source-Version: 1:1.2-0~rc4-4

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

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated aircrack-ng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 14:29:58 +0100
Source: aircrack-ng
Binary: aircrack-ng airgraph-ng
Architecture: source
Version: 1:1.2-0~rc4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team 

Changed-By: Sophie Brun 
Description:
 aircrack-ng - wireless WEP/WPA cracking utilities
 airgraph-ng - Tool to graph txt files created by aircrack-ng
Closes: 882172
Changes:
 aircrack-ng (1:1.2-0~rc4-4) unstable; urgency=medium
 .
   [ Sophie Brun ]
   * Team upload.
   * debian/rules: override dh_fixperms only for arch-indep packages.
 Closes: #882172
 .
   [ Raphaël Hertzog ]
   * Add dh-python to Build-Depends.
Checksums-Sha1:
 635aa6ea0e20b2fe3a061220f3ffd48d007890dc 1987 aircrack-ng_1.2-0~rc4-4.dsc
 7788d8378507ce91b8629110f0221241aad80c7b 16424 
aircrack-ng_1.2-0~rc4-4.debian.tar.xz
 0cdebd86084cbac7e85855a95dc5ef4a9a5428af 5982 
aircrack-ng_1.2-0~rc4-4_source.buildinfo
Checksums-Sha256:
 3c093b2ab647c86f788d8784261186f8ecbd49920e5ad33fdd3096aeb8469e84 1987 
aircrack-ng_1.2-0~rc4-4.dsc
 896907cc4b24699fff2131cd03b787d30f600f98a5c876ae1e8d451624d907a5 16424 
aircrack-ng_1.2-0~rc4-4.debian.tar.xz
 416f817212852980007bedd14055116863e41e2bd86558cd35b6c22ac4213d6b 5982 
aircrack-ng_1.2-0~rc4-4_source.buildinfo
Files:
 e385010010d7248587db30c36202efdb 1987 net optional aircrack-ng_1.2-0~rc4-4.dsc
 ef223c4cc046fb480a2f0af72fd7fd04 16424 net optional 
aircrack-ng_1.2-0~rc4-4.debian.tar.xz
 4800d5b2efb1f8ac0292e545a05011c8 5982 net optional 
aircrack-ng_1.2-0~rc4-4_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAloS6MEACgkQA4gdq+vC
mrk1JwgAmgR1/PHWkfXJ2ahqSxCUHIred0DMHU1wnT1RO6if8mFjISmGiRAXszKf
jLE/PGJ7cjR5LmeQ2rX0dG2vwTSjroLtRsWUjfvSGgiwxucs5WUKuRBGpfabJ4Np
PmtnLdmd4sVgnjzBNrdWKzXLm3tiI1V+LCWAtcqy8gMjcQsSjNu+TQjHaekR8w34
7Nk8io6cRbCeoi2H8y++v4IbtJoTS0/zK9hWWNk3pHunCDlS52z9UnZiqI3Fg2NK
Kdydj0/3Q+cLoFbqXgLW8UK9ZsuLcI5Wq1ns9WLpF89h1PaY8wvhf46VDU5GRT3e
X1tA2yHqrVXtU1sLrFOIUm2Nf8FK7w==
=PCAN
-END PGP SIGNATURE End Message ---

Processed: clamav FTBFS with LLVM 4.0 as default

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 clamav FTBFS with LLVM 4.0 as default
Bug #873401 [src:clamav] clamav: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Changed Bug title to 'clamav FTBFS with LLVM 4.0 as default' from 'clamav: 
Please update to llvm-toolchain 4.0 or, better, 5.0'.
> severity -1 serious
Bug #873401 [src:clamav] clamav FTBFS with LLVM 4.0 as default
Severity set to 'serious' from 'normal'

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

Bug#881997: marked as done (vboot-utils FTBFS on 32bit: test failure)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 15:34:20 +
with message-id 
and subject line Bug#881997: fixed in vboot-utils 0~R63-10032.B-2
has caused the Debian Bug report #881997,
regarding vboot-utils FTBFS on 32bit: test failure
to be marked as done.

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

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


-- 
881997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vboot-utils
Version: 0~R63-10032.B-1
Severity: serious

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

...
Testing prog... /<>/build/utility/bmpblk_utility
tests/futility/run_test_scripts.sh /<>/build/install_for_test/bin
-- builtin --
test_bdb.sh ... FAILED. Stdout is recorded in 
/<>/build/tests/futility_test_results/test_bdb.sh.stdout
+ me=test_bdb.sh
+ TMP=test_bdb.sh.tmp
+ cd /<>/build/tests/futility_test_results
+ BDB_FILE=bdb.bin
+ TESTKEY_DIR=/<>/tests/testkeys
+ TESTDATA_DIR=/<>/tests/testdata
+ BDBKEY_PUB=/<>/tests/testkeys/bdbkey.keyb
+ BDBKEY_PRI=/<>/tests/testkeys/bdbkey.pem
+ DATAKEY_PUB=/<>/tests/testkeys/datakey.keyb
+ DATAKEY_PRI=/<>/tests/testkeys/datakey.pem
+ BDBKEY_DIGEST=/<>/tests/testdata/bdbkey_digest.bin
+ DATAKEY_DIGEST=/<>/tests/testdata/datakey_digest.bin
+ DATA_FILE=/<>/tests/testdata/sp-rw.bin
+ declare -i num_hash
+ load_address=0x60061ec0de
+ /<>/build/install_for_test/bin/futility bdb --create bdb.bin 
--bdbkey_pri /<>/tests/testkeys/bdbkey.pem --bdbkey_pub 
/<>/tests/testkeys/bdbkey.keyb --datakey_pub 
/<>/tests/testkeys/datakey.keyb --datakey_pri 
/<>/tests/testkeys/datakey.pem --load_address 0x60061ec0de
BDB is created successfully
+ verify
+ local key_digest=/<>/tests/testdata/bdbkey_digest.bin
+ local extra_option=
+ /<>/build/install_for_test/bin/futility bdb --verify bdb.bin 
--key_digest /<>/tests/testdata/bdbkey_digest.bin
BDB is successfully verified.
+ check_field 'Load Address:' 0x60061ec0de
++ /<>/build/install_for_test/bin/futility show bdb.bin
++ grep 'Load Address:'
+ x='  Load Address:   0x'
+ '[' '  Load Address:   0x' ']'
+ x='   0x'
+ '[' '   0x' ']'
+ x=0x
+ '[' 0x == 0x60061ec0de ']'
+ return 1
test_create.sh ... PASSED
test_dump_fmap.sh ... PASSED
test_gbb_utility.sh ... PASSED
test_load_fmap.sh ... PASSED
test_main.sh ... PASSED
test_rwsig.sh ... 1024 2048 2048_exp3 3072_exp3 4096 8192 PASSED
test_show_contents.sh ... PASSED
test_show_kernel.sh ... PASSED
test_show_vs_verify.sh ... PASSED
test_show_usbpd1.sh ... 1024 2048 4096 8192 PASSED
test_sign_firmware.sh ... 1 2 3 4 5 6 PASSED
test_sign_fw_main.sh ... PASSED
test_sign_kernel.sh ... amd64: 1 2 3 4 5 6 arm: 1 2 3 4 5 6 PASSED
test_sign_keyblocks.sh ... PASSED
test_sign_usbpd1.sh ... 1 2 3 4 PASSED
test_file_types.sh ... PASSED
FAIL: 16 / 17 passed
Makefile:1490: recipe for target 'runfutiltests' failed
make[2]: *** [runfutiltests] Error 1
make[2]: Leaving directory '/<>'
debian/rules:23: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: vboot-utils
Source-Version: 0~R63-10032.B-2

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

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated vboot-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 14:19:32 +0100
Source: vboot-utils
Binary: vboot-utils cgpt vboot-kernel-utils
Architecture: source
Version: 0~R63-10032.B-2
Distribution: unstable
Urgency: medium
Maintainer: Sophie Brun 
Changed-By: Sophie Brun 
Description:
 cgpt   - GPT manipulation tool with support for Chromium OS extensions
 vboot-kernel-utils - Chrome OS verified boot utils required to sign kernels
 vboot-utils - Chrome OS verified u-boot utilities
Closes: 881997
Changes:
 

Bug#841133: marked as done (ruby-gruff: FTBFS: Tests hang after segmentation fault)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 16:42:11 +0100
with message-id <20171120154211.3wog23nnnildvkx4@shiraz>
and subject line transitive bug
has caused the Debian Bug report #841133,
regarding ruby-gruff: FTBFS: Tests hang after segmentation fault
to be marked as done.

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

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


-- 
841133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gruff
Version: 0.6.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-gruff fails to build from source in unstable/amd64:

  […]

  /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:65:in `run_suite'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `catch'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:468:in `block in run'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:283:in `run_setup'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:248:in `run_fixture'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in 
create_fixtures_runner'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in 
create_fixtures_runner'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:470:in `block (2 levels) in 
run'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:744:in `run_test'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
 `test_bezier'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
 `new'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:230:in
 `initialize'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `reset_themes'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `new'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `initialize'
  
  -- Machine register context 
   RIP: 0x7f59938d0249 RBP: 0x RSP: 0x7ffd0ad90bd0
   RAX: 0x RBX: 0x01ee7510 RCX: 0x0021
   RDX: 0x RDI: 0x7f5993bf1b00 RSI: 0x
R8: 0x01ee7520  R9: 0x41a0 R10: 0x
   R11: 0x R12: 0x7f5993bf1b58 R13: 0x7f5993bf1b18
   R14: 0x01ee7510 R15: 0x7f5993bf1b00 EFL: 0x00010246
  

  […]

The full build log is attached.


Regards,

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


ruby-gruff.0.6.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---

Hi,

according to ci.debian.org, the package has been usable since Jan 1,
2017 after a long period of failure, matching the date of the bug
report.

I could build it here locally without problem and the problem mentioned
by Gunnar isn't showing up.

It was probably a bug triggered by a dependency, updated in the mean
time.

I am therefore closing this bug.

Cheers,

Cédric


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

Processed: Pending fixes for bugs in the golang-github-nebulouslabs-fastrand package

[Debian Bug Tracking System]

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

> tag 881105 + pending
Bug #881105 [src:golang-github-nebulouslabs-fastrand] 
golang-github-nebulouslabs-fastrand build depends on the obsolete golang-1.8-go
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#881105: Pending fixes for bugs in the golang-github-nebulouslabs-fastrand package

[pkg-go-maintainers]

tag 881105 + pending
thanks

Some bugs in the golang-github-nebulouslabs-fastrand package are
closed in revision bbb620584bd893a88f665ae7f7144f31880f1684 in branch
'master' by Dr. Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-nebulouslabs-fastrand.git/commit/?id=bbb6205

Commit message:

Use golang-any instead of the obsolete golang-1.8-go.

Closes: #881105

Bug#881105: marked as done (golang-github-nebulouslabs-fastrand build depends on the obsolete golang-1.8-go)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 16:19:28 +
with message-id 
and subject line Bug#881105: fixed in golang-github-nebulouslabs-fastrand 
0.0~git20170512.60b6156-1
has caused the Debian Bug report #881105,
regarding golang-github-nebulouslabs-fastrand build depends on the obsolete 
golang-1.8-go
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.)


-- 
881105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-nebulouslabs-fastrand
Version: 0.0~git20170420.0.5a1a312-1
Severity: serious

golang-github-nebulouslabs-fastrand build depends on the
obsolete golang-1.8-go.
--- End Message ---
--- Begin Message ---
Source: golang-github-nebulouslabs-fastrand
Source-Version: 0.0~git20170512.60b6156-1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-nebulouslabs-fastrand package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Nov 2017 17:04:38 +0100
Source: golang-github-nebulouslabs-fastrand
Binary: golang-github-nebulouslabs-fastrand-dev
Architecture: source
Version: 0.0~git20170512.60b6156-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-nebulouslabs-fastrand-dev - 10x faster than crypto/rand
Closes: 881105
Changes:
 golang-github-nebulouslabs-fastrand (0.0~git20170512.60b6156-1) unstable; 
urgency=medium
 .
   [ Bjorn Dolk ]
   * Team upload.
   * Use gbp pq for patches
 .
   [ Dr. Tobias Quathamer ]
   * New upstream version 0.0~git20170512.60b6156
   * Use golang-any instead of the obsolete golang-1.8-go. (Closes: #881105)
   * Update to Standards-Version 4.1.1
 - Use HTTPS URL for d/copyright
 - Use Priority: optional
   * Add missing golang-github-dchest-blake2b-dev to dependencies
Checksums-Sha1:
 895756d2fdf7f51de4688fd50e9440218fbf0a5f 2497 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.dsc
 f8750291bd98f441a73de75ecb769908d8d486ef 6480 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156.orig.tar.xz
 03878272be255e6687effdc7282e3de29a5f162e 2872 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.debian.tar.xz
 e4d2e19468d7a6f4868d478665cb21c0b7f13e3b 6159 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1_amd64.buildinfo
Checksums-Sha256:
 e6781a5dff3518f5a29ecc36082813634cc8ada12e1b9d3d59b764507b6d79d7 2497 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.dsc
 f2b8076fcdcfdbf4b398e26a17fe2105f2e72613ffc1aa199b1cf6d8ec39eac5 6480 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156.orig.tar.xz
 617eb1bcecdf1b1d00235cd7d30351193ca39aea1b5d6aea8d7f703b4191e472 2872 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.debian.tar.xz
 87b63ba050196e75a407ec04525b5818e2c9cb28025efac27ad19235499c882f 6159 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1_amd64.buildinfo
Files:
 240072007915557d763b05afd6263db0 2497 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.dsc
 012b6813e74a523c50e1401d4d285cfe 6480 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156.orig.tar.xz
 e141df2d550c8af459d3a0a078e4e8ba 2872 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.debian.tar.xz
 68135dc23c13fa0e19b3b8b4a6eac0df 6159 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAloS/h0ACgkQEwLx8Dbr
6xnDXhAAiS6rYZMm4imUUVnmzOyCw0fWDTqfQ/K4M1kdgdXyP1HOKt7B4DIUWvoK
4+82mGCdRLRZGZe826btiEtFxZnBy3t34EqvlHW67K2ZsHFVZcEf/SHwU9apAEFt
3W1yx3Pc+0uO4GRcDvWP49gPbIg0bcXumV8LyxXShefkgcnrKLcjKaFD0uZ4Nyu+
6I0Z8vhrhU3iDX4z51W4l8na4zM3gRuzhE/ax3afBAPatZZ1Bt44dDMvlBX5kEAy
f+M6voHgEe1V/Bhej0CDVHlVg+puo4sOl7ohJ3dupY/SD/G+tV8+gFjcl1+Cb0xP
EjR+EDobY/IM5nzX8cVkdxpOd8m

Bug#881107: Pending fixes for bugs in the gb package

[pkg-go-maintainers]

tag 881107 + pending
thanks

Some bugs in the gb package are closed in revision
9afede07d1d81a512b989566f61e1944b994e53e in branch 'master' by Dr.
Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/gb.git/commit/?id=9afede0

Commit message:

Build-Depend on golang 1.9.

Closes: #881107

Processed: Pending fixes for bugs in the gb package

[Debian Bug Tracking System]

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

> tag 881107 + pending
Bug #881107 [src:gb] gb (build) depends on the obsolete golang-1.8-go
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882239: dfwinreg FTBFS with construct 2.8.16

[Adrian Bunk]

Source: dfwinreg
Version: 20170706-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/dfwinreg-20170706'
python run_tests.py
Checking availability and versions of dependencies.
[FAILURE]   construct version: 2.8.16 is too recent, 2.5.3 or earlier 
required.
[OK]dfdatetime version: 20171109
[OK]pyregf version: 20170130
[OK]six version: 1.11.0

debian/rules:22: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Processed: tagging 881756

[Debian Bug Tracking System]

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

> tags 881756 = confirmed moreinfo
Bug #881756 [swi-prolog] swi-prolog: FTBFS on mips: Build killed with signal 
TERM
Removed tag(s) help.
> thanks
Stopping processing here.

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

Processed: severity of 881756 is normal

[Debian Bug Tracking System]

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

> severity 881756 normal
Bug #881756 [swi-prolog] swi-prolog: FTBFS on mips: Build killed with signal 
TERM
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#881107: marked as done (gb (build) depends on the obsolete golang-1.8-go)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 16:49:23 +
with message-id 
and subject line Bug#881107: fixed in gb 0.4.4-2
has caused the Debian Bug report #881107,
regarding gb (build) depends on the obsolete golang-1.8-go
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.)


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

gb depends and build depends on the obsolete golang-1.8-go.
--- End Message ---
--- Begin Message ---
Source: gb
Source-Version: 0.4.4-2

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated gb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Nov 2017 17:18:26 +0100
Source: gb
Binary: gb golang-github-constabulary-gb-dev
Architecture: source
Version: 0.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 gb - project based build tool for Go
 golang-github-constabulary-gb-dev - project based build tool for Go (source)
Closes: 881107
Changes:
 gb (0.4.4-2) unstable; urgency=medium
 .
   * Team upload.
   * Build-Depend on golang 1.9. (Closes: #881107)
   * Use debhelper v10
   * Update to Standards-Version 4.1.1
 - Use HTTPS URL for d/copyright
 - Use Priority: optional
   * Remove empty d/patches directory
Checksums-Sha1:
 bb28b3b9ef3f2233691edc5d16ed0ec815e735d2 2228 gb_0.4.4-2.dsc
 55595c3f1d2993466bbe6efb81d87bfcf445d179 4180 gb_0.4.4-2.debian.tar.xz
 01243e2e84a0fd0078a5d39122541658ea859245 5884 gb_0.4.4-2_amd64.buildinfo
Checksums-Sha256:
 97a4f025582b0de59b24e62dc39a53364596c60dfd02a456618433188c4cc6f0 2228 
gb_0.4.4-2.dsc
 73297c67f6636b4225e07f2aa545d9a270d7432c73622b4d4ae9f36e57adf9bb 4180 
gb_0.4.4-2.debian.tar.xz
 7d65090276fa1b45ac9ba47526f82ae53dd8fcc6769ac37da714f4257595d859 5884 
gb_0.4.4-2_amd64.buildinfo
Files:
 948de29f47376e9c7fd45dec5c1b4d25 2228 devel optional gb_0.4.4-2.dsc
 ad47125029bc1ca27ebadaa18bf53075 4180 devel optional gb_0.4.4-2.debian.tar.xz
 dfd71687ee61b486aa885bb31f6612ff 5884 devel optional gb_0.4.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAloTAdgACgkQEwLx8Dbr
6xmTNg//dswzcZbrJMJDdqb5TLfEIJ6WrXb0zEZ95Oi+5ZXaJRVsZFO+nowdNzyK
AoUJh/b026tP4rbjh0XjsO67s5UMe715tGGzGoy6P8i5zeMUT2LsxV1GYH+xzCa3
OXBhl4lzUjp19Xa2lzMrrRFHc35bhecuhVNyMJwvCMuKPQ3/UE8AsgDWPA285YHB
Y3stYqs0uH66Hx3HIv5HJxKdDSnzSocW87iG/bdSzYNTdYvQ89rdFcmxzCaCAAMY
erfqyetERl4qZiytHQyC7+aBJN8x4n5AaACTE5smtN1Ho6cW8GzVG+Lql+unzp0b
Z5kNMDreTYjFWvcAN4hlLdulYJ/kqJS4UCftaCaEBYiQ6nFlb3YxL2dHYtAZhud7
zJtMoq3P1i1sBkHUK8QowZVvb5c/bdUlcfr1ayNDQkTnfa2T3GGlLgJSXpgLErj/
6rCtB40m3K1aKBSff3Sc8aUJ98PJUMcGuw63FUlRpyrDikX0Umed+SV3IsofcV6R
Xx1CSPuBP85aUL7RlTV+UZ00bZqnC6ZXOrDTWKBj2/jJVzPIR54k06bcVibyr5gt
BAD74V7SGLS8tP4EP/rwTZnHwoejczpJRraJqITafd5LcAJijyrBpibo43X5i0pE
4z5k5fi50EHuTJ0Y1m3XHOFmTkvJk9v18/wP8As1LPD6j9Ymd/A=
=IvQX
-END PGP SIGNATURE End Message ---

Bug#882099: marked as done (libnih1: Dependency from libc6<2.25 breaks dist-upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 18:49:07 +0200
with message-id <20171120164907.wgizgxpyh3zbscwu@localhost>
and subject line After the second binNMU libnih1 has the correct dependency
has caused the Debian Bug report #882099,
regarding libnih1: Dependency from libc6<2.25 breaks dist-upgrade
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.)


-- 
882099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnih1
Version: 1.0.3-8
Severity: normal

Dear Maintainer,

Apt dist-upgrade wants to delete the following packages:
  cgmanager kde-plasma-desktop kdeconnect libcgmanager0 libnih-dbus1 libnih1 
libpam-systemd libvirt-daemon-system plasma-desktop plasma-widgets-addons 
plasma-workspace policykit-1 polkit-kde-1
  polkit-kde-agent-1 systemd-shim sysvinit-core udisks2


Seems the culprit is in libnih1 package:

root@hpsiddie:/home/manul# apt-get dist-upgrade -d libnih1+
Reading package lists... Done
Building dependency tree   
Reading state information... Done
libnih1 is already the newest version (1.0.3-8).
Calculating upgrade... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libnih1 : Depends: libc6 (< 2.25) but 2.25-1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


root@hpsiddie:/home/manul# apt-cache policy libc6
libc6:
  Installed: 2.24-17
  Candidate: 2.25-1
  Version table:
 2.25-1 500
500 http://ftp.us.debian.org/debian sid/main amd64 Packages
 *** 2.24-17 100
100 /var/lib/dpkg/status




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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libnih1 depends on:
ii  libc6  2.24-17

libnih1 recommends no packages.

libnih1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
After the second binNMU libnih1 has the correct dependency.

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

Bug#882243: dfvfs FTBFS with construct 2.8.16

[Adrian Bunk]

Source: dfvfs
Version: 20171022-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/dfvfs-20171022'
python run_tests.py
Checking availability and versions of dependencies.
[OK]Crypto version: 2.6.1
[FAILURE]   construct version: 2.8.16 is too recent, 2.5.3 or earlier 
required.
[OK]dfdatetime version: 20171109
[OPTIONAL]  lzma.
[OK]pybde version: 20170902
[OK]pyewf version: 20140608
[OK]pyfsntfs version: 20170315
[OK]pyfvde version: 20170930
[OK]pyfwnt version: 20170115
[OK]pyqcow version: 20170222
[OK]pysigscan version: 20170124
[OK]pysmdev version: 20171112
[OK]pysmraw version: 20171105
[OK]pytsk3 version: 20171108
[OK]pyvhdi version: 20170223
[OK]pyvmdk version: 20170226
[OK]pyvshadow version: 20170902
[OK]pyvslvm version: 20160110
[OK]six version: 1.11.0
[OK]sqlite3 version: 3.21.0

debian/rules:23: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Processed: [bts-link] source package src:collectd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:collectd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #881757 (http://bugs.debian.org/881757)
> # Bug title: collectd: CVE-2017-16820: snmp plugin: double free or heap 
> corruption
> #  * https://github.com/collectd/collectd/issues/2291
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 881757 + fixed-upstream
Bug #881757 [src:collectd] collectd: CVE-2017-16820: snmp plugin: double free 
or heap corruption
Added tag(s) fixed-upstream.
> usertags 881757 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#882247:

[積丹尼 Dan Jacobson]

Package: firefox
Version: 58.0~b4-1
Severity: grave

Firefox just starts in the corner of the screen with a . Unusable.

Bug#881577: marked as done (libmagics++-dev: cmake files require libraries without package dependency)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 17:20:15 +
with message-id 
and subject line Bug#881577: fixed in magics++ 2.34.3-6
has caused the Debian Bug report #881577,
regarding libmagics++-dev: cmake files require libraries without package 
dependency
to be marked as done.

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

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


-- 
881577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmagics++-dev
Version: 2.34.3-4
Severity: serious
Control: affects -1 src:metview

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

...
/usr/bin/ld: cannot find -lOdb_fortran
/usr/bin/ld: cannot find -lOdb
/usr/bin/ld: cannot find -leckit
/usr/bin/ld: cannot find -leckit_geometry
/usr/bin/ld: cannot find -leckit_linalg
/usr/bin/ld: cannot find -leckit_maths
/usr/bin/ld: cannot find -leckit_web
/usr/bin/ld: cannot find -leckit_cmd
/usr/bin/ld: cannot find -lmetkit
collect2: error: ld returned 1 exit status
src/uPlot/CMakeFiles/uPlot.dir/build.make:3405: recipe for target 'bin/uPlot' 
failed
make[3]: *** [bin/uPlot] Error 1


The libraries at the commandline seem to come from
/usr/lib/x86_64-linux-gnu/cmake/magics/magics-*
--- End Message ---
--- Begin Message ---
Source: magics++
Source-Version: 2.34.3-6

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated magics++ package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Nov 2017 15:29:03 +
Source: magics++
Binary: libmagplus3v5 libmagics++-dev magics++ python-magics++ python3-magics++ 
libmagics++-data libmagics++-metview-dev
Architecture: source all amd64
Version: 2.34.3-6
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libmagics++-data - Data files needed for magics++ library
 libmagics++-dev - Development files for ECMWF  plotting software MAGICS++
 libmagics++-metview-dev - Libraries needed for building MetView
 libmagplus3v5 - ECMWF meteorological plotting software library
 magics++   - Executables for the magics++ library
 python-magics++ - python support for Magics++
 python3-magics++ - Python3 support for Magics++
Closes: 881577
Changes:
 magics++ (2.34.3-6) unstable; urgency=medium
 .
   * Fix typo in control file. Closes: #881577
Checksums-Sha1:
 227e5a457a4386735018efe65f5b81a605a5f67e 2833 magics++_2.34.3-6.dsc
 e619d8efe7fb3d31dc8be5c59af5265c0d9f3b8b 35732 magics++_2.34.3-6.debian.tar.xz
 0d3c85811273eb6ddeabaeffecf6525681770423 36646324 
libmagics++-data_2.34.3-6_all.deb
 edb8fce11d8f8f85d137b6c43b50f0aa3ebb8929 109176 
libmagics++-dev_2.34.3-6_amd64.deb
 eb2e400ec4be0df97a957eb93b5a209b40a95a05 761720 
libmagics++-metview-dev_2.34.3-6_amd64.deb
 f200b34c89a9d9a43de4115242d1ffe8164904e8 72856780 
libmagplus3v5-dbgsym_2.34.3-6_amd64.deb
 27a60ba1947d0a7bcfda9c90ffd8630f002cc9a7 3052832 
libmagplus3v5_2.34.3-6_amd64.deb
 3f0dda1e477290edb22d5c3bc340e2d6f985edae 321280 
magics++-dbgsym_2.34.3-6_amd64.deb
 4585059df2673b0829ae4bb85d265f8166e15510 18950 
magics++_2.34.3-6_amd64.buildinfo
 fe11de3ec5b682ca49786f2b4ff29b1ab1e98e4d 62408 magics++_2.34.3-6_amd64.deb
 7c6d5b0f3beaf2ce3429ef429bc4e8f102065f68 61896 
python-magics++-dbgsym_2.34.3-6_amd64.deb
 0df23a87053c30864282e3aaff0b3c65195bfdb5 62824 
python-magics++_2.34.3-6_amd64.deb
 749e8041fc118a2a3fd6a94d6f709529d560c58e 62496 
python3-magics++-dbgsym_2.34.3-6_amd64.deb
 cccf6f8e36c37df39348b10ab1de19759e05921d 62460 
python3-magics++_2.34.3-6_amd64.deb
Checksums-Sha256:
 52f1d0d9ac768a204bdfddc2a69aac2dda53cd3067760ce1ef5726bb6257fb51 2833 
magics++_2.34.3-6.dsc
 dc28351ec8adfcdce7b281da2d5fe41edafe7b9ecfe3dca301d810e77072 35732 
magics++_2.34.3-6.debian.tar.xz
 03c1968e7907138f5766cb22a3442e2267c2c1cbfb0674eaf66e81256f0386c3 36646324 
libmagics++-data_2.34.3-6_all.deb
 2f9c93e58cd2357164ec95ceea826e2102c9e1a1ab346c255de14b72490a36bb 109176 
libmagics++-dev_2.34.3-6_amd64.deb
 4725a29770

Bug#882248: sympathy FTBFS with glibc 2.25

[Adrian Bunk]

Source: sympathy
Version: 1.2.1+woking+cvs+git20161222
Severity: serious
Tags: buster sid

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

...
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -g -Werror -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libsympathy_a-lockfile.o `test -f 'lockfile.c' || echo './'`lockfile.c
lockfile.c: In function 'lockfile_add_name_from_dev':
lockfile.c:317:13: error: In the GNU C Library, "major" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "major", include 
 directly. If you did not intend to use a system-defined macro
 "major", you should undefine it after including . [-Werror]
   sprintf (buf, "LCK.%03d.%03d", major (dev), minor (dev));
 ^~~



 
lockfile.c:317:13: error: In the GNU C Library, "minor" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "minor", include 
 directly. If you did not intend to use a system-defined macro
 "minor", you should undefine it after including . [-Werror]
   sprintf (buf, "LCK.%03d.%03d", major (dev), minor (dev));
 ^~~



 
cc1: all warnings being treated as errors
Makefile:988: recipe for target 'libsympathy_a-lockfile.o' failed
make[3]: *** [libsympathy_a-lockfile.o] Error 1

Bug#882247:

[Jos van Wolput]

Package: firefox
Version: 58.0~b4-1
Severity: grave

After upgrading firefox to version 58.0~b4-1 I get the same issue.

Bug#881876: marked as done (astromenace: FTBFS on 32-bit arches: dh_install: astromenace missing files: astromenace_64.png)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 19:10:43 +0100
with message-id 
and subject line Re: Bug#881876: astromenace: FTBFS on 32-bit arches: 
dh_install: astromenace missing files: astromenace_64.png
has caused the Debian Bug report #881876,
regarding astromenace: FTBFS on 32-bit arches: dh_install: astromenace missing 
files: astromenace_64.png
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.)


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

Hi,

astromenace FTBFS on 32-bit architectures (tried i386 and armhf) while
it builds fine on amd64.

   debian/rules override_dh_install
make[1]: Entering directory '/build/astromenace-1.3.2+repack'
dh_install --exclude=astromenace_64.png
dh_install: astromenace missing files: astromenace_64.png
dh_install: missing files, aborting
debian/rules:28: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 25

This could be caused by a change in debhelper.


Andreas


astromenace_1.3.2+repack-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On 2017-11-20 14:08, James Cowgill wrote:
> I can't reproduce this with debhelper 10.10.9. Could you try building it
> again?

It was reproducible a few days ago (and even hit amd64 shortly after
after I filed the bug), but today it built cleanly on both sid and
buster for amd64, i386 and armhf. So something else was fixed inbetween. :-)


Andreas--- End Message ---

Bug#881496: [Pkg-privacy-maintainers] Bug#881496: onioncircuits: python3/testing and apparmor/testing breaks onioncircuits

[Sascha Steinbiss]

Hi all,

ah, this sheds some light on the situation. However:

> audit[3722]: AVC apparmor="DENIED" operation="file_mmap" 
> profile="/usr/bin/onioncircuits" 
> name="/usr/lib/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so" 
> pid=3722 comm="onioncircuits" requested_mask="m" denied_mask="m" fsuid=1000 
> ouid=0

This is interesting, since the corresponding line in the python AppArmor
abstractions [1] (which are imported by the onioncircuits profile [2]) is:

  /usr/lib{,32,64}/python3.[0-6]/lib-dynload/*.somr,

which indeed already has the mmap flag set. It's been in testing for
some while now (since bzr revision #1671, which was the initial update
to upstream's 2.11.1).
I also can't see it being overridden anywhere. So I am not sure why this
permission should be denied...

Any ideas? (AppArmor-savvy team members?)

Cheers
Sascha


[1]
https://alioth.debian.org/scm/loggerhead/collab-maint/apparmor/view/head:/profiles/apparmor.d/abstractions/python
[2]
https://anonscm.debian.org/cgit/pkg-privacy/packages/onioncircuits.git/tree/apparmor/usr.bin.onioncircuits#n8

> So, python3/testing + apparmor/testing is a breaking
> combination. Downgrading to apparmor/stable fixes the problem.
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers stable
>   APT policy: (500, 'stable'), (70, 'unstable'), (60, 'testing'), (50, 
> 'experimental')
> Architecture: amd64
>  (x86_64)
> 
> Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages onioncircuits depends on:
> ii  gir1.2-glib-2.01.54.1-3
> ii  gir1.2-gtk-3.0 3.22.26-1
> ii  python3-gi 3.22.0-2
> ii  python3-pycountry  17.5.14+ds1-0.1
> ii  python3-stem   1.6.0-1
> pn  python3:any
> 
> onioncircuits recommends no packages.
> 
> Versions of packages onioncircuits suggests:
> ii  tor-geoipdb  0.3.1.8-2
> 
> -- no debconf information
> 
> ___
> Pkg-privacy-maintainers mailing list
> pkg-privacy-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-privacy-maintainers
> 



signature.asc
Description: OpenPGP digital signature

Bug#858828: Pending fixes for bugs in the golang-github-google-certificate-transparency package

[pkg-go-maintainers]

tag 858828 + pending
thanks

Some bugs in the golang-github-google-certificate-transparency
package are closed in revision
6105e2a0ad302a6d7cdfda8cfb64dee1cb910e30 in branch 'master' by Dr.
Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-google-certificate-transparency.git/commit/?id=6105e2a

Commit message:

Build-Depend on libssl-dev.

Closes: #858828

Processed: Pending fixes for bugs in the golang-github-google-certificate-transparency package

[Debian Bug Tracking System]

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

> tag 858828 + pending
Bug #858828 [golang-github-google-certificate-transparency] 
golang-github-google-certificate-transparency: Please migrate to openssl1.1 in 
Buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

Package: libc6-amd64
Version: 2.25-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I have a x86-64 system with i386 and x32 foreign architectures (because I
need to develop software for i386 and x32 architectures).

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

I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.

   * What was the outcome of this action?

Halfway through apt upgrade it failed and I ended up with unusable system where
large number of binaries were segfauting on startup without doign anything.

   * What outcome did you expect instead?

The upgrade to libc-2.25 should work.


The reason for the catastrophic failure is this:

There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
x86-64 libc in /lib64/). This package is not technically needed (because
x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
installed nonetheless because of some dependencies.

apt makes sure that all libc packages are upgraded at once to the same
version. However, during the upgrade process, the package
libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, we
temporarily have two libcs with different versions on the system, and this
mismatch makes most of the x86-64 binaries crash. Due to the crashes, the
upgrade doesn't proceed and it doesn't install the correct libc version in
/lib/x86_64-linux-gnu/.

The result is unusable system.

The system can be fixed if we mount it from another machine and remove the
libc files from /lib64 directory - the upgrade can then proceed and
install correct libc in /lib/x86_64-linux-gnu/.

The libc package should be fixed, so that if we have mismatching libc
version in /lib64 and in /lib/x86_64-linux-gnu/, it shouldn't crash,
because such mismatch happens temporarily during upgrade.


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

Kernel: Linux 4.14.0 (SMP w/12 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8), 
LANGUAGE=cs_CZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libc6-amd64 depends on:
ii  libc6  2.25-1

libc6-amd64 recommends no packages.

libc6-amd64 suggests no packages.

-- no debconf information

Bug#858828: marked as done (golang-github-google-certificate-transparency: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 18:49:29 +
with message-id 
and subject line Bug#858828: fixed in 
golang-github-google-certificate-transparency 0.0~git20160709.0.0f6e3d1~ds1-3
has caused the Debian Bug report #858828,
regarding golang-github-google-certificate-transparency: 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.)


-- 
858828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-google-certificate-transparency
Version: 0.0~git20160709.0.0f6e3d1~ds1-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertag: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Source: golang-github-google-certificate-transparency
Source-Version: 0.0~git20160709.0.0f6e3d1~ds1-3

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-google-certificate-transparency package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Nov 2017 19:32:14 +0100
Source: golang-github-google-certificate-transparency
Binary: golang-github-google-certificate-transparency-dev
Architecture: source
Version: 0.0~git20160709.0.0f6e3d1~ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-google-certificate-transparency-dev - Framework for monitoring 
and auditing SSL certificates
Closes: 858828
Changes:
 golang-github-google-certificate-transparency 
(0.0~git20160709.0.0f6e3d1~ds1-3) unstable; urgency=medium
 .
   * Team upload.
   * Use debhelper v10
   * Update to Standards-Version 4.1.1
 - Use HTTPS URL for d/copyright
 - Use Priority: optional
   * Build-Depend on libssl-dev. (Closes: #858828)
Checksums-Sha1:
 3b9510c64cb29f6d8f763dae116c3d748bc1fed9 2824 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.dsc
 b47575e2226431d0dd3b755257f2780b1cdc1a20 4628 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.debian.tar.xz
 6fa42fa93bf131f8358166c900c9a449304456b6 6913 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3_amd64.buildinfo
Checksums-Sha256:
 2879921007038c988fe8d817ecace36f4ed08ec0020bc1ababa28be57c265b1c 2824 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.dsc
 5f1bfb85df22d2037f7774775f20fa0ec19cf9aa8d1347807648dcccbb9f9024 4628 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.debian.tar.xz
 03aad6797a23a1245685c47fe8d6cd785fd4c729d5b0be3a942f503aa394f1bb 6913 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3_amd64.buildinfo
Files:
 2652c83c2deca11cd0d2854ff9d4f474 2824 devel optional 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.dsc
 1fc5bc1c025b06932608bf8399417a06 4628 devel optional 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.debian.tar.xz
 5ea59b33df32452c0320c7192948191c 6913 devel optional 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAloTIGQACgkQEwLx8Dbr
6xlsIw/9FLAfOuO/jNJ9DfsClU3KXsSyaT218yAs4JI0kIjG/IZfjd8cy9g+OYX6
V3TxXeDkQG8tYHh83J+tEpltvmqtASqEp8tJiVIqMr7hEzdmNSxy+bY82xZqUNTr
liP0lFgIqdlW4gT21TRZICAwFveiH/jM4VuutQTejMQu6A2YxaEuMd84MnOejiOt
nwvCosOtYI4aSYvxIznGGO2pS87SeAWmIp0s6FzWYvpbIwVcB2OnJBZPJbr0rP8e
F3uhS7gB27s3ZFGcreX5H8QU0kd21UMkngVuAiI5/L4asG+JgT0k4cxYGekF0bNe
zqbTNNpIvuDQ0ucPjYnbV8jR/oW4cLgOKglilJAiASVNLSAIzzio9sFvqx/Dhn/7
kiCI7chIypK7gn92nF+NcAiolXcL7ZPzfU2pYOU7L6TV5HmH0D5pFFG1b3PPKrcy
IYlL5ynWY2vFIIzjA6YRtSYfnlc4FJRiyJk7y/cHBjx7fYMAY72MxaMHvZNCDpKH
wFca9U2FrsOt0xZ68kUIJjM30Pr422QwHc5XppnZU5WHF37E

Processed: Re: julia: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873408 [src:julia] julia: Please update to llvm-toolchain 4.0 or, better, 
5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: ycmd: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873412 [src:ycmd] ycmd: Please update to llvm-toolchain 4.0 or, better, 5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: Bug#873411: kdevelop: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873411 [src:kdevelop] kdevelop: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: pocl: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873417 [src:pocl] pocl: Please update to llvm-toolchain 4.0 or, better, 5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: qtcreator: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873414 [src:qtcreator] qtcreator: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Severity set to 'serious' from 'normal'

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

Bug#881643: marked as done (spacefm not updated after libavfilter update, broken link.)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 20:08:19 +0100
with message-id <98e7f6a9-2b21-bd87-820e-29278a276...@linuxmint.pl>
and subject line Re: Bug#881643: spacefm not updated after libavfilter update, 
broken link.
has caused the Debian Bug report #881643,
regarding spacefm not updated after libavfilter update, broken link.
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.)


-- 
881643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spacefm-gtk3
Version: 1.0.5-2
Severity: grave
Source: spacefm
Tags: sid

$ spacefm
spacefm: relocation error: /usr/lib/x86_64-linux-gnu/libavfilter.so.6: symbol
av_hwframe_map, version LIBAVUTIL_55 not defined in file libavutil.so.55 with 
link time
reference
$

Looks like the spacefm shoul dbe re-built using the new version of libavfilter
(libavfilter6 is in version 7:3.4-2) and libavutil (libavutil55 in version 
10:3.2.2-dmo1),
or that libavutil is missing some symbols.


$ ls /usr/lib/x86_64-linux-gnu/libavutil.so*
/usr/lib/x86_64-linux-gnu/libavutil.so.55
/usr/lib/x86_64-linux-gnu/libavutil.so.55.34.100

$ls /usr/lib/x86_64-linux-gnu/libavfilter.so.6*
/usr/lib/x86_64-linux-gnu/libavfilter.so.6
/usr/lib/x86_64-linux-gnu/libavfilter.so.6.107.100


libc6 : Version: 2.24-17


-- 
Nathaël PAJANI - ED3L - Techno-Innov
Internet : http://www.ed3l.fr - http://www.techno-innov.fr
--- End Message ---
--- Begin Message ---

Bug was invalid. Error was related to the configuration of user system.


--
 .''`.  Mateusz Łukasik
: :' :  https://l0calh0st.pl
`. `'   Debian Member - mat...@linuxmint.pl
  `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851--- End Message ---

Bug#873411: kdevelop: Please update to llvm-toolchain 4.0 or, better, 5.0

[Pino Toscano]

Control: severity -1 important

(see below why...)

In data lunedì 20 novembre 2017 20:05:20 CET, Emilio Pozuelo Monfort ha scritto:
> Control: severity -1 serious
> 
> On Wed, 06 Sep 2017 21:34:47 +0200 Pino Toscano  wrote:
> > Hi,
> > 
> > In data domenica 27 agosto 2017 16:01:25 CEST, Sylvestre Ledru ha scritto:
> > > Source: kdevelop
> > > Severity: normal
> > > 
> > > Hello,
> > > 
> > > Currently, we have 6 versions of the llvm toolchain in the archive.
> > > I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)
> > > 
> > > Could you please update your package to use 4.0 (or, better, 5.0 which 
> > > will be released very 
> > > soon)?
> > 
> > Sure, but only after the versions available build and work at least on
> > all the release architectures.  So far, llvm 3.9 is still affected by
> > #866354, since it did not build fine again since then -- this is
> > holding kdevelop in unstable for more than 2 months, and I really would
> > like to get it into testing.
> > 
> > I see that each of the llvm sources has various bugs, FTBFSes, cmake
> > issues, and so forth... as a suggestion from a bystander, what about
> > focusing on at most 3 versions of llvm in the archive, instead of
> > upload every version available (and then have to cleanup llvm users
> > periodically, like with bugs like this)?
> > 
> > > I will update the severity of this bug at the end of September
> > 
> > Doing that with the current state of llvm versions would be a bad idea.
> 
> It should be fine now with 4.0. Would be good if this could move to either
> unversioned llvm/clang (which defaults to 4.0 now) or to versioned 4.0. 
> Bumping
> to serious as we want to remove 3.8 soon to reduce the high number of llvm
> versions that we currently ship.

IMHO, if the goal would really be getting rid of old llvm versions in
the archive, then (as I wrote above) the llvm maintainers ought to
a) fix the latest stable (= 5.0)
b) switch llvm-defaults to the above

llvm got versioned symbols, so loading two llvm versions in the same
process (hello, mesa), although it is ugly. This should allow kdevelop
to switch back to llvm-defaults, even if llvm maintainers should care
a bit more about it, instead of almost letting it rot...

Anyway, I just lowered the severity of this bug to important, so
kdevelop 5.2 can migrate to testing.  Yes, it is an important update
(merged kdevplatform, so the separate source can be dropped), so I
really it to reach testing.
Because of another issue in the past, related to llvm (#866354),
kdevelop 5.1.x was stuck in unstable for basically 2 months. I don't
want llvm to get in the way of kdevelop, once again.

-- 
Pino Toscano

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

Processed: Re: Bug#873411: kdevelop: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #873411 [src:kdevelop] kdevelop: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Severity set to 'important' from 'serious'

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

Bug#882258: busybox: CVE-2017-16544: lineedit: do not tab-complete any strings which have control characters

[Salvatore Bonaccorso]

Source: busybox
Version: 1:1.27.2-1
Severity: grave
Tags: security

Hi,

the following vulnerability was published for busybox. I realize you
know of the issue already but just filling to have a tracking bug as
well in the BTS.

CVE-2017-16544[0]:
| In the add_match function in libbb/lineedit.c in BusyBox through
| 1.27.2, the tab autocomplete feature of the shell, used to get a list
| of filenames in a directory, does not sanitize filenames and results in
| executing any escape sequence in the terminal. This could potentially
| result in code execution, arbitrary file writes, or other attacks.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16544
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16544
[1] 
https://git.busybox.net/busybox/commit/?id=c3797d40a1c57352192c6106cc0f435e7d9c11e8

Please adjust the affected versions in the BTS as needed, only
unstable checked so far.

Regards,
Salvatore

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Samuel Thibault]

Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> x86-64 libc in /lib64/). This package is not technically needed (because
> x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> installed nonetheless because of some dependencies.

The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
tried to do it in the past, just to see, with the same kind of effect as
you had.

The question is rather how that got pulled at all. What package thinks
it's a good idea to pull libc6-amd64?  Apart from libc64* packages
(which should normally not get pulled either), I can see uc-echo which
should rather use foreign dependencies, and :i386 multilib packages
which don't really make sense to install either.

I don't remember whether it was tried to make libc6-amd64:i386 conflict
with libc6:amd64 (and vice-versa for i386) to make sure that this
doesn't happen by misfortune?

Samuel

Processed: severity of 882258 is important, tagging 882258

[Debian Bug Tracking System]

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

> severity 882258 important
Bug #882258 [src:busybox] busybox: CVE-2017-16544: lineedit: do not 
tab-complete any strings which have control characters
Severity set to 'important' from 'grave'
> tags 882258 + upstream fixed-upstream
Bug #882258 [src:busybox] busybox: CVE-2017-16544: lineedit: do not 
tab-complete any strings which have control characters
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#882260: neutron-lbaas FTBFS: testtools.matchers._impl.MismatchError: 'www.hostfromdnsname1.com' != u'www.hostFromDNSName1.com'

[Adrian Bunk]

Source: neutron-lbaas
Version: 1:11.0.1-1
Severity: serious

Some recent change in unstable makes neutron-lbaas FTBFS:

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

...
==
FAIL: 
neutron_lbaas.tests.unit.common.tls_utils.test_cert_parser.TestTLSParseUtils.test_alt_subject_name_parses
neutron_lbaas.tests.unit.common.tls_utils.test_cert_parser.TestTLSParseUtils.test_alt_subject_name_parses
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "neutron_lbaas/tests/unit/common/tls_utils/test_cert_parser.py", line 
243, in test_alt_subject_name_parses
self.assertEqual('www.hostfromdnsname1.com', hosts['dns_names'][0])
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 'www.hostfromdnsname1.com' != 
u'www.hostFromDNSName1.com'


--
Ran 544 tests in 264.046s

FAILED (failures=1)
debian/rules:41: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Processed: Re: Bug#881149: htslib FTBFS: test failures on i386

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #881149 [src:htslib] htslib FTBFS: test failures on i386
Added tag(s) patch.

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

Bug#881149: htslib FTBFS: test failures on i386

[Graham Inggs]

Control: tags -1 + patch

I found the documentation of the optimization flags for GCC 7.2.0 [1].
I was then able to bisect the list of flags enabled for -O2 and
determine which ones needed to be disabled in order to build htslib on
i386.  Patch follows.

--- a/debian/rules
+++ b/debian/rules
@@ -7,7 +7,9 @@

 include /usr/share/dpkg/default.mk

-export DEB_CFLAGS_MAINT_APPEND = -fno-strict-aliasing
+ifneq (,$(filter $(DEB_HOST_ARCH),i386))
+  export DEB_CFLAGS_MAINT_APPEND=-fno-strict-aliasing -fno-code-hoisting
+endif

 %:


[1] https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Optimize-Options.html

Processed: found 882255 in 2.24-1

[Debian Bug Tracking System]

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

> found 882255 2.24-1
Bug #882255 [libc6-amd64] libc6-amd64: Multilib causes catastrophic system 
failure during upgrade to libc 2.25
Marked as found in versions glibc/2.24-1.
> thanks
Stopping processing here.

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

Bug#882173: marked as pending

[Jaromír Mikeš]

tag 882173 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/audacity.git/commit/?id=9464548

---
commit 9464548bfc7fd10c10198d5bdfd007bc743f122e
Author: Jaromír Mikeš 
Date:   Mon Nov 20 21:08:35 2017 +0100

Start new upload.

diff --git a/debian/changelog b/debian/changelog
index d6bcb89..84ceb5e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+audacity (2.2.0-2) UNRELEASED; urgency=medium
+
+  * Build without sbsms to fix FTBFS on non-x86 archs. (Closes: #882173)
+
+ -- Jaromír Mikeš   Mon, 20 Nov 2017 21:08:16 +0100
+
 audacity (2.2.0-1) unstable; urgency=medium
 
   [ Sebastian Ramacher ]

Processed: Bug#882173 marked as pending

[Debian Bug Tracking System]

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

> tag 882173 pending
Bug #882173 [src:audacity] audacity: FTBFS on !x86 and baseline violation on 
i386
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#882181: mockito: FTBFS - java.lang.UnsupportedOperationException: Cannot nest operations in the same thread

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #882181 [src:mockito] mockito: FTBFS - 
java.lang.UnsupportedOperationException: Cannot nest operations in the same 
thread
Added tag(s) confirmed.

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

Bug#882181: mockito: FTBFS - java.lang.UnsupportedOperationException: Cannot nest operations in the same thread

[Markus Koschany]

Control: tags -1 confirmed

Am 20.11.2017 um 00:27 schrieb Gilles Filippini:
> Source: mockito
> Version: 1.10.19-2
> Severity: serious
> Justification: FTBFS
> 
> Hi,
> 
> While testing a build of mockito against a new json-simple releae I've
> experienced a FTBFS which is reproducible when building into a clean sid
> chroot:
> 
> Task :test class loader hash: 83f3637f6805a7b149525a93c5faad58
> Task :test actions class loader hash: d883a18cf154fc57e90f4d3fa9e5588f
> Executing task ':test' (up-to-date check took 0.041 secs) due to:
>   No history is available.
> Cannot nest operations in the same thread. Each nested operation must run in 
> its own thread.

[...]

Hi,

thanks for reporting. This appears to be the same issue Olivier Sallou
has mentioned on debian-java a few weeks ago. [1] This is a Gradle bug.
I'm not exactly sure why it is surfacing now. I am in the process of
updating Gradle to a newer version but it will take more time to finish
the work.

Regards,

Markus

[1] https://lists.debian.org/debian-java/2017/10/msg00078.html



signature.asc
Description: OpenPGP digital signature

Processed: tagging 790204

[Debian Bug Tracking System]

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

> tags 790204 + pending
Bug #790204 [src:gnucash] gnucash: depends on libwebkitgtk-1.0-0 which is 
deprecated
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> found 873414 4.3.1-1
Bug #873414 [src:qtcreator] qtcreator: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Marked as found in versions qtcreator/4.3.1-1.
> found 873417 0.13-9
Bug #873417 [src:pocl] pocl: Please update to llvm-toolchain 4.0 or, better, 5.0
Marked as found in versions pocl/0.13-9.
> found 873408 0.4.7-7
Bug #873408 [src:julia] julia: Please update to llvm-toolchain 4.0 or, better, 
5.0
Marked as found in versions julia/0.4.7-7.
> thanks
Stopping processing here.

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

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-20 20:47, Samuel Thibault wrote:
> Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > x86-64 libc in /lib64/). This package is not technically needed (because
> > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > installed nonetheless because of some dependencies.
> 
> The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
> tried to do it in the past, just to see, with the same kind of effect as
> you had.
> 
> The question is rather how that got pulled at all. What package thinks
> it's a good idea to pull libc6-amd64?  Apart from libc64* packages
> (which should normally not get pulled either), I can see uc-echo which
> should rather use foreign dependencies, and :i386 multilib packages
> which don't really make sense to install either.
> 
> I don't remember whether it was tried to make libc6-amd64:i386 conflict
> with libc6:amd64 (and vice-versa for i386) to make sure that this
> doesn't happen by misfortune?

Arch-qualified conflicts are not supported. What you can do is make
libc6-amd64 and libc6:amd64 not coinstallable (by changing the Replaces
into a Conflicts). Maybe it's time to do it and let GCC enjoy multiarch
+ multilib pain.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#882263: libc6-dev-mips64el-cross breaks linking executables

[Helmut Grohne]

Package: libc6-dev-mips64el-cross
Version: 20
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

I was trying to use gcc-mips64el-linux-gnuabi64 to link a trivial
executable:

$ echo 'int main(){return 0;}' | mips64el-linux-gnuabi64-gcc -x c - -o /dev/null

With libc6-dev:mips64el installed, this just works. As soon as I install
libc6-dev-mips64el-cross, it fails though:

/usr/lib/gcc-cross/mips64el-linux-gnuabi64/7/../../../../mips64el-linux-gnuabi64/bin/ld:
 cannot find /usr/mips64el-linux-gnuabi64/lib/ld.so.1
collect2: error: ld returned 1 exit status

This renders libc6-dev-mips64el-cross pretty much useless.

Helmut

Bug#882264: libtemplate-declare-perl FTBFS with libhtml-lint-perl 2.26+dfsg-1

[Adrian Bunk]

Source: libtemplate-declare-perl
Version: 0.47-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libtemplate-declare-perl.html

...
Test Summary Report
---
t/aliasing.t  (Wstat: 1280 Tests: 30 Failed: 5)
  Failed tests:  11, 16, 21, 26, 30
  Non-zero exit status: 5
t/arg-declaration-styles.t (Wstat: 2048 Tests: 39 Failed: 8)
  Failed tests:  3, 6, 9, 15, 21, 27, 33, 39
  Non-zero exit status: 8
t/attributes.t(Wstat: 1280 Tests: 10 Failed: 5)
  Failed tests:  2, 4, 6, 8, 10
  Non-zero exit status: 5
t/closures.t  (Wstat: 2048 Tests: 16 Failed: 8)
  Failed tests:  2, 4, 6, 8, 10, 12, 14, 16
  Non-zero exit status: 8
t/forms.t (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/importing.t (Wstat: 512 Tests: 18 Failed: 2)
  Failed tests:  14, 18
  Non-zero exit status: 2
t/indexhtml.t (Wstat: 512 Tests: 4 Failed: 2)
  Failed tests:  2, 4
  Non-zero exit status: 2
t/mixing.t(Wstat: 1280 Tests: 30 Failed: 5)
  Failed tests:  11, 16, 21, 26, 30
  Non-zero exit status: 5
t/private.t   (Wstat: 1024 Tests: 14 Failed: 4)
  Failed tests:  3, 6, 9, 12
  Non-zero exit status: 4
t/self.t  (Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  3
  Non-zero exit status: 1
t/siblings.t  (Wstat: 768 Tests: 7 Failed: 3)
  Failed tests:  2, 4, 7
  Non-zero exit status: 3
t/subclassing.t   (Wstat: 768 Tests: 11 Failed: 3)
  Failed tests:  3, 5, 11
  Non-zero exit status: 3
t/subtemplates.t  (Wstat: 1024 Tests: 9 Failed: 4)
  Failed tests:  2, 4, 6, 9
  Non-zero exit status: 4
t/trivial.t   (Wstat: 1024 Tests: 9 Failed: 4)
  Failed tests:  2, 4, 6, 9
  Non-zero exit status: 4
t/utf8.t  (Wstat: 1536 Tests: 12 Failed: 6)
  Failed tests:  2, 4, 6, 8, 10, 12
  Non-zero exit status: 6
t/xss.t   (Wstat: 1024 Tests: 8 Failed: 4)
  Failed tests:  2, 4, 6, 8
  Non-zero exit status: 4
Files=51, Tests=478, 12 wallclock secs ( 0.23 usr  0.15 sys +  6.65 cusr  0.71 
csys =  7.74 CPU)
Result: FAIL
Failed 16/51 test programs. 65/478 subtests failed.
Makefile:786: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 4

Bug#874295: clementine: installs non-free plugin at runtime

[Anthony DeRobertis]

(from Jonas Smedegaard  via the bug):

> One of several functions of Clementine is to stream audio from cloud
> service Spotify.  Initially selecting that function triggers a routine
> where Clementine (asks for concent and then) downloads and installs a
> non-free binary driver.
> 
> Policy 2.2.1 states that "None of the packages in the main archive area
> require software outside of that area to function."
> 
> Clementine should either be moved to contrib, or the Spotify function be
> removed.

I suggest this isn't a Policy violation. Clementine functions without
the Spotify plugin; e.g., it'll happily play local music files, or from
any of the non-Spotify streaming sources.

Compare to, for example, all web browsers except lynx (and similar).
They all happily and automatically download and execute non-free code
(JavaScript), without any warning whatsoever. And if you turn off
JavaScript, they lose quite a bit more functionality than Clementine
does (I'd go so far as to say they become fairly useless — quite a bit
of the web doesn't work w/o JavaScript).

Many of them have their own plugin services (at least both Firefox and
Chromium do) that happily install and execute non-free code, again
without any warning (the only warnings they give are about access to
data, browsing history, etc., nothing about freedom).

Further, Debian understands software broadly (including, e.g.,
data—basically, "not hardware"), not just executables. If this bug
report's reading of policy were correct, Clementine would need to
disable most of streaming music services as the music they provide
doesn't follow DFSG. (And even lynx would have to be removed.)

I think it'd be reasonable to make the confirmation dialog explicitly
say that the plugin is not free software. But other than that, which
does not warrant severity: serious, I think this bug should be closed as
not a bug.

Bug#874295: clementine: installs non-free plugin at runtime

[Anthony DeRobertis]

[resending just to -submitter, sorry I messed up the address the first
time.]

(from Jonas Smedegaard  via the bug):

> One of several functions of Clementine is to stream audio from cloud
> service Spotify.  Initially selecting that function triggers a routine
> where Clementine (asks for concent and then) downloads and installs a
> non-free binary driver.
> 
> Policy 2.2.1 states that "None of the packages in the main archive area
> require software outside of that area to function."
> 
> Clementine should either be moved to contrib, or the Spotify function be
> removed.

I suggest this isn't a Policy violation. Clementine functions without
the Spotify plugin; e.g., it'll happily play local music files, or from
any of the non-Spotify streaming sources.

Compare to, for example, all web browsers except lynx (and similar).
They all happily and automatically download and execute non-free code
(JavaScript), without any warning whatsoever. And if you turn off
JavaScript, they lose quite a bit more functionality than Clementine
does (I'd go so far as to say they become fairly useless — quite a bit
of the web doesn't work w/o JavaScript).

Many of them have their own plugin services (at least both Firefox and
Chromium do) that happily install and execute non-free code, again
without any warning (the only warnings they give are about access to
data, browsing history, etc., nothing about freedom).

Further, Debian understands software broadly (including, e.g.,
data—basically, "not hardware"), not just executables. If this bug
report's reading of policy were correct, Clementine would need to
disable most of streaming music services as the music they provide
doesn't follow DFSG. (And even lynx would have to be removed.)

I think it'd be reasonable to make the confirmation dialog explicitly
say that the plugin is not free software. But other than that, which
does not warrant severity: serious, I think this bug should be closed as
not a bug.

Bug#882266: horizon accesses the internet during the build

[Adrian Bunk]

Source: horizon
Version: 3:12.0.0-4
Severity: serious

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

...
==
ERROR: Failure: ConnectionError 
(HTTPSConnectionPool(host='translate.openstack.org', port=443): Max retries 
exceeded with url: /rest/project/horizon/version/master/locales (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary 
failure in name resolution',)))
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/build/1st/horizon-12.0.0/horizon/management/commands/pull_catalog.py", 
line 21, in 
ZANATA_LOCALES = requests.get("https://translate.openstack.org/rest/project";
  File "/usr/lib/python2.7/dist-packages/requests/api.py", line 72, in get
return request('get', url, params=params, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/api.py", line 58, in request
return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 502, in 
request
resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 612, in 
send
r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 504, in 
send
raise ConnectionError(e, request=request)
ConnectionError: HTTPSConnectionPool(host='translate.openstack.org', port=443): 
Max retries exceeded with url: /rest/project/horizon/version/master/locales 
(Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] 
Temporary failure in name resolution',))

--
Ran 209 tests in 66.346s

FAILED (SKIP=7, errors=1)
...

Processed: reassign 882223 to glibc-doc

[Debian Bug Tracking System]

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

> # match possible intention of reporter
> reassign 882223 glibc-doc
Bug #882223 [manpages-dev] Document security problems with system.3 and popen.3 
(argument injection)
Bug reassigned from package 'manpages-dev' to 'glibc-doc'.
No longer marked as found in versions manpages/4.13-3.
Ignoring request to alter fixed versions of bug #882223 to the same values 
previously set
> thanks
Stopping processing here.

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