Re: [lfs-dev] Script to check package versions
Baho Utot wrote: > You can change > > } 2>&1 | tee -a $LOG > > to > > } |& tee -a $LOG > > > the |& does the same thing as 2>&1 Perhaps, but the construct I use is clear to me. There is more than one way to do things. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] util-linux issues
- Mail original -
> De: "Bruce Dubbs"
> À: "LFS Developers Mailinglist"
> Envoyé: Mercredi 15 Mai 2013 20:16:58
> Objet: Re: [lfs-dev] util-linux issues
>
> Gilles Espinasse wrote:
> >
> >
> > - Mail original -
> >> De: "Bruce Dubbs"
> >> À: "LFS Developers Mailinglist"
> >> Envoyé: Mardi 14 Mai 2013 20:59:08
> >> Objet: [lfs-dev] util-linux issues
> >>
> >> 1. The latest git commit in util-linux now has a fix for umount not
> >> remounting the root fs read only with a 'umount -a -r' command.
> >>
> >
> > My mind is that 2.23 has too much bugs. For serious use, I would
> > wait until 2.23.1 release.
> >
> > Test suite (non-root user) was ok with 2.22.2 and 2.23 show 9 fdisk
> > segfault and
> > ipcs: basic limits ... FAILED
> > (ipcs/limits2)
> > ipcs: mk-rm-shm ... FAILED
> > (ipcs/mk-rm-shm)
> > misc: fallocate ... FAILED
> > (misc/fallocate)
> > misc: ionice ... FAILED
> > (misc/ionice)
> >
>
> For me, I get All 113 tests PASSED, but that is not in an LFS chroot
> environment. That passes non-root.
>
Should be a clue that developer only run tests on 64 bits actually.
> When running 'sudo tests/run.sh', there are a bunch of issues because
> scsi_debug is not in the kernel. It also doesn't want to sync with
> 0.fedora.pool.ntp.org. One root level test seemed to hang.
>
In my build system, I solved the needed kernel modules issue by copying them
into the chroot before to enter the chroot.
The list of modules is 'scsi_debug crc-t10dif scsi_mod md-mod'.
I need too to create a mini modules.{alias,dep} for those modules inside the
chroot.
The only limit is that kernel version name of the running kernel need to be
different from the kernel version name to be build.
Anyway running util-linux test suite as root in LFS build order is not fully
usable as modprobe is not yet build.
And I would not let everyone run that test suite on everyone machine due to the
big warning at start test.
Copying modules inside the chroot half work for BLFS packages like mdadm or
parted (but I have multiple issues in mdadm test suite and one in parted).
> Overall, the tests are fairly new. We don't know if the errors are in
> the tests or the code. We do need ot keep an eye on this prior to the
> next stable LFS release.
>
> > Current git tree doesn't compile in make check (lib/ttyutils.c:)
>
> Intermittent git commits aren't used in LFS.
>
Sure, that was just to look if all 2.23 tests failures were already fixed.
Gilles
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] Script to check package versions
On 05/15/2013 03:56 PM, Bruce Dubbs wrote:
> William Harrington wrote:
>> On May 15, 2013, at 12:12 PM, Bruce Dubbs wrote:
>>
>>> Not quite. I just put that out as an example of fetching via
>>> svn/ftp/http and some examples of using regex expressions.
>>>
>>> The changes are not great, but the edited diff below shows the relevant
>>> changes. Mostly regex additions/changes.
>> Excellent. Thanks for the info. I'm planning on adding checks for my
>> current server build for packages I have installed. The script will give
>> me a great base to start from.
>>
>> I decided to increase my apache/php/mysql knowledge and created
>> databases for LFS or CLFS builds and I have the package name, version,
>> configure options, and notes (I use for the installation instructions as
>> well). I have it to where I can edit add or delete entries. As I
>> update versions I update the configure and notes if required.
>>
>> So each build I have a database and build order using mysql. A bit
>> overkill, but it is a good project!
> Yes, I 'd say it was a bit of overkill, but if it gives you some DB
> experience then it's good.
>
> You might want to like into https://mariadb.org/. mysql is being
> impacted by Oracle in some not-helpful ways.
>
> Personally, I have some simple bash scripts that log each package as
> it's built in a simple file. E.g:
>
> $ head packages-SVN-20121218.log
> Tue Dec 18 21:28:30 GMT 2012 /usr/src/bc/bc-1.06.95.tar.bz2
> Tue Dec 18 21:30:01 GMT 2012 /usr/src/lsb-release/lsb-release-1.4.tar.gz
> Tue Dec 18 21:41:49 GMT 2012 /usr/src/sudo/sudo-1.8.6p3.tar.gz
> Tue Dec 18 21:46:39 GMT 2012 /usr/src/openssl/openssl-1.0.1c.tar.gz
> Tue Dec 18 21:48:28 GMT 2012 /usr/src/openssh/openssh-6.1p1.tar.gz
> Wed Dec 19 00:09:11 GMT 2012 /usr/src/alsa/alsa-lib/alsa-lib-1.0.26.tar.bz2
> Wed Dec 19 00:16:23 GMT 2012
> /usr/src/alsa/alsa-utils/alsa-utils-1.0.26.tar.bz2
> Wed Dec 19 00:49:10 GMT 2012 /usr/src/cdparanoia/cdparanoia-III-10.2.src.tgz
> Wed Dec 19 04:08:34 GMT 2012 /usr/src/which/which-2.20.tar.gz
> Wed Dec 19 04:26:50 GMT 2012 /usr/src/yasm/yasm-1.2.0.tar.gz
>
> All my sources are in /usr/src and I just create a new Makefile for each
> revision for example I have:
>
> bc-1.06.log
> bc-1.06.95.log
> bc-1.06.95.tar.bz2
> bc-1.06.log
> bc-1.06.tar.gz
> make-bc-1.06
> make-bc-1.06.95
>
> If I want to build a new version, I copy make-bc-1.06.95 make-bc-1.xx.xx
> and edit the contents, most of which is boilerplate. Usually only a few
> commands or a version need to be updated:
>
> $ cat make-bc-1.06.95
> #!/bin/bash
>
> source /usr/src/stats
>
> ###
> # Installing bc
>
> DIR=`pwd`
> PROGRAM=bc-1.06.95
> LOG="$DIR/$PROGRAM.log"
> TITLE="$PROGRAM"
> TIMEFORMAT="$TIMEFMT $TITLE"
>
> BUILDDIR=/tmp/bc
>
> rm -f $LOG
> rm -rf $BUILDDIR
> mkdir $BUILDDIR
> cd $BUILDDIR
>
> before=`df -k /tmp | grep / | sed -e "s/ \{2,\}/ /g" | cut -d' ' -f3`
>
> tar -xf $DIR/$PROGRAM.tar.?z* || exit 1
>
> cd $PROGRAM
> { time \
> {
> echo Making $TITLE
> date
>
> ./configure --prefix=/usr --with-readline &&
> make&&
> #echo "quit" | ./bc/bc -l Test/checklib.b&&
> $SUDO make install
> }
> } 2>&1 | tee -a $LOG
You can change
} 2>&1 | tee -a $LOG
to
} |& tee -a $LOG
the |& does the same thing as 2>&1
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] Problem with xzless
On May 15, 2013, at 3:44 PM, Fernando wrote:
> # cat /etc/lfs-release
> SVN-20130512
> 64bit, built with jhalfs
>
> I am worried about this:
>
> Either as normal user or as root:
> env LANG=C xzless
> /home/fernando/Downloads/blfs/links-2.7-2013.05.15-17h21m20s.log.xz
>
> error message:
> /usr/bin/xzless: line 49: test: 458 (POSIX regular expressions):
> integer
> expression expected
>
> (used env in order to get English message, but it appears in my locale
> LANG too.)
>
> Line 49 of xzless is:
>
> if test "$(less -V | { read ver && echo ${ver#less }; })" -ge 429;
> then
>
> I am thinking in reinstalling xz, but before, please, can someone give
> me some advice?
>
> --
> []s,
> Fernando
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-dev
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
[lfs-dev] Problem with xzless
# cat /etc/lfs-release
SVN-20130512
64bit, built with jhalfs
I am worried about this:
Either as normal user or as root:
env LANG=C xzless
/home/fernando/Downloads/blfs/links-2.7-2013.05.15-17h21m20s.log.xz
error message:
/usr/bin/xzless: line 49: test: 458 (POSIX regular expressions): integer
expression expected
(used env in order to get English message, but it appears in my locale
LANG too.)
Line 49 of xzless is:
if test "$(less -V | { read ver && echo ${ver#less }; })" -ge 429; then
I am thinking in reinstalling xz, but before, please, can someone give
me some advice?
--
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] Script to check package versions
On May 15, 2013, at 2:56 PM, Bruce Dubbs wrote: You might want to like into https://mariadb.org/. mysql is being impacted by Oracle in some not-helpful ways. I moved from Solaris to linux with my sun machines when oracle took over as they squashed free support for required patches. Was looking into MariaDB long ago, but I could never get it to build past a certain point cause of an error based in additions MariaDB with their sql_logger: /sources/blfs/mariadb-5.5.30/plugin/sql_errlog/sql_logger.cc:25:8: error: ‘PSI_mutex_key’ does not name a type /sources/blfs/mariadb-5.5.30/plugin/sql_errlog/sql_logger.cc:26:8: error: ‘PSI_mutex_info’ does not name a type /sources/blfs/mariadb-5.5.30/plugin/sql_errlog/sql_logger.cc: In function ‘void init_logger_mutexes()’: /sources/blfs/mariadb-5.5.30/plugin/sql_errlog/sql_logger.cc:192:17: error: ‘PSI’ has no member named ‘register_mutex’ /sources/blfs/mariadb-5.5.30/plugin/sql_errlog/sql_logger.cc:192:46: error: ‘mutex_list’ was not declared in this scope Otherwise I'd use it. It's been that way with each release. I'm tired of debugging it. Sincerely, William Harrington-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] Script to check package versions
William Harrington wrote:
>
> On May 15, 2013, at 12:12 PM, Bruce Dubbs wrote:
>
>> Not quite. I just put that out as an example of fetching via
>> svn/ftp/http and some examples of using regex expressions.
>>
>> The changes are not great, but the edited diff below shows the relevant
>> changes. Mostly regex additions/changes.
>
> Excellent. Thanks for the info. I'm planning on adding checks for my
> current server build for packages I have installed. The script will give
> me a great base to start from.
>
> I decided to increase my apache/php/mysql knowledge and created
> databases for LFS or CLFS builds and I have the package name, version,
> configure options, and notes (I use for the installation instructions as
> well). I have it to where I can edit add or delete entries. As I
> update versions I update the configure and notes if required.
>
> So each build I have a database and build order using mysql. A bit
> overkill, but it is a good project!
Yes, I 'd say it was a bit of overkill, but if it gives you some DB
experience then it's good.
You might want to like into https://mariadb.org/. mysql is being
impacted by Oracle in some not-helpful ways.
Personally, I have some simple bash scripts that log each package as
it's built in a simple file. E.g:
$ head packages-SVN-20121218.log
Tue Dec 18 21:28:30 GMT 2012 /usr/src/bc/bc-1.06.95.tar.bz2
Tue Dec 18 21:30:01 GMT 2012 /usr/src/lsb-release/lsb-release-1.4.tar.gz
Tue Dec 18 21:41:49 GMT 2012 /usr/src/sudo/sudo-1.8.6p3.tar.gz
Tue Dec 18 21:46:39 GMT 2012 /usr/src/openssl/openssl-1.0.1c.tar.gz
Tue Dec 18 21:48:28 GMT 2012 /usr/src/openssh/openssh-6.1p1.tar.gz
Wed Dec 19 00:09:11 GMT 2012 /usr/src/alsa/alsa-lib/alsa-lib-1.0.26.tar.bz2
Wed Dec 19 00:16:23 GMT 2012
/usr/src/alsa/alsa-utils/alsa-utils-1.0.26.tar.bz2
Wed Dec 19 00:49:10 GMT 2012 /usr/src/cdparanoia/cdparanoia-III-10.2.src.tgz
Wed Dec 19 04:08:34 GMT 2012 /usr/src/which/which-2.20.tar.gz
Wed Dec 19 04:26:50 GMT 2012 /usr/src/yasm/yasm-1.2.0.tar.gz
All my sources are in /usr/src and I just create a new Makefile for each
revision for example I have:
bc-1.06.log
bc-1.06.95.log
bc-1.06.95.tar.bz2
bc-1.06.log
bc-1.06.tar.gz
make-bc-1.06
make-bc-1.06.95
If I want to build a new version, I copy make-bc-1.06.95 make-bc-1.xx.xx
and edit the contents, most of which is boilerplate. Usually only a few
commands or a version need to be updated:
$ cat make-bc-1.06.95
#!/bin/bash
source /usr/src/stats
###
# Installing bc
DIR=`pwd`
PROGRAM=bc-1.06.95
LOG="$DIR/$PROGRAM.log"
TITLE="$PROGRAM"
TIMEFORMAT="$TIMEFMT $TITLE"
BUILDDIR=/tmp/bc
rm -f $LOG
rm -rf $BUILDDIR
mkdir $BUILDDIR
cd $BUILDDIR
before=`df -k /tmp | grep / | sed -e "s/ \{2,\}/ /g" | cut -d' ' -f3`
tar -xf $DIR/$PROGRAM.tar.?z* || exit 1
cd $PROGRAM
{ time \
{
echo Making $TITLE
date
./configure --prefix=/usr --with-readline &&
make&&
#echo "quit" | ./bc/bc -l Test/checklib.b&&
$SUDO make install
}
} 2>&1 | tee -a $LOG
if [ $PIPESTATUS -ne 0 ]; then exit 1; fi;
stats $LOG $DIR/$PROGRAM.tar.?z* $before
exit 0
I'm just mentioning some alternatives here.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] Script to check package versions
On May 15, 2013, at 12:12 PM, Bruce Dubbs wrote: Not quite. I just put that out as an example of fetching via svn/ftp/http and some examples of using regex expressions. The changes are not great, but the edited diff below shows the relevant changes. Mostly regex additions/changes. Excellent. Thanks for the info. I'm planning on adding checks for my current server build for packages I have installed. The script will give me a great base to start from. I decided to increase my apache/php/mysql knowledge and created databases for LFS or CLFS builds and I have the package name, version, configure options, and notes (I use for the installation instructions as well). I have it to where I can edit add or delete entries. As I update versions I update the configure and notes if required. So each build I have a database and build order using mysql. A bit overkill, but it is a good project! There are lots of good things that are shared among the LFS community that others can use. Sincerely, WIlliam Harrington-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] util-linux issues
Gilles Espinasse wrote: > > > - Mail original - >> De: "Bruce Dubbs" >> À: "LFS Developers Mailinglist" >> Envoyé: Mardi 14 Mai 2013 20:59:08 >> Objet: [lfs-dev] util-linux issues >> >> 1. The latest git commit in util-linux now has a fix for umount not >> remounting the root fs read only with a 'umount -a -r' command. >> > > My mind is that 2.23 has too much bugs. For serious use, I would > wait until 2.23.1 release. > > Test suite (non-root user) was ok with 2.22.2 and 2.23 show 9 fdisk segfault > and > ipcs: basic limits ... FAILED (ipcs/limits2) > ipcs: mk-rm-shm ... FAILED (ipcs/mk-rm-shm) > misc: fallocate ... FAILED (misc/fallocate) > misc: ionice ... FAILED (misc/ionice) > For me, I get All 113 tests PASSED, but that is not in an LFS chroot environment. That passes non-root. When running 'sudo tests/run.sh', there are a bunch of issues because scsi_debug is not in the kernel. It also doesn't want to sync with 0.fedora.pool.ntp.org. One root level test seemed to hang. Overall, the tests are fairly new. We don't know if the errors are in the tests or the code. We do need ot keep an eye on this prior to the next stable LFS release. > Current git tree doesn't compile in make check (lib/ttyutils.c:) Intermittent git commits aren't used in LFS. > losetup with offset is broken (is now fixed and test suite has been added) > > By the way, bc is used in one test (test is ignored if bc is not found) bc has been added to LFS. We may need to move it up when we start running the test suite. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] util-linux issues
- Mail original - > De: "Bruce Dubbs" > À: "LFS Developers Mailinglist" > Envoyé: Mardi 14 Mai 2013 20:59:08 > Objet: [lfs-dev] util-linux issues > > 1. The latest git commit in util-linux now has a fix for umount not > remounting the root fs read only with a 'umount -a -r' command. > My mind is that 2.23 has too much bugs. For serious use, I would wait until 2.23.1 release. Test suite (non-root user) was ok with 2.22.2 and 2.23 show 9 fdisk segfault and ipcs: basic limits ... FAILED (ipcs/limits2) ipcs: mk-rm-shm ... FAILED (ipcs/mk-rm-shm) misc: fallocate ... FAILED (misc/fallocate) misc: ionice ... FAILED (misc/ionice) Current git tree doesn't compile in make check (lib/ttyutils.c:) losetup with offset is broken (is now fixed and test suite has been added) By the way, bc is used in one test (test is ignored if bc is not found) Gilles -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] Script to check package versions
William Harrington wrote:
>
> On May 14, 2013, at 11:27 PM, Bruce Dubbs wrote:
>
>> I fixed that a couple of days ago.
>>
>> -- Bruce
>>
> Is the script at
> http://anduin.linuxfromscratch.org/~bdubbs/lfs-latest-files reflecting
> your changes or do you copy the script after changes?
Not quite. I just put that out as an example of fetching via
svn/ftp/http and some examples of using regex expressions.
The changes are not great, but the edited diff below shows the relevant
changes. Mostly regex additions/changes.
-- Bruce
--- public_html/lfs-latest-files.phps 2013-05-10 14:27:18.0 +
+++ latest.php 2013-05-15 02:55:03.0 +
@@ -11,14 +11,16 @@
$exceptions[ 'gmp' ] = "UPDIR=/.*(gmp-\d[\d\.-]*\d).*/:DOWNDIR=";
$regex = array();
-$regex[ 'bzip2' ] = "/^.*current version is ([\d\.]+).*$/";
-$regex[ 'expect' ] = "/^.*Download expect([\d\.]+)\.tar.*$/";
-$regex[ 'mpc'] = "/^Version ([\d\.]+).*$/";
-$regex[ 'mpfr' ] = "/^mpfr-([\d\.]+)\.tar.*$/";
-$regex[ 'tcl'] = "/^.*Download tcl([\d\.]+)-src.*$/";
-$regex[ 'tzdata' ] = "/^.*tzdata([\d]+[a-z]).*$/";
-$regex[ 'xz' ] = "/^.*xz-([\d\.]*\d).*$/";
-$regex[ 'zlib' ] = "/^.*zlib ([\d\.]*\d).*$/";
+$regex[ 'bzip2'] = "/^.*current version is ([\d\.]+).*$/";
+$regex[ 'expect' ] = "/^.*Download expect([\d\.]+)\.tar.*$/";
+$regex[ 'less' ] = "/^.*current released version is less-(\d+).*$/";
+$regex[ 'mpc' ] = "/^Version ([\d\.]+).*$/";
+$regex[ 'mpfr' ] = "/^mpfr-([\d\.]+)\.tar.*$/";
+$regex[ 'sysvinit' ] = "/^.*sysvinit-([\d\.]+)dsf\.tar.*$/";
+$regex[ 'tcl' ] = "/^.*Download tcl([\d\.]+)-src.*$/";
+$regex[ 'tzdata' ] = "/^.*tzdata([\d]+[a-z]).*$/";
+$regex[ 'xz' ] = "/^.*xz-([\d\.]*\d).*$/";
+$regex[ 'zlib' ] = "/^.*zlib ([\d\.]*\d).*$/";
function find_max( $lines, $regex_match, $regex_replace )
{
@@ -202,7 +207,7 @@
foreach ( $lines as $l )
{
if ( preg_match( "/sperl/", $l ) ) continue; // Don't want this
-$ver = preg_replace( "/^.*$package-([\d\.-]*\d).*$/", "$1", $l );
+$ver = preg_replace( "/^.*perl-([\d\.]+\d)\.tar.*$/", "$1", $l );
if ( $ver == $l ) continue;
list( $s1, $s2, $rest ) = explode( ".", $ver );
if ( $s2 % 2 == 1 ) continue; // Remove odd minor versions
@@ -214,7 +219,7 @@
// Most packages are in the form $package-n.n.n
// Occasionally there are dashes (e.g. 201-1)
- $max = find_max( $lines, "/$package/", "/^.*$package-([\d\.-]*\d).*$/" );
+ $max = find_max( $lines, "/$package/",
"/^.*$package-([\d\.-]*\d)\.tar.*$/" );
return $max;
}
@@ -282,10 +288,13 @@
global $vers;
global $dirs;
$to = "lfs-b...@linuxfromscratch.org";
+ $from= "bdu...@linuxfromscratch.org";
$subject = "LFS Package Currency Check - $date GMT";
+ $headers = "From: bdu...@anduin.linuxfromscratch.org";
- $message = "Package LFS Upstream Flag\n\n";
+ $message = "Package LFS Upstream Flag\n\n";
foreach ( $dirs as $pkg => $dir )
{
@@ -297,13 +306,14 @@
// Pad for output
$pad = "";
$p = substr( $pkg . $pad, 0, 15 );
- $l = substr( $vers[ $pkg ] . $pad, 0, 7 );
+ $l = substr( $vers[ $pkg ] . $pad, 0, 8 );
$c = substr( $v. $pad, 0, 10 );
$message .= "$p $l $c $flag\n";
}
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] login error after intallng linux-PAM, cracklib and reinstall shadow , need help
> If you follow the BLFS shadow page after installing linux-pam, those > get commented. > It's under the heading: Configuring Linux-PAM to Work with Shadow > Read carefully which options you want for shadow and what you should > be enabling or disabling thank's is work, . -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
