Michael Moerz <[EMAIL PROTECTED]> writes:
> The problem is that metamail makes use of mkstemp and it leaves
> tmp files behind
> [...]
> 1) I could add each tmp file to a list and clean it up before the
>program leaves. (that would not require to touch even a single
>line of code, but I wo
Hi!
I am currently trying to fix the "only open" wishlist bug for
metamail. (I have fixed the rest and tryed to get a sponsor
already and I am in the nm - queue ).
The problem is that metamail makes use of mkstemp and it leaves
tmp files behind, when it is invoked with a multipart mime
message. S
Michael Moerz <[EMAIL PROTECTED]> writes:
> The problem is that metamail makes use of mkstemp and it leaves
> tmp files behind
> [...]
> 1) I could add each tmp file to a list and clean it up before the
>program leaves. (that would not require to touch even a single
>line of code, but I w
Hi!
I am currently trying to fix the "only open" wishlist bug for
metamail. (I have fixed the rest and tryed to get a sponsor
already and I am in the nm - queue ).
The problem is that metamail makes use of mkstemp and it leaves
tmp files behind, when it is invoked with a multipart mime
message.
On Nov 26, Atsuhito Kohda <[EMAIL PROTECTED]> wrote:
>I plan to add a new feature so that xearth can display
>city name in Japanese when a user sets LANG=ja_JP.eucJP
>and I am not sure but I guess it can support Chinese and/or
>Hangul.
Please use gettext, then other translators will not have t
On Nov 26, Atsuhito Kohda <[EMAIL PROTECTED]> wrote:
>I plan to add a new feature so that xearth can display
>city name in Japanese when a user sets LANG=ja_JP.eucJP
>and I am not sure but I guess it can support Chinese and/or
>Hangul.
Please use gettext, then other translators will not have
On Sunday 26 November 2000 21:17, Steve Robbins wrote:
> On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
> > On Sunday 26 November 2000 20:40, Steve Robbins wrote:
> > > 1. Automake inserts a makefile variable "TAR" into every Makefile.in
> > > generated. Upstream has "TAR = gtar", but I have "TAR
On Sunday 26 November 2000 21:22, Adrian Bunk wrote:
> On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
> >...
> > have to use it just once. Probably you will not avoid to rebuild
> > configure stuff but I think it's not a problem, just only bigger
> > *.diff.gz.
>
> You can avoid the bigger *.diff.g
On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
>...
> have to use it just once. Probably you will not avoid to rebuild configure
> stuff but I think it's not a problem, just only bigger *.diff.gz.
You can avoid the bigger *.diff.gz if you remove generated files like
configure in the clean target.
On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
> On Sunday 26 November 2000 20:40, Steve Robbins wrote:
> > 1. Automake inserts a makefile variable "TAR" into every Makefile.in
> > generated. Upstream has "TAR = gtar", but I have "TAR = tar", greatly
> > (and needlessly) inflating the .diff. The
On Sunday 26 November 2000 20:40, Steve Robbins wrote:
> 1. Automake inserts a makefile variable "TAR" into every Makefile.in
> generated. Upstream has "TAR = gtar", but I have "TAR = tar", greatly
> (and needlessly) inflating the .diff. The value of TAR is hardcoded into
> automake itself.
I do
Hi,
The package I'm working on [Geomview] uses automake & autoconf, so I
thought "great! I know how this stuff works". But I keep running into
small buglets like the following.
1. Automake inserts a makefile variable "TAR" into every Makefile.in
generated. Upstream has "TAR = gtar", but I hav
On Sunday 26 November 2000 21:17, Steve Robbins wrote:
> On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
> > On Sunday 26 November 2000 20:40, Steve Robbins wrote:
> > > 1. Automake inserts a makefile variable "TAR" into every Makefile.in
> > > generated. Upstream has "TAR = gtar", but I have "TAR
On Sunday 26 November 2000 21:22, Adrian Bunk wrote:
> On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
> >...
> > have to use it just once. Probably you will not avoid to rebuild
> > configure stuff but I think it's not a problem, just only bigger
> > *.diff.gz.
>
> You can avoid the bigger *.diff.
On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
>...
> have to use it just once. Probably you will not avoid to rebuild configure
> stuff but I think it's not a problem, just only bigger *.diff.gz.
You can avoid the bigger *.diff.gz if you remove generated files like
configure in the clean target
On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
> On Sunday 26 November 2000 20:40, Steve Robbins wrote:
> > 1. Automake inserts a makefile variable "TAR" into every Makefile.in
> > generated. Upstream has "TAR = gtar", but I have "TAR = tar", greatly
> > (and needlessly) inflating the .diff. Th
On Sunday 26 November 2000 20:40, Steve Robbins wrote:
> 1. Automake inserts a makefile variable "TAR" into every Makefile.in
> generated. Upstream has "TAR = gtar", but I have "TAR = tar", greatly
> (and needlessly) inflating the .diff. The value of TAR is hardcoded into
> automake itself.
I d
Hi,
The package I'm working on [Geomview] uses automake & autoconf, so I
thought "great! I know how this stuff works". But I keep running into
small buglets like the following.
1. Automake inserts a makefile variable "TAR" into every Makefile.in
generated. Upstream has "TAR = gtar", but I ha
On Sun, Nov 26, 2000 at 05:06:15PM +0100, Domenico Andreoli wrote:
> my AM is a very busy one and now a couple of months are gone since the first
> contact. i'm still waiting for the "Philosophy and Procedures Check" being
> checked.
>
> as soon as i posted my application i looked around for a pac
On Mon, Nov 20, 2000 at 03:53:12PM +, Paul Martin wrote:
> On Mon, Nov 20, 2000 at 08:05:06AM -0500, stramiello wrote:
> > How long does it take after submitting my info to the webpage until I hear
> > from an AM? Just curious since its been a few weeks...
>
> It can take months. Once you've b
On Sun, 26 Nov 2000, Josip Rodin wrote:
> Yes, build daemons for i386, m68k, sparc, powerpc should be active.
> I'm not sure about the alpha one, but there's always Chris Chimelis :)
Hehehe...just call me Chris "build daemon" Chimelis :-) If dinstall puts
a package into the master archives, I b
#include
peter karlsson wrote on Sun Nov 26, 2000 um 02:10:44PM:
> I have a program that is building against Qt 2.1 that I would like to
> upload, but I notice that only Qt 2.2 is available in woody, and I
> would prefer not to install Qt 2.2, since it requires XFree86 4.0.1,
> which removes a nu
On Sun, Nov 26, 2000 at 02:46:37PM +0100, peter karlsson wrote:
> > You can upload the sources only nowadays...
>
> There are autobuilders for all platforms that handle the compilations
> for me, then?
Yes, build daemons for i386, m68k, sparc, powerpc should be active.
I'm not sure about the alph
I'm trying to do a source only upload, but I'm failing to get
dpkg-source not to overwrite my tarfile (I would like to use the exact
same tarfile as my official distribution of the program, not re-pack it
for Debian).
I'm running "dpkg-source -ss -sn -b ", but it is still
overwriting the tarfile..
On Sun, Nov 26, 2000 at 05:06:15PM +0100, Domenico Andreoli wrote:
> my AM is a very busy one and now a couple of months are gone since the first
> contact. i'm still waiting for the "Philosophy and Procedures Check" being
> checked.
>
> as soon as i posted my application i looked around for a pa
Josip Rodin:
> You can upload the sources only nowadays...
There are autobuilders for all platforms that handle the compilations
for me, then?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/re
On Mon, Nov 20, 2000 at 03:53:12PM +, Paul Martin wrote:
> On Mon, Nov 20, 2000 at 08:05:06AM -0500, stramiello wrote:
> > How long does it take after submitting my info to the webpage until I hear
> > from an AM? Just curious since its been a few weeks...
>
> It can take months. Once you've
On Sun, Nov 26, 2000 at 02:10:44PM +0100, peter karlsson wrote:
> I have a program that is building against Qt 2.1 that I would like to
> upload, but I notice that only Qt 2.2 is available in woody, and I
> would prefer not to install Qt 2.2, since it requires XFree86 4.0.1,
> which removes a numbe
Hi!
I have a program that is building against Qt 2.1 that I would like to
upload, but I notice that only Qt 2.2 is available in woody, and I
would prefer not to install Qt 2.2, since it requires XFree86 4.0.1,
which removes a number of programs that I use regurarly.
Should I
1) upload the packag
On Sun, 26 Nov 2000, Roberto Suarez Soto wrote:
> > cdcover
> > wallp
>
> I would like to adopt these two. I'm not using wallp now, but I used
> it a while ago and I liked it; and I hope to buy a cd-burner soon and have a
> reason to use cdcover :-)
They are now your packages.
cu,
Adr
On Sun, 26 Nov 2000, Josip Rodin wrote:
> Yes, build daemons for i386, m68k, sparc, powerpc should be active.
> I'm not sure about the alpha one, but there's always Chris Chimelis :)
Hehehe...just call me Chris "build daemon" Chimelis :-) If dinstall puts
a package into the master archives, I
#include
peter karlsson wrote on Sun Nov 26, 2000 um 02:10:44PM:
> I have a program that is building against Qt 2.1 that I would like to
> upload, but I notice that only Qt 2.2 is available in woody, and I
> would prefer not to install Qt 2.2, since it requires XFree86 4.0.1,
> which removes a n
On Sun, Nov 26, 2000 at 02:46:37PM +0100, peter karlsson wrote:
> > You can upload the sources only nowadays...
>
> There are autobuilders for all platforms that handle the compilations
> for me, then?
Yes, build daemons for i386, m68k, sparc, powerpc should be active.
I'm not sure about the alp
I'm trying to do a source only upload, but I'm failing to get
dpkg-source not to overwrite my tarfile (I would like to use the exact
same tarfile as my official distribution of the program, not re-pack it
for Debian).
I'm running "dpkg-source -ss -sn -b ", but it is still
overwriting the tarfile.
On Nov/24/2000, Adrian Bunk wrote:
> cdcover
> wallp
I would like to adopt these two. I'm not using wallp now, but I used
it a while ago and I liked it; and I hope to buy a cd-burner soon and have a
reason to use cdcover :-)
--
Roberto Suarez Soto And at d
Josip Rodin:
> You can upload the sources only nowadays...
There are autobuilders for all platforms that handle the compilations
for me, then?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/r
On Sun, Nov 26, 2000 at 02:10:44PM +0100, peter karlsson wrote:
> I have a program that is building against Qt 2.1 that I would like to
> upload, but I notice that only Qt 2.2 is available in woody, and I
> would prefer not to install Qt 2.2, since it requires XFree86 4.0.1,
> which removes a numb
Hi!
I have a program that is building against Qt 2.1 that I would like to
upload, but I notice that only Qt 2.2 is available in woody, and I
would prefer not to install Qt 2.2, since it requires XFree86 4.0.1,
which removes a number of programs that I use regurarly.
Should I
1) upload the packa
On Sun, 26 Nov 2000, Roberto Suarez Soto wrote:
> > cdcover
> > wallp
>
> I would like to adopt these two. I'm not using wallp now, but I used
> it a while ago and I liked it; and I hope to buy a cd-burner soon and have a
> reason to use cdcover :-)
They are now your packages.
cu,
Ad
On Nov/24/2000, Adrian Bunk wrote:
> cdcover
> wallp
I would like to adopt these two. I'm not using wallp now, but I used
it a while ago and I liked it; and I hope to buy a cd-burner soon and have a
reason to use cdcover :-)
--
Roberto Suarez Soto And at
40 matches
Mail list logo
