IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 9 May 2021 (all times are UTC)
| 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 (shored!~shored@81-175-153-95.bb.dnainternet.fi, Ping timeout: 246 seconds) | |
| 04:53 | shored has joined IRC (shored!~shored@81-175-153-95.bb.dnainternet.fi) | |
| 05:47 | <alkisg> !tarball
| |
| 05:47 | <ltspbot> tarball: You can download tarballs of tagged LTSP releases from e.g. https://github.com/ltsp/ltsp/tarball/v21.01
| |
| 05:50 | <alkisg> !forget tarball
| |
| 05:50 | <ltspbot> The operation succeeded.
| |
| 05:50 | <alkisg> !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
| |
| 05:50 | <ltspbot> The operation succeeded.
| |
| 05:58 | <vagrantc> why specify the version in the example?
| |
| 06:07 | <alkisg> It's a different github interface, I haven't explored it fully yet, maybe it will allow to get -latest, even without a tag
| |
| 06:08 | Aah got it, https://github.com/ltsp/ltsp/archive/refs/heads/main.tar.gz
| |
| 06:09 | !forget tarball
| |
| 06:09 | <ltspbot> The operation succeeded.
| |
| 06:09 | jgee has left IRC (jgee!~jgee@186.80.49.20, Quit: Ping timeout (120 seconds)) | |
| 06:09 | jgee has joined IRC (jgee!~jgee@186.80.49.20) | |
| 06:09 | <alkisg> 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 | |
| 06:14 | <vagrantc> 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... | |
| 06:15 | <vagrantc> i've been trying to figure out why it didn't work anymore ... though i've always found the debian/watch file syntax confusing
| |
| 06:16 | <alkisg> The one is ltsp is different to the one in epoptes
| |
| 06:16 | Is the ltsp one still working?
| |
| 06:16 | * alkisg hasn't read about watch files at all... | |
| 06:17 | <alkisg> https://github.com/ltsp/@PACKAGE@/releases .*/v@ANY_VERSION@@ARCHIVE_EXT@
| |
| 06:17 | https://github.com/epoptes/epoptes/releases .*/archive/v@ANY_VERSION@@ARCHIVE_EXT@
| |
| 06:18 | Maybe the problem is in the extra "archive" there?
| |
| 06:18 | <vagrantc> used to work... :)
| |
| 06:18 | but yeah, that could be it
| |
| 06:19 | <alkisg> 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 ... | |
| 06:20 | <vagrantc> appears to be the issue
| |
| 06:20 | <alkisg> uscan
| |
| 06:20 | <vagrantc> uscan does all sorts of things
| |
| 06:20 | pretty much a screen scraper with fancy knobs
| |
| 06:21 | <alkisg> I was looking for how to reproduce it locally, to test changes etc
| |
| 06:22 | https://manpages.debian.org/buster/devscripts/uscan.1.en.html#github.com
| |
| 06:22 | 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
| |
| 06:23 | alkisg@alkis:/home/Public/Development/git/epoptes/epoptes$ uscan
| |
| 06:23 | uscan warn: In debian/watch no matching files for watch line
| |
| 06:23 | https://github.com/epoptes/epoptes/releases .*/archive/v(?:[-_]?(\d[\-+\.:\~\da-zA-Z]*))(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|zip|tgz|tbz|txz))
| |
| 06:26 | vagrantc: using the uscan manpage example, it seems to work. Diff: https://termbin.com/h1mi
| |
| 06:26 | I've no idea about watches; if you think it's right, go ahead and commit it or tell me to do it
| |
| 06:27 | From what I understand, we can use the exact watch file in both ltsp and epoptes, as it's using @PACKAGE@
| |
| 06:27 | *exact same
| |
| 06:27 | <vagrantc> right
| |
| 06:28 | it needs to use @PACKAGE@ in more places
| |
| 06:29 | <alkisg> See my termbin, I've put it in 3 places there, I have no mention of "epoptes" anymore
| |
| 06:29 | uscan --verbose ==> uscan info: Matching target for downloadurlmangle: https://github.com/epoptes/epoptes/archive/refs/tags/v21.02.tar.gz
| |
| 06:29 | It seems good enough for me, say the word and I'll commit it :)
| |
| 06:30 | 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 :) | |
| 06:31 | <alkisg> wget https://termbin.com/h1mi -O -
| |
| 06:31 | No need for a web browser :P
| |
| 06:32 | wget https://termbin.com/h1mi -qO -
| |
| 06:32 | <vagrantc> why not use @ANY_VERSION@@ARCHIVE_EXTENSION@ ?
| |
| 06:32 | er, @ARCHIVE_EXT@
| |
| 06:32 | <alkisg> vagrantc: I started with the "github example" that uscan has in its man page
| |
| 06:32 | It doesn't have @ARCHIVE_EXT@ anywhere there
| |
| 06:33 | And that's all my knowledge about the whole issue :P
| |
| 06:33 | <vagrantc> the "debian uupdate" seems extraneous
| |
| 06:33 | <alkisg> man uscan => search for github inside the man page
| |
| 06:34 | <vagrantc> https://github.com/@PACKAGE@/@PACKAGE@/releases .*/v@ANY_VERSION@@ARCHIVE_EXT@
| |
| 06:34 | that works for me
| |
| 06:36 | <alkisg> 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
| |
| 06:36 | <vagrantc> anyways, whatever works :)
| |
| 06:38 | <alkisg> I guess the "debian uupdate" is for upstreams where the version isn't compatible with debian package versioning
| |
| 06:38 | 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
| |
| 06:38 | OK pushing...
| |
| 06:39 | vagrantc: wanna push it, or should I?
| |
| 06:39 | *commit
| |
| 06:46 | Pushed
| |
| 06:48 | 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?
| |
| 06:49 | 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
| |
| 06:51 | <vagrantc> alkisg: lots of hard feelings against nodejs
| |
| 06:52 | <alkisg> Ouch. Do you mean for the `npm` packages later on? We won't need those
| |
| 06:52 | Or for nodejs itself?
| |
| 06:52 | <vagrantc> just raw nodejs?
| |
| 06:52 | <alkisg> Along with debian packaged nodejs packages
| |
| 06:52 | E.g. node-express is in debian; we could use it
| |
| 06:53 | <vagrantc> the long-term maintainability of any non-core functionality is dubious
| |
| 06:55 | but i really don't know ... my initial reaction is definitely concerned :)
| |
| 06:55 | <alkisg> 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?
| |
| 06:55 | <vagrantc> right, that's the problem of an ecosystem where there are thousands of one-line libraries
| |
| 06:56 | <alkisg> What would you choose for ltsp-webserver? Apache/nginx/etc + php/python/js, or hand made http servers... ?
| |
| 06:56 | <vagrantc> depending on non-packaged components for core functionality is a very different project
| |
| 06:57 | haven't written much, but in all that python looks the most hopeful :)
| |
| 06:58 | <alkisg> Without a web server? To implement something based on simplehttpserver? Hmmm, dunno, it sounds prone to security issues..
| |
| 06:58 | <vagrantc> sure, use a real webserver
| |
| 06:58 | which one probably shouldn't matter much ...
| |
| 06:59 | <alkisg> 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
| |
| 07:01 | 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 (shored!~shored@81-175-153-95.bb.dnainternet.fi, Remote host closed the connection) | |
| 09:43 | shored has joined IRC (shored!~shored@dc790tyjcbssqlvn070vt-3.rev.dnainternet.fi) | |
| 10:06 | <alkisg> !tag
| |
| 10:06 | <ltspbot> tag: tag: git tag -s v20.03 -m 'Version 20.03' && git push --tags
| |
| 12:05 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.0.1) | |
| 12:07 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
| 13:47 | woernie has joined IRC (woernie!~werner@p5ddec80a.dip0.t-ipconnect.de) | |
| 16:22 | Hyperbyte has left IRC (Hyperbyte!~jan@middelkoop.cc, Ping timeout: 260 seconds) | |
| 17:48 | woernie has left IRC (woernie!~werner@p5ddec80a.dip0.t-ipconnect.de, Ping timeout: 252 seconds) | |
| 17:50 | woernie has joined IRC (woernie!~werner@p5ddec80a.dip0.t-ipconnect.de) | |
| 17:58 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
| 18:59 | Hyperbyte has joined IRC (Hyperbyte!~jan@middelkoop.cc) | |
| 19:22 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Remote host closed the connection) | |
| 19:47 | woernie has left IRC (woernie!~werner@p5ddec80a.dip0.t-ipconnect.de, 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 | |