Issue tracker moved to https://gitlab.archlinux.org/archlinux/aurweb/-/issues
FS#18758 - Allow to upload attachment for AUR
Attached to Project:
AUR web interface
Opened by 甘露(Lu Gan) (ganlu) - Saturday, 20 March 2010, 11:25 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 17 November 2012, 15:57 GMT
Opened by 甘露(Lu Gan) (ganlu) - Saturday, 20 March 2010, 11:25 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 17 November 2012, 15:57 GMT
|
DetailsDescription:
Please allow attachment in AUR, so at some case we can upload patch for PKGBUILD, whtch will make thing much easier. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Always |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Saturday, 17 November 2012, 15:57 GMT
Reason for closing: Won't implement
Saturday, 17 November 2012, 15:57 GMT
Reason for closing: Won't implement
Comment by Lukas Fleischer (lfleischer) -
Sunday, 30 May 2010, 11:30 GMT
Patches specified in the PKGBUILD's "source" array are included in the source tarball automatically.
Comment by Ray Rashif (schivmeister) -
Monday, 07 June 2010, 18:35 GMT
What the reporter meant is a patch against the PKGBUILD/package, not against its result/content. For now the comment system is being used to post changes to PKGBUILDs. The thing is, the AUR is not a bug-tracking system; uploading patches is a bug-tracking feature.
Comment by canyonknight (canyonknight) -
Saturday, 17 November 2012, 15:53 GMT
-1 from me on this. Attachments could just complicate things and would be another feature to maintain.