August 2012 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] Upstream Tracker - Weekly Update
by N B Prashanth 16 Aug '12

16 Aug '12

Hi, Last week a lot of things have been updated in the project. 1. The python backend now uses multiple threads to process records. 2. Added paper trail support for reverting to older versions of the record. 3. Added record history table showing the details of record changes. 4. Added Devise for user authentication (sign up/sign in). Applicable for reverting and deleting records. 5. Updated and improved DEHS support. 6. Added multiple branch support (currently i/p and o/p are in CSV format). 7. Several small UI enhancements. What's left : 1. Documentation on setting up and working with the upstream tracker with examples on using the API. 2. Add a ToDo list in the documentation which indicates possible future enhancements. 3. Multi branch support should return multiple branch details in proper XML rather than in CSV format. -- Regards, N.B.Prashanth -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [gsoc] osc2 client - summary of week 12
by Marcus Hüwe 15 Aug '12

15 Aug '12

Hi, here’s a small summary of the 12th (coding) week. The last week I continued the work on the new user interface. As a result the "request" command is more or less implemented. Yesterday I pushed the current code and it's also possible to play around with it: - checkout the code [1] - cd osc2/osc/cli - export PYTHONPATH=/path/to/osc2 - python cli.py -h (for more information) Example: In order to list a request it is sufficient to run "python cli.py request api://your_project" (Note: all https requests are _insecure_ - so far the certificate etc. is not checked). Some implementation details: In my last mail/post I described how a new (sub)command can be specified so I'll leave out the details here. In the following I'll shortly explain how the arguments specified by the user at the commandline are passed to a function (which does the actual work - like listing the requests). class RequestList(CommandDescription, Request): """ ... """ cmd = 'list' args = 'api://project?/package?' opt_user = Option('U', 'user', 'list only requests for USER') func = call(request.list) As we can see the project and package parameters are optional. After the parsing process a so called "info" object is returned which encapsulates the specified arguments. Assume the user runs "request list api://test_prj" then the info object has the following attributes: info.apiurl = <the default apiurl> info.project = 'test_prj' info.package = None The question is how can we pass this data to the request.list function? A simple (and naive) approach would be to simply pass the "info" object to the request.list function that is "list" has the following signature "def list(info)". As a consequence inside the method we always have to use "info.project", "info.package" etc. which is a bit awkward - at least for parameters which are quite frequently used in the method definition. So it would be nice if there's a way to pass frequently used parameters directly to the method (that is they're declared as formal parameters in the method definition) and infrequently used parameters can still be accessed via the info object. Exactly like this it is currently implementend in osc2. So the following signatures would be correct for our example: def list(project, package, info) def list(project, package, user) def list(project, package, user, info) def list(project, info) def list(info, project) def list(project) # using the info object is not mandatory def list() # quite useless... ... Invalid signatures: def list(prj, pkg, info) def list(foo, info) ... So it is up to the developer how to define the signature of the request.list function - it is not completely dictated by osc:) Marcus [1] https://github.com/openSUSE/osc2 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] GSoC: AppStream / Software-Center project #8
by Matthias Klumpp 15 Aug '12

15 Aug '12

Hi! Sorry for the late report this time (since I switched to weekly reports), but I had a crazy time the last days and haven't had the time to write this report. Stuff dome the last week: * Wrote some more documentation about AppStream stuff * Discussed the AppStream index library, we now have very concrete plans * Tried to track down a Zif bug with Richard - I need this Zif bug solved to continue testing the SC properly, so unfortunately this stuff took lots of time and isn't finished yet * More SC madness: Added some more code to make using the SC easier, found some more things to port to the new API * Various improvements on the SC Unfortunately, because testing is very difficult, I'm not really fast with the SC stuff. In a few days I have to write a important exam again, so I will now focus on minor improvements and changes, which don't break the SC much and might produce other difficulties. (This was planned anyway, since we're now past the suggested-pencils-down date) As always, if you have questions, ask! I'll write a complete report about the stuff I've done after firm 'pencils down' date as a blogpost - there'll also be a video inside to show you how the SC works on other distributions, because it's still hard to set-up. I hope I can do as many improvements as possible before. Cheers, Matthias -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] GSoC: AppStream / Software-Center project #7
by Matthias Klumpp 14 Aug '12

14 Aug '12

Hi! Work done during the last week: * Discussed writing a libappstream with developers of other Software-Centers, which will allow accessing the AppStream-DB via an easy GObject-based interface. This will allow us to have all SC projects agree on a common DBagreement ("standard") which would be the AppStream database. All like the idea, so I added this to my post-SoC-TODO - some talking still has to be done. * Finished PackageKit parallelization, the most important part of my work! - wrote remaining unit tests - added lots of documentation and a extended the porting-guide for PackageKit backends - tested with Zif and Aptcc backend * PackageKit 0.8.3 release with all changes upstream, released today! :-) * Run some performance tests on Fedora * Added a whole bunch of improvements to the SC code, including some bugfixes - E.g. we no use the more advanced PkTasks object for some actions now (where it makes sense) - Fixed some crashes - Adjusted to new PK 0.8.x API - Directly connect to the AppStream database, so we can Resolve() as many packages as possible * Unfortunately, the Zypper backend of OpenSUSE is not yet ready * Experienced some new problems, details below I also had a meeting with people from OpenSUSE/SUSE to talk about what is necessary to get Software-Center support in OpenSUSE. It was a very productive meeting, and I hope you'll see the results later. For now, I will create a step-by-step plan about what needs to be done to make AppStream/SC work in any distribution. I already have some drafts for it (notes I wrote down during my work on the AppStream DB) and will publish the list this week. Also, the PK backends are in a not-so-great shape, which makes testing the SC really, really hard and annoying. This will become better soon, but I don't think it will work in time with my SoC. So I will probably not have a usable SC and the end, but I'll have a SC which will work good as soon as PackageKit backends are fixed. The remaining time I'll try to squash as many annoying bugs I can find and make the SC work well enough for basic testing. To get a great and usable project, I'll have to invest some more time after the SoC, which I'll do. These are the recent changes/findings, I'll keep you updated! As always if you have questions, feel free to ask! Cheers, Matthias -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] How does the decision making progress is called
by Togan Muftuoglu 13 Aug '12

13 Aug '12

Hi, In a recent mail to opensuse-factory [1] , regarding the implementation of Secure Boot for openSUSE - a proposal for the coming openSUSE release here is what Andreas wrote "Based on the feedback on this mailing list as well on opensuse-project, this is a clear "go" for the proposal." Now let me begin by stating the proposal is fine, and I am in favor of it. Nevertheless, the way "clear go " is defined makes me wonder, if the community is a follower or the leader. I thought the poll system was to include the community in situations like this, giving the opportunity to be involved in the decision process. If what has been preached is not practiced then what does opensuse member system stands for other than giving the email, irc cloaking and similar things. Togan http://lists.opensuse.org/opensuse-factory/2012-08/msg00294.html -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

10 14

Re: Fwd: Re: [opensuse-project] UEFI Secure Boot
by Greg Freemyer 11 Aug '12

11 Aug '12

On Fri, Aug 10, 2012 at 8:59 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > > > On Fri, Aug 10, 2012 at 8:25 AM, Basil Chupin <blchupin(a)iinet.net.au> wrote: >> >> On 10/08/12 19:44, Vojtech Pavlik wrote: >>> >>> On Fri, 10 Aug 2012 18:59:26 +1000, Basil Chupin wrote: >>> >>>> My question is: what would happen when one should use - as I did today - >>>> a bootable CD like System Rescue Disc? (I am guessing that if this were >>>> the openSUSE installation DVD then it would have some code in it which >>>> would allow it to boot without problems.) >>> >>> The openSUSE installation DVD will of course boot, having all the >>> proper signatures that you needed to install the OS in the first place. >>> And it will be booting the kernel present on the DVD, which is signed by >>> the SUSE key. >>> >>> In case you wanted to create your own rescue DVD that'd be booting >>> custom kernels, that'll be possible, too, using the same shim loader >>> you'll be able to enroll your MOK, or just use one if already present on >>> the system. >> >> >> Thank you for confirming what I suspected. >> >> My apologies for using the wrong name for the CD I mentioned above, >> however I was wondering how a bootable CD such as the SystemRescueCD which >> comes from systemrescuecd.org >> (http://www.sysresccd.org/SystemRescueCd_Homepage), and similar bootable >> media, would boot under this UEFI process? >> >> >> BC >> It was my impression that most UEFI bios solutions would not test CD boot media. Forcing CD/DVD boot media to be signed with a well known key would end the use of CD/DVD boot media for all but Microsoft I suspect. (ie. How does the initial openSUSE install get on to a box if install media doesn't have a way around the signing/validation rules.) The same will also need to apply to USB boot media I hope. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 5

Re: [opensuse-project] UEFI Secure Boot
by Basil Chupin 10 Aug '12

10 Aug '12

On 10/08/12 22:59, Greg Freemyer wrote: > > > On Fri, Aug 10, 2012 at 8:25 AM, Basil Chupin <blchupin(a)iinet.net.au > <mailto:blchupin@iinet.net.au>> wrote: > > On 10/08/12 19:44, Vojtech Pavlik wrote: > > On Fri, 10 Aug 2012 18:59:26 +1000, Basil Chupin wrote: > > My question is: what would happen when one should use - as > I did today - > a bootable CD like System Rescue Disc? (I am guessing that > if this were > the openSUSE installation DVD then it would have some code > in it which > would allow it to boot without problems.) > > The openSUSE installation DVD will of course boot, having all the > proper signatures that you needed to install the OS in the > first place. > And it will be booting the kernel present on the DVD, which is > signed by > the SUSE key. > > In case you wanted to create your own rescue DVD that'd be booting > custom kernels, that'll be possible, too, using the same shim > loader > you'll be able to enroll your MOK, or just use one if already > present on > the system. > > > Thank you for confirming what I suspected. > > My apologies for using the wrong name for the CD I mentioned > above, however I was wondering how a bootable CD such as the > SystemRescueCD which comes from systemrescuecd.org > <http://systemrescuecd.org> > (http://www.sysresccd.org/SystemRescueCd_Homepage), and similar > bootable media, would boot under this UEFI process? > > > BC > > It was my impression that most UEFI bios solutions would not test CD > boot media. > > Forcing CD/DVD boot media to be signed with a well known key would end > the use of CD/DVD boot media for all but Microsoft I suspect. > > (ie. How does the initial openSUSE install get on to a box if install > media doesn't have a way around the signing/validation rules.) > > The same will also need to apply to USB boot media I hope. > > Greg OK, interesting. Sorry for being 'dense' on this matter but a bootable disc like SystemRescueCD is a Linux bootable disc which loads a system with a kernel and contains many tools to be able to access and alter an existing system installed on an HDD. I even used this disc to remove encryption from my /home directory when an update to openSUSE 12.1 went wrong. Would such a disc be affected by this UEFI? BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.0-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 5

Re: Fwd: Re: [opensuse-project] UEFI Secure Boot
by Vojtech Pavlik 10 Aug '12

10 Aug '12

On Fri, 10 Aug 2012 18:59:26 +1000, Basil Chupin wrote: > My question is: what would happen when one should use - as I did today - > a bootable CD like System Rescue Disc? (I am guessing that if this were > the openSUSE installation DVD then it would have some code in it which > would allow it to boot without problems.) The openSUSE installation DVD will of course boot, having all the proper signatures that you needed to install the OS in the first place. And it will be booting the kernel present on the DVD, which is signed by the SUSE key. In case you wanted to create your own rescue DVD that'd be booting custom kernels, that'll be possible, too, using the same shim loader you'll be able to enroll your MOK, or just use one if already present on the system. -- Vojtech Pavlik Director SuSE Labs -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 3

[opensuse-project] update about openSUSE Team at SUSE
by Agustin Benito Bethencourt 10 Aug '12

10 Aug '12

Hi, As you probably know, the team within SUSE supporting the openSUSE community is going through some changes. To begin with, I have joined SUSE as Team Leader [1] and we are hiring [2] to fill other vacant positions. Secondly, to reflect the team's increased responsibility for openSUSE within the company, we've dropped the term 'Boosters' to become simply 'the openSUSE team'. We are concentrating our efforts on three main tasks. a.- 12.2 Release b.- openSUSE Conference and openSUSE Summit (especially the first one since it is larger) c.- Internal reorganization a.- 12.2 Release Those of you involved in the technical side are already aware that Ismail Doenmez is now part of the (virtual) Release Team, assisting Coolo with release management. This team is working alongside you on having the best possible openSUSE 12.2 release from the technical point of view. The release process of openSUSE, like any other complex integration process, requires the participation of people from different teams and expertise areas. An open project combines community, SUSE and other professional contributions as well as external involvements like media production. This makes the management/coordination perspective even more complex. One of the things we think is needed is to update the documentation related with the release. We thought it was the first step to go through the entire process, analyze it and improve it for future releases. So, we are talking internally with the people involved in previous releases collecting what they did, trying to have a simple document as an early result. Yes, this is preventing some of us on focusing on "real release work" for a few days, but we hope that will save us time in the near future. Whatever we do can only ever be partial if we do not take account of the huge amount of work on openSUSE done by the community. So next week, we will publish a draft describing the release processes, so that you can give us input for an open release process. The goal is not to have a perfect document this first iteration, but a useful document. This draft will include the actual 12.2 release date. As you can see, we are aiming to meet the adjusted schedule. b.- oSC'12 We will give you some update about the openSUSE Conference (from our perspective) later this month. Please ping any of the team members if we haven't done it by the end of August. Obviously you can ask Michal Hrusecky for details any time. c.- Internal reorganization SUSE is concentrating the professionals that work full time on openSUSE around a single team. So in addition to the technical support we usually provided, this team will also provide community, marketing and economic (coordination) support to the Free Software project. We will also serve as link to the service team, who takes care of the infrastructure, and other teams within SUSE which work is directly on indirectly related to the community. The goal of this new configuration is: 1.- Simplify management and coordination. 2.- Increase community engagement. 3.- Improve efficiency. We expect to provide a clearer view of how these changes can be executed during the openSUSE Conference. The idea right now is to use the event to collect as much input from you as possible. we will close our Action Plan afterward. [1] http://lists.opensuse.org/opensuse-project/2012-06/msg00258.html [2] http://www.suse.com/careers Saludos -- Agustin Benito Bethencourt openSUSE Team Lead at SUSE abebe(a)suse.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 3

[opensuse-project] larger openSUSE deployments?
by Ludwig Nussel 10 Aug '12

10 Aug '12

Hi, I'm currently investigating whether and how openSUSE is used in larger deployments. Does anyone know someone who manages like let's say 30 or more openSUSE machines at once? I'm interested in e.g. what tools are used in such a scenario and what rough edges in the distro we maybe have that could be improved. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

13 19