installation does not take into account server : always think it is 127.0.0.1

[Alain Baeckeroot]

Binary package hint: hobbit-client

apt-get install hobbit client ask for a hobbit server (127.0.0.1 by default)

If we provide a server IP (192.168.12.13) it is not taken into account, /etc/default/hobbit-client still contains HOBBITSERVERS="127.0.0.1"

It is needed to do `dpkg-reconfigure hobbit-client`, or to manually edit /etc/default/hobbit-client to put the right server.

Tested on both i386 and x86_64 hardy heron

# lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04

#apt-cache policy hobbit-client
hobbit-client:
  Installé : 4.2.0.dfsg-10
  Candidat : 4.2.0.dfsg-10
 Table de version :
 *** 4.2.0.dfsg-10 0
        500 http://fr.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

#

[Jon Kjaersgaard (kjaersgaard)]

This looks a lot like bug #227189
It seems it's fixed in 4.2.0.dfsg-12, but that version is for Ubuntu 8.10 Intrepid only.
For some reason the fix has not made it back to Hardy (why?)

-- Jon

[Alain Baeckeroot (alain-baeckeroot)]

True, this is the same bug, and indeed, we have very large deployments (university), and choose LTS on purpose, with _need_ of great quality :-)

bug #227189 is Fixed in intrepid in 4.2.0.dfsg-12 since 2008-05-31 (Wouter Stomp), it should be done in Hardy too.

/Alain

[Jon Kjaersgaard (kjaersgaard)]

My point excatly, I also work at a university, and we have also specifically chosen a LTS version :)

Hope it's not the Dapper story all over again, once again! Once the distro ships some developers and maintainer stop caring about it, and only work on the next dist. This is perhaps acceptable in a ordinary dist, that for most people will be replaced after 6 months. But a LTS dist targets a different crowd (companies, universities, schools ...), that doesn't have that option.
If I were to change dist every 6 months, the faculty would crucify me :)
And tools like hobbit, that are of particular use in large deployments, _must_ be supported until the next LTS dist comes along.

If no fix is available, thats one thing. But there is a fix for this, and it have been released for the next dist. Why then not for the LTS dist? I mean Hardy isn't even 6 months old, and it is _supposed_ to be supported until 2011.

I would feel a lot better if a maintainer of the package would comment here. (Or at bug #227189)
Even if it is to tell us that there is some problem that prevents them from making a hardy fix.

Just let us know that they are aware of the problem.

-- Jon