Dear Maintainer,

I tried to download the source package of squid3 but got a 404.

I figure out that the link is broken:

http://httpredir.debian.org/debian/pool/updates/main/s/squid3/squid3_3.4.8-6+deb8u4.dsc

It should be

http://httpredir.debian.org/debian/pool/main/s/squid3/squid3_3.4.8-6+deb8u4.dsc

The “/updates/” should not be there.

Regards.

Hi,

Right. The problem is that the package first appeared on
security.debian.org, the "directory" field of the Sources entry was
associated to the source package and when the package moved to the main
mirror it was not updated.

This is a problem with the data model used by the tracker. The "directory"
field should never have been associated to a SourcePackage but to
its associated SourcePackageRepositoryEntry. After all the package can
reside on two mirrors in different locations while still being the same
package.

This fix is not hard but not trivial either since we have to handle a
database schema update and adjust the code accordingly. We will also have
to adjust some code to have a way to force an update of the field.

Cheers,

Happened today with:
https://tracker.debian.org/pkg/pyjwt

Paolo

I started to work on this issue. The migration itself (both schema and data) is pretty straightforward. However, the rest of the code refactoring will take bit of time.

Could you please clarify if the "directory" field should be a part of the SourcePackageRepositoryEntry model, or a part of the Repository model?

Right now, I have it as a part of the SourcePackageRepositoryEntry model (because that is what made sense in my mind) but I wanted to double check to make sure I was on the right track.

Best,
Lev

Hi,

I think I have been quite clear. The "directory" field should be part of
the SourcePackageRepositoryEntry model (and not the SourcePackage model
where it currently resides).

Cheers,

 Hi, it's me Ken. Did you have an opportunity to look at my email?