First Last Prev Next    This bug is not in your last search results.
Bug 7657 - up2date wipes out .mailcap file first time it runs
up2date wipes out .mailcap file first time it runs
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
6.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 1999-12-07 14:02 EST by Mark Lord
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-24 13:51:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Mark Lord 1999-12-07 14:02:45 EST 
When the redhat update agent is run for the very first time,
it wipes out the user's ~/.mailcap file, replacing it with
two new lines for the update manager.

Once the two lines are in ~/.mailcap, the problem goes away.

Not sure where the bug is, since the /sbin/up2date script
appears to try to open the .mailcap in "w+" mode.. maybe this
is not a valid mode in Pythonspeak?

Cheers

mlord@pobox.com
Comment 1 Mark Lord 1999-12-07 14:16:59 EST 
Ahh.. looked in the Python references, and the "w+" mode means "truncate".
This script /usr/sbin/up2date should be using "w" instead of "w+" when
opening the ~/.mailcap file for updating!!

-ml
Comment 2 Mark Lord 1999-12-07 14:18:59 EST 
Ooopps.. meant to say that open mode should be "a", not "w" or "w+"!!
Comment 3 Preston Brown 2000-02-24 13:51:59 EST 
this is very true.  fixed for 6.2.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.