[opensuse-buildservice] ANN: Yabsc 0.4
I have just made another release of Yabsc. Source can be downloaded from http://www.funktronics.ca/yabsc/ Packages can be found at http://software.opensuse.org/search?baseproject=openSUSE%3A10.3&p=1&q=yabsc Changes include: - Incremental package search - Build target filtering If there are any more features anybody would like to see, please let me know. -- James Oakley jfunk@funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday, 5. March 2008 20:28:35 James Oakley wrote:
If there are any more features anybody would like to see, please let me know
It would be nice to be able to view log files directly when clicking on the status in the matrix view (instead of showing package info and requiring you to click a second time on 'failed' etc). Also the detailed view could show which packages block the build (like it lists the packages for an expansion error). Bye, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 3/5/2008 at 21:28, James Oakley <jfunk@funktronics.ca> wrote: I have just made another release of Yabsc.
Source can be downloaded from http://www.funktronics.ca/yabsc/
Packages can be found at http://software.opensuse.org/search?baseproject=openSUSE%3A10.3&p=1&q=yabsc
Changes include: - Incremental package search - Build target filtering
If there are any more features anybody would like to see, please let me know.
James, I tried it a bit last days and I have to say it's quiet a nice piece of a tool.. I'll probably use it more often. One thing I could use (maybe others too) would be the option for sort of a meta project. I am maintainer of several packages, scattered over several projects, some being GNOME:Community and KDE:Community and almost all of the games:* nevertheless, I'm hardly interested in all the packages happening in those projects (when it comes to build status of course). So my idea would be to have a 'My packages'-'project', where I can put my packages, that are cluttered over the whoe BS and show the status for all of those.. as that is actually what I am interested in... (hmm. after rereading, I wonder myself if anybody understands what I mean...) I'm sure you get the idea, right? Do you think something like this would be possible? Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On March 6, 2008, Dominique Leuenberger wrote:
So my idea would be to have a 'My packages'-'project', where I can put my packages, that are cluttered over the whoe BS and show the status for all of those.. as that is actually what I am interested in... (hmm. after rereading, I wonder myself if anybody understands what I mean...)
I'm sure you get the idea, right? Do you think something like this would be possible?
This is the sort of thing that should be implemented server-side. If you define this metaproject in the client, then it will break once you move or rename a package. You would also have to manually maintain the list, which would quickly become tiresome. What would be better would be an API call that would return a list of packages which the user is a maintainer of. -- James Oakley jfunk@funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 3/6/2008 at 19:56, James Oakley <jfunk@funktronics.ca> wrote: On March 6, 2008, Dominique Leuenberger wrote: So my idea would be to have a 'My packages'-'project', where I can put my packages, that are cluttered over the whoe BS and show the status for all of those.. as that is actually what I am interested in... (hmm. after rereading, I wonder myself if anybody understands what I mean...)
I'm sure you get the idea, right? Do you think something like this would be possible?
This is the sort of thing that should be implemented server-side. If you define this metaproject in the client, then it will break once you move or rename a package. You would also have to manually maintain the list, which would quickly become tiresome.
What would be better would be an API call that would return a list of packages which the user is a maintainer of.
I see what you mean... the problem there might be, that 'maintainer' of a random project has automatically maintainer status in the packages below. So just checking for packages with me as maintainer will possibly return a much larger list than I'm interested in. but an extension of the API might be the only thing working out here I think. Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I see what you mean... the problem there might be, that 'maintainer' of a random project has automatically maintainer status in the
Dominique Leuenberger wrote: packages below. Not quite: $ osc maintainer server:database rmax, darix, peternixon, michal-m, LenzGr, weigon $ osc maintainer server:database mysql-proxy darix Of course, project maintainers have full control over the packages, but they don't become package maintainers automatically. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 3/7/2008 at 09:57, Michal Marek <mmarek@suse.cz> wrote: Dominique Leuenberger wrote: I see what you mean... the problem there might be, that 'maintainer' of a random project has automatically maintainer status in the packages below.
Not quite: $ osc maintainer server:database rmax, darix, peternixon, michal-m, LenzGr, weigon $ osc maintainer server:database mysql-proxy darix
Of course, project maintainers have full control over the packages, but they don't become package maintainers automatically.
Michal, thanks for clarifying it... I was wrongly assuming it and the lack of a Linux Desktop at mywork place (*sigh*) did not make it easier for me to check it. But some companies are to old fashioned to change... Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2008-03-07 08:57:27 +0100, Michal Marek wrote:
I see what you mean... the problem there might be, that 'maintainer' of a random project has automatically maintainer status in the
Dominique Leuenberger wrote: packages below.
Not quite: $ osc maintainer server:database rmax, darix, peternixon, michal-m, LenzGr, weigon $ osc maintainer server:database mysql-proxy darix
Of course, project maintainers have full control over the packages, but they don't become package maintainers automatically.
and on projects where i am maintainer i sometimes remove the maintainer line in the package. sorry for sabotaging that idea ;p darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 07 March 2008 08:41:52 wrote Dominique Leuenberger:
On 3/6/2008 at 19:56, James Oakley <jfunk@funktronics.ca> wrote:
On March 6, 2008, Dominique Leuenberger wrote:
So my idea would be to have a 'My packages'-'project', where I can put my packages, that are cluttered over the whoe BS and show the status for all of those.. as that is actually what I am interested in... (hmm. after rereading, I wonder myself if anybody understands what I mean...)
I'm sure you get the idea, right? Do you think something like this would be possible?
Do you speak about a "Watched Packages" like we have with "Watched Projects" atm ?
This is the sort of thing that should be implemented server-side. If you define this metaproject in the client, then it will break once you move or rename a package. You would also have to manually maintain the list, which would quickly become tiresome.
What would be better would be an API call that would return a list of packages which the user is a maintainer of.
yes, we lack this definitive ... Just created a bug entry for this #368084 .
I see what you mean... the problem there might be, that 'maintainer' of a random project has automatically maintainer status in the packages below. So just checking for packages with me as maintainer will possibly return a much larger list than I'm interested in.
hm, when you have suggestions, what kind of search results would be interessting for you, please add it to the bugreport. thanks adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 3/7/2008 at 10:16, Adrian Schröter <adrian@suse.de> wrote: On Friday 07 March 2008 08:41:52 wrote Dominique Leuenberger:
On 3/6/2008 at 19:56, James Oakley <jfunk@funktronics.ca> wrote:
So my idea would be to have a 'My packages'-'project', where I can put my packages, that are cluttered over the whoe BS and show the status for all of those.. as that is actually what I am interested in... (hmm. after rereading, I wonder myself if anybody understands what I mean...)
I'm sure you get the idea, right? Do you think something like
On March 6, 2008, Dominique Leuenberger wrote: this would
be possible?
Do you speak about a "Watched Packages" like we have with "Watched Projects" atm ?
This is the sort of thing that should be implemented server-side. If you define this metaproject in the client, then it will break once you move or rename a package. You would also have to manually maintain the
Yes, something in this form... as I described, I have about 20 packages (ok, I'm a small fish in a big pool) across several projects. Especially now with Factory upgrades, I see them failing from time to time (gcc upgrades, whatever can happen) and it would be very handy to have 'my' packages in an easy overview. list,
which would quickly become tiresome.
What would be better would be an API call that would return a list of packages which the user is a maintainer of.
yes, we lack this definitive ...
Just created a bug entry for this #368084 .
I see what you mean... the problem there might be, that 'maintainer' of a random project has automatically maintainer status in the packages below. So just checking for packages with me as maintainer will possibly return a much larger list than I'm interested in.
hm, when you have suggestions, what kind of search results would be interessting for you, please add it to the bugreport.
Thanks for the bug report.. I'll subscribe to it and should I have some more comments, participate on it. Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (6)
-
Adrian Schröter -
Dominique Leuenberger -
James Oakley -
Marcus Rueckert -
Michal Marek -
Stephan Binner