Bug 30132 - Up2date gets error updating amanda
Summary: Up2date gets error updating amanda
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 7.1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-01 03:55 UTC by Mike Chambers
Modified: 2015-01-07 23:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-01 16:55:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Chambers 2001-03-01 03:55:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)


When trying to update all available packages, or just amanda itself, 
up2date errors with dependency problem

Reproducible: Always
Steps to Reproduce:
1.try to update all packages
2.try to update just amanda package
3.
	

Actual Results:  Get error stating ..

"Could not solve dependency libamanda-2.4.2.so"

Expected Results:  Should update amanda as this program hasn't been 
touched except during initial wolverine install.

I do have kernel 2.4.2 installed/compiled so not sure if this plays a part 
or not, but it shouldn't.  Just thought I should mention it.

Comment 1 Adrian Likins 2001-03-01 16:21:09 UTC
This is more or less "notabug". What is happening is that
amanda has flagged configuration files, and up2date does a config
file check for these packages and by default, does not install
some of the updated amanda packages because of this. 

The easiest thing to do is to run the gui version, and select
all the amanda packages to be upgraded in the "Packages marked to be
skipped list" screen. If all the packages are selected, this depenency
error will not occur.

Comment 2 michaelc 2001-03-01 16:55:45 UTC
Ok thanks.  I do have couple amanda packages that are marked as changed so I 
will look into trying that tonight.


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