Bug#553111: baycomepp: postinst-must-call-ldconfig
On Sun, Nov 29, 2009 at 05:39:37PM -0800, Yoshio Nakamura wrote: > Package baycomepp > tags 553111 +patch > thanks > > On Sat, Nov 28, 2009 at 06:43:43PM +0100, gregor herrmann wrote: > > On Wed, 28 Oct 2009 23:49:35 -0500, Manoj Srivastava wrote: > > > > > Package: baycomepp > > > Version: 0.10-12 > > > Severity: serious > > > Justification: The package installs shared libraries in a directory > > > controlled > > > User: lintian-ma...@debian.org > > > Usertags: postinst-must-call-ldconfig > > > > > > Refer to Debian Policy Manual section 8.1.1 (ldconfig) for details. > > > > The attached patch fixes this bug, but the output of dpkg-shlibdeps > > doesn't make me happy: > > > > dpkg-shlibdeps: warning: symbol sig_usr2 used by > > debian/baycomepp/usr/lib/baycomfpga_init.so found in none of the libraries. > > I looked at > http://lintian.debian.org/maintainer/debian-h...@lists.debian.org.html > , and saw baycomepp listed, with links: > * W shlib-without-versioned-soname --- > http://lintian.debian.org/tags/shlib-without-versioned-soname.html > o usr/lib/baycomfpga_init.so baycomfpga_init.so > * E postinst-must-call-ldconfig > o usr/lib/baycomfpga_init.so > * W package-name-doesnt-match-sonames --- > http://lintian.debian.org/tags/package-name-doesnt-match-sonames.html > o baycomfpga-init One of the programs in baycomepp is dlopen()ing baycomfpga_init.so, so no versioned soname is required. The symbols sig_usr2 etc are provided by the hosting application. I don't know why the application has been structued this way - possibly as a hack around some licensing issues. baycomfpga_init.so contains binary blobs of firmware for the hardware. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#553111: baycomepp: postinst-must-call-ldconfig
On Mon, Nov 30, 2009 at 06:41:44PM +0100, gregor herrmann wrote: > On Mon, 30 Nov 2009 17:29:58 +1100, Hamish Moffatt wrote: > > > On Sun, Nov 29, 2009 at 05:39:37PM -0800, Yoshio Nakamura wrote: > > > Package baycomepp > > > tags 553111 +patch > > > thanks > > Thanks, I indeed forgot the tag. > > > > > The attached patch fixes this bug, but the output of dpkg-shlibdeps > > > > doesn't make me happy: > > > > dpkg-shlibdeps: warning: symbol sig_usr2 used by > > > > debian/baycomepp/usr/lib/baycomfpga_init.so found in none of the > > > > libraries. > > > One of the programs in baycomepp is dlopen()ing baycomfpga_init.so, so > > no versioned soname is required. The symbols sig_usr2 etc are provided > > by the hosting application. > > Ah, thanks for the explanation. > > I guess you're talking care about the upload to fix the ldconfig bug? NMU is ok, is it already in the delayed upload queue? thanks, Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#553111: baycomepp: postinst-must-call-ldconfig
On Tue, Dec 01, 2009 at 12:04:36AM +0100, gregor herrmann wrote: > On Tue, 01 Dec 2009 09:44:07 +1100, Hamish Moffatt wrote: > > > > I guess you're talking care about the upload to fix the ldconfig bug? > > NMU is ok, is it already in the delayed upload queue? > > No, I was scared by the warnings. > > Ok, I've uploaded it now, into DELAYED/2, just in case. Thanks for your help with this bug Gregor. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527840: Needs to be actively maintained or removed
On Thu, Dec 03, 2009 at 10:29:50PM +0100, Moritz Muehlenhoff wrote: > The only really supportable way would be to hack xpdf to link against > poppler, maintaining a separate copy needs to stop for Squeeze. I agree in the context of the current maintenance of the Xpdf package, but if Xpdf was fully maintained I think that's rather unfair to Xpdf upstream. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527840: Needs to be actively maintained or removed
On Thu, Jul 23, 2009 at 01:18:44PM -1000, Ryo Furue wrote: > Hi > > > (An cleanest solution might be to drop xpdf altogether; the > > correct way to implement a PDF viewer these days is to build > > on top of poppler, such a okular, evince or epdfview. > > xpdf has been the only PDF viewer that is light enough > to be usable remotely(*). I wish it's maintained rather > than abandoned. > > Ryo > --- > (*)I log in to my workstation at my workplace from home > and invoke xpdf: For example, > > home$ ssh -X work.example.com > . . . log in to "work" . . . > work$ xpdf mydoc.pdf & > work$ > > okular and acroread are so slow that it's utterly > impossible to use remotely. > (I've never used evince or epdfview.) It's available for adoption - #535261. Hamish -- Hamish Moffatt VK3SB -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527840: Needs to be actively maintained or removed
On Tue, Jul 28, 2009 at 03:13:39PM -1000, Ryo Furue wrote: > Hi Moritz, > > | xpdf is a dead end. > | > I'm sorry to hear that. (No, it's not possible > for me to take care of the package, unfortunately.) That's Moritz's observation/opinion rather than Xpdf's author's. It's certainly a long time between releases though. Hamish -- Hamish Moffatt VK3SB -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567932: schroot: chroot failed, cleaned up my host /etc
Package: schroot Version: 1.4.0-1 Severity: critical Justification: causes serious data loss I upgraded schroot from 1.2.3-1+b1 to 1.4.0-1, which wanted to replace some config files, which I have customised. I declined, intending to fix it later. I started an schroot into an old sid 32-bit chroot (from my sid 64-bit host), and didn't notice any error messages, but found I was still running 64-bit binaries. I think the actual chroot() failed. Later after exitting, I found that a bunch of files in /etc were now empty: passwd, group, shadow, hosts, protocols, services. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages schroot depends on: ii libboost-filesystem1.40.01.40.0-6+b1 filesystem operations (portable pa ii libboost-program-options1.40 1.40.0-6+b1 program options library for C++ ii libboost-regex1.40.0 1.40.0-6+b1 regular expression library for C++ ii libboost-system1.40.01.40.0-6+b1 Operating system (e.g. diagnostics ii libc62.10.2-5Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.3-1 GCC support library ii liblockdev1 1.0.3-1.3 Run-time shared library for lockin ii libpam0g 1.1.0-4 Pluggable Authentication Modules l ii libstdc++6 4.4.3-1 The GNU Standard C++ Library v3 ii libuuid1 2.16.2-0Universally Unique ID library ii schroot-common 1.4.0-1 common files for schroot schroot recommends no packages. Versions of packages schroot suggests: pn aufs-modules | unionfs-module (no description available) ii debootstrap 1.0.20 Bootstrap a basic Debian system ii lvm2 2.02.54-1 The Linux Logical Volume Manager ii unzip 6.0-1 De-archiver for .zip files -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561906: [Pkg-electronics-devel] Bug#561906: FTBFS: make[5]: *** [tests] Error 1
On Mon, Dec 21, 2009 at 07:31:20AM +0100, Cyril Brulebois wrote: > Package: geda-gaf > Version: 1:1.6.0-1 > Severity: serious > Justification: FTBFS > > Hi, > > your package FTBFS on all buildds. Build logs at the usual place: > https://buildd.debian.org/status/package.php?suite=unstable&p=geda-gaf > | 1,2d0 > | < ERROR: Found a bus inside a symbol > | < 1 ERROR found This is a mystery to us and to upstream. The tests are comparing the output of the gsymcheck program with pre-prepared output via diff. From the diff output it looks like the newly built gsymcheck is producing no output at all. It behaves ok in pbuilder, and in a regular build tree built as both a normal user with fakeroot, and as root. Are there any other environment differences on the autobuilders that we should be aware of that may help? Is the build log capturing stderr, or do we need to modify the package build scripts to redirect stderr to stdout? thanks Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561906: [Pkg-electronics-devel] Bug#561906: FTBFS: make[5]: *** [tests] Error 1
On Mon, Dec 21, 2009 at 03:03:33PM +0100, Cyril Brulebois wrote: > Hamish Moffatt (21/12/2009): > > This is a mystery to us and to upstream. The tests are comparing the > > output of the gsymcheck program with pre-prepared output via > > diff. From the diff output it looks like the newly built gsymcheck > > is producing no output at all. > > > > It behaves ok in pbuilder, and in a regular build tree built as both > > a normal user with fakeroot, and as root. > > > > Are there any other environment differences on the autobuilders that > > we should be aware of that may help? Is the build log capturing > > stderr, or do we need to modify the package build scripts to > > redirect stderr to stdout? > > Usual suspects: > - HOME being set to a non-existing directory, or even more tricky: to >a directory which exists but which isn't writable. > - no net access. > > In this case, I was able to trigger a successful build on my > kfreebsd-i386 porterbox with “debuild -B”, and a failed build with > “HOME=/foo debuild -B”. > > Happy fixing. ;) Thanks! I see now that it's trying to write logs into ~/.gEDA which won't work with an unwritable/non-existent $HOME. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561906: [Pkg-electronics-devel] Bug#561906: FTBFS: make[5]: *** [tests] Error 1
On Mon, Dec 21, 2009 at 10:14:40PM +, Peter Clifton wrote: > On Tue, 2009-12-22 at 08:14 +1100, Hamish Moffatt wrote: > > > Thanks! I see now that it's trying to write logs into ~/.gEDA which won't > > work with an unwritable/non-existent $HOME. > > Perhaps we will be able to fix this upstream (for 1.6.1?). > > Hamish.. is there any way we can work around the issue for the 1.6.0 > build? Can we export a temporary $HOME somewhere in the build tree > whilst the tests are run? Yes I think that would be the best solution for now. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561906: [Pkg-electronics-devel] Bug#561906: FTBFS: make[5]: *** [tests] Error 1
On Mon, Dec 21, 2009 at 10:14:40PM +, Peter Clifton wrote: > Hamish.. is there any way we can work around the issue for the 1.6.0 > build? Can we export a temporary $HOME somewhere in the build tree > whilst the tests are run? I've uploaded a workaround. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561906: [Pkg-electronics-devel] Bug#561906: FTBFS: make[5]: *** [tests] Error 1
On Mon, Dec 21, 2009 at 03:03:33PM +0100, Cyril Brulebois wrote: > Usual suspects: > - HOME being set to a non-existing directory, or even more tricky: to >a directory which exists but which isn't writable. > - no net access. > > In this case, I was able to trigger a successful build on my > kfreebsd-i386 porterbox with “debuild -B”, and a failed build with > “HOME=/foo debuild -B”. Hmm, so I set HOME= a temporary directory under $(PWD), but it's failed too because $(PWD) was not the root of the unpacked source tree.. I'm really confused about how dpkg-buildpackage is being called? Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561906: [Pkg-electronics-devel] Bug#561906: Bug#561906: FTBFS: make[5]: *** [tests] Error 1
On Tue, Dec 22, 2009 at 07:25:29AM +0200, أحمد المحمودي wrote: > On Tue, Dec 22, 2009 at 06:54:19AM +0200, أحمد المحمودي wrote: > > On Tue, Dec 22, 2009 at 11:18:30AM +1100, Hamish Moffatt wrote: > > > Hmm, so I set HOME= a temporary directory under $(PWD), but it's failed > > > too because $(PWD) was not the root of the unpacked source tree.. I'm > > > really confused about how dpkg-buildpackage is being called? > > ---end quoted text--- > > > > Use $(CURDIR) > ---end quoted text--- > > I've uploaded a new Debian release to mentors: > http://mentors.debian.net/debian/pool/main/g/geda-gaf/geda-gaf_1.6.0-3.dsc Uploaded, thanks Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561906: [Pkg-electronics-devel] Bug#561906: Bug#561906: FTBFS: make[5]: *** [tests] Error 1
On Tue, Dec 22, 2009 at 02:05:00PM +0200, أحمد المحمودي wrote: > On Tue, Dec 22, 2009 at 10:56:17PM +1100, Hamish Moffatt wrote: > > Uploaded, thanks > ---end quoted text--- > > Thanks, it's wierd though that 1.6.0-2 built successfully only on armel > (even though $PWD evaluated to /home/buildd) ! Yes... the i386 autobuilder just succeeded on -3 so perhaps we have success at last. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#550256: podracer: intent to nmu
NMU whenever you are ready. If you want to adopt or co-maintain the package that would help.. Real life interests are taking all my time lately. Thanks. -original message- Subject: podracer: intent to nmu From: Rémi Vanicat Date: 23/01/2010 5:45 PM Hello, podracer has this old critical bug with patch. I will nmu it soon By the way, do you need help to maintain this package? 2+ month to fix such a small bug is a very long time. -- Rémi Vanicat -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567932: [buildd-tools-devel] Bug#567932: schroot: chroot failed, cleaned up my host /etc
Hi Roger,
Here are the only files which were modified. I have since put in the
versions from 1.4.0-1 and customized those and schroot is working fine.
Hamish
# schroot chroot definitions.
# See schroot.conf(5) for complete documentation of the file format.
#
# Please take note that you should not add untrusted users to
# root-groups, because they will essentially have full root access
# to your system. They will only have root access inside the chroot,
# but that's enough to cause malicious damage.
#
# The following lines are examples only. Uncomment and alter them to
# customise schroot for your needs, or create a new entry from scratch.
#
#
[sid]
description=Debian sid (unstable) 32-bit
location=/var/chroot/i386-sid
priority=3
users=hamish
root-groups=root
run-setup-scripts=true
run-exec-scripts=true
aliases=unstable,default
type=directory
personality=linux32
[etch]
description=Debian etch (4.0) 64-bit
location=/var/chroot/amd64-etch
priority=3
users=hamish
root-groups=root
run-setup-scripts=true
type=directory
[gutsy]
description=Ubuntu Gutsy 64-bit
location=/var/chroot/amd64-gutsy
priority=3
users=hamish
root-groups=root
run-setup-scripts=true
type=directory
[gutsy32]
description=Ubuntu Gutsy 32-bit
location=/var/chroot/i386-gutsy
priority=3
users=hamish
root-groups=root
run-setup-scripts=true
type=directory
personality=linux32
[etch32]
description=Debian etch (4.0) 32-bit
location=/var/chroot/i386-etch
priority=3
users=hamish
root-groups=root
run-setup-scripts=true
type=directory
personality=linux32
[feisty]
description=Ubuntu Feisty (7.04) 32-bit
location=/var/chroot/i386-feisty
priority=3
users=hamish
root-groups=root
run-setup-scripts=true
type=directory
personality=linux32
#
#[sid-snap]
#type=lvm-snapshot
#description=Debian sid snapshot
##location=/srv/chroot/sid
#priority=3
#groups=sbuild,root
#root-users=rleigh
#root-groups=root,sbuild
#source-root-users=rleigh
#device=/dev/hda_vg/sid_chroot
#mount-options=-o atime,sync,user_xattr
#lvm-snapshot-options=--size 2G
#run-setup-scripts=true
#run-exec-scripts=true
#
#[etch]
#description=Debian etch (testing) 32-bit
#location=/srv/chroot/etch
#priority=3
#groups=sbuild-security
#aliases=testing
#run-setup-scripts=false
#run-exec-scripts=false
#personality=linux32
#
#[sarge]
#description=Debian sarge (stable)
#location=/srv/chroot/sarge
#priority=2
#groups=sbuild
#aliases=stable
#
#[sarge-file]
#description=Debian sarge (stable)
#file=/srv/chroot/sarge.tar.gz
#priority=2
#groups=sbuild
#
#[sarge-secure]
#description=Debian sarge (stable)
#location=/srv/chroot/sarge
#priority=2
#groups=sbuild-security
#aliases=stable-security
#
#[experimental]
#type=block-device
#description=Debian experimental (unstable)
#priority=4
#groups=sbuild,root
#root-groups=root,sbuild
#aliases=unstable,default
#device=/dev/hda_vg/experimental_chroot
#mount-options=-o atime,sync,user_xattr
#location=/experimental
#run-setup-scripts=true
#run-exec-scripts=true
#!/bin/sh
# Copyright © 2005-2007 Roger Leigh
#
# schroot is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# schroot 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.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston,
# MA 02111-1307 USA
set -e
if [ -f "$CHROOT_SCRIPT_CONFIG" ]; then
. "$CHROOT_SCRIPT_CONFIG"
fi
# Mount a filesystem
# $1: mount options
# $2: mount device
# $3: mount location
do_mount()
{
if [ "$AUTH_VERBOSITY" = "verbose" ]; then
echo "Mounting $2 on $3"
fi
if [ ! -d "$3" ]; then
mkdir -p "$3"
fi
if [ ! -d "$3" ]; then
echo "$3 does not exist, and could not be created"
exit 1
fi
mount $VERBOSE $1 "$2" "$3"
}
# Unmount all filesystem under specified location
# $1: mount base location
do_umount_all()
{
mounts="$("$LIBEXEC_DIR/schroot-listmounts" -m "$1")"
if [ "x$mounts" != 'x' ]; then
echo "$mounts" |
while read mountloc; do
if [ "$AUTH_VERBOSITY" = "verbose" ]; then
echo "Unmounting $mountloc"
fi
umount "$mountloc" || exit 1
done || exit 1
fi
}
if [ "$AUTH_VERBOSITY" = "verbose" ]; then
VERBOSE="-v"
# FSCK_VERBOSE="-V"
fi
if [ "$CHROOT_TYPE" = "plain" ] || [ "$CHROOT_TYPE" = "directory" ] || [
"$CHROOT_TYPE" = "file" ] || [ "$CHROOT_TYPE" = "block-device" ] || [
"$CHROOT_TYPE" = "lvm-snapshot" ]; then
if [ "$CHROOT_TYPE" = "plain" ]; then
CHROOT_MOUNT_OPTIONS="--rbind"
CHROOT_MOUNT_DEVICE="$CHROOT_LOCATION"
elif [ "$C
Bug#567932: [buildd-tools-devel] Bug#567932: schroot: chroot failed, cleaned up my host /etc
On Wed, Feb 17, 2010 at 11:12:52PM +, Roger Leigh wrote: > On Thu, Feb 18, 2010 at 09:41:17AM +1100, Hamish Moffatt wrote: > > Here are the only files which were modified. I have since put in the > > versions from 1.4.0-1 and customized those and schroot is working fine. > > Many thanks, I'll look at these in more detail tomorrow. > > Just to check, if you didn't upgrade the altered conffiles during the > update, this left 10mount in its customised state with the replacement > as 10mount.dpkg-new, and all the other setup scripts were updated? That's correct. thanks, Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594901: system-config-printer: won't start - syntax error
Package: system-config-printer Version: 1.2.3-0.3 Severity: serious Justification: won't start [11:37PM] ham...@buzzword:~ $ system-config-printer Traceback (most recent call last): File "/usr/bin/X11/system-config-printer", line 95, in import jobviewer File "/usr/share/system-config-printer/jobviewer.py", line 21, in import asyncconn File "/usr/share/system-config-printer/asyncconn.py", line 27, in import asyncpk1 File "/usr/share/system-config-printer/asyncpk1.py", line 82 reply_handler=self._pk_reply_handler, ^ SyntaxError: invalid syntax -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.29-2-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages system-config-printer depends on: ii gnome-icon-theme 2.28.0-1 GNOME Desktop icon theme ii python2.5.4-9An interactive high-level object-o ii python-cups 1.9.48-1 Python bindings for CUPS ii python-cupshelpers1.2.3-0.3 Python utility modules around the ii python-dbus 0.83.1-1 simple interprocess messaging syst ii python-glade2 2.17.0-4 GTK+ bindings: Glade support ii python-gnome2 2.28.0-2 Python bindings for the GNOME desk ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge ii python-notify 0.1.1-2+b2 Python bindings for libnotify ii python-support1.0.7 automated rebuilding support for P Versions of packages system-config-printer recommends: ii cups-pk-helper0.1.0-2PolicyKit helper to configure cups ii system-config-printer-udev1.2.3-0.3 Utilities to detect and configure Versions of packages system-config-printer suggests: pn python-gnomekeyring(no description available) pn python-smbc(no description available) pn sessioninstaller (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770954: gmFSK maintainence
On 06/05/15 01:37, Iain R. Learmonth wrote: Hi Hamish, Do you plan to do any porting of gmFSK to use ALSA or PulseAudio from OSS? If not, I can file a removal bug for this. We have plenty of other packages in Debian for various digital modes. Please record your reply on this bug if you're happy for the package to be removed so I can point ftp-master at it. Hi Iain, No I don't intend to do any work on gMFSK. It would be better for it to be removed. Thanks, Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#857327: libapache2-authenntlm-perl: does not work with Apache 2.4
On 11/03/17 02:46, gregor herrmann wrote: From reading the above URLs, it seems that remote_addr -> client_addr remote_ip -> client_ip should do the trick. Could you maybe try this proposed fix? If it works, we can prepare an updated package for stretch. I tried that, and it's better - no problems on the Apache side at least. I think it's outdated on the NTLM side, as Edge on Windows 10 was not able to authenticate to it. But the basic authentication fallback works at least, as I was able to authenticate that way from cURL. Given that this package has been broken for years without anyone noticing perhaps it should be removed instead? thanks, Hamish
Bug#750141: libqt4-xml: vulnerable to billion laughs attack
On 09/06/14 15:17, Salvatore Bonaccorso wrote:
Hi,
On Sun, Jun 01, 2014 at 11:30:15PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
tag 750141 moreinfo
thanks
On Monday 02 June 2014 11:19:05 Hamish Moffatt wrote:
Package: libqt4-xml
Severity: serious
Tags: security
Justification: security
Qt 4.8.6 has a fix for a denial of service attack due to XML entity
expansion ("billion laughs attack"). This fix doesn't seem to be in the
wheezy packages yet.
http://blog.qt.digia.com/blog/2014/04/24/qt-4-8-6-released/
Ubuntu patched their 4.8.4;
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1259577
Hi Hamish! I patched Qt4 for jessie at that time but IIRC (I might be mixing
CVEs here) when I asked someone from the security team over IRC (or maybe by
mail, I don't remember now) they told me it wasn't too important to get an
update in stable.
Yep, perl mail It was on 2013-12-06, where Moritz had written:
Hi Lisandro,
this doesn't warrant a DSA. It can be fixed through a point update, though
or we can line it up for a future QT DSA.
Cheers,
Moritz
For the BTS, I think this was fixed in 4:4.8.5+git192-g085f851+dfsg-1.
Hi. OK I guess I can understand it not being too important to update
stable; while there are quite a lot of rdepends for libqt4-xml I don't
see many daemons among them. Depends on whether libqt4-xml is just being
used for config or whether to decode wire protocols, ie those apps could
be vulnerable to remote denial of service. mumble-server is one daemon I
notice..
Thanks
Hamish
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750141: libqt4-xml: vulnerable to billion laughs attack
Package: libqt4-xml
Severity: serious
Tags: security
Justification: security
Qt 4.8.6 has a fix for a denial of service attack due to XML entity
expansion ("billion laughs attack"). This fix doesn't seem to be in the
wheezy packages yet.
http://blog.qt.digia.com/blog/2014/04/24/qt-4-8-6-released/
Ubuntu patched their 4.8.4;
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1259577
Hamish
-- System Information:
Debian Release: 7.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#374131: gerbv: gerbv 1.0.1 works incorrectly with GTK+ 2
On Sat, Jun 17, 2006 at 04:45:50PM +0400, Evgeny M. Zubok wrote: > Package: gerbv > Version: 1.0.1-2 > Severity: grave > > gervbv from Debian/Etch incorrectly shows the GERBER files with GTK+ 2. It > works well only with GTK+ 1.2 and gdk-pixbuf2. Hi, Can you please provide an example file and tell me how it is different? I build 1.0.1-2 with GTK+ 1.2 here and I could not see a difference with the example files. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374131: (no subject)
On Sat, Jun 17, 2006 at 07:58:44PM +0400, Evgeny M. Zubok wrote: > For example, take GERBER from Ronja project. > http://www.artelektronika.ru/bug/twister.pcb.output_front.gbr > > gerbv 1.0.1 (GTK+ 1.2): > http://www.artelektronika.ru/bug/gerbv_1.0.1_with_gtk1.png > > gerbv 1.0.1 (GTK+ 2.0) from official Debian Repository: > http://www.artelektronika.ru/bug/gerbv_1.0.1_with_gtk2.png Hi, Thanks for the examples. However I can't reproduce your results. With the standard gerbv from etch, my result looks identical to your GTK+ 2.0 result. I tested in unstable(sid) on both i386 and amd64 architectures. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388649: "Probably parenthesis mismatch in" errors in geda
On Thu, Sep 21, 2006 at 02:39:56PM -0400, H. S. wrote: > Package: geda > Version: 20060123-1 > Severity: grave > Justification: renders package unusable Hi, This bug is with gschem so please report it against gschem. Then I would get gschem's dependency information (eg your libgeda20 and geda-symbols versions). Could you please tell me your versions of those two? I suspect the problem could be that etch (testing) now has geda-symbols from gEDA 20060906, while the other packages are still 20060123. Have you modified any of the configuration files? Perhaps you could report this bug again against geda-gschem. Then I would get your configuration files also. Thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388695: geda-gschem: "Probably parenthesis mismatch in" errors in gschem
On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote: > (here is the bug again here for geda-gschem, instead of for geda) Thanks. geda-gschem 20060906 should be in etch in a day or two. Can you try it again then and see if the problem is solved? system-gafrc is provided by geda-symbols, which is already updated in etch. However system-gschemrc is not yet. I suspect the skew between them is causing the problem. I will tighten the dependencies in the future. > ii geda-gschem20060123-1 GNU EDA -- Electronics design software -- > sc > ii geda-symbols 20060906-1 Symbols for GNU EDA -- Electronics design > so thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388695: geda-gschem: "Probably parenthesis mismatch in" errors in gschem
reassign 388695 geda-symbols thanks On Thu, Sep 21, 2006 at 11:50:42PM -0700, Steve Langasek wrote: > On Fri, Sep 22, 2006 at 03:22:17PM +1000, Hamish Moffatt wrote: > > On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote: > > > (here is the bug again here for geda-gschem, instead of for geda) > > Thanks. geda-gschem 20060906 should be in etch in a day or two. > Not if this RC bug is open, it won't be. Good to know. > > system-gafrc is provided by geda-symbols, which is already updated in > > etch. However system-gschemrc is not yet. I suspect the skew between > > them is causing the problem. I will tighten the dependencies in the > > future. > > If you're certain that this is the cause, which package needs to be updated > with added conflicts -- geda-symbols or geda-gschem? If it's geda-symbols, > could you please reassign this bug there? If the change needs to be made to > geda-gschem, please say so and I'll override this RC bug for the update into > testing for now. Well, upgrading geda-gschem will certainly get it working. As to where the change belongs I'm not sure -- basically the two packages need to have matched versions. So either geda-gschem (and geda-gnetlist, gsymcheck, gattrib and possibly utils) conflict with a newer geda-symbols, or symbols conflicts with old geda-*. I think I prefer the latter solution, so I'll reassign. thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389154: geda-gschem: gschem crashing after start and gschem don't work properly
On Sun, Sep 24, 2006 at 03:50:59PM +0400, [EMAIL PROTECTED] wrote: > Package: geda-gschem > Version: 20060123-1 > Severity: critical > > gEDA/gschem version 20060123 > Versions of packages geda-gschem depends on: > ii geda-symbols20060906-1 Symbols for GNU EDA -- > Electronics Hi, It's because you have mismatched versions of geda-symbols (20060906) and geda-gschem (20060123). It's already reported as #388695. Please upgrade. etch (testing) has working versions of everything now. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347386: guile-gtk: [m68k, ia64]: FTBFS m68k-linux-gcc: command not found
On Tue, Jan 10, 2006 at 02:37:35PM +0100, Christian T. Steigies wrote: > Package: guile-gtk > Version: 1.2_0.31-4 > Severity: serious > Justification: no longer builds from source > > Hi, > your package fails to build on m68k and ia64, since you specify a (no > longer) existing/used compiler: > > guile-1.6-snarf -o guile-gtk.x guile-gtk.c -DHAVE_CONFIG_H -I. -I. > -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include > -D_REENTRANT -g -O2 > /usr/bin/guile-1.6-snarf: line 53: m68k-linux-gcc: command not found > make[1]: *** [guile-gtk.x] Error 1 > > If you have to call the compile by it's exact name, it is m68k-linux-gnu-gcc > since etch, and probably similar for ia64. It should not build on other > arches as well, but maybe they still have an older compiler installed > besides the default gcc-4.0. Actually this appears to be bug#317600, which is that guile-1.6-snarf is calling the wrong compiler. That bug is fixed in guile-1.6 1.6.7-1.1, which isn't built on m68k or ia64 due to bug#326905. Even on i386 and amd64 it's actually calling x86_64-linux-gnu-gcc. m68k and ia64 must have renamed their compiler since guile-1.6 last built properly. Looks like I can workaround this anyway. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364693: glade-gnome: uninstallable on amd64 due to binNMU, not binNMU-safe
Package: glade-gnome Version: 2.12.1-3+b1 Severity: serious Justification: uninstallable glade has been binNMUd for amd64, resulting in version 2.12.1-3+b1. However it depends on glade-common (= 2.12.1-3+b1) which will not exist, as this was a binNMU. Hence glade is uninstallable. The dependencies need to be modified to be binNMU-safe. Thanks, Hamish -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-amd64-k8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages glade-gnome depends on: ii glade-common 2.12.1-3Common files for GTK+ 2 User Inter ii gnome-common 2.12.0-1common scripts and macros to devel ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libatk1.0-0 1.11.4-1The ATK accessibility toolkit ii libaudiofile00.2.6-6 Open-source version of SGI's audio ii libavahi-client3 0.6.9-8+b1 Avahi client library ii libavahi-common3 0.6.9-8+b1 Avahi common library ii libavahi-glib1 0.6.9-8+b1 Avahi glib integration library ii libbonobo2-0 2.14.0-1Bonobo CORBA interfaces library ii libbonoboui2-0 2.14.0-2The Bonobo UI library ii libc62.3.6-7 GNU C Library: Shared libraries ii libcairo21.0.4-1+b1 The Cairo 2D vector graphics libra ii libdbus-1-2 0.61-5 simple interprocess messaging syst ii libesd0 0.2.36-3Enlightened Sound Daemon - Shared ii libfontconfig1 2.3.2-5.1 generic font configuration library ii libfreetype6 2.1.10-3FreeType 2 font engine, shared lib ii libgconf2-4 2.14.0-1GNOME configuration database syste ii libgcrypt11 1.2.2-1 LGPL Crypto library - runtime libr ii libglib2.0-0 2.10.2-1The GLib library of C routines ii libgnome-keyring00.4.9-1 GNOME keyring services library ii libgnome2-0 2.14.1-1The GNOME 2 library - runtime file ii libgnomecanvas2-02.14.0-2A powerful object-oriented display ii libgnomeui-0 2.14.1-1The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.1-1GNOME virtual file-system (runtime ii libgnutls12 1.2.9-2+b1 the GNU TLS library - runtime libr ii libgpg-error01.2-1 library for common error values an ii libgtk2.0-0 2.8.17-1The GTK+ graphical user interface ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library ii libjpeg626b-12 The Independent JPEG Group's JPEG ii liborbit21:2.14.0-1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-01.12.1-2Layout and rendering of internatio ii libpng12-0 1.2.8rel-5.1PNG library - runtime ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm6 1:1.0.0-4 X11 Session Management library ii libtasn1-2 1:0.2.17-2 Manage ASN.1 structures (runtime) ii libx11-6 2:1.0.0-6 X11 client-side library ii libxcursor1 1.1.5.2-5 X cursor management library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxi6 1:1.0.0-5 X11 Input extension library ii libxinerama1 1:1.0.1-4 X11 Xinerama extension library ii libxml2 2.6.23.dfsg.2-3 GNOME XML library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.0.2-4 X Rendering Extension client libra ii zlib1g 1:1.2.3-11 compression library - runtime Versions of packages glade-gnome recommends: ii autoconf 2.59a-9 automatic configure script builder ii automake1.4 1:1.4-p6-9 A tool for generating GNU Standard ii gettext 0.14.5-2GNU Internationalization utilities ii libgail-gnome-module 1.1.3-2 GNOME Accessibility Implementation ii libgail171.8.11-1+b1 GNOME Accessibility Implementation ii libgnomeui-dev 2.14.1-1The GNOME 2 libraries (User Interf -- no debconf information -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352371: xastir: FTBFS because of unmet build-dep on libgdal1-dev
severity 352371 minor thanks On Sat, Feb 11, 2006 at 04:56:23PM +0100, Luk Claes wrote: > Package: xastir > Severity: serious > Version: 1.8.0-1 > > Hi > > Your package FTBFS because libgdal1-dev is not available (anymore). You > might want to update the build dependency to libgdal1-1.3.1-dev. libgdal1-1.3.1-dev provides libgdal1-dev now. I'll update the dependency on the next upload anyway. (Or perhaps I shouldn't, since it seems more specific than libgdal1-dev and therefore more prone to change?) thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352371: xastir: FTBFS because of unmet build-dep on libgdal1-dev
On Sun, Mar 19, 2006 at 12:30:11AM +0100, Luk Claes wrote: > Hamish Moffatt wrote: > > libgdal1-1.3.1-dev provides libgdal1-dev now. I'll update the dependency > > on the next upload anyway. (Or perhaps I shouldn't, since it seems more > > specific than libgdal1-dev and therefore more prone to change?) > > It's not enough to have it provided by another package as the buildds > can't handle with that. So it's still a serious bug. Say what? What do you mean the buildds can't handle that? > Note that the bug is already fixed in a NMU by Matej Vela on 19 Feb... True, I forgot about that. thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352371: xastir: FTBFS because of unmet build-dep on libgdal1-dev
On Sun, Mar 19, 2006 at 12:53:12AM +0100, Luk Claes wrote: > Hamish Moffatt wrote: > > Say what? What do you mean the buildds can't handle that? > > The buildds will not try to install virtual packages. It will only > install real packages... So you could change the build-dep to Argh, that old bug. OK, you're right. "apt-get build-dep xastir" does the right thing, so I don't know why the buildds don't use that command instead. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#359017: marked as done (gpredict: Fails to install)
Benjamin Seidenberg <[EMAIL PROTECTED]> wrote: > Package: gpredict > > This package depends on hamlib3, however this package no longer exists > (although it is mentioned in hamlib-dev's description). Steve Langasek <[EMAIL PROTECTED]> wrote: > gpredict (and other hamlib-using packages) has been queued for binNMUs on > all architectures. Fixed packages should be available in unstable soon, > with no further action required from the maintainer to resolve this bug. I was planning to wait for the next hamlib to do anything because the package has been renamed again. Upstream's library filename is libhamlib-1.2.4.so.2.0.3, in the case of hamlib3. The API is compatible between versions but they keep changing the library filename unnecessarily. That's recently been fixed. Our hamlib4 contains libhamlib.so.2.0.4 (Joop pulled in the filename fix early, to remove the -1.2.4), meaning no more mass rebuilds in the future. However the package name still doesn't match the library version (not such a big deal). So, Joop is intending to change the name one last time to libhamlib2. Details are at http://lists.debian.org/debian-hams/2006/03/msg00012.html ; looks like it hasn't been uploaded yet though. So another round on binNMUs will be needed at that stage. Thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352767: lircd broken here also
I see the same issue with lircd. When the init.d script runs it, I get the following result: tv:/etc/lirc# lircd --driver=Default Driver `Default' not supported. Supported drivers: null debian/rules for lirc calls configure with "--with-driver=none" which doesn't look right? Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352767: --with-driver=serial
I recompiled with --with-driver=serial and it works for me now. --with-driver=any failed to compile due to #error directives in the BTTV driver. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352371: xastir 1.8.0-1.1 NMU
Hi Matej, OK. I think one week delay for an otherwise active maintainer is a bit quick but otherwise I have no objection. urgency=medium also seems unjustified? Thanks, Hamish On Sat, Feb 18, 2006 at 11:29:47PM +0100, Matej Vela wrote: > Hello, > > I'm doing an NMU of xastir to fix #352371; diff attached. > > Thanks, > > Matej > diff -u xastir-1.8.0/debian/changelog xastir-1.8.0/debian/changelog > --- xastir-1.8.0/debian/changelog > +++ xastir-1.8.0/debian/changelog > @@ -1,3 +1,10 @@ > +xastir (1.8.0-1.1) unstable; urgency=medium > + > + * NMU. > + * Update GDAL build dependency to libgdal1-1.3.1-dev. Closes: #352371. > + > + -- Matej Vela <[EMAIL PROTECTED]> Sat, 18 Feb 2006 23:23:40 +0100 > + > xastir (1.8.0-1) unstable; urgency=low > >* New upstream release > diff -u xastir-1.8.0/debian/control xastir-1.8.0/debian/control > --- xastir-1.8.0/debian/control > +++ xastir-1.8.0/debian/control > @@ -3,7 +3,7 @@ > Priority: optional > Maintainer: Hamish Moffatt <[EMAIL PROTECTED]> > Standards-Version: 3.6.2 > -Build-Depends: debhelper (>= 4), libax25-dev, lesstif2-dev, libxext-dev | > xlibs-dev, libxp-dev | xlibs-dev, libxt-dev | xlibs-dev, festival-dev > [!hppa], festival [!hppa], libmagick9-dev (>= 6:6.2.4.5-0.2) | libmagick-dev, > libshp-dev, gpsman, gpsmanshp, proj, libpcre3-dev, libcurl3-gnutls-dev | > libcurl-ssl-dev, libgdal1-dev > +Build-Depends: debhelper (>= 4), libax25-dev, lesstif2-dev, libxext-dev | > xlibs-dev, libxp-dev | xlibs-dev, libxt-dev | xlibs-dev, festival-dev > [!hppa], festival [!hppa], libmagick9-dev (>= 6:6.2.4.5-0.2) | libmagick-dev, > libshp-dev, gpsman, gpsmanshp, proj, libpcre3-dev, libcurl3-gnutls-dev | > libcurl-ssl-dev, libgdal1-1.3.1-dev | libgdal1-dev > > Package: xastir > Architecture: any -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352371: xastir 1.8.0-1.1 NMU
On Sun, Feb 19, 2006 at 11:37:01AM +0100, Matej Vela wrote: > Hamish Moffatt <[EMAIL PROTECTED]> writes: > > > On Sat, Feb 18, 2006 at 11:29:47PM +0100, Matej Vela wrote: > >> I'm doing an NMU of xastir to fix #352371; diff attached. > > > > OK. I think one week delay for an otherwise active maintainer is a bit > > quick but otherwise I have no objection. > > Sorry if I stepped on your toes. I just saw an RC bug with no activity > in a week, and didn't investigate further since we're in permanent BSP > mode at the moment. [1] > > [1] <http://lists.debian.org/debian-devel-announce/2006/01/msg1.html> OK no problem. Thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337729: [EMAIL PROTECTED]: geotoad 3.9.0b5 announcement (almost there)]
The new release appears to be imminent.. Cheers, Hamish - Forwarded message from Thomas Strömberg <[EMAIL PROTECTED]> - X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00, UNPARSEABLE_RELAY autolearn=ham version=3.1.0 From: Thomas Strömberg <[EMAIL PROTECTED]> Subject: geotoad 3.9.0b5 announcement (almost there) Date: Fri, 10 Mar 2006 17:36:39 -0500 To: Thomas Stromberg <[EMAIL PROTECTED]> Thanks again for you're rapid feedback. I've got another beta for you at http://toadstool.se/dist/geotoad/ The biggest change is how we're assembling the Windows executables. Please test on a Windows machine if you have it handy. The windows download is a lot larger now and will open much slower, but hopefully be more reliable under Windows 2000. I've switched from compiling executables with exerb and ruby 1.8.2 to using RubyScript2Exe with ruby 1.8.4. Here are the other changes: * If no caches are found in the TUI (text user interface), don't exit * Update the software listing in the FAQ * Do better at finding fun_scores.dat, and handle the loss if we cannot find it. Bug reported by Jason Beaird. * Rebuild Windows .exe to avoid timeout.rb deadlock. Bug reported by John Hooey. * You can now enable "verbose" (debugging) mode from the text user interface by pressing "v". * fix single-comment-in-GPX bug (and most likely others) reported by Medcin Medcin * fix --output relative path bug * display outputDir, not pwd in the TUI directory prompt I plan to release geotoad 3.9.0 tonight if no major issues are found. Thanks again! // Thomas Strömberg // http://toadstool.se/ // +1 678 773 9475 - End forwarded message - -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375923: preinst fails because /usr/doc/cpio does not exist
Package: cpio Version: 2.6-14 Severity: grave Justification: renders package unusable cpio 2.6-14's preinst fails here because /usr/doc/cpio does not exist. (This system was new pre-sarge hence has no /usr/doc leftovers.) The preinst does test -L /usr/doc/cpio && rm -f /usr/doc/cpio which returns a failure. Hamish -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages cpio depends on: ii libc6 2.3.6-15 GNU C Library: Shared libraries cpio recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358822: Processed: severity of 358822 is grave
On Tue, Jul 11, 2006 at 02:48:29PM -0700, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > severity 358822 grave > Bug#358822: www-sql: Upgrade build-depends from libmysqlclient10-dev to 15 > Severity set to `grave' from `minor' Please justify 'grave'. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358822: Processed: severity of 358822 is grave
On Tue, Jul 11, 2006 at 04:41:17PM -0700, Steve Langasek wrote: > On Wed, Jul 12, 2006 at 08:50:29AM +1000, Hamish Moffatt wrote: > > On Tue, Jul 11, 2006 at 02:48:29PM -0700, Debian Bug Tracking System wrote: > > > Processing commands for [EMAIL PROTECTED]: > > > > > severity 358822 grave > > > Bug#358822: www-sql: Upgrade build-depends from libmysqlclient10-dev to 15 > > > Severity set to `grave' from `minor' > > > Please justify 'grave'. > > libmysqlclient10-dev has been removed from unstable. > > Should probably be 'serious' rather than 'grave'. I figured as much. www-sql will need some work to build with the new version. Even the autoconf tests fail due to mysql_connect() disappearing. (Actually, it's still defined in mysql.h and the reference manual says it is deprecated, but it's missing from the shared library.) Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374131: Changing severity, Tagging
On Thu, Jul 20, 2006 at 06:59:26PM -0300, Margarita Manterola wrote: > I can reproduce this bug both in Etch and in Sid (i386), and in Sid (amd64). > I'm attaching the dependency list for all of them. Thanks. Turns out it's a locale problem - I can reproduce it if I set my locale to es_ES, but it looks fine in en_AU. As you reported it's fixed in 1.0.2. Thanks for testing that, I am preparing the upload now. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386042: podracer: Fails with traceback as result
severity 386042 important tags 386042 + moreinfo thanks On Mon, Sep 04, 2006 at 10:45:58PM +0200, Kristian Wernersson wrote: > Package: podracer > Version: 1.4-1 > Severity: grave > Justification: renders package unusable (I think you meant "important". podracer works fine on direct HTTP downloads. The problem appears to be with a BitTorrent feed. It might even be "normal" if it's not all BitTorrent feeds.) > Everytime I run podracer iI get this output from it. > > Traceback (most recent call last): > File "", line 6, in ? > File "/usr/lib/python2.4/site-packages/BitTorrent/download.py", line 56, in > ? > from khashmir.utkhashmir import UTKhashmir > File "/usr/lib/python2.4/site-packages/khashmir/utkhashmir.py", line 11, in > ? > import khashmir, knode > File "/usr/lib/python2.4/site-packages/khashmir/khashmir.py", line 18, in ? > from BitTorrent.defaultargs import common_options, rare_options > File "/usr/lib/python2.4/site-packages/BitTorrent/defaultargs.py", line 30, > in ? > basic_options = [ > NameError: name '_' is not defined Can you please send your ~/.podracer/subscriptions ? Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#339271: library package needs to be renamed (libstdc++ allocator change)
On Tue, Nov 15, 2005 at 07:57:24AM +0100, Matthias Klose wrote: > Package: tqsllib > Severity: important > > Please do not take any action before reading > http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html > > This bug report is filed against the source package which builds > a library depending on libstdc++6 and defining or referencing > *mt_alloc* symbols. The package has to be rebuilt with either > g++-4.0_4.0.2-4 or g++-3.4_3.4.4-10 (or newer). Please rename the > library package to a name with a "c2a" suffix, and adjust the build > dependencies if dependencies on another renamed library do exist. [..] My package tqsllib is only used by my other package trustedqsl. Can I cheat and skip the library rename by simply setting better dependencies on the rebuilds? (Library conflicts app, library shlibs updated, app build-depends new library.) Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342337: xpdf: Security hole CAN-2005-3193
merge 342281 342337 thanks On Wed, Dec 07, 2005 at 10:30:15AM +0100, Jan Niehusmann wrote: > Package: xpdf-reader > Version: 3.00-13 > Severity: grave > Tags: security patch > Justification: user security hole > > CAN-2005-3193 lists a security hole of xpdf. A fix is available at > http://www.foolabs.com/xpdf/download.html (the patch seems to be > suitable for a security update - only overflow protection added, no new > features). It applies cleanly to the debian package. > > Reportbug just told me there is a new version in incoming. I guess it'll > fix the issue, but I decided to still post this report mainly for > reference. Thanks, but your report is identical to #342281. The fixed version is an update to 3.01, not 3.00. #342281 is already fixed in unstable. sarge and woody fixes are pending (as we need to create our own patch). Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342337: xpdf: Security hole CAN-2005-3193
On Wed, Dec 07, 2005 at 02:00:55PM +0100, Jan Niehusmann wrote: > On Wed, Dec 07, 2005 at 11:42:08PM +1100, Hamish Moffatt wrote: > > merge 342281 342337 > Oops - I'm sorry, I missed that report. That's ok, thanks for helping. > > The fixed version is an update to 3.01, not 3.00. > I know, but the patch applies to 3.00 without much trouble. Yes I have 3.00-13.1 ready to go now and will contact the security team about uploading it. > > #342281 is already fixed in unstable. sarge and woody fixes are pending > > (as we need to create our own patch). > > Ok, so you noticed that my analysis was not completely correct - while > the woody version indeed doesn't contain JPXStream.cc (and consequently, > the JPX stream reader bug doesn't exist in woody), the other security > holes (in Stream.cc) do exist in woody and need patching. I'll work on that next, but it won't be for a day or two due to time constraints. It looks like a bit more work that woody. You are welcome to work on it if you like. Regards Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328553: podracer: depends on gnu extensions in awk
On Fri, Sep 16, 2005 at 04:17:04AM +0200, Uli Martens wrote: > Package: podracer > Severity: serious > Tags: upstream patch > Justification: Policy 3.5 > > podracer uses the awk function 'gensub' which does not exist in mawk but > fails without any error message. Which podracer version? 1.3-1 uploaded this morning is meant to remove the dependence on gawk. Indeed, the code you changed is not present in 1.3-1. thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324579: patch
tags 324579 +patch thanks Here's a patch I used to fix this. tct now builds correctly. Hamish --- tct-1.11.orig/src/file/compress.c +++ tct-1.11/src/file/compress.c @@ -11,6 +11,7 @@ #include #include #include +#include #include "file.h" --- tct-1.11.orig/src/file/fsmagic.c +++ tct-1.11/src/file/fsmagic.c @@ -31,6 +31,7 @@ #include #include #include +#include #ifndefmajor /* if `major' not defined in types.h, */ #include /* try this one. */ #endif --- tct-1.11.orig/src/file/file.c +++ tct-1.11/src/file/file.c @@ -36,6 +36,7 @@ #include /* for MAXPATHLEN */ #include #include /* for open() */ +#include #if (__COHERENT__ >= 0x420) #include #else -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323097: www-sql: FTBFS: libpq-fe.h: No such file or directory
On Sun, Aug 14, 2005 at 07:44:15PM +0200, Andreas Jochens wrote: > Package: www-sql > Version: 0.5.7-18 > Severity: serious > > When building 'www-sql' on unstable, > I get the following error: > > make[1]: Entering directory `/www-sql-0.5.7' > gcc -O2 -g -Wall -I. -DHAVE_CONFIG_H -DSQL_USER=\"www-data\" -DSQL_PASS=\"\" > -I/usr/include/postgresql -c pgsql.c -o pgsql.o > pgsql.c:25:22: error: libpq-fe.h: No such file or directory It appears that libpq-dev has reverted this change. However I'll make www-sql use pg_config so it's immune from future changes. Thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317720: < 0.060 test dangerous?
Marco wrote: > > udev 0.062-4 still installs without a warning on my unstable box. > You could at least have taken the time to read the changelog entry > that closes this bug: "This will only affect upgrades from versions > earlier than 0.060." > The rationale is that if people already installed a >= 060 release > then there is no point in delaying the upgrade to this one. I don't understand. If it's still dangerous, why allow it? I installed 060 in early July, but I haven't rebooted. Now my system has installed 062 even though I'm running 2.6.8-11. Is my system hosed if I reboot? Is your logic that my system is hosed anyway, therefore upgrading does no additional harm? I think it would be better if the preinst still failed so as to bring this to my attention now rather than on the next reboot. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289310: this is important
severity 289310 serious thanks I hope you won't mind me fiddling with your bug priorities, but galeon-common can't be removed (for >= 17 days now) and that's got to be 'serious' rather than 'minor'. It's serious because it makes the package unsuitable for release. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292831: udev: udev prevents X from beeing started
On Mon, Jan 31, 2005 at 05:31:03AM +0100, Joey Hess wrote: > Marco d'Itri wrote: > > My package works as designed, but let me know if you can design > > something better. > > Oh, so it's udev that's responsible for what IIRC is a race that can > cause X to not see the ps/2 mouse if the module is loaded as part of X's > setup? Nice design. :-P > > FWIW, we have worked around this bug in d-i unstable for at least i386 > and amd64 by always putting psmouse in /etc/modules. I did an amd64 install last week from the (then) current install image and didn't end up with psmouse in /etc/modules; I added it by hand when I found that udev was preventing X from starting. :-( I am yet to submit a report; my bad. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293686: geda: uninstallable on unstable
On Sat, Feb 05, 2005 at 01:41:41PM +1300, Mark Robinson wrote: > Package: geda > Version: 20041228-1 > Severity: grave > Justification: renders package unusable Thanks for your bug report, but it's rather useless. libgeda22 is in incoming requiring NEW processing. Filing bug reports on geda won't change that. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293686: geda: uninstallable on unstable
On Fri, Feb 04, 2005 at 07:23:33PM -0800, Steve Langasek wrote: > reassign 293686 geda-gschem > retitle 293686 geda-gschem: uninstallable in unstable > tags 293686 sid > clone 293686 -1 > reassign -1 geda-gnetlist > retitle -1 geda-gnetlist: uninstallable in unstable > thanks > > This is not a bug in geda, it's a bug in the packages depended on. It's > also specific to the new version that's only in sid, so tagged as such. Actually, they're just waiting on libgeda22 to be processed in incoming, so it's not exactly a bug at all. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#308402: missing dependency
On Tue, May 10, 2005 at 03:17:22AM +0200, Frank Lichtenheld wrote: > Package: node > Severity: serious > > Installing the package in a clean chroot leads to the following error: > Setting up node (0.3.2-3) ... > /var/lib/dpkg/info/node.postinst: line 27: update-inetd: command not found > dpkg: error processing node (--configure): > subprocess post-installation script returned error exit status 127 > Errors were encountered while processing: > node > E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks. I just uploaded 0.3.2-4 to fix this. I'll email debian-release to request thawing. I think the chroot environment is a bit artificial though. In practice, when would netbase ever not be installed? It's in section base and it's priority: important. 149 packages rdepend on it. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#308489: geda: segfault in malloc()
On Tue, May 10, 2005 at 05:51:26PM +0300, Timo Juhani Lindfors wrote: > Package: geda > Version: 20050313-1 > Severity: grave > Justification: renders package unusable > Yup I can confirm this happens on i386. Oddly enough it seems to work perfectly on amd64. I'll forward your report. Thanks for all the details. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309486: libc6 upgrade failed leaving system unusable
Package: libc6 Version: 2.3.2.ds1-22 Severity: critical Justification: breaks the whole system I don't know whether this is a libc6 bug or a dpkg bug. During a routine update from unstable (of a few weeks ago) to current unstable, I started getting segfaults during a libc6 upgrade. After that, every command segfaulted, including init, meaning the system wouldn't boot. I used a rescue CD to unpack the .deb and replace the files in /lib. Then it worked. The disk wasn't full (6Gb available). Hamish Here's the upgrade log. Fetched 104MB in 3m42s (465kB/s) Preconfiguring packages ... (Reading database ... 43118 files and directories currently installed.) Preparing to replace libc6-dev 2.3.2.ds1-21 (using .../libc6-dev_2.3.2.ds1-22_i386.deb) ... Unpacking replacement libc6-dev ... Preparing to replace debconf-i18n 1.4.48 (using .../debconf-i18n_1.4.49_all.deb) ... Unpacking replacement debconf-i18n ... Preparing to replace debconf 1.4.48 (using .../debconf_1.4.49_all.deb) ... Unpacking replacement debconf ... Preparing to replace locales 2.3.2.ds1-21 (using .../locales_2.3.2.ds1-22_all.deb) ... Unpacking replacement locales ... Preparing to replace libc6 2.3.2.ds1-21 (using .../libc6_2.3.2.ds1-22_i386.deb) ... /var/lib/dpkg/tmp.ci/preinst: line 124: 11779 Segmentation fault expr $dir : "/lib.*" >/dev/null /var/lib/dpkg/tmp.ci/preinst: line 124: 11780 Segmentation fault expr $dir : "/emul/.*" >/dev/null /var/lib/dpkg/tmp.ci/preinst: line 124: 11785 Segmentation fault expr $dir : "/lib.*" >/dev/null /var/lib/dpkg/tmp.ci/preinst: line 124: 11786 Segmentation fault expr $dir : "/emul/.*" >/dev/null /usr/lib/dpkg/methods/apt/install: line 107: 11808 Segmentation fault $DPKG "$DPKG_OPTS" --configure -a installation script returned error exit status 100. Press to continue. installation script was terminated by a signal: Segmentation fault. Press to continue. installation script was terminated by a signal: Segmentation fault. Press to continue. tv:~# tv:~# tv:~# ls Illegal instruction tv:~# dmesg Segmentation fault tv:~# cat Segmentation fault -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libc6 depends on: ii libdb1-compat 2.1.3-7The Berkeley database routines [gl -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309486: libc6 upgrade failed leaving system unusable
On Tue, May 17, 2005 at 11:34:58AM -0400, Daniel Jacobowitz wrote: > On Wed, May 18, 2005 at 01:09:16AM +1000, Hamish Moffatt wrote: > > Package: libc6 > > Version: 2.3.2.ds1-22 > > Severity: critical > > Justification: breaks the whole system > > > > I don't know whether this is a libc6 bug or a dpkg bug. During > > a routine update from unstable (of a few weeks ago) to current > > unstable, I started getting segfaults during a libc6 upgrade. > > What kind of system is this? Am I reading you right to say that you > unpacked the same -22 debs and then things worked again? unstable on i386. Nothing unusual. I unpacked the same .deb manually, ran ldconfig and then everything worked. Then I chrooted into my install and installed the deb properly, which succeeded. > If you dare, could you try to reproduce the problem? I can try that, as the system isn't too critical. Installing the -22 deb now works. Should I install -21 and then -22 again? Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309486: libc6 upgrade failed leaving system unusable
On Wed, May 18, 2005 at 10:42:08AM +1000, Hamish Moffatt wrote: > On Tue, May 17, 2005 at 11:34:58AM -0400, Daniel Jacobowitz wrote: > > If you dare, could you try to reproduce the problem? > > I can try that, as the system isn't too critical. Installing the -22 deb > now works. Should I install -21 and then -22 again? That worked. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#475669: azureus: downloads never start with gij-4.3
On Sat, Apr 12, 2008 at 03:18:27PM -0700, Shaun Jackman wrote: > package azureus > severity 475669 serious > tag 475669 confirmed > merge 449176 475669 > thanks Sorry Shaun.. I missed that other bug report. I did check the BTS first but missed it :-( I had the Sun JVM as my preferred one but something switched it. Grr. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464275: [Pkg-electronics-devel] Bug#464275: Patch (debdiff)
On Sat, Feb 09, 2008 at 05:36:52PM +, Peter Clifton wrote: > http://launchpadlibrarian.net/11848710/geda-xgsch2pcb.debdiff Thanks, uploaded. By the way, lintian reports that the build-dependency on debhelper should insist on at least 5.0.51 to get dh_icons, not just 5. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465518: FTBFS - clean target broken
On Tue, Feb 12, 2008 at 11:51:05PM +0200, Riku Voipio wrote: > Package: hamfax > Version: 0.6.4-4 > Severity: serious > > from the build logs: > > -snip- > # Add here commands to clean up after the build process. > [ ! -f Makefile ] || /usr/bin/make clean > make[1]: Entering directory `/build/buildd/hamfax-0.6.4' > /bin/sh ./config.status --recheck > /bin/sh: ./config.status: No such file or directory > make[1]: *** [config.status] Error 127 > make[1]: Leaving directory `/build/buildd/hamfax-0.6.4' > make: *** [clean] Error 2 > -snip- Argh. A stale Makefile was left in the .diff.gz (my fault) which is causing this. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465400: [Pkg-electronics-devel] Bug#465400: FTBFS: missing build-dependency on desktop-file-utils
fixed 456400 1.4.0-2 thanks On Tue, Feb 12, 2008 at 06:42:03PM +1100, William Grant wrote: > Package: geda-gattrib > Version: 1.4.0-1 > Severity: serious > Justification: no longer builds from source > > geda-gattrib's configure script wants to find update-desktop-database, > which is in desktop-file-utils. That is not build-depended upon, so the > build fails. Thanks, fixed in 1.4.0-2. Unfortunately I can't easily pbuilder geda-* until libgeda* is in the archive.. I should work out how to set up a local repository that pbuilder could use to fetch that dependency from. I pbuilder everything else to catch failures like this. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#466484: unresolved file conflict with extra-xdg-menus
On Tue, Feb 19, 2008 at 02:57:57PM +1100, Drew Parsons wrote: > Package: hamradiomenus > Version: 1.1 > Severity: serious > > Although hamradiomenus Depends: extra-xdg-menus (>= 1.0-2), there is > nevertheless a file conflict which prevents upgrading. > > extra-xdg-menus cannot upgrade to 1.0-2 because hamradiomenus already > has /etc/xdg/menus/applications-merged/hamradio.menu, and therefore > hamradiomenus is broken since it depends of extra-xdg-menus (>= 1.0-2). Hmm. I'm confused; extra-xdg-menus conflicts and replaces the old version of hamradiomenus, so I expected this would work. Obvious I need to study the relevant documentation some more. thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6
Package: openoffice.org-writer2latex
Version: 0.5-6
Followup-For: Bug #468202
Installation of openoffice.org-writer2latex is failing for me.
[10:20AM] [EMAIL PROTECTED]:oboe/apps/callexec $ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
icedove icedove-gnome-support linuxprinting.org-ppds
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up openoffice.org-writer2latex (0.5-6) ...
Adding extension
/usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
unopkg failed.
dpkg: error processing openoffice.org-writer2latex (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
openoffice.org-writer2latex
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- Package-specific info:
Identifier: org.openoffice.legacy.writer2latex.uno.pkg
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg
is registered: yes
Media-Type: application/vnd.sun.star.package-bundle
Description: Extension
bundled Packages: {
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/writer2latex.jar
is registered: yes
Media-Type: application/vnd.sun.star.uno-component;type=Java
Description: UNO Java Component
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_types.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description: Configuration Data
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_filters.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description: Configuration Data
}
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages openoffice.org-writer2latex depends on:
ii openoffice.org-core1:2.4.0~rc1-3 OpenOffice.org office suite archit
ii openoffice.org-java-common 1:2.4.0~rc1-3 OpenOffice.org office suite Java s
openoffice.org-writer2latex recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6
On Fri, Feb 29, 2008 at 03:24:19AM +0100, Rene Engelhard wrote:
> And you unregistered the extension manually to have a clean state if it
> failed before? Read the buglog...
How?
[ 5:09PM] [EMAIL PROTECTED] $ sudo /usr/lib/openoffice/program/unopkg list
--shared
all deployed shared packages:
Identifier: org.openoffice.legacy.writer2latex.uno.pkg
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg
is registered: yes
Media-Type: application/vnd.sun.star.package-bundle
Description: Extension
bundled Packages: {
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/writer2latex.jar
is registered: yes
Media-Type: application/vnd.sun.star.uno-component;type=Java
Description: UNO Java Component
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_types.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description: Configuration Data
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_filters.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description: Configuration Data
}
[ 5:10PM] [EMAIL PROTECTED]: $ sudo /usr/lib/openoffice/program/unopkg remove
org.openoffice.legacy.writer2latex.uno.pkg
ERROR: There is no such extension deployed:
org.openoffice.legacy.writer2latex.uno.pkg
unopkg failed.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6
On Fri, Feb 29, 2008 at 03:24:19AM +0100, Rene Engelhard wrote: > Hi, > > Hamish Moffatt wrote: > > [10:20AM] [EMAIL PROTECTED]:oboe/apps/callexec $ sudo apt-get dist-upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > The following packages have been kept back: > > icedove icedove-gnome-support linuxprinting.org-ppds > > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. > > 1 not fully installed or removed. > > After this operation, 0B of additional disk space will be used. > > Do you want to continue [Y/n]? > > Setting up openoffice.org-writer2latex (0.5-6) ... > > Adding extension > > /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg... > > unopkg failed. > > dpkg: error processing openoffice.org-writer2latex (--configure): > > subprocess post-installation script returned error exit status 1 > > Errors were encountered while processing: > > openoffice.org-writer2latex > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > And you unregistered the extension manually to have a clean state if it > failed before? Read the buglog... OK, I removed it (forgot the --shared in the last attempt), and now the package configures. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6
On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote: > Hamish Moffatt wrote: > > > And you unregistered the extension manually to have a clean state if it > > > failed before? Read the buglog... > > > > OK, I removed it (forgot the --shared in the last attempt), and now the > > package configures. > > Thanks, so I close this again. Well, it isn't satisfactory that manual intervention is required for anyone who installed 0.5-5. You said the problem is on the old postinst. Therefore, you can fix it in the new preinst. Either prepare for it, or remove the script, or whatever. See the policy manual section: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6
On Fri, Feb 29, 2008 at 12:24:36PM +0100, Rene Engelhard wrote: > Hamish Moffatt wrote: > > On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote: > > > Hamish Moffatt wrote: > > > > > And you unregistered the extension manually to have a clean state if > > > > > it > > > > > failed before? Read the buglog... > > > > > > > > OK, I removed it (forgot the --shared in the last attempt), and now the > > > > package configures. > > > > > > Thanks, so I close this again. > > > > Well, it isn't satisfactory that manual intervention is required for > > anyone who installed 0.5-5. > > > > You said the problem is on the old postinst. Therefore, you can fix it > > No, I didn't. Read again. I changed the *prerm*. Sorry, my fault. > > http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html > > Will have a look again, though. Thanks. The manual says that if the old prerm fails, dpkg should try the same operation with the new prerm, which you said is fixed. I didn't see it try to do this. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6
On Fri, Feb 29, 2008 at 08:00:58PM +0100, Rene Engelhard wrote: > Hi, > > Hamish Moffatt wrote: > > Thanks. The manual says that if the old prerm fails, dpkg should try the > > same operation with the new prerm, which you said is fixed. I didn't see > > it try to do this. > > The problem here might be that the prerm didn't actually fail in > the sense that it returned an exitcode != 0... But it failed to do its > job. > > unopkg often returns 0 even if it failed.. So, the new postinst fails because the old prerm failed to do its work (although it returned success)? In that case can't you simply deal with this in the new postinst? Thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#466484: about unresolved file conflict with extra-xdg-menus
reopen 466484 thanks On Thu, Mar 13, 2008 at 09:58:57AM +1100, Drew Parsons wrote: > > On Wed, 2008-03-12 at 20:25 +0100, Joop Stakenborg wrote: > > Hello List, Drew and Hamish, > > > > This bug seems to have gone here. Can you guys please check so we might > > close it? > > > > Thanks, > > Joop PG4I > > You're right, Joop, it's installing OK now: > > $ dpkg -l hamradiomenus extra-xdg-menus > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name VersionDescription > +++-==-==- > ii extra-xdg-menu 1.0-2 Extra menu categories for applications > under > ii hamradiomenus 1.1hamradio menus for GNOME and KDE > > > Must have been some ghost in the shell. No, upgrading from 1.0-3 still fails: [10:22AM] [EMAIL PROTECTED]:packages/ham/menu $ sudo dpkg -i hamradiomenus_1.0-3_all.deb Selecting previously deselected package hamradiomenus. (Reading database ... 171311 files and directories currently installed.) Unpacking hamradiomenus (from hamradiomenus_1.0-3_all.deb) ... Setting up hamradiomenus (1.0-3) ... [10:22AM] [EMAIL PROTECTED]:packages/ham/menu $ sudo apt-get install hamradiomenus Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: extra-xdg-menus The following NEW packages will be installed: extra-xdg-menus The following packages will be upgraded: hamradiomenus 1 upgraded, 1 newly installed, 0 to remove and 5 not upgraded. Need to get 0B/15.1kB of archives. After this operation, 147kB of additional disk space will be used. Do you want to continue [Y/n]? (Reading database ... 171318 files and directories currently installed.) Preparing to replace hamradiomenus 1.0-3 (using .../hamradiomenus_1.1_all.deb) ... Unpacking replacement hamradiomenus ... Unpacking extra-xdg-menus (from .../extra-xdg-menus_1.0-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/extra-xdg-menus_1.0-2_all.deb (--unpack): trying to overwrite `/etc/xdg/menus/applications-merged/hamradio.menu', which is also in package hamradiomenus Errors were encountered while processing: /var/cache/apt/archives/extra-xdg-menus_1.0-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I meant to fix this but haven't yet (not sure of the best approach yet). Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#458434: digikam: Me too
Package: digikam Version: 2:0.9.2-5+b1 Followup-For: Bug #458434 I'm seeing the red tint with my TIFF images too. thanks, Hamish -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-rc6 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages digikam depends on: ii kdebase-kio-plugins 4:3.5.8.dfsg.1-5 core I/O slaves for KDE ii kdelibs4c2a 4:3.5.8.dfsg.1-5 core libraries and binaries for al ii libacl1 2.2.45-1 Access control list shared library ii libart-2.0-22.3.19-3 Library of functions for 2D graphi ii libattr11:2.4.39-1 Extended attribute shared library ii libaudio2 1.9.1-1 Network Audio System - shared libr ii libc6 2.7-5GNU C Library: Shared libraries ii libexif12 0.6.16-2.1 library to parse EXIF files ii libexiv2-0 0.15-2 EXIF/IPTC metadata manipulation li ii libfam0 2.7.0-13 Client library to control the FAM ii libfontconfig1 2.5.0-2 generic font configuration library ii libfreetype62.3.5-1+b1 FreeType 2 font engine, shared lib ii libgcc1 1:4.2.2-5GCC support library ii libgphoto2-22.4.0-8 gphoto2 digital camera library ii libgphoto2-2-dev2.4.0-8 gphoto2 digital camera library (de ii libgphoto2-port02.4.0-8 gphoto2 digital camera port librar ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii libidn111.1-1GNU libidn library, implementation ii libjasper1 1.900.1-3The JasPer JPEG-2000 runtime libra ii libjpeg62 6b-14The Independent JPEG Group's JPEG ii libkdcraw2 0.1.3-1 Raw picture decoding C++ library ( ii libkexiv2-3 0.1.6-1 Qt like interface for the libexiv2 ii libkipi00.1.5-2 library for apps that want to use ii liblcms11.16-7 Color management library ii libltdl31.5.24-2 A system independent dlopen wrappe ii libpcre37.3-2Perl 5 Compatible Regular Expressi ii libpng12-0 1.2.15~beta5-3 PNG library - runtime ii libqt3-mt 3:3.3.7-9Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libsqlite3-03.4.2-2 SQLite 3 shared library ii libstdc++6 4.2.2-5 The GNU Standard C++ Library v3 ii libtiff43.8.2-7 Tag Image File Format (TIFF) libra ii libx11-62:1.0.3-7X11 client-side library ii libxcursor1 1:1.1.9-1X cursor management library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxi6 2:1.1.3-1X11 Input extension library ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxrandr2 2:1.2.2-1X11 RandR extension library ii libxrender1 1:0.9.4-1X Rendering Extension client libra ii libxt6 1:1.0.5-3X11 toolkit intrinsics library ii zlib1g 1:1.2.3.3.dfsg-8 compression library - runtime Versions of packages digikam recommends: ii kdeprint4:3.5.8.dfsg.1-5 print system for KDE ii kipi-plugins0.1.4-1+b3 image manipulation/handling plugin ii konqueror 4:3.5.8.dfsg.1-5 KDE's advanced file manager, web b -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459031: fldigi: FTBFS: /usr/include/c++/4.2/bits/locale_facets.tcc:118: error: 'dynamic_cast' not permitted with -fno-rtti
On Fri, Jan 04, 2008 at 10:29:57AM +0100, Lucas Nussbaum wrote: > Package: fldigi > version: 2.05-3 > Severity: serious > User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20080103 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on i386. Could you please try on 2.07-1, uploaded last night? I built using up to date unstable on amd64 without issue. thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459031: fldigi: FTBFS: /usr/include/c++/4.2/bits/locale_facets.tcc:118: error: 'dynamic_cast' not permitted with -fno-rtti
On Fri, Jan 04, 2008 at 02:30:25PM +, Stelios Bounanos wrote: > tags 459031 + patch > thanks > > The FTBFS happens with g++-4.2 4.2.2-5 but not 4.2.2-4. I have tracked down > the > error to a change made to /usr/include/c++/4.2/bits/locale_facets.tcc and just > filed a bug report for libstdc++6-4.2-dev. > > The -fno-rtti switch will be removed in fldigi-2.08 for unrelated reasons. You > could also remove it in 2.07 and solve the problem that way. Thanks Stelios, I've uploaded a fixed fldigi package with your suggested change. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459570: upgrading to findutils/locate loses updatedb configuration!
Package: locate Version: 4.2.31-4 Severity: serious Justification: Configuration changes lost It looks like the new locate package reads /etc/updatedb.findutils.cron.local as its configuration file now. Configuration changes made to /etc/updatedb.conf are lost with this package split, which is a serious bug. It looks like the format of the files is compatible so it could be renamed by the scripts instead. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages locate depends on: ii findutils 4.2.31-4 utilities for finding files--find, ii libc6 2.7-5 GNU C Library: Shared libraries locate recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#446346: exim4-config: incorrect condition in new configuration files causing bounced email
Package: exim4-config
Version: 4.68-1
Severity: grave
Justification: causes non-serious data loss
After upgrading exim4-config to 4.68-1 this morning I'm getting a lot of
messages bounced, with the following in the paniclog:
2007-10-12 20:59:41 1IgIEv-0005de-Ep failed to expand condition "${if
${match_ip{$sender_host_address}{:@[]}}{1}{0}}" for real_local router:
condition name expected, but found "${match_ip{$send"
This comes from the new conf.d/router/300_exim4-config_real_local:
COND_LOCAL_SUBMITTER = "\
${if {match_ip{$sender_host_address}{:@[]}}\
{1}{0}\
}"
I don't know in what way this is wrong but I've disabled the condition
for now.
I have "deliver real-hamish" at the end of my .forward which is
triggering this. I guess nobody else does this as nobody has reported it
until now.
Thanks
Hamish
-- Package-specific info:
Exim version 4.68 #1 built 07-Oct-2007 21:06:42
Copyright (c) University of Cambridge 2006
Berkeley DB: Berkeley DB 4.6.19: (August 10, 2007)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch
nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
dc_eximconfig_configtype='smarthost'
dc_other_hostnames='cloud.net.au'
dc_local_interfaces=''
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets='192.168.42.0/24'
dc_smarthost='mail.risingsoftware.com'
CFILEMODE='644'
dc_use_split_config='true'
dc_hide_mailname='false'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:cloud.net.au
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages exim4-config depends on:
ii adduser 3.105 add and remove users and groups
ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy
exim4-config recommends no packages.
-- debconf information:
* exim4/dc_smarthost: mail.risingsoftware.com
exim4/dc_relay_domains:
exim4/dc_localdelivery: mbox format in /var/mail/
exim4/exim3_upgrade: true
* exim4/dc_eximconfig_configtype: mail sent by smarthost; received via SMTP or
fetchmail
exim4/dc_readhost:
exim4/exim4-config-title:
exim4/dc_noalias_regenerate: false
* exim4/dc_relay_nets: 192.168.42.0/24
* exim4/mailname: cloud.net.au
* exim4/dc_local_interfaces:
* exim4/dc_minimaldns: false
* exim4/dc_other_hostnames: cloud.net.au
* exim4/no_config: true
* exim4/hide_mailname: false
* exim4/dc_postmaster: hamish
* exim4/use_split_config: true
exim4/internal/exim4-config.reconfigure: false
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444509: Bug#444514: marked as done (gpredict: FTBFS: error: 'GtkTooltips' undeclared)
On Sat, Oct 13, 2007 at 08:52:39PM +, Debian Bug Tracking System wrote:
> Changes:
> grig (0.7.2-1.1) unstable; urgency=low
> .
>* Non-maintainer upload.
>* Remove “-DGTK_DISABLE_DEPRECATED” from src/Makefile.{am,in} to avoid
> FTBFS
> due to the transition to Gtk 2.12 (Closes: #444514).
>* Move the menu section from “Apps/Hamradio” to “Applications/Amateur
> Radio”
> as part of the menu transition.
>* No longer ignore “make distclean” errors, per lintian.
>* Improve the copyright by adding the GPLv2 blurb, add a link to the exact
> location of the license, and add copyright years.
>* Also modify Makefile.{am,in} not to ship COPYING.
>* Add a “Homepage” field in the control file.
Thanks for your NMU Cyril. However I think the above is excessive for a
simple FTBFS NMU for an otherwise maintained package.
For example the Makefile.{am,in} COPYING change: this is purely
cosmetic. I disagree that your solution is the best; maintaining patches
to upstream sources is a nuisance, while fixing things up afterwards in
debian/rules is easier.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447819: shlibs file incorrect: does not force dependency on libportaudiocpp0
Package: libportaudiocpp0
Version: 19+svn20070125-1
Severity: serious
The shlibs file for libportaudiocpp0 only results in a dependency on
libportaudio2, not libportaudiocpp0:
libportaudiocpp 0 libportaudio2 (>= 19+cvs20060311-1)
This results in programs that use it with automatic depends via
${shlib:Depends} having incorrect dependencies, eg bug#447548 in fldigi.
Thanks
Hamish
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libportaudiocpp0 depends on:
ii libc6 2.6.1-5 GNU C Library: Shared libraries
ii libgcc1 1:4.2.2-3GCC support library
ii libportaudio2 19+svn20070125-1 Portable audio I/O - shared librar
ii libstdc++6 4.2.2-3 The GNU Standard C++ Library v3
libportaudiocpp0 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447819: shlibs file incorrect: does not force dependency on libportaudiocpp0
On Wed, Oct 24, 2007 at 07:27:46AM +0100, Mark Purcell wrote:
> On Tue, 23 Oct 2007, Hamish Moffatt wrote:
> > The shlibs file for libportaudiocpp0 only results in a dependency on
> > libportaudio2, not libportaudiocpp0:
> >
> > libportaudiocpp 0 libportaudio2 (>= 19+cvs20060311-1)
> >
> > This results in programs that use it with automatic depends via
> > ${shlib:Depends} having incorrect dependencies, eg bug#447548 in fldigi.
>
> Thanks Hamish,
>
> Unfortunately this problem also appears with the upload we did yesterday:
>
> portaudio19 (19+svn20071022-1) unstable; urgency=low
>
> [ Mark Purcell ]
> * New upstream release
> - libportaudio2: new snapshot (Closes: #447338)
>
> [ Kilian Krause ]
> * Use ${binary:Version} for binNMU-safe uploads.
> Add dpkg-dev (>= 1.13.19) to Build-Depends
> * Don't ignore make clean errors.
> * Fix dh_makeshlibs call. Get rid of libportaudiocpp0 binary:
> shlibs-declares-dependency-on-other-package libportaudio2.
> * Add Homepage field as added in dpkg-dev 1.14.6.
>
> -- Mark Purcell <[EMAIL PROTECTED]> Tue, 23 Oct 2007 07:13:43 +0100
>
> I will have a look tonight and see if we can't get the shlibs
> tonight, I'm happy if you would also like to reassign bug#447548 to
> portaudio.
I kept #447548 assigned to fldigi and opened a new bug (this one)
instead, as a reminder that we need to rebuild fldigi once portaudio19
is fixed.
Thanks,
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#448617: xinetd: diverts inetd but does not read its configuration file!!!
Package: xinetd Version: 1:2.3.14-1.1 Severity: grave Justification: causes non-serious data loss xinetd diverts inetd (as provided by openbsd-inetd or netkit-inetd), but the default configuration does not read its configuration file (-inetd_compat switch). Thus any services in /etc/inetd.conf are just disabled without warning. Hamish -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xinetd depends on: ii libc6 2.6.1-6GNU C Library: Shared libraries ii libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra ii netbase 4.30 Basic TCP/IP networking system Versions of packages xinetd recommends: ii logrotate 3.7.1-3Log rotation utility ii sysklogd [system-log-daemon] 1.5-1 System Logging Daemon -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490123: dnsmasq: appears to be vulnerable to cache poisoning attack CVE-2008-1447
Package: dnsmasq Version: 2.42-4 Severity: grave Tags: security Justification: user security hole dnsmasq appears to be vulnerable to CVE-2008-1447, the DNS cache poisoning exploit. From my reading of the source code and observation with tcpdump, dnsmasq doesn't do any source port randomisation. dnsmasq binds a UDP socket for each of the forwarding name servers when they are added (on startup, or configuration change), then uses those sockets forever. The source port doesn't change between queries. tcpdump confirms this. thanks Hamish -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dnsmasq depends on: ii adduser 3.108 add and remove users and groups ii dnsmasq-base 2.42-4 A small caching DNS proxy and DHCP ii netbase 4.32 Basic TCP/IP networking system dnsmasq recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490123: additional note re: dnsmasq vulnerability
This is noted at: http://www.kb.cert.org/vuls/id/AAMN-7GDV56 And I note that Simon has announced a release candidate with a solution at: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2008q3/002148.html Apologies Simon, I didn't realise that you were also upstream and obviously well aware of this issue already. thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#466484: about unresolved file conflict with extra-xdg-menus
On Thu, Mar 13, 2008 at 04:33:07PM +0100, Joop Stakenborg wrote: > > Op donderdag 13-03-2008 om 10:24 uur [tijdzone +1100], schreef Hamish > Moffatt: > > > No, upgrading from 1.0-3 still fails: > > Ouch, of course... the bug appears when _upgrading_. Thanks for pointing > that out. Fixed in extra-xdg-menus 1.0-3. You also need hamradiomenus 1.2, else purging hamradiomenus takes part of extra-xdg-menus with it! Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400252: libgeda: links against libgd instead of against libgdgeda
On Fri, Nov 24, 2006 at 07:46:41PM +0100, Joost Yervante Damad wrote: > Package: libgeda > Version: 20061020-1 > Severity: important > > > This package is supposed to be linked against libgdgeda, however instead > it is linked against libgd. Actually upstream has changed to use libgd and not the special libgdgeda any more. I will fix the build-deps and upload. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400307: libgeda: broken shlibs will cause broken deps for any third-party packages
Hi Steve, On Fri, Nov 24, 2006 at 09:47:18PM -0800, Steve Langasek wrote: > So looking at libgeda for bug #400252 brings another RC bug to my attention: > you have not been changing your library package name in keeping with the > soname changes of this library, and the shlibs provided by libgeda reference > this same, unchanging package name, which means any packages built against > an older version of the package will be installable but broken when a new > soname of the lib is available. > > Evidently you've worked around this in all the in-archive packages that > depend on libgeda by adding versioned conflicts each time a new version of > libgeda comes out, which explains some of the other release-critical bugs > I've seen in the past. This is technically sound for those packages in > Debian, albeit high-maintenance and aesthetically displeasing; but shlibs > files must contain sufficient information that *others* get correct > dependencies when linking against your library as well, which is currently > not the case. Yes you are quite right. libgeda conflicts with old versions of the binaries and the binaries depend on a sufficient version of the library, the end result being a tight coupling between the versions. This works as long as all of the applications are released together, which currently they are. Upstream originally released just one tarball, but now release individual tarballs for each application - but as a matching set, like the Debian binary packages. > In addition, since there are no file overlaps between subsequent versions of > libgeda, this breaks co-installability of packages built against different > versions of libgeda for no apparent reason. If there *were* file conflicts > between the different versions, I would say that your use of Provides: is a > perfectly reasonable technical solution and that the only thing in need of > fixing is the shlibs file, but as it stands I think this is a gratuitous > deviation from Debian library best practices. Please fix libgeda so that > the library package name matches the soname, and update the shlibs to match. > Although this does mean new upstream versions of libgeda will have to go > through the NEW queue, it also should require much less packaging work on > the whole when updating... This was a working for slow NEW processing, and also for the perception that repeated NEW processing was a bit of a nuisance in this case because the packages are always a matched set. This is definitely a case where it would be nice if NEW processing only applied for new sources, not just new binaries. I do agree that it's a horrid violation of policy though. > The library package name is not a release-critical issue, BTW, so if you > insist on keeping this package name, geda won't be kicked from the release > because of it. But the shlibs do need to be fixed. The shlibs for libgeda20 20061020 says libgeda 27 libgeda20 (>= 20061020) I think this is correct - it means a sufficient version of libgeda20 is used in the Dependences of geda-gattrib et al. In itself it doesn't prevent a later incompatible version of libgeda meeting the dependency, but the new libgeda will Conflict with old applications. The only improvement I see would be to specify (>= 20061020) && (< 20061021~0) or similar in the shlibs file. Then libgeda's would no longer need to conflict with old versions (though the existing conflicts would need to stay). Is this your recommendation? I have libgeda providing virtual package libgeda-27, but unfortunately dpkg has a bug where it doesn't prevent libgeda20 being upgraded if it no longer provides virtual packages required by other installed packages. Else I could just use libgeda-NN in the shlibs file. Thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#427265: aprsd: diff for NMU version 1:2.2.5-13-3.2
Thanks for the NMU Julien. Hamish On Fri, Jul 20, 2007 at 03:26:46PM +0200, Julien Cristau wrote: > tags 427265 + patch > thanks > > Hi, > > Attached is the diff for my aprsd 1:2.2.5-13-3.2 NMU. -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435462: add upstream patch
Hi Steffen,
Upstream has released 3.02pl1 to address this.
However please upload your 3.02-1.1 version for now. I am very busy and
don't have time to work on the package for at least a few more days.
Thanks for your offer.
Hamish
On Sun, Aug 05, 2007 at 08:54:44PM +1000, Steffen Joeris wrote:
> Hi Hamish
>
> I attached a patch to fix this problem. In case you are busy, can I upload
> the
> NMU patch?
>
> Cheers
> Steffen
> diff -u xpdf-3.02/debian/changelog xpdf-3.02/debian/changelog
> --- xpdf-3.02/debian/changelog
> +++ xpdf-3.02/debian/changelog
> @@ -1,3 +1,12 @@
> +xpdf (3.02-1.1) unstable; urgency=high
> +
> + * Non-maintainer upload
> + * Fix integer overflow in the StreamPredictor::StreamPredictor
> +function by adding post-3.5.7-kdegraphics-CVE-2007-3387.diff.dpatch
> +(Closes: #435462) Fixes: CVE-2007-3387
> +
> + -- Steffen Joeris <[EMAIL PROTECTED]> Sun, 05 Aug 2007 10:03:53 +
> +
> xpdf (3.02-1) unstable; urgency=low
>
>* New upstream release (closes: #413611)
> diff -u xpdf-3.02/debian/patches/00list xpdf-3.02/debian/patches/00list
> --- xpdf-3.02/debian/patches/00list
> +++ xpdf-3.02/debian/patches/00list
> @@ -18,0 +19,3 @@
> +
> +# Fix CVE-2007-3387
> +post-3.5.7-kdegraphics-CVE-2007-3387.diff.dpatch
> only in patch2:
> unchanged:
> ---
> xpdf-3.02.orig/debian/patches/post-3.5.7-kdegraphics-CVE-2007-3387.diff.dpatch
> +++ xpdf-3.02/debian/patches/post-3.5.7-kdegraphics-CVE-2007-3387.diff.dpatch
> @@ -0,0 +1,25 @@
> +#! /bin/sh /usr/share/dpatch/dpatch-run
> +## post-3.5.7-kdegraphics-CVE-2007-3387.diff.dpatch
> +##
> +## All lines beginning with `## DP:' are a description of the patch.
> +## DP: Fix integer overflow in the StreamPredictor::StreamPredictor
> +## function
> +
> [EMAIL PROTECTED]@
> +Index: kpdf/xpdf/xpdf/Stream.cc
> +===
> +--- kpdf/xpdf/xpdf/Stream.cc (revision 689574)
> xpdf-3.02/xpdf/Stream.cc (working copy)
> +@@ -411,9 +411,9 @@ StreamPredictor::StreamPredictor(Stream
> +
> + nVals = width * nComps;
> + if (width <= 0 || nComps <= 0 || nBits <= 0 ||
> +- nComps >= INT_MAX / nBits ||
> +- width >= INT_MAX / nComps / nBits ||
> +- nVals * nBits + 7 < 0) {
> ++ nComps > gfxColorMaxComps || nBits > 16 ||
> ++ width >= INT_MAX / nComps ||
> ++ nVals >= (INT_MAX - 7) / nBits) {
> + return;
> + }
> + pixBytes = (nComps * nBits + 7) >> 3;
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389522: Some of your Debian packages might need attention
On Fri, Jun 22, 2007 at 04:47:50AM -0600, DDPOMail robot wrote: > Dear Debian Hamradio Maintainers, > > The following possible problem(s) were detected in the package(s) > you maintain in Debian: > > wsjt: > This package has 1 RC bug(s) more than 30 days old: >- #389522 Thanks. The bug is an FTBFS. I'm confused about this. It's fixed in 5.9.6.r309-2, which is the second most recent version in unstable. The BTS graph shows it not fixed in 5.9.7.r383-1, which is the latest. I don't know why. There don't seem to be any reports of it being found in that version, and the buildd web site doesn't show any build failures. It appears that the changelog for 5.9.7* is missing the changelog entry for 5.9.6.r309-2 (oops) so the bts thinks it is a separate branch. Can anyone confirm? thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420442: file conflicts between packages
On Sun, Apr 22, 2007 at 12:48:06PM +0200, Michael Ablassmeier wrote: > Package: vertex, gtkwave > Severity: serious > Usertags: qa-file-conflict > Justification: Policy violation, see section 7.2 > > hi, > > both vertex and gtwave ship `/usr/bin/vertex' but do neither conflict or > add a diversion, thus fail to be installed on the same environment: > > dpkg: error processing /var/cache/apt/archives/vertex_0.1.15-1.2_i386.deb > (--unpack): > trying to overwrite `/usr/bin/vertex', which is also in package gtkwave > dpkg-deb: subprocess paste killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/vertex_0.1.15-1.2_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks, that's bug #420346 already. Please check the bts before filing new reports. I guess as gtkwave has just introduced this binary, it needs to be the one to change. OTOH vertex is less popular according to popcon, and hasn't had a maintainer upload in 2 years. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419618: /usr/bin/pdftops: pdftops segfault, additional file
On Tue, Apr 17, 2007 at 10:58:05AM +0100, Stephen Gran wrote: > This one time, at band camp, Andreas Bombe said: > > The file I encountered the bug on is available at > > http://www.kba.de/Stabsstelle/ZentraleRegister/VZR/FormularVZRneu1.pdf > > > > Most other PDFs I tried seem to work, a few also crash pdftops. > > It seems that you're right about pdftops. However, it is also the case > that the pdf viewers still exit, implying that they're not handling the > failure of pdftops very well, or that they have their own crash issues > as well. Trying to get a stack trace from kpdf gave me over 3000 > frames, for instance :/ I can't reproduce this any more with libc6 2.5-4. I'm going to upload xpdf 3.02 soon anyway which also seemed to fix it with libc6 2.5-1. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389522: Unreproducible on amd64
On Sat, Oct 07, 2006 at 11:23:40PM +0200, Jérémy Bobbio wrote: > I can't reproduce this FTBFS on amd64. Neither can I - but since I built the uploaded binary package on amd64 that's not surprising. :) > Is this bug specific to s390? According to http://buildd.debian.org/build.php?arch=&pkg=wsjt it happens on sparc, powerpc, hppa, m68k, mips and mipsel also. ie only i386, arm, ia64 and amd64 build ok. The fix is simple and I will upload very soon. thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388695: Why reopen these bugs?
On Sat, Oct 14, 2006 at 02:56:26PM +0100, Steve McIntyre wrote: > Hey Steinar, > > I'm curious why you re-opened #388695. It all *seems* fixed, and there's > no comment from you to explain why it should be re-opened... Hi Steve, It's working now (matching versions are in testing) but a fix is needed to ensure that mismatched versions can't be installed, ie tighter dependencies. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392968: /dvb
On Sat, Oct 14, 2006 at 11:18:30PM -0400, Joey Hess wrote:
> Are you sure you don't have a /dvb directory? The code is as follows:
> if [ -e /dvb ] ; then
> echo -n "Incorrect directory /dvb found; attempting to delete it ..."
> find /dvb -type c -exec rm {} \;
> find /dvb -type d -exec rmdir {} 2> /dev/null \;
>
> rmdir /dvb 2> /dev/null
>
>
> I guess that running sh -x /var/lib/dpkg/info/dvbtune.postinst will show what
> the problem is with this. Only bug I see in the above is that it fails
> if /dvb exists as a file, not a directory.
I didn't have one at the time of reporting the bug; I had run the
postinst a few times by then and a previous iteration may have removed
it (but then it shouldn't keep failing).
Interestingly, I was running the upgrade from sudo ("sudo apt-get
dselect-upgrade"); later I had occasion to be switched to root with su
and the postinst ran ok. I don't know whether that's connected. Odd.
thanks
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388695: Why reopen these bugs?
On Sun, Oct 15, 2006 at 09:12:04AM +0100, Steve McIntyre wrote: > On Sat, Oct 14, 2006 at 04:38:39PM -0700, Steve Langasek wrote: > >If this bug allows a user of sarge to install individual packages from etch > >in an inconsistent an unusable configuration, then it is RC. > > Yup, I was wrong. Sorry for any hassle caused... Fixed now anyway (geda-symbols 20060906-2). Thanks for the input guys. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#393480: xastir: FTBFS: Package libgdal1-1.3.1-dev has no installation candidate
On Mon, Oct 16, 2006 at 04:50:09PM +0200, Andreas Jochens wrote: > When building 'xastir' on unstable, I get the following error: > > E: Package libgdal1-1.3.1-dev has no installation candidate > E: Failed to process build dependencies > With the attached patch 'xastir' can be built on unstable. > The patch changes the Build-Depends from libgdal1-1.3.1-dev to > libgdal1-1.3.2-dev. > +Build-Depends: debhelper (>= 4), libax25-dev, lesstif2-dev, libxext-dev | > xlibs-dev, libxp-dev | xlibs-dev, libxt-dev | xlibs-dev, festival-dev > [!hppa], festival [!hppa], libmagick9-dev (>= 6:6.2.4.5-0.2) | libmagick-dev, > libshp-dev, gpsman, gpsmanshp, proj, libpcre3-dev, libcurl3-gnutls-dev | > libcurl-ssl-dev, libgdal1-1.3.2-dev | libgdal-dev This should be unnecessary as libgdal-dev is an alternative and libgdal1-1.3.2-dev provides it. "apt-get build-dep .." seems to be broken in this regard. It looks like it will do the right thing, then aborts: [8:25am] [EMAIL PROTECTED]:~> sudo apt-get build-dep xastir Reading package lists... Done Building dependency tree... Done Package libgdal1-1.3.1-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libgdal1-1.3.2-dev Note, selecting libgdal1-1.3.2-dev instead of libgdal-dev The following packages will be REMOVED: libgdal1-1.3.1 The following NEW packages will be installed: libgdal1-1.3.2 libgdal1-1.3.2-dev 0 upgraded, 2 newly installed, 1 to remove and 50 not upgraded. E: Package libgdal1-1.3.1-dev has no installation candidate E: Failed to process build dependencies No improvement if I remove libgdal1-1.3.1 manually first. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#393480: xastir: FTBFS: Package libgdal1-1.3.1-dev has no installation candidate
On Mon, Oct 23, 2006 at 11:39:06PM +0200, Bas Zoetekouw wrote: > Hi Hamish! > > Would you like me to NMU xastor to fix this bug, or are you uploading a > fixed package soonish? Hi Bas, Thanks for the offer.. you reminded me to just do it myself. 1.8.2-2 now uploaded. Forgot to close the bug in the changelog though :( Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397859: elinks: Can't build twice in same source tree - insufficient cleanup
Package: elinks
Version: 0.11.1-1
Severity: serious
Justification: no longer builds from source
The debian/rules clean target does not remove the build-lite and
build-main directories, so a subsequent build in the same source tree
fails because those directiories cannot be created (they still exist).
mkdir build-main && cd build-main && ../configure --build x86_64-linux-gnu
--enable-fastmem --prefix=/usr --mandir=\${prefix}/share/man
--sysconfdir=/etc/elinks --without-openssl --without-x --with-gnutls=/usr
--with-perl --enable-nntp --enable-256-colors --enable-leds
--without-spidermonkey --enable-html-highlight
mkdir: cannot create directory `build-main': File exists
make: *** [debian/build-heavy] Error 1
This is a risk of using pbuilder for all your development builds :-|
Hamish
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-amd64
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Versions of packages elinks depends on:
ii debconf 1.5.8 Debian configuration management sy
ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co
ii libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii libexpat11.95.8-3.3 XML parsing C library - runtime li
ii libgnutls13 1.4.4-2 the GNU TLS library - runtime libr
ii libgpmg1 1.19.6-22 General Purpose Mouse - shared lib
ii libidn11 0.6.5-1 GNU libidn library, implementation
ii liblua50 5.0.3-2 Main interpreter library for the L
ii liblualib50 5.0.3-2 Extension library for the Lua 5.0
ii libmozjs0d 1.8.0.7-1 The Mozilla SpiderMonkey JavaScrip
ii libperl5.8 5.8.8-6.1 Shared Perl library
ii zlib1g 1:1.2.3-13 compression library - runtime
elinks recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411063: verilog: diff for NMU version 0.8-4.2
On Wed, Feb 28, 2007 at 05:47:34PM +0100, Steinar H. Gunderson wrote: > tags 411063 + patch > thanks > > Hi, > > Attached is the diff for my verilog 0.8-4.2 NMU. Thanks for the NMU Steinar. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419618: xpdf: segfault on print
On Mon, Apr 16, 2007 at 11:51:03PM +0100, Stephen Gran wrote: > Package: xpdf-reader > Version: 3.01-9 > Severity: grave > > The pdf at http://travel.state.gov/pdf/ds-5504.pdf can reliably crash > xpdf, kpdf, and evince when I try to print it. This may be a problem > of the interaction between the pdf viewers and cups, although since all > 3 share the segfault and acroread doesn't, I am inclined to think it's > a problem of the viewers. I have marked it grave, as segfaults usually > make me worry about arbitrary code execution and the like. If you feel > that the severity isn't justified, feel free to lower the priority. > > I'll clone this to evince and kpdf once I get a bug number back from the > BTS. Hi, It prints ok here on etch. CUPS is my print server also. Do you have trouble printing to file, or only to the printer? Xpdf 3.02 should be uploaded RSN so I'll be interested to get an update from you at that time. Thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
