[arch-dev-public] New devtools in testing
I pushed a 0.4 release of devtools to the testing repository tonight. Please install them and let Aaron, Jason, or I know if you find any problems. Highlights: * Two new scripts to assist with chroot creation and builds * extrapkg now takes an -l argument to limit the scp upload bandwidth (Andy, please test) -Dan
2007/10/30, Dan McGee <dpmcgee@gmail.com>:
I pushed a 0.4 release of devtools to the testing repository tonight. Please install them and let Aaron, Jason, or I know if you find any problems.
Highlights: * Two new scripts to assist with chroot creation and builds * extrapkg now takes an -l argument to limit the scp upload bandwidth (Andy, please test)
Tested extrapkg 5 minutes ago. [roman@linuxbox ftjam]$ extrapkg roman@archlinux.org's password: ftjam-2.5.3rc2-1-i686.pkg.tar.gz 100% 40KB 40.5KB/s 00:00 roman@archlinux.org's password: File integrity okay. ===> Uploaded /home/roman/packages/ftjam-2.5.3rc2-1-i686.pkg.tar.gz cvs commit: Examining . roman@cvs.archlinux.org's password: ===> Commited with "upgpkg: ftjam 2.5.3rc2-1" message roman@cvs.archlinux.org's password: cvs tag: Tagging . ===> Tagged as CURRENT The fun thing is that it asked my password 4 times. :-P I should use ssh keys. -- Roman Kyrylych (Роман Кирилич)
Roman Kyrylych schrieb:
The fun thing is that it asked my password 4 times. :-P I should use ssh keys.
Another cool solution: Put this in ~/.ssh/config ControlPath /home/roman/.ssh/master-%h-%p-%r Host gerolde HostName archlinux.org Host cvs.archlinux.org HostName archlinux.org Then run ssh -M roman@gerolde once (leave this session open until you are done with whatever you do). Then try ssh roman@gerolde, you won't be asked for a password. Furthermore, connecting is much faster, because the old connection is reused.
2007/10/30, Dan McGee <dpmcgee@gmail.com>:
I pushed a 0.4 release of devtools to the testing repository tonight. Please install them and let Aaron, Jason, or I know if you find any problems.
Highlights: * Two new scripts to assist with chroot creation and builds * extrapkg now takes an -l argument to limit the scp upload bandwidth (Andy, please test)
Some bugs in makechrootpkg: 1) It doesn't check for --help before checking if there is PKGBUILD [root@linuxbox pkgbuilds]# makechrootpkg --help This must be run in the directory of a built package. 2) It doesn't pass unrecognized options to makepkg: [root@linuxbox gossip]# makechrootpkg -g /usr/sbin/makechrootpkg: illegal option -- g usage makechrootpkg [-h] [-c CHROOT_SHELL] [makepkg args] Run this script in a PKGBUILD dir to build a package inside a clean chroot. All unrecognized arguments passed to this script will be passed to makepkg. The $CHROOT_SHELL environment variable is used to determine where your chroot shell is. The shell consists of the following directories: $CHROOT_SHELL/{root, rw, union} but only 'root' is required by default. The rest will be created as needed The chroot shell 'root' directory must be created via the following command: mkarchroot $CHROOT_SHELL base base-devel sudo Default makepkg args: -Ss 3) It doesn't work [root@linuxbox gossip]# makechrootpkg building union chroot moving build files to chroot allowing 'nobody' sudo rights in the chroot /usr/sbin/makechrootpkg: line 97: /chroot/union/etc/sudoers: No such file or directory /usr/sbin/makechrootpkg: line 111: ./mkarchroot: No such file or directory build complete... check $CHROOT_SHELL/build for build results cleaning up unioned mounts [root@linuxbox gossip]# ls /chroot/build ls: cannot access /chroot/build: No such file or directory chroot was created with mkarchroot $CHROOT_SHELL base base-devel sudo where $CHROOT_SHELL is /chroot P.S.: after sudo will be in base or base-devel the usage message in makechrootpkg should be updated. I didn't looked inside makechrootpkg yet, when I'll have more time I'll try to find the reason why it fails here. -- Roman Kyrylych (Роман Кирилич)
On 10/31/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/10/30, Dan McGee <dpmcgee@gmail.com>:
I pushed a 0.4 release of devtools to the testing repository tonight. Please install them and let Aaron, Jason, or I know if you find any problems.
Highlights: * Two new scripts to assist with chroot creation and builds * extrapkg now takes an -l argument to limit the scp upload bandwidth (Andy, please test)
Some bugs in makechrootpkg:
1) It doesn't check for --help before checking if there is PKGBUILD
[root@linuxbox pkgbuilds]# makechrootpkg --help This must be run in the directory of a built package.
2) It doesn't pass unrecognized options to makepkg:
[root@linuxbox gossip]# makechrootpkg -g /usr/sbin/makechrootpkg: illegal option -- g usage makechrootpkg [-h] [-c CHROOT_SHELL] [makepkg args] Run this script in a PKGBUILD dir to build a package inside a clean chroot. All unrecognized arguments passed to this script will be passed to makepkg.
The $CHROOT_SHELL environment variable is used to determine where your chroot shell is. The shell consists of the following directories: $CHROOT_SHELL/{root, rw, union} but only 'root' is required by default. The rest will be created as needed
The chroot shell 'root' directory must be created via the following command: mkarchroot $CHROOT_SHELL base base-devel sudo
Default makepkg args: -Ss
3) It doesn't work
[root@linuxbox gossip]# makechrootpkg building union chroot moving build files to chroot allowing 'nobody' sudo rights in the chroot /usr/sbin/makechrootpkg: line 97: /chroot/union/etc/sudoers: No such file or directory /usr/sbin/makechrootpkg: line 111: ./mkarchroot: No such file or directory build complete... check $CHROOT_SHELL/build for build results cleaning up unioned mounts [root@linuxbox gossip]# ls /chroot/build ls: cannot access /chroot/build: No such file or directory
chroot was created with mkarchroot $CHROOT_SHELL base base-devel sudo where $CHROOT_SHELL is /chroot
P.S.: after sudo will be in base or base-devel the usage message in makechrootpkg should be updated.
I didn't looked inside makechrootpkg yet, when I'll have more time I'll try to find the reason why it fails here.
Maybe put these issues on flyspray? I'm not overly concerned about the new tools working perfectly (as long as they don't completely break your system). Because no one depends on them yet, I just wanted to get them out there so we can do an archiso release in the next couple of days. -Dan
2007/10/31, Dan McGee <dpmcgee@gmail.com>:
On 10/31/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/10/30, Dan McGee <dpmcgee@gmail.com>:
I pushed a 0.4 release of devtools to the testing repository tonight. Please install them and let Aaron, Jason, or I know if you find any problems.
Highlights: * Two new scripts to assist with chroot creation and builds * extrapkg now takes an -l argument to limit the scp upload bandwidth (Andy, please test)
Some bugs in makechrootpkg:
[skipped]
Maybe put these issues on flyspray? I'm not overly concerned about the new tools working perfectly (as long as they don't completely break your system). Because no one depends on them yet, I just wanted to get them out there so we can do an archiso release in the next couple of days.
http://bugs.archlinux.org/task/8468 -- Roman Kyrylych (Роман Кирилич)
Am Mon, 29 Oct 2007 21:47:14 -0500 schrieb "Dan McGee" <dpmcgee@gmail.com>:
* extrapkg now takes an -l argument to limit the scp upload bandwidth (Andy, please test)
I'm using it from git now for a while. Works well with -l and the PKGDEST for uploading in extrapkg. I'm also using now ssh keys. It's ready to move I think. It would be nice to have the usage of PKGDEST also for checkpkg. Also checkpkg should check first if the oldpkg already exists there. Right now I mount the PKGDEST temporarly into each chroot to have two common pkg collecting directories, one for each architecture. That also allows me to use "corepkg" from outside the core chroot. But it's useless since we have to sign off packages. I can use extrapkg also for i686 extra repository from within the i686 extra chroot. To be able to use testingpkg/corepkg from within i686 core chroot I'm forced to install i686 cvs pkg into the core chroot. Not a clean way but a possible solution. Any other way known? -Andy
On 10/31/07, Andreas Radke <a.radke@arcor.de> wrote:
Am Mon, 29 Oct 2007 21:47:14 -0500 schrieb "Dan McGee" <dpmcgee@gmail.com>:
* extrapkg now takes an -l argument to limit the scp upload bandwidth (Andy, please test)
I'm using it from git now for a while. Works well with -l and the PKGDEST for uploading in extrapkg. I'm also using now ssh keys.
It's ready to move I think.
And its off to extra, for both architectures. -Dan
participants (4)
-
Andreas Radke
-
Dan McGee
-
Roman Kyrylych
-
Thomas Bächler