internal error: command failed with error code 123

Bug #351901 reported by Benjamin Drung
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lintian (Debian)
Fix Released
Unknown
lintian (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: lintian

lintian fails on gnome-colors package:

internal error: command failed with error code 123
warning: collect info file-info about package gnome-colors: 512
warning: skipping check of source package gnome-colors

To reproduce run following commands:

bzr branch lp:gnome-colors-pkg
cd gnome-colors-pkg
uscan --force-download
cd ..
mkdir gnome-colors-3.0
cd gnome-colors-3.0
tar -xvf ../gnome-colors_3.0.orig.tar.gz
cp -r ../gnome-colors-pkg/debian .
debuild -S

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: lintian 2.2.5ubuntu1
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: lintian
Uname: Linux 2.6.28-11-generic x86_64

Revision history for this message
Benjamin Drung (bdrung) wrote :
Revision history for this message
Russ Allbery (rra-debian) wrote : Re: [Bug 351901] [NEW] internal error: command failed with error code 123

Benjamin Drung <email address hidden> writes:

> Binary package hint: lintian
>
> lintian fails on gnome-colors package:
>
> internal error: command failed with error code 123
> warning: collect info file-info about package gnome-colors: 512
> warning: skipping check of source package gnome-colors

This is probably the problem fixed in Lintian 2.2.7. (Debian Bug#517899)

--
Russ Allbery (<email address hidden>) <http://www.eyrie.org/~eagle/>

Changed in lintian:
status: Unknown → Fix Released
Changed in lintian (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

I can confirm that the new version in debian resolved this issue.

I've prepared a merge from Debian. Subscribing ubuntu-release for guidance.

Do we want the newest version in Jaunty? It would be helpful (beyond fixing this bug) for those of us working on packages for Debian as the new release uses Standards Version 3.8.1 Though I don't know what Ubuntu policy is on something like this. Should this wait for jaunty-backports?

If ubuntu-release decides to hold off on this, I could prepare a patch for this bug alone.

Upstream git commit resolving this issue:

http://git.debian.org/?p=lintian/lintian.git;a=commitdiff;h=1dcd45e8941505fe78995036a4f697ab43f31106

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Since we don't have/use Standards-Version 3.8.1 yet, I'd prefer a backport of this, as a target of opportunity. I don't consider it a release critical problem anyway. Thank you!

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

Fixed in Karmic.

lintian (2.2.9ubuntu1) karmic; urgency=low

  * Resynchronise with Debian. Remaining changes:
    - Don't complain about `dist-packages' in /usr/lib/python*.
  * Permit data.tar.lzma for packages with Ubuntu distributions at the head
    of their changelog (LP: #339519).

Changed in lintian (Ubuntu):
status: Confirmed → 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.