Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: TLP Admin
    • Labels:
      None

      Description

      UNIX Name: jspwiki (jspwiki.apache.org)
      DNS entry
      Unix/LDAP group creation [#1]
      PMC Chair karma [#1]
      mailing list migration [#2]
      Subversion public tree migration [#3]
      buildbot config changes
      website migration [#4]

      Notes:

      [#1]: seems to be created
      {code}
      juanpablo@minotaur:~$ list_unix_group.pl jspwiki
      ajaquith
      altheim
      brushed
      clr
      csauer
      florianh
      gmazza
      henning
      jalkanen
      juanpablo
      metskem
      rubys
      snoopdave
      {code}

      [#2]: all the lists have been already migrated:
      * user@jspwiki.apache.org
      * dev@jspwiki.apache.org
      * commits@jspwiki.apache.org
      * private@jspwiki.apache.org

      however we don't know who has admin-list karma (=power to moderate, see how many people are subscribed to each list, etc.). We need that role for [any|every]body in the LDAP group.

      [#3] seems to be migrated: http://svn.apache.org/repos/asf/jspwiki/ However, although having the ldap group created (cfr. [#1]), seems we're not yet allowed to make commits. As the LDAP group is created and populated, is there any other thing to do that we may have missed? Also, see INFRA-6492 for related details

      [#4] JIRAs already opened related to this issue: INFRA-6492, INFRA-5943 (not directly related to migration, but would be nice if easily doable)

        Issue Links

          Activity

          Hide
          #asfinfra IRC Bot added a comment -
          <danielsh> Let's close this, INFRA-6492 is basically a duplicate of what remains to be done here. Please add any further information there.
          Show
          #asfinfra IRC Bot added a comment - <danielsh> Let's close this, INFRA-6492 is basically a duplicate of what remains to be done here. Please add any further information there.
          Hide
          #asfinfra IRC Bot added a comment -
          <danielsh> Let's close this, INFRA-6492 is basically a duplicate of what remains to be done here. Please add any further information there.
          Show
          #asfinfra IRC Bot added a comment - <danielsh> Let's close this, INFRA-6492 is basically a duplicate of what remains to be done here. Please add any further information there.
          Hide
          #asfinfra IRC Bot added a comment -
          <danielsh> Let's close this, * View on Board
          Show
          #asfinfra IRC Bot added a comment - <danielsh> Let's close this, * View on Board
          Hide
          #asfinfra IRC Bot added a comment -
          <danielsh> I'm guessing the CMS update somehow didn't happen.... (/usr/local/cms/wc/jspwiki still has dev_list and checkouts of incubator)
          Show
          #asfinfra IRC Bot added a comment - <danielsh> I'm guessing the CMS update somehow didn't happen.... (/usr/local/cms/wc/jspwiki still has dev_list and checkouts of incubator)
          Hide
          Juan Pablo Santos Rodríguez added a comment -
          Hi Danielsh,

          just created INFRA-6611; I've also forced a full WC, but the svn message still persists

          thanks for your time looking into this
          Show
          Juan Pablo Santos Rodríguez added a comment - Hi Danielsh, just created INFRA-6611 ; I've also forced a full WC, but the svn message still persists thanks for your time looking into this
          Hide
          #asfinfra IRC Bot added a comment -
          <danielsh> I see the problem: the 301 Permanent Redirect response is given to the second request (a REPORT), not to the initial OPTIONS request. Can you please open a new issue about this? In the meantime, "Force a new WC" via the CMS UI. (I tried a 'swtitch', but that triggered APR_INCOMPLETE...)
          Show
          #asfinfra IRC Bot added a comment - <danielsh> I see the problem: the 301 Permanent Redirect response is given to the second request (a REPORT), not to the initial OPTIONS request. Can you please open a new issue about this? In the meantime, "Force a new WC" via the CMS UI. (I tried a 'swtitch', but that triggered APR_INCOMPLETE...)
          Hide
          Juan Pablo Santos Rodríguez added a comment -
          Hi Danielsh,

          I'm afraid I didn't explain clearly previously, the message appears when using the CMS bookmarklet (my working copy is ok, I can update, commit, etc, but the changes don't propagate to the site), the complete message:

          Updating 'usr/local/cms/wc/jspwiki/juanpablo-9Enkzj/trunk/content/jspwiki':
          svn: E175011: Repository moved permanently to 'https://svn.apache.org/repos/asf/jspwiki/site/trunk/content&#39;; please relocate

          probably I'm missing something obvious, but how do I relocate on usr/local/etc.?

          Lastly, of course it's ok to get handled INFRA-6492 on due course, thought it was related to the svn message when updating


          br,
          juan pablo


          Show
          Juan Pablo Santos Rodríguez added a comment - Hi Danielsh, I'm afraid I didn't explain clearly previously, the message appears when using the CMS bookmarklet (my working copy is ok, I can update, commit, etc, but the changes don't propagate to the site), the complete message: Updating 'usr/local/cms/wc/jspwiki/juanpablo-9Enkzj/trunk/content/jspwiki': svn: E175011: Repository moved permanently to ' https://svn.apache.org/repos/asf/jspwiki/site/trunk/content&#39;; please relocate probably I'm missing something obvious, but how do I relocate on usr/local/etc.? Lastly, of course it's ok to get handled INFRA-6492 on due course, thought it was related to the svn message when updating br, juan pablo
          Hide
          #asfinfra IRC Bot added a comment -
          <danielsh> 1. Do what the error message says ('svn relocate https://svn.apache.org/repos/asf/jspwiki/site/trunk/content&#39;, if your working copy root's URL is trunk/content/). 2. This is INFRA-6577. INFRA-6492 is a separate ticket which is outstanding. It will be handled in due course.
          Show
          #asfinfra IRC Bot added a comment - <danielsh> 1. Do what the error message says ('svn relocate https://svn.apache.org/repos/asf/jspwiki/site/trunk/content&#39;, if your working copy root's URL is trunk/content/). 2. This is INFRA-6577 . INFRA-6492 is a separate ticket which is outstanding. It will be handled in due course.
          Hide
          Juan Pablo Santos Rodríguez added a comment -
          Hi,

          the website migration is almost there. When trying to update any resource we get a "svn: E175011: Repository moved permanently to 'https://svn.apache.org/repos/asf/jspwiki/site/trunk/content&#39;; please relocate" message.

          Also, according to INFRA-6492, the website location should be https://svn.apache.org/repos/asf/incubator/jspwiki/trunk/jspwiki-site/src/site/trunk instead of https://svn.apache.org/repos/asf/incubator/jspwiki/site/trunk


          thx + br,
          juan pablo
          Show
          Juan Pablo Santos Rodríguez added a comment - Hi, the website migration is almost there. When trying to update any resource we get a "svn: E175011: Repository moved permanently to ' https://svn.apache.org/repos/asf/jspwiki/site/trunk/content&#39;; please relocate" message. Also, according to INFRA-6492 , the website location should be https://svn.apache.org/repos/asf/incubator/jspwiki/trunk/jspwiki-site/src/site/trunk instead of https://svn.apache.org/repos/asf/incubator/jspwiki/site/trunk thx + br, juan pablo

            People

            • Assignee:
              Unassigned
              Reporter:
              Juan Pablo Santos Rodríguez
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Review Date:

                Development