Problem with KDevelop rpm packaging
Amilcar do Carmo Lucas
amilcar at ida.ing.tu-bs.de
Mon Nov 24 09:13:38 UTC 2008
On Monday 24 November 2008 04:28:00 you wrote:
> Hi
>
> I have bumped in to an rpm packaging problem with Kdevelop. I
> downloaded and installed Kdevelop 3.5.3-4.1 rpm from the openSUSE site on
> RHEL 5.1 without any issues. I then tried to remaster the RHEL 5 DVD with
> this new rpm file. But the installer failed with the python script failing
> on maximum recursion depth reached. The debug messages tagged kdevelop as
> the problematic package. Googling a bit, I learnt that the problem occurs
> when a package obsoletes itself.
>
> After downloading the source rpm from the same site, I checked the spec
> file and found that the package indeed obsoletes 'kdevelop'. Is this OK?
>
> From the spec file:
> Provides: kdevelop
> Obsoletes: kdevelop
> Obsoletes: gideon
> Obsoletes: kdevelop2
>
> Is it normal for something to obsolete the very thing it provides?
I'm not sure. Can you point me to the place that explains why it is not OK to
do that ?
> I'm yet
> to remove that obsoleting and re-build. Will try that today.
>
> One more doubt, in the spec file, there are constants:
> %define branch_source_date 20081101
> %define kdevelop_version 3.5.3
> %define kde_version 3.4.0
> %define qt_version 3.3.2
>
> Do I need to modify any of these to reflect the versions on my system?
No. You should not change those constants.
--
Eng. Amilcar do Carmo Lucas
Institut fuer Datentechnik und Kommunikationsnetze
Technische Universitaet Braunschweig
Hans-Sommer-Str. 66, D-38106 Braunschweig, Germany
Tel: +49 (0)531 391 3751, Fax: +49 (0)531 391 3750
http://www.ida.ing.tu-bs.de/~amilcar
More information about the KDevelop-devel
mailing list