Menu

#24111 netwonk: sourceforge update of github code

closed
nobody
None
https://sourceforge.net/p/netwonk/code/ci/main/tree/
netwonk
2023-01-09
2022-12-19
No

My main 'netwonk' repository is on Github.
I mirrored it by Importing all the code to Sourceforge 'netwonk'
I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
Now there are updates to the netwonk Code on Github.
The Sourceforge version of netwonk is not updating.
I can't see any way to make it update.
In short, I am totally lost, and it's all out of sync.
Please help....
Jack

Discussion

  • SourceForge Support

    Hello,

    Our GItHub integration tool works only with file releases.
    However, you can set your git client push to both SF & Github together and keep them in sync https://sourceforge.net/p/forge/documentation/GitHub%20Importer/#source-code

    Sincerely,
    SourceForge Support

     
    • Jack Gallagher

      Jack Gallagher - 2022-12-19

      Thanks for the response -- how does a file release differ?Is that not appropriate for what I'm doing?thanks,Jack

      On Monday, December 19, 2022 at 03:52:29 PM CST, SourceForge Support <sf-support@users.sourceforge.net> wrote:
      

      Hello,

      Our GItHub integration tool works only with file releases.
      However, you can set your git client push to both SF & Github together and keep them in sync https://sourceforge.net/p/forge/documentation/GitHub%20Importer/#source-code

      Sincerely,
      SourceForge Support

      [site-support:#24111] netwonk: sourceforge update of github code

      Status: open
      Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
      Last Updated: Mon Dec 19, 2022 06:22 PM UTC

      Owner: nobody
      My main 'netwonk' repository is on Github.
      I mirrored it by Importing all the code to Sourceforge 'netwonk'
      I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
      Now there are updates to the netwonk Code on Github.
      The Sourceforge version of netwonk is not updating.
      I can't see any way to make it update.
      In short, I am totally lost, and it's all out of sync.
      Please help....
      Jack

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
    • Jack Gallagher

      Jack Gallagher - 2022-12-21

      I'm hitting a further issue.
      this is my git clone text:   ssh://jackg23@git.code.sf.net/p/netwonk/code netwonk-code
      Here's what I get:
      C:\Users\jackg>git remote add sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code netwonk-code
      fatal: not a git repository (or any of the parent directories): .git
      The empty space doesn't seem right in the url.  Things I've tried don't affect anything.
      Ideas?
      thanksJack

      On Monday, December 19, 2022 at 03:52:29 PM CST, SourceForge Support sf-support@users.sourceforge.net wrote:

      Hello,

      Our GItHub integration tool works only with file releases.
      However, you can set your git client push to both SF & Github together and keep them in sync https://sourceforge.net/p/forge/documentation/GitHub%20Importer/#source-code

      Sincerely,
      SourceForge Support

      [site-support:#24111] netwonk: sourceforge update of github code

      Status: open
      Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
      Last Updated: Mon Dec 19, 2022 06:22 PM UTC

      Owner: nobody
      My main 'netwonk' repository is on Github.
      I mirrored it by Importing all the code to Sourceforge 'netwonk'
      I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
      Now there are updates to the netwonk Code on Github.
      The Sourceforge version of netwonk is not updating.
      I can't see any way to make it update.
      In short, I am totally lost, and it's all out of sync.
      Please help....
      Jack

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
      • Dave Brondsema

        Dave Brondsema - 2022-12-22

        When you run the git remote add ... command, make sure you're in the directory of your git repository. The error message you got means you weren't in the right directory.

        And also you are correct you don't a space for this command. git remote add sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code would be the full command to use for this.

        Sincerely,
        SourceForge Support

         
        • Jack Gallagher

          Jack Gallagher - 2022-12-22

          Thanks much Dave, I'll have at it. 

          On Thursday, December 22, 2022 at 01:42:56 PM CST, Dave Brondsema <brondsem@users.sourceforge.net> wrote:
          

          When you run the git remote add ... command, make sure you're in the directory of your git repository. The error message you got means you weren't in the right directory.

          And also you are correct you don't a space for this command. git remote add sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code would be the full command to use for this.

          Sincerely,
          SourceForge Support

          [site-support:#24111] netwonk: sourceforge update of github code

          Status: open
          Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
          Last Updated: Tue Dec 20, 2022 04:17 PM UTC
          Owner: nobody

          My main 'netwonk' repository is on Github.
          I mirrored it by Importing all the code to Sourceforge 'netwonk'
          I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
          Now there are updates to the netwonk Code on Github.
          The Sourceforge version of netwonk is not updating.
          I can't see any way to make it update.
          In short, I am totally lost, and it's all out of sync.
          Please help....
          Jack

          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

           
        • Jack Gallagher

          Jack Gallagher - 2022-12-23

          It seems like I'm almost there.I'm stuck on this:
          $ git push sourceforge main
          Keyboard-interactive authentication prompts from server:
          fatal: protocol error: bad line length character: | Pa

          I've reviewed all my ssh key stuff, and it seems like it should be fine.
          But, no luck yet.What am I missing?Thanks,Jack

          On Thursday, December 22, 2022 at 01:42:56 PM CST, Dave Brondsema <brondsem@users.sourceforge.net> wrote:
          

          When you run the git remote add ... command, make sure you're in the directory of your git repository. The error message you got means you weren't in the right directory.

          And also you are correct you don't a space for this command. git remote add sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code would be the full command to use for this.

          Sincerely,
          SourceForge Support

          [site-support:#24111] netwonk: sourceforge update of github code

          Status: open
          Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
          Last Updated: Tue Dec 20, 2022 04:17 PM UTC
          Owner: nobody

          My main 'netwonk' repository is on Github.
          I mirrored it by Importing all the code to Sourceforge 'netwonk'
          I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
          Now there are updates to the netwonk Code on Github.
          The Sourceforge version of netwonk is not updating.
          I can't see any way to make it update.
          In short, I am totally lost, and it's all out of sync.
          Please help....
          Jack

          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

           
  • SourceForge Support

    Hello,

    You are probably right, it's just a feature we currently don't have.
    We are constantly working on improvements that will be helpful to most of our customers.

    To request that SourceForge.net add new or change existing functionality, post to our Feature Requests system here: https://sourceforge.net/p/forge/feature-requests/

    SourceForge.net staff also pays attention to the voting on Feature Request posts.
    But it is not the only factor considered. If we have a good reason, we may reject a suggestion, even if it has high votes.

    Sincerely,

    SourceForge Support

     
  • SourceForge Support

    Hello,

    Is this still an issue?

    Did you try connecting from a command line or terminal.
    If you can log in "manually", the issue could be in the keys setup.

    Make sure to upload your key here: https://sourceforge.net/auth/shell_services
    Also add them to your client authentication agent and that it is running when you try to connect.

    Sincerely,
    SourceForge Support

     
    • Jack Gallagher

      Jack Gallagher - 2023-01-04

      Thanks for the reply -- this has progressed past my initial note you show below.
      I do have the SSH key set up.I am able to create a shell and connect that way using the key, but no luck on Git.
      I'm running Git on a Windows box here, and I'm invoking this command from the source directory in Git Bash,but I'm still getting the same failure:

      MINGW64 ~/Documents/GitHub/netwonk (main)
      $ git push sourceforge main
      Keyboard-interactive authentication prompts from server:
      fatal: protocol error: bad line length character: | Pa

      I haven't figured out how to fix this yet.Clearly I'm missing something.

      Jack

      On Tuesday, January 3, 2023 at 02:22:33 PM CST, SourceForge Support <sf-support@users.sourceforge.net> wrote:
      

      Hello,

      Is this still an issue?

      Did you try connecting from a command line or terminal.
      If you can log in "manually", the issue could be in the keys setup.

      Make sure to upload your key here: https://sourceforge.net/auth/shell_services
      Also add them to your client authentication agent and that it is running when you try to connect.

      Sincerely,
      SourceForge Support

      [site-support:#24111] netwonk: sourceforge update of github code

      Status: open
      Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
      Last Updated: Thu Dec 22, 2022 07:42 PM UTC

      Owner: nobody
      My main 'netwonk' repository is on Github.
      I mirrored it by Importing all the code to Sourceforge 'netwonk'
      I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
      Now there are updates to the netwonk Code on Github.
      The Sourceforge version of netwonk is not updating.
      I can't see any way to make it update.
      In short, I am totally lost, and it's all out of sync.
      Please help....
      Jack

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
  • SourceForge Support

    Hello,

    We don't see any problems with our services.

    I downloaded and installed Git-2.39.0.2-64-bit on WIndows 10 using git bash to clone and push to a test repo with no issues.

    You could try the connection without ssh keys to make sure everything is working properly

    You may want to double check your ssh key setup:
    Create a key with $ ssh-keygen command
    That command will create it here: C:\Users\YOURUSERNAME\.ssh\id_rsa
    Upload your id_rsa.pub here: https://sourceforge.net/auth/shell_services

    Sincerely,

    SourceForge Support

     
    • Jack Gallagher

      Jack Gallagher - 2023-01-04

      Yeah, you keep replying to old notes from me, so I don't know if you see the most recent.I can see why you would be ready to bail on this, but give me a moment:

      Anyway, I mentioned I can create a shell connection using the command ssh -t jackg23@shell.sourceforge.net create, so the keys are working. I'm using ed25519 rather than rsa.  That's telling me the key setup is OK, right? 

      I can upload changes from git local repos to the Github remote repos.
      The only thing I can't do is push from git to sourceforge.I always get this error --    fatal: protocol error: bad line length character: | Pa
      I'm guessing the "Pa" there is the start of a Password query -- but it should be connecting the keys.
      Why would this one thing be wrong?
      thanks,Jack

      On Wednesday, January 4, 2023 at 01:38:36 PM CST, SourceForge Support <sf-support@users.sourceforge.net> wrote:
      

      Hello,

      We don't see any problems with our services.

      I downloaded and installed Git-2.39.0.2-64-bit on WIndows 10 using git bash to clone and push to a test repo with no issues.

      You could try the connection without ssh keys to make sure everything is working properly

      You may want to double check your ssh key setup:
      Create a key with $ ssh-keygen command
      That command will create it here: C:\Users\YOURUSERNAME.ssh\id_rsa
      Upload your id_rsa.pub here: https://sourceforge.net/auth/shell_services

      Sincerely,

      SourceForge Support

      [site-support:#24111] netwonk: sourceforge update of github code

      Status: open
      Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
      Last Updated: Tue Jan 03, 2023 08:22 PM UTC

      Owner: nobody
      My main 'netwonk' repository is on Github.
      I mirrored it by Importing all the code to Sourceforge 'netwonk'
      I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
      Now there are updates to the netwonk Code on Github.
      The Sourceforge version of netwonk is not updating.
      I can't see any way to make it update.
      In short, I am totally lost, and it's all out of sync.
      Please help....
      Jack

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
  • Dave Brondsema

    Dave Brondsema - 2023-01-05

    Hi,

    Your shell connection with an ed25519 key does indicate that part is okay. In your local git repo, can you run git remote -v and paste the output? Let's make sure you're pushing to the right locations.

    Also can you run this? echo $GIT_SSH

    And you can also try ssh -v git.code.sf.net

    Sincerely,
    SourceForge Support

     
    • Jack Gallagher

      Jack Gallagher - 2023-01-05

      Thanks!
      $ git remote -v
      origin  https://github.com/jackg23x/netwonk.git (fetch)
      origin  https://github.com/jackg23x/netwonk.git (push)
      sourceforge     ssh://jackg23@git.code.sf.net/p/netwonk/code (fetch)
      sourceforge     ssh://jackg23@git.code.sf.net/p/netwonk/code (push)

      $ echo $GIT_SSH
      C:\Program Files\PuTTY\plink.exe

      wow -it's using putty -- I thought it was using openssh
       $ ssh -v git.code.sf.net
      OpenSSH_9.0p1, OpenSSL 1.1.1q  5 Jul 2022
      debug1: Reading configuration data /etc/ssh/ssh_config
      debug1: Connecting to git.code.sf.net [216.105.38.16] port 22.
      debug1: Connection established.
      debug1: identity file /c/Users/jackg/.ssh/id_rsa type 0
      debug1: identity file /c/Users/jackg/.ssh/id_rsa-cert type -1
      debug1: identity file /c/Users/jackg/.ssh/id_ecdsa type -1
      debug1: identity file /c/Users/jackg/.ssh/id_ecdsa-cert type -1
      debug1: identity file /c/Users/jackg/.ssh/id_ecdsa_sk type -1
      debug1: identity file /c/Users/jackg/.ssh/id_ecdsa_sk-cert type -1
      debug1: identity file /c/Users/jackg/.ssh/id_ed25519 type 3
      debug1: identity file /c/Users/jackg/.ssh/id_ed25519-cert type -1
      debug1: identity file /c/Users/jackg/.ssh/id_ed25519_sk type -1
      debug1: identity file /c/Users/jackg/.ssh/id_ed25519_sk-cert type -1
      debug1: identity file /c/Users/jackg/.ssh/id_xmss type -1
      debug1: identity file /c/Users/jackg/.ssh/id_xmss-cert type -1
      debug1: identity file /c/Users/jackg/.ssh/id_dsa type -1
      debug1: identity file /c/Users/jackg/.ssh/id_dsa-cert type -1
      debug1: Local version string SSH-2.0-OpenSSH_9.0
      debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
      debug1: compat_banner: match: OpenSSH_7.4 pat OpenSSH_7.4* compat 0x04000006
      debug1: Authenticating to git.code.sf.net:22 as 'jackg'
      debug1: load_hostkeys: fopen /c/Users/jackg/.ssh/known_hosts2: No such file or directory
      debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
      debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
      debug1: SSH2_MSG_KEXINIT sent
      debug1: SSH2_MSG_KEXINIT received
      debug1: kex: algorithm: curve25519-sha256@libssh.org
      debug1: kex: host key algorithm: ssh-ed25519
      debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
      debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
      debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
      debug1: SSH2_MSG_KEX_ECDH_REPLY received
      debug1: Server host key: ssh-ed25519 SHA256:vDwNztsrZFViJXWpUTSKGo8cF6n79iKAURNiK68n/yE
      debug1: load_hostkeys: fopen /c/Users/jackg/.ssh/known_hosts2: No such file or directory
      debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
      debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
      debug1: hostkeys_find_by_key_hostfile: hostkeys file /c/Users/jackg/.ssh/known_hosts2 does not exist
      debug1: hostkeys_find_by_key_hostfile: hostkeys file /etc/ssh/ssh_known_hosts does not exist
      debug1: hostkeys_find_by_key_hostfile: hostkeys file /etc/ssh/ssh_known_hosts2 does not exist
      The authenticity of host 'git.code.sf.net (216.105.38.16)' can't be established.
      ED25519 key fingerprint is SHA256:vDwNztsrZFViJXWpUTSKGo8cF6n79iKAURNiK68n/yE.
      This key is not known by any other names
      Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
      Warning: Permanently added 'git.code.sf.net' (ED25519) to the list of known hosts.
      debug1: rekey out after 134217728 blocks
      debug1: SSH2_MSG_NEWKEYS sent
      debug1: expecting SSH2_MSG_NEWKEYS
      debug1: SSH2_MSG_NEWKEYS received
      debug1: rekey in after 134217728 blocks
      debug1: Will attempt key: /c/Users/jackg/.ssh/id_rsa RSA SHA256:xTsi0Ov4oxEZsAjC7QrcEPdGSXEocMq7QWWvVZKA8CI
      debug1: Will attempt key: /c/Users/jackg/.ssh/id_ecdsa
      debug1: Will attempt key: /c/Users/jackg/.ssh/id_ecdsa_sk
      debug1: Will attempt key: /c/Users/jackg/.ssh/id_ed25519 ED25519 SHA256:zq2Xo8AIRzE6fdzU5aLoHIKPEAnGx0NGy1TYCWWjg2c
      debug1: Will attempt key: /c/Users/jackg/.ssh/id_ed25519_sk
      debug1: Will attempt key: /c/Users/jackg/.ssh/id_xmss
      debug1: Will attempt key: /c/Users/jackg/.ssh/id_dsa
      debug1: SSH2_MSG_EXT_INFO received
      debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
      debug1: SSH2_MSG_SERVICE_ACCEPT received
      debug1: Authentications that can continue: publickey,keyboard-interactive
      debug1: Next authentication method: publickey
      debug1: Offering public key: /c/Users/jackg/.ssh/id_rsa RSA SHA256:xTsi0Ov4oxEZsAjC7QrcEPdGSXEocMq7QWWvVZKA8CI
      debug1: Authentications that can continue: publickey,keyboard-interactive
      debug1: Trying private key: /c/Users/jackg/.ssh/id_ecdsa
      debug1: Trying private key: /c/Users/jackg/.ssh/id_ecdsa_sk
      debug1: Offering public key: /c/Users/jackg/.ssh/id_ed25519 ED25519 SHA256:zq2Xo8AIRzE6fdzU5aLoHIKPEAnGx0NGy1TYCWWjg2c
      debug1: Authentications that can continue: publickey,keyboard-interactive
      debug1: Trying private key: /c/Users/jackg/.ssh/id_ed25519_sk
      debug1: Trying private key: /c/Users/jackg/.ssh/id_xmss
      debug1: Trying private key: /c/Users/jackg/.ssh/id_dsa
      debug1: Next authentication method: keyboard-interactive
      (jackg@git.code.sf.net) Password:</rsa-sha2-256,rsa-sha2-512></implicit></implicit>

      Hi,

      Your shell connection with an ed25519 key does indicate that part is okay. In your local git repo, can you run git remote -v and paste the output? Let's make sure you're pushing to the right locations.

      Also can you run this? echo $GIT_SSH

      And you can also try ssh -v git.code.sf.net

      Sincerely,
      SourceForge Support

      [site-support:#24111] netwonk: sourceforge update of github code

      Status: open
      Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
      Last Updated: Wed Jan 04, 2023 07:38 PM UTC

      Owner: nobody
      My main 'netwonk' repository is on Github.
      I mirrored it by Importing all the code to Sourceforge 'netwonk'
      I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
      Now there are updates to the netwonk Code on Github.
      The Sourceforge version of netwonk is not updating.
      I can't see any way to make it update.
      In short, I am totally lost, and it's all out of sync.
      Please help....
      Jack

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
      • Dave Brondsema

        Dave Brondsema - 2023-01-05

        Yea I think putty is the problem. If you remove the GIT_SSH environment variable, like export GIT_SSH= and then try, will it work?

        Sincerely,
        SourceForge Support

         
        • Jack Gallagher

          Jack Gallagher - 2023-01-06

          Would/could that screw up SSH to GitHub?

          On Thursday, January 5, 2023 at 05:07:30 PM CST, Dave Brondsema <brondsem@users.sourceforge.net> wrote:
          

          Yea I think putty is the problem. If you remove the GIT_SSH environment variable, like export GIT_SSH= and then try, will it work?

          Sincerely,
          SourceForge Support

          [site-support:#24111] netwonk: sourceforge update of github code

          Status: open
          Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
          Last Updated: Thu Jan 05, 2023 07:37 PM UTC
          Owner: nobody

          My main 'netwonk' repository is on Github.
          I mirrored it by Importing all the code to Sourceforge 'netwonk'
          I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
          Now there are updates to the netwonk Code on Github.
          The Sourceforge version of netwonk is not updating.
          I can't see any way to make it update.
          In short, I am totally lost, and it's all out of sync.
          Please help....
          Jack

          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

           
        • Jack Gallagher

          Jack Gallagher - 2023-01-07

          Yeah man, you nailed it. I changed the putty-oriented environment variable to point at OpenSSH.
          previous:    declare -x GIT_SSH="C:\Program Files\PuTTY\plink.exe"
          fixed:       declare -x GIT_SSH="C:\Windows\System32\OpenSSH\ssh.exe"
          $ git push sourceforge main
          Warning: Permanently added the ED25519 host key for IP address '1x6.1x5.x8.x6' to the list of known hosts.
          Enumerating objects: 59, done.
          Counting objects: 100% (59/59), done.
          Delta compression using up to 8 threads
          Compressing objects: 100% (50/50), done.
          Writing objects: 100% (50/50), 10.49 KiB | 2.62 MiB/s, done.
          Total 50 (delta 33), reused 0 (delta 0), pack-reused 0
          remote: <repository git="" p="" netwonk="" code.git=""> refresh queued.
          To ssh://git.code.sf.net/p/netwonk/code
             022d5fb..61f4555  main -> main</repository>

          A beautiful thing.Thanks a lot,Jack

          On Thursday, January 5, 2023 at 05:07:30 PM CST, Dave Brondsema brondsem@users.sourceforge.net wrote:

          Yea I think putty is the problem. If you remove the GIT_SSH environment variable, like export GIT_SSH= and then try, will it work?

          Sincerely,
          SourceForge Support

          [site-support:#24111] netwonk: sourceforge update of github code

          Status: open
          Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher
          Last Updated: Thu Jan 05, 2023 07:37 PM UTC
          Owner: nobody

          My main 'netwonk' repository is on Github.
          I mirrored it by Importing all the code to Sourceforge 'netwonk'
          I believe I set up Importing so it would update automatically -- at least the SF webpage tells me I did.
          Now there are updates to the netwonk Code on Github.
          The Sourceforge version of netwonk is not updating.
          I can't see any way to make it update.
          In short, I am totally lost, and it's all out of sync.
          Please help....
          Jack

          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/forge/site-support/24111/

          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

           
  • SourceForge Support

    • status: open --> closed
     
  • SourceForge Support

    Hi,

    Thank you for your feedback
    With your issue resolved, this ticket will be closed.

    Sincerely,
    SourceForge Support

     

Log in to post a comment.