August 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Chromium to be included in Factory ?
by Raymond Wooninck 29 Aug '11

29 Aug '11

Since last week Chromium has received it's own little place in the openSUSE OBS and will be removed from the Contrib repo's in the next few days. The thinking behind this move was to submit Chromium (including it's javascript interpreter V8) to Factory. It would be definitely good to have Chromium and V8 checked legally, but I wonder if inclusion in Factory is something that is really wanted. Or that there are obvious objections against it. If we would like to go forward with this, then I would like to ask if the project network:chromium can be listed as devel project for chromium, so that I can submit both packages. Thanks Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 5

[opensuse-factory] cdemu
by Anders Johansson 29 Aug '11

29 Aug '11

Hi, Would there be any interest in including http://cdemu.sourceforge.net into the distro? I've packaged it in my home project home:ajohansson:cdemu and I've been playing with it for a few hours, and it seems really useful. One step above loopback devices, in that the whole system thinks the ISO image is a real CD/DVD, and it handles multiple formats What's the opinion here? I could volunteer to maintain it if it's accepted Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 10

[opensuse-factory] Banshee-1 failing to build in factory or Tumbleweed or openSUSE 11.4
by Greg KH 29 Aug '11

29 Aug '11

Hi, Something's happened recently to keep banshee-1 from building properly in openSUSE 11.4 or Tumbleweed or Factory. Any hints as to what went wrong and how to fix it? I'm looking at the Banshee project for this, should I be looking somewhere else for updated versions of Banshee to link into Tumbleweed instead? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 8

[opensuse-factory] RFC: Dropping xsane in favour of simple-scan from the default gnome pattern
by Atri 29 Aug '11

29 Aug '11

Hi! I would like to request considering dropping xsane (the scanning application so the default in openSUSE GNOME) from the default gnome pattern in openSUSE 12.1 in favour of simple-scan [1], which is (as the name suggests) a much simpler and, in my opinion, more usable scanning utility. Simple-scan is also a gtk3 app making it integrate nicely in GNOME 3+. Please note that the request is to drop xsane from the default pattern alone, but not to have it removed from the OSS repo at all. Anyone who wants to use xsane instead could still do a "zypper install xsane" and with the default repositories enabled that would be that. For factory testers, simple-scan is already in Factory, and you can simply do "zypper in simple-scan" to install and start testing simple-scan. xsane should already be a part of your installation at the moment. Thanks and bye -- Atri [1]: http://ftp.gnome.org/pub/GNOME/sources/simple-scan/3.1/ https://launchpad.net/simple-scan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 8

[opensuse-factory] gdk-pixbuf/gdk-pixbuf.h: No such file or directory
by Ilya Chernykh 29 Aug '11

29 Aug '11

Hi! It seems the header gdk-pixbuf/gdk-pixbuf.h has been removed from Factory. With what should I replace it? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 16

[opensuse-factory] New package: gigaset-frontend
by Pascal Bleser 29 Aug '11

29 Aug '11

SR: 79986 Userspace configuration tools for Siemens Gigaset ISDN devices. Extremely useful for those who use such devices, as it is pretty much the only non-broken way to configure them. While there probably aren't that many ISDN users left out there, for those who are, it is even more useful if it is included in the distribution. URL: http://gigaset307x.sourceforge.net/frontend.html Security record: none, but there has been no exploit as of now; low risk, as it is a hardware configuration tool Upstream contact: Tilman Schmidt <tilman(a)imap.cc>, who is an openSUSE user, does intensive testing of that project on openSUSE, and also one of the upstream developers; he can definitely provide feedback and help if the need arises The package is currently in the "hardware" project. cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf

1 0

[opensuse-factory] WINE problems, and why it matters.
by Roger Luedecke 26 Aug '11

26 Aug '11

So, Blizzard sent me some promo time and I figured I would go ahead and use it. Why not? AppDB lists it as Platinum or Gold, so its sure to work. And the installer runs beautifully, the launcher renders correctly. But once I click play, it doesn't actually launch the game... a game with a reputation for working really well with WINE. This is hardly the first problem I have had with gold and platinum rated games... in fact, none I have bothered with ever actually worked. The few times I have tried software not in the AppDB, and that worked... I wasn't able to add my findings to their DB since the version of WINE shipping with openSUSE is deprecated. I even installed the CVS builds from the WINE CVS repo. Still not working as it should. So the question is, what is the problem with our WINE implementation? And is there any chance a massive distro like ours could reach out to the WINE Developers to make sure when WINE ships in 12.1 it will perform better? To the credit of the experience of using WINE on openSUSE vs. Ubuntu (or Fedora if I remember correctly) we at least don't have the paranoia of CD/DVD executable media that makes it necessary to copy all files to HD just in order to use them. As far as that goes, we definately did better. Many of you may consider WINE to be a non-concern. I must however object that though it is not essential to the progression of our core technologies, it is very useful to the person checking it out; the casual user who still enjoys games, and has no ideological problem with using some proprietary software. It is hard for me to sell openSUSE to friends of mine who hate Windows, but still love games. "Well, there is WINE which will allow you (in theory) to run many Windows software titles... you can check the AppDB at WINEhq. But, honestly I find it rarely works quite as it says in the AppDB." Not a great way to get gamers to dump Windows. Roger Luedecke openSUSE Ambassador -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] no builds after openSUSE-KDE-LiveCD-x86_64-Build0186-Media.iso
by doiggl＠velocitynet.com.au 26 Aug '11

26 Aug '11

Hello Hopefully correct category. [opensuse-factory] There seems to be unresolvable statuses on all live cd builds [1] openSUSE:Factory:Live > Status Monitor Something broke ? The latest live kde cd [2] seem to be dated 05-Aug-2011 nothing after that. Thanks Glenn [1]https://build.opensuse.org/project/monitor?commit=Filter%3A&failed=1&unre… [2]http://download.opensuse.org/factory/iso/openSUSE-KDE-LiveCD-x86_64-Build… 05-Aug-2011 05:47 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

9 16

[opensuse-factory] Re: Systemd Service % specifiers in ExecStart
by Frederic Crozat 26 Aug '11

26 Aug '11

Le jeudi 25 août 2011 à 14:27 +0200, Dr. Werner Fink a écrit : > Hi, > > does anyone know how systemd.service(5): > > ExecStart= > [...] > Unless Type=forking is set, the process started via > this command line will be considered the main process > of the daemon. The command line accepts % specifiers > as described in systemd.unit(5). On top of that basic > environment variable substitution is supported, where > ${FOO} is replaced by the string value of the > environment variable of the same name. Also $FOO may > appear as separate word on the command line in which > case the variable is replaced by its value split at > whitespaces. Note that the first argument (i.e. the > binary to execute) may not be a variable, and must be > a literal and absolute path name. > > will work ... currently it does not and a > > systemctl show kdm(a)tty7.service > > will cause > > [...] > Type=forking > Restart=no > PIDFile=/var/run/kdm.pid > NotifyAccess=none > RestartUSec=100ms > TimeoutUSec=1min 30s > ExecStartPre={ path=/bin/echo ; argv[]=/bin/echo %p %P %I %n %N %f ; ignore=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/ } > ExecStart={ path=/usr/bin/%p ; argv[]=/usr/bin/%p ; ignore=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/ } > [...] > > also a > > systemctl start kdm(a)tty7.service According to upstream, you are not supposed to create path "on the fly" like this. And ExecStart is not started in a shell, so it doesn't expand everything like a shell. If %p and other don't work, please open a bugreport on https://bugs.freedesktop.org/ against systemd. -- Frederic Crozat <fcrozat(a)novell.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 14

[opensuse-factory] logger only working with strace?
by Stefan Seyfried 26 Aug '11

26 Aug '11

Hi all, this issue is so strange, that I'd first like to ask if someone else is also seeing this before filing a bug report :-) System: * pretty current FACTORY * running systemd * running rsyslogd Symptoms: * "logger foo" does nothing. No entry in /var/log/messages or anywhere * "strace logger foo" does work. * "echo foo > /dev/kmsg" also works as a workaround. anyone else seeing this? -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 7