Re: Adpkg (was Re: How to trick debian into thinking a package is installed)
Thanks, Craig - > "Craig" == Craig Sanders <[EMAIL PROTECTED]> writes: Craig> if you install dpgk again before removing adpkg, nothing will Craig> break: Craig> dpkg -i dpkg_1.4.0.8.deb dpkg -r --force-remove-essential Craig> adpkg Craig> I've successfully removed adpkg from at least a dozen systems Craig> like this. That's very good to know, will do. Craig> I used adpkg for a while - i really like the way it's dselect Craig> scans the binary directories first and builds a list of Craig> packages to install, and i also like the way it configures Craig> packages immediately. Unfortunately, it needs some dependancy Craig> ordering so that it doesn't try configuring a package before Craig> all packages it depends on are configured - which leads to Craig> having to run Install about a million times and also manually Craig> install some packages. There are other problems with adpkg as Craig> well. I hadn't been aware of that stuff; it's interesting. (I wasn't sure what, if, or how much adpkg was doing for the standard dpkg & dselect commands. Adpkg says it replaces & provides dpkg, but dpkg's files are still listed in dpkg.list, and its status is 'installed'; I haven't know what to consider whose.) Is there a doc source you know about, or is that from the source or debian-devel, or general smarts? :-) Maybe I could bone up on adpkg before I remove it. Craig> adpkg shows a lot of promise, but it needs more work. (Not just for Craig; he's helped enough :) Is there still work being done on adpkg, or are the ideas being moved into the deity project or some such? Well, I'm chattering a bit, those are just browsing-level interest questions, I know what I need to know practically now. Thanks again, Craig, Ed -- Ed Donovan [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Adpkg (was Re: How to trick debian into thinking a package is installed)
On 12 May 1997, Ed Donovan wrote: > While the topic is raised--I installed adpkg a while ago, mistakenly > thinking it could come out cleanly if I wanted to remove it. I haven't > used deb2asc or asc2deb yet, and don't think I'm using anything else > provided by adpkg. I'd like to remove it for now, but as an 'Essential' > package dpkg/dselect doesn't want to let it go. I could > force-remove-essential it, but with it being tied so closely to dpkg, I > haven't wanted to risk that going wrong (not fully confident in my > prediction of dpkg's actions). Or I could purge it out manually. I > like to leave my dpkg and debian installation as clean and > uninterfered-with as possible, so I'm curious to hear what the group > knows before trying anything more. if you install dpgk again before removing adpkg, nothing will break: dpkg -i dpkg_1.4.0.8.deb dpkg -r --force-remove-essential adpkg I've successfully removed adpkg from at least a dozen systems like this. I used adpkg for a while - i really like the way it's dselect scans the binary directories first and builds a list of packages to install, and i also like the way it configures packages immediately. Unfortunately, it needs some dependancy ordering so that it doesn't try configuring a package before all packages it depends on are configured - which leads to having to run Install about a million times and also manually install some packages. There are other problems with adpkg as well. adpkg shows a lot of promise, but it needs more work. craig -- craig sanders networking consultant Available for casual or contract temporary autonomous zone system administration tasks. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Adpkg (was Re: How to trick debian into thinking a package is installed)
> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes: Christoph> Those tools are in the adpkg package... But that package Christoph> also has an experimental version of dpkg in it. I will Christoph> put it back somehow. If you have access to an earlier Christoph> version of adpkg then get that. Hi - While the topic is raised--I installed adpkg a while ago, mistakenly thinking it could come out cleanly if I wanted to remove it. I haven't used deb2asc or asc2deb yet, and don't think I'm using anything else provided by adpkg. I'd like to remove it for now, but as an 'Essential' package dpkg/dselect doesn't want to let it go. I could force-remove-essential it, but with it being tied so closely to dpkg, I haven't wanted to risk that going wrong (not fully confident in my prediction of dpkg's actions). Or I could purge it out manually. I like to leave my dpkg and debian installation as clean and uninterfered-with as possible, so I'm curious to hear what the group knows before trying anything more. Thanks all, Ed Donovan [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to trick debian into thinking a package is installed
Those tools are in the adpkg package... But that package also has an experimental version of dpkg in it. I will put it back somehow. If you have access to an earlier version of adpkg then get that. On Sat, 10 May 1997, Igor Grobman wrote: >There used to exist 2 utilities called deb2asc and asc2deb which were very >useful for this kind of thing. They were part of debmake at one time then were >moved to adpkg, and after adpkg's removal from distribution seem to have >disappeared. > >Christoph, >would you put them back into debmake or anywhere else for that matter? These >utilities are truly useful for creating dummy packages. > >With those utilities available, you would just need to create a text file >containing something like this: > >%control >Package: dummy >Version: 1.0 >Provides: motif, tetex > >(and some more standard control file lines) > >Then you run asc2deb, and a .deb package is built. > >On May 9, Steve Hsieh wrote >> >> >> Hi, >> >> Can someone tell me how I can trick debian into thinking that a package is >> installed? Specifically, I have the real motif installed on my system. >> However, since this is (obviously) not a debian package, debian has no >> idea that I have it. And so if I try to install the xmcd package, it >> refuses to install because lesstif isn't installed, but I can't install >> lesstif without overwriting the real motif... I guess I could also use >> the --force-depends option in dpkg to force an install? >> >> So my questions are; >> >> 1. what's the dirty way to modify the config files so debian thinks >> lesstif is installed? >> >> 2. if I create my own binary .deb package with my motif binaries inside >> it, how do I change the control file so it "provides" lesstif? >> >> On a side note, motif apps really ought to "require" a motif package, and >> lesstiff should "provide" motif, as opposed to packages directly requiring >> lesstif. >> >> Steve >> >> >> >> -- >> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to >> [EMAIL PROTECTED] . >> Trouble? e-mail to [EMAIL PROTECTED] . >> > >-- >Proudly running Debian Linux! Linux vs. Windows is a no-Win situation >Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED] > > --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to trick debian into thinking a package is installed
There used to exist 2 utilities called deb2asc and asc2deb which were very useful for this kind of thing. They were part of debmake at one time then were moved to adpkg, and after adpkg's removal from distribution seem to have disappeared. Christoph, would you put them back into debmake or anywhere else for that matter? These utilities are truly useful for creating dummy packages. With those utilities available, you would just need to create a text file containing something like this: %control Package: dummy Version: 1.0 Provides: motif, tetex (and some more standard control file lines) Then you run asc2deb, and a .deb package is built. On May 9, Steve Hsieh wrote > > > Hi, > > Can someone tell me how I can trick debian into thinking that a package is > installed? Specifically, I have the real motif installed on my system. > However, since this is (obviously) not a debian package, debian has no > idea that I have it. And so if I try to install the xmcd package, it > refuses to install because lesstif isn't installed, but I can't install > lesstif without overwriting the real motif... I guess I could also use > the --force-depends option in dpkg to force an install? > > So my questions are; > > 1. what's the dirty way to modify the config files so debian thinks > lesstif is installed? > > 2. if I create my own binary .deb package with my motif binaries inside > it, how do I change the control file so it "provides" lesstif? > > On a side note, motif apps really ought to "require" a motif package, and > lesstiff should "provide" motif, as opposed to packages directly requiring > lesstif. > > Steve > > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . > Trouble? e-mail to [EMAIL PROTECTED] . > -- Proudly running Debian Linux! Linux vs. Windows is a no-Win situation Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to trick debian into thinking a package is installed
I remember reading, maybe on the lesstif web site, that lesstif now uses different lib naming conventions so it can co-exist with motif. On Sat, 10 May 1997, Maarten Boekhold wrote: > > 1. what's the dirty way to modify the config files so debian thinks > > lesstif is installed? > > I don't think that this will work. lesstif isn't binary compatible with > motif AFAIK, only source-level. So to use programs linked against lesstif, > you will need lesstif, and not motif (ofcourse you could recompile > yourself...). > > If this is not correct, by all means say so. I don't use any of > motif/lesstif myself :) > > > On a side note, motif apps really ought to "require" a motif package, and > > lesstiff should "provide" motif, as opposed to packages directly requiring > > lesstif. > > Maarten > > _ > | Maarten Boekhold, Faculty of Electrical Engineering TU Delft, NL| > |[EMAIL PROTECTED] [EMAIL PROTECTED] | > - > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . > Trouble? e-mail to [EMAIL PROTECTED] . > --Rick [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to trick debian into thinking a package is installed
> 1. what's the dirty way to modify the config files so debian thinks > lesstif is installed? I don't think that this will work. lesstif isn't binary compatible with motif AFAIK, only source-level. So to use programs linked against lesstif, you will need lesstif, and not motif (ofcourse you could recompile yourself...). If this is not correct, by all means say so. I don't use any of motif/lesstif myself :) > On a side note, motif apps really ought to "require" a motif package, and > lesstiff should "provide" motif, as opposed to packages directly requiring > lesstif. Maarten _ | Maarten Boekhold, Faculty of Electrical Engineering TU Delft, NL| |[EMAIL PROTECTED] [EMAIL PROTECTED] | - -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to trick debian into thinking a package is installed
On Fri, 9 May 1997, Steve Hsieh wrote: > Can someone tell me how I can trick debian into thinking that a > package is installed? > Get hold of the unofficial package "equivs-1.0.deb-unoff.src.tar.gz" from "http://www.uni-mainz.de/~pseelig/debian.html"; and have a look at it. This is a small hack i have been trying to fool "dpkg" in believing that certain packages are already installed by simply editing the "Provides:" line of the package's control file. It has some rough edges and needs to be improved a lot but i think this should be done someone who knows such a thing better than i do!? Anybody interested in making it an official Debian package? I made this package because i wanted to install Thomas Esser's LaTeX distribution "teTeX" separately to take advantage of his update shell scripts without worrying about Debian's package management. Not that i don't appreciate Christoph Martin's fine work in making a "teTeX" package for Debian! Only fools (like me obviously) wouldn't want to use his fine packages! ;-) Cheers, P. *8^) -- Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
How to trick debian into thinking a package is installed
Hi, Can someone tell me how I can trick debian into thinking that a package is installed? Specifically, I have the real motif installed on my system. However, since this is (obviously) not a debian package, debian has no idea that I have it. And so if I try to install the xmcd package, it refuses to install because lesstif isn't installed, but I can't install lesstif without overwriting the real motif... I guess I could also use the --force-depends option in dpkg to force an install? So my questions are; 1. what's the dirty way to modify the config files so debian thinks lesstif is installed? 2. if I create my own binary .deb package with my motif binaries inside it, how do I change the control file so it "provides" lesstif? On a side note, motif apps really ought to "require" a motif package, and lesstiff should "provide" motif, as opposed to packages directly requiring lesstif. Steve -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
