On Mon, Oct 22, 2007 at 02:44:24AM -0700, Steve Langasek wrote: > On Thu, Oct 18, 2007 at 02:45:15PM +0200, Ola Lundqvist wrote: > > > "Not working" is a problem, of course, and is what the cited bug report > > > talks about. > > > Yes that is a problem, on all amd64 arches. > > I guess you mean "all 64-bit arches"? That encompasses alpha and ia64 as > well.
Emm yes. > > > As a first step, let's fix the severity of the bug. This should have been > > > RC all along - amd64 is not our only 64-bit architecture, so if vncserver > > > is > > > not 64-bit-clean, that needs to be dealt with (one way or another) instead > > > of leaving broken binaries in the archive. > > > I agree to some extent, but I'm not fully sure that it should be grave. > > I classified it as important as the problem is only seen on 64 bit arches. > > For several release cycles, the release team has treated the presence of any > unusable binary package in the archive as a release-critical bug. If a Ok. > package is unsupported on a given architecture, it should be a simple matter > to remove the binary from the archive (by fixing the package to not build > it), rather than letting users mirror and install a package that won't work. > > Furthermore, if we leave per-arch-broken binary packages around in the > archive, how do we know for sure that other packages aren't also broken as a > result of depending on them? True. > > > > The same package(s) is(are) included in the stable/etch release. Is it > > > > possible to remove a package after the release? > > > > Yes, though of course fixing the package would be far preferable. > > > I actually think that we should simply remove build for amd64 for this > > package. vnc4 is available. The only problem there is that some development > > libraries will not be available in this case. > > > But removing the entire package is not good at this point (becuase of the > > development packages). > > > So what do you think it the best solution? > > * Remove amd64 build. > > * Remove entire package (it will require some work on vnc4 package to build > > the development libraries). > > * Fix the problem (I need a big patch for that) and I do not think it is > > worth the effort. I do not have access to amd64 machine so I can not > > test it either. > > * Keep as is > > What about removing just the *server* package on the 64-bit archs, if that's > the bit that's broken? I think the client is ok, I believe I've used it > from 64-bit systems. So just changing debian/rules to stop building > vncserver on the 64-bit archs should fix this bug. That is of course a solution. I'll see what I can do about it. I'm not fully sure how I do that in the debian/rules file but it is likely not that hard. Best regards, // Ola > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > [EMAIL PROTECTED] http://www.debian.org/ > > > -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]