octave forge repo issues

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

octave forge repo issues

John Donoghue-3

I guess a FYI

I had a ticket in to source forge for the arduino repo being broken yesterday and got a reply back of the following:

From https://sourceforge.net/p/forge/site-support/18932/:

Hello,

Files in the Octave arduino, control, statistics, video, and zeromq repos were damaged and are unrepairable. To get the repositories going again with all the correct files and metadata, we have moved the repos aside as a backup copy, and put a clean empty repo in their place. Please run hg push in your local checkouts of each of those repos and it should push everything up and be all set. If you don't have checkouts of all those repos, other developers of the project will need to do the hg push. Let us know if we should reach out to help coordinate that, or if you encounter any further issues.

Sincerely,

SourceForge Support



I've been actively working on arduino and zeromq, and I believe I was the last push up on statistics, so will push those.

Video, and control will have to be someone else.

Reply | Threaded
Open this post in threaded view
|

Re: octave forge repo issues

Andreas Weber-6
Am 15.01.19 um 01:33 schrieb John Donoghue:
> Video, and control will have to be someone else.

Thank you for this info, I pushed video.
For control I think the last commit was made by Doug.

-- Andy



Reply | Threaded
Open this post in threaded view
|

Re: octave forge repo issues

Doug Stewart-4


On Tue, Jan 15, 2019, 2:16 PM Andreas Weber <[hidden email] wrote:
Am 15.01.19 um 01:33 schrieb John Donoghue:
> Video, and control will have to be someone else.

Thank you for this info, I pushed video.
For control I think the last commit was made by Doug.

-- Andy

 
Yes I will  do it. Give me a day or 2 I am traveling, bit I brought my laptop with the code.
Reply | Threaded
Open this post in threaded view
|

Re: octave forge repo issues

John Donoghue-3
In reply to this post by John Donoghue-3
On 1/14/19 7:33 PM, John Donoghue wrote:

I guess a FYI

I had a ticket in to source forge for the arduino repo being broken yesterday and got a reply back of the following:

From https://sourceforge.net/p/forge/site-support/18932/:

Hello,

Files in the Octave arduino, control, statistics, video, and zeromq repos were damaged and are unrepairable. To get the repositories going again with all the correct files and metadata, we have moved the repos aside as a backup copy, and put a clean empty repo in their place. Please run hg push in your local checkouts of each of those repos and it should push everything up and be all set. If you don't have checkouts of all those repos, other developers of the project will need to do the hg push. Let us know if we should reach out to help coordinate that, or if you encounter any further issues.

Sincerely,

SourceForge Support



I've been actively working on arduino and zeromq, and I believe I was the last push up on statistics, so will push those.

Video, and control will have to be someone else.

Another FYI from sourceforge

https://sourceforge.net/p/forge/site-support/19194/

For the database pkg repo:

"Looks like this repo suffered from a file corruption issue back in early January but wasn't noticed then. I've restored an older backup we have into its place, and verified it is good. If you or another developer has more recent commits, please do an hg push in the local database repo to push them up to the server"

And:

... checked all the other octave repositories, running hg verify in each. The secs and stk repositories also had this issue. They didn't have an error when browsing them on the web, but the repository was not fully complete. So I also set those aside and moved backups into their place. The backups of those are also fairly old, so they also need hg push to push up commits they are missing.



Reply | Threaded
Open this post in threaded view
|

Re: octave forge repo issues

Olaf Till-2
On Thu, Mar 21, 2019 at 08:49:29PM -0400, John Donoghue wrote:

> On 1/14/19 7:33 PM, John Donoghue wrote:
> >
> > I guess a FYI
> >
> > I had a ticket in to source forge for the arduino repo being broken
> > yesterday and got a reply back of the following:
> >
> > From https://sourceforge.net/p/forge/site-support/18932/:
> >
> > Hello,
> >
> > Files in the Octave arduino, control, statistics, video, and zeromq
> > repos were damaged and are unrepairable. To get the repositories going
> > again with all the correct files and metadata, we have moved the repos
> > aside as a backup copy, and put a clean empty repo in their place.
> > Please run |hg push| in your local checkouts of each of those repos and
> > it should push everything up and be all set. If you don't have checkouts
> > of all those repos, other developers of the project will need to do the
> > |hg push|. Let us know if we should reach out to help coordinate that,
> > or if you encounter any further issues.
> >
> > Sincerely,
> >
> > SourceForge Support
> >
> >
> >
> > I've been actively working on arduino and zeromq, and I believe I was
> > the last push up on statistics, so will push those.
> >
> > Video, and control will have to be someone else.
> >
> Another FYI from sourceforge
>
> https://sourceforge.net/p/forge/site-support/19194/
>
> For the database pkg repo:
>
> "Looks like this repo suffered from a file corruption issue back in early
> January but wasn't noticed then. I've restored an older backup we have into
> its place, and verified it is good. If you or another developer has more
> recent commits, please do an |hg push| in the local |database| repo to push
> them up to the server"
I've restored the missing changesets.

> And:
>
> ... checked all the other octave repositories, running |hg verify| in each.
> The |secs| and |stk| repositories also had this issue. They didn't have an

I can't help with these, my local repositories are not more current
(didn't keep them current since I quitted OF co-administration).

@ Julien: stk?

Olaf

> error when browsing them on the web, but the repository was not fully
> complete. So I also set those aside and moved backups into their place. The
> backups of those are also fairly old, so they also need |hg push| to push up
> commits they are missing.
>
>
>

--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: octave forge repo issues

John Donoghue-3


> -----Original Message-----
> From: Olaf Till [mailto:[hidden email]]
> Sent: Friday, March 22, 2019 12:28 PM
> To: John Donoghue
> Cc: Octave Maintainers List; Julien Bect
> Subject: Re: octave forge repo issues
>
> On Thu, Mar 21, 2019 at 08:49:29PM -0400, John Donoghue wrote:
> > On 1/14/19 7:33 PM, John Donoghue wrote:
> > >
> > > I guess a FYI
> > >
> > > I had a ticket in to source forge for the arduino repo being broken
> > > yesterday and got a reply back of the following:
> > >
> > > From https://sourceforge.net/p/forge/site-support/18932/:
> > >
> > > Hello,
> > >
> > > Files in the Octave arduino, control, statistics, video, and zeromq
> > > repos were damaged and are unrepairable. To get the repositories
> > > going again with all the correct files and metadata, we have moved
> > > the repos aside as a backup copy, and put a clean empty repo in their
place.

> > > Please run |hg push| in your local checkouts of each of those repos
> > > and it should push everything up and be all set. If you don't have
> > > checkouts of all those repos, other developers of the project will
> > > need to do the
> > > |hg push|. Let us know if we should reach out to help coordinate
> > > |that,
> > > or if you encounter any further issues.
> > >
> > > Sincerely,
> > >
> > > SourceForge Support
> > >
> > >
> > >
> > > I've been actively working on arduino and zeromq, and I believe I
> > > was the last push up on statistics, so will push those.
> > >
> > > Video, and control will have to be someone else.
> > >
> > Another FYI from sourceforge
> >
> > https://sourceforge.net/p/forge/site-support/19194/
> >
> > For the database pkg repo:
> >
> > "Looks like this repo suffered from a file corruption issue back in
> > early January but wasn't noticed then. I've restored an older backup
> > we have into its place, and verified it is good. If you or another
> > developer has more recent commits, please do an |hg push| in the local
> > |database| repo to push them up to the server"
>
> I've restored the missing changesets.
>
> > And:
> >
> > ... checked all the other octave repositories, running |hg verify| in
each.
> > The |secs| and |stk| repositories also had this issue. They didn't
> > have an
>
> I can't help with these, my local repositories are not more current
(didn't keep

> them current since I quitted OF co-administration).
>
> @ Julien: stk?
>
> Olaf
>
> > error when browsing them on the web, but the repository was not fully
> > complete. So I also set those aside and moved backups into their
> > place. The backups of those are also fairly old, so they also need |hg
> > push| to push up commits they are missing.
> >
> >
> >
>
> --


I had a version of the sec repo on my computer so tried pushing that but it
said was no changes - which might be correct - its been unmaintained for a
log while


Reply | Threaded
Open this post in threaded view
|

Re: octave forge repo issues

jbect
In reply to this post by Olaf Till-2
Le 22/03/2019 à 17:28, Olaf Till a écrit :
... checked all the other octave repositories, running |hg verify| in each.
The |secs| and |stk| repositories also had this issue. They didn't have an
I can't help with these, my local repositories are not more current
(didn't keep them current since I quitted OF co-administration).

@ Julien: stk?

I will take care of stk.


Reply | Threaded
Open this post in threaded view
|

Re: octave forge repo issues

jbect
Le 22/03/2019 à 20:08, Julien Bect a écrit :
Le 22/03/2019 à 17:28, Olaf Till a écrit :
... checked all the other octave repositories, running |hg verify| in each.
The |secs| and |stk| repositories also had this issue. They didn't have an
I can't help with these, my local repositories are not more current
(didn't keep them current since I quitted OF co-administration).

@ Julien: stk?

I will take care of stk.


I have pushed the missing changesets for stk.