On 10/31/2017 11:41 AM, Florian Weimer wrote:
On 10/31/2017 05:09 AM, Ralf Corsepius wrote:
> Fortunately, I meanwhile managed to get a couple of the coredumps off
> the machine and uploaded them to
https://corsepiu.fedorapeople.org/rpm/
These files aren't readable:
Urgh, they should be readable now ;)
-rw-r-----. 1 corsepiu corsepiu 324542 Oct 31 03:55
core.rpm.0.17abf534e68e47a5b5083faf5456eedd.1197.1509376379000000.lz4
-rw-r-----. 1 corsepiu corsepiu 323956 Oct 31 03:55
core.rpm.0.c8d8c97534bc4d8e84f203294ef440b0.1171.1509376197000000.lz4
-rw-r-----. 1 corsepiu corsepiu 324793 Oct 31 03:55
core.rpm.0.c8d8c97534bc4d8e84f203294ef440b0.1175.1509376201000000.lz4
-rw-r-----. 1 corsepiu corsepiu 324938 Oct 31 03:55
core.rpm.0.c8d8c97534bc4d8e84f203294ef440b0.1179.1509376203000000.lz4
I doubt that restoring from backup will be necessary unless there is
actual corruption. If this is indeed a build problem, you should be
able to upgrade the affected packages using rpm --root from rescue media
once we've fixed the problem.
This machine is in a multiboot configuration.
The way, I am restoring it, is rsync'ing the backup from LAN from inside
a different installation (fc25).
Ralf