Closed petefoth closed 6 months ago
Sat 06 Jan 24
a52q
-> gauguin
gingko
Sat 20 Jan 24
griffin
, s3ve3gjv
& jfltexx
18.1 builds: rebuilding themgriffin
, s3ve3gjv
& jfltexx
18.1 builds all rebuilt and pubisheddf -h
Filesystem Size Used Avail Use% Mounted on
...
/dev/vdb1 590G 249G 311G 45% /mnt/archive
Sun 21 Jan 24
# 45 on download server
find . -type d -empty | wc -l
45
find . -type d -empty -exec rmdir {} \;
# leaves 237 directories with 266 builds, disk space
df -h
Filesystem Size Used Avail Use% Mounted on
...
/dev/vdb1 590G 251G 309G 45% /mnt/archive
find . -type d -empty | wc -l 68 find . -type d -empty -exec rmdir {} \;
We have 'extra' builds on the build server, which are old 18.1 builds for devices which are no longer supported / on the LOS build target list
After the February build run, we should have two builds of all current build targets, 18.1 & 20.0, except for devices which built for the first time this month (radxa0, odroidc4, m5)
So we can safely delete all files matching pattern lineage*2023*
in the zips
directory tree (25 complete builds(
find . -name lineage*2023*.zip -delete
Then we can remove any empty directories, because if there are no 2024 builds, the device is no longer in the current build target list.
Your missing the fact that some devices did not have builds in January, e.g. pdx203 and pdx206. So you would only keep one file.
Also I do not agree with removing devices that are not built anymore: people should be able to access the last existing build for some time (maybe not forever, but I would say for one year or something like that).
(For instance in the case of my pdx203, I would have been quite unhappy if the July build was removed while no newer one was published)
Also I don’t agree with removing device that are not built anymore: people should be able to access the last existing build.
So how far back do we go? By that logic we would have a lot of 15.1, 16.1 and 17.1 builds hanging around.
For instance in the case of my pdx203, I would have been quite unhappy if the July build was removed while no newer one was published
Why? So long as you pick up the OTA update then you don't need that build again. Our aim is to
deliver regular builds of the project for all the phones and tablets currently supported officially by LOS
LIneageOS don't keep builds around fro long once they are removed from the build target list
Also I don’t agree with removing device that are not built anymore: people should be able to access the last existing build.
So how far back do we go? By that logic we would have a lot of 15.1, 16.1 and 17.1 builds hanging around.
I’ve edited my post to say not forever, I don’t know what LineageOS policy is, but something similar I guess?
For instance in the case of my pdx203, I would have been quite unhappy if the July build was removed while no newer one was published
Why? So long as you pick up the OTA update then you don't need that build again.
When I got the device (late 2023), the July build was the only one available. If you had removed it because the device was not built anymore, there would have been none.
Our aim is to
deliver regular builds of the project for all the phones and tablets currently supported officially by LOS
LIneageOS don't keep builds around fro long once they are removed from the build target list
OK, then I would say remove them once LineageOS did so. FTR, pdx203 and 206 were not removed from their download while it wasn’t build, likely because it was meant to be temporary (they were waiting for a modem crash issue to be fixed). However I can see that e.g. https://download.lineage.microg.org/Spacewar/ is already removed.
See new issue Build retention strategy
#573 for a more flexible approach to this issue
Closing this issue now - I won't 'tidy' any more builds until we can agree on, and implement that startegy
The 18.1 devices that have been built this month seem to have three builds - because I did a second build run on Jan 20 - and they are not getting deleted. I'll clean up the earlier January builds
To Do
.ing
files for GChecked
ls -t */line*.zip
find . -name *.zip