June 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Installing an obsserver as an appliance in Amazon Cloud service
by Dominig ar Foll (Intel OTC) 28 Jun '12

28 Jun '12

Hello, following a long thread of debug with Tim, I am pleased to give here a short HowTo for those who would like to create an OBS server in the cloud. Having an OBS in the cloud can be an interesting model to get a large server for validation and test without the initial investment or to provide a scalable service. I let you do your math and do not take this email as an advise to use or not use the service. I have used the appliance provided by the obslight project and made my test with Amazon EC2 cloud service Create an acount on Amazon cloud service. https://console.aws.amazon.com Login and select EC2 "Virtual Server in the Cloud" In "My Ressources" (first time only) Create a new pair of key and save it in your local drive (will be needed later to connect as root). Prepare your AWS credential https://aws-portal.amazon.com/gp/aws/securityCredentials (first time only) Get the OBS appliance http://susestudio.com/a/e0uuBG/meego-obs (note this process is valid from the version 1.0.48) Select the Type "Cloud" Select "upload to EC2" Add your credential to SUSE Studio (first time only) UN-select the "Automatic Launch option" (if you forget that you will just have to terminate the instance started by SUSE) Click on "Upload to Amazon" Return to AWS Management Console -> EC2 Select Network-Security -> Security Groups Create a new security Group called observer in "InBound" Tabulation add two rules for the ports 82 and 444 with Source 0.0.0.0/0 (Note in production, your rules will need to be smarter) Select Images -> AMIs you see an image called ....MeeGo_OBS..... Select it with a click Right Click to access contextual menu -> Launch Instance Instance Type -> change to Medium (m1.medium) or higher Click "Continue", 3 times until 'Create KeyPairs' Select the Key pair that you have saved previously Click "Continue" to 'Configure Firewall' Select all the available rules Click "Continue" to 'Review' Click Launch Select Instance -> Instances Your instance is running. Once that 'status checks' is green (running green is not enough) Connect with ssh on your instance. the name is something like ec2-xxx-xxx-xx-xxx.compute-n.amazonaws.com add an entry for obslightserver in /etc/hosts on your local PC (mandatory) IP address is the number in the appliance host name. use ssh -i path-to-you-key.pem root(a)ec2-xxx-xxx-xx-xxx.compute-n.amazonaws.com Increase the HDD size which by default is only 10GB. resize2fs /dev/sda1 50G Correct the obsworker mode of operation to select chroot vi /etc/sysconfig/obs-server change OBS_VM_TYPE = "none" rcobsworker stop rcobsworker start Your OBS appliance is ready. Note that its name and IP address will change each time that you stop it by default. Remember the entry in /etc/host You can now connect to the appliance from your PC with https://obslightserver You can follow the process to add Tizen IVI 1.0 in your new private OBS, as Fake OBS is already installed you you can jump the first phases. https://lists.tizen.org/pipermail/ivi/2012-May/000038.html Enjoy. -- Dominig ar Foll Senior Software Architect Open Source Technology Centre Intel SSG -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

Re: [opensuse-buildservice] debbuild for building LSB debian packages with RPM spec files on OBS?
by Michael Schroeder 28 Jun '12

28 Jun '12

On Mon, Jun 25, 2012 at 08:15:11PM -0500, Conan Kudo (?$B%K!<%k!&%4%s%Q) wrote: > Have you done any tests to see if debbuild support can be integrated > into OBS yet? Well, I did a couple of commits in the master branch to move it in the right direction. To be specific, we now allow a "Binarytype" directive in the project config to configure the type of the binaries (rpm/deb) independent of the type of the sources (spec/dsc). So you would use Type: spec Binarytype: deb in the build config of your project. What's still missing is support for "debbuild" in the build script, i.e. it should call debbuild instead of rmbuild if the binarytype is set to "deb". OBS itself doesn't need to be changed for that, we need to support this in the "build" package. Also note that build.opensuse.org currently runs the 2.3 branch, so "Binarytype" is not yet available. We'll change to master this week, though. Cheers. Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] OBS password quality
by Cristian Rodríguez 27 Jun '12

27 Jun '12

Hi: It is impossible to use a high quality password in the opensuse.org buildservice instance, for some reason the brillant policies disallow special characters allowing only letters and numbers, hence significantly reducing the possible password entropy. Can something be done about this ? also is it possible to use a different method such as a cryptographic key ? Cheers. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Hermes configuration
by Cristian Morales Vega 27 Jun '12

27 Jun '12

How should I configure my hermes account if I want to be notified of: - Source changes made by somebody else in packages where I am the maintainer or bugowner - Metadata changes made by somebody else in packages where I am the maintainer or bugowner - New packages created by somebody else in projects where I am the maintainer or bugowner - Packages deleted by somebody else in projects where I am the maintainer or bugowner - Metadata changes made by somebody else in projects where I am the maintainer or bugowner ? The expert interface is really confusing. Parameters "rm" and "_type"? Thanks. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] [PATCH] run build under uid 0 when userootforbuild is used
by Michal Vyskocil 27 Jun '12

27 Jun '12

osc --userootforbuild setup the --build_uid to 0:0. When both specified, --userootforbuild has bigger priority. --- osc/build.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/osc/build.py b/osc/build.py index 9f97063..6879a2e 100644 --- a/osc/build.py +++ b/osc/build.py @@ -442,6 +442,8 @@ def main(apiurl, opts, argv): build_uid = config['build-uid'] if opts.build_uid: build_uid = opts.build_uid + if opts.userootforbuild: + build_uid='0:0' if build_uid: buildidre = re.compile('^[0-9]{1,5}:[0-9]{1,5}$') if build_uid == 'caller': -- 1.7.10.4 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] Using OBS appliance 2.3.1 out of the box ==> Tweaking requirement
by JAFFREZIC Xavier 27 Jun '12

27 Jun '12

Hi OBS newbies users … (hope also some useful commentaries from guru if needed) Starting an OBS appliance in Virtual Machine for MeeGo building is quite easy with the knowledge of few tricks Lot of usefull information could be found on http://en.opensuse.org/openSUSE:Build_Service_private_installation NB: some of them are replicated here (apologize for copying ...) I've been using virtualbox 4.12 for this using xubuntu 11.10 as host OS ... Supposing that downloading, uncompressing and basic use of virtualbox is known ... → Setting a new Virtual machine : - Attach the VMDK appliance to virtual machine - Attach secondary VDI drive (fixed size of at least 30Gb) ==> this will be for OBS storage data [LVM] - Depending on your Host capabilities (less than 6Gb of Memory) you may need to attach a third VDI drive of 10Gb for workers. → Boot the virtual machine and login Secondary drive (OBS storage) should be is seen as /dev/sdb Third drive (if attached) should be seen as /dev/sdc Start the ssh server (on boot and now) because I found that use of the virtual box console is a bit uncomfortable !! >>insserv sshd >>sshd start ********************************************************************************* ⇒ From this point you may log from another host using ssh ... ********************************************************************************* → Stop the all of OBS server process : - find /etc/init.d -name obs\* -exec {} stop \; - rcmysql stop → Configure the secondary drive (OBS storage) as LVM (/dev/OBS/server) : >> fdisk /dev/sdb (create a new primary partition with type 8e). >> pvcreate /dev/sdb1 >> vgcreate "OBS" /dev/sdb1 >> lvcreate --extents 100%VG -n "server" OBS >> mkfs.ext4 /dev/OBS/server → Clean previously created files during appliance initialization >> rm –Rf /srv/obs/* >> rm -Rf /var/cache/obs/worker This will save some space because appliance has only 300Mb space left on the rootfs and this space is temporarily used will importing package from other OBS server using the "osc copypac". For example, the QT package is about 200 Mb ... and if there is less disk space then your package size on the rootfs, the copypac command will fail. → Configure disk space for workers ... Option A : if your host can allocate at least 5Gb for a ramdisk you need to add the following line in /etc/fstab tmpfs /var/cache/obs/worker tmpfs defaults,size=5G,mode=777 0 0 Option B: your host as not so much memory then you need to use the third drive >> fdisk /dev/sdc (create a new primary partition with type 83). >> mkfs.ext4 /dev/sdc1 → You may be are behind a firewall so you need to set some proxy. There are to settings on OBS. One is to allow OpenSuse to access world and the setting are located in /etc/sysconfig/proxy Second is to allow OBS to access world and is located in /usr/lib/obs/server/BSConfig → Adapt the type of architecture to you want to build : settings are located in /etc/sysconfig/obs-server → There is still a small bug on the OBS 2.3.1 for published binaries web access The file to correct is /etc/apache2/vhosts.d/obs.conf In the "# Build Results" section you have to replace "/srv/obs/repos" by "/obs/repos" making ********************************************************************************* ⇒ At this point your Appliance is almost ready : just need to reboot in order to activate properly all attached drives and let OBS reinstall the webUI and the database ********************************************************************************* If you have plan to build package for non Intel architecture there are some additional tweaking. OBS is capable for building other architectures out of the box, but it is not fully ready for this. You will need to inform the linux kernel that the it will have to support other architectures. For this you need to run a script : /usr/sbin/qemu-binfmt-conf.sh But it is not part of the original appliance packages... It belong to the qemu-linux-user package so you need to install this package ... >> zypper addrepo http://download.opensuse.org/repositories/Virtualization/openSUSE_12.1/Virt… >> zypper refresh >> zypper install qemu-linux-user Copy the script to the root directory >> cp /usr/sbin/qemu-binfmt-conf.sh . The package is not need anymore on OBS ... so to save place (about 90Mb) remove it >> zypper remove qemu-linux-user Stop all Workers, run the script, then restart the Workers ... >> rcobsworker stop >> ./ qemu-binfmt-conf.sh >> rcobsworker start These last 3 commands will be required each time you restart the appliance (with workers in a ramdisk for my settings)... It may be not necessary if workers are in a attached third drive ... **** From now you will have to import your build target (not covered in this mail) If the project config is based taken from old OBS version, it may need some tweaking to match last OBS building settings for non Intel architecture ... Take a look to openSUSE:Factory:ARM project config to see the required adaptation **** Regards Xavier -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system.

1 0

[opensuse-buildservice] [gsoc] osc2 client - summary of week 5
by Marcus Hüwe 26 Jun '12

26 Jun '12

Hi, here's a small summary of the 5th (coding) week. Last week I spent most of my time with working on the cpio module. Finally I ended up with a complete rewrite of osc's "old" cpio module. The cpio implementation details are taken from the cpio 2.11 package. Currently only the "new ascii" format is supported and we can only handle regular files (this is sufficient for our needs). Here's a small example how to use it: # cpio_open is just a convenience method for CpioArchive(filename=fname) with cpio_open(fname) as archive: for archive_file in archive: # print filename print archive_file.hdr.name # print contents print archive_file.read() It's also possible to pass a file-like object to a CpioArchive instance (in this case we do not need to use the with statement). Also it can be "easily" enhanced to support different cpio formats (one just have to write the specific ArchiveReader and ArchiveWriter classes:) ). The code is available at [1] and the testcases at [2]. Todo for this week: * finish the build module * start with working on the package fetching code Marcus [1] https://github.com/openSUSE/osc2/blob/master/osc/util/cpio.py [2] https://github.com/openSUSE/osc2/blob/master/test/util/test_cpio.py -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Building with osc/kvm - failing for me...
by Malcolm 25 Jun '12

25 Jun '12

Hi I've enabled qemu-kvm and it's working fine for running an iso image as my user. I've configured my ~/.oscrc for the three options: build-device, build-swap and build-memory, however when testing I get the following; http://paste.opensuse.org/72274785 I'm on SLED 11 SP2, with osc version 0.134.1. Is there something I'm missing? -- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.31-0.9-default up 1:11, 4 users, load average: 0.69, 0.73, 0.68 CPU Intel i5 CPU M520(a)2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Rename project and branching
by He Zhenxing 25 Jun '12

25 Jun '12

Hi, OBS does not provide a way to rename a project, so I'd like to know if there is a way (manually or with some tools) to rename a project. And also the are branched packages or parent packages of branched packages in other projects. I'd like to keep the branching relationship after the renaming of the project. Any help would be appreciated! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] unresolvable errors while building packages for RHEL_6
by S. Nandhini 22 Jun '12

22 Jun '12

Hi, How can the unresolvable errors be fixed? When I try building lvm rpm for RHEL_6 (x86_64) it reports the following error Nothing provides corosynclib-devel >= 1.2.0-1, openaislib-devel >= 1.1.1-1, clusterlib-devel >= 3.0.6-1 Similarly for unixODBC rpm on RHEL_6 x86_64 I get the following error. Nothing provides libtool-ltdl-devel Is there a way to add customized repository for individual projects? Thanks in advance. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 7