Package: wnpp
Severity: wishlist
Owner: Michael Fladischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-sievelib
Version : 0.8
Upstream Author : Antoine Nguyen
* URL : https://pypi.python.org/pypi/sievelib
* License : Expat
Program
Once again, the python policy about Maintainer/Uploaders has been ignored
http://python-modules.alioth.debian.org/python-modules-policy.html#maintainership
https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
either policy changes or this has to stop at some point.
On Tue, Sep 29, 2015 at 1
[Sandro Tosi, 2015-09-29]
> Once again, the python policy about Maintainer/Uploaders has been ignored
>
> http://python-modules.alioth.debian.org/python-modules-policy.html#maintainership
> https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
>
> either policy changes or this has to stop at
On Tue, Sep 29, 2015 at 12:26:44 +0100, Sandro Tosi wrote:
> Once again, the python policy about Maintainer/Uploaders has been ignored
>
> http://python-modules.alioth.debian.org/python-modules-policy.html#maintainership
> https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
>
> either poli
> OTOH, this is experimental. It's not like this upload has any effect on
> anyone except to let Thomas work on packages that depend on it.
still the policy defines a set of rules that apply to any debian
suites, or are you suggesting that experimental is not cover by those
rules and we could do
On September 29, 2015 7:55:36 AM EDT, Julien Cristau
wrote:
>On Tue, Sep 29, 2015 at 12:26:44 +0100, Sandro Tosi wrote:
>
>> Once again, the python policy about Maintainer/Uploaders has been
>ignored
>>
>>
>http://python-modules.alioth.debian.org/python-modules-policy.html#maintainership
>> ht
On Sep 29, 2015, at 12:26 PM, Sandro Tosi wrote:
>Once again, the python policy about Maintainer/Uploaders has been ignored
>
>either policy changes or this has to stop at some point.
A few observations.
The policy should perhaps be better promoted or more explicitly written. The
links you prov
On Tue, 29 Sep 2015 at 15:48 Barry Warsaw wrote:
> The wiki says that the general rule of thumb is to set the team as
> Maintainer,
> to which I agree. I may not have been as deliberate about my own
> packages, so
> I plan on reviewing them, and will fix any that aren't "special".
>
After readi
[Barry Warsaw, 2015-09-29]
> How should the change be acknowledged by the
> maintainer? Should I Cc the mailing list when I contact the maintainer? Is
do we really need a written policy how to contact fellow co-maintainer?
Ping on IRC, send an email, send a message via xmpp or phone, ... use
wh
On Sep 29, 2015, at 02:02 PM, Tristan Seligmann wrote:
>After reading this thread, I feel like I should go through all of my
>packages and remove the team from Maintainer for all of them. I try very
>hard to respond promptly to pings (bugs, email, IRC, ...) about my
>packages, even if it's just to
Hi,
Le mardi 29 sept. 2015 à 09:48:16 (-0400), Barry Warsaw a écrit :
> On Sep 29, 2015, at 12:26 PM, Sandro Tosi wrote:
>
> >Once again, the python policy about Maintainer/Uploaders has been ignored
> >
> >either policy changes or this has to stop at some point.
>
> A few observations.
>
> The
On Sep 29, 2015, at 05:40 PM, Julien Puydt wrote:
>- I want lintian not to bug me about NMU ;
This one's easy. Just put "Team upload" in the changelog (e.g. `dch --team`).
Cheers,
-Barry
Hi,
I am developing a plugin for IBus, written in python3. The project depends
on some other python modules and system packages, like python3-gi,
gir1.2-ibus-1.0 etc. Also, it needs to install data files to the system (
inside /usr/lib/ibus/component/) to make itself available to IBus. I am a
debia
On Sep 29, 2015, at 04:30 PM, Piotr Ożarowski wrote:
>Maintainer vs Uploaders rules needs to be moved to policy. I will
>propose a patch to the policy soon (I'd prefer a native speaker to do
>it, though)
+1, and I'd be happy to review the specific text.
Cheers,
-Barry
[Barry Warsaw, 2015-09-29]
> On Sep 29, 2015, at 05:40 PM, Julien Puydt wrote:
>
> >- I want lintian not to bug me about NMU ;
>
> This one's easy. Just put "Team upload" in the changelog (e.g. `dch --team`).
it's even easier than that... add yourself to Uploaders (you're
maintaining it after
Hi,
Le mercredi 30 sept. 2015 à 00:17:32 (+0600), Titon Barua a écrit :
> I found some online resource where someone suggested using autotools for
> building GTK+python applications. I can definitely go that route, but how
> would it affect packaging for debian? How am I supposed to specify the
>
Le mardi 29 sept. 2015 à 20:40:11 (+0200), Piotr Ożarowski a écrit :
> [Barry Warsaw, 2015-09-29]
> > On Sep 29, 2015, at 05:40 PM, Julien Puydt wrote:
> >
> > >- I want lintian not to bug me about NMU ;
> >
> > This one's easy. Just put "Team upload" in the changelog (e.g. `dch
> > --team`).
[Julien Puydt, 2015-09-29]
> Yes, that's what I said: I put myself as uploaders so lintian
> doesn't bug me about NMU.
my guess¹ is that you used different name/email in debian/control and
debian/changelog
[¹] and it's the last one, include pointer to sources next time
(and remember to remov
On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
>(and remember to remove DPMT from debian/control if it's not in SVN ;P)
Given that the final git migration is imminent (really! otherwise I'm going to
scream ;), can we not force people to go through this churn right now?
Yes, let's discourag
Dnia 2015-09-27, nie o godzinie 10:28 -0400, Scott Kitterman pisze:
[ cut ]
> Yes. They have started. I think we're about a third of the way
> through Dependency level 1. Numpy is in Dependency level 5, so this
> is not unexpected for now. You can follow the progress in the
> transition tracker
Le mardi 29 sept. 2015 à 15:51:44 (-0400), Barry Warsaw a écrit :
> On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
>
> >(and remember to remove DPMT from debian/control if it's not in SVN ;P)
>
> Given that the final git migration is imminent (really! otherwise I'm going to
> scream ;), can
On Sep 29, 2015, at 10:31 PM, Julien Puydt wrote:
>I still have a series of things I plan to package for Debian ; those are
>Python Modules, and I'll use git. If that's a problem for the Debian
>Python Modules Team, can you point me to a more appropriate team?
This illustrates my concern. We'v
[Barry Warsaw, 2015-09-29]
> On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
>
> >(and remember to remove DPMT from debian/control if it's not in SVN ;P)
>
> Given that the final git migration is imminent (really! otherwise I'm going to
> scream ;), can we not force people to go through this
On Sep 29, 2015, at 11:05 PM, Piotr Ożarowski wrote:
>but it's OK to force others to search for repo location, used workflow,
>tool, naming convention, etc?
No, definitely not! We have the svn we all know and love , and if it's
not there, then it can only otherwise be in git with the workflow an
On Tuesday, September 29, 2015 11:05:19 PM Piotr Ożarowski wrote:
> [Barry Warsaw, 2015-09-29]
>
> > On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
> > >(and remember to remove DPMT from debian/control if it's not in SVN ;P)
> >
> > Given that the final git migration is imminent (really! ot
On Tuesday, September 29, 2015 04:48:09 PM Barry Warsaw wrote:
> On Sep 29, 2015, at 10:31 PM, Julien Puydt wrote:
> >I still have a series of things I plan to package for Debian ; those are
> >Python Modules, and I'll use git. If that's a problem for the Debian
> >Python Modules Team, can you poin
On Tuesday, September 29, 2015 10:31:23 PM Julien Puydt wrote:
> Le mardi 29 sept. 2015 à 15:51:44 (-0400), Barry Warsaw a écrit :
> > On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
> > >(and remember to remove DPMT from debian/control if it's not in SVN ;P)
> >
> > Given that the final git
❦ 29 septembre 2015 23:05 +0200, Piotr Ożarowski :
>> Yes, let's discourage any new packages from manually migrating or starting
>> out
>> in git just until flag day. But I'm not sure it's worth removing DPMT on
>> existing repos just to add it back, hopefully RSN.
>
> we agreed to something -
28 matches
Mail list logo
