aptitude why error message has no newline

Bug #589909 reported by Brian Beck
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)
Fix Released
Low
Unassigned
Lucid
Won't Fix
Undecided
Unassigned
Maverick
Fix Released
Low
Unassigned

Bug Description

Binary package hint: aptitude

At the command prompt when you type "aptitude why" you get the following:

why: this command requires at least one argument (the package to query).bbeck@tardis:~$

Notice there is no newline after the error message so the prompt is directly after the error message. It should appear like so:

why: this command requires at least one argument (the package to query).
bbeck@tardis:~$

My version information:
Description: Ubuntu 10.04 LTS
Release: 10.04

aptitude:
  Installed: 0.4.11.11-1ubuntu10
  Candidate: 0.4.11.11-1ubuntu10
  Version table:
 *** 0.4.11.11-1ubuntu10 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

I have attached a patch, and I believe this problem is solved in later versions of aptitude, so there may be not much benefit pushing upstream.

Revision history for this message
Brian Beck (brian-beck76) wrote :
Changed in aptitude (Ubuntu):
assignee: nobody → Teej (xteejx)
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

I have generated a debdiff for this. It's attached.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :
Changed in aptitude (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: Teej (xteejx) → nobody
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you send the change to the Debian BTS as well (bugs.debian.org)?

Changed in aptitude (Ubuntu):
importance: Medium → Low
Revision history for this message
Michael Vogt (mvo) wrote :

This problem is fixed in maverick, the code reads now:

      fprintf(stderr, _("%s: this command requires at least one argument (the package to query).\n"),

I don't think we can backport that easily to lucid as it does break a lot of translation. Unless someone tries to manually unfuzzy?

Changed in aptitude (Ubuntu):
status: Triaged → Incomplete
Changed in aptitude (Ubuntu Lucid):
status: New → Won't Fix
Changed in aptitude (Ubuntu Maverick):
status: Incomplete → Fix Released
Revision history for this message
Michael Vogt (mvo) wrote :

I set this to Won't fix for now, but we can reopen it if its feasible to manually unfuzzy the strings.

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.