Your message dated Sun, 15 Jan 2017 18:32:23 +0100
with message-id <[email protected]>
and subject line Re: Bug#834990: pbuilder-satisfydepends segfaults on armhf 
emulation
has caused the Debian Bug report #834990,
regarding pbuilder-satisfydepends segfaults on armhf emulation
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.)


-- 
834990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834990
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pbuilder
Version: 0.225.2
Severity: important

I tried creating an armhf-sid chroot through pbuilder successfully. Then
I tried building an armhf package using the pbuilder image and ran into
the following segfault.


The following packages are RECOMMENDED but will NOT be installed:
  at-spi2-core curl dbus krb5-locales libgtk-3-bin libltdl-dev
  libmail-sendmail-perl libpng-tools libx11-doc lynx-cur wget
  xdg-user-dirs xml-core 
  0 packages upgraded, 260 newly installed, 0 to remove and 0 not
  upgraded.
  Need to get 79.5 MB/102 MB of archives. After unpacking 351 MB will be
  used.
  Writing extended state information...
  /usr/lib/pbuilder/pbuilder-satisfydepends: line 29: 29996 Segmentation
  fault      $CHROOTEXEC env XDG_CACHE_HOME=/root aptitude -y
  --without-recommends -o APT::Install-Recommends=false
  "${APTITUDEOPT[@]}" -o Aptitude::ProblemResolver::StepScore=100 -o
  "Aptitude::ProblemResolver::Hints::KeepDummy=reject
  pbuilder-satisfydepends-dummy :UNINST" -o
  Aptitude::ProblemResolver::Keep-All-Level=55000 -o
  Aptitude::ProblemResolver::Remove-Essential-Level=maximum install
  pbuilder-satisfydepends-dummy
  E: pbuilder-satisfydepends failed.
  I: unmounting /var/tmp/lxc/ccache/ccache filesystem
  I: unmounting /var/cache/apt/archives/ filesystem
  I: unmounting dev/pts filesystem
  I: unmounting run/shm filesystem
  I: unmounting proc filesystem
  I: unmounting sys filesystem
  I: cleaning the build env 
  I: removing directory /var/tmp/Debian-Build/Build//29633 and its
  subdirectories
  gbp:error: '/home/rrs/bin/gbp-pbuilder' failed: it exited with 1
  2016-08-21 / 16:38:45 ♒♒♒  ☹  => 1  


To me, it looks like aptitude may be the culprit. But I'm not sure.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (500, 
'unstable-debug'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.1bfqv8r2+ (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  debootstrap            1.0.81
ii  dpkg-dev               1.18.10
ii  wget                   1.18-2+b1

Versions of packages pbuilder recommends:
ii  devscripts  2.16.6
ii  eatmydata   105-3
ii  fakeroot    1.21-1
ii  iproute2    4.6.0-1
ii  net-tools   1.60+git20150829.73cef8a-2
ii  sudo        1.8.17p1-2

Versions of packages pbuilder suggests:
ii  cowdancer   0.80
ii  gdebi-core  0.9.5.7

-- debconf information:
* pbuilder/rewrite: false
  pbuilder/nomirror:
  pbuilder/mirrorsite: http://ftp.debian.org/debian/

--- End Message ---
--- Begin Message ---
On Sun, Aug 21, 2016 at 05:32:33PM +0530, Ritesh Raj Sarraf wrote:
> On Sun, 2016-08-21 at 16:46 +0530, Ritesh Raj Sarraf wrote:
> > 
> > To me, it looks like aptitude may be the culprit. But I'm not sure.
> 
> It does look like aptitude failing.

Oh, well, I'm closing this bug.

There is really nothing pbuilder can do if an underlying tool segfaults,
moreover I recently used aptitute in an armhf chroot and it just worked.

> On this topic, should we also have an option
> to select an apt backend of choice ?

They are not really interchangable when used like this.  Anyway, now
there is also an apt resolver, and I invite you to try it (you can also
do cross builds with it!).

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to