林博仁 Buo-ren Lin

Hello, apologies for the ignorance. I've installed a Debian 12 virtual machine and tried to replicate the problem, but I cannot reproduce the same symptoms: From your `snap version` command's...

The relevant GitLab API seems to be: [Project remote mirrors API | GitLab](https://docs.gitlab.com/ee/api/remote_mirrors.html#update-a-remote-mirrors-attributes)

@amimas Thanks for the answer! Unfortunately I'm not aquainted with Python enough to implement this functionality at the moment.

@deckstose > If I'm getting it right we have the packaging files and a CI job to build it, but we do not publish from this repo? (Is it done...

@Kenya-West > Is there an option that Snap version could possibly become stale, too? Not necessarily, as it depends on whether the snap publisher can follow the upstream's releases well....

@kz6fittycent > I also saw [@brlin-tw](https://github.com/brlin-tw) 's PR ([#1261](https://github.com/aristocratos/btop/pull/1261)) for upgrading to `core22`, but the snap has been `core24` for some time (see here: https://github.com/kz6fittycent/btop/blob/main/snap/snapcraft.yaml). Thanks for the heads up!...

Not sure, but I think there's a sysfs thing on Linux that can do this exact thing.