Re: [arch-general] Deploy Arch linux to many virtual machines
On 23.01.2014 19:59, Кравец Роман wrote: How I can make auto-installation over PXE in Arch? https://wiki.archlinux.org/index.php/PXE Put that into the kernel line: script=http://whatever.com/some-script-here; Used by this script upon the automatic root login on tty1: https://projects.archlinux.org/archiso.git/tree/configs/releng/root-image/root/.automated_script.sh Might also be helpful: My script for extracting a new iso: https://paste.xinu.at/Lcka/ Also my setup script: http://git.server-speed.net/users/flo/bin/tree/setup-arch-vm signature.asc Description: OpenPGP digital signature
Re: [arch-general] Deploy Arch linux to many virtual machines
On Thursday 23 Jan 2014 21:59:06 Plonky Duby wrote: You can use docker. http://docs.docker.io/en/latest/installation/archlinux/ Thank you; I was not aware of Docker. It looks *awesome*. Paul
Re: [arch-general] Deploy Arch linux to many virtual machines
On Friday, January 24, 2014 02:17:01 AM Paul Gideon Dann wrote: On Thursday 23 Jan 2014 21:59:06 Plonky Duby wrote: You can use docker. http://docs.docker.io/en/latest/installation/archlinux/ Thank you; I was not aware of Docker. It looks *awesome*. FYI, stock lxc works very well with arch. I have blogged about it at http://www.ghodechhap.net/blog/ -- Regards Shridhar
Re: [arch-general] Deploy Arch linux to many virtual machines
Dear Florian, Put that into the kernel line: script=http://whatever.com/some-script-here; It is answer to my questions!! Thank you! On Fri, Jan 24, 2014 at 1:43 PM, Florian Pritz bluew...@xinu.at wrote: On 23.01.2014 19:59, Кравец Роман wrote: How I can make auto-installation over PXE in Arch? https://wiki.archlinux.org/index.php/PXE Put that into the kernel line: script=http://whatever.com/some-script-here; Used by this script upon the automatic root login on tty1: https://projects.archlinux.org/archiso.git/tree/configs/releng/root-image/root/.automated_script.sh Might also be helpful: My script for extracting a new iso: https://paste.xinu.at/Lcka/ Also my setup script: http://git.server-speed.net/users/flo/bin/tree/setup-arch-vm -- С уважением, Кравец Роман.
[arch-general] /usr/bin/makepkg: eval: line 2180: unexpected EOF while looking for matching `}'
Guys,
I have a build that completes successfully, but the package is empty (other
than .PKGINFO and .MTREE). The build output contains the following:
/usr/bin/makepkg: eval: line 2180: unexpected EOF while looking for matching `}'
/usr/bin/makepkg: eval: line 2181: syntax error: unexpected end of file
== Making package: tde-adept 14.0.0-1 (Fri Jan 24 19:41:55 CST 2014)
== Retrieving sources...
- Found applications-adept.tar.gz
== Validating source files with md5sums...
applications-adept.tar.gz ... Passed
/usr/bin/makepkg: eval: line 2180: unexpected EOF while looking for matching `}'
/usr/bin/makepkg: eval: line 2181: syntax error: unexpected end of file
I have checked forums, etc. and this usually means you have missed a closing '
or somewhere in the pkgbuild and it is causing problems in makepkg. I have
checked the pkgbuild closely and run namcap and it doesn't report any problems.
Is there something obvious below, or is this a bug?
The PKGBUILD is:
# Maintainer: David C. Rankin drankinatty at gmail dot com
pkgname=tde-adept
pkgver=14.0.0
pkgrel=1
pkgdesc=TDE adept Advanced Package Management Tool - Trinity upstream GIT
version
arch=('i686' 'x86_64')
url=http://scm.trinitydesktop.org/scm/git/${pkgname#*-};
license=('GPL')
groups=('tde-dev' 'tde-complete')
depends=('tde-tdebase')
makedepends=('pkgconfig' 'autoconf')
# optdepends=()
provides=(${pkgname#*-})
options=('staticlibs' 'libtool' '!emptydirs')
# install='pkgname.install'
source=(applications-${pkgname#*-}.tar.gz)
md5sums=('4beffd7764446ae737e70c36084bdc4e')
build() {
cd ${srcdir}
## Set up environment
msg Setting PATH, Trinity Environment variables
# Source the QT and TDE profile
[ $QTDIR = ] . /etc/profile.d/tqt3.sh # or tqt3.sh
[ $TDEDIR = ] . /etc/profile.d/trinity.sh # or tde.sh
## Generate config files and update with autoreconf
cd ${srcdir}/${pkgname#*-}
msg Copying system libtool files
cp /usr/share/aclocal/libtool.m4 ./admin/libtool.m4.in
cp /usr/share/libtool/config/ltmain.sh ./admin
msg Running make -f admin/Makefile.common
make -f admin/Makefile.common
## configure
msg Configuring - ${pkgname}...
./configure \
--prefix=${TDEDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
--with-extra-includes=/usr/include/tqt:/usr/include/tqt/Qt \
--with-extra-libs=${TDEDIR}/lib/trinity \
--sysconfdir=${TDEDIR}/etc \
--localstatedir=/var \
--enable-debug=full
msg Building - ${pkgname}...
make $NUMJOBS
}
package() {
msg Packaging - $pkgname-$pkgver
cd ${srcdir}/${pkgname#*-}
make -j1 DESTDIR=$pkgdir install
}
--
David C. Rankin, J.D.,P.E.
Re: [arch-general] /usr/bin/makepkg: eval: line 2180: unexpected EOF while looking for matching `}'
Is there something obvious below, or is this a bug?
This line is causing this:
provides=(${pkgname#*-})
--
Kind regards,
Damian Nowak
StratusHost
www.AtlasHost.eu
Re: [arch-general] Is there a burning tool able to replace K3b?
On 01/21/2014 04:43 AM, Ralf Mardorf wrote: I'm experimenting with getting rid of Xfce and I'm testing Jwm at the moment, but generating the menu is PITA and to find good replacements for editors, file browsers etc. isn't easy. fluxbox is my favorite non-KDE/GTK desktop. Menu generation is a snap (any text editor pointed to ~/.fluxbox/menu will do) IIRC dfm is a good dual-pane file manager that is Qt/GTK independent. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] /usr/bin/makepkg: eval: line 2180: unexpected EOF while looking for matching `}'
On 01/24/2014 08:10 PM, Nowaker wrote:
Is there something obvious below, or is this a bug?
This line is causing this:
provides=(${pkgname#*-})
Thank you!
provides=('tde-adept')
It is working now.
--
David C. Rankin, J.D.,P.E.
Re: [arch-general] Is there a burning tool able to replace K3b?
On 01/24/2014 09:24 PM, David C. Rankin wrote: On 01/21/2014 04:43 AM, Ralf Mardorf wrote: I'm experimenting with getting rid of Xfce and I'm testing Jwm at the moment, but generating the menu is PITA and to find good replacements for editors, file browsers etc. isn't easy. fluxbox is my favorite non-KDE/GTK desktop. Menu generation is a snap (any text editor pointed to ~/.fluxbox/menu will do) IIRC dfm is a good dual-pane file manager that is Qt/GTK independent. +1 for fluxbox. Openbox and fvwm-crystal are also nice lightweight wm's. DR
[arch-general] Howto setup i686 archroot on x86_64 box? (not linux32 chroot)
All, I have built all x86_64 packages in an archroot on my x86_64 box. I would like to set up and i686 archroot on the same box to build the i686 packages on the same box due to build times dropping from about 8 hours on i686 to less than 3 on the x86_64 box. I am unclear how best to do it -- or if it is doable. I've read https://wiki.archlinux.org/index.php/Arch64_FAQ about multilib with ~/.makepkg.i686.conf and a true linux32 chroot setup, but none of those are specific to the archroot setup. Both seem like they would work, but don't know if they are the right choice for build the 110 packages TDE requires. I would like to do this in an archroot if possible. I use the Classic Way of handling the build specified in https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot. All dependency packages are installed in the rw layer of the chroot with the first package built, a [local] repo is created under $CHROOT/root/repo, and as packages are built, they are installed, the resulting package is copied to $CHROOT/root/repo, and the repo index is updated with repo-add, and the process repeats with the next package until the build of TDE is complete. (that chroot is usually used to finish and tweaks needed for that set of package, then deleted and a new archroot created for the next major set of updates) It seems like setting up another archroot, and installing multilib would allow an archroot to work, but how would you tell makechrootpkg to build the i686 version instead of the x86_64 version. I don't want to have to modify the PKGBUILDs or do a significant re-write of the build script that automates the build, but if it is as simple as changing the makechrootpkg call, that would be a simple config-file fix. How best to handle this? (or just use the old i686 box and run it overnight?) -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Howto setup i686 archroot on x86_64 box? (not linux32 chroot)
On 01/25/2014 12:25 AM, David C. Rankin wrote: All, I have built all x86_64 packages in an archroot on my x86_64 box. I would like to set up and i686 archroot on the same box to build the i686 packages on the same box due to build times dropping from about 8 hours on i686 to less than 3 on the x86_64 box. I am unclear how best to do it -- or if it is doable. I've read https://wiki.archlinux.org/index.php/Arch64_FAQ about multilib with ~/.makepkg.i686.conf and a true linux32 chroot setup, but none of those are specific to the archroot setup. Both seem like they would work, but don't know if they are the right choice for build the 110 packages TDE requires. I would like to do this in an archroot if possible. I use the Classic Way of handling the build specified in https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot. All dependency packages are installed in the rw layer of the chroot with the first package built, a [local] repo is created under $CHROOT/root/repo, and as packages are built, they are installed, the resulting package is copied to $CHROOT/root/repo, and the repo index is updated with repo-add, and the process repeats with the next package until the build of TDE is complete. (that chroot is usually used to finish and tweaks needed for that set of package, then deleted and a new archroot created for the next major set of updates) It seems like setting up another archroot, and installing multilib would allow an archroot to work, but how would you tell makechrootpkg to build the i686 version instead of the x86_64 version. I don't want to have to modify the PKGBUILDs or do a significant re-write of the build script that automates the build, but if it is as simple as changing the makechrootpkg call, that would be a simple config-file fix. How best to handle this? (or just use the old i686 box and run it overnight?) I've found: https://wiki.archlinux.org/index.php/Building_32-bit_packages_on_a_64-bit_system. I'll setup another chroot configured as suggested and build as usual in the i686 chroot. If there are any additional pointers of gotchas, please let me know. Thanks. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Howto setup i686 archroot on x86_64 box? (not linux32 chroot)
Am 25.01.2014 07:25, schrieb David C. Rankin: I use the Classic Way of handling the build specified in https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot. If you use devtools anyway (which you definitely should when building a packages for more than one computer), simply run 'sudo extra-x86_64-build sudo extra-i686-build' in the PKGBUILD directory. There's not much more to do. signature.asc Description: OpenPGP digital signature
