- openSUSE Support

[opensuse-support] Is there a way to preserve RPM packages installed via autoinst.xml?
by Brian Reichert 30 Aug '19

30 Aug '19

We're using the SLES 12 SP3 DVD, and AutoYaST, to install a subset of that DVD into a new server. I want to retain the RPM packages of the installed RPMs somewhere on the filesystem. I don't see a hook in any docs for autoyast.xml / autoinst.xml to do this. Maybe there's a way of presenting a flag to zypper to retain them? I'm open to any advice people may have. Thanks! -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 5

[opensuse-support] tracking for a fix for Samba bug
by Brian Reichert 30 Aug '19

30 Aug '19

I'm trying to reproduce an issue one of our customers is having. They are running one of our servers, based on the SLES 12 SP3 DVD. That DVD came with this version of samba: samba-client-4.6.5+git.27.6afd48b1083-2.11.x86_64.rpm There are, of course, several samba-related RPMs with the same version number. I think our customer is getting bit by the bug, while accessing a NetApp: https://bugzilla.samba.org/show_bug.cgi?id=13009 I know that version 4.6.16+git.154.2998451b912-3.40.3 of the samba packages is available to us, but it's unclear to me, from it's changelog, if that fix was backported to the SLES-provided RPMs. Can anyone provide some insight? -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 4

[opensuse-support] WTF, why does systemd-logind power down my computer?
by Peter Suetterlin 30 Aug '19

30 Aug '19

Just happened the second time. I had pressed CTRL-ALT-Backspace twice to kill the X server - and the system shuts down instead of restarting it! The log reveals Aug 23 12:35:51 woodstock.pitnet kdeinit5[4101]: kdeinit5: sending SIGTERM to children. Aug 23 12:35:51 woodstock.pitnet kdeinit5[4101]: kdeinit5: Exit. Aug 23 12:35:51 woodstock.pitnet kwin_x11[4139]: The X11 connection broke (error 1). Did the X11 server die? Aug 23 12:35:51 woodstock.pitnet kscreen_backend_launcher[4138]: The X11 connection broke (error 1). Did the X11 server die? Aug 23 12:35:51 woodstock.pitnet systemd-logind[960]: System is powering down. Is that the latest "invention" of the systemd crew? -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 13

[opensuse-support] Accessing SD cards broken in Tumbleweed?
by Christian Boltz 29 Aug '19

29 Aug '19

Hello, am I the only one who can't access SD cards with current Tumbleweed? (Last updated yesterday, but I'm quite sure that this problem existed for at least a week. Actually I had a similar problem months ago, but it magically fixed itsself before I had time to report it.) Both the internal SD card reader of my laptop, and an USB-connected card reader refuse to work. This means: - for the internal card reader, I don't get a /dev/mmc* device or any log message when inserting a SD card - the external card reader starts to flash its LEDs, I sometimes (not always) get a message about a possibly bad cable [1], but it doesn't recognize the SD card. - using another cable with the external card reader, I was able to access a 512 MB SD card, but not a 16 GB card. For this, I get a flood of mtp-probe messages [2]. I tested on my old laptop (with terribly outdated Tumbleweed 20160603, it lived in the shelf since then), and things just worked: - the internal card reader of the old laptop works - the external card reader (using the same cable that caused [1]) works - (I didn't test with the other cable) IMHO it's very unlikely that the internal and external card reader (or its cable) broke at the same time, while everything still works with the old laptop. Oh, of course I tested with multiple SD cards to exclude a broken SD card as a reason. (All cards worked in my old laptop, and they also work in other devices like a camera.) Therefore - does someone else have problems accessing SD cards with internal or external card readers using current Tumbleweed? Do I need to provide some more details for debugging? Regards, Christian Boltz [1] Aug 28 22:43:51 tux kernel: usb usb1-port3: Cannot enable. Maybe the USB cable is bad? [2] Aug 28 22:50:01 tux kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6362, bcdDevice= 1.10 Aug 28 22:50:01 tux kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 28 22:50:01 tux kernel: usb 1-3: Product: Mass Storage Device Aug 28 22:50:01 tux kernel: usb 1-3: Manufacturer: Generic Aug 28 22:50:01 tux kernel: usb 1-3: SerialNumber: 058F312D81A Aug 28 22:50:01 tux kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Aug 28 22:50:01 tux kernel: scsi host7: usb-storage 1-3:1.0 Aug 28 22:50:02 tux kmail[4150]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux kdeinit5[3623]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux kmail[4150]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux kdeinit5[3623]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux kmozillahelper[5902]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux krunner[3702]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux krunner[2521]: Last message 'org.kde.solid.udisks' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux org_kde_powerdevil[3740]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux kmozillahelper[5902]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux kmail[4150]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sde" Aug 28 22:50:02 tux kmail[2521]: Last message 'org.kde.solid.udisks' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[2521]: Last message 'UdevQt: unhandled de' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[2521]: Last message 'UdevQt: unhandled de' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux mtp-probe[3837]: checking bus 1, device 48: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:02 tux mtp-probe[3837]: bus: 1, device: 48 was not an MTP device Aug 28 22:50:02 tux kernel: usb 1-3: USB disconnect, device number 48 Aug 28 22:50:02 tux kernel: usb 1-3: new high-speed USB device number 49 using xhci_hcd Aug 28 22:50:02 tux kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6362, bcdDevice= 1.10 Aug 28 22:50:02 tux kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 28 22:50:02 tux kernel: usb 1-3: Product: Mass Storage Device Aug 28 22:50:02 tux kernel: usb 1-3: Manufacturer: Generic Aug 28 22:50:02 tux kernel: usb 1-3: SerialNumber: 058F312D81A Aug 28 22:50:02 tux kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Aug 28 22:50:02 tux kernel: scsi host6: usb-storage 1-3:1.0 Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux mtp-probe[3865]: checking bus 1, device 49: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:02 tux mtp-probe[3865]: bus: 1, device: 49 was not an MTP device Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux mtp-probe[3866]: checking bus 1, device 49: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:02 tux mtp-probe[3866]: bus: 1, device: 49 was not an MTP device Aug 28 22:50:03 tux kernel: usb 1-3: USB disconnect, device number 49 Aug 28 22:50:03 tux kernel: usb 1-3: new high-speed USB device number 50 using xhci_hcd Aug 28 22:50:03 tux kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6362, bcdDevice= 1.10 Aug 28 22:50:03 tux kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 28 22:50:03 tux kernel: usb 1-3: Product: Mass Storage Device Aug 28 22:50:03 tux kernel: usb 1-3: Manufacturer: Generic Aug 28 22:50:03 tux kernel: usb 1-3: SerialNumber: 058F312D81A Aug 28 22:50:03 tux kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Aug 28 22:50:03 tux kernel: scsi host6: usb-storage 1-3:1.0 Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux mtp-probe[3899]: checking bus 1, device 50: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:03 tux mtp-probe[3899]: bus: 1, device: 50 was not an MTP device Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" -- So feel free to add Skimmed-by: Seth Arnold <seth.arnold(a)canonical.com> or whatever says I didn't spot anything wrong but I also didn't understand the finer points of what I've read. :) [Seth Arnold in apparmor] -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 3

[opensuse-support] bash script problem
by Patrick Shanahan 29 Aug '19

29 Aug '19

I regularly import photos from a flash drive and rename them with a script to YYMODD_HHMMSS_<orig_file_name>.ext Sometime recently my script, which I have used successfully for quite a few years, failed me and I cannot determine why. The script: exiv2 mv \-k \-r %y%m%d_%H%M%S_:basename: \.\/*.{nef,jpg} exiv2 is a compiled app similar to exiftool, a perl app directory contents before script: -rwxr-xr-x 1 paka users 57253957 aug 21 16:12 aaa_3410.nef -rwxr-xr-x 1 paka users 56087308 aug 21 16:12 aaa_3411.nef -rwxr-xr-x 1 paka users 54191672 aug 21 16:12 aaa_3412.nef -rwxr-xr-x 1 paka users 54679653 aug 21 16:12 aaa_3413.nef -rwxr-xr-x 1 paka users 59877177 aug 21 16:12 aaa_3414.nef -rwxr-xr-x 1 paka users 59788737 aug 21 16:12 aaa_3415.nef -rwxr-xr-x 1 paka users 58250749 aug 21 16:12 aaa_3416.nef screen output of the failure: > rename2date -k: Failed to open the file -r: Failed to open the file %y%m%d_%H%M%S_:basename:: Failed to open the file exiv2: File `./20190821_201219.nef' exists. [O]verwrite, [r]ename or [s]kip? ^C directory contents after script: -rwxr-xr-x 1 paka users 57253957 Aug 21 16:12 20190821_201216.nef -rwxr-xr-x 1 paka users 56087308 Aug 21 16:12 20190821_201217.nef -rwxr-xr-x 1 paka users 54191672 Aug 21 16:12 20190821_201219.nef -rwxr-xr-x 1 paka users 54679653 Aug 21 16:12 aaa_3413.nef -rwxr-xr-x 1 paka users 59877177 Aug 21 16:12 aaa_3414.nef -rwxr-xr-x 1 paka users 59788737 Aug 21 16:12 aaa_3415.nef -rwxr-xr-x 1 paka users 58250749 Aug 21 16:12 aaa_3416.nef in exiv2 :basename: is the original filename w/o extension I understand the failure as the script is trying to write the next filename as an existing filename. What I do not understand is why ":basename:" is not being applied. If ":basename:" was being applied there would be no failure as there would be no duplication of filenames. and I tried escaping, \:basename\: tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 6

[opensuse-support] PAM rules in KDE Plasma - where is the setting of focus?
by stakanov 29 Aug '19

29 Aug '19

I have the following problem since 15.1 Open user session A Open user session B Open user session C The setting of the machine is "secure", that is, to mount an usb key you need the root password. Normal behavior: You stick in the usb key while in user session B, the password request pops up and you enter the password the key is mounted. Observed behavior since 15.1: focus stealing. You plug in the usb key in user A or user B it does not matter. The password request does not appear. The machine times out and tells you that you are not authorized. Now if you go while waiting to Session C, the password requests opens. You discard it and return to B: you will now(!) be presented correctly with the password request. You can now mount the key. For any other user session our amount of session it is the same. Question: is there a config where I can avoid focus stealing? Does anybody else faces this problem (must be with secure settings of course) then I will raise a bug against it. Thank you. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] Headsup: konsole 19.08
by Achim Gratz 27 Aug '19

27 Aug '19

Besides the problem with the acticity indicator on the tabs no longer working (which I posted about on the wrong list), I've also had konsole start with no active tab in my KDE session and it would crash with a SEGV after creating new tabs and the leaving them all. That's probably another bug, but at least it has a reasonably easy workaround: I'm happy to report that this has cleared up by starting a fresh konsole window and saving the KDE session, the closing and starting KDE again. 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-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] fstrim after almost every wake-up from suspend-to-ram?
by Sebastian M. Ernst 26 Aug '19

26 Aug '19

Hi all, I am seeing `fstrim` running (and virtually freezing) my laptop after almost every wake-up from suspend-to-ram for about a minute or two. I do not observe this behavior on boot / reboot. Is this intentional, broken configuration of some kind, a potential bug or a potential hardware issue? I am running a Leap 15.1 on top of BTRFS on a new Samsung SATA SSD inside a W530 Thinkpad. I do not have a swap partition, so I can not test suspend-to-disk for comparison. Best regards, Sebastian -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] privoxy running but fails to resolve addresses when on travel
by stakanov 25 Aug '19

25 Aug '19

which puzzles me a lot. sudo rcprivoxy status ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2019-08-15 07:25:10 CEST; 50min ago Process: 2558 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/ SUCCESS) Process: 1623 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/ privoxy.pid --user privoxy /etc/config (code=exited, status=0/SUCCESS) Process: 1619 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/ libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SUCCESS) Process: 1612 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, status=1/ FAILURE) Main PID: 1627 (privoxy) Tasks: 6 (limit: 4915) CGroup: /system.slice/privoxy.service └─1627 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config Aug 15 07:25:09 roadrunner systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Aug 15 07:25:09 roadrunner cp[1612]: /usr/bin/cp: impossibile eseguire stat di '/etc/resolv.conf': File o directory non esistente Aug 15 07:25:10 roadrunner systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities. Aug 15 07:26:08 roadrunner.suse systemd[1]: Reloading Privoxy Web Proxy With Advanced Filtering Capabilities. Aug 15 07:26:08 roadrunner.suse systemd[1]: Reloaded Privoxy Web Proxy With Advanced Filtering Capabilities. /etc/resolv/conf exists and is functional (as I resolve without proxy). I have the failure with name resolution so I tried: sudo netconfig update -f No error but no success. Is it possible that a recent update changed something in permissions? And why do I have this problem only when I travel and use my pc outside the usual network? When I set the browser to not use proxy it runs normally. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 1

[opensuse-support] python module with C-code
by Axel Braun 20 Aug '19

20 Aug '19

Good morning, I'm in desperate need of a grib file converter (weather data) and wanted to build pygrib: https://build.opensuse.org/package/show/home:DocB:Tryton5/python-pygrib I get it compiling, but it seems there is some issue with including the C- library - it does not find the pygrib module during testing. Do I 'just' need to link it into %{python_sitelib} ? Thanks Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 4