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#59772 - [haskell-cmark-gfm] conflicts with cmark package
Attached to Project:
Community Packages
Opened by amaurydaviau (nam1962) - Thursday, 23 August 2018, 10:15 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 23 August 2018, 13:37 GMT
Opened by amaurydaviau (nam1962) - Thursday, 23 August 2018, 10:15 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 23 August 2018, 13:37 GMT
|
DetailsDescription: conflict with cmark
erreur : la validation de la transaction a échoué (conflit de fichiers) cmark-gfm : /usr/include/cmark.h est déjà présent dans le système de fichiers (appartenant à cmark) cmark-gfm : /usr/include/cmark_export.h est déjà présent dans le système de fichiers (appartenant à cmark) cmark-gfm : /usr/include/cmark_version.h est déjà présent dans le système de fichiers (appartenant à cmark) Des erreurs se sont produites, aucun paquet n’a été mis à jour. Additional info: * package version(s) haskell-cmark-gfm 0.1.3-6 cmark 0.28.3-1 haskell-cmark 0.5.6-9 * config and/or log files etc. Related to this bug : https://bugs.archlinux.org/task/58280?project=5&string=cmark-gfm Steps to reproduce: sudo pacman-mirrors -f0 && sudo pacman -Syyu |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Thursday, 23 August 2018, 13:37 GMT
Reason for closing: Duplicate
Additional comments about closing: It's not "related", it's the same exact bug as FS#58280 , plus oh wait, how about
FS#59727 and FS#59729 too.
Thursday, 23 August 2018, 13:37 GMT
Reason for closing: Duplicate
Additional comments about closing: It's not "related", it's the same exact bug as