[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1096144: marked as done (ben tracker -g something -q isn't really quiet)

Your message dated Tue, 18 Feb 2025 13:28:06 +0100
with message-id <e897ce662e8125d9cffa248f8341f683@dogguy.org>
and subject line Re: Bug#1096144: ben tracker -g something -q isn't really quiet
has caused the Debian Bug report #1096144,
regarding ben tracker -g something -q isn't really quiet
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 owner@bugs.debian.org
immediately.)


-- 
1096144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096144
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ben
Version: 0.10.1+b1
Severity: normal

Hi,
Today respighi (the host that runs the Release Team tools) was upgraded to bookworm. Since the upgrade we're getting cron e-mails about errors from ben. It turns out ben runs fine, but it does output to stderr. 

elbrus@respighi:/home/release/www/transitions$ sudo -u release make cron
umask 0002; nice -n 10 ionice -c 3 /usr/bin/ben tracker -g /srv/release.debian.org/www/transitions/global.conf -u -q 
read_global_config /srv/release.debian.org/www/transitions/global.conf

Note the "read_global_config" line that wasn't there apparently in bullseye.

I can reproduce with:
elbrus@respighi:/home/release/www/transitions$ /usr/bin/ben tracker -g xxx --help > /dev/null 
read_global_config xxx

Thanks for maintaining ben

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Version: 0.10.2

On 2025-02-17 21:23, Paul Gevers wrote:

If it's currently present, please just fix it in unstable. If it's
already fixed, then just close the bug with the right meta-info.



Fixed already.

--
Mehdi

--- End Message ---
Reply to: