Errors: parsing parser_rfc822 eol and /usr/bin/env

[k4lk1]

I'm trying to build Kali with I3WM for amd64 on a Kali live amd64 and i get this after lb build:

[2013-04-14 05:51:33] lb build 
P: Executing auto/build script.
[2013-04-14 05:51:33] lb build noauto
[2013-04-14 05:51:33] lb bootstrap 
P: Setting up cleanup function
[2013-04-14 05:51:33] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2013-04-14 05:51:33] lb bootstrap_cdebootstrap 
P: Begin bootstrapping system...
[2013-04-14 05:51:33] lb testroot 
P: If the following stage fails, the most likely cause of the problem is with your mirror configuration or a caching proxy.
P: Running cdebootstrap (download-only)... 
P: Retrieving InRelease
P: Validating InRelease
I: Good signature from "Kali Linux Repository <[email protected]>"
P: Parsing InRelease
W: parser_rfc822: Iek! Don't find end of field, it seems to be after the end of the line!
E: Couldn't parse InRelease!
P: Begin unmounting filesystems...
P: Saving caches...
chroot: failed to run command `/usr/bin/env': No such file or directory
STOP

[Wyti]

Got the same error, even with the default configuration (tried with an up to date kali system as of today and the live-script-config given in the kali git).

The strange part is that before the 4th april everything worked fine (got to build a KDE system, changed some package, even toying with hooks for personnalized lauch menu) but after this fated day, live-build just seems broken.

When I reported it in the bug tracker 11 days ago, the ticket got closed because it's working on their side, so what are we missing ?

What I tried that didn't work : A shittons load of configuration option, I though I broke it on my side after too much experiment. <-- not the config since the default works
using the live cd of kali 1.0.2 with updated tools : "apt-get update && apt-get install git live-build cdebootstrap kali-archive-keyring" and then
"git clone git://git.kali.org/live-build-config.git
cd live-build-config
lb config
lb build"

don't have any ideas anymore.

[maverik35]

Somehow the InRelease file is not a complient file with rfc822 standard. So it will not recognize or parse the file, then it stops..It can be headers or Key..I read something about it in a Debian thread.

We would have to see if for some architectures the InRealese is a valid one...

I'll be reporting a bug as to non-pae 386 builds..The InRelease as seen in your post was downloaded, validated and has the good signature from kali.

When installer tries to parse the file, it does not recognize the standar file, something is wrong there...

Luck.

[k4lk1]

What I tried that didn't work : A shittons load of configuration option, I though I broke it on my side after too much experiment. <-- not the config since the default works
using the live cd of kali 1.0.2 with updated tools : "apt-get update && apt-get install git live-build cdebootstrap kali-archive-keyring" and then
"git clone git://git.kali.org/live-build-config.git
cd live-build-config
lb config
lb build"

I did so:
apt-get update
apt-get install git live-build cdebootstrap kali-archive-keyring
git clone git://git.kali.org/live-build-config.git
cd live-build-config
lb config
ins the gui and removed some packets
lb config --architecture amd64
lb build

When installer tries to parse the file, it does not recognize the standar file, something is wrong there...
Luck.

So i tryed to launch lb build without any changes and the error parser_rfc822 disappear. Then made a sym link in chroot dir of /usr/bin/env but the error is still here.

This is the chroot file:

# config/chroot - options for live-build(7), chroot stage

# $LB_CHROOT_FILESYSTEM: set chroot filesystem
# (Default: squashfs)
LB_CHROOT_FILESYSTEM="squashfs"

# $LB_UNION_FILESYSTEM: set union filesystem
# (Default: aufs)
LB_UNION_FILESYSTEM="aufs"

# $LB_EXPOSED_ROOT: expose root as read only
# (Default: false)
LB_EXPOSED_ROOT="false"

# $LB_HOOKS: set hook commands
# (Default: empty)
LB_HOOKS=""

# $LB_INTERACTIVE: set interactive build
# (Default: false)
LB_INTERACTIVE="false"

# $LB_KEYRING_PACKAGES: set keyring packages
# (Default: empty)
LB_KEYRING_PACKAGES="kali-archive-keyring"

# $LB_LINUX_FLAVOURS: set kernel flavour to use
# (Default: autodetected)
LB_LINUX_FLAVOURS="amd64"

# $LB_LINUX_PACKAGES: set kernel packages to use
# (Default: autodetected)
LB_LINUX_PACKAGES="linux-image"

# $LB_SECURITY: enable security updates
# (Default: true)
LB_SECURITY="true"

# $LB_UPDATES: enable updates updates
# (Default: false)
LB_UPDATES="false"

# $LB_BACKPORTS: enable backports updates
# (Default: false)
LB_BACKPORTS="false"

[charonsecurity]

Just a dumb question, I'm sure you already did, but did you update the sources.list file before doing the apt-get update?

[k4lk1]

Just a dumb question, I'm sure you already did, but did you update the sources.list file before doing the apt-get update?

here the sourcelist:

deb cdrom:[Debian GNU/Linux 7.0 _Kali_ - Official Snapshot amd64 LIVE/INSTALL Binary 20130327-17:54]/ kali contrib main non-free 

# deb cdrom:[Debian GNU/Linux 7.0 _Kali_ - Official Snapshot amd64 LIVE/INSTALL Binary 20130327-17:54]/ kali contrib main non-free 

deb http://http.kali.org/kali/ kali main non-free contrib 
# deb-src http://http.kali.org/kali/ kali main non-free contrib 

## Security updates
deb http://security.kali.org/kali-security/ kali/updates main contrib non-free

[Wyti]

Someone found the solution : http://bugs.kali.org/view.php?id=270

Issue Solved !!!
This is a bug in package libdebian-installer4 .

Fixing it

apt-get remove --purge libdebian-installer4
wget http://ftp.debian.org/debian/pool/ma...er_0.85.tar.gz [^]
tar xvf libdebian-installer_0.85.tar.gz
cd libdebian-installer/
grep -R parser_rfc822 src
apt-get install automake libtool
autoreconf -i -v
./configure
make
make install
git clone git://git.kali.org/live-build-config.git [^]
cd live-build-config/
lb config
lb build

apparently it's libdebian-installer that dropped support of pgp file in version >= 0.85
installing the version 0.85 works for me.

[dache-mr79]

hello brother has done everything right and the 1 error output
but then I get this message



The following NEW packages will be installed:
dctrl-tools
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 167 kB of archives.
After this operation, 571 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
dctrl-tools
E: There are problems and -y was used without --force-yes
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree..


anyone knows any solution thanks

[sakure]

I ran into same error while doing a standard live-build as recommonded in this bug
http://bugs.kali.org/view.php?id=76

try
lb config --apt-options "--force yes --yes"
lb build

I was able to get past the error, so far so good. still building...

have never built a debian image with live-build. learning as I go along,
check out the manual for live-build
http://live.debian.net/manual/4.x/ht...lation.en.html

there is a debug option too.

lb build --debug

happy building!!

[thinker]

I ran into same error while doing a standard live-build as recommonded in this bug
http://bugs.kali.org/view.php?id=76

try
lb config --apt-options "--force yes --yes"
lb build

I had to remove the live-build-config directory and reinstall it. It seems that not finding the E17 (enlightenment) package screwed something up, and left dctrl-tools "unfindable" even after manually installing dctrl-tools and deselecting E17 for installation. So I reinstalled live-build-config, and this time with E17 (enlightenment) unselected for installation, the build process is succeeding. Just wanted to post this quick solution for others.