| Summary: | Build issue: tqt3 FTBFS with postgresql >= 9.3.3-2 | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Slávek Banko <slavek.banko> |
| Component: | qt3 | Assignee: | Michele Calgaro <michele.calgaro> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | bugwatch, michele.calgaro, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2014 | ||
| Attachments: |
qt3 patch
tqt3 patch |
||
|
Description
Slávek Banko
2014-03-22 14:25:41 CDT
Confirmed. Slavek, the bug is a FTBFS but Jessie is a rolling distro. Should we add this to the v14.0.0 bug list? Considering that sooner or later the package would go into Wheezy and that it will take at least 2-3 months of work before v14.0.0 is ready, I think we should. The importance of this bug is raised because in the upcoming Ubuntu 14.04 (Trusty) Postgresql has been updated to problematic version. This bug prevents tqt3 from building in Jessie, so it is time it get addressed. A full TDE rebuild is way overdue on my system. I am going to work on this in this coming week. Attached proposed patches for qt3 and tqt3. I have tested on Debian Jessie and they work well. Based on information about Debian and Ubuntu packages, it should be ok also for all other Debian/Ubuntu distros. Slavek, Tim, before I push to GIT, please test and confirm (at least on Ubuntu Trusty). Created attachment 2034 [details]
qt3 patch
Created attachment 2035 [details]
tqt3 patch
Excellent - beautifully simple. I tested Ubuntu Trusty and Lucid and both were built fine. I think that you can push the patch. Pushed in commits bd47e75 (qt3) and fcd6bc2 (tqt3) Because launchpad on build-farm resolves dependencies a little differently than standard apt, dependencies was fixed in commit d3df6df7. > Because launchpad on build-farm resolves dependencies a little differently
> than standard apt
Interesting, I didn't know that. What is the difference between the build-farm way and standard apt?
(In reply to Michele Calgaro from comment #10) > > Because launchpad on build-farm resolves dependencies a little differently > > than standard apt > Interesting, I didn't know that. What is the difference between the > build-farm way and standard apt? It seems that while pbuilder solves the installation of dependencies by creating an empty package (pbuilder-satisfydepends-dummy.deb) and using a standard installation by apt, launchpad is probably trying to resolve the dependencies itself. And I had already noticed problems if in the alternative dependency is the first package with the condition <= or <<. > And I had already noticed problems if in the alternative dependency is the
> first package with the condition <= or <<.
Thanks for the explanation, Slavek.
I will try to remember this for future patches, so to avoid the same problem.
|