Re: packages which have not been rebuild since December 2016
- Date: Wed, 27 Jun 2018 10:09:24 +0200
- From: Andreas Tille <tille@xxxxxxxxxx>
- Subject: Re: packages which have not been rebuild since December 2016
sorry, I've spotted this very late - may be it is helpful anyway.
On Wed, May 30, 2018 at 10:29:24PM +0100, Chris Lamb wrote:
> Hi Holger,
> > One issue we forgot to mention there is that all binary packages built
> > with dpkg < 1.18.17 need to be rebuild. Is that something easy to find
> > out with UDD?
> Unless I'm missing something, I don't think that UDD has this. Whilst
> we have a `packages` relation that can "detect" binNMUs (ie. SELECT *
> FROM packages WHERE version != source_version) there is no timestamp
> on this.
> We have the "upload_history" relation but that will only give us an
> upper limit (roughly 50% of the archive).
Why do you think upload_history would be incomplete.
I wonder whether this query might be helpful. It sorts the Debian
packages according to date in upload_history - you can draw your cutting
line wherever you want.
SERVICE="--host=public-udd-mirror.xvm.mit.edu --username=public-udd-mirror udd"
psql $SERVICE >packages_sort_by_age.txt <<EOT
SELECT u.source, u.version, cast(u.date as date) AS date, s.release, u.maintainer_name, u.changed_by_name, u.signed_by_name FROM (
SELECT source, r.release, strip_binary_upload(MAX(version)) AS version,
row_number() OVER (PARTITION BY source ORDER BY r.sort DESC)
FROM packages p
JOIN releases r ON p.release = r.release
WHERE (r.sort >= (SELECT sort FROM releases WHERE role = 'stable') OR r.sort = 0) -- 0 for experimental
GROUP BY source, r.release, r.sort
JOIN upload_history u ON s.source = u.source AND s.version = u.version
WHERE row_number = 1
ORDER BY date, source
May be you want to drop all non-sid releases since they might be
Hope this helps