Re: [sbabic/libubootenv] Non-existing devices results in parsing error (Issue #33)

[Stefano Babic]

Hi,

please see that the only place for discussion about this project is the
Mailing List. It is just a case I found this:

On 2/17/26 14:27, Alexander Dahl wrote:
> *LeSpocky* left a comment (sbabic/libubootenv#33) <https://github.com/
> sbabic/libubootenv/issues/33#issuecomment-3914707799>
>
> Anyone having a good idea or even solution for this problem? I'd like to
> use libubootenv's /fw_setenv///fw_printenv/ with a config like this for
> a device which has its env in either nor or nand flash:
>
> # See: https://github.com/sbabic/libubootenv/blob/master/docs/
> fw_env_config.md
> ---
> nor:
> size:0x10000
> devices:
> -path:/dev/mtd/nor/env1
> -path:/dev/mtd/nor/env2
>
> nand:
> size:0x20000
> devices:
> -path:/dev/mtd/nand/env1
> -path:/dev/mtd/nand/env2
>

I confirm that this use case is not supported.

> The proposed solution in #37 <https://github.com/sbabic/libubootenv/
> pull/37> seems more like a quick and dirty hack to me.

The right solution is to rearrange code and call check_env() when this
is used. This must be caleld just once, that is the reason it is now
done as extension of the configuration (really, I haven't taken into
account this use case). So the proposed solution is a hack, but the
right solution must be implemented.

Best regards,
Stefano Babic

[Alexander Dahl]

Hello Stefano,

Stefano Babic schrieb am Mittwoch, 18. Februar 2026 um 10:39:25 UTC+1:

Hi,

please see that the only place for discussion about this project is the
Mailing List.

Maybe you should configure your GitHub project to not allow opening issues and pull requests then? 

You could disable them through https://github.com/sbabic/libubootenv/settings … but I don't know what happens to old issues / pull-requests then. The current state is confusing and frustrating for contributors, because it looks like the project is not maintained. The GitHub repo is the official upstream repo for libubootenv, right?

Greets

Alex

[Stefano Babic]

Hi Alexander,

On 2/18/26 11:26, Alexander Dahl wrote:
> Hello Stefano,
>
> Stefano Babic schrieb am Mittwoch, 18. Februar 2026 um 10:39:25 UTC+1:
>
> Hi,
>
> please see that the only place for discussion about this project is the
> Mailing List.
>
>
> Maybe you should configure your GitHub project to not allow opening
> issues and pull requests then?

It wasn't possible, I see now it is allowed, thanks. Issues are away.

> You could disable them through https://github.com/sbabic/libubootenv/
> settings … but I don't know what happens to old issues / pull-requests
> then. The current state is confusing and frustrating for contributors,
> because it looks like the project is not maintained. The GitHub repo is
> the official upstream repo for libubootenv, right?

The repos is the official repo for the project - contributors have just
to *read* the first page and the section "Contributing to the project"
to feel not frustrated....

Best regards,
Stefano

>
> Greets
> Alex
>
> It is just a case I found this:
>
> On 2/17/26 14:27, Alexander Dahl wrote:
> > *LeSpocky* left a comment (sbabic/libubootenv#33) <https://

> github.com/ <https://github.com/>

> > sbabic/libubootenv/issues/33#issuecomment-3914707799>
> >
> > Anyone having a good idea or even solution for this problem? I'd
> like to
> > use libubootenv's /fw_setenv///fw_printenv/ with a config like
> this for
> > a device which has its env in either nor or nand flash:
> >
> > # See: https://github.com/sbabic/libubootenv/blob/master/docs/
> <https://github.com/sbabic/libubootenv/blob/master/docs/>
> > fw_env_config.md
> > ---
> > nor:
> > size:0x10000
> > devices:
> > -path:/dev/mtd/nor/env1
> > -path:/dev/mtd/nor/env2
> >
> > nand:
> > size:0x20000
> > devices:
> > -path:/dev/mtd/nand/env1
> > -path:/dev/mtd/nand/env2
> >
>
> I confirm that this use case is not supported.
>
> > The proposed solution in #37 <https://github.com/sbabic/

> libubootenv/ <https://github.com/sbabic/libubootenv/>

> > pull/37> seems more like a quick and dirty hack to me.
>
> The right solution is to rearrange code and call check_env() when this
> is used. This must be caleld just once, that is the reason it is now
> done as extension of the configuration (really, I haven't taken into
> account this use case). So the proposed solution is a hack, but the
> right solution must be implemented.
>
> Best regards,
> Stefano Babic
>

> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> swupdate/5c92fd6f-6dcd-4b1c-a60c-0be43b82277fn%40googlegroups.com
> <https://groups.google.com/d/msgid/swupdate/5c92fd6f-6dcd-4b1c-
> a60c-0be43b82277fn%40googlegroups.com?utm_medium=email&utm_source=footer>.