Report forwarded to debian-bugs-dist@lists.debian.org, Sean 'Shaleh' Perry <shaleh@debian.org>:
Bug#92122; Package lintian.   debian-bugs-dist@lists.debian.orgSean 'Shaleh' Perry  Subject: Bug#92122: lintian: Lots of perl warnings on m68k Reply-To: Simon Richter , 92122@bugs.debian.org Resent-From: Simon Richter Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Sean 'Shaleh' Perry Resent-Date: Thu, 29 Mar 2001 19:33:53 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 92122 X-Debian-PR-Package: lintian X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by bugs@bugs.debian.org id=B.9858940257991 (code B ref -1); Thu, 29 Mar 2001 19:33:53 GMT From: Simon Richter To: Debian Bug Tracking System X-Reportbug-Version: 1.14 X-Mailer: reportbug 1.14 Date: Thu, 29 Mar 2001 23:08:31 +0200 Message-Id: <14ijei-1N7-00@lasagna.hogyros> Delivered-To: submit@bugs.debian.org Package: lintian Version: 1.20.6 Severity: normal Hi, during a lintian run I get loads of warnings about ambiguous use of '&' and future reserved words (Treated with sort | uniq for briefness): -+- cut here -+- Ambiguous use of & resolved as operator & at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 116) line 1. Ambiguous use of & resolved as operator & at (eval 119) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 116) line 1. Operator or semicolon missing before &supported at (eval 119) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 116) line 1. Unquoted string "supported" may clash with future reserved word at (eval 119) line 1. -+- cut here -+- Simon -- System Information Debian Release: testing/unstable Architecture: m68k Kernel: Linux lasagna 2.2.10 #1 Mon Nov 27 20:50:14 CET 2000 m68k Versions of packages lintian depends on: ii binutils 2.9.5.0.37-1 The GNU assembler, linker and bina ii diffstat 1.28-1 produces graph of changes introduc ii file 3.33-4 Determines file type using "magic" ii perl 5.6.0-20 Larry Wall's Practical Extracting ii perl [perl5] 5.6.0-20 Larry Wall's Practical Extracting   Acknowledgement sent to Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>:
New Bug report received and forwarded. Copy sent to Sean 'Shaleh' Perry <shaleh@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: Simon Richter Subject: Bug#92122: Acknowledgement (lintian: Lots of perl warnings on m68k) Message-ID: In-Reply-To: <14ijei-1N7-00@lasagna.hogyros> References: <14ijei-1N7-00@lasagna.hogyros> X-Debian-PR-Message: ack 92122 Thank you for the problem report you have sent regarding Debian. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the developers mailing list for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Sean 'Shaleh' Perry If you wish to submit further information on your problem, please send it to 92122@bugs.debian.org (and *not* to bugs@bugs.debian.org). Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at submit) by bugs.debian.org; 29 Mar 2001 19:27:05 +0000 From geier@phobos.fachschaften.tu-muenchen.de Thu Mar 29 13:27:05 2001 Return-path: Received: from mailrelay2.lrz-muenchen.de [129.187.254.102] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14ii4W-00024q-00; Thu, 29 Mar 2001 13:27:05 -0600 Received: from [129.187.40.79] by mailrelay2.lrz-muenchen.de with ESMTP; Thu, 29 Mar 2001 21:27:02 +0200 Received: from geier by lasagna.hogyros with local (MasqMail 0.1.7) id 14ijei-1N7-00; Thu, 29 Mar 2001 23:08:32 +0200 From: Simon Richter To: Debian Bug Tracking System Subject: lintian: Lots of perl warnings on m68k X-Reportbug-Version: 1.14 X-Mailer: reportbug 1.14 Date: Thu, 29 Mar 2001 23:08:31 +0200 Message-Id: <14ijei-1N7-00@lasagna.hogyros> Delivered-To: submit@bugs.debian.org Package: lintian Version: 1.20.6 Severity: normal Hi, during a lintian run I get loads of warnings about ambiguous use of '&' and future reserved words (Treated with sort | uniq for briefness): -+- cut here -+- Ambiguous use of & resolved as operator & at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 116) line 1. Ambiguous use of & resolved as operator & at (eval 119) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 116) line 1. Operator or semicolon missing before &supported at (eval 119) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 116) line 1. Unquoted string "supported" may clash with future reserved word at (eval 119) line 1. -+- cut here -+- Simon -- System Information Debian Release: testing/unstable Architecture: m68k Kernel: Linux lasagna 2.2.10 #1 Mon Nov 27 20:50:14 CET 2000 m68k Versions of packages lintian depends on: ii binutils 2.9.5.0.37-1 The GNU assembler, linker and bina ii diffstat 1.28-1 produces graph of changes introduc ii file 3.33-4 Determines file type using "magic" ii perl 5.6.0-20 Larry Wall's Practical Extracting ii perl [perl5] 5.6.0-20 Larry Wall's Practical Extracting   Information forwarded to debian-bugs-dist@lists.debian.org, Sean 'Shaleh' Perry <shaleh@debian.org>:
Bug#92122; Package lintian.   debian-bugs-dist@lists.debian.orgSean 'Shaleh' Perry  Subject: Bug#92122: lintian: Lots of perl warnings on m68k Reply-To: "Sean 'Shaleh' Perry" , 92122@bugs.debian.org Resent-From: "Sean 'Shaleh' Perry" Orignal-Sender: Sean 'Shaleh' Perry Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Sean 'Shaleh' Perry Resent-Date: Thu, 29 Mar 2001 21:18:15 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 92122 X-Debian-PR-Package: lintian X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 92122-bugs@bugs.debian.org id=B92122.98590058330681 (code B ref 92122); Thu, 29 Mar 2001 21:18:15 GMT Content-Length: 438 Message-ID: X-Mailer: XFMail 1.4.4 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14ijei-1N7-00@lasagna.hogyros> Date: Thu, 29 Mar 2001 13:14:04 -0800 (PST) Organization: VA Linux From: "Sean 'Shaleh' Perry" To: Simon Richter Cc: 92122@bugs.debian.org Sender: Sean 'Shaleh' Perry Delivered-To: 92122@bugs.debian.org On 29-Mar-2001 Simon Richter wrote: > Package: lintian > Version: 1.20.6 > Severity: normal > > Hi, > > during a lintian run I get loads of warnings about ambiguous use of '&' and > future reserved words (Treated with sort | uniq for briefness): > Someone always submits a bug after i sit on a release for a week, sigh. Ok, can you mail me the entire unadulturated version? There is not enough info there for me to track it down.   Acknowledgement sent to "Sean 'Shaleh' Perry" <shaleh@valinux.com>:
Extra info received and forwarded to list. Copy sent to Sean 'Shaleh' Perry <shaleh@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: "Sean 'Shaleh' Perry" Subject: Bug#92122: Info received (was Bug#92122: lintian: Lots of perl warnings on m68k) Message-ID: In-Reply-To: References: X-Debian-PR-Message: ack-info-maintonly 92122 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Sean 'Shaleh' Perry If you wish to continue to submit further information on your problem, please send it to 92122@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at 92122) by bugs.debian.org; 29 Mar 2001 21:16:23 +0000 From shaleh@valinux.com Thu Mar 29 15:16:22 2001 Return-path: Received: from mail.valinux.com [198.186.202.175] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14ijmI-0007yo-00; Thu, 29 Mar 2001 15:16:22 -0600 Received: from geisha.engr.valinux.com ([10.12.3.6] ident=mail) by mail.valinux.com with esmtp (Exim 3.22 #1 (Debian)) id 14ijhM-0005zR-00; Thu, 29 Mar 2001 13:11:16 -0800 Received: from shaleh by geisha.engr.valinux.com with local (Exim 3.22 #1 (Debian)) id 14ijk4-00042A-00; Thu, 29 Mar 2001 13:14:04 -0800 Content-Length: 438 Message-ID: X-Mailer: XFMail 1.4.4 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14ijei-1N7-00@lasagna.hogyros> Date: Thu, 29 Mar 2001 13:14:04 -0800 (PST) Organization: VA Linux From: "Sean 'Shaleh' Perry" To: Simon Richter Subject: RE: Bug#92122: lintian: Lots of perl warnings on m68k Cc: 92122@bugs.debian.org Sender: Sean 'Shaleh' Perry Delivered-To: 92122@bugs.debian.org On 29-Mar-2001 Simon Richter wrote: > Package: lintian > Version: 1.20.6 > Severity: normal > > Hi, > > during a lintian run I get loads of warnings about ambiguous use of '&' and > future reserved words (Treated with sort | uniq for briefness): > Someone always submits a bug after i sit on a release for a week, sigh. Ok, can you mail me the entire unadulturated version? There is not enough info there for me to track it down.   Information forwarded to debian-bugs-dist@lists.debian.org, Sean 'Shaleh' Perry <shaleh@debian.org>:
Bug#92122; Package lintian.   debian-bugs-dist@lists.debian.orgSean 'Shaleh' Perry  Subject: Bug#92122: lintian: Lots of perl warnings on m68k Reply-To: Simon Richter , 92122@bugs.debian.org Resent-From: Simon Richter Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Sean 'Shaleh' Perry Resent-Date: Fri, 30 Mar 2001 09:18:29 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 92122 X-Debian-PR-Package: lintian X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 92122-bugs@bugs.debian.org id=B92122.9859434275792 (code B ref 92122); Fri, 30 Mar 2001 09:18:29 GMT Date: Fri, 30 Mar 2001 11:10:17 +0200 (CEST) From: Simon Richter To: Sean 'Shaleh' Perry cc: <92122@bugs.debian.org> In-Reply-To: Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: 92122@bugs.debian.org On Thu, 29 Mar 2001, Sean 'Shaleh' Perry wrote: > > during a lintian run I get loads of warnings about ambiguous use of '&' and > > future reserved words (Treated with sort | uniq for briefness): > Someone always submits a bug after i sit on a release for a week, sigh. At least it isn't marked important as the untraceable bug on my package... :-) > Ok, can you mail me the entire unadulturated version? There is not enough info > there for me to track it down. I doubt this will help more, since it still doesn't contain filenames. :-/ Simon -+- cut here -+- Unquoted string "supported" may clash with future reserved word at (eval 116) line 1. Operator or semicolon missing before &supported at (eval 116) line 1. Ambiguous use of & resolved as operator & at (eval 116) line 1. Unquoted string "supported" may clash with future reserved word at (eval 119) line 1. Operator or semicolon missing before &supported at (eval 119) line 1. Ambiguous use of & resolved as operator & at (eval 119) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. -+- cut here -+- -- GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc Fingerprint: DC26 EB8D 1F35 4F44 2934 7583 DBB6 F98D 9198 3292 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! NP: Aphex Twin - Hot Butter Popcorn UP: 11:10am up 34 days, 15:41, 1 user, load average: 0.97, 0.59, 0.45   Acknowledgement sent to Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>:
Extra info received and forwarded to list. Copy sent to Sean 'Shaleh' Perry <shaleh@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: Simon Richter Subject: Bug#92122: Info received (was Bug#92122: lintian: Lots of perl warnings on m68k) Message-ID: In-Reply-To: References: X-Debian-PR-Message: ack-info-maintonly 92122 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Sean 'Shaleh' Perry If you wish to continue to submit further information on your problem, please send it to 92122@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at 92122) by bugs.debian.org; 30 Mar 2001 09:10:27 +0000 From Simon.Richter@phobos.fachschaften.tu-muenchen.de Fri Mar 30 03:10:27 2001 Return-path: Received: from mailrelay1.lrz-muenchen.de [129.187.254.101] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14iuvL-0001VN-00; Fri, 30 Mar 2001 03:10:27 -0600 Received: from phobos.fachschaften.tu-muenchen.de by mailrelay1.lrz-muenchen.de with ESMTP; Fri, 30 Mar 2001 11:10:24 +0200 Received: from geier (helo=localhost) by phobos.fachschaften.tu-muenchen.de with local-esmtp (Exim 3.12 #1 (Debian)) id 14iuvF-0000NU-00; Fri, 30 Mar 2001 11:10:21 +0200 Date: Fri, 30 Mar 2001 11:10:17 +0200 (CEST) From: Simon Richter To: Sean 'Shaleh' Perry cc: <92122@bugs.debian.org> Subject: RE: Bug#92122: lintian: Lots of perl warnings on m68k In-Reply-To: Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: 92122@bugs.debian.org On Thu, 29 Mar 2001, Sean 'Shaleh' Perry wrote: > > during a lintian run I get loads of warnings about ambiguous use of '&' and > > future reserved words (Treated with sort | uniq for briefness): > Someone always submits a bug after i sit on a release for a week, sigh. At least it isn't marked important as the untraceable bug on my package... :-) > Ok, can you mail me the entire unadulturated version? There is not enough info > there for me to track it down. I doubt this will help more, since it still doesn't contain filenames. :-/ Simon -+- cut here -+- Unquoted string "supported" may clash with future reserved word at (eval 116) line 1. Operator or semicolon missing before &supported at (eval 116) line 1. Ambiguous use of & resolved as operator & at (eval 116) line 1. Unquoted string "supported" may clash with future reserved word at (eval 119) line 1. Operator or semicolon missing before &supported at (eval 119) line 1. Ambiguous use of & resolved as operator & at (eval 119) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. Unquoted string "supported" may clash with future reserved word at (eval 112) line 1. Operator or semicolon missing before &supported at (eval 112) line 1. Ambiguous use of & resolved as operator & at (eval 112) line 1. Unquoted string "supported" may clash with future reserved word at (eval 115) line 1. Operator or semicolon missing before &supported at (eval 115) line 1. Ambiguous use of & resolved as operator & at (eval 115) line 1. -+- cut here -+- -- GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc Fingerprint: DC26 EB8D 1F35 4F44 2934 7583 DBB6 F98D 9198 3292 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! NP: Aphex Twin - Hot Butter Popcorn UP: 11:10am up 34 days, 15:41, 1 user, load average: 0.97, 0.59, 0.45   Information forwarded to debian-bugs-dist@lists.debian.org, Sean 'Shaleh' Perry <shaleh@debian.org>:
Bug#92122; Package lintian.   debian-bugs-dist@lists.debian.orgSean 'Shaleh' Perry  Subject: Bug#92122: lintian: Lots of perl warnings on m68k Reply-To: "Sean 'Shaleh' Perry" , 92122@bugs.debian.org Resent-From: "Sean 'Shaleh' Perry" Orignal-Sender: Sean 'Shaleh' Perry Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Sean 'Shaleh' Perry Resent-Date: Fri, 30 Mar 2001 17:18:37 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 92122 X-Debian-PR-Package: lintian X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 92122-bugs@bugs.debian.org id=B92122.98597253720516 (code B ref 92122); Fri, 30 Mar 2001 17:18:37 GMT Content-Length: 982 Message-ID: X-Mailer: XFMail 1.4.4 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 30 Mar 2001 09:13:22 -0800 (PST) Organization: VA Linux From: "Sean 'Shaleh' Perry" To: Simon Richter Cc: 92122@bugs.debian.org Sender: Sean 'Shaleh' Perry Delivered-To: 92122@bugs.debian.org On 30-Mar-2001 Simon Richter wrote: > On Thu, 29 Mar 2001, Sean 'Shaleh' Perry wrote: > >> > during a lintian run I get loads of warnings about ambiguous use of '&' >> > and >> > future reserved words (Treated with sort | uniq for briefness): > >> Someone always submits a bug after i sit on a release for a week, sigh. > > At least it isn't marked important as the untraceable bug on my package... >:-) > true enough, however ...... >> Ok, can you mail me the entire unadulturated version? There is not enough >> info >> there for me to track it down. > > I doubt this will help more, since it still doesn't contain filenames. :-/ > > Simon > > -+- cut here -+- > Unquoted string "supported" may clash with future reserved word at (eval 116) > line 1. The word 'supported' does not appear in lintian -- anywhere. It appears in a desc file, but that is not code, just text that it prints when --info is enabled. I think this is coming from somewhere else. Sorry.   Acknowledgement sent to "Sean 'Shaleh' Perry" <shaleh@valinux.com>:
Extra info received and forwarded to list. Copy sent to Sean 'Shaleh' Perry <shaleh@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: "Sean 'Shaleh' Perry" Subject: Bug#92122: Info received (was Bug#92122: lintian: Lots of perl warnings on m68k) Message-ID: In-Reply-To: References: X-Debian-PR-Message: ack-info-maintonly 92122 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Sean 'Shaleh' Perry If you wish to continue to submit further information on your problem, please send it to 92122@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at 92122) by bugs.debian.org; 30 Mar 2001 17:15:37 +0000 From shaleh@valinux.com Fri Mar 30 11:15:37 2001 Return-path: Received: from mail.valinux.com [198.186.202.175] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14j2Ur-0005Kq-00; Fri, 30 Mar 2001 11:15:37 -0600 Received: from geisha.engr.valinux.com ([10.12.3.6] ident=mail) by mail.valinux.com with esmtp (Exim 3.22 #1 (Debian)) id 14j2Py-0005ww-00; Fri, 30 Mar 2001 09:10:34 -0800 Received: from shaleh by geisha.engr.valinux.com with local (Exim 3.22 #1 (Debian)) id 14j2Sg-00046v-00; Fri, 30 Mar 2001 09:13:22 -0800 Content-Length: 982 Message-ID: X-Mailer: XFMail 1.4.4 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 30 Mar 2001 09:13:22 -0800 (PST) Organization: VA Linux From: "Sean 'Shaleh' Perry" To: Simon Richter Subject: RE: Bug#92122: lintian: Lots of perl warnings on m68k Cc: 92122@bugs.debian.org Sender: Sean 'Shaleh' Perry Delivered-To: 92122@bugs.debian.org On 30-Mar-2001 Simon Richter wrote: > On Thu, 29 Mar 2001, Sean 'Shaleh' Perry wrote: > >> > during a lintian run I get loads of warnings about ambiguous use of '&' >> > and >> > future reserved words (Treated with sort | uniq for briefness): > >> Someone always submits a bug after i sit on a release for a week, sigh. > > At least it isn't marked important as the untraceable bug on my package... >:-) > true enough, however ...... >> Ok, can you mail me the entire unadulturated version? There is not enough >> info >> there for me to track it down. > > I doubt this will help more, since it still doesn't contain filenames. :-/ > > Simon > > -+- cut here -+- > Unquoted string "supported" may clash with future reserved word at (eval 116) > line 1. The word 'supported' does not appear in lintian -- anywhere. It appears in a desc file, but that is not code, just text that it prints when --info is enabled. I think this is coming from somewhere else. Sorry.   Information forwarded to debian-bugs-dist@lists.debian.org, Sean 'Shaleh' Perry <shaleh@debian.org>:
Bug#92122; Package lintian.   debian-bugs-dist@lists.debian.orgSean 'Shaleh' Perry  Subject: Bug#92122: lintian: Lots of perl warnings on m68k Reply-To: Simon Richter , 92122@bugs.debian.org Resent-From: Simon Richter Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Sean 'Shaleh' Perry Resent-Date: Sun, 01 Apr 2001 16:03:53 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 92122 X-Debian-PR-Package: lintian X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 92122-bugs@bugs.debian.org id=B92122.98614069517479 (code B ref 92122); Sun, 01 Apr 2001 16:03:53 GMT Date: Sun, 1 Apr 2001 17:58:05 +0200 (CEST) From: Simon Richter To: Sean 'Shaleh' Perry cc: <92122@bugs.debian.org>, In-Reply-To: Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: 92122@bugs.debian.org reassign 92122 perl-modules thanks On Fri, 30 Mar 2001, Sean 'Shaleh' Perry wrote: > The word 'supported' does not appear in lintian -- anywhere. It appears in a > desc file, but that is not code, just text that it prints when --info is > enabled. I think this is coming from somewhere else. Sorry. Hrm, what about this: geier@lasagna:~/librfc822$ grep -r '&supported' /usr/lib/perl /usr/lib/perl/5.6.0/asm/unistd.ph: eval 'sub __NR_iopl () { ¬ &supported;}' unless defined(&__NR_iopl); /usr/lib/perl/5.6.0/asm/unistd.ph: eval 'sub __NR_vm86 () { ¬ &supported;}' unless defined(&__NR_vm86); That would explain the messages about the "&" and the "supported". :-) Simon -- GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc Fingerprint: DC26 EB8D 1F35 4F44 2934 7583 DBB6 F98D 9198 3292 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!   Acknowledgement sent to Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>:
Extra info received and forwarded to list. Copy sent to Sean 'Shaleh' Perry <shaleh@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: Simon Richter Subject: Bug#92122: Info received (was Bug#92122: lintian: Lots of perl warnings on m68k) Message-ID: In-Reply-To: References: X-Debian-PR-Message: ack-info-maintonly 92122 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Sean 'Shaleh' Perry If you wish to continue to submit further information on your problem, please send it to 92122@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at 92122) by bugs.debian.org; 1 Apr 2001 15:58:15 +0000 From Simon.Richter@phobos.fachschaften.tu-muenchen.de Sun Apr 01 10:58:15 2001 Return-path: Received: from mailrelay1.lrz-muenchen.de [129.187.254.101] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14jkF5-0004Xq-00; Sun, 01 Apr 2001 10:58:15 -0500 Received: from phobos.fachschaften.tu-muenchen.de by mailrelay1.lrz-muenchen.de with ESMTP; Sun, 1 Apr 2001 17:58:13 +0200 Received: from geier (helo=localhost) by phobos.fachschaften.tu-muenchen.de with local-esmtp (Exim 3.12 #1 (Debian)) id 14jkF1-0004uJ-00; Sun, 01 Apr 2001 17:58:11 +0200 Date: Sun, 1 Apr 2001 17:58:05 +0200 (CEST) From: Simon Richter To: Sean 'Shaleh' Perry cc: <92122@bugs.debian.org>, Subject: RE: Bug#92122: lintian: Lots of perl warnings on m68k In-Reply-To: Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: 92122@bugs.debian.org reassign 92122 perl-modules thanks On Fri, 30 Mar 2001, Sean 'Shaleh' Perry wrote: > The word 'supported' does not appear in lintian -- anywhere. It appears in a > desc file, but that is not code, just text that it prints when --info is > enabled. I think this is coming from somewhere else. Sorry. Hrm, what about this: geier@lasagna:~/librfc822$ grep -r '&supported' /usr/lib/perl /usr/lib/perl/5.6.0/asm/unistd.ph: eval 'sub __NR_iopl () { ¬ &supported;}' unless defined(&__NR_iopl); /usr/lib/perl/5.6.0/asm/unistd.ph: eval 'sub __NR_vm86 () { ¬ &supported;}' unless defined(&__NR_vm86); That would explain the messages about the "&" and the "supported". :-) Simon -- GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc Fingerprint: DC26 EB8D 1F35 4F44 2934 7583 DBB6 F98D 9198 3292 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!   Bug reassigned from package `lintian' to `perl-modules'. Request was from Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 1 Apr 2001 15:58:15 +0000 From Simon.Richter@phobos.fachschaften.tu-muenchen.de Sun Apr 01 10:58:15 2001 Return-path: Received: from mailrelay1.lrz-muenchen.de [129.187.254.101] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14jkF5-0004Xq-00; Sun, 01 Apr 2001 10:58:15 -0500 Received: from phobos.fachschaften.tu-muenchen.de by mailrelay1.lrz-muenchen.de with ESMTP; Sun, 1 Apr 2001 17:58:13 +0200 Received: from geier (helo=localhost) by phobos.fachschaften.tu-muenchen.de with local-esmtp (Exim 3.12 #1 (Debian)) id 14jkF1-0004uJ-00; Sun, 01 Apr 2001 17:58:11 +0200 Date: Sun, 1 Apr 2001 17:58:05 +0200 (CEST) From: Simon Richter To: Sean 'Shaleh' Perry cc: <92122@bugs.debian.org>, Subject: RE: Bug#92122: lintian: Lots of perl warnings on m68k In-Reply-To: Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: control@bugs.debian.org reassign 92122 perl-modules thanks On Fri, 30 Mar 2001, Sean 'Shaleh' Perry wrote: > The word 'supported' does not appear in lintian -- anywhere. It appears in a > desc file, but that is not code, just text that it prints when --info is > enabled. I think this is coming from somewhere else. Sorry. Hrm, what about this: geier@lasagna:~/librfc822$ grep -r '&supported' /usr/lib/perl /usr/lib/perl/5.6.0/asm/unistd.ph: eval 'sub __NR_iopl () { ¬ &supported;}' unless defined(&__NR_iopl); /usr/lib/perl/5.6.0/asm/unistd.ph: eval 'sub __NR_vm86 () { ¬ &supported;}' unless defined(&__NR_vm86); That would explain the messages about the "&" and the "supported". :-) Simon -- GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc Fingerprint: DC26 EB8D 1F35 4F44 2934 7583 DBB6 F98D 9198 3292 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!   Bug reassigned from package `perl-modules' to `perl'. Request was from Brendan O'Dea <bod@debian.org> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 9 Jan 2002 05:02:50 +0000 From bod@compusol.com.au Tue Jan 08 23:02:50 2002 Return-path: Received: from 210-50-77-245.cust.syd.iprimus.net.au (duende.compusol.com.au) [210.50.77.245] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16OAsz-0008Bn-00; Tue, 08 Jan 2002 23:02:50 -0600 Received: from bod by duende.compusol.com.au with local (Exim 3.33 #1 (Debian)) id 16OAsY-0004YU-00 for ; Wed, 09 Jan 2002 16:02:22 +1100 Date: Wed, 9 Jan 2002 16:02:22 +1100 From: Brendan O'Dea To: control@bugs.debian.org Subject: Reassign perl-related packages to "perl" Message-ID: <20020109050222.GA17509@compusol.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Sender: Brendan O'Dea Delivered-To: control@bugs.debian.org # libperl5.6 reassign 113881 perl # perl-5.005 reassign 44375 perl reassign 49004 perl reassign 49820 perl reassign 50151 perl reassign 52166 perl reassign 53590 perl reassign 54987 perl reassign 55796 perl reassign 55913 perl reassign 56785 perl reassign 58326 perl reassign 58398 perl reassign 63906 perl reassign 64308 perl reassign 64757 perl reassign 65224 perl reassign 67479 perl reassign 68483 perl reassign 72635 perl reassign 72675 perl reassign 75053 perl reassign 78104 perl reassign 79190 perl reassign 126608 perl # perl-5.005-base reassign 57217 perl reassign 61765 perl reassign 64310 perl reassign 65096 perl reassign 65715 perl reassign 66702 perl reassign 67376 perl reassign 72689 perl reassign 75116 perl reassign 77707 perl reassign 78437 perl reassign 81571 perl reassign 61301 perl # perl-5.005-doc reassign 51962 perl reassign 63405 perl reassign 68876 perl reassign 76293 perl # perl-5.6 reassign 78143 perl reassign 78157 perl reassign 78311 perl reassign 79532 perl reassign 86561 perl # perl-5.6-base reassign 78724 perl reassign 79943 perl # perl-base reassign 69378 perl reassign 71573 perl reassign 95879 perl reassign 104361 perl reassign 104414 perl reassign 116528 perl reassign 128146 perl # perl-doc reassign 96132 perl reassign 101933 perl reassign 113370 perl reassign 114060 perl # perl-modules reassign 92122 perl reassign 98235 perl reassign 103055 perl reassign 127581 perl reassign 127689 perl thanks   Changed Bug submitter from Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de> to Simon Richter <sjr@debian.org>. Request was from Simon Richter <sjr@debian.org> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 23 Sep 2008 18:18:28 +0000 From Simon.Richter@kleinhenz.com Tue Sep 23 18:18:28 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3-bugs.debian.org_2005_01_02 (2007-08-08) on rietz.debian.org X-Spam-Level: X-Spam-Bayes: score:0.0000 Tokens: new, 41; hammy, 29; neutral, 37; spammy, 2. spammytokens:0.987-1--92899, 0.940-+--H*r:sk:rietz.d hammytokens:0.000-+--H*u:Mutt, 0.000-+--H*r:Client, 0.000-+--H*UA:1.5.18, 0.000-+--H*u:1.5.18, 0.000-+--H*UA:2008-05-17 X-Spam-Status: No, score=-12.0 required=4.0 tests=AWL,BAYES_00,FROMDEVELOPER, VALID_BTS_CONTROL autolearn=ham version=3.2.3-bugs.debian.org_2005_01_02 Return-path: Received: from static.88-198-202-190.clients.your-server.de ([88.198.202.190] helo=kleinhenz.com) by rietz.debian.org with esmtp (Exim 4.63) (envelope-from ) id 1KiCSx-00016e-TS for control@bugs.debian.org; Tue, 23 Sep 2008 18:18:28 +0000 Received: from localhost (mnch-5d87206b.pool.einsundeins.de [93.135.32.107]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Simon Richter", Issuer "CA Cert Signing Authority" (verified OK)) by kleinhenz.com (Postfix) with ESMTP id 782323926ED for ; Tue, 23 Sep 2008 20:31:24 +0200 (CEST) Date: Tue, 23 Sep 2008 20:18:34 +0200 From: Simon Richter To: control@bugs.debian.org Subject: old address is old Message-ID: <20080923181834.GB14186@richter> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Delivered-To: control@bugs.debian.org submitter 92122 ! submitter 112349 ! submitter 87862 ! submitter 88486 ! submitter 89725 ! submitter 92899 ! submitter 33991 ! submitter 35691 ! submitter 63833 ! submitter 285768 ! thanks