[arch-dev-public] Signoff report for [testing]
=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 15 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 6 fully signed off packages * 28 packages missing signoffs * 4 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == New packages in [testing] in last 24 hours (15 total) == * automake-1.14-1 (any) * e2fsprogs-1.42.8-1 (i686) * linux-3.9.7-1 (i686) * linux-lts-3.0.83-1 (i686) * e2fsprogs-1.42.8-1 (x86_64) * linux-3.9.7-1 (x86_64) * linux-lts-3.0.83-1 (x86_64) * gnu-efi-libs-3.0u-2 (i686) * lirc-1:0.9.0-48 (i686) * nvidia-319.23-3 (i686) * nvidia-304xx-304.88-9 (i686) * gnu-efi-libs-3.0u-2 (x86_64) * lirc-1:0.9.0-48 (x86_64) * nvidia-319.23-3 (x86_64) * nvidia-304xx-304.88-9 (x86_64) == Incomplete signoffs for [core] (12 total) == * automake-1.14-1 (any) 0/2 signoffs * grub-efi-x86_64-2.00-2 (any) 0/2 signoffs * e2fsprogs-1.42.8-1 (i686) 0/1 signoffs * grub-2.00-5 (i686) 0/1 signoffs * linux-lts-3.0.83-1 (i686) 0/1 signoffs * nfs-utils-1.2.8-8 (i686) 0/1 signoffs * ppp-2.4.5-8 (i686) 0/1 signoffs * e2fsprogs-1.42.8-1 (x86_64) 0/2 signoffs * grub-2.00-5 (x86_64) 0/2 signoffs * linux-lts-3.0.83-1 (x86_64) 1/2 signoffs * nfs-utils-1.2.8-8 (x86_64) 1/2 signoffs * ppp-2.4.5-8 (x86_64) 0/2 signoffs == Incomplete signoffs for [extra] (16 total) == * freetype2-2.5.0.1-1 (i686) 0/1 signoffs * gnu-efi-libs-3.0u-2 (i686) 0/1 signoffs * gummiboot-33-1 (i686) 0/1 signoffs * libseccomp-2.1.0-1 (i686) 0/1 signoffs * lirc-1:0.9.0-48 (i686) 0/1 signoffs * nvidia-319.23-3 (i686) 0/1 signoffs * nvidia-304xx-304.88-9 (i686) 0/1 signoffs * qemu-1.5.0-4 (i686) 0/1 signoffs * vim-7.3.1200-1 (i686) 0/1 signoffs * gnu-efi-libs-3.0u-2 (x86_64) 0/2 signoffs * gummiboot-33-1 (x86_64) 1/2 signoffs * libseccomp-2.1.0-1 (x86_64) 0/2 signoffs * lirc-1:0.9.0-48 (x86_64) 0/2 signoffs * nvidia-319.23-3 (x86_64) 0/2 signoffs * nvidia-304xx-304.88-9 (x86_64) 0/2 signoffs * qemu-1.5.0-4 (x86_64) 1/2 signoffs == Completed signoffs (6 total) == * linux-3.9.7-1 (i686) * syslinux-5.10-3 (i686) * linux-3.9.7-1 (x86_64) * syslinux-5.10-3 (x86_64) * freetype2-2.5.0.1-1 (x86_64) * vim-7.3.1200-1 (x86_64) == All packages in [testing] for more than 14 days (4 total) == * qemu-1.5.0-4 (i686), since 2013-06-04 * qemu-1.5.0-4 (x86_64), since 2013-06-04 * syslinux-5.10-3 (i686), since 2013-06-06 * syslinux-5.10-3 (x86_64), since 2013-06-06 == Top five in signoffs in last 24 hours == 1. foutrelis - 3 signoffs 2. tomegun - 1 signoffs 3. andyrtr - 1 signoffs
[arch-dev-public] Bootstrap images for installing Arch from another system
So, I heard a few people struggled installing Arch from another distro or from a root server rescue system recently. The requirements for pacman and friends are numerous and most systems don't have recent enough libraries to easily meet them. Setting up Arch on a root server should be as easy as this: * Boot rescue system, make sure you have Linux 2.6.32 or later * Download tarball from Arch, extract to /tmp/root.x86_64/ * Set up partitions and such, mount to /tmp/root.x86_64/mnt/ * chroot /tmp/root.x86_64/ (well, also some bind-mounts) * pacman-key --populate archlinux * pacstrap /mnt base and follow the installation guide I'd like to generate such tarballs regularly (monthly like our ISOs?) and put them on our mirrors, unless there are objections. I took the liberty of writing a small script: https://paste.xinu.at/ixbqt/ These are the resulting files: total 143M -rw-r--r-- 1 root root 71M 22. Jun 17:13 archlinux-bootstrap-2013.06.22-i686.tar.gz -rw-r--r-- 1 root root 73M 22. Jun 17:15 archlinux-bootstrap-2013.06.22-x86_64.tar.gz Note that they are only gzipped, because we can rely on tar and gzip being widely available. Any comments? signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
On 06/22/2013 12:33 PM, Thomas Bächler wrote:
So, I heard a few people struggled installing Arch from another distro
or from a root server rescue system recently. The requirements for
pacman and friends are numerous and most systems don't have recent
enough libraries to easily meet them.
Setting up Arch on a root server should be as easy as this:
* Boot rescue system, make sure you have Linux 2.6.32 or later
* Download tarball from Arch, extract to /tmp/root.x86_64/
* Set up partitions and such, mount to /tmp/root.x86_64/mnt/
* chroot /tmp/root.x86_64/ (well, also some bind-mounts)
* pacman-key --populate archlinux
* pacstrap /mnt base and follow the installation guide
I'd like to generate such tarballs regularly (monthly like our ISOs?)
and put them on our mirrors, unless there are objections.
I took the liberty of writing a small script:
https://paste.xinu.at/ixbqt/
These are the resulting files:
total 143M
-rw-r--r-- 1 root root 71M 22. Jun 17:13
archlinux-bootstrap-2013.06.22-i686.tar.gz
-rw-r--r-- 1 root root 73M 22. Jun 17:15
archlinux-bootstrap-2013.06.22-x86_64.tar.gz
Note that they are only gzipped, because we can rely on tar and gzip
being widely available.
Any comments?
Good,
I suggest to use Architecture = auto and use setarch ${arch}
pacstrap In this way, scriptlets will be executed in the right
architecture ;)
Have a nice day.
--
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1
signature.asc
Description: OpenPGP digital signature
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
Am 22.06.2013 18:00, schrieb Gerardo Exequiel Pozzi:
On 06/22/2013 12:33 PM, Thomas Bächler wrote:
So, I heard a few people struggled installing Arch from another distro
or from a root server rescue system recently. The requirements for
pacman and friends are numerous and most systems don't have recent
enough libraries to easily meet them.
Setting up Arch on a root server should be as easy as this:
* Boot rescue system, make sure you have Linux 2.6.32 or later
* Download tarball from Arch, extract to /tmp/root.x86_64/
* Set up partitions and such, mount to /tmp/root.x86_64/mnt/
* chroot /tmp/root.x86_64/ (well, also some bind-mounts)
* pacman-key --populate archlinux
* pacstrap /mnt base and follow the installation guide
I'd like to generate such tarballs regularly (monthly like our ISOs?)
and put them on our mirrors, unless there are objections.
I took the liberty of writing a small script:
https://paste.xinu.at/ixbqt/
These are the resulting files:
total 143M
-rw-r--r-- 1 root root 71M 22. Jun 17:13
archlinux-bootstrap-2013.06.22-i686.tar.gz
-rw-r--r-- 1 root root 73M 22. Jun 17:15
archlinux-bootstrap-2013.06.22-x86_64.tar.gz
Note that they are only gzipped, because we can rely on tar and gzip
being widely available.
Any comments?
Good,
I suggest to use Architecture = auto and use setarch ${arch}
pacstrap In this way, scriptlets will be executed in the right
architecture ;)
Seem reasonable - are there any known failures with the wrong
architecture set?
signature.asc
Description: OpenPGP digital signature
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
On 06/22/2013 01:02 PM, Thomas Bächler wrote:
Am 22.06.2013 18:00, schrieb Gerardo Exequiel Pozzi:
On 06/22/2013 12:33 PM, Thomas Bächler wrote:
So, I heard a few people struggled installing Arch from another distro
or from a root server rescue system recently. The requirements for
pacman and friends are numerous and most systems don't have recent
enough libraries to easily meet them.
Setting up Arch on a root server should be as easy as this:
* Boot rescue system, make sure you have Linux 2.6.32 or later
* Download tarball from Arch, extract to /tmp/root.x86_64/
* Set up partitions and such, mount to /tmp/root.x86_64/mnt/
* chroot /tmp/root.x86_64/ (well, also some bind-mounts)
* pacman-key --populate archlinux
* pacstrap /mnt base and follow the installation guide
I'd like to generate such tarballs regularly (monthly like our ISOs?)
and put them on our mirrors, unless there are objections.
I took the liberty of writing a small script:
https://paste.xinu.at/ixbqt/
These are the resulting files:
total 143M
-rw-r--r-- 1 root root 71M 22. Jun 17:13
archlinux-bootstrap-2013.06.22-i686.tar.gz
-rw-r--r-- 1 root root 73M 22. Jun 17:15
archlinux-bootstrap-2013.06.22-x86_64.tar.gz
Note that they are only gzipped, because we can rely on tar and gzip
being widely available.
Any comments?
Good,
I suggest to use Architecture = auto and use setarch ${arch}
pacstrap In this way, scriptlets will be executed in the right
architecture ;)
Seem reasonable - are there any known failures with the wrong
architecture set?
No, just in case ;)
--
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1
signature.asc
Description: OpenPGP digital signature
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
Am 22.06.2013 17:33, schrieb Thomas Bächler: Setting up Arch on a root server should be as easy as this: * Boot rescue system, make sure you have Linux 2.6.32 or later * Download tarball from Arch, extract to /tmp/root.x86_64/ * Set up partitions and such, mount to /tmp/root.x86_64/mnt/ * chroot /tmp/root.x86_64/ (well, also some bind-mounts) * pacman-key --populate archlinux * pacstrap /mnt base and follow the installation guide I'd like to generate such tarballs regularly (monthly like our ISOs?) and put them on our mirrors, unless there are objections. Good idea. I had something like this in mind for some time; I did not think of putting only pacstrap and deps into the tar though. I wonder if you could use arch-chroot isntead of just chroot here. You can also use the pacman.conf from the releng scripts. And to be safe you should prefix pacstrap with a setarch call. I'd say we include this script into the releng scripts (either archiso or create a nwe package; atm I use some additional script for releasing an ISO image) and upload such a tar at the same time as the ISO image. Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
Am 22.06.2013 20:10, schrieb Pierre Schmitz: Am 22.06.2013 17:33, schrieb Thomas Bächler: Setting up Arch on a root server should be as easy as this: * Boot rescue system, make sure you have Linux 2.6.32 or later * Download tarball from Arch, extract to /tmp/root.x86_64/ * Set up partitions and such, mount to /tmp/root.x86_64/mnt/ * chroot /tmp/root.x86_64/ (well, also some bind-mounts) * pacman-key --populate archlinux * pacstrap /mnt base and follow the installation guide I'd like to generate such tarballs regularly (monthly like our ISOs?) and put them on our mirrors, unless there are objections. Good idea. I had something like this in mind for some time; I did not think of putting only pacstrap and deps into the tar though. I think I tested this once and it is sufficient. As a plus, it has all dependencies so you can use pacman to install more packages into the chroot. I wonder if you could use arch-chroot isntead of just chroot here. It requires bash 4 - if that's not installed on the host, arch-chroot will not work. I would rather provide instructions involving manual bind-mounting and chroot. You can also use the pacman.conf from the releng scripts. I pretty much used the default pacman.conf from our packages (also enabled Color, but that didn't do anything). Is the releng one different? And to be safe you should prefix pacstrap with a setarch call. Already done as per Gerardo's suggestion: https://paste.xinu.at/lNIrq/ I'd say we include this script into the releng scripts (either archiso or create a nwe package; atm I use some additional script for releasing an ISO image) and upload such a tar at the same time as the ISO image. I was thinking about including this into arch-install-scripts, but I am unsure if it really fits in there. signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
On Jun 22, 2013 2:49 PM, Thomas Bächler tho...@archlinux.org wrote: Am 22.06.2013 20:10, schrieb Pierre Schmitz: Am 22.06.2013 17:33, schrieb Thomas Bächler: Setting up Arch on a root server should be as easy as this: * Boot rescue system, make sure you have Linux 2.6.32 or later * Download tarball from Arch, extract to /tmp/root.x86_64/ * Set up partitions and such, mount to /tmp/root.x86_64/mnt/ * chroot /tmp/root.x86_64/ (well, also some bind-mounts) * pacman-key --populate archlinux * pacstrap /mnt base and follow the installation guide I'd like to generate such tarballs regularly (monthly like our ISOs?) and put them on our mirrors, unless there are objections. Good idea. I had something like this in mind for some time; I did not think of putting only pacstrap and deps into the tar though. I think I tested this once and it is sufficient. As a plus, it has all dependencies so you can use pacman to install more packages into the chroot. I wonder if you could use arch-chroot isntead of just chroot here. It requires bash 4 - if that's not installed on the host, arch-chroot will not work. I would rather provide instructions involving manual bind-mounting and chroot. If you think its worthwhile to make the install scripts bash 3 compat I can look into doing this. You can also use the pacman.conf from the releng scripts. I pretty much used the default pacman.conf from our packages (also enabled Color, but that didn't do anything). Is the releng one different? And to be safe you should prefix pacstrap with a setarch call. Already done as per Gerardo's suggestion: https://paste.xinu.at/lNIrq/ I'd say we include this script into the releng scripts (either archiso or create a nwe package; atm I use some additional script for releasing an ISO image) and upload such a tar at the same time as the ISO image. I was thinking about including this into arch-install-scripts, but I am unsure if it really fits in there.
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
Am 22.06.2013 20:49, schrieb Thomas Bächler: I wonder if you could use arch-chroot isntead of just chroot here. It requires bash 4 - if that's not installed on the host, arch-chroot will not work. I would rather provide instructions involving manual bind-mounting and chroot. Fair enough. It should not be too hard to make it work with bash 3 though. But maybe this is a good time to think about our minimum requirements. E.g. Debian 6 (oldstable) already has Bash 4 and it seems our glibc requires at least Linux 2.6.32. (it seems Debian 5 had 2.6.26 so that wont work anyway) You can also use the pacman.conf from the releng scripts. I pretty much used the default pacman.conf from our packages (also enabled Color, but that didn't do anything). Is the releng one different? Not really; this would just reduce duplication and makes sure these tars and the iso iamges allways match. I'd say we include this script into the releng scripts (either archiso or create a nwe package; atm I use some additional script for releasing an ISO image) and upload such a tar at the same time as the ISO image. I was thinking about including this into arch-install-scripts, but I am unsure if it really fits in there. Yes, seems difficult. As I said, I also have other scripts like creating torrents etc. that are used for a realease. Maybe we can create a releng repo/package for these. -- Pierre Schmitz, https://pierre-schmitz.com
Re: [arch-dev-public] Bootstrap images for installing Arch from another system
Am 22.06.2013 20:55, schrieb Dave Reisner: I wonder if you could use arch-chroot isntead of just chroot here. It requires bash 4 - if that's not installed on the host, arch-chroot will not work. I would rather provide instructions involving manual bind-mounting and chroot. If you think its worthwhile to make the install scripts bash 3 compat I can look into doing this. Is it worthwhile? All we want is run arch-chroot to get into our bootstrap environment cleanly, so that is the only tool that would need adjustment. If we want to ensure compatibility here, I would make it #!/bin/sh compatible so it'll work everywhere. It would also need to deal with missing /run gracefully. signature.asc Description: OpenPGP digital signature
