Excellent news! I like Slackware!
|
Okay, did some research and set TERM=xterm and everything is back to normal. No more weird chars in the terminal.
|
Again, x86_64 package mixed into 32-bit.
|
Quote:
|
Quote:
Code:
slackware-current$ find -name '*x86_64*' |
What mirror are you using?
|
Quote:
|
Indeed. At least on that mirror and the mirrors at TDS the y series is all x86_64 packages. ftp://slackware.mirrors.tds.net/pub/...t/slackware/y/
EDIT: oddly enough, the packages in 64-current and -current don't appear to be the same packages, at least based on size. Quote:
Quote:
|
Just upgraded from beta to 13.1 RC1 32 bit and all seems well (apart from a very minor glitch on task manager bar in KDE which I fixed by changing theme).
I rsync'd from slackware.mirrors.tds.net::slackware and was surprised to find this 64 bit package in what should be a 32 bit tree: Code:
y/bsd-games-2.13-x86_64-10.txz |
Quote:
Later: BINGO! The crappified package that install the lib64 directories is aaa_base-13.1-i486-1.txz |
Doing "ls /var/log/packages/*x86_64*" in my 32bit slackware-current box gave:
Code:
/var/log/packages/bsd-games-2.13-x86_64-10 |
I downloaded most of the 32-bit tree and most of the 64-bit tree using Alien Bob's mirror-slackware-current.sh and I have no rogue packages at all.
I do not download /e /f /kdei /t /y so I can't really comment on those. samac |
Quote:
|
Quote:
|
It may still be in aaa_base 32-bit, but is this a bug or deliberate?
samac |
All times are GMT -5. The time now is 01:02 AM. |