On 01/24/15 14:14, Steven Shiau wrote:
So is this option no more in live-build 4.x or is the manual wrong?
i've removed that some time ago; what's your use case for pulling
$dist-updates *not* from the same mirror that contains $dist in the
first place?
--
Address:Daniel Baumann,
On 01/25/2015 05:08 PM, Daniel Baumann wrote:
On 01/24/15 14:14, Steven Shiau wrote:
So is this option no more in live-build 4.x or is the manual wrong?
i've removed that some time ago; what's your use case for pulling
$dist-updates *not* from the same mirror that contains $dist in the
first
Yeah, the manuals are very much out of date with respect to the code
unfortunately. I have been doing bits of work here and there to update
them, the largest single instance of which is covered by bug #774730. I
haven't yet thoroughly combed through the set of parameters, but I have
provided fixes
Hi jnqnfe,
Got it. Thanks for your explanation. I believe Daniel has a good reason
for that.
For the time being, I could use put the repository in config/archives/
so that's not a big problem to me.
Thanks.
Steven.
On 01/25/2015 11:35 AM, jnqnfe wrote:
Yes, the basic mirror
Thanks for your reply.
Since jessie-updates exists, e.g.
http://ftp.debian.org/debian/dists/
Could you please tell me why the flexibility to assign the parent mirror
binary updates URL is removed in live-build v4?
Does it mean the parent updates URL must use the same repository as that
Yes, the basic mirror (LB_PARENT_MIRROR_CHROOT / LB_MIRROR_CHROOT /
LB_PARENT_MIRROR_BINARY / LB_MIRROR_BINARY, where appropriate) is used
also as the updates mirror, with no way to use a different mirror
specifically for such updates.
As long as LB_UPDATES is set to true, an updates entry will
Dear all,
In the manual of live-build 4.0.4-1, option
--parent-mirror-binary-updates is shown:
$ man -P cat lb_config | grep -- --parent-mirror-binary-updates
[--parent-mirror-binary-updates URL]
--parent-mirror-binary-updates URL
However, when I ran lb config with this option,
