Ticket #45 (closed Task: fixed)
Make .deb package
Reported by: | JuergeN | Owned by: | silke |
---|---|---|---|
Priority: | Major | Milestone: | |
Component: | DeepaMehta Standard Distribution | Version: | |
Keywords: | Cc: | ||
Complexity: | 3 | Area: | |
Module: |
Description
We want to have a DeepaMehta .deb package at some point. Let's find out what we need to do!
Here is a first results of my research: http://taksmind.org/?p=20
Change History
comment:3 Changed 14 years ago by silke
- Cc silke@… removed
- Owner set to silke
- Status changed from new to accepted
Debian Docs: Packaging Java http://pkg-java.alioth.debian.org/docs/tutorial.html
comment:4 Changed 13 years ago by silke
Just gathering information... Creating a .deb from a .bin or .tgz: http://www.debianhelp.co.uk/debianjava.htm (which we do not have and which is obsolete from debian squeeze on)
http://www.tomprogs.at/tutorials/linux/debian-paket-tutorials-01-ein-erstes-paket.xhtml
http://wiki.debian.org/Java/MavenBuilder
http://mojo.codehaus.org/deb-maven-plugin/using-deb.html (libraries only, but interesting)
comment:5 Changed 13 years ago by silke
Including scripts http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
comment:6 Changed 13 years ago by silke
Created first very basic .deb package with many wrong/non-standard file permissions. What works: Creation of a deepamehta user during installation.
comment:7 Changed 13 years ago by silke
I had a problem to create a pid file in /var/run as deepamehta user. Therefore I changed the init script in the following way:
PIDFILE=/var/run/$NAME/$NAME.pid
and added
mkdir -p /var/run/deepamehta chown -R deepamehta:deepamehta /var/run/deepamehta
in the postinst script.
comment:8 Changed 13 years ago by silke
Experiments with the Snapshot
Execute inside the debian dir:
- dch -i
And in the directory deepamehta-4.0.5:
- rm ../deepamehta_4.0.5.orig.tar.gz
- tar -czf ../deepamehta_4.0.5.orig.tar.gz bin/ init/ apache/
- debuild -S -sa
- dput ppa:sil-ke/deepamehta deepamehta_4.0.5-2ubuntu1_source.changes
comment:9 Changed 13 years ago by silke
Preconfigured file directory /var/lib/deepamehta/deepamehta-filedir
comment:10 Changed 13 years ago by JuergeN
Hi Silke,
congratulations! I just downloaded the package from your PPA website:
https://launchpad.net/~sil-ke/+archive/deepamehta/+build/2849136
using this URL:
https://launchpad.net/~sil-ke/+archive/deepamehta/+build/2849136/+files/deepamehta_4.0.5-2ubuntu1_all.deb
Then I installed it with
dpkg -i ~/Downloads/deepamehta_4.0.5-2ubuntu1_all.deb
The package does exactly what I would expect it to do.
comment:11 Changed 13 years ago by JuergeN
The package did not get published yet. :(
Maybe this has to do with the selected component? (just a guess):
https://launchpad.net/~sil-ke/+archive/deepamehta/+build/2849136
main sounds quite official?! But I could not find any further hints on the net so far ...
comment:12 follow-up: ↓ 15 Changed 13 years ago by silke
Has been published over night! You're right, contrib would sound more adequat. I could now "copy the files" for 10.10, 11.04 and 11.11. They are now awaiting publication.
You'll then be able to install the 4.0.5-SNAPSHOT in Ubuntu running:
sudo add-apt-repository ppa:sil-ke/deepamehta sudo aptitude update sudo aptitude install deepamehta
(Note2self: Uploading the orig.tar.gz with different contents is impossible -> learn the diff stuff!)
comment:13 follow-up: ↓ 17 Changed 13 years ago by silke
Yet another note: Ubuntu is using the upstart system now, I'm still using init...
comment:14 follow-up: ↓ 16 Changed 13 years ago by silke
Config files are still not deleted during deinstallation.
dpkg: Warnung: Während Entfernens von deepamehta ist Verzeichnis »/usr/lib/deepamehta/conf« nicht leer, wird daher nicht gelöscht.
And I still have a strange directory mistake:
/usr/lib/deepamehta/conf /usr/lib/deepamehta/conf/conf
Maybe I ought to symlink single files, not the conf directory...
comment:15 in reply to: ↑ 12 Changed 13 years ago by JuergeN
Replying to silke:
Has been published over night!
Yeah! Now I could add your repo and was able to install your package as described. :)
comment:16 in reply to: ↑ 14 Changed 13 years ago by JuergeN
Replying to silke:
Config files are still not deleted during deinstallation.
I cannot confirm this! Deinstallation works fine on my computer. Please re-ckech that your machine is not messed up some-how. I will try it on my other computers, and report back.
comment:17 in reply to: ↑ 13 Changed 13 years ago by JuergeN
Replying to silke:
Yet another note: Ubuntu is using the upstart system now, I'm still using init...
Upstart is very Ubuntu specific and not used by Debian and other .deb-based distros. On the other hand Ubuntu do still support init. So I would not make any changes to this at the moment until the will be a real need to shift.
comment:18 Changed 13 years ago by JuergeN
How about closing this ticket soon and make new ones for new tasks?
comment:19 Changed 13 years ago by silke
- Status changed from accepted to closed
- Resolution set to fixed
OK! :-)
comment:20 Changed 13 years ago by silke
Create diff:
- keep old orig.tar.gz file
- run debuild -S (not -S -sa which would mean "upload the orig.tar.gz again")
- run dput deepamehta deepamehta_4.0.5-XubuntuX_source.changes
comment:21 Changed 11 years ago by jri
- Milestone Build .deb Package deleted
Milestone Build .deb Package deleted