Custom Query (894 matches)

1. In interactive mode, the client asks whether to upgrade packages. However, the proposed version might be older than the installed one.

Upgrade Package netbase (4.28 -> 4.27)? (y/N)
}}}}

I'm not sure whether we can always have a credible way to check which package is newer, so maybe the best (or at least easiest) fix is to change the text to something like "Upgrade/downgrade Package".

2. With ConfigFile entries, the client asks this question for any kind of anomaly:

{{{
Would you like to install ConfigFile: /etc/hosts? (y/N):
}}}

This question should better indicate what is going to happen if one says "y" here. It might mean installing a whole new file or changing file contents and/or permissions/ownership. (Yes, the client might have printed lines such as "ConfigFile /etc/hosts permissions wrong: are 0640 should be 0644" but they are not necessarily adjacent to the question.) How many different question texts are needed?

1. In interactive mode, the client asks whether to upgrade packages. However, the proposed version might be older than the installed one.

Upgrade Package netbase (4.28 -> 4.27)? (y/N)

I'm not sure whether we can always have a credible way to check which package is newer, so maybe the best (or at least easiest) fix is to change the text to something like "Upgrade/downgrade Package".

2. With ConfigFile? entries, the client asks this question for any kind of anomaly:

Would you like to install ConfigFile: /etc/hosts? (y/N):

This question should better indicate what is going to happen if one says "y" here. It might mean installing a whole new file or changing file contents and/or permissions/ownership. (Yes, the client might have printed lines such as "ConfigFile? /etc/hosts permissions wrong: are 0640 should be 0644" but they are not necessarily adjacent to the question.) How many different question texts are needed?

This seems odd. When running the client as "bcfg2 -q -d -v -I -r all", diffs are printed for only some of the changes config files.

Well, this might actually be the same bug as #365. Maybe the #365 error occurs when printing diffs on config files that include non-utf8 data.