Re: Building from GIT source & tde-packaging - tde-devels

Timothy Pearson

6 Aug 6 Aug

2:47 p.m.

New subject: [trinity-devel] Re: Building from GIT source & tde-packaging

Michele Calgaro <michele.calgaro@...> writes:

Hi there, after several months, I have started to rebuild TDE from the current GIT sources on Debian/Testing, but I have soon noticed that the "tde-packaging" repository is not up to date with the "tde" repository. Namely, when trying to build "tdelibs" I run into a broken dependency for "libart-2.0-dev" version >=14.0.0. The current files in the "tde-packaging" repository for "libart" builds to a version which is 2.3.22. I double-checked the nightly builds on the web site, and I saw that the correct package (version 14.0.0) is created. So my questions are: 1) is there a date already scheduled for an update of the "tde-packaging" repository, and if so when 2) otherwise, is there any other place where I can find the updated packaging files (other than download the .dsc and .tar.xz file for each package from the nightly build website and then extract the packaging scripts)? Thanks Michele

Hi there, a few days have gone by since my original post, so I think it should be ok to ask again. Is there any place where I can find the updated packaging files for building TDE for Debian/Jessie, other than extracting those from each package in the nightly build website? Thanks again Michele

Yep, sorry about the delay in response. All of the packaging files are in GIT at http://git.trinitydesktop.org/cgit/tde-packaging/tree/ The autobuild system uses the files in that repository, so you should have no problems doing the same. Tim

Reply

Michele Calgaro

7 Aug 7 Aug

7:02 a.m.

New subject: [Bulk] Re: [trinity-devel] Re: Building from GIT source & tde-packaging

-----Original Message----- From: Slávek Banko [mailto:slavek.banko@axis.cz] Sent: Wednesday, August 07, 2013 2:45 AM To: trinity-devel(a)lists.pearsoncomputing.net Subject: [Bulk] Re: [trinity-devel] Re: Building from GIT source & tde-packaging Dne út 6. srpna 2013 Timothy Pearson napsal(a):

...

Michele Calgaro <michele.calgaro@...> writes: > Hi there, > after several months, I have started to rebuild TDE from the > current GIT sources on Debian/Testing, but I have soon noticed that > the "tde-packaging" > repository is not up to date with the "tde" repository. > Namely, when trying to build "tdelibs" I run into a broken > dependency for "libart-2.0-dev" version >=14.0.0. The current files > in the "tde-packaging" > repository for "libart" builds to a version which is 2.3.22. > .....

Yep, sorry about the delay in response. All of the packaging files are in GIT at http://git.trinitydesktop.org/cgit/tde-packaging/tree/ The autobuild system uses the files in that repository, so you should have no problems doing the same. Tim

...

Here I have to add: scripts that Tim and I use to generate deb packages in

the package changelog automatically adds >the newest record with current version of git build.

...

For example, in my script to generate a deb packages I use script

create_tarball, resulting tarball are used as "orig" >for the deb package (I use quilt format) and version from tarball is used as base for the version of the package.

...

Slavek

Hi Tim, Darrell, Slavek, thanks all for your feedback. Slavek's comments explain the problem I was facing. I am using the sources from the GIT repository for TDE and TDE-packaging. In December/January 2013 (the last time I had enough time to build TDE) I had no major problems building TDE. Last week when I tried again, I run into this dependency problem and after checking with the nightly build website I found the differences in the package version number I mentioned in my first message. So as Slavek said, the scripts used to generate the .deb packages automatically add the new version number and that's why the nightly build tarball builds to a 14.0.0 version instead of 2.3.22. So I will just have to do the same. -- Unless I am doing something wrong or missing something in the building process (which could well be the case :) )--, IMO the TDE-packaging and TDE GIT repository should be synchronized, by either updating the package build scripts or by adding the scripts that are used by the autobuild system. At the moment if a Debian user tries to build TDE package-by-package from the GIT repository using the current TDE-packaging GIT repository, he/she will run into dependency problems like the one I mentioned. Cheers Michele

Reply

Michele Calgaro

23 Aug 23 Aug

7:30 a.m.

New subject: [trinity-devel] RE: [Bulk] Re: [trinity-devel] Re: Building from GIT source & tde-packaging

...

Hi Tim, Darrell, Slavek, thanks all for your feedback. Slavek's comments explain the problem I was facing. I am using the sources from the GIT repository for TDE and TDE-packaging. In December/January 2013 (the last time I had enough time to build TDE) I had no major problems building TDE. Last week when I tried again, I run into this dependency problem and after checking with the nightly build website I found the differences in the package version number I mentioned in my first message. So as Slavek said, the scripts used to generate the .deb packages automatically add the new version number and that's why the nightly build tarball builds to a 14.0.0 version instead of 2.3.22. So I will just have to do the same. -- Unless I am doing something wrong or missing something in the building process (which could well be the case :) )--, IMO the TDE-packaging and TDE GIT repository should be synchronized, by either updating the package build scripts or by adding the scripts that are used by the autobuild system. At the moment if a Debian user tries to build TDE package-by-package from the GIT repository using the current TDE-packaging GIT repository, he/she will run into dependency problems like the one I mentioned. Cheers Michele

Constantly updated versions in tde-packaging to me does not seem like a good idea. Not only would it generate a lot of unnecessary changes, but also would not guarantee that the version actually corresponds to the current state of appropriate git module. Sense might have if version will be updated at the time of release of the new final version => be labeled using git tag. However, this does not solve your trouble. What could you help if I gave you my script for generating source deb packages... Slavek

Hi Slavek, thanks for coming back on this. I agree with you that changing the version number in tde-packaging every time is not a good idea and also very time consuming. Much better using a script that automatically updates the version number at building time, as you and Tim do. I also have my own set of scripts to build TDE and I just had to add a "dch" line to get every package to the same version number. Anyhow IMO we should also make sure that there are no broken dependencies between tde and tde-packaging git repositories, because if someone tries to build TDE from git without updating the package version, at the moment he would run into broken dependencies (at least in Debian testing). tdelibs requiring libart version >=14.0.0 is one example, and there may be more. One way to do that is to review the dependencies of each package one by one, but perhaps a wiser idea would be to include the scripts used by the autobuilder farm into the tde-packaging repository. By the way, the "How to build TDE" web page (http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild) is full of nice information, but it strikes me that there is no mentioning of the tde-packaging repository. It would be worth adding a couple of lines at the top of the page that says something like "Hey guys, most of the scripts you need can be found in the tde-packaging git repository. Check them out" I think this would encourage more people to help the development of TDE. Cheers Michele

Reply