May 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] multiple sources in .deb?
by Isaac Hailperin 16 May '12

16 May '12

Hi, in rpms I can define multiple sources. For debs I could not find a way to do it. Is there a way? Isaac -- Isaac Hailperin Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-45 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] Mirroring base distributions to private OBS instance
by Andrzej Lisowski 16 May '12

16 May '12

Hi, I'm busy with piloting private OBS instance at our company. So far the results are promising and we received positive feedback from the first users. I have been requested though to make sure that our private OBS instance will be able to run independent from public one at https://build.opensuse.org/ I understood that in order to achieve that I need to mirror so called base distributions from https://build.opensuse.org/ I tried initially to mirror the RedHat:RHEL-6 and SUSE:SLE-11:SP2 to my local instance but unfortunately without success. I followed the instruction that is provided with OBS RPMs i.e. /usr/share/doc/packages/obs-server/README.SETUP and I tried to follow the WiKi http://en.opensuse.org/openSUSE:Build_Service_private_instance_boot_strappi… Unfortunately none of these procedures provided expected results. My basic problem is that the imported SLES and RHEL projects are not recognized by OBS backend after import those project using the obs_mirror_project command. I tried various tricks like for example restarting OBS scheduler or rescanning repository using command /usr/lib/obs/server/bs_admin --rescan-repository $PROJECT $REPO $ARCH but without any luck. I can see that SLES and RH RPM packages are properly imported to the /srv/obs/build directory and the project files the xml and conf files appear in the /srv/obs/projects. They don't appear in the mySQL DB though as other projects that are created manually. The base distributions do not appear in my private instance in the list of the projects in a way as you can see it on the public OBS instance either. I received advice that I should run /srv/www/obs/api/script/import to finalize the import but I was not able to find any further information about how to apply this command. I would appreciate if someone could please provide me with hints on how can I mirror the base distribution from the public OBS instance to our private one. I'm running OBS 2.3 RC on top of SLES 11 SP2 64 bit. Thanks in advance, Andrzej.-- 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] Avoiding the rpm signing warnings for Fedora
by Frank Lichtenheld 16 May '12

16 May '12

Hi. All builds against Fedora_16 on OBS currently throw a lot of warnings during chroot setup due to missing key for checking the package signatures. This does not seem to cause any problems but it irritated me (since it makes this part of the log very hard to read) and so I did investigate how this happens. The problem is as follows: - "build" usually uses --nosignature - But it wants to do so only for rpm v4, not v3 (probably v3 didn't have the option?) - It checks the rpm version not by checking the rpm version but by checking for the existence of the program "rpmsign" in the chroot - In Fedora (at least 15 and 16, i.e. the OBS-supported versions) the program "rpmsign" is not in the "rpm" rpm, but in the "rpm-sign" rpm - The "rpm-sign" rpm is not installed by the current Fedora:16 project config Possible solutions: 1) add "Preinstall: rpm-sign", "Required: rpm-sign" to Fedora:16 project config (I tested it and it indeed does avoid the warnings) 2) just remove the check from "build", does anyone still use ancient rpm? 3) change the check to something that doesn't require the presence of the rpmsign binary 1 is clearly the easy way out, but if you would prefer 2 or 3 I would be happy to make a patch for build. Gruesse, -- Frank Lichtenheld Lead Engineer email: frank.lichtenheld(a)sophos.com tel: +49 721 25516-362 cell: +49 174 1748211 SOPHOS You're safer in our world Unified | Web | Email | Endpoint | Mobile | Network | Data -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] configure logrotate - best practice
by Isaac Hailperin 16 May '12

16 May '12

Hi, I am building a package that needs to configure logrotate. Now two possiblities come to my mind: a) Put /etc/logrotate.d/mypackage in the rpm and install it just like any other file from the package b) Create /etc/logrotate.d/mypackage with a postinstall script I was wondering which way is the "best" or most common way to do things like this for rpms. But also in the light of the build service, where I want to create rpms and debs alike. Best, Isaac -- Isaac Hailperin Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-45 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] Translated descriptions of packages on software.opensuse.org
by Andrey Gankov 16 May '12

16 May '12

Hi, Please tell, are you have any plans to implement display translated package descriptions for the new software.opensuse.org I think that descriptions in native language would be a very demand feature for non-English speaking users. We have a lot of translations into Russian. Probably translations into other languages, too, is enough. Thanks. -- Andrey Gankov openSUSE Member Email:gankov@opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 14

[opensuse-buildservice] Old repo policy?
by Joop Boonen 16 May '12

16 May '12

Hi All, I wonder what the policy is related to outdated repos? I see for example that packages are still being build for openSUSE 11.3 < in for instance project server:mail, Application:Geo and probably quite few more. Should this be like this, isn't this a waste of resources? Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] 2.1 -> 2.3 upgrade problem
by Troy Telford 15 May '12

15 May '12

I've had a system in production for a few years now; I've upgraded from 2.1 -> 2.3, and have the following problem, and I figure I need to fix it to continue. (--trace added to increase verbosity) As a result, my OBS system is now down, and I kinda need to get it going again quickly: Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html # RAILS_ENV="production" rake db:migrate --trace (in /srv/www/obs/api) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == AddIndexForAttributes: migrating ========================================== -- add_index(:attrib_types, [:attrib_namespace_id, :name], {:unique=>true}) rake aborted! An error has occurred, all later migrations canceled: Mysql::Error: Duplicate entry '1-RequestCloned' for key 'index_attrib_types_on_attrib_namespace_id_and_name': CREATE UNIQUE INDEX `index_attrib_types_on_attrib_namespace_id_and_name` ON `attrib_types` (`attrib_namespace_id`, `name`) /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/abstract_adapter.rb:227:in `log' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/mysql_adapter.rb:324:in `execute' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/abstract/schema_statements.rb:292:in `add_index' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:352:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:352:in `method_missing' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:348:in `method_missing' ./db/migrate//20120223105426_add_index_for_attributes.rb:4:in `up_without_benchmarks' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:282:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:365:in `__send__' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:365:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:491:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:567:in `call' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:567:in `ddl_transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:490:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:477:in `each' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:477:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:401:in `up' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:383:in `migrate' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.14/lib/tasks/databases.rake:112 /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib64/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 -- Troy Telford -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Project request
by Schlomo Schapiro 15 May '12

15 May '12

Hi, I need a project work space and submitted a bug for this: https://bugzilla.novell.com/show_bug.cgi?id=761640 When can we expect any action on this? We really would like to meet the LinuxTag next week with our "new" package build space for the Relax and Recover project. It would be really great if this would work out. Thanks a lot, Schlomo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] To %make_install or to %makeinstall (spec-cleaner)
by Joop Boonen 15 May '12

15 May '12

Hi all, I have been using spec cleaner for while. What I notice it that it uses macro %make_install instead of %makeinstall. Both macros are OK for openSUSE but the first one breaks the build for SLE. <quote> + %make_install /var/tmp/rpm-tmp.59594: line 45: fg: no job control </quote> I wonder if this should be fixed, in either spec-cleaner (use%makeinstall in stead of %make_install) or in the buildserver (add macro %make_install for SLE)? Regards, Joop. See also: https://bugzilla.novell.com/show_bug.cgi?id=712171 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 11

[opensuse-buildservice] Solution for compiling kernel modules for openSUSE:Tumbleweed (and Kernel:stable)
by Paolo Pantò 13 May '12

13 May '12

Originally posted in http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/47452… Hi, I don't know if this is the right place to post. The "problem" concerns various scopes - Tumbleweed - Kernel(:stable) - Open Build Service (OBS) Currently it is not possible to compile kernel modules for openSUSE:Tumbleweed (and Kernel:stable) for the i586 arch on OBS. Have a look eg. at - https://build.opensuse.org/project/show?project=multimedia%3Aaudio%3AKMP - https://build.opensuse.org/project/show?project=Virtualization%3AVirtualBox… For now the entry for i586 reads "unresolvable": nothing provides kernel-desktop-devel = 3.3.2-20 needed by kernel-syms, nothing provides kernel-pae-devel = 3.3.2-20 needed by kernel-syms, nothing provides kernel-xen-devel = 3.3.2-20 needed by kernel-syms The reason is that the project configs for openSUSE:11.4/standard, on which Kernel:stable depends, and openSUSE:12.1/standard, on which openSUSE:Tumbleweed depends, includes the line ExportFilter: \.i686\.rpm$ i686 New kernels are built with "BuildArch: i686" on %ix86, the ExportFilter config makes it impossible for other packages to find the proper devel-packages - kernel-default is still build for i586. I've created a sample environment on OBS with - https://build.opensuse.org/project/show?project=home%3Amunix9%3AKernel%3A11… - https://build.opensuse.org/project/show?project=home%3Amunix9%3AKernel%3ATu… This projects aggregates the problematic packages and contains the project config line ExportFilter: \.i686\.rpm$ i586 Now kernel modules are built fine, eg. for virtualbox https://build.opensuse.org/project/monitor?project=home%3Amunix9%3AVirtuali… On openSUSE:Factory (on which eg. Kernel:HEAD depends) it works already fine, because the appropriate line "ExportFilter: \.i686\.rpm$ i686" is missing. If I'm right, then a global solution would make sense, to allow also other projects to build proper kernel modules. Ciao, Paolo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4