Control: tag -1 moreinfo On Mon, Jun 17, 2013 at 22:04:27 +0200, Picca Frédéric-Emmanuel wrote:
> 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) > Where is the version number picked? If it depends on the running kernel on the build/runtime host then this needs to be fixed properly, not worked around with binNMUs on kernel version changes. Cheers, Julien
signature.asc
Description: Digital signature
