I’m trying to run a slightly old yocto build project on Manjaro that previously was only tested on WSL Ubuntu. I’m getting this error: Traceback (most recent call last): File "/home/slawo/Work/project/poky/bitbake/bin/bitbake", line 24, in <module> from bb.main import bitbake_main, BitBakeCon…

Today I could update some packages that were not ahead of my branch mix :smiley: ▶ Update Log And also while installing the droidcam client I had to install my kernel headers. [2024-05-14T10:00:25+0200] [ALPM] installed pahole (1:1.26-2) [2024-05-14T10:00:26+0200] [ALPM] installed linux66-headers (…

[image] slawo: /usr/bin/python: No module named build I dont think I have ever seen this error. The first general AUR thing is that base-devel is required. sudo pacman -Syu base-devel Because this is a python error … I might ask have you installed python things from outside the package man…

yes, I have base-devel installed, I got this “install toolchain dependency” script with the project that had the ubuntu dependencies, so I converted it for manjaro based on previous errors and google :slight_smile: if [ "$1" = "ubuntu" ]; then sudo apt-get update sudo apt-get install build-essent…

Don’t mix local and system Python packages. See: [image] [root tip] [How To] Avoid common pitfalls as developer Tutorials Spend your time coding As a long time developer - using Arch and Manjaro - I can tell from experience - having your workflow broken is ext…

As far as I can tell I’m not mixing. Or is installing from AUR count as mixing? Regarding the ln I know its dirty, but I ran into this problem and until stable catches up to last weeks unstable that’s the only thing I can do because I can’t downgrade back to stable: [image] Booting…

While its good not to do it, sometimes it’s the best that is available. Package managers really should gain some sane way to manage hacks like this. How easy would it be to tell pacman that libalpm14 provides libalpm13 and have a centralized place to manage it instead of just links you hopefully r…

[image] varikonniemi: Package managers really should gain some sane way to manage hacks like this. How easy would it be to tell pacman that libalpm14 provides libalpm13 and have a centralized place to manage it instead of just links you hopefully remember. The real issue here is the attempt …

you can try and explain it away in this case, but it was not my argument. My argument was that sometimes it’s the only option. And for that case, sane support should be provided instead of leaving everyone to improvise in any which way.

“Do not put diesel into an unleaded engine.” “OK, but sometimes I only have diesel, so instead of telling me not to do it, the engine should provide some way of processing diesel.” (also: “Whats wrong with my car?”)

what a stupid analogy you employ. How often do you drive well with diesel in gasoline car? Never. How often did i fix library not found error with only problem being a strict check for file name? quite a few times. Only problem being from that is that as it works you forget about it. And THEN the …

Its times like these I really miss the retort plugin. :laughing: (instead of engaging with trite name-calling … I must laugh at the message … in its entirety)