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

[arch-dev-public] [signoff] tar
by Andreas Radke 13 Oct '07

13 Oct '07

available for both archs in testing * please sign off before the big move! Andy

2 1

[arch-dev-public] [big move] db/heimdal/gtk/gnome/gcc
by Andreas Radke 13 Oct '07

13 Oct '07

What bugs or rebuilds are pending? Any move stoppers left? I only know the gtk2 package, Jan wants to fix the X crashes. If he won't be around I'll try myself later tonight. The plan: - Many packages depend on x11-libs. Jan told me it's safe to move the x11-libs expect libgl to extra. everything else from Xorg will stay in testing. - All other packages will move right after gtk2 got fixed. Andy

1 0

[arch-dev-public] [signoff] openssl
by Pierre Schmitz 13 Oct '07

13 Oct '07

Hi, I have updated openssl from 0.9.8e to 0.9.8f and put it into [testing]. Because this is a [core]-package please test and tell me. Pierre -- archlinux.de

3 4

Re: [arch-dev-public] [arch-commits] CVS update of extra/science/plotutils (PKGBUILD)
by Dan McGee 13 Oct '07

13 Oct '07

On 10/12/07, Damir Perisa <damir(a)archlinux.org> wrote: > Date: Friday, October 12, 2007 @ 21:29:35 > Author: damir > Path: /home/cvs-extra/extra/science/plotutils > > Added: PKGBUILD (1.1) > > upgpkg: plotutils 2.5-1 > > > ----------+ > PKGBUILD | 33 +++++++++++++++++++++++++++++++++ > 1 file changed, 33 insertions(+) > > > Index: extra/science/plotutils/PKGBUILD > diff -u /dev/null extra/science/plotutils/PKGBUILD:1.1 > --- /dev/null Fri Oct 12 21:29:35 2007 > +++ extra/science/plotutils/PKGBUILD Fri Oct 12 21:29:35 2007 > @@ -0,0 +1,33 @@ > +# $Id: PKGBUILD,v 1.1 2007/10/13 01:29:35 damir Exp $ > +# Maintainer: damir <damir(a)archlinux.org> > +# Packager: Maksim Sipos (maxsipos at gmail dot com) > + > +pkgname=plotutils > +pkgver=2.5 > +pkgrel=1 > +arch=('x86_64' 'i686') > +pkgdesc="Set of utilities and libraries for plotting." > +url="http://directory.fsf.org/graphics/plotutils.html" > +license=("GPL") > +depends=("libpng" "gcc-libs" "libxaw") > +makedepends=("flex") > +# _patches="" > +source=("http://ftp.gnu.org/pub/gnu/plotutils/$pkgname-$pkgver.tar.gz" \ > + ${_patches}) > +options=('!libtool') > + > +build() { > + cd $startdir/src/$pkgname-$pkgver > +# for patch in ${_patches} > +# do > +# patch -Np1 -i $startdir/src/$patch > +# done > + ./configure --prefix=/usr \ > + --with-gnu-ld \ > + --with-x \ > + --enable-libplotter \ > + --enable-libxmi > + make || return 1 > + make DESTDIR=$startdir/pkg install > +} > +md5sums=('0d6855cce17832afe2ff75c26a57be49') > > _______________________________________________ > arch-commits mailing list > arch-commits(a)archlinux.org > http://archlinux.org/mailman/listinfo/arch-commits > OK, I don't want to start a flame war here, just a healthy discussion. Obviously Damir uses all these science packages and is willing to maintain them, so that is why they end up in the extra repository. But I'd like to pose a question to the developers- do these pacakges truely belong in extra? Considering we already have enough issues with orphaned packages and such, I feel like we should be a bit more strict when adding packages to our developer repositories. Even if we have a maintainer now for a package, as soon as a dev decides to depart our ranks we could be left with well over 100 packages no one wants to maintain. I feel like this is the reason there are still several packages in extra that have been orphaned and un-updated for over 2 years. The above was mostly opinion-free, so my last paragraph will be my opinion. I feel like packages like this belong in community or unsupported, not extra. We no longer look at community of less of a repo than extra- the only difference is who can place packages there. The community has always filled a great role as having some of the more niche packages, and most science stuff belongs in this category. And guess what the best part is? Even if you are a dev, you can build and upload packages to community. To Damir- this isn't directed at you as much as our general policy, which I believe we should work on setting so that all developers know what is acceptable and not acceptable. I'm sure other developers have added packages mostly for their personal use as well. -Dan

3 3

[arch-dev-public] kernel 2.6.23 status
by Tobias Powalowski 12 Oct '07

12 Oct '07

Hi 2.6.23 packages built + modules issues: fglrx is not working and lirc needs probably to change to cvs again to compile. The rest was compilable, when should i checkin to testing? breaking ati cards in testing is it worth the trouble or delay it? thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

9 13

[arch-dev-public] [signoff] libelf 0.8.10
by Andreas Radke 12 Oct '07

12 Oct '07

in testing for both architectures.

2 2

[arch-dev-public] [to sign off] grep, man-pages
by Andreas Radke 10 Oct '07

10 Oct '07

I've built grep and man-pages for x86_64 and ise has both for i686. They are now in testing. Please sign them off and move then to core. -Andy

4 3

[arch-dev-public] Plans for renaming kernel26suspend2 to kernel26tuxonice
by Daniel Isenmann 10 Oct '07

10 Oct '07

Hi, I plan to rename the kernel26suspend2 package to kernel26tuxonice and the corresponding modules are getting the suffix tuxonice instead of suspend2. Since the suspend2 developers change their name to tuxonice, this is the logical decision to avoid confusion. The next reason for changing the package name is the fact, that the tuxonice developers changed all refernces in their code to tuxonice. I think it's logical to name the package like the original one. I know, that there are other packages which would be affected by these changes. But I'm going to find those packages and rebuild/fix them or inform the maintainer of it. But no panic, I don't do it now...This is just an information to start discussion about this step. tuxonice doesn't released a stable version which build fine with kernel 2.6.23, so there is some time to think about it. But my plan is, that the next version of kernel26suspend2 becomes kernel26tuxonice. Daniel

1 0

[arch-dev-public] where to put unstable/testing packages?
by Andreas Radke 09 Oct '07

09 Oct '07

I've built my first pkg for unstable repo. It is built against testing packages. So do I put it into testing first and move it later to unstable or directly to unstable? Andy

5 5

[arch-dev-public] Replacing slocate?
by Aaron Griffin 09 Oct '07

09 Oct '07

Hey guys, I wanted to get some opinions on this bug here. http://bugs.archlinux.org/task/4490 I'm entirely neutral on it, but if one is technically superior, we should probably switch to it. So I'm going to put this out there so someone with more of an opinion can chime in. (Please comment on the bug tracker itself)

1 0