openSUSE Factory November 2014

factory@lists.opensuse.org

111 participants
95 discussions

[opensuse-factory] openSUSE maintainer finder tool
by Bernhard M. Wiedemann 14 Jan '16

14 Jan '16

Hi, during our Hackweek at SUSE I spent a day or two to improve my tool to help finding the maintainer for software in Factory, which comes in handy for bugzilla-screening (getting bugs to the right people). You can use the tool at http://maintainer.zq1.de/ You can give it command names, full filepath, or package names (exact matches (including case) only) If you want to run or extend it, the code is all open on https://github.com/bmwiedemann/susepkginfo and the databases can be fetched from http://aw.zq1.de/db.suse/ The actual maintainer information comes from OBS, so is always current. Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 14

[opensuse-factory] xgettext aborts [Fwd: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64]
by Bernhard Voelker 30 Nov '15

30 Nov '15

What happened to xgettext? [ 198s] /usr/bin/xgettext --default-domain=coreutils --directory=.. \ [ 198s] --add-comments=TRANSLATORS: --keyword=_ --keyword=N_ --flag=_:1:pass-c-format --flag=N_:1:pass-c-format --flag=error:3:c-format --flag=error_at_line:5:c-format --flag=asnprintf:3:c-f ormat --flag=asprintf:2:c-format --flag=error:3:c-format --flag=error_at_line:5:c-format --flag=vasnprintf:3:c-format --flag=vasprintf:2:c-format --flag=verror:3:c-format --flag=verror_at_line:5:c- format --flag=wrapf:1:c-format --flag=xasprintf:1:c-format --flag=xfprintf:2:c-format --flag=xprintf:1:c-format --from-code=UTF-8 --keyword=proper_name:1,'"This is a proper name. See the gettext ma nual, section Names."' --keyword=proper_name_utf8:1,'"This is a proper name. See the gettext manual, section Names."' ${end_of_xgettext_options+} --flag=error:3:c-format --flag=error_at_line:5:c-f ormat --keyword='proper_name:1,"This is a proper name. See the gettext manual, section Names."' --keyword='proper_name_utf8:1,"This is a proper name. See the gettext manual, section Names."' --flag =asprintf:2:c-format --flag=vasprintf:2:c-format --flag=verror:3:c-format --flag=verror_at_line:5:c-format --flag=xprintf:1:c-format --flag=xvprintf:1:c-format --flag=xfprintf:2:c-format --flag=xvf printf:2:c-format --flag=xasprintf:1:c-format \ [ 198s] --files-from=./POTFILES.in \ [ 198s] --copyright-holder='Free Software Foundation, Inc.' \ [ 198s] --package-name="${package_gnu}coreutils" \ [ 198s] --package-version='8.22' \ [ 198s] --msgid-bugs-address="$msgid_bugs_address" \ [ 198s] ;; \ [ 198s] esac [ 198s] *** Error in `/usr/bin/xgettext': realloc(): invalid pointer: 0x00000000018ff590 *** [ 198s] ======= Backtrace: ========= [ 198s] /lib64/libc.so.6(+0x7343f)[0x7fa6640e043f] [ 198s] /lib64/libc.so.6(+0x78cae)[0x7fa6640e5cae] [ 198s] /lib64/libc.so.6(+0x7bde5)[0x7fa6640e8de5] [ 198s] /usr/lib64/libgettextlib-0.19.1.so(xrealloc+0xe)[0x7fa66445b56e] [ 198s] /usr/bin/xgettext[0x40b301] [ 198s] /usr/bin/xgettext[0x40b38d] [ 198s] /usr/bin/xgettext[0x40b4e1] [ 198s] /usr/bin/xgettext[0x40b98e] [ 198s] /usr/bin/xgettext[0x40ba93] [ 198s] /usr/bin/xgettext[0x40c340] [ 198s] /usr/bin/xgettext[0x406953] [ 198s] /usr/bin/xgettext[0x4052cc] [ 198s] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fa66408eb05] [ 198s] /usr/bin/xgettext[0x405ba3] Have a nice day, Berny -------- Original Message -------- Subject: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64 Date: Wed, 11 Jun 2014 18:15:31 +0000 From: hermes(a)opensuse.org Reply-To: hermes(a)opensuse.org To: mail(a)bernhard-voelker.de Package coreutils-testsuite (version 8.22-248.68) of project Base:System failed to build for openSUSE_Factory / x86_64. Review the build log: osc remotebuildlog Base:System coreutils-testsuite openSUSE_Factory x86_64 | less Check out the package for editing: osc checkout Base:System coreutils-testsuite -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

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

15 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] Mandos in openSUSE
by mots 01 May '15

01 May '15

Hello, I was told on the opensuse(a)opensuse.org list to post this here. Debian GNU/Linux has a program called Mandos, which allows computers with encrypted root filesystem to boot unattended as long as they are in the same LAN segment as the mandos server. If someone steals the computer or copies the storage of an ecrypted VM then they'll still have to enter the password on boot. It needs to install its client in the initrd of the encrypted machine, which is why it only works on Debian GNU/Linux for now. I feel like it would be a great addition to openSUSE GNU/Linux, but it needs a lot of changes in the boot process in order to work. More info about Mandos: https://wiki.recompile.se/wiki/Mandos Regards, mots

2 1

[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] [Tumbleweed] nmap: Illegal instruction
by Achim Gratz 28 Feb '15

28 Feb '15

I've just installed nmap to test the ciphersuites offered by some webservers and the RPM install failed with an illegal instruction. That went away after several retries. When I now use nmpa I see sporadic "Illegal instruction" failures right after starting nmap. Re-starting the same command always succeeds. model name : Intel(R) Xeon(R) CPU E3-1225 v3 @ 3.20GHz stepping : 3 microcode : 0x1c flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt (BTW, ht is disabled for this CPU, even though it's reported that some batch escaped with the HT feature not fused off). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 9

[opensuse-factory] can if-up/if-down networking be restored to 13.2 to replace wicked until it's fixed?
by grantksupport＠operamail.com 03 Feb '15

03 Feb '15

Upgrade from 13.1 -> 13.2 removed support for traditional/stable if-up/if-down network control, replacing it with wicked. In 13.2, wicked's currently badly broken; there are existing/critical issues, that prevent production use; those issues include, among mounting others, e.g., (1) tun https://bugzilla.suse.com/show_bug.cgi?id=904903 (2) up/down script usage https://bugzilla.suse.com/show_bug.cgi?id=907215 (3) ipv6 https://bugzilla.suse.com/show_bug.cgi?id=907694 Those issues need fixing, and are getting some attention already. In current state, these network problems leave 13.2 unstable at best, unusable at worst. In 13.1 all the aforementioned issues are not a problem -- everything was working. IMO, disabling working if up/down prior to full-release-vetting of wicked et al is an operational mistake. We'd prefer to stay with 13.2 .... but our available production solutions atm are (1) downgrade 13.2 -> 13.1 (2) switch to a known/working other distribution (Redhat/Centos 7, e.g.) (1) is messy and painful, and functionally regresses many of the OTHER solutions that modern/current 13.2 brings. (2) is what we've done -- currently at all our production/edge boxes. In lieu of immeidate fixes to 13.2, is it possible to reenable 'old' ifup/ifdown networking, disabling wicked, so we can get the distro back to working/production state? Or is wicked simply too wired-into 13.2? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 13

[opensuse-factory] 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] firewalld as alternative for SuSEfirewall2?
by Mathias Homann 26 Jan '15

26 Jan '15

Hi, Request for discussion: Should we offer firewalld as alternative/complement for SuSEfirewall2? I think we should... reasoning: mobile users (laptops) who use NetworkManager / Wicked for managing their ip connectivity "in userspace" would want to be able to have multiple wifi setups that end up being in different zones. I'm going to try to package the latest firewalld from fedora for openSUSE, and test it with 13.2. Progress report will follow in due time. cheers MH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

17 47

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory November 2014