>
> The Debian policy manual don't agree with you, AFAIR.
I know it doesn't, that's why lintian complains. But what should I do? I think
renaming a command would cause more disruption.
Best
--
Salvo Tomaselli
"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/14 00:26, gregor herrmann wrote:
> On Sun, 09 Mar 2014 21:39:01 +, Dave Walker wrote:
>
>>> Net::Frame::Device includes two scripts that are installed to
>>> /usr/bin, but both have .pl extensions therefore giving me a
>>> Lintian warning
Le Mon, Mar 10, 2014 at 03:19:51PM +0800, Thomas Goirand a écrit :
> On 03/10/2014 04:49 AM, Salvo Tomaselli wrote:
> > Not sure if fixing it by renaming the files is what you want to do.
> >
> > I have such a warning in xinetd and honestly I just ignore it because I
> > don't
> > think that ren
On 03/10/2014 04:49 AM, Salvo Tomaselli wrote:
> Not sure if fixing it by renaming the files is what you want to do.
>
> I have such a warning in xinetd and honestly I just ignore it because I don't
> think that renaming scripts after they have been there for many years is a
> good idea. Besides
On Sun, 09 Mar 2014 21:39:01 +, Dave Walker wrote:
> > Net::Frame::Device includes two scripts that are installed to /usr/bin,
> > but both have .pl extensions therefore giving me a Lintian warning.
> >
> > My initial thought on fixing this is to rename the files by overriding
> > dh_auto_inst
On 9 Mar 2014 19:52, "Daniel Lintott" wrote:
>
> Hi,
>
> I am in the process packaging Net::Frame::Device
> (libnet-frame-device-perl) as part of a the fix to a bug.
>
> Net::Frame::Device includes two scripts that are installed to /usr/bin,
> but both have .pl extensions therefore giving me a Lin
Not sure if fixing it by renaming the files is what you want to do.
I have such a warning in xinetd and honestly I just ignore it because I don't
think that renaming scripts after they have been there for many years is a
good idea. Besides that's the upstream name so that's how they will be
pro
Hi,
I am in the process packaging Net::Frame::Device
(libnet-frame-device-perl) as part of a the fix to a bug.
Net::Frame::Device includes two scripts that are installed to /usr/bin,
but both have .pl extensions therefore giving me a Lintian warning.
My initial thought on fixing this is to renam
> Od: Charles Plessy
>
JM> > I have output this output from lintian:
JM> > --
JM> > W: zynjacku: script-with-language-extension usr/bin/lv2rack.py
JM> > W: zynjacku: script-with-language-extension usr/bin
On 2009-10-05, Charles Plessy wrote:
> I have repened the Policy bug where the renaming policy was decided, and hope
> to get it reverted.
Don't expect it to happen, but you are free to hope.
/Sune
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscr
Le Mon, Oct 05, 2009 at 02:32:50AM +0200, Jaromír Mikeš a écrit :
> Hello mentors,
>
> I have output this output from lintian:
> --
> W: zynjacku: script-with-language-extension usr/bin/lv2rack.py
> W: zynjacku: script-with-language-extension usr/bin/zynjacku.py
>
On Mon, Oct 05, 2009 at 01:44:11PM +1100, Ben Finney wrote:
> Matthew Palmer writes:
>
> > So someone's using a single file as both a library and a stand-alone
> > program. Damned silly idea.
>
> Not so silly; a Python module can be useful both as a main program and
> as a re-useable component i
On Mon, 2009-10-05 at 13:12 +1100, Matthew Palmer wrote:
> On Mon, Oct 05, 2009 at 03:43:22AM +0200, Jarom?r Mike? wrote:
> > > Od: Jarom?r Mike?
> >
> > JM> > I did it, but it breaks functionality ... there exist also symlinks
> > with
> > JM> same name and in same location.
> >
> > JM> > usr/
Jaromír Mikeš writes:
> Any link where I can study more to understand and solve problem?
The ‘debian-python’ forum already mentioned, and the documentation (such
as it is) for the popular third-party ‘setuptools’ extension for the
Python distutils.
--
\ “I think it would be a good idea.”
> Od: Ben Finney
MP> > Stick zynjacku.py in a proper library path somewhere, and write a
MP> > little shim wrapper to stick in /usr/bin that calls zynjacku as it
MP> > expects to be called.
BF> Yes, that's one way to do it, and quite valid. It does, though, involve
BF> creating that shim separa
Matthew Palmer writes:
> So someone's using a single file as both a library and a stand-alone
> program. Damned silly idea.
Not so silly; a Python module can be useful both as a main program and
as a re-useable component in other programs. The well-known Python idiom
of testing ‘if __name__ == '
> Od: Matthew Palmer
JM> > I did it, but it breaks functionality ... there exist also symlinks
JM> > with same name and in same location.
JM> > usr/bin/lv2rack
JM> > usr/bin/zynjacku
JM> > usr/bin/zynspect
JM> > --
JM> > usr/bin/lv2rack.py
JM> > usr/bin/zynjacku.py
JM> > usr/bin/zynspect.py
> Od: Chow Loong Jin
> You should probably try reading the Debian Python New Policy[1] and getting
> help
> from #debian-python on OFTC or debian-pyt...@lists.debian.org.
>
> [1] http://wiki.debian.org/DebianPython/NewPolicy
I didn't know that there is debian-python list, I will try ask there.
On Mon, Oct 05, 2009 at 03:43:22AM +0200, Jarom?r Mike? wrote:
> > Od: Jarom?r Mike?
>
> JM> > I did it, but it breaks functionality ... there exist also symlinks with
> JM> same name and in same location.
>
> JM> > usr/bin/lv2rack
> JM> > usr/bin/zynjacku
> JM> > usr/bin/zynspect
> JM> > --
On Monday 05,October,2009 09:43 AM, Jaromír Mikeš wrote:
> BTW: error message for lv2rack is:
> ---
> $ lv2rack
> Traceback (most recent call last):
> File "/usr/bin/lv2rack", line 52, in
> import zynjacku as zynjacku
> --
>
> I got warning from other mailing list that this package
> Od: Jaromír Mikeš
JM> > I did it, but it breaks functionality ... there exist also symlinks with
JM> same name and in same location.
JM> > usr/bin/lv2rack
JM> > usr/bin/zynjacku
JM> > usr/bin/zynspect
JM> > --
JM> > usr/bin/lv2rack.py
JM> > usr/bin/zynjacku.py
JM> > usr/bin/zynspect.py
CL
> Od: Chow Loong Jin
JM> > I did it, but it breaks functionality ... there exist also symlinks with
same
JM> name and in same location.
JM> > usr/bin/lv2rack
JM> > usr/bin/zynjacku
JM> > usr/bin/zynspect
JM> > --
JM> > usr/bin/lv2rack.py
JM> > usr/bin/zynjacku.py
JM> > usr/bin/zynspect.py
>
r/bin/zynjacku.py
> usr/bin/zynspect.py
>
> Hmmm what about remove these symlink first and then remove suffix?
> I am going to try it.
How about just mv /usr/bin/lv2rack.py /usr/bin/lv2rack and so on? `lintian-info
-t script-with-language-extension` is a good read as to why stuff in /usr/bin/
From: Jose Luis Rivas
JM> I have output this output from lintian:
JM> --
JM> W: zynjacku: script-with-language-extension usr/bin/lv2rack.py
JM> W: zynjacku: script-with-language-extension usr/bin/zynjacku.py
JM> W: zynjacku: script-with-language-extension usr/bin
On Mon, Oct 05, 2009 at 02:32:50AM +0200, Jaromír Mikeš wrote:
> Hello mentors,
>
> I have output this output from lintian:
> --
> W: zynjacku: script-with-language-extension usr/bin/lv2rack.py
> W: zynjacku: script-with-language-extension usr/bin/zynjacku.py
>
Hello mentors,
I have output this output from lintian:
--
W: zynjacku: script-with-language-extension usr/bin/lv2rack.py
W: zynjacku: script-with-language-extension usr/bin/zynjacku.py
W: zynjacku: script-with-language-extension usr/bin/zynspect.py
--
I tried (one by one
26 matches
Mail list logo
