QGIS - GRASS Repository conflict

[wildintellect]

The current QGIS(launchpad ppa) and GRASS(Jachym) repos will conflict with each other unless we specify and lock specific versions. Note QGIS is also bugged by it's GDAL version, moving to 1.6 is recommended to fix it, but I'm not sure if 1.0.2 is available against it. We might want to just get GRASS and QGIS from UbuntuGIS ppa?

[wildintellect]

I included a specific version in the apt-get install

qgis=1.2.0-1~jaunty1

It was the only way to make sure it pulled the right one, not sure how it will effect upgrades down the line but seems to work with multiple repos available. changeset:1873

[hamish]

fyi I've asked Jachym to package an updated version of GRASS and to see if it is possible to consolidate that at ppa.launchpad.net instead of his personal repo.

IIUC in the plain /etc/sources.list file you can set the repo priority by putting one before the other on the list. I'm not sure how to do that with sources.list.d, but that's just for identical version numbers.

AFAIK Jachym's repo depends on the ppa.launchpad repo for qgis, but I've got no control over if a specific qgus version is depended upon by his package.

We might want to just get GRASS and QGIS from UbuntuGIS ppa?

that would be great, if GRASS 6.4.0rc5-2 were available from there. (?)

Hamish

[hamish]

re. r1873:

apt-get install --assume-yes --force-yes  ... grass-doc

"--force-yes" is a big hammer, just keep an eye out that you don't deinstall grass in the process if it finds a different version of grass-doc.

       --force-yes
           Force yes; This is a dangerous option that will
           cause apt to continue without prompting if it is
           doing something potentially harmful. It should
           not be used except in very special situations.
           Using force-yes can potentially destroy your
           system!

those conflict checks are there for a reason.

Hamish

[hamish]

Replying to hamish:

just keep an eye out that you don't deinstall grass in the process if it finds a different version of grass-doc.

[deinstall -> break]

[wildintellect]

I'm only doing version select on qgis, as for repos I'm using UbuntuGIS which seems to have the same version of GRASS as Jachym, whom I've spoke with about starting to upload to launchpad before.

For now I'll separate out the apt command into 2 so the force option is only on the qgis part. When I tried it without, it wouldn't let me do it.

[hamish]

Replying to wildintellect:

I'm only doing version select on qgis, as for repos I'm using UbuntuGIS which seems to have the same version of GRASS as Jachym, whom I've spoke with about starting to upload to launchpad before. For now I'll separate out the apt command into 2 so the force option is only on the qgis part. When I tried it without, it wouldn't let me do it.

what was the error?

Hamish

[wildintellect]

It appears that the error was cause by Jachym's repo not being authenticated, specifically for libgdal1-1.6.0 which seems to pull from there instead of Ubuntugis because it's a slightly higher build version.

[hamish]

Ok, one thing that would not be good at all is to be installing different binary packages which depend on different versions of GDAL. I suspect that libgdal-1.5.0 and libgdal-1.6.0 would peacefully coexist (the whole point of versioning their package names after all), but it seems a bit wasteful and might confuse anything built from source. (?)

Each binary will be built for one specific version (soname) of libgdal, and should have a rule to require exactly that version if it is to function. Hopefully they all do.

We could 'debuild' the latest GRASS 6.4.0 release branch SVN into a package as part of the GRASS build script so it would match, but that would require a load of -dev scripts to build it. (I'm already doing that for gpsdrive). Similarly we could rebuild QGIS+ for the older version.

Well, fingers crossed for an updated GRASS package.

What other packages depend on gdal directly and are affected by this? In the end we will not be able to rebuild every package in the suite to accommodate using the latest-greatest new release of one package.

:-/ but we will see.

Hamish

[hamish]

GRASS 6.4.0rc4 is available here:

 http://ppa.launchpad.net/ubuntugis/ubuntugis-unstable/ubuntu/pool/main/g/grass/

so we should just use that instead of Jachym's repo? Does it give us everything we need? The .dsc file says that Frankie is the uploader, but I suspect that might just be left over from the Debian package setting. (I know next to nothing about how launchpad works)

The GRASS package there does depend on libgdal-1.5.0:  http://ppa.launchpad.net/ubuntugis/ubuntugis-unstable/ubuntu/pool/main/g/grass/grass_6.4.0~rc4-3intrepid1.dsc

The best solution would be good to get the latest 6.4.0rc5-2 from Debian/unstable or testing or Ubuntu 9.10 rebuilt for 9.04 and in that launchpad repo. No idea how to make that happen.

Hamish

[wildintellect]

I think that's an error on the qgis-grass-plugin, I'm pretty sure 1.6 also works. I'm pulling all from UbuntuGIS on my laptop and 1.5 and 1.6 got pulled because of that rule but I'm pretty sure QGIS is using 1.6.

Oh how confusing, the place to ask about that is the UbuntuGIS mailing list, Alan uploaded most of the packages.

[hamish]

fyi I removed --force-yes from the install_qgis.sh script, it is just too dangerous and could break everything. (I've done this in the past, it can be ugly to clean up) Also I got word from Jachym that he is currently building a new 6.4.0rc5 package.

the place to ask about that is the UbuntuGIS mailing list, Alan uploaded most of the packages.

I am not familiar with them; can you ask if they can backport 6.4.0rc5 from debian/unstable|testing or ubuntu 9.10 repos into that launchpad.net repo, building with the exact same version of gdal as the qgis version does? Then everything may be in harmony and we can just use the single non-conflicting sources.list entry.

thanks, Hamish

[jachym]

Packages recompiled and uploaded to Les-ejk. I did not sign them, because of the last person in changelog is Frankie and I did no changes - any hint, how to approach in this kind of situations?

Maybe somebody already has written to me, how to upload the packages, I'm providing, to launchpad - I have not understand the whole idea of launchpad yet. So, any quick howto would help. I already asked for it and did nothing, due to time reasons :-( Thanks.

[hamish]

Hi,

I found my notes from Francesco on how to add changelog entries. From the the main source dir (one below the debian/ dir)

append a new changelog item to the current package version:

debchange -a "your message here"

increment version and add a new entry with message:

debchange -i "your message here"

or you can just cut and paste & edit a new entry by hand, but syntax counts so be careful.

If based on grass 6.4.0rc5 + DebianGIS svn packaging you might then edit the version number to be like 6.4.0~rc5-2.intrepid.

Re. editors something like vi is already changelog aware. (for better or worse)

hope it helps, Hamish

[hamish]

Packages recompiled and uploaded to Les-ejk. I did not sign them, because of the last person in changelog is Frankie and I did no changes - any hint, how to approach in this kind of situations?

add a new changelog entry manually editing the version to match which changelog message like "repackage for Ubuntu 9.04" or something.

Besides the version number you may want to change "unstable" to "stable". But I'm not sure how much that matters.

I have not understand the whole idea of launchpad yet.

me neither.

Hamish

[hamish]

Alan Boudreault wrote:

grass 6.4.0~rc5.2 has been built in the UbuntuGIS PPA.

Ok, grass_install.sh updated in svn to use the UbuntuGIS repo. So now gdal + qgis + grass should all be in sync for Jaunty.

 http://ppa.launchpad.net/ubuntugis/

Hamish

[neteler]

test - please ignore

[neteler]

test - please ignore (for ML forward)

[neteler]

sorry, one more mailing list test

[hamish]

everything seems fine in the latest beta2 build. only possible issue is that we don't need to add the qgis-specific launchpad key now that we only use the ubuntugis one.

closing bug.

Hamish