Package: cowbuilder
Version: 0.70
Severity: minor
Tags: patch

Dear Maintainer,

While trying to run cowbuilder --update quietly from a cronjob (using 
redirections), I noticed that it currently sends benign (info) messages to 
stderr.
I assume those are benign since they appear with the info level everytime I run 
cowbuilder.
Also, a comment in the code suggests at least one of those messages is expected.
Please consider sending those messages to stdout instead (see attached patch 
against latest version of cowbuilder).

How to reproduce:
1. Create a new chroot environment
2. Try to update it using cowbuilder --update while redirecting stdout to 
/dev/null

root@localhost# cowbuilder --update --architecture i386 --distribution jessie 
--basepath /var/cache/pbuilder/base-jessie_i386.cow > /dev/null
I: removed stale ilistfile /var/cache/pbuilder/build//cow.26250/.ilist


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

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

Versions of packages cowbuilder depends on:
ii  cowdancer  0.70
ii  libc6      2.16-0experimental1
ii  pbuilder   0.213

cowbuilder recommends no packages.

cowbuilder suggests no packages.

-- no debconf information
--- a/cowdancer-0.73/cowbuilder.c	2014-01-04 13:31:58.000000000 +0100
+++ b/cowdancer-0.73/cowbuilder.c	2014-01-04 13:33:49.000000000 +0100
@@ -198,13 +198,11 @@
       /* if there was no ilist file in the beginning, that's not a
 	 problem.
        */
-      fprintf(stderr, "I: unlink for ilistfile %s failed, it didn't exist?\n",
-	      ilistfile);
+      printf("I: unlink for ilistfile %s failed, it didn't exist?\n", ilistfile);
     }
   else
     {
-      fprintf(stderr, "I: removed stale ilistfile %s\n",
-	      ilistfile);
+      printf("I: removed stale ilistfile %s\n", ilistfile);
     }
   free(ilistfile);
 

Reply via email to