Wed, Jan 13
Tue, Jan 12
Mon, Jan 11
Thu, Dec 31
I used to take notes in my discrete math classes in LaTeX, so if help is needed there, I can probably assist. However, I suspect that @lynorian's Sphinx skills will likely suffice.
Thanks for setting up Jenkins.
Wed, Dec 30
Thanks @teward for your assistance with CI. We may have some further sysadmin things dealing with this task once we figure out what we want to do with this.
I want to go on the record and say this is fantastic @apt-ghetto! Very nice work.
One minor thing, in the task you mentioned looking at the output and tweaking the CSS. I think we need to poke at the TOC if possible. I am not sure what our options are there but it gets all bunched up and the sub-chapters are not visible in the Table.
We still have some TODO's left, I will edit the task so those items are check boxes indicating where we stand with the task.
Fixed. Needed another plugin added (HTML Publisher). Working now.
However, you still get brokenness:
PDF builds should work now. At least, Docker can execute. The container Jenkins is in did not have nesting enabled. We're no longer getting instant failures.
Yes, Jenkins is running inside an LXD environment. I can try and set up nested dockerization in that.
Dec 22 2020
General (wiki) looking & some minor editing.. Comments & discoveries so far
Dec 18 2020
Dec 13 2020
Oct 28 2020
I have a feeling the Jenkins host is running in LXD. @teward?
$ docker build -t 8e412831f28fd62a57d2b81c5f3292b9354b7b81 -f Dockerfile . Sending build context to Docker daemon 115.4MB Step 1/2 : FROM ubuntu:focal focal: Pulling from library/ubuntu 6a5697faee43: Pull complete ba13d3bc422b: Pull complete a254829d9e55: Pull complete Digest: sha256:fff16eea1a8ae92867721d90c59a75652ea66d29c05294e6e2f898704bdb8cf1 Status: Downloaded newer image for ubuntu:focal ---> d70eaf7277ea Step 2/2 : RUN export DEBIAN_FRONTEND=noninteractive && apt-get update && apt-get install --yes --no-install-recommends python3-pip python3-sphinx latexmk texlive texlive-formats-extra arcanist build-essential python3-sphinx-rtd-theme python3-sphinx-bootstrap-theme ---> Running in a59b504f9a82 OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"proc\\\" to rootfs \\\"/var/lib/docker/vfs/dir/7497de1b8053cc4c8931cf844dea638b3789f29354e9d63a0157e5cf0ef33437\\\" at \\\"/proc\\\" caused \\\"permission denied\\\"\"": unknown
Oct 19 2020
Jul 23 2020
Jul 22 2020
May 20 2020
May 17 2020
Jan 6 2020
@wxl give me the valid link and I'll poke it in.
@tsimonq2 it doesn't seem like this is resolved when https://manual.lubuntu.me/lts doesn't seem to go anywhere or rather it seems to go to https://manual.lubuntu.me/stable/lts which is obviously not valid. Perhaps this one is @teward's fault????
Dec 16 2019
In case I didn't make myself clear, Lyn, I do not envision this as another thing to lump on your plate. I mean, hey, if you want to add to your TODO list, knock yourself out, but you already do so much.
Dec 15 2019
This seems like it would be a nice enhancement to the fantastic manual we already have. I would be willing to help with this project as time permits. I know AntiX / MX linux has a fair bit for video content that Dolphin Oracle put together. It seems to be a well utilized resource for them. I don't think there are too many other distros that have as much content as they do. I think like the current manual this could be something that could evolve over time, continually improving on the last iteration so I don't think we should focus too much about the initial quality.
Thing is I have never edited videos before. I also hate listening to the sound of my own voice.
Oct 17 2019
Oct 12 2019
The plan is that manual.lubuntu.me would automatically redirect to the stable branch.
Oct 3 2019
I was asking more for where https://manual.lubuntu.me/ what to have redirect to. I think almost all of the branches are named that other than LXDE which 18.04 is basically a copy as I could not find an easy way to rename a git branch rather than take a new branch with a new name and delete the old and did not delete the old.
Bump, because I'd like to deploy this on release day if it's feasible.
Oct 1 2019
That's a good idea. What about renaming the old branches to follow XX.YY? We could then follow the existing procedure, and you could go ahead and delete branches when you think it's necessary.
Sep 30 2019
Agreed this is is similar to what I want right now. I mean I don't see the point in keeping old realeases published without support. I really don't think getting rid of the branches in the git tree would be best. I say keep old versions of source in branches around as that is easy if say we end up switching back to an program from a previous release So I don't have to start over from scratch. This is really similar to what I wanted. The only other question is what would just the old manual url link to if say someone had a URL saved to get to it.