this post was submitted on 23 May 2024
478 points (98.8% liked)

linuxmemes

21263 readers
1881 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    478
    Every time I boot up my computer (lemmy.ca)
    submitted 5 months ago by [email protected] to c/[email protected]
    52 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 80 points 5 months ago* (last edited 5 months ago) (2 children)

    WTF are all these "Refresh of version..." updates? Am I unfresh? Do I need to bathe? (probably)

    Edit: It's like it saw my post from yesterday and said "oh you like that do you?"

    [–] [email protected] 59 points 5 months ago (2 children)

    I had been wondering about that too so I looked it up and apparently it's just what discover displays whenever there's an update that doesn't change the version number which is things like rebuilds with a newer compiler. Very confusing wording, I feel like just "update of version [version]" would be less confusing

    [–] [email protected] 18 points 5 months ago (1 children)

    This is why semver is a thing. If a program is released under 1.1.x, and then recompiled with a new compiler, then it can be 1.1.y where y > x

    [–] [email protected] 23 points 5 months ago (1 children)

    A recompilation or repackaging of Linux 6.6.6 is still Linux 6.6.6

    [–] [email protected] 10 points 5 months ago (2 children)

    Yeah, but in the context of flatpak isn't the distribution managed by the developer themselves? Also, in the distro release version case, they usually add something distro specific to differentiate it.

    [–] [email protected] 5 points 5 months ago* (last edited 5 months ago)

    isn't the distribution managed by the developer themselves?

    No, most often it's not.
    Valve literally just had a fiasco with them not long ago with them falsely marking steam as verified when Valve are not the ones packing the Flatpak.

    [–] [email protected] 1 points 5 months ago (1 children)

    I'm not sure about specific packages, but in general a packager may not want to increase the upstream version even if they can do it themselves - for example, they may have made some mistake in the packaging process.

    [–] [email protected] 1 points 5 months ago

    Yes, and hence my comment on flatpak which turns out is false (that the upstream developer is usually the distributor/packager too). And the other still applies, distro usually adds a specific tag anyway for their refresh. Like that one time xz on rolling debian was named something x.y.z-really-a.b.c.

    I think flatpak packagers should also append the specific tag too if that is the case. Like, x.y.z-flatpak-w where w can be the build release version