Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-8072

Conda-lsst broken when running make-recipes

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      [dev@centos-7 conda-lsst]$ conda lsst make-recipes build:b2317 afw --build
      Traceback (most recent call last):
        File "/opt/conda-lsst/bin/conda-lsst", line 105, in <module>
          config = Config(root_dir, [os.path.expanduser('~/.condalsstrc'), 'etc/conf
      ig.yaml'])
        File "/opt/conda-lsst/conda_lsst/config.py", line 298, in __init__
          ] + _get_our_channels(self.our_channel_regex)
        File "/opt/conda-lsst/conda_lsst/config.py", line 315, in _get_our_channels
          chans = [ urljoin(conda.config.context.channel_alias, str(u)).rstrip('/ '$
       + '/' for u in conda.config.get_rc_urls() ]
        File "/opt/conda-lsst/miniconda/lib/python2.7/urlparse.py", line 259, in ur$
      join
          urlparse(base, '', allow_fragments)
        File "/opt/conda-lsst/miniconda/lib/python2.7/urlparse.py", line 143, in ur$
      parse
          tuple = urlsplit(url, scheme, allow_fragments)
        File "/opt/conda-lsst/miniconda/lib/python2.7/urlparse.py", line 182, in ur$
      split
          i = url.find(':')
      AttributeError: 'Channel' object has no attribute 'find'
      

        Attachments

          Activity

          Hide
          jmatt J Matt Peterson [X] (Inactive) added a comment -

          Trivial change. But still required to use the current conda. It'll be PR'ed with all of v12.1. See commit:

          https://github.com/jmatt/conda-lsst/commit/3243b741c5e2f8652c0c33c6b7d81239431ee412

          Show
          jmatt J Matt Peterson [X] (Inactive) added a comment - Trivial change. But still required to use the current conda. It'll be PR'ed with all of v12.1. See commit: https://github.com/jmatt/conda-lsst/commit/3243b741c5e2f8652c0c33c6b7d81239431ee412
          Hide
          jhoblitt Joshua Hoblitt added a comment -

          Why can't this be PR'd now?

          Show
          jhoblitt Joshua Hoblitt added a comment - Why can't this be PR'd now?
          Hide
          jmatt J Matt Peterson [X] (Inactive) added a comment -

          Fell free to PR it.

          I have all my other changes for 0.12.1 on my v12.1 branch. Previously many of the changes were interdependent on one another so I just put them together on a release branch and moved forward. I was working solo at the time, so there was no reason to do it.

          Show
          jmatt J Matt Peterson [X] (Inactive) added a comment - Fell free to PR it. I have all my other changes for 0.12.1 on my v12.1 branch. Previously many of the changes were interdependent on one another so I just put them together on a release branch and moved forward. I was working solo at the time, so there was no reason to do it.
          Hide
          jhoblitt Joshua Hoblitt added a comment -

          Typically, you don't ask for a review until something is ready to merge. Ready to merge literally means a branch that will be a fast-forward merge into master. Additionally, branch names are how we attach work to a jira issue. How you did your development work is irrelevant at the review stage. Branches are not a finite resource. If you don't want to follow Data Management's basic development work flow, then don't ask for a review.

          Show
          jhoblitt Joshua Hoblitt added a comment - Typically, you don't ask for a review until something is ready to merge. Ready to merge literally means a branch that will be a fast-forward merge into master. Additionally, branch names are how we attach work to a jira issue. How you did your development work is irrelevant at the review stage. Branches are not a finite resource. If you don't want to follow Data Management's basic development work flow, then don't ask for a review.
          Hide
          jmatt J Matt Peterson [X] (Inactive) added a comment -

          Created a PR.

          Show
          jmatt J Matt Peterson [X] (Inactive) added a comment - Created a PR.
          Hide
          jmatt J Matt Peterson [X] (Inactive) added a comment -

          I recommend DM-7666 too since that is another problem related to the current stable conda version.

          Show
          jmatt J Matt Peterson [X] (Inactive) added a comment - I recommend DM-7666 too since that is another problem related to the current stable conda version.
          Hide
          jmatt J Matt Peterson [X] (Inactive) added a comment -

          The Conda v12.1 (semantic version 0.12.1) binaries have been successfully created. The repository for this release is: http://conda.lsst.codes/stack/0.12.1

          Show
          jmatt J Matt Peterson [X] (Inactive) added a comment - The Conda v12.1 (semantic version 0.12.1) binaries have been successfully created. The repository for this release is: http://conda.lsst.codes/stack/0.12.1

            People

            • Assignee:
              jmatt J Matt Peterson [X] (Inactive)
              Reporter:
              jmatt J Matt Peterson [X] (Inactive)
              Reviewers:
              Joshua Hoblitt
              Watchers:
              J Matt Peterson [X] (Inactive), Joshua Hoblitt
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel