Bug#899313: viking fails to install

[Paddy Smith]

Package: viking
Version: 1.6.2-3+b2
Severity: important

Dear Maintainer,

I have a problem installing and/or using viking on my system

If I try to install the package I get the following:

The following packages have unmet dependencies:
 viking : Depends: libmapnik3.0 (>= 3.0.20+ds) but it is not going to be
installed:

The aptitude solver suggests downgrading:

 Downgrade the following packages:
1) libboost-regex1.62.0 [1.62.0+dfsg-5.1 (now, unstable) ->
1.62.0+dfsg-5+b1 (testing)]

However, if I do this the packages installs successfully, but then fails to
start. When I try to run viking I get the following:

viking: symbol lookup error: /usr/lib/libmapnik.so.3.0: undefined symbol:
_ZNK5boost16re_detail_10620031icu_regex_traits_implementation12do_transformEPKiS3_PKN6icu_608CollatorE

So I am not sure if the problem is in the viking package, or a bug in
libmapnik3.0 or libboost1.62 - but something is misconfigured somewhere



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.9-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages viking depends on:
ii  gpsbabel 1.5.4-2
ii  libatk1.0-0  2.28.1-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcurl3-gnutls  7.60.0-1
ii  libexpat12.2.5-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libfribidi0  0.19.7-2
ii  libgcc1  1:8.1.0-3
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libgexiv2-2  0.10.8-1
ii  libglib2.0-0 2.56.1-2
ii  libgps23 3.17-5+b1
ii  libgtk2.0-0  2.24.32-1
ii  libicu60 60.2-6
ii  libmagic11:5.33-2
pn  libmapnik3.0 
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libpangoft2-1.0-01.42.1-1
ii  libsqlite3-0 3.23.1-1
ii  libstdc++6   8.1.0-3
ii  libx11-6 2:1.6.5-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages viking recommends:
pn  expect-dev  

Versions of packages viking suggests:
pn  gpsd  

Bug#888952: nvidia-driver and opencl

[Paddy Steed]

How can I unsubscribe from this list? For years now, I have been asking how to 
unsubscribe and nothing has worked.

> On 5 Feb 2018, at 07:54, Andreas Beckmann  wrote:
> 
> On 2018-02-05 08:44, Hiromasa YOSHIMOTO wrote:
>> Although nvidia-modprobe is setuided, it seems
>> not to work properly as expected. 
> 
> Which is probably caused by some hardening configuration on your
> systems. Is there anything about nvidia-modprobe in the logfiles in
> /var/log/ ?
> 
> 
> Andreas
> 

Bug#888035: nvidia-kernel-dkms: Fails to build against linux-image-4.14.0-0.bpo.2-amd64 (stretch+backports)

[Paddy Steed]

Again. How can I unsubscribe from these emails?

> On 22 Jan 2018, at 20:41, Guilherme Gondim  wrote:
> 
> Oh, amazing! It isn't showing up in my package list yet. I will wait for it. 
> Thank you Andreas!
> 
>  Original Message 
>> On January 22, 2018 6:37 PM, Andreas Beckmann  wrote:
>> 
>> On 2018-01-22 21:21, Guilherme Gondim wrote:
>> Oh, I see. Didn't notice that. Should I request for a backport? Currently it 
>> isn't backported.
>>  
>> 384.111-3~bpo9+1 is there for more than a day already (well, about 1 day
>> 4 hours to be exact :-)
>>  
>>  
>> Andreas
> 

Bug#881744: virtualbox-dkms and virtualbox-guest-dkms fail to build on kernel 4.14.0

[Paddy Smith]

Package: virtualbox-dkms
Version: 5.2.0-dfsg-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

virtualbox dkms packages fail to build on kernel 4.14.0

apt output:

--
Deleting module version: 5.2.0
completely from the DKMS tree.
--
Done.
Unpacking virtualbox-dkms (5.2.0-dfsg-5) over (5.2.0-dfsg-5) ...
Preparing to unpack .../virtualbox-guest-dkms_5.2.0-dfsg-5_all.deb ...

--
Deleting module version: 5.2.0
completely from the DKMS tree.
--
Done.
Unpacking virtualbox-guest-dkms (5.2.0-dfsg-5) over (5.2.0-dfsg-5) ...
Setting up virtualbox-dkms (5.2.0-dfsg-5) ...
Loading new virtualbox-5.2.0 DKMS files...
Building for 4.14.0-towo.1-siduction-amd64
Building initial module for 4.14.0-towo.1-siduction-amd64
Error! Bad return status for module build on kernel: 4.14.0-towo.1-siduction-
amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/5.2.0/build/make.log for more information.
Job for virtualbox.service failed because the control process exited with error
code.
See "systemctl  status virtualbox.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2017-11-14 13:20:14 AST; 9ms
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 14163 ExecStart=/etc/init.d/virtualbox start (code=exited,
status=1/FAILURE)

Nov 14 13:20:14 greyhame virtualbox[14163]: Loading VirtualBox kernel
modules...No suitable module for running kernel found ... failed!
Nov 14 13:20:14 greyhame virtualbox[14163]:  failed!
Nov 14 13:20:14 greyhame systemd[1]: virtualbox.service: Child 14163 belongs to
virtualbox.service
Nov 14 13:20:14 greyhame systemd[1]: virtualbox.service: Control process
exited, code=exited status=1
Nov 14 13:20:14 greyhame systemd[1]: virtualbox.service: Got final SIGCHLD for
state start.
Nov 14 13:20:14 greyhame systemd[1]: virtualbox.service: Failed with result
'exit-code'.
Nov 14 13:20:14 greyhame systemd[1]: virtualbox.service: Changed start ->
failed
Nov 14 13:20:14 greyhame systemd[1]: virtualbox.service: Job
virtualbox.service/start finished, result=failed
Nov 14 13:20:14 greyhame systemd[1]: Failed to start LSB: VirtualBox Linux
kernel module.
Nov 14 13:20:14 greyhame systemd[1]: virtualbox.service: Unit entered failed
state.
Setting up virtualbox-guest-dkms (5.2.0-dfsg-5) ...
Loading new virtualbox-guest-5.2.0 DKMS files...
Building for 4.14.0-towo.1-siduction-amd64
Building initial module for 4.14.0-towo.1-siduction-amd64
Error! Bad return status for module build on kernel: 4.14.0-towo.1-siduction-
amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/5.2.0/build/make.log for more
information.

===
Contents of make.log (virtualbox):


/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.c: In
function ‘vboxNetFltLinuxSkBufFromSG’:
/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-
linux.c:741:24: error: ‘SKB_GSO_UDP’ undeclared (first use in this function);
did you mean ‘SKB_GSO_ESP’?
 fGsoType = SKB_GSO_UDP;
^~~
SKB_GSO_ESP
/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-
linux.c:741:24: note: each undeclared identifier is reported only once for each
function it appears in
In file included from
/var/lib/dkms/virtualbox/5.2.0/build/include/iprt/types.h:29:0,
 from /var/lib/dkms/virtualbox/5.2.0/build/r0drv/linux/the-
linux-kernel.h:34,
 from
/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.c:24:
/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.c: In
function ‘vboxNetFltLinuxCanForwardAsGso’:
/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-
linux.c:1276:53: error: ‘SKB_GSO_UDP’ undeclared (first use in this function);
did you mean ‘SKB_GSO_ESP’?
 if (RT_UNLIKELY( skb_shinfo(pSkb)->gso_type & ~(SKB_GSO_UDP |
SKB_GSO_DODGY | SKB_GSO_TCPV6 | SKB_GSO_TCPV4) ))
 ^
/var/lib/dkms/virtualbox/5.2.0/build/include/iprt/cdefs.h:1631:53: note: in
definition of macro ‘RT_UNLIKELY’
 #  define RT_UNLIKELY(expr) __builtin_expect(!!(expr), 0)
 ^~~~
/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.c: In
function ‘vboxNetFltLinuxForwardToIntNetInner’:
/var/lib/dkms/virtualbox/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-
linux.c:1526:47: error: ‘SKB_GSO_UDP’ undeclared (first use in this function);
did you mean ‘SKB_GSO_ESP’?
 if (   (skb_shinfo(pBuf)->gso_type & 

Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

[Paddy Steed]

Why do I keep on getting these emails, please for the love of God someone
tell me how to unsubscribe from whatever nightmare list this is.

On 26 Oct 2017 11:57, "Vincent Lefevre"  wrote:

Package: libgles1-glvnd-nvidia
Version: 375.82-6
Severity: grave
Justification: renders package unusable

In the upgrade to 375.82-6:

Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ...
Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb ...
Unpacking nvidia-legacy-check (375.82-6) over (375.82-5) ...
Preparing to unpack .../35-nvidia-driver-libs-i386_375.82-6_i386.deb ...
Unpacking nvidia-driver-libs-i386:i386 (375.82-6) over (375.82-5) ...
Processing triggers for mime-support (3.60) ...
Setting up libnvidia-eglcore:amd64 (375.82-6) ...
Setting up libnvidia-eglcore:i386 (375.82-6) ...
Processing triggers for desktop-file-utils (0.23-2) ...
Setting up libnvidia-glcore:amd64 (375.82-6) ...
Setting up libnvidia-glcore:i386 (375.82-6) ...
Processing triggers for libc-bin (2.24-17) ...
Setting up nvidia-egl-common (375.82-6) ...
Setting up nvidia-vulkan-common (375.82-6) ...
Setting up nvidia-legacy-check (375.82-6) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up nvidia-alternative (375.82-6) ...
Processing triggers for nvidia-alternative (375.82-6) ...
Setting up libglx-nvidia0:amd64 (375.82-6) ...
Setting up nvidia-vulkan-icd:amd64 (375.82-6) ...
Setting up nvidia-kernel-support (375.82-6) ...
Setting up nvidia-vdpau-driver:amd64 (375.82-6) ...
Setting up libegl-nvidia0:amd64 (375.82-6) ...
Setting up libegl-nvidia0:i386 (375.82-6) ...
Setting up libgles-nvidia2:i386 (375.82-6) ...
Setting up libgles-nvidia2:amd64 (375.82-6) ...
Setting up libnvidia-cfg1:amd64 (375.82-6) ...
Setting up libnvidia-cfg1:i386 (375.82-6) ...
dpkg: dependency problems prevent configuration of
libgles1-glvnd-nvidia:amd64:
 libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is
unpacked but not configured.
  libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of
libgles1-glvnd-nvidia:i386:
 libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and is
unpacked but not configured.
  libgles1-glvnd-nvidia:i386 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:i386 (--configure):
 dependency problems - leaving unconfigured
Setting up nvidia-kernel-dkms (375.82-6) ...
[...]
Setting up libnvidia-ml1:amd64 (375.82-6) ...
dpkg: dependency problems prevent configuration of libgles-nvidia1:amd64:
 libgles-nvidia1:amd64 depends on libgles1 (>= 0.2.999) |
libgles1-glvnd-nvidia; however:
  Package libgles1 is not installed.
  Package libgles1-glvnd-nvidia:amd64 which provides libgles1 is not
configured yet.
  Package libgles1-glvnd-nvidia:amd64 is not configured yet.

dpkg: error processing package libgles-nvidia1:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgles-nvidia1:i386:
 libgles-nvidia1:i386 depends on libgles1 (>= 0.2.999) |
libgles1-glvnd-nvidia; however:
  Package libgles1-glvnd-nvidia:i386 which provides libgles1 is not
configured yet.
  Package libgles1-glvnd-nvidia:i386 is not configured yet.

dpkg: error processing package libgles-nvidia1:i386 (--configure):
 dependency problems - leaving unconfigured
Setting up libgl1-nvidia-glvnd-glx:amd64 (375.82-6) ...
Setting up xserver-xorg-video-nvidia (375.82-6) ...
Setting up nvidia-driver-bin (375.82-6) ...
Setting up libglx-nvidia0:i386 (375.82-6) ...
Setting up nvidia-vulkan-icd:i386 (375.82-6) ...
Setting up nvidia-egl-icd:i386 (375.82-6) ...
Setting up nvidia-egl-icd:amd64 (375.82-6) ...
Setting up libgl1-nvidia-glvnd-glx:i386 (375.82-6) ...
Setting up nvidia-driver-libs:amd64 (375.82-6) ...
Setting up nvidia-driver-libs:i386 (375.82-6) ...
Setting up nvidia-driver (375.82-6) ...
Setting up nvidia-driver-libs-i386:i386 (375.82-6) ...
Processing triggers for glx-alternative-nvidia (0.8.0) ...
Processing triggers for libc-bin (2.24-17) ...
Processing triggers for update-glx (0.8.0) ...
Processing triggers for glx-alternative-nvidia (0.8.0) ...
Processing triggers for libc-bin (2.24-17) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-1-amd64
Errors were encountered while processing:
 libgles1-glvnd-nvidia:amd64
 libgles1-glvnd-nvidia:i386
 libgles-nvidia1:amd64
 libgles-nvidia1:i386
[...]
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of
libgles1-glvnd-nvidia:amd64:
 libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is
unpacked but not configured.
  libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:amd64 (--configure):
 dependency problems - leaving 

Bug#869783: Security - upgrade NVidia driver to 375.82 in stable.

[Paddy Steed]

I keep on getting emails for Nvidia stuff, how can I stop this?

On 26 Jul 2017 23:21, "Luca Boccassi"  wrote:

Control: tags -1 pending

On Wed, 2017-07-26 at 13:48 +0200, Julien Aubin wrote:
> Package: nvidia-driver
> Version: 375.66-2
> Severity: critical
>
> Hi,
>
> NVidia driver is currently targetted by several critical
> vulnerabilities as
> disclosed by NVidia. Full description there :
> https://nvidia.custhelp.com/app/answers/detail/a_id/4525
>
> Some of the vulnerabilities affect Linux users with issues including
> privilege escalation and denial of service.
>
> Updated package is 375.82.
>
> Could you please release quickly the updated packages ?
>
> Thanks

Uploaded to unstable.

Dear Security Team,

CVE-2017-6257 and CVE-2017-6259 affect Stretch - how would you like to
see this handled?

- upload through security
- upload through p/u
- ignore

I have tested this new version on a Stretch amd64 desktop and didn't
encounter any issue.

The debdiff from 375.66-2~deb9u1 to 375.82-1 is attached.

Apart from the new upstream version, the other bug fixes are:

- update binary library blobs symbols files reflecting upstream changes
- allow parallel dkms builds if requested (#864639)
- re-allow dkms ccache usage if enabled
- switch watch files protocol to https, upstream deprecated ftp
(#868815)
- mark the dkms modules as build-tested on kernel 4.11
- add support for buster in the nvidia-detect script (#866126)

Kind regards,
Luca Boccassi

Bug#744125: spiped: The version number in the man pages is 1.3.0 when the version distrubuted is 1.3.1-1

[Paddy Steed]

Package: spiped
Version: 1.3.1-1
Severity: minor

Dear Maintainer,

In the man pages spiped(1) and spipe(1) the version number shown is
incorrect, it shows 1.3.0 when it should be 1.3.1-1. There is no version
flag in the spiped or spipe programs and therefore I think I is likely
people will check the version of the program using the man pages.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages spiped depends on:
ii  libc62.18-4
ii  libssl1.0.0  1.0.1g-2

spiped recommends no packages.

spiped suggests no packages.

-- no debconf information


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

Bug#613538: kde-plasma-desktop: Desktop forgets icon-positions and rearranges them on each login

[paddy]

Package: kde-plasma-desktop
Version: 5:66
Severity: important

KDE4 Desktop forgets Icon-Positions after logout and rearranges (stacks)
them from the top-left after each login. Yes, it's set to unsorted.
Seems as it has something to to do with:

https://bugs.kde.org/show_bug.cgi?id=242073
https://bugs.kde.org/show_bug.cgi?id=227157

The desktop is somekind of unuseable that way, several postings
in different forums say, the bug is fixed in KDE 4.5.3.



-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kde-plasma-desktop depends on:
ii  hal   0.5.14-3   Hardware Abstraction Layer
ii  kdebase-apps  4:4.4.5-2  base applications from the officia
ii  kdebase-runtime   4:4.4.5-1  runtime components from the offici
ii  kdebase-workspace 4:4.4.5-7  KDE Plasma Workspace components
ii  plasma-desktop4:4.4.5-7  The KDE Plasma workspace for deskt

Versions of packages kde-plasma-desktop recommends:
pn  kdm   none (no description available)
ii  xserver-xorg  1:7.5+8the X.Org X server

Versions of packages kde-plasma-desktop suggests:
ii  kde-l10n-de [kde-l10n]4:4.4.5-1  German (de) localization files for

-- no debconf information



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

Bug#611989: libdecodeqr-examples: fails to decode sample image debian.org.qr.jpg STATUS=2089

[Paddy Smith]

Package: libdecodeqr-examples
Version: 0.9.3-4
Severity: important


Hi,

I've been trying to use libdecodeqr-simpletest. It works with three of 
the supplied sample images, but then

$ ./libdecodeqr-simpletest ../../../img/debian.org.qr.jpg
libdecodeqr version 0.9.3 ($Rev: 42 $)
STATUS=2089


Hit any key to end.
$

and a test using qrencode

$ qrencode -o test.png 
testing 1 2 3 ...
$ libdecodeqr-simpletest test.png 
libdecodeqr version 0.9.3 ($Rev: 42 $)
STATUS=2088


Hit any key to end.
$

both of these qr codes seem to decode okay using the barcode app on android.

Regards,
Paddy

-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages libdecodeqr-examples depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libcv2.1  2.1.0-3computer vision library
ii  libdecodeqr0  0.9.3-4A C/C++ library for decoding QR co
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libhighgui2.1 2.1.0-3computer vision GUI library
ii  libstdc++64.4.5-8The GNU Standard C++ Library v3

libdecodeqr-examples recommends no packages.

libdecodeqr-examples suggests no packages.

-- no debconf information



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

Bug#391935: [Pkg-xen-devel] Bug#391935: Bug #391935: Re: The answer from Citrix Xen.org

[paddy]

On Thu, Oct 09, 2008 at 01:33:22PM +1100, Ben Finney wrote:

  Any free/community use can do whatever it wants, quite literally.  
  Any commercial distribution that wishes to call itself Xen must be 
  compatible with other Xen branded commercial offerings, otherwise 
  the commercial distribution is not Xen.   This is determined by the 
  FIT test.
 
 If ???compatible with ?? can be ???determined by the FIT test??? without 
 the 
 prospective redistributor ever needing to contact another particular 
 party, this would seem to me to satisfy the DFSG.
 
 If, on the other hand, such compatibility requires some kind of 
 interaction with a particular party (e.g. to get the FIT test, 
 register for compatibility, confirm the test, or otherwise) then this 
 is a ???phone home??? restriction on redistribution.
 
 A useful test is the ???dissident??? test: can someone who wishes to 
 remain anonymous manage to determine whether their commercial 
 redistribution is permitted?
 
 Another useful test is the ???desert island??? test: can someone who is 
 isolated from any arbitrary portion of the larger world, and has 
 *only* the work in question (the Xen code base), nevertheless modify 
 and redistribute the work commercially to others in their circle, 
 knowing that they are complying with the applicable licenses?
 
 I guess in both those instances, the redistributor could simply rename 
 the work to be on the safe side. So long as this option remains 
 available I guess the combination is DFSG-free.

Will the FIT test be DFSG free ?

Regards,
Paddy
-- 
Segmentation fault (core dumped): .sig too big



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

Bug#99401: She said I thrust harder than him

[paddy Sibley]

Home made sex videos of women coming during hot sex.

http://www.sesuhshi.com/
Results in just 6-8 weeks.



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

Bug#185972: their wired lives wears

[farlay paddy]

CockLargishSonia http://www.Twalveen.com




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

Bug#43640: Your chixxxx can never forget these wonderful nights!

[davide paddy]

Hello
Your holiday would be not full without gd se..
http://seasonorgan.com
Kerstin mcclafferty
To his Aunt Jobiska's Park.




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

Bug#439335: CVE-2007-4131: GNU tar Directory Traversal

[paddy]

previously ...

Nico Golde [EMAIL PROTECTED] [Sun, 9 Sep 2007 14:30:06 +0200]:
 Hi,
 * Sylvain Beucler [EMAIL PROTECTED] [2007-09-09 13:56]:
  Was this forwarded to the Stable security team?
  
  If I'm given a tarball that can replace /etc/passwd, I'd say this is
  grave bug.
 
 This bug is monitored via the security tracker:
 http://security-tracker.debian.net/tracker/CVE-2007-4131
 So they should be aware of it.

just noticed this going past in an osx update and had a what ever
happenned to that? moment.

Regards,
Paddy




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

Bug#439363: request youtube-dl 2007.10.09-1 / 2006.11.12-1 for Etch

[paddy]

On Sat, Nov 03, 2007 at 01:50:45PM -, [EMAIL PROTECTED] wrote:
 Hi.
 youtube-dl 2006.11.12-1 in Etch has been unusable for a while now because
 of a change by YouTube (I think to the syntax of their URI but I'm not
 sure). youtube-dl 2007.10.09-1 works and is in Testing.
 
 I would like to request youtube-dl 2007.10.09-1 be included in Volatile
 please.
 
 It only consists of one Python script and sundry files; only depends on
 python (= 2.4). Here are the included files:
 
   /usr/bin/youtube-dl
   /usr/share/doc/youtube-dl/copyright
   /usr/share/doc/youtube-dl/changelog.Debian.gz
   /usr/share/man/man1/youtube-dl.1.gz
 
 I've been using a version from upstream by just replacing
 /usr/bin/youtube-dl and that has worked OK.
 

It is up to the package maintainer to make such a request.

Looks like the suggestion has already been made to him in debian bug #439363,
which I am cc'ing in this.

Such a program seems to falls into a category that has been considered before, 
and reading the archives of the list for this should prove instructive.  In 
particular, whether changes in the code might be so dramatic as to make any 
guarantee of stability hard to make.

Regards,
Paddy




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

Bug#441295: debbugs: apt-listbugs reportbug-ng fail at SOAP call, API broken ?

[paddy]

Package: debbugs
Severity: important


looks like #437154, #437103, #437020, #436163

ie:

Retrieving bug reports... 0% Fail
Error retrieving bug reports from the server with the following error
message:
 W: Mandatory parameter 'bug' missing in call to
 Debbugs::Status::get_bug_status
  at /usr/local/lib/site_perl/Debbugs/SOAP.pm line 131
  It could be because your network is down, or because of broken proxy
  servers, or the BTS server itself is down. Check network configuration
  and try again
  Retry downloading bug information?[Y/n]? n

and 

DebianBTSWARNING  Caught exception in __soapGetStatus(([334000, ...
, 277747],)), returning empty bug list.

Regards,
Paddy


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.21-2-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


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

Bug#438977: debian-cd: links to CD images not updated to r1

[Paddy Smith]

Package: www.debian.org
Severity: normal


see links under http://www.debian.org/CD/


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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

Bug#392927: Spfmilter dies unexpectedly with SIGABRT

[paddy]

On Tue, Jul 24, 2007 at 03:03:13PM -0700, Mike Markley wrote:
 On Thu, Jul 19, 2007 at 03:36:27PM -0700, Mike Markley [EMAIL PROTECTED] 
 wrote:
  On Fri, Jul 13, 2007 at 04:26:08PM +, [EMAIL PROTECTED] [EMAIL 
  PROTECTED] wrote:
   commenting out the three xfree()s after the referenced comment stops
   the crash.  I couldn't say whether spfmilter will then leak in the
   way that the comment warns ofi (I suspect not), but that would be a 
   less severe bug in my book.  I will feedback when I know more about 
   that question.
   
   scary though it may sound, please consider applying this to libspf0, 
   and putting the resulting package(s) forward for the next point release 
   of etch.
  
  I've applied this patch on one of my etch boxes that often experiences
  this crash. It's quite memory-contrained, so any memory leaks should
  also be reasonably obvious. I'll report results as I get them.
 
 I've been running this for nearly a week on my medium-volume backup MX,
 and if there's a memory leak, it's a very slow one. My baseline
 (off-peak) vsize for spfmilter started out as 10340 on 7/20 and then
 increased to 10396 on 7/21 and to 10460 on 7/23. Nonetheless, it does
 appear to be leaking. I can't actually prove that it's libspf0 leaking,
 though, since I'm not stable enough without the patch to take any real
 measurements.
 
 According to my etch system, whitelister is the only other package using
 libspf0. It's probably worth getting in touch with its maintainer to get
 his take.

yes, and wnpp recently said ...

The following packages have been orphaned:

  libspf (#433108), orphaned 5 days ago
 Description: the ANSI C SPF reference library
 Reverse Depends: libspf-dev spfmilter spfqtool whitelister
 Installations reported by Popcon: 203

If I have understood the relative state of maintenance of libspf0 and
libspf2 then the right thing to do long-term is to get packages still
depending on libspf0 across onto libspf2, but in the short term an
upload of libspf0 to straighten this out sounds like a good idea.

the bug in libspf appears to be the freeing of p-current_domain and
p-original_domain when they point to the same place (I am triggering
this repeatably using an @gmail.com MAIL FROM for testing, but I
haven't look deep enough to say what is required).

the following patch, which mimics the other place where these are freed,
would seem to be what the author intended.

--- main.c.orig 2007-07-25 10:26:40.0 +
+++ main.c  2007-07-25 10:20:01.0 +
@@ -1683,7 +1683,8 @@
 xfree(p-from);
   }

-  if (p-spf_rlevel  0)
+  if ((p-spf_rlevel  0) 
+  (p-current_domain != p-original_domain))
   {
 xfree(p-current_domain);
   }

I recall now that I looked at using this version of libspf0, and
specifically this bug, when I built myself an spfmilter for sarge,
and at the time I decided I'd rather stick with the version that 
was in sarge :-(

I would guess that spfqtool would not suffer from this, but that 
whitelister, being a similar sort of thing may. On postfix I mostly
see recommendations for other implementations, so it may be that it,
like spfmilter, is little used in debian ?

Regards,
Paddy



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

Bug#434514: reload db failed, clamav-daemon terminates

[Paddy Smith]

Package: clamav
Version: 0.90.1-3etch3
Severity: important


seen something like this twice recently.

Sat Jul  7 18:01:52 2007 - SelfCheck: Database status OK.
Sat Jul  7 19:06:24 2007 - SelfCheck: Database modification detected. Forcing 
reload.
Sat Jul  7 19:06:24 2007 - Reading databases from /var/lib/clamav
Sat Jul  7 19:06:25 2007 - ERROR: reload db failed: CVD extraction failure
Sat Jul  7 19:06:25 2007 - Terminating because of a fatal error.Sat Jul  7 
19:06:26 2007 - Socket file removed.
Sat Jul  7 19:06:26 2007 - ERROR: Can't unlink the pid file 
/var/run/clamav/clamd.pid
Sat Jul  7 19:06:26 2007 - --- Stopped at Sat Jul  7 19:06:26 2007

meanwhile,

--
Received signal: wake up
ClamAV update process started at Sat Jul  7 18:29:49 2007
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.90.1 Recommended version: 0.90.3
DON'T PANIC! Read http://www.clamav.net/support/faq
main.inc is up to date (version: 43, sigs: 104500, f-level: 14, builder: sven)
Downloading daily-3608.cdiff [0%]
daily.inc updated (version: 3608, sigs: 29779, f-level: 16, builder: ccordes)
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Current functionality level = 14, recommended = 16
DON'T PANIC! Read http://www.clamav.net/support/faq
Database updated (134279 signatures) from db.local.clamav.net (IP: 
64.142.100.50)

I have yet to try to look into whether this is repeatable, although I would
tend to assume not :-(

and more recently,

Fri Jul 20 17:29:18 2007 - SelfCheck: Database status OK.
Fri Jul 20 18:30:01 2007 - SelfCheck: Database modification detected. Forcing 
reload.
Fri Jul 20 18:30:01 2007 - Reading databases from /var/lib/clamav
Fri Jul 20 18:30:05 2007 - ERROR: reload db failed: Malformed database
Fri Jul 20 18:30:05 2007 - Terminating because of a fatal error.Fri Jul 20 
18:30:06 2007 - Socket file removed.
Fri Jul 20 18:30:06 2007 - ERROR: Can't unlink the pid file 
/var/run/clamav/clamd.pid
Fri Jul 20 18:30:06 2007 - --- Stopped at Fri Jul 20 18:30:06 2007

freshclam seems to have stopped logging before this, there was nothing
obviously special in it's logs prior to stopping.

I run MailScanner also, but I am fairly certain that is not attempting
to update clam.

my /etc/clamav is unchanged from the distibuted versions.  I see an 
onerrorexecute.d there that I should perhaps look into.

I note that I do not have the suggested: daemon package installed.

Regards,
Paddy

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages clamav depends on:
hi  clamav-freshclam [clamav-d 0.90.1-3etch3 downloads clamav virus databases f
hi  libc6  2.3.6.ds1-13  GNU C Library: Shared libraries
hi  libclamav2 0.90.1-3etch3 virus scanner library
hi  zlib1g 1:1.2.3-13compression library - runtime

Versions of packages clamav recommends:
hi  arj3.10.22-2 archiver for .arj files
hi  clamav-base0.90.1-3etch3 base package for clamav, an anti-v
hi  unzoo  4.4-5 zoo archive extractor

-- no debconf information


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

Bug#431444: merge

[paddy]

merge 431444 392927


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

Bug#392927: Spfmilter dies unexpectedly with SIGABRT

[paddy]

yes, looks like this is happening in SPF_smtp_from()

and it is the double free that aaron reports in #315196.
it is hard to be sure about the earlier report in that bug,
if that is a different author.

I have a version of this built some time back against
a libspf version slightly before the comment that Herbert quotes,
which doesn't suffer from this problem, I'll look at the diff.

probably this bug should be filed against the libspf0 library.

as far as I understand it neither of this or the libspf2 libs
are supported upstream, and they probably have more subtle bugs
in their implementation of SPF.  I suggest interested users
look at the archives of, or ask on the spf mailing lists.

nevertheless, I've had some good use out of my build of this
with sarge, and would like to see this bug fixed since this 
package is in etch.



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

Bug#392927: Spfmilter dies unexpectedly with SIGABRT

[paddy]

commenting out the three xfree()s after the referenced comment stops
the crash.  I couldn't say whether spfmilter will then leak in the
way that the comment warns ofi (I suspect not), but that would be a 
less severe bug in my book.  I will feedback when I know more about 
that question.

scary though it may sound, please consider applying this to libspf0, 
and putting the resulting package(s) forward for the next point release 
of etch.

Regards,
Paddy


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

Bug#425569: kicker crash with backtrace

[paddy]

Package: kicker
Version: 4:3.5.5a.dfsg.1-6
Severity: normal

*** Please type your report below this line ***

Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
[Thread debugging using libthread_db enabled]
[New Thread -1232709408 (LWP 5520)]
[KCrash handler]
#9  TaskContainer::updateKickerTip (this=0x81b9e98, [EMAIL PROTECTED])
at /tmp/buildd/kdebase-3.5.5a.dfsg.1/./kicker/taskbar/taskcontainer.cpp:1538
#10 0xb6723473 in KickerTip::display (this=0x81137a8)
at /tmp/buildd/kdebase-3.5.5a.dfsg.1/./kicker/libkicker/kickertip.cpp:129
#11 0xb6723a1f in KickerTip::qt_invoke (this=0x81137a8, _id=48, _o=0xbfe44cec)
at ./kickertip.moc:91
#12 0xb721ad4f in QObject::activate_signal (this=0x811387c, clist=0x81697f8, 
o=0xbfe44cec) at kernel/qobject.cpp:2356
#13 0xb721b7e0 in QObject::activate_signal (this=0x811387c, signal=2)
at kernel/qobject.cpp:2325
#14 0xb75a5faa in QTimer::timeout (this=0x811387c)
at .moc/debug-shared-mt/moc_qtimer.cpp:82
#15 0xb7242603 in QTimer::event (this=0x811387c, e=0xbfe45038)
at kernel/qtimer.cpp:219
#16 0xb71b2c26 in QApplication::internalNotify (this=0x8094048, 
receiver=0x811387c, e=0xbfe45038) at kernel/qapplication.cpp:2635
#17 0xb71b4a43 in QApplication::notify (this=0x8094048, receiver=0x811387c, 
e=0xbfe45038) at kernel/qapplication.cpp:2358
#18 0xb78a8e0e in KApplication::notify (this=0x8094048, receiver=0x811387c, 
event=0xbfe45038)
at /tmp/buildd/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550
#19 0xb7146421 in QApplication::sendEvent (receiver=0x811387c, 
event=0xbfe45038) at ../include/qapplication.h:520
#20 0xb71a5623 in QEventLoop::activateTimers (this=0x80acc10)
at kernel/qeventloop_unix.cpp:556
#21 0xb715a76f in QEventLoop::processEvents (this=0x80acc10, flags=4)
at kernel/qeventloop_x11.cpp:389
#22 0xb71cd179 in QEventLoop::enterLoop (this=0x80acc10)
at kernel/qeventloop.cpp:198
#23 0xb71ccf9a in QEventLoop::exec (this=0x80acc10)
at kernel/qeventloop.cpp:145
#24 0xb71b47bf in QApplication::exec (this=0x8094048)
at kernel/qapplication.cpp:2758
#25 0xb662d6dd in kdemain (argc=1, argv=0x807d020)
at /tmp/buildd/kdebase-3.5.5a.dfsg.1/./kicker/kicker/core/main.cpp:149
#26 0xb7f05524 in kdeinitmain (argc=1, argv=0x807d020) at kicker_dummy.cpp:3
#27 0x0804e457 in launch (argc=1, _name=0x8071764 kicker, 
args=0x807176b , cwd=0x0, envc=0, envs=0x807176f , reset_env=false, 
tty=0x0, avoid_loops=false, startup_id_str=0x8050d2e 0)
at /tmp/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:673
#28 0x0804ecf9 in handle_launcher_request (sock=9)
at /tmp/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1240
#29 0x0804f092 in handle_requests (waitForPid=0)
at /tmp/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1443
#30 0x080502b1 in main (argc=5, argv=0xbfe45ad4, envp=0xbfe45aec)
at /tmp/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1909
#31 0xb7c7cea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#32 0x0804b911 in _start () at ../sysdeps/i386/elf/start.S:119

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages kicker depends on:
hi  kdebase-data   4:3.5.5a.dfsg.1-6 shared data files for the KDE base
hi  kdelibs4c2a4:3.5.5a.dfsg.1-8 core libraries and binaries for al
hi  libacl12.2.41-1  Access control list shared library
hi  libart-2.0-2   2.3.17-1  Library of functions for 2D graphi
hi  libattr1   2.4.32-1  Extended attribute shared library
hi  libaudio2  1.8-4 The Network Audio System (NAS). (s
hi  libc6  2.3.6.ds1-13  GNU C Library: Shared libraries
hi  libfontconfig1 2.4.2-1.2 generic font configuration library
hi  libfreetype6   2.2.1-5   FreeType 2 font engine, shared lib
hi  libgamin0 [libfam0]0.1.8-2   Client library for the gamin file 
hi  libgcc11:4.1.1-21GCC support library
hi  libice61:1.0.1-2 X11 Inter-Client Exchange library
hi  libidn11   0.6.5-1   GNU libidn library, implementation
hi  libjpeg62  6b-13 The Independent JPEG Group's JPEG 
hi  libkonq4   4:3.5.5a.dfsg.1-6 core libraries for Konqueror
hi  libpng12-0 1.2.15~beta5-1PNG library - runtime
hi  libqt3-mt  3:3.3.7-4 Qt GUI Library (Threaded runtime v
hi  libsm6 1:1.0.1-3 X11 Session Management library
hi  libstdc++6 4.1.1-21  The GNU Standard C++ Library v3
hi  libx11-6   2:1.0.3-7 X11 client-side library
hi  libxau61:1.0.1-2 X11 authorisation library
hi  libxcomposite1 1:0.3-3  

Bug#292858: new accounts have

[paddy Larouche]

In ImageReady, the layer style is added with a default name.

AN ALLE FINANZINVESTOREN!
DIESE AKTIE WIRD DURCHSTARTEN!
FREITAG 20. APRIL STARTET DIE HAUSSE!
REALISIERTER KURSGEWINN VON 400%+ IN 5 TAGEN!

Symbol: G7Q.F
Company: COUNTY LINE ENERGY
5 Tages Kursziel: 0.95
Schlusskurs: 0.21
WKN:  A0J3B0
ISIN: US2224791077
Markt: Frankfurt

LASSEN SIE SICH DIESE CHANCE NICHT ENTGEHEN!
G7Q WIRD WIE EINE RAKETE DURCHSTARTEN!
UNSERE ERWARTUNGEN WIRD G7Q.F UBERTREFFEN!

You may also need these packages if you upgrade your source tree using patches, 
although we try to avoid this.



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

Bug#67612: at secure school

[paddy heywood]

coach Lamoriello takes over Hailing taxi
http://img444.imageshack.us/img444/9610/6njjlg7.jpg
TrueAir TrueLevel Motor Homes View Aspect Access



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

Bug#411984: crash in konsole (SIGABRT)

[paddy]

Package: konsole
Version: 4:3.5.5a.dfsg.1-6
Severity: important

*** Please type your report below this line ***

I was using the scrollbar at the time

(no debugging symbols found)
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232484672 (LWP 8547)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#9  0xb7f3e410 in ?? ()
#10 0xbf86435c in ?? ()
#11 0x0006 in ?? ()
#12 0x2163 in ?? ()
#13 0xb7cc9811 in raise () from /lib/tls/i686/cmov/libc.so.6
#14 0xb7ccafb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#15 0xb7cfed3a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#16 0xb7d065cf in mallopt () from /lib/tls/i686/cmov/libc.so.6
#17 0xb7d06672 in free () from /lib/tls/i686/cmov/libc.so.6
#18 0xb6689853 in TEmulation::showBulk () from /usr/lib/libkdeinit_konsole.so
#19 0xb668a133 in TEmulation::qt_invoke () from /usr/lib/libkdeinit_konsole.so
#20 0xb668a184 in TEmuVt102::qt_invoke () from /usr/lib/libkdeinit_konsole.so
#21 0xb7252d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#22 0xb72537e0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb75dde5e in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#24 0xb727a603 in QTimer::event () from /usr/lib/libqt-mt.so.3
#25 0xb71eac26 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#26 0xb71eca43 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#27 0xb78e0e0e in KApplication::notify () from /usr/lib/libkdecore.so.4
#28 0xb717e421 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#29 0xb71dd623 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#30 0xb719276f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#31 0xb7205179 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#32 0xb7204f9a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#33 0xb71ec7bf in QApplication::exec () from /usr/lib/libqt-mt.so.3
#34 0xb66acd25 in kdemain () from /usr/lib/libkdeinit_konsole.so
#35 0xb7f3a524 in kdeinitmain () from /usr/lib/kde3/konsole.so
#36 0x0804e457 in ?? ()
#37 0x0001 in ?? ()
#38 0x08073c40 in ?? ()
#39 0x0001 in ?? ()
#40 0x in ?? ()



-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages konsole depends on:
ii  kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al
ii  libc6  2.3.6.ds1-11  GNU C Library: Shared libraries
hi  libgcc11:4.1.1-21GCC support library
hi  libstdc++6 4.1.1-21  The GNU Standard C++ Library v3
hi  libxrender11:0.9.1-3 X Rendering Extension client libra
hi  libxtst6   1:1.0.1-5 X11 Testing -- Resource extension 

konsole recommends no packages.

-- no debconf information


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

Bug#407308: gnustep-gui-runtime: The gnustep_sndd tool is not built; missing build-depends on portaudio19-dev

[Paddy Smith]

Thanks, I've managed to get a sndd built and get sound out of it.  I'm
finding that if I run it by the init script from the root user, the
desktop user doesn't find it and starts its own, and I'm still
battling with getting the various sound systems to play nicely
together.

There seems to be an option in GNUmail to play a sound when mail is
received, and IIRC from looking at the code it uses NSSound.  That
would, I imagine, be an example of non-trivial breakage, but I don't
use GNUmail and I'm having trouble actually getting it to make the
sound, even with a working sndd :-)

Regards,
Paddy


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

Bug#365416: /lib/udev/eciadsl: $PRODUCT is not defined! This script should be run by hotplug

[paddy]

 

  racoon:~# fxload -vvv -s /usr/share/usb/a3load.hex -I 
/usr/local/lib/eciadsl/synch03.bin -D /proc/bus/usb/001/008
  microcontroller type: fx
  1st stage:  load 2nd stage loader
  open RAM hexfile image /usr/share/usb/a3load.hex
  stop CPU
  can't modify CPUCS: Broken pipe
  
and I've even tried some old image I found lying around:

  racoon:~/old_eci# ./eci-load1 --version
  ECIADSL USB modem driver (ECIADSL) 0.6 (Feb  7 2003 17:03:27)
  racoon:~/old_eci# ./eci-load1 0x1690 0x215 0x 0x 
/usr/local/lib/eciadsl/firmware00.bin 
  can't find your EZUSB USB ADSL Loader
  ECI load 1: failed
  
right now I would just like to get this to work, and I'm about to start 
throwing other distros at it.

Longer term I'd be keen to see this work and be well supported in debian 
as this seems to be the modem used by BT engineers in the UK for testing 
lines.  The value of this becomes clear in my current situation, where 
I am asked to consider a possible modem incompatibility.

You say you have no equipment of this sort? If I were to ship you one,
would that help?

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall


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

Bug#346117: heartbeat: use invoke-rc.d in postinst ?

[paddy]

Package: heartbeat
Version: 1.2.3-9sarge4
Severity: important


See the Subject. Is there a reason why not ?

I haven't looked into this deeply.  Personally I'd want restart if
running type thing.  Anything else is just scary :)

Indeed, I was tempted to file this as critical, and I actually think 
that it is, but I can see that its debatable.

My reasoning was simply that heartbeat can be so much fun, having
as it does the power to reboot systems, other systems even :) 
I'd wager there are scenarios that would include data loss.

I have drbd, and it was only luck that it was running.  I'm not sure
what would have happenned if it weren't, but I could try it out on
a test system if you want to know.

Let me know if you need a patch.

Regards,
Paddy

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages heartbeat depends on:
hi  adduser3.63  Add and remove users and groups
hi  iproute20041019-3Professional tools to control the 
hi  iputils-ping   3:20020927-2  Tools to test the reachability of 
hi  libc6  2.3.2.ds1-22  GNU C Library: Shared libraries an
hi  libglib1.2 1.2.10-9  The GLib library of C routines
hi  libnet11.1.2.1-2 library for the construction and h
ii  libpils0   1.2.3-9sarge4 Plugin and Interface Loading Syste
ii  libstonith01.2.3-9sarge4 Interface for remotely powering do
hi  python 2.3.5-2   An interactive high-level object-o

-- no debconf information


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

Bug#346117: heartbeat: use invoke-rc.d in postinst ?

[paddy]

On Fri, Jan 06, 2006 at 12:18:54PM +0900, Horms wrote:
 heartbeat: use invoke-rc.d in postinst ?
 
 On Thu, Jan 05, 2006 at 07:07:30PM +, paddy wrote:
  Package: heartbeat
  Version: 1.2.3-9sarge4
  Severity: important
  
  
  See the Subject. Is there a reason why not ?
snip 
 Hi Paddy,
 
 A way for heartbeat to use invoke-rc.d seems like a good idea to me.
 Perhaps the best way would be to make a resource that acts as a
 simple wrapper for invoke-rc.d and can be listed in the haresources
 file.

Hi Horms,

My first reaction was no, just in postinst!, but I think you have a
point: could be a whole can of worms!

I'm still inclined to imagine that something like 

diff -u old/heartbeat.postinst new/heartbeat.postinst
--- old/heartbeat.postinst  2005-09-28 07:09:28.0 +0100
+++ new/heartbeat.postinst  2006-01-06 12:45:19.701212210 +
@@ -45,13 +45,21 @@
update-rc.d heartbeat start 75 2 3 4 5 . stop 05 0 1 6 . /dev/null || 
true

ldconfig
-
-   /etc/init.d/heartbeat start || true
+
+if [ -x /usr/sbin/invoke-rc.d ]; then
+invoke-rc.d heartbeat start || exit 0
+else
+/etc/init.d/heartbeat start || exit 0
+fi
 ;;

 abort-upgrade|abort-remove|abort-deconfigure)
# restart heartbeat
-   /etc/init.d/heartbeat start || true
+if [ -x /usr/sbin/invoke-rc.d ]; then
+invoke-rc.d heartbeat start || exit 0
+else
+/etc/init.d/heartbeat start || exit 0
+fi
 ;;

 *)

(and I'm imagining similarly in preinst. And you might want to change 
that comment some day :).

would be an improvement on its own, but I agree that it makes sense to 
consider the bigger picture in a case like heartbeat.

I'll have a stab at that now.  Please correct me on the details that
I get wrong, or at least take what I say with a large pinch of salt,
as I have yet to study the code or read the extensive discussion that
took place at the time.

During debian package upgrades (and presumably other package ops)
there is a hazard(s) with the use of 

  /etc/init.d/servicename start

which is resolved or improved by the use of a wrapper as above.

Two obvious possibilities are that the service is not defined to start
in the current runlevel, or that the service was not running prior
to the upgrade and so should not be started.

The question that seems to follow is this:

Suppose that heartbeat is running at the time of an upgrade.
(I'm imagining that) the preinst script will stop it and the
postinst script will start it again, (at least in my ideal
world, and given that I'm guessing the functions of the scripts 
correctly.)

Since heartbeat is a kind of init system within an init system,
does this create a parallel situation inside of heartbeat which 
could require a similar solution?

At first blush the answer would appear to be:

  heartbeat _could_ do stuff it wouldn't otherwise do. (eg: failover),
  but those _should_ be things it is configured to do.
  
  heartbeat doesn't really have runlevels or admin-set-it-that-way
  like sysvinit does?
  
So then there is no problem to solve?

Nevertheless, I find the whole question to be fairly open-ended.

What happens if you have an underlying dependency-based init ?

Might there be a situation in which a request to stop and start
a heartbeat service in order to upgrade a package should be 
denied by the heartbeat system ? (bring another node online or
overide this safety and then we'll talk about it ?)

Both package management and init-type systems are open areas of 
development, so its kinda like trying to shoot a moving target 
from a moving platform.  I certainly seems like fun to ask the 
questions, but in the absence of anything promising I'd be happy
to take the easy win.

 I've CCed the linux-ha-dev list as thats a good place for discussions
 like this. Though only members can post (to cut down on spam) so
 you'll need to join up or pass messages to me (or 346117).

I've subscribed to the linux-ha-dev list.

I've refrained from CCing initscripts-ng-devel@lists.alioth.debian.org,
as much because I'm rather dependent on mutt's r,g, and L keys, after
which I'm making it up, and I'm already at the making it up stage! :)

Besides which I recall mixed feelings about whether heartbeat is in scope.
Perhaps there will be something interesting to take there later.

Incidentally, what is X-Cluestick: seven ?  and what does it go up to ?

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall


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

Bug#346117: heartbeat: use invoke-rc.d in postinst ?

[paddy]

Package: heartbeat
Version: 1.2.3-9sarge4
Severity: important


See the Subject. Is there a reason why not ?

I haven't looked into this deeply.  Personally I'd want restart if
running type thing.  Anything else is just scary :)

Indeed, I was tempted to file this as critical, and I actually think 
that it is, but I can see that its debatable.

My reasoning was simply that heartbeat can be so much fun, having
as it does the power to reboot systems, other systems even :) 
I'd wager there are scenarios that would include data loss.

I have drbd, and it was only luck that it was running.  I'm not sure
what would have happenned if it weren't, but I could try it out on
a test system if you want to know.

Let me know if you need a patch.

Regards,
Paddy

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages heartbeat depends on:
hi  adduser3.63  Add and remove users and groups
hi  iproute20041019-3Professional tools to control the 
hi  iputils-ping   3:20020927-2  Tools to test the reachability of 
hi  libc6  2.3.2.ds1-22  GNU C Library: Shared libraries an
hi  libglib1.2 1.2.10-9  The GLib library of C routines
hi  libnet11.1.2.1-2 library for the construction and h
ii  libpils0   1.2.3-9sarge4 Plugin and Interface Loading Syste
ii  libstonith01.2.3-9sarge4 Interface for remotely powering do
hi  python 2.3.5-2   An interactive high-level object-o

-- no debconf information


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

Bug#319258: mailscanner: respawn broken - what happenned to MailScanner.off lock ?

[Paddy Smith]

Package: mailscanner
Version: 4.41.3-2
Severity: important
Tags: patch


Hi Mathias,

I take /etc/cron.d/mailscanner (and its equivalent upstream) to be a 
respawn mechanism: If the service ceases to function, the periodic respawn 
starts it up again.

The upstream init.d script and cron respawn script use a lockfile
Mailscanner.off, but this is missing in the Debian version.  

The lockfile enables the least surprise behaviour of when I (the admin)
stops the service, it stays stopped.  Or when I change to a runlevel in 
which the service is not stopped, it stays stopped.  And so on ...

Clearly I could abuse the $run_mailscanner /etc/default variable to
get this effect, but the default behaviour would still wrong.

I attach an (untested!) patch against 4.41.3-2 which attempts to simply 
reinstate this mechanism.

Please consider fixing this in future sarge point releases.

Regards,
Paddy

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mailscanner depends on:
hi  debconf   1.4.30.13  Debian configuration management sy
hi  libarchive-zip-perl   1.14-1 Module for manipulation of ZIP arc
hi  libcompress-zlib-perl 1.34-1 Perl module for creation and manip
hi  libconvert-binhex-perl1.119-2Perl5 module for extracting data f
hi  libconvert-tnef-perl  0.17-4 Perl module to read TNEF files
hi  libhtml-parser-perl   3.45-2 A collection of modules that parse
hi  libmime-perl  5.417-1Perl5 modules for MIME-compliant m
hi  libnet-cidr-perl  0.10-1 Manipulate IPv4/IPv6 netblocks in 
hi  perl  5.8.4-8Larry Wall's Practical Extraction 
hi  sendmail-bin [mail-transport- 8.13.4-3   powerful, efficient, and scalable 
ii  spamassassin  3.0.3-2Perl-based spam filter using text 
hi  ucf   1.17   Update Configuration File: preserv
hi  unzip 5.52-1 De-archiver for .zip files
hi  wget  1.9.1-12   retrieves files from the web
diff -urN mailscanner-4.41.3/debian/cron.d mailscanner-4.41.3-0hs1/debian/cron.d
--- mailscanner-4.41.3/debian/cron.d2005-07-20 19:25:32.611364026 +0100
+++ mailscanner-4.41.3-0hs1/debian/cron.d   2005-07-20 19:30:54.755422483 
+0100
@@ -9,4 +9,4 @@
 # them from stepping on each other's toes.  The worst that will
 # happen is that they will temporarily corrupt the database...
 
[EMAIL PROTECTED]   root[ -f $LOCKFILE ]  exit 0; run_mailscanner=0; 
run_nice=0; if [ -f /etc/default/mailscanner ]; then . 
/etc/default/mailscanner; fi; [ $run_mailscanner = 0 ]  exit 0; trap rm -f 
$LOCKFILE EXIT; touch $LOCKFILE; /usr/bin/nice -$run_nice 
/usr/sbin/check_mailscanner /dev/null 21; exit 0
[EMAIL PROTECTED]   root[ -f $LOCKFILE ]  exit 0; run_mailscanner=0; 
run_nice=0; if [ -f /etc/default/mailscanner ]; then . 
/etc/default/mailscanner; fi; [ $run_mailscanner = 0 ]  exit 0; [ -f 
/var/lock/subsys/MailScanner.off ]  exit 0; trap rm -f $LOCKFILE EXIT; 
touch $LOCKFILE; /usr/bin/nice -$run_nice /usr/sbin/check_mailscanner 
/dev/null 21; exit 0
diff -urN mailscanner-4.41.3/debian/init.d mailscanner-4.41.3-0hs1/debian/init.d
--- mailscanner-4.41.3/debian/init.d2005-07-20 19:25:32.637361367 +0100
+++ mailscanner-4.41.3-0hs1/debian/init.d   2005-07-20 19:32:29.949687953 
+0100
@@ -90,6 +90,7 @@
RETVAL=$?
if [ $RETVAL -eq 0 ]; then
rm -f /var/lock/subsys/mailscanner
+   touch /var/lock/subsys/MailScanner.off
fi
if ps axww | grep -i $DAEMON | grep -qv grep; then
echo -n (waiting

Bug#319258: mailscanner: respawn broken - what happenned to MailScanner.off lock ?

[paddy]

Sorry, silly mistake.
Please consider the attached instead.

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall
diff -urN mailscanner-4.41.3/debian/cron.d mailscanner-4.41.3-0hs2/debian/cron.d
--- mailscanner-4.41.3/debian/cron.d2005-07-20 19:25:32.611364026 +0100
+++ mailscanner-4.41.3-0hs2/debian/cron.d   2005-07-20 19:30:54.755422483 
+0100
@@ -9,4 +9,4 @@
 # them from stepping on each other's toes.  The worst that will
 # happen is that they will temporarily corrupt the database...
 
[EMAIL PROTECTED]   root[ -f $LOCKFILE ]  exit 0; run_mailscanner=0; 
run_nice=0; if [ -f /etc/default/mailscanner ]; then . 
/etc/default/mailscanner; fi; [ $run_mailscanner = 0 ]  exit 0; trap rm -f 
$LOCKFILE EXIT; touch $LOCKFILE; /usr/bin/nice -$run_nice 
/usr/sbin/check_mailscanner /dev/null 21; exit 0
[EMAIL PROTECTED]   root[ -f $LOCKFILE ]  exit 0; run_mailscanner=0; 
run_nice=0; if [ -f /etc/default/mailscanner ]; then . 
/etc/default/mailscanner; fi; [ $run_mailscanner = 0 ]  exit 0; [ -f 
/var/lock/subsys/MailScanner.off ]  exit 0; trap rm -f $LOCKFILE EXIT; 
touch $LOCKFILE; /usr/bin/nice -$run_nice /usr/sbin/check_mailscanner 
/dev/null 21; exit 0
diff -urN mailscanner-4.41.3/debian/init.d mailscanner-4.41.3-0hs2/debian/init.d
--- mailscanner-4.41.3/debian/init.d2005-07-20 19:25:32.637361367 +0100
+++ mailscanner-4.41.3-0hs2/debian/init.d   2005-07-20 19:53:51.210622375 
+0100
@@ -80,6 +80,7 @@
RETVAL=$?
if [ $RETVAL -eq 0 ]; then
touch /var/lock/subsys/mailscanner
+   rm -f /var/lock/subsys/MailScanner.off
fi
echo $NAME.
;;
@@ -90,6 +91,7 @@
RETVAL=$?
if [ $RETVAL -eq 0 ]; then
rm -f /var/lock/subsys/mailscanner
+   touch /var/lock/subsys/MailScanner.off
fi
if ps axww | grep -i $DAEMON | grep -qv grep; then
echo -n (waiting

Bug#74889: Any software backups for lowest pricest.

[Paddy]

We focus on OEM and Retail Box for Microsoft, Adobe, Macromedia, Corel, 
Symantec and more.
http://dflig.j8ngm0jcgb18y2j.agnosislk.com




Listen; there's a hell of a good universe next door: let's go. 
To-day is the pupil of yesterday.   





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

Bug#314447: package somewhere available?

[paddy]

On Fri, Jul 01, 2005 at 01:52:38PM +0200, Willi Mann wrote:
 Willi,
 
 Its already there, and (I'm fairly sure) was there before I posted the 
 bug. (I meant to check but I forgot!)  I think that the Sarge tag also 
 means this.
 
 # apt-cache showsrc spamassassin
 Package: spamassassin
 Binary: spamassassin, spamc
 Version: 3.0.4-2
 
 No, it wasn't. 3.0.4-2 is in testing (etch), 

sorry, I did realise that ...

 but not in sarge, because new 
 upstream versions are a big no-no for stable. 

Granted, my apologies.  I should really think before I hit send !

 See
 
 http://packages.qa.debian.org/s/spamassassin.html
 
 I asked for the fixed package for stable, which would be some 3.0.3-x, 
 because I don't want to install new upstream versions to fix security bugs, 
 and I want to avoid version chaos.

Again, apologies.  I misunderstood.

 BTW: This bug can be closed, as the new spamassassin 3.0.3-2 was released 
 tonight.

Kudos to all!

I see the DSA, but I don't see the files on s.d.o yet ...
... maybe I'm doing something wrong.

 I won't close it as I'm not submitter, maintainer or member of the 
 security team.

I think I'm the submitter, and closing a bug sounds rather fun,
but doesn't the release process do that automatically ? 

(besides I don't feel like I've done anything to earn the priviledge).

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall


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

Bug#314447: package somewhere available?

[paddy]

Willi,

Its already there, and (I'm fairly sure) was there before I posted the bug. 
(I meant to check but I forgot!)  I think that the Sarge tag also means this.

# apt-cache showsrc spamassassin
Package: spamassassin
Binary: spamassassin, spamc
Version: 3.0.4-2
Priority: optional
Section: mail
Maintainer: Duncan Findlay [EMAIL PROTECTED]
Build-Depends: debhelper (= 4.1.16), perl (= 5.6.0-16), libssl-dev, dpatch, 
libdigest-sha1-perl, libhtml-parser-perl (= 3.24), libmime-base64-perl | perl 
(= 5.8.0)
Architecture: any
Standards-Version: 3.6.1
Format: 1.0
Directory: pool/main/s/spamassassin
Files:
 251e0bb1778c8d816a7ce94fa47b82ac 777 spamassassin_3.0.4-2.dsc
 51926fe5aabaf57eed2c09061fe8fb02 1001430 spamassassin_3.0.4.orig.tar.gz
 6c182f1ce2980d5ba07fc100f3815e28 47354 spamassassin_3.0.4-2.diff.gz
Uploaders: Jesus Climent [EMAIL PROTECTED]

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall


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

Bug#314447: spamassassin: CAN-2005-1266 Denial of Service Vulnerability in SpamAssassin 3.0.1-3.0.3, fixed in 3.0.4

[Paddy Smith]

Package: spamassassin
Version: 3.0.3-1
Severity: important
Tags: security, fixed-upstream

as per:

 From [EMAIL PROTECTED]  Wed Jun 15 21:12:13 2005
 From: Daniel Quinlan [EMAIL PROTECTED]
 To: announce@spamassassin.apache.org
 Subject: Denial of Service Vulnerability in Apache SpamAssassin 3.0.1-3.0.3
 
 Apache SpamAssassin 3.0.4 was recently released [0], and fixes a denial
 of service vulnerability in versions 3.0.1, 3.0.2, and 3.0.3.  The
 vulnerability allows certain misformatted long message headers to cause
 spam checking to take a very long time.
 
 While the exploit has yet to be seen in the wild, we are concerned that
 there may be attempts to abuse the vulnerability in the future.
 Therefore, we strongly recommend all users of these versions upgrade to
 Apache SpamAssassin 3.0.4 as soon as possible.
 
 This issue has been assigned CVE id CAN-2005-1266 [1].
 
 To contact the Apache SpamAssassin security team, please e-mail
 security at spamassassin.apache.org.  For more information about Apache
 SpamAssassin, visit the http://spamassassin.apache.org/ web site.
 
 Apache SpamAssassin Security Team
 
 [0]: 
 http://mail-archives.apache.org/mod_mbox/spamassassin-dev/200506.mbox/[EMAIL 
 PROTECTED]
 
 [1]: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-1266

Although CVE still says When the candidate has been publicized, the
details for this candidate will be provided. 

Wasn't sure what severity to give this.

Regards,
Paddy

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages spamassassin depends on:
hi  debconf   1.4.30.13  Debian configuration management sy
hi  libdigest-sha1-perl   2.10-1 NIST SHA-1 message digest algorith
hi  libhtml-parser-perl   3.45-2 A collection of modules that parse
hi  perl [libstorable-perl]   5.8.4-8Larry Wall's Practical Extraction 
hi  spamc 3.0.3-1Client for SpamAssassin spam filte

-- debconf information:
  spamassassin/upgrade/2.40:
  spamassassin/upgrade/2.40w:
  spamassassin/upgrade/cancel: Continue
  spamassassin/upgrade/2.42m: No
  spamassassin/upgrade/2.42u: No


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

Bug#312565: webmin-snort: conf_rules.cgi does not understand VARs (like $RULE_PATH)

[Paddy Smith]

Package: webmin-snort
Version: 1.1-3
Severity: important
Tags: patch


The attached patch is intended to fix:

#286777 conf_rules.cgi: Rule file cannot be found 
(/etc/snort/$RULE_PATH/scan.rules).
#296481 Rule file cannot be found when viewing

It doesn't try to notice if its passed in a non-existent $VAR, but just
blithely replaces it with the empty string.  We're past access control at 
this point.

it's against webmin-snort_1.1-3

Here's the patch inline:

--- conf_rules.cgi.dist 2005-06-08 19:47:58.369061511 +
+++ conf_rules.cgi  2005-06-08 19:45:03.136592356 +
@@ -37,7 +37,10 @@

 # Some basic error checking
 snort_error($text{'rule_norule'}) if !$in{'rule'};
-$rulefile = $config{'snort_rules_path'} . / . $in{'rule'} . .rules;
+$rulefile = $in{'rule'};
+$conf = get_config(var) if $rulefile =~ /\$/;
+$rulefile =~ s/\$(\w+)/$$conf{$1}-{'value'}/ while $rulefile =~ /\$/;
+$rulefile .= .rules;
 snort_error($text{'rule_nofile'},  ($rulefile)) if (! -r $rulefile);

 # Grab the rule file and parse it into arrays

Regards,
Paddy

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages webmin-snort depends on:
hi  perl  5.8.4-8Larry Wall's Practical Extraction 
hi  snort 2.3.2-3Flexible Network Intrusion Detecti
hi  webmin1.180-3web-based administration toolkit

-- no debconf information
--- conf_rules.cgi.dist 2005-06-08 19:47:58.369061511 +
+++ conf_rules.cgi  2005-06-08 19:45:03.136592356 +
@@ -37,7 +37,10 @@
 
 # Some basic error checking
 snort_error($text{'rule_norule'}) if !$in{'rule'};
-$rulefile = $config{'snort_rules_path'} . / . $in{'rule'} . .rules;
+$rulefile = $in{'rule'};
+$conf = get_config(var) if $rulefile =~ /\$/;
+$rulefile =~ s/\$(\w+)/$$conf{$1}-{'value'}/ while $rulefile =~ /\$/ ;
+$rulefile .= .rules;
 snort_error($text{'rule_nofile'},  ($rulefile)) if (! -r $rulefile);
 
 # Grab the rule file and parse it into arrays

Bug#301671: apt-listbugs: cron.daily destroys the contents of symlinked /etc/apt/preferences

[paddy]

Thanks for the quick reply, Steve.
I didn't mean to imply that it wasn't a good reason.
I take it that all such removals are documented by the RC bugs.

The contents of the preferences file seem to get destroyed by the
line:

  /usr/share/apt-listbugs/aptcleanup  /etc/apt/preferences.apt-listbugs.$$

when it is writing to the same file it is reading from.

Perhaps something more like:
(stealing shamelessly from /etc/cron.monthly/acct)

  #!/bin/sh -e
  
  prefclean() {
  
test -x /usr/share/apt-listbugs/aptcleanup || return 0
test -x /usr/sbin/apt-listbugs || return 0
test -f /etc/apt/preferences || return 0
  
PTMP=$(tempfile)
/usr/share/apt-listbugs/aptcleanup  $PTMP
if ! diff $PTMP /etc/apt/preferences  /dev/null; then
  savelog /etc/apt/preferences
  mv $PTMP /etc/apt/preferences
fi
/bin/rm -f $PTMP
  
  }
  
  prefclean
  
savelog doesn't seem to handle the symlink either.

better options might be something along the lines of

  cp -aH /etc/apt/preferences /etc/apt/preferences.0

or resolving the symlink and rotating in the parent directory of the file.

(the difference between making the backup at the client or the server
in Zed's configuration where preferences is mounted shared from a server)

or perhaps savelog should.

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall


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

Bug#301671: apt-listbugs: cron.daily destroys the contents of symlinked /etc/apt/preferences

[paddy]

On Mon, Apr 11, 2005 at 01:33:16PM +0100, paddy wrote:
 PTMP=$(tempfile)
 /usr/share/apt-listbugs/aptcleanup  $PTMP
 if ! diff $PTMP /etc/apt/preferences  /dev/null; then
   savelog /etc/apt/preferences
   mv $PTMP /etc/apt/preferences
 fi

D'oh!

s/mv/cp/

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall


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

Bug#301671: apt-listbugs: cron.daily destroys the contents of symlinked /etc/apt/preferences

[paddy]

Hi,

[EMAIL PROTECTED] writes:
snip
 If you don't notice it before the next night's autoupgrade sequence 
 suddenly tries to update a bunch of machines on your network to 
 unstable, breaking them all
snip

*ouch* that would hurt.

I just noticed that:

 Why is package X not in testing yet?
 Checking apt-listbugs
 
 * apt-listbugs is scheduled for removal
 * Removal request by vorlon 
 
Is this because of this bug ?

From your description, the real problem is with aptcleanup?
which sadly I don't understand, yet.

Does this cron job even need to be enabled by default?

I really like apt-listbugs, it would be a shame to lose it.

On a rather silly note, 

Perhaps there should be a mechanism in apt-listbugs to issue a recall
by placing a bug in the BTS.  It could then issue a message along 
the lines of:

### 
### We have just recieved an urgent message 
###  from an apt-bugs in the future.
### 
###  This mission will now self-terminate.
###  Expect the replacement agent shortly.
###

or perhaps this is a job better left to apt-removebugs ...

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall


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

Bug#291234: [Parted-maintainers] Bug#291234: parted: No Implementation: This ext2 filesystem has a rather strange layout! Parted No Implementation: This ext2 filesystem has a rather strange layout!

[paddy]

What you can do as a workaround is use the relevant tool to remove
the ext3 features that parted doesn't like, resize, and then add them
back in.

Off the top of my head, 
debugfs (use 'help' and 'features').
??? doesn't like journal or hashed directory indexes

Sorry I don't recall the exact specifics, I recommend you check the
details before you do anything (and don't forget that backup !)

The exact details are surprisingly hard to google up quickly, although
I expect they feature prominently in a HOWTO or FAQ somewhere.  Simply
improving the error message would be a huge step: google turns up large
numbers of people stumped by this error message.

Regards,
Paddy

On Wed, Jan 19, 2005 at 03:47:11PM +0100, Joel Soete wrote:
 Package: parted
 Version: 1.6.11-9
 Severity: normal
 
 Hello all,
 
 I am running a debian  unstable' (today updated) with a developement kernel
 2.6.11-rc1-pa3 on hppa box (b2000).
 This system own 2 Disk: one boot disk of 9gb and a 'data' disk of 36Gb.
 
 the boot disk sda has the following slicing schema (cfdisk):
 Disk /dev/sda: 9100 MB, 9100044288 bytes
 64 heads, 32 sectors/track, 8678 cylinders
 Units = cylinders of 2048 * 512 = 1048576 bytes
 
Device Boot  Start End  Blocks   Id  System
 /dev/sda1   1  61   62448   f0  Linux/PA-RISC boot
 /dev/sda2  62 306  250880   82  Linux swap / Solaris
 /dev/sda3 307 367   62464   83  Linux
 /dev/sda4 3688557 83865605  Extended
 /dev/sda5 3681953 1624048   83  Linux
 /dev/sda619542197  249840   83  Linux
 /dev/sda721982319  124912   83  Linux
 /dev/sda823202441  124912   83  Linux
 /dev/sda924424394 1999856   83  Linux
 /dev/sda10   43956347 1999856   83  Linux
 /dev/sda11   63488300 1999856   83  Linux
 /dev/sda12   83018557  263152   83  Linux
 
 And the second disk:
 Disk /dev/sdb: 36.4 GB, 36420075520 bytes
 64 heads, 32 sectors/track, 34732 cylinders
 Units = cylinders of 2048 * 512 = 1048576 bytes
 
Device Boot  Start End  Blocks   Id  System
 /dev/sdb1   1   3473235565552   83  Linux
 
 As I don't need any more to have the full disk for a data slice on this disk,
 I would like to use parted to re-partition as:
 /dev/sdb1   1  61   62448   f0  Linux/PA-RISC boot
 /dev/sdb2  62 306  250880   82  Linux swap / Solaris
 /dev/sdb3 307 367   62464   83  Linux
 /dev/sdb4 3688557 83865605  Extended
 /dev/sdb5 3681953 1624048   83  Linux
 /dev/sdb619542197  249840   83  Linux
 /dev/sdb721982319  124912   83  Linux
 /dev/sdb823202441  124912   83  Linux
 /dev/sdb924424394 1999856   83  Linux
 /dev/sdb10   43956347 1999856   83  Linux
 /dev/sdb11   63488300 1999856   83  Linux
 /dev/sdb12   8301   3473235565552   83  Linux
 
 (for mirroring with raid1)
 
 (in summary:
 parted
 resize 1 0.016 26432.000 (i.e. 34732 - 8300)
 move 1 0.016 8300.000
 
 then create sdb[1..11] )
 
 but when I asked 'parted' to check the disk slice 1:
 # ./parted/parted /dev/sdb
 [...]
 Using /dev/sdb
 (parted) p  
 
 Disk geometry for /dev/sdb: 0.000-34732.890 megabytes
 Disk label type: msdos
 MinorStart   End Type  Filesystem  Flags
 1  0.016  34732.000  primary   ext3
 (parted) check 1
 
 No Implementation: This ext2 filesystem has a rather strange layout!  Parted
 can't resize this (yet).
 
 So am I not very confident to go ahead ;-)
 
 As sudgested on gnu site I grab the last 1.6.21 release which I build
 # ../configure --prefix=/usr --sbindir=/sbin --mandir=\${prefix}/share/man
 --infodir=\${prefix}/share/info --enable-mtrace --disable-shared  
 --build=hppa-linux
 --host=hppa-linux
 (as debian debug pkg would do?)
 
 but the pb is the same:
 # ./parted/parted /dev/sdb
 
 GNU Parted 1.6.21
 Copyright (C) 1998 - 2004 Free Software Foundation, Inc.
 This program is free software, covered by the GNU General Public License.
 
 This program is distributed in the hope that it will be useful, but WITHOUT
 ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General
 Public License for more details.
 
 Using /dev/sdb
 (parted) p  
 
 Disk geometry for /dev/sdb: 0.000-34732.890 megabytes
 Disk label type: msdos
 MinorStart   End Type  Filesystem  Flags
 1  0.016