Bug 648134 - broken deps for ghc-xmonad-contrib
Summary: broken deps for ghc-xmonad-contrib
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ghc-xmonad-contrib
Version: 14
Hardware: All
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Ben Boeckel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-31 09:06 UTC by Fabien Georget
Modified: 2010-11-01 20:49 UTC (History)
4 users (show)

Fixed In Version: ghc-xmonad-contrib-0.9.1-8.fc14
Clone Of:
Environment:
Last Closed: 2010-11-01 20:49:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fabien Georget 2010-10-31 09:06:39 UTC
Description of problem:
I can't recompile xmonad with "xmonad --recompile" because the package xmonad-contrib seems to have broken dependancy :

[manawy@cafeline ~]$ ghc-pkg check 
There are problems in package xmonad-contrib-0.9.1:
  dependency "xmonad-0.9.1-f1132d530c8ecde0566fd1fa29b9f893" doesn't exist

The following packages are broken, either because they have a problem
listed above, or because they depend on a broken package.
xmonad-contrib-0.9.1


Version-Release number of selected component (if applicable):

Package version :
ghc-xmonad.x86_64                                0.9.1-8.fc14                    @updates-testing
ghc-xmonad-contrib.x86_64                        0.9.1-7.fc14.1                  @updates-testing
ghc-xmonad-contrib-devel.x86_64                  0.9.1-7.fc14.1                  @updates-testing
ghc-xmonad-contrib-prof.x86_64                   0.9.1-7.fc14.1                  @updates-testing
ghc-xmonad-devel.x86_64                          0.9.1-8.fc14                    @updates-testing
ghc-xmonad-prof.x86_64                           0.9.1-8.fc14                    @updates-testing
xmonad.x86_64                                    0.9.1-8.fc14                    @updates-testin

How reproducible:
When you want to recompile xmonad.hs

Steps to Reproduce:
1. modify your xmonad.hs (which must use some files of the xmonad-contrib package)
2. "xmonad --recompile"
  
Actual results:
Doesn't work, files from xmonad-contrib package are missing

Comment 1 Ben Boeckel 2010-10-31 16:08:42 UTC
Hmm. Seems as though the xmonad rebuild didn't go out with an xmonad-contrib update. I'll ask AutoQA to run `ghc-pkg check` as well to help try and catch things like this.

In the meantime, I'll rebuild xmonad-contrib and issue an update.

Comment 2 Fedora Update System 2010-10-31 16:20:18 UTC
ghc-xmonad-contrib-0.9.1-8.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/ghc-xmonad-contrib-0.9.1-8.fc14

Comment 3 Fedora Update System 2010-10-31 21:32:56 UTC
ghc-xmonad-contrib-0.9.1-8.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update ghc-xmonad-contrib'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/ghc-xmonad-contrib-0.9.1-8.fc14

Comment 4 Jens Petersen 2010-11-01 00:40:34 UTC
Sigh :-(

ghc-xmonad-contrib-0.9.1-7.fc14.1 was a releng rebuild for gcc
and so was built without the newer xmonad override in the buildroot.

Hence this breakage. :-(

Of course that is what I get for patching xmonad
and not testing the final builds before pushing...

Anyway in F15 we will include pkg hash metadata which
should avoid this kind of problem from recurring.

Comment 5 Jens Petersen 2010-11-01 02:29:31 UTC
Thanks Ben for pushing an update quickly to testing.

With Fedora 14 being released in the next day or two
it would be great if people could verify and give
this karma now, so that we can this fix pushed
to stable asap.

Comment 6 Fedora Update System 2010-11-01 20:49:28 UTC
ghc-xmonad-contrib-0.9.1-8.fc14 has been pushed to the Fedora 14 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.