Can't remove (still existing) organization.

[rustonaut]

Current Behavior

Removing org fails:

╚☛ cargo owner --remove github:dac-gmbh:rust
    Updating crates.io index
       Owner removing ["github:dac-gmbh:rust"] from crate vec1
error: failed to remove owners from crate vec1

Caused by:
  api errors (status 200 OK): could not find the github team dac-gmbh/rust

Expected Behavior

Removing org/team does not fail.

Steps To Reproduce

Likely not possible to reproduce without my auth token.

Environment

• OS: GNU/Linux 5.18.0-arch1-1 x86_64

Anything else?

The user is listed:

╚☛ cargo owner --list
    Updating crates.io index
rustonaut (Philipp Korber)
github:dac-gmbh:rust (rust)

This affects all crates on which I need to remove the org:

• media-type
• vec1
• quoted-string
• soft-ascii-string
• total-order-multi-map
• vec-drain-where
• (more see below)

Context:

I'm currently the only member of the dac-gmbh github org, and the rust team. I do have owner rights (in github).
I plan to delete/archive the org. But I still want to at least passive maintain some of the repositories. I'm user-owner of all crates in that list (like shown in the owner list command above).

I could delete the team/org but then I end up with issue #1818 .

I'm worried that if I delete the org and someone else crates a org with the same name they could take over some of the crates.

Because of this I think the org should also be removed from the other crates it's on (they are all in the same situation as the first list, but I currently have not time to care about them):

• galemu
• lut
• mail
• mail-cars
• media-type-impl-util
• new-tokio-smtp

And while I currently mainly care about the first list I might come back to some of them if I happen to have more time again (the reason I'm running into it now and not over a year ago is because I didn't had any time for hobby open source work on github).

My speculation is that the reason might lie with github I don't remember but I think the org might have been a payed org in the past but now obviously isn't anymore.

[rustonaut]

Actually not an issue: It turns out re-logging in to crates.io triggered an updated to the Github authorization after which the issue went away.