|03:11||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|03:41||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|04:14||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|04:14||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Client Quit)|
|04:15||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|04:52||shored has left IRC (firstname.lastname@example.org, Ping timeout: 246 seconds)|
|04:53||shored has joined IRC (email@example.com)|
tarball: You can download tarballs of tagged LTSP releases from e.g. https://github.com/ltsp/ltsp/tarball/v21.01
The operation succeeded.
!learn tarball as You can download tarballs of tagged LTSP releases from either https://github.com/ltsp/ltsp/releases or e.g. https://github.com/ltsp/ltsp/tarball/v21.01
The operation succeeded.
why specify the version in the example?
It's a different github interface, I haven't explored it fully yet, maybe it will allow to get -latest, even without a tag
Aah got it, https://github.com/ltsp/ltsp/archive/refs/heads/main.tar.gz
The operation succeeded.
|06:09||jgee has left IRC (firstname.lastname@example.org, Quit: Ping timeout (120 seconds))|
|06:09||jgee has joined IRC (email@example.com)|
You can download tarballs of tagged LTSP releases from https://github.com/ltsp/ltsp/releases or git HEAD from https://github.com/ltsp/ltsp/archive/refs/heads/main.tar.gz
|06:10||* alkisg wonders if there's a static URL for the "latest release"...|
|06:13||* vagrantc doubts, but who knows|
for some reason the debian/watch file for epoptes stopped working a while back ... does it have to do with exploring these new "tarball" locations?
|06:14||* alkisg checks...|
i've been trying to figure out why it didn't work anymore ... though i've always found the debian/watch file syntax confusing
The one is ltsp is different to the one in epoptes
Is the ltsp one still working?
|06:16||* alkisg hasn't read about watch files at all...|
Maybe the problem is in the extra "archive" there?
used to work... :)
but yeah, that could be it
What does debian do there, wget the releases url, and then sed the html to match something?
|06:19||* alkisg reads https://wiki.debian.org/debian/watch ...|
appears to be the issue
uscan does all sorts of things
pretty much a screen scraper with fancy knobs
I was looking for how to reproduce it locally, to test changes etc
version=4 opts="filenamemangle=s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%<project>-$1.tar.gz%" \ https://github.com/<user>/<project>/tags \ (?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate
uscan warn: In debian/watch no matching files for watch line
vagrantc: using the uscan manpage example, it seems to work. Diff: https://termbin.com/h1mi
I've no idea about watches; if you think it's right, go ahead and commit it or tell me to do it
From what I understand, we can use the exact watch file in both ltsp and epoptes, as it's using @PACKAGE@
it needs to use @PACKAGE@ in more places
See my termbin, I've put it in 3 places there, I have no mention of "epoptes" anymore
uscan --verbose ==> uscan info: Matching target for downloadurlmangle: https://github.com/epoptes/epoptes/archive/refs/tags/v21.02.tar.gz
It seems good enough for me, say the word and I'll commit it :)
uscan info: Newest version of epoptes on remote site is 21.02, local version is 21.02 => Package is up to date for from
|06:31||* vagrantc fires up a www browser :)|
wget https://termbin.com/h1mi -O -
No need for a web browser :P
wget https://termbin.com/h1mi -qO -
why not use @ANY_VERSION@@ARCHIVE_EXTENSION@ ?
vagrantc: I started with the "github example" that uscan has in its man page
It doesn't have @ARCHIVE_EXT@ anywhere there
And that's all my knowledge about the whole issue :P
the "debian uupdate" seems extraneous
man uscan => search for github inside the man page
that works for me
The man page example works for me. I don't know why they limited it to e.g. tar.gz instead of @ARCHIVE_EXT@, maybe to avoid extra matches? No idea
anyways, whatever works :)
I guess the "debian uupdate" is for upstreams where the version isn't compatible with debian package versioning
It's not useful in our case, but it might be a good idea to have it there for easier copy/pasting to other projects :D
vagrantc: wanna push it, or should I?
vagrantc: btw, for next year, I'm thinking of developing the web service part of ltsp in nodejs instead of python; it allows code reuse between backend and frontend (HTML/JS). Any hard feelings against nodejs?
It's also cross platform; in the very distant future, I could use my mobile phone as the ltsp server of a school computer lab :D
alkisg: lots of hard feelings against nodejs
Ouch. Do you mean for the `npm` packages later on? We won't need those
Or for nodejs itself?
just raw nodejs?
Along with debian packaged nodejs packages
E.g. node-express is in debian; we could use it
the long-term maintainability of any non-core functionality is dubious
but i really don't know ... my initial reaction is definitely concerned :)
While if we only used npm, and declared express to be fetched via npm as an ltsp-webserver.npm dependency, that wouldn't be good either?
right, that's the problem of an ecosystem where there are thousands of one-line libraries
What would you choose for ltsp-webserver? Apache/nginx/etc + php/python/js, or hand made http servers... ?
depending on non-packaged components for core functionality is a very different project
haven't written much, but in all that python looks the most hopeful :)
Without a web server? To implement something based on simplehttpserver? Hmmm, dunno, it sounds prone to security issues..
sure, use a real webserver
which one probably shouldn't matter much ...
Indeed, as long as they can support python as a service that can run all the time and not have to be reloaded for each request
OK I'll gain some experience with nodejs/npm due to another project, and we'll revisit this next year. Thank you for your thoughts, much appreciated!
|07:20||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 268 seconds)|
|09:12||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|09:43||shored has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|09:43||shored has joined IRC (email@example.com)|
tag: tag: git tag -s v20.03 -m 'Version 20.03' && git push --tags
|12:05||quinox has left IRC (firstname.lastname@example.org, Quit: WeeChat 3.0.1)|
|12:07||quinox has joined IRC (email@example.com)|
|13:47||woernie has joined IRC (firstname.lastname@example.org)|
|16:22||Hyperbyte has left IRC (Hyperbyteemail@example.com, Ping timeout: 260 seconds)|
|17:48||woernie has left IRC (firstname.lastname@example.org, Ping timeout: 252 seconds)|
|17:50||woernie has joined IRC (email@example.com)|
|17:58||RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)|
|18:59||Hyperbyte has joined IRC (Hyperbytefirstname.lastname@example.org)|
|19:22||RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Remote host closed the connection)|
|19:47||woernie has left IRC (email@example.com, Remote host closed the connection)|
|20:11||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|21:38||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|22:02||Vercas2 has joined IRC (Vercas2!~Vercas@gateway/tor-sasl/vercas)|
|22:02||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))|
|22:02||Vercas2 is now known as Vercas|