Links to binary packages from versioned +source drop version

Matt, the source package page has changed substantially since you reported this bug. The page at the first URL you cite seems to no longer link to the second one (or any other URLs of the same type), and nor does the page at the second URL seem to link to the third one. Can you still reproduce this problem at all? If so, can you give an up-to-date example?

On Mon, Jan 28, 2008 at 04:54:31PM -0000, Matthew Paul Thomas wrote:
> Matt, the source package page has changed substantially since you
> reported this bug. The page at the first URL you cite seems to no longer
> link to the second one (or any other URLs of the same type), and nor
> does the page at the second URL seem to link to the third one. Can you
> still reproduce this problem at all? If so, can you give an up-to-date
> example?
>
> ** Changed in: soyuz
> Status: New => Incomplete

This problem (or something like it) is still there; Kiko stumbled across it
the other day while we were on the phone.

--
 - mdz

Is this the same as bug 63808, perhaps? That bug report has still-reproducible steps.

This bug is still here. By loading https://launchpad.net/ubuntu/+source/xorg-server/1:1.0.2-0ubuntu10.3 (working around bug 187376), you can see that the hyperlinks for the binary packages (e.g. xserver-xorg-core) link to pages like https://edge.launchpad.net/ubuntu/dapper/+package/xserver-xorg-core (which, as you can see, refers to version 1:1.0.2-0ubuntu10.10 of the package, not version 1:1.0.2-0ubuntu10.3 as the referring page did)

Retargeting to 3.0, which is the new name for 2.2.9. Haven't renamed the milestone as the 3.0 milestone is in a different series.

Still relevant today.

Have updated the summary. That said, most of the time what we have works ok, so I'm going to drop this to Low - patches appreciated, of course. I suspect its fairly shallow to fix, though care needed to avoid creating timeouts (of course)