Re: [arch-dev-public] [arch-general] packages are newer in extra than in staging

On 03/10/10 09:57, Evangelos Foutras wrote:

On Sun, Oct 3, 2010 at 2:24 AM, Ionuț Bîru wrote:

...

Hi,

some packages have been updated in extra and have been mark as done in the python todo list but they weren't rebuilt against staging.

looking quick on the list, django (staging removed on 9 september)

extra 1.2.3-1 marked as done and nothing in staging.

mercurial 1.6.4-1 in extra, 1.6.3-2 in staging

please, check your packages again because i don't intent to fix any of this inconsistencies

-- Ionuț

I wrote a script [1] to check for packages in [staging] and [community-staging] that are not newer than their [core], [extra] and [community] counterparts.

So, below are a few more possibly problematic packages. mercurial isn't included because the ABS tree hasn't been updated with it yet.

==> Checking [staging] denyhosts (2.6-4 isn't newer than 2.6-4 in [extra]) python-pip (0.8-2 isn't newer than 0.8.1-1 in [extra]) python-virtualenv (1.4.9-2 isn't newer than 1.5.1-1 in [extra])

==> Checking [community-staging] cdemu-client (1.2.0-2 isn't newer than 1.3.0-1 in [community]) griffith (0.11-3 isn't newer than 0.11-3 in [community]) lilypond (2.12.3-5 isn't newer than 2.12.3-6 in [community]) openshot (1.2.2-1 isn't newer than 1.2.2-1 in [community]) python-sphinx (1.0.3-2 isn't newer than 1.0.4-1 in [community]) recoll (1.13.04-3 isn't newer than 1.14.2-1 in [community]) trac (0.12-3 isn't newer than 0.12-4 in [community])

Thanks. I have re-flagged those packages on the TODO list. Everyone, please be careful when updating packages. Either update them in only in the [staging] repo or _both_ the main repo and the staging one. Allan