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
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
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
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
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
Control: severity -1 normal
Interesting self-reflection, yes, stop trolling, Thorsten. Your initial bug
report was inappropriate.
It is _absolutely_ job of the security library to set the system-wide security
policies.
In fact, Debian should have a system-wide policy that would be inherited in
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
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
13 matches
Mail list logo
