binary packaging details shows wrong on the +source and +packaging pages

Bug #71545 reported by Robert Collins
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

if you look at https://launchpad.net/products/opensync/+packages, you see

Release series “trunk”
Distribution Release Source Package Version
Ubuntu 6.06 (dapper) opensync
Ubuntu 6.10 (edgy) opensync 0.18-2.2

This suggests it is not packaged in feisty. However, if you jump to https://launchpad.net/distros/ubuntu/feisty/+source/opensync the details there are correct: it links back to https://launchpad.net/products/opensync/trunk as it should.

Changed in launchpad:
status: Unconfirmed → Confirmed
Curtis Hovey (sinzui)
tags: added: package-link
affects: launchpad-foundations → launchpad-registry
Changed in launchpad-registry:
importance: Undecided → Low
status: Confirmed → Triaged
Curtis Hovey (sinzui)
Changed in launchpad-registry:
milestone: none → 3.1.12
Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Low → High
Revision history for this message
Curtis Hovey (sinzui) wrote :

The distro side is also wrong. feisty clearly states that "There is no current release of this source package in The Feisty Fawn", but I see several binaries. There is something wrong in the data or in the rules to get the last published binary.

summary: - packaging details shows wrong on the product side but correct on the
- distro side
+ binary packaging details shows wrong on the +source and +packaging pages
Revision history for this message
Curtis Hovey (sinzui) wrote :

While there is history is versions published in feisty, there is no distroseries.getCurrentSourceReleases(). There appears to be missing data or a bad join in the method that prevents the version from showing in SourcePackagePublishingHistory.

affects: launchpad-registry → soyuz
Changed in soyuz:
importance: High → Low
milestone: 3.1.12 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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