Package: php-net-dns2
Version: 1.5.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
after upgrading to Debian 12, Horde stopped working. It logs messages like:
PHP Fatal error: Uncaught ValueError: fread(): Argument #2 ($len
On Friday 22 October 2021, Yves-Alexis Perez wrote:
> On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote:
> > MDEV-15912: Remove traces of insert_undo
> >
> > Let us simply refuse an upgrade from earlier versions if the
> > upgrade procedure was not fo
dff451f0a7a6d6246334aace697b230b4174f2c1 M mysql-test
:04 04 4a0352d498b9487cae46c6363d86603de0ccb361
3e6aa2377e89f28192e987f2f8655e3d866ab4be M storage
--
Ondrej Zary
Tested upstream mariadb packages. 10.3.30 works, 10.3.31 fails.
--
Ondrej Zary
OR] Unknown/unsupported storage engine: InnoDB
> 2021-10-14 9:38:49 0 [ERROR] Aborting
>
> So maybe I do have a corrupted database or something but I'm unsure what to do
> next (I don't think I have an older backups of the database). Also it still
> works just fine with 10.3.25.
I still get the error too. That patch was meant to fix a problem specific to
BSD.
--
Ondrej Zary
e1), then shutdown ended
immediately. Seems that the file structure is corrupted somehow - probably
because of a previous bug. One table is also affected by the "ERROR 1118
(42000): Row size too large (> 8126)" bug.
When complete SQL dump is restored with a new ibdata1, everything works
(upgrade to 10.3.31 and also clean shutdown).
--
Ondrej Zary
t mariadb-10.3.30 but dpkg-buildpackage failed with:
dh_install: mariadb-plugin-cassandra missing files:
etc/mysql/conf.d/cassandra.cnf
--
Ondrej Zary
gt;
> Thanks for reporting. Could you please check if this has been reported
> upstream at jira.mariadb.org?
>
> There isn't much we can do about InnoDB internals in Debian packaging.
--
Ondrej Zary
Package: mariadb-server
Version: 1:10.3.31-0+deb10u1
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
upgrading mariadb-server from 1:10.3.29-0+deb10u1 to 1:10.3.31-0+deb10u1 failed
because mariadb failed to start. /var/log/mysql/error.log:
2021-10-10 15:12:49 0 [ERROR
ules/@vue/component-compiler-utils/dist/parse.js:15:23)
at Object.module.exports
(/var/lib/gitlab/node_modules/vue-loader/lib/index.js:67:22)
@ ./pages/projects/new/index.js 5:0-57 28:29-50 32:15-36
@ multi ./main ./pages/projects/index.js ./pages/projects/new/index.js
--
Ondrej Zary
Package: gitlab
Version: 13.12.9+ds1-1~fto10+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
installing gitlab 13.12.9+ds1-1~fto10+1 on buster amd64 fails with:
Installing node modules...
Resolving 2.4.2 to a url...
error An unexpected error occurred: "Release not found
directory)
Where comes the weird CHANNELID 0x0103F8 from? Maybe 0x3f8 as I/O address of PC
COM1 port?
The working /etc/reader.conf.d/libtowitoko2 file is:
FRIENDLYNAME "Towitoko Chipdrive Reader"
LIBPATH /usr/lib/libtowitoko.so.2.0.0
CHANNELID 1
However, it should probably be commented-out by default (as in
/etc/reader.conf.d/libccidtwin)
--
Ondrej Zary
Package: bind9
Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
Followup-For: Bug #860225
Dear Maintainer,
looks like I've just been hit by CVE-2017-3139 on Debian Wheezy.
Seems it's not limited to RedHat:
Aug 31 17:03:24 r210 named[29899]: validator.c:1858: INSIST(rdataset->type
== ((dns_rdatatype_t)dns_
Package: python-suds
Version: 0.3.9-1+deb6u1
Severity: serious
Justification: breaks unrelated software
The deb6u1 update to python-suds fixed insecure temporary directory
creation (/tmp/suds) by creating directories with random names in /tmp.
However, these directories are never deleted, causin
14 matches
Mail list logo
