On Thu, Sep 21, 2017 at 04:26:53PM +0100, Rodrigo Campos wrote:
> On Thu, Sep 21, 2017 at 09:54:49AM +0200, Ángel wrote:
> > Salvatore wrote:
> > > have you identified already the issue -> fixing commit mappings?
> >
> > For version 4.8.1 [buster, sid], upstr
On Thu, Sep 21, 2017 at 09:54:49AM +0200, Ángel wrote:
> Salvatore wrote:
> > have you identified already the issue -> fixing commit mappings?
>
> For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2
> https://codex.wordpress.org/Version_4.8.2
And for jessie backports I'll update as
Hi,
Just in case you weren't aware, several security issues has been fixed in flash.
Here is the last batch of fixes that I know of:
https://blog.qualys.com/laws-of-vulnerabilities/2017/05/09/adobe-fixes-half-dozen-flash-vulnerabilities-and-more
These is, of course, not fixed in debian because
On Wed, May 17, 2017 at 09:54:55PM +1000, Craig Small wrote:
> Source: wordpress
> Version: 4.7.4+dfsg-1
> Severity: grave
> Tags: upstream security
> Justification: user security hole
>
> Wordpress 4.7.4 and earlier has 6 security holes that are fixed in
> 4.7.5[1]
>
> * 2.7.0 - 4.7.4
>
On Wed, Sep 16, 2015 at 06:47:04PM +0200, Salvatore Bonaccorso wrote:
> Hi,
>
> On Wed, Sep 16, 2015 at 10:54:27AM +0200, Salvatore Bonaccorso wrote:
> > See https://wordpress.org/news/2015/09/wordpress-4-3-1/ for details. I
> > have not checked older versions in jessie and wheezy. Are they
Not
On Sat, Jun 13, 2015 at 07:24:15AM +, Gianfranco Costamagna wrote:
Control: severity -1 grave
Control: found -1 1.5.0~rc1-2
Control: fixed -1 1.5.2-1
thanks
I'm setting the correct severity, since the jessie package is completely
unusable.
Well, it's not completely unusable. It
On Tue, Jun 16, 2015 at 10:12:03AM -0500, Matt Domsch wrote:
Buckets with dots is the AWS recommended method, and is required for all
regions except for us-east-1. It becomes usable if you use
Ohh, didn't know that. Then I fully agree =)
Thanks a lot,
Rodrigo
--
To UNSUBSCRIBE, email to
On Wed, Dec 03, 2014 at 05:58:11PM +1100, Craig Small wrote:
On Tue, Dec 02, 2014 at 02:17:37PM +, Rodrigo Campos wrote:
The upstream release was on Nov 20, it's been almost 2 weeks and the bug
seem
kind of serious. Any chance to do a quick fix and then continue to discuss
changing
Hi,
The upstream release was on Nov 20, it's been almost 2 weeks and the bug seem
kind of serious. Any chance to do a quick fix and then continue to discuss
changing wordpress version in stable ? Or any ETA on when the fixes will come to
stable ?
I've manually applied the workaround suggested
On Tue, Nov 05, 2013 at 12:10:35AM +0100, Francesco Poli wrote:
On Mon, 4 Nov 2013 13:01:22 +0100 Vincent Lefevre wrote:
On 2013-11-01 12:58:19 +0100, Francesco Poli (wintermute) wrote:
I wonder why nobody thought to report a release-critical bug against
libfontconfig1, in order to
Hi,
Besides is probably pretty clear from the bug report, I add this information
just in case is useful for someone else.
Downgrading the library to the previous version on testing makes xpdf work
again. I did this by adding:
deb
Hi,
I have, like Stefan Beller, a 32-bit system with fluxbox started by gdm too and
hit the very same problem he describe. What did work for me was removing phonon,
like this:
aptitude purge phonon phonon-backend-xine
(I did have phonon installed, not phonon-backend-vlc)
This removed
On Sat, Jul 07, 2012 at 03:54:43PM -0300, Rodrigo Campos wrote:
Hi,
I have, like Stefan Beller, a 32-bit system with fluxbox started by gdm too
and
hit the very same problem he describe. What did work for me was removing
phonon,
like this:
aptitude purge phonon phonon-backend
On Mon, Aug 31, 2009 at 12:34:01PM +0200, Sebastian Harl wrote:
The problem is an error in the build system. collectd ships its own
version of libiptc (which is used by the iptables plugin) because this
library used to be available as a static lib only (which cannot be
linked into a shared
On Mon, Aug 31, 2009 at 03:36:28PM +0200, Sebastian Harl wrote:
Hi,
On Mon, Aug 31, 2009 at 09:22:49AM -0300, Rodrigo Campos wrote:
On Mon, Aug 31, 2009 at 12:34:01PM +0200, Sebastian Harl wrote:
The problem is an error in the build system. collectd ships its own
version of libiptc
On Mon, Aug 31, 2009 at 09:55:52PM +0200, Sebastian Harl wrote:
Hi Rodrigo,
On Mon, Aug 31, 2009 at 04:27:42PM -0300, Rodrigo Campos wrote:
On Mon, Aug 31, 2009 at 03:36:28PM +0200, Sebastian Harl wrote:
On Mon, Aug 31, 2009 at 09:22:49AM -0300, Rodrigo Campos wrote:
It seems
Package: linux-image-2.6.18-5-686
Version: 2.6.18.dfsg.1-13
Severity: grave
Justification: renders package unusable
Hi, the other day i upgrade from lastest linux-image-2.6.18-4-686 to
linux-image-2.6.18-5-686 from proposed-updates and all seems to be ok.
But yesterday after i power it on, i
Tags 05 + patch
Thanks
--- config 2006-08-29 18:50:07.0 -0300
+++ rata.config 2006-08-29 18:52:18.0 -0300
@@ -120,7 +120,7 @@
if [ $INSTALL_STAT = installed ]; then
if [ -x /etc/init.d/thttpd ]; then
-/etc/init.d/thttpd stop 12 /dev/null || true
+
Tags 381122 + patch
Thanks
The attached patch replace the $RANDOM and let bash internal functions
using external commands in coreutils.
--- debian/cron.daily 2006-06-16 11:05:37.0 -0300
+++ debian/rata.daily 2006-08-04 11:17:18.0 -0300
@@ -1,9 +1,9 @@
#!/bin/sh
RANGE=3600
Tags 381167 + patch
Thanks
--- debian/postfix.preinst 2006-08-03 11:08:09.0 -0300
+++ debian/rata.preinst 2006-08-03 11:21:23.0 -0300
@@ -254,9 +254,7 @@
tlsmgr_warning
fi
- if [ ! start-stop-daemon -K -q -o \
- --pidfile /var/spool/postfix/pid/master.pid \
- --exec
20 matches
Mail list logo
