Processed: theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #918090 [src:theano] theano: C-optimized ops fail with "module 
'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"
Added tag(s) patch.

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

Bug#918090: theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"

[Rebecca N. Palmer]

Source: theano
Version: 1.0.2+dfsg-1
Severity: serious
Control: tags -1 patch

Many Theano operations include C code for speed; the compilation process 
uses an undocumented Numpy function to check ABI compatibility.


In Numpy 1.16 (recently added to sid), this function is moved, causing 
all compiles to fail: 
https://ci.debian.net/data/packages/unstable/amd64/t/theano/latest-autopkgtest/log.gz


Fix:

--- a/theano/theano/gof/cc.py
+++ b/theano/theano/gof/cc.py
@@ -1375,12 +1375,8 @@

 # We must always add the numpy ABI version here as
 # DynamicModule always add the include 
-if np.lib.NumpyVersion(np.__version__)<'1.16.0a':
-ndarray_c_version = np.core.multiarray._get_ndarray_c_version()
-else:
-ndarray_c_version = 
np.core._multiarray_umath._get_ndarray_c_version()

 sig.append('NPY_ABI_VERSION=0x%X' %
-   ndarray_c_version)
+   np.core.multiarray._get_ndarray_c_version())
 if c_compiler:
 sig.append('c_compiler_str=' + c_compiler.version_str())

Bug#915765: marked as done (pystaticconfiguration FTBFS: test error)

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 07:19:33 +
with message-id 
and subject line Bug#915765: fixed in pystaticconfiguration 0.10.3-2
has caused the Debian Bug report #915765,
regarding pystaticconfiguration FTBFS: test error
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.)


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

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd 
/build/1st/pystaticconfiguration-0.10.3/.pybuild/cpython2_2.7_staticconf/build; 
python2.7 -m pytest tests
= test session starts ==
platform linux2 -- Python 2.7.15+, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/1st/pystaticconfiguration-0.10.3, inifile:
collected 142 items

tests/config_test.py ...
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
184, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
224, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/hooks.py", line 
284, in __call__
INTERNALERROR> return self._hookexec(self, self.get_hookimpls(), kwargs)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", 
line 67, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", 
line 61, in 
INTERNALERROR> firstresult=hook.spec.opts.get("firstresult") if hook.spec 
else False,
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 208, in _multicall
INTERNALERROR> return outcome.get_result()
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 81, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 187, in _multicall
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
245, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/hooks.py", line 
284, in __call__
INTERNALERROR> return self._hookexec(self, self.get_hookimpls(), kwargs)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", 
line 67, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", 
line 61, in 
INTERNALERROR> firstresult=hook.spec.opts.get("firstresult") if hook.spec 
else False,
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 208, in _multicall
INTERNALERROR> return outcome.get_result()
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 81, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 187, in _multicall
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", 
line 77, in pytest_runtest_protocol
INTERNALERROR> runtestprotocol(item, nextitem=nextitem)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", 
line 86, in runtestprotocol
INTERNALERROR> rep = call_and_report(item, "setup", log)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", 
line 173, in call_and_report
INTERNALERROR> hook = item.ihook
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/nodes.py", line 
118, in ihook
INTERNALERROR> return self.session.gethookproxy(self.fspath)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
418, in gethookproxy
INTERNALERROR> my_conftestmodules = pm._getconftestmodules(fspath)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 409, in 
_getconftestmodules
INTERNALERROR> for parent in directory.realpath().parts():
INTERNALERROR>   File 

Bug#917001: MR

[Sébastien Delafond]

Here is the corresponding MR:

  https://salsa.debian.org/python-team/modules/python-twilio/merge_requests/1

Cheers,

-- 
Seb

Bug#915765: MR

[Sébastien Delafond]

Here is the corresponding MR:

  
https://salsa.debian.org/python-team/modules/pystaticconfiguration/merge_requests/1

Cheers,

-- 
Seb

Bug#918088: autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)"

[Andreas Maus]

Package: autofs-ldap
Version: 5.1.2-4
Severity: grave
Justification: renders package unusable

Good morning.

After the latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) automount
starts but dies immediately after accessing a automounter point.

Automount is configured to authenticate via GSSAPI using system keytab.
After the GSSAPI authentication succeeded, any access to a configure
automount entry causes automount to die with an assertion failure
(followed by an abort()):

root@dagon:~# /usr/sbin/automount -d -f 
Starting automounter version 5.1.2, master map /etc/auto.master
using kernel protocol version 5.03
lookup_nss_read_master: reading master file /etc/auto.master
do_init: parse(sun): init gathered global options: (null)
lookup_read_master: lookup(file): read entry /home
master_do_mount: mounting /home
automount_path_to_fifo: fifo name /var/run/autofs.fifo-home
lookup_nss_read_map: reading map ldap 
ldap:automountmapname=auto.home,cn=badphish,cn=automount,dc=badphish,dc=ypbind,dc=de
parse_server_string: lookup(ldap): Attempting to parse LDAP information from 
string 
"ldap:automountmapname=auto.home,cn=badphish,cn=automount,dc=badphish,dc=ypbind,dc=de".
parse_server_string: lookup(ldap): server "(default)", base dn 
"automountmapname=auto.home,cn=badphish,cn=automount,dc=badphish,dc=ypbind,dc=de"
parse_ldap_config: lookup(ldap): ldap authentication configured with the 
following options:
parse_ldap_config: lookup(ldap): use_tls: 1, tls_required: 0, auth_required: 2, 
sasl_mech: GSSAPI
parse_ldap_config: lookup(ldap): user: (null), secret: unspecified, client 
principal: host/dagon.badphish.ypbind...@badphish.ypbind.de credential cache: 
(null)
do_init: parse(sun): init gathered global options: rw,hard,intr,nosuid
find_server: trying server uri ldap://ipa-1.badphish.ypbind.de
do_bind: lookup(ldap): auth_required: 2, sasl_mech GSSAPI
sasl_do_kinit: initializing kerberos ticket: client principal 
host/dagon.badphish.ypbind...@badphish.ypbind.de
sasl_do_kinit: calling krb5_parse_name on client principal 
host/dagon.badphish.ypbind...@badphish.ypbind.de
sasl_do_kinit: Using tgs name krbtgt/badphish.ypbind...@badphish.ypbind.de
sasl_do_kinit: Kerberos authentication was successful!
sasl_bind_mech: Attempting sasl bind with mechanism GSSAPI
sasl_log_func: GSSAPI client step 1
getuser_func: called with context (nil), id 16385.
sasl_log_func: GSSAPI client step 1
getuser_func: called with context (nil), id 16385.
sasl_log_func: GSSAPI client step 2
sasl_bind_mech: sasl bind with mechanism GSSAPI succeeded
do_bind: lookup(ldap): autofs_sasl_bind returned 0
get_query_dn: lookup(ldap): found query dn 
automountmapname=auto.home,cn=badphish,cn=automount,dc=badphish,dc=ypbind,dc=de
connected to uri ldap://ipa-1.badphish.ypbind.de
read_one_map: lookup(ldap): searching for "(objectclass=automount)" under 
"automountmapname=auto.home,cn=badphish,cn=automount,dc=badphish,dc=ypbind,dc=de"
do_get_entries: lookup(ldap): examining entries
do_get_entries: lookup(ldap): failed to get next entry for query 
(objectclass=automount)
read_one_map: lookup(ldap): done updating map
remount_active_mount: trying to re-connect to mount /home
mounted indirect on /home with timeout 300, freq 75 seconds
remount_active_mount: re-connected to mount /home
st_ready: st_ready(): state = 0 path /home
ghosting enabled
handle_packet: type = 3
handle_packet_missing_indirect: token 3, name maus, request pid 6541
attempting to mount entry /home/maus
lookup_mount: lookup(ldap): looking up maus
do_bind: lookup(ldap): auth_required: 2, sasl_mech GSSAPI
sasl_bind_mech: Attempting sasl bind with mechanism GSSAPI
sasl_log_func: GSSAPI client step 1
getuser_func: called with context (nil), id 16385.
k5_mutex_lock: Received error 22 (Invalid argument)
automount: ../../../../src/include/k5-thread.h:376: k5_mutex_lock: Assertion `r 
== 0' failed.
Aborted (core dumped)

Backtrace of the core dump:

root@dagon:~# gdb /usr/sbin/automount /core
GNU gdb (Debian 8.2-1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/automount...(no debugging symbols found)...done.
[New LWP 6542]
[New LWP 6521]
[New LWP 6522]
[New LWP 6523]
[New LWP 6526]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by 

Processed: gitlab: CVE-2018-20488 CVE-2018-20489 CVE-2018-20490 CVE-2018-20491 CVE-2018-20492 CVE-2018-20493 CVE-2018-20494 CVE-2018-20495 CVE-2018-20496 CVE-2018-20497 CVE-2018-20498 CVE-2018-20499 C

[Debian Bug Tracking System]

Processing control commands:

> found -1 11.6.0+dfsg-1
Bug #918086 [src:gitlab] gitlab: CVE-2018-20488 CVE-2018-20489 CVE-2018-20490 
CVE-2018-20491 CVE-2018-20492 CVE-2018-20493 CVE-2018-20494 CVE-2018-20495 
CVE-2018-20496 CVE-2018-20497 CVE-2018-20498 CVE-2018-20499 CVE-2018-20500 
CVE-2018-20501 CVE-2018-20507
Marked as found in versions gitlab/11.6.0+dfsg-1.

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

Bug#918086: gitlab: CVE-2018-20488 CVE-2018-20489 CVE-2018-20490 CVE-2018-20491 CVE-2018-20492 CVE-2018-20493 CVE-2018-20494 CVE-2018-20495 CVE-2018-20496 CVE-2018-20497 CVE-2018-20498 CVE-2018-20499

[Salvatore Bonaccorso]

Source: gitlab
Version: 11.5.5+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 11.6.0+dfsg-1

Hi,

The following vulnerabilities were published for gitlab, fixed in the
11.6.1, 11.5.6, and 11.4.13 versions, cf [15].

CVE-2018-20488[0]:
Secret CI variable exposure

CVE-2018-20489[1]:
URL rel attribute not set

CVE-2018-20490[2]:
Persistent XSS Autocompletion

CVE-2018-20491[3]:
Persistent XSS wiki in IE browser

CVE-2018-20492[4]:
Todos improper access control

CVE-2018-20493[5]:
Source code disclosure merge request diff

CVE-2018-20494[6]:
Guest user CI job disclosure

CVE-2018-20495[7]:
CI job token LFS error message disclosure

CVE-2018-20496[8]:
Persistent XSS label reference

CVE-2018-20497[9]:
SSRF repository mirroring

CVE-2018-20498[10]:
Improper access control branches and tags

CVE-2018-20499[11]:
SSRF in project imports with LFS

CVE-2018-20500[12]:
Improper access control CI/CD settings

CVE-2018-20501[13]:
Missing authorization control merge requests

CVE-2018-20507[14]:
Missing authentication for Prometheus alert endpoint

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-20488
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20488
[1] https://security-tracker.debian.org/tracker/CVE-2018-20489
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20489
[2] https://security-tracker.debian.org/tracker/CVE-2018-20490
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20490
[3] https://security-tracker.debian.org/tracker/CVE-2018-20491
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20491
[4] https://security-tracker.debian.org/tracker/CVE-2018-20492
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20492
[5] https://security-tracker.debian.org/tracker/CVE-2018-20493
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20493
[6] https://security-tracker.debian.org/tracker/CVE-2018-20494
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20494
[7] https://security-tracker.debian.org/tracker/CVE-2018-20495
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20495
[8] https://security-tracker.debian.org/tracker/CVE-2018-20496
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20496
[9] https://security-tracker.debian.org/tracker/CVE-2018-20497
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20497
[10] https://security-tracker.debian.org/tracker/CVE-2018-20498
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20498
[11] https://security-tracker.debian.org/tracker/CVE-2018-20499
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20499
[12] https://security-tracker.debian.org/tracker/CVE-2018-20500
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20500
[13] https://security-tracker.debian.org/tracker/CVE-2018-20501
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20501
[14] https://security-tracker.debian.org/tracker/CVE-2018-20507
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20507
[15] 
https://about.gitlab.com/2018/12/31/security-release-gitlab-11-dot-6-dot-1-released/
  

Regards,
Salvatore

Bug#917001: marked as done (python3-twilio: twilio missing dependency on requests)

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 06:49:28 +
with message-id 
and subject line Bug#917001: fixed in python-twilio 6.8.2-2
has caused the Debian Bug report #917001,
regarding python3-twilio: twilio missing dependency on requests
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.)


-- 
917001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-twilio
Version: 6.8.2-1
Severity: serious

Hi,

I get an import error on a minimal Debian chroot:

```
In [3]: from twilio.rest import Client as TwilioRestClient
---
ModuleNotFoundError   Traceback (most recent call last)
 in ()
> 1 from twilio.rest import Client as TwilioRestClient

/usr/lib/python3/dist-packages/twilio/rest/__init__.py in ()
 12 from twilio.base.exceptions import TwilioException
 13 from twilio.base.obsolete import obsolete_client
---> 14 from twilio.http.http_client import TwilioHttpClient
 15
 16

/usr/lib/python3/dist-packages/twilio/http/http_client.py in ()
> 1 from requests import Request, Session, hooks
  2
  3 from twilio.http import HttpClient
  4 from twilio.http.response import Response
  5 from twilio.http.request import Request as TwilioRequest

ModuleNotFoundError: No module named 'requests'
```

Please add a dependency on `requests`.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss

Member of United Internet
--- End Message ---
--- Begin Message ---
Source: python-twilio
Source-Version: 6.8.2-2

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated python-twilio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 30 Dec 2018 18:52:12 +0100
Source: python-twilio
Binary: python-twilio python3-twilio
Architecture: source
Version: 6.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sebastien Delafond 
Description:
 python-twilio - Twilio API client and TwiML generator (Python 2)
 python3-twilio - Twilio API client and TwiML generator (Python 3)
Closes: 917001
Changes:
 python-twilio (6.8.2-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Chris Lamb ]
   * Remove new-package-should-not-package-python2-module override as it will 
be marked as 'unused' in the next release (and should have been mentioned in 
the changelog).
 .
   [ Sébastien Delafond ]
   * Add myself to Uploaders
   * Add requests to dependencies (Closes: #917001)
Checksums-Sha1:
 6eb4d1142b263fb4cf1ae0e622da51dc42445e06 2085 python-twilio_6.8.2-2.dsc
 aa09bd3b88e82d5f774d19db21ba436eaca84759 2212 
python-twilio_6.8.2-2.debian.tar.xz
 c8aa6ca87af5f3f8c603b292ea80b1c067cfc479 7929 
python-twilio_6.8.2-2_amd64.buildinfo
Checksums-Sha256:
 baf13c11889d688e65cb33e22f088cd0329a6bcf836b606412d14a52163817ff 2085 
python-twilio_6.8.2-2.dsc
 a81066a09b13d0d66d3936851cd75d85bcd6a931b5a910b7943c2fb560ae2145 2212 
python-twilio_6.8.2-2.debian.tar.xz
 845196359f27caa67f5c021fe0f1250413323977fb387895884e93dad2913a16 7929 
python-twilio_6.8.2-2_amd64.buildinfo
Files:
 0d39b173354c99c657c689adb1412881 2085 python optional python-twilio_6.8.2-2.dsc
 5b1bbcff860fea3578b00b2a6e1d2105 2212 python optional 
python-twilio_6.8.2-2.debian.tar.xz
 8245a00dca2aef91daf12a0250acb93d 7929 python optional 
python-twilio_6.8.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAlwtreQACgkQEL6Jg/PV
nWQkBQgAsQ27fZCrq+tRLtedxwnnE6nmHfrVEN/2qu58iCQNTtl/rNWAibV96jYV

Processed: your mail

[Debian Bug Tracking System]

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

> tag 916805 fixed-upstream pending
Bug #916805 [src:assess-el] assess-el: FTBFS with Emacs 26.1: tests fail
Added tag(s) fixed-upstream and pending.
> thanks
Stopping processing here.

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

Bug#918083: cutesdr FTCBFS: does not pass cross flags to cmake

[Helmut Grohne]

Source: cutesdr
Version: 1.20-2
Severity: serious
Justification: policy 4.6
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

cutesdr fails to cross build from source, because its builds two cmake
projects (one via dh_auto_foo and then the siqs directory explicitly in
override_dh_auto_install) and the latter invocation lacks cross flags.
The easiest way of fixing that is using dh_auto_configure. Doing so is
sufficient to make cutesdr cross buildable. Please consider applying the
attached patch.

I also noticed that cutesdr chains build commands with ";". Doing so is
prohibited by Debian policy section 4.6, thus satisfying serious
severity. My patch fixes this issue as well. Please lower the severity
of this bug if you fix the policy violation independently, but I think
it would be least effort to simply use the patch thus filing only one
bug.

Helmut
diff --minimal -Nru cutesdr-1.20/debian/changelog cutesdr-1.20/debian/changelog
--- cutesdr-1.20/debian/changelog   2018-08-29 06:18:15.0 +0200
+++ cutesdr-1.20/debian/changelog   2019-01-02 22:07:05.0 +0100
@@ -1,3 +1,11 @@
+cutesdr (1.20-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #-1)
+  * Propagate errors from cmake (policy 4.6).
+
+ -- Helmut Grohne   Wed, 02 Jan 2019 22:07:05 +0100
+
 cutesdr (1.20-2) unstable; urgency=medium
 
   * update to svn r75, builds with qt5.11. (Closes:#907226)
diff --minimal -Nru cutesdr-1.20/debian/rules cutesdr-1.20/debian/rules
--- cutesdr-1.20/debian/rules   2018-05-23 05:01:12.0 +0200
+++ cutesdr-1.20/debian/rules   2019-01-02 22:07:05.0 +0100
@@ -8,7 +8,8 @@
 override_dh_auto_install:
dh_auto_install
mkdir siqsbuild
-   (cd siqsbuild ; cmake ../siqs ; make)
+   dh_auto_configure --builddirectory=siqsbuild --sourcedirectory=siqs
+   dh_auto_build --builddirectory=siqsbuild
cp siqsbuild/siqs_ftdi debian/cutesdr/usr/bin/siqs_ftdi
rm -rf siqsbuild
cp CuteSdr debian/cutesdr/usr/bin/CuteSdr

Bug#917576: marked as done (stegosuite: depends on libswt-gtk2 which is no longer built)

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 05:19:56 +
with message-id 
and subject line Bug#917576: fixed in stegosuite 0.8.0-2
has caused the Debian Bug report #917576,
regarding stegosuite: depends on libswt-gtk2 which 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.)


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

jameica depends on libswt-gtk2-4-jni but that package is no longer
built by swt4-gtk.

Please switch to using libswt-gtk-4-jni instead (which uses gtk3
instead of gtk2).

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: stegosuite
Source-Version: 0.8.0-2

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated stegosuite 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, 02 Jan 2019 20:42:14 -0800
Source: stegosuite
Binary: stegosuite
Architecture: source
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 stegosuite - steganography tool to hide information in image files
Closes: 917576
Changes:
 stegosuite (0.8.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Tobias Ilte ]
   * Fix typo in man page
 .
   [ tony mancill ]
   * Update runtime dependency from libswt-gtk2-4-jni to libswt-gtk-4-jni
 (Closes: #917576)
   * Update Vcs- fields in debian/control for Salsa
   * Drop get-orig-source target from debian/rules
   * Use debhelper 11
   * Bump Standards-Version to 4.3.0
Checksums-Sha1:
 435ceeeabc1181439970ba4711ec94550083bae4 2150 stegosuite_0.8.0-2.dsc
 48f07576b866366db46f4924fd46420eea2444e8 6148 stegosuite_0.8.0-2.debian.tar.xz
 53460af09411c82c95454a5f1e4ec17567ea4a33 14184 
stegosuite_0.8.0-2_amd64.buildinfo
Checksums-Sha256:
 78638375837bea684761b90a51e55d953e95fc5671e621cfd8faacdf0f0a2045 2150 
stegosuite_0.8.0-2.dsc
 e96dc6d1e456c7b7c6253feec4ee18ddd8034e3eb73102ed4ff607dee1723205 6148 
stegosuite_0.8.0-2.debian.tar.xz
 cb98b39c5b1c700cd0ff50f631af3329477f765e0ff8a3ce1800e8ea116038c4 14184 
stegosuite_0.8.0-2_amd64.buildinfo
Files:
 0be8fc09c4c04a6090236eafcecbea71 2150 graphics optional stegosuite_0.8.0-2.dsc
 61c48cb83d2244aed6d258b23f8d784e 6148 graphics optional 
stegosuite_0.8.0-2.debian.tar.xz
 5845eb9269d89151af7be5226db05d81 14184 graphics optional 
stegosuite_0.8.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlwtlJ8UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZZihAAye/X8bSxodWYniLYbn1ykBj4d2d3
LHGcXyToyAeuSsmeyMYsof1Z1vKjxTAwrVd8lY74rrMg9ZiPrkR3fbx6PYlb6QQM
Mxht29fjrel4Hs6rWe8IT8s9eAoLo2xY+Wp06hR7059omIjB24OGLkbhj7S3cuCJ
zyIWRuOHUx2/Ivs+9fvmKnZrt6Qriw58fwsi9ySwVYZKbUfg9AswTMLsNo7Y1uXH
LMQVI6qrregZ/CuQ2TI0Pimjm9a9o+UKd3M7Im7TcJip8lx2OuJFX9JKQA49cOvR
sC+eF0LiBTeUy9hTl5EEDz7MWb0AUwLi9Ck9mj4A/EnBpLoJfXOvca3ssHOSTMim
TQjbjK49SHEGTzZAta6sxgd3aTemM9KZZQ1yhYS2NU+4nCvBswo5SK0JGaszyfkb
1crKPb89onoz+n8h8Fv+Z840J8mNu5D0hrPN2yDdp6P5Co7K5E9+u+6u4CyTsALl
hbgRikilqkUmMnazpmQZf1+NHdvlb9Bdl1aruVyBMFVawaztsyqyOVe/tjyxC68m
aJOkpjVvYE7QAW+0lbTDY98GBrETbUuglq4pAvlFYQSGU5MjxMtw7azlTzB6mkA/
rkEwbIy2AmUnxtOwTyYpdVhz7NuszbMfeajF0x/OkbW7SeJHlgFlDm89Zjzghn2E
l9huG7MmoAOgcIM=
=1yDr
-END PGP SIGNATURE End Message ---

Bug#916548: marked as done (python3.7: Version constraint in pyzo breaks is too strict)

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 04:04:49 +
with message-id 
and subject line Bug#916548: fixed in python3.7 3.7.2-1
has caused the Debian Bug report #916548,
regarding python3.7: Version constraint in pyzo breaks is too strict
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.)


-- 
916548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3.7
Version: 3.7.2~rc1-1
Severity: important

The following packages have unmet dependencies:
 python3.7 : Breaks: pyzo (< 4.6) but 4.4.3-1.1 is to be installed

The Breaks should be lowered to
  pyzo (<< 4.4.3-1.1~)
--- End Message ---
--- Begin Message ---
Source: python3.7
Source-Version: 3.7.2-1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Jan 2019 03:55:40 +0100
Source: python3.7
Binary: python3.7 python3.7-venv libpython3.7-stdlib python3.7-minimal 
libpython3.7-minimal libpython3.7 python3.7-examples python3.7-dev 
libpython3.7-dev libpython3.7-testsuite idle-python3.7 python3.7-doc 
python3.7-dbg libpython3.7-dbg
Architecture: source
Version: 3.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.7 - IDE for Python (v3.7) using Tkinter
 libpython3.7 - Shared Python runtime library (version 3.7)
 libpython3.7-dbg - Debug Build of the Python Interpreter (version 3.7)
 libpython3.7-dev - Header files and a static library for Python (v3.7)
 libpython3.7-minimal - Minimal subset of the Python language (version 3.7)
 libpython3.7-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.7-testsuite - Testsuite for the Python standard library (v3.7)
 python3.7  - Interactive high-level object-oriented language (version 3.7)
 python3.7-dbg - Debug Build of the Python Interpreter (version 3.7)
 python3.7-dev - Header files and a static library for Python (v3.7)
 python3.7-doc - Documentation for the high-level object-oriented language 
Python
 python3.7-examples - Examples for the Python language (v3.7)
 python3.7-minimal - Minimal subset of the Python language (version 3.7)
 python3.7-venv - Interactive high-level object-oriented language (pyvenv 
binary, v
Closes: 916548
Changes:
 python3.7 (3.7.2-1) unstable; urgency=medium
 .
   * Python 3.7.2 release.
   * Revert the link optimization changes which appeared after the
 release candidate.
   * Make the build compatible with sphinx 1.6.x.
   * Loosen the pyzo break. Closes: #916548.
Checksums-Sha1:
 ee42e7280e30a5075885727c5945e9469a7f43e0 3439 python3.7_3.7.2-1.dsc
 c3dc6928516bcb934cf4740461044c79c7c35494 17042320 python3.7_3.7.2.orig.tar.xz
 9ed8f8cee84c70fdd759e48801bfeb91ba08d3bb 209616 python3.7_3.7.2-1.debian.tar.xz
 bf67c514b8c9ed9da2e409a7c86ac7982754dbab 9740 
python3.7_3.7.2-1_source.buildinfo
Checksums-Sha256:
 68b50972f8cc623fe07098052281660f9c4008062844c4a90a529b950f06db0b 3439 
python3.7_3.7.2-1.dsc
 d83fe8ce51b1bb48bbcf0550fd265b9a75cdfdfa93f916f9e700aef8444bf1bb 17042320 
python3.7_3.7.2.orig.tar.xz
 c553b625ffe97438a6f178c0579a0d4cb3670fc763b6a7173d66317d828b7a94 209616 
python3.7_3.7.2-1.debian.tar.xz
 4251ab0c54ff7c63deb88b7639c48fd7df4feb416e5a89e9e787b1e83ef84533 9740 
python3.7_3.7.2-1_source.buildinfo
Files:
 744514fa9efdce55f1d1d514271ab17b 3439 python optional python3.7_3.7.2-1.dsc
 df6ec36011808205beda239c72f947cb 17042320 python optional 
python3.7_3.7.2.orig.tar.xz
 ca9df7454c97d6e10c3516c828f5 209616 python optional 
python3.7_3.7.2-1.debian.tar.xz
 466f2333d4f71b442d4d5cde5afacb74 9740 python optional 
python3.7_3.7.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlwteksQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9amjEADOWRWtZ343TitPH6TdGpC3fUo1Tr1/hBdi

Bug#918079: pandas: FTBFS: B-D on python-nbsphinx which is no longer installable nor built any more

[Thorsten Glaser]

Source: pandas
Version: 0.23.3-1
Severity: serious

See #917418 for “python-nbsphinx (0.4.1+ds-1) is not installable”.

src:nbsphinx (0.4.1+ds-3) now only builds the py3k package.

python-nbsphinx (= 0.3.5+ds-1) is installable and usable, but no
longer in Debian, so please move to python3-nbsphinx instead.

Bug#906688: marked as done (ruby-netrc: FTBFS in buster/sid (test_missing_environment fails))

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 02:43:47 +
with message-id 
and subject line Bug#906688: fixed in ruby-netrc 0.11.0-2
has caused the Debian Bug report #906688,
regarding ruby-netrc: FTBFS in buster/sid (test_missing_environment fails)
to be marked as done.

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

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


-- 
906688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-netrc
Version: 0.11.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

TestNetrc#test_multi_without_default = 0.00 s = .
TestNetrc#test_set = 0.00 s = .
TestNetrc#test_missing_environment = 0.00 s = F
TestNetrc#test_permission_error = 0.00 s = .
TestNetrc#test_save = 0.00 s = .
TestNetrc#test_entry_splat = 0.00 s = .
TestNetrc#test_get_missing = DEPRECATED: Use assert_nil if expecting nil from 
/<>/test/test_netrc.rb:169. This will fail in Minitest 6.
0.00 s = .
TestNetrc#test_netrc_environment_variable = 0.00 s = .
TestNetrc#test_add_get = 0.00 s = .
TestNetrc#test_add_newlineless = 0.00 s = .
TestNetrc#test_permission_error_windows = 0.00 s = .
TestNetrc#test_multi_with_default = 0.00 s = .
TestNetrc#test_allow_permissive_netrc_file_option = 0.00 s = .
TestNetrc#test_write_entry = 0.00 s = .
TestNetrc#test_parse_file = 0.00 s = .
TestNetrc#test_with_default = 0.00 s = .
TestNetrc#test_entry_implicit_splat = 0.00 s = .
TestNetrc#test_missing_file = 0.00 s = .
TestNetrc#test_parse_empty = 0.00 s = .
TestNetrc#test_set_get = 0.00 s = .
TestNetrc#test_password_file = 0.00 s = .
TestNetrc#test_add = 0.00 s = .
TestNetrc#test_login_file = 0.00 s = .

Finished in 0.022940s, 1787.2391 runs/s, 2571.8807 assertions/s.

  1) Failure:
TestNetrc#test_missing_environment [/<>/test/test_netrc.rb:203]:
--- expected
+++ actual
@@ -1,2 +1 @@
-# encoding: ASCII-8BIT
-"/<>/.netrc"
+"/build/.netrc"


41 runs, 59 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_lex.rb" 
"test/test_netrc.rb" "test/test_parse.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-netrc returned 
exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The above build was made with sbuild and schroot, under a user called "buildd" 
having
/build as its home directory.

Note: This does not happen in reproducible builds, but I don't know why.
Apparently, this happens every time, in any way it's built (sbuild or by hand),
as far as the build directory is different than the HOME directory.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby-netrc
Source-Version: 0.11.0-2

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated ruby-netrc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Jan 2019 10:51:18 +0900
Source: ruby-netrc
Binary: ruby-netrc
Architecture: source
Version: 0.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Hideki 

Bug#918077: python-meep-mpich2 fails to install, postinst script looks for wrong package name.

[peter green]

Package: python-meep-lam4
Version: 1.7.0-2
Severity: serious

https://piuparts.debian.org/sid/fail/python-meep-lam4_1.7.0-2.log

  Setting up python-meep-lam4 (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-lam4 (--configure):
   installed python-meep-lam4 package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.28-4) ...
  Errors were encountered while processing:
   python-meep-lam4
  E: Sub-process /usr/bin/dpkg returned an error code (1)



After some investigating it looks like this was caused by failing to update the 
package name in the postinst script
when copying the python changes from the plain meep source package to the 
meep-lam4 source package. The prerm
script also seems to suffer from a similar issue.

A debdiff fixing that is attatched, no intent to NMU.



diff -Nru meep-lam4-1.7.0/debian/changelog meep-lam4-1.7.0/debian/changelog
--- meep-lam4-1.7.0/debian/changelog2018-12-25 15:30:09.0 +
+++ meep-lam4-1.7.0/debian/changelog2019-01-03 02:10:44.0 +
@@ -1,3 +1,9 @@
+meep-lam4 (1.7.0-2+rpi1) buster-staging; urgency=medium
+
+  * Fix postinst and prerm scripts for python-meep-mpich2 to use correct 
package name.
+
+ -- Peter Michael Green   Thu, 03 Jan 2019 02:10:44 
+
+
 meep-lam4 (1.7.0-2) unstable; urgency=medium
 
   * upload to unstable
diff -Nru meep-lam4-1.7.0/debian/python-meep-lam4.postinst 
meep-lam4-1.7.0/debian/python-meep-lam4.postinst
--- meep-lam4-1.7.0/debian/python-meep-lam4.postinst2018-12-23 
11:39:19.0 +
+++ meep-lam4-1.7.0/debian/python-meep-lam4.postinst2019-01-03 
02:10:44.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pycompile >/dev/null 2>&1; then
-  pycompile -p python-meep
+  pycompile -p python-meep-lam4
 fi
 
 #DEBHELPER#
diff -Nru meep-lam4-1.7.0/debian/python-meep-lam4.prerm 
meep-lam4-1.7.0/debian/python-meep-lam4.prerm
--- meep-lam4-1.7.0/debian/python-meep-lam4.prerm   2018-12-23 
11:39:19.0 +
+++ meep-lam4-1.7.0/debian/python-meep-lam4.prerm   2019-01-03 
02:10:44.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pyclean >/dev/null 2>&1; then
-  pyclean -p python-meep 
+  pyclean -p python-meep-lam4
 else
   dpkg -L python-meep | grep \.py$ | while read file
   do  

Bug#816640: Bug #816640 in ruby-eventmachine marked as pending

[Hideki Yamane]

Hi,

On Fri, 16 Feb 2018 13:48:16 + z...@debian.org wrote:
> Bug #816640 in ruby-eventmachine reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below, and you can check the diff of the fix at:
> 
> https://salsa.debian.org/ruby-team/ruby-eventmachine/commit/a752744e504c657cc43044df98881b6713d6bd65
> 
> 
> Blacklist another "network"-needing test. Closes: #816640

 Is there any reason not upload to the repository?
 It would be nice to fix this FTBFS :)


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#883778: problems building guile-2.0 on armel

[Rob Browning]

Kurt Roeckx  writes:

> I've enabled guile-2.0 and 2.2 again on armel yesterday, and it
> seems to build without issues now.

Nice!  And thanks much.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#918074: python-meep-mpich2 fails to install, postinst script looks for wrong package name.

[peter green]

Package: python-meep-mpich2
Version: 1.7.0-2
Severity: serious

https://piuparts.debian.org/sid/fail/python-meep-mpich2_1.7.0-2.log


Setting up python-meep-mpich2 (1.7.0-2) ...
   dpkg-query: package 'python-meep' is not installed
   Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
   Traceback (most recent call last):
 File "/usr/bin/pycompile", line 289, in 
   main()
 File "/usr/bin/pycompile", line 262, in main
   options.force, options.optimize, e_patterns)
 File "/usr/bin/pycompile", line 154, in compile
   for fn, versions_to_compile in filter_files(files, e_patterns, versions):
 File "/usr/bin/pycompile", line 109, in filter_files
   for fn in files:
 File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
   for fn in files:
 File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
   for fn in files:
 File "/usr/share/python/debpython/files.py", line 69, in filter_public
   for fn in files:
 File "/usr/share/python/debpython/files.py", line 53, in from_package
   raise Exception("cannot get content of %s" % package_name)
   Exception: cannot get content of python-meep
   dpkg: error processing package python-meep-mpich2 (--configure):
installed python-meep-mpich2 package post-installation script subprocess 
returned error exit status 1
   Processing triggers for libc-bin (2.28-4) ...
   Errors were encountered while processing:
python-meep-mpich2
   E: Sub-process /usr/bin/dpkg returned an error code (1)

After some investigating it looks like this was caused by failing to update the 
package name in the postinst script when copying the python changes from the 
plain meep source package to the meep-mpich2 source package. The prerm script 
also seems to suffer from a similar issue.

While working on the above issues I also discovered that the clean target did 
not clean up properly, so I fixed that too.

A debdiff fixing that is attatched, no intent to NMU.


diff -Nru meep-mpich2-1.7.0/debian/changelog meep-mpich2-1.7.0/debian/changelog
--- meep-mpich2-1.7.0/debian/changelog  2018-12-25 15:29:02.0 +
+++ meep-mpich2-1.7.0/debian/changelog  2019-01-03 01:21:28.0 +
@@ -1,3 +1,9 @@
+meep-mpich2 (1.7.0-2+rpi1) buster-staging; urgency=medium
+
+  * Fix postinst script for python-meep-mpich2 to use correct package name.
+
+ -- Peter Michael Green   Thu, 03 Jan 2019 01:21:28 
+
+
 meep-mpich2 (1.7.0-2) unstable; urgency=medium
 
   * upload to unstable
diff -Nru meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst 
meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst
--- meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst2018-12-23 
11:41:15.0 +
+++ meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst2019-01-03 
01:19:17.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pycompile >/dev/null 2>&1; then
-  pycompile -p python-meep
+  pycompile -p python-meep-mpich2
 fi
 
 #DEBHELPER#
diff -Nru meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm 
meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm
--- meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm   2018-12-23 
11:41:15.0 +
+++ meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm   2019-01-03 
01:21:28.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pyclean >/dev/null 2>&1; then
-  pyclean -p python-meep 
+  pyclean -p python-meep-mpich2
 else
   dpkg -L python-meep | grep \.py$ | while read file
   do  
diff -Nru meep-mpich2-1.7.0/debian/rules meep-mpich2-1.7.0/debian/rules
--- meep-mpich2-1.7.0/debian/rules  2018-12-23 15:24:08.0 +
+++ meep-mpich2-1.7.0/debian/rules  2019-01-03 01:21:28.0 +
@@ -50,6 +50,7 @@
rm -f meep_mpi.pc
rm -f src/libmeep_mpi.la
dh_clean
+   rm -f scheme/meep_enum_renames.i scheme/meep_renames.i 
scheme/meep_swig_bug_workaround.i scheme/meep_wrap.cxx src/sphere-quad.h 
src/step_generic_stride1.cpp
 
 override_dh_auto_test:
echo ${arch}

Bug#918068: sagemath: still not building on unstable :-(

[Julian Gilbey]

Package: sagemath
Version: 8.4-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Thanks for fixing the build dependencies!

Unfortunately the build of 8.4-3 is now failing on the buildds :-(

I presume you realise this, but letting you know just in case you
don't.

Best wishes,

   Julian

Bug#918057: marked as done (gnucash: FTBFS: test suite failure)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 23:04:43 +
with message-id 
and subject line Bug#918057: fixed in gnucash 1:3.4-1
has caused the Debian Bug report #918057,
regarding gnucash: FTBFS: test suite 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.)


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

Gnucash has a test suite problem. There is a log here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnucash.html

showing:
[pass] line:641, test: dual amount column, grand totals available
[fail] line:644, test: dual amount column, first transaction correct
transaction.scm/display options
 -> expected: ("01/03/18" "$103 income" "Root.Asset.Bank" "$103.00" "$103.00")
 -> obtained: ("01/03/20" "$103 income" "Root.Asset.Bank" "$103.00" "$103.00")

This is an other log showing it:
https://buildd.debian.org/status/fetch.php?pkg=gnucash=armel=1%3A3.3-2=1546423068=0


Kurt
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:3.4-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnucash package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Jan 2019 08:51:54 +1100
Source: gnucash
Binary: gnucash gnucash-common python3-gnucash
Architecture: source all amd64
Version: 1:3.4-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gnucash- personal and small-business financial-accounting software
 gnucash-common - common files for the financial-accounting software Gnucash
 python3-gnucash - Gnucash interface for Python
Closes: 918057 918059
Changes:
 gnucash (1:3.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #918059).
   * New patch to fix "test-transaction" (Closes: #918057).
Checksums-Sha1:
 bb73ecba3c4301dd4351349a279d1e0715662b86 2398 gnucash_3.4-1.dsc
 a6f2e59d492cbd0f61ea87f9dcae168339f1de96 9440224 gnucash_3.4.orig.tar.xz
 ab6d0d0152b3a20106daf4b3c7c861c601106d28 37028 gnucash_3.4-1.debian.tar.xz
 e7cf4094c02ae21e7fd47e8ceab85f6bb419591f 5126836 gnucash-common_3.4-1_all.deb
 71b2a943fb7634b2b65c32bf372fba5672f395d7 20772656 
gnucash-dbgsym_3.4-1_amd64.deb
 48e9a702765a2531263b9878806c54266e9b4c38 18823 gnucash_3.4-1_amd64.buildinfo
 f6586382dcbf5b355e87525046bb1b6bc2a2d9d3 4451336 gnucash_3.4-1_amd64.deb
 be43ee4993b355c614e845b5731a40099d543d8b 766572 
python3-gnucash-dbgsym_3.4-1_amd64.deb
 2de13b58a0a100aca93af6b8abef2acc77747f6e 306704 python3-gnucash_3.4-1_amd64.deb
Checksums-Sha256:
 fc42b666acc117829513e92acee8390cefb18b40187776de3f04939a6fb83bf0 2398 
gnucash_3.4-1.dsc
 6018b554ff3851aa16bcf2700251eb3698c1d1cfab6e5d84eb6a4de5937d7194 9440224 
gnucash_3.4.orig.tar.xz
 96711237c5fc8a346b64e8601ed37be545cf5cc8033522d564cf5fc906d37994 37028 
gnucash_3.4-1.debian.tar.xz
 73dee915d0a86cf2028c219b69de1696cdded5a54863a9e1e3fe683160fe7c51 5126836 
gnucash-common_3.4-1_all.deb
 de00fd0a0d07fe1202de72a117a37d4ef45225a59ea3e1f4048567a33dd89752 20772656 
gnucash-dbgsym_3.4-1_amd64.deb
 cce5b9cea39541668d8dd9489366f396205cdd6ceed7f1a1e810ef92627d0c1a 18823 
gnucash_3.4-1_amd64.buildinfo
 e543a3f044c409ba4cf1fed88b38bb53b56512d04845d528856c481685311871 4451336 
gnucash_3.4-1_amd64.deb
 63c453acf191a44cd3598b0b48c46482ff8565c9beca014b22faf7f6969344da 766572 
python3-gnucash-dbgsym_3.4-1_amd64.deb
 407a3e9795d4f2f5dd526578806950d4f4667217dc1c99a71c1c664505e25d2a 306704 
python3-gnucash_3.4-1_amd64.deb
Files:
 46595b6da220f3616c6efe92fb3f7cbf 2398 gnome optional gnucash_3.4-1.dsc
 06bfe2523e2f11a58a82b81b8db3cb07 9440224 gnome optional gnucash_3.4.orig.tar.xz
 9b51933550a10f7465a9a8dbb444fbc7 37028 gnome optional 
gnucash_3.4-1.debian.tar.xz
 be085b65d42047ad6fcb78473146a43c 5126836 gnome optional 
gnucash-common_3.4-1_all.deb
 845955e659e3c35625db9a3f2894635e 20772656 debug optional 

Bug#913604: Please downgrade [Lack of login storage API]

[Simon Valiquette]

Package: firefox-esr
Version: 60.3.0esr-1~deb9u1
Followup-For: Bug #913604


Bernie Elbourn wrote:

> Hello,
>
> I am not maintainer. Just regular "Joe" trying to get to grips with why
> firefox updates have stopped due to apt-listbugs.
>
> I have sympathy with the sentiment ..
>
> "By implementing the nsiLoginStorage API, this lets the users choose a
> single password manager they want to use and integrate it with Firefox."
>
>.. may I gently suggest it is not really a serious Debian bug. These are:

While I understand your point, my understanding is that it is a regression
after Debian Stable (Stretch) was released and that is worked at least in
Firefox 56. A feature regression within Debian Stable usually shouldn't
be marked only as 'wishlist' or 'minor', especially if no workaround is
provided.

Unless of course it was already broken when Debian Stable was released,
in which case 'serious' is way too high, but I don't think so.

It would be interesting to know in which version exactly it stoped working,
as if it only stopped from version 60.3.0esr-1~deb9u1, then it should
definitely be tagged as a security-upgrade regression.

At least the current bug level will make it noticed for Buster and give an
opportunity to provide at least another way to provide a similar feature,
an perhaps even an upgrade path from Debian-oldstable (Jessie).

That said, I wouldn't be against downgrading it to important, especially
as this regression don't seems to be written in the changelog (as required
in the Debian Policy if done on purpose or knowingly). But having it at an
higher level than 'normal' is necessary IMHO if it is a Debian-stable
regression (a problem that was far less common when maintaining of the
original version was still possible).

Have a nice day,

Simon Valiquette


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 9.5
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1), LANGUAGE=fr_CA 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#906859: xul-ext-dom-inspector no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Wed, Oct 03, 2018 at 05:19:49PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Sep 08, 2018 at 03:12:40PM +0800, Paul Wise wrote:
> > On Tue, 21 Aug 2018 21:11:16 +0300 Adrian Bunk wrote:
> > 
> > > Package: xul-ext-dom-inspector
> > > 
> > > XUL addons are no longer supported.
> > 
> > The native Firefox developer tools are almost a replacement,
> > so I think this package can just be removed from Debian.
> 
> David, agreed to remove?

I've filed a removal bug now.

Cheers,
Moritz

Bug#906868: xul-ext-toggle-proxy no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Wed, Sep 26, 2018 at 06:42:31PM +0200, Sascha Girrulat wrote:
> Hi,
> 
> would be ok for me.

I've filed a removal bug now.

Cheers,
Moritz

Bug#906832: xul-ext-kwallet5 no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Wed, Oct 03, 2018 at 05:20:23PM +0200, Moritz Mühlenhoff wrote:
> On Tue, Aug 21, 2018 at 07:53:52PM +0300, Adrian Bunk wrote:
> > On Tue, Aug 21, 2018 at 07:11:59PM +0300, Adrian Bunk wrote:
> > > Package: xul-ext-kwallet5
> > > Version: 1.0-2
> > > Severity: serious
> > > 
> > > XUL addons are no longer supported.
> > 
> > If it is confirmed that this package works with thunderbird 60,
> > it might be an option to change the dependency to only thunderbird.
> 
> addons.thunderbird.net only lists it as compatible to versions
> up to 49.
> 
> Shall we remove xul-ext-kwallet5 from the archive?

No objections in three months, filed a removal bug.

Cheers,
Moritz

Bug#918061: Should ckermit be removed?

[Moritz Muehlenhoff]

Package: ckermit
Severity: serious

Should ckermit be removed from the archive?
- Hasn't seen a maintainer upload in almost six years
- Multiple RC bugs at this point

Cheers,
Moritz

Processed: bug 918057 is forwarded to https://bugs.gnucash.org/show_bug.cgi?id=797008

[Debian Bug Tracking System]

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

> forwarded 918057 https://bugs.gnucash.org/show_bug.cgi?id=797008
Bug #918057 [src:gnucash] gnucash: FTBFS: test suite failure
Set Bug forwarded-to-address to 
'https://bugs.gnucash.org/show_bug.cgi?id=797008'.
> thanks
Stopping processing here.

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

Bug#918057: Bug #918057 in gnucash marked as pending

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/gnucash/commit/8c3f299ab109932ae3048d3fbffbb96b527e2f19


New patch to fix "test-transaction" (Closes: #918057).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918057

Processed: Bug #918057 in gnucash marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918057 [src:gnucash] gnucash: FTBFS: test suite failure
Added tag(s) pending.

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

Processed: affects 915151

[Debian Bug Tracking System]

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

> affects 915151 src:lbzip2
Bug #915151 [gnulib] gnulib does not work with glibc/2.28
Bug #915171 [gnulib] lbzip2 FTBFS with glibc 2.28
Added indication that 915151 affects src:lbzip2
Added indication that 915171 affects src:lbzip2
> thanks
Stopping processing here.

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

Bug#918060: iwyu FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

[Adrian Bunk]

Source: iwyu
Version: 7.0-1
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/fetch.php?pkg=iwyu=armel=7.0-2=1545913678=0

...
/usr/bin/c++   -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 
-w -ffunction-sections -fdata-sections  -Wl,-z,relro  -Wl,-rpath-link,  -Wl,-O3 
-Wl,--gc-sections CMakeFiles/include-what-you-use.dir/iwyu.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_ast_util.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_cache.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_driver.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_getopt.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_globals.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_include_picker.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_lexer_utils.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_location_util.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_output.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_path_util.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_preprocessor.cc.o 
CMakeFiles/include-what-you-use.dir/iwyu_verrs.cc.o  -o 
bin/include-what-you-use -Wl,-rpath,"\$ORIGIN/../lib:/usr/lib/llvm-7/lib" 
-lpthread /usr/lib/llvm-7/lib/libclangBasic.a /usr/lib/llvm-7/lib/libclangLex.a 
/usr/lib/llvm-7/lib/libclangAST.a /usr/lib/llvm-7/lib/libclangSema.a 
/usr/lib/llvm-7/lib/libclangFrontend.a /usr/lib/llvm-7/lib/libclangDriver.a 
/usr/lib/llvm-7/lib/libclangParse.a /usr/lib/llvm-7/lib/libclangSerialization.a 
/usr/lib/llvm-7/lib/libclangSema.a /usr/lib/llvm-7/lib/libclangAnalysis.a 
/usr/lib/llvm-7/lib/libclangEdit.a /usr/lib/llvm-7/lib/libclangAST.a 
/usr/lib/llvm-7/lib/libclangLex.a /usr/lib/llvm-7/lib/libclangBasic.a 
/usr/lib/llvm-7/lib/libLLVM-7.so.1 
/usr/bin/ld: 
/usr/lib/llvm-7/lib/libclangFrontend.a(SerializedDiagnosticReader.cpp.o): 
undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'
/usr/bin/ld: //usr/lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: 
DSO missing from command line
collect2: error: ld returned 1 exit status
make[4]: *** [CMakeFiles/include-what-you-use.dir/build.make:282: 
bin/include-what-you-use] Error 1


Fix:

--- debian/rules.old2019-01-02 21:28:52.105189952 +
+++ debian/rules2019-01-02 21:29:17.129189713 +
@@ -13,6 +13,10 @@
ADDITIONAL_CXX_FLAGS += -mxgot
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel))
+   export DEB_LDFLAGS_MAINT_APPEND = -latomic
+endif
+
 %:
dh $@ --buildsystem=cmake --builddirectory=$(TARGET_BUILD)
 

Processed: lbzip2 copies the files at build time from gnulib

[Debian Bug Tracking System]

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

> reassign 915171 gnulib
Bug #915171 [src:lbzip2] lbzip2 FTBFS with glibc 2.28
Bug reassigned from package 'src:lbzip2' to 'gnulib'.
No longer marked as found in versions lbzip2/2.5-2.
Ignoring request to alter fixed versions of bug #915171 to the same values 
previously set
> notforwarded 915171
Bug #915171 [gnulib] lbzip2 FTBFS with glibc 2.28
Unset Bug forwarded-to-address
> forcemerge 915151 915171
Bug #915151 [gnulib] gnulib does not work with glibc/2.28
Bug #915151 [gnulib] gnulib does not work with glibc/2.28
Added tag(s) sid, patch, and buster.
Bug #915171 [gnulib] lbzip2 FTBFS with glibc 2.28
Removed indication that 915171 affects src:lbzip2
Marked as found in versions gnulib/20140202+stable-3.
Merged 915151 915171
> thanks
Stopping processing here.

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

Bug#917717: marked as done (pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 21:34:19 +
with message-id 
and subject line Bug#917717: fixed in pylint-django 2.0.5-1
has caused the Debian Bug report #917717,
regarding pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i 
python{version} -p 3.7 returned exit code 13
to be marked as done.

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

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


-- 
917717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint-django
Version: 2.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONDONTWRITEBYTECODE=1 
> PYTHONPATH=. {interpreter} pylint_django/tests/test_func.py" dh_auto_test
> I: pybuild base:217: PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3.7 
> pylint_django/tests/test_func.py
> = test session starts 
> ==
> platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
> rootdir: /<>, inifile:
> collected 0 items / 1 errors
> 
>  ERRORS 
> 
> __ ERROR collecting pylint_django/tests/test_func.py 
> ___
> ImportError while importing test module 
> '/<>/pylint_django/tests/test_func.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> pylint_django/__init__.py:6: in 
> from pylint_django import plugin
> pylint_django/plugin.py:5: in 
> from pylint_django.checkers import register_checkers
> pylint_django/checkers/__init__.py:3: in 
> from pylint_django.checkers.models import ModelChecker
> pylint_django/checkers/models.py:11: in 
> from pylint_django.utils import node_is_subclass, PY3
> pylint_django/utils.py:4: in 
> from astroid.util import YES
> E   ImportError: cannot import name 'YES' from 'astroid.util' 
> (/usr/lib/python3/dist-packages/astroid/util.py)
> !!! Interrupted: 1 errors during collection 
> 
> === 1 error in 0.07 seconds 
> 
> E: pybuild pybuild:338: test: plugin custom failed with: exit code=2: 
> PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3.7 
> pylint_django/tests/test_func.py
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned 
> exit code 13

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/pylint-django_2.0.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: pylint-django
Source-Version: 2.0.5-1

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

Debian distribution maintenance software
pp.
Joseph Herlant  (supplier of updated pylint-django 
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, 02 Jan 2019 12:54:41 -0800
Source: pylint-django
Binary: python3-pylint-django
Architecture: source
Version: 2.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Joseph Herlant 
Description:
 python3-pylint-django - Pylint plugin for analysing code using Django (Python 
3)
Closes: 917717
Changes:
 pylint-django (2.0.5-1) unstable; urgency=medium
 .
   * New upstream version 2.0.5 (Closes: #917717).
   * Add the new factory-boy dependency.
   * d/control: bump standards to 4.3.0. No further change needed.
   * Adding a d/upstream/metadata file to be DEP-12 compliant.
   * Add -v to the test command as recommended 

Bug#918054: [Debichem-devel] Bug#918054: elkcode: frequent test hangs

[Michael Banck]

Hi,

On Wed, Jan 02, 2019 at 10:36:48PM +0200, Adrian Bunk wrote:
> Source: elkcode
> Version: 5.2.14-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/package.php?p=elkcode=sid
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elkcode.html
> 
> Tests seems to frequently hang, with no clear pattern which test
> or which architecture (amd64 built on the buildd but hangs in
> reproducible).

Yeah, I noticed, but I didn't get around to dig into it yet.  I thought
I'd had to checkout one of the porter boxes but if you say it sometimes
hangs on amd64 as well, I will try to reproduce locally.


Michael

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

[Adrian Bunk]

On Wed, Jan 02, 2019 at 09:56:51PM +0100, Gregor Riepl wrote:
> >> That, or the fix wasn't enough.
> > 
> > Works for me.
> 
> Odd.
> 
> > What failure are you getting, and what is the contents
> > of /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc ?
> 
> I'm getting the same pthread detection error as reported in the bug.

The pthread detection error is just part of a huge log file that gets 
dumped when cmake fails, with contents mostly unrelated to the problem.

In your build log, what are the lines *before*
  ==> CMakeCache.txt <==
?

> Contents:
> 
> $ cat /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc
> prefix=/usr
> exec_prefix=${prefix}
> libdir=${prefix}/lib/x86_64-linux-gnu
> sharedlibdir=${prefix}/lib/x86_64-linux-gnu
> includedir=${prefix}/include/polyclipping
> 
> Name: polyclipping
> Description: polygon clipping library
> Version:
> 
> Requires:
> Libs: -L${libdir} -L${sharedlibdir} -lpolyclipping
> Cflags: -I${includedir}

Looks OK to me.

cu
Adrian

-- 

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

Bug#883778: problems building guile-2.0 on armel

[Kurt Roeckx]

I've enabled guile-2.0 and 2.2 again on armel yesterday, and it
seems to build without issues now.

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

[Gregor Riepl]

>> That, or the fix wasn't enough.
> 
> Works for me.

Odd.

> What failure are you getting, and what is the contents
> of /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc ?

I'm getting the same pthread detection error as reported in the bug.

Contents:

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc
prefix=/usr
exec_prefix=${prefix}
libdir=${prefix}/lib/x86_64-linux-gnu
sharedlibdir=${prefix}/lib/x86_64-linux-gnu
includedir=${prefix}/include/polyclipping

Name: polyclipping
Description: polygon clipping library
Version:

Requires:
Libs: -L${libdir} -L${sharedlibdir} -lpolyclipping
Cflags: -I${includedir}

Bug#918057: gnucash: FTBFS: test suite failure

[Kurt Roeckx]

Source: gnucash
Version: 1:3.3-2
Severity: serious

Gnucash has a test suite problem. There is a log here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnucash.html

showing:
[pass] line:641, test: dual amount column, grand totals available
[fail] line:644, test: dual amount column, first transaction correct
transaction.scm/display options
 -> expected: ("01/03/18" "$103 income" "Root.Asset.Bank" "$103.00" "$103.00")
 -> obtained: ("01/03/20" "$103 income" "Root.Asset.Bank" "$103.00" "$103.00")

This is an other log showing it:
https://buildd.debian.org/status/fetch.php?pkg=gnucash=armel=1%3A3.3-2=1546423068=0


Kurt

Bug#918055: gnss-sdr FTBFS: test failures on most architectures

[Adrian Bunk]

Source: gnss-sdr
Version: 0.0.10-2
Severity: serious
Tags: ftbfs

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

At first sight I would sort the test failures as follows:

Randomly:
  6 - trk_test (Timeout/SEGFAULT)

arm64 and armhf on arm64 hw (problem in the NEON code?):
  1 - flowgraph_test (Timeout)
  2 - gnss_block_test (Timeout)
  5 - acq_test (Timeout)

big endian:
  3 - gnuradio_block_test (Failed)
  5 - acq_test (Failed)

s390x additionally (perhaps due to 64bit big endian):
  2 - gnss_block_test (Failed)

No actual debugging done, so part of the guesses above might be wrong.

Bug#918054: elkcode: frequent test hangs

[Adrian Bunk]

Source: elkcode
Version: 5.2.14-1
Severity: serious
Tags: ftbfs

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

Tests seems to frequently hang, with no clear pattern which test
or which architecture (amd64 built on the buildd but hangs in
reproducible).

Bug#918053: elk-lapw is missing dependency on openmpi-bin

[Adrian Bunk]

Package: elk-lapw
Version: 4.0.15-2
Severity: serious

Found at https://bugs.launchpad.net/ubuntu/+source/elkcode/+bug/1416296
and reproduced.

Bug#918052: python-ltfatpy FTBFS: TestPsech.test_exceptions failure

[Adrian Bunk]

Source: python-ltfatpy
Version: 1.0.12-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=python-ltfatpy=sid

...
=== FAILURES ===
__ TestPsech.test_exceptions ___

self = 

def test_exceptions(self):
mess = "\nException TypeError should be raised with declaration "
mess += "psech(10.2)\n"
self.assertRaises(TypeError, psech, 10.2, mess)
mess = "\nException TypeError should be raised with declaration "
mess += "psech(10,(1,1))\n"
>   self.assertRaises(TypeError, psech, 10, (1, 1))

ltfatpy/tests/fourier/test_psech.py:93: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def psech(L, tfr=None, s=None, **kwargs):
"""Sampled, periodized hyperbolic secant

- Usage:

| ``(g, tfr) = psech(L)``
| ``(g, tfr) = psech(L, tfr)``
| ``(g, tfr) = psech(L, s=...)``

- Input parameters:

:param int L: length of vector.
:param float tfr: ratio between time and frequency support.
:param int s: number of samples (equivalent to :math:`tfr=s^2/L`)

- Output parameters:

:returns: ``(g, tfr)``
:rtype: tuple
:var numpy.ndarray g: periodized hyperbolic cosine
:var float tfr: calculated ratio between time and frequency support

``psech(L,tfr)`` computes samples of a periodized hyperbolic secant.
The function returns a regular sampling of the periodization
of the function :math:`sech(\pi\cdot x)`

The returned function has norm equal to 1.

The parameter **tfr** determines the ratio between the effective support
of **g** and the effective support of the DFT of **g**. If **tfr** > 1
then **g** has a wider support than the DFT of **g**.

``psech(L)`` does the same setting than **tfr** = 1.

``psech(L,s)`` returns a hyperbolic secant with an effective support of
**s** samples. This means that approx. 96% of the energy or 74% or the
area under the graph is contained within **s** samples. This is
equivalent to ``psech(L,s^2/L)``.

``(g,tfr) = psech( ... )`` returns the time-to-frequency support ratio.
This is useful if you did not specify it (i.e. used the **s** input
format).

The function is whole-point even.  This implies that
``fft(psech(L,tfr))`` is real for any **L** and **tfr**.

If this function is used to generate a window for a Gabor frame, then
the window giving the smallest frame bound ratio is generated by
``psech(L,a*M/L)``.

- Examples:

This example creates a ``psech`` function, and demonstrates that it
is its own Discrete Fourier Transform:

>>> import numpy as np
>>> import numpy.linalg as nla
>>> g = psech(128)[0] # DFT invariance: Should be close to zero.
>>> diff = nla.norm(g-np.fft.fft(g)/np.sqrt(128))
>>> np.abs(diff) < 10e-10
True

.. seealso:: :func:`~ltfatpy.fourier.pgauss.pgauss`, :func:`pbspline`,
:func:`pherm`

- References:
:cite:`jast02-1`
"""
if not isinstance(L, six.integer_types):
raise TypeError('L must be an integer')

if s is not None:
if not isinstance(s, six.integer_types):
raise TypeError('s must be an integer')
tfr = float(s**2 / L)
elif tfr is None:
tfr = 1

safe = 12
g = np.zeros(L)
sqrtl = np.sqrt(L)
w = tfr

# Outside the interval [-safe,safe] then sech(pi*x) is numerically zero.
nk = np.ceil(safe / np.sqrt(L / np.sqrt(w)))

lr = np.arange(L)
>   for k in np.arange(-nk, nk+1):
E   ValueError: The truth value of an array with more than one element is 
ambiguous. Use a.any() or a.all()

ltfatpy/fourier/psech.py:157: ValueError
...
= 1 failed, 138 passed, 291 warnings in 59.44 seconds ==
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7_ltfatpy/build; python3.7 -m pytest 
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned 
exit code 13
make[1]: *** [debian/rules:15: override_dh_auto_test] Error 25

Processed: tagging 917635

[Debian Bug Tracking System]

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

> tags 917635 + buster sid
Bug #917635 [elkcode] elkcode FTBFS, undefined reference to 
xc_f90_mgga_x_tb09_set_par_
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#917788: marked as done (libmedc11: Overwrites a file from libmedc1v5)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 19:35:38 +
with message-id 
and subject line Bug#917788: fixed in med-fichier 4.0.0+repack-5
has caused the Debian Bug report #917788,
regarding libmedc11: Overwrites a file from libmedc1v5
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.)


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

Dear Maintainer,

While trying to update freecad I run into the following broken apt
state:

Preparing to unpack .../libmedc11_4.0.0+repack-3_amd64.deb ...
Unpacking libmedc11:amd64 (4.0.0+repack-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libmedc11_4.0.0+repack-3_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libmedC.so.11.0.0', which is 
also in package libmedc1v5:amd64 4.0.0+repack-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libmedc11_4.0.0+repack-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've followed the solution given in this post [1] to fix it. It is also
suggested that a line such as 'Conflict: libmedc1v5' be added to the
control file.

 [1]: https://askubuntu.com/a/433510


Thanks a lot,
Rock

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

Kernel: Linux 4.19.0-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)
LSM: AppArmor: enabled

Versions of packages libmedc11 depends on:
ii  libc62.28-3
ii  libgcc1  1:8.2.0-13
iu  libhdf5-openmpi-103  1.10.4+repack-4
ii  libopenmpi3  3.1.3-6
ii  libstdc++6   8.2.0-13

libmedc11 recommends no packages.

Versions of packages libmedc11 suggests:
pn  libmed-doc
pn  libmed-tools  

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD
--- End Message ---
--- Begin Message ---
Source: med-fichier
Source-Version: 4.0.0+repack-5

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated med-fichier 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, 02 Jan 2019 19:42:17 +0100
Source: med-fichier
Binary: libmed-dev libmed-doc libmed-tools libmed11 libmedc-dev libmedc11 
libmedimport-dev libmedimport0v5 python-med python3-med
Architecture: source
Version: 4.0.0+repack-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Gilles Filippini 
Description:
 libmed-dev - Development files for libmed
 libmed-doc - Documentation for the MED-fichier library
 libmed-tools - Runtime tools to handle MED files
 libmed11   - Library to exchange meshed data (Fortran version)
 libmedc-dev - Development files for libmedc
 libmedc11  - Library to exchange meshed data (C version)
 libmedimport-dev - Development files for libmedimport0
 libmedimport0v5 - Library to import old version files
 python-med - python API for MED-fichier
 python3-med - python3 API for MED-fichier
Closes: 917788
Changes:
 med-fichier (4.0.0+repack-5) unstable; urgency=medium
 .
   * Drop debian/source/lintian-overrides; these lintian tags were removed
 in 2012
   * libmedc?11: Breaks / Replaces libmedc?1v5 (= 4.0.0+repack-1)
 (Closes: #917788)
Checksums-Sha1:
 0809c584450271503b367b550373dcf01d39e94d 2567 med-fichier_4.0.0+repack-5.dsc
 58e7fba3b04d12f6407d801ea0b4b8d70db9718d 12772 
med-fichier_4.0.0+repack-5.debian.tar.xz
 ca602c16eb45a3368836f1dccafab55e80876d91 8472 
med-fichier_4.0.0+repack-5_source.buildinfo
Checksums-Sha256:
 00b60820c354a657320ffe52dcde3c69ab62c446f749be9b8f78acf98b225339 2567 
med-fichier_4.0.0+repack-5.dsc
 

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

[Adrian Bunk]

On Wed, Jan 02, 2019 at 05:28:13PM +0100, Gregor Riepl wrote:
> 
> >> I will look into the issue.
> >> If you have any idea why it might be occurring, please share.
> > 
> > The actual error is in #917057, which was already correctly marked as 
> > affecting src:cura-engine.
> 
> I'm positive that the problem is more complex than that, because I already
> committed and tested the fix for #917057 and I still get an error.
> 
> That, or the fix wasn't enough.

Works for me.

What failure are you getting, and what is the contents
of /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc ?

cu
Adrian

-- 

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

Bug#917837: RM: clutter-gesture -- ROM; dead upstream

[Ying-Chun Liu (PaulLiu)]

Package: ftp.debian.org
Severity: wishlist


Dear ftp-master,


Please remove clutter-gesture. It is dead upstream.

I don't have time to check if clutter/clutter-gesture-action.h from
libclutter-1.0-dev is the replacement for same functionality. But since
clutter-gesture losts its upstream source repo we can remove this from
Debian to prevent people using it in the future.

Currently there's no reverse denpendencies in Debian.


Yours,

Paul

Bug#917771: marked as done (python-pywebview: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 17:19:51 +
with message-id 
and subject line Bug#917771: fixed in python-pywebview 2.2.1+dfsg-2
has caused the Debian Bug report #917771,
regarding python-pywebview: Incomplete debian/copyright?
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.)


-- 
917771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pywebview
Version: 2.2.1+dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jochen Sprickerhof , 
ftpmas...@debian.org

Hi,

I just ACCEPTed python-pywebview from NEW but noticed it was missing 
attribution in debian/copyright for at least examples/todos/README.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.

(Please also clarify in debian/rules why you disable the testsuite
there.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-pywebview
Source-Version: 2.2.1+dfsg-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated python-pywebview 
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, 02 Jan 2019 17:49:46 +0100
Source: python-pywebview
Binary: python3-pywebview
Architecture: source
Version: 2.2.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Jochen Sprickerhof 
Description:
 python3-pywebview - Build GUI for your Python program with JavaScript, HTML, 
and CSS
Closes: 917771
Changes:
 python-pywebview (2.2.1+dfsg-2) unstable; urgency=medium
 .
   * Add comment for disabled tests
   * Add missing copyrights.
 Thanks to Chris Lamb (Closes: #917771)
Checksums-Sha1:
 07842c446dd2a64019674d4caf7e5abf86c2ed59 2182 python-pywebview_2.2.1+dfsg-2.dsc
 bc051eea519f6fed9be7ced42916bcd16edd1e6c 2904 
python-pywebview_2.2.1+dfsg-2.debian.tar.xz
 f74101122871617ee9f5bf22f84d16b6fce008a5 9306 
python-pywebview_2.2.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 fe465a8af13227ecd8296112f24826c111824b674c733836f500be2c7eed14f3 2182 
python-pywebview_2.2.1+dfsg-2.dsc
 32519432a31214f4fe6093402f22ca5345045ac039fe086242603a6b3c0123ed 2904 
python-pywebview_2.2.1+dfsg-2.debian.tar.xz
 30d0e7a3649b9d6f41bd79cc156c0b1dea0d14438f810afa52206b587bbf7b45 9306 
python-pywebview_2.2.1+dfsg-2_source.buildinfo
Files:
 3c7410c7be8cb1c25940e75172f32c3b 2182 python optional 
python-pywebview_2.2.1+dfsg-2.dsc
 dc5e1b30db63b51fd21d6edda1782b0b 2904 python optional 
python-pywebview_2.2.1+dfsg-2.debian.tar.xz
 aacbaff98dd7a2050487eabafd19791c 9306 python optional 
python-pywebview_2.2.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlws67oUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDNT8w//ebES6GDlZpyY9ItA/AycDWBMdmnG
Nmp3Rr1tyv2DoEF8mKSj470iL1Rtvrwl+9w4/zK5d6jpLOt9Ud09J4Dia13DnKLB
eBQ9Gu+Ua1jCveIJBtwN4Cih4iFNN1YiTWK+S1z/9+ZzxL62Usjox2B5bprF/YDG
HvcVyBtwcZ3neZrUCPW8Q10IxtoKZYV/958AirXDma2xD8oQstRDiExzR/9RvHiL
DrYAaZF6x3QdJH3TeRHC72PJHCNnhBjLCjX+EsuT0DOx91r0liH+Qxut9+a99eNG
c67/JfhWTJEfbrYCQC7ZjqHffZIhbAvSzHWQAaPmJZxVjtliEo+ZPc8/2mybP2/P
gM8xhYKNvzDbNousZkN0V4EoEeGFBgzGw3ULkYvcJZ08IQQBJqPpODUNvvtKIQMX
9q8x3XSXxXzBVIiO/CHzqnSuqbxvnasftyaglBMOAq0Z8BSCZSru9Sz54ZX/rojJ
EXaIG2vImWOBPePVCrGOT+2tA2VCH3SyC4glBGkR/1Vsrax6w+l6LI2bWXJvrgdW
WrX13EjrQasg/6QA6SqxjJAn1rVcCds3bJXiJfh5Xkfa56DWUrBmqrjn1LKReSbw
4O24G00hb214839TC/g1xICbBt2EwZXJfv+GZbRGT6QxOIwGTzY49KC3rI454B7A
dazKOF13jZ7DaOQ=
=jHg/
-END PGP SIGNATURE End Message ---

Bug#917869: python-escript FTBFS on armhf, mips, mipsel and mips64el

[Anton Gladky]

Thanks, I will take care of it.

Anton

Am Mi., 2. Jan. 2019 um 00:51 Uhr schrieb Adrian Bunk :
>
> On Mon, Dec 31, 2018 at 06:51:12AM +, peter green wrote:
> >... while the mips and mipsel builds ran out of virtual memory.
> >
> > It may be worth playing with the settings, the first thing to try is 
> > probably -Wl,-no-keep-memory , if that fails it may be worth trying 
> > optimising for size ( -Os instead of -O2 )
>
> I'd be surprised if -Os would help.
>
> Most of the time the mips/mipsel build can be fixed by appending -g1 to
> the CXXFLAGS, overwriting the default -g (which is -g2).
>
> 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
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#864709: xfce CD1 image should contain fonts for languages supported by debian installer

[Steve McIntyre]

On Mon, Dec 31, 2018 at 12:54:52AM +0900, Hideki Yamane wrote:
>
>On Sun, 30 Dec 2018 18:46:45 +0530
>Pirate Praveen  wrote:
>> We have not stopped providing CD images. DVD is an additional option. I 
>> think this matters still.
>
> Well, we've already stopped it 3 years ago.
> https://lists.debian.org/debian-devel-announce/2015/09/msg4.html
>
> But, https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ shows
> debian-9.6.0-amd64-xfce-CD-1.iso as default desktop image... why?

After a lot of requests, I added back configuration to build a
single-CD installer image for xfce. If that's now looking too small
and is missing key packages, I'll check and see what we can do. But we
may now be forced to drop it - we've already worked on minimisation
several times in the last few years.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.

Bug#912245: marked as done (ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key too small)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 16:35:16 +
with message-id 
and subject line Bug#912245: fixed in ruby-nio4r 2.3.1-1~exp1
has caused the Debian Bug report #912245,
regarding ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key too small
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.)


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

ruby-nio4r fails to build in unstable with the current openssl:

| Failures:
| 
|   1) OpenSSL::SSL::SSLSocket behaves like an NIO selectable selects readable 
objects
|  Failure/Error: ssl_peer = OpenSSL::SSL::SSLSocket.new(peer, 
ssl_server_context)
| 
|  OpenSSL::SSL::SSLError:
|SSL_CTX_use_certificate: ee key too small
|  Shared Example Group: "an NIO selectable" called from 
./spec/nio/selectables/ssl_socket_spec.rb:160
|  # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `initialize'
|  # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `new'
|  # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `block (2 levels) in 
'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block 
(2 levels) in let'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block 
(3 levels) in fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `fetch'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block 
(2 levels) in fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/support/reentrant_mutex.rb:23:in 
`synchronize'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:156:in `block 
in fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:155:in `fetch'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:155:in 
`fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block 
in let'
|  # ./spec/support/selectable_examples.rb:5:in `block (2 levels) in '
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `instance_exec'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in `block in 
with_around_and_singleton_context_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in `block in 
with_around_example_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in 
`run_around_example_hooks_for'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in 
`with_around_example_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in 
`with_around_and_singleton_context_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:629:in `block in 
run_examples'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in `map'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in 
`run_examples'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `block in 
run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `map'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (3 
levels) in run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `map'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (2 
levels) in run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1989:in 
`with_suite_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `block in 
run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:74:in `report'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:110:in `run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
|  # /usr/bin/rspec:4:in `'
| 
|   2) OpenSSL::SSL::SSLSocket behaves like an NIO selectable does not select 
unwritable objects
|  Failure/Error: ssl_peer = OpenSSL::SSL::SSLSocket.new(peer, 
ssl_server_context)
| 
|  OpenSSL::SSL::SSLError:
|

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

[Gregor Riepl]

>> I will look into the issue.
>> If you have any idea why it might be occurring, please share.
> 
> The actual error is in #917057, which was already correctly marked as 
> affecting src:cura-engine.

I'm positive that the problem is more complex than that, because I already
committed and tested the fix for #917057 and I still get an error.

That, or the fix wasn't enough.

Bug#916941: libvncserver: Multiple security vulnarabilities

[Salvatore Bonaccorso]

Control: tags -1 + patch

Attached is proposed debdiff for the update, but though not yet
uploaded. 

The fix for CVE-2018-15126 unfortunately introduced two new symbols
while dropping CloseUndoneFileTransfer, but afaics from sources.d.n
search nobody is using it directly.

Regards,
Salvatore
diff -Nru libvncserver-0.9.11+dfsg/debian/changelog 
libvncserver-0.9.11+dfsg/debian/changelog
--- libvncserver-0.9.11+dfsg/debian/changelog   2018-06-05 14:43:47.0 
+0200
+++ libvncserver-0.9.11+dfsg/debian/changelog   2019-01-02 16:26:53.0 
+0100
@@ -1,3 +1,32 @@
+libvncserver (0.9.11+dfsg-1.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix multiple security vulnerabilities (Closes: #916941)
+- Use-after-free in file transfer extension allows for potential
+  code execution (CVE-2018-15126)
+- Heap out-of-bounds write in
+  rfbserver.c:rfbProcessFileTransferReadBuffer() allows for
+  potential code execution (CVE-2018-15127)
+- Multiple heap out-of-bound writes in VNC client code
+  (CVE-2018-20019)
+- Heap out-of-bound write inside structure in VNC client code allows
+  for potential code execution (CVE-2018-20020)
+- Infinite loop in VNC client code allows for denial of service
+  (CVE-2018-20021)
+- Improper initialization in VNC client code allows for information
+  disclosure (CVE-2018-20022)
+- Improper initialization in VNC Repeater client code allows for
+  information disclosure (CVE-2018-20023)
+- NULL pointer dereference in VNC client code allows for denial of
+  service (CVE-2018-20024)
+- Use-after-free in file transfer extension server code allows for
+  potential code execution (CVE-2018-6307)
+  * Update symbols file for libvncserver1.
+The fix for CVE-2018-15126 removes CloseUndoneFileTransfer and
+introduces new CloseUndoneFileDownload and CloseUndoneFileUpload.
+
+ -- Salvatore Bonaccorso   Wed, 02 Jan 2019 16:26:53 +0100
+
 libvncserver (0.9.11+dfsg-1.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols 
libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols
--- libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols   2018-06-05 
14:43:47.0 +0200
+++ libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols   2019-01-02 
16:26:53.0 +0100
@@ -3,7 +3,9 @@
  ChkFileDownloadErr@Base 0.9.10
  ChkFileUploadErr@Base 0.9.10
  ChkFileUploadWriteErr@Base 0.9.10
- CloseUndoneFileTransfer@Base 0.9.10
+#MISSING: 0.9.11+dfsg-1.2~# CloseUndoneFileTransfer@Base 0.9.10
+ CloseUndoneFileDownload@Base 0.9.11+dfsg-1.2~
+ CloseUndoneFileUpload@Base 0.9.11+dfsg-1.2~
  ConvertPath@Base 0.9.10
  CreateDirectory@Base 0.9.10
  CreateFileDownloadBlockSizeDataMsg@Base 0.9.10
diff -Nru 
libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch
 
libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch
--- 
libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch
  1970-01-01 01:00:00.0 +0100
+++ 
libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch
  2019-01-02 16:26:53.0 +0100
@@ -0,0 +1,51 @@
+From: Christian Beier 
+Date: Sun, 21 Oct 2018 23:38:40 +0200
+Subject: [1/5] tightvnc-filetransfer: tie the download thread to the control
+ structure
+Origin: 
https://github.com/LibVNC/libvncserver/commit/89419fb1a0cef42b63528e6930f4e545cfef4c95
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-15126
+Bug-Debian: https://bugs.debian.org/916941
+Bug: https://github.com/LibVNC/libvncserver/issues/242
+
+re #242
+---
+ libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c | 3 +--
+ libvncserver/tightvnc-filetransfer/rfbtightproto.h | 1 +
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c 
b/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
+index 0473783164f2..8e38f8880f5b 100644
+--- a/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
 b/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
+@@ -508,7 +508,6 @@ RunFileDownloadThread(void* client)
+ void
+ HandleFileDownload(rfbClientPtr cl, rfbTightClientPtr rtcp)
+ {
+-  pthread_t fileDownloadThread;
+   FileTransferMsg fileDownloadMsg;
+   
+   memset(, 0, sizeof(FileTransferMsg));
+@@ -521,7 +520,7 @@ HandleFileDownload(rfbClientPtr cl, rfbTightClientPtr rtcp)
+   rtcp->rcft.rcfd.downloadInProgress = FALSE;
+   rtcp->rcft.rcfd.downloadFD = -1;
+ 
+-  if(pthread_create(, NULL, RunFileDownloadThread, 
(void*) 
++  if(pthread_create(>rcft.rcfd.downloadThread, NULL, 
RunFileDownloadThread, (void*)
+   cl) != 0) {
+   

Bug#916355: marked as done (cython: References to non-existent members of PyThreadState in Python 3.7)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 16:19:42 +
with message-id 
and subject line Bug#916355: fixed in cython 0.29.2-1
has caused the Debian Bug report #916355,
regarding cython: References to non-existent members of PyThreadState in Python 
3.7
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.)


-- 
916355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cython
Version: 0.28.4-1
Severity: grave
Tags: upstream patch
Justification: renders package unusable

Dear Maintainer,

While building and testing an update to lasagne, I got the following
error, which I have tracked down to cython.

```
E Exception: ('The following error happened while compiling the node',
forall_inplace,cpu,scan_fn}(Elemwise{sub,no_inplace}.0,
Subtensor{int64:int64:int64}.0, IncSubtensor{InplaceSet;:int64:}.0,
Join.0), '\n', 'Compilation failed (return status=1):
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:
In function ‘void __Pyx__ExceptionSave(PyThreadState*, PyObject**,
PyObject**,
PyObject**)’:. 
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12749:21:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_type’; did you mean ‘curexc_type’?.  *type = tstate->exc_type;.
^~~~.
curexc_type. 
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12750:22:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_value’; did you mean ‘curexc_value’?.  *value =
tstate->exc_value;.  ^.
curexc_value. 
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12751:19:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_traceback’; did you mean ‘curexc_traceback’?.  *tb =
tstate->exc_traceback;.  ^.
curexc_traceback. 
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:
In function ‘void __Pyx__ExceptionReset(PyThreadState*, PyObject*,
PyObject*,
PyObject*)’:. 
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12758:24:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_type’; did you mean ‘curexc_type’?.  tmp_type =
tstate->exc_type;.  ^~~~.
```

Lasagne uses theano, which run-time compiles Python extensions using
cython.  When used with python 3.7, cython generates code containing
references to members of PyThreadState that do not exist.  This seems
to be related to an upstream bug which has been fixed:

https://github.com/cython/cython/issues/1955

Therefore, I recommend upgrading the cython package to the latest
release which is only a couple of weeks old.  I have provided a merge
request for this update here:

https://salsa.debian.org/python-team/applications/cython/merge_requests/2


regards,
Steve


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

Kernel: Linux 4.15.0-42-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages cython depends on:
ii  libc6   2.28-2
ii  python  2.7.15-3

Versions of packages cython recommends:
ii  gcc 4:8.2.0-2
ii  python-dev  2.7.15-3

Versions of packages cython suggests:
pn  cython-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cython
Source-Version: 0.29.2-1

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated cython 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)

Processed: Re: Bug#916941: libvncserver: Multiple security vulnarabilities

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #916941 [libvncserver] libvncserver: Multiple security vulnerabilities
Added tag(s) patch.

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

Processed: Bug #912245 in ruby-nio4r marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912245 [src:ruby-nio4r] ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key 
too small
Added tag(s) pending.

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

Bug#904592: predict-gsat: No executable is included

[Manolo Díaz]

El 30 de diciembre de 2018 14:17:00 CET, Christoph Berg  
escribió:
>Re: Manolo Díaz 2018-07-25
><153252250500.25469.2624480834566544223.reportbug@localhost>
>> No gsat executable is included
>
>Good news: I fixed this in git.
>
>Bad news: predict doesn't start for me. It keeps asking for my station
>coordinates, and just exits once I pressed Enter a few times.
>
>The whole package seems pretty horrible, given that we have even a
>patch to add a cmake build system, plus a load of other huge patches.
>Unless someone steps in to work with upstream to get these patches
>integrated, I'd claim it would be best to drop this package from
>Debian. The alternative gpredict seems to work well.
>
>Christoph

I agree. Gpredict works well.

Manolo.


-- 
Manolo Díaz

Bug#912245: Bug #912245 in ruby-nio4r marked as pending

[Cédric Boutillier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-nio4r/commit/014aba7f578d428e070b578055056760f4952f89


Add patch to create larger keys in tests (Closes: #912245)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912245

Bug#884658: marked as done (dkms: Should really depends on dpkg-dev for dpkg-architecture)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 15:50:39 +
with message-id 
and subject line Bug#884658: fixed in dkms 2.6.1-2
has caused the Debian Bug report #884658,
regarding dkms: Should really depends on dpkg-dev for dpkg-architecture
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.)


-- 
884658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dkms
Version: 2.3-3
Severity: important

Dear Maintainer,

dkms depends on "make | build-essential | dpkg-dev" but /usr/sbin/dkms call
explicitly dpkg-architecture in make_debian()

As example, if dpkg-dev isn't installed you can't build virtualbox-guest-dkms 
modules.

Christian

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

Kernel: Linux 4.1.48 (SMP w/8 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)

Versions of packages dkms depends on:
ii  build-essential  12.4
ii  coreutils8.28-1
ii  dpkg-dev 1.19.0.4
ii  gcc  4:7.2.0-1d1
ii  kmod 24-1
ii  make 4.1-9.1
ii  patch2.7.5-1+b2

Versions of packages dkms recommends:
ii  fakeroot 1.22-2
pn  linux-headers-686-pae | linux-headers-amd64 | linux-headers-gen  
ii  lsb-release  9.20170808
ii  sudo 1.8.21p2-2

Versions of packages dkms suggests:
ii  menu2.1.47+b1
pn  python3-apport  

-- Configuration Files:
/etc/modprobe.d/dkms.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dkms
Source-Version: 2.6.1-2

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated dkms 
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, 02 Jan 2019 16:15:32 +0100
Source: dkms
Binary: dkms
Architecture: source
Version: 2.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dynamic Kernel Modules Support Team 
Changed-By: Gianfranco Costamagna 
Description:
 dkms   - Dynamic Kernel Module Support Framework
Closes: 832558 884658
Changes:
 dkms (2.6.1-2) unstable; urgency=medium
 .
   * Team upload (salsa shared repo)
   * Add dpkg-dev dependency, needed for dpkg-architecture calls (Closes: 
#884658)
   * cherry-pick shim-signed break relationship from Ubuntu
 - (will be needed if Debian shim-signed is updated)
   * debian/patches/6ef1a48eda99ec0d728302830483fd0137174d17.patch:
 cherry-pick upstream fix for kernel version parsing
   * debian/patches/0015-change-arch-in-mkdeb-template.patch: cherry-pick
 Ubuntu applied fix for mkbmdeb (Closes: #832558)
Checksums-Sha1:
 4cb6a139f06e9fd3851f0341c5b9b33b3067c3cd 1965 dkms_2.6.1-2.dsc
 3bc42fdc341cd2c8395fe109451cf1a71a170dee 21084 dkms_2.6.1-2.debian.tar.xz
 bee59efe7bf357945a728450e78c1b71e3eeffd0 6628 dkms_2.6.1-2_source.buildinfo
Checksums-Sha256:
 65841b4985e58a1c87010a2abb1d71e0ce1659852018674d8ca5373c0ccabcf1 1965 
dkms_2.6.1-2.dsc
 a1f62322cc4dffa3debc10e209d47cc58bcf79b5dd45f75ecb414b907c19690b 21084 
dkms_2.6.1-2.debian.tar.xz
 a9466fdb6fd8c112d9e87a8462c6a465203b2fe9c1036a5495fc0a6e08d06c44 6628 
dkms_2.6.1-2_source.buildinfo
Files:
 0e16360529fe40b846d17b5b012ac1b7 1965 kernel optional dkms_2.6.1-2.dsc
 9bb45bbef3575fefda9515209e954be5 21084 kernel optional 
dkms_2.6.1-2.debian.tar.xz
 edc5b8e30d4c5382327347fcfbe548d8 6628 kernel optional 
dkms_2.6.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAlws2kwACgkQ808JdE6f
XdnZlBAAwrT/yX1t5SPxMQPVPT1XWdpCNXV4kMHkSvL9Ig56JuzcNjAY8dyl1RRI

Bug#914835: marked as done (python3-defaults breaks aiocoap autopkgtest)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 15:49:07 +
with message-id 
and subject line Bug#914835: fixed in aiocoap 0.3-3
has caused the Debian Bug report #914835,
regarding python3-defaults breaks aiocoap autopkgtest
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.)


-- 
914835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3-defaults, aiocoap
Control: found -1 python3-defaults/3.7.1-2
Control: found -1 aiocoap/0.3-2
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of python3-defaults (which changed the default
python3 from 3.6 to 3.7) the autopkgtest of aiocoap fails in testing
when that autopkgtest is run with the binary packages of
python3-defaults from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
python3-defaults   from testing3.7.1-2
aiocoapfrom testing0.3-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is contributing to the delay of the migration
of python3-defaults to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package? If needed,
please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/a/aiocoap/1389066/log.gz

==
ERROR: test_counter (tests.observe.TestObserve)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.bj1_ax2e/downtmp/build.c9j/src/tests/server.py",
line 213, in setUp
super(WithTestServer, self).setUp()
  File
"/tmp/autopkgtest-lxc.bj1_ax2e/downtmp/build.c9j/src/tests/server.py",
line 231, in setUp
super(WithClient, self).setUp()
  File
"/tmp/autopkgtest-lxc.bj1_ax2e/downtmp/build.c9j/src/tests/server.py",
line 171, in setUp
super(WithAsyncLoop, self).setUp()
  File
"/tmp/autopkgtest-lxc.bj1_ax2e/downtmp/build.c9j/src/tests/server.py",
line 138, in setUp
self.handler = self.ListHandler()
  File "/usr/lib/python3.7/logging/__init__.py", line 824, in __init__
self.createLock()
  File "/usr/lib/python3.7/logging/__init__.py", line 847, in createLock
_register_at_fork_acquire_release(self)
  File "/usr/lib/python3.7/logging/__init__.py", line 250, in
_register_at_fork_acquire_release
_at_fork_acquire_release_weakset.add(instance)
  File "/usr/lib/python3.7/_weakrefset.py", line 84, in add
self.data.add(ref(item, self._remove))
TypeError: unhashable type: 'ListHandler'




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: aiocoap
Source-Version: 0.3-3

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

Debian distribution maintenance software
pp.
Agustin Henze  (supplier of updated aiocoap 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, 02 Jan 2019 00:17:17 +
Source: aiocoap
Binary: python3-aiocoap python-aiocoap-doc
Architecture: source all
Version: 0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Agustin Henze 
Description:
 python-aiocoap-doc - Python implementation of CoAP (doc)
 python3-aiocoap - Python implementation of CoAP
Closes: 914835
Changes:
 aiocoap (0.3-3) unstable; urgency=medium
 .
   [ Agustin Henze ]
   * Switch to master branch as debian branch
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * Use 'python3 -m sphinx' instead of sphinx-build for 

Bug#915207: marked as done (gnudatalanguage: autopkgtests fail: test_bug_n000720, test_idlneturl, test_point_lun, test_save_restore, test_zip)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 15:34:41 +
with message-id 
and subject line Bug#915207: fixed in gnudatalanguage 0.9.9-2
has caused the Debian Bug report #915207,
regarding gnudatalanguage: autopkgtests fail: test_bug_n000720, test_idlneturl, 
test_point_lun, test_save_restore, test_zip
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.)


-- 
915207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnudatalanguage
Version: 0.9.8-7
Severity: serious
Justification: Block HDF5 and netcdf transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Autopkgtest fails for gnudatalanguage [1]. This is not due to HDF5 nor
netcdf transitions, because I've rebuilt gnudatalanguage on unstable
against HDF5 1.10.0 and netcdf 4.6.1 and I observ the same failures:

The following tests FAILED:
 69 - test_bug_n000720.pro (Failed)
 93 - test_fft_leak.pro (Failed)
 96 - test_file_delete.pro (Failed)
103 - test_fix.pro (Failed)
106 - test_formats.pro (Failed)
114 - test_hdf5.pro (Failed)
116 - test_idlneturl.pro (Failed)
129 - test_make_dll.pro (Failed)
140 - test_n_tags.pro (Failed)
142 - test_obj_isa.pro (Failed)
144 - test_parse_url.pro (Failed)
150 - test_point_lun.pro (Failed)
166 - test_resolve_routine.pro (Failed)
168 - test_rounding.pro (Failed)
171 - test_save_restore.pro (Failed)
190 - test_total.pro (Failed)
201 - test_zip.pro (Failed)

Unfortunately I don't have the knowledge to dig further into this issue.

Thanks,

_g.

[1] https://ci.debian.net/packages/g/gnudatalanguage/unstable/amd64/

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlwCyh4ACgkQ7+hsbH/+
z4NHOgf/WRRJMYmvqXncFMwNPW0hdXaB/MBsbWXUog8K62QL4ZVBqBZxGihtGkL3
Iv/sLSG3sX1/INS921cwEUnLztR8pe3JnX9WOp8+V1ko9lTsVD5Qs8IFqV+Ex8p0
CqWGzVBkSpUNL4k9AMCyAvAW+B4J8vp1HdxUr3HcsLn7Yets1DoImTwepZX+RPwI
XABz5u9hAgrzWcVLz3CVLZXQP25yo46u3K6dNzLmPQ7bKz5voe8WUYKnLf/DEX7g
nI8HLzHUTGbdbIKE+9lkSBr6CkrjsG8iglEVERyg40GQRVvwoaP8+bj2lP+JVnDF
4y/6QRpWJSSPMXxibmvh8kdgOCvphg==
=xVNn
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: gnudatalanguage
Source-Version: 0.9.9-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated gnudatalanguage 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, 02 Jan 2019 16:02:15 +0100
Source: gnudatalanguage
Binary: libgnudatalanguage0 gnudatalanguage python-gdl
Architecture: source
Version: 0.9.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Description:
 gnudatalanguage - Free IDL compatible incremental compiler
 libgnudatalanguage0 - Free IDL compatible incremental compiler shared library
 python-gdl - Python interface for the GNU Data Language
Closes: 915207
Changes:
 gnudatalanguage (0.9.9-2) unstable; urgency=medium
 .
   * Add some known failing tests to ignore
   * Drop unneeded using namespace std that conflicts with ALTIVEC vector
   * Temporarily disable HDF-5 support. Closes: #915207
   * Push Standards-Version to 4.3.0. No changes needed.
Checksums-Sha1:
 f8a92083ac57936adfa6db992eca3490e8cfc080 2713 gnudatalanguage_0.9.9-2.dsc
 554003c06af693fd0f5e74258627c2464a0aa45a 20476 
gnudatalanguage_0.9.9-2.debian.tar.xz
Checksums-Sha256:
 69b46f376c906f5b68c58ff44547bd711c217e1f837ac93c64c7911d3b316a78 2713 
gnudatalanguage_0.9.9-2.dsc
 

Bug#912236: marked as done (ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: ee key too small)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 15:23:48 +
with message-id 
and subject line Bug#912236: fixed in ruby-ffi-rzmq 2.0.6-2
has caused the Debian Bug report #912236,
regarding ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: ee key too small
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.)


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

ruby-ffi-rzmq fails to build from source in unstable (but not in
testing):

| Failures:
| 
|   1) ZMQ::Poller poll works with SSLSocket
|  Failure/Error: server = OpenSSL::SSL::SSLSocket.new(s, ctx)
| 
|  OpenSSL::SSL::SSLError:
|SSL_CTX_use_certificate: ee key too small
|  # ./spec/poll_spec.rb:254:in `initialize'
|  # ./spec/poll_spec.rb:254:in `new'
|  # ./spec/poll_spec.rb:254:in `block (3 levels) in '
| 
| Finished in 2.72 seconds (files took 0.12738 seconds to load)
| 443 examples, 1 failure
| 
| Failed examples:
| 
| rspec ./spec/poll_spec.rb:240 # ZMQ::Poller poll works with SSLSocket
| 
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install /<>/debian/ruby-ffi-rzmq 
returned exit code 1
| make: *** [debian/rules:15: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Looks like more openssl fallout.

Helmut
--- End Message ---
--- Begin Message ---
Source: ruby-ffi-rzmq
Source-Version: 2.0.6-2

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-ffi-rzmq 
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, 02 Jan 2019 15:55:00 +0100
Source: ruby-ffi-rzmq
Binary: ruby-ffi-rzmq
Architecture: source
Version: 2.0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-ffi-rzmq - FFI based Ruby bindings for ZeroMQ (ØMQ) networking library
Closes: 912236
Changes:
 ruby-ffi-rzmq (2.0.6-2) unstable; urgency=medium
 .
   * Team upload
   * Bump Standards-Version to 4.3.0 (no changes needed)
   * Add a helper script to regenerate keys and certificates if needed
 under debian/keys_and_certificates.rb
   * Add patch for longer RSA private key and related certificate to run
 successfully tests about SSL socket (Closes: #912236)
Checksums-Sha1:
 44ade94ca2a640f1276c59e1581dd4dfec72cd35 1755 ruby-ffi-rzmq_2.0.6-2.dsc
 ae89a664d4ab6008e3357579fb720704a0683fb2 8784 
ruby-ffi-rzmq_2.0.6-2.debian.tar.xz
 b48cb159e7d82eedbece3d433fb4651f969445d3 13731 
ruby-ffi-rzmq_2.0.6-2_source.buildinfo
Checksums-Sha256:
 9c0b1693d5fd0f2d75e251ce2d53e42c3a0bf6b07515d0d60fa730bf3029b637 1755 
ruby-ffi-rzmq_2.0.6-2.dsc
 9e3498b05d7e7c25d44dc46138262c5a9e943ce2fc9610a13475b7370422a968 8784 
ruby-ffi-rzmq_2.0.6-2.debian.tar.xz
 4552cb42b40e6cc87bb5eb9143f873cfbb202ed8f2068a8f67a7747f4abd7dec 13731 
ruby-ffi-rzmq_2.0.6-2_source.buildinfo
Files:
 871e11a49d14178ebcc1dbc3b7513b05 1755 ruby optional ruby-ffi-rzmq_2.0.6-2.dsc
 1b9333dd12ac8793c7d7581e25cc9797 8784 ruby optional 
ruby-ffi-rzmq_2.0.6-2.debian.tar.xz
 81d289b868b998032e194968f30bed5c 13731 ruby optional 
ruby-ffi-rzmq_2.0.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlws0zcACgkQia+CtznN
IXq/CQf/aDKpDF5eEwac2Sr0y7U6BBAEyTLqE3kv9k7gCOavojWC6Agh4BU1mf9t
PLRGnSXVnPVRJio8ieas6KdpmkQe0Z/88R1hIKT0TMnru6EuAibGESnLBhDLm4iA
zwxVEeCUaWTJeV2zFdAZ1s3qfuqvuH/Vinm4BPg0k9RwxBHYp2DiZVbpZiUSfMxV
RBTLBy3iGgR5MT1jNUdHE/mOXEl8xEzkll0bF99g04ZEdAd/hd+hv5vamtNf0Rp5
VfgN0HGskkqq7LIqyxZSSN8UL08qVQ3UP/JEwswljq+D4lqnJVMWT2H79Tx4/Ayw
a4tR4+RrhDHHeH7YNR562u4IchTVnQ==
=v1u+
-END PGP SIGNATURE End Message ---

Bug#918003: marked as done (nwchem FTBFS on 32bit: BLAS size mismatch with Global Arrays)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 15:22:35 +
with message-id 
and subject line Bug#918003: fixed in nwchem 6.8.1-2
has caused the Debian Bug report #918003,
regarding nwchem FTBFS on 32bit: BLAS size mismatch with Global Arrays
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.)


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

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

...
   debian/rules override_dh_auto_build-arch
make[1]: Entering directory '/<>'
mkdir -p /<>/bin/LINUX
(cd /<>/src && NWCHEM_TOP=/<> make nwchem_config)
make[2]: Entering directory '/<>/src'

NWChem requires Global Arrays built with same BLAS size 
you asked BLAS_SIZE=8
Global Arrays was built with BLAS size=4

config/makefile.h:125: *** .  Stop.
make[2]: Leaving directory '/<>/src'
make[1]: *** [debian/rules:75: override_dh_auto_build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: nwchem
Source-Version: 6.8.1-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Jan 2019 15:54:31 +0100
Source: nwchem
Binary: nwchem nwchem-data
Architecture: source
Version: 6.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 nwchem - High-performance computational chemistry software
 nwchem-data - High-performance computational chemistry software (data files)
Closes: 918003
Changes:
 nwchem (6.8.1-2) unstable; urgency=medium
 .
   * debian/rules (BLAS_SIZE): Set to 4 on all architectures. Closes: #918003.
   * debian/rules (USE_SCALAPACK_I8): Removed.
Checksums-Sha1:
 ca4e82215ba44d995c4d5e821b3ad3ad6ca73850 2197 nwchem_6.8.1-2.dsc
 a307244c7a11c72c93f100fa4b875ca943fdb33c 19500 nwchem_6.8.1-2.debian.tar.xz
 190d49ff49fd798c1204133c6157ff8e0cc7c771 6661 nwchem_6.8.1-2_source.buildinfo
Checksums-Sha256:
 ea1f0d45d44628e7b53989dbb51aab74bea7d0e7c404ba7af714f338cdffcf81 2197 
nwchem_6.8.1-2.dsc
 3739024bc537b95353d85021fe329bcb3126aa3ffa8efaaf6a3e486fd7e23492 19500 
nwchem_6.8.1-2.debian.tar.xz
 ce1eba43dccfd85084e0404557abfa299a6f61c98f758dc398ef7ee8273b5858 6661 
nwchem_6.8.1-2_source.buildinfo
Files:
 5fa975e30c398cef3534da3d6a286f26 2197 science optional nwchem_6.8.1-2.dsc
 688721395e6dd91a4677a0478ed85363 19500 science optional 
nwchem_6.8.1-2.debian.tar.xz
 35eedb4589874c765e405dcf2afcbd89 6661 science optional 
nwchem_6.8.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAlws0LwACgkQ3GhqJ7Q0
gbANnA/+O2ew5kxBTaU2a+laYHuGQXiMhYUnaCRMvGLzOdjLQ1c3xy9jaFwWltGW
k+Xo+cdzIKsvUIZxsUn5rQYIf8vJhzG37DPXk1jcXCFEeGdYsAmc+dd1MVY0Fm4U
/0/hMu89TSG2pwVdXOYwCDZAqqeknCDZXR942H/HhFsMjiatdfvlFQiy/HejPVkK
kn3aonls/ME/Gi2HJ3jQ5rb/anTWcSxtMn5hHGjNi1eB9o07nvY4dsoLVgulirY+
22P6hhZjIjB2AxE3ai4bEk2C58JV4nr2//3tFhXpX8l3fmXKfXMS/OJKsz8w3eT4
jL92YN6D63i5RNrx8U02JLnE4XE4D0vWPqNnFi8WExPChcx2s/LeTlSMsqjhhFWH
lwdtmzNYQvVziBfktS24/vxSE33FZqYfaFGvlCiFgC1x9NS/f7SCpCZPq9dQJSaX
f/h+/hKTSYAcFRHjBRHhIbHwA/BNEyV12SkfoGm858R0Hrqbae0DAKkcLFToZ8sK
aOPb4vhHHVfYWdieAZzebRrev1zrNCb3m4bKpkGslHxto/VTPbCxFvOpxrZwjHnu
9A/42uiE9pL/9aku1Rm8ISxWcSEqqLkTlNUGKh777pzPIpHo2Co/+1299catrshF
cXf0U7R+uGwVJ05e6PrPkJddNuAnDFq/YaXIonex8b7hq+6qFF0=
=42kw
-END PGP SIGNATURE End Message ---

Bug#912236: Bug #912236 in ruby-ffi-rzmq marked as pending

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #912236 in ruby-ffi-rzmq reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ruby-team/ruby-ffi-rzmq/commit/15ad9dd6f4c3358acbd7db2c7e288aae2d5efcf8


longer RSA private key for tests  (Closes: #912236)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912236

Processed: Bug #912236 in ruby-ffi-rzmq marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912236 [src:ruby-ffi-rzmq] ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: 
ee key too small
Added tag(s) pending.

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

Bug#907149: marked as done (roodi: FTBFS in buster/sid FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 14:56:53 +
with message-id 
and subject line Bug#907149: fixed in roodi 5.0.0-2
has caused the Debian Bug report #907149,
regarding roodi: FTBFS in buster/sid FTBFS in buster/sid (failing tests)
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.)


-- 
907149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:roodi
Version: 5.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --test

[... snipped ...]

Checked 87 files
Found 0 errors.
.
Running Roodi checks

Checked 87 files
Found 0 errors.
.

Failures:

  1) Roodi::Checks::EmptyRescueBodyCheck should reject a rescue block that only 
contains a comment
 Failure/Error: errors[0].to_s.should match(/dummy-file.rb:[5] - Rescue 
block should not be empty./)

   expected "dummy-file.rb:3 - Rescue block should not be empty." to match 
/dummy-file.rb:[5] - Rescue block should not be empty./
   Diff:
   @@ -1,2 +1,2 @@
   -/dummy-file.rb:[5] - Rescue block should not be empty./
   +"dummy-file.rb:3 - Rescue block should not be empty."
 # ./spec/roodi/checks/empty_rescue_body_check_spec.rb:209:in `block (2 
levels) in '

Deprecation Warnings:

Using `should_not` from rspec-expectations' old `:should` syntax without 
explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
:should }` instead. Called from 
/<>/spec/roodi/checks/abc_metric_method_check_spec.rb:12:in 
`verify_content_score'.

Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling 
the syntax is deprecated. Use the new `:expect` syntax or explicitly enable 
`:should` instead. Called from 
/<>/spec/roodi/core/runner_spec.rb:58:in `block (3 levels) in '.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

2 deprecation warnings total

Finished in 0.92636 seconds (files took 0.34406 seconds to load)
115 examples, 1 failure

Failed examples:

rspec ./spec/roodi/checks/empty_rescue_body_check_spec.rb:197 # 
Roodi::Checks::EmptyRescueBodyCheck should reject a rescue block that only 
contains a comment

/usr/bin/ruby2.5 /usr/bin/rspec 
spec/roodi/checks/abc_metric_method_check_spec.rb 
spec/roodi/checks/assignment_in_conditional_check_spec.rb 
spec/roodi/checks/case_missing_else_check_spec.rb 
spec/roodi/checks/class_line_count_check_spec.rb 
spec/roodi/checks/class_name_check_spec.rb 
spec/roodi/checks/class_variable_check_spec.rb 
spec/roodi/checks/control_coupling_check_spec.rb 
spec/roodi/checks/core_method_override_check_spec.rb 
spec/roodi/checks/cyclomatic_complexity_block_check_spec.rb 
spec/roodi/checks/cyclomatic_complexity_method_check_spec.rb 
spec/roodi/checks/empty_rescue_body_check_spec.rb 
spec/roodi/checks/for_loop_check_spec.rb 
spec/roodi/checks/method_line_count_check_spec.rb 
spec/roodi/checks/method_name_check_spec.rb 
spec/roodi/checks/module_line_count_check_spec.rb 
spec/roodi/checks/module_name_check_spec.rb 
spec/roodi/checks/npath_complexity_method_check_spec.rb 
spec/roodi/checks/parameter_number_check_spec.rb spec/roodi/core/runner_spec.rb 
spec/roodi_task_spec.rb failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/roodi returned exit 
code 1
make: *** [debian/rules:15: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build 

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

[Michael Banck]

Control: tag -1 pending

Hello,

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

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


* debian/rules (BLAS_SIZE): Set to 4 on all architectures. Closes: #918003.
  * debian/rules (USE_SCALAPACK_I8): Removed.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918003

Bug#917904: tightvncserver does not ask for password set by vncpasswd

[Christoph Terasa]

Hi Ola,

thank you for your answer. I checked:

$ ls -l /etc/alternatives/vnc*
lrwxrwxrwx 1 root root 24 Jul 27  2017 /etc/alternatives/vncconnect -> 
/usr/bin/tightvncconnect
lrwxrwxrwx 1 root root 40 Jul 27  2017 /etc/alternatives/vncconnect.1.gz 
-> /usr/share/man/man1/tightvncconnect.1.gz
lrwxrwxrwx 1 root root 23 Jul 27  2017 /etc/alternatives/vncpasswd -> 
/usr/bin/tightvncpasswd
lrwxrwxrwx 1 root root 39 Jul 27  2017 /etc/alternatives/vncpasswd.1.gz 
-> /usr/share/man/man1/tightvncpasswd.1.gz
lrwxrwxrwx 1 root root 23 Jul 27  2017 /etc/alternatives/vncserver -> 
/usr/bin/tightvncserver
lrwxrwxrwx 1 root root 39 Jul 27  2017 /etc/alternatives/vncserver.1.gz 
-> /usr/share/man/man1/tightvncserver.1.gz



Before I will purge my configuration as well, I would try to keep my 
system in its current state. Is there are way to get more debugging info 
from tightvncserver, or a log file? The man page does not seem to 
mention anything in that regard.



kind regards,
Christoph


On 1/2/19 1:26 AM, Ola Lundqvist wrote:

Hi Jan

Thank you for the report.
I have now tested this myself. I purged all vnc software installed, 
installed tightvncserver, run tightvncserver and then run vncpasswd to 
set a password.

I failed to reproduce the problem. I'm asked for a password.

So the question is what you did differently. Can it be so that you 
have some other vncpasswd software as an alternative and that happen 
to not be updating the same things?


Best regards

// Ola

On Mon, 31 Dec 2018 at 15:33, Jan Christoph Terasa 
mailto:christ...@kohlio.de>> wrote:


Package: tightvncserver
Version: 1:1.3.9-9
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

I installed tightvncserver on my VPS machine via apt. This did set up
tightvncserver as an alternative for vncserver. Using a normal
user account and
starting vncserver for the first time asks for a 8-letter
password. My assumption
is this password will be used to authenticate users when
connecting to the vnc
server.

After starting the vnc server via vncserver script, it is served
on port 5901.
On the client machine I use vinagre to connect to the server on
port 5901. When
connecting, I am not asked for a password, but rather directly
taken to the X
session. I would have expected the server to ask for the password
I specified
earlier.

As a workaround, to ensure the integrity of the system, I set up
iptable rules to
not allow direct WAN connections to this port, but only allow
local connections
and use an SSH tunnel for connecting to the vnc server.


kind regards,
Christoph


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

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

Versions of packages tightvncserver depends on:
ii  libc6            2.27-8
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libx11-6         2:1.6.7-1
ii  libxext6         2:1.3.3-1+b2
ii  perl             5.28.0-3
ii  x11-common       1:7.7+19
ii  x11-utils        7.7+4
ii  xauth            1:1.0.10-1
ii  xserver-common   2:1.20.3-1
ii  zlib1g           1:1.2.11.dfsg-1

Versions of packages tightvncserver recommends:
ii  x11-xserver-utils  7.7+8
ii  xfonts-base        1:1.0.4+nmu1

Versions of packages tightvncserver suggests:
pn  tightvnc-java  

-- no debconf information



--
 --- Inguza Technology AB --- MSc in Information Technology 
/ o...@inguza.com            Folkebogatan 26     
       \
| o...@debian.org            654 68 KARLSTAD   
         |

| http://inguza.com/            Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Processed: Bug #918003 in nwchem marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918003 [src:nwchem] nwchem FTBFS on 32bit: BLAS size mismatch with Global 
Arrays
Added tag(s) pending.

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

Bug#913631: marked as done (FTBFS: libapache2-mod-auth-openidc on multiple arches)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 14:52:05 +
with message-id 
and subject line Bug#913631: fixed in libapache2-mod-auth-openidc 2.3.10-1
has caused the Debian Bug report #913631,
regarding FTBFS: libapache2-mod-auth-openidc on multiple arches
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.)


-- 
913631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libapache2-mod-auth-openidc
Version: 2.3.8-1
Control: tags -1 patch pending ftbfs

--

Hi,

libapache2-mod-auth-openidc fails to build on amd64, ppc64el and a
number of unofficial arches. I think this is due to the parallel build.
Here is a patch that I tested successfully :

https://salsa.debian.org/debian/libapache2-mod-auth-openidc/merge_requests/1

Regards,


F.


pgp5RsU5y2Quf.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-auth-openidc
Source-Version: 2.3.10-1

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

Debian distribution maintenance software
pp.
Moritz Schlarb  (supplier of updated 
libapache2-mod-auth-openidc 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, 02 Jan 2019 14:58:25 +0100
Source: libapache2-mod-auth-openidc
Binary: libapache2-mod-auth-openidc
Architecture: source
Version: 2.3.10-1
Distribution: unstable
Urgency: medium
Maintainer: Moritz Schlarb 
Changed-By: Moritz Schlarb 
Description:
 libapache2-mod-auth-openidc - OpenID Connect authentication module for Apache
Closes: 913631
Changes:
 libapache2-mod-auth-openidc (2.3.10-1) unstable; urgency=medium
 .
   [ Frédéric Bonnard ]
   * Fix parallel build (Closes: #913631)
 .
   [ Moritz Schlarb ]
   * Update Maintainer and Standards-Version fields
   * New upstream version 2.3.10
Checksums-Sha1:
 cf84304bac6e1f8d61a728282296b8f4c14b2dfc 2518 
libapache2-mod-auth-openidc_2.3.10-1.dsc
 c7903cd02c91a24a8b9aaa4f5be5aa58096a3083 263537 
libapache2-mod-auth-openidc_2.3.10.orig.tar.gz
 a6df56da1b3f358c2e957539fab7b45f4ea96c3a 4700 
libapache2-mod-auth-openidc_2.3.10-1.debian.tar.xz
 a57a10ba26b2aa7038b14c5b0b7f0cdd2ab988b7 7277 
libapache2-mod-auth-openidc_2.3.10-1_amd64.buildinfo
Checksums-Sha256:
 fdecaa01d6a53543029ca65df1553711316ca151febb81df54dd31984974f4a0 2518 
libapache2-mod-auth-openidc_2.3.10-1.dsc
 5172d5576d75604dceaf4d8ecddbb2ba7de80ae26c8c44e0c8c824325c02dd68 263537 
libapache2-mod-auth-openidc_2.3.10.orig.tar.gz
 6077cb31ca384b7bbb5bd337a13e66028e097cf451d443acbbd802167f601e7e 4700 
libapache2-mod-auth-openidc_2.3.10-1.debian.tar.xz
 a39ea5f079c325d75da471f5e0cc70d39ad7c1401c6ce1c35dc0d412bb14685e 7277 
libapache2-mod-auth-openidc_2.3.10-1_amd64.buildinfo
Files:
 bf66916781d1992b3c5bb076da933d02 2518 httpd optional 
libapache2-mod-auth-openidc_2.3.10-1.dsc
 62b9707f0400a9051eb4aa0a9e606e5f 263537 httpd optional 
libapache2-mod-auth-openidc_2.3.10.orig.tar.gz
 51e826b4c93e761ed032b92c092aba22 4700 httpd optional 
libapache2-mod-auth-openidc_2.3.10-1.debian.tar.xz
 2f79f24f79b23214dcf12128ed54f88c 7277 httpd optional 
libapache2-mod-auth-openidc_2.3.10-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEE3wEiR7/GVQGv8oRFDCS4Qcfduq8FAlwsw8sWHHNjaGxhcmJt
QHVuaS1tYWluei5kZQAKCRAMJLhBx926r58WD/4/oR/DC11HCUlend394rO4AiF7
MhN9Cn2s8x8bfoyqXU57qEV+WbXLqOih78KwrkG63OtEJmIm4MjsSMeH+vHBHkxd
nGmgYCKKhlP8Jhiun/Xd6pHX5/3hP78E/kYlOs5kX+k6hOjhDgE2BOwz9VqBrlJ2
HX9I1A72ZSsw21NwczozXHatVtr/g8XFeBqQpo+Pz9PlilbYhaxSzzSesBvS+etc
RI5klfqLgp2w5r9z6IWvPKe2ZmcshN1IivyxdKWL81u16Y41BErEtupovbEWgXam
w/OewAeKGQc0cil3jQVQzsDQGlQPwdYzXk8T4oT0rudHa8g/y1ssAFKvcsipgzTe
frornc7lz37sMpYtldDzpbA+XL59bjMigd0m93SkwITwAs6smyZ030FsWnkHEf4l
mAdrYkNx1m0R8UBUbw1HJUaxMVLChRAMyEHFJpHpK/NAiod29CKHoS3HJcTUL+G3
2lGsPcJT4242qMRpJWXhYaMyBeLaiBrA0JvXj8v00PDnaopCROnro0Avu4mobyi/
uo45ZoPjjrJ02aXyXI2ecpnoke1h1wageB47aXBAJ+uYZmLC3qZymTUDZgHKJUVz
gjRDNr0GL/74WZgqSq/2RJ+PfOZoiBJO4cnm/YP+rHF0b/zWt2o9GwgVM+3POFT3
I4bP7cDWILfl7GFTOA==
=rnw9
-END PGP SIGNATURE End Message 

Bug#916941: libvncserver: Multiple security vulnarabilities

[Salvatore Bonaccorso]

Hi

I have been working on an update for libvncserver for unstable
(buster) as NMU. I will post a proposed debdiff when I'm relatively
confident on the result.

Regards,
Salvatore

Processed: Bug #907149 in roodi marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #907149 [src:roodi] roodi: FTBFS in buster/sid FTBFS in buster/sid (failing 
tests)
Added tag(s) pending.

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

Bug#907149: Bug #907149 in roodi marked as pending

[Cédric Boutillier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/roodi/commit/86762a68a3d2e5be04c50f5b9a1b7e949117


Add upstream patch fto fix outdated test causing build failures (Closes: 
#907149)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/907149

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

[Antonio Terceiro]

Package: ruby-sinatra-contrib
Version: 2.0.5-1
Severity: serious
Justification: unsatisfiable dependencies

# apt install ruby-sinatra-contrib
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ruby-sinatra-contrib : Depends: ruby but it is not going to be installed
Depends: ruby-mustermann (>= 1.0~) but it is not going 
to be installed
Depends: ruby-sinatra (>= 2.0.5~) but it is not going 
to be installed
Depends: ruby-backports (>= 2.8.2) but it is not going 
to be installed
Depends: ruby-tilt (>= 1.3~) but it is not going to be 
installed
Depends: ruby-rack-protection (>= 2.0.5~) but it is not 
going to be installed
Depends: ruby-multi-json but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.


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

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

Versions of packages ruby-sinatra-contrib depends on:
ii  ruby  1:2.5.1
ii  ruby-backports3.11.1-1
ii  ruby-multi-json   1.12.1-1
ii  ruby-rack-protection  1.5.3-2.1
ii  ruby-rack-test0.7.0-1
ii  ruby-sinatra  1.4.8-1
ii  ruby-tilt 2.0.9-1

ruby-sinatra-contrib recommends no packages.

ruby-sinatra-contrib suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#915714: gnustep-base: Please use pkg-config to detect icu

[Yavor Doganov]

Hugh McMaster wrote:
> Control: severity -1 serious
> Control: tags -1 + patch

> As the removal of icu-config from Debian is imminent, I have prepared a
> patch for gnustep-base so its build system uses pkg-config to detect icu.

Thanks for the patch but AFAICT this is a cosmetic issue that
definitely does not warrant RC severity.  Since 1.25.1-2 gnustep-base
is configured with --disable-icu-config so icu-config is not used to
detect ICU.  This was necessary because icu-config has been removed in
icu/59.1-1 but was reintroduced later.

The package builds fine without icu-config so I'm inclined to close
this bug or at least downgrade the severity.

Bug#917990: marked as done (libplplotada1-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 13:21:50 +
with message-id 
and subject line Bug#917990: fixed in plplot 5.14.0+dfsg-2
has caused the Debian Bug report #917990,
regarding libplplotada1-dev: fails to upgrade from 'testing' - trying to 
overwrite /usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali
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.)


-- 
917990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libplplotada1-dev
Version: 5.14.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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 .../libplplotada1-dev_5.14.0+dfsg-1_amd64.deb ...
  Unpacking libplplotada1-dev (5.14.0+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libplplotada1-dev_5.14.0+dfsg-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali', which is 
also in package libplplot-ada-dev:amd64 5.13.0+dfsg-9
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libplplotada1-dev_5.14.0+dfsg-1_amd64.deb


cheers,

Andreas


libplplot-ada-dev=5.13.0+dfsg-9_libplplotada1-dev=5.14.0+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: plplot
Source-Version: 5.14.0+dfsg-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated plplot 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, 02 Jan 2019 13:57:57 +0100
Source: plplot
Binary: libplplot-dev libplplot16 libplplotcxx14 libplplotfortran0 
libplplot-java libcsironn0 libcsirocsa0 libqsastime0 libqsastime-dev 
plplot-driver-xwin plplot-driver-wxwidgets libplplotwxwidgets1 plplot-tcl 
plplot-tcl-bin plplot-tcl-dev plplot-driver-cairo plplot-driver-qt libplplotqt2 
python3-plplot python3-plplot-qt octave-plplot libplplotada4 libplplotada1-dev 
plplot-doc libplplot-ocaml libplplot-ocaml-dev libplplot-lua
Architecture: source
Version: 5.14.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Ole Streicher 
Description:
 libcsirocsa0 - Scientific plotting library (CSIRO csa library)
 libcsironn0 - Scientific plotting library (CSIRO nn library)
 libplplot-dev - Scientific plotting library (development files)
 libplplot-java - Scientific plotting library (Java bindings)
 libplplot-lua - Scientific plotting library (Lua bindings)
 libplplot-ocaml - OCaml bindings for the scientific plotting library
 libplplot-ocaml-dev - OCaml support for the PLplot plotting library 
(development files)
 libplplot16 - Scientific plotting library
 libplplotada1-dev - Ada support for PLplot, a plotting library (development 
files)
 libplplotada4 - Ada support for PLplot, a plotting library
 libplplotcxx14 - Scientific plotting library (C++ binding)
 libplplotfortran0 - Scientific plotting library (fortran bindings)
 libplplotqt2 - Scientific plotting library (Qt bindings)
 libplplotwxwidgets1 - Scientific plotting library (wxWidgets bindings)
 libqsastime-dev - Time format conversion library (development files)
 libqsastime0 - Time format conversion library
 octave-plplot - Octave support for PLplot, a plotting library
 plplot-doc - Documentation for PLplot, a plotting library
 plplot-driver-cairo - Scientific plotting library (Cairo driver)
 plplot-driver-qt - Scientific plotting library (Qt driver)
 plplot-driver-wxwidgets - Scientific plotting 

Bug#912631: marked as done (liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 13:21:26 +
with message-id 
and subject line Bug#912631: fixed in lwjgl 2.9.3+dfsg-5
has caused the Debian Bug report #912631,
regarding liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, 
amd64, mips
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.)


-- 
912631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblwjgl-java-jni
Version: 2.9.3+dfsg-1
Severity: important

Hello,

I was trying to set up my debian for a vintage minecraft test play and I had to 
use not bundled
lwjgl library for it (unsupported architecture). After a quick setup the java 
failed with unsatisfied
link error because of missing symbols in native library. A look into 
liblwjgl.so and a compare with
the bundled version revealed a big differences in library size. The debian one 
is about 37kB and
the bundled one is over 300kB. Some of the missing symbols are: getJNIVersion, 
nLockAWT and many
openGL wrappers. The symbols/native methods calls are present in java classes.

The problem doesn't depend on system architecture (verified on 386, amd64 and 
mipsel) and exists
on actual stretch and sid (probably doesn't depend on this too).

I've tried to compile my local version, but the problem doesn't get resolved. I 
suppose the problem
is in original build system. I've tried to fix the problem with copying all .c 
and .h files into
a single directory at src/native/linux, which resulted in the working version 
of the library.

It seems the build system ignores the (sub)directories other than 
src/native/linux. I'm not familiar
with java development (and ant) nor patching in debian build system so I'm not 
able to make a fix.


Petr Cvek

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

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

Versions of packages liblwjgl-java-jni depends on:
ii  libc62.24-11+deb9u3
ii  libx11-6 2:1.6.4-3
ii  libxcursor1  1:1.1.14-1+deb9u1
ii  libxrandr2   2:1.5.1-1
ii  libxxf86vm1  1:1.1.4-1+b2

liblwjgl-java-jni recommends no packages.

liblwjgl-java-jni suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lwjgl
Source-Version: 2.9.3+dfsg-5

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated lwjgl 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, 28 Dec 2018 22:35:13 +0100
Source: lwjgl
Binary: liblwjgl-java liblwjgl-java-jni liblwjgl-java-doc
Architecture: source
Version: 2.9.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 liblwjgl-java - Lightweight Java Game Library
 liblwjgl-java-doc - Lightweight Java Game Library (javadoc)
 liblwjgl-java-jni - Lightweight Java Game Library (jni)
Closes: 912631
Changes:
 lwjgl (2.9.3+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
   * Fix broken liblwjgl-java-jni package by compiling all needed source files.
 Thanks to Petr Cvek for the report and Le Gall Guillaume for further
 investigations and the patch. (Closes: #912631)
   * Declare compliance with Debian Policy 4.3.0.
   * Override dh_shlibdeps and fix broken link against libjawt.so.
Checksums-Sha1:
 268c71c30e54f111c40416d85e4da19d72297503 2371 lwjgl_2.9.3+dfsg-5.dsc
 cd9de0a7b5c3be3a816ce3b0f6851bb3fdbca8ad 10356 lwjgl_2.9.3+dfsg-5.debian.tar.xz
 eccd7d24035860749075b28771445caad0462aa1 14219 
lwjgl_2.9.3+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 2cb4ab446b8c89a82b6c727037f5f9ddd34e284d30f4bd7582a6f96f51a0ac64 2371 
lwjgl_2.9.3+dfsg-5.dsc
 

Bug#917726: globus-gass-copy: FTBFS: tests failed

[Mattias Ellert]

Hi Lucas.

I have a question regarding your report.

Is it really a requirement that the package build should succeed even
if the user account doing the package build is disabled for logins?

Not accepting remote logins during the build is very reasonable. But a
test that starts a server on the build machine to accept logins from
test scripts running on the same build machine should be allowed.

This has not been a problem before. These tests work fine when building
using pbuilder locally, and there has never been a problem when running
the tests during the builds on the buildd servers either in the past.

Is this a misconfiguration of the FTBFS test build server, or is it
really intended to block logins from localhost to localhost during the
build?

It is not impossible to fix this. The server binary that is used during
the test has an -allow-disabled-logins flag already, so I can add that
to the test wrapper script. But I just wanted to check that this
restriction was really intended before I do this.

Mattias

lör 2018-12-29 klockan 23:26 +0100 skrev Lucas Nussbaum:
> Source: globus-gass-copy
> Version: 10.3-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: buster sid
> Usertags: ftbfs-20181229 ftbfs-buster
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> > # 
> > # error: globus_ftp_client: the server responded with an error
> > # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> The full build log is available from:
>http://aws-logs.debian.net/2018/12/29/globus-gass-copy_10.3-2_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.



smime.p7s
Description: S/MIME cryptographic signature

Bug#915426: git breaks git-remote-hg autopkgtest

[Jonas Smedegaard]

I can do yet another NMU to fix this, but am hesitating as I worry if 
that will masquerade a lack of responsive maintenance.

Please tell if it is sensible that I take over maintenance of this 
package, or join as co-maintainer, or however is appreciated.

Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: Bug #912631 in lwjgl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912631 [liblwjgl-java-jni] liblwjgl-java-jni: Missing symbols in 
liblwjgl.so, stretch-sid, 386, amd64, mips
Ignoring request to alter tags of bug #912631 to the same tags previously set

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

Bug#918014: REMOVE

[John Gates]

Best Regards,

John Gates, CISSP

*Let’s Connect!*

   


On Wed, Jan 2, 2019 at 6:33 AM Dominik George 
wrote:

> Package: apache2
> Version: 2.4.37-1
> Severity: grave
> Justification: renders package unusable
>
> apache2 segfaults on start, but only when started normally through
> systemd.
> Starting apache2 by hand with the samer command line does not result in a
> segfault…
>
> #0  0x7f6049d7c3d0 in ?? () from /usr/lib/apache2/modules/mod_filter.so
> #1  0x7f604a35f088 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x7f604a31ec1a in fork () from /lib/x86_64-linux-gnu/libc.so.6
> #3  0x7f604a464855 in apr_proc_detach () from
> /usr/lib/x86_64-linux-gnu/libapr-1.so.0
> #4  0x7f6049d318a4 in prefork_pre_config (p=,
> plog=, ptemp=) at prefork.c:1272
> #5  0x55c1ddff31be in ap_run_pre_config (pconf=0x7f604a524028,
> plog=0x7f604a1a5028, ptemp=0x7f604a1a9028) at config.c:89
> #6  0x55c1ddfcee5f in main (argc=, argv= out>) at main.c:775
>
> -- Package-specific info:
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing-debug
>   APT policy: (500, 'testing-debug'), (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.19.0-1-amd64 (SMP w/1 CPU core)
> 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)
> LSM: AppArmor: enabled
>
> Versions of packages apache2 depends on:
> ii  apache2-bin2.4.37-1
> ii  apache2-data   2.4.37-1
> ii  apache2-utils  2.4.37-1
> ii  dpkg   1.19.2
> ii  lsb-base   10.2018112800
> ii  mime-support   3.61
> ii  perl   5.28.1-3
> ii  procps 2:3.3.15-2
>
> Versions of packages apache2 recommends:
> ii  ssl-cert  1.0.39
>
> Versions of packages apache2 suggests:
> pn  apache2-doc  
> pn  apache2-suexec-pristine | apache2-suexec-custom  
> ii  firefox-esr [www-browser]60.4.0esr-1
> ii  lynx [www-browser]   2.8.9rel.1-2
>
> Versions of packages apache2-bin depends on:
> ii  libapr1  1.6.5-1+b1
> ii  libaprutil1  1.6.1-3+b1
> ii  libaprutil1-dbd-sqlite3  1.6.1-3+b1
> ii  libaprutil1-ldap 1.6.1-3+b1
> ii  libbrotli1   1.0.7-1
> ii  libc62.28-2
> ii  libcurl4 7.62.0-1
> ii  libjansson4  2.12-1
> ii  libldap-2.4-22.4.47+dfsg-1
> ii  liblua5.2-0  5.2.4-1.1+b2
> ii  libnghttp2-141.35.1-1
> ii  libpcre3 2:8.39-11
> ii  libssl1.11.1.1a-1
> ii  libxml2  2.9.4+dfsg1-7+b3
> ii  perl 5.28.1-3
> ii  zlib1g   1:1.2.11.dfsg-1
>
> Versions of packages apache2-bin suggests:
> pn  apache2-doc  
> pn  apache2-suexec-pristine | apache2-suexec-custom  
> ii  firefox-esr [www-browser]60.4.0esr-1
> ii  lynx [www-browser]   2.8.9rel.1-2
>
> Versions of packages apache2 is related to:
> ii  apache2  2.4.37-1
> ii  apache2-bin  2.4.37-1
>
> -- Configuration Files:
> /etc/apache2/apache2.conf changed [not included]
>
> -- no debconf information
>

Bug#912631: Bug #912631 in lwjgl marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/lwjgl/commit/f57d384523e2a555be440d9dc6cd7648f50377cc


Add add-missing-symbols-in-native-lib-v2.patch.

Readd the missing symbols in lwjgl's native library.

Closes: #912631
Thanks: Petr Cvek for the report and Le Gall Guillaume for the patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912631

Processed: Re: liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #912631 [liblwjgl-java-jni] liblwjgl-java-jni: Missing symbols in 
liblwjgl.so, stretch-sid, 386, amd64, mips
Added tag(s) pending.

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

Bug#912631: liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips

[Markus Koschany]

Control: tags -1 pending

Am 31.12.18 um 06:13 schrieb Le Gall Guillaume:
> Hello,
> 
> 
> and thank you very much for your answer.
> 
> 
> First, about OpenJDK 11, and "debian/patches/javah.patch". You are
> absolutely right to point that out. Actually, I had missed that the
> "javah" tool was removed since OpenJDK 10. Sorry for that.
> 
> I was able to reproduce the same error as the one you showed with
> OpenJDK 11.
> If we take care of a few more C headers include and constant export, it
> works. At least for me.
> Maybe just a thing to note: the path to "libjawt.so" has changed between
> 8 and 11, and we need to remove the "${os.arch}" part when giving that
> path to GCC, in "platform_build/linux_ant/build.xml".
> 
> Please find attached a new version of the patch I proposed, including
> those modifications specific to OpenJDK 11.
> Should you want to try it, please apply after everything else, including
> "javah.patch". (but not the previous version I sent).
> 
> Please let me know if this works for you, or maybe what you think about it.

Thank you for the updated patch. I have applied it and intend to upload
a new revision shortly. However I noticed that something still seems to
be wrong with linking libjawt.so. Your observation that we can remove
the ${os.arch} part is correct. However our debhelper tool dh_shlibdeps
is unable to link libjawt.so into liblwjgl.so. I have to explicitly set
the LD_LIBRARY_PATH in debian/rules when I override dh_shlibdeps but
then I still get a warning:

dpkg-shlibdeps: warning: can't extract name and version from library
name 'libjawt.so'

ldd shows:

ldd /usr/lib/jni/liblwjgl.so

libjawt.so => not found

That is strange to say the least. Let me know if the new version works
for you, otherwise we have to dig deeper into this problem.

> Then, about "OpenGL" and "OpenGL ES": from what I understand they are
> two versions of the same thing.

[...]

Thanks for your explanation!

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#918014: apache2: Segfault in mod_filter only wehen started by systemd

[Dominik George]

Package: apache2
Version: 2.4.37-1
Severity: grave
Justification: renders package unusable

apache2 segfaults on start, but only when started normally through systemd. 
Starting apache2 by hand with the samer command line does not result in a
segfault…

#0  0x7f6049d7c3d0 in ?? () from /usr/lib/apache2/modules/mod_filter.so
#1  0x7f604a35f088 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7f604a31ec1a in fork () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x7f604a464855 in apr_proc_detach () from 
/usr/lib/x86_64-linux-gnu/libapr-1.so.0
#4  0x7f6049d318a4 in prefork_pre_config (p=, 
plog=, ptemp=) at prefork.c:1272
#5  0x55c1ddff31be in ap_run_pre_config (pconf=0x7f604a524028, 
plog=0x7f604a1a5028, ptemp=0x7f604a1a9028) at config.c:89
#6  0x55c1ddfcee5f in main (argc=, argv=) at 
main.c:775

-- Package-specific info:

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/1 CPU core)
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)
LSM: AppArmor: enabled

Versions of packages apache2 depends on:
ii  apache2-bin2.4.37-1
ii  apache2-data   2.4.37-1
ii  apache2-utils  2.4.37-1
ii  dpkg   1.19.2
ii  lsb-base   10.2018112800
ii  mime-support   3.61
ii  perl   5.28.1-3
ii  procps 2:3.3.15-2

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.39

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  firefox-esr [www-browser]60.4.0esr-1
ii  lynx [www-browser]   2.8.9rel.1-2

Versions of packages apache2-bin depends on:
ii  libapr1  1.6.5-1+b1
ii  libaprutil1  1.6.1-3+b1
ii  libaprutil1-dbd-sqlite3  1.6.1-3+b1
ii  libaprutil1-ldap 1.6.1-3+b1
ii  libbrotli1   1.0.7-1
ii  libc62.28-2
ii  libcurl4 7.62.0-1
ii  libjansson4  2.12-1
ii  libldap-2.4-22.4.47+dfsg-1
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libnghttp2-141.35.1-1
ii  libpcre3 2:8.39-11
ii  libssl1.11.1.1a-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  perl 5.28.1-3
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  firefox-esr [www-browser]60.4.0esr-1
ii  lynx [www-browser]   2.8.9rel.1-2

Versions of packages apache2 is related to:
ii  apache2  2.4.37-1
ii  apache2-bin  2.4.37-1

-- Configuration Files:
/etc/apache2/apache2.conf changed [not included]

-- no debconf information

Bug#912593: marked as done (sagemath has unfulfillable build-dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 12:05:04 +
with message-id 
and subject line Bug#912593: fixed in sagemath 8.4-3
has caused the Debian Bug report #912593,
regarding sagemath has unfulfillable build-dependencies
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.)


-- 
912593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sagemath
Version: 8.4-2
Severity: serious
Tags: sid buster

sagemath has unfulfillable build-dependencies. libsingular4, which only
libsingular4m1 is in the archive.

A package should *never* have specific runtime libraries as a dependency, these
should be handled by the corresponding -dev packages.
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.4-3

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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, 02 Jan 2019 11:28:59 +
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese)
 sagemath-doc-pt - Open Source Mathematical Software - documentation 
(Portuguese)
 sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian)
 sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish)
 sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel
Closes: 890231 912593 912980
Changes:
 sagemath (8.4-3) unstable; urgency=medium
 .
   * New (Build-)Depends:
 - gap (>= 4r10p0-3) (Closes: #912980)
 - networkx (>= 2.2)
 - gdb
   * Removed (Build-)Depends:
 - libgap-sage
 - libsingular4 (Closes: #912593)
 - gdb-python2 (Closes: #890231)
   * New patches:
 - u0-gap-util.patch
 - u0-version-gap-4.10.patch  #22626
 - u0-version-networkx-2.2.patch  #26326
 - d0-libgap-path.patch
   * Removed patches:
 - d0-libgap-sage.patch
   * Add lintian overrides for threejs example files with long lines.
   * Allow 90 test failures for 'arch' tests, 10 for 'indep'.
   * Install shlibs.local for libgap.
   * Add lintian override for /usr/lib/*/gap in rpath.
Checksums-Sha1:
 b9282d817e1d38f5f0c31f90e48dd58bb067c7ed 6824 sagemath_8.4-3.dsc
 9985dd3f6ed46badc63e97b4501c4dd57b07dda7 114528 sagemath_8.4-3.debian.tar.xz
 eb5c754d08c2e3af9b5e7e65eda50429165cbb87 28554 sagemath_8.4-3_source.buildinfo
Checksums-Sha256:
 088b45f3d87133a7d781a14ef2768a003b27529a4bf12cb71e73a0135d39271e 6824 
sagemath_8.4-3.dsc
 c271a5672a4910b35980d6827667e605320aeade99507e47e8cae2f763fdef2f 114528 
sagemath_8.4-3.debian.tar.xz
 fadb693716ef2260426a573d8fba15ef088dd791ab36d383b0424fea149fd778 28554 
sagemath_8.4-3_source.buildinfo
Files:
 8d13687519ef0cc821928ff9230de00b 6824 math optional sagemath_8.4-3.dsc
 990405fffe949158e4c7cc48b5ba3afb 114528 math optional 
sagemath_8.4-3.debian.tar.xz
 

Bug#912980: marked as done (sagemath is incompatible with GAP 4.9)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 12:05:04 +
with message-id 
and subject line Bug#912980: fixed in sagemath 8.4-3
has caused the Debian Bug report #912980,
regarding sagemath is incompatible with GAP 4.9
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.)


-- 
912980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sagemath
Version: 8.4-2
Severity: serious
Tags: sid buster
Control: forwarded -1 https://trac.sagemath.org/ticket/22626
Control: block -1 by 912862

gap 4.9.3 was recently uploaded to Debian unstable. sagemath is not yet 
compatible to this version, see upstream bug.
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.4-3

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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, 02 Jan 2019 11:28:59 +
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese)
 sagemath-doc-pt - Open Source Mathematical Software - documentation 
(Portuguese)
 sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian)
 sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish)
 sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel
Closes: 890231 912593 912980
Changes:
 sagemath (8.4-3) unstable; urgency=medium
 .
   * New (Build-)Depends:
 - gap (>= 4r10p0-3) (Closes: #912980)
 - networkx (>= 2.2)
 - gdb
   * Removed (Build-)Depends:
 - libgap-sage
 - libsingular4 (Closes: #912593)
 - gdb-python2 (Closes: #890231)
   * New patches:
 - u0-gap-util.patch
 - u0-version-gap-4.10.patch  #22626
 - u0-version-networkx-2.2.patch  #26326
 - d0-libgap-path.patch
   * Removed patches:
 - d0-libgap-sage.patch
   * Add lintian overrides for threejs example files with long lines.
   * Allow 90 test failures for 'arch' tests, 10 for 'indep'.
   * Install shlibs.local for libgap.
   * Add lintian override for /usr/lib/*/gap in rpath.
Checksums-Sha1:
 b9282d817e1d38f5f0c31f90e48dd58bb067c7ed 6824 sagemath_8.4-3.dsc
 9985dd3f6ed46badc63e97b4501c4dd57b07dda7 114528 sagemath_8.4-3.debian.tar.xz
 eb5c754d08c2e3af9b5e7e65eda50429165cbb87 28554 sagemath_8.4-3_source.buildinfo
Checksums-Sha256:
 088b45f3d87133a7d781a14ef2768a003b27529a4bf12cb71e73a0135d39271e 6824 
sagemath_8.4-3.dsc
 c271a5672a4910b35980d6827667e605320aeade99507e47e8cae2f763fdef2f 114528 
sagemath_8.4-3.debian.tar.xz
 fadb693716ef2260426a573d8fba15ef088dd791ab36d383b0424fea149fd778 28554 
sagemath_8.4-3_source.buildinfo
Files:
 8d13687519ef0cc821928ff9230de00b 6824 math optional sagemath_8.4-3.dsc
 990405fffe949158e4c7cc48b5ba3afb 114528 math optional 
sagemath_8.4-3.debian.tar.xz
 25162fad952c8f6e25694fa1e02cb835 28554 

Bug#916586: marked as done (sagemath: depends on specific libsingular4 which is no longer being built in unstable)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 12:05:04 +
with message-id 
and subject line Bug#912593: fixed in sagemath 8.4-3
has caused the Debian Bug report #912593,
regarding sagemath: depends on specific libsingular4 which is no longer being 
built in unstable
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.)


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

Hello,

I don't know whether this is an easy issue to fix or not (I hope it's
easy).  sagemath currently depends on a very specific version of
libsingular4, but the singular now in unstable only builds
libsingular4m1; as far as I can tell, no source package in unstable
now builds libsingular4.

So sagemath will need to be updated to link to libsingular4m1, if that
is possible.

Thanks for all your work on this package!

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.4-3

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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, 02 Jan 2019 11:28:59 +
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese)
 sagemath-doc-pt - Open Source Mathematical Software - documentation 
(Portuguese)
 sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian)
 sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish)
 sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel
Closes: 890231 912593 912980
Changes:
 sagemath (8.4-3) unstable; urgency=medium
 .
   * New (Build-)Depends:
 - gap (>= 4r10p0-3) (Closes: #912980)
 - networkx (>= 2.2)
 - gdb
   * Removed (Build-)Depends:
 - libgap-sage
 - libsingular4 (Closes: #912593)
 - gdb-python2 (Closes: #890231)
   * New patches:
 - u0-gap-util.patch
 - u0-version-gap-4.10.patch  #22626
 - u0-version-networkx-2.2.patch  #26326
 - d0-libgap-path.patch
   * Removed patches:
 - d0-libgap-sage.patch
   * Add lintian overrides for threejs example files with long lines.
   * Allow 90 test failures for 'arch' tests, 10 for 'indep'.
   * Install shlibs.local for libgap.
   * Add lintian override for /usr/lib/*/gap in rpath.
Checksums-Sha1:
 b9282d817e1d38f5f0c31f90e48dd58bb067c7ed 6824 sagemath_8.4-3.dsc
 9985dd3f6ed46badc63e97b4501c4dd57b07dda7 114528 sagemath_8.4-3.debian.tar.xz
 eb5c754d08c2e3af9b5e7e65eda50429165cbb87 28554 sagemath_8.4-3_source.buildinfo
Checksums-Sha256:
 088b45f3d87133a7d781a14ef2768a003b27529a4bf12cb71e73a0135d39271e 6824 
sagemath_8.4-3.dsc
 c271a5672a4910b35980d6827667e605320aeade99507e47e8cae2f763fdef2f 114528 
sagemath_8.4-3.debian.tar.xz
 

Bug#890231: marked as done (sagemath should use gdb, not gdb-python2, to be removed for buster)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 12:05:04 +
with message-id 
and subject line Bug#890231: fixed in sagemath 8.4-3
has caused the Debian Bug report #890231,
regarding sagemath should use gdb, not gdb-python2, to be removed for buster
to be marked as done.

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

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


-- 
890231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sagemath
Version: 8.2-3
Severity: important
Tags: sid buster

sagemath should use gdb, not gdb-python2, to be removed for buster.  Please
don't introduce new python2 (build) dependencies.
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.4-3

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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, 02 Jan 2019 11:28:59 +
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese)
 sagemath-doc-pt - Open Source Mathematical Software - documentation 
(Portuguese)
 sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian)
 sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish)
 sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel
Closes: 890231 912593 912980
Changes:
 sagemath (8.4-3) unstable; urgency=medium
 .
   * New (Build-)Depends:
 - gap (>= 4r10p0-3) (Closes: #912980)
 - networkx (>= 2.2)
 - gdb
   * Removed (Build-)Depends:
 - libgap-sage
 - libsingular4 (Closes: #912593)
 - gdb-python2 (Closes: #890231)
   * New patches:
 - u0-gap-util.patch
 - u0-version-gap-4.10.patch  #22626
 - u0-version-networkx-2.2.patch  #26326
 - d0-libgap-path.patch
   * Removed patches:
 - d0-libgap-sage.patch
   * Add lintian overrides for threejs example files with long lines.
   * Allow 90 test failures for 'arch' tests, 10 for 'indep'.
   * Install shlibs.local for libgap.
   * Add lintian override for /usr/lib/*/gap in rpath.
Checksums-Sha1:
 b9282d817e1d38f5f0c31f90e48dd58bb067c7ed 6824 sagemath_8.4-3.dsc
 9985dd3f6ed46badc63e97b4501c4dd57b07dda7 114528 sagemath_8.4-3.debian.tar.xz
 eb5c754d08c2e3af9b5e7e65eda50429165cbb87 28554 sagemath_8.4-3_source.buildinfo
Checksums-Sha256:
 088b45f3d87133a7d781a14ef2768a003b27529a4bf12cb71e73a0135d39271e 6824 
sagemath_8.4-3.dsc
 c271a5672a4910b35980d6827667e605320aeade99507e47e8cae2f763fdef2f 114528 
sagemath_8.4-3.debian.tar.xz
 fadb693716ef2260426a573d8fba15ef088dd791ab36d383b0424fea149fd778 28554 
sagemath_8.4-3_source.buildinfo
Files:
 8d13687519ef0cc821928ff9230de00b 6824 math optional sagemath_8.4-3.dsc
 990405fffe949158e4c7cc48b5ba3afb 114528 math optional 
sagemath_8.4-3.debian.tar.xz
 25162fad952c8f6e25694fa1e02cb835 28554 math optional 
sagemath_8.4-3_source.buildinfo

Bug#917727: openhft-lang: FTBFS: [ERROR] /<>/lang/src/main/java/net/openhft/lang/io/IOTools.java:[85, 13] cannot find symbol

[Emmanuel Bourg]

Le 30/12/2018 à 17:29, tony mancill a écrit :

> Given that there aren't many (or any?) r-deps for the openhft libraries,
> I'm tempted to pull the versions in experimental into unstable so we
> have the libraries in buster.  It's either that, or not include these
> packages in buster at all.
> 
> Thoughts?

The OpenHFT libraries are used by Spring (libspring-java), and if I
remember well I had to pick very specific versions to have a consistent
set of compatible libraries. I plan to upgrade Spring to the version 5.1
before the freeze, I'll see at this moment what versions of the OpenHFT
libraries are required.

Emmanuel Bourg

Bug#917576: stegosuite: depends on libswt-gtk2 which is no longer built

[Emmanuel Bourg]

Le 30/12/2018 à 15:45, tony mancill a écrit :

> The issue I am running into is that ${maven:Depends} is injecting an
> unresolvable dependency on "libswt-gtk-4-java (>= 4.x)" and so the
> resulting binary package fails to install with:
> 
> dpkg: dependency problems prevent configuration of stegosuite:
>  stegosuite depends on libswt-gtk-4-java (>= 4.x); however:
>   Version of libswt-gtk-4-java on system is 4.10.0-1.

Hi Tony,

There is an issue with the Maven artifacts for SWT, they are installed
with the versions 'debian' and '4.x', and we've set the
--has-package-version flag stating that the pom and the package have the
same version, which is wrong.

I've fixed that in swt4-gtk/4.10.0-2

Emmanuel Bourg

Bug#917717: [Python-modules-team] Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

[eamanu15]

Hi Joseph!


El mar., 1 de ene. de 2019 a la(s) 21:27, Joseph Herlant (
aerosti...@debian.org) escribió:

> Control: tags -1 - fixed
> Control: tags -1 + patch
> Hi guys,
>
> Thanks Lucas for the report. Sorry for the late reply, I was out of
> the country with very limited internet access.
>
> Thanks Emmanuel for the quick patch.
> Notes for next time:
>  * Please use meaningful commit messages, especially when committing
> to the master branch of a package you don't maintain. Using commit
> messages like "fix issue 917717" makes the commit history harder to
> read and the use of tools like gbp dch impossible as well as rendering
> the gitlab hooks in place for tagging the bugs as pending unusable.
> (If you're not sure about your patches, please just create a MR and
> the maintainer can help getting the patch to a better standard)
>

Ok! I will do it!. What is the meaning of MR?

 * Please conform to the DEP-3 headers when you are writing a quilt
> patch header. See https://dep-team.pages.debian.net/deps/dep3/


I used gbp-pq to create the patch. Maybe, I am using this tool
from a wrong way?


>  * If you have a patch that you thing is good enough for Debian, it's
> generally a good practice to propose it upstream as upstream is
> generally aware of the potential negative impacts and this would avoid
> having to maintain diverging patch hell, especially on packages you
> don't maintain.
>
Ok. Thanks.


>  * Please don't tag bugs as "fixed" as long as there's no NMU uploaded
> (as long as the package is not in the archive). In your case the tag
> "patch" seems more appropriate.
>

Great. thanks

>
> There is an upstream upgrade I need to do so I'll clean the previous
> points and do the upload today or tomorrow.
>
> Thanks,
> Joseph
>
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team


Thanks for your tips. I will keep them in mind :-)

Cheers,


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#918012: docker-compose: invalid version of python3-docker dependency

[Alberto Cortes]

Package: docker-compose
Version: 1.21.0-3~bpo9+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I tried to run docker-compose but it fails:

; docker-compose --version
Traceback (most recent call last):
  File "/usr/bin/docker-compose", line 11, in 
load_entry_point('docker-compose==1.21.0', 'console_scripts', 'docker-
compose')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 561, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2631,
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2291,
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2297,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 22, in

from ..bundle import get_image_digests
  File "/usr/lib/python3/dist-packages/compose/bundle.py", line 13, in 
from .network import get_network_defs_for_service
  File "/usr/lib/python3/dist-packages/compose/network.py", line 8, in 
from docker.types import IPAMConfig
ImportError: No module named 'docker.types'

My version of docker is:

; docker --version
Docker version 18.09.0, build 4d60db4

If I upgrade my python3-docker package from 1.9.0-1 (stretch) to 3.4.1-3~bpo9+1
(stretch-backports) docker-compose
works fine:

; sudo aptitude install -t stretch-backports python3-docker
The following NEW packages will be installed:
  golang-docker-credential-helpers{a} python3-dockerpycreds{a}
The following packages will be upgraded:
  python3-docker
1 packages upgraded, 2 newly installed, 0 to remove and 137 not upgraded.
Need to get 0 B/556 kB of archives. After unpacking 2,190 kB will be used.
Do you want to continue? [Y/n/?]
Reading changelogs... Done
Selecting previously unselected package golang-docker-credential-helpers.
(Reading database ... 244293 files and directories currently installed.)
Preparing to unpack .../golang-docker-credential-
helpers_0.3.0+git20160601.0.5128fa1-1+b2_amd64.deb ...
Unpacking golang-docker-credential-helpers (0.3.0+git20160601.0.5128fa1-1+b2)
...
Selecting previously unselected package python3-dockerpycreds.
Preparing to unpack .../python3-dockerpycreds_0.3.0-1~bpo9+1_all.deb ...
Unpacking python3-dockerpycreds (0.3.0-1~bpo9+1) ...
Preparing to unpack .../python3-docker_3.4.1-3~bpo9+1_all.deb ...
Unpacking python3-docker (3.4.1-3~bpo9+1) over (1.9.0-1) ...
Setting up golang-docker-credential-helpers (0.3.0+git20160601.0.5128fa1-1+b2)
...
Setting up python3-dockerpycreds (0.3.0-1~bpo9+1) ...
Setting up python3-docker (3.4.1-3~bpo9+1) ...

Current status: 137 (-1) upgradable.
;
;
;
;
; docker-compose --version
docker-compose version 1.21.0, build unknown

I believe a fix would be to make docker-compose 1.21.0-3~bpo9+1 depend on
python3-docker version 3.4.1-3~bpo9+1 instead of just depending on an
unversioned python3-docker:

; apt-cache show docker-compose=1.21.0-3~bpo9+1 | grep '^Depends'
Depends: python3-cached-property (>= 1.2.0), python3-docker, python3-dockerpty
(>= 0.4.1), python3-docopt (>= 0.6.1), python3-jsonschema, python3-requests (>=
2.6.1), python3-six (>= 1.3.0), python3-six (<< 2), python3-texttable (>=
0.9.0), python3-websocket (>= 0.32.0), python3-yaml (>= 3.10), python3:any (>=
3.5~)



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

Kernel: Linux 4.9.0-8-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)

Versions of packages docker-compose depends on:
ii  python3  3.5.3-1
ii  python3-cached-property  1.3.0-2
ii  python3-docker   1.9.0-1
ii  python3-dockerpty0.4.1-1
ii  python3-docopt   0.6.2-1
ii  python3-jsonschema   2.5.1-6
ii  python3-requests 2.12.4-1
ii  python3-six  1.10.0-3
ii  python3-texttable1.5.0-1~bpo9+1
ii  python3-websocket0.37.0-2
ii  python3-yaml 3.12-1

Versions of packages docker-compose recommends:
pn  docker.io  

docker-compose suggests no packages.

-- no debconf information

Bug#917650: FTBFS: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier]

[Steve McIntyre]

On Wed, Jan 02, 2019 at 11:28:19AM +0200, Timo Lindfors wrote:
>Hi,
>
>On Sat, 29 Dec 2018, Steve McIntyre wrote:
>> Package: src:qi
>> Version: 2013-1
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the 
>> past)
>
>thanks for working on ARM support (much appreciated!). At this point I'm
>considering dropping qi completely since upstream is dead and I have also
>migrated away from the openmoko gta02 phone three years ago. If somebody
>wants to get qi they can easily get the binary from archive.debian.org.

ACK. I did wonder about that when I looked on tracker - it's been a
while since anybody had to play with this stuff, clearly.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis

Bug#915337: marked as done (rr: baseline violation on i386)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 11:19:42 +
with message-id 
and subject line Bug#915337: fixed in rr 5.2.0-4
has caused the Debian Bug report #915337,
regarding rr: baseline violation on i386
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.)


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

MMX and SSE are not part of the i386 baseline.
--- End Message ---
--- Begin Message ---
Source: rr
Source-Version: 5.2.0-4

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated rr 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, 02 Jan 2019 12:02:08 +0100
Source: rr
Binary: rr
Architecture: source
Version: 5.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 rr - application execution recorder, player and debugger
Closes: 915337
Changes:
 rr (5.2.0-4) unstable; urgency=medium
 .
   * Build only on amd64, since the i386 package isn’t aligned with the
 i386 “baseline”. Closes: #915337.
   * Switch to C++14 for C++ code, as required by capnproto 0.7.
   * Standards-Version 4.3.0, no change required.
Checksums-Sha1:
 eecedf2dd9363c1100f8fd9326f644ccee36741b 1858 rr_5.2.0-4.dsc
 7474b402b506e3b6f96e060f245e1f589f580d3e 9316 rr_5.2.0-4.debian.tar.xz
 694c02eba5ba1ea10da182974968b78bd9d29e7c 8994 rr_5.2.0-4_source.buildinfo
Checksums-Sha256:
 2671b4f94cbff56870b1c883ae5a31d05bb63d031bb408b2e3c8164a3c8ebcd4 1858 
rr_5.2.0-4.dsc
 9b6d325fd4cdde502909447b64afe2a9c08fa22d17cd6c6ecc2e5829397211d8 9316 
rr_5.2.0-4.debian.tar.xz
 9a4532b3ffa5956a281d7f63daed2d92772cdc91ffec1ba8d565eb43d4cd2293 8994 
rr_5.2.0-4_source.buildinfo
Files:
 1e2bf5f307c1881cb4b36ee3cf0199ef 1858 devel optional rr_5.2.0-4.dsc
 1d6cac0577edf0b9c22006280e9b6aac 9316 devel optional rr_5.2.0-4.debian.tar.xz
 979d8d3f7765f3beb1bd528c99cfac0f 8994 devel optional 
rr_5.2.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlwsmjsACgkQgNMC9Yht
g5x0PQ//eRbkqSrR4UGc8ykGKeWwsoyX8eINTrBk4imSjMq0hBXS1BeZRtVOmlJ7
73dhVmr6OvTtw07IvhaCFAj+ztB5yGQp8/oTYQ7hNgepz5Kg/jGxKAXU/QKaxJ4y
u/8fj+EPaKJvsSIUGPxZpfwo8iulvg45tO3E4hvyRV49nDS48y/L6+zE9HV8SYhq
FZUf7m3KcSR1KyeFV+cL8BXDz6IYSa/S6tF6RxD842jLYK+KIEmybaRvwurbOLeT
3+DSE0+9HcH02+KsjC3ndBggUw13q/hRo5nHUT0eqYyUdZgHeCcYm/uZkX+ltwSU
qqsjkRjGfoiBubLjhHN2nmwsE3mjSIf4eVCA6p+E/gf3pSOZ7HHagagZEzVJfqgl
TJq9Qown6c4sdvWTiPjcTs+ctHgbfGvuiXhgEj2+R8iWVEBWY/VbsNvABPolTKOi
xxPHZOXVOgJeuj/PTGEvfqAXWnCofL+g/qENHpNRlol+5JNTN4DCp5ud3xATN9+e
5aN2qqNrq0jZI3qPPH9TxXZB8MQZSzTE2JhbDZi4+C3sfH+sPa0PuGSYqfhETj09
qh3C13IPB41y/5W52MZjZ28l9uQFnWvfjfCx00GFe2qQEnEfeUTtUOsZLU/VqZKT
UyEVrTKr3VZ/meStMN9aijafemsp7RRjjh8qL0eOqmaslNY+2fc=
=UA2H
-END PGP SIGNATURE End Message ---

Bug#916262: marked as done (staden-io-lib: data/xx#unsorted.sam fails randomly)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 11:19:50 +
with message-id 
and subject line Bug#916262: fixed in staden-io-lib 1.14.11-6
has caused the Debian Bug report #916262,
regarding staden-io-lib: data/xx#unsorted.sam fails randomly
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.)


-- 
916262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: staden-io-lib
Version: 1.14.11-5
Severity: serious
Tags: ftbfs
Control: block 912272 by -1

https://buildd.debian.org/status/package.php?p=staden-io-lib
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/staden-io-lib.html

...
=== testing ./data/xx#unsorted.sam ===
 ../progs/scramble  ./data/xx#unsorted.sam test.out/xx#unsorted.bam
 ../progs/scramble  -r ./data/xx.fa test.out/xx#unsorted.bam 
test.out/xx#unsorted.full.cram
 ../progs/scramble  test.out/xx#unsorted.bam > test.out/tmp.sam
 ../progs/scramble  test.out/xx#unsorted.full.cram > 
test.out/xx#unsorted.full.sam
 ../progs/scramble  -O bam test.out/xx#unsorted.full.cram > 
test.out/xx#unsorted.full.bam
 ../progs/scramble  test.out/xx#unsorted.full.bam test.out/tmp.sam
./compare_sam.pl --nopg test.out/xx#unsorted.full.sam 
test.out/xx#unsorted.full.bam.sam
 ../progs/scramble  -x -r ./data/xx.fa test.out/xx#unsorted.bam 
test.out/xx#unsorted.full.cram
 ../progs/scramble  test.out/xx#unsorted.full.cram > 
test.out/xx#unsorted.full.sam
./compare_sam.pl --unknownrg ./data/xx#unsorted.sam 
test.out/xx#unsorted.full.bam.sam

../progs/scramble -H -r ./data/ce.fa test.out/ce#sorted.full.cram
No region:   1024176
FAIL: scram.test
...
=== testing ./data/xx#unsorted.sam ===
 ../progs/scramble -t4 ./data/xx#unsorted.sam test.out/xx#unsorted.bam
 ../progs/scramble -t4 -r ./data/xx.fa test.out/xx#unsorted.bam 
test.out/xx#unsorted.full.cram
 ../progs/scramble -t4 test.out/xx#unsorted.bam > test.out/tmp.sam
 ../progs/scramble -t4 test.out/xx#unsorted.full.cram > 
test.out/xx#unsorted.full.sam
 ../progs/scramble -t4 -O bam test.out/xx#unsorted.full.cram > 
test.out/xx#unsorted.full.bam
 ../progs/scramble -t4 test.out/xx#unsorted.full.bam test.out/tmp.sam
./compare_sam.pl --nopg test.out/xx#unsorted.full.sam 
test.out/xx#unsorted.full.bam.sam
 ../progs/scramble -t4 -x -r ./data/xx.fa test.out/xx#unsorted.bam 
test.out/xx#unsorted.full.cram
 ../progs/scramble -t4 test.out/xx#unsorted.full.cram > 
test.out/xx#unsorted.full.sam
./compare_sam.pl --unknownrg ./data/xx#unsorted.sam 
test.out/xx#unsorted.full.bam.sam

../progs/scramble -t4 -H -r ./data/ce.fa test.out/ce#sorted.full.cram
No region:   1024176
FAIL: scram_mt.test
...


data/xx#unsorted.sam seems to fail randomly, with failures and passes
seen on the same architecture (including amd64).
--- End Message ---
--- Begin Message ---
Source: staden-io-lib
Source-Version: 1.14.11-6

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated staden-io-lib 
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, 02 Jan 2019 03:08:23 -0800
Source: staden-io-lib
Binary: staden-io-lib-utils libstaden-read-dev libstaden-read13 
staden-io-lib-examples
Architecture: source
Version: 1.14.11-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 libstaden-read-dev - development files for libstaden-read
 libstaden-read13 - Staden library for reading and writing DNA sequencing 
results
 staden-io-lib-examples - programs for manipulating DNA sequencing files (usage 
examples)
 staden-io-lib-utils - programs for manipulating DNA sequencing files
Closes: 916262
Changes:
 staden-io-lib (1.14.11-6) unstable; urgency=medium
 .
   * Switch to -O0 on armhf, mips. Closes: #916262
   * Standards-Version: 4.3.0
   * debian/control: mark staden-io-lib-examples as Multi-Arch: foreign
   * changelog & debian/patches/spelling: typo fix (independent)

Bug#904422: Bumped severity

[Pirate Praveen]

Control: severity -1 important

On Wed, 2 Jan 2019 10:57:31 +0100 Ruben Undheim
 wrote:
> Bumped the severity since now nodejs 10 is in unstable.

I don't think this warrants an rc bug. It is only a warning and does not
affect npm functionality or violates any policy. Serious bugs are for
packages violating debian policy, please site which section of the
policy it is violating if you would like to keep it as serious.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bumped severity

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #904422 [npm] npm: complains about too-new nodejs
Severity set to 'important' from 'serious'

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

Bug#916115: marked as done (389-ds-base: Please use pkg-config to detect icu)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 11:04:12 +
with message-id 
and subject line Bug#916115: fixed in 389-ds-base 1.4.0.19-3
has caused the Debian Bug report #916115,
regarding 389-ds-base: Please use pkg-config to detect icu
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.)


-- 
916115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 389-ds-base
Version: 1.4.0.19-2
Severity: normal

Dear Maintainer,

icu-config has been deprecated by its upstream developers for some years now.
In icu 63.1, icu-config is optional to install, but installed by default. In
the next version, icu-config will no longer be installed by default.

The developers recommend downstream packages use pkg-config to detect the icu
libraries.

Debian will remove icu-config from libicu-dev shortly. Hence, the need to
switch to pkg-config.

Please let me know if you need any help with this change.



-- 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-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: 389-ds-base
Source-Version: 1.4.0.19-3

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated 389-ds-base 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, 02 Jan 2019 12:43:23 +0200
Source: 389-ds-base
Binary: 389-ds 389-ds-base-libs 389-ds-base-dev 389-ds-base python3-lib389 
cockpit-389-ds
Architecture: source
Version: 1.4.0.19-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 389-ds - 389 Directory Server suite - metapackage
 389-ds-base - 389 Directory Server suite - server
 389-ds-base-dev - 389 Directory Server suite - development files
 389-ds-base-libs - 389 Directory Server suite - libraries
 cockpit-389-ds - Cockpit user interface for 389 Directory Server
 python3-lib389 - Python3 module for accessing and configuring the 389 
Directory Se
Closes: 916115 916118
Changes:
 389-ds-base (1.4.0.19-3) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI.
   * Trim trailing whitespace.
   * Use secure URI in Vcs control header.
 .
   [ Hugh McMaster ]
   * control: Mark 389-ds-base-libs{,-dev} M-A: same, cockpit-389-ds M-A:
 foreign and arch:all. (Closes: #916118)
   * Use pkg-config to detect icu. (Closes: #916115)
Checksums-Sha1:
 4be19898707808163a86f47a61b515185a4b3e75 2642 389-ds-base_1.4.0.19-3.dsc
 18862df4e32d6b240aba12243138222b2a5a35c0 445676 
389-ds-base_1.4.0.19-3.debian.tar.xz
 1e90fadb0ddc49876d217a1d4f0e26afdd7f68be 7842 
389-ds-base_1.4.0.19-3_source.buildinfo
Checksums-Sha256:
 701fa45cf47d1a1b3c7e4b034aee65410266ce06d684ea6498ab737a9f0120a1 2642 
389-ds-base_1.4.0.19-3.dsc
 4e4a919d49a1f9235c7a4d71dc9c506fa70944c52d61d99f3ee82f349e03de40 445676 
389-ds-base_1.4.0.19-3.debian.tar.xz
 3ef3bc0cd841f3bcd5e07bde39033926901dca80ce6b3566963d6994d6fafcaa 7842 
389-ds-base_1.4.0.19-3_source.buildinfo
Files:
 62d3588bc1ebbda499b8937bc92d5b3a 2642 net optional 389-ds-base_1.4.0.19-3.dsc
 0d98c6bb1e85b2b03144290b295757bc 445676 net optional 
389-ds-base_1.4.0.19-3.debian.tar.xz
 3c8ee181dd3c9aab96b6f1a7e6c4ce83 7842 net optional 
389-ds-base_1.4.0.19-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlwslikACgkQy3AxZaiJ
hNy6YQ//VLClP+8o1bAXXqXwYOxIwaRT6yDIf7GU16WVCrLzA3Z83w/c7eeoI77z
U1awI3Zjs9jeNLxrC4JrBmHCKhF+GQrmuiOsfBaKIKfObbdlsellPiCclTvOEOtk
4aTNfpGF+S/d60NlQfomRKkhWl/VCLCVXNjJENt8jfBDVry1FkkK0LjFLp7Q0trc

Processed: Bumping severity

[Debian Bug Tracking System]

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

> severity 904422 serious
Bug #904422 [npm] npm: complains about too-new nodejs
Severity set to 'serious' from 'minor'
> stop
Stopping processing here.

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

Bug#917650: FTBFS: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier]

[Timo Lindfors]

Hi,

On Sat, 29 Dec 2018, Steve McIntyre wrote:

Package: src:qi
Version: 2013-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)


thanks for working on ARM support (much appreciated!). At this point I'm 
considering dropping qi completely since upstream is dead and I have also 
migrated away from the openmoko gta02 phone three years ago. If somebody 
wants to get qi they can easily get the binary from archive.debian.org.


-Timo