July 2011 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] upcoming features!
by Jos Poortvliet 16 Jul '11

16 Jul '11

Hi all, A bit of a reminder as well as a thank you for the page about upcoming features for openSUSE 12.1. I saw some people have added some features, which is great! If you want to talk about openSUSE 12.1 and what is coming, use it: http://en.opensuse.org/openSUSE:Upcoming_features If you KNOW what might come or are working on something, OR can fix something - please do! Cheers, Jos

1 0

[opensuse-project] [Off-topic] Does SUSE move to suse.com?
by Kim Leyendecker 16 Jul '11

16 Jul '11

Hello withsusesians! When I open http://www.suse.com I still get redirected to http://www.novell.com/de-de/linux. Are their plans for moving back to suse.com as an independent website? thanks -- Kim Leyendecker (kdl(a)k-dl.de.vu) openSUSE Ambassador, openSUSE Wiki Team DE HAVE A LOT OF FUN! http://www.opensuse.org Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute or create your own Linux distro. Give SUSE Studio a try. http://www.susestudio.… [View More]

6 12

[opensuse-project] Suse Bug Reporter - GSoC midterm report
by Mihnea Dobrescu-Balaur 15 Jul '11

15 Jul '11

Hello everyone, The expected/requested functionalities for the project are done. I'm talking about the CLI version of the tool. Its main functionalities are splitted in four categories at the moment: * aid - helps the user to determine which is the „suspected” package that causes a problem * gather - scans the system for relevant data to provide in a bug report or to someone that helps, via IRC let's say * query - search the Bugzilla instance for bug reports that fit given keywords and sorts … [View More]

3 12

[opensuse-project] Planning Meeting on 2011-07-19
by Andreas Jaeger 15 Jul '11

15 Jul '11

I suggest that we meet on 2011-07-19 to discuss together what the current state of the conference is, who's responsible and what needs to be done. I've started with a first agenda: http://en.opensuse.org/openSUSE:Conference_meeting Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) … [View More]

1 0

[opensuse-project] openSUSE Conference registration open!
by Jos Poortvliet 14 Jul '11

14 Jul '11

The organization team is excited to announce that the registration for the openSUSE Conference, from September 11 to 14 in Nürnberg, is now open. Head over to our registration form and register to help us plan for a great event! http://bit.ly/r2mxGN Preparations Two months from now the openSUSE and SUSE Labs Conference will kick off in Nuremberg, Germany. That means, as flights don’t get cheaper, you have to start planning your days off, your trip, hotel and send in a talk while the CfP … [View More]is still open! Hotel The openSUSE conference team has made a list of hotels where you can book your stay for the duration of the conference. http://en.opensuse.org/openSUSE:Conference_hotels It is recommended to use these hotels as they will not only have fellow geekos in them but are also for special conference prices and not too far from our location, Zentrifuge. Financial travel support For some of you, the trip to Nuremberg is financially not easy. You might be a student, or have to fly in all the way from India. We know that very well and you can count on an announcement of the what and how of travel subsidy soon. We will do everything we can to ensure our community members from far away or on low budget are also able to come and join us! Visa Another important thing to think of in time is access to Europe/Germany. We have a standard invitation letter you can get from us on request. For that, send a mail with some personal details (who you are, what you do for openSUSE, what you will do at the conf, that stuff) to opensuse-conference(a)opensuse.org and the team will send you one. Registration Registering makes sure there’s a badge for you at the conference, you won’t have to wait in line for us to create one for you on the spot. It’ll also make sure you are able to go on the wifi and we have a place for you at the party. And of course it allows us to plan better so it matters a lot that you register as soon as possible if you intend to come! http://bit.ly/r2mxGN Please note that for the registration, you don’t have to create an account. Last but not least, there is an option between two different tickets. Entrance is free for all but those who want to support the conference and can afford it can buy a professional ticket. For $350 or €250 you get, besides access to the conference, a networking dinner with the speakers and other professional ticket holders as well as a session with SUSE Product Management. Helping Out Meanwhile, the conference team is welcomes all the help it can get! If you want to get involved and help us make the openSUSE conference the best ever, please subscribe to the team mailinglist: opensuse-conference(a)opensuse.org and checkout the planning page. [View Less]

1 0

[opensuse-project] openSUSE Conference Registration now open!
by Bryen M. Yunashko 14 Jul '11

14 Jul '11

openSUSE Conference... bigger than ever, better than ever, and made awesomer than ever by your presence at the conference! We're happy to announce that the registration for openSUSE Conference Here's some relevant information for you: - Registration Form - http://bit.ly/nfN4FL - Recommended Hotels - http://bit.ly/qVLplm This year's conference will be held in Nuremberg Germany September 11-14, 2011 in a new location at Zentrifuge. RWX3 is our theme as we are creating a conference in which … [View More]

2 1

[opensuse-project] [GSoC] Entomologist UI Changes - Midterm Report
by David Williams 14 Jul '11

14 Jul '11

Hi everyone, You can find my midterm report at [0] and the text below. I really recommend reading the blog post as it has screenshots of everything :). ----Report Text ---- This report is a summary of all the work that I've completed so far for my Summer of Code and what is to come :). Porting Entomologist to Windows and Mac OS X: Entomologist works mostly flawlessly on Mac OS X. Windows was an awkward platform to port for and it still doesn't function as well as it could but once we hit … [View More]version 1.0 a lot of the problems can be addressed. Tabbed Interface for selecting Trackers: This took a few weeks to complete as it was awkward to get everything to work correctly, I also had the learning curve/understanding new code slowing me down whilst doing it. Overall I'm pretty happy with how it looks and how it works. New Comments Dialog: Next on the list was creating a New Comments Dialog. The goal was to make it easier to select a bug and see the comments and add new comments for that specific bug. The dialog works by either highlighting a bug in the table and hitting Ctrl + Shift + N(Cmd + Shift + N on a Mac) or by clicking the new comments button in the expanded comments dialog. If no bug is highlighted it defaults to opening the first bug in the list. ToDo Lists: This is probably the most helpful feature I've worked on throughout the project. It has been a bit of a learning curve and I think I'm starting to 'Get' QT and I can definitely see why QT is usually classed as better than GTK. This feature still isn't finished but it is nearly all there and I'm currently working on the mechanism to add new ToDoLists. Once that's completed the first basic iteration will be there and it should be useful in that state. Post Midterm Plans: Post midterm I want to add cloud sync to the ToDoLists so you can sync the items to whichever tra cker you feel is appropriate. This should help in organising data and recording milestones through bugs :). I think I'll start by having it export to calendar formats that can be read by normal desktop viewers and they can handle the sync. But the plan is to add that service integration to entomologist itself. After that work is completed I will look at how we can integrate QML into Entomologist so the trackers that it supports can be extended by using QML. This would take a lot of work away from Matt as he won't have to add new trackers, the users that want them can use QML to define them and they can submit them as an extension :). I think this is the best way to manage most bug trackers as there are a lot of different ones out there. So that's it for the work completed so far. Hopefully at the end we'll reach version 1.0 of Entomologist and move on with adding shiny new things :). [0] - http://redache.wordpress.com/2011/07/14/midterm-report-things-completed-so-… Thanks, David Williams Entomologist UI Changes.-- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org [View Less]

1 0

[opensuse-project] Re: Fwd: Suse Bug Reporter - GSoC midterm report
by Mihnea Dobrescu-Balaur 14 Jul '11

14 Jul '11

On Thu, Jul 14, 2011 at 1:19 PM, Michal Vyskocil <mvyskocil(a)suse.cz> wrote: > On Mon, Jul 11, 2011 at 04:41:34PM +0300, Mihnea Dobrescu-Balaur wrote: >> Hello Michal, >> >> This is the report I've sent to the mailing list. >> >> >> Mihnea >> >> >> ---------- Forwarded message ---------- >> From: Mihnea Dobrescu-Balaur <mihneadb(a)gmail.com> >> Date: Mon, Jul 11, 2011 at 4:39 PM >> Subject: Suse Bug Reporter … [View More]- GSoC midterm report >> To: opensuse-project(a)opensuse.org >> >> >> Hello everyone, >> >> The expected/requested functionalities for the project are done. I'm >> talking about the CLI version of the tool. >> Its main functionalities are splitted in four categories at the moment: >> * aid - helps the user to determine which is the „suspected” package >> that causes a problem >> * gather - scans the system for relevant data to provide in a bug >> report or to someone that helps, via IRC let's say >> * query - search the Bugzilla instance for bug reports that fit given >> keywords and sorts them by relevance >> * submit - gets input from the user and submits the bug report to Bugzilla >> >> Underlying nice stuff: >> * duplicate search - this feature was very wanted from what I could >> tell. I managed to implement it using a sorting by relevance of bug >> reports. From what I could see in the tests I've done, it works great. >> Also, it supports "excluded words" functionality. >> * get assignee + maintainers - I use data from the rpm and then get >> the relevant information via OBS, using it's python bindings, not the >> shell tool >> * check account - verifies that the user has a valid account and if >> so, it stores the user's credentials in a hidden file, base64 >> encrypted and pickled to make them not human readable; if the data is >> stored, the user isn't prompted again for username & password when >> interacting with bugzilla >> * globbing : when searching for a package, you can also do something >> like search for ' kde* ' and it will show you what packages match >> * searching local rpm database: it also looks in 'provides', not only in 'name' >> >> There are also some other things that I've implemented by necessity, >> but I think the ones listed above are the ones that deserve to be >> mentioned in this report. >> >> Some sample usage for submitting is here [0]. >> >> You can find the repo here: [1] >> >> There is more to the tool that I can think of right now, so if you got >> any questions, fire away! >> >> I intend to do also a GUI version but I don't know what to use. Maybe >> if libYUI comes along nicely I could use it. What do you think? > > I would postpone the gui version to the next GSoc and focus on the > command line client first :). > >> >> Also, I'll research what I can do to have maybe the bug reporter pop >> up when something crashes. I'm thinking of listening for specific >> signals, like SIGSEGV. Any suggestions are welcome! > > That's trivial - read man 5 core - there's a special file called > /proc/sys/kernel/core_pattern, which can be used for defining the > default name of cores. You might add the /cores/core.%e.%p, which will > created cores like /cores/core.mutt.5687. And you might check this dir > using inotify. > > An alternative approach is add the '| > /usr/bin/susre-bug-reporter-crash-handler' and then the core will be > sent to the standard input of such program. This has only one caveat, > when your handler crasher, it will trigger and another handler run, > which will very probably crashes as well, so the new handler will be > executed, .... and you will end with the DOS on your system. > > Ubuntu's Apport and Fedora's ABRT use this approach, so you might want to check > https://wiki.ubuntu.com/Apport > http://kerneltrap.org/node/14010 > http://justlearningtoblog.wordpress.com/2010/07/23/enable-core-dump-files-i… > > or simply google > http://www.google.com/search?q=apport+core_pattern&ie=UTF-8&oe=UTF-8 > http://www.google.com/search?hl=cs&q=abrt+core_patern&aq=f&aqi=&aql=&oq= > > > BTW: listening of SIGSEGV isn't so trivial, because only parent > processes can do it reliable, so the core_pattern approach is much > simpler. The only one think to do is where to setup - it's not the > problem, after your program is packaged, the init script started on boot > will do it. > I want to implement the crash-watch-feature via core_pattern and inotify. I guess in the C daemon that I will write (something like this [0]) I can have a system call to the bug reporter giving it the path to the core dump file and having that I can detect which package was it and attach the dump to the bug report. What do you think? Speaking of attach - python-bugzilla hasn't got the attach functionality implemented. I'm not sure I know how to implement it myself. I'm thinking something like - using the bugzilla XMLRPC and doing it via http somehow - documentation is here [1]. I don't know if this would be too 'dirty' and if there is a better way. Please let me know, I'm new to this kind of programming. :) One more thing - regarding what files / logs to attach when reporting against certain packages (i.e. Yast log for reporting against yast), I'm thinking of implementing some sort of application hooks (as Ubuntu's Apport calls it). That means a file for each app with a string that represents what to attach. Over this, I'd write a function that scans the folder for such files and checks if the package name in the report matches one of the respective files. If so, it attaches the corresponding log. If you can think of a better infrastructure for this, please let me know! Mihnea [0] http://www.ibm.com/developerworks/linux/library/l-ubuntu-inotify/index.html - example C application [1] http://www.bugzilla.org/docs/tip/en/html/api/Bugzilla/Attachment.html -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org [View Less]

2 2

[opensuse-project] [gsoc] An online repository for color profiles. Mid-term report
by Sebastian Oliva 14 Jul '11

14 Jul '11

Hello everyone! I have my report on http://www.sebastianoliva.com/en/2011/07/gsoc-midterm-report/ Feel free to comment or contact me for anything. Or give it a go and install it locally from the sources at https://gitorious.org/gsoc-2011/gsoc-2011 Regards, Sebastian Oliva -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 1

[opensuse-project] [gsoc] Archlinux backend for Open Build Service midterm report
by Nikolay Rysev 14 Jul '11

14 Jul '11

Hello, all! Sorry for the long silence, I had some problems with my health, but now all is ok. This mail is brief midterm report for «Archlinux backend for OBS». What is done: - Arch module for build which can: * parse PKGBUILDs and extract dependencies * parse .PKGINFO files from .pkg.tar.?z pakages and get info about it - Helper script, which gets repository metadata and prints information about packages in build corresponding format (package metadata parsing functions are also in … [View More]

1 0