Bugs cannot be filed against packages in the commercial repository.

Bug #58495 reported by Paul Sladen
30
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Julian Edwards

Bug Description

Currently there doesn't seem to be able way to track bugs on packages in the 'dapper-commerical' archive with the Launchpad infrastructure because the packages are not known to Launchpad.

Tags: lp-bugs
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Hi Paul,

what do you mean? If those packages aren't published in LP isn't it a soyuz bug?
Thanks for reporting,

Changed in malone:
status: Unconfirmed → Needs Info
Revision history for this message
Brad Bollenbach (bradb) wrote :

Not enough info from reporter. sladen, please feel free to reopen if you can provide more details about the unique requirements for dapper-commercial.

Changed in malone:
status: Needs Info → Rejected
Revision history for this message
Paul Sladen (sladen) wrote :

Normally when I want to file a bug, I pop over to[1]:

  launchpad.net/.../+source/realplay/+filebug

In the case of 'realplay', this is _not_ published via Soyuz and so does not appear in the Malone system; that is not necessarily a bug with Soyuz/Malone.

Whether, or how to file bugs on software published via the '-commercial' channel is a policy issue that _Canonical_ (as custodian of '-commercial') needs to work out.

mdz/Malcolm: where would be a good place to be able to file bugs on software which falls under this separate category?

[1] (yes, I type in the whole URL, since it's 10x faster than clicking through the webpages...)

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

The reporter has provided more information. But whether this bug is valid is a policy decision, I guess. Should Launchpad (and its bug tracker in particular) know about every package in a distribution, or just about the Free Software packages?

Changed in malone:
assignee: nobody → sabdfl
status: Rejected → Unconfirmed
Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 58495] Re: no way to track dapper-commerical bugs/packages in LP

Yes, bug tracking for these packages should happen in Launchpad.

Mark

Revision history for this message
Malcolm Yates (mdy) wrote : Re: no way to track dapper-commerical bugs/packages in LP

If the bugs are reported in Launchpad ( which woudl sem sensible ), what would be the most effective way of ensuring these are flagged to the company / entity that owns the package ? For each of them to have a launchpad account and transfer the bug report report to their internal tracking process ? Discussion and suggestions welcome, as we currently have no policy on this.

Malc

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: dapper-commercial packages are not represented in Launchpad

Kiko, perhaps we should be running gina or similar on -commercial to bring in these packages?

Alternatively, what would it take to run -commercial in Launchpad rather than externally? That would make this a non-problem.

description: updated
Changed in malone:
assignee: sabdfl → nobody
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Diogo Matsubara (matsubara) wrote :

re-assigning to soyuz, as it doesn't seem to be a malone issue.

Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → cprov
Changed in soyuz:
assignee: cprov → julian-edwards
Revision history for this message
Matti Lindell (mlind) wrote :

ping? any process with this issue?

Changed in soyuz:
status: Confirmed → In Progress
Revision history for this message
Christian Reis (kiko) wrote :

Removing some confusion here. This will be solved with commercial package upload support.

Changed in soyuz:
status: In Progress → Confirmed
description: updated
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Fix committed in RF 4729.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.