he package
site). Investigating a bit further I noticed this bot does not seem to
do any checks if the package is still buildable or anything [3]. My
question now: is there any policy about such bots? Are they allowed?
Should they at least test if the package still builds before uploading
the package upda
Hi,
at least yay [1] has a feature which does exactly this. It fetches the
upstream repos of VCS packages when it's told to look for updates and
then also suggests updating the VCS packages, if there are new commits
upstream since the last rebuild.
Glad to help
j.r
[1] https://github.com/
debug
this further, could somebody please help me or at least give me a hint?
Thanks in advance
j.r
[1]
https://wiki.archlinux.org/title/Python%20package%20guidelines#Standards_based_(PEP_517)
[2] https://aur.archlinux.org/packages/telegram-tg
hip with distro obtained keys.
Following up this answer, I'm thinking about what is the best way to get
the client key during the build phase without the user needing to edit
the PKGBUILD?
Best regard
j.r
Should we require users to create their own
client secret, which is pretty bad UX?
Best regards
j.r
Yeah I would also expect that they would become orphaned. But anyway I
brought them back by pushing to the repos.
Thanks for your quick help (also thanks to Morten)
j.r
On 20/12/30 13:41, Morten Linderud via aur-general wrote:
User deleted their account which deleted the packages.
I would
Does somebody know what happened with them / why they where removed?
Thanks
j.r
