When I looked yesterday on the main indi page, it hadn't been updated to reflect the release of 0.6.1. Just removing the Pardus package and doing a configure-make-install process would force the removal of kdeedu (kstars).

I'll try to modify the pspec.xml for the new release -- that should be a bit easier than messing with svn or snapshot builds.

I have a need to build a package for the latest SVN of indilib (an astronomical telescope control library) because of a bug in the driver for my telescope in the current release, that is supposed to be fixed in the upcoming version.

I think most of what I need to do is reasonably clear, but I'm not sure whether it's possible to directly specify an SVN download in the <Archive> tag of pspec.xml, (an alternative is to use the daily(?) development tarball.).

The Archive tag in the current pspec.xml is:

The url of the snapshot is:

The svn checkout is:

What do I need to put into the Archive tag?

When I connect to a network from my Pardus machine, it does not appear to pick up the domain name, though the network recognizes the system as belonging to it (e.g. it allows me to connect to machines that can only be accessed from inside the network). I do not see the same issue with Kubuntu.

For example:
works in Kubuntu but not Pardus, while:

works with either.

Is this:
a) A design feature
b) A configuration error, or
c) a bug?

 If (c) then do you have any suggestions which package to file against?

As the development version of gimp is getting a significant amount of attention, I thought it would be worth giving a quick rundown of what's needed.

First a few caveats:

1) The 2.7.0 tarball on ftp.gimp.org is too old to include many of the interesting things like the single window mode, so don't bother with it.

2) This was done on a box running 2009-testing so it is possible that there may be (different) version issues, with 2009.1.

3) gimp 2.7 is in development, things may be broken, it's not a good idea to rely on it as your only graphics editor.


Step 1: Ensure that you have a development environment installed (and I may have missed a few things here, if you find such please add them as replies, but everything not explicitly listed as needing to be built is in either the main or the contrib repositories):

Step 2: Remove your current gimp installation (you can restore it later)
Keep a note of all the dependencies that were also removed.
N.B. It may be possible to avoid this step but the configure scripts got confused about babl & gegl versions until I did it.

Step 3: Get the sources you need:
The current tarballs for babl & gegl on ftp.gimp.org work as of this posting, so download those & unpack them.
For the gimp itself you need the latest git version. To download this use:

Step 4: Make sure pkg-config will be able to find the libraries etc:

Step 5: Build babl:

Step 6: Build gegl (same formula in the gegl directory)

Step 7: Build gimp:
The executable is /usr/local/bin/gimp-2.7

Step 8 (optional): Add gimp-data-extras.
At least with the 2009-testing version you will need to edit autogen.sh as it doesn't know about automake 1.11, the quick & dirty way is just to replace "automake-1.10" with "automake-1.11" everywhere it occurs.

Step 9: Restore the distribution gimp (optional)
Where the ellipsis represents anything else that was removed in step 2 and is not a dependency of gimp (e.g. extra plugins, translations etc.)

It is always possible that at some stage the git versions of babl & gegl may be needed.

At what stage does it say that? When you try to play back the files you've written on the CD? If so, can you play them in the original directory where you downloaded them?

Finally got around to building it. The main dependencies you need are (I'm not sure which are part of a default install as most were installed on my machine):

The last of these was the only one I didn't have installed and it was a bit confusing as it's really a dependency of libgnomeui so the configure script kept reporting that libgnomeui was not installed -- I've reported the missing dependency on the Pardus Bugzilla system.

Has anybody ever tried to  build gwc on a Pardus system? This is a tool I use in the cleaning up of 78rpm recordings and one of the things that ties my main box to Kubuntu.

If you have please share your thoughts problems here. If not I'll give it a go on my Pardus machine, using the postings I can find here about gnome as a guide.

Thanks.

I was meaning -- will the 3D capabilities be enabled in future releases?

http://www.happyassassin.net/2010/02/12/from-the-freaking-awesome-department-3d-support-on-nouveau/ reports on 3D support on Nouveau in Fedora.

Are we likely to see it in the 2009.2 or 2010 versions of Pardus? (For me that would be great as one of my Pardus machines has a  Graphics Card / Monitor combination that only works in Nouveau).

Thanks, I thought I had to be missing something obvious.

I'm sure I must be missing something obvious but I can't find an option to pisi to list the files in an installed package [i.e. like dpkg -L on Debian-based systems] (or in a .pisi file). Since pisi can remove packages, it must have a list of files somewhere but I don't see a way to print that list.

If there really isn't such an option, then I'll put in a wishlist bug report.

The lock-up on boot issue should now be resolved.

After bouncing a series of tests back & forth with the developers, the problem was isolated to the Athlon XP series CPU and they were able to find a fix to the kernel in time for the release.

This sounds very similar to the problem discussed in a number of the comments on this thread:
http://worldforum.pardus-linux.nl/index.php?topic=3129.0. You might want to compare your hardware with those comments.

Mine's 2800XP & Nvidia 5200 -- I've added a comment to the bug report.