On Wed, Apr 14, 2010 at 20:00, Niels Breet <ni...@maemo.org> wrote:
>
> As part of this task we need to decide with the 'broken' or affected
> packages which have been built on the PR1.2 SDK and have gotten PR1.2
> dependencies.
The simple thing would be to resubmit all packages which have been
built successfully since the autobuilder SDK change on 2010-03-24[1].
However if that's too complex/too large; alternatively:
1) We identify any package with a known uninstallable dependency
(libhildon >= 2.2.10 being the best example, but there are a
few others); and resubmit them.
2) After that, we email everyone who has uploaded a package in
that time which has been built successfully and ask them to
check their packages (ideally with links to the specific
pages on maemo.org/packages/) and reupload.
Would it also be possible to show, on maemo.org/packages/ - based on
package version constraints - the minimum release required to install
the app?
> We can automatically import all rebuilt packages into extras-devel or we
> can decide to let developers re-submit their packages after the builder
> has been switched to the new setup.
I definitely favour the resubmitting approach. It's easiest for
developers by far; and so in terms of total effort is the lowest
overall.
However, will we have issues with version numbers? If we auto resubmit
them, should we ensure that each package is resubmitted with a new
version number? If so, a suffix of "-20100415" would be sufficient?
Cheers,
Andrew
[1] http://lists.maemo.org/pipermail/maemo-developers/2010-March/025512.html
--
Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
