On Fri, 2012-07-20 at 16:20:24 +0200, Philipp Kern wrote:
> On Fri, Jul 20, 2012 at 03:35:01PM +0200, Guillem Jover wrote:
> > ISTR other segfaults in other dpkg code paths on s390x (maybe I'm just
> > misremembering), if that's the case that might hint at a deeper
> > problem in the architecture,
On Fri, Jul 20, 2012 at 03:35:01PM +0200, Guillem Jover wrote:
> ISTR other segfaults in other dpkg code paths on s390x (maybe I'm just
> misremembering), if that's the case that might hint at a deeper
> problem in the architecture, hardware, kernel, glibc, etc?
You'd be surprised, however, about
On Fri, 2012-07-20 at 13:37:05 +0300, Damyan Ivanov wrote:
> wb gb firebird2.5_2.5.2~svn+54698.ds4-1 . s390x
>
> The regular build[1] failed with a very strange error in the package
> creation phase:
>
> dpkg-shlibdeps: error: dpkg-query --control-path libicu48:s390x symbols died
> from sign
On Fri, Jul 20, 2012 at 01:37:05PM +0300, Damyan Ivanov wrote:
> wb gb firebird2.5_2.5.2~svn+54698.ds4-1 . s390x
>
> The regular build[1] failed with a very strange error in the package
> creation phase:
>
> dpkg-shlibdeps: error: dpkg-query --control-path libicu48:s390x symbols died
> from
wb gb firebird2.5_2.5.2~svn+54698.ds4-1 . s390x
The regular build[1] failed with a very strange error in the package
creation phase:
dpkg-shlibdeps: error: dpkg-query --control-path libicu48:s390x symbols died
from signal 11
[1]
https://buildd.debian.org/status/fetch.php?pkg=firebird2.5&a
5 matches
Mail list logo