Per Jessen wrote:

Bernhard M. Wiedemann wrote:

...

Am 08.09.2011 09:25, schrieb Per Jessen:

...

Is there a way of tracking/getting notified of changes to specific areas/packages such that I know that has changed, and that function/regression test is probably needed?

/Per Jessen, Zürich

you could adapt http://openqa.opensuse.org/opensuse/tools/recentchanges.pl in line 28 to filter the time and area of your interest. Currently it outputs all changes to installed packages in last ten days.

But on a running system, right? When I want to test something, I usually set up a test-system from scratch, so that wouldn't really work.

Is there really no way of "subscribing" to <something> (package, area, pattern etc) and be notified when it changes?

/Per Jessen, Zürich

Per, I use hermes to track check-ins to a few packages I care about. I don't know if it can track at a larger scale or not. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

On Tue, Sep 13, 2011 at 8:07 AM, Per Jessen wrote:

Greg Freemyer wrote:

...

Per Jessen wrote:

...

Bernhard M. Wiedemann wrote:

...

Am 08.09.2011 09:25, schrieb Per Jessen:

...

Is there a way of tracking/getting notified of changes to specific areas/packages such that I know that has changed, and that function/regression test is probably needed?

/Per Jessen, Zürich

you could adapt http://openqa.opensuse.org/opensuse/tools/recentchanges.pl in line 28 to filter the time and area of your interest. Currently it outputs all changes to installed packages in last ten days.

But on a running system, right?  When I want to test something, I usually set up a test-system from scratch, so that wouldn't really work.

Is there really no way of "subscribing" to <something> (package, area, pattern etc) and be notified when it changes?

/Per Jessen, Zürich

Per,

I use hermes to track check-ins to a few packages I care about.  I don't know if it can track at a larger scale or not.

Thanks Greg, I'll have to take a closer look at that.

/Per Jessen, Zürich

Per, As an example: Start at: https://hermes.opensuse.org/subscriptions Then click expert interface towards the bottom. Then click "add subscription". Then from the pull-down select OBS: Source Commit Create Subscription Then add filter. That's about as far as my knowledge goes, but I think you have a lot of flexibility in there. Greg -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Bernhard M. Wiedemann wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Am 13.09.2011 08:16, schrieb Per Jessen:

...

Bernhard M. Wiedemann wrote:

...

Am 08.09.2011 09:25, schrieb Per Jessen:

...

Is there a way of tracking/getting notified of changes to specific areas/packages such that I know that has changed, and that function/regression test is probably needed?

/Per Jessen, Zürich

you could adapt http://openqa.opensuse.org/opensuse/tools/recentchanges.pl in line 28 to filter the time and area of your interest. Currently it outputs all changes to installed packages in last ten days.

But on a running system, right? When I want to test something, I usually set up a test-system from scratch, so that wouldn't really work.

Is there really no way of "subscribing" to <something> (package, area, pattern etc) and be notified when it changes?

/Per Jessen, Zürich

https://hermes.opensuse.org/subscriptions lets you subscribe to certain OBS events. e.g. I use it for my bugzilla-OBS integration. And there is opensuse-commit@opensuse.org ML

Ciao Bernhard M.

Thanks Bernhard, thanks Greg - I am in fact subscribed to e.g. FATE via Hermes, but having looked again at Hermes, it sure looks complicated (for the non-initiated). Here is what prompted my question - there is an open issue on the minimum server pattern/selection. Ludwig Nussel has been working on fixing it, and mentioned in the report that it was completely broken on M5, and suggested I keep an eye on factory to keep up with it (minimum server pattern). Greg, in your explanation yesterday, what would I pick instead of OBS commit to keep up with Factory? Sounds like OBS_REPO_PUBLISHED could be the right one? /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org