[opensuse-buildservice] osc init problem.
Hello, I had a hard drive crash, so I wanted to start my osc projects fresh on a new drive. I think there may be a bug in osc. I did the following. cd ~/work/BS/opensuse/ gerberb@suse103:~/work/BS/opensuse> osc co server:mail gerberb@suse103:~/work/BS/opensuse> osc co games:roleplay gerberb@suse103:~/work/BS/opensuse> osc co devel:languages:python gerberb@suse103:~/work/BS/opensuse> osc co devel:languages:perl gerberb@suse103:~/work/BS/opensuse> osc co home:gerberb gerberb@suse103:~/work/BS/opensuse> l total 64 drwxr-xr-x 7 gerberb zenez 4096 2008-02-11 22:51 ./ drwxr-xr-x 3 gerberb zenez 4096 2008-02-11 21:58 ../ drwxr-xr-x 249 gerberb zenez 12288 2008-02-11 22:24 devel:languages:perl/ drwxr-xr-x 137 gerberb zenez 4096 2008-02-11 22:43 devel:languages:python/ drwxr-xr-x 6 gerberb zenez 4096 2008-02-11 22:46 games:roleplay/ drwxr-xr-x 11 gerberb zenez 4096 2008-02-11 22:03 home:gerberb/ drwxr-xr-x 72 gerberb zenez 4096 2008-02-11 23:10 server:mail/ There should be an easy way to init all projects quickly. I tried the following. gerberb@suse103:~/work/BS/opensuse> osc init home:gerberb osc init: takes exactly 2 arguments (1 given) Try 'osc help init' for info. gerberb@suse103:~/work/BS/opensuse> osc init home:gerberb * osc init: takes exactly 2 arguments (6 given) Try 'osc help init' for info. The above has two arguments. If I cd to each directory and then do a ls in each directory and output to a file and then file in a for loop on each they init. But shouldn't I be able to do an init right after a check out? This is what worked. gerberb@suse103:~/work/BS/opensuse> for i in `cat blglist`; do osc init home:gerberb $i; done Thanks, -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Boyd Lynn Gerber wrote:
But shouldn't I be able to do an init right after a check out?
You don't need init after checkout. osc init is a hack to avoid a full checkout if you already have the sources from somewhere else. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi! Am Dienstag, 12. Februar 2008 07:47 schrieb Boyd Lynn Gerber:
gerberb@suse103:~/work/BS/opensuse> osc init home:gerberb * osc init: takes exactly 2 arguments (6 given) Try 'osc help init' for info.
The above has two arguments.
No it doesn't, except in the rare case where home:gerberb is the only entry in the directory current directory. Even worse, in your current case it would expand to "devel:languages:perl games:roleplay home:gerberb server:mail" which is problably not what you want.
If I cd to each directory and then do a ls in each directory and output to a file and then file in a for loop on each they init. But shouldn't I be able to do an init right after a check out?
This is what worked.
gerberb@suse103:~/work/BS/opensuse> for i in `cat blglist`; do osc init home:gerberb $i; done
You could probably even do "for i in home:gerberb/*"`; do osc init home:gerberb $i; done" However I, too, think that it would be nice to have in option in osc init to init all packages in a project. Regards, Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, On Mon, Feb 11, 2008 at 11:47:45PM -0700, Boyd Lynn Gerber wrote:
Hello,
I had a hard drive crash, so I wanted to start my osc projects fresh on a new drive. I think there may be a bug in osc.
I did the following.
In short, what you show below is actually what is to be expected.
cd ~/work/BS/opensuse/ gerberb@suse103:~/work/BS/opensuse> osc co server:mail gerberb@suse103:~/work/BS/opensuse> osc co games:roleplay gerberb@suse103:~/work/BS/opensuse> osc co devel:languages:python gerberb@suse103:~/work/BS/opensuse> osc co devel:languages:perl gerberb@suse103:~/work/BS/opensuse> osc co home:gerberb gerberb@suse103:~/work/BS/opensuse> l total 64 drwxr-xr-x 7 gerberb zenez 4096 2008-02-11 22:51 ./ drwxr-xr-x 3 gerberb zenez 4096 2008-02-11 21:58 ../ drwxr-xr-x 249 gerberb zenez 12288 2008-02-11 22:24 devel:languages:perl/ drwxr-xr-x 137 gerberb zenez 4096 2008-02-11 22:43 devel:languages:python/ drwxr-xr-x 6 gerberb zenez 4096 2008-02-11 22:46 games:roleplay/ drwxr-xr-x 11 gerberb zenez 4096 2008-02-11 22:03 home:gerberb/ drwxr-xr-x 72 gerberb zenez 4096 2008-02-11 23:10 server:mail/
There should be an easy way to init all projects quickly. I tried the following.
gerberb@suse103:~/work/BS/opensuse> osc init home:gerberb osc init: takes exactly 2 arguments (1 given) Try 'osc help init' for info.
-> one argument missing indeed.
gerberb@suse103:~/work/BS/opensuse> osc init home:gerberb * osc init: takes exactly 2 arguments (6 given) Try 'osc help init' for info.
* expands to a number of arguments higher than 2, so that's not working either.
The above has two arguments. If I cd to each directory and then do a ls in each directory and output to a file and then file in a for loop on each they init. But shouldn't I be able to do an init right after a check out?
This is what worked.
gerberb@suse103:~/work/BS/opensuse> for i in `cat blglist`; do osc init home:gerberb $i; done
That's what you can do, indeed. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (4)
-
Boyd Lynn Gerber -
Dr. Peter Poeml -
Matthias Bach -
Michal Marek