Brendan Perrine's syslog contains interesting clues.

https://bugs.launchpad.net/ubuntu/+source/lubuntu-
meta/+bug/1417784/comments/13

“Feb  4 01:22:26 debconf-copydb: Cannot open file 
/target/var/cache/debconf/config.dat-new: No such file or directory
Feb  4 01:22:26 debconf-copydb: Cannot open file 
/target/var/cache/debconf/templates.dat-new: No such file or directory
Feb  4 01:22:26 base-installer: chroot: can't execute 'debconf-set-selections': 
No such file or directory
Feb  4 01:22:26 base-installer: warning: 
/usr/lib/base-installer.d/20console-setup returned error code 127”

“Feb  4 01:23:04 debootstrap: Preparing to unpack 
.../login_1%3a4.1.5.1-1ubuntu9_amd64.deb ...
Feb  4 01:23:04 debootstrap: dpkg: error: --compare-versions takes three 
arguments: <version> <relation> <version>”

and this one I have seen in my remixes, it should be possible to fix:
“Feb  4 01:25:48 in-target: W: GPG error: http://extras.ubuntu.com trusty 
Release: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 16126D3A3E5C1192”

That's for a search on the chain "error". When it comes to "warning"
there are a bunch. The very first one looks related to the hardware only
though:

“Feb  4 01:19:01 kernel: [    0.000000] WARNING: CPU: 0 PID: 0 at 
/build/buildd/linux-lts-utopic-3.16.0/drivers/iommu/dmar.c:760 
warn_invalid_dmar+0x81/0x93()
Feb  4 01:19:01 kernel: [    0.000000] Your BIOS is broken; DMAR reported at 
address 0!
Feb  4 01:19:01 kernel: [    0.000000] BIOS vendor: Hewlett-Packard; Ver: F.33; 
Product Version: Rev 1”

Then, the warnings are about files missing:

“Feb  4 01:19:14 cdrom-retriever: warning: File 
/cdrom/dists/trusty/main/debian-installer/binary-amd64/Packages does not exist.
Feb  4 01:19:14 cdrom-retriever: warning: File 
/cdrom/dists/trusty/restricted/debian-installer/binary-amd64/Packages does not 
exist.
Feb  4 01:19:14 cdrom-retriever: warning: File 
/cdrom/dists/trusty/universe/debian-installer/binary-amd64/Packages does not 
exist.
Feb  4 01:19:14 cdrom-retriever: warning: Unable to find 
multiverse/debian-installer/binary-amd64/Packages in 
/cdrom/dists/trusty/Release.
Feb  4 01:19:14 cdrom-retriever: warning: Unable to find 
multiverse/debian-installer/binary-amd64/Packages.gz in 
/cdrom/dists/trusty/Release.”

later, about nefcfg looking for a wpa-supplicant pid file:
“Feb  4 01:19:44 netcfg[14971]: INFO: Starting netcfg v.1.116ubuntu2 (built 
20140923-2000)
Feb  4 01:19:44 netcfg[14971]: WARNING **: Couldn't read Wpasupplicant pid 
file, not trying to kill.”

and some more warnings to be examined. Once these errors and warnings
will have been reduced to their very minimum and hopefully harmless
warnings, we will be very near to the release.

I have an idea about just a few specific packages which are missing and
could help improve the general behavior. I'll try tomorrow and report
back if I see a difference.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417784

Title:
  several packages missing or added in Lubuntu 14.04.2 manifests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1417784/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to