[opensuse-buildservice] how to deal with osc build?
According to this email http://lists.opensuse.org/opensuse-buildservice/2006-09/msg00133.html it is possible to execute: $ osc build Fedora_Extras_5 i586 *spec But when I try that I get: $ osc build Fedora_Extras_5 i586 /var/tmp/gramps/gramps.spec Getting buildinfo from server Traceback (most recent call last): File "/usr/bin/osc", line 7, in <module> commandline.main() File "/usr/lib/python2.5/site-packages/osc/commandline.py", line 1050, in main cmd(args) File "/usr/lib/python2.5/site-packages/osc/commandline.py", line 768, in buildinfo package = store_read_package(wd) File "/usr/lib/python2.5/site-packages/osc/core.py", line 1280, in store_read_package p = open(os.path.join(dir, store, '_package')).readlines()[0].strip() IOError: [Errno 2] No such file or directory: './.osc/_package' wrong repo/arch? What is the error? Is the packagecachedir (/var/tmp/osbuild-packagecache) missing? Is the build-root missing (/var/tmp/build-root-%(repo)s-%(arch)s)? Is the repo not good, if not what is not good? I have the packages on a DVD that came Januari 2007 issue of linuxformat. I execute osc in: /media/LXFDVD88A/Fedora/RPMS Is this http://lists.opensuse.org/opensuse-buildservice/2006-09/msg00133.html information available on the opensuse wiki? -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Richard, On Saturday 30 December 2006 09:48, Richard Bos wrote: [...]
'_package')).readlines()[0].strip() IOError: [Errno 2] No such file or directory: './.osc/_package' wrong repo/arch?
osc can not find the file ./.osc/_package in your current working directory. Is it there? The file structure for osc looks like this: werner@werner-amd64:~/daten/packages/osc/science/octave> find . . ./.osc ./.osc/_meta ./.osc/_project ./.osc/octave-2.9.9.tar.bz2 ./.osc/_files ./.osc/_osclib_version ./.osc/octave.spec ./.osc/_package ./octave-2.9.9.tar.bz2 ./octave.spec Regards Werner --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Werner, thanks for your fast response! Op zaterdag 30 december 2006 10:12, schreef Werner Hoch:
osc can not find the file ./.osc/_package in your current working directory.
Is it there?
No, it isn't.
The file structure for osc looks like this: werner@werner-amd64:~/daten/packages/osc/science/octave> find . . ./.osc ./.osc/_meta ./.osc/_project ./.osc/octave-2.9.9.tar.bz2 ./.osc/_files ./.osc/_osclib_version ./.osc/octave.spec ./.osc/_package ./octave-2.9.9.tar.bz2 ./octave.spec
How is this created? Is it done manually? If so, what values should be stored where? -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sat, Dec 30, 2006 at 10:22:14AM +0100, Richard Bos wrote:
Werner,
thanks for your fast response!
Op zaterdag 30 december 2006 10:12, schreef Werner Hoch:
osc can not find the file ./.osc/_package in your current working directory.
Is it there?
No, it isn't.
The file structure for osc looks like this: werner@werner-amd64:~/daten/packages/osc/science/octave> find . . ./.osc ./.osc/_meta ./.osc/_project ./.osc/octave-2.9.9.tar.bz2 ./.osc/_files ./.osc/_osclib_version ./.osc/octave.spec ./.osc/_package ./octave-2.9.9.tar.bz2 ./octave.spec
How is this created? Is it done manually? If so, what values should be stored where?
One way to transform a directory into a "checkout" is osc init <prjname> <pacname> The other way is, of course, to actually do a checkout. Peter -- SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo: Research & Development A malevolent monster (not true?); Some mischief microbic; What makes someone phobic; The work one does not want to do. From: Chris Young (The Omnificent English Dictionary In Limerick Form)
On Sat, Dec 30, 2006 at 09:48:33AM +0100, Richard Bos wrote:
According to this email http://lists.opensuse.org/opensuse-buildservice/2006-09/msg00133.html it is possible to execute: $ osc build Fedora_Extras_5 i586 *spec
But when I try that I get: $ osc build Fedora_Extras_5 i586 /var/tmp/gramps/gramps.spec Getting buildinfo from server Traceback (most recent call last): File "/usr/bin/osc", line 7, in <module> commandline.main() File "/usr/lib/python2.5/site-packages/osc/commandline.py", line 1050, in main cmd(args) File "/usr/lib/python2.5/site-packages/osc/commandline.py", line 768, in buildinfo package = store_read_package(wd) File "/usr/lib/python2.5/site-packages/osc/core.py", line 1280, in store_read_package p = open(os.path.join(dir, store, '_package')).readlines()[0].strip() IOError: [Errno 2] No such file or directory: './.osc/_package' wrong repo/arch?
What is the error? Is the packagecachedir (/var/tmp/osbuild-packagecache) missing? Is the build-root missing (/var/tmp/build-root-%(repo)s-%(arch)s)? Is the repo not good, if not what is not good?
I have the packages on a DVD that came Januari 2007 issue of linuxformat. I execute osc in: /media/LXFDVD88A/Fedora/RPMS
Is this http://lists.opensuse.org/opensuse-buildservice/2006-09/msg00133.html information available on the opensuse wiki?
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.) Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Op zaterdag 30 december 2006 10:35, schreef u:
I have the packages on a DVD that came Januari 2007 issue of linuxformat. I execute osc in: /media/LXFDVD88A/Fedora/RPMS
Is this http://lists.opensuse.org/opensuse-buildservice/2006-09/msg00133.html information available on the opensuse wiki?
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.)
Aha :) Now that is clear. The information is in the 'osc help build' output, but that made it not clear to me. It currently states: "You need to call the command inside a package directory." Perhaps it can be extended, with your explanation? Like: "You need to call the command inside a package directory, which should be a buildsystem checkout. (Local modifications are fine.)" Is it possible to use 'osc build' for a repository that is not present yet? I currently get: $ osc build Fedora_Core_5 i586 gramps.spec Getting buildinfo from server Error: can't get 'https://api.opensuse.org/rpm/home:rbos/Fedora_Core_5/i586/gramps/buildinfo' HTTP Error 404: Not Found wrong repo/arch? I don't want to add Fedora_Core_5 (or 4 or 6 ;)) now on the BS, as I have to adjust all the other packages.... I first want to test the spec file locally... -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sat, Dec 30, 2006 at 10:52:36AM +0100, Richard Bos wrote:
Op zaterdag 30 december 2006 10:35, schreef u:
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.)
Aha :) Now that is clear.
The information is in the 'osc help build' output, but that made it not clear to me. It currently states: "You need to call the command inside a package directory." Perhaps it can be extended, with your explanation? Like: "You need to call the command inside a package directory, which should be a buildsystem checkout. (Local modifications are fine.)"
That makes sense, yes. I'll fix it.
Is it possible to use 'osc build' for a repository that is not present yet? I currently get:
In theory it is possible to build a package which does not exist in a project yet. In practice, osc doesn't know how to do that but I'll fix it in the future. Thanks, Peter -- SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo: Research & Development A malevolent monster (not true?); Some mischief microbic; What makes someone phobic; The work one does not want to do. From: Chris Young (The Omnificent English Dictionary In Limerick Form)
Op zaterdag 30 december 2006 10:35, schreef Marcus Meissner:
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.)
Is this intended output? Getting buildinfo from server /tmp/buildinfo.RBLgRp.xml Updating cache of required packages (openSUSE:10.2) bind-libs-9.3.2-47 10% |== | 88 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 21% |====== | 184 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 27% |======== | 240 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 50% |============== | 432 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 61% |================= | 528 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 72% |===================== | 624 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 84% |======================== | 728 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 95% |=========================== | 824 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 100% |=============================| 862 kB 00:02 I would expect the progress marker to stay at one line? -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sat, Dec 30, 2006 at 10:55:06AM +0100, Richard Bos wrote:
Op zaterdag 30 december 2006 10:35, schreef Marcus Meissner:
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.)
Is this intended output?
Getting buildinfo from server /tmp/buildinfo.RBLgRp.xml Updating cache of required packages (openSUSE:10.2) bind-libs-9.3.2-47 10% |== | 88 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 21% |====== | 184 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 27% |======== | 240 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 50% |============== | 432 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 61% |================= | 528 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 72% |===================== | 624 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 84% |======================== | 728 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 95% |=========================== | 824 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 100% |=============================| 862 kB 00:02
I would expect the progress marker to stay at one line?
Did you resize the window? Or type anything? Its harmless I guess. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Op zaterdag 30 december 2006 16:40, schreef Marcus Meissner:
I would expect the progress marker to stay at one line?
Did you resize the window? No.
Or type anything? Its harmless I guess. Sure.
-- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
* Marcus Meissner <meissner@suse.de> [2006-12-30 16:40]:
On Sat, Dec 30, 2006 at 10:55:06AM +0100, Richard Bos wrote:
Op zaterdag 30 december 2006 10:35, schreef Marcus Meissner:
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.)
Is this intended output?
Getting buildinfo from server /tmp/buildinfo.RBLgRp.xml Updating cache of required packages (openSUSE:10.2) bind-libs-9.3.2-47 10% |== | 88 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 21% |====== | 184 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 27% |======== | 240 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 50% |============== | 432 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 61% |================= | 528 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 72% |===================== | 624 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 84% |======================== | 728 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 95% |=========================== | 824 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 100% |=============================| 862 kB 00:02
I would expect the progress marker to stay at one line?
Did you resize the window? Or type anything? Its harmless I guess.
Same behaviour here. I'm using Terminal (same terminal widget as gnome-terminal) with TERM=xterm-256color if that matters. But for me that doesn't matter. ;) Regards, Bernhard
Bernhard Walle schreef:
* Marcus Meissner <meissner@suse.de> [2006-12-30 16:40]:
On Sat, Dec 30, 2006 at 10:55:06AM +0100, Richard Bos wrote:
Op zaterdag 30 december 2006 10:35, schreef Marcus Meissner:
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.)
Is this intended output?
Getting buildinfo from server /tmp/buildinfo.RBLgRp.xml Updating cache of required packages (openSUSE:10.2) bind-libs-9.3.2-47 10% |== | 88 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 21% |====== | 184 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 27% |======== | 240 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 50% |============== | 432 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 61% |================= | 528 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 72% |===================== | 624 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 84% |======================== | 728 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 95% |=========================== | 824 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 100% |=============================| 862 kB 00:02
I would expect the progress marker to stay at one line?
Did you resize the window? Or type anything? Its harmless I guess.
Same behaviour here. I'm using Terminal (same terminal widget as gnome-terminal) with TERM=xterm-256color if that matters. But for me that doesn't matter. ;)
Believe it or not, but you need to use a very very wide window. Much more than 80 characters wide, perhaps 160 characters. With such a wide window, the progress marker is just working fine. -- Richard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sat, Dec 30, 2006 at 07:42:28PM +0100, Bernhard Walle wrote:
* Marcus Meissner <meissner@suse.de> [2006-12-30 16:40]:
On Sat, Dec 30, 2006 at 10:55:06AM +0100, Richard Bos wrote:
Op zaterdag 30 december 2006 10:35, schreef Marcus Meissner:
You need to build in the current directory, which should be a buildsystem checkout. (Local modifications are fine.)
Is this intended output?
Getting buildinfo from server /tmp/buildinfo.RBLgRp.xml Updating cache of required packages (openSUSE:10.2) bind-libs-9.3.2-47 10% |== | 88 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 21% |====== | 184 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 27% |======== | 240 kB 00:02 (openSUSE:10.2) bind-libs-9.3.2-47 50% |============== | 432 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 61% |================= | 528 kB 00:01 (openSUSE:10.2) bind-libs-9.3.2-47 72% |===================== | 624 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 84% |======================== | 728 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 95% |=========================== | 824 kB 00:00 (openSUSE:10.2) bind-libs-9.3.2-47 100% |=============================| 862 kB 00:02
I would expect the progress marker to stay at one line?
Did you resize the window? Or type anything? Its harmless I guess.
Same behaviour here. I'm using Terminal (same terminal widget as gnome-terminal) with TERM=xterm-256color if that matters. But for me that doesn't matter. ;)
Interesting ;) I have tried different window widths when I implemented it, and I didn't notice it. Regards, Peter -- SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo: Research & Development A malevolent monster (not true?); Some mischief microbic; What makes someone phobic; The work one does not want to do. From: Chris Young (The Omnificent English Dictionary In Limerick Form)
participants (5)
-
Bernhard Walle -
Dr. Peter Poeml -
Marcus Meissner -
Richard Bos -
Werner Hoch