Your message dated Mon, 1 Nov 2010 21:58:47 +0000
with message-id <[email protected]>
and subject line Re: Bug#272955: sbuild: cannot install versioned dependencies 
correclty
has caused the Debian Bug report #272955,
regarding sbuild: cannot install versioned dependencies correclty
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
272955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272955
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.33
Severity: normal

Automatic build of ximian-connector_2.0.0-1 on nighthawk.oase.mhn.de by
sbuild/i386 1.169
Build started at 20040923-0146
******************************************************************************
ximian-connector_2.0.0-1.dsc exists in cwd
** Using build dependencies supplied by package:
Build-Depends: cdbs, debhelper (>= 4.1.0), intltool, evolution (>= 2.0),
evolution-dev (>= 2.0), evolution-data-server-dev (>= 1.0),
libgnomeprintui2.2-dev, libldap2-dev, heimdal-dev
Checking for already installed source dependencies...
[...]
evolution: missing
evolution-dev: missing
evolution-data-server-dev: missing
[...]
Get:1 http://ftp.de.debian.org unstable/main evolution 1.4.6-5 [10.3MB]
[...]
Selecting previously deselected package evolution.
Unpacking evolution (from .../evolution_1.4.6-5_i386.deb) ...
[...]
Checking correctness of source dependencies...
After installing, the following source dependencies are still unsatisfied:
evolution(inst 1.4.6-5 ! >= wanted 2.0) evolution-dev(inst 1.4.6-5 ! >=
        wanted 2.0)
Source-dependencies not satisfied; skipping ximian-connector

I got experimental (where evolution 2.0 lives) in my chroot's APT but
this does not seem to be enough. I do not have any APT-pinning set, if I
do pin experimental highter than unstable, evolution 2.0 gets installed
(along with the rest of GNOME-2.8, which seems alright).

Do we think that people should have a $(chroot)/etc/apt/preferences
pinning experimental higher than unstable in order to correctly build
experimental packages? Should sbuild work around this? Am I missing
something?


Michael
source, but it does not get dragged in
-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=POSIX, lc_ctype=de_de.iso-8859...@euro

Versions of packages sbuild depends on:
ii  adduser                       3.59       Add and remove users and groups
ii  apt                           0.5.27     Advanced front-end for dpkg
ii  dpkg-dev                      1.10.23    Package building tools for Debian
ii  exim4                         4.34-6     An MTA (Mail Transport Agent)
ii  exim4-daemon-light [mail-tran 4.34-6     Lightweight version of the Exim (v
ii  perl                          5.8.4-2.2  Larry Wall's Practical Extraction 
ii  sudo                          1.6.7p5-2  Provide limited super user privile

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.60.0-1

On Thu, Sep 23, 2004 at 10:25:20AM +0200, Francesco Paolo Lovergine wrote:
> On Thu, Sep 23, 2004 at 03:11:48AM +0200, Michael Banck wrote:
> > I got experimental (where evolution 2.0 lives) in my chroot's APT but
> > this does not seem to be enough. I do not have any APT-pinning set, if I
> > do pin experimental highter than unstable, evolution 2.0 gets installed
> > (along with the rest of GNOME-2.8, which seems alright).
> > 
> > Do we think that people should have a $(chroot)/etc/apt/preferences
> > pinning experimental higher than unstable in order to correctly build
> > experimental packages? Should sbuild work around this? Am I missing
> > something?
> 
> I think yes currently. Sbuild follows the same internals of apt, and 
> you can only install explicitly experimental packages, without pinning.
> That should be documented somewhere, indeed.

The pain of building experimental packages is now solved with the
addition of the "aptitude" build-dep resolver to sbuild.  In
consequence, I'm closing this old bug.


Thanks,
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.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to