On 4 May 2005, at 6:39 pm, Wouter Verhelst wrote:
On Wed, May 04, 2005 at 04:35:25PM +0100, Tim Cutts wrote:
On 1 May 2005, at 8:53 am, Wouter Verhelst wrote:
True. However, it does no harm to add the conflicts, while it does
make
it easier for your users. When presented with a bug in another
On 1 May 2005, at 8:53 am, Wouter Verhelst wrote:
On Sun, May 01, 2005 at 12:38:41AM +0200, Jeroen van Wolffelaar wrote:
On Sat, Apr 30, 2005 at 06:45:26PM -0300, Otavio Salvador wrote:
But you remove the package from testing doesn't mean we won't
have
users with it installed since it was
On Wed, May 04, 2005 at 04:35:25PM +0100, Tim Cutts wrote:
On 1 May 2005, at 8:53 am, Wouter Verhelst wrote:
True. However, it does no harm to add the conflicts, while it does make
it easier for your users. When presented with a bug in another package
that completely breaks mine (rather than
On Sun, May 01, 2005 at 12:38:41AM +0200, Jeroen van Wolffelaar wrote:
On Sat, Apr 30, 2005 at 06:45:26PM -0300, Otavio Salvador wrote:
But you remove the package from testing doesn't mean we won't have
users with it installed since it was present there so, IMHO, the
Conflict is
On Sun, May 01, 2005 at 12:38:41AM +0200, Jeroen van Wolffelaar wrote:
On Sat, Apr 30, 2005 at 06:45:26PM -0300, Otavio Salvador wrote:
But you remove the package from testing doesn't mean we won't have
users with it installed since it was present there so, IMHO, the
Conflict is
On Sat, Apr 30, 2005 at 10:04:35PM +0200, Goswin von Brederlow wrote:
A Replaces without a Conflicts is I think always wrong.
No, absolutely not. See policy, section 7.5, for details -- especially
section 7.5.1.
--
The amount of time between slipping on the peel and landing on the
pavement is
Adam M. [EMAIL PROTECTED] writes:
Anthony DeRobertis wrote:
Klaus Ethgen wrote:
The according bug is #306608.
This is a bug, though possibly not in the libwxgtk2.4-python package. If
the relevant maintainers (libwxgtk2.4-python, wxpython2.5.3) and bug
sumitters can't work out a
Wouter Verhelst [EMAIL PROTECTED] writes:
On Sat, Apr 30, 2005 at 10:04:35PM +0200, Goswin von Brederlow wrote:
A Replaces without a Conflicts is I think always wrong.
No, absolutely not. See policy, section 7.5, for details -- especially
section 7.5.1.
Still leaves the following problem:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Just some respoces: (There is several quotings from several people.)
1st the tecnical:
Josselin Mouette:
As I understand the issue, I have to agree with the maintainer: the
conflict statement should be added in the wxwidgets 2.5 packages,
On Sun, May 01, 2005 at 09:56:42AM +0200, Wouter Verhelst wrote:
On Sat, Apr 30, 2005 at 10:04:35PM +0200, Goswin von Brederlow wrote:
A Replaces without a Conflicts is I think always wrong.
No, absolutely not. See policy, section 7.5, for details -- especially
section 7.5.1.
Policy is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
this is a maybe bit OT mail to this List but I think as improoving the
quality of debian is a bit toppic of the list.
The problem is that I do not know how to handle with a bug. The
maintainer of this bug is not in the mood to fix the bug he
On Sat, Apr 30, 2005 at 08:30:38PM +0200, Klaus Ethgen wrote:
The according bug is #306608.
having read through the bug report, it seems to me the appropriate thing
to have done all along was add a Conflicts statement, which really does
no harm and does resolve the issue.
HOWEVER, that said,
Le samedi 30 avril 2005 à 15:06 -0400, sean finney a écrit :
On Sat, Apr 30, 2005 at 08:30:38PM +0200, Klaus Ethgen wrote:
The according bug is #306608.
having read through the bug report, it seems to me the appropriate thing
to have done all along was add a Conflicts statement, which
Klaus Ethgen wrote:
The according bug is #306608.
It looks like the issue there (trying to quickly read through it) is if
package libwxgtk2.4-python nedds to declare a Conflicts: with package
wxpython2.5.3. The reason being that both provide a /usr/bin/helpviewer.
First off, this is a tad bit
(reply to public mail sent to d-devel).
On Sat, 30 Apr 2005, Klaus Ethgen wrote:
The problem is that I do not know how to handle with a bug. The
maintainer of this bug is not in the mood to fix the bug he rather
slight the submitters (not only me) in the bugreport and also by private
mail.
On Sat, 30 Apr 2005, sean finney wrote:
having read through the bug report, it seems to me the appropriate thing
to have done all along was add a Conflicts statement, which really does
no harm and does resolve the issue.
Wrong. The other package has a broken replaces header, without the
On Sat, Apr 30, 2005 at 04:36:29PM -0300, Henrique de Moraes Holschuh wrote:
Wrong. The other package has a broken replaces header, without the required
conflicts header it needs to have.
yeah, looks like i was. that said, the rest of my response (this should
be forwarded to the tech
Anthony DeRobertis wrote:
Klaus Ethgen wrote:
The according bug is #306608.
This is a bug, though possibly not in the libwxgtk2.4-python package. If
the relevant maintainers (libwxgtk2.4-python, wxpython2.5.3) and bug
sumitters can't work out a solution, then ask the Technical
Anthony DeRobertis [EMAIL PROTECTED] writes:
Klaus Ethgen wrote:
The according bug is #306608.
It looks like the issue there (trying to quickly read through it) is if
package libwxgtk2.4-python nedds to declare a Conflicts: with package
wxpython2.5.3. The reason being that both provide a
On Sat, Apr 30, 2005 at 03:06:31PM -0400, sean finney wrote:
On Sat, Apr 30, 2005 at 08:30:38PM +0200, Klaus Ethgen wrote:
The according bug is #306608.
having read through the bug report, it seems to me the appropriate thing
to have done all along was add a Conflicts statement, which really
steve == Steve Langasek [EMAIL PROTECTED] writes:
steve On Sat, Apr 30, 2005 at 03:06:31PM -0400, sean finney
steve wrote:
On Sat, Apr 30, 2005 at 08:30:38PM +0200, Klaus Ethgen wrote:
The according bug is #306608.
having read through the bug report, it seems to me the
On Sat, Apr 30, 2005 at 06:45:26PM -0300, Otavio Salvador wrote:
But you remove the package from testing doesn't mean we won't have
users with it installed since it was present there so, IMHO, the
Conflict is need.
The bug is in the other package, packages are not required to work
22 matches
Mail list logo
