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
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
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
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
>
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.
Am 01.05.2018 um 23:35 schrieb Emmanuel Bourg:
> Le 01/05/2018 à 23:21, Markus Koschany a écrit :
>
>> apt source yourpackage ?
>
> This doesn't give a Git working copy.
The command git clone will give you a working copy.
You can also use
git clone
Le 01/05/2018 à 23:21, Markus Koschany a écrit :
> apt source yourpackage ?
This doesn't give a Git working copy.
> Seriously I can write you a little shell script that does all that for
> you too. If this is the only _real_ blocker, I'm more than happy to do that.
We'll probably also want to
Am 01.05.2018 um 23:17 schrieb Emmanuel Bourg:
> Le 01/05/2018 à 22:54, Markus Koschany a écrit :
>
>> debcheckout https://salsa.debian.org/java-team/yourpackage ?
>>
>> I don't understand why you would need such a tool that simply calls
>>
>> git clone
>>
>> though...
>
> It also pulls the
Le 01/05/2018 à 22:54, Markus Koschany a écrit :
> debcheckout https://salsa.debian.org/java-team/yourpackage ?
>
> I don't understand why you would need such a tool that simply calls
>
> git clone
>
> though...
It also pulls the upstream tarball and the .dsc of the latest upload.
Am 01.05.2018 um 22:49 schrieb Emmanuel Bourg:
> Le 01/05/2018 à 21:18, Markus Koschany a écrit :
>
>> I have tried to discuss this on debian-devel but as usual there is
>> always someone who strongly disagrees, mostly those people who update
>> five packages per year. In my opinion there is no
Le 01/05/2018 à 21:18, Markus Koschany a écrit :
> I have tried to discuss this on debian-devel but as usual there is
> always someone who strongly disagrees, mostly those people who update
> five packages per year. In my opinion there is no need to convince
> everyone. It's completely fine if
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
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
Hi,
Am 01.05.2018 um 20:31 schrieb Giovanni Mascellani:
> Hi,
>
> Il 29/04/2018 23:13, Markus Koschany ha scritto:
>> Let's remove all VCS fields from all our packages. Those fields are
>> optional and not required. We simply use conventions. All packages are
>> maintained in Git at
Hi,
Il 29/04/2018 23:13, Markus Koschany ha scritto:
> Let's remove all VCS fields from all our packages. Those fields are
> optional and not required. We simply use conventions. All packages are
> maintained in Git at salsa.debian.org. Period.
In line of principle I agree that some package meta
Am 29.04.2018 um 23:13 schrieb Markus Koschany:
[...]
> I suggest the following:
>
> Let's remove all VCS fields from all our packages. Those fields are
> optional and not required. We simply use conventions. All packages are
> maintained in Git at salsa.debian.org. Period. The address space
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
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
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
Le 29/04/2018 à 04:00, Paul Wise a écrit :
> I'd suggest deleting the migrated repositories so that DSA doesn't
> have to store a copy of them in the alioth archive forever.
Yes, I plan to do that once I'm confident the migration worked properly.
Emmanuel Bourg
On Mon, Apr 30, 2018 at 1:18 AM, tony mancill wrote:
> I realize that this isn't the right forum, so please redirect
> appropriately for follow-ups, but do you know whether there is any plan
> for a redirect host/service for the alioth repos? The BTS is full of
> links commits in Alioth, so the
Am 29.04.2018 um 22:33 schrieb Thorsten Glaser:
[...]
> As far as I’m informed, due to the massively different structure
> of GitLab, such a service cannot be provided with reasonable or
> even somewhat unreasonable effort, and there *were* tons of URL
> redirection layers already anyway, so they
Hi tony,
> On Sun, Apr 29, 2018 at 10:00:58AM +0800, Paul Wise wrote:
> > I'd suggest deleting the migrated repositories so that DSA doesn't
> > have to store a copy of them in the alioth archive forever.
in fact we were *requested* to do so by DSA, so we SHOULD comply.
> appropriately for
On Sun, Apr 29, 2018 at 10:00:58AM +0800, Paul Wise wrote:
> On Sat, Apr 28, 2018 at 4:48 AM, Emmanuel Bourg wrote:
>
> > Thank you Tony. I was leaning toward such a solution, but considering
> > that Alioth is going to be killed and the repositories archived and
> > moved offline there is no
On Sat, Apr 28, 2018 at 4:48 AM, Emmanuel Bourg wrote:
> Thank you Tony. I was leaning toward such a solution, but considering
> that Alioth is going to be killed and the repositories archived and
> moved offline there is no real point disabling the migrated
> repositories. I think I'll just move
On 27/04/2018 22:48, Emmanuel Bourg wrote:
> I think I'll just move them under a special directory (for
> example /srv/git.debian.org/git/pkg-java/migrated).
I migrated a first batch of ~100 Maven related packages. Moving the
repositories on Alioth wasn't a great idea since the import process on
On 19/04/2018 21:52, tony mancill wrote:
> Regarding item (1), perhaps you can leverage the disable-repository
> script [4]? I used the migration scripts from that repo for non-team
> migrations with good results.
Thank you Tony. I was leaning toward such a solution, but considering
that Alioth
On Mon, Apr 16, 2018 at 10:16:07PM +0200, Emmanuel Bourg wrote:
> Le 16/04/2018 à 20:30, Andreas Tille a écrit :
>
> > I noticed that under
> >
> >https://salsa.debian.org/java-team/
> >
> > some packages are migrated but the mass of packages is on Alioth as far
> > as I can see. Is there
Le 16/04/2018 à 20:30, Andreas Tille a écrit :
> I noticed that under
>
>https://salsa.debian.org/java-team/
>
> some packages are migrated but the mass of packages is on Alioth as far
> as I can see. Is there any migration date? I'm just asking since Alioth
> will be switched of in about
Hi,
On Thu, 1 Feb 2018 Emmanuel Bourg wrote:
> I personally would prefer migrating all
> the repositories simultaneously, leaving only the packages still managed
> by Subversion on Alioth for a migration later.
I noticed that under
https://salsa.debian.org/java-team/
some packages are
On 02/02/2018 12:31 AM, gregor herrmann wrote:
> On Thu, 01 Feb 2018 17:13:53 +0100, Bas Couwenberg wrote:
>
>>> Mehdi Dogguy wrote some scripts performing most of these operations [1],
>>> I'd like to assemble them into a unique script tailored for the Java
>>> team.
>> For the Debian GIS team I
On Thu, 01 Feb 2018 17:13:53 +0100, Bas Couwenberg wrote:
> > Mehdi Dogguy wrote some scripts performing most of these operations [1],
> > I'd like to assemble them into a unique script tailored for the Java
> > team.
> For the Debian GIS team I wrote similar scripts, see:
>
Le 01/02/2018 à 17:13, Bas Couwenberg a écrit :
> For the Debian GIS team I wrote similar scripts, see:
>
> https://lists.debian.org/debian-gis/2018/01/msg00023.html
Thank you for sharing! This will help.
Emmanuel Bourg
On 2018-02-01 15:22, Emmanuel Bourg wrote:
Ideally I'd like to come up with a migration script that :
1. imports the repository to Salsa
2. configures the hook notifying pkg-java-maintainers on pushes
3. configures the hook notifying the #debian-java channel on IRC
4. configures the hook adding
Le 01/02/2018 à 12:44, Hideki Yamane a écrit :
> Can someone import git repos in alioth to salsa under java-team?
> Use script with java-team ID (2588) like below with certain privilege
> would be fine.
Hi Hideki,
I started working on the migration to Salsa. This topic hasn't been
discussed
Hi,
Can someone import git repos in alioth to salsa under java-team?
Use script with java-team ID (2588) like below with certain privilege
would be fine.
#!/bin/sh
set -eux
PROJECT="${1%.git}"
DESCRIPTION="$PROJECT packaging"
36 matches
Mail list logo
