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

[arch-dev-public] [signoff] sysvinit-2.88-2
by Eric Bélanger 04 Oct '10

04 Oct '10

Hi, sysvinit-2.88-2 is in testing. Changes: - Add install scriptlet to reload init (close FS#21013). It should fix unclean unmount when the package is updated like Allan reported in the sigonoff thread for sysvinit-2.88-1 Please test and signoff. Eric

3 2

[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

[arch-dev-public] Putting the process of adding new mirrors on hold
by Roman Kyrylych 30 Sep '10

30 Sep '10

Currently we have almost 90 active mirrors in the official mirror list and new requests for becoming an official mirror are appearing quite often. However, not all mirrors are good ones (outdated, incomplete, admins don't respond, etc). I marked inactive many of them during past months (including about 20 during FrOSCon), and will continue to do this until all of the mirrors meet the requirements. 22 mirrors that are in the official list did not move to the 2-tier scheme yet, which means we do not know where do they sync from, admins did not respond or there is no known email address of the admin. These will be removed from the list very soon. If you are using some mirror that was removed from the list recently and you know how to contact the admin - let me know. Considering the fact that there is no package signing support yet I don't see a reason why we should have that many mirrors, especially when they don't meet the requirements. Recently I had to defer some requests to become an official mirror from some private sites. I apologize that this caused a frustration of their admins and hope that the reasons are understandable. To make this fair to everyone I'm thinking about (temporary) putting the process of adding new mirrors on hold. -- Roman Kyrylych (Роман Кирилич)

4 5

[arch-dev-public] Clearing out [testing]
by Allan McRae 29 Sep '10

29 Sep '10

Hi, I want to move the python rebuilds to the [testing] repo after the new GNOME release hits the main repo. So now would be a good time for us to do a clear out of [testing]. Here is a somewhat annotated list of packages currently in the repo: needing signoff: autoconf ed flex hdparm libtool linux-firmware make wpa_supplicant{,_gui} lts-kernel: kernel26-lts kernel26-lts-headers ndiswrapper-lts tiacx-lts xorg-1.9: ati-dri intel-dri libgl mach64-dri mesa mga-dri nouveau-dri nouveau-drm-lts r128-dri savage-dri sis-dri tdfx-dri unichrome-dri xf86-input-* xf86-video-* xkeyboard-config xorg-server xorg-server-common xorg-server-devel xorg-server-xdmx xorg-server-xephyr xorg-server-xnest xorg-server-xvfb texlive: texlive-* misc: cairo dssi fluidsynth hydrogen mailman qt{,-doc} Can their maintainers post a short status for the ones not waiting for a signoff? Allan

11 17

[arch-dev-public] [extra] new package: qt-assistant-compat
by Ronald van Haren 29 Sep '10

29 Sep '10

Hi, I've just added a new package to our svn: qt-assistant-compat. This is a compatibility package for the deprecated qt assistant version which was removed from qt since 4.7.0. Some packages still need it (at least my qtiplot package does, but I'm sure there are others) though, so it will be there if you need it. Obviously I'll remove it again if said packages are updated to the new qt online documentation system. Binary packages will follow if I find some building time. Ronald

1 0