Futures 0.2 has been yanked

[Igor Gnatenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hey,

Recently upstream of "futures" crate yanked all 0.2 releases and pushed
them as "futures-preview". I wonder what we should do in regard to this…

Also there is no way to get automatic notifications whether upstream has
yanked something, we probably want to build some automation in anitya.

Thoughts?
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAls49dMACgkQaVcUvRu8
> X0yE7w/9Gma8yrqEPGQfC4uIPZKtmqmrsqzNiHZ3G+sNSdeXLY75gmqHM5zKVyze
> nRqcXR4ZQNQ/LnN7AlG5hsJEhfOWlBMWEECZUshV2YdmjSEbtd6ZW6kMOlMGKzCb
> fVCeMUQV4jbXSvVsS306UFu05FKn2g9lPeTuqN16PKRjPN2lnxEjteOhRvWTbDlX
> AFPYU+XuWm4u33JBAuq+AJWo3OVGVuNRRQGfJqy7wTAF9fvBH+F/ZC/kV87/yzcN
> 4zo2a9hd589R02SbkL97ZxZz37lXmyy3UtkmpEWFNDFD10amJNpkc9Z4ZBM9f8kY
> NFNSStGxLxsIWrFl0QoFZzAzMuRKVUMaizCkIYBVpQqeP894Uq8f4GBIPn3Q50J1
> JbVrV4jkDCBjDJb8s/IgNjUQU+SqWh5cPwqHBcjkUIXq5YHw3s1aNtGHhsvo9oXn
> KkRmDShpAYh9j7OLKxmgAIbMuKbOlxXoAfljlxRJiTmPqSHvRJoJM8X2U3K98NjC
> f8/Me6sKgUuVZ44IFIYGeXVofOzb+47SeCHp7Z45C29o6nwjp6PT0FrRKbvYznao
> sHKehMTkZ2RKg5ei1UlB64IuargGLxO1qq08n3pzVRMxy8C0RIftOU39hE7+p/OE
> wiaNPoZJn78ZH9g+sOzSSnSOwWOCpF5sKIwN+i/V5y0E5oyaEvI=
> =19YJ
> -----END PGP SIGNATURE----- 
-- 

-Igor Gnatenko

[Ximin Luo]

Igor Gnatenko:
>  Hey,
>  
>  Recently upstream of "futures" crate yanked all 0.2 releases and pushed
>  them as "futures-preview". I wonder what we should do in regard to this…
>  
>  Also there is no way to get automatic notifications whether upstream has
>  yanked something, we probably want to build some automation in anitya.
>  
>  Thoughts?
>   
AFAIU yanking just means that no new crates can be published that depend on it, but old
crates that still depend on it will still be able to access it in order to satisfy the
dependency requirements. Distros should just be able to ignore the yanking?

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

[Igor Gnatenko]

On Sun, Jul 1, 2018 at 8:10 PM Ximin Luo <infinity0(a)debian.org&gt; wrote:

>  Igor Gnatenko:
>  > Hey,
>  >
>  > Recently upstream of "futures" crate yanked all 0.2 releases and pushed
>  > them as "futures-preview". I wonder what we should do in regard to this…
>  >
>  > Also there is no way to get automatic notifications whether upstream has
>  > yanked something, we probably want to build some automation in anitya.
>  >
>  > Thoughts?
>  >
>
>  AFAIU yanking just means that no new crates can be published that depend
>  on it, but old crates that still depend on it will still be able to access
>  it in order to satisfy the dependency requirements. Distros should just be
>  able to ignore the yanking?
>  
Yes, but I wonder if it's what we want to do. Some upstreams will move into
using futures-preview from now on and I wonder if we should package
-preview versions and having symlinks or...?
-- 

-Igor Gnatenko

[Josh Stone]

On 07/01/2018 12:10 PM, Ximin Luo wrote:
>  Igor Gnatenko:
> > Hey,
> >
> > Recently upstream of "futures" crate yanked all 0.2 releases and pushed
> > them as "futures-preview". I wonder what we should do in regard to this…
> >
> > Also there is no way to get automatic notifications whether upstream has
> > yanked something, we probably want to build some automation in anitya.
> >
> > Thoughts?
> >
>  
>  AFAIU yanking just means that no new crates can be published that depend on it, but old
> crates that still depend on it will still be able to access it in order to satisfy the
> dependency requirements. Distros should just be able to ignore the yanking? 
Often yanking means there was a serious problem with that release.  I
think in most cases that would be followed by a fixed release, so the
distro could just update further, but it would still be nice for us to
have some notification that this happened.