termux-packages icon indicating copy to clipboard operation
termux-packages copied to clipboard

lyrebird package outdated

Open someone2037492034 opened this issue 2 weeks ago • 8 comments

Hello, the lyrebird package received a new version, but it's outdated in the main repo. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/tree/lyrebird-0.7.0?ref_type=tags

someone2037492034 avatar Dec 08 '25 07:12 someone2037492034

The lyrebird package does have auto updates enabled and I don't see any auto update failure issue for it. Will need to investigate.

TomJo2000 avatar Dec 08 '25 08:12 TomJo2000

Alright I've dug into this and we're getting back a null for the latest version. It looks like the Tor Gitlab is blocking requests to that URI path.

TomJo2000 avatar Dec 08 '25 08:12 TomJo2000

could it be changed to TERMUX_PKG_UPDATE_METHOD=repology to solve this?

robertkirkman avatar Dec 08 '25 11:12 robertkirkman

could it be changed to TERMUX_PKG_UPDATE_METHOD=repology to solve this?

That's already what it uses.

The gitlab method only applies for packages with gitlab.com srcurls. I'm actually refactoring that right now to work for any gitlab instance. Almost done, just needs some spot fixes for a couple packages.

lyrebird does happen to be a package where both the Gitlab and Repology methods are currently misbehaving.

TomJo2000 avatar Dec 08 '25 15:12 TomJo2000

Alright I've dug into this and we're getting back a null for the latest version. It looks like the Tor Gitlab is blocking requests to that URI path.

Oh, thanks for looking into this! So would the fix bypass that rate limiting error or something?

someone2037492034 avatar Dec 08 '25 16:12 someone2037492034

I don't think it's a rate limiting error. I haven't actually gotten to looking at lyrebird specifically yet. I refactored the gitlab update method to work for other instances than gitlab.com automatically, and it's been a game of whack-a-mole to find what errors that has caused for various packages.

Because they should have been using the gitlab method automatically, but weren't.

Edit: here's the current fail list.

1. netcat-openbsd
2. cmocka
3. libgedit-gtksourceview
4. libgedit-amtk
5. libgedit-tepl
6. lyrebird
7. gegl
8. libgf2x
9. xkeyboard-config
10. liblmdb
11. babl
12. media-types
13. libgedit-gfls
14. snowflake
15. xeyes
16. dbus-python
17. torsocks

TomJo2000 avatar Dec 08 '25 16:12 TomJo2000

I noticed that when I visit https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/tree/lyrebird-0.7.0?ref_type=tags with a blank browser, I get a rate limited request error (429) and am unable to browse the tag before opening the instance differently.

someone2037492034 avatar Dec 08 '25 19:12 someone2037492034

I got it working in my refactor branch. All the Gitlab instance packages are working now, I'm running final validation on a full update run right now.

Edit: new fail list.

1. wordgrinder
2. oma
3. hangover-wine
4. iverilog
5. openssh
6. mdbook-katex

Oh that's way less mayhem than I expected.

TomJo2000 avatar Dec 08 '25 19:12 TomJo2000