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

[arch-dev-public] cvslog added to core repo
by Aaron Griffin 17 Sep '07

17 Sep '07

The core repo should now send us emails on the arch-commits list. If someone has something legitimate to commit, please test and let me know if it worked - I don't want to artificially inflate the repo. Aaron

1 0

[arch-dev-public] Devtools problems
by Dan McGee 17 Sep '07

17 Sep '07

dmcgee@dublin ~/projects/repos/core/base/pacman $ corepkg scp: staging/core/add: No such file or directory Cancelled dmcgee@dublin ~/projects/repos/core/base/pacman $ ll /usr/bin/*pkg -rwxr-xr-x 1 root root 1.6K 2007-09-16 07:48 /usr/bin/checkpkg lrwxrwxrwx 1 root root 17 2007-05-12 01:46 /usr/bin/communitypkg -> /usr/bin/extrapkg lrwxrwxrwx 1 root root 8 2007-09-16 07:48 /usr/bin/corepkg -> extrapkg -rwxr-xr-x 1 root root 1.9K 2007-09-16 07:48 /usr/bin/extrapkg lrwxrwxrwx 1 root root 11 2007-06-18 11:02 /usr/bin/ghc-pkg -> ghc-pkg-6.6 -rwxr-xr-x 1 root root 28K 2007-06-20 01:25 /usr/bin/makepkg -rwxr-xr-x 1 root root 4.3K 2007-05-14 23:48 /usr/bin/queuepkg lrwxrwxrwx 1 root root 8 2007-09-16 07:48 /usr/bin/testingpkg -> extrapkg -rwxr-xr-x 1 root root 4.3K 2007-09-16 17:33 /usr/bin/testpkg -rwxr-xr-x 1 root root 5.2K 2007-02-22 02:23 /usr/bin/tupkg lrwxrwxrwx 1 root root 8 2007-09-16 07:48 /usr/bin/unstablepkg -> extrapkg -rwxr-xr-x 1 root root 5.4K 2007-08-02 02:40 /usr/bin/versionpkg A few problems here: 1. Why did the behavior of corepkg/extrapkg and friends suddenly require a staging directory on my machine? This seems wrong. The old way was perfectly acceptable... 2. Why is communitypkg an absolute link and the rest are not? Right now, devtools is broken to me. Let me know if someone plans on fixing it or if I'm going to back out changes that seem wrong to me. Right now I can't upgrade a package if I wanted to (pacman 3.0.6 anyone?). -Dan

2 2

[arch-dev-public] Important changes for all users, developers and TUs
by Thomas Bächler 17 Sep '07

17 Sep '07

Hi lists, we made some changes to repositories and packages which I'd like to summarize here. 1) (everyone, including users): The current repository is gone. Instead, we have a slimmer core repository and the rest of the packages went to the extra repository. I won't discuss the reasons for that change here, but if necessary, I'd be happy to explain it in a later post. If any packages are missing, don't hesitate to post bug reports. A pacman update will add a /etc/pacman.d/core file and users should change all references in pacman.conf from current to core. We added symlinks for compatibility, so the name current should still work for a while. 2) (everyone, including users): The repository scripts on our server now support the pacman3 style package naming. Our repositories are now partially incompatible with pacman2, as it will fail to find some files. If you haven't updated to pacman3 yet, you can still manually download the libarchive, libdownload and pacman packages from the ftp and install them with pacman2. 3) (users) FTP installations are broken for now, maybe we will have time to fix them soon. Until then, use a base CD to install. 4) (developers and TUs) Related to 1) and 2), a new devtools package has been uploaded. Packages are not renamed any more when uploading. An exception to this is communitypkg, as the community scripts on the server haven't been updated to the pacman3 naming style yet. All devs are encouraged to use the new style names from now on. The currentpkg script is gone, instead there is a corepkg script now, as well as /arch/db-core{,64} on the server. 5) (developers and TUs) The gcc package has been split in gcc and gcc-libs. Packages must not depend on gcc anymore, all those packages should be changed to depend on gcc-libs. This allows us to use C++ applications without forcing users to have gcc installled. Please update your packages as soon as possible. 6) (developers) All former current packages are now in extra or core. We lost the mantainer data for those, so please adopt all packages that were previously yours. This also affects packages which were moved from extra to core. If I forgot anything, tell me. Keep having fun with Arch. Thomas

3 6

[arch-dev-public] moving OOo/neon stuff from testing to extra
by Andreas Radke 16 Sep '07

16 Sep '07

Daniel and me are preparing to move neon and new OpenOffice incl. i18n later tonight. these are big uploads. it will take a while until we can run the db scripts. btw: i've changed the OOo splash - but it's still showing our nice non Abiword logo! :D Andy

1 0

[arch-dev-public] New fglrx drivers - no official package.
by Travis Willard 16 Sep '07

16 Sep '07

Hey guys. AMD's released their new radeon drivers, which are a complete rewrite. Exciting times, however AMD warns that these might not be production ready. After a bit of thought, I've decided to keep the 8.40.4 drivers in the repos for now (especially since this new release doesn't add kernel 2.6.23 or xorg 7.3 support) but make a custom repo for the new drivers for those who want to experiment. In the spirit of not doing things unilaterally, I'm notifying you all here. If there's no objection, I'll be posting an advisory to the forums later (maybe tonight or tomorrow) that will say essentially the following: -8<---8<---8<---8<---8<---8<---8<---8<-- Hi everyone, Today, AMD's 8.41.7 fglrx drivers, which are a complete rewrite of their codebase which they have spent more than a year of work on, were released today. On their release notes page, they offer the following recommendation: [quote]Caution: AMD recommends that this release of the AMD Proprietary Linux software driver not be used for distribution packages. Distributors should continue to use the AMD Proprietary Linux driver version 8.40.4[/quote] After some thought, I've decided to take this warning to heart, and will not be packaging this version of the drivers 'officially'. HOWEVER, tonight or possibly tomorrow I will be making packages for these drivers and a custom repo to obtain them from if you wish to test them out - these will not be 'official' archlinux packages, however, and the 8.40.4 release will remain in the repos until AMD releases a new version which they feel is suitable for general use. I will update this advisory once the new packages are available, and hope you all understand my reasoning on this. -8<---8<---8<---8<---8<---8<---8<---8<-- Any thoughts or suggestions, just reply to this thread. :) Thanks, Travis

5 9

[arch-dev-public] Arch mirrors
by Roman Kyrylych 16 Sep '07

16 Sep '07

Hi! The mirrorlist on http://archlinux.org/download/ page is outdated. I suggest we just write something like 'You can also download ISOs via FTP/HTTP/rsync from /iso/ directory on <a href="http://wiki.archlinux.org/index.php/Mirrors">mirrors</a>' instead of incomplete and outdated mirrorlist. Also, installer's mirrors.txt file should be updated as well (minus those that don't sync isos from main server). -- Roman Kyrylych (Роман Кирилич)

1 0

[arch-dev-public] [core] progress
by Tobias Powalowski 15 Sep '07

15 Sep '07

Hi ok guys sum up what already done: [core] cvs partially setup ok base is moved in and divided into the categories according to this: https://www.archlinux.org/wiki/Core-Repository/ - packages from extra is still missing though - gcc splitup is pending - syslogng needs to be reviewed - the move to of the rest of current to cvs-extra2 is not done im tired now and going to bed, i'll continue on it tomorrow morning. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

6 12

[arch-dev-public] Repository cleanup [current] and [base] --> [core], this weekend!
by Tobias Powalowski 15 Sep '07

15 Sep '07

Hi it's quite a long time ago we had a dev meeting, but i think there were quite some agreement what [core] should be and we should start doing this soon. Our next ISOs shouldn't have the big current anymore only ftp and [core]. [non-free] repository we should add a non-free repository with stuff that is not freely distributable, like acroread, sun java, firmware files, flash etc. this cleanup would affect [extra] and [current] that way we could finally have cds of [extra] too without getting into trouble. As Romashka said, these are the types we need to look at: 1) those that are not possible to distribute due to prohibition of original package modification, but it does not work without modifications to installation procedure - like vmware 2) those that are not allowed to be redistributed by EULA - like commercial edition of virtualbox 3) those that are not allowed to be sold on a CD, but can be distributed over internet 4) those that are just not Free Software - it's nice to have them splitted if someone wants to have FOSS-only mirror/CD/etc 1+2 should be probably moved out of the official repositories, if not already done. 3+4 should be ok [core] repository should be like [base] + some extra stuff the question is: what is extra stuff? imho, it should be everything that is needed for networking free kernel network modules free wlan stuff all supported main filesystems suggestion list of packages to add: ndiswrapper ndiswrapper-utils wlan-ng26 rt2500 madwifi madwifi-utils fuse ntfs-3g iptables bcm43xx-fwcutter dosfsutils ntfsprogs kexec-tools snarf dnsutils hdparm bridge-utils ifenslave xinetd portmap nfsidmap nfs-utils openssh netkit-telnet screen isdn4k-utils capi4k-utils vpnc openvpn everything else from [current] should be moved to [extra]. your opinions, lets get something done this weekend. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

17 42

[arch-dev-public] IMPORTANT: Repo DB scripts hacked!
by Thomas Bächler 14 Sep '07

14 Sep '07

As rewriting the repo db scripts is a time intensive process which involves cleaning up the web backend too, I did a few hacks to our current scripts to support both the pacman2 and pacman3 naming scheme. I changed the updatesync-many, pkgdb1, db-inc and genpkglist files. Please everyone who is familiar with the scripts (and everyone else, because noone is actually familiar with them) look over my changes and see if they make sense. If no errors are found, the scripts WILL be moved from CVS to /arch and WILL be used. So make sure I didn't screw up. For the lazy, I attached the diff. Index: db-inc =================================================================== RCS file: /home/cvs-arch/arch/scripts/db-inc,v retrieving revision 1.6 diff -u -r1.6 db-inc --- db-inc 7 May 2006 18:02:42 -0000 1.6 +++ db-inc 14 Sep 2007 16:38:14 -0000 @@ -16,6 +16,18 @@ exit 1 fi +# Get the package name from the filename +# hackish, but should work for now +getpkgname() { + local tmp + + tmp=${1##*/} + tmp=${tmp%.pkg.tar.gz} + tmp=${tmp%-i686} + tmp=${tmp%-x86_64} + echo ${tmp%-*-*} +} + cleanup() { rm -rf $TMPDIR # unlock @@ -134,7 +146,7 @@ cd $stagedir/del ( for i in *.pkg.tar.gz; do - pkgname=${i%-*-*} + pkgname=$(getpkgname $i) echo $pkgname done ) | $ARCHDIR/pkgdb2-del $repoid $stagedir/del @@ -147,7 +159,7 @@ if [ "$updatelists" ]; then echo "==> Generating Text Package List..." >&2 cd $TMPDIR/$cvsmod - $ARCHDIR/genpkglist $ftppath + $ARCHDIR/genpkglist $ftppath $arch # hack -- only Current's packages.txt goes in a "setup" subdir if [ "$reponame" = "current" ]; then Index: genpkglist =================================================================== RCS file: /home/cvs-arch/arch/scripts/genpkglist,v retrieving revision 1.14 diff -u -r1.14 genpkglist --- genpkglist 5 May 2006 01:38:33 -0000 1.14 +++ genpkglist 14 Sep 2007 16:38:14 -0000 @@ -8,8 +8,21 @@ # (also used to check for missing packages in the download directory) # +# Get the package name from the filename +# hackish, but should work for now +getpkgname() { + local tmp + + tmp=${1##*/} + tmp=${tmp%.pkg.tar.gz} + tmp=${tmp%-i686} + tmp=${tmp%-x86_64} + echo ${tmp%-*-*} +} + pkgfile="`pwd`/packages.txt" ftppath=$1 +dbarch=$2 rm -f $pkgfile for category in `find * -maxdepth 0 -type d | grep -v CVS`; do @@ -20,8 +33,10 @@ . PKGBUILD if [ -f $ftppath/$pkgname-$pkgver-$pkgrel.pkg.tar.gz ]; then echo "$category/$pkgname-$pkgver-$pkgrel.pkg.tar.gz" >>$pkgfile + elif [ -f $ftppath/$pkgname-$pkgver-$pkgrel-$dbarch.pkg.tar.gz ]; then + echo "$category/$pkgname-$pkgver-$pkgrel-$dbarch.pkg.tar.gz" >>$pkgfile else - echo "notice: Missing $pkgname-$pkgver-$pkgrel.pkg.tar.gz in ftp site" >&2 + echo "notice: Missing $pkgname-$pkgver-$pkgrel-$dbarch.pkg.tar.gz in ftp site" >&2 fi fi cd .. @@ -32,7 +47,7 @@ cd $ftppath unset DUPES DUPEFILES last for pkg in *.pkg.tar.gz; do - pkgname=${pkg%-*-*} + pkgname=$(getpkgname $pkg) if [ "$last" = "$pkgname" ]; then DUPES="$DUPES $pkgname" DUPEFILES="$DUPEFILES $pkg" Index: pkgdb1 =================================================================== RCS file: /home/cvs-arch/arch/scripts/pkgdb1,v retrieving revision 1.4 diff -u -r1.4 pkgdb1 --- pkgdb1 20 Feb 2006 06:33:40 -0000 1.4 +++ pkgdb1 14 Sep 2007 16:38:14 -0000 @@ -1,6 +1,18 @@ #!/bin/bash # $Id: pkgdb1,v 1.4 2006/02/20 06:33:40 judd Exp $ +# Get the package name from the filename +# hackish, but should work for now +getpkgname() { + local tmp + + tmp=${1##*/} + tmp=${tmp%.pkg.tar.gz} + tmp=${tmp%-i686} + tmp=${tmp%-x86_64} + echo ${tmp%-*-*} +} + STAGEDIR=`pwd` ABSDIR=$1 @@ -16,9 +28,8 @@ cd $STAGEDIR for pkgfile in `ls $STAGEDIR/*.pkg.tar.gz`; do - tmp=${pkgfile##*/} - pkgname=${tmp%-*-*}; - fullname=${tmp%.pkg.tar.gz} + pkgname=$(getpkgname $pkgfile); + fullname=$(basename $pkgfile) # find the matching PKGBUILD tmpf=$(mktemp /tmp/pkgdb1.XXXXXXXXXX) || exit 1 find $ABSDIR -type d -name "$pkgname" >$tmpf Index: updatesync-many =================================================================== RCS file: /home/cvs-arch/arch/scripts/updatesync-many,v retrieving revision 1.2 diff -u -r1.2 updatesync-many --- updatesync-many 5 May 2006 01:38:33 -0000 1.2 +++ updatesync-many 14 Sep 2007 16:38:14 -0000 @@ -1,4 +1,5 @@ #!/bin/bash +# $Id: $ # # updatesync-many # @@ -46,6 +47,18 @@ echo "updatesync-many: $*" >&2 } +# Get the package name from the filename +# hackish, but should work for now +getpkgname() { + local tmp + + tmp=${1##*/} + tmp=${tmp%.pkg.tar.gz} + tmp=${tmp%-i686} + tmp=${tmp%-x86_64} + echo ${tmp%-*-*} +} + check_option() { local i for i in ${options[@]}; do @@ -76,6 +89,9 @@ cd $pkgname-$pkgver-$pkgrel # desc : >desc + echo "%FILENAME%" >>desc + echo "$2" >>desc + echo "" >>desc echo "%NAME%" >>desc echo "$pkgname" >>desc echo "" >>desc @@ -138,10 +154,8 @@ delete_entry() { - # strip to the basename - tmp=${1##*/} # grab the pkgname - pkgname=${tmp%-*-*} + pkgname=$(getpkgname $1) for i in *; do if [ "${i%-*-*}" = "$pkgname" ]; then rm -rf $i @@ -152,9 +166,8 @@ update_entry() { pkgfile=$1 - tmp=${pkgfile##*/} - pkgname=${tmp%-*-*}; - fullname=${tmp%.pkg.tar.gz} + pkgname=$(getpkgname ${pkgfile}) + fullname=$(basename ${pkgfile}) # find the matching PKGBUILD tmpf=$(mktemp /tmp/updatesync-many.XXXXXXXXXX) || exit 1 @@ -185,7 +198,7 @@ pkgmd5sum=`get_md5checksum $pkgfile` [ -z $pkgmd5sum ] && die "error generating checksum for $pkgfile" - db_write_entry $pkgbuild || die "error writing entry for $pkgname" + db_write_entry ${pkgbuild} ${fullname} || die "error writing entry for $pkgname" cd - >/dev/null } @@ -237,9 +250,7 @@ lsof $pkgfile &>/dev/null [ $? -ne 1 ] && continue - tmp=${pkgfile##*/} - pkgname=${tmp%-*-*}; - fullname=${tmp%.pkg.tar.gz} + pkgname=$(getpkgname ${pkgfile}) if [ "$ACTION" = "del" ]; then msg "Deleting entry: $pkgname" delete_entry $pkgfile

2 2

[arch-dev-public] FYI: Split gcc/libgcc
by Thomas Bächler 14 Sep '07

14 Sep '07

Aaron is right about communication, so I am posting this here: While splitting the current/base category into core/base and core/devel, it has been decided to split the gcc package into gcc(tools) and libgcc(libs:libstdc++,libgcc_s,...), so that no package will have to depend on gcc in the future, but rather on libgcc. gcc will depend on libgcc, gcc will go to core/devel and libgcc will go to core/base. Jan hopes he can do the split tonight.

4 4