OBS Light project deliverable which are available are listed on this page. Publication of the information will follow the progress of the implementation (yes, we do publish early draft versions, using them is at your risk)
A command line version of any individual feature will generally precede its implementation as an OSC plugin (when applicable) and creation of a UI will come last. Please note that once a command will have been published as an osc plugin the stand alone command will be deprecated.
Packaged versions of the OBS Light client (still in development) are available for OpenSUSE, MeeGo, Debian and Ubuntu.
The repository is here. To install:
zypper ar http://repo.pub.meego.com/home:/ronan:/OBS_Light/openSUSE_11.4/home:ronan:OBS_Light.repo zypper --gpg-auto-import-keys ref zypper in obslight-base
The repository is here. Add these lines to your /etc/apt/sources.list file (or to a new file /etc/apt/sources.list.d/obslight):
deb http://repo.pub.meego.com/home:/ronan:/OBS_Light/Ubuntu_11.04/ ./ deb http://download.opensuse.org/repositories/openSUSE:/Tools/xUbuntu_11.04 ./
Refresh the APT database and install OBS Light:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/xUbuntu_11.04/Release.key -O - | sudo apt-key add - sudo apt-get update sudo apt-get install obslight build
Add yourself to the users group:
sudo usermod -a -G users `whoami`
[Not tested] The repository is here.
[Not tested] The repository is here.
Note: the obslight package has a dependency to PySide, which is neither included in Debian stable nor in Debian testing. So you will need Debian unstable if you want to test.
To get a brief overview of all available commands, just type:
This message appears when adding packages in ARM chroot. It may come from a broken version of zypper/libzypp in your chroot, which do not see noarch packages. This problem was reported with zypper 1.5.3 and libzypp 8.12.1. We suggest you to update your zypper version to 1.6+. For convenience, we pre-built zypper 1.6.15 and libzypp 9.10.2 to Meego 1.2.0.
First add our repository to your chroot's zypper configuration file:
obslight addRepoInChRoot --projectLocalName $ProjectName --url http://repo.pub.meego.com/home:/fvennetier:/zypper-backport/MeeGo_1.2.0_standard/ --alias "Zypper_1.6.15_backport"
Then go to the chroot and update zypper:
obslight goToChRoot --projectLocalName $ProjectName # zypper update zypper # exit
The build package of your chroot does not support armv8el builds. Consider using another version, like the 2011.03.29 of MeeGo repositories.
First add the MeeGo building tools repository to your chroot's zypper configuration file:
obslight addRepoInChRoot --projectLocalName $ProjectName --url http://download.meego.com/live/Tools:/Building/MeeGo_1.2.0/ --alias "Tools:Building_MeeGo_1.2.0"
Then go to the chroot and update build:
obslight goToChRoot --projectLocalName $ProjectName # zypper update build # exit
This appears when binfmt_misc is not or badly configured. Launch qemu's binfmt configuration script (as root):
If you still get the same message, try this (as root):
echo -1 > /proc/sys/fs/binfmt_misc/arm echo ":arm:M::\x7fELF\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:`which qemu-arm`:" > /proc/sys/fs/binfmt_misc/register
This error appears on Ubuntu when running obslight from a console, without a graphical environment. At the moment, the only known solution is to run obslight only from a graphical environment (e.g. Gnome).
One of the problem that any user of a private OBS will quickly face, is the need to tag specific version of a project and allow the copy of the project from an OBS to an other OBS or from one project to an other project.
More details on obstag and obs2obscopy can be found here