Hi Lumin,
On Tue, Feb 06, 2018 at 03:27:22PM +, Lumin wrote:
> With patch [1] dpkg-buildpackage can go a bit further while building
> this package.
> See requirements-dev.txt. And new problems arose:
I've added python-flask to Build-Depends and can reproduce this issue:
> 1. $ make test #
[Ole Streicher, 2018-02-07]
> Piotr Ożarowski writes:
> > [W. Martin Borgert, 2018-02-07]
> >> And how about merging the modules and apps teams into one?
> >
> > I don't understand this, though. Why you want to merge them?
> > Sure, packaging Python applications is very similar to packaging
> > li
Piotr Ożarowski writes:
> [W. Martin Borgert, 2018-02-07]
>> And how about merging the modules and apps teams into one?
>
> I don't understand this, though. Why you want to merge them?
> Sure, packaging Python applications is very similar to packaging
> libraries but the difference is very signifi
Hello,
On Wed, 07 Feb 2018, W. Martin Borgert wrote:
> how about moving the Python team(s) to salsa?
Definitely!
But we might want to learn from the perl team to structure the
python-team:
https://lists.debian.org/debian-perl/2018/01/msg00039.html
We could then have everything python related in
On 2018-02-07 09:58, Matthias Klose wrote:
> I don't think that is a good idea. Both teams are not very active when it
> comes
> to address RC issues and updating to new upstream versions. From my point of
> view the apps team is worse than the modules team in this regard.
In fact, this is one
[W. Martin Borgert, 2018-02-07]
> how about moving the Python team(s) to salsa?
that's the natural place to move from alioth for both teams.
PAPT's repos will also have to be converted from svn to git.
All we need is a volunteer who will prepare it and supervise the
process.
> And how about mergi
On 07.02.2018 10:12, Ghislain Vaillant wrote:
> 2018-02-07 8:58 GMT+00:00 Matthias Klose :
>> On 07.02.2018 08:37, W. Martin Borgert wrote:
>>> Hi,
>>>
>>> how about moving the Python team(s) to salsa?
>>> And how about merging the modules and apps teams into one?
>>>
>>> Moving git packages (modul
2018-02-07 8:58 GMT+00:00 Matthias Klose :
> On 07.02.2018 08:37, W. Martin Borgert wrote:
>> Hi,
>>
>> how about moving the Python team(s) to salsa?
>> And how about merging the modules and apps teams into one?
>>
>> Moving git packages (modules team) is very easy using
>> import.sh from https://s
On 07.02.2018 08:37, W. Martin Borgert wrote:
> Hi,
>
> how about moving the Python team(s) to salsa?
> And how about merging the modules and apps teams into one?
>
> Moving git packages (modules team) is very easy using
> import.sh from https://salsa.debian.org/mehdi/salsa-scripts.git
>
> Movin
Hi,
2018-02-07 8:37 GMT+01:00 W. Martin Borgert :
> how about moving the Python team(s) to salsa?
>
+1
> And how about merging the modules and apps teams into one?
>
+1
> Moving git packages (modules team) is very easy using
> import.sh from https://salsa.debian.org/mehdi/salsa-scripts.git
Le 7 févr. 2018 07:38, "W. Martin Borgert" a écrit :
Hi,
how about moving the Python team(s) to salsa?
I'd be in favour for that.
And how about merging the modules and apps teams into one?
Same here. A single Python Team (python-team in salsa) would make sense.
Moving git packages (module
11 matches
Mail list logo
