On Sun, Dec 17, 2006 at 02:48:24PM +0100, Marco d'Itri wrote:
On Dec 16, Sven Luther [EMAIL PROTECTED] wrote:
Well, i never dealt with udev, i have not even the faintest idea where to
start, and the initramfs-tools or d-i environment i have to play with is
really not all that user
On Monday 18 December 2006 12:25, Baruch Even wrote:
Did you load the module for your processor? you need load kvm-intel or
kvm-amd depending on what your CPU is.
Hmm!! I hoped the kvm module should have taken care of that.
Anyway. I manually loaded the kvm and kvm-intel module with which the
If you helped me out with compilation of the package, I think I could
gather some more info.
Following the Debian reference Sec. 2.2.12 , I did:
su
apt-get source fontconfig
dpkg-source -x fontconfig_2.4.2-1.dsc
cd fontconfig-2.4.2
dpkg-buildpackage
But the last command fails with
On Mon, 2006-12-18 at 08:49 +0100, Leszek Koltunski wrote:
If you helped me out with compilation of the package, I think I could
gather some more info.
Ok, let's try building just the raw upstream package; trust me, there
aren't any significant debian changes outside of the configuration
Guillem Jover [EMAIL PROTECTED] writes:
tags 403216 - patch
thanks
On Fri, 2006-12-15 at 13:26:41 +0100, Goswin von Brederlow wrote:
Package: dpkg-dev
Version: 1.13.24
Severity: critical
File: /usr/bin/dpkg-shlibdeps
Tags: patch
Er, there's not patch in here... and I think the proposed
tajwan:~/tmp/orig-source/fontconfig-2.4.2/fc-cache# ../libtool
--mode=execute gdb fc-cache
GNU gdb 6.5-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it
Norbert Preining [EMAIL PROTECTED] wrote:
On Sam, 16 Dez 2006, Frank Küster wrote:
THis name change is currently under discussion in the tex-live
(upstream) mailing list with the original authors participating. As soon
as we have come to a conclusion there it will be executed in Debian.
retitle 400923 multi-gnome-terminal: $DISPLAY variable not set from the
--display argument
thanks
I've just rebuilt the package. Forgot to close a bug.
--
GNU/Linux registered user #224950
Proud Egyptian GNU/Linux User Group www.eglug.org Member.
Life powered by Debian, Homepage:
Processing commands for [EMAIL PROTECTED]:
retitle 400923 multi-gnome-terminal: $DISPLAY variable not set from the
--display argument
Bug#400923: gdm: $DISPLAY variable not set
Changed Bug title.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
after
apt-get source fontconfig
dpkg-source -x fontconfig_2.4.2-1.dsc
I already can see a directory named 'fontconfig-2.4.2' . This is the
source with all Debian patches applied, right? If I compile that the
'./configure ...' way, fc-cache also doesn't crash.
Looks like the package
... php5-xcache failed to build on all
architectures; it doesn't seem to be compatible with php 5.2 without
modifications.
Yes, any many upstream releases have been made over the past four
months that provide many bugfixes and full PHP 5.2 support.
See
maximilian attems a écrit :
reassign rootskel
stop
On Tue, 12 Dec 2006, sferriol wrote:
Package: libklibc-dev
Version: 1.4.30-2
Severity: normal
in d-i, building rootskel/src-bootfloppy/bin/timeout_read.c failed
on alpha, amd64, ia64, s390
undefined reference to '__FD_ZERO'
Am Freitag, den 15.12.2006, 14:39 +0100 schrieb Markus Dahms:
I made two patches which resolve the problem for me, one fixes
magic_compile(), the other one magic_check():
Sorry, you were too slow.
All the problems are missing initializations, there can be many more of
these bugs in the code
Package: libattr1
Version: 2.4.35-1
Severity: serious
Justification: make other packages FTBFS
There has been a regression on your package since 2.4.32-1.
When building gnu-fdisk yesterday for instance, it went fine. However,
today with 2.4.35-1, I got:
make[3]: Entering directory
Aurelien Jarno ha scritto:
reopen 403379
thanks
Sorry, but I still have the same problem. Also a debdiff show no code
change between this version and the previous one.
I forgot to copy the patch from my -debug tree to my -build tree
before debuild (damn it)
the patch is not on this PC, but
gregor herrmann wrote:
On Sat, 16 Dec 2006 10:55:34 +0100, Julien Danjou wrote:
There was a problem while autobuilding your package:
t/01-epoll...Can't bind : IO::Socket::INET: Bad protocol 'udp'
I've fixed this bug by adding netbase to Build-Depends-Indep in our
svn repository.
Package: libattr1
Version: 2.4.35-1
Severity: Serious
Tags: sid
Long directory listings does not work any longer:
ls: OK
ls -l:
ls: relocation error: /lib/libacl.so.1: symbol getxattr, version
ATTR_1.0 not defined in file libattr.so.1 with link time reference
Reverting to
Your message dated Mon, 18 Dec 2006 14:47:36 +0500
with message-id [EMAIL PROTECTED]
and subject line Closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen
Moreover:
*The scsi-idle patch (for 2.6 kernels) provides only a silly IOCTL for finding
out the time since the last disk access. The same information can be
extracted by monitoring /sys/block/sda/stat, with sufficient accuracy for the
indented application (spinning down hard disks).
*The
On Mon, 2006-12-18 at 10:07 +0100, Leszek Koltunski wrote:
after
apt-get source fontconfig
dpkg-source -x fontconfig_2.4.2-1.dsc
I already can see a directory named 'fontconfig-2.4.2' . This is the
source with all Debian patches applied, right? If I compile that the
'./configure ...'
Package: libattr1
Version: 2.4.35-1
Severity: critical
Justification: breaks unrelated software
Since upgrade of libattr1 ls -l returns the error in the subject:
$ ls -dl /
ls: relocation error: /lib/libacl.so.1: symbol getxattr, version ATTR_1.0 not
defined in file libattr.so.1 with link time
On Mon, 18 Dec 2006 00:33:58 +0100
Bill Allombert [EMAIL PROTECTED] wrote:
What worry me about the patch is the fact that create_lock() and
check_dpkglock() are not performed in the same order. In particular, if
create_lock() fail we exit with error 0 instead of 1 thus maybe
On Mon, 18 Dez 2006, Frank Küster wrote:
No, we don't have any problems (for etch):
- aleph has been removed and will probably be reintroduced as afnix
Good.
- octave uses /usr/bin/mex2.1
True, I already have removed the conflict some time ago, but forgot it
;-)
We should, however,
* Kiko Piris ([EMAIL PROTECTED]) [061218 11:08]:
Package: libattr1
Version: 2.4.35-1
Severity: critical
Justification: breaks unrelated software
Since upgrade of libattr1 ls -l returns the error in the subject:
$ ls -dl /
ls: relocation error: /lib/libacl.so.1: symbol getxattr,
Processing commands for [EMAIL PROTECTED]:
clone 403585 -1
Bug#403585: Regression in 2.4.35-1
Bug 403585 cloned as bug 403599.
reassign -1 libacl1
Bug#403599: Regression in 2.4.35-1
Bug reassigned from package `libattr1' to `libacl1'.
found -1 2.2.42-1
Bug#403599: Regression in 2.4.35-1
Bug
CFLAGS=-g or CFLAGS='' does not make any difference.
But here's another clue: now I noticed that the
fontconfig-2.4.2/fc-cache/fc-cache I was tracing with gdb is really a
wrapper script that just runs fontconfig-2.4.2/fc-cache/.libs/lt-fc-cache.
If I run that 'lt-fc-cache' directly, it also
clone 403585 -1
reassign -1 libacl1
found -1 2.2.42-1
retitle -1 Regression in 2.2.42-1
thanks
On Mon, Dec 18, 2006 at 10:29:54AM +0100, Aurélien GÉRÔME wrote:
Package: libattr1
Version: 2.4.35-1
Severity: serious
Justification: make other packages FTBFS
There has been a regression on your
Is there some easy way I can reproduce this? Format a disk with LUKS
on one PC, connect it to the slug and do what exactly to trigger the
corruption?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Package: tex-common
Version: 0.42
Severity: serious
Justification: fails to install
I get the following while trying to install tex-common:
Setting up tex-common (0.42) ...
cp: relocation error: /lib/libacl.so.1: symbol getxattr, version ATTR_1.0 not
defined in file libattr.so.1 with link
Your message dated Mon, 18 Dec 2006 11:02:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403319: fixed in libdanga-socket-perl 1.55-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Mon, 18 Dec 2006 11:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403320: fixed in libsys-syscall-perl 0.22-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Processing commands for [EMAIL PROTECTED]:
reopen 394392
Bug#394392: msync() in recent kernels fails LSB
Bug reopened, originator not changed.
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Package: exim4-config
Version: 4.63-11
Severity: grave
Justification: email was bounced, thus lost to me
I have a wildcard MX *.wurtel.net, and that's filled in
/etc/exim4/update-exim4.conf.conf accordingly:
dc_other_hostnames='wurtel.net : *.wurtel.net : ...'
However, I noticed once that
I have two hypotheses in mind:
--- hypothesis 1
Aurelien Jarno ha scritto:
mplayer segfaults on a file I have (probably badly) downloaded from the
Internet. Note that other video applications in Debian (vlc, kaffeine)
do not segfault. It is very likely a security problem.
reassign 403601 libattr1
merge 403601 403592
thanks
---
Dr. Norbert Preining [EMAIL PROTECTED]Università di Siena
Debian Developer [EMAIL PROTECTED] Debian TeX Group
gpg DSA:
Processing commands for [EMAIL PROTECTED]:
reassign 403601 libattr1
Bug#403601: tex-common: unable to install because of cp
Bug#403592: libattr1: relocation error: /lib/libacl.so.1:
Bug reassigned from package `libattr1' to `libattr1'.
merge 403601 403592
Bug#403592: libattr1: relocation
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.26
reassign 403601 libattr1
Bug#403601: tex-common: unable to install because of cp
Bug reassigned from package `tex-common' to `libattr1'.
forcemerge 403592 403601
Bug#403592:
On Mon, 18 Dec 2006, Andreas Barth wrote:
* Henrique de Moraes Holschuh ([EMAIL PROTECTED]) [061217 23:17]:
On Fri, 15 Dec 2006, Andreas Barth wrote:
* Holger Levsen ([EMAIL PROTECTED]) [061204 02:03]:
scanning with usb-connected devices does not work on powerpc (or all
little
Package: libattr1
Version: 2.4.35-1
Followup-For: Bug #403592
Getting the same error here.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=en_GB,
Your message dated Mon, 18 Dec 2006 12:02:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403379: fixed in mplayer 1.0~rc1-10
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Package: xemacs21-basesupport
Version: 2006.05.10-1
Severity: serious
Justification: release criterion 5.(e)
The xsl mode (xslide) supplied in this package interprets the delete
key as a backspace. This is inconsistent with other emacs modes and
the rest of the system.
-- System Information:
On Fri, 15 Dec 2006 15:57:48 +, Steve McIntyre [EMAIL PROTECTED] wrote:
On Fri, Dec 15, 2006 at 02:02:58AM +0100, Julien Cristau wrote:
I can confirm that the attached patch fixes this problem for me.
Excellent, thanks for the help in tracking this down, Julien and
Samuel! I'll add this
On Mon, Dec 18, 2006 at 10:05:43AM -0300, Martin Marques wrote:
On Fri, 15 Dec 2006 15:57:48 +, Steve McIntyre [EMAIL PROTECTED] wrote:
On Fri, Dec 15, 2006 at 02:02:58AM +0100, Julien Cristau wrote:
I can confirm that the attached patch fixes this problem for me.
Excellent, thanks for
On Mon, 18 Dec 2006, Stefan Hornburg wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 18 Dec 2006 09:24:57 +0100
Source: sympa
Binary: sympa
Architecture: source i386
Version: 5.2.3-0.1
Distribution: experimental
Stefan, why are you ignoring all the comments
Raphael Hertzog wrote:
On Mon, 18 Dec 2006, Stefan Hornburg wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 18 Dec 2006 09:24:57 +0100
Source: sympa
Binary: sympa
Architecture: source i386
Version: 5.2.3-0.1
Distribution: experimental
Stefan, why are you ignoring
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.27
notfound 402100 1.00-1
Bug#402100: enigma: 1.00 beta should not enter etch
Bug marked as not found in version 1.00-1.
End of message, stopping processing here.
Please contact me if
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.27
tags 401530 pending upstream fixed-upstream
Bug#401530: usb-scanners don't work on powerpc (big endian)
Tags were: upstream
Tags added: pending, upstream, fixed-upstream
End of
On Mon, 18 Dec 2006 13:21:06 +, Steve McIntyre [EMAIL PROTECTED] wrote:
I haven't uploaded yet; there's another issue with inetd configuration
that needs fixing as well I'm afraid. I'm expecting a fix for that
ASAP. Even then, it'll take a couple of days to migrate to testing,
and I'll
* Andreas Barth ([EMAIL PROTECTED]) [061218 11:28]:
Given how many bug reports reached us I wonder if the maintainer has
tested his upload as all before - and I propose to do a 0-day-NMU back
to the old version within 24 hours unless the maintainer disagrees.
After some more bug reports, I
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.27
notfound 386259 0.81.1-2
Bug#386259: FTBFS: aclocal: macro `AM_PROG_MKDIR_P' required but not defined
Bug marked as not found in version 0.81.1-2.
(By the way, this Bug is currently
Hello,
thanks for your answer.
On Mon, 18 Dec 2006, Stefan Hornburg (Racke) wrote:
I'm in the progress in merging the package offered by Jean Charles Delepine
into my sources. While it is definitely better than my last released
package, it still has rough edges. If you are not satisfied with
Processing commands for [EMAIL PROTECTED]:
severity 403573 important
Bug#403573: webcam-server_0.50-1(ia64/unstable): FTBFS: Bad build-depends
Severity set to `important' from `serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for [EMAIL PROTECTED]:
severity 403585 critical
Bug#403585: Regression in 2.4.35-1
Severity set to `critical' from `serious'
severity 403599 critical
Bug#403599: Regression in 2.2.42-1
Severity set to `critical' from `serious'
thanks
Stopping processing here.
Please
Your message dated Mon, 18 Dec 2006 14:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403601: fixed in attr 1:2.4.32-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 18 Dec 2006 14:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403599: fixed in attr 1:2.4.32-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 18 Dec 2006 14:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403590: fixed in attr 1:2.4.32-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 18 Dec 2006 14:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403585: fixed in attr 1:2.4.32-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Processing commands for [EMAIL PROTECTED]:
severity 370384 normal
Bug#370384: If its not capable of processing jigdo files, what's it doing in
testing?
Severity set to `normal' from `grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Your message dated Mon, 18 Dec 2006 14:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403601: fixed in attr 1:2.4.32-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
severity 370384 normal
thanks
I basically agree, it is a bit misleading that the jigdo GUI application is
not yet capable of processing .jigdo files.
However, the app is not useless; it is a normal download manager for FTP
and HTTP.
Furthermore, jigdo-file (i.e. the package containing
Package: ghdl
Severity: serious
Currently debian/copyright mentions that the package is licensed under
plain GPL and assigns this copyright only to Tristan Gingold.
But, the source tarball contains, at dir vhdl/libraries/ieee/, *.vhdl
files with this header:
-- Copyright 1995 by IEEE. All
severity 403573 important
thanks
This is not a regression so it is not RC. The whole versioned libc6-dev
dependency seems unnecessary, c library is pulled in via build-essential
and there is no explanation why version 2.3.6 or newer is needed.
Cheers,
Riku
--
To UNSUBSCRIBE, email to [EMAIL
Your message dated Mon, 18 Dec 2006 14:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403592: fixed in attr 1:2.4.32-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
severity 403585 critical
severity 403599 critical
thanks
I did not see that the system was completely broken after installation.
Cheers,
--
.''`. Aurélien GÉRÔME
: :' :
`. `'` Free Software Developer
`- Unix Sys Net Admin
signature.asc
Description: Digital signature
Raphael Hertzog [EMAIL PROTECTED] écrivait (wrote) :
On Mon, 18 Dec 2006, Stefan Hornburg wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 18 Dec 2006 09:24:57 +0100
Source: sympa
Binary: sympa
Architecture: source i386
Version: 5.2.3-0.1
Your message dated Mon, 18 Dec 2006 14:02:09 +
with message-id [EMAIL PROTECTED]
and subject line Bug#401530: fixed in hplip 1.6.10-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 18 Dec 2006 14:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403592: fixed in attr 1:2.4.32-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Processing commands for [EMAIL PROTECTED]:
package exim4-config
Ignoring bugs not assigned to: exim4-config
severity #403605 important
Bug#403605: exim4-config: dc_other_hostnames expanded by the shell, corrupting
it
Severity set to `important' from `grave'
thanks
Stopping processing here.
package exim4-config
severity #403605 important
thanks
On Mon, Dec 18, 2006 at 12:41:27PM +0100, Paul Slootman wrote:
Package: exim4-config
Version: 4.63-11
Severity: grave
Justification: email was bounced, thus lost to me
Bounced e-mail is not lost. Downgrading.
I have a wildcard MX
Stefan Hornburg (Racke) [EMAIL PROTECTED] écrivait (wrote) :
I'm in the progress in merging the package offered by Jean Charles Delepine
into my sources. While it is definitely better than my last released
package,
it still has rough edges. If you are not satisfied with the result tomorrow,
Installing libattr1 2.4.32-1 does indeed fix this, but the version
containing the problem is 2.4.35-1, so apt immediately tries to upgrade
it again. It's easy enough to put it on hold, but it's still broken for
Sid until the fix makes it into the newer version.
Mike
Eric H [EMAIL PROTECTED] writes:
Please, is someone can tell me what how to do this manual intervention ?
I'd suggest the approach I ended up taking -- namely, moving
/usr/bin/pycentral aside, upgrading to 0.3.0.r2-2, and moving
pycentral back:
# mv /usr/bin/pycentral /usr/bin/pycentral_
#
Although gtk-recordmydesktop uses python-central, it lacks a proper
Python-Version: field, and consequently gets stuck in a half-installed
state from which one cannot even back it out without manual intervention:
I installed gtk-recordmydestop 0.3.0r2-1, and it gets stuck in a
Package: udev
Version: 0.103-1
Followup-For: Bug #403136
Hi, ...
I have experimented a bit, thanks to Marco's hints. And we narrowed this done
to the scsi-devfs.sh script not even being launched. A udevtrigger showed that
all those scripts are :
Jan 12 22:14:07 udevd[347]: udev_done: seq
Package: tetex-base
Version: 3.0.dfsg.3-3
Severity: serious
Hi,
It seems that you can't uninstall the package if things aren't set up
properly.
From the buildd log I see:
Selecting previously deselected package tetex-base.
Unpacking tetex-base (from .../tetex-base_3.0.dfsg.3-3_all.deb) ...
package: libgtk-directfb-2.0-0
severity: serious
tags: upsteam
It was recently found that during a g-i installation the GTK frontend
can easily cause an out of memory error, due to the big amount of memory
allocated at every installation step (nearly 1 MB).
After some investigations with
On Dec 18, Sven Luther [EMAIL PROTECTED] wrote:
I have experimented a bit, thanks to Marco's hints. And we narrowed this done
to the scsi-devfs.sh script not even being launched. A udevtrigger showed that
all those scripts are :
Jan 12 22:14:07 udevd[347]: udev_done: seq 2161, pid [7002]
El lun, 18-12-2006 a las 10:13 -0500, Aaron M. Ucko escribió:
Eric H [EMAIL PROTECTED] writes:
Please, is someone can tell me what how to do this manual intervention ?
I'd suggest the approach I ended up taking -- namely, moving
/usr/bin/pycentral aside, upgrading to 0.3.0.r2-2, and
Package: libattr1
Version: 2.4.32-1
Severity: grave
Justification: renders package unusable
After today dist-upgrade and reboot, kde failed to start telling:
kdeinit could not start. Check your installation.
The problem seems due to the new libattr1, because after having installed the
previous
Processing commands for [EMAIL PROTECTED]:
severity 403419 normal
Bug#403419: typo3-src-4.0: Completely broken: Cannot find tslib/
Severity set to `normal' from `grave'
tags 403419 +moreinfo
Bug#403419: typo3-src-4.0: Completely broken: Cannot find tslib/
There were no tags set.
Tags added:
Your message dated Mon, 18 Dec 2006 17:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#401796: fixed in zope-cmfplone 2.5.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Kurt Roeckx [EMAIL PROTECTED] wrote:
Package: tetex-base
Version: 3.0.dfsg.3-3
Severity: serious
Hi,
It seems that you can't uninstall the package if things aren't set up
properly.
Hm, yes. What happens is:
- tex-common is unpacked
- tetex-base is unpacked
- the install run fails
Your message dated Mon, 18 Dec 2006 18:33:19 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#403645: libattr1: kdeinit fails to start
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
On Mon, 2006-12-18 at 11:22 +0100, Leszek Koltunski wrote:
CFLAGS=-g or CFLAGS='' does not make any difference.
Ah, but not setting CFLAGS is different from setting it to the empty
string. When unset, automake picks some defaults (-O -g) which turns on
optimization.
But here's another clue:
tags 370132 + help moreinfo
thanks
Hi Aurelien,
snmpd no longer works on ia64. It dies when receiving first query.
I have got the same exact problem on s390. Given that this bug renders
I tested this in a chroot on merulo and raptor by running snmpd as user
and using a different port number,
On Mon, Dec 18, 2006 at 06:33:21PM +0100, Frank Küster wrote:
Kurt Roeckx [EMAIL PROTECTED] wrote:
Package: tetex-base
Version: 3.0.dfsg.3-3
Severity: serious
Hi,
It seems that you can't uninstall the package if things aren't set up
properly.
Hm, yes. What happens is:
-
On Sat, Dec 16, 2006 at 04:21:51AM +0200, Guillem Jover wrote:
tags 403216 - patch
thanks
On Fri, 2006-12-15 at 13:26:41 +0100, Goswin von Brederlow wrote:
Package: dpkg-dev
Version: 1.13.24
Severity: critical
File: /usr/bin/dpkg-shlibdeps
Tags: patch
Er, there's not patch in
On Fri, Dec 15, 2006 at 05:53:38PM -0600, Peter Samuelson wrote:
[H. S. Teoh]
Hi, the old patch (currently in unstable) already works---my test was
invalid because I upgraded apache2 but forgot to upgrade libapr1. Do
you still want me to test the new patch?
Ahh - great to hear! Yes,
Aaron M. Ucko a écrit :
Eric H [EMAIL PROTECTED] writes:
Please, is someone can tell me what how to do this manual intervention ?
I'd suggest the approach I ended up taking -- namely, moving
/usr/bin/pycentral aside, upgrading to 0.3.0.r2-2, and moving
pycentral back:
# mv
Your message dated Mon, 18 Dec 2006 12:36:02 -0600
with message-id [EMAIL PROTECTED]
and subject line FW: Re: Need help with RC #396817
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Package: inform
Version: 6.30-2
Followup-For: Bug #289739
Since this bug's fix is small (and only applies to inform-docs, not
inform) and the reporter seems to be a DD, I was wondering whether he
could NMU it; otherwise inform will not be in etch, which seems a bit
silly for the sake of such a
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.22~bpo.2
reassign 403599 libattr1 2.4.35-1
Bug#403599: Regression in 2.2.42-1
Bug reassigned from package `libacl1' to `libattr1'.
close 403599 1:2.4.32-1.1
Bug#403599: Regression in
severity 403083 normal
tags 403083 unreproducible help moreinfo
thanks
Hi,
I tried building this on i386 and couldn't reproduce the problem. It
worked fine. My version of haddock and ghc6 matched yours.
Also, I checked the Debian buildd logs, and no platforms seemed to have
reported this
Processing commands for [EMAIL PROTECTED]:
severity 392510 normal
Bug#392510: eclipse-rcp: creating files in /usr/local violates FHS
Severity set to `normal' from `serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
severity 392510 normal
thanks
it's not policy violation.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
severity 403204 normal
thanks
- you should have reopened the original report, not opening a new one.
- the package works ok, when zenity is installed. the severity
therefore is not grave.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Processing commands for [EMAIL PROTECTED]:
severity 403204 normal
Bug#403204: eclipse: still using wrong kdialog syntax
Severity set to `normal' from `grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Processing commands for [EMAIL PROTECTED]:
severity 403083 normal
Bug#403083: missingh: FTBFS:
dist/build/tmp/MissingH/IO/Binary.hs:dist/build/tmp/MissingH/IO/Binary.hs:
219:1: Parse error
Severity set to `normal' from `serious'
tags 403083 unreproducible help moreinfo
Bug#403083: missingh:
Dear Release Managers,
do you consider the following scenario release-critical? If yes, we
have more than one RC bug:
- $packagemanager install B X
- package A is unpacked
- package B which Depends: A is unpacked
- package X which is unrelated is tried to unpack, but fails (e.g. a
file
Package: sash
Version: 3.7-7.1
Severity: grave
Justification: renders package unusable
NMU of this package appears to be no longer statically linked.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (950, 'testing'), (750, 'unstable'), (550, 'stable')
Architecture:
1 - 100 of 152 matches
Mail list logo
