[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#694886: dpkg: Complain about missing descriptions for packages in /var/lib/dpkg/available



Control: reassign -1 debootstrap
Control: retitle -1 debootstrap: Creates available file w/o Description fields

On Sat, 2012-12-01 at 21:21:33 +0100, Petter Reinholdtsen wrote:
> [Guillem Jover]
> > Was it obvious from the log when did it start to warn?
> 
> Yes.  It happened while deboostrap was running.  Just after e2fsprogs
> was configured and before adduser was unpacked:

> Dec  1 17:16:00 debootstrap: Setting up sysvinit (2.88dsf-34) ...
> Dec  1 17:16:00 debootstrap: sysvinit: creating /run/initctl
> Dec  1 17:16:00 debootstrap: Not restarting sysvinit: init not running
> Dec  1 17:16:00 debootstrap: Setting up e2fsprogs (1.42.5-1) ...
> Dec  1 17:16:00 debootstrap: dpkg: warning: parsing file '/var/lib/dpkg/available' near line 35 package 'libc-bin':
> Dec  1 17:16:00 debootstrap:  missing description
> [...]
> Dec  1 17:16:01 debootstrap:  missing description
> Dec  1 17:16:01 debootstrap: dpkg: warning: parsing file '/var/lib/dpkg/available' near line 3870 package 'whiptail':
> Dec  1 17:16:01 debootstrap:  missing description
> Dec  1 17:16:01 debootstrap: (Reading database ... 
> Dec  1 17:16:01 debootstrap: 6256 files and directories currently installed.)
> Dec  1 17:16:01 debootstrap: Unpacking adduser (from .../adduser_3.113+nmu3_all.deb) ...
> Dec  1 17:16:01 debootstrap: Unpacking libstdc++6:i386 (from .../libstdc++6_4.7.2-4_i386.deb) ...
> Dec  1 17:16:01 debootstrap: Unpacking libapt-pkg4.12:i386 (from .../libapt-pkg4.12_0.9.7.6_i386.deb) ...
> Dec  1 17:16:02 debootstrap: Unpacking gpgv (from .../gpgv_1.4.12-6_i386.deb) ...

> > Maybe the file was not right from the start; I'm not sure if d-i
> > populates it.
> 
> No idea. :)

Ok, having checked debootstrap code now, it would seem like
functions:setup_available() is the culprit. And the setup_available()
call in sid:second_stage_install() would seem to match what's
happening on the log.

Thanks,
Guillem


Reply to: