Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Add --last-ver command line option for mixer init #576

Open
gtkramer opened this issue May 15, 2019 · 2 comments
Open

Enhancement: Add --last-ver command line option for mixer init #576

gtkramer opened this issue May 15, 2019 · 2 comments

Comments

@gtkramer
Copy link

DevOps needs to know about the internals of mixer in order to keep it's operations running when things go wrong. If a build is bad and cannot be used in the update chain for swupd for whatever reason, DevOps currently writes to the LAST_VER file manually with an echo with the proper build that needs to be here. In favor of passing more options at the command line, this LAST_VER should be another option that can be passed during mixer init, just as format can, so that mixer.state is always created correctly prior to starting the mix.

@jwakre jwakre self-assigned this May 16, 2019
@jwakre jwakre removed their assignment Jun 17, 2019
@gtkramer
Copy link
Author

gtkramer commented Jul 24, 2019

Today, this prints the following messages:

$ mixer build update --offline --config /home/clrbuilder/projects/clr-release-tools/chroots/builder.conf --min-version 29750 --format 28 --no-publish --no-signing --native
Warning: Using PREVIOUS_MIX_VERSION default value

It would be beneficial to have a command line option that defined this value, removing the need to warn how mixer.state is managed.

@gtkramer
Copy link
Author

Would be obsoleted with a CLI design similar to #627

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants