Search found 231 matches

by Papasot
13 Nov 2022 23:20
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

I will upgrade everything. Right now, I'm on a newer (for me!) Acer Aspire 5. ok, just did full upgrade with no excludes. New kernel, glibc, etc. So far, everything seems to be working properly :) I bet it doesn't just seem to work, it just works. Trust me, if it wasn't working you would know it im...
by Papasot
07 Oct 2022 22:09
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

So i upload in 64bit repos as well the file-5.41-x86_64-1.txz version from slackware-15 and now fakeroot is working. do a sudo spkg -d file sudo slapt-get -u sudo slapt-get -i file and check with fakeroot slkbuild -X Thanks. Indeed, it does work now. This "downgraded" file from version 5....
by Papasot
07 Oct 2022 18:28
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

It turns out fakeroot actually works in 32-bit but not in 64-bit. And it might be because in 32-bit we have fakeroot 1.26-i586- 1 .dj, which was not changed recently, and it is the same as before glibc 2.36. On the other hand, in 64-bit we have fakeroot 1.26-x86_64- 2 .dj. Maybe recompiling fakeroot...
by Papasot
07 Oct 2022 13:14
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

My fault, i had to also remove aaa_glibc-from repos, sorry. try again sudo slapt-get -u and upgrade aaa_glibc-solibs also. Ok, everything works now. One thing I noticed is, in a fresh installation (upgraded just now), fakeroot slkbuild -X actually works. However, as we already know, it does not wor...
by Papasot
06 Oct 2022 07:23
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

I removed glibc-2.35 packages from repos. I had forgot to do it for i486. So glibc-2.36 will install now. This is what I suspected it was happening. I tried again, almost sure this time it will work. Fresh installation, I manually upgraded everything related to glibc, plus aaa_base (this time it sa...
by Papasot
05 Oct 2022 14:52
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

There seems to be a problem with Slackel 32-bit (Openbox, at least). After a fresh installation, whenever I try to upgrade the system it will install glibc 2.35, not 2.36. However all the other packages upgraded will require glibc 2.36 (even bash, so after reboot I can't even login anymore). I re-in...
by Papasot
23 Aug 2022 09:20
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

Since your system broke when upgrading to glibc-2.36 it is also has this problem. If you have time just download slackware64 current iso and burn it or put it in a usb and try to boot with it. check if just boots. The problem is this machine is 32-bit, and there is a full iso for Slackware-Current ...
by Papasot
19 Aug 2022 05:51
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

It is weird Slackware-Current has issues with glibc 2.36 and nobody else talks about it. I am guessing we still have to wait and avoid upgrading for now.
Ventoy is a nice tool I wasn't aware of.
by Papasot
12 Aug 2022 07:22
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

Your x86_6 system is working because i uploaded on slackel repos all previous files in x folder so they have first priority over slackware packages. I did not manage to do it for 32 bit because slackware repo has already been upgraded with new x packages. I suspected you did something like that bec...
by Papasot
11 Aug 2022 17:09
Forum: Problems
Topic: IMPORTANT: DO NOT UPGRADE
Replies: 27
Views: 8114

Re: IMPORTANT: DO NOT UPGRADE

It is not your system only. I did the mistake of upgrading before checking the forums first. I upgraded the 64-bit system and for some reason all went ok. So, still unaware of the issue, I tried to update my 32-bit system as well - and then the problem appeared. It upgrades as if all is ok, but afte...