On Sun, 9 Mar 2008 17:34:05 +0100 "Sandro Tosi" <[EMAIL PROTECTED]>
wrote:
>Hi all,
>I'd like to report here my feelings about the current way to maintain
>package in our repositories (DPMT and PAPT).
>
>As of now, policy[1] states that:
>
> Thus if you bring some packages into the team, you can
* Piotr Ożarowski <[EMAIL PROTECTED]> [2008-03-09 19:27:01 +0100]:
> Unless I'm wrong[0], I don't see a need to change the policy. INAL, but
> I think the policy allows me to do above (nasty) things :-)
I don't really think any of this is a problem, providing people stick to
common sense; for exa
[Piotr Ożarowski, 2008-03-09]
> * if DPMT/PAPT is in our repo. (no matter where the team name is, in
s,DPMT/PAPT,package
sorry
pgpN28nSzs0aN.pgp
Description: PGP signature
On Sun, Mar 09, 2008, Emilio Pozuelo Monfort wrote:
> For example, in the pkg-gnome team, it's even discouraged to put the team
> as the Maintainer, but everybody's welcome to touch any package, no
> matter who's listed as the Maintainer.
The rationale here is that packages with an assigned mai
Hi,
[Sandro Tosi, 2008-03-09]
> I'd like to report here my feelings about the current way to maintain
> package in our repositories (DPMT and PAPT).
my turn. How I understand the team relationship: [0]
* if DPMT/PAPT is in our repo. (no matter where the team name is, in
Maintainer or in Upload
Hello,
Sandro Tosi wrote:
Hi all,
I'd like to report here my feelings about the current way to maintain
package in our repositories (DPMT and PAPT).
As of now, policy[1] states that:
Thus if you bring some packages into the team, you can keep your
name in the Maintainer field. You will rec
Hi all,
I'd like to report here my feelings about the current way to maintain
package in our repositories (DPMT and PAPT).
As of now, policy[1] states that:
Thus if you bring some packages into the team, you can keep your
name in the Maintainer field. You will receive bug reports and
handle
Hi,
> (Paul pointed me here, so if you're getting this twice: my apologies)
>
>
> I'm looking to run my python2.5-dependent application (uses hashlib) on Etch,
> connecting to a mysql database.
> It appears the python-mysqldb package only provides for 2.3/2.4.
> I tried serveral things (link
Hello,
(Paul pointed me here, so if you're getting this twice: my apologies)
I'm looking to run my python2.5-dependent application (uses hashlib) on Etch,
connecting to a mysql database.
It appears the python-mysqldb package only provides for 2.3/2.4.
I tried serveral things (link modules, c
9 matches
Mail list logo
