Bug#118969: Close?

2002-01-17 Thread Colin Watson
On Thu, Jan 17, 2002 at 09:22:35PM +, Stephen Stafford wrote:
> This looks like it is no longer the case.  Perhaps this bug should be 
> closed?  (I will not close it myself as I don't use zope at all, so 
> perhaps there are issues here I don't understand)

The conflict in zope was, as I understand it, to get appropriate python
dependencies in zope products. (See the zope Debian changelog.) I don't
think this bug should be closed until those are added, but it could be
downgraded to non-RC.

Actually, thinking about it, I'm not sure I understand why the conflicts
were added. zope-pythonmethod doesn't depend on python itself, but
depends on zope which depends on python for it. If it has
version-dependent code then this could be grounds for a bug, but it
doesn't look like grounds for a conflict to me. Could the zope
maintainer please comment on this?

Thanks,

-- 
Colin Watson  [EMAIL PROTECTED]



Bug#118969: Close?

2002-01-17 Thread Stephen Stafford
This looks like it is no longer the case.  Perhaps this bug should be 
closed?  (I will not close it myself as I don't use zope at all, so 
perhaps there are issues here I don't understand)

stephen:~$ sudo apt-get install zope-pythonmethod
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
  zope zope-bytecodehacks
The following NEW packages will be installed:
  zope zope-bytecodehacks zope-pythonmethod
0 packages upgraded, 3 newly installed, 0 to remove and 33  not 
upgraded.
Need to get 0B/2171kB of archives. After unpacking 12.0MB will be used.
Do you want to continue? [Y/n]
Selecting previously deselected package zope.
(Reading database ... 82528 files and directories currently installed.)
Unpacking zope (from .../zope_2.4.99beta3-0.2_i386.deb) ...
Selecting previously deselected package zope-bytecodehacks.
Unpacking zope-bytecodehacks (from 
.../zope-bytecodehacks_0.1.7-3_i386.deb) ...
Selecting previously deselected package zope-pythonmethod.
Unpacking zope-pythonmethod (from 
.../zope-pythonmethod_0.1.7-3_i386.deb) ...
Setting up zope (2.4.99beta3-0.2) ...
/usr/lib/zope/lib/python/Products/zbytecodehacks/closure.py:121: 
SyntaxWarning: local name 'n' in 'make_adder' shadows use of 'n' as 
global in nested scope 'adder'
  def make_adder(n):

WARNING: The default http port of ZServer has been changed to 9673,
  since 8080 conflicted with proxy server.
  If you're used to access Zope as http://localhost:8080/, you'll
  now have to use http://localhost:9673/.

  For further information about configuring ZServer, please refer
  to /usr/share/doc/zope/README.Debian.

Press Enter to continue:


We will now set up an administrator user in Zope.
Please choose a username and a password for the Zope administrator:
(This username and the password are only used inside Zope. They are
completely unrelated to your system's accounts. You can encrypt
the password in SHA, CRYPT or CLEARTEXT. You can limit the domains
from which the administrator can login into Zope, by providing
a list of domain names separated with spaces.

Username: stephen
Password:
Verify password:

Please choose a format from:

SHA - SHA-1 hashed password
CRYPT - UNIX-style crypt password
CLEARTEXT - no protection.

Encoding: SHA
Domain restrictions:
Starting Zope. done.

Setting up zope-bytecodehacks (0.1.7-3) ...

Setting up zope-pythonmethod (0.1.7-3) ...
For Zope to recognize the new package, it will need to be
restarted.

Restart Zope now? [Y]
Restarting Zope... done.

Cheers,
-- 
Stephen Stafford
finger [EMAIL PROTECTED] to get gpg public key



Bug#27273: marked as done (psplpr does not accept -P printer)

2002-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Jan 2002 15:06:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#27273: fixed in psptools 1.2.2-7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 30 Sep 1998 16:50:11 +
Received: (qmail 7535 invoked from network); 30 Sep 1998 16:50:03 -
Received: from pot.cnuce.cnr.it (HELO fly.cnuce.cnr.it) ([EMAIL PROTECTED])
  by master.debian.org with SMTP; 30 Sep 1998 16:50:03 -
Received: by fly.cnuce.cnr.it
id m0zOPRj-0008FdC
(Debian Smail-3.2.0.101 1997-Dec-17 #2); Wed, 30 Sep 1998 18:49:47 
+0200 (CEST)
Message-Id: <[EMAIL PROTECTED]>
Date: Wed, 30 Sep 1998 18:49:47 +0200 (CEST)
From: Francesco Potorti` <[EMAIL PROTECTED]>
To: Debian Linux bug list <[EMAIL PROTECTED]>
Subject: psplpr does not accept -P printer
Organization: CNUCE-CNR, Via S.Maria 36, Pisa - Italy +39-50-593211

Package: psptools
Version: 1.2.2-2
Severity: wishlist

Like in traditional lpr, psptools accepts "-Pprinter", but not "-P printer"
which, if i am not wrong, is  Posix conformant, and which is the way lpr on
linux works.


I think it should accept both, or only the latter.
---
Received: (at 27273-close) by bugs.debian.org; 17 Jan 2002 20:21:35 +
>From [EMAIL PROTECTED] Thu Jan 17 14:21:35 2002
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16RJ2V-0006Sp-00; Thu, 17 Jan 2002 14:21:35 -0600
Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian))
id 16RIng-0008KB-00; Thu, 17 Jan 2002 15:06:16 -0500
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.66 $
Subject: Bug#27273: fixed in psptools 1.2.2-7
Message-Id: <[EMAIL PROTECTED]>
Sender: James Troup <[EMAIL PROTECTED]>
Date: Thu, 17 Jan 2002 15:06:16 -0500
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
psptools, which has been installed in the Debian FTP archive:

psptools_1.2.2-7.diff.gz
  to pool/main/p/psptools/psptools_1.2.2-7.diff.gz
psptools_1.2.2-7.dsc
  to pool/main/p/psptools/psptools_1.2.2-7.dsc
psptools_1.2.2-7_all.deb
  to pool/main/p/psptools/psptools_1.2.2-7_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[EMAIL PROTECTED]> (supplier of updated psptools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 17 Jan 2002 03:07:26 +
Source: psptools
Binary: psptools
Architecture: source all
Version: 1.2.2-7
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Colin Watson <[EMAIL PROTECTED]>
Description: 
 psptools   - Tools for PostScript printers and devices
Closes: 27273 116263 128669 129287 129414 129437 129461
Changes: 
 psptools (1.2.2-7) unstable; urgency=low
 .
   * QA upload.
   * Accept '-P printer' as well as '-Pprinter' (closes: #27273).
   * Patches from Don (closes: #128669, #129287, #129414, #129437):
 - Accept --lp and --lpr as well as -lp and -lpr.
 - Don't output psplprdict lines unless the PageSetup option is set.
 - Fix typo, $addsc -> $adddsc.
   * Append a newline to --ppdpath output (#26831 part 1).
   * Supply default locations for BSD_LPR and SYSV_LP, avoiding
 build-dependencies. Touch configure in case make decides to run
 autoconf.
   * Save the current line before outputting %%BeginSetup, and output it
 after %%EndSetup, as otherwise it got overwritten in the process of
 reading features (closes: #116263, #129461).
   * Policy version 3.5.6.
   * Perl policy version 1.20:
 - Install libraries in /usr/share/perl5 rather than /usr/lib/perl5.
Files: 
 8be742c6dc1834f5e34074bf41f70083 641 text optional psptools_1.2.2-7.dsc
 d0ea548182e7d9ff2773af4128c99e8e 9197 text optional psptools_1.2.2-7.diff.gz
 a11696419bfcf2ef3e2503db7b7ee4dc 38700 text optional psptools_1.2.2-7_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG

Bug#129414: marked as done (psptools: try this patch -p0 on psplpr.pl.in instead of #129287)

2002-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Jan 2002 15:06:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#128669: fixed in psptools 1.2.2-7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 15 Jan 2002 23:01:23 +
>From [EMAIL PROTECTED] Tue Jan 15 17:01:23 2002
Return-path: <[EMAIL PROTECTED]>
Received: from butte_r2a1m65.in-tch.com (desktop) [216.166.189.65] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16Qca1-0007mp-00; Tue, 15 Jan 2002 17:01:21 -0600
Received: from theme by desktop with local (Exim 3.33 #1 (Debian))
id 16Qcax-0007s3-00
for <[EMAIL PROTECTED]>; Tue, 15 Jan 2002 16:02:19 -0700
To: [EMAIL PROTECTED]
Subject: psptools: try this patch -p0 on psplpr.pl.in instead of #129287
Message-Id: <[EMAIL PROTECTED]>
From: Don <[EMAIL PROTECTED]>
Date: Tue, 15 Jan 2002 16:02:19 -0700
Delivered-To: [EMAIL PROTECTED]

Package: psptools
Version: 1.2.2-6
Severity: normal

This diff supercedes my previous #129287 and #128669.

1. My custom output of allfeatures after the EndComments is removed.
I found the outstanding problem with some lines being dropped or duplicated 
in the final postscript output and want those to be fixed first.

2. There are some changes added that my solve that show stopper.
This works on some postscript. The input file is a big variable so a variety
of tests would be needed. Files from dvips could be a problem because
the psplpr tries to replace the dvips %%Feature: . The program maybe should
be used as a filter first and the output examined before printing and
before any regular use.

3. My perl is too poor to really figure this out.

4. If this is good enough then the following diff can be added to the
existing debian package building diff for pstools.


Don
[EMAIL PROTECTED]







--- psptools-1.2.2.orig/src/psplpr.pl.inWed Jul  3 04:49:28 1996
+++ psptools-1.2.2/src/psplpr.pl.in Tue Jan 15 15:34:56 2002
@@ -33,6 +33,8 @@
 require 'ppd.pl';
 require 'printer.pl';
 
+$used_prog_lpr = $prog_lpr; # default value (overridden by --output)
+
 #
 # tell_user(what)
 #
@@ -157,7 +159,7 @@
++$dictsz if $pagesetup;
 }
 
-return unless $dictsz;
+return unless ($dictsz > 1);
 
 if (!$nodsc) {
print "%%BeginResource: procset psplpr\n";
@@ -290,8 +292,8 @@
print "$who\n";
print "%%BoundingBox: 0 0 0 0\n%%Pages: 0\n";
print "%%EndComments\n";
-} else {
-print "%!\n";
+#} else {
+#print "%!\n";
 }
 
 if (!$doc) {
@@ -346,7 +348,7 @@
 }
 
 if (!$doc) {
-   print "psplprdict begin psplprsetup end\n";
+   print "psplprdict begin psplprsetup end\n" if 
countfeatures('PageSetup');
 }
 
 if ($doc && $dsc) {
@@ -507,22 +509,32 @@
 ignoredeps('ExitServer');
 ignoredeps('JCLSetup');
 
+local ($allout) = 0;
+
 $_ = readpsline($conformant);
 
 if (!$_) {
-   %all_options = outputallfeatures($nodsc, !$dirty, $safer,
-   $nonstd, $special);
+print "%!\n%%Creator: psplpr " . localtime() . "\n";
+print "%%EndComments\n";
+print "%\n% " . $myname . ": outputing all features... \n";
+   %all_options = outputallfeatures($nodsc, 666, $safer,
+   $nonstd, $special) unless $allout;
+$allout = 1;
 } else {
$_ =~ s/^\004//;
 
local($bad);
 
-   if ($dirty || ($bad = !/^%!PS/)) {
+   if ($dirty || ($bad = !/^%!PS-Adobe-3/)) {
+print;
+print "% " . $myname .": Looking for PS-Adobe-3.0 DSC conforming 
document...\n"; 
+print "% " . $myname .": with %%BeginProlog, %%BeginSetup, 
%%EndComments, etc. ... or\n";
+print "% " . $myname .": prepending! (not DSC compliant) at " . 
localtime() . "\n%\n";
local($first) = $_;
-
+
%all_options = outputallfeatures($nodsc, 0, $safer, $nonstd,
-   $special);
-
+   $special) unless $allout;
+$allout = 1;
if ($bad && !$dontglob) {
$glob = 1;
}
@@ -538,12 +550,23 @@
 
++$lineno;
 
+   
if (/^%%Begin/) {
$in_comment = 1;
} elsif (/^%%End/) {
$in_comment = 0;
}
 
+# begin 15jan02 change
+#if (/^%%EndComments/) {
+#print "%%Modified: by psplpr ".localtime()."\n" if $nodsc >= 
0;
+#print if $nodsc >= 

Bug#128669: marked as done (psptools fixes for psplpr blocking and usage problem)

2002-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Jan 2002 15:06:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#128669: fixed in psptools 1.2.2-7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 11 Jan 2002 01:55:45 +
>From [EMAIL PROTECTED] Thu Jan 10 19:55:45 2002
Return-path: <[EMAIL PROTECTED]>
Received: from btte_r1a1m236.in-tch.com (desktop) [216.166.185.236] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16Oqv2-Qj-00; Thu, 10 Jan 2002 19:55:45 -0600
Received: from theme by desktop with local (Exim 3.33 #1 (Debian))
id 16OqvW-0005AB-00
for <[EMAIL PROTECTED]>; Thu, 10 Jan 2002 18:56:14 -0700
To: [EMAIL PROTECTED]
Subject: psptools fixes for psplpr blocking and usage problem
Message-Id: <[EMAIL PROTECTED]>
From: Don <[EMAIL PROTECTED]>
Date: Thu, 10 Jan 2002 18:56:14 -0700
Delivered-To: [EMAIL PROTECTED]

Package: psptools
Version: 1.2.2-6
Severity: normal

This diff corrects the upstream psplpr source. The --lpr option is still needed
even when -Pprinter is used contrary to the man page. The --lpr is also
needed when using psplpr as a filter with the -o or --output option. They should
be mutually exclusive. Setting the default $used_lpr_prog = $lpr_prog at the
beginning of psplpr is one solution or just continue to use the --lpr option 
even if 
used as a filter. This diff makes psplpr work without exporting a PRINTER 
environment 
variable before starting the driver.

Ref: this fixes #26831 item 3 

Diff dated 10 Jan 02 to psptools.pl.in dated 3 July 1996:

818c818
< } elsif ($args[0] eq "-${lopt_prefix}lpr") {
---
> } elsif ($args[0] eq "--${lopt_prefix}lpr") {
820c820
< } elsif ($args[0] eq "-${lopt_prefix}lp") {
---
> } elsif ($args[0] eq "--${lopt_prefix}lp") {



Here is a small enhancement to fix outstanding report #27273

Diff dated 10 Jan 02 to psptools.pl.in dated 3 July 1996:

821a822,825
> } elsif ($args[0] eq "-${opt_prefix}P") {
> $printer = $args[1];
> usage(1) if (($printer = $args[1]) eq '');
> $used_prog_lpr = $prog_lpr;


Maybe some maintainer can plug these into the debian diff to
the source package instead of waiting for the source to change?

[EMAIL PROTECTED]
10 January 2002

---
Received: (at 128669-close) by bugs.debian.org; 17 Jan 2002 20:08:12 +
>From [EMAIL PROTECTED] Thu Jan 17 14:08:12 2002
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16RIpX-0004T3-00; Thu, 17 Jan 2002 14:08:11 -0600
Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian))
id 16RIng-0008Jk-00; Thu, 17 Jan 2002 15:06:16 -0500
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.66 $
Subject: Bug#128669: fixed in psptools 1.2.2-7
Message-Id: <[EMAIL PROTECTED]>
Sender: James Troup <[EMAIL PROTECTED]>
Date: Thu, 17 Jan 2002 15:06:16 -0500
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
psptools, which has been installed in the Debian FTP archive:

psptools_1.2.2-7.diff.gz
  to pool/main/p/psptools/psptools_1.2.2-7.diff.gz
psptools_1.2.2-7.dsc
  to pool/main/p/psptools/psptools_1.2.2-7.dsc
psptools_1.2.2-7_all.deb
  to pool/main/p/psptools/psptools_1.2.2-7_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[EMAIL PROTECTED]> (supplier of updated psptools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 17 Jan 2002 03:07:26 +
Source: psptools
Binary: psptools
Architecture: source all
Version: 1.2.2-7
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Colin Watson <[EMAIL PROTECTED]>
Description: 
 psptools   - Tools for PostScript printers and devices
Closes: 27273 116263 128669 129287 129414 129437 129461
Changes: 
 psptools (1.2.2-7) unstable; urgency=low
 .
   * QA upload.
   

Bug#129287: marked as done (psptools: try this patch -P0 on psplpr.pl.in, supercedes #128669)

2002-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Jan 2002 15:06:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#128669: fixed in psptools 1.2.2-7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 14 Jan 2002 23:29:42 +
>From [EMAIL PROTECTED] Mon Jan 14 17:29:42 2002
Return-path: <[EMAIL PROTECTED]>
Received: from butte_r2a1m39.in-tch.com (desktop) [216.166.189.39] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16QGXr-0006b4-00; Mon, 14 Jan 2002 17:29:41 -0600
Received: from theme by desktop with local (Exim 3.33 #1 (Debian))
id 16QGYS-0006wP-00
for <[EMAIL PROTECTED]>; Mon, 14 Jan 2002 16:30:16 -0700
To: [EMAIL PROTECTED]
Subject: psptools: try this patch -P0 on psplpr.pl.in, supercedes #128669
Message-Id: <[EMAIL PROTECTED]>
From: Don <[EMAIL PROTECTED]>
Date: Mon, 14 Jan 2002 16:30:16 -0700
Delivered-To: [EMAIL PROTECTED]

Package: psptools
Version: 1.2.2-6
Severity: normal

This diff supercedes my #128669. There are some corrections
to the original source with a few extras, for example: 

1. The psplpr looks for %!PS-Adobe-3.0 instead of %!PS on the first line.
The PPD allfeatures are more likely to be prepended to the beginning
of the file unless the file is really DSC compliant. The parser also must have
the %%BeginSetup and %%BeginProlog, for example, in a DSC document for those
types of PPD features. So, prepending allfeatures should be more reliable.

2. The psplprdict can cause errors and is probably not used much.
The psplprprolog should not now be included routinely. Anybody who
used the /pagesetup def could see a change.

3. The -P printer form is now included. That was an outstanding item.
The old -Pprinter is still there. The rest should be easy to see. 
My perl is still not good enough.


Don
[EMAIL PROTECTED]



--- psptools-1.2.2.orig/src/psplpr.pl.inWed Jul  3 04:49:28 1996
+++ psptools-1.2.2/src/psplpr.pl.in Mon Jan 14 16:24:08 2002
@@ -33,6 +33,8 @@
 require 'ppd.pl';
 require 'printer.pl';
 
+$used_prog_lpr = $prog_lpr; # default value (overridden by --output)
+
 #
 # tell_user(what)
 #
@@ -157,7 +159,7 @@
++$dictsz if $pagesetup;
 }
 
-return unless $dictsz;
+return unless ($dictsz > 1);
 
 if (!$nodsc) {
print "%%BeginResource: procset psplpr\n";
@@ -290,8 +292,8 @@
print "$who\n";
print "%%BoundingBox: 0 0 0 0\n%%Pages: 0\n";
print "%%EndComments\n";
-} else {
-print "%!\n";
+#} else {
+#print "%!\n";
 }
 
 if (!$doc) {
@@ -346,7 +348,7 @@
 }
 
 if (!$doc) {
-   print "psplprdict begin psplprsetup end\n";
+   print "psplprdict begin psplprsetup end\n" if 
countfeatures('PageSetup');
 }
 
 if ($doc && $dsc) {
@@ -507,22 +509,32 @@
 ignoredeps('ExitServer');
 ignoredeps('JCLSetup');
 
+local ($allout) = 0;
+
 $_ = readpsline($conformant);
 
 if (!$_) {
-   %all_options = outputallfeatures($nodsc, !$dirty, $safer,
-   $nonstd, $special);
+print "%!\n%%Creator: psplpr " . localtime() . "\n";
+print "%%EndComments\n";
+print "%\n% " . $myname . ": outputing all features... \n";
+   %all_options = outputallfeatures($nodsc, 666, $safer,
+   $nonstd, $special) unless $allout;
+$allout = 1;
 } else {
$_ =~ s/^\004//;
 
local($bad);
 
-   if ($dirty || ($bad = !/^%!PS/)) {
+   if ($dirty || ($bad = !/^%!PS-Adobe-3/)) {
+print;
+print "% " . $myname .": Looking for PS-Adobe-3.0 DSC conforming 
document...\n"; 
+print "% " . $myname .": with %%BeginProlog, %%BeginSetup, 
%%EndComments, etc. ... or\n";
+print "% " . $myname .": prepending! (not DSC compliant) at " . 
localtime() . "\n%\n";
local($first) = $_;
-
+
%all_options = outputallfeatures($nodsc, 0, $safer, $nonstd,
-   $special);
-
+   $special) unless $allout;
+$allout = 1;
if ($bad && !$dontglob) {
$glob = 1;
}
@@ -538,13 +550,19 @@
 
++$lineno;
 
+   
if (/^%%Begin/) {
$in_comment = 1;
} elsif (/^%%End/) {
$in_comment = 0;
}
 
-   if (/^%%BeginProlog/) {
+if (/^%%EndComments/) {
+print "%%Modified: by psplpr ".localtime()."\n" if $nodsc >= 0;
+   

Bug#129437: marked as done (psptools: try this patch first, cancels previous submits)

2002-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Jan 2002 15:06:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#128669: fixed in psptools 1.2.2-7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 16 Jan 2002 02:26:38 +
>From [EMAIL PROTECTED] Tue Jan 15 20:26:38 2002
Return-path: <[EMAIL PROTECTED]>
Received: from murphy.debian.org [216.234.231.6] 
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 16Qfmg-000720-00; Tue, 15 Jan 2002 20:26:38 -0600
Received: (qmail 2364 invoked from network); 16 Jan 2002 02:26:11 -
Received: from butte?r2a1m65.in-tch.com (HELO desktop) (216.166.189.65)
  by murphy.debian.org with SMTP; 16 Jan 2002 02:26:11 -
Received: from theme by desktop with local (Exim 3.33 #1 (Debian))
id 16QfiC-0008IP-00
for <[EMAIL PROTECTED]>; Tue, 15 Jan 2002 19:22:00 -0700
To: [EMAIL PROTECTED]
Subject: psptools: try this patch first, cancels previous submits
Message-Id: <[EMAIL PROTECTED]>
From: Don <[EMAIL PROTECTED]>
Date: Tue, 15 Jan 2002 19:22:00 -0700
Delivered-To: [EMAIL PROTECTED]


Package: psptools
Version: 2.2.1-6
Severity: normal


These are just the bug fixes. The previous additions are not
performing as expected. At least this works and does not affect
the upstream author's approach as my previous patches did.

This would be the best choice for a first attempt in my opinion.
This patch supercedes all of my previous patches.

Don
[EMAIL PROTECTED]


--- psptools-1.2.2.orig/src/psplpr.pl.inWed Jul  3 04:49:28 1996
+++ psptools-1.2.2/src/psplpr.pl.in Tue Jan 15 15:34:56 2002
@@ -33,6 +33,8 @@
 require 'ppd.pl';
 require 'printer.pl';
 
+$used_prog_lpr = $prog_lpr; # default value (overridden by --output)
+
 #
 # tell_user(what)
 #
@@ -157,7 +159,7 @@
++$dictsz if $pagesetup;
 }
 
-return unless $dictsz;
+return unless ($dictsz > 1);
 
 if (!$nodsc) {
print "%%BeginResource: procset psplpr\n";
@@ -346,7 +348,7 @@
 }
 
 if (!$doc) {
-   print "psplprdict begin psplprsetup end\n";
+   print "psplprdict begin psplprsetup end\n" if 
countfeatures('PageSetup');
 }
 
 if ($doc && $dsc) {
@@ -598,7 +625,7 @@
}
 
if (/^%%Page:/) {
-   local($addsc) = 0;
+   local($adddsc) = 0;
 
if (!$prolog_output) {
outputfeatures('Prolog', $nodsc, $safer, $nonstd,
@@ -815,10 +845,15 @@
$opt_output = $args[1];
usage(1) if (!$opt_output);
shift @args;
-} elsif ($args[0] eq "-${lopt_prefix}lpr") {
+} elsif ($args[0] eq "--${lopt_prefix}lpr") {
$used_prog_lpr = $prog_lpr;
-} elsif ($args[0] eq "-${lopt_prefix}lp") {
+} elsif ($args[0] eq "--${lopt_prefix}lp") {
$used_prog_lpr = $prog_lp;
+} elsif ($args[0] eq "-${opt_prefix}P") {
+$printer = $args[1];
+usage(1) if (($printer = $args[1]) eq '');
+$used_prog_lpr = $prog_lpr;
+shift @args;
 } elsif ($args[0] eq "--${lopt_prefix}verbose") {
 $opt_verbose = 1;
 } elsif ($args[0] eq "-${opt_prefix}q"

---
Received: (at 128669-close) by bugs.debian.org; 17 Jan 2002 20:08:12 +
>From [EMAIL PROTECTED] Thu Jan 17 14:08:12 2002
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16RIpX-0004T3-00; Thu, 17 Jan 2002 14:08:11 -0600
Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian))
id 16RIng-0008Jk-00; Thu, 17 Jan 2002 15:06:16 -0500
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.66 $
Subject: Bug#128669: fixed in psptools 1.2.2-7
Message-Id: <[EMAIL PROTECTED]>
Sender: James Troup <[EMAIL PROTECTED]>
Date: Thu, 17 Jan 2002 15:06:16 -0500
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
psptools, which has been installed in the Debian FTP archive:

psptools_1.2.2-7.diff.gz
  to pool/main/p/psptools/psptools_1.2.2-7.diff.gz
psptools_1.2.2-7.dsc
  to pool/main/p/psptools/psptools_1.2.2-7.dsc
psptools_1.2.2-7_all.deb
  to pool/main/p/psptools/psptools_1.2.2-7_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],

Bug#116263: marked as done (postscript line removed from input file.)

2002-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Jan 2002 15:06:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#129461: fixed in psptools 1.2.2-7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 19 Oct 2001 14:37:21 +
>From [EMAIL PROTECTED] Fri Oct 19 09:37:21 2001
Return-path: <[EMAIL PROTECTED]>
Received: from sdt.univ-brest.fr [194.167.226.209] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15uam1-0005fU-00; Fri, 19 Oct 2001 09:37:21 -0500
Received: from dormeur.sdt.univ-brest.fr (dormeur.univ-brest.fr 
[194.167.226.194])
  by sdt.univ-brest.fr (8.9.3/jtpda-5.3.1) with ESMTP id QAA07754
  ; Fri, 19 Oct 2001 16:37:15 +0200 (MET DST)
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 19 Oct 2001 16:38:31 +0200 (MEST)
From: [EMAIL PROTECTED]
Subject: postscript line removed from input file.
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]

Package: psptools
Version: 1.2.2-3

Hello,

In certain circumstances, psplpr can remove a postscript line and
duplicate another one.

I use debian 2.2r3 with security updates on i386.
This bug is present in both version 1.2.2-3 and 1.2.2-5.

Here is how to reproduce the bug :
zcat /usr/doc/gs-aladdin/examples/golfer.ps.gz >/tmp/golfer.ps
cd /tmp
/usr/bin/psplpr -k /tmp/hp1055c1.ppd  -o - -u '*OutputMode=Best' \
< golfer.ps > toto.ps

The ppd file comes from HP, and is the PPD for HP 1055cm printer for
windows 9x with EOL properly converted to unix convention.

A ``diff golfer.ps toto.ps'' shows that :
feature '*OutputMode=Best' was added
original line 74, containing ``u'' was removed
original line 75, containing ``0.9 g'' was added
diff golfer.ps toto.ps :
72a73
> %%BeginProlog
74c75,85
< u
---
> %%BeginSetup
> %%BeginFeature: *OutputMode Best
>   << /HWResolution [600 600]
> /PostRenderingEnhance true
> /PostRenderingEnhanceDetails
> << /PrintQuality 3
>   /Type 11 >>
>   >> setpagedevice
> %%EndFeature
> %%EndSetup
> 0.9 g

Christophe
-- 
char*p="[)1++11+(QI1)9191991)9)1)(II1)919Y91)9)1)(AK+9;991+3*(9I1*IY991)Q1\
)(1I1))A91991)Q1)(+)1)1++9;)Q1+(";main(_){while(*p){for(_=*p-32>>3;_;--_)
putchar(' ');if(!(_=*p++-32&7))putchar('\n');else while(_--)printf("_/");}}


---
Received: (at 129461-close) by bugs.debian.org; 17 Jan 2002 20:08:07 +
>From [EMAIL PROTECTED] Thu Jan 17 14:08:07 2002
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16RIpT-0004SG-00; Thu, 17 Jan 2002 14:08:07 -0600
Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian))
id 16RIng-0008K4-00; Thu, 17 Jan 2002 15:06:16 -0500
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.66 $
Subject: Bug#129461: fixed in psptools 1.2.2-7
Message-Id: <[EMAIL PROTECTED]>
Sender: James Troup <[EMAIL PROTECTED]>
Date: Thu, 17 Jan 2002 15:06:16 -0500
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
psptools, which has been installed in the Debian FTP archive:

psptools_1.2.2-7.diff.gz
  to pool/main/p/psptools/psptools_1.2.2-7.diff.gz
psptools_1.2.2-7.dsc
  to pool/main/p/psptools/psptools_1.2.2-7.dsc
psptools_1.2.2-7_all.deb
  to pool/main/p/psptools/psptools_1.2.2-7_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[EMAIL PROTECTED]> (supplier of updated psptools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 17 Jan 2002 03:07:26 +
Source: psptools
Binary: psptools
Architecture: source all
Version: 1.2.2-7
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Colin Watson <[EMAIL PROTECTED]>
Description: 
 psptools   - Tools for PostScript printers and devices
Closes: 27273 116263 128669 129287 129414 129437 129461
Changes: 
 pspto

Bug#129461: marked as done (psptools: lines still dropped and duplicated)

2002-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Jan 2002 15:06:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#129461: fixed in psptools 1.2.2-7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 16 Jan 2002 06:31:01 +
>From [EMAIL PROTECTED] Wed Jan 16 00:31:01 2002
Return-path: <[EMAIL PROTECTED]>
Received: from butte_r2a1m65.in-tch.com (desktop) [216.166.189.65] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16QjbA-cV-00; Wed, 16 Jan 2002 00:31:00 -0600
Received: from theme by desktop with local (Exim 3.33 #1 (Debian))
id 16Qjc7-0008Uh-00
for <[EMAIL PROTECTED]>; Tue, 15 Jan 2002 23:31:59 -0700
To: [EMAIL PROTECTED]
Subject: psptools: lines still dropped and duplicated
Message-Id: <[EMAIL PROTECTED]>
From: Don <[EMAIL PROTECTED]>
Date: Tue, 15 Jan 2002 23:31:59 -0700
Delivered-To: [EMAIL PROTECTED]

Package: psptools
Version: 1.2.2-6
Severity: normal

Here is the current problem after my patch #129437.

The psplpr is dropping lines and duplicating lines.
I have tried several solutions and have solved the
problem is some cases yet there could be consequences
because of the large variety of possible postscript.
This program should have an experienced perl programmer
who can follow the code to really fix this.

This could be my last report on this subject unless
eventually I learn enough perl before anybody fixes this.

Don
[EMAIL PROTECTED]


##

this shows a DSC (first line = %!PS) psplpr error
notice the %%BoundingBox is dropped and the %%%Creator is duplicated 

##

267c267,288
< %%%BoundingBox: 54 72 558 720
---
> %%BeginSetup
> %%BeginFeature: *OKColorRenderStyle Saturation
>   globaldict /[EMAIL PROTECTED] known not
> {globaldict begin /[EMAIL PROTECTED] 1 def end}if
>   globaldict /[EMAIL PROTECTED] get 5 ne{
> /DefaultColorRendering
> [null /Saturation null null null]
> globaldict /[EMAIL PROTECTED] get get
> dup null ne{
>   findcolorrendering pop /ColorRendering findresource /ColorRendering
>   defineresource setcolorrendering
> }{pop pop}ifelse
>   }if
>   globaldict /[EMAIL PROTECTED] get 1 eq{
> globaldict begin
>   /[EMAIL PROTECTED] {currentcolorrendering /CRDName get}stopped
> {pop pop null}if def
> end
>   }if
> %%EndFeature
> %%EndSetup
> %%%Creator: Mozilla (NetScape) HTML->PS



##

this shows a non DSC (first line = %!) psplpr error
notice the %%BoundingBox is dropped and the showsheet 
from mpage 2up is duplicated.

##

1a2,21
> %%BeginFeature: *OKColorRenderStyle Saturation
>   globaldict /[EMAIL PROTECTED] known not
> {globaldict begin /[EMAIL PROTECTED] 1 def end}if
>   globaldict /[EMAIL PROTECTED] get 5 ne{
> /DefaultColorRendering
> [null /Saturation null null null]
> globaldict /[EMAIL PROTECTED] get get
> dup null ne{
>   findcolorrendering pop /ColorRendering findresource /ColorRendering
>   defineresource setcolorrendering
> }{pop pop}ifelse
>   }if
>   globaldict /[EMAIL PROTECTED] get 1 eq{
> globaldict begin
>   /[EMAIL PROTECTED] {currentcolorrendering /CRDName get}stopped
> {pop pop null}if def
> end
>   }if
> %%EndFeature
> %!
267c287,306
< %%%BoundingBox: 54 72 558 720
---
> %%BeginSetup
> %%BeginFeature: *OKColorRenderStyle Saturation
>   globaldict /[EMAIL PROTECTED] known not
> {globaldict begin /[EMAIL PROTECTED] 1 def end}if
>   globaldict /[EMAIL PROTECTED] get 5 ne{
> /DefaultColorRendering
> [null /Saturation null null null]
> globaldict /[EMAIL PROTECTED] get get
> dup null ne{
>   findcolorrendering pop /ColorRendering findresource /ColorRendering
>   defineresource setcolorrendering
> }{pop pop}ifelse
>   }if
>   globaldict /[EMAIL PROTECTED] get 1 eq{
> globaldict begin
>   /[EMAIL PROTECTED] {currentcolorrendering /CRDName get}stopped
> {pop pop null}if def
> end
>   }if
> %%EndFeature
274a314,315
> %%EndSetup
> /showsheet { showpage } bind def

---
Received: (at 129461-close) by bugs.debian.org; 17 Jan 2002 20:08:07 +
>From [EMAIL PROTECTED] Thu Jan 17 14:08:07 2002
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16RIpT-0004SG-00; Thu, 17

psptools_1.2.2-7_i386.changes INSTALLED

2002-01-17 Thread Debian Installer

Installing:
psptools_1.2.2-7.diff.gz
  to pool/main/p/psptools/psptools_1.2.2-7.diff.gz
psptools_1.2.2-7.dsc
  to pool/main/p/psptools/psptools_1.2.2-7.dsc
psptools_1.2.2-7_all.deb
  to pool/main/p/psptools/psptools_1.2.2-7_all.deb
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 116263 128669 129287 129414 129437 129461 27273 


Thank you for your contribution to Debian.



Bug#129104: bug 129104 (buffer overflow + template reading in cgiemail)

2002-01-17 Thread Colin Watson
On Wed, Jan 16, 2002 at 04:17:25PM -0500, Thomas Smith wrote:
> I had released a new version with an almost-correct fix for the buffer
> overflow problem last night, and just looked at your mail to the bug
> this afternoon.  My fix was almost the same as yours; it used
> CGI_ERRMSG_MAX-1 instead of CGI_ERRMSG_MAX.  My next upload will use
> your correct version.

Right, that change isn't too big a deal.

> That leaves the other stuff...  the main problem is the template files,
> and I like the solution you suggested (restricting them to a specific
> directory).  The relevant code, I think, is in the
> cgi_standard_{email,echo,file} functions at the end of cgilib.c
> (beginning on line 1010).
> 
> Hmm, one problem that just occurred to me is that we can't easily make
> the location of the template files a compile-time option because people
> reconfigure their webservers to have different document roots, and the
> current design of cgiemail requires the template files to have
> PATH_TRANSLATEDs.  That means, I guess, that configuration file parsing
> might have to be added.

Yes, with the current design there really isn't any way to do it well
(including backwards compatibility), only patch it up. I suggest a
simple 'templatedir="/foo/bar/baz"' in a trusted place like
/etc/cgiemail.conf. That has the advantage that it can be parsed by the
shell, so you can easily set it with debconf and not clobber the old
setting on upgrades.

> Maybe could restrict to files with extension .CGIEMAIL_TEMPLATE.
> 
> Do you have any other ideas, or a preference between these two?

I think I prefer the directory idea: I usually prefer moving files
between directories to renaming files, somehow.

> The other issue is that it uses mkstemp() which is not very secure.  I
> don't guess that this is exploitable, but should be fixed at some point.

tmpnam(), rather - mkstemp() is fine. It's not very hard to convert from
one to the other with a bit of care, so I'll do that later.

-- 
Colin Watson  [EMAIL PROTECTED]