Package: python-jinja2
Version: 2.7.2-2
Severity: normal
User: [email protected]
Usertags: adequate broken-symlink

Dear Maintainer,
        I was installing ipython-notebook and one of the depends is
python-jinja2 in it. This is the output that adequate told after doing
the install.

adequate found packaging bugs
-----------------------------

python-jinja2: broken-symlink /usr/share/doc/python-jinja2/html ->
../python-jinja2-doc/html
python-jinja2: broken-symlink /usr/share/doc/python-jinja2/rst ->
../python-jinja2-doc/html/_sources
ipython-notebook-common: py-file-not-bytecompiled
/usr/share/ipython/notebook/static/components/fabfile.py

I am reporting the first two. I looked at the PATH and for sure there
in no python-jinja2-doc directory.

I did cd /usr/share/doc/python-jin <TAB> for tab-completion and it completed :-

$ cd /usr/share/doc/python-jinja2/ which means that directory isn't
created. Could you please look into it.

An additional point, if I may, as can be seen python-jinja2-doc
package is a suggests. If the symlink should be in this package, then
python-jinja2-doc should be in recommnds or even depends.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'testing-updates'), (1,
'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages python-jinja2 depends on:
ii  python             2.7.5-5
ii  python-markupsafe  0.18-1+b1

Versions of packages python-jinja2 recommends:
ii  python-pkg-resources  2.2-1

Versions of packages python-jinja2 suggests:
pn  python-jinja2-doc  <none>

-- 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


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to