Are you one of those people with some mad system with lots of CPUs? Having a hard time trying to see them all? Well top is coming out with two new features.
The first is two CPUs per row for wide (about over 160 columns) screens.
The second is to be able to group cpus into, um groups, so you can see pairs of cpu stats aggregated or 4 aggregated etc.
#autopkgtest is very useful facility to check for Debian packages as-installed. It probably has the second-worst documentation in history (the first being sendmail).
If I actually understood it, I'd fix the documentation, but I don't.
The #debian project is planning on holding a mini DebConf online.
This will be "4 days of Debianites working together to improve Debian" and will be totally online like all the cool kids are doing.
It will be 28-31st May 2020, more details at https://wiki.debian.org/DebianEvents/internet/2020/MiniDebConfOnline
Guess what? #wordpress have release a new version and its a security fix. There are 6 security bugs fixed, they even have CVE IDs! Much excitement.
Pretty much every version of wordpress is vulnerable except for CVE-2020-11030 because the block editor is new from about WordPress 5.0 or so.
I'll be cooking up the #Debian packages this weekend.
I can't really see much that is different. They have done some enhancements in the editor and there is a new 2020 theme but other than that, its the same WordPress you know and love (or hate, or both, whatever).
Is there anything more confusing than shared library numbering?
There are three numbers: current, revision and age. Depending on what you are doing to the API one or more of those numbers will change. Seems the last #procps relase I did months ago I got it wrong and bumped the age when that can't happen by itself, I think.
Oh and the soname of the library is definitely connected to, but not exactly, those three numbers (I think its C.R.R-A or something like that).
Found a curious bug in the #debian #wordpress package last night. There is a reasonably old security patch for CVE-2017-14990 where the activation key is stored in plaintext for multisite users (normal users it's hashed).
Anyway it's a broken patch because it doesn't decide the user id. Easy to fix but I never used it before.
I just found out someone still maintains one of the first free software programs I wrote so many years ago. Checked the changelog and it was 25 July 1995! A 24 -year old program still in use.
There has been a bit of a clean up and all my comment out debug code removed (good!) but its basically the same.
Fortunately the Linux kernel driver I wrote has long gone 😱
#wordpress 5.2.4 is now available! This security release fixes 6 security issues.
WordPress versions 5.2.3 and earlier are affected by these bugs, which are fixed in version 5.2.4. Updated versions of WordPress 5.1 and earlier are also available for any users who have not yet updated to 5.2
Every time I have to interact with sourceforge it reminds me how backward the site is. I have had so many 503 errors, comments disappearing from bug reports or some truly bizzare happenings in text boxes where the words repeat.
I'm so glad I moved my stuff off it, originally due to the previous owners dodgy behavior but now for all this.
An update! They looked at the net-snmp bug again and there was a fix already, just not in the current release.
Amazing how two simple lines can ruin your day.
Free Software programmer, network engineer and Debian developer.
100% tomato verified. 🍅✔
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!