Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #10409 > unrolled thread

Re: Import git repo from alioth to salsa

Back to article view | Back to linux.debian.maint.java

Contents

  Re: Import git repo from alioth to salsa Andreas Tille <andreas@an3as.eu> - 2018-04-16 20:40 +0200
    Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-04-16 22:20 +0200
      Re: Import git repo from alioth to salsa tony mancill <tmancill@debian.org> - 2018-04-19 22:00 +0200
        Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-04-28 10:00 +0200
          Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-04-28 13:00 +0200
          Re: Import git repo from alioth to salsa Paul Wise <pabs@debian.org> - 2018-04-29 04:10 +0200
            Re: Import git repo from alioth to salsa tony mancill <tmancill@debian.org> - 2018-04-29 19:20 +0200
              Re: Import git repo from alioth to salsa Thorsten Glaser <t.glaser@tarent.de> - 2018-04-29 22:50 +0200
                Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-04-29 23:20 +0200
                  Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-05-01 14:50 +0200
                  Re: Import git repo from alioth to salsa Giovanni Mascellani <gio@debian.org> - 2018-05-01 20:40 +0200
                    Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-05-01 21:20 +0200
                      Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-05-01 22:50 +0200
                        Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-05-01 23:00 +0200
                          Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-05-01 23:20 +0200
                            Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-05-01 23:30 +0200
                              Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-05-01 23:40 +0200
                                Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-05-01 23:50 +0200
              Re: Import git repo from alioth to salsa Paul Wise <pabs@debian.org> - 2018-04-30 04:30 +0200
            Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-04-30 09:30 +0200
              Re: Import git repo from alioth to salsa Giovanni Mascellani <gio@debian.org> - 2018-04-30 13:50 +0200
                Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-04-30 19:30 +0200
                  Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-04-30 21:30 +0200
                    Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-05-01 22:10 +0200
                      Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-05-04 11:50 +0200
                        Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-05-04 15:30 +0200
                          Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-05-04 15:50 +0200
                          Re: Import git repo from alioth to salsa Markus Koschany <apo@debian.org> - 2018-05-04 15:50 +0200
                  Re: Import git repo from alioth to salsa Giovanni Mascellani <gio@debian.org> - 2018-04-30 22:10 +0200
                    Re: Import git repo from alioth to salsa Emmanuel Bourg <ebourg@apache.org> - 2018-05-01 22:30 +0200
                      Re: Import git repo from alioth to salsa Giovanni Mascellani <gio@debian.org> - 2018-05-02 09:10 +0200

Page 2 of 2 — ← Prev page 1 [2]

#10441

Dear Emmanuel,

Il 30/04/2018 09:25, Emmanuel Bourg ha scritto:
> Yes, I plan to do that once I'm confident the migration worked properly.

Thank you very much for working on this migration. Is manual migration
of one's packages helpful, neutral or disruptive? I would like to upload
geogebra (and maybe other packages), and would take the chance to
migrate it and update Vcs-* tags, but I can wait for the migration to
finish if this would disturb your scripts.

Thanks, Giovanni.
-- 
Giovanni Mascellani <g.mascellani@gmail.com>
Postdoc researcher - Université Libre de Bruxelles

[toc] | [prev] | [next] | [standalone]

#10444

Le 30/04/2018 à 13:42, Giovanni Mascellani a écrit :

> Thank you very much for working on this migration. Is manual migration
> of one's packages helpful, neutral or disruptive? I would like to upload
> geogebra (and maybe other packages), and would take the chance to
> migrate it and update Vcs-* tags, but I can wait for the migration to
> finish if this would disturb your scripts.

Hi Giovanni,

I've moved the geogebra repository, could you check if it's ok?

  https://salsa.debian.org/java-team/geogebra

I think I'll just complete the mass migration myself, but I'll need help
afterward to check if everything is ok (like missing or empty
repositories). I'll also need help to migrate the ~60 packages still in
Subversion.

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10445

[Multipart message — attachments visible in raw view] — view raw

Am 30.04.2018 um 19:22 schrieb Emmanuel Bourg:
[...]
> I'll also need help to migrate the ~60 packages still in
> Subversion.

I believe we shouldn't panic about this. Do you have a list with names
of those packages? I can clone and import them into a single Git
repository (todo-subversion) ? and when we have time and there is a need
to we can convert them into proper single Git repositories.

[toc] | [prev] | [next] | [standalone]

#10459

Le 30/04/2018 à 21:20, Markus Koschany a écrit :

> I believe we shouldn't panic about this. Do you have a list with names
> of those packages? I can clone and import them into a single Git
> repository (todo-subversion) ? and when we have time and there is a need
> to we can convert them into proper single Git repositories.

We can get the list of packages still in SVN from the DDPO [1] after
keeping only the packages in unstable and sorting by VCS. This gives the
list below.

As I understand the SVN repository will be made available as an archive.
If we aren't able to convert the remaining packages in time we can
rebuild a SVN server somewhere based on the archive and convert the
packages later.

  asm3
  boilerpipe
  c3p0
  colorpicker
  fontchooser
  jama
  jardiff
  jcm
  jline
  kunststoff
  libajaxtags-java
  libbasicplayer-java
  libbsf-java
  libcobra-java
  libcommons-discovery-java
  libcommons-el-java
  libcommons-launcher-java
  libezmorph-java
  libflexdock-java
  libfonts-java
  libformula
  libisfreetype-java
  libisrt-java
  libjamon-java
  libjazzy-java
  libjcalendar-java
  libjcip-annotations-java
  libjdepend-java
  libjdom1-java
  libjdom2-java
  libjemmy2-java
  libjgrapht0.6-java
  libjgrapht0.8-java
  libjgraphx-java
  libjhlabs-filters-java
  libjlayer-java
  libjmac-java
  libjorbis-java
  libjrosetta-java
  liblastfm-java
  libloader
  libmp3spi-java
  libpdfrenderer-java
  libpixie-java
  libsimple-validation-java
  libswarmcache-java
  libswingx1-java
  libvorbisspi-java
  libxmpcore-java
  libyanfs-java
  mockobjects
  netbeans-cvsclient
  opencsv
  plexus-utils
  simple-xml
  slashtime
  stringtemplate
  swing-layout
  tagsoup
  werken.xpath
  xmlbeans
  xom

Emmanuel Bourg

[1]
https://qa.debian.org/developer.php?login=pkg-java-maintainers@lists.alioth.debian.org

[toc] | [prev] | [next] | [standalone]

#10478

[Multipart message — attachments visible in raw view] — view raw

Am 01.05.2018 um 22:07 schrieb Emmanuel Bourg:
[...]
>   asm3
>   boilerpipe
>   c3p0
>   colorpicker
>   fontchooser
>   jama
>   jardiff
>   jcm
>   jline
>   kunststoff
>   libajaxtags-java
>   libbasicplayer-java
>   libbsf-java
>   libcobra-java
>   libcommons-discovery-java
>   libcommons-el-java
>   libcommons-launcher-java
>   libezmorph-java
>   libflexdock-java
>   libfonts-java
>   libformula
>   libisfreetype-java
>   libisrt-java
>   libjamon-java
>   libjazzy-java
>   libjcalendar-java
>   libjcip-annotations-java
>   libjdepend-java
>   libjdom1-java
>   libjdom2-java
>   libjemmy2-java
>   libjgrapht0.6-java
>   libjgrapht0.8-java
>   libjgraphx-java
>   libjhlabs-filters-java
>   libjlayer-java
>   libjmac-java
>   libjorbis-java
>   libjrosetta-java
>   liblastfm-java
>   libloader
>   libmp3spi-java
>   libpdfrenderer-java
>   libpixie-java
>   libsimple-validation-java
>   libswarmcache-java
>   libswingx1-java
>   libvorbisspi-java
>   libxmpcore-java
>   libyanfs-java
>   mockobjects
>   netbeans-cvsclient
>   opencsv
>   plexus-utils
>   simple-xml
>   slashtime
>   stringtemplate
>   swing-layout
>   tagsoup
>   werken.xpath
>   xmlbeans
>   xom

I have converted all these packages and moved them to salsa.
libjgraphx-java, libjrosetta-java, xmlbeans, c3p0 and colorpicker did
already exist. The only step left now is to import the current (and
maybe stable/olstable) packages into Git when someone works on them
again. Git-buildpackage and gbp import-dsc come in handy for that.

Regards,

Markus

[toc] | [prev] | [next] | [standalone]

#10479

Le 04/05/2018 à 11:48, Markus Koschany a écrit :

> I have converted all these packages and moved them to salsa.

Thank you!

> libjgraphx-java, libjrosetta-java, xmlbeans, c3p0 and colorpicker did
> already exist.

Do you know if the existing repositories were up to date? The SVN
repository may have more changes if the Git repository wasn't used by
lack of upload with the updated Vcs-* fields.


> The only step left now is to import the current (and
> maybe stable/olstable) packages into Git when someone works on them
> again. Git-buildpackage and gbp import-dsc come in handy for that.

Do you mean the packages removed from unstable, still in SVN, and never
migrated to Git?

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10480

Le 04/05/2018 à 15:40, Markus Koschany a écrit :

> That's true. I didn't check whether the Git repository was up-to-date,
> only if it existed. By looking at colorpicker I can see your suspicion
> is confirmed. I would just import the latest version with gbp import-dsc
> though and be done with it.

I'd rather preserve the history, don't bother I'll reimport them.

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10481

[Multipart message — attachments visible in raw view] — view raw

Am 04.05.2018 um 15:26 schrieb Emmanuel Bourg:
> Le 04/05/2018 à 11:48, Markus Koschany a écrit :
> 
>> I have converted all these packages and moved them to salsa.
> 
> Thank you!
> 
>> libjgraphx-java, libjrosetta-java, xmlbeans, c3p0 and colorpicker did
>> already exist.
> 
> Do you know if the existing repositories were up to date? The SVN
> repository may have more changes if the Git repository wasn't used by
> lack of upload with the updated Vcs-* fields.

That's true. I didn't check whether the Git repository was up-to-date,
only if it existed. By looking at colorpicker I can see your suspicion
is confirmed. I would just import the latest version with gbp import-dsc
though and be done with it.

>> The only step left now is to import the current (and
>> maybe stable/olstable) packages into Git when someone works on them
>> again. Git-buildpackage and gbp import-dsc come in handy for that.
> 
> Do you mean the packages removed from unstable, still in SVN, and never
> migrated to Git?

The SVN->Git conversion gives us only the debian directory with all its
changes and tags, provided releases were tagged. I usually import the
complete package with all source code afterwards. I haven't done this
automatically because sometimes you want to import older releases as
well not only the latest one and I thought I leave that decision to the
next uploader of the package. In some cases it may even make sense to
just commit the debian directory because Git is not very good at
handling large binary files (images/sounds/videos) but this use case is
very rare for the Java team.

Markus

[toc] | [prev] | [next] | [standalone]

#10448

Hi,

Il 30/04/2018 19:22, Emmanuel Bourg ha scritto:
> I've moved the geogebra repository, could you check if it's ok?
> 
>   https://salsa.debian.org/java-team/geogebra

It is, thank you!

> I think I'll just complete the mass migration myself, but I'll need help
> afterward to check if everything is ok (like missing or empty
> repositories). I'll also need help to migrate the ~60 packages still in
> Subversion.

I can help to check, at least for my packages. I can also check others,
but maybe will not be as good as spotting problems.

For svn, I think I can help, although if you already have a list (as
Markus asked) that would help.

BTW, this recalls me that libjgrapht0.8 (which is my only package still
on svn) is probably in the need of some dust removal. Debian also ships
libjgrapht0.6 as a separate source package. Both are terribly old, since
upstream has released 1.1.0. However, I am a bit unsure on how to handle
this situation: I do not know much the API remained stable between 0.6,
0.6 and 1.1.0 and thus how to manage the update causing the least
inconvenience possible. I also have a similar problem with
libstax2-api-java and libwoodstox-java. Maybe it is better to wait for
the end of the migration, but if someone could at some point enlighten
me on the best practices, I would be grateful.

Thanks, Giovanni.
-- 
Giovanni Mascellani <g.mascellani@gmail.com>
Postdoc researcher - Université Libre de Bruxelles

[toc] | [prev] | [next] | [standalone]

#10460

Le 30/04/2018 à 22:02, Giovanni Mascellani a écrit :

> BTW, this recalls me that libjgrapht0.8 (which is my only package still
> on svn) is probably in the need of some dust removal. Debian also ships
> libjgrapht0.6 as a separate source package. Both are terribly old, since
> upstream has released 1.1.0. However, I am a bit unsure on how to handle
> this situation:

I suggest starting from scratch with a new unversioned jgrapht package
containing the latest upstream release. The reverse dependencies of the
versions 0.6 and 0.8 can later be updated to use the latest version if
necessary.


> I also have a similar problem with libstax2-api-java and libwoodstox-java.

What is the issue with these package?

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10469

Hi,

Il 01/05/2018 22:24, Emmanuel Bourg ha scritto:
> I suggest starting from scratch with a new unversioned jgrapht package
> containing the latest upstream release. The reverse dependencies of the
> versions 0.6 and 0.8 can later be updated to use the latest version if
> necessary.

Ok, thanks.

>> I also have a similar problem with libstax2-api-java and libwoodstox-java.
> 
> What is the issue with these package?

I have packaged in experimental new upstream releases, but I am not sure
on how to handle the little transition associated to them, not having
ever done such a thing. Upstream said that the new version should be
mostly compatible with the old one, except that the maven group id has
changed (but the namespaces did not).

So I guess what should happen is that I upload the new version, then go
through the reverse dependencies and file bugs/patches or directly
upload a new version for team maintained packages. But what if at some
point a reverse dependency does not build anymore with the new woodstox?
Should I first test rebuilding everything on my computer with the new
woodstox?

When I uploaded the packages to experimental, I emailed all the reverse
dependencies to ask them to test them, but noone answered. Then I forgot
about that thing until now.

So basically the questions boil down to: what is the best way to handle
a small transition for Java packages, trying to cause the less
disruption and surprise possible, but not depending on the
responsiveness of too many people?

Thanks, Giovanni.
-- 
Giovanni Mascellani <g.mascellani@gmail.com>
Postdoc researcher - Université Libre de Bruxelles

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.maint.java

csiph-web