-- Leo's gemini proxy
-- Connecting to gemini.tuxmachines.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini;lang=en-GB
Tux Machines
Posted by Roy Schestowitz on Mar 11, 2023
> Developers who build distributions often (but not always) put considerable effort into backward compatibility, ensuring, for example, that a program built for one release will continue to run on later releases. Forward compatibility, where it is possible to move a program (or other artifact) from a more recent release to an older one, can be less of a concern, but it still tends to be seen as something that is better to not break if possible. So it is not surprising that an issue affecting the forward-compatibility of ext4 filesystems built for the upcoming Debian 12 ("bookworm") release has generated a fair amount of discussion, even if the number of affected users is likely to be small.
> Immudb is an open-source, immutable database. That means it uses a variety of security techniques such as cryptographic proof and verification and zero trust to make its data and transactions tamperproof. That's great, if you're using immudb. But, say you're not. Well, immudb's parent company Codenotary has an answer for you. Database connectors that enable data stored in other data stores to be made tamper-proof.
> Until now, there has been no easy way to guarantee the integrity of data kept in other databases for forensic, judicial, or auditing purposes. This could be a game-changer for companies and organizations that must ensure that the data in their databases is reliable.
> The immudb connectors do this by providing cryptographic verification. This validates the integrity of the data at every transaction, ensuring it is tamper-proof. The connectors make it possible to extend data to and store it inside immudb, while still providing high performance and full query capabilities.
> The Python-packaging discussions continued in January and February; they show no sign of abating in March either. This time around, we look (again) at tools for packaging, including a brand new Rust-based entrant. There is also a proposal to have interested parties create Python Enhancement Proposals (PEPs) for packaging solutions that would be judged by a panel of PEP delegates in order to try to choose something that the whole community can rally around—without precluding the existence of other options. As always, it is all a difficult balancing act.
> Linux users often work with text files; tools like grep, awk, and sed are standard utilities in their toolbox. However, these tools fall short when trying to extract or edit data from files in a binary format, analyze corrupt media files, or for parsing a binary data format. FOSDEM 2023 in Brussels had a whole binary tools devroom dedicated to open-source programs that deal with binary data.
> Line-based text files can be handled with the standard tools, but even better tools exist for data formats that store structured data in text, like JSON, YAML, and XML. For JSON, the command-line processor jq has become popular. It was also the inspiration for at least two tools called yq that handle YAML, JSON, XML, and other text-based formats: one by Mike Farah and another by Andrey Kislyuk.
> The Chrome team is excited to announce the promotion of Chrome 112 to the Beta channel for Windows, Mac and Linux. Chrome 112.0.5615.20 contains our usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore - please head to the Chromium blog to learn more!
> Dear Tumbleweed users and hackers,
> This week we have only published 6 snapshots. One was held back as we identified an issue in one package (libfdisk1) which requires manual intervention (on transactional updates) or an error to be ignored. The problem is in the %postun script of the package, so it’s already ‘on disk’, and thus not fixable. But having seen it, we at least wanted to make sure this will only happen once, and not a 2nd time later on when the script is fixed (transactional-update will learn how to deal with this specific package in the following days; so you can safely let it revert the update for now and let the process play out).
> The 6 snapshots published were 0302, 0303, 0304, 0306, 0307, and 0308 and they contained these changes:
> [...]
-- Response ended
-- Page fetched on Fri Jun 14 02:11:40 2024