Please create a component for deb.tpo

It's the second time that I wanted to report an issue about deb.tpo and I had no proper component to use. I think that's a sign we need one.

weasel, what do you think of adding one? Would you be fine owning that component?

added component::internal services/service - trac owner::qbi priority::medium resolution::fixed severity::normal status::closed type::task labels

Ticket #10899 (moved) would belong to such a component.

Ticket #18871 (moved) and #18868 (moved) would also belong there so please create it.

Trac:
Status: new to assigned
Sponsor: N/A to N/A
Severity: N/A to Normal
Reviewer: N/A to N/A
Owner: N/A to qbi

Trac:
Status: assigned to new

A component for deb.tpo is fine. However, we need to make it clear that this is for tickets about the repository, and not for any issues in the .debs themselves.

I created a component called Internal Services/Debian repository and also left a description to make it clear that this is not about issues in .debs.

Trac:
Resolution: N/A to fixed
Status: new to closed

Replying to weasel:

A component for deb.tpo is fine. However, we need to make it clear that this is for tickets about the repository, and not for any issues in the .debs themselves. Would #18871 (moved) fall under the issues in .debs category? If so, what would the appropriate component be for these types of tickets?

It seems older, similar tickets were filed under Core Tor/Tor. So I also changed the component this way.

closed