Conversation
Notices
-
@Zergling_man @realman543 >package management
:vomit:
-
@Zergling_man Really the most simple solution is to move the binary from the more recent update to the right place and symbolic link it back to where it was (if necessary for other programs, otherwise put a text file in there or something to remind you).
-
@realman543 No that doesn't work. The problem is that it can't install because /bin exists as a symlink and it's expecting it to be a directory that it can then dump files in.
So the location has to be fixed in the package if I want to install it using the package manager, which of course I do, because motherfuckers need package management.
-
@realman543 (Though I've already shoved a fixed version of the package in place and it's bitching about checksum stuff, so the simpler solution is to just update everything else, then immediately update it with all checks disabled.)
-
@realman543 It's literally just a new release from 6.6.1-2 to 6.6.1-3, it somehow went wrong.
I'm tempted to just install 6.6.1-2. Somehow I already have it even though I'm running 6.6.1-1.
-
@Zergling_man The optimist in me wants to think this was a mistype of some sort.
It was probably intentional.
-
(I have made this mistake before, I did not realise that /bin was a link. I found out at that time and have never made the mistake since.
And I didn't do it in live artix repos lol.)
-
(Bonus points: This is not a new package. It was correct before.)
-
Some genius deployed a python package with stuff in /bin instead of /usr/bin.
† top dog :pedomustdie:
reeeeeelman
Zergling_man
All ０７６萌ＳＮＳ content and data are available under the