Thanks in advance.
fatsort-1.1.331 has been removed from the tree. The upstream version scheme which added the subversion revision number after the normal version caused incorrect sorted versions. All versions in tree now have the revision number removed. Please stabilize sys-fs/fatsort-1.1.1 instead.
dependency.bad 16 sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop/gnome) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop/kde) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(default/linux/amd64/13.0/developer) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: x86(default/linux/x86/13.0) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: x86(default/linux/x86/13.0/desktop) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: x86(default/linux/x86/13.0/desktop/gnome) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: x86(default/linux/x86/13.0/desktop/kde) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: x86(default/linux/x86/13.0/developer) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(hardened/linux/amd64) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib/selinux) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: amd64(hardened/linux/amd64/selinux) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: x86(hardened/linux/x86) ['dev-util/bbe'] sys-fs/fatsort/fatsort-1.1.1.ebuild: DEPEND: x86(hardened/linux/x86/selinux) ['dev-util/bbe'] http://blogs.gentoo.org/ago/2012/07/06/repoman-check-before-file-stable-request/
I could have mentioned this before, but yes dev-util/bbe needs to be stabilized as well. Maybe I am wrong but I was under the impression that dependency stabilization is implied.
(In reply to Daniel Pielmeier from comment #3) > Maybe I am wrong but I was under the impression that > dependency stabilization is implied. I don't know if you judge that dep ready for the stabilization or not, this is the reasone because I like to see all packages in the summary
(In reply to Agostino Sarubbo from comment #4) > (In reply to Daniel Pielmeier from comment #3) > > Maybe I am wrong but I was under the impression that > > dependency stabilization is implied. > > I don't know if you judge that dep ready for the stabilization or not, this > is the reasone because I like to see all packages in the summary Nowadays I do so but this time I simply forgot about it.
amd64 stable
x86 stable. Last arch, closing