Opps, wrong one - this one https://github.com/MariaDB/server/pull/3039
On Mon, 12 Feb 2024 at 10:10, Daniel Black wrote:
>
> Fixed by https://github.com/MariaDB/server/pull/3002 which didn't make
> the release unfortunately.
>
> On Mon, 12 Feb 2024 at 09:43, Otto Ke
Fixed by https://github.com/MariaDB/server/pull/3002 which didn't make
the release unfortunately.
On Mon, 12 Feb 2024 at 09:43, Otto Kekäläinen wrote:
>
> Version: 1:10.11.7-1
>
> I confirm this was fixed in latest upload MariaDB 1:10.11.7-1, which
> included
>
merged - https://github.com/MariaDB/server/pull/2995
Thought my last comment was obvious, but here's it more explicitly:
requires https://github.com/MariaDB/server/pull/2893 as debian
explicit architectures aren't neede since dh_auto_configure handles
this.
If it works, upstream welcome.
Hurd string from uname -m, "SYSTEM processor: i686-AT386"
Since revering to linux-image-5.10.0-20 we've been free of the same errors.
On Tue, Feb 28, 2023 at 5:24 PM Diederik de Haas wrote:
>
> On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> > Source: linux
> > Version: 5.10.0-21-powerpc64le
> > Severity: grave
> > Justification: causes non-serious data loss
> > X-Debbugs-
Source: linux
Version: 5.10.0-21-powerpc64le
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you
btw, I never said it was the same bug. Given this was a hang and the
MDEV-30728 was a corrupted page read it's likely to be different.
2023-02-01 0:35:16 0 [Warning] mariadbd: Couldn't allocate 8388608
bytes (Large/HugeTLB memory page size 2097152); errno 22; continuing
I believe it is a kernel bug.
MariaDB is reading the page size from /sys/kernel/mm/hugepages.
mapflag= MAP_PRIVATE | OS_MAP_ANON;
mapflag|=
Rex has created a commit to try to identify the cause of the problem
in the main.order_by_innodb tests:
https://github.com/MariaDB/server/commit/a0300390b5efbd7b408cb166e0ee715364a85f3c
I don't know if salsa supports this, but a PR is
Some crashes in the signal handler are the just created "MDEV-30613
output_core_info crashes in my_read()" with a probable cause. Doesn't
help the original crash reason however.
A single thread backtrace isn't sufficient on errors like:
" InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded
So what Fedora does is a prep script called at StartPre on their
systemd service.
https://src.fedoraproject.org/rpms/mariadb/blob/rawhide/f/mariadb-prepare-db-dir.sh
Which even recently was seen as bloated
(https://lists.launchpad.net/maria-discuss/msg06376.html).
What could be done is a oneshot
Package: linux-signed-arm64
Dear Maintainer,
This is derived from https://jira.mariadb.org/browse/MDEV-29610
MariaDB-10.6+ uses liburing as its default async IO layer. In our CI
infrastructure there are a considerable amount of encryption.innodb*
test errors where uring returns the error IO
Actual error earlier in logs:
-- Performing Test HAVE_PEERCRED
-- Performing Test HAVE_PEERCRED - Failed
-- Performing Test HAVE_SOCKPEERCRED
-- Performing Test HAVE_SOCKPEERCRED - Failed
-- Performing Test HAVE_XUCRED
-- Performing Test HAVE_XUCRED - Failed
-- Performing Test HAVE_UNPCBID
--
The error is earlier in the logs:
-- Looking for sched_getcpu - found
-- Could NOT find PMEM (missing: PMEM_LIBRARIES PMEM_INCLUDE_DIR)
CMake Error at storage/innobase/CMakeLists.txt:345 (MESSAGE):
WITH_PMEM=ON cannot be satisfied
When the configure stage fails, the builds outputs the
The next and build log succeeds
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6=ppc64=1%3A10.6.7-3=1647203640=0
The remaining test failure main.func_json_notembedded has a fix
waiting (MDEV-27955)
When I see a SIGILL in a test case I'll believe it's incorrectly
called. In the
They won't crash, because the CPU features are tested before any call
to the optimized code is made.
https://github.com/MariaDB/server/blob/10.6/mysys/crc32/crc32c.cc#L542-L564
As the Debian CI undoubtedly runs the basic unit tests that cover
crc32 on the minimum hardware, and succeeds, it
On Thu, Mar 3, 2022 at 8:16 AM John Paul Adrian Glaubitz
wrote:
>
> Hello!
>
> On 3/2/22 21:14, Otto Kekäläinen wrote:
> > A recent build regression on ppc64el is preventing a new MariaDB version
> > from migrating from unstable to testing.
> >
> > Could any experts on this list help out?
>
> I
-- Forwarded message -
From: Daniel Black
Date: Thu, Dec 23, 2021 at 10:40 AM
Subject: Re: MariaDB 10.6 regressed ruby-mysql2
To: Otto Kekäläinen
Cc: , Tuukka Pasanen
, Faustin Lammler
expected Mysql2::Error with message matching /Lost connection to
MySQL server/, got
Marko tested this is fixed in linux-image-5.14.0-4-amd64 (5.14.16-1).
Thanks for the update.
https://jira.mariadb.org/browse/MDEV-26674?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=204907#comment-204907
https://marc.info/?l=linux-block=163489378723217=2
/
211021 11:23:27 [ERROR] mysqld got signal 6 ;
On Thu, Oct 21, 2021 at 10:10 PM Diederik de Haas wrote:
>
> On Thursday, 21 October 2021 12:41:34 CEST Salvatore Bonaccorso wrote:
> > On Thu, Oct 21, 2021 at 09:38:00AM +0000, Daniel Black wrote:
> > > Package: src:linux
>
Package: src:linux
Version: 5.14.12-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org
Dear Maintainer,
MariaDB has been investigating a 10.6+ related problem for a while
https://jira.mariadb.org/browse/MDEV-26674
fixed per upstream in 10.5.9
Hi,
MDEV-25394 is dissimilar. It is in InnoDB while this appears to be in
the optimizer code.
A new 10.3.31 is coming soon
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/pipelines/273217
The optimizer related fixes in the two version since 10.3.29 are:
Jeremy,
You are correct in that this is due to one of the hardening directives
in the service file Protect{Home,System} or PrivateDevices that is
trying to be applied before the kernel/system has completed the
underlying mounts on which they depend.
Without these hardening directives, and
RocksDB level fix:
https://github.com/facebook/rocksdb/commit/29f7bbef995bdf83098963799c66af742e95373f
The rocksdb submodule within mariadb is significantly older however -
https://github.com/MariaDB/server/tree/10.3/storage/rocksdb and I don't
know the update policy on it.
On Fri, Mar 12, 2021 at 6:51 AM Otto Kekäläinen wrote:
> Hello!
>
> Thanks for reviewing the systemd scripts in MariaDB. I added a couple
> of MariaDB devs as the systemd service files are not maintained in
> Debian but inherited from upstream MariaDB.
>
> On Thu, 11 Mar 2021 at 19:42, Marc
I noticed and wrote https://jira.mariadb.org/browse/MDEV-23900 covering this
Thanks for the tests.
Looks like removing the rocksdb part of the patch was overly ambitious.
Also need atomics on the unittest/mysys/my_atomic-t.c
I've updated:
https://github.com/MariaDB/server/tree/bb-10.3-danielblack-MDEV-23892-pr979
aka
https://jira.mariadb.org/browse/MDEV-23892 created for this issue.
https://github.com/MariaDB/server/pull/979 modified to be more minimal
https://github.com/MariaDB/server/commit/970984e9f9b385d7a64d896baa437a40d65d3f2f
is now in testing.
Comments welcome.
Testing on riscv64 is also very
I don't think so.
There's no case for it.
In the direction of eliminating mysql names in MariaDB let's not take
a step back.
On Sun, Oct 4, 2020 at 9:04 PM Otto Kekäläinen wrote:
>
> Hello!
>
> Any comments to this
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971255 from anyone?
>
>
Upstream PR is very welcome.
Occasional nagging also.
Providing a different sysvinit service name different from the systemd
service name is a violation of the packaging guidelines
https://wiki.debian.org/Teams/pkg-systemd/Packaging?action=show#systemd_unit_files_naming_and_installation
Wasn't this covered already in
I'm probably going to add a fix to
https://github.com/MariaDB/server/blob/10.5/configure.cmake#L865 to
include libatomic globally if needed.
AIX needs it too.
On Mon, Sep 21, 2020 at 7:56 AM Otto Kekäläinen wrote:
>
> Package: mariadb-10.5
> Version: 1:10.5.5-1~exp1
>
> The riscv64 builds on
As Thadeu Lima de Souza Cascardo said, the build time detected page size
isn't correct, perhaps using --with-lg-page=/--with-lg-page-sizes at
compile time.
This is available in the 3.6.0 version of jemalloc.
(upstream currently
at 4.4.0).
As an aside, I've got part way though an upstream patch
As Thadeu Lima de Souza Cascardo said, the build time detected page size
isn't correct, perhaps using --with-lg-page=/--with-lg-page-sizes at
compile time.
This is available in the 3.6.0 version of jemalloc. (upstream currently
at 4.4.0). I've got part way though an upstream patch to change this
On 08/09/16 17:40, Sylvestre Ledru wrote:
...
> This is working fine with 3.6. Sorry but I am not planning to fix that as 3.5
> is pretty old...
> http://apt.llvm.org/ is providing up to date versions of clang.
True, but not for ppc64le against which the bug was written.
N: Skipping acquire
Package: selinux-basics
Version: 0.5.2
Severity: wishlist
Dear Maintainer,
* What led up to the situation?
I started a freedombox using freedombox maker which uses vmdebootstrap to
create and image. The VM has extlinux as the bootloader.
I followed the selinux steps on
tags 742267 patch
Two patches as suggested by Petter (which I have a preference too):
vmdebootstrap-vmlinuz-nonversioned.patch - for non-versioned /vmlinux boot
vmdebootstrap-etc-extlinux.patch for placing etclinux.conf in /etc
directory and to put a symlink there (if the filesystem supports
Package: corosync
Version: 1.4.2-3
Severity: minor
{/etc/corosync,/usr/share/docs/corosync/examples}/corosync.conf.example*
contains the path /var/log/cluster/corosync.log
Because /var/log/cluster doesn't exist the rather unspecific error is returned.
[] Restarting corosync daemon:
Package: pacemaker
Version: 1.1.7-1
Severity: minor
For pacemaker to provide a working crm interface the following is needed in the
corosync configuration.
Adding the following would assist in this matter.
Install the following contents in /etc/corosync/service.d/pacemaker.conf:
service {
#
To be fixed in 0.9 release
https://github.com/fail2ban/fail2ban/commit/d07df6637071b7ffa8be988a834a6bb71d9bf932
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
https://github.com/fail2ban/fail2ban/commit/224e795f4c45fc9cf4b8c769b1fa97d544aeacde
for 0.8.12 release
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
-0.6 has some nice features if a version bump can be considered.
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise maintenance for MySQL/MariaDB server environments.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
That is sad that iirc we do not have in fail2ban an easy ability to
extend list of failregex's in additional file like
/etc/fail2ban/filter.d/sshd.local so you didn't have to 'merge' for
every upgrade. Feel free to file a wishlist bug, who knows... ;-)
No, but at least now we can use a
control: +patch
to remove the negative numbers the patch previously mentioned does work and was
accepted upstream: https://github.com/munin-monitoring/munin/pull/126
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
The pull request to upstream: https://github.com/munin-monitoring/munin/pull/126
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
patch created by ksmadsen in
http://munin-monitoring.org/ticket/1275
The description provided was:
I've traced this problem to the fact that on the RH kernel we are using,
the rd_ticks/wr_ticks in /sys/block/*/stat are 32-bit numbers, so when
the ticks wraps, a negative value is reported.
Package: munin-plugins-core
Version: 2.0.6-4+deb7u1
Severity: normal
Tags: patch
Dear Maintainer,
The created /etc/cron.d/munin-node doesn't work as when the plugins are run
from cron they don't know the state directory
Adding the following to this cron file fixed it for me:
Package: munin-async
Version: 2.0.6-4+deb7u1
Severity: normal
Tags: patch
Dear Maintainer,
I needed a status to run this init under puppet without continious restarts.
While adding this (copied from munin-node) I noticed the pid file wasn't remove
on stop
and the the SCRIPTNAME was wrong.
--
Few init script changes required:
in do_start - there is no --test argument.
not sure why --make-pidfile is there, lsyncd creates its own pid file (but
still doesn't remove it -
(https://github.com/axkibe/lsyncd/issues/196)
Hope pages and doco should refer to github and its wiki as it seems
Package: lsyncd
Version: 2.1.4-1
Severity: wishlist
There's a small bit of fuzz correction needed with the patch however the rest
of the build works.
The trickest thing is the user configation file options have changed for rsync.
In 2.0.7 the following configuration worked and it doesn't in
1. Also missing from the pacemaker dependencies is libheartbeat2
This is dl loaded at the start of the runtime.
From log at pacemakerd startup:
Apr 14 07:19:23 tx-web05 pacemakerd[5000]:error: find_library_function:
Fatal: Could not open libhbclient.so.1: libhbclient.so.1: cannot open
Package: pacemaker
Version: 1.1.9+git20130321-1
Severity: normal
I was doing a backport that was going ok until these two missing dependancies.
I probably can get around them but just reminding you in case you missed adding
two packages.
I'm about to write/put a bunch of patches in the pervent
Package: corosync
Version: 2.3.0-1
Severity: serious
Justification: fails to build from source
While doing a backport of corosync-2.3.0-1 to squeeze I it wouldn't build and
complained that dbus was missing.
It seems libdbus-1-dev was missing from the dependancy list.
-- System Information:
For ref I did a comparison against the only long term supported 2.6.33+ kernel,
2.6.34.14 released 2013-01-16 (ref: https://www.kernel.org/). Note dm-snap got
merged into the 2.6.32 kernel on 2009-12-03.
Looking at changes in dm-snap.c
After the kernel change previously described snapshot-origin is there.
$ sudo dmsetup targets
snapshot-merge v1.0.0
snapshot-origin v1.7.0
snapshot v1.9.0
striped v1.3.0
linear v1.1.0
errorv1.0.1
$ uname -a
Linux quoll 2.6.32-5-amd64 #1 SMP Sun May 6
I had the same problem an did a successful restore on a live system as follows:
apt-get install linux-source-2.6.32
This involved copying 5 files from the 2.6.33 kernel.org release in the
directory drivers/md :
dm-snap.c
dm-snap-persistent.c
dm-snap-transient.c
dm-exception-store.h
reported upstream. Patch there as well
https://sourceforge.net/tracker/?func=detailaid=3596229group_id=269812atid=1147701
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: opendkim
Version: 2.0.1+dfsg-1
Severity: normal
run opendkim-genkey:
look at default.txt. This has a deprecated g=*
default._domainkey IN TXT v=DKIM1; g=*; k=rsa;
p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDUS6bO3Gk/xAHIlOOxYVAh+tXqdxkPDqQfXurDryvMlfe3m9Nl9CddAmRPpR/KckalaoE0RhRDL6WyU
/lib/munin-async/*0 {
daily
missingok
...
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise maintenance for MySQL/MariaDB server environments.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
patch here:
https://github.com/grooverdan/munin-debian/commit/8e537fcc99632de38f3d9fe5ec5dad3d4fc26250
(with other munin patches)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
patch here:
https://github.com/grooverdan/munin-debian/commit/ed145ce0067ddc40911aa0077f52ae456d50438d
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: munin-async
patch:
https://github.com/grooverdan/munin-debian/commit/74919f02b17eed908cdd362b60e71a00b9ea5041
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: munin-async
patch:
https://github.com/grooverdan/munin-debian/commit/155116a7c9c716c58eadb45ee490d82eb6a6c6c9
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I've reworked the article a little to account for fixes (including some of my
pending ones) and improvments.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
patch:
https://github.com/grooverdan/munin-debian/commit/162dd395cb75889d57b0dc36c114cc3dccfe1243
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
package: munin-plugins-core
patch:
https://github.com/grooverdan/munin-debian/commit/598a1ebe07ec46fadb3da741e7f4b0c5e23949c7
sample from munin.log without dependancy installed:
--
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise maintenance for MySQL/MariaDB
patch:
https://github.com/grooverdan/munin-debian/commit/ff90b8f3be96128afc5d3a45f60131e61aafb1a4
doesn't disable the cidr as recommended previously however.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: munin-async
Version: 2.0.6-1~bpo60+1
Severity: important
Tags: patch
As the munin-asyncd process needs to write to /var/lib/munin-async this
package should make this directory owned by the munin-async user when it
installs it.
-- System Information:
Debian Release: 6.0.6
APT prefers
Package: munin-async
Version: 2.0.6-1~bpo60+1
Severity: important
Both munin-node and munin-async start at S17 on runlevels 2 3 4 5.
munin-async however requires that munin-node is running otherwise it terminates.
Because alphabetically munin-async munin-node this always fails on startup.
As recommended by CoolCold.
Also changed NAME to searchd to make /etc/init.d/sphinxsearch status work.
The /proc/{pid}/cmdline is searchd not /usr/bin/search when checking the status.
--
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise maintenance for MySQL
reopen 656326
No cron changes or permission changes on the pid occurred. I've attached the
diff in the attached patch. I also enhanced the variable escaping.
--
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise maintenance for MySQL/MariaDB server environments
such that the sphinxsearch
user can read this file.
Cheers and thanks for packaging this.
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise maintenance for MySQL/MariaDB server environments.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
such that the sphinxsearch
user can read this file.
Cheers and thanks for packaging this.
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise maintenance for MySQL/MariaDB server environments.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Package: selinux-policy-default
Version: 2:0.2.20100524-7+squeeze1
Severity: important
Similar to bug 599053 which is archived:
New install:
Error 1: sendmail...
Cannot run (postfix) sendmail under selinux
$ sudo ls -ldaZ /usr/sbin/postdrop /var/spool/postfix/maildrop
-r-xr-sr-x. 1 root
Package: selinux-policy-default
Version: 2:0.2.20100524-7+squeeze1
Severity: low
On bootup I'm getting the following errors:
Dec 15 20:25:43 tx-web01 kernel: [1419609.818930] type=1400
audit(1323998741.657:3): avc: denied { read } for
pid=245 comm=fstab_import name=fstab dev=xvda
Package: usb-modeswitch-data
Version: 20111023
Severity: normal
This version bump contains a number of additional 3G modems that don't have
switch mode configurations.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386
--
Daniel Black
Cloud Central
Scale Your Data Center In The Cloud
Switch: 1300 144 007
Fax: 02 6173 7339
Email: dan...@cloudcentral.com.au
--- /etc/init.d/ssh.orig 2010-02-11 18:27:46.0 +1100
+++ /etc/init.d/ssh 2010-02-11 18:32:16.0 +1100
@@ -57,6 +57,17 @@
fi
=markup
http://cvs.fedoraproject.org/viewvc/rpms/openssh/F-11/sshd.init?view=markup
thanks for your maintainer efforts so far.
--
Daniel Black
Cloud Central
Scale Your Data Center In The Cloud
Switch: 1300 144 007
Fax: 02 6173 7339
Email: dan...@cloudcentral.com.au
--
To UNSUBSCRIBE, email
On Monday 23 November 2009 23:32:11 Ondřej Surý wrote:
And what is the problem?
libunbound1 does depend on libldns1 and none of the exported symbols
from libunbound-dev does need libldns-dev.
Ok. at the moment I only have libunbound-dev installed. The ldns hint in the
libunbound.la file
Package: libunbound-dev
Version: 1.0.2-1
Severity: normal
The libunbound.so library also contains a dynamic section to ldns and there are
ldns symbols in the
file:
readelf -a /usr/lib/libunbound.so |fgrep UND\ ldns
3: 152 FUNCGLOBAL DEFAULT UND ldns_calc_keytag_raw
5:
according to other references m2crypt seems to be a requirement.
http://www.nabble.com/Bug-in-HTTPSHandler-td15779972.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: sympa
Version: 5.3.4-5
Severity: normal
Global task models according to the documentation should be in the
global_task_models directory.
Installing the directory /etc/sympa/general_task_models is confusing and won't
work as replacement
for global_task_models.
-- System Information:
Package: sympa
Version: 5.3.4-5
Severity: normal
/var/lib/sympa/expl/X509-user-certs should be created owned by sympa:sympa.
This is where the
sympa process stores user certificates.
-- System Information:
Debian Release: 4.0
APT prefers oldstable
APT policy: (500, 'oldstable')
Package: dkim-filter
Version: 2.6.0.dfsg-1
http://sourceforge.net:80/project/shownotes.php?group_id=139420release_id=654247
Mike, as you discovered 2.6.0-2.8.0 has a DoS security vulnerability. Can this
be fixed in lenny/etch-backports please?
Cheers,
Daniel
--
To UNSUBSCRIBE, email to
/shownotes.php?group_id=133598release_id=533414
--
Daniel Black [EMAIL PROTECTED]
Gentoo Foundation
signature.asc
Description: This is a digitally signed message part.
Watch out for a gcc-3 compile error
https://bugs.gentoo.org/show_bug.cgi?id=165340
FreeBSD may have some patches - investigating now - will report in above url
--
Daniel Black [EMAIL PROTECTED]
Gentoo Foundation
pgpMQcSbIXZeT.pgp
Description: PGP signature
/show_bug.cgi?id=133092
http://bugs.gentoo.org/show_bug.cgi?id=145974
2.
http://www.freebsd.org/cgi/cvsweb.cgi/ports/net/wireshark/files/patch-epan_dissectors_packet-diameter.c
--
Daniel Black [EMAIL PROTECTED]
Gentoo Foundation
pgpVUhVMQuX8p.pgp
Description: PGP signature
90 matches
Mail list logo
