Menu
▾
▴
octave-dev
|
From: Carnë D. <car...@gm...> - 2012-09-23 10:08:50
|
Hi everyone with the upgrade in sourceforge the location for the repository changed so you should make a new checkout. See message below from sourceforge. Carnë ---------- Forwarded message ---------- From: SourceForge.net <nor...@in...> Date: 23 September 2012 06:59 Subject: SourceForge Repo Clone Complete To: no...@in... Your cloned repository code in project octave is now ready for use. Old repository url: http://octave.svn.sourceforge.net/svnroot/octave New repository checkout command: svn checkout --username=carandraug svn+ssh://car...@sv.../p/octave/code/trunk octave-code You and any other developers should do a fresh checkout using the new repository location. |
|
From: Juan P. C. <car...@if...> - 2012-09-23 10:48:07
|
On Sun, Sep 23, 2012 at 12:08 PM, Carnë Draug <car...@gm...> wrote: > Hi everyone > > with the upgrade in sourceforge the location for the repository > changed so you should make a new checkout. See message below from > sourceforge. > > Carnë > > ---------- Forwarded message ---------- > From: SourceForge.net <nor...@in...> > Date: 23 September 2012 06:59 > Subject: SourceForge Repo Clone Complete > To: no...@in... > > > Your cloned repository code in project octave is now ready for use. > > Old repository url: http://octave.svn.sourceforge.net/svnroot/octave > > New repository checkout command: svn checkout --username=carandraug > svn+ssh://car...@sv.../p/octave/code/trunk octave-code > > You and any other developers should do a fresh checkout using the new > repository location. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://ad.doubleclick.net/clk;258768047;13503038;j? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev You can get your own checkout command by going to your account --> projects --> Octave Forge --> Code However, what credentials should we use? My sourceforge credentials are not working for the checkout. -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ |
|
From: c. <car...@gm...> - 2012-09-23 11:05:44
|
On 23 Sep 2012, at 12:47, Juan Pablo Carbajal wrote: > You can get your own checkout command by going to your account --> > projects --> Octave Forge --> Code > > However, what credentials should we use? My sourceforge credentials > are not working for the checkout. > Is anonymous checkput still possible? c. |
|
From: Carnë D. <car...@gm...> - 2012-09-23 11:55:09
|
On 23 September 2012 13:06, c. <car...@gm...> wrote: > On 23 Sep 2012, at 12:47, Juan Pablo Carbajal wrote: > >> You can get your own checkout command by going to your account --> >> projects --> Octave Forge --> Code >> >> However, what credentials should we use? My sourceforge credentials >> are not working for the checkout. >> > Is anonymous checkput still possible? Should be. On https://sourceforge.net/p/octave/code/ there's 3 buttons (RW/RO/HTTP). I imagine it means read+write and read only (through SSH) and http (that's the previous method). I'm also asked for a password when using the SSH methods and my SF password is not being accepted. As I never gave SF my public keys it can't be those either. But checking out through HTTPS is working fine. Carnë |
|
From: Juan P. C. <car...@if...> - 2012-09-23 12:47:47
|
On Sun, Sep 23, 2012 at 1:54 PM, Carnë Draug <car...@gm...> wrote: > On 23 September 2012 13:06, c. <car...@gm...> wrote: >> On 23 Sep 2012, at 12:47, Juan Pablo Carbajal wrote: >> >>> You can get your own checkout command by going to your account --> >>> projects --> Octave Forge --> Code >>> >>> However, what credentials should we use? My sourceforge credentials >>> are not working for the checkout. >>> >> Is anonymous checkput still possible? > > Should be. On https://sourceforge.net/p/octave/code/ there's 3 buttons > (RW/RO/HTTP). I imagine it means read+write and read only (through > SSH) and http (that's the previous method). I'm also asked for a > password when using the SSH methods and my SF password is not being > accepted. As I never gave SF my public keys it can't be those either. > But checking out through HTTPS is working fine. > > Carnë Works with HTTP! We should then recommend checking out with the HTTP option. @Carnë: If you need help updatign the text in the website let me know, we should use this opportunity to put it up to date. Cheers -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ |
|
From: Mike M. <mtm...@ie...> - 2012-09-23 13:20:04
|
On Sun, Sep 23, 2012 at 8:47 AM, Juan Pablo Carbajal <car...@if...> wrote: > On Sun, Sep 23, 2012 at 1:54 PM, Carnë Draug <car...@gm...> wrote: >> On 23 September 2012 13:06, c. <car...@gm...> wrote: >>> On 23 Sep 2012, at 12:47, Juan Pablo Carbajal wrote: >>> >>>> You can get your own checkout command by going to your account --> >>>> projects --> Octave Forge --> Code >>>> >>>> However, what credentials should we use? My sourceforge credentials >>>> are not working for the checkout. >>>> >>> Is anonymous checkput still possible? >> >> Should be. On https://sourceforge.net/p/octave/code/ there's 3 buttons >> (RW/RO/HTTP). I imagine it means read+write and read only (through >> SSH) and http (that's the previous method). I'm also asked for a >> password when using the SSH methods and my SF password is not being >> accepted. As I never gave SF my public keys it can't be those either. >> But checking out through HTTPS is working fine. >> >> Carnë > > Works with HTTP! We should then recommend checking out with the HTTP option. > > @Carnë: If you need help updatign the text in the website let me know, > we should use this opportunity to put it up to date. All, SSH is working for me, you can add one or more SSH keys to your SF account at https://sourceforge.net/account/ssh and then it should work. -- mike |
|
From: Carnë D. <car...@gm...> - 2012-09-24 06:54:43
|
On 23 September 2012 14:47, Juan Pablo Carbajal <car...@if...> wrote: > @Carnë: If you need help updatign the text in the website let me know, > we should use this opportunity to put it up to date. I was more of a midndset to move the instructions to the wiki... Should make it easier to change in the future. Carnë |
|
From: Juan P. C. <car...@if...> - 2012-09-24 07:23:46
|
On Mon, Sep 24, 2012 at 8:54 AM, Carnë Draug <car...@gm...> wrote: > On 23 September 2012 14:47, Juan Pablo Carbajal <car...@if...> wrote: >> @Carnë: If you need help updatign the text in the website let me know, >> we should use this opportunity to put it up to date. > > I was more of a midndset to move the instructions to the wiki... > Should make it easier to change in the future. > > Carnë Sounds great, will also help in the transition to Agora. Ok, can you take the lead and create the corresponding pages so we can stat updating the content? When the process is over, I guess you will empty this page http://octave.sourceforge.net/developers.html and just live a nice link to the wiki, right? -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ |
|
From: c. <car...@gm...> - 2012-09-24 07:48:19
|
On 24 Sep 2012, at 09:23, Juan Pablo Carbajal wrote: > On Mon, Sep 24, 2012 at 8:54 AM, Carnë Draug <car...@gm...> wrote: >> On 23 September 2012 14:47, Juan Pablo Carbajal <car...@if...> wrote: >>> @Carnë: If you need help updatign the text in the website let me know, >>> we should use this opportunity to put it up to date. >> >> I was more of a midndset to move the instructions to the wiki... >> Should make it easier to change in the future. >> >> Carnë > > Sounds great, will also help in the transition to Agora. > Ok, can you take the lead and create the corresponding pages so we can > stat updating the content? > > When the process is over, I guess you will empty this page > http://octave.sourceforge.net/developers.html > > and just live a nice link to the wiki, right? I'd be careful with such changes, the autogenerated files for package documentation have hardcoded links to various pages on the Octave-Forge website, if you start moving things around those links will be broken and ALL packages will have to be generated again. c. |
|
From: Juan P. C. <car...@if...> - 2012-09-24 07:58:39
|
On Mon, Sep 24, 2012 at 9:48 AM, c. <car...@gm...> wrote: > > On 24 Sep 2012, at 09:23, Juan Pablo Carbajal wrote: > >> On Mon, Sep 24, 2012 at 8:54 AM, Carnë Draug <car...@gm...> wrote: >>> On 23 September 2012 14:47, Juan Pablo Carbajal <car...@if...> wrote: >>>> @Carnë: If you need help updatign the text in the website let me know, >>>> we should use this opportunity to put it up to date. >>> >>> I was more of a midndset to move the instructions to the wiki... >>> Should make it easier to change in the future. >>> >>> Carnë >> >> Sounds great, will also help in the transition to Agora. >> Ok, can you take the lead and create the corresponding pages so we can >> stat updating the content? >> >> When the process is over, I guess you will empty this page >> http://octave.sourceforge.net/developers.html >> >> and just live a nice link to the wiki, right? > > I'd be careful with such changes, the autogenerated files for package documentation have hardcoded links to various pages on the Octave-Forge website, > if you start moving things around those links will be broken and ALL packages will have to be generated again. > c. Which if itself is not a bad idea! releasePKG is working fine, we can make a script to generate the html of all packages. -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ |
|
From: c. <car...@gm...> - 2012-09-24 08:21:14
|
On 24 Sep 2012, at 09:58, Juan Pablo Carbajal wrote: > Which if itself is not a bad idea! releasePKG is working fine, we can > make a script to generate the html of all packages. No, we do not want that. that's like the old monolithic build process, sounded like a good idea in the beginning, proved to be __BAD__™ in the end. Been there already, we don't want to go there again. c. |
|
From: Juan P. C. <car...@if...> - 2012-09-24 08:44:51
|
On Mon, Sep 24, 2012 at 10:21 AM, c. <car...@gm...> wrote: > > On 24 Sep 2012, at 09:58, Juan Pablo Carbajal wrote: > >> Which if itself is not a bad idea! releasePKG is working fine, we can >> make a script to generate the html of all packages. > > No, we do not want that. that's like the old monolithic build process, > sounded like a good idea in the beginning, proved to be __BAD__™ in the end. > Been there already, we don't want to go there again. > > c. > I mean it as a one-shot thing, not as a standard procedure. Also, detecting where are the hardlinks (and getting rid of them when possible) is also good. However it can create insurmountable delays. -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ |
|
From: c. <car...@gm...> - 2012-09-24 08:53:23
|
On 24 Sep 2012, at 10:44, Juan Pablo Carbajal wrote: > On Mon, Sep 24, 2012 at 10:21 AM, c. <car...@gm...> wrote: >> >> On 24 Sep 2012, at 09:58, Juan Pablo Carbajal wrote: >> >>> Which if itself is not a bad idea! releasePKG is working fine, we can >>> make a script to generate the html of all packages. >> >> No, we do not want that. that's like the old monolithic build process, >> sounded like a good idea in the beginning, proved to be __BAD__™ in the end. >> Been there already, we don't want to go there again. >> >> c. >> > > I mean it as a one-shot thing, not as a standard procedure. > > Also, detecting where are the hardlinks (and getting rid of them when > possible) is also good. However it can create insurmountable delays. as a one-timer it's of course OK, but I do expect lots of problems. c. |
|
From: Carnë D. <car...@gm...> - 2012-09-24 12:36:39
|
On 23 September 2012 12:08, Carnë Draug <car...@gm...> wrote: > Hi everyone > > with the upgrade in sourceforge the location for the repository > changed so you should make a new checkout. See message below from > sourceforge. > > Carnë > > ---------- Forwarded message ---------- > From: SourceForge.net <nor...@in...> > Date: 23 September 2012 06:59 > Subject: SourceForge Repo Clone Complete > To: no...@in... > > > Your cloned repository code in project octave is now ready for use. > > Old repository url: http://octave.svn.sourceforge.net/svnroot/octave > > New repository checkout command: svn checkout --username=carandraug > svn+ssh://car...@sv.../p/octave/code/trunk octave-code > > You and any other developers should do a fresh checkout using the new > repository location. I just noticed that it's still possible to commit to the old repository. There's two repositories and this is not git or mercurial. Both me and Andrius Sutas made a commit to the old one after the "split". Please everyone, make a fresh clone and forget the old one. Sorry for the trouble this may have caused. Carnë |
|
From: Paul D. <sl...@pa...> - 2012-09-24 16:12:39
|
Maybe it is good to rename the trunk _trunk or something (for the old repository), so people commiting to the wrong repository notice the difference. Unfortunately one then notices the change at a late stage, but that is better than committing and not knowing it was for a dead end repository. Paul Carnë Draug skrev 2012-09-24 14.36: > On 23 September 2012 12:08, Carnë Draug <car...@gm...> wrote: >> Hi everyone >> >> with the upgrade in sourceforge the location for the repository >> changed so you should make a new checkout. See message below from >> sourceforge. >> >> Carnë >> >> ---------- Forwarded message ---------- >> From: SourceForge.net <nor...@in...> >> Date: 23 September 2012 06:59 >> Subject: SourceForge Repo Clone Complete >> To: no...@in... >> >> >> Your cloned repository code in project octave is now ready for use. >> >> Old repository url: http://octave.svn.sourceforge.net/svnroot/octave >> >> New repository checkout command: svn checkout --username=carandraug >> svn+ssh://car...@sv.../p/octave/code/trunk octave-code >> >> You and any other developers should do a fresh checkout using the new >> repository location. > > I just noticed that it's still possible to commit to the old > repository. There's two repositories and this is not git or mercurial. > Both me and Andrius Sutas made a commit to the old one after the > "split". > > Please everyone, make a fresh clone and forget the old one. Sorry for > the trouble this may have caused. > > Carnë > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev > |
|
From: Carnë D. <car...@gm...> - 2012-09-24 18:46:26
|
On 24 September 2012 18:12, Paul Dreik <sl...@pa...> wrote: > Maybe it is good to rename the trunk _trunk or something (for the old > repository), so people commiting to the wrong repository notice the > difference. Unfortunately one then notices the change at a late stage, > but that is better than committing and not knowing it was for a dead end > repository. > > Paul I'd settle for just removing the damn thing... Carnë |
|
From: Carnë D. <car...@gm...> - 2012-10-05 13:21:39
|
On 24 September 2012 20:45, Carnë Draug <car...@gm...> wrote: > On 24 September 2012 18:12, Paul Dreik <sl...@pa...> wrote: >> Maybe it is good to rename the trunk _trunk or something (for the old >> repository), so people commiting to the wrong repository notice the >> difference. Unfortunately one then notices the change at a late stage, >> but that is better than committing and not knowing it was for a dead end >> repository. > > I'd settle for just removing the damn thing... I finnally got instructions to do it. If someone has problems with the repo let me know... maybe I did something I shouldn't had. Carnë |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X