Bug#906769: arm kernels fail to boot

[Domenico Andreoli]

On Wed, Aug 22, 2018 at 4:36 AM Salvatore Bonaccorso  wrote:
>
> Hi,

ciao,

> On Tue, Aug 21, 2018 at 10:07:42PM +0200, Salvatore Bonaccorso wrote:
> > I have put in
> >
> > https://people.debian.org/~carnil/tmp/linux/arm64/
> > https://people.debian.org/~carnil/tmp/linux/armel/
> > [https://people.debian.org/~carnil/tmp/linux/all/]
>
> armhf packages:
> https://people.debian.org/~carnil/tmp/linux/armhf/

armmp on Allwinner A20: it works.

thanks,
Domenico

-- 
3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13

Bug#906769: arm kernels fail to boot

[Salvatore Bonaccorso]

Hi,

On Tue, Aug 21, 2018 at 10:07:42PM +0200, Salvatore Bonaccorso wrote:
> I have put in
> 
> https://people.debian.org/~carnil/tmp/linux/arm64/
> https://people.debian.org/~carnil/tmp/linux/armel/
> [https://people.debian.org/~carnil/tmp/linux/all/]

armhf packages:
https://people.debian.org/~carnil/tmp/linux/armhf/

Regards,
Salvatore

Bug#906901: debian-policy: Perl script shebang requirement is disturbing and inconsistent with rest of policy

[Russ Allbery]

Control: severity -1 normal

Norbert Preining  writes:

> The recent addition to the Debian Policy to require a Perl shebang of
> /usr/bin/perl is inconsistent with the rest of script usage, and hinders
> the user/system administrator to freely override Perl.

This isn't recent.  All we did was change should to must in the main
policy, and it was already must in the Perl policy.

> If a user/system admin wants to replace Perl by prepending the path to a
> self compiled Perl to the PATH, it is his right to do so, and Perl
> scripts are expected to follow this decision. It is the obligation of
> the one doing the change to ensure proper availability of modules and
> support files.

There were literally zero packages in Debian that did this that Lintian
could find.  Did we miss something?

-- 
Russ Allbery (r...@debian.org)   

Processed: Re: Bug#906901: debian-policy: Perl script shebang requirement is disturbing and inconsistent with rest of policy

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #906901 [debian-policy] debian-policy: Perl script shebang requirement is 
disturbing and inconsistent with rest of policy
Severity set to 'normal' from 'serious'

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

Bug#905578: emacs-goodies-el: Another output

[Alexandre Lymberopoulos]

Package: emacs-goodies-el
Version: 40.0
Followup-For: Bug #905578

Dear Maintainer,

I just tried to run apt-get upgrade and the output was

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  paprefs
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB

Total disk space freed by localepurge: 0 KiB

W: APT had planned for dpkg to do more than it reported back (0 vs 4).
   Affected packages: emacs-goodies-el:amd64

Hope this helps to ellucidate what is going on.

Thanks in advance,
Alexandre

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

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

Versions of packages emacs-goodies-el depends on:
ii  bash   4.4.18-3.1
ii  dpkg   1.19.0.5+b1
ii  emacs25 [emacsen]  25.2+1-6+b3
ii  emacsen-common 2.0.8
ii  install-info   6.5.0.dfsg.1-4

Versions of packages emacs-goodies-el recommends:
pn  elpa-apache-mode
pn  elpa-bar-cursor 
pn  elpa-bm 
pn  elpa-boxquote   
pn  elpa-browse-kill-ring   
pn  elpa-csv-mode   
pn  elpa-debian-el  
pn  elpa-devscripts 
pn  elpa-diminish   
pn  elpa-dpkg-dev-el
pn  elpa-eproject   
pn  elpa-graphviz-dot-mode  
pn  elpa-htmlize
pn  elpa-initsplit  
pn  elpa-markdown-mode  
pn  elpa-pod-mode   
pn  elpa-session
pn  elpa-tabbar 
pn  perl-doc
ii  wget1.19.5-1

emacs-goodies-el suggests no packages.

-- no debconf information

Bug#905578: emacs-goodies-el: Same failure here

[Alexandre Lymberopoulos]

Package: emacs-goodies-el
Version: 40.0
Followup-For: Bug #905578

Dear Maintainer,

I report the same error here, after running dpkg --configure emacs-goodies-el I 
get:

Setting up emacs-goodies-el (40.0) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
Install emacs-goodies-el for emacs25
install/emacs-goodies-el: Handling emacs25, logged in /tmp/elc_xb2p1N.log
Building autoloads for emacs25 in /usr/share/emacs25/site-lisp/emacs-goodies-el
ERROR: install script from emacs-goodies-el package failed
dpkg: error processing package emacs-goodies-el (--configure):
 installed emacs-goodies-el package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 emacs-goodies-el

On aptitude interface I have to hold this package to be able to upgrade any 
other package and emacs-goodies-el is marked as partially installed (with C) on 
it. If I try to reinstall it I get

E: Internal Error, No file name for emacs-goodies-el:amd64

When I "unhold" it I see

Performing actions...
Setting up emacs-goodies-el (40.0) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
Install emacs-goodies-el for emacs25
install/emacs-goodies-el: Handling emacs25, logged in /tmp/elc_luFPQp.log
Building autoloads for emacs25 in /usr/share/emacs25/site-lisp/emacs-goodies-el
ERROR: install script from emacs-goodies-el package failed
dpkg: error processing package emacs-goodies-el (--configure):
 installed emacs-goodies-el package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 emacs-goodies-el
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB

Total disk space freed by localepurge: 0 KiB

E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up emacs-goodies-el (40.0) ...
Install emacsen-common for emacs25
emacsen-common: Handling install of emacsen flavor emacs25
Install emacs-goodies-el for emacs25
install/emacs-goodies-el: Handling emacs25, logged in /tmp/elc_rnS13E.log
Building autoloads for emacs25 in /usr/share/emacs25/site-lisp/emacs-goodies-el
ERROR: install script from emacs-goodies-el package failed
dpkg: error processing package emacs-goodies-el (--configure):
 installed emacs-goodies-el package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 emacs-goodies-el
Press Return to continue, 'q' followed by Return to quit.

I may provide any information to maintainers to help solve this.

Thanks in advance, Alexandre.

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

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

Versions of packages emacs-goodies-el depends on:
ii  bash   4.4.18-3.1
ii  dpkg   1.19.0.5+b1
ii  emacs25 [emacsen]  25.2+1-6+b3
ii  emacsen-common 2.0.8
ii  install-info   6.5.0.dfsg.1-4

Versions of packages emacs-goodies-el recommends:
pn  elpa-apache-mode
pn  elpa-bar-cursor 
pn  elpa-bm 
pn  elpa-boxquote   
pn  elpa-browse-kill-ring   
pn  elpa-csv-mode   
pn  elpa-debian-el  
pn  elpa-devscripts 
pn  elpa-diminish   
pn  elpa-dpkg-dev-el
pn  elpa-eproject   
pn  elpa-graphviz-dot-mode  
pn  elpa-htmlize
pn  elpa-initsplit  
pn  elpa-markdown-mode  
pn  elpa-pod-mode   
pn  elpa-session
pn  elpa-tabbar 
pn  perl-doc
ii  wget1.19.5-1

emacs-goodies-el suggests no packages.

-- no debconf information

Bug#906901: debian-policy: Perl script shebang requirement is disturbing and inconsistent with rest of policy

[Norbert Preining]

Package: debian-policy
Version: 4.2.0.1
Severity: serious

The recent addition to the Debian Policy to require a Perl shebang of
/usr/bin/perl is inconsistent with the rest of script usage, and hinders
the user/system administrator to freely override Perl.

If a user/system admin wants to replace Perl by prepending the path to
a self compiled Perl to the PATH, it is his right to do so, and Perl
scripts are expected to follow this decision. It is the obligation of
the one doing the change to ensure proper availability of modules and
support files.

Package maintainers are free to use the more restrictive /usr/bin/perl
shebang when the consider it necessary, but this must not be a
requirement in the policy.

I hereby suggest removing this line
In the case of Perl scripts this must be "#!/usr/bin/perl".
from policy 10.4.

Sincerely yours

Norbert


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

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

Versions of packages debian-policy depends on:
ii  libjs-sphinxdoc  1.7.6-1

debian-policy recommends no packages.

Versions of packages debian-policy suggests:
pn  doc-base  

-- no debconf information
Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#906762: marked as done (lmodern: FTBFS in buster/sid (New files were found in the patched tarball))

[Debian Bug Tracking System]

Your message dated Wed, 22 Aug 2018 01:34:19 +
with message-id 
and subject line Bug#906762: fixed in lmodern 2.004.5-5
has caused the Debian Bug report #906762,
regarding lmodern: FTBFS in buster/sid (New files were found in the patched 
tarball)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh_testdir fonts/type1/public/lm/lmr10.pfb tex/latex/lm/lmodern.sty
# Warn the person building the package if new files were added
# to the .orig.tar.gz + .diff.gz that this script is not aware of.
New files were found in the patched tarball (.orig.tar.gz + .diff.gz):
  ./.pc/.quilt_series
  ./.pc/.quilt_patches
  ./.pc/.version
  ./.pc/applied-patches

Please update the debian/rules file accordingly.
make: *** [debian/rules:11: build-indep-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lmodern.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: lmodern
Source-Version: 2.004.5-5

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

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

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated lmodern package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Aug 2018 10:15:43 +0900
Source: lmodern
Binary: lmodern fonts-lmodern
Architecture: source all
Version: 2.004.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX maintainers 
Changed-By: Norbert Preining 
Description:
 fonts-lmodern - OpenType fonts based on Computer Modern
 lmodern- scalable PostScript and OpenType fonts based on Computer Modern
Closes: 906762
Changes:
 lmodern (2.004.5-5) unstable; urgency=medium
 .
   * go back to source format 1.0, dpkg/quilt creates irrelevant
 directories in case no patches are available, breaking builds
 (Closes: #906762)
Checksums-Sha1:
 9fe9355beddfb5919111955361f89dafd385249a 1722 lmodern_2.004.5-5.dsc
 8463358188e2c0a5f9145a7188f74d9fc9fe11c2 20344 lmodern_2.004.5-5.diff.gz
 c990eb7a265bc2eecbf83689b82b0ca655634e56 4539100 
fonts-lmodern_2.004.5-5_all.deb
 6d82ad3ad4462fed80a1a3a5ac8fc57facf8401d 9479748 lmodern_2.004.5-5_all.deb
 b3de137bbac93e4ce69fd187c5a7aaef0b120aa7 5991 lmodern_2.004.5-5_amd64.buildinfo
Checksums-Sha256:
 1dc4968d399f3aa1eae98bc7c24445496e8e69a16c9ed9d571aabfcd435e99e9 1722 
lmodern_2.004.5-5.dsc
 bed6f5d7d84852bd4e10691d929da10e415088719e54b616bfe0a84ce213ed39 20344 
lmodern_2.004.5-5.diff.gz
 e41e04430baec20d5d0fe28b0ead93af32fbfbb2b7c6c4e478c94c8735a9cbae 4539100 
fonts-lmodern_2.004.5-5_all.deb
 e4663efc99b288c599c9c230508520aaa4ecfc8b18572d16e849f73c7ba395e6 9479748 
lmodern_2.004.5-5_all.deb
 d4bc209b87b9ef84c3a212d3cba7a128852c98f78469b210b0f754e7a583cd86 5991 
lmodern_2.004.5-5_amd64.buildinfo
Files:
 61bf40192671fedf8a7e002acb219268 1722 fonts optional lmodern_2.004.5-5.dsc
 5de710705e6413750ac2fd59bffbe4d6 20344 fonts optional lmodern_2.004.5-5.diff.gz
 25faf8aa437b42fedb30abcf3f78d5ff 4539100 fonts optional 
fonts-lmodern_2.004.5-5_all.deb
 a3153d028da77feb4da3527372d9d3c3 9479748 fonts optional 
lmodern_2.004.5-5_all.deb
 4c10fa199a36fc833064f769fc7f33f0 5991 fonts optional 
lmodern_2.004.5-5_amd64.buildinfo

-BEGIN PGP 

Processed (with 1 error): Properly set usertag for #906861 nukeimage removal

[Debian Bug Tracking System]

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

> severity 906861 normal
Bug #906861 [ftp.debian.org] RM: nukeimage -- RoM; Firefox no longer supports 
XUL addons
Severity set to 'normal' from 'serious'
> user ftp.debian@packages.debian.org
Setting user to ftp.debian@packages.debian.org (was 073p...@gmail.com).
> usertag remove
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#885740: gnomekiss: Port to GTK+ 3

[Markus Koschany]

Am 21.08.2018 um 11:41 schrieb Yavor Doganov:
> Yavor Doganov wrote:
>> Please find attached a patch that ports the program to GTK+ 3.
> 
> I wasn't careful enough; my patch introduces memory leaks.  Please
> find attached an updated version (compressed); please use it instead.
> Thanks.

Hey, thanks for your patch again!

I have uploaded a new revision just now. This is quite an old game from
2006 so we should take a closer look if the changes work out.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#906861: mozilla-nukeimage no longer works with firefox-esr 60

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #906861 [mozilla-nukeimage] mozilla-nukeimage no longer works with 
firefox-esr 60
Bug reassigned from package 'mozilla-nukeimage' to 'ftp.debian.org'.
No longer marked as found in versions nukeimage/0.3-12.
Ignoring request to alter fixed versions of bug #906861 to the same values 
previously set
> affects -1 mozilla-nukeimage
Bug #906861 [ftp.debian.org] mozilla-nukeimage no longer works with firefox-esr 
60
Added indication that 906861 affects mozilla-nukeimage
> retitle -1 RM: nukeimage -- RoM; Firefox no longer supports XUL addons
Bug #906861 [ftp.debian.org] mozilla-nukeimage no longer works with firefox-esr 
60
Changed Bug title to 'RM: nukeimage -- RoM; Firefox no longer supports XUL 
addons' from 'mozilla-nukeimage no longer works with firefox-esr 60'.

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

Bug#906861: mozilla-nukeimage no longer works with firefox-esr 60

[Colin Watson]

Control: reassign -1 ftp.debian.org
Control: affects -1 mozilla-nukeimage
Control: retitle -1 RM: nukeimage -- RoM; Firefox no longer supports XUL addons

On Tue, Aug 21, 2018 at 09:14:08PM +0300, Adrian Bunk wrote:
> Package: mozilla-nukeimage
> Version: 0.3-12
> Severity: serious
> 
> XUL addons are no longer supported.

Yeah, I think it's time to put this package to bed.  ftpmaster, please
remove it.

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Processed: bug 906708 is not forwarded

[Debian Bug Tracking System]

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

> notforwarded 906708
Bug #906708 [src:hepmc] hepmc: FTBFS on i386 / arm64 / ppc64el / s390x
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

Bug#895642: marked as done (sqlite: snprintf wrongly used, path truncated)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 23:09:01 +
with message-id 
and subject line Bug#895642: fixed in sqlite 2.8.17-15
has caused the Debian Bug report #895642,
regarding sqlite: snprintf wrongly used, path truncated
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.)


-- 
895642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlite
Version: 2.8.17-14
Severity: serious

Compiling lemon.c with -Wall, leads to the following warning (among many
others):

| cc -g -O2 -fdebug-prefix-map=/tmp/sqlite-2.8.17=. -fstack-protector-strong 
-Wformat -Werror=format-security -DTHREADSAFE=1 -Wall -o lemon ./tool/lemon.c
| ./tool/lemon.c: In function 'pathsearch':
| ./tool/lemon.c:2724:37: warning: argument to 'sizeof' in 'snprintf' call is 
the same expression as the destination; did you mean to provide an explicit 
length? [-Wsizeof-pointer-memaccess]
|  if( path ) snprintf(path,sizeof path,"%s/%s",argv0,name);
|  ^~~~
| ./tool/lemon.c:2737:30: warning: argument to 'sizeof' in 'snprintf' call is 
the same expression as the destination; did you mean to provide an explicit 
length? [-Wsizeof-pointer-memaccess]
|  snprintf(path,sizeof path,"%s/%s",pathlist,name);
|   ^~~~

Looking at the code, it comes from those lines:

|  char *path,*cp;
| ...
|path = (char *)malloc( strlen(argv0) + strlen(name) + 2 );
|if( path ) snprintf(path,sizeof path,"%s/%s",argv0,name);

and

|path = (char *)malloc( strlen(pathlist)+strlen(name)+2 );
| ... 
|snprintf(path,sizeof path,"%s/%s",pathlist,name);

The second argument of snprintf limits the number of byte written. While
the buffer path is allocated dynamically using malloc, the size passed
to snprintf is the size of the pointer, which is 4 or 8 bytes depending
on the architecture, resulting in a truncation of the path.

The issue is specific to the debian package and has been introduced by
debian/patches/02-lemon-snprintf.patch. The original code is correct
so the two corresponding hunk should be reverted.

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: sqlite
Source-Version: 2.8.17-15

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated sqlite 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: Tue, 21 Aug 2018 21:19:22 +
Source: sqlite
Binary: sqlite sqlite-doc libsqlite0 libsqlite0-dev libsqlite-tcl
Architecture: source amd64 all
Version: 2.8.17-15
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libsqlite-tcl - SQLite 2 Tcl bindings
 libsqlite0 - SQLite 2 shared library
 libsqlite0-dev - SQLite 2 development files
 sqlite - command line interface for SQLite 2
 sqlite-doc - SQLite 2 documentation
Closes: 872535 895642
Changes:
 sqlite (2.8.17-15) unstable; urgency=medium
 .
   * Make the package multiarch.
   * Drop incorrect hunks from lemon patch (closes: #895642).
   * Fix package installation.
   * Fix test compilation.
   * Ignore test failures for known problems.
   * Make rebuildable.
   * Update debhelper level to 11:
 - don't specify parallel to debhelper.
   * Update Standards-Version to 4.1.5 .
 .
   [ Aurelien Jarno  ]
   * Fix FTBFS with GCC 7/8 on architectures with unsigned char
 (closes: #872535).
Checksums-Sha1:
 d5326a8e6114f10bce35a6909f0611f6d68c8388 1982 sqlite_2.8.17-15.dsc
 

Bug#872535: marked as done (sqlite FTBFS with gcc-7/8 on architectures with unsigned char)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 23:09:01 +
with message-id 
and subject line Bug#872535: fixed in sqlite 2.8.17-15
has caused the Debian Bug report #872535,
regarding sqlite FTBFS with gcc-7/8 on architectures with unsigned char
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.)


-- 
872535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlite
Version: 2.8.17-14
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlite.html

...
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-DTHREADSAFE=1 -o lemon ./tool/lemon.c
./tool/lemon.c: In function 'tplt_open':
./tool/lemon.c:2821:7: warning: implicit declaration of function 'access' 
[-Wimplicit-function-declaration]
   if( access(buf,004)==0 ){
   ^~
./tool/lemon.c:2713:14: note: previous declaration of 'access' was here
   extern int access();
  ^~
cp ./tool/lempar.c .
cp ./src/parse.y .
./lemon parse.y
Makefile:261: recipe for target 'parse.c' failed
make[2]: *** [parse.c] Segmentation fault
make[2]: *** Deleting file 'parse.c'
make[2]: Leaving directory '/build/1st/sqlite-2.8.17'
debian/rules:37: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2


I've confirmed on armel that the segfault is also present there,
and goes away when building lemon with gcc-6.
--- End Message ---
--- Begin Message ---
Source: sqlite
Source-Version: 2.8.17-15

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated sqlite 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: Tue, 21 Aug 2018 21:19:22 +
Source: sqlite
Binary: sqlite sqlite-doc libsqlite0 libsqlite0-dev libsqlite-tcl
Architecture: source amd64 all
Version: 2.8.17-15
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libsqlite-tcl - SQLite 2 Tcl bindings
 libsqlite0 - SQLite 2 shared library
 libsqlite0-dev - SQLite 2 development files
 sqlite - command line interface for SQLite 2
 sqlite-doc - SQLite 2 documentation
Closes: 872535 895642
Changes:
 sqlite (2.8.17-15) unstable; urgency=medium
 .
   * Make the package multiarch.
   * Drop incorrect hunks from lemon patch (closes: #895642).
   * Fix package installation.
   * Fix test compilation.
   * Ignore test failures for known problems.
   * Make rebuildable.
   * Update debhelper level to 11:
 - don't specify parallel to debhelper.
   * Update Standards-Version to 4.1.5 .
 .
   [ Aurelien Jarno  ]
   * Fix FTBFS with GCC 7/8 on architectures with unsigned char
 (closes: #872535).
Checksums-Sha1:
 d5326a8e6114f10bce35a6909f0611f6d68c8388 1982 sqlite_2.8.17-15.dsc
 fd20283ad2f87676299f0dfcc8ad178de97fe6a5 11004 sqlite_2.8.17-15.debian.tar.xz
 762059bc65bfdaba475a41c766852c3d40fd22dd 35968 
libsqlite-tcl-dbgsym_2.8.17-15_amd64.deb
 37ef3b2c5c0119f4dd62b156a8bd7d2956d386be 12976 
libsqlite-tcl_2.8.17-15_amd64.deb
 c29171378826148210861740b6000fba5db05c75 390916 
libsqlite0-dbgsym_2.8.17-15_amd64.deb
 f33a76070f76621c179c79d6b10cf54e9e68f63d 191868 
libsqlite0-dev_2.8.17-15_amd64.deb
 b39c671038fc20cdce475b10b9663acafe36275e 165392 libsqlite0_2.8.17-15_amd64.deb
 673590bc53c051454a5bc8c2523fdaec645fb246 23436 
sqlite-dbgsym_2.8.17-15_amd64.deb
 621e1c3decb76a4386d39ad70327d9313a64dcf4 136332 sqlite-doc_2.8.17-15_all.deb
 3d824aae9eae0db6a307a98d74d6616f9043ce36 8699 sqlite_2.8.17-15_amd64.buildinfo
 31d8bbf50bc35101d5eea52508222ab6f3ddac55 21548 sqlite_2.8.17-15_amd64.deb
Checksums-Sha256:
 d773d1dbfeddc54c4a2441c22f00dd3fb719043d9e7f38894786fbeff2dfb3e5 1982 
sqlite_2.8.17-15.dsc
 beb87e551fc2cfe47e6f1c8ae949bee3c06c55b5e0575e28a2ab35d89aa9edd4 11004 
sqlite_2.8.17-15.debian.tar.xz
 3a77f08856e6e01c78f73c71006eab12ce4ceb6f8e5ea01427381ccdf17ad86f 35968 

Bug#885740: marked as done (gnomekiss: Depends on libgnomeui)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 23:06:36 +
with message-id 
and subject line Bug#885740: fixed in gnomekiss 2.0-6
has caused the Debian Bug report #885740,
regarding gnomekiss: Depends on libgnomeui
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.)


-- 
885740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnomekiss
Version: 2.0-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnomekiss
Source-Version: 2.0-6

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Aug 2018 23:51:15 +0200
Source: gnomekiss
Binary: gnomekiss
Architecture: source
Version: 2.0-6
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 gnomekiss  - KiSS paper doll viewer for GNOME
Closes: 885740
Changes:
 gnomekiss (2.0-6) unstable; urgency=low
 .
   * Team upload.
   * Add gtk3-port.patch. Replace obsolete Gnome 2 build-dependencies and port
 the game to GTK-3. Thanks to Yavor Doganov for the patch! (Closes: #885740)
   * Switch to compat level 11.
   * Declare compliance with Debian Policy 4.2.0.
   * Move the package to salsa.debian.org.
   * Drop deprecated menu file.
Checksums-Sha1:
 4b2efd5438cf5b46a291668b029840452aca69de 2129 gnomekiss_2.0-6.dsc
 ae956a5a95d394c21a8ece7e7241f5ef1c6ec2b8 25860 gnomekiss_2.0-6.debian.tar.xz
 fc17801fe010b7a9261f7893b094dc7135eb313c 14157 gnomekiss_2.0-6_amd64.buildinfo
Checksums-Sha256:
 49c9b261c25a5c65df4d149248f277d6cd541d9f22f0d93aefeb6a10b415c6d1 2129 
gnomekiss_2.0-6.dsc
 c069097a24faf4a3169a207dd4825b6262be15c0f4e378bf198ff730825fa7d1 25860 
gnomekiss_2.0-6.debian.tar.xz
 d5a0003b04f1147dd3bd6e9f357bfd1af9469721928843195cd6b0e47cb221f4 14157 
gnomekiss_2.0-6_amd64.buildinfo
Files:
 4ac62e6ea918bdc54b05137257e24015 2129 gnome optional gnomekiss_2.0-6.dsc
 5b247d8b20ecc649ad990638a82bed47 25860 gnome optional 
gnomekiss_2.0-6.debian.tar.xz
 51156bbdcd59c1707ed48010e413e946 14157 gnome optional 
gnomekiss_2.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlt8lZRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkSDIQALWYVM29PmV2zoIziIw75MQvGj8bCAN8To0r
w4vy4I/AEFK7pPVjZ7hLaInYVpPQt0QnHQdLz3yZNLhbOEK0xRhyfDz+HaG4+jaw
MFz033YjiWH5zhSjvuBaruleMPR47Dd5suHw0rcIn1HXsNfNFM+zLiz4qyCE+hbH
tnSygg2OGV6GN//kRAuIcuq8zRVfAMUSMQKIlNS8a33mq12bZtcMCPEM4eQ7QAVY
9sLwQJm4a74UENZ2/Cdc0VhmAj4ve/7WwkuqVwRKSRUi7NlhmRp9lHwXPmfc4bpA
/BRR1XotYMXPxBzwJiNQw1IxmE/VSDB9NK/Toj1Xozbo+p5/BPj4EkbTddRJY8Wy
5C2mX4JuS6yyh5uAroXPU+mlM9y7Wm+suRBHI9V+nSQ99fDtOJ4yr+pttK50DCBd
JJ8g2T09ubk4dBtVhsn3l169WrDJ/x87hJWQf3zsCcO6KKedDBQaeMfzFYcvqW2H
7UQXAK4U2vOSajfRmYN5As+NQ5jnI+Op9qrm+/al2agmvcF1T8xs5LxyrZX58Z7w
JsbbDJLeijWrN7E0Ae3j2XMxucDw6aidlc5plbMeajvFLX06X/DlxQbDeaVkTy5q
Wdjpf87qeA6HTl4aVNUFgqBSrT3z3vErw/w3VgLoTIbVqeLrX+fujZDpL/9yfdRA
2Lco1XGl
=scmm
-END PGP SIGNATURE End Message ---

Bug#906892: marked as done (gimp: file conflict with gimp-python)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 22:28:25 +
with message-id 
and subject line Bug#906892: fixed in gimp 2.10.6-2
has caused the Debian Bug report #906892,
regarding gimp: file conflict with gimp-python
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.)


-- 
906892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.6-1
Severity: serious
Justification: fails to upgrade/install

Hi!
On upgrading:

Unpacking gimp (2.10.6-1) over (2.10.2-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-zHQiJC/10-gimp_2.10.6-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/gimp/2.0/plug-ins/colorxhtml/colorxhtml.py', 
which is also in package gimp-python 2.10.6-1

The file is present in the new version of gimp-python as well, thus a fresh
install would fail the same.


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

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

Versions of packages gimp depends on:
iu  gimp-data2.10.6-1
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-00.1.56-1
ii  libbz2-1.0   1.0.6-9
ii  libc62.27-5
ii  libcairo21.15.10-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.2.0-4
iu  libgdk-pixbuf2.0-0   2.36.12-2
ii  libgegl-0.4-00.4.8-1
ii  libgexiv2-2  0.10.8-1
iu  libgimp2.0   2.10.6-1
ii  libglib2.0-0 2.56.1-2
ii  libgs9   9.22~dfsg-2.1
iu  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b1.8.8-2
ii  libheif1 1.3.2-1
ii  libilmbase23 2.2.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  liblzma5 5.2.2-1.3
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2
ii  libopenexr23 2.2.1-4
ii  libopenjp2-7 2.3.0-1
ii  libpango-1.0-0   1.42.4-1
ii  libpangocairo-1.0-0  1.42.4-1
ii  libpangoft2-1.0-01.42.4-1
ii  libpng16-16  1.6.34-2
ii  libpoppler-glib8 0.63.0-2
ii  librsvg2-2   2.40.20-2
ii  libstdc++6   8.2.0-4
ii  libtiff5 4.0.9-6
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libwmf0.2-7  0.2.8.4-12
ii  libx11-6 2:1.6.5-1
ii  libxcursor1  1:1.1.15-1
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gimp recommends:
ii  ghostscript  9.22~dfsg-2.1

Versions of packages gimp suggests:
ii  gimp-data-extras  1:2.0.2-1
ii  gimp-help-en [gimp-help]  2.8.2-0.1
iu  gimp-python   2.10.6-1
pn  gvfs-backends 
ii  libasound21.1.6-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gimp
Source-Version: 2.10.6-2

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gimp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Aug 2018 17:47:28 -0400
Source: gimp
Binary: gimp gimp-data gimp-python libgimp2.0 libgimp2.0-dev libgimp2.0-doc
Architecture: source
Version: 2.10.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gimp   - GNU Image Manipulation Program
 gimp-data  - Data files for GIMP
 gimp-python - Python scripting support for GIMP
 libgimp2.0 - Libraries for 

Bug#906879: marked as done (security issue with the PASS command and duplicate server instances)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 22:26:24 +
with message-id 
and subject line Bug#906879: fixed in charybdis 4.1.1-1
has caused the Debian Bug report #906879,
regarding security issue with the PASS command and duplicate server instances
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.)


-- 
906879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: charybdis
Version: 4.1-1
Severity: grave
Tags: security

Upstream released Charybdis 4.0.1 and 4.1.1 fixing a security issue
which, apparently, is "with the PASS command and duplicate server
instances", at least according to the NEWS file:

https://github.com/charybdis-ircd/charybdis/blob/charybdis-4.1.1/NEWS.md

The hotfix seems to be:

https://github.com/charybdis-ircd/charybdis/commit/d4b2529a61fb48ebcd54bc0fcc6f400f97bfe251

And it seems like 3.x series (so stable and earlier) are not affected,
but I need to double-check that.

Upstream requested a CVE through the DWF but that process has
stalled. I recommended they go directly with MITRE or get an OVE, but
they instead generated the following UUID to track this issue:

a4c15999-a0b6-11e8-88af-00805fc181fe

Go figure...

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

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

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

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

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated charybdis 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: Tue, 21 Aug 2018 17:52:12 -0400
Source: charybdis
Binary: charybdis
Architecture: source
Version: 4.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 charybdis  - fast, scalable irc server
Closes: 906879
Changes:
 charybdis (4.1.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #906879).
Checksums-Sha1:
 bae9bc11dd76b9cb7226d5bb440748cfa002c32c 1777 charybdis_4.1.1-1.dsc
 854e491bca6c7cca91b931fd257e8cc93f6baf17 2691216 charybdis_4.1.1.orig.tar.gz
 6f058ad62a2712a57c33821319a539fec4b7a3e0 11776 charybdis_4.1.1-1.debian.tar.xz
 bb2ba8ad02d1ad9fb5642bcb457b544ae22a2b5f 5959 charybdis_4.1.1-1_amd64.buildinfo
Checksums-Sha256:
 a035388651d44d40ee9a6a288b33b3539ed007c63c7079332ce9573bf0366447 1777 
charybdis_4.1.1-1.dsc
 037eacaaf3076f60fc5ca6cfbad349f2d59694f788535f3b28e633529f56c2c1 2691216 
charybdis_4.1.1.orig.tar.gz
 782400e212c6d41abaf9a12b9eaabc082961882f57ce9872207c7f791a249e2b 11776 
charybdis_4.1.1-1.debian.tar.xz
 3b84d82bd26b5d68c074018623069a9769cfa39cb7a82334c2dd4774a08a6a9b 5959 
charybdis_4.1.1-1_amd64.buildinfo
Files:
 d865581e0d127f7b69e61cc7f3fffe0b 1777 net optional charybdis_4.1.1-1.dsc
 0aa13e596d0913cfb5dd117f42a2be59 2691216 net optional 
charybdis_4.1.1.orig.tar.gz
 c5259c1b996ed3b88dda590d3f9b23fb 11776 net optional 
charybdis_4.1.1-1.debian.tar.xz
 9ae8b26ddf7fb1e469113d1fda78915b 5959 net optional 
charybdis_4.1.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlt8itoACgkQPqHd3bJh
2Xs/UAf7BvSGqbsMoE6KNKVlnIJ3aFF3WixtNjQsGKNynyyZ0/zXy161f89Akf02
f/96+4qrw0x4XJMy8G9z3DUEfxE0dJsfau71QByUF/6fIPf3CQU4QZl9I/kenuN7
7KarJ9TCUcLrNrMC+VUs+G67ykZZlGQ8PYtNKD8QQwfWGQQP5quaupzoCrIo4n6x
d15GupHb9ijmrMeqFT5FIt3xBXlpaPW4M4Pg43EsJb3TVQvvDLEti7Qij/3thOlI
tz8LFG3Vtg1w+M2SimzH9eTwaVLT/NPVYlCDhZVlg9G1iNOBfAQpnFAIoMKyV2Xh
Y+/2rjSut94U0PCU3sAJUA6cDeVtnQ==
=P3Bd
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#906888: fdroidserver fails it's autopkg tests

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-libcloud
Bug #906888 [src:fdroidserver] fdroidserver fails it's autopkg tests
Bug reassigned from package 'src:fdroidserver' to 'python3-libcloud'.
No longer marked as found in versions fdroidserver/1.0.9-1.
Ignoring request to alter fixed versions of bug #906888 to the same values 
previously set
> forcemerge 903388 -1
Bug #903388 [python3-libcloud] Failure to install with Python 3.7
Bug #906888 [python3-libcloud] fdroidserver fails it's autopkg tests
Severity set to 'serious' from 'important'
902788 was blocked by: 903457 903145 904642 902757 905253 902794 902650 904587 
906159 904576 902631 904351 903528 904373 904381 903784 904357 903826 904298 
902900 904656 903016 904650 904350 903522 904365 902715 904492 902817 903031 
904367 904383 904653 904382 904644 904343 904615 904654 903526 904369 904358 
904390 903527 904361 904371 905213 904648 904888 904579 902989 903030 902761 
904581 904368 903558 902766 904491 904364 904388 903525 904363 904370 902646 
903388 903423 904453 903529 904389 904603 903218 904649 904657 903888
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 906888
Marked as found in versions libcloud/2.3.0-1.
Added tag(s) fixed-upstream.
Bug #903388 [python3-libcloud] Failure to install with Python 3.7
Added tag(s) sid and buster.
Merged 903388 906888
> affects -1 src:fdroidserver
Bug #906888 [python3-libcloud] fdroidserver fails it's autopkg tests
Bug #903388 [python3-libcloud] Failure to install with Python 3.7
Added indication that 906888 affects src:fdroidserver
Added indication that 903388 affects src:fdroidserver

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

Bug#906892: Bug #906892 in gimp marked as pending

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #906892 in gimp 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/gnome-team/gimp/commit/565a4d63aa9808839bd972cdceea9f94d424e74d


debian/gimp.install: Remove extra line which caused file conflict

Closes: #906892



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/906892

Processed: Bug #906892 in gimp marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906892 [gimp] gimp: file conflict with gimp-python
Added tag(s) pending.

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

Bug#906892: gimp: file conflict with gimp-python

[Adam Borowski]

Package: gimp
Version: 2.10.6-1
Severity: serious
Justification: fails to upgrade/install

Hi!
On upgrading:

Unpacking gimp (2.10.6-1) over (2.10.2-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-zHQiJC/10-gimp_2.10.6-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/gimp/2.0/plug-ins/colorxhtml/colorxhtml.py', 
which is also in package gimp-python 2.10.6-1

The file is present in the new version of gimp-python as well, thus a fresh
install would fail the same.


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

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

Versions of packages gimp depends on:
iu  gimp-data2.10.6-1
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-00.1.56-1
ii  libbz2-1.0   1.0.6-9
ii  libc62.27-5
ii  libcairo21.15.10-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.2.0-4
iu  libgdk-pixbuf2.0-0   2.36.12-2
ii  libgegl-0.4-00.4.8-1
ii  libgexiv2-2  0.10.8-1
iu  libgimp2.0   2.10.6-1
ii  libglib2.0-0 2.56.1-2
ii  libgs9   9.22~dfsg-2.1
iu  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b1.8.8-2
ii  libheif1 1.3.2-1
ii  libilmbase23 2.2.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  liblzma5 5.2.2-1.3
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2
ii  libopenexr23 2.2.1-4
ii  libopenjp2-7 2.3.0-1
ii  libpango-1.0-0   1.42.4-1
ii  libpangocairo-1.0-0  1.42.4-1
ii  libpangoft2-1.0-01.42.4-1
ii  libpng16-16  1.6.34-2
ii  libpoppler-glib8 0.63.0-2
ii  librsvg2-2   2.40.20-2
ii  libstdc++6   8.2.0-4
ii  libtiff5 4.0.9-6
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libwmf0.2-7  0.2.8.4-12
ii  libx11-6 2:1.6.5-1
ii  libxcursor1  1:1.1.15-1
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gimp recommends:
ii  ghostscript  9.22~dfsg-2.1

Versions of packages gimp suggests:
ii  gimp-data-extras  1:2.0.2-1
ii  gimp-help-en [gimp-help]  2.8.2-0.1
iu  gimp-python   2.10.6-1
pn  gvfs-backends 
ii  libasound21.1.6-1

-- no debconf information

Processed: severity of 906888 is important

[Debian Bug Tracking System]

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

> severity 906888 important
Bug #906888 [src:fdroidserver] fdroidserver fails it's autopkg tests
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 906844 src:protobuf
Bug #906844 [python3-protobuf] python3-protobuf: Installing 'python3-protobuf' 
causes uninstallation of 'python3-numpy'
Bug reassigned from package 'python3-protobuf' to 'src:protobuf'.
No longer marked as found in versions protobuf/3.0.0-9.1.
Ignoring request to alter fixed versions of bug #906844 to the same values 
previously set
> forcemerge 902597 906844
Bug #902597 {Done: Laszlo Boszormenyi (GCS) } [src:protobuf] 
protobuf ftbfs with python3.7 as a supported version
Bug #906844 [src:protobuf] python3-protobuf: Installing 'python3-protobuf' 
causes uninstallation of 'python3-numpy'
Marked Bug as done
Marked as fixed in versions protobuf/3.6.1-1.
Marked as found in versions protobuf/3.0.0-9.1.
Added tag(s) experimental, sid, and buster.
Merged 902597 906844
> affects 902597 python3-protobuf
Bug #902597 {Done: Laszlo Boszormenyi (GCS) } [src:protobuf] 
protobuf ftbfs with python3.7 as a supported version
Bug #906844 {Done: Laszlo Boszormenyi (GCS) } [src:protobuf] 
python3-protobuf: Installing 'python3-protobuf' causes uninstallation of 
'python3-numpy'
Added indication that 902597 affects python3-protobuf
Added indication that 906844 affects python3-protobuf
> thanks
Stopping processing here.

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

Bug#903362: marked as done (percol: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 21:06:53 +
with message-id 
and subject line Bug#903362: fixed in percol 0.2.1-2
has caused the Debian Bug report #903362,
regarding percol: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   dh_auto_build -i
dh_auto_build: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_build: This feature will be removed in compat 12.
python setup.py build --force
running build
running build_py
creating build

[... snipped ...]

python setup.py install --force --root=/<>/debian/percol 
--no-compile -O0 --install-layout=deb
running install
running build
running build_py
running build_scripts
running install_lib
creating /<>/debian/percol/usr
creating /<>/debian/percol/usr/lib
creating /<>/debian/percol/usr/lib/python2.7
creating /<>/debian/percol/usr/lib/python2.7/dist-packages
creating /<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/command.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/action.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/info.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/actions.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/tty.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/cli.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/lazyarray.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/finder.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/view.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/__init__.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/model.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/markup.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/key.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/debug.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/display.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/ansi.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
running install_egg_info
running egg_info
creating percol.egg-info
writing requirements to percol.egg-info/requires.txt
writing percol.egg-info/PKG-INFO
writing top-level names to percol.egg-info/top_level.txt
writing dependency_links to percol.egg-info/dependency_links.txt
writing manifest file 'percol.egg-info/SOURCES.txt'
reading manifest file 'percol.egg-info/SOURCES.txt'
writing manifest file 'percol.egg-info/SOURCES.txt'
Copying percol.egg-info to 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol-0.2.1.egg-info
Skipping SOURCES.txt
running install_scripts
creating /<>/debian/percol/usr/bin
copying build/scripts-2.7/percol -> /<>/debian/percol/usr/bin
changing mode of /<>/debian/percol/usr/bin/percol to 775
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my 

Processed: severity of 906890 is important

[Debian Bug Tracking System]

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

> severity 906890 important
Bug #906890 [src:dropbear] dropbear: CVE-2018-15599
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#906890: dropbear: CVE-2018-15599

[Salvatore Bonaccorso]

Source: dropbear
Version: 2016.74-1
Severity: grave
Tags: security
Forwarded: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2018q3/002108.html

Hi,

The following vulnerability was published for dropbear.

CVE-2018-15599[0]:
| The recv_msg_userauth_request function in svr-auth.c in Dropbear
| through 2018.76 is prone to a user enumeration vulnerability because
| username validity affects how fields in SSH_MSG_USERAUTH messages are
| handled, a similar issue to CVE-2018-15473 in an unrelated codebase.

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-15599
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15599
[1] http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2018q3/002108.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: Re: Bug#906840: libgd2 FTBFS: cannot find -lgd

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #906840 [src:libgd2] libgd2 FTBFS: cannot find -lgd
Added tag(s) patch.

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

Bug#906840: libgd2 FTBFS: cannot find -lgd

[Adrian Bunk]

Control: tags -1 patch

On Tue, Aug 21, 2018 at 06:52:27PM +0200, Helmut Grohne wrote:
>...
> | gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/include/libpng16  -I/usr/include/freetype2 -I/usr/include/libpng16  
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include -I/usr/include/x86_64-linux-gnu-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -fvisibility=hidden -c -o gdcmpgif.o 
> gdcmpgif.c
> | /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -fvisibility=hidden  -Wl,-z,relro 
> -Wl,-z,now -Wl,--as-needed -o gdcmpgif gdcmpgif.o -lgd  -lm   -lz  -lpng16 
> -lz  -lfreetype  -lfontconfig -lfreetype   -ljpeg  -lXpm -lX11 -L/usr/lib 
> -ltiff   -lwebp
> | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
> -fvisibility=hidden -Wl,-z -Wl,relro -Wl,-z -Wl,now -o gdcmpgif gdcmpgif.o  
> -Wl,--as-needed -lgd -lm -lpng16 -lz -lfontconfig 
> /usr/lib/x86_64-linux-gnu/libfreetype.so -ljpeg -lXpm -lX11 -L/usr/lib -ltiff 
> -lwebp
> | /usr/bin/ld: cannot find -lgd
> | collect2: error: ld returned 1 exit status
> | make[3]: *** [Makefile:810: gdcmpgif] Error 1
> | make[3]: Leaving directory '/<>/src'
> | make[2]: *** [Makefile:623: all] Error 2
> | make[2]: Leaving directory '/<>/src'
> | make[1]: *** [Makefile:419: all-recursive] Error 1
> | make[1]: Leaving directory '/<>'
> | dh_auto_build: make -j1 returned exit code 2
> | make: *** [debian/rules:23: build] Error 2
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
> 
> I suspect a relation to autotools being updated.

And the actual bug is the src/Makefile.am part of 
debian/patches/tests-make-a-little-change-for-autopkgtest.patch
that should be removed.

> Helmut

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#906888: fdroidserver fails it's autopkg tests

[Matthias Klose]

Package: src:fdroidserver
Version: 1.0.9-1
Severity: serious
Tags: sid buster

see
https://ci.debian.net/data/packages/unstable/amd64/f/fdroidserver/latest-autopkgtest/log.gz

autopkgtest: WARNING: package fdroidserver is not installed though it should be
command2 FAIL badpkg
blame: fdroidserver
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
autopkgtest [10:10:07]:  summary
command1 PASS
command2 FAIL badpkg
blame: fdroidserver
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.

Bug#897764: possible patch

[Hilko Bengen]

Control: tag -1 patch

Hi,

it turns out that the alignof macro can probably be replaced by a GCC
builtin. The attached patch does that. I am not committing this to Salsa
right away because I am not 100% sure that __alignof__ (t) is
functionally equivalent to the macro that has become illegal in GCC 8:

#define alignof(type)  offsetof (struct { char c; type x; }, x)

Cheers,
-Hilko
Index: guymager/md5.cpp
===
--- guymager.orig/md5.cpp
+++ guymager/md5.cpp
@@ -376,8 +376,7 @@ void MD5Append (t_pMD5Context pContext,
if (Len >= 64)
{
   #if !_STRING_ARCH_unaligned
- #define alignof(type)  offsetof (struct { char c; type x; }, x)
- #define UNALIGNED_P(p) (((size_t) p) % alignof (uint32_t) != 0)
+ #define UNALIGNED_P(p) (((size_t) p) % __alignof__ (uint32_t) != 0)
 
  if (UNALIGNED_P (pBuffer))
  {
Index: guymager/sha1.cpp
===
--- guymager.orig/sha1.cpp
+++ guymager/sha1.cpp
@@ -263,8 +263,7 @@ void SHA1Append (t_pSHA1Context pContext
if (len >= 64)
{
   #if !_STRING_ARCH_unaligned
- #define alignof(type) offsetof (struct { char c; type x; }, x)
- #define UNALIGNED_P(p) (((size_t) p) % alignof (uint32_t) != 0)
+ #define UNALIGNED_P(p) (((size_t) p) % __alignof__ (uint32_t) != 0)
  if (UNALIGNED_P (buffer))
 while (len > 64)
 {
Index: guymager/sha256.cpp
===
--- guymager.orig/sha256.cpp
+++ guymager/sha256.cpp
@@ -812,8 +812,7 @@ void SHA256Append (t_pSHA256Context pCon
if (len >= 64)
{
   #if !_STRING_ARCH_unaligned
- #define alignof(type) offsetof (struct { char c; type x; }, x)
- #define UNALIGNED_P(p) (((size_t) p) % alignof (uint32) != 0)
+ #define UNALIGNED_P(p) (((size_t) p) % __alignof__ (uint32) != 0)
  if (UNALIGNED_P (buffer))
  {
 while (len > 64)

Processed: possible patch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #897764 [src:guymager] guymager: ftbfs with GCC-8
Added tag(s) patch.

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

Processed: Re: dico: FTBFS in buster/sid (makeinfo: command not found)

[Debian Bug Tracking System]

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

> reassign 906744 php-yaml 2.0.2+1.3.1-2
Bug #906744 [automake] /usr/lib/php/20151012/yaml.so: cannot open shared object 
file
Bug reassigned from package 'automake' to 'php-yaml'.
Ignoring request to alter found versions of bug #906744 to the same values 
previously set
Ignoring request to alter fixed versions of bug #906744 to the same values 
previously set
Bug #906744 [php-yaml] /usr/lib/php/20151012/yaml.so: cannot open shared object 
file
Marked as found in versions php-yaml/2.0.2+1.3.1-2.
> quit
Stopping processing here.

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

Bug#906769: arm kernels fail to boot

[Salvatore Bonaccorso]

Hi

I have put in

https://people.debian.org/~carnil/tmp/linux/arm64/
https://people.debian.org/~carnil/tmp/linux/armel/
[https://people.debian.org/~carnil/tmp/linux/all/]

built packages available for testing. armhf builds are at the time of
writing not yet done, but can put those there as well.

If you were experiencing the issue, please test those and report back
if they fix the issue.

Regards,
Salvatore

Processed: tagging 906769

[Debian Bug Tracking System]

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

> tags 906769 + pending
Bug #906769 [src:linux] arm kernels fail to boot
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#906887: xul-ext-automatic-save-folder no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-automatic-save-folder
Version: 1.0.5~20140831-4
Severity: serious

XUL addons are no longer supported. 

Bug#906811: FTBFS: libconfig.h: No such file or directory

[Andreas Tille]

Control: tags -1 pending

The issue can be fixed by

   Build-Depends: libpbdata-dev

which is done in Git[1].  However there is a new upstream version and
I intend to upload this one instead of fixing old code.  Since the
build system has changed there is some additional work to do.

Thanks for reporting this bug

Andreas.

[1] https://salsa.debian.org/med-team/blasr

-- 
http://fam-tille.de

Processed: Re: Bug#906811: FTBFS: libconfig.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #906811 [src:blasr] FTBFS: libconfig.h: No such file or directory
Added tag(s) pending.

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

Bug#905179: marked as done (apticron: prompting due to modified conffiles which were not modified by the user: /etc/apticron/apticron.conf)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 19:34:09 +
with message-id 
and subject line Bug#905179: fixed in apticron 1.2.1
has caused the Debian Bug report #905179,
regarding apticron: prompting due to modified conffiles which were not modified 
by the user: /etc/apticron/apticron.conf
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.)


-- 
905179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apticron
Version: 1.2.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up apticron (1.2.0) ...
  
  Configuration file '/etc/apticron/apticron.conf'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** apticron.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
apticron (--configure):
   end of file on stdin at conffile prompt
  Setting up libgssapi-krb5-2:amd64 (1.16-2) ...
  Processing triggers for libc-bin (2.27-5) ...
  Errors were encountered while processing:
   apticron


cheers,

Andreas


apticron_1.2.0.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apticron
Source-Version: 1.2.1

We believe that the bug you reported is fixed in the latest version of
apticron, 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.
Tiago Bortoletto Vaz  (supplier of updated apticron 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: Tue, 21 Aug 2018 12:19:31 -0400
Source: apticron
Binary: apticron apticron-systemd
Architecture: source all
Version: 1.2.1
Distribution: unstable
Urgency: medium
Maintainer: Tiago Bortoletto Vaz 
Changed-By: Tiago Bortoletto Vaz 
Description:
 apticron   - Simple tool to mail about pending package updates - cron version
 apticron-systemd - Simple tool to mail about pending package updates - systemd 
versi
Closes: 879275 905179
Changes:
 apticron (1.2.1) unstable; urgency=medium
 .
   * Stateless configuration back. Thanks to Gioele Barabucci. (Closes: #879275)
   * Fix prompting not modified conffiles. Thanks to Andreas Beckmann.
 (Closes: #905179)
Checksums-Sha1:
 71af90010d714073b0bcc26ea0dbe599229f5106 1602 apticron_1.2.1.dsc
 5a0e1788b18105d1b8fba454faa14b31328b4b20 20124 apticron_1.2.1.tar.xz
 8845cbe34ba1f042b714eeaa8044633821ef0a1b 17280 apticron-systemd_1.2.1_all.deb
 445c62a7c7fce1bd477087cdbf2144c43f0e08cf 18804 apticron_1.2.1_all.deb
 99f0073859d7b45f3d13aea959991600055658e5 5810 apticron_1.2.1_amd64.buildinfo
Checksums-Sha256:
 ad2a93b75ecf694d2efa3fdbac24261626f202cbe78a8019f1bc1e726d2d8f47 1602 
apticron_1.2.1.dsc
 46bcd2d1726d2dbf73a24aa21303ec358d0d28fb0db54adf73be9ad9c62127b3 20124 
apticron_1.2.1.tar.xz
 

Bug#906744: dico: FTBFS in buster/sid (makeinfo: command not found)

[أحمد المحمودي]

reassign 906744 php-yaml/2.0.2+1.3.1-2
quit

Sorry commented to wrong bug number

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#906879: security issue with the PASS command and duplicate server instances

[Antoine Beaupre]

Source: charybdis
Version: 4.1-1
Severity: grave
Tags: security

Upstream released Charybdis 4.0.1 and 4.1.1 fixing a security issue
which, apparently, is "with the PASS command and duplicate server
instances", at least according to the NEWS file:

https://github.com/charybdis-ircd/charybdis/blob/charybdis-4.1.1/NEWS.md

The hotfix seems to be:

https://github.com/charybdis-ircd/charybdis/commit/d4b2529a61fb48ebcd54bc0fcc6f400f97bfe251

And it seems like 3.x series (so stable and earlier) are not affected,
but I need to double-check that.

Upstream requested a CVE through the DWF but that process has
stalled. I recommended they go directly with MITRE or get an OVE, but
they instead generated the following UUID to track this issue:

a4c15999-a0b6-11e8-88af-00805fc181fe

Go figure...

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

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

Processed: affects 899309

[Debian Bug Tracking System]

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

> affects 899309 xul-ext-autofill-forms
Bug #899309 [src:autofill-forms] autofill-forms: Replace it with non legacy 
autofillforms-e10 to be compatible with ff 60.
Added indication that 899309 affects xul-ext-autofill-forms
> thanks
Stopping processing here.

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

Bug#906000: marked as done (etckeeper: missing dependency on python)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 19:04:10 +
with message-id 
and subject line Bug#906000: fixed in etckeeper 1.18.8-1
has caused the Debian Bug report #906000,
regarding etckeeper: missing dependency on python
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.)


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

etckeeper installs a Python module but no longer
has a python dependency.
--- End Message ---
--- Begin Message ---
Source: etckeeper
Source-Version: 1.18.8-1

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

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

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated etckeeper 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: Tue, 21 Aug 2018 12:27:05 -0400
Source: etckeeper
Binary: etckeeper
Architecture: source
Version: 1.18.8-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 etckeeper  - store /etc in git, mercurial, bzr or darcs
Closes: 850679 906000
Changes:
 etckeeper (1.18.8-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #850679)
   * Revert port to py3, requires bzrlib to port first (Closes: #906000)
   * update standards version, no change
Checksums-Sha1:
 16714fd913018b96898e1b021bb63ef5a8c32846 1594 etckeeper_1.18.8-1.dsc
 ab0c534014887e3198b98c9bdebf72149e4ee9e6 84964 etckeeper_1.18.8.orig.tar.gz
 bd6a892184ffb36add8064f5854d994dccf02c2a 22704 etckeeper_1.18.8-1.debian.tar.xz
 1c5abb9d531d7466d16cb5698c95fb4b53c721b7 6934 
etckeeper_1.18.8-1_source.buildinfo
Checksums-Sha256:
 7200c6869a3e74302268205678dae8606a33fe5d32f3a0dc80264860ad590173 1594 
etckeeper_1.18.8-1.dsc
 97ba6908399a877b749e9137b9b71ada6db1373695da1bd646c5825e7c17d08e 84964 
etckeeper_1.18.8.orig.tar.gz
 04b049de797bc69e4e7a324e710908d35041bbb03067e6307a0c72caf2ab6152 22704 
etckeeper_1.18.8-1.debian.tar.xz
 24445ec7e130109fd2bfbe597a6620162dda6ce4c8253868bf3e6f4252202ee3 6934 
etckeeper_1.18.8-1_source.buildinfo
Files:
 57a74053f731d25db173f7f8047a1007 1594 admin optional etckeeper_1.18.8-1.dsc
 d3ce4568868324af81ed8c46f9a5d3eb 84964 admin optional 
etckeeper_1.18.8.orig.tar.gz
 0c69ba90daeee352422b1be0a4f9a1f9 22704 admin optional 
etckeeper_1.18.8-1.debian.tar.xz
 006737599727fb2fafea087b04d60cc3 6934 admin optional 
etckeeper_1.18.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCAAxFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlt8XeQTHGFuYXJjYXRA
ZGViaWFuLm9yZwAKCRA+od3dsmHZe77VCACng9810IOOX4FEsLxr18JBaFZvkCKl
25FuAmXosCo1rz2hChCC9h2sRjcwPT0znvy0/VDGBOI3hgYGDdiXIX3J6n4TbZVh
mP0PPcX91zDuB1l9yZyQBTLJItUivCeCjeTjuDqOVaRvp6grU1TfZJHkIvSv9fak
hphAYalL+2Yt/5kL9ZexzYdSUlSTSqahussfLE8zOh7MmAyKVvHkKKYxyRz6pB+7
PA8cRciw9Mgw7WHa3Jg3nc6D1uOpKUKdm/LVnY01zBJqgX3eRLhGCRmTGNnFvckE
YvHroSCE16K4CiDBB4VF47EARa5sbbGFJVeC7P/yYdSV6eOmV6p2dMc9
=bBx6
-END PGP SIGNATURE End Message ---

Bug#906746: marked as done (freeorion FTBFS on armel/armhf: virtual memory exhausted: Cannot allocate memory)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 19:04:23 +
with message-id 
and subject line Bug#906746: fixed in freeorion 0.4.8~RC2-2
has caused the Debian Bug report #906746,
regarding freeorion FTBFS on armel/armhf: virtual memory exhausted: Cannot 
allocate 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.)


-- 
906746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeorion
Version: 0.4.8~RC2-1
Severity: serious
Tags: ftbfs patch

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

...
[ 18%] Building CXX object 
CMakeFiles/freeorionparseobj.dir/parse/ValueRefParser.cpp.o
/usr/bin/c++  -DBINPATH=\"/usr/bin\" -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LINK 
-DBOOST_OPTIONAL_CONFIG_USE_OLD_IMPLEMENTATION_OF_OPTIONAL -DENABLE_BINRELOC 
-DFREEORION_BUILD_PARSE -DFREEORION_LINUX -DNDEBUG -DSHAREPATH=\"/usr/share\" 
-isystem "/<>/GG"  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Os -DNDEBUG -fPIC   -Wall -fvisibility=hidden -O3 
-std=c++11 -o CMakeFiles/freeorionparseobj.dir/parse/ValueRefParser.cpp.o -c 
"/<>/parse/ValueRefParser.cpp"
virtual memory exhausted: Cannot allocate memory


Changes in the patch below:
- less debug info (-g1) on all 32bit architectures except i386
- optimizing for size instead of speed with -Os (MinSizeRel)
  does not help with this kind of problems, "Release" is
  appropriate to make cmake not overwrite the added -gq
- build on linux-any

With these changes the build succeeded on armel and mips,
which should cover this kind of problems for all
release architectures.

--- debian/control.old  2018-08-19 19:31:03.498132567 +
+++ debian/control  2018-08-19 20:09:50.782947393 +
@@ -30,7 +30,7 @@
 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-games/freeorion.git
 
 Package: freeorion
-Architecture: alpha amd64 arm64 armel armhf hppa i386 mips64el powerpc ppc64 
ppc64el s390x sparc64 x32
+Architecture: linux-any
 Depends:
  freeorion-data (= ${source:Version}),
  ${misc:Depends},
--- debian/rules.old2018-08-19 19:21:28.459317241 +
+++ debian/rules2018-08-19 19:50:26.455475862 +
@@ -4,14 +4,17 @@
 export CCACHE_DIR=$(CURDIR)/ccache
 DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
-WEAK_HOSTS := armel armhf
 
-ifneq (,$(findstring $(DEB_HOST_ARCH),$(WEAK_HOSTS)))
+MAX  := 2
+TYPE := RelWithDebInfo
+
+ifeq (32,$(DEB_HOST_ARCH_BITS))
+ifeq (,$(filter $(DEB_HOST_ARCH), i386))
MAX  := 1
-   TYPE := MinSizeRel
-else
-   MAX  := 2
-   TYPE := RelWithDebInfo
+   TYPE := Release
+   export DEB_CFLAGS_MAINT_APPEND = -g1
+   export DEB_CXXFLAGS_MAINT_APPEND = -g1
+endif
 endif
 
 %:
--- End Message ---
--- Begin Message ---
Source: freeorion
Source-Version: 0.4.8~RC2-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Aug 2018 19:48:02 +0200
Source: freeorion
Binary: freeorion freeorion-data
Architecture: source
Version: 0.4.8~RC2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 freeorion  - turn-based space empire and galactic conquest game
 freeorion-data - turn-based space empire and galactic conquest game -- data
Closes: 906746
Changes:
 freeorion (0.4.8~RC2-2) unstable; urgency=medium
 .
   * Replace dh_install --fail-missing with dh_missing --fail-missing.
   * Declare compliance with Debian Policy 4.2.0.
   * Fix memory exhaustion issues on 32bit architectures.
 - less debug info (-g1) on all 32bit architectures except i386
 - optimizing for size instead of speed with -Os (MinSizeRel)
   does not help with this kind of problems, "Release" is
   appropriate to make cmake not 

Processed: affects 864827

[Debian Bug Tracking System]

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

> affects 864827 xul-ext-zotero
Bug #864827 [zotero-standalone] [zotero-standalone] No longer works with 
firefox 54 update
Added indication that 864827 affects xul-ext-zotero
> thanks
Stopping processing here.

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

Bug#904870: marked as done (autopkgtest: calls su with an empty username, thus fails)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 20:57:37 +0200
with message-id <09a5d4a6-f993-3c7c-7440-47093ea7e...@debian.org>
and subject line Re: Bug#904870: fixed in autopkgtest 5.4.2?
has caused the Debian Bug report #904870,
regarding autopkgtest: calls su with an empty username, thus fails
to be marked as done.

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

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


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

Dear autopkgtest Maintainers,

In various situations autopkgtest calls /bin/su with an empty string for
the username. The old su (from login) ignored this, but newer su
versions (from util-linux 2.32-0.2) do not accept this, and abort.
Personally I think autopkgtest got lucky that this worked before, but
this probably was not a valid thing to do.

One of the affected lines:
   https://sources.debian.org/src/autopkgtest/5.4.1/lib/adt_testbed.py/#L1096

Example output from autopkgtest:

   autopkgtest [15:52:36]: test supported-algos: [---
   su: user  does not exist
   autopkgtest [15:52:36]: test supported-algos: ---]
   Unexpected error:
   Traceback (most recent call last):
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
   command()
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
   r = f(c, ce)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
   copyupdown(c, ce, True)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
   copyupdown_internal(ce[0], c[1:], upp)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
copyupdown_internal
   copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
copyup_shareddir
   shutil.copy(tb, host)
 File "/usr/lib/python3.6/shutil.py", line 241, in copy
   copyfile(src, dst, follow_symlinks=follow_symlinks)
 File "/usr/lib/python3.6/shutil.py", line 120, in copyfile
   with open(src, 'rb') as fsrc:
   FileNotFoundError: [Errno 2] No such file or directory: 
'/tmp/autopkgtest.zwqy11/supported-algos-stdout'
   autopkgtest [15:52:36]: ERROR: testbed failure: cannot send to testbed: 
[Errno 32] Broken pipe
   autopkgtest [15:52:36]: Binaries: resetting testbed apt configuration

Note that tests that say "Restrictions: needs-root" do not appear to hit
those code paths.

I might try to come up with a patch if no one beats me to it.

Chris
--- End Message ---
--- Begin Message ---
Version: 5.4.2

On 21-08-18 14:23, Nicholas D Steeves wrote:
> Control: reopen -1

> I ran into this just now with autopkgtest 5.5 (inside LXC, or schroot)
> when the host system is using either 4.4 or 5.4.1~bpo9+2.

Yes, the bug is still present in 4.4 and 5.4.1~bpo9+2 as the BTS will
happily tell you. It is the host autopkgtest that provides the commands.
autopkgtest inside the LXC or whatever doesn't do anything and is
completely useless to have that installed, unless you are testing
autopkgtest itself or need it as a dependency for you test.

> Will this be solved if 5.5 is backported?

If you update the host to use that, yes.

> As a consequence, does this
> also mean all stretch systems with sid autopkgtest chroots must switch
> to using backported autopkgtests?

I guess so. There is nothing we can do about that. But it is good that
you remind us of the missing backports. I'll try to upload it tonight.

Paul



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#906876: xul-ext-scrapbook no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-scrapbook
Version: 1.5.13-3
Severity: serious

XUL addons are no longer supported. 

Bug#906878: xul-ext-sage no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-sage
Version: 1.5.4-2
Severity: serious

XUL addons are no longer supported. 

Processed: Re: dico: FTBFS in buster/sid (makeinfo: command not found)

[Debian Bug Tracking System]

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

> reassign 906774 automake
Bug #906774 [src:dico] dico: FTBFS in buster/sid (makeinfo: command not found)
Bug reassigned from package 'src:dico' to 'automake'.
No longer marked as found in versions dico/2.5-1.
Ignoring request to alter fixed versions of bug #906774 to the same values 
previously set
> quit
Stopping processing here.

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

Bug#906774: dico: FTBFS in buster/sid (makeinfo: command not found)

[أحمد المحمودي]

reassign 906774 automake
quit

  geda-gaf and dico FTBFS on Debian after automake got updated to 1.16, 
  as the following happens during build[2]:

 Making all in scheme-api
 make[4]: Entering directory '/<>/docs/scheme-api'
 Updating ./version.texi
 make[4]: Leaving directory '/<>/docs/scheme-api'

  which later triggers rebuild of info files during 'make check':

> Making check in doc
> make[3]: Entering directory '/<>/doc'
> restore=: && backupdir=".am$$" && \
> am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
> rm -rf $backupdir && mkdir $backupdir && \
> if (/bin/bash /<>/build-aux/missing makeinfo --version) 
> >/dev/null 2>&1; then \
>   for f in dico.info dico.info-[0-9] dico.info-[0-9][0-9] dico.i[0-9] 
> dico.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>   done; \
> else :; fi && \
> cd "$am__cwd"; \
> if /bin/bash /<>/build-aux/missing makeinfo -I ../imprimatur -D 
> DISTRIB  -I . \
>  -o dico.info dico.texi; \
> then \
>   rc=0; \
>   CDPATH="${ZSH_VERSION+.}:" && cd .; \
> else \
>   rc=$?; \
>   CDPATH="${ZSH_VERSION+.}:" && cd . && \
>   $restore $backupdir/* `echo "./dico.info" | sed 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; exit $rc
> /<>/build-aux/missing: line 81: makeinfo: command not found
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> make[3]: *** [Makefile:1263: dico.info] Error 127

  Adding texinfo to build-dep would get around the FTBFS, but I 
  am not convinced with it. Could you advise me us as whether this is a 
  problem in automake 1.16 or something needs to be fixed in dico & 
  geda-gaf build scripts, or if adding texinfo to build-deps is actually 
  the proper way to go ?

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Processed: Bug #906746 in freeorion marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906746 [src:freeorion] freeorion FTBFS on armel/armhf: virtual memory 
exhausted: Cannot allocate memory
Added tag(s) pending.

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

Bug#906746: Bug #906746 in freeorion marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #906746 in freeorion 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/games-team/freeorion/commit/1c08143ca2784ddfe72a2906dfd3915ec6b8b6e5


Fix memory exhaustion issues on 32bit architectures.

Changes in the patch below:
- less debug info (-g1) on all 32bit architectures except i386
- optimizing for size instead of speed with -Os (MinSizeRel)
  does not help with this kind of problems, "Release" is
  appropriate to make cmake not overwrite the added -gq
- build on linux-any

Closes: #906746
Thanks: Adrian Bunk for the report and patch.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/906746

Processed: severity of 769441 is serious

[Debian Bug Tracking System]

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

> severity 769441 serious
Bug #769441 [xul-ext-monkeysphere] Does not work with Iceweasel 33
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#906875: xul-ext-lyz no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-lyz
Version: 2.1.5-3-g895ff3a-1
Severity: serious

XUL addons are no longer supported. 

Processed: xul-ext-https-everywhere no longer works with firefox-esr 60

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2018.1.29-1
Bug #906874 [xul-ext-https-everywhere] xul-ext-https-everywhere no longer works 
with firefox-esr 60
Marked as fixed in versions https-everywhere/2018.1.29-1.
> close -1
Bug #906874 [xul-ext-https-everywhere] xul-ext-https-everywhere no longer works 
with firefox-esr 60
Marked Bug as done

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

Bug#906874: xul-ext-https-everywhere no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-https-everywhere
Version: 5.2.8-1
Severity: serious
Control: fixed -1 2018.1.29-1
Control: close -1

XUL addons are no longer supported. 

This is already fixed in unstable.

Bug#906872: xul-ext-flashgot no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-flashgot
Version: 1.5.6.13+dfsg-1
Severity: serious

XUL addons are no longer supported. 

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906871: xul-ext-flashblock no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-flashblock
Version: 1.5.20-2
Severity: serious

XUL addons are no longer supported.

Bug#906363: marked as done (hdmi2usb-fx2-firmware: FTBFS in buster/sid (extern definition for 'putchar' mismatches with declaration.))

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 18:34:43 +
with message-id 
and subject line Bug#906363: fixed in hdmi2usb-fx2-firmware 0.0.0~git20151225-2
has caused the Debian Bug report #906363,
regarding hdmi2usb-fx2-firmware: FTBFS in buster/sid (extern definition for 
'putchar' mismatches with declaration.)
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.)


-- 
906363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hdmi2usb-fx2-firmware
Version: 0.0.0~git20151225-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
make -C lib
make[2]: Entering directory '/<>/lib'
sdcc -mmcs51  -I../include -c serial.c -o serial.rel
sdcc -mmcs51  -I../include -c i2c.c -o i2c.rel
sdcc -mmcs51  -I../include -c delay.c -o delay.rel
sdcc -mmcs51  -I../include -c setupdat.c -o setupdat.rel
sdcc -mmcs51  -I../include -c gpif.c -o gpif.rel

[... snipped ...]

sdcc -mmcs51  -I../include -c interrupts/ep2_isr.c -o interrupts/ep2_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep0ping_isr.c -o 
interrupts/ep0ping_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep4isoerr_isr.c -o 
interrupts/ep4isoerr_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep2pf_isr.c -o interrupts/ep2pf_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep1in_isr.c -o interrupts/ep1in_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep8ping_isr.c -o 
interrupts/ep8ping_isr.rel
sdcc -mmcs51  -I../include -c interrupts/sof_isr.c -o interrupts/sof_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep0ack_isr.c -o 
interrupts/ep0ack_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep2ef_isr.c -o interrupts/ep2ef_isr.rel
sdcc -mmcs51  -I../include -c interrupts/sudav_isr.c -o interrupts/sudav_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep2ff_isr.c -o interrupts/ep2ff_isr.rel
sdcc -mmcs51  -I../include -c interrupts/sutok_isr.c -o interrupts/sutok_isr.rel
sdcc -mmcs51  -I../include -c interrupts/hispeed_isr.c -o 
interrupts/hispeed_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep2isoerr_isr.c -o 
interrupts/ep2isoerr_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep4ef_isr.c -o interrupts/ep4ef_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ibn_isr.c -o interrupts/ibn_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep8pf_isr.c -o interrupts/ep8pf_isr.rel
sdcc -mmcs51  -I../include -c interrupts/suspend_isr.c -o 
interrupts/suspend_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep6ping_isr.c -o 
interrupts/ep6ping_isr.rel
sdcc -mmcs51  -I../include -c interrupts/ep4ping_isr.c -o 
interrupts/ep4ping_isr.rel
sdas8051 -logs usbav.a51
sdcclib fx2.lib serial.rel i2c.rel delay.rel setupdat.rel gpif.rel eputils.rel 
interrupts/spare_isr.rel interrupts/usbreset_isr.rel interrupts/ep6_isr.rel 
interrupts/ep6ef_isr.rel interrupts/ep0out_isr.rel interrupts/ep6ff_isr.rel 
interrupts/ep1ping_isr.rel interrupts/ep1out_isr.rel interrupts/ep4ff_isr.rel 
interrupts/errlimit_isr.rel interrupts/ep8isoerr_isr.rel 
interrupts/gpifwf_isr.rel interrupts/ep4_isr.rel interrupts/ep6isoerr_isr.rel 
interrupts/gpifdone_isr.rel interrupts/ep8ef_isr.rel interrupts/ep6pf_isr.rel 
interrupts/ep8_isr.rel interrupts/ep4pf_isr.rel interrupts/ep2ping_isr.rel 
interrupts/ep8ff_isr.rel interrupts/ep0in_isr.rel interrupts/ep2_isr.rel 
interrupts/ep0ping_isr.rel interrupts/ep4isoerr_isr.rel 
interrupts/ep2pf_isr.rel interrupts/ep1in_isr.rel interrupts/ep8ping_isr.rel 
interrupts/sof_isr.rel interrupts/ep0ack_isr.rel interrupts/ep2ef_isr.rel 
interrupts/sudav_isr.rel interrupts/ep2ff_isr.rel interrupts/sutok_isr.rel 
interrupts/hispeed_isr.rel interrupts/ep2isoer
 r_isr.rel interrupts/ep4ef_isr.rel interrupts/ibn_isr.rel 
interrupts/ep8pf_isr.rel interrupts/suspend_isr.rel interrupts/ep6ping_isr.rel 
interrupts/ep4ping_isr.rel usbav.rel
make[2]: Leaving directory '/<>/lib'
make -C examples
make[2]: Entering directory '/<>/examples'
make -C bulkloop 
make[3]: Entering directory '/<>/examples/bulkloop'
mkdir -p build
for a in dscr.a51; do \
 cp $a build/; \
 cd build && sdas8051 -logs `basename $a` && cd ..; done
for s in bulkloop.c; do \
 THISREL=$(basename `echo "$s" | sed -e 's/\.c$/\.rel/'`); \
 sdcc -mmcs51  --code-size 0x3c00 --xram-size 0x0200 --xram-loc 0x3c00 -Wl"-b 
DSCR_AREA=0x3e00" -Wl"-b 

Bug#896389: marked as done (python3-future: depend on python3-lib2to3)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 18:35:54 +
with message-id 
and subject line Bug#896216: fixed in python-future 0.15.2-5
has caused the Debian Bug report #896216,
regarding python3-future: depend on python3-lib2to3
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.)


-- 
896216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-autoindex
Version: 0.6+0git20160725-02b454-6
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-flask-autoindex importing the module flask_autoindex
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_autoindex/__init__.py", line 22, 
in 
from .entry import *
  File "/usr/lib/python3/dist-packages/flask_autoindex/entry.py", line 1, in 

from past.builtins import cmp
  File "/usr/lib/python3/dist-packages/past/__init__.py", line 88, in 
from past.translation import install_hooks as autotranslate
  File "/usr/lib/python3/dist-packages/past/translation/__init__.py", line 41, 
in 
from lib2to3.pgen2.parse import ParseError
ModuleNotFoundError: No module named 'lib2to3'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-future
Source-Version: 0.15.2-5

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-future package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Aug 2018 20:06:43 +0200
Source: python-future
Binary: python-future python3-future python-future-doc
Architecture: source all
Version: 0.15.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-future - single-source support for Python 3 and 2 - Python 2.x
 python-future-doc - Clean single-source support for Python 3 and 2 - doc
 python3-future - Clean single-source support for Python 3 and 2 - Python 3.x
Closes: 870038 896216
Changes:
 python-future (0.15.2-5) unstable; urgency=medium
 .
   * Team upload.
   * Bump required version of dh-python because test autodetection is
 not working in older versions
   * Bumped debhelper compat version to 11
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * Convert git repository from git-dpm to gbp layout
   * Add python3-lib2to3 to depends (Closes: #896216)
   * d/*.postinst: Prefer Python 3 version if both versions installed
 (Closes: #870038)
   * Add Python 3.7 support
   * Standards version is 4.2.0 now (no changes)
Checksums-Sha1:
 53d13a3831b0a6f252807cb035a66779a81405b7 2397 python-future_0.15.2-5.dsc
 599dd8dfa58e04abbfdfe862fd13d04929ff2ca3 10888 
python-future_0.15.2-5.debian.tar.xz
 d8944a3367ce257bf157ad669c1cfda21bb88812 323156 
python-future-doc_0.15.2-5_all.deb
 a8b78f689dcf4e6b66ae0697168ee35ae82745d2 347160 python-future_0.15.2-5_all.deb
 e59d766781b5f7441f3ebb6b56b0340da57023d1 8692 
python-future_0.15.2-5_amd64.buildinfo
 8a5fe7b379f88ade47c444072f4199d5c242bdb5 345404 python3-future_0.15.2-5_all.deb
Checksums-Sha256:
 12e4a72ced834e619c7c8415ad43850c86b3931ec426ec2354dada493027909e 2397 
python-future_0.15.2-5.dsc
 7937eb7dfec078327cd980a99aa3d2645819dd753307748b2558303e316d 10888 
python-future_0.15.2-5.debian.tar.xz
 b56b80b2c330700ae8999ae8e76dfc731ebdc72007ef17bb06a4e5ee8e52c0a6 323156 
python-future-doc_0.15.2-5_all.deb
 

Bug#896216: marked as done (python3-future: depend on python3-lib2to3)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 18:35:54 +
with message-id 
and subject line Bug#896216: fixed in python-future 0.15.2-5
has caused the Debian Bug report #896216,
regarding python3-future: depend on python3-lib2to3
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.)


-- 
896216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pytest-cookies
Version: 0.3.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-pytest-cookies importing the module pytest_cookies
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pytest_cookies.py", line 6, in 
from cookiecutter.main import cookiecutter
  File "/usr/lib/python3/dist-packages/cookiecutter/main.py", line 15, in 

from .generate import generate_context, generate_files
  File "/usr/lib/python3/dist-packages/cookiecutter/generate.py", line 27, in 

from .hooks import run_hook
  File "/usr/lib/python3/dist-packages/cookiecutter/hooks.py", line 13, in 

from cookiecutter import utils
  File "/usr/lib/python3/dist-packages/cookiecutter/utils.py", line 19, in 

from .prompt import read_user_yes_no
  File "/usr/lib/python3/dist-packages/cookiecutter/prompt.py", line 14, in 

from past.builtins import basestring
  File "/usr/lib/python3/dist-packages/past/__init__.py", line 88, in 
from past.translation import install_hooks as autotranslate
  File "/usr/lib/python3/dist-packages/past/translation/__init__.py", line 41, 
in 
from lib2to3.pgen2.parse import ParseError
ModuleNotFoundError: No module named 'lib2to3'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-future
Source-Version: 0.15.2-5

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-future package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Aug 2018 20:06:43 +0200
Source: python-future
Binary: python-future python3-future python-future-doc
Architecture: source all
Version: 0.15.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-future - single-source support for Python 3 and 2 - Python 2.x
 python-future-doc - Clean single-source support for Python 3 and 2 - doc
 python3-future - Clean single-source support for Python 3 and 2 - Python 3.x
Closes: 870038 896216
Changes:
 python-future (0.15.2-5) unstable; urgency=medium
 .
   * Team upload.
   * Bump required version of dh-python because test autodetection is
 not working in older versions
   * Bumped debhelper compat version to 11
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * Convert git repository from git-dpm to gbp layout
   * Add python3-lib2to3 to depends (Closes: #896216)
   * d/*.postinst: Prefer Python 3 version if both versions installed
 (Closes: #870038)
   * Add Python 3.7 support
   * Standards version is 4.2.0 now (no changes)
Checksums-Sha1:
 53d13a3831b0a6f252807cb035a66779a81405b7 2397 python-future_0.15.2-5.dsc
 599dd8dfa58e04abbfdfe862fd13d04929ff2ca3 10888 
python-future_0.15.2-5.debian.tar.xz
 d8944a3367ce257bf157ad669c1cfda21bb88812 323156 
python-future-doc_0.15.2-5_all.deb
 a8b78f689dcf4e6b66ae0697168ee35ae82745d2 347160 python-future_0.15.2-5_all.deb
 e59d766781b5f7441f3ebb6b56b0340da57023d1 8692 

Bug#896597: marked as done (python3-future: depend on python3-lib2to3)

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 18:35:54 +
with message-id 
and subject line Bug#896216: fixed in python-future 0.15.2-5
has caused the Debian Bug report #896216,
regarding python3-future: depend on python3-lib2to3
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.)


-- 
896216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-future
Version: 0.15.2-4
Severity: serious
Tags: sid buster patch

lib2to3 now lives in it's own package. python3-future needs a dependency pn
python3-lib2to3.

patch at
https://patches.ubuntu.com/p/python-future/python-future_0.15.2-4ubuntu2.patch
--- End Message ---
--- Begin Message ---
Source: python-future
Source-Version: 0.15.2-5

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-future package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Aug 2018 20:06:43 +0200
Source: python-future
Binary: python-future python3-future python-future-doc
Architecture: source all
Version: 0.15.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-future - single-source support for Python 3 and 2 - Python 2.x
 python-future-doc - Clean single-source support for Python 3 and 2 - doc
 python3-future - Clean single-source support for Python 3 and 2 - Python 3.x
Closes: 870038 896216
Changes:
 python-future (0.15.2-5) unstable; urgency=medium
 .
   * Team upload.
   * Bump required version of dh-python because test autodetection is
 not working in older versions
   * Bumped debhelper compat version to 11
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * Convert git repository from git-dpm to gbp layout
   * Add python3-lib2to3 to depends (Closes: #896216)
   * d/*.postinst: Prefer Python 3 version if both versions installed
 (Closes: #870038)
   * Add Python 3.7 support
   * Standards version is 4.2.0 now (no changes)
Checksums-Sha1:
 53d13a3831b0a6f252807cb035a66779a81405b7 2397 python-future_0.15.2-5.dsc
 599dd8dfa58e04abbfdfe862fd13d04929ff2ca3 10888 
python-future_0.15.2-5.debian.tar.xz
 d8944a3367ce257bf157ad669c1cfda21bb88812 323156 
python-future-doc_0.15.2-5_all.deb
 a8b78f689dcf4e6b66ae0697168ee35ae82745d2 347160 python-future_0.15.2-5_all.deb
 e59d766781b5f7441f3ebb6b56b0340da57023d1 8692 
python-future_0.15.2-5_amd64.buildinfo
 8a5fe7b379f88ade47c444072f4199d5c242bdb5 345404 python3-future_0.15.2-5_all.deb
Checksums-Sha256:
 12e4a72ced834e619c7c8415ad43850c86b3931ec426ec2354dada493027909e 2397 
python-future_0.15.2-5.dsc
 7937eb7dfec078327cd980a99aa3d2645819dd753307748b2558303e316d 10888 
python-future_0.15.2-5.debian.tar.xz
 b56b80b2c330700ae8999ae8e76dfc731ebdc72007ef17bb06a4e5ee8e52c0a6 323156 
python-future-doc_0.15.2-5_all.deb
 f46d026d76ffbf2ba11cbb44c73e149f77acc658678500a1a25bdcbf7f6d85e0 347160 
python-future_0.15.2-5_all.deb
 ae451519bac750b26883c6e405c14643bba3c2350c35fd184e44a0b44a6cabd1 8692 
python-future_0.15.2-5_amd64.buildinfo
 71a0769bb3003f5743d43618ee391f2a82ad662edbceaca980134d4f6c5b2945 345404 
python3-future_0.15.2-5_all.deb
Files:
 8459932ffabf9e8b33cbc231695d803c 2397 python optional 
python-future_0.15.2-5.dsc
 8e5f81b3456bec18806ae13d67ac8ae4 10888 python optional 
python-future_0.15.2-5.debian.tar.xz
 e7cc6cdbaf3dff0a03c7b020301a67d9 323156 doc optional 
python-future-doc_0.15.2-5_all.deb
 7504e72bd56822c3ccaacaaf0e8770c6 347160 python optional 
python-future_0.15.2-5_all.deb
 b46ae1ac1cf902d70353686d42cf7664 8692 python optional 
python-future_0.15.2-5_amd64.buildinfo
 7f1316878cea2871939aff5de164c610 345404 python optional 
python3-future_0.15.2-5_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAlt8Vt0ACgkQNXMSVZ0e
BkvZcQ/6A3NVQ1gnqXuuH9fft1O4d7ObcGlZ1N+vxpARG/Qj4U4oVCdsN4bXcc1f

Bug#906870: xul-ext-certificatepatrol no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-certificatepatrol
Version: 2.0.14-5
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906869: xul-ext-uppity no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-uppity
Version: 1.5.8-5
Severity: serious

XUL addons are no longer supported.

Processed: severity of 864827 is serious

[Debian Bug Tracking System]

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

> severity 864827 serious
Bug #864827 [zotero-standalone] [zotero-standalone] No longer works with 
firefox 54 update
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 853992 is serious

[Debian Bug Tracking System]

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

> severity 853992 serious
Bug #853992 [xul-ext-requestpolicy] xul-ext-requestpolicy: update requestpolicy 
to 1.0 beta12.4 - compatibility with web extensions
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: firefox-esr 60 is now in unstable and will soon be in stretch

[Debian Bug Tracking System]

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

> severity 881812 serious
Bug #881812 [xul-ext-treestyletab] xul-ext-treestyletab: new version required 
for Firefox 57
Severity set to 'serious' from 'important'
> found 881812 0.18.2016111701-1
Bug #881812 [xul-ext-treestyletab] xul-ext-treestyletab: new version required 
for Firefox 57
Marked as found in versions tree-style-tab/0.18.2016111701-1.
> forcemerge 881812 889941
Bug #881812 [xul-ext-treestyletab] xul-ext-treestyletab: new version required 
for Firefox 57
Bug #889941 [xul-ext-treestyletab] xul-ext-treestyletab: please package 
xul-treestyletab 2.4.11 for firefox 57 or later
Severity set to 'serious' from 'normal'
Marked as found in versions tree-style-tab/0.18.2016111701-1.
Added tag(s) pending.
Merged 881812 889941
> thanks
Stopping processing here.

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

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

[Adrian Bunk]

Package: xul-ext-toggle-proxy
Version: 1.9-2
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906867: xul-ext-status4evar no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-status4evar
Version: 2016.10.11.01-1
Severity: serious

XUL addons are no longer supported.

Bug#906866: xul-ext-reloadevery no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-reloadevery
Version: 45.0.0-2
Severity: serious

XUL addons are no longer supported.

Bug#906363: Bug #906363 in hdmi2usb-fx2-firmware marked as pending

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #906363 in hdmi2usb-fx2-firmware reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/debian/hdmi2usb-fx2-firmware/commit/7e7bb8debc36b91380ec5957a3df80ff671e0489


Change putchar() prototype to match sdcc. (Closes: #906363)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/906363

Processed: Bug #906363 in hdmi2usb-fx2-firmware marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906363 [src:hdmi2usb-fx2-firmware] hdmi2usb-fx2-firmware: FTBFS in 
buster/sid (extern definition for 'putchar' mismatches with declaration.)
Added tag(s) pending.

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

Bug#906865: xul-ext-refcontrol no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-refcontrol
Version: 0.8.17-3
Severity: serious

XUL addons are no longer supported.

Processed: severity of 827310 is serious

[Debian Bug Tracking System]

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

> severity 827310 serious
Bug #827310 [xul-ext-pwdhash] xul-ext-pwdhash from stable is not compatible to 
firefox-esr and gets disabled
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#906864: xul-ext-perspectives no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-perspectives
Version: 4.6.4-1
Severity: serious

XUL addons are no longer supported.

Bug#906863: xul-ext-personasplus no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-personasplus
Version: 1.7.8-1
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906862: xul-ext-openinbrowser no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-openinbrowser
Version: 1.17-1
Severity: serious

XUL addons are no longer supported.

Bug#906860: xul-ext-mozvoikko no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-mozvoikko
Version: 2.2-0.1
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906861: mozilla-nukeimage no longer works with firefox-esr 60

[Adrian Bunk]

Package: mozilla-nukeimage
Version: 0.3-12
Severity: serious

XUL addons are no longer supported.

Processed: severity of 878425 is serious

[Debian Bug Tracking System]

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

> severity 878425 serious
Bug #878425 [xul-ext-itsalltext] it's all text will stop working in Firefox 57
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

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

[Adrian Bunk]

Package: xul-ext-dom-inspector
Version: 1:2.0.16-2
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906858: xul-ext-livehttpheaders no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-livehttpheaders
Version: 0.17.1-2
Severity: serious

XUL addons are no longer supported.

Processed: firefox-esr 60 is now in unstable and will soon be in stable

[Debian Bug Tracking System]

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

> tags 895315 - buster sid
Bug #895315 [xul-ext-greasemonkey] xul-ext-greasemonkey: Could not use script 
with recent firefox need to upgrade to 4.x
Removed tag(s) sid and buster.
> forcemerge 895315 864820
Bug #895315 [xul-ext-greasemonkey] xul-ext-greasemonkey: Could not use script 
with recent firefox need to upgrade to 4.x
Bug #895315 [xul-ext-greasemonkey] xul-ext-greasemonkey: Could not use script 
with recent firefox need to upgrade to 4.x
Added tag(s) fixed-upstream.
Bug #864820 [xul-ext-greasemonkey] xul-ext-greasemonkey: userscripts no longer 
available with firefox 54
Merged 864820 895315
> severity 864820 serious
Bug #864820 [xul-ext-greasemonkey] xul-ext-greasemonkey: userscripts no longer 
available with firefox 54
Bug #895315 [xul-ext-greasemonkey] xul-ext-greasemonkey: Could not use script 
with recent firefox need to upgrade to 4.x
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#906854: xul-ext-firexpath no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-firexpath
Version: 0.9.7.1-3
Severity: serious

XUL addons are no longer supported.

Bug#906852: xul-ext-firetray no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-firetray
Version: 0.6.1+dfsg-1
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906855: gcu-plugin: NPAPI plugins are no longer supported by firefox-esr

[Adrian Bunk]

Package: gcu-plugin
Version: 0.14.15-1
Severity: serious

NPAPI plugins are no longer supported by firefox-esr.

Processed: Re: Bug#906820: octave-statistics: autopkgtest failure on i386

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch ftbfs
Bug #906820 [src:octave-statistics] octave-statistics: autopkgtest failure on 
i386
Added tag(s) patch and ftbfs.
> severity -1 serious
Bug #906820 [src:octave-statistics] octave-statistics: autopkgtest failure on 
i386
Severity set to 'serious' from 'normal'

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

Bug#906851: xul-ext-firegestures no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-firegestures
Version: 1.10.9-1
Severity: serious

XUL addons are no longer supported.

Processed: severity of 881894 is serious

[Debian Bug Tracking System]

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

> severity 881894 serious
Bug #881894 [xul-ext-cookie-monster] xul-ext-cookie-monster: dead upstream, 
broken in FF57
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 899309 is serious

[Debian Bug Tracking System]

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

> severity 899309 serious
Bug #899309 [src:autofill-forms] autofill-forms: Replace it with non legacy 
autofillforms-e10 to be compatible with ff 60.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#906849: xul-ext-all-in-one-sidebar no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-all-in-one-sidebar
Version: 0.7.28-2
Severity: serious

XUL addons are no longer supported.

Bug#906848: xul-ext-adblock-plus-element-hiding-helper no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-adblock-plus-element-hiding-helper
Version: 1.3.8-1
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906847: xul-ext-adblock-plus no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-adblock-plus
Version: 2.7.3+dfsg-1
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.

Bug#906487: marked as done (libsmpp34: FTBFS in buster/sid (No rule to make target '../binaries/libsmpp34.la'))

[Debian Bug Tracking System]

Your message dated Tue, 21 Aug 2018 17:49:42 +
with message-id 
and subject line Bug#906487: fixed in libsmpp34 1.12.0-3
has caused the Debian Bug report #906487,
regarding libsmpp34: FTBFS in buster/sid (No rule to make target 
'../binaries/libsmpp34.la')
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
I: libsmpp34_1.12.0
dh build-arch --no-parallel --with autoreconf
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'aux_config'.
libtoolize: copying file 'aux_config/ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:12: installing 'aux_config/compile'
configure.ac:14: installing 'aux_config/config.guess'
configure.ac:14: installing 'aux_config/config.sub'
configure.ac:8: installing 'aux_config/install-sh'

[... snipped ...]

checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.20... yes
checking for ANSI C header files... (cached) yes
checking for stdlib.h... (cached) yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdint.h... (cached) yes
checking for string.h... (cached) yes
checking for LIBXML2... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for memset... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating def_frame/Makefile
config.status: creating def_list/Makefile
config.status: creating binaries/Makefile
config.status: creating test_apps/Makefile
config.status: creating libsmpp34.pc
config.status: creating aux_config/config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
cat debian/libsmpp34.pc.in | sed 's/$VERSION/1.12.0/' | sed 's/$PREFIX/\/usr/' \
 | sed 's#$LIBDIR#/usr/lib/x86_64-linux-gnu#' > debian/libsmpp34.pc
make[1]: Leaving directory '/<>'
   dh_auto_build -a
make -j1
make[1]: Entering directory '/<>'
echo UNKNOWN > .version-t && mv .version-t .version
make  all-recursive
make[2]: Entering directory '/<>'
Making all in binaries
make[3]: Entering directory '/<>/binaries'
gcc -DHAVE_CONFIG_H -I. -I../aux_config -I../src -I.. -D_REENTRANT -DBSD_COMP 
-D_POSIX_PTHREAD_SEMANTICS -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -fPIC  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o core.o `test -f '../test_pdu/core.c' || echo 
'./'`../test_pdu/core.c
gcc -DHAVE_CONFIG_H -I. -I../aux_config -I../src -I.. -D_REENTRANT -DBSD_COMP 
-D_POSIX_PTHREAD_SEMANTICS -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -fPIC  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o submit_multi_resp_test.o `test -f 
'../test_pdu/submit_multi_resp_test.c' || echo 
'./'`../test_pdu/submit_multi_resp_test.c
make[3]: *** No rule to make target '../binaries/libsmpp34.la', needed by 
'submit_multi_resp_test'.  Stop.
make[3]: Leaving directory '/<>/binaries'
make[2]: *** [Makefile:470: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:379: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:18: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

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

If this is really a bug in one of the 

Bug#875430: emacs25: please add Breaks: edb (<< 1.32)

[David Bremner]

Andreas Beckmann  writes:

> Package: emacs25
> Version: 25.2+1-5
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> emacs25 fails to install if edb 1.31 is installed, see #840748 for the
> edb bug, which suggests that this is fixed in the next upstream release
> of edb.
>
> To ensure smooth upgrades to emacs25, we need a Breaks against the
> problematic version, s.t. edb either gets upgraded or removed.
>
>
> Andreas

Hi Andreas;

Thanks for all your work with piuparts.  I agree that your proposal
would unbreak things for some (fairly small number of) users.

On the other hand, I'm not really convinced that emacs should add a
breaks for every add-on that is broken. There are more than 300
potential addons. They need to be fixed or removed. I also don't think
it really makes sense to delay emacs migration to testing when edb isn't
actually in testing.

With a popcon of 18, and an RC bug open for almost two years, removing
edb seems justifiable.

all the best,

David

Processed: found 890804 in 0.5.0.1-1

[Debian Bug Tracking System]

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

> found 890804 0.5.0.1-1
Bug #890804 [xul-ext-tabmixplus] xul-ext-tabmixplus: add WebExtensions version
Marked as found in versions tabmixplus/0.5.0.1-1.
> thanks
Stopping processing here.

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

Processed: found 882287 in 2.9.0.14-1

[Debian Bug Tracking System]

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

> found 882287 2.9.0.14-1
Bug #882287 [xul-ext-noscript] xul-ext-noscript: new upstream version 
(WebExtensions)
Marked as found in versions mozilla-noscript/2.9.0.14-1.
> thanks
Stopping processing here.

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

Processed: severity of 881506 is serious

[Debian Bug Tracking System]

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

> severity 881506 serious
Bug #881506 [xul-ext-gnome-keyring] xul-ext-gnome-keyring doesn't work with 
firefox >=57
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#906844: python3-protobuf: Installing 'python3-protobuf' causes uninstallation of 'python3-numpy'

[Ruben Undheim]

Package: python3-protobuf
Version: 3.0.0-9.1
Severity: serious

Dear Maintainer,

When installing 'python3-protobuf' in sid, 'python3-numpy' which is needed for
a number of reasons, becomes uninstalled.

'python3-numpy' depends on 'python3.7:any', while 'python3.7' has
'python3-protobuf (<= 3.0.0-9.1+b1)' in its break field.

A binNMU should then resolve this, I suppose.


Cheers
Ruben

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages python3-protobuf depends on:
ii  libc6  2.27-5
ii  libgcc11:8.2.0-4
ii  libprotobuf10  3.0.0-9.1
ii  libstdc++6 8.2.0-4
ii  python33.6.6-1
ii  python3-pkg-resources  39.2.0-1
ii  python3-six1.11.0-2

python3-protobuf recommends no packages.

python3-protobuf suggests no packages.

-- no debconf information

Bug#906843: xul-ext-custom-tab-width no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-custom-tab-width
Version: 1.1-1
Severity: serious

XUL addons are no longer supported.