Re: Why is lb config using stretch repos instead of buster?
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, jnqnfe@gmail.com <jnqnfe@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 , <jnqnfe@gmail.com> 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 007@caiway.net, <007@caiway.net>
>> > > wrote:
>> > > > On Thu, 23 Apr 2020 13:49:05 +0530
>> > > >
>> > > > Harshad Joshi <firewalrus@gmail.com> 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 , <jnqnfe@gmail.com> 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 , <jnqnfe@gmail.com> 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 values, they don't get
>> > > > updated per
>> > > >
>> > > > > > the change you're trying to make.
>> > > >
>> > > > > >
>> > > >
>> > > > > > There are some options that automatically get set per the
>> > > >
>> > > > > > distribution option value. I suspect that the most likely
>> > > > cause of
>> > > >
>> > > > > > your problem is that you've got an existing config with
>> > > > these other
>> > > >
>> > > > > > options set to 'stretch' from your first attempt at
>> > > > creating a
>> > > >
>> > > > > > config, and thus your subsequent use of `lb config --
>> > > > distribution
>> > > >
>> > > > > > buster` is not propagating to those other config options.
>> > > >
>> > > > > >
>> > > >
>> > > > > > The easiest fix for this here (assuming this is indeed the
>> > > > cause)
>> > > >
>> > > > > > is to just delete the existing config directory, then re-
>> > > > run `lb
>> > > >
>> > > > > > config --distribution buster`.
>> > > >
>> > > > > >
>> > > >
>> > > > > >
>> > > >
>> > > > > > On Thu, 2020-04-23 at 11:29 +0530, Harshad Joshi wrote:
>> > > >
>> > > > > >
>> > > >
>> > > > > > Please check attachments sent in this mail. I have
>> > > > configured lb to
>> > > >
>> > > > > > use buster and we can see it is building configuration for
>> > > > debian
>> > > >
>> > > > > > buster distribution
>> > > >
>> > > > > >
>> > > >
>> > > > > > However as per second attachent in next stage of live
>> > > > build, we can
>> > > >
>> > > > > > see it is using stretch repositories to download binary
>> > > > packages
>> > > >
>> > > > > >
>> > > >
>> > > > > > Why is this happening??
>> > > >
>> > > > > >
>> > > >
>> > > > > > --sent from OnePlus device--
>> > > >
>> > > > > >
>> > > >
>> > > > > > On Thu, 23 Apr, 2020, 11:23 AM , <jnqnfe@gmail.com> wrote:
>> > > >
>> > > > > >
>> > > >
>> > > > > > On Thu, 2020-04-23 at 11:16 +0530, Harshad Joshi wrote:
>> > > >
>> > > > > >
>> > > >
>> > > > > > I have downloaded a buster live CD from debian site and I
>> > > > am trying
>> > > >
>> > > > > > to build live CD using buster repository, but live build is
>> > > > using
>> > > >
>> > > > > > stretch repositories by default despite me configuring it
>> > > > to use
>> > > >
>> > > > > > buster lb config -
>> > > >
>> > > > > > - distribution buster
>> > > >
>> > > > > >
>> > > >
>> > > > > > Please help me in resolving this issue.
>> > > >
>> > > > > >
>> > > >
>> > > > > > --sent from OnePlus device--
>> > > >
>> > > > > >
>> > > >
>> > > > > >
>> > > >
>> > > > > > replace: lb config - - distribution buster
>> > > >
>> > > > > > with: lb config --distribution buster
>> > > >
>> > > > > >
>> > > >
>> > > > > > note the unwanted spaces in yours
>> > > >
>> > > > > >
>> > > >
>> > > > > >
>> > > >
>> > > >
>> > > >
>
Reply to: