Frank Griffin [EMAIL PROTECTED] writes:
Warly wrote:
Yes and I replied that I tried to fix it.
Have you tried again?
The bug you replied about was a different one, where MakeCD would
immediately error out without creating images. That one was fixed,
and I closed the Bugzilla report for
Frank Griffin [EMAIL PROTECTED] writes:
I've been building and testing cooker systems for over a year,
primarily by creating ISOs with MakeCD and burning them. I've tried
harddrive and network installs, but they don't work for me (as
documented in bug 3295).
Recently, as documented in bug
Warly wrote:
Yes and I replied that I tried to fix it.
Have you tried again?
The bug you replied about was a different one, where MakeCD would
immediately error out without creating images. That one was fixed, and
I closed the Bugzilla report for it.
4057 is different, in that the ISO
Thanks, I'll make a note of the urpmi --auto-select technique, but most
of the bugs I report are with the install itself, not just with this
package or that. Without being able to do an install, those aren't
going to get reported, and I can't tell if the old ones have been fixed
(when
I think you have a valid point. However, it has been answered before that a
working mkcd between releases is not a priority. In fact it appears to be a
distraction to keep it working. (This last sentence is my interpretation of
what I have read here.)
So, while I agree fully with your
Le mer 02/07/2003 à 18:21, w9ya a écrit :
I think you have a valid point. However, it has been answered before that a
working mkcd between releases is not a priority. In fact it appears to be a
distraction to keep it working. (This last sentence is my interpretation of
what I have read
That's why i've asked long time ago if it was possible to have a kind
of binary mkcd that would always work, but nobody considered this as
a cool feature at that time ...
the problem wih mkcd is a dependancy one, IIRC.
So, keeping the distibution always installable would only slowdown the
Le mer 02/07/2003 à 20:36, Michael Scherer a écrit :
That's why i've asked long time ago if it was possible to have a kind
of binary mkcd that would always work, but nobody considered this as
a cool feature at that time ...
the problem wih mkcd is a dependancy one, IIRC.
So, keeping the
I've been building and testing cooker systems for over a year, primarily
by creating ISOs with MakeCD and burning them. I've tried harddrive and
network installs, but they don't work for me (as documented in bug 3295).
Recently, as documented in bug 4057, burning ISOs stopped working as
well,
On Tue, 2003-07-01 at 01:18, Frank Griffin wrote:
I've been building and testing cooker systems for over a year, primarily
by creating ISOs with MakeCD and burning them. I've tried harddrive and
network installs, but they don't work for me (as documented in bug 3295).
*snippety*
I've
I *think* the original point was that mkcd wasn't happening for him anymore,
and he wanted to make sure that it got fixed before the next release. I don;t
think was having any issues about running cooker per se. (But I *might*have
missed something.)
Bob Finch
On Tuesday 01 July 2003 07:55
On Tue, 2003-07-01 at 18:54, w9ya wrote:
I *think* the original point was that mkcd wasn't happening for him anymore,
and he wanted to make sure that it got fixed before the next release. I don;t
think was having any issues about running cooker per se. (But I *might*have
missed something.)
12 matches
Mail list logo
