40
submitted 16 hours ago* (last edited 15 hours ago) by hello_hello@hexbear.net to c/libre@hexbear.net

The GNOME Calendar maintainers bring up the fact that Linux Mint ships a nearly 2 year old version of GNOME Calendar to its users and still keep the GNOME branding and support links.

The Linux Mint team don't see an issue with shipping old, unmaintained software and would rather ignore the issue and pretend it doesn't exist. The recent releases of Linux Mint have downgraded several pieces of software to their older GNOME 3 versions which re-introduce fixed bugs and removes newer features. This was done to support their theming engine, despite the fact that their theming is already several releases too old for GNOME apps.

In addition, they utilize several old GNOME related system components that apps rely on such as GNOME Calendar so even installing a newer version of Calendar wouldn't be enough.

This ties into a much larger issue of "Long Term Support" desktop operating systems where software can be pulled back for nearly 5 years (or even longer under a contract). Necessary fixes that are too complicated to be patched back in (or count as features) are then missed by users. Users end up using years-old flagship desktops (GNOME and KDE) and get their first impression of those projects from versions that none of the upstream maintainers support.

It's a shitty situation all around: I personally think it's incredibly important to use the latest release of software that's supported by upstream. GNOME does not actively support older versions of its app and shell from more than a release ago and distributions shipping these older GNOME releases can only cause damage to GNOME's reputation.

If this isn't possible, then I don't think it's right to still keep the branding and trademark of the application, much less keep the original support links intact.

you are viewing a single comment's thread
view the rest of the comments
[-] ashinadash@hexbear.net 7 points 12 hours ago

Aw hell yeah, Tesk article.

The issue itself was originally calm and straight to the point. Half a year passed by and there was no response. Then, the packager was pinged, they chimed in, and changed the subject immediately. The tone shifted, and they took the easy way out by locking the issue and misleadingly stating that this is an upstream problem for choosing the wrong license.

In other words, you have two choices:

You kindly ask, and nothing happens apart from your own time and energy getting wasted for a considerable amount of time, with constant red herring or silence.

You start acting like a ‘dick’, and now they use this as an excuse to no longer communicate with you, all the while still refusing to address the underlying issue.

Sounds like they're the ones acting like a 'dick' to me... This does make me think of Stenzek, though, which near as I can tell the Stenzek/AUR stuff was a similar-ish thing.

[-] hello_hello@hexbear.net 4 points 10 hours ago* (last edited 10 hours ago)

Stenzek actually did change the license of duckstation to a nonfree license but it didn't stop anyone from redistributing duckstation because people started saying that they're shipping a build script to download duckstation from the Internet and not duckstation itself and then he started going to war with Arch Linux (and later NixOS lmao because they used the same reason).

You can't stop the Linux G@ymer doggirl-smug

this post was submitted on 25 Jul 2026
40 points (100.0% liked)

libre

10220 readers
104 users here now

Welcome to libre

A comm dedicated to the fight for free software with an anti-capitalist perspective.

The struggle for libre computing cannot be disentangled from other forms of socialist reform. One must be willing to reject proprietary software as fiercely as they would reject capitalism. Luckily, we are not alone.

libretion

Resources

  1. Free Software, Free Society provides an excellent primer in the origins and theory around free software and the GNU Project, the pioneers of the Free Software Movement.
  2. Switch to GNU/Linux! If you're still using Windows in $CURRENT_YEAR, try a GNU/Linux distribution.

Rules

  1. Be on topic: Posts should be about free software and other hacktivst struggles. Topics about general tech news should be in the technology comm or programming comm. That doesn't mean all posts have to be serious though, memes are welcome!
  2. Avoid using misleading terms/speading misinformation: Here's a great article about what those words are. In short, try to avoid parroting common Techbro lingo and topics.
  3. Avoid being confrontational: People are in different stages of liberating their computing, focus on informing rather than accusing. Debatebro nonsense is not tolerated.
  4. All site-wide rules still apply

Artwork

founded 5 years ago
MODERATORS