The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Contribution in detail
(New page: = Local build of current version = Need prerequisites for osc and build == Branch the package to work on it == osc -A https://obs:444/ branch Mer.org:Core:i586 systemd A bug in the OB...)
Revision as of 19:12, 10 November 2011
Local build of current version
Need prerequisites for osc and build
Branch the package to work on it
osc -A https://obs:444/ branch Mer.org:Core:i586 systemd
A bug in the OBS means that the new branch project will not have the correct repos so add them manually
<repository name="Mer_Core_i586"> <path repository="Core_i586" project="Mer.org:Core:i586"/> <arch>i586</arch> </repository>
The repository needs to be set to publish too.
osc -A https://obs:444 co home:Admin:branches:Mer.org:Core:i586/systemd cd home:Admin:branches:Mer.org:Core:i586/systemd osc build i586
Pull the latest Mer version and .git
Clone the mer git repo too:
cd home:Admin:branches:Mer.org:Core:i586 git clone ssh://firstname.lastname@example.org:29418/mer-ore/systemd tmp mv tmp/.git systemd/ rm -rf tmp cd systemd git status
You can now edit the code and packaging.
Of course you'll need to do one or more builds to verify the code.
osc ar osc ci osc chroot osc build
Use a suitable .ks
IMG supports a feature called "Extra repositories and packages" This allows you to use a standard kickstart and add a specific repository to use for overrides.
Select the OBS and enter the repository/repo eg:
Build a suitable image, install and test
DEVICE=/dev/sdh curl http://imgw1/images/web/root/1-20111110-090037/meego-nemo-trial-126.96.36.19911110.1000.iso | sudo dd of=$DEVICE bs=4M oflag=direct && sudo eject $DEVICE
Package SOMETHING.rpm is damaged:
This means a checksum mismatch was seen and the package was re-downloaded.
Push for review
In the obs/mer build directory:
cd home:Admin:branches:Mer.org:Core:i586 git commit -s --amend git push origin HEAD:refs/for/master