July 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

Re: [opensuse-factory] repository priorities with Tumbleweed
by Thomas Langkamp 16 Jul '15

16 Jul '15

> No, please don't confuse people, if you add more repos than just > Tumbleweed you really had better know what you are doing or bad things > can, and will, happen :) I understand. I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed - between ## is the new stuff: "The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT support this ## " It would also be good to move this information to "Special concerns" and to move the whole "Special concerns"-section up. For example "Special Concerns Virtual Machines ... Third Party Drivers ... ## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the Tumbleweed-Standard repo. Everything else is not supported and might break the system ## " >You do know the legal reasons behind why packman is there, right? Yes. Then I do not whish you personaly to support Packman with TW - I understand now that this is not possible from your perspectivg. But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman. So I will ask the Packman-guys to do that... I hope this is possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;) thanks anyway :D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 18

[opensuse-factory] Export broken for KinfoCenter
by Roger Luedecke 30 Jan '15

30 Jan '15

Export button is greyed out no matter what. -- 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] New Package - libhal1-flash (re-enabling Flash-Player DRM content on Linux)
by Christopher Horler 13 Sep '14

13 Sep '14

Good afternoon! I've written and packaged a compatibility library for flash to enable playback of DRM content (this removes the dependency on the HAL package). I'd like to know what steps I can take to have the package considered for inclusion in openSUSE 12.3 and 13.1. Can I submit the package to devel:openSUSE:Factory, or is there another action I should be taking? Details of the bug and links to upstream are here (please briefly review): https://bugzilla.novell.com/show_bug.cgi?id=768562#c19 OBS location: https://build.opensuse.org/package/show?package=hal-flash&project=home%3Ach… I will maintain the package until such time that HTML5 Video content is a viable alternative or the Flash plugin is completely withdrawn. RPMs, debs... are all available on the build service. Three noteworthy points: - package naming (libhal1-flash) doesn't 100% align with the Shared Library Policy (I've suffixed -flash to make clear this is not a fully functional HAL layer and also to avoid naming conflicts as some distros seem to have a shared library package already named libhal1). - The packages depends on dbus and udisks. It seems to work find when udisks is launched on demand (as for openSUSE 12.3) - The flash-player package could have some kind of RPM dependency on this package to assist the user when looking in YaST (Install / Remove Software) / Package Manager. Chris -- 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] source_validator error: signature does not validate
by Kyrill Detinov 25 Aug '14

25 Aug '14

Hello. I can't build a package. Service source_validator failed. % osc build Run source service: /usr/lib/obs/service/format_spec_file --outdir /tmp/tmpVbBhay Run source service: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector.keyring gpg: enabled debug flags: memstat gpg: keyring `/tmp/check_if_valid_source_dir-NL8Ezs/.checkifvalidsourcedir-gpg-keyring' created gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: key 015475F5: public key "Jakub Wilk <jwilk(a)jwilk.net>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks gpg: enabled debug flags: memstat gpg: Signature made Mon Jun 24 22:36:51 2013 MSK using RSA key ID 015475F5 gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: Good signature from "Jakub Wilk <jwilk(a)jwilk.net>" gpg: aka "Jakub Wilk <jwilk(a)debian.org>" gpg: aka "Jakub Wilk <ubanus(a)users.sf.net>" random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks (E) signature /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector-0.11.1.tar.gz.asc does not validate Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i Source service run failed! As far as I can see, the signature is good. This also happens with another package (graphics/icoutils). What is the problem? -- WBR Kyrill

2 5

[opensuse-factory] libav and multimedia idea
by Tomáš Chvátal 14 May '14

14 May '14

Hello guys, I have created proof of concept libav library with disabled patented codecs in my home project [1]. This means that this library si up par with what we have in chromium and it should be legal to distribute. Apart from the library the repo contains vlc chromium and xbmc (built localy fails on obs, meh) which seems to run fine, just not to play almost anything ^_^. The possibility here is to include all the media players and stuff around it into openSUSE release, where one has to flip the switch in libav (see the spec file) and can build full-fledged-european-edition which can play our sweet movies. Let me know what you think about this plan and what would you use as base devel project for this. Cheers Tom [1] https://build.opensuse.org/project/show?project=home%3Ascarabeus_iv

8 11

[opensuse-factory] YaST2 "install/remove" doesn't display solver diagram
by Kyrill Detinov 13 Jan '14

13 Jan '14

Hello. There is a regression in YaST2 *Qt* "install/remove software" module. It doesn't show solver diagram. First, no dependencies on libqdialogsolver. Second, installed libqdialogsolver doesn't help. Reported ages ago. And confirmed. All the info is provided. https://bugzilla.novell.com/show_bug.cgi?id=785431 WBR Kyrill

3 3

Re: [opensuse-factory] Nothing provides /usr/bin/php5
by Sascha Peilicke 11 Jan '14

11 Jan '14

On 12/01/2011 11:44 AM, Kyrill Detinov wrote: > > Hello. > > We have one package affected in standard repo: leechcraft-eiskaltdcpp. > The program itself doesn't require php5. But the package includes > example scripts with shebang '!/usr/bin/php5'. So the package isn't > installable. > > Also I see the same problem with pgfouine from Contrib (written in > PHP) and eiskaltdcpp from filesharing repo. Maybe more in third-party > repositories. > > Can we have symlink /usr/bin/php -> php5 in php5 package? Or affected > packages should be fixed? > Please file a bug against php5 and assign to Cristian Rodríguez. -- Viele Grüße, Sascha -- 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] SOLVED: postfix does not run
by Christian Boltz 06 Nov '13

06 Nov '13

Hello, Am Freitag, 22. März 2013 schrieb Patrick Shanahan: > /etc/postfix/main.cf had @_some-parameter_@ setting for every > "xxxxxxx_directory =" line. > > After correcting "xxxxxxxx_directory =" settings per my Tumbleweed > machine, postfix appears working correctly. > > This mess probably occurred on installing/upgrading postfix: > postfix-2.9.6-2.1.x86_64 Sun Mar 10 11:14:39 2013 > but the rpm main.cf does not contain "@.............@". This sounds like https://bugzilla.novell.com/show_bug.cgi?id=796162 which should be fixed since some time. I'd guess some older postfix package broke your main.cf. Nevertheless, if you want to be really sure, uninstall postfix, move away /etc/postfix and re-install the postfix package. Regards, Christian Boltz -- Argh, ich wollte heute doch gar nicht mehr siggen! [Michael Hoffmann in dag°] -- 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] Warning: new systemd version landing in Factory
by Frederic Crozat 20 Sep '13

20 Sep '13

Hi all, systemd v202 should be landed in Factory soon. It contains a lot of changes (and bug fixes) compared to v195 we had in 12.3, like (this is an extract from the .changes I wrote): + udev now supports different naming policies for network interface for predictable names (this one is disabled by /usr/lib/tmpfiles.d/network.conf until network team had a chance to look at it and test it). This should be enabled by default in Factory soon (see http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac… ) This can be also be turned off with kernel command line switch: net.ifnames=0 (when the tmpfiles.d is removed in the near future) + udev gained support for loading additional device properties from an indexed database. %udev_hwdb_update macro should be used by packages adding entries to this database. + Journal gained support for "Message Catalog", indexed database to link up additional information with journal entries. %journal_catalog_update macro should be used by packages adding %entries to this database. + New rpm macros has been added: %udev_rules_update(), %_udevhwdbdir, %_udevrulesdir, %_journalcatalogdir, %_tmpfilesdir, %_sysctldir. + "age" field for tmpfiles entries can be set to 0, forcing removal of files matching this entry. + coredumpctl gained "gdb" verb to invoke gdb on selected coredump. + In service files, %U can be used for configured user name of the service. + nspawn can be invoked without a controlling TTY. + systemd and nspawn can accept socket file descriptors when started for socket activation. This allow socket activated nspawn containers. + logind can now automatically suspend/hibernate/shutdown system on idle. + ConditionACPower can be used in unit file to detect if AC power source is connected or if system is on battery power. + EnvironmentFile= in unit files supports file globbing. + Behaviour of PrivateTmp=, ReadWriteDirectories=, ReadOnlyDirectories= and InaccessibleDirectories= has changed. The private /tmp and /var/tmp directories are now shared by all processes of a service (which means ExecStartPre= may now leave data in /tmp that ExecStart= of the same service can still access). When a service is stopped its temporary directories are immediately deleted (normal clean-up with tmpfiles is still done in addition to this though). + Resource limits (as exposed by cgroup controlers) can be controlled dynamically at runtime for all units, using "systemctl set-cgroup-attr foobar.server cgroup.attribute value". Those settings are stored persistenly on disk. + systemd-vconsole-setup will now copy all fonts settings to all allocated VTs. + timedated now exposes CanNTP property to indicate if a local NTP service is available. + pstore file system is mounted by default, if available. + SMACK policies are loaded at early boot, if available. + Timer units now support calendar time events. + systemd-detect-virt detect xen PVs. + Some distributions specific LSB targets has been dropped: $x-display-manager, $mail-transfer-agent, $mail-transport-agent, $mail-transfer-agent, $smtp, $null. As well mail-transfer-agent.target and syslog.target has been removed. + systemd-journal-gatewayd gained SSL support and now runs as unprivileged user/group "systemd-journal-gateway:systemd-journal-gateway" + systemd-analyze will read, when available, boot time performance from EFI variable from boot loader supporting it. + A new generator for automatically mounting EFI System Partition (ESP) to /boot (if empty and no other file system has been configured in fstab for it). + logind will now send out PrepareForSleep(false) out unconditionally, after coming back from suspend. + tmpfiles gained a new "X" line type, that allows configuration of files and directories (with wildcards) that shall be excluded from automatic cleanup ("aging"). + udev default rules set the device node permissions now only at "add" events, and do not change them any longer with a later "change" event. + A new bootctl tool has been added that is an interface for certain EFI boot loader operations. + A new tool kernel-install has been added to install kernel images according to Boot Loader Specification. + A new tool systemd-activate can be used to test socket activation. + A new group "systemd-journal" is now owning journal files, replacing "adm" group. + journalctl gained "--reverse" to show output in reverse order, "--pager-end" to jump at the end of the journal in the pager (only less is supported) and "--user-unit" to filter for user units. + New unit files has been addedto ease for systemd usage in initrd. + "systemctl start" now supports "--irreversible" to queue operations which can be reserved. It is now used to make shutdown requests more robust. + Auke Kok's bootchart has been merged and relicensed to LGPLv2.1+. + nss-myhostname has been merged in systemd codebase. + some defaults sysctl values are now set by default: the safe sysrq options are turned on, IP route verification is turned on, and source routing disabled. The recently added hardlink and softlink protection of the kernel is turned on. + journald will now explicitly flush journal files to disk at the latest 5 min after each write and will mark file offline until next read. This should increase reliability in case of crash. + remote-fs-setup.target target has been added to pull in specific services when at least one remote file system is to be mounted. + timers.target and paths.target have been added as canonical targets to pull user timer and path units, similar to sockets.targets. + udev daemon now sets default number of worker processes in parallel based on number of CPUs instead of RAM. + Most unit file settings which takes likst of items can now be reset by assigning empty string to them, using drop-in. + Add support for drop-in configuration file for units. + Most unit file settings which takes likst of items can now be reset by assigning empty string to them, using drop-in. + 'hostnamectl set-hostname' allows setting FQDN hostnames. + fractional time intervals are now parsed properly. + localectl can list available X11 keymaps. + systemd-analyze dot can filter for specific units and has been rewritten in C. + systemctl gained "list-dependencies" command. + Inhibitors are now honored no only in GNOME. + 'systemctl list-jobs' got some polishing. '--type=' argument may now be passed more than once. 'systemctl list-sockets' has been added. + systemd gained a new unit 'systemd-static-nodes.service' that generates static device nodes earlier during boot, and can run in conjunction with udev. + systemd-nspawn now places all containers in the new /machine top-level cgroup directory in the name=systemd hierarchy. + bootchart can now store its data in the journal. + journactl can now take multiple --unit= and --user-unit= switches. + The cryptsetup logic now understands the "luks.key=" kernel command line switch. If a configured key file is missing, it will fallback to prompting the user. -- 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

10 31

[opensuse-factory] /boot partition is too small when you selected "Create LVM Based Proposal"in "Suggested Partitioning" on installer .
by 1xx 15 Sep '13

15 Sep '13

Hi all . When I selected "Create LVM Based Proposal" in "Suggested Partitioning" on installer, Installer suggested "Create boot volume /dev/sda1 (156.88 MB)" . But it is too small for for updating the kernel . The present state is as follows. Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 154691 108188 38516 74% /boot rpm -qa 'kernel-desktop' kernel-desktop-3.7.10-1.16.1.x86_64 kernel-desktop-3.7.10-1.11.1.x86_64 Disk storage capacity runs short in update of the next kernel . In the past, disk storage capacity actually ran short by update of the kernel . I think that the /boot partition should be more than 256 M byte required. (ex: 1 G byte) I wrote https://bugzilla.novell.com/show_bug.cgi?id=826981 . I want you to tell your opinions . -- 1xx <ItSANgo(a)gmail.com> <https://twitter.com/ItSANgo> <http://d.hatena.ne.jp/Itisango/> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

23 47

[opensuse-factory] openqa/factory lamp testing question
by doiggl＠velocitynet.com.au 19 Aug '13

19 Aug '13

Hello, I have a openqa/factory question:Perhaps for Bernhard. Can a test LAMP[1] be included in the openqa tests,to test the lamp software stack works with some software which uses all these components, see example see[2], The install output listed at[3] I have not tested the configuration settings yet as I have not been able to get apache2 part going yet. Thanks Glenn [1] definition Linux (operating system), Apache HTTP Server, MySQL (database software), and PHP, Perl or Python http://en.wikipedia.org/wiki/LAMP_%28software_bundle%29 [2] LAMP_setup and software setup - http://en.opensuse.org/SDB:LAMP_setup - http://en.opensuse.org/Cacti changed/updated instructions to suit newer version of cacti. zypper ar http://download.opensuse.org/repositories/server:/monitoring/openSUSE_Facto… server:monitoring zypper in cacti cacti-plugin-autom8 cacti-plugin-boost cacti-plugin-clog cacti-plugin-cycle cacti-plugin-discovery cacti-plugin-docs cacti-plugin-flowview cacti-plugin-hostinfo cacti-plugin-loginmod cacti-plugin-mactrack cacti-plugin-monitor cacti-plugin-npc cacti-plugin-ntop cacti-plugin-realtime cacti-plugin-routerconfigs cacti-plugin-settings cacti-plugin-ssl cacti-plugin-syslog cacti-plugin-thold cacti-plugin-tools cacti-plugin-update cacti-plugin-weathermap [3] install output Loading repository data.. Reading installed packages.. Resolving package dependencies.. The following NEW packages are going to be installed: cacti cacti-plugin-autom8 cacti-plugin-boost cacti-plugin-clog cacti-plugin-cycle cacti-plugin-discovery cacti-plugin-docs cacti-plugin-flowview cacti-plugin-hostinfo cacti-plugin-loginmod cacti-plugin-mactrack cacti-plugin-monitor cacti-plugin-npc cacti-plugin-ntop cacti-plugin-realtime cacti-plugin-routerconfigs cacti-plugin-settings cacti-plugin-ssl cacti-plugin-syslog cacti-plugin-thold cacti-plugin-tools cacti-plugin-update 22 new packages to install. Overall download size: 7.7 MiB. After the operation, additional 22.5 MiB will be used. Continue? [y/n/?] (y): Retrieving package cacti-0.8.8a-14.2.noarch Installing: cacti-plugin-boost-5.1-2.3 ............................................................[done] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 14

[opensuse-factory] Qt5 and openSUSE
by Luca Beltrame 11 Aug '13

11 Aug '13

Hello, Qt 5.0 was released quite a while ago: the currently available version is Qt 5.1, with 5.2 on the horizon. In parallel, KDE Frameworks 5 development (KF5) has been slowly picking up steam. Given that: - Qt5 is incompatible with Qt4; - KF5 won't be released for a while; - Qt5 programs are also starting to appear; - We cannot overwrite people's installed Qt4; it would be very wise to have Qt5 co-installable with Qt4. It's not like people have been idle: shumski made quite an effort to make Qt5 coinstallable with Qt4, and made a SR (#182437) which, up to this day, for more than a month, was not reviewed yet. Then I see Kubuntu offering a way for people to develop Qt5 and KF5 with its Project Neon 5 effort[1], and since oS has the OBS, it would be a prime chance of taking advantage of that. While discussion on this specfic topic is off-topic for the Factory ML, the basic pre-requisite is to have co- installable Qt5 packages. Since that aside from the aforementioned SR the movement has been pretty much non existent, there are some questions: - What can be done to solve the impasse? - How can additional contributors help with this effort? This problem is going to bite us anyway in a number of months, so the sooner it is faced, the better. [1] http://blogs.kde.org/2013/07/31/project-neon-5-daily-builds-ubiquity-wirele… -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 11

[opensuse-factory] On kmod-compat replacing m-i-t
by Jan Engelhardt 08 Aug '13

08 Aug '13

Currently, the only package that still blocks the removal of module-init-tools from a system is the kernel rpm package, with an express dependency "module-init-tools >= 3.4". What is so particular about m-i-t 3.4? Can it be replaced by modutils, or do we need to add some virtual Provides: mitmagic34 to both module-init-tools.spec and kmod-compat.spec? -- 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] unify ca-certificates installations
by Ruediger Meier 05 Aug '13

05 Aug '13

Hi, today I wanted to install globally a custom ca-certificate (actually just the ca-certificates-cacert rpm package). I found that it's a bit annoying that this is not easily possible since different programs are using different paths to look for ca certificates and we have a lot duplicated certs installed For example we have some packages giving us some certificates ca-certificates-mozilla: /usr/share/ca-certificates/mozilla/ kdelibs3: /opt/kde3/share/apps/kssl/ca-bundle.crt kdelibs4: /usr/share/kde4/apps/kssl/ca-bundle.crt (They all have more less the same content.) Then we have autogenerated bundle file and directory /etc/ssl/ca-bundle.pem /etc/ssl/certs/ which are generated from everything below /usr/share/ca-certificates/ and possibly some other paths. Many programs (like curl or wget) are using /etc/ssl/ to search for certificates. But to get firefox, kde4 and kde3 in sync I need to ln -sf /etc/ssl/ca-bundle.pem /opt/kde3/share/apps/kssl/ca-bundle.crt ln -sf /etc/ssl/ca-bundle.pem /usr/share/kde4/apps/kssl/ca-bundle.crt and somehow to teach firefox to use /etc/ssl/certs/ instead of /usr/share/ca-certificates/mozilla/. My question is, couldn't we do that per default? So that installing custom ca-certificates globally would affect hopefully all possible programs. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 19

[opensuse-factory] password behavior too nuts to file a bug - yet
by Felix Miata 03 Aug '13

03 Aug '13

I started to file the following as a bug, but seems like I must be missing something: Summary: passwordless and null password account logins rejected (KDE3 and vttys) Systems: both 12.3 & 13.1M2 on both i586 and x86_64 Comments: To reproduce: 1-install minimal X normally but without creating any regular user(s) 2-set grub cmdline(s) to include 3 parameter 3-set solver.onlyRequires=true in /etc/zypp.conf 4-install minimalist via zypper and set default KDM/KDE (3 and/or 4) 5-create group account (e.g. # groupadd -g 1999 mygroup) 6-create user account (e.g. # useradd -g 1999 -u 1999 myaccount) 7a-delete password (e.g. # passwd -d myaccount), or 7b-set password null (e.g. #passwd myaccount, <ENTER>, <ENTER>) 8-attempt to login with new user account (hostname login: myaccount)(in KDM or vtty) Actual results: 1a-(KDE) Login failed 1b-(vtty) Login incorrect 2-(vtty) login prompt refreshes Expected results: 1-(vtty) Last login XXX XXX ## ##:"##:## on ttyX 2-(vtty) Have a lot of fun... 3-(all KDE) login succeeds Comments: 1-applies also to 12.3 (local hosts gx150 & big41) 2-In pre-12.3 openSUSE versions, deleting password failed too, but setting password null worked. In Fedora 19 (as in previous versions) and Mageia 3 (as in previous versions, and Mandriva, and Mandrake), setting password null fails, but deleting password works. 3-IIRC (I need to verify if I can figure out which systems this applies to), 12.2 systems (at least those with sysvinit-init installed) for which users and null password(s) was/were set and which were upgraded to 12.3 via zypper continue to accept logins. 4-On 3 of the 4 installations, once KDM had been started after the users and passwords had been set and at least one reboot, this bug permanently disappeared, remaining only on host gx150 running 13.1 and KDE3. What am I missing? The gx150 13.1M2 system has krb5-1.11.3-2.1, pam-1.1.6-8.1 and xauth-1.0.7-5.2, and also repositories/KDE:/KDE3/openSUSE_Factory enabled. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] Fiddling with our development model
by Robert Schweikert 03 Aug '13

03 Aug '13

Hi all, This is NOT board intervention, this is just me ;) While at present things appear to be reasonably smooth sailing some (including me) think that there is trouble brewing. Thus, before things move into a more troublesome direction it is probably a good thing to think about changes that could avoid wreckage. Behind the "smooth sailing" appearance is a ton of work that is ever increasing and getting ever more complex. The current push model leads to problems we experience every time a new gcc version shows up, a bunch of stuff breaks and only 2 or 3 people fix things. While the use of staging projects "hides" the problems from Factory users, the problems remain the same. The work for the most part, ends up with the release team as they are the integrators. Partially the behavior of non release team members is understandable as for the most part getting your package build broken by others is annoying at best, and it generally happens at an inconvenient time. Partially the problem may also be that people plain and simply do not get the information about their package being broken in factory. With this as a short background I'd like to propose a change in development model for our beloved distribution. Everything needs a catchy title, thus I'll call it "Integration of independently released components with pull option", very catchy I know ;) . The idea is that we define components, this is going to be a chunk of work, and for each component we define it's dependencies. The component model is not set in stone and would get refined over time to reduce potential overlap and improve interoperability. A component is developed by a team and you can think of a component as a "mini factory replica" (factory as we know it today.) The component team works on releases of their component according to some common and some component specific guidelines we'd have to define and publish. Any component consists of one or more packages and may get fed by devel projects or development may take place in component branches. Each component advances based on it's own release cycle and the component team decides which release of it's dependent components to build against. Some tooling will be needed to help sort out the combinatorial problem. How does this work in more concrete terms? Lets say we have a "Core" component that includes the kernel, glibc, the toolchain and a few other things, but no fluff ;) . This component then gets released every time a new kernel is released and every time a new gcc or glibc are released, or based on some other criteria the core team determines and publishes. Every release gets a number. When a new release of the core component happens nothing breaks because by default nothing builds against the new release yet. Component teams higher up the stack decide against which release of a dependent component they want to build. This puts the "adopt a new toolchain" decision into the court of the component teams rather than having it in the realm of the release team, i.e. the integrators, or the realm of the toolchain team. Therefore, a component team decides on it's time scale when to build against a new release of a dependent component. This concept works whether a given component depends on one or many other components. Obviously there needs to be some notification mechanism that lets dependent component owners know when a new release of one of their dependent components is available. There also needs to be some tagging mechanism for releases and other mechanisms of notification and tracking. A simple example: Lets say component A depends on component B. Component A is released as version 1 (A-1) and component B is also released as version 1 (B-1). Now component team B decides to have release number 2 (B-2) and thus component team A gets notified. Component team A can now create a branch of component A and start building against B-2. If the changes to get A-1 to build against B-2 are trivial and A-1 can work with both B-1 and B-2, component team A merges the changes back from the branch and tags A-1 as working with B-1 and B-2. If the changes to A are extensive component team A may decide to have a new release, tag it as release 2 (A-2) and tag it to be working with B-1 and B-2 or only with B-2 if that is the case. These same principles apply for components with multiple dependencies, with the caveat that things get a bit more complex, still less cumbersome of course than the battles the release team has to fight day in and day out in today's model. This change does imply the end of factory as we know it today. Factory may be "empty" for a good chunk of the release cycle. The replacement for "living on the edge" developers is a set of component selections that can keep you in "alpha mode" all the time. When a release approaches,the release team picks a version of the core component that will be the base for the next openSUSE release. This version is used to populate factory and may be the only component that is in factory for a little while. As other component teams integrate and build against the version of their dependencies that end up in factory and make their own component releases the openSUSE release team can fill factory by pulling more and more per-integrated components. With things per-integrated at the released component level the work of the openSUSE release team becomes easier and sustainable. The underlying assumption is that component teams have an interest in having their component be part of the openSUSE release and thus component teams will have an interest in building against new releases of dependent components. This underlying assumption is not much different from today's. What do we gain from all of this? Interesting work of course ;) , but we also switch to a model that is sustainable in the long run. I am not the only one arguing that the work the release team is doing in its present form cannot be sustained with a growing distribution. The work has to be distributed in some way, and more people doing the same thing that is being done today is probably not the answer. We also gain a unique and interesting development model, that with some additional tooling will allow developers to generate a distribution that is tailored to exactly their need. This in turn should stir interest give us some nice publicity and help us find more fingers on the keyboard to help grow the developer community and with it the distribution. With the independent release of components one can easily imagine an interface where a developer picks a component at a given release level, gets choices of versions of dependent components to select and so on. In the end we can relatively easily generate a tailored "release". This also works the other way around, pick a released version of the core and the interface shows you other components that match this core and so on up the stack. Lots of work, yes, but in the long run we have to make some changes. Thus, the sooner we start the easier it will be. 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

24 70

[opensuse-factory] Intel video driver artifacts after resume with Tumbleweed kernel
by Ronan Arraes Jardim Chagas 02 Aug '13

02 Aug '13

Hi, I'm using OpenSUSE Tumbleweed with latest kernel (3.10.0-16.g3dcd746-desktop). After the last update, when I resume the computer from a hibernation, I see lots of artifacts on screen. Most of them disappear when the screen is redraw, but some are only fixed by restarting X. Is anyone having the same problem? Best regards, Ronan.

3 3

[opensuse-factory] Btrfs features
by Jeff Mahoney 02 Aug '13

02 Aug '13

Hi all - In another thread, someone posted about wanting an updated btrfsprogs (it's coming, as soon as I finish writing this email). He mentioned it in terms of wanting to try out the RAID5 code. One of the things that's made it possible for SUSE to support btrfs in our enterprise products is often overlooked in media reports and casual analysis: We limit the feature set we support. In SLE11 SP3, we actively limit the feature set without a mount option enabling access to those features. We don't enable compression or multi-volume file systems. So, the question is: Is this something we should consider for openSUSE as well? The goal isn't to ever deny users access to the available features or to force them to rebuild the kernel to enable them, but to shield unsuspecting users from features that may not be fully baked yet. For example, the RAID5 code in particular is still fairly fragile. -Jeff -- Jeff Mahoney SUSE Labs

6 9

[opensuse-factory] Contribute a new package to Factory
by GHui 02 Aug '13

02 Aug '13

Hi, I'm developing an open source program, it's named Paramon. I'm the beginner of the program. And I will upload the code to http://sourceforge.net/projects/openparamon. If I want to contribute the Paramon to SUSE distribution, what should I do? Any help will be appreciated. The following is the introduction of the Paramon. Paramon is a visual program for monitoring cpu used time, cpu sys+wa time, memory used rate, swap used rate, net send/recv MB per sec and disk read/write MB per sec. Paramon UI is dependents on Qt library. By this way, you can monitor the main performance (memory, cpu, disk, net) in visualization. And in future, it will monitor CPU microarch data, such as Gflops, CPI, LLCMiss, etc. Thanks, GHui

3 2

[opensuse-factory] Tumbleweed: Screensaver backlight doesn't power down
by Patrick Shanahan 31 Jul '13

31 Jul '13

openSUSE Tumbleweed display is SyncMaster 2433bw 1920x1200 95x93 60hz GeForce GTS 450/PCIe/SSE2 OpenGL version string: 4.3.0 NVIDIA 319.23 My screensaver appears to work as it should but the backlight on the screen never shuts down unless I shut off the power. Booting with a "live" disk, the screen works as expected, screensaver kicks in, and some time later, screen backlight will go off. xset reports: Screen Saver: prefer blanking: yes allow exposures: yes timeout: 0 cycle: 600 Colors: default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff DPMS (Energy Star): Standby: 360 Suspend: 540 Off: 720 DPMS is Enabled Monitor is On Suggestions? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] New Haskell packages for Factory
by Peter Trommler 31 Jul '13

31 Jul '13

Folks, As part of the upgrade to Haskell Platform 2013.2.0.0, which is the latest upstream, I will submit the following new packages to Factory: * ghc-GLURaw * ghc-OpenGLRaw * ghc-attoparsec * ghc-case-insensitive * ghc-hashable * ghc-unordered-containers See http://www.haskell.org/platform/changelog.html for details on Haskell Platform and updated package versions and new packages. Note: ghc-extensible-exceptions, which was built as part of ghc (the Haskell compiler), has been dropped from Haskell Platform. Some Haskell packages (not in Factory) need it. If you want it to remain in Factory, please let me know and I'll prepare a separate package. Note2: The packages implement the new Haskell packaging guidelines presented at opensuse-packaging and made effective as of today. Though spec files are a bit more verbose now they are more readable for our review team by not abstracting lots of things as macros. I will be the maintainer of those new Haskell Platform packages and keep maintaining Haskell Platform of course. I hope to get everything into Factory before M4! Cheers, Peter -- 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] Is openqa testing not keeping up with factory
by doiggl＠velocitynet.com.au 31 Jul '13

31 Jul '13

Hello, Is openqa testing not keeping up with factory ? Any way to speed up iso test reault ? -- Glenn - openqa is testing openSUSE_Factory NET x86_64 0625 - openSUSE_Factory is at Build0630 - http://ftp5.gwdg.de/pub/opensuse/factory/iso/openSUSE-Factory-NET-x86_64-Bu… - http://openqa.opensuse.org/results/?sort=-mtime&hours=96&match=&ob= -- 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-security] CVE-2013-4854:bind critical security issue ??
by 1xx 31 Jul '13

31 Jul '13

Hi all . 2013/7/30 johann Luce <johann.luce(a)wanadoo.fr>: > > is there something declared about this > > https://kb.isc.org/article/AA-01015/0/CVE-2013-4854%3A-A-specially-crafted-… > > or is it already patched in the 9.9.2 p2??? I built BIND 9.9.2P2 package . http://software.opensuse.org/download.html?project=home%3AMitsutoshi%3Abran… http://software.opensuse.org/package/bind Would you review it ? And would you test it ? Please see also: http://lists.opensuse.org/archive/opensuse-ja/2013-07/msg00182.html . -- 1xx <ItSANgo(a)gmail.com> <https://twitter.com/ItSANgo> <http://d.hatena.ne.jp/Itisango/> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] Libreoffice 4 Tumbleweed - stuck on 3.6
by Trent Hawkins 31 Jul '13

31 Jul '13

Hi folks, I apologise if this is a well known issue. I did try searching for this but haven't unearthed anything. Yesterday i switched repos to Tumbleweed and "zypper dup"ed. I had expected to get Libreoffice 4 by doing this, but i found i am still on 3.6. I notice on OBS that there is indeed LO4 successfully built for Tumbleweed, but i can't tell if it is in the main TW repos. Its certainly not the end of the world for me if i don't get LO4. linux-cuq3:/home/trentos # zypper ref Repository 'Packman Tumbleweed' is up to date. Repository 'openSUSE Current non-oss' is up to date. Repository 'openSUSE non-oss Current updates' is up to date. Repository 'openSUSE Current oss' is up to date. Repository 'openSUSE Current updates' is up to date. Repository 'openSUSE Tumbleweed' is up to date. All repositories have been refreshed. linux-cuq3:/home/trentos # zypper up libreoffice Loading repository data... Reading installed packages... No update candidate for 'libreoffice-3.6.3.2.4-2.4.1.x86_64'. The highest available version is already installed. Resolving package dependencies... Nothing to do. Cheers, Trent -- 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] HDHomeRun package in Factory
by Kevin Adler 31 Jul '13

31 Jul '13

I'd like to add a few packages to openSUSE Factory: libhdhomerun, hdhomerun_config, and hdhomerun_config_gui. These packages contain a shared library, command line client, and gui for interacting with the HDHomeRun tuners built by Silicon Dust. The packages are updated fairly regularly (roughly twice a year) and are LGPL/GPL licensed. The benefit of including this software would be the ability to use the hardware, for example in an HTPC or the like. I am currently maintaining it in the hardware devel project, but would be open to suggestions for a different devel project for it. -- 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] new package perl-Sys-Virt for Factory
by Jim Fehlig 30 Jul '13

30 Jul '13

Hi, We've had the libvirt perl bindings in the Virtualization project for some time now and I'd like to submit this package to Factory. The bindings are used by various tools that will eventually be submitted to Factory as well, e.g. libguestfs, virt-v2v, etc. https://build.opensuse.org/package/show/Virtualization/perl-Sys-Virt Regards, Jim -- 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] Tumbleweed update today breaks vlc from packman
by Patrick Shanahan 30 Jul '13

30 Jul '13

09:58 Crash: ~ > vlc VLC media player 2.0.6 Twoflower (revision 2.0.6-0-gbe9623c) Segmentation fault 09:58 Crash: ~ > rpm -q --last vlc vlc-2.0.6-116.4.x86_64 Thu 25 Apr 2013 09:50:02 AM EDT ?? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 30

[opensuse-factory] Can libreoffice/factory be updated to version 4.1.0 from version 4.0.3
by doiggl＠velocitynet.com.au 29 Jul '13

29 Jul '13

Hello, Can libreoffice/factory[2] be updated to version 4.1.0 from version 4.0.3 perhaps copy from https://build.opensuse.org/package/show/LibreOffice:Unstable/libreoffice to https://build.opensuse.org/package/show/openSUSE:Factory/libreoffice libreoffice 4.1.0 builds ok in https://build.opensuse.org/package/show/LibreOffice:Unstable/libreoffice http://download.opensuse.org/repositories/LibreOffice:/Unstable/openSUSE_Fa… Bug report raised here [1]https://bugzilla.novell.com/show_bug.cgi?id=831837 [2]https://build.opensuse.org/package/show/openSUSE:Factory/libreoffice Cheers Glenn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6

[opensuse-factory] webkitgtk not build against the right icu
by Guido Berhoerster 28 Jul '13

28 Jul '13

X11:xfce/midori currently fails to build with: [ 99s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libwebkitgtk-1.0.so: undefined reference to `ucnv_toUnicode_51' [ 99s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libwebkitgtk-1.0.so: undefined reference to `UCNV_TO_U_CALLBACK_SUBSTITUTE_51' [ 99s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libwebkitgtk-1.0.so: undefined reference to `usearch_getMatchedLength_51' [ 99s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libjavascriptcoregtk-1.0.so: undefined reference to `ucol_setAttribute_51' [ 99s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libwebkitgtk-1.0.so: undefined reference to `ubrk_last_51' [ 99s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libwebkitgtk-1.0.so: undefined reference to `u_totitle_51' etc. So I guess webkitgtk hasn't been rebuilt against icu after the recent SONAME change? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] RPMlint crashes.
by Ilya Chernykh 28 Jul '13

28 Jul '13

I have a problem with rpnlint crashing at creating rpmlint report in this package: https://build.opensuse.org/package/live_build_log/KDE:KDE3/kfolding/openSUS… [ 159s] RPMLINT report: [ 159s] =============== [ 160s] Traceback (most recent call last): [ 160s] File "rpmlint.py", line 378, in <module> [ 160s] File "rpmlint.py", line 168, in main [ 160s] File "rpmlint.py", line 228, in runChecks [ 160s] File "AbstractCheck.py", line 83, in check [ 160s] File "MenuXDGCheck.py", line 43, in check_file [ 160s] File "/usr/lib/python2.7/ConfigParser.py", line 340, in get [ 160s] raise NoOptionError(option, section) [ 160s] ConfigParser.NoOptionError: No option 'Exec' in section: 'Desktop Entry' [ 160s] 0 packages and 0 specfiles checked; 0 errors, 4 warnings. What should I do? -- 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] Why wont mariadb [Factory] start
by doiggl＠velocitynet.com.au 27 Jul '13

27 Jul '13

Hello, Why wont mariadb [Factory]start. How can it be fixed/started ? So far I found/tried the following[1] Cheers Glenn [1] - sources used: http://ftp5.gwdg.de/pub/opensuse/repositories/server:/database/openSUSE_Fac… # rpm -qa | grep -i mariadb | sort mariadb-5.5.32-128.3.x86_64 mariadb-client-5.5.32-128.3.x86_64 mariadb-errormessages-5.5.32-128.3.x86_64 # rcmysql start redirecting to systemctl start mysql Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -n' for details. # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: failed (Result: exit-code) since Sat, 2013-07-27 21:14:03 EST; 1min 26s ago Process: 14739 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/mysql.service Jul 27 21:13:33 test.site mysql[14739]: Try 'chown --help' for more information. Jul 27 21:13:33 test.site mysql[14739]: /etc/init.d/mysql: line 334: :mysql: command not found Jul 27 21:13:33 test.site mysql[14739]: Will update MySQL now, if you encounter any problems, please read following file: Jul 27 21:13:33 test.site mysql[14739]: /usr/share/doc/packages/mariadb/README.SuSE Jul 27 21:13:33 test.site mysql[14739]: Running protected MySQL... Jul 27 21:14:03 test.site mysql[14739]: error: /var/tmp/mysql-protected.f6lOVv/mysql.sock file didn't appeared... Jul 27 21:14:03 test.site mysql[14739]: Try checking "/var/log/mysql/mysqld-upgrade-run.log"... Jul 27 21:14:03 test.site mysql[14739]: ..failed Jul 27 21:14:03 test.site systemd[1]: Failed to start LSB: Start the MySQL database server. Jul 27 21:14:03 test.site systemd[1]: Unit mysql.service entered failed state # journalctl -n -- Logs begin at Sat, 2013-07-27 15:11:36 EST, end at Sat, 2013-07-27 21:15:02 EST. -- Jul 27 21:13:33 test.site mysql[14739]: /usr/share/doc/packages/mariadb/README.SuSE Jul 27 21:13:33 test.site mysql[14739]: Running protected MySQL... Jul 27 21:14:03 test.site mysql[14739]: error: /var/tmp/mysql-protected.f6lOVv/mysql.sock file didn't appeared... Jul 27 21:14:03 test.site mysql[14739]: Try checking "/var/log/mysql/mysqld-upgrade-run.log"... Jul 27 21:14:03 test.site mysql[14739]: ..failed Jul 27 21:14:03 test.site systemd[1]: mysql.service: control process exited, code=exited status=1 Jul 27 21:14:03 test.site systemd[1]: Failed to start LSB: Start the MySQL database server. Jul 27 21:14:03 test.site systemd[1]: Unit mysql.service entered failed state Jul 27 21:15:02 test.site /usr/sbin/cron[15261]: pam_unix(crond:session): session opened for user root by (uid=0) Jul 27 21:15:02 test.site /USR/SBIN/CRON[15261]: pam_unix(crond:session): session closed for user root # Jul 27 21:13:33 test.site mysql[14739]: /etc/init.d/mysql: line 334: :mysql: command not found # head -334 /etc/init.d/mysql | tail -1 chown -R mysq;:mysql "$log_dir" # which mysql /usr/bin/mysql # mysql -V mysql Ver 15.1 Distrib 5.5.32-MariaDB, for Linux (x86_64) using readline 5.1 -- 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] Plan to add kdumpid to Factory
by Petr Tesarik 26 Jul '13

26 Jul '13

Hi, I'd like to add kdumpid to Factory (https://build.opensuse.org/package/show/Kernel:kdump/kdumpid). This small utility can read an unknown kernel core file and determine the kernel version from it. It is very useful in conjunction with the crash utility if you happen to have a core file and don't know from which kernel version it was generated. Comments welcome. If there are none, I will create a submit request tomorrow. Petr Tesarik -- 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] /usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libreoffice/program/libmergedlo.so : undefined symbol: _ZTIN8icu_51_222RuleBasedBreakIteratorE
by doiggl＠velocitynet.com.au 25 Jul '13

25 Jul '13

Hello, Anyone else get this error libreoffice/factory # libreoffice /usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libreoffice/program/libmergedlo.so: undefined symbol: _ZTIN8icu_51_222RuleBasedBreakIteratorE rpms installed: --Glenn # rpm -qa | grep -i libreoffice |sort libreoffice-4.0.3.3.5-46.2.x86_64 libreoffice-base-4.0.3.3.5-46.2.x86_64 libreoffice-base-drivers-mysql-4.0.3.3.5-46.2.x86_64 libreoffice-base-extensions-4.0.3.3.5-46.2.x86_64 libreoffice-branding-openSUSE-4.0-20.4.noarch libreoffice-calc-4.0.3.3.5-46.2.x86_64 libreoffice-calc-extensions-4.0.3.3.5-46.2.x86_64 libreoffice-draw-4.0.3.3.5-46.2.x86_64 libreoffice-draw-extensions-4.0.3.3.5-46.2.x86_64 libreoffice-filters-optional-4.0.3.3.5-46.2.x86_64 libreoffice-help-en-GB-4.0.3.3.5-46.2.noarch libreoffice-help-en-US-4.0.3.3.5-46.3.noarch libreoffice-hyphen-20110203.1-10.3.noarch libreoffice-icon-theme-crystal-4.0.3.3.5-46.1.noarch libreoffice-icon-theme-galaxy-4.0.3.3.5-46.1.noarch libreoffice-icon-theme-hicontrast-4.0.3.3.5-46.1.noarch libreoffice-icon-theme-oxygen-4.0.3.3.5-46.1.noarch libreoffice-icon-theme-tango-4.0.3.3.5-46.1.noarch libreoffice-impress-4.0.3.3.5-46.2.x86_64 libreoffice-impress-extensions-4.0.3.3.5-46.2.x86_64 libreoffice-kde-4.0.3.3.5-46.2.x86_64 libreoffice-kde4-4.0.3.3.5-46.2.x86_64 libreoffice-mailmerge-4.0.3.3.5-46.2.x86_64 libreoffice-math-4.0.3.3.5-46.2.x86_64 libreoffice-officebean-4.0.3.3.5-46.2.x86_64 libreoffice-openclipart-3.5-12.38.noarch libreoffice-pyuno-4.0.3.3.5-46.2.x86_64 libreoffice-templates-en-3.3-12.30.noarch libreoffice-templates-labels-a4-1.0.1-9.3.noarch libreoffice-templates-labels-letter-1.0.1-9.3.noarch libreoffice-templates-presentation-layouts-3.3-11.29.noarch libreoffice-thesaurus-en-US-20060111.1-19.4.noarch libreoffice-voikko-3.1.2-16.6.x86_64 libreoffice-writer-4.0.3.3.5-46.2.x86_64 libreoffice-writer-extensions-4.0.3.3.5-46.2.x86_64 -- 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] News for darktable users
by Togan Muftuoglu 24 Jul '13

24 Jul '13

Hi, For those using darktable package from either official openSUSE repos or factory, or from graphics repos, roughly a month ago, I have announced that the thumbnail compression will be removed. Now thanks to packman this option is back and all you have to is use the Multimedia repo and select darktable from packman. This version has the squish library enabled meaning thumbnails are compressed and smaller. Have fun Togan -- Life is endless possibilities -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] fvwm 2.6.4
by Dr. Werner Fink 24 Jul '13

24 Jul '13

On Thu, Jul 18, 2013 at 01:40:27PM +0200, Andreas.C.Klein(a)physik.uni-wuerzburg.de wrote: > -----"Dr. Werner Fink" <werner(a)suse.de> wrote: ----- > > >To: opensuse-factory(a)opensuse.org > >From: "Dr. Werner Fink" <werner(a)suse.de> > >Date: 2013-07-18 12:39 > >Subject: Re: [opensuse-factory] fvwm 2.6.4 > > > >On Thu, Jul 18, 2013 at 12:29:54PM +0200, Stephan Kulow > >wrote: > >> On 18.07.2013 12:16, > >Andreas.C.Klein(a)physik.uni-wuerzburg.de wrote: > >> > > >> > Hi all, > >> > > >> > I've just seen, that factory still has fvwm 2.6.4 which > >crashes on opensuse 12.2 and 12.3 x86_64. I downgraded fvwm > >to version 2.5.26 to prevent it from crashing. > >> > > >> OK, so if we have a fvwm that crashes for 2 releases, > >please file a > >> deleterequest - it's obviously unused and unmaintained. > > > >I'm using fvwm 2.6.4 and xterm and I do not have any > >crashes on 12.3 > >otherwise I would fix that. > > It only happens on x86_64. At least I and 3 colleagues have > exactly the same issue on their machines. We just installed > the fvwm from 12.1 on 12.3 and everything is fine on all 4 > machines. > There is also a newer version fvwm 2.6.5 which fixes a segfault > (http://permalink.gmane.org/gmane.linux.redhat.fedora.extras.cvs/891504), > but it seems to be triggered differently. I haven't tried that version, > since the rpm from opensuse 12.1 works perfectly on 12.3 > (just one addtional library is needed from 12.1). Just give home:WernerFink:branches:X11:windowmanagers/fvwm2 on build.opensuse.org a try ... this is 2.6.5 + parts of snapshot 2012/10/11 Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

2 2

[opensuse-factory] icu status
by šumski 23 Jul '13

23 Jul '13

Dear all, since couple of weeks we have a nice situation with invented icu so bump, which causes some warnings for users, and also uncovered some buid failures/buildsystem shortcomings. For Qt i have created sr#184115, but i'm not sure is this the best way to move forward. My question now is, will we stick with this invention, and patch the rest of the depending stack, or it's plan to revert to original, upstream behavior? Regards, Hrvoje -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: [opensuse-factory] Btrfs features
by Ulf 23 Jul '13

23 Jul '13

On Tue, Jul 23, 2013 at 4:33 PM, Jeff Mahoney <jeffm(a)suse.com> wrote: >So, the question is: Is this something we should consider for openSUSE >as well? The goal isn't to ever deny users access to the available >features or to force them to rebuild the kernel to enable them, but to >shield unsuspecting users from features that may not be fully baked yet. >For example, the RAID5 code in particular is still fairly fragile. >-Jeff Hi, SLES needs to be as stable as it can be, but openSUSE should provide a platform to test new things. You should not make the new and experimental features available through YaST, this way only users with more experience will use it. To be honest many bugs will only be found if somebody runs into the problem. In the case of btrfs you see a lot of warnings about the experimental status. Regards, Ulf -- 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] openSUSE 13.1 M3 update btrfsprogs to support RAID5
by Ulf 23 Jul '13

23 Jul '13

Hi, since Kernel 3.9 btrfs supports RAID5 (experimental). Unfortunately M3 ships with btrfsprogs 0.19, which do not support the RAID5 feature. I compiled btrfs-progs from git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git and created a RAID5 with the new version. Would it be possible to integrate a more recent version in openSUSE 13.1? Below you will find my short test: # ./mkfs.btrfs -f -d raid5 -m raid5 -L myRAID5 /dev/sdb1 /dev/sdc1 /dev/sdd1 WARNING! - Btrfs v0.20-rc1-358-g194aa4a IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using adding device /dev/sdc1 id 2 adding device /dev/sdd1 id 3 Setting RAID5/6 feature flag fs created label myRAID5 on /dev/sdb1 nodesize 4096 leafsize 4096 sectorsize 4096 size 24.00GB Btrfs v0.20-rc1-358-g194aa4a # mount /dev/sdb1 /mnt/ # df -h /mnt/ Filesystem Size Used Avail Use% Mounted on /dev/sdb1 24G 28K 20G 1% /mnt # ./btrfs filesystem df /mnt Data: total=8.00MB, used=0.00 Data, RAID5: total=2.00GB, used=0.00 System: total=4.00MB, used=0.00 System, RAID5: total=16.00MB, used=4.00KB Metadata: total=8.00MB, used=0.00 Metadata, RAID5: total=2.00GB, used=24.00KB # ./btrfs filesystem show /dev/sdb1 Label: 'myRAID5' uuid: 7a975562-c571-4a73-b617-a8c299e151cb Total devices 3 FS bytes used 28.00KB devid 3 size 8.00GB used 2.01GB path /dev/sdd1 devid 2 size 8.00GB used 2.01GB path /dev/sdc1 devid 1 size 8.00GB used 2.03GB path /dev/sdb1 Btrfs v0.20-rc1-358-g194aa4a Regards, Ulf -- 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] Keyserver problem
by Thomas Taylor 22 Jul '13

22 Jul '13

I'm having a problem trying to generate a new key set for email use. I can generate the key (attachment 2)but am unable to export it to a keyserver. When I try to export it returns a message "Couldn't export key" (attachment 1). I've tested this by changing ~/.gnupg/gpg.conf to use each of the entries one at a time with the same results. I will try rebooting into an older (12.3) stable version to see what it does later today. Any suggestions regarding what additional steps I could take? openSUSE 13.1-M3 KDE 4.10.90 Claws-Mail 3.9.2 Seahorse 3.9.1 Thanks, Tom -- Insight comes more often than not, from looking at what's been on the table all along. - David McCullough ^^ --... ...-- / -.- --. --... -.-. ..-. -.-. ^^^^ Tom Taylor - retired penguin - KG7CFC AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 openSUSE 12.3-x86_64 KDE 4.10.00, FF 19.0, claws-mail 3.9.1 registered linux user 263467

1 0

[opensuse-factory] two grub2 features
by Hans Witvliet 22 Jul '13

22 Jul '13

Obviously, using "new grub2 features" can not not be exploited anymore in 13.1. First feature is that with grub2, you are allowed to but "/boot" inside a LVM (not allowed by grub-legacy and hence not supported bay YaST-installer) Second feature is to have /boot within an encrypted LVM. Again, (not allowed by grub-legacy and hence not supported bay YaST-installer) Only unprotected parts are the grub2-images (core.img, etc) I presume it will have impact on the installer and YaST. It's another (small) step to make systems a little bit more secure. Perhaps something for 13.2 ? hw -- 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] openSUSE 13.1 M3 with YaST in Ruby
by David Majda 22 Jul '13

22 Jul '13

Hi, YCP Killer project here. We just published images of openSUSE 13.1 M3 with YaST in Ruby [*]. You can download them from here: http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/ (use the *.iso files with "Milestone3" in their names) If you have a bit of time, please help us test these. We are mainly interested to know whether everything in the installation and YaST itself works in the same way for you as in regular M3 (which still uses YCP-based YaST). See below for more info about the project, detailed instructions on downloading & running the DVDs, on reporting bugs, etc. This is the last testing release before planned integration of our work into M4 (see [1]). We will post more detailed plan regarding the integration shortly. YCP Killer Project ------------------ The goal of the YCP Killer project [2] is to rewrite YaST code written in YCP into Ruby, to make maintenance and feature development easier. The translation itself is done automatically using Y2R [3] -- a YCP to Ruby transpiler. We plan to finish the translation soon and integrate everything into openSUSE 13.1 M4. We created modified M2 and M3 builds as testbeds that allow others to help us with testing and exercising the translated code in various situations. Download Details ---------------- We have two installation images: * fullDVD -- basically the Milestone 3 DVD ISO * miniDVD -- just a subset of packages needed for "Minimal X" installation (other modes than "Minimal X" and "Minimal Text Mode" will fail) If possible, please use the fullDVD, as this is more similar to real-world openSUSE DVD. Note the images are available only for x86_64 to save OBS resources. Installation ------------ You need to manually add "insecure=1" boot option because the ISOs are not signed by the official openSUSE GPG key. You will also need to accept the OBS YaST:Head:ruby GPG key when adding the installation repository during installation. Known issues ------------ * Bootloader configuration fails when one tries to change it from the default. Reporting Bugs -------------- Please report any bugs as Github issues against the YCP Killer project: https://github.com/yast/ycp-killer/issues Bonus points for verifying that the bug doesn't occur in regular M3 (which means it isn't an upstream bug, but ours). If you are not sure whether something is a bug, or have any questions, feedback, etc., feel free to contact us via #yast channel on freenode or via yast-devel(a)opensuse.org. Happy testing :-) ----- [1] http://lists.opensuse.org/opensuse-factory/2013-05/msg00361.html [2] https://github.com/yast/ycp-killer [3] https://github.com/yast/y2r [*] The packages on the DVDs may not be *exactly* the versions found in M3, but they are close enough, as they were built in the same time period as M3. -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 5

[opensuse-factory] fvwm 2.6.4
by Andreas.C.Klein＠physik.uni-wuerzburg.de 22 Jul '13

22 Jul '13

Hi all, I've just seen, that factory still has fvwm 2.6.4 which crashes on opensuse 12.2 and 12.3 x86_64. I downgraded fvwm to version 2.5.26 to prevent it from crashing. How to reproduce: - Log in with fvwm 2.6.4 (64 bit) - open 10 xterms (it only works with xterms) - press ctrl+d to close the xterm. - typically the fourth closed xterm crashes fvwm with something like this: fvwm[1547]: segfault at 24793 ip 00007f306822a634 sp 00007fff3191caf8 error 4 in libc-2.17.so[7f30681ac000+1a3000] have a nice day, andreas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] zypper locking docs clear as mud
by Felix Miata 20 Jul '13

20 Jul '13

I've been using locks for years, but only for what I consider to be specific single packages. Man page, --help and Google all fail to describe in manner I can understand how to lock all packages containing a string. Is this the default? Is all I need to lock all kdebase4 packages simply 'zypper al kdebase4'? Or is it 'zypper al -t pattern kdebase4'? I've currently applied the latter (correct?), but I think the man page could use some clarification. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] broadcom-wl for m3/factory
by Alex Naumov 19 Jul '13

19 Jul '13

Hello, I'm testing oS 13.1 milestone 3 right now and can't find broadcom-wl package for 13.1[1]. Does anybody know where I can find it? Thanks, Alex [1] http://packman.inode.at/suse/openSUSE_Factory -- 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] Cannot connect to bugzilla
by Andrey Borzenkov 19 Jul '13

19 Jul '13

I cannot connect to bnc - I get recursive redirection. From both Firefox and Chrome and after removing all suse, novell and attachemate cookies. Anyone else? I'd really love to be able to work on bug reports ... :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] zypper in zypper requires deinstallation of gfxboot
by Felix Miata 19 Jul '13

19 Jul '13

What? How can this be? Attempting upgrade from M1 to factory-snapshot. Zypper in gfxboot wants to upgrade 54 packages. :-O Does gfxboot really depend on all of perl and most of yast2? Is this just a quirk caused by rubyfying Yast? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] openSUSE ARM under QEMU?
by Andrey Borzenkov 19 Jul '13

19 Jul '13

Is it possible to run one of images in QEMU? If yes, could someone point to simple howto for dummies? Thank you! -- 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] Cannot set resolution in installer unless KMS is disabled
by Andrey Borzenkov 18 Jul '13

18 Jul '13

Running installation in QEMU it selects some KMS driver by default and sets too huge resolution which exceeds physical screen size on my notebook. But I could not find anyway to actually request different resolution. Using F3 in installer is happily ignored (clear, it applies to legacy framebuffer only and we have new and shiny KMS today ...) but adding video=800x600 to command line is ignore as well. The only way is to add nomodeset, but this also disables KMS for installed system (yes, I know how to change it :) ). Is it possible to somehow influence resolution when using "native" driver? -- 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: [obs submit-request 183188] Base:System/mc: created by subchaser
by Brian K. White 17 Jul '13

17 Jul '13

Just so it doesn't look derelict, if no one else does I should get a chance to go over this sometime today or tomorrow. It looks ok but I want to verify the packaging changes (ie: not so much the upstream code changes) before accepting. Holy cow the new comments/discussion feature being developed for obs & webui sure will be welcome. It was probably more work and more time to manually assemble this email and cc list than it would have been to just do the review! And it still doesn't even do the job since I only mailed mc maintainers, not everyone who can see the SR and have the ability to accept/deny. -- bkw On 7/15/2013 6:14 PM, subchaser(a)mail.ru wrote: > > > home:subchaser:midnight-commander:latest/mc -> Base:System/mc > > > https://build.opensuse.org/request/show/183188 > > Description: Updated to latest released versions > > changes files: > -------------- > --- mc.changes > +++ mc.changes > @@ -1,0 +2,89 @@ > +Thu Jul 11 15:00:48 UTC 2013 - subchaser1(a)gmail.com > + > +- Update to 4.8.9 (latest released version) > + > +Major changes since 4.8.8 > +VFS > + extfs: support unrar-5 (#3015) > + extfs: use xorriso (if exists) for writing into ISO images (#3027) > + > +Editor > + Support unlimited file size (#1743) > + > +Misc > + Lot of code cleanups (#2990, #2071, #2164, #2998, #3003, #3005, #3022) > + Display additional info while viewing (by F3) *.iso files (#2006) > + New skins: > + modarin256: set of 256-color skins from Oliver Lange (#2737) > + > +Fixes > + Fail to link if system lib does not contain strverscmp (#2992) > + Segfault when mc's temporary directory doesn't belong to the correct user (#3021) > + Race condition when creating temporary directory (#3025) > + Mouse doesn't work in screen and tmux (#3011) > + Incorrect file size in copy/move overwrite query dialog (#3000) > + Garbage in subshell prompt (#3001) > + Incorrect WLabel redraw after text change (#2991) > + Find File: "All charsets" options don't work (#3026) > + When an unknown key is pressed, it is interpreted as garbage (#2988) > + Segfault on creating new file in external editor (#3020) > + Rotating dash is not removed when mc finishes reading the directory (#2163) > + mcedit: word completion failed if word to be completed is begun from begin of file (#2245) > + mcview: broken switch between raw and parse modes (#2968) > + Hex viewer: continue search doesn't work (#2706) > + sftpfs: broken SSH aliases (#2923) > + > +------------------------------------------------------------------- > +Thu Jun 27 07:42:44 UTC 2013 - subchaser1(a)gmail.com > + > +- Apply bugfixes from upstream version: > + * Incorrect file size in copy/move overwrite query dialog (#3000) > + * Incorrect WLabel redraw after text change (#2991) > + > +------------------------------------------------------------------- > +Tue Apr 2 19:46:19 UTC 2013 - subchaser1(a)gmail.com > + > +- Update to 4.8.8 (latest released version) > + > +Major changes since 4.8.7 > +Core > + Make copy/move progress dialog window wider up to 2/3 of screen width (#2076) > + Ask file name before create new file in editor (#2585) > + Support newer extended mouse protocol SGR-1006 instead of URXVT-1015 (#2956) > + Allow skip directory scanning before file operation. Print directory count and size in addition to directory name (#2101) > + Add jump support to target line in some external editors and viewers (#2206) > + > +Editor > + Update syntax highlighting: > + Jal programming language (#2855) > + gplink configuration files (.lkr extension) (#2855) > + Makefile with .mak extension (#2896) > + ZSH configuration files (#2950) > + Fortran (#2962) > + > +Misc > + Code cleanup (#2944, #2954) > + Report real compiler in MC_CHECK_ONE_CFLAG instead of 'gcc' > + Hints files now translated via Transifex (#2980) > + > +Fixes > + Segfault in file operation due to unhandled regexp error (#2493) > + Tab completion vs. spaces and escaping (#55)\ > + Special chars are not escaped in autocompletion of filenames (#2626) > + Buttons in the 'Directory hotlist' window are placed incorrectly (#2958) > + Mouse doesn't select text in subshell in native console (#2964) > + Mouse click below non-droppeddown menubar activates menu box (#2971) > + Insufficient quoting and wrong message in user menu (#2947) > + mcedit: floating point exception (division by zero) (#2953) > + mcedit: broken autocompletion (#2957) > + mcview: broken magic mode (#2976) > + Broken opening of .war archives (#2974) > + > +------------------------------------------------------------------- > +Sat Mar 9 09:06:35 UTC 2013 - subchaser1(a)gmail.com > + > +- Update to 4.8.7 (latest released version) > + The changes since 4.8.1.7 are to numerous to list here. > + Please see the file NEWS in the documentation for a complete list. > + > +------------------------------------------------------------------- > > old: > ---- > mc-4.8.1.7.tar.xz > mc-apps-mediainfo.patch > mc-apps-torrent.patch > mc-apps.patch > mc-extensions.patch > mc-palmsupport.patch > mc-word_docs.patch > mc-x11browser.diff > > new: > ---- > mc-4.8.9.tar.xz > mc-ext-audio.patch > mc-extd-doc.patch > mc-extd-misc.patch > mc-extd-sound.patch > mc-extd-video.patch > mc-extd-xdg.patch > > spec files: > ----------- > --- mc.spec > +++ mc.spec > @@ -21,9 +21,9 @@ > License: GPL-3.0+ > Group: Productivity/File utilities > Url: http://www.midnight-commander.org/ > -Version: 4.8.1.7 > +Version: 4.8.9 > Release: 0.0 > -Source: https://www.midnight-commander.org/downloads/mc-%{version}.tar.xz > +Source: http://ftp.midnight-commander.org/mc-%{version}.tar.xz > Source1: x11_browser > Source2: %{name}.desktop > Source3: %{name}.png > @@ -31,12 +31,12 @@ > Source5: mc-rpmlintrc > Patch18: mc-Syntax.cmake.patch > Patch0: mc-fix_lib_search_path.patch > -Patch6: mc-apps.patch > -Patch61: mc-apps-mediainfo.patch > -Patch62: mc-apps-torrent.patch > -Patch7: mc-palmsupport.patch > -Patch8: mc-word_docs.patch > -Patch9: mc-x11browser.diff > +Patch61: mc-extd-misc.patch > +Patch62: mc-extd-video.patch > +Patch63: mc-extd-doc.patch > +Patch64: mc-extd-sound.patch > +Patch69: mc-extd-xdg.patch > +Patch71: mc-ext-audio.patch > Patch12: mc-wrapper.patch > Patch16: mc-esc-seq.patch > Patch17: mc-rpm.patch > @@ -50,7 +50,6 @@ > # PATCH-FIX-UPSTREAM mc-multi-press-f-keys.patch mc287 sbrabec(a)suse.cz - Fixed Esc + Numeral F-key emulation. > Patch41: mc-multi-press-f-keys.patch > # Patches from Fedora > -Patch50: mc-extensions.patch > #Patch adding -fpie and -pie to compilation and linking of setuid binaries > Patch52: mc-pie.patch > > @@ -105,12 +104,12 @@ > %prep > %setup -q > %patch0 > -%patch6 > %patch61 > %patch62 > -%patch7 > -%patch8 > -%patch9 > +%patch63 > +%patch64 > +%patch69 > +%patch71 > %patch12 > %patch16 > %patch17 > @@ -121,13 +120,15 @@ > %patch31 > %patch32 > %patch41 > -%patch50 > %patch52 -p1 > > %build > autoreconf --force --install > %define warn_flags -W -Wall -Wstrict-prototypes -Wpointer-arith -Wformat-security -Wno-unused-parameter > export CFLAGS="$RPM_OPT_FLAGS %{warn_flags}" > + > +export X11_WWW="%{_datadir}/mc/x11_browser" > + > %configure \ > --localstatedir=/var/lib \ > --enable-charset \ > @@ -151,7 +152,9 @@ > %suse_update_desktop_file -i %name System FileManager > # Remove not supported language > rm -rf %{buildroot}%{_datadir}/locale/be@tarask > -%{find_lang} %{name} > + > +%find_lang %name > + > %fdupes -s %{buildroot}%{_prefix} > > %clean > @@ -168,20 +171,21 @@ > %doc ABOUT-NLS COPYING NEWS README > %config %{_sysconfdir}/profile.d/* > %{_bindir}/mc* > -%dir %{_sysconfdir}/mc > +%dir %{_sysconfdir}/mc/ > %config %{_sysconfdir}/mc/filehighlight.ini > %config %{_sysconfdir}/mc/sfs.ini > %config %{_sysconfdir}/mc/mc.menu > %config %{_sysconfdir}/mc/mc.ext > -%config %{_sysconfdir}/mc/mc.keymap.emacs > -%config %{_sysconfdir}/mc/edit.spell.rc > +###config #{_sysconfdir}/mc/edit.spell.rc > %config %{_sysconfdir}/mc/mcedit.menu > -%config %{_sysconfdir}/mc/mc.keymap.default > %config %{_sysconfdir}/mc/mc.keymap > +%config %{_sysconfdir}/mc/mc.default.keymap > +%config %{_sysconfdir}/mc/mc.emacs.keymap > %config %{_sysconfdir}/mc/edit.indent.rc > -%dir %{_libexecdir}/mc > +#(!)dir #{_libexecdir}/mc > %verify(not mode) %{_libexecdir}/mc/cons.saver > %{_mandir}/man1/* > +%exclude %{_mandir}/*/man1/* > %{_datadir}/mc > %{_datadir}/mc/syntax/Syntax > %{_datadir}/mc/mc.charsets > @@ -192,18 +196,26 @@ > %{_datadir}/mc/help/mc.hlp > %exclude %{_datadir}/mc/help/mc.hlp.* > %exclude %{_sysconfdir}/mc/mc.menu.* > +%exclude %{_datadir}/locale/*/LC_MESSAGES/mc.mo > + > %{_datadir}/applications/%{name}.desktop > %{_datadir}/pixmaps/%{name}.png > %exclude %{_sysconfdir}/mc/mc.menu.* > > -%files lang -f %{name}.lang > +%files lang -f %name.lang > %defattr(-, root, root) > -%lang(es) %doc %{_mandir}/es > -%lang(hu) %doc %{_mandir}/hu > -%lang(it) %doc %{_mandir}/it > -%lang(pl) %doc %{_mandir}/pl > -%lang(ru) %doc %{_mandir}/ru > -%lang(sr) %doc %{_mandir}/sr > +%lang(hu) %dir %{_mandir}/hu/ > +%lang(hu) %dir %{_mandir}/hu/man1/ > +%lang(hu) %{_mandir}/hu/man1/mc.1.gz > + > +%lang(pl) %dir %{_mandir}/pl/ > +%lang(pl) %dir %{_mandir}/pl/man1/ > +%lang(pl) %{_mandir}/pl/man1/mc.1.gz > + > +%lang(sr) %dir %{_mandir}/sr/ > +%lang(sr) %dir %{_mandir}/sr/man1/ > +%lang(sr) %{_mandir}/sr/man1/mc.1.gz > + > %lang(cs) %doc %{_datadir}/mc/*/mc.*.cs > %lang(es) %doc %{_datadir}/mc/*/mc.*.es > %lang(hu) %doc %{_datadir}/mc/*/mc.*.hu > > other changes: > -------------- > > ++++++ mc-4.8.1.7.tar.xz -> mc-4.8.9.tar.xz > (258118 lines skipped) > > ++++++ mc-Syntax.cmake.patch > --- mc-Syntax.cmake.patch > +++ mc-Syntax.cmake.patch > @@ -1,11 +1,8 @@ > --- misc/syntax/Syntax.in.orig 2012-12-28 12:47:48.000000000 +0400 > +++ misc/syntax/Syntax.in 2013-03-07 09:36:14.233306543 +0400 > -@@ -67,7 +67,7 @@ > - file (.\*[Mm]akefile[\\\.A-Za-z0-9]\*|..\*\\.mk|Kbuild)$ Makefile > - include makefile.syntax > +@@ -69,4 +69,4 @@ > > -file CMakeLists.txt$ CMake > +file (\/CMakeLists.txt|.cmake)$ CMake > include cmake.syntax > > - file ..\*\\.(pp|PP|pas|PAS|dpr|DPR|inc|INC)$ Pascal\sProgram > > ++++++ mc-esc-seq.patch > --- mc-esc-seq.patch > +++ mc-esc-seq.patch > @@ -1,13 +1,11 @@ > -Index: lib/util.c > -=================================================================== > ---- lib/util.c.orig 2010-07-05 21:12:51.000000000 +0200 > -+++ lib/util.c 2010-07-06 19:19:06.919536838 +0200 > -@@ -853,6 +853,8 @@ strip_ctrl_codes (char *s) > - /* strchr() matches trailing binary 0 */ > - while (*(++r) && strchr ("0123456789;?", *r)); > +--- lib/util.c.orig 2013-07-09 14:43:17.000000000 +0400 > ++++ lib/util.c 2013-07-11 18:48:01.258511499 +0400 > +@@ -745,6 +745,8 @@ > + while (*(++r) != '\0' && strchr ("0123456789;?", *r) != NULL) > + ; > } > + else if (*r == '(') > -+ r++; > ++ r++; > else if (*r == ']') > { > /* > > ++++++ mc-ext-audio.patch (new) > --- mc-ext-audio.patch > +++ mc-ext-audio.patch > @@ -0,0 +1,47 @@ > +--- misc/mc.ext.in.orig 2012-12-11 01:04:32.000000000 +0400 > ++++ misc/mc.ext.in 2013-03-10 10:59:02.741159661 +0400 > +@@ -433,16 +433,19 @@ > + ### Sound files ### > + > + regex/i/\.(wav|snd|voc|au|smp|aiff|snd|m4a|ape|aac|wv)$ > +- Open=@EXTHELPERSDIR@/sound.sh open common > ++ Include=audio > + > + regex/i/\.(mod|s3m|xm|it|mtm|669|stm|ult|far)$ > + Open=@EXTHELPERSDIR@/sound.sh open mod > ++ View=%view{ascii} @EXTHELPERSDIR@/sound.sh view mod > + > + shell/i/.waw22 > + Open=@EXTHELPERSDIR@/sound.sh open wav22 > ++ View=%view{ascii} @EXTHELPERSDIR@/sound.sh view wav22 > + > + shell/i/.mp3 > + Open=@EXTHELPERSDIR@/sound.sh open mp3 > ++ Include=audio > + View=%view{ascii} @EXTHELPERSDIR@/sound.sh view mp3 > + > + regex/i/\.og[gax]$ > +@@ -450,15 +453,22 @@ > + View=%view{ascii} @EXTHELPERSDIR@/sound.sh view ogg > + > + regex/i/\.(spx|flac)$ > +- Open=@EXTHELPERSDIR@/sound.sh open common > ++ Include=audio > + > + regex/i/\.(midi?|rmid?)$ > + Open=@EXTHELPERSDIR@/sound.sh open midi > ++ View=%view{ascii} @EXTHELPERSDIR@/sound.sh view midi > + > + shell/i/.wma > + Open=@EXTHELPERSDIR@/sound.sh open wma > + View=%view{ascii} @EXTHELPERSDIR@/sound.sh view wma > + > ++shell/i/.mka > ++ Include=audio > ++ > ++include/audio > ++ Open=@EXTHELPERSDIR@/sound.sh open common > ++ View=%view{ascii} @EXTHELPERSDIR@/sound.sh view common > + > + ### Play lists ### > + > > ++++++ mc-extd-doc.patch (new) > --- mc-extd-doc.patch > +++ mc-extd-doc.patch > @@ -0,0 +1,16 @@ > +--- misc/ext.d/doc.sh.in.orig 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/doc.sh.in 2013-03-10 08:03:31.889494487 +0400 > +@@ -50,3 +50,3 @@ > + msdoc) > +- which wvHtml >/dev/null 2>&1 && > ++ which wvHtml >/dev/null 2>&1 && which elinks >/dev/null 2>&1 && > + { > +@@ -57,2 +57,3 @@ > + } || \ > ++ wvText "${MC_EXT_FILENAME}" - || \ > + antiword -t "${MC_EXT_FILENAME}" || \ > +@@ -63,3 +64,3 @@ > + msxls) > +- which xlHtml >/dev/null 2>&1 && { > ++ which xlHtml >/dev/null 2>&1 && which elinks >/dev/null 2>&1 && { > + tmp=`mktemp -d ${TMPDIR:-/tmp}/%p.XXXXXX` > > ++++++ mc-extd-misc.patch (new) > --- mc-extd-misc.patch > +++ mc-extd-misc.patch > @@ -0,0 +1,13 @@ > +--- misc/ext.d/misc.sh.in.orig 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/misc.sh.in 2013-03-09 12:10:56.696615817 +0400 > +@@ -47,3 +47,9 @@ > + torrent) > +- ctorrent -x "${MC_EXT_FILENAME}" 2>/dev/null > ++ if type -p ctorrent >/dev/null 2>&1 ; then > ++ ctorrent -x "${MC_EXT_FILENAME}" 2>/dev/null > ++ elif type -p transmission-show >/dev/null 2>&1 ; then > ++ transmission-show "${MC_EXT_FILENAME}" > ++ else > ++ file "${MC_EXT_FILENAME}" > ++ fi > + ;; > > ++++++ mc-extd-sound.patch (new) > --- mc-extd-sound.patch > +++ mc-extd-sound.patch > @@ -0,0 +1,56 @@ > +--- misc/ext.d/sound.sh.orig 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/sound.sh 2013-03-10 11:54:01.186301679 +0400 > +@@ -6,27 +6,46 @@ > + action=$1 > + filetype=$2 > + > +-[ -n "${MC_XDG_OPEN}" ] || MC_XDG_OPEN="xdg-open" > ++[ -n "${MC_XDG_OPEN}" ] || MC_XDG_OPEN="_xdg_open" > ++ > ++_xdg_open() > ++{ > ++ if [ -n "$DISPLAY" ] && type -p gmplayer ; then > ++ gmplayer "${MC_EXT_FILENAME}" > ++ elif type -p mplayer ; then > ++ mplayer "${MC_EXT_FILENAME}" > ++ else > ++ xdg-open "${MC_EXT_FILENAME}" > ++ fi > ++} > + > + do_view_action() { > + filetype=$1 > + > ++ if type -p mediainfo >/dev/null 2>&1 ; then > ++ mediainfo "${MC_EXT_FILENAME}" > ++ return $? > ++ fi > ++ > + case "${filetype}" in > + mp3) > +- mpg123 -vtn1 "${MC_EXT_FILENAME}" 2>&1 | \ > +- sed -n '/^Title/,/^Comment/p;/^MPEG/,/^Audio/p' > ++ if type -p mpg123 ; then > ++ mpg123 -vtn1 "${MC_EXT_FILENAME}" 2>&1 | \ > ++ sed -n '/^Title/,/^Comment/p;/^MPEG/,/^Audio/p' > ++ return 0 > ++ fi > + ;; > + ogg) > +- ogginfo "${MC_EXT_FILENAME}" > ++ type -p ogginfo && ogginfo "${MC_EXT_FILENAME}" && return 0 > + ;; > + wma) > + mplayer -quiet -slave -frames 0 -vo null -ao null -identify "${MC_EXT_FILENAME}" 2>/dev/null | \ > + tail +13 || file "${MC_EXT_FILENAME}" > +- ;; > +- *) > +- cat "${MC_EXT_FILENAME}" > ++ return $? > + ;; > + esac > ++ > ++ mplayer -identify -vo null -ao null -frames 0 "${MC_EXT_FILENAME}" 2>&1 | sed -n '/^ID_/p' > + } > + > + do_open_action() { > > ++++++ mc-extd-video.patch (new) > --- mc-extd-video.patch > +++ mc-extd-video.patch > @@ -0,0 +1,39 @@ > +--- misc/ext.d/video.sh.orig 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/video.sh 2013-03-09 12:29:54.845011661 +0400 > +@@ -6,7 +6,18 @@ > + action=$1 > + filetype=$2 > + > +-[ -n "${MC_XDG_OPEN}" ] || MC_XDG_OPEN="xdg-open" > ++[ -n "${MC_XDG_OPEN}" ] || MC_XDG_OPEN="_xdg_open" > ++ > ++_xdg_open() > ++{ > ++ if [ -n "$DISPLAY" ] && type -p gmplayer ; then > ++ gmplayer "${MC_EXT_FILENAME}" > ++ elif type -p mplayer ; then > ++ mplayer "${MC_EXT_FILENAME}" > ++ else > ++ xdg-open "${MC_EXT_FILENAME}" > ++ fi > ++} > + > + do_view_action() { > + filetype=$1 > +@@ -13,8 +13,14 @@ > + > + case "${filetype}" in > + *) > +- mplayer -identify -vo null -ao null -frames 0 "${MC_EXT_FILENAME}" 2>&1 | \ > +- sed -n 's/^ID_//p' > ++ if type -p mediainfo >/dev/null 2>&1 ; then > ++ mediainfo "${MC_EXT_FILENAME}" > ++ elif type -p mplayer >/dev/null 2>&1 ; then > ++ mplayer -identify -vo null -ao null -frames 0 "${MC_EXT_FILENAME}" 2>&1 | \ > ++ sed -n 's/^ID_//p' > ++ else > ++ file "${MC_EXT_FILENAME}" > ++ fi > + ;; > + esac > + } > > ++++++ mc-extd-xdg.patch (new) > --- mc-extd-xdg.patch > +++ mc-extd-xdg.patch > @@ -0,0 +1,72 @@ > +diff -ru1 misc/ext.d.orig/archive.sh misc/ext.d/archive.sh > +--- misc/ext.d.orig/archive.sh 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/archive.sh 2013-03-10 09:01:31.154705008 +0400 > +@@ -145,3 +145,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" "${pager}" > +diff -ru1 misc/ext.d.orig/doc.sh.in misc/ext.d/doc.sh.in > +--- misc/ext.d.orig/doc.sh.in 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/doc.sh.in 2013-03-10 09:01:48.230710602 +0400 > +@@ -189,3 +189,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" > +diff -ru1 misc/ext.d.orig/image.sh misc/ext.d/image.sh > +--- misc/ext.d.orig/image.sh 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/image.sh 2013-03-10 09:02:00.086714848 +0400 > +@@ -56,3 +56,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" > +diff -ru1 misc/ext.d.orig/misc.sh.in misc/ext.d/misc.sh.in > +--- misc/ext.d.orig/misc.sh.in 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/misc.sh.in 2013-03-10 09:02:13.470718625 +0400 > +@@ -90,3 +90,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" > +diff -ru1 misc/ext.d.orig/package.sh misc/ext.d/package.sh > +--- misc/ext.d.orig/package.sh 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/package.sh 2013-03-10 09:02:23.630723087 +0400 > +@@ -53,3 +53,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" > +diff -ru1 misc/ext.d.orig/sound.sh misc/ext.d/sound.sh > +--- misc/ext.d.orig/sound.sh 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/sound.sh 2013-03-10 09:02:31.222725342 +0400 > +@@ -86,3 +86,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" > +diff -ru1 misc/ext.d.orig/text.sh.in misc/ext.d/text.sh.in > +--- misc/ext.d.orig/text.sh.in 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/text.sh.in 2013-03-10 09:02:39.018727707 +0400 > +@@ -135,3 +135,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" "${pager}" > +diff -ru1 misc/ext.d.orig/video.sh misc/ext.d/video.sh > +--- misc/ext.d.orig/video.sh 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/video.sh 2013-03-10 09:02:48.414731630 +0400 > +@@ -45,3 +45,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" > +diff -ru1 misc/ext.d.orig/web.sh.in misc/ext.d/web.sh.in > +--- misc/ext.d.orig/web.sh.in 2012-12-27 12:13:20.000000000 +0400 > ++++ misc/ext.d/web.sh.in 2013-03-10 09:02:56.670734093 +0400 > +@@ -48,3 +48,3 @@ > + open) > +- "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > ++ [ -n "$DISPLAY" ] && "${MC_XDG_OPEN}" "${MC_EXT_FILENAME}" 2>/dev/null || \ > + do_open_action "${filetype}" > > ++++++ mc-multi-press-f-keys.patch > --- mc-multi-press-f-keys.patch > +++ mc-multi-press-f-keys.patch > @@ -34,15 +34,15 @@ > if (!mc_global.tty.alternate_plus_minus) > switch (c) > { > -@@ -1724,7 +1737,7 @@ get_key_code (int no_delay) > - { > - /* Convert escape-digits to F-keys */ > - if (g_ascii_isdigit (c)) > -- c = KEY_F (c - '0'); > -+ c = KEY_F_IMMUTABLE (c - '0'); > - else if (c == ' ') > - c = ESC_CHAR; > - else > +@@ -1928,7 +1928,7 @@ get_key_code (int no_delay) > + { > + /* Convert escape-digits to F-keys */ > + if (g_ascii_isdigit (c)) > +- c = KEY_F (c - '0'); > ++ c = KEY_F_IMMUTABLE (c - '0'); > + else if (c == ' ') > + c = ESC_CHAR; > + else > Index: lib/tty/tty-slang.h > =================================================================== > --- lib/tty/tty-slang.h.orig > > ++++++ mc-rpm.patch > --- mc-rpm.patch > +++ mc-rpm.patch > @@ -18,14 +18,14 @@ > echo "$FILEPREF 0 $DATE INFO/EPOCH" > echo "$FILEPREF 0 $DATE INFO/LICENSE" > echo "$FILEPREF 0 $DATE INFO/REQUIRENAME" > -+ echo "$FILEPREF 0 $DATE INFO/ENHANCES" > -+ echo "$FILEPREF 0 $DATE INFO/SUGGESTS" > ++ echo "$FILEPREF 0 $DATE INFO/ENHANCES" > ++ echo "$FILEPREF 0 $DATE INFO/SUGGESTS" > echo "$FILEPREF 0 $DATE INFO/OBSOLETES" > echo "$FILEPREF 0 $DATE INFO/PROVIDES" > -+ echo "$FILEPREF 0 $DATE INFO/ENHANCES" > -+ echo "$FILEPREF 0 $DATE INFO/SUGGESTS" > -+ echo "$FILEPREF 0 $DATE INFO/RECOMMENDS" > -+ echo "$FILEPREF 0 $DATE INFO/SUPPLEMENTS" > ++ echo "$FILEPREF 0 $DATE INFO/ENHANCES" > ++ echo "$FILEPREF 0 $DATE INFO/SUGGESTS" > ++ echo "$FILEPREF 0 $DATE INFO/RECOMMENDS" > ++ echo "$FILEPREF 0 $DATE INFO/SUPPLEMENTS" > echo "$FILEPREF 0 $DATE INFO/CONFLICTS" > echo "$FILEPREF 0 $DATE INFO/CHANGELOG" > } > > ++++++ deleted files: > --- mc-apps-mediainfo.patch > --- mc-apps-torrent.patch > --- mc-apps.patch > --- mc-extensions.patch > --- mc-palmsupport.patch > --- mc-word_docs.patch > --- mc-x11browser.diff > > > To REVIEW against the previous version: > osc request show --diff 183188 > > To ACCEPT the request: > osc request accept 183188 --message="reviewed ok." > > To DECLINE the request: > osc request decline 183188 --message="declined for reason xyz (see ... for background / policy / ...)." > > To REVOKE the request: > osc request revoke 183188 --message="retracted because ..., sorry / thx / see better version ..." > -- 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] Integration of YaST in Ruby
by David Majda 16 Jul '13

16 Jul '13

Hi, as promised in my yesterday's mail [1], here is a plan of integration of YaST in Ruby into the openSUSE M4. Please let me know if you have any comments or objections. Description ----------- Technically, the integration consists of the following steps: 1. Freeze YaST Git repositories. 2. Do the final translation of frozen code into Ruby (with final versions of YCP Killer and Y2R, which would be labeled as 1.0 at that point). 3. Commit translated Ruby code into master branches of affected YaST repositories. Create tags marking the last YCP-based version and first Ruby-based version. 4. Increase version of all YaST modules to 3.0 (as previously discussed [2]). 5. Wait for YaST packages in YaST:head to build (this will happen automagically after comitting the changes). 6. Submit new YaST packages into Factory. 7. Unfreeze YaST Git repositories. 8. Grab a beer and celebrate the beginning of new shiny Ruby era :-) Plan ---- We think the best time to do the work above is during 3 days from Wednesday July 31 to Friday August 2. This means we would still have few weeks to finish our tooling, stabilize & test everything, and get ready for integration. These dates also fit best vacation schedules and other constrains of people involved. At the same time, there will be still some days before the M4 release. Our goal is actually to accomplish everything on the list on Wednesday July 31 already. Think of the remaining two days as a reserve in case of unforeseen problems (build service trouble, conflicting upstream changes, etc.). So, what do you think? ----- [1] http://lists.opensuse.org/opensuse-factory/2013-07/msg00265.html [2] http://lists.opensuse.org/yast-devel/2013-05/msg00040.html -- David Majda SUSE Studio developer http://susestudio.com/ -- 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] How to add new project to the offical repo?
by Roy Mu 16 Jul '13

16 Jul '13

Hi all! My name is Roy, and I'm new here. I want to know how to add new project to the official repo? Any rules/tutorials can I follow? Thanks! PS: I know how to write spec file and create new project with OSC. -- In the beginning was the lambda. God saw it, realized he didn't need anything else, and stopped there. —— 《FP Bible》 -- 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] Milestone 3 - delta iso
by Basil Chupin 15 Jul '13

15 Jul '13

When may one expect to see the x86_64 delta iso for MS 3, please? BC -- Using openSUSE 12.3, KDE 4.10.5 & kernel 3.10.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 15

[opensuse-factory] Fwd: [obs submit-request 182623] openSUSE:Factory:NonFree/openmotif: accepted by coolo
by Stephan Kulow 15 Jul '13

15 Jul '13

Hi, What sounds like a random hermes mails, is actually worth mentioning here: openmotif is LGPL now. So I will move the free apps needing motif back into factory after M3. Greetings, Stephan -------- Original Message -------- Subject: [obs submit-request 182623] openSUSE:Factory:NonFree/openmotif: accepted by coolo Date: Wed, 10 Jul 2013 15:30:00 +0000 From: coolo(a)suse.com Reply-To: coolo(a)suse.com To: coolo(a)suse.com State of submit-request #182623 was changed by coolo: new -> accepted Comment: checkin https://build.opensuse.org/request/diff/182623 Source project: devel:libraries:c_c++ package: openmotif revision: 18 Target: project: openSUSE:Factory:NonFree package: openmotif -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) . -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 7

[opensuse-factory] BtrFS Usage/Complaints
by Jeff Mahoney 15 Jul '13

15 Jul '13

Hi all - Over the past year, btrfs has received substantial attention in the areas of both stability and performance. I've been running it, personally, on a 4 TB data volume as well as my root partitions for my openSUSE 12.2/12.3 systems. I've been able to do stress tests like a long fsmark run simultaneously with creating and removing snapshots (with syncs to force them to disk) and haven't run into any issues. David Sterba, who's been leading the charge at SUSE for btrfs stability has likewise regularly run it through an array of torture tests and has found that problems are occurring a whole lot less frequently than they have in the past. The upstream btrfs community in which we participate has also started focusing less on feature development and more on stability and performance. But these are only anecdotal data points from two file system guys and if my experiences working for a major operating systems vendor have taught me anything, it's that our users can be a lot more creative at finding ways to break things than we are. ;) So, I'd like to hear your stories. What's worked for you? What hasn't worked? What would you consider the pain points with using btrfs? Lastly, I'd like to ask that you take the opportunity to test with the latest openSUSE Factory kernel running 3.10-final. 12.3 used the 3.7 kernel since it was the most recent release going into the beta cycle and we've seen a bunch of btrfs fixes since that release. I look forward to your feedback and the opportunity to improve btrfs for the 13.1 release and future releases. Thanks! -Jeff -- Jeff Mahoney -- Jeff Mahoney SUSE Labs

20 43

[opensuse-factory] NM Plasmoid not starting during desktop start up in Milestone 3
by Roman Bysh 14 Jul '13

14 Jul '13

Hello List mates, In this version of openSUSE 13.1 M3, is the networkmanagement plasmoid supposed to start up when the system boots to plasma-desktop? Or are we going to set it up manually via Yast? Or auto startup as was done in 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

1 0

[opensuse-factory] milestone 3 - what the status of networking?
by Per Jessen 14 Jul '13

14 Jul '13

I've just upgraded to/from factory-snapshot, and during bootup, the network seems a little confused. I get DHCP running on the wrong interface, which means my iSCSI root isn't found. I tried "ifup ethx" at the emergency shell, and was told that "Network is managed by '' --> skipping". -- Per Jessen, Zürich (25.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- 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] kde live iso build 574 kernel not getting installed
by Dale Ritchey 12 Jul '13

12 Jul '13

I downloaded the live iso and installed it. duringthe the kernel does not get installed. I worked around this by chroot /mnt launching yast . package manager and ticking kernel-desktop this is after changing the repo from http://download.opensuse.org/distribution/13.1-Milestone2/oss to factory and reinstalling the kernel. This is done while the retry boot loader is displayed then retry the boot loader on reboot grub2 uefi secure worked -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 8

Re: [opensuse-factory] 12.3 RC1 R128 trouble (was: ...install mysteries)
by Felix Miata 12 Jul '13

12 Jul '13

On 2013-02-18 16:40 (GMT+0100) Roger Oberholtzer composed: > I am installing 12.3 RC1 on a machine that happily runs earlier versions > of openSUSE. The graphics is, admittedly, an older ATI Rage XL (MACH64). > It runs as a server, and this is on the MB. It is usually only seen > during install. > The install was a bit of a PITA because, no matter what display I used, > I could not get a graphic install to work. I tried setting various > resolutions and even 'No KMS' in the initial install screen. The screen > would go black, and I could do nothing. No virtual terminals. Nothing. > Eventually I had settle for the text install. Using 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Rage Mobility M3 AGP 2x (rev 02) here. 11.4 works OK. I installed HTTP started by Grub using latest factory-snapshot with nomodeset on cmdline. Graphical install worked fine, though slow with only 384M RAM, but resulting X is unusable. The left half of the screen is fine, but the right side is a mess, as if there were some kind of buffer misalignment repeating portions and omitting others. Using nomodeset produces mostly black screens with colored lines in various places at various times in attempting to start the login manager, and kills keyboard. Bunch of Xorg.0.log files: http://fm.no-ip.com/Tmp/Linux/Xorg/os123r128/ Anyone looked for a match to any of these upstream R128 bugs? http://tinyurl.com/bz5lfmv I've commented in the last bug in that list. Exiting X makes the system unresponsive to keyboard and mostly empties the screen to black. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] dracut tests
by Per Jessen 12 Jul '13

12 Jul '13

Starting a new thread - it's my last day at work before two weeks holiday, I felt like playing with dracut a bit. Per Jessen wrote: > On a test-system running 12.3: > > 1st attempt: Running dracut with the default options produced an > initrd of 27Mb, more than 4 times bigger than the initrd made by > mkinitrd. It took 50 seconds (mkinitrd took 10seconds). > 2nd attempt: omitting a few modules created an initrd only 2.5times > bigger and in only 35seconds. > > I'm working on figuring out what else to omit. Ah, "--hostonly" helps a lot - that got me a 4.4Mb initrd in 13seconds, about 30% smaller than with mkinitrd. The next thing is to see if works. This build seemed to include a lot less stuff/modules than mkinitrd. I guess I need to add some modules. Problem - I need 'iscsi', which is supposedly a dracut module, but when I try to build it, I get E: dracut module 'iscsi' cannot be found or installed. -- Per Jessen, Zürich (20.0°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] need working /etc/apache2/mod_log_config.conf
by doiggl＠velocitynet.com.au 12 Jul '13

12 Jul '13

Hello, Can anyone post a working /etc/apache2/mod_log_config.conf I get following errors. Thanks Glenn # rpm -qa | sort | grep apache2 apache2-2.4.4-1.2.x86_64 apache2-doc-2.4.4-1.2.noarch apache2-example-pages-2.4.4-1.2.x86_64 apache2-utils-2.4.4-1.2.x86_64 apache2-worker-2.4.4-1.2.x86_64 # systemctl status apache2.service apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; disabled) Active: failed (Result: exit-code) since Fri, 2013-07-12 20:46:05 EST; 4min 8s ago Process: 3111 ExecStop=/usr/sbin/start_apache2 -D SYSTEMD -DNO_DETACH -k graceful-stop (code=exited, status=1/FAILURE) Process: 3091 ExecStart=/usr/sbin/start_apache2 -D SYSTEMD -DNO_DETACH -k start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/apache2.service Jul 12 20:46:05 test.site start_apache2[3091]: Check the APACHE_MODULES setting in /etc/sysconfig/apache2. Jul 12 20:46:05 test.site start_apache2[3091]: AH00526: Syntax error on line 11 of /etc/apache2/mod_log_config.conf: Jul 12 20:46:05 test.site start_apache2[3091]: Invalid command 'LogFormat', perhaps misspelled or defined by a module not included in the server configuration Jul 12 20:46:05 test.site systemd[1]: apache2.service: main process exited, code=exited, status=1/FAILURE Jul 12 20:46:05 test.site start_apache2[3111]: Module ""actions" is not installed, ignoring. Jul 12 20:46:05 test.site start_apache2[3111]: Check the APACHE_MODULES setting in /etc/sysconfig/apache2. Jul 12 20:46:05 test.site start_apache2[3111]: AH00526: Syntax error on line 11 of /etc/apache2/mod_log_config.conf: Jul 12 20:46:05 test.site start_apache2[3111]: Invalid command 'LogFormat', perhaps misspelled or defined by a module not included in the server configuration Jul 12 20:46:05 test.site systemd[1]: Failed to start The Apache Webserver. Jul 12 20:46:05 test.site systemd[1]: Unit apache2.service entered failed state #journalctl -n -- Logs begin at Fri, 2013-07-12 19:53:16 EST, end at Fri, 2013-07-12 20:46:05 EST. -- Jul 12 20:46:05 test.site start_apache2[3091]: AH00526: Syntax error on line 11 of /etc/apache2/mod_log_config.conf: Jul 12 20:46:05 test.site start_apache2[3091]: Invalid command 'LogFormat', perhaps misspelled or defined by a module not included in the server configuration Jul 12 20:46:05 test.site systemd[1]: apache2.service: main process exited, code=exited, status=1/FAILURE Jul 12 20:46:05 test.site start_apache2[3111]: Module ""actions" is not installed, ignoring. Jul 12 20:46:05 test.site start_apache2[3111]: Check the APACHE_MODULES setting in /etc/sysconfig/apache2. Jul 12 20:46:05 test.site start_apache2[3111]: AH00526: Syntax error on line 11 of /etc/apache2/mod_log_config.conf: Jul 12 20:46:05 test.site start_apache2[3111]: Invalid command 'LogFormat', perhaps misspelled or defined by a module not included in the server configuration Jul 12 20:46:05 test.site systemd[1]: apache2.service: control process exited, code=exited status=1 Jul 12 20:46:05 test.site systemd[1]: Failed to start The Apache Webserver. Jul 12 20:46:05 test.site systemd[1]: Unit apache2.service entered failed state # cat /etc/apache2/mod_log_config.conf # # The following directives define some format nicknames for use with # a CustomLog directive. # # http://httpd.apache.org/docs-2.2/mod/mod_log_config.html # # # Format string: Nickname: # LogFormat "%h %l %u %t \"%r\" %>s %b" common LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common LogFormat "%{Referer}i -> %U" referer LogFormat "%{User-agent}i" agent LogFormat "%h %l %u %t \"%r\" %>s %b \ \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%v %h %l %u %t \"%r\" %>s %b \ \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined # To use %I and %O, you need to enable mod_logio <IfModule mod_logio.c> LogFormat "%h %l %u %t \"%r\" %>s %b \ \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio </IfModule> # Use one of these when you want a compact non-error SSL logfile on a virtual # host basis: <IfModule mod_ssl.c> Logformat "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \ \"%r\" %b" ssl_common Logformat "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \ \"%r\" %b \"%{Referer}i\" \"%{User-Agent}i\"" ssl_combined </IfModule> -- 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] devel project request
by Theo Chatzimichos 12 Jul '13

12 Jul '13

Hello, I'd like to request to mark security:passwordmanagement repository as factory devel proejct, so I can push password-store package to factory. TIA, Theo PS: Keep me in CC please, I'm not subscribed to the list

1 0

[opensuse-factory] overstepping maintainers
by Ludwig Nussel 12 Jul '13

12 Jul '13

Hi, Looks like we went from one extreme (submit requests hanging around for months) to the other. It happened now for the second time in two days that I see a submit request accepted within a few hours that was a) not submitted by the actual package maintainer and b) not accepted nor acknowledged by the actual package maintainer and c) not urgent in any way. Both cases were core distro packages. Please, if you are project maintainer but not package maintainer give the actual maintainer a chance to review what arbitrary people do to their package. By giving a chance I'm talking about weeks rather than hours. It's very unfair and annoying to active contributors if they find their package messed up after returning from a week of vacation. Can we find a sensible middle way please? 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

13 20

[opensuse-factory] Which milestone will have dracut configured for the first time installation
by Roman Bysh 12 Jul '13

12 Jul '13

Hello all, Does any one know when "dracut" will finally be configured for the default installation? 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

7 22

[opensuse-factory] Can you get offers for both Med and Dent simultaneously?
by rubensanchan 12 Jul '13

12 Jul '13

Hi if I were to order my preferences as such: 1. UQ Provisional MBBS-unbonded 2. Griffith Medical Science 3. UQ Provisional MBBS-bonded 4. UQ Dental Science And the OP and UMAT requirements were achieved: Is it possible to get offers from either UQ med unbonded AND UQ dental science or UQ med bonded AND UQ dental science? Thanks! ----- greys anatomy nursing uniforms -- View this message in context: http://opensuse.14.x6.nabble.com/Can-you-get-offers-for-both-Med-and-Dent-s… Sent from the opensuse-factory mailing list archive at Nabble.com. -- 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] Has anyone had any success on getting apache2-2.4.4 on opensuse-factory
by doiggl＠velocitynet.com.au 12 Jul '13

12 Jul '13

Hello, Has anyone had any success on getting apache2-2.4.4 on opensuse-factory bug report raised: https://bugzilla.novell.com/show_bug.cgi?id=813705 Bug 813705 - apache 2.4 fails to start - Invalid command 'User' --Glenn -- 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] Have apache-mod_nss in openSUSE:Factory
by Aeneas Jaißle 11 Jul '13

11 Jul '13

In an effort to push most packages currently in server:Kolab:Extras to openSUSE:Factory, I'd like to open a submit request from mozilla:Factory/apache-mod_nss (currently: mozilla/apache-mod_nss) to openSUSE:Factory/apache-mod_nss. The mod_nss module provides strong cryptography for the Apache Web server via the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols using the Network Security Services (NSS) security library. It is needed to build 389-admin (389 Administration Server). -- Aeneas Jaißle » e: aj(a)ajaissle.de Sent using Kontact and Kolab on openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 6

[opensuse-factory] KVM, Xen, and libvirt package changes
by Jim Fehlig 11 Jul '13

11 Jul '13

Hi All, A quick note about some recent packaging changes in KVM, Xen, and libvirt... KVM: Since the qemu-kvm fork has been merged with qemu.git, the kvm package is now a simple wrapper around the qemu package. This results in a few changes to default values: guest RAM changes from 640M to 128M and NIC changes from rtl8139 to e1000. Also, the Windows virtio drivers are no longer bundled with the kvm package. Xen: For Xen, the xen-docs-pdf package has been dropped since its outdated content no longer exists upstream. The legacy xm/xend toolstack has been removed from xen-tools since it is unmaintained/deprecated upstream and has been moved to the new xen-xend-tools package. As has been the case for a few releases, xen-tools contains the new xl/libxl toolstack, which is now the default Xen toolstack. libvirt: The libvirt package has been split into several sub-packages, allowing installation of a hypervisor-specific libvirtd, e.g. libvirt-daemon-qemu for QEMU/KVM, libvirt-daemon-xen for Xen, libvirt-daemon-lxc for LXC, etc. Previously, all hypervisor drivers supported by libvirt were stuffed into the libvirt package, bloating its footprint and potentially bringing in unneeded dependencies, e.g. xen-libs on a KVM-only site. The xen_server pattern has been updated to accommodate these changes. I've also created a kvm_server pattern [1], which I hope coolo will merge into openSUSE/patterns. I'm still unsure how to handle libvirt-daemon-lxc. The cloud folks use libvirt with LXC in some of their testing infrastructure, so I would like to make the packaging changes as painless as possible for such users, without a proliferation of [hypervisor-of-the-day]_patterns. Suggestions welcome. Regards, Jim [1] https://github.com/openSUSE/patterns/pull/39 -- 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] Have mozilla-jss in openSUSE:Factory
by Aeneas Jaißle 11 Jul '13

11 Jul '13

In an effort to push most packages currently in server:Kolab:Extras to openSUSE:Factory, I'd like to open a submit request from mozilla:Factory/mozilla-jss to openSUSE:Factory/mozilla-jss. Java Security Services (JSS) is a java native interface which provides a bridge for java-based applications to use native Network Security Services (NSS). This only works with gcj. Other JREs require that JCE providers be signed. It is required by idm-console-framework (required for building 389-ds-console, the management interface for 389-ds), that is needed for Kolab Groupware. Any objections? -- Aeneas Jaißle » e: aj(a)ajaissle.de Sent using Roundcube and Kolab on openSUSE -- 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] Have perl-Mozilla-LDAP in openSUSE:Factory
by Aeneas Jaißle 11 Jul '13

11 Jul '13

In an effort to push most packages currently in server:Kolab:Extras to openSUSE:Factory, I'd like to open a submit request from mozilla/perl-Mozilla-LDAP to openSUSE:Factory/perl-Mozilla-LDAP. perl-Mozilla-LDAP provides a perl LDAP module that wraps the OpenLDAP C SDK. It is required by 389-admin, that is needed for Kolab Groupware. Any objections? -- Aeneas Jaißle » e: aj(a)ajaissle.de Sent using Kontact and Kolab on openSUSE -- 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] Milestone #2 and nouveau driver
by Basil Chupin 11 Jul '13

11 Jul '13

What incantations does one need to use and how many times does one need to wave a chicken foot while doing so to get rid of the nouveau driver in Milestone #2, please? :-) I want to install nVidia driver 319.23 but it won't "go in" because the nouveau driver refuses to be dismissed even though I have removed it using YaST and it is blacklisted in all the right places. :-( BC -- Using openSUSE 12.3, KDE 4.10.4 & kernel 3.9.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 23

[opensuse-factory] pdfpc is looking for devel prj
by Mariusz Fik 10 Jul '13

10 Jul '13

Hi, I've been told to push pdfpc forward. At this moment pdfpc[1] is build in my home prj. What devel prj should I choose as new home for pdfpc package? Publishing or something with GNOME in namespace? [1] - https://build.opensuse.org/package/show/home:Fisiu/pdfpc -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

2 2

Re: [opensuse-factory] Milestone #2 and nouveau driver
by Alin M Elena 09 Jul '13

09 Jul '13

I am sorry Patrick... to the downloaded .run from nvidia bash NVIDIA-Linux-x86_64-319.23.run --apply-patch /home/alin/Downloads/nvidia-3.10.patch hope helps, Alin On Tuesday 09 Jul 2013 13:53:50 you wrote: > * Alin M Elena <alinm.elena(a)gmail.com> [07-09-13 11:30]: > > I think this is the patch I used for 319.23 64 bit and kernel 3.10 > > > > I do not remember where I downloaded from... it may be was posted on the > > nvidia or arch forums... > > And for one with "Little Knowledge"(!tm), what did you apply the patch to? > Please give the command line... > > tks, -- Without Questions there are no Answers! _______________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin 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

2 1

Re: [opensuse-factory] BtrFS Usage/Complaints
by Arvin Schnell 09 Jul '13

09 Jul '13

On Sat, Jul 06, 2013 at 06:04:50PM +0200, Jan Ritzerfeld wrote: > Am Samstag, 6. Juli 2013, 15:55:23 schrieb Arvin Schnell: > > On Sat, Jul 06, 2013 at 02:18:44PM +0200, Jan Ritzerfeld wrote: > > > TIMELINE_LIMIT_* does not: > > > TIMELINE_LIMIT_HOURLY=5 keeps the last five snapshots and not only five > > > hourly snapshots per day. And although I set TIMELINE_LIMIT_DAILY=5 and > > > the rest 0, there are still snapshots made eight days ago (five hourly > > > and five daily). > > > > Could be because the cleanup algorithm only runs once a day. > > [...] > > Hmm, no. I manually did a "snapper cleanup timeline". > ATM, I am looking at client/cleanup.cc. And the code indeed does what I > observed. do_cleanup_timeline fetches a full list of timeline snapshots and > then removes the ones that should be kept. The remaining snapshots will be > deleted: > > if (num_hourly < limit_hourly && is_first_hourly(it, tmp.end(), *it)) > { > ++num_hourly; > it = tmp.erase(it); > } > else if (num_daily < limit_daily && is_first_daily(it, tmp.end(), *it)) > { > ++num_daily; > it = tmp.erase(it); > } > else if... > > Obviously, if all snapshots are both the first hourly and the first daily, > they will be only counted for the hourly limit. This is wrong, because you > will get "limit_daily" additional snapshots (if there are enough left). The > same holds true for monthly and yearly. > The correct code would be little bit more complicated: > > bool keep = false; > if (num_hourly < limit_hourly && is_first_hourly(it, tmp.end(), *it)) > { > ++num_hourly; > keep = true; > } > if (num_daily < limit_daily && is_first_daily(it, tmp.end(), *it)) > { > ++num_daily; > keep = true; > } > if (num_monthly < limit_monthly && is_first_monthly(it, tmp.end(), *it)) > { > ++num_monthly; > keep = true; > } > if (num_yearly < limit_yearly && is_first_yearly(it, tmp.end(), *it)) > { > ++num_yearly; > keep = true; > } > if (keep) > { > it = tmp.erase(it); > } > else > { > ++it; > } The result of the modified code is indeed easier to understand. I have changed snapper and also added a manpage snapper-configs(5). Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] Status: Distribution
by Stephan Kulow 09 Jul '13

09 Jul '13

Hi, Friday I switched to gcc 4.8 and triggered a full rebuild of openSUSE:Factory and yesterday we integrated KDE 4.11 beta. What bothers me at the moment are broken live cds and the fact that I didn't have working DVDs for the last weeks. I still hope we can have M3 this week though. Greetings, Stephan -- 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] Submitting python-construct and python-pybeam to Factory.
by Matwey V. Kornilov 09 Jul '13

09 Jul '13

This message is to introduce two packages which are being sent to Factory. python-construct is required by python-pybeam python-pybeam is required by https://github.com/openSUSE/rpmlint-checks/pull/2 (rpmlint) and is being sent to Factory in order to provide dependencies to this pull-requrest. python-construct description is located at its package page at OBS: https://build.opensuse.org/package/show/devel:languages:python/python-const… Summarizing, python-construct is declarative binary data parser for Python, able to parse such things like Ext2fs, Fat, ELF binaries, and so on. python-construct may be interesting not only as requirement for python-pybeam, but as powerful python module for people dealing with binary data format and network protocols. python-pybeam is Erlang VM BEAM format parser, based on python-construct module. python-pybeam makes it possible to do deep inspection of BEAM executable files. Initial purpose for python-pybeam was to implement rpmlint checks for erlang packages. The author of python-pybeam is one of the maintainers of devel:languages:erlang. Brief description of pull request #2 to openSUSE/rpmlint-checks: It adds two basic rpmlint checks for erlang packages. Proposed enhancements have been tested in home:matwey:erlang -- 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] normal? or bug? renaming config->config.save when no changes
by Linda Walsh 07 Jul '13

07 Jul '13

I don't remember this _always_ being the case (occasionally), but not usually. But now 90% of the time I'm seeing ".rpmsave" files that are identical (including date/time) to the ones added. In some cases, I'm 75-80% sure I've made some change, but that change is gone and it's not in the rpmsave file (a few cases, I know it's changed where I keep an RCS dir to manage changes). I thought rpm only saved off rpmsave files when it had a different MD5sum than the original rpm stated? Has that changed or was that a random property of each rpm package or what? I sure preferred the old method of not creating rpmsave files for files that haven't changed only creating rpmsave or similar when there was a user change. What it boils down to is there are 100's of configs, most of which I know nothing about and if they were to change, I wouldn't know if it was good or bad, so I assume good. I'm really only interested where I had to customize something and then something replaces my customized copy. Then I have to look to see if it is still useful or valid...etc.. So...did something change? If it is random, could something change to make the process more regular -- and only create 'old' files when they've been altered -- AND also, if they are different... (have a bunch of rpmsave files in my font dir that are identical to the new ones...)... Simple enough to fix w/a script, but still ... is it possible to not create them in the first place? -- 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] Any thoughts about openSUSE creating their own font for the desktop environment, wiki and forums
by Roman Bysh 07 Jul '13

07 Jul '13

Hello List mates, Has any one thought about openSUSE creating their own font type for their desktops wiki and forums. Ubuntu, Mac and $Microsoft use their own style. 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

4 9

[opensuse-factory] Mismatch in Tumbleweed kernel files
by Vahis 07 Jul '13

07 Jul '13

The kernel and source, as well as other stuff is not same version, 3.9.8-15-1 and 3.9.8-15-2. -- Vahis -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 8

Re: [opensuse-factory] BtrFS Usage/Complaints
by Claudio Freire 07 Jul '13

07 Jul '13

On Sat, Jul 6, 2013 at 5:26 PM, Jan Ritzerfeld <suse(a)mailinglists.jan.ritzerfeld.org> wrote: >> But if you were >> focused on saving snapshots, what snapper does is exactly fine. >> [...] > > I also focus on saving snapshots. You could use the same logic as me to say > that there must be never more than "limit_hourly" snapshots in total. That > is because every first daily, first monthly, and first yearly snapshot is an > hourly, too. But my proposed code will not do that. But then it's not an hourly limit, it's just limit. So, limit_hourly works as intended, you want an hypothetical limit_total. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] BtrFS Usage/Complaints
by Claudio Freire 06 Jul '13

06 Jul '13

On Sat, Jul 6, 2013 at 1:04 PM, Jan Ritzerfeld <suse(a)mailinglists.jan.ritzerfeld.org> wrote: > Obviously, if all snapshots are both the first hourly and the first daily, > they will be only counted for the hourly limit. This is wrong, because you > will get "limit_daily" additional snapshots (if there are enough left). The > same holds true for monthly and yearly. I don't think that's wrong. You're biased because you're focused on saving space. But if you were focused on saving snapshots, what snapper does is exactly fine. You probably want 0 daily and 0 monthly. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] BtrFS Usage/Complaints
by Arvin Schnell 06 Jul '13

06 Jul '13

On Sat, Jul 06, 2013 at 02:18:44PM +0200, Jan Ritzerfeld wrote: > Am Freitag, 5. Juli 2013, 11:17:07 schrieb Matthias G. Eckermann: > > Or to put it differently: Snapper should delete > > older snapshots much more frequently and aggressivly. > > [...] > > Yes. But how? I have been struggeling with its configuration for weeks > because it takes days to check the effect of configuration changes. While > the NUMBER_LIMIT roughly works as I expected (pre and posts count as 1), No, pre and post should not count as one. But the algorithm deletes pre and post together, so a limit of 1 and 2 might appear to be identical. > TIMELINE_LIMIT_* does not: > TIMELINE_LIMIT_HOURLY=5 keeps the last five snapshots and not only five > hourly snapshots per day. And although I set TIMELINE_LIMIT_DAILY=5 and the > rest 0, there are still snapshots made eight days ago (five hourly and five > daily). Could be because the cleanup algorithm only runs once a day. But I see that this needs better documentation. Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] automounting USB devices with xfce on 12.3
by Karl Eichwalder 05 Jul '13

05 Jul '13

I usually update my system with the traditional yast method. Now on 12.3, xfce no longer automounts devices in my USB card-reader. I think it used to work on 12.2, and it definitely work on a 12.3 installation from scratch. How can I debug this on my updated 12.3 system? Do others suffer from the same? If yse, I'd create a bug. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 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

5 9

[opensuse-factory] devel project for yubi packages wanted
by Timo Benk 04 Jul '13

04 Jul '13

Hi, i am looking for an obs devel project for the packages at home:t_benk:yubi. the packages here are - a pam module - some utilities related to the yubico token - some shared libraries used by the pam module and the utilities - two php applications used for validating the generated one time passwords what is the best way to go? - use a new devel project for all yubico related software - split the packages into different devel projects, eg. devel:languages:php and devel:libraries:c_c++ - something else i already tried to submit the packages to devel:openSUSE:Factory but got a reject. greetings, -timo -- Timo Benk Linux / Unix Consultant & Trainer Tel.: +49-178-8066638 Mail: benk(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- 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] Hermes mails and DNS issues
by Togan Muftuoglu 04 Jul '13

04 Jul '13

Hi, I am not entirely sure if this issues should be reported here but, for a couple of days I am not receiving notifications from hermes, due to the fact that sender domain dhl.suse.de is not found NOQUEUE: reject: RCPT from dhl.opensuse.org[195.135.221.142]: 450 4.1.8 <hermes(a)dhl.suse.de>: Sender address rejected: Domain not found; Until a couple of days ago, there was no problem so my best guess is some infrastructure changes have happened. Am I the only one effected ? Thanks Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] override sysctl.d settings ?
by Per Jessen 04 Jul '13

04 Jul '13

I created the following file: /etc/sysctl.d/ipv6tempaddr.conf --- net.ipv6.conf.default.use_tempaddr = 0 --- It seemed to be being ignored, so I checked dmesg: systemd-sysctl[258]: Duplicate assignment of net/ipv6/conf/default/use_tempaddr in file '/etc/sysctl.d/ipv6tempaddr.conf', ignoring. I know /etc/sysctl.conf says: # To disable or override a distribution provided file just place a # file with the same name in /etc/sysctl.d/ but it seems pretty silly to have to copy all of /usr/lib/sysctl.d/50-default.conf to override a single setting? -- Per Jessen, Zürich (17.2°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 7

[opensuse-factory] php 5.5.0
by Petr Gajdos 04 Jul '13

04 Jul '13

.. is in devel:languages:php:php55. Feel free to test and tell your opinion about factory inclusion. http://www.php.net/manual/en/migration55.incompatible.php Thanks! Petr

5 12

[opensuse-factory] Have python-augeas in openSUSE:Factory
by Aeneas Jaißle 03 Jul '13

03 Jul '13

In an effort to push most packages currently in server:Kolab:Extras to openSUSE:Factory, I'd like to open a submit request from devel:languages:python/python-augeas to openSUSE:Factory/python-augeas. python-augeas provides Python bindings for Augeas, a library for programmatically editing configuration files. Any objections? -- Aeneas Jaißle » e: aj(a)ajaissle.de Sent using Kontact and Kolab on openSUSE -- 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] yast2:ruby - just ran zypper up, now yast won't start.
by Per Jessen 03 Jul '13

03 Jul '13

>From y2log: 2013-07-03 08:59:16 <1> chestnut(1796) [liby2] genericfrontend.cc(main):575 Launched YaST2 component 'y2base' 'menu' 'ncurses' 2013-07-03 08:59:16 <1> chestnut(1796) [ui-component] YUIComponentCreator.cc(createInternal):124 Creating UI component for "" 2013-07-03 08:59:16 <1> chestnut(1796) [liby2] genericfrontend.cc(main):764 YAST_IS_RUNNING is yes 2013-07-03 08:59:16 <1> chestnut(1796) [wfm] Y2WFMComponent.cc(SetLanguage):523 GET encoding for en_GB.UTF-8: UTF-8 2013-07-03 08:59:16 <1> chestnut(1796) [Ruby] yast/wfm.rb:80 Call client /usr/share/YaST2/clients/menu.rb 2013-07-03 08:59:16 <3> chestnut(1796) [Ruby] yast/wfm.rb:85 Client call failed with undefined method `Opt' for #<Yast::MenuClient:0x00000001a96158> and backtrace ["/usr/share/YaST2/clients/menu.rb:159:in `DisplaySplash'", "/usr/share/YaST2/clients/menu.rb:22:in `main'", "/usr/share/YaST2/clients/menu.rb:313:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:83:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:83:in `run_client'"] 2013-07-03 08:59:16 <1> chestnut(1796) [liby2] genericfrontend.cc(main):780 Finished YaST2 component 'y2base' 2013-07-03 08:59:16 <1> chestnut(1796) [liby2] genericfrontend.cc(main):785 Exiting with client return value 'nil' 2013-07-03 08:59:16 <1> chestnut(1796) [Y2Ruby] binary/YRuby.cc(~YRuby):104 Shutting down ruby interpreter. -- Per Jessen, Zürich (17.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- 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] Windows freezing in M2
by Jon Cosby 02 Jul '13

02 Jul '13

I have windows freezing periodically in M2 GNOME i686. The mouse is still active, but I can't move or switch windows for five minutes or so. The clock stops, too. It's happened several times in the yast software manager, but it's not limited to that. I can be casually surfing in Firefox and see the same thing. I don't see anything interesting in the .xsession-errors, but I'm attaching that if anyone wants to peruse it. Any guesses what's going on? Specs: 3GB RAM and an AMD64 3800 2.0GHz, GeForce 6150 LE. Jon Cosby

2 1

[opensuse-factory] Status: Distribution
by Stephan Kulow 02 Jul '13

02 Jul '13

Hi, We integrated perl 5.18 and gcc 4.8 is my next aim. To ease that I rebased openSUSE:Factory:Gcc48 to build a minimal installation medium that we can test. I setup openSUSE:Factory:Build to keep the bootstrap cycle self contained and openSUSE:Factory:Core to build a small product medium. My goal is to have both these projects full green all time and the rest of factory is up to be dropped if it fails. Basically: if you submit something to factory that is part of these 2 projects, it's your responsibility that :Build and :Core are green with it, the rest of the packages in factory are the responsibility of the maintainers of those to keep green. We'll see how far we can go with that rule, it would be good to have a working KDE, GNOME and libreoffice too in factory, but I have to start somewhere, so having a base system and an installer to go with it is my Core for now. Greetings, Stephan -- 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] Fcitx 4.2.8 hit in M17N (and 13.1)!
by Marguerite Su 01 Jul '13

01 Jul '13

Hi, listmates, I'm pleased to announce that our M17N team has successfully packaged and shipped fcitx 4.2.8 released earilier today, GMT -0400 NY Time. For early testers, you can add M17N repo and update. Or you can wait for 13.1 M3 (seems). NOTICE Western people can also use "keyboard" input methods in fcitx to speed your life up. It has m17n-lib map support, spell checking and even word prediction with the help of presage (A Cambridge western language model). You can check my previous (4.2.7) video for demo: https://www.youtube.com/watch?v=NkTnbrLfrI4&hd=1 PROMOTION VIDEO http://www.youtube.com/watch?v=E15G-ZvMCtc http://v.youku.com/v_show/id_XNTc3NDM0NjI0.html?firsttime=326 (Chinese only, because Youtube was blocked in this area) NEW FEATURES See https://www.csslayer.info/wordpress/fcitx-dev/fcitx-4-2-8/ for details. The highlights for non-Chinese people: Core * New dbus-based tray icons * Polished desktop notifications * Disable status bar by default, so make you more concentrate on your work. * Some built-in "quick phrases", eg: emoji. Cloudpinyin * It was a feature for Chinese to find the more accurate words. But yes, its public servers are provided by research/IME companies which upstream has no interest in. Then some users outside China reported a security bug about censorship and Communist China. This update will let you disable it by short-cuts Hangul * Fixed a blocker bug: Google Code #696 Libpinyin * Now you can download user-contributed dictionaries online from sogou.com (A Chinese IME company providing free-of-charge software and service) M17N * We update its backend m17n-lib/m17n-db/libotf/m17n-contrib to the latest upstream versions Japanese * Fedora 19 introduced a new JP IME named "libkkc", it's based on marisa language model. But it ships IBus frontend "ibus-kkc" only (We'll have it too in 13.1) * openSUSE is the first ditribution ships fcitx-kkc. Thanks to my push and upstream's will to listen & great hard work PACKAGER TODO * Check out if there're more out-dated dependencies and update'em. * Test on GNOME 3.9 and further versions (GNOME integrates IBus since 3.6, so all other IM frameworks need to find their own way to survive. We hope it "just works" but there may be bad luck everyday.) PS: Its core devs are all studying in the United States now, one in MIT for bachelor and one in Stonybrook for PHD. So eastern US LUGs/Conferences are welcome to ask them to give lightening talks about how input methods work in design and reality. And if you can, buy them beers (I gave them openSUSE Chinese T-Shirts aka the version I published on G+ for this release) Greetings Marguerite -- 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] packages for pam_yubico, ykval and ykksm server
by Timo Benk 01 Jul '13

01 Jul '13

Hi, i have packaged the yubico pam plugin, the php validation server and the php key storage module. there are still some minor issues like missing manual pages which will be fixed if i will submit request the packages to factory. however, i would first wait for any comments, maybe i have missed something and yubico support is already on the way into factory. obs project: home:t_benk:yubi from the yubico homepage (http://www.yubico.com): Yubico's mission is to make strong two-factor authentication easy and affordbale for everyone. The company’s flagship product, the YubiKey, uniquely combines driver-less USB and NFC hardware with open source software. comments, feedback and patches are very welcome. greetings, -timo -- Timo Benk Linux / Unix Consultant & Trainer Tel.: +49-178-8066638 Mail: benk(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- 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] Why systemd over upstart?
by Linda Walsh 01 Jul '13

01 Jul '13

Was just looking for performance articles on boot and ran into upstart -- it seems somewhat similar to systemd in that it is a replacement -- but it's design was for performance and reliability -- things that systemd doesn't seem to emphasize. Also its well documented (http://upstart.ubuntu.com/cookbook/ also in the form of a 183p PDF). and has been in use for a few years -- so it's not alpha quality like systemd. Even fedora has used it -- though I guess they are switching to systemd? I just couldn't help but notice the large amound of examples and docs -- as well as a service scripting language -- something systemd fails hard on. So why go for an unfinished alpha over upstart? Advantages? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 15