reopen 233818 thanks On Fri, Feb 20, 2004 at 07:03:44PM +0100, Mario 'BitKoenig' Holbe wrote: > > You may be able to rectify your problem, however, by using the "equivs" > > Well, the problem is: as long as you Conflict: xlib6g in xlibs, nobody > will be able to install any package that even just Provides: xlib6g. Damn. You're quite right, of course. > That's why the way you suggest just simply does not work. (And yes, I > tried it, I did build my own fake-xlib6g with Provides: xlib6g). > > That was my reason for 233818. > > There is no other chance currently, than repackage any package that > depends on xlib6g currently with modified control file. > > The question is: Since the last xlib6g packages are empty packages > anyways... do you really need to Conflict: it? I'd really like to force them off the system. Would it be so awful to rebuild some of these packages that haven't been updated since potato? -- G. Branden Robinson | Debian GNU/Linux | Yeah, that's what Jesus would do. branden@debian.org | Jesus would bomb Afghanistan. Yeah. http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature