Bug 176763 - Releases of R should be co-ordinated with dependent packages
Summary: Releases of R should be co-ordinated with dependent packages
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: R
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 176762 177078
TreeView+ depends on / blocked
 
Reported: 2006-01-01 21:13 UTC by Alex Lancaster
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-04-07 19:23:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alex Lancaster 2006-01-01 21:13:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Galeon/2.0.0

Description of problem:
Releases of R should be co-ordinated with other dependent packages. Case in point: the upgrade of R to 2.2.1 breaks the rpy package (bug #176762), and there maybe others.  Unfortunately rpy doesn't have an explicit dependency on a particular R version so it makes it a bit difficult to know this dependency or check it automatically (it probably should be added), but rpy will fail at runtime.  This bug is a tracker for other R version dependent packages and to bring it to the R maintainer's notice that co-ordination with dependent packages is required to avoid breakage.

Version-Release number of selected component (if applicable):
R-2.2.1-2.fc4

How reproducible:
Always

Steps to Reproduce:
1. See bug #176762
  

Additional info:

Comment 1 Tom "spot" Callaway 2006-04-07 19:22:39 UTC
To help manage issues like this, I've created a mailing list: fedora-r-devel-list

http://www.redhat.com/mailman/listinfo/fedora-r-devel-list

Comment 2 Alex Lancaster 2006-04-07 20:25:54 UTC
Any reason that the archives for this list aren't public?

Comment 3 Tom "spot" Callaway 2006-04-07 20:35:36 UTC
Oversight? :) Should be public now.


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