Package: debtags
Version: 1.7.2
Severity: minor
Tags: patch

*** Please type your report below this line ***

It's nice to have a daily-update cron-job for debtags (at least on
my Testing machine; it'll be a bit pointless once it reaches the
Stable ones).  But every time it successfully updates via http, it's
going to send me an e-mail about it:

 /etc/cron.daily/debtags:         
 --13:40:21--  http://debtags.alioth.debian.org/tags//vocabulary.gz
         => 
`/var/lib/debtags/debtags-fetch-http---debtags.alioth.debian.org-tags-.voc.gz.tmp'
 Resolving debtags.alioth.debian.org... 217.196.43.134         
 Connecting to debtags.alioth.debian.org|217.196.43.134|:80... connected.
 HTTP request sent, awaiting response... 200 OK
 Length: 14,142 (14K) [application/x-gzip]
         
    0K .......... ...                                        100% 100.52 KB/s
             
 13:40:22 (100.52 KB/s) - 
`/var/lib/debtags/debtags-fetch-http---debtags.alioth.debian.org-tags-.voc.gz.tmp'
 saved [14142/14142]
        
  --13:40:22-- http://debtags.alioth.debian.org/tags//tags-current.gz
        => 
`/var/lib/debtags/debtags-fetch-http---debtags.alioth.debian.org-tags-.tag.gz.tmp'
 Resolving debtags.alioth.debian.org... 217.196.43.134
 Connecting to debtags.alioth.debian.org|217.196.43.134|:80... connected.
 HTTP request sent, awaiting response... 200 OK
 Length: 273,193 (267K) [application/x-gzip]
         
    0K .......... .......... .......... .......... .......... 18% 138.59 KB/s
   50K .......... .......... .......... .......... .......... 37% 270.55 KB/s
  100K .......... .......... .......... .......... .......... 56%  71.63 KB/s
  150K .......... .......... .......... .......... .......... 74%  89.58 KB/s
  200K .......... .......... .......... .......... .......... 93%  91.84 KB/s
  250K .......... ......                                     100% 128.04 KB/s
           
 13:40:24 (107.69 KB/s) - 
`/var/lib/debtags/debtags-fetch-http---debtags.alioth.debian.org-tags-.tag.gz.tmp'
 saved [273193/273193]

I really don't want to hear about this every morning.  The real
solution would be to use "debtags --quiet update", but there's no
such thing; the workaround I've been using in my own local version
of this cronjob was:

 debtags update 2>/dev/null || echo debtags update error

(well, actually I used logger, not echo, but not everybody runs a
logchecker.) 

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i586)

Kernel: Linux 2.6.21.xan
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages debtags depends on:
ii  apt [libapt-pkg-libc6.5 0.7.3            Advanced front-end for dpkg
ii  libc6                   2.5-9+b1         GNU C Library: Shared libraries
ii  libept0                 0.5.9+b1         High-level library for managing De
ii  libgcc1                 1:4.2-20070627-1 GCC support library
ii  libstdc++6              4.2-20070627-1   The GNU Standard C++ Library v3
ii  libxapian15             1.0.1-1          Search engine library
ii  perl                    5.8.8-7          Larry Wall's Practical Extraction 
ii  zlib1g                  1:1.2.3.3.dfsg-3 compression library - runtime

debtags recommends no packages.

-- no debconf information
diff -ru debtags-1.7.2.old/debian/debtags.cron.daily debtags-1.7.2/debian/debtags.cron.daily
--- debtags-1.7.2.old/debian/debtags.cron.daily	2007-06-22 14:35:01.000000000 +0100
+++ debtags-1.7.2/debian/debtags.cron.daily	2007-07-06 15:30:48.000000000 +0100
@@ -1,4 +1,4 @@
 #!/bin/sh
 
 # Update the data and index files of Debtags
-debtags update
+debtags update 2>/dev/null || echo debtags update error

Reply via email to