Hi all,
I spent a half-day hacking cyrus-sasl2 and I uploaded 2.1.27 to experimental. I
would appreciate if more people can test the package (I won’t have time until
tomorrow or next week). I didn’t even had a chance to test it myself, so even
the basic it installs and nothing breaks horribly w
That seems overly complicated for a little gain. dns-root-data has the current
root key and keeps it up-to-date for all DNS related packages.
--
Ondřej Surý
> On 20 Jan 2019, at 21:38, Simon Deziel wrote:
>
> Inspired by discussions on the unbound-users list [1] and what other
> distros (SLES
No harm doing was intended. I simply missed the NMU.
If you can point me to the direction of the patches you prepared I will try to
care of it before soft freeze.
Ondrej
--
Ondřej Surý
> On 25 Dec 2018, at 11:58, Helmut Grohne wrote:
>
> Hi Ryan,
>
>> On Mon, Dec 24, 2018 at 03:48:19PM -080
In that case, I would advise you to fill a bug directly with upstream
developers at bugs.php.net.
I can do it for you, but usually it’s better if the person affect education by
the bug do the filling for more swift communication.
Please report the PHP bug number back here.
Ondřej
--
Ondřej Su
Oh, so thought I already uploaded it, but I hadn’t. So, I did it just now.
Thanks!
--
Ondřej Surý
> On 14 Nov 2018, at 15:47, Felipe Sateler wrote:
>
> Hi Ondrej,
>
> On Wed, Nov 14, 2018 at 11:42 AM Ondřej Surý wrote:
>>> The previous fix was not a real fix, it only rebuilt the package i
> The previous fix was not a real fix, it only rebuilt the package in a
> non-merged environment.
Umm, what?
https://salsa.debian.org/php-team/php/blob/master-7.3/debian/patches/0048-Don-t-use-sed-found-by-configure-use-the-sed-command.patch
--
Ondřej Surý
> On 14 Nov 2018, at 14:42, Felipe
Paul,
thank you for all the effort you have put into this. I understand and
appreciate the effort.
I am basically not objecting to whatever solution there will be, it is
ultimately that package maintainer’s decision, and I am sorry I can’t be more
helpful, but my free time is limited and all I
The versioned depends is needed only for autopkgtests and not for the package
itself. So, I think the dependency is useless there.
Ondrej
--
Ondřej Surý
> On 9 Nov 2018, at 10:37, Paul Gevers wrote:
>
> Hi,
>
> Hmm, I should read my backlog before replying.
>
>> On 08-11-18 22:53, Ondřej Su
PHP 7.2 had been removed from Debian unstable and it will go from testing as
soon as the transition is complete.
NextCloud is not available from Debian, but generally speaking, if you want a
stable distribution then you need to use Debian stable.
Ondrej
--
Ondřej Surý
> On 31 Oct 2018, at 17:
Also libtidy5deb1 doesn’t have libtidy.so, just libtidy.so.5deb1 and
libtidy.so.5deb1.0.0. It worked before because there was fallback to
libtidy.so.5 in LIBNAMES. But now instead of whacking the new SONAME into the
package every time it changes, you should solve it once and forever to resolve
That way the package would be binNMUable
--
Ondřej Surý
> On 26 Oct 2018, at 13:49, Michal Čihař wrote:
>
> Hi
>
>> On Fri, 2018-10-26 at 10:51 +0200, Ondřej Surý wrote:
>> LIBTIDY_LIBRARY=$(shell readlink -f
>> /usr/lib/$(DEB_HOST_MULTIARCH)/libtidy.so)
>
> Well it all started from this fil
libtidy-dev will go to B-D
--
Ondřej Surý
> On 26 Oct 2018, at 13:49, Michal Čihař wrote:
>
> Hi
>
>> On Fri, 2018-10-26 at 10:51 +0200, Ondřej Surý wrote:
>> LIBTIDY_LIBRARY=$(shell readlink -f
>> /usr/lib/$(DEB_HOST_MULTIARCH)/libtidy.so)
>
> Well it all started from this file being absent
PHP 7.0 and 7.1 has been already removed and PHP 7.2 is next to be removed.
--
Ondřej Surý
> On 23 Oct 2018, at 11:08, Bjoern Schiessle wrote:
>
> Package: php-xdebug
> Version: 2.7.0
>
> The current php-xdebug package in sid only contains xdebug for PHP 7.3
> while Debian sid still comes wit
Thanks! All look good now.
Now, if you can bump php-defaults, so it migrates earlier and kick kopanocore
and php-mailparse from testing, and we could remove php7.2 from the archive and
be done with this transition.
Thank you,
Ondřej
--
Ondřej Surý
> On 20 Oct 2018, at 12:58, Emilio Pozuelo Mo
Control: notfound -1 2.1.27~rc8-1.1
Control: close -1
Hi,
while looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911481 I
have a suggestion, what if you double check your system and its configuration
before you go on a spree filling RC bugs that looks awfully similar?
Your system i
nce
> Debian wants to provide?
>
>> On 2018-10-06 06:34, OndÅej Surý wrote:
>> Control: severity -1 important
>> That’s not a grave bug. Please do not abuse severities.
>> Ondřej
>> --
>> Ondřej Surý
>>> On 6 Oct 2018, at 01:23, Piotr
Control: severity -1 important
That’s not a grave bug. Please do not abuse severities.
Ondřej
--
Ondřej Surý
> On 6 Oct 2018, at 01:23, Piotr Jurkiewicz
> wrote:
>
> Package: php7.3-mysql
> Version: 7.3.0~rc2-2
> Severity: grave
>
> After update to 7.3.0~rc2-2 (sid), mysqli extension stopp
I don’t see how php-memcache can be at fault. It’s more likely the DOM
extension isn’t loaded.
Ondřej
--
Ondřej Surý
> On 4 Oct 2018, at 09:54, Paul Gevers wrote:
>
> Source: php-memcache, php-doctrine-cache-bundle
> Control: found -1 php-memcache/3.0.9~20170802.e702b5f-1
> Control: found -1
No, mcrypt is deprecated and dangerous to use. It was removed for reason.
The software using mcrypt must be fixed, not the other way around.
Ondrej
--
Ondřej Surý
> On 20 Sep 2018, at 01:23, Nikolai Lusan wrote:
>
> Package: php-mcrypt
> Version: 1:7.0+57
> Followup-For: Bug #893481
>
> Sinc
That usually happens when fpm isn’t compiled with systemd. Can you please check
the binary with ldd?
--
Ondřej Surý
> On 19 Aug 2018, at 20:02, Olaf van der Spek wrote:
>
> Package: php7.2-fpm
> Version: 7.2.9-1
> Severity: normal
>
> Hi,
>
> Not sure why, 7.0 start just fine, can't find an
It would be an easy thing if I get a ack from backports masters, but I am not
going ask them again.
Ondřej
--
Ondřej Surý
> On 19 Aug 2018, at 18:31, Olaf van der Spek wrote:
>
> Hi,
>
> I'd love to see a backport as well.
>
> --
> Olaf
>
Control: severity -1 wishlist
Control: tags -1 +wontfix
Closing as rant.
If somebody actually provides a build profile, we might actually consider using
it if it doesn’t complicate things too much.
Ondřej
--
Ondřej Surý
> On 25 Feb 2018, at 11:57, lkcl wrote:
>
> Package: mariadb-server
> S
Thanks for understanding. If you are to switch to embedded botan 1.10 before
upstream sorts this out, you probably ought to upgrade the embedded version to
latest upstream (1.10.17).
I think Christian has already filled RM bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889675
Ondřej
-
Control: tags -1 +wheezy
You should probably contact the Debian LTS team as it affects wheezy that’s
maintained by LTS Team.
Ondrej
--
Ondřej Surý
> On 3 Feb 2018, at 11:12, Vladislav Kurz wrote:
>
> Package: bind9
> Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> Severity: grave
> Tags: security
Control: tags -1 +wontfix
Hi,
seccomp is broken as it needs to be constantly updated to match the running
kernel, so upstream is also going to remove seccomp support for subsequent
releases. Henceforth it makes no sense to enable it, there are better
mechanisms to protect the system. Also ther
25 matches
Mail list logo