openSUSE Project July 2012

project@lists.opensuse.org

50 participants
41 discussions

by Marioh mrs

Hi all, Progress so far is another patchset for the tst_tmpdir file in the test library. This patchset includes coding style fixes, removal of obsolete calls / methods as well as a test file implementing a simple test case to check that the file works as expected. Work currently undergoing: Creating a file to document the tst_ inrface of the test library to be uploaded in github's documentation pages as well as cleaning up/fixing a few more files from the tst_ inteface. You can track the progress in the ltp mailing list (https://lists.sourceforge.net/lists/listinfo/ltp-list) or the ltp's github (https://github.com/linux-test-project/ltp) -- Marios Makris -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 11 months

[opensuse-project] openSUSE Summit & openSUSE Travel Support Team

by Izabel Valverde

Hello all, The openSUSE Travel Support Team is happy to announce that we are ready to process applications to sponsor openSUSE people to attend openSUSE Summit. The openSUSE Summit will happen in Orlando, Florida - September 21-23, 2012. Instructions on how to apply and further information about the Travel Support Program and eligibility can be found http://en.opensuse.org/openSUSE:Travel_Support_Program Important dates! The Sponsorship Request period for openSUSE Summit ends on July 20, 2012. Responses will be given before July 30, 2012. Some additional comments: * A clear and complete application is faster and easier to process, so please read the wiki page carefully! * We cannot fulfill all requests, keep in mind that there is no guarantee you will get sponsored. * Sponsorship decisions are influenced by the history of the requester, like having followed the requirement of writing a report about a conference you attended with sponsorship or having send in the required paperwork in time. * If you were part of Google Summer of Code as openSUSE student or mentor you should mention it in your application. * If you submitted an abstract to be presented at openSUSE Summit should mention it in your application. The Travel Team sends a reply upon receiving your application. We will then wait for all applicants to send in their requests for the event and only once we have a full overview, responses will be given. Please do not send personal emails, always CC the travel-support team in your replies. Best Regards, Izabel Valverde On behalf of openSUSE Travel Support Team -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 11 months

Fw: [opensuse-project] larger openSUSE deployments?

by vetter＠physik.uni-wuerzburg.de

Hi, we are running a computer pool for students with 48 machines on openSUSE 12.1. Ususally we try to install "almost everything" except software that is really annoying when $HOME is on NFS (e.g. beagle in former times). In older times we used autoyast to install a new version of openSUSE. But autoyast is just taking too long to install such a long list of software, and when you forget about a small thing, the turnaround time with such a big number of packages to install is too long. So we switched to autoyast and images (tar.gz method) for new machines (or new harddisks) and zypper dup for upgrading on working machines to new releases. These upgrades take place in the break between semesters. zypper dup usually works great. But somehow from 11.4 to 12.1 the update-alternative files for java were messed up resulting in a non-working java plugin for browsers. Found out by accident last week. Since our university uses Novell iprint for charging the students for printouts, we had to find out, that cups 1.5 does not work with iprint client. And so we had to build cups 1.4 for openSUSE 12.1. Printing seems to be one of the most complicated problems in universe ;) Students love n-up printing to save money. But somehow this seems to confuse printers from all kinds of different manufacturers (HP, Lexmark, Sharp). There is also no clear statement how to do it right, because for some PDFs you better use n-up printing from acroread and for others you can only use okular and cups n-up printing. Failure of printing "the right way" (TM) will result in hanging or resetting the printer. Since the machines are administered by central root, we disable NetworkManager, Update Notifications, and so on. Bad thing is, this changes from release to release, and we have to consider all desktop flavours (KDE, Gnome, LXDE, ...). For updates we use the automatic online update. Problem here was: SuSEconfig is not run. But this problem decreases, since SuSEconfig does less from release to release. Another thing I'm not quite sure about is: when e.g. openssl library is updated, a lot of services are affected (zypper ps can tell you), but the services are not restarted automatically. Since our machine run rather long (until next kernel update or crash or power plug pulled) they only get restarted when we do a zypper ps manually and either restart services manually or reboot. Well this should not be necessary, but I'd feel better if zypper ps shows nothing. To change the configuration on all machines, we usually copy the configuration file(s) to all machines and restart the service. We have scripts using SSH with authorized_keys for that. Problem is, if a machine is not online, it does not get the change and one must remember to change it, when the machine comes back. If there is a better solution, please let me know. Wow, that was log. I didn't intend a such long post ;-) -- Mit freundlichen Gruessen, Andreas Vetter Informations- und Kommunikationstechnik Fakultaet fuer Physik und Astronomie Universitaet Wuerzburg -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 11 months

[opensuse-project] Today's meeting minutes

by Robert Schweikert

Meeting ended Wed Jul 11 18:56:40 2012 UTC. The log and minutes are available from: (v 0.1.4) (02:56:42 PM) bugbot: Minutes: http://community.opensuse.org/meetings/opensuse-project/2012/opensuse-proje… (02:56:42 PM) bugbot: Minutes (text): http://community.opensuse.org/meetings/opensuse-project/2012/opensuse-proje… (02:56:42 PM) bugbot: Log: http://community.opensuse.org/meetings/opensuse-project/2012/opensuse-proje… -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 11 months

[opensuse-project] Upstream-Tracker:GSoC 2012:Weekly report

by N B Prashanth

Hi, The last week has not been very eventful as I had to shift to Singapore from India for higher studies. But there have been a few changes. The major work pertains to supporting custom regex in the URL input fields. A partial support for this is available, but is not sufficient. We would ideally like to have full regex support and this is the main part of the project I am currently working on. Apart from this, support to track sourceforge hosted projects has been added. Once the custom regex has been implemented, DEHS imports can be worked upon. -- 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

9 years, 11 months

[opensuse-project] [reminder] openSUSE Project Meeting tomorrow at 17:00 UTC

by openSUSE Meeting Reminder

Hello all, The biweekly project meeting will be held tomorrow at 17:00 UTC in #opensuse-project on freenode. Everybody is invited to join and participate! Find out what time the meeting will be in your timezone: http://timeanddate.com/worldclock/fixedtime.html?day=11&month=7&year=2012&h… Agenda of the meeting: http://en.opensuse.org/openSUSE:Project_meeting#Agenda_for_the_next_meeting If you cannot participate and want a specific question to be answered during the meeting, please add your question to: http://en.opensuse.org/openSUSE:Project_meeting#Questions_Section Minutes and logs of previous meetings can be found at: http://community.opensuse.org/meetings/opensuse-project/ Thanks, -- openSUSE Meeting Reminder -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 11 months

[opensuse-project] [gsoc] osc2 client - summary of week 7

by Marcus Hüwe

Hi, here's a small summary of the 7th (coding) week. Last week I was really busy with university stuff (it was the second last week in the lecture period so I had to recap quite some stuff) and didn't manage to work much on the GSoC project. I'm going work off the TODO this weekend. Marcus -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 11 months

Re: [opensuse-project] larger openSUSE deployments?

by Ludwig Nussel

vetter(a)physik.uni-wuerzburg.de wrote: > we are running a computer pool for students with 48 machines on openSUSE > 12.1. Ususally we try to install "almost everything" except software that > is really annoying when $HOME is on NFS (e.g. beagle in former times). Ah, the famous "zzz All" entry :-) > and images (tar.gz method) for new machines (or new harddisks) and zypper > dup for upgrading on working machines to new releases. These upgrades take > place in the break between semesters. So for that I guess you have to log into each machine and run and watch zypper dup manually? > Printing seems to be one of the most complicated problems in universe ;) Yeah :-) > For updates we use the automatic online update. Problem here was: > SuSEconfig is not run. But this problem decreases, since SuSEconfig does > less from release to release. > Another thing I'm not quite sure about is: when e.g. openssl library is > updated, a lot of services are affected (zypper ps can tell you), but the > services are not restarted automatically. Since our machine run rather > long (until next kernel update or crash or power plug pulled) they only > get restarted when we do a zypper ps manually and either restart services > manually or reboot. Well this should not be necessary, but I'd feel better > if zypper ps shows nothing. Indeed. With systemd it should even be possible to automatically determine the service for each pid. Maybe worth filing a feature request. > To change the configuration on all machines, we usually copy the > configuration file(s) to all machines and restart the service. We have > scripts using SSH with authorized_keys for that. Problem is, if a machine > is not online, it does not get the change and one must remember to change > it, when the machine comes back. If there is a better solution, please let > me know. Isn't that someting puppet or func try to solve? 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

9 years, 11 months

[opensuse-project] fdisk project - GSoC weekly report 6

by Davidlohr Bueso

Hi, To begin, it's worth summarizing were fdisk currently stands as per gsoc tasks. Up to this point a good part of the API is now established and implemented - with the device, MBR, geometry and topology information already upstream. For the next few weeks the label specific disk operations will be implemented. There are still a few details as to the design, specially keeping in mind that it must be generic and labels operations often aren't. Specifically, this week the label probing logic is being written and will be sent for review as soon as possible. Thanks, Davidlohr -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 11 months

[opensuse-project] [gsoc] osc2 client - summary of week 6

by Marcus Hüwe

Hi here's a small summary of the 6th (coding) week. Last week I continued working on the build module and developed a concept for the package fetcher (and discussed some parts with darix:) ). The main idea is to modularize the fetcher code, verify code etc. Thus we have a fetcher class which takes care of retrieving the packages. The fetcher class utilizes a "cache manager" which takes care of storing the fetched packages on the filesystem. The goal is that at some point in time one can exchange the "simple" cache manager with a more "clever" cache manager (which for instance cleans up the cache from time to time or only allows exactly one version of a package in the cache etc.). In order to achieve this no code in the fetcher has to be touched - instead it's sufficient to pass a different cache manager object to the fetcher. Additionally the fetcher provides some hooks like pre, pre_fetch, post_fetch and post. For instance a post_fetch hook can be used to verify the just fetched package etc. TODO: - write testcases and implement the concept from above If you have questions, suggestions etc. feel free to contact me:) Marcus -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 years, 12 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project July 2012