Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

[Y]

Package: qemu-guest-agent
Version: 1:8.1.2+ds-1~bpo12+1
Severity: serious
Justification: 6

Dear Maintainer,

The problem arose after upgrading from bullseye to bookworm.
All was OK on bullseye, but on bookworm qemu-ga refuse to start with
following messages :

1702295113.963828: debug: disabling command: guest-get-devices
1702295113.963868: critical: error opening channel 
'/dev/virtio-ports/org.qemu.guest_agent.0': No such file or directory
1702295113.963873: critical: failed to create guest agent channel
1702295113.963875: critical: failed to initialize guest agent channel

The systemd command looks like :
[Unit]
Description=QEMU Guest Agent
BindsTo=dev-virtio\x2dports-org.qemu.guest_agent.0.device
After=dev-virtio\x2dports-org.qemu.guest_agent.0.device

[Service]
ExecStart=-/usr/sbin/qemu-ga
Restart=always
RestartSec=0

[Install]


Regards

JP P


-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-0.deb11.13-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qemu-guest-agent depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9+deb12u3
ii  libglib2.0-0 2.74.6-2
ii  libnuma1 2.0.16-1
ii  libudev1 252.19-1~deb12u1
ii  liburing22.3-3

qemu-guest-agent recommends no packages.

qemu-guest-agent suggests no packages.

-- Configuration Files:
/etc/init.d/qemu-guest-agent changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="QEMU Guest Agent"
NAME=qemu-ga
DAEMON=/usr/sbin/$NAME
PIDFILE=/var/run/$NAME.pid
set -x
DAEMON_ARGS=""
TRANSPORT=virtio-serial:/dev/virtio-ports/org.qemu.guest_agent.0
[ -x "$DAEMON" ] || exit 0
. /lib/init/vars.sh
do_check_transport() {
method=${TRANSPORT%%:*}; path=${TRANSPORT#*:}
case "$method" in
virtio-serial | isa-serial)
if [ ! -e "$path" ]; then
echo log_warning_msg "$NAME: transport endpoint not found, 
not starting"
return 1
fi
;;
*) echo 'Not virtio-serial or isa-serial'
   ;;
esac
}
do_start()
{
# Return
#   0 if daemon has been started
#   1 if daemon was already running
#   2 if daemon could not be started
echo start-stop-daemon -Sq -p $PIDFILE -x $DAEMON --test > /dev/null \
|| return 1
echo start-stop-daemon -Sq -p $PIDFILE -x $DAEMON -- --daemonize \
$DAEMON_ARGS -m "$method" -p "$path" \
|| return 2
}
do_stop()
{
# Return
#   0 if daemon has been stopped
#   1 if daemon was already stopped
#   2 if daemon could not be stopped
#   other if a failure occurred
echo start-stop-daemon -Kq --retry=TERM/30/KILL/5 -p $PIDFILE --name 
$NAME
}
case "$1" in
  start)
do_check_transport || exit 0
echo 'Apres check-transport'
exit 10
[ "$VERBOSE" != no ] && echo log_daemon_msg "Starting $DESC" $NAME
echo do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && echo log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && echo log_end_msg 1 ;;
esac
;;
  stop)
[ "$VERBOSE" != no ] && echo log_daemon_msg "Stopping $DESC" $NAME
echo do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && echo log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && echo log_end_msg 1 ;;
esac
;;
  status)
status_of_proc "$DAEMON" $NAME && exit 0 || exit $?
;;
  restart|force-reload) # we do not support reload
do_check_transport || exit 0
echo log_daemon_msg "Restarting $DESC" $NAME
echo do_stop
case "$?" in
  0|1)
echo do_start
case "$?" in
0) echo log_end_msg 0 ;;
1) echo log_end_msg 1 ;; # Old process is still running
*) echo log_end_msg 1 ;; # Failed to start
esac
;;
  *)
# Failed to stop
echo log_end_msg 1
;;
esac
;;
  *)
echo "Usage: /etc/init.d/qemu-guest-agent 
{start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac


-- no debconf information

Bug#1016903: Update debian patches for enabling git-updates.diff in gcc-12-12.2.0-14 and 17

[Ricky X. Y. LIU]

diff -Narup a/debian/patches/gcc-distro-specs.diff 
b/debian/patches/gcc-distro-specs.diff
--- a/debian/patches/gcc-distro-specs.diff  2022-10-31 21:50:28.0 
+0800
+++ b/debian/patches/gcc-distro-specs.diff  2023-04-07 09:57:08.034297864 
+0800
@@ -1,20 +1,19 @@
 # DP: Add empty distro and hardening specs

 a/src/gcc/gcc.cc
-+++ b/src/gcc/gcc.cc
-@@ -27,6 +27,11 @@ CC recognizes how to compile each input
- Once it knows which kind of compilation to perform, the procedure for
+--- a/src/gcc/gcc.cc   2023-04-06 08:20:07.0 +0800
 b/src/gcc/gcc.cc   2023-04-07 09:54:02.948157378 +0800
+@@ -28,6 +28,10 @@ Once it knows which kind of compilation
  compilation is specified by a string called a "spec".  */

+ #define INCLUDE_STRING
 +/* Inject some default compilation flags which are used as the default.
 +   Done by the packaging build system.  Should that be done in the headers
 +   gcc/config//*.h instead?  */
 +#include "distro-defaults.h"
-+
  #include "config.h"
  #include "system.h"
  #include "coretypes.h"
-@@ -984,6 +989,90 @@ proper position among the other output f
+@@ -986,6 +990,90 @@ proper position among the other output f
  #define LINK_GCC_C_SEQUENCE_SPEC "%G %{!nolibc:%L %G}"
  #endif

@@ -105,7 +104,7 @@
  #ifndef LINK_SSP_SPEC
  #ifdef TARGET_LIBC_PROVIDES_SSP
  #define LINK_SSP_SPEC "%{fstack-protector|fstack-protector-all" \
-@@ -1040,7 +1129,7 @@ proper position among the other output f
+@@ -1042,7 +1130,7 @@ proper position among the other output f
  #ifndef LINK_PIE_SPEC
  #ifdef HAVE_LD_PIE
  #ifndef LD_PIE_SPEC
@@ -114,7 +113,7 @@
  #endif
  #else
  #define LD_PIE_SPEC ""
-@@ -1157,6 +1246,7 @@ proper position among the other output f
+@@ -1159,6 +1247,7 @@ proper position among the other output f
 "%{flto|flto=*:%
Subject: Update debian patches for enabling git-updates.diff in 
gcc-12-12.2.0-14 and 17

Dear,

The patch git-updates.diff including bug fixes from release/gcc-12 branch have 
not been enabled in rules.patch, for gcc-12-12.2.0-14 and -17 (sid and exp).
( see  
https://salsa.debian.org/toolchain-team/gcc/-/blob/gcc-12-debian/debian/rules.patch
 line 15~17 )

To enable git-updates.diff, some of debian patches need to be updated :

debian/patches/gcc-distro-specs.diff
and
debian/patches/gcc-multilib-multiarch.diff

I made a patch to update these debian patches, so that the build of 
gcc-12-12.2.0-14 and -17 work normally, and PR 106322 is included.
[https://salsa.debian.org/assets/twitter_card-570ddb06edf56a2312253c5872489847a0f385112ddbcd71ccfa1570febab5d2.jpg]
debian/rules.patch · gcc-12-debian · Debian GCC Maintainers / GCC · 
GitLab
Debian Salsa Gitlab
salsa.debian.org




Thanks,
Best Regards,
Ricky X.Y. LIU





CONFIDENTIALITY NOTICE:

The content of this email and any attachments (“Email”) is confidential, may be 
privileged, subject to copyright and may be read, copied and used only by the 
intended recipient.

If you are not the intended recipient, please notify the sender by return email 
or telephone immediately and erase all copies (including any attachments) and 
do not disclose the Email or any part of it to any person. Any use, retention, 
disclosure, copying, printing, forwarding or dissemination of the Email is 
strictly prohibited if you are not the intended recipient.

ASTRI reserve the right to monitor all email communications through ASTRI’s 
networks.

Bug#1016903: Update debian patches for enabling git-updates.diff in gcc-12-12.2.0-14 and 17

[Ricky X. Y. LIU]

Dear,

The patch git-updates.diff including bug fixes from release/gcc-12 branch have 
not been enabled in rules.patch, for gcc-12-12.2.0-14 and -17 (sid and exp).
( see  
https://salsa.debian.org/toolchain-team/gcc/-/blob/gcc-12-debian/debian/rules.patch
 line 15~17 )

To enable git-updates.diff, some of debian patches need to be updated :

debian/patches/gcc-distro-specs.diff
and
debian/patches/gcc-multilib-multiarch.diff

I made a patch to update these debian patches, so that the build of 
gcc-12-12.2.0-14 and -17 work normally, and PR 106322 is included.
[https://salsa.debian.org/assets/twitter_card-570ddb06edf56a2312253c5872489847a0f385112ddbcd71ccfa1570febab5d2.jpg]
debian/rules.patch · gcc-12-debian · Debian GCC Maintainers / GCC · 
GitLab
Debian Salsa Gitlab
salsa.debian.org




Thanks,
Best Regards,
Ricky X.Y. LIU





CONFIDENTIALITY NOTICE:

The content of this email and any attachments (“Email”) is confidential, may be 
privileged, subject to copyright and may be read, copied and used only by the 
intended recipient.

If you are not the intended recipient, please notify the sender by return email 
or telephone immediately and erase all copies (including any attachments) and 
do not disclose the Email or any part of it to any person. Any use, retention, 
disclosure, copying, printing, forwarding or dissemination of the Email is 
strictly prohibited if you are not the intended recipient.

ASTRI reserve the right to monitor all email communications through ASTRI’s 
networks.


diff -Narup a/debian/patches/gcc-distro-specs.diff b/debian/patches/gcc-distro-specs.diff
--- a/debian/patches/gcc-distro-specs.diff	2022-10-31 21:50:28.0 +0800
+++ b/debian/patches/gcc-distro-specs.diff	2023-04-07 09:57:08.034297864 +0800
@@ -1,20 +1,19 @@
 # DP: Add empty distro and hardening specs
 
 a/src/gcc/gcc.cc
-+++ b/src/gcc/gcc.cc
-@@ -27,6 +27,11 @@ CC recognizes how to compile each input
- Once it knows which kind of compilation to perform, the procedure for
+--- a/src/gcc/gcc.cc	2023-04-06 08:20:07.0 +0800
 b/src/gcc/gcc.cc	2023-04-07 09:54:02.948157378 +0800
+@@ -28,6 +28,10 @@ Once it knows which kind of compilation
  compilation is specified by a string called a "spec".  */
  
+ #define INCLUDE_STRING
 +/* Inject some default compilation flags which are used as the default.
 +   Done by the packaging build system.  Should that be done in the headers
 +   gcc/config//*.h instead?  */
 +#include "distro-defaults.h"
-+
  #include "config.h"
  #include "system.h"
  #include "coretypes.h"
-@@ -984,6 +989,90 @@ proper position among the other output f
+@@ -986,6 +990,90 @@ proper position among the other output f
  #define LINK_GCC_C_SEQUENCE_SPEC "%G %{!nolibc:%L %G}"
  #endif
  
@@ -105,7 +104,7 @@
  #ifndef LINK_SSP_SPEC
  #ifdef TARGET_LIBC_PROVIDES_SSP
  #define LINK_SSP_SPEC "%{fstack-protector|fstack-protector-all" \
-@@ -1040,7 +1129,7 @@ proper position among the other output f
+@@ -1042,7 +1130,7 @@ proper position among the other output f
  #ifndef LINK_PIE_SPEC
  #ifdef HAVE_LD_PIE
  #ifndef LD_PIE_SPEC
@@ -114,7 +113,7 @@
  #endif
  #else
  #define LD_PIE_SPEC ""
-@@ -1157,6 +1246,7 @@ proper position among the other output f
+@@ -1159,6 +1247,7 @@ proper position among the other output f
 "%{flto|flto=*:%

Bug#987641: Bug#988830: [pre-approval] unblock e2fsprogs [Was: Bug#987641: e2fsprogs: FTBFS on armel/armhf with a 64-bit kernel]

[Theodore Y. Ts'o]

On Thu, May 20, 2021 at 05:55:34PM +0200, Cyril Brulebois wrote:
> Paul Gevers  (2021-05-20):
> > On 20-05-2021 00:11, Theodore Y. Ts'o wrote:
> > 
> > Unfortunately, there was no release.debian.org bug to track this.  Due
> > to the current high volume to our list, this fell from the radar. To
> > avoid this I now generate a pre-approval unblock request to discuss
> > this, because than it shows up in our tools. Please follow up there.
> 
> Yes, and I see a question was raised for the Installer team but
> debian-boot@ wasn't cc'd, and we aren't psychic. :)

My apologies for not getting the process right by opening a
pre-approval bug earlier!

> > Can you elaborate where you see the *risks* of the patch? Is this
> > patch backwards compatible? I.e. does it work correctly on data
> > generated with the old e2fsprogs? If not, what must the user do to
> > avoid issues? Should it be mentioned in the release notes?

That patch is rather long, but it's all mostly of the form:

-   tail = (struct ext4_fc_tail *)ext4_fc_tag_val(tl);
+   memcpy(, ext4_fc_tag_val(tl), sizeof(tail));

So the risks are very low.

> > Apart from the failing test cases, I see in the patch description that
> > there's also real use cases impacted (corner cases if I interpret them
> > right). IIUC these are no regressions but I'd like to be sure. And
> > what's the impact for users of those corner cases (especially the new
> > Linux feature, I would expect that some users would be going to use
> > those).

Ext4 fast commits is a relatively new feature which is not enabled by
mke2fs by default.  It's a pretty cool feature in that in can result
in some very impressive performance increases (75-130% improvements on
some benchmarks), but there are still some rough edges.  So in general
it's not something that an "enterprise distro" would be supporting,
although I imagine there will be some intrepid Debian Stable users who
might want to try using it.

The real world corner cases are if you are using a 32-bit arm binary
on a 64-bit binary, and if you are using a sparc64 system (not an
officially supported Debian arch).  I'm not sure if misaligned pointer
accesses are allowed in arm-32 kernel code, but it's definitely not
supported on sparc64, so there is also a kernel-side patch which
needed for those platforms that will be in 5.13 (landing upstream in
2-3 weeks).

There are number of other minor bug fixes that I might want to include
at the same time, but none of them are ones that I can honestly call
"release-critical".  Perhaps the one that I would want to pull in, and
which is very low risk is:

  libext2fs: fix missing mutex unlock in an error path of the Unix I/O manager

  Originally from https://github.com/tytso/e2fsprogs/pull/68

  Signed-off-by: Alexander Kanavin 
  Signed-off-by: Theodore Ts'o 

Cheers,

- Ted

Bug#987641: [PING to debian-release] Re: Bug#987641: e2fsprogs: FTBFS on armel/armhf with a 64-bit kernel

[Theodore Y. Ts'o]

Ping to the debian-release bug.  Do you want me to upload a fix to
this bug where e2fsprogs fails its regression test (and thus its
package build) when armhf and armel are running on a 64-bit ARM
platform, but they were built successfully when run on a 32-bit ARM
builder?

No question this is a real bug, and it is fixed upstream already.  But
do you want me to upload a fix *now*, during the hard freeze, given
the impact on the installer, et. al.?

Thanks!
- Ted


On Mon, May 03, 2021 at 06:24:54PM -0400, Theodore Ts'o wrote:
> On Mon, May 03, 2021 at 11:00:37PM +0200, Aurelien Jarno wrote:
> > 
> > Maybe I should give a bit of context here. First of all, there is one armhf
> > buildd, arm-arm-01, setup as an arm64 machine with a 32-bit armhf chroot. It
> > has been setup following [1] a study from Steve McIntyre [1]. It appears
> > that e2fsprogs first failed to build there [2] and got requeued on another
> > buildd where it succeed.
> > 
> > Now with my DSA and buildd maintainer hat on, we have been experiencing for
> > quite a lot of VM crashes when building packages in 32-bit armhf/armel VMs
> > on arm64 machines, so we have recently stopped using VMs to build them and
> > instead rely on chroots.
> 
> Thanks for the context.  I had indeed noticed shortly after 1.46.2-1
> was released that it had failed on the first armhf buildd, and then
> when it was retried, it got successfully built.  Given that this was
> right before the bulleye release freeze hardened, this had been on my
> radar screen to fix, since it was clearly non-optimal, but I had
> assumed that it would be OK to let things slide until after the
> Bullseye release, since after all e2fsprogs 1.46.2-1 *did*
> successfully get built on armhf.
> 
> For me, this is really a question of timing.  It will definitely be
> the case that the next source upload of e2fsprogs will have the
> armhf/armel build fix.  The question I have is should I upload the fix
> before Bullseye releases, or after the Bullseye release.
> 
> What is the impact on the buildd and DSA support effort if we wait
> until after the Debian 11.0 release?  What is the pain if we leave
> this unfixed until Bullseye releases (I'm assuming that it's going to
> be released soon)?  The buildd's aren't going to be rebuilding
> e2fsprogs until the next source upload, I would think.
> 
> Contrawise, what is the impact on the Debian Release and Debian
> Installer teams if I push out a bug-fix-only e2fsprogs source package
> in the next week or so?
> 
> I'll do what is least disruptive for all of the relevant teams.  Let
> me know what's preferred.
> 
> Cheers,
> 
>   - Ted

Bug#987353: CVE-2020-8903 CVE-2020-8907 CVE-2020-8933

[Theodore Y. Ts'o]

On Thu, May 13, 2021 at 09:56:53PM +0100, Marcin Kulisz wrote:
> 
> I hope that we're be able to change it, but for me fundamental
> question is if Google is interested in participating in effort to
> keep those packages in Debian main and if so what resources can be
> committed to do so.  From my side I can say that I'll try to find
> time to work on the relevant packages or to sponsor uploads if
> somebody else want to take on this task.

I'd be interested in helping; while I happen to work for Google, this
would only be in my personal compacity.  One caveat, though, which is
why I've hesitated in replying, is I don't have any experience
packaging Python applications.

In particular, if the Google SDK requires python packages that are
either newer or older than what is packaged in Debian, Debian's
prohibition of private copies of dependencies could make this quite
painful (if nothing else, just simply testing to make sure things
still work with variations in the Python packages available in
Debian)

- Ted

Bug#966813: closing 966813

[Theodore Y. Ts'o]

close 966813 
thanks

This was fixed when e2fsprogs 1.46.0 was uploaded to experimental (the
complain was originally about a very outdated version of e2fsprogs in
experimental).   e2fsprogs 1.46.1 is now in sid and testing.

Bug#948508: CVE-2019-5188: malicious fs can cause stack underflow in e2fsck

[Theodore Y. Ts'o]

Package: e2fsprogs
Version: 1.43.4-2+deb9u1
Severity: grave
Tags: security
Justification: user security hole

E2fsprogs 1.45.5 contains a bug fix for CVE-2019-5188 / TALOS-2019-0973.
The following commits need to be backported to address this
vulnerability in Debian Buster and Debian Stretch:

8dd73c14 - e2fsck: abort if there is a corrupted directory block when rehashing
71ba1375 - e2fsck: don't try to rehash a deleted directory

The impact of this bug is that if an attacker can tricker the system
into running e2fsck on an untrustworthy file system, a maliciously
crafted file system could result in a stack underflow.  The primary
concern is on 32-bit systems; due to limitations in the kind of stack
corruption which can be triggered due to this bug, it is probably not
exploitable on 64-bit systems.

Bug#946639: iwd 1.2-1 is crashing making WiFi access impossible

[Theodore Y. Ts'o]

Package: iwd
Version: 1.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I upgraded my Debian testing system to the latest version of Bullseye,
and I was completely unable to connect to wireless.  In the logs, I see
that iwd is crashing:

Dec 12 09:40:11 lambda kernel: [55486.381334] iwd[202645]: segfault at 38 ip 
55b1995e2056 sp 7ffc966c5360 error 6 in iwd[55b1995c4000+84000]
Dec 12 09:40:11 lambda kernel: [55486.381374] Code: 48 83 c4 20 e9 58 fe ff ff 
0f 1f 00 3c 21 0f 85 70 ff ff ff 31 c0 80 7c 24 10 00 0f 95 c0 83 c0 01 41 89 
47 08 48 8b 44 24 18 <49> 89 46 38 e9 51 ff ff ff 90 41 8b 77 08 85 f6 0f 84 44 
ff ff ff

The iwd crash happens when a wireless network is selected via
NetworkManager.  The NetworkManager icon will then show that it is
trying to connect to a network, and after a few seconds, it will go back
to the "I'm not connected to any network" --- and the logs show that iwd
has crashed again.  :-(

Reverting to iwd 1.1-1 makes my system usable again.  I was able to
download iwd 1.1-1 by using a USB attached ethernet using the Verizon
MiFi hotspot.  So that confirms that it's not a DHCP failure, but rather
a WiFi association failure and between that and "reverting to the
previous version" fixes it, puts the finger of blame pretty squarely on
iwd 1.2-1.

This failure occured when connecting to three different network.  (a)
GoogleGuest at GoogleNYC, (b) a hotspot using a Pixel 4 XL handset, and
(c) a Verizon LTE MiFi hotspot.  I am running a 5.3.0 kernel with
minimal changes (the ext4 patches that were pushed to Linus during the
recent pre-5.4-rc1 merge window) that should not be relevant to this
failure.

The hardware is a Dell XPS 13 model 9370, using the ath10k_pci driver.

Please let know if there is anything I can do to help debug this
failure.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-00068-g7ec6dbcda3db (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iwd depends on:
ii  libc6 2.29-3
ii  libreadline8  8.0-3

iwd recommends no packages.

iwd suggests no packages.

-- no debconf information

Bug#941139: CVE-2019-5094: malicious fs can cause buffer overrun in e2fsck

[Theodore Y. Ts'o]

Package: debian
Version: 1.44.5-1+deb10u1
Severity: grave
Tags: security
Justification: user security hole

E2fsprogs 1.45.4 contains a bugfix for CVE-2019-5094 / TALOS-2019-0887.
We need to backport commit 8dbe7b475ec5: "libsupport: add checks to
prevent buffer overrun bugs in quota code" to the versions of e2fsprogs
found in Debian Buster and Stretch.

The impact of this bug is that if an attacker can tricker the system
into running e2fsck on an untrustworthy file system as root, a
maliciously crafted file system could result in a buffer overflow that
can result in arbitrary userspace memory modification.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-00068-g7ec6dbcda3db (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#940092: flowblade doesn't start

[Theodore Y. Ts'o]

Package: flowblade
Version: 2.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed flowblade, and then tried to start it.  It failed to start;
I expected it to start and be usable.  :-)

% flowblade
FLOWBLADE MOVIE EDITOR 2.2
--
Launch script dir: /bin
Running from filesystem...
MLT found, version: 6.16.0
Failed to import module app.py to launch Flowblade!
ERROR: No module named processutils
Installation was assumed to be at: /bin/Flowblade


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-rc4-15023-g572feee69df4 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flowblade depends on:
ii  frei0r-plugins1.6.1-3
ii  gir1.2-gdkpixbuf-2.0  2.38.1+dfsg-1
ii  gir1.2-glib-2.0   1.58.3-2
ii  gir1.2-gtk-3.03.24.10-1
ii  gir1.2-pango-1.0  1.42.4-7
ii  gmic  2.4.5-1+b1
ii  libmlt-data   6.16.0-3
ii  librsvg2-common   2.44.14-1
ii  python2.7.16-1
ii  python-cairo  1.16.2-1+b1
ii  python-dbus   1.2.8-3
ii  python-gi 3.32.2-1
ii  python-gi-cairo   3.32.2-1
ii  python-mlt6.16.0-3
ii  python-numpy  1:1.16.2-1
ii  python-pil6.1.0-1
ii  swh-plugins   0.4.17-2

flowblade recommends no packages.

flowblade suggests no packages.

-- no debconf information

Bug#932874: logsave: Insufficient Breaks/Replaces on e2fsprogs

[Theodore Y. Ts'o]

On Wed, Jul 24, 2019 at 05:46:50AM +0200, Sven Joachim wrote:
> Package: logsave
> Version: 1.45.3-1
> Severity: serious
> 
> Installing logsave without upgrading e2fsprogs fails:
> 
> ,
> | Preparing to unpack .../logsave_1.45.3-1_amd64.deb ...
> | Unpacking logsave (1.45.3-1) ...
> | dpkg: error processing archive 
> /var/cache/apt/archives/logsave_1.45.3-1_amd64.deb (--install):
> |  trying to overwrite '/sbin/logsave', which is also in package e2fsprogs 
> 1.45.2-1
> `
> 
> There are a Replaces/Breaks relationships on e2fsprogs (<< 1.45.2-1)
> which need to be bumped to (<< 1.45.3-1).

... and I missed this in the blizzard of Debian bugs e-mails re:
logsave as well.  Will fix in the next upload...

   - Ted

Bug#932855: Bug#932881: add dependency on logsave

[Theodore Y. Ts'o]

Control: tags 932855 +pending
Control: tags 932859 +pending
Control: tags 932861 +pending
Control: tags 932881 +pending
Control: tags 932888 +pending

My apologies, I hadn't realized initramfs had a dependency on logsave.
I guess I should have known that, but it had slipped my mind.  This
will be fixed in the next release of e2fsprogs.

 - Ted

commit f3223c5fa2b7e0e3e10c96dea0fce2048910ff98
Author: Theodore Ts'o 
Date:   Wed Jul 24 12:20:11 2019 -0400

debian: add a hard dependency on logsave to e2fsprogs

The initramfs created by the initramfs-tools package needs logsave and
assumes it comes along with e2fsprogs.  If it is not present, the
result systems which will fail to boot.  Fix this by adding the
dependency.

In the future initramfs-tools will explicitly ask for logsave (tracked
in Debian Bug: #932854), but we'll need to keep this dependency until
the next stable release of Debian.

Addresses-Debian-Bug: #932855
Addresses-Debian-Bug: #932859
Addresses-Debian-Bug: #932861
Addresses-Debian-Bug: #932881
Addresses-Debian-Bug: #932888

Signed-off-by: Theodore Ts'o 

diff --git a/debian/control b/debian/control
index 3ea0b404..f20e9228 100644
--- a/debian/control
+++ b/debian/control
@@ -200,8 +200,9 @@ Description: ext2/ext3/ext4 file system libraries - headers 
and static libraries
 Package: e2fsprogs
 XB-Important: yes
 Pre-Depends: ${shlibs:Depends}, ${misc:Depends}, libblkid1, libuuid1
+Depends: logsave
 Multi-Arch: foreign
-Suggests: gpart, parted, fuse2fs, e2fsck-static, logsave
+Suggests: gpart, parted, fuse2fs, e2fsck-static
 Recommends: e2fsprogs-l10n
 Architecture: any
 Description: ext2/ext3/ext4 file system utilities

Bug#923457: test_likelihood_nh (Failed)

[Julien Y. Dutheil]

Dear Andreas,

Ok, great. Will try to fix that unit test thing upstream for next time.

Best,

Julien.

On Tue, Mar 12, 2019 at 3:18 PM Andreas Tille  wrote:

> Hi Julien
>
> On Tue, Mar 12, 2019 at 11:56:49AM +0100, Julien Y. Dutheil wrote:
> > Ok, I have committed a patch removing the test. But just realized I did
> not
> > update the changelog... should that now be version 2.4.1-3?
>
> I've updated d/changelog but will *not* upload anything since meanwhile
> the package has build on all architectures (randomness was this time on
> our side) and so there is no need to touch anything.  In case the package
> might receive another RC bug we are now on the safe side.
>
> Thanks a lot for your contribution
>
>Andreas.
>
> --
> http://fam-tille.de
>


-- 
Julien Y. Dutheil, Ph-D
0 (+49) 4522 763 298

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#923457: test_likelihood_nh (Failed)

[Julien Y. Dutheil]

Dear Andreas,

Ok, I have committed a patch removing the test. But just realized I did not
update the changelog... should that now be version 2.4.1-3?

Cheers,

Julien.

On Tue, Mar 12, 2019 at 11:03 AM Andreas Tille  wrote:

> On Tue, Mar 12, 2019 at 09:53:10AM +0100, Julien Y. Dutheil wrote:
> > This all boils down to the fact that this unit test is badly designed: it
> > basically maximizes a function from initial random values. I some
> > particular combinations of initial values though, the convergence may
> fail
> > or take too much time. I will redesign the test, but do not have time at
> > the moment. Would it be possible to just deactivate that test for now?
>
> Sure.  IMHO that's the most straightforward way to deal with this issue.
> Since I expect you to be more familiar with the tests I simply assumed
> that you find a more elegant way to deactivate the test than I. ;-)
>
> > In the meantime I also found more symbols errors in libbpp-popgen and I
> > fixed that. I also propagated your modification from bpp-phyl to bpp-seq
> > and bpp-popgen.
>
> I've seen the commits.  Thanks for this.  I'll upload in case there will
> be more bugs reported.  In Freeze we touch only packages with RC bugs.
>
> > On a side note: how can I change my email address (the one that appears
> in
> > the changelog file) ? That one is now deprecated.
>
> It should be changed in debian/control in the Uploaders field as well.
> Both strings need to match each other.
>
> Thanks for your contribution
>
>   Andreas.
>
> --
> http://fam-tille.de
>


-- 
Julien Y. Dutheil, Ph-D
0 (+49) 4522 763 298

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#923457: test_likelihood_nh (Failed)

[Julien Y. Dutheil]

Dear Andreas,

This all boils down to the fact that this unit test is badly designed: it
basically maximizes a function from initial random values. I some
particular combinations of initial values though, the convergence may fail
or take too much time. I will redesign the test, but do not have time at
the moment. Would it be possible to just deactivate that test for now?

In the meantime I also found more symbols errors in libbpp-popgen and I
fixed that. I also propagated your modification from bpp-phyl to bpp-seq
and bpp-popgen.

On a side note: how can I change my email address (the one that appears in
the changelog file) ? That one is now deprecated.

Best regards,

Julien.

On Fri, Mar 8, 2019 at 9:36 AM Julien Y. Dutheil 
wrote:

> Dear Andreas,
>
> Will give it a look asap.
>
> Best,
>
> Julien.
>
> On Fri, Mar 8, 2019 at 9:34 AM Julien Yann Dutheil <
> julien.duth...@univ-montp2.fr> wrote:
>
>> Dear Andreas,
>>
>> Will give it a look asap.
>>
>> Best,
>>
>> Julien.
>>
>> On Fri, Mar 8, 2019 at 6:30 AM Andreas Tille  wrote:
>>
>>> Hi Julien,
>>>
>>> after fixing bug #923457 I realised that the package does not
>>> build on all architectures[1]. S390x fails with[2]
>>>
>>>  4/14 Test  #5: test_likelihood_nh ...***Failed2.44 sec
>>>
>>> / 1
>>> - 2
>>> \ 3
>>> - 4
>>> / 5
>>> - 6
>>> \ 7
>>> - 8
>>> / 9
>>> - 10
>>> \ 11 nodes loaded.
>>> Theta0 set to 0.444785
>>> Theta1 set to 0.137341
>>> Theta2 set to 0.219281
>>> Theta3 set to 0.759382
>>> Theta4 set to 0.549516
>>> Theta5 set to 0.925583
>>> Theta6 set to 0.527333
>>> Theta7 set to 0.891561
>>> Theta8 set to 0.331932
>>> Theta9 set to 0.523327
>>> Initializing data structure: Done.
>>> Number of distinct sites...: 363
>>> Initializing data structure: Done.
>>> Number of distinct sites...: 363
>>>
>>> Optimizing... / 1
>>> Optimizing... - 2
>>> Optimizing... \ 3
>>> Optimizing... - 4
>>> Optimizing... / 5
>>> Optimizing... - 6
>>> Optimizing... \ 7
>>> Optimizing... - 8
>>> Optimizing... / 9
>>> Optimizing... - 10
>>> Optimizing... \ 11
>>> Optimizing... - 12
>>> Optimizing... / 13
>>> Optimizing... - 14
>>>
>>>
>>> Optimizing... / 1
>>> Optimizing... - 2
>>> Optimizing... \ 3
>>> Optimizing... - 4
>>> Optimizing... / 5
>>> Optimizing... - 6
>>> Optimizing... \ 7
>>> Optimizing... - 8
>>> Optimizing... / 9
>>> Optimizing... - 10
>>> Optimizing... \ 11
>>> Optimizing... - 12
>>> Optimizing... / 13
>>> Optimizing... - 14
>>>
>>> 15: 5347.92 15: 5347.92
>>> 0.516673 0.516673
>>> 0.184681 0.184681
>>> 0.209158 0.209158
>>> 0.795359 0.795359
>>> 0.489372 0.489372
>>> 0.918414 0.918414
>>> 0.489537 0.489537
>>> 0.913968 0.913968
>>> 0.180359 0.180359
>>> 0.797456 0.797456
>>> Initializing data structure: Done.
>>> Number of distinct sites...: 365
>>> Initializing data structure: Done.
>>> Number of distinct sites...: 365
>>>
>>> Optimizing... / 1
>>> Optimizing... - 2
>>> Optimizing... \ 3
>>> Optimizing... - 4
>>> Optimizing... / 5
>>> Optimizing... - 6
>>> Optimizing... \ 7
>>> Optimizing... - 8
>>> Optimizing... / 9
>>> Optimizing... - 10
>>> Optimizing... \ 11
>>> Optimizing... - 12
>>> Optimizing... / 13
>>> Optimizing... - 14
>>> Optimizing... \ 15
>>> Optimizing... - 16
>>> Optimizing... / 17
>>>
>>>
>>> Optimizing... / 1
>>> Optimizing... - 2
>>> Optimizing... \ 3
>>> Optimizing... - 4
>>> Optimizing... / 5
>>> Optimizing... - 6
>>> Optimizing... \ 7
>>> Optimizing... - 8
>>> Optimizing... / 9
>>> Optimizing... - 10
>>> Optimizing... \ 11
>>> Optimizing... - 12
>>> Optimizing... / 13
>>> Optimizing... - 14
>>> Optimizing... \ 15
>>> Optimizing... - 16
>>> Optimizing... / 17
>>>
>>> 18: 5391.43 18: 5391.43
>>> 0.60777 0.60777
>>> 0.127151 0.127151
>>> 0.189039 0.189

Bug#923457: test_likelihood_nh (Failed)

[Julien Y. Dutheil]

>> 0.900203 0.900203
>> 0.411605 0.411605
>> 0.919716 0.919716
>> 0.563041 0.563041
>> 0.813833 0.813833
>> 0.194868 0.194868
>> 0.801315 0.801315
>> 0.444785 0.514541 0.514541
>> 0.137341 0.15071 0.15071
>> 0.219281 0.231066 0.231066
>> 0.759382 0.828058 0.828058
>> 0.549516 0.48858 0.48858
>> 0.925583 0.926483 0.926483
>> 0.527333 0.539292 0.539292
>> 0.891561 0.857552 0.857552
>> 0.331932 0.244253 0.244253
>> 0.523327 0.772256 0.772256
>>
>>
>> ...
>>
>> 93% tests passed, 1 tests failed out of 14
>>
>> Total Test time (real) =  31.15 sec
>>
>> The following tests FAILED:
>>5 - test_likelihood_nh (Failed)
>>
>>
>> I remember that I once had even a test failure on my local amd64 - so
>> this test might be a bit undetermined.  Please confirm this and I'd be
>> happy if you could send an *as simple as possible* patch or simply
>> deactivate the patch.  We are in deep freeze and need to find a quick
>> and also simple solution.
>>
>> Kind regards
>>
>>Andreas.
>>
>>
>> [1] https://buildd.debian.org/status/package.php?p=libbpp-phyl
>> [2]
>> https://buildd.debian.org/status/fetch.php?pkg=libbpp-phyl=s390x=2.4.1-2=1551477555=0
>>
>> --
>> http://fam-tille.de
>>
>>
>
> --
> Julien Y. Dutheil, Ph-D
> 0 (+49) 6421 178 986
>
> § Max Planck Institute for Evolutionary Biology
> Molecular Systems Evolution
> Department of Evolutionary Genetics
> Plön -- GERMANY
>
> § Institute of Evolutionary Sciences - Montpellier
> University of Montpellier 2 -- FRANCE
>


-- 
Julien Y. Dutheil, Ph-D
0 (+49) 4522 763 298

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

[Theodore Y. Ts'o]

On Thu, Dec 20, 2018 at 03:17:03PM -0500, Daniel Kahn Gillmor wrote:
> 
> I wonder whether we can rule out any interaction with gpg-agent itself
> -- does "echo getpin | pinentry-gnome3" itself fall back to curses on
> your system when nfs-kernel-server is installed?

I can confirm that that I did this experiment before I uninstalled
nfs-kernel-server --- and it fell back to curses.

The next experiment to do would be to reinstall nfs-kernel-server and
reboot --- and see if it falls back to curses again.

  - Ted

Bug#905195: e2fslibs-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Theodore Y. Ts'o]

Thanks for the report.  I've checked in a fix for this into the
e2fsprogs git repository, and it will be in the next release of e2fsprogs.

  - Ted

Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

[Y. Gablin]

Package: nodejs
Version: 4.4.0~dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,


   * What led up to the situation?
Need for a newer NodeJS than available in Debian-stable, in order to install a 
full Firefox-sync server.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I first tried to apt-get source nodejs from unstable && debbuild on stable.
Then I tried to just install nodejs from unstable onto stable (changing 
sources.list).
As all failed, I then debootstraped Debian stretch in a chroot (systemd-nspawn).
This last test failed too so I installed the nodejs from unstable into the 
chroot.

   * What was the outcome of this action?
Newer NodeJS always fail with "illegal instruction".

   * What outcome did you expect instead?
NodeJS and npm working.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect (that's because of systemd-nspawn; my init system is 
systemd)

Versions of packages nodejs depends on:
ii  libc62.21-9
ii  libgcc1  1:5.3.1-11
ii  libicu55 55.1-7
ii  libssl1.0.2  1.0.2g-1
ii  libstdc++6   5.3.1-11
ii  libuv1   1.8.0-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

nodejs recommends no packages.

nodejs suggests no packages.

-- no debconf information

Bug#814333: squid3: SSL error "sec_error_inadequate_key_usage" in the browser

[Y]

Package: squid3
Version: 3.4.8-6+deb8u1+aptbuild1
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

I downloaded and compiled the squid through apt-build by adding the following 
lines in "/var/cache/apt-build/build/squid3-3.4.8/debian/rules":
 --enable-ssl \
 --enable-ssl-CRTD \
 --with-openssl \

Some https sites aprsentam as error the "sec_error_inadequate_key_usage" 
message as error code.
The errors appear when using Firefox and Iceweasel browsers.
The same sites that feature error in Firefox-based browsers work perfectly in 
Chrome.
A website as an example is the https://pt.wikipedia.org/

I found a palliative in 
https://www.howtoforge.com/filtering-https-traffic-with-squid site that worked.
Apparently removing the line which has the code "NID_key_usage," the file 
/var/cache/apt-build/build/squid3-3.4.8/src/ssl/gadgets.cc solve, but do not 
know if this would imply some other problem .
Compiling the squid using the source of the project site, it does not occur 
this error.



-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages squid3 depends on:
ii  adduser  3.113+nmu3
ii  libc62.19-18+deb8u2
ii  libcap2  1:2.24-8
ii  libcomerr2   1.42.12-1.1
ii  libdb5.3 5.3.28-9
ii  libecap2 0.2.0-3
ii  libexpat12.1.0-6+deb8u1
ii  libgcc1  1:4.9.2-10
ii  libgssapi-krb5-2 1.12.1+dfsg-19+deb8u2
ii  libk5crypto3 1.12.1+dfsg-19+deb8u2
ii  libkrb5-31.12.1+dfsg-19+deb8u2
ii  libldap-2.4-22.4.40+dfsg-1+deb8u2
ii  libltdl7 2.4.2-1.11
ii  libnetfilter-conntrack3  1.0.4-1
ii  libnettle4   2.7.1-5
ii  libpam0g 1.1.8-3.1+deb8u1
ii  libsasl2-2   2.1.26.dfsg1-13+deb8u1
ii  libssl1.0.0  1.0.1k-3+deb8u2
ii  libstdc++6   4.9.2-10
ii  libxml2  2.9.1+dfsg1-5+deb8u1
ii  logrotate3.8.7-1+b1
ii  lsb-base 4.1+Debian13+nmu1
ii  netbase  5.3
ii  squid3-common3.4.8-6+deb8u1+aptbuild1

squid3 recommends no packages.

Versions of packages squid3 suggests:
pn  resolvconf   
pn  smbclient
pn  squid-cgi
pn  squid-purge  
pn  squidclient  
pn  ufw  
pn  winbindd 

-- Configuration Files:
/etc/squid3/squid.conf changed:
acl SSL_ports port 443
acl Safe_ports port 80  # http
acl Safe_ports port 21  # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70  # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
acl sites_bloqueados dstdomain "/etc/squid3/empresa/sites-bloqueados"
acl localnet src 192.168.25.0/24
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost manager
http_access deny manager
http_access deny sites_bloqueados
http_access allow localnet
http_access allow localhost
http_access deny all
http_port 3128 transparent
https_port 3129 transparent ssl-bump generate-host-certificates=on 
dynamic_cert_mem_cache_size=4MB cert=/etc/squid3/certificado/empresa.pem
ssl_bump server-first all
sslcrtd_program /usr/lib/squid3/ssl_crtd -s /etc/squid3/certificado/ssl_db -M 
4MB
coredump_dir /var/spool/squid3
refresh_pattern ^ftp:   144020% 10080
refresh_pattern ^gopher:14400%  1440
refresh_pattern -i (/cgi-bin/|\?) 0 0%  0
refresh_pattern .   0   20% 4320
always_direct allow all


-- no debconf information

Bug#751511: xfslibs-dev: Incorrect licensing information in debian/copyright

[Y Giridhar Appaji Nag]

Source: xfslibs-dev
Severity: serious
Justification: Policy 4.5

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It looks like the xfslibs-dev package source files are licensed under LGPL
v2.1, however the debian/copyright file indicates that only the libhandle
package is under LGPL and that the rest of the package is licensed under GPL.

Giridhar

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJTmwnSAAoJEKjSzROqVEqhm4wQAIVHEEsJ1+YkbxQOx8ubKHov
hW4HJK1h6PoBudiyK+RSBIekl8WV08qvwaUJHg6xPodH3N/WhfDw7vduQv97s5Hr
DJ92DWA5j06XUOKNPsRFGi6mGL2VVPgOkb+3xGPWgTLpAeUfbkukOStp7Gi8tOEI
6REM2z3uh8krCzuIsB1RS4j8SWXFVy3OE0ROKfL92JsWyVgUpRmDdU0nwEmhjrfn
7Bk4ecEaZA3nXeT5FY2yAEtk0hIat/rtCYe66lJw6k7FmogD5W46tb6U2bgtmqt1
I1JGDivQgbBd1pogxUdgNyK4lizSkTOdg24WuaGHMhI7sH6+DHMPOiC81INsf1qY
6q8OB7naez3x8BFGMH03BL6wpn1yVAd+m0nEXJLluu3niLlOHjSTLAbqiX8h+n2b
PyXFnTViaGI8oYGHbTnOC+t/o+mbnbIE7hnsfdDhVXqDhZo5dJtWl4VxNuOBTOV8
7ZiNH4y8kHwU8yT6dW/dGLCYxWvE+RvTGhgL/V0tO2ipkuVUmZaMyvvUuk6xSfER
wSf1AUWhhgJBJzGRZj4UglWJ99MaZMxYzLMJq20uQmTSzlnN//vLsmjMcfFcx61f
33AaniHi0fbOwPHV5lecxjyxKgjo5CSd0EqaCV7fenAB1Tr6mKXB3frrOJMxbhlr
c69uwhjzVNZRP8tudDtC
=yzqb
-END PGP SIGNATURE-


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

Bug#724972: otrs2: Postmaster mail account fetch mail internal server error

[y]

Package: otrs2
Version: 3.2.10-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,
Afer update of perl to perl5.18.1-4. OTRS2 postmaster account fetch mail fails 
with the followin error in the log.

[Mon Sep 30 16:13:08.312400 2013] [:error] [pid 6811] [Mon Sep 30 16:13:08 
2013] -e: open body: Invalid argument at /usr/share/perl5/MIME/Entity.pm line 
1878.\n



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

Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages otrs2 depends on:
ii  adduser  3.113+nmu3
ii  apache2  2.4.6-3
ii  apache2-bin [httpd-cgi]  2.4.6-3
ii  dbconfig-common  1.8.47+nmu1
ii  debconf [debconf-2.0]1.5.51
ii  dpkg 1.16.10
ii  libapache-dbi-perl   1.12-1
ii  libapache2-reload-perl   0.12-2
ii  libauthen-sasl-perl  2.1500-1
ii  libcrypt-passwdmd5-perl  1.3-10
ii  libcss-minifier-perl 0.01-1
ii  libdate-pcalc-perl   6.1-2+b1
ii  libdbd-mysql-perl4.023-1+b1
ii  libdbd-pg-perl   2.19.3-1+b1
ii  libdbi-perl  1.628-1+b1
ii  libemail-valid-perl  0.190-1
ii  libgd-graph-perl 1.44-6
ii  libgd-text-perl  0.86-8
ii  libio-interactive-perl   0.0.6-1
ii  libio-stringy-perl   2.110-5
ii  libjavascript-minifier-perl  1.05-1
ii  libjs-jquery 1.7.2+dfsg-3
ii  libjs-jquery-ui  1.10.1+dfsg-1
ii  libjs-prototype  1.7.1-3
ii  libjs-yui2.9.0.dfsg.0.1-0.1
ii  libjson-perl 2.59-1
ii  libmail-imapclient-perl  3.31-2
ii  libmail-pop3client-perl  2.18-1
ii  libmailtools-perl2.12-1
ii  libmime-tools-perl   5.503-1
ii  libnet-imap-simple-perl  1.2100-1
ii  libnet-imap-simple-ssl-perl  1.3-3
ii  libnet-smtp-ssl-perl 1.01-3
ii  libpdf-api2-perl 2.020-1
ii  libsoap-lite-perl0.716-1
ii  libtext-csv-perl 1.32-1
ii  libtext-diff-perl1.41-1
ii  libxml-feedpp-perl   0.43-1
ii  libxml-parser-perl   2.41-1+b2
ii  libyaml-libyaml-perl 0.38-3+b1
ii  libyaml-perl 0.84-1
ii  perl [libdigest-sha-perl]5.18.1-4
ii  ttf-dejavu-core  2.33+svn2514-3
ii  ttf-dejavu-extra 2.33+svn2514-3
ii  ucf  3.0027+nmu1

Versions of packages otrs2 recommends:
ii  ispell3.3.02-6
ii  mysql-server  5.5.31+dfsg-1
ii  postgresql9.3+149
ii  procmail  3.22-20

Versions of packages otrs2 suggests:
ii  libencode-hanextra-perl 0.23-2+b3
ii  libjson-xs-perl 2.340-1+b1
ii  libnet-ldap-perl1:0.5700-1
ii  libnet-smtp-tls-butmaintained-perl  0.24-1
ii  libtext-csv-xs-perl 1.01-1+b1
ii  otrs2-doc-en20130520-1

-- debconf information:
  otrs2/pgsql/admin-user: postgres
  otrs2/db/dbname: otrs2
  otrs2/pgsql/authmethod-admin: ident
  otrs2/pgsql/changeconf: false
  otrs2/install-error: abort
  otrs2/mysql/admin-user: root
  otrs2/remote/port:
  otrs2/pgsql/manualconf:
* otrs2/database-type: pgsql
  otrs2/upgrade-error: abort
  otrs2/upgrade-backup: true
  otrs2/pgsql/method: unix socket
  otrs2/db/basepath:
  otrs2/remote/host:
  otrs2/internal/skip-preseed: false
  otrs2/remote/newhost:
  otrs2/db/app-user: otrs
  otrs2/internal/reconfiguring: false
  otrs2/passwords-do-not-match:
  otrs2/pgsql/no-empty-passwords:
  otrs2/dbconfig-remove:
* otrs2/dbconfig-install: true
  otrs2/pgsql/authmethod-user: ident
  otrs2/mysql/method: unix socket
  otrs2/dbconfig-reinstall: false
  otrs2/remove-error: abort
  otrs2/purge: false
  otrs2/missing-db-package-error: abort
  otrs2/dbconfig-upgrade: true


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

Bug#691890: general: sudoers problem

[Y]

Package: general
Severity: grave
Tags: d-i
Justification: renders package unusable



-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

I can not install any software, because if I type 'sudo su' and type the 
correct Password I get only:
USER is not in the sudoers file.  This incident will be reported.

I am the Admin, but I cannot do anything to personalyse my KDE Debian System.

I also cannot edit the sudoers file, witch is empty, because I have not the
Privileges to edit/Save the file

Please send me help per e-mail

Thank you!

PS: I am sorry for my bad english, I am german


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

Bug#579494: socat is GPLv2-only, links against GPLv3 libreadline6

[James Y Knight]

Package: socat
Version: 1.7.1.2-1
Severity: serious

Socat is licensed under the GPLv2, according to the README file, not  
GPLv2 or later. The debian package is built against libreadline6,  
which is under GPLv3 or later. Since GPLv2 and GPLv3 are incompatible,  
this is a license violation.


I'd suggest making socat Build-Depend on libreadline5-dev again to  
solve this problem. (Which thus unfixes bug 553853; that should be  
marked wontfix, since fixing it necessarily involves a license  
violation.)


James



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

Bug#560963: cl-cffi: Loading cffi fails

[James Y Knight]

This is probably related to bug 560781.



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

Bug#552214: (no subject)

[y]

Subject: linux-image-2.6.26-1-686: je n'arrive pas à avoir un affichage 
graphique avec ma lenny et une carte graphique ATI Radeon HD
Package: linux-image-2.6.26-1-686
Version: 2.6.26-13lenny2
Severity: critical
Justification: breaks unrelated software



-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-13lenny2) (da...@debian.org) (gcc 
version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Mar 13 
18:08:45 UTC 2009

** Command line:
root=/dev/sdc1 ro single

** Not tainted

** Kernel log:
[6.055401] usb 5-2: configuration #1 chosen from 1 choice
[6.063999] usb 5-2: New USB device found, idVendor=04d9, idProduct=048e
[6.064037] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[6.064088] usbcore: registered new interface driver hiddev
[6.096888] input: Logitech Logitech USB Keyboard as /class/input/input0
[6.100903] input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech USB 
Keyboard] on usb-:00:1d.0-1
[6.120787] input: Logitech Logitech USB Keyboard as /class/input/input1
[6.120787] input,hidraw1: USB HID v1.11 Device [Logitech Logitech USB 
Keyboard] on usb-:00:1d.0-1
[6.156787] input: HID 04d9:048e as /class/input/input2
[6.168806] ata3: SATA link down (SStatus 0 SControl 300)
[6.172785] input,hidraw2: USB HID v1.10 Mouse [HID 04d9:048e] on 
usb-:00:1d.0-2
[6.172785] usbcore: registered new interface driver usbhid
[6.172785] usbhid: v2.6:USB HID core driver
[6.538040] ata4: SATA link down (SStatus 0 SControl 300)
[6.967549] ahci :03:00.0: AHCI 0001. 32 slots 2 ports 3 Gbps 0x3 
impl SATA mode
[6.967587] ahci :03:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
[6.967622] PCI: Setting latency timer of device :03:00.0 to 64
[6.971512] scsi4 : ahci
[6.971512] scsi5 : ahci
[6.971512] ata5: SATA max UDMA/133 abar m8...@0xe700 port 0xe7000100 
irq 19
[6.971512] ata6: SATA max UDMA/133 abar m8...@0xe700 port 0xe7000180 
irq 19
[7.534400] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[007b0ced1fd0]
[7.546321] ata5: SATA link down (SStatus 0 SControl 300)
[7.878328] ata6: SATA link down (SStatus 0 SControl 300)
[7.898306] JMB: IDE controller (0x197b:0x2363 rev 0x02) at  PCI slot 
:03:00.1
[7.898306] JMicron IDE :03:00.1: enabling device ( - 0001)
[7.898306] ACPI: PCI Interrupt :03:00.1[B] - GSI 16 (level, low) - 
IRQ 16
[7.898306] JMB: 100% native mode on irq 16
[7.898306] PCI: Setting latency timer of device :03:00.1 to 64
[7.898306] ide0: BM-DMA at 0xc400-0xc407
[7.898306] ide1: BM-DMA at 0xc408-0xc40f
[7.898306] Probing IDE interface ide0...
[9.239862] hda: TSSTcorp CDDVDW SH-S222A, ATAPI CD/DVD-ROM drive
[9.911519] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[9.911691] hda: drive side 80-wire cable detection failed, limiting max 
speed to UDMA33
[9.911725] hda: UDMA/33 mode selected
[9.912909] Probing IDE interface ide1...
[   10.674139] ide0 at 0xc000-0xc007,0xc102 on irq 16
[   10.680196] ide1 at 0xc200-0xc207,0xc302 on irq 16
[   11.253139] Driver 'sd' needs updating - please use bus_type methods
[   11.253139] sd 0:0:0:0: [sda] 293044655 512-byte hardware sectors (150039 MB)
[   11.253139] sd 0:0:0:0: [sda] Write Protect is off
[   11.253139] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   11.253139] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   11.253139] sd 0:0:0:0: [sda] 293044655 512-byte hardware sectors (150039 MB)
[   11.253139] sd 0:0:0:0: [sda] Write Protect is off
[   11.253139] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   11.253139] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   11.253139]  sda: sda1
[   11.257139] sd 0:0:0:0: [sda] Attached SCSI disk
[   11.257139] sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 
MB)
[   11.257139] sd 1:0:0:0: [sdb] Write Protect is off
[   11.257139] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   11.257139] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   11.257139] sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 
MB)
[   11.257139] sd 1:0:0:0: [sdb] Write Protect is off
[   11.257139] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   11.257139] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   11.257139]  sdb:6hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB 
Cache
[   11.261146] Uniform CD-ROM driver Revision: 3.20
[   11.265139]  sdb1
[   11.265139] sd 1:0:0:0: [sdb] Attached SCSI disk
[   11.265139] sd 1:0:1:0: [sdc] 586072368 512-byte hardware sectors (300069 MB)
[   11.265139] sd 1:0:1:0: [sdc] Write Protect is off
[   11.265139] sd 1:0:1:0: [sdc] Mode Sense: 00 3a 00 00
[   11.265139] sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, 
doesn't 

Bug#551238: elinks: FTBFS: spidermonkey.c:(.text+0x52858): undefined reference to `JS_SetBranchCallback'

[Y Giridhar Appaji Nag]

On 09/10/16 18:30 +0200, Lucas Nussbaum said ...
  /build/user-elinks_0.12~pre5-1-amd64-G2x4mV/elinks-0.12~pre5/src/scripting/lua/core.c:247:
   warning: the use of `tempnam' is dangerous, better use `mkstemp'
  lib.o: In function `setup_safeguard':
  spidermonkey.c:(.text+0x52858): undefined reference to 
  `JS_SetBranchCallback'

I believe JS_SetBranchCallback is not longer available and we would have to
use JS_SetOperationCallback.  I'll work on a patch to fix this.

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#551238: elinks: FTBFS: spidermonkey.c:(.text+0x52858): undefined reference to `JS_SetBranchCallback'

[Y Giridhar Appaji Nag]

On 09/10/16 23:47 +0530, Y Giridhar Appaji Nag said ...
 On 09/10/16 18:30 +0200, Lucas Nussbaum said ...
   /build/user-elinks_0.12~pre5-1-amd64-G2x4mV/elinks-0.12~pre5/src/scripting/lua/core.c:247:
warning: the use of `tempnam' is dangerous, better use `mkstemp'
   lib.o: In function `setup_safeguard':
   spidermonkey.c:(.text+0x52858): undefined reference to 
   `JS_SetBranchCallback'
 
 I believe JS_SetBranchCallback is not longer available and we would have to
 use JS_SetOperationCallback.  I'll work on a patch to fix this.

Fixed in git, it would be available from next upload to the archive.

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#549818: fusecompress: FTBFS: ./boost/archive/portable_binary_iarchive.hpp:242:62: error: boost/archive/impl/archive_pointer_iserializer.ipp: No such file or directory

[Y Giridhar Appaji Nag]

On 09/10/05 20:22 +0200, Lucas Nussbaum said ...
 
 Relevant part:
  g++ -DHAVE_CONFIG_H -I. -I..  -D_GNU_SOURCE -D_REENTRANT 
  -D_POSIX_C_SOURCE=200112L -D_POSIX_SOURCE -D_SVID_SOURCE -D_BSD_SOURCE 
  -D_XOPEN_SOURCE=500 -pedantic -Wno-long-long -Wall -fpermissive 
  -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=26 -DNDEBUG  
  -DRLOG_COMPONENT=fusecompress -g -O2   -MT Compress.o -MD -MP -MF 
  .deps/Compress.Tpo -c -o Compress.o Compress.cpp
  In file included from Compress.cpp:21:
  ./boost/archive/portable_binary_iarchive.hpp:242:62: error: 
  boost/archive/impl/archive_pointer_iserializer.ipp: No such file or 
  directory
  In file included from Compress.cpp:22:
  ./boost/archive/portable_binary_oarchive.hpp:232:62: error: 
  boost/archive/impl/archive_pointer_oserializer.ipp: No such file or 
  directory
  In file included from Compress.cpp:21:
  ./boost/archive/portable_binary_iarchive.hpp:269: error: 
  'archive_pointer_iserializer' is not a template
  ./boost/archive/portable_binary_iarchive.hpp:269: error: 
  'archive_pointer_iserializer' in namespace 'boost::archive::detail' does 
  not name a type
  In file included from Compress.cpp:22:
  ./boost/archive/portable_binary_oarchive.hpp:257: error: 
  'archive_pointer_oserializer' is not a template
  ./boost/archive/portable_binary_oarchive.hpp:257: error: 
  'archive_pointer_oserializer' in namespace 'boost::archive::detail' does 
  not name a type
  make[2]: *** [Compress.o] Error 1

serialization 1.40 has an API change and the new interface should be used.
See http://www.boost.org/doc/libs/1_40_0/libs/serialization/doc/release.html

Giridhar

-- 
Y Giridhar Appaji Nag | http://people.debian.org/~appaji/


signature.asc
Description: Digital signature

Bug#545358: system-tools-backends: Interfaces configuration have no effect

[Aldo Vizcaino y Fernando Lopez]

Package: system-tools-backends
Version: 2.6.0-2lenny3
Severity: grave
Tags: patch
Justification: renders package unusable

As for the 2.6.0-2lenny3 version of system-tools-backends we have noted 
network-admin configurations has no effect, for example opening network-admin 
and setting a static ip for a interface has no effect, when we checked 
/etc/network/interfaces it remains unchanged.

It's a bug introduced in the module Ifaces.pm, in the hash containing the 
supported distributions debian is absent.

By adding debian = debian, it can be solved

patch--
--- Ifaces.pm-old   2009-09-03 14:48:07.0 -0300
+++ Ifaces.pm   2009-09-03 14:59:04.0 -0300
@@ -2011,6 +2011,7 @@
gentoo  = gentoo,
freebsd-5   = freebsd-5,
solaris-2.11= solaris-2.11,
+debian  = debian,
   );

  return $dist_map{$Utils::Backend::tool{platform}};
---end of patch

We sorry if the report isn't correct as it is the first time we report a bug.

Greetings, the Lihuen development team (lihuen.linti.unlp.edu.ar).

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

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages system-tools-backends depends on:
ii  adduser   3.110  add and remove users and groups
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libdbus-1-3   1.2.1-5+lenny1 simple interprocess messaging syst
ii  libdbus-glib-1-2  0.76-1 simple interprocess messaging syst
ii  libglib2.0-0  2.16.6-2   The GLib library of C routines
ii  libnet-dbus-perl  0.33.6-1+b1Extension for the DBus bindings

system-tools-backends recommends no packages.

system-tools-backends suggests no packages.

-- 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#543730: SIP 4.8 has a new (non-free?) license

[James Y Knight]

Source: sip4-qt3
Version: 4.8.1-1
Severity: serious

The copyright file in the package contains the license for SIP 4.0 not  
SIP 4.8. (That's a bug in itself...)


The *actual* SIP 4.8 license (contained in the file named LICENSE)  
is substantially different. In particular, it now contains a new clause:

4. Licensee may not use SIP 4.8.1 to generate Python bindings for any
C or C++ library for which bindings are already provided by Riverbank.



As I understand things, this makes the license non-free due to DFSG6  
No Discrimination Against Fields of Endeavor, and furthermore, not  
GPL-compatible.





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

Bug#539151: inotifyx - FTBFS

[Y Giridhar Appaji Nag]

On 09/08/23 15:53 +0200, Bastian Blank said ...
 You seem to have a large missunderstanding how to build Debian packages,
 especially what the difference between arch indenpendent and arch
 dependent is. Also your sponsor (cced) either did not review the

It certainly looks like I did a poor job of reviewing this.  Thank you for
pointing out.

Ritesh, inotifyx being Arch: any should have binary-arch (and not
binary-indep) creating the binary package.  Please make the changes and we can
do another upload fixing this.  Do take a look at policy section 4.9 before
that.

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#527806: exim4-config: fails during postinst sed: -e expression #1, char 2: delimiter ...

[Y Giridhar Appaji Nag]

Package: exim4-config
Version: 4.69-10
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I just did an aptitude update and a dist-upgrade and encountered this error.
Too late in the night to look at where the problem is, please let me know if
you would like me to provide some additional information.  Thank you for your
work on exim.

Errors were encountered while processing:
 exim4-config
 exim4-base
 exim4-daemon-light
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up exim4-config (4.69-10) ...
sed: -e expression #1, char 2: delimiter character is not a single-byte
character
dpkg: error processing exim4-config (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of exim4-base:
 exim4-base depends on exim4-config (= 4.30) | exim4-config-2; however:
  Package exim4-config is not configured yet.
  Package exim4-config-2 is not installed.
  Package exim4-config which provides exim4-config-2 is not configured yet.
dpkg: error processing exim4-base (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of exim4-daemon-light:
 exim4-daemon-light depends on exim4-base (= 4.69); however:
  Package exim4-base is not configured yet.
dpkg: error processing exim4-daemon-light (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-config
 exim4-base
 exim4-daemon-light
Reading package lists... Done 
Building dependency tree   
Reading state information... Done
Reading extended state information  
Initializing package states... Done
Writing extended state information... Done

- -- Package-specific info:
Exim version 4.69 #1 built 02-May-2009 07:56:52
Copyright (c) University of Cambridge 2006
Berkeley DB: Berkeley DB 4.6.21: (September 27, 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'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='satellite'
dc_other_hostnames='loktak.appaji.net'
dc_local_interfaces='127.0.0.1'
dc_readhost='appaji.net'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.appaji.net'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:appaji.net

- -- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages exim4-config depends on:
ii  adduser   3.110  add and remove users and groups
ii  debconf [debconf-2.0] 1.5.26 Debian configuration management sy

exim4-config recommends no packages.

exim4-config suggests no packages.

- -- debconf information:
* exim4/dc_smarthost: mail.appaji.net
  exim4/dc_relay_domains:
  exim4/dc_localdelivery: mbox format in /var/mail/
* exim4/dc_eximconfig_configtype: mail sent by smarthost; no local mail
* exim4/dc_readhost: appaji.net
  exim4/exim4-config-title:
  exim4/dc_relay_nets:
* exim4/mailname: appaji.net
* exim4/dc_local_interfaces: 127.0.0.1
* exim4/dc_minimaldns: false
* exim4/dc_other_hostnames: loktak.appaji.net
  exim4/no_config: true
  exim4/hide_mailname: true
  exim4/dc_postmaster:
* exim4/use_split_config: false

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iQEcBAEBAgAGBQJKBJiKAAoJENbfLHnbvsrcxlwH/Av9vEGatnBsZPWKQKofL+Hp
MpeyADF8kGbRoGjmkp05OfaddkEkXWxT1jqJbojgedcCAYaKu9w2OZ66F6LOvh6C
PICCpGczb6j9QXqm68GQ78d7tNrfgTYpCwuqSdaAsg1FySjzJlaC8UTGxYYK3Q3A
BkvkneJTo7XEuWEdXcZrS4FmpUcs5631KTn7lrKiDaY63Wt05JBeI5BYzzZjOqVq

Bug#526349: elinks: FTBFS on i386 auto build

[Y Giridhar Appaji Nag]

On 09/05/01 13:24 +0300, Kalle Olavi Niemitalo said ...
 We have AsciiDoc 7.1.2 configuration files in the ELinks source
 tree in order to lock the input syntax against AsciiDoc upgrades
 (Debian bug 491820) or user modifications of /etc/asciidoc.
 The AsciiDoc User Guide recommends bundling the asciidoc script
 too (under Shipping stand-alone AsciiDoc source) but I had
 previously assumed I could rely on the script remaining
 compatible with old config files.  So I'll now add the script
 there, and Debian can then replace the asciidoc build-dependency
 with some version of python.

Thank you, that will help.

 This change will go in the elinks-0.12 and master branches.
 Do you need it in elinks-0.11 as well?

No, unless there is a security fix we will not update 0.11.4 in stable
(also, elinks 0.11.4 builds using asciidoc 8.2.7 in Debian -- both in
stable in case someone wants to build it in lenny).

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://people.debian.org/~appaji/


signature.asc
Description: Digital signature

Bug#526835: libcherokee-config0: upgrade from 0.99.11-1 to 0.99.13-1 fails

[y]

Package: libcherokee-config0
Version: 0.99.11-1
Severity: grave
Justification: renders package unusable


Upgrading the package, I get:

=
Preparing to replace libcherokee-config0 0.99.11-1 (using
.../libcherokee-config0_0.99.13-1_i386.deb) ...
Usage: update-python-modules [-v] [-c] package_directory [...]
   update-python-modules [-v] [-c] package.dirs [...]
   update-python-modules [-v] [-a|-f|-p]

update-python-modules: error:
/usr/share/python-support/libcherokee-config0.private is not a directory
dpkg: warning - old pre-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
Usage: update-python-modules [-v] [-c] package_directory [...]
   update-python-modules [-v] [-c] package.dirs [...]
   update-python-modules [-v] [-a|-f|-p]

update-python-modules: error:
/usr/share/python-support/libcherokee-config0.private is not a directory
dpkg: error processing
/var/cache/apt/archives/libcherokee-config0_0.99.13-1_i386.deb (--unpack):
 subprocess new pre-removal script returned error exit status 2
Usage: update-python-modules [-v] [-c] package_directory [...]
   update-python-modules [-v] [-c] package.dirs [...]
   update-python-modules [-v] [-a|-f|-p]

update-python-modules: error:
/usr/share/python-support/libcherokee-config0.private is not a directory
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libcherokee-config0_0.99.13-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
=

Purging and reinstalling results in the same error.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libcherokee-config0 depends on:
ii  libc6 2.9-8  GNU C Library: Shared libraries
ii  libcherokee-base0 0.98.1-1   Cherokee web server - Base librari
ii  libcherokee-client0   0.98.1-1   Cherokee web server - Client libra
ii  libcherokee-server0   0.98.1-1   Cherokee web server - Server libra
ii  libssl0.9.8   0.9.8g-16  SSL shared libraries
ii  python2.5.4-2An interactive high-level object-o

libcherokee-config0 recommends no packages.

libcherokee-config0 suggests no packages.

-- 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#526007: [FFmpeg] libxxx-unstripped should also Provide libxxx

[Yonas Y]

Subject: ffmpeg: libxxx-unstripped should also Provide libxxx
Package: ffmpeg
Version: 3:0.svn20090303-1ubuntu6
Severity: serious
Justification: no longer builds from source

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

Copied from:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/312898


Binary package hint: ffmpeg

libxxx-unstripped should also
Provides: libxxx

so it would possible to have libxxx-dev and libxxx-unstripped installed at
the same time.
Thanks


-- System Information:
Debian Release: 5.0
  APT prefers jaunty-updates
  APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500,
'jaunty')
Architecture: i386 (i686)

Kernel: Linux 2.6.28-11-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ffmpeg depends on:
ii  lib 3:0.svn20090303-1ubuntu2+unstripped1 ffmpeg codec library
ii  lib 3:0.svn20090303-1ubuntu2+unstripped1 ffmpeg device handling library
ii  lib 3:0.svn20090303-1ubuntu6 ffmpeg video filtering library
ii  lib 3:0.svn20090303-1ubuntu2+unstripped1 ffmpeg file format library
ii  lib 3:0.svn20090303-1ubuntu2+unstripped1 ffmpeg utility library
ii  lib 2.9-4ubuntu6 GNU C Library: Shared libraries
ii  lib 3:0.svn20090303-1ubuntu2+unstripped1 ffmpeg video postprocessing
librar
ii  lib 1.2.13-4ubuntu3  Simple DirectMedia Layer
ii  lib 3:0.svn20090303-1ubuntu2+unstripped1 ffmpeg video scaling library

ffmpeg recommends no packages.

ffmpeg suggests no packages.

Bug#494058: epiphany-browser: Download window is broken

[Y Giridhar Appaji Nag]

Hi Sam,

On 08/10/02 17:54 +0100, Sam Morris said ...
 On Thu, 2008-10-02 at 18:36 +0200, Josselin Mouette wrote:
  Le jeudi 02 octobre 2008 à 17:15 +0100, Sam Morris a écrit :
   I can reproduce the hanging problem fairly easily.
   
1. Open Page Info window
2. In a new tab, go to about:config
3. Try to modify a string value
4. Try to close the about:config tab

I understand that with the page info extension in use you are able to
reproduce this consistently, however, are you able to reproduce this bug
as originally stated without epiphany-extensions installed?

The reason I ask is because you also reported #492972 (sev: important)
on epiphany-extensions

And just to be in a position to narrow this down, would you be able to
start with a fresh epiphany install (where you don't have the settings,
the profile etc.) and still reproduce this as you had reported here [1].

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494058#10

I will also try to reproduce this on an AMD64 machine that I got access
to recently.

  To me, this looks like #393837, which is triggered whenever you open a
  chrome window with parameters.
  
  If this issue is related to #393837, that would explain a lot, and
  unfortunately would not ease its fixing...
 
 The backtrace is similar to the one on
 http://bugzilla.gnome.org/show_bug.cgi?id=535127 ... but maybe not
 similar enough now that I look closely.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#502858: aptitude: changelog entry malformed

[Y Giridhar Appaji Nag]

Hi Ben,

On 08/10/20 22:04 +1100, Ben Finney said ...
 Package: aptitude
 Version: 0.4.11.9-1lenny1
 Severity: serious
 Justification: violates Policy §4.4

This part of the policy is a should and not a must.  I'll leave it
to the package maintainer, but I suppose this bug is not serious.  It
would be made must (post #489460 which is not yet released).

 A malformed changelog entry can cause problems for any tools 
 attempting to extract structured information from that changelog. The 

Since the above is a should and not a must, tools doing this must be
prepared [1] to encounter bad entries.

[1] 
http://packages.debian.org/changelogs/pool/main/a/aptitude/current/changelog#versionversion0.4.11.9-1lenny1

One less RC bug if you or Daniel downgrade this :-)

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#502824: Freeze exception for alevt [Was: Re: Bug#502824: fixed in alevt 1:1.6.1-10.1]

[Y Giridhar Appaji Nag]

[did not see an unblock request on debian-release yet for this, hence
the mail]

Hi release team,

On 08/10/20 23:17 +, Chris Lamb said ...
  alevt (1:1.6.1-10.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Add support in postinst for building video4linux devices in /dev/.static 
 as
  well as /dev. (Closes: #502824)

Can you please unblock alevt for this RC bug to let it into Lenny?

Thanks,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#483073: fixed in nant 0.85.dfsg1-5

[Y Giridhar Appaji Nag]

Hi release team,

Can you please unblock nant for #483073

Cheers,

Giridhar

On 08/10/16 22:17 +, Mirco Bauer said ...
  nant (0.85.dfsg1-5) unstable; urgency=low
  .
[ David Paleino ]
* debian/control:
  + Removed Dave Beckett [EMAIL PROTECTED] from Uploaders.
  .
[ Mirco Bauer ]
* debian/control:
  + Enhanced package description.
  + Added Vcs-Browser field.
  + Bumped cli-common-dev build-dep to = 0.5.4 as we are using
dh_clistrip and dh_clifixperms from it.
* debian/rules:
  + Removed -m paramater to dh_clideps call, as it doesn't know such
parameter.
  + Added dh_clistrip and dh_clifixperms calls.
  + Removed find call to fix file permissions, as dh_clifixperms takes now
care of this.
  + Removed dh_shlibdeps call as this package doesn't contain native
binaries or libraries.
  + Delete examples/StyleTask/SimpleExtensionObject/SimpleExtension.dll
before the build to force nant to rebuild it (as the file is shipped in
the tarball).
* debian/patches/005-nant-ExternalProgramBase-race.dpatch:
  + New patch to prevent Mono detection failure due to a race on SMP
machines. Based on upstream fix for bug 1733671 (Closes: #483073)
(thanks goes to Y Giridhar Appaji Nag [EMAIL PROTECTED] for
 investigation and providing the dpatch)

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#501412: ikvm: FTBFS in lenny: Illegal characters in path

[Y Giridhar Appaji Nag]

On 08/10/11 21:51 +0200, Frank Lichtenheld said ...
 On Sat, Oct 11, 2008 at 07:31:52PM +0200, Mirco Bauer wrote:
  Nothing is different (well hardware is), as this is a race-condition
  that happens on SMP systems, see:
  
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483073
  
  Not sure how to proceed here... someone NMU ikvm with the named
  workaround of #483073?
 
 Hmm, if that bug affects many other packages it would probably better
 to get a fixed nant in lenny instead. Upstream claims that it is fixed
 in a newer version, so it would be helpful if someone could try to find
 out how big the patch is.

Got in touch with upstream, will keep the bugs posted.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#501412: ikvm: FTBFS in lenny: Illegal characters in path

[Y Giridhar Appaji Nag]

On 08/10/15 13:04 +0530, Y Giridhar Appaji Nag said ...
 On 08/10/11 21:51 +0200, Frank Lichtenheld said ...
  Hmm, if that bug affects many other packages it would probably better
  to get a fixed nant in lenny instead. Upstream claims that it is fixed
  in a newer version, so it would be helpful if someone could try to find
  out how big the patch is.
 
 Got in touch with upstream, will keep the bugs posted.

I posted a nmudiff to #483073 and it would be great if someone who is
able to reproduce tests the fix before we do an upload.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#500555: tries to access not existing/usr/var/run

[Y Giridhar Appaji Nag]

Hi debian-release,

On 08/10/01 08:31 +0200, Pierre Habouzit said ...
 On Tue, Sep 30, 2008 at 10:54:11AM +, Y Giridhar Appaji Nag wrote:
  
  On 08/09/29 12:26 +0200, Rene Engelhard said ...
   Package: libdaemon0
   Version: 0.10-1
   Severity: grave
  
  Since 0.13 is already in sid and this bug affects 0.12-1 (in Lenny) I
  would like to upload 0.12-1lenny1 to testing-proposed-updates.  Please
  do let me know if that is OK.

(The version numbers should have been 0.12-2 and 0.12-2lenny1.)

 Please do.

Now that libdaemon 0.12-2lenny1 has been built on all architectures, can
someone please push it to testing?

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#500555: tries to access not existing/usr/var/run

[Y Giridhar Appaji Nag]

Hi release-team,

On 08/09/29 12:26 +0200, Rene Engelhard said ...
 Package: libdaemon0
 Version: 0.10-1
 Severity: grave

Since 0.13 is already in sid and this bug affects 0.12-1 (in Lenny) I
would like to upload 0.12-1lenny1 to testing-proposed-updates.  Please
do let me know if that is OK.

 Sep 29 10:02:21 frodo nfschecker[26995]: open(/usr/var/run/nfschecker.pid): 
 No cuch file or directory
 Sep 29 10:02:21 frodo nfschecker[26995]: Could not create PID file (No such 
 file or directory)
 
 Sounds like you miss to specify --with-localstatedir=/var to that it doesn't
 use /usr/var.

The change is as follows:

Index: debian/rules
===
--- debian/rules(revision 11413)
+++ debian/rules(revision 11414)
@@ -28,7 +28,7 @@
 endif
[ ! -f doc/README.html ] || mv -f doc/README.html doc/README.html.ups
[ ! -f doc/README ] || mv -f doc/README doc/README.ups
-   ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) 
--prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info 
CFLAGS=$(CFLAGS) LDFLAGS=-Wl,-z,defs
+   ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) 
--prefix=/usr --localstatedir=/var --mandir=\$${prefix}/share/man 
--infodir=\$${prefix}/share/info CFLAGS=$(CFLAGS) LDFLAGS=-Wl,-z,defs
 
 build: build-stamp
 build-stamp: config.status

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#500555: tries to access not existing/usr/var/run

[Y Giridhar Appaji Nag]

# Bcc: control
tags 500555 + pending
thanks

On 08/09/29 12:26 +0200, Rene Engelhard said ...
 [ seen on 0.13-1 but I have no reason to believe older versions
 are unaffected ]

You are right, from libdaemon/dpid.c:

 #define VARRUN LOCALSTATEDIR /run
 
 const char *daemon_pid_file_ident = NULL;
 daemon_pid_file_proc_t daemon_pid_file_proc = daemon_pid_file_proc_default;

   --localstatedir=DIR modifiable single-machine data [PREFIX/var]
 
 Sounds like you miss to specify --with-localstatedir=/var to that it doesn't
 use /usr/var.

Should just be --localstatedir=/var :)

Thank you for reporting this.  I've committed a fix to svn and an
updated 0.13 package will be uploaded to unstable.  I'll work with the
release team for getting the fix to Lenny via testing-proposed-updates
for 0.12.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#499347: empty /usr/share/doc/elinks

[Y Giridhar Appaji Nag]

Hi release team,

On 08/09/18 00:37 +0200, Julien Cristau said ...
 Package: elinks
 Version: 0.11.4-2
 Severity: serious
 
 elinks seems to want to have its doc dir as a symlink to elinks-data.
 It doesn't handle the transition from previous versions properly,

Can you please Lenny-freeze unblock ELinks for this bug?

Thanks,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#499347: empty /usr/share/doc/elinks

[Y Giridhar Appaji Nag]

# Bcc: control
tags 499347 + confirmed
thanks

On 08/09/18 00:37 +0200, Julien Cristau said ...
 elinks seems to want to have its doc dir as a symlink to elinks-data.
 It doesn't handle the transition from previous versions properly,
 though, so on upgrade you get an empty /usr/share/doc/elinks/ directory.
 Please fix this in your postinst (on upgrade, rmdir and create the
 symlink).

Subtle bug, thank you for the report.  I'll fix this in the next upload.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#494025: FTBFS: ../../../../src/util/time.h:44: error: expected ')' before 'n'

[Y Giridhar Appaji Nag]

# reduce priority because it is a build with DEB_BUILD_OPTIONS and since
# this bug (on 0.11.1-1.2etch1) would block 0.11.4-2 from entering testing.
severity 494025 important
tags 494025 + moreinfo
thanks

On 08/08/06 21:46 +0300, Timo Juhani Lindfors said ...
  from ../../../../src/document/html/renderer.c:13:
 ../../../../src/util/time.h:44: error: expected ')' before 'n'

Can you add #include sys/types.h before #ifdef HAVE_SYS_TIME_H in
src/util/time.h and try to build again?

 Any idea what's wrong?

Not too sure, my etch chroot creation failed and I can't try this out.
Can you please try the above and let me know how this goes?

snip
$ sudo cowbuilder --create --distribution etch
...
P: Unpacking package util-linux
E: Internal error: install
pbuilder: cdebootstrap failed
 - Aborting with an error
 pbuilder create failed
/snip

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#491820: elinks: FTBFS: xmlto input does not validate

[Y Giridhar Appaji Nag]

tags 491820 + confirmed
thanks

On 08/07/22 00:38 -0700, Daniel Schepler said ...
 Document /tmp/buildd/elinks-0.11.4/build-main/doc/elinks.1.xml does not 
 validate
 make[1]: *** [elinks.1] Error 3
 rm elinks.1.xml
 make[1]: Leaving directory `/tmp/buildd/elinks-0.11.4/build-main/doc'
 make: *** [build-indep-stamp] Error 2
 dpkg-buildpackage: failure: debian/rules build gave error exit status 2

Thank you for the report.  I can reproduce this in my pbuilder and I will take
a look.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#487374: FTBFS: Cannnot calculate stack trace

[James Y Knight]

I built this package successfully on amd64 by adding:
DEB_CONFIGURE_EXTRA_FLAGS := --enable-frame-pointers

to debian/rules. I expect that should be conditional upon the arch  
being amd64 but I don't know how to do that.


Unfortunately, the build failures on powerpc and ia64 look to be  
completely different problems.


James



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

Bug#485955: gdb: completely fails to detect frames

[James Y Knight]

Could this be the same bug as:
https://bugzilla.novell.com/show_bug.cgi?id=390722
and
https://bugs.launchpad.net/ubuntu/hardy/+source/gdb/+bug/111869
?
(with patch available)

James



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

Bug#484311: reportbug adds os.curdir to sys.path

[Y Giridhar Appaji Nag]

On 08/06/03 18:26 +0200, Thomas Arendsen Hein said ...
 sys.path = [os.curdir, '/usr/share/reportbug'] + sys.path

It looks like os.curdir has been added to sys.path only for temporary
debugging purposes (code modified in local directory and wanting to test it
without installing reportbug).

Chris, can you confirm that this is case?  We can remove os.curdir or add it
as the last entry in sys.path.

As an aside, I noticed that /usr/share/reportbug is added to sys.path once
again in __main__ in reportbug_submit.py.

And in querybts too:

 27 import sys, os
 28 sys.path = [os.curdir, '/usr/share/reportbug'] + sys.path

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#484311: reportbug adds os.curdir to sys.path

[Y Giridhar Appaji Nag]

# Bcc: control
tags 484311 + patch
thanks

On 08/06/04 16:51 +0530, Y Giridhar Appaji Nag said ...
 Chris, can you confirm that this is case?  We can remove os.curdir or add it
 as the last entry in sys.path.
 
 As an aside, I noticed that /usr/share/reportbug is added to sys.path once
 again in __main__ in reportbug_submit.py.
 
 And in querybts too:

Attached patch.  This can be modified -- the parts in the patch that change
sys.path.append should be removed -- for a minimally modified reportbug for
the security upload queues.

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/
Index: querybts
===
--- querybts	(revision 517)
+++ querybts	(working copy)
@@ -25,7 +25,7 @@
 # $Id: querybts,v 1.7.2.3 2008-04-18 05:38:27 lawrencc Exp $
 
 import sys, os
-sys.path = [os.curdir, '/usr/share/reportbug'] + sys.path
+sys.path = ['/usr/share/reportbug'] + sys.path + [os.curdir]
 
 from reportbug_exceptions import *
 
Index: reportbug_submit.py
===
--- reportbug_submit.py	(revision 517)
+++ reportbug_submit.py	(working copy)
@@ -30,7 +30,7 @@
 from reportbug import VERSION, VERSION_NUMBER
 
 import os
-sys.path = [os.curdir, '/usr/share/reportbug'] + sys.path
+sys.path = ['/usr/share/reportbug'] + sys.path + [os.curdir]
 
 import re
 import commands
@@ -484,7 +484,6 @@
 'o'
 
 if __name__ == '__main__':
-sys.path.append('/usr/share/reportbug')
 try:
 main()
 except KeyboardInterrupt:
Index: reportbug
===
--- reportbug	(revision 522)
+++ reportbug	(working copy)
@@ -1798,7 +1798,6 @@
 return
 
 if __name__ == '__main__':
-sys.path.append('/usr/share/reportbug')
 try:
 main()
 except KeyboardInterrupt:


signature.asc
Description: Digital signature

Bug#478156: elinks_0.12~20080127-3(sparc/experimental): FTBFS: error: assuming signed overflow does not occur when assuming that (X + c) X is always false

[Y Giridhar Appaji Nag]

# Bcc: control
tags 478156 + experimental
thanks

On 08/04/27 17:54 +0200, Frank Lichtenheld said ...
 | cc1: warnings being treated as errors
 | /build/buildd/elinks-0.12~20080127/src/main/event.c: In function 
 'unregister_event_hook':
 | /build/buildd/elinks-0.12~20080127/src/util/math.h:36: error: assuming 
 signed overflow does not occur when assuming that (X + c)  X is always false

Thank you for reporting, let me check.

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#470860: distcc has missing depends on dbus

[Y Giridhar Appaji Nag]

Hi Carsten,

This bug is blocking distcc's migration to testing.   I was wondering if you
would make an upload soon because it has been marked as pending about a month
ago :)

Thank you for your work on distcc.

Cheers,

Giridhar

On 08/03/13 23:13 -0500, Adam Heath said ...
 severity: serious

 After an strace, I discovered the problem.  Installing dbus allowed it  
 to continue.  This might be related to the recent zeroconf patch(the  
 avahi part of the message).

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#464384: FTBFS etc., pending upload

[Y Giridhar Appaji Nag]

For those interested in packages with this bug fixed, the source package
with a fix is available[1], and will be uploaded shortly to the archive
(the package adds two new binary packages with debugging symbols, is NEW
and hence I can't upload it as a DM).

[1] http://mentors.debian.net/debian/pool/main/e/elinks/

Thank you for your patience :)

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#465719: elinks_0.12~20080127-1(experimental/powerpc/anakreon): -Werror and warning: comparison is always true due to limited range of data type

[Y Giridhar Appaji Nag]

# Bcc: control
tags 465719 + pending
thanks

On 08/02/14 10:12 +0100, Marc 'HE' Brockschmidt said ...
 On my ppc buildd, another warning then the one reported in #464384 leads
 to an FTBFS:
 
 | cc1: warnings being treated as errors
 | /build/buildd/elinks-0.12~20080127/src/protocol/bittorrent/peerwire.c: In 
 function 'do_send_bittorrent_peer_message':
 | /build/buildd/elinks-0.12~20080127/src/protocol/bittorrent/peerwire.c:260: 
 warning: comparison is always true due to limited range of data type
 | /build/buildd/elinks-0.12~20080127/src/protocol/bittorrent/peerwire.c:323: 
 warning: case label value is less than minimum value for type
 | make[4]: *** [peerwire.o] Error 1

This (and FTBFSs on arm/s390 because of this warning) are fixed in the
Debian ELinks git, pending upload.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#464384: elinks_0.12~20080127-1(experimental/amd64/xenophanes): -Werror, warning: cast from pointer to integer of different size

[Y Giridhar Appaji Nag]

On 08/02/10 20:55 +0530, Y Giridhar Appaji Nag said ...
 builds should go through fine now I suppose.  I had them tested
 atleast on amd64 and powerpc.  I'll request an upload.

Hopefully around the weekend, I'll be added to the DM keyring and we
will do an upload after an initial DM-Upload-Allowed: yes upload is
done.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#464384: elinks_0.12~20080127-1(experimental/amd64/xenophanes): -Werror, warning: cast from pointer to integer of different size

[Y Giridhar Appaji Nag]

On 08/02/10 11:37 +0200, Kalle Olavi Niemitalo said ...
 Thank you.  I pushed the following patch, which should fix these.
 
 commit 61019c31304f89141248b0381974d1e3886cf160

Thank you KON.  I pushed changes based on these to alioth git.  The
builds should go through fine now I suppose.  I had them tested atleast
on amd64 and powerpc.  I'll request an upload.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#464384: elinks_0.12~20080127-1(experimental/amd64/xenophanes): -Werror, warning: cast from pointer to integer of different size

[Y Giridhar Appaji Nag]

On 08/02/09 00:39 +0200, Kalle Olavi Niemitalo said ...
 I see amd64 has given these warnings already in ELinks 0.11.3,
 but there they didn't break the build, because configure was not
 run with --enable-debug and so it did not add -Werror to $CFLAGS.

Enabled debugging because this package is for experimental and
features.conf suggested it.

I added a patch to modify bittorrent_peer_request to change the id from
char to enum bittorrent_message_id.  We FTBFS on powerpc[1] and s390[2]
otherwise.

[1] 
http://experimental.debian.net/fetch.php?pkg=elinksver=0.12%7E20080127-1arch=powerpcstamp=1202132370file=logas=raw
[2] 
http://experimental.debian.net/fetch.php?pkg=elinksver=0.12%7E20080127-1arch=s390stamp=1202495801file=logas=raw

However, I don't have a non-x86 box to test any of these.  I suspect
FTBFSs may be a frequent occurance with 0.12 because of -Werror (And I
suppose -Werror for the unreleased versions of ELinks is present with
--enable-debug for a reason).

 Please try the appended patch.
 
 There has been a similar warning in src/network/ssl/socket.c, at
 the gnutls_transport_set_ptr call.  That could also be silenced

I picked both the patches but didn't request an upload yet.  I will try
and find someone who can do these builds and then request for an upload.

Thank you.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#464384: elinks_0.12~20080127-1(experimental/amd64/xenophanes): -Werror, warning: cast from pointer to integer of different size

[Y Giridhar Appaji Nag]

On 08/02/10 09:38 +0530, Y Giridhar Appaji Nag said ...
 I added a patch to modify bittorrent_peer_request to change the id from
 char to enum bittorrent_message_id.  We FTBFS on powerpc[1] and s390[2]
 otherwise.

I submitted the patch at http://bugzilla.elinks.cz/show_bug.cgi?id=1002

There are further warnings down the line that cause build failures (this
is for AMD64).

make[4]: Entering directory 
`/tmp/buildd/elinks-0.12~20080127/build-main/src/protocol/smb'
  [CC]   src/protocol/smb/smb2.o
cc1: warnings being treated as errors
/tmp/buildd/elinks-0.12~20080127/src/protocol/smb/smb2.c: In function 'do_smb':
/tmp/buildd/elinks-0.12~20080127/src/protocol/smb/smb2.c:352: warning: format 
'%lld' expects type 'long long int', but argument 3 has type '__off_t'
make[4]: *** [smb2.o] Error 1

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#460858: more info: segfault error while loading NIC driver

[Nick Y Kuzminyh]

Dear support team member,
I've failed to find install log file.
I see the following message every time linux boot:
---
Jan 10 12:22:57 mitek kernel: Intel(R) PRO/1000 Network Driver - version 
7.1.9-k4-NAPI
Jan 10 12:22:57 mitek kernel: Copyright (c) 1999-2006 Intel Corporation.
Jan 10 12:22:57 mitek kernel: vbetool[2733]: segfault at 10e0 rip 
004248df rsp 7fff9e76b480 error 4
---
(this is a fragment of kern.log)
Processor is Intel Core2Duo.
NIC driver seems to be identified correctly (e1000 kernel module)


-- 
Best regards,
 Nick  mailto:[EMAIL PROTECTED]




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

Bug#460598: nxtvepg 2.8.0 needs to be patched for tcl/tk 8.5

[y]

Package: nxtvepg
Version: 2.7.6-1
Severity: serious
Tags: patch
Justification: no longer builds from source

nxtvepg 2.8.0 needs the attached patch to work with thread-enabled
tcl/tk 8.5. Without the patch it will crash at startup with SIGSEGV.
The patch was created by nxtvepg upstream author.


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

Kernel: Linux 2.6.23.1-3enrico
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nxtvepg depends on:
ii  libc6 2.7-5  GNU C Library: Shared libraries
ii  libx11-6  2:1.0.3-7  X11 client-side library
ii  libxmu6   1:1.0.3-1  X11 miscellaneous utility library
ii  tcl8.58.5.0-2Tcl (the Tool Command Language) v8
ii  tk8.5 8.5.0-1Tk toolkit for Tcl and X11, v8.5 -

nxtvepg recommends no packages.

-- no debconf information
--- /tmp/nxtvepg-2.8.0/epgui/epgmain.c	2007-12-31 17:34:42.0 +0100
+++ epgui/epgmain.c	2008-01-13 18:31:35.976371505 +0100
@@ -2163,15 +2163,15 @@ int main( int argc, char *argv[] )

if ( IS_GUI_MODE(mainOpts) || IS_DUMP_MODE(mainOpts) )
{
+  // initialize Tcl interpreter and compile all scripts
+  // Tk is only initialized if a GUI will be opened
+  ui_init(argc, argv, IS_GUI_MODE(mainOpts));
+
   #ifndef WIN32
   exitAsyncHandler = Tcl_AsyncCreate(AsyncHandler_AppTerminate, NULL);
   signalAsyncHandler = Tcl_AsyncCreate(AsyncHandler_Signalled, NULL);
   #endif

-  // initialize Tcl interpreter and compile all scripts
-  // Tk is only initialized if a GUI will be opened
-  ui_init(argc, argv, IS_GUI_MODE(mainOpts));
-
   encIso88591 = Tcl_GetEncoding(interp, iso8859-1);

   RcFile_Init();

Bug#457260: Can't use meld anymore

[Y Giridhar Appaji Nag]

severity 457149 grave
retitle 457149 should depend on python-gnomecanvas and python-gconf
reassign 457260 python-gnome2
merge 457149 457260
thanks

On 07/12/24 11:28 +0530, Y Giridhar Appaji Nag said ...
 The fix for this bug would be to add a dependency on
 python-gnomecanvas and python-gconf.

Actually, it is python-gnome that needs to add a dependency.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#451432: ifplugd: FTBFS on amd64: Conflicting types for loff_t

[Y Giridhar Appaji Nag]

tags 451432 +patch
thanks

Adapting a patch from Ubuntu (which was likely tested on AMD64).  I
don't have a non-i386 sid, it would be good if someone can give this a
spin and comment here.  Please feel free to do an NMU if you can test
this (not just for the FTBFS, but an 'install and use' test).

Giridhar

On 07/11/15 17:26 -0500, Daniel Schepler said ...
 In file included from interface.c:27:
 /usr/include/sys/types.h:46: error: conflicting types for 'loff_t'
 /usr/include/linux/types.h:30: error: previous declaration of 'loff_t' was 
 here

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur original/ifplugd-0.28/debian/control ifplugd/ifplugd-0.28/debian/control
--- original/ifplugd-0.28/debian/control	2007-11-21 15:59:07.0 +0530
+++ ifplugd/ifplugd-0.28/debian/control	2007-11-22 12:31:56.518739000 +0530
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Oliver Kurth [EMAIL PROTECTED]
-Build-Depends: debhelper ( 4.1.16), libdaemon-dev (= 0.7), lynx | lynx-ssl, pkg-config, po-debconf
+Build-Depends: debhelper ( 4.1.16), dpatch, libdaemon-dev (= 0.7), lynx | lynx-ssl, pkg-config, po-debconf
 Standards-Version: 3.6.1
 
 Package: ifplugd
diff -Nur original/ifplugd-0.28/debian/patches/00list ifplugd/ifplugd-0.28/debian/patches/00list
--- original/ifplugd-0.28/debian/patches/00list	1970-01-01 05:30:00.0 +0530
+++ ifplugd/ifplugd-0.28/debian/patches/00list	2007-11-22 12:39:39.75292 +0530
@@ -0,0 +1 @@
+01_loff_t_dev_t_conflict
diff -Nur original/ifplugd-0.28/debian/patches/01_loff_t_dev_t_conflict.dpatch ifplugd/ifplugd-0.28/debian/patches/01_loff_t_dev_t_conflict.dpatch
--- original/ifplugd-0.28/debian/patches/01_loff_t_dev_t_conflict.dpatch	1970-01-01 05:30:00.0 +0530
+++ ifplugd/ifplugd-0.28/debian/patches/01_loff_t_dev_t_conflict.dpatch	2007-11-22 12:40:55.94687 +0530
@@ -0,0 +1,31 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 01_loff_t_dev_t_conflict.dpatch from Jeremie Corbier [EMAIL PROTECTED]
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Fixes FTBFS: Conflict between sys/types.h linux/types.h loff_t/dev_t
+
[EMAIL PROTECTED]@
+diff -urNad ifplugd-0.28~/src/interface.c ifplugd-0.28/src/interface.c
+--- ifplugd-0.28~/src/interface.c	2005-01-04 16:25:31.0 -0800
 ifplugd-0.28/src/interface.c	2007-01-12 19:19:14.0 -0800
+@@ -23,7 +23,6 @@
+ #endif
+ 
+ #include linux/sockios.h
+-#include linux/if_ether.h
+ #include sys/types.h
+ #include sys/socket.h
+ #include sys/ioctl.h
+diff -urNad ifplugd-0.28~/src/interface.h ifplugd-0.28/src/interface.h
+--- ifplugd-0.28~/src/interface.h	2004-05-09 16:20:56.0 -0700
 ifplugd-0.28/src/interface.h	2007-01-12 19:19:45.0 -0800
+@@ -21,6 +21,9 @@
+  * Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
+  */
+ 
++/* From linux/if_ether.h */
++#define ETH_ALEN 6
++
+ int interface_auto_up;
+ int interface_do_message;
+ 
diff -Nur original/ifplugd-0.28/debian/rules ifplugd/ifplugd-0.28/debian/rules
--- original/ifplugd-0.28/debian/rules	2007-11-21 15:59:07.0 +0530
+++ ifplugd/ifplugd-0.28/debian/rules	2007-11-22 12:09:59.116953000 +0530
@@ -5,6 +5,8 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+include /usr/share/dpatch/dpatch.make
+
 # These are used for cross-compiling and for saving the configure script
 # from having to guess our platform (since we know it already)
 DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
@@ -21,7 +23,7 @@
 	INSTALL_PROGRAM += -s
 endif
 
-config.status: configure
+config.status: patch configure
 	dh_testdir
 	# Add here commands to configure the package.
 	./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --sysconfdir=/etc
@@ -43,7 +45,7 @@
 
 	touch build-stamp
 
-clean:
+clean: unpatch
 	dh_testdir
 	dh_testroot
 	rm -f build-stamp 


signature.asc
Description: Digital signature

Bug#446693: uclibc: should this package be orphaned?

[Y Giridhar Appaji Nag]

severity 446693 normal
reassign 446693 ftp.debian.org
merge 446693 438738
thanks

On 07/10/15 00:26 +0200, Lucas Nussbaum said ...
 If you think that it should be removed from Debian instead of being
 orphaned, please reply to this bug and tell so.

See #438738

 If you agree that it should be orphaned, sending the following commands
 to [EMAIL PROTECTED] should do it (after replacing nn with
 this bug's number):

See #418808

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#430328: ldbl128 transition for alpha, powerpc, sparc, s390

[Y Giridhar Appaji Nag]

A dummy upload to close this bug will rebuild the package, and this bug
can be closed.  There aren't any libraries in splint that need renaming
as suggested.

Giridhar

On 07/06/23 15:49 +0200, Matthias Klose said ...
 This package has been indentified as one with header files in
 /usr/include matching 'long *double'. Please close this bug report
 if it is a false positive, or rename the package accordingly.

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#367727: jukebox-mercury: must use invoke-rc.d

[Y Giridhar Appaji Nag]

tags 367727 +patch
thanks

On 06/05/18 00:21 +0300, Lars Wirzenius said ...
 As of Debian Policy Manual version 3.7.2, the use of invoke-rc.d to
 run init.d scripts has been made mandatory. Earlier, its use was

Patch attached to fix this.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur jukebox-mercury-0.1/debian/postinst 
jukebox-mercury-0.1.new/debian/postinst
--- jukebox-mercury-0.1/debian/postinst 2003-12-11 18:44:50.0 +0530
+++ jukebox-mercury-0.1.new/debian/postinst 2007-09-12 11:15:55.60840 
+0530
@@ -7,7 +7,11 @@
 fi
 
 if [ -e /dev/mercury -a -e /dev/mercury-1 -a -e /dev/mercury-2 ]; then
-   /etc/init.d/$prog start
+  if which invoke-rc.d /dev/null 21; then
+invoke-rc.d $prog start
+  else
+ /etc/init.d/$prog start
+  fi
 else
echo This program needs some manual configuration.  In /dev create 
symlinks for the
echo following targets:
diff -Nur jukebox-mercury-0.1/debian/prerm jukebox-mercury-0.1.new/debian/prerm
--- jukebox-mercury-0.1/debian/prerm2003-12-11 18:44:50.0 +0530
+++ jukebox-mercury-0.1.new/debian/prerm2007-09-12 11:17:26.156969000 
+0530
@@ -3,7 +3,11 @@
 prog=jukebox-mercury
 
 if [ -x /etc/init.d/$prog ]; then
-   /etc/init.d/$prog stop
+  if which invoke-rc.d /dev/null 21; then
+invoke-rc.d $prog stop
+  else
+ /etc/init.d/$prog stop
+  fi
 fi
 
 #DEBHELPER#


signature.asc
Description: Digital signature

Bug#367760: libtowitoko2: must use invoke-rc.d

[Y Giridhar Appaji Nag]

tags 367760 +patch
thanks

On 06/05/18 00:21 +0300, Lars Wirzenius said ...
 As of Debian Policy Manual version 3.7.2, the use of invoke-rc.d to
 run init.d scripts has been made mandatory. Earlier, its use was

Patch attached to fix this.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur towitoko-2.0.7/debian/libtowitoko2.postinst 
towitoko-2.0.7.new/debian/libtowitoko2.postinst
--- towitoko-2.0.7/debian/libtowitoko2.postinst 2007-09-12 10:58:38.0 
+0530
+++ towitoko-2.0.7.new/debian/libtowitoko2.postinst 2007-09-12 
11:18:33.997124000 +0530
@@ -59,7 +59,11 @@
   db_stop
 
   if [ -x /etc/init.d/pcscd ]; then
-invoke-rc.d pcscd restart 3/dev/null
+if which invoke-rc.d /dev/null 21; then
+  invoke-rc.d pcscd restart 3/dev/null
+else
+  /etc/init.d/pcscd restart 3/dev/null
+fi
   fi
 fi
 
diff -Nur towitoko-2.0.7/debian/libtowitoko2.postrm 
towitoko-2.0.7.new/debian/libtowitoko2.postrm
--- towitoko-2.0.7/debian/libtowitoko2.postrm   2007-09-12 10:58:38.0 
+0530
+++ towitoko-2.0.7.new/debian/libtowitoko2.postrm   2007-09-12 
11:19:46.766151000 +0530
@@ -23,7 +23,11 @@
 # restart pcscd (PCSC daemon) if the package is installed
 # and if pcscd is running
 if [ -x /etc/init.d/pcscd ]; then
-  invoke-rc.d pcscd restart 3/dev/null || true
+  if which invoke-rc.d /dev/null 21; then
+invoke-rc.d pcscd restart 3/dev/null || true
+  else
+/etc/init.d/pcscd restart 3/dev/null || true
+  fi
 fi
 
 ;;


signature.asc
Description: Digital signature

Bug#367753: xpilot-ng-server: must use invoke-rc.d

[Y Giridhar Appaji Nag]

tags 367753 +patch
thanks

On 06/05/18 00:21 +0300, Lars Wirzenius said ...
 As of Debian Policy Manual version 3.7.2, the use of invoke-rc.d to
 run init.d scripts has been made mandatory. Earlier, its use was

Patch attached to fix this.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur xpilot-ng-4.7.2/debian/xpilot-ng-server.postinst 
xpilot-ng-4.7.2.new/debian/xpilot-ng-server.postinst
--- xpilot-ng-4.7.2/debian/xpilot-ng-server.postinst2007-09-12 
10:58:36.0 +0530
+++ xpilot-ng-4.7.2.new/debian/xpilot-ng-server.postinst2007-09-12 
11:21:51.368801000 +0530
@@ -64,7 +64,11 @@
 # we customize the prerm and therefore run dh_installinit --noscripts.
 if [ -x /etc/init.d/xpilot-ng-server ]; then
 update-rc.d xpilot-ng-server defaults /dev/null
-invoke-rc.d xpilot-ng-server start
+if which invoke-rc.d /dev/null 21; then
+invoke-rc.d xpilot-ng-server start
+else
+/etc/init.d/xpilot-ng-server start
+fi
 fi
 
 #DEBHELPER#


signature.asc
Description: Digital signature

Bug#367762: gnudip: must use invoke-rc.d

[Y Giridhar Appaji Nag]

tags 367762 +patch
thanks

On 06/05/18 00:21 +0300, Lars Wirzenius said ...
 As of Debian Policy Manual version 3.7.2, the use of invoke-rc.d to
 run init.d scripts has been made mandatory. Earlier, its use was

Patch attached to fix this.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur gnudip-2.1.1/debian/postinst gnudip-2.1.1.new/debian/postinst
--- gnudip-2.1.1/debian/postinst2007-09-12 10:58:38.0 +0530
+++ gnudip-2.1.1.new/debian/postinst2007-09-12 11:14:12.632102000 +0530
@@ -247,7 +247,7 @@
 
 # Set up the init.d stuff...
 system (update-rc.d gnudip defaults 99 49 /dev/null)  die update-rc.d;
-system (/etc/init.d/gnudip start)  die Cannot start gnudip;
+system (if which invoke-rc.d /dev/null 21; then invoke-rc.d gnudip start; 
else /etc/init.d/gnudip start; fi)  die Cannot start gnudip;
 
 exit 0;
 


signature.asc
Description: Digital signature

Bug#441954: icedove: When collecting email, it crashes.

[Y Giridhar Appaji Nag]

merge 441951 441954
thanks

On 07/09/12 16:50 +1000, Robert Moonen said ...
 When collecting email, it collects the email from the server, but
 doesn't delete it from the server, it crashes before/or while doing

Looks like your earlier email did go through.
See http://bugs.debian.org/441951

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Bug#348263: dict-jargon: use invoke-rc.d

[Y Giridhar Appaji Nag]

tags 348263 +patch
thanks

On 06/01/16 01:36 +0200, Lars Wirzenius said ...
 postinst
 script runs /etc/init.d/dictd directly instead of using invoke-rc.d. If
 it used invoke-rc.d, which calls the policy-rc.d that piuparts sets up,
 it wouldn't even try to run the init.d script

Attached patch to fix this.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur dict-jargon-4.4.4/debian/postinst 
dict-jargon-4.4.4.new/debian/postinst
--- dict-jargon-4.4.4/debian/postinst   2007-09-11 18:44:04.0 +0530
+++ dict-jargon-4.4.4.new/debian/postinst   2007-09-11 18:53:37.766613000 
+0530
@@ -7,7 +7,11 @@
 case $1 in 
  configure)
  if [ -x /usr/sbin/dictdconfig ]; then dictdconfig -w ;fi
- if [ -x /etc/init.d/dictd ]; then /etc/init.d/dictd restart;fi
+ if which invoke-rc.d /dev/null 21; then
+  invoke-rc.d dictd restart
+ else
+  /etc/init.d/dictd restart
+ fi
  exit 0
  ;;
 
diff -Nur dict-jargon-4.4.4/debian/postrm dict-jargon-4.4.4.new/debian/postrm
--- dict-jargon-4.4.4/debian/postrm 2007-09-11 18:44:04.0 +0530
+++ dict-jargon-4.4.4.new/debian/postrm 2007-09-11 18:54:15.79369 +0530
@@ -5,7 +5,11 @@
 case $1 in 
 remove|purge)
  if [ -x /usr/sbin/dictdconfig ]; then dictdconfig -w ;fi
- if [ -x /etc/init.d/dictd ]; then /etc/init.d/dictd restart;fi
+ if which invoke-rc.d /dev/null 21; then
+  invoke-rc.d dictd restart
+ else
+  /etc/init.d/dictd restart
+ fi
 
  exit 0
  ;;


signature.asc
Description: Digital signature

Bug#430755: libpam-smbpass: fails when pam tries to use it for password syncing/migration.

[y]

Package: libpam-smbpass
Version: 3.0.25a-1
Severity: grave
Justification: renders package unusable


when enabled in the /etc/pam.d/common-[auth|password], and then trying 
to change a users password it fails with pam complaining about unknown 
module.  The errors shown in the log auth.log are as follows:

Jun 28 03:57:58 silverbox passwd[4381]: PAM unable to resolve symbol: 
pam_sm_chauthtok
Jun 28 03:57:58 silverbox passwd[4381]: PAM unable to resolve symbol: 
pam_sm_authenticate
Jun 28 03:57:58 silverbox passwd[4381]: PAM unable to resolve symbol: 
pam_sm_setcred
Jun 28 03:57:58 silverbox passwd[4381]: PAM unable to resolve symbol: 
pam_sm_chauthtok

This problem does not occur in the current stable version: 3.0.24-6

The current unstable version 3.0.25a-2 also suffers from this 
problem/regression.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash


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

Bug#422452: bzr-svn missing dependancy on python-pysqlite2

[James Y Knight]

Package: bzr-svn
Version: 0.3.2-1
Severity: serious
Justification: Policy 3.5

*** Please type your report below this line ***
Running 'bzr branch' emits:
Needs at least Python2.5 or Python2.4 with the pysqlite2 module
Unable to load plugin 'svn' from '/usr/lib/python2.4/site-packages/ 
bzrlib/plugins'


And indeed, bzr-svn is unusable.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (700, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1.1381_FC3smp
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages bzr-svn depends on:
ii  bzr 0.15-1   bazaar-ng, the next- 
generation dis
ii  python  2.4.4-2  An interactive high- 
level object-o
ii  python-central  0.5.12   register and build  
utility for Pyt
ii  python-subversion   1.4.2dfsg1-2 Python bindings for  
Subversion
ii  python2.4   2.4.4-3  An interactive high- 
level object-o


bzr-svn recommends no packages.



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

Bug#400558: gtkpod: dumps core on startup (*** glibc detected *** double free or corruption (out): 0x0850e280 ***)

[Y Giridhar Appaji Nag]

Package: gtkpod
Version: 0.99.4-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

gtkpod aborts with SIGABRT due to glibc detected double free (happes
when not run from within gdb also).

$ gdb /usr/bin/gtkpod
GNU gdb 6.5-debian
Copyright (C) 2006 Free Software Foundation, Inc.

[snip...]

Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.

(gdb) r
Starting program: /usr/bin/gtkpod
(no debugging symbols found)

[snip...]

[New Thread 998194096 (LWP 6201)]
*** glibc detected *** double free or corruption (out): 0x0850e138 ***

Program received signal SIGABRT, Aborted.
[Switching to Thread 995096288 (LWP 6197)]
0xe410 in __kernel_vsyscall ()
(gdb) q
The program is running.  Exit anyway? (y or n) y
$
$ 

Like in #326007, I will try and provide more information by running a
debug version.

Giridhar

- --
Y Giridhar Appaji Nag | http://www.appaji.net/

- -- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gtkpod depends on:
ii  libatk1.0-01.12.3-1  The ATK accessibility toolkit
ii  libc6  2.3.6.ds1-8   GNU C Library: Shared libraries
ii  libcairo2  1.2.4-4   The Cairo 2D vector graphics libra
ii  libfontconfig1 2.4.1-2   generic font configuration library
ii  libglade2-01:2.6.0-2 library to load .glade files at ru
ii  libglib2.0-0   2.12.4-2  The GLib library of C routines
ii  libgpod0   0.4.0-0.3 a library to read and write songs 
ii  libgtk2.0-02.8.20-3  The GTK+ graphical user interface 
ii  libid3tag0 0.15.1b-8 ID3 tag reading library from the M
ii  libpango1.0-0  1.14.8-2  Layout and rendering of internatio
ii  libx11-6   2:1.0.3-4 X11 client-side library
ii  libxcursor11.1.7-4   X cursor management library
ii  libxext6   1:1.0.1-2 X11 miscellaneous extension librar
ii  libxi6 1:1.0.1-3 X11 Input extension library
ii  libxinerama1   1:1.0.1-4.1   X11 Xinerama extension library
ii  libxml22.6.27.dfsg-1 GNOME XML library
ii  libxrandr2 2:1.1.0.2-4   X11 RandR extension library
ii  libxrender11:0.9.1-3 X Rendering Extension client libra
ii  zlib1g 1:1.2.3-13compression library - runtime

gtkpod recommends no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFam7l4eu+pR04mIcRAsW5AKCNnbSyJYxHGyJBQFL0I/XrZErrNQCffWlv
BHNPHoGYFSg55geKEH1C4uY=
=LdKX
-END PGP SIGNATURE-


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

Bug#329667: mozilla-thunderbird --compose executes shell commands

[Y Giridhar Appaji Nag]

merge 329664 329667
thanks

On 05/09/22 17:27 +0200, Florian Weimer said ...
 Package: mozilla-thunderbird
 Version: 1.0.6-3
 Severity: grave
 Tags: security
 
 The --compose option executes shell commands:
 
   mozilla-thunderbird --compose 'mailto:`df`'
 
 The df output appears in the To: line of the message.
 
 (This is related to the recently disclosed Firefox bug, which does not
 seem to affect Debian thanks to a different wrapper script.)

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


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

Bug#326007: imapfilter: Immediately aborts with *** glibc detected *** corrupted double-linked list: 0xb7d84218 ***

[Y Giridhar Appaji Nag]

Further information on this.

I build the lua50 debian packages and imapfilter without dh_strip from
the apt-gotten source packages in debian and these are some findings.

On 05/09/05 18:12 +0530, Y Giridhar Appaji Nag - Debian said ...
 On 05/09/01 09:35 +0200, Ulf Rompe said ...
  
  imapfilter dies after setting up an imap connection:
 
 In my case, it dies much before that.  Looks like just after initiating
 a CAPABILITY transaction.
 
 I will do some more tests, try and compile with debugging symbols and
 run this under gdb to provide more data.

S (6): * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL 
ACL2=UNION] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc.  See 
COPYING for distribution information.
C (6): 1000 CAPABILITY
*** glibc detected *** corrupted double-linked list: 0x402de218 ***

Program received signal SIGABRT, Aborted.
0x401d29e7 in raise () from /lib/tls/libc.so.6
(gdb) bt
#0  0x401d29e7 in raise () from /lib/tls/libc.so.6
#1  0x401d431b in abort () from /lib/tls/libc.so.6
#2  0x40209365 in __fsetlocking () from /lib/tls/libc.so.6
#3  0x4020f50c in malloc_usable_size () from /lib/tls/libc.so.6
#4  0x402105ab in free () from /lib/tls/libc.so.6
#5  0x40211901 in calloc () from /lib/tls/libc.so.6
#6  0x40258679 in re_compile_pattern () from /lib/tls/libc.so.6
#7  0x4025bc96 in re_compile_pattern () from /lib/tls/libc.so.6
#8  0x4025ebeb in regexec () from /lib/tls/libc.so.6
#9  0x0804e62a in check_tag ()
#10 0x0804e812 in response_generic ()
#11 0x0804e8ea in response_capability ()
#12 0x0804dbf1 in request_login ()
#13 0x0804ada4 in ifcore_login ()
#14 0x40051d41 in luaD_precall (L=0x8083e50, func=0x8082d74) at ldo.c:260
#15 0x4006200a in luaV_execute (L=0x8083e50) at lvm.c:627
#16 0x400522ae in luaD_call (L=0x8083e50, func=0x8082d44, nResults=-1) at 
ldo.c:313
#17 0x4004c8a6 in f_call (L=0x8083e50, ud=0x0) at lapi.c:672
#18 0x40051923 in luaD_rawrunprotected (L=0x8083e50, f=0x4004c880 f_call, 
ud=0xba74) at ldo.c:88
#19 0x4005290c in luaD_pcall (L=0x8083e50, func=0x4004c880 f_call, 
u=0xba74, old_top=0, ef=0) at ldo.c:416
#20 0x4004dce8 in lua_pcall (L=0x8083e50, nargs=0, nresults=0, errfunc=0) at 
lapi.c:685
#21 0x0804cfb6 in start_lua ()
#22 0x0804c91c in main ()
(gdb)

I placed breakpoints at each of the above function calls and ran
commands to check for memory corruption at that point using mcheck

[snip...]
(gdb) b luaD_precall
Function luaD_precall not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 9 (luaD_precall) pending.
(gdb) b ifcore_login
Breakpoint 10 at 0x804acb8
(gdb) b request_login
Breakpoint 11 at 0x804dadb
(gdb) b response_capability
Breakpoint 12 at 0x804e8db
[snip...]

Followed by ...

[snip...]
(gdb) command 9
Type commands for when breakpoint 9 is hit, one per line.
End with a line saying just end.
call mcheck(0)
continue
end
(gdb) command 10
Type commands for when breakpoint 10 is hit, one per line.
End with a line saying just end.
call mcheck(0)
continue
end
(gdb) command 11
Type commands for when breakpoint 11 is hit, one per line.
End with a line saying just end.
call mcheck(0)
continue
end
(gdb) command 12
Type commands for when breakpoint 12 is hit, one per line.
End with a line saying just end.
call mcheck(0)
continue
end
[snip...]

And ran it again.  This is what happens:

(gdb) r -v -c ~/.imapfilter/lists.lua
[snip...]
Breakpoint 24, luaD_precall (L=0x809a420, func=0x80992b0) at ldo.c:223
223   ptrdiff_t funcr = savestack(L, func);
$54 = 0

Breakpoint 24, luaD_precall (L=0x809a420, func=0x809928c) at ldo.c:223
223   ptrdiff_t funcr = savestack(L, func);
$55 = 0

Breakpoint 10, 0x0804acb8 in ifcore_login ()
$56 = 0

Breakpoint 11, 0x0804dadb in request_login ()
$57 = 0
block freed twice

Program received signal SIGABRT, Aborted.
0x401d29e7 in raise () from /lib/tls/libc.so.6
(gbd)

So looks like there is a double free in request_login.

(gdb) l request_login
No line number known for request_login.
(gdb) f 12
#12 0x0804db93 in request_login ()
(gdb) l
685   status = luaD_pcall(L, f_call, c, savestack(L, c.func), func);
686   lua_unlock(L);
687   return status;
688 }
689
690
691 /*
692 ** Execute a protected C call.
693 */
694 struct CCallS {  /* data to `f_Ccall' */
(gdb)

But that shows up the last call for which the source was available.  I'll
try to figure out which package the request_login function is from and then
send in more updates.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


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

Bug#326007: imapfilter: Immediately aborts with *** glibc detected *** corrupted double-linked list: 0xb7d84218 ***

[Y Giridhar Appaji Nag]

On 05/09/06 16:46 +0530, Y Giridhar Appaji Nag - Debian said ...
 
 I'll try to figure out which package the request_login function is
 from and then send in more updates.

Uggh!  It is the imapfilter sources that have request_login func.  The
CFLAGS that would be set by having DEB_BUILD_OPTIONS define debug are
being overridden by the Makefile.dpath

 26  MYCFLAGS = -Wall -O
 27  MYLDFLAGS =
 28 @@ -14,7 +14,7 @@
 29  CFLAGS = $(MYCFLAGS) $(DEFS) $(INCDIRS)
 30  LDFLAGS = $(MYLDFLAGS) $(LIBDIRS)

It should be CFLAGS += $(MYCFLAGS) ...

Anyways,

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


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

Bug#326007: imapfilter: Immediately aborts with *** glibc detected *** corrupted double-linked list: 0xb7d84218 ***

[Y Giridhar Appaji Nag]

On 05/09/06 16:46 +0530, Y Giridhar Appaji Nag - Debian said ...
 
 try to figure out which package the request_login function is from and
 then send in more updates.

[snip...]
Breakpoint 7, request_login (server=0x80ad750 mail.appaji.net, user=0x80a9f70 
[EMAIL PROTECTED], pass=0x80a20c0 , port=0, ssl=0x80a9fb0 tls1)
at request.c:51
51  if ((s = session_find(server, user)))
$80 = 0
block freed twice

Program received signal SIGABRT, Aborted.
0x401d29e7 in raise () from /lib/tls/libc.so.6
(gdb) bt
#0  0x401d29e7 in raise () from /lib/tls/libc.so.6
#1  0x401d431b in abort () from /lib/tls/libc.so.6
#2  0x40209365 in __fsetlocking () from /lib/tls/libc.so.6
#3  0x402093a4 in __libc_fatal () from /lib/tls/libc.so.6
#4  0x40214bc7 in __default_morecore () from /lib/tls/libc.so.6
#5  0x4021541c in mcheck_check_all () from /lib/tls/libc.so.6
#6  0x4020fe55 in free () from /lib/tls/libc.so.6
#7  0x0804d666 in xfree (ptr=0xb698) at memory.c:54
#8  0x0804a9ca in check_cert (pcert=0x80dda30,
pmd=0xb688 [EMAIL PROTECTED],
pmdlen=0xb684) at cert.c:126
#9  0x0804a7ce in get_cert (ssn=0x0) at cert.c:46
#10 0x0804fa6b in open_secure_connection (ssn=0x80a9818, protocol=0x80a9fb0 
tls1) at socket.c:115
#11 0x0804f95a in open_connection (ssn=0x80a9818, server=0x80ad750 
mail.appaji.net, port=993, sprotocol=0x80a9fb0 tls1) at socket.c:67
#12 0x0804db93 in request_login (server=0x80ad750 mail.appaji.net, 
user=0x80a9f70 [EMAIL PROTECTED], pass=0x80a20c0 , port=993, ssl=0x80a9fb0 
tls1)
at request.c:69
#13 0x0804ada4 in ifcore_login (lua=0x809a420) at core.c:100
#14 0x40051d41 in luaD_precall (L=0x809a420, func=0x8099298) at ldo.c:260
#15 0x4006200a in luaV_execute (L=0x809a420) at lvm.c:627
#16 0x400522ae in luaD_call (L=0x809a420, func=0x809925c, nResults=-1) at 
ldo.c:313
#17 0x4004c8a6 in f_call (L=0x809a420, ud=0x0) at lapi.c:672
#18 0x40051923 in luaD_rawrunprotected (L=0x809a420, f=0x4004c880 f_call, 
ud=0xba54) at ldo.c:88
#19 0x4005290c in luaD_pcall (L=0x809a420, func=0x4004c880 f_call, 
u=0xba54, old_top=0, ef=0) at ldo.c:416
#20 0x4004dce8 in lua_pcall (L=0x809a420, nargs=0, nresults=0, errfunc=0) at 
lapi.c:685
#21 0x0804cfb6 in start_lua () at lua.c:61
#22 0x0804c91c in main (argc=4, argv=0xbb44) at imapfilter.c:114
(gdb) f 8
#8  0x0804a9ca in check_cert (pcert=0x80dda30,
pmd=0xb688 [EMAIL PROTECTED],
pmdlen=0xb684) at cert.c:126
126 xfree(certf);
(gdb) l
121 }
122
123 fclose(fd);
124 X509_free(cert);
125
126 xfree(certf);
127
128 return r;
129 }
130
(gdb) l check_cert
[snip...]
95
96  if (!exists_file(certf))
97  return 0;
98
99  fd = fopen(certf, r);
(gdb)
100
101 xfree(certf);
102
103 if (fd == NULL)
104 return -1;
[snip...]
122
123 fclose(fd);
124 X509_free(cert);
125
126 xfree(certf);

So the problem here is that we are xfree-ing certf twice, once at line
101 and again on line 126.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


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

Bug#326007: imapfilter: Immediately aborts with *** glibc detected *** corrupted double-linked list: 0xb7d84218 ***

[Y Giridhar Appaji Nag]

tags 326007 + patch
thanks

On 05/09/06 18:22 +0530, Y Giridhar Appaji Nag - Debian said ...
 (gdb) f 8
 #8  0x0804a9ca in check_cert (pcert=0x80dda30,
 pmd=0xb688 [EMAIL PROTECTED],
 pmdlen=0xb684) at cert.c:126
 126 xfree(certf);
 (gdb) l
 121 }
 122
 123 fclose(fd);
 124 X509_free(cert);
 125
 126 xfree(certf);
 127
 128 return r;
 129 }
 130
 (gdb) l check_cert
 [snip...]
 95
 96  if (!exists_file(certf))
 97  return 0;
 98
 99  fd = fopen(certf, r);
 (gdb)
 100
 101 xfree(certf);
 102
 103 if (fd == NULL)
 104 return -1;
 [snip...]
 122
 123 fclose(fd);
 124 X509_free(cert);
 125
 126 xfree(certf);
 
 So the problem here is that we are xfree-ing certf twice, once at line
 101 and again on line 126.

The following patch will fix this issue.  It also fixes another minor
memory leak in case the certificates file doesn't exist.

--- cert.c.orig 2005-09-06 18:28:37.64823 +0530
+++ cert.c  2005-09-06 18:28:45.185932000 +0530
@@ -93,8 +93,10 @@
certf = (char *)xmalloc((n + 1) * sizeof(char));
snprintf(certf, n + 1, %s/%s, env.home, PATHNAME_CERTS);
 
-   if (!exists_file(certf))
+   if (!exists_file(certf)) {
+   xfree(certf);
return 0;
+   }
 
fd = fopen(certf, r);
 
@@ -123,8 +125,6 @@
fclose(fd);
X509_free(cert);
 
-   xfree(certf);
-
return r;
 }
 

Ulf, can you please check if it works for you as well?

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


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

Bug#316664: icon: FTBFS with new dpkg

[Y Giridhar Appaji Nag]

On 05/08/07 00:28 +0530, Y Giridhar Appaji Nag said ...
 
 The attached patch takes care of this.  It uses Colin Watson's tip for

There was an error in the previous patch.  The debian name for GNU CPU
name x86_64 is amd64.  New patch file icon-9.4.2.patch316664-1.txt with
the said correction attached.

--- icon-9.4.2.patch316664.txt  2005-08-07 02:43:03.0 +0530
+++ icon-9.4.2.patch316664-1.txt2005-08-07 02:47:53.0
+0530
@@ -60,7 +60,7 @@
  CFLAGS_OPT = -O0
  endif
 -ifeq $(DEB_HOST_GNU_CPU) x86_64
-+ifeq $(DEB_HOST_ARCH_CPU) x86_64
++ifeq $(DEB_HOST_ARCH_CPU) amd64
  CFLAGS_OPT = -O0
  endif

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur icon-9.4.2.orig/debian/rules icon-9.4.2/debian/rules
--- icon-9.4.2.orig/debian/rules2005-08-07 00:15:25.0 +0530
+++ icon-9.4.2/debian/rules 2005-08-07 00:15:55.0 +0530
@@ -3,43 +3,58 @@
 # Do we make rt.a into an ELF library?
 # Do we make iconx link with xpm.so?
 
-DEB_HOST_GNU_SYSTEM := $(shell dpkg-architecture -qDEB_HOST_GNU_SYSTEM)
-DEB_HOST_GNU_CPU := $(shell dpkg-architecture -qDEB_HOST_GNU_CPU)
+DEB_HOST_ARCH_OS := $(shell dpkg-architecture -qDEB_HOST_ARCH_OS 2/dev/null)
+DEB_HOST_ARCH_CPU := $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU 2/dev/null)
+
+# Take account of old dpkg-architecture output.
+
+ifeq ($(DEB_HOST_ARCH_CPU),)
+  DEB_HOST_ARCH_CPU := $(shell dpkg-architecture -qDEB_HOST_GNU_CPU)
+  ifeq ($(DEB_HOST_ARCH_CPU),x86_64)
+DEB_HOST_ARCH_CPU := amd64
+  endif
+endif
+ifeq ($(DEB_HOST_ARCH_OS),)
+  DEB_HOST_ARCH_OS := $(subst -gnu,,$(shell dpkg-architecture 
-qDEB_HOST_GNU_SYSTEM))
+  ifeq ($(DEB_HOST_ARCH_OS),gnu)
+DEB_HOST_ARCH_OS := hurd
+  endif
+endif
 
 CFLAGS_OPT = -O2
 
-ifeq $(DEB_HOST_GNU_CPU) alpha
+ifeq $(DEB_HOST_ARCH_CPU) alpha
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) hppa
+ifeq $(DEB_HOST_ARCH_CPU) hppa
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) ia64
+ifeq $(DEB_HOST_ARCH_CPU) ia64
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) mips
+ifeq $(DEB_HOST_ARCH_CPU) mips
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) mipsel
+ifeq $(DEB_HOST_ARCH_CPU) mipsel
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) powerpc
+ifeq $(DEB_HOST_ARCH_CPU) powerpc
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) s390
+ifeq $(DEB_HOST_ARCH_CPU) s390
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) sparc
+ifeq $(DEB_HOST_ARCH_CPU) sparc
 CFLAGS_OPT = -O0
 endif
-ifeq $(DEB_HOST_GNU_CPU) x86_64
+ifeq $(DEB_HOST_ARCH_CPU) amd64
 CFLAGS_OPT = -O0
 endif
 
-ifneq (, $(filter $(DEB_HOST_GNU_SYSTEM), linux kfreebsd-gnu knetbsd-gnu))
+ifneq (, $(filter $(DEB_HOST_ARCH_OS), linux kfreebsd-gnu knetbsd-gnu))
 system = linux
 else
-system = $(DEB_HOST_GNU_SYSTEM)
+system = $(DEB_HOST_ARCH_OS)
 endif
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))

Bug#318539: grub: FTBFS: Invalid storage class for function

[Y Giridhar Appaji Nag]

On 05/07/15 20:31 -0700, Daniel Schepler said ...
 builtins.c: In function 'blocklist_func':
 builtins.c:145: error: invalid storage class for function 
 'disk_read_blocklist_func'
 builtins.c:145: warning: no previous prototype for 'disk_read_blocklist_func'
 builtins.c: In function 'color_func':
 builtins.c:609: error: invalid storage class for function 'color_number'
 builtins.c:609: warning: no previous prototype for 'color_number'

There were multiple issues in getting grub compiled with gcc 4.0.  The
patches and explanation for some of these included here.

1. static vars in smp-imps.c are extern in smp-imps.h and smp-imps.h is
#included in smp-imps.c.

2. subfuctions used in builtins.c, char_io.c, device.c and asmstub.c are
static.  The savedefault_helper should be declared before use.

3. console_current_color variable is extern from term.h but declared as
static and initialised in asmstub.c

gcc4.0 doesn't allow any of these with the current flags used to compile
grub.

smp-imps.diff, static_subfunc.diff and console_current_color.diff fix
the above three respectively.  And can be included from debian/patches
with 00list.patch applied.

However, there are a few more issues:

1. -fwritable-strings is used by grub ...

and from ChangeLog

1999-03-26  OKUJI Yoshinori  [EMAIL PROTECTED]
[snip]
* grub/Makefile.am (CPPFLAGS): Use -fwritable-strings, because
grub assumes that all strings resides at the data section.

... but gcc 4.0 no longer accepts the -fwritable-strings option.  It is
recommended that character arrays be used for writable strings.

With the above patches applied I was able to compile, and after removing
-fwritable-strings from {grub,stage2}/Makefile.{am,in}, I managed to
successfully build a grub_0.95+cvs20040624-17_i386.deb using
'dpkg-buildpackage -B -uc -rfakeroot'.

2. 'dpkg-buildpackage -b -uc -rfakeroot' doesn't work inspite of the
above patches.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur grub-0.95+cvs20040624.orig/stage2/smp-imps.c 
grub-0.95+cvs20040624/stage2/smp-imps.c
--- grub-0.95+cvs20040624.orig/stage2/smp-imps.c2001-12-11 
13:19:16.0 +0530
+++ grub-0.95+cvs20040624/stage2/smp-imps.c 2005-08-07 03:25:57.0 
+0530
@@ -246,19 +246,45 @@
 };
 
 /*
- *  Exported globals here.
+ *  Private globals here.
+ */
+
+/*
+ *  imps_any_new_apics is non-zero if any of the APICS (local or I/O)
+ *  are *not* an 82489DX.  This is useful to determine if more than 15
+ *  CPUs can be supported (true if zero).
  */
 
 static int imps_any_new_apics = 0;
-#if 0
-volatile int imps_release_cpus = 0;
-#endif
+
+/*
+ *  imps_enabled is non-zero if the probe sequence found IMPS
+ *  information and was successful.
+ */
+
 static int imps_enabled = 0;
-static int imps_num_cpus = 1;
+
+/*
+ *  This contains the local APIC hardware address.
+ */
+
 static unsigned imps_lapic_addr = ((unsigned) (lapic_dummy)) - LAPIC_ID;
+
+/*
+ *  This represents the number of CPUs found.
+ */
+
+static int imps_num_cpus = 1;
+
+/*
+ *  These map from virtual cpu numbers to APIC id's and back.
+ */
 static unsigned char imps_cpu_apic_map[IMPS_MAX_CPUS];
 static unsigned char imps_apic_cpu_map[IMPS_MAX_CPUS];
 
+#if 0
+volatile int imps_release_cpus = 0;
+#endif
 
 /*
  *  MPS checksum function
diff -Nur grub-0.95+cvs20040624.orig/stage2/smp-imps.h 
grub-0.95+cvs20040624/stage2/smp-imps.h
--- grub-0.95+cvs20040624.orig/stage2/smp-imps.h1999-06-24 
05:33:28.0 +0530
+++ grub-0.95+cvs20040624/stage2/smp-imps.h 2005-08-07 03:25:57.0 
+0530
@@ -177,41 +177,6 @@
 unsigned char dest_apic_intin;
   };
 
-
-/*
- *  Exported globals here.
- */
-
-/*
- *  imps_any_new_apics is non-zero if any of the APICS (local or I/O)
- *  are *not* an 82489DX.  This is useful to determine if more than 15
- *  CPUs can be supported (true if zero).
- */
-extern int imps_any_new_apics;
-
-/*
- *  imps_enabled is non-zero if the probe sequence found IMPS
- *  information and was successful.
- */
-extern int imps_enabled;
-
-/*
- *  This contains the local APIC hardware address.
- */
-extern unsigned imps_lapic_addr;
-
-/*
- *  This represents the number of CPUs found.
- */
-extern int imps_num_cpus;
-
-/*
- *  These map from virtual cpu numbers to APIC id's and back.
- */
-extern unsigned char imps_cpu_apic_map[IMPS_MAX_CPUS];
-extern unsigned char imps_apic_cpu_map[IMPS_MAX_CPUS];
-
-
 /*
  *  This is the primary function for probing for Intel MPS 1.1/1.4
  *  compatible hardware and BIOS information.  While probing the CPUs
--- grub-0.95+cvs20040624.orig/stage2/builtins.c2005-08-07 
03:40:20.0 +0530
+++ grub-0.95+cvs20040624/stage2/builtins.c 2005-08-07 03:39:26.0 
+0530
@@ -141,7 +141,7 @@
 
   /* Collect contiguous blocks into one entry as many as possible,
  and print the blocklist notation on the screen.  */
-  static void disk_read_blocklist_func (int sector, int offset, int length)
+  void

Bug#320270: FTBFS: Invalid lvalues in assignments

[Y Giridhar Appaji Nag]

tags 320270 + patch

On 05/07/27 07:58 -0700, Matt Kraai said ...
 
 brutefir fails to build because it contains invalid lvalues in
 assignments:

The attached patch fixes this.  The variables in structure declarations
have been marked as the right type and the type-cast in the lvalue has
been removed in this patch.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/
diff -Nur brutefir-1.0c.orig/bfio_jack.c brutefir-1.0c/bfio_jack.c
--- brutefir-1.0c.orig/bfio_jack.c  2005-01-04 13:52:41.0 +0530
+++ brutefir-1.0c/bfio_jack.c   2005-08-07 07:19:52.0 +0530
@@ -30,7 +30,7 @@
 #define DEFAULT_CLIENTNAME brutefir
 
 static bool_t debug;
-static bool_t stopped = false;
+static volatile bool_t stopped = false;
 static bool_t has_started = false;
 static struct jack_state *handles[2][BF_MAXCHANNELS];
 static void **states[2];
@@ -102,13 +102,13 @@
sizeof(jack_default_audio_sample_t));
 }
 }
-(volatile bool_t)stopped = true;
+stopped = true;
 return -1;
 }
 frames_left = process_cb(states, n_handles, iobufs, n_frames,
  BF_CALLBACK_EVENT_NORMAL);
 if (frames_left == -1) {
-(volatile bool_t)stopped = true;
+stopped = true;
 return -1;
 }
 
@@ -454,7 +454,7 @@
 bfio_synch_stop(void)
 {
 if (!(volatile bool_t)stopped) {
-(volatile bool_t)stopped = true;
+stopped = true;
 jack_client_close(client);
 }
 }
diff -Nur brutefir-1.0c.orig/bflogic_eq.c brutefir-1.0c/bflogic_eq.c
--- brutefir-1.0c.orig/bflogic_eq.c 2005-01-04 13:52:41.0 +0530
+++ brutefir-1.0c/bflogic_eq.c  2005-08-07 07:29:15.0 +0530
@@ -39,8 +39,8 @@
 int band_count;
 int taps;
 int coeff[2];
-int active_coeff;
-bool_t not_changed;
+volatile int active_coeff;
+volatile bool_t not_changed;
 double *freq;
 double *mag;
 double *phase;
@@ -113,7 +113,7 @@
 active = c[(volatile int)equalisers[n].active_coeff];
 if (*coeff == c[0] || *coeff == c[1]) {
 *coeff = active;
-(volatile bool_t)equalisers[n].not_changed = false;
+equalisers[n].not_changed = false;
 }
 }
 }
diff -Nur brutefir-1.0c.orig/bfrun.c brutefir-1.0c/bfrun.c
--- brutefir-1.0c.orig/bfrun.c  2005-01-04 13:52:41.0 +0530
+++ brutefir-1.0c/bfrun.c   2005-08-07 07:25:39.0 +0530
@@ -96,19 +96,19 @@
 
 
 struct intercomm_area {
-bool_t doreset_overflow;
+volatile bool_t doreset_overflow;
 int sync[BF_MAXPROCESSES];
-uint32_t period_us[BF_MAXPROCESSES];
-double realtime_index;
+volatile uint32_t period_us[BF_MAXPROCESSES];
+volatile double realtime_index;
 struct bffilter_control fctrl[BF_MAXFILTERS];
 struct bfoverflow overflow[BF_MAXCHANNELS];
 uint32_t ismuted[2][BF_MAXCHANNELS/32];
-int delay[2][BF_MAXCHANNELS];
-int n_pids;
-pid_t pids[BF_MAXPROCESSES];
-int exit_status;
-bool_t full_proc[BF_MAXPROCESSES];
-bool_t ignore_rtprio;
+volatile int delay[2][BF_MAXCHANNELS];
+volatile int n_pids;
+volatile pid_t pids[BF_MAXPROCESSES];
+volatile int exit_status;
+volatile bool_t full_proc[BF_MAXPROCESSES];
+volatile bool_t ignore_rtprio;
 
 struct {
 uint64_t ts_start;
@@ -496,7 +496,7 @@
 if (delay  0 || delay  bfconf-maxdelay[io][channel]) {
return -1;
 }
-(volatile int)icomm-delay[io][channel] = delay;
+icomm-delay[io][channel] = delay;
 
 if (bfconf-n_virtperphys[io][physch] == 1) {
return dai_change_delay(io, physch, delay);
@@ -601,7 +601,7 @@
 }
 
 if ((volatile bool_t)icomm-doreset_overflow) {
-(volatile bool_t)icomm-doreset_overflow = false;
+icomm-doreset_overflow = false;
 memset(overflow, 0, sizeof(struct bfoverflow) *
bfconf-n_channels[OUT]);
 }
@@ -631,7 +631,7 @@
 pinfo(rti: not full processing - no rti update\n);
 }
 }
-(volatile double)icomm-realtime_index = max_rti;
+icomm-realtime_index = max_rti;
 check_overflows(overflow);
 lastprinttime = tt;
 }
@@ -1324,10 +1324,10 @@
 if (bit_find(partial_proc, 0, n_filters - 1) == -1) {
 timersub(period_end, period_start, tv);
 period_length = tv.tv_sec * 100 + tv.tv_usec;
-(volatile uint32_t)icomm-period_us[process_index] = period_length;
-(volatile bool_t)icomm-full_proc[process_index] = true;
+icomm-period_us[process_index] = period_length;
+icomm-full_proc[process_index] = true;
 } else {
-(volatile bool_t)icomm-full_proc[process_index] = false;
+icomm-full_proc[process_index] = false;
 }
 gettimeofday(period_start, NULL);
 
@@ -2078,9 +2078,9 @@
 memset(icomm-debug, 0xFF, sizeof(icomm-debug));
 memcpy

Bug#318728: Please mention in nonvulns/woody

[Y Giridhar Appaji Nag]

On 05/07/23 11:44 +, Alexander Sack said ...
 Helge Kreutzmann wrote:
 
  before closing this bug (once sarge and sid are updated) please add
  the CANs to http://www.debian.org/security/nonvulns-woody

 Yes, but how? Never have done so before.

I would assume one needs to edit the
webwml/english/security/nonvulns-woody.src file from  the CVS repository
cvs.debian.org:/cvs/webwml and commit that.  One needs to apply for CVS
write access.

More details at
http://www.debian.org/devel/website/
http://www.debian.org/devel/website/working
http://www.debian.org/devel/website/using_cvs

I don't know how this works, but doesn't the security team add the CANs
to the nonvulns files?

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


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

Bug#310420: kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3

[Y Giridhar Appaji Nag]

Package: kernel-image-2.6.11-1-686
Version: 2.6.11-5
Severity: grave
Justification: renders package unusable

I upgraded from 2.6.11-3 to 2.6.11-5 (dist-upgrade) and the kernel fails
to boot with error messages indicating that a few files cannot be found.

The transcripts of upgrade sessions and the error messages while booting
follow:

$ agdu
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Done
The following packages will be upgraded:
  kernel-image-2.6.11-1-686
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/15.9MB of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 90899 files and directories currently installed.)
Preparing to replace kernel-image-2.6.11-1-686 2.6.11-3 (using 
.../kernel-image-2.6.11-1-686_2.6.11-5_i386.deb) ...
The directory /lib/modules/2.6.11-1-686 still exists. Continuing as directed.
Unpacking replacement kernel-image-2.6.11-1-686 ...
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /vmlinuz-2.6.11-1-686
Found kernel: /vmlinuz-2.6.10-1-686
Found kernel: /vmlinuz-2.4.18-bf2.4
Found kernel: /memtest86.bin
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst ... done

Setting up kernel-image-2.6.11-1-686 (2.6.11-5) ...
dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table === is 
this ok?
dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table === is 
this ok?
Not touching initrd symlinks since we are being reinstalled (2.6.11-3)
Not updating image symbolic links since we are being updated (2.6.11-3)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /vmlinuz-2.6.11-1-686
Found kernel: /vmlinuz-2.6.10-1-686
Found kernel: /vmlinuz-2.4.18-bf2.4
Found kernel: /memtest86.bin
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst ... done

While booting (messages hand typed - I did not find a way to capture
these as the boot process failed):

[snip]
hda: Host Protected Area disabled.
hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4  p5 p6 p7 p8 p9 p10 p11 p12 p13 
p14 p15 
Kernel can not convert a name into desc number
Check your 'root=' argument passed on boot by bootloader.
initrd-tools: 0.1.80
/sbin/init: 360: cannot open bin/root: no such file
umount: bin: not mounted
/sbin/init: 362: cannot create proc/sys/kernel/real-root-dev: Directory non 
existant
cat: proc/cmdline: No such file or directory
umount: proc not mounted
[snip]

After this, the messages from 'Kernel can not...' are repeated in a loop.

-- 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-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages kernel-image-2.6.11-1-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  fileutils 5.2.1-2The GNU file management utilities 
ii  initrd-tools  0.1.80 tools to create initrd image for p
ii  module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo

-- no debconf information


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

Bug#310420: kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3

[Y Giridhar Appaji Nag]

On 05/05/23 18:49 +0530, Giridhar - Debian said ...
 
 [snip]
 hda: Host Protected Area disabled.
 hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4  p5 p6 p7 p8 p9 p10 p11 p12 
 p13 p14 p15 
 Kernel can not convert a name into desc number
 Check your 'root=' argument passed on boot by bootloader.
 initrd-tools: 0.1.80
 /sbin/init: 360: cannot open bin/root: no such file
 umount: bin: not mounted
 /sbin/init: 362: cannot create proc/sys/kernel/real-root-dev: Directory non 
 existant
 cat: proc/cmdline: No such file or directory
 umount: proc not mounted
 [snip]

I don't know the complete boot process and how initrd works, but I have
included some more information related to the initrd.img in the and the
above error messages:

$ sudo mount /boot/initrd.img-2.6.11-1-686 -o loop /mnt/c
$ pwd
/mnt/c
$ ls bin/root
ls: bin/root: No such file or directory
$ ls proc/sys/kernel/real-root-dev
ls: proc/sys/kernel/real-root-dev: No such file or directory
$ ls proc/cmdline
ls: proc/cmdline: No such file or directory

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


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

Bug#307095: mesag3: error processing package: trying to overwrite `/usr/lib/libGLU.so.1.3.060201

[Monique Y. Mudama]

Package: mesag3
Version: 6.2.1-3
Severity: grave
Justification: renders package unusable


When upgrading package through aptitude, I get the following message:

Preparing to replace mesag3 6.2.1-3 (using .../mesag3_6.2.1-4_i386.deb) ...
Unpacking replacement mesag3 ...
dpkg: error processing /var/cache/apt/archives/mesag3_6.2.1-4_i386.deb 
(--unpack):
 trying to overwrite `/usr/lib/libGLU.so.1.3.060201', which is also in package 
libglu1-mesa
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/mesag3_6.2.1-4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ack!  Something bad happened while installing packages.  Trying to recover:


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-6.toadstool
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages mesag3 depends on:
ii  libc62.3.2.ds1-21GNU C Library: Shared libraries an
ii  libglu1-mesa [libglu 6.2.1-3 The OpenGL utility library (GLU)
ii  libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li
ii  libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte
ii  xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu

-- no debconf information


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

Bug#305179: preinst returned error exit status 1 (sed: -e expression #1, char 48: Extra characters after command)

[Y Giridhar Appaji Nag]

Package: zsh
Version: 4.2.5-3
Severity: grave

When I try to install zsh version 4.2.5-3 (latest in unstable), the
installation fails in the pre-installation script with the following
error.

# sudo apt-get install zsh
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  zsh-doc
The following packages will be upgraded:
  zsh
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/2035kB of archives.
After unpacking 1696kB of additional disk space will be used.
(Reading database ... 89512 files and directories currently installed.)
Preparing to replace zsh 4.0.4-33 (using .../archives/zsh_4.2.5-3_i386.deb) ...
sed: -e expression #1, char 48: Extra characters after command
dpkg: error processing /var/cache/apt/archives/zsh_4.2.5-3_i386.deb (--unpack):
 subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/zsh_4.2.5-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This happened originally when I was trying to do a dist-upgrade when the
version of zsh was 4.2.4-7.  I 'apt-get remove --purge'd that version of
zsh and tried to install the versions 4.2.5-3 and 4.2.5-1 of the package
and failed with the same error. 4.0.4-33 installation succeeded and then
an upgrade to either 4.2.5-1 or 4.2.5-3 fails.

Giridhar

PS: The above install log shows an upgrade from 4.0.4-33 because I did
not find 4.2.4-7 at http://http.us.debian.org/debian/pool/main/z/zsh/ so
I downloaded 4.2.5-1 (which failed) and then 4.0.4-33 (which succeeded)
and tried to install 4.2.5-3, which failed.

--
Y Giridhar Appaji Nag

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)


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