October 2014 - openSUSE Factory - openSUSE Mailing Lists

[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 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] Is driver:wireless without a maintainer?
by LB 09 Jan '15

09 Jan '15

Hello, about two months ago I submitted a package to driver:wireless without hearing anything more. Yesterday I tried to contact the maintainer (vbotka) directly but the email bounced. Is there someone else who is in charge? Regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 17

[opensuse-factory] NVIDIA driver package for Factory possible?
by jcsl 30 Dec '14

30 Dec '14

Hi. Is it possible to have the NVIDIA driver packaged for Factory? Now that it is a rolling version there seems to be a growing interest by users on it. But I read frequently that users won't install Factory because this driver isn't available (AFAIK). I myself am using Factory in a netbook with Intel graphics and I would like to use it in my desktop too but I don't want to be reinstalling the driver on every kernel update. If packaging the driver isn't an option, is there an automatized way to have the driver working after kernel upgrades? Greetings. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 16

[opensuse-factory] reiserfs kernel threads present even after reiserfs kernel module is unloaded
by auxsvr＠gmail.com 12 Dec '14

12 Dec '14

Hello, I'm running 3.16.4-1.g7a8842b-desktop x86_64 from kernel:stable and I observe this on a system without any reiserfs partitions: # ps axu | grep [r]eiser root 16287 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda4] root 16431 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda9] root 25392 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda4] root 25561 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda9] # lsmod | grep reiser # On 8 and 9/10, the system log indicates that os-prober attempted to mount sda4 and sda9 using every possible filesystem kernel module, but sda4 is an extended partition and sda9 is an unformatted one, which probably resulted in reiserfs kernel threads remaining even after I unloaded the reiserfs kernel module. To verify this, every time I run: #mount /dev/sda4 /mnt -t reiserfs mount: wrong fs type, bad option, bad superblock on /dev/sda4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. #modprobe -r reiserfs another reiserfs kernel thread is added to the aforementioned ones. Should I file a bug report about this? -- Regards, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 4

Re: [opensuse-factory] Wanted: Correct power-switch for ARM based Chromebook
by Dr. Werner Fink 04 Dec '14

04 Dec '14

Hi, just to be noted, that is not required to boot with openSUSE. Any nmodern Linux is enough, that is that there should be is the /sys file system and the filled /dev/input/ directory. I'd like to know the output of for n in /dev/input/event*; do udevadm info -a --name=$n done then we might catch the input device for gpio-keys.8 and the power switch therein. Werner > Le 01/10/2014 14:35, Andreas Färber a écrit : > > Hi, > Let's CC opensuse-arm for such ARM questions... > Am 30.09.2014 um 09:29 schrieb Dr. Werner Fink: > > Hi, > > just to be noted that the patch > > rules-add-lid-switch-of-ARM-based-Chromebook-as-a-power-sw.patch > > which includes the line > > SUBSYSTEM=="input", KERNEL=="event*", KERNELS=="gpio-keys.8", > > TAG+="power-switch" > > in the 70-power-switch.rules can not be fully corect. This because the > > "gpio-keys.8" > > is much to general and may cause trouble with other keyboard layouts. > > Therefore I'd like to see the output of such a Chromebook of the command: > > udevadm info -a /dev/input/by-path/*kbd > > which may give the more specific name of the power button. > > > > Werner > > Alex? Guillaume? Can any of you provide the requested information for > the Samsung Chromebook? > > From Chrome OS (kernel 3.8.11), "udevadm info -a > --name=/dev/input/by-path/*kbd" returns: > ********************************************************************** > Udevadm info starts with the device specified by the devpath and then > walks up the chain of parent devices. It prints for every device > found, all possible attributes in the udev rules key format. > A rule to match, can be composed by the attributes of the device > and the attributes from one single parent device. > > looking at device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0/event0': > KERNEL=="event0" > SUBSYSTEM=="input" > DRIVER=="" > > looking at parent device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0': > KERNELS=="input0" > SUBSYSTEMS=="input" > DRIVERS=="" > ATTRS{name}=="cros-ec-i2c" > ATTRS{phys}=="i2c-4-mux (chan_id 0)" > ATTRS{uniq}=="" > ATTRS{properties}=="0" > > looking at parent device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3': > KERNELS=="cros-ec-keyb.3" > SUBSYSTEMS=="platform" > DRIVERS=="cros-ec-keyb" > > looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e': > KERNELS=="104-001e" > SUBSYSTEMS=="i2c" > DRIVERS=="cros-ec-i2c" > ATTRS{name}=="cros-ec-i2c" > > looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104': > KERNELS=="i2c-104" > SUBSYSTEMS=="i2c" > DRIVERS=="" > ATTRS{name}=="i2c-4-mux (chan_id 0)" > > looking at parent device '/devices/12ca0000.i2c/i2c-4': > KERNELS=="i2c-4" > SUBSYSTEMS=="i2c" > DRIVERS=="" > ATTRS{name}=="s3c2410-i2c" > > looking at parent device '/devices/12ca0000.i2c': > KERNELS=="12ca0000.i2c" > SUBSYSTEMS=="platform" > DRIVERS=="s3c-i2c" > ********************************************************************** > > My openSUSE SD card is currently broken, so I cannot test under openSUSE. > > > Independent of the exact GPIO key, the term "ARM based Chromebook" in > > the subject and patch name seems to be rather broad given that there's > > the original Samsung Chromebook, plus the HP Chromebook 11, plus an Acer > > Chromebook based on Tegra, plus some based on Rockchip, etc. which > > likely all use different GPIO configurations. > > Mine is a Samsung Chromebook. > > > Guillaume > -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

2 2