FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CRUX > CRUX

 
 
LinkBack Thread Tools
 
Old 02-09-2011, 01:02 PM
Hazel Russman
 
Default Is this a "reportable" bug?

What counts as a reportable bug in Crux and what is "upstream" and therefore someone else's responsibility? I ask because there is a critical bug in Sylpheed v.310 (built last week) which seems to be identical to one reported on the Debian list on 2nd February (Bug #611855).
--
Hazel Russman <hazel_russman@yahoo.co.uk>
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux
 
Old 02-09-2011, 04:37 PM
acrux
 
Default Is this a "reportable" bug?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 9 Feb 2011 14:02:21 +0000
Hazel Russman <hazel_russman@yahoo.co.uk> wrote:

> What counts as a reportable bug in Crux and what is "upstream" and
> therefore someone else's responsibility? I ask because there is a
> critical bug in Sylpheed v.310 (built last week) which seems to be
> identical to one reported on the Debian list on 2nd February (Bug
> #611855).

hi,
as Sylpheed is my favourite client and i use it everyday i never
noticed this kind of problem.

Instead, if you use gnupg & gpgme you'll need pinentry-gtk2 too.

greetz,
- --
GNU/Linux on Power Architecture
CRUX PPC - http://cruxppc.org/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk1S0L8ACgkQxq34tDeO7LjA9wCfUvOz7/wpTWpfAw7NxOFH5mRa
P14AnjfPI6PB8uqchFSJR02g6tmaEVLv
=CeyX
-----END PGP SIGNATURE-----
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux
 
Old 02-09-2011, 04:52 PM
Juergen Daubert
 
Default Is this a "reportable" bug?

On Wed, Feb 09, 2011 at 02:02:21PM +0000, Hazel Russman wrote:
> What counts as a reportable bug in Crux and what is "upstream" and
> therefore someone else's responsibility? I ask because there is a
> critical bug in Sylpheed v.310 (built last week) which seems to be
> identical to one reported on the Debian list on 2nd February
> (Bug #611855).

That's definitely a upstream bug and not within our scope.

As a general rule our ports provide plain upstream software
without CRUX specific patches that go beyond configuration.
As always there are exceptions, e.g. if the program is no
longer maintained upstream but still required for some reason.
An example might be core/tcp_wrappers, for which we use the
patches collected by gentoo.


Greetings
Juergen

--
Juergen Daubert | mailto:jue@jue.li
Korb, Germany | http://jue.li/crux

_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux
 

Thread Tools




All times are GMT. The time now is 07:10 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org