Hi,
This is the 3th bugs against Helix package in our BTS.
I close these bug without reading them.
But for one I've some problem (bug 68343).
This bug has been closed 2 times and reopen 2 times. Here is the latest reopen:
What I need to do ?
**
At 10:46 AM 08/01/2000 -0700, Sean 'Shaleh' Perry wrote:
On 01-Aug-2000 Ben Steinberg wrote:
> I am in the new maintainers' queue, and have a package ready to go
> (lifelines, a genealogy program). Is it okay to upload my files to the
> upstream website at sourceforge, or is it preferable to wa
On 01-Aug-2000 Ben Steinberg wrote:
> I am in the new maintainers' queue, and have a package ready to go
> (lifelines, a genealogy program). Is it okay to upload my files to the
> upstream website at sourceforge, or is it preferable to wait until I'm an
> official developer?
>
if the upstream i
I am in the new maintainers' queue, and have a package ready to go
(lifelines, a genealogy program). Is it okay to upload my files to the
upstream website at sourceforge, or is it preferable to wait until I'm an
official developer?
Thanks,
Ben
...
At 10:46 AM 08/01/2000 -0700, Sean 'Shaleh' Perry wrote:
>On 01-Aug-2000 Ben Steinberg wrote:
> > I am in the new maintainers' queue, and have a package ready to go
> > (lifelines, a genealogy program). Is it okay to upload my files to the
> > upstream website at sourceforge, or is it preferable
On 01-Aug-2000 Ben Steinberg wrote:
> I am in the new maintainers' queue, and have a package ready to go
> (lifelines, a genealogy program). Is it okay to upload my files to the
> upstream website at sourceforge, or is it preferable to wait until I'm an
> official developer?
>
if the upstream
I am in the new maintainers' queue, and have a package ready to go
(lifelines, a genealogy program). Is it okay to upload my files to the
upstream website at sourceforge, or is it preferable to wait until I'm an
official developer?
Thanks,
Ben
..
Once upon a time, I heard Chanop Silpa-Anan say
> Hi,
>
> This is a little bit off topic but I've got a mail from debian-mentor list
> that crash mutt 1.2-1 (woody one).
Oh it happen only one particular machine where I set up mutt to my personal
taste.
I set charset=iso8859-11 since it's a char
Hi,
This is a little bit off topic but I've got a mail from debian-mentor list
that crash mutt 1.2-1 (woody one).
From strace, it says that mutt has opened a lot of charmap
[snip]
open("/usr/share/i18n/charmaps/T.61-8BIT", O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=30751, ...}) = 0
o
Once upon a time, I heard Chanop Silpa-Anan say
> Hi,
>
> This is a little bit off topic but I've got a mail from debian-mentor list
> that crash mutt 1.2-1 (woody one).
Oh it happen only one particular machine where I set up mutt to my personal
taste.
I set charset=iso8859-11 since it's a cha
Hi,
This is a little bit off topic but I've got a mail from debian-mentor list
that crash mutt 1.2-1 (woody one).
From strace, it says that mutt has opened a lot of charmap
[snip]
open("/usr/share/i18n/charmaps/T.61-8BIT", O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=30751, ...}) = 0
On Mon, Jul 31, 2000 at 04:49:44PM +0200, Christian Hammers wrote:
>
> Before forcing the maintainers to make themselfes the work to figure these
> dependencies out we should tell them that such a list already exists!
> (And don't tell me that they should have known it from various discussions
> u
On Mon, Jul 31, 2000 at 04:49:44PM +0200, Christian Hammers wrote:
>
> Before forcing the maintainers to make themselfes the work to figure these
> dependencies out we should tell them that such a list already exists!
> (And don't tell me that they should have known it from various discussions
>
13 matches
Mail list logo
