This is a far long outstanding issue indeed.
Well, one way could be to build the %sizeof hash through a C program. We
are doing that for us.
For instance:
https://github.com/i-MSCP/imscp/tree/hotfixes/engine/PerlLib/h2ph
--
Laurent Declercq
iHMS/i-MSCP CEO & Lead Developer
Message transféré
Sujet : Debian opendkim package -- #864162
Date : Wed, 11 Oct 2017 12:17:25 +0200
De :Declercq Laurent <l.decle...@nuxwin.com>
Organisation : iHMS/i-MSCP
Pour : sc...@kitterman.com
Good morning,
I would attire your attention on the c
I've already reported the issue to upstream author.
See https://github.com/netblue30/firejail/issues/704
--
Laurent Declercq
iHMS/i-MSCP Project Director
can still reproduce the problem with Jessie (8.3)
How to reproduce?
1. Login as usually (gnome)
2. Open gedit editor
3. Close gedit editor
Once you do that, dconf automatically recreate the
/run/user/1000/dconf/user file with root:root as owner/group and the
following error is raised:
Jan
Le 06/01/2016 17:14, Felipe Sateler a écrit :
Package: libapache2-mod-php5
Version: 5.6.16+dfsg-4
Severity: important
Hi,
I've noticed that now php7 and php5 are now coinstallable. However, upon
install apache2 dumps core:
Message: Process 12966 (apache2) of user 0 dumped core.
Such situation should be resolved with a conflict or in the same way MPM
are managed.
E.g. if you enable one module, other is automatically disabled.
--
Laurent Declercq
iHMS/i-MSCP Project Director
Le 05/01/2016 13:48, 積丹尼 Dan Jacobson a écrit :
"OS" == Ondřej Surý writes:
OS> Control: severity -1 minor
OS> Control: tags -1 +wontfix experimental
OS> That's intentional to keep old configuration files in place to allow
OS> local administrator to upgrade the configuration
Hello,
Just to say that this bug is also affecting Debian Jessie servers
(pop3/imap SSL courier servers). For instance, with the default
dhparams.pem file, they are unable to connect to the server from Outlook
2013. The solution is same: Regenerating the dhparams.pem file.
See:
This bug is still present in Bind9 package that is provided in Jessie...
Two things:
- That would be awesome if that bug could be fixed (even for Jessie)
since it breaks systems which rely on resolvconf to setup their local
resolver.
- This service is not enabled by default, whatever the
Hello ;
After some investigation, it appears that the problem occurs when a
sysvinit script for the same service is also installed in the
/etc/init.d directory. It seem that LSB headers (required-*) are in
conflict with the upstart job stanza (start on and stop on). For
instance, if I run
Package: sysvinit-utils
Version: 2.88dsf-41+deb7u1
Severity: important
Dear maintainer ;
For our project, I've created an upstart job which is responsible to
start our service once the MySQL server is running.
This script must work whatever the MySQL server is started by an upstart
job or
Duplicate of #763030 due to mailer issue.
This report can be closed. I've read the documentation again and in
fact, it's not mentionned that files are copied automatically. They have
to be listed in the forceCopy option.
--
Laurent Declercq
iHMS/i-MSCP Project Lead
--
To UNSUBSCRIBE, email
This report can be closed. I've read the dco again and in fact, it's not
mentionned that files are copied automatically. They have to be listed
in the forceCopy option.
Sorry for this false report.
--
Laurent Declercq
iHMS/i-MSCP Project Lead
--
To UNSUBSCRIBE, email to
Hello ;
First, sorry for my previous report.. It was too much sarcastic for you
as I see.
Well, I can provide you a patch for all the bugs linked here. It's not a
problem for me since we are using our own vlogger version for our
control panel. Therefor, I would be happy to help as long you
A typo error has been inserted in my report.
The right piece of code is:
##
sub execute($;$$)
{
my ($command, $stdout, $stderr) = @_;
fatal('$stdout must be a scalar reference') if $stdout ref
$stdout ne 'SCALAR';
fatal('$stderr must be a scalar reference') if $stderr ref
Le 20/10/2011 14:52, Stefano Rivera a écrit :
Hi Laurent (2011.10.20_08:18:34_+0200)
BTW, you don't have to use reportbug to reply to this bug, you can just
reply to the e-mail. As long as a copy goes to 645...@bugs.debian.org,
it will be added to the bug page.
Sure, It's what I've tried
16 matches
Mail list logo