Invalid username in .cf is handled too late (after upload)
Bug #389709 reported by
LCID Fire
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I tried to upload a package but had an error in my .dput.cf. It let my upload fine and later on complained about not finding the (incorrectly spelled) "person" (via email). First off - the person should be called login name and secondly it would be far better to reject the upload in the first place if no group/user is present.
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| Changed in soyuz: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: ppa soyuz-upload |
| tags: | added: poppy |
To post a comment you must log in.
Okay, that specific error message you mentioned was improved per bug #386242, it now says:
{{{
Launchpad failed to process the upload path '~boing/ppa':
Could not find person or team named 'boing'
It is likely that you have a configuration problem with dput/dupload.
Please check the documentation at https:/
}}}
So, PPAs can be related with a Launchpad person or team, it's not necessarily about your login name.
That said, the second part of the bug is legitimate, it'd be better indeed if the rejection warning was presented synchronous and caused dput to fail.
This bug is part of a set of bugs that urge for a better upload server-side, like bug #136593 and others.