Bug 820180 - Request for watch 0.3.0
Summary: Request for watch 0.3.0
Alias: None
Product: Fedora
Classification: Fedora
Component: procps
Version: 16
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
: 801626 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2012-05-09 10:54 UTC by Tom Klingenberg
Modified: 2016-02-01 01:56 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2012-07-27 18:52:50 UTC

Attachments (Terms of Use)

Description Tom Klingenberg 2012-05-09 10:54:17 UTC
Currently in Fedora 16 I have watch 0.2.0.

I'd like to have watch 0.3.0 which is available because it has the `--color` switch.

Comment 1 Jaromír Cápík 2012-05-09 11:33:20 UTC
Hello Tom.

AFAIK watch 0.3.0 has never been officially released by the procps (legacy) upstream. The change is available only in form of unofficial patches and as it introduces also UTF8/widechar related changes, it's questionable if such change is minor enough to be considered appropriate for inclusion in already released Fedora 16.
Anyway ... Fedora 18 brings completely reborn next generation procps tools (called procps-ng) including the --color switch. The legacy version became almost unmaintainable and that's why we decided to drop it completely and replace it with procps-ng in Fedora 18.
Please, let me know if you can wait for Fedora 18 or if you really need the requested feature in Fedora 16.

Thank you and have a nice day.


Comment 2 Tom Klingenberg 2012-05-10 11:55:27 UTC
Hello Jaromir,

thanks for the clarification. I was wondering as well because on sourceforge.net I could only find the sources updated until the year 2009 and that codebase was without the --color switch. But found it in some git tree.

Would it be appropriate to get in contact with the current fedora package maintainer and ask to patch for the color switch? AFAIK it's something minor and so probably easily done. Or can I just patch it on my own and rebuild the package (technically this should be possible right? - but I've never done that only tested some rawhide packages in bugreporting).

Comment 3 Jaromír Cápík 2012-05-11 08:45:15 UTC
Hello Tom.

I'm the Fedora's procps maintainer. It is not about the patch creation. It's about the Fedora's update policy I have to follow. If we talk about package updates in scope of stable Fedora releases, then the updates should only aim to fix bugs, and not introduce new features, particularly when those features would materially affect the user or developer experience. Moreover procps can be considered a critical path package and therefore it shouldn't be touched unless it's major functions are broken. So, even if the feature introduction might be easy, we can't simply touch it unless we have a really good reason to do so. And I must admit that I'm really struggling to do that in this case.
I could create something like diagnostic build and share it for testing purposes here, but it would be easier to do a scratch-build of procps-ng for f16 and share it instead of patching the legacy procps version.

Please, let me know if you would like to test the procps-ng 3.3.2 on Fedora 16 instead. That wouldn't be so time consuming and could work better than the currently available F16 version. Just note, that any of these testing packages would probably never get to the official F16 repository.

Please, let me know.

Thank you.


Comment 4 Tom Klingenberg 2012-05-11 13:56:28 UTC
Hi Jaromir,

thanks again for the detailed and well understandable feedback.

You can ask me anytime to test those packages, I'm planing to migrate to Fedora 17 relativly early (after stable release) so if I should test on that version as well, let me know. I also have a Fedora 17 beta install on some other location so I can test there as well (if this helps you).

Thank you!

Kind regards,

Comment 5 Jaromír Cápík 2012-05-21 16:03:22 UTC
Hi Tom.

You can download the procps-ng scratch-builds from the following two locations:


Please, let me know if you like the new version or not. Just a note. The new version is not 100% compatible with the previous one. If there's any important feature missing, then let me know, please.

Thank you and have a nice day.


Comment 6 Tom Klingenberg 2012-05-23 10:08:46 UTC
Hi Jaromir,

I could install the rpm with no problem, the output is not working as expected but I have not analyzed it so far, it looks like two characters are "eaten". Just for reference, I should file a proper bug-report instead maybe, let me know which kind of feedback you prefer:

Standard command, as expected, with colors in output:

    $ phpunit tests/Composer/Test/Util/SpdxLicenseIdentifierTest.php

Watch command, w/o colors:

    $ watch -n 1 phpunit tests/Composer/Test/Util/SpdxLicenseIdentifierTest.php

Gives the "ansi codes" (I do not even know if these are really the correct terms) like:

    [30;42m[2KOK (196 tests, 196 assertions)

Now with colors enabled:

    $ watch -c -n 1 phpunit tests/Composer/Test/Util/SpdxLicenseIdentifierTest.php

It gives no colored output, but the ansi codes are stripped and a space and the opening bracket ( is missing, compare:

    tests, 196 assertions)

This is just for refrence / quick feedback. I have not verified if the phpunit software does actually use the standard codes here (I assume it does). What I can say is, that it works in the terminal when called (here the first command line example). It does not work with using the watch --color (or -c) switch in the same terminal (I'm using the standard gnome terminal).

As some characters are stripped, I might should provide my locale info:

$ locale

I also tried with the -x switch but I think that's specially for ubuntu which uses dash and not bash for sh and it's behaving differently because of being more POSIX strict.

Comment 7 Jaromír Cápík 2012-06-04 11:56:45 UTC
Hi Tom.

Yes, please. Create a new bug report filled against procps-ng in Fedora Rawhide. I would close this one if you have no objections.

Thanks in advance.


Comment 8 Jaromír Cápík 2012-07-27 18:46:05 UTC
*** Bug 801626 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.