[...] a different package which got uploaded by the user
Not too much to contribute to the existing conversation. But if a
maintainer didn't put their name/email at the top of a PKGBUILD, one can
always have a look at the git history instead:
$ git clone https://aur.archlinux.org/icu73-bin.
Am 12. Februar 2025 14:08:34 MEZ schrieb Polarian :
>Hello,
>
>> They put their e-mail in a PKGBUILD file for another of their AUR
>> PKGBUILD files.
>>
>> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=libzim8
>
>Michal has already said that the PKGBUILD does not have a email
>provided, pl
Hello,
> They put their e-mail in a PKGBUILD file for another of their AUR
> PKGBUILD files.
>
> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=libzim8
Michal has already said that the PKGBUILD does not have a email
provided, please see [1] there is no email only a username/name?
I can
They put their e-mail in a PKGBUILD file for another of their AUR PKGBUILD
files.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=libzim8
If the maintainer is not active and does not respond within a week or two then
you could mark the package as out of date and then do an orphan reques
Hi!
I recently fixed a bug in icu73-bin AUR package and started to investigate how to push
this properly to the maintainer. Wiki clearly says that one should avoid pasting patches
into the comments section and rather email the patch to the maintainer. However, the
profile detail of the maintai
