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

[arch-dev-public] linuxpowertop.org patches
by Jan de Groot 18 May '07

18 May '07

Morning, Given our recent firefox SSL problems, and now this one with pidgin: http://bbs.archlinux.org/viewtopic.php?id=33136 I won't include any linuxpowertop patches anymore, I will remove the one from pidgin at least. I wonder if these guys from linuxpowertop.org test their patches, removing a "useless" timer that isn't useless breaks things it seems.

2 1

[arch-dev-public] broken firefox 2.0.0.3-2
by Paul Mattal 18 May '07

18 May '07

The patch introduced in this version breaks my ability to talk to my standard https webserver. The first one or two gets go fine, but after that, nothing.. from same or other https servers, until I restart firefox. Anyone else seeing this large problem? Why are we including this new patch? Is it intended to go in upstream? - P

3 2

[arch-dev-public] 2007.05 Duke ISOs released
by Tobias Powalowski 18 May '07

18 May '07

Hi Archlinux Community, 17th May, 16:10 CEST (Central European Summer Time) it's done final 2007.05 Duke ISOs for i686 and x86_64 are ready :) Get Archlinux ISOs in /iso/2007.05/{i686,x86_64} on your favorite mirror. Download_Wiki: http://wiki.archlinux.org/index.php/Mirrors or Download_Homepage: http://www.archlinux.org/download/>Download_Homepage Please don't forget to check md5sums. Torrents are already up and seeded. Metalink packages will be prepared soon. Changelog to last Voodoo installation ISO: - pacman3 usage - kernel 2.6.21.1 usage Setup changes: - soundcards are now also ordered by hwdetect - rsync has been added to installation environment - proxy support during ftp installation - selection to copy installation network setup to final installed system - selection about keeping package cache during cd/ftp installation - selection of primary pacman sync server added - fixed grub installing on software raid devices Bug collector of fixed showstoppers is here: http://bugs.archlinux.org/task/6767 Feedback about 2007.05 Duke installations is here: http://bbs.archlinux.org/viewtopic.php?pid=251210#p251210 I would like to thank you all, who assisted in testing and of course finding/fixing bugs, you users/devs simply rock. Happy installing and have fun. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

4 4

[arch-dev-public] Old gtkmm package removal
by Jan de Groot 17 May '07

17 May '07

Looking at http://bugs.archlinux.org/task/7180 : We imported these packages (gtkmm1, gtkmm2.2) because we had apps that required it (I remember packaging gtkmm2.2 for passepartout which never made it to our repositories). I already cleaned gtkmm2.2 and libsigc++2, the one left here is gtkmm1 and its dependency libsigc++: [jan@laptop pacman]$ grep gtkmm1 */*/depends extra/ickle-0.3.2-1/depends:gtkmm1 [jan@laptop pacman]$ grep libsigc++ */*/depends | grep -v sigc++2 extra/gtkmm1-1.2.10-2/depends:libsigc++ extra/libicq2000-0.3.2-3/depends:libsigc++ extra/libuta-0.4.4-1/depends:libsigc++ [jan@laptop pacman]$ grep libicq2000 */*/depends extra/ickle-0.3.2-1/depends:libicq2000>=0.3.2 [jan@laptop pacman]$ grep libuta */*/depends [jan@laptop pacman]$ [jan@laptop pacman]$ pacman -Ss ickle extra/ickle 0.3.2-1 ickle - a icq2000 client First, we have ickle, which requires gtkmm1 and libsigc++. Then we have libuta, which is a library used by nothing. Given the fact that gtk1 and especially gtkmm1 is very old and unmaintained, I would like to remove them from the repositories or move them to unsupported. According to archstats, there's 2 users having ickle installed, where we have lots of users who have a different ICQ client installed (gaim/pidgin, kopete and possibly others). What's our opinion on this? Purge or move all these packages?

2 1

[arch-dev-public] Master Server (gerolde.archlinux.org) reboot scheduled for today.
by Dale Blount 17 May '07

17 May '07

It's been a long time coming - we really need to reboot gerolde and apply updates. It's been good to us for 7 months :) Approx 1:30 EDT today I will -Syu and reboot gerolde. Please refrain from uploading packages / updating around this time so it is not interrupted. Kexec should kick in and only require about 60 seconds for a reboot if all works well. Are there any known issues with django and the new python? Or flyspray and the new php? Anything else like that? Thanks, Dale

9 21

[arch-dev-public] Unused websites?
by eliott 16 May '07

16 May '07

Greetings, I was taking a look at the list of websites that AL provides this evening. I ran across a few sites that I had actually forgotten! Arch Artwork Gallery - art.archlinux.org Development Blog - blog.archlinux.org Just curious how much traffic these sites get, and if it would be reasonable to drop them or not. I know I haven't made much use of them in the past. My thinking is as follows: Art.archlinux.org -- This site doesn't seem to get much use. Most of the screenshot action is in the forums, in the screenshot threads. I have seen a few wallpaper threads rolling around in the forums too. blog.archlinux.org -- Not sure how visible this is, and how used it is. I *do* see posts on it, but hardly ever any comments. I do not know how much community engagement it has. If it is just "one more place for noise", perhaps we could just drop that, and post those type of news items on the front page along with other news. Thoughts? Ideas?

6 12

Re: [arch-dev-public] test
by Aaron Griffin 16 May '07

16 May '07

On 5/15/07, Aaron Griffin <aaronmgriffin(a)gmail.com> wrote: > On 5/15/07, Aaron Griffin <aaronmgriffin(a)gmail.com> wrote: > > gerolde reboot, testing the ml > > > > Away we go, mailman upgraded.... anything borked? > Omg brokens?

2 1

[arch-dev-public] test
by Aaron Griffin 15 May '07

15 May '07

gerolde reboot, testing the ml

1 0

[arch-dev-public] FTP (re)organization
by Thomas Bächler 15 May '07

15 May '07

While discussing with Dale about where to put the new isos, the issue of the ftp organization came up: Right now, we have subdirectories, 0.1, ..., 0.8 and current is a symlink to 0.8. This is bad for several reasons. It suggests that we have a "release", which we don't. And everytime we release a new version, we move 0.X to 0.Y, and re-set the current symlink, that means the mirrors will re-pull all the current packages (which they already have, but download anyway). I suggest doing this for cleanup: - rm current; mv 0.8 current (I know this will cause the same problem as described above, but at least it will be the last time) - rm release - remove all isos from current/iso/* and replace them with the new ones (this means we won't keep the old isos, but do we need them?) - ln -s current/iso iso-download so that people can find the isos more easily on the mirror. Any objections/suggestions?

10 23

[arch-dev-public] duke isos i686 ready for testing
by Tobias Powalowski 14 May '07

14 May '07

Hi guys just to inform you new duke isos are hosted here meanwhile: http://www.archlinux.org/~tpowa/duke-isos/ they are not tested yet at all, will do some tests tomorrow, if you have time try to break them here is the changelog: Hi Arch community, Arch Linux Duke Changelog to last Voodoo installation ISO: - pacman3 usage - kernel 2.6.21.1 usage Setup changes: - soundcards are now also ordered by hwdetect - rsync has been added to installation environment - proxy support during ftp installation - selection to copy installation network setup to final system - selection about keeping package cache during cd/ftp installation - selection of primary pacman sync server added greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

5 13