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 request to take over the package. I did that for the "blabel" package a few years ago since the previous maintainer didn't update it. https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/message/UJ7ZVCLWC5HEYJ6SPVVXUUPDP7CGONVD/ https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/message/JNFOET4CPGWVPMWFOSCAYGSFSB5VSY4V/ Venlig hilsen / Best regards Morten Jakobsen On Tuesday, February 11th, 2025 at 20:03, Michal Feix <michal@feix.family> wrote: > 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 maintainer with > this package shows his e-mail address as "hidden". The PKGBUILD itself also > does not have any maintainer entry that could be used to identify contact > details of the maintainer so I broke the wiki rule and pasted the patch into > the comments section. As the maintainer did not responded yet, my question in > the meantime is - how is one supposed to discover maintainer's contact email > in such case? > > Thanks, > > -- > Michal
