x11-wm/dwm-6.0 works fine on my arm netbook. Reproducible: Always
Created attachment 447930 [details] build.log for x11-wm/dwm-6.1
An automated check of this bug failed - the following atom is unknown: x11-wm/dwm Please verify the atom list.
An automated check of this bug succeeded - the previous repoman errors are now resolved.
(In reply to Stabilization helper bot from comment #2) > An automated check of this bug failed - the following atom is unknown: > > x11-wm/dwm > > Please verify the atom list. That's a valid atom. x11-wm/dwm-6.1 is NOT a valid atom. =x11-wm/dwm-6.1 would be nice to have, but the request is for an ARM keyword on whatever is current, which is to say any version, not a very specific one. Please fix that bot.
(In reply to Jeroen Roovers from comment #4) > (In reply to Stabilization helper bot from comment #2) > > An automated check of this bug failed - the following atom is unknown: > > > > x11-wm/dwm > > > > Please verify the atom list. > > That's a valid atom. > > x11-wm/dwm-6.1 is NOT a valid atom. > > =x11-wm/dwm-6.1 would be nice to have, but the request is for an ARM keyword > on whatever is current, which is to say any version, not a very specific one. > > Please fix that bot. Please see the description for the "package list field". Unqualified atoms are not valid in this field.
>(In reply to Jeroen Roovers from comment #4) > =x11-wm/dwm-6.1 would be nice to have, but the request is for an ARM keyword > on whatever is current, which is to say any version, not a very specific one. I believe the point of this field is to provide a list without ambiguity, in that you should pick a version, and then recursively ensure the right dependencies, in order to produce absolutely no confusion ( or choices ) that the arch-tester has to think about. Providing a range opens the possibility that one-or-more possible atoms in the list have dependencies outside the list, which would be illegal. It may be feasible to get a bot to consider this as well, but it dilutes the utility of even having this field if we do that. Arch Testers should thus be told a narrow spec, and only arch testers who are sure they know what they're doing should deviate from that spec. ( And maintainers can then communicate any necessary keywording afterwards just like they do when they bump a version )
add ~arm.
