On Tue, Jul 15, 2014 at 07:18:39AM +0200, Aurelien Jarno wrote:
I can follow up with a list affected packages, but we are slowly
discovering them one by one, so it might takes time. So far we have:
* Mixing modules/libraries built with pre-2.19 and 2.19 libc
- perl
- libpng
* Using libc
On Tue, Jul 15, 2014 at 1:18 AM, Aurelien Jarno aure...@debian.org wrote:
On Mon, Jul 14, 2014 at 11:14:42PM -0400, Carlos O'Donell wrote:
On Mon, Jul 14, 2014 at 4:36 PM, Aurelien Jarno aure...@debian.org wrote:
glibc 2.19 has changed the libc ABI on s390, more specifically the
On Tue, Jul 15, 2014 at 09:21:30AM +0200, Philipp Kern wrote:
On Tue, Jul 15, 2014 at 07:18:39AM +0200, Aurelien Jarno wrote:
I can follow up with a list affected packages, but we are slowly
discovering them one by one, so it might takes time. So far we have:
* Mixing modules/libraries
On Tue, Jul 15, 2014 at 03:49:04AM -0400, Carlos O'Donell wrote:
On Tue, Jul 15, 2014 at 1:18 AM, Aurelien Jarno aure...@debian.org wrote:
On Mon, Jul 14, 2014 at 11:14:42PM -0400, Carlos O'Donell wrote:
On Mon, Jul 14, 2014 at 4:36 PM, Aurelien Jarno aure...@debian.org wrote:
glibc 2.19
On 2014-07-12 23:30 +0200, Stephen Powell wrote:
The problem occurs when libc6 must be upgraded during apt-get upgrade
or apt-get dist-upgrade. I see a screen which looks like this:
-
lu Configuring libc6:s390x tk
x Running services and
On Thu, Jul 10, 2014 at 09:46:05PM +0200, Aurelien Jarno wrote:
Hmm, the above has actually been removed in favor of a test on
$(DEB_BUILD_PROFILES).
Instead of duplicating the code, please test for both stage1 and stage2
in the same test.
Updating patch addressing both concerns.
6 matches
Mail list logo
