Bug#847768: hoichess: please make the build reproducible

2017-06-20 Thread Holger Ruckdeschel
On Mon, 19 Jun 2017 21:59:00 -0300, Samuel Henrique wrote:

> I see on the changelog of 0.20.0:
> 
> > * Included reproducible-build patch from Debian package
> >hoichess_0.19.0-3.
> >  
> 
> ​Although, 0.21.0 still has other reproducibility problems[1], could you
> help us with that?

Hello Samuel,

I have applied the attached change to my source, it will be included in the
next releases. You could still replace this by the Debian package version
as suggested by Daniel Shahaf. In this case, I kindly ask you to add e.g.
"-debian" to the version string to avoid confusion.

Best regards,
Holger
Index: src/build/print_version_str
===
--- src/build/print_version_str	(revision 2536)
+++ src/build/print_version_str	(revision 2537)
@@ -6,7 +6,6 @@
 	mydir=`dirname "$0"`
 	basedir="$mydir"/..
 fi
-progname="hoichess"
 
 svn info "$basedir" >/dev/null 2>&1
 if [ $? -eq 0 ]; then
@@ -19,17 +18,7 @@
 
 	version_str="$branch-$rev-svn"
 else
-	dirname=`cd "$basedir" && pwd | xargs basename`
-	case "$dirname" in
-		"$progname"-*)
-			version=`echo "$dirname" | sed -e "s/^$progname-//"`
-			;;
-		*)
-			version="unknown"
-			;;
-	esac
-
-	version_str="$version"
+	version_str=`awk '/^Version/ {print $2; exit}' "$basedir/ChangeLog"`
 fi
 
 echo "$version_str"


Bug#401164: hoichess: the opening-book is missing

2006-12-12 Thread Holger Ruckdeschel
oliver [EMAIL PROTECTED] wrote:

 What I really would like to have, is the possibility to do something like: 
 
 'cat openings.pgn | hoichess -B openingbook.bin'

Actually, you can do it this way:

echo book create openingbook.bin openings.pgn 0 10 | hoichess

 Another Question is if the opening book is not compiled at the system, if I 
 will get problems with litle/big endian.

No, opening books are now architecture independent.

Best regards,
Holger


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#364656: hoichess_0.4.0-1(amd64/unstable): arch: any package sets -march=i686

2006-04-30 Thread Holger Ruckdeschel
Frederik Schüler [EMAIL PROTECTED] wrote:

 There was an error while trying to autobuild your package:
  [...]
  g++-4.0 -W -Wall -O3 -march=i686  -c -o bench.o bench.cc
  bench.cc:1: error: CPU you selected does not support x86-64 instruction set
  bench.cc:1: error: CPU you selected does not support x86-64 instruction set
  make[2]: *** [bench.o] Error 1
  make[2]: Leaving directory `/build/buildd/hoichess-0.4.0/src'
  make[1]: *** [all] Error 2
  make[1]: Leaving directory `/build/buildd/hoichess-0.4.0'
  make: *** [build-stamp] Error 2
 
 Please do not use -march=i686 on an arch: any package, or make it arch:
 i386 if it is not portable at all.

The '-march=i686' option, as well as the explicit use of g++-4.0, are just
local definitions that I use on my development system. I guess it was not 
a good idea to put them into the source distribution. Sorry about that, 
I'll remove them with the next release.
In fact, HoiChess should be quite portable, although I was only able to
test it on Solaris (of course without -march=i686) and Windows (using 
gcc-mingw32).


Best regards,
Holger



Bug#301190: libgstreamer0.8-0: package installation creates files in ~root

2005-03-24 Thread Holger Ruckdeschel
Package: libgstreamer0.8-0
Version: 0.8.8-1
Severity: normal

Hi,

When installing libgstreamer0.8-0, the postinst script calls
gst-register-0.8, which creates the directory /root/.gstreamer-0.8:

| Rebuilding global_registry (/var/lib/gstreamer/0.8/registry.xml) ...
| Added plugin gstvideo with 0 features.
| [...]
| Rebuilding user_registry (/root/.gstreamer-0.8/registry.xml) ...
| Loaded 19 plugins with 27 features.

I think no package should ever create files in any user's home
directory, especially not in root's.


Regards,
Holger


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages libgstreamer0.8-0 depends on:
ii  libc6   2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libglib2.0-02.6.3-1  The GLib library of C routines
ii  libpopt01.7-5lib for parsing cmdline parameters
ii  libxml2 2.6.16-3 GNOME XML library
ii  zlib1g  1:1.2.2-3compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#299041: debhelper: packages using dh_gconf should not create files in /root

2005-03-11 Thread Holger Ruckdeschel
Package: debhelper
Version: 4.2.31
Severity: normal

Hi,

When installing or upgrading gnome packages, the postinst/prerm scripts
sometimes create gnome-related directories in /root: .gconf, .gconfd,
.gnome, .gnome2, .gnome2_private. These directories are all empty or
contain empty files.

Here is part of the code that debhelper writes into these scripts:

HOME=/root GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source` \
gconftool-2 \
--makefile-install-rule $SCHEMA_LOCATION/$SCHEMA  /dev/null

See also Bug#116898. I think, using 'HOME=/root' is bad for two reasons:

(a) According to FHS, the home directory of root may be a different one
than /root.
(b) More important, simply installing/upgrading packages should not
create files in any user's home, especially not in root's.

Perhaps it would be better to use something like HOME=`mktemp -d` and
to remove this temporary directory afterwards.


Regards,
Holger


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages debhelper depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  debconf-utils 1.4.30.11  debconf utilities
ii  dpkg-dev  1.10.27Package building tools for Debian
ii  file  4.12-1 Determines file type using magic
ii  fileutils 5.2.1-2The GNU file management utilities 
ii  html2text 1.3.2a-1   An advanced HTML to text converter
ii  perl  5.8.4-6Larry Wall's Practical Extraction 
ii  po-debconf0.8.21 manage translated Debconf template

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#298329: latex2html: pstoimg -multipage reads temporary files from other instances running at same time

2005-03-06 Thread Holger Ruckdeschel
Package: latex2html
Version: 2002-2-1-8
Severity: important
Tags: patch

Hi,

When two or more instances of pstoimg, called with the -multipage option
and using the same temporary directory (/tmp by default), run at the same
time, the results may get mixed up. This is because pstoimg uses a wrong
pattern to collect the files created by ghostscript.

Here is a patch which fixes the problem:

 snip 
--- /usr/bin/pstoimg2004-09-01 20:50:36.0 +0200
+++ pstoimg 2005-03-06 20:40:54.0 +0100
@@ -894,7 +894,7 @@
   print qq{$prompt: Error: Could not open directory $pnmdir:
$!\n};
   return 0;
   }
-my @list = grep(/^\d+_\w*\./,readdir(DIR));
+my @list = grep(/^\d+_${pnmbase}\.pnm/,readdir(DIR));
 closedir(DIR);
 if(@list) {
   my $i;
 snap 

Regards,
Holger


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (800, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages latex2html depends on:
ii  gs8.01-5 Transitional package
ii  gs-gpl [gs]   8.01-5 The GPL Ghostscript PostScript int
ii  netpbm2:10.0-8   Graphics conversion tools
ii  perl  5.8.4-6Larry Wall's Practical Extraction 
ii  tetex-bin 2.0.2-26   The teTeX binary files
ii  tetex-extra   2.0.2c-6   Additional library files of teTeX

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]