Re: Planning for next squeeze point release (6.0.4)

[Michael .]

I'm sorry but as fascinating as this is this discussion between you two
(Adam and Daniel) is it is not educational, informative or constructive and
has nothing to do, now, with anything that any of us Plebian live users
need to know about.

Have a great weekend [?]

Michael
<<35C.png>>

E: Unable to locate package lightdm

[Michael .]

Good Morning everyone.

I have a small problem with either Live Build (or the Debian Repositories)
that is stopping me building a livecd and would appreciate some feedback or
suggestions.

I am building a Squeeze based distro but pulling some packages from Sid
such as the kernel and LightDM. I run through the build process and
everything goes well up until this point below.

"Get:16 http://cdn.debian.net squeeze/non-free amd64 Packages [124 kB]
Fetched 15.2 MB in 1min 35s (160 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
P: Begin creating manifest...
P: Begin installing local package lists...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package lightdm
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
Del lightdm-gtk-greeter 1.0.6-3 [30.4 kB]
Del lightdm 1.0.6-3 [124 kB]
root@michael-laptop:/home/michael/Cobber/uluru-minimal-amd64#"

Now I know LightDM is available in the repositories because I downloaded it
with apt-get download and placed it, and other debs, in the
/config/packages.chroot/ and /config/packages.binary/ folders. LightDM is
also listed in my preferences file to grab from Sid (it's not available in
Squeeze) and I have a sid.bainary and sid.chroot file in archives.

Does anyone have any idea what I am doing wrong or is there another issue?
If you need any more information just ask and I'll supply it.

Cheers.
Michael.

P.S. Happy New Year.

Re: E: Unable to locate package lightdm

[Michael .]

Thank you for your reply Daniel.

I do understand things may not work but I didn't expect LB not to be able
to find a package I had manually placed within the config structure. I
tried a different build just yesterday using Wheezy, I added the
repositories for the MATE desktop environment (which is for wheezy) and got
this error "E: Unable to locate package mate-core" which I know works
because I have it running on my laptop. I have again placed files in the
appropriate places added the appropriate keyrings (that install correctly)
and added the appropriate repositories (.binary and .chroot) and to get
this same message with a file built for the version I am trying to build
tells me there is something wrong with either my settings or LB being able
to bring something in from a "foreign" repository.

I am currently building a repo with MATE in it that I will host on a NAS
just for this project. I will see what is happening once I get that up and
running.

Again thanks for your reply.
Michael.

On 2 January 2012 10:02, Daniel Baumann <
daniel.baum...@progress-technologies.net> wrote:

> On 01/01/2012 09:25 PM, Michael . wrote:
> > I am building a Squeeze based distro but pulling some packages from Sid
> > such as the kernel and LightDM.
>
> you cannot just put packages from sid into a squeeze system and hope
> that they install or work correctly. the way of making that work is
> known as backporting (rebuilding newer packages from testing or unstable
> on stable).
>
> for the kernel, maintained backports for squeeze are available at
> progress-linux.org. for lightdm, i'm not aware of an existing backports,
> but it's trivial to do yourself (simple rebuild should be enough).
>
> --
> Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
> Email:  daniel.baum...@progress-technologies.net
> Internet:   http://people.progress-technologies.net/~daniel.baumann/
>
>
> --
> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> http://lists.debian.org/4f00e620.6050...@progress-technologies.net
>
>

Re: E: Unable to locate package lightdm

[Michael .]

You are correct I am using lb3 (sorry I should have written that in my
first message but I kind of figured people would see what I was using by
the locations I wrote about) but your assumption that I am putting it in
lb2 locations is incorrect. From my first message

"Now I know LightDM is available in the repositories because I downloaded
it with apt-get download and placed it, and other debs, in the
/config/packages.chroot/ and /config/packages.binary/ folders. LightDM is
also listed in my preferences file to grab from Sid (it's not available in
Squeeze) and I have a sid.bainary and sid.chroot file in archives."

So yes, I believe I am placing the required files in the correct places.

On 5 January 2012 23:17, Daniel Baumann <
daniel.baum...@progress-technologies.net> wrote:

> On 01/05/2012 10:03 AM, Michael . wrote:
> > I do understand things may not work but I didn't expect LB not to be
> > able to find a package I had manually placed within the config
> > structure.
>
> it finds it if you put it in the right location; i presume you were
> using lb3 and put it in the old location for lb2 (old:
> config/chroot_local-packages; new: config/packages.chroot).
>
> > I tried a different build just yesterday using Wheezy, I
> > added the repositories for the MATE desktop environment (which is for
> > wheezy) and got this error "E: Unable to locate package mate-core"
>
> have you put the archive definitions in the right location? lb2 used
> config/chroot_sources/foo.{binary,chroot} and
> config/chroot_sources/foo.{binary,chroot}.gpg, lb3 uses
> config/archives/foo.{list,key}.{chroot,binary}
>
> --
> Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
> Email:  daniel.baum...@progress-technologies.net
> Internet:   http://people.progress-technologies.net/~daniel.baumann/
>
>
> --
> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> http://lists.debian.org/4f0594f6.8090...@progress-technologies.net
>
>

Re: E: Unable to locate package lightdm

[Michael .]

Ok, so adding the keyring, and yes it installs correctly, to the packages
{binary,chroot} folders isn't good enough.

On 6 January 2012 06:09, Ben Armstrong  wrote:

> On 01/05/2012 02:22 PM, Michael . wrote:
> > and I have a sid.bainary and sid.chroot file in archives."
> >
> > So yes, I believe I am placing the required files in the correct places.
>
> Perhaps not ...
>
> > On 5 January 2012 23:17, Daniel Baumann <
> daniel.baum...@progress-technologies.net> wrote:
> > lb3 uses config/archives/foo.{list,key}.{chroot,binary}
>
> I don't see '.list' in the filenames you indicated above. You also need
> the corresponding '.key' files. If you don't have correct sid
> config/archives/ files, any dependencies from your included .deb won't
> be resolvable.
>
> Ben
>

Huge /pool folder with 202 MB of debs in basic minimal live system.

[Michael .]

Good evening everyone.

I am using Live Build 3.0~a41-1. I've just finished building a live
binary-hybrid.iso and before I tried burning to disc I thought I'd check
the size of the iso. The iso is 514.9 MB which I thought was way to big for
a basic image with icewm, synaptic, iceweasel, menu, and xterm (+
dependencies), I expected about 300-350 MB. Upon further investigation I
see my /pool folder is 202 MB and full of debs. Now I have 2
package.list.binary that contain contrib and non-free wireless firmware and
ndiswrapper and these debs are in the /pool folder as I expected them to be
(contrib folder is 120.8 KB, non-free folder is 11.3 MB). However I also
have a huge /main folder (190.6 MB) in /pool and would like to be able to
remove it from the build process if at all possible. Why? Well this iso is
supposed to be a minimal graphical environment where the end user picks
what they want to install instead of me supplying what I think is best for
them.

So my question is, what triggers do I need to modify in config to achieve
this? From my reading of the mailing list there used to be something in LB2
but I can't see anything in LB3. If there is nothing in config is there
another way to stop packages being placed in the /pool folder being the
exact opposite to my deliberately placing the packages.list.binary files in
the config/packages folder to place the non-free firmware and ndiswrapper
debs in the /pool folder.

Cheers.
Michael

Re: Huge /pool folder with 202 MB of debs in basic minimal live system.

[Michael .]

On 14 January 2012 23:22, Ben Armstrong  wrote:

> On 01/14/2012 06:42 AM, Ben Armstrong wrote:
> > So, it sounds like you're using a packages.list where you meant to use
> > packages.list.chroot.
>

What did I say that makes you assume that? Maybe next time I'll write down
every minute detail in my email or should I just place a copy of my config
tree in my email. I have 2 package.list.binary that are supposed to put
things in /pool (I did this deliberately) the other file is a
package.list.chroot (while I never mentioned it specifically I assumed, my
fault, you would recognise I did this because I did the binary).

>
> p.s. We did warn about this in the doc:
>

Yes you did, that is why I did it how I did it .

Btw I did another run last night changing  --debian-installer in my auto
config file to live instead of true and that made the /pool/main folder
134.9 MB (very different to 190.6 MB) so the type of debian-installer used
can add nearly 60 MB on it's own (there is nothing in the doc that mentions
this).

Cheers.
Michael.

Re: Simple default ISO generation fails

[Michael .]

On 26 January 2012 09:48, Ben Armstrong  wrote:

> On 25/01/12 04:47 PM, Daniel Ellison wrote:
>
>> On 25/01/12 01:32 PM, Daniel Ellison wrote:
>>
>>> Thanks for the response, Jake/Snow. I'll try adding udev to my pinned
>>> sid live-* packages in chroot_apt/preferences and see what happens.
>>>
>>
>> Unfortunately it made no difference. My config/chroot_apt/preferences
>> now looks like this (with no line breaks):
>>
>> Package: live-boot live-boot-initramfs-tools live-config
>> live-config-sysvinit udev
>> Pin: release n=sid
>> Pin-Priority: 1001
>>
>
> I don't think you can do that. I think you need a separate stanza per
> package, e.g.
>
> Package: live-boot
>
> Pin: release n=sid
> Pin-Priority: 1001
>
> etc.
>
> Ben
>
>
>
> --
> To UNSUBSCRIBE, email to 
> debian-live-request@lists.**debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/**4F2086DB.7070501@sanctuary.**
> nslug.ns.ca<http://lists.debian.org/4f2086db.7070...@sanctuary.nslug.ns.ca>
>
> 8.4.5 Apt-Pinning in the manual seems to disagree with you on this point.

"Package: live-boot live-boot-initramfs-tools live-config
live-config-sysvinit
Pin: release n=sid
Pin-Priority: 600"

Regards
Michael.

Re: Australian mirrors result in "Encountered a section with no Package: header"

[Michael .]

Hi Jason.

There are frequently problems with the Australian mirrors, all of them,
even with just normal system updating. If it occurs during a LiveBuild I
just adjust the settings to use the US or a geographically closer mirror
while for regular system updating I just try again later in the day.

Cheers.
Michael.

Re: Including firmware packages automatically by default from now on

[Michael .]

On 27 April 2012 07:26, Daniel Baumann <
daniel.baum...@progress-technologies.net> wrote:

> The next version of live-build (current HEAD of debian-next branch in git)
> now includes firmware by default in all images.
>

This is excellent news. Thanks for this new development.

Cheers.
Michael

Auto scripts missing.

[Michael .]

Hi everyone.

I've just had an opportunity to get back into Debian Live and have found
that my previous auto scripts that I used with testing no longer work. I
read through the manual and they are still mentioned in the manual so I
assumed I was doing something wrong. I went looking for the folder
(/usr/share/doc/live-build/examples/auto/*) the scripts are supposed to be
in so I could copy them over again and the "examples" folder and subsequent
folders are not there.

Has this capability been removed from Live Build? If yes what has replaced
this capability? If no why is it not on my system? I have completely
re-insatlled Live Build on a new Wheezy install.

Regards.
Michael.

Re: Auto scripts missing.

[Michael .]

Thanks for that Chals.

I have found them again. My next question is then why isn't Live Build
seeing the Auto scripts and adjusting the config files accordingly.

I am using Wheezy for this so my version is, like yours, 3.0~a51-1.

I might purge then reinstall Live Build and see if that helps.
Cheers.
Michael.

On 20 September 2012 08:16, chals  wrote:

> On Wed, Sep 19, 2012 at 7:25 AM, Michael .  wrote:
> >
> > I read through the manual and they are still mentioned in the manual so I
> > assumed I was doing something wrong. I went looking for the folder
> > (/usr/share/doc/live-build/examples/auto/*) the scripts are supposed to
> be
> > in so I could copy them over again and the "examples" folder and
> subsequent
> > folders are not there.
> >
>
> Well, I think you are caught somewhere in-between.
>
> If I'm not wrong, the version currently in wheezy (3.0~a51-1) still
> stores the example auto/ scripts in:
>
> /usr/share/live/build/examples/auto/build
> /usr/share/live/build/examples/auto/clean
> /usr/share/live/build/examples/auto/config
>
> Whereas sid's version (3.0~a58-1) stores them in (as stated in live-manual
> 3.x):
>
> /usr/share/doc/live-build/examples/auto/build
> /usr/share/doc/live-build/examples/auto/clean
> /usr/share/doc/live-build/examples/auto/config
>
> You can check the list of auto files in the package using:
>
>  $ dpkg -L live-build | grep auto
>
> Have a nice day!
>
> --
> chals
> www.chalsattack.com
>

Re: Auto scripts missing.

[Michael .]

Thanks again Chals for your input.

I checked if my config script is executable and it is, the other two were
copied over from the correct location that you indicated to me. I purged
Live Build and then reinstalled it. Still no good. I purged it again.
Rebooted my laptop, reinstalled Live Build again and it worked. Now all I
need to check is that the build starts, and the final build works correctly
after completion.

Regards.
Michael.

On 20 September 2012 09:09, chals  wrote:

> On Thu, Sep 20, 2012 at 12:26 AM, Michael .  wrote:
> > Thanks for that Chals.
> >
>
> You are welcome :)
>
> > I have found them again. My next question is then why isn't Live Build
> > seeing the Auto scripts and adjusting the config files accordingly.
> >
> > I am using Wheezy for this so my version is, like yours, 3.0~a51-1.
> >
>
> I use the latest version (3.0~a58-1) in both sid and wheezy. However,
> I have downgraded my wheezy's live-build to 3.0~a51-1 for the sake of
> testing whether auto/ scripts work or not. And they *do* work here. I
> have no idea what you are doing wrong.
>
> Just to make sure, if I were you, I would, first of all make the build
> directory and create the 'auto' directory inside it with my scripts;
> whether copied from the 'examples' or handmade. In this last case
> remember to make them executable. Auto scripts are *scripts* so you
> have to give them execute permission. This is not necessary if you
> just copy them from the 'examples/auto' directory because they already
> are.
>
> And then, once the scripts are in place, call 'lb config' as user and
> then 'lb build' as root. And you will see something like this:
>
> chals@aelita:~/sandbox/testauto$ lb config
> [2012-09-20 00:49:59] lb_config
> P: Executing auto/config script.
>
> and this:
>
> root@aelita:/home/chals/sandbox/testauto# lb build
> [2012-09-20 01:03:22] lb_build
> P: Executing auto/build script.
>
> Good luck
>
> --
> chals
> www.chalsattack.com
>

Re: Auto scripts missing.

[Michael .]

On 20 September 2012 21:44, Ben Armstrong wrote:

> I'll respond to any practical suggestions you have for improvement of the
> software, manual or
> support process if you post it publicly to the list. I'm not interested in
> following up in private
> email, sorry.
>
> As for my "superior tone", it was not my intent to come across this way,
> so I do apologize if there
> was any hint of that. If there was some way in which I misunderstood why
> the purge/reinstall/reboot
> dance you did actually made sense, you could have addressed that technical
> concern of mine with a
> technical rebuttal (again, on the public list) without responding as if
> you had been attacked.
>
> Ben
>

Ben I did not mean for that last reply to be private. I am more than
willing for you to post it in *this* public discussion.

As for practical suggestions I'd suggest you or someone else posts a manual
on the live site, that is actually accurate for the versions of Live Build
that are available in each dist. If the manual was accurate in the first
instance I wouldn't have come onto the list to ask a question.

Another practical suggestion. You may be sorry about the "superior tone"
but your choice of words, even in this email with the word "dance", says to
me you are still using the "superior tone". Dance is in no way a technical
term in IT circles, if you want your users to use technical terms then I
personally would appreciate it if you would do likewise.

Chals was a great help filling in the blanks of the manual and offering
other suggestions, I appreciate his assistance. I'm not interested in
discussing this further as the issue I asked the question about has been
resolved.

Regards
Michael.

Re: Auto scripts missing.

[Michael .]

Ben, I accept all of your points. I to can be a bit brusque in such
circumstances. I also apologise.

Just as a  quick aside, something is broken deeper in my system, other
applications (e.g. dropbox) have broken. Now to work through all those
issues and post reports to the appropriate people and places (not here).

Regards.
Michael.

On 21 September 2012 21:02, Ben Armstrong wrote:

> Michael,
>
> I would like to explain the unfortunate circumstances of manuals being out
> of sync. I hope my
> explanation below as to why things are the way they are is satisfactory.
> As to my own conduct
> towards you, I admit I was a bit brusque and presumptive, and do offer
> apology. While it may be
> somewhat of an occupational hazard, I do not mean to excuse it, but I do
> wish to clear up the
> intention behind my remarks, which was certainly not to belittle.
>
> On 09/20/2012 04:27 PM, Michael . wrote:
> > As for practical suggestions I'd suggest you or someone else posts a
> manual on the live site, that
> > is actually accurate for the versions of Live Build that are available
> in each dist. If the manual
> > was accurate in the first instance I wouldn't have come onto the list to
> ask a question.
>
> Unfortunately, that would take considerably more work than you might
> imagine. The manual authors and
> translators make commits into git which, in turn, flow into unstable and
> then to testing. We don't
> write documentation directly for testing. By the time it reaches testing,
> it may in fact be ahead of
> live-build or behind, as we have no way to predict when the migrations
> will be complete for each
> version. The end result is some slight out-of-sync-ness of manual version
> with live-build version,
> not to mention also live-boot, live-config and friends. So you see,
> keeping the doc in sync during
> the turbulent pre-release period is a non-trivial problem to solve. You
> will also see, looking at
> http://live.debian.net, that we mark the versions of the documentation we
> make available online as
> being for oldstable, stable and unstable. This is no accident. It cannot
> easily be any other way.
> The good news is that by the time stable releases, we work towards
> complete synchronization of the
> documentation with the software that ends up in the stable release. In the
> meantime, as a user of
> testing, you need to be aware of the situation and work around it. Often
> the simplest thing to do is
> to install live-build from unstable, and mix in live-boot and live-config
> from unstable in your test
> builds (as live-manual explains how to do with APT pinning).
>
> > Another practical suggestion. You may be sorry about the "superior tone"
> but your choice of words,
> > even in this email with the word "dance", says to me you are still using
> the "superior tone". Dance
> > is in no way a technical term in IT circles, if you want your users to
> use technical terms then I
> > personally would appreciate it if you would do likewise.
>
> Maybe this is simply a matter of culture/language clash? In my lexicon,
> which is heavily laced with
> terms commonly used in informal speech in technical circles, "dance" is by
> no means a pejorative. If
> anything, it is a somewhat whimsical way to refer to any seemingly complex
> and possibly not
> necessary (or at least something we *wish* were not necessary) set of
> steps to achieve an intended
> result. If I failed to see the point of the steps you took, making it
> appear to me as a "dance",
> please do not take that as an insult. It speaks more of my own ignorance,
> in that case, than a
> deliberate, mean-spirited and/or arrogant stance. I am certainly not
> beyond taking correction when
> I've misunderstood.
>
> Let's clear up the intention behind those remarks. Because you did not
> state any theory about
> potential corruption (files you had removed yourself? your disk going bad?
> brokenness of one of our
> maintainer scripts?) nor any direct evidence of corruption (mismatched
> 'debsums' to name one) nor
> did you include any output, preferring instead to very briefly summarize
> the actions you took, this
> gave the *appearance* of you trying random things with unclear motivation
> as to your line of
> reasoning. In the private email you sent, you divulged further details
> about the systematic line of
> inquiry you were taking. That was unclear from your public posts. If there
> is anything left her for
> me to beg apology for, it is for having assumed the lack of a plan (that
> was not in evidence at the
> time) instead of assuming the reverse and encouraging you to explain y

Building a Live system with Liquorix kernel instead of a regular Debian kernel.

[Michael .]

Hello everyone.

I want to build an iso that uses the Liquorix kernel instead of the Debian
Kernel. I have not given this a go yet so I am just clarifying what I need
to do before I start.

My auto/config is attached to this message so you can see how it is setup.
I would draw your attention to the lines:
--archives "ftp.au.debian.org backports.debian.org repo.mate-desktop.org
liquorix.net" \
--keyring-packages "debian-archive-keyring mate-archive-keyring
liquorix-keyrings" \
--linux-packages "linux-image" \

Now from my understanding --linux-packages "linux-image" \ is the line that
deals with the installed kernel, if I'm wrong in this understanding please
let me know. If I am correct in this understanding what would I enter
instead of "linux-image" to get Live Build to use the Liquorix kernel
instead of the Debian kernel. Or is this maybe so someone can use a BSD or
Hurd kernel instead?

The other thing I was thinking is maybe all I need to do is place the
relevant Liquorix packages into either the config/packages,
config/packages.binary, or config/packages.chroot folder. But then again,
would that then install both kernels (Debian and Liquorix) when all I want,
in this instance, is the Liquorix kernel?

Or do I need to specify the Liquorix kernel in my
config/package-lists/cobber-mate-.list.{binary-chroot} file/s.

In my config/archive folder I have added liquorix-keyring.key.binary and
liquorix-keyring.key.chroot and during the build everything is recognised
as it should be (I did this so I could add the Liquorix kernel later on if
need be).

In my config/archive/mate-repository.list.{binary-chroot} I have all the
relevant lines for the sources.list and this works as it should.

Anyway, if anyone can point me in the right direction here I'd really
appreciate it.

Regards.
Michael.


config
Description: Binary data


cobber-mate.list.binary
Description: Binary data


mate-repository.list.binary
Description: Binary data

Re: Building a Live system with Liquorix kernel instead of a regular Debian kernel.

[Michael .]

I have looked already but will look again.

On 22 September 2012 15:56, Daniel Baumann <
daniel.baum...@progress-technologies.net> wrote:

> On 09/22/2012 03:34 AM, Michael . wrote:
>
>> I want to build an iso that uses the Liquorix kernel instead of the
>> Debian Kernel.
>>
>
> see mailinglist archive about using custom kernels, this has been
> discussed many times already.
>
> --
> Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
> Email:  
> daniel.baumann@progress-**technologies.net
> Internet:   http://people.progress-**technologies.net/~daniel.**
> baumann/ <http://people.progress-technologies.net/~daniel.baumann/>
>
>
> --
> To UNSUBSCRIBE, email to 
> debian-live-request@lists.**debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/**505D52F7.8030803@progress-**
> technologies.net<http://lists.debian.org/505d52f7.8030...@progress-technologies.net>
>
>

Re: Building a Live system with Liquorix kernel instead of a regular Debian kernel.

[Michael .]

Thanks Ben.

I will go through it later today, it isn't even 5am here right now, and
correct the errors you pointed out and will go through the manual and check
the rest. The auto script has not given me problems for a long time, even
when I was using it before my long hiatus, so I assumed I had caught the
issues that would break the build.

On 22 September 2012 21:31, Ben Armstrong wrote:

> Michael,
>
> On 09/21/2012 10:34 PM, Michael . wrote:
> > My auto/config is attached to this message so you can see how it is
> setup.
>
> There are quite a number of problems with your config, the first one being
> that it is very long,
> concealing actual problems. It is best practice to only include configs
> that actually differ from
> the defaults, making it much easier to see the actual customizations you
> have made. Default
> configurations are often better tested, so when problems arise, it is the
> changed configurations we
> need to see in order to troubleshoot.
>
> Some others I noticed:
>
> --archives "ftp.au.debian.org backports.debian.org
> repo.mate-desktop.org liquorix.net" \
>
> Please note the doc (man lb_config) about this option, as you are not
> using it correctly:
>
>--archives ARCHIVE|"ARCHIVES"
>enables one of available third-party archive configurations in
> /usr/share/live/build/archives.
>
> Read live-manual again on how to enable third-party archives. Also, your
> main Debian archive does
> not belong in this list, and backports can be enabled with --backports
> true, since they are
> officially supported by Debian and not third-party.
>
> You needn't set any of the --parent options at all, as you are not
> building a derivative, and these
> options relate specifically to derivatives. You also needn't set many of
> the --mirror options, as
> most of them default to values of others. See live-manual for details.
>
> Inclusion of debian-archive-keyring in your --keyring-packages option is
> unnecessary, as that is
> automatically installed.
>
> Provided your third-party kernel provides a linux-image-2.6-amd64
> metapackage that points at the
> third-party kernel, there is no need at all to specify --linux-packages.
> Otherwise, specify the stub
> which, when the architecture is suffixed, forms the whole kernel package
> name. (And yes, as Daniel
> suggested, you may also look for that recent thread in the list archive in
> which we cover this, but
> since this turns out to be an FAQ, I plan to add it as an example to
> live-manual.)
>
> There is a typo in --debconf-nowarnings. You have put a blank between the
> words in the option name
> instead of a dash. This will probably break all options from there to the
> end of the line.
>
> I did not rigorously check all other options against their default values,
> as that would be tedious
> indeed. In future, if you follow my advice and confine your config to only
> include changes from the
> defaults, that would help us all to communicate better concerning your
> config, and will likely also
> reduce the number of mistakes you make.
>
> Ben
>

--debian-installer "live" \ yet no installer option on Live CD bootloader.

[Michael .]

Hello again everyone

I have successfully setup a live build of Debian Wheezy with MATE desktop
environment. Everything is working as it should except the iso is missing
an installer on the bootloader. In my auto script I have told the config to
use the "live" installer yet there is no installer available. All that is
listed is "Live" and "Live (Failsafe)" and these both, as they should, go
straight to a working desktop.

Following the manual which says
12.1 Types of Debian Installer
<http://live.debian.net/manual-3.x/html/live-manual.en.html#579>

The three main types of installer are:
<http://live.debian.net/manual-3.x/html/live-manual.en.html#580>

*"Regular" Debian Installer*: This is a normal Debian Live image with a
separate kernel and initrd which (when selected from the appropriate
bootloader) launches into a standard Debian Installer instance, just as if
you had downloaded a CD image of Debian and booted it. Images containing a
live system and such an otherwise independent installer are often referred
to as "combined images".
<http://live.debian.net/manual-3.x/html/live-manual.en.html#581>

On such images, Debian is installed by fetching and installing .deb
packages using *debootstrap* or *cdebootstrap*, from the local media or
some network-based network, resulting in a standard Debian system being
installed to the hard disk.
<http://live.debian.net/manual-3.x/html/live-manual.en.html#582>

This whole process can be preseeded and customized in a number of ways; see
the relevant pages in the Debian Installer manual for more information.
Once you have a working preseeding file, *live-build* can automatically put
it in the image and enable it for you.
<http://live.debian.net/manual-3.x/html/live-manual.en.html#583>

*"Live" Debian Installer*: This is a Debian Live image with a separate
kernel and initrd which (when selected from the appropriate bootloader)
launches into an instance of the Debian Installer.
<http://live.debian.net/manual-3.x/html/live-manual.en.html#584>

Installation will proceed in an identical fashion to the "Regular"
installation described above, but at the actual package installation stage,
instead of using *debootstrap* to fetch and install packages, the live
filesystem image is copied to the target. This is achieved with a special
udeb called *live-installer*.
<http://live.debian.net/manual-3.x/html/live-manual.en.html#585>

After this stage, the Debian Installer continues as normal, installing and
configuring items such as bootloaders and local users, etc.
<http://live.debian.net/manual-3.x/html/live-manual.en.html#586>

*Note:* to support both normal and live installer entries in the bootloader
of the same live media, you must disable *live-installer* by preseeding
live-installer/enable=false.

The man page says

*--debian-installer* true|cdrom|netinst|netboot|businesscard|live|false
   defines which type, if  any,  of  the  debian-installer  should  be
   included in the resulting binary image. By default, no installer is
   included. All available flavours except live are the identical con-
   figurations  used  on  the  installer  media  produced  by  regular
   debian-cd.  When  live  is  choosen,  the  live-installer  udeb  is
   included  so that debian-installer will behave different than usual
   - instead of installing the debian system from  packages  from  the
   medium or the network, it installs the live system to the disk.

So I am assuming I have that part correct and that I am missing something
else.

My auto/config is attached, I have stripped sections that been suggested I
did not need and will strip more after this coming weekend.
Regards.
Michael.


config
Description: Binary data

Re: --debian-installer "live" \ yet no installer option on Live CD bootloader.

[Michael .]

On 24 September 2012 23:41, Daniel Baumann <
daniel.baum...@progress-technologies.net> wrote:

> On 09/24/2012 10:18 AM, Michael . wrote:
>
>> the iso is missing an installer on the bootloader.
>>
>
> see bts.
>
> --
> Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
> Email:  
> daniel.baumann@progress-**technologies.net
> Internet:   http://people.progress-**technologies.net/~daniel.**
> baumann/ <http://people.progress-technologies.net/~daniel.baumann/>
>
>
> --
> To UNSUBSCRIBE, email to 
> debian-live-request@lists.**debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/**50606314.6040300@progress-**
> technologies.net<http://lists.debian.org/50606314.6040...@progress-technologies.net>
>
> I may be blind but after looking through the bts list of thousands upon
thousands of bugs I can't find one that relates to this issue. I'd
appreciate it if someone could/would point me in the right direction.

Regards.
Michael.

Re: --debian-installer "live" \ yet no installer option on Live CD bootloader.

[Michael .]

I forgot to add I'm now using the live build in Sid.

On 1 October 2012 06:00, Michael .  wrote:

>
>
> On 24 September 2012 23:41, Daniel Baumann <
> daniel.baum...@progress-technologies.net> wrote:
>
>> On 09/24/2012 10:18 AM, Michael . wrote:
>>
>>> the iso is missing an installer on the bootloader.
>>>
>>
>> see bts.
>>
>> --
>> Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
>> Email:  
>> daniel.baumann@progress-**technologies.net
>> Internet:   http://people.progress-**technologies.net/~daniel.**
>> baumann/ <http://people.progress-technologies.net/~daniel.baumann/>
>>
>>
>> --
>> To UNSUBSCRIBE, email to 
>> debian-live-request@lists.**debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmas...@lists.debian.org
>> Archive: http://lists.debian.org/**50606314.6040300@progress-**
>> technologies.net<http://lists.debian.org/50606314.6040...@progress-technologies.net>
>>
>> I may be blind but after looking through the bts list of thousands upon
> thousands of bugs I can't find one that relates to this issue. I'd
> appreciate it if someone could/would point me in the right direction.
>
> Regards.
> Michael.
>

Re: Creating a Wheezy Debian live installer?

[Michael .]

On 2 October 2012 01:08, Strickland, Carl  wrote:

> ** **
>
> Now I’m trying to create a live Wheezy installer for the host PXE system
> and am running into issues.
>
> ** **
>
> I’ve included debian-installer-launcher in my package list and selected
> “—debian-installer live” as an option, but this isn’t generating the
> expected live install CD (though I am getting a live CD with a command
> prompt).
>
> ** **
>
> What am I missing? Is there a tutorial out there showing how to use the
> new live tools to generate a very simple custom Debian live installer?
>
> ** **
>
> Any help is much appreciated!
>
> ** **
>
> ** **
>
> Thank you,
>
> Carl Strickland
>

I asked this question last week, 8 or 9 days ago actually, and was told to
look at the BTS. I have looked through the BTS, there are thousands of bugs
to sift through, and haven't found anything yet, so I posted back here
yesterday to ask for a little help. I hope you get a response as it is my
last big hurdle.

Regards.
Michael.

Re: --debian-installer "live" \ yet no installer option on Live CD bootloader.

[Michael .]

Still trying to find anything on the BTS that gives a clue of how to
resolve this problem. Has anyone else found anything on the BTS? If you
have can you link to it please? if not can someone give any other clue as
to a work around? Would a hook to adjust the boot menu work?

On 1 October 2012 06:04, Michael .  wrote:

> I forgot to add I'm now using the live build in Sid.
>
>
> On 1 October 2012 06:00, Michael .  wrote:
>
>>
>>
>> On 24 September 2012 23:41, Daniel Baumann <
>> daniel.baum...@progress-technologies.net> wrote:
>>
>>> On 09/24/2012 10:18 AM, Michael . wrote:
>>>
>>>> the iso is missing an installer on the bootloader.
>>>>
>>>
>>> see bts.
>>>
>>> --
>>> Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
>>> Email:  
>>> daniel.baumann@progress-**technologies.net
>>> Internet:   http://people.progress-**technologies.net/~daniel.**
>>> baumann/ <http://people.progress-technologies.net/~daniel.baumann/>
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to 
>>> debian-live-request@lists.**debian.org
>>> with a subject of "unsubscribe". Trouble? Contact
>>> listmas...@lists.debian.org
>>> Archive: http://lists.debian.org/**50606314.6040300@progress-**
>>> technologies.net<http://lists.debian.org/50606314.6040...@progress-technologies.net>
>>>
>>> I may be blind but after looking through the bts list of thousands upon
>> thousands of bugs I can't find one that relates to this issue. I'd
>> appreciate it if someone could/would point me in the right direction.
>>
>> Regards.
>> Michael.
>>
>
>

Re: Meaning of --parent-distribution and --parent-distribution

[Michael .]

On 8 October 2012 10:36, Mark Schneider  wrote:

>  Hello,
>
> What is "*--parent-distribution*" and "*
> --parent-debian-installer-distribution*" for? I don't want to guess ...
> There are appriopriate entries in conf/bootstrap file.
>
> There is no description in manual. Thank you.
>
> regards, Mark
>
> -- m...@it-infrastrukturen.org
> http://rsync.it-infrastrukturen.org
>
>  From the man page:

-d|*--parent-distribution* *CODENAME*
   defines  the  parent  distribution for derivatives of the resulting
   live system.

   -d|*--parent-debian-installer-distribution* *CODENAME*
   defines the parent debian-installer distribution for derivatives of
   the resulting live system.

Hope that helps.

Re: cannot install openjdk-6-jre on wheezy hdd live

[Michael .]

On 26 October 2012 06:04, upite...@lycos.com  wrote:

> Package openjdk-6-jre is not available, but is referred to by another
> package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> However the following packages replace it:
>   openjdk-6-jre-headless icedtea-netx-common icedtea-netx icedtea-6-plugin
>
> Package openjdk-6-jre-headless is not available, but is referred to by
> another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> However the following packages replace it:
>   openjdk-6-jre default-jre-headless icedtea-netx-common icedtea-netx
>

The clue is in here, openjdk-6-jre etc are no longer available as discreet
packages but are instead probably part of other packages. Just adjust your
setup to include the other packages instead of the packages you are being
told are no longer available.

May I suggest if you come across this again you take a look at the Debian
Packages web page. It will tell you what is and isn't available.

Cheers.
Michael.

Re: live-build system published at sourceforge

[Michael .]

All I get is a 404 not found for the actual file.

On 29 October 2012 13:59, Arne de Boer  wrote:

> At:
> http://sourceforge.net/projects/sposkpat/
> a live-build system is published
>
>
> --
> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> http://lists.debian.org/1351479558.51509.yahoomailclas...@web162404.mail.bf1.yahoo.com
>
>

Re: last call: remaining items for wheezy

[Michael .]

I have never yet seen an email address with a full stop at the end. Chals
has picked up a valid typographical error

Michael.


On 12 December 2012 17:50, Michal Suchanek  wrote:

> On 11 December 2012 20:49, Daniel Baumann
>  wrote:
> > On 12/11/2012 03:00 PM, chals wrote:
> >>
> >> Francis Ndangi, who offered to help on the mailing list
> >> https://lists.debian.org/debian-live/2012/11/msg00018.html has already
> >> revised the French translation.
> >
> >
> > great.
> >
> >
> >> - One of the mailing list addresses is not recognized by mail clients
> >> because there is a dot at the end → ‹debian-live@lists.debian.org.›
> >
> >
> > please, just fix it ;)
>
> This is a valid email adress AFAIK.
>
> You mail client is bogus.
>
> Thanks
>
> Michal
>
>
> --
> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> http://lists.debian.org/caomqctrjdy4ao7+_96bzwy+qd+vsmgjhbkoq5pobzfamowm...@mail.gmail.com
>
>

Re: apt-get install "Failed to fetch" "404 Not Found" IP ...

[Michael .]

Without some access to a repository you will not be able to obtain packages
to install them. If they are available online as updates it is recommended
that you install them, especially security updates, at the time they are
obtained. Updates are updates for a reason, they either fill in a security
flaw or they fix a bug or functionality.

So you have 3 options
1. connect to the net.
2. obtain up to date discs each and every time an update is rolled out
(highly impractical)
3. use something like apt-offline.

Cheers

On 6 May 2017 at 21:31, Albretch Mueller  wrote:

>  For more than one good reason (among them an unreliable Internet
> connection at times or simply not wanting to go online)
>
>  I would like to run apt-get locally (or be able to functionally do
> the same using dpkg or whatever). This is what I have in mind:
>
>  1) use apt-get in simulate mode to know which files I need to install
> and in what order
>
>  2) fetch those files and keep them locally
>
>  3) install them locally whenever I need to
>
>  Most (all?) people simply go "sudo apt-get" under the assumption that
> the back end repositories will be fine etc.
>
>  Yes, I am trying to install stuff when I need it without having to
> connect to the Internet
>
>  How do you do this? What would be the pros and cons of doing things this
> way?
>
>  lbrtchx
>
>

Re: Current LiveCDs don't include UFW!

[Michael .]

Why UFW? There are other packages available what makes UFW so special?

On 28 May 2017 at 01:59, Anonymous  wrote:

> IMO it's important to include the UFW package on LiveCDs.
>
> Please consider adding it in future versions, thank you.
>
>

Re: Configuration - packages list etc. for current stable live ISO images

[Michael .]

I don't think the official iso images are built with Live Build anymore, I
think you'll find they are built with Live Wrapper.

On 26 June 2017 at 14:27, Phil Wyett  wrote:

> Hi,
>
> Call me blind. I have been looking for the configs in-order to
> replicate the official stable live ISO images builds with 'lb'. I have
> looked here and there on Alioth etc. and cannot seem to find them.
> Could someone point me in the right direction?
>
> Regards
>
> Phil
>
> --
> Playing the game for the games sake.
>
> Web: https://kathenas.org
>
> Twitter: kathenasorg
>
> Instagram: kathenasorg

Re: IMPORTANT: Do live Debian images have a future?

[Michael .]

I'm not a dev but I am a user and I do test so I'll add my bit here.

Let's be frank Live Wrapper only exists because of animosity within Debian
towards the originator of Live Build (and to be honest his own lack of
concern for what Debian required of Live Build). Live Wrapper was rushed
and was never going to be ready for Stretch and in hindsight it was a
little foolish to think it would be ready to build the types of images
Debian required. Live Build wasn't up to scratch but the UEFI support issue
has been fixed so what other issues are there with Live Build that makes it
unreasonable to use?

On 27 June 2017 at 00:08, Steve McIntyre  wrote:

> [ Note the cross-posting... ]
>
> Hey folks,
>
> Background: we released live images for Stretch using new tooling,
> namely live-wrapper. It is better than what we had before (live-build)
> in a number of ways, particularly in terms of build reliability and
> some important new features (e.g. UEFI support). But it's also less
> mature and has seen less testing. There have been bugs because of
> that. I have fixes for most of the ones I know about [1], and I'm
> still working on more bugfixes yet.
>
> While the bugs are annoying, what worries me more is that they were
> only spotted in release builds. There had been testing versions of
> live images available for multiple weeks beforehand, presumably with
> the same bugs included. (Almost) none of them reported. This shows
> that we don't have enough people using these live images and/or caring
> about filing bugs.
>
> We have a similar lack of involvement in terms of the content of the
> live images. As I said above, I'm happy that we now have a reliable
> tool for building our live images - that makes my life much
> easier. But I honestly have no idea if the multiple desktop-specific
> live images are actually reasonable representations of each of the
> desktops. For example, I *seriously* hope that normal KDE
> installations are not effected by #865382 like our live KDE
> images. Validation by the various desktop teams would be useful here.
>
> The current situation is *not* good enough. I ended up getting
> involved in live image production because the images needed making,
> and I was already the main person organising production of Debian's
> official images. To be frank, I had (and still have) no direct use for
> the live images myself and I don't *particularly* care about them all
> that much. Despite that, I've ended up spending a lot of time working
> on them. A few other people have also spent a lot of time working in
> this area - thanks are due to those people too. But it's still not
> enough.
>
> If our live images are going to be good enough to meet the standards
> that Debian users deserve and expect, we need *consistent*,
> *sustained* involvement from a lot more people. Please tell me if
> you're going to help. If we don't see a radical improvement soon, I'll
> simply disable building live images altogether to remove the false
> promises they're making.
>
> [1] https://get.debian.org/images/release/current-live/amd64/
> iso-hybrid/#issues
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> "...In the UNIX world, people tend to interpret `non-technical user'
>  as meaning someone who's only ever written one device driver." -- Daniel
> Pead
>

Re: IMPORTANT: Do live Debian images have a future?

[Michael .]

Charles, let me clear up a couple of misconceptions for you. Debian Live
(made with Live Wrapper) is an official Debian project. Live Build (the old
Debian Live) apparently wasn't official but was recognised by Debian for
its official images. Live Build is now officially part of Debian and Rafael
Hertzog is the new developer maintainer of Live Build. As for reporting
bugs because Debian Live (that uses Live Wrapper) is an official Debian
project bugs should be reported through the bug tracker. That is the way it
has been since Live Wrapper was first released. However people still do,
and I have done it also, report issues with Live Wrapper in the Live
mailing list. Hope that helps.

On 27 June 2017 at 21:54, Charles Chambers  wrote:

> And I'll add my 2¢ as an end user.
>
> The live images exist IMHO to test compatibility before committing to
> installation, and to install what was just tested and demonstrated,
> regardless of environment.   It's a nice feature (arguably an essential
> feature) that the actual install mirror *exactly* the tested compatibility
> and appearance.  To go with this, it *was* nice to be able to install in
> the absence of a network connection or Internet service.
>
> The Live environment still works fine for testing for compatibility,
> especially when the Nonfree repository is included.  Installation, no
> longer.
>
> My 2¢ is that installation suffers from a lack of testing, probably
> because Debian Live is a "unofficial" branch off the development tree.
> It's made worse because bugs for Live have no clear reporting process.
> Where DOES one report a problem - to this mailing list, or the mailing list
> more obviously suited (think a bug found while installing...report here, or
> report to debian-install, or to debian-boot)?
>
> Inquiring minds want to know! 
>
> Charlie
>
>
>
> On Jun 26, 2017 12:55 PM, "Michael ."  wrote:
>
>> I'm not a dev but I am a user and I do test so I'll add my bit here.
>>
>> Let's be frank Live Wrapper only exists because of animosity within
>> Debian towards the originator of Live Build (and to be honest his own lack
>> of concern for what Debian required of Live Build). Live Wrapper was rushed
>> and was never going to be ready for Stretch and in hindsight it was a
>> little foolish to think it would be ready to build the types of images
>> Debian required. Live Build wasn't up to scratch but the UEFI support issue
>> has been fixed so what other issues are there with Live Build that makes it
>> unreasonable to use?
>>
>> On 27 June 2017 at 00:08, Steve McIntyre  wrote:
>>
>>> [ Note the cross-posting... ]
>>>
>>> Hey folks,
>>>
>>> Background: we released live images for Stretch using new tooling,
>>> namely live-wrapper. It is better than what we had before (live-build)
>>> in a number of ways, particularly in terms of build reliability and
>>> some important new features (e.g. UEFI support). But it's also less
>>> mature and has seen less testing. There have been bugs because of
>>> that. I have fixes for most of the ones I know about [1], and I'm
>>> still working on more bugfixes yet.
>>>
>>> While the bugs are annoying, what worries me more is that they were
>>> only spotted in release builds. There had been testing versions of
>>> live images available for multiple weeks beforehand, presumably with
>>> the same bugs included. (Almost) none of them reported. This shows
>>> that we don't have enough people using these live images and/or caring
>>> about filing bugs.
>>>
>>> We have a similar lack of involvement in terms of the content of the
>>> live images. As I said above, I'm happy that we now have a reliable
>>> tool for building our live images - that makes my life much
>>> easier. But I honestly have no idea if the multiple desktop-specific
>>> live images are actually reasonable representations of each of the
>>> desktops. For example, I *seriously* hope that normal KDE
>>> installations are not effected by #865382 like our live KDE
>>> images. Validation by the various desktop teams would be useful here.
>>>
>>> The current situation is *not* good enough. I ended up getting
>>> involved in live image production because the images needed making,
>>> and I was already the main person organising production of Debian's
>>> official images. To be frank, I had (and still have) no direct use for
>>> the live images myself and I don't *particularly* care about them all
>>> that much. Despite

Re: No su

[Michael .]

Bug reports should be made via the normal Debian bug reporting system. Do
you have reportbug or reportbug-ng installed?

On 29 June 2017 at 11:35, Phil Wyett  wrote:

> Hi,
>
> I have built a raw disk via 'lwr -d stretch' and debian installed it
> via GUI option.
>
> Even having simple character only password only, I cannot 'su'.
>
> Are all others getting the same? Is there a bug report to play with on
> this one?
>
> Regards
>
> Phil
>
> --
> Playing the game for the games sake.
>
> Web: https://kathenas.org
>
> Twitter: kathenasorg
>
> Instagram: kathenasorg

Re: No su

[Michael .]

Read these pages
https://www.debian.org/Bugs/
https://www.debian.org/Bugs/Reporting

On 29 June 2017 at 12:18, Michael .  wrote:

> Bug reports should be made via the normal Debian bug reporting system. Do
> you have reportbug or reportbug-ng installed?
>
> On 29 June 2017 at 11:35, Phil Wyett  wrote:
>
>> Hi,
>>
>> I have built a raw disk via 'lwr -d stretch' and debian installed it
>> via GUI option.
>>
>> Even having simple character only password only, I cannot 'su'.
>>
>> Are all others getting the same? Is there a bug report to play with on
>> this one?
>>
>> Regards
>>
>> Phil
>>
>> --
>> Playing the game for the games sake.
>>
>> Web: https://kathenas.org
>>
>> Twitter: kathenasorg
>>
>> Instagram: kathenasorg
>
>
>

Re: IMPORTANT: Do live Debian images have a future?

[Michael .]

Thomas it is all fine and good to say  "(lets not go into details why this
happened)" but the details support the reality of the situation. Please
read (https://lists.debian.org/debian-live/2015/11/msg8.html) and see
where Iain says

>>It is worth noting that live-build is not a Debian project, it is an
external project that claims to be an official Debian project. This is
something that needs to be fixed.

My understanding come from the people who initiated the take over of
building live images. If I am wrong then so was Iain and you should have
been a part of the discussion back in November 2015 to clear it all up for
us.

I want Live-Wrapper to succeed (only because it is the official Debian Live
system) and I support it through testing it and reporting on things I have
found which would limit the audience who could use it but I also want
Live-Build to continue (because Live-Build is more suitable for a roll your
own images that derivatives would create).

I must admit I am concerned about this reluctance "to go into details".
This type of thing keeps people in the dark and that is something I do not
support. There is no need to go over all the details but at least provide
proof as I have done.

On 5 July 2017 at 08:34, Thomas Goirand  wrote:

> On 06/27/2017 11:53 PM, Michael . wrote:
> > Charles, let me clear up a couple of misconceptions for you. Debian Live
> > (made with Live Wrapper) is an official Debian project. Live Build (the
> > old Debian Live) apparently wasn't official but was recognised by Debian
> > for its official images. Live Build is now officially part of Debian
>
> Hum... You also have some misunderstanding here. Live-build has been
> packaged in Debian, and fully part of Debian for *years* (well before
> Raphael worked on it).
>
> What changed is that, since Daniel Baumann doesn't build the live images
> anymore (let's not go into details why this happened), Steve does it at
> the same time as other Debian images. It's now included in a single
> process of building images.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
>

Re: debian-9.0.0-amd64-netinst.iso

[Michael .]

Is Debian Live available as a netinst now?

On 16 July 2017 at 10:31, Tom & Karen Pino  wrote:

> The entire system is too screwy.  dbus is screwed.  Not worth messing with.
>
>
> On 07/15/2017 05:54 PM, Tom & Karen Pino wrote:
>
> Created a user and assigned passwords for that user and for root.
>
> Cleaned up the
> /etc/apt/sources.list
>
> Am going to try to boot the system.
>
> On 07/15/2017 05:41 PM, Tom & Karen Pino wrote:
>
> I have not finished checking this out but it can't be called a good
> outcome.
>
> I am running on a ASUS M5A99FX Pro R2.0 MB with a FX6300 cpu.
>
> ISO was good.  Went on the stick fine with dd.  Booted nicely.  I am
> running on legacy bios boot and had no problem booting to that.
>
> CPU started heating up - could tell by the whine of the fan that it was in
> the mid 50s (C) - normal is upper 20s low 30s.  But when the installer got
> to the actual install that dropped down to very nice (no whine) temps.
>
> Took nearly and hour to get the packages for a lxde install downloaded.
> Every thing went fine.
>
> Got to the "clean up" portion and the cpu freaked out system went down.
>
> I have not set up an IRC connection or would have gone there.  But figured
> I better get this out there somehow.
>
> Am going to see what happens in a chroot.  Suspect it is easily fixed.
> But the install didn't work right.
>
> This is quite an improvement over my recent attempts.  It booted, all menu
> entries were fine.
>
> Hardware and networking seemed to go fine.
>
> Partitioning was its usual solid self.  I was using existing partitions.
> This install is using a shared /home.  No encryption.
>
> I used the non graphic install used the default tasksel choices (used
> Lxde).
>
> --
>
>
>
>

Re: Topic of this list (was: live-build: how to include .deb files not in any repository?)

[Michael .]

>>thanks so for jeesie and strech i must use live-wrpper and for squeeze
and wheeze i must use live-build

Live-Build is more suitable for everything up to but not including Stretch.
Having said that I don't see any complaints about Live images of Stretch
built using Live-Build not working.

Re: Install debian 9.1 live usb

[Michael .]

It is nice to know Rufus works with Live images built with live-wrapper now.
Rufus is a great application but from my understanding it was never
designed to prepare a usb for persistence.
To get persistence I suggest you look at either YUMI
 or the Arch
Linux wiki page on how to install an iso to usb and have persistence

Cheers

On 22 August 2017 at 07:47, A Abbes  wrote:

> Hello all!
>
>   thanks for the discussion, and the advice for remastering the iso. I did
> not know the method Thomas proposed, which seems quite elegant, it seems to
> be a good idea. Personaly, for remastering the iso, I used to mount it with
> -o,loop option, then cp it into a /mnt/foo folder, modified all I want, and
> finaly remaster it with the desired booting option.
>
> But my problem finaly moved to knowing how to manage the persistence.
>
>  I was on a hurry, and I finally performed a "hard install", as I expained
> in the preceding answer of the post.
>
>   Formerly, I used syslinux on the usb stick, and I cp the content of the
> iso on it. I just had to rename all the "isolinux" to "syslinux". Then i
> had to modify the options in the live.cfg file with the persistence
> options, and make a "live-rw" file or partition.
>
>   Now that it works with grub, and EFI, and that it is no more well
> documented, it is difficult to know how to do. I succeeded to install 9.1
> live on a stick with a nice automatic tool "rufus" (https://rufus.akeo.ie/),
> that works quite well, but does not manage persistence. I found the config
> file as /boot/grub/grub.cfg.
>
>   I append a "persistence" option in one menu entry. Then created a
> partition called "persistence". But I am not sure of the defaut name of the
> persistence partition, of file, and even of the option to put.
>
>   Is there a documentation of the actual live system?
>
> Regards,
>
>
>
>
> Le 14/08/2017 à 17:12, Thomas Schmitt a écrit :
>
>> Hi,
>>
>> A Abbes wrote:
>>
>>> I cannot modify the grub.cfg file to allow persistence.

>>> Meanwhile we had the proposal to remaster the ISO and the proposal
>> to install a normal Debian to a separate USB stick.
>> (For the latter Debian 9 Live ISOs have earned a bad reputation on
>>   debian-user mailing list. So they could well need more practicing.)
>>
>> There is also the method of creating a new partition on the USB stick
>> after the ISO end. It would get a read-write filesystem (e.g. ext2)
>> and would possibly be mapped over the ISO as overlay filesystem.
>> Knoppix does it that way.
>>
>> I skip the fourth opportunity: Patching of existing data files while
>> maintaining their sizes. That's binary hacking.
>>
>> Number five is ISO 9660 Multi-session.
>>
>>
>> Andreas Heinlein wrote:
>>
>>> There are tools which would allow you to modify the ISO file, but it's
>>> rather complicated.
>>>
>> Not too complicated but not necessarily what one wants. :))
>>
>> By ISO 9660 multi-session the ISO gets appended a new superblock, a new
>> directory tree, and the content blocks of the changed data files.
>> Depending on the medium type, the superblock at the start of the medium
>> (or image file) needs to be overwritten. On write-once multi-session media
>> Linux will mount the superblock of the youngest hardware session.
>>
>> One will in any case want to do all intended changes in one sweep,
>> although one can add more than one session.
>>
>> The main difficulty is to keep all the boot starting points working.
>> Because it is so nicely small, i practice with a netinst ISO image:
>>
>>cp debian-9.1.0-amd64-netinst.iso test.iso
>>iso=test.iso
>>
>> or with USB stick /dev/sdc which already holds that ISO:
>>
>>dd if=debian-9.1.0-amd64-netinst.iso bs=1M of=/dev/sdc
>>iso=stdio:/dev/sdc
>># chmod yourself write permission to /dev/sdc or become superuser
>>
>> A session gets appended by:
>>
>>xorriso -dev "$iso" \
>>-map my_new_grub.cfg /boot/grub/grub.cfg \
>>-boot_image any replay
>>
>> Between the -map command and the -boot_image command there may be more
>> manipulation commands to put files into the ISO, or rename, or delete
>> them.
>>
>> With xorriso versions older than 1.4.2 one would use
>>-boot_image any keep
>> which is broken since 1.4.4, as i now learned. A simple intitialization
>> bug.
>> "replay" is smarter, anyways.
>> The version number is told by:
>>xorriso -version
>>
>>
>> Have a nice day :)
>>
>> Thomas
>>
>>
>

Bug#874527: live-build: Live installer creates duplicate sources: sources.list and sources.list.d/base.list

[Michael .]

Did you use the official Debian Live iso image or did you make your own?
The reason I ask is if you used the official image it would have been built
with Live-Wrapper not Live-Build.

On 7 September 2017 at 08:06, Alan Jenkins <
alan.christopher.jenk...@gmail.com> wrote:

> Package: live-build
> Severity: normal
>
> Dear Maintainer,
>
> I just installed Debian from the Live image for 9.1.0.
> I ended up with duplicate sources, which show up when apt-get downloads.
> I'm not familiar with the live-build chain, hopefully this is a sensible
> place
> to report it.
>
> I believe base.list is created by vmdebootstrap.
>
> I very much like having the deb.debian.org line on the running live image.
> But maybe it needs to be moved to /etc/apt/sources.list, so
> debian-installer
> will overwrite it and avoid annoying duplicates?  Maybe it's not so simple
> though, I dunno.
>
> Thanks
> Alan
>
>
> $ sudo apt-get update
> Ign:1 http://ftp.uk.debian.org/debian stretch InRelease
> Ign:2 http://deb.debian.org/debian stretch InRelease
> ...
>
> $ cat /etc/orig.apt/sources.list.d/base.list
> deb http://deb.debian.org/debian/ stretch main
> #deb-src http://deb.debian.org/debian/ stretch main
>
> $ cat /etc/orig.apt/sources.list
> #
>
> # deb cdrom:[Official Debian GNU/Linux Live 9.1.0 gnome 2017-07-23T01:42]/
> stretch main
>
> #deb cdrom:[Official Debian GNU/Linux Live 9.1.0 gnome 2017-07-23T01:42]/
> stretch main
>
> deb http://ftp.uk.debian.org/debian/ stretch main
> deb-src http://ftp.uk.debian.org/debian/ stretch main
>
> deb http://security.debian.org/debian-security stretch/updates main
> deb-src http://security.debian.org/debian-security stretch/updates main
>
> # stretch-updates, previously known as 'volatile'
> deb http://ftp.uk.debian.org/debian/ stretch-updates main
> deb-src http://ftp.uk.debian.org/debian/ stretch-updates main
>
>
>
> -- System Information:
> Debian Release: 9.1
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages live-build depends on:
> pn  debootstrap  
>
> Versions of packages live-build recommends:
> ii  apt-utils   1.4.7
> ii  cpio2.11+dfsg-6
> pn  live-boot-doc   
> pn  live-config-doc 
> pn  live-manual-html | live-manual  
> ii  wget1.18-5
>
> live-build suggests no packages.
>
>

Bug#874527: live-build: Live installer creates duplicate sources: sources.list and sources.list.d/base.list

[Michael .]

You have probably filed the bug report against the wrong package then.
I wonder if you can ask for the bug report to be changed from live-build to
live-wrapper or if you should ask for it to be closed and open a new one
against live-wrapper instead.

@ live developers, this shows how confusing the current "live" system is.
If I may make a suggestion, maybe someone needs to sit down and do an
indepth "live" bug reporting page so people know what packages do what jobs
and they can file their bug reports against the correct packages.

On 7 September 2017 at 17:40, Alan Jenkins <
alan.christopher.jenk...@gmail.com> wrote:

> On 07/09/2017, Michael .  wrote:
> > Did you use the official Debian Live iso image or did you make your own?
> > The reason I ask is if you used the official image it would have been
> built
> > with Live-Wrapper not Live-Build.
>
> Thanks!  I used the official image.
>
> > On 7 September 2017 at 08:06, Alan Jenkins <
> > alan.christopher.jenk...@gmail.com> wrote:
> >
> >> Package: live-build
> >> Severity: normal
> >>
> >> Dear Maintainer,
> >>
> >> I just installed Debian from the Live image for 9.1.0.
> >> I ended up with duplicate sources, which show up when apt-get downloads.
> >> I'm not familiar with the live-build chain, hopefully this is a sensible
> >> place
> >> to report it.
>

Re: How to request to include new packages in debian live images?

[Michael .]

I think, although I am happy to be proven wrong if I am wrong, that the
Live images are supposed to be exactly the same as what you would get if
you did a regular Debian CD/DVD install. If the packages aren't on the
regular install they won't be on the Live install either.

Can anyone confirm this either way?

On 21 September 2017 at 02:41, Andres Pavez  wrote:

> Hi,
> Quick question. How is the process to request to include packages into
> the official debian live images in all flavors?
> I want to request to include the packages cups (only cinnamond has it)
> and enscript (it isn't part of any image flavors)
> Thanks,
> --
> Andrés Pavez
>
>

Re: Can I install from Stretch or Buster Mate Live System?

[Michael .]

>>Is there a command I can run from these systems that will allow
installation to hard drive?
As Steve suggested there are options to install directly from the boot
menu.
When you get to the boot menu you will see what is there.

>>I find nothing on menus or desktop, and the package 'debian-installer'
seems not to be in the repository.
Before this can be answered properly what "live" system are you using? Are
you using the official system based on live-wrapper or are you using the,
now unofficial, system based on live-build?
Live Build had an option in the menu of the running live system, I am not
sure about live-wrapper though.
Debian Installer, or d-i, is a script that answers questions or prompts the
person to answer questions so the system can be installed.

>> Also, if I have the assistive technologies and orca screen readers set
to run at start, will the installed system have accessibility at start?
Not on first start but if you set it up to run at start after that it
should work. In live-build you could probably get it to run on first boot,
I don't know about live-wrapper.

On 5 October 2017 at 03:35, Steve McIntyre  wrote:

> On Wed, Oct 04, 2017 at 12:28:42PM -0400, Dave Hunt wrote:
> >Is there a command I can run from these systems that will allow
> installation
> >to hard drive?  I find nothing on menus or desktop, and the package
> >'debian-installer' seems not to be in the repository.  Also, if I have the
> >assistive technologies and orca screen readers set to run at start, will
> the
> >installed system have accessibility at start?
>
> There are options to install directly from the boot menu on those live
> images.
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> < liw> everything I know about UK hotels I learned from "Fawlty Towers"
>
>

Re: Can I install from Stretch or Buster Mate Live System?

[Michael .]

>>I used the current live build with non-free firmware.

Can you provide a link where you got this or did you build it yourself?


>>I can run orca on the running live system, but the boot menu is inaccessible.

How do you run the live system if the boot menu isn't accessible? It
must just be timing out or something and booting straight into it.


>>I'm trying the live because I cannot get sound on the net install.

Have you got sound on the live system when it is running? If yes it's
probably due to non-free firmware being available.


On 5 October 2017 at 08:10, Dave Hunt  wrote:

> Hi,
>
> Thanks for the information.  I used the current live build with non-free 
> firmware.  I can run orca on the running live system, but the boot menu is 
> inaccessible.  I'm trying the live because I cannot get sound on the net 
> install.
>
>
> Thanks,
>
>
> Dave
>
>
>
>
>

Re: Debian-live manual: bad advice and bad URL

[Michael .]

Hi Lou

The Live Manual (that is a live-build, not live-wrapper, package) wasn't
written for official stretch based releases. The reason for this is
official stretch live releases are built with live-wrapper not live-build.
I, personally, believe the "live manual" should be re-written and note the
differences between the 2 build systems. Last time I looked the official
documentation for live-wrapper was extremely minimal so it could certainly
do with some work and, in order to stop alot of what I see as confusion
because people keep talking about current debian live as though it is
live-build based and not live-wrapper based, including both systems in it
would be very helpful.

Cheers.

On 3 November 2017 at 07:14, Lou Poppler  wrote:

> I would like to point out 2 small corrections to the debian-live manual
> http://debian-live.alioth.debian.org/live-manual/stable/
> manual/html/live-manual.en.html
>
> At this point I am far from able to create and commit changes myself,
> so I offer them to this list, hoping someone else might propagate them.
>
> In section 4.2 the URL given for older, upcoming, and unofficial live
> images
> http://debian-live.alioth.debian.org/cdimage/release/
> is 404.  I would suggest instead listing this URL:
> https://cdimage.debian.org/cdimage/
>
> In section 4.5.3 the suggestion for adding a partition to extra space at
> the end of a live image USB stick says to use parted or Gparted.
> For the current live images, with a xorisso-style partition layout,
> (for example the file debian-live-9.2.0-amd64-kde+nonfree.iso)
> parted (as of 3.2-17) and gparted (as of 0.25.0-1+b1) do not detect
> the first partition, containing the entire .iso, they only notice
> the small 500KB EFI partition 2, embedded inside it.  They see the
> first partition as empty space, and will allow using the space after
> partition 2 in creating a new partition 3.  Thus these programs are
> no longer appropriate in this case.  Regular old fdisk (as of 2.29.2-1)
> works correctly for this; gnome-disks (as of 3.22.1-1) works correctly
> for this.  These 2 would be good suggestions for this section of the
> webpage.  I also checked KDE partitionmanager (as of 3.0.0-1) and it
> does not see the partition 1, and incorrectly offers to include part
> of it in a new partition, like parted on which it is based I think.
>
> Thanks to anyone who can help update this documentation.
>
>

Re: Getting "failed to fetch - 404 Not Found" for stretch-backports packages when using live-build, but worked fine before 9.Nov.2017 - any idea why?

[Michael .]

To the best of my knowledge that backports sources.list is incorrect.
I have http://ftp.debian.org/debian stretch-backports in my current
sources.list

On 10 November 2017 at 09:51, Karen Gabrielyan <
karen.gabriel...@fixmestick.com> wrote:

>
> Hi,
>
> I'm wondering if anyone else is running into live-build problems like
> below as of 9.Nov?
> Do you guys know how this can be resolved?
>
> The URLs for backports are auto-generated by live-build through specifying
> distribution as "stretch" and asking for backports (--backports true)
>
>
> W: The repository 'http://backports.debian.org/debian-backports
> stretch-backports Release' does not have a Release file.
> E: Failed to fetch http://backports.debian.org/debian-backports/dists/
> stretch-backports/non-free/source/Sources  404  Not Found
> E: Failed to fetch https://backports.debian.org/debian-backports/dists/
> stretch-backports/contrib/source/Sources  404  Not Found
> E: Failed to fetch https://backports.debian.org/debian-backports/dists/
> stretch-backports/main/binary-i386/Packages  404  Not Found
>
>
>
>
> I was able to build things properly before, but now consistently get these
> errors.
>
> For reference, the for the "lb config" command I use backports=true :
>
> lb config noauto \
> --distribution "stretch" \
> --parent-distribution "stretch" \
> --backports true \
> --clean \
> --ignore-system-defaults \
> --mode "debian" \
> --initsystem systemd \
> --initramfs live-boot \
> --compression lzip \
> --debian-installer false \
> --firmware-chroot false \
> --apt-indices false \
> --apt-recommends false \
> --apt-secure false \
> --memtest none \
> --security true \
> --linux-packages "linux-image linux-headers" \
> --archive-areas "main contrib non-free"
>
>
> Thanks,
> Karen
>

Re: Multiarch live CDs

[Michael .]

Live wrapper has replaced live build for official images.
Live build is still being maintained by a Debian Developer (Raphael) and is
being used by the wider community and many Debian based offshoots.
The link you provided for multiarch is a netinst image not a live image. As
far as I am aware Debian has never released a multiarch live image but I am
happy to be proven wrong.
Building a multiarch live image with live build may be possible but you
will need 2 different squashfs filesystems at the very least. It is
something I have wanted to try but have never had the time to sit down and
work out all the different requirements.

On 13 November 2017 at 09:02, Borden Rhodes  wrote:

> On 12 November 2017 at 09:32, Andreas Heinlein  wrote:
> > Am 12.11.2017 um 08:38 schrieb Borden Rhodes:
> >> There were days, about a year ago, when I could write in auto/config:
> >>
> >> --architectures 'i386'
> >> --linux-flavours 'amd64 686-pae'
> >>
> >> And this made me happy because I could generate an image that ran
> >> natively on both 32 and 64-bit processors (every now and then I run
> >> into a 32-bit processor I want to run this live CD on). However, now
> >> when I run lb build, I eventually get the error message:
> >>
> >> Couldn't find any package whose name or description matched
> "linux-image-amd64"
> >>
> >> Which, I think, makes sense because it's looking for the amd64 kernel
> >> package in the i386 architecture but it obviously doesn't exist.
> >>
> >> I'm pretty sure that it's still possible to build multi-arch live CDs
> >> because this page exists:
> >> https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/ .
> >> Unfortunately, I can't find where in
> >> https://anonscm.debian.org/cgit/debian-live/ the auto/config file is
> >> hiding to copy its settings.
> >>
> >> Therefore, I'd like guidance on either:
> >> 1) How to build a multiarch live CD (specifically, that runs natively
> >> on 32 and 64-bit processors); or
> >> 2) Where to find the auto/config and config files for the
> >> multi-arch/iso-cd file so I can learn how it accomplishes this feat,
> >> if it does at all.
> >>
> >> With thanks,
> >>
> > I am afraid I cannot help you with the actual problem, but for
> > clarification: Live CDs for Debian 9 are no longer built with
> > live-build, but with a different package named live wrapper. That's why
> > you will not find any auto/config file for the current 'official'
> > multi-arch CDs.
>
> I read in the git repos that live-wrapper is the "next generation' way
> of generating images. The documentation still seems to be for
> live-build and I couldn't find live-wrapper docs online. Is
> live-wrapper going to replace live-build in the future?
>
> > If I understand it right, you want a 64bit kernel with a 32bit userland,
> > correct? That should still be possible by using a hook, but it is going
> > to be a bit complicated, I guess. Maybe someone else here on the list
> > has already done that.
>
> The short answer to your question is 'yes'. I'm designing this boot
> disk for house-call troubleshooting. I'll normally run the 64-bit
> operating system but, in the few times I run into old processors, I'll
> need to run a 32-bit OS. The long answer is 'I'd like both package
> sets installed so I can choose which to run'. When my auto/config file
> worked, I believe it was running a 32 userland on top of a 64 kernel
> when I opted for 64-bit mode.
>
> > Bye,
> >
> > Andreas
> >
>
> I'm much obliged for your assistance.
>
> With thanks,
>
>

Re: Debian live stable images with just console and software speech using espeakup

[Michael .]

If you use Debian then you can make one yourself using live-build. If
you don't use Debian then you may want to ask if someone can create an
iso image for you.

P.S. Sorry to Narcis for accidentally sending this reply just to him

On 25/12/2017, Narcis Garcia  wrote:
> Nick is asking for this:
> https://cdimage.debian.org/cdimage/archive/8.10.0-live/
>
>
>
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this mail public archive. Public archive administrator
> should fix this against automated addresses collectors.
> El 23/12/17 a les 21:10, Nick Gawronski ha escrit:
>> Hi, I was looking for a Debian live disc that is just for console use for
>> doing things like copying off files and installing a basic console Debian
>> system using software speech.  I searched the Debian live project but
>> could not find just console images they all had a desktop on them which I
>> don't need.  Could this be looked into for times where a minimal live
>> disc
>> is needed?  Nick Gawronski
>>
>
>

Re: Reproducing unofficial weekly images?

[Michael .]

Hi Leandro
The simplest way, for me, to do what you are asking about is to
download the zip or tar.gz for the distribution you require from
https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/ Once
you have done that unpack it into your live-build environment
(config/includes.binary/firmware) before you start the build process.
This will then put the non-free firmware packages into the firmware
folder of the iso root directory so that when you boot from the iso
d-i will look for and find the required firmware and install it so you
can get your non-free hardware working.
Cheers.
Michael.

On 24/03/2018, Leandro Doctors  wrote:
> (Please reply with CC to be, as I am not on the list)
>
>
> Dear all,
>
> I am learning to build Debian Live images using live-build.
>
> Based on the examples published by your project, I have managed to
> replicate some weekly generated images (such as "gnome-desktop", based
> on the scripts available in [0]).
>
> [0]:
> https://salsa.debian.org/live-team/live-images/tree/debian/images/gnome-desktop
>
>
> My next step is to reproduce the unofficial images from [1].
>
> [1]:
> https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/weekly-live-builds/amd64/iso-hybrid/
>
>
> Could anyone be so king to tell me where could I get the corresponding
> scripts, please? (As they are unofficial, they are logically
> unavailable from the official repo.)
>
> Specifically, I would like to know whether there is a meta-package or
> task that would allow me to include "all non-free firmware", so I can
> make sure the system will boot and its Wi-Fi will work in most
> computers where I may use it.
>
>
> Thank you in advance for your reply.
>
> Best,
> Leandro
>
>

Re: Reproducing unofficial weekly images?

[Michael .]

Choose what works for you and let us know how you go. The way I do it
is" valid" everytime I do a new build because the files are already in
the config tree and all I need to do is lb clean, lb config, lb build
and it just works. I don't get the files for each build, I get them
once and put them in my config.

I tried the auto/config method years ago and it just wouldn't work,
that is the reason I do it the way I do it.

Also you shouldn't need both --firmware-binary true   \ and
--firmware-chroot true \ in the same auto/config. The chroot (or live
image) should detect the files are available in the binary (iso image)
and use them. If you do both you are actually putting the files in
both file systems and that is doubling up. Choosing one or the other
should suffice but having said that using it never worked properly for
me no matter what options I chose, and I chose all options until I
started doing it the way I currently do it.

Cheers.
Michael.

On 25/03/2018, Leandro Doctors  wrote:
> On 25 March 2018 at 03:45, John Crawley (johnraff) 
> wrote:
>> On 24 March 2018 at 07:13, Michael .  wrote:
>> >
>> > The simplest way, for me, to do what you are asking about is to
>> > download the zip or tar.gz for the distribution you require from
>> > https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/ Once
>> > you have done that unpack it into your live-build environment
>> > (config/includes.binary/firmware) before you start the build process.
>>
>>
>> Live-build's auto/config file allows the options:
>> --firmware-binary true \
>> --firmware-chroot true \
>>
>> I think those will cause all the available firmware to be installed in
>> the
>> Debian installer and the installed system.
>
> Dear Michael and John,
>
> Thank you both very much for your answers!
>
> Unfortunately Michael's proposal would be valid only once.
> So, I will try John's one and get back to you about my experience.
>
> Even though I had already seen the options in the documentation, from
> reading it I could not get that it referred to non-free firmware.
> (Chances are I will also have to specify "non-free" as a source for
> packages...)
>
> Just a friendly reminder: If someone has another suggestion, please
> remember to CC to me, as I am not on the list.
>
> Best,
> Leandro
>
>

Re: Boot .iso with GRUB2

[Michael .]

There was a thread on Linux Questions years ago about this exact
topic. I managed to get Grub to boot multiple Debian Live iso images
but ended up testing various applications from Pendrive Linux simply
because everything was automated. I haven't tried with the new iso
made with Live Wrapper so there may be a few differences.

On 06/04/2018, Thomas Schmitt  wrote:
> Hi,
>
> Narcis Garcia wrote:
>> I've tried this with no luck:
>> iso_path="/debian-live-9.4.0-amd64-gnome.iso"
>>   linux  /live/vmlinuz-4.9.0-6-amd64 boot=live components
>> "${loopback}"
>>   initrd /live/initrd.img-4.9.0-6-amd64
>>
>> Results in:
>> [...] ... mounted filesystem...
>
> So GRUB obviously found the ISO and started the kernel with that initrd.
>
>
>> (initramfs) Unable to find a medium containing a live file system
>
> A possible emitter of this message is in the initrd inside the ISO.
>
>   gunzip < /mnt/iso/live/initrd.img-4.9.0-6-amd64 | strings | less
>
> produces the string
>   Unable to find a medium containing a live file system
> and leads me via "livefs_root", "find_livefs", "check_dev" to
>   fromiso=
>
> Dunno whether
>   https://manpages.debian.org/testing/live-boot-doc/live-boot.7.en.html
> is applicable to debian-live-9.4.0-amd64-gnome.iso, but it has
>
>   findiso=/PATH/TO/IMAGE
> Look for the specified ISO file on all disks where it usually looks
> for the .squashfs file (so you don't have to know the device name
> as in fromiso=).
>
>   fromiso=/PATH/TO/IMAGE
> Use a filesystem from within an ISO image that's available on
> live-media.
>
> If this does not yield insight, then one will have to unpack the compressed
> cpio archive initrd.img-4.9.0-6-amd64, to identify the script that bears
> the
> code about "Unable to find a medium containing a live file system", and
> to find out how to make it accept a ISO image file instead of e.g. a CD-ROM
> device.
>
>
> Have a nice day :)
>
> Thomas
>
>

Re: Changes to consider for debian-live (calamares and gparted)

[Michael .]

I agree with adding gparted but what does Calamares do that graphical
d-i doesn't?
Cheers

On 22/05/2018, Jonathan Carter  wrote:
> Hi Richard
>
> On 21/05/2018 17:50, Richard Owlett wrote:
>> As to Calamares, what might it look like to the end-user?
>> [https://calamares.io/] gives no hint.
>
> Ah yes, so, here's the installation instructions for AIMS Desktop, a
> derivative I work on that happens to have some nice screenshots of
> calamares:
>
> https://desktop.aims.ac.za/getting-started/
>
> Then I also quickly threw together a 3 minute video on how calamares
> looks on Debian:
>
> https://highvoltage.tv/media/quick-calamares-demo-for-debian-live-mailing-list
>
> HTH,
>
> -Jonathan
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
>   ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
>   ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
>   ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.
>
>

New install of Live Build on Buster E: debootstrap - command not found

[Michael .]

Hi.
Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output

root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb clean
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb config
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb build
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
/usr/lib/live/build/bootstrap: 35: /usr/lib/live/build/bootstrap:
chroot: not found
root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386#

As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test run). I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

>From memory live-build used to detect the version it was installed on
and build an iso based on that unless it had been told to do something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.

Cheers.
Michael.

Re: New install of Live Build on Buster E: debootstrap - command not found

[Michael .]

Hi everyone
Usually I think when there is no reply to a question people don't know
the answer and I am sure this is probably the case here but this is a
crippling issue for me. It has literally stopped me dead in my tracks.
I don't really want to have to go back to Stretch if I can help it. If
anyone is using an up to date Buster (current testing) system to use
Live Build successfully please let me know otherwise I'll assume Live
Build isn't suitable for Buster and I will revert back to Stretch.
Cheers.
Michael.

>>Hi.
Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output

root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb clean
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb config
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb build
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
/usr/lib/live/build/bootstrap: 35: /usr/lib/live/build/bootstrap:
chroot: not found
root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386#

As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test run). I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

>From memory live-build used to detect the version it was installed on
and build an iso based on that unless it had been told to do something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.

Cheers.
Michael.

Re: New install of Live Build on Buster E: debootstrap - command not found

[Michael .]

Thank you for your reply Luca, now I know it should be working.
As I said in my original message it was a totally new install and
everything was new. I purged the system of live-* packages and
reinstalled them only to have the problem again. I have done the same
thing this morning and still get the same issue. I will continue to
work on it now I know it should be working and when I find what the
issue is I will report back.
Cheers.
Michael.

On 06/11/2018, Luca Boccassi  wrote:
> Just tried on a sid chroot, it seems to work just fine, so I'd suggest
> to check your configuration:
>
> # lb clean
> [2018-11-05 22:29:13] lb clean
> P: Executing auto/clean script.
> [2018-11-05 22:29:13] lb clean noauto
> P: Cleaning chroot
> # lb config
> [2018-11-05 22:29:15] lb config
> P: Executing auto/config script.
> [2018-11-05 22:29:15] lb config noauto --apt apt --apt-recommends false
> --apt-indices false --apt-source-archives false --apt-options --yes -o
> Acquire::Check-Valid-Until=false --bootappend-live boot=live components
> splash username=root console=tty0 console=ttyS0 --bootappend-live-
> failsafe boot=live components username=root debug live-boot.debug
> memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
> vga=normal console=tty0 console=ttyS0 --bootloaders syslinux,grub-efi
> --cache-indices false --checksums md5 sha256 --chroot-filesystem
> squashfs --debconf-frontend noninteractive --distribution stable --
> parent-distribution stable --firmware-binary false --firmware-chroot
> false --ignore-system-defaults --image-name standard_20181105T2229 --
> initramfs live-boot --linux-flavours amd64 --mode debian --source false
> --security true --updates true --backports false --verbose --onie true
> --onie-kernel-cmdline systemd.show_status=1 net.ifnames=1
> P: Updating config tree for a debian/stable/amd64 system
> P: Symlinking hooks...
> # lb build
> [2018-11-05 22:29:17] lb build
> P: Executing auto/build script.
> [2018-11-05 22:29:17] lb build noauto
> P: live-build 1:20180925
> P: Building config tree for a debian/stable/amd64 system
> [2018-11-05 22:29:17] lb bootstrap
> P: Setting up cleanup function
> [2018-11-05 22:29:17] lb bootstrap_cache restore
> P: Restoring bootstrap stage from cache...
> [2018-11-05 22:29:17] lb bootstrap_debootstrap
> P: Begin bootstrapping system...
> P: If the following stage fails, the most likely cause of the problem
> is with your mirror configuration or a caching proxy.
> P: Running debootstrap (download-only)...
> I: Retrieving InRelease
> I: Retrieving Release
> I: Retrieving Release.gpg
> I: Checking Release signature
> I: Valid Release signature (key id
> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
> I: Retrieving Packages
> I: Validating Packages
> I: Resolving dependencies of required packages...
> I: Resolving dependencies of base packages...
>
> On Tue, 2018-11-06 at 09:08 +1100, Michael . wrote:
>> Hi everyone
>> Usually I think when there is no reply to a question people don't
>> know
>> the answer and I am sure this is probably the case here but this is a
>> crippling issue for me. It has literally stopped me dead in my
>> tracks.
>> I don't really want to have to go back to Stretch if I can help it.
>> If
>> anyone is using an up to date Buster (current testing) system to use
>> Live Build successfully please let me know otherwise I'll assume Live
>> Build isn't suitable for Buster and I will revert back to Stretch.
>> Cheers.
>> Michael.
>>
>> > > Hi.
>>
>> Haven't been around for a while because I haven't come across any
>> issues, until now. Not sure if this is a bug or if something else is
>> causing this but on a new (everything is new) install of Buster and
>> Live-Build I am getting this output
>>
>> root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb
>> clean
>> [2018-09-17 07:41:21] lb clean
>> P: Executing auto/clean script.
>> [2018-09-17 07:41:21] lb clean noauto
>> P: Cleaning chroot
>> root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb
>> config
>> [2018-09-17 07:41:26] lb config
>> P: Updating config tree for a debian/stretch/amd64 system
>> P: Symlinking hooks...
>> root@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb
>> build
>> [2018-09-17 07:41:36] lb build
>> P: Executing auto/build script.
>> [2018-09-17 07:41:36] lb build noauto
>> P: live-build 1:20180618
>> P: Building config tree for a debian/stretch/amd64 system
>> [2018-09-17 07:41:36] lb bootstrap
>> P: Setting up cleanup function
>> [2018-09-17 07:41:36] lb bootstrap_cache rest

Re: New install of Live Build on Buster E: debootstrap - command not found

[Michael .]

Ok I thought I'd go through the process again, without reinstalling
the OS itself, and this is the outcome. Everything done via command
line instead of creating the folders via the file manager.

michael@michael-desktop:~$ cat /etc/debian_version
buster/sid
michael@michael-desktop:~$ mkdir LiveBuild
michael@michael-desktop:~$ cd LiveBuild
michael@michael-desktop:~/LiveBuild$ mkdir x86-64
michael@michael-desktop:~/LiveBuild$ cd x86-64
michael@michael-desktop:~/LiveBuild/x86-64$ su
Password:
root@michael-desktop:/home/michael/LiveBuild/x86-64# lb clean
[2018-11-06 10:12:57] lb clean
P: Cleaning chroot
root@michael-desktop:/home/michael/LiveBuild/x86-64# lb config
[2018-11-06 10:13:03] lb config
P: Creating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
root@michael-desktop:/home/michael/LiveBuild/x86-64# lb build
[2018-11-06 10:13:12] lb build
P: live-build 1:20180925
P: Building config tree for a debian/stretch/amd64 system
[2018-11-06 10:13:12] lb bootstrap
P: Setting up cleanup function
[2018-11-06 10:13:12] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-06 10:13:12] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
/usr/lib/live/build/bootstrap: 35: /usr/lib/live/build/bootstrap:
chroot: not found
root@michael-desktop:/home/michael/LiveBuild/x86-64#

Totally new folders, totally new config created by Live Build itself.
My system is Buster but Live Build is reverting to Stretch. I believe
this is what is causing the problem.


On 06/11/2018, Michael .  wrote:
> Thank you for your reply Luca, now I know it should be working.
> As I said in my original message it was a totally new install and
> everything was new. I purged the system of live-* packages and
> reinstalled them only to have the problem again. I have done the same
> thing this morning and still get the same issue. I will continue to
> work on it now I know it should be working and when I find what the
> issue is I will report back.
> Cheers.
> Michael.
>
> On 06/11/2018, Luca Boccassi  wrote:
>> Just tried on a sid chroot, it seems to work just fine, so I'd suggest
>> to check your configuration:
>>
>> # lb clean
>> [2018-11-05 22:29:13] lb clean
>> P: Executing auto/clean script.
>> [2018-11-05 22:29:13] lb clean noauto
>> P: Cleaning chroot
>> # lb config
>> [2018-11-05 22:29:15] lb config
>> P: Executing auto/config script.
>> [2018-11-05 22:29:15] lb config noauto --apt apt --apt-recommends false
>> --apt-indices false --apt-source-archives false --apt-options --yes -o
>> Acquire::Check-Valid-Until=false --bootappend-live boot=live components
>> splash username=root console=tty0 console=ttyS0 --bootappend-live-
>> failsafe boot=live components username=root debug live-boot.debug
>> memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
>> vga=normal console=tty0 console=ttyS0 --bootloaders syslinux,grub-efi
>> --cache-indices false --checksums md5 sha256 --chroot-filesystem
>> squashfs --debconf-frontend noninteractive --distribution stable --
>> parent-distribution stable --firmware-binary false --firmware-chroot
>> false --ignore-system-defaults --image-name standard_20181105T2229 --
>> initramfs live-boot --linux-flavours amd64 --mode debian --source false
>> --security true --updates true --backports false --verbose --onie true
>> --onie-kernel-cmdline systemd.show_status=1 net.ifnames=1
>> P: Updating config tree for a debian/stable/amd64 system
>> P: Symlinking hooks...
>> # lb build
>> [2018-11-05 22:29:17] lb build
>> P: Executing auto/build script.
>> [2018-11-05 22:29:17] lb build noauto
>> P: live-build 1:20180925
>> P: Building config tree for a debian/stable/amd64 system
>> [2018-11-05 22:29:17] lb bootstrap
>> P: Setting up cleanup function
>> [2018-11-05 22:29:17] lb bootstrap_cache restore
>> P: Restoring bootstrap stage from cache...
>> [2018-11-05 22:29:17] lb bootstrap_debootstrap
>> P: Begin bootstrapping system...
>> P: If the following stage fails, the most likely cause of the problem
>> is with your mirror configuration or a caching proxy.
>> P: Running debootstrap (download-only)...
>> I: Retrieving InRelease
>> I: Retrieving Release
>> I: Retrieving Release.gpg
>> I: Checking Release signature
>> I: Valid Release signature (key id
>> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
>> I: Retrieving Packages
>> I: Validating Packages
>> I: Resolving dependencies o

Re: New install of Live Build on Buster E: debootstrap - command not found

[Michael .]

Yes debootsrap is installed. I have purged it, as well as the Live
Build packages, and reinstalled it a couple of times.
Unfortunately I don't have time to work on this now and probably won't
until the weekend. Thanks for your suggestions so far.
Cheers,
Michael.

On 07/11/2018, Luca Boccassi  wrote:
> In a chroot:
>
> # mkdir lb
> # cd lb
> # lb clean
> [2018-11-06 16:54:35] lb clean
> P: Cleaning chroot
> # lb config
> [2018-11-06 16:54:38] lb config
> P: Creating config tree for a debian/stretch/amd64 system
> P: Symlinking hooks...
> # lb build
> [2018-11-06 16:54:40] lb build
> P: live-build 1:20180925
> P: Building config tree for a debian/stretch/amd64 system
> [2018-11-06 16:54:40] lb bootstrap
> P: Setting up cleanup function
> [2018-11-06 16:54:40] lb bootstrap_cache restore
> P: Restoring bootstrap stage from cache...
> [2018-11-06 16:54:40] lb bootstrap_debootstrap
> P: Begin bootstrapping system...
> P: If the following stage fails, the most likely cause of the problem
> is with your mirror configuration or a caching proxy.
> P: Running debootstrap (download-only)...
> I: Retrieving InRelease
> I: Retrieving Release
> I: Retrieving Release.gpg
> I: Checking Release signature
> I: Valid Release signature (key id
> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
> I: Retrieving Packages
> I: Validating Packages
> ...
>
>
> Are you sure you've got debootstrap installed? Can you run it manually?
>
> On Tue, 2018-11-06 at 10:18 +1100, Michael . wrote:
>> Ok I thought I'd go through the process again, without reinstalling
>> the OS itself, and this is the outcome. Everything done via command
>> line instead of creating the folders via the file manager.
>>
>> michael@michael-desktop:~$ cat /etc/debian_version
>> buster/sid
>> michael@michael-desktop:~$ mkdir LiveBuild
>> michael@michael-desktop:~$ cd LiveBuild
>> michael@michael-desktop:~/LiveBuild$ mkdir x86-64
>> michael@michael-desktop:~/LiveBuild$ cd x86-64
>> michael@michael-desktop:~/LiveBuild/x86-64$ su
>> Password:
>> root@michael-desktop:/home/michael/LiveBuild/x86-64# lb clean
>> [2018-11-06 10:12:57] lb clean
>> P: Cleaning chroot
>> root@michael-desktop:/home/michael/LiveBuild/x86-64# lb config
>> [2018-11-06 10:13:03] lb config
>> P: Creating config tree for a debian/stretch/amd64 system
>> P: Symlinking hooks...
>> root@michael-desktop:/home/michael/LiveBuild/x86-64# lb build
>> [2018-11-06 10:13:12] lb build
>> P: live-build 1:20180925
>> P: Building config tree for a debian/stretch/amd64 system
>> [2018-11-06 10:13:12] lb bootstrap
>> P: Setting up cleanup function
>> [2018-11-06 10:13:12] lb bootstrap_cache restore
>> P: Restoring bootstrap stage from cache...
>> [2018-11-06 10:13:12] lb bootstrap_debootstrap
>> E: debootstrap - command not found
>> I: debootstrap can be obtained from
>> http://ftp.debian.org/debian/pool/main/d/debootstrap/
>> I: On Debian based systems, debootstrap can be installed with 'apt-
>> get
>> install debootstrap'.
>> P: Begin unmounting filesystems...
>> P: Saving caches...
>> /usr/lib/live/build/bootstrap: 35: /usr/lib/live/build/bootstrap:
>> chroot: not found
>> root@michael-desktop:/home/michael/LiveBuild/x86-64#
>>
>> Totally new folders, totally new config created by Live Build itself.
>> My system is Buster but Live Build is reverting to Stretch. I believe
>> this is what is causing the problem.
>>
>>
>> On 06/11/2018, Michael .  wrote:
>> > Thank you for your reply Luca, now I know it should be working.
>> > As I said in my original message it was a totally new install and
>> > everything was new. I purged the system of live-* packages and
>> > reinstalled them only to have the problem again. I have done the
>> > same
>> > thing this morning and still get the same issue. I will continue to
>> > work on it now I know it should be working and when I find what the
>> > issue is I will report back.
>> > Cheers.
>> > Michael.
>> >
>> > On 06/11/2018, Luca Boccassi  wrote:
>> > > Just tried on a sid chroot, it seems to work just fine, so I'd
>> > > suggest
>> > > to check your configuration:
>> > >
>> > > # lb clean
>> > > [2018-11-05 22:29:13] lb clean
>> > > P: Executing auto/clean script.
>> > > [2018-11-05 22:29:13] lb clean noauto
>> > > P: Cleaning chroot
>> > > # lb config
>> > > [2018-11-05 22:29:15] lb config
>> > > P: Executing 

Re: New install of Live Build on Buster E: debootstrap - command not found

[Michael .]

Thank you eznix. Today is the 1st day since my last message I have had
an opportunity to look at this and it now works. I very much
appreciate your help.

On 12/11/2018, eznix  wrote:
> I too have experienced this problem. For me, the $PATH was the cause. When
> I su in Buster, my $PATH does not contain /sbin and /usr/sbin. debootstrap
> is in /usr/sbin/ and hence could not be found when running live-build when
> su'ing in the terminal. It worked perfectly when I exported /usr/sbin and
> /sbin into my $PATH. Live-build also worked perfectly when I su -l in the
> terminal. Hope this helps. It does not appear to be a live-build problem,
> but a $PATH problem.
>

Re: error live build with "method driver /usr/lib/apt/methods/https could not be found"

[Michael .]

Take a look at the Live Build manual here
https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html
and specifically this page
https://live-team.pages.debian.net/live-manual/html/live-manual/customizing-package-installation.en.html#446.
This should help you achieve what you are after.

On 17/05/2019, PICCORO McKAY Lenz  wrote:
> in the list to be used inside the chroot i configure the openbuild service
> repository.. that are https not just http so the when live-build go to the
> repositories configuration raise that error:
>
> P: Configuring file /etc/apt/sources.list
> E: The method driver /usr/lib/apt/methods/https could not be found.
> N: Is the package apt-transport-https installed?
> E: The method driver /usr/lib/apt/methods/https could not be found.
> N: Is the package apt-transport-https installed?
> P: Begin unmounting filesystems...
> P: Saving caches...
> Reading package lists... Done
> Building dependency tree... Done
>
> how can i include the apt-transport-https inside the pre installed chroot
> packge root to be able to use that repositories and not just only http
> repos?
>
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
>

Re: error live build with "method driver /usr/lib/apt/methods/https could not be found"

[Michael .]

Alot more information is required. What version of Debian are you
using? and what version of Debian are you trying to build? Conflicts
often happen if we are trying to build testing or Unstable, if that is
what you are doing you'll have to wait until the repository for the
dist you are building from has the conflicts sorted.

On 19/05/2019, PICCORO McKAY Lenz  wrote:
> Thanks, but i solved by parsing todebootstrap the packages to include.. BUT
> NOW HAVE CONFLICTS:
>
> The following packages have unmet dependencies:
>  courier-mta : Conflicts: mail-transport-agent
>  exim4-config : Conflicts: courier-mta but 0.73.1-1.6 is to be installed
>  exim4-daemon-light : Conflicts: mail-transport-agent
>  ifupdown : Breaks: systemd (< 228-3~) but 215-17+deb8u13 is to be
> installed
> E: Unable to correct problems, you have held broken packages.
> P: Begin unmounting filesystems...
> P: Saving caches...
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
>
>
> El vie., 17 de may. de 2019 a la(s) 05:17, Michael . (keltoi...@gmail.com)
> escribió:
>
>> Take a look at the Live Build manual here
>>
>> https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html
>> and specifically this page
>>
>> https://live-team.pages.debian.net/live-manual/html/live-manual/customizing-package-installation.en.html#446
>> .
>> This should help you achieve what you are after.
>>
>> On 17/05/2019, PICCORO McKAY Lenz  wrote:
>> > in the list to be used inside the chroot i configure the openbuild
>> service
>> > repository.. that are https not just http so the when live-build go to
>> the
>> > repositories configuration raise that error:
>> >
>> > P: Configuring file /etc/apt/sources.list
>> > E: The method driver /usr/lib/apt/methods/https could not be found.
>> > N: Is the package apt-transport-https installed?
>> > E: The method driver /usr/lib/apt/methods/https could not be found.
>> > N: Is the package apt-transport-https installed?
>> > P: Begin unmounting filesystems...
>> > P: Saving caches...
>> > Reading package lists... Done
>> > Building dependency tree... Done
>> >
>> > how can i include the apt-transport-https inside the pre installed
>> > chroot
>> > packge root to be able to use that repositories and not just only http
>> > repos?
>> >
>> >
>> > Lenz McKAY Gerardo (PICCORO)
>> > http://qgqlochekone.blogspot.com
>> >
>>
>

Bug#929271: backports customizations are not enabled for live-build

[Michael .]

Jessie security support ended June 17 2018. Asking the live project to
support a dist that is no longer security supported adds work to an
already huge workload.

On 22/05/2019, PICCORO McKAY Lenz  wrote:
> Roland, i track back all the history and get not lost.. BUT IN ANY CASE
> THAT BEHAVIOUR ARE NOT VIABLE, lest see:
>
> about the commits history: seems the migration was not as espected
> (migrations was done good but the results are not same as xpected)
>
> the commits are :
> https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2
>
> and also
> https://salsa.debian.org/live-team/live-build/commit/68700f466c142082e7423282ca4caaf7552bf8e9
>
> I EXPLAIN WHY THAT COMMITS MUST BE REVERTED
>
> 1. - the mirror are track from default mirror.. so oldstable moving of
> backports (as seems always) are not in same repository, that made this
> behaviour ilogic and ridiculus, due for olstable the repository will be
> archived .. same for updates repository!
>
> 2. -for low performance networks it's a good practice have differents
> mirrors so download task will be separatelly, i mean event have normal and
> backports in same domain.. i setup different origin domains sources for
> normal repository and backports repository... that's a good practice
>
> there's more reason but in my case those are enouoght
>
> Please therat that issue quick due i cannot build any jessie image property
> or i cannot use any strecth image in good shape!
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
>
>
> El mar., 21 de may. de 2019 a la(s) 02:38, Roland Clobus
> (rclo...@rclobus.nl)
> escribió:
>
>> Hello PICCORO,
>>
>> On 20/05/2019 15:42, PICCORO McKAY Lenz wrote:
>> > when try to build live jessie image using strecht i got those errors
>> >
>> > lb config: unrecognized option '--mirror-chroot-updates'
>> > lb config: unrecognized option '--parent-mirror-binary-updates'
>> > lb config: unrecognized option '--parent-mirror-chroot-updates'
>>
>> When working on the documentation, I've noticed these command line
>> options as well. They are not present in the scripts, they are only in
>> the documentation.
>> Unfortunately due to the migration from alioth to salsa the git history
>> got lost, so I cannot trace it back. I would assume that the
>> functionality was remove from the scripts at some time, and that someone
>> forgot to update the documentation accordingly. I've downloaded the
>> package 1:20151215 [1], and the command line is mentioned there also
>> only in the documentation, which confirms my assumption.
>>
>> Instead of (re-)implementing these options, I would update the
>> documentation instead.
>>
>> With kind regards,
>> Roland Clobus
>>
>> [1] https://snapshot.debian.org/package/live-build/1%3A20151215/
>>
>>
>>
>>
>

Bug#929271: backports customizations are not enabled for live-build

[Michael .]

I am sorry I obviously didn't pay attention when you said and I quote
"when try to build live jessie image using strecht i got those
errors".

On 22/05/2019, PICCORO McKAY Lenz  wrote:
> obviously you Maichael do not paid attention, i repeat:
>
> 1. the bug was reported agains strecht.. i cannot build strecht image using
> different mirrors for each case!
> 2. -for low performance networks it's a good practice have differents
> mirrors so download task will be separatelly,
> 3. docummentation are obviuslly out of date, script obvouslly are out of
> date, all are obviouslly out of sync
>
> in any case, that are ilogic, iu can provide different mirror for chroot
> installer and for booststrap but not for backports? PUFFF
>
> i mean event have normal and backports in same domain.. i setup different
> origin domains sources for normal repository and backports repository...
> that's a good practice
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
>
>
> El mar., 21 de may. de 2019 a la(s) 15:16, Michael . (keltoi...@gmail.com)
> escribió:
>
>> Jessie security support ended June 17 2018. Asking the live project to
>> support a dist that is no longer security supported adds work to an
>> already huge workload.
>>
>> On 22/05/2019, PICCORO McKAY Lenz  wrote:
>> > Roland, i track back all the history and get not lost.. BUT IN ANY CASE
>> > THAT BEHAVIOUR ARE NOT VIABLE, lest see:
>> >
>> > about the commits history: seems the migration was not as espected
>> > (migrations was done good but the results are not same as xpected)
>> >
>> > the commits are :
>> >
>> https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2
>> >
>> > and also
>> >
>> https://salsa.debian.org/live-team/live-build/commit/68700f466c142082e7423282ca4caaf7552bf8e9
>> >
>> > I EXPLAIN WHY THAT COMMITS MUST BE REVERTED
>> >
>> > 1. - the mirror are track from default mirror.. so oldstable moving of
>> > backports (as seems always) are not in same repository, that made this
>> > behaviour ilogic and ridiculus, due for olstable the repository will be
>> > archived .. same for updates repository!
>> >
>> > 2. -for low performance networks it's a good practice have differents
>> > mirrors so download task will be separatelly, i mean event have normal
>> and
>> > backports in same domain.. i setup different origin domains sources for
>> > normal repository and backports repository... that's a good practice
>> >
>> > there's more reason but in my case those are enouoght
>> >
>> > Please therat that issue quick due i cannot build any jessie image
>> property
>> > or i cannot use any strecth image in good shape!
>> >
>> > Lenz McKAY Gerardo (PICCORO)
>> > http://qgqlochekone.blogspot.com
>> >
>> >
>> > El mar., 21 de may. de 2019 a la(s) 02:38, Roland Clobus
>> > (rclo...@rclobus.nl)
>> > escribió:
>> >
>> >> Hello PICCORO,
>> >>
>> >> On 20/05/2019 15:42, PICCORO McKAY Lenz wrote:
>> >> > when try to build live jessie image using strecht i got those errors
>> >> >
>> >> > lb config: unrecognized option '--mirror-chroot-updates'
>> >> > lb config: unrecognized option '--parent-mirror-binary-updates'
>> >> > lb config: unrecognized option '--parent-mirror-chroot-updates'
>> >>
>> >> When working on the documentation, I've noticed these command line
>> >> options as well. They are not present in the scripts, they are only in
>> >> the documentation.
>> >> Unfortunately due to the migration from alioth to salsa the git
>> >> history
>> >> got lost, so I cannot trace it back. I would assume that the
>> >> functionality was remove from the scripts at some time, and that
>> >> someone
>> >> forgot to update the documentation accordingly. I've downloaded the
>> >> package 1:20151215 [1], and the command line is mentioned there also
>> >> only in the documentation, which confirms my assumption.
>> >>
>> >> Instead of (re-)implementing these options, I would update the
>> >> documentation instead.
>> >>
>> >> With kind regards,
>> >> Roland Clobus
>> >>
>> >> [1] https://snapshot.debian.org/package/live-build/1%3A20151215/
>> >>
>> >>
>> >>
>> >>
>> >
>>
>

Re: lb config for buster => building stretch ?

[Michael .]

Hi Johann
I had this issue, among many others, and found it to be that Live
Build was occasionally building the iso in the root folder instead of
the folder my config settings were in (in my home folder). You didn't
give us the entire command sequence so I am not sure of you have cd
into another directory apart from the root.
Cheers.
Michael.

P.S. I forgot to click reply all so this has now been sent to the list
as well as the reply (exact same) that I sent to you.

On 01/06/2019, Johann  wrote:
> Hi,
>
> I'm confused. I configure live-build to get it to compile a "buster",
> and I still get a stretch result ! What could be hapenning ?
>
> There's some loggs where you can see the "paradox".
>
> ++ lb clean --all
> [2019-05-31 17:09:27] lb clean
> P: Cleaning chroot
> ++ lb config
> [2019-05-31 17:09:28] lb config
> P: Executing auto/config script.
> [2019-05-31 17:09:28] lb config noauto -a amd64 --linux-flavours amd64
> --debian-installer live --debian-installer-gui true --memtest memtest86
> --distribution buster --debian-installer-distribution daily
> --iso-application otybian --iso-volume otybian --mode debian --system
> live --archive-areas main contrib --security true --updates true
> --backports false --binary-filesystem fat32 --binary-images iso-hybrid
> --apt-indices true --apt-recommends true --apt-secure true
> --apt-source-archives false --firmware-binary true --firmware-chroot
> true --win32-loader false --memtest none --clean --debug --verbose
> --source false D: Reading configuration file config/common D: Reading
> configuration file config/bootstrap D: Reading configuration file
> config/chroot D: Reading configuration file config/binary D: Reading
> configuration file config/source P: Updating config tree for a
> debian/buster/amd64 system P: Symlinking hooks... ++ lb build ++ tee
> cook.log [2019-05-31 17:09:29] lb build P: live-build 1:20190311 P:
> Building config tree for a debian/buster/amd64 system [2019-05-31
> 17:09:29] lb bootstrap P: Setting up cleanup function [2019-05-31
> 17:09:29] lb bootstrap_cache restore P: Restoring bootstrap stage from
> cache... [2019-05-31 17:09:30] lb bootstrap_debootstrap P: Begin
> bootstrapping system... W: skipping bootstrap, already done
> [2019-05-31 17:09:30] lb bootstrap_cache save
> P: Saving bootstrap stage to cache...
> [2019-05-31 17:09:31] lb chroot_devpts install
> P: Begin mounting /dev/pts...
> [2019-05-31 17:09:31] lb chroot_proc install
> P: Begin mounting /proc...
> [2019-05-31 17:09:31] lb chroot_selinuxfs install
> [2019-05-31 17:09:31] lb chroot_sysfs install
> P: Begin mounting /sys...
> [2019-05-31 17:09:32] lb chroot_debianchroot install
> P: Configuring file /etc/debian_chroot
> [2019-05-31 17:09:32] lb chroot_dpkg install
> P: Configuring file /sbin/start-stop-daemon
> [2019-05-31 17:09:32] lb chroot_tmpfs install
> [2019-05-31 17:09:32] lb chroot_sysv-rc install
> P: Configuring file /usr/sbin/policy-rc.d
> [2019-05-31 17:09:33] lb chroot_hosts install
> P: Configuring file /etc/hosts
> [2019-05-31 17:09:33] lb chroot_resolv install
> P: Configuring file /etc/resolv.conf
> [2019-05-31 17:09:33] lb chroot_hostname install
> P: Configuring file /etc/hostname
> P: Configuring file /bin/hostname
> [2019-05-31 17:09:33] lb chroot_apt install
> P: Configuring file /etc/apt/apt.conf
> [2019-05-31 17:09:33] lb bootstrap_archives binary
> P: Configuring file /etc/apt/sources.list
> Get:1 http://security.debian.org/debian-security stretch/updates
> InRelease [94.3 kB] Ign:2 http://deb.debian.org/debian stretch InRelease
> Get:3 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
> Get:4 http://security.debian.org/debian-security stretch/updates/main
> amd64 Packages [492 kB] Hit:5 http://deb.debian.org/debian stretch
> Release Get:7 http://deb.debian.org/debian stretch-updates/main amd64
> Packages [27.2 kB] Get:8 http://deb.debian.org/debian
> stretch-updates/main Translation-en [11.2 kB] Get:9
> http://deb.debian.org/debian stretch/main Translation-en [5384 kB]
> Get:10 http://security.debian.org/debian-security stretch/updates/main
> Translation-en [219 kB] Get:11
> http://security.debian.org/debian-security stretch/updates/contrib
> amd64 Packages [1760 B] Get:12
> http://security.debian.org/debian-security stretch/updates/contrib
> Translation-en [1759 B] ^C
>
>

Re: Add non-package files to an ISO.

[Michael .]

https://live-team.pages.debian.net/live-manual/html/live-manual/customizing-contents.en.html#customizing-contents

On 21/06/2019, andy pugh  wrote:
> Is it possible to include non-packaged files in a Live ISO image /
> installer?
>
> Google auto-completes the search term, but doesn't seem to take me to any
> pages that answer the question.
>
> The specific application is a bunch of FPGA firmware files to be installed
> in /lib/firmware.
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is designed
> for the especial use of mechanical geniuses, daredevils and lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1916
>

Re: Suspicious Debian 10.0.0 download behaviour.

[Michael .]

I just tried the 1st link and it works fine, I tried the second link
and I get a 404 not found.

The distrowatch link in the reply above works as it should, there is
no 403 forbidden on that page for me.
Cheers.
Michael.

On 09/08/2019, Thomas Schmitt  wrote:
> Hi,
>
> Rick wrote:
>> when I tried to download Debian 10.0.0 via Distrowatch I was surprised to
>> be
>> asked for my admin password at the end of the download plus there was
>> another window requesting something else.
>> [...]
>> The original download link from Distrowatch was:
>> (1)https://cdimage.debian.org/debian-cd/10.0.0-live/amd64/iso-hybrid/debian-live-10.0.0-amd64-gnome.iso
>> [cdimage.debian.org]
>> This redirected to the following Swedish site:
>> (2)https://caesar.ftp.acc.umu.se/debian-cd/10.0.0-live/amd64/iso-hybrid/debian-live-10.0.0-amd64-cinnamon.iso/
>> [caesar.ftp.acc.umu.se]
>
> I tested
>
>   wget
> https://caesar.ftp.acc.umu.se/debian-cd/10.0.0-live/amd64/iso-hybrid/debian-live-10.0.0-amd64-cinnamon.iso
>
> which asked for no passwords and popped no windows.
> So it has to be assumed that your download procedure is to blame.
>
> What operating system did you use for downloading ?
> What download tool (web browser) ?
>
> How did you get around the 403 "Forbidden" error when trying to view
>   https://distrowatch.com/
> by a web browser ?
>
>
> Have a nice day :)
>
> Thomas
>
>

Re: great!! thank you!!!

[Michael .]

It defaults to stretch because the base configuration in live build
live config has not been changed by the maintainer. You could file a
bug report on it if you want.

On 09/10/2019, p...@gilbertson.biz  wrote:
> Thanks Jacek for the help. I typed "lb config --debian-installer live -d
> buster"   and it worked!!  I wonder why it was defaulting to stretch?
>
> Cheers
>
>

Re: Reducing the amount of i386 Live images for bullseye

[Michael .]

Good morning Jonathan and list group.

I personally think dropping i386 isn't a good thing to do. I,
personally, am trying to help developing countries (in Oceania) get
into Linux and many people rely on gifted hardware which much of it is
i386. If you decide to drop i386 you will limit how many people can
use Debian.

Dropping i386 because so many other distros are doing it is not a
valid reason for dropping it.

If you keep it I think keeping MATE, LX** (both), XFCE is appropriate
because you want to give people choice of what they want not what you
think they want. To me Standard is useless, and always has been, it is
much easier to install via netinst than via standard. Another thing to
consider is an image with a Window Manager like Fluxbox that has
Synaptic so that people can install their favourite DE rather than the
DE that Debian thinks everyone wants.

FYI I run a few i386 machines (an old Pentium 4 desktop, 3 Panasonic
Toughbook CF-29, and an eMachine netbook) that are still going strong.
The CF-29s and eMachine are used everyday.

Of course this is just my humble opinion.
Cheers.
Michael.

On 18/10/2019, Jonathan Carter  wrote:
> Hi Live team
>
> For a while, the discussions have popped up whether we still want or
> need i386 desktop live images. Building all those images and testing
> them at a regular basis (sometimes regular as in, every few months) and
> also at release time is quite tedious, and they're pretty much useless
> compared to the amd64 images on any computer from the last 5 years (yes,
> that crappy Atom cpu laptop that is locked to 32 bit is older than 5
> years already).
>
> I believe that at least the KDE and Gnome i386 images aren't that
> useful. You need a reasonably beefy computer with enough memory to run
> those, and at that point you might as well use the amd64 media.
>
> Since many other distributions are making the jump to dropping i386
> installation media entirely, I think that it's a good idea to keep some
> live media around for one more release, as long as bullseye continues to
> make it easy to do so. This will make it possible for users with 32-bit
> hardware (who probably mostly uses it for hobby/specialist reasons by
> the time bullseye is released) to continue using it for a few more years
> on a supported linux system.
>
> At DebConf we discussed this for a bit too, where I said I'd take it to
> the debian-live list for some additional feedback.
>
> Here is the list of our current i386 images:
>
>  * debian-live-i386-cinnamon
>  * debian-live-i386-gnome
>  * debian-live-i386-kde
>  * debian-live-i386-lxde
>  * debian-live-i386-lxqt
>  * debian-live-i386-mate
>  * debian-live-i386-standard
>  * debian-live-i386-xfce
>
> I propose:
>  * At the minimum, dropping: cinnamon, gnome and kde
>  * Keep at least standard and one of the lighter desktop environments
>(perhaps lxqt? xfce?)
>
> I'm not sure where the best place is to draw the lines, but standard is
> very useful on old hardware since installing a headless/cli-only system
> using a live image is a lot easier on old hardware than installing every
> individual package using dpkg. And it seems worth while having one GUI
> system available too (if only to test things like whether the hardware
> even works on Debian, which I did recently on an old ThinkPad with S3
> graphics).
>
> So, what I'm asking is, how far should we cut back? Is there any
> compelling reason at all to keep any of the 3 installation mediums I
> want to drop? Do we need more than one gui system? And if just one, any
> strong preference (along with reasons?).
>
> -Jonathan
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
>   ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
>   ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
>   ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.
>
>

Re: Live-Build a Multi Arch Debian ISO with live desktop

[Michael .]

Do you mean multi-arch where an 64bit system can use 32 bit packages?
or do you mean an iso that has 2 different live systems one being 43
bit and the other being 64 bit?

If it;s the 1st you simply enable 32 bit libraries.
If it's the 2nd there is no built in way to do it that I am aware of
although it would be extremely helpful if there was. I think it could
be done but you would need to build 2 different systems and then merge
them ensuring you have either 2 different live folders (e.g. live-32
and live-64) or 2 different squashfs files (also named *-32  and
*-64). You would then need to change the syslinux menu to show the
appropriate 32 or 64 bit options on the appropriate machines. Rebuild
the iso, and test it.

On 28/02/2020, GSM PakOS  wrote:
> Hello dear Sir, I am trying to make a multi arch live ISO , With live lxqt
> desktop with my choice of software. Where can I find the base scripts for
> 1. Building a multi arch ISO
> 2. A multi arch ISO with a live squashfs based file.
>
> My debian respin named PakOS is available on
> https://sourceforge.net/projects/pakos/
> However I build the whole thing by chrooting into the i386 squashfs, not an
> elegant solution. If a base script is available anywhere, please point me
> to
> it . Thx.
>
> gSM
>

Re: combining multiple distributions

[Michael .]

Have a squeeze.list file with the appropriate entries for Squeeze in
the sources.list.d folder.
In your preferences file have an entry that puts the Squeeze version
of the package you want with a priority of 600. An the same file put
an entry for the Bullseye/Sid version(s) of the package with a
priority of -1.

On 02/03/2020, 0...@caiway.net <0...@caiway.net> wrote:
> Hi!
>
> I want to make a live image containing programs from multiple
> distributions.
>
> What woud be the proper way to achieve this?
>
> The reason: The program from the older distro squeeze is better,
> but bullseye/sid have better graphics
>
> Combining two distributions is what I want.
>
> Feel free to ask more specific questions!
>
> Thanks!
>
>

Re: live-build copyright notices

[Michael .]

I think, I may be wrong so am happy to be corrected if I am, it is
customary in Linux to acknowledge copyright of previous authors. Let's
be frank and admit that if it wasn't for Daniel Live Build probably
wouldn't have existed in the 1st place. I think removing
acknowledgement of Daniel's copyright status while he was the primary
author of the software would be nearly, but not quite, as bad as the
way in which some people launched into an attempted take over of the
live build name. Interestingly I'm not even sure if those people are
involved in Debian Live at all anymore, not having heard a peep out of
them with regards to Live Wrapper and its development for a very long
time.

I think, as a mark of respect to Daniel, the best thing the Debian
community could do is leave Daniel's name on the copyright notice for
the time he was the lead, if not the only, developer working on Live
Build.

On 10/03/2020, jnq...@gmail.com  wrote:
> since Daniel Baumann abandoned the live-build project a few years ago,
> should the copyright notices not now be updated to reflect this?, i.e.
>
> ```
> ## Copyright (C) 2016 The Debian Live team <
> debian-live@lists.debian.org>
> ## Copyright (C) 2006-2015 Daniel Baumann 
> ```
>
> since effectively his copyright ownership covers up to the point where
> he abandoned it and the live-team owns the versions with changes that
> have been applied since.
>
> similarly the authorship in the man pages.
>
> should the notices in the files not also include references to which
> license actually applies?
>
> would you be open to an MR to address this if my doing the work helps?
>
> Lyndon
>
>

Bug#954081: debian-live-10.3.0-amd64-gnome.iso fails to load desktop on Acer A515-43-R19L laptop

[Michael .]

Let me guess, your CPU and Graphics are AMD?
The only Debian based distro that I could get to work with modern AMD
graphics is MX19, Ubuntu 20.04 MATE works but back when I was removing
W10 Ubuntu 20.04 had just entered development status.
Give MX19 a try and if it works for you you will also have the added
benefit of a choice between Sysvinit and SystemD at boot time,
something no other currently available distro offers.

On 18/03/2020, jnq...@gmail.com  wrote:
> Just throwing a couple of thoughts your way in case it helps at all.
>
> Ending up with a blank screen with a blinking cursor in the top left
> instead of the graphical login suggests that the graphical environment
> could not load for some reason. I have experienced this myself a couple
> of times using Debian's unstable channel after a major partial upgrade
> to a new version of Gnome. I also happen to have experienced it today
> when I returned to my computer only to find that a download had used up
> all of my remaining free disk space and things were not happy.
>
> Note that you can use CTRL+ALT+ to switch to a different
> console interface and thus login in in text based mode. (The default
> graphical environment is assigned to one of the F1-12 keys, just try
> different F1-12 keys with CTRL+ALT until you get a text console).
>
> Since other distro live discs are working, but not the current Debian
> discs, have you tried an older Debian disc? Perhaps the particular
> package versions in the latest discs have a bug, just like I've
> experienced with the updated Gnome situation just mentioned, and the CD
> release team did not notice or it only occurs in certain situations.
>
> Note that you can build your own custom live disc with Debian's live-
> build tool, though of course if you're having trouble getting Debian
> installed in the first place ...
>
> On Mon, 2020-03-16 at 11:13 -0700, Lou Poppler wrote:
>> This is possibly a "non-free" firmware problem.  I suggest you try
>> with one of
>> the "unofficial" "non-free" live images or installer images.
>>
>> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
>>
>> On Mon, 2020-03-16 at 09:25 -0400, Mike Haag wrote:
>> > Package: debian-live
>> > Severity: important
>> >
>> > I first updated the BIOS using the supplied Windows 10, then
>> > replaced the
>> > supplied 128GB SSD with a new 500GB SSD.
>> >
>> > Verified the iso file with SHA512, and tried running as both DVD
>> > and USB thumb
>> > drive:
>> >
>> > Grub starts as expected.
>> >
>> > 1. Attempted to start the live desktop environment from the first
>> > Grub menu
>> > item, "Debian GNU/Linux Live (kernel 4.19.0-8-amd64)".
>> > 2. Multiple status messages are displayed. Then, a Debian splash
>> > screen is
>> > briefly displayed, followed immediately by a blank screen with a
>> > blinking
>> > cursor, and the system freezes.
>> > 3. Ctrl-Alt-Del will reboot the laptop into the Grub menu.
>> >
>> > The graphical installer (third Grub menu item) runs, and appears to
>> > complete
>> > successfully. But, the installed system exhibits the same problem:
>> > Multiple
>> > startup messages, and the system freezes before the desktop
>> > environment starts,
>> > just displaying a blank screen and blinking cursor.
>> >
>> > For what it's worth, I also tried several other Debian-based and
>> > RPM
>> > distributions. Could only get a working system with the RPMs:
>> >
>> > 1. Debian: The following produce the same results as above.
>> >
>> >  debian-live-10.3.0-amd64-gnome+nonfree.iso
>> >  debian-live-testing-amd64-gnome.iso
>> >  debian-10.3.0-amd64-netinst.iso
>> >
>> > 2. Ubuntu 19.10 and LinuxMint 19.3: The live distributions work as
>> >expected. Installed systems begin to boot but then both fail
>> > with
>> >unspecified watchdog soft lock errors before their respective
>> > desktop
>> >environments start.
>> >
>> > 3. Fedora 31: Live runs as expected. Installed system boots and
>> > runs as
>> > expected.
>> >
>> > 4. OpenSUSE Leap 15.1: Live runs as expected. Installed system
>> > boots and runs
>> > as expected.
>> >
>> > The only recommendation I could find using the Acer user forum and
>> > other
>> > internet searches, was to try editing the Grub menu line to
>> > "nomodeset", but
>> > that doesn't work. There was also some theorizing that the kernel
>> > needed to be
>> > updated to 5.0, but openSUSE 15.1 is kernel 4.12, and that is
>> > working.
>> >
>> > Looking for advice and suggestions: I do not know how to proceed
>> > with further
>> > trouble-shooting.
>> >
>> > Thanks, Mike
>> >
>> >
>> >
>> > -- System Information:
>> > Debian Release: 10.3
>> >   APT prefers stable-updates
>> >   APT policy: (500, 'stable-updates'), (500, 'stable')
>> > Architecture: amd64 (x86_64)
>> >
>> > Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
>> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
>> > LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
>> > Shell: /bin/sh linked to /u

Bug#954081: MX19.1 Live fails similar to Debian 10.3 Live on Acer A515-43 laptop

[Michael .]

MX19 isn't Debian therefor a bug report to Debian about MX19 probably
wont achieve anything.

On 19/03/2020, Mike Haag  wrote:
> Thanks for the suggestion to try MX19. It does look like an interesting
> distribution, and currently leads the page hit rankings on DistroWatch.
> Unfortunately, it didn't work on the Acer laptop.
>
> I first verified the image, then successfully tested the USB on my
> desktop machine. Sadly, on the Acer laptop, it fails the same as the
> Debian live images: After several boot messages, the desktop environment
> (XFCE in this case) fails to load, and the machine freezes. The last two
> on-screen diagnostics are...
>
>  1. "Waiting for /dev to be fully populated...done (timeout)" [It takes
> two or three minutes for the trailing, "done (timeout)" part to
> appear.]
>  2. "Activating swap..."
>
> Nothing else after about 10 minutes.
>
> Thanks, Mike
>
>

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

Hi Subhani
I just had a look at Pak OS, nice project, and I have 1 question for
you that may help many others who use live build. How did you create
an iso image with both 32 and 64 bit architectures using live build?
If you would share your knowledge with teh live community I am sure
many would be extremely grateful.
Regards.
Michael.

On 16/04/2020, Pak OS  wrote:
> I am maintaining a multi Arch live image with Calamares Installer and
> debian installer at source forge.
> Please search for PakOS on Google, it should be 1st result. Go to my source
> forge page. It's a large one. 3.3 GB. A lot of software.
> Pl see if it suits you. I am available for any help.
>
> https://sourceforge.net/projects/pakos/files/Main/
>
> gSM
>

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

Thank you Subhani
I will try this out today and see what happens.
May I suggest you create a github page for PakOS and put all the
materials, e.g. configs etc, that you want to share in there.
Regards.
Michael.

On 17/04/2020, Pak OS  wrote:
> I have installed PakOS on offline systems and it works. For Calamares, it
> failed so I had to install some packages later on, using chroot to enter
> ISO. This made the calamares installer useable. There are a lot of
> iterations, which I try to document. Since I am one person trying to
> maintain this ISO, so I can't do a lot of testing on diverse hardware.
> Recently I tested PakOS on an HP laptop, and all installers failed to
> install on blank hard disk. But once a portion was present, it installed
> correctly.
> So it's a journey. I would request anyone interested in joining me in any
> capacity. I am ready to share all code, what so ever humble work I have
> done.
> Thanks for your interest.
>
> gSM
>
> On Thu, Apr 16, 2020, 20:04 adrian15sgd  wrote:
>
>> Nice.
>>
>> Finally does it installer fetch the packages from the same iso or does
>> the
>> installer need an internet connection to work (e.g. fetches the packages
>> from the internet) ?
>>
>>
>> Thank you.
>> El 16/4/20 a las 17:01, Pak OS escribió:
>>
>> it installs on both. And automatically selects kernal based on underlying
>> architecture.
>>
>> gSM
>>
>> On Thu, Apr 16, 2020, 19:59 adrian15sgd  wrote:
>>
>>> With such a setup Can you install a 64-bit Debian? Or is it only useful
>>> for installing 32-bit Debian?
>>>
>>>
>>> Thank you.
>>> El 16/4/20 a las 14:46, Pak OS escribió:
>>>
>>> Ok, here goes:
>>>
>>> lb config --binary-images iso-hybrid --mode debian --architectures i386
>>> --linux-flavours 686 amd64 --distribution buster --archive-areas "main
>>> contrib non-free" --updates true --security true --cache true
>>> --apt-recommends true --debian-installer live --debian-installer-gui
>>> true
>>> --win32-loader true --iso-application PakOS10.3 --iso-preparer
>>> subhaniminhas-https://sourceforge.net/projects/pakos/ --iso-publisher
>>> subhaniminhas-https://sourceforge.net/projects/pakos/ --iso-volume
>>> PakOS10.3
>>>
>>> Hope this helps
>>>
>>> PakOS on Debian Derivatives List (
>>> https://wiki.debian.org/Derivatives/Census/PakOS)
>>> PakOS on LWN as only Pakistan Based Linux Distro (
>>> https://static.lwn.net/Distributions/#pakistan)
>>> Please vote for PakOS on DistroWatch waiting list at
>>> (https://distrowatch.com/dwres-mobile.php?resource=links)
>>>
>>>
>>> On Thu, 16 Apr 2020 at 16:49, Pak OS  wrote:
>>>
>>>> I will be honored. If you need, I can share the whole project you need
>>>> on SourceForge. Its actually just 1 switch in lb config. Since I am
>>>> typing
>>>> on my mobile. So can't access my laptop right now. The clue was given
>>>> on
>>>> this very forum.
>>>> In case you need any specific functionality in PakOS, please let me
>>>> know.
>>>>
>>>> If you like the work I have done and can benefit from it, please click
>>>> on the Distrowatch Waiting list Recommend Button against PakOS. I need
>>>> a
>>>> lot of votes to be part of Distro watch list of Distros.
>>>>
>>>> gSM
>>>>
>>>> On Thu, Apr 16, 2020, 08:37 Michael .  wrote:
>>>>
>>>>> Hi Subhani
>>>>> I just had a look at Pak OS, nice project, and I have 1 question for
>>>>> you that may help many others who use live build. How did you create
>>>>> an iso image with both 32 and 64 bit architectures using live build?
>>>>> If you would share your knowledge with teh live community I am sure
>>>>> many would be extremely grateful.
>>>>> Regards.
>>>>> Michael.
>>>>>
>>>>> On 16/04/2020, Pak OS  wrote:
>>>>> > I am maintaining a multi Arch live image with Calamares Installer
>>>>> > and
>>>>> > debian installer at source forge.
>>>>> > Please search for PakOS on Google, it should be 1st result. Go to my
>>>>> source
>>>>> > forge page. It's a large one. 3.3 GB. A lot of software.
>>>>> > Pl see if it suits you. I am available for any help.
>>>>> >
>>>>> > https://sourceforge.net/projects/pakos/files/Main/
>>>>> >
>>>>> > gSM
>>>>> >
>>>>>
>>>>
>>>
>>> --
>>> Regards
>>>
>>> gSm
>>>
>>> https://sourceforge.net/projects/pakos/
>>> https://distrowatch.com/dwres.php?resource=links#new
>>> https://lwn.net/Distributions/#pakistan
>>> https://wiki.debian.org/Derivatives/Census/PakOS
>>>
>>>
>

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

Sometimes I'm an idiot and I forget to "reply to all". Thank you to
dbgr for pointing out my error to me. So please find below what I have
tried and what the outcomes were.

I just tried Subhani's tip and it failed with
E: Error reading the CPU table
P: Begin unmounting filesystems...
P: Saving caches...
E: Error reading the CPU table

I suspected, as I have said in previous threads, that we will need  to
build 2 different systems and then merge them into 1 iso with menu
providing the options of which system to load. I'd like a copy of the
complete configuration for PakOS to see if it works on my system
before I suggest there are other things that need doing.

And then

In the previous build I followed Subhani's suggestion and then checked
the chroot file in the config folder. I had to manually edit it after
the lb config command and then run lb build to which I got the failure
mentioned in my previous reply.

I have just done an lb clean --all and removed my cache folder to
force a completely new build. lb config and then lb build to get it
running. Checked the chroot file in the config folder and only 686-pae
is listed in the chroot file. lb config is only passing one option to
the chroot file not both 32 and64 bit options. First test failed with
the result as mentioned in my previous reply, 2nd test failed with lb
config only passing 1 linux-flavor option rather than the 2 as
suggested by Subhani.

Anyone else trying this and finding anything different to my findings?
Regards.

On 17/04/2020, dbgr  wrote:
> Hello everybody.
>
> Thank you very much for your tips, recommendations, attention and time.
>
> In the next days I will try to look into everything you recommended me
> in this thread and test the different possibilities. Then I will try to
> write about my experience and send here.
>
> If anyone knows about any other options, tools, hacks, etc. that are
> pertinent to this discussion, please, share it with us :)
>
>
> On 2020-04-16 18:59, Pak OS wrote:
>> I intend to do it on source forge. Till then I am available here for
>> any queries.
>>
>> gSM
>>
>> On Thu, Apr 16, 2020, 23:55 Michael .  wrote:
>>
>>> Thank you Subhani
>>> I will try this out today and see what happens.
>>> May I suggest you create a github page for PakOS and put all the
>>> materials, e.g. configs etc, that you want to share in there.
>>> Regards.
>>> Michael.
>>>
>>> On 17/04/2020, Pak OS  wrote:
>>>> I have installed PakOS on offline systems and it works. For
>>> Calamares, it
>>>> failed so I had to install some packages later on, using chroot to
>>> enter
>>>> ISO. This made the calamares installer useable. There are a lot of
>>>> iterations, which I try to document. Since I am one person trying
>>> to
>>>> maintain this ISO, so I can't do a lot of testing on diverse
>>> hardware.
>>>> Recently I tested PakOS on an HP laptop, and all installers failed
>>> to
>>>> install on blank hard disk. But once a portion was present, it
>>> installed
>>>> correctly.
>>>> So it's a journey. I would request anyone interested in joining me
>>> in any
>>>> capacity. I am ready to share all code, what so ever humble work I
>>> have
>>>> done.
>>>> Thanks for your interest.
>>>>
>>>> gSM
>>>>
>>>> On Thu, Apr 16, 2020, 20:04 adrian15sgd 
>>> wrote:
>>>>
>>>>> Nice.
>>>>>
>>>>> Finally does it installer fetch the packages from the same iso or
>>> does
>>>>> the
>>>>> installer need an internet connection to work (e.g. fetches the
>>> packages
>>>>> from the internet) ?
>>>>>
>>>>>
>>>>> Thank you.
>>>>> El 16/4/20 a las 17:01, Pak OS escribió:
>>>>>
>>>>> it installs on both. And automatically selects kernal based on
>>> underlying
>>>>> architecture.
>>>>>
>>>>> gSM
>>>>>
>>>>> On Thu, Apr 16, 2020, 19:59 adrian15sgd 
>>> wrote:
>>>>>
>>>>>> With such a setup Can you install a 64-bit Debian? Or is it only
>>> useful
>>>>>> for installing 32-bit Debian?
>>>>>>
>>>>>>
>>>>>> Thank you.
>>>>>> El 16/4/20 a las 14:46, Pak OS escribió:
>>>>>>
>>>>>> Ok, here goes:
>>>>>>
>>>>>> lb config

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

Hi Subhani and everyone else reading this.
Thanks for your efforts I'm not sure you need to upload your entire
build folders, instead all I think you would need to upload is your
configuration files (auto/config & config/*).
Cheers.
Michael.

On 21/04/2020, Pak OS  wrote:
> Sir, seeing your results, I will try to upload my method on sourceforge.net
> soon, but full build folders are large. And my upload speed is just 100k.
> I will try to so in a next few days.
>
> On Tue, Apr 21, 2020, 5:07 AM Michael .  wrote:
>
>> Sometimes I'm an idiot and I forget to "reply to all". Thank you to
>> dbgr for pointing out my error to me. So please find below what I have
>> tried and what the outcomes were.
>>
>> I just tried Subhani's tip and it failed with
>> E: Error reading the CPU table
>> P: Begin unmounting filesystems...
>> P: Saving caches...
>> E: Error reading the CPU table
>>
>> I suspected, as I have said in previous threads, that we will need  to
>> build 2 different systems and then merge them into 1 iso with menu
>> providing the options of which system to load. I'd like a copy of the
>> complete configuration for PakOS to see if it works on my system
>> before I suggest there are other things that need doing.
>>
>> And then
>>
>> In the previous build I followed Subhani's suggestion and then checked
>> the chroot file in the config folder. I had to manually edit it after
>> the lb config command and then run lb build to which I got the failure
>> mentioned in my previous reply.
>>
>> I have just done an lb clean --all and removed my cache folder to
>> force a completely new build. lb config and then lb build to get it
>> running. Checked the chroot file in the config folder and only 686-pae
>> is listed in the chroot file. lb config is only passing one option to
>> the chroot file not both 32 and64 bit options. First test failed with
>> the result as mentioned in my previous reply, 2nd test failed with lb
>> config only passing 1 linux-flavor option rather than the 2 as
>> suggested by Subhani.
>>
>> Anyone else trying this and finding anything different to my findings?
>> Regards.
>>
>> On 17/04/2020, dbgr  wrote:
>> > Hello everybody.
>> >
>> > Thank you very much for your tips, recommendations, attention and time.
>> >
>> > In the next days I will try to look into everything you recommended me
>> > in this thread and test the different possibilities. Then I will try to
>> > write about my experience and send here.
>> >
>> > If anyone knows about any other options, tools, hacks, etc. that are
>> > pertinent to this discussion, please, share it with us :)
>> >
>> >
>> > On 2020-04-16 18:59, Pak OS wrote:
>> >> I intend to do it on source forge. Till then I am available here for
>> >> any queries.
>> >>
>> >> gSM
>> >>
>> >> On Thu, Apr 16, 2020, 23:55 Michael .  wrote:
>> >>
>> >>> Thank you Subhani
>> >>> I will try this out today and see what happens.
>> >>> May I suggest you create a github page for PakOS and put all the
>> >>> materials, e.g. configs etc, that you want to share in there.
>> >>> Regards.
>> >>> Michael.
>> >>>
>> >>> On 17/04/2020, Pak OS  wrote:
>> >>>> I have installed PakOS on offline systems and it works. For
>> >>> Calamares, it
>> >>>> failed so I had to install some packages later on, using chroot to
>> >>> enter
>> >>>> ISO. This made the calamares installer useable. There are a lot of
>> >>>> iterations, which I try to document. Since I am one person trying
>> >>> to
>> >>>> maintain this ISO, so I can't do a lot of testing on diverse
>> >>> hardware.
>> >>>> Recently I tested PakOS on an HP laptop, and all installers failed
>> >>> to
>> >>>> install on blank hard disk. But once a portion was present, it
>> >>> installed
>> >>>> correctly.
>> >>>> So it's a journey. I would request anyone interested in joining me
>> >>> in any
>> >>>> capacity. I am ready to share all code, what so ever humble work I
>> >>> have
>> >>>> done.
>> >>>> Thanks for your interest.
>> >>>>
>> >>>> gSM
>> >>>>
>&g

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

This is the config I have used when I had the error and subsequent
failure. It is a modified version of what used to be use by Ozzie
(STAR Linux). This configuration works for everything I have done
until the 2nd flavour as per Subhani's suggestion is added and that
breaks this configuration.

#!/bin/sh

set -e

#_A="amd64" \ CPU Architecture i386 = 32 BIT (686 and 686-pae) amd64 =
64 BIT. It would be great if we could build ARM images for RPi.
_A="i386" \
#_AA="main contrib non-free" \ Archive Areas must have at least main,
contrib and non-free are optional
_AA="main contrib non-free" \
#_BIT="x86-64" \ x86 = 32 BIT system x86-64 = 64 BIT system
_BIT="x86" \
#_DD="buster" \ Debian Distribution e.g. buster
_DD="buster" \
#_D="Rugged" \ Debian Derivative Distro e.g. Cobber or Rugged
_D="Rugged" \
#_F="false" \ When the answer to a question is false
_F="false" \
#_FL="amd64" \ Linux Flavour as in BIT. Options (currently) are 686
686-pae amd64. Flavor MUST match _A="" (CPU Architecture) to work
_FL="686-pae amd64" \
#_MB="http://deb.debian.org/debian/"; \ Repository Mirror to be used
_MB="http://deb.debian.org/debian/"; \
#_MS="http://security.debian.org/"; \ Security Repository Mirror, this
is usually always http://security.debian.org/ unless you are building
a non Debian system
_MS="http://security.debian.org/"; \
#_T="true" \ When the answer to a question is true
_T="true" \
#_DE="builder-choice" \ Desktop Environment or Window Manager used in
the build. Choices are Cinnamon, Gnome, KDE, LXDE, LXQT, Mate, TDE
(Trinity), XFCE, etc etc etc.
_DE="Mate" \
#_WM="builder-choice" \ Window Manager used in the build. Choices are,
currently, Fluxbox.
_WM="Fluxbox" \

lb config noauto \
--apt "apt" \
--apt-indices "${_F}" \
--apt-options "--yes" \
--apt-recommends "${_F}" \
--apt-secure "${_T}" \
--apt-source-archives "${_F}" \
--aptitude-options "--assume-yes" \
--architectures "${_A}" \
--archive-areas "${_AA}" \
--backports "${_F}" \
--binary-filesystem "fat32" \
--bootappend-live "boot=live config quiet splash keyboard-layouts=us" \
--bootappend-live-failsafe "boot=live components memtest noapic noapm
nodma nomce nolapic nomodeset nosmp nosplash vga=normal" \
--bootloaders "syslinux, grub-efi" \
--cache "${_T}" \
--cache-indices "${_F}" \
--cache-packages "${_T}" \
--cache-stages "bootstrap chroot" \
--checksums "md5 sha1 sha256" \
--chroot-filesystem "squashfs" \
--debian-installer "live" \
--distribution "${_DD}" \
--debian-installer-distribution "${_DD}" \
--debian-installer-gui "${_T}" \
--fdisk "fdisk" \
--firmware-binary "${_F}" \
--firmware-chroot "${_F}" \
--gzip-options "-6 --rsyncable" \
--hdd-label ""${_D}"Live" \
--initramfs "live-boot" \
--initramfs-compression "gzip" \
--iso-application ""${_D}"-Live-"${_DE}"" \
--iso-preparer "Michael" \
--iso-publisher ""${_D}" GNU/Linux" \
--iso-volume ""${_D}" "${_DE}" "${_BIT}" $(date +%Y%m%d)" \
--keyring-packages "mx19-archive-keyring" "antix-archive-keyring"/
--linux-flavours "${_FL}" \
--linux-packages "linux-image" \
--mirror-binary "${_MB}" \
--mirror-bootstrap "${_MB}" \
--mirror-debian-installer "${_MB}" \
--parent-mirror-binary-security "${_MS}" \
--parent-mirror-bootstrap "${_MB}" \
--parent-mirror-chroot-security "${_MS}" \
--quiet "${_F}" \
--security "${_T}" \
--source "${_F}" \
--source-images "${_F}" \
--system "live" \
    --tasksel "apt" \
--uefi-secure-boot "enable" \
--updates "${_T}" \
--verbose "${_T}" \
--win32-loader "${_F}" \
--zsync "${_T}" \
"${@}"

After reading Subhani's latest reply, and Subhani please don't call
anything MichaelOS, there is much more to it that just a regular live
build.
Cheers.
Michael.

On 21/04/2020, jnq

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

Debian doesn't have "official" non-free iso images because it breaks the DFSG.

On 21/04/2020, Pak OS  wrote:
> An after thought, is it possible that I and anyone interested can
> contribute the iso in debian official repos. I would love to build a multi
> arch debian iso with non free drivers set, in debian official iso
> downloads. Where can I apply for this.
>
> On Tue, Apr 21, 2020, 6:44 AM Pak OS  wrote:
>
>> Also, using this method is not very fool proof and stable. The iso has
>> bugs installing on many systems, which I could not understand, so
>> extensive
>> testing on multiple systems is required so that we can create a stable
>> iso.
>> I will request Michael and others interested to please collaborate on a
>> single base so that we can achieve a fully tested and stable iso with
>> full
>> multi arch support. We can name it anything, let's say MichealOS :)
>>
>> On Tue, Apr 21, 2020, 6:36 AM Pak OS  wrote:
>>
>>> ok here is my full script , here goes:
>>> Please consider, i am not very skilled in Live Build, and my work is
>>> based on eznix, a great open source enthusiast, his full work is
>>> available
>>> at  Sourceforge at https://sourceforge.net/projects/eznixos/
>>>
>>> #!/bin/bash
>>>
>>> #
>>>
>>> # bldPakOS10.3 -- Revision: 103r1 -- by SubhaniMinhas (
>>> https://sourceforge.net/projects/pakos/)
>>>
>>> # (GNU/General Public License version 3.0)
>>>
>>> #
>>>
>>> # Step by Step Live-Build
>>>
>>> #
>>>
>>> #
>>>
>>> # ~/PakOS10.3 -- build folder
>>>
>>> # ~/PakOS103 -- files location
>>>
>>> #
>>>
>>> #
>>>
>>> # Phase 1: - Assign WKDIR variable the output of pwd
>>>
>>> #
>>>
>>> WKDIR="$(pwd)"
>>>
>>> #
>>>
>>> #
>>>
>>> # Phase 2: - Create the build staging folder
>>>
>>> #
>>>
>>> rm -r PakOS10.3
>>>
>>> mkdir PakOS10.3
>>>
>>> #
>>>
>>> cd PakOS10.3
>>>
>>> #
>>>
>>> #
>>>
>>> # Phase 3: - Set up build environment
>>>
>>> #
>>>
>>> lb config --binary-images iso-hybrid --mode debian --architectures i386
>>> --linux-flavours 686 amd64 --distribution buster --archive-areas "main
>>> contrib non-free" --updates true --security true --cache true
>>> --apt-recommends true --debian-installer live --debian-installer-gui
>>> true
>>> --win32-loader true --iso-application PakOS10.3 --iso-preparer
>>> subhaniminhas-https://sourceforge.net/projects/pakos/ --iso-publisher
>>> subhaniminhas-https://sourceforge.net/projects/pakos/ --iso-volume
>>> PakOS10.3
>>>
>>> #
>>>
>>> #
>>>
>>> # Phase 4: - Install desktop and applications
>>>
>>> #
>>>
>>> echo lxqt-core featherpad lximage-qt lxqt-admin lxqt-branding-debian
>>> lxqt-openssh-askpass lxqt-powermanagement lxqt-sudo pavucontrol-qt
>>> qlipper
>>> qps xfce4-terminal lightdm engrampa xfwm4 audacious nm-tray feathernotes
>>> gucharmap meteo-qt qpdfview screengrab smplayer thunderbird >
>>> $WKDIR/PakOS10.3/config/package-lists/desktop.list.chroot
>>>
>>> #
>>>
>>> echo aqemu haveged less orage gdebi galculator grsync psensor synaptic
>>> gparted bleachbit flac faad faac mjpegtools x265 x264 mpg321 ffmpeg
>>> streamripper sox mencoder dvdauthor twolame lame asunder aisleriot
>>> gnome-mahjongg gnome-chess dosbox filezilla libxvidcore4 vlc
>>> soundconverter
>>> hplip-gui cdrdao frei0r-plugins htop jfsutils xfsprogs ntfs-3g cdtool
>>> mtools gthumb gimp testdisk numix-gtk-theme greybird-gtk-theme
>>> breeze-icon-theme breeze-gtk-theme xorriso cdrskin p7zip-full p7zip-rar
>>> keepassx hardinfo inxi gnome-disk-utility simplescreenrecorder
>>> thunderbird
>>> simple-scan remmina arc-theme gstreamer1.0-plugins-bad
>>> gstreamer1.0-plugins-ugly gstreamer1.0-plugins-good gnome-system-tools
>>> dos2unix dialog papirus-icon-theme faenza-icon-theme liferea
>>> transmission-gtk handbrake handbrake-cli audacity python-glade2 rar
>>> unrar
>>> ssh cifs-utils fuse gvfs-fuse gvfs-backends gvfs-bin pciutils
>>> squashfs-tools syslinux syslinux-common dosfstools isolinux live-build
>&g

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

JNQNFE I think you need to make it clear who you are replying to. At
one stage I thought you were talking to me so I replied but looking
back it is not clear if you were talking to me or someone else.

With regards to my config it "just works" as it is. With regards to
the keyring slash I noticed it as I pasted it into the email but I
didn't change it because guess what it still "just works".

If you know how to build a multi arch system please share exaclty how
to do it. I ask this because it has been brought up a few times over
the years and Subhani is the only one that has said he has it working.

Cheers.
Michael.



On 21/04/2020, jnq...@gmail.com  wrote:
> I've not taken a detailed look at this, but some things stand out:
>
> 1) if you're using live-build version 20191219 or newer, add an
> architecture specifier to the secondary kernel flavour.
>
> -  _FL="686-pae amd64" \
> +  _FL="686-pae amd64:amd64" \
>
> 2) with bootloaders you're mixing comma AND space separation. this may
> work, but it might not. i'd air on the side of caution and just use
> comma separation.
>
> -  --bootloaders "syslinux, grub-efi" \
> +  --bootloaders "syslinux,grub-efi" \
>
> 3) "config" in --bootappend-live needs to be replaced with "components"
> (for live-config 4.x+ compatibility)
>
> -   --bootappend-live "boot=live config quiet splash keyboard-
> layouts=us" \
> +   --bootappend-live "boot=live components quiet splash keyboard-
> layouts=us" \
>
> 4) i would not recommand caching the chroot stage
>
> -  --cache-stages "bootstrap chroot" \
> +  --cache-stages "bootstrap" \
>
> (or just remove it, thus leaving it as default)
>
> 5) --fdisk "fdisk" is an old hack, you should just remove this
>
> 6) --gzip-options "-6 --rsyncable" is the default, so just remove it
>
> 7) bad quoting in --iso-publisher and --iso-volume
>
> -   --iso-publisher ""${_D}" GNU/Linux" \
> +   --iso-publisher "${_D} GNU/Linux" \
>
> -   --iso-volume ""${_D}" "${_DE}" "${_BIT}" $(date +%Y%m%d)" \
> +   --iso-volume "${_D} ${_DE} ${_BIT} $(date +%Y%m%d)" \
>
> 8) bad quoting for keyring packages and wrong slash at end of line
>
> -   --keyring-packages "mx19-archive-keyring" "antix-archive-keyring"/
> +   --keyring-packages "mx19-archive-keyring antix-archive-keyring" \
>
> 9) --tasksel is an obsolete option, remove it
>
> there are other options using defaults, but no particular needs to
> remove them.
>
>
> On Tue, 2020-04-21 at 12:47 +1000, Michael . wrote:
>> This is the config I have used when I had the error and subsequent
>> failure. It is a modified version of what used to be use by Ozzie
>> (STAR Linux). This configuration works for everything I have done
>> until the 2nd flavour as per Subhani's suggestion is added and that
>> breaks this configuration.
>>
>> #!/bin/sh
>>
>> set -e
>>
>> #_A="amd64" \ CPU Architecture i386 = 32 BIT (686 and 686-pae) amd64
>> =
>> 64 BIT. It would be great if we could build ARM images for RPi.
>> _A="i386" \
>> #_AA="main contrib non-free" \ Archive Areas must have at least main,
>> contrib and non-free are optional
>> _AA="main contrib non-free" \
>> #_BIT="x86-64" \ x86 = 32 BIT system x86-64 = 64 BIT system
>> _BIT="x86" \
>> #_DD="buster" \ Debian Distribution e.g. buster
>> _DD="buster" \
>> #_D="Rugged" \ Debian Derivative Distro e.g. Cobber or Rugged
>> _D="Rugged" \
>> #_F="false" \ When the answer to a question is false
>> _F="false" \
>> #_FL="amd64" \ Linux Flavour as in BIT. Options (currently) are 686
>> 686-pae amd64. Flavor MUST match _A="" (CPU Architecture) to work
>> _FL="686-pae amd64" \
>> #_MB="http://deb.debian.org/debian/"; \ Repository Mirror to be used
>> _MB="http://deb.debian.org/debian/"; \
>> #_MS="http://security.debian.org/"; \ Security Repository Mirror, this
>> is usually always http://security.debian.org/ unless you are building
>> a non Debian system
>> _MS="http://security.debian.org/"; \
>> #_T="true" \ When the answer to a question is true
>> _T="true" \
>> #_DE="builder-choice" \ Desktop Environment or Window Manager used in
>> the build. Choices are Cinnamon, Gnome, KDE, LXDE, LXQT, Mate, T

Re: [Question] Integrating the debian installer in live-build - DVD, multi-arch, custom, etc.

[Michael .]

@Lyndon
No your name hasn't been showing at my end and fwiw I wasn't shouting
but I'll let you take it whatever way you want to. This is the
internet if you take 1 thing written in caps lock as shouting then
imagine how you take an entire paragraph?

Please understand that if something doesn't work in Live-Build it is
rather obvious when it doesn't show up in the build. You can pick my
config apart all you like and ask me to "trust you" all you like but
lets be clear here and understand that when I said it "just works" I
mean exactly that. Take me at my word or ignore me altogether, either
way I'll be a happy camper ;-)

Let's get back to Sunhani's build efforts for a minute and what my
understanding of it is. Subhani replied to a thread started by DBGR
(oops sorry dbgr) about building a system that can install both 32 and
64 bit systems. That is what I am working through. I am not interested
in 1 system that is 32 bit that can install on a 64 bit architecture.
Can we or can we not create an iso like the netinst but with both live
images that can install a 32 but system on a 32 bit machine and a 64
bit system on a 64 bit machine? Simple question, hopefully you can
give a simple answer. If we can, how? if we can't, why not? what is
lacking in live build and can you rectify it?
Cheers.
Michael.

On 21/04/2020, jnq...@gmail.com  wrote:
> @michael I always quote (include) the message I am replying to in my
> message when writing to multiple people or a mailing list, or otherwise
> use "@person" to address a specific person. When quoting, the quote
> always starts clearly with an "On [DATE, TIME] Michael wrote" type line
> (at least in my email program). Sometimes I write my message above the
> quoted text, sometimes below, sometimes broken up inbetween where bits
> of my reply need to be associated with specific parts of what I am
> replying to for clarity. Perhaps the issue lies with the set of email
> addresses that this thread has accumulated in the 'to' and 'cc' fields,
> rather than generically being targetted at the
> 'debian-live@lists.debian.org' mailing list address, or perhaps you're
> not used to me replying above quoted text rather than below?? I feel I
> am being perfectly clear; I do not understand why there's any
> confusion.
>
> btw 'jnqnfe' is my handle, my first name is Lyndon, is this not
> appearing at your end? I see your name as "Michael ." at my end. Also
> it's typical to address someone in the form @keltoiboy or @michael
> rather than just a handle/name in all caps (shouting) fwiw.
>
> Yes I know how to create a multi-arch system, not that I've actually
> tried it, but I'm very familiar with live-build being a significant
> contributor to the codebase.
>
> I've already discussed the details a little in this thread tonight, but
> to repeat a little:
>  1. You use -a i386 --linux-flavours "686 amd64", replacing "amd64"
> there with "amd64:amd64" if using live-build version 20191219 or newer.
> This gets you the correct set of kernels.
>  2. Having just one single package name like 'firefox:amd64' in a
> package list in your config is enough for live-build to know to run
> `dpkg --add-architecture amd64` and thus get a combined i386 and amd64
> image.
>
> Whether or not you need to have both 'Foo' and 'Foo:amd64' in your
> package lists for every single package you add to your package lists to
> get them in both arch forms is a detail I do not know off the top of my
> head. But just one in the form 'Foo:amd64' is enough to get the
> additional architecture configured as just stated.
>
> This gives you such a combined live environment, and if you use the
> "live" version of the installer, you thus also have a means of
> installing it. If you use the other installer types on the otherhand
> then you'll only get the one for the base architecture (i386 here) and
> thus only be able to install i386 (though you can manually add amd64
> later of course).
>
> Note that having a live environment containing both i386 and amd64
> architectures like this is the only means of having multiple
> architectures in a single image. You can **not** have an i386 live OS
> and an amd64 live OS sat side by side in the same image, selectable
> from different menu entries.
>
> With regards to your config, note that there is a big difference
> between appearing to work and actually working. Just because something
> appears to work does not mean that there is not a problem.
>
> Furthermore your script in fact is **not** working just fine, it IS
> broken, as I've just confirmed by 

Re: Why is lb config using stretch repos instead of buster?

[Michael .]

I wasn't going to post but this is a "problem" that has been occurring
for quite a while now and has been brought up in this list before. The
best thing to do with all live build commands (i.e. lb clean, lb
config, lb build) is to run them as root. Doing this forces live build
to run the config you tell it to run and where you tell it to run. If
you run lb config as root without having changed directory (e.g. cd
home/USERNAME/LiveBuild) it will create the config and build it in the
root folder.

On 28/04/2020, jnq...@gmail.com  wrote:
> Sorry, to be more clear, by root I wasn't referring to actual root, but
> use of sudo, as in I expected that you must have run `sudo lb
> config...` to initially create the config instead of just `lb
> config...`, but dropped the `sudo` on trying to modify it, which then
> failed. `lb config` does not require `sudo`, unlike the other commands.
> So yeah, if you'd created it initially with sudo, I can understand it
> requiring sudo to then make adjustments. But no error appearing in a
> situation of having originally used `sudo` and then trying to modify
> without is very much not ideal.
> On Tue, 2020-04-28 at 10:34 +0530, Harshad Joshi wrote:
>> My initial attempts were done using normal account. Even using sudo
>> seemed to create the issue, hence switching to root using su - did
>> the trick.
>>
>> --sent from OnePlus device--
>> On Tue, 28 Apr, 2020, 3:21 AM ,  wrote:
>> > Oh good! :)
>> > I had not thought of that since I'd have expected a clear
>> > permissions error to have occurred. I presume one did not? (I do
>> > not recall having happened to have tried doing that before).
>> > While all other commands require root, `lb config` does not and it
>> > is not typical to run it as root, but perfectly possible/valid to
>> > do so; it seems you must have done so originally.
>> > I've added it to my to-do list to check out and see if things could
>> > be improved in any way (see if a permissions error or similar can
>> > be output if not already; maybe issuing a warning if run as root to
>> > suggest that a future problem like this could be encountered). If
>> > so I'll craft such changes and submit for consideration.
>> > Lyndon.
>> > On Mon, 2020-04-27 at 12:07 +0530, Harshad Joshi wrote:
>> > > Issue was resolved when I did lb config - - distribution buster
>> > > as root.
>> > >
>> > >
>> > >
>> > > --sent from OnePlus device--
>> > >
>> > > On Thu, 23 Apr, 2020, 2:24 PM 0...@caiway.net, <0...@caiway.net>
>> > > wrote:
>> > > > On Thu, 23 Apr 2020 13:49:05 +0530
>> > > >
>> > > > Harshad Joshi  wrote:
>> > > >
>> > > >
>> > > >
>> > > > Hi,
>> > > >
>> > > > what does
>> > > >
>> > > > # cat config/build | grep Distribution
>> > > >
>> > > > say?
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > > Did everytime from rm -rf * to rebuild entire chroot but
>> > > > issue is
>> > > >
>> > > > > still on.
>> > > >
>> > > > >
>> > > >
>> > > > > I will update it here if issue gets resolved. I am trying to
>> > > > isolate
>> > > >
>> > > > > the problem
>> > > >
>> > > > >
>> > > >
>> > > > > --sent from OnePlus device--
>> > > >
>> > > > >
>> > > >
>> > > > > On Thu, 23 Apr, 2020, 1:20 PM ,  wrote:
>> > > >
>> > > > >
>> > > >
>> > > > > > did you `lb clean` to get a fresh start before you retried
>> > > > `lb
>> > > >
>> > > > > > build`?
>> > > >
>> > > > > >
>> > > >
>> > > > > > so:
>> > > >
>> > > > > >
>> > > >
>> > > > > > sudo rm -rf config
>> > > >
>> > > > > > sudo lb clean
>> > > >
>> > > > > > lb config --distribution buster
>> > > >
>> > > > > > sudo lb build
>> > > >
>> > > > > >
>> > > >
>> > > > > > does that sort things out?
>> > > >
>> > > > > >
>> > > >
>> > > > > > On Thu, 2020-04-23 at 12:21 +0530, Harshad Joshi wrote:
>> > > >
>> > > > > >
>> > > >
>> > > > > > Did it multiple times but no use. It's still downloading
>> > > > stretch
>> > > >
>> > > > > > repositories!
>> > > >
>> > > > > >
>> > > >
>> > > > > > I am not able to isolate root cause as from where live
>> > > > builder is
>> > > >
>> > > > > > taking stretch repo settings at second stage when I have
>> > > > explicitly
>> > > >
>> > > > > > set distribution option to buster!
>> > > >
>> > > > > >
>> > > >
>> > > > > > --sent from OnePlus device--
>> > > >
>> > > > > >
>> > > >
>> > > > > > On Thu, 23 Apr, 2020, 12:14 PM ,  wrote:
>> > > >
>> > > > > >
>> > > >
>> > > > > > Did you just run `lb config --distribution buster` on top
>> > > > of an
>> > > >
>> > > > > > existing config?
>> > > >
>> > > > > >
>> > > >
>> > > > > > Understand that the first time you run `lb config` some
>> > > > options, if
>> > > >
>> > > > > > not explicitly set, are automatically determined based upon
>> > > > others.
>> > > >
>> > > > > > The final config is then saved to disk. If you then
>> > > > subsequently
>> > > >
>> > > > > > run `lb config` to change something, you have to be careful
>> > > > because
>> > > >
>> > > > > > some options may end up with old val

Re: How to change menu entries in grub?

[Michael .]

Grub 2 reads various files for its naming system. Files such as
/etc/issue, /etc/lsb-release, /etc/debian-version, and various others
all contribute to what you are refereing to. There is a page somewhere
written by Paul (pabs) maybe in the census that tells maintainers what
files they need to change so not to infringe Debian copyright notices.
I suggest you locate it and read it and then change the files
mentioned and you'll probably find you don't have this difficulty
anymore.
Cheers.
Michael.

On 03/05/2020, jnq...@gmail.com  wrote:
> To achieve what???
> I already previously responded with what to do if you want to change
> the "Debian GNU/Linux 10 (buster)" text shown as part of the default
> background splash. It's in the very text you quoted in your reply...
> There is no text "Debian" in actual grub2/syslinux menus...
> Regards,Lyndon
> On Sat, 2020-05-02 at 22:18 +0500, Pak OS wrote:
>> Kindly inform, what files to change, if we are using grub 2. Thanks.
>>
>> gSM
>> On Sat, May 2, 2020, 22:00   wrote:
>> > Ah, you speak of "boot/grub/menu.list", which is the configuration
>> > file for grub-legacy. I presumed that you meant grub2 (grub-
>> > pc|grub-efi).
>> > The grub-legacy support is largely unmaintained, and their is no
>> > **config option** for replacing the "Debian" text in the grub-
>> > legacy menus. That's not to say it's impossible though, it **is**
>> > possible.
>> > Since this is just text in text based files, you can easily enough
>> > construct a "hook" that you can place in your config to make the
>> > necessary modification to the binary contents before it is finally
>> > wrapped up as an ISO/IMG/whatever.
>> > So: 1. You create a small "hook" script in your config directory
>> > which does text replacement on the binary/boot/grub/menu.list file.
>> > 2. You execute the build.
>> > What happens: 1. When the build reaches the grub-legacy setup
>> > stage, it writes the config with "Debian" strings. 2. A little
>> > later the binary hooks stage is reached, and your hook gets run,
>> > which modifies that file to replace those strings as you desire. 3.
>> > After this the stage for wrapping things up as an ISO or whatever
>> > is reached, completing your image.
>> > You should find instructions for writing hooks in the `live-
>> > manual`.
>> > Alternatively, stop using grub-legacy.
>> > Regards,Lyndon
>> > On Sat, 2020-05-02 at 21:52 +0530, Harshad Joshi wrote:
>> > > No it is not about the graphics that are displayed on grub menu.
>> > > I have my own kernel and set of binaries that don't have debian
>> > > license so calling my live+install CD as debian os would be
>> > > wrong.
>> > > Hence I want to rename the debian entry in grub as something
>> > > else. I had previously done this by editing /boot/grub/menu.lst
>> > > in 2013-14 but now a lot has changed underneath both the debian
>> > > live wrapper and grub itself.
>> > >
>> > > So please assist me in making those required changes that will
>> > > reflect my os name after live CD installation on hdd.
>> > >
>> > > --sent from OnePlus device--
>> > > On Sat, 2 May, 2020, 5:10 AM ,  wrote:
>> > > > I presume that what you really mean is the text at the top of
>> > > > the screen in the bootloader? Like "Debian GNU/Linux 10
>> > > > (buster)".
>> > > > If that's what you mean, it's a part of the background image
>> > > > (splash), automatically generated from an SVG, with the text
>> > > > hard coded into live-build.
>> > > > At the current time the only solution available to you, besides
>> > > > hacking live-build, is to use a custom bootloader splash, which
>> > > > involves: 1. making a "bootloaders" directory within your
>> > > > config. 2. copying the folders for the bootloaders you're using
>> > > > from /usr/share/live/build/bootloaders into it. 3. replacing
>> > > > the splash. 4. doing a build of course.
>> > > > Note that you can throw away the SVG file in your syslinux
>> > > > (isolinux|syslinux|extlinuz|pxelinux) folder and replace with a
>> > > > PNG instead. grub only takes a PNG.
>> > > > Note that grub (default used for EFI) has a wierd thing in its
>> > > > config where it actually uses the sys

Re: Can't build with installer on bullseye

[Michael .]

I think you are using the Buster version of live build, try upgrading
all the live-* packages on your system to the testing (bullseye) or
unstable (sid) version.
Cheers.
Michael.

On 07/05/2020, Johann  wrote:
> Hey,
> I'm using bullseye (live-build 1:20190311) and if I try to build a
> project for a ISO with bullseye. When adding the installer bits
>
> “--debian-installer “live” --debian-installer-gui “true”
>
> Even to a "blank" project, the building crashes with
>>cp: cannot stat
>>‘/usr/share/live/build/data/debian-cd/bullseye/amd64_netinst_udeb_include’:
>>No such file or directory
>
> Any insight ?
> Thanks again for the great project.
>
>

Re: A couple of dumb questions

[Michael .]

>From memory the 2017 stuff for 1) was  me but I can't remember how it all went.
2) if you don't want items listed in the metapackage try apt-pinning,
the only other alternative is to write a list including things in the
metapackage you do want but not things you don't want.
3) it used to be possible but I'm not sure if it is anymore. In the
past if you wanted a non-standard kernel you had to list it in lb
config.

On 05/07/2020, andy pugh  wrote:
> 1) lb is making the creation of a liveCD surprisingly easy, but the
> one I have built does not seem to be able to install:
> "debian install "the debootstrap program exited with an error (return
> value 1)""
> Googling this seems to find a lot from 2017, but nothing more recent.
> Perhaps someone knows what the fix is?
>
> 2) Is there a way to remove some applications from a desktop task?
> I have task-xfce-desktop in my list.desktop.chroot but would prefer to
> have Geany instead of Mousepad and to skip Libre Office completely. Is
> it possible to pick-and-choose with the metapackages?
>
> 3) I would quite like to provide two alternative kernels. (-rt-amd64
> and -rtai-amd64). Is this possible? And how do I set which one is the
> boot choice after installation? I could probably work this out by
> experiment, apart from 1)
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>
>

Re: A couple of dumb questions

[Michael .]

>That sounds like a bit of a chore, I have no idea what it takes to put
>together a Desktop like XFCE, Mate etc.
Go to packages.debian.org and do a search for task-xfce-desktop then
look at the list of packages that are Dependencies and the packages
that are recommended

Dependencies.
light-locker
lightdm
task-desktop
tasksel
xfce4

Recommends.
atril
default-dbus-session-bus or dbus-session-bus
hunspell-en-us
hyphen-en-us
libreoffice
libreoffice-gtk2
libreoffice-help-en-us
mousepad
mythes-en-us
network-manager-gnome
orca
parole
quodlibet
synaptic
system-config-printer
tango-icon-theme
xfce4-goodies
xfce4-mixer
xfce4-power-manager
xfce4-terminal
xsane

Take out the packages you don't want, add the packages you do want. It
really isn't all that hard (and no I'm not being sarcastic).
Personally I'd forget about the recommends for now and just install
xfce4 and lightdm.

On 05/07/2020, andy pugh  wrote:
> On Sun, 5 Jul 2020 at 02:41, Michael .  wrote:
>
>> 2) if you don't want items listed in the metapackage try apt-pinning,
>> the only other alternative is to write a list including things in the
>> metapackage you do want but not things you don't want.
>
> That sounds like a bit of a chore, I have no idea what it takes to put
> together a Desktop like XFCE, Mate etc.
>
>> 3) it used to be possible but I'm not sure if it is anymore. In the
>> past if you wanted a non-standard kernel you had to list it in lb
>> config.
>
> The rt-amd64 kernel is fairly standard, the RTAI one isn't, but will
> be on a publicly-accessible repository.
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>

Re: A couple of dumb questions

[Michael .]

And network-manager-gnome or wicd for network connection

On 05/07/2020, Michael .  wrote:
>>That sounds like a bit of a chore, I have no idea what it takes to put
>>together a Desktop like XFCE, Mate etc.
> Go to packages.debian.org and do a search for task-xfce-desktop then
> look at the list of packages that are Dependencies and the packages
> that are recommended
>
> Dependencies.
> light-locker
> lightdm
> task-desktop
> tasksel
> xfce4
>
> Recommends.
> atril
> default-dbus-session-bus or dbus-session-bus
> hunspell-en-us
> hyphen-en-us
> libreoffice
> libreoffice-gtk2
> libreoffice-help-en-us
> mousepad
> mythes-en-us
> network-manager-gnome
> orca
> parole
> quodlibet
> synaptic
> system-config-printer
> tango-icon-theme
> xfce4-goodies
> xfce4-mixer
> xfce4-power-manager
> xfce4-terminal
> xsane
>
> Take out the packages you don't want, add the packages you do want. It
> really isn't all that hard (and no I'm not being sarcastic).
> Personally I'd forget about the recommends for now and just install
> xfce4 and lightdm.
>
> On 05/07/2020, andy pugh  wrote:
>> On Sun, 5 Jul 2020 at 02:41, Michael .  wrote:
>>
>>> 2) if you don't want items listed in the metapackage try apt-pinning,
>>> the only other alternative is to write a list including things in the
>>> metapackage you do want but not things you don't want.
>>
>> That sounds like a bit of a chore, I have no idea what it takes to put
>> together a Desktop like XFCE, Mate etc.
>>
>>> 3) it used to be possible but I'm not sure if it is anymore. In the
>>> past if you wanted a non-standard kernel you had to list it in lb
>>> config.
>>
>> The rt-amd64 kernel is fairly standard, the RTAI one isn't, but will
>> be on a publicly-accessible repository.
>>
>> --
>> atp
>> "A motorcycle is a bicycle with a pandemonium attachment and is
>> designed for the especial use of mechanical geniuses, daredevils and
>> lunatics."
>> — George Fitch, Atlanta Constitution Newspaper, 1912
>>
>

Re: sources.list

[Michael .]

Take a look at the Kali build scripts on their git page. They add some
lines to their build so that it adds them at the end of the build. I'm
going to add it to my builds as well.

On 16/08/2020, andy pugh  wrote:
> As far as I can tell from the documentation one would expect the
> default mirroring deb.debian.org/debian entry to be in
> /etc/apt/sources.list
>
> However on my lb config (once installed) I only
>
> # deb cdrom:[Debian GNU/Linux 10 _Buster_ - Official Snapshot amd54
> LIVE/INSTALL Binary 20200811-22:46[/ buster contrib main non-free
>
> #deb cdrom:[Debian GNU/Linux 10 _Buster_ - Official Snapshot amd54
> LIVE/INSTALL Binary 20200811-22:46[/ buster contrib main non-free
>
> deb http://security.debain.org/debain-security buster/updates main
> contrib non-free
> deb-src http://security.debain.org/debain-security buster/updates main
> contrib non-free
>
> What do I need to configure to have
> deb http://deb.debian.org/debian buster main contrib non-free
> deb-src  http://deb.debian.org/debian buster main contrib non-free
>
> Appear, in the usual way?
>
> The config is:
> #!/bin/sh
>
> set -e
>
> lb config noauto \
> --linux-packages linux-image-4.19.0-9-rt\
> --distribution buster \
> --binary-images iso-hybrid \
> --debian-installer live \
> --archive-areas "main contrib non-free" \
> --iso-application "LinuxCNC-2.8.0" \
> --iso-preparer "bodge...@gmail.com" \
> --iso-volume "LinuxCNC_2.8.0" \
> --iso-publisher "www.linuxcnc.org" \
> --apt-recommends true \
> "${@}"
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>
>

live-build minibase iso of 1.9 GB in size???

[Michael .]

On 21/09/2020, Michael .  wrote:
> I am trying to build a minibase iso for a specific machine that I am
> testing builds on. I have attached relevant files to this message for
> people to look at to see if I have done anything wrong.
>
> The problem that I have is the iso, without an DE or WM, that is built
> is 1.9 GB in size yet I can build an iso that is not minibase with
> MATE of 1.3 GB in size.
>
This is the 2nd time I am trying to send this email off, the 1st time
it was blocked because I dared to attach some files for people to look
at if they wanted to.

So I've just built a totally fresh iso and it is down to 343.9 MB
which is alot compared to the 110 or so that is written about in the
live build manual. My auto/config is below can someone tell me how I
can get this smaller or is that impossible now due to the advances in
Linux? The reason I am asking is I am trying to make a very specific
build for very specific hardware and I really don't want a huge iso
when I am finished the final iteration. I initially thought the pool
and pool-udeb folders were part of the problem and to a certain extent
I still do because I do not understand why a minibase system without
anything else will require alsa-utils or why a "live" system needs
debs as though a normal install which installs from debs does. Anywho
this has me a bit perplexed.

#!/bin/sh

set -e

#_A="amd64" \ CPU Architecture i386 = 32 BIT (686 and 686-pae) amd64 = 64 BIT
_A="i386" \
#_AA="main contrib non-free" \ Archive Areas must have at least main,
contrib and non-free are optional
_AA="main contrib non-free" \
#_BIT="x86-64" \ x86 = 32 BIT system x86-64 = 64 BIT system
_BIT="x86" \
#_DD="buster" \ Debian Distribution e.g. buster
_DD="buster" \
#_D="Rugged" \ Debian Derivative Distro e.g. Cobber or Rugged
_D="Rugged" \
#_F="false" \ When the answer to a question is false
_F="false" \
#_FL="amd64" \ Linux Flavour as in BIT. Options (currently) are 686
686-pae amd64. Flavor MUST match _A="" (CPU Architecture) to work
_FL="686-pae" \
#_MB="http://deb.debian.org/debian/"; \ Repository Mirror to be used
_MB="http://deb.debian.org/debian/"; \
#_MS="http://security.debian.org/"; \ Security Repository Mirror, this
is usually always http://security.debian.org/ unless you are building
a non Debian system
_MS="http://security.debian.org/"; \
#_T="true" \ When the answer to a question is true
_T="true" \
#_DE="builder-choice" \ Desktop Environment or Window Manager used in
the build. Choices are Cinnamon, Gnome, KDE, LXDE, LXQT, Mate, TDE
(Trinity), XFCE, etc etc etc.
_DE="" \
#_WM="builder-choice" \ Window Manager used in the build. Choices are,
currently, Fluxbox.
_WM="" \

lb config noauto \
--apt "apt" \
--apt-http-proxy "http://localhost:3142/"; \
--apt-indices "${_F}" \
--apt-options "--yes" \
--apt-recommends "${_F}" \
--apt-secure "${_T}" \
--apt-source-archives "${_F}" \
--aptitude-options "--assume-yes" \
--architectures "${_A}" \
--archive-areas "${_AA}" \
--backports "${_F}" \
--binary-filesystem "fat32" \
--bootappend-live "boot=live config quiet splash keyboard-layouts=us" \
--bootappend-live-failsafe "boot=live components memtest noapic noapm
nodma nomce nolapic nomodeset nosmp nosplash vga=normal" \
--bootloaders "syslinux" \
--cache "${_T}" \
--cache-indices "${_F}" \
--cache-packages "${_T}" \
--cache-stages "bootstrap chroot" \
--checksums "md5 sha1 sha256" \
--chroot-filesystem "squashfs" \
--debootstrap-options "--variant=minbase" \
    --debian-installer "live" \
--distribution "${_DD}" \
--debian-installer-distribution "${_DD}" \
--debian-installer-gui "${_T}" \
--fdisk "fdisk" \
--firmware-binary "${_F}" \
--firmware-chroot "${_F}" \
--gzip-options "-6 --rsyncable" \
--hdd-label ""${_D}"Live" \
--initramfs "live-boot" \
--initramfs-compression "gzip" \
--interactive "${_F}" \
--iso-application ""${_D}"-Live-"${_DE}"" \
--iso-preparer "Michael" \
--iso-publisher ""${_D}" GNU/Linux" \
--iso-volume ""${_D}" "${_DE}" "${_BIT}" $(date +%Y%m%d)" \
--linux-flavours "${_FL}" \
--linux-packages "linux-image" \
--mirror-binary "${_MB}" \
--mirror-bootstrap "${_MB}" \
--mirror-debian-installer "${_MB}" \
--parent-mirror-binary-security "${_MS}" \
--parent-mirror-bootstrap "${_MB}" \
--parent-mirror-chroot-security "${_MS}" \
--quiet "${_F}" \
--security "${_T}" \
--source "${_F}" \
--source-images "${_F}" \
--system "live" \
--tasksel "apt" \
--uefi-secure-boot "enable" \
--updates "${_T}" \
--verbose "${_T}" \
--win32-loader "${_F}" \
--zsync "${_T}" \
"${@}"

Re: Live-build (buster) builds stretch No buster.

[Michael .]

There was an answer. https://lists.debian.org/debian-live/2019/10/msg3.html

On 04/10/2020, charlie101  wrote:
> I found this  question has already been asked here:
> https://lists.debian.org/debian-live/2019/10/msg2.html.
>
> Unfortunately there was no accompanying answer.
>
> Can anyone tell me what the deal is with live-build building 'stretch'
> images instead of buster, and how one might fix this, assuming there is
> an easy fix.  Or should I report it as a bug?
>
> Thanks in advance
>
> charlie
>
>

Re: I managed to get Debian Live working on the Raspberry Pi3, but it takes some tweaking

[Michael .]

For
# --bootstrap-flavour minimal
# this doesn't seem to be a valid parameter any more?
try
--debootstrap-options "--variant=minbase"
but be aware that it doesn't really seem to work anymore. I've been
playing with it lately and had iso images larger than without it.

On 13/10/2020, Stefan Baur  wrote:
> Hi List,
>
> I've been tinkering with getting Debian Live to run on the Raspberry Pi3
> (and, since it has become available, on the Pi4, but that's a different
> can of worms - I got it working on both, but let's stick to the Pi3 for
> the scope of this post).
>
> I took some inspiration from
> , which either never
> fully worked or ceased to work, I don't remember the details any more.
>
> Anyways, I did manage to create a bootable image (created on amd64, with
> target platform arm64 - this uses qemu-arm-static).
>
> For a minimal working build, this is what I came up with:
>
> #!/bin/bash
>
> if  [ -z "$(which lb)" ] || \
> [ -z "$(which find)" ] || \
> [ -z "$(which head)" ] || \
> [ -z "$(which sfdisk)" ] || \
> [ -z "$(which losetup)" ] || \
> [ -z "$(which qemu-arm-static)" ] || \
> [ -z "$(which sed)" ] ; then
> echo "At least one of the required tools is missing."
> exit 1
> fi
>
> # create a builddir and change into it.
> mkdir -p builddir && cd builddir
>
> # start configuring the build
> lb config \
>  --architectures arm64 \
>  --bootstrap-qemu-arch arm64 \
>  --bootstrap-qemu-static /usr/bin/qemu-arm-static \
>  --firmware-binary false \
>  --firmware-chroot false \
>  --binary-filesystem fat32 \
>  --binary-images hdd \
>  --chroot-filesystem squashfs \
>  --hdd-size 512 \
>  --initramfs live-boot \
>  --system live \
>  --apt-indices none \
>  --apt-secure false \
>  --apt-source-archives false \
>  --archive-areas 'main firmware non-free' \
>  --bootappend-live "boot=live config hostname=pi username=pi" \
>  --cache-stages false \
>  --compression gzip \
>  --distribution buster \
>  --gzip-options '-9 --rsyncable' \
>  --mode debian \
>  --security false \
>
> # note that these parameters don't work as intended:
> # --binary-filesystem fat32
> # this uses mkfs.fat32 (or whatever), but the partition type is set to
> # 83 instead of b.  Which is bad.
>
> # --bootstrap-flavour minimal
> # this doesn't seem to be a valid parameter any more?
>
> # --bootappend-live "boot=live config hostname=pi username=pi"
> # this does not end up in cmdline.txt, so we need to patch it
> # in manually later on
>
> # we need to add a firmware package to make our image bootable ...
> echo "raspi3-firmware" >config/package-lists/raspi.list.chroot
>
>
> # the config is done, let's start the build.
> lb build
>
> # after the build, let's determine the name of our image file ...
> IMAGEFILE=$(find . -name "live*img" | head -n 1)
>
> # ... and change the partition type to reflect the file
> # system actually in use for partition 1 ("b" is FAT32)
> sfdisk --part-type $IMAGEFILE 1 b
>
> # next, we need to patch two things inside the image, so
> # we need to set up a loop device for it.
> FREELOOP=$(losetup -f)
> # note that this could become a TOCTOU issue if more than
> # 1 process tries to use loop devices
>
> # as the image is a full disk image containing a partition, we
> # need to jump to the position where the first partition starts
> losetup -o 1048576 $FREELOOP $IMAGEFILE
>
> # now let's mount it
> mkdir -p tempmount
> mount $FREELOOP tempmount
>
> # first, we copy the contents of the boot/firmware/ folder to the root
> directory, because that is where these files are needed
> cp -a chroot/boot/firmware/* tempmount
>
> # next, we replace the "root=" parameter with the parameters needed for
> # live-booting (this goes all on one line)
> sed -e 's#root=/dev/mmcblk0p2 #boot=live components config toram
> hostname=pi username=pi #' -i tempmount/cmdline.txt
>
> # here comes the cleanup part
> sync
> umount $FREELOOP
> losetup -d $FREELOOP
>
> Now if you dd the resulting *.img file to an SD card or to USB media,
> the pi will boot from it.
>
>
> However, the following questions remain:
>
> First, something seems to be wrong with "--binary-filesystem fat32"
> which creates a FAT32 filesystem in a partition marked as 83 (Linux)
> instead of b (FAT32).  Should I report this as a bug, or am I "holding
> it wrong"?
>
> Second, "--bootstrap-flavour minimal", which was used in the
> above-mentioned git repo, doesn't seem to exist any more?  What was it
> good for?  What has it been replaced with?
>
> Third, "--bootappend-live " seems to get ignored as well.  Again, should
> I report this as a bug, or am I "holding it wrong"?
>
> Fourth, all the files needed to boot a Pi need to go into the root
> directory of the first partition (which neeeds to be a FAT partition) of
> the boot media.  At the moment, live-build saves them in /boot/firmware
> inside the squashfs file, so even with the partition type issue

Re: About /etc/os-release

[Michael .]

You will need to pin the debian package "base-files" to -1 so it does
not install because it is the package that contains the file you are
referring to.

On 21/10/2020, Harshad Joshi  wrote:
> It is observed that modified content of /etc/os-release for live iso gets
> changed back to debian after apt-get upgrade from buster repository.
>
> Due to this, grub menu gets modified and instead of customized os name it
> gets changed to debian.
>
> How can we make sure that customized os title remains same?? Please advise.
>
> --sent from OnePlus device--
>

Re: Bug Report Information.

[Michael .]

Hi Philip
There are some issues with your request.
1. You don't tell us how you obtained Kali Linux, did you download it
of the Kali website or did you build it using the Kali instructions or
did you build it with the Vanilla Debian Live tools?
2.You don't tell us what the error is.
3. You have posted this to Debian Live which is the mailing list for
Debian not Kali.
4. You haven't posted this on Kali Linux so there are absolutely no
guarantees anyone from Kali will actually see your post here.
Please clarify these things for us so we may be able to assist you.
Cheers.


On 25/10/2020, Philip Cooper  wrote:
> Hello, I recently tried to Install a Kali Linux amd64 distribution and
> while installing, I encountered an Error in your code. I would appreciate
> if this could be Solved. Thank you.
>

Re: Trouble with running on non-debian systems.

[Michael .]

Hi Alex.
I'm not suggesting that you give up on this but understand that if you
do keep going you will probably be the 1st person in a very long time,
if not ever, to actually try this. The original developer has long
since gone and the things you are trying to do originate from his
work.

On 27/11/2020, Alex King  wrote:
> Spoke too soon there were errors related to /dev/pts, not sure if
> those are significant?
>
> [2020-11-27 04:13:18] lb chroot_devpts install
> P: Begin mounting /dev/pts...
> mount: wrong fs type, bad option, bad superblock on devpts-live,
>     missing codepage or helper program, or other error
>     (for several filesystems (e.g. nfs, cifs) you might
>     need a /sbin/mount. helper program)
>     In some cases useful info is found in syslog - try
>     dmesg | tail  or so
>
> Then the script chokes again because the host system has an old rsync,
> which does not support --chown:
>
> P: Begin copying chroot includes after packages have been installed...
> P: Copying includes.chroot into chroot using rsync...
> rsync: --chown=0:0: unknown option
> rsync error: syntax or usage error (code 1) at main.c(1459) [client=3.0.9]
> E: An unexpected failure occurred, exiting...
>
> Here's a diff to discuss:
>
> [root@el6 live-build]# git diff
> diff --git a/functions/chroot.sh b/functions/chroot.sh
> index d62a4fa..97b7401 100755
> --- a/functions/chroot.sh
> +++ b/functions/chroot.sh
> @@ -62,10 +62,10 @@ Chroot_copy_dir() {
>      local NAME="${2:-$(basename ${DIR})}"
>
>      Check_installed host /usr/bin/rsync rsync
> -   if [ "${INSTALL_STATUS}" -eq "0" ]
> -   then
> -   Echo_message "Copying ${NAME} into chroot using rsync..."
> +   if [ "${INSTALL_STATUS}" -eq "0" ] && \
>      rsync -Klrv --chown=0:0 "${DIR}" chroot/
> +   then
> +   Echo_message "Copy of ${NAME} into chroot using rsync
> succeeded"
>      else
>      cd "${DIR}"
>      Echo_message "Creating a tarball with files from
> ${NAME}..."
> diff --git a/scripts/build/bootstrap_debootstrap
> b/scripts/build/bootstrap_deboo
> index 49f0f88..1fedb47 100755
> --- a/scripts/build/bootstrap_debootstrap
> +++ b/scripts/build/bootstrap_debootstrap
> @@ -32,7 +32,7 @@ Check_crossarchitectures
>
>   Echo_message "Begin bootstrapping system..."
>
> -Check_package host bin/debootstrap debootstrap
> +Check_installed host /usr/sbin/debootstrap debootstrap
>
>   # Checking stage file
>   Check_stagefile "bootstrap"
>
>
> On 27/11/20 4:51 pm, Alex King wrote:
>> Further to this, after commenting out the package check in
>> /usr/lib/live/build/bootstrap_debootstrap, I got a further error about
>> /usr/share/keyrings/debian-archive-keyring.gpg not being available.
>>
>> So I copied /usr/share/keyrings/ from the debian-archive-keyring deb,
>> it's now getting a lot further.  I'm guessing it will now get to
>> completion.
>>
>> Seems like some fairly simple fixes to keep it working on non-deb
>> systems, e.g. checking for the binary instead of the package, and
>> working around not having the gpg files available.
>>
>> Thanks,
>> Alex
>>
>> On 27/11/20 4:30 pm, Alex King wrote:
>>
>>> Reading
>>> https://live-team.pages.debian.net/live-manual/html/live-manual/installation.en.html#110:
>>>
>>>
>>>
>>> "Note that using Debian or a Debian-derived distribution is not
>>> required"
>>>
>>> I am trying to run it on a centos6 system.  I have all the stated
>>> requirements.  Live build is installed via git clone and make
>>> install.  running lb build I get:
>>>
>>> ...
>>>
>>> [2020-11-27 03:15:22] lb bootstrap_debootstrap
>>> P: Begin bootstrapping system...
>>> E: You need to install debootstrap on your host system.
>>> E: An unexpected failure occurred, exiting...
>>>
>>> I had debootstrap 1.0.100 or so rpm installed (from epel?)  I thought
>>> that may be too old, so I removed that and installed debootstrap
>>> 1.0.123 by extracting the deb straight to the filesystem.  Now I have:
>>>
>>> [root@el6 ~]# debootstrap --version
>>> debootstrap 1.0.123
>>> [root@el6 ~]# which debootstrap
>>> /usr/sbin/debootstrap
>>>
>>> Exact same result, "You need to install debootstrap"
>>>
>>> Reading through /usr/lib/live/build/bootstrap_debootstrap, it's
>>> running "Check_package host bin/debootstrap debootstrap"
>>>
>>> Reading through /usr/share/live/build/functions/packages.sh, it's
>>> running dpkg-query to find if the package is installed.
>>>
>>> It looks like this is never going to work other than on deb based
>>> systems, and the manual on the above URL is simply inconsistent with
>>> reality
>>>
>>> Any hints? Web page need updating?
>>>
>>> Thanks,
>>> Alex
>>>
>
>

Re: Replacing live-wrapper for live images by live-build?

[Michael .]

Good morning everyone.
As a live user, and one who was extremely vocal a few years ago, I do
understand how people felt about live build but I must say I'm glad
Debian is not a country that needs running. The effort that went into
killing live build was immense and the saviour of Debian's live
presence never really got off the ground.

Diplomacy is not one of Debian's fine points is it? Really lets be
honest about this. Debian wants people to take on a project that was
unceremoniously killed off and its author publicly crucified. Yes I am
well aware than Daniel was difficult but what happened or more
correctly how it happened was wrong. If the leadership team at Debian
still don't recognise that then there is a problem.

Debian has had a few problems over the last few years and of the ones
I know about the live build problem was the least public. Debian lost
some really brilliant people, had an extremely public (so much so the
media reported it) blow up, and a complete forking of Debian over
systemd and Devuan is going reasonably well.

Now having said all that let me just ask you why would someone or
"people" plural want to take on a task like this in Debian when Debian
isn't fixing the problems it created.  Maybe if Debian acknowledged
the  handling of the issue and made provisions to working on ways that
would not create such a hostile situation again Debian may find some
people who are willing to work with it but I'll just say I think it's
unlikely that Debian has the ability or the desire to do that.

n.b when I say Debian I am referring to the organisation and its structure.

Regards.
Michael.

On 20/04/2021, Jonathan Carter  wrote:
> Hi Roland (and Steve (and others))
>
> On 2021/04/19 19:10, Steve McIntyre wrote:
>> Thanks for asking, and for your efforts so far. I'm going to be frank
>> in my response - please don't take this personally!
>
> Ditto, your work is much appreciated.
>
>> My experiences with live-build over the years have been so bad that I
>> personally never want to touch it again [1]. However, if you and
>> others think it is now a reasonable piece of software, then of course
>> I'm not going to stand in your way and try to stop you from using it.
>>
>> My main worry, however, is that we need some *people* (plural) to own
>> Debian's live builds going forwards: maintaining the software we use
>> (whatever that might be), running it, debugging it, making and testing
>> releases with it. In particular, the latter is not a small
>> undertaking. This is an ongoing commitment.
>
> I test the live images regularly and have gotten a bunch of papercuts
> fixed in the resulting live images over the last two releases, and also
> integrated calamares and worked with upstream to fix some bugs for us.
> I'm happy to continue doing that, but also don't have a particular
> interest in live-build for the exact reasons that you list, which also
> makes me particularly grateful that Roland is looking into it, until
> today I was worried that most of Roland's work has been on a shelf
> collecting dust, but I learned that it has been merged into live-build,
> so that's really great.
>
> I think the live images are as important as our other installation media
> and I'm also glad that buxy has taken care of so many things, I'd do
> more but like Steve, my fingers are in so many pies already so at some
> point you have to draw a line on how much you can take on.
>
> So yes, in summary, thanks for all your work, and I'm happy to continue
> testing, working on calamares integration (I had some plans for bullseye
> that didn't work out that I still intend to pursue for bookworm[1]) and
> fix/file Desktop bugs and meta-package issues for -live. So for what
> it's worth, you're also not alone when it comes to the live images.
>
> -Jonathan
>
> [1] https://jonathancarter.org/2019/10/17/calamares-plans-for-debian-11/
>
>

Re: Replacing live-wrapper for live images by live-build?

[Michael .]

Hi Raphael
I'm going to start by saying you have my utmost respect with your work
on Live Build but let me just say you totally misunderstood my point.

I have no doubt the live build developer community works very well
together and that there are a meaningful amount of merge requests. I
get regular emails about updates to it so I am aware to a certain
degree of how much goes into keeping it a fully maintained collection
of software packages.

Having said the above paragraph I do not see how that makes my view of
the situation within Debian incorrect. When individuals have made
comments that they feel burned the indication is there is a cultural
problem within the organisation itself that has led to people feeling
burned. How/why did this happen? If Debian (the organisation) knows
how it happened what has, or is being ,done to fix it and stop it
happening again? Lets be honest live build is not the only thing that
Debian has had difficulty over in recent memory (you didn't quote that
part of my previous message for some reason you just decided to
discuss live build). So again I'll ask why would anyone take on
something like this until Debian made provisions to working on ways
that would not create such a hostile situation again? If people within
Debian are shying away from doing things because they feel burned why
would someone knowingly volunteer to put themselves in a position
where the same thing would happen to them? We are all human, we have
feelings and most "normal" people don't willingly put themselves in
harms way (even psychological harm).

I understand that some may disagree with me and that is their right
but from my vantage point Debian has a cultural problem that needs
fixing so others do not end up shying away from projects because they
don't want to be "burned".

Ignore my 2 cents worth if you wish but please understand my desire is
to offer constructive critique about a situation that has been brewing
for a few years now. It literally has nothing to do with merge
requests but everything to do with peoples feelings of being valued.

Regards.
Michael.

On 20/04/2021, Raphael Hertzog  wrote:
> Hello,
>
> On Tue, 20 Apr 2021, Michael . wrote:
>> Now having said all that let me just ask you why would someone or
>> "people" plural want to take on a task like this in Debian when Debian
>> isn't fixing the problems it created.  Maybe if Debian acknowledged
>> the  handling of the issue and made provisions to working on ways that
>> would not create such a hostile situation again Debian may find some
>> people who are willing to work with it but I'll just say I think it's
>> unlikely that Debian has the ability or the desire to do that.
>
> The regular flow of merge requests that are processed and live-build
> uploads do not agree with your view of the situation.
>
> live-build and its development community is in a relatively good shape but
> we are lacking volunteers to care about the generation of release ISO for
> the end users because all the current developers are using the tool for
> their own need.
>
> That kind of position with responsibilities requires some amount of trust
> so it's not clear to me what are the requirements for the person that
> would be volunteering (that is if she isn't a Debian developer already).
>
> But maybe a call on d-d-a would be in order ?
>
> Cheers,
> --
>   ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
>   ⣾⠁⢠⠒⠀⣿⡁
>   ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
>   ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS
>

Re: Trying to build minimal live cd but get large /pool folder in the iso image. Please find attached my auto config and also my config folder (tar.gz). As far as I am aware if I use packages.list.chr

[Michael .]

I forgot to add, sorry, that this is in Wheezy using Wheezy LiveBuild.


On 26 June 2013 19:15, Michael .  wrote:

>
>

Re: large /pool folder in the iso image

[Michael .]

Hello Ben, thank you for your reply.

>First of all, what's with putting the whole message in the Subject:
>field of your email? I had to copy and hand reformat the whole thing
>below. Please don't let that happen again.

Re: formatting. I use Gmail for this. When I hit compose I had a screen pop
up I have never seen before. I used the only available spot, sorry if that
caused you undue grief.


>You may have forgotten to 'lb clean' between builds. You should include
>your log.

I do lb clean every  time, I have started new folders using the auto and
config I attached that never got through, did you get the screenshot?

>No, we never received any message from you with either of these things.
>If your config was particularly large, it may have been rejected by the
>mailing list software due to size. Please post at a publicly accessible
>location instead. You should also post your log.

The files sizes are "auto config" 960 B, "config.tar.gz." 24.7 kB, and
"screenshot" 76 kB. My apology if 960 B is to big for the list please find
them at these links auto
confighttps://dl.dropboxusercontent.com/u/30169329/config,
config.tar.gz
https://dl.dropboxusercontent.com/u/30169329/config.tar.gz , screenshot
https://dl.dropboxusercontent.com/u/30169329/Screenshot-uluru-mate-core-i386.iso%20%5Bread%20only%5D.png,

log https://dl.dropboxusercontent.com/u/30169329/build.log, pool.txt
https://dl.dropboxusercontent.com/u/30169329/pool.txt

>Not from that list itself, no. But maybe for other reasons (such as
>missing 'lb clean' and previously using '.list' by mistake instead of
>'.list.chroot').

I'll make this perfectly clear. This occurs with a new fresh Debian install
and new fresh install of Live Build that has never been used. I have not
used  just ".list" by mistake for over 12 months. I used name.list.chroot.
for all but the ndis.list.binary.

>A directory listing of the pool would be useful.

Please refer to the pool.txt link above.


>Retest, making sure you 'lb clean' first. Then if it still fails,
include the information indicated above in the manner I requested.

I have been doing this since last year religiously using lb clean (even on
new installs), lb config, and then lb build. Nothing changes. I am
presenting the information the best way I can but may need some guidance.
Please note nothing fails, I get a working iso after the process is
complete my only concern is the size of the pool folder and from my
understanding I shouldn;t have a pool folder for anything but ndis packages
and its dependencies. If I do have a pool folder it should not be as big as
it is when my package.list are name.list.chroot apart from
ndis.list.binary. I see many packages are .udeb files so I am assuming they
are required to install the live image onto a hard drive but I wonder if
this is the case for the .deb files. if it is not how can I minimise this,
maybe, wasted resource


>Thanks. You should always specify the live-build version#, as shown by
>"dpkg -l live-build" just to be completely unambiguous.

Here is my dpkg -l live-build

uluru-mate@michael-laptop:~$ dpkg -l live-build
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  live-build 3.0.5-1  all  Live System Build Scripts
uluru-mate@michael-laptop:~$

Cheers.

P.S. Sorry about the previous message only going to you.


On 26 June 2013 19:55, Ben Armstrong  wrote:

> First of all, what's with putting the whole message in the Subject:
> field of your email? I had to copy and hand reformat the whole thing
> below. Please don't let that happen again.
>
> On 26/06/13 06:21 AM, Michael . wrote:
> > Re: Trying to build minimal live cd but get large /pool folder in the >
> iso image.
>
> You may have forgotten to 'lb clean' between builds. You should include
> your log.
>
> > Please find attached my auto config and also my config
> > folder (tar.gz).
>
> No, we never received any message from you with either of these things.
> If your config was particularly large, it may have been rejected by the
> mailing list software due to size. Please post at a publicly accessible
> location instead. You should also post your log.
>
> > As far as I am aware if I use packages.list.chroot I
> > should not get a pool folder.
>
> Not from that list itself, no. But maybe for other reasons (such as
> missing 'lb clean' and previously using '.list' by mistake instead of
> '.list.chroot').
>
> > I do 

Re: large /pool folder in the iso image

[Michael .]

>OK, this is normal when you include the installer. And i386 architecture
>is a worst case scenario because both 486 and 686-pae kernel udebs are
>included. With amd64 installer, at least you only have the one kernel
>flavour, amd64.

Thank you. OK, not worrying about the architecture, because it is a similar
size with amd64 anyway, is there a "best practise" method to minimise this?
By your reply it seems the udebs are required regardless of what installer
is used. Is this correct? I only want a live system that can be installed.
I don't want the installer to "pull packages" from a pool like a regular
installer if I can stop it. Is this possible with Debian Live?

>It's not wasted if you really do want the installer.

What about the debs (not the udebs)? are they also required?

Cheers.



On 28 June 2013 10:53, Ben Armstrong  wrote:

> On 06/27/2013 07:51 PM, Michael . wrote:
> >>A directory listing of the pool would be useful.
> >
> > Please refer to the pool.txt link above.
>
> OK, this is normal when you include the installer. And i386 architecture
> is a worst case scenario because both 486 and 686-pae kernel udebs are
> included. With amd64 installer, at least you only have the one kernel
> flavour, amd64.
>
> > if it is not how can I minimise this, maybe, wasted resource
>
> It's not wasted if you really do want the installer.
>
> Ben
>
>

Re: large /pool folder in the iso image

[Michael .]

Ok thanks, I'll work through my different lists now to see where I can
minimise this.


On 28 June 2013 18:57, Ben Armstrong  wrote:

> On 27/06/13 10:54 PM, Michael . wrote:
> > By your reply it seems the udebs are required regardless
> > of what installer is used. Is this correct?
>
> Yes, and the live installer has less overhead than the standard
> installer, but it is still a significant amount of space.
>
> > I only want a live system
> > that can be installed. I don't want the installer to "pull packages"
> > from a pool like a regular installer if I can stop it. Is this possible
> > with Debian Live?
>
> The udebs are for bootstrapping the install, so those are required to
> make the installer work. That's non-negotiable.
>
> >>It's not wasted if you really do want the installer.
> >
> > What about the debs (not the udebs)? are they also required?
>
> The installer needs some debs as well. While the installer uses the live
> system itself instead of a normal bootstrap to do a "live" install,
> other things after that stage depend on choices the user makes and, as I
> understand it, are where the debs come into play.
>
> Together, the udebs and debs make up about 119M on i386 or 92M on amd64
> for our prebuilt wheezy gnome images. I have not yet measured them on
> the other flavours, but I would expect them to be the same size. I do
> not consider this to be excessive. You've reported higher figures but,
> as you have indicated, you have included some additional packages for
> ndiswrapper. That would include every dependency needed to install those
> packages, so it does add up.
>
> Ben
>
>

Re: #89 tutorial backup failure

[Michael .]

I think you will find this is not even a Linux problem but rather the OP
has tried doing something with Windows and it has not worked, he has then
somehow interpreted a message about live.log as an email address to ask for
help. Just my 2 cents, I may be wrong.


On 26 August 2013 19:07, Ben Armstrong  wrote:

> On 25/08/13 10:51 PM, The Outlaw wrote:
> > This email address came up when I tried to make an automatic Windows
> > backup backup that "failed." I was using the #89 Tutorial.  It listed a
> > "/live.log" file that I cannot find.  Can you help determine why this
> > backup failed.  I've made this backup on my laptop and it works as
> > advertised.
>
> Please provide us with:
>
> - what, exactly, you're trying to accomplish
> - the version of live-build you're using
> - the URL to the tutorial you're following ("the #89 tutorial" means
> nothing to me)
> - the backup failure output (exact error message text)
> - what you mean by "it works as advertised" -- you said the backup
> failed ...
>
> It would be a good time to review the section in live-manual on "Bugs",
> as you've failed to provide even the barest details on which we could
> formulate a useful response.
>
> Thanks,
> Ben
>
>
> --
> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/521b1add.9050...@sanctuary.nslug.ns.ca
>
>

Re: Live Build Unable to locate package linux-image-*

[Michael .]

When you have --architecture i386
you don't have to put --linux-flavor "486 686-pae"
because it will get both automatically.

If you only want 686-pae then you use --linux-flavor "686-pae" or likewise
if you only want 486 you only put --linux-flavor "486"

I also never use linux-packages "linux headers"

Try that and see how you go.


On 20 November 2013 09:37, Luigi Cirillo  wrote:

> Hello, I am trying to build a custom live starting from debian standard
> live.
> -
> lb config --config git://live-systems.org/git/live-images.git
> -
> I changed the config file:
> -
> lb config noauto \
>--clean \
>--ignore-system-defaults \
>--mode debian \
>--debian-installer live \
> --architectures i386 \
>--linux-flavours "486 686-pae" \
>--linux-packages "linux-image linux-headers" \
>--source "true" \
> 
> But "lb build" return
> 
> Package linux-headers-686-pae is not available, but is referred to by
> another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Unable to locate package linux-image-486
> E: Unable to locate package linux-headers-486
> E: Unable to locate package linux-image-686-pae
> E: Package 'linux-headers-686-pae' has no installation candidate
> P: Begin unmounting filesystems...
> P: Saving caches...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> ---
> Why the kernel is missing?
>
> I am using live-build 3.0.5-1 on Debian Wheezy amd64
> Thank You
>
>
> --
> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> http://lists.debian.org/cag0ki35tg-hcc3o3cctfxvzcc-dm5nnds2lbwzio8a1ecj0...@mail.gmail.com
>
>