Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change 
notification.

The "DebianMed/HowToGet" page has been changed by TimBooth:
http://wiki.debian.org/DebianMed/HowToGet?action=diff&rev1=7&rev2=8

Comment:
Tested instrux and fixed

  
   #Check the version of the tarball you downloaded and set the version of this 
package appropriately.
   #In this case I had velvet_1.1.05.tgz
+  dch -v 1.1.05-custom1 'Local build of new version'
-  #Note that 'dch' will launch an editor for you to add any comments about the 
build.
-  dch -v 1.1.05-custom1
  
   #See what build dependencies are required and then install them manually
   dpkg-checkbuilddeps
   sudo apt-get install cdbs debhelper zlib1g-dev help2man
   
   #Check patches.  Sometimes, a patch fails and needs to be fixed manually.
+  export QUILT_PATCHES=debian/patches
   quilt push -a   #Try to apply all Debian-specific patches.  If this works, 
skip to next part
   quilt push -f   #There is an error, so force the final patch
   cat *.rej       #Examine conflicts
@@ -91, +91 @@

   sudo dpkg -i ../velvet_1.1.05-custom1_amd64.deb
  }}}
  
- The above is the most direct route to building a fairly simple package for 
your own use, but if you want to get more involved in package building or 
contribute fixes back to Debian Med then it is suggested to read the available 
documentation, and especially the 
[[http://debian-med.alioth.debian.org/docs/policy.html|Debian Med group 
policy]].  This package happens to be in the Subversion repository but the 
package you want may be in Git, and also note that some tools may be part of a 
larger download and will be packaged under that name.  The trickiest bit in the 
above build was that the final patch failed because the small issue it 
addressed had been fixed by the newer upstream but in a slightly different way. 
 Sorting this out it required a little knowledge of the 
[[http://pkg-perl.alioth.debian.org/howto/quilt.html|quilt]] patch system, 
Makefile syntax, and linking to standard shared libraries (libz, libm) in order 
to get a working Makefile.  Quilt was then refreshed to capture the necessary 
modifications as a patch file.  The aim is to get to the point where 'debuild' 
runs successfully as this does all the work to make the DEB, and will complain 
if there are outstanding dependency or patch issues.
+ The above is the most direct route to building a fairly simple package for 
your own use, but if you want to get more involved in package building or 
contribute fixes back to Debian Med then it is suggested to read the available 
documentation, and especially the 
[[http://debian-med.alioth.debian.org/docs/policy.html|Debian Med group 
policy]].  This package happens to be in the Subversion repository but the 
package you want may be in Git, and also note that some tools may be part of a 
larger download and will be packaged under that name.  The trickiest bit in the 
above build was that the final patch failed because the small issue it 
addressed had been fixed by the newer upstream but in a slightly different way. 
 Sorting this out it required a little knowledge of the 
[[http://pkg-perl.alioth.debian.org/howto/quilt.html|quilt]] patch system, 
Makefile syntax, and linking to standard shared libraries (libz, libm) in order 
to get a working Makefile.  Quilt was then refreshed to capture the necessary 
modifications as a patch file.  The aim is to get to the point where 'debuild' 
runs successfully as this does all the work to build the source and make the 
DEB, and will complain if there are outstanding dependency or patch issues.
  
  If you attempt a package build and get compilation failures, even when all 
dependencies are satisfied, then people on the 
[[http://lists.debian.org/debian-med/|Debian Med mailing list]] should be able 
to help.
  

_______________________________________________
debian-med-commit mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-commit

Reply via email to