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

[arch-dev-public] [signoff] devtools 0.9.1
by Pierre Schmitz 17 Feb '10

17 Feb '10

Am Samstag, 13. Februar 2010 00:18:30 schrieb Eric Bélanger: > I found the cause of this error. This error happens when the CacheDir > is undefined. The chroot_mount function in mkarchroot then fails to > create the cache_dir directory. It should be fixed by the commit to > give cache_dir a default value. Thanks, that explains a lot. I have put 0.9.1 into [testing] fixing this issue and being a little more verbose when an action might take longer (like svn commit) -- Pierre Schmitz, https://users.archlinux.de/~pierre

6 23

[arch-dev-public] [PATCH 1/2] remove unused script
by Pierre Schmitz 16 Feb '10

16 Feb '10

Signed-off-by: Pierre Schmitz <pierre(a)archlinux.de> --- convert-to-any | 71 -------------------------------------------------------- 1 files changed, 0 insertions(+), 71 deletions(-) delete mode 100755 convert-to-any diff --git a/convert-to-any b/convert-to-any deleted file mode 100755 index 53d1a7b..0000000 --- a/convert-to-any +++ /dev/null @@ -1,71 +0,0 @@ -#!/bin/bash -# -# Converts an existing architecture-independent package -# for i686 or x86_64 into a package with "arch = any" -# - -# -- Abhishek Dasgupta <abhidg(a)gmail.com> - -[ "$UID" = "" ] && UID=$(uid) -OUTDIR="$(pwd)" -WORKDIR="/tmp/convert-to-any.$UID" - -if [ $# -ne 1 ]; then - echo "Syntax: $(basename $0) <package-file>" - exit 1 -fi - -. "$(dirname $0)/db-functions" -. "$(dirname $0)/config" - -cleanup() { - trap '' 0 2 - rm -rf "$WORKDIR" - [ "$1" ] && exit $1 -} - -ctrl_c() { - echo "Interrupted" >&2 - cleanup 0 -} - -die() { - echo "$*" >&2 - cleanup 1 -} - -mkdir -p "$WORKDIR/build" - -oldpkgname="$1" - -if [ -z "$oldpkgname" ]; then - die "convert-to-any: which package to convert?" -fi - -pkg="$(basename $oldpkgname)" -newpkgname=$(echo $pkg | sed "s/-$i686\|x86_64$$PKGEXT/-any$PKGEXT/") - -if ! cp "$oldpkgname" "$WORKDIR/build/$pkg"; then - die "convert-to-any: failed to copy package to $WORKDIR" -fi -pushd "$WORKDIR/build" >/dev/null - -# Conversion of i686 package into "any" package. -mkdir -p package -if ! fakeroot bsdtar xf "$pkg" -C package; then - die "convert-to-any: error in extracting $oldpkgname" -fi - -sed -i "s/arch = $i686\|x86_64$/arch = any/g" package/.PKGINFO -pushd package >/dev/null -case "$newpkgname" in - *tar.gz) TAR_OPT="z" ;; - *tar.bz2) TAR_OPT="j" ;; - *tar.xz) TAR_OPT="J" ;; - *) die "$newpkgname does not have a valid archive extension." ;; -esac -fakeroot bsdtar c${TAR_OPT}f "$OUTDIR/$newpkgname" .PKGINFO * -popd >/dev/null - -popd >/dev/null -cleanup -- 1.6.6.1 -- Pierre Schmitz, https://users.archlinux.de/~pierre

1 0

[arch-dev-public] Let's agree on a common coding style
by Pierre Schmitz 15 Feb '10

15 Feb '10

Hi all, while looking at our devtools, other scripts we have written together and even PKGBUILDs, you will see as much different types of indention, bracing etc. as there are authors. This always annoyed me and as I just watched Greg's talk at fosdem about committing kernel patches I'll go ahead and will start with devtools. I would suggest to use this coding style: * indent with tabs * tabs have 8 characters * don't use more than 132 columns * opening braces are top right, closing are bottom left: function foo() { echo bar } * if and for statements are like this: if true; then do something else do something else fi for i in a b c; do echo $i done * use single quotes if a string does not parseable content We could also talk about using `` or $(); source vs. .; $foo vs. ${bar} etc.. But that's probably too much. Greetings, Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre

6 14

[arch-dev-public] devtools and db-scripts plans
by Allan McRae 15 Feb '10

15 Feb '10

Hi all, There has been talk about what is needed/wanted for the future of devtools and db-scripts but not much done lately. So I thought I would get together a list of ideas so we could perhaps do a coding sprint to implement them. Here is what I have got so far: devtools - split-PKGBUILDs with (supported in future pacman): -> both binary and arch=any packages -> overridden pkgver -> overridden pkgrel (and only selected sub-packages) - support for xz compression (nothing needed?) db-scripts - support for xz compression transition (e.g. in clean-up script) - support for single "package" directory with symlinks to repos - allow db-move to handle multiple packages (or add a script to help moving from community-testing) - delta support... Any others? Allan

7 12

[arch-dev-public] Files database, potential changes
by Dan McGee 15 Feb '10

15 Feb '10

So right now we have our create-filelists cronjob in the dbscripts pumping out files databases. This is great, except that the file is a lot less useful to automated processes than you would think. If you hadn't guessed yet, I'm trying to get this stuff back in the website. I have it working about 90% locally but the last 10% is the key. The problem stems from our old single-arch, no-any packages mentality. The files DB simply doesn't have enough information to match up a *complete* package specification with its files due to these busted assumptions. Although we can parse the pkgname and pkgver from the directory names in the zip, we have no idea what is an 'any' package and what is an arch-specific package. Since every package is unique on the tuple of (pkgname, repo, arch), we are missing one of the three components here in this database. One thought is to actually implement the hack into create-filelists as I currently do when parsing the files DB: if type == 'files' and fname == 'files': # we don't have desc to provide us with name/version here, # so we need to do some of the work on our own. dirname = os.path.split(tarinfo.name)[0] tpkg.write('%NAME%\n') tpkg.write('-'.join(dirname.split('-')[:-2])) tpkg.write('\n\n%VERSION%\n') tpkg.write('-'.join(dirname.split('-')[-2:])) tpkg.write('\n\n%ARCH%\n') tpkg.write('i686\n') These are the required attributes to get a full package spec. Does anyone object to placing a desc file inside the files database holding this information to make it easier for tools to work with our multi-architecture ecosystem these days? Or if you have a better idea than the above, I would of course be up for that as well. -Dan

4 3

[arch-dev-public] signoff: vi 050325-2
by Paul Mattal 15 Feb '10

15 Feb '10

This fix just adds a patch to increase the TUBECOLS and TUBESIZE such that vi will work on larger terminals with default settings/variables set. Those of use with large console widths have been excited about this fix: http://bugs.archlinux.org/task/15844 Please signoff both arches. I've tested myself on each arch, so need one more on each arch. - P

3 3

Re: [arch-dev-public] [arch-general] Let's agree on a common coding style
by Thayer Williams 14 Feb '10

14 Feb '10

On Sun, Feb 14, 2010 at 1:08 AM, Ray Rashif <schivmeister(a)gmail.com> wrote: > Keeping it consistent-by-individual should be enough, i.e you don't > change your own style across your works, and if you do you should > reflect the new style throughout everything else. It's easy to see how quickly this can turn into a bikeshed debate. Regarding the tab widths, I'm curious to know how some of you handle pseudo source code, such as XHTML/CSS. Using 8-col tab widths in HTML can get ridiculous due to the nesting involved. Also, do you guys setup autocmds in vim for handling all non-code files, or do you set up autocmds explicitly for source code files and leave the default tabwidth to something more conservative? I work with such a mix of file types so frequently that I'm not sure which practise to apply by default.

1 0

[arch-dev-public] [signoff] mkinitcpio 0.6-1 and friends
by Thomas Bächler 14 Feb '10

14 Feb '10

Please sign off these packages: mkinitcpio 0.6-1 - Remove klibc dependency - Rewrite many hooks to be better, have less bugs and work with busybox - Random other fixes mkinitcpio-busybox 1.15.3-5 - Core component of mkinitcpio 0.6: Busybox build especially configured for mkinitcpio mkinitcpio-nfs-utils 0.1-1 - nfsmount and ipconfig utilities ported from klibc for NFS root support (Could someone please test this, AFAIK nobody ever verified that it works) cryptsetup 1.1.0-2 device-mapper 2.02.60-3 dmraid 1.0.0.rc16-2 lvm2 2.02.60-3 mdadm 3.1.1-2 v86d 0.1.9-10 - Hooks adjusted to work with the new busybox shell and tools - Static or klibc binaries replaced by dynamic glibc binaries

6 12

[arch-dev-public] No signoff thread for vi?
by Thomas Bächler 14 Feb '10

14 Feb '10

Where is the signoff thread for vi? We need this in core, which won't happen without a signoff thread.

1 0

[arch-dev-public] [signoff] devtools 0.9.0
by Pierre Schmitz 14 Feb '10

14 Feb '10

Hi TUs and DEVs, I just packaged a new set of devtools today. I'll put it into testing first; so please give it a try and let me know if there are any problems. And of course I'd appreciate if you could also drop a line if everything works as expected. A warning for those who use makechrootpkg: the rw and union subdirs are no longer used and cannot be used with the new tools. Aufs is no longer needed. For details see http://projects.archlinux.org/devtools.git/log/ The most noticeable changes are: Use the host's SRCDEST and PKGDEST if defined Reset umask before touching the chroot. make sure all files are owned by nobody before building Move build and package logs to WORKDIR, otherwise it is lost Create a working copy instead of using an union layer Read pacman cache dir from pacman.conf or cli Reduce verbosity to a sane minimum simplify and optimize upload process Replace expensive merge with delete and copy Add missing -n option to getopt list for mkarchroot abort if not all local source files are under version control Greetings, Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre

1 1