Community Packages

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!
Tasklist

FS#65236 - [alacritty-terminfo] incorrect arch

Attached to Project: Community Packages
Opened by Filipe Laíns (FFY00) - Wednesday, 22 January 2020, 01:36 GMT
Last edited by Jiachen Yang (farseerfc) - Wednesday, 22 January 2020, 02:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Rebischke (Shibumi)
Jiachen Yang (farseerfc)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

allacritty-terminfo should be `any`

Use case where it is relevant: ssh-ing to a machine of different arch
This task depends upon

Closed by  Jiachen Yang (farseerfc)
Wednesday, 22 January 2020, 02:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  It's a bug of dbscripts
Comment by Jiachen Yang (farseerfc) - Wednesday, 22 January 2020, 01:51 GMT
Yes, I also want alacritty-terminfo to be arch=("any").
But there is an issue (or missing feature) of our repository managing infrastructure, that prevents the packages from the same pkgbase to have different arch= .
So we cannnot package alacritty-terminfo as arch=("any") unless we separate it from alacritty package and do packaging twice, or until we fix the issue in our repository infrastructure.
If you search for terminfo in our repository, you will find many terminal's terminfo is having arch=("x86_64"), I believe it's for the same reason.
Comment by Filipe Laíns (FFY00) - Wednesday, 22 January 2020, 01:53 GMT
Yeah, Eli just told me that on IRC. Sorry.

We can close for now and revisit when dbscripts gets updated to handle this case.

Loading...