On 6 February 2015 at 12:46, dino99 <email address hidden> wrote:
> Note: to avoid upcoming upgrading issues, it should be preferable to
> remove the 3.15.2 packages from "proposed" archive
>
huh? vivid-proposed must not be used by humans, and should not be
enabled during development stage of the release.
it is guaranteed to contain broken packages, and has upgrade skew.
vivid suite on the other hand is safe-guarded away from such breaks.
On 6 February 2015 at 12:46, dino99 <email address hidden> wrote:
> Note: to avoid upcoming upgrading issues, it should be preferable to
> remove the 3.15.2 packages from "proposed" archive
>
huh? vivid-proposed must not be used by humans, and should not be
enabled during development stage of the release.
it is guaranteed to contain broken packages, and has upgrade skew.
vivid suite on the other hand is safe-guarded away from such breaks.
--
Regards,
Dimitri.