Package Details: ozone 28:3.32a-0

Git Clone URL: https://aur.archlinux.org/ozone.git (read-only, click to copy)
Package Base: ozone
Description: Segger Ozone JLink debugger for Linux
Upstream URL: https://www.segger.com/jlink-software.html
Licenses: custom
Groups: jlink
Conflicts: jlink-debugger
Provides: jlink-debugger
Replaces: jlink-debugger
Submitter: AlexisPolti
Maintainer: AlexisPolti
Last Packager: AlexisPolti
Votes: 23
Popularity: 0.50
First Submitted: 2016-06-08 17:22 (UTC)
Last Updated: 2024-03-14 14:32 (UTC)

Latest Comments

« First ‹ Previous 1 2 3

GeirThomassen commented on 2016-08-29 18:13 (UTC)

Great work! One small problem, an ordinary user can't read the register definition files: $ ls -l /opt/SEGGER/Ozone/Config total 8 drwx------ 2 root root 4096 Aug 24 10:25 CPU drwx------ 2 root root 4096 Aug 24 10:25 Peripherals The debugger starts as usual, but emits this error message: Project.AddSvdFile ("ARM7.svd"); Project.AddSvdFile ("ARM7.svd"): invalid filename File.Open: completed in 110 ms

AlexisPolti commented on 2016-06-08 17:50 (UTC)

This package is now deprecated. You should install Ozone instead.

AlexisPolti commented on 2016-03-03 00:36 (UTC)

On a second thought : you're saying that if I keep epoch > 0, any 2.14x will be considered newer as 2.14 ? I'll test it tomorrow. Thanx for the tip :) BTW (as I'm quite new to Arch packaging), what's the problem with incrementing epoch ?

AlexisPolti commented on 2016-03-03 00:30 (UTC)

Sadly Segger released their first version as 2.14. And for AUR packaging system, 2.14a is a downgrade regarding 2.14. So I had to resort to epoch to force 2.14x to be newer as 2.14. If you have a better idea, please don't hesitate, I searched a lot but didn't find anything better than this.

hzy199411 commented on 2016-03-03 00:20 (UTC)

I think you should not change epoch so frequently. beacuse version 2.14c > 2.14b, so you don't need update the epoch.

« First ‹ Previous 1 2 3