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