binary vs "real debian" packages
I've built a few debian "binary" style packages [1] but the maintainer of my local repository is asking that I have all the "proper" debian files, like the .dsc, .orig, .diff, .changes, etc so some how he can sleep better at night or something. He likes dupload for putting packages into the repo and that requires a .changes my contents are not source (configure, make, etc), rather I'm more interested in the preinst/postinst scripts, the Depends part of the control file, a few config files and placing a few scripts on the filesystem that require no compiling. All the howto info that I've found so far is aimed at making "proper" debian packages from source which means working with dh_make and checkinstall, etc which I don't thnk I need here. At least, I don't think that I need checkinstall as there is no "make install" command to run. Further, I understand the concept of an upstream provider and understand that I don't have one in this case, unless I sort of fake it somehow. Is that wise or is there a well understood method of having an .orig file and then doing stuff to make your .dsc, .diff and .changes files? What would the contents of an orig file like that look like in my case where it's not a source package? thank you! Will [1] http://tldp.org/HOWTO/Debian-Binary-Package-Building-HOWTO/x88.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
custom package dependencies not installing
I have a binary style package that I've created. The control file has a large number of Depends entries in it which all install fine by themselves. When I attempt to install the package (via dpkg -i) , it lists all of the Depends and it helpfully tells me that they are not installed (which is true) like so and just returns me to a prompt: ash036:/tmp# dpkg -i -webserver-apps-0.0.1-10.deb Selecting previously deselected package -webserver-apps. (Reading database ... 18443 files and directories currently installed.) Unpacking -webserver-apps (from -webserver-apps-0.0.1-10.deb) ... dpkg: dependency problems prevent configuration of -webserver-apps: -webserver-apps depends on php-date (>= 1.4.7); however: Package php-date is not installed. -webserver-apps depends on php-file-mogile (>= 0.0.2); however: Package php-file-mogile is not installed. dpkg: error processing -webserver-apps (--install): dependency problems - leaving unconfigured Errors were encountered while processing: -webserver-apps however, if I immediately follow this up with apt-get -f install all dependencies (in my repo) and the original .deb file (it's not yet in my repo) install just fine and everything works. No packages report any errors at all. I admit this is my first custom .deb project but I think I've done everything correctly but I must be missing something that's causing the missing dependencies to install? thanks, Will -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
avoid conf file overwrite message?
I have a package that I made which does a dpkg-divert in the 'preinst' on a couple of config files and then installs replacements from them. However, even though the dpkg-divert has run (and I've verified it does move it to the name I specify), I still get a message that looks like this: (this is similar to mine but not exact, I just grabbed it from the net as I don't have mine handy) Configuration file `/etc/twiki/apache.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : background this process to examine the situation The default action is to keep your current version. *** apache.conf (Y/I/N/O/D/Z) [default=N] ? Y Installing new version of config file /etc/twiki/apache.conf ... Is there a way (short of piping in /usr/bin/yes or something similar) to make that go away? Eventually I'll use something like puppet to manage these files but for now this happens to be the easiest way. If I do answer 'Y' it does indeed do what I want. thanks, Will -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
control file Replaces: question
I want to manage the config files for several other packages centrally in one package that I'm going to maintain. According to the package maintainers guide, section 7.5.1 [1] , this is entirely possible and perfectly reasonable via the Replaces: option in the control file. My question is, how do I use the Replaces: option to take ownership of just one file and not have it delete the entire package? Also, can I make my config package Depend: on the package that I'm going to replace the config file of, or does it need to be installed first for this to work? thanks, Will [1] http://www.debian.org/doc/debian-policy/ch-relationships.html#s7.5.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
