August 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 956262] New: cobbler dependencies.
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=956262 Bug ID: 956262 Summary: cobbler dependencies. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: osynge(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The applications: cobbler-2.6.6-3.8.noarch cobbler-web-2.6.6-3.8.noarch Are separately packaged hence "cobbler" should not depend on apache. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 935339] New: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz
by bugzilla_noreply＠novell.com 05 Jul '19

05 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=935339 Bug ID: 935339 Summary: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Uninstalling gpgme, I get the following: 1 package to remove. After the operation, 355.3 KiB will be freed. Continue? [y/n/? shows all options] (y): y (1/1) Removing gpgme-1.5.5-1.1 .........................................................................................................[done] Additional rpm output: install-info: No such file or directory for /usr/share/info/gpgme.info.gz warning: %postun(gpgme-1.5.5-1.1.x86_64) scriptlet failed, exit status 1 # rpm -ql gpgme | grep info /usr/share/info/gpgme.info-1.gz /usr/share/info/gpgme.info-2.gz /usr/share/info/gpgme.info.gz This looks similar to bug #929415 and may have the same fix? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 925561] New: NetworkManager should provide a way to designate any connection as a mobile data connection
by bugzilla_noreply＠novell.com 03 Jul '19

03 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=925561 Bug ID: 925561 Summary: NetworkManager should provide a way to designate any connection as a mobile data connection Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jrhodes(a)redpointsoftware.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Apper has an option in it's settings regarding when to automatically download and install updates. Under this setting there's an option "unless I am on a mobile data connection", which supposedly ensures that Apper doesn't download software updates while connected to a mobile (or metered) network. Unfortunately there doesn't appear to be any way in NetworkManager to designate a wireless or wired connection as being a mobile connection, i.e. a connection provided by a wireless hotspot or USB tethered phone. I'd really like to set Apper to automatically download and install updates as soon as they are available (I'm running on openSUSE Tumbleweed, which I believe is just Factory now?), but I can't do this because I occasionally have my laptop connected to my 4G hotspot, and I don't want to risk having packages download over 4G. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 914681] New: jing doesn't find Saxon extension
by bugzilla_noreply＠novell.com 01 Jul '19

01 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=914681 Bug ID: 914681 Summary: jing doesn't find Saxon extension Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomas.schraitle(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The jing package is used to validate an XML document with a RNG schema. When installing the jing package and running it without any options, you get: ----------------- $ rpm -q jing jing-20091111-19.1.3.noarch $ jing /usr/bin/build-classpath: error: Could not find saxon Java extension for this JVM /usr/bin/build-classpath: error: Some specified jars were not found Jing version 20091111 usage: java com.thaiopensource.relaxng.util.Driver [-i] [-c] [-s] [-t] [-C catalogFile] [-e encoding] RNGFile XMLFile... RELAX NG is a schema language for XML See http://relaxng.org/ for more information. ----------------- After investigating it, the respective line is this: BASE_JARS="jing xerces-j2 xml-commons-apis saxon xml-commons-resolver" This contains the list of all JAR files which is used by jing. However, "saxon" doesn't exist anymore, it should be "saxon6". The above line should be therefor look like this: BASE_JARS="jing xerces-j2 xml-commons-apis saxon6 xml-commons-resolver" -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 941235] New: Upgrading to python-virtualenv-12.0.7-2.1 fails: cpio: rename
by bugzilla_noreply＠novell.com 01 Jul '19

01 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=941235 Bug ID: 941235 Summary: Upgrading to python-virtualenv-12.0.7-2.1 fails: cpio: rename Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: robert.munteanu(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When upgrading to Tumbleweed 20150807 I get the following error: (1/1) Installing: python-virtualenv-12.0.7-2.1 ...............................................................................[error] Installation of python-virtualenv-12.0.7-2.1 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib/python2.7/site-packages/virtualenv-1 2.0.7-py2.7.egg-info: cpio: rename error: python-virtualenv-12.0.7-2.1.noarch: install failed error: python-virtualenv-12.0.7-1.3.noarch: erase skipped Installed version is $ rpm -q python-virtualenv python-virtualenv-12.0.7-1.3.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 947161] New: Attempt the goal to have a default setup without any -32bit packages installed
by bugzilla_noreply＠novell.com 24 Jun '19

24 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=947161 Bug ID: 947161 Summary: Attempt the goal to have a default setup without any -32bit packages installed Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A standard x86_64 machine should not have to pull in any -32bit packages. Those are compatibility layers, generally provided for backwards compatibility with binary-only modules. The goal is to eliminate the installation of *-32bit by default (the goal is NOT to eliminate the presence of the *-32bit packages!) This might actually solve issues like ug 799367 as well -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 901115] New: yast2-network overwrites postfix configuration
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=901115 Bug ID: 901115 Summary: yast2-network overwrites postfix configuration Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lmb(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 609975 --> http://bugzilla.suse.com/attachment.cgi?id=609975&action=edit main.cf mods caused by yast2 network After a long time, I used yast2-network to change something in the network configuration of my node. (Changed the hostname.) As a result, my postfix main.cf was overwritten and rendered unusuable. I'm entirely unsure why some of these parameters were touched - why would it unset mailbox_command, set mailbox_transport, unset relay_host? Yes, this was facilitated by me having /etc/sysconfig/mail:MAIL_CREATE_CONFIG="yes" at the default value, but normally, none of the yast2 tools overwrites manually modified files silently, without even creating an in-place backup. Especially since this looks as if unrelated parameters were touched. I might have understood rewriting "mydestination", but the other parameters make absolutely no sense. I'm attaching the diff here - I restored the main.cf from backup. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 965304] New: Change gnome-ppp on gtk-ppp
by bugzilla_noreply＠novell.com 23 May '19

23 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=965304 Bug ID: 965304 Summary: Change gnome-ppp on gtk-ppp Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: roman_romul(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- GTK PPP is an easy to use graphical dialup connection configuring and dialing tool with system tray icon support. It uses GTK+ for its graphical interface and integrates well in GNOME desktop environment. It also uses WvDial dialer as its backend, providing simple configuration via config files. You can also use plain wvdial if you don't have X running. GTK PPP is GTK3 fork of GNOME PPP. https://sourceforge.net/projects/gtk-ppp/ Gnome-ppp was for OpenSuSE 12.X -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 991188] New: Extra \n's in shim-install --help output
by bugzilla_noreply＠novell.com 14 May '19

14 May '19

http://bugzilla.suse.com/show_bug.cgi?id=991188 Bug ID: 991188 Summary: Extra \n's in shim-install --help output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: glin(a)suse.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fmn:~ # shim-install --help Usage: shim-install [OPTION] [INSTALL_DEVICE] Install Secure Boot Loaders on your drive.\n --directory=DIR use images from DIR.\n --grub-probe=FILE use FILE as grub-probe.\n --removable the installation device is removable.\n --bootloader-id=ID the ID of bootloader.\n --efi-directory=DIR use DIR as the EFI System Partition root.\n --config-file=FILE use FILE as config file, default is /boot/grub2/grub.cfg.\n --clean remove all installed files and configs.\n INSTALL_DEVICE must be system device filename.\n -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 991187] New: shim-install keeping silent about obvious errors
by bugzilla_noreply＠novell.com 14 May '19

14 May '19

http://bugzilla.suse.com/show_bug.cgi?id=991187 Bug ID: 991187 Summary: shim-install keeping silent about obvious errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: glin(a)suse.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In my custom installation shim-install failed during installation. The only information installer relayed was exit code 1. After re-running shim-install on the installed system I got the same result. fmn:~ # shim-install --config-file=/boot/grub2/grub.cfg fmn:~ # echo $? 1 Running shim-install with Bash debugging enabled has shown the root cause. fmn:~ # bash -x /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg ... + bootdir=/boot + '[' -n '' ']' + test -n '' + test -d /boot/efi + test -d /boot/EFI + test -n '' + test -n '' + test -n '' + exit 1 I forgot to instruct the installer to mount EFI partition during installation. I would welcome a more verbose message from shim-install in this case for the sake of reduced debugging time. -- You are receiving this mail because: You are on the CC list for the bug.

1 4