Bug#919287: FATAL: systemd-tmpfiles fails - Detected unsafe path transition

2019-01-14 Thread Robert Stone
Package: systemd
Version: 240-2

4.19.0-1 buster/sid

Since upgrading systemd to version 240-2, systemd-tmpfiles fails with error
message:-

Detected unsafe path transition

for every conf file in /usr/lib/tmpfiles.d.

Consequently, /tmp/.x11-unix is one of the paths NOT created which causes
gnome-shell to fail, filling up all the logfiles. See bug#918574.

Result:- my laptop is useless.

An urgent fix is requested.


Bug#918574: FATAL gnome-shell loops on boot filling up syslog

2019-01-07 Thread Robert Stone
Package: gnome-shell

Version: 3.30.1-2


Testing 4.19.0-1 (buster amd64)

Cannot boot my laptop. gnome-shell fills up syslog with these messages.

There may be some typo's as I had to write this down and go to the
local library.


gnome-shell[1458]: failed to bind to /tmp/.X11-unix/X1024: No such
file or directory

gnome-shell[1458]: failed to bind to /tmp/.X11-unix/X1025: No such
file or directory

These repeat with the X number increasing by one until I remove the
battery and then restart in recovery mode. The last lines are as
follows:-

gnome-shell[1458]: failed to bind to /tmp/.X11-unix/X120805: No such
file or directory

gnome-shell[1458]: failed to bind to /tmp/.X11-unix/X120806: No such
file or directory

kernel:[   134.986875] do.trap: 14 callbacks suppressed

kernel:[   134.986878] traps: gnome-shell[1458] trap int3
ip:7fe777dd4be5 sp:7ffdcca78120 error:0 in
libglib-2.0.so.5800.2[7fe777d9c000+7e00]

gnome-shell[1458]: failed to bind to /tmp/.X11-unix/X120807: No such
file or directory

gnome-shell[1458]: failed to bind to /tmp/.X11-unix/X120809: No such
file or directory

gnome-shell[1458]: failed to write pid to lock file /tmp/.X120810-lock

gnome-shell[1458]: Failed to create an X lock file

gnome-shell[1458]: Failed to start X Wayland


Please fix this ASAP. My laptop is dead in the water.


TIA,

Robert


Bug#758847: updating Encode::ConfigLocal

2014-08-21 Thread Robert Stone
Package: libencode-hanextra-perl
Version: 0.23-3

When I run the Perl code:

use strict;
use warnings;
use HTML::Form ();

my($f) = HTML::Form-parse(q{
form action=example, method=POST accept-charset=GB18030
input type=hidden name=example value=example
/form
}, URI-new(http://www.example.com/;));

print $f-click()-as_string();

I am given the error message:

Unknown encoding 'GB18030' at /usr/share/perl5/HTML/Form.pm ...

Installing lbencode-hanextra-perl does not resolve the issue until I
also run enc2xs -C so that Encode is informed which module provides
the GB18030 encoding.

It would be great if enc2xs -C was run after installation and
after removal of lbencode-hanextra-perl if there isn't some better way
to inform Encode of available encodings.  A web crawler application, for
example, is not well suited to know which encoding modules will be
required ahead of time.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#401132: Devel::Peek enhancement

2013-08-12 Thread Robert Stone
On Sun, Aug 11, 2013 at 11:18:06PM +0200, Dominic Hargreaves wrote:
 
 A fix for this has now been applied upstream:
 
 http://perl5.git.perl.org/perl.git/commit/da1929e7566d4399b20541f8609bd48b40663034
 
 As the bug is old and the severity is minor, I don't plan any backporting
 work, but hopefully this will meet your needs when it makes it into 
 Debian at some point?

That's great to hear.  I agree that a backport is unnecessary.
Thanks for your help!

-Robert


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#654280: installation-reports

2012-01-02 Thread Robert Stone
Package: installation-reports

Boot method: How did you boot the installer? CD? floppy? network?
CD
Image version: Full URL to image you downloaded is best
2.6.32-5amd64
Date: Date and time of the install
28/12/2011

Machine: Description of machine (eg, IBM Thinkpad R32)
Compaq Presario CQ43-111BR
Processor: Intel Pentium Dual-core P6200
Memory: 4Gb
Partitions: df -Tl will do; the raw partition table is preferred

root@roblaptop:/home/rob# df -Tl
Filesystem Type  1K-blocksUsed Available Use% Mounted on
/dev/sda1  ext39611492 4234932   4888320  47% /
tmpfs  tmpfs  5120   0  5120   0% /lib/init/rw
tmpfs  tmpfs385656 132385524   1% /run
udev   tmpfs   1922316 204   1922112   1% /dev
tmpfs  tmpfs771308   0771308   0% /run/shm
/dev/sda6  ext3  290639064  322204 275553240   1% /home
root@roblaptop:/home/rob#


Output of lspci -knn (or lspci -nn):
root@roblaptop:/home/rob# lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM
Controller [8086:0044] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation Core
Processor Integrated Graphics Controller [8086:0046] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: i915
00:16.0 Communication controller [0780]: Intel Corporation 5
Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
Subsystem: Hewlett-Packard Company Device [103c:3674]
00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series
Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series
Chipset High Definition Audio [8086:3b56] (rev 05)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 3 [8086:3b46] (rev 05)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 5 [8086:3b4a] (rev 05)
Kernel driver in use: pcieport
00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series
Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset
LPC Interface Controller [8086:3b09] (rev 05)
Subsystem: Hewlett-Packard Company Device [103c:3674]
00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series
Chipset 4 port SATA AHCI Controller [8086:3b29] (rev 05)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset
SMBus Controller [8086:3b30] (rev 05)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: i801_smbus
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136]
(rev 05)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: r8169
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:1629]
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
Device [10ec:5209] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:3674]
Kernel driver in use: rts_pstor
ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath
Architecture Generic Non-core Registers [8086:2c62] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:3674]
ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder [8086:2d01] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:3674]
ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link
0 [8086:2d10] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:3674]
ff:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI
Physical 0 [8086:2d11] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:3674]
ff:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved
[8086:2d12] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:3674]
ff:02.3 Host bridge [0600]: Intel Corporation Core Processor 

Bug#401132: Devel::Peek enhancement

2010-01-27 Thread Robert Stone
On Wed, Jan 27, 2010 at 12:31:44PM +0200, Niko Tyni wrote:
 
 Sorry for the lack of action on this.

No problem at all, thanks for looking into this.
 
 What's wrong with Devel::Peek:SvREFCNT(\%m) ?

\%m is a reference constructor, so SvREFCNT() ends up
reporting the reference count of that newly constructed SV.  The
situation can be illustrated with this small script:

#!/usr/bin/perl
use strict;
use warnings;
use Devel::Peek;
my %m = (a = 'b');
my $mr = \%m;
Devel::Peek::Dump($mr);
print Devel::Peek::SvREFCNT(\%m), \n;

From the Dump you can see that %m (the PVHV) has a refcount of
2, but Devel::Peek::SvREFCNT(\%m) reports 1.  The reason for this can
be illustrated by breaking that call up a little bit.  One would
normally expect that:

Devel::Peek::SvREFCNT(\%m)

should be equivalent to

my $tmp = \%m;
Devel::Peek::SvREFCNT($tmp)

which unsurprisingly reports a refcount of 1 for $tmp.  Nothing changes
when $tmp is an immediate, unlabeled value on the argument stack to
SvREFCNT() and I think that's expected and correct behavior.

The proposed patch solves this difficulty by always passing the
argument from Perl by reference and then unconditionally dereferencing
to access the target value.

Thanks,
Robert Stone



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#490862: HttpOnly support for APR::Request::Cookie

2008-07-14 Thread Robert Stone
Package: libapache2-request-perl
Version: 2.08-4
Severity: wishlist

As best I can tell libapreq2 has no direct way to add the
HttpOnly flag to the cookies it sets.  Although browser support for this
feature is not universal, it is a useful measure to limit the impact of
cross-site scripting attacks in supported browsers.
http://msdn.microsoft.com/en-us/library/ms533046.aspx provides
some info on the syntax and support.

Thanks,
Robert Stone
diff -Naur libapreq2-2.08.old/glue/perl/lib/Apache2/Cookie.pm libapreq2-2.08/glue/perl/lib/Apache2/Cookie.pm
--- libapreq2-2.08.old/glue/perl/lib/Apache2/Cookie.pm	2006-08-08 21:26:45.0 -0700
+++ libapreq2-2.08/glue/perl/lib/Apache2/Cookie.pm	2008-07-14 12:06:05.0 -0700
@@ -436,6 +436,20 @@
 
 
 
+=head2 httponly
+
+$cookie-httponly()
+$cookie-httponly($set)
+
+Get or set the HttpOnly flag for the cookie:
+
+$cookie-httponly(1);
+$is_HttpOnly = $cookie-httponly;
+$cookie-httponly(0);
+
+
+
+
 =head2 comment
 
 $cookie-comment()
diff -Naur libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod
--- libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod	2006-08-08 21:26:45.0 -0700
+++ libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod	2008-07-14 12:08:26.0 -0700
@@ -117,6 +117,8 @@
 
 =item -secure
 
+=item -httponly
+
 =item -version
 
 =item -path
@@ -235,6 +237,28 @@
 
 
 
+=head2 httponly
+
+$cookie-httponly()
+$cookie-httponly($set)
+
+
+Get/set the cookie's HttpOnly flag.
+
+=for example begin
+
+$cookie-httponly(1);
+ok $cookie-httponly == 1;
+
+=for example end
+
+=for example_testing
+$cookie-httponly(0);
+is $cookie-httponly, 0, HttpOnly;
+
+
+
+
 =head2 version
 
 $cookie-version()
diff -Naur libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs
--- libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs	2006-08-08 21:26:45.0 -0700
+++ libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs	2008-07-14 12:09:34.0 -0700
@@ -74,6 +74,23 @@
 RETVAL
 
 UV
+httponly(obj, val=NULL)
+APR::Request::Cookie obj
+SV *val
+
+  CODE:
+RETVAL = apreq_cookie_is_httponly(obj);
+if (items == 2) {
+if (SvTRUE(val))
+apreq_cookie_httponly_on(obj);
+else
+apreq_cookie_httponly_off(obj);
+}
+
+  OUTPUT:
+RETVAL
+
+UV
 version(obj, val=0)
 APR::Request::Cookie obj
 UV val
diff -Naur libapreq2-2.08.old/include/apreq_cookie.h libapreq2-2.08/include/apreq_cookie.h
--- libapreq2-2.08.old/include/apreq_cookie.h	2006-08-08 21:26:44.0 -0700
+++ libapreq2-2.08/include/apreq_cookie.h	2008-07-14 11:44:17.0 -0700
@@ -106,6 +106,27 @@
 APREQ_FLAGS_OFF(c-flags, APREQ_COOKIE_SECURE);
 }
 
+/** @return 1 if the HttpOnly flag is set, 0 otherwise. */
+static APR_INLINE
+unsigned apreq_cookie_is_httponly(const apreq_cookie_t *c) {
+return APREQ_FLAGS_GET(c-flags, APREQ_COOKIE_HTTPONLY);
+}
+
+/** Sets the cookie's HttpOnly flag, meaning it is not
+ *  accessible through client-side script in supported
+ *  browsers.
+ */
+static APR_INLINE
+void apreq_cookie_httponly_on(apreq_cookie_t *c) {
+APREQ_FLAGS_ON(c-flags, APREQ_COOKIE_HTTPONLY);
+}
+
+/** Turns off the cookie's HttpOnly flag. */
+static APR_INLINE
+void apreq_cookie_httponly_off(apreq_cookie_t *c) {
+APREQ_FLAGS_OFF(c-flags, APREQ_COOKIE_HTTPONLY);
+}
+
 
 /** @return 1 if the taint flag is set, 0 otherwise. */
 static APR_INLINE
diff -Naur libapreq2-2.08.old/include/apreq.h libapreq2-2.08/include/apreq.h
--- libapreq2-2.08.old/include/apreq.h	2006-08-08 21:26:44.0 -0700
+++ libapreq2-2.08/include/apreq.h	2008-07-14 11:35:52.0 -0700
@@ -179,6 +179,19 @@
  */
 #define APREQ_COOKIE_SECURE_MASK1
 
+/**
+ * Cookie's HttpOnly Bit 
+ * @see APREQ_FLAGS_OFF @see APREQ_FLAGS_ON
+ * @see APREQ_FLAGS_GET @see APREQ_FLAGS_SET
+ */
+#define APREQ_COOKIE_HTTPONLY_BIT14
+/**
+ * Cookie's HttpOnly Mask
+ * @see APREQ_FLAGS_OFF @see APREQ_FLAGS_ON
+ * @see APREQ_FLAGS_GET @see APREQ_FLAGS_SET
+ */
+#define APREQ_COOKIE_HTTPONLY_MASK1
+
 /** Character encodings. */
 typedef enum {
 APREQ_CHARSET_ASCII  =0,
diff -Naur libapreq2-2.08.old/library/cookie.c libapreq2-2.08/library/cookie.c
--- libapreq2-2.08.old/library/cookie.c	2006-08-08 21:26:44.0 -0700
+++ libapreq2-2.08/library/cookie.c	2008-07-14 12:36:45.0 -0700
@@ -118,6 +118,13 @@
 apreq_cookie_secure_off(c);
 return APR_SUCCESS;
 
+case 'h': /* httponly */
+if (vlen  0  *val != '0'  strncasecmp(off,val,vlen))
+apreq_cookie_httponly_on(c);
+else
+apreq_cookie_httponly_off(c

Bug#466298: more info

2008-02-25 Thread Robert Stone
I believe this is perl upstream bug
http://rt.perl.org/rt3/Public/Bug/Display.html?id=40654, which seems to
be fixed in perl v5.10.0.  Here is perhaps a simpler reproduction of the
issue: perl -e '(q{ab} x 10) =~ m{(?:ab*)*};'
The segfault is due to stack consumption and you can workaround
by setting RLIMIT_STACK higher than the default 8 megs via setrlimit(2)
(or ulimit -s unlimited from the shell).
-Robert



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



Bug#411947: HttpOnly support for Apache::Cookie

2007-02-21 Thread Robert Stone
Package: libapache-request-perl
Version: 1.33-1
Severity: wishlist

As best I can tell Apache::Cookie has no direct way to add the
HttpOnly flag to the cookies it sets.  Although browser support for this
feature is still spotty, it is a useful measure to limit the impact of
cross-site scripting attacks in supported browsers.
http://msdn.microsoft.com/workshop/author/dhtml/httponly_cookies.asp
provides some info on the intended syntax and support.

Thanks,
Robert Stone
diff -Naur libapache-request-perl-1.33.old/c/apache_cookie.c 
libapache-request-perl-1.33/c/apache_cookie.c
--- libapache-request-perl-1.33.old/c/apache_cookie.c   2004-11-26 
15:02:03.0 -0800
+++ libapache-request-perl-1.33/c/apache_cookie.c   2007-02-21 
15:42:01.924134177 -0800
@@ -59,6 +59,14 @@
}
retval = c-secure ? on : ;
break;
+case 'h':
+   if(val) {
+   c-httponly =
+   !strcaseEQ(val, off) 
+   !strcaseEQ(val, 0);
+   }
+   retval = c-httponly ? on : ;
+   break;
 default:
ap_log_rerror(APC_ERROR,
  [libapreq] unknown cookie pair: `%s' = `%s', key, val);
@@ -78,6 +86,7 @@
 c-r = r;
 c-values = ap_make_array(r-pool, 1, sizeof(char *));
 c-secure = 0;
+c-httponly = 0;
 c-name = c-expires = NULL;
 
 c-domain = NULL;
@@ -201,6 +210,9 @@
 if (c-secure) {
cookie_push_arr(values, secure);
 }
+if(c-httponly) {
+   cookie_push_arr(values, HttpOnly);
+}
 
 cookie = ap_pstrcat(p, escape_url(p, c-name), =, NULL);
 for (i=0; ic-values-nelts; i++) {
diff -Naur libapache-request-perl-1.33.old/c/apache_cookie.h 
libapache-request-perl-1.33/c/apache_cookie.h
--- libapache-request-perl-1.33.old/c/apache_cookie.h   2004-11-26 
15:02:03.0 -0800
+++ libapache-request-perl-1.33/c/apache_cookie.h   2007-02-21 
15:45:47.076077858 -0800
@@ -29,6 +29,7 @@
 char *expires;
 char *path;
 int secure;
+int httponly;
 } ApacheCookie;
 
 #ifdef  __cplusplus
diff -Naur libapache-request-perl-1.33.old/Cookie/Cookie.pm 
libapache-request-perl-1.33/Cookie/Cookie.pm
--- libapache-request-perl-1.33.old/Cookie/Cookie.pm2004-11-26 
15:02:04.0 -0800
+++ libapache-request-perl-1.33/Cookie/Cookie.pm2007-02-21 
17:27:45.176540603 -0800
@@ -146,6 +146,13 @@
  my $secure = $cookie-secure;
  $cookie-secure(1);
 
+=head2 httponly
+
+Get or set the HttpOnly flag for the cookie:
+
+ my $HttpOnly = $cookie-httponly;
+ $cookie-httponly(1);
+
 =back
 
 =head1 CAVEATS
diff -Naur libapache-request-perl-1.33.old/Cookie/Cookie.xs 
libapache-request-perl-1.33/Cookie/Cookie.xs
--- libapache-request-perl-1.33.old/Cookie/Cookie.xs2004-12-06 
06:49:46.0 -0800
+++ libapache-request-perl-1.33/Cookie/Cookie.xs2007-02-21 
17:28:25.687726275 -0800
@@ -130,6 +130,9 @@
 #define ApacheCookie_secure(c, val) \
 ApacheCookie_attr(c, secure, val)
 
+#define ApacheCookie_httponly(c, val) \
+ApacheCookie_attr(c, httponly, val)
+
 MODULE = Apache::CookiePACKAGE = Apache::Cookie   PREFIX = ApacheCookie_
 
 PROTOTYPES: DISABLE 
@@ -297,6 +300,11 @@
 Apache::Cookie c
 char *val
 
+char *
+ApacheCookie_httponly(c, val=NULL)
+Apache::Cookie c
+char *val
+
 void
 ApacheCookie_bake(c)
 Apache::Cookie c
diff -Naur libapache-request-perl-1.33.old/libapreq.pod 
libapache-request-perl-1.33/libapreq.pod
--- libapache-request-perl-1.33.old/libapreq.pod2004-11-26 
15:02:04.0 -0800
+++ libapache-request-perl-1.33/libapreq.pod2007-02-21 17:26:16.902210826 
-0800
@@ -243,6 +243,12 @@
 of IOn or IOff.  
 The default is IOff.
 
+=item -httponly
+
+Sets the IHttpOnly field to true or false using a given string value
+of IOn or IOff.  
+The default is IOff.
+
 =back
 
 Example:


Bug#401132: Devel::Peek enhancement

2006-11-30 Thread Robert Stone
Package: perl
Version: 5.8.8-6.1

I recently discovered that Devel::Peek's SvREFCNT, SvREFCNT_inc
and SvREFCNT_dec functions are not as flexible as the XS functions that
they wrap.  In XS where you wish to get the reference count of an hash
your HV * pointer will cast to an SV * when passed as an argument to
SvREFCNT().  In Perl using Devel::Peek:SvREFCNT(%m) does not return the
reference count of %m, but rather treats %m as a list of arguments to
the function causing a runtime error.  I believe the intent of the code was
to return the reference count of the parameter passed and the difference
between Perl Prototypes and C casting was overlooked.
A small patch (attached) will extend these three functions to
work on any perl variable type.  This could break code in cases where
users expect an array of one member passed to these functions to operate
on that only member of the array, but for all other data types (and
arrays of any other length) these functions currently croak.  Possibly a
new family of functions is warranted to maintain reverse compatibility
in the single element array case in the existing functions, but it is
not my place to make that judgement.
Thanks,
Robert Stone
diff -Naur perl-5.8.8.deborig/ext/Devel/Peek/Peek.xs 
perl-5.8.8/ext/Devel/Peek/Peek.xs
--- perl-5.8.8.deborig/ext/Devel/Peek/Peek.xs   2005-06-07 09:27:36.0 
-0700
+++ perl-5.8.8/ext/Devel/Peek/Peek.xs   2006-11-30 15:49:39.837153699 -0800
@@ -383,15 +383,22 @@
 I32
 SvREFCNT(sv)
 SV *   sv
+PROTOTYPE: [EMAIL PROTECTED]*]
+PPCODE:
+{
+RETVAL = SvREFCNT(SvRV(sv)) - 1; // -1 because our ref doesn't count
+PUSHi(RETVAL);
+}
 
 # PPCODE needed since otherwise sv_2mortal is inserted that will kill the 
value.
 
 SV *
 SvREFCNT_inc(sv)
 SV *   sv
+PROTOTYPE: [EMAIL PROTECTED]*]
 PPCODE:
 {
-RETVAL = SvREFCNT_inc(sv);
+RETVAL = SvREFCNT_inc(SvRV(sv));
 PUSHs(RETVAL);
 }
 
@@ -400,9 +407,10 @@
 void
 SvREFCNT_dec(sv)
 SV *   sv
+PROTOTYPE: [EMAIL PROTECTED]*]
 PPCODE:
 {
-SvREFCNT_dec(sv);
+SvREFCNT_dec(SvRV(sv));
 PUSHs(sv);
 }
 


Bug#307346: Some images packaged with apache-common not in apache2-common

2006-11-13 Thread Robert Stone
That's a perfectly valid response.  If a stock apache doesn't
refer to the content, then there isn't a strong reason to make sure
they are available.
Thanks for the update.
-Robert

On Sun, Nov 12, 2006 at 02:42:11PM +0100, Thijs Kinkhorst wrote:
 Hi,
 
  There are a number of Debian and Linux banners that the
  apache-common package provides that were overlooked by the apache2-common
  package.  I don't really know if they should be provided by this package,
  but thought it might have been an oversight.
 
 Thanks for your report. I indeed do think that these images do not
 belong in the Apache package; it seems to be a rather arbitrary place to
 package such stuff. Also notice that Apache doesn't provide a default
 web page anymore that includes any such logo's.
 
 I propose to close this bug.
 
 
 Thijs




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



Bug#307346: Some images packaged with apache-common not in apache2-common

2005-05-02 Thread Robert Stone
Package: apache2-common
Version: 2.0.54-2
Severity: minor

There are a number of Debian and Linux banners that the
apache-common package provides that were overlooked by the apache2-common
package.  I don't really know if they should be provided by this package,
but thought it might have been an oversight.

This is the list of images:
icons/debian/banner_a.gif
icons/debian/banner_h.gif
icons/debian/banner_h.html
icons/debian/banner_v.gif
icons/debian/banner_v.html
icons/debian/banner_v.jpg
icons/debian/button-1.gif
icons/debian/openlogo-100.jpg
icons/debian/openlogo-25.jpg
icons/debian/openlogo-50.jpg
icons/debian/openlogo-75.jpg
icons/debian/openlogo-nd-100.jpg
icons/debian/openlogo-nd-25.jpg
icons/debian/openlogo-nd-50.jpg
icons/debian/openlogo-nd-75.jpg
icons/jhe061.gif
icons/linuxins.jpg
icons/linux-pengo-small.gif
icons/linux-small.jpg
icons/logo-sm2.gif
icons/penguinlogo1.jpg
icons/pp-2.gif


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



Bug#299017: please include Thawte SSL Domain CA

2005-03-10 Thread Robert Stone
Package: ca-certificates
Version: 20040809

The ca-certificates package does not include the Thawte SSL
Domain CA from Thawte's root certificate set.  Thawte appears to be
issuing server certificates for live e-commerce sites from this root, so
I think we may want to include it.
http://www.thawte.com/roots/index.html provided me with a root set
that included this certificate.
Thanks,
Robert Stone


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