-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Am 21.12.2012 11:27, schrieb Laszlo Boszormenyi (GCS):
On Fri, 2012-12-21 at 10:00 +0100, stefano wrote:
the package conflicts with php5-common 5.4.4-11 (the last of sid)
but in aptitude the phpapi-20100525 (requests by php-suhosin)
On Tue, Jun 4, 2013 at 1:31 PM, Jan Wagner w...@cyconet.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Am 21.12.2012 11:27, schrieb Laszlo Boszormenyi (GCS):
On Fri, 2012-12-21 at 10:00 +0100, stefano wrote:
the package conflicts with php5-common 5.4.4-11 (the last
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ondřej,
thanks for your reply.
Am 04.06.2013 13:59, schrieb Ondřej Surý:
On Tue, Jun 4, 2013 at 1:31 PM, Jan Wagner w...@cyconet.org
mailto:w...@cyconet.org wrote: as this Break is unversioned, how
is the plan to get a (maybe in the future)
On Tue, Jun 4, 2013 at 2:41 PM, Jan Wagner w...@cyconet.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ondřej,
thanks for your reply.
Am 04.06.2013 13:59, schrieb Ondřej Surý:
On Tue, Jun 4, 2013 at 1:31 PM, Jan Wagner w...@cyconet.org
mailto:w...@cyconet.org wrote: as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 04.06.2013 15:01, schrieb Ondřej Surý:
On Tue, Jun 4, 2013 at 2:41 PM, Jan Wagner w...@cyconet.org
mailto:w...@cyconet.org wrote: When there's some activity on the
upstream part, we can create a plan. The last commit in suhosin
repository on
On Tue, Jun 4, 2013 at 3:30 PM, Jan Wagner w...@cyconet.org wrote:
Okay ... I was talking here about pu in general, not php specific.
As I understand from some d-d discussion, we could be a little bit more
aggressive with pu now.
Okay ... we should have had talked a bit much more about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ondřej,
Am 04.06.13 16:32, schrieb Ondřej Surý:
Okay ... we should have had talked a bit much more about this
topic. With suhosin abounded upstream, I didn't follow your
packaging very close, so I wasn't aware of the issue (as the change
was
On Tue, Jun 4, 2013 at 4:57 PM, Jan Wagner w...@cyconet.org wrote:
Maybe you could with the next upload to wheezy include a versioned
Break against php5-suhosin (=0.9.33-3), which doesn't hurt anyone
but give us the option to get a php5-suhosin installed on wheezy
afterwards?
Definitely not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 04.06.13 17:26, schrieb Ondřej Surý:
On Tue, Jun 4, 2013 at 4:57 PM, Jan Wagner w...@cyconet.org
mailto:w...@cyconet.org wrote:
Maybe you could with the next upload to wheezy include a versioned
Break against php5-suhosin (=0.9.33-3), which
Package: php5-suhosin
Version: 0.9.33-3
Severity: normal
Dear Maintainer,
the package conflicts with php5-common 5.4.4-11 (the last of sid)
but in aptitude the phpapi-20100525 (requests by php-suhosin)
seems provided by php5-cgi 5.4.4-11 (for example).
-- System Information:
Debian Release:
Hi Stefano,
On Fri, 2012-12-21 at 10:00 +0100, stefano wrote:
the package conflicts with php5-common 5.4.4-11 (the last of sid)
but in aptitude the phpapi-20100525 (requests by php-suhosin)
seems provided by php5-cgi 5.4.4-11 (for example).
It is known and intentional. As php5-suhosin
11 matches
Mail list logo
