July 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Packman Tumbleweed gives an error when selecting certain packages for installation -- nothing provides libc.so.6(GLIBC_2.15)
by Roman Bysh 27 Jul '12

27 Jul '12

Hello all, I'm using Tumbleweed and Packman Tumbleweed. However, on a number of package selections I keep getting an error referring to libc.so.6(GLIBC_2.15). //////////////////////////////////////////////////////// Example #### YaST2 conflicts list - generated 2012-07-26 21:08:26 #### needed by xvidcap-1.1.7-7.15.x86_64 [ ] break xvidcap-1.1.7-7.15.x86_64 by ignoring some of its dependencies [ ] do not install xvidcap-1.1.7-7.15.x86_64 #### YaST2 conflicts list END ### To get around this I must disable Packman Tumbleweed and enable the Packman for openSUSE 12.1. Any thoughts? 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 8

[opensuse-factory] Is there going to be a Grub2 rescue included on the DVD and Live CD?
by Roman Bysh 27 Jul '12

27 Jul '12

Hello all, Since Grub2 can be lost or corrupted. Especially when you have more than one or two distros or OS on your drive. Can openSUSE include a Grub2 install or rescue in the menu of the openSUSE 12.2 DVD and Live CD? It would help out a lot of users. 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

3 2

Re: [opensuse-factory] texlive 2012 and pgf
by Alin M Elena 27 Jul '12

27 Jul '12

Hi Werner, any news on this? at least where and how to generate an updated version of texlive-pgf package? Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- 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] bluetooth not working since kernel 3.4.4
by Alin M Elena 27 Jul '12

27 Jul '12

Hi, since updating to kernel 3.4.4 my bluetooth stopped working... kde claims there is no adapter available and the same gnome... the device is Bus 004 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) [alin@abbaton:~]: dmesg | grep bt [ 15.862126] usbcore: registered new interface driver btusb [alin@abbaton:~]: hcitool dev Devices: I have updated since to the new 3.5.0 kernel and the situation is the same. [alin@abbaton:~]: uname -a Linux abbaton.ucd.ie 3.5.0-1-desktop #1 SMP PREEMPT Tue Jul 24 13:38:05 UTC 2012 (fb9c50b) x86_64 x86_64 x86_64 GNU/Linux Anyone else seeing the same? any advice? Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- 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] SLES 11 Update Repository Broken
by Günther J. Niederwimmer 25 Jul '12

25 Jul '12

Hello, know you that the NU_NOVELL Server is broken ? On my system all Update or other repository Directory are deleted :(. A rerun from the Register Tool have no effect. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- 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] Is systemdadm being added to Yast for 12.2 or 12.3?
by Roman Bysh 25 Jul '12

25 Jul '12

Hello List Mates, I know that systemd has a gui called systemadm. Any chance that it will be added to Yast System? 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

1 0

[opensuse-factory] How many init systems openSUSE needs?
by Michal Vyskocil 25 Jul '12

25 Jul '12

Hallo, At the moment we have two different init systems - the previous old sysvinit and the new one systemd, which is the default one since 12.1. As my hackweek project is very connected into boot, I've discovered this situation ends in a fact that we do not have a good support for sysvinit neither systemd. Few examples: * there is a lot of overlapping between sysv scripts we still use and systemd - systemd-modules-load.service versus /etc/init.d/boot.loadmodules from mkinitrd noone catched because LSB scripts "just works" with systemd * on the other hand Marcus Meissner found several issues in sysvinit support shows a big lack of a testing, because systemd is the default one I do not believe that extending the "transition period" for one, or more openSUSE releases will make anything better. In fact it will extend the painfull perior when systemd-lovers will be upset by a taking a care about the old sysvinit way and sysvinit lovers will feels like second-class citizens in the new world. And that's a perfect example of no-win situation [1]. Therefor I am convinced we as openSUSE community have to 1.) decide 2.) make the winner system the default one and the best one 3.) in case there will be a strong community willing to support the second system from the contest, let invent a way how they can do that. With all great features we have (zypp, OBS) it won't be so hard. I am not sure is how to make such decision in openSUSE community. Would we use FATE voting for that? Or find some dictator/board who will decide? BTW: I hope that you will discuss how many init system we need and in case one is the answer, how to make the decision. Having the last flamewar [2] in a mind, I'd like to have a fire suit. [1] http://en.wikipedia.org/wiki/No-win_situation [2] http://opensuse.14.n6.nabble.com/RFC-DRAFT-Phasing-out-sysvinit-tt3355356.h… Regards Michal Vyskocil

7 11

[opensuse-factory] Check-ins of openSUSE:12.2:Update vs pass through devel projects
by Dimstar / Dominique Leuenberger 25 Jul '12

25 Jul '12

Hi all, I just realize that some packages apparently are entering openSUSE:12.2:Update without passing through their devel projects / openSUSE:Factory. Whereas I of course see that some devel projects move further compared to the freeze in 12.2, I still think it is absolutely crucial that the devel-projects receive the fixes as well, so that they can also enter openSUSE:Factory. I did see in the past that patches went to a release, never did it in Factory and Release+1 had the bug back... things, that could easily be avoided with some minimal 'follow the rules' processes. Important in this case of course would be that the Maintenance team and the package maintainers / devel project maintainers stay in contact about updates... I think, that's something that can be expected. Just looking for thoughts. It's not about blaming or flaming. I'm ONLY interested in improving the process! (This is also why I don't want to give references to any particular incident.. the people affected have been informed by means of bugzilla.. this is sufficient). Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

Re: [opensuse-factory] How many init systems openSUSE needs?
by Frederic Crozat 25 Jul '12

25 Jul '12

Le mardi 24 juillet 2012 à 14:07 -0300, Claudio Freire a écrit : > On Tue, Jul 24, 2012 at 2:02 PM, Frederic Crozat <fcrozat(a)suse.com> wrote: > > If features are missing for sysadmins, please ask for them (with a > > rationale, it is even better) on systemd mailing list. If there are bugs > > remaining, open bug reports. > > I did. There were bug reports, I didn't start them. Not gonna dig them > up, systemd guys (not sure if they were the authors, the maintainers > or what) made it clear they weren't interested in implementing them. > Everything's in the archives. Care to list them here ? -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- 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] Re: openSUSE build & testing procedure and faulty pruning of builds causing build failures
by Linda Walsh 24 Jul '12

24 Jul '12

Marcus Meissner wrote: > On Fri, Jul 20, 2012 at 06:14:53AM -0400, Greg Freemyer wrote: >> On Fri, Jul 20, 2012 at 12:17 AM, Linda Walsh <suse(a)tlinx.org> wrote: >>> What it *sounds* like is that openSuSE is no longer a development >>> / build environment -- that is supported to work to build it's own >>> RPM's. >> Linda, >> >> You are tilting a windmills and you know it. >> >> openSUSE has moved to a new build paradigm and you are complaining the >> old one no longer works and you can't use it to build the distro >> pieces. > > This paradigm you describe is the one we live for ... I do not know ... over 10 > years now, at least for as long as I am with SUSE (10 years). > > That rpmbuild works within a system was always optional. > Patches are welcome btw. --- Could you point the sources and documentation for the tools you use to produce binary & source RPM's, *OTHER* than rpmbuild? What packages don't need to have rpmbuild installed in the buildroot in order to build their RPM's? Unless you show evidence to the contrary, I would submit that rpmbuild is currently used to build rpm's as part of the OBS. I don't think there has ever been any question whether or not rpmbuild was used or supported. The issue is about what is already installed in your build environment. [Open]SuSE, if you remember, rarely used BuildRequires before suse10. Separate "-devel" packages weren't widely used if at all sometime before 10 or 9. It was assumed they were included by installing the product. Only by stripping out what packages normally include not including what the original "product/project" produces with it's configure and make do you run into to these problems. For that matter, it used to be that doc packages were usually not separate either. If OSC/OSB is required to build a distro, why is it not included in the shipped distro binaries and source rpms? What version of OSC/OSB is required to build each release: 11.1 => 12.2? Is this documented and made available for each release? If you don't ship the tools on the distro disks, then you are committing to keeping them online. You may not support SuSE 9.0, However, I don't believe the requirements for supplying the tools and sources to build that release expire -- as the GPL doesn't say that sources to binaries can be unavailable if it is more than 'n' years past their initial release date. That wouldn't be in the spirit of including (or making available) all the sources and tools necessary to build something. At what point did openSuse stop shipping complete sources to build the distro, with the distro? I.e. at what point did you require obs/osc to be the build environment? If isn't already a GPL license issue, is could soon become one if past distro build tools become no longer available. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 19