Mirror prober doesn't know how to generate the filename for binary packages whose version starts with "<some-number>:"

Bug #38256 reported by Guilherme Salgado
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Guilherme Salgado

Bug Description

The mirror prober was thought that to generate the filename for a binarypackagerelease (BPR), all he needed to do was to append a string of the format "_version_architecture.extension" to that binarypackagename. The problem is that we have some BPRs for which this won't work.

For example, we have a binarypackagerelease for the 'xfs', with version '1:1.0.1-0ubuntu2', but the actual filename, as one can see at http://archive.ubuntu.com/ubuntu/pool/universe/x/xfs/ is xfs_1.0.1-0ubuntu2_i386.deb, that is, without the leading '1:' of the version.

I'm tempted to assume that the fix would be to simply remove any number of digits followed by a colon from the version, before appending it to the BPR's name. If this is correct, does it apply to SourcePackageReleases too?

Revision history for this message
Guilherme Salgado (salgado) wrote :

The right thing to do here, as explained by Daniel Silverstone, is to get the binarypackagefile of that BPR and then get the filename from there.

Changed in launchpad:
assignee: nobody → salgado
status: Unconfirmed → Confirmed
Changed in launchpad:
status: Confirmed → Fix Committed
Changed in launchpad:
status: Fix Committed → Fix Released
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.