21 Aug
2013
21 Aug
'13
8:23 p.m.
On Wednesday 07 of August 2013 09:02:51 Michele Calgaro wrote:
-----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):
the package changelog automatically adds >the newest record with current
version of git build.
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
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 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