Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: binnmu
Hello It seems that with the latest python the extensions are expected to be under /usr/lib/python2.x/site-package/<package>/gnukfreebsd9 instead of gnukfreebsd8 (when the package was uploaded) the first effect is that the package is broken under kfreebsd but also that it cause FTBFS for other packages. like the current state of mmtk. I do not know if other packages are affected by this problem, and I do not know if this nmu is the right way to deal with this issue. I am trying to find a better to way to deal with this with the upstream (move the Extension in the right namespace instead of building this kind of Extension) thanks Frederic nmu python-scientific_2.9.2-4 . kfreebsd-amd64 kfreebsd-i386 . -m "Rebuild to take into account the new toolchain" -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.9-1-486 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
