Re: [Owfs-developers] git pull returns 502 error message

[Jan Kandziora]

Am 04.04.2018 um 22:20 schrieb Johan Ström:
>
> Whatever we do, I really suggest shutting down Sourceforge git. Still
> only me and Jan with commit access on github, but I assume any previous
> commiters will raise their voices when they need to commit, if not before.
>
I second that.


> 
> I'm not familiar with procedures of building releases, as that will
> change a bit, perhaps Jan who have done latest release can add step by
> step instructions for how it works today, into some doc file?
> 
No, this won't change as there's no version control involved when
building releases. You had to change

VERSION_MAJOR=3
VERSION_MINOR=2
VERSION_PATCHLEVEL=2

in ./configure.ac, (then commit and tag the release in git), then

$ make clean
$ make distclean
$ ./bootstrap
$ ./configure
$ make dist

That creates the .tar.gz which I upload along with a README created by
hand, enriched with data from the git log.

Kind regards

Jan

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Johan Ström]

On 07/03/18 07:40, Johan Ström wrote:

On 06/03/18 07:47, Jan Kandziora wrote:

Am 06.03.2018 um 07:23 schrieb Johan Ström:

And no opinion against here either.. SF seems to have shaped up last day
or two, but who know how long that will keep..

What are your suggestions?

Move GIT only, and keep site + mailinglist on sourceforge?
Releases on Github I guess?
(https://help.github.com/articles/creating-releases/)


100% Github, please. The numerous ways to file bug reports and asking
for help make me dizzy already.

Moving tickets and pull requests, yes definitely.

Mailinglist fills a function which github tickets does not really fill,
imo. I'd be fine with just keeping that on SF (and of course the
owfs-developers archive, very important resource!), not sure if there is
anything else to keep.
My sync script starts exhibiting weird behavior... it tried to remove 
all branches and tags from github mirror, as they had disappeared from 
sourceforge! Of course they hadn't, I assume Sourceforge servers got 
confused somewhere and said that there where no branches... including 
master..! The "git fetch --prune" command had pruned them all at least. 
Good thing they seem to be back now, but seems to go back and forth a bit...


Whatever we do, I really suggest shutting down Sourceforge git. Still 
only me and Jan with commit access on github, but I assume any previous 
commiters will raise their voices when they need to commit, if not before.


*If no-one protests in the coming days,* I will*:*
* Make the Source Forge repo read-only for all current developers/admins 
(as well as it can be done)

* Set custom Checkout URL on sourceforge to point to github
* Remove all non-master branches from sourceforge.
* Adjust my clone script to pull from github and push master + tags to 
sourceforge instead, then it can make a best-effort to work.


Then..
* See if I can make sourceforge tickets readonly
* as well as possible update all info to point code+tickets to github repo

I'm not familiar with procedures of building releases, as that will 
change a bit, perhaps Jan who have done latest release can add step by 
step instructions for how it works today, into some doc file?


Regards
Johan
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Johan Ström]

On 06/03/18 07:47, Jan Kandziora wrote:
> Am 06.03.2018 um 07:23 schrieb Johan Ström:
>> And no opinion against here either.. SF seems to have shaped up last day
>> or two, but who know how long that will keep..
>>
>> What are your suggestions?
>>
>> Move GIT only, and keep site + mailinglist on sourceforge?
>> Releases on Github I guess?
>> (https://help.github.com/articles/creating-releases/)
>>
> 100% Github, please. The numerous ways to file bug reports and asking
> for help make me dizzy already.

Moving tickets and pull requests, yes definitely.

Mailinglist fills a function which github tickets does not really fill,
imo. I'd be fine with just keeping that on SF (and of course the
owfs-developers archive, very important resource!), not sure if there is
anything else to keep.

Johan


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Jan Kandziora]

Am 06.03.2018 um 07:23 schrieb Johan Ström:
> And no opinion against here either.. SF seems to have shaped up last day
> or two, but who know how long that will keep..
> 
> What are your suggestions?
> 
> Move GIT only, and keep site + mailinglist on sourceforge?
> Releases on Github I guess?
> (https://help.github.com/articles/creating-releases/)
> 
100% Github, please. The numerous ways to file bug reports and asking
for help make me dizzy already.

Kind regards

Jan

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Johan Ström]

And no opinion against here either.. SF seems to have shaped up last day
or two, but who know how long that will keep..

What are your suggestions?

Move GIT only, and keep site + mailinglist on sourceforge?
Releases on Github I guess?
(https://help.github.com/articles/creating-releases/)

Anyway, the repo is there and ready for use. So far it's only me and Jan
Kandziora who have access. To get admin/member/colaborator access, we
need to add you.


Johan


On 05/03/18 13:16, Ben Oliver wrote:
> On 18-03-05 13:11:23, Matthias Urlichs via Owfs-developers wrote:
>> On 05.03.2018 11:15, Stefano Miccoli wrote:
>>> In my opinion it should be time to migrate the principal OWFS repo
>>> from SF to GH.
>>
>> Seconded. SF is not going to get better, long-term.
>>
>> -- -- Matthias Urlichs
>
> Thirded. I noticed that vim is about to jump ship after loads of
> issues with their site.
>
> --
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Ben Oliver]

On 18-03-05 13:11:23, Matthias Urlichs via Owfs-developers wrote:

On 05.03.2018 11:15, Stefano Miccoli wrote:

In my opinion it should be time to migrate the principal OWFS repo from SF to 
GH.


Seconded. SF is not going to get better, long-term.

-- -- Matthias Urlichs


Thirded. I noticed that vim is about to jump ship after loads of issues 
with their site.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Matthias Urlichs via Owfs-developers]

On 05.03.2018 11:15, Stefano Miccoli wrote:
> In my opinion it should be time to migrate the principal OWFS repo from SF to 
> GH.

Seconded. SF is not going to get better, long-term.

-- 
-- Matthias Urlichs


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Stefano Miccoli]

In my opinion it should be time to migrate the principal OWFS repo from SF to 
GH.

Stefano

> On 5 Mar 2018, at 07:26, Johan Ström  wrote:
> 
> On 02/03/18 01:48, Gregg Levine wrote:
>> Hello!
>> I have the most recent numbered release on a Pi3 (now on a Pi Zero W)
>> running and working. However since I previously also released the
>> newest code via a git clone when setting up the directory.
>> 
>> Now however I need to update things, and it is returning that error
>> message. It means bad gateway.
>> 
> 
> (re-send, now second time, as my mail server gave up on trying to reach
> Sourceforge... and on first retry Sourceforge mail server said "no such
> user"..  trying again now)
> 
> Sourceforge is having huge issues back and forth since their "datacenter
> migration" a few weeks back. Apparently the mailinglists seems to work
> at least? [scratch that]
> 
> https://twitter.com/sfnet_ops
> 
> Fortunately, a while back I setup a mirror on Github,
> https://github.com/owfs/owfs, which is (or at least attempts to be)
> synced every 15 minutes.
> This can be used for read access when sourceforge is unreachable.
> 
> Also, so far we've actually had 2 pull requests coming in through GH!
> 
> Regards
> Johan
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Martin Patzak (GMX)]

> Fortunately, a while back I setup a mirror on Github,
> https://github.com/owfs/owfs, which is (or at least attempts to be)
> synced every 15 minutes.
> This can be used for read access when sourceforge is unreachable.
>
> Also, so far we've actually had 2 pull requests coming in through GH!
I was one of those two! Who was the other on, I wonder? ;-)

But, I think it's habit, that people use sf over github for owfs...
>
> Regards
> Johan
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Johan Ström]

On 02/03/18 01:48, Gregg Levine wrote:
> Hello!
> I have the most recent numbered release on a Pi3 (now on a Pi Zero W)
> running and working. However since I previously also released the
> newest code via a git clone when setting up the directory.
>
> Now however I need to update things, and it is returning that error
> message. It means bad gateway.
>

(re-send, now second time, as my mail server gave up on trying to reach
Sourceforge... and on first retry Sourceforge mail server said "no such
user"..  trying again now)

Sourceforge is having huge issues back and forth since their "datacenter
migration" a few weeks back. Apparently the mailinglists seems to work
at least? [scratch that]

https://twitter.com/sfnet_ops

Fortunately, a while back I setup a mirror on Github,
https://github.com/owfs/owfs, which is (or at least attempts to be)
synced every 15 minutes.
This can be used for read access when sourceforge is unreachable.

Also, so far we've actually had 2 pull requests coming in through GH!

Regards
Johan

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Jan Kandziora]

Am 02.03.2018 um 01:48 schrieb Gregg Levine:
> Hello!
> I have the most recent numbered release on a Pi3 (now on a Pi Zero W)
> running and working. However since I previously also released the
> newest code via a git clone when setting up the directory.
> 
> Now however I need to update things, and it is returning that error
> message. It means bad gateway.
> 
sf.net has the hiccups at the moment.

Kind regards

Jan

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] git pull returns 502 error message

[Colin Law]

On 2 March 2018 at 00:48, Gregg Levine  wrote:
> Hello!
> I have the most recent numbered release on a Pi3 (now on a Pi Zero W)
> running and working. However since I previously also released the
> newest code via a git clone when setting up the directory.
>
> Now however I need to update things, and it is returning that error
> message. It means bad gateway.

What does
git remote -v
show? From the git directory obviously.

Colin

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] git pull returns 502 error message

[Gregg Levine]

Hello!
I have the most recent numbered release on a Pi3 (now on a Pi Zero W)
running and working. However since I previously also released the
newest code via a git clone when setting up the directory.

Now however I need to update things, and it is returning that error
message. It means bad gateway.

Incidentally for those of us in NYC, I demonstrated it on that Pi3 for
a group of people as part of my commitment to participation in the
Hack A Day NYC meeting, which was subtitled "Bring a hack". This was
using the ttyUSB0 connection which is what I also use here, when the
laptop is running Slackware.

Now I want to reduce it to working on a Pi Zero W and found one for
sale with the headers on it already. First via ttyUSB0 and then via
i2c since there's a company who make prepared sleds for the mounting
of chips in SMT formats.

Incidentally Paul if you're listening, I gave a generous nod to your
efforts to create the OWFS software for your home project.
-
Gregg C Levine gregg.drw...@gmail.com
"This signature fought the Time Wars, time and again."

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers