Package: mbuffer / 20241007+ds1-1

Metadata

Package Version Patches format
mbuffer 20241007+ds1-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
pipe buf.patch | (download)

log.c | 143 47 + 96 - 0 !
1 file changed, 47 insertions(+), 96 deletions(-)

 use fpathconf() if pipe_buf is not defined.
typos.patch | (download)

ChangeLog | 24 12 + 12 - 0 !
configure.in | 2 1 + 1 - 0 !
globals.c | 2 1 + 1 - 0 !
mbconf.h | 2 1 + 1 - 0 !
mbuffer.1.in | 2 1 + 1 - 0 !
mbuffer.c | 4 2 + 2 - 0 !
mbuffer.rc | 2 1 + 1 - 0 !
settings.c | 10 5 + 5 - 0 !
8 files changed, 24 insertions(+), 24 deletions(-)

 fix some grammatical and typographical errors.
test library.patch | (download)

Makefile.in | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 use cppflags and ldflags for idev and tapetest, too.
tapetest format.patch | (download)

tapetest.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 open more than 1000 files in tapetest.
internal symbol.patch | (download)

tapetest.c | 3 0 + 3 - 0 !
1 file changed, 3 deletions(-)

 drop __use_gnu; _gnu_source is the correct symbol.
libmhash so version.patch | (download)

hashing.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 look for libmhash.so.2, not libmhash.so.
 The libmhash.so file is usually just a symlink installed by
 the development package so that the build-time linker can find
 the proper shared object to look symbols up in and to record
 the SONAME into the executable file.  On most Linux distributions
 that make a distinction between development packages and shared
 library packages, it is very unlikely that a *.so file will exist
 at runtime.
cppflags.patch | (download)

Makefile.in | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 honor cppflags during compilation.
build stamp.patch | (download)

Makefile.in | 7 4 + 3 - 0 !
1 file changed, 4 insertions(+), 3 deletions(-)

 fix the build file and directory dependencies.
 Create a build/created.stamp file and depend on it instead of
 the build/ directory itself when checking for stale object and
 executable files. This fixes a problem with make(1) considering
 everything as out of date since the build/ directory's timestamp
 has been updated after the object files within it.
cross.patch | (download)

configure.in | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 unbreak cross-compilation: we do not need target tools.
decrease numblocks.patch | (download)

mbuffer.c | 5 5 + 0 - 0 !
1 file changed, 5 insertions(+)

 do not try to allocate more than the available memory.
verbose test.patch | (download)

Makefile.in | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 display the mbuffer defaults before the test.
clean files.patch | (download)

Makefile.in | 10 6 + 4 - 0 !
1 file changed, 6 insertions(+), 4 deletions(-)

 clean up more autogenerated files
 Make sure the mbuffer.1 manual page is recreated by also removing
 the autogenerated version.h file so that the mkversion.sh tool
 (which also generates the manual page) is also run the second time
 around.
 Remove some more test output files.
Bug-Debian: https://bugs.debian.org/1048349
Bug-Debian: https://bugs.debian.org/1049628