June 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] drop openmotif
by Stephan Kulow 20 Jul '12

20 Jul '12

Hi, For some reason we have one non-oss package in our oss repo and this needs to be fixed - so I would like to drop openmotif from oss and move it (and it's dependencies). To quote from http://www.opengroup.org/openmotif/faq.html: The Open Group Public License for Motif grants rights only to use the software on or with operating systems that are themselves Open Source programs. In restricting the applicability of the license to Open Source platforms this does not meet term 8 of the Open Software Definition (http://www.opensource.org/osd.html). Now the FAQ also claims they will make an open source release rather soon, but that document was updated last 2004 - and I don't think we will see a lot of new motif software in openSUSE in the future. Right now we have this list of packages that buildrequires openmotif: ddd dx libGLw MesaGLw mfsm mgdiff TeX-Guy timidity vtk xawtv xgrabsc xibod xmgrace xmoontool xpdf-poppler yudit 7 of those are on DVD and would be removed from it - and move to non-oss addon: ddd MesaGLw TeX-Guy timidity xawtv xpdf-poppler yudit Greetings, Stephan -- Last week's pet, this week's special. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6

[opensuse-factory] php 5.4
by pgajdos＠suse.cz 10 Jul '12

10 Jul '12

Hi, I am almost ready to submit php 5.4 branch which now lives in home:pgajdos to devel project/factory as replacement of 5.3. There are also some dependencies building against it so you can try them out. Are there any objections against this step? Petr

10 28

[opensuse-factory] cinnamon
by Nelson Marques 06 Jul '12

06 Jul '12

Coolo, I know this is going to enable you in 'Wrath of God' mode, but nevertheless I have to do it... There's a lot of reports from Cinnamon not being working with proprietary drivers, it does with open source drivers. To be honest, though it's just two packages, it's something not worth the trouble to maintain... here's why: 1) We have 2 GNOME releases per cycle; this means 2 completly different cinnamon's for every cycle; 2) Upstream development isn't either as active as we would like, neither has been receptive to bugs outside Ubuntu/Debian; this is good enough to drop this packages on the spot... 3) Fedora and openSUSE have been having a few issues with prelinking; I can't fix this, goes way over the stuff I know. 4) Fedora has a lot of people trying to block cinnamon from being available in Fedora due to how upstream is doing the development.... This to say... either someone takes cinnamon or it dies right here and right now. I don't have time to go on crazy wild goose chases... and maybe it's time to stop the crazy non-sense stuff I've been doing and dedicate myself to hunting, which at least does provide food :) I'm going to vaporize cinnamon and request deletion from Factory if there are no objections and never look to the thing again :) -- Nelson Marques // I've stopped trying to understand sandwiches with a third piece of bread in the middle... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

Re: [opensuse-factory] Calling for a new openSUSE development model
by Jan Engelhardt 06 Jul '12

06 Jul '12

In http://lists.opensuse.org/opensuse-factory/2012-06/msg00618.html : > >a gcc update would be useful, this probably has to happen very early in >the cycle (right after the release). It looks like this proposal has potential, but I wonder and ponder. I went on to compare the development schedules of a few groups. Because I could not find the freeze dates for older openSUSE anymore (why remove them from the detailed view?), I took RC1 as freeze point. #Group Ratio days between merge-phase and frozen-phase # openSUSE_11.4 7.50 210/28(RC1) openSUSE_12.1 8.62 224/26(RC1) openSUSE_12.2 7.78 210/27(RC1) (prerel-freeze: 6.18, 204/33) Debian_4 4.73 553/117 Debian_5 2.34 476/203 Debian_6 2.91 536/184 Fedora_17 1.22 111/91 Fedora_16 1.67 105/63 Fedora_15 1.06 104/98 And now for the winners: Linux_3.4 0.24 12/50 Linux_3.3 0.25 15/59 Linux_3.2 0.24 14/58 My interpretation: there is not enough testing going on in openSUSE. In http://lists.opensuse.org/opensuse-factory/2012-06/msg00611.html : > >People that commit (accept) changes to a repo should check back within >the next 24h whether the repo still builds and if not fix their >breakage. Manually checking is time consuming. Email delivery about failed events would be better. Such already exists in OBS, but with a handful of twists. For one, the notification system is too coarse: IIRC, lnussel has enabled notifications for his account, and he will get fail reports for packages/PRPs he is not interested in. That is what I remember from a mail of his after I added non-SUSE targets to security:netfilter... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 34

[opensuse-factory] grub2
by Hans Witvliet 05 Jul '12

05 Jul '12

Hi all, today i received a message that grub-2.0 is finally released. I lost track counting how may years they needed for it ;-) Obviously this version can not be included into 12.2, much too late for that now. >From what i learned from the grub2-list, last couple of weeks quite a number of changes finally made it. So will grub2.0 be in a update after the 12.2 release, or will it be 12.3? Hans -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 22

[opensuse-factory] settings needed to get apache working on a local pc {127.0.0.1}
by doiggl＠velocitynet.com.au 04 Jul '12

04 Jul '12

Hello, I am trying to get apache working on a local pc {127.0.0.1} and get this message. Access forbidden! You don't have permission to access the requested directory. There is either no index document or the directory is read-protected. If you think this is a server error, please contact the webmaster. Error 403 127.0.0.1 Wed May 30 19:08:55 2012 Apache/2.2.22 (Linux/SUSE) I have this version of Apache installed on Opensuse 12.2 factory # rpm -qa | grep -i apache | sort apache2-2.2.22-2.3.x86_64 apache2-mod_php5-5.3.10-1.3.x86_64 apache2-prefork-2.2.22-2.3.x86_64 apache2-utils-2.2.22-2.3.x86_64 Questions: - Which directory should this index document reside ? - Is there some documentation on how to get apache working, have you got a link to it ? Thanks Glenn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] splitting the update repo in oss/non-oss?
by Ludwig Nussel 03 Jul '12

03 Jul '12

Hi, openSUSE currently has separate repos for free software according to the free software definition and software that is not free according to that definition (*:NonFree projects in obs). There's only one update repo though that mixes both types of software again. Question is whether we should clean that up an have two update repos. One for oss and one for non-oss. Advantage of two repos is the clear separation of non-free components of course. You can't accidentally build against non-free stuff then. Disadvantage might be that this would add two more repos to a default installation (the non-oss update repo itself and a separate debuginfo repo). Any opinions on the matter? 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-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 13

[opensuse-factory] Disk not bootable after zypper up with grub install problem
by Jogchum Reitsma 03 Jul '12

03 Jul '12

Hi, Yesterday I did a zypper up on the 12.2 beta 2 (Mantis) located on my test disk. Some 2000 packages were to be upgraded, one of them grub 2. Installation of grub halted at 100%, so I decided to give it a Ctr-C, whereupon zypper complained that grub was unable to read from /dev/fd0. No surprise, since a floppy station is present, but no floppy in it. Install of grub being at 100% I chose Ignore, and the install of the rest went on OK. But now I cannot boot from that disk anymore. It's only a test disk, so no harm done, but is the a chance to make it bootable again whthout a fresh install of 12.2? I should add that I have a working 12.1 disk set on the same machine (which I 'm using right now). Besides that, the install behaviour seems wrong to me. In can't find a bug (against grub) for this one, I take it I should file one? regards, Jogchum -- 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] Re: [opensuse] problems building perl 5.14.2 or 5.16.0 using RPMBUILD, build from tar or perlbrew (a cpan util)
by Linda Walsh 02 Jul '12

02 Jul '12

Philipp Thomas wrote: > * Linda Walsh (suse(a)tlinx.org) [20120625 20:28]: > >> COLLECT_GCC_OPTIONS='-v' '--version' '-mtune=generic' '-march=x86-64' >> cc1 -quiet -v -iprefix ../lib64/gcc/x86_64-suse-linux/4.6/ >> help-dummy -quiet -dumpbase help-dummy -mtune=generic -march=x86-64 >> -auxbase help-dummy -version --version -o /tmp/ccggVtI6.s >> gcc: error trying to exec 'cc1': execvp: No such file or directory > > No wonder! Something like COMPILER_PATH=/usr/lib64/gcc/x86_64-suse-linux/4.6/ > is missing in the output so it's no wonder the compiler driver doesn't find > the languge specific compilers which reside in a version specific directory. > Which version of SuSE is this, I assume 12.1? Is this the gcc that comes with > that distribution? > > Why don't you use 'osc build' which will build the package locally but > fetches all that's needed from the obs? > > Philipp > ---- Why doesn't the compiler look where it needs to when it is run? Seems like using a special build system to get around a GCC bug is missing the point. What variables is GCC not setting so it can call it's "cc1" phase"? My PATH is set ok, but we never used to have to set internal paths for compilers for them to work. Seriously -- this is a good reason NOT to build on obs -- because things like this don't get discovered. You didn't see Ritchie using obs when he build "Hello World" -- But at that point I couldn't even write "Hello World " and have it work -- that's pretty bad. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 5

[opensuse-factory] M17N scim gtk help needed.
by Marguerite Su 01 Jul '12

01 Jul '12

Hi, all, I need some gtk coding help to fix scim related packages in M17N repository. package status here: https://build.opensuse.org/project/monitor?blocked=0&building=0&dispatching… == Long version : == I updated scim main package to 1.4.13. You may never heard of this project. It's an old Input Method Framework project. Upstream indeed didn't maintain it for a long time They didn't claim it, but actually all Input Engine sub-packages can't be built against lastest IMF main package. it means they didn't maintain the input engine interfaces like scim-pinyin, scim-chewing, scim-anthy, scim-canna, scim-tables, scim-skk....all of them. So any upstream bug report will be "abandoned". Even if we can open and wait, openSUSE can't. Here's the situation: According to its maintenance status (inactive package maintainers in M17N and upstream, the latest SR against one of them is from coolo about 12 month ago), broken status and popularity among the users, we have made a deal to get rid of it from DVD. And I removed provides tag from scim main package. But, because of sub packages' broken status against Factory, I can't submit any SR against them. It means we may have about 10 broken dependency packages installed in openSUSE 12.2. ( newer version of scim, and old versions of all the others. they can't work together.) So possible solutions are: 1. Drop them completely. Since I fixed all the packages related to zh_CN locale, and I don't know how many people use it in other locales. I can't make such decision. And another reason is because SLE_11_SP2 is still using it. (SLE_11_SP2 is a longer supported version. if I drop them, it'll cause many problems to both SuSE staff and SLE users. Dependencies in SLE_11_SP2 are not new enough to build other IMF like IBus/Fcitx/Mozc/Gcin.) 2. Fix them and remove the provides tags from them. That's exactly I did. Some maintainers said just let scim die. but if we can let it die, we have already done. scim-anthy, scim-chewing and others didn't see any new release since 2006, we're still maintaining it. Because there're no other solutions in some of openSUSE derivatives. Now I have fixed: scim-pinyin, scim-unikey, scim-anthy, scim-hangul. I can't fix others because it's out of my effort. Some of the GTK functions and macros used in them are too old (GTK 2.12) and have no new alternatives. It means we have to rewrite some lines of its codes. like GTK_Fileselection to GTK_Dialog, GTK_combo to GTK_combobox. So if anyone have time and GTK coding experience, please offer some help. Greetings, Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 16