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#37477 - {archweb} colons in depends (for epoch) not recognized correctly on website
Attached to Project:
Arch Linux
Opened by Felix Yan (felixonmars) - Friday, 25 October 2013, 05:12 GMT
Last edited by Felix Yan (felixonmars) - Tuesday, 28 January 2014, 15:38 GMT
Opened by Felix Yan (felixonmars) - Friday, 25 October 2013, 05:12 GMT
Last edited by Felix Yan (felixonmars) - Tuesday, 28 January 2014, 15:38 GMT
|
DetailsAs xapian-core added an epoch to downgrade back to 1.2.15 (1:1.2.15), I have to use xapian-core=1:1.2.15 in depends for python2-xapian. But this dependency is not shown correctly on the website - it was treated the same way as reason for optdepends and thus "xapian-core=1" becomes virtual.
Link: https://www.archlinux.org/packages/community/i686/python2-xapian/ |
This task depends upon
Comment by Dan McGee (toofishes) -
Wednesday, 06 November 2013, 15:47 GMT
This is probably a simple fix, I've just never actually tested this case. I'll take a look soon, thanks for noticing!
Comment by Dan McGee (toofishes) -
Thursday, 07 November 2013, 23:39 GMT
Fixed in my (local) archweb checkout, and for now, I updated the rows in the database that were affected by this parsing problem.
Comment by Felix Yan (felixonmars) -
Tuesday, 28 January 2014, 15:38 GMT
Looks good here. Thanks a lot!