View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000252Kali LinuxKali Package Bugpublic2013-04-10 16:212013-04-15 18:17
ReporterWyti Assigned Tomuts  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platformamd64OSKali linuxOS Version1.0.2
Summary0000252: live-build can't parse InRelease
Description

I had an already working live-build configuration (the image generated worked for me) I've done some changes but couldn't build it again.
I always end up with the error :

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!

I then tried with the default configuration (only using the command lb config followed by lb build) with the latest git version of your live-build-config and still got the same error.

Steps To Reproduce

Download the live-build-config from git : git clone git://git.kali.org/live-build-config
cd live-build-config
lb config
lb build

Additional Information

Included the binary.log file if that helps.

Attached Files
binary.log (861 bytes)    
[2013-04-10 18:09:15] lb build noauto
[2013-04-10 18:09:17] lb bootstrap 
P: Setting up cleanup function
[2013-04-10 18:09:18] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2013-04-10 18:09:20] lb bootstrap_cdebootstrap 
P: Begin bootstrapping system...
[2013-04-10 18:09:21] 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
binary.log (861 bytes)   

Activities

saberzaid

saberzaid

2013-04-10 18:14

reporter   ~0000358

im facing the same problem here :)
muts

muts

2013-04-15 08:06

reporter   ~0000374

Works great for me. Since not additional info was given, we're closing the ticket.

You might just need to :
lb clean --purge
before your next build.

Issue History

Date Modified Username Field Change
2013-04-10 16:21 Wyti New Issue
2013-04-10 16:21 Wyti File Added: binary.log
2013-04-10 18:14 saberzaid Note Added: 0000358
2013-04-15 08:06 muts Note Added: 0000374
2013-04-15 08:06 muts Status new => closed
2013-04-15 08:06 muts Assigned To => muts
2013-04-15 08:06 muts Resolution open => no change required