Alejandro R Mosteo
Alejandro R Mosteo
This feature is in the roadmap, yes. > it is easy to find yourself with a prior build for the wrong target This shouldn't be happening because the compiler should...
Indeed, thanks for pointing this out.
Thanks for the reproducer, @reznikmm. I'll see if this is easily fixable, I don't see an evident reason why `show` and `printenv` should collide.
Yes, hints are printed if there was no other way to solve the dependency. But we have discussed their removal as we don't really use them (yours would be first?)...
What you want is achieved with `alr settings --show-origin`. Still, it is true that when unsetting we could inform whether the source not being unset is still set.
Curious. For the time being, you can workaround the build step with `--skip-build`.
I can reproduce it, reason being that a compiler isn't available and the default compiler selection is not kicking in.
`update` will clear the post-fetch flag, so the next build will do a post-fetch. `clean` is not clearing such flag, and it's true it makes sense it does. > found...
Thanks for the report, I see the root of the problem is that in `22.04` there is a point number (`1:1.2.11.dfsg-2ubuntu9.2`) that is no longer there in `24.04`. This is...
Fixed in #1704.