<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-live-build.git/scripts/build/chroot_resolv, branch cla</title>
<subtitle> (mirror of https://github.com/vyos/vyos-live-build.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-live-build.git/atom?h=cla</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-live-build.git/atom?h=cla'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/'/>
<updated>2020-10-27T15:07:11+00:00</updated>
<entry>
<title>Added the option to include files before and after package installation</title>
<updated>2020-10-27T15:07:11+00:00</updated>
<author>
<name>Thore Sommer</name>
<email>debian@thson.de</email>
</author>
<published>2020-10-27T15:07:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=7360d50fa6b7ef4809d28cf873ab7d29dc2a6f97'/>
<id>urn:sha1:7360d50fa6b7ef4809d28cf873ab7d29dc2a6f97</id>
<content type='text'>
Moved includes.chroot to includes.chroot_after_packages and added
includes.chroot_before_packages. includes.chroot does still work as before.

We also now use rsync for copying files if it is installed.
This improves runtime and space consumption for large includes.

Gbp-Dch: Short
Closes: #927128
</content>
</entry>
<entry>
<title>adjust action arg consumption order</title>
<updated>2020-05-03T00:31:47+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-05-02T23:58:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=43b4f9cdf62972bff5cff45f895305c391a895f2'/>
<id>urn:sha1:43b4f9cdf62972bff5cff45f895305c391a895f2</id>
<content type='text'>
did not properly consider all usage cases properly in deciding placement.

this captured `--usage` in `$PROGRAM --usage` as the action for instance.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>output error for incorrect action in chroot prep scripts</title>
<updated>2020-05-02T12:46:41+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-05-02T12:41:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=da1fab116139150db562eb2c104dea55b7535a33'/>
<id>urn:sha1:da1fab116139150db562eb2c104dea55b7535a33</id>
<content type='text'>
...alongside printing usage (which is perhaps unnecessary), so that it is
actually clear to users that a problem occurred, and what.

and capture it before option processing of remaining args.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>chroot_resolve: fix broken network connectivity</title>
<updated>2020-04-23T19:53:31+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-04-23T18:55:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=10bbb095a8bab26a91288f737d464c4d025d8682'/>
<id>urn:sha1:10bbb095a8bab26a91288f737d464c4d025d8682</id>
<content type='text'>
introduced by an issue with the implementation of
91d446d93ed717b1082bb646fbef65cd1cbc25f5

the introduced of that commit caused builds to fail doing `apt-get update`
or downloading packages and such.

this tweak fixes the problem.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>stagefiles: guard unnecessary chroot removal</title>
<updated>2020-04-23T17:26:15+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-04-02T19:23:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=d79c96232b40fb082233c97ac8d4f75b821ecefe'/>
<id>urn:sha1:d79c96232b40fb082233c97ac8d4f75b821ecefe</id>
<content type='text'>
just as most scripts are skipped if their stagefile exists (indicating
that they have already been run to completion), including chroot
preparation scripts in install mode, this implements the same guard for
chroot prep remove mode, such that they exit early if their stagefile
does not exist, indicating that the modification has already been removed.
(also override-able by --force in the same way).

this basically just uses a tweaked copy of Check_stagefile().

Gbp-Dch: Short
</content>
</entry>
<entry>
<title>Use descriptive parameter names for Usage()</title>
<updated>2020-04-23T14:38:59+00:00</updated>
<author>
<name>Raphaël Hertzog</name>
<email>hertzog@debian.org</email>
</author>
<published>2020-04-23T14:38:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=4c75f80e6763490d5bcb0e0a460b096a3292ae61'/>
<id>urn:sha1:4c75f80e6763490d5bcb0e0a460b096a3292ae61</id>
<content type='text'>
</content>
</entry>
<entry>
<title>usage: take exit code as param</title>
<updated>2020-04-23T14:32:26+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-03-30T16:32:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=b3bba232ac6e1feff9e506506247aa20cd7f467c'/>
<id>urn:sha1:b3bba232ac6e1feff9e506506247aa20cd7f467c</id>
<content type='text'>
thus it can correctly indicate success/fail status instead of always
indicating failure. when a user asks for usage with -u|--usage then we
should exit in success mode rather than failure as when usage in printed
in response to incorrect usage.

Gbp-Dch: Short
</content>
</entry>
<entry>
<title>Fix permissions &amp; ownership of copied /etc/resolv.conf</title>
<updated>2020-04-23T10:20:35+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-04-10T01:44:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=91d446d93ed717b1082bb646fbef65cd1cbc25f5'/>
<id>urn:sha1:91d446d93ed717b1082bb646fbef65cd1cbc25f5</id>
<content type='text'>
Closes: #857740

[tweaked by Raphaël Hertzog to fix the chown root:root call]
</content>
</entry>
<entry>
<title>stagefiles: s/Require_stagefile/Require_stagefiles/</title>
<updated>2020-03-17T22:59:37+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-03-15T13:05:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=fb0790cc4379280084cc9a4469a515e243f45b9b'/>
<id>urn:sha1:fb0790cc4379280084cc9a4469a515e243f45b9b</id>
<content type='text'>
this function takes one or more required stage fileS _plural_, and exits
if any are missing (or at least it does now after the refactor).

let's rename it to make things more clear

Gbp-Dch: Short
</content>
</entry>
<entry>
<title>stagefiles: further robustify with auto filenames</title>
<updated>2020-03-17T18:57:02+00:00</updated>
<author>
<name>Lyndon Brown</name>
<email>jnqnfe@gmail.com</email>
</author>
<published>2020-03-13T17:11:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-live-build.git/commit/?id=fe9195b59c9647598ecea00900edfe2678bddcac'/>
<id>urn:sha1:fe9195b59c9647598ecea00900edfe2678bddcac</id>
<content type='text'>
as suggested by Raphaël

rather than have fixed stagefile filename strings at all in the scripts,
use `$(basename $0)` to use the name of the script (which is the same for
almost all cases anyway, and the stage files are supposed to be almost
exclusively unique per-script). we can thus simplify things by determining
the filename for most use cases within the functions themselves.

this does change the file used by a couple of scripts, affecting backwards
compatibility of executing live-build upon an existing partially or fully
completed build:
 - binary_grub-pc used "binary_grub"
 - chroot_includes used "includes.chroot"

care had to be taken for the following cases:
 - there are some cases like bootstrap_cache, source_debian and
   bootstrap_debootstrap which are dealing with more than one file, and/or
   otherwise a filename that is not specific to the script itself exactly,
   or should not be based upon its name.
 - some cases like chroot_cache, bootstrap_cache and
   chroot_install-packages need to append something to the end of the name
   depending upon which pass/action mode the script is being executed with.
 - furthermore in the bootstrap_cache case one of the filenames is used
   within the bootstrap_debootstrap and thus needs very careful handling
   to be certain that a change in filename of bootstrap_cache does not
   break bootstrap_debootstrap.

Gbp-Dch: Short
</content>
</entry>
</feed>
