Re: Installed sather 1.2.1-5 (i386 all source)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 29 October 2001 08:15, Branden Robinson wrote:
>
> His changelog entry said:
> > * fix: the correct build dependencies are tcl/tk 8.2 rather than 8.3.
> > sather doesn't build with 8.3 yet.
>
> The build dependencies were already fixed thus in 1.2.1-4. If he had
> bothered to look at that version of the package, he'd have known that.
> Instead, evidence indicates that aside from being aware of its existence,
> he completely ignored it.
>
> That is not the proper way to recognize an NMU.
I will gladly present the proper response.
I did bother to look at 1.2.1-3 which broke sather:
orion:nmu$ gzip -d -c sather_1.2.1-2.3.diff.gz | grep tcl
int to_int(Tcl_Interp *tcl) {
return ((int) tcl);
- --- sather-1.2.1.orig/System/Platforms/tcltk/Make.target.inc
+++ sather-1.2.1/System/Platforms/tcltk/Make.target.inc
- -TCL_LIB_NAME = $(shell if [ -e /usr/lib/libtcl8.0.so ] ; then echo "tcl8.0"
; else echo "tcl"; fi)
+TCL_INC_NAME = $(shell if [ -d /usr/include/tcl8.2 ]; then echo
"/usr/include/tcl8.2"; else echo "/usr/include"; fi)
+TCL_LIB_NAME = $(shell if [ -e /usr/lib/libtcl8.2.so ] ; then echo "tcl8.2"
; else echo "tcl"; fi)
- --- sather-1.2.1.orig/System/Platforms/tcltk/Platform.module
+++ sather-1.2.1/System/Platforms/tcltk/Platform.module
+ - REAL BEFORE VIRTUAL (for emacsen, c-shell, tclsh)
+ - use {tcl,tk}8.3* instead of 8.2
+ * Changed from tcl/tk 8.0 to 8.2 in System/Platforms/tcltk/Make.target.inc
+Build-Depends: debhelper, libgc6-dev, tcl8.3-dev, tk8.3-dev, xlibs-dev
- -Depends: sather, c-shell, tclsh, ${shlibs:Depends}
+Depends: sather, tcsh | c-shell, tcl8.3 | tclsh, ${shlibs:Depends}
It takes a little more than changing debian/control to build with tcl/tk 8.3
rather than 8.2. Obviously, you have not read neither the changelog of
sather, nor debian-devel mailing list. I have indicated what the reasons were
for the NMU's after my initial upload of sather in a previous post (and I
*will* elaborate on that it seems) and also why I have not used tcl/tk 8.3.
In the sather changelog, it's seen how the build dependencies can be modified:
* Changed from tcl/tk 8.0 to 8.2 in System/Platforms/tcltk/Make.target.inc
And, I have effectively ignored the 1.2.1-4 NMU because
* Its changelog did not list any fixes.
* I have not been acknowledged in any way about the NMU. And it has
occurred only a very short time after my 1.2.1-3 upload which did fix bugs.
* It was not properly numbered.
Here is that glamorous changelog in which, IMHO, you demonstrate your
inability of social conduct. I include it here for the record.
sather (1.2.1-4) unstable; urgency=low
.
* Setting maintainer to Debian QA Group; no maintainer upload in 14
months, and current maintainer only did one release, until this month,
and
then he didn't properly acknowledge previous NMU's or even include
changes
from 1.2.1-2.3 except for the build-dependency fix, which included fixes
for a bunch of Debian Policy violations and lintian warnings
* Eray's sponsorship should be revoked and people should not sign his
packages.
* Acknowledge bugs fixed in previous NMU's.
(Closes: #116166, #105109, #115164, #112234, #74507, #81525)
(Not sure how katie decides if this is an NMU or not; by version number,
or Changed-By != Maintainer? Guess we'll find out.)
So, it does not seem that you have made any changes to the source code, yet
you'd like me to include these absurd statements in the changelog.
Please do not waste any more volunteer time[*] with your vicious acts. It
would be better used in making more contributions.[+]
I will continue maintaining sather. Please direct your requests through the
BTS.
At your service,
Thanks,
[*] Both yours and mine. See the notes below.
[+] Which means I will not reply any other post of yours under this thread.
Notes:
Here are dates of recent sather uploads. I had not looked at 1.2.1-2.3 when I
had sent my 1.2.1-3 to my sponsor because I could not have known its
existence. I was not acknowledged, and it's quite possible that Branden knew
I was trying to get a new version uploaded just when he did 1.2.1-2.3. I had
the opportunity to incorporate changes in 1.2.1-2.3 only in 1.2.1-5 version.
sather (1.2.1-5) unstable; urgency=low
- -- Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr> Wed, 24 Oct 2001 20:35:27
+0300
sather (1.2.1-4) unstable; urgency=low
-- Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr> Wed, 24 Oct 2001 17:51:33
+0300
sather (1.2.1-3) unstable; urgency=low
- -- Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr> Mon, 22 Oct 2001 01:26:32
+0300
sather (1.2.1-2.3) unstable; urgency=low
- -- Branden Robinson <branden@debian.org> Tue, 23 Oct 2001 07:59:32 -0500
sather (1.2.1-2.2) unstable; urgency=low
- -- John R. Daily <jdaily@progeny.com> Thu, 18 Oct 2001 11:19:40 -0500
sather_1.2.1-4 (Branden's wonderful NMU): Date: Wed, 24 Oct 2001 09:40:02
- -0500
- --
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE73S03fAeuFodNU5wRAqzoAJsEEINwwLX+Fu6IZxM/7ANbPpH0mwCfZOlZ
/iEowSTno1wwxnUA+IqcEAA=
=brd/
-----END PGP SIGNATURE-----
Reply to: