Bug#871062: collectd: FTBFS: client.c:621:23: error: '%s' directive output may be truncated writing up to 1023 bytes into a region of size 1010 [-Werror=format-truncation=]

[Marc Fournier]

Hello Michael,

On Mon, Aug 21, 2017 at 06:11:02PM +0200, Michael Stapelberg wrote:
> Hi,
> 
> Steve Langasek  writes:
> > The attached one-liner patch corrects this build failure by simply ignoring
> > the (IMHO uninteresting) new gcc-7 warning.  I think this is a reasonable
> > way to handle this until it gets fixed upstream.
> 
> Marc, Sebastian, does either of you have time to upload this patch, or
> would you prefer an NMU?
> 
> This is somewhat time-critical, because this RC bug will cause
> freeradius to be removed from testing.

Thanks for the heads-up ! Sorry for having let these FTBFS issues pile up :-(

I'm getting back on track and will take care of uploading 5.7.2 + the misc
fixes needed so the package builds again.

For this specific issue, I feel this fix would be better suited:
https://github.com/collectd/collectd/issues/2200

Cheers,
Marc

Bug#852924: collectd: FTBFS: ld: cannot find -lssl

[Marc Fournier]

On Sat, Jan 28, 2017 at 09:30:20AM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > /bin/bash ../libtool  --tag=CC   --mode=link x86_64-linux-gnu-gcc -Wall 
> > -Werror -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> > -Wno-error=deprecated-declarations -module -avoid-version 
> > -export-symbols-regex '\' -Wl,-z,relro -o notify_email.la 
> > -rpath /usr/lib/collectd notify_email.lo -lesmtp -lssl -lcrypto 
> > libtool: link: /usr/bin/x86_64-linux-gnu-nm -B  .libs/notify_email.o   | 
> > sed -n -e 's/^.*[   ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
> > ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' | /bin/sed 
> > 's/.* //' | sort | uniq > .libs/notify_email.exp
> > libtool: link: /bin/grep -E -e "\" 
> > ".libs/notify_email.exp" > ".libs/notify_email.expT"
> > libtool: link: mv -f ".libs/notify_email.expT" ".libs/notify_email.exp"
> > libtool: link: echo "{ global:" > .libs/notify_email.ver
> > libtool: link:  cat .libs/notify_email.exp | sed -e "s/\(.*\)/\1;/" >> 
> > .libs/notify_email.ver
> > libtool: link:  echo "local: *; };" >> .libs/notify_email.ver
> > libtool: link:  x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  
> > .libs/notify_email.o   -lesmtp -lssl -lcrypto  -g -O2 
> > -fstack-protector-strong -Wl,-z -Wl,relro   -Wl,-soname -Wl,notify_email.so 
> > -Wl,-version-script -Wl,.libs/notify_email.ver -o .libs/notify_email.so
> > /usr/bin/ld: cannot find -lssl
> > /usr/bin/ld: cannot find -lcrypto
> > collect2: error: ld returned 1 exit status
> 
> The full build log is available from:
>http://aws-logs.debian.net/2017/01/28/collectd_5.7.1-1_unstable.log

Nice catch, thanks !

One thing that puzzles me, is why didn't this pop up earlier. collectd does
*not* build-depend on libssl-dev. But according to the latest build log[1]
libssl1.0-dev gets installed nevertheless (making this mistake in
collectd's Makefile work by accident). This is not the case on the
AWS-based builder.

There seems to be some discrepancy between the official builders and the
AWS one (the latter being correct/stricter).

Cheers,
Marc

[1] 
https://buildd.debian.org/status/fetch.php?pkg=collectd=amd64=5.7.1-1=1485207190=0

Bug#852658: collectd-core: Won't start without non-required packages libsensors4 liboping0

[Marc Fournier]

On Thu, Jan 26, 2017 at 08:05:06AM +, Jan Huijsmans wrote:
> Package: collectd-core
> Version: 5.7.0-3
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Installation of collectd fails on the start of the package.
> The package misses files from libsensors4 liboping0, but these
> packages are only recommended or even suggested.

The configuration file shipped with the collectd package only loads these
plugins by default:

marc@lonquimay:~/src/pkg-collectd/debian$ grep ^LoadPlugin collectd.conf
LoadPlugin syslog
LoadPlugin battery
LoadPlugin cpu
LoadPlugin df
LoadPlugin disk
LoadPlugin entropy
LoadPlugin interface
LoadPlugin irq
LoadPlugin load
LoadPlugin memory
LoadPlugin processes
LoadPlugin rrdtool
LoadPlugin swap
LoadPlugin users

None of them depend on libsensors4 or liboping0 (the sensors and ping
plugins do, but they aren't enabled by default).

So my guess is that this system previously had a non-default configuration
(maybe some config snippets in /etc/collectd/collectd.conf.d/ ?) in place,
and installing/upgrading collectd-core made the missing runtime
dependencies strike out.

Are you able to confirm ?

NB: I agree such a failure is undesirable. The collectd plugin loading
mechanism could maybe be changed to not abort startup in this case (just
skip loading the plugin and emit an error message).

> Manual installation of libsensors4 liboping0 solved the issue.
> 
> When a package won't complete it's installation without a
> package, it should be a requirement, not anything less.
> 
> Probably an issue with the debian packages as well.

Are you aware of /usr/share/doc/collectd-core/README.Debian.plugins.gz ?

Cheers,
Marc

Bug#565738: drupal6: please lower #565738 severity to non-RC

[Marc Fournier]

Excerpt from /usr/share/doc/apache2.2-common/README.Debian.gz:

If the local administrator is not comfortable with packages
activating their config files by default, it is possible
to change the 'Include /etc/apache2/conf.d/' in apache2.conf
into 'Include /etc/apache2/conf.d.enabled/' and create that
directory. He can then put symlinks to the files in conf.d
which he wants to enable into conf.d.enabled.


Given this bug:
 - has a workaround as suggested above
 - is the same as #553173 and #604980
 - could apply to many other packages (nagios, gitweb, doc-central, etc)
 - should probably get fixed in apache itself (#605227)
 - is a release blocker

I suggest its severity should get lowered.

Many thanks !



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#553173: javascript-common: please lower #553173 severity to non-RC

[Marc Fournier]

block 553173 by 605227
thanks

Excerpt from /usr/share/doc/apache2.2-common/README.Debian.gz:

If the local administrator is not comfortable with packages
activating their config files by default, it is possible
to change the 'Include /etc/apache2/conf.d/' in apache2.conf
into 'Include /etc/apache2/conf.d.enabled/' and create that
directory. He can then put symlinks to the files in conf.d
which he wants to enable into conf.d.enabled.


Given this bug:
 - has a workaround as suggested above
 - is the same as #565738 and #604980
 - could apply to many other packages (nagios, gitweb, doc-central, etc)
 - should probably get fixed in apache itself (#605227)
 - is a release blocker

I suggest its severity should get lowered.

Many thanks !



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#474913: javascript-common: please lower #474913 severity to non-RC

[Marc Fournier]

clone 474913 -1
retitle 474913 javascript-common overrides /javascript globally in apache2
retitle -1 javascript-common overrides /javascript globally in lighttpd
notfound -1 5
thanks

Excerpt from /usr/share/doc/apache2.2-common/README.Debian.gz:

If the local administrator is not comfortable with packages
activating their config files by default, it is possible
to change the 'Include /etc/apache2/conf.d/' in apache2.conf
into 'Include /etc/apache2/conf.d.enabled/' and create that
directory. He can then put symlinks to the files in conf.d
which he wants to enable into conf.d.enabled.


Given this bug:
 - has a workaround as suggested above
 - is the same as #565738 and #604980
 - could apply to many other packages (nagios, gitweb, doc-central, etc)
 - should probably get fixed in apache itself (#605227)
 - is a release blocker

I suggest its severity should get lowered.

Furthermore, I'm splitting this bug in:
 - javascript-common overrides /javascript globally in apache2
 - javascript-common overrides /javascript globally in lighttpd

The latter only being in javascript-common/8, it doesn't affect squeeze and
therefore shouldn't be listed in squeeze release blockers.

Many thanks !



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#603789: cdargs should not depend on emacsen-common

[Marc Fournier]

Package: cdargs
Version: 1.35-5
Severity: normal
Tags: patch


I believe this problem can be fixed by removing emacsen-common from the
package dependencies.

This package does not benefit anyhow from having emacsen installed (although
the opposite is true).

Furthermore, when upgrading/installing version 1.35-5 of this package on a
stripped-down machine, it pulls down a whole load of stuff you probably don't
want:

# dpkg -l cdargs | grep cdargs
ii  cdargs  1.35-3  bookmarks and 
browsing for the cd command
# apt-get install cdargs=1.35-5  
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  anthy-common cdargs cpp cpp-4.4 defoma emacs23 emacs23-bin-common 
emacs23-common emacsen-common fontconfig
  fontconfig-config gconf2-common hicolor-icon-theme libanthy0 libasound2 
libatk1.0-0 libatk1.0-data
  libavahi-client3 libavahi-common-data libavahi-common3 libcairo2 libcroco3 
libcups2 libdatrie1 libdbus-glib-1-2
  libfont-freetype-perl libfontconfig1 libfontenc1 libfreetype6 libfribidi0 
libgconf2-4 libgd2-noxpm libgif4
  libgmp3c2 libgsf-1-114 libgsf-1-common libgtk2.0-0 libgtk2.0-bin 
libgtk2.0-common libice6 libidl0 libjasper1
  libjpeg62 libm17n-0 libmpfr4 liborbit2 libotf0 libpango1.0-0 
libpango1.0-common libpixman-1-0 libpng12-0
  librsvg2-2 libsm6 libthai-data libthai0 libtiff4 libxcb-render-util0 
libxcb-render0 libxcomposite1 libxcursor1
  libxdamage1 libxfixes3 libxfont1 libxft2 libxi6 libxinerama1 libxpm4 
libxrandr2 libxrender1 libxt6 m17n-contrib
  m17n-db ttf-dejavu-core x-ttcidfont-conf x11-common xfonts-encodings 
xfonts-utils
Suggested packages:
  cpp-doc gcc-4.4-locales defoma-doc psfontmgr dfontmgr emacs23-common-non-dfsg 
emacs23-el libasound2-plugins
  cups-common libgd-tools librsvg2-common gvfs libjasper-runtime m17n-docs 
ttf-japanese-gothic
  ttf-japanese-mincho ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp 
ttf-arphic-bsmi00lp ttf-arphic-gkai00mp
  ttf-arphic-bkai00mp librsvg2-bin gawk
The following NEW packages will be installed:
  anthy-common cpp cpp-4.4 defoma emacs23 emacs23-bin-common emacs23-common 
emacsen-common fontconfig
  fontconfig-config gconf2-common hicolor-icon-theme libanthy0 libasound2 
libatk1.0-0 libatk1.0-data
  libavahi-client3 libavahi-common-data libavahi-common3 libcairo2 libcroco3 
libcups2 libdatrie1 libdbus-glib-1-2
  libfont-freetype-perl libfontconfig1 libfontenc1 libfreetype6 libfribidi0 
libgconf2-4 libgd2-noxpm libgif4
  libgmp3c2 libgsf-1-114 libgsf-1-common libgtk2.0-0 libgtk2.0-bin 
libgtk2.0-common libice6 libidl0 libjasper1
  libjpeg62 libm17n-0 libmpfr4 liborbit2 libotf0 libpango1.0-0 
libpango1.0-common libpixman-1-0 libpng12-0
  librsvg2-2 libsm6 libthai-data libthai0 libtiff4 libxcb-render-util0 
libxcb-render0 libxcomposite1 libxcursor1
  libxdamage1 libxfixes3 libxfont1 libxft2 libxi6 libxinerama1 libxpm4 
libxrandr2 libxrender1 libxt6 m17n-contrib
  m17n-db ttf-dejavu-core x-ttcidfont-conf x11-common xfonts-encodings 
xfonts-utils
The following packages will be upgraded:
  cdargs
1 upgraded, 76 newly installed, 0 to remove and 0 not upgraded.
[...]


With cdargs not depending on emacsen-common, installation is clean and lean,
and upgrade from 1.35-3 works like a charm:

# dpkg -l cdargs | grep cdargs
ii  cdargs  1.35-3  bookmarks and 
browsing for the cd command
# apt-get install cdargs=1.35-5.1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  emacs23 xemacs21 emacsen
The following packages will be upgraded:
  cdargs
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/51.6 kB of archives.
After this operation, 12.3 kB disk space will be freed.
WARNING: The following packages cannot be authenticated!
  cdargs
Install these packages without verification [y/N]? y
(Reading database ... 25886 files and directories currently installed.)
Preparing to replace cdargs 1.35-3 (using ..././cdargs_1.35-5.1_amd64.deb) ...
Unpacking replacement cdargs ...
Processing triggers for man-db ...
Setting up cdargs (1.35-5.1) ...


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'testing-proposed-updates'), (500, 
'stable'), (300, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cdargs depends on:
ii  emacsen-common1.4.19 Common facilities for all emacsen
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.5-6  GCC support library
ii  libncurses5   5.7+20100313-4 shared libraries for terminal hand
ii  libstdc++64.4.5-6  

Bug#542815: maybe related to #538178 ?

[Marc Fournier]

I had the same error message when using mach and yum today, and found
out that a guy also reported this problem in #538178.

In my case, this was easily solved by removing the files in
/usr/lib/python2.5/site-packages/rpm/ (which didn't belong to any installed
package):

lrwxrwxrwx  1 root root   36 2008-05-22 13:54 _rpmmodule.a - 
/usr/share/pyshared/rpm/_rpmmodule.a
lrwxrwxrwx  1 root root   37 2008-05-22 13:54 _rpmmodule.la - 
/usr/share/pyshared/rpm/_rpmmodule.la
lrwxrwxrwx  1 root root   35 2008-05-22 13:54 __init__.py - 
/usr/share/pyshared/rpm/__init__.py

Maybe it would be an idea to investigate why different people have their
rpm-related python package get broken because of some (apparently)
generated files ?

Let me know if can be of any help !

Marc




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#509438: libaugeas-ruby: missing augeas.rb in package

[Marc Fournier]

Package: libaugeas-ruby
Version: 0.2.0-1
Severity: grave
Tags: patch
Justification: renders package unusable


The package ships without the ruby wrapper for augeas which is included in the
upstream ruby gem.

I believe the attached patch solves the problem.

By the way, I suggest decreasing debhelper version from 7 to 5 to allow folks
to backport the package to etch:


diff -urN libaugeas-ruby-0.2.0.orig/debian/compat 
libaugeas-ruby-0.2.0/debian/compat
--- libaugeas-ruby-0.2.0.orig/debian/compat 2008-12-22 12:55:24.0 +0100
+++ libaugeas-ruby-0.2.0/debian/compat  2008-12-22 12:51:36.0 +0100
@@ -1 +1 @@
-7
+5
diff -urN libaugeas-ruby-0.2.0.orig/debian/control 
libaugeas-ruby-0.2.0/debian/control
--- libaugeas-ruby-0.2.0.orig/debian/control  2008-12-22 12:55:24.0 
+0100
+++ libaugeas-ruby-0.2.0/debian/control 2008-12-22 12:51:36.0 +0100
@@ -2,7 +2,8 @@
 Section: libs
 Priority: optional
 Maintainer: Bart Cortooms b...@kumina.nl
-Build-Depends: debhelper (= 7), ruby1.8, ruby1.8-dev, ruby1.9, ruby1.9-dev, 
cdbs, ruby-pkg-tools (= 0.14), libaugeas-dev, pkg-config
+Build-Depends: debhelper (= 5), ruby1.8, ruby1.8-dev, ruby1.9, ruby1.9-dev, 
cdbs, ruby-pkg-tools (= 0.11), libaugeas-dev, pkg-config
 Standards-Version: 3.8.0
 Homepage: http://augeas.net/



-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'testing-proposed-updates'), (300, 
'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libaugeas-ruby depends on:
ii  libaugeas-ruby1.8 0.2.0-1Augeaus bindings for the Ruby lang

libaugeas-ruby recommends no packages.

libaugeas-ruby suggests no packages.

-- no debconf information
diff -urN libaugeas-ruby-0.2.0.orig/debian/libaugeas-ruby1.8.dirs libaugeas-ruby-0.2.0/debian/libaugeas-ruby1.8.dirs
--- libaugeas-ruby-0.2.0.orig/debian/libaugeas-ruby1.8.dirs	1970-01-01 01:00:00.0 +0100
+++ libaugeas-ruby-0.2.0/debian/libaugeas-ruby1.8.dirs	2008-12-22 12:51:17.0 +0100
@@ -0,0 +1 @@
+usr/lib/ruby/1.8
diff -urN libaugeas-ruby-0.2.0.orig/debian/libaugeas-ruby1.9.dirs libaugeas-ruby-0.2.0/debian/libaugeas-ruby1.9.dirs
--- libaugeas-ruby-0.2.0.orig/debian/libaugeas-ruby1.9.dirs	1970-01-01 01:00:00.0 +0100
+++ libaugeas-ruby-0.2.0/debian/libaugeas-ruby1.9.dirs	2008-12-22 12:51:17.0 +0100
@@ -0,0 +1 @@
+usr/lib/ruby/1.9
diff -urN libaugeas-ruby-0.2.0.orig/debian/rules libaugeas-ruby-0.2.0/debian/rules
--- libaugeas-ruby-0.2.0.orig/debian/rules	2008-12-22 12:55:24.0 +0100
+++ libaugeas-ruby-0.2.0/debian/rules	2008-12-22 12:51:17.0 +0100
@@ -6,4 +6,10 @@
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/ruby-pkg-tools/1/class/ruby-extconf-rb.mk
 
+install/libaugeas-ruby1.8::
+	cp $(CURDIR)/lib/augeas.rb $(CURDIR)/debian/libaugeas-ruby1.8/usr/lib/ruby/1.8/augeas.rb
+
+install/libaugeas-ruby1.9::
+	cp $(CURDIR)/lib/augeas.rb $(CURDIR)/debian/libaugeas-ruby1.9/usr/lib/ruby/1.9/augeas.rb
+
 DEB_RUBY_SETUP_CMD = $(CURDIR)/ext/augeas/extconf.rb