date:20181024

Processed: closing 871197

2018-10-24 Thread Debian Bug Tracking System

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

> close 871197 2.14.0-1
Bug #871197 [src:eclipse-emf] eclipse-emf: FTBFS: 
java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (No such file or directory)
Marked as fixed in versions eclipse-emf/2.14.0-1.
Bug #871197 [src:eclipse-emf] eclipse-emf: FTBFS: 
java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (No such file or directory)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#871197: closing 871197

2018-10-24 Thread Jochen Sprickerhof

close 871197 2.14.0-1
thanks

Processed: src

2018-10-24 Thread Debian Bug Tracking System

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

> affects 910485 - hypre
Bug #910485 [libpsm2-2] libpsm2-2: times out on /dev/hfi1_0 device and causes 
test errors
Removed indication that 910485 affects hypre
> affects 910485 + src:hypre
Bug #910485 [libpsm2-2] libpsm2-2: times out on /dev/hfi1_0 device and causes 
test errors
Added indication that 910485 affects src:hypre
> thanks
Stopping processing here.

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

Bug#911716: marked as done (python-urllib3 FTBFS: ssl tests fail)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Thu, 25 Oct 2018 03:36:30 +
with message-id 
and subject line Bug#911716: fixed in python-urllib3 1.24-1
has caused the Debian Bug report #911716,
regarding python-urllib3 FTBFS: ssl tests fail
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.)


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

python-urllib3 fails to build from source in unstable. Building the
experimental version succeeds. A build ends with:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-urllib3_1.22-1.rbuild.log.gz

| === FAILURES 
===
| _ TestConnection.test_match_hostname_mismatch 
__
| 
| self = 
| 
| def test_match_hostname_mismatch(self):
| cert = {'subjectAltName': [('DNS', 'foo')]}
| asserted_hostname = 'bar'
| try:
| with mock.patch('urllib3.connection.log.error') as mock_log:
| >   _match_hostname(cert, asserted_hostname)
| 
| test/test_connection.py:39: 
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
| 
| cert = {'subjectAltName': [('DNS', 'foo')]}, asserted_hostname = 'bar'
| 
| def _match_hostname(cert, asserted_hostname):
| try:
| >   match_hostname(cert, asserted_hostname)
| 
| urllib3/connection.py:356: 
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
| 
| cert = {'subjectAltName': [('DNS', 'foo')]}, hostname = 'bar'
| 
| def match_hostname(cert, hostname):
| """Verify that *cert* (in decoded format as returned by
| SSLSocket.getpeercert()) matches the *hostname*.  RFC 2818 and RFC 
6125
| rules are followed.
| 
| The function matches IP addresses rather than dNSNames if hostname is 
a
| valid ipaddress string. IPv4 addresses are supported on all platforms.
| IPv6 addresses are supported on platforms with IPv6 support (AF_INET6
| and inet_pton).
| 
| CertificateError is raised on failure. On success, the function
| returns nothing.
| """
| if not cert:
| raise ValueError("empty or no certificate, match_hostname needs a 
"
|  "SSL socket or SSL context with either "
|  "CERT_OPTIONAL or CERT_REQUIRED")
| try:
| host_ip = _inet_paton(hostname)
| except ValueError:
| # Not an IP address (common case)
| host_ip = None
| dnsnames = []
| san = cert.get('subjectAltName', ())
| for key, value in san:
| if key == 'DNS':
| if host_ip is None and _dnsname_match(value, hostname):
| return
| dnsnames.append(value)
| elif key == 'IP Address':
| if host_ip is not None and _ipaddress_match(value, host_ip):
| return
| dnsnames.append(value)
| if not dnsnames:
| # The subject is only checked when there is no dNSName entry
| # in subjectAltName
| for sub in cert.get('subject', ()):
| for key, value in sub:
| # XXX according to RFC 2818, the most specific Common Name
| # must be used.
| if key == 'commonName':
| if _dnsname_match(value, hostname):
| return
| dnsnames.append(value)
| if len(dnsnames) > 1:
| raise CertificateError("hostname %r "
| "doesn't match either of %s"
| % (hostname, ', '.join(map(repr, dnsnames
| elif len(dnsnames) == 1:
| raise CertificateError("hostname %r "
| "doesn't match %r"
| >   % (hostname, dnsnames[0]))
| E   ssl.SSLCertVerificationError: ("hostname 'bar' doesn't match 
'foo'",)
| 
| /usr/lib/python3.7/ssl.py:327: SSLCertVerificationError
| 
| During handling of the above exception, another exception occurred:
| 
| self = 
| 
| def test_match_hostname_mismatch(self):
| cert = {'subjectAltName': [('DNS', 'foo')]}
| asserted_hostname = 'bar'
| try:
| with mock.patch('urllib3.connection.log.error') as mock_log:
| _match_hostname(cert, asserted_hostname)
|

Bug#911733: marked as done (libfiu: FTBFS on 32-bit architectures?)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Thu, 25 Oct 2018 03:34:50 +
with message-id 
and subject line Bug#911733: fixed in libfiu 0.97-2
has caused the Debian Bug report #911733,
regarding libfiu: FTBFS on 32-bit architectures?
to be marked as done.

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

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


-- 
911733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfiu
Version: 0.97-1
Severity: serious
Justification: fails to build from source
X-Debbugs-CC: Alberto Bertogli 

Hi,

libfiu fails to build from source in sid/i386:

[…]

for i in modules/libc.mm.mod.fl modules/libc.str.mod.fl modules/linux.io.mod.fl 
modules/posix.io.mod.fl modules/posix.mm.mod.fl modules/posix.proc.mod.fl 
modules/posix.stdio.mod.fl; do cat $i >> function_list; done
In file included from modules/posix.stdio.mod.c:9:
modules/posix.stdio.mod.c:568:20: error: conflicting types for 'ftello64'
 mkwrap_top(off_t , ftello64, (FILE *stream), (stream), (FILE *), (-1))
^~~~
./codegen.h:99:8: note: in definition of macro 'mkwrap_def'
  RTYPE NAME PARAMS \
^~~~
modules/posix.stdio.mod.c:568:1: note: in expansion of macro 'mkwrap_top'
 mkwrap_top(off_t , ftello64, (FILE *stream), (stream), (FILE *), (-1))
 ^~
In file included from modules/posix.stdio.mod.c:14:
/usr/include/stdio.h:751:18: note: previous declaration of 'ftello64' was here
 extern __off64_t ftello64 (FILE *__stream) __wur;
  ^~~~
make[4]: *** [Makefile:67: modules/posix.stdio.mod.o] Error 1
m
[…]

The full build log is attached or can be viewed here:

  
https://buildd.debian.org/status/fetch.php?pkg=libfiu=i386=0.97-1=1540338469=1

§

Any ideas? There are some other failures that can be viewed here:

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

… which looks like 32-bit architectures only. (Click "Build
Attempted"...)


Best wishes,

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


libfiu.0.97-1.sid.i386.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libfiu
Source-Version: 0.97-2

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated libfiu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Oct 2018 23:17:19 -0400
Source: libfiu
Binary: libfiu0 fiu-utils libfiu-dev python-fiu python3-fiu
Architecture: source amd64
Version: 0.97-2
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 fiu-utils  - userspace fault injection framework (utilities)
 libfiu-dev - userspace fault injection framework (development libraries)
 libfiu0- userspace fault injection framework
 python-fiu - userspace fault injection framework (Python bindings)
 python3-fiu - userspace fault injection framework (Python 3 bindings)
Closes: 911733
Changes:
 libfiu (0.97-2) unstable; urgency=medium
 .
   * Mangle the return offset size for 64-bit variants too to prevent FTBFS on
 32-bit architectures. (Closes: #911733)
Checksums-Sha1:
 64cfb8e2604ad56c3930b61769b58c0d3f8c22d3 2154 libfiu_0.97-2.dsc
 27da5216be7892724a641b3d4a1a86a894f42f80 6372 libfiu_0.97-2.debian.tar.xz
 7dbe40ce18583eba071bfbca9aa64fafa5cb11f9 12524 fiu-utils_0.97-2_amd64.deb
 7c33e0dba693437a2a7d22e6364c99792109ccee 29048 libfiu-dev_0.97-2_amd64.deb
 ba2dc6e1b1d8dadfc94698035de680237caf50ae 106396 libfiu0-dbgsym_0.97-2_amd64.deb
 9ba1497ddd69aad717681ba08fb4ba9761a33b09 36212 libfiu0_0.97-2_amd64.deb
 1210f36069bedb792e9ea81bc3eb650dda0476d2 8746 libfiu_0.97-2_amd64.buildinfo
 3c6289d6d70c54f68151265be13a25f2bdde248f 13204 
python-fiu-dbgsym_0.97-2_amd64.deb
 06e868406c7ac2300479b548538fcea22b0d9964 11896 python-fiu_0.97-2_amd64.deb
 9d1948740ef0047f85d3cda78bd306117f4362b9 27236 
python3-fiu-dbgsym_0.97-2_amd64.deb
 19bd30b06af43597c9611d65b98d642bc03c397e 12152 python3-fiu_0.97-2_amd64.deb
Checksums-Sha256:

Bug#910394: sqlcipher: Crashes on running any SQL Statement (with a key)

2018-10-24 Thread Mark Eichin

Freshly installed to test this:

i-meant-that$ dpkg --status sqlcipher|grep Version
Version: 3.2.0-2
i-meant-that$ sqlcipher mydata.db
SQLCipher version 3.8.6 2014-08-15 11:46:33
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> pragma key = 'passphrase';
sqlite> create table memos(text, priority INTEGER);
Segmentation fault

ie. one line from https://www.zetetic.net/sqlcipher/sqlcipher-api/ about
actually setting a key, plus the first line of the man page example.

(Bonus points for maybe adding any mention at all of "pragma key" to the man 
page :-)

i-meant-that$ gdb --quiet -ex run --args sqlcipher mydata.db
SQLCipher version 3.8.6 2014-08-15 11:46:33
sqlite> pragma key = 'passphrase';
sqlite> create table memos(text, priority INTEGER);

Program received signal SIGSEGV, Segmentation fault.
0x76fc195f in EVP_EncryptUpdate () from 
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
(gdb) where
#0  0x76fc195f in EVP_EncryptUpdate () from 
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#1  0x77b22e3b in sqlcipher_openssl_cipher (ctx=0x5579c238, 
mode=, key=0x5579c258 
"\352U\243\236\375\266\026\037\242\247\370\232\215\323\063O\362-w\367\223c\242ɑ^W_]\254#)",
key_sz=, iv=0x55797f98 
"+\372\032\331\003O\271\246\201>\210\210\360\375W\034\253p\227\303\315\331Y\210@\252\233\\\212<\032y\177\334\330\030\231\213F\177.\365\032\222\360\063\361\067q",
in=0x5579d1b8 "\004", in_sz=960, out=0x55797bd8 "") at 
sqlite3.c:16517
#2  0x77b3347e in sqlcipher_page_cipher (ctx=ctx@entry=0x55797b38, 
for_ctx=, pgno=1, mode=1, page_sz=, 
in=0x5579d1b8 "\004", out=0x55797bd8 "") at sqlite3.c:15696
#3  0x77b45104 in sqlite3Codec (iCtx=0x55797b38, 
data=0x5579d1a8, pgno=1, mode=6) at sqlite3.c:14389
#4  0x77b53799 in pager_write_pagelist 
(pPager=pPager@entry=0x55785a78, pList=0x5579d5e0) at sqlite3.c:48086
#5  0x77b5b5fa in sqlite3PagerCommitPhaseOne (pPager=0x55785a78, 
zMaster=zMaster@entry=0x0, noSync=noSync@entry=0) at sqlite3.c:50033
#6  0x77b5b7cf in sqlite3PagerCommitPhaseOne (noSync=0, zMaster=0x0, 
pPager=) at sqlite3.c:49932
#7  sqlite3BtreeCommitPhaseOne (p=0x55785558, zMaster=zMaster@entry=0x0) at 
sqlite3.c:57764
#8  0x77b5f421 in sqlite3BtreeCommitPhaseOne (zMaster=0x0, p=) at sqlite3.c:89551
#9  vdbeCommit (p=0x5579cb48, db=0x5576ec58) at sqlite3.c:1586
#10 sqlite3VdbeHalt (p=p@entry=0x5579cb48) at sqlite3.c:1993
#11 0x77b8e926 in sqlite3VdbeExec (p=p@entry=0x5579cb48) at 
sqlite3.c:71867
#12 0x77b8f8cf in sqlite3Step (p=0x5579cb48) at sqlite3.c:69631
#13 sqlite3_step (pStmt=) at sqlite3.c:4161
#14 0xa9d3 in shell_exec (db=0x5576ec58, zSql=0x5576ebc0 
"create table memos(text, priority INTEGER);", pArg=0x7fffd2d0, 
pzErrMsg=0x7fffd138, xCallback=0x9a90 )
at ./src/shell.c:1360
#15 0xbbdf in process_input (p=0x7fffd2d0, in=0x0) at 
./src/shell.c:3613
#16 0x7406 in main (argc=, argv=) at 
./src/shell.c:4129

Processed: Re: libfiu: FTBFS on 32-bit architectures?

2018-10-24 Thread Debian Bug Tracking System

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

> tags 911733 + pending patch
Bug #911733 [src:libfiu] libfiu: FTBFS on 32-bit architectures?
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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

Bug#911733: libfiu: FTBFS on 32-bit architectures?

2018-10-24 Thread Chris Lamb

tags 911733 + pending patch
thanks

Hi Alberto,

I think this is what we need:

  
https://salsa.debian.org/lamby/pkg-libfiu/commit/f80fb7ab3a96fe206e8610fc1f01dd1b370f206e

  ...e-return-offset-size-for-64-bit-variants-to.patch | 20 
  debian/patches/series|  1 +
  2 files changed, 21 insertions(+)


Regards,

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

Bug#911801: pacemaker: Cannot complete pcs cluster setup command, returns error HTTP401

2018-10-24 Thread Duncan Hare

Package: pacemaker
Version: 1.1.16-1
Severity: grave
Justification: causes non-serious data loss



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

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

Versions of packages pacemaker depends on:
ii  corosync   2.4.2-3+deb9u1
ii  dbus   1.10.26-0+deb9u1
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u3
ii  libcfg62.4.2-3+deb9u1
ii  libcib41.1.16-1
ii  libcmap4   2.4.2-3+deb9u1
ii  libcorosync-common42.4.2-3+deb9u1
ii  libcpg42.4.2-3+deb9u1
ii  libcrmcluster4 1.1.16-1
ii  libcrmcommon3  1.1.16-1
ii  libcrmservice3 1.1.16-1
ii  libglib2.0-0   2.50.3-2
ii  libgnutls303.5.8-5+deb9u3
ii  liblrmd1   1.1.16-1
ii  libpam0g   1.1.8-3.6
ii  libpe-rules2   1.1.16-1
ii  libpe-status10 1.1.16-1
ii  libpengine10   1.1.16-1
ii  libqb0 1.0.1-1
ii  libquorum5 2.4.2-3+deb9u1
ii  libstonithd2   1.1.16-1
ii  libtransitioner2   1.1.16-1
ii  lsb-base   9.20161125
ii  pacemaker-common   1.1.16-1
ii  pacemaker-resource-agents  1.1.16-1
ii  perl   5.24.1-3+deb9u4

Versions of packages pacemaker recommends:
ii  fence-agents 4.0.25-1
ii  pacemaker-cli-utils  1.1.16-1

Versions of packages pacemaker suggests:
ii  cluster-glue  1.0.12-5
ii  pcs   0.9.155+dfsg-2+deb9u1


Running: /usr/bin/ruby -I/usr/share/pcsd/ /usr/share/pcsd/pcsd-cli.rb auth
--Debug Input Start--
{"username": "hacluster", "local": false, "nodes": ["greene", "pinke"], 
"password": "Cl3nt4n@@", "force": true}
--Debug Input End--
Return Value: 0
--Debug Output Start--
{
  "status": "ok",
  "data": {
"auth_responses": {
  "pinke": {
"status": "ok",
"token": "c4dca519-18ab-4ca9-b218-af6e03b3731d"
  },
  "greene": {
"status": "ok",
"token": "d0ea589d-0a05-40d8-a366-82b40d557465"
  }
},
"sync_successful": true,
"sync_nodes_err": [

],
"sync_responses": {
}
  },
  "log": [
"I, [2018-10-24T17:03:01.093531 #7491]  INFO -- : PCSD Debugging enabled\n",
"D, [2018-10-24T17:03:01.093652 #7491] DEBUG -- : Did not detect RHEL 6\n",
"I, [2018-10-24T17:03:01.093733 #7491]  INFO -- : Running: 
/usr/sbin/corosync-cmapctl totem.cluster_name\n",
"I, [2018-10-24T17:03:01.093816 #7491]  INFO -- : CIB USER: hacluster, 
groups: \n",
"D, [2018-10-24T17:03:01.134130 #7491] DEBUG -- : [\"totem.cluster_name 
(str) = debian\\n\"]\n",
"D, [2018-10-24T17:03:01.134912 #7491] DEBUG -- : []\n",
"D, [2018-10-24T17:03:01.135169 #7491] DEBUG -- : Duration: 0.040189124s\n",
"I, [2018-10-24T17:03:01.135618 #7491]  INFO -- : Return Value: 0\n",
"I, [2018-10-24T17:03:01.430297 #7491]  INFO -- : Running: /usr/sbin/pcs 
status nodes corosync\n",
"I, [2018-10-24T17:03:01.430644 #7491]  INFO -- : CIB USER: hacluster, 
groups: \n",
"D, [2018-10-24T17:03:03.173921 #7491] DEBUG -- : [\"Corosync Nodes:\\n\", 
\" Online:\\n\", \" Offline:\\n\"]\n",
"D, [2018-10-24T17:03:03.174581 #7491] DEBUG -- : []\n",
"D, [2018-10-24T17:03:03.174852 #7491] DEBUG -- : Duration: 1.743259319s\n",
"I, [2018-10-24T17:03:03.175252 #7491]  INFO -- : Return Value: 0\n",
"I, [2018-10-24T17:03:03.184745 #7491]  INFO -- : Sending config 'tokens' 
version 1 baa843266738f0107221006d0e7dfd43ba74c73b to nodes: \n"
  ]
}
--Debug Output End--


Running: /usr/sbin/corosync -v

Finished running: /usr/sbin/corosync -v
Return value: 0
--Debug Stdout Start--
Corosync Cluster Engine, version '2.4.2'
Copyright (c) 2006-2009 Red Hat, Inc.

--Debug Stdout End--
--Debug Stderr Start--

--Debug Stderr End--

Destroying cluster on nodes: pinke, greene...
Running: /usr/bin/ruby -I/usr/share/pcsd/ /usr/share/pcsd/pcsd-cli.rb 
read_tokens
--Debug Input Start--
{}
--Debug Input End--
Running: /usr/bin/ruby -I/usr/share/pcsd/ /usr/share/pcsd/pcsd-cli.rb 
read_tokens
--Debug Input Start--
{}
--Debug Input End--
Return Value: 0
--Debug Output Start--
{
  "status": "ok",
  "data": {
  },
  "log": [
"I, [2018-10-24T17:03:36.610130 #7562]  INFO -- : PCSD Debugging enabled\n",
"D, [2018-10-24T17:03:36.610225 #7562] DEBUG -- : Did not detect RHEL 6\n",
"I, [2018-10-24T17:03:36.610297 #7562]  INFO -- : Running: 
/usr/sbin/corosync-cmapctl totem.cluster_name\n",
"I, [2018-10-24T17:03:36.610391 #7562]  INFO -- : CIB USER: hacluster, 
groups: \n",
"D, [2018-10-24T17:03:36.793991 #7562] DEBUG -- :

Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread Ben Hutchings

On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote:
> On 10/24/18 6:42 PM, Oliver Riesener wrote:
> > No unetbootin, it’s the stock  stretch netboot   installation.
> > initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
> > didn’t find kernel modules anymore. The old one before too. 
> > It’s a point release problem. Older versions of modules (.udeb ?) seems
> > to be from debian repo. 
> Are you sure you used a matching kernel image and initrd? Both have to match
> their version otherwise it won't work.

But when you use netboot the udebs in the archive *also* have to match.
And they don't after a point release.

Ben.

> I'm creating debian-installer images myself on a regular basis and from my
> current knowledge and testing, it's very unlikely that there is a bug in
> the kernel and initrd matching.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates




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

Bug#911768: [pkg-gnupg-maint] Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

2018-10-24 Thread Daniel Kahn Gillmor

Hi Tiziano--

On Wed 2018-10-24 17:24:33 +0200, Tiziano Zito wrote:
> pinentry-gnome3 (but also pinentry-gtk-2) does not open a window anymore to 
> ask for a passphrase. If run from terminal it shows:
>
> No Gcr System Prompter available, falling back to curses
> OK Pleased to meet you
>
> It was working fine since years. Of the packages pinentry-gnome3 depends on, 
> I have only upgraded recently libgpg-error0,  libncursesw6, libtinfo6.
> Even downgrading libgpg-error0 to 1.32-1 does not fix the issue.

hmm, looking at the installed packages:

> Versions of packages pinentry-gnome3 depends on:
> ii  gcr  3.28.0-1
> ii  libassuan0   2.5.1-2
> ii  libc62.27-6
> ii  libgcr-base-3-1  3.28.0-1
> ii  libglib2.0-0 2.58.1-2
> ii  libgpg-error01.32-3
> ii  libncursesw6 6.1+20181013-1
> ii  libsecret-1-00.18.6-3
> ii  libtinfo66.1+20181013-1
>
> Versions of packages pinentry-gnome3 recommends:
> pn  dbus-user-session  

can you try installing dbus-user-session, then log out and log back in
and let me know whether it works in that case?

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#911797: Multiple vulnerabilities

2018-10-24 Thread Moritz Muehlenhoff

Source: open-build-service
Severity: grave
Tags: security

Please verify whether these affect OBS as packaged in Debian:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12477
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12478
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12479
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12467
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12466

Cheers,
Moritz

Bug#886394: marked as done (java.lang.ClassNotFoundException: javafx.scene.layout.HBox)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 20:59:57 +
with message-id 
and subject line Bug#886394: fixed in pdfsam 3.3.7-1
has caused the Debian Bug report #886394,
regarding java.lang.ClassNotFoundException: javafx.scene.layout.HBox
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.)


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

Dear Maintainer,

I can't launch pdfsam. Here is the traceback:

Exception in thread "main" java.lang.NoClassDefFoundError: 
javafx/scene/layout/HBox
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
at 
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:801)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:699)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:622)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:580)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
at org.pdfsam.community.App.main(App.java:34)
Caused by: java.lang.ClassNotFoundException: javafx.scene.layout.HBox
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
... 10 more

Thanks.

Ludo

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 
'experimental')
Architecture: i386 (i686)

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

Versions of packages pdfsam depends on:
ii  libatinject-jsr330-api-java1.0+ds1-5
ii  libbcmail-java 1.58-1
ii  libbcprov-java 1.58-1
ii  libcommons-io-java 2.5-2
ii  libcommons-lang3-java  3.5-1
ii  libfontawesomefx-java  8.9-1
ii  libgettext-commons-java0.9.6-6
ii  libhibernate-validator-java4.3.3-3
ii  libjackson2-jr-java2.9.1-1
ii  liblogback-java1:1.2.3-2
ii  libsambox-java 1.1.19-1
ii  libsejda-eventstudio-java  1.0.6-1
ii  libsejda-injector-java 1.0.2-1
ii  libsejda-java  3.2.38-1
ii  libslf4j-java  1.7.25-2
ii  openjdk-8-jre [java8-runtime]  8u151-b12-1
ii  openjdk-9-jre [java8-runtime]  9.0.1+11-1
ii  openjfx8u141-b14-3

pdfsam recommends no packages.

pdfsam suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pdfsam
Source-Version: 3.3.7-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 Oct 2018 20:45:43 +0200
Source: pdfsam
Binary: pdfsam
Architecture: source
Version: 3.3.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 pdfsam - PDF Split and Merge
Closes: 886394
Changes:
 pdfsam (3.3.7-1) unstable; urgency=medium
 .
   * New upstream version 3.3.7.
   * Switch to compat level 11.
   * Add javafx.patch and port PDFsam to use

Bug#909624: flightgear-phi: diff for NMU version 2018.1.1+dfsg1-1.1

2018-10-24 Thread Adrian Bunk

Control: tags 909624 + patch
Control: tags 909624 + pending

Dear maintainer,

I've prepared an NMU for flightgear-phi (versioned as 2018.1.1+dfsg1-1.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

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

diff -Nru flightgear-phi-2018.1.1+dfsg1/debian/changelog flightgear-phi-2018.1.1+dfsg1/debian/changelog
--- flightgear-phi-2018.1.1+dfsg1/debian/changelog	2018-05-14 21:39:03.0 +0300
+++ flightgear-phi-2018.1.1+dfsg1/debian/changelog	2018-10-24 23:31:32.0 +0300
@@ -1,3 +1,10 @@
+flightgear-phi (2018.1.1+dfsg1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the sprintf.min.js symlink. (Closes: #909624)
+
+ -- Adrian Bunk   Wed, 24 Oct 2018 23:31:32 +0300
+
 flightgear-phi (2018.1.1+dfsg1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru flightgear-phi-2018.1.1+dfsg1/debian/links flightgear-phi-2018.1.1+dfsg1/debian/links
--- flightgear-phi-2018.1.1+dfsg1/debian/links	2018-05-14 21:39:03.0 +0300
+++ flightgear-phi-2018.1.1+dfsg1/debian/links	2018-10-24 23:31:29.0 +0300
@@ -8,4 +8,4 @@
 usr/share/javascript/requirejs/text.jsusr/share/games/flightgear/Phi/3rdparty/require/text.js
 usr/share/javascript/bootstrap/css/bootstrap.min.css  usr/share/games/flightgear/Aircraft/c172p/WebPanel/bootstrap/bootstrap.min.css
 usr/share/javascript/bootstrap/js/bootstrap.min.jsusr/share/games/flightgear/Aircraft/c172p/WebPanel/bootstrap/bootstrap.min.js
-usr/lib/nodejs/sprintf-js/src/sprintf.min.js  usr/share/games/flightgear/Phi/3rdparty/sprintf/sprintf.min.js
+usr/share/javascript/sprintf-js/sprintf.min.jsusr/share/games/flightgear/Phi/3rdparty/sprintf/sprintf.min.js

Processed: flightgear-phi: diff for NMU version 2018.1.1+dfsg1-1.1

2018-10-24 Thread Debian Bug Tracking System

Processing control commands:

> tags 909624 + patch
Bug #909624 [flightgear-phi] flightgear: broken symlink: 
/usr/share/games/flightgear/Phi/3rdparty/sprintf/sprintf.min.js -> 
../../../../../../lib/nodejs/sprintf-js/src/sprintf.min.js
Added tag(s) patch.
> tags 909624 + pending
Bug #909624 [flightgear-phi] flightgear: broken symlink: 
/usr/share/games/flightgear/Phi/3rdparty/sprintf/sprintf.min.js -> 
../../../../../../lib/nodejs/sprintf-js/src/sprintf.min.js
Added tag(s) pending.

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

Processed: found 909027 in 1.30.4-1

2018-10-24 Thread Debian Bug Tracking System

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

> found 909027 1.30.4-1
Bug #909027 [gvfs-daemons] Leaves daemons running after purge
Marked as found in versions gvfs/1.30.4-1.
> thanks
Stopping processing here.

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

Bug#911780: psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8

2018-10-24 Thread Ervin Hegedüs

Hi Andreas,

On Wed, Oct 24, 2018 at 07:17:21PM +0200, Andreas Beckmann wrote:
> Package: psk31lx
> Version: 2.1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> lenny had the following binary package (from src:twpsk):

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

> According to
> http://snapshot.debian.org/binary/psk31lx/
> there is quite a mess of version numbers.
> 
> Bumping the source package version to 2.1+really2.1-1 with no further
> changes should fix this. This is preferred over adding an epoch.
> 
> $ dpkg --compare-versions 2.1+2.2beta1-8 lt 2.1+really2.1-1 && echo lt
> lt

thanks for the info, I've contacted with Ted, the maintainer of
psk31lx, is there any avaliable new relase - hope he will answer
as soon.

Anyway, I've checked the source package of psk31lx on stretch:

$ lsb_release -id
Distributor ID: Debian
Description:Debian GNU/Linux 9.4 (stretch)

$ apt-get source psk31lx
...

$ cat psk31lx-2.1/debian/changelog 
psk31lx (2.1-1) unstable; urgency=low

  * Initial release. (Closes: #772087)

 -- Milan Kupcevic   Sat, 07 Nov 2015 19:51:41 -0500

$ cat psk31lx-2.1/debian/control 
Source: psk31lx
Section: hamradio
Priority: optional
Maintainer: Debian Hamradio Maintainers 
Uploaders: Milan Kupcevic 
Build-Depends: debhelper (>= 9.0.0), libncurses5-dev, libpulse-dev
Standards-Version: 3.9.6
Homepage: http://wa0eir.bcts.info/psk31lx.html

Package: psk31lx
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: PSK31 terminal application with text-based user
interface
 psk31lx is a simple text-based terminal program with a built-in phase scope 
 and spectrum analyzer to aid in signal tuning. It uses a sound card to receive 
 and transmit PSK31 tone.

So looks like the avaliable source and binary packages are
differs (just fyi).

(And I din't find the source of the current stable package - the package site
is this:

https://packages.debian.org/stretch/psk31lx

the source points to here:
http://http.debian.net/debian/pool/main/p/psk31lx/psk31lx_2.1-1.debian.tar.xz

which is what I got through apt-get source, not the released
binary source (2.1-1+b1). This package contains an "empty"
changelog, there isn't any version history - how could I fix this
what you described?)

thanks, regards,

a.

Bug#910836: marked as done (libeclipse-e4-ui-services-java: unsatisfiable dep on libeclipse-e4-core-di-services-java)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 20:13:06 +
with message-id 
and subject line Bug#910836: fixed in eclipse-platform-ui 4.7.3-3
has caused the Debian Bug report #910836,
regarding libeclipse-e4-ui-services-java: unsatisfiable dep on 
libeclipse-e4-core-di-services-java
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.)


-- 
910836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libeclipse-e4-ui-services-java
Version: 1.3.0+eclipse4.7.3-2
Severity: serious

libeclipse-e4-ui-services-java has an unsatisifiable dependency on
libeclipse-e4-core-di-services-java

I'm wondering if that's a typo and it should depend on
libeclipse-e4-ui-services-java

I looked at
https://salsa.debian.org/java-team/eclipse-platform-ui/commit/df00f1b0

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: eclipse-platform-ui
Source-Version: 4.7.3-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated eclipse-platform-ui 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 19 Oct 2018 15:13:16 +0200
Source: eclipse-platform-ui
Binary: libeclipse-core-commands-java libeclipse-core-databinding-java 
libeclipse-core-databinding-beans-java 
libeclipse-core-databinding-observable-java 
libeclipse-core-databinding-property-java libeclipse-e4-core-commands-java 
libeclipse-e4-emf-xpath-java libeclipse-e4-ui-bindings-java 
libeclipse-e4-ui-css-core-java libeclipse-e4-ui-css-swt-java 
libeclipse-e4-ui-css-swt-theme-java libeclipse-e4-ui-di-java 
libeclipse-e4-ui-dialogs-java libeclipse-e4-ui-model-workbench-java 
libeclipse-e4-ui-services-java libeclipse-e4-ui-swt-gtk-java 
libeclipse-e4-ui-widgets-java libeclipse-e4-ui-workbench-java 
libeclipse-e4-ui-workbench3-java libeclipse-e4-ui-workbench-addons-swt-java 
libeclipse-e4-ui-workbench-renderers-swt-java 
libeclipse-e4-ui-workbench-swt-java libeclipse-jface-java 
libeclipse-jface-databinding-java libeclipse-ui-forms-java 
libeclipse-ui-workbench-java
Architecture: source all
Version: 4.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libeclipse-core-commands-java - Eclipse Commands
 libeclipse-core-databinding-beans-java - Eclipse JFace Data Binding for 
JavaBeans
 libeclipse-core-databinding-java - Eclipse JFace Data Binding
 libeclipse-core-databinding-observable-java - Eclipse JFace Data Binding 
Observables
 libeclipse-core-databinding-property-java - Eclipse JFace Data Binding 
Properties
 libeclipse-e4-core-commands-java - Eclipse e4 core commands
 libeclipse-e4-emf-xpath-java - Eclipse EMF XPath
 libeclipse-e4-ui-bindings-java - Eclipse Bindings Support
 libeclipse-e4-ui-css-core-java - Eclipse CSS Core Support
 libeclipse-e4-ui-css-swt-java - Eclipse CSS SWT Support
 libeclipse-e4-ui-css-swt-theme-java - Eclipse CSS SWT Theme Support
 libeclipse-e4-ui-di-java - Eclipse UI Dependency Injection
 libeclipse-e4-ui-dialogs-java - Eclipse e4 dialogs
 libeclipse-e4-ui-model-workbench-java - Eclipse Workbench Model
 libeclipse-e4-ui-services-java - Eclipse UI Application Services
 libeclipse-e4-ui-swt-gtk-java - Eclipse UI GTK Enhancements
 libeclipse-e4-ui-widgets-java - Eclipse UI Custom widgets
 libeclipse-e4-ui-workbench-addons-swt-java - Eclipse e4 Workbench Add-ons
 libeclipse-e4-ui-workbench-java - Eclipse e4 Workbench
 libeclipse-e4-ui-workbench-renderers-swt-java - Eclipse e4 Workbench SWT 
Renderer
 libeclipse-e4-ui-workbench-swt-java - Eclipse e4 Workbench SWT
 libeclipse-e4-ui-workbench3-java - Bundle for Workbench APIs available in e4
 libeclipse-jface-databinding-java - Eclipse JFace Data Binding for SWT and 
JFace
 libeclipse-jface-java - Eclipse JFace
 libeclipse-ui-forms-java - Eclipse UI forms
 libeclipse-ui-workbench-java - Eclipse Workbench
Closes: 910836
Changes:
 eclipse-platform-ui (4.7.3-3) unstable; urgency=medium
 .

Bug#869639: marked as done (firmware-brcm80211: BroadPwn vulnerability CVE-2017-9417)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 20:13:13 +
with message-id 
and subject line Bug#869639: fixed in firmware-nonfree 20161130-4
has caused the Debian Bug report #869639,
regarding firmware-brcm80211: BroadPwn vulnerability CVE-2017-9417
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.)


-- 
869639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-brcm80211
Version: 0.43
Severity: critical
Tags: security upstream
Justification: root security hole

Dear Maintainer,

CVE-2017-8386 "BroadPwn" has been around for a while.

It seems Debian ships the relevant firmware in this package.

Could I impose on you to ensure that all is as it should be?

Many thanks.
Mark

https://nvd.nist.gov/vuln/detail/CVE-2017-8386
https://security-tracker.debian.org/tracker/CVE-2017-9417
https://packages.debian.org/search?keywords=firmware-brcm80211
http://boosterok.com/blog/broadpwn/

-- System Information:
Debian Release: 8.9
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (1000, 'oldstable'), (500, 
'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: firmware-nonfree
Source-Version: 20161130-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Oct 2018 20:27:06 +0100
Source: firmware-nonfree
Binary: firmware-linux firmware-linux-nonfree firmware-adi firmware-ralink 
firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x 
firmware-brcm80211 firmware-cavium firmware-intelwimax firmware-intel-sound 
firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas 
firmware-misc-nonfree firmware-myricom firmware-netxen firmware-qlogic 
firmware-realtek firmware-samsung firmware-siano firmware-ti-connectivity
Architecture: all source
Version: 20161130-4
Distribution: stretch
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 869639 907320
Description: 
 firmware-adi - Binary firmware for Analog Devices Inc. DSL modem chips (dummmy 
p
 firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips
 firmware-atheros - Binary firmware for Atheros wireless cards
 firmware-bnx2 - Binary firmware for Broadcom NetXtremeII
 firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb
 firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards
 firmware-cavium - Binary firmware for Cavium Ethernet adapters
 firmware-intel-sound - Binary firmware for Intel sound DSPs
 firmware-intelwimax - Binary firmware for Intel WiMAX Connection
 firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and 
pvrusb2 d
 firmware-iwlwifi - Binary firmware for Intel Wireless cards
 firmware-libertas - Binary firmware for Marvell wireless cards
 firmware-linux - Binary firmware for various drivers in the Linux kernel 
(meta-pac
 firmware-linux-nonfree - Binary firmware for various drivers in the Linux 
kernel (meta-pac
 firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel
 firmware-myricom - Binary firmware for Myri-10G Ethernet adapters
 firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 
3100 Se
 firmware-qlogic - Binary firmware for QLogic HBAs
 firmware-ralink - Binary firmware for Ralink wireless cards (dummmy package)
 firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters
 firmware-samsung - Binary firmware for Samsung MFC video codecs
 firmware-siano - Binary firmware for Siano MDTV receivers

Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)

2018-10-24 Thread Bernhard Übelacker

Hello Alex Andreotti,
just tried to reproduce this issue but did not happen inside my unstable amd64 
qemu VM.

Probably you can install an core dump collector like systemd-coredump?

Then you could see the stack where the crash happened by:
  coredumpctl gdb list
  coredumpctl gdb 

And even better would be if you could add the debug symbol repository
described in [1] and install e.g. lightdm-gtk-greeter-dbgsym plus
maybe more dbgsym packages for the shared objects shown in the stack.

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace

Bug#909818: confirm downgrade of fontconfig solves the problem

2018-10-24 Thread Francesco Potortì

I can confirm that downgrading fontconfig and libfontcofig1 solves the
problem.  Unfortunately, the 2.13.0 version is no more available in the
archive, and previous versions are not compatible.  So I had to
recompile them myself.  Here are the packages I just installed on my
amd64 box:

 
 

You can download them, install them with

$ sudo dpkg -i libfontconfig1_2.13.0-5_amd64.deb fontconfig_2.13.0-5_amd64.deb

and prevent upgrading them with

$ sudo aptitude hold fontconfig libfontconfig1

until this bug is solved

-- 
Francesco Potortì (ricercatore)Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR  Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa Skype:  wnlabisti
(entrance 20, 1st floor, room C71) Web:http://fly.isti.cnr.it

Bug#895622: marked as done (php-crypt-chap: build-depends on php-mcrypt which is no more)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 17:36:44 +
with message-id 
and subject line Bug#911722: Removed package(s) from unstable
has caused the Debian Bug report #895622,
regarding php-crypt-chap: build-depends on php-mcrypt which is no more
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.)


-- 
895622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-crypt-chap
Version: 1.5.0-2
Severity: serious

Hi,

php-mcrypt is no longer built, so php-crypt-chap should stop build-depending
on it.

Emilio
--- End Message ---
--- Begin Message ---
Version: 1.5.0-2+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---

Bug#911782: python-cryptography FTBFS: openssl test fails

2018-10-24 Thread Helmut Grohne

Source: python-cryptography
Version: 2.3-1
Severity: serious
Tags: ftbfs

python-cryptography fails to build from source in unstable. The same
version builds fine in testing. This indicates that a dependency (e.g.
openssl) is the cause.

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-cryptography_2.3-1.rbuild.log.gz

| === FAILURES 
===
|  TestOpenSSL.test_openssl_assert_error_on_stack 

| 
| self = 
| 
| def test_openssl_assert_error_on_stack(self):
| b = Binding()
| b.lib.ERR_put_error(
| b.lib.ERR_LIB_EVP,
| b.lib.EVP_F_EVP_ENCRYPTFINAL_EX,
| b.lib.EVP_R_DATA_NOT_MULTIPLE_OF_BLOCK_LENGTH,
| b"",
| -1
| )
| with pytest.raises(InternalError) as exc_info:
| _openssl_assert(b.lib, False)
| 
| error = exc_info.value.err_code[0]
| >   assert error.code == 101183626
| E   AssertionError: assert 337146240L == 101183626
| E+  where 337146240L = _OpenSSLErrorWithText(code=337146240L, lib=20, 
func=391, reason=384, reason_text='error:14187180:SSL 
routines:ssl_do_config:bad value').code
| 
| ../../../tests/hazmat/bindings/test_openssl.py:98: AssertionError
| === warnings summary 
===
...
| = 1 failed, 96853 passed, 4186 skipped, 25 warnings in 443.73 seconds 
==
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-cryptography-2.3/.pybuild/cpython2_2.7_cryptography/build; 
python2.7 -m pytest {dir}/tests/
| dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
| make: *** [debian/rules:17: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#889120: marked as done (php-crypt-chap FTBFS with PHP 7.2)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 17:36:44 +
with message-id 
and subject line Bug#911722: Removed package(s) from unstable
has caused the Debian Bug report #889120,
regarding php-crypt-chap FTBFS with PHP 7.2
to be marked as done.

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

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


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-crypt-chap.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-crypt-chap-1.5.0'
pear run-tests Crypt_CHAP-*/tests
Running 1 tests
FAIL Crypt_CHAP: simple test[Crypt_CHAP-1.5.0/tests/Crypt_CHAP.phpt]
wrote log to "/build/1st/php-crypt-chap-1.5.0/run-tests.log"
TOTAL TIME: 00:00
0 PASSED TESTS
0 SKIPPED TESTS
1 FAILED TESTS:
/build/1st/php-crypt-chap-1.5.0/Crypt_CHAP-1.5.0/tests/Crypt_CHAP.phpt
Some tests failed
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.5.0-2+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---

Bug#910764: openjfx: segmentation fault in GtkNativeMainLoopThread

2018-10-24 Thread Markus Koschany

I believe I have found a way to workaround this issue for the moment. If
I pass -Djdk.gtk.version=2 to PDFsam version 3.3.7 it no longer crashes.
However there is another issue with fontawesomefx, so there is still
some work to do. I think I will forward this issue to the OpenJFX
developers because it looks like a bug in the GTK3 related native libraries.



signature.asc
Description: OpenPGP digital signature

Bug#911780: psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8

2018-10-24 Thread Andreas Beckmann

Package: psk31lx
Version: 2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

lenny had the following binary package (from src:twpsk):

Package: psk31lx
Priority: optional
Section: hamradio
Installed-Size: 148
Maintainer: Joop Stakenborg 
Architecture: i386
Source: twpsk
Version: 2.1+2.2beta1-8
Depends: libc6 (>= 2.7-1), libgcc1 (>= 1:4.2.1), libncurses5 (>= 
5.6+20071006-3), libstdc++6 (>= 4.2.1)
Filename: pool/main/t/twpsk/psk31lx_2.1+2.2beta1-8_i386.deb
Size: 33248
MD5sum: a47956cf6af3d155f797ffc8b4a644b1
SHA1: 3ce698aa6974a1b4b049a7944d1a474e4e3c7b0c
SHA256: 173e0a76cbf0afcbb83f1c0ad4368b816c5acbc8dc459ecccf81a308dd62c674
Description: Soundcard-based ncurses program for operating PSK31
 Psk31lx uses a soundcard to receive and transmit PSK31, an extremely
 narrow band HF-mode. PSK31 is a mode for keyboard QSO's.


while stretch has this one with a lower version number (from src:psk31lx):

Package: psk31lx
Source: psk31lx (2.1-1)
Version: 2.1-1+b1
Installed-Size: 91
Maintainer: Debian Hamradio Maintainers 
Architecture: i386
Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.0), libncurses5 (>= 6), libpulse0 (>= 
0.99.1), libstdc++6 (>= 5), libtinfo5 (>= 6)
Description: PSK31 terminal application with text-based user interface
Homepage: http://wa0eir.bcts.info/psk31lx.html
Description-md5: 55820db20bf58c287b473c1e3b6c6ac7
Tag: hardware::hamradio, hardware::modem, implemented-in::c,
 interface::text-mode, role::program, scope::utility,
 uitoolkit::ncurses, use::chatting
Section: hamradio
Priority: optional
Filename: pool/main/p/psk31lx/psk31lx_2.1-1+b1_i386.deb
Size: 34248
MD5sum: 74882786eba9fdc15634323f36e617d1
SHA256: 8eeeaf4a951c62b424c16e8c76b97e873c2b2b92c8d7d00790c5b6f0cd7d472a


According to
http://snapshot.debian.org/binary/psk31lx/
there is quite a mess of version numbers.

Bumping the source package version to 2.1+really2.1-1 with no further
changes should fix this. This is preferred over adding an epoch.

$ dpkg --compare-versions 2.1+2.2beta1-8 lt 2.1+really2.1-1 && echo lt
lt


Andreas

Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread John Paul Adrian Glaubitz

On 10/24/18 6:42 PM, Oliver Riesener wrote:
> No unetbootin, it’s the stock  stretch netboot   installation.
> initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
> didn’t find kernel modules anymore. The old one before too. 
> It’s a point release problem. Older versions of modules (.udeb ?) seems
> to be from debian repo. 
Are you sure you used a matching kernel image and initrd? Both have to match
their version otherwise it won't work.

I'm creating debian-installer images myself on a regular basis and from my
current knowledge and testing, it's very unlikely that there is a bug in
the kernel and initrd matching.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread Oliver Riesener

No unetbootin, it’s the stock  stretch netboot   installation.
initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
didn’t find kernel modules anymore. The old one before too. 
It’s a point release problem. Older versions of modules (.udeb ?) seems
to be from debian repo. 

> Am 24.10.2018 um 17:26 schrieb John Paul Adrian Glaubitz 
> :
> 
> On 10/24/18 5:15 PM, Oliver Riesener wrote:
>> Debian Stretch 9.5 (stable) kernel 3.16.0-4
>> * no packages matching kernel failed.
> 
> This error usually comes up with installation media created using
> unetbootin. Have you, by any chance, used unetbootin to create your
> installation medium?
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>

Bug#911776: fontconfig: makes Firefox, Gimp, Inkscape occasionally freeze

2018-10-24 Thread Francesco Potortì

Package: fontconfig
Version: 2.13.0-5
Severity: grave

Details are reported in bug #909818

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

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=C:en_GB:en:en_US:it:fr:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fontconfig depends on:
ii  fontconfig-config  2.13.1-1
ii  libc6  2.27-6
pn  libfontconfig1 
ii  libfreetype6   2.8.1-2

fontconfig recommends no packages.

fontconfig suggests no packages.

-- no debconf information

Processed: user debian...@lists.debian.org, unarchiving 678807, usertagging 678807 ...

2018-10-24 Thread Debian Bug Tracking System

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> unarchive 678807
Bug #678807 {Done: Lifeng Sun } [ttf-root-installer] 
ttf-root-installer: post installation fails
Unarchived Bug 678807
> usertags 678807 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 678807 5.18.00-2.3~lenny1
Bug #678807 {Done: Lifeng Sun } [ttf-root-installer] 
ttf-root-installer: post installation fails
Marked as found in versions root-system/5.18.00-2.3~lenny1.
> thanks
Stopping processing here.

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

Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))

2018-10-24 Thread Andrius Merkys

On 10/24/18 1:40 PM, Emmanuel Bourg wrote:
> I've uploaded mojo-executor and string-template-maven-plugin, they are
> awaiting in the NEW queue for the FTP masters approval. Thanks a lot
> Andrius.

Many thanks for reviewing and uploading the packages!

Best,
Andrius

Processed: fixed 907835 in 4.11.1~pre.20180911.5acdd26fdc+dfsg-5

2018-10-24 Thread Debian Bug Tracking System

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

> fixed 907835 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
Bug #907835 {Done: Hans van Kranenburg } [src:xen] newer 
version in stable
Marked as fixed in versions xen/4.11.1~pre.20180911.5acdd26fdc+dfsg-5.
> thanks
Stopping processing here.

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

Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread John Paul Adrian Glaubitz

On 10/24/18 5:15 PM, Oliver Riesener wrote:
> Debian Stretch 9.5 (stable) kernel 3.16.0-4
> * no packages matching kernel failed.

This error usually comes up with installation media created using
unetbootin. Have you, by any chance, used unetbootin to create your
installation medium?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

2018-10-24 Thread Tiziano Zito

Package: pinentry-gnome3
Version: 1.1.0-1+b1
Severity: serious

Hi!

pinentry-gnome3 (but also pinentry-gtk-2) does not open a window anymore to ask 
for a passphrase. If run from terminal it shows:

No Gcr System Prompter available, falling back to curses
OK Pleased to meet you

It was working fine since years. Of the packages pinentry-gnome3 depends on, I 
have only upgraded recently libgpg-error0,  libncursesw6, libtinfo6.
Even downgrading libgpg-error0 to 1.32-1 does not fix the issue.

I am clueless, but willing to help to find the culprit...

Ciao!
Tiziano

PS: not sure it is relevant, but I am not running GNOME, I use fvwm instead. 
Dbus is running.

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

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

Versions of packages pinentry-gnome3 depends on:
ii  gcr  3.28.0-1
ii  libassuan0   2.5.1-2
ii  libc62.27-6
ii  libgcr-base-3-1  3.28.0-1
ii  libglib2.0-0 2.58.1-2
ii  libgpg-error01.32-3
ii  libncursesw6 6.1+20181013-1
ii  libsecret-1-00.18.6-3
ii  libtinfo66.1+20181013-1

Versions of packages pinentry-gnome3 recommends:
pn  dbus-user-session  

Versions of packages pinentry-gnome3 suggests:
ii  pinentry-doc  1.1.0-1

-- no debconf information

Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread Oliver Riesener


A tiresome subject for YEARS.

It has happened again today.


Debian Stretch 9.5 (stable) kernel 3.16.0-4
* no packages matching kernel failed.

Bug#911762: marked as done (trash-cli: FTBFS - segmentation fault during test phase)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 15:04:12 +
with message-id 
and subject line Bug#911762: fixed in trash-cli 0.17.1.14-1
has caused the Debian Bug report #911762,
regarding trash-cli: FTBFS - segmentation fault during test phase
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.)


-- 
911762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trash-cli
Version: 0.12.9.14-2.1
Severity: serious

FTBFS as per attached. sbuild fails too

I'm hoping this is cured by the new upstream version and/or
tightening a python version, and I'm going to attempt to fix
it.

-- System Information:
Debian Release: 9.5
   APT prefers stable
   APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information
$ gbp buildpackage -rfakeroot -us -uc
 dpkg-buildpackage -rfakeroot -us -uc -i -I
dpkg-buildpackage: info: source package trash-cli
dpkg-buildpackage: info: source version 0.12.9.14-3
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Javi Merino 
 dpkg-source -i -I --before-build trash-cli
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python2
   debian/rules override_dh_clean
make[1]: Entering directory '/home/jon/git/debian/trash/trash-cli'
rm -rf trash_cli.egg-info/
make[1]: Leaving directory '/home/jon/git/debian/trash/trash-cli'
 dpkg-source -i -I -b trash-cli
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building trash-cli using existing 
./trash-cli_0.12.9.14.orig.tar.gz
dpkg-source: info: building trash-cli in trash-cli_0.12.9.14-3.debian.tar.xz
dpkg-source: info: building trash-cli in trash-cli_0.12.9.14-3.dsc
 debian/rules build
dh build --with python2
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/trashcli
copying trashcli/fs.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/rm.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/cmds.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/list_mount_points.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/trash.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/__init__.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/fstab.py -> build/lib.linux-x86_64-2.7/trashcli
running build_scripts
creating build/scripts-2.7
copying and adjusting bin/trash-list -> build/scripts-2.7
copying and adjusting bin/trash -> build/scripts-2.7
copying and adjusting bin/trash-put -> build/scripts-2.7
copying and adjusting bin/restore-trash -> build/scripts-2.7
copying and adjusting bin/trash-empty -> build/scripts-2.7
copying and adjusting bin/trash-rm -> build/scripts-2.7
changing mode of build/scripts-2.7/trash-list from 644 to 755
changing mode of build/scripts-2.7/trash from 644 to 755
changing mode of build/scripts-2.7/trash-put from 644 to 755
changing mode of build/scripts-2.7/restore-trash from 644 to 755
changing mode of build/scripts-2.7/trash-empty from 644 to 755
changing mode of build/scripts-2.7/trash-rm from 644 to 755
   debian/rules override_dh_auto_test
make[1]: Entering directory '/home/jon/git/debian/trash/trash-cli'
nosetests
.SS...debian/rules:12: recipe for target 
'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Segmentation fault
make[1]: Leaving directory '/home/jon/git/debian/trash/trash-cli'
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1116:
dpkg-buildpackage -rfakeroot -us -uc -i -I failed
gbp:error: 'debuild -i -I -rfakeroot -us -uc' failed: it exited with 29

--- End Message ---
--- Begin Message ---
Source: trash-cli
Source-Version: 0.17.1.14-1

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

Bug#911680: xserver-xorg-core: X server crashes when loading libglamorgl.so module

2018-10-24 Thread Bernhard Übelacker

Hello Massimo,

Am 24.10.2018 um 15:54 schrieb Massimo MANGHI:
> ... and the new patch will be 
> included in the next upload, is it correct? Am I supposed to take any 
> further action? Something like changing the bug status or applying some 
> extra tag to the bug in order to specify the environment (VirtualBox) 
> where the problem occurs?

I really was just trying to debug the issue,
further actions are up to the maintainers.

Also another user reported a workaround in [1] that
you might have not received by mail.

Kind regards,
Bernhard

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

Processed: Re: lastpass-cli: error: Peer certificate cannot be authenticated with given CA certificates

2018-10-24 Thread Debian Bug Tracking System

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

> affects 911767 lastpass-cli
Bug #911767 [release.debian.org] stable-pu: package 
lastpass-cli/1.0.0-1.2+deb9u1
Added indication that 911767 affects lastpass-cli
> block 898940 by 911767
Bug #898940 {Done: Chris Lamb } [lastpass-cli] lastpass-cli: 
error: Peer certificate cannot be authenticated with given CA certificates
898940 was not blocked by any bugs.
898940 was not blocking any bugs.
Added blocking bug(s) of 898940: 911767
> thanks
Stopping processing here.

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

Bug#898940: lastpass-cli: error: Peer certificate cannot be authenticated with given CA certificates

2018-10-24 Thread Chris Lamb

affects 911767 lastpass-cli
block 898940 by 911767
thanks

Hi,

> error: Peer certificate cannot be authenticated with given CA
> certificates

An request to update the "stable" distribution has been filed
as #911767.


Regards,

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

Bug#907835: newer version in stable

2018-10-24 Thread Antoine Beaupré

On 2018-10-24 13:43:34, Hans van Kranenburg wrote:
> Control: fixed 907835 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
>
> On 9/26/18 4:22 PM, Ian Jackson wrote:
>> Antoine Beaupré writes ("Re: [Pkg-xen-devel] Bug#907835: newer version in 
>> stable"):
>>> It's been two weeks and stable still has a newer version than unstable,
>>> which suffers from four security issues fixed in stable.
>>>
>>> I understand you might have other plans in the long term, but in the
>>> meantime, why not just upload deb9u10 to unstable?
>> 
>> I went to do this but sadly, it no longer builds due to gcc8.  There
>> are upstream patches that could be cherry-picked but it's certainly no
>> longer simply a matter of importing the security update.
>> 
>> I am going to look at these failures since they are blocking my
>> package refactoring work and I expect that as an output I will produce
>> a list of upstream commits to cherry pick, which I will send to this
>> bug.
>
> Xen 4.11 has now transitioned to testing! \o/
>
> So, the weird situation has been resolved.

Great! Thanks everyone! :)

a.

-- 
During times of universal deceit, telling the truth becomes a
revolutionary act.   - Georges Orwell

Bug#911760: lightdm: more info

2018-10-24 Thread Alex Andreotti

Package: lightdm
Version: 1.26.0-3
Followup-For: Bug #911760

Could have something to do with the systemd/libpam upgrade? 
I have another issue with a password prompter (see attachment)
Oct 24 15:42:45 hellspawn gpg-agent[1931]: failed to unprotect the secret key: 
Inappropriate ioctl for device
Oct 24 15:42:45 hellspawn gpg-agent[1931]: failed to read the secret key
Oct 24 15:42:45 hellspawn gpg-agent[1931]: command 'PKDECRYPT' failed: 
Inappropriate ioctl for device 
Oct 24 15:42:45 hellspawn dbus-daemon[1485]: [session uid=1000 pid=1485] 
Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.22' 
(uid=1000 pid=1986 comm="pinentry --display :0 ")
Oct 24 15:42:45 hellspawn dbus-daemon[1485]: [session uid=1000 pid=1485] 
Activated service 'org.gnome.keyring.SystemPrompter' failed: Process 
org.gnome.keyring.SystemPrompter received signal 11
Oct 24 15:42:45 hellspawn gpg-agent[1931]: No Gcr System Prompter available, 
falling back to curses
Oct 24 15:42:45 hellspawn kernel: gcr-prompter[1991]: segfault at 696e6420 ip 
7ff4696c5907 sp 7fff5a80b198 error 4 in 
libc-2.27.so[7ff46958d000+146000]
Oct 24 15:42:45 hellspawn kernel: Code: f9 20 77 1f c5 fd 74 0f c5 fd d7 c1 85 
c0 0f 85 df 00 00 00 48 83 c7 20 83 e1 1f 48 83 e7 e0 eb 36 66 90 83 e1 1f 48 
83 e7 e0  fd 74 0f c5 fd d7 c1 d3 f8 85 c0 74 1b f3 0f bc c0 48 01 f8 48

Bug#911680: xserver-xorg-core: X server crashes when loading libglamorgl.so module (Bug #911680)

2018-10-24 Thread Massimo MANGHI

Hello Bernhard

thank you for taking care of the problem so quickly

On 10/23/18 9:24 PM, Bernhard Übelacker wrote:
> Hello Massimo Manghi,
> just tried to reproduce the issue inside a debian buster amd64 qemu VM.
> I never hit the crash and found you were probably running inside a VirtualBox.
> 

you got it

> Nevertheless with installed debug informations I think the crash shown
> in the Xorg.log points to that location:
> 
> 
> [...]
> 
> glamor/glamor_egl.c:
> 990
> 991 renderer = glGetString(GL_RENDERER);
> 992 if (strstr((const char *)renderer, "llvmpipe")) {
> 993 xf86DrvMsg(scrn->scrnIndex, X_INFO,
> 994"Refusing to try glamor on llvmpipe\n");
> 
> 
> Therefore my guess would be that "glGetString(GL_RENDERER)" returns
> in VirtualBox (or at least that installation) something odd.
> 
> 
> That line originates from this patch that is applied upstream and
> I assume is cherry picked [1] for that debian package version:
> ./debian/patches/08_dont-init-glamor-on-llvmpipe.diff
> 
> Upstream added on top of that another patch [2] to
> avoid a crash that is probably exact that one we see here.
> 

very good, I guess this clarifies the issue and the new patch will be 
included in the next upload, is it correct? Am I supposed to take any 
further action? Something like changing the bug status or applying some 
extra tag to the bug in order to specify the environment (VirtualBox) 
where the problem occurs?

  thank you a lot

  regards

  -- Massimo

Bug#911444: marked as done (python-flask-httpauth-doc: missing Breaks+Replaces: python-flask-httpauth (<< 3.2.4))

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 13:50:01 +
with message-id 
and subject line Bug#911444: fixed in python-flask-httpauth 3.2.4-3
has caused the Debian Bug report #911444,
regarding python-flask-httpauth-doc: missing Breaks+Replaces: 
python-flask-httpauth (<< 3.2.4)
to be marked as done.

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

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


-- 
911444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-flask-httpauth-doc
Version: 3.2.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python-flask-httpauth-doc_3.2.4-1_all.deb ...
  Unpacking python-flask-httpauth-doc (3.2.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-flask-httpauth-doc_3.2.4-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/python-flask-httpauth/examples/basic_auth.py', which is also in 
package python-flask-httpauth 3.2.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-flask-httpauth-doc_3.2.4-1_all.deb


cheers,

Andreas


python-flask-httpauth=3.2.1-1_python-flask-httpauth-doc=3.2.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-flask-httpauth
Source-Version: 3.2.4-3

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated python-flask-httpauth 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Oct 2018 13:27:30 +
Source: python-flask-httpauth
Binary: python-flask-httpauth python3-flask-httpauth python-flask-httpauth-doc
Architecture: source
Version: 3.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Martín Ferrari 
Changed-By: Martín Ferrari 
Description:
 python-flask-httpauth - Basic and Digest HTTP authentication for Flask (Python 
2)
 python-flask-httpauth-doc - Basic and Digest HTTP authentication for Flask 
(documentation)
 python3-flask-httpauth - Basic and Digest HTTP authentication for Flask 
(Python 3)
Closes: 911444
Changes:
 python-flask-httpauth (3.2.4-3) unstable; urgency=medium
 .
   * debian/control: Put the Breaks/Replaces in the proper place; previous
 upload was a mistake.  Closes: #911444.
Checksums-Sha1:
 15014804fcac51f43cd64716ba72cdbd03eb3161 2302 python-flask-httpauth_3.2.4-3.dsc
 0687c061d04bc7ca434cf3efbcaa19015fbd99ab 4868 
python-flask-httpauth_3.2.4-3.debian.tar.xz
 886de7cddf343371ec6985b5e0ea4bd22eab4f7f 8506 
python-flask-httpauth_3.2.4-3_amd64.buildinfo
Checksums-Sha256:
 d1e5022f0117e6a1e8d48704862a57651a13b382c67753932ca49539a17a2c3d 2302 
python-flask-httpauth_3.2.4-3.dsc
 fd83adbb23813088270367873bc63e5430e32ac17dee4e8c9329053cb3b95e4e 4868 
python-flask-httpauth_3.2.4-3.debian.tar.xz
 298c7314808749ef36ee6612ed294d39e67dd1f73f75e11b3665d80bdc6ebf01 8506 
python-flask-httpauth_3.2.4-3_amd64.buildinfo
Files:
 8a5ce13312ff00999e5b0e286fc31239 2302 python optional 
python-flask-httpauth_3.2.4-3.dsc
 e3b0f82e810cb88c2c4cd1fea755dbcf 4868 python optional 
python-flask-httpauth_3.2.4-3.debian.tar.xz
 9cd21b67254eccf9eeb9f27db2fe2d7a 8506 python optional 
python-flask-httpauth_3.2.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlvQdFwACgkQXdjgv5Gj
09rwtA//b0zfUOp9oEX0jbXLN+7KHyz7YfKWjvRAHs5KXHHwoIw6JPRM2x0SwEMR
vWHsf1qw+VFGD2d4ytIFvr3v581+64rMM+RHFWW2AP1Cp3nadK0xZsByUDnVA6N1
XbJHwdESpCUVoNl8uViGAQQ7yL5zmgi4ULsV/2EvgoNHgNHMDHDSRgQnhbu5D2rh
nD8eKoYQl9vOeNucksTLkvy7FkQfNhhhu1JnGq7IIrBrkQbiJMPomgw3gRov+D4g

Bug#911762: trash-cli: FTBFS - segmentation fault during test phase

2018-10-24 Thread Jonathan Dowland

Source: trash-cli
Version: 0.12.9.14-2.1
Severity: serious

FTBFS as per attached. sbuild fails too

I'm hoping this is cured by the new upstream version and/or
tightening a python version, and I'm going to attempt to fix
it.

-- System Information:
Debian Release: 9.5
   APT prefers stable
   APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information
$ gbp buildpackage -rfakeroot -us -uc
 dpkg-buildpackage -rfakeroot -us -uc -i -I
dpkg-buildpackage: info: source package trash-cli
dpkg-buildpackage: info: source version 0.12.9.14-3
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Javi Merino 
 dpkg-source -i -I --before-build trash-cli
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python2
   debian/rules override_dh_clean
make[1]: Entering directory '/home/jon/git/debian/trash/trash-cli'
rm -rf trash_cli.egg-info/
make[1]: Leaving directory '/home/jon/git/debian/trash/trash-cli'
 dpkg-source -i -I -b trash-cli
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building trash-cli using existing 
./trash-cli_0.12.9.14.orig.tar.gz
dpkg-source: info: building trash-cli in trash-cli_0.12.9.14-3.debian.tar.xz
dpkg-source: info: building trash-cli in trash-cli_0.12.9.14-3.dsc
 debian/rules build
dh build --with python2
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/trashcli
copying trashcli/fs.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/rm.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/cmds.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/list_mount_points.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/trash.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/__init__.py -> build/lib.linux-x86_64-2.7/trashcli
copying trashcli/fstab.py -> build/lib.linux-x86_64-2.7/trashcli
running build_scripts
creating build/scripts-2.7
copying and adjusting bin/trash-list -> build/scripts-2.7
copying and adjusting bin/trash -> build/scripts-2.7
copying and adjusting bin/trash-put -> build/scripts-2.7
copying and adjusting bin/restore-trash -> build/scripts-2.7
copying and adjusting bin/trash-empty -> build/scripts-2.7
copying and adjusting bin/trash-rm -> build/scripts-2.7
changing mode of build/scripts-2.7/trash-list from 644 to 755
changing mode of build/scripts-2.7/trash from 644 to 755
changing mode of build/scripts-2.7/trash-put from 644 to 755
changing mode of build/scripts-2.7/restore-trash from 644 to 755
changing mode of build/scripts-2.7/trash-empty from 644 to 755
changing mode of build/scripts-2.7/trash-rm from 644 to 755
   debian/rules override_dh_auto_test
make[1]: Entering directory '/home/jon/git/debian/trash/trash-cli'
nosetests
.SS...debian/rules:12: recipe for target 
'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Segmentation fault
make[1]: Leaving directory '/home/jon/git/debian/trash/trash-cli'
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1116:
dpkg-buildpackage -rfakeroot -us -uc -i -I failed
gbp:error: 'debuild -i -I -rfakeroot -us -uc' failed: it exited with 29

Bug#911444: python-flask-httpauth-doc: missing Breaks+Replaces: python-flask-httpauth (<< 3.2.4)

2018-10-24 Thread Martín Ferrari

On 24/10/18 13:04, Andreas Beckmann wrote:
> Followup-For: Bug #911444
> Control: found -1 3.2.4-2
> 
> Hi,
> 
> you added the B+R to python3-flask-httpauth instead of
> python-flask-httpauth-doc

Oh, ffs. Sorry, I will reupload now


-- 
Martín Ferrari (Tincho)

Bug#894360: marked as done (icedtea-web (build) depends on openjdk-8)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 13:19:17 +
with message-id 
and subject line Bug#894360: fixed in icedtea-web 1.7.1-1
has caused the Debian Bug report #894360,
regarding icedtea-web (build) depends on openjdk-8
to be marked as done.

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

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


-- 
894360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icedtea-web
Version: 1.6.2-3.1
Severity: serious
Tags: buster sid

openjdk-8-jdk is not expected to be part of the buster release.

icedtea-web build depends on openjdk-8 and icedtea-{netx,8-plugin}
have openjdk-8-jre dependencies.
--- End Message ---
--- Begin Message ---
Source: icedtea-web
Source-Version: 1.7.1-1

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated icedtea-web package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 Oct 2018 14:42:28 +0200
Source: icedtea-web
Binary: icedtea-netx
Architecture: source
Version: 1.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 icedtea-netx - NetX - implementation of the Java Network Launching Protocol 
(JNL
Closes: 642901 712292 743922 798946 886109 889448 894360
Changes:
 icedtea-web (1.7.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Vincent Privat ]
   * IcedTea-Web 1.7.1 release (Closes: #886109).
   * Build using default-jdk (Closes: #894360).
   * Add support for openjdk-10.
   * Drop support of browser plugin (deprecated technology).
   * Drop unneeded patches.
   * Fix lintian warnings.
   * Update the copyright file.
 .
   [ Emmanuel Bourg ]
   * No longer integrate icedtea-web with a specific JDK
 (Closes: #743922, #642901, #712292)
   * Merged icedtea-netx-common into icedtea-netx (Closes: #798946)
   * Package transferred to the Java Team.
   * Removed Damien Raude-Morvan from the uploaders (Closes: #889448)
   * Fixed the detection of Java 10+ in the configure script
   * No longer generate debian/control from template files
   * Updated the .desktop files
   * Build with the DH sequencer
   * Use Breaks/Replaces instead of Conflicts/Replaces in debian/control
   * Standards-Version updated to 4.2.1
   * Switch to debhelper level 11
   * Use a secure URL in debian/watch
Checksums-Sha1:
 c93e82e5158c027cd76df0cb42b4134381cf14b6 2018 icedtea-web_1.7.1-1.dsc
 a484daa20cadefe4d4ba2c1e3b28dbb39c986f4b 2074562 icedtea-web_1.7.1.orig.tar.gz
 15b4b4b5a1128254815d46df617956d15326f28b 23736 
icedtea-web_1.7.1-1.debian.tar.xz
 74d94273f7780be4a4a72d04eb75f29b97ea8ff1 11015 
icedtea-web_1.7.1-1_source.buildinfo
Checksums-Sha256:
 3ceb95e6b8869f370e26db57673913bd3ee04321846394f8d3b18573fbc63f8e 2018 
icedtea-web_1.7.1-1.dsc
 c972cefaae1e106fc32be4c553616e71c44da21376fde62e164cb7b052043fad 2074562 
icedtea-web_1.7.1.orig.tar.gz
 08fea71e364057d5354479f498e2a837cb698eb62be2dc360a1d17177729f013 23736 
icedtea-web_1.7.1-1.debian.tar.xz
 6ab67766a011e7cbd601d32ab1de28d62051da101ba88b03cea89ee12e1a1b3e 11015 
icedtea-web_1.7.1-1_source.buildinfo
Files:
 6ba1cdbcd9fe75b35a12ad59754f6fd4 2018 java optional icedtea-web_1.7.1-1.dsc
 f55d3b47c657a3603b05c637ca8a4572 2074562 java optional 
icedtea-web_1.7.1.orig.tar.gz
 f44c54bb652dd147d5b4d088e338b28d 23736 java optional 
icedtea-web_1.7.1-1.debian.tar.xz
 3eb304843fc0b904a3b93595b171caa0 11015 java optional 
icedtea-web_1.7.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlvQa90SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs9+MP/3Fj+5Pf4RC9spBPnM/qk4sKvlBj4dxv
uhh7m8dUqBEuufsaIOMnDFMFuXLEm0t4pP4gYSo4R1jYVnVwzHow9SFsiE/mBXs5
DF5OunIP2kgbJ9GimN3JvqC4ve5niEY0OZWb+y7iZkMHLbUWbHXlSfwiiLLiiFoT
VqVQh4QGHvvgLuJX/citCJroBuZMETMyh1fSDPKeW41D1Uo4Ap0ENYEvb6d8k2BI
NvuZuYuaB/USVzRxd4hgHLJHnaHvEaJSIVxCRF0W71xbRvNpP2ECPJ2M6b6vCZ4m
QUf80yII/1NGGqyTvsw+W6YCE+lL8lZzl0P9ZJhT/GQxQpcjKhRRzt7RxvnV0qwc

Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop

2018-10-24 Thread Alex Andreotti

Package: lightdm
Version: 1.26.0-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

A system upgrade, a list of the packages upgraded should be attached, I don't 
see any relation with lightdm but I could be missing something

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

apt update
apt upgrade
reboot

   * What was the outcome of this action?

lightdm doesn't start, segfault and restart until systemd stop it

   * What outcome did you expect instead?

the usual login dialog

Attached there should be the `journal -xe` segfault, the list of the packages 
installed by the upgrade, the backtrace of a `gdb lighdm --debug` session.
Please let me know how/if I can help with more logs.


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

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

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.10-1
ii  debconf [debconf-2.0]  1.5.69
ii  libaudit1  1:2.8.4-2
ii  libc6  2.27-6
ii  libgcrypt201.8.3-1
ii  libglib2.0-0   2.58.1-2
ii  libpam-systemd 239-10
ii  libpam0g   1.1.8-3.8
ii  libxcb11.13.1-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.5-1
ii  lsb-base   9.20170808

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.8-2
ii  xserver-xephyr   2:1.20.1-5

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
[XDMCPServer]
[VNCServer]


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm
Starting program: /usr/sbin/lightdm --debug --test-mode
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.03s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=2132
[+0.05s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
[+0.07s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.10s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
[+0.12s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.14s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.16s] DEBUG: Registered seat module local
[+0.19s] DEBUG: Registered seat module xremote
[+0.21s] DEBUG: Registered seat module unity
[+0.23s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[New Thread 0x76714700 (LWP 2136)]
[New Thread 0x75f13700 (LWP 2137)]
[New Thread 0x756cc700 (LWP 2138)]
[+0.36s] DEBUG: Monitoring logind for seats
[+0.38s] DEBUG: New seat added from logind: seat0
[+0.40s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.42s] DEBUG: Seat seat0: Starting
[+0.44s] DEBUG: Seat seat0: Creating greeter session
[+0.46s] DEBUG: Seat seat0: Creating display server of type x
[+0.48s] DEBUG: posix_spawn avoided (fd close requested)
[+0.49s] DEBUG: Could not run plymouth --ping: Failed to execute child process 
?plymouth? (No such file or directory)
[+0.51s] DEBUG: Using VT 7
[+0.53s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.55s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.57s] DEBUG: XServer 0: Writing X server authority to 
/var/run/lightdm/root/:0
[+0.59s] DEBUG: XServer 0: Launching X Server
[+0.61s] DEBUG: Launching process 2140: /usr/bin/X :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.63s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.65s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.67s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+0.69s] WARNING: Error getting user list from org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
[+0.73s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.76s] WARNING: Failed to read password database: No such file or directory
[+0.78s] DEBUG: User alex added
[+0.80s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close 
requested)
[+0.91s] DEBUG: Seat seat0

Bug#911103: marked as done (android-platform-dalvik: libandroid-dex-java dependency is no longer built)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 12:48:59 +
with message-id 
and subject line Bug#911103: fixed in android-platform-dalvik 8.1.0+r23-1
has caused the Debian Bug report #911103,
regarding android-platform-dalvik: libandroid-dex-java dependency is no longer 
built
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.)


-- 
911103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-dalvik
Version: 7.0.0+r33-1
Severity: serious
X-Debbugs-CC: saif...@cse.mrt.ac.lk

android-platform-dalvik depends and build-dpeends on
libandroid-dex-java but that package is no longer built by
android-platform-libcore.

This has led to android-sdk-meta being removed from Testing.

The libcore update said:
"Remove `libandroid-dex-java`: Sources are moved to `android-platform-dalvik`"

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: android-platform-dalvik
Source-Version: 8.1.0+r23-1

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

Debian distribution maintenance software
pp.
Kai-Chung Yan  (supplier of updated 
android-platform-dalvik package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 Oct 2018 20:28:49 +0800
Source: android-platform-dalvik
Binary: hprof-conv dalvik-exchange
Architecture: source
Version: 8.1.0+r23-1
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Kai-Chung Yan 
Description:
 dalvik-exchange - Manipulate Dalvik eXchange format and produce dex files
 hprof-conv - HPROF Converter
Closes: 911103
Changes:
 android-platform-dalvik (8.1.0+r23-1) unstable; urgency=medium
 .
   [ Hans-Christoph Steiner ]
   * New upstream release
   * Switch to Salsa
   * Remove get-orig-source
   * Fix missing-notice-file-for-apache-license
 .
   [ Kai-Chung Yan ]
   * Standards-Version => 4.2.1
   * No longer build dmtracedump or dexdump in this package. They have been 
moved
 to android-platform-art.
   * Annotate Multi-Arch on all packages
   * Build hprof-conv on all architectures
   * dalvik-exchange:
 * Use the package upstream version as the JAR version
 * No longer build against dex.jar (Closes: #911103)
 * Fix some literal errors in the package description
 * Install mainDexClassesNoAapt.rules
Checksums-Sha1:
 4171c5f5f542b9e11ab6e11385339b6b9e6a9b40 2351 
android-platform-dalvik_8.1.0+r23-1.dsc
 dea3e423e899b2a0dda6dc5ad9a4d57382f33c6a 673776 
android-platform-dalvik_8.1.0+r23.orig.tar.xz
 01dd05bea113450cac4338fc8b60905e8369ec6f 5608 
android-platform-dalvik_8.1.0+r23-1.debian.tar.xz
 8cfd1bef607f2b742dbc39bb81e5b0b6cd80b3d5 11442 
android-platform-dalvik_8.1.0+r23-1_source.buildinfo
Checksums-Sha256:
 164b4bc0efb6c490c61c0b4678d6094f564cb987ef3084faefdf2eb119348e90 2351 
android-platform-dalvik_8.1.0+r23-1.dsc
 881587dea0750c159cb6c4bf2849ad6020862064e4751fd82582fc3164f7cb12 673776 
android-platform-dalvik_8.1.0+r23.orig.tar.xz
 71aa461b4331d05c81158138e1a604329ba4b69864c71c0498138fe720038d51 5608 
android-platform-dalvik_8.1.0+r23-1.debian.tar.xz
 36f84a55fa0b67dc2503aad6e3c68c1d92eeff6186786eb70f48b0e8f79ff47b 11442 
android-platform-dalvik_8.1.0+r23-1_source.buildinfo
Files:
 b1313eb1378fcb0e289d912c6afd835c 2351 devel optional 
android-platform-dalvik_8.1.0+r23-1.dsc
 dade3e045d6c1cc878d33373ae3094a9 673776 devel optional 
android-platform-dalvik_8.1.0+r23.orig.tar.xz
 161d4ee686e6e83fa9010da00ad2964c 5608 devel optional 
android-platform-dalvik_8.1.0+r23-1.debian.tar.xz
 9822a1284e853e8cb1fdc97812914c96 11442 devel optional 
android-platform-dalvik_8.1.0+r23-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuIoVOt09lz87H/ea3R+riTf+mCUFAlvQZfIACgkQ3R+riTf+
mCXHrhAAvwkwet1rKG7xoYrAiUgh6eXMZhfs02ijrL7KjCwNh+xTzYqPHqXA2kf4
fAE+Q9L37I/Il2Q1WeVzdkE9pF+AF56u9nzCuo0iYkF+g7c3Wl2CJ7V/Qv75Ewm7
YU3iRDhGrGcB4h1o2+rcbAh5r3OMpHpsX+5i7NqJc6apjmzzE4vvDCuyuo4xWe1t
5FjnFBAnfEfMWHGZN4b/OqVMojnJFB5JegIQP0uJHacG1FAuSpBsQQLu3O2sfDJA

Processed: Re: python-flask-httpauth-doc: missing Breaks+Replaces: python-flask-httpauth (<< 3.2.4)

2018-10-24 Thread Debian Bug Tracking System

Processing control commands:

> found -1 3.2.4-2
Bug #911444 {Done: Martín Ferrari } 
[python-flask-httpauth-doc] python-flask-httpauth-doc: missing Breaks+Replaces: 
python-flask-httpauth (<< 3.2.4)
Marked as found in versions python-flask-httpauth/3.2.4-2; no longer marked as 
fixed in versions python-flask-httpauth/3.2.4-2 and reopened.

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

Bug#911444: python-flask-httpauth-doc: missing Breaks+Replaces: python-flask-httpauth (<< 3.2.4)

2018-10-24 Thread Andreas Beckmann

Followup-For: Bug #911444
Control: found -1 3.2.4-2

Hi,

you added the B+R to python3-flask-httpauth instead of
python-flask-httpauth-doc


Andreas

Bug#907835: marked as done (newer version in stable)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 13:43:34 +0200
with message-id 
and subject line Re: Bug#907835: newer version in stable
has caused the Debian Bug report #907835,
regarding newer version in stable
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.)

-- 
907835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xen
Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9
Severity: serious

The version of the Xen packages in unstable and buster is lower than
the one in Debian stretch. That seems highly irregular and will
obviously break upgrades to buster.

The reason this is marked as "serious" is because I consider this a
"severe violation of Debian policy". This would be section 3 of the
Debian policy, although it curiously does not explicitely state that
versions between different suites should be incrementing.

I still consider this a release critical bug and that new upstream
packages should first be uploaded to unstable, unless there is a
security issue (which is the case here) in which case they should be
simultaneously uploaded to both suites.

Thanks,

A.

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Control: fixed 907835 4.11.1~pre.20180911.5acdd26fdc+dfsg-5

On 9/26/18 4:22 PM, Ian Jackson wrote:
> Antoine Beaupré writes ("Re: [Pkg-xen-devel] Bug#907835: newer version in 
> stable"):
>> It's been two weeks and stable still has a newer version than unstable,
>> which suffers from four security issues fixed in stable.
>>
>> I understand you might have other plans in the long term, but in the
>> meantime, why not just upload deb9u10 to unstable?
> 
> I went to do this but sadly, it no longer builds due to gcc8.  There
> are upstream patches that could be cherry-picked but it's certainly no
> longer simply a matter of importing the security update.
> 
> I am going to look at these failures since they are blocking my
> package refactoring work and I expect that as an output I will produce
> a list of upstream commits to cherry pick, which I will send to this
> bug.

Xen 4.11 has now transitioned to testing! \o/

So, the weird situation has been resolved.

Hans--- End Message ---

Bug#892454: marked as done (rlvm: Please use 'pkg-config' to find FreeType 2)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 11:35:31 +
with message-id 
and subject line Bug#892454: fixed in rlvm 0.14-3
has caused the Debian Bug report #892454,
regarding rlvm: Please use 'pkg-config' to find FreeType 2
to be marked as done.

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

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


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

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in rlvm.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: rlvm
Source-Version: 0.14-3

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated rlvm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 Oct 2018 05:21:20 +0800
Source: rlvm
Binary: rlvm
Architecture: source amd64
Version: 0.14-3
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 rlvm   - RealLive virtual machine clone
Closes: 892454
Changes:
 rlvm (0.14-3) unstable; urgency=low
 .
   * Use pkg-config instead of freetype-config (Closes: #892454)
 - Add 003_use_pkg-config_for_freetype2.patch
 - Use local debian/freetype-config which will call pkg-config instead
   - Bump Standards-Version to 4.2.1: nothing needs to be changed.
   - Bump debhelper compat to 10
   - Fix lintian warnings on debian/copyright
Checksums-Sha1:
 528f4249741585961b9803ab8150a9cddb661aaf 2215 rlvm_0.14-3.dsc
 5fe6ff50fe6f1f146acf6c2f2279860cf21f5bd5 12676 rlvm_0.14-3.debian.tar.xz
 4a92632863f802f93448c31ec60c151040a713b8 215224 rlvm-dbgsym_0.14-3_amd64.deb
 2258770a558049e49bf3d6863f3378da8f0899c5 17232 rlvm_0.14-3_amd64.buildinfo
 37364e58246281ba448f7c9af77a09ee4369cb11 699220 rlvm_0.14-3_amd64.deb
Checksums-Sha256:
 6114c96a8dc8584e59d883a1e5a54cd5f0b227f638e24b1bc331210ac9f747e5 2215 
rlvm_0.14-3.dsc
 9920e300b5b44280e04207dbce66637c5fea6e70117c7a6bd2bf01e6a811c297 12676 
rlvm_0.14-3.debian.tar.xz
 f82f073df83c7d4cb0c26a41add83937fcee4869db6c4cf0944547c2c0cc2856 215224 
rlvm-dbgsym_0.14-3_amd64.deb
 17efe8bece7eb98c2bb816d3bb6ae14002a47c78a3d2538c57eccbb95463ec04 17232 
rlvm_0.14-3_amd64.buildinfo
 5d1b4f819ea4c41e9003fb8c316dbd5c5df7ee8419c15a529294a4a43bcdb0cf 699220 
rlvm_0.14-3_amd64.deb
Files:
 b33d250a5819e07f163de37d98a76e58 2215 games optional rlvm_0.14-3.dsc
 7e93bc4b64d22835629240297ae75223 12676 games optional rlvm_0.14-3.debian.tar.xz
 7c70f819ff37da8c3596d21f6e317652 215224 debug optional 
rlvm-dbgsym_0.14-3_amd64.deb
 db076f8d80eb646725547b649336d11a 17232 games optional 
rlvm_0.14-3_amd64.buildinfo
 ec4bb80a5355b6bc7e0eedbd63ff585d 699220 games optional rlvm_0.14-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAlvPk3cTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiHHNEACn+fG4bbkCWl9TMLTTwqY6gkuJSJCS
ICWpQEhxS95w5lAjf4bSXEy3Irv7oEpRodP1eBYnOqBkp5curLN6c5+PAiiIREcF
YhlhSMzpfz7Ut4NIQoBIVcBeHle5CTyFMT2Eoi2s9SKl69yqPj7Uzno8FqhU1jxb
DIP9ZaUeQt+cABPjBTQdi/sTkEx7Hd6Lwy3S4/lJ2HwIvbf49Z7ayICMTybJSgsR
vLNO4hAmr61dyzmVsduHZ+Iv8AFLSfCUa4Z3jbi8tbn+RtVdHsr03IdtIdxhaOPp
bzw90ASpkVEEJBgqr2Zts912aSZdyqsz/ijF5soZim0Tr7HQoVcjwDgoZOA8r1rJ
K1OiUSvDgUPLZ+Ky5yNEMYbcnrNRYRJM+iEOup3Ud5cHKLAuX/VDhMAQW9VuDstT
jlPmtbPGe3emEbLQtFsl43gPzp1rzb9+D1QW778Z/lihT4GeFdTZqbqeeYg59qtg

Bug#911754: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz

2018-10-24 Thread Matthias Klumpp

Am Mi., 24. Okt. 2018 um 12:45 Uhr schrieb Andrey Rahmatullin :
>
> Package: appstream-generator
> Version: 0.7.4-1
> Severity: grave
>
> I've just installed appstream-generator and ran it:
>
> $ appstream-generator
> appstream-generator: symbol lookup error: appstream-generator: undefined
> symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz
>
> So it's either underlinked or some dependency dropped that symbol without
> bumping the soname, in which case please reassign the bug accordingly.

This is because the package wasn't properly rebuilt with the latest
LDC release in the last LDC transition.
A simple package rebuild should fix this issue.

There is another LDC transition pending, which starts when LDC clears
NEW, I'll merge this issue with the transition bug then.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#911754: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz

2018-10-24 Thread Andrey Rahmatullin

Package: appstream-generator
Version: 0.7.4-1
Severity: grave

I've just installed appstream-generator and ran it:

$ appstream-generator
appstream-generator: symbol lookup error: appstream-generator: undefined
symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz

So it's either underlinked or some dependency dropped that symbol without
bumping the soname, in which case please reassign the bug accordingly.



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

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

Versions of packages appstream-generator depends on:
ii  libappstream40.12.3-1
ii  libarchive13 3.2.2-5
ii  libc62.27-6
ii  libcairo21.16.0-1
ii  libcurl3-gnutls  7.61.0-1
ii  libdcontainers0  0.8.0~alpha.9-1
ii  libfontconfig1   2.13.1-1
ii  libfreetype6 2.8.1-2
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglib2.0-0 2.58.1-2
ii  libglibd-2.0-0   2.0.0-1+b1
ii  libjs-highlight.js   9.12.0+dfsg1-4
ii  libjs-jquery-flot0.8.3+dfsg-1
ii  liblmdb0 0.9.22-1
ii  libmustache-d0   0.1.3-3+b1
ii  libpango-1.0-0   1.42.4-3
ii  libphobos2-ldc-shared78  1:1.8.0-3
ii  librsvg2-2   2.40.20-3
ii  libstdx-allocator0   2.77.2-1

Versions of packages appstream-generator recommends:
ii  optipng  0.7.6-1.1

appstream-generator suggests no packages.

-- no debconf information

Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))

2018-10-24 Thread Emmanuel Bourg

Control: tags 911286 + pending
Control: tags 911302 + pending

Le 19/10/2018 à 16:42, Andrius Merkys a écrit :

> updating antlr4 to 4.7 requires two new Debian packages, 
> libmojo-executor-java (ITP #911286) and libstring-template-maven-plugin-java 
> (ITP #911302). I have pushed their packaging to Salsa:
> 
> * https://salsa.debian.org/merkys-guest/mojo-executor
> * https://salsa.debian.org/merkys-guest/string-template-maven-plugin 
> (build-depends on libmojo-executor-java)
> 
> It would be great if you could review and, if possible, sponsor them.

I've uploaded mojo-executor and string-template-maven-plugin, they are
awaiting in the NEW queue for the FTP masters approval. Thanks a lot
Andrius.

Emmanuel Bourg

Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related

2018-10-24 Thread Martin Steigerwald

Dmitry Shachnev - 19.10.18, 17:48:
> Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=400028
> 
> On Fri, Oct 19, 2018 at 11:49:45AM +0200, Martin Steigerwald wrote:
> > Unfortunately Akregator still crashes with Qt 5.11.2 packages.
> > 
> > Maybe heise.de is a quite good way to reproduce it, in case that
> > tracking script stuff is somehow related:
> > 
> > http://www.heise.de/open/news/news-atom.xml
> 
> I have reported this bug to Qt upstream, but they say it is not their
> bug, but a thread safety issue in libkf5webengineviewer5. So I have
> now filed a bug to KDE.

Here further links to upstream bug reports.

Bug which the bug 400028 you marked a duplicate of:

[Bug 371511] kontact/akregator crashes while trying to open a link from 
the
list (middle click)
https://bugs.kde.org/371511

Another upstream bug report:
[akregator] [Bug 397866] akregator crashes when closing the rightmost 
tab
https://bugs.kde.org/397866

Thanks
-- 
Martin

Processed: retitle 910964 to Need to figure out a way to handle multiple protobuf versions during migrations

2018-10-24 Thread Debian Bug Tracking System

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

> retitle 910964 Need to figure out a way to handle multiple protobuf versions 
> during migrations
Bug #910964 [libprotobuf17] Autopkgtest failure: error: cannot find symbol 
public com.google.protobuf.Timestamp
Changed Bug title to 'Need to figure out a way to handle multiple protobuf 
versions during migrations' from 'Autopkgtest failure: error: cannot find 
symbol public com.google.protobuf.Timestamp'.
> thanks
Stopping processing here.

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

Processed: severity of 910964 is important

2018-10-24 Thread Debian Bug Tracking System

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

> severity 910964 important
Bug #910964 [libprotobuf17] Need to figure out a way to handle multiple 
protobuf versions during migrations
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#899529: marked as done (graphite-carbon: Invalid maintainer address pkg-graphite-ma...@lists.alioth.debian.org)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 08:36:28 +
with message-id 
and subject line Bug#899529: fixed in graphite-carbon 1.0.2-1.1
has caused the Debian Bug report #899529,
regarding graphite-carbon: Invalid maintainer address 
pkg-graphite-ma...@lists.alioth.debian.org
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.)


-- 
899529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:graphite-carbon
Version: 1.0.2-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of graphite-carbon,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package graphite-carbon since the list address
pkg-graphite-ma...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-graphite-ma...@lists.alioth.debian.org is 5.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: graphite-carbon
Source-Version: 1.0.2-1.1

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated graphite-carbon 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 23 Oct 2018 14:42:36 +0200
Source: graphite-carbon
Binary: graphite-carbon
Architecture: source all
Version: 1.0.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Graphite Group 
Changed-By: Christoph Martin 
Description:
 graphite-carbon - backend data caching and persistence daemon for Graphite
Closes: 899529
Changes:
 graphite-carbon (1.0.2-1.1) unstable; urgency=medium
 .
   * NMU
   * VCS move to salsa
   * change maintainer to tracker list (closes: #899529)
Checksums-Sha1:
 62e78e5cf8a523c80a0c0ed8c5da7ae922eb9ca0 2085 graphite-carbon_1.0.2-1.1.dsc
 77d27d66449ab32fd888e47a69c9bb259ae3da3e 12840 
graphite-carbon_1.0.2-1.1.debian.tar.xz
 0400bf687797281ee1901f143cff354f09dbc4e8 68556 
graphite-carbon_1.0.2-1.1_all.deb
 cfa3e7269e76043b6608042d0c979b8de911a86c 7324 
graphite-carbon_1.0.2-1.1_amd64.buildinfo
Checksums-Sha256:
 95d6f435bed9d8087d5c0d01ab5052a1d33db18a4cfafea9c71386512a149ea1 2085 
graphite-carbon_1.0.2-1.1.dsc
 cb213eea5ce173846f48d63d7c54e23ddc537291432147962b19c890edbb1db3 12840 
graphite-carbon_1.0.2-1.1.debian.tar.xz
 48be3f9e09f27c08197da2737be6991f680d57c70d06d0942246e4f55eca 68556 
graphite-carbon_1.0.2-1.1_all.deb

Bug#911582: marked as done (emacspeak does'nt work after upgrading emacs)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 08:36:19 +
with message-id 
and subject line Bug#911582: fixed in emacspeak 47.0+dfsg-2~0
has caused the Debian Bug report #911582,
regarding emacspeak does'nt work after upgrading emacs
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
after upgrading emacs in unstable, emacsen-common install script for emacspeak 
exits because flavour emacs is not accepted by script.

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages emacspeak depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.69
ii  emacs  1:25.2+1-11
ii  emacs-lucid [emacs]1:25.2+1-11
ii  make   4.2.1-1.2
ii  perl   5.26.2-7+b1
ii  tcl8.6.0+9
ii  tclx8.48.4.1-2

Versions of packages emacspeak recommends:
ii  emacspeak-espeak-server  47.0+dfsg-1
ii  sox  14.4.2-3

Versions of packages emacspeak suggests:
pn  eflite 
pn  emacspeak-ss   
ii  espeak-ng-espeak [espeak]  1.49.2+dfsg-4
pn  psgml  
pn  w3m-el 
ii  xsltproc   1.1.32-2

-- debconf information:
  shared/emacspeak/groupies:
* shared/emacspeak/port: none
  shared/emacspeak/program: espeak
* shared/emacspeak/device: espeak
  shared/emacspeak/database:
  shared/emacspeak/invalidport:
  shared/emacspeak/rootgroup:
  shared/emacspeak/fake:
  shared/emacspeak/tcl: tcl
  shared/emacspeak/invaliduser:
--- End Message ---
--- Begin Message ---
Source: emacspeak
Source-Version: 47.0+dfsg-2~0

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated emacspeak package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 Oct 2018 09:54:17 +0200
Source: emacspeak
Binary: emacspeak emacspeak-espeak-server
Architecture: source
Version: 47.0+dfsg-2~0
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 emacspeak  - speech output interface to Emacs
 emacspeak-espeak-server - espeak synthesis server for emacspeak
Closes: 911582
Changes:
 emacspeak (47.0+dfsg-2~0) unstable; urgency=medium
 .
   * control: Bump Standards-Version to 4.2.0 (no changes).
   * emacsen-install: Fix byte-compilation with flavor emacs with newer emacs
 version (Closes: Bug#911582).
Checksums-Sha1:
 aa4e1764de8a0e2b5ed2d6777ccaf37577fc1a27 2183 emacspeak_47.0+dfsg-2~0.dsc
 c4b70f92e20f74e916b04b8e2212e2e4b8b6c712 49264 
emacspeak_47.0+dfsg-2~0.debian.tar.xz
Checksums-Sha256:
 e9fd4bc881f27a1fd3b9621d5511a93d474aa568d06fa31fdbdbac81ffc87c42 2183 
emacspeak_47.0+dfsg-2~0.dsc
 990a159094e2d5c3856de58f4e077502500c90318da2b3c591957adb0545301d 49264 
emacspeak_47.0+dfsg-2~0.debian.tar.xz
Files:
 b844dcba0025c0bffeadd64aee9d11d6 2183 editors optional 
emacspeak_47.0+dfsg-2~0.dsc
 d413b7e31ad01d637619d774f0fa2f5a 49264 editors optional 
emacspeak_47.0+dfsg-2~0.debian.tar.xz

-BEGIN PGP SIGNATURE-

Processed: fixed 911697 in 0.47.2-1, found 911697 in 0.48.1-1

2018-10-24 Thread Debian Bug Tracking System

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

> fixed 911697 0.47.2-1
Bug #911697 [meson] meson: varying levels of quote interpretation make it 
impossible to define G_LOG_DOMAIN
Marked as fixed in versions meson/0.47.2-1.
> found 911697 0.48.1-1
Bug #911697 [meson] meson: varying levels of quote interpretation make it 
impossible to define G_LOG_DOMAIN
Marked as found in versions meson/0.48.1-1.
> thanks
Stopping processing here.

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

Processed: tagging 910873

2018-10-24 Thread Debian Bug Tracking System

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

> tags 910873 - patch
Bug #910873 [src:calligra] calligra: FTBFS with poppler 0.69.0-1
Bug #911502 [src:calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Removed tag(s) patch.
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 910873, reassign 911502 to src:calligra, forcibly merging 910873 911502

2018-10-24 Thread Debian Bug Tracking System

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

> tags 910873 - pending
Bug #910873 [src:calligra] calligra: FTBFS with poppler 0.69.0-1
Removed tag(s) pending.
> reassign 911502 src:calligra calligra/1:3.1.0+dfsg-3
Bug #911502 [calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Bug reassigned from package 'calligra' to 'src:calligra'.
No longer marked as found in versions calligra/1:3.1.0+dfsg-3.
Ignoring request to alter fixed versions of bug #911502 to the same values 
previously set
Bug #911502 [src:calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Marked as found in versions calligra/1:3.1.0+dfsg-3.
> forcemerge 910873 911502
Bug #910873 [src:calligra] calligra: FTBFS with poppler 0.69.0-1
Bug #911502 [src:calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Severity set to 'serious' from 'normal'
Added tag(s) ftbfs and patch.
Merged 910873 911502
> thanks
Stopping processing here.

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

Bug#911680: xserver-xorg-core: X server crashes when loading libglamorgl.so module (Bug #911680)

2018-10-24 Thread Dan Zhou


Hi, I had the same crash with xorg-server 2:1.20.1-5 on Virtualbox. I worked 
around it by turning off  the “3D accelaration” option for my VM from 
VirtualBox.

Bug#911582: emacspeak does'nt work after upgrading emacs

2018-10-24 Thread Michelangelo Rodriguez





On Tue, 23 Oct 2018, Samuel Thibault wrote:


Hello,

Michelangelo Rodriguez, le mar. 23 oct. 2018 10:21:09 +0200, a ecrit:

On Tue, 23 Oct 2018, Samuel Thibault wrote:

Michelangelo Rodriguez, le mar. 23 oct. 2018 08:47:03 +0200, a ecrit:

this is the output of dpkg -l \*emacs\*:


I'm still not geting the issue with that list of package.

Could you send the actual output you are getting during package
configuration?

Samuel


Hi, this is the output when i run dpkg-reconfigure emacspeak:
Install emacspeak for emacs
/usr/lib/emacsen-common/packages/install/emacspeak running in /
And that's all.
when i open the script i read that if flavour is emacs it has to exit.
And i think that it happens.


Ah, ok.

Could you try the package at
https://people.debian.org/~sthibault/tmp/emacspeak_47.0+dfsg-2~0_all.deb
?

Samuel


Hi,
Yes, your package installs fine!
Regards,
Michelangelo

Processed (with 2 errors): Re: Bug#911697: at-spi2-core: causes SIGSEGV because of improper quoting of G_LOG_DOMAIN

2018-10-24 Thread Debian Bug Tracking System

Processing control commands:

> retitle -1 meson: varying levels of quote interpretation make it impossible 
> to define G_LOG_DOMAIN
Bug #911697 [src:at-spi2-core] at-spi2-core: varying levels of quote removal 
during meson build process mess up compilation of G_LOG_DOMAIN macro
Changed Bug title to 'meson: varying levels of quote interpretation make it 
impossible to define G_LOG_DOMAIN' from 'at-spi2-core: varying levels of quote 
removal during meson build process mess up compilation of G_LOG_DOMAIN macro'.
> reassign -1 meson
Bug #911697 [src:at-spi2-core] meson: varying levels of quote interpretation 
make it impossible to define G_LOG_DOMAIN
Bug reassigned from package 'src:at-spi2-core' to 'meson'.
No longer marked as found in versions at-spi2-core/2.30.0-2.
Ignoring request to alter fixed versions of bug #911697 to the same values 
previously set
> fixed 0.47.2-1
Unknown command or malformed arguments to command.

> found 0.48.1-1
Unknown command or malformed arguments to command.


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

Bug#911697: at-spi2-core: causes SIGSEGV because of improper quoting of G_LOG_DOMAIN

2018-10-24 Thread Samuel Thibault

Control: retitle -1 meson: varying levels of quote interpretation make it 
impossible to define G_LOG_DOMAIN
Control: reassign -1 meson
Control: fixed 0.47.2-1
Control: found 0.48.1-1

Hello,

Jan Nordholz, le mer. 24 oct. 2018 02:01:56 +0200, a ecrit:
> your build fix actually made it worse: now G_LOG_DOMAIN works properly for
> the gtkdoc-scangobj stuff, but the extra quotes cause literal integer values
> to be inserted wherever you expected a string pointer in the library proper:

Yeeech...

So the issue is in meson itself: it seems one can't get 

compile_args: [ '-DG_LOG_DOMAIN="dbind"' ],

to be correctly interpreted as making G_LOG_DOMAIN #defined to "dbind"
both for the binary compilation and for the documentation generation.

FTR, this was working with meson 0.47.2-1 (see
https://buildd.debian.org/status/fetch.php?pkg=at-spi2-core=amd64=2.30.0-2=1536983011=0
), so I guess it's 0.48.0 which broke this.

Samuel

Bug#911715: marked as done (ros-rosdep FTBFS: flake8 failure)

2018-10-24 Thread Debian Bug Tracking System

Your message dated Wed, 24 Oct 2018 06:18:58 +
with message-id 
and subject line Bug#911715: fixed in ros-rosdep 0.12.2-3
has caused the Debian Bug report #911715,
regarding ros-rosdep FTBFS: flake8 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.)


-- 
911715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-rosdep
Version: 0.12.2-2
Severity: serious
Tags: ftbfs

ros-rosdep fails to build from source in unstable:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ros-rosdep_0.12.2-2.rbuild.log.gz

| ==
| ERROR: test.test_flake8.test_flake8
| --
| Traceback (most recent call last):
|   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
| self.test(*self.arg)
|   File 
"/build/1st/ros-rosdep-0.12.2/.pybuild/cpython2_2.7_rosdep2/build/test/test_flake8.py",
 line 63, in test_flake8
| 'flake8 reported {report.total_errors} errors'
| AttributeError: 'str' object has no attribute 'format_map'
|  >> begin captured stdout << -
| 
| 8 W504 line break after binary operator
| 
| - >> end captured stdout << --
|  >> begin captured logging << 
...
| - >> end captured logging << -
| 
| --
| Ran 151 tests in 24.045s
| 
| FAILED (errors=1)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/ros-rosdep-0.12.2/.pybuild/cpython2_2.7_rosdep2/build; python2.7 -m 
nose -v test
| dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
| make: *** [debian/rules:7: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut
--- End Message ---
--- Begin Message ---
Source: ros-rosdep
Source-Version: 0.12.2-3

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-rosdep 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 Oct 2018 07:56:03 +0200
Source: ros-rosdep
Binary: python-rosdep2 python3-rosdep2
Architecture: source
Version: 0.12.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 python-rosdep2 - rosdep package manager abstraction tool for Robot OS (Python 
2)
 python3-rosdep2 - rosdep package manager abstraction tool for Robot OS (Python 
3)
Closes: 911715
Changes:
 ros-rosdep (0.12.2-3) unstable; urgency=medium
 .
   * Disable flake8 in unit test (Closes: #911715)
   * Bump policy version (no changes)
Checksums-Sha1:
 1f5b32f10776cf67152acbaf7400501f9f7b2aa2 2435 ros-rosdep_0.12.2-3.dsc
 470513abc7d10b256a70c5d861b57b0154235a9e 4344 ros-rosdep_0.12.2-3.debian.tar.xz
 b5f72ff87a41bf617c3353eeaf8399866261b7c3 8674 
ros-rosdep_0.12.2-3_source.buildinfo
Checksums-Sha256:
 0c321a6b4b31af3691dd3082399bda4532f524825cbaa7c8433e5dbcab09b3a6 2435 
ros-rosdep_0.12.2-3.dsc
 44a5d28721c16b1d9851d0f613f56d06721b024f1c9f79248c82535bae1a9694 4344 
ros-rosdep_0.12.2-3.debian.tar.xz
 5acc71f173f7aee36df0b73bb1cbc83c67d8c4665310d27a75947812842a0f08 8674 
ros-rosdep_0.12.2-3_source.buildinfo
Files:
 99d25f727968de88ca37e6352909871a 2435 python optional ros-rosdep_0.12.2-3.dsc
 e2003806810622a0ccd633a8250a3509 4344 python optional 
ros-rosdep_0.12.2-3.debian.tar.xz
 5adf0a262652152d5b7225f46004f01c 8674 python optional 
ros-rosdep_0.12.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlvQCYcUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDNbcw//b5wVDLebh0I/c3X1RGtRF4HItox/

68 matches

Mail list logo