Sounds good. Thank you for your work on this!

On Sat, Mar 10, 2018 at 10:20 PM, Alexandre Viau <av...@debian.org> wrote:

> On 2018-03-01 11:16 AM, Alexandre Viau wrote:
> > On 2018-03-01 11:04 AM, Michael Stapelberg wrote:
> >> We still have 208 packages which don’t use a secure Vcs-* uri (but
> >> rather git://). Will redirects work for them, too, or will we need to
> >> upload a new version?
> >
> > I had not noticed this.The redirect won't work for these packages.
> >
> > I can selectively re-upload only these packages during the migration.
>
> I have modified my migration script to do that.
>
> However, if there are packages that have new un-uploaded upstream
> versions, I will leave them behind, as I don't want to risk
> automatically uploading new upstream versions. This means that there may
> still be some manual work to do after the migration, but it should be
> very minimal compared to what will be automated.
>
> Just to be clear:
>  - Packages that use the git:// scheme in their vcs-git urls, and that
> have uploaded modifications or upstream versions, will be left behind.
>
> I will produce a list of what was left behind, and the reason, so that
> we can finish the work. I may have the time to fix it all by myself
> during the migration.
>
> I'll send the migration email soon. So maybe we can migrate next monday,
> or the one after that.
>
> Sorry for the delay, I had very few times in the past weeks due to
> mid-semester.
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>


-- 
Best regards,
Michael
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to