January 2014 - 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] openSUSE:Factory:NonFree repository
by Kyrill Detinov 03 Jul '15

03 Jul '15

Hello. /factory/repo/non-oss/ isn't updated since September 23. -- WBR Kyrill

4 9

[opensuse-factory] Monospace font issue
by Kyrill Detinov 07 Apr '15

07 Apr '15

Hello. Recently updated my Factory running workstation (x86_64, Xfce). Monospace font interval is increased badly. I'm sure, I use DejaVu Sans Mono as a monospace font. I choose 'monospace 9' in programs settings. There is a screenshot: http://susepaste.org/view/simple/38919191 Changing to 'DejaVu Sans Mono 9': http://susepaste.org/view/simple/70371539 It looks like it was before. % fc-match Monospace Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. please move it to /home/kent/.config/fontconfig/fonts.conf manually Monospace: "Monospace" "Regular" -- WBR Kyrill

9 23

[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] Tumbleweed: systemd cannot start privoxy
by Patrick Shanahan 30 Oct '14

30 Oct '14

up to date Tumbleweed (13.1) systemctl start privoxy 18:26 Crash: ~ # systemctl start privoxy Job for privoxy.service failed. See 'systemctl status privoxy.service' and 'journalctl -xn' for details. 18:27 Crash: ~ # systemctl status privoxy privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; disabled) Active: failed (Result: exit-code) since Wed 2013-11-20 18:27:09 EST; 15s ago Process: 9430 ExecStart=/usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy /etc/privoxy/config (code=exited, status=1/FAILURE) Nov 20 18:27:08 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Nov 20 18:27:09 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1 Nov 20 18:27:09 Crash systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. Nov 20 18:27:09 Crash systemd[1]: Unit privoxy.service entered failed state. 18:27 Crash: ~ # journalctl -xn -- Logs begin at Sat 2013-03-30 18:27:22 EDT, end at Wed 2013-11-20 -- 18:27:35 EST. -- Nov 20 18:27:08 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... -- Subject: Unit privoxy.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit privoxy.service has begun starting up. Nov 20 18:27:09 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1 Nov 20 18:27:09 Crash systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. -- Subject: Unit privoxy.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: -- http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba4… -- -- Unit privoxy.service has failed. -- -- The result is failed. Nov 20 18:27:09 Crash systemd[1]: Unit privoxy.service entered failed state. Nov 20 18:27:15 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=282 TOS=0x00 PREC=0x00 TTL=64 ID=51684 DF PROTO=UDP SPT=631 DPT=631 LEN=262 Nov 20 18:27:15 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=282 TOS=0x00 PREC=0x00 TTL=64 ID=51685 DF PROTO=UDP SPT=631 DPT=631 LEN=262 Nov 20 18:27:34 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=247 TOS=0x00 PREC=0x00 TTL=64 ID=51686 DF PROTO=UDP SPT=631 DPT=631 LEN=227 Nov 20 18:27:34 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=247 TOS=0x00 PREC=0x00 TTL=64 ID=51687 DF PROTO=UDP SPT=631 DPT=631 LEN=227 Nov 20 18:27:35 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=263 TOS=0x00 PREC=0x00 TTL=64 ID=51688 DF PROTO=UDP SPT=631 DPT=631 LEN=243 Nov 20 18:27:35 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=263 TOS=0x00 PREC=0x00 TTL=64 ID=51689 DF PROTO=UDP SPT=631 DPT=631 LEN=243 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 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

9 20

[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] what happened to fbset?
by Felix Miata 04 Aug '14

04 Aug '14

in 11.4: # fbset -i mode "1152x864" geometry 1152 864 1152 864 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : radeondrmfb Address : 0xd80c0000 Size : 3981312 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 1 YPanStep : 1 YWrapStep : 0 LineLength : 4608 Accelerator : No In 13.1B1: # fbset -l if 'fbset' is not a typo, You can use... # zypper se -s fbset ... No packages found. # command-not-found fbset fbset: command not found -- "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

8 18

[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] wow
by Peter Czanik 02 Apr '14

02 Apr '14

Hello, I just did a fresh installation of factory. Network manager in KDE displays an error, but networking seems to work fine. $SUBJECT is "wow" because I don't recall openSUSE booting ever so fast! What was changed? I did not check with a timer, but it seems to be faster now than other distros, while earlier openSUSE was among the slow starters. Not that it matters on a machine I turn on only once a day, but still :-) Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 25

[opensuse-factory] Releases going forward
by Robert Schweikert 31 Mar '14

31 Mar '14

Hi, Releases going forward, or, how do we release without full time paid worker bees? With all the discussion toward the end of last year I suppose that today's e-mail "Timeline and roadmap V2" [1] finally shed light on the inevitable conclusion, the openSUSE team (@SUSE) will spend more time on other stuff and less time, if any, on turning the release crank. This is the team's prerogative just like everyone is free to work on the project, or not, in areas of interest to them. We can argue whether the way this is coming about is giving the project the best chance to succeed or whether the transition is being put worth in a nice and friendly way, but I think we should not go down that path. Thanks! to the openSUSE Team for the hard work they have put forth in the past to turning the release crank, it is much appreciated. I think the time has come to move forward and deal with the new situation. As of right now we still have a release cycle of 8 month. That would put us into May for openSUSE 13.2. This brings about two questions: - Given the current situation can we meet a May release date? - Do we skip the May release and move to a yearly cycle and release 13.2 in November of 2014? During last year's discussions there were a number of people favoring a yearly release cycle. We have to make a decision, - stick to 8 month or move to 12 month? Voice your opinion but stick to the point and please be concise. For simplicity lets just assume that there will be no full time paid help to turn the release crank and that the work is all on those that are not part of the openSUSE Team. Under any circumstances I'd say our first go around will be a bit rough around the edges and that's OK, we have to learn. What do I have to offer? After all stuff will not get done by me sending an e-mail into the world. I offer to take on part of the role of "Release Manager". I will not be able to do all of it and I have a new definition for the role (see below.) Stephan did way more and was always the tireless worker that brought everything together. No one that does not work on openSUSE full time can obviously fulfill that role, thus we have to split things up. I figure there are about 60 to 70 hours worth of work per week that we have to distribute. I'll define "Release Manager" as: The person or group that runs after people, keeps an eye on the schedule and tries to herd the cats to get the stuff fixed that is broken. I am willing to take part of that role, and with this mail hopefully be a rallying point to put openSUSE releases on a bit more of a solid footing than where we are today, after [1]. If we go this route it implies that everyone that has stuff in Factory, what will become the next release, nothing there changes, has more responsibility in helping out than they do today. We no longer have people that can fix everything and get to spend all their time on the distribution and integration of stuff. Every maintainer has more responsibility. So where do we go from here? Do we bootstrap an effort to get a release out the door without openSUSE @SUSE or do we drift along in the uncertainty of "maybe we know something in August"? I am happy to be a rallying point and fulfill part of the role of "Release Manager" as outlined above. Maintainers/Packagers be heard, speak up, but lets not drift into rat holes, the situation is actually quite simple. Later, Robert [1] http://lists.opensuse.org/opensuse-factory/2014-01/msg00350.html -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect 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

30 62

[opensuse-factory] Btrfs under heavy write makes system sluggish-er than ext
by Claudio Freire 06 Feb '14

06 Feb '14

So, the subject says it all. I've been testing a huge database on 13.1 RC1, well actually factory, with a btrfs partition (not the system partition, just a dedicated partition), and under heavy write it chokes the system much more than ext4 does. It also seems to have lower thoughput on what should be mostly parallel sequential access (ie: multiple sequential threads), but I'll have to perform more accurate benchmarks to be sure. It may be an fsync issue. It's not a critical issue, of course, but I'm in a position to assist with tests, benchmarks and diagnostics... so... what do I need to do to provide useful info here? -- 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] Timeline and roadmap V2
by Michal Hrusecky 03 Feb '14

03 Feb '14

Hi all, As you know we had a week-long meeting in Nuremberg. Quite a few of the things we've been working on (openQA, OBS workflow etc) were shared by now. Besides discussing features, we scheduled our work. In the previous thread on $SUBJECT, Simon noted that going for a release in November seemed a far smarter compromise between the benefits of releasing and getting some improvements in our tool chain than skipping a release. Most of the team agreed on this right away and we'd like to go for that. However. This does not mean the initial idea of doing a more 'relaxed' release is off the table. Planning software development is hard, planning experimentation (like the staging projects we are toying with) is impossible so we can not predict when we will be done. This means that we still intend to take those of you who stepped forward to help out with the release up on their offer. The exact nature of what we release is still to be determined and we'd like to make a more final decision on how much effort we can and will put in in August. So far it is sure that we would need some volunteer to keep eye on Factory and release milestones at least till then. So, for now, this will be a 'community release'. This might mean less QA but also no security updates provided by SUSE! Especially if it comes to the latter case we should communicate this carefully to our users as it will be more like a slightly more stabilized milestone than a successor to openSUSE 13.1. How to call it, how to communicate and what exactly it will look like - August. When exactly we will be fully back to working on Factory, releasing milestones, and working on the release we will hopefully be able to determine in August as well. Thoughts? The openSUSE Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

26 43

[opensuse-factory] rc* symlinks and systemd
by Ludwig Nussel 03 Feb '14

03 Feb '14

Hi, openSUSE has a packing policy of requiring rc* symlinks for each init script. So for e.g. /etc/init.d/foo there must be a symlink /usb/sbin/rcfoo -> /etc/init.d/foo. There is an rpmlint check for this policy (suse-missing-rclink). Now that more and more packages correctly switch to systemd only and drop the init scripts the rpmlint check doesn't work anymore. So we are slowly losing a nice convenience feature of openSUSE. Techically the feature works also for systemd units by making the rc symlinks point to /usr/sbin/service. When in involked as e.g. "rcfoo start" this script would then run "systemctl start foo.service". Personally I'd like to see us keeping the rc* feature also in the future so I'd like to propose introducing an rpmlint check to complain about missing rc* symlinks also for systemd unit files. Any objections on that? Otherwise I'd extend the suse-missing-rclink rpmlint check to .service files at some point. 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

11 21

[opensuse-factory] Factory currently does not boot in VirtualBox
by Wolfgang Rosenauer 31 Jan '14

31 Jan '14

Hi, I've updated a VM to Factory today and now it doesn't boot anymore in VirtualBox. The last thing I can see is "Loading initial ramdisk" and afterwards VirtualBox (4.3.6) switches into "Guru Meditation" and fails to boot further. Any ideas how to solve that? Wolfgang -- 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] Announce: 13.2 release in November
by Stephan Kulow 31 Jan '14

31 Jan '14

Hi, After reviewing the mailing list thread - and verifying with SUSE management that there is no other news, I guess I need to clarify some bits. To avoid any further uncertainties let's put this whole discussion to rest and name the beast: 13.2 will be released in November 2014. As 12.2 has shown, summer releases are *bad* - especially with conferences in spring, so I just don't want to go there and avoid the July release. This means: I will take the 13.1 release schedule and adapt it and start releasing milestones soon enough. IMO enough people volunteered to help and I sure hope they stick to their claim. As a reminder: http://s.kulow.org/131-issues shows what tasks the openSUSE team collected as TODO - so please be ready to say which of those tasks you volunteer for. 13.1 Milestone1 was in May - so openSUSE conference in April is the perfect time to bootstrap a release team. Naturally the release after 13.2 would be again in July - and the same argument applies then too, but let's talk about the future schedule once we have experience with the 12 months. 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 1

Re: [opensuse-factory] Announce: 13.2 release in November
by Stephan Kulow 31 Jan '14

31 Jan '14

Richard asked me to bounce it while he's "mobile" ;) Greetings, Stephan -------- Original Message -------- Subject: Re: [opensuse-factory] Announce: 13.2 release in November Date: Fri, 31 Jan 2014 14:14:15 +0100 From: Richard Brown <RBrownCCB(a)opensuse.org> To: Stephan Kulow <coolo(a)suse.de> Coolo, Thank you a whole bunch for this clear, concise announcement I'm looking forward to a November release, and I think its an excellent idea to use oSC14 to bring together the new release volunteers. A note to everyone who is willing to join the Release Team, don't forget the TSP is there, available and willing to help sponsor you to get to oSC14 :) On 31 Jan 2014 13:33, "Stephan Kulow" <coolo(a)suse.de <mailto:coolo@suse.de>> wrote: Hi, After reviewing the mailing list thread - and verifying with SUSE management that there is no other news, I guess I need to clarify some bits. To avoid any further uncertainties let's put this whole discussion to rest and name the beast: 13.2 will be released in November 2014. As 12.2 has shown, summer releases are *bad* - especially with conferences in spring, so I just don't want to go there and avoid the July release. This means: I will take the 13.1 release schedule and adapt it and start releasing milestones soon enough. IMO enough people volunteered to help and I sure hope they stick to their claim. As a reminder: http://s.kulow.org/131-issues shows what tasks the openSUSE team collected as TODO - so please be ready to say which of those tasks you volunteer for. 13.1 Milestone1 was in May - so openSUSE conference in April is the perfect time to bootstrap a release team. Naturally the release after 13.2 would be again in July - and the same argument applies then too, but let's talk about the future schedule once we have experience with the 12 months. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org <mailto:opensuse-factory%2Bunsubscribe@opensuse.org> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org <mailto:opensuse-factory%2Bowner@opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] wicked: How to override MAC address?
by Andreas Färber 31 Jan '14

31 Jan '14

Hi, On one of my ARM boards the MAC address gets initialized randomly on power-up. On Android that's band-aided by running a shell script with the netcfg equivalent of: ip link set enp1s0 down ip link set enp1s0 address 00:... ip link set enp1s0 up http://mydragonboard.org/2013/updating-ifc6410-software/ Older openSUSE posts advertised using LLADDR='00:...' in ifcfg-*, but for 13.1 that caused network.service (well, network(a)enp1s0.service) to timeout and in Factory wicked seems to simply ignore that option. Is that a bug? How to set the MAC address each boot before DHCP potentially sends out traffic from the wrong address? Should I write a custom .service with the above working commands and somehow intertwine that with network@.service? Or use ifup.d and somehow limit it to enp1s0? Any other place to easily set such an option? Thanks, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 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

2 1

[opensuse-factory] How to add a local mirror as a repositorie
by Luiz Alberto Saba 31 Jan '14

31 Jan '14

Hi guys Sorry if my question is dumb, but I'm a new user... I have a local mirror (rsynced with opensuse.c3sl.ufpr.br) and I'm trying (without success) to configure it as my main repositorie. If someone could give the "stones path"... Thanks Luiz Alberto Saba -- 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] NOTE: auto-cleanup of ~:branches: projects is active now!
by Adrian Schröter 30 Jan '14

30 Jan '14

To reduce the build load of our build.opensuse.org instance we did activate the new auto-cleanup mechanism of OBS now. This means, by default all default branch projects (home:<ACCOUNT>:branches:...) get an attribute to self-destruct after a given time (currently 60 days). No panic, this is less grave as you may think now, because: * The deletion will happen via a request. If you decline that one the project will stay. * Delete requests will not created if there are still running requests involving this project. * there is the "osc undelete" command to bring the project sources back * You can Opt-Out by removing the OBS:AutoCleanup attribute This will free hopefully lots of build power and make us more responsive again :) thank you adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (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

3 4

[opensuse-factory] RFC: move ifconfig and friends out of default installation
by Michal Kubecek 30 Jan '14

30 Jan '14

Hello, I've got one daring proposition. As you probably know, the ifconfig utility is obsolete since kernel 2.2 (released 15 years ago) so that it doesn't show you all requested information, sometimes it shows you things that don't exist and sometimes it does something else than you asked. There are more obsolete utilities (like route or arp) and even one that doesn't work at all for a very long time (rarp). As we have already kicked out of the distribution tools that were much less obsolete and much more useful, I propose to move the obsolete network config utilities out of the default installation, i.e. - move ifconfig, route, arp, nameif, ipmaddr, iptunnel into a separate package, e.g. net-tools-obsolete, which wouldn't be part of a default installation - drop rarp I'm not including netstat in the list as I'm afraid only few people even know that ss exists. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

16 36

Re: [opensuse-factory] wicked wicked
by Dr. Werner Fink 30 Jan '14

30 Jan '14

Hi Jan, I'd like to know why you Mail User Agent is using CR+NL and what the binary line below the PGP signature is good for? Should I open a bug against Claws Mail User Agent? This because my mutt handle such mails as binary waste. Even the file(1) command reports on the saved mail body: /suse/werner> file mail-body mail-body: data if I remove last the binary line I see /suse/werner> file mail-body mail-body: UTF-8 Unicode text which it should be. Werner ----- Forwarded message from Jan Matejka <JMatejka(a)suse.cz> ----- [... header removed...] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Fri, 24 Jan 2014 11:43:54 +0100 Frederic Crozat <fcrozat(a)suse.com> wrote: > Le vendredi 24 janvier 2014 à 00:03 -0600, Larry Finger a écrit : > > > I won't go so far as to say that the devs will never learn; > > however, wicd (aka wicked) is extremely wicked. I installed a copy > > to test something for a user, and I also was unable to return to > > NetworkManager when through. The only thing was to reinstall. > > wicked is not wicd.. "WICD (pronounced like wicked)" [1]_ .. [1] https://help.ubuntu.com/community/WICD - -- Jan Matějka | QA Engineer for Maintenance SUSE s.r.o. | https://www.suse.com/ GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCgAGBQJS6KvxAAoJEIN+7RD5ejahZ34H/jgnnl3LiSvW4AcFAT8ev9yh DhuKY5G4dCmAQ3UyJI3VQzLTrxpFfM8SzneIt6NVzuycNHHFj+hNbPv7WCXh3Cbk 40zzqqyLy8NjPYmNlS6VEvg3JSd12ZFnQY8wwxYwraHrxNDZcEC/6n/A8aTwF9y4 9BzF7hlVNHOMHSArtUasK4DDl9B2mhBRkN0c7+9aXard4JDrysDnVgqq1zf79qIm 5TdH8R2FVyMeZyc1PF07FFNp6JSu3XZIlimPeRRxJTRAB1zdxPbGCMDxVx9UkkIR R7NTWh3u8Ww5znFSLSpT5+wA5NuN/dkN1vK/0GM1Af3p1rzD/G1GXG2IWaj3g9U= =OahG -----END PGP SIGNATURE----- ��{.n�+��{��_��}�-��{.n�+��N�(�֜��^� ޯ��^�ˬ{��r�+��0�� ----- End forwarded message ----- -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

6 5

[opensuse-factory] Question regarding qpopper
by Carlos E. R. 30 Jan '14

30 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I ask this on behalf of a forum user. Looking here: <http://software.opensuse.org/package/qpopper> qpopper is available for 12.2, 12.3, and factory. Yet it is missing from the recent 13.1. Why? There is a bugzilla about this, dated last November, unanswered. <https://bugzilla.novell.com/show_bug.cgi?id=850801> There is no need to answer on the list if the bugzilla is answered. Thanks. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlLpXMEACgkQtTMYHG2NR9VllACdEhqMpRfVWtprHMQcYEP042xu R9MAoJJ5mzHuAKIyBzrFM2QVVW40I5qD =q9J0 -----END PGP SIGNATURE----- -- 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] [tumbleweed] Kernel 3.13.0 WARNING with Raid
by Bruno Friedmann 30 Jan '14

30 Jan '14

If you use tumbleweed with raid soft subsystem beware of bug that can freeze it https://bugzilla.novell.com/show_bug.cgi?id=860252 -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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] Fwd: Re: [opensuse-packaging] exfat-nofuse in factory or at least consolidated in filesystem
by Stefan Seyfried 29 Jan '14

29 Jan '14

Damn crossposting, and then to the wrong list first... :-) -------- Original-Nachricht -------- Betreff: Re: [opensuse-packaging] exfat-nofuse in factory or at least consolidated in filesystem Datum: Tue, 28 Jan 2014 08:27:54 +0100 Von: Stefan Seyfried <stefan.seyfried(a)googlemail.com> An: opensuse-packaging(a)opensuse.org Hi Bruno, Am 27.01.2014 22:25, schrieb Bruno Friedmann: > For the shake, it would be wonderful to synchronize the different offer we have on obs about exfat. > > For example have the best of dkms alternative available here > https://build.opensuse.org/package/show/home:aevseev/exfat-nofuse-dkms > or native > https://build.opensuse.org/package/show/home:Akoellh:Kernelmodules/exfat-no… > > and the fuse exfat-utils > > https://build.opensuse.org/package/show/home:seife:testing/exfat-utils > https://build.opensuse.org/package/view_file/home:seife:testing/fuse-exfat I just packaged those because I was under the impression that exfat would be a good filesystem for external storage portable across OSs (Hint: it is not), so I'm not really using it anymmore. I can submit it to filesystems, but I will certainly not maintain it, since I am not using it. > Would be nice to have all effort submitted to filesystems repository and then pushed to factory. > Also the different packagers could work together offering a perfect need for our end-users community For Factory / openSUSE, the legal limbo in which all this exFAT stuff is hanging is probably a problem. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- 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] Removing WebYaST from Factory
by Jiri Srain 29 Jan '14

29 Jan '14

Hi, The YaST team currently maintains WebYaST, although this is right now not under active development. We are considering dropping maintanance for Factory so we can focus our efforts on YaST itself. We are aware, that there are WebYaST users in the openSUSE community, however, given the amount of bugs, which are reported, as well as data we have from SUSE Studio (where WebYaST is not used very often either), it looks obvious that YaST is much more used than WebYaST (and, I admit, in the past, YaST did not get the amount of care that it would deserve). Let us know, if you have any comments on this move. Thanks in advance for your feedback, Jiri -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- 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] Stagings are on
by Michal Hrusecky 29 Jan '14

29 Jan '14

Hi, yesterday we had initial kick-off meeting about staging projects idea. We have quite some tasks[1] on our plate and more will surely come as great part of this project is investigating possibilities. We are going to work in two week sprints and we already selected few tasks for the first sprint[2] that we are going to start working on right away. Apart from that we found even some area of small non-blocking tasks[3] if you want to help. We expect this section to grow over time as well. In general, you can track our progress in redmine[1], but don't worry, when sprint ends, we will report our progress. We are available on #opensuse-factory and #opensuse-project on freenode (scarabeus knows best the current state, but you can offload some easy questions to me - |miska| is my nick). We are also reading mailing lists, so if you have questions, feel free to ask :-) The important part of the message is that we are starting to work and you can track what we are doing. More about this project is in mail[4] that coolo sent on Monday. [1] https://progress.opensuse.org/projects/stagings/issues [2] https://progress.opensuse.org/versions/68 [3] https://progress.opensuse.org/versions/69 [4] http://lists.opensuse.org/opensuse-factory/2014-01/msg00278.html -- Michal HRUSECKY SUSE LINUX, s.r.o. openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- 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] openQA plans
by Antonio Larrosa 29 Jan '14

29 Jan '14

Hi, Last week we discussed how to proceed with our work on openQA integration in Factory development. As you know from our initial workflow proposal [1], openQA would be inserted between devel/staging projects and Factory; and 'after' Factory to create Factory-Tested. Our final goal with openQA and Staging projects is: *help the creation of Factory-Tested*, as a version of Factory that is more stable. As staging projects are still very experimental [2] our first priority will be to get openQA ready for a public deployment suitable for user interaction. That is, get openQAv2 out so packagers can check the testing results and QA volunteers can help create tests. After openQA has been made available publicly, we will move on to pre- integration testing. We expect that making openQA available publicly will take around 1 or 2 months but readying openQA and OBS for pre-integration testing will take 2 to 3 months after that. After this, we want to move on to: * make test creation easier * integrate openQA for integration testing The order of these is not clear yet. Timeline-wise, our goal is that by August, we have made serious progress in one of those. We are adding tasks to progress.opensuse.org [3] and will give regular updates on the status of our work on this mailing list. Cheers, Antonio Larrosa [1] https://github.com/SUSE/hackweek/wiki/Improved-Factory-devel-project-submis… [2] http://lists.opensuse.org/opensuse-factory/2014-01/msg00278.html [3] https://progress.opensuse.org/projects/openqav3/issues/ -- 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] Delete requests for failing packages
by Stephan Kulow 29 Jan '14

29 Jan '14

Hi, I just filed several drop requests for packages that fail for more than 100 days. This is basically all of webyast (actually when webyast is out, I would like to drop nginx too as it's only in factory for webyast and is a bitch of a package ;( and libsyncml. You're free to resubmit fixed packages. Greetings, Stephan -- 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] wicked wicked
by Felix Miata 29 Jan '14

29 Jan '14

Yesterday I installed fresh. Result was too much screwed up to make sense of it all. I tried zypper rm wicked, but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network(a)eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked. Tabooing wicked deselects zypper, and breaks too much to remember it all, a vast amount of yast, making software selection during installation take horrendous extra time clicking all those break xxx instead of allow wicked to be installed dialogs. e.g. inexplicable ones like yast2-users. Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be? -- "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

15 24

[opensuse-factory] Re: [opensuse] rpmdb2solv extremely slow
by šumski 28 Jan '14

28 Jan '14

On Sunday 19 of January 2014 13:58:02 auxsvr wrote: > Hi, > > Since last week, running zypper on oS 13.1 is extremely slow, performing > a lot of disk I/O. After some investigation, it seems that it removes > and creates again the database at /var/cache/zypp/solv/@System every > time it tries to do anything related with package management. According > to /var/log/zypper.log, earlier (normal) runs of rpmdb2solv returned > after 10 s (from "ExternalProgram.cc(start_program):402 pid 4833 > launched" to "ExternalProgram.cc(checkStatus):503 Pid 4833 successfully > completed"), whereas lately this lasts about 10 minutes, slower by a > factor of 60! > > Has anyone else seen something like this? Any ideas? I am seeing this on Factory also. Cheers, Hrvoje

8 16

[opensuse-factory] exfat-nofuse in factory or at least consolidated in filesystem
by Bruno Friedmann 27 Jan '14

27 Jan '14

For the shake, it would be wonderful to synchronize the different offer we have on obs about exfat. For example have the best of dkms alternative available here https://build.opensuse.org/package/show/home:aevseev/exfat-nofuse-dkms or native https://build.opensuse.org/package/show/home:Akoellh:Kernelmodules/exfat-no… and the fuse exfat-utils https://build.opensuse.org/package/show/home:seife:testing/exfat-utils https://build.opensuse.org/package/view_file/home:seife:testing/fuse-exfat Would be nice to have all effort submitted to filesystems repository and then pushed to factory. Also the different packagers could work together offering a perfect need for our end-users community I know that could submit them to filesystems devel repo, but I would prefer to see a (small) debate on the pro & cons by people who knows what they are doing ;-) Truly yours. -- Bruno Friedmann openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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] [ANN] zypper-cron: zypper package updates reporter
by Marcello Barnaba 27 Jan '14

27 Jan '14

Hi, I am new to the mailing list, I hope I am posting this to the right place :-). I have just thrown together https://github.com/ifad/zypper-cron, a tool inspired by Debian's apticron[1]. It runs zypper ref and zypper -x list-patches, parses the XML output and, if patches are missing, summarizes them on the standard output. I have packaged it here: https://build.opensuse.org/package/show/home:vjt:ifad/zypper-cron, upon installation it adds /etc/cron.d/zypper-cron that runs the script daily at 4AM. It'll certainly need saving its state to avoid duplicate e-mails about updates already notified, and as well incremental mailings. I am not aware on any other similar open source effort, so I decided to scratch my own itch. Comments (and GitHub pull requests) appreciated! ~Marcello [1]: http://packages.debian.org/wheezy/apticron -- 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] Live on Stagings
by Stephan Kulow 27 Jan '14

27 Jan '14

Hi, Last week we had some more discussions on how to proceed with the staging workflow. We took some decisions for our next steps and you're invited to give feedback and pull requests wherever you see a problem. We did not talk about any long term planning, we will do research - implementing changes as we see problems. One thing we want to start with is replacing build service groups with staging project reviews, so let me explain this a bit as most won't even be aware of the problem ;) As requests come to Factory, we have to be very careful not to accept A before its dependencies are in and not to accept B before all the packages fixed for the update are in. My current solution for that are request groups - implemented in a hackweek project[1]. This makes sure that we can't accept the delete request of a rename couple before the new package name is through legal review. But it's pretty intransparent to the reporter, so we would like to replace it with a more visible approach: grouping requests in staging projects. If you read my previous mails about the staging projects, they already group requests that are tested together. So the request groups and the requests that end up together in a staging project have overlaps that make the whole thing even more inscrutable. So the idea is as follows: if 2 requests need to go into factory together, they need to go into the same staging project and both requests get a review "by project openSUSE:Factory:Staging:F". So the reporter sees the project he has to check - and we can use the comments of that project to track the status of the reviews. This is a bigger task than it appears to be - as we need to adapt quite some tools, the repo checker needs basically to merge with the staging checker and both need to implement e.g. some logic for delete requests. This is all part of the factory-auto repo[2] Greetings, Stephan [1] https://github.com/SUSE/hackweek/wiki/Improved-Factory-devel-project-submis… [2] https://github.com/coolo/factory-auto -- 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] service ntp
by Achim Gratz 26 Jan '14

26 Jan '14

Ever since systemd took over it waits for ntp to complete startup, which takes a long time on my machine. Is there any way I can make systemd start ntp, but not wait for it before it considers bringing up kdm? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

14 42

[opensuse-factory] New package presentation: ejabberd.
by Matwey V. Kornilov 26 Jan '14

26 Jan '14

Hi, ejabberd is the famous XMPP server daemon. many public XMPP server are powered by ejabberd (https://xmpp.net/directory.php) As far as I know, Factory doesn't have any XMPP server software and this limits usage. I think it would be great to have at least one. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp:0x2207@jabber.ru -- 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] boot is taking much too long
by Felix Miata 26 Jan '14

26 Jan '14

15.352s lvm2-activation.service 11.897s systemd-fsck(a)dev-disk-by\x2dlabel-suse122.service 11.140s systemd-fsck(a)dev-disk-by\x2dlabel-suse121.service 9.890s systemd-fsck(a)dev-disk-by\x2dlabel-fedora19.service 9.159s systemd-fsck(a)dev-disk-by\x2dlabel-os131p20.service 9.026s systemd-fsck(a)dev-disk-by\x2dlabel-14usrlcl.service 7.504s systemd-fsck(a)dev-disk-by\x2dlabel-fedora18.service 7.367s network.service 6.848s systemd-fsck(a)dev-disk-by\x2dlabel-13home.service 5.599s systemd-fsck(a)dev-disk-by\x2dlabel-03boot.service 5.585s systemd-fsck(a)dev-disk-by\x2dlabel-suse123.service 4.778s lvm2-activation-early.service 3.014s home.mount 2.750s systemd-fsck(a)dev-disk-by\x2dlabel-fedora20.service 2.667s systemd-fsck(a)dev-disk-by\x2dlabel-suse114.service 2.651s systemd-fsck-root.service 2.537s systemd-fsck(a)dev-disk-by\x2dlabel-15pub.service 2.372s disks-E.mount 2.370s systemd-udev-root-symlink.service Why is LVM even in there? I used it briefly 6 or 8 years ago. I never expect to use it again. fsck? Are all partitions going down dirty even when I didn't even boot 13.2 last? -- "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

4 23

[opensuse-factory] [Tumbleweed] kernel: waiting module removal not supported: please upgrade
by Achim Gratz 25 Jan '14

25 Jan '14

Since upgrading the kernel to 3.13 I'm getting the above warning during shutdown. The corresponding change is here: http://lkml.org/lkml/2013/9/16/31 but it doesn't tell me what I should upgrade. From reading the comments I suppose that all occurences of "rmmod --wait" should be purged (from where?). The messages seem to be printed around the shutdown of kdm and NetworkManager, but there is probably a lot more going on that could trigger them. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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] box characters not used by ncurses
by Felix Miata 25 Jan '14

25 Jan '14

http://fm.no-ip.com/SS/Suse/badtty132.png mc http://fm.no-ip.com/SS/Suse/badtty132y.png yast Both using en_US on hardware, this happens also in Fedora and Mageia, so it must have an upstream cause. Anyone know what best to report a bug against, or how to fix it if mere config or missing package problem? -- "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

14 48

[opensuse-factory] package request: lldb for llvm
by Jason Newton 23 Jan '14

23 Jan '14

Hi Folks, I'm writing in for some help on bringing lldb to opensuse users. I've tried my hands at building it a number of times and I just can't get the darn thing to compile, it always errors out on it's python module in a cmake step that doesn't take into consideration oS's specific paths.... I've tried fixing that but it still hasn't worked out and I don't see what the ubuntu guys did to make it work. I'm hoping one of the LLVM maintainers reads factory and can manage to work out the build issues and add it to the llvm builds in devel:tools:compiler. By the way, for packages like llvm, which take over 45 minutes to compile on recent workstations, is there any recipe to "continue" building packages when using OBS local builds? You know, to speed up most of the build->fail->attempt fix->rebuild cycle? I tear up when I think of all those wasted CPU cycles. -Jason -- 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] LVM2 package in Base:System is causing stability issues related to grub and systemd
by Raymond Wooninck 23 Jan '14

23 Jan '14

Dear Listmates, For quite some time I am using the lvm2 package from Base:System. It's already quite some time ago and I don't remember why I switched it. But the last few days I saw stability issues where issuing the os-prober command from grub was hanging on detecting filesystems and also shutting the system down caused a hang situation. Due to this I lost a couple of time already the KDE configuration as that I had to do a hard reset. Together with Hrovje (shumski) and Luca (einar77), I managed to find the package that was responsible for this misery. Tracing the os-prober command and the shutdown process, it seemed that both were hanging as soon as a lvm2 command was issues. Killing that lvm2 command, made the system behave correctly again. I reverted back to the lvm2 version in Factory and the system is functioning normally again. Therefore I would like to ask the maintainer of lvm2, to validate the latest changes to make sure that his changes are working properly together with grub and systemd. Until that time it would be good not to submit or accept the current version that is in Base:System. For those that are using this version, I would recommend to revert back to the version in Factory. Regards Raymond -- 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] wicked and network configs
by Sid Boyce 22 Jan '14

22 Jan '14

After on zypper dup and during another networking was lost. Network interfaces deconfigured. From dmesg:- [83889.988963] br1: port 1(eth1) entered disabled state [83889.992691] br0: port 1(eth0) entered disabled state [83889.992730] br0: topology change detected, propagating [83890.022425] device eth1 left promiscuous mode [83890.022507] br1: port 1(eth1) entered disabled state [83890.025398] device eth0 left promiscuous mode [83890.025455] br0: port 1(eth0) entered disabled state [83890.069753] wickedd (750) used greatest stack depth: 3304 bytes left [83890.131542] device eth1 entered promiscuous mode [83890.137569] device eth0 entered promiscuous mode [83890.297438] IPv6: ADDRCONF(NETDEV_UP): enp0s19f2u4u4u4: link is not ready [83890.304990] br1: port 1(eth1) entered listening state [83890.305020] br1: port 1(eth1) entered listening state [83890.305114] IPv6: ADDRCONF(NETDEV_UP): br1: link is not ready [83890.308101] br0: port 1(eth0) entered listening state [83890.308129] br0: port 1(eth0) entered listening state [83890.308228] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready [83900.954449] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s19f2u4u4u4: link becomes ready So far I have set them up manually with e.g "ifconfig br0 192.168.10.2" "route add default gw 192.168.10.103" The devices all still showed with ifconfig but weren't configured as per /etc/sysconfig/network/ifcfg-br0. Bug #859801 submitted Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- 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] MC - Shifted Fn inconsistency between run in X and run on tty
by Felix Miata 21 Jan '14

21 Jan '14

All my installations are en_US. Any support any of them may have for anything else escaped my notice and intent. For many years, regardless of distro or version, shifted function keys running MC have usually varied according to whether it is running in X, or on tty[1-6]. In every case of unshifted, F5 is copy and F6 is Move, with both assuming *to* opposing pane. Always when shift is applied to F5/F6, and MC is running in X, instead of assuming copy/move *to* opposite pane, the current filename is presented for editing. On tty[1-6], the most common behavior has always been that copy/move with name for editing is found with Shift-F3/Shift-F4 instead of Shift-F5/Shift-F6. Occasionally I've run across behavior on tty[1-6] being Shift-F3=view, Shift-F4=edit, Shift-F5=copy to editname, and Shift-F6=move to editname. Now on one 13.2 installation (host gx280) I've again stumbled onto a case of the latter behavior. Because of the activity in thread "box characters not used by ncurses" I looked here at output from locale and found LC_CTYPE unset (everything else either null or "POSIX"), unlike on most openSUSE installations here where LC_CTYPE=en_US.UTF-8. On most of my non-openSUSE installations, all locale output is either en_US.UTF-8 or null, while on most of my openSUSE installations, most locale output is "POSIX", with one or more entries null, and LC_CTYPE=en_US.UTF-8. What's going on here in openSUSE using POSIX for most but not all, and occasionally leaving LC_CTYPE unset, while other times LC_CTYPE=en_US.UTF-8? Where does LC_CTYPE ever get set? What does one need to do to keep MC keystrokes same on ttys as in X? -- "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

1 0

[opensuse-factory] obs web interface going crazy
by Cristian Rodríguez 18 Jan '14

18 Jan '14

Hi: There seems to be a caching issue in the OBS web interface, on every page reload you appear logged in as a different user.. in my case as "lrupp, cpansubmitter, Superpeppo89, etc" Will be cool if someone can take a look -- 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] Lord of the Rings IV: staging projects
by Stephan Kulow 17 Jan '14

17 Jan '14

Hi, I used the silent nights on OBS over Christmas to get serious about the ring projects and made sure that :Build and :Core are 100% succeeding and :MainDesktops actually can build live cds. As this was a lot of work, I want to preserve that and added now a little reviewer that makes sure updates to :Build and :Core go over my desk. I'm adding them to one of the staging projects on a "roll a dice" base to verify that adding updates is not adding any red to my beloved project monitor. https://build.opensuse.org/project/subprojects/openSUSE:Factory:Staging is my "dashboard" for the time being. It's a very manual process, but I'm refining my preferences of what's the best process daily - so bear with me. I just wanted to let you know about the change. It will delay updates to base packages, but for a good reason I hope you'll agree. 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 5

[opensuse-factory] Re: /etc/sysconfig/kernel vs. /etc/dracut.conf
by Linda Walsh 17 Jan '14

17 Jan '14

Felix Miata wrote: > > Does your Dell BIOS boot config menu allow to include addin devices? ---- The built-in INTEL Sata has a port out the back for eSATA. That can either be enabled or disabled. Unlike the 3 internal SATA ports (mostly used for optical drives), if it is enabled and no cable is present, no error message is displayed on boot (vs. enabled-internal SATA + disconnected power or cable => bios boot displays error and waits for a key to continue). The order of the other, SAS controller and any addin-cards can also be specified in the bios. Then it scans those cards on boot -- from that point you can choose which drives are boot drives and which order to try them in. (Precision 7600; PowerEdge T610 has similar setup -- but no eSATA port -- it does let me choose the boot drives to try and their order. I have an external-SAS port card (LSI) that gets scanned for drives 1st so it comes up with sda+sdb. sdc & sdd are internal drives -- w/boot and OS on sdc. > Dells are really persnickity about having HDs added or removed. I don't > remember ever seeing one's BIOS present any option to allow a HD > connected to an eSATA addin card as an explicit boot choice to be > preferred to the 4 more or less standard options, floppy, OM, HD, > network/PXE. Even if they were, I wouldn't be wanting them even as an > option, much less preferred to internally installed options. ---- It's "like" the optical disc, -- if there is no bootable media in it, then it gets ignored, but if there is, it will boot from it. Can config USB similarly, I believe, but I've never done 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] dracut mkinitrd doesn't see modules Bug #858378 submitted
by Sid Boyce 16 Jan '14

16 Jan '14

Built 3.13-rc7 on 3 boxes where dracut had replaced mkinitrd. zypper dup installed dracut. I spotted the problem on 2 systems and installed module-init-tools. On a third system I forgot to install module-init-tools and reboot failed with no access to usb or wired keyboard, network or anything else that needed modules were started. I had to do a fresh install, "zypper in module-init-tools", built and installed vanilla 3.13-rc7 and rebooted successfully. I did play around with booting from CD, mounting /dev/sda2 as /tmp/2, chroot /tmp/2 and mounting /dev/sda1 as /boot but that didn't allow zypper in module-init-tools to work. Reproducible: Always Steps to Reproduce: 1.#!/bin/sh cp arch/x86/boot/bzImage /boot/vmlinuz-$1;cp System.map /boot/System.map-$1 rm /boot/System.map;ln -s /boot/System.map-$1 /boot/System.map cp .config /boot/config-$1 cd /boot;mkinitrd /boot/initrd-$1 $1 grub2-mkconfig -o /boot/grub2/grub.cfg 2. 3. Actual Results: mkinitrd complained it couldn't find modules for 3.13.0-rc7 although they were present and worked when module-init-tools were installed on the other 2 boxes. Expected Results: Modules should have been picked up by mkinitrd. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- 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] Changes in Factory
by Jos Poortvliet 16 Jan '14

16 Jan '14

Hi all, We have digested most of your input on our proposed changes to the factory development workflow. Based on that, we'll be making some more concrete plans on what to hack on first to get there, like the openQA integration and staging projects. Next week our team has a meeting in Nuremberg and we'll have a more concrete plan after that. Feedback and offers for help continue to be welcome! The openSUSE Team

1 0

[opensuse-factory] new package: mozjs24
by Wolfgang Rosenauer 16 Jan '14

16 Jan '14

Hi, I've just created a submitrequest to Factory for the source package mozjs24 (Mozilla JS engine version 24). This is basically an update for mozjs17 and not a real new package. mozjs17 has to stay though until all consumers have been changed to use mozjs24. mozjs17 is unmaintained from a security perspective so depending projects should look into migrating to use mozjs24 instead. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6

[opensuse-factory] Warning for cryptsetup users
by Stephan Kulow 15 Jan '14

15 Jan '14

Hi, I just stumbled about this gentoo bug: https://bugs.gentoo.org/show_bug.cgi?id=497654 If this applies to our libgrypt update too, this means encrypted roots are unbootable in factory. It would be good if someone tried on a VM and gave feedback about it. 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] KDE 4.12 and Tumbleweed testing requested
by Greg KH 15 Jan '14

15 Jan '14

Hi all, I've imported all of KDE 4.12 into openSUSE:Tumbleweed:Testing, and it seems to mostly build properly, with the exception of some branding packages, which I'm guessing is not really needed: https://build.opensuse.org/project/monitor/openSUSE:Tumbleweed:Testing Anyway, if some of you could test it out and let me know if it works or not, that would be greatly appreciated. And thanks go out to Jiri Slaby for doing the hard work in getting this into Tumbleweed. He got the package lists all correct, I just ran a script :) thanks, greg k-h -- 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] broken Tumbleweed build cups-1.5.4-136.1.x86_64
by Patrick Shanahan 15 Jan '14

15 Jan '14

Tumbleweed build of cups-1.5.4-136.1.x86_64 is broken: Retrieving package cups-1.5.4-136.1.x86_64 (1/1), 7.2 MiB ( 11.0 MiB unpacked) Retrieving: cups-1.5.4-136.1.x86_64.rpm ..............................................................................[done (1.5 MiB/s)] .......................................................................................[done] (1/1) Installing: cups-1.5.4-136.1 ..............................................................................................[error] Installation of cups-1.5.4-136.1 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/cups/fonts: cpio: rename failed - Is a directory error: cups-1.5.4-136.1.x86_64: install failed error: cups-1.5.4-134.1.x86_64: erase skipped -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 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

3 5

[opensuse-factory] wxWidgets-3_0 for 13.2?
by Mariusz Fik 15 Jan '14

15 Jan '14

Hi, are there any plans to push wxWidgets-3_0 to Factory and get it included in next openSUSE release, 13.2? I found wxWidgets-3_0 is already in X11:wxWidgets project[1]. I'm asking about it because I maintain codelite package and its recent version requires wxWidgets-3_0. Without it, codelite can't be updated in Factory... [1] https://build.opensuse.org/package/show/X11:wxWidgets/wxWidgets-3_0 -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

2 1

[opensuse-factory] details on users of packages etc
by Jos Poortvliet 15 Jan '14

15 Jan '14

Heya, If you maintain or build a package in your home repo, you might be interested in knowing how many people download your package, how many update frequently, stuff like that. And that also goes for the devel projects - how many users do they have? We are thinking about making stuff like that visible. The question: what else would you want to know about your packages and their users? The most common star sign of your users we can't get but there's surely other things we can display ;-) And are there things you don't want to know? Hugs, J

4 3

[opensuse-factory] KDE 4.12 in Tumbleweed
by Ronan Chagas 14 Jan '14

14 Jan '14

Hi guys, Is there any plans to upgrade Tumbleweed KDE version to 4.12? Or, can I install it from any external repo? I needed it because it seems to improve KMail search, which is totally unreliable to me in the current version (4.11). Best regards, Ronan -- 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] Your thoughts on dropping pm-utils
by Vojtěch Dziewięcki 13 Jan '14

13 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I maintain pm-utils, and I want to drop them soon, because systemd can handle (sort of) suspend and hibernation and also becouse their upstream is dead and I'm not able to (and don't want to) fix all the bugs all by myself. There is some information and an initial discussion on the topic here: https://bugzilla.novell.com/show_bug.cgi?id=790157 The current state is that pm-utils are sort of "plugged in" to systemd and are called from systemd to perform suspend and hibernate, if they are installed. Doesn't work too well. So I'm interested in other people's opinions on how this should be done and in particular what hooks you would like to see rewritten as systemd units, since I can usually do that. IMO the most important hook is 99Zgrub that prevents to boot another OS if we have hibernated, I've already rewritten that one, if someone wants to look at it or test it (just put it in /usr/lib/systemd/system-sleep, hibernate without pm-utils and see if the grub menu appears when you turn the computer on - it shouldn't) , here's the link: http://bugzillafiles.novell.org/attachment.cgi?id=569356 I just modified it at the end, so it works as a systemd unit, but all the functions are the same as in 99ZGrub from pm-utils. I also think it would be nice to have a "transitional period", when pm-utils won't be used as default, but if someone would be unhappy with using systemd for suspending, pm-utils could be installed. So please share your thoughts on this. I also realize there are people who would like to keep pm-utils, but unfortunately I'm not able to fix those bugs any more, so if someone wants to disagree with dropping pm-utils, that person would have to become the maintainer and fix all the bugs (or find someone else to do it), because I can't and don't want to, thanks for understanding. Wojtek Dziewięcki -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSlhzWAAoJEHrcxBn8c1xjNVMH/2qvaIUSxUz/wtCBPqSmhlv9 nJXyrst1/eM3WMA2cGt6+8DjpeNDq19Fs2j19H/WH4l1MPCyvW6R8b2UKwb++fPt RDJd4T6vKBaK46hzL6DNdigwf7JtSFJB7B69ohN85fNoSNyrzIzVtnQA0Cl5QGU8 SStmp0vy8n67WXKkOerszmpOqdpomUu+GPdy4OCcjbK2Z6VLnwBVGnFw4IcTNw2N Wu2U/Iplyt1e7mpueNOxFCQr3qJePlyqbHLeLRYi3ROshJiJycx/siyD8yB7WGa6 UmKHPj5a+Q2yZ2T9/gzZm5OmQscfum/jgPV+B4Uh53BudnW2wm75xPSuOQOyaQI= =b39f -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

17 27

[opensuse-factory] skelcd-control-openSUSE-* moved to Yast Git and to YaST:Head OBS project
by Ladislav Slezak 13 Jan '14

13 Jan '14

Hi, This is JFYI, I have moved the development of the skelcd-control-* packages to Yast Git and to the YaST:Head OBS project. The reason is that the control files actually were stored in a Yast Git repository, but were part of yast2-installation Git and the changes were not synced to OBS automatically. That required some manual work to sync the changes to skelcd packages and the files easily go out of sync (the OBS modifications were not ported back to Git) and that sometimes lead to confusions. So if you want to update the installation control files use the new GitHub repositories [1] since now. Use the usual fork/pull request GitHub workflow [2]. The packages are built/submitted to OBS via Jenkins [3] the same way as the other Yast packages, i.e. all changes in master are sent to YaST:Head automatically and if the version number is increased (changed) a SR to Factory is created. Ladislav [1] https://github.com/yast/skelcd-control-openSUSE https://github.com/yast/skelcd-control-openSUSE-LangAddOn [2] https://help.github.com/articles/fork-a-repo https://help.github.com/articles/using-pull-requests [3] http://ci.opensuse.org/view/Yast/job/yast-skelcd-control-openSUSE-master/ http://ci.opensuse.org/view/Yast/job/yast-skelcd-control-openSUSE-LangAddOn… -- Ladislav Slezak Appliance department / YaST Developer Lihovarska 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] 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

[opensuse-factory] Thanks for RPi port of openSUSE
by Larry Finger 10 Jan '14

10 Jan '14

Bernhard, I finally got the chance to switch from Raspian to openSUSE on my Pi. I dislike system management under any flavor of Debian - openSUSE is so much more intuitive. The only file I saved was /boot/config.txt. It took me too long to get the graphics on the monitor set up correctly to want to redo that. I run a cross-compiler and build new kernels on an x86_64 desktop, then copy them over NFS to the Pi. Doing those builds on the Pi was just too painful. I use the source from the raspberrypi repo at GitHub, and I have switched to the 3.12.y branch, which is currently at 3.12.6. I have installed FXCE as the desktop, but have not yet switched to it. IceWM is a bit plain. Thanks again, Larry -- 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] Tumbleweed kernel-source missing
by Vahis 08 Jan '14

08 Jan '14

The other kernel stuff is from three days back. -- Vahis -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] Tumbleweed kernel packages
by Achim Gratz 05 Jan '14

05 Jan '14

Since some time kernels in Tumbleweed have multiple builds for each version. The build number is not taken into account correctly when multiversion kernels are enabled. I've filed bug#855517 and Michael Andres commented that he thinks the packaging is incorrect. The current situation looks like this onh my system: i | kernel-pae | package | 3.12.6-5.1.g080d0df | i686 | (System Packages) v | kernel-pae | package | 3.12.6-5.2.g080d0df | i686 | Tumbleweed If I were to install the new build, both builds would be recognized as installed, but since both kernels install into /lib/modules/3.12.6-5.g080d0df-pae only the latest install would actually be present. This then confuses the old kernel cleanup script to remove kernels that it should keep and "keep" kernels that are not actually installed. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- 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 is esound-daemon automatically installed on opensuse 12.3 when using zypper dup?
by Joop Boonen 04 Jan '14

04 Jan '14

Dear all, Today I did a sudo zypper dup. I saw: sudo zypper dup root's password: Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Retrieving repository 'openSUSE-12.3-Update' metadata ................................................................................[done] Building repository 'openSUSE-12.3-Update' cache .....................................................................................[done] Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW package is going to be installed: esound-daemon The following packages are going to be upgraded: As I wondered why esound-daemon was installed I've checked out what package needs this package: rpm -q --whatrequires esound-daemon no package requires esound-daemon I've deleted this package via: rpm -evh esound-daemon Preparing... ################################# [100%] Cleaning up / removing... 1:esound-daemon-0.2.41-23.1.1 ################################# [100%] without any problems. I wonder why esound-daemon is automatically installed? Regards, Joop. -- 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] What happened to startup_en.pdf?
by Richard Weinberger 03 Jan '14

03 Jan '14

Hi! http://download.opensuse.org/distribution/13.1/repo/oss/docu/ does no longer contain the files startup_en/de.pdf. Has this documentation been killed? :-( -- Thanks, //richard -- 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] smpppd anyone?
by Ludwig Nussel 02 Jan '14

02 Jan '14

Hi, Is anyone interested in maintaining smpppd? My personal usecase is gone so I have no use for smpppd anymore. If no one steps up I'll request dropping it from Factory. 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 24

[opensuse-factory] Possible 3.13-rc nouveau regression with GT 560 Ti
by Sid Boyce 02 Jan '14

02 Jan '14

System x86_64 with openSUSE 13.1. X.Org version: 1.14.99.905 openSUSE 12.2 kernels boot successfully into a graphical screen, login to KDE4, etc. all normal. 3.13-rc kernels boot fully with X running but no graphical screen and it freezes in VC with not all the startup messages displayed but I could ssh in from another box to check dmesg and logs. Xorg.0.log which I thought I had saved did not log an error. dmesg said "nouveau Playlist update failed". Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and running. If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log information. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 10

[opensuse-factory] FATE#313506 (multiple initrd builds each dup)
by Felix Miata 01 Jan '14

01 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=786318 refers to the inaccessible $SUBJECT. Can someone with access provide a progress report? According to the bug, target is 13.2. I'm in the middle of a 1126 package 13.2 zypper dup that is taking what seems like forever to do, because I neglected to remove all but one kernel first, and zypper seems to be spending about half its time running dracut to create initrds that will be recreated within mere minutes every time dracut, udev, mdadm, lvm2, multipath-tools and maybe others (kpartx?) are updated. Maybe what those lacking LVM and RAID should be doing is running rpm -e --nodeps and then locking all but dracut prior to every zypper dup. Why do so many packages unconditionally require these often unused packages? Yast2-network? Yast2-sudo? Yast2-users? Yast2-samba-server? Really? -- "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

1 0