Summary: | app-portage/nattka: 'sanity-check' seems to update bugs by default, but claims otherwise | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joshua Kinard <kumba> |
Component: | Current packages | Assignee: | Michał Górny <mgorny> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | ionen, kumba |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joshua Kinard
2024-04-14 23:54:07 UTC
That update was done with the "NATTkA bot" bugzilla account (which runs automatically), unless you have + using the api key for it you can't do that yourself. If used your own api key and without pretend mode, it'd show your own account. Or am I misunderstanding something here? (In reply to Ionen Wolkens from comment #1) > That update was done with the "NATTkA bot" bugzilla account (which runs > automatically), unless you have + using the api key for it you can't do that > yourself. > > If used your own api key and without pretend mode, it'd show your own > account. > > Or am I misunderstanding something here? So the "NATTkA bot" is a completely separate thing from app-portage/nattka? I thought they were related. Does this bot account do stablereq processing entirely on its own shortly after such a bug is created? The nattka bot *is* using app-portage/nattka, just without pretend running on our infra. So I wouldn't call them unrelated -- but you can use it locally yourself (useful to confirm and the like), it just won't be using the same account if you were to actually update bugs. ...which is not something you normally need to do given infra's nattka checks all open keywording/stablereq bugs for updates. Usually pretty fast (few short minutes at most) to pickup changes. Like if added CC-ARCHES keyword, then it'll go ahead and cc amd64@g.o and friends for you after a short wait. Anyhow, the command you ran locally did nothing to the bug. (In reply to Ionen Wolkens from comment #3) > The nattka bot *is* using app-portage/nattka, just without pretend running > on our infra. So I wouldn't call them unrelated -- but you can use it > locally yourself (useful to confirm and the like), it just won't be using > the same account if you were to actually update bugs. > > ...which is not something you normally need to do given infra's nattka > checks all open keywording/stablereq bugs for updates. Usually pretty fast > (few short minutes at most) to pickup changes. Like if added CC-ARCHES > keyword, then it'll go ahead and cc amd64@g.o and friends for you after a > short wait. > > Anyhow, the command you ran locally did nothing to the bug. Yup, so this boils down to a misunderstanding on my part, then. I thought the tool being used locally triggered the bot to do something to a bug. Would explain why there seemed to be a time lag between when I ran the command locally and then the bug got modified by the bot -- automated action on the server. Okay, TIL! |