+addpackage oopses if the "Source Package Name" is left blank

Bug #344376 reported by Ursula Junque on 2009-03-17
10
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Curtis Hovey

Bug Description

Steps to reproduce:

1) Go to a project which you have admin permissions, I created https://staging.launchpad.net/foobar2 for that
2) Go to foobar2/trunk/+addproject page
3) Without filling in the Source Package Name field, click on Continue
4) OOPS-1172S158, KeyError: 'sourcepackagename'

More: OOPS-1204H98

Related branches

Curtis Hovey (sinzui) wrote :

Clearly there is a required field that is not marked as such, or the view assumes it will always be passed.

Changed in launchpad-registry:
importance: Undecided → Low
status: New → Triaged
Ursula Junque (ursinha) on 2009-04-23
description: updated
Curtis Hovey (sinzui) on 2009-10-09
tags: added: package-link
removed: registry-projects
Curtis Hovey (sinzui) on 2009-10-16
Changed in launchpad-registry:
importance: Low → High
status: Triaged → In Progress
assignee: nobody → Curtis Hovey (sinzui)
milestone: none → 3.1.10
summary: - in +addpackage in a project, it oopses if the "Source Package Name" is
- left blank
+ +addpackage oopses if the "Source Package Name" is left blank
Curtis Hovey (sinzui) wrote :

Fixed in launchpad devel r9727.

Changed in launchpad-registry:
status: In Progress → Fix Committed

Fixed released in launchpad-project 3.1.10.

Changed in launchpad-registry:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers