Bug#849827: live-build fails to build amd64 target

2017-01-01 Thread Michael . 
And here goes the live-build community once more into a meltdown.

Peter, I haven't seen your name in many, if any, discussions before this so
take this from someone who has been a part of the user community for many
many years.
Your attitude and method of communication alienates yourself from people
wanting to take their time to help you. Live-build has, while I have been a
user, always been a volunteer community.
As users we file bug reports and make comments without fear or favour. Yes
there has been a few times where the response has seemed quite short but
this is the internet and reading tone into replies is a dangerous thing. It
is the words used that matter and injecting tone is something the reader
does not the writer. The words you have used are pre-empting a stern reply
by suggesting you will get a brush off rather than any help, what a great
way to make friends and influence people.

In other words please don't come here telling this community we are doing
it all wrong if you are not in any way shape or form willing to offer
assistance.
Just my $0.02 in reply to yours.

On 2 January 2017 at 09:09, Ben Armstrong 
wrote:

> On January 1, 2017 4:47:39 PM "Peter.Stein" 
> wrote:
>
> > I actually had a bunch of comments, but suspected they would not be well
> > received
>
> Try us.
>
> >
>
> and thus tried to be diplomatic
>
> I must have missed that. ;)
>
> >
>
> and productive by suggesting a
> > step-by-step HOWTO. It's needed, everyone knows what one is, and
> > shouldn't be difficult to put together by the live-build experts. You
> > wanted an improvement suggestion and I gave you a very "actionable" one.
>
> I know how many hundreds of hours of my personal time went into the
> original document before I called it quits and doubt your assessment of the
> ease of replacing the current doc. Since it's "incomprehensible", it seems
> it all needs to be replaced from scratch ... or was that hyperbole, perhaps?
>
>
> > I'm always reluctant to get into these "improvement" discussions because
> > the fact of the matter is you open source folks don't take constructive
> > criticism very well and invariably end up copping an attitude - like you
> > are now. I've developed software professionally for 35 years and can
> > state unequivocally that this documentation does not meet the
> > "production grade" standard.
>
> I am not "you open source folks". I'm a person with feelings, not a bundle
> of stereotypes. I'm particularly not impressed by you "pulling rank" by
> trotting out your "senior developer" status when I haven't seen a single
> line of code or sentence of doc contributed by you to this project. Show me
> the code (or doc).
>
> >
>
> I hear what you're saying about limited
> > resources and community efforts, but as the old saying goes "the road to
> > hell is paved with good intentions". At some point somewhat needs to
> > step back, take a deep breath, and do an honest assessment to determine
> > what if any improvements are needed.
>
> I was that someone. I did that assessment, and this is what, within a
> reasonable amount of time, I managed to accomplish to cut through the
> information-dense manual and try to guide any new user through getting
> oriented. I hope you've read it and tried at least this "crash course"
> outline. If you did, please tell me what you thought of it:
>
> https://debian-live.alioth.debian.org/live-manual/stable/
> manual/html/live-manual.en.html#8
>
> I know it's just a small thing, but it's what time and energy allowed in
> lieu of a more ambitious total rewrite, which I was painfully aware was
> needed, but lacked the resources to carry out.
>
> But that day has come and gone. What's left of the  team is just keeping
> this doc, and live-build itself on life support. The main thrust of
> development is now in live-wrapper. So my honest assessment is: live-manual
> is imperfect, but it's the doc we have. If it falls short of your
> expectations, it falls on you, the users who still care about it, to make
> it better, because it's not likely anyone else will. That's not "copping an
> attitude". That's just giving you my experienced opinion on the state of
> things.
>
> >
>
> Griping from the user community
> > should not be the impetus for change. That's my $.02. ;-)
>
> So if you truly believe that, switch from griping to contributing!
>
> Ben
>

Bug#849827: live-build fails to build amd64 target

2017-01-01 Thread Ben Armstrong 

On January 1, 2017 4:47:39 PM "Peter.Stein"  wrote:


I actually had a bunch of comments, but suspected they would not be well
received


Try us.


and thus tried to be diplomatic


I must have missed that. ;)


and productive by suggesting a
step-by-step HOWTO. It's needed, everyone knows what one is, and
shouldn't be difficult to put together by the live-build experts. You
wanted an improvement suggestion and I gave you a very "actionable" one.


I know how many hundreds of hours of my personal time went into the 
original document before I called it quits and doubt your assessment of the 
ease of replacing the current doc. Since it's "incomprehensible", it seems 
it all needs to be replaced from scratch ... or was that hyperbole, perhaps?



I'm always reluctant to get into these "improvement" discussions because
the fact of the matter is you open source folks don't take constructive
criticism very well and invariably end up copping an attitude - like you
are now. I've developed software professionally for 35 years and can
state unequivocally that this documentation does not meet the
"production grade" standard.


I am not "you open source folks". I'm a person with feelings, not a bundle 
of stereotypes. I'm particularly not impressed by you "pulling rank" by 
trotting out your "senior developer" status when I haven't seen a single 
line of code or sentence of doc contributed by you to this project. Show me 
the code (or doc).



I hear what you're saying about limited
resources and community efforts, but as the old saying goes "the road to
hell is paved with good intentions". At some point somewhat needs to
step back, take a deep breath, and do an honest assessment to determine
what if any improvements are needed.


I was that someone. I did that assessment, and this is what, within a 
reasonable amount of time, I managed to accomplish to cut through the 
information-dense manual and try to guide any new user through getting 
oriented. I hope you've read it and tried at least this "crash course" 
outline. If you did, please tell me what you thought of it:


https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#8

I know it's just a small thing, but it's what time and energy allowed in 
lieu of a more ambitious total rewrite, which I was painfully aware was 
needed, but lacked the resources to carry out.


But that day has come and gone. What's left of the  team is just keeping 
this doc, and live-build itself on life support. The main thrust of 
development is now in live-wrapper. So my honest assessment is: live-manual 
is imperfect, but it's the doc we have. If it falls short of your 
expectations, it falls on you, the users who still care about it, to make 
it better, because it's not likely anyone else will. That's not "copping an 
attitude". That's just giving you my experienced opinion on the state of 
things.



Griping from the user community
should not be the impetus for change. That's my $.02. ;-)


So if you truly believe that, switch from griping to contributing!

Ben

Bug#849827: live-build fails to build amd64 target

2017-01-01 Thread Ozi Traveller 
Hi Peter

I use live-build to create my isos and I have a small explanation of what I
do here:
https://sourceforge.net/projects/linnix/files/

I'm not suggesting that you use what I have created, but it might help fill
in some of the blanks in the documentation.

I found the documentation very difficult to understand. I always hoped that
they might create some worked examples, as I found the small examples in
the docs too small to connect all the dots to get what I wanted.

Cheers



On Mon, Jan 2, 2017 at 7:47 AM, Peter.Stein  wrote:

> I actually had a bunch of comments, but suspected they would not be well
> received and thus tried to be diplomatic and productive by suggesting a
> step-by-step HOWTO. It's needed, everyone knows what one is, and shouldn't
> be difficult to put together by the live-build experts. You wanted an
> improvement suggestion and I gave you a very "actionable" one. I'm always
> reluctant to get into these "improvement" discussions because the fact of
> the matter is you open source folks don't take constructive criticism very
> well and invariably end up copping an attitude - like you are now. I've
> developed software professionally for 35 years and can state unequivocally
> that this documentation does not meet the "production grade" standard. I
> hear what you're saying about limited resources and community efforts, but
> as the old saying goes "the road to hell is paved with good intentions". At
> some point somewhat needs to step back, take a deep breath, and do an
> honest assessment to determine what if any improvements are needed. Griping
> from the user community should not be the impetus for change. That's my
> $.02. ;-)
> Cheers.
>
> On 01/01/17 13:09, Ben Armstrong wrote:
>
> On January 1, 2017 2:26:58 PM "Peter.Stein" 
>  wrote:
>
> > I eventually figured out by trial and error how to get the iso to build.
> > Not because of the documentation, but in spite of it. The resulting iso
> > won't boot via GRUB2, but that's a GRUB issue not a live-build issue.
> > HOWTOs are commonplace in the linux world. That's an obvious way to
> > improve the body of documentation for live-build.
>
>
>
> Each chapter of live-manual covers "how to" customize different aspects of
> live-build. The section on local package lists, which is the closest
> equivalent to the old command-line option, is here:
>
> https://debian-live.alioth.debian.org/live-manual/stable/
> manual/html/live-manual.en.html#409
>
> I'll be the first to admit that this documentation is not perfect: a
> documentation writer's job is never done and there's always room for
> improvement, but so far you have not made any actionable suggestions for
> making it better. Unfortunately, we're at an impasse. We cannot make the
> doc any better if you won't tell us, specifically, what about it didn't
> work for you.
>
> Ben
> p.s. Although I contributed to the authorship of this doc considerably
> before my retirement, it was a group effort, all done by volunteers like
> me, so credit for its good bits goes to the whole group. I'm sure you
> understand that group authorship can sometimes lack the coherence of
> single-authored documents, but we had a lot of material to cover, and
> worked with what meagre resources we had. I doubt if any of the remaining
> team is interested in this point at a complete rewrite (though really,
> that's entirely up to them,) so it will have to be incremental
> improvements. Your cavalier dismissal of the whole work of the doc as
> "incomprehensible" coupled with your refusal to give us anything concrete
> to work with to improve it disinclines me to help anymore. Good luck.
>
>
>

Bug#849827: live-build fails to build amd64 target

2017-01-01 Thread Peter.Stein 
I actually had a bunch of comments, but suspected they would not be well 
received and thus tried to be diplomatic and productive by suggesting a 
step-by-step HOWTO. It's needed, everyone knows what one is, and 
shouldn't be difficult to put together by the live-build experts. You 
wanted an improvement suggestion and I gave you a very "actionable" one. 
I'm always reluctant to get into these "improvement" discussions because 
the fact of the matter is you open source folks don't take constructive 
criticism very well and invariably end up copping an attitude - like you 
are now. I've developed software professionally for 35 years and can 
state unequivocally that this documentation does not meet the 
"production grade" standard. I hear what you're saying about limited 
resources and community efforts, but as the old saying goes "the road to 
hell is paved with good intentions". At some point somewhat needs to 
step back, take a deep breath, and do an honest assessment to determine 
what if any improvements are needed. Griping from the user community 
should not be the impetus for change. That's my $.02. ;-)

Cheers.

On 01/01/17 13:09, Ben Armstrong wrote:


On January 1, 2017 2:26:58 PM "Peter.Stein"  
wrote:


> I eventually figured out by trial and error how to get the iso to 
build.

> Not because of the documentation, but in spite of it. The resulting iso
> won't boot via GRUB2, but that's a GRUB issue not a live-build issue.
> HOWTOs are commonplace in the linux world. That's an obvious way to
> improve the body of documentation for live-build.



Each chapter of live-manual covers "how to" customize different 
aspects of live-build. The section on local package lists, which is 
the closest equivalent to the old command-line option, is here:


https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#409

I'll be the first to admit that this documentation is not perfect: a 
documentation writer's job is never done and there's always room for 
improvement, but so far you have not made any actionable suggestions 
for making it better. Unfortunately, we're at an impasse. We cannot 
make the doc any better if you won't tell us, specifically, what about 
it didn't work for you.


Ben
p.s. Although I contributed to the authorship of this doc considerably 
before my retirement, it was a group effort, all done by volunteers 
like me, so credit for its good bits goes to the whole group. I'm sure 
you understand that group authorship can sometimes lack the coherence 
of single-authored documents, but we had a lot of material to cover, 
and worked with what meagre resources we had. I doubt if any of the 
remaining team is interested in this point at a complete rewrite 
(though really, that's entirely up to them,) so it will have to be 
incremental improvements. Your cavalier dismissal of the whole work of 
the doc as "incomprehensible" coupled with your refusal to give us 
anything concrete to work with to improve it disinclines me to help 
anymore. Good luck.

Bug#849827: live-build fails to build amd64 target

2017-01-01 Thread Ben Armstrong 

On January 1, 2017 2:26:58 PM "Peter.Stein"  wrote:


I eventually figured out by trial and error how to get the iso to build.
Not because of the documentation, but in spite of it. The resulting iso
won't boot via GRUB2, but that's a GRUB issue not a live-build issue.
HOWTOs are commonplace in the linux world. That's an obvious way to
improve the body of documentation for live-build.


Each chapter of live-manual covers "how to" customize different aspects of 
live-build. The section on local package lists, which is the closest 
equivalent to the old command-line option, is here:


https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#409

I'll be the first to admit that this documentation is not perfect: a 
documentation writer's job is never done and there's always room for 
improvement, but so far you have not made any actionable suggestions for 
making it better. Unfortunately, we're at an impasse. We cannot make the 
doc any better if you won't tell us, specifically, what about it didn't 
work for you.


Ben
p.s. Although I contributed to the authorship of this doc considerably 
before my retirement, it was a group effort, all done by volunteers like 
me, so credit for its good bits goes to the whole group. I'm sure you 
understand that group authorship can sometimes lack the coherence of 
single-authored documents, but we had a lot of material to cover, and 
worked with what meagre resources we had. I doubt if any of the remaining 
team is interested in this point at a complete rewrite (though really, 
that's entirely up to them,) so it will have to be incremental 
improvements. Your cavalier dismissal of the whole work of the doc as 
"incomprehensible" coupled with your refusal to give us anything concrete 
to work with to improve it disinclines me to help anymore. Good luck.

Bug#849827: live-build fails to build amd64 target

2017-01-01 Thread Peter.Stein 
I eventually figured out by trial and error how to get the iso to build. 
Not because of the documentation, but in spite of it. The resulting iso 
won't boot via GRUB2, but that's a GRUB issue not a live-build issue. 
HOWTOs are commonplace in the linux world. That's an obvious way to 
improve the body of documentation for live-build.


On 12/31/16 16:15, Ben Armstrong wrote:


On December 31, 2016 6:10:55 PM "Peter.Stein" 
 wrote:

> I'm only seeing --linux-packages as a possible option for specifying
> configuration PACKAGES. Is there another option in this list that's
> appropriate?

No. You use package lists instead.


> As for what's in that manual - it's nearly incomprehensible. Is there a
> step-by-step HOWTO available somewhere?

Read the section on using package lists. If you don't understand 
something there, ask here, making reference to the part of the manual 
you don't understand so we can improve it.


Ben

Bug#849827: Fwd: Re: Bug#849827: live-build fails to build amd64 target

2016-12-31 Thread Ben Armstrong 

User error. This bug should be closed.


--- Forwarded message ---
From: Ben Armstrong <sy...@sanctuary.nslug.ns.ca>
Date: December 31, 2016 5:45:12 PM
Subject: Re: Bug#849827: live-build fails to build amd64 target
To: Peter.Stein <peter.st...@comcast.net>, sub...@bugs.debian.org

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" <peter.st...@comcast.net> 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

Bug#849827: live-build fails to build amd64 target

2016-12-31 Thread Ben Armstrong 
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"  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

Bug#849827: live-build fails to build amd64 target

2016-12-31 Thread Ben Armstrong 

On December 31, 2016 6:10:55 PM "Peter.Stein"  wrote:

I'm only seeing --linux-packages as a possible option for specifying
configuration PACKAGES. Is there another option in this list that's
appropriate?



No. You use package lists instead.


As for what's in that manual - it's nearly incomprehensible. Is there a
step-by-step HOWTO available somewhere?


Read the section on using package lists. If you don't understand something 
there, ask here, making reference to the part of the manual you don't 
understand so we can improve it.


Ben

Bug#849827: live-build fails to build amd64 target

2016-12-31 Thread Amilton Jesus 
Em sáb,
 31 de dez de 2016 às 20:06, Peter.Stein  escreveu:

>
>
>
>
>
>
>
>
>
>
> Ok, my bad. But there are plenty of
>
> examples oqn the web of specifying pacmgkages via the "lb config"
>
> command such as:
>
>
>
>
>
> http://www.debianuserforums.orrg/viewtopic.php?f=9=185
> 
>
>
>
>
>
> The --packages option shown there and in other examples isn't
>
> available in my version of live-build:
>
>
>
>
>
> lb config   [--apt apt|aptitude]
>
>
> [--apt-ftp-proxy URL]
>
>
> [--apt-http-proxy URL]
>
>
> [--apt-indices true|false]
>
>
> [--apt-options OPTION|"OPTIONS"]
>
>
> [--aptitude-options OPTION|"OPTIONS"]
>
>
> [--apt-pipeline DEPTH]
>
>
> [--apt-recommends true|false]
>
>
> [--apt-secure true|false]
>
>
> [--apt-source-archives true|false]
>
>
> [-a|--architectures ARCHITECTURE]
>
>
> [-b|--binary-images iso|iso-hybrid|netboot|tar|hdd]
>
>
> [--binary-filesystem fat16|fat32|ext2|ext3|ext4|ntfs]
>
>
> [--bootappend-install PARAMETER|"PARAMETERS"]
>
>
> [--bootappend-live PARAMETER|"PARAMETERS"]
>
>
> [--bootappend-live-failsafe PARAMETER|"PARAMETERS"]
>
>
> [--bootloaders grub-legacy|grub-pc|syslinux|grub-efi]
>
>
> [--cache true|false]
>
>
> [--cache-indices true|false]
>
>
> [--cache-packages true|false]
>
>
> [--cache-stages STAGE|"STAGES"]
>
>
> [--checksums md5|sha1|sha256|sha512|none]
>
>
> [--compression bzip2|gzip|lzip|xz|none]
>
>
> [--config GIT_URL::GIT_BRANCH]
>
>
> [--zsync true|false]
>
>
> [--build-with-chroot true|false]
>
>
> [--chroot-filesystem
>
> ext2|ext3|ext4|squashfs|jffs2|none]
>
>
> [--clean
>
>
> [-c|--conffile FILE]
>
>
> [--debconf-frontend
>
> dialog|editor|noninteractive|readline]
>
>
> [--debconf-priority low|medium|high|critical]
>
>
> [--debian-installer
>
> true|cdrom|netinst|netboot|businesscard|live|false]
>
>
> [--debian-installer-distribution daily|CODENAME]
>
>
> [--debian-installer-preseedfile FILE|URL]
>
>
> [--debian-installer-gui true|false]
>
>
> [--debootstrap-options OPTIONS]
>
>
> [--debootstrap-script SCRIPT]
>
>
> [--debug]
>
>
> [-d|--distribution CODENAME]
>
>
> [--parent-distribution CODENAME]
>
>
> [--parent-debian-installer-distribution CODENAME]
>
>
> [--dump]
>
>
> [--fdisk fdisk|fdisk.dist]
>
>
> [--force]
>
>
> [--grub-splash FILE]
>
>
> [--gzip-options OPTION|"OPTIONS"]
>
>
> [--ignore-system-defaults]
>
>
> [--initramfs auto|none|live-boot]
>
>
> [--initramfs-compression bzip2|gzip|lzma]
>
>
> [--initsystem sysvinit|systemd|none]
>
>
> [--image-name [NAME]
>
>
> [--interactive shell]
>
>
> [--isohybrid-options OPTION|"OPTIONS"]
>
>
> [--hdd-label LABEL]
>
>
> [--hdd-size MB]
>
>
> [--hdd-partition-start [parted unit, e.g. 63s]
>
>
> [--iso-application NAME]
>
>
> [--iso-preparer NAME]
>
>
> [--iso-publisher NAME]
>
>
> [--iso-volume NAME]
>
>
> [--jffs2-eraseblock SIZE]
>
>
> [--keyring-packages PACKAGE|"PACKAGES"]
>
>
> [-k|--linux-flavours FLAVOUR|"FLAVOURS"]
>
>
> [--linux-packages "PACKAGES"]
>
>
> [--losetup losetup|losetup.orig]
>
>
> [--memtest memtest86+|memtest86|none]
>
>
> [-m|--parent-mirror-bootstrap URL]
>
>
> [--parent-mirror-chroot URL]
>
>
> [--parent-mirror-chroot-security URL]
>
>
> [--parent-mirror-binary URL]
>
>
> [--parent-mirror-binary-security URL]
>
>
> [--parent-mirror-debian-installer URL]
>
>
> [--mirror-bootstrap URL]
>
>
> [--mirror-chroot URL]
>
>
> [--mirror-chroot-security URL]
>
>
> [--mirror-binary URL]
>
>
> [--mirror-binary-security URL]
>
>
> [--mirror-debian-installer URL]
>
>
> [--mode debian]
>
>
> [--system live|normal]
>
>
> [--net-root-filesystem nfs|cfs]
>
>
> [--net-root-mountoptions OPTIONS]
>
>
> [--net-root-path PATH]
>
>
> [--net-root-server IP|HOSTNAME]
>
>
> [--net-cow-filesystem nfs|cfs]
>
>
> [--net-cow-mountoptions OPTIONS]
>
>
> [--net-cow-path PATH]
>
>
> [--net-cow-server IP|HOSTNAME]
>
>
> [--net-tarball true|false]
>
>
> [--quiet]
>
>
>

Bug#849827: live-build fails to build amd64 target

2016-12-31 Thread Peter.Stein 
Ok, my bad. But there are plenty of examples on the web of specifying 
packages via the "lb config" command such as:


http://www.debianuserforums.org/viewtopic.php?f=9=185

The --packages option shown there and in other examples isn't available 
in my version of live-build:


lb config   [--apt apt|aptitude]
[--apt-ftp-proxy URL]
[--apt-http-proxy URL]
[--apt-indices true|false]
[--apt-options OPTION|"OPTIONS"]
[--aptitude-options OPTION|"OPTIONS"]
[--apt-pipeline DEPTH]
[--apt-recommends true|false]
[--apt-secure true|false]
[--apt-source-archives true|false]
[-a|--architectures ARCHITECTURE]
[-b|--binary-images iso|iso-hybrid|netboot|tar|hdd]
[--binary-filesystem fat16|fat32|ext2|ext3|ext4|ntfs]
[--bootappend-install PARAMETER|"PARAMETERS"]
[--bootappend-live PARAMETER|"PARAMETERS"]
[--bootappend-live-failsafe PARAMETER|"PARAMETERS"]
[--bootloaders grub-legacy|grub-pc|syslinux|grub-efi]
[--cache true|false]
[--cache-indices true|false]
[--cache-packages true|false]
[--cache-stages STAGE|"STAGES"]
[--checksums md5|sha1|sha256|sha512|none]
[--compression bzip2|gzip|lzip|xz|none]
[--config GIT_URL::GIT_BRANCH]
[--zsync true|false]
[--build-with-chroot true|false]
[--chroot-filesystem ext2|ext3|ext4|squashfs|jffs2|none]
[--clean
[-c|--conffile FILE]
[--debconf-frontend dialog|editor|noninteractive|readline]
[--debconf-priority low|medium|high|critical]
[--debian-installer 
true|cdrom|netinst|netboot|businesscard|live|false]

[--debian-installer-distribution daily|CODENAME]
[--debian-installer-preseedfile FILE|URL]
[--debian-installer-gui true|false]
[--debootstrap-options OPTIONS]
[--debootstrap-script SCRIPT]
[--debug]
[-d|--distribution CODENAME]
[--parent-distribution CODENAME]
[--parent-debian-installer-distribution CODENAME]
[--dump]
[--fdisk fdisk|fdisk.dist]
[--force]
[--grub-splash FILE]
[--gzip-options OPTION|"OPTIONS"]
[--ignore-system-defaults]
[--initramfs auto|none|live-boot]
[--initramfs-compression bzip2|gzip|lzma]
[--initsystem sysvinit|systemd|none]
[--image-name [NAME]
[--interactive shell]
[--isohybrid-options OPTION|"OPTIONS"]
[--hdd-label LABEL]
[--hdd-size MB]
[--hdd-partition-start [parted unit, e.g. 63s]
[--iso-application NAME]
[--iso-preparer NAME]
[--iso-publisher NAME]
[--iso-volume NAME]
[--jffs2-eraseblock SIZE]
[--keyring-packages PACKAGE|"PACKAGES"]
[-k|--linux-flavours FLAVOUR|"FLAVOURS"]
[--linux-packages "PACKAGES"]
[--losetup losetup|losetup.orig]
[--memtest memtest86+|memtest86|none]
[-m|--parent-mirror-bootstrap URL]
[--parent-mirror-chroot URL]
[--parent-mirror-chroot-security URL]
[--parent-mirror-binary URL]
[--parent-mirror-binary-security URL]
[--parent-mirror-debian-installer URL]
[--mirror-bootstrap URL]
[--mirror-chroot URL]
[--mirror-chroot-security URL]
[--mirror-binary URL]
[--mirror-binary-security URL]
[--mirror-debian-installer URL]
[--mode debian]
[--system live|normal]
[--net-root-filesystem nfs|cfs]
[--net-root-mountoptions OPTIONS]
[--net-root-path PATH]
[--net-root-server IP|HOSTNAME]
[--net-cow-filesystem nfs|cfs]
[--net-cow-mountoptions OPTIONS]
[--net-cow-path PATH]
[--net-cow-server IP|HOSTNAME]
[--net-tarball true|false]
[--quiet]
[--archive-areas ARCHIVE_AREA|"ARCHIVE_AREAS"]
[--parent-archive-areas ARCHIVE_AREA|"ARCHIVE_AREAS"]
[--security true|false]
[--source true|false]
[-s|--source-images iso|netboot|tar|hdd]
[--firmware-binary true|false]
[--firmware-chroot true|false]
[--swap-file-path PATH]
[--swap-file-size MB]
[--tasksel apt|aptitude|tasksel]
[--updates true|false]
[--backports true|false]
[--verbose]
[--loadlin true|false]
[--win32-loader true|false]
[--bootstrap-qemu-exclude PACKAGES]
[--bootstrap-qemu-static PATH]
[--bootstrap-qemu-arch ARCH]

I'm only seeing

Bug#849827: live-build fails to build amd64 target

2016-12-31 Thread Ozi Traveller 
I didn't find a package named a2ps-amd64, but there is on named a2ps.

Also maybe try
--debian-installer daily
instead of
--debian-installer live

Just my 2cents

Ozi

On Sun, Jan 1, 2017 at 7:42 AM, Peter.Stein  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
>

Bug#849827: live-build fails to build amd64 target

2016-12-31 Thread Peter.Stein 

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