Uploaded image for project: 'BoxGrinder Build'
  1. BoxGrinder Build
  2. BGBUILD-210

In Fedora 14 parameters are not being expanded, and cause early string truncation.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 0.9.1
    • Fix Version/s: 0.9.2
    • Component/s: Core
    • Labels:
    • Environment:

      ALL

    • Steps to Reproduce:
      Hide

      Build modular test appliances, error emanates from boxgrinder-appliances/testing-appliances/modular-appls/_repos_boxgrinder_permanent_noarch.appl

      https://github.com/msavy/boxgrinder-appliances/blob/master/testing-appliances/modular-appls/_repos_boxgrinder_permanent_noarch.appl

      Show
      Build modular test appliances, error emanates from boxgrinder-appliances/testing-appliances/modular-appls/_repos_boxgrinder_permanent_noarch.appl https://github.com/msavy/boxgrinder-appliances/blob/master/testing-appliances/modular-appls/_repos_boxgrinder_permanent_noarch.appl
    • Workaround Description:
      Hide

      For test day volunteers:
      <msavy> edit boxgrinder-appliances/testing-appliances/modular-appls/_test_base.appl, comment out (or remove) line 13. Note this in your references, and see if you can build successfully from this point

      Otherwise:
      None, wait for fix.

      Show
      For test day volunteers: <msavy> edit boxgrinder-appliances/testing-appliances/modular-appls/_test_base.appl, comment out (or remove) line 13. Note this in your references, and see if you can build successfully from this point Otherwise: None, wait for fix.

      Description

      Test Day volunteer verdurin triggered this issue when doing the modular appliances test-build https://fedoraproject.org/wiki/QA:TestCase_boxgrinder_modular_test_appliances_build.

      Paths that utilise parameters such as #BASE_ARCH# cause string truncation, so http://example.com/#BASE_ARCH/#SOMETHING#/blah becomes http://example.com, and hence the repo metadata isn't found.

      This happens in all revisions of Fedora. It was previously (incorrectly) thought to be F14 only, but this was due to a tester accidentally forgetting to update to 0.9.1 and using 0.9.0 before the new parser.

      See comments section for reason for this new problem.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                goldmann Marek Goldmann
                Reporter:
                msavy Marc Savy
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: