| Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I missed the ".1". lol
|
|
current one vanished mysteriousl.
|
|
|
|
merged/pool/DEBIAN-SECURITY/updates/main/g/glibc/libc6-dev_2.36-9+deb12u6_amd64.deb for a test.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
base-files instead.
|
|
|
|
|
|
|
|
|
|
1.4.10 is no longer in DEBIAN-SECURITY.
|
|
|
|
Coz it got changed to deb.rr.devuan.org.
|
|
|
|
|
|
|
|
How did this last so long?
|
|
|
|
|
|
|
|
|
|
cat:
'results/STATUS_deb.devuan.org_deb.devuan.org_2a01:4f8:162:7293:__merged_pool_DEBIAN_main_d_debian-keyring_debian-keyring_2019.02.25_all.deb.txt':
No such file or directory
Is the error, so I touch it first, but not all of them get to the rm
later, so now we have a bunch of empty ones. No idea, it's really
random and hard to catch.
|
|
|
|
|
|
Should move that up higher. Something else is going wrong.
|
|
|
|
couple of months.
|