Re: [Cooker] PLEASE address build/install problems
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 it. 4057 is different, in that the ISO images are built without error, but either stuff is missing or the dependencies are screwed, because the install hangs or loops at looking for available packages. I have re-tried this every day or every other day since you fixed the first bug. Ah yes, this is a fpons bug, I do not think he has fix it yet. -- Warly
Re: [Cooker] PLEASE address build/install problems
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 4057, burning ISOs stopped working as well, and a previous comment in this list drew a response that indicates that at least one other person is having the same problem with MakeCD. Yes and I replied that I tried to fix it. Have you tried again? -- Warly
Re: [Cooker] PLEASE address build/install problems
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 images are built without error, but either stuff is missing or the dependencies are screwed, because the install hangs or loops at looking for available packages. I have re-tried this every day or every other day since you fixed the first bug. Thanks, Frank
Re: [Cooker] PLEASE address build/install problems
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 bugzilla asks me every month). I fully understand that it is the nature of cooker than things break. But some things are more critical to the intended goals of cooker than others. If you want people to test a system install, the install has to work at least to the point of completing and producing a bootable system. Have I got this backwards ? Is it really the intention to address only application package issues in the early part of the release cycle, and leave install issues until the betas/RCs ?
Re: [Cooker] PLEASE address build/install problems
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 sentiment and your desire, the folks in charge are (basically) not going to worrry about this issue until sometime shortly before a release of some sort. Bob Finch On Wednesday 02 July 2003 07:26 am, Frank Griffin wrote: 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 bugzilla asks me every month). I fully understand that it is the nature of cooker than things break. But some things are more critical to the intended goals of cooker than others. If you want people to test a system install, the install has to work at least to the point of completing and producing a bootable system. Have I got this backwards ? Is it really the intention to address only application package issues in the early part of the release cycle, and leave install issues until the betas/RCs ?
Re: [Cooker] PLEASE address build/install problems
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 here.) So, while I agree fully with your sentiment and your desire, the folks in charge are (basically) not going to worrry about this issue until sometime shortly before a release of some sort. Bob Finch 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 ... Stef signature.asc Description: PGP signature
Re: [Cooker] PLEASE address build/install problems
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 developpement. I remind you that cooker is not for daily use, that upgrading to cooker is much easier than burning a cd, and, everything will be fine before the release. -- Michaël Scherer
Re: [Cooker] PLEASE address build/install problems
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 distibution always installable would only slowdown the developpement. I remind you that cooker is not for daily use, that upgrading to cooker is much easier than burning a cd, and, everything will be fine before the release. I agree, but i was talking about an external program that can be development-independent, like this, it will always work ;-)) I remember when testing latest two releases during the beta procedures, there was sometimes 2/3 weeks between next release, so in that cas, i was hardly able to follow bugfixing process since i don't have dsl home. I was trying to burn CD sets from there, but even during that period, mkcd was from time to time broken. BTW, it is just a suggestion, because for now for example, one could have a snaphost of cooker, just to try to improve visual aspects of Mandrake and not in the rushing time of betas and rcs releases. BTW(2) : i'm just asking, but have no idea how to implement it ... Stef -- Teletchéa Stéphane [EMAIL PROTECTED] signature.asc Description: PGP signature
[Cooker] PLEASE address build/install problems
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, and a previous comment in this list drew a response that indicates that at least one other person is having the same problem with MakeCD. There's been a lot of traffic on this list about telling people that they'd better report certain problems by a certain point in the development cycle if they want to see the bug addressed in the final release. That's quite reasonable, but it falls apart if the build/install process itself is broken and just stays that way. I entered bug 3295 on March 14 (hd/network installs giving package errors that ISO installs from ISOs burned from the exact same directories do NOT give), and nobody's commented on it but me. After finding bug 4057 (installs from ISOs hang at looking for available packages), I no longer have any way to build or install a Cooker system. This bug showed up sometime between the beginning of June and mid-June. There was another mkcd bug which Warly addressed around mid-June that had made it impossible to build ISO images at all from about June 3 to June 12, so I can't tell when in that timeframe bug 4057 surfaced. I would very much like to continue testing Cooker for you, and I realize that you are short-staffed. If I had never gotten a build to work, I could understand a certain amount of skepticism about bug reports saying my cooker won't work. But that's not the case here. If I can build/burn ISOs which install without problems, yet the exact same directories won't install without problems if I do an hd or network install, then I don't think the problem is in the directories. Likewise, if I have been building/installing burned ISO systems all along, and they suddenly stop installing when I haven't changed my mirroring code, AND someone else is seeing the same problem, the problem isn't in my copy of Cooker. Recent posts to this list indicate that we're coming close to a beta milepost for 9.2, and it is really annoying to not be able to test anything, since I will no doubt hear later on that I should have reported that bug back in whenever. Please take a look at these bug reports and provide some feedback.
Re: [Cooker] PLEASE address build/install problems
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 installed Cooker from network source quite often and it's never caused any trouble. Having said that, the most trouble-free way to install Cooker is generally to install the previous stable release, define Cooker sources, and urpmi --auto-select to get to current Cooker. Since Cooker is by definition unstable, installation can never be guaranteed to work, so it's better to work from a stable base. -- adamw
Re: [Cooker] PLEASE address build/install problems
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 am, Adam Williamson wrote: 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 installed Cooker from network source quite often and it's never caused any trouble. Having said that, the most trouble-free way to install Cooker is generally to install the previous stable release, define Cooker sources, and urpmi --auto-select to get to current Cooker. Since Cooker is by definition unstable, installation can never be guaranteed to work, so it's better to work from a stable base.
Re: [Cooker] PLEASE address build/install problems
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.) That was basically the point, but he was complaining about the install process more generally, and I was just pointing out that it's not something you should expect to be able to rely on. It's been specifically stated that mkcd etc can be broken between releases and no-one will go out of their way to fix them until they're needed to build the beta and release images. -- adamw
