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

[arch-dev-public] [signoff] wget 1.11.3-1
by Andreas Radke 17 Jun '08

17 Jun '08

* Changes in Wget 1.11.3 ** Downgraded -N with -O to a warning, rather than an error. ** Translation updates - in testing for both arches, please signoff. Andy

3 2

[arch-dev-public] Adding keytouch and keytouch-editor in [extra]
by Eric Belanger 16 Jun '08

16 Jun '08

Hi, I would like to add both keytouch and keytouch-editor to [extra]. I currently maintain them in community. I am currently cleaning up my packages in AUR/community and considering moving most (perhaps all) of the remaining to extra to centralize my packaging to the official repos. I'll let you know at the time, for now it's just keytouch and keytouch-editor that I plan to move. At last, keytouch and keytouch-editor have 48 and 44 votes, respectively. Any objections? Thanks, Eric -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 2

[arch-dev-public] GCC update in core and kernels
by Jan de Groot 15 Jun '08

15 Jun '08

I noticed GCC has been moved to the core repository today. AFAIK, modules built with GCC 4.3.1 won't load in a kernel compiled with GCC 4.3.0 and the other way around. If this really is the case, we should rebuild the kernel and all modules with the new GCC and while we're at it, close some bugreports that require a rebuild of the kernel and all modules also.

2 1

[arch-dev-public] [signoff] new toolchain
by Andreas Radke 15 Jun '08

15 Jun '08

I've updated both architectures to: gcc-libs-4.3.1-1 gcc-4.3.1-1 - minor bugfixes kernel-headers-2.6.25.6-1 glibc-2.8-1 - major bump binutils-2.18-7 - minor fixes tzdata-2008c-1 glibc doesn't ship tarballs anymore. we use cvs checkouts from the stable branch. so we get all latest bugfixes that went upstream. we do it the same way now for binutils. please test these packages a bit more intensive. some gcc related updates for packages in extra will follow soon. please signoff after testing. (my own "will OpenOffice build and run" test is still pending) When the toolchain has moved to core I plan to update "db" with another nice .so bump... -Andy glibc changes: Version 2.8 * New locales: bo_CN, bo_IN. * New encoding: HP-ROMAN9, HP-GREEK8, HP-THAI8, HP-TURKISH8. * Sorting rules for some Indian languages (Devanagari and Gujarati). Implemented by Pravin Satpute. * IPV6 addresses in /etc/resolv.conf can now have a scope ID * nscd caches now all timeouts for DNS entries Implemented by Ulrich Drepper. * nscd is more efficient and wakes up less often. Implemented by Ulrich Drepper. * More checking functions: asprintf, dprintf, obstack_printf, vasprintf, vdprintf, and obstack_vprintf. Implemented by Jakub Jelinek. * Faster memset for x86-64. Implemented by Harsha Jagasia and H.J. Lu. * Faster memcpy on x86. Implemented by Ulrich Drepper. * ARG_MAX is not anymore constant on Linux. Use sysconf(_SC_ARG_MAX). Implemented by Ulrich Drepper. * Faster sqrt and sqrtf implemention for some PPC variants. Implemented by Stephen Munroe.

4 7

[arch-dev-public] [signoff] kernel26 2.6.25.6-1
by Thomas Bächler 14 Jun '08

14 Jun '08

Updated to new stable release. There are some security fixes, so I apologize for the delay and hope you guys sign off on it quickly. I had no time to look at the numerous other bugs, so this is only the update to the latest stable. Packages should be up in testing in a few minutes.

3 2

[arch-dev-public] On the road to KDE 4.1
by Pierre Schmitz 12 Jun '08

12 Jun '08

Hey guys, I have made some packages of the first beta release of KDE 4.1. I had to update some dependencies and put them into [testing]. I also cleaned up the QT package. Due to a file conflict with kdelibs-4 I disabled phonon. The PKGBUILDs are built from scratch and I tried to keep it as simple as possible. This is more a test on how to package this stuff rather then testing the next kde itself. My suggestion would be: Let's create a kde-repo on top of our testing repo and see how we can package it and manage the transition from kde3. I have setup such a repo as an example: [kde-testing] http://users.archlinux.de/~pierre/kde-testing/x86_64/ There are the most important parts of KDE and in addition to this an example of how we could handle old packages which depend on KDE3: kaffeine. I would like to see some comments about this and some help would be nice, too. :-) Before putting this into you pacman.conf, please read this: This repo is just for testing packaging. It's incomplete and will break things. You should uninstall all kde3-stuff before: pacman -Rcsn kde Last but not least: especially to all "adventurous users" out there: please don't use this repo if you just want to have a look at the next kde; use one of the live-cds instead. Pierre -- http://www.archlinux.de

6 12

[arch-dev-public] [signoff] findutils-4.4.0-1
by Eric Belanger 12 Jun '08

12 Jun '08

In testing for both arches. Please signoff. Changes: - Upstream update to 4.4.0 - Updated license to GPL3 - Rebuilt against testing toolchain. Should be moved to core at the same time than the toolchain. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[arch-dev-public] Where is cactus?
by Grigorios Bouzakis 12 Jun '08

12 Jun '08

Hi, i seem to be having trouble finding elliot under the assignees list in flyspray. Anyone have any idea whats going on? I guess he is still part of the crew and its a weird flyspray bug of some sort. Greg

3 2

[arch-dev-public] maintainers wanted
by Andreas Radke 11 Jun '08

11 Jun '08

I want to concentrate more on packages that take much time like OOo and our toolchain. In the past I adopted many packages just to solve the orphan state. So I'd like to give away a few of my packages I don't use myself: cyrus-sasl cyrus-sasl-plugins maybe gnash (i'm using swfdec most time) ntp procmail python ruby tcl/tk opera-devel Maybe some more. If you want to adopt one of these or any other of my packages just drop me a mail or catch me on irc or any messenger. -Andy

2 1

[arch-dev-public] Repo cleanup / Package adoption
by Eric Belanger 10 Jun '08

10 Jun '08

Hi, This is yet another repo cleanup package adoption thread. There hasn't been much feedback when I last brought up the subject so let's try to fix this once for all. This is an important issue. The cleanup is mostly done. The current issue is orphaned (make)depends. I'll repeat the process. Go to https://dev.archlinux.org/wiki/Repo%20Cleanup/ There is the list of orphans and the packages that depends on them. The name of the maintainer of the package depending on orphans is also listed so just search for your name. It's as simple as that so it only takes a few minutes. Keep in mind that these orphanes are in the repo because YOUR package depends on them so they need to be maintained as well. There are still orphaned core packages. Of course, anyone is free to adopt any orphans that they wish. Once you adopted some packages, remove them from the list to keep the list up-to-date. You can also post the list of packages you have adopted in this thread and I'll take care of removing them from the wiki list. Either way, please reply in this thread to confirm that you went through the list. That will give me an idea on how many devs have checked the list. However, it is possible that some of you already have the maximum workload that they can handle so they can't really adopt any or all of their packages' orphaned depends. At least, check the list to see if your packages depends on orphaned packages and let us know. Perhaps someone else, who can add to their current workload, would be willing to adopt some of these orphans especially if they use the package that depends on them. I'm sure we'll be able to split the present orphans workload somehow between us. Currently, we just need an idea on the current workload state. In summary, we should ideally get a reply in this thread from every active dev confirming that they went though the wiki list and: a) have adopted all or some of their "assigned" orphans and have modified the list accordingly or b) have adopted all or some of their "assigned" orphans and posted a list here so I can update the wiki and/or c) have adopted none or only some of their "assigned" orphans because of too high workload or other reason. Two other points: I would like to remind everyone that after adding a package in the repo or moving it to another repo, don't forget to adopt it afterwards in the dashboard. I believe that's one reason explaining why several packages are currently orphaned. I haven't updated the wiki list since the last time except a when I happen to stumble on a new orphan so it might be slightly out-of-date compared to the dashboard orphans. When it'll be significantly smaller, I'll update it. Thanks for your cooperation, Eric -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

12 25