-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I am a developper for MediaWiki ( http://www.mediawiki.org/ ) the php
wiki engine used by the free online encyclopedia Wikipedia.
I noticed the package wnpp got a bug against mediawiki ( #217571 ) and
that packaging is ongoing for more than 400 d
* Ashar Voultoiz [Sat, 18 Dec 2004 13:22:10 +0100]:
> Hello,
> I am a developper for MediaWiki ( http://www.mediawiki.org/ ) the php
> wiki engine used by the free online encyclopedia Wikipedia.
> I noticed the package wnpp got a bug against mediawiki ( #217571 ) and
> that packaging is ongoing
Hello,
I'm looking for a sponsor[1] for the package cpufrequtils[2], source
packages are available here:
deb-src http://oioio.altervista.org/debian source/
and i386 binaries here:
deb http://oioio.altervista.org/debian binary/
Both are built in a sid environment and lintian clean.
thanks a lot to
Hi,
I hope this isn't a too dumb question!
I'm the maintainer for xwrits, and partway through the NM process. My
application manager (Frank Lichtenheld) has sent me a review of my packages,
and I am confused about one of the things he suggested I do.
xwrits currently depends on xlibs-dev. Frank
On Sat, Dec 18, 2004 at 10:39:37PM +, Helen Faulkner wrote:
> Hi,
Hello.
> I hope this isn't a too dumb question!
;)
> I'm the maintainer for xwrits, and partway through the NM process. My
> application manager (Frank Lichtenheld) has sent me a review of my
> packages, and I am confused
El ds 18 de 12 del 2004 a les 22:39 +, en/na Helen Faulkner va
escriure:
> Hi,
>
> I hope this isn't a too dumb question!
>
> I'm the maintainer for xwrits, and partway through the NM process. My
> application manager (Frank Lichtenheld) has sent me a review of my packages,
> and I am confu
Hi everyone,
After checking appropriate docs and asking around and getting different
answers, I thought I'd see if there was any consensus on this:
How do you deal with new upstream releases? The general answers I'm getting
seem to be along the lines of "move the debian/ directory to the new
rele
On Sat, Dec 18, 2004 at 10:39:37PM +, Helen Faulkner wrote:
> Hi,
>
> I hope this isn't a too dumb question!
*peeking forward*: no, it isn't.
> xwrits currently depends on xlibs-dev. Frank suggests that I replace that
> with only the needed dependencies.
>
> So, the only thing I thought
On Sun, 2004-12-19 at 00:04, Bartosz Fenski aka fEnIo wrote:
> On Sat, Dec 18, 2004 at 10:39:37PM +, Helen Faulkner wrote:
> > Hi,
>
> Hello.
>
> > I hope this isn't a too dumb question!
>
> ;)
>
> > I'm the maintainer for xwrits, and partway through the NM process. My
> > application ma
* Erinn Clark <[EMAIL PROTECTED]> [2004:12:18 18:23 -0500]:
Of course, just after sending this mail, I was directed to:
http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream
...which I somehow managed to miss. It's still a bit sparse, so any other
tips people have for dealing w
Thanks Jeroen and all others who have answered :)
I'll have a go at the ideas you suggested and see how far I get with it...
d) Tell Frank to not be so annoying, since the advantage (a bit less
build-deps needed during build time, but no differences in the
resulting .debs) does not outweight
In gmane.linux.debian.devel.mentors, you wrote:
> So, the only thing I thought to do is
> a) look at every header file that is #included in the xwrits code
>
> But this will take me quite a long time. I wondered if I am missing
> something obvious and there is a better way to do it. Or am I on
On 20041218T182328-0500, Erinn Clark wrote:
> How do you deal with new upstream releases? The general answers I'm getting
> seem to be along the lines of "move the debian/ directory to the new
> release and tweak it til things work". Is this correct? If so (or if not),
> shouldn't there be somethin
On Sun, Dec 19, 2004 at 12:04:41AM +0100, Bartosz Fenski aka fEnIo wrote:
> > I'm the maintainer for xwrits, and partway through the NM process. My
> > application manager (Frank Lichtenheld) has sent me a review of my
> > packages, and I am confused about one of the things he suggested I do.
>
On Sun, Dec 19, 2004 at 02:48:02AM +0200, Antti-Juhani Kaijanaho wrote:
> Like with many other things in Debian, how you do it doesn't matter as
> long as you don't break things. Things that should be considered
> include:
> - Use a -1 Debian revision number for the new upstream release.
> - P
On Sat, 18 Dec 2004, Erinn Clark wrote:
> How do you deal with new upstream releases? The general answers I'm getting
I'd suggest using a version control system (even a lame one such as CVS), so
that you know exactly what changed from one upstream to another, and update
the debian/ stuff and any d
* Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [2004:12:18 23:53 -0200]:
> On Sat, 18 Dec 2004, Erinn Clark wrote:
> > How do you deal with new upstream releases? The general answers I'm getting
>
> I'd suggest using a version control system (even a lame one such as CVS), so
> that you know ex
Erinn Clark <[EMAIL PROTECTED]> writes:
> * Erinn Clark <[EMAIL PROTECTED]> [2004:12:18 18:23 -0500]:
>
>
> Of course, just after sending this mail, I was directed to:
>
> http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream
>
> ...which I somehow managed to miss. It's still a b
On Sat, Dec 18, 2004 at 01:36:07PM +0100, Adeodato Simó wrote:
> * Ashar Voultoiz [Sat, 18 Dec 2004 13:22:10 +0100]:
Hi, Ashar. I'm working on a mediawiki package for Debian; thus the ITP
registration. As you know, I'm also a MediaWiki developer.
I'l be happy to incorporate any features from your
19 matches
Mail list logo
