Re: CVS support at SourceForge and Nov. 30

Alexander Hansen <[email protected]> Fri, 1 Dec 2017 09:05:08 -0800
Newsgroups gmane.os.apple.fink.core
Message-ID <[email protected]>
--===============3789346077475059444==
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_2E05A1C9-613B-4860-818D-076E6B329C9C"


--Apple-Mail=_2E05A1C9-613B-4860-818D-076E6B329C9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Dec 1, 2017, at 05:35, Max Horn <[email protected]> wrote:
>=20
> Dear all,
>=20
>=20
> SF.net meant to disable CVS commits yesterday, but it seems they have =
not yet (at least I was just able to commit something).
>=20
>=20
> I have been badly out of the loop, but: is anybody working on a =
transition plan? It seems high time for one, no? It seems we need at =
least this, in order:
>=20
> 1. A fink release with selfupdate-git or -svn support (done!)
>=20

It=E2=80=99s in master but a release hasn=E2=80=99t been tagged yet.

> 2. A full migration of the CVS repository to SVN or GIT (status?)
>   and disable write access to the CVS repository for everybody (except =
for handful of admins, so they can perform the next step)
>=20

I=E2=80=99m not sure what the repository status is. =20

I would like folks to stop using *just* IRC and also record issues and =
the like on github.com/fink/fink <http://github.com/fink/fink> so that =
we don=E2=80=99t have to rely on people=E2=80=99s memories, fragile IRC =
bots, or people being logged in to IRC all the time (I don=E2=80=99t =
even open my laptop when I get home some days).=20

I just sent out a message with a soft freeze announcement.  I=E2=80=99ll =
adjust CVSROOT later on.

> 3. A fink release (with an .info file in the CVS repository) which =
disables selfupdate-cvs, and instead prompts the user to switch to the =
-git or -svn variant.
>=20

And how, exactly, should this be done?  A diff or PR against current =
master would be great.  I don=E2=80=99t have a lot of focused time or =
available CPUs on my machine most workdays, so it=E2=80=99s hard to look =
into the code, make modifications, and spin up test update cases. =20

> Ideally, around step 2, all maintainers would be notified how to =
access the new distribution, I guess?
>=20

Also:

4.  The rsync mirrors need to switch from using the CVS repository to =
using GitHub as the basis for updates.

> Is anybody working on this? If not, once CVS write access is down for =
good, I fear lots of Fink users will be stranded and will require manual =
work to migrate to git/svn.
>=20

IMO it was a bit of a jerk move for SF.net <http://sf.net/> to schedule =
it this way, since US people are just barely back up to speed after =
Thanksgiving. That being said, I slept for quite a bit of the holiday =
weekend because I needed to do that. =20


Honestly, lots of Fink users strand themselves by updating their OSes =
before updating Fink, so we=E2=80=99re used to that.  The specter of =
user inconvenience doesn=E2=80=99t add more productive hours to my day, =
unfortunately.

>=20
> Cheers,
> Max



--Apple-Mail=_2E05A1C9-613B-4860-818D-076E6B329C9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Dec 1, 2017, at 05:35, Max Horn &lt;<a =
href=3D"mailto:[email protected]" class=3D"">[email protected]</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Dear all,<br class=3D""><br class=3D""><br class=3D""><a =
href=3D"http://SF.net" class=3D"">SF.net</a> meant to disable CVS =
commits yesterday, but it seems they have not yet (at least I was just =
able to commit something).<br class=3D""><br class=3D""><br class=3D"">I =
have been badly out of the loop, but: is anybody working on a transition =
plan? It seems high time for one, no? It seems we need at least this, in =
order:<br class=3D""><br class=3D"">1. A fink release with =
selfupdate-git or -svn support (done!)<br class=3D""><br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>It=E2=80=
=99s in master but a release hasn=E2=80=99t been tagged yet.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">2. A full migration of the CVS repository to SVN or GIT =
(status?)<br class=3D""> &nbsp;&nbsp;and disable write access to the CVS =
repository for everybody (except for handful of admins, so they can =
perform the next step)<br class=3D""><br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>I=E2=80=
=99m not sure what the repository status is. &nbsp;</div><div><br =
class=3D""></div><div>I would like folks to stop using *just* IRC and =
also record issues and the like on <a href=3D"http://github.com/fink/fink"=
 class=3D"">github.com/fink/fink</a>&nbsp;so that we don=E2=80=99t have =
to rely on people=E2=80=99s memories, fragile IRC bots, or people being =
logged in to IRC all the time (I don=E2=80=99t even open my laptop when =
I get home some days).&nbsp;</div><div><br class=3D""></div><div>I just =
sent out a message with a soft freeze announcement. &nbsp;I=E2=80=99ll =
adjust CVSROOT later on.</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">3. A fink release (with an =
.info file in the CVS repository) which disables selfupdate-cvs, and =
instead prompts the user to switch to the -git or -svn variant.<br =
class=3D""><br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>And how, exactly, should this be done? &nbsp;A =
diff or PR against current master would be great. &nbsp;I don=E2=80=99t =
have a lot of focused time or available CPUs on my machine most =
workdays, so it=E2=80=99s hard to look into the code, make =
modifications, and spin up test update cases. &nbsp;</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">Ideally, around step 2, all maintainers would be notified how =
to access the new distribution, I guess?<br class=3D""><br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Also:</div><div><br class=3D""></div><div>4. =
&nbsp;The rsync mirrors need to switch from using the CVS repository to =
using GitHub as the basis for updates.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">Is anybody =
working on this? If not, once CVS write access is down for good, I fear =
lots of Fink users will be stranded and will require manual work to =
migrate to git/svn.<br class=3D""><br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>IMO =
it was a bit of a jerk move for <a href=3D"http://SF.net" =
class=3D"">SF.net</a>&nbsp;to schedule it this way, since US people are =
just barely back up to speed after Thanksgiving. That being said, I =
slept for quite a bit of the holiday weekend because I needed to do =
that. &nbsp;</div><div><br class=3D""></div><div><br =
class=3D""></div><div>Honestly, lots of Fink users strand themselves by =
updating their OSes before updating Fink, so we=E2=80=99re used to that. =
&nbsp;The specter of user inconvenience doesn=E2=80=99t add more =
productive hours to my day, unfortunately.</div><div class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D""><br class=3D"">Cheers,<br class=3D"">Max<br =
class=3D""></div></div></blockquote><br class=3D""></div><div><br =
class=3D""></div></body></html>=

--Apple-Mail=_2E05A1C9-613B-4860-818D-076E6B329C9C--


--===============3789346077475059444==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--===============3789346077475059444==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
fink-core mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

--===============3789346077475059444==--