Bug 177233 - recent upgrade of net6 package breaks dependency for obby (and gooby) packages
Summary: recent upgrade of net6 package breaks dependency for obby (and gooby) packages
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: obby
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Luke Macken
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-08 00:53 UTC by John Guthrie
Modified: 2016-09-20 02:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-01-10 22:39:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Guthrie 2006-01-08 00:53:13 UTC
Description of problem:
When I run up2date -u, it runs just fine until it verifies the dependencies.  At
that time, I get the message:

There was a package dependency problem. The message was:

Unresolvable chain of dependencies:
gobby  0.2.2-6.fc4                       requires libnet6-1.1.so.0
obby  0.2.0-6.fc4                        requires libnet6-1.1.so.0

As it turns out, it appears that the net6 package was recently upgraded to
version 1.2.2-1.fc4.  So it looks like, the library that obby and gobby need are
being pulled out from under them.  I'm guessing that all this really requires is
a recompiling and release increment of the obby and gobby packages.

Version-Release number of selected component (if applicable):
obby-0.2.0-6.fc4

How reproducible:
Every time

Steps to Reproduce:
1.Find a machine that has obby installed on it.
2.Run up2date -u
  
Actual results:
I got the error message indicated above, and up2date did nothing.

Expected results:
I should have received no error message, and up2date should have updated all of
the packages.

Additional info:

Comment 1 Luke Macken 2006-01-10 22:39:43 UTC
I build obby-0.3.0-3 and gobby-0.3.0-2 for FC4.  They should hit the repos in
the near future.


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