Package: iputils-ping
Version: 3:20121221-5+b2
Severity: normal
Tags: upstream
Dear Maintainer,
Target System
=
buster / testing
iputils-ping3:20180629-2armhf
Summary
===
A process using ping with a count will hang/freeze for a period of time between
packets if the
Package: python-wxglade
Version: 0.6.8-2.2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the o
Also perl and python bindings for net-snmp.
libsnmp-python
libsnmp-perl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Request for net-snmp packages
snmpd
snmp
snmp is used in every (or close to every) piece of networking equipment
that constitutes the Internet. It is the most common method used to
monitor and manage networking equipment, be it routers, switches,
firewalls, gateways, servers, etc, etc.
I installed snmp 5.4.1 from experimental onto a Lenny box and the AES
seems to be compiled in, so I guess this bug should be closed.
How soon can we get snmp 5.4 into testing ???
Cheers, Brendan.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
I think I have tracked this down to the configure script. The stub
program used to test for the function AES_cfb128_encrypt() is failing
compilation. It seems the linker is not being passed -lcrypto.
I will try to learn some autoconf stuff and try to figure out a patch.
I do wonder why AC_CH
Package: snmp
Version: 5.2.3-7
Severity: important
The net-snmp command line apps (eg. snmpget, etc) do not have support for AES
compiled in.
This can easily be tested by running the following command.
$ snmpget -h 2>&1 | grep "\-x"
It reports:
-x PROTOCOL set privacy proto
I'm running Etch (testing) on an amd64 server. trac is currently broken
but I notice it is 0.9.6. Apparently Clearsilver requires 0.10.x for
x86_64 architectures so I _assume_ the same is true of amd64.
I'd really like to get the 0.10.x series into testing and thus in the
next stable release
I'm running Etch (testing) on an amd64 server. trac is currently broken
but I notice it is 0.9.6. Apparently Clearsilver requires 0.10.x for
x86_64 architectures so I _assume_ the same is true of amd64.
I'd really like to get the 0.10.x series into testing and thus in the
next stable release
9 matches
Mail list logo
