[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#705363: marked as done (parley-data: adequate reports py-file-not-bytecompiled bugs in parley-data)

Your message dated Sat, 13 Apr 2013 20:13:15 +0200
with message-id <201304132013.20159.pino@debian.org>
and subject line Re: Bug#705363: parley-data: adequate reports py-file-not-bytecompiled bugs in parley-data
has caused the Debian Bug report #705363,
regarding parley-data: adequate reports py-file-not-bytecompiled bugs in parley-data
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 owner@bugs.debian.org
immediately.)


-- 
705363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705363
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: parley-data
Version: 4:4.10.2-1
Justification: Policy 2.6
Severity: serious

Dear Maintainer,
Adequate reported quite a few py-file-not-bytecompiled bugs when
upgrading parley-data today which can be seen in Debian Python Policy
2.6 in the python package
/usr/share/doc/python/python-policy.html/ch-module_packages.html

The policy says :-

2.6 Modules Byte-Compilation

If a binary package provides any binary-independent modules (foo.py
files), the corresponding byte-compiled modules (foo.pyc files) and
optimized modules (foo.pyo files) must not ship in the package.
Instead, they should be generated in the package's postinst, and
removed in the package's prerm. The package's prerm has to make sure
that both foo.pyc and foo.pyo are removed.

A binary package should only byte-compile the files which belong to the package.

The file /etc/python/debian_config allows configuration how modules
should be byte-compiled. The postinst scripts should respect these
settings.

Pure Python modules in private installation directories that are
byte-compiled with the default Python version must be forcefully
byte-compiled again when the default Python version changes. Public
Python extensions should be bin-NMUed. Private Python extensions
should be subject to binary NMUs every time the default interpreter
changes, unless the extension is updated through a .rtupdate script.

Now this is what adequate reports :-

parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/google_images.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/wiktionary_sound.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/example.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/page.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/http.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/errors.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/client.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/compatibility.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/__init__.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/page_nowriteapi.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/ex.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/simplejson/decoder.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/simplejson/scanner.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/simplejson/encoder.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/simplejson/__init__.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/simplejson/jsonfilter.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/mwclient/listing.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/leo-dict.py
parley-data: py-file-not-bytecompiled
/usr/share/kde4/apps/parley/plugins/google_dictionary.py

Could somebody fix this ?

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (10, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information
-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17

--- End Message ---
--- Begin Message --- 
Hi,

before starting to report such stuff, what about contacting us 
beforehand?

Alle sabato 13 aprile 2013, shirish शिरीष ha scritto:
> Adequate reported quite a few py-file-not-bytecompiled bugs when
> upgrading parley-data today which can be seen in Debian Python Policy
> 2.6 in the python package
> /usr/share/doc/python/python-policy.html/ch-module_packages.html

Note this is specific to *modules*.

> Now this is what adequate reports :-
> 
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/google_images.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/wiktionary_sound.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/example.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/page.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/http.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/errors.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/client.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/compatibility.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/__init__.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/page_nowriteapi.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/ex.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/simplejson/decoder.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/simplejson/scanner.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/simplejson/encoder.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/simplejson/__init__.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/simplejson/jsonfilter.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/mwclient/listing.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/leo-dict.py
> parley-data: py-file-not-bytecompiled
> /usr/share/kde4/apps/parley/plugins/google_dictionary.py
> 
> Could somebody fix this ?

Those are just scripts executed in parley as tools, and not Python 
modules.

Nothing to fix there, hence closing.

-- 
Pino Toscano

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: