Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
gets the same output as before.
libicu57 is on hold to prevent it from upgrading right? But it is not working. I tried with unhold too - same dependency errors.
I also tried deleting the available and status files and info directory from var/lib/dpkg, after this I ran dpkg --configure -a, and reinstalled some packages but when it reached libicu57 unpacking, i got a reboot again... now i restored the old files (I made a backup earlier)
alma359 wrote:libicu57 is on hold to prevent it from upgrading right?)
The system did not put it on hold: you did it ! The question was why ?
Now you have played with dpkg files, I am sorry to not be able to make a new exact status and detect new inconsistencies.
Hope a courageous one can help you now to start again investigations.
alma359 wrote:libicu57 is on hold to prevent it from upgrading right?)
The system did not put it on hold: you did it ! The question was why ?
I told him (here: http://forums.debian.net/viewtopic.php? ... 21#p709605) to put it on hold to test if upgrading the rest of packages would work or not, i.e. to determine whether the problem is (directly or indirectly) caused by libicu57.
Now you have played with dpkg files, I am sorry to not be able to make a new exact status and detect new inconsistencies.
Hope a courageous one can help you now to start again investigations.
..... buster is the stable release ....
I've read the latest posts now (big thanks to you for being so diligent!), but I'm out of ideas. Either it's a hardware issue, or the package database (or the .deb's themselves) are somehow corrupted. Maybe it's just a bad mirror, but it would be the first time I hear about such a thing.
In any case, good luck to @alma359 (maybe a reinstall would be in order? :)
The right tool to clarify tricky situations is aptitude which better explains what's going on.
If dpkg database is broken, for any reason, or seems to be, it's too late to think about it !
'apt' command should be reserved for simple operations, but cannot do more.
Now, there would be another solution to try by directly digging into /var/lib/dpkg/status file , but difficult to drive in a forum.
My feeling is that some dpkg files have been deleted..... and apt is lost.
I managed to successfully update my packages. I deleted the dpkg files again and then created a empty status file and empty info directory. After this hold on libicu57 worked and i reinstalled all packages, this generated the dpkg files again. I don't know what exactly caused the issue but i think maybe a power loss currupted some files. I will buy a ups power backup for my server.
Thanks for the help