Your message dated Wed, 20 May 2009 19:58:30 +0100
with message-id <4a1452d6.9030...@sapo.pt>
and subject line Looks like it's fixed
has caused the Debian Bug report #520956,
regarding aap: Traceback on unknown build target error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
520956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aap
Version: 1.072-1.1
Severity: normal
Tags: patch


Maybe this is fixed upstream, but when I got an error about "Do not know
how to build ..." I get this traceback:

Traceback (most recent call last):
  File "/usr/bin/aap", line 12, in <module>
    Main.main()
  File "/usr/lib/aap/Main.py", line 186, in main
    handle_work_done(msg, work)
  File "/usr/lib/aap/Main.py", line 194, in handle_work_done
    error_msg(work.recdict, msg)
  File "/usr/lib/aap/Main.py", line 34, in error_msg
    msg_error(recdict, msg)
  File "/usr/lib/aap/Message.py", line 164, in msg_error
    msg_msg(recdict, msg, msgt_error, mode = mode, rpstack = rpstack)
  File "/usr/lib/aap/Message.py", line 133, in msg_msg
    print "Aap: " + msg
TypeError: cannot concatenate 'str' and 'tuple' objects


Attached is a patch for 1.072 that fixes this.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable'), (75, 'testing'), (50, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.28.7
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aap depends on:
ii  python                        2.5.4-2    An interactive high-level object-o
ii  python-support                0.8.7      automated rebuilding support for P

aap recommends no packages.

Versions of packages aap suggests:
ii  aap-doc                       1.072-1.1  make-like "expert system" for buil

-- no debconf information
--- /tmp/Main.orig.py	2009-03-23 18:42:55.211298212 -0300
+++ /usr/lib/aap/Main.py	2009-03-23 18:42:58.311301585 -0300
@@ -125,7 +125,7 @@ def do_the_work(argv, find_recipe, comma
         msg = _("Interrupted")
     except UserError, e:
         exit_status = 1
-        msg = e.args
+        msg = e.args[0]
     except SyntaxError, e:
         exit_status = 1
         exit_info = sys.exc_info()
--- /tmp/Error.orig.py	2009-03-23 18:12:20.456340680 -0300
+++ /usr/lib/aap/Error.py	2009-03-23 18:42:34.445296191 -0300
@@ -23,28 +23,28 @@ class FinishRecipe(Exception):
 class UserError(Exception):
     """Error for something the user has done wrong.
        Usually causes us to exit with a non-zero value."""
-    def __init__(self, args = None):
+    def __init__(self, *args):
         Exception.__init__(self)
         self.args = args
 
 class WriteAfterRead(Exception):
     """Error for writing a local variable after reading it from another scope.
     """
-    def __init__(self, args = None):
+    def __init__(self, *args):
         Exception.__init__(self)
         self.args = args
 
 class InternalError(Exception):
     """Error for something wrong in our code.
        Usually causes us to exit with a non-zero value."""
-    def __init__(self, args = None):
+    def __init__(self, *args):
         Exception.__init__(self)
         self.args = args
 
 class OriginUpdate(Exception):
     """An ":recipe" command updated the recipe file and throws this exception
        to cancel executing the old one."""
-    def __init__(self, args = None):
+    def __init__(self, *args):
         Exception.__init__(self)
         self.args = args
 

--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi!

I'm closing this bug, because reporter said it's been fixed in latest unstable 
version.

Thanks

- --
Marco Rodrigues

http://Marco.Tondela.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJKFFLRAAoJENDqNB6bSPIzj48QAIpArViOeEk1tuMAiEqlP4Er
JAnxVXD2JJwyjxTwsuCMZF6L9xg+UkL5fmLL84tuIB46vvp4uk77jXw1/9KnyCSu
SdzEj9oSePI61QFK2IiWDOxSqGT/woigZEJDqY9C2BSlcw7fnxpibeylIrmwgLnU
hxi/PifJXmSZEcdaaCbf0JB+15d0NKck0SkHFUveyXIetk/t8AOPMxfRBqwcc8l9
jMND4XlSiYyqRx7c7c6ZDKIsKBIXf0xDl7JSdhss2QUXQUTtm+D9gEvBuaE9RZVN
+8MLnvan2c691Omswpv57aX2vj8zWN2BtOz+oPUqdTjnYwmtSLVWFtn9D7S2bbpW
b3J/2fgoP2KPLtZzch1Sxlz47P7lof9jmiLm9iNSHx3poxkTAy6CiS8bMwQVq05C
ghqZxPf6EwQeUI+5peeiiL6/1vmaXCURFg85TrsH0iNt6qvytR5jmN7OH9G21xU9
MlXpuplPz0/DTPYRtJ4XvNzgFKSIh+zmjum9QgC6CnWY6K8+UJCZBOkfgO/gr3xc
FsOsM0nodvpDa+7w9YmB9qfbfNugjZ0rSGiX7rMKzlkZptf1OhAgeXHs9zDz7p0E
0+jejk6qiQQs2PtBsq0veWZGU8WCazkwkYQ6sjF+BxPHU+vI90l6v1RdZWM5Tjy6
0TfWqxf/OITEGw07lnJn
=8O77
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to