[buildd-tools-devel] Bug#403246: Bug#403246: Bug#403246: #403246 not fixed as solution not used on buildds

[Roger Leigh]

tags 403246 + fixed-upstream pending
thanks

On Thu, Feb 24, 2011 at 07:51:40PM +0000, Roger Leigh wrote:
> On Mon, Feb 14, 2011 at 11:13:03PM +0100, Bernd Zeimetz wrote:
> > Unfortunately the solution for #403246 is not enough as the aptitude resolver
> > is not used on buildds. Please implement a proper dependency solution in the
> > traditional solver.
> 
> Just to update you on what's happened:
> 
> - new release 0.61.0-1 adds the ability to disable (use first alternative
>   only) or enable alternative build deps for the 'apt' and 'aptitude'
>   resolvers.  It defaults to disabled; setting: $resolve_alternatives
> - current git (0.61.1 prerelease) makes 'apt' the default resolver, and
>   deprecates the old 'internal' resolver.
> - I will shortly make $resolve_alternatives default to off for 'internal'
>   and 'apt', and to on for 'aptitude'.  This will still be configurable,
>   but will match the historical behaviour of all three resolvers.
> 
> We will hopefully soon switch to using 'apt' as the default resolver on
> the buildds, because it is now identical to the internal resolver now it
> uses first-only alternatives, and behaves identically.  Once all buildds
> are using it, 'internal' will be obsoleted and subsequently deleted.
> 
> Following discussion on debian-devel and #debian-devel, the consensus
> was to not allow alternative build dependencies when building for
> unstable, due to the inconsistencies it can introduce to builds.  Note
> that this does not include alternative architecture-specific
> dependencies, which are allowed.  They will be allowed for experimental
> with the aptitude resolver, and possibly backports.
> 
> So, in summary, the bug will be fixed, but it will in most cases not be
> the default behaviour.  I think the solution we have ended up with is
> about the best we can get, and if the default behaviour is not what you
> want you will have the ability to alter it.

From NEWS for the next release:

* Major changes in 0.61.1:

  1) 'apt' is now the default build dependency resolver.  Users should
     not see any significant changes compared with the old 'internal'
     resolver.  Please note that you may need to generate a GPG key
     for the local archive created for dependency package
     installation, if one does not already exist; see sbuild-update
     (--keygen) for further details.

  2) The 'internal' build dependency resolver is deprecated.  It is
     not recommended for future use, and will be removed once it is no
     longer used by the buildd infrastructure.  Please use the 'apt'
     resolver as a drop-in replacement.

  3) The 'aptitude' build dependency resolver will, unlike 'apt' and
     'internal', consider alternative dependencies by default, rather
     than only using the first alternative.  This is intended to both
     preserve backward compatibility, and make the 'aptitude' resolver
     the preferred choice for more complex situations, such as
     building for experimental.

I will be closing the bug now the resolver changes are complete unless
anyone has any objections or further comments?


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20110224/595f0956/attachment-0001.pgp>