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#60764 - [lhasa] unnecessary conflict with aur/lha
Attached to Project:
Community Packages
Opened by Mantas Mikulėnas (grawity) - Saturday, 10 November 2018, 23:24 GMT
Last edited by Levente Polyak (anthraxx) - Sunday, 11 November 2018, 10:41 GMT
Opened by Mantas Mikulėnas (grawity) - Saturday, 10 November 2018, 23:24 GMT
Last edited by Levente Polyak (anthraxx) - Sunday, 11 November 2018, 10:41 GMT
|
Detailslhasa has conflicts=(lha) in it, even though it ships *none* of the files that are also present in lha, therefore no actual conflicts. This seems like it should be removed.
|
This task depends upon
Closed by Levente Polyak (anthraxx)
Sunday, 11 November 2018, 10:41 GMT
Reason for closing: Not a bug
Sunday, 11 November 2018, 10:41 GMT
Reason for closing: Not a bug
Comment by Mantas Mikulėnas (grawity) -
Saturday, 10 November 2018, 23:44 GMT
Actually nevermind that – I was looking at the wrong filelist. They do conflict.
Comment by Doug Newgard (Scimmia) -
Sunday, 11 November 2018, 00:20 GMT
A community package doesn't need to conflict with an AUR one, though.