Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52505 - xmonad unconfigurable while xmonad, xmonad-contrib out of sync
Attached to Project:
Arch Linux
Opened by Petrus (petrus) - Thursday, 12 January 2017, 09:29 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 12 January 2017, 14:12 GMT
Opened by Petrus (petrus) - Thursday, 12 January 2017, 09:29 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 12 January 2017, 14:12 GMT
|
DetailsDescription:
When xmonad and xmonad-contrib are not upgraded simultaneously xmonad becomes unconfigurable until the two packages in sync again. ghc uses a library hash to precisely check/satisfy dependencies so arch package system won't avoid this situation to occur. It is reasonable to assume that most users of xmonad also uses xmonad-contrib so for them the out sync situation breaks xmonad. I suggest to tightly link the upgrades of the two packages somehow to avoid this problem. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 12 January 2017, 14:12 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#52499
Thursday, 12 January 2017, 14:12 GMT
Reason for closing: Duplicate
Additional comments about closing: