October 2010 - Arch-dev-public - lists.archlinux.org

[arch-dev-public] [signoff] kernel26-lts 2.6.32.24-1
by Andreas Radke 03 Oct '10

03 Oct '10

Upstream update. Please signoff. Only one Xen related change. -Andy

2 2

Re: [arch-dev-public] [arch-general] packages are newer in extra than in staging
by Allan McRae 03 Oct '10

03 Oct '10

On 03/10/10 09:57, Evangelos Foutras wrote: > On Sun, Oct 3, 2010 at 2:24 AM, Ionuț Bîru<ibiru(a)archlinux.org> 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

2 1

[arch-dev-public] mailman, python24, db4.1, db4.5
by Allan McRae 02 Oct '10

02 Oct '10

Hi, The updated mailman package has been in [testing] for a long time now so I am moving it to [extra]. With this we no longer need python24 in to repos so I will remove that to the AUR. That also removes the need for db4.5, so say bye to that too. And while I am at it, say bye to db4.1 which is no longer needed by anything... The next person to update gerolde should take care with mailman as its install has moved from /home/mailman to somewhere more appropriate. That will probably need some intervention. Allan

1 0

[arch-dev-public] packages are newer in extra than in staging
by Ionuț Bîru 02 Oct '10

02 Oct '10

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ț

1 0

[arch-dev-public] The "Great Python Rebuild of 2010" begins
by Allan McRae 02 Oct '10

02 Oct '10

Hi, I have pushed the new python (3.1) and python2 (2.7) packages to the new [staging] repo so rebuilds can start there. Remember the staging repo should never be used outside a build chroot... If you do, everything python related will break on your system. TUs will not be able to start uploading rebuilds yet as they do not have a staging equivalent, but we will sort something out for them once we get all the db-scripts/devtools changes tested for the main one first. The package pool is going to save us a heap of issues when this gets moved so it is worth the wait. The key things to remember with the rebuild are: - build in clean chroots. Most packages will detect "python2" or "python-2.7" once they see no "python" and use that. Some will need simple patching. - change your dependencies to python2 - check files for #!'s with "/usr/bin/python" or "/usr/bin/env python". If you have those you will need to do a sed to change them to python2. If you come across a package that you can not easily fix, add it to http://wiki.archlinux.org/index.php/DeveloperWiki:Python_Todo_List#Packages… and I will take a look at it. Have fun, Allan

8 27

[arch-dev-public] Mirror status page
by Dan McGee 01 Oct '10

01 Oct '10

We'll bring it up here before we make a more public announcement to iron out any kinks, but it is live and updating once an hour: http://www.archlinux.org/mirrors/status/ -Dan

2 6