st regards,
Lars
On Sat, 2023-11-11 at 10:30 -0600, Gunnar Wolf wrote:
> I am adding a Recommends: on zerofree and will soon upload (and close
> thus bug). Michael: I understand your point, but given this is a
> design decision from our upstream author, I prefer adding a Cc: to
> Lars and ask him
Hi,
upstream fixed with release 1.14.1
With Best Regards,
Lars Windolf
-2424 CVE-2021-2425 CVE-2021-2426
- CVE-2021-2427 CVE-2021-2429 CVE-2021-2437 CVE-2021-2440
- CVE-2021-2441 CVE-2021-2444 CVE-2021-22901
Ref: https://www.oracle.com/security-alerts/cpujul2021.html#AppendixMSQL
Regards,
Lars Tangvald
Regards,
Lars Tangvald
-2060 CVE-2021-2061 CVE-2021-2065 CVE-2021-2070
- CVE-2021-2072 CVE-2021-2076 CVE-2021-2081 CVE-2021-2088
- CVE-2021-2122
Ref: https://www.oracle.com/security-alerts/cpujan2021.html#AppendixMSQL
Regards,
Lars Tangvald
-2020-14870 CVE-2020-14873 CVE-2020-14878
- CVE-2020-14888 CVE-2020-14891 CVE-2020-14893
Ref: https://www.oracle.com/security-alerts/cpuoct2020.html#AppendixMSQL
Regards,
Lars Tangvald
Thanks. I'm waiting for maintainer access to the source package, and I
should be able to finally get all these closed.
--
Lars
On 28.01.2020 08:20, Salvatore Bonaccorso wrote:
Source: mysql-5.7
Version: 5.7.26-1
Severity: grave
Tags: security upstream
Justification: user security hol
On Thu, 2019-11-28 at 10:40 -0600, Gunnar Wolf wrote:
> Lars Wirzenius dijo [Thu, Nov 28, 2019 at 11:27:54AM +0200]:
> > Thanks, I've applied the changes and pushed them to git.liw.fi and
> > gitlab.
>
> Thanks for your prompt attention, Lars!
>
> I am about t
Thanks, I've applied the changes and pushed them to git.liw.fi and
gitlab.
On Mon, Nov 25, 2019 at 03:27:31PM -0300, Antonio Terceiro wrote:
> Hello,
>
> The following patch drops the remaining usage of python2 in vmdb2, in
> the build system and test suite.
>
> Gunnar: I just uploaded a cmdtest
ther applying it helps.
/Lars
(the idea was to get me DM access so I could handle these updates more
completely, but that process got shifted to the backlog), but should
hopefully get a better routine going soon.
--
Lars
On 16.10.2019 15:44, Salvatore Bonaccorso wrote:
Source: mysql-5.7
Version: 5.7.26-1
Severity: grave
bug or on the
respective GitHub issues. There is a new itstool version available,
but it only includes the fixes that we've had available as long as this
bug has been open.
Best regards,
Lars
On Wed, 2019-03-06 at 12:39 +0200, Jonathan Carter wrote:
> Hi Lars, I promise that we will stop using vmdebootstap as soon as
> humanly possible after buster. I'm just not sure it's safely and
> reasonably possible before then.
Good. If I get betterer, I may be able to hel
On Wed, Mar 06, 2019 at 06:33:00AM +, Niels Thykier wrote:
> I am sorry to hear that you are sad by this. To be honest, I had
> expected you were informed about this already.
>
> This was requested in #922826 with the argument that our live image
> builds no longer worked and that it was too
On Tue, Mar 05, 2019 at 07:24:03PM +, Debian Bug Tracking System wrote:
> Added tag(s) bullseye and sid.
Does this mean buster is going to be released with vmdebootstrap? This
would make me sad. Why is this? I'm not going to spend any time to fix
vmdebootstrap. I'd really rather nobody else di
Redhat now have this bug in their bug tracker. Given that the itstool author
seems to
either be or have been a Redhat employee at some point, I guess this is good.
https://bugzilla.redhat.com/show_bug.cgi?id=1677838
> What precisely do you mean by "not applied"? Does typing into Firefox
> and GTK2 apps behave as though you were using a USA keyboard
> (shift+2 -> @, shift+3 -> #, etc.) or does it have some other
> behaviour?
In native GNOME applications, pressing the key that normally gives
me "-" (dash) give
t; value specified above.
Maybe upstream moved that directory somewhere else or removed it completely?
Cheers,
Lars
BTW, the pull request at https://github.com/itstool/itstool/pull/18 looks
interesting.
A quick test of the copyNode fix therein seems to at least allow itstool to
complete
(in a loop that ran 100 times). It may not apply cleanly any longer, haven't
tried.
/Lars
this bug to itstool?
/Lars
Hmm, moving the files out of the original directory structure and trying from
there works.
This gets weirder and weirder.
in itstool. So then the question becomes,
what is this? an error
in the input data (that shouldn't cause a crash of course), in itstool, in
libxml2 or what?
I've also opened an itstool issue on GitHub, containing my most recent findings:
https://github.com/itstool/itstool/issues/36
/Lars
oaded.
--
Lars
On 19.01.2019 22:14, Salvatore Bonaccorso wrote:
Source: mysql-5.7
Version: 5.7.24-3
Severity: grave
Tags: security upstream
Justification: user security hole
Hi
Details at
https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#AppendixMSQL
Regards,
Salv
Control: tags -1 +pending
Hello Andreas,
thank you for your report.
I prepared a fix for the issue.
@Holger: please take a look at the commit (6d4791c9) in my repository on salsa
[1] and merge it, if it looks good for you.
Cheers,
Lars
[1] g...@salsa.debian.org:sumpfralle-guest/munin.git
On Tue, Oct 23, 2018 at 04:51:39PM +0200, Helmut Grohne wrote:
> Source: vmdb2
> Version: 0.13.2-1
> Severity: serious
> Tags: ftbfs
>
> vmdb2 fails to build from source in unstable for multiple architectures,
> e.g. amd64:
Noting this for whoever looks at this again: the problem is that new
vers
Hi
5.7.24 has been released now. I'll prepare the upload for unstable.
--
Lars
On 17. okt. 2018 11:11, Salvatore Bonaccorso wrote:
Source: mysql-5.7
Version: 5.7.23-2
Severity: grave
Tags: security upstream
Hi
Details at
https://www.oracle.com/technetwork/security-advisory/cpuoc
I've uploaded a version that should fix this.
On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote:
> On Thu, 05 Jul 2018 17:35:30 +0300 Lars Wirzenius wrote:
> > On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote:
> > > But the upgrade path fr
On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote:
> Do you have an ETA on the upload fixing cliapp? At the moment, cliapp
> is a key package and as such a potential blocker for the new Debian release.
Key pacakge? I did not know that. What makes cliapp a key package?
I'll try to get this f
Correction: This should be for 5.7.22, I think.
CVE List:
CVE-2018-0739
CVE-2018-2767
CVE-2018-3054
CVE-2018-3056
CVE-2018-3058
CVE-2018-3060
CVE-2018-3061
CVE-2018-3062
CVE-2018-3064
CVE-2018-3065
CVE-2018-3066
CVE-2018-3070
CVE-2018-3071
CVE-2018-3077
CVE-2018-3081
--
Lars
On 07/20/2018 06
Also note 5.7.23 has not yet been released (it will be out by the end of
the month).
--
Lars
On 07/20/2018 07:34 AM, Lars Tangvald wrote:
Correction: This should be for 5.7.22, I think.
CVE List:
CVE-2018-0739
CVE-2018-2767
CVE-2018-3054
CVE-2018-3056
CVE-2018-3058
CVE-2018-3060
CVE-2018
On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote:
> But the upgrade path from stretch is not clean:
>
> Selecting previously unselected package python3-cliapp.
> Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
> Unpacking python3-cliapp (1.20170827-1) ...
> dpkg: e
On Wed, Jul 04, 2018 at 06:34:41PM +0300, Lars Wirzenius wrote:
> (Also, the advice to use Replaces+Breaks is just wrong for this
> package. The bug is that the same file is in both the python2 and
> python3 versions of the package. The correct solution is to have it in
> at most on
On Wed, Sep 06, 2017 at 12:31:19AM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails
> because it tries to overwrite other packages files without declaring a
> B
Hi,
We'll prepare the update once 5.7.22 has been released (the release is
almost always before the advisory, but not this time).
--
Lars
On 04/18/2018 03:00 PM, Salvatore Bonaccorso wrote:
Source: mysql-5.7
Version: 5.7.21-1
Severity: grave
Tags: security upstream
Hi
Detail at
On Monday, 9 April 2018 12:56:12 CEST Lars Kollstedt wrote:
[...]
> This patch should IMHO work, but I have no opportunity to test it without
> your help, since we're in udeb and testing preseed issues. ;-)
Hi again,
20 times looked at it and still overlooked one detail.
This must o
I'm also trying to assign a useful name to the key added this way.
This patch should IMHO work, but I have no opportunity to test it without your
help, since we're in udeb and testing preseed issues. ;-)
Kind regards,
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail:
On Fri, 2018-02-16 at 23:19 +0100, Benjamin Drung wrote:
> Standard error from shell command:
> Traceback (most recent call last):
> File "/tmp/tmpWTVTHk", line 7, in
> from yarnutils import *
> ImportError: No module named yarnutils
I seem to have failed to upload to Debian
only delete its own data.
--
Lars
On 10/19/2017 10:09 AM, Emilio Pozuelo Monfort wrote:
On 18/10/17 20:46, Salvatore Bonaccorso wrote:
Hi lars,
On Wed, Oct 18, 2017 at 03:51:26PM +0200, Lars Tangvald wrote:
Hi,
5.5.58 packages for Debian 7 and 8 are built, and pass the test suite.
Attached are debdiff files for Wheezy and
-10379
CVE-2017-10384
--
Lars
On 13. okt. 2017 12:34, Norvald H. Ryeng wrote:
Source: mysql-5.7
Version: 5.7.18-1
Severity: grave
Tags: security upstream fixed-upstream
The Oracle Critical Patch Update for October 2017 will be released on
Tuesday, October 17. According to the pre-release
CVE List for 5.5:
CVE-2017-10268
CVE-2017-10378
CVE-2017-10379
CVE-2017-10384
--
Lars
On 13. okt. 2017 12:34, Norvald H. Ryeng wrote:
Source: mysql-5.5
Version: 5.5.57-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream
The Oracle Critical Patch Update for October 2017 will be
king the history of the file /usr/share/man/man5/munin.conf.5.gz as
an example:
* stretch/buster/sid: part of "munin-doc"
* experimental: part of "munin"
Andreas' log indicated the same conflict / transition from
"munin-plugins-extra" to "munin".
CVE list for 5.5:
CVE-2017-3635
CVE-2017-3636
CVE-2017-3641
CVE-2017-3648
CVE-2017-3651
CVE-2017-3652
CVE-2017-3653
--
Lars
-3652
CVE-2017-3653
CVE-2017-3732
--
Lars
update the bug with CVE numbers when they become available, and
test the update to ensure there are no packaging issues that need
addressing.
Regards,
Lars Tangvald
[1]
http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
will update the bug with CVE numbers when they become available, and
test the update to ensure there are no packaging issues that need
addressing.
Regards,
Lars Tangvald
[1]
http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
On 04/24/2017 10:27 AM, Salvatore Bonaccorso wrote:
Hi Lars,
On Mon, Apr 24, 2017 at 07:59:36AM +0200, Lars Tangvald wrote:
On 04/21/2017 08:04 AM, Salvatore Bonaccorso wrote:
Hi Lars,
On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote:
Hi,
I lost internet connectivity where
On 04/21/2017 08:04 AM, Salvatore Bonaccorso wrote:
Hi Lars,
On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote:
Hi,
I lost internet connectivity where I am right now, so probably unable to get
this done until Monday. Could maybe use the previous debdiff for Jessie if
you'
oad access for 5.5
--
Lars
On 19. april 2017 15:30, Salvatore Bonaccorso wrote:
Hi Lars,
On Wed, Apr 19, 2017 at 04:26:30AM -0700, Lars Tangvald wrote:
Hi,
We've prepared and tested the update to MySQL 5.5.55 for Jessie.
Debdiff output is attached.
Only packaging changes are one refreshe
Hi,
- car...@debian.org wrote:
> Hi Lars,
>
> On Wed, Apr 19, 2017 at 04:26:30AM -0700, Lars Tangvald wrote:
> > Hi,
> >
> >
> > We've prepared and tested the update to MySQL 5.5.55 for Jessie.
> > Debdiff output is attached.
> > Only pack
Whoops, that went to the wrong address...
Message just says that a patch added by the lts team to 5.5.54 doesn't apply on
5.5.55 :)
--
Lars
- lars.tangv...@oracle.com wrote:
> Hei,
>
> Denne patchen:
> https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/tr
Hei,
Denne patchen:
https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/tree/debian/patches/fix_use_after_free_in_mysql_prune_stmt_list.patch?h=debian/wheezy
Ble lagt til (kun debian 7) for 5.5.54, og får konflikt i 5.5.55. Har du tid
til å ta en titt og evt. lage oppdatert patch?
--
Lars
CVE-2017-3599
CVE-2017-3600
--
Lars
CVE list for 5.5:
CVE-2017-3302
CVE-2017-3305
CVE-2017-3308
CVE-2017-3309
CVE-2017-3329
CVE-2017-3453
CVE-2017-3456
CVE-2017-3461
CVE-2017-3462
CVE-2017-3463
CVE-2017-3464
CVE-2017-3600
--
Lars
ome errors in syslog or
/var/log/mysql ?
When I did a quick test, I just replaced jessie with stretch in
/etc/apt/sources.list, ran apt-get update and apt-get dist-upgrade
--
Lars
___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debia
On 03/15/2017 07:25 AM, Gabriel Filion wrote:
Lars Tangvald:
- gabs...@lelutin.ca wrote:
Ugh, I fail at reportbug again :(
real sorry about the initial report.
here's the real description of the problem:
when upgrading from jessie to stretch, the upgrade goes through
witho
. are named so because there isn't a better
term for "mysql-ish"). While the current situation with mysql being
half-uninstalled is pretty odd, we shouldn't automatically replace mysql-server
with mariadb-server, as it can cause problems for users who want to keep using
mysql, while those who are fine with either just need to install mariadb after
the upgrade.
--
Lars
On 02/21/2017 01:59 PM, Julian Gilbey wrote:
On Tue, Feb 21, 2017 at 01:27:44PM +0100, Lars Tangvald wrote:
I've looked at it some more, and I'm hesitant about including such a big
patch for a pretty rare scenario, which in the worst case does ask the
following:
The /var/lib/mysql
I just want to hint on a workaround for this bug by running:
debsecan --config <(echo
SOURCE="https://security-tracker.debian.org/tracker/debsecan/release/1/";)
Tested to run fine on Squeeze, Wheezy and Jessie.
Cheers,
Lars
Thanks for the bug report, and for doing rebuild tests.
On Sat, Jan 28, 2017 at 09:27:24AM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > fi
> > * Module cliapp.app
> > C:346,3
>
> It's been tested for upgrades, clean install, remove and purge.
>
> Best wishes,
>
>Julian
Thanks!
I'll look it over and test a little myself.
--
Lars
On 01/30/2017 10:28 AM, Robie Basak wrote:
Hi Julian,
Thank you for reporting this.
On Mon, Jan 30, 2017 at 09:24:46AM +0100, Lars Tangvald wrote:
Anyone else have any good ideas on how to handle this?
I think the root cause here is that both MySQL and MariaDB packaging
"own"
so that it would run
correctly after the package's own binary is removed, but that's
-server-core, which doesn't run any postrm (we could add it, but part of
the point of the core packages is that they don't run anything).
Anyone else have any good ideas on how to handle
- car...@debian.org wrote:
> Hi Lars,
>
> On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> >
> > - car...@debian.org wrote:
> >
> >
> > > > >With that fixed, and build with -sa (to include the orig
> tarball)
> >
> yes it nees to be a key in the DD keyring. Do you have a DD in the
> mysql-pkg team who could sponsor the upload?
>
Not really, unfortunately (Otto is a DD, but he's only involved with the
MariaDB packaging).
It's an issue for us, since it also causes problems with uploads to unstable.
--
Lars
Hi,
On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:
Hi Lars,
On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
Hi,
The update builds and passes testing.
I've attached debdiff output for Wheezy and Jessie for this update. Aside
from the changelog, the only change to pack
CVE List for 5.5:
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318
--
Lars
On 01/13/2017 09:19 AM, Norvald H. Ryeng wrote:
Source: mysql-5.5
Version: 5.5.53-0+deb8u1
Severity: grave
Tags: security
CVE List for 5.6:
CVE-2016-8318
CVE-2016-8327
CVE-2017-3238
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3273
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318
--
Lars
On 01/17/2017 09:48 PM, Lars Tangvald wrote:
I've built and tested the update
CVE List for 5.7:
CVE-2016-8318
CVE-2016-8327
CVE-2017-3238
CVE-2017-3244
CVE-2017-3251
CVE-2017-3256
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3273
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318
CVE-2017-3319
CVE-2017-3320
--
Lars
On 01/17/2017 09:48 PM, Lars
I've built and tested the updates, and will pass debdiffs on to the security
team once the CVE list is available.
--
Lars
- norvald.ry...@oracle.com wrote:
> Source: mysql-5.7
> Version: 5.7.16-2
> Severity: grave
> Tags: security upstream fixed-upstream
>
> Th
I've built and tested the updates, and will pass debdiffs on to the security
team once the CVE list is available.
--
Lars
- norvald.ry...@oracle.com wrote:
> Source: mysql-5.5
> Version: 5.5.53-0+deb8u1
> Severity: grave
> Tags: security upstream fixed-upstream
>
&
I've built and tested the update, and will pass debdiffs on to the security
team once the CVE list is available.
--
Lars
- norvald.ry...@oracle.com wrote:
> Source: mysql-5.6
> Version: 5.6.34-1
> Severity: grave
> Tags: security upstream fixed-upstream
>
> The Oracl
5.7 has a fix for this in place (editline uses a different datatype in newer
versions). At first glance it looks like it should be simple to apply the same
fix for 5.6.
--
Lars
- a...@debian.org wrote:
> Source: mysql-5.6
> Version: 5.6.34-1
> Severity: serious
> Justificati
chroot by default.
--
Lars
ibmysqlclient_r, as the latter was only included for backwards
compatibility.
I can do some digging to find out exactly when _r was made a symlink.
--
Lars
mysql/mysql.git
--
Lars
On 11/14/2016 12:39 AM, Michael Biebl wrote:
Package: libmysqlclient-dev
Version: 5.7.16-1
Severity: serious
File: /usr/bin/mysql_config
Hi,
I just tried to build the rsyslog package, which resulted in a build
failure:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I.
ken pipe)
Thanks. As you say, it looks like we're missing a breaks/replaces on the
server-core package.
--
Lars
cheers,
Andreas
___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
erify that mysql_config and mysqlclient.pc don't pick up any flags
they shouldn't.
Regards,
Norvald
I've verified that libmysqlclient-dev built with this patch fixes the
rsyslog build, so hopefully we can get a build uploaded that fixes thi
- lu...@debian.org wrote:
> On 14/11/16 at 02:47 -0800, Lars Tangvald wrote:
> >
> > - lu...@debian.org wrote:
> >
> > > On 13/11/16 at 22:59 -0800, Lars Tangvald wrote:
> > > >
> > > > - lu...@debian.org wrote:
>
- lu...@debian.org wrote:
> On 13/11/16 at 22:59 -0800, Lars Tangvald wrote:
> >
> > - lu...@debian.org wrote:
> >
> > > > Do you have the logs from the last run?
> > > > While we could disable the test that's failing, it would be
&g
hout your patch applied
>
> Lucas
Or did you mean with? It's failing in a different way. I think the way it's
failing here is to do with insufficient system resources.
--
Lars
hout your patch applied
>
> Lucas
And with the patch?
--
Lars
Forgot the bug
--
Lars--- Begin Message ---
- lu...@debian.org wrote:
> On 09/11/16 at 07:27 -0800, Lars Tangvald wrote:
> >
> > - lu...@debian.org wrote:
> >
> > >
> > > Hi,
> > >
> > > I don't think that
a patch that should fix the test to actually specify a blank user.
Are you able to test your build with the head of
https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/log/?h=mysql-5.7/ltangvald ?
It's the same as the 5.7.16 uploaded to unstable, just with that one extra
commit.
--
Lars
On 11/09/2016 10:11 AM, Lars Tangvald wrote:
Forgot to add in the bug.
On 11/09/2016 10:01 AM, Lars Tangvald wrote:
On 11/09/2016 08:59 AM, Lucas Nussbaum wrote:
On 09/11/16 at 08:17 +0100, Lars Tangvald wrote:
On 11/07/2016 03:43 PM, Lucas Nussbaum wrote:
Hi,
I don't think
On 11/08/2016 10:53 PM, Dominic Hargreaves wrote:
Hi Lars,
Now uploaded.
Cheers,
Dominic.
Great, thanks!
--
Lars
Hi all,
We prepared a security upload for the Oracle October 2016 CPU, but we need
someone with access to sponsor the upload to Debian unstable. Is anyone
available to do this?
The source should be ready to go from
https://anonscm.debian.org/cgit/pkg-mysql/mysql.git
--
Lars
Hi,
I can't reproduce this failure, with 5.7.15 or the 5.7.16 we've prepared
for #841163
I think maybe this is an unstable test, in which case we can disable it
until it's resolved upstream.
Could you retry the build and see if it happens again?
--
Lars
Hi,
On 10/19/2016 10:18 AM, Moritz Muehlenhoff wrote:
Hi,
On Wed, Oct 19, 2016 at 09:10:59AM +0200, Lars Tangvald wrote:
So for Linux we consider this fixed in 5.5.52, but the complete fix
was in 5.5.53.
Is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837984
addressed in 5.5.53?
No
On 10/19/2016 08:21 AM, Salvatore Bonaccorso wrote:
Hi Lars, hi Norvald,
On Wed, Oct 19, 2016 at 08:03:00AM +0200, Lars Tangvald wrote:
The following CVEs are fixed in 5.5.53:
CVE-2016-6662 CVE-2016-7440 CVE-2016-5584
The listing of CVE-2016-6662 is confusing here. This should actually
The following CVEs are fixed by 5.7.16:
CVE-2016-5584 CVE-2016-6304 CVE-2016-6662 CVE-2016-7440
--
Lars
On 10/18/2016 10:24 AM, Norvald H. Ryeng wrote:
Source: mysql-5.7
Version: 5.7.15-1
Severity: grave
Tags: security upstream fixed-upstream
The Oracle Critical Patch Update for October 2016
Hi,
This might be an error in the CPU announcement (they sometimes get
corrections after the initial announcement). I'll try to track down
someone who's worked on this fix and ask.
--
Lars
On 10/19/2016 08:21 AM, Salvatore Bonaccorso wrote:
Hi Lars, hi Norvald,
On Wed, Oct 19,
The following CVEs are fixed in 5.5.53:
CVE-2016-6662 CVE-2016-7440 CVE-2016-5584
On 10/17/2016 10:05 AM, Norvald H. Ryeng wrote:
Source: mysql-5.5
Version: 5.5.52-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream
The Oracle Critical Patch Update for October 2016 will be released
The following CVEs are noted as fixed since 5.6.30:
CVE-2016-3492 CVE-2016-5507 CVE-2016-5584 CVE-2016-5609
CVE-2016-5612 CVE-2016-5616 CVE-2016-5617 CVE-2016-5626
CVE-2016-5627 CVE-2016-5629 CVE-2016-5630 CVE-2016-6304
CVE-2016-6662 CVE-2016-7440 CVE-2016-8283 CVE-2016-8284
--
Lars
On 10/17
e the
default security, i.e. change packaging to create the mysql-files
directory. We're not aware of any other packages that rely on this
functionality, but there is a risk of this change disrupting user workflows.
--
Lars
On 10/17/2016 10:05 AM, Norvald H. Ryeng wrote:
Source: mysql-5.5
Versi
fault security, i.e. change packaging to create the mysql-files
directory. We're not aware of any other packages that rely on this
functionality, but there is a risk of this change disrupting user workflows.
--
Lars
On 10/17/2016 10:05 AM, Norvald H. Ryeng wrote:
Source: mysql-5.6
Version
fvisibility=hidden -o
CMakeFiles/taocrypt.dir/src/dsa.cpp.o -c
/«PKGBUILDDIR»/extra/yassl/taocrypt/src/dsa.cpp
debian/rules:142: recipe for target 'build-stamp' failed
make[1]: *** [build-stamp] Error 1
make[1]: *** Waiting for unfinished jobs
...
--
Lars
On 09/16/2016 10:39
Thanks, Bjoern. Did you run the dep8 test suite as well (I just started
a full test run now, so no big deal either way)?
--
Lars
On 09/15/2016 12:54 PM, Bjoern Boschman wrote:
Hi,
I've updated the git repo after I did a successful build on jessie.
Someone with upload rights just nee
Hi,
- car...@debian.org wrote:
> Hi Lars,
>
> On Wed, Apr 20, 2016 at 08:20:56AM +0200, Salvatore Bonaccorso wrote:
> > Hi Lars,
> >
> > On Tue, Apr 19, 2016 at 12:27:51PM -0700, Lars Tangvald wrote:
> > > We've prepared MySQL 5.5.49 packages for
1 - 100 of 377 matches
Mail list logo
