January 2013 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] systemd handling of suspend/hibernate keys and lidswitch
by Richard Brown 23 Jan '13

23 Jan '13

On Wed, Jan 23, 2013 at 7:02 AM, Guido Berhoerster wrote: > Part of that responsibility for breakage also lies within > openSUSE, this is configurable and could easily be changed back > to the default setting acpid had. > The only advantage of the change in defaults is that now laptops > without a desktop environment installed will suspend/hibenate if > you press the corresponding keys/use the lidswitch. On the other > hand desktop environments (including GNOME) in openSUSE which > previously handled this and continue to handle this currently > have to be patched because the necessary changes are not upstream > or in a release yet. When it comes to GNOME, Dimstar (with a little help from myself) looked into this at the recent openSUSE Polish Hackathon You can see the patch here, which is now in Factory: https://build.opensuse.org/request/show/149461 Philosophically, I understand where the systemd developers are coming from and like the idea of there being some power management in the absence of a DE But that does mean the DE's need to do their part to either fully 'take over' from, or properly 'hand off' to systemd to avoid problems like this Hope this helps settle any concerns Richard Brown RBrownCCB(a)opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Maintainer model clean up
by Robert Schweikert 23 Jan '13

23 Jan '13

Hi, This is also related to the "Coolo needs help thread". During osc12 we had various discussions related to the topic of getting the distribution out the door and how we can get there within the release schedule that we had agreed to a while back. Part of this discussion are the two sessions I had the opportunity to lead, both are available on youtube opensusetv, if you are interested in this topic please go and watch these sessions, as well as Stephan's session, also on youtube. Unfortunately we did not have video equipment in the BoF session. The basic proposal is, and this received general agreement at osc12, that we will move toward changing the model as proposed in the session. This implies the following: - In the web UI one will no longer see inherited project maintainers on the package page, only the "true" package maintainers. (Inherited "maintainers" will be hidden in an expandable tree) - We will collect information about all packages in all devel projects that feed factory. We will generate a list of packages that have no maintainer, and a list of packages that need help, i.e. a package that has fewer than 5 maintainers. In addition we will list packages that have more than 5 maintainers and try to encourage maintainers from those packages (to get the number to 5) to take on packages that need help. - We want to clean up the devel project maintainer list to a ratio of 10/500 packages with a max of 25. ~ In many cases package maintainers in a given project do not care about all the other packages in the project, yet they are on the project maintainer list. ~ Also many people have their Hermes notifications disabled as they get too many messages about packages they do not care, hopefully with the changes more people will re-enable their Hermes notifications (more on this below) - We would like to see a notification on the package page if the package fails to build in factory - Would like to see package build status information on the factory status page about the status of the package in it's devel project. - Having the monitor page and the status page presented in the current form is confusing, we need to somehow merge the information. - It would be really nice if there were some kind of policy engine that could enforce the "no more than 5 per package" and the "no more than 25 project maintainers" policies. ~ now OBS is not just for openSUSE, thus this cannot be hard coded into the OBS code, thus this is potentially a lot of work. - We would like to have some kind of rating system on the devel projects - We will produce guidelines for package and product maintainers outlining what is expected. ~ These guidelines are not hard rules, but provide help to new people stepping in to define the role they are comfortable with. There appears to be a problem that the complete void of guidelines in this area leads to paralysis and people just do not know what to do if they want to help. We have documents how to package, these guidelines will be a hopefully short list of "what is expected". These are the rough outlines of the "plan". Obviously there is work to be done and the OBS team already has plenty to do. It is up to me to document in more detail the requirements/use case before a potential timeline can be developed. I will also start a wiki page attempting to define the various roles in the devel process and then opening that up for discussion once the basics are in place. Now to a couple of counter points. - Yes we will step on some people's toe, sorry. Meaning if you get removed as project maintainer from a devel project and you really really want to be a project maintainer you are probably not going to be happy. Please do not take it personal and get yourself added back to the project. Preferably you would find one of the project maintainers that remained, by chance and chance alone, and get that person to drop of the list. Chances are you will find someone willing to "make space for you" ~ Sorry, but this process has to be somewhat arbitrary due to the large number on the various devel projects. ~ Please be not offended, there is no vicious intent, just the intent to help the project grow and scale better. - Yes, the "rules" are changing, and if you maintain a package that is also in factory there will now be some expectations ~ In the end we all should have the same goal, create a quality distro in the time frame we promise, thus this should really not be a big deal Before I close this rather long e-mail (sorry) I have a kind of survey question. I would like to have the hermes settings of package maintainers reset "automatically" as we move through the house keeping project such that package maintainers get notification of build failures of their packages. I realize many people have these turned off today, but again, this is probably due to the number of notifications due to the project maintainer mails that most people do not care about. OK, before I write another couple of pages about this subject I'll stop here. Thanks for your attention, please no flaming, bitching and moaning. Great ideas and help are welcome. Later, Robert -- 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-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 12

[opensuse-factory] Why was kio_sysinfo - My Computer removed for 12.3?
by Roman Bysh 23 Jan '13

23 Jan '13

Hello List mates, Does anyone know why kio_sysinfo was removed for 12.3? Cheers! Roman ------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! ------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 12

[opensuse-factory] systemd handling of suspend/hibernate keys and lidswitch
by Guido Berhoerster 23 Jan '13

23 Jan '13

The systemd version in Factory now handles power/suspend/ hibernate keys and lidswitch by default which breaks power-managers which are not systemd-aware (see e.g. bnc#789057), that is everything except GNOME3/KDE4 such as xfce4-power-manager, empower, or kpowersave. All DEs handle lid-switches, power buttons etc. fine without it and pure WM users are likely to have mechanisms in place (such as a custom acpid configuration) if they need it, so this change in default behavior doesn't have any benefits. Can we change the systemd default settings back to what they are/were with acpid, that is handle only the power button (if possible, only if no DE is running)? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 34

[opensuse-factory] openvpn
by Hans Witvliet 23 Jan '13

23 Jan '13

Hi all, I know you are all busy with 12.3... But any chance that the repo "./network:/vpn/...." got some modest attention? openvpn-2.3 has been released some time ago (8-jan). Besides bug-fixes, it has full IPv6 support. The most recent i can find is the rc1 in mludvig's home dir. Kind regards, Hans -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] 12.3 Beta1 - observations
by Jim Henderson 23 Jan '13

23 Jan '13

I've just installed 12.3 Beta1 in a VirtualBox VM and have run into a few issues that I'm wondering if anyone else has seen. 1. The VirtualBox guest components all seem to be outdated (result from the last milestone was a 640x480 display only, in Beta1 the GUI doesn't start at all). I worked around it by installing the 4.2.6 guest addons after removing the pre-installed packages (which are version 4.2.4). Could we get the 4.2.6 addons in the release? 1.a. Even with the 4.2.6 OSE addons installed, I cannot get 1280x1024 resolution. That may not be a 12.3-specific issue, but I thought I'd mention that I can only select 1280x960 (along with other "standard" resolutions). 2. When I log out and go to log back in, I never get a password prompt (I select the user, and it moves but then bounces back to selecting the user). If I select "Not listed?" and enter my username, I get the error message "[Invalid UTF-8]" (the username is "jhenderson", so I'm not sure what's invalid about that). 3. I installed GNOME3 as the default desktop, then added the other desktops later, but the login screen doesn't seem to have any place to select the DE. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 10

[opensuse-factory] thermal_sys
by Peter Czanik 22 Jan '13

22 Jan '13

Hello, I have a ThinkPad T410 running the latest Factory release since the last couple of days. For the first time ever my laptop was shut down automatically. I found this line in /var/log/messages: 2013-01-22T11:59:36.922822+01:00 linux-4xb2 kernel: [18838.761023] thermal_sys: Critical temperature reached (100 C), shutting down Is this a new feature (after 12.2, which I used until recently), that's why it never happened before? Or it's a bug in thermal management and / or sensors, so I should enter it into bugzilla? Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] SR#149565: Revert libdvbpsi to 0.2.2
by Dominique Leuenberger a.k.a. Dimstar 22 Jan '13

22 Jan '13

Hi Coolo, and list I just submitted SR#149565 to Factory, which reverts libdvbpsi from 1.0.0 back to 0.2.2... Rationale: - libdvbpsi 1.0.0 has a bunch of (not very trivial) API changes... - The most prominent consumer of libdvbpsi is the VideoLAN Project (vlc media player) - To my knowledge, this is rather 'the only consumer of the lib' - VLC (incl. git master) does not yet support this new libdvbpsi API - Nothing in the Factory tree uses libdvbpsi (It's there for convenience only) The proposal to revert to 0.2.2 (last release before 1.0.0) is to - Make my life as VLC maintainer easier :) - Make the life of any user trying to build other packages relying on libdvbpsi easier (if any such package even exists). Please consider this exceptional version change. Best regards, Dominique PS: I'm not aware of any specific guideline on how such a revert is to be done correctly... I now did osc sr -r <rev>; but that obviously removes the .changes entries as well.. Is this sufficient? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Fwd: Re: [opensuse-factory] Reminder: we're in feature freeze
by Sascha Peilicke 22 Jan '13

22 Jan '13

Sorry, this was intended for the list -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) --- Weitergeleitete Mail --- Von: Sascha Peilicke <saschpe(a)suse.de> Datum: 22. Januar 2013 10:24:35 Betreff: Re: [opensuse-factory] Reminder: we're in feature freeze An: Ismail Doenmez <idoenmez(a)suse.de> Am 21. Januar 2013 20:50:28 schrieb Ismail Doenmez <idoenmez(a)suse.de>: > Quoting Cristian Rodríguez <crrodriguez(a)opensuse.org>: > > > El 21/01/13 12:58, Stephan Kulow escribió: > >> Hi, > >> > >> I'm still getting tons of stupid version updates thrown at me. > >> Get real guys - unless you come up with *really* good arguments > >> *on this list* I don't see any reason to take it. > > > > OK, then why isnt the product branched so factory can move along > > regardless of the release status ? > > Because we are supposed to do bugfixes for the release, branching it > off early will result in everyone ignoring and submitting shitloads of > new stuff to Factory. I get the impression that being a openSUSE release manager implies converging on a rather confronting language. Instead you should communicate clear messages. The last one I got was "submit, we gonna decide". The message I get now is "please don't submit for the time being". Which is good. I suspect coolo already disabled factory-auto submissions and he'll inform us once he re-enables that. In the meantime, I agree that it would help that the "forward to factory" checkbox should be disabled by default for now. > > -- > SUSE LINUX Products GmbH > Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] About the reminder mails just sent
by Stephan Kulow 22 Jan '13

22 Jan '13

Hi, Just in case you may wonder: the reminder mails also include a reminder on version updates. This *does* not mean, I want them now. But I won't change the format now - just ignore the section not fitting the current release phase. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0