date:20190220

Hi,

On Fri, Feb 08, 2019 at 08:54:46AM +0100, bitfreak25 wrote:
> I want to mention that I there is still a patch here that prevents the
> package from autoremoval on 22 February.

I think my response will reset the counter for the testing autoremoval.

> Maybe my last message was a bit confusing. The patch I've added removes 
> the random ingame pause.

I will apply the patch and do a team upload.  Since I can not see any
activity of Colin Tuckley I think it might be a good idea to move the
package to Debian Games team.  Colin, if I do not hear from you I assume
you are OK with this if I put you as Uploader.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#922805: strophejs: FTBFS (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js)

2019-02-20 Thread Juhani Numminen

Dear maintainer,

On Wed, 20 Feb 2019 22:10:55 + Santiago Vila  wrote:

> make[1]: Entering directory '/<>/strophejs-1.2.14+dfsg'
> node /usr/lib/nodejs/requirejs/r.js -o build.js 
> name=/usr/lib/nodejs/node-almond/almond.js insertRequire=strophe-polyfill 
> include=strophe-polyfill out=strophe.min.js
> Error: Error: ERROR: module path does not exist: 
> /usr/lib/nodejs/node-almond/almond.js for module named: 
> /usr/lib/nodejs/node-almond/almond.js. Path is relative to: 
> /<>/strophejs-1.2.14+dfsg

It seems that /usr/lib/nodejs/node-almond/ was recently changed to
/usr/lib/nodejs/almond/. See https://bugs.debian.org/920929 .

Regards,
Juhani

Processed: affects 915559

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

> affects 915559 fakechroot dash
Bug #915559 [coreutils] coreutils: Use renameat2 from glibc instead of syscall
Added indication that 915559 affects fakechroot and dash
> thanks
Stopping processing here.

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

Bug#919007: marked as done (Needs to be updated for libexempi8)

Your message dated Thu, 21 Feb 2019 05:19:22 +
with message-id 
and subject line Bug#921714: Removed package(s) from unstable
has caused the Debian Bug report #919007,
regarding Needs to be updated for libexempi8
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.)


-- 
919007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xmp-toolkit
Version: 2.0.1+git20140309.5437b0a-5
Severity: serious

Hi,

libexempi bumped its soname from 3 → 8.
The transition is tracked at
https://release.debian.org/transitions/html/auto-exempi.html
and via #918687.

I tried updating the package with the attached patch, but this triggers
test-suite failures (see build.log).

Unfortunately I don't know enough Python to fix this myself.

Regards,
Michael


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

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog
--- python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog   
2017-06-19 19:40:03.0 +0200
+++ python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog   
2019-01-11 17:22:13.0 +0100
@@ -1,3 +1,9 @@
+python-xmp-toolkit (2.0.1+git20140309.5437b0a-6) UNRELEASED; urgency=medium
+
+  * Update to libexempi8
+
+ -- Michael Biebl   Fri, 11 Jan 2019 17:22:13 +0100
+
 python-xmp-toolkit (2.0.1+git20140309.5437b0a-5) unstable; urgency=medium
 
   * Orphaning package:
diff -Nru python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control
--- python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control 2017-06-19 
19:39:58.0 +0200
+++ python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control 2019-01-11 
17:21:55.0 +0100
@@ -5,7 +5,7 @@
 Build-Depends:
  debhelper (>= 9),
  dh-python,
- libexempi3 (>= 2.2.0),
+ libexempi8 (>= 2.2.0),
  python-all,
  python-mock,
  python-setuptools,
@@ -25,7 +25,7 @@
 Package: python-libxmp
 Architecture: all
 Depends:
- libexempi3,
+ libexempi8,
  ${misc:Depends},
  ${python:Depends}
 Suggests:
@@ -43,7 +43,7 @@
 Package: python3-libxmp
 Architecture: all
 Depends:
- libexempi3,
+ libexempi8,
  ${misc:Depends},
  ${python3:Depends}
 Suggests:
diff -Nru 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
--- 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
2017-01-22 18:29:41.0 +0100
+++ 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
2019-01-11 17:22:13.0 +0100
@@ -18,7 +18,7 @@
  Loads exempi library.
  """
 -path = ctypes.util.find_library('exempi')
-+path = 'libexempi.so.3'
++path = 'libexempi.so.8'
  if path is None:
  if platform.system().startswith('Darwin'):
  if os.path.exists('/opt/local/lib/libexempi.dylib'):
[0mI: Copying COW directory[0m
[0mI: forking: rm -rf /var/cache/pbuilder/build/cow.13636[0m
[0mI: forking: cp -al /var/cache/pbuilder/sid.cow 
/var/cache/pbuilder/build/cow.13636[0m
[0mI: removed stale ilistfile /var/cache/pbuilder/build/cow.13636/.ilist[0m
[0mI: forking: chroot /var/cache/pbuilder/build/cow.13636 
cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type 
l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''[0m
[0mI: Invoking pbuilder[0m
[0mI: forking: pbuilder build --buildplace /var/cache/pbuilder/build/cow.13636 
--buildresult /var/cache/pbuilder/result/ --mirror 
http://ftp.de.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.13636 cow-shell' 
/home/michael/debian/build-area/python-xmp-toolkit/python-xmp-toolkit_2.0.1+git20140309.5437b0a-6.dsc[0m
[0mI: Running in no-targz mode[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Fri Jan 11 17:39:00 CET 2019[0m
[0mI: pbuilder-time-stamp: 1547224740[0

Bug#922730: i686 only

2019-02-20 Thread 積丹尼 Dan Jacobson

i686 only. Works fine on x86_64.

Bug#922806: chromium-driver: Cannot start browser through python-selenium.

reassign 922806 python-selenium
severity 922806 important
thanks

On Wed, Feb 20, 2019 at 11:19:53PM +0100, Jens- Birger Schlie wrote:
> Package: chromium-driver
> Version: 70.0.3538.110-1~deb9u1
> Severity: grave
> Justification: renders package unusable
> 
> Before this worked like a bliss.
> 
> Some research showed the chromium-driver was upgraded this morning from
> 70.0.3538.110 to 72.0.3626.96-1~deb9u1.
> 
> After downgrading back to 70.0.3538.110 the test tool is working again.

Chromium is a moving target, it doesn't provide any API guarantees for
external instrumentation tools. You'll need to upgrade Selenium (or
the Python bindings for it) to adapt to newer versions.

Cheers,
Moritz

Bug#828441: moonshot-trust-router: FTBFS with openssl 1.1.0

On Wed, Feb 20, 2019 at 05:30:35PM -0500, Sam Hartman wrote:
> Is it possible to remove openssl and make moonshot-trust-router
> uninstallable?

That might be possible, I'll check with the FTP masters.

Cheers,
Moritz

Processed: Re: chromium-driver: Cannot start browser through python-selenium.

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

> reassign 922806 python-selenium
Bug #922806 [chromium-driver] chromium-driver: Cannot start browser through 
python-selenium.
Bug reassigned from package 'chromium-driver' to 'python-selenium'.
No longer marked as found in versions chromium-browser/70.0.3538.110-1~deb9u1.
Ignoring request to alter fixed versions of bug #922806 to the same values 
previously set
> severity 922806 important
Bug #922806 [python-selenium] chromium-driver: Cannot start browser through 
python-selenium.
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#922806: chromium-driver: Cannot start browser through python-selenium.

2019-02-20 Thread Jens- Birger Schlie

Package: chromium-driver
Version: 70.0.3538.110-1~deb9u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when using my page test tool, which is using python-selenium, I could no longer
start the browser.

There was an error message thrown by the python selenium binding:

"Traceback (most recent call last):
  File "./TestRunner.py", line 166, in 
pr.init()
  File "/home/forky/source/mdl_shop_test/telluriumShell/running/context.py",
line 149, in init
self.driver = webdriver.Chrome(executable_path="/usr/bin/chromedriver")
  File "/usr/lib/python2.7/dist-
packages/selenium/webdriver/chrome/webdriver.py", line 67, in __init__
desired_capabilities=desired_capabilities)
  File "/usr/lib/python2.7/dist-
packages/selenium/webdriver/remote/webdriver.py", line 91, in __init__
self.start_session(desired_capabilities, browser_profile)
  File "/usr/lib/python2.7/dist-
packages/selenium/webdriver/remote/webdriver.py", line 173, in start_session
'desiredCapabilities': desired_capabilities,
  File "/usr/lib/python2.7/dist-
packages/selenium/webdriver/remote/webdriver.py", line 233, in execute
self.error_handler.check_response(response)
  File "/usr/lib/python2.7/dist-
packages/selenium/webdriver/remote/errorhandler.py", line 194, in
check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome
failed to start: exited abnormally
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/chromium is no longer
running, so ChromeDriver is assuming that Chrome has crashed.)
  (Driver info: chromedriver=72.0.3626.96,platform=Linux 4.9.0-8-amd64 x86_64)
"

Before this worked like a bliss.

Some research showed the chromium-driver was upgraded this morning from
70.0.3538.110 to 72.0.3626.96-1~deb9u1.

After downgrading back to 70.0.3538.110 the test tool is working again.



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

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

Versions of packages chromium-driver depends on:
ii  chromium 70.0.3538.110-1~deb9u1
ii  libatomic1   6.3.0-18+deb9u1
ii  libc62.24-11+deb9u4
ii  libdrm2  2.4.74-1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.0-2+deb9u1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libicu57 57.1-6+deb9u2
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1.1+deb9u1
ii  libpng16-16  1.6.28-1
ii  libstdc++6   6.3.0-18+deb9u1
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libwebpmux2  0.5.2-1
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libx11-xcb1  2:1.6.4-3+deb9u1
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-1+deb9u2
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.8.dfsg-5

chromium-driver recommends no packages.

chromium-driver suggests no packages.

-- no debconf information

Bug#828441: moonshot-trust-router: FTBFS with openssl 1.1.0

2019-02-20 Thread Sam Hartman

Status is that I didn't find the time to get moonshot-trust-router dealt
with before buster and so I had deprioritized it.
There is in fact a new upstream, and it does fix the issue.
Blocking on moonshot-trust-router is silly: no one wants the version in
unstable anyway.
Is it possible to remove openssl and make moonshot-trust-router
uninstallable?
In my mind the only reason to keep moonshot-trust-router around now is
to avoid needing to take a trip through new again when I do fix it post
buster.

If you really need me to go deal with moonshot-trust-router now, I'll do
that, but my preference for my Debian time is to focus on buster
issues.

Bug#828441: moonshot-trust-router: FTBFS with openssl 1.1.0

On Fri, Oct 13, 2017 at 12:24:26AM -0400, Sam Hartman wrote:
> There's a new upstream for moonshot-trust-router that I believe should
> work with openssl 1.1.
> Realistically, I should be able to deal with moonshot-gss-eap #848680
> within a month.
> I think it may be more like two months to deal with both
> moonshot-gss-eap and moonshot-trust-router, both of which have new
> upstreams.
> Right now, neither is in testing.  I expect Buster to be the first
> release to include moonshot-trust-router and definitely plan to get
> moonshot-gss-eap back into testing for Buster, but I'm not bothered if
> moonshot-trust-router spends a month FTBFS because you remove openssl
> 1.0.

What's the status? We're down to five packages still blocking the removal
of OpenSSL 1.0 and moonshot-trust-router is one of them.

Cheers,
Moritz

Bug#915805: Should this package be removed?

On Tue, Jan 15, 2019 at 10:31:17AM +, Kevin Smith wrote:
> On 27 Dec 2018, at 22:52, Moritz Mühlenhoff  wrote:
> > 
> > On Fri, Dec 07, 2018 at 01:41:47PM +, Kevin Smith wrote:
> >> Apologies, I’d forgotten that we’d prepared an update from upstream and 
> >> not gotten it submitted. We’ll try to address this in the next week or so.
> > 
> > What's the status :-)
> 
> I’m sitting with packages in front of me, I need to test them, and then 
> remember what to do next :)

Please sort this out ASAP, we're down to five packages depending on OpenSSL 1.0
and those will simply be removed along in a few weeks tops.

Cheers,
Moritz

Bug#922804: makehuman: FTBFS (Could not import extension sphinx.ext.pngmath)

2019-02-20 Thread Santiago Vila

Package: src:makehuman
Version: 1.1.1-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 --with python2 --with quilt
   dh_quilt_patch -i
Applying patch 01_makehuman.py.patch
patching file makehuman/makehuman.py

Now at patch 01_makehuman.py.patch
   dh_update_autotools_config -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Building docs
sh debian/scripts/gendoc.sh
Creating API documentation
make[2]: Entering directory '/<>/docs/sphinx'
sphinx-build -b html -d build/doctrees  -D html_last_updated_fmt="June 24, 
2017" source build/html
Running Sphinx v1.8.3
WARNING: while setting up extension matplotlib.sphinxext.mathmpl: directive 
u'math' is already registered, it will be overridden

Extension error:
Could not import extension sphinx.ext.pngmath (exception: No module named 
pngmath)
make[2]: *** [Makefile:40: html] Error 2
make[2]: Leaving directory '/<>/docs/sphinx'
make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:3: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#922805: strophejs: FTBFS (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js)

2019-02-20 Thread Santiago Vila

Package: src:strophejs
Version: 1.2.14+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/strophejs-1.2.14+dfsg'
node /usr/lib/nodejs/requirejs/r.js -o build.js 
name=/usr/lib/nodejs/node-almond/almond.js insertRequire=strophe-polyfill 
include=strophe-polyfill out=strophe.min.js
Error: Error: ERROR: module path does not exist: 
/usr/lib/nodejs/node-almond/almond.js for module named: 
/usr/lib/nodejs/node-almond/almond.js. Path is relative to: 
/<>/strophejs-1.2.14+dfsg
at /usr/lib/nodejs/requirejs/r.js:28446:35

make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>/strophejs-1.2.14+dfsg'
make: *** [debian/rules:14: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#859553: pidentd: Please migrate to openssl1.1 in buster

On Wed, Feb 20, 2019 at 08:51:16AM +0100, Moritz Muehlenhoff wrote:
> On Wed, Feb 20, 2019 at 12:28:48AM +0100, Sebastian Andrzej Siewior wrote:
> > On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote:
> > > this is a remainder about the openssl transition [0]. We really want to
> > > remove libssl1.0-dev from unstable for Buster. I will raise the severity
> > > of this bug to serious in a month. Please react before that happens.
> > 
> > There has been no action on pidentd and it is out of testing during
> > soft-freeze. Should there be a RM bug filled? We do have alternative
> > ident daemons in the archive. This package is holding back the removal
> > of openssl 1.0.2 in the archive.
> 
> Or alternatively we can simply drop the idecrypt binary package, and remove
> --with-des* from the configure (and the build dep). I doubt anyone really
> uses the DES feature of ident...

Like the attached patch.

Cheers,
Moritz
diff -Nru pidentd-3.0.19.ds1/debian/changelog 
pidentd-3.0.19.ds1/debian/changelog
--- pidentd-3.0.19.ds1/debian/changelog 2016-11-25 18:27:16.0 +0100
+++ pidentd-3.0.19.ds1/debian/changelog 2019-02-20 23:02:49.0 +0100
@@ -1,3 +1,11 @@
+pidentd (3.0.19.ds1-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove DES support and the idecrypt package, incompatible with
+OpenSSL 1.1 (Closes: #859553)
+
+ -- Moritz Muehlenhoff   Wed, 20 Feb 2019 23:02:49 +0100
+
 pidentd (3.0.19.ds1-8) unstable; urgency=medium
 
   * Fix uses-deprecated-compression-for-data-tarball.
diff -Nru pidentd-3.0.19.ds1/debian/control pidentd-3.0.19.ds1/debian/control
--- pidentd-3.0.19.ds1/debian/control   2016-11-25 18:23:17.0 +0100
+++ pidentd-3.0.19.ds1/debian/control   2019-02-20 23:02:49.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Anibal Monsalve Salazar 
 Standards-Version: 3.9.8
-Build-Depends: autotools-dev, debhelper (>= 7), libssl1.0-dev | libssl-dev (<< 
1.1.0~), linux-libc-dev (>= 2.6.16)
+Build-Depends: autotools-dev, debhelper (>= 7), linux-libc-dev (>= 2.6.16)
 Homepage: http://www.lysator.liu.se/~pen/pidentd/
 
 Package: pidentd
@@ -14,18 +14,6 @@
 Replaces: netstd, pidentd-des (<< 3.0.14)
 Priority: optional
 Section: net
-Description: TCP/IP IDENT protocol server with DES support
+Description: TCP/IP IDENT protocol server
  Identd is a server which implements the TCP/IP proposed standard IDENT user
  identification protocol as specified in the RFC 1413 document.
- .
- This package has been built with DES support.
-
-Package: idecrypt
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Replaces: pidentd-des (<< 3.0.14)
-Priority: optional
-Section: utils
-Description: decrypt an encrypted response from pidentd
- This package contains the idecrypt(8) utility which is used to decrypt
- encrypted responses from a pidentd server with DES encryption turned on.
diff -Nru pidentd-3.0.19.ds1/debian/idecrypt.8 
pidentd-3.0.19.ds1/debian/idecrypt.8
--- pidentd-3.0.19.ds1/debian/idecrypt.82008-09-23 11:48:19.0 
+0200
+++ pidentd-3.0.19.ds1/debian/idecrypt.81970-01-01 01:00:00.0 
+0100
@@ -1,50 +0,0 @@
-.\" $Id: idecrypt.8,v 1.1 2000/04/28 22:44:01 herbert Exp $
-.\" Copyright (c) 2000 Herbert Xu 
-.\" This manual page is released into the public domain."
-.TH idecrypt 8 "28 Apr 2000"
-.SH NAME
-idecrypt \- Encrypted IDENT response decryption utility
-.SH SYNOPSIS
-.B idecrypt
-[\fIfile\fR]...
-.SH DESCRIPTION
-.B Idecrypt
-decrypts authentication tokens returned by an
-.BR identd (8)
-server that supports encryption.  The tokens can be supplied in
-.IR file ,
-or from the standard input.  The decrypted tokens are displayed
-on the standard output.
-.PP
-This program will attempt to decrypt a token with all
-the keys stored in the key file until it succeeds (or have tried
-all the keys).
-.SH FILES
-.TP
-.B /etc/identd.key
-If compiled with
-.I DES
-encryption enabled, the 1024 first bytes of this file is used to specify
-the secret key for encrypting replies.
-.SH AVAILABILITY
-The daemon is free software. You can redistribute it and/or
-modify it as you wish - as long as you don't claim that you wrote
-it.
-.PP
-The source code for the latest version of the daemon can always be
-FTP'd from one of the following addresses:
-.TP 12
-.B Main site:
-ftp://ftp.lysator.liu.se/pub/ident/servers/
-.TP 12
-.B Mirror:
-ftp://ftp.uu.net/networking/ident/servers/
-.PP
-The author can be contacted at:
-.TP 12
-.B Email:
-.B Peter Eriksson 
-.SH "SEE ALSO"
-.BR identd (8)
-,
-.BR ikeygen (8)
diff -Nru pidentd-3.0.19.ds1/debian/idecrypt.dirs 
pidentd-3.0.19.ds1/debian/idecrypt.dirs
--- pidentd-3.0.19.ds1/debian/idecrypt.dirs 2008-09-23 11:48:19.0 
+0200
+++ pidentd-3.0.19.ds1/debian/idecrypt.dirs 1970-01-01 01:00:00.0 
+0100
@@ -1,2 +0,0 @@
-usr/sbin
-usr/share/man/man8
diff -Nru pidentd-3.0.19.ds1/debian/rules pidentd-3.0.19.ds1/debian/rules
--- pidentd-3.0.19.ds1/debian/rules

Bug#907452: marked as done (OpenVPN deadlock when adding PKCS#11 provider (fix proposed))

Your message dated Wed, 20 Feb 2019 21:50:16 +
with message-id 
and subject line Bug#907452: fixed in openvpn 2.4.7-1
has caused the Debian Bug report #907452,
regarding OpenVPN deadlock when adding PKCS#11 provider (fix proposed)
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.)


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

Hello,

In addition to OpenVPN deadlocking at PIN prompt as reported in debian bug 
#772812 (solved by adding a few patches):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772812

OpenVPN will *also* deadlock when adding the PKCS#11 provider(s), before any 
PIN prompt attempt:

  https://lists.freedesktop.org/archives/p11-glue/2015-May/000555.html

I managed to work around that issue in pkcs11-helper by:
- including patch 
https://github.com/OpenSC/pkcs11-helper/commit/9b8debf331d7bd5eda1fa6feb322c0e31657e9b5
 (incl. in version 1.25)
- including patch 
https://github.com/OpenSC/pkcs11-helper/commit/4ea1afedec542b3f454dc6b02e86ef479d04a6ac
 (incl. in version 1.25.1)
- *disabling* threading (--disable-threading and --disable-slotevent)

Note that unless threading is disabled, OpenVPN will deadlock *even* when using 
the "management" interface, since the loading the PKCS#11 provider still 
happens during OpenVPN initialization (independently from the PIN prompt being 
offloaded to the management client):

  https://github.com/OpenSC/pkcs11-helper/issues/5 (alonbl's last comment 
before closing)

I can't find back the reference to a comment stating that OpenVPN might be the 
only user, nowadays, of the pkcs11-helper.
Based on my experience working with PKCS#11 along PAM, Kerberos, Firefox, 
Thunderbird and Chromium, I can tell only the OpenVPN package did pull the 
libpkcs11-helper-1 pakage as a dependency.
The change proposed here should thus not affect too broad an audience.

I know the culprit in all this seems to be OpenVPN but since this bug has been 
along for several years and nobody seems to be willing to address it,
would you consider those changes nonetheless ?

Thanks and best,

Cédric

-- 
Cédric Dufour @ Idiap Research Institute
--- End Message ---
--- Begin Message ---
Source: openvpn
Source-Version: 2.4.7-1

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated openvpn 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, 20 Feb 2019 14:50:03 +0100
Source: openvpn
Architecture: source
Version: 2.4.7-1
Distribution: unstable
Urgency: medium
Maintainer: Bernhard Schmidt 
Changed-By: Bernhard Schmidt 
Closes: 772812 868806 900805 907452 913265
Changes:
 openvpn (2.4.7-1) unstable; urgency=medium
 .
   [ Bernhard Schmidt ]
   * New upstream version 2.4.7
 - improvements regarding TLSv1.3
 - Add CAP_AUDIT_WRITE for auth_pam for upstream units (Closes: #868806)
   * adjust kfreebsd_support.patch for new upstream version
   * Also Add CAP_AUDIT_WRITE for auth_pam for openvpn@.service (Closes: 
#868806)
   * openvpn@.service: Bump LimitNPROC to 100, see #861923
 .
   [ Simon Deziel ]
   * d/control: suggests openvpn-systemd-resolved (Closes: #913265)
 .
   [ Hilko Bengen ]
   * Avoid hangs when spawning child processes by not setting pkcs11-helper
 "safe fork mode" (Closes: #772812, #900805, #907452)
Checksums-Sha1:
 78370f27746d543b807ac36efa7c8d24e4e1f009 2072 openvpn_2.4.7-1.dsc
 322d6460f74781dcd32f4a13236dd65e91d41240 953116 openvpn_2.4.7.orig.tar.xz
 6b7fd23ed953755aebd8fa496e19cba299e5eecf 56556 openvpn_2.4.7-1.debian.tar.xz
 556b2a2e79eedce114cac26082f88803039c34ff 6753 openvpn_2.4.7-1_amd64.buildinfo
Checksums-Sha256:
 8f1fa03afd18f0a651fac659af6898ffda2d15ba80252d2afc746826796839a7 2072 
openvpn_2.4.7-1.dsc
 a42f53570f669eaf10af68e98d65b531015ff9e12be7a62d9269ea684652f648 953116 
openvpn_2.4.7.orig.tar.xz
 f87fd3cc2cebce1cdf6d8ac78a014260aaa48f23601240524882f68319fa

Processed: limit source to packaging-tutorial, tagging 921801

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

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

> tags 921801 + pending
Bug #921801 [src:packaging-tutorial] packaging-tutorial: FTBFS (LaTeX error)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#919914: gnome-tweaks now equates "don't suspend on lid close" with "don't lock on lid close" (security issue)

2019-02-20 Thread Jeremy Bicha

Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/84

Processed: hg-git is only broken in testing

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

> tag 921732 sid
Bug #921732 [hg-git] hg-git: incompatible with mercurial 4.9
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#917644: FTBFS: segmentation faults in test suite

2019-02-20 Thread Matthew Fluet

On Wed, Feb 20, 2019 at 8:06 AM Thierry fa...@linux.ibm.com <
thie...@linux.ibm.com> wrote:

> On Tue, 19 Feb 2019 16:50:00 +0100 "Thierry fa...@linux.ibm.com"
>  wrote:
> > On Mon, 7 Jan 2019 16:49:41 + Steve McIntyre 
> wrote:
> > > Hi Matthew,
> > >
> > > On Sun, Dec 30, 2018 at 05:38:57PM -0500, Matthew Fluet wrote:
> > > >If it is just the `world` regression tests that are failing, then it
> > > >is almost certainly due to save/restore world being incompatible with
> > > >ASLR; see http://mlton.org/MLtonWorld#_notes.  Perhaps Debian
> > > >arm64-linux has gained ASLR since the last time the regression suite
> > > >was run on this platform?  In any case, you'll notice that the `world`
> > > >regression tests are explicitly whitelisted (i.e., these tests failing
> > > >do not cause a failure exit status from the regression script) because
> > > >of this issue.
> > >
> > As this bug is not specifically opened for one arch, I also want to
> > mention it fails on ppc64el. I see the sequence
> > testing wordn-array
> > testing world1
> > 2c2,3
> > < I am the clone
> > ---
> > > unhandled exception: Fail: child failed
> > > Nonzero exit status.
> > world1: difference with -type-check true
> > testing world2
> > 1c1,2
> > < 30
> > ---
> > > unhandled exception: Fail: child failed
> > > Nonzero exit status.
> > world2: difference with -type-check true
> > testing world3
> > 1c1,2
> > < caught foo
> > ---
> > > unhandled exception: Fail: child failed
> > > Nonzero exit status.
> > world3: difference with -type-check true
> > testing world4
> > 4,6c4,5
> > < between saves
> > < after saves
> > < after saves
> > ---
> > > unhandled exception: Fail: child failed
> > > Nonzero exit status.
> > world4: difference with -type-check true
> > testing world5
> > 2c2,3
> > < success
> > ---
> > > unhandled exception: Fail: child failed
> > > Nonzero exit status.
> > world5: difference with -type-check true
> > testing world6
> > 1,4c1
> > < ./world6
> > < a
> > < b
> > < c
> > ---
>
> This pad is hosted in Toulouse LTC lab. Created at 2019-02-19 09:45:56.
>
> Hi,
> I have run make check without world tests and result is code 1 because
> of failing tests on some architectures
> testing mlton.overload
> testing mlton.share
> 1c1
> < size of a is 1600
> ---
> > size of a is 2408
> 102c102
> < size of a is 484
> ---
> > size of a is 920
>
> testing size2
> 2,23c2,23
> < The size of an int list of length 4 is = 48 bytes.
> < The size of a string of length 10 is = 24 bytes.
> < The size of an int array of length 10 is = 52 bytes.
> < The size of a double array of length 10 is = 92 bytes.
> < The size of a (word32 * double) array of length 10 is = 132 bytes.
> < The size of a (word32 * word32 * double) array of length 10 is = 172
> bytes.
> < The size of a (word64 * double) array of length 10 is = 172 bytes.
> < The size of a (word16 * double) array of length 10 is = 132 bytes.
> < The size of a word64 array of length 10 is = 92 bytes.
> < The size of a (word32 * word64) array of length 10 is = 132 bytes.
> < The size of a (word32 * word32 * word64) array of length 10 is = 172
> bytes.
> < The size of a (word64 * word64) array of length 10 is = 172 bytes.
> < The size of a (word16 * word64) array of length 10 is = 132 bytes.
> < The size of an array of length 10 of 2-ples of ints is = 92 bytes.
> < The size of an array of length 10 of 2-ples of (shared) ints is = 92
> bytes.
> < The size of an array of length 10 of arrays of length 20 of ints is =
> 972 bytes.
> < The size of an array of length 10 of (shared) arrays of length 20 of
> ints is = 144 bytes.
> < The size of an array of length 10 of tuples of word16 * (arrays of
> length 20 of ints) is = 1012 bytes.
> < The size of an array of length 10 of tuples of word32 * (arrays of
> length 20 of ints) is = 1012 bytes.
> < The size of an array of length 10 of tuples of word64 * (arrays of
> length 20 of ints) is = 1052 bytes.
> < The size of an array of length 10 of tuples of real32 * (arrays of
> length 20 of ints) is = 1012 bytes.
> < The size of an array of length 10 of tuples of real64 * (arrays of
> length 20 of ints) is = 1052 bytes.
> ---
> > The size of an int list of length 4 is = 96 bytes.
> > The size of a string of length 10 is = 40 bytes.
> > The size of an int array of length 10 is = 64 bytes.
> > The size of a double array of length 10 is = 104 bytes.
> > The size of a (word32 * double) array of length 10 is = 184 bytes.
> > The size of a (word32 * word32 * double) array of length 10 is = 184
> bytes.
> > The size of a (word64 * double) array of length 10 is = 184 bytes.
> > The size of a (word16 * double) array of length 10 is = 184 bytes.
> testing size3
> 1c1,114
> < size3.$arch-$os.ok missing
> ---
> > The size of unit is = 0 bytes.
> > The size of unit * unit is = 0 bytes.
> > The size of bool is = 0 bytes.
> > The size of bool * bool is = 16 bytes.
> > The size of day is = 0 bytes.
> > The size of day * day is = 0 bytes.
> > The size of a char is = 0 byte

Bug#859715: marked as done (resiprocate: Please migrate to openssl1.1 in Buster)

Your message dated Wed, 20 Feb 2019 17:41:39 +
with message-id
and subject line Bug#920572: Removed package(s) from unstable
has caused the Debian Bug report #859715,
regarding resiprocate: Please migrate to openssl1.1 in Buster
to be marked as done.

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

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

--
859715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: resiprocate
Version: 1:1.11.0~alpha2-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828532. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/resiprocate_1.10.2-1_amd64-20160529-1531

Sebastian
--- End Message ---
--- Begin Message ---
Version: 1:1.11.0~beta5-1+rm

Dear submitter,

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

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

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

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

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

Bug#912143: marked as done (resiprocate FTBFS with asio 1:1.12.1-1)

Your message dated Wed, 20 Feb 2019 17:41:39 +
with message-id 
and subject line Bug#920572: Removed package(s) from unstable
has caused the Debian Bug report #912143,
regarding resiprocate FTBFS with asio 1:1.12.1-1
to be marked as done.

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

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


-- 
912143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: resiprocate
Version: 1:1.11.0~beta5-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:reconserver

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

...
AsyncTlsSocketBase.cxx: In member function 'virtual unsigned int 
reTurn::AsyncTlsSocketBase::getSocketDescriptor()':
AsyncTlsSocketBase.cxx:39:48: error: 
'asio::ssl::stream 
>::lowest_layer_type' {aka 'class asio::basic_socket'} has no 
member named 'native'
return (unsigned int)mSocket.lowest_layer().native();
^~
AsyncTlsSocketBase.cxx: In member function 'virtual bool 
reTurn::AsyncTlsSocketBase::validateServerCertificateHostname()':
AsyncTlsSocketBase.cxx:164:40: error: 'class 
asio::ssl::stream >' has no member 
named 'impl'
ciph=SSL_get_current_cipher(mSocket.impl()->ssl);
^~~~
In file included from AsyncTlsSocketBase.cxx:15:
AsyncTlsSocketBase.cxx:166:35: error: 'class 
asio::ssl::stream >' has no member 
named 'impl'
   <<  SSL_get_version(mSocket.impl()->ssl) << " "
   ^~~~
../rutil/Logger.hxx:156:39: note: in definition of macro 'GenericLog'
  _resip_log_guard.asStream()  args_;\
   ^
AsyncTlsSocketBase.cxx:165:4: note: in expansion of macro 'InfoLog'
InfoLog( << "TLS session set up with "
^~~
AsyncTlsSocketBase.cxx:171:50: error: 'class 
asio::ssl::stream >' has no member 
named 'impl'
X509* cert = SSL_get_peer_certificate(mSocket.impl()->ssl);
  ^~~~
AsyncTlsSocketBase.cxx: In member function 'virtual void 
reTurn::AsyncTlsSocketBase::transportClose()':
AsyncTlsSocketBase.cxx:317:53: error: 
'asio::ssl::stream 
>::lowest_layer_type' {aka 'class asio::basic_socket'} has no 
member named 'native'
   mOnBeforeSocketCloseFp(mSocket.lowest_layer().native());
 ^~
...
--- End Message ---
--- Begin Message ---
Version: 1:1.11.0~beta5-1+rm

Dear submitter,

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

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

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

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

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

Bug#905495: marked as done (resiprocate: CVE-2018-12584)

Your message dated Wed, 20 Feb 2019 17:41:39 +
with message-id 
and subject line Bug#920572: Removed package(s) from unstable
has caused the Debian Bug report #905495,
regarding resiprocate: CVE-2018-12584
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.)


-- 
905495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: resiprocate
Version: 1:1.11.0~beta1-3
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for resiprocate.

CVE-2018-12584[0]:
| The ConnectionBase::preparseNewBytes function in
| resip/stack/ConnectionBase.cxx in reSIProcate through 1.10.2 allows
| remote attackers to cause a denial of service (buffer overflow) or
| possibly execute arbitrary code when TLS communication is enabled.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-12584
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12584
[1] http://joachimdezutter.webredirect.org/advisory.html
[2] 
https://github.com/resiprocate/resiprocate/commit/2cb291191c93c7c4e371e22cb89805a5b31d6608

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1:1.11.0~beta5-1+rm

Dear submitter,

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

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

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

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

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

Bug#889996: marked as done (resiprocate-turn-server: broken init script stop action)

Your message dated Wed, 20 Feb 2019 17:41:39 +
with message-id 
and subject line Bug#920572: Removed package(s) from unstable
has caused the Debian Bug report #889996,
regarding resiprocate-turn-server: broken init script stop action
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.)


-- 
889996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: resiprocate-turn-server
Version: 1:1.11.0~beta1-3
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
X-Debbugs-Cc: debian-ad...@lists.debian.org

Hi,

your init script "stop" action is broken.

  stop)
log_daemon_msg "Stopping $DESC ($NAME)" $BIN
if start-stop-daemon --stop --quiet --oknodo --user $USER --pidfile 
$PIDFILE --exec $DAEMON ;
then
log_end_msg 0
else
log_end_msg 1
fi
;;

It is missing the --retry option which means it doesn't wait until the
process is actually dead before exiting.  This shows up in the "restart"
action with:

  restart)
$0 stop && sleep 2 && $0 start
;;

That "sleep" is evidence that "stop" is broken.

And because systemd never calls the init script with "restart" but uses
"stop" followed by "start" (which is supposed to be the same thing), the
old "sleep" workaround for broken "stop" no longer works.  Please add
the appropriate "--retry" option to "stop" and remove that "sleep".

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Version: 1:1.11.0~beta5-1+rm

Dear submitter,

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

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

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

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

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

Bug#869404: marked as done (resiprocate: CVE-2017-11521: Adding too many media connections may lead to memory exhaustion)

Your message dated Wed, 20 Feb 2019 17:41:39 +
with message-id 
and subject line Bug#920572: Removed package(s) from unstable
has caused the Debian Bug report #869404,
regarding resiprocate: CVE-2017-11521: Adding too many media connections may 
lead to memory exhaustion
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.)


-- 
869404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: resiprocate
Version: 1:1.9.7-5
Severity: grave
Tags: upstream security
Forwarded: https://github.com/resiprocate/resiprocate/pull/88

Hi,

the following vulnerability was published for resiprocate.

CVE-2017-11521[0]:
| The SdpContents::Session::Medium::parse function in
| resip/stack/SdpContents.cxx in reSIProcate 1.10.2 allows remote
| attackers to cause a denial of service (memory consumption) by
| triggering many media connections.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-11521
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11521
[1] https://github.com/resiprocate/resiprocate/pull/88

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1:1.11.0~beta5-1+rm

Dear submitter,

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

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

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

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

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

Bug#918852: ufo-filters: FTBFS with Sphinx 1.8: cannot import name 'Directive' from 'sphinx.directives'

On Wed, Feb 20, 2019 at 04:35:52PM +, PICCA Frederic-Emmanuel wrote:
> thanks a lot both of you, I could not manage to find enought time these days 
> for this package...

You are welcome.  Please check new upstream which failed to build but
I had no time to fix this.  In Git you will find adapted patches for
the new version.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#918852: ufo-filters: FTBFS with Sphinx 1.8: cannot import name 'Directive' from 'sphinx.directives'

2019-02-20 Thread PICCA Frederic-Emmanuel

thanks a lot both of you, I could not manage to find enought time these days 
for this package...

Cheers

Fred

Bug#918852: marked as done (ufo-filters: FTBFS with Sphinx 1.8: cannot import name 'Directive' from 'sphinx.directives')

Your message dated Wed, 20 Feb 2019 16:39:13 +
with message-id 
and subject line Bug#918852: fixed in ufo-filters 0.14.1+dfsg1-2
has caused the Debian Bug report #918852,
regarding ufo-filters: FTBFS with Sphinx 1.8: cannot import name 'Directive' 
from 'sphinx.directives'
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.)


-- 
918852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ufo-filters
Version: 0.14.1+dfsg1-1.1
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.8
Forwarded: https://github.com/ufo-kit/ufo-filters/pull/171

Dear Maintainer,

ufo-filters fails to build with Sphinx 1.8, currently available in
experimental:

  Running Sphinx v1.8.3

  Exception occurred:
File "/<>/ufo-filters-0.14.1+dfsg1/docs/sphinxgobject/domain.py", 
line 4, in 
  from sphinx.directives import ObjectDescription, Directive
  ImportError: cannot import name 'Directive' from 'sphinx.directives'
  (/usr/lib/python3/dist-packages/sphinx/directives/__init__.py)

The Directive class should be imported from docutils.parsers.rst, not from
sphinx.directives module.

I have submitted a pull request upstream to fix this, see Forwarded field.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ufo-filters
Source-Version: 0.14.1+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
ufo-filters, 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.
Andreas Tille  (supplier of updated ufo-filters 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, 20 Feb 2019 17:02:52 +0100
Source: ufo-filters
Binary: ufo-filters ufo-filters-doc ufo-filters-data
Architecture: source
Version: 0.14.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Picca Frédéric-Emmanuel 
Changed-By: Andreas Tille 
Description:
 ufo-filters - Set of plugins for ufo-core - runtime
 ufo-filters-data - Library for high-performance, GPU-based computing - data
 ufo-filters-doc - Library for high-performance, GPU-based computing - 
documentation
Closes: 918852
Changes:
 ufo-filters (0.14.1+dfsg1-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Adrian Bunk ]
   * Add upstream fix for FTBFS with Sphinx 1.8. (Closes: #918852)
 .
   [ Andreas Tille ]
   * debhelper 12
   * Standards-Version: 4.3.0
   * Remove trailing whitespace in debian/changelog
   * Lintian-override for non-issue since the not excluded file does not harm
Checksums-Sha1:
 723d475f9c0b7ca3251c6f74505d8accc8848c8e 2203 ufo-filters_0.14.1+dfsg1-2.dsc
 a48c5e18343c8c81dfa61e4eb60327d774772364 4076 
ufo-filters_0.14.1+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 bd857e87b5ab837ec8aa0f096dbd30ec2d95b2a8af908c81bc54ebfd467ca5f9 2203 
ufo-filters_0.14.1+dfsg1-2.dsc
 449013c11769b305088329894af2f9ae039258d2da797c3264615baa79c01402 4076 
ufo-filters_0.14.1+dfsg1-2.debian.tar.xz
Files:
 5b7298c734e7de073467899b39ff 2203 libs optional 
ufo-filters_0.14.1+dfsg1-2.dsc
 7a3f989ca815e6298d79e51c9702c38b 4076 libs optional 
ufo-filters_0.14.1+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxtfUwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEslhAAlW9yufnG8nPSn9jVUG6E/TxWMa7s8wG3
DU71eMTBEVLO+AaZkQaFsQygK9cCK2KtJv+UBTnpUq3DJNgXxRvL0tqwNaOQtOva
Qx8X6/ypYUQdlhtkbQl371zMKm6LhMYbzceGJYslCtsLeqp0XiLlOzF+NTUw0i6L
bx+CLNR7t8BwLIqPxiEo6g/gZhiTae1MuP2a820FHh1w5npP9M5AyyGqz6RW9Qqs
gZvoCpoJZPcuA4SSMSSqJbFl2cvM6nDdDdXcKpU4Gr9jKjN9pkeBwdr10ef5dKzu
B76tU7VPf/fHTunks8sfr1OtNoJr6t4SWpx+hTEbY8KZsrTXHA1cB4yp3OhPCjrO
5oRjskayE/Ip5BF1Qefjj2Zpf/1RsGFzIrd3pUHPTOGXtwzlT65LcbAa8GhPIapq
KYD12lpq2n/iAB31nq2D21IcfeGhyyPkYSyhbWZh6jM2J8OvRiXWNvBF8bGLJrjk
lh65VP8LIrgT/0VOGqde+XpU/1mBvXk4hdKqwbZMO7A6X93CG2M8mUsQnD0cKSJQ
7UgykZrDQKQEjBeEmdzs8d+IX34oEmkZBqhX6sgToGbHafEphWMBQEFN8FGJnF3A
vD16Vhc/xwk/VLMfNB4ADYeMe5srYLPgQBrg0j6DkBL9VtzeSW5IQLQkKgHH8vvE
S/wCUbnQQEQ=
=lozu
-END PGP SIGNATURE End Message ---

Bug#844778: clsync FTBFS on !x86: error: '__NR_select' undeclared here

On Sat, 19 Nov 2016 01:09:28 +0200 Adrian Bunk  wrote:
> Source: clsync
> Version: 0.4.2-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=clsync&suite=sid
> 
> ...
> In file included from privileged.c:64:0:
> privileged.c:88:34: error: '__NR_select' undeclared here (not in a function)
>   BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, __NR_##syscall, 0, 1), \
> ...
> 
> 

Depending on arch you have different __NR_ functions not present - for
example, __NR_alarm or __NR_shmdt

Bug#918852: ufo-filters: FTBFS with Sphinx 1.8: cannot import name 'Directive' from 'sphinx.directives'

Hi,

I'm doing a team upload of this package with some more updates.

Adrian, thanks a lot for the NUM-diff in any case - I think for Debian
Science team the very long delay for FTBFS issues is not needed.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#909861: shark FTBFS on i386 with gcc 8

On Sat, 29 Sep 2018 20:48:49 +0300 Adrian Bunk  wrote:
> Source: shark
> Version: 3.1.4+ds1-1
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/shark.html
> 
> ...
>  57/160 Test  #67: Trainers_MissingFeatureSvmTrainer ***Failed
> 0.52 sec
> Running 2 test cases...
> ./Test/Algorithms/Trainers/MissingFeatureSvmTrainerTests.cpp(165): error: in 
> "Algorithms_Trainers_MissingFeatureSvmTrainerTests/MissingFeatures": check 
> test::verifyVectors(output1, output2) has failed. index:0, seen:1.23556e+267, 
> expected:-5.83284e+118
> 
> *** 1 failure is detected in the test module 
> "MissingFeaturesSvmTrainerTestModule"
> ...
> 99% tests passed, 1 tests failed out of 160
> 
> Total Test time (real) = 697.78 sec
> 
> The following tests FAILED:
>67 - Trainers_MissingFeatureSvmTrainer (Failed)
> Errors while running CTest
> make[2]: *** [Makefile:143: test] Error 8
> 
> 
This test is also failing on amd64 and ppc64el ... and may be others !

Processed: Re: Bug#922755: groovy: FTBFS on Buster

Processing control commands:

> tags -1 pending
Bug #922755 [src:groovy] groovy: FTBFS on Buster
Added tag(s) pending.

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

Bug#922755: groovy: FTBFS on Buster

2019-02-20 Thread Markus Koschany

Control: tags -1 pending

Am 20.02.19 um 11:45 schrieb Ritesh Raj Sarraf:
> Source: groovy
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> Dear Maintainer,
> 
> The package fails to build on Buster/Sid. The relevant build failure
> snippet is below and full build log is attached:

This is again caused by the recent change in OpenJDK that broke Javadoc
generation. We found a workaround for Maven based packages but the
detectJavaApiLink appears to be Maven specific. As a workaround for
groovy, which uses Gradle, I set failOnError to false for javadoc. If
this affects more packages we should probably look for a more general
solution/workaround.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#922773: FTBFS since the acl/attr uploads of 2019-05-15+16

2019-02-20 Thread Axel Beckert

Source: adequate
Version: 0.15.1
Severity: serious
Tags: ftbfs

Since the uploads of acl and attr with this changelog entry, adequate
FTBFS:

   * Perform a proper and correct /usr-merge transition by moving the package
 contents from / to /usr.

Build log of a failed build:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/adequate.html

The relevant lines are:

TESTING: ./adequate coreutils
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/cp => 
/usr/lib/x86_64-linux-gnu/libacl.so.1
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/cp => 
/usr/lib/x86_64-linux-gnu/libattr.so.1
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/mv => 
/usr/lib/x86_64-linux-gnu/libacl.so.1
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/mv => 
/usr/lib/x86_64-linux-gnu/libattr.so.1
make: *** [debian/rules:17: debian/build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

While I personally value that
bin-or-sbin-binary-requires-usr-lib-library check a lot, Debian has
decided to not go down that path and to allow library and other
dependencies from /bin/ and /sbin/ into /usr/. With acl and attr
having its libraries in /usr/lib/, coreutils is no more adequate-clean
and hence that test fails.

IMHO adequate shouldn't use any other package than itself or maybe a
dummy package included in the test suite — as lintian does, although
that's probably more difficult for as-installed testing.

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

-- no debconf information

Bug#888733: hyantesite FTBFS on most architectures: test failures

On Mon, 29 Jan 2018 11:47:06 +0200 Adrian Bunk  wrote:
> Source: hyantesite
> Version: 1.3.0-2
> Severity: serious
> 
> hyantesite FTBFS on most architectures with varying test failures:
> 
> https://buildd.debian.org/status/package.php?p=hyantesite
> 
> 
Since the tests are failing because (apparently) the result of float 0
is being minus signed I suspect this is related to arch representation
of some signed variables during calculation.
Any guess ?

here is an example of the result of the comparison
diff test/two_circles.out /tmp/libhypersmooth.zVpJKq
41c41
< -1.00 0.00 0.00
---
> -1.00 -0.00 0.00
122c122
< -0.975000 0.00 0.00
---
> -0.975000 -0.00 0.00

Bug#922772: redmine: start via unicorn fails

2019-02-20 Thread Jörg-Volker Peetz

Package: redmine
Version: 4.0.1-1
Severity: grave

Dear Maintainer team,

after upgrading from 3.4.6 the start of redmine via unicorn
fails. Please find the error protocol appended.
It seems to fail in line 19 of /usr/share/redmine/config/environment.rb

Regards,
Jörg.

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

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

Versions of packages redmine depends on:
ii  dbconfig-common 2.0.11
ii  debconf [debconf-2.0]   1.5.70
ii  libjs-jquery3.3.1~dfsg-1
ii  libjs-jquery-ui 1.12.1+dfsg-5
ii  libjs-raphael   2.1.0-1
ii  redmine-sqlite  4.0.1-1
ii  ruby1:2.5.1
ii  ruby-actionpack-action-caching  1.2.0-2
ii  ruby-actionpack-xml-parser  2.0.1-3
ii  ruby-bundler1.17.3-2
ii  ruby-coderay1.1.2-2
ii  ruby-csv3.0.2-1
ii  ruby-i18n   1.5.3-1
ii  ruby-jquery-rails   4.3.3-1
ii  ruby-mail   2.7.1+dfsg1-1
ii  ruby-mime-types 3.2.2-1
ii  ruby-mimemagic  0.3.2+dfsg-1
ii  ruby-mini-mime  1.0.1-1
ii  ruby-net-ldap   0.16.1-1
ii  ruby-nokogiri   1.10.0+dfsg1-2
ii  ruby-openid 2.7.0debian-1
ii  ruby-rack   2.0.6-3
ii  ruby-rack-openid1.4.2-1
ii  ruby-rack-test  0.7.0-1
ii  ruby-rails  2:5.2.2+dfsg-5
ii  ruby-rails-dom-testing  2.0.3-3
ii  ruby-rails-observers0.1.5-1
ii  ruby-rbpdf  1.19.5+ds.1-1
ii  ruby-redcarpet  3.4.0-4+b1
ii  ruby-request-store  1.3.0-1
ii  ruby-rmagick2.16.0-6
ii  ruby-roadie 3.2.2-1
ii  ruby-roadie-rails   1.3.0-1
ii  ruby-rouge  3.3.0-1

Versions of packages redmine recommends:
pn  passenger  

Versions of packages redmine suggests:
pn  bzr 
ii  cvs 2:1.12.13+real-27
pn  darcs   
ii  git 1:2.20.1-2
ii  mercurial   4.9-2
pn  ruby-fcgi   
ii  subversion  1.10.4-1

-- debconf information:
  redmine/instances/default/missing-db-package-error: abort
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/instances/default/remote/newhost:
* redmine/current-instances: default
* redmine/instances/default/default-language: en
  redmine/instances/default/upgrade-backup: true
  redmine/default-language: en
  redmine/instances/default/mysql/admin-user:
  redmine/old-instances:
  redmine/instances/default/pgsql/changeconf: false
* redmine/instances/default/dbconfig-install: true
  redmine/instances/default/db/app-user: redmine
  redmine/instances/default/dbconfig-reinstall: false
  redmine/instances/default/upgrade-error: abort
* redmine/instances/default/db/basepath: /var/lib/redmine/default/db
  redmine/notify-migration:
  redmine/instances/default/internal/skip-preseed: false
  redmine/instances/default/passwords-do-not-match:
  redmine/instances/default/dbconfig-remove:
  redmine/instances/default/remote/host: localhost
  redmine/instances/default/dbconfig-upgrade: true
* redmine/instances/default/db/dbname: redmine.sqlite
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/remote/port:
  redmine/instances/default/remove-error: abort
  redmine/instances/default/pgsql/no-empty-passwords:
  redmine/instances/default/pgsql/authmethod-user: password
  redmine/instances/default/pgsql/method: TCP/IP
  redmine/missing-redmine-package:
  redmine/instances/default/purge: false
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/instances/default/install-error: abort
  redmine/instances/default/mysql/method: Unix socket
* redmine/instances/default/database-type: sqlite3
I, [2019-02-20T12:01:44.139905 #29924]  INFO -- : Refreshing Gem list
I, [2019-02-20T12:01:48.342802 #29924]  INFO -- : listening on 
addr=/run/www/unicorn-redmine-default.sock fd=13
I, [2019-02-20T12:01:48.353250 #29924]  INFO -- : master process ready
I, [2019-02-20T12:01:48.385812 #29930]  INFO -- : worker=1 ready
I, [2019-02-20T12:01:48.386122 #29927]  INFO -- : worker=0 ready
I, [2019-02-20T12:02:22.860110 #29924]  INFO -- : reaped # worker=0
I, [2019-02-20T12:02:22.860331 #29924]  INFO -- : reaped # worker=1
I, [2019-02-20T12:02:22.860486 #29924]  INFO -- : master complete
I, [2019-02-20T13:13:34.284742 #373]  INFO -- : Refreshing Gem list
/usr/share/rubygems-integration/all/gems/actionpack-5.2.2/lib/action_dispatch/routing/mapper.rb:2099:in
 `direct': The direct met

Bug#922770: lvfs: GRUB disappeared after Thinkpad T480s firmware update

2019-02-20 Thread Steve McIntyre

Control: severity -1 normal

On Wed, Feb 20, 2019 at 02:16:20PM +0100, Alejandro Sanchez wrote:
>Package: fwupd
>Version: 1.1.4-1
>Severity: critical
>File: lvfs
>Justification: breaks the whole system
>
>Dear Maintainer,
>
>The Software Update manager popped up a message for a Thinkpad T480s firmware
>update. I proceeded with the Install & Reboot, and after the update finished
>and laptop restarted, GRUB completely disappeared. Then I had to follow the
>instructions in the following page to reinstall grub:
>
>https://wiki.debian.org/GrubEFIReinstall
>
>I can't find any references to 'fw' and/or 'lvfs' in either:
>
>/var/log/apt/history.log
>
>or
>
>/var/log/apt/term.log
>
>but I believe that the Firmware update was this one:
>
>https://fwupd.org/lvfs/device/ebfe8df8-dee7-4692-a721-cbcf5095c5cf
>
>Lenovo ThinkPad T480s System Firmware Version 1.29.

This isn't a bug in fwupd, it's a problem with the Lenovo firmware
throwing away boot entries on upgrade. There's very little we can do
about that. :-/

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
  note stuck to the mini-bar saying "Paul: This fridge and
  fittings are the correct way around and do not need altering"

Processed: Re: Bug#922770: lvfs: GRUB disappeared after Thinkpad T480s firmware update

Processing control commands:

> severity -1 normal
Bug #922770 [fwupd] lvfs: GRUB disappeared after Thinkpad T480s firmware update
Severity set to 'normal' from 'critical'

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

Bug#922770: lvfs: GRUB disappeared after Thinkpad T480s firmware update

2019-02-20 Thread Alejandro Sanchez

Package: fwupd
Version: 1.1.4-1
Severity: critical
File: lvfs
Justification: breaks the whole system

Dear Maintainer,

The Software Update manager popped up a message for a Thinkpad T480s
firmware
update. I proceeded with the Install & Reboot, and after the update finished
and laptop restarted, GRUB completely disappeared. Then I had to follow the
instructions in the following page to reinstall grub:

https://wiki.debian.org/GrubEFIReinstall

I can't find any references to 'fw' and/or 'lvfs' in either:

/var/log/apt/history.log

or

/var/log/apt/term.log

but I believe that the Firmware update was this one:

https://fwupd.org/lvfs/device/ebfe8df8-dee7-4692-a721-cbcf5095c5cf

Lenovo ThinkPad T480s System Firmware Version 1.29.

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

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

Versions of packages fwupd depends on:
ii  libappstream-glib8 0.7.14-1
ii  libarchive13   3.3.3-4
ii  libc6  2.28-6
ii  libefiboot137-1
ii  libefivar1 37-1
ii  libelf10.175-2
ii  libfwupd2  1.1.4-1
ii  libgcab-1.0-0  1.2-2
ii  libglib2.0-0   2.58.3-1
ii  libgnutls303.6.6-2
ii  libgpg-error0  1.35-1
ii  libgpgme11 1.12.0-6
ii  libgudev-1.0-0 232-2
ii  libgusb2   0.3.0-1
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpolkit-gobject-1-0  0.105-25
ii  libsmbios-c2   2.4.1-1
ii  libsoup2.4-1   2.64.2-2
ii  libsqlite3-0   3.26.0+fossilbc891ac6b-2
ii  libuuid1   2.33.1-0.1

Versions of packages fwupd recommends:
ii  bolt   0.7-2
ii  fwupd-amd64-signed [fwupd-signed]  1.1.4+1
ii  python33.7.2-1

fwupd suggests no packages.

-- no debconf information

Bug#917644: FTBFS: segmentation faults in test suite

On Tue, 19 Feb 2019 16:50:00 +0100 "Thierry fa...@linux.ibm.com"
 wrote:
> On Mon, 7 Jan 2019 16:49:41 + Steve McIntyre  wrote:
> > Hi Matthew,
> > 
> > On Sun, Dec 30, 2018 at 05:38:57PM -0500, Matthew Fluet wrote:
> > >If it is just the `world` regression tests that are failing, then it
> > >is almost certainly due to save/restore world being incompatible with
> > >ASLR; see http://mlton.org/MLtonWorld#_notes.  Perhaps Debian
> > >arm64-linux has gained ASLR since the last time the regression suite
> > >was run on this platform?  In any case, you'll notice that the `world`
> > >regression tests are explicitly whitelisted (i.e., these tests failing
> > >do not cause a failure exit status from the regression script) because
> > >of this issue.
> > 
> As this bug is not specifically opened for one arch, I also want to
> mention it fails on ppc64el. I see the sequence
> testing wordn-array
> testing world1
> 2c2,3
> < I am the clone
> ---
> > unhandled exception: Fail: child failed
> > Nonzero exit status.
> world1: difference with -type-check true
> testing world2
> 1c1,2
> < 30
> ---
> > unhandled exception: Fail: child failed
> > Nonzero exit status.
> world2: difference with -type-check true
> testing world3
> 1c1,2
> < caught foo
> ---
> > unhandled exception: Fail: child failed
> > Nonzero exit status.
> world3: difference with -type-check true
> testing world4
> 4,6c4,5
> < between saves
> < after saves
> < after saves
> ---
> > unhandled exception: Fail: child failed
> > Nonzero exit status.
> world4: difference with -type-check true
> testing world5
> 2c2,3
> < success
> ---
> > unhandled exception: Fail: child failed
> > Nonzero exit status.
> world5: difference with -type-check true
> testing world6
> 1,4c1
> < ./world6
> < a
> < b
> < c
> ---

This pad is hosted in Toulouse LTC lab. Created at 2019-02-19 09:45:56.

Hi,
I have run make check without world tests and result is code 1 because
of failing tests on some architectures
testing mlton.overload
testing mlton.share
1c1
< size of a is 1600
---
> size of a is 2408
102c102
< size of a is 484
---
> size of a is 920

testing size2
2,23c2,23
< The size of an int list of length 4 is = 48 bytes.
< The size of a string of length 10 is = 24 bytes.
< The size of an int array of length 10 is = 52 bytes.
< The size of a double array of length 10 is = 92 bytes.
< The size of a (word32 * double) array of length 10 is = 132 bytes.
< The size of a (word32 * word32 * double) array of length 10 is = 172
bytes.
< The size of a (word64 * double) array of length 10 is = 172 bytes.
< The size of a (word16 * double) array of length 10 is = 132 bytes.
< The size of a word64 array of length 10 is = 92 bytes.
< The size of a (word32 * word64) array of length 10 is = 132 bytes.
< The size of a (word32 * word32 * word64) array of length 10 is = 172
bytes.
< The size of a (word64 * word64) array of length 10 is = 172 bytes.
< The size of a (word16 * word64) array of length 10 is = 132 bytes.
< The size of an array of length 10 of 2-ples of ints is = 92 bytes.
< The size of an array of length 10 of 2-ples of (shared) ints is = 92
bytes.
< The size of an array of length 10 of arrays of length 20 of ints is =
972 bytes.
< The size of an array of length 10 of (shared) arrays of length 20 of
ints is = 144 bytes.
< The size of an array of length 10 of tuples of word16 * (arrays of
length 20 of ints) is = 1012 bytes.
< The size of an array of length 10 of tuples of word32 * (arrays of
length 20 of ints) is = 1012 bytes.
< The size of an array of length 10 of tuples of word64 * (arrays of
length 20 of ints) is = 1052 bytes.
< The size of an array of length 10 of tuples of real32 * (arrays of
length 20 of ints) is = 1012 bytes.
< The size of an array of length 10 of tuples of real64 * (arrays of
length 20 of ints) is = 1052 bytes.
---
> The size of an int list of length 4 is = 96 bytes.
> The size of a string of length 10 is = 40 bytes.
> The size of an int array of length 10 is = 64 bytes.
> The size of a double array of length 10 is = 104 bytes.
> The size of a (word32 * double) array of length 10 is = 184 bytes.
> The size of a (word32 * word32 * double) array of length 10 is = 184
bytes.
> The size of a (word64 * double) array of length 10 is = 184 bytes.
> The size of a (word16 * double) array of length 10 is = 184 bytes.
testing size3
1c1,114
< size3.$arch-$os.ok missing
---
> The size of unit is = 0 bytes.
> The size of unit * unit is = 0 bytes.
> The size of bool is = 0 bytes.
> The size of bool * bool is = 16 bytes.
> The size of day is = 0 bytes.
> The size of day * day is = 0 bytes.
> The size of a char is = 0 bytes.
> The size of a char * char is = 0 bytes.
> The size of a word8 is = 0 bytes.
> The size of a word8 * word8 is = 0 bytes.
> The size of a word16 is = 0 bytes.


-- 
Thierry Fauck @ fr.ibm.com

Processed: retitle 922692 to galax: FTBFS - ERROR: unable to find camomileLibrary.cmi in /usr/lib/ocaml/camomile ...

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

> retitle 922692 galax: FTBFS - ERROR: unable to find camomileLibrary.cmi in 
> /usr/lib/ocaml/camomile
Bug #922692 [galax] galax: FTBFS on ppc64el - ERROR: unable to find 
camomileLibrary.cmi in /usr/lib/ocaml/camomile
Changed Bug title to 'galax: FTBFS - ERROR: unable to find camomileLibrary.cmi 
in /usr/lib/ocaml/camomile' from 'galax: FTBFS on ppc64el - ERROR: unable to 
find camomileLibrary.cmi in /usr/lib/ocaml/camomile'.
> tags 922692 + sid buster
Bug #922692 [galax] galax: FTBFS - ERROR: unable to find camomileLibrary.cmi in 
/usr/lib/ocaml/camomile
Added tag(s) sid and buster.
> tags 918632 + sid buster
Bug #918632 [src:simplejson, src:json-schema-validator] simplejson breaks 
json-schema-validator autopkgtest
Added tag(s) sid and buster.
> tags 908493 + sid buster
Bug #908493 [src:pegtl] Duplicate of tao-pegtl
Added tag(s) sid and buster.
> found 922755 2.4.16-1
Bug #922755 [src:groovy] groovy: FTBFS on Buster
Marked as found in versions groovy/2.4.16-1.
> tags 921790 + sid buster
Bug #921790 {Done: Kyle Robbertze } 
[libcamlimages-ocaml-dev] liquidsoap: FTBFS (ld: cannot find -lexif)
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#922745: gdb needs a backport for PR binutils/23919

2019-02-20 Thread Héctor Orón Martínez

Missatge de Matthias Klose  del dia dc., 20 de febr.
2019 a les 10:15:
>
> Package: src:gdb
> Version: 8.2.1-1
> Severity: serious
> Tags: sid buster
>
> gdb needs a backport for PR binutils/23919. The PR fixes an issue with
> compressed debug sections, and is needed so that gdb can handle the fixed 
> debug
> sections.  elfutils already has the fix.
>
> The patch can be taken from the binutils 2.31 branch.

Patch applied in git.
https://salsa.debian.org/gdb-team/gdb/commit/b2e31f9b1cff137fc33f379b8e98bc134d648033

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Processed: found 905908 in 0.8.8~deb9u2

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

> found 905908 0.8.8~deb9u2
Bug #905908 {Done: Andreas Beckmann } [glx-alternative-mesa] 
libGL.so.1: cannot open shared object file: No such file or directory when 
updating to 4.4.1~rc2-3
Marked as found in versions glx-alternatives/0.8.8~deb9u2.
> thanks
Stopping processing here.

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

Processed: reassign 922678 to src:openjdk-11-jre-dcevm

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

> reassign 922678 src:openjdk-11-jre-dcevm 11.0.1+7-1
Bug #922678 [src:openjdk-11-dcevm] openjdk-11-dcevm ftbfs on i386
Warning: Unknown package 'src:openjdk-11-dcevm'
Bug reassigned from package 'src:openjdk-11-dcevm' to 
'src:openjdk-11-jre-dcevm'.
No longer marked as found in versions openjdk-11-dcevm/11.0.1+7-1.
Ignoring request to alter fixed versions of bug #922678 to the same values 
previously set
Bug #922678 [src:openjdk-11-jre-dcevm] openjdk-11-dcevm ftbfs on i386
Marked as found in versions openjdk-11-jre-dcevm/11.0.1+7-1.
> thanks
Stopping processing here.

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

Processed: tagging 922745

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

> tags 922745 + pending
Bug #922745 [src:gdb] gdb needs a backport for PR binutils/23919
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#916317: Ping

2019-02-20 Thread Jonathan Carter

Bug ping to delay harmful autoremove.

Bug#913467: nvidia-graphics-drivers: CVE‑2018‑6260: access to application data processed on the GPU through a side channel exposed by the GPU performance counters

2019-02-20 Thread Andreas Beckmann

On 2019-02-19 17:42, Moritz Muehlenhoff wrote:
>> Unfortunately we have no idea - NVIDIA's security tracker was never
>> updated after the initial mention of the CVE:
>>
>> https://nvidia.custhelp.com/app/answers/detail/a_id/4738
> 
> Ack, we can revisit once more information is available.

There was an upstream changelog entries that appeared for the 340.xx
series in the 410.93 release:

- Added a new kernel module parameter,
NVreg_RestrictProfilingToAdminUsers,
  to allow restricting the use of GPU performance counters to system
  administrators only.

but that was not announced afaik. That change should be in sid (410.xx)
and experimental (415.xx) (but there haven't been 340/390 releases
since). But the entry is again missing from the 418.xx beta upstream
changelog, which could either indicate a missing upstream merge or a
revert ...

Andreas

Bug#919928: marked as done (htslib breaks python-pysam autopkgtest)

Your message dated Wed, 20 Feb 2019 11:34:54 +
with message-id 
and subject line Bug#919928: fixed in python-pysam 0.15.2+ds-2
has caused the Debian Bug report #919928,
regarding htslib breaks python-pysam 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.)


-- 
919928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: htslib, python-pysam
Control: found -1 htslib/1.9-10
Control: found -1 python-pysam/0.15.1+ds-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of htslib the autopkgtest of python-pysam fails in
testing when that autopkgtest is run with the binary packages of htslib
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
htslib from testing1.9-10
python-pysam   from testing0.15.1+ds-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of htslib 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=htslib

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pysam/1739216/log.gz

=== FAILURES
===
_ TestIndexing.test_indexing_to_custom_location_works
__

self = 

def test_indexing_to_custom_location_works(self):
'''test indexing a file with a non-default location.'''

index_path = get_temp_filename(suffix='custom.tbi')
pysam.tabix_index(self.tmpfilename, preset="gff",
  index=index_path, force=True)
>   self.assertTrue(checkBinaryEqual(index_path, self.filename_idx))
E   AssertionError: False is not true

tests/tabix_test.py:89: AssertionError
 TestIndexing.test_indexing_with_explict_columns_works
_

self = 

def test_indexing_with_explict_columns_works(self):
'''test indexing via preset.'''

pysam.tabix_index(self.tmpfilename,
  seq_col=0,
  start_col=3,
  end_col=4,
  line_skip=0,
  zerobased=False)
self.assertTrue(checkBinaryEqual(
>   self.tmpfilename + ".tbi", self.filename_idx))
E   AssertionError: False is not true

tests/tabix_test.py:102: AssertionError
_ TestIndexing.test_indexing_with_preset_works
_

self = 

def test_indexing_with_preset_works(self):
'''test indexing via preset.'''

pysam.tabix_index(self.tmpfilename, preset="gff")
self.assertTrue(checkBinaryEqual(
>   self.tmpfilename + ".tbi", self.filename_idx))
E   AssertionError: False is not true

tests/tabix_test.py:81: AssertionError



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-pysam
Source-Version: 0.15.2+ds-2

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated python-pysam 
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, 20 Feb 2019 02:45:47 -0800
Source: python-pysam
Architecture: source
Version: 0.15.2+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 919928 920250
Changes:
 python-pysam (0.15.2+ds-2) unstable; urgency=medium
 .
   * Team u

Bug#920250: marked as done (python-pysam ftbfs from source (test failures))

Your message dated Wed, 20 Feb 2019 11:34:54 +
with message-id 
and subject line Bug#920250: fixed in python-pysam 0.15.2+ds-2
has caused the Debian Bug report #920250,
regarding python-pysam ftbfs from source (test failures)
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.)


-- 
920250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pysam
Version: 0.15.2+ds-1
Severity: serious
Tags: sid buster

=== FAILURES ===
_ TestIndexing.test_indexing_to_custom_location_works __

self = 

def test_indexing_to_custom_location_works(self):
'''test indexing a file with a non-default location.'''

index_path = get_temp_filename(suffix='custom.tbi')
pysam.tabix_index(self.tmpfilename, preset="gff",
  index=index_path, force=True)
>   self.assertTrue(checkBinaryEqual(index_path, self.filename_idx))
E   AssertionError: False is not true

tests/tabix_test.py:89: AssertionError
 TestIndexing.test_indexing_with_explict_columns_works _

self = 

def test_indexing_with_explict_columns_works(self):
'''test indexing via preset.'''

pysam.tabix_index(self.tmpfilename,
  seq_col=0,
  start_col=3,
  end_col=4,
  line_skip=0,
  zerobased=False)
self.assertTrue(checkBinaryEqual(
>   self.tmpfilename + ".tbi", self.filename_idx))
E   AssertionError: False is not true

tests/tabix_test.py:102: AssertionError
_ TestIndexing.test_indexing_with_preset_works _

self = 

def test_indexing_with_preset_works(self):
'''test indexing via preset.'''

pysam.tabix_index(self.tmpfilename, preset="gff")
self.assertTrue(checkBinaryEqual(
>   self.tmpfilename + ".tbi", self.filename_idx))
E   AssertionError: False is not true

tests/tabix_test.py:81: AssertionError
=== warnings summary ===
/usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py:367
  /usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py:367: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File:
/<>/python-pysam-0.15.2+ds/.pybuild/cpython2_2.7_pysam/build/tests/_compile_test.pyx
tree = Parsing.p_module(s, pxd, full_module_name)

.pybuild/cpython2_2.7_pysam/build/tests/AlignmentFile_test.py::TestTruncatedBAM::testTruncatedBamIterator

/<>/python-pysam-0.15.2+ds/.pybuild/cpython2_2.7_pysam/build/tests/AlignmentFile_test.py:1459:
UserWarning: no BGZF EOF marker; file may be truncated
ignore_truncation=True)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
 3 failed, 906 passed, 17 skipped, 2 warnings in 60.36 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/python-pysam-0.15.2+ds/.pybuild/cpython2_2.7_pysam/build;
python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make[1]: *** [debian/rules:32: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>/python-pysam-0.15.2+ds'
make: *** [debian/rules:24: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: python-pysam
Source-Version: 0.15.2+ds-2

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated python-pysam 
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, 20 Feb 2019 02:45:47 -0800
Source: python-pysam
Architecture: source
Version: 0.15.2+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Pa

Bug#866357: marked as done (reconserver FTBFs on several architectures: error: 'installSignalHandler' was not declared in this scope)

Your message dated Wed, 20 Feb 2019 11:20:06 +
with message-id 
and subject line Bug#922721: Removed package(s) from unstable
has caused the Debian Bug report #866357,
regarding reconserver FTBFs on several architectures: error: 
'installSignalHandler' was not declared in this scope
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.)


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

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

...
make  all-am
make[2]: Entering directory '/<>'
g++ -DPACKAGE_NAME=\"reConServer\" -DPACKAGE_TARNAME=\"reconserver\" 
-DPACKAGE_VERSION=\"0.15.2\" -DPACKAGE_STRING=\"reConServer\ 0.15.2\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"reconserver\" 
-DVERSION=\"0.15.2\" -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/sipxtapi -D__pingtel_on_posix__ -D_linux_ -D_REENTRANT 
-D_FILE_OFFS -DDEFAULT_BRIDGE_MAX_IN_OUTPUTS=20 -DRESIP_TOOLCHAIN_GNU 
-DUSE_CARES -DUSE_SSL -DUSE_IPV6  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fpermissive -c -o 
reConServer.o reConServer.cxx
In file included from MyUserAgent.hxx:16:0,
 from reConServer.hxx:13,
 from reConServer.cxx:49:
RegistrationForwarder.hxx:28:33: warning: 'template class std::auto_ptr' 
is deprecated [-Wdeprecated-declarations]
   void internalProcess(std::auto_ptr);
 ^~~~
In file included from /usr/include/c++/6/memory:81:0,
 from /usr/include/boost/function/function_base.hpp:16,
 from /usr/include/boost/function/detail/prologue.hpp:17,
 from /usr/include/boost/function.hpp:24,
 from /usr/include/recon/UserAgent.hxx:4,
 from reConServer.cxx:42:
/usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
   template class auto_ptr;
^~~~
In file included from reConServer.cxx:49:0:
reConServer.hxx:36:9: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
std::auto_ptr mConversationManager;
 ^~~~
In file included from /usr/include/c++/6/memory:81:0,
 from /usr/include/boost/function/function_base.hpp:16,
 from /usr/include/boost/function/detail/prologue.hpp:17,
 from /usr/include/boost/function.hpp:24,
 from /usr/include/recon/UserAgent.hxx:4,
 from reConServer.cxx:42:
/usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
   template class auto_ptr;
^~~~
reConServer.cxx: In member function 'virtual int 
reconserver::ReConServerProcess::main(int, char**)':
reConServer.cxx:763:25: error: 'installSignalHandler' was not declared in this 
scope
installSignalHandler();
 ^
reConServer.cxx:1364:16: error: 'mainLoop' was not declared in this scope
   mainLoop();
^
Makefile:444: recipe for target 'reConServer.o' failed
make[2]: *** [reConServer.o] Error 1
make[2]: Leaving directory '/<>'
Makefile:339: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:34: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
--- End Message ---
--- Begin Message ---
Version: 0.15.2-1+rm

Dear submitter,

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

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

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

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

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

Bug#922080: marked as done (borgbackup: fuse mount exposes backup to unauthorized users)

Your message dated Wed, 20 Feb 2019 10:55:58 + (UTC)
with message-id <140254903.3562327.1550660158...@mail.yahoo.com>
and subject line Re: Bug#922080: borgbackup: fuse mount exposes backup to 
unauthorized users
has caused the Debian Bug report #922080,
regarding borgbackup: fuse mount exposes backup to unauthorized users
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.)

-- 
922080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: borgbackup
Version: 1.1.8-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/borgbackup/borg/issues/3903
Control: fixed -1 1.1.9-1

As there is no CVE assigned for this issue, fill a bug for having an
unique identifier withing Debian.

Upstream issue: https://github.com/borgbackup/borg/issues/3903

Please adjust found versions as needed, is stable affected?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
 I propose to close the bug since it is fixed in unstable/testing (tomorrow)
G.

Il martedì 12 febbraio 2019, 19:37:56 CET, Gianfranco Costamagna 
 ha scritto:  

 On Mon, 11 Feb 2019 21:02:03 +0100 Salvatore Bonaccorso  
wrote:
> Source: borgbackup
> Version: 1.1.8-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Forwarded: https://github.com/borgbackup/borg/issues/3903
> Control: fixed -1 1.1.9-1
> 
> As there is no CVE assigned for this issue, fill a bug for having an
> unique identifier withing Debian.
> 
> Upstream issue: https://github.com/borgbackup/borg/issues/3903
> 
> Please adjust found versions as needed, is stable affected?
> 

Hello, yes, I think stable is affected.

the patch doesn't apply cleanly but it shoult be easy to rebase it.

Do you think you can go with a security update for stable?

G.
> Regards,
> Salvatore
> 
> 

  --- End Message ---

Bug#922739: marked as done (r-cran-vegan: autopkgtest regression)

Your message dated Wed, 20 Feb 2019 10:34:34 +
with message-id 
and subject line Bug#922739: fixed in r-cran-vegan 2.5-4+dfsg-2
has caused the Debian Bug report #922739,
regarding r-cran-vegan: autopkgtest regression
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.)


-- 
922739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-vegan
Version: 2.5-4+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of 2.5-4+dfsg-1, r-cran-vegan has been failing its
own autopkgtests [1] with the following error:

autopkgtest [15:46:18]: test run-unit-test: [---
gzip: *.gz: No such file or directory
autopkgtest [15:46:18]: test run-unit-test: ---]
autopkgtest [15:46:18]: test run-unit-test:  - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-vegan/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: r-cran-vegan
Source-Version: 2.5-4+dfsg-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-vegan 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, 20 Feb 2019 08:50:56 +0100
Source: r-cran-vegan
Binary: r-cran-vegan
Architecture: source
Version: 2.5-4+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Description:
 r-cran-vegan - Community Ecology Package for R
Closes: 922739
Changes:
 r-cran-vegan (2.5-4+dfsg-2) unstable; urgency=medium
 .
   * Fix and enhance autopkgtest
 Closes: #922739
Checksums-Sha1:
 c07d34df70fc88f16c9114f7dee9b68245684218 2141 r-cran-vegan_2.5-4+dfsg-2.dsc
 6c5099dcb0ba264ab81b7e9c74a7dd73b96d6d27 5380 
r-cran-vegan_2.5-4+dfsg-2.debian.tar.xz
Checksums-Sha256:
 4d5ba94a05ea5ea8136a16c04da363a262c6c8ca8a693142c0638a8ffbed70bd 2141 
r-cran-vegan_2.5-4+dfsg-2.dsc
 a7632478d82ba68a921934d4f70960301c93548f6bfc04822b74f7f554c7a7b2 5380 
r-cran-vegan_2.5-4+dfsg-2.debian.tar.xz
Files:
 7064e94872bb2ea1e617b66d5708a950 2141 gnu-r optional 
r-cran-vegan_2.5-4+dfsg-2.dsc
 6e8d6a8eb62d06f3a3a9f83405e96f8e 5380 gnu-r optional 
r-cran-vegan_2.5-4+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxtKIcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGu+Q//RDePQvX6wJNEEleprhq/WiQ2psHe51Tp
dD6E29R21Xn77RYaRXcl2xwKM8CmUQ+3YZOmCISgD69fwLtnYV6NH6KYoXfqaYl+
8OWw82YOU6SJ3eyEHBMDs8gSsUICV+vJMKBED3k3qw0/IV9OW6FARPFbnKoK+lkC
PjtpEu6f9sskvflVM4izW/Lf6hg8qBzEsP/KucQUUAgte/mxuLuvAr558IKSTle6
YDgOTalj6Xh/ySq32DfhDlyFXf9NTf0lXgB1kuL/De1ja6TF0PBiXfdIL7w23bsn
F59nvY3WOj7MT+7YCtKQz7hdbPxe2eD1CNxneLp/3nE/Mphl5ep45tBDzXKWlpCo
+ZEn/+iYZkfI+M6Nt3NJ/DVyt+x1DtPDH9r50Tzel0nYZOMtaMF/oehw1obiLF0P
l2dDeSD4HV/SGXkoC5cYDyD5cRac5w5HBvUFwXgRqp8biJKF7GhnR04d7jhQ/4ch
+MXeTPghAtCHfYzX69a38bPZm9GwNzQuTjTxw5+xjz1YZyr0wn+TPgFWdSmI0S7V
LdNvHIaGrhHLF3Z3n4XBn9RRZ5MFX7lG26Swm3HQXUxUpYrTwiHI7t/V8VJUsmis
clN2B3J+Q9xiiE5a8rYx5AIN78PiGae0fzJMG+glJFKNPqbN1c50TnWc3gp6uXM2
AkJ7UEfqnlA=
=mKSC
-END PGP SIGNATURE End Message ---

Bug#922745: gdb needs a backport for PR binutils/23919

2019-02-20 Thread Matthias Klose

Package: src:gdb
Version: 8.2.1-1
Severity: serious
Tags: sid buster

gdb needs a backport for PR binutils/23919. The PR fixes an issue with
compressed debug sections, and is needed so that gdb can handle the fixed debug
sections.  elfutils already has the fix.

The patch can be taken from the binutils 2.31 branch.

Processed (with 2 errors): cloning 919798, reassign -2 to src:libjsr305-java

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

> clone 919798 -2
Bug #919798 {Done: tony mancill } 
[src:maven-javadoc-plugin] javadoc: The code being documented uses modules but 
the packages defined in … are in the unnamed module
Bug #919800 {Done: tony mancill } 
[src:maven-javadoc-plugin] javadoc: The code being documented uses modules but 
the packages defined in … are in the unnamed module
Bug #919874 {Done: tony mancill } 
[src:maven-javadoc-plugin] javadoc: The code being documented uses modules but 
the packages defined in … are in the unnamed module
Bug #919875 {Done: tony mancill } 
[src:maven-javadoc-plugin] javadoc: The code being documented uses modules but 
the packages defined in … are in the unnamed module
Bug #919878 {Done: tony mancill } 
[src:maven-javadoc-plugin] javadoc: The code being documented uses modules but 
the packages defined in … are in the unnamed module
Bug #920747 {Done: tony mancill } 
[src:maven-javadoc-plugin] dirgra FTBFS with recent OpenJDK
Bug #920748 {Done: tony mancill } 
[src:maven-javadoc-plugin] jnr-posix FTBFS with recent OpenJDK
Bug #920750 {Done: tony mancill } 
[src:maven-javadoc-plugin] libparanamer-java FTBFS with recent OpenJDK
Bug #920794 {Done: tony mancill } 
[src:maven-javadoc-plugin] localizer FTBFS with recent OpenJDK
Bug #920795 {Done: tony mancill } 
[src:maven-javadoc-plugin] weupnp FTBFS with recent OpenJDK
Bug #922369 {Done: tony mancill } 
[src:maven-javadoc-plugin] javamail: FTBFS on Buster/Sid
Failed to clone 919798: Bug is marked as being merged with others. Use an 
existing clone.

> reassign -2 src:libjsr305-java
Failed to clear fixed versions and reopen on -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_package did not pass regex check
.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919928: [pysam-developers/pysam] Test suite failures (#761)

On Wed, Feb 20, 2019 at 08:39:02AM +, Michael R. Crusoe wrote:
> The difference between the Debian -10 release of htslib v1.9 and the Debian 
> -9 release of htslib is that libdeflate, GCS, and S3 are enabled.
> 
> This even changes the output of `tabix` itself when indexing 
> https://github.com/pysam-developers/pysam/blob/master/tests/tabix_data/example.gtf.gz
>  so it is no surprise that these pysam tests break.

So your suggestion is to generate a new example.gtf.gz to compare with the test 
result?
If yes, would you mind creating such a file to fix the test suite?
Thanks for your investigation in any case, Andreas.

Bug#917744: marked as done (php-zeta-base: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /usr/share/php/ezc/UnitTest/test/case.php:33)

Your message dated Wed, 20 Feb 2019 08:43:53 +
with message-id 
and subject line Bug#917744: fixed in php-zeta-base 1.9.1-1
has caused the Debian Bug report #917744,
regarding php-zeta-base: FTBFS: PHP Fatal error:  Uncaught Error: Class 
'PHPUnit_Framework_TestCase' not found in 
/usr/share/php/ezc/UnitTest/test/case.php:33
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.)


-- 
917744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-zeta-base
Version: 1.9-3
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 '/<>'
> phpunit
> PHP Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not 
> found in /usr/share/php/ezc/UnitTest/test/case.php:33
> Stack trace:
> #0 /usr/share/php/ezc/UnitTest/autoload.php(19): require()
> #1 [internal function]: PHPUnit\Util\FileLoader::{closure}('ezcTestCase')
> #2 /<>/tests/base_init_test.php(34): 
> spl_autoload_call('ezcTestCase')
> #3 /usr/share/php/PHPUnit/Util/FileLoader.php(57): 
> include_once('/build/php-zeta...')
> #4 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/build/php-zeta...')
> #5 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-zeta...')
> #6 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-zeta...')
> #7 /usr/share/php/PHPUnit/Util/Configuration.php(1137): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #8 /usr/share/php/PHPUnit/Util/Configuration.php(996): 
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #9 /u in /usr/share/php/ezc/UnitTest/test/case.php on line 33
> make[1]: *** [debian/rules:17: override_dh_auto_test] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/php-zeta-base_1.9-3_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: php-zeta-base
Source-Version: 1.9.1-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-zeta-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: SHA256

Format: 1.8
Date: Thu, 14 Feb 2019 16:38:30 -1000
Source: php-zeta-base
Architecture: source
Version: 1.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 882917 917744
Changes:
 php-zeta-base (1.9.1-1) unstable; urgency=medium
 .
   [ Derick Rethans ]
   * Renamed and updated license file
   * Go with Base 1.9.1
 .
   [ Remi Collet ]
   * object is a reserved keyword in PHP 7.2
 .
   [ David Prévot ]
   * Update copyright
   * Move repository to salsa.d.o
   * Drop get-orig-source target
   * Simplify clean target
   * Use debhelper-compat 12
   * Update Standards-Version to 4.3.0
   * Update versioned build-dependency
   * Update for recent version of PHPUnit (Closes: #882917, #917744)
   * Workaround autload issue during tests
Checksums-Sha1:
 89e5af3415065414f8ee717c0623469b18f7378e 1856 php-zeta-base_1.9.1-1.dsc
 9b7f2a95442fda788b9a6d2720fdcde7eee75ab8 252350 php-zeta-base_1.9.1.orig.tar.gz
 c982b6c46be73bc5531f9fbecdcb925cbc755d20 6120 
php-zeta-base_1.9.1-1.debian.tar.xz
 a37d4d6209f2c94a316cc04bc6462375fe4e0666 7817 
php-zeta-base_1.9.1-1_amd64.buildinfo
Checksums-Sha256:
 a3dc4282a42ab76365feaca58761581f4d11200b455a7b3d450b18b8af561103 1856 
php-zeta-base_1.9.1-1.dsc
 df4c0c7282e5

Bug#882917: marked as done (php-zeta-base FTBFS with phpunit 6.4.4-2)

Your message dated Wed, 20 Feb 2019 08:43:52 +
with message-id 
and subject line Bug#882917: fixed in php-zeta-base 1.9.1-1
has caused the Debian Bug report #882917,
regarding php-zeta-base FTBFS with phpunit 6.4.4-2
to be marked as done.

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

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


-- 
882917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-zeta-base
Version: 1.9-3
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-zeta-base-1.9'
phpunit
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/usr/share/php/ezc/UnitTest/test/case.php on line 33
debian/rules:17: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-zeta-base
Source-Version: 1.9.1-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-zeta-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: SHA256

Format: 1.8
Date: Thu, 14 Feb 2019 16:38:30 -1000
Source: php-zeta-base
Architecture: source
Version: 1.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 882917 917744
Changes:
 php-zeta-base (1.9.1-1) unstable; urgency=medium
 .
   [ Derick Rethans ]
   * Renamed and updated license file
   * Go with Base 1.9.1
 .
   [ Remi Collet ]
   * object is a reserved keyword in PHP 7.2
 .
   [ David Prévot ]
   * Update copyright
   * Move repository to salsa.d.o
   * Drop get-orig-source target
   * Simplify clean target
   * Use debhelper-compat 12
   * Update Standards-Version to 4.3.0
   * Update versioned build-dependency
   * Update for recent version of PHPUnit (Closes: #882917, #917744)
   * Workaround autload issue during tests
Checksums-Sha1:
 89e5af3415065414f8ee717c0623469b18f7378e 1856 php-zeta-base_1.9.1-1.dsc
 9b7f2a95442fda788b9a6d2720fdcde7eee75ab8 252350 php-zeta-base_1.9.1.orig.tar.gz
 c982b6c46be73bc5531f9fbecdcb925cbc755d20 6120 
php-zeta-base_1.9.1-1.debian.tar.xz
 a37d4d6209f2c94a316cc04bc6462375fe4e0666 7817 
php-zeta-base_1.9.1-1_amd64.buildinfo
Checksums-Sha256:
 a3dc4282a42ab76365feaca58761581f4d11200b455a7b3d450b18b8af561103 1856 
php-zeta-base_1.9.1-1.dsc
 df4c0c7282e5c017e24bd4d9bab36980e63a5729e67ffba7cf7c4f4ba2160e23 252350 
php-zeta-base_1.9.1.orig.tar.gz
 6950c6fc16fce5da75d3187796907f8097a45b8d31743242aa1330859c412b07 6120 
php-zeta-base_1.9.1-1.debian.tar.xz
 00af8e9325089692106f96fcdb3b1df2b829c214968e526294e6473cf541c0f4 7817 
php-zeta-base_1.9.1-1_amd64.buildinfo
Files:
 5315403327c98ca36b119bca2334bddf 1856 php optional php-zeta-base_1.9.1-1.dsc
 fad8693f65cafef09034a1ee811f05fe 252350 php optional 
php-zeta-base_1.9.1.orig.tar.gz
 709a8f5d27b213a5d7f150057b957a4c 6120 php optional 
php-zeta-base_1.9.1-1.debian.tar.xz
 6ccdf683f1fe81b96ae6d1257236d4b5 7817 php optional 
php-zeta-base_1.9.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAlxtEF8SHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08EQ8H/jMo4uBkv7iEkgOoHYGekn2SuPPx1u3l
P/FPFaHn1ObZQKoMudueALnPyzn/enHbEsq+hHFzRfTo87jFh3y1Sg1UwbXXyUtR
M1iYJ9O2P9VjrSTrj4uaZD45pppQJ79caxuAsdrkVWB5GeeS79VFnuU1+A/0oRsW
Jfp2JMP/XikCpJSYSMqb2C+t8kKrDmt30teJnqxW75eUMxHcWRbGwndUKmJzKlRc
rm8xxEOoxYKrCm/AK2l2gHWDSINpBeDEiEIDPe9uWhXVlW8YgzvsIQAxOC56iRSt
TZc4AuowOjHuoq3foYfytB+t0/ihMLn8YibVJUtyGwNSFnwLh6zaYvI=
=p3xL
-END PGP SIGNATURE End Message ---

Bug#916102: closing 916102

2019-02-20 Thread Salvatore Bonaccorso

close 916102 2.7.6+dfsg-1
thanks

Processed: closing 916102

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

> close 916102 2.7.6+dfsg-1
Bug #916102 {Done: Salvatore Bonaccorso } [src:ansible] 
ansible: CVE-2018-16876: Information disclosure in vvv+ mode with no_log on
Ignoring request to alter fixed versions of bug #916102 to the same values 
previously set
Bug #916102 {Done: Salvatore Bonaccorso } [src:ansible] 
ansible: CVE-2018-16876: Information disclosure in vvv+ mode with no_log on
Bug 916102 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: closing 916102

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

> close 916102 2.7.6+dfsg-1
Bug #916102 [src:ansible] ansible: CVE-2018-16876: Information disclosure in 
vvv+ mode with no_log on
Marked as fixed in versions ansible/2.7.6+dfsg-1.
Bug #916102 [src:ansible] ansible: CVE-2018-16876: Information disclosure in 
vvv+ mode with no_log on
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: severity of 916102 is serious

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

> severity 916102 serious
Bug #916102 [src:ansible] ansible: CVE-2018-16876: Information disclosure in 
vvv+ mode with no_log on
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 922537 is serious