| Summary: | app-misc/utimer-0.4-r1: core dump on invalid TIMELENGTH | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | lekto |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | ceamac, jstein, treecleaner |
| Priority: | Normal | Keywords: | PMASKED |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
btimer |
||
|
Description
lekto
2023-12-26 15:01:08 UTC
Thank you for the report. This should be fixed upstream. So if there is a real need for such a tool, someone should fork it and maintain it. One has to keep in mind that a proper parser for utime will have 10x more code lines than the utime source. Hardly any distributions ship this package: https://repology.org/project/utimer/versions The bug seems to be not very critical to me and such a simple program could work for another decade. Which alternative tools do the same job? Honestly, ping -c could be used instead of it, but utimer has better interface. I had some time and willingness to write Bash script as utimer replacement, I called it btimer from Bash timer. Created attachment 880744 [details]
btimer
Package removed. |