Bug 117681 - Why up2date can't be quiet when there is nothing to say?
Summary: Why up2date can't be quiet when there is nothing to say?
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: up2date
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Fanny Augustin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-07 02:47 UTC by Petri T. Koistinen
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-22 21:22:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Petri T. Koistinen 2004-03-07 02:47:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040122 Debian/1.6-1

Description of problem:
I want to keep my system up to date. I use script like this:

$ cat /etc/cron.daily/up2date.sh
#!/bin/sh
 
up2date --nox -u | egrep -v '^($|Fetching|Name|---|All)'

Why up2date don't have --non-verbose option that will supress all
output when there is nothing to say, i.e. no updates.

Version-Release number of selected component (if applicable):
up2date-4.3.11-2.1

How reproducible:
Always

Steps to Reproduce:
1. up2date -u daily
2. if no update is available you will only see useless noise

Additional info:

Comment 1 Petri T. Koistinen 2004-03-22 20:48:50 UTC
Oh, you don't bother even to leave a comment why you closed this
enchancement request. I find that quite arrogant, but what else you
can expect from somebody living in USA.

Comment 2 Adrian Likins 2004-03-22 21:10:45 UTC
I'm not going to fix it.

Comment 3 Petri T. Koistinen 2004-03-22 21:15:32 UTC
I am sorry, that's little bit too harsh comment. I did try to say:
"Please, don't ignore me.", but that's too late now, I guess.

Comment 4 Petri T. Koistinen 2004-03-22 21:17:14 UTC
Thanks for comment. It is OK to say that don't want to fix it. Fine.
I'll just my script.


Note You need to log in before you can comment on or make changes to this bug.