January 2017 - CRUX - lists.crux.nu

Re: CRUX Boot fails from Ubuntu Grub2
by Steve Volumetric 27 Jan '17

27 Jan '17

How or more importantly why are you using Ubuntu's grub2 in crux? Is it an EFI system? I'm not sure what you mean by UUID in the context of fstab, I almost always have something like: /dev/sdb1 / ext4 defaults,noatime(or whatever) 0 1 I wouldn't recommend using utilities for a different distrobution, crux comes with grub2. -vsteve On Fri, Jan 27, 2017 at 11:42 AM, Milton Smith <miltonsj(a)gmail.com> wrote: > I am trying to boot from the Grub that comes standard with an Ubuntu > installation. I am installing on bare metal. I did compile my root > filesystem into the kernel. I am using ext4. I did setup fstab with the > uuid of the CRUX partition. Sorry for the confusion. > > Sent from BlueMail <http://www.bluemail.me/r> > On Jan 27, 2017, at 9:55 AM, Steve Volumetric <volumetricsteve(a)gmail.com> > wrote: >> >> I have a few questions, but first, what is "ubuntu grub2"? Are you >> installing on a VM or bare metal? >> Did you compile your root file system into your kernel? What file system >> are you using on your root file system? Did you set up fstab? >> >> -vsteve >> >> On Fri, Jan 27, 2017 at 10:46 AM, Milton Smith <miltonsj(a)gmail.com> >> wrote: >> >>> Everytime I try to boot CRUX from Ubuntu's Grub2 it fails with a kernel >>> panic. >>> >>> It gives me the error message, " unable to mount root filesystem on >>> unknown block (0,0)". >>> >>> Can someone help me with this? Thanks! >>> >>> Sent from BlueMail <http://www.bluemail.me/r> >>> >>> ______________________________ _________________ >>> CRUX mailing list >>> CRUX(a)lists.crux.nu >>> https://lists.crux.nu/mailman/listinfo/crux >>> >>> >>

1 0

CRUX Boot fails from Ubuntu Grub2
by Milton Smith 27 Jan '17

27 Jan '17

⁣Everytime I try to boot CRUX from Ubuntu's Grub2 it fails with a kernel panic. It gives me the error message, " unable to mount root filesystem on unknown block (0,0)". Can someone help me with this? Thanks! Sent from BlueMail

2 1

ports/opt (3.3): [notify] hexchat: some users get missing autoconf-archive on configure, since it's so small depend on it
by crux＠crux.nu 26 Jan '17

26 Jan '17

commit 5ac653a2396dac0750e4e21e79ed16b34a4042f9 Author: Danny Rawlins <monster.romster(a)gmail.com> Date: Thu Jan 26 12:01:57 2017 +1100 [notify] hexchat: some users get missing autoconf-archive on configure, since it's so small depend on it diff --git a/hexchat/Pkgfile b/hexchat/Pkgfile index 0b70787..3a80607 100644 --- a/hexchat/Pkgfile +++ b/hexchat/Pkgfile @@ -2,7 +2,7 @@ # URL: http://hexchat.github.io/ # Maintainer: Danny Rawlins, crux at romster dot me # Packager: Danny Rawlins, crux at romster dot me -# Depends on: intltool iso-codes libnotify libsexy pciutils xorg-libxdamage +# Depends on: autoconf-archive intltool iso-codes libnotify libsexy pciutils xorg-libxdamage # Optional: enchant libcanberra lua name=hexchat

1 0

Re:Re: why does pkgmk exports PKG and SRC?
by phi 26 Jan '17

26 Jan '17

> On the other hand I can't find a difference in> exporting PKG and SRC and calling build afterwards versus calling > "PKG=$PKG SRC=$SRC build" - maybe I'm missing something here ... Oh I was wrong, they are the same if build was a shell script, since build is a function, "PKG=$PKG SRC=$SRC build" is equivalent to "build". > If I look at pkgmk, it should not be required to "export PKG=$pkg" in your > build function at the end. Yes, I just forgot the build function is already inside a subshell: (set -e -x ; build) So no need to retain $PKG after the build. While export does have side effects on build scripts. I think the build function itself works even if PKG is not exported, since the Pkgfile is sourced inside pkgmk. if does not export PKG, then PKG is still available inside the build function, and it won't propagate to build scripts. I have verified that by removing the export command from pkgmk, my port builds fine without any special treatment.

1 0

ports/opt (3.2): [notify] hexchat: some users get missing autoconf-archive on configure, since it's so small depend on it
by crux＠crux.nu 26 Jan '17

26 Jan '17

commit 5ac653a2396dac0750e4e21e79ed16b34a4042f9 Author: Danny Rawlins <monster.romster(a)gmail.com> Date: Thu Jan 26 12:01:57 2017 +1100 [notify] hexchat: some users get missing autoconf-archive on configure, since it's so small depend on it diff --git a/hexchat/Pkgfile b/hexchat/Pkgfile index 0b70787..3a80607 100644 --- a/hexchat/Pkgfile +++ b/hexchat/Pkgfile @@ -2,7 +2,7 @@ # URL: http://hexchat.github.io/ # Maintainer: Danny Rawlins, crux at romster dot me # Packager: Danny Rawlins, crux at romster dot me -# Depends on: intltool iso-codes libnotify libsexy pciutils xorg-libxdamage +# Depends on: autoconf-archive intltool iso-codes libnotify libsexy pciutils xorg-libxdamage # Optional: enchant libcanberra lua name=hexchat

1 0

why does pkgmk exports PKG and SRC?
by phi 25 Jan '17

25 Jan '17

Hi, everyone, I've just encountered a weird bug when I'm making a port, the configure script works fine if I run it by hand, but always fail if it was invoked inside pkgmk. After digging for a while, I found out that the configure script uses the shell variable PKG internally. Checked pkgmk, I see that pkgmk exports PKG and SRC before calling build(). Relevant code in pkgmk: build_package() { ... make_work_dir # here export PKG and SRC ... (set -e -x ; build) I think it's better to change that to: build_package() { ... make_work_dir # do not export ... (set -e -x; PKG=$PKG SRC=$SRC build) I don't know if this change would affect other things. Without making any change in pkgmk, my port currently looks like: build() { local pkg=$PKG unset PKG ... # build using $pkg export PKG=$pkg }

2 1

[ANN] CRUX 3.3-rc3 available for testing
by Matt Housh 24 Jan '17

24 Jan '17

Greetings, The CRUX team is pleased to announce the availability of a third release candidate for the upcoming CRUX 3.3. I didn't bother to announce -rc2 as it wasn't particularly interesting. Please note that this is a release candidate, NOT the final release. Please test it if you have a chance and report any problems you find to us! Note that this means problems with the ISO or installation/upgrade process; ports issues should be reported in the usual way. Important details about the upcoming release can be found here: http://crux.nu/Wiki/TODO33 The ISO itself can be found here: https://crux.ninja/crux/crux-3.3-rc3.iso https://crux.ninja/crux/crux-3.3-rc3.md5 Enjoy! Cheers, Matt (for the CRUX team)

1 0

ports/opt (3.3): [notify] php: update to 5.6.30
by crux＠crux.nu 20 Jan '17

20 Jan '17

commit 0b84d8a01c93cafbeffc1d7a4af272679cd17519 Author: Juergen Daubert <jue(a)jue.li> Date: Fri Jan 20 12:10:41 2017 +0100 [notify] php: update to 5.6.30 Security update, see http://php.net/archive/2017.php#id2017-01-19-3 diff --git a/php/.md5sum b/php/.md5sum index 79c1fec..f9084c6 100644 --- a/php/.md5sum +++ b/php/.md5sum @@ -1 +1 @@ -190bf5b52d1fc68d5500a8cdc7e33164 php-5.6.29.tar.xz +68753955a8964ae49064c6424f81eb3e php-5.6.30.tar.xz diff --git a/php/Pkgfile b/php/Pkgfile index 605757d..7b015c7 100644 --- a/php/Pkgfile +++ b/php/Pkgfile @@ -4,7 +4,7 @@ # Depends on: readline libpcre libxml2 curl db gdbm xz name=php -version=5.6.29 +version=5.6.30 release=1 source=(http://php.net/distributions/php-$version.tar.xz)

1 0

ports/opt (3.2): [notify] php: update to 5.6.30
by crux＠crux.nu 20 Jan '17

20 Jan '17

commit 0b84d8a01c93cafbeffc1d7a4af272679cd17519 Author: Juergen Daubert <jue(a)jue.li> Date: Fri Jan 20 12:10:41 2017 +0100 [notify] php: update to 5.6.30 Security update, see http://php.net/archive/2017.php#id2017-01-19-3 diff --git a/php/.md5sum b/php/.md5sum index 79c1fec..f9084c6 100644 --- a/php/.md5sum +++ b/php/.md5sum @@ -1 +1 @@ -190bf5b52d1fc68d5500a8cdc7e33164 php-5.6.29.tar.xz +68753955a8964ae49064c6424f81eb3e php-5.6.30.tar.xz diff --git a/php/Pkgfile b/php/Pkgfile index 605757d..7b015c7 100644 --- a/php/Pkgfile +++ b/php/Pkgfile @@ -4,7 +4,7 @@ # Depends on: readline libpcre libxml2 curl db gdbm xz name=php -version=5.6.29 +version=5.6.30 release=1 source=(http://php.net/distributions/php-$version.tar.xz)

1 0

ports/opt (3.3): [notify] jre: update to 1.8.0_121
by crux＠crux.nu 19 Jan '17

19 Jan '17

commit d2f89531627a8ea86558fa6cbc3af75f1793076a Author: Juergen Daubert <jue(a)jue.li> Date: Thu Jan 19 10:26:30 2017 +0100 [notify] jre: update to 1.8.0_121 Includes security fixes, see http://www.oracle.com/technetwork/java/javase/8u121-relnotes-3315208.html diff --git a/jre/.md5sum b/jre/.md5sum index 9f0cb39..3df319f 100644 --- a/jre/.md5sum +++ b/jre/.md5sum @@ -1 +1 @@ -5ccc09b2cbbf715b583fad72b070b69d jre-8u112-linux-x64.tar.gz +093e22e4f0a55420780a0e437ab9fcd4 jre-8u121-linux-x64.tar.gz diff --git a/jre/Pkgfile b/jre/Pkgfile index 9021346..2b63e76 100644 --- a/jre/Pkgfile +++ b/jre/Pkgfile @@ -4,7 +4,7 @@ # Packager: Simone Rota, sip at crux dot nu name=jre -version=1.8.0_112 +version=1.8.0_121 release=1 source=(file:///$name-8u${version#*_}-linux-x64.tar.gz)

1 0