Hi, Thanks a lot for your analysis.
On 02/04/08 at 16:55 +0200, Nicolas François wrote: > Hi, > > On Wed, Apr 02, 2008 at 12:41:52PM +0200, [EMAIL PROTECTED] wrote: > > > > During a rebuild of all packages in sid, your package failed to build on > > i386. > > Thanks a lot for all these rebuilds and analysis. > > > Build deps on a | b are not supported by sbuild, because they would > > cause uncertainties in the resulting binaries. Please don't use them, > > and choose a single python version in your build-deps. > > This is explicitly allowed by policy (7.1), and is really what is needed > to build the translate toolkit. > > The toolkit needs the ElementTree module from xml.etree (provided by > python2.5) or from elementtree (provided by the python-elementtree > module). The module is needed during the build to load applications and > generate manpages. It will not really be used and will not cause > uncertainties in the resulting binaries. > > This dependency permits to use the same package on Debian, Ubuntu, and > backport. > > I will check later what I will do with this bug (it is IMO a bug in > sbuild). > > I can imagine some solutions to fix this bug: > * invert the '|' dependencies. > This should bypass the bug in sbuild now, and this will have to be > reverted when Debain will switch to python 2.5 > * Always build with python-elementtree. > This will make the package FTBFS when Debian will move to python 2.5 > This will make the Ubuntu package to differ from the Debian package > * Always build with python2.5 > This will make the package FTBFS when Debian will move to python 2.6 > This will make the backport package to differ > * Do not build the manpages at build time > This makes the build process non-automatic > > * python2.5 could Provide python-elementtree. Currently it provides > python-elementtree2.5 > python-elementtree and python-elementtree2.5 are not identical the > import line in Python is different, so I don't think it would be > correct. > > My preference would go to the first one (or fix sbuild). > > I will wait for the translate toolkit to exit the NEW queue (#472954) > before uploading any changes. My order of preference goes to: 1) > * Always build with python2.5 > This will make the package FTBFS when Debian will move to python 2.6 > This will make the backport package to differ 2) > * invert the '|' dependencies. > This should bypass the bug in sbuild now, and this will have to be > reverted when Debain will switch to python 2.5 3) Since the package is arch:all, I can mark it as "FTBFS, but sbuild problem" in my list if you don't want to fix that (but most packages where that occurs were fixed) the other solutions don't seem to be good ideas, for the reasons you pointed out. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
