> 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 (e
On Sat, Sep 08, 2001 at 11:17:47PM +0300, Baruch Even wrote:
> I've taken over wvdial package with permission. The package had several
> bugs fixed in former NMUs and I've uploaded a new version to fix another
> one, but the bugs fixed in former NMUs are still marked as fixed in NMU
> instead of be
On Sat, Sep 08, 2001 at 12:12:47PM -0700, Sean 'Shaleh' Perry wrote:
>
> On 08-Sep-2001 Christian T. Steigies wrote:
> > Hi,
> > I get a lot of those with lintian on m68k:
> >
> > Operator or semicolon missing before &supported at (eval 115) line 1.
> > Ambiguous use of & resolved as operator & a
On Sat, Sep 08, 2001 at 09:45:09PM -0700, Sean 'Shaleh' Perry wrote:
> > 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)
> 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 (
On Sun, Sep 09, 2001 at 01:36:31AM +0300, Baruch Even wrote:
> > > > > I've taken over wvdial package with permission. The package had
> > > > > several
> > > > > bugs fixed in former NMUs and I've uploaded a new version to fix
> > > > > another
> > > > > one, but the bugs fixed in former NMUs ar
* Josip Rodin <[EMAIL PROTECTED]> [010909 01:35]:
> On Sun, Sep 09, 2001 at 12:27:11AM +0300, Baruch Even wrote:
> > > > I've taken over wvdial package with permission. The package had several
> > > > bugs fixed in former NMUs and I've uploaded a new version to fix another
> > > > one, but the bugs
On Sun, Sep 09, 2001 at 12:27:11AM +0300, Baruch Even wrote:
> > > I've taken over wvdial package with permission. The package had several
> > > bugs fixed in former NMUs and I've uploaded a new version to fix another
> > > one, but the bugs fixed in former NMUs are still marked as fixed in NMU
> >
* Josip Rodin <[EMAIL PROTECTED]> [010909 00:22]:
> On Sat, Sep 08, 2001 at 11:17:47PM +0300, Baruch Even wrote:
> > I've taken over wvdial package with permission. The package had several
> > bugs fixed in former NMUs and I've uploaded a new version to fix another
> > one, but the bugs fixed in fo
On Sun, Sep 09, 2001 at 01:36:31AM +0300, Baruch Even wrote:
> > > > > I've taken over wvdial package with permission. The package had several
> > > > > bugs fixed in former NMUs and I've uploaded a new version to fix another
> > > > > one, but the bugs fixed in former NMUs are still marked as fix
On Sat, Sep 08, 2001 at 11:17:47PM +0300, Baruch Even wrote:
> I've taken over wvdial package with permission. The package had several
> bugs fixed in former NMUs and I've uploaded a new version to fix another
> one, but the bugs fixed in former NMUs are still marked as fixed in NMU
> instead of be
Hello,
I've taken over wvdial package with permission. The package had several
bugs fixed in former NMUs and I've uploaded a new version to fix another
one, but the bugs fixed in former NMUs are still marked as fixed in NMU
instead of being marked as plain fixed.
What should I have done to get th
* Josip Rodin <[EMAIL PROTECTED]> [010909 01:35]:
> On Sun, Sep 09, 2001 at 12:27:11AM +0300, Baruch Even wrote:
> > > > I've taken over wvdial package with permission. The package had several
> > > > bugs fixed in former NMUs and I've uploaded a new version to fix another
> > > > one, but the bug
On 08-Sep-2001 Christian T. Steigies wrote:
> Hi,
> I get a lot of those with lintian on m68k:
>
> 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 w
On Sun, Sep 09, 2001 at 12:27:11AM +0300, Baruch Even wrote:
> > > I've taken over wvdial package with permission. The package had several
> > > bugs fixed in former NMUs and I've uploaded a new version to fix another
> > > one, but the bugs fixed in former NMUs are still marked as fixed in NMU
>
* Josip Rodin <[EMAIL PROTECTED]> [010909 00:22]:
> On Sat, Sep 08, 2001 at 11:17:47PM +0300, Baruch Even wrote:
> > I've taken over wvdial package with permission. The package had several
> > bugs fixed in former NMUs and I've uploaded a new version to fix another
> > one, but the bugs fixed in f
Hi Christian!
You wrote:
> 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.
Looks like a bug in lintian to me. Have you
Hi,
I get a lot of those with lintian on m68k:
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.
Is my package really that bad?
On Sat, Sep 08, 2001 at 11:17:47PM +0300, Baruch Even wrote:
> I've taken over wvdial package with permission. The package had several
> bugs fixed in former NMUs and I've uploaded a new version to fix another
> one, but the bugs fixed in former NMUs are still marked as fixed in NMU
> instead of b
Hello,
I've taken over wvdial package with permission. The package had several
bugs fixed in former NMUs and I've uploaded a new version to fix another
one, but the bugs fixed in former NMUs are still marked as fixed in NMU
instead of being marked as plain fixed.
What should I have done to get t
On 08-Sep-2001 Christian T. Steigies wrote:
> Hi,
> I get a lot of those with lintian on m68k:
>
> 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
Hi Christian!
You wrote:
> 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.
Looks like a bug in lintian to me. Have yo
Hi,
i´ve packaged eroaster (a cdrecord frontend) and gkrellm-gnome (a plugin for
gkrellm that adds gnome support). I also plan to package 3 perl modules.
The packages can be found at www.blendi.org/debian/
I am searching for a debian developer who is willing to sponsor and advocate
me.
Martin
--
Hi,
i´ve packaged eroaster (a cdrecord frontend) and gkrellm-gnome (a plugin for
gkrellm that adds gnome support). I also plan to package 3 perl modules.
The packages can be found at www.blendi.org/debian/
I am searching for a debian developer who is willing to sponsor and advocate
me.
Martin
--
24 matches
Mail list logo
