Re: [alfs-log] [ALFS Trac] #1726: Change SBU report to use lscpu
#1726: Change SBU report to use lscpu --+- Reporter: bdubbs@… | Owner: pierre Type: defect| Status: closed Priority: normal| Milestone: 3.0 Component: jhalfs| Version: SVN Severity: normal| Resolution: fixed Keywords:| --+- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: fixed at r4174 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1726#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1700: Remove && in BLFS scripts
#1700: Remove && in BLFS scripts -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+--- Changes (by pierre): * owner: alfs-log@… => pierre * status: new => assigned Comment: I think I'll remove the && except when preceded by [...] or test ... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1700#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[alfs-log] [ALFS Trac] #1721: Some installation instructions are not generated correctly when using porg
#1721: Some installation instructions are not generated correctly when using porg + Reporter: pierre | Owner: alfs-log@… Type: defect | Status: new Priority: normal | Milestone: 3.0 Component: ablfs |Version: SVN Severity: normal | Keywords: + Generating installation instructions for BLFS, taking into account whether running as user or root, whether using porg, destdir package management or nothing is a complicated task because markup in the book is not very accurate: - The only indication telling a tag is an installation instructions is that has a role="root" attribute, and that the tag occurs in a sect2 with role="installation" attribute. But some of those tags are not installation instructions: for example, they can be user or group adding, or some database updating (mime, desktop, icons, ...). - There may be several tags, which should be grouped in order to generate the porg logging correctly. But if they are interspersed with config instructions, this is hard... This may lead to buggy instructions, for example beginning with porg opening stanzas and finishing without closing stanzas, or converse... Also, some single quotes may be escaped (as `'\''`), when not needed, leading to errors when running the script... This can be improved in two directions: - improve the stylesheet generating those instructions. - improve the book itself so that different types of instructions are more clearly identified (and of course adapt the stylesheet to use that). -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1721> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1719: Some files may be not logged when using cmake+porg
#1719: Some files may be not logged when using cmake+porg +- Reporter: pierre | Owner: alfs-log@… Type: defect | Status: new Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +- Comment (by pierre): There are two possibilities for avoiding that (maybe others, of course): - One brutal way is to remove files when they are there (use '''porg -rb $JH_PKG_DIR''' before install, or even before cmake). - Another possibility is to use a DESTDIR install (hopefully, the DESTDIR is empty). There are several drawbacks with the first approach: some packages are needed for compiling/installing, so cannot be removed from the system, even just before installation (occurs only in LFS, I think. One such package is coreutils. Of course, also glibc, and a couple of others). Also, some packages change library versions at each update, so that removing the old library breaks all packages compiled against that library (example poppler). I'm sure the issue does not exist with autotools: existing files are overwritten. I do not know for meson. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1719#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1720: unset MAKELEVEL in scriptlets
#1720: unset MAKELEVEL in scriptlets +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Changes (by pierre): * owner: alfs-log@… => pierre * status: new => assigned -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1720#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1714: Add some pages from "After LFS Configuration Issues" to ablfs
#1714: Add some pages from "After LFS Configuration Issues" to ablfs -+- Reporter: pierre | Owner: alfs-log@… Type: enhancement | Status: closed Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: fixed Keywords: | -+- Changes (by pierre): * status: new => closed * resolution: => fixed Comment: Done at r4064 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1714#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1700: Remove && in BLFS scripts
#1700: Remove && in BLFS scripts
-+-
Reporter: pierre | Owner: alfs-log@…
Type: enhancement | Status: new
Priority: normal | Milestone: 3.0
Component: ablfs| Version: SVN
Severity: normal | Resolution:
Keywords: |
-+-
Comment (by pierre):
This should be easy enough. of course, only && at the end of lines should
be removed. But it is possible the a dev intends to have:
{{{
long instruction A &&
instruction B
}}}
to be equivalent to:
{{{
if long instruction A; then
instruction B
}}}
How to know? Ask dev to not use the && construct? When ''long instruction
A'' is of the form ''[ -letter something ]'', that may be detected, but
otherwise?
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1700#comment:2>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1713: Use sect1info tags to get tarball names and versions in LFS
#1713: Use sect1info tags to get tarball names and versions in LFS -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | -+--- Changes (by pierre): * owner: alfs-log@… => pierre * status: new => assigned -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1713#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[alfs-log] [ALFS Trac] #1720: unset MAKELEVEL in scriptlets
#1720: unset MAKELEVEL in scriptlets
+
Reporter: pierre | Owner: alfs-log@…
Type: defect | Status: new
Priority: normal | Milestone: 3.0
Component: jhalfs |Version: SVN
Severity: normal | Keywords:
+
jhalfs (and blfs extension) run scriptlets from a Makefile, so that
MAKELEVEL=1 when starting "make" in a build directory. This can lead to
weird errors, as explained in postgresql INSTALL file:
{{{
If you want to invoke the build from another makefile rather than
manually, you must unset MAKELEVEL or set it to zero, for instance
like this:
build-postgresql:
$(MAKE) -C postgresql MAKELEVEL=0 all
Failure to do that can lead to strange error messages, typically
about missing header files.
}}}
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1720>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1721: Some installation instructions are not generated correctly when using porg
#1721: Some installation instructions are not generated correctly when using porg +- Reporter: pierre | Owner: alfs-log@… Type: defect | Status: closed Priority: normal | Milestone: 3.0 Component: ablfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: new => closed * resolution: => fixed Comment: Fixed at r4093 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1721#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[alfs-log] [ALFS Trac] #1719: Some files may be not logged when using cmake+porg
#1719: Some files may be not logged when using cmake+porg + Reporter: pierre | Owner: alfs-log@… Type: defect | Status: new Priority: normal | Milestone: 3.0 Component: jhalfs |Version: SVN Severity: normal | Keywords: + When a file is already present on the system, cmake does not reinstall it. SO porg does not log it. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1719> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1720: unset MAKELEVEL in scriptlets
#1720: unset MAKELEVEL in scriptlets +- Reporter: pierre | Owner: alfs-log@… Type: defect | Status: new Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +- Comment (by pierre): I guess MAKELEVEL=1 is harmless in most cases, but for the few cases it is not (postgresql is one such case), we should unset MAKELEVEL (or set it to 0) in the generated scriptlets. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1720#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1721: Some installation instructions are not generated correctly when using porg
#1721: Some installation instructions are not generated correctly when using porg +- Reporter: pierre | Owner: alfs-log@… Type: defect | Status: new Priority: normal | Milestone: 3.0 Component: ablfs | Version: SVN Severity: normal | Resolution: Keywords: | +- Comment (by pierre): One first thing to do is to have more than two modes for outputting instructions (right now, with only have mode="root", and no mode). Also, checking that there is no role"root" before for outputting porg stanzas may be not enough, same for no role="root" after for closing... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1721#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1700: Remove && in BLFS scripts
#1700: Remove && in BLFS scripts -+- Reporter: pierre | Owner: pierre Type: enhancement | Status: closed Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: fixed Keywords: | -+- Changes (by pierre): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1700#comment:5> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1700: Remove && in BLFS scripts
#1700: Remove && in BLFS scripts -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+--- Comment (by pierre): Fixed at r4100 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1700#comment:4> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1713: Use sect1info tags to get tarball names and versions in LFS
#1713: Use sect1info tags to get tarball names and versions in LFS -+- Reporter: pierre | Owner: pierre Type: enhancement | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | -+- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r4090 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1713#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1713: Use sect1info tags to get tarball names and versions in LFS
#1713: Use sect1info tags to get tarball names and versions in LFS
-+---
Reporter: pierre | Owner: pierre
Type: enhancement | Status: assigned
Priority: normal | Milestone: 3.0
Component: jhalfs | Version: SVN
Severity: normal | Resolution:
Keywords: |
-+---
Comment (by pierre):
It is slightly more complicated... The url and package names are taken
from the adequate pages (chapter 3 for LFS, chapter 4 for HLFS, chapter
materials/${ARCH}-chapter for CLFS), and put in respective files urls.lst
and pkg_tarball_list.
On the other hand, scripts are generated with names taken from the
processing instructions. Then, when creating the
Makefile, the name of the tarball has to be guessed from the script name.
This is because unpacking and changing to the build directory is done in
the Makefile. Things could be much simpler if unpacking and changing to
the build directory were done in the scriptlet itself. Then the sect1info
tags could be used when generating the scriptlet, and no guess would be
needed...
But this entails some drastic change in Makefile generation. Note that
those changes have to be done only in master.sh and lfs.xsl, since CLFS is
not supposed to be touched by those changes, at least ATM.
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1713#comment:2>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1720: unset MAKELEVEL in scriptlets
#1720: unset MAKELEVEL in scriptlets +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r4088 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1720#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1698: Add measurements of sizes and timings in BLFS tools
#1698: Add measurements of sizes and timings in BLFS tools +- Reporter: pierre | Owner: pierre Type: task| Status: closed Priority: normal | Milestone: 3.0 Component: ablfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r4043. There is no way to detect doc only instructions. Test instructions have been improved. Lines have to be shuffled in script, if the order is not make; make test; make install (or same with ninja)... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1698#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1715: $LFS should be owned by root from the beginning
#1715: $LFS should be owned by root from the beginning -+- Reporter: pierre | Owner: pierre Type: enhancement | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | -+- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r4036 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1715#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1712: Possible conflict between script variables and package variables
#1712: Possible conflict between script variables and package variables +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r4031 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1712#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1695: Always generate test instructions, but comment them out according to the settings
#1695: Always generate test instructions, but comment them out according to the settings -+- Reporter: pierre | Owner: pierre Type: enhancement | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: minor| Resolution: fixed Keywords: | -+- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: CLFS fixed at r4021 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1695#comment:5> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1695: Always generate test instructions, but comment them out according to the settings
#1695: Always generate test instructions, but comment them out according to the settings -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: minor| Resolution: Keywords: | -+--- Comment (by pierre): LFS Fixed at r4020. Turning now to CLFS. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1695#comment:4> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1711: Warn about removing build_dir
#1711: Warn about removing build_dir -+- Reporter: pierre | Owner: pierre Type: enhancement | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | -+- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r4014. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1711#comment:4> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1711: Warn about removing build_dir
#1711: Warn about removing build_dir -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | -+--- Comment (by pierre): Better to test $JHALFSDIR/*gcc-pass1, which timestamps a successful install. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1711#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools -+- Reporter: pierre | Owner: pierre Type: enhancement | Status: closed Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: fixed Keywords: | -+- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Nobody commented (except Roger Koehler, who praised the addition). Closing -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703#comment:8> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+--- Comment (by pierre): A few fixes later... use r4000! -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703#comment:7> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+--- Comment (by pierre): I think I've come to something usable at revision r3997. Will leave open in case somebody wants to comment. Also, the documentation needs to be updated! -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703#comment:6> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools
-+---
Reporter: pierre | Owner: pierre
Type: enhancement | Status: assigned
Priority: normal | Milestone: 3.0
Component: ablfs| Version: SVN
Severity: normal | Resolution:
Keywords: |
-+---
Comment (by pierre):
The tracking directory may be populated from /jhalfs/logs...
Package.xml should have a "LFS packages", with a "Chapter
6", a "chapter 8" (containing only kernel), and possibly a
"chapter 9" (for {os,lfs,lsb}-release, but that would need
something special for version).
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703#comment:5>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+--- Comment (by pierre): Replying to [comment:1 pierre]: > This would involve: > - [...] > - excluding gcc and shadow (and maybe systemd for systemd users) since they are in the "Beyond" book. But we need to have the version built in LFS for those packages in the tracking dir, if they haven't been updated in BLFS yet... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703#comment:4> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+--- Comment (by pierre): Version of LFS (in /etc/os-release (for systemd), /etc/lfs-release, and /etc/lsb-release) needs to be updated too... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Timings and sizes are the same with anf without package management now. Fixed at r3976 in trunk and r3975 in 2.4 branch. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:13> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in
effect
+---
Reporter: pierre | Owner: pierre
Type: defect | Status: assigned
Priority: normal | Milestone: 3.0
Component: jhalfs | Version: SVN
Severity: normal | Resolution:
Keywords: |
+---
Comment (by pierre):
4 months later, had some time to think a little more:
- for SBUs: From '''man bash''' about the '' SECONDS'' variable:
{{{
Each time this parameter is referenced, the number of seconds
since shell invocation is returned. If a value is assigned to
SECONDS, the value returned upon subsequent references is the
number of seconds since the assignment plus the value assigned.
}}}
so it is possible to have something like:
{{{
PREV_SEC=$SECONDS
PackInstall
SECONDS=$PREV_SEC
}}}
and the packing time is not counted.
- for Sizes: just exclude '' /var/lib'' from '''du''' commands
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:12>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1708: Date reported for the SBU report file not the same as date in the filename of the report
#1708: Date reported for the SBU report file not the same as date in the filename of the report +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: 2.4.1 Component: jhalfs | Version: 2.4 Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: fixed at r3972 in trunk, and r3974 in 2.4 branch -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1708#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1709: quote bash variables when passing them to xsltproc
#1709: quote bash variables when passing them to xsltproc +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: 2.4.1 Component: jhalfs | Version: 2.4 Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: fixed in trunk at r3970, and in 2.4 branch at r3971 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1709#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1707: Do not use lfs.org as a domain name
#1707: Do not use lfs.org as a domain name +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: high| Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * version: 2.4 => SVN * resolution: => fixed * milestone: 2.4.1 => 3.0 Comment: Fixed at r3969 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1707#comment:6> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1706: Fix the blfs-bootscript download instructions
#1706: Fix the blfs-bootscript download instructions +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: high| Milestone: 2.4.1 Component: ablfs | Version: 2.4 Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r3967 in 2.4 branch, and r3968 in trunk -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1706#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1710: $JHALFSDIR maybe put twice in a path
#1710: $JHALFSDIR maybe put twice in a path +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: 2.4.1 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r 3962 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1710#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1710: $JHALFSDIR maybe put twice in a path
#1710: $JHALFSDIR maybe put twice in a path +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4.1 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): Ah, I see, it is only used when "Rebuild the Makefile" has been selected". I've not used it for a while... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1710#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1707: Do not use lfs.org as a domain name
#1707: Do not use lfs.org as a domain name +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: high| Milestone: 2.4.1 Component: jhalfs | Version: 2.4 Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): It's used in both. My concern is that the users may not be aware they would have to set that name, because it is hidden in a submenu. It is not fair to check and come back with a message "you forgot to set the domain name" or so, if the user has not even seen that the domain name needed to be edited. And silently ignoring the name if not set is maybe worse. I plan to add help about that (and the hostname), with references to the RFC's. But for me "local" seems to be a sane default. It may be a problem when the network uses active directory, but in this case, the user is in a corporation or institution, and should have received instructions about host- and domain- names. I'll make clear in the help that the names used should be as given by the person in charge of the network (note that if the user ''is'' the person in charge of the network, they should know what they are doing). -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1707#comment:5> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1707: Do not use lfs.org as a domain name
#1707: Do not use lfs.org as a domain name +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: high| Milestone: 2.4.1 Component: jhalfs | Version: 2.4 Severity: normal | Resolution: Keywords: | +--- Comment (by bdubbs@…): I'm not 100% sure of the use of this entry. If it to create resolve.conf, then then if the value it EDITME, then just omit the domain entry. If it is used to create the hosts file, then just omit the fqdn from the line with the static ip address if it is EDITME. Another option if the value is **EDITME** is to check it when doing the sanity check and tell the user to fix it. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1707#comment:4> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1707: Do not use lfs.org as a domain name
#1707: Do not use lfs.org as a domain name
+---
Reporter: pierre | Owner: pierre
Type: defect | Status: assigned
Priority: high| Milestone: 2.4.1
Component: jhalfs | Version: 2.4
Severity: normal | Resolution:
Keywords: |
+---
Comment (by pierre):
Using something illegal (!**EDITME for example) and testing it in jhalfs
is not fair to users, because it is in a submenu the user may just not
open and not see... In this [https://www.howtogeek.com/167190/how-and-why-
to-assign-the-.local-domain-to-your-raspberry-pi/ HowTo], you can find
some reasons to use "local". Roughly, if avahi is present on the machine
with a full name of the form ''hostname.local'', it can be found by name
on the local network, instead of by address. OTOH, that may be a bad
choice for some other configurations see [http://www.mdmarra.com/2012/11
/why-you-shouldnt-use-local-in-your.html this blog]. The use of "local" is
defined in [https://tools.ietf.org/html/rfc6762 RFC 6762]. Here is a
extract:
However, the majority of home computer users do not
have easy access to any portion of the global DNS namespace within
which they have the authority to create names. This leaves the
majority of home computers effectively anonymous for practical
purposes.
To remedy this problem, this document allows any computer user to
elect to give their computers link-local Multicast DNS host names of
the form: "single-dns-label.local.". For example, a laptop computer
may answer to the name "!MyComputer.local.". Any computer user is
granted the authority to name their computer this way, provided that
the chosen host name is not already in use on that link. Having
named their computer this way, the user has the authority to continue
utilizing that name until such time as a name conflict occurs on the
link that is not resolved in the user's favor. [...]
Now, as long as the local network is isolated from global internet, and
specially from outside DNS, you can use any domain name. This is the case
if using the network stack from qemu, as the other default addresses
suggest. So why bother?
Well, advising users to use registered domain names might not be a good
idea, if they happen to misconfigure their DNS... Names which are
guaranteed to work on local networks and to be harmless on global internet
are example{,.com,.net,.org}. See [https://tools.ietf.org/html/rfc6761 RFC
6761] But they normally are reserved for documentation.
Another possibility is to use .test names
([https://tools.ietf.org/html/rfc6761 RFC 6761]). They should not be
recognized as special by softwares, but are recognized as non existent by
caching DNS and root DNS.
All in all, I think "local" default is the most adapted for what we think
users will do. Otherwise, "lfs.test" might be not too bad. Comments?
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1707#comment:3>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1707: Do not use lfs.org as a domain name
#1707: Do not use lfs.org as a domain name +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: high| Milestone: 2.4.1 Component: jhalfs | Version: 2.4 Severity: normal | Resolution: Keywords: | +--- Description changed by pierre: Old description: > The default for the domain name in the host configuration is lfs.org. > SHould be changed, since lfs.org is a registerd domain, which has nothing > to do with Linux From scratch. New description: The default for the domain name in the host configuration is lfs.org. Should be changed, since lfs.org is a registered domain, which has nothing to do with Linux From scratch. -- -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1707#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1705: Patches and bootscripts (or units) are not copied to SRC_ARCHIVE
#1705: Patches and bootscripts (or units) are not copied to SRC_ARCHIVE +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: 3.0 Component: jhalfs | Version: 2.4 Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Should be fixed in both SVN and just created 2.4 branch (for bug fixes) at r3961 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1705#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1695: Always generate test instructions, but comment them out according to the settings
#1695: Always generate test instructions, but comment them out according to the settings -+- Reporter: pierre | Owner: alfs-log@… Type: enhancement | Status: new Priority: low | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: minor| Resolution: Keywords: | -+- Comment (by pierre): Maybe this can be coupled to #1694. In that case, we'll change milestone to 2.4. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1695#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[alfs-log] [ALFS Trac] #1701: No error message when packageManager.xml does not exist and package management is requested
#1701: No error message when packageManager.xml does not exist and package management is requested + Reporter: pierre | Owner: alfs-log@… Type: defect | Status: new Priority: high| Milestone: 2.4 Component: jhalfs |Version: SVN Severity: normal | Keywords: + The jhalfs script should test this and exit if not found... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1701> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1700: Remove && in BLFS scripts
#1700: Remove && in BLFS scripts -+- Reporter: pierre | Owner: alfs-log@… Type: enhancement | Status: new Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+- Changes (by pierre): * type: defect => enhancement * component: jhalfs => ablfs -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1700#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1698: Add measurements of sizes and timings in BLFS tools
#1698: Add measurements of sizes and timings in BLFS tools +- Reporter: pierre | Owner: alfs-log@… Type: task| Status: new Priority: normal | Milestone: 3.0 Component: ablfs | Version: SVN Severity: normal | Resolution: Keywords: | +- Changes (by pierre): * milestone: => 3.0 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1698#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1699: Instructions for generating network files do not work with systemd
#1699: Instructions for generating network files do not work with systemd --+- Reporter: pierre| Owner: alfs-log@… Type: defect| Status: closed Priority: normal| Milestone: Component: new_features | Version: SVN Severity: normal| Resolution: fixed Keywords:| --+- Changes (by pierre): * status: new => closed * resolution: => fixed Comment: Fixed at r3909, provided the LFS book is dated 20170310 or later -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1699#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1701: No error message when packageManager.xml does not exist and package management is requested
#1701: No error message when packageManager.xml does not exist and package management is requested +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: high| Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Changes (by pierre): * owner: alfs-log@… => pierre * status: new => assigned -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1701#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[alfs-log] [ALFS Trac] #1702: Packages which are not tarball or zip file cannot be build
#1702: Packages which are not tarball or zip file cannot be build + Reporter: pierre | Owner: alfs-log@… Type: defect | Status: new Priority: high| Milestone: 2.4 Component: jhalfs |Version: SVN Severity: major | Keywords: + Those packages are not extracted and are only present in the source directory. They are not found in the build directory. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1702> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools -+- Reporter: pierre | Owner: alfs-log@… Type: enhancement | Status: new Priority: normal | Milestone: 3.0 Component: ablfs| Version: SVN Severity: normal | Resolution: Keywords: | -+- Comment (by pierre): This would involve: - tracking the versions of LFS packages in the tracking file - including those packages in packages.xml (with dependency on the preceding one) - excluding gcc and shadow (and maybe systemd for systemd users) since they are in the "Beyond" book. - being very careful with glibc... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1695: Always generate test instructions, but comment them out according to the settings
#1695: Always generate test instructions, but comment them out according to the settings -+- Reporter: pierre | Owner: alfs-log@… Type: enhancement | Status: new Priority: low | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: minor| Resolution: Keywords: | -+- Changes (by pierre): * milestone: => 3.0 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1695#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [alfs-log] [ALFS Trac] #1702: Packages which are not tarball or zip file cannot be built (was: Packages which are not tarball or zip file cannot be build)
#1702: Packages which are not tarball or zip file cannot be built +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: high| Milestone: 2.4 Component: jhalfs | Version: SVN Severity: major | Resolution: Keywords: | +--- Changes (by pierre): * owner: alfs-log@… => pierre * status: new => assigned -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1702#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[alfs-log] [ALFS Trac] #1703: Allow to update LFS packages in BLFS tools
#1703: Allow to update LFS packages in BLFS tools -+ Reporter: pierre | Owner: alfs-log@… Type: enhancement | Status: new Priority: normal | Milestone: 3.0 Component: ablfs|Version: SVN Severity: normal | Keywords: -+ Presently, only BLFS packages are presented into the menu. Normally, all LFS packages have been built, so there is no reason to show them in the menu, except when there is a new version. In the latter case, it'd be nice to be able to select them. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1703> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[alfs-log] [ALFS Trac] #1700: Remove && in BLFS scripts
#1700: Remove && in BLFS scripts
+
Reporter: pierre | Owner: alfs-log@…
Type: defect | Status: new
Priority: normal | Milestone: 3.0
Component: jhalfs |Version: SVN
Severity: normal | Keywords:
+
If you have instructions of the form:
{{{
instruction A &&
instruction B &&
instruction C
}}}
and A fails, B and C are not executed (which is what is intended), but the
error code is 0 (because bash thinks it is equivalent to:
{{{
if instruction A; then
if instruction B; then
instruction C
fi
fi
}}}
which returns an error code only if C is executed and exits with an error.
This is not desirable in our case, because it defeats the use of ''set
-e''.
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1700>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [ALFS Trac] #1704: When using a tag in clfs, "git pull" returns an error
#1704: When using a tag in clfs, "git pull" returns an error +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: high| Milestone: 2.4 Component: jhalfs | Version: SVN Severity: major | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r3949 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1704#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[ALFS Trac] #1704: When using a tag in clfs, "git pull" returns an error
#1704: When using a tag in clfs, "git pull" returns an error + Reporter: pierre | Owner: pierre Type: defect | Status: new Priority: high| Milestone: 2.4 Component: jhalfs |Version: SVN Severity: major | Keywords: + If a tag has been used in clfs, and you come back without "rebuild files", an update of the book source is attempted with "git pull". But since the directory is in "detached head state", the pull fails... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1704> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1704: When using a tag in clfs, "git pull" returns an error
#1704: When using a tag in clfs, "git pull" returns an error +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: high| Milestone: 2.4 Component: jhalfs | Version: SVN Severity: major | Resolution: Keywords: | +--- Changes (by pierre): * status: new => assigned -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1704#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1702: Packages which are not tarball or zip file cannot be built
#1702: Packages which are not tarball or zip file cannot be built +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: high| Milestone: 2.4 Component: ablfs | Version: SVN Severity: major | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: fixed at r3927 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1702#comment:4> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1702: Packages which are not tarball or zip file cannot be built
#1702: Packages which are not tarball or zip file cannot be built
+---
Reporter: pierre | Owner: pierre
Type: defect | Status: assigned
Priority: high| Milestone: 2.4
Component: ablfs | Version: SVN
Severity: major | Resolution:
Keywords: |
+---
Comment (by pierre):
Actually, ATM, the only case is CA certificates. But there used to be
others...
First, there is a real bug:
{{{
UNPACKDIR=$PKG_DIR-build
mkdir $UNPACKDIR
cp $PACKAGE $UNPACKDIR
}}}
should be:
{{{
UNPACKDIR=$PKG_DIR-build
mkdir $UNPACKDIR
cp $SRC_DIR/$PACKAGE $UNPACKDIR
}}}
Second, certdata.txt is in BUILD_DIR (as a symlink), not in UNPACKDIR, but
the book instructions suppose it ''is'' in UNPACKDIR... What could be done
is just copy all the symlinks (right now, only one, but possibly more when
another similar package is added) from BUILD_DIR to UNPACKDIR...
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1702#comment:3>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [ALFS Trac] #1702: Packages which are not tarball or zip file cannot be built
#1702: Packages which are not tarball or zip file cannot be built +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: high| Milestone: 2.4 Component: ablfs | Version: SVN Severity: major | Resolution: Keywords: | +--- Changes (by pierre): * component: jhalfs => ablfs -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1702#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1701: No error message when packageManager.xml does not exist and package management is requested
#1701: No error message when packageManager.xml does not exist and package management is requested +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: high| Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Fixed at r3926 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1701#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1701: No error message when packageManager.xml does not exist and package management is requested
#1701: No error message when packageManager.xml does not exist and package
management is requested
+---
Reporter: pierre | Owner: pierre
Type: defect | Status: assigned
Priority: high| Milestone: 2.4
Component: jhalfs | Version: SVN
Severity: normal | Resolution:
Keywords: |
+---
Comment (by pierre):
The reason why it is not flagged when trying to copy package Manager;xml
and packInstall.sh to $JHALFSDIR is that it is in a '&&' sequence:
{{{
[[ "$PKGMNGT" = "y" ]] && [[ "$PROGNAME" = "lfs" ]] &&
cp $PKGMNGTDIR/packageManager.xml $JHALFSDIR/ &&
cp $PKGMNGTDIR/packInstall.sh $JHALFSDIR/
}}}
If $PKGMNGTDIR/packageManager.xml does not exist, the non zero exit code
just stops the sequence but does not raise an error...
So replacing with if..then will flag the error. But it'd be better to have
it detected earlier when checking the configuration.
--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1701#comment:2>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): Workaround committed in r3924 r3925: Make SBU and size computations incompatible with package management in Config.in... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:11> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 3.0 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Changes (by pierre): * milestone: 2.4 => 3.0 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:10> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): OK, I cannot think of a "minimal" way of doing this. I'll move the milestone to 3.0, and document that figures are wrong when using package management. Hmm, maybe a more radical way: make package management incompatible with SBU report in Config.in! -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:9> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): Replying to [comment:7 pierre]: > Problem is with packages, which do things ''after'' install: tests for systemd and dejagnu, and locales in glibc (actually, I'm not sure how those should be counted, since the user may choose to not install them or to install all, or to install one more for her(his) own locale). Anyway, those things occur after the binary package has been saved to its repo, so all size calculation will include the size of the binary package, unless we exclude /var/lib/packages from the '''du''' command. But wait, what about the timings? > > Wouldn't it be possible to packInstall after the "adjust"/"test" phase? I'd say it's the way to go. > No, it is just stupid: those phases need an installed package... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:8> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): Problem is with packages, which do things ''after'' install: tests for systemd and dejagnu, and locales in glibc (actually, I'm not sure how those should be counted, since the user may choose to not install them or to install all, or to install one more for her(his) own locale). Anyway, those things occur after the binary package has been saved to its repo, so all size calculation will include the size of the binary package, unless we exclude /var/lib/packages from the '''du''' command. But wait, what about the timings? Wouldn't it be possible to packInstall after the "adjust"/"test" phase? I'd say it's the way to go. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:7> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): But now, we would change "create-sbu_du-report.sh to account for those 3 values. This means it will not work anymore for CLFS... Or we have to change CLFS too. Well it's just a few lines more in clfs.xsl. It is maybe a big change for a "rc" time, but let's try... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:6> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): A possible plan: - Remove the second "KB: ..." generation from Makefile. - generate 2 "KB: ..." during the script, one before install, and one after. We would have 3 "KB: ..." values (KB1, KB2, KB3) and we can compute: - Required size = KB3 -KB1 - Installed size = KB3 -KB2 Let's try that... -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:5> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): For SBU, It is easy to output the "Totalseconds: ..." before packing and after install. For sizes, it is more complicated: right now, the Makefile outputs "KB: ..." before unpacking the tarball, and another "KB: ..." after the script exits. The computation is done in the following way: Required space : KB after - KB before Installed size : KB before next script - KB before this script. We can of course keep the same protocol for "KB before", and get a value of "KB after" by outputting after install and before packing. Problem is the installed size. The next "KB before" will include both installed size and the size of the package binary (.deb or .tar.gz). We can get the installed size from "du -sk $PKG_DEST", but then we would have to change the create-SBU_du-report.sh script, depending on whether we use package management or not... Furthermore, when we later want to include porg style, it'll break again. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:4> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: 2.4 Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Changes (by pierre): * milestone: => 2.4 Comment: Let's try to do that for 2.4, but if the changes are to painful, we'll revert to 3.0. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1697: Systemd units are not installed by the blfs tools
#1697: Systemd units are not installed by the blfs tools +- Reporter: pierre | Owner: pierre Type: defect | Status: closed Priority: normal | Milestone: Component: ablfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | +- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: Hopefully fixed at r3894 (r3895 in branch new_features) -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1697#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Measured times and sizes include packaging, when package management is in effect (was: Measured times include packaging, when package management is in effect)
#1694: Measured times and sizes include packaging, when package management is in effect +--- Reporter: pierre | Owner: pierre Type: defect | Status: assigned Priority: normal | Milestone: Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | +--- Comment (by pierre): This is not a small change, because right now, the total size of the system is measured before launching the scriptlet, and after it has exited. For times, it is slightly easier, because the command to report the time is included in the scriptlet. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1693: Fortify unpacking in the scripts generated for BLFS
#1693: Fortify unpacking in the scripts generated for BLFS -+- Reporter: pierre | Owner: pierre Type: enhancement | Status: closed Priority: normal | Milestone: Component: jhalfs | Version: SVN Severity: normal | Resolution: fixed Keywords: | -+- Changes (by pierre): * status: assigned => closed * resolution: => fixed Comment: fixed at r3837 -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1693#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1693: Fortify unpacking in the scripts generated for BLFS
#1693: Fortify unpacking in the scripts generated for BLFS -+--- Reporter: pierre | Owner: pierre Type: enhancement | Status: assigned Priority: normal | Milestone: Component: jhalfs | Version: SVN Severity: normal | Resolution: Keywords: | -+--- Changes (by pierre): * status: new => assigned -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1693#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
[ALFS Trac] #1693: Fortify unpacking in the scripts generated for BLFS
#1693: Fortify unpacking in the scripts generated for BLFS -+ Reporter: pierre | Owner: pierre Type: enhancement | Status: new Priority: normal | Milestone: Component: jhalfs |Version: SVN Severity: normal | Keywords: -+ Presently, the scripts account only for two cases for the downloaded tarball: - a zip archive - a tar archive (compressed or not) Now that cacerts has been included in the possible scripts, the downloaded file may also be a text file. It would therefore be nice to account for this case. Also, the scripts always suppose that the zip archive is not extracted in its own directory, so that it creates one. That does not work for example for jasper. So it would be good also to test whether unpacking has created a directory or not. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1693> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Your Key To Success: Make Money Taking Surveys
#1694: Your Key To Success: Make Money Taking Surveys -+- Reporter: FloraMarrero | Owner: thomasp@… Type: enhancement | Status: new Priority: normal | Milestone: jhalfs-1.0 Component: ablfs| Version: 6.1 Severity: minor| Resolution: Keywords: free surveys for money paid survey | sites opinion surveys | -+- Changes (by thomasp@…): * owner: alfs-log@… => thomasp@… -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:1> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1694: Closed for Spam (was: Your Key To Success: Make Money Taking Surveys)
#1694: Closed for Spam -+- Reporter: Anonymous| Owner: thomasp@… Type: enhancement | Status: closed Priority: normal | Milestone: jhalfs-1.0 Component: ablfs| Version: 6.1 Severity: minor| Resolution: fixed Keywords: | -+- Changes (by thomasp@…): * status: new => closed * reporter: FloraMarrero => Anonymous * keywords: free surveys for money paid survey sites opinion surveys => * resolution: => fixed Old description: > Survey Sites That Pay - Before You Obtain Started SEVERAL Factors You > Should Know > > I'm likely to speak questionnaire websites that spend. There are MANY > study sites which can be out there and you also truly must see the fine > print and be mindful everything you sign up for. Nevertheless, > undertaking surveys might not be fun and, in lots of situations, > unrewarding , as in INCOME! I enjoy performing surveys, but there exists > a several items I want to clear up about surveys websites that spend. > ONE. You'll not qualify for all the surveys! Don't think that as you have > registered and they've acknowledged your program that addressing issues > will be simply started by you and get your cash. They're searching for > certain categories of class or individuals to perform each one of these > and never everybody matches each and every time to the invoice. > Consequently don't rely on it. > 2. Survey sites that pay rely on one to not be dishonest. The firms that > spend the review organizations depend on , sincere that is exact info to > produce product decisions that are significant. The survey firms take > this quite really so, if you're considering simply placing along any > previous replies just to get the reimbursement, do not bother signing up. > 3. Invest some time before anyone reply and read each concern totally. > Trust in me once I say that survey sites that pay their questionnaires to > be completed by one observe closely time IT WILL consider you to remedy a > question and the timeframe you ACTUALLY take to answer the question. > Trust me, in the event you hurry through your research so you will obtain > your reimbursement to make it to the finish, you'll be kicked the cell > off and any future partnership using corporation will soon not be > seriously undamaged. > FOUR. The larger paying studies demand more function and > [http://Browse.deviantart.com/?q=commitment commitment]. You get that > which you purchase and these firms learn this. For example, having one > particular business with which I have a connection there's a fairly big > reimbursement for joining a "market-research program". as follows the > arrangement is: > "The client is interested in actions and your web experiences. The > pursuits will be used to provide marketing companies that are major with > responses. To become listed on this system you should download and put in > a meter on your computer. Enrollment involves filling a number of details > out and only requires FOUR minutes. You'll not need to accomplish > anything to observe it after adding the meter. Your things will be > received by you, as long as anyone stay not inactive regarding at-least > 35 days. Take into account, address and an exact identify must certanly > be offered within your member report for one to get these rewards. We > should reassure you the meter effect or will not interfere the managing > of the pc." > Some people are not with allowing this, comfortable so the settlement is > a lot more than that of most of one other common research, and also this > is known by the business. Therefore preserve that in your mind. > Furthermore, some incorporate online product screening that needs a > credit-card to "try the merchandise ". Currently, the majority of the > period that you don't have [http://www.getsurveysforcash.com paid to take > surveys] purchase something, however, you have to observe the information > and CANCEL your contract together with the product tester before your > test time expires should you choose not want the item. Maintain records > that are great! > Supplying your view can be an entertaining strategy to invest spare time, > make your style observed and make several more money. You will find > review websites that pay! Check the page below to find out the web sites > I take advantage of and recommend.Click here to determine my favorite > study websites that pay! Each of these are used by myself almost daily > and I GET attained funds with each one of these. Take a look. They cost > nothing to enroll. New description: -- -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1694#comment:2> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
Re: [ALFS Trac] #1690: error root required when logged in as root
#1690: error root required when logged in as root --+- Reporter: krichter | Owner: alfs-log@… Type: defect| Status: closed Priority: normal| Milestone: Component: jhalfs| Version: SVN Severity: normal| Resolution: invalid Keywords: root | --+- Changes (by pierre): * status: new => closed * resolution: => invalid Comment: Sorry for the late reply. This error is raised if the user ID is 0. It has nothing to do with directory ownership. Closing as invalid. -- Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1690#comment:3> ALFS Trac <http://wiki.linuxfromscratch.org/alfs/> Automated Linux From Scratch -- http://lists.linuxfromscratch.org/listinfo/alfs-log Unsubscribe: See the above information page
