dpkg-reconfigure landscape-common broken for intrepid and jaunty

Bug #410378 reported by Andreas Hasenack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Fix Released
High
Free Ekanayaka

Bug Description

I have been testing the landscape-client packages at https://launchpad.net/~free.ekanayaka/+archive/ppa in preparation for a SRU request.

After the update, dpkg-reconfigure landscape-common doesn't work anymore, meaning it just says:
"""
usermod: no changes
"""

Before it would allow to chose how to run landscape-sysinfo (see attached screenshot):
- do not display sysinfo at login
- use update-motd
- run on every login

Therve suspects the bug was introduced because karmic no longer uses update-motd, but intrepid and jaunty do.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

And now the screenshot

Changed in landscape-client:
importance: Undecided → High
milestone: none → 1.3.4
assignee: nobody → Free Ekanayaka (free.ekanayaka)
Revision history for this message
Free Ekanayaka (free.ekanayaka) wrote :

This happens because the client's trunk is missing the debian/landscape-common.config file, which was probably present in the non-trunk-based branches the intrepid/jaunty packages were built against.

I've added the file and everything is fine.

tags: added: review
Changed in landscape-client:
status: New → In Progress
Revision history for this message
Jamu Kakar (jkakar) wrote :

+1, thanks for explaining the details!

Revision history for this message
Thomas Herve (therve) wrote :

Thanks for spotting the problem, +1!

tags: removed: review
Changed in landscape-client:
status: In Progress → Fix Committed
Jamu Kakar (jkakar)
tags: added: needs-testing
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Tested, qa + 1

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Just a note, update-motd apparently has a bug in jaunty:
<andreas> kirkland`: hey
<andreas> kirkland`: I'm testing update-motd + landscape-sysinfo on jaunty
<andreas> kirkland`: I may have found a problem, I don't think the files in /var/run/$NAME/<scriptoutput> are ever cleared
<andreas> kirkland`: I removed landscape-sysinfo and /var/run/motd keeps the old output forever, and /var/run/$NAME/50-landscape-sysinfo still exists from previous runs
<andreas> kirkland`: intrepid doesn't have this bug

tags: removed: needs-testing
tags: added: needs-testing
tags: removed: needs-testing
Changed in landscape-client:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.