aptitude-0.4.5-alt13.src	specfile-url-is-dead	warn	Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
aptitude-0.4.5-alt13.src	specfile-url-permanent-https-redirect	experimental	Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems; Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems; Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems; Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems; Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems; 
aptitude-0.4.5-alt13.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount 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.; 
aptitude-doc-0.4.5-alt13.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.;