Hm...
You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right.
2012/10/18 Jos Poortvliet jos@opensuse.org:
On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote:
Hi,
Is there a page to see full list of submit requests, ordered by date? This
statistics is of quite interest.
For instance, there is no reaction for two month: (It is not ok for devel:
project, I think)
https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam
qp
I think, having such a page, such statistics, one would be able to
redistribute his power.
Not a bad idea at all - it'd nice to show which projects need some help, which are doing very well etcetera. Maybe a top-ten of fastest SR/MR solvers, too ;-)
Crazy idea: Adrian responded to you that it is possible to request this info from the API. If you got the skillzz to do that, it'd be nice to publish those statistics somewhere - and that part I could help with. Something like a weekly overview of the health of the OBS projects and stuff like that.
Up for it?
/Jos
Ok,
I've put test table here: http://0x2207.blogspot.com/2012/10/obs-submit- request-top.html
On Sat, Oct 20, 2012 at 5:28 AM, Matwey V. Kornilov matwey.kornilov@gmail.com wrote:
Ok,
I've put test table here: http://0x2207.blogspot.com/2012/10/obs-submit- request-top.html
The 2 oldest are just add role SRs. Maybe you should break out the "add role" SRs from the rest. They seem less important to me, but then again I've never had one sit around for more than a week or two.
Greg
Am 20.10.2012 16:32, schrieb Greg Freemyer:
On Sat, Oct 20, 2012 at 5:28 AM, Matwey V. Kornilov matwey.kornilov@gmail.com wrote:
Ok,
I've put test table here: http://0x2207.blogspot.com/2012/10/obs-submit- request-top.html
The 2 oldest are just add role SRs. Maybe you should break out the "add role" SRs from the rest. They seem less important to me, but then again I've never had one sit around for more than a week or two.
And the old validators requests are actually to delete the packages and the project. In that case it's pretty obvious that they are unmaintained.
Greetings, Stephan
Am Montag, 22. Oktober 2012, 10:59:41 schrieb Stephan Kulow:
Am 20.10.2012 16:32, schrieb Greg Freemyer:
On Sat, Oct 20, 2012 at 5:28 AM, Matwey V. Kornilov matwey.kornilov@gmail.com wrote:
Ok,
I've put test table here: http://0x2207.blogspot.com/2012/10/obs-submit- request-top.html
The 2 oldest are just add role SRs. Maybe you should break out the "add role" SRs from the rest. They seem less important to me, but then again I've never had one sit around for more than a week or two.
And the old validators requests are actually to delete the packages and the project. In that case it's pretty obvious that they are unmaintained.
Yep, I removed the project now.
Most of them are orphaned. Should obs purge such requests from database or change their state to 'incorrect'?
Stephan Kulow wrote:
And the old validators requests are actually to delete the packages and the project. In that case it's pretty obvious that they are unmaintained.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
There is the case, when you want to have several packages in sync, like:
packageA-ver1-rev1, packageB-ver1-rev1, packageC-ver1-rev1 an so on...
but sometimes it happens this bad case, when one package was rebuild by OBS and another - didn't:
packageA-ver1-rev1, packageB-ver1-rev9, packageC-ver1-rev14 ...
My questions are: What is the best, less intrusive, way to sync it again up to a revision number ? How to prevent this in the future ?
Cheers.
On Wednesday 2015-02-18 18:32, Opensuse user wrote:
but sometimes it happens this bad case, when one package was rebuild by OBS and another - didn't:
packageA-ver1-rev1, packageB-ver1-rev9, packageC-ver1-rev14 ...
My questions are: What is the best, less intrusive, way to sync it again up to a revision number ? How to prevent this in the future ?
Are they in any way _linked?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Currently they linked like (for package1):
<link package="package2" cicount="copy" />
But this is the little different case, since package1 are actually links to package2, while I want only to link version + revision.
So if you want to link two or more packages by version + revision only, how would you do this initially ?
Cheers.
18.02.2015 19:36, Jan Engelhardt пишет:
On Wednesday 2015-02-18 18:32, Opensuse user wrote:
but sometimes it happens this bad case, when one package was rebuild by OBS and another - didn't:
packageA-ver1-rev1, packageB-ver1-rev9, packageC-ver1-rev14 ...
My questions are: What is the best, less intrusive, way to sync it again up to a revision number ? How to prevent this in the future ?
Are they in any way _linked?
On Wednesday 2015-02-18 19:18, Opensuse user wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Currently they linked like (for package1):
<link package="package2" cicount="copy" />
But this is the little different case, since package1 are actually links to package2, while I want only to link version + revision.
So if you want to link two or more packages by version + revision only, how would you do this initially ?
I would not do it at all. If the packages have nothing to do with one another and thus do not have a _link, there is no point in forcing one.
buildservice@lists.opensuse.org
-
Adrian Schröter -
Greg Freemyer -
Jan Engelhardt -
Matwey V. Kornilov -
Matwey V. Kornilov
-
Opensuse user -
Stephan Kulow