Package Details: jlink-software-and-documentation 7.82d-0

Git Clone URL: https://aur.archlinux.org/jlink-software-and-documentation.git (read-only, click to copy)
Package Base: jlink-software-and-documentation
Description: Segger JLink software & documentation pack for Linux
Upstream URL: https://www.segger.com/jlink-software.html
Licenses: custom, GPLv2
Conflicts: j-link-software-and-documentation
Replaces: j-link-software-and-documentation
Submitter: AlexisPolti
Maintainer: AlexisPolti (pzl)
Last Packager: AlexisPolti
Votes: 50
Popularity: 0.20
First Submitted: 2016-01-22 00:03 (UTC)
Last Updated: 2022-11-23 16:42 (UTC)

Pinned Comments

AlexisPolti commented on 2019-10-29 19:59 (UTC)

Please allow me at least 24h to build the new package! :)

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

AlexisPolti commented on 2022-11-18 12:42 (UTC) (edited on 2022-11-18 12:47 (UTC) by AlexisPolti)

Effectively chaotic-aur doesn't seem to take epoch into account correctly, which makes the tuple (epoch, rel) non-transitive:

  • 7.82 is older than 7.82b

  • 7.82b is older than 7.82c

  • but 7.82 is newer than 7.82c (!!!)

I reset epoch to 0, to test the behaviour with regular yay, it seems to work. I'm waiting for chaotic-aur to build the package. If it succeeds, let's keep it that way.

taotieren commented on 2022-11-18 03:55 (UTC)

I'm using yay-git. And the chaotic-aur feed is enabled. Jlink compiled packages are also available in chaotic-aur. It saves the process of downloading, decompressing and repackaging.

AlexisPolti commented on 2022-11-17 19:13 (UTC) (edited on 2022-11-17 19:17 (UTC) by AlexisPolti)

Epoch has been incremented when going from 7.82 to 7.82a (49 to 50) as rel doesn't indicate an update. It doesn't need to be incremented when the rel indicates an update, for example when going from 7.82b to 7.82c, as long as they share the same epoch, AFAIK

This is the way this package has always been handled and yay handles it correctly. Which AUR manager are you using ?

taotieren commented on 2022-11-17 17:52 (UTC)

The most recent version updates epoch have not been updated. Caused the jlink* package not to be updated. It will cause users not to receive updates to this package.

AlexisPolti commented on 2022-11-17 13:36 (UTC) (edited on 2022-11-17 13:37 (UTC) by AlexisPolti)

@taotieren: I'm sure I understand what you mean by "the package will not be updated".

I'm using epoch to ensure that 7.82a is considered newer as 7.82, which is not the case with only the rel field. cf. "It is used when the version numbering scheme of a package changes (or is alphanumeric), breaking normal version comparison logic."

But ofc I don't change it between 7.82a and 7.82b (and so on)

Is that a problem?

taotieren commented on 2022-11-17 05:50 (UTC)

The epoch tag is a mandatory update. It is recommended to set null or 0. Otherwise, the version number will only be updated and the package will not be updated. Thank you.

- epoch=50
+ epoch=

taotieren commented on 2022-06-27 10:04 (UTC)

I hope you get well soon. Thank you for your contribution.

AlexisPolti commented on 2022-06-26 20:22 (UTC)

@taotieren: sorry, fixed! To be honest, I felt in a campfire last month and burnt my hands in the 3rd degree. Since then I've slowly recovered (first I dictated my code to a friend / co-worker), then I typed with 2 fingers, and so on. That's why I made so many mistakes lately. But it's getting better, I should be able to be fully operational soon :) 

taotieren commented on 2022-06-26 14:03 (UTC)

Hello, can you add JFlashSPIExe.desktop file to JFlashSPIExe. Thank you

dp7hgh7 commented on 2022-06-25 22:53 (UTC)

Thanks!