On Sun, Jul 13, 2003 at 01:51:07PM +1000, Ben Burton wrote:
It seems then that our options are as follows.
(i) Wait for the Qt maintainers to upload a fix.
(ii) Do an NMU for Qt, despite the fact that this bug is not release-critical.
(iii) Resort to the technical committee.
(iv) Keep the
On Sat, Jul 12, 2003 at 11:51:18PM -0500, Steve Langasek wrote:
On Sun, Jul 13, 2003 at 01:51:07PM +1000, Ben Burton wrote:
It seems then that our options are as follows.
(i) Wait for the Qt maintainers to upload a fix.
(ii) Do an NMU for Qt, despite the fact that this bug is not
On Sun, Jul 13, 2003 at 12:14:52AM -0500, Branden Robinson wrote:
To punt this to the Technical Committee is to stall a solution for
potentially a very long time.
If you're certain you're right, and you can get the NMU correct, the
only people who will complain will be the package
I suppose there's always the option of NMUing, and hoping it sticks --
then taking it up with the tech ctte. if it doesn't...
This is more or less what I was thinking of. The impression I get is
that the Qt maintainers have shifted their stances on this issue from
defense to apathy. Though
Ben Burton writes:
Hi ho, it's time for another rant from me regarding the
libqt3-compat-headers split.
(i) Wait for the Qt maintainers to upload a fix.
(ii) Do an NMU for Qt, despite the fact that this bug is not
release-critical.
(iii) Resort to the technical committee.
(iv) Keep
I wouldn't do it. Suppose you were the Qt maintainer, and you made a
technical choice that some people disagree with
You mean a technical choice with a significant negative impact on users that
breaks compatibility with upstream and every other linux distribution
and that most (not some)
On Sun, Jul 13, 2003 at 12:14:52AM -0500, Branden Robinson wrote:
Bah, the Technical Committee takes months, sometimes over a year, to do
something even as seemingly uncontroversial as voting in opposition to
whichever solution Branden Robinson proposes.
So? This is more than enough time.
On Sun, Jul 13, 2003 at 01:51:07PM +1000, Ben Burton wrote:
It seems then that our options are as follows.
(i) Wait for the Qt maintainers to upload a fix.
(ii) Do an NMU for Qt, despite the fact that this bug is not release-critical.
(iii) Resort to the technical committee.
(iv) Keep the
Bah, the Technical Committee takes months, sometimes over a year, to do
something even as seemingly uncontroversial as voting in opposition to
whichever solution Branden Robinson proposes.
So? This is more than enough time. This problem is to be fixed in sarge ...
Hmm? Are you saying
My suggestion: Add a Recommends: libqt3-compat-headers to libqt3-dev.
This is indeed what I would add were I to do an NMU, and I would
include it in the list of solutions that I see as satisfactory were I to
put it to the TC.
b.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 13 July 2003 06:32, Steve Langasek [EMAIL PROTECTED]
wrote:
On Sun, Jul 13, 2003 at 12:14:52AM -0500, Branden Robinson wrote:
To punt this to the Technical Committee is to stall a solution for
potentially a very long time.
If
On Sun, Jul 13, 2003 at 09:08:03PM +1000, Ben Burton wrote:
Bah, the Technical Committee takes months, sometimes over a year, to do
something even as seemingly uncontroversial as voting in opposition to
whichever solution Branden Robinson proposes.
So? This is more than enough time.
Sebastian Rittau [EMAIL PROTECTED] writes:
On Sun, Jul 13, 2003 at 01:51:07PM +1000, Ben Burton wrote:
It seems then that our options are as follows.
(i) Wait for the Qt maintainers to upload a fix.
(ii) Do an NMU for Qt, despite the fact that this bug is not
release-critical.
(iii)
AT == Anthony Towns aj@azure.humbug.org.au writes:
BB Hmm? Are you saying that sarge is definitively well over a
BB year away?
AT If he is, he's wrong.
Hubris! Famous last words! The pride what cometh before a fall!
~ESP
--
Evan Prodromou
[EMAIL PROTECTED]
On Sun, Jul 13, 2003 at 11:44:38AM -0400, Evan Prodromou wrote:
AT == Anthony Towns aj@azure.humbug.org.au writes:
BB Hmm? Are you saying that sarge is definitively well over a
BB year away?
AT If he is, he's wrong.
Hubris! Famous last words! The pride what cometh before a fall!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi ho, it's time for another rant from me regarding the libqt3-compat-headers
split. This time my ex-housemate has been hit by the problem: she's just
started working with Qt, and lo and behold she received a missing header
compile error. She
16 matches
Mail list logo
