Mailinglist Archive: opensuse-buildservice (351 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] osc submitreq tries to send a submission to the wrong project
- From: Klaas Freitag <freitag@xxxxxxx>
- Date: Sat, 12 Jul 2008 16:35:28 +0200
- Message-id: <200807121635.28249.freitag@xxxxxxx>
Am Samstag, 12. Juli 2008 01:01:55 schrieb Peter Poeml:
Hi,
nightmare case devel project 5 again points to project 1 :-(
POV as long as we successfully avoid circles. However, the question is if we
get a benefit from really using it - a benefit that is bigger than the
confusion that might arise from that. Not sure atm. What do others think?
Klaas
--
Klaas Freitag Architect OPS/IPD
SUSE LINUX Products GmbH - Nuernberg
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
Hi,
Then, I see the following:One or two or three other chained devel projects? Hmm. And finally the
% osc meta pkg openSUSE:Factory gconf2 | grep devel
<devel project="GNOME:Factory"/>
% osc meta pkg GNOME:Factory gconf2 | grep devel
<devel project="GNOME:UNSTABLE"/>
osc looks up in openSUSE:Factory that gconf2's develproject is set to
GNOME:Factory. But it doesn't look there if there is (even) another
develproject.
nightmare case devel project 5 again points to project 1 :-(
I do not see a reason atm why chaining should not be allowed from a technical
Gee... I am not sure if this is intended in this way :-)
POV as long as we successfully avoid circles. However, the question is if we
get a benefit from really using it - a benefit that is bigger than the
confusion that might arise from that. Not sure atm. What do others think?
Klaas
--
Klaas Freitag Architect OPS/IPD
SUSE LINUX Products GmbH - Nuernberg
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |