January 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] SR 149536
by Robert Schweikert 22 Jan '13

22 Jan '13

Hi, SR 149536 contains the fix for image building and is expected to address the issues with "addon-lang" build. The fix for this issue is the only change from the current version in factory, thus the risk is low. 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

1 0

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

22 Jan '13

-- 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:30:07 Betreff: Re: [opensuse-factory] Reminder: we're in feature freeze An: Stephan Kulow <coolo(a)suse.de> Am 21. Januar 2013 22:15:58 schrieb Stephan Kulow <coolo(a)suse.de>: > Am 21.01.2013 20:39, schrieb Robert Schweikert: > > I would argue that the devel project maintainers should be protected > > from themselves and release managers should be protected from auto > > submits after feature freeze. This implies that after feature freeze > > anything that goes through "auto submit" goes to a queue or that "auto > > submit" is disabled between feature freeze and branch. > > > > All of this should be reasonably easy to implement and will be more > > effective than expecting every devel project maintainer to remember at > > every hour of every day that we are now in feature freeze mode. > > > You're serious? I'm having a hard time replying to this - it sounds like > a bad joke. You make it sounds as if it depends on the moon phase if > we're in feature freeze or not. > > Greetings, Stephan > > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > Please reply without ">" in front, makes it easier to follow the discussion. And I do think Robert has a point there but I'm not going to argue with anyone. My takeaway is that I'll try to not submit to Factory anymore until I'm told to do otherwise. -- 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

2 1

[opensuse-factory] replace LXDE with E17 on medium
by Tomas Cech 21 Jan '13

21 Jan '13

Hi, I'd like to add E17 on installation medium which is pretty hard task. My estimation is that ~ 35 MB of space is needed for basic RPMs. I'd like to know what is your opinion, if E17 could replace LXDE on installation medium? Is this still even developed? Thanks. Tomas Cech Sleep_Walker

4 3

[opensuse-factory] VNC install not working
by Chuck Payne 21 Jan '13

21 Jan '13

Guys, Have VNC been remove or is broken on the 12.3 Beta. I have a remote site that I am doing install on. I am doing the following at boot prompt on the the grub menu has I have done in the past vnc=1 vncpassword=installme I get prompt for the network setting, I do set that up, and I can ping the server I am going to install on. Once it starts, I can't connect with vnc client, I have looked at the ps and I don't see any vnc agent. I have even did an nmap to see if the client is up and running, nothing. Please let me know if you need more informations. -- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 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. www.susestudio.com. See you at Southeast Linux Fest, June 7-9, 2013 in Charlotte, NC. www.southeastlinuxfest.org -- 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] Tomahawk 0.6.0 for Factory
by Dominik Schmidt 21 Jan '13

21 Jan '13

Hey list, hey Stephan, I would really like to see an exception from the Factory feature freeze for Tomahawk 0.6.0. It hardly introduces new features but does *A* *LOT* of polishing and fixing up rough edges compared to 0.5.5. We tested it very well before the release and haven't had any reports for regressions or new crashes since the beta1 a few weeks ago. I'm convinced this has much higher quality than the 0.5.5 release and every openSUSE should benefit from it. Best regards, Dominik -- 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] PulseAudio 3.0
by Ondrej Holecek 21 Jan '13

21 Jan '13

Hi, I noticed PA3 did not make it into factory, so it wont be in oS 12.3, is that correct? If so was there a reason to not include it? I noticed that PA in devel project is still being build against factory/snapshot with wrong Bluez thus failing. But against factory/standard is builds ok. I am using PA3 for some time now and was looking forward to not using home project for that in oS 12.3 :) Ondrej

2 2

[opensuse-factory] factory incomplete?
by Peter Czanik 21 Jan '13

21 Jan '13

Hello, I just switched my laptop to factory. The latest update seems to be incomplete from the KDE point of view. Zypper dup says: Problem: nothing provides nepomuk-core >= 4.9.98 needed by kdebase4-runtime-4.9.98-1.1.i586 Solution 1: keep obsolete kdebase4-runtime-4.9.97-1.1.i586 Solution 2: break kdebase4-runtime-4.9.98-1.1.i586 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): And looking at the repository I see: czanik@roxen:/pub/opensuse/factory/repo/oss/suse/i586$ ls *4.9.98* | wc -l 94 czanik@roxen:/pub/opensuse/factory/repo/oss/suse/i586$ ls *4.9.97* | wc -l 186 So, part of KDE is still the old version, part of it is later. I just checked, http://download.opensuse.org/factory/repo/oss/suse/i586/ also seems to be in a similar state, so it's not just my local mirror... Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Who decides what projects are on the yast2 community project list?
by Ralf Lang 20 Jan '13

20 Jan '13

When yast2 add repository dialog is opened, it offers a list of community projects, including packman and some obs projects. How is this list compiled, what are the criteria? If it lists server:php, is this just the top repository or including server:php:extensions and server:php:applications? I have googled a bit but did not find the answer. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Re: [opensuse-factory] MariaDB as a default MySQL
by darx＠sent.com 20 Jan '13

20 Jan '13

On Sat, Jan 19, 2013, at 04:12 PM, Michal Hrusecky wrote: > Well, these are using MySQL API, which is the same. There are reasons that many projects still fully support only one, and not the other. Despite the presumed "same" API. That situation will likely improve/change over time. > > -- a separate devel pkg , libs & includes, be made available. > > I was thinking about that, but it would made it more confusing, > transitions harder and there would be people in obs building against one > and people building against the other one and it will be more messy in > general... I couldn't disagree more. With the "more confusing" & "more messy", in particular. The potential already exists for people building across different libs/apis for a given package. Lua* is one example that causes headaches. That's a result of developer/packager sloppiness, not of having cleanly delineated and complete packaging. If the distro 'standard' should be "always build against _this_, not that, package's libraries, that's a documentation & standards issue. Hobbled or incomplete packaging of mainstream apps is, imo, a bad idea. > Yes, I know, but we are testing them living together for many openSUSE > versions so I believe that most of the issues were polished over the > years already. And during all those years, the default has been MySQL. Proposing the change of *default* at _this_ stage, _this_ late in the 12.3 release cycle, without a more thorough discussion is what I find problematic. MySQL et al are hardly leaf packages. I suspect this is likely happening anyway. In the end, it may be best for the general user/desktop segment. As that's not my own, personal interest, I'll likely add MySQL to my 'DIY' stack and eliminate the issue locally. At this point, I don't find real advantage or benefit in this change, see it as simply change for change's sake, and am concerned that it's a rushed process. Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] OpenStack stable fixes vs version freeze
by Vincent Untz 20 Jan '13

20 Jan '13

Hi all, Thanks to the fast reviews of the legal team and the factory reviewers, OpenStack 2012.2 is in Factory now. That's great news! Now to the next step :-) Some background: we package OpenStack directly from git, and we update to latest git every now and then. There's a nice diagram if you want to get a clear view of this: https://en.opensuse.org/OpenStack_and_Crowbar_development_process The reason we can do this is that there's a pretty strong focus on stability upstream, and changes can only be committed after reviews + automatic testing. So we're quite confident in the quality of what is in upstream git. On stable branches (like 2012.2, aka Folsom, that we have in Factory), committed changes are really only a few bug fixes (and no new features). For instance, between December 17 and today, here's the amount of changes in upstream git for core components of OpenStack: cinder: 1 glance: 4 horizon: 9 keystone: 7 nova: 6 quantum: 21 swift: 0 (I used 'git log --pretty=oneline --since="2012-12-17"' for this, not sure if it's the totally correct way; but it gives an idea of the amount of changes) So that's the amount of bug fixes we get in one month for the stable branch (and as it becomes older, there'll be fewer and fewer fixes). Now, to my question: to what extent would it be accepted that we push these upstream fixes to Factory after the version freeze? I was thinking that it could be okay to keep pushing them until the freeze for RC1. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3