The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Search results
From Mer Wiki
Create the page "Obs" on this wiki!
- * C is a number which is incremented by OBS If you build the package outside of the OBS or if you copy a package then you will of course not get the correct C or B35 KB (5,469 words) - 23:20, 13 June 2013
- ...t. The approach is not in any way Mer-specific and can be applied to other OBS-using distributions. This will only work with SB2 2.3_development branch == What does SB2-OBS do differently than the old approach ==13 KB (2,027 words) - 11:51, 22 October 2014
- I'm thinking of a split of Mer into two OBS projects.1 KB (206 words) - 20:08, 16 December 2011
- ===Patterns and OBS=== 23:12 < sledges> faenil: an OBS admin points special script to a repo which has package providing patterns.28 KB (4,317 words) - 20:33, 10 June 2014
- * Mer OBS development https://api.merproject.org Mer Community OBS16 KB (2,476 words) - 20:41, 24 June 2016
- == Building for different targets in OBS == * inter-OBS link provided by build.opensuse.org5 KB (699 words) - 14:12, 18 January 2012
- ...implified guide you will need an account on the [[:Category:cobs|Community OBS]] ...s setup properly, create a home project for the adaptation in the selected OBS. Check the [[OBS_architecture_naming]] for the repository naming. Below is14 KB (2,171 words) - 16:51, 27 June 2013
- * OBS project location (eg Mer:Tools etc) * They should be one or two words : ":Category:community obs"3 KB (477 words) - 15:30, 21 January 2012
- ...es file to the end of the .spec. (So, if you're building packages without OBS/osc, then you will need to do this manually.)14 KB (1,828 words) - 17:44, 10 August 2013
- ...OBS] same account as bugzilla below, https://wiki.merproject.org/wiki/Nemo/OBS#Getting_started_with_the_build_system #* Third option is let OBS build the package. (In practice in this point ignoring if the fix works and5 KB (817 words) - 19:47, 11 February 2014
- This area essentially describes the core. It contains configuration for the OBS and other build tools used to build Mer. This includes: * OBS prjconfig2 KB (258 words) - 13:11, 3 April 2013
- ....g., Maliit (VKB) or resource policy management. See list of packages from OBS: https://build.pub.meego.com/project/packages?project=CE%3AMW%3AShared4 KB (639 words) - 16:13, 27 July 2012
- ...d_xforward and rubygem-passenger to be built against the apache in the Mer OBS project osc -A suse copypac openSUSE:Tools apache2 -t cobs Mer:OBS:Testing:Devel -m "initial import"3 KB (403 words) - 21:18, 4 April 2012
- ...y changing, these repositories are available at http://repo.merproject.org/obs/nemo:/.5 KB (766 words) - 00:50, 24 January 2014
- ...d to '''devel'''. This is done by editing ''mer:devel'' project in the Mer OBS, e.g., ...ocess is similar to '''devel''', i.e., edit ''mer:testing'' project in Mer OBS. Addition thing with ''testing'' level is that one needs also update the re8 KB (1,149 words) - 21:44, 4 February 2014
- == Creating an SB2 Target for any (non-x86) Mer OBS package (draft) == When SB2 is enabled on the OBS (as it is in the MeeGo public OBS) then it also creates a suitable SB2 'target'.15 KB (2,448 words) - 11:35, 23 May 2014
- ...rm SDK needs to be able to function without an OBS account or access to an OBS.2 KB (290 words) - 09:38, 29 July 2012
- ...mer-meeting.2012-05-24-12.00.html Meeting minutes 2012-05-24, QA tools and OBS]5 KB (603 words) - 12:38, 8 October 2012
- # '''Input''': BOSS delivers the changed package to OBS and OBS builds the package for all architectures. '''Output''': The build result # '''Input''': Update changed packages to vendor OBS. '''Output''': Repository where to find the packages3 KB (517 words) - 16:34, 6 May 2012
- #REDIRECT [[Building against Mer in Community OBS]]51 B (7 words) - 15:49, 24 April 2012
