[bt-devel] Moving away from SourceForge
Gary Holmlund
gary.holmlund at gmail.com
Fri Jun 19 08:20:47 MST 2015
Jaak,
I can provide the exact bits for the last version of BT on Windows
(bibletime-2.10.1-win32.exe). I have also download the SourceForge
version and it is the same as my local copy.
Gary
On 06/18/2015 10:16 PM, Jaak Ristioja wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Given the recent rumors of SourceForge taking over "abandoned"
> projects, I'd rather not leave anything on SourceForge.net. Therefore
> I think we must consider dropping all older downloads.
>
> J
>
>
> On 19.06.2015 06:35, Jonathan Morgan wrote:
>> Hi Jaak,
>>
>> One possibility would be to move / rebuild the last two or three
>> versions of BibleTime, and leave the rest on Sourceforge. That way
>> they are still there if people want them, but it's not common to go
>> much further back than the latest version.
>>
>> Jon
>>
>> On Fri, Jun 19, 2015 at 12:42 AM, Jaak Ristioja <jaak at ristioja.ee
>> <mailto:jaak at ristioja.ee>> wrote:
>>
>> I know that one can attach binaries to releases/tags in Github.
>> But what about our older releases and such? Does Github allow us to
>> host those also? If yes, then where exactly can I find that feature
>> in Github ?
>>
>> Secondly, I just downloaded all of our files from SourceForge
>> using
>>
>> scp -r frs.sourceforge.net:/home/frs/project/b/bi/bibletime/ dest/
>>
>> I guess I can verify the integrity of our source archives because
>> I've checksummed them at each release, but what about the
>> binaries?
>>
>> J
>>
>> On 18.06.2015 17:21, Greg Hellings wrote:
>>> Github.com allows the distribution of both source tarballs and
>>> build artifacts. If our source is already there, no reason not
>>> to have our releases hosted there as well.
>>> --Greg
>>> On Thu, Jun 18, 2015 at 9:13 AM, Jaak Ristioja <jaak at ristioja.ee
>>> <mailto:jaak at ristioja.ee>> wrote: Hello!
>>> Due to recent issues with SourceForge taking over projects,
>>> serving malware etc. becoming a bigger problem day by day and
>>> browsers such as Google Chrome already blocking parts of
>>> sourceforge.net <http://sourceforge.net>, we need to move our
>>> downloads to somewhere else.
>>> The question is: where to?
>>> If anybody has a good answer to this question, please let us
>>> know.
>>
>>> Blessings, J
>> _______________________________________________ bt-devel mailing
>> list bt-devel at crosswire.org <mailto:bt-devel at crosswire.org>
>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>
>>
>>
>>
>> _______________________________________________ bt-devel mailing
>> list bt-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBAgAGBQJVg6WtAAoJECnioa4pvExqrRcP/jrBT+mDSNzjmYQddZQpQWOz
> w0NKmV4mdW6gjwUgy1DRRYEJ2l3wTDXCTPTX7WQQ8RJW2x6AqTIIH6uZcwDcIed8
> ReShd+HDdhHYc450+4BIiMIG8rXTlK4oo6CKeoliYCD6hbrzrIN8EQqX1DXEF5o/
> 6XB9rOvvr+ML7/uf3ukIbCVpWxPb0DUiigtVGbHdSLRYcK0CWAazJSiEN5Tpsrwo
> fpVN+Sd5w5ODplYYvDss7UDWl84DcU8h+MbFI2iI4Fz6kejYJarn91wRoqCTDPmP
> MGZTkzwpeyDku/K87f+9bPZuiI16fHU3Z0ZBOAEHzxvgzg15CBdrevByJKhwqYDA
> u0NbaGMxiZ6PygXaW/HURpDY9AHDPSaNQOtIPCMv6WKBpbY5jC2xvxfDsCq3aZFt
> E2wreKWsd3DKVJJDIs9GnZfEQpoBze0rqpgtS8u8wM06D0tGMGq3f6K6jXT20Och
> 0+b2gsOSLCNm8FSHIE6hCxdMEQyX8A33zSGksJdShbMCQWFsSPMA/ennfiJXmkk1
> CcKHxGT0/UVnJsvpivyNOdxOQ1AA4KAPe3xfT2ZEkEZURQjyUuyajD77Q5pLAKWu
> VeFRvIVcd1CpMgJFW/GBvmH/bzRNxLo9chP0bqW7v2vK4uV1hPTzXYy6tWAS444G
> TLbD1Pd6mUeoRdi2Gln0
> =v+dc
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> bt-devel mailing list
> bt-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/bt-devel
More information about the bt-devel
mailing list