May 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 761977] New: Publishing:TeXLive: Can not build package texlive-specs
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=761977 https://bugzilla.novell.com/show_bug.cgi?id=761977#c0 Summary: Publishing:TeXLive: Can not build package texlive-specs Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: werner(a)suse.com ReportedBy: werner(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- The last famous words from the virtual system is 6424 packages and 0 specfiles checked; 0 errors, 76 warnings. ... creating baselibs /.build/build: line 549: /usr/bin/chroot: Argument list too long [15324.871575] SysRq : Power Off Warning: clean shut down of the VM didn't work [15331.715541] Power down. How can I avoid this? Why the system is not able to copy back the 6424 packages build by the main spec file texlive-specs.spec? Do I've really create 2200 main packages for the 2200 spec files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 735288] New: go: make: /usr/lib/go/bin/8g: Command not found
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=735288 https://bugzilla.novell.com/show_bug.cgi?id=735288#c0 Summary: go: make: /usr/lib/go/bin/8g: Command not found Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dmacvicar(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- go package installs binaries in %{_bindir} instead of $GOROOT/bin But if you use gomake, this looks for the compiler in GOBIN=$GOROOT/bin (as defined in Make.inc) resulting in a make: /usr/lib/go/bin/8g: Command not found -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 891829] New: source_validator incorrectly parses conditionals in preamble
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=891829 https://bugzilla.novell.com/show_bug.cgi?id=891829#c0 Summary: source_validator incorrectly parses conditionals in preamble Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sbrabec(a)suse.com QAContact: adrian(a)suse.com CC: ro(a)suse.com Found By: --- Blocker: --- Created an attachment (id=602295) --> (http://bugzilla.novell.com/attachment.cgi?id=602295) util-linux.spec file passed to rpmbuild When processing new util-linux package, I got following error: error: Duplicate License entries in package: (main package) Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpUOqaab However rpmbuild -ba util-linux.spec does not see any problems of this spec file. This statement is apparently incorrect. Looking at the spec file, I see: One License tag inside "%if %build_util_linux" - this one should be active. Second License tag inside "%if %build_python_libmount" and inside %else of "%if %build_util_linux" - this should be inactive. Third License tag inside "%if %build_util_linux_systemd" and inside %else of "%if %build_util_linux" - this should be inactive. According to the initial evaluation of variables, we should have: %define build_util_linux 1 %define build_util_linux_systemd 0 %define build_python_libmount 0 %define verify_sig 0 But if I look into preprocessed /tmp/check_if_valid_source_dir-5rRp5R/tmp.spec, I see that all are supposed to be 1. Note that this bug is triggered by format_spec_file (see bug 891152), which forces placing License tags to each %if branch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 638893] New: /usr/share/doc/packages/openssh/README.SuSE update wanted
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=638893 https://bugzilla.novell.com/show_bug.cgi?id=638893#c0 Summary: /usr/share/doc/packages/openssh/README.SuSE update wanted Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: anicka(a)novell.com ReportedBy: ke(a)novell.com QAContact: qa(a)suse.de Found By: Documentation Blocker: --- Please, update /usr/share/doc/packages/openssh/README.SuSE. I guess, by now we can remove 9.1 and earlier items. Also please remove the opener (Dear ...) and the closer (Your team). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 530885] New: sshd fails to honour /etc/nologin presence when ssh keys used during login
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=530885 Summary: sshd fails to honour /etc/nologin presence when ssh keys used during login Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: liam.gretton(a)leicester.ac.uk QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 With the pam module pam_nologin in use, all non-root logins are supposed to be prevented if the file /etc/nologin exists. SSH fails to prevent user logins if /etc/nologin exists and the user authenticates with a key. Authentications with a password are successfully prevented, as expected. Reproducible: Always Steps to Reproduce: 1. Add pam_nologin to /etc/pam.d/login: auth requisite pam_nologin.so 2. Create /etc/nologin 3. Log in via SSH with a password. Login will be correctly prevented. 4. Log in via SSH with a key. Login is successful. Actual Results: SSH login with a key is not prevented by pam_nologin. Expected Results: SSH login with a key should be prevented by pam_nologin when /etc/nologin is present. openssh-5.1p1-40.15 pam-1.0.2-13.4 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 506831] New: /etc/init.d/sshd: incorrect usage of daemonstartproc ?
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=506831 Summary: /etc/init.d/sshd: incorrect usage of daemonstartproc ? Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: anicka(a)novell.com ReportedBy: puzel(a)novell.com QAContact: qa(a)suse.de Found By: Development # /etc/init.d/sshd restart Shutting down SSH daemon Starting SSH daemonstartproc: option -p does not work in force mode sshd daemon seems to work OK, though. reproducible: always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 880212] New: build cannot locate Net/SSL.pm in @INC
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=880212 https://bugzilla.novell.com/show_bug.cgi?id=880212#c0 Summary: build cannot locate Net/SSL.pm in @INC Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i686 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 The package build requires the package Net::SSL, which is undeclared and nowhere to be found. Reproducible: Always Steps to Reproduce: 1. { build; } Actual Results: 1. [ 53s] Can't locate Net/SSL.pm in @INC (you may need to install the Net::SSL module) (@INC contains: /usr/lib/perl5/site_perl/5.18.1/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.18.1 /usr/lib/perl5/vendor_perl/5.18.1/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.18.1 /usr/lib/perl5/5.18.1/i586-linux-thread-multi /usr/lib/perl5/5.18.1 /usr/lib/perl5/site_perl .) at /usr/lib/build/download line 3. [ 53s] BEGIN failed--compilation aborted at /usr/lib/build/download line 3. Expected Results: 1. The build tool should be able to build. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 827480] New: openSUSE:Tools: Bug
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=827480 https://bugzilla.novell.com/show_bug.cgi?id=827480#c0 Summary: openSUSE:Tools: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: adrian(a)suse.com ReportedBy: Rene.vanPaassen(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Other Blocker: No obs-service-source_validator.noarch 0:0.3-43.1 doesn't install on Fedora for lack of gpg2, which is called gnupg2 on Fedora To be solved by: %if 0%{?fedora_version} Substitute: gpg2 gnupg2 %endif in the meta file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 625552] New: openssh: inprove recommendation in "REMOTE HOST IDENTIFICATION HAS CHANGED" message
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=625552 http://bugzilla.novell.com/show_bug.cgi?id=625552#c0 Summary: openssh: inprove recommendation in "REMOTE HOST IDENTIFICATION HAS CHANGED" message Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: anicka(a)novell.com ReportedBy: sbrabec(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- When remote host identification changes, following message appears: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is ................ Please contact your system administrator. Add correct host key in /home/sbrabec/.ssh/known_hosts to get rid of this message. Offending key in /home/sbrabec/.ssh/known_hosts:1 RSA host key for ben has changed and you have requested strict checking. Host key verification failed. Following the message and opened known_hosts file, I found just an ASCII noise. Well, I tried to delete line 1 (guessing from the error message) and got this message: The authenticity of host 'foo (...)' can't be established. RSA key fingerprint is ............ Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'foo' (RSA) to the list of known hosts. Warning: the RSA host key for foo' differs from the key for the IP address '...' Offending key for IP in /home/sbrabec/.ssh/known_hosts:1 Are you sure you want to continue connecting (yes/no)? yes It would be nice to change the messsage and offer ssh-keygen -R or so. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 776058] New: Go language - go get/install fails with permission denied
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=776058 https://bugzilla.novell.com/show_bug.cgi?id=776058#c0 Summary: Go language - go get/install fails with permission denied Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: graham(a)andtech.eu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1226.0 Safari/537.4 SUSE/22.0.1226.0 With the Go 1.0.2 update, as a non priveleged user using the 'go' toolchain command to get/install a third party package from an SCM repo may fail with the message: go install runtime: open /usr/lib64/go/pkg/linux_amd64/runtime.a: permission denied The go build command somehow thinks the runtime .a archive is older than the runtime package source and so tries to rebuild the runtime package for linking. Known workarounds: 1. Pass the openSUSE specific -s flag to 'go get', 'go build' e.g. go get -s example.com/package 2. Update the file time on the runtime .a archive, as root do: find /usr/lib64/go/pkg -type f -exec touch {} + Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11