Your message dated Sun, 1 Jan 2017 15:51:45 +0100
with message-id <[email protected]>
and subject line Re: Bug#849827: Fwd: Re: Bug#849827: live-build fails to build
amd64 target
has caused the Debian Bug report #849827,
regarding live-build fails to build amd64 target
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
849827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849827
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: live-build
Version: 1:20161216
I configure with:
lb config --debian-installer live -d stretch --archive-areas main
contrib non-free upstream restricted --linux-packages `dpkg-query -f
'${binary:Package}\n' -W`
This configures the target for the same packages as those installed on
the build host. It seems to correctly configure:
P: Creating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
Now whenever a build (lb build) is attempted it fails in the same way.
The build chugs along retrieving/verifying/unpacking packages. So far so
good.
But the build eventually fails with:
Reading package lists... Done
Building dependency tree
Reading state information... Done
[2016-12-31 14:30:15] lb chroot_install-packages install
P: Begin installing packages (install pass)...
Reading package lists... Done
Building dependency tree
Reading state information... Done
*E: Unable to locate package a2ps-amd64*
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note *E: Unable to locate package a2ps-amd64
*a2ps happens to be the first package in my package list. It doesn't
matter which package is first - the build appends the suffix "-amd64" to
create an illegal package name (no such package exists). As there are no
options for either "lb config" or "lb build" which affect this behavior
I'm concluding this is a bug. I've scoured all the documentation such as
https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html
and spent hours googling for answers or workarounds without success.
Please advise.
Build host:
uname -a
Linux nehalem 4.1.17 #2 SMP Sun Feb 14 22:42:14 CST 2016 x86_64 GNU/Linux
--- End Message ---
--- Begin Message ---
On Sat, 31 Dec 2016, Ben Armstrong wrote:
> User error. This bug should be closed.
Ack, doing it now, feel free to do it yourself in the future.
Cheers,
> --- Forwarded message ---
> From: Ben Armstrong <[email protected]>
> Date: December 31, 2016 5:45:12 PM
> Subject: Re: Bug#849827: live-build fails to build amd64 target
> To: Peter.Stein <[email protected]>, [email protected]
>
> You are misusing the --linux-packages option which is only to specify kernel
> and kernel modules. See live-manual and use package lists instead.
>
> Ben
>
> On December 31, 2016 4:45:26 PM "Peter.Stein" <[email protected]> wrote:
>
> > Package: live-build
> > Version: 1:20161216
> >
> > I configure with:
> >
> > lb config --debian-installer live -d stretch --archive-areas main
> > contrib non-free upstream restricted --linux-packages `dpkg-query -f
> > '${binary:Package}\n' -W`
> >
> > This configures the target for the same packages as those installed on
> > the build host. It seems to correctly configure:
> >
> > P: Creating config tree for a debian/stretch/amd64 system
> > P: Symlinking hooks...
> >
> > Now whenever a build (lb build) is attempted it fails in the same way.
> > The build chugs along retrieving/verifying/unpacking packages. So far so
> > good.
> > But the build eventually fails with:
> >
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > [2016-12-31 14:30:15] lb chroot_install-packages install
> > P: Begin installing packages (install pass)...
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > *E: Unable to locate package a2ps-amd64*
> > P: Begin unmounting filesystems...
> > P: Saving caches...
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> >
> > Note *E: Unable to locate package a2ps-amd64
> >
> > *a2ps happens to be the first package in my package list. It doesn't
> > matter which package is first - the build appends the suffix "-amd64" to
> > create an illegal package name (no such package exists). As there are no
> > options for either "lb config" or "lb build" which affect this behavior
> > I'm concluding this is a bug. I've scoured all the documentation such as
> > https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html
> > and spent hours googling for answers or workarounds without success.
> > Please advise.
> >
> > Build host:
> > uname -a
> > Linux nehalem 4.1.17 #2 SMP Sun Feb 14 22:42:14 CST 2016 x86_64 GNU/Linux
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--- End Message ---
