On Thursday 17 of March 2016 23:10:28 deloptes wrote: > Sl�vek Banko wrote: > > On Thursday 17 of March 2016 10:43:38 deloptes wrote: > > > > > > Tarballs generated from the git unfortunately are not sufficient because > > they contain submodules - usually admin and cmake. Either you have to > > download and add these submodules, or you can use the "orig.tar.xz" from > > debian / ubuntu repository - for example: > > http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu/pool/ma >in/t/tdelibs-trinity/tdelibs-trinity_14.0.3.orig.tar.xz > > http://mirror.xcer.cz/trinity-sb/pool/main-r14/t/tdelibs-trinity/tdelibs-tr >inity_14.0.4~pre1.orig.tar.xz > > > Hi Slavek, Michele, all, > where do I get the proper debian files? > > http://mirror.git.trinitydesktop.org/cgit/tde-packaging/tree/debian/squeeze >/tdelibs/debian/changelog > > tdelibs-trinity (4:3.5.12-0ubuntu6+r1116280) lucid; urgency=low > > * Automated svn build > deloptes, you took the right file! The trick is (very simplified) as follows: 1) take the source code of module from the git (including submodules) 2) add the appropriate debian folder from the git source tde-packaging 3) into debian/changelog add at the top version of your build and date 4) build your package :) As I mentioned, the procedure is shown greatly simplified. For example: because the packages are created in the format "3.0 (quilt)", you have to prepare tarball "orig.tar.xz" with the corresponding version number. To enable a smooth path for update packages, you need to establish the method of counting the basic version of the packages and in addition counting version of the "packaging" files - including the version of the distribution, for which the package is created. For this reason, Tim, Michele and I have scripts that automate this process. If you were interested in: For preliminary stable builds repository is now from one git module generated 18 source packages - for each version of the distributions. From these source packages is then 49 builds of binary packages - for each platform of each distribution. Establish rules for counting versions is therefore very important step :) If you plan to simply test your upcoming patches on the current version of the package, you can simplify your work as follows: 1) apt-get source _package_ "orig.tar.xz", "debian.tar.xz" and "dsc" will be downloaded and extracted 2) add your desired patches to folder debian/patches and write them to the list debian/patches/series 3) if you wish, enter a higher version number in the debian/changelog 4) build your updated package :) -- Sl�vek