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


Groups > linux.debian.maint.java > #10469

Re: Import git repo from alioth to salsa

From Giovanni Mascellani <gio@debian.org>
Newsgroups linux.debian.maint.java
Subject Re: Import git repo from alioth to salsa
Date 2018-05-02 09:10 +0200
Message-ID <vKU3M-6hS-1@gated-at.bofh.it> (permalink)
References (5 earlier) <vKbq2-OG-11@gated-at.bofh.it> <vKftD-3wm-1@gated-at.bofh.it> <vKkMG-7ea-11@gated-at.bofh.it> <vKnhw-AB-7@gated-at.bofh.it> <vKK4q-7LU-1@gated-at.bofh.it>
Organization Debian

Show all headers | View raw


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

Back to linux.debian.maint.java | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

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

csiph-web