Hallo, * Raúl Sánchez Siles [Sun, Oct 12 2014, 07:12:58PM]: > Hi: > > > El Domingo, 12 de octubre de 2014 11:36:05 Eduard Bloch escribió: > [...] > > * Raúl Sánchez Siles [Sat, Oct 11 2014, 11:11:23PM]: > > Even without mentioning the last detail, that is exactly what I was > > thinking. How could one manage to get a system into such insane > > condition... > > > > I have a workaround in mind but it's dirty and I have to rethink that > > and I cannot promise a fix before Freeze, though. > > > > And this time I can give you just a pragmatic answer: read the > > manual, use the web UI to delete broken files, and the cache should > > recover after some days of usage. And hire an admin who knows how to > > keep systems working without running into OOM or ENOSPACE. > > I'm ok to consider this as wishlist if this is due to lack of disk space. I > admit, handling ENOSPACE is out of the scope of apt-cacher-ng. I also agree a > wishlist is no hurry for jessie. > > Just in case, I'd like to attach a new maintenance log with the same > problem. Even ot much, I think this time I have space enough, more than 150MB
Yes. I said "delete them" and "after some days of usage" and I that is exactly what I meant, please do so. These conditions will trigger some recovery code which will restore Sources.xz with download information. > $ ll /var/cache/apt-cacher-ng/debrep/dists/experimental/non-free/source/ > total 25 It says 25 but you show me only the first files. I must assume Sources.xz.head is there and also has zero byte size. > -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 6706 oct 12 19:00 Sources > -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 0 feb 18 2014 Sources.bz2 > -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 0 feb 18 2014 Sources.bz2.head > drwxr-sr-x 2 apt-cacher-ng apt-cacher-ng 5120 oct 12 19:00 Sources.diff > -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 2579 oct 12 19:00 Sources.gz > -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 249 oct 12 19:00 Sources.gz.head > -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 263 oct 12 19:00 Sources.head > > I think the maintenance task ended successfully, but there error is there. > I > wonder why Sources.xz is not downloaded. Because it doesn't know where to download it from. You haven't configured backend servers so it cannot pick one from there, and the head files don't provide useful information (see above). My planned workaround will be looking around, getting the download URL of the Release or InRelease file that is lying around somewhere in the hierarchy and make up an URL for Sources.xz based on this data. Regards, Eduard. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
