turba2 too old in dapper

[Ian Smith-Heisters]

Binary package hint: turba2

Trying to install turba2 package, but fails due to a requirement for horde3. Horde3 is already installed and working. At the least, the given error message is misleading.

# apt-get install turba2
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  turba2: Depends: horde3 but it is not going to be installed
E: Broken packages
# dpkg -l horde3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=====================-=====================-==========================================================
ii horde3 3.1.1-1 horde web application framework
#

[Steve Kowalik (stevenk)]

I am unable to reproduce this on an up-to-date Edgy machine. Does this still occur for you?

[Ian Smith-Heisters (public-0x09)]

I'm unable to verify/deny since I don't have any edgy machines, and
furthermore no longer have access to the system that was having the
problem. *Were* you able to reproduce the error on Dapper (which is
what I had the problem on)?

On 10/7/06, Steve Kowalik <email address hidden> wrote:
> I am unable to reproduce this on an up-to-date Edgy machine. Does this
> still occur for you?
>
> --
> won't install, false error message
> https://launchpad.net/bugs/55786
>

[Steve Kowalik (stevenk)]

Yes the problem still exists in Dapper, due to an issue with horde3:

steven@liquified:~% apt-cache show horde3 | grep Conflicts
Conflicts: horde, turba2 (<< 2.1)

This doesn't occur in Edgy due to turba2 being updated to 2.1-1

[Steve Kowalik (stevenk)]

As this bug is fixed in Edgy, and Edgy is due to be released in two days, I am closing this bug.

[Sam Hathaway (sam.hathaway)]

This bug should be reopened since it makes turba2 non-installable on Dapper. If I understand correctly, Dapper is still "supported" until 2011.

[Luca Lesinigo (luckyluke)]

I totally agree with Sam and confirm that the turba2 package is unusable on Dapper, even with dapper-backports.

Since porting the turba2 package from Edgy would solve this bug, where's the problem in doing that?

[Luca Lesinigo (luckyluke)]

PS - this is a blocking bug, turba2 can't be installed. Maybe the urgency should be raised?