Re: Missing "--parent-mirror-binary-updates" for live-build 4.x?
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 (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 be written
> to the apt source config. You can control this via the --updates param,
> and it is currently set to false by default for sid and jessie, and true
> for everything else. Actually, I think you've helped highlight a bug
> here, being false for jessie looks like a mistake, in fact the same is
> true for the security source. Setting sid and jessie to false, per git
> history, was done as "future proofing" in v3.x, and jessie should
> probably have been removed from that in 4.x, I'll create a bug report
> and patch for that.
>
> Daniel (the maintainer and author of live-build) deliberately removed
> the capability to specify an updates specific mirror back in version
> 4.0_a16-1, which I can see by checking the git history. The specific
> commit that removed it (68700f466c142082e7423282ca4caaf7552bf8e9) has
> the following comment attached:
>
> "Dropping dedicated updates (formerly volatile) mirror handling, not
> needed anymore."
>
> I imagine he had good reasons for removing it, but if you want to argue
> the case for getting it back, by all means put forward your case, and if
> he seems willing for it to be reintroduced, build a patch and submit it
> with wishlist severity to the BTS.
>
>
> On 25/01/2015 02:19, Steven Shiau wrote:
>> 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
>> --parent-mirror-binary?
>> If you think it's OK to have it back, for sure I could help to have a
>> patch for that.
>> Thank you very much.
>>
>> Steven.
>>
>> On 01/25/2015 08:32 AM, jnqnfe wrote:
>>> 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 for one or two similar discrepancies in them here and
>>> there in patches currently waiting for review, I'll add yours to the
>>> todo list.
>>>
>>> Of course you're very welcome to help and go through it yourself.
>>>
>>>
>>> On 24/01/2015 13:14, Steven Shiau wrote:
>>>> 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, it gave me an error:
>>>> $ lb config --parent-mirror-binary-updates http://ftp.debian.org/
>>>> [2015-01-24 21:12:03] lb config --parent-mirror-binary-updates
>>>> http://ftp.debian.org/
>>>> lb config: unrecognized option '--parent-mirror-binary-updates'
>>>>
>>>> This option does exist in live-build 3.x.
>>>> So is this option no more in live-build 4.x or is the manual wrong?
>>>> Thanks.
>>>>
>>>> Steven.
>>>>
--
Steven Shiau <steven _at_ stevenshiau org>
Public Key Server PGP Key ID: 4096R/47CF935C
Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C
Reply to: