Bug 551025 - blacs fails to upgrade from -33 to -34
Summary: blacs fails to upgrade from -33 to -34
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: blacs
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-28 14:59 UTC by Chris Schanzle
Modified: 2010-01-12 23:45 UTC (History)
3 users (show)

Fixed In Version: 1.7.5-8.fc12.1
Clone Of:
Environment:
Last Closed: 2010-01-12 23:44:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Schanzle 2009-12-28 14:59:55 UTC
Did we lose blacs-lam-1.1-34?


# yum update
Loaded plugins: downloadonly, fastestmirror, priorities, protectbase, refresh-packagekit, security
Loading mirror speeds from cached hostfile
 * fedora: darkstar.cam.nist.gov
 * rpmfusion-free: mirror.liberty.edu
 * rpmfusion-free-updates: mirror.liberty.edu
 * rpmfusion-nonfree: mirror.liberty.edu
 * rpmfusion-nonfree-updates: mirror.liberty.edu
 * updates: darkstar.cam.nist.gov
1 packages excluded due to repository priority protections
0 packages excluded due to repository protections
Skipping security plugin, no data
Setting up Update Process
Resolving Dependencies
Skipping security plugin, no data
--> Running transaction check
--> Processing Dependency: blacs-common = 1.1-33.fc12 for package: blacs-lam-1.1-33.fc12.x86_64
---> Package blacs-common.x86_64 0:1.1-34.fc12.1 set to be updated
--> Finished Dependency Resolution
blacs-lam-1.1-33.fc12.x86_64 from installed has depsolving problems
  --> Missing Dependency: blacs-common = 1.1-33.fc12 is needed by package blacs-lam-1.1-33.fc12.x86_64 (installed)
Error: Missing Dependency: blacs-common = 1.1-33.fc12 is needed by package blacs-lam-1.1-33.fc12.x86_64 (installed)
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest

Comment 1 Chris Schanzle 2010-01-01 16:29:46 UTC
My Fedora systems with R-RScaLAPACK depend on blacs-lam and fail to yum-cron (auto-update) without manual intervention, so this is rather annoying.  Can I help by diving into the spec differences between the versions?

Comment 2 Pierre-YvesChibon 2010-01-02 14:55:00 UTC
same issue for me:

blacs-lam-1.1-33.fc12.x86_64 from installed has depsolving problems
  --> Missing Dependency: blacs-common = 1.1-33.fc12 is needed by package blacs-lam-1.1-33.fc12.x86_64 (installed)


Also came from the yum install R-\* so R-RScaLAPACK.

Comment 3 Tom "spot" Callaway 2010-01-02 17:31:45 UTC
I should be able to fix this next week when I have a bit more time.

Comment 4 Tom "spot" Callaway 2010-01-08 18:01:39 UTC
This actually has nothing to do with R-RScaLAPACK, and everything to do with blacs. I'm going to push an update to fix it on F-12.

Comment 5 Fedora Update System 2010-01-12 23:44:52 UTC
scalapack-1.7.5-8.fc12.1, orsa-0.7.0-11.fc12.1, mpich2-1.2.1-2.fc12, blacs-1.1-34.fc12.3 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2010-01-12 23:45:01 UTC
scalapack-1.7.5-8.fc12.1, orsa-0.7.0-11.fc12.1, mpich2-1.2.1-2.fc12, blacs-1.1-34.fc12.3 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2010-01-12 23:45:09 UTC
scalapack-1.7.5-8.fc12.1, orsa-0.7.0-11.fc12.1, mpich2-1.2.1-2.fc12, blacs-1.1-34.fc12.3 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2010-01-12 23:45:17 UTC
scalapack-1.7.5-8.fc12.1, orsa-0.7.0-11.fc12.1, mpich2-1.2.1-2.fc12, blacs-1.1-34.fc12.3 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


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