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

[arch-dev-public] [signoff] nfs-utils 1.1.3-2
by Ronald van Haren 07 Oct '08

07 Oct '08

please signoff for both archs Ronald

3 4

[arch-dev-public] Mono upgrade to 2.0
by Daniel Isenmann 07 Oct '08

07 Oct '08

Hi all, I'm planning the upgrade of Mono to version 2.0. I will rebuild all necessary packages and update them, too. (For example: boo) So, if anyone maintain a package which is affected, just like the mentioned "boo", you don't have to do anything. I will build and package those in one run for both architectures if it's necessary. Daniel

2 1

[arch-dev-public] [idea] Kernel Release Policy
by Jud 07 Oct '08

07 Oct '08

Hi Devs, Please do not take this a complaint, I am a fan of consistent improvement and I hope after reading this you'll agree there is some room for improvement and by working together it can be realised. After the disaster of early the early upstream kernel 2.6.25 releases (many annoying minor problems that shouldn't have happend and the quick concession of updates) and the recent wake-up call of 2.6.27-RCs [1] I felt compelled to write this, so Arch won't be doomed to let history repeat. I think Arch should be smarter about the way it handles it's kernel releases and I present an idea for discussion. - The current [core] kernel 2.6.x release is always updated until it really makes sense to update to the next .x version. - The latest "stable" kernel is always available in [testing/unstable] for the bleeding-edge crowd. - This "policy" is announced to inform the user-base via Forum, Website, Newsletter, Mailing-List so to avoid any confusion. Optional: - A criteria is created and met so the next kernel version can be throughly tested and pushed for a seamless user upgrade. - Multiple Kernel Maintainers is implemented and eventually all Arch core developers could release a perfect kernel. Let me explain what usually happens: 2.6.27.0 will come out, about the same time a 2.6.26.6 will be released Arch will abandon .26.y and start testing .27.0. Somethings will break, then get fixed, etc until everyone is happy and ready to release. Meanwhile 26.y might be at .9 with many important fixes that cannot be used. I know there is ABS but this is from a multiple computers systems and the community as a whole point-of-view. So my major point is: The only thing I want to really change is while the newer .x kernel is been prepped for released, Arch does not abandon the current .x kernel. Benefits: - Arch remains "stable" while still maintaining it's "bleeding edge" aura - Lot less breakages and complaints - Smoother workflow and more development/bug-squashing time for Devs Thanks for your time, and I hope this discussion is taken in the right way as it serves only to improve Arch and it's users computing experience. PS:- I already have had some positive feedback and as a result I present some ideas on the co-existing kernels problem, open for disscussion. a) The testing kernel package is named slightly different with the 'replaces/force' PKGBUILD magic. Once the testing kernel proves stable/ready enough for a [core] release (usually about version 2.6.x.5) rename and push out, this only really affects the testing people who would easily have the skills to overcome any problems b) Use another Repo, I know [unstable] was killed off but as dumb as it sounds, perfect for this task. c) The current kernel in [core] the .y updates get tested "behind-the-scenes" and then move straight into [core], with the next .x kernel in [testing] [1] http://www.phoronix.com/scan.php?page=news_item&px=Njc0Nw

4 3

[arch-dev-public] Repository Maintenance 06-10-2008 21:00
by repomaint＠archlinux.org 07 Oct '08

07 Oct '08

Scan complete for core (i686) at /home/ftp/core/os/i686/ The following files are out of date They will be moved to /home/package-cleanup initscripts-2008.08-1-i686.pkg.tar.gz klibc-1.5-6-i686.pkg.tar.gz klibc-extras-2.4-2-i686.pkg.tar.gz klibc-kbd-1.15.20080312-6-i686.pkg.tar.gz klibc-module-init-tools-3.4-1-i686.pkg.tar.gz klibc-udev-116-4-i686.pkg.tar.gz udev-119-1-i686.pkg.tar.gz Scan complete for core (x86_64) at /home/ftp/core/os/x86_64/ The following files are out of date They will be moved to /home/package-cleanup initscripts-2008.08-1-x86_64.pkg.tar.gz klibc-1.5-6-x86_64.pkg.tar.gz klibc-extras-2.4-2-x86_64.pkg.tar.gz klibc-kbd-1.15.20080312-6-x86_64.pkg.tar.gz klibc-module-init-tools-3.4-1-x86_64.pkg.tar.gz klibc-udev-116-4-x86_64.pkg.tar.gz udev-119-1-x86_64.pkg.tar.gz Scan complete for extra (i686) at /home/ftp/extra/os/i686/ The following files are out of date They will be moved to /home/package-cleanup banshee-1.2.1-2-i686.pkg.tar.gz hal-0.5.11-1-i686.pkg.tar.gz ipod-sharp-0.8.0-1-i686.pkg.tar.gz pm-utils-1.2.1-1-i686.pkg.tar.gz v86d-0.1.5.2-1-i686.pkg.tar.gz Scan complete for extra (x86_64) at /home/ftp/extra/os/x86_64/ The following files are out of date They will be moved to /home/package-cleanup hal-0.5.11-1-x86_64.pkg.tar.gz v86d-0.1.5.2-1-x86_64.pkg.tar.gz Scan complete for testing (i686) at /home/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /home/package-cleanup hal-0.5.11-4-i686.pkg.tar.gz initscripts-2008.09-2-i686.pkg.tar.gz klibc-1.5.14-1-i686.pkg.tar.gz klibc-extras-2.5-1-i686.pkg.tar.gz klibc-kbd-1.15.20080312-7-i686.pkg.tar.gz klibc-module-init-tools-3.4-2-i686.pkg.tar.gz klibc-udev-128-1-i686.pkg.tar.gz udev-128-5-i686.pkg.tar.gz v86d-0.1.7-1-i686.pkg.tar.gz Scan complete for testing (x86_64) at /home/ftp/testing/os/x86_64/ The following files are in the repo but not the db They will be moved to /home/package-cleanup hal-0.5.11-4-x86_64.pkg.tar.gz initscripts-2008.09-2-x86_64.pkg.tar.gz klibc-1.5.14-1-x86_64.pkg.tar.gz klibc-extras-2.5-1-x86_64.pkg.tar.gz klibc-kbd-1.15.20080312-7-x86_64.pkg.tar.gz klibc-udev-128-1-x86_64.pkg.tar.gz udev-128-5-x86_64.pkg.tar.gz v86d-0.1.7-1-x86_64.pkg.tar.gz

1 0

[arch-dev-public] Repository Maintenance 06-10-2008 15:00
by repomaint＠archlinux.org 06 Oct '08

06 Oct '08

Scan complete for core (i686) at /home/ftp/core/os/i686/ The following files are out of date They will be moved to /home/package-cleanup pptpclient-1.7.1-3-i686.pkg.tar.gz Scan complete for core (x86_64) at /home/ftp/core/os/x86_64/ The following files are out of date They will be moved to /home/package-cleanup pptpclient-1.7.1-3-x86_64.pkg.tar.gz Scan complete for testing (i686) at /home/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /home/package-cleanup pptpclient-1.7.2-1-i686.pkg.tar.gz Scan complete for testing (x86_64) at /home/ftp/testing/os/x86_64/ The following files are in the repo but not the db They will be moved to /home/package-cleanup pptpclient-1.7.2-1-x86_64.pkg.tar.gz

1 0

[arch-dev-public] draft klibc move news item
by Allan McRae 06 Oct '08

06 Oct '08

Hi all, We need a news item for the klibc move to [core] due to the whole "349 lines of file conflict messages" thing... [draft] klibc upgrade requires user intervention Due to a limitation in how pacman handles conflict checking and symlinks to directories, the upgrade to klibc-1.5.14-1 requires the manual removal of a symlink prior to updating. Please do a "rm /usr/lib/klibc/include/asm" to remove the symlink that causes lots of false file conflicts. [/draft] Sounds fine? Allan

3 2

[arch-dev-public] Repository Maintenance 06-10-2008 06:00
by repomaint＠archlinux.org 06 Oct '08

06 Oct '08

Scan complete for core (i686) at /home/ftp/core/os/i686/ The following files are out of date They will be moved to /home/package-cleanup bridge-utils-1.2-2-i686.pkg.tar.gz Scan complete for core (x86_64) at /home/ftp/core/os/x86_64/ The following files are out of date They will be moved to /home/package-cleanup bridge-utils-1.2-2-x86_64.pkg.tar.gz Scan complete for extra (i686) at /home/ftp/extra/os/i686/ The following files are out of date They will be moved to /home/package-cleanup libdvdcss-1.2.9-2.pkg.tar.gz libpng-1.2.31-1-i686.pkg.tar.gz quilt-0.46-2-i686.pkg.tar.gz scons-0.98.5-1-i686.pkg.tar.gz sip-4.7.7-1-i686.pkg.tar.gz swig-1.3.31-1.pkg.tar.gz unrar-3.8.2-1-i686.pkg.tar.gz whois-4.7.24-1-i686.pkg.tar.gz Scan complete for testing (i686) at /home/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /home/package-cleanup bridge-utils-1.4-2-i686.pkg.tar.gz Scan complete for testing (x86_64) at /home/ftp/testing/os/x86_64/ The following files are in the repo but not the db They will be moved to /home/package-cleanup bridge-utils-1.4-2-x86_64.pkg.tar.gz

1 0

[arch-dev-public] Repository Maintenance 06-10-2008 03:00
by repomaint＠archlinux.org 06 Oct '08

06 Oct '08

Scan complete for core (i686) at /home/ftp/core/os/i686/ The following files are out of date They will be moved to /home/package-cleanup atl2-2.0.4-4-i686.pkg.tar.gz cracklib-2.8.13-1-i686.pkg.tar.gz iputils-20070202-4-i686.pkg.tar.gz linux-atm-2.4.1-3-i686.pkg.tar.gz pciutils-3.0.1-1-i686.pkg.tar.gz Scan complete for core (x86_64) at /home/ftp/core/os/x86_64/ The following files are out of date They will be moved to /home/package-cleanup atl2-2.0.4-4-x86_64.pkg.tar.gz cracklib-2.8.12-1-x86_64.pkg.tar.gz iputils-20070202-4-x86_64.pkg.tar.gz linux-atm-2.4.1-3-x86_64.pkg.tar.gz pciutils-3.0.1-1-x86_64.pkg.tar.gz Scan complete for testing (i686) at /home/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /home/package-cleanup atl2-2.0.5-1-i686.pkg.tar.gz iputils-20071127-2-i686.pkg.tar.gz linux-atm-2.5.0-1-i686.pkg.tar.gz pciutils-3.0.2-1-i686.pkg.tar.gz Scan complete for testing (x86_64) at /home/ftp/testing/os/x86_64/ The following files are in the repo but not the db They will be moved to /home/package-cleanup atl2-2.0.5-1-x86_64.pkg.tar.gz cracklib-2.8.13-1-x86_64.pkg.tar.gz iputils-20071127-2-x86_64.pkg.tar.gz linux-atm-2.5.0-1-x86_64.pkg.tar.gz pciutils-3.0.2-1-x86_64.pkg.tar.gz

1 0

[arch-dev-public] draft klibc move news item
by Jud 06 Oct '08

06 Oct '08

> On Oct 05, 2008 at 08:37 PM, Allan McRae <allan at archlinux.org> > wrote: "rm /usr/lib/klibc/include/asm" Needed to be done as super-user? I would assume that a good percentage of users would struggle first-time around. The "limitation" with pacman, is it a one time thing? will it manifest into further problems? has the problem been fixed? I don't mean to sound negative, it's good that the Dev's are been upfront and proactive but the community will have questions.

3 2

Re: [arch-dev-public] draft klibc move news item
by Thayer Williams 06 Oct '08

06 Oct '08

On Oct 05, 2008 at 08:37 PM, Allan McRae <allan(a)archlinux.org> wrote: > Sounds fine? Sounds good to me.

1 0