openSUSE Users August 2020

users@lists.opensuse.org

62 participants
62 discussions

[opensuse] download.opensuse.org html listing format - get rid of horizontal lines...
by David C. Rankin 09 Aug '20

09 Aug '20

All, Since someone changed the basic listing format from download.opensuse.org/repositories to some unwanted html format, the biggest problem is the damn horizontal lines drawn between every directory and they are drawn in a bright-white over a dark background -- it's like looking into a floodlight trying to pick out details behind it. Take a look at: https://download.opensuse.org/repositories/X11:/ Where I see: https://paste.opensuse.org/61684564 It is enough to drive you blind. Can we at least remove the horizontal lines? I could live with cyan folder names on a dark background if there wasn't a bright white line in between every folder. Personally, I'd prefer the raw folder listing that reduces the bandwidth by 500%, but I understand it's hard to gore somebody's new ox. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] How to turn OFF new html-ized directory listings at http://download.opensuse.org/source/distribution/leap/
by David C. Rankin 08 Aug '20

08 Aug '20

All, Just going through source listings at http://download.opensuse.org/source/distribution/leap/ there is some kind of new "Pretty Print" html-ized format being used that underlines the entire row containing the srpm instead of the normal raw directory listing that only underlines the package. This (1) doubles the height of the listing you have to scroll and (2) makes scanning the listing awkward. Is there some way, or switch, that will revert to the simple listing? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 16

[opensuse] [SOLVED] Leap 15.2 and VLC - missing libs - libavcodec57(unrestricted)
by Andrei Verovski 08 Aug '20

08 Aug '20

Hi, Installing VLC from official VideoLAN.org repository throws these error: Problem: nothing provides libavcodec57(unrestricted) needed by vlc-codecs-3.0.11-lp152.333.3.x86_64 Solution 1: do not install vlc-codecs-3.0.11-lp152.333.3.x86_64 Solution 2: break vlc-codecs-3.0.11-lp152.333.3.x86_64 by ignoring some of its dependencies Solution is to add Packman repo which have all necessary libs. So this page need to be somehow updated (have no admin contacts). https://www.videolan.org/vlc/download-suse.html -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Convert from classic to transactional server?
by seroton10＠gmail.com 08 Aug '20

08 Aug '20

Hi, When installing openSUSE (any flavour), the installer offers a choice between the "server" and "transactional server" roles, among others. If I choose to install a "server" system, is there a (supported) procedure by which I can later convert it into a "transactional server"? I tried to do this conversion on a test system running openSUSE Leap 15.2, as follows: * run "zypper install patterns-base-transactional_base" * edit /etc/fstab to make root read-only * reboot This appears to work: The system self-updates and reboots when needed, /etc has been turned into an overlay filesystem, and zypper up tells me to use the transaction-update tool. However, one of the packages installed during the conversion is "read- only-root-fs", and its description contains a rather stern warning: Files, scripts and directories to run the system with a read-only root filesystem with /etc writeable via overlayfs. This package should never be installed in an already running system! It should only be selected by a system role for a read-only root filesystem with transactional updates. The package will create / modify entries for mounting /etc and /var. Those entries are used by dracut to mount the overlay file systems during the early boot phase. After reading this, I ask myself, was it just dumb luck that the test system wasn't destroyed during the conversion? Any clarification on this would be much appreciated. Regards, Olav -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Why do we reboot after a systemd upgrade instead of --system daemon-reexec?
by David C. Rankin 06 Aug '20

06 Aug '20

General question, On 15.2 today, updates included systemd, ghostscript and a few other peripheral libraries, but nothing other than systemd would have conceivably called for a reboot, but yet zypper up said a reboot was required. Question, why when we update systemd do we call for a reboot instead of executing a --system daemon-reexec in the post-install part of the update? E.g. systemctl --system daemon-reexec That itself will reload system and any/all new service files. More a curiosity than a problem. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 11

[opensuse] gcc 8 on Tumbleweed
by Roger Oberholtzer 06 Aug '20

06 Aug '20

I am using the NVIDIA NVCC GPU /CUDA compiler on Tumbleweed. The package I am building (darknet) seems to work best with NVCC 10.2. So I have been using that on Tumbleweed. I am setting up a new Tumbleweed system, and I see that gcc-8 (64-bit) is no longer available. I see gcc-7 and gcc-9. But no gcc-8. If it has been removed, is it perhaps still possible to find it for Tumbleweed? I did a search on openSUSE downloads, and it only had some Debian release. Nothing for openSUSE. I tried other GCC releases witn NVCC, but it complains that they are unsupported versions. It wants gcc-8. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] Portkocking problem
by Marc Chamberlin 06 Aug '20

06 Aug '20

Hello - I am experiencing a problem with port knocking and am in need of some guidance from someone with a deeper understanding of the Linux/OpenSuSE architecture than I have. I have a computer with 2 NIC cards defined as eth0 and eth1. I am running 2 knockd daemons using nearly identical configuration files that define the knock sequences needed to open a port. The IP addresses for each card are on the same internal private subnet and assigned by a DHCPD server. When I send a knock sequence from my laptop to this system on it's eth0 interface all works fine. But when I send the same knock sequence to the eth1 interface it generally fails, although every once in awhile, as I am trying to figure out what is going on, it will work one time and then again fails on subsequent tests. I don't know what I am doing that causes these occasional successes. I have tried bringing down and back up the eth1 interface with ifup and ifdown, and tried restarting the firewalld, network, and knockd services. I have also tried putting both interfaces on the same (INTERNAL) zone (not what I really want to do, but this eliminates the possibility that placing each interface in separate zones could be causing problems.) I fired up wireshark on my target computer to monitor the eth1 interface (and the eth0 interface to see if there were any differences that might give me a clue) and wireshark does indeed show the arrival of the knock packets coming from my laptop, on both interfaces. So I know that I am sending the knocks OK and that they are indeed arriving on the appropriate interfaces. So I next inserted the following rule into the head of the INPUT chain of the iptables to monitor what it is seeing - *iptables -w -I INPUT 1 -s 192.168.10.10 -j LOG; tail -n-0 -f /var/log/messages|stdbuf -o0 grep 192.168.10.10* (192.168.10.10 is the IP address of my laptop) and while this does show the knocks coming in on eth0, it fails to show any knocks coming in on eth1 (except occasionally as I mentioned above). Does this command look correct? In particular I am not really sure where the LOG chain will send its output, I am guessing it is to the messages log file. (I have turned back on logging to the messages log file since I prefer using text files rather than the journal log which I find is too difficult to work with) I imagine that wireshark is directly monitoring eth1 by making low level calls to the eth1 driver and I would have expected iptables to be doing the same, but apparently not. So what lies between the low level driver for eth1 that wireshark is apparently using, and the beginning of the iptables chain that is blocking these port knock packets from reaching the iptables chains? Anyone with ideas? As always much appreciated and thanks in advance for taking the time to help me out! Marc.... -- *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 14

[opensuse] Strange bash/su error after upgrade
by Kai Bojens 04 Aug '20

04 Aug '20

~> su - Passwort: -bash: test: too many arguments This occured today for the first time after the 'zypper dup'. -> root has no bash config in /root -> 'set -x' in /etc/bash.bashrc showed that this is happening before loading this config -> 'set -x' in ~$home/bash of the user doesn't show any error in regard to this problem -> 'strace' showed no obvious errors (although this doesn't work very well) Any ideas on how I could narrow this down? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] How to name a disk itself (not the partition)
by Daniel Bauer 04 Aug '20

04 Aug '20

Hi, I have several external 6TB disks. They all have 1 partition to which I assigned a name. But the drives themselves don't have a name. Now when I plug in two or three of them, the notifyer tells me: 5.5 TiB enrypted drive for each of those. If I want to unplug one I don't know which one. So I'd like to give the drive itself a name. How can I do that? /dev/sdi (no name) - /dev/sdi1 (myName) -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] Question about zypper local directory repo
by Carlos E. R. 03 Aug '20

03 Aug '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have one local repository: cer@Telcontar:~> cat /etc/zypp/repos.d/Local_RPMs.repo [Local_RPMs] name=Local RPMs enabled=1 autorefresh=1 baseurl=dir:/data/storage_c/repositorios_zypp/LocalRPMs path=/ type=plaindir priority=100 keeppackages=0 cer@Telcontar:~> In it, I have one rpm which is a symlink: cer@Telcontar:/data/storage_c/repositorios_zypp/LocalRPMs> l auto* lrwxrwxrwx 1 cer users 74 Jul 23 11:33 autofirma-1.6.5-1.noarch_SUSE.rpm -> /home/cer/aeat/programas/autofirma_linux/autofirma-1.6.5-1.noarch_SUSE.rpm cer@Telcontar:/data/storage_c/repositorios_zypp/LocalRPMs> "zypper se" (after a forced refresh) does not see it. Telcontar:~ # zypper se autofirma Loading repository data... Reading installed packages... No matching items found. Telcontar:~ # If I replace the symlink with the actual file, and refresh, zypper sees it: Telcontar:~ # zypper se autofirma Loading repository data... Reading installed packages... S | Name | Summary | Type - --+-----------+-----------------------------------------------------------------+-------- | autofirma | Aplicación de firma electrónica en escritorio y en trámites web | package Telcontar:~ # Is this a bug, or a feature? (Leap 15.1) P.S: If you are curious, the rpm comes from the Spanish government, for signing documents, and it is GNU GPL v. 2.0 and EUPL v. 1.1 <https://firmaelectronica.gob.es/Home/Descargas.html> - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXxlbVRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVePoAn0AUpR3k830n0jFxImL2 6eJkHXkrAJsGDUUV4TMS8DFjbDptXoqah2j7eA== =Ik8c -----END PGP SIGNATURE-----

3 9

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users August 2020