I've only _just_ noticed that the metadata in profiles.desc for bsd is out-dated compared to bugzilla: # Gentoo/FreeBSD Profiles # @MAINTAINER: bsd@gentoo.org amd64-fbsd default/bsd/fbsd/amd64/11.1 exp amd64-fbsd default/bsd/fbsd/amd64/11.1/clang exp x86-fbsd default/bsd/fbsd/x86/11.1 exp Have I misunderstood something, or should these be grouped with the proper relevant aliases? And more-over, where does mail to bsd@ go, and is it the same audience as x86-fbsd@, amd64-bsd@ ? Yes, I know, nobody cares. But I find things like this.
It's intentional. *-fbsd@ aliases cover specific arch-testing, while bsd@ covers maintaining everything.
(In reply to Michał Górny from comment #1) > It's intentional. *-fbsd@ aliases cover specific arch-testing, while bsd@ > covers maintaining everything. Its just due to this indirection I managed to not CC the right teams in some former keyword requests :(. Can both sets of aliases be mentioned?
(In reply to Kent Fredric (IRC: kent\n) from comment #2) > (In reply to Michał Górny from comment #1) > > It's intentional. *-fbsd@ aliases cover specific arch-testing, while bsd@ > > covers maintaining everything. > > Its just due to this indirection I managed to not CC the right teams in some > former keyword requests :(. You seem to be confusing profiles and arches. Did you CC me for arch testing amd64 on 17.1 profiles? ;-P > Can both sets of aliases be mentioned? I don't really care. Gentoo/FreeBSD is dead anyway, so whether you mail one, the other or the pope himself, nothing's gonna happen.
(In reply to Michał Górny from comment #3) > (In reply to Kent Fredric (IRC: kent\n) from comment #2) > > (In reply to Michał Górny from comment #1) > > > It's intentional. *-fbsd@ aliases cover specific arch-testing, while bsd@ > > > covers maintaining everything. > > > > Its just due to this indirection I managed to not CC the right teams in some > > former keyword requests :(. > > You seem to be confusing profiles and arches. Did you CC me for arch > testing amd64 on 17.1 profiles? ;-P Its just there isn't currently a better file for this data, so profiles.desc contains a /defacto/ set of metadata allowing you to correlate arch and profile. If there's a better file for this I've overlooked, I'm all ears. > > > Can both sets of aliases be mentioned? > > I don't really care. Gentoo/FreeBSD is dead anyway, so whether you mail > one, the other or the pope himself, nothing's gonna happen. Sure, probably. I just like to make sure at least _I_ took reasonable steps to informing whoever might care, and give them some time to respond. If they don't, that's on them :) Its self-imposed bureaucracy I guess.
You're really supposed to use arch chooser from bugzilla.
(In reply to Michał Górny from comment #5) > You're really supposed to use arch chooser from bugzilla. I have tooling that spits out all the CC's I need (well, it was _supposed_ to), because the frequent large keyword reqs I do tended towards having problems mentally transferring the data to a stupid user interface. Clearly _how_ that works on my side needs to be improved, but I'm not sure which data-source I should use to improve that.
I just told you. That little list is reference source of arches, arch teams and whether they have stable keywords.
(In reply to Michał Górny from comment #7) > I just told you. That little list is reference source of arches, arch teams > and whether they have stable keywords. Maybe I can phrase it differently: Is there a web-accessible URL I can point something like `curl` at and get a JSON mapping or something? Or is hand-transferring it from the web-page about as good as I'm gonna get?
*-fbsd is gone.