http://bugzilla.opensuse.org/show_bug.cgi?id=1029961
Bug ID: 1029961
Summary: [META] Finalize /bin -> /usr/bin merge
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: daniel.molkentin(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Some packages still install files to /bin that are not symlinks.
A "find /bin -type f -exec rpm -qf {} \; | sort -u" on a recent TW yields:
bash-4.4-95.1.x86_64
dbus-1-1.10.16-1.1.x86_64
keyutils-1.5.9-5.33.x86_64
ksh-93v-6.15.x86_64
net-tools-deprecated-1.60-770.1.x86_64
procps-3.3.12-3.1.x86_64
psmisc-22.21-6.9.x86_64
rpm-4.13.0.1-1.1.x86_64
sash-3.8-2.8.x86_64
sysvinit-tools-2.88+-103.1.x86_64
tar-1.29-3.1.x86_64
tcsh-6.20.00-3.1.x86_64
util-linux-2.29.1-1.1.x86_64
vim-8.0.324-2.1.x86_64
These packages should all install their binaries to %_bindir, i.e. /usr/bin,
and have a symlink in /bin. This would finalize the /bin deprecation.
I am opening bugs for each of the packages. Once they are all closed, I'll
close this one.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1106751
Bug ID: 1106751
Summary: iptables does not work with kernel-default-base
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-maintainers(a)forge.provo.novell.com
Reporter: fvogt(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Initially reported as
https://github.com/kubic-project/automation/pull/474#issuecomment-417329301
Docker (and cri-o) do not work in Kubic VM images as iptables does not work:
g47:~ # iptables -L
iptables: No chain/target/match by that name.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1114673
Bug ID: 1114673
Summary: New UI for firewalld: interface not assigned to the
right zone when changed to public in first run
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: jeriveramoya(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Interface is not assigned to the right zone after following steps:
- Open new UI for firewalld: yast2 firewall
- Assign interface to different zone (for example public)
- In Zones, set different zone (for example trusted) as default.
- Accept
- Check with firewall-cmd interface assignation:
firewall-cmd --list-interfaces --zone=public | grep ens4 (is not there)
but firewall-cmd --list-interfaces --zone=trusted | grep ens4 (it succeeds and
it is pointing to the default zone not the one that was assigned) (same result
also after trying a firewall-cmd --reload)
Assignation works in general, but in this combination and just when the user
enters first to this screen and set previous steps, does not work (perhaps some
wrong initialization).
Expected result: Point to the interface that is assigned in the UI (in the
example, to public)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=944832
Bug ID: 944832
Summary: installing updates during shutdown causes reboot
Classification: openSUSE
Product: openSUSE Distribution
Version: 42.1 Milestone 2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: bnc-team-gnome(a)forge.provo.novell.com
Reporter: ohering(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
fresh leap milestone 2.
I switched from the iso install source to the online oss repo. This repo had a
few differend packages compared to the iso. The gnome software installer
recognized them as updates. Once I had to shutdown the system it offered a knob
to install pending updates, then shutdown. I enabled that box, and hit return.
I think nothing was downloaded, but the box did a reboot instead of the
expected shutdown.
If that feature is not ready yet I suggest to hide it for the time being to
really and always do a reliable powerdown if that was requested.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1165294
Bug ID: 1165294
Summary: haveged is marked as deleted after reboot
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: hpj(a)urpla.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Hi,
*After reboot*, a couple of my TW systems show:
$ zyp ps
Verbosity: 2
Checking for running processes using deleted libraries...
The following running processes use deleted files:
PID | PPID | UID | User | Command | Service | Files
----+------+-----+------+-------------------+---------
+------------------------------
531 | 1 | 0 | root | haveged (deleted) | haveged | /lib64/ld-2.31.so
| | | | | | /lib64/libc-2.31.so
| | | | | | /usr/sbin/haveged
(deleted)
| | | | | |
/usr/lib64/libhavege.so.1.1.0
You may wish to restart these processes.
See 'man zypper' for information about the meaning of values in the above
table.
No core libraries or services have been updated.
Reboot is probably not necessary.
Marcus Meissner noted on the factory ML, that:
> It is ran in the initrd and probably still running after transition to the
> regular system.
>
> (Likely pulled in via dracut-fips module)
Shouldn't a transition from initrd to regular operation include a restart of
this service then?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168405
Bug ID: 1168405
Summary: adjust issue handling to new agetty
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: lnussel(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
agetty from util-linux 2.35 (not yet packaged) supports reading issue files
from /run and /usr in the following way:
if /etc/issue exists:
read /etc/issue and /etc/issue.d
else if /run/issue exists or /run/issue.d has any files
read those
else
read /usr/lib/issue
read /usr/lib/issue.d
Moreover, the \4 and \6 escape codes use the first configured interface to
print the IP address.
That means for the most useful default case we don't need to run the extra code
of issue generator to enumerate network interfaces and merge issue files
anymore. We can rely on agetty built-in features only. Those who need the extra
features to print ssh keys or custom computed stuff could still install
issue-generator. So I propose the following change:
- don't hard require issue-generator in openSUSE-release
- don't ship /etc/issue
- ship /usr/lib/issue.d/10-openSUSE.issue with the following content:
Welcome to \S{PRETTY_NAME} \S{VERSION_ID} - Kernel \r (\l).
\4 \6
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093592
Bug ID: 1093592
Summary: redshift doesn't work after geoclue2 update
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X11 Applications
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: dmarcoux(a)posteo.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 770512
--> http://bugzilla.opensuse.org/attachment.cgi?id=770512&action=edit
redshift error
Hello,
I updated to the latest snapshot (2018 05 15) and since then, redshift with
geoclue2 doesn't work. After launching, it displays an error (see attachment).
This wasn't happening with the previous snapshot I had, but I'm not sure which
one. The issue seems to arise due to changes within the recent revisions of the
geoclue2 package, so as far as 2 months ago. So by looking at the snapshots, I
suspect it is in one of those:
- 2018 03 04
- 2018 04 24
- 2018 05 11
- 2018 05 13
The workaround is to provide the latitude and longitude manually with the
option -l.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1144506
Bug ID: 1144506
Summary: sphinx-build requires python-attrs to run but does not
require it
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: dcermak(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The sphinxcontrib-autopgrogram and sphinxcontrib-asyncio packages started to
fail to build on OBS with the following error:
[ 43s] + sphinx-build -b html -d doc/_build/doctrees doc doc/_build/html
[ 43s] Traceback (most recent call last):
[ 43s] File "/usr/bin/sphinx-build", line 6, in <module>
[ 43s] from pkg_resources import load_entry_point
[ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py",
line 3241, in <module>
[ 43s] @_call_aside
[ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py",
line 3225, in _call_aside
[ 43s] f(*args, **kwargs)
[ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py",
line 3254, in _initialize_master_working_set
[ 43s] working_set = WorkingSet._build_master()
[ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py",
line 583, in _build_master
[ 43s] ws.require(__requires__)
[ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py",
line 900, in require
[ 43s] needed = self.resolve(parse_requirements(requirements))
[ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py",
line 786, in resolve
[ 43s] raise DistributionNotFound(req, requirers)
[ 43s] pkg_resources.DistributionNotFound: The 'attrs' distribution was not
found and is required by packaging
[ 43s] error: Bad exit status from /var/tmp/rpm-tmp.tYlY4G (%build)
Both invoke sphinx-build during %build. For some reason sphinx-build appears to
require python-attrs now, but this is not reflected in the rpm. Thus OBS does
not know about this dependency and leaves out python-attrs out of the buildroot
(thereby causing the above error).
Affected packages:
-
https://build.opensuse.org/package/show/devel:languages:python/python-sphin…
-
https://build.opensuse.org/package/show/devel:languages:python/python-sphin…
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111657
Bug ID: 1111657
Summary: python-cffi build fail with glibc maintenance update
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.1
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: mlin(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
With glibc maintenance update https://build.opensuse.org/request/show/639803 ,
python-cffi build failed due to it can not pass unittest[1]. Both package are
from SLE.
[1]
https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1:Stagin…
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149754
Bug ID: 1149754
Summary: Translations are good!
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Translations
Assignee: ke(a)suse.com
Reporter: snwint(a)suse.com
QA Contact: ke(a)suse.com
Found By: ---
Blocker: ---
Weblate creates automated github commits that unfortunately don't align to
the usual workflow as there a bugzilla (or jira) reference is required.
So I've created this bug to auto-add its number to every Weblate commit
message.
--
You are receiving this mail because:
You are on the CC list for the bug.