Missing tag `ua-parser-rs-0.1.5`

[dotlambda]

Version 0.1.5 of us-parser-rs was released on PyPI but is missing from https://github.com/ua-parser/uap-rust/tags.

[dotlambda]

Actually it looks like the code was moved to https://github.com/ua-parser/uap-python/tree/master/ua-parser-rs.
But the link on PyPI still points to this repo and the other one also doesn't have an appropriate tag.

[masklinn]

Actually it looks like the code was moved to https://github.com/ua-parser/uap-python/tree/master/ua-parser-rs.

Yes, I decided the python repository was a better home for its accelerator than this one in the end. Completely forgot to ping you, sorry about that. Thanks for the note about the pypi links, I missed them during the move.

I pushed a ua-parser-rs tag by hand.

[dotlambda]

I pushed a ua-parser-rs tag by hand.

Thanks! Would you be able to do the same for ua-parser-builtins?

[masklinn]

Would you be able to do the same for ua-parser-builtins?

I fear not, the part of -builtins that’s in the repository is just the building, it otherwise derives from uap-core directly (on the 1st of each month a cron runs, fetches the latest -core, and builds a release), and that is not synchronized.

[dotlambda]

Couldn't the cron create the tag?

[masklinn]

There is nothing to tag, the tags would have to be in -core.

[dotlambda]

the tags would have to be in -core.

That sounds fine to me.

[masklinn]

That sounds fine to me.

It's not fine because it's not an option: the entire reason I ended up doing monthly cuts of whatever core was at is that they stopped emitting tags and didn't respond to inquiries about it.

Honestly if you want to publish builtins for nix you can just take the build scripts and build whatever commit of core you want, my picking the first of the month was entirely arbitrary. If you want the exact same versioning and commit, the hash of core used to build the package is in the REVISION file at the root of the wheel.