Login
You're viewing the techdon.dev public feed.
  • May 11, 2026, 5:29 PM

    All of this brings me to GNOME Calendar and @linuxmint. For years, we've been dealing with users reporting issues about Linux Mint's package of GNOME Calendar to us, that were either never present or addressed releases ago.

    Just a couple of examples:

    There were a couple of discussions regarding this in the past, in chat, but none of it ended up being productive. Eventually, we got fed up by it and I opened issue #1 on Mint's package of GNOME Calendar — the first issue ever in their package's repository — asking them to remove all links pointing to upstream GNOME Calendar and rebranding the app. This had no response for 6 months, all the while we were still getting bug reports about Mint's broken package. @nekohayo eventually got fed up (again!) and pinged the packager. The packager replied with something completely unrelated and asked which modifications we did not like, completely ignoring our actual request. So, I just told him bluntly that we don't have the time to look through the code just to pinpoint specific issues, so I'll just loosely say "everything", and the only way for us to be happy is if they could rebrand and we can move on.

    Then, once again, the packager responds with something unrelated once again, ignoring the essence of my comment, and follows with a whataboutism — "As i said, 46 and 48 are used by millions of people right now in Ubuntu LTS and Debian Stable. Are you going to request Debian and Ubuntu stop shipping GNOME apps?" — in other words, "what about Ubuntu LTS and Debian Stable?" - as a bonus, twisting my words and going from GNOME Calendar to "GNOME apps".

    So, once again, I reminded that this is not what the issue is about.

    As a side note: no, never would we go after Debian or Ubuntu over this. If the distribution in question is doing its job properly by simply not bothering the people writing the software that they package, then why should we go after them? They are not the ones misleading users into opening in the wrong place, so there is no reason for us to be upset about. In this case, Linux Mint is leeching off of Debian, and pushing their responsibility onto us.

    The packager then explains what to do, and redirects us to Debian to take down the package, essentially roping Debian into Linux Mint's problem — all the while completely ignoring the premise of this post. Sure, both Linux Mint and Debian's packages share the same source; however, this is just a technical detail. The actual problem, one that regularly affects us, is that Linux Mint users report issues to us, whereas Debian users report them to Debian.

    So, I remind him bluntly that this is not our responsibility as an upstream to fix his problems.

    He then suggests to incorporate code upstream to check if the user is running an outdated version or not. In other words, either phoning home, somehow keeping track of releases every 6 months, or something unrealistic.

    I lose my patience and hostily tell him that we upstreams don't care about how distributions operate, and reminded, once again, that all we want is for them to rebrand. To which he replied with "If you don't care, then neither do we." — confirming that Linux Mint doesn't care about Debian or even itself as a distribution. Then says "probably requires GNOME Calendar to move away from free licenses" and locks the issue — once again, completely ignoring the essence of this entire issue.

    Now they know what the problem is, and have refused to act on it by shoving their responsibilities onto us, but this time intentionally, because that should show upstream for hurting my feelings, never mind the fact that we are the ones doing the hard work, and they are making us do more work. This is the length some distributors will go to abuse people's generosity.

    #MaintainerLife #Linux #GNOME #GNOMECalendar #FOSS #OpenSource #FreeSoftware

    💬 2🔄 1⭐ 5

Replies

  • May 11, 2026, 5:53 PM

    @TheEvilSkeleton @linuxmint @nekohayo okay, so to be consistent, I expect you to now file issues and be hostile towards every LTS distro, that ships GNOME - Ubuntu, Debian, openSUSE Leap.

    You really don't see how stupid this is? The whole POINT of LTS distributions is to ship outdated packages. That's how they operated FOR DECADES. You have NO RIGHT to request removal of a package, or rebranding it, simply because you don't feel like dealing with bug reports coming from LTS

    This is so stupid

    💬 1🔄 0⭐ 0
  • May 11, 2026, 5:54 PM

    @TheEvilSkeleton @linuxmint @nekohayo if you tried that with Ubuntu or openSUSE you would just get laughed at and the issue would be locked without any further discussion. But now you feel strong and powerful picking at a smaller project. Good job you. And then you wonder, why people call GNOME development team toxic...

    💬 0🔄 0⭐ 0
  • May 11, 2026, 6:13 PM

    @leniwcowaty @TheEvilSkeleton @linuxmint @nekohayo There is a difference between shipping outdated packages and offloading your issues to upstream. Distributions can (and should) ship outdated software with changed branding.

    > You have NO RIGHT to request removal of a package

    Statements like this make me seriously question whether I should publish any of my work under an open source license, which I think is a rather sad thing :(

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • May 11, 2026, 6:19 PM

    @leniwcowaty @TheEvilSkeleton @linuxmint @nekohayo I doubt it, considering they are explicitly asked to change branding.
    Once again there is also a difference between having 'GNOME Calendar' with a link to the GNOME issuetracker and a forked 'Mint Calendar' which has a credit line in the about section.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 2
  • May 11, 2026, 6:51 PM

    @bragefuglseth @TheEvilSkeleton If you do decide to write one (or one about distro-packaging in general), feel free to send me a message, I have an additional argument that I'm happy to share (I don't want to share it before, it would ruin the fun :)).

    💬 0🔄 0⭐ 1