[Pkg-javascript-devel] <DKIM> Re: Migrating *all* packages from alioth to salsa (Was: migrating my packages from alioth to salsa)
Paolo Greppi
paolo.greppi at libpf.com
Wed Apr 25 09:31:47 BST 2018
Il 24/04/2018 18:52, Andreas Tille ha scritto:
> Hi Paolo,
>
> On Tue, Apr 24, 2018 at 04:17:35PM +0200, Paolo Greppi wrote:
>> That one is not in stretch but not in sid so it fails criterion 1.
>
> Criterion 1 is "are in sid/unstable" and I get
>
> $ apt-cache policy libjs-handlebars
> libjs-handlebars:
> Installiert: (keine)
> Installationskandidat: 3:4.0.10-5
> Versionstabelle:
> 3:4.0.10-5 501
> 501 http://httpredir.debian.org/debian testing/main amd64 Packages
> 501 http://httpredir.debian.org/debian testing/main i386 Packages
> 50 http://httpredir.debian.org/debian unstable/main amd64 Packages
> 50 http://httpredir.debian.org/debian unstable/main i386 Packages
>
> Am I missing something? I admit I also consider the criterion "belongs
I was referring to the source libjs-handlebars:
https://tracker.debian.org/pkg/libjs-handlebars
that was removed from testing on 2018-01-22.
There is a separate node-handlebars source:
https://tracker.debian.org/pkg/node-handlebars
which produces the libjs-handlebars binary that as you point out is installable now in sid.
So I think it is correct that I did not migrate the repo for the first one:
https://anonscm.debian.org/cgit/pkg-javascript/libjs-handlebars.git
because the right repo to migrate is the one for the second:
https://anonscm.debian.org/cgit/pkg-javascript/node-handlebars.git
and if you click this link it indeed redirects you to:
https://salsa.debian.org/js-team/node-handlebars
> to release xy" as some artificial criterion. Even packages outside sid
> have either some history (before removed from sid), might be in
> experimental - so interesting) or are in preparation (in new or even
> before uploaded to new). I fail to see any reason why those should not
> be restricted to salsa.
I agree, on the other hand we do not want to migrate cruft or dead repos like libjs-handlebars.
>> We may decide to perform a separate automated migration for those
>
> I'd strongly recommend this to save developer work.
I am ready to spend some more time doing automated migrations, if we agree on the selection criteria.
What about this:
1. the repo on alioth has seen some activity since January 1st 2018
2. there is no repo on salsa
3. there is no conflict with source or binary packages which we already migrated (this may need manual inspection)
I did:
ssh git.debian.org
cd /git/pkg-javascript
find . -name info -newermt 2018-01-01 -ls
this yields a list of 120 repos, of which 86 have already been migrated.
14 were already on salsa 2 days ago, so we are left with 20:
emojify.js
gitgraph.js
jquery-areyousure
libjs-autolink
libjs-dropzone
libjs-handlebars <-- !!
mathjax
node-clean-stack
node-compare-versions
node-is-utf8
node-jquery-backstretch
node-knockout
node-knockout-sortable
node-knockout-transformations
node-lightgallery
node-opentip
node-progressjs
node-tippex
rainloop
simplemde-markdown-editor
> Kind regards and thanks ro your work in any case
;-)
>
> Andreas.
Paolo
More information about the Pkg-javascript-devel
mailing list