Processed: Bug #919103 in libreoffice marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919103 [libreoffice-kde5] libreoffice-kde5: failure to upgrade from 
stretch: soffice.odg also in libreoffice-kde
Added tag(s) pending.

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

Bug#919103: Bug #919103 in libreoffice marked as pending

[Rene Engelhard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/462630fbb685595d134ada5dde5e3b5c7f85d6e7


debian/control.kde*.in: Replaces: libreoffice-kde (<< 1:6.1.0~alpha1-1) 
(closes: #919103)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919103

Bug#914632: uw-imap: CVE-2018-19518

[Salvatore Bonaccorso]

Hi Magnus,

On Fri, Dec 28, 2018 at 10:22:53AM +0100, Moritz Mühlenhoff wrote:
> On Wed, Dec 26, 2018 at 05:20:40PM +0100, Magnus Holmgren wrote:
> > > CVE-2018-19518[0]:
> > > | University of Washington IMAP Toolkit 2007f on UNIX, as used in
> > > | imap_open() in PHP and other products, launches an rsh command (by
> > > | means of the imap_rimap function in c-client/imap4r1.c and the
> > > | tcp_aopen function in osdep/unix/tcp_unix.c) without preventing
> > > | argument injection, 
> > 
> > I'm wondering if anyone would complain if I'd disable RSH (SSH) connections 
> > altogether.
> 
> Full ack, that seems like the most sensible fix.

Any news on this approach, or did you spot any problem with that way?

Regards,
Salvatore

Bug#912633: Status Update

[Soren Stoutner]

Any idea when the new version that fixes this bug will be released?

-- 
Soren Stoutner
Small Business Tech Solutions
so...@smallbusinesstech.net
623-262-6169

Bug#895039: marked as done (ido: deprecated in Debian, switch over to ayatana-ido)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 05:12:47 +
with message-id 
and subject line Bug#919129: Removed package(s) from unstable
has caused the Debian Bug report #895039,
regarding ido: deprecated in Debian, switch over to ayatana-ido
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.)


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

Package: src:ido
Severity: serious

The IDO shared lib (Indicator Display Objects) is deprecated in Debian  
and shall be phased out during the buster release cycle.


Applications using it (mostly indicator renderers) shall switch over  
to src:ayatana-ido instead. The following renderers of indicators have  
already been ported to ayatana-ido:


  mate-indicator-applet
  xfce4-indicator-plugin

Another renderer has a bug with a patch filed:

  budgie-indicator-applet

So, the current status is: Once that budgie-indicator-applet has been  
ported, src:ido can be removed from Debian.


Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgp0cgMhgDsyY.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Version: 0.3.4-1.1+rm

Dear submitter,

as the package ido 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/919129

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

Processed: Re: xnbd FTBFS with glibc 2.28

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #916002 [src:xnbd] xnbd FTBFS with glibc 2.28
Added tag(s) patch.

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

Bug#916002: xnbd FTBFS with glibc 2.28

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/glibc-2.28.patch: Fix FTBFS against glibc 2.28.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru xnbd-0.3.0/debian/patches/glibc-2.28.patch 
xnbd-0.3.0/debian/patches/glibc-2.28.patch
--- xnbd-0.3.0/debian/patches/glibc-2.28.patch  1969-12-31 19:00:00.0 
-0500
+++ xnbd-0.3.0/debian/patches/glibc-2.28.patch  2019-01-12 23:33:17.0 
-0500
@@ -0,0 +1,19 @@
+Description: Fix build with glibc 2.28
+Author: Logan Rosen 
+Forwarded: https://bitbucket.org/hirofuchi/xnbd/pull-requests/1
+Last-Update: 2019-01-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/lib/io.h
 b/lib/io.h
+@@ -35,6 +35,10 @@
+ #include 
+ #include 
+ 
++#ifdef __GNU_LIBRARY__
++#include 
++#endif
++
+ 
+ void read_all(int fd, void *buf, size_t len);
+ void write_all(int fd, const void *buf, size_t len);
diff -Nru xnbd-0.3.0/debian/patches/series xnbd-0.3.0/debian/patches/series
--- xnbd-0.3.0/debian/patches/series2013-05-20 10:47:09.0 -0400
+++ xnbd-0.3.0/debian/patches/series2019-01-12 23:32:30.0 -0500
@@ -0,0 +1 @@
+glibc-2.28.patch

Bug#919139: cli-common: Invalid maintainer email address

[Scott Kitterman]

Package: cli-common
Version: 0.9+nmu3
Severity: serious
Justification: Policy 3.3

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pkg-cli-common-t...@lists.alioth.debian.org
host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
SMTP error from remote mail server after RCPT 
TO::
550 Unrouteable address

A valid maintainer address is required.

Scott K

Bug#905674: parallel citation-begging issue

[Kurt Fitzner]

Hi Rogerio, 

I am writing in support of the recent patch to remove the citation
message from Debian's version of GNU Parallel.  This citation
solicitation is actually quite troubling from an academic perspective,
not just from a licensing standpoint. 

The assertion of Mr. Tange, the upstream author, that "[a]cademic
tradition requires you to cite works you base your article on" is true,
however the active words here are "works" and "base".  In this case,
when writing an article, the nature of the "work" I would base my
article on would be another article.  An academic article (in general)
is not inherently based on the work of the programmer who wrote some of
the software infrastructure used to create or analyze the data.  Mr.
Tange's assertion that mere use of GNU Parallel constitutes a moral
obligation to cite an entry-level self-help tutorial on how to use that
software is an egregious mischaracterization of the academic tradition
Mr. Tange relies on.  Especially, in this case, where the software in
question has nothing to do with data analysis or production, but is a
middleware parallelization job scheduler.  If the article in question is
itself on middleware parallelization job schedulers, that's one thing. 
In virtually every other case the notice is just fishing for something
that is highly inappropriate.  The correct way of mentioning the
software involved is in a footnote, or perhaps in an appendix, when
describing how to replicate the results and analysis.  You include
scripts involved, and the "evidence chain" of the data in such a way. 
This is problematic for Mr. Tange, however, because footnotes are not
tracked.  Citations are.  Which is clearly why he is fishing for them. 

Now, the above isn't Debian's problem.  This is academia's problem. 
What is Debian's problem is what will happen if Mr. Tange convinces
Debian leadership that the citation-begging notice has to be allowed
back in.  Because this will open the flood gates to everyone who wants
the prestige of being cited in an academic journal.  All you have to do
is have a minor article on a piece software, it doesn't have to be an
academic article - just a how to use it will do, published literally
anywhere that is citable, for any software in the processing-chain
commonly used in academia.  Use a shell script, be prepared to have the
Bash authors start putting in citation-begging notices.  Arguably those
that wrote the actual Linux task schedulers and SMP code are just as
worthy of notice as the authors of GNU Parallel.  Or GCC, or PERL, or
Python.  Or how about grep?  If this citation-begging notice gets back
in to Debian, it will become a far larger issue than just whether or not
Mr. Tange is skating on the right side of the GPL/DFSG legalities. 
Debian is going to have to ask the question on whether advertising in a
STDERR message is appropriate at all. 

I would ask you, if and when this comes up for review with the
leadership at Debian, to bring up these issues.  It is my hope that
Debian will see that it is in their best interest to look at a policy
that will exclude this kind of behaviour, before it spreads. 

Thank-you 

Regards, 

  Kurt Fitzner

Bug#917761: marked as done (php-monolog: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /<>/tests/Monolog/ErrorHandlerTest.php:16)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 02:45:49 +
with message-id 
and subject line Bug#917761: fixed in php-monolog 1.24.0-1
has caused the Debian Bug report #917761,
regarding php-monolog: FTBFS: PHP Fatal error:  Uncaught Error: Class 
'PHPUnit_Framework_TestCase' not found in 
/<>/tests/Monolog/ErrorHandlerTest.php:16
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap autoload.php --include-path src
> PHP Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not 
> found in /<>/tests/Monolog/ErrorHandlerTest.php:16
> Stack trace:
> #0 /usr/share/php/PHPUnit/Util/FileLoader.php(57): include_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/build/php-mono...')
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-mono...')
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-mono...')
> #4 /usr/share/php/PHPUnit/Util/Configuration.php(1137): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #5 /usr/share/php/PHPUnit/Util/Configuration.php(996): 
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #6 /usr/share/php/PHPUnit/TextUI/Command.php(902): 
> PHPUnit\Util\Configuration->getTestSuiteConfiguration('')
> #7 /usr/share/php/PHPUnit/TextUI/Command.php(173): 
> PHPUnit\TextUI\Command->handleArguments(Array)
> #8 /usr/share/php/PHPUnit in 
> /<>/tests/Monolog/ErrorHandlerTest.php on line 16
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/php-monolog_1.23.0-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
php-monolog, 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-monolog 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: Sun, 13 Jan 2019 12:15:58 +1100
Source: php-monolog
Binary: php-monolog
Architecture: source
Version: 1.24.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 php-monolog - send logs to various destination and web services
Closes: 917761
Changes:
 php-monolog (1.24.0-1) unstable; urgency=medium
 .
   * Drop versioned dependencies satisfied in stable
   * Drop get-orig-source target
   * Use https in Format
   * Move Vcs-* to salsa.d.o
   * Make preview handling more generic
   * Track version 1 for Buster
   * Drop outdated test suite (Closes: #917761)
   * Use debhelper-compat 12
   * Update Standards-Version to 4.3.0
Checksums-Sha1:
 72685f64532bbdf015f12525456313bdaf971607 1663 php-monolog_1.24.0-1.dsc
 5d4d370be4eb91b7bb445574dddb922b97b24dd2 133367 php-monolog_1.24.0.orig.tar.gz
 c9c4a542f03040ad8e0a5356f876be0094868fb0 5112 
php-monolog_1.24.0-1.debian.tar.xz
 a8e84ea1c48f81764b731b5e34f4e9e4250b109e 5662 
php-monolog_1.24.0-1_amd64.buildinfo
Checksums-Sha256:
 7f326db21ae1ef4d17a1b3d41804ad437442dd8b6b05b68f750cbf061514e472 1663 
php-monolog_1.24.0-1.dsc
 9879db1eeac4b1c52d69fb6179870529e87689eee0e7a47694dbdc68a866a257 133367 

Bug#875404: gridengine and java

[Afif Elghraoui]

Control: tag -1 + help

status update on this bug:

I tried to get the build working months ago with the java10 branch on 
Salsa [1]. The current issue is an error when trying to use jemalloc, 
which I've reported upstream [2]. the error is


[java] [java] 
/<>/gridengine-8.1.9+dfsg/source/libs/jgdi/build.xml:495: 
java.lang.UnsatisfiedLinkError?: 
/<>/gridengine-8.1.9+dfsg/source/LINUXAMD64/libdrmaa.so: 
/usr/lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in 
static TLS block


and more details (including the build log) are on the upstream ticket [2].


1. https://salsa.debian.org/hpc-team/gridengine/tree/java10
2. https://arc.liv.ac.uk/trac/SGE/ticket/1642

--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Processed: gridengine and java

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + help
Bug #875404 [src:gridengine] FTBFS with Java 9: sun.rmi.server
Added tag(s) help.

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

Processed: limit source to php-monolog, tagging 917761

[Debian Bug Tracking System]

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

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

> tags 917761 + pending
Bug #917761 [src:php-monolog] php-monolog: FTBFS: PHP Fatal error:  Uncaught 
Error: Class 'PHPUnit_Framework_TestCase' not found in 
/<>/tests/Monolog/ErrorHandlerTest.php:16
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#918916: Unicorn not reporting proper version for gemfile?

[Julian Calaby]

Package: unicorn
Version: 5.4.1-1
Followup-For: Bug #918916

For reference:

As a workaround, changing _both_ versions in the shipped gemspec and the
version in the filename from 0 to 5.4.1 fixes packages which depend on
this, e.g. gitlab.

Detailed steps:

1. Edit /usr/share/rubygems-integration/2.5.0/specifications/unicorn-0.gemspec
2. On line 2, change 0 to 5.4.1 so it reads: # stub: unicorn 5.4.1 ruby lib
3. On line 7, change 0 to 5.4.1 so it reads:   s.version = "5.4.1"
4. Rename the file to unicorn-5.4.1.gemspec

Thanks,

Julian Calaby

Bug#916606: Possible cause

[bitfreak25]

On Mon, 7 Jan 2019 08:59:30 +0100 Stephen Kitt  wrote:
> On Sat, Jan 05, 2019 at 03:32:02AM -0500, Full Name wrote:
> > A similar problem occurs in DOSBox.  I'm not sure if this is a bug in xorg 
> > or SDL.
> > 
> > What is happening is that when you unpause, lbreakout2 tries to fence the 
> > mouse in its window,
> > but instead the window immediately loses focus causing lbreakout2 to pause 
> > again.  I'm not sure
> > why the mouse lock works the first time, but once it releases it cannot be 
> > regained.
> 
> Yup, this does seem to be the case. This issue was fixed in DOSBox
> with the patch available at
> https://www.dosbox.com/downloads/74-2-events.diff (also included in
> the current DOSBox package in unstable and testing).
> 
> Regards,
> 
> Stephen

Hi,

I've implemented the mentioned fix for DOSBox and it worked. (see added 
diff-file) But I couldn't add the macro from the DOSBox diff, because it 
doesn't work (don't know why). I'm also not very familiar with debian 
packaging, so I expect the diff file wasn't created/applied correctly. But here 
it is.

Kind regards,
bitfreak25
--- lbreakout2-2.6.5.orig/client/game.c	2013-05-03 19:06:20.0 +0200
+++ lbreakout2-2.6.5/client/game.c	2019-01-13 00:21:06.339765000 +0100
@@ -1150,6 +1150,17 @@
 		/* check wether an event occured */
 		button_clicked = key_pressed = 0;
 		if ( SDL_PollEvent(  ) ) {
+			// Special code for broken SDL with Xorg 1.20.1, where pairs of inputfocus gain and loss events are generated
+			// when locking the mouse in windowed mode.
+			if (event.type == SDL_ACTIVEEVENT && event.active.state == SDL_APPINPUTFOCUS && event.active.gain == 0) {
+SDL_Event test; //Check if the next event would undo this one.
+if (SDL_PeepEvents(,1,SDL_PEEKEVENT,SDL_ACTIVEEVENTMASK) == 1 && test.active.state == SDL_APPINPUTFOCUS && test.active.gain == 1) {
+	// Skip both events.
+	SDL_PeepEvents(,1,SDL_GETEVENT,SDL_ACTIVEEVENTMASK);
+	continue;
+}
+			}
+			
 			if ( client_state == CS_PAUSE && game->game_type == GT_NETWORK )
 gui_dispatch_event( , ms );
 			else

Bug#917700: dimbl: FTBFS: build-dependency not installable: libtimbl4-dev

[Steve Langasek]

Package: dimbl
Followup-For: Bug #917700
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Hello,

FWIW, no new upstream version is required in order to fix this build
failure, it's a trivial change to debian/control to drop the versioned -dev
package names leaving only the unversioned ones.

I've uploaded the attached patch to Ubuntu to fix the bug there.  But since
there is a comment suggesting that this may not be worth maintaining in
Debian and should be removed, I have not uploaded an NMU.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru dimbl-0.15/debian/control dimbl-0.15/debian/control
--- dimbl-0.15/debian/control   2018-01-24 13:15:46.0 +0100
+++ dimbl-0.15/debian/control   2019-01-13 01:27:06.0 +0100
@@ -7,8 +7,8 @@
 Build-Depends: debhelper (>= 11~),
pkg-config,
libxml2-dev,
-   libticcutils2-dev | libticcutils-dev,
-   libtimbl4-dev | libtimbl-dev
+   libticcutils-dev,
+   libtimbl-dev
 Standards-Version: 4.1.3
 Vcs-Browser: https://salsa.debian.org/science-team/dimbl.git
 Vcs-Git: https://salsa.debian.org/science-team/dimbl.git

Bug#918260: ruby-protected-attributes: Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed

[xia boles]

On Fri, 04 Jan 2019 22:00:09 +0200 Adrian Bunk  wrote:
> Source: ruby-protected-attributes
> Version: 1.1.4-2
> Severity: serious
>
> The following packages have unmet dependencies:
>  ruby-protected-attributes : Depends: ruby-activemodel (< 2:5.0) but 
> 2:5.2.0+dfsg-2 is to be installed
>
>
Sent from Mail for Windows 10
Hi, what processor architecture is it?
Otherwise, try installing ruby-activemodel.

Processed: Sorry, wrong bug number

[Debian Bug Tracking System]

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

> severity 827832 serious
Bug #827832 [src:python-pytc] python-shade: Improvement of error message when 
failing to build on small machines (?)
Severity set to 'serious' from 'minor'
> retitle 827832 python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found
Bug #827832 [src:python-pytc] python-shade: Improvement of error message when 
failing to build on small machines (?)
Changed Bug title to 'python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not 
found' from 'python-shade: Improvement of error message when failing to build 
on small machines (?)'.
> thanks
Stopping processing here.

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

Processed: Re: Investigation results

[Debian Bug Tracking System]

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

> severity 918751 minor
Bug #918751 [src:python-shade] python-shade: FTBFS in sid
Severity set to 'minor' from 'serious'
> retitle 918751 python-shade: Improvement of error message when failing to 
> build on small machines (?)
Bug #918751 [src:python-shade] python-shade: FTBFS in sid
Changed Bug title to 'python-shade: Improvement of error message when failing 
to build on small machines (?)' from 'python-shade: FTBFS in sid'.
> thanks
Stopping processing here.

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

Bug#918751: Investigation results

[Santiago Vila]

severity 918751 minor
retitle 918751 python-shade: Improvement of error message when failing to build 
on small machines (?)
thanks

Sorry, this was my fault.

Here is the reason why it failed for me:

This package (version 1.7.0) used to need 200 MB of RAM to build,
and I was using a small machine (1 GB of RAM) to build it. So far, so
good.

The problem was that the current version (1.30.0) required around 1900 MB
of RAM to build (a lot more than before) while I was still using small
machines to build it.

(You might be wondering why I'm using machines with 1 GB to build
Debian packages: well, around 96.6% of all Debian packages in buster
require 1 GB of RAM or less to build, and machines with 2 GB of RAM
usually cost double the price per-hour).

So no FTBFS problem here. Special thanks to Stewart Ferguson for
actually looking at the build logs.

Now I wonder if the error message in cases like this could be improved
so that it's even more clear that lack of RAM was the problem.
Probably it does not worth the effort, but I leave this to you.

Thanks a lot.

Bug#919002: marked as done (CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 23:16:47 +
with message-id 
and subject line Bug#918841: fixed in systemd 240-4
has caused the Debian Bug report #918841,
regarding CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and 
CVE-2018-16866
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.)


-- 
918841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 240-3
Severity: normal

Dear all,
Saw this on zdnet today -

https://www.zdnet.com/article/new-linux-systemd-security-holes-uncovered/

I did the cursory thing of seeing maybe if the CVE's had been
mentioned in the changelog -

/usr/share/doc/systemd$ zless changelog.Debian.gz | grep CVE
(CVE-2018-15686, Closes: #912005)
(CVE-2018-15688, LP: #1795921, Closes: #912008)
(CVE-2018-15687, LP: #1796692, Closes: #912007)
  non-terminal path components. (CVE-2018-6954, Closes: #890779)
(CVE-2017-15908, Closes: #880026, LP: #1725351)
CVE-2017-9445 (Closes: #866147, LP: #1695546)
Fixes: CVE-2017-9217 (Closes: #863277)
by avoiding a race condition in scraping /proc (CVE-2013-4327).
  Fixes CVE-2012-1174, closes: #664364
- Fixes local DoS (CVE-2012-1101).  Closes: #662029

I did also look at systemd --version if GCC's -fstack-clash-protection
is mentioned therein in the version command but couldn't find it.

It is very much possible that you may be working on it, in any case,
look forward to the fixes.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.13.2-3
ii  libaudit11:2.8.4-2
ii  libblkid12.33-0.2
ii  libc62.28-2
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.6-1
ii  libgcrypt20  1.8.4-4
ii  libgnutls30  3.6.5-2
ii  libgpg-error01.33-3
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-3
ii  libkmod2 25-2
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.2-1.3
ii  libmount12.33-0.2
ii  libpam0g 1.1.8-3.8
ii  libseccomp2  2.3.3-3
ii  libselinux1  2.8-1+b1
ii  libsystemd0  240-3
ii  mount2.33-0.2
ii  util-linux   2.33-0.2

Versions of packages systemd recommends:
ii  dbus1.12.12-1
ii  libpam-systemd  240-3

Versions of packages systemd suggests:
ii  policykit-10.105-23
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.132
ii  udev 240-2

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-4

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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: Sat, 12 Jan 2019 21:49:44 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-4
Distribution: unstable
Urgency: medium

Bug#918841: marked as done (systemd: CVE-2018-16864)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 23:16:47 +
with message-id 
and subject line Bug#918841: fixed in systemd 240-4
has caused the Debian Bug report #918841,
regarding systemd: CVE-2018-16864
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.)


-- 
918841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 204-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 232-25+deb9u6
Control: found -1 240-2

Hi,

The following vulnerability was published for systemd.

CVE-2018-16864[0]:
memory corruption

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-16864
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16864
[1] https://www.openwall.com/lists/oss-security/2019/01/09/3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-4

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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: Sat, 12 Jan 2019 21:49:44 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 909396 917607 918841 918848 918927
Changes:
 systemd (240-4) unstable; urgency=medium
 .
   [ Benjamin Drung ]
   * Fix shellcheck issues in initramfs-tools scripts
 .
   [ Michael Biebl ]
   * Import patches from v240-stable branch (up to f02b5472c6)
 - Fixes a problem in logind closing the controlling terminal when using
   startx. (Closes: #918927)
 - Fixes various journald vulnerabilities via attacker controlled alloca.
   (CVE-2018-16864, CVE-2018-16865, Closes: #918841, Closes: #918848)
   * sd-device-monitor: Fix ordering of setting buffer size.
 Fixes an issue with uevents not being processed properly during coldplug
 stage and some kernel modules not being loaded via "udevadm trigger".
 (Closes: #917607)
   * meson: Stop setting -fPIE globally.
 Setting -fPIE globally can lead to miscompilations on certain
 architectures. Instead use the b_pie=true build option, which was
 introduced in meson 0.49. Bump the Build-Depends accordingly.
 (Closes: #909396)
Checksums-Sha1:
 71e37bb2f12272a16b7b50f45f77d47518e8c5a0 4898 systemd_240-4.dsc
 e8160f259001a6563c5a7523aa22e58a90883f9c 164740 systemd_240-4.debian.tar.xz
 

Bug#918322: marked as done (4.19.0-1-amd64 kernel fails to boot with "Gave up waiting for root file system device")

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 23:16:47 +
with message-id 
and subject line Bug#917607: fixed in systemd 240-4
has caused the Debian Bug report #917607,
regarding 4.19.0-1-amd64 kernel fails to boot with "Gave up waiting for root 
file system device"
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.)


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



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

Kernel: Linux 4.9.0-8-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-4

We believe that the bug you reported is fixed in the latest version of
systemd, 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.
Michael Biebl  (supplier of updated systemd 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: Sat, 12 Jan 2019 21:49:44 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 909396 917607 918841 918848 918927
Changes:
 systemd (240-4) unstable; urgency=medium
 .
   [ Benjamin Drung ]
   * Fix shellcheck issues in initramfs-tools scripts
 .
   [ Michael Biebl ]
   * Import patches from v240-stable branch (up to f02b5472c6)
 - Fixes a problem in logind closing the controlling terminal when using
   startx. (Closes: #918927)
 - Fixes various journald vulnerabilities via attacker controlled alloca.
   (CVE-2018-16864, CVE-2018-16865, Closes: #918841, Closes: #918848)
   * sd-device-monitor: Fix ordering of setting buffer size.
 Fixes an issue with uevents not being processed properly during coldplug
 stage and some kernel modules not being loaded via "udevadm trigger".
 (Closes: #917607)
   * meson: Stop setting -fPIE globally.
 Setting -fPIE globally can lead to miscompilations on certain
 architectures. Instead use the b_pie=true build option, which was
 introduced in meson 0.49. Bump the Build-Depends accordingly.
 (Closes: #909396)
Checksums-Sha1:
 71e37bb2f12272a16b7b50f45f77d47518e8c5a0 4898 systemd_240-4.dsc
 e8160f259001a6563c5a7523aa22e58a90883f9c 164740 systemd_240-4.debian.tar.xz
 b70e6881b2d011a8afe72697b004e1333084660f 9092 systemd_240-4_source.buildinfo
Checksums-Sha256:
 

Bug#918848: marked as done (systemd: CVE-2018-16865)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 23:16:47 +
with message-id 
and subject line Bug#918848: fixed in systemd 240-4
has caused the Debian Bug report #918848,
regarding systemd: CVE-2018-16865
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.)


-- 
918848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 43-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 232-25+deb9u6
Control: found -1 240-2

Hi,

The following vulnerability was published for systemd, opening
tracking bug.

CVE-2018-16865[0]:
memory corruption

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-16865
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16865
[1] https://www.openwall.com/lists/oss-security/2019/01/09/3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-4

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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: Sat, 12 Jan 2019 21:49:44 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 909396 917607 918841 918848 918927
Changes:
 systemd (240-4) unstable; urgency=medium
 .
   [ Benjamin Drung ]
   * Fix shellcheck issues in initramfs-tools scripts
 .
   [ Michael Biebl ]
   * Import patches from v240-stable branch (up to f02b5472c6)
 - Fixes a problem in logind closing the controlling terminal when using
   startx. (Closes: #918927)
 - Fixes various journald vulnerabilities via attacker controlled alloca.
   (CVE-2018-16864, CVE-2018-16865, Closes: #918841, Closes: #918848)
   * sd-device-monitor: Fix ordering of setting buffer size.
 Fixes an issue with uevents not being processed properly during coldplug
 stage and some kernel modules not being loaded via "udevadm trigger".
 (Closes: #917607)
   * meson: Stop setting -fPIE globally.
 Setting -fPIE globally can lead to miscompilations on certain
 architectures. Instead use the b_pie=true build option, which was
 introduced in meson 0.49. Bump the Build-Depends accordingly.
 (Closes: #909396)
Checksums-Sha1:
 71e37bb2f12272a16b7b50f45f77d47518e8c5a0 4898 systemd_240-4.dsc
 e8160f259001a6563c5a7523aa22e58a90883f9c 164740 systemd_240-4.debian.tar.xz
 

Bug#919031: marked as done (libmono-system4.0-cil: not installable on amd64)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 23:15:49 +
with message-id 
and subject line Bug#919031: fixed in mono 5.16.0.220+dfsg3-2
has caused the Debian Bug report #919031,
regarding libmono-system4.0-cil: not installable on amd64
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.)


-- 
919031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmono-system4.0-cil
Version: 5.16.0.220+dfsg3-1
Severity: important

Dear Maintainer,

libmono-system4.0-cil contains in its dependencies on amd64 a dependency
on mono-runtime-common 5.18:

Depends: ..., mono-runtime (>= 5.16.0.220), mono-runtime-common (>= 
5.18.0.225), mono-runtime (<< 5.16.0.221)

This probably will never work, since mono-runtime depends on the exact
same version of mono-runtime-common. The dependency is not listed in
debian/control, so it seems it must have been introduced by
${misc:Depends} or ${cli:Depends} - was this package built on a system
with mono 5.18 packages installed?


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

Kernel: Linux 4.19.12-echse-4.1920181222 (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: sysvinit (via /sbin/init)

Versions of packages libmono-system4.0-cil depends on:
ii  libc62.28-4
ii  libmono-corlib4.5-cil4.6.2.7+dfsg-2
ii  libmono-security4.0-cil  4.6.2.7+dfsg-2
ii  libmono-system-configuration4.0-cil  4.6.2.7+dfsg-2
ii  libmono-system-xml4.0-cil4.6.2.7+dfsg-2
ii  mono-runtime 4.6.2.7+dfsg-2

Versions of packages libmono-system4.0-cil recommends:
ii  ca-certificates-mono  4.6.2.7+dfsg-2

Versions of packages libmono-system4.0-cil suggests:
ii  libasound2  1.1.7-2
ii  libgamin0   0.1.10-5+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mono
Source-Version: 5.16.0.220+dfsg3-2

We believe that the bug you reported is fixed in the latest version of
mono, 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.
Jo Shields  (supplier of updated mono 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: Sat, 12 Jan 2019 15:01:30 -0500
Source: mono
Binary: mono-runtime-common mono-runtime mono-runtime-sgen mono-runtime-boehm 
mono-runtime-dbg mono-utils ca-certificates-mono mono-complete libmono-2.0-1 
libmono-2.0-dev libmonosgen-2.0-1 libmonosgen-2.0-1-dbg libmonosgen-2.0-dev 
libmonoboehm-2.0-1 libmonoboehm-2.0-1-dbg libmonoboehm-2.0-dev libmono-profiler 
libmono-cil-dev libmono-posix4.0-cil libmono-codecontracts4.0-cil 
libmono-compilerservices-symbolwriter4.0-cil libmono-csharp4.0c-cil 
libmono-http4.0-cil libmono-cecil-private-cil libmono-webbrowser4.0-cil 
libmono-management4.0-cil libmono-messaging4.0-cil 
libmono-messaging-rabbitmq4.0-cil libmono-rabbitmq4.0-cil libmono-simd4.0-cil 
libmono-smdiagnostics0.0-cil libmono-corlib4.5-cil libmono-i18n4.0-all 
libmono-i18n4.0-cil libmono-i18n-cjk4.0-cil libmono-i18n-mideast4.0-cil 
libmono-i18n-other4.0-cil libmono-i18n-rare4.0-cil libmono-i18n-west4.0-cil 
libmono-parallel4.0-cil libmono-system4.0-cil 
libmono-system-componentmodel-composition4.0-cil
 libmono-system-componentmodel-dataannotations4.0-cil 
libmono-system-configuration4.0-cil libmono-system-configuration-install4.0-cil 
libmono-system-core4.0-cil libmono-system-drawing4.0-cil 
libmono-system-dynamic4.0-cil libmono-system-enterpriseservices4.0-cil 
libmono-system-json4.0-cil libmono-system-json-microsoft4.0-cil 
libmono-system-management4.0-cil libmono-system-net4.0-cil 
libmono-system-net-http4.0-cil libmono-system-net-http-formatting4.0-cil 
libmono-system-numerics4.0-cil libmono-system-numerics-vectors4.0-cil 
libmono-system-security4.0-cil libmono-btls-interface4.0-cil 
libmono-system-serviceprocess4.0-cil 

Bug#918751: Investigation results

[Santiago Vila]

severity 827832 minor
retitle 827832 python-shade: Improvement of error message when failing to build 
on small machines (?)
thanks

Sorry, this was my fault.

Here is the reason why it failed for me:

This package (version 1.7.0) used to need 200 MB of RAM to build,
and I was using a small machine (1 GB of RAM) to build it. So far, so
good.

The problem was that the current version (1.30.0) required around 1900 MB
of RAM to build (a lot more than before) while I was still using small
machines to build it.

(You might be wondering why I'm using machines with 1 GB to build
Debian packages: well, around 96.6% of all Debian packages in buster
require 1 GB of RAM or less to build, and machines with 2 GB of RAM
usually cost double the price per-hour).

So no FTBFS problem here. Special thanks to Stewart Ferguson for
actually looking at the build logs.

Now I wonder if the error message in cases like this could be improved
so that it's even more clear that lack of RAM was the problem.
Probably it does not worth the effort, but I leave this to you.

Thanks a lot.

Processed: Re: Investigation results

[Debian Bug Tracking System]

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

> severity 827832 minor
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Severity set to 'minor' from 'serious'
> retitle 827832 python-shade: Improvement of error message when failing to 
> build on small machines (?)
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Changed Bug title to 'python-shade: Improvement of error message when failing 
to build on small machines (?)' from 'python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found'.
> thanks
Stopping processing here.

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

Bug#905443: marked as done (ball: FTBFS - test failures)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 23:00:12 +
with message-id 
and subject line Bug#905443: fixed in ball 1.5.0+git20180813.37fc53c-1
has caused the Debian Bug report #905443,
regarding ball: FTBFS - 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.)


-- 
905443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ball
Version: 1.4.3~beta1-4
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python-ball

Hi,

ball FTBFS on most architectures:
https://buildd.debian.org/status/package.php?p=ball=unstable
keeping uninstallable packages in the archive that depend on the no
longer available sip-api-11.3.


Andreas
--- End Message ---
--- Begin Message ---
Source: ball
Source-Version: 1.5.0+git20180813.37fc53c-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ball package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Jan 2019 20:52:01 +0100
Source: ball
Binary: libball1.5-data libball1.5 libball1.5-dev libballview1.5 
libballview1.5-dev python-ball ballview libball1.5-doc
Architecture: source amd64 all
Version: 1.5.0+git20180813.37fc53c-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 ballview   - free molecular modeling and molecular graphics tool
 libball1.5 - Biochemical Algorithms Library
 libball1.5-data - Biochemical Algorithms Library (data files)
 libball1.5-dev - Header files for the Biochemical Algorithms Library
 libball1.5-doc - documentation for the BALL library
 libballview1.5 - Biochemical Algorithms Library, VIEW framework
 libballview1.5-dev - Header files for the VIEW part of the Biochemical 
Algorithms Libr
 python-ball - Python bindings for the Biochemical Algorithms Library
Closes: 784451 874837 905443 911881
Changes:
 ball (1.5.0+git20180813.37fc53c-1) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI.
   * Trim trailing whitespace.
 .
   [ Andreas Tille ]
   * New upstream version
 Closes: #784451, #905443, #911881
   * Use Git mode in watch file
   * debhelper 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.3.0
   * Switch to Qt5
 Closes: #874837
   * Drop python-ballview package
   * Do not fail in case of build time test failures
   * d/control: Remove X-Python-Version field
   * d/rules: Remove manual CFLAGS settings
   * d/rules: Remove cruft from python-ball package
   * Use wrapper to export BALL_DATA_PATH
Checksums-Sha1:
 6ce0cd0f439586d76d7a8465fb63c8cd5e7ccf56 3028 
ball_1.5.0+git20180813.37fc53c-1.dsc
 696a5708b583fdd96051e4496c3a4d8e188f349d 21325220 
ball_1.5.0+git20180813.37fc53c.orig.tar.xz
 69c09c4e14b715ae09a88f51e0e3af455e4ce6c4 12084 
ball_1.5.0+git20180813.37fc53c-1.debian.tar.xz
 f0b59974317a842ae4dba6fb8856a18de13c89fc 20485 
ball_1.5.0+git20180813.37fc53c-1_amd64.buildinfo
 32aa5ab73150c3247fe3bed7c026fe361f3e15e2 1716860 
ballview-dbgsym_1.5.0+git20180813.37fc53c-1_amd64.deb
 f8dfc6d36dcb95ae93a0c977f34a6b15b59aa2f7 200692 
ballview_1.5.0+git20180813.37fc53c-1_amd64.deb
 bbe056104f3bb251866906f401fd6559f3e61d13 16585916 
libball1.5-data_1.5.0+git20180813.37fc53c-1_all.deb
 90f60139db51c577d21441315c989ff5f983863a 88929996 
libball1.5-dbgsym_1.5.0+git20180813.37fc53c-1_amd64.deb
 48ba5935387c7b08ec71b992f044fa521b771ffa 537220 
libball1.5-dev_1.5.0+git20180813.37fc53c-1_amd64.deb
 06974fd10bbb23f4eab7c206fd09d105b15c344d 8126944 
libball1.5-doc_1.5.0+git20180813.37fc53c-1_all.deb
 80672ba2475d9f8b821c1cdc29b80a4af1c37ffe 3119428 
libball1.5_1.5.0+git20180813.37fc53c-1_amd64.deb
 e6b7530d67c5b52c82ae3785770d633e391d2bbd 38240932 
libballview1.5-dbgsym_1.5.0+git20180813.37fc53c-1_amd64.deb
 e0d99068e7adeea46ed4b79f076673dcb435c0a2 147932 
libballview1.5-dev_1.5.0+git20180813.37fc53c-1_amd64.deb
 

Bug#784451: marked as done ([ball] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 23:00:12 +
with message-id 
and subject line Bug#784451: fixed in ball 1.5.0+git20180813.37fc53c-1
has caused the Debian Bug report #784451,
regarding [ball] Qt4's WebKit removal
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.)


-- 
784451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ball
Version: 1.4.2+20140406-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Med Packaging Team ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: ball
Source-Version: 1.5.0+git20180813.37fc53c-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ball package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Jan 2019 20:52:01 +0100
Source: ball
Binary: libball1.5-data libball1.5 libball1.5-dev libballview1.5 
libballview1.5-dev python-ball ballview libball1.5-doc
Architecture: source amd64 all
Version: 1.5.0+git20180813.37fc53c-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 ballview   - free molecular modeling and molecular graphics tool
 libball1.5 - Biochemical Algorithms Library
 libball1.5-data - Biochemical Algorithms Library (data files)
 libball1.5-dev - Header files for the Biochemical Algorithms Library
 libball1.5-doc - documentation for the BALL library
 libballview1.5 - Biochemical Algorithms Library, VIEW framework
 libballview1.5-dev - Header files for the VIEW part of the Biochemical 
Algorithms Libr
 python-ball - Python bindings for the Biochemical Algorithms Library
Closes: 784451 874837 905443 911881
Changes:
 ball (1.5.0+git20180813.37fc53c-1) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI.
   * Trim trailing whitespace.
 .
   [ Andreas Tille ]
   * New upstream version
 Closes: #784451, #905443, #911881
   * Use Git mode in watch file
   * debhelper 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.3.0
   * Switch to Qt5
 Closes: #874837
   * Drop python-ballview package
   * Do not fail in case of 

Processed: Re: Investigation results

[Debian Bug Tracking System]

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

> owner 918751 sanv...@debian.org
Bug #918751 [src:python-shade] python-shade: FTBFS in sid
Owner changed from Stewart Ferguson  to sanv...@debian.org.
> thanks
Stopping processing here.

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

Bug#918751: Investigation results

[Santiago Vila]

owner 918751 sanv...@debian.org
thanks

I believe this problem is not directly related with the number of CPUs.

Will do some additional tests and will probably downgrade this myself
if I confirm my current suspicious.

Thanks.

Bug#904404: marked as done (liece-dcc: fails to install with emacs25)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 22:06:15 +
with message-id 
and subject line Bug#904404: fixed in liece 2.0+0.20030527cvs-12
has caused the Debian Bug report #904404,
regarding liece-dcc: fails to install with emacs25
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.)


-- 
904404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liece-dcc
Version: 2.0+0.20030527cvs-11.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Setting up emacs25 (25.2+1-6+b3) ...
  update-alternatives: using /usr/bin/emacs25-x to provide /usr/bin/emacs 
(emacs) in auto mode
  update-alternatives: using /usr/bin/emacs25 to provide /usr/bin/editor 
(editor) in auto mode
  Install emacsen-common for emacs25
  emacsen-common: Handling install of emacsen flavor emacs25
  Install liece for emacs25
  install/liece: Handling emacs25, logged in /tmp/elc_Mb8V4E.log
  ERROR: install script from liece package failed
  dpkg: error processing package emacs25 (--configure):
   installed emacs25 package post-installation script subprocess returned error 
exit status 1

The logfile contains:

emacs25 -q -no-site-file --no-site-file -batch -l liece-make.el -f 
autoload-liece
Loading /usr/share/emacs25/site-lisp/liece/liece-config.el (source)...
Cannot open load file: No such file or directory, install


cheers,

Andreas


liece-dcc_2.0+0.20030527cvs-11.2+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: liece
Source-Version: 2.0+0.20030527cvs-12

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated liece 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: Sat, 12 Jan 2019 22:21:21 +0100
Source: liece
Binary: liece liece-dcc
Architecture: source
Version: 2.0+0.20030527cvs-12
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 liece  - IRC (Internet Relay Chat) client for Emacs
 liece-dcc  - DCC program for liece
Closes: 865143 904404
Changes:
 liece (2.0+0.20030527cvs-12) unstable; urgency=medium
 .
   * QA upload.
   * Set Maintainer to Debian QA Group.  (See: #654941)
   * Switch to source format 3.0 (quilt).
   * Switch to unversioned automake.  (Closes: #865143)
   * Switch to Priority: optional.
   * Apply emacsen-install patch from Tatsuya Kinoshita.  (Closes: #904404)
Checksums-Sha1:
 9b028b680fc0587ef7da1208cca95fd40985ba8a 1876 liece_2.0+0.20030527cvs-12.dsc
 4b75f1fe4f0013ed91dd29a8296f581d3118804b 13460 
liece_2.0+0.20030527cvs-12.debian.tar.xz
 e8d7e85db09bccb902144cac249d8d85891138f4 6755 
liece_2.0+0.20030527cvs-12_source.buildinfo
Checksums-Sha256:
 b8efa5bf3aaad7bb42edd2505934324e8781ccafbebd421f9e49ced8bc76a471 1876 
liece_2.0+0.20030527cvs-12.dsc
 0ec39401ff3a84b253738097b36f0a2cf0487ca34b0dd4446168511ec4e59d97 13460 
liece_2.0+0.20030527cvs-12.debian.tar.xz
 c66711218c32519e514c59b3f53d0238de1da6f2837636811002e78ee4d3b384 6755 
liece_2.0+0.20030527cvs-12_source.buildinfo
Files:
 6e41b2e53a15f7898af679c2d57d00c0 1876 net optional 
liece_2.0+0.20030527cvs-12.dsc
 fabef534c826503fc65a8ca20d5fcff4 13460 net optional 
liece_2.0+0.20030527cvs-12.debian.tar.xz
 4d401b577de68b72bb02caf1271e9ba8 6755 net optional 
liece_2.0+0.20030527cvs-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlw6XSsQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCJrrD/4pgMtlvxqVsn7yaA+OriHpUrW96Zc7zn7d
GJ9q/T6Nq9/SkOe/6Yr5hpJRycsgh+bXpe9oRLrRL1btMyPqG4lrWmJUfaZJH3dv
QaqdL414tXMKWtuMHgZ9SwUbZTD0CR8jx4b/ghhkw6lVUUN6GUnSqNXLPmLMlX+o
ZUY2FwWc1GvHayb4C+DAAZlYjmcth9hNHFRpa2tRWo2J/LfvCfZx9Opxy0Os78pS

Bug#918733: marked as done (googletest FTBFS on mips/mipsel: out of memory)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 22:06:08 +
with message-id 
and subject line Bug#918733: fixed in googletest 1.8.1-3
has caused the Debian Bug report #918733,
regarding googletest FTBFS on mips/mipsel: out of memory
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.)


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

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

...
as: out of memory allocating 4072 bytes after a total of 543838208 bytes
/tmp/ccnTRJ3H.s: Assembler messages:
/tmp/ccnTRJ3H.s: Fatal error: can't close 
CMakeFiles/gmock-matchers_test.dir/test/gmock-matchers_test.cc.o: memory 
exhausted
make[3]: *** [googlemock/CMakeFiles/gmock-matchers_test.dir/build.make:66: 
googlemock/CMakeFiles/gmock-matchers_test.dir/test/gmock-matchers_test.cc.o] 
Error 1


Fix:

--- debian/rules.old2019-01-08 12:16:26.188970969 +
+++ debian/rules2019-01-08 12:16:43.685280431 +
@@ -9,11 +9,11 @@
 ifeq ($(DEB_HOST_ARCH),hppa)
 CXXFLAGS += -mlong-calls
 else ifeq ($(DEB_BUILD_ARCH), mips)
-CXXFLAGS += -mxgot
+CXXFLAGS += -mxgot -g1
 else ifeq ($(DEB_BUILD_ARCH), mips64el)
 CXXFLAGS += -mxgot
 else ifeq ($(DEB_BUILD_ARCH), mipsel)
-CXXFLAGS += -mxgot
+CXXFLAGS += -mxgot -g1
 endif
 
 export CXXFLAGS
--- End Message ---
--- Begin Message ---
Source: googletest
Source-Version: 1.8.1-3

We believe that the bug you reported is fixed in the latest version of
googletest, 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.
Steve M. Robbins  (supplier of updated googletest 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: Sat, 12 Jan 2019 15:42:59 -0600
Source: googletest
Binary: googletest googletest-tools libgtest-dev libgmock-dev google-mock
Architecture: source
Version: 1.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Steve M. Robbins 
Changed-By: Steve M. Robbins 
Description:
 google-mock - Google's framework for writing and using C++ mock classes
 googletest - Google's C++ test framework sources
 googletest-tools - Google's C++ test framework sources
 libgmock-dev - Google's framework for writing C++ tests
 libgtest-dev - Google's framework for writing C++ tests
Closes: 918733
Changes:
 googletest (1.8.1-3) unstable; urgency=medium
 .
   [ Steven Robbins ]
   * [ba2ba66] Fix build on mips/mipsel by using flag -g1. Closes: #918733
 (thanks, Adrian Bunk).
Checksums-Sha1:
 0377871a4fce29718d38f2d73a69246341a13279 2159 googletest_1.8.1-3.dsc
 04ce02f920381f1c45407ff5cddef888b07f036e 11036 googletest_1.8.1-3.debian.tar.xz
 038b17bbf4602e7b5f669bf9f9a99cb794b369d7 7145 
googletest_1.8.1-3_source.buildinfo
Checksums-Sha256:
 7ccce8fd0b4263c83998fa190a5ddba4c193a22581c886743c6836ee11044917 2159 
googletest_1.8.1-3.dsc
 960e7dd2cdbaa108707b93fc5b5681a4b123682dda05af103018761cba4e6280 11036 
googletest_1.8.1-3.debian.tar.xz
 ada2f67be721ae54cde581ce1c4b7df13d4f5f8fd44ecdfa324c1e58a3f8c67f 7145 
googletest_1.8.1-3_source.buildinfo
Files:
 0c483ecbb3ad21a9abfa105967247b2a 2159 devel optional googletest_1.8.1-3.dsc
 5d2ce80a58a9ee57bb275ac930e39287 11036 devel optional 
googletest_1.8.1-3.debian.tar.xz
 97d468cf04095fb7acf201d10db3d2ac 7145 devel optional 
googletest_1.8.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEy89k8fa3rclNjyokyeVeL63I9LkFAlw6X7AACgkQyeVeL63I
9LlHPxAAha5sc/chcSz4QIR+jg0x5kjXFREv0Su8RSruPcRqa/5/DMfIkMznkdbc
BdThJcvFUeioz3ptxvkHofCRkMQPiliEDL4FSoWqZ1Rkc3FnL6FXM275oZULQNL5
vD8XjNh1shjENoe6UOkJ8MATXi6o68jNjc0J5cYpcwmGF6wgEN5VlH/qFy5FHWoQ
TificJ/SQVV7zewswtYk2C3hwa7co1kd3Qf1pvjE0cR5Okn+O3sOanaS29p+lu6z
q2GiXKNcjphmW4spYjKH3tt5F4GQyzyWAYWkwribbRVkUrFnvzPX+FMBusxH/swO
yzftNsR6kluVSiwEX/PI+wB+hIbna/SCRUoP4ru+BP4rhCQR0D54HDcIt1x87hQ1
SE+EECahqt6ztZZnOTpAdvJtkVlKvAXdwgrF9E68rkEceHp+86Bfxy/f1yPW6zWQ
HsdcX1/KjD4xRePmxQBidblmJomLnZ6CY6hSgNn1YTrMhQs145hLlQk+z3yold4H
zeqpDsz3UkZBVVUa+JYqqo66T0QPgN0WTdnlpqhTuQBoBAZFrWD6Dj1hfpOOOZA2

Bug#912969: marked as done (gecode: FTBFS on mips and mipsel)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 22:05:59 +
with message-id 
and subject line Bug#912969: fixed in gecode 6.1.0-2
has caused the Debian Bug report #912969,
regarding gecode: FTBFS on mips and mipsel
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.)


-- 
912969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gecode
Version: 6.1.0-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/Gecode/gecode/issues/34

Building Gecode 6.1.0-1 fails on mips and mipsel.  The previous
version (6.0.1-1) had no trouble.  GCC versions have changed between
the build attempts and that may be a factor.  The error occurs in the
test suite that's run after the build itself at the same place for
both arches.

https://buildd.debian.org/status/fetch.php?pkg=gecode=mips=6.1.0-1=1540903224=0
https://buildd.debian.org/status/fetch.php?pkg=gecode=mipsel=6.1.0-1=1540907457=0

I've reported this to the upstream but it's likely that this needs to
be figured out on Debian's end.
--- End Message ---
--- Begin Message ---
Source: gecode
Source-Version: 6.1.0-2

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

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

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

Debian distribution maintenance software
pp.
Kari Pahula  (supplier of updated gecode 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: Sat, 12 Jan 2019 22:58:51 +0200
Source: gecode
Binary: libgecode-dev libgecode-doc libgecode48 libgecodegist48 
libgecodeflatzinc48 flatzinc
Architecture: source amd64 all
Version: 6.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Kari Pahula 
Changed-By: Kari Pahula 
Description:
 flatzinc   - constraint problem modelling language
 libgecode-dev - generic constraint development environment
 libgecode-doc - generic constraint development environment
 libgecode48 - generic constraint development environment
 libgecodeflatzinc48 - Gecode support for FlatZinc modelling language
 libgecodegist48 - Gecode Interactive Search Tool library
Closes: 912969
Changes:
 gecode (6.1.0-2) unstable; urgency=medium
 .
   * Backport upstream patch to skip failing tests. (Closes: #912969)
Checksums-Sha1:
 38651527bcbdaef5905d3e06bb1704b0b4953f3d 2156 gecode_6.1.0-2.dsc
 3cae9aa634c0f76989046636af64e0343b1bb910 15760 gecode_6.1.0-2.debian.tar.xz
 221503cb4a2547454d9e7e5a1c25a1836391cf85 119704 
flatzinc-dbgsym_6.1.0-2_amd64.deb
 12d4379a768e7fc2f2ee47196ab7cfeee2196f22 66996 flatzinc_6.1.0-2_amd64.deb
 6066a281d2248635dbf4b4707c004af346ceaa27 14714 gecode_6.1.0-2_amd64.buildinfo
 219f6be26a6d403e90731fdfdf82194360d7a44a 507676 libgecode-dev_6.1.0-2_amd64.deb
 2a720899a4f7f7d2738ab24e856d4c42b00ff88f 10859124 libgecode-doc_6.1.0-2_all.deb
 722dd24cb915c7c8241e406316e1cc7cbe35c966 59237056 
libgecode48-dbgsym_6.1.0-2_amd64.deb
 edade56697bdf79e1e4f27812d48ac62272512ce 2693500 libgecode48_6.1.0-2_amd64.deb
 b913e0a672bb6bf6e69769a99f6b7f2e23ec3319 2677764 
libgecodeflatzinc48-dbgsym_6.1.0-2_amd64.deb
 214475a0161facceb691ff09a475c5623f6f1460 251760 
libgecodeflatzinc48_6.1.0-2_amd64.deb
 f16d8d1f477f5b3f44a96b10a697483e47dc3435 3546156 
libgecodegist48-dbgsym_6.1.0-2_amd64.deb
 c169f5865f899c38419bfe8ec376dc6a57a68a47 172936 
libgecodegist48_6.1.0-2_amd64.deb
Checksums-Sha256:
 8a77ed62c39138ab04c79e2cd30087d1245470f63ad8d13a3e2c0883e878e4a0 2156 
gecode_6.1.0-2.dsc
 68aa72bba76b2a8368cbb15eddfc0563139c66c53fe6690adf8355e7915b0477 15760 
gecode_6.1.0-2.debian.tar.xz
 8452d95abbaae7cbcec38dc3dc1388aa4ff9ded87ad726ca5138b7d26c4b8f69 119704 
flatzinc-dbgsym_6.1.0-2_amd64.deb
 af61d33f0e3247d0fb5108fc0281e17e6e68b13cbfe2fa055d46a04b0f47d700 66996 
flatzinc_6.1.0-2_amd64.deb
 8ecc42e4adcc9264d41a9bb268fc50c6cbfdf7528138d4d271d73e7de8a53aa6 14714 
gecode_6.1.0-2_amd64.buildinfo
 90764fc3f843c8db07da88a514ba6bed7a9769e332406d5ea1d43c09fc4d7916 507676 
libgecode-dev_6.1.0-2_amd64.deb
 a71057d3f6fbc2a77c1f751d49f44944c6c1cae66d7eb03c6d7594cad097c442 10859124 
libgecode-doc_6.1.0-2_all.deb
 436de4df8b7602341025809570a978b5d2b71d2b3f598cb5121f773af6712913 

Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream

[Yavor Doganov]

On Wed, 09 Jan 2019 07:24:00 +0200,
Jeremy Bicha wrote:
> We'd like to remove those libraries soon, but I am willing to wait a
> bit longer for someone to port linsmith to gtk3.

JFTR, I don't intend to work on this package.  I don't have time at
the moment, but more importantly I don't have the motivation, knowing
in advance that this is already fixed upstream.

(I spent good few days working on rasmol, glaring at those molecules
and fighting with ancient code, and the reward was that my work ended
up in the trashcan only because the maintainer didn't bother to write
one or two lines informing people that the issue is fixed upstream.  I
knew my patch was suboptimal but it still leaves a bitter taste in my
mouth -- I could have spent these days working on something else.)

Bug#741464: grub-pc-bin: hangs after displaying boot menu

[Jeroen Dekkers]

Control: tag -1 +patch

On Mon, 29 Oct 2018 00:36:00 +0100,
Colin Watson wrote:
> 
> On Sun, Feb 01, 2015 at 11:16:59PM +0100, Marco Gamberoni wrote:
> > I see this same at_keyboard behaviour: working in VirtualBox, delivering 
> > garbage on this real hardware:
> >  - an HP Proliant DL380 Gen5 machine
> >  - with a Compaq PS/2 keyboard italian layout attached
> >  - booted from an iso image made with grub-mkrescue (GRUB) 2.02~beta2-15, 
> > containing a keyboard layout file made with
> >   ckbcomp -model pc105 -layout it | grub-mklayout -o pc105-it.gkb
> [...]
> > Having read
> > 
> > http://web.archive.org/web/20040604041507/http://panda.cs.ndsu.nodak.edu/~achapwes/PICmicro/keyboard/atkeyboard.html
> > it is obvious what's going on: at_keyboard is using scankey set 1 but the 
> > keyboard is using set 2 and the keyboard controller is not translating.
> 
> Sorry for the long delay.  Are you still in a position to test this?
> 
> I just ran across this upstream commit:
> 
>   
> https://git.savannah.gnu.org/cgit/grub.git/commit/?id=c4b8bec5fee4e30a165fd14a188cf3ab8eccd095
> 
> Ignoring the specific hardware mentioned here, it seems like this could
> be a plausible cause: if GRUB manages to get out of sync with the
> keyboard controller on the command/data sequence, then it could easily
> end up confused about which is the current scan code set (see the
> changes to query_mode in particular) and so end up using the wrong set,
> or possibly even send a nonsense command somehow.  It seems worth
> testing if you can.

I cherry-picked that commit and tested it but it didn't fix the
problem.

The bug was introduced somewhere between GRUB 2.00 and 2.02 so I used
git bisect to find the commit that introduced the bug:

https://git.savannah.gnu.org/cgit/grub.git/commit/?id=0c62a5b28e2783d84d266341c4388b494e058114

As far as I understand the change it will no longer poll forever in
the module init when the keyboard controller isn't ready. The problem
seems to be that we used to initialize the keyboard controller in the
module init but now we always do it later when getkey is
called. Somehow this messes up things but I have no idea why.

I changed it so that it only initializes the keyboard controller when
it is ready and doesn't poll when it isn't. Here is the merge request:

https://salsa.debian.org/grub-team/grub/merge_requests/6

I've tested this on my old laptop (X200s thinkpad) and the problem
goes away with this patch.

Kind regards,

Jeroen Dekkers

Processed: Re: Bug#741464: grub-pc-bin: hangs after displaying boot menu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +patch
Bug #741464 [grub-pc-bin] grub-pc-bin: freezes after "terminal_input 
at_keyboard"
Added tag(s) patch.

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

Bug#918439: cockpit: FTBFS (failing tests)

[Santiago Vila]

On Sat, Jan 12, 2019 at 09:41:49PM +0100, Andreas Henriksson wrote:

> It might be a good idea to first just test if all problems vanishes
> if builting in a less network restricted environment, [...]

I guess not, because I'm using plain sbuild on a stretch machine,
which AFAIK does not have (by default) network restrictions.

For completeness, I've put a bunch of my build logs here:

https://people.debian.org/~sanvila/build-logs/cockpit/

Also, this started to happen quite recently. This is my build history
for buster:

Status: successful  cockpit_183-1_amd64-20181201T044648Z
Status: successful  cockpit_183-1_amd64-20181210T093126.625Z
Status: successful  cockpit_184-1_amd64-20181216T140526.278Z
Status: successful  cockpit_184-1_amd64-20181226T121643.534Z
Status: failed  cockpit_184-1_amd64-20190105T051830.660Z
Status: failed  cockpit_184-1_amd64-20190112T210843.011Z
Status: failed  cockpit_184-1_amd64-20190112T210843.654Z
Status: failed  cockpit_184-1_amd64-20190112T210842.534Z
Status: failed  cockpit_184-1_amd64-20190112T210841.999Z

Note: I believe this FTBFS problem is "general", but if for whatever
reason you can't reproduce it, please contact me privately, I could
offer ssh access to a machine where this happens all the time.

Thanks.

Processed: gnome-phone-manager: diff for NMU version 0.69-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 899530 + patch
Bug #899530 [src:gnome-phone-manager] gnome-phone-manager: Invalid maintainer 
address pkg-bluetooth-maintain...@lists.alioth.debian.org
Added tag(s) patch.
> tags 899530 + pending
Bug #899530 [src:gnome-phone-manager] gnome-phone-manager: Invalid maintainer 
address pkg-bluetooth-maintain...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#899530: gnome-phone-manager: diff for NMU version 0.69-2.1

[Adrian Bunk]

Control: tags 899530 + patch
Control: tags 899530 + pending

Dear maintainer,

I've prepared an NMU for gnome-phone-manager (versioned as 0.69-2.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru gnome-phone-manager-0.69/debian/changelog gnome-phone-manager-0.69/debian/changelog
--- gnome-phone-manager-0.69/debian/changelog	2014-07-17 04:33:45.0 +0300
+++ gnome-phone-manager-0.69/debian/changelog	2019-01-12 23:05:31.0 +0200
@@ -1,3 +1,10 @@
+gnome-phone-manager (0.69-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Maintainer: to the new address. (Closes: #899530)
+
+ -- Adrian Bunk   Sat, 12 Jan 2019 23:05:31 +0200
+
 gnome-phone-manager (0.69-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru gnome-phone-manager-0.69/debian/control gnome-phone-manager-0.69/debian/control
--- gnome-phone-manager-0.69/debian/control	2014-07-17 03:35:14.0 +0300
+++ gnome-phone-manager-0.69/debian/control	2019-01-12 23:05:31.0 +0200
@@ -1,7 +1,7 @@
 Source: gnome-phone-manager
 Section: gnome
 Priority: extra
-Maintainer: Debian Bluetooth Maintainers 
+Maintainer: Debian Bluetooth Maintainers 
 Uploaders: Francesco Namuri , Geert Stappers , Filippo Giunchedi 
 Build-Depends: cdbs,
  debhelper (>= 5), 

Bug#918119: marked as done (bugwarrior: Python 3.7: configparser: TypeError: option values must be strings)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 21:19:30 +
with message-id 
and subject line Bug#918119: fixed in bugwarrior 1.6.0-1
has caused the Debian Bug report #918119,
regarding bugwarrior: Python 3.7: configparser: TypeError: option values must 
be strings
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.)


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

As reported [1] upstream, the bug makes bugwarrior crash at the very beginning
with an error in 'configparser' used to parse the application configuration
file because of empty values. See also trace below.

A patch is already available [2] and included in version 1.6.0 released last
August.

~~

1. https://github.com/ralphbean/bugwarrior/issues/597
2. 
https://github.com/ralphbean/bugwarrior/pull/600/commits/da9221ea673b32fe3f9732b13c818604cf657230

-- Trace:
Traceback (most recent call last):
  File "/usr/bin/bugwarrior-pull", line 11, in 
load_entry_point('bugwarrior==1.5.1', 'console_scripts', 
'bugwarrior-pull')()
  File "/usr/lib/python3/dist-packages/click/core.py", line 759, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 714, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 951, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 552, in invoke
return callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/bugwarrior/command.py", line 62, in pull
config = _try_load_config(main_section, interactive)
  File "/usr/lib/python3/dist-packages/bugwarrior/command.py", line 35, in 
_try_load_config
return load_config(main_section, interactive)
  File "/usr/lib/python3/dist-packages/bugwarrior/config.py", line 207, in 
load_config
config = BugwarriorConfigParser({'log.level': "INFO", 'log.file': None})
  File "/usr/lib/python3.7/configparser.py", line 638, in __init__
self._read_defaults(defaults)
  File "/usr/lib/python3.7/configparser.py", line 1216, in _read_defaults
self.read_dict({self.default_section: defaults})
  File "/usr/lib/python3.7/configparser.py", line 753, in read_dict
self.set(section, key, value)
  File "/usr/lib/python3.7/configparser.py", line 1197, in set
self._validate_value_types(option=option, value=value)
  File "/usr/lib/python3.7/configparser.py", line 1182, in _validate_value_types
raise TypeError("option values must be strings")
TypeError: option values must be string

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

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

Versions of packages bugwarrior depends on:
ii  libjs-sphinxdoc1.7.9-1
ii  python33.7.1-3
ii  python3-click  6.7+git20180829-1
ii  python3-dateutil   2.7.3-1
ii  python3-dogpile.cache  0.6.2-6
ii  python3-future 0.15.2-5
ii  python3-jinja2 2.10-1
ii  python3-lockfile   1:0.12.2-2
ii  python3-requests   2.20.0-2
ii  python3-six1.12.0-1
ii  python3-taskw  1.2.0-2
ii  python3-tz 2018.7-1

Versions of packages bugwarrior recommends:
ii  python3-keyring  17.1.1-1
ii  python3-phabricator  0.7.0-1

bugwarrior suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: bugwarrior
Source-Version: 1.6.0-1

We believe that the bug you reported is fixed in the latest version of
bugwarrior, 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.
Jochen Sprickerhof  (supplier of updated bugwarrior 
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 

Processed: Fwd: Claiming bug 827832

[Debian Bug Tracking System]

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

> owner 827832 !
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Owner recorded as Stewart Ferguson .
>
End of message, stopping processing here.

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

Processed: Move to the package where it was fixed

[Debian Bug Tracking System]

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

> reassign 916710 src:glew
Bug #916710 {Done: Alastair McKinstry } [src:info-beamer] 
info-beamer FTBFS with glew 2.1.0
Bug reassigned from package 'src:info-beamer' to 'src:glew'.
No longer marked as found in versions info-beamer/1.0~pre3+dfsg-0.1.
No longer marked as fixed in versions glew/2.1.0-4.
> forcemerge 915112 916710
Bug #915112 {Done: Alastair McKinstry } [src:glew] glew: 
incompatible with glext.h from current mesa
Bug #915112 {Done: Alastair McKinstry } [src:glew] glew: 
incompatible with glext.h from current mesa
Added tag(s) ftbfs, buster, and sid.
Bug #916710 {Done: Alastair McKinstry } [src:glew] 
info-beamer FTBFS with glew 2.1.0
915481 was blocked by: 915112 918123
915481 was not blocking any bugs.
Added blocking bug(s) of 915481: 916710
Added indication that 916710 affects src:pymol
Marked as fixed in versions glew/2.1.0-4.
Marked as found in versions glew/2.1.0-3 and glew/2.1.0-2.
Added tag(s) patch.
Merged 915112 916710
> affects 915112 src:info-beamer
Bug #915112 {Done: Alastair McKinstry } [src:glew] glew: 
incompatible with glext.h from current mesa
Bug #916710 {Done: Alastair McKinstry } [src:glew] 
info-beamer FTBFS with glew 2.1.0
Added indication that 915112 affects src:info-beamer
Added indication that 916710 affects src:info-beamer
> thanks
Stopping processing here.

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

Bug#918841: Bug #918841 in systemd marked as pending

[Michael Biebl]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/systemd-team/systemd/commit/ce0e48e43979e955df2413dca23c64088a729ed8


Import patches from v240-stable branch (up to f02b5472c6)

- Fixes a problem in logind closing the controlling terminal when using
  startx. (Closes: #918927)
- Fixes various journald vulnerabilities via attacker controlled alloca.
  (CVE-2018-16864, CVE-2018-16865, Closes: #918841, Closes: #918848)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918841

Bug#918848: Bug #918848 in systemd marked as pending

[Michael Biebl]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/systemd-team/systemd/commit/ce0e48e43979e955df2413dca23c64088a729ed8


Import patches from v240-stable branch (up to f02b5472c6)

- Fixes a problem in logind closing the controlling terminal when using
  startx. (Closes: #918927)
- Fixes various journald vulnerabilities via attacker controlled alloca.
  (CVE-2018-16864, CVE-2018-16865, Closes: #918841, Closes: #918848)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918848

Processed: Bug #917607 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917607 [udev] udev 240 Makes System Unbootable; rootfs Not Found
Bug #918096 [udev] linux-image-4.19.0-1-amd64: disk and keyboard do not work - 
unusable even in recovery mode
Bug #918322 [udev] 4.19.0-1-amd64 kernel fails to boot with "Gave up waiting 
for root file system device"
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Bug #918848 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918848 [src:systemd] systemd: CVE-2018-16865
Added tag(s) pending.

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

Bug#917607: Bug #917607 in systemd marked as pending

[Michael Biebl]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/systemd-team/systemd/commit/647f8894a374e5994eb8bab93d981e4c44bd7857


sd-device-monitor: Fix ordering of setting buffer size

Fixes an issue with uevents not being processed properly during coldplug
stage and some kernel modules not being loaded via "udevadm trigger".

Closes: #917607


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917607

Processed: Bug #918841 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918841 [src:systemd] systemd: CVE-2018-16864
Bug #919002 [src:systemd] CVE's for systemd vulnerabilities CVE-2018-16864, 
CVE-2018-16865 and CVE-2018-16866
Added tag(s) pending.
Added tag(s) pending.

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

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

[Jonas Smedegaard]

Quoting Ivo De Decker (2019-01-12 17:18:02)
> On Wed, Aug 23, 2017 at 11:41:28PM +0530, Pirate Praveen wrote:
> > On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote:
> > > Package: node-lodash-packages
> > > Severity: serious
> > > Justification: Policy 2.1
> > 
> > I do not think the root issue is serious, but only important.
> > 
> > > The source package node-lodash-packages does not contain the 
> > > source form preferred for editing by upstream.  Instead, upstream 
> > > documents how the contents of that code is generated from the 
> > > sources included in Debian in the source package node-lodash.
> > 
> > Adding a build dependency on node-lodash would be enough for the 
> > policy requirement.
> 
> No it wouldn't. You need to actually generate the code instead of 
> shipping the pregenerated code from upstream. Not doing that is a 
> serious bug. If you think this is easy to fix, please do so. If not, 
> this package should be removed from testing.

Relevant part of Debian Policy §2.1:

  The program must include source code

Build-depending on another package while using prebuilt code is 
argually permitted (but then discourage in other sections, with less 
strong words than "must"), but only if ensuring that in fact the 
distributed code was once built from this exact version of code in the 
build-depended on package.

I find it disgusting that you try find loopholes in policy, Praveen, 
instead of following the spirit of Debian Policy which is to distribute 
source, and build only from that distributed source (avoid distributing 
pre-built/pre-miified/pre-whatever code).

Please fix this properly!


 - Jonas

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

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


signature.asc
Description: signature

Bug#907015: [Pkg-openssl-devel] Bug#907015: marked as done (openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed)

[Sebastian Andrzej Siewior]

On 2019-01-12 15:51:03 [+], Debian Bug Tracking System wrote:
> Paul just told me this should be ok now, so closing.

Okay. We have one additional breaks in git. If anyone needs more, I
don't mind adding them later if it helps…

> Ivo

Sebastian

Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

[Adrian Bunk]

Control: reassign -1 src:pyside2
Control: retitle -1 pyside2 should build without patchelf also on mips+mipsel
Control: affects -1 src:pivy

On Sun, Dec 23, 2018 at 11:47:26PM +, peter green wrote:
> Package: pivy
> Version: 0.6.4-1
> Severity: serious
> 
> pivy cannot be built on mips/mipsel because of a depedency on pyside2 which 
> is not built on mips/mipsel pyside2 is not being built on those architectures 
> due to a dependency on patchelf. patchelf is not currently building on mips* 
> due to a testsuite failure.
> 
> mips64el also looks like it will become a problem going forward as patchelf 
> is not currently available there (but was at the time pyside2 was last built).
> 
> Possible solutions (in roughly descending order of preference):
> 
> 1. Fix the patchelf testsuite failures.
> 2. Break the dependency chain (only possible if the functionality in question 
> is optional, I have not researched that).
>...

pyside2 is now built without patchelf on mips64el.

Doing the same for mips and mipsel should fix the problem for pivy.

cu
Adrian

-- 

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

Bug#915290: marked as done (strace FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 20:52:26 +
with message-id 
and subject line Bug#915290: fixed in strace 4.26-0.1
has caused the Debian Bug report #915290,
regarding strace FTBFS with glibc 2.28
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.)


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

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

...
In file included from /usr/include/x86_64-linux-gnu/sys/stat.h:446,
 from ../../tests/xstatx.c:68,
 from ../../tests/statx.c:64:
/usr/include/x86_64-linux-gnu/bits/statx.h:25:8: error: redefinition of 'struct 
statx_timestamp'
 struct statx_timestamp
^~~
In file included from ../../tests/statx.c:33:
/usr/include/linux/stat.h:56:8: note: originally defined here
 struct statx_timestamp {
^~~
--- End Message ---
--- Begin Message ---
Source: strace
Source-Version: 4.26-0.1

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

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

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated strace package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 20:32:27 +0100
Source: strace
Binary: strace strace64 strace-udeb
Architecture: source
Version: 4.26-0.1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Andreas Henriksson 
Description:
 strace - System call tracer
 strace-udeb - System call tracer (udeb)
 strace64   - System call tracer for 64bit binaries
Closes: 915290
Changes:
 strace (4.26-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload, with maintainer permission.
 .
   [ Ondřej Nový ]
   * d/control: Removing redundant Priority field in binary package
   * d/watch: Use https protocol
 .
   [ Andreas Henriksson ]
   * debian/watch: update for new official release site
   * New upstream version 4.26 (Closes: #915290)
Checksums-Sha1:
 5384c70c251c548837905161e3655a3f143db0dc 2411 strace_4.26-0.1.dsc
 b4a054adb74563fc121bcd19b158f58955a20a33 1444216 strace_4.26.orig.tar.xz
 1d0382ce3a5df252ce2a66f80e5c02c41dc299e8 801 strace_4.26.orig.tar.xz.asc
 df79803f3e2a37624bb8d75a15117a7afbf8a775 19380 strace_4.26-0.1.debian.tar.xz
 fc1bbb48ce891edd303dc72485f5ceb445264958 7000 strace_4.26-0.1_amd64.buildinfo
Checksums-Sha256:
 0f712eb11826219c2b3c8d6ff4a5b40249902afab2544af7231bb7a7e20ea5cc 2411 
strace_4.26-0.1.dsc
 7c4d2ffeef4f7d1cdc71062ca78d1130eb52f947c2fca82f59f6a1183bfa1e1c 1444216 
strace_4.26.orig.tar.xz
 510bd54bef4cee57677e9cc72ee8210d9694d5b984dbad65f074befb3d286bcf 801 
strace_4.26.orig.tar.xz.asc
 e51402ec7254e63f7a6726676b0be05dc8d8319958bf5a73e9e9ddefbbd2fc51 19380 
strace_4.26-0.1.debian.tar.xz
 ea7ea45c36f7f941619bab28ab1d630980af4621d3b39d730f68427b9ed6a83c 7000 
strace_4.26-0.1_amd64.buildinfo
Files:
 94d98605441dd05f75ff1b9cac04ed99 2411 utils optional strace_4.26-0.1.dsc
 daa51acc0c7c696221ec03cf0b30a7af 1444216 utils optional strace_4.26.orig.tar.xz
 09a00725189b7c9f42798dbb1d0927c6 801 utils optional strace_4.26.orig.tar.xz.asc
 f6401932b05b987b7b18d68db5c0b3fb 19380 utils optional 
strace_4.26-0.1.debian.tar.xz
 0f34a74ddd1b7a6c8c08fc89e433f022 7000 utils optional 
strace_4.26-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlw6RLERHGFuZHJlYXNA
ZmF0YWwuc2UACgkQC8R9xk0TUwbjLg//ZE6eDorc7gg0R6+Q8DB4deC4pHtSz70F
4sPigdJ32H9pUOpFzChDP1fb6UdVvxZ4aX0QcKxHohoAHopbBCYtcYWBp/Dc+cj8
Rg5A4E56/obGm8OWrZwTrCCq35fMUx47iVAXZL9j/LpbatyEGy/DJQCgBZd/Jn5w
e/n5uBa2iYLjVmqGMmCsHDXSt1OEQ2XYUmrJSvPnelWIUdnhbM+MTLBs+Ur/A6HA
qXGUqKyT3B2PRIAQq6ysZ3uldDEoFbqRkIbYi8b6T0xsgB4+snNmD8Gt3orIUedE
gq6r6ThlMrvLMzZi2R/c7GJS37aXXvqHRc0rW8Jr4bp9StEFE743c8Z8AJeC6UpN
pBhJWbdHY1tLlxC/FdCHjV5rsc5UHOumkSGW7qVsfExE3jaA7tRI6OTdmVrtmtCs
096Owm0nYe9NnmmISaRtQGqhELgBTiSQkfh7D9kvB0fAqCNJ8CHhV4mPmV9nnCp3

Bug#918779: marked as done (r10k: uninitialized constant Cri::Error)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 20:50:54 +
with message-id 
and subject line Bug#918779: fixed in r10k 3.1.0-1
has caused the Debian Bug report #918779,
regarding r10k: uninitialized constant Cri::Error
to be marked as done.

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

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


-- 
918779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r10k
Version: 2.6.3-1
Severity: important

Dear Maintainer,

When running r10k I get the following error today;
Traceback (most recent call last):
    11: from /usr/bin/r10k:3:in `'
    10: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 9: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 8: from /usr/lib/ruby/vendor_ruby/r10k/cli.rb:3:in `'
 7: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 6: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 5: from /usr/lib/ruby/vendor_ruby/r10k/cli/ext/logging.rb:1:in `'
 4: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 3: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 2: from /usr/lib/ruby/vendor_ruby/cri/command_dsl.rb:3:in `'
 1: from /usr/lib/ruby/vendor_ruby/cri/command_dsl.rb:6:in 
`'
/usr/lib/ruby/vendor_ruby/cri/command_dsl.rb:9:in `': 
uninitialized constant Cri::Error (NameError)
Did you mean?  IOError
   Errno

This is because the package ruby-cri was upgraded on this system today (from 
2.10.1-1 to 2.15.2-1).

Upstream this error/behavior is already reported 
(https://github.com/puppetlabs/r10k/issues/853) and fixed 
(https://github.com/puppetlabs/r10k/pull/854).
Please upgrade the r10k package to a newer version with this fix included, or
change the require in lib/r10k/cli/ext/logging.rb to require 'cri' (as
described in 
https://github.com/puppetlabs/r10k/issues/853#issuecomment-424608028)

I've tested changing the require to 'cri' myself, and this works.

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

Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages r10k depends on:
ii  ruby    1:2.5.1
ii  ruby-colored    1.2-2
ii  ruby-cri    2.15.2-1
ii  ruby-gettext-setup  0.30-2
ii  ruby-log4r  1.1.10-4
ii  ruby-minitar    0.6.1-1
ii  ruby-multi-json 1.12.1-1
ii  ruby-puppet-forge   2.2.9-2
ii  ruby-rugged 0.27.4+ds-1

Versions of packages r10k recommends:
ii  git  1:2.20.1-1

r10k suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: r10k
Source-Version: 3.1.0-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 21:18:54 +0100
Source: r10k
Binary: r10k
Architecture: source
Version: 3.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Sebastien Badia 
Description:
 r10k   - Puppet environment and module deployment
Closes: 918779
Changes:
 r10k (3.1.0-1) unstable; urgency=medium
 .
   * New upstream version 3.1.0 (fix cri dependency Closes: #918779)
   * d/watch: Bump watchfile to version 4
   * d/control: Bump to Standards-Version 4.3.0 (no changes needed)
   * d/copyright: Update copyright years
Checksums-Sha1:
 296cb873d66d6daafe8529e62df03cbac91a 2267 r10k_3.1.0-1.dsc
 bf0223df2d720c0c4406f33b74921d3467fc93e8 199755 r10k_3.1.0.orig.tar.gz
 56fa62330a883cbf0b7488e8da9d2bd7d6da8d9d 

Processed: Re: Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:pyside2
Bug #917199 [pivy] pivy, unbuildable on mips* due to testsuite failures in 
patchelf.
Bug reassigned from package 'pivy' to 'src:pyside2'.
No longer marked as found in versions 0.6.4-1.
Ignoring request to alter fixed versions of bug #917199 to the same values 
previously set
> retitle -1 pyside2 should build without patchelf also on mips+mipsel
Bug #917199 [src:pyside2] pivy, unbuildable on mips* due to testsuite failures 
in patchelf.
Changed Bug title to 'pyside2 should build without patchelf also on 
mips+mipsel' from 'pivy, unbuildable on mips* due to testsuite failures in 
patchelf.'.
> affects -1 src:pivy
Bug #917199 [src:pyside2] pyside2 should build without patchelf also on 
mips+mipsel
Added indication that 917199 affects src:pivy

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

Bug#907277: autoconf: AC_SEARCH_LIBS with AC_LANG([C++]) broken when using gcc 8

[Chaim Zax]

Hi, autoconf developers, Debian gcc maintainers,

In Debian there is a bug [1] reported on the autoconf package which
relates to a change in gcc 8. After looking into the issue it's not
completely clear to me what the best solution should be.

The autoconf function AC_SEARCH_LIBS check the availability of a
specific library by generating and compiling a small c++ program. From
gcc version 8 on this seems to fail for some libraries (e.g. atomic),
but not all (we haven't seen major fallout so far).

To reproduce this issue the following configure.ac script can be used:

$ cat configure.ac
AC_INIT
AC_PROG_CXX
AC_LANG([C++])
AC_SEARCH_LIBS([__atomic_load_8],[atomic])

$ autoconf


When configured (build) with g++ 7 the result is correct, as expected:

$ CXX=g++-7 ./configure
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++-7 accepts -g... yes
checking for library containing __atomic_load_8... -latomic


But when configured (build) with g++ 8 the atomic library is not found:

$ CXX=g++-8 ./configure
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++-8 accepts -g... yes
checking for library containing __atomic_load_8... no


The c++ file generated is:

/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
/* end confdefs.h.  */

/* Override any GCC internal prototype to avoid an error.
   Use char because int might match the return type of a GCC
   builtin and then its argument prototype would still apply.  */
#ifdef __cplusplus
extern "C"
#endif
char __atomic_load_8 ();
int
main ()
{
return __atomic_load_8 ();
  ;
  return 0;
}


When compiled with g++ 7 it only gives a warning, the function arguments
of '__atomic_load_8' are missing:

$ g++-7 -o conftest -g -O2   test.cpp -latomic
test.cpp:16:6: warning: new declaration ‘char __atomic_load_8()’
ambiguates built-in declaration ‘long unsigned int __atomic_load_8(const
volatile void*, int)’ [-Wbuiltin-declaration-mismatch]
 char __atomic_load_8 ();
  ^~~


When compiled with g++ 8 it fails with an compilation error, the missing
arguments are now resulting in an error:

$ g++-8 -o conftest -g -O2   test.cpp -latomic
test.cpp:16:6: error: new declaration ‘char __atomic_load_8()’
ambiguates built-in declaration ‘long unsigned int __atomic_load_8(const
volatile void*, int)’ [-fpermissive]
 char __atomic_load_8 ();
  ^~~
test.cpp: In function ‘int main()’:
test.cpp:20:25: error: too few arguments to function ‘long unsigned int
__atomic_load_8(const volatile void*, int)’
 return __atomic_load_8 ();


This error is interpreted by autoconf, which concludes the library is
not available. When the generated c++ file is changed to use a different
function from different library (e.g. the 'exp' function from 'libm')
the file [2] does compile with c++ 8.

$ g++-8 -o conftest -g -O2   exp.cpp -latomic
exp.cpp:16:6: warning: declaration of ‘char exp()’ conflicts with
built-in declaration ‘double exp(double)’ [-Wbuiltin-declaration-mismatch]
 char exp();
  ^~~


To know the impact of this bug on other Debian packages it's important
to know when g++ will produce an error, and when only a warning. We
suspect only the libraries provided by gcc itself seem to produce this
error (although we haven't investigated that further), otherwise it
would be likely lots of other Debian packages would produce this error
as well. Perhaps someone knows exactly when g++ triggers this error, and
possibly on which libraries? When updating autoconf it might be
interesting to know if there is a compilation flag to change this error
to a warning.

To fix this issue it's most likely autoconf itself that needs to be
updated as well. If this check only fails on libraries provided with g++
the usage of the AC_SEARCH_LIBS function is probably not needed at all
to check the availability on these libraries, Debian's package
dependencies will automatically make sure these libraries will be
available when autoconf is installed.

Because autoconf can be used outside a Debian environment this solution
might not work for everyone. Perhaps the AC_SEARCH_LIBS function should
be extended so function arguments needed to check a library could be
provided as well, or perhaps there is an other way to make it compatible
with g++ 8.

Regards,
Chaim Zax & Paul

p.s. I'm not an autoconf developer, currently working at the BSP in
Venlo 

Processed: Move to the source package so that the BTS knows it is fixed

[Debian Bug Tracking System]

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

> reassign 874727 src:coin3
Bug #874727 {Done: Kurt Kremitzki } [libcoin80v5] 
libcoin80v5: Program using libcoin80v5 and any other library that uses 
lebexpat1 segfaults.
Bug reassigned from package 'libcoin80v5' to 'src:coin3'.
No longer marked as found in versions coin3/3.1.4~abc9f50+dfsg1-2 and 
coin3/3.1.4~abc9f50+dfsg3-2.
No longer marked as fixed in versions coin3/3.1.4~abc9f50+dfsg2-1 and 
4.0.0~CMake~6f54f1602475+ds1-1.
> fixed 874727 4.0.0~CMake~6f54f1602475+ds1-1
Bug #874727 {Done: Kurt Kremitzki } [src:coin3] libcoin80v5: 
Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.
Marked as fixed in versions coin3/4.0.0~CMake~6f54f1602475+ds1-1.
> affects 874727 libcoin80v5
Bug #874727 {Done: Kurt Kremitzki } [src:coin3] libcoin80v5: 
Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.
Added indication that 874727 affects libcoin80v5
> thanks
Stopping processing here.

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

Bug#918439: cockpit: FTBFS (failing tests)

[Andreas Henriksson]

Hello,

On Sun, Jan 06, 2019 at 12:55:49AM +, Santiago Vila wrote:
> Package: src:cockpit
> Version: 184-1
> Severity: serious
> Tags: ftbfs
[...]
> 
> Testsuite summary for Cockpit 184
> 
> # TOTAL: 882
> # PASS:  806
> # SKIP:  45
> # XFAIL: 0
> # FAIL:  31

Lots of failing tests there

> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> Please report to de...@lists.cockpit-project.org
> 
[...]
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cockpit.html
[...]

I just looked at the first one and it fails here:

$ head -n 57 src/common/test-webserver.c  | tail -n 2
  inet = cockpit_test_find_non_loopback_address ();
  g_assert (inet != NULL);

I'm thus going to assume that the build environments that runs into
these problems uses network namespaces or similar and doesn't expose
anything but loopback to the build chroot.

I looked a bit closer at cockpit_test_find_non_loopback_address
in src/common/cockpittest.c and it seems it needs the following
conditions met:
- interface is up
- ipv4 or ipv6 address configured
- g_inet_address_get_is_loopback () returning false for a found address

I presume the rest of the "webserver" tests fail for followup reasons
related to that, but there are also other tests that fails that
I haven't really diven deeper into to find why they fail.

It might be a good idea to first just test if all problems vanishes
if builting in a less network restricted environment, maybe that
confirms the suspision without having to dive deep in every problem
instantly.

HTH

The long-term solution should probably be that the test-suite
automatically checks pre-conditions it has and skips the tests
that can not be run under the current build environment automatically.

Regards,
Andreas Henriksson

Bug#919095: marked as done (Please remove (build-)dependency on mongodb for buster)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 20:42:50 +
with message-id 
and subject line Bug#919095: fixed in apache-log4j2 2.11.1-2
has caused the Debian Bug report #919095,
regarding Please remove (build-)dependency on mongodb for buster
to be marked as done.

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

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


-- 
919095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongodb
Version: 1:3.4.15-1
Severity: serious
Justification: Cannot be properly supported

MongoDB should not be part of (at least) Buster for the following 
reasons:

 - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it 
   to be included in Buster.

 - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch 
   to SSPLv1 complicates matters. As discussed in #915537, we will not 
   be distributing any SSPL-licensed software, and keeping the last 
   AGPL-licensed version (3.6.8 or 4.0.3) without the ability to 
   cherry-pick upstream fixes is not a viable option. (I am currently 
   not considering distributing mongodb in non-free.)

I will not request removal immediately, to allow other packages time to 
adjust their dependencies, but eventually auto-removal will kick in.  

That said, MongoDB 3.4 will probably remain in sid for as long as it is 
AGPL-licensed and supported upstream.

Apollon

[1] https://www.mongodb.com/support-policy
--- End Message ---
--- Begin Message ---
Source: apache-log4j2
Source-Version: 2.11.1-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 11:33:45 -0800
Source: apache-log4j2
Binary: liblog4j2-java liblog4j2-java-doc
Architecture: source
Version: 2.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 liblog4j2-java - Apache Log4j - Logging Framework for Java
 liblog4j2-java-doc - Documentation for Apache Log4j 2
Closes: 919095
Changes:
 apache-log4j2 (2.11.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop support for mongodb (Closes: #919095)
   * Standards-Version updated to 4.3.0
Checksums-Sha1:
 c3a2f78f4725558ce0176fc0a8730d34300d67d9 3006 apache-log4j2_2.11.1-2.dsc
 27511b409139dcce4842a2db2efc9bf228e4082e 6632 
apache-log4j2_2.11.1-2.debian.tar.xz
 37b2a30d33a756e1813ac26d8ff8c1fec03e1abe 16897 
apache-log4j2_2.11.1-2_amd64.buildinfo
Checksums-Sha256:
 187ec798c69f2e617dd32ef5db0a0f47b71535a85ca50d19c364fe89086498c6 3006 
apache-log4j2_2.11.1-2.dsc
 4a22e42fa2addda17a4e46e7ce8559a1c60b19e5b9f759b1a217b3dc64382c66 6632 
apache-log4j2_2.11.1-2.debian.tar.xz
 b6b7565156e04546d08d3ed574639c60e1053182ca395e4400bcd78c1722b9e0 16897 
apache-log4j2_2.11.1-2_amd64.buildinfo
Files:
 d2202aadf7b7df460e88759dc89d8ba0 3006 java optional apache-log4j2_2.11.1-2.dsc
 2c813daa3c3b056446842e1f2feacfed 6632 java optional 
apache-log4j2_2.11.1-2.debian.tar.xz
 cb23087de7ddb0c9788c6cdde6b63e78 16897 java optional 
apache-log4j2_2.11.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlw6RhUUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbV9A//cHsjm3WUNuAVtZELPOM/maPSAEri
AHXiRDUZeo8pnhf9pci/ypyf+6hxrMYyGHe0nr+Mr83S4HtotWcsjNvjKLhVLfmb
AQ5cUhA8meWOapX4Trkf0+7Oh/0h3eGJprizUDvOmBrKxvD7tAjDS1ZYwrNEVcXB
BSPBAcsw2VG//Sgka4r25FLW94/0lHVewPHcytXWjc4EI21BTdDITua1TlrGSMun
hea/HbvNfJRI+IzsCs+o9V7lgPzT3bYDcTqgVQ2Oijbixq/Rslxs6ryPSoVdmUw3
q/G6kr+Qk7QY3E+zLO0+KnttXgv4Natssz0AUMB9MR7pcbW8c3UZXsrbtJ/HEDKw
J6jHN+nAsa5WbvJYrL3DSEkZnTNnxqfnKd1KMpNYVix01Sbji6sOyaJxu/3QZVSG
ngpjjrtNvSwiSWSu2WPqMrakLnkmmj0QwZaRDhUYsAABgoQTbmHGlxQT9QcHL5et
ZgNeKcW0TCMjuHPcKYwObsDP8UrSKkL7hlP96APM/D40eX2tdqUoPVtJPIHx8OTn
qL+aD8hk4bSBCourcJftUJK30bwfP5JzrcI9QBtNgRUrYiN3lBwpC4G29sQGuvBI
TkZrkSx47y/EMHYKBF85mls3aGX+1fWI4ZK5AR7nBIAZWKDt+ECZLVU/SHiczfVQ
QxthNcelSrEzZqQ=
=VwDc
-END PGP SIGNATURE End 

Bug#919092: Bug#919095: Bug#919092: fixed in mongo-java-driver 3.6.3-2

[tony mancill]

On Sat, Jan 12, 2019 at 09:21:51PM +0100, Ivo De Decker wrote:
> Hi Emmanuel,
> 
> On Sat, Jan 12, 2019 at 07:35:09PM +, Emmanuel Bourg wrote:
> >* Removed the unused build dependency on mongodb-server (Closes: #919092)
> 
> Thanks for the quick fix.
> 
> Does this mean #919095 can just be closed? apache-log4j2 only (build-)depends
> on libmongodb-java, not (directly) on mongodb.

Oops, I interpreted the bug report to mean that we should drop support
for MongoDB completely, but might have been a tad too hasty.

Should I revert 
https://salsa.debian.org/java-team/apache-log4j2/commit/4d8cf4493ad9f63a8cf8d24ae463bd18a12ed1a1
 and restore support for that logging adapter?

Thank you,
tony

Bug#905254: update of libphp-phpmailer to 6.0

[Paul Gevers]

Hi all,

On Mon, 10 Dec 2018 12:03:04 +0100 Cyrille Bollu  wrote:
> Cacti:
> 
> 
> Latest version of cacti upstream still uses PHPMailer 5.2.x.
> 
> I've created a bug upstream: https://github.com/Cacti/cacti/issues/2206

Cacti upstream release a new version with phpmailer 6 embedded. I need
the new version as well.

> tt-rss:
> 
> 
> It seems like latest version don't necessarily use phpmailer anymore:
> 
> (https://git.tt-rss.org/fox/tt-rss/src/master)
> 
> >commit 57932e183745bada9c6183056597cb5276f68d10
> >Author: Andrew Dolgov 
> >Date:   Thu Nov 22 14:45:14 2018 +0300
> >
> >remove PHPMailer and related directives from config.php-dist; add
> pluggable Mailer class
> >
> 
> maybe tt-rss maintainer should be asked to update to latest upstream
> version?

@tt-rss maintainers, I am working on uploading a new version of
libphp-phpmailer with the latest upstream release. I expect that has
impact for the functionality of tt-rss, but that is going to be removed
from buster anyways if we don't fix this bug anyways. This is your
heads-up that you probably need to adapt one way or the other.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Investigation results

[Debian Bug Tracking System]

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

> noowner 827832
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Removed annotation that Bug was owned by Stewart Ferguson .
> thank you
Stopping processing here.

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

Processed: closing 915574

[Debian Bug Tracking System]

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

> close 915574 3.6.1+dfsg-5
Bug #915574 [libsimbody3.6] libsimbody3.6: missing Breaks+Replaces: 
libsimbody3.5v5
Marked as fixed in versions simbody/3.6.1+dfsg-5.
Bug #915574 [libsimbody3.6] libsimbody3.6: missing Breaks+Replaces: 
libsimbody3.5v5
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#918751: Investigation results

[Stewart Ferguson]

noowner 827832
thank you

The interesting part of the reporter's logs suggest that the following test
fails:

shade.tests.unit.test_object.TestObjectUploads.test_object_segment_retry_failure

The failure is caused by a thread failing to spawn due to resource
limitations on
the reporter's machine.

The reporter is using a single-processor VM.  I tried to emulate this by using
`dpkg-buildpackage -j1` and again by using `taskset --cpu-list 0
dpkg-buildpackage`.

I was unable to reproduce the problem.  I also fixed another RC bug in
this package

and buildd was also able to build this package.

Because buildd and other single-core builds are all successful, I
would regard this

bug as `important` instead of `serious`.  I am offloading ownership as
I focus on

other RC bugs.

Bug#919092: fixed in mongo-java-driver 3.6.3-2

[Ivo De Decker]

Hi Emmanuel,

On Sat, Jan 12, 2019 at 07:35:09PM +, Emmanuel Bourg wrote:
>* Removed the unused build dependency on mongodb-server (Closes: #919092)

Thanks for the quick fix.

Does this mean #919095 can just be closed? apache-log4j2 only (build-)depends
on libmongodb-java, not (directly) on mongodb.

Thanks,

Ivo

Bug#919113: buildbot-doc: missing Breaks+Replaces: buildbot (<< 1.7.0)

[Andreas Beckmann]

Package: buildbot-doc
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../buildbot-doc_1.7.0-2_all.deb ...
  Unpacking buildbot-doc (1.7.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/buildbot-doc_1.7.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/buildbot/html/_images/force-build.png', 
which is also in package buildbot 0.8.12-3.2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/buildbot-doc_1.7.0-2_all.deb


cheers,

Andreas


buildbot=0.8.12-3.2_buildbot-doc=1.7.0-2.log.gz
Description: application/gzip

Bug#919031: libmono-system4.0-cil: not installable on amd64

[Jo Shields]

Another reason this bug makes no sense is there's no 5.18 references at
all in src:mono, and it doesn't depend on anything externally which
could add it.



I'll try a no-change version bump on another computer.

On 12/01/2019 09:42, Ingo Saitz wrote:
> On Fri, Jan 11, 2019 at 09:52:46PM -0500, Jo Shields wrote:
>> Maybe a typo in debian/rules? I do my builds in a chroot, this kind of thing 
>> shouldn't happen 
> 
> I just tried rebuilding mono 5.16.0.220+dfsg3-1 in a clean chroot, and
> the dependencies look good:
> 
> Package: libmono-system4.0-cil
> Source: mono
> Version: 5.16.0.220+dfsg3-1
> Architecture: all
> Maintainer: Debian Mono Group 
> Installed-Size: 3101
> Depends: libc6 (>= 2.28) | libc6.1 (>= 2.28) | libc0.1 (>= 2.28), 
> libmono-corlib4.5-cil (>= 5.16.0.220), libmono-security4.0-cil (>= 4.6.1.3), 
> libmono-system-configuration4.0-cil (>= 4.0.0~alpha1), 
> libmono-system-xml4.0-cil (>= 4.6.1.3), mono-runtime (>= 5.16.0.220), 
> mono-runtime (<< 5.16.0.221)
> Recommends: ca-certificates-mono (= 5.16.0.220+dfsg3-1)
> Suggests: libasound2 (>> 1.0.18), libgamin0
> Section: cli-mono
> Priority: optional
> Homepage: http://www.mono-project.com/
> Description: Mono System libraries (for CLI 4.0)
>  Mono is a platform for running and developing applications based on the
>  ECMA/ISO Standards. Mono is an open source effort led by Xamarin.
>  Mono provides a complete CLR (Common Language Runtime) including compiler and
>  runtime, which can produce and execute CIL (Common Intermediate Language)
>  bytecode (aka assemblies), and a class library.
>  .
>  This package contains the BCL (Base Class Libraries) of Mono for CLI 4.0.
> 
> 
> I'll keep the buildroot around till this bug can be closed, just query
> me if you want additional information about it.
> 
> Ingo
> 

Bug#919081: kio-gdrive: Unable to create io-slave. klauncher said: error loading gdrive.so

[Nicholas D Steeves]

Control: tags -1 unreproducible moreinfo
Control: severity -1 important

Hi Benoît!

On Sat, Jan 12, 2019 at 03:45:30PM +0100, Benoît Merlet wrote:
> 
> Dear Maintainer,
> 
> After installing kio-gdrive and configuring a Google account in 
> systemsettings5,
> I cannot connect to my Google Drive:
> 
> $ LANG=C kioclient5 exec gdrive:/
> kf5.kio.core: couldn't create slave: "klauncher said: Error loading « 
> /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so »."
> kf5.kio.widgets: KRun(0xa1c13a10) ERROR 173 "Unable to create io-slave. 
> klauncher said: Error loading « 
> /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so »."
> 
> I am not sure how to further debug the problem, but as you can see the
> package is quite unusable.
> 
> Best regards,
> Benoît
> 

I just did the following:

1. Installed buster
2. Logged in and installed kio-gdrive
3. Logged out and logged in again
4. Configured a Google user under "Online Accounts"
5. Opened dolphin -> Network -> Google Drive -> u...@gmail.com

Success.  See attached screenshot.  Because of this, I've downgraded
the severity of this bug to important, according to 
https://www.debian.org/Bugs/Developer#severities

This success was with en_CA.UTF-8.  I wonder if it's possible #915496
is contributing to the issue you're experiencing?  Would you please
confirm the following:

a) Have you tried logging out and logging back in?
b) Is kwallet enabled or disabled and/or was its configuration skipped?

Thank you,
Nicholas


signature.asc
Description: PGP signature

Processed: Re: Bug#919081: kio-gdrive: Unable to create io-slave. klauncher said: error loading gdrive.so

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible moreinfo
Bug #919081 [kio-gdrive] kio-gdrive: Unable to create io-slave. klauncher said: 
error loading gdrive.so
Added tag(s) unreproducible and moreinfo.
> severity -1 important
Bug #919081 [kio-gdrive] kio-gdrive: Unable to create io-slave. klauncher said: 
error loading gdrive.so
Severity set to 'important' from 'grave'

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

Processed: tagging 919091

[Debian Bug Tracking System]

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

> tags 919091 + buster sid
Bug #919091 [loofah] Please remove (build-)dependency on mongodb for buster
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#912069: marked as done (flask-wtf FTBFS: FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase))

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 19:49:08 +
with message-id 
and subject line Bug#912069: fixed in flask-wtf 0.14.2-3
has caused the Debian Bug report #912069,
regarding flask-wtf FTBFS: FAIL: test_i18n_enabled 
(tests.test_i18n.TestI18NCase)
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.)


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

Some recent change in unstable makes flask-wtf FTBFS:

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

...

==
FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase)
--
Traceback (most recent call last):
  File 
"/build/1st/flask-wtf-0.14.2/.pybuild/cpython2_2.7_flaskext.wtf/build/tests/test_i18n.py",
 line 32, in test_i18n_enabled
assert '\u8be5\u5b57\u6bb5\u662f' in to_unicode(response.data)
AssertionError

--
Ran 52 tests in 0.661s

FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/flask-wtf-0.14.2/.pybuild/cpython2_2.7_flaskext.wtf/build; python2.7 
-m nose -v tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:11: build] Error 25
--- End Message ---
--- Begin Message ---
Source: flask-wtf
Source-Version: 0.14.2-3

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated flask-wtf 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: Sat, 12 Jan 2019 20:36:43 +0100
Source: flask-wtf
Binary: python-flaskext.wtf python3-flaskext.wtf python-flaskext.wtf-doc
Architecture: source
Version: 0.14.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christoph Berg 
Description:
 python-flaskext.wtf - Simple integration of Flask and WTForms (Python 2)
 python-flaskext.wtf-doc - Simple integration of Flask and WTForms (doc)
 python3-flaskext.wtf - Simple integration of Flask and WTForms (Python 3)
Closes: 912069
Changes:
 flask-wtf (0.14.2-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
 .
   [ Christoph Berg ]
   * Clean docs/_build/ and don't fail on building twice.
   * Remove obsolete comment about needing flask-testing.
   * Mark python-flaskext.wtf-doc as M-A: foreign.
   * Disable failing i18n test. (Closes: #912069)
   * Disable failing recaptcha test.
Checksums-Sha1:
 01463654a12cba5d03dd9a4fbc9425b734360caf 2382 flask-wtf_0.14.2-3.dsc
 18c91c23fdca72d6c8a8749f6f5469821669de77 4492 flask-wtf_0.14.2-3.debian.tar.xz
Checksums-Sha256:
 c9a106ae7401be7c17062df707e9161186952a45dea8607c0961e4a79f53c2eb 2382 
flask-wtf_0.14.2-3.dsc
 28fc04cd1ea4d03f0f23273400f1885b37be3e4db4f846458bc17dc85b8efec9 4492 
flask-wtf_0.14.2-3.debian.tar.xz
Files:
 b4b88d130bd83089f7d2026b1490c956 2382 python optional flask-wtf_0.14.2-3.dsc
 05822e11af02e9e6ea1d03eb059e6451 4492 python optional 
flask-wtf_0.14.2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlw6Qj4ACgkQTFprqxLS
p67OsA//UmSEN09e37u0Il3sYxkDoTQQ6VF32uyOcgqvxc76okOYlj5UM+d1wYMP
jmlPkjYvhBr+Pi7shN6pdb9Jh78yEv9ajxfjbt8L7FAZ/qLYyFh9NDzJKx4b7sHj
+rBgPlQcTT7zx3oS3AbYrkojUkAmGzeYpKNmxzkoofpiU5YT3Hs/7XSqi0CC8qlb
uKmpY4k93D+CRaebZmBDBgQAGTzm3cimZ0HoxWBDiQNl7w8+qw9ymzpRy7vZ0Bts
jg8ToJgjG3YZiJWscORItNtyV0tjpk6VryAAipbPPCswiZ60wucgHsEHv9oFCGJa

Bug#919092: marked as done (Please remove (build-)dependency on mongodb for buster)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 19:35:09 +
with message-id 
and subject line Bug#919092: fixed in mongo-java-driver 3.6.3-2
has caused the Debian Bug report #919092,
regarding Please remove (build-)dependency on mongodb for buster
to be marked as done.

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

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


-- 
919092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongodb
Version: 1:3.4.15-1
Severity: serious
Justification: Cannot be properly supported

MongoDB should not be part of (at least) Buster for the following 
reasons:

 - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it 
   to be included in Buster.

 - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch 
   to SSPLv1 complicates matters. As discussed in #915537, we will not 
   be distributing any SSPL-licensed software, and keeping the last 
   AGPL-licensed version (3.6.8 or 4.0.3) without the ability to 
   cherry-pick upstream fixes is not a viable option. (I am currently 
   not considering distributing mongodb in non-free.)

I will not request removal immediately, to allow other packages time to 
adjust their dependencies, but eventually auto-removal will kick in.  

That said, MongoDB 3.4 will probably remain in sid for as long as it is 
AGPL-licensed and supported upstream.

Apollon

[1] https://www.mongodb.com/support-policy
--- End Message ---
--- Begin Message ---
Source: mongo-java-driver
Source-Version: 3.6.3-2

We believe that the bug you reported is fixed in the latest version of
mongo-java-driver, 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.
Emmanuel Bourg  (supplier of updated mongo-java-driver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 19:32:55 +0100
Source: mongo-java-driver
Binary: libmongodb-java
Architecture: source
Version: 3.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libmongodb-java - MongoDB Java Driver
Closes: 919092
Changes:
 mongo-java-driver (3.6.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Removed the unused build dependency on mongodb-server (Closes: #919092)
   * Standards-Version updated to 4.3.0
   * Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
 d8619515ce9c45398763b04baf8a0b226ebb0e95 2205 mongo-java-driver_3.6.3-2.dsc
 9ca1e3c4cb87dc910db59b2a8561e5210a99d188 16432 
mongo-java-driver_3.6.3-2.debian.tar.xz
 f839b62d09e73ec536f6347819202ffc9823326c 14587 
mongo-java-driver_3.6.3-2_source.buildinfo
Checksums-Sha256:
 64a051845cb417cdf3f18f4d5e867915b4436156c52d4e3156e923be30b9809a 2205 
mongo-java-driver_3.6.3-2.dsc
 2bc7c890f49c343a59211964c672b223dbf706497913e0027bfee291bc49e10b 16432 
mongo-java-driver_3.6.3-2.debian.tar.xz
 99480ac198431a2a3fed6ef2a9049a621cfee87bf9d38d22e3b118e761499409 14587 
mongo-java-driver_3.6.3-2_source.buildinfo
Files:
 a3f39203d745523b1e9b59baebcd46d9 2205 java optional 
mongo-java-driver_3.6.3-2.dsc
 7fb04b58273f2c1c8398be3055a0d1a7 16432 java optional 
mongo-java-driver_3.6.3-2.debian.tar.xz
 5bfb1f2967dcdf13374e8c8606ad07d0 14587 java optional 
mongo-java-driver_3.6.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlw6PBQSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsot4P/1n+FEhDn0R6LYSG0cK3NDgNoGmGVdXg
iXnDwXGN7SdHmQqoo4s+qW3sUJMNtczmQuXrElotL+7LNyvBm8rgLy1nInx/ud9Q
XDHJ5YdFx3kRkTfdOoqGUYwfTgav0ywTpMKjF5trrn7NWgvA33SsEEN2MdG4XJiE
33uIHOO8E1QgunTN8z7pGM9XUH8/d2tvLeGYMELYE4bMa6Um5KP9mN92Z3tJTSa3
yqPDGz2Qpd/YkQWkd6jzcNj/5aUa5nigSWncNhOrxRkKvcXOKMXEkN1HMNRChNsn
l9+Tiaey2xbQfQyA7rGxkiYBUfGsr/tBEQ7Pbv+kG75+048FzW5nO9jl+7+beUgI
L1wXtgT5R11MPS8/ERi+JgiZIkktqC/K72Fq8wa0rk2uz6VRRu2uo5jUdH8ozOnq
5utc4T+UFN682B0WMpnAD8GEzmggO3LiX6Nn7LdR/C/bA5LFWbz+DXXEKMKuZARz
hjSp2CSR1jlLKoUsMcYAY7nhsSeS5J95hoQR1EDjv87sq8LpbnJ1vQvs0I6UvJVq
8HktV6lu7ravBkz8haSlcuTBl6tOvo2igi4SRXwpp0x4VZU+3lAG1HHsQdu8Zsmy
cVNjqxmeEUEOi7o+ZuVJ8fT668BU9pufH/12bDInkahCIJS/4KGWv8CZfc7ezlv0
QWnYz9lMuRfd
=Stcw
-END PGP 

Processed: owner 919095

[Debian Bug Tracking System]

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

> owner 919095 tmanc...@debian.org
Bug #919095 [apache-log4j2] Please remove (build-)dependency on mongodb for 
buster
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Processed: Bug 827832 fixed, but needs upload

[Debian Bug Tracking System]

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

> tags 827832 + pending
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: Bug #919092 in mongo-java-driver marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919092 [mongo-java-driver] Please remove (build-)dependency on mongodb for 
buster
Added tag(s) pending.

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

Bug#919092: Bug #919092 in mongo-java-driver marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/mongo-java-driver/commit/2131e5961ae832ebbc21c9ac4295bf0fbaed7d22


Removed the unused build dependency on mongodb-server (Closes: #919092)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919092

Bug#915834: marked as done (Breaks SSH connections, listens on \0)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:50:15 +
with message-id 
and subject line Bug#915834: fixed in irqbalance 1.5.0-2
has caused the Debian Bug report #915834,
regarding Breaks SSH connections, listens on \0
to be marked as done.

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

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


-- 
915834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: irqbalance
Version: 1.5.0-0.1
Severity: critical

Thanks to waldi for his help in diagnosing this.

With irqbalance installed, it is no longer possible to connect to
remote systems using SSH when SSH_AUTH_SOCK is unset.

  % SSH_AUTH_SOCK= ssh -S none -v cymbaline true
  […]
  debug1: rekey after 134217728 blocks

and then the client just stays there, indefinitely.

strace reveals:

  socket(AF_UNIX, SOCK_STREAM, 0) = 4
  fcntl(4, F_SETFD, FD_CLOEXEC)   = 0
  connect(4, {sa_family=AF_UNIX, 
sun_path=@"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"},
 110) = 0
  write(4, "\0\0\0\1", 4) = 4
  write(4, "\v", 1)   = 1
  read(4,

and lsof identifies this socket as

  ssh 28605 madduck4u  unix 0x94bc2389  0t0  287876 
type=STREAM

So diving into this, we stumbled over:

  netstat -nap:
  unix  2  [ ACC ] STREAM LISTENING 23121


and then looked at sss -xenp output:

  u_str ESTAB   00  
  

 29 3502* 289678
   users:(("irqbalance",pid=1455,fd=22)) <->
  u_str ESTAB   10  
  

 29 2010* 0 
   users:(("irqbalance",pid=1455,fd=19)) ---
  u_str ESTAB   00  
  

 27 9132* 0 
   users:(("irqbalance",pid=1455,fd=12)) ---

and sure enough, purging irqbalance makes SSH work again.

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

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

Versions of packages irqbalance depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.28-2
ii  libcap-ng0 0.7.9-1+b1
ii  libglib2.0-0   2.58.1-2
ii  libncursesw6   6.1+20181013-1
ii  libnuma1   2.0.12-1
ii  libsystemd0239-14
ii  libtinfo6  6.1+20181013-1
ii  lsb-base   10.2018112800

irqbalance recommends no packages.

irqbalance suggests no packages.


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
--- Begin Message ---
Source: irqbalance
Source-Version: 1.5.0-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated irqbalance package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#918435: libgit-raw-perl: FTBFS (failing tests)

[Niko Tyni]

On Sun, Jan 06, 2019 at 12:14:33AM +, Santiago Vila wrote:
> Package: src:libgit-raw-perl
> Version: 0.79-5
> Severity: serious
> Tags: ftbfs

> Test Summary Report
> ---
> t/33-worktree.t   (Wstat: 512 Tests: 11 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: No plan found in TAP output

This was fixed upstream with

  
https://github.com/jacquesg/p5-Git-Raw/commit/30f7a4491ab453d28ae1fa1b393fcd023f6c344d

which is in upstream 0.82 and just removes the failing test.

However, the newer upstream releases rely on libgit2 bundled API changes,
so they are not suitable for Debian (which uses the system libgit2,
not the bundled one) at this point.

Therefore I've just uploaded a backported targeted fix for this issue,
versioned as 0.79-6.
-- 
Niko Tyni   nt...@debian.org

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

[Rob Browning]

Pavel Kreuzt  writes:

> Package: emacs-gtk
> Version: 1:25.2+1-11
> Severity: important
>
> Dear Maintainer,
>
> when trying to upgrade emacs to 1.26.1+1-3, some installation script fails 
> with following error:

I think it's very likely that this isn't a bug in emacs, but rather one
of the add-on packages, perhaps emacspeak, judging from the placement.

> Remove emacspeak for emacs
> remove/emacspeak: purging byte-compiled files for emacs
> rm: missing operand
> Try 'rm --help' for more information.
> ERROR: remove script from emacspeak package failed
> dpkg: warning: old emacs-gtk package pre-removal script subprocess returned 
> error exit status 1
> dpkg: trying script from the new package instead ...

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

Bug#919000: spyder: 1

[Drew Parsons]

On 2019-01-12 10:08, Adrian Bunk wrote:


https://www.debian.org/Bugs/Developer#severities


"serious" is the severity that is commonly used for missing 
dependencies.



"Grave" could also be justified, "makes the package mostly unusable".

Drew

Processed: Re: ruby-factory-girl-rails: installs files with generic names in /usr/bin

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #910930 [ruby-factory-girl-rails] ruby-factory-girl-rails: installs files 
with generic names in /usr/bin
Bug 910930 cloned as bug 919104
> reassign -2 ruby-factory-bot-rails 4.11.1-1
Bug #919104 [ruby-factory-girl-rails] ruby-factory-girl-rails: installs files 
with generic names in /usr/bin
Bug reassigned from package 'ruby-factory-girl-rails' to 
'ruby-factory-bot-rails'.
No longer marked as found in versions ruby-factory-girl-rails/4.7.0-1.
Ignoring request to alter fixed versions of bug #919104 to the same values 
previously set
Bug #919104 [ruby-factory-bot-rails] ruby-factory-girl-rails: installs files 
with generic names in /usr/bin
Marked as found in versions ruby-factory-bot-rails/4.11.1-1.
> retitle -2 ruby-factory-bot-rails: installs file with generic name: 
> /usr/bin/setup
Bug #919104 [ruby-factory-bot-rails] ruby-factory-girl-rails: installs files 
with generic names in /usr/bin
Changed Bug title to 'ruby-factory-bot-rails: installs file with generic name: 
/usr/bin/setup' from 'ruby-factory-girl-rails: installs files with generic 
names in /usr/bin'.

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

Bug#918435: marked as done (libgit-raw-perl: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:24:54 +
with message-id 
and subject line Bug#918435: fixed in libgit-raw-perl 0.79-6
has caused the Debian Bug report #918435,
regarding libgit-raw-perl: FTBFS (failing tests)
to be marked as done.

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

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


-- 
918435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgit-raw-perl
Version: 0.79-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
SSH2 support enabled
SSL support disabled
CURL support disabled
Threads support enabled
Checking if your kit is complete...
Warning: the following files are missing in your kit:
deps/libgit2/appveyor.yml
deps/libgit2/AUTHORS

[... snipped ...]

ok 36
ok 37
ok 38 - An object of class 'Git::Raw::Rebase::Operation' isa 
'Git::Raw::Rebase::Operation'
ok 39
ok 40
ok 41
ok 42
ok 43
ok 44
ok 45
ok 46
ok 47 - An object of class 'Git::Raw::Rebase' isa 'Git::Raw::Rebase'
ok 48
ok 49
ok 50 - An object of class 'Git::Raw::Index' isa 'Git::Raw::Index'
1..50
ok
t/98-internal.t . 
ok 1
ok 2
ok 3
ok 4
1..4
ok
t/99-cleanup.t .. 
ok 1
ok 2
ok 3
1..3
ok
t/author-pod-coverage.t . skipped: these tests are for testing by the author
t/author-pod-syntax.t ... skipped: these tests are for testing by the author
t/release-check-manifest.t .. skipped: these tests are for release candidate 
testing

Test Summary Report
---
t/33-worktree.t   (Wstat: 512 Tests: 11 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=40, Tests=1667, 12 wallclock secs ( 0.48 usr  0.12 sys +  9.16 cusr  2.34 
csys = 12.10 CPU)
Result: FAIL
Failed 1/40 test programs. 0/1667 subtests failed.
make[1]: *** [Makefile:1290: test_dynamic] Error 255
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
make: *** [debian/rules:4: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

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.
--- End Message ---
--- Begin Message ---
Source: libgit-raw-perl
Source-Version: 0.79-6

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

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

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated libgit-raw-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 12 Jan 2019 19:59:32 +0200
Source: libgit-raw-perl
Binary: libgit-raw-perl
Architecture: source
Version: 0.79-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Niko Tyni 
Description:
 libgit-raw-perl - Perl bindings to the Git linkable library (libgit2)
Closes: 918435
Changes:
 libgit-raw-perl (0.79-6) unstable; urgency=medium
 .
   * Team upload.
   * Backport upstream patch disabling a failing test due to libgit2
 changes (Closes: #918435)
   * Update to Standards-Version 4.3.0
   * Declare that the package does not need (fake)root to build
   * Add Testsuite 

Bug#910930: ruby-factory-girl-rails: installs files with generic names in /usr/bin

[Andreas Beckmann]

Followup-For: Bug #910930
Control: clone -1 -2
Control: reassign -2 ruby-factory-bot-rails 4.11.1-1
Control: retitle -2 ruby-factory-bot-rails: installs file with generic name: 
/usr/bin/setup

... and another one was hit ...


Andreas

Bug#918583: marked as done (libc6: version in nocache Breaks is incorrect)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:20:59 +
with message-id 
and subject line Bug#918583: fixed in glibc 2.28-5
has caused the Debian Bug report #918583,
regarding libc6: version in nocache Breaks is incorrect
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.)


-- 
918583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.28-4
Severity: serious

Breaks: ..., nocache (<< 1.0-1),...

1.0-1 is the version in stable, so this is basically a nop.

It should be Breaks: nocache (<< 1.1-1~)
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.28-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 18:50:25 +0100
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 
libc6-dev-x32 libc6-xen libc0.3-xen libc6.1-alphaev67
Architecture: source
Version: 2.28-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc0.1- GNU C Library: Shared libraries
 libc0.1-dbg - GNU C Library: detached debugging symbols
 libc0.1-dev - GNU C Library: Development Libraries and Header Files
 libc0.1-dev-i386 - GNU C Library: 32bit development libraries for AMD64
 libc0.1-i386 - GNU C Library: 32bit shared libraries for AMD64
 libc0.1-pic - GNU C Library: PIC archive library
 libc0.1-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3- GNU C Library: Shared libraries
 libc0.3-dbg - GNU C Library: detached debugging symbols
 libc0.3-dev - GNU C Library: Development Libraries and Header Files
 libc0.3-pic - GNU C Library: PIC archive library
 libc0.3-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3-xen - GNU C Library: Shared libraries [Xen version]
 libc6  - GNU C Library: Shared libraries
 libc6-amd64 - GNU C Library: 64bit Shared libraries for AMD64
 libc6-dbg  - GNU C Library: detached debugging symbols
 libc6-dev  - GNU C Library: Development Libraries and Header Files
 libc6-dev-amd64 - GNU C Library: 64bit Development Libraries for AMD64
 libc6-dev-i386 - GNU C Library: 32-bit development libraries for AMD64
 libc6-dev-mips32 - GNU C Library: o32 Development Libraries for MIPS
 libc6-dev-mips64 - GNU C Library: 64bit Development Libraries for MIPS64
 libc6-dev-mipsn32 - GNU C Library: n32 Development Libraries for MIPS64
 libc6-dev-powerpc - GNU C Library: 32bit powerpc development libraries for 
ppc64
 libc6-dev-ppc64 - GNU C Library: 64bit Development Libraries for PowerPC64
 libc6-dev-s390 - GNU C Library: 32bit Development Libraries for IBM zSeries
 libc6-dev-sparc - GNU C Library: 32bit Development Libraries for SPARC
 libc6-dev-sparc64 - GNU C Library: 64bit Development Libraries for UltraSPARC
 libc6-dev-x32 - GNU C Library: X32 ABI Development Libraries for AMD64
 libc6-i386 - GNU C Library: 32-bit shared libraries for AMD64
 libc6-mips32 - GNU C Library: o32 Shared libraries for MIPS
 libc6-mips64 - GNU C Library: 64bit Shared libraries for MIPS64
 

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

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:19:41 +
with message-id 
and subject line Bug#867140: fixed in cqrlog 2.3.0-1
has caused the Debian Bug report #867140,
regarding cqrlog: 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.)


-- 
867140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cqrlog
Version: 2.0.5-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.

Sebastian
--- End Message ---
--- Begin Message ---
Source: cqrlog
Source-Version: 2.3.0-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated cqrlog 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: Sat, 12 Jan 2019 18:51:27 +0100
Source: cqrlog
Binary: cqrlog
Architecture: source
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Description:
 cqrlog - Advanced logging program for hamradio operators
Closes: 867140
Changes:
 cqrlog (2.3.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version.
   * Remove build-dependency on libssl*-dev, it is not used at build time.
   * Remove hardcoded dependency on libssl at runtime; we depend on
 default-mysql-client which will pull in a suitable libssl package anyway.
 (Closes: #867140)
   * Move appdata.xml to /usr/share/metainfo.
   * Priority: optional.
   * Run wrap-and-sort -st.
Checksums-Sha1:
 cbaad48b497de4692e5b6d1185f8e53f1f14e513 2244 cqrlog_2.3.0-1.dsc
 35fbaa4aae88e264f158149a19fec88b0bed6d6a 10407716 cqrlog_2.3.0.orig.tar.gz
 81783b1bc9c0b4ce4f953f2c4869d8a6198b648e 11512 cqrlog_2.3.0-1.debian.tar.xz
Checksums-Sha256:
 14f35e54524d7cc632ad048b35543c19b3b0cf069a62b3864ae888a447d8b4cb 2244 
cqrlog_2.3.0-1.dsc
 59809b3fba42b17e3c50aaefe6fe57d593d847c9697ee6386ee4a64b6b04c483 10407716 
cqrlog_2.3.0.orig.tar.gz
 238c6361bed34ebd13e1bf9b760d822d3ce03580b60e74c9861cf09495731e60 11512 
cqrlog_2.3.0-1.debian.tar.xz
Files:
 646977659a3744e12e4c537e3cb03464 2244 hamradio optional cqrlog_2.3.0-1.dsc
 7c5b9982aa8c8f78773949906da822d8 10407716 hamradio optional 
cqrlog_2.3.0.orig.tar.gz
 327a1abbb92f981073cce9e6560595b3 11512 hamradio optional 
cqrlog_2.3.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlw6Ko0ACgkQTFprqxLS
p67jfQ/+PtkKX0acs4i+j+g2ZK/uhg7kYYT3Yy0nsFUCsm66gR7UDMr5nCXzZ2ZF
614daw/JF14BfngxDeKvHXknMm0Qa8iUhiqLZeM6PEoUdvP93yL1J7xJI8laRNYC
osl2fQCDh6IiVIHwNICy2ZbpCMF+UqGRMjCBr+0mIigzQlt6AKuZw3Cg/LgIOx5D
14we3u+gNOWx7ANNLSTZ09AVgboSNTIlPTc8JPU/w098UomdRZdo1ECXtf1NM8TL
HROGZ+hzH7l/pMoIq8bKVe/QTthPcy6Sr7cxzSXONhwJVl56zpmGNJVz2xbeBXvs
zBDc7jFsRmbqjRAGKAYpYOiyX+fa7fBu0StfbEZZ7eejwR7Cz3DQoYlzHqpC63F8
QBx8dtIYWMkiCgMomZN+55BofXs527LEKieEO3Iv96aFAYaokT2/Bd8keP42r147
rAzirzp9H3p+gB9fSN/7FXaZQr8DYvlSEPRcgbBBSxP1NuL/f+IPzYAlsXKjW1/V
25+29mxtEsIHGrdoIqil1cfwOzvR0tUQ1fT63QYEA35eq16KqxCj5xHP8NcdEHdn
Nal1Qos7zYKBPsUtJHdC6T1Y8zm6CwWWG2z66PTWz8nMXb8weeiuZ+zJFZBURoTl
eUg1635zo6r3WcmuorIVgPtwGFpQYdoQAl63O1B4LLtHQn6MKq8=
=Gp00
-END PGP SIGNATURE End Message ---

Bug#919103: libreoffice-kde5: failure to upgrade from stretch: soffice.odg also in libreoffice-kde

[Cyril Brulebois]

Package: libreoffice-kde5
Version: 1:6.1.4-3
Severity: serious
Justification: failure to install/upgrade

Hi,

Testing the upgrade path from stretch to buster for various desktop
tasks, I've noticed the following issue:

Unpacking libreoffice-kde5 (1:6.1.4-3+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-q3iqce/43-libreoffice-kde5_1%3a6.1.4-3+b1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/templates/.source/soffice.odg', which is 
also in package libreoffice-kde 1:5.2.7-1+deb9u4

which breaks the dist-upgrade.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Processed: Bug #918435 in libgit-raw-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918435 [src:libgit-raw-perl] libgit-raw-perl: FTBFS (failing tests)
Added tag(s) pending.

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

Bug#918435: Bug #918435 in libgit-raw-perl marked as pending

[Niko Tyni]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libgit-raw-perl/commit/39a5e0ca9046cfe7153db125c10608288c1de031


Backport upstream patch disabling a failing test due to libgit2 changes

Closes: #918435


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918435

Bug#916567: marked as done (golang-github-juju-testing-dev: depends on the removed golang-github-juju-utils-dev)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:10:10 +
with message-id 
and subject line Bug#916567: fixed in golang-github-juju-utils 
0.0~git20171220.f38c0b0-5
has caused the Debian Bug report #916567,
regarding golang-github-juju-testing-dev: depends on the removed 
golang-github-juju-utils-dev
to be marked as done.

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

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


-- 
916567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-juju-testing-dev
Version: 0.0~git20170608.2fe0e88-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 golang-github-juju-testing-dev : Depends: golang-github-juju-utils-dev but it 
is not installable

golang-github-juju-utils-dev was recently removed from sid.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: golang-github-juju-utils
Source-Version: 0.0~git20171220.f38c0b0-5

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

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

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

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated golang-github-juju-utils 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Dec 2018 13:34:19 -0500
Source: golang-github-juju-utils
Binary: golang-github-juju-utils-dev
Architecture: source all
Version: 0.0~git20171220.f38c0b0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Alexandre Viau 
Description:
 golang-github-juju-utils-dev - General utility functions
Closes: 916567
Changes:
 golang-github-juju-utils (0.0~git20171220.f38c0b0-5) unstable; urgency=medium
 .
   * New upload to unstable. The package should not have been removed as
 it still has relevant reverse dependencies. (Closes: #916567)
   * Remove unused golang-github-juju-mutex-dev dependency.
Checksums-Sha1:
 10341f1d187d327aeac25eef0808798dd7eae402 2686 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5.dsc
 2daf471af438c15280227842e916b1f10b4f1a8b 3872 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5.debian.tar.xz
 c82b5ebdfac93f310a5a90e8d6e0cd21d46bb719 172964 
golang-github-juju-utils-dev_0.0~git20171220.f38c0b0-5_all.deb
 3df1b9ce22f93151c9b4b8b3c46ad11eeb94ee2f 7298 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5_amd64.buildinfo
Checksums-Sha256:
 eeb55998fd42e25353031a7557b379cacc39fd438e46ce3d7893545cb4bdc0fd 2686 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5.dsc
 3a65b325d9c71aa348ade6fe510f78889aa06d5c5369db1bdd8e13fc595e1669 3872 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5.debian.tar.xz
 abd6d1063b5b33fee92389e0f29f3096b837556a7705d209994dc8c149b1b1d8 172964 
golang-github-juju-utils-dev_0.0~git20171220.f38c0b0-5_all.deb
 eeb3cebe7f7d90c8a0a834cc23bb65db9d40a689a62a0ba055f69e529b2d321a 7298 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5_amd64.buildinfo
Files:
 11c77323e108441534aa5040917d3941 2686 devel optional 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5.dsc
 a204839e5ca57e0679f17ccc292d9a30 3872 devel optional 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5.debian.tar.xz
 aab7f38eaa26d8e8ee4f8d8f00b4eedf 172964 devel optional 
golang-github-juju-utils-dev_0.0~git20171220.f38c0b0-5_all.deb
 d1e1274bbdeedeb324dc0bb14d89fbac 7298 devel optional 
golang-github-juju-utils_0.0~git20171220.f38c0b0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEB0B3ii38SjnAyLyMjysRPGU1xacFAlwqZMkACgkQjysRPGU1
xacnYQ/9FGWvf3it8wz9yvo82LI6masFv8U1/3C+8XR+h86Jc3qMOpAAsfbtFZ80
EO7oOop0zLJp5DyvnaOJVgeuHMnS56Yf1C43Po5Pz12Y7VL2A5c4gUYeNqXmXp44
/q1Z6qY0SBLCORHOOSAB7YCH8iXhnQrDLO1gvb9Od6jc5j7yQKAxCjfA19HOpmLm
Q5y09eo/e+O6//BpCdAfVHg06voLYnbitwNuA7ncgbCg/RIprK0PbfnUjviszO+D
PvgyV0UosFvr8kDYbcgYsdkr/QHn44wSEYiaeh1v6PxZ6yqfOUD9Ad9CpId8kKXx
06LWHrrmFy9fEZ7Wh5b9C2u/1cSN4m3PUJ4BPux7ZLngRlkvEBYolW1o8PV7aPTa
l+ZNxNyNXxVl08Gq/7tV3ZFnBtadhxrxlaKMhfAsKlhzj9CnGyzGU7Y5rrmWrtHG

Bug#899943: marked as done (thin-provisioning-tools: Invalid maintainer address pkg-lvm-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:07:54 +
with message-id 
and subject line Bug#899943: fixed in thin-provisioning-tools 0.7.6-1
has caused the Debian Bug report #899943,
regarding thin-provisioning-tools: Invalid maintainer address 
pkg-lvm-maintain...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:thin-provisioning-tools
Version: 0.7.4-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of thin-provisioning-tools,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: thin-provisioning-tools
Source-Version: 0.7.6-1

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

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

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

Debian distribution maintenance software
pp.
Bastian Blank  (supplier of updated thin-provisioning-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 18:01:30 +0100
Source: thin-provisioning-tools
Binary: thin-provisioning-tools
Architecture: source
Version: 0.7.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LVM Team 
Changed-By: Bastian Blank 
Description:
 thin-provisioning-tools - Tools for handling thinly provisioned device-mapper 
meta-data
Closes: 899943
Changes:
 thin-provisioning-tools (0.7.6-1) unstable; urgency=medium
 .
   * New upstream release.
   * Set maintainer to team via tracker.debian.org. (closes: #899943)
   * Fix spelling error in description.
   * Don't run tests if asked not to.
Checksums-Sha1:
 d33d23180969292267da9d67ba1fe24dd25ae026 1731 
thin-provisioning-tools_0.7.6-1.dsc
 4dbbd83f7cfcf247fa8a9ad8a7ab756d578834f7 216560 
thin-provisioning-tools_0.7.6.orig.tar.xz
 5e39a271afa4f3430eb5b1c340fed54fbe7079a8 4248 
thin-provisioning-tools_0.7.6-1.debian.tar.xz
 dce1c5ce43723ea688ceec64f293d88eac95e1e8 5220 
thin-provisioning-tools_0.7.6-1_source.buildinfo
Checksums-Sha256:
 b436656a32bce80467ab53b5e2ae5eef5d2f3647942395ed5b420267ea7ae896 1731 
thin-provisioning-tools_0.7.6-1.dsc
 

Bug#915630: marked as done (simbody: tests fail on several architectures)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:07:12 +
with message-id 
and subject line Bug#915630: fixed in simbody 3.6.1+dfsg-5
has caused the Debian Bug report #915630,
regarding simbody: tests fail on several architectures
to be marked as done.

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

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


-- 
915630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simbody
Version: 3.5.4+dfsg2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

simbody FTBFS on several architectures with test failures:

https://buildd.debian.org/status/package.php?p=simbody=unstable
https://buildd.debian.org/status/package.php?p=simbody=experimental

In a local rebuild (of the version in experimental) on i386
I also got a std::bad_alloc, so these may be related.


Andreas
--- End Message ---
--- Begin Message ---
Source: simbody
Source-Version: 3.6.1+dfsg-5

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

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

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated simbody 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 16:21:58 +
Source: simbody
Binary: libsimbody3.6 libsimbody-dev simbody-doc
Architecture: source
Version: 3.6.1+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libsimbody-dev - SimTK multibody dynamics API - development files
 libsimbody3.6 - SimTK multibody dynamics API - shared library
 simbody-doc - SimTK multibody dynamics API - Documentation
Closes: 915630
Changes:
 simbody (3.6.1+dfsg-5) unstable; urgency=medium
 .
   * Update patch to disable non ending tests on i386
 (Closes: #915630)
Checksums-Sha1:
 96fea52847d346499722dbcf07590289cc54cbe8 1865 simbody_3.6.1+dfsg-5.dsc
 943895b4c711fd0d8e519bf96cd2e5ef2421da04 13692 
simbody_3.6.1+dfsg-5.debian.tar.xz
 caff3601dfe6e5538a4e9ab99b82c8368c8a43c7 11917 
simbody_3.6.1+dfsg-5_source.buildinfo
Checksums-Sha256:
 c8041a70565d6ca80e51a0c434ffb1525a6f1974e9d17507932e619363f444b8 1865 
simbody_3.6.1+dfsg-5.dsc
 9e3974affd1e88795ea777520808ae7dfaf477feaa158cf94897f153eb186a7b 13692 
simbody_3.6.1+dfsg-5.debian.tar.xz
 181b0a93e0f3cb576c242d2fd6150e68d8e0cc73ef97c8ae04d7091556015022 11917 
simbody_3.6.1+dfsg-5_source.buildinfo
Files:
 9aee7df7502a0af4a2916446f3bddac7 1865 science optional simbody_3.6.1+dfsg-5.dsc
 2062075019d16a1f8e5f478e20107d9d 13692 science optional 
simbody_3.6.1+dfsg-5.debian.tar.xz
 31b33808fdd57e8b6cdc9a737c3ea58d 11917 science optional 
simbody_3.6.1+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFOBAEBCgA4FiEEoIFhu+wcwGOWFFkDXpRsCQr/BCcFAlw6HccaHGpyaXZlcm9A
b3NyZm91bmRhdGlvbi5vcmcACgkQXpRsCQr/BCcxxQf/STiwcULTu7kGIJB/vVTI
MTIqXz0MdK+d+rx+L9SET8/HEpOvYDZQPp7h6mS3Ebkv+QZpCjXf3KOhC4HqJFSW
r6Sx5zMg74lRKkyF5YSJ4E2yjxvzmyi3pR4cDc2d5sQVsh/GNDbfaiMFOrcdxN7Y
l7bUNpCoy7olTxuS40hSvg1h5xzf3ZXE88XsIEr7ZIVVVAgmfl75qfpM28ywgNqk
xmX6Bw7GELg2PYNwyZAtDcjXZc6SovR+INsQxq0pw8HXH//5GcxilEd++i1ld30f
edt/7jwg+IQJyvRgfC+B4QN2JuExeivs2D3VD10KoNVAZRhmwOIY5uhGptK2gaGO
zw==
=qAM8
-END PGP SIGNATURE End Message ---

Bug#918671: marked as done (python-shade: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 18:03:49 +
with message-id 
and subject line Bug#918671: fixed in python-shade 1.30.0-2
has caused the Debian Bug report #918671,
regarding python-shade: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
918671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-shade
Version: 1.30.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Clint Byrum , ftpmas...@debian.org

Hi,

I just ACCEPTed python-shade from NEW but noticed it was missing 
attribution in debian/copyright for at least OVH, IBM, Red Hat.

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


Regards,

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

We believe that the bug you reported is fixed in the latest version of
python-shade, 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.
Stewart Ferguson  (supplier of updated python-shade 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: Sat, 12 Jan 2019 16:01:01 +0100
Source: python-shade
Binary: python-shade python3-shade shade-inventory
Architecture: source
Version: 1.30.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Stewart Ferguson 
Description:
 python-shade - Client library for operating OpenStack clouds
 python3-shade - Client library for operating OpenStack clouds
 shade-inventory - Ansible inventory script for OpenStack clouds
Closes: 918671
Changes:
 python-shade (1.30.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Completing d/copyright (Closes: #918671)
Checksums-Sha1:
 42d5cec2f9bdcf4d029a48ac79778b88f9c31b01 2583 python-shade_1.30.0-2.dsc
 713de4f14fd1049262824dacbfbc0bf2fc2bce98 4452 
python-shade_1.30.0-2.debian.tar.xz
Checksums-Sha256:
 e19f345b0a4ff768e5dd273d026abb4d9e94665c2eaa2ca5d10acd43e80aa792 2583 
python-shade_1.30.0-2.dsc
 7504b2a4b0fe40a1ac47bf7f16e24f8554ee677148d7752ca1651c2350b16499 4452 
python-shade_1.30.0-2.debian.tar.xz
Files:
 d82d03ab8403e625d33400026a8137dc 2583 python optional python-shade_1.30.0-2.dsc
 54f87465e90764437a74aacf06a82263 4452 python optional 
python-shade_1.30.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlw6D/sACgkQnFyZ6wW9
dQpIowf+NIJ7S9OUlaQVTIBIGQPJfM+VIigMDPRHOeRppl6ww+N4Yc8dPFFGsD6P
OPX8g7rCvWmFk1phCs1G5eEP3Gq5BpIcUWtIzJNmeuNxrE6nR2/RHWaeB/Ja2rY3
7WcNu1On7sdRLUiEM/KS+/WcNJ26/mEgwCGrz1JkwgqYT/V1MDUfk/Dq7tJQfzPr
blQed9+tI4sagSxl9KT+P0s1a4eq0M2V0Rj71TxT0F+Le+gnBKrd2dbIWvSlSfjc
2R8X2z36kAAGyd7QqQcRgHZJDViSIBx6OXiyUTmyciricsmYxEGuSY6uViQqzRZW
sQ+CkOs8gyAgYVkLUq0Pziduhc5z6w==
=478h
-END PGP SIGNATURE End Message ---

Processed: Claiming an issue

[Debian Bug Tracking System]

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

> owner 918751 !
Bug #918751 [src:python-shade] python-shade: FTBFS in sid
Owner recorded as Stewart Ferguson .
> owner 918761 !
Bug #918761 [abcde] abcde: glyrc and recode required
Owner recorded as Stewart Ferguson .
>
End of message, stopping processing here.

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

Bug#917251: marked as done (eas4tbsync: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 17:52:15 +
with message-id 
and subject line Bug#917251: fixed in eas4tbsync 0.7.20-2
has caused the Debian Bug report #917251,
regarding eas4tbsync: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
917251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eas4tbsync
Version: 0.7.20-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Mechtilde Stehmann , 
ftpmas...@debian.org

Hi,

I just ACCEPTed eas4tbsync from NEW but noticed it was probably
missing  attribution in debian/copyright for Ingo Mueller as
the "Initial Developer"?

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: eas4tbsync
Source-Version: 0.7.20-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 18:02:41 +0100
Source: eas4tbsync
Binary: webext-eas4tbsync
Architecture: source all
Version: 0.7.20-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Mechtilde Stehmann 
Description:
 webext-eas4tbsync - Provide Exchange ActiveSync (EAS v2.5 & v14.0) 
synchronization ca
Closes: 917251
Changes:
 eas4tbsync (0.7.20-2) unstable; urgency=medium
 .
   [ Mechtilde ]
   * complete license statement (Closes: #917251)
   * bump standard version to 4.3.0
Checksums-Sha1:
 9a09aafbef5ca7bfa37992d2eb06923296710e27 2000 eas4tbsync_0.7.20-2.dsc
 e3a43d1ab6b9c3e5447e212e2ff60af80f2ebb8e 7808 eas4tbsync_0.7.20-2.debian.tar.xz
 e63b2bf688137b76eacd6b7bcaa456a6b03cdaa3 7058 
eas4tbsync_0.7.20-2_amd64.buildinfo
 5341377206e54af404379dd10395b6341a7b5b56 226212 
webext-eas4tbsync_0.7.20-2_all.deb
Checksums-Sha256:
 ad1f284edde7bd85b705d5d7a8b608368a17868ac3d4f45c70f14d070e42ca83 2000 
eas4tbsync_0.7.20-2.dsc
 07789d79f7301dd3cc17812d85a52e52a29a548a5071ff1d400ffa6407790761 7808 
eas4tbsync_0.7.20-2.debian.tar.xz
 49705e8ace6cc1850d5e4307d2a4962c2be2609861286c6aaa56083cfe3543df 7058 
eas4tbsync_0.7.20-2_amd64.buildinfo
 b1134d2822990f31b89de7873ef2230206cbaa2dd4bf1e7a0fc07a69be50e391 226212 
webext-eas4tbsync_0.7.20-2_all.deb
Files:
 e1dc0e92cbda30d78a633b6ddf4c2539 2000 mail optional eas4tbsync_0.7.20-2.dsc
 0901cfccc8c316ce292ece4901825d17 7808 mail optional 
eas4tbsync_0.7.20-2.debian.tar.xz
 7063927524176deef65f0b660b7f 7058 mail optional 
eas4tbsync_0.7.20-2_amd64.buildinfo
 ee6de980c0231649491d47a6ecaf6156 226212 mail optional 
webext-eas4tbsync_0.7.20-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAlw6HlwACgkQ8od7uhQa
rX/keQ//Q9fc+YwdD+Lz+zrIXe7i8bpw8PuEn0uMMmegSa/zh33g9/bXM5VxcLNy
T5Hna9VzPddcXh/WZ/gqpHflfwAVkkFseDjunWpUeP+bCl+EsO5MGga0ouJxaVrX
LHzeqP4V1FSzdhKtXk+lN/aD0jQCxHFi7lShpTaqxe9R0uo+EzgCRFPrHrnzLj/v
Ljc07qLCUJ4nUSJoWPQjHkwd66mPU1ahC0PVPkNk/EQot7luSHSUBTSNu3A6tYcr
iUC0ejxJ6JyITmucjGmdmd2HB3peHe7MClzB1ioauVtQ0ipcWoD7QcoV5uPkQwUX
P15N+5y2rG9/x4GXa7JmuapaZtJNhOH3+LOEz1spjexpviRzhzMzMHPVh20+hcMi
6TKtNdaWjk96JrzWKqtm9b3yGHFVe/saupV4W653aG9BzzmrgDsvloBUC31FA6dC
02EOiOuESTnMD5N3d/FsAyKq4NhCLFAKgf2D3XZQtYnioYnrlOWcJQGZKUgIS58z
qOitqAUOm3mNwpuBe/MQPYgHcTkOvHzRwSIdt87zc/IFaoSCZYtCl0EaMjGQXjpI
IV8aELHQq/FVXGxWJ0fm+RaKV1L81zCBeRQHE68X1F0YnJIVLTBb4Y8DId06ObGG
IIFJx3tE/WM7msWdIePUL8xmNWN3YPLEwad9AC7UoNO3LSN4Duw=
=Zr93
-END PGP SIGNATURE End Message ---

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

[A. Maitland Bottoms]

On Sat, 12 Jan 2019 16:02:02 +0100
Christoph Berg  wrote:
> Maitland, can we remove predict?
> 
> Christoph

Yes...
Certainly predict-gsat is obsolete and unmaintained - and gpredict is
the logical successor.

But...
There might be curses interface fans who would mourn its removal, but
the codebase has never been easy to adapt.

There is a voice mode in predict that I think is still on the TODO list
to migrate to gpredict.

So...
I won't stand in the way of a consensus to remove predict...
I find myself using gpredict or even Python sgp4 rather than predict.

-Maitland

Bug#918447: working on these Pelican bugs

[Geert Stappers]

user debian-rele...@lists.debian.org
usertags -1 + bsp-2019-01-nl-venlo
thank you

One is about a new release, the other python3.
And 918447 is a FTBFS

Context https://wiki.debian.org/BSP/2019/01/nl/Venlo


Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: PGP signature

Processed: Tagging bug 827832

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was s...@ferg.aero).
> usertags 827832 + bsp-2019-01-nl-venlo
Usertags were: bsp-2019-01-nl-venlo.
Usertags are now: bsp-2019-01-nl-venlo.
> owner 827832 !
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Ignoring request to set the owner of bug #827832 to the same value
>
End of message, stopping processing here.

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

Processed: Claiming bug 827832

[Debian Bug Tracking System]

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

> owner 827832 !
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Owner recorded as Stewart Ferguson .
>
End of message, stopping processing here.

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

Bug#917249: marked as done (dav4tbsync: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 16:19:28 +
with message-id 
and subject line Bug#917249: fixed in dav4tbsync 0.10-2
has caused the Debian Bug report #917249,
regarding dav4tbsync: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
917249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dav4tbsync
Version: 0.10-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Mechtilde Stehmann , 
ftpmas...@debian.org

Hi,

I just ACCEPTed dav4tbsync from NEW but noticed it was missing 
attribution in debian/copyright for at least Aleksandr Kitov.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: dav4tbsync
Source-Version: 0.10-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 17:01:28 +0100
Source: dav4tbsync
Binary: webext-dav4tbsync
Architecture: source all
Version: 0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Mechtilde Stehmann 
Description:
 webext-dav4tbsync - Provide CalDAV & CardDAV for TbSync
Closes: 917249
Changes:
 dav4tbsync (0.10-2) unstable; urgency=medium
 .
   [ Mechtilde ]
   * complete license statement (Closes: #917249)
   * fixed uscan error
   * changed standard version to 4.3.0
 + no changes needed
   * remove lintian warnings
   * add lintian-overrides
 + line 323 in content/sync.js is source code
Checksums-Sha1:
 13e53f05ad9b71bf8dba359855ad1f823dd14bb4 1986 dav4tbsync_0.10-2.dsc
 f1a74fd6f8883c6e169aed4aa3f60061638b6d2a 8364 dav4tbsync_0.10-2.debian.tar.xz
 3076d719519d395ae0b3f4db741515cc4581f314 7042 dav4tbsync_0.10-2_amd64.buildinfo
 dcc14ffde34b7ba5911fb43669b7bb90ca74ecf4 113088 
webext-dav4tbsync_0.10-2_all.deb
Checksums-Sha256:
 4d329ee3e7e91eeaa6eb723d3e046f2017134cb4a6a6247b7db33ddf1829e74d 1986 
dav4tbsync_0.10-2.dsc
 3316181b2affb227c4ed4cc79a9d5274a728b3c9f1ba2baabf47a2a04e7ace43 8364 
dav4tbsync_0.10-2.debian.tar.xz
 459cdbf8dd128f38aab4e99efa4d314cd10e8e5f829a6686fe0dc81f59bb1522 7042 
dav4tbsync_0.10-2_amd64.buildinfo
 aabfb8070e03d05f8a8fe3e25a8056d1d569d94d5d6af1cb18c96263e5217375 113088 
webext-dav4tbsync_0.10-2_all.deb
Files:
 4c36ec315089f0c094ef45d6adc205bc 1986 mail optional dav4tbsync_0.10-2.dsc
 4577fb6e155632bf8c8a96a7dfcc5d19 8364 mail optional 
dav4tbsync_0.10-2.debian.tar.xz
 6737bd43bad809d94475b50854b5fbac 7042 mail optional 
dav4tbsync_0.10-2_amd64.buildinfo
 60a8b4a7a69fb42e301c9854e3b59204 113088 mail optional 
webext-dav4tbsync_0.10-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAlw6D9oACgkQ8od7uhQa
rX//eg//Y7Cpw+kaHtznQdpK/VdS51bobs7DeV3CGY5fxLMK0D3aOJLa+X6qJFRr
58SFucNKLMZKBblZ5yqBLTcC2Vziir55dnbNQZtEviVVkUU+sIjHlTFNZyl/8JCF
uAftYtQpfJ0lYBRKoP2uM3hDNtuT5v/xYrhCSalaDnkZS2HWrVr8oDzOyrMQqqB1
FQeGzrCwXdLWb0khVAb2TBZbm9t/+yd3+CAggkIserTladhZOcWIaEgcbU6scW8+
b458kzwKZfmKjLUyGWXfzB8Poavoz1YuoZhkZeTZjOc+JkjzQqVWeKvThe7dC73p
AsbX9i8FmooGwPPKnIGP6dpSafTWN+Fi86JuaiTbXWxZXYt6Ki3a2Xv3ciZqYC/O
MJapduYjsox/czH4ljR/3OovJw7QYJQ7asHy3l7vI0a2+mTGxgQcIjAzBW2/4Azq
S5Y94IBR1Yxmhh+JVMnVTuidg/p+X+Q9Sg+b1HglcSF+NuJgimZ+fAQXPAwm9YMY
m318wQ4lqEd0XbZ1YsYAI7t1CO0gIR8ldalIv6EJOgq8c41tCC8sk3F/XqSnSJyf
qA1s57kANa3xTHiF2scW8Z3Ekt8QcEPO6txycHFy7p2gHNBPGXfvxdKY2EDH4mS5
YjbGLtgWeASQnoNI59Z+Q1QWEAbPTN+4UNmB1u3HLs0x6nNnBp8=
=5dyz
-END PGP SIGNATURE End Message ---

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

[Ivo De Decker]

Hi,

On Wed, Aug 23, 2017 at 11:41:28PM +0530, Pirate Praveen wrote:
> On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote:
> > Package: node-lodash-packages
> > Severity: serious
> > Justification: Policy 2.1
> 
> I do not think the root issue is serious, but only important.
> 
> > The source package node-lodash-packages does not contain the source form
> > preferred for editing by upstream.  Instead, upstream documents how the
> > contents of that code is generated from the sources included in Debian
> > in the source package node-lodash.
> 
> Adding a build dependency on node-lodash would be enough for the policy
> requirement.

No it wouldn't. You need to actually generate the code instead of shipping the
pregenerated code from upstream. Not doing that is a serious bug. If you think
this is easy to fix, please do so. If not, this package should be removed
from testing.

Thanks,

Ivo