View Single Post
Old 01-29-2021, 06:00 PM   #921
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@mergen3107: It's an (old, giant) SVN repo hosted on a dedicated server (whose HDD died a horrible fiery death a few weeks ago, hence the delays ;p).

(There's usually a Trac frontend, but, the dead HDD meant a new install, so, I'm waiting for Trac 1.6 to come out for Python 3 support to bring it back up, because SVN 1.14 + Python 2 meant broken bindings the last time I tried, and I didn't feel like downgrading a 30GB SVN repo ;p).

The packaging & release process itself is handled by the usual scripts (e.g., a cascade of the per-hack make-packages.sh; c.f., make-packages.sh, upload.sh & go.sh in the x-tc tarball, or the Misc folder of the repo), and stuff gets uploaded to an OpenStack container. Basically, the only thing I have left to do manually is to c/p the updated post on MR .

Last edited by NiLuJe; 01-29-2021 at 06:03 PM.
NiLuJe is offline   Reply With Quote