It's been at least a few hours and the DUB registry hasn't picked up
the new 'v0.8.3' tag in 'sdlang-d'. Has something gone wrong?
Am 27.03.2013 18:01, schrieb Nick Sabalausky:
It's been at least a few hours and the DUB registry hasn't picked up
the new 'v0.8.3' tag in 'sdlang-d'. Has something gone wrong?
The hoster has upgraded their infrastructure and now IPv6 is not working
anymore and network connectivity in general is quite broken (only every
4th request to github is getting through). I probably shouldn't have
made a positive statement about them... ;)
I'll check with them at the end of the week when I'm back home and
things are still not working.
I'll check with them at the end of the week when I'm back home and
things are still not working.
Version updates are back working. Still need to fix IPv6, but fortunately that does not impede anything else.
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig589DA4DD07D83F99A1ACC729
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 03/30/2013 12:29 PM, S=C3=B6nke Ludwig wrote:
I'll check with them at the end of the week when I'm back home and=20
things are still not working.
=20
Version updates are back working. Still need to fix IPv6, but fortunate=
ly that does not impede anything else.
=20
I've been thinking about this for a while, and this seems to be the
perfect opportunity.
Is there any sort of system in place to allow simple, secure mirroring?
--------------enig589DA4DD07D83F99A1ACC729
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJRfr4SAAoJEJr6+71xx0TYr7EQAK56GCc6l/DFZ2l0xwz1rHoo
48Z5COpW9zinz+pgKNEqwIJCCugipH8QyVXDvNGkloB2XnjvAyM7cgqX+rPyoawh
NWnvvhEHUWJfS+OI3ezVomtgscMY9ZjnE0Mxwn84Wzks1q5VeHlG5z+pajDcsPUC
eLt7fvDxo/yeRNFca/Lw4zDwZHIt7tf1c1PkkGtwN5vVjglMi1bbQe6dG8F/AwjS
tJezfkI0juiYsouQNxd22PD4LhAwXr9ypMEZm2y8eDl0rA4sHg6uQgHHAA19tX6b
l6vRhTkDQ9ZvzMC3VrT0GCyuxC+7ofpwx3xJxXRyPEgnUI2nyaKKh3Ki6kDm/Tf8
7+9Z6sph14UdsSk0qFylj2dJ4YZGXH6AtGHuY22REtkFKkaiaCL6WTk+MBLO256r
R1xH/wgYzWpqDspbFNWoVeYFzBcK4QewVVrmkF8qYOeo1UmzZh2Lj4pCPczLe0wt
nuJbN6gRF1f2ArN2MzPpFGkFGGuoMJ1NeTqIT3VA8xoTmukxbNlWY8DPVCIDBZhz
dVDl0Sm1HcaPnfxfPOAWpwrNTqsBhktD7Hx1G7OWq6q3MpJNsjLglOiUJfr5l0LV
C2qNvVDPUvdaRRoAIkrgbxXZar5Np3Q7uZyvdvt8YNNQYqbrf5gfnTq+MjV0mQXB
QNHTSi/Wagl+HhzHzZbb
=RQY7
-----END PGP SIGNATURE-----
--------------enig589DA4DD07D83F99A1ACC729--
Am 29.04.2013 20:37, schrieb 1100110:
On 03/30/2013 12:29 PM, Sönke Ludwig wrote:
I'll check with them at the end of the week when I'm back home and
things are still not working.Version updates are back working. Still need to fix IPv6, but fortunately that does not impede anything else.
I've been thinking about this for a while, and this seems to be the
perfect opportunity.Is there any sort of system in place to allow simple, secure mirroring?
There is no specific function, but one relatively easy way would be to
start the dub-registry site in a special mode, in which it periodically
queries an upstream registry for packages and adds those to its own
database. In that mode it wouldn't allow user registrations, but put
everything under a single special user account. ...and then
https://github.com/rejectedsoftware/dub/issues/22 still needs to be
fully implemented to use the fallback mirrors of course.
Speaking of that, it would also be good to find a proper domain name for
the main registry. After all, DUB has nothing really to do with vibe.d
anymore.
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig19E7FC06FEF3AB8DEA1CA8B9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 04/30/2013 02:25 AM, S=C3=B6nke Ludwig wrote:
Am 29.04.2013 20:37, schrieb 1100110:
On 03/30/2013 12:29 PM, S=C3=B6nke Ludwig wrote:
I'll check with them at the end of the week when I'm back home and=20
things are still not working.Version updates are back working. Still need to fix IPv6, but fortuna=
tely that does not impede anything else.
I've been thinking about this for a while, and this seems to be the
perfect opportunity.Is there any sort of system in place to allow simple, secure mirroring=
?
=20
There is no specific function, but one relatively easy way would be to
start the dub-registry site in a special mode, in which it periodically=queries an upstream registry for packages and adds those to its own
database. In that mode it wouldn't allow user registrations, but put
everything under a single special user account. ...and then
https://github.com/rejectedsoftware/dub/issues/22 still needs to be
fully implemented to use the fallback mirrors of course.
=20
Speaking of that, it would also be good to find a proper domain name fo=
r
the main registry. After all, DUB has nothing really to do with vibe.d
anymore.
=20
Well... I own dlib.us, I don't really have any plans for it...
--------------enig19E7FC06FEF3AB8DEA1CA8B9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJRgbAhAAoJEJr6+71xx0TY3TYP/RmbKpDOzxXhcbanR7vMPcGf
VQeEOXj+/41LPT1PtW3QWxcEMc2bJvxroOiz4p8Jn5KwAL4yrXr1+1dl6G3wb0Hz
dHoUcY8cT8gxUVYQ+xBhtYvOJMcivFFE4GIQ+uWW7QKKo2QNcEDllYanrVbFUBzh
skVNxtWtBrKJltkwMg9YHWA9nGzBDKu1PcC3MM/UOZDSSJgkGj//KizmVA0jXlK+
jP5W+F5AwRo0gm/JXTNafzxYQS9/0PkHfIhewD4akHTlyvv12ciF8bdBjL2CowXR
BogKMUPyA0tr1tk69fpdVss3AmjuFx5HTLLWBR6OnyLd+9Hd0/tJ3qTBpGsRZG7u
5oifFXwgRvUuNaMqf0e6adV7A05Wn2Zvn7K3wT3cVmBlTxYYnlpJuGsgU3md85A6
ntVT5uE3wy5nz/+8FvnaQRHeqx7vEXgwPdyT/JZl6gokB7AhE5zfs1DKnWyy06Q1
mn2kdyAJ2yN+FI96CvgeAhc//ppTEy8ap/sIb3TfjAgvR1EFDhJpzHSGRxirWvnp
4Pgwslo6RxALtUnFLIGxIUz5MT5ZYlL1VNESbojF3Eta7LeGl2tZxa3NyCT9o/uP
UwiTyTIIN894cchUG39noSFNIv2dxt4na3OT105dZW9//6YfqAumphO5D6xHcNoU
7ubvHUHxCjHtA76cbVMS
=HHxe
-----END PGP SIGNATURE-----
--------------enig19E7FC06FEF3AB8DEA1CA8B9--