FS#21335 - [haskell-mtl] preupgrade script fails
Attached to Project:
Arch Linux
Opened by Jakob Gruber (schuay) - Tuesday, 19 October 2010, 10:33 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Friday, 21 January 2011, 06:54 GMT
Opened by Jakob Gruber (schuay) - Tuesday, 19 October 2010, 10:33 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Friday, 21 January 2011, 06:54 GMT
|
Details
Description:
This probably doesn't matter ATM as only the pkgrel has been incremented, but it might lead to problems if a new pkgver is released? Not sure.. ghc-pkg: unregistering mtl-1.1.0.2 would break the following packages: xmonad-contrib-0.9.1 xmonad-0.9.1 (use --force to override) error: command failed to execute correctly (2/5) upgrading haskell-mtl [######################] 100% Additional info: * package version(s) haskell-mtl 1.1.0.2-5 * config and/or log files etc. Steps to reproduce: Upgrade haskell-mtl (1.1.0.2-4 -> 1.1.0.2-5) while xmonad-contrib is installed. |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Friday, 21 January 2011, 06:54 GMT
Reason for closing: Fixed
Additional comments about closing: All packages build in the last three months have the correct flag set.
Friday, 21 January 2011, 06:54 GMT
Reason for closing: Fixed
Additional comments about closing: All packages build in the last three months have the correct flag set.
Comment by
Andrzej Giniewicz (Giniu) -
Thursday, 21 October 2010, 12:44 GMT
Comment by
Rémy Oudompheng (remyoudompheng) -
Sunday, 31 October 2010, 09:44 GMT
It actually happens for all packages on which something depends in
cabal. It sounds like bigger issue with approach to updating
Haskell packages in whole. Should the unregistering be forced?
Assuming that all dependent packages will be rebuilt together with
their dependencies, forcing unregister is safe. If it is minor
update that don't change anything important, it's probably safe
too?
The --force flag is gradually added to the unregister scripts for
Haskell packages.