Bug#903217: backuppc: Web interface status page doesn't show graphs

2018-07-07 Thread Dominique Brazziel 
Package: backuppc
Version: 3.3.1-5
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Select status page
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
No graphs shown, images broken
   * What outcome did you expect instead?
Graph images
*** End of the template - remove these template lines ***

Patch to fix:

--- /usr/share/backuppc/lib/BackupPC/CGI/GeneralInfo.pm.orig2016-09-06
04:04:33.466484120 -0400
+++ /usr/share/backuppc/lib/BackupPC/CGI/GeneralInfo.pm 2016-09-06
04:05:34.271384202 -0400
@@ -47,8 +47,11 @@
 if ($In{image} ne "") {
$In{image} =~ /([0-9]+)/;
my $weeks = $1;
+my $real = $<;  ### SUID
+$< = $>;### SUID
print "Content-type: image/png\n\n";
print `/usr/bin/rrdtool graph - --imgformat=PNG --start=end-${weeks}w
--end=-300 --title="BackupPC Pool Size (${weeks} weeks)" --base=1000
--height=100 --width=600 --alt-autoscale-max --lower-limit=0 --vertical-
label="" --slope-mode --font TITLE:10:Times --font AXIS:8:Times --font
LEGEND:8:Times --font UNIT:8:Times -c BACK#FF
DEF:ao="$LogDir/pool.rrd":ckb:AVERAGE CDEF:a=ao,1024,* AREA:a#95B8DB:"CPool in
bytes"  GPRINT:a:LAST:"Current\\:%8.2lf %s" GPRINT:a:AVERAGE:"Average\\:%8.2lf
%s" GPRINT:a:MAX:"Maximum\\:%8.2lf %s\\n"`;
+$< = $real;   ### SUID
return;
 }

That was per: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1612600


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

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

Versions of packages backuppc depends on:
ii  adduser3.117
ii  apache2 [httpd]2.4.33-3+b1
ii  apache2-utils  2.4.33-3+b1
ii  bzip2  1.0.6-8.1
ii  debconf [debconf-2.0]  1.5.67
ii  dpkg   1.19.0.5+b1
ii  exim4-daemon-light [mail-transport-agent]  4.91-5
ii  iputils-ping   3:20161105-1
ii  libarchive-zip-perl1.60-1
ii  libc6  2.27-3
ii  libcgi-pm-perl 4.38-1
pn  libdigest-md5-perl 
ii  libtime-parsedate-perl 2015.103-2
ii  libwww-perl6.34-1
ii  lsb-base   9.20170808
ii  perl [libio-compress-perl] 5.26.2-6
ii  samba-common-bin   2:4.8.2+dfsg-2
ii  smbclient  2:4.8.2+dfsg-2
ii  tar1.30+dfsg-2
ii  ucf3.0038

Versions of packages backuppc recommends:
ii  libfile-rsyncp-perl  0.74-2.1+b4
ii  libio-dirent-perl0.05-1+b6
ii  openssh-client [ssh-client]  1:7.7p1-2
ii  rrdtool  1.7.0-1+b2
ii  rsync3.1.2-2.1

Versions of packages backuppc suggests:
ii  chromium [www-browser] 67.0.3396.87-1
ii  firefox-esr [www-browser]  52.9.0esr-1
ii  hv3 [www-browser]  3.0~fossil20110109-6
pn  par2   
ii  w3m [www-browser]  0.5.3-36+b1

-- Configuration Files:
/etc/backuppc/hosts [Errno 13] Permission denied: '/etc/backuppc/hosts'
/etc/backuppc/localhost.pl [Errno 13] Permission denied:
'/etc/backuppc/localhost.pl'
/etc/default/backuppc changed:
NICE=0
IONICE=idle



-- debconf information:
  backuppc/restart-webserver: true

Processed: bug 580614 is not forwarded

2018-07-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # bts-link cleanup: forwarded url points to an error page
> notforwarded 580614
Bug #580614 [gnomint] help buttons do nothing
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

awffull_3.10.2-4+deb9u1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

2018-07-07 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Feb 2018 19:13:16 +0200
Source: awffull
Binary: awffull
Architecture: source
Version: 3.10.2-4+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 awffull- web server log analysis program
Closes: 728362
Changes:
 awffull (3.10.2-4+deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * Don't use removed options in /etc/cron.daily/awffull,
 thanks to Ludovic Rousseau. (Closes: #728362)
Checksums-Sha1:
 18222c8f0a302cfa61adc2a0368a9065f152d786 2040 awffull_3.10.2-4+deb9u1.dsc
 707608f4c138d194c068f5775a9b20f97c6ebf3b 15916 
awffull_3.10.2-4+deb9u1.debian.tar.xz
Checksums-Sha256:
 36bfa57f8e5851a764e7518514cc7410ad20b6b876882038255ff160b5632499 2040 
awffull_3.10.2-4+deb9u1.dsc
 87fc26d965005f9e944cd5154aacb4bc1e48d35f5f65726e726ea3c712c37fa3 15916 
awffull_3.10.2-4+deb9u1.debian.tar.xz
Files:
 91eb73f0a03655e80bf6229f4ce75be0 2040 web optional awffull_3.10.2-4+deb9u1.dsc
 7afae304ad26b5db3f2f1c1655705d73 15916 web optional 
awffull_3.10.2-4+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAls/wc8ACgkQiNJCh6LY
mLG4GA/+KuO13Mg0LMqauuVChpnR9IHefsRNAqIUyDuX+S7+XZ1PtyaGn4gv1y93
nHb1VbhdiQnWopCF/AqvXHJanrSu+tU2KQudvUY5GyoQZRgVE2Kcp0TPLJq2NxRS
gA/3vyohFOcU39uknlQMWAlZ/i2CpV5+DQKGjrSb3t3ptQtGnI5oNRc3VqbixxqL
eRF1bxO1ch/bERqvrnxHoU84A8dAIor+d/gJnAlczvN2GxnMhJ6ZlXvIvyXmZ0JB
TFK9H3C9BS4FVmewL7ATJu7DIIyKe9/KOrt8pHBoQu5GXdNF4SN95fOqMJSTgEiN
KOBSX6e2Zz32IllXFI1/A9gFr5SgtIkNy6ce7n4AQl9Sq2jPsly3fyVBW7jvGHZG
pPD6BUbKCA07Gw1nqPhPMyilRC7bljeGE454mWW2036ios7I1N0LCgQfTs/Bwr2I
31wJ4+kKjNvATJaQWp6fRlKj3qN+Wm0yxDhVja4+MuNaDFatwsOGDS2uEalNC1Rh
7YVpcLL85QdxYesp2izzIhNYW5ON5HYueaDd2zIzVjdJiWF7R3qvYdORI4JeHQDk
APHv3JYpUrsf27oFZ5FmlC3X7UezPpZFKz05sUmHSmnD8G55VTdof8dDQkiK96mx
gvscOwBIPVc+PGXPnk1FNZpbAzhfNy+RCSJKt4+wPiMy7DnHzhI=
=JaaX
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#728362: marked as done (awffull: /etc/cron.daily/awffull needs update)

2018-07-07 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Jul 2018 14:16:56 +
with message-id 
and subject line Bug#728362: fixed in awffull 3.10.2-4+deb9u1
has caused the Debian Bug report #728362,
regarding awffull: /etc/cron.daily/awffull needs update
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.)


-- 
728362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: awffull
Version: 3.10.2-4
Severity: important
Tags: patch

I get the following error message:

/etc/cron.daily/awffull:
Use of "Really Quiet (-Q)" has been deprecated.
Initially processed default config file: /etc/awffull/awffull.conf
awffull 3.10.2 (Linux 3.11-1-amd64) English
Error: Can't open log file 0
ERROR: Running awffull, exit status: 1

obviously /etc/cron.daily/awffull is not updated to the current command line
parameters



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

Kernel: Linux 3.11-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages awffull depends on:
ii  debconf [debconf-2.0]  1.5.51
ii  libc6  2.17-93
ii  libgd3 2.1.0-3
ii  libgeoip1  1.5.1-2
ii  libpcre3   1:8.31-2
ii  zlib1g 1:1.2.8.dfsg-1

awffull recommends no packages.

Versions of packages awffull suggests:
ii  apache2-bin [httpd]  2.4.6-3
pn  dnshistory   
ii  ttf-dejavu   2.33+svn2514-3

-- Configuration Files:
/etc/cron.daily/awffull changed:
AWFFULL=/usr/bin/awffull
AWFFULL_CONFDIR=/etc/awffull
[ -x ${AWFFULL} ] || exit 0;
[ -d ${AWFFULL_CONFDIR} ] || exit 0;
for i in ${AWFFULL_CONFDIR}/*.conf; do
  # run agains a rotated or normal logfile
  LOGFILE=`awk '$1 ~ /^LogFile$/ {print $2}' $i`;
  # empty ?
  [ -s "${LOGFILE}" ] || { echo "ERROR: LogFile not found: ${LOGFILE}"; 
continue; };
  # readable ?
  [ -r "${LOGFILE}" ] || { echo "ERROR: LogFile is not readable: ${LOGFILE}"; 
continue; };
  
  # there was a output ?
  OUTDIR=`awk '$1 ~ /^OutputDir$/ {print $2}' $i`;
  #  exists something ?
  [ "${OUTDIR}" != "" ] || { echo "ERROR: OutputDir not defined: ${OUTDIR}"; 
continue; };
  # its a directory ?
  [ -d ${OUTDIR} ] || { echo "ERROR: OutputDir is not a directory: ${OUTDIR}"; 
continue; };
  # its writable ?
  [ -w ${OUTDIR} ] || { echo "ERROR: OutputDir not writable: ${OUTDIR}"; 
continue; };
  # Run Really quietly, exit with status code if !0
  ${AWFFULL} ${i} || { echo "ERROR: Running awffull, exit status: $?"; 
continue; };
  RET=$?;
  # Non rotated log file
  NLOGFILE=`awk '$1 ~ /^LogFile$/ {gsub(/\.[0-9]+(\.gz)?/,""); print $2}' $i`;
  # check current log, if last log is a rotated logfile
  if [ "${LOGFILE}" != "${NLOGFILE}" ]; then
# empty ?
[ -s "${NLOGFILE}" ] || { echo "INFO: Non-rotated LogFile empty or missing: 
${NLOGFILE}"; continue; };
# readable ?
[ -r "${NLOGFILE}" ] || { echo "WARNING: Non-rotated LogFile is not 
readable: ${NLOGFILE}"; continue; };
${AWFFULL} -v 0 ${i} -Q ${NLOGFILE};
RET=$?;
  fi;
done;
exit $RET;


-- debconf information:
  awffull/logfile: /var/log/apache2/access.log.1
  awffull/directory: /var/www/awffull
--- End Message ---
--- Begin Message ---
Source: awffull
Source-Version: 3.10.2-4+deb9u1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated awffull package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Feb 2018 19:13:16 +0200
Source: awffull
Binary: awffull
Architecture: source
Version: 3.10.2-4+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 awffull- web server log analysis program

Processed: tagging 902454, found 881580 in 1.2.2

2018-07-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 902454 + sid buster
Bug #902454 {Done: Stephen Kitt } [src:bochs] bochs: FTBFS in 
buster/sid ('AmlCode' undeclared)
Added tag(s) sid and buster.
> found 881580 1.2.2
Bug #881580 [googleearth-package] googleearth-package: Generated package is 
uninstallable, and application unrunnable
Marked as found in versions googleearth-package/1.2.2.
> thanks
Stopping processing here.

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

Bug#833915: marked as done (awffull cron script broken)

2018-07-07 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Jul 2018 14:16:56 +
with message-id 
and subject line Bug#728362: fixed in awffull 3.10.2-4+deb9u1
has caused the Debian Bug report #728362,
regarding awffull cron script broken
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.)


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

Package: awffull
Version: awffull_3.10.2-4_amd64

The script in /etc/cron.daily is broken/old in Jessie. The cron script from
wheezy works. diff those two cron scripts and you ll see the problem.

Here is the error from the jessie script:

root@srv:/etc/cron.daily# ./awffull
Benutzung von "Wirklich Verlassen (-Q)" ist veraltet.
Initially processed default config file: /etc/awffull/awffull.conf
awffull 3.10.2 (Linux 3.16.0-4-amd64) German
Nutze GeoIP für Adressauflösung: /usr/share/GeoIP/GeoIP.dat
Fehler: Kann die Logdatei nicht öffnen. 0
ERROR: Running awffull, exit status: 1

I suggest to use the cron script from wheezy.

I am using Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3
(2016-07-02) x86_64 GNU/Linux
--- End Message ---
--- Begin Message ---
Source: awffull
Source-Version: 3.10.2-4+deb9u1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated awffull package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Feb 2018 19:13:16 +0200
Source: awffull
Binary: awffull
Architecture: source
Version: 3.10.2-4+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 awffull- web server log analysis program
Closes: 728362
Changes:
 awffull (3.10.2-4+deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * Don't use removed options in /etc/cron.daily/awffull,
 thanks to Ludovic Rousseau. (Closes: #728362)
Checksums-Sha1:
 18222c8f0a302cfa61adc2a0368a9065f152d786 2040 awffull_3.10.2-4+deb9u1.dsc
 707608f4c138d194c068f5775a9b20f97c6ebf3b 15916 
awffull_3.10.2-4+deb9u1.debian.tar.xz
Checksums-Sha256:
 36bfa57f8e5851a764e7518514cc7410ad20b6b876882038255ff160b5632499 2040 
awffull_3.10.2-4+deb9u1.dsc
 87fc26d965005f9e944cd5154aacb4bc1e48d35f5f65726e726ea3c712c37fa3 15916 
awffull_3.10.2-4+deb9u1.debian.tar.xz
Files:
 91eb73f0a03655e80bf6229f4ce75be0 2040 web optional awffull_3.10.2-4+deb9u1.dsc
 7afae304ad26b5db3f2f1c1655705d73 15916 web optional 
awffull_3.10.2-4+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAls/wc8ACgkQiNJCh6LY
mLG4GA/+KuO13Mg0LMqauuVChpnR9IHefsRNAqIUyDuX+S7+XZ1PtyaGn4gv1y93
nHb1VbhdiQnWopCF/AqvXHJanrSu+tU2KQudvUY5GyoQZRgVE2Kcp0TPLJq2NxRS
gA/3vyohFOcU39uknlQMWAlZ/i2CpV5+DQKGjrSb3t3ptQtGnI5oNRc3VqbixxqL
eRF1bxO1ch/bERqvrnxHoU84A8dAIor+d/gJnAlczvN2GxnMhJ6ZlXvIvyXmZ0JB
TFK9H3C9BS4FVmewL7ATJu7DIIyKe9/KOrt8pHBoQu5GXdNF4SN95fOqMJSTgEiN
KOBSX6e2Zz32IllXFI1/A9gFr5SgtIkNy6ce7n4AQl9Sq2jPsly3fyVBW7jvGHZG
pPD6BUbKCA07Gw1nqPhPMyilRC7bljeGE454mWW2036ios7I1N0LCgQfTs/Bwr2I
31wJ4+kKjNvATJaQWp6fRlKj3qN+Wm0yxDhVja4+MuNaDFatwsOGDS2uEalNC1Rh
7YVpcLL85QdxYesp2izzIhNYW5ON5HYueaDd2zIzVjdJiWF7R3qvYdORI4JeHQDk
APHv3JYpUrsf27oFZ5FmlC3X7UezPpZFKz05sUmHSmnD8G55VTdof8dDQkiK96mx
gvscOwBIPVc+PGXPnk1FNZpbAzhfNy+RCSJKt4+wPiMy7DnHzhI=
=JaaX
-END PGP SIGNATURE End Message ---

Processed: found 902573 in 60.1.0esr-1, found 894371 in 2.8.4-1, tagging 903065, tagging 899998, tagging 903063 ...

2018-07-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> found 902573 60.1.0esr-1
Bug #902573 [firefox-esr] firefox-esr: firefox 60.1.0esr requires nss >= 3.36.4
Marked as found in versions firefox-esr/60.1.0esr-1.
> found 894371 2.8.4-1
Bug #894371 {Done: Gert Wollny } [src:gdcm] gdcm: depends on 
openjdk-8
Marked as found in versions gdcm/2.8.4-1.
> tags 903065 + sid buster
Bug #903065 [dbab] dbab FTBFS: update Build-Depends: ruby-ronn -> ronn
Added tag(s) sid and buster.
> tags 88 + sid buster
Bug #88 {Done: Andreas Beckmann } 
[nvidia-legacy-340xx-kernel-dkms] nvidia-legacy-340xx-kernel-dkms: Dmesg 
output: "Bad or missing usercopy whitelist? Kernel memory exposure attempt 
detected from SLUB object 'nvidia_stack_t'"
Added tag(s) sid and buster.
> tags 903063 + sid buster
Bug #903063 [coquelicot] coquelicot FTBFS: update Build-Depends: ruby-ronn -> 
ronn
Added tag(s) buster and sid.
> tags 903070 + sid buster
Bug #903070 [src:haproxyctl] haproxyctl FTBFS: update Build-Depends: ruby-ronn 
-> ronn
Added tag(s) buster and sid.
> tags 857260 + sid buster
Bug #857260 {Done: Simon McVittie } [src:libappindicator] 
libappindicator: please do not build-depend on libindicate
Added tag(s) sid and buster.
> tags 901405 + sid buster
Bug #901405 [systemd-shim] systemd-shim: Please add a sysvinit service to 
create directories on /run at boot
Added tag(s) sid and buster.
> tags 901404 + sid buster
Bug #901404 [systemd-shim] systemd-shim: Please dpkg-divert the dbus services 
you want dbus-activatable
Added tag(s) buster and sid.
> retitle 882103 obfsproxy: crashing with "ImportError: No module named 
> load_entry_point"
Bug #882103 {Done: Adrian Bunk } [obfsproxy] 
python-pkg-resources: crashing with "ImportError: No module named 
load_entry_point"
Changed Bug title to 'obfsproxy: crashing with "ImportError: No module named 
load_entry_point"' from 'python-pkg-resources: crashing with "ImportError: No 
module named load_entry_point"'.
> tags 902385 + sid buster
Bug #902385 [blacs-pvm-test] blacs-pvm-test: depends on removed package 
blacs-test-common
Added tag(s) sid and buster.
> tags 903056 + sid buster
Bug #903056 [src:foremancli] foremancli FTBFS: update Build-Depends: ruby-ronn 
-> ronn
Added tag(s) buster and sid.
> found 902631 1.6.5-1
Bug #902631 [src:astroid] Not compatible with Python 3.7
Marked as found in versions astroid/1.6.5-1.
> retitle 902631 astroid: Not compatible with Python 3.7
Bug #902631 [src:astroid] Not compatible with Python 3.7
Changed Bug title to 'astroid: Not compatible with Python 3.7' from 'Not 
compatible with Python 3.7'.
> found 903028 0.2018.04.28~dfsg0-2
Bug #903028 [src:ejabberd-contrib] ejabberd-contrib: FTBFS with ejabberd >= 
18.06
Marked as found in versions ejabberd-contrib/0.2018.04.28~dfsg0-2.
> fixed 902810 4.16-1um-2
Bug #902810 [src:user-mode-linux] user-mode-linux: FTBFS in stretch (Hunk #1 
FAILED in 07-remove-rpath.patch)
Marked as fixed in versions user-mode-linux/4.16-1um-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
857260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857260
882103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882103
894371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894371
88: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88
901404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901404
901405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901405
902385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902385
902573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902573
902631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902631
902810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902810
903028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903028
903056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903056
903063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903063
903065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903065
903070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

libappindicator_0.4.92-6_source.changes ACCEPTED into unstable

2018-07-07 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Jul 2018 13:01:20 +0100
Source: libappindicator
Binary: libappindicator1 gir1.2-appindicator-0.1 libappindicator-dev 
libappindicator-doc libappindicator3-1 libappindicator3-dev 
gir1.2-appindicator3-0.1
Architecture: source
Version: 0.4.92-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Simon McVittie 
Description:
 gir1.2-appindicator-0.1 - Typelib files for libappindicator1
 gir1.2-appindicator3-0.1 - Typelib files for libappindicator3-1
 libappindicator-dev - allow applications to export a menu into the panel -- 
development
 libappindicator-doc - allow applications to export a menu into the panel -- 
documentati
 libappindicator1 - allow applications to export a menu into the panel
 libappindicator3-1 - allow applications to export a menu into the panel -- 
GTK3 versio
 libappindicator3-dev - allow applications to export a menu into the panel -- 
GTK3 develo
Closes: 857260 890153 897473
Changes:
 libappindicator (0.4.92-6) unstable; urgency=medium
 .
   * QA upload.
   * Remove Vcs-* since bzr.debian.org is no more. History can be found
 at .
   * d/p/Remove-unnecessary-GObject-cast.patch:
 Remove an unnecessary cast to fix FTBFS with newer GLib versions
 (Closes: #897473)
   * Do not build-depend on libindicate, which appears to have been due to
 confusion between the various indicator libraries. libappindicator
 (deprecated) depends on libindicator (also deprecated) but has
 no particular relationship to libindicate (also deprecated), and
 removing this dependency gets us 33% closer to being able to remove
 libindicate from Debian. (Closes: #857260)
   * Move all binary packages to oldlibs section (this also requires
 ftp team action, requested in #903089)
   * Remove legacy PyGTK bindings (python-appindicator) since nothing in
 Debian depends on them any more
 - d/p/Disable-legacy-Python-bindings.patch:
   Hack out the PyGTK bindings from the build system
 - This incidentally removes a dependency on the deprecated
   python-gobject transitional package (Closes: #890153)
   * Drop unused build-dependency on gnome-doc-utils
   * Drop unused build-dependency on quilt
   * d/rules: Remove remnants of Mono bindings
   * Add missing dependency from each -dev package to the corresponding
 gir1.2-* GObject-Introspection package as per the g-i mini-policy
Checksums-Sha1:
 da779eb4ed4881945cc46cdfc39e53dd248ea1f1 2688 libappindicator_0.4.92-6.dsc
 69487f71659daa129617bdac9f0611a213e42e6c 13368 
libappindicator_0.4.92-6.debian.tar.xz
 bf0efecd5ada0ffd4260455b7be78d96b9853dd8 15925 
libappindicator_0.4.92-6_source.buildinfo
Checksums-Sha256:
 74696113d9a80236be43ceb87489004e13d9065e71a1526a0062fff8341c52cc 2688 
libappindicator_0.4.92-6.dsc
 fa31f4dd86b56a6916047e0842a646ef9437feb8406eb006f8558d6802a4a844 13368 
libappindicator_0.4.92-6.debian.tar.xz
 0e597b08750f627c37f85ad1fba3fd368fd717f12599f8a889f4e68d2b748b45 15925 
libappindicator_0.4.92-6_source.buildinfo
Files:
 8abd86176198eb6f93b9a1098fba5ce7 2688 oldlibs optional 
libappindicator_0.4.92-6.dsc
 d2e2718882d960d6b64c7fe92c7e12cb 13368 oldlibs optional 
libappindicator_0.4.92-6.debian.tar.xz
 618a985c30cf0a2dce684b9bcc5eb9ad 15925 oldlibs optional 
libappindicator_0.4.92-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAltAr3sACgkQ4FrhR4+B
TE/iDxAAi6gnAUmYTkq4WKniM0HCUxv7x0TknvL4mDmo6CLHUV0rVoshD8TzOZ20
3eV9u3SS4TWu6DQYgsvKj2tHUaxp3CQ8liqqkP2Q8MC+v8MTTQYY0yHnBFASKqRa
TgzvCoh2Pj4B4emxxl2SqBM5vcriYvMPbxXArPiWbvqOQdhlo006AnXpQmzm3eDi
brB+qd5ZIFtYo7E/07ew/FrOe5khoN8f/E2FIllNpDGWoe0uDLRxx7SPpvROE2BZ
mI59IYjaA3phWN/xGVViCIBvN2v6Yt681HGehR+RrU30gMjZwK1sxiRvmQ1mMReA
wk2X+O6baij2HPYpvVZZg+VlnC4KT0WKMJJt2pEgGTKYWltk6uwH4El/j0IpF4e+
rvioU7LZtzsQpdRxUFiSABVbfpW/cpmYZwhNt777XRUKPX6//hum3/Uqi8OUiJa3
HDg384jfY9fdu85Iw1kjVMJ3PmQkt3b+3APaPVkeFv3GOZPWPxim9SOh8JOrLGD1
M1AGtN+erY2sGZUUEpNxBReslLX/sPnszqpByFdLXPoehXxYsNYglPAFsTqLMT+I
5339AN/AX85u1rKOjZ64tmdyGyx5sOgIDbD0Y9c+NzWo/UE2n1FEsco6BjU5zvff
of86O6Y8aL4CjvcFxB+51OoGc6wzACJTEi2xM1Defv/gdOz77aI=
=yw55
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of libappindicator_0.4.92-6_source.changes

2018-07-07 Thread Debian FTP Masters 
libappindicator_0.4.92-6_source.changes uploaded successfully to localhost
along with the files:
  libappindicator_0.4.92-6.dsc
  libappindicator_0.4.92-6.debian.tar.xz
  libappindicator_0.4.92-6_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#890153: marked as done (libappindicator: Please switch to python-gobject-2/python-gi)

2018-07-07 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Jul 2018 12:34:48 +
with message-id 
and subject line Bug#890153: fixed in libappindicator 0.4.92-6
has caused the Debian Bug report #890153,
regarding libappindicator: Please switch to python-gobject-2/python-gi
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.)


-- 
890153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libappindicator
Version: 0.4.92-5
Severity: important
Tags: buster sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: pygobject-trans-rm

Dear Maintainer,

Your package libappindicator depends against the python-gobject
transitional package.

We would like to drop this transitional package for buster.

Could you please switch to either python-gobject-2 (if your package
is using the old python binding for GObject) or to python-gi (if your
package is using the new gobject-introspection one).

Please don't hesitate to contact me if you have any questions.

Kind Regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: libappindicator
Source-Version: 0.4.92-6

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libappindicator package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Jul 2018 13:01:20 +0100
Source: libappindicator
Binary: libappindicator1 gir1.2-appindicator-0.1 libappindicator-dev 
libappindicator-doc libappindicator3-1 libappindicator3-dev 
gir1.2-appindicator3-0.1
Architecture: source
Version: 0.4.92-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Simon McVittie 
Description:
 gir1.2-appindicator-0.1 - Typelib files for libappindicator1
 gir1.2-appindicator3-0.1 - Typelib files for libappindicator3-1
 libappindicator-dev - allow applications to export a menu into the panel -- 
development
 libappindicator-doc - allow applications to export a menu into the panel -- 
documentati
 libappindicator1 - allow applications to export a menu into the panel
 libappindicator3-1 - allow applications to export a menu into the panel -- 
GTK3 versio
 libappindicator3-dev - allow applications to export a menu into the panel -- 
GTK3 develo
Closes: 857260 890153 897473
Changes:
 libappindicator (0.4.92-6) unstable; urgency=medium
 .
   * QA upload.
   * Remove Vcs-* since bzr.debian.org is no more. History can be found
 at .
   * d/p/Remove-unnecessary-GObject-cast.patch:
 Remove an unnecessary cast to fix FTBFS with newer GLib versions
 (Closes: #897473)
   * Do not build-depend on libindicate, which appears to have been due to
 confusion between the various indicator libraries. libappindicator
 (deprecated) depends on libindicator (also deprecated) but has
 no particular relationship to libindicate (also deprecated), and
 removing this dependency gets us 33% closer to being able to remove
 libindicate from Debian. (Closes: #857260)
   * Move all binary packages to oldlibs section (this also requires
 ftp team action, requested in #903089)
   * Remove legacy PyGTK bindings (python-appindicator) since nothing in
 Debian depends on them any more
 - d/p/Disable-legacy-Python-bindings.patch:
   Hack out the PyGTK bindings from the build system
 - This incidentally removes a dependency on the deprecated
   python-gobject transitional package (Closes: #890153)
   * Drop unused build-dependency on gnome-doc-utils
   * Drop unused build-dependency on quilt
   * d/rules: Remove remnants of Mono bindings
   * Add missing dependency from each -dev package to the corresponding
 gir1.2-* GObject-Introspection package as per the g-i mini-policy
Checksums-Sha1:
 da779eb4ed4881945cc46cdfc39e53dd248ea1f1 2688 libappindicator_0.4.92-6.dsc
 69487f71659daa129617bdac9f0611a213e42e6c 13368 
libappindicator_0.4.92-6.debian.tar.xz

Bug#897473: marked as done (libappindicator: FTBFS: app-indicator.c:2188:28: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types])

2018-07-07 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Jul 2018 12:34:48 +
with message-id 
and subject line Bug#897473: fixed in libappindicator 0.4.92-6
has caused the Debian Bug report #897473,
regarding libappindicator: FTBFS: app-indicator.c:2188:28: error: assignment 
from incompatible pointer type [-Werror=incompatible-pointer-types]
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.)


-- 
897473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libappindicator
Version: 0.4.92-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I/<>/./src -I..-pthread -I/usr/include/libindicator-0.4 
> -I/usr/include/libdbusmenu-gtk-0.4 -I/usr/include/libdbusmenu-glib-0.4 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/fribidi -I/usr/include/uuid -I/usr/include/freetype2 
> -I/usr/include/libpng16 -Wall -Werror -DG_LOG_DOMAIN=\"libappindicator\" -g 
> -O2 -c -o libappindicator_la-app-indicator.lo `test -f 'app-indicator.c' || 
> echo '/<>/./src/'`app-indicator.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/<>/./src -I.. 
> -pthread -I/usr/include/libindicator-0.4 -I/usr/include/libdbusmenu-gtk-0.4 
> -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -Wall 
> -Werror -DG_LOG_DOMAIN=\"libappindicator\" -g -O2 -c 
> /<>/./src/app-indicator.c  -fPIC -DPIC -o 
> .libs/libappindicator_la-app-indicator.o
> /<>/./src/app-indicator.c: In function 
> 'app_indicator_set_secondary_activate_target':
> /<>/./src/app-indicator.c:2188:28: error: assignment from 
> incompatible pointer type [-Werror=incompatible-pointer-types]
>   priv->sec_activate_target = g_object_ref(G_OBJECT(menuitem));
> ^
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:721: libappindicator_la-app-indicator.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/libappindicator_0.4.92-5_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libappindicator package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Jul 2018 13:01:20 +0100
Source: libappindicator
Binary: libappindicator1 gir1.2-appindicator-0.1 libappindicator-dev 
libappindicator-doc libappindicator3-1 libappindicator3-dev 
gir1.2-appindicator3-0.1
Architecture: source
Version:

Bug#857260: marked as done (libappindicator: please do not build-depend on libindicate)

2018-07-07 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Jul 2018 12:34:48 +
with message-id 
and subject line Bug#857260: fixed in libappindicator 0.4.92-6
has caused the Debian Bug report #857260,
regarding libappindicator: please do not build-depend on libindicate
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.)


-- 
857260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libappindicator
Version: 0.4.92-4
Severity: normal

While investigating whether an RC bug in the orphaned package
src:libindicate should be resolved by fixing the bugs or by removing the
package, I noticed that libappindicator Build-Depends on libindicate-dev,
but has no libindicate runtime dependency.

This appears to have been caused by confusion between libindicator,
which libappindicator does legitimately depend on, and libindicate,
which is not used.

Please remove this obsolete build-dependency.

This bug might be escalated to serious if it is feasible to remove
libindicate from stretch, because the less unmaintained code we have,
the better.

Regards,
S
--- End Message ---
--- Begin Message ---
Source: libappindicator
Source-Version: 0.4.92-6

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libappindicator package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Jul 2018 13:01:20 +0100
Source: libappindicator
Binary: libappindicator1 gir1.2-appindicator-0.1 libappindicator-dev 
libappindicator-doc libappindicator3-1 libappindicator3-dev 
gir1.2-appindicator3-0.1
Architecture: source
Version: 0.4.92-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Simon McVittie 
Description:
 gir1.2-appindicator-0.1 - Typelib files for libappindicator1
 gir1.2-appindicator3-0.1 - Typelib files for libappindicator3-1
 libappindicator-dev - allow applications to export a menu into the panel -- 
development
 libappindicator-doc - allow applications to export a menu into the panel -- 
documentati
 libappindicator1 - allow applications to export a menu into the panel
 libappindicator3-1 - allow applications to export a menu into the panel -- 
GTK3 versio
 libappindicator3-dev - allow applications to export a menu into the panel -- 
GTK3 develo
Closes: 857260 890153 897473
Changes:
 libappindicator (0.4.92-6) unstable; urgency=medium
 .
   * QA upload.
   * Remove Vcs-* since bzr.debian.org is no more. History can be found
 at .
   * d/p/Remove-unnecessary-GObject-cast.patch:
 Remove an unnecessary cast to fix FTBFS with newer GLib versions
 (Closes: #897473)
   * Do not build-depend on libindicate, which appears to have been due to
 confusion between the various indicator libraries. libappindicator
 (deprecated) depends on libindicator (also deprecated) but has
 no particular relationship to libindicate (also deprecated), and
 removing this dependency gets us 33% closer to being able to remove
 libindicate from Debian. (Closes: #857260)
   * Move all binary packages to oldlibs section (this also requires
 ftp team action, requested in #903089)
   * Remove legacy PyGTK bindings (python-appindicator) since nothing in
 Debian depends on them any more
 - d/p/Disable-legacy-Python-bindings.patch:
   Hack out the PyGTK bindings from the build system
 - This incidentally removes a dependency on the deprecated
   python-gobject transitional package (Closes: #890153)
   * Drop unused build-dependency on gnome-doc-utils
   * Drop unused build-dependency on quilt
   * d/rules: Remove remnants of Mono bindings
   * Add missing dependency from each -dev package to the corresponding
 gir1.2-* GObject-Introspection package as per the g-i mini-policy
Checksums-Sha1:
 da779eb4ed4881945cc46cdfc39e53dd248ea1f1 2688 libappindicator_0.4.92-6.dsc
 69487f71659daa129617bdac9f0611a213e42e6c 13368

Bug#829786: marked as done (libappindicator: Uses deprecated gnome-common macros/variables)

2018-07-07 Thread Debian Bug Tracking System 
Your message dated Sat, 7 Jul 2018 12:58:57 +0100
with message-id <20180707115857.ga15...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#829786: libappindicator: Uses deprecated gnome-common 
macros/variables
has caused the Debian Bug report #829786,
regarding libappindicator: Uses deprecated gnome-common macros/variables
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.)


-- 
829786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libappindicator
Version: 0.4.92-4
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-common

Hi,

gnome-common did a cleanup upstream and deprecated quite a few macros
and variables.

gnome-doc-utils removal
===
The gnome-doc-utils build infrastructure was removed completely along
with the following macros:

 GNOME_DOC_INIT [1]
 GNOME_COMMON_INIT [2]


deprecated variables

The following variables used in gnome-autogen.sh have been declared
deprecated [3]:

 REQUIRED_GNOME_DOC_UTILS_VERSION
 REQUIRED_DOC_COMMON_VERSION
 USE_COMMON_DOC_BUILD
 FORBIDDEN_M4MACROS
 GNOME2_DIR
 GNOME2_PATH
 USE_GNOME2_MACROS

deprecated macros
=
The following macros have also been declared deprecated:

 GNOME_COMPILE_WARNINGS [4]
 GNOME_CXX_WARNINGS [5]

Upstream has documentation at [6] with how you can fix your package and
why those particular changes were made.

According to codesearch.d.n your package libappindicator uses one of the macros 
or
variables so might be affected, especially once you run autoreconf. Please
update your package accordingly and forward it to upstream if possible.

If you have further question, please don't hesitate to ask.

Regards,
Michael

[1] https://git.gnome.org/browse/gnome-common/commit/?id=6684e2fa5
[2] https://git.gnome.org/browse/gnome-common/commit/?id=1f60e9536
[3] https://git.gnome.org/browse/gnome-common/commit/?id=4c8d8ad93
[4] https://git.gnome.org/browse/gnome-common/commit/?id=b57bae0be
[5] https://git.gnome.org/browse/gnome-common/commit/?id=2bffd7e1u
[6] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
On Tue, 05 Jul 2016 at 22:29:45 +0200, bi...@debian.org wrote:
> According to codesearch.d.n your package libappindicator uses one of the 
> macros or
> variables so might be affected, especially once you run autoreconf.

This appears to be a false positive. libappindicator's autogen.sh uses
deprecated gnome-common facilities, but the Debian packaging doesn't
run it and there is no build-dependency.

libappindicator is dead upstream (#895037) so this will not be fixed
there either. Its successor libayatana-appindicator uses mate-common,
a maintained fork of gnome-common.

smcv--- End Message ---

Bug#903177: libcdio-paranoia: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-07 Thread Santiago Vila 
Package: src:libcdio-paranoia
Version: 10.2+0.94+2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh_testdir
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:80: installing './compile'
configure.ac:28: installing './missing'
example/C++/Makefile.am: installing './depcomp'

[... snipped ...]

Making install in test
make[2]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
Making install in cdda_interface
make[3]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[4]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[3]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
Making install in data
make[3]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[4]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[3]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[3]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[4]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[3]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[2]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
Making install in example
make[2]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[3]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[4]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[3]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[2]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[2]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[3]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p 
'/<>/libcdio-paranoia-10.2+0.94+2/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 libcdio_paranoia.pc libcdio_cdda.pc 
'/<>/libcdio-paranoia-10.2+0.94+2/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[2]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[1]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2'
dh_testdir
dh_testroot
dh_installchangelogs ChangeLog
dh_installdocs
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

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


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

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.

Bug#903167: autofs: FTBFS in buster/sid (dh_installman: Cannot find "debian/tmp/usr/share/man/man5/autofs_ldap_auth.conf.conf.5")

2018-07-07 Thread Santiago Vila 
Package: src:autofs
Version: 5.1.2-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with systemd
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
autoreconf --force
MOUNT=/bin/mount UMOUNT=/bin/umount \
MOUNT_NFS=/sbin/mount.nfs \
E2FSCK=/sbin/fsck.ext2 E3FSCK=/sbin/fsck.ext3 E4FSCK=/sbin/fsck.ext4 \
initdir=/etc/init.d piddir=/var/run \
sssldir=/usr/lib/x86_64-linux-gnu/sssd/modules \
dh_auto_configure -- \
--disable-mount-locking \
--enable-force-shutdown \

[... snipped ...]

Installed package default configuration as "autofs.conf".

Installing autofs init configuation in /etc/default
'autofs.init.conf' -> '/<>/debian/tmp/etc/default/autofs'
Installed package init configuration as "autofs".

Installing autofs ldap auth config "autofs_ldap_auth.conf" in /etc
'autofs_ldap_auth.conf' -> 
'/<>/debian/tmp/etc/autofs_ldap_auth.conf'
Installed package auth config as "autofs_ldap_auth.conf".

Installing autofs default master map in /etc
'auto.master' -> '/<>/debian/tmp/etc/auto.master'
Installed package master map as "auto.master".

Installing autofs sample map "auto.misc" in /etc
'auto.misc' -> '/<>/debian/tmp/etc/auto.misc'
Installed package sample map as "auto.misc".
Backup of existing map made to "auto.misc.orig".

Installing autofs sample map "auto.net" in /etc
'auto.net' -> '/<>/debian/tmp/etc/auto.net'
Installed package sample map as "auto.net".

Installing autofs sample map "auto.smb" in /etc
'auto.smb' -> '/<>/debian/tmp/etc/auto.smb'
Installed package sample map as "auto.smb".

make[2]: Leaving directory '/<>/samples'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# remove hesiod and ldap modules, they're in separate packages
rm -f debian/autofs/usr/lib/*/autofs/*hesiod*.so \
  debian/autofs/usr/lib/*/autofs/*ldap*.so
make[1]: Leaving directory '/<>'
   dh_installdocs -a
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
dh_installchangelogs CHANGELOG
make[1]: Leaving directory '/<>'
   dh_installexamples -a
   dh_installman -a
dh_installman: Cannot find (any matches for) 
"debian/tmp/usr/share/man/man5/autofs_ldap_auth.conf.conf.5" (tried in .)

dh_installman: Aborting due to earlier error
debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


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

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.