Newbyte
Spending the afternoon in a slowly revolving door.
Tagged #postmarketOS #pmbootstrap 3.10.0 last night. Highlights include the install command prompting for user password and "pmOS is already installed on this medium" much earlier so you don't have to babysit it, run0 support if sudo and doas aren't installed, and UEFI boot by default for QEMU.
Other than that, lots of smaller bug fixes and enhancements as well as technical debt being cleaned up. Big thanks to all the new contributors who showed up to help out with this!
Do you think "downstream" ports are useful in #postmarketOS? I'm especially interested in your reasons if you answered "Yes".
If you're interested in a semi-beginner friendly contribution opportunity in #postmarketOS, we currently have an issue with using Podman/Distrobox in the Console terminal emulator. @craftyguy@freeradical.zone already investigated it and found a probable root cause, so either just verifying his hypothesis or sending an actual fix upstream would be helpful!
See https://gitlab.postmarketos.org/postmarketOS/pmaports/-/work_items/4469 for more information.
#postmarketOS #pmbootstrap users: Do you have any use for the "quiet" feature enabled by the -q argument and if so why haven't you complained about it being broken for the last two years? 😅
If you're interested in beginner-friendly tasks for contributing to #postmarketOS in #Python, #pmbootstrap has some clean-ups that need to be done—in particular, migrating the remaining commands from the legacy frontend.py to the new "commands" module.
See https://gitlab.postmarketos.org/postmarketOS/pmbootstrap/-/commit/7df1ab11218dfbf4797dfb3ef896f3a060749549 for an example. Essentially, each command should have its own .py file and take a list of arguments instead of the whole "args" namespace.
I've been bugged by some of the #postmarketOS #pmbootstrap subcommand names for a while, so I decided to finally write my thoughts down in an issue: https://gitlab.postmarketos.org/postmarketOS/pmbootstrap/-/work_items/2745
Any thoughts or suggestions are more than welcome. Hearing others' experiences and thoughts about this would be great.
Does anyone have an actual use-case for the "pmbootstrap apkindex_parse" subcommand? Asking because apparently it was broken for over a year and no one seemed to complain 😅
@Oleksii@social.linux.pizza It just makes pmbootstrap not output any log messages. It's in pmbootstrap --help.
Would be pretty cool to repurpose an old tablet to make your own departure sign for your closest public transport sign. I found that my local public transport company has a web version of their signs on URLs like this one: https://avgangar.ostgotatrafiken.se/tinnerbacksbadet?size=large
Is there any easy way to just put a web link in a directory in #GNOME with #Nautilus for organisational purposes? Like if I have a directory with files relating some particular task and I also have a link that's very relevant to this task, is there any way I can have a file that opens a given link in a browser when tapped on? Generally I think this would be handled by desktop files, but it doesn't look like Nautilus cares about them. And they're not very convenient to make.
Whenever I make the mistake of thinking that Stack Exchange is good actually and people just need to get it I'm swiftly proven wrong.
Apparently as a nice side-effect a newer version of this MR than what was described here also unintentionally works around a bug in old versions of sudo-rs that broke pmbootstrap install on Ubuntu 25.10!
