Hi,
Stefan Fritsch (20/03/2011):
> this is probably the libdb conflict, #619036. Unfortunately, I don't
> know when it will be fixed. But considering that php5 5.3.6-1 has
> been uploaded, this is no longer a problem related to this binNMU of
> 5.3.5-1.
still an issue for 5.3.6-1 though. FTR: Ma
Hi Cyril,
On Saturday 19 March 2011, Cyril Brulebois wrote:
> Cyril Brulebois (15/03/2011):
> > that doesn't appear to be sufficient. Even with that version
> > available, I'm getting auto-give-backs.
>
> shall I expect a fix on the build-dep side at some point? Or shall
> I just mark php5 as fa
Hi Stefan,
Cyril Brulebois (15/03/2011):
> that doesn't appear to be sufficient. Even with that version
> available, I'm getting auto-give-backs.
shall I expect a fix on the build-dep side at some point? Or shall I
just mark php5 as failed? I keep on getting those give-back mails and
I'm not sur
Hi,
Stefan Fritsch (05/03/2011):
> This should have a dep-wait on libapr1-dev_1.4.2-8, obviously.
that doesn't appear to be sufficient. Even with that version
available, I'm getting auto-give-backs. Log excerpt:
|
┌──┐
On Monday 07 March 2011, Russ Allbery wrote:
> > fsvs
> > libapache2-mod-perl2
> > php5
> > php-svn
> > rapidsvn
> > subversion
> >
> > Does this make sense together with my explanations above?
>
> Yes, but note that _FILE_OFFSET_BITS could be set in config.h, in
> which case the grep won't find
Stefan Fritsch writes:
> Maybe my initial report was misleading. Packages which *only* use apxs
> or apr-config to determine CFLAGS/CPPFLAGS should be fine. If they have
> another means to add additional CFLAGS/CPPFLAGS (in particular -
> D_FILE_OFFSET_BITS=64), they may be affected by the proble
On Monday 07 March 2011, Russ Allbery wrote:
> Stefan Fritsch writes:
> > I fear this affects more packages: I have looked at all packages
> > that depend on libapr1 or have libapache2 in their name. From
> > those, I have grepped for FILE_OFFSET_BITS in their newest
> > kfreebsd build log. If I d
Stefan Fritsch writes:
> I fear this affects more packages: I have looked at all packages that
> depend on libapr1 or have libapache2 in their name. From those, I have
> grepped for FILE_OFFSET_BITS in their newest kfreebsd build log. If I
> didn't do something wrong, these packages need to be
title 616590 nmu various libapr1 rdeps on kfreebsd-*
thanks
I fear this affects more packages: I have looked at all packages that
depend on libapr1 or have libapache2 in their name. From those, I have
grepped for FILE_OFFSET_BITS in their newest kfreebsd build log. If I
didn't do something wron
This should have a dep-wait on libapr1-dev_1.4.2-8, obviously.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Hi,
there is a problem with apr changing ABI on kfreebsd-* depending on
-D_FILE_OFFSET_BITS=64 being used by a libapr user or not. This causes segfaults
for mod_php. See bug #616323
This sh
11 matches
Mail list logo
