Re: CVS support at SourceForge and Nov. 30

Daniel Johnson <[email protected]> Sat, 2 Dec 2017 10:29:56 -0500
Newsgroups gmane.os.apple.fink.core
Message-ID <[email protected]>
--===============3169364844697143838==
Content-Type: multipart/signed;
	boundary="Apple-Mail=_E37C9ED6-AE8C-449F-8336-80558EE05CD2";
	protocol="application/pgp-signature";
	micalg=pgp-sha256


--Apple-Mail=_E37C9ED6-AE8C-449F-8336-80558EE05CD2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Dec 1, 2017, at 6:38 PM, Alexander Hansen =
<[email protected]> wrote:
>=20
>>=20
>> On Dec 1, 2017, at 09:05, Alexander Hansen =
<[email protected]> wrote:
>>=20
>>=20
>>> 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
>>=20
>> It=E2=80=99s in master but a release hasn=E2=80=99t been tagged yet.
>>=20
>>> 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
>>=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 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=99l=
l adjust CVSROOT later on.
>>=20
>>> 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
>>=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
>>=20
>> Also:
>>=20
>> 4.  The rsync mirrors need to switch from using the CVS repository to =
using GitHub as the basis for updates.
>>=20
>>> 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
>>=20
>> IMO it was a bit of a jerk move for 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
>>=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
>>>=20
>>> Cheers,
>>> Max
>>=20
>>=20
>=20
> Well, so much for that idea.  It took effect.  We=E2=80=99re down to =
only pserver checkouts :
>=20
> I guess our update strategy is now:
>=20
> 1)  For people using /sw, use =E2=80=9Capt-get install fink=E2=80=9D =
to get a new fink, for distributions where we=E2=80=99re currently =
building a bindist.
> 2)  For other folks, grab the appropriate fink*.info file from GitHub =
or inject from master or the 0.43 branch when that goes live.
>=20
> That=E2=80=99ll make testing a bit easier, since there won=E2=80=99t =
be a direct upgrade path.
> --
> Alexander Hansen, Ph.D.
> Fink User Liaison
>=20

Just FYI, I checked and the https://github.com/fink/fink-distributions =
repo is up-to-date. Looks like I was the last one to commit to cvs. I =
successfully switched to it with selfupdate-git.

I suspect that most normal users use rsync rather than cvs updating so =
once rsync points to git they should get updates. It=E2=80=99s fink =
committers that will need the most help.

Daniel


--Apple-Mail=_E37C9ED6-AE8C-449F-8336-80558EE05CD2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEEl5Lc0dwslORbyb+chn1bGmwCOEFAloixvQACgkQchn1bGmw
COGZrxAAjKSTeqi0hqkQBfBNPRf0qyGkkb45GKHcyZGH7hyD5gDFhlA3/9bMPVpC
e6Ew/AfrEWt4BVfcIZX5YMWOYrIX2sHidL85eIL4iQmyzH11Mgd2g++I847u3Uv4
6pd3L8H3+yQAOyvqE4mh/rKN9EfY1aANPdTvukrWNV4vZH1bh+98rjY9bxfW1c//
5YwBpTA8jpchlf7SIBWfohzvQjy/jOG+k1h9a0Pg7e2L+8dpyfpZmPJMwcKVNXI8
eHO5tnoND0VvW3h/GFIA/7qlHIYe8BBkk/A5li2gXSimg7nFnYKm0j4N9jo6puCS
gB1mv6q6jgNFK3Gk2rxrUzjkYmdnOd8HOaCo8dpDfLHxoh3dv7M0p5GC9bAxfw6z
nndqRKxUpS5a5dJOl2UZRSQIsT95JEZC+yHNv4p5bsipBRimYn60AaCd3KQHyXSD
fPcdiQ0/a4yrRte7MpgmBiQ4dbSHvqTYBeLYWCEjFPrie+rnWqEibqxjoa6olOSF
HocG1A+eLqxb5+Y1///JcCqs//+HgHTdfFa3YSMNhNvDTHr+ZXQjbIcYU5VWPgLN
469hxp4KFpUpr5muAvwespqCBqboqBlV0GRc+zhuZk72SNX0aUwMSOnHJQ2giw2q
2+jmVaMdiTVaht5jbKYMSbzTRNZQ4TUN3qvYVDrgtKREraSWS9o=
=WC0C
-----END PGP SIGNATURE-----

--Apple-Mail=_E37C9ED6-AE8C-449F-8336-80558EE05CD2--


--===============3169364844697143838==
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
--===============3169364844697143838==
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

--===============3169364844697143838==--