|
rpm id |
test |
status |
message |
|
icon-theme-Sevi-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-black-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-black-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-blue-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-blue-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-brown-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-brown-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-green-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-green-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-grey-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-grey-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-orange-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-orange-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-pink-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-pink-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-purple-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-purple-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-red-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
icon-theme-Sevi-red-dark-20230324-alt1.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |