Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4997

MaxScale: BUILD/install_build_deps.sh: deprecated --force-yes

    XMLWordPrintable

Details

    Description

      [COPY FROM MAILING LIST]
      Hi dear MaxScale contributors
      I've tried to build MaxScale from source code on 23.08 and noticed the use of `--force-yes` flag with apt-get which is deprecated in 1.1 version of apt-get and results a warning log:
      W: --force-yes is deprecated, use one of the options starting with --allow instead.
      I think we should use --allow even we should all --allow flags, but also I think not all them are useful.
      Here is complete list:
      --allow-downgrades
      --allow-remove-essential
      --allow-change-held-packages
      --allow-unauthenticated
      --allow-insecure-repositories
      --allow-releaseinfo-change

      I'll research on real use cases and open a PR if you confirm on this email. I'm also interested on background of this flag and the reason it used as it should used in very special cases.

      Sincerely,
      Salar Nosrati-Ershad

      [COPY FROM MAILING LIST]
      Hi,

      The --force-yes has been there for a long time. I don't think it's even needed and should probably just be removed. The change is simple to implementbut the problem is testing it on all of the Ubuntu/Debian versions that MaxScale supports. If you want to, you can open a Jira issue and the MaxScale developers can fix it as we have the capability to easily verify that it doesn't break the builds.

      Markus

      Attachments

        Activity

          People

            markus makela markus makela
            s3r Salar Nosrati-Ershad
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.