|
rpm id |
test |
status |
message |
|
icon-theme-Tela-20230203-alt2.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-Tela-black-20230203-alt2.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-Tela-black-dark-20230203-alt2.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-Tela-blue-20230203-alt2.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-Tela-blue-dark-20230203-alt2.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-Tela-brown-20230203-alt2.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-Tela-brown-dark-20230203-alt2.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-Tela-dark-20230203-alt2.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-Tela-dracula-20230203-alt2.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-Tela-dracula-dark-20230203-alt2.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-Tela-green-20230203-alt2.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-Tela-green-dark-20230203-alt2.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-Tela-grey-20230203-alt2.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-Tela-grey-dark-20230203-alt2.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-Tela-manjaro-20230203-alt2.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-Tela-manjaro-dark-20230203-alt2.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-Tela-nord-20230203-alt2.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-Tela-nord-dark-20230203-alt2.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-Tela-orange-20230203-alt2.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-Tela-orange-dark-20230203-alt2.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-Tela-pink-20230203-alt2.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-Tela-pink-dark-20230203-alt2.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-Tela-purple-20230203-alt2.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-Tela-purple-dark-20230203-alt2.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-Tela-red-20230203-alt2.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-Tela-red-dark-20230203-alt2.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-Tela-ubuntu-20230203-alt2.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-Tela-ubuntu-dark-20230203-alt2.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-Tela-yellow-20230203-alt2.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-Tela-yellow-dark-20230203-alt2.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. |