• Many Porcelain commands that internally use the merge machinery were taught to consistently honor the diff.algorithm configuration.

• A few descriptions in "git show-ref -h" have been clarified.

• A 'P' command to "git add -p" that passes the patch hunk to the pager has been added.

• "git grep -W" omits blank lines that follow the found function at the end of the file, just like it omits blank lines before the next function.

• The value of http.proxy can have "path" at the end for a socks proxy that listens to a unix-domain socket, but we started to discard it when we taught proxy auth code path to use the credential helpers, which has been corrected.

• The code paths to compact multiple reftable files have been updated to correctly deal with multiple compaction triggering at the same time.

• Support to specify ref backend for submodules has been enhanced.

• "git svn" has been taught about svn:global-ignores property recent versions of Subversion has.

• The default object hash and ref backend format used to be settable only with explicit command line option to "git init" and environment variables, but now they can be configured in the user's global and system wide configuration.

• "git send-email" learned "--translate-aliases" option that reads addresses from the standard input and emits the result of applying aliases on them to the standard output.

• 'git for-each-ref' learned a new "--format" atom to find the branch that the history leading to a given commit "%(is-base:)" is likely based on.

• The command line prompt support used to be littered with bash-isms, which has been corrected to work with more shells.

• Support for the RUNTIME_PREFIX feature has been added to z/OS port.

• "git send-email" learned "--mailmap" option to allow rewriting the recipient addresses.

• "git mergetool" learned to use VSCode as a merge backend.

• "git pack-redundant" has been marked for removal in Git 3.0.

• One-line messages to "die" and other helper functions will get LF added by these helper functions, but many existing messages had an unnecessary LF at the end, which have been corrected.

• The "scalar clone" command learned the "--no-tags" option.

• The environment GIT_ADVICE has been intentionally kept undocumented to discourage its use by interactive users. Add documentation to help tool writers.

...

cross-posted from: https://lemmy.nz/post/15137443

Hello everyone!

I'd like to announce the start of development and the public availability of what we currently refer to as Leap 16.0 pre-Alpha. Since this is a pre-Alpha version, significant changes may occur, and the final product may look very different in the Alpha, Beta, Release Candidate, or General Availability stages. The installer will currently offer you Base, GNOME, and KDE.

Users can get our new Agama install images from get.opensuse.org/leap/16.0. The installer will currently offer you Base, GNOME, and KDE installation.

Leap 16.0 is a traditional distribution and a successor to Leap 15.6 with expected General Availability arriving in the Fall of 2025.

We intend to provide users with sufficient overlap so that 15.6 users can have a smooth migration, just like they're used to from previous releases.

Further details are available on our roadmap. The roadmap is subject to change since we have to respond to any SUSE Linux Enterprise Server 16 schedule changes.

Users can expect a traditional distribution in a brand new form based on binaries from the latest SLES 16 and community packages from our Factory development codebase.

There is no plan to make a Leap 15.7, however, we still need to deliver previously released community packages from Leap 15 via Package HUB for the upcoming SLES 15 SP7. This is why there are openSUSE:Backports:SLE-15-SP7 project and 15.7 repos in OBS.

The target audience for pre-Alpha are early adopters and contributors who would like to actively be part of this large effort. Adopters should consider booting Agama Media from time to time just to check compatibility with their hardware.

For non-contributor users, I highly recommend waiting until we have a Beta, which is expected in the late Spring of 2025.

Specifically for Agama I highly recommend using github.com/agama-project and collaborating with the YaST team on suggestions and incorporating any changes.

For the rest of the components, the workflow isn't changing; just select version 16.0 for bug submissions.

Feature requests will be reviewed every Monday at a feature review meeting where we'll convert code-o-o requests into JIRA requests used by SUSE Engineering where applicable.

The factory-auto bot will reject all code submit requests against SLES packages with a pointer to code-o-o. You can get a list of all SLFO/SLES packages simply by running osc ls SUSE:SLFO:1.1:Build.

Just for clarification SLFO, SUSE Linux Framework One, is the source pool for SLES 16 and SL Micro 6.X.

I highly recommend using code-o-o to co-ordinate larger community efforts such as Xfce enablement, where will likely need to update some of SLES dependencies. This allows us to share the larger story and better reasoning for related SLES update requests. The list of features is also extremely valuable for the Release article.

For quality control, we have basic test suites based on Agama installations in Leap 16.0 job group. Later, we plan to rework the existing Leap 16.0 Images job group for testing the remaining appliance images.

The project where we maintain community packages is subject to change as we have not fully finalized yet how to make Package HUB; we may use a similar structure with Backports as in 15.3+).

Further test suite enablement is one of the areas where we currently need the most help. Related progress.opensuse.org trackers poo#164141 Leap 16.0 enablement and poo#166562 upgrade from 15.6.

Another area where you can help is new package submissions and related maintainer review of package submissions to Leap 16.0. These reviews make sense as we'd like to check with maintainers whether that software in a given version makes sense for inclusion into Leap 16.0, rather than blindly copying all packages over.

Do you want to help us on this front? Spread the news and feel free to join the #openSUSE_Marketing Telegram channel(https://t.me/openSUSE_Marketing)! https://en.opensuse.org/openSUSE:Marketing_team

Many thanks to all who helped us to reach this point.

Lubos Kocman on behalf of the openSUSE Release team

cross-posted from: https://lemmy.world/post/20535629

ZLUDA is a compatibility layer for Nividia’s CUDA on other processors

cross-posted from: https://slrpnk.net/post/13942074

cross-posted from: https://biglemmowski.win/post/2784381

I've remembered this exists and there seems to be some very recent activity in the repo so if you didn't know what was possible with TUI graphics now you know! (recommended watching with sound :)

Official site: https://notcurses.com/
Repo: https://github.com/dankamongmen/notcurses

PS: dank (the guy behind it) is definitely one of a kind, just read the releases haha

PPS: here is a doom running through notcurses in the terminal: https://www.youtube.com/watch?v=a_w5rh3c76g

The Xfce 4.20 schedule can be found on the Xfce.org Wiki. Expect Xfce 4.20 to offer up more Wayland support improvements, bug fixes, translation updates, and other modernization improvements. The developers have been hoping that Xfce 4.20 will feature usable Wayland support while retaining X11 compatibility.

Hello,

So I've been a long time Linux user (since 2000) and for the past 20 years, I've been using exclusively Ubuntu and its flavours. Lately I've been seeing posts and articles about how Ubuntu's Snaps are ruining the user experience and causing a lot of discontent. Since I was on the verge of scrapping Windows on my machine and going full Linux.

I started to explore the different distros out there. I installed Linux Mint, (K/L)Ubuntu, Ubuntu Budgie, Debian, Endeavour OS (Arch), Bazzite, Fedora, OpenSuse Tumbleweed, Elementary OS, Fedora Kinoite, Nobara, etc. I wanted to see which one could be my next long run install it and forget it distro. In the end, I was already comfortable with Kubuntu and the few tests I tried in a VM seemed like it was still pretty solid and I really didn't have any reason to change. So I installed Kubuntu as my main and only OS... And I'm starting to regret it dearly.

Snaps really is awful. And the only reason is because Canonical is forcing it on its users. Modifying APT to install Snap packages instead of Debian packages?! And having certain software exclusively available as Snaps? Firefox, Thunderbird, CUPS, FFMpeg, and some of their own utilities like Firmware Updater, and even some KDE core stuff apparently?

So as I was finishing configuring my freshly installed Kubuntu, I was having problems with SDDM. My computer would completely freeze whenever I logged out. Like nothing worked except the power button on my PC. I installed the NVidia drivers and that appeared to have fixed it. I also installed ZSH and set it as my default shell. However, upon reboot, I realized all my Snap based apps were gone from my application menu. I couldn't even set them as default apps in the control center. Firefox being one of them and that's why I noticed.

After checking in the Discover app, I saw it was still installed. I noticed a bunch other ones were missing, but they all appeared as installed. I tried uninstalling Firefox and reinstalling, but that didn't work. I don't know whether it's Snap or KDE that's broken. So I started removing all the Snap variants and installing their Flatpak counterpart instead. But I soon realized this couldn't be done with all software. Like CUPS. The printing system. It's only available as a Snap??? You can't even install it as a Debian package? Some apps are only available as Snaps and they won't show up in my KDE applications menu or anywhere else.

This is incredibly frustrating and disappointing. I feel like I'm being pushed in a corner by Canonical. I'm afraid I really have to switch distributions after all these years. I think I'll be installing Debian 12 stable. Besides, with Flatpak I can get fairly updated applications instead of the .deb packages. So the "old packages" reputation becomes almost irrelevant.

UPDATE:

So installing zsh and setting it as my default shell is what broke Snap. Apparently, zsh doesn't run any of the /etc/profile and /etc/profile.d/ scripts which run scripts that set up environment variables for snap and flatpak and stuff. Adding the following line to /etc/zsh/zprofile fixed my problem:

emulate sh -c 'source /etc/profile'

Anyway, it's still bullshit.

UPDATE 2:

Thanks @Ephera@lemmy.ml for the advice. I've since reverted my default shell to bash in my /etc/passwd file and configured my console app to start ZSH instead to avoid any further problems. #LessonsLearned

I was testing out Debian in a VM and trying to set up Timeshift to see if I can make snapshots and Timeshift didn't work because of how Debian sets up volumes with BTRFS.

Apparently Timeshift uses Ubuntu's way of setting up volumes and nothing else. Check this video to find out how to install Debian on BTRFS so it works with Timeshift.

Just got back from a long but enjoyable day as I've convinced yet another to escape Windows and join Linux

Hopefully they should feel more comfortable with building their own computer and using Linux in general as I went through the entire process with them; from having them insert their new CPU all the way to boot switching between Linux and Windows 10 via ~~BIOS~~ UEFI

They've got a few proprietary requirements remaining (hence the dual boot) but 95% of their apps are now on PopOS (they're planning to switch to Arch in about 3-4 months after some certain conditions are met)

Just wanted to share this as I've missed posting on the fedicomms and also wanted to provide an update for afking🤗

Anyways here's another to Windows's death ~~knell~~ null!🎉

https://security-tracker.debian.org/tracker/CVE-2024-47176, archive

As of 10/1/24 3:52 UTC time, Trixie/Debian testing does not have a fix for the severe cupsd security vulnerability that was recently announced, despite Debian Stable and Unstable having a fix.

Debian Testing is intended for testing, and not really for production usage.

https://tracker.debian.org/pkg/cups-filters, archive

So the way Debian Unstable/Testing works is that packages go into unstable/ for a bit, and then are migrated into testing/trixie.

Issues preventing migration: ∙ ∙ Too young, only 3 of 5 days old

Basically, security vulnerabilities are not really a priority in testing, and everything waits for a bit before it updates.

I recently saw some people recommending Trixie for a "debian but not as unstable as sid and newer packages than stable", which is a pretty bad idea. Trixie/testing is not really intended for production use.

If you want newer, but still stable packages from the same repositories, then I recommend (not an exhaustive list, of course).:

• Opensuse Leap (Tumbleweed works too but secure boot was borked when I used it)
• Fedora

If you are willing to mix and match sources for packages:

• Flatpaks
• distrobox — run other distros in docker/podman containers and use apps through those
• Nix

Can get you newer packages on a more stable distros safely.

i've recently acquired a 4060 ti for €300 from a seller that i've been told was reliable. after installing the gpu and updating the drivers to the latest recommended ones i've noticed odd lag spikes lasting several seconds when using blender, these did not happen when i used my previous gtx 1060 ti.
How can i go about diagnosing if it's a gpu or driver issue? any benchmarks or tools i should use?

i'm on linux mint 21.3 cinnamon.

cross-posted from: https://lemmy.zip/post/23601247

I hope this goes without saying but please do not run this on machines you don't own.

The good news:

• the exploit seems to require user action

The bad news:

• Device Firewalls are ineffective against this

• if someone created a malicious printer on a local network like a library they could create serious issues

• it is hard to patch without breaking printing

• it is very easy to create printers that look legit

• even if you don't hit print the cups user agent can reveal lots of information. This may be blocked at the Firewall

TLDR: you should be careful hitting print

cross posted from: https://programming.dev/post/19937352

cross-posted from: https://ani.social/post/6217644

This is a really great article about how to use BTRFS snapshots with examples.