Dave Vasilevsky wrote... > Hi Christoph,
Sorry for the late response, details below.
> Were you able to look into restoring some of the lost period of snapshots
> for debian-ports? I've found a Debian derivative, MintPPC, that currently
> seems to only be usable with snapshots from between Sep 2023 and Jan 2024,
> so it would be very helpful.
Always glad to learn about powerpc enthusiasts out there. Be warned
however, ports for right that time period you're asking for are mostly
lost unfortunately. As mentioned earlier, I will be able to emulate the
pool directory structure - with forseeable many missing files - but the
Packages indexes and signature have not been saved, so that period will
not be apt'able. Expect the first full snapshot for Januar 29th 2024.
Otherwise, import from my private archive to snapshot.d.o gained
traction again, it was delayed by life outside Debian and certain
activities inside that kill enthusiasm big scale.
Current ETA for the time period January-June 2024 is the end of the year.
The other gap (July 2023-January 2024) might follow soon afterwards but
I haven't fully planned the reconstruction process yet.
For those who are curious, some background why it's taking to long:
Before importing, I need to compute the SHA-1 hash sum of each and every
file, and in all the copies (technically: zfs snapshots) I've created.
Just doing this straightforward would take a looong time, so I
implemented a shortcut, and then saw the need to shortcut that shortcut
as well. Still, this means dealing with more than a billion files, and
already a simple tree walk takes four days: zfs has a lot of very
interesting and useful features - but performance isn't among them,
especially on spinning rust.
The metadata to work on still is somewhere in the range of a few 100
Gbyte, so it's worth to look for efficient solutions, and being patient.
Eventually, we'll have to transfer the actual files to the Debian
infrastructure. As I don't want to overload the link, I expect this
to take more than a week. I cannot tell how much time post-processing
will need, in my understanding it could be quick. I might be wrong.
Another issue, I took the opportunity to also verify all the hashsums
that are already inside each copy, like comparing the SHA-256 hashsum of
a binary package to what is listed in the related Packages index. And,
surprise, there are mismatches. Finding a solution for this is another
issue.
Christoph
signature.asc
Description: PGP signature
