Bug#392488: lilypond-data: byte-compiled python file in /usr/share violates FHS

severity 392488 important thanks You can now stop playing BTS tag; thanks. Andreas Barth <[EMAIL PROTECTED]> writes: > severity 392488 serious > > * Thomas Bushnell BSG ([EMAIL PROTECTED]) [061012 10:39]: >> However, .pyc files are machine-independent, so there is no violation >> in having them

Processed: Re: Bug#392488: lilypond-data: byte-compiled python file in /usr/share violates FHS

Processing commands for [EMAIL PROTECTED]: > severity 392488 serious Bug#392488: lilypond-data: don't ship .pyc files in accord with Python policy Severity set to `serious' from `important' > * Thomas Bushnell BSG ([EMAIL PROTECTED]) [061012 10:39]: Unknown command or malformed arguments to comma

Processed: Re: Bug#392488: lilypond-data: byte-compiled python file in /usr/share violates FHS

Processing commands for [EMAIL PROTECTED]: > severity 392488 important Bug#392488: lilypond-data: byte-compiled python file in /usr/share violates FHS Severity set to `important' from `serious' > retitle 392488 lilypond-data: don't ship .pyc files in accord with Python

Bug#392488: lilypond-data: byte-compiled python file in /usr/share violates FHS

severity 392488 important retitle 392488 lilypond-data: don't ship .pyc files in accord with Python policy thanks "Sam Hocevar \(Debian packages\)" <[EMAIL PROTECTED]> writes: > Package: lilypond-data > Version: 2.6.5-2 > Severity: serious > Justification: Policy 9.1.1 > >/usr/share/lilypond

Bug#392488: lilypond-data: byte-compiled python file in /usr/share violates FHS

Package: lilypond-data Version: 2.6.5-2 Severity: serious Justification: Policy 9.1.1 /usr/share/lilypond/2.6.5/python/*.pyc should be moved out of /usr/share and out of the Arch:all package. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'un