Re: [MeeGo-dev] Adding Repo to OBS
So... I thought I understood what repo actually went to what path (ie: MeeGo.Com seems to go to the build.meego.com) but now I know I don't get it. I have added a repo called Meego:Trunk/standard, which I thought actually was download.meego.com/live/trunk/standard. It's not... Using a .ks that identifies the afore mentioned directory, I am getting some slightly different packages availability (gpsd 2.96 in the one I linked to 2.37 for the Meego:Trunk/standard). So back to the original question, how do I tell what path matches the repo listed on the pub OBS. BTW, a repo added from MeeGo.com won't be built against. Even though I can branch packages off of it. Nasa - Original Message - On 08/12/2011 06:44 AM, Nasa wrote: - Original Message - The one thing that I am still confused on... When I add a repository I assume I am building against a list of packages included in said repo. But I don't see a way to see what packages are actually included in the repo I may have just added. I think the best way is to check the repository link of said project. Regards, ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
On Sun, Aug 14, 2011 at 9:29 PM, Nasa nas...@comcast.net wrote: So, I continued to try and get this to work... I came across somethings - build.meego.com == MeeGo.com:xxx (for trunk it's MeeGo.com:Trunk). Wow, interesting, I didn't know that. So anything that ends up in the build repos can be used to build against? That is cool but I wish it were documented somewhere. The field wants to give you other options -- I ignored that and kept with what I entered, for 1.2oss I put in MeeGo.com:1.2oss I still didn't see anything related to 1.2.0.90 (is it actually being worked on?). Looking at the official OBS, you can see a lot of projects -- their names don't clearly identify what they are for (what's the difference between 1.2oss and 1.2.0oss, and they are different). The paths for these projects repo is http://download.meego.com/live/MeeGo:/, may vary depending on project. This gives an insight on what files versions a particular project is working with. The single problem I am still working on is building my project against one of those repositories. The repository screen (for the project) shows it listed, but none of my packages show it at all. Guess I'll keep looking... The versioning scheme for MeeGo has become very confusing, I agree. Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
- Original Message - On Sun, Aug 14, 2011 at 9:29 PM, Nasa nas...@comcast.net wrote: So, I continued to try and get this to work... I came across somethings - build.meego.com == MeeGo.com:xxx (for trunk it's MeeGo.com:Trunk). Wow, interesting, I didn't know that. So anything that ends up in the build repos can be used to build against? That is cool but I wish it were documented somewhere. While this appears to be the case, I haven't gotten it to work yet. If you look here https://build.pub.meego.com/project/repositories?project=home%3Anasa you'll see 2 repos, the 2nd one linking to build.meego.com. However, look here: https://build.pub.meego.com/package/show?package=NAVIT-svnproject=home%3Anasa which is the package page for my repacking the svn version of navit, you'll see the it only builds against the 1st one. Still looking to see if I missed something. Nasa The field wants to give you other options -- I ignored that and kept with what I entered, for 1.2oss I put in MeeGo.com:1.2oss I still didn't see anything related to 1.2.0.90 (is it actually being worked on?). Looking at the official OBS, you can see a lot of projects -- their names don't clearly identify what they are for (what's the difference between 1.2oss and 1.2.0oss, and they are different). The paths for these projects repo is http://download.meego.com/live/MeeGo:/, may vary depending on project. This gives an insight on what files versions a particular project is working with. The single problem I am still working on is building my project against one of those repositories. The repository screen (for the project) shows it listed, but none of my packages show it at all. Guess I'll keep looking... The versioning scheme for MeeGo has become very confusing, I agree. Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
On 08/12/2011 06:44 AM, Nasa wrote: - Original Message - The one thing that I am still confused on... When I add a repository I assume I am building against a list of packages included in said repo. But I don't see a way to see what packages are actually included in the repo I may have just added. I think the best way is to check the repository link of said project. Regards, ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
So, I continued to try and get this to work... I came across somethings - build.meego.com == MeeGo.com:xxx (for trunk it's MeeGo.com:Trunk). The field wants to give you other options -- I ignored that and kept with what I entered, for 1.2oss I put in MeeGo.com:1.2oss I still didn't see anything related to 1.2.0.90 (is it actually being worked on?). Looking at the official OBS, you can see a lot of projects -- their names don't clearly identify what they are for (what's the difference between 1.2oss and 1.2.0oss, and they are different). The paths for these projects repo is http://download.meego.com/live/MeeGo:/, may vary depending on project. This gives an insight on what files versions a particular project is working with. The single problem I am still working on is building my project against one of those repositories. The repository screen (for the project) shows it listed, but none of my packages show it at all. Guess I'll keep looking... Nasa - Original Message - [sorry, i am a new subscriber joining a current conversation that is the exact problem i see] --snip-- You should be able to add various repos in the advanced tab on that same page, where it says: Or pick one via advanced interface. There are a lot of distros to build against, I haven't seen the one you're after but I didn't go through the whole list. It isn't obvious, but that form is partial an auto-complete form. So start typing in the project field until you find the repo you want to build against. Thanks Jeremiah, I was putting in the name of my project in that field instead of other projects. Once I did things like meego a whole lot more options showed up... However, I didn't see anything related to 1.2.0.90 and/or 1.3. It looks like this field is only pulling from projects listed on pub OBS - not the build one. Is there a way to cross connect the two? Good question. I don't know the answer. I know that one can upload an entire distro and load that into the OBS to build against, you'll likely need special permissions to do that on the official OBS though I'm not sure. At this point, I think we need to get some more info on; 1. The nature and purpose of the various 1.2 point releases 2. How to configure these to build against in the MeeGo OBS --snip-- +1 on confusion on how to (read-only) link to core repo pkg from pub obs from the build.pub.meego.com side, all the build.meego.com repos appear empty? (to me, a new user with only community obs account). if i try build service - projects - (select MeeGo:Trunk) while logged in,i see: MeeGo Trunk Import of MeeGo trunk Information: This project does not have any packages yet. maybe this is a temporary breakage? the tutorial http://wiki.meego.com/Build_Infrastructure/Packagers_Developers/WebUI_part_2 (for a build.meego.com user) shows that obs should support linking to a package. all the other build repos i checked look the same from the pub side. --snip-- The one thing that I am still confused on... When I add a repository I assume I am building against a list of packages included in said repo. But I don't see a way to see what packages are actually included in the repo I may have just added. That is a very good question. To peer into the repo I think you'll have to go to the separate repo URL. I am not sure if there is a way to introspect the entire package list of one of those repos from the OBS though that sounds like a very good feature. --snip-- yes, you can try http://build.meego.com/project/show?project=Trunk or similar. it looks the way it probably is supposed to look if viewing it inside pub repo worked: MeeGo Trunk The Main development tree and core components There are 64 problematic packages of 1408 total (and you can browse all 64 / 1408 pkgs) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
On Fri, Aug 12, 2011 at 2:32 AM, Nasa nas...@comcast.net wrote: Rudi Thanks Rudi, I will have to take a read. I obviously didn't explain what I was after very well. On the https://build.pub.meego.com/project/add_repository_from_default_list?project=home%3Anasa page there a list of repositories one can add (such as Meego 1.1, 1.2, debian, etc), however, there isn't one for some of the development tracks. For my interest, 1.2.0.90 (ie: future 1.2.1) is the repository I would like to build some updated packages against. I have already done it against Meego 1.2 and Current:Core. From your example, how was the repo for trunk added? It's not listed as a repo that can be added... You should be able to add various repos in the advanced tab on that same page, where it says: Or pick one via advanced interface. There are a lot of distros to build against, I haven't seen the one you're after but I didn't go through the whole list. It isn't obvious, but that form is partial an auto-complete form. So start typing in the project field until you find the repo you want to build against. Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
- Original Message - On Fri, Aug 12, 2011 at 2:32 AM, Nasa nas...@comcast.net wrote: Rudi Thanks Rudi, I will have to take a read. I obviously didn't explain what I was after very well. On the https://build.pub.meego.com/project/add_repository_from_default_list?project=home%3Anasa page there a list of repositories one can add (such as Meego 1.1, 1.2, debian, etc), however, there isn't one for some of the development tracks. For my interest, 1.2.0.90 (ie: future 1.2.1) is the repository I would like to build some updated packages against. I have already done it against Meego 1.2 and Current:Core. From your example, how was the repo for trunk added? It's not listed as a repo that can be added... You should be able to add various repos in the advanced tab on that same page, where it says: Or pick one via advanced interface. There are a lot of distros to build against, I haven't seen the one you're after but I didn't go through the whole list. It isn't obvious, but that form is partial an auto-complete form. So start typing in the project field until you find the repo you want to build against. Thanks Jeremiah, I was putting in the name of my project in that field instead of other projects. Once I did things like meego a whole lot more options showed up... However, I didn't see anything related to 1.2.0.90 and/or 1.3. It looks like this field is only pulling from projects listed on pub OBS - not the build one. Is there a way to cross connect the two? The one thing that I am still confused on... When I add a repository I assume I am building against a list of packages included in said repo. But I don't see a way to see what packages are actually included in the repo I may have just added. Thanks for putting up with us old, slow men. Nasa ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
On Fri, Aug 12, 2011 at 1:14 PM, Nasa nas...@comcast.net wrote: - Original Message - On Fri, Aug 12, 2011 at 2:32 AM, Nasa nas...@comcast.net wrote: Rudi Thanks Rudi, I will have to take a read. I obviously didn't explain what I was after very well. On the https://build.pub.meego.com/project/add_repository_from_default_list?project=home%3Anasa page there a list of repositories one can add (such as Meego 1.1, 1.2, debian, etc), however, there isn't one for some of the development tracks. For my interest, 1.2.0.90 (ie: future 1.2.1) is the repository I would like to build some updated packages against. I have already done it against Meego 1.2 and Current:Core. From your example, how was the repo for trunk added? It's not listed as a repo that can be added... You should be able to add various repos in the advanced tab on that same page, where it says: Or pick one via advanced interface. There are a lot of distros to build against, I haven't seen the one you're after but I didn't go through the whole list. It isn't obvious, but that form is partial an auto-complete form. So start typing in the project field until you find the repo you want to build against. Thanks Jeremiah, I was putting in the name of my project in that field instead of other projects. Once I did things like meego a whole lot more options showed up... However, I didn't see anything related to 1.2.0.90 and/or 1.3. It looks like this field is only pulling from projects listed on pub OBS - not the build one. Is there a way to cross connect the two? Good question. I don't know the answer. I know that one can upload an entire distro and load that into the OBS to build against, you'll likely need special permissions to do that on the official OBS though I'm not sure. At this point, I think we need to get some more info on; 1. The nature and purpose of the various 1.2 point releases 2. How to configure these to build against in the MeeGo OBS I think perhaps Joel C. can answer the first one and Anas the second one? The one thing that I am still confused on... When I add a repository I assume I am building against a list of packages included in said repo. But I don't see a way to see what packages are actually included in the repo I may have just added. That is a very good question. To peer into the repo I think you'll have to go to the separate repo URL. I am not sure if there is a way to introspect the entire package list of one of those repos from the OBS though that sounds like a very good feature. Thanks for putting up with us old, slow men. heh, you can't be older than me. :) Nor slower. Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Adding Repo to OBS
[sorry, i am a new subscriber joining a current conversation that is the exact problem i see] --snip-- * You should be able to add various repos in the advanced tab on that** same page, where it says: Or pick one via advanced interface. There** are a lot of distros to build against, I haven't seen the one you're** after but I didn't go through the whole list. It isn't obvious, but** that form is partial an auto-complete form. So start typing in the** project field until you find the repo you want to build against. Thanks Jeremiah, I was putting in the name of my project in that field instead of** other projects. Once I did things like meego a whole lot more options** showed up... However, I didn't see anything related to 1.2.0.90 and/or** 1.3. It looks like this field is only pulling from projects listed on pub** OBS - not the build one. Is there a way to cross connect the two?* Good question. I don't know the answer. I know that one can upload an entire distro and load that into the OBS to build against, you'll likely need special permissions to do that on the official OBS though I'm not sure. At this point, I think we need to get some more info on; 1. The nature and purpose of the various 1.2 point releases 2. How to configure these to build against in the MeeGo OBS --snip-- +1 on confusion on how to (read-only) link to core repo pkg from pub obs from the build.pub.meego.com side, all the build.meego.com repos appear empty? (to me, a new user with only community obs account). if i try build service - projects - (select MeeGo:Trunk) while logged in,i see: MeeGo Trunk Import of MeeGo trunk Information: This project does not have any packages yet. maybe this is a temporary breakage? the tutorial http://wiki.meego.com/Build_Infrastructure/Packagers_Developers/WebUI_part_2 (for a build.meego.com user) shows that obs should support linking to a package. all the other build repos i checked look the same from the pub side. --snip-- * The one thing that I am still confused on... When I add a repository I assume** I am building against a list of packages included in said repo. But I don't** see a way to see what packages are actually included in the repo I may have** just added.* That is a very good question. To peer into the repo I think you'll have to go to the separate repo URL. I am not sure if there is a way to introspect the entire package list of one of those repos from the OBS though that sounds like a very good feature. --snip-- yes, you can try http://build.meego.com/project/show?project=Trunk or similar. it looks the way it probably is supposed to look if viewing it inside pub repo worked: MeeGo Trunk The Main development tree and core components There are 64 problematic packages of 1408 total (and you can browse all 64 / 1408 pkgs) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Adding Repo to OBS
- Original Message - Hi Nasa, I wrote two whitepapers on OBS: An Introduction to Open Build Service (OBS) and Building MeeGo with OBS. You can download them, for free of course, from the Linux Foundation website: http://www.linuxfoundation.org/publications/workgroup . If you could explain a little more what you are looking to do I may be able to help you out better. With osc you would specify: osc build platform architecture to build your project e.g. osc build Trunk i585 to build your project against the MeeGo Trunk for i586. Rudi Thanks Rudi, I will have to take a read. I obviously didn't explain what I was after very well. On the https://build.pub.meego.com/project/add_repository_from_default_list?project=home%3Anasa page there a list of repositories one can add (such as Meego 1.1, 1.2, debian, etc), however, there isn't one for some of the development tracks. For my interest, 1.2.0.90 (ie: future 1.2.1) is the repository I would like to build some updated packages against. I have already done it against Meego 1.2 and Current:Core. From your example, how was the repo for trunk added? It's not listed as a repo that can be added... Thanks again, Nasa ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
