Hi Wes,
I actually suspect more people fall into that boat than people that will
make use of the new structure directly in their application. I just
think most people don't mind recompiling as much as third party
commercial products running on an OS which just distributed a new
version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Thomas,
Logged with Debian, right? Packaging bugs don't belong in our tracker...
No, in *our* tracker, because the issue prevents us from upgrading to autoconf
2.60 (or later) for 5.5.
In fact autoconf 0.59c contains the relevant change:
*
Hi Dave,
Index: agent/mibgroup/Makefile.in
===
RCS file: /cvsroot/net-snmp/net-snmp/agent/mibgroup/Makefile.in,v
retrieving revision 5.3
diff -u -r5.3 Makefile.in
--- agent/mibgroup/Makefile.in13 Sep 2006 17:00:27 -
Hi Thomas,
I think it's overdue. I'm happy to attach a revised patch that changes all oid
length variables/parameters consistently to size_t, matching the main library.
I'm calling for votes to include this in 5.4.
+1 from me.
From the Debian point of view, the next release will support yet
Thomas Anders schrieb:
-Coders,
I've committed a few additional manual pages that have been supplied by
Debian:
encode_keychange.1.def mib2c-update.1.def tkmib.1.def
fixproc.1.def net-snmp-config.1.def traptoemail.1.def
Attached please find the proposed patch to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
net-snmp-5.4 comes with the new directory doc/rfc containing several IETF RFCs.
Unfortunately, they come with a license that prevents a redistribution under the
Debian terms (see http://wiki.debian.org/NonFreeIETFDocuments for details). This
Hi,
Wes Hardaker wrote:
I've published 5.4.rc1 to the Net-SNMP download site:
https://sourceforge.net/project/showfiles.php?group_id=12694package_id=11571release_id=448774
While building a package for Debian, i found pythoninstall not honoring the
DESTDIR environment variable.
Any
Hi Petr,
In long term we have to simplify include/net-snmp/system/kfreebsd.h
by polishing our kernel headers and glibc headers.
But in mean time, it would be nice, if you could include this patch.
It would help us, as libsnmp-dev have rather big set of packages
that (recursively)
Hi Hilmar,
The default value of the sysObjectID is .1.3.6.0.0.0.0.0.0.0, which
is not a valuable information. I've compared it to an how grown net
snmp 5.0.6, which give out on that OID the value
.1.3.6.1.4.1.8072.3.2.xx (where xx is one of the numbers 1-13
depending on which OS it is
Hi Dave,
I can sort-of see an argument for distinguishing the 5.2.x line,
given this is still being actively maintained. But 5.1.x is
basically winding down, and 5.0.x is completely closed. So I'm
unconvinced that it's worth distinguishing between the two at
this late stage.
I would also
Hi Dave,
I can sort-of see an argument for distinguishing the 5.2.x line,
given this is still being actively maintained. But 5.1.x is
basically winding down, and 5.0.x is completely closed. So I'm
unconvinced that it's worth distinguishing between the two at
this late stage.
I would also
Hi Mike,
Do you have individual patches which may have been rolled up
into net-snmp_5.1.2-5.diff.gz ?
No, not yet. One of my plans is to switch the build system for net-snmp to
cdbs after sarge is out of the door. This will include seperating the
patches.
Jochen, Would like to review these
Hi Robert,
Ack! Is there a bug report for this one?
I just opened bug number 1017112 for this problem.
I'm guessing this a 64 bit system, where a long is 64 bits?
This is on an alpha. long is really 64 bits on this arch.
Thanks,
Jochen
Hi Richard,
Checking a few of the sourceforge compile farms hosts reveal that neither
FreeBSD or OpenBSD have SCNuMAX defined in inttypes.h. So instead of an
out-and-out replacement, we need to break down and use an ifdef on
__STDC_FORMAT_MACROS to add the new 64-bit compatabile definitions.
14 matches
Mail list logo
