On Sun, Dec 16, 2007 at 05:12:23AM -0600, hugo vanwoerkom wrote:
> Those are installed:
> ...
> ii xfonts-100dpi 1:1.0.0-4
>100 dpi fonts for X
[...]
> It would be strange if the standard default install of Etch not
> installed xfonts.
Yes, but Ted seems to n
Package: courier-imap
Version: 4.3.0-1.
Severity: grave
Justification: renders package unusable
Hello,
I have observed this error since my last daily Lenny update:
before everything was fine.
In fact, this bug sounds as a former one (#455210),
nevertheless I think it can not be solved as suggest
Last patch is also wrong. :) The attached patch fixes several remaining bugs
that showed up at the end of the build, in particular a problem related to
the new dpkg-shlibdeps behavior in unstable.
With this patch, I get a full build of all the packages, which I'll be doing
a final review on now; i
Your message dated Mon, 17 Dec 2007 08:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#455421: fixed in ccsm 0.6.0-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 is now your
Your message dated Mon, 17 Dec 2007 08:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#455421: fixed in ccsm 0.6.0-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 is now your
Only one line
search kast
Mike Markley schreef:
Aside from the updated deb, can I see your resolv.conf?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Dec 17, 2007 at 10:08:07AM +0100, Jos <[EMAIL PROTECTED]> wrote:
> search kast
How do you do name resolution?
--
Mike Markley <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: edac-utils
Version: 0.10-1
Severity: grave
Justification: renders package unusable
The package cannot be installed:
dpkg --configure edac-utils
Setting up edac-utils (0.10-1) ...
Registering DIMM labels for Memory Error Detection and Correction: edac
invoke-rc.d: initscript edac, action "
Package: kobodeluxe
Version: 0.5.0-2
Severity: grave
Justification: renders package unusable
Hi.
The last version crashes when starting:
$ kobodl
Application path: '.'
[39] Shadow buffer not supported with OpenGL drivers!
[149] Could not get h/w display surface.
[1332] audio.c: Warning: Requeste
Processing commands for [EMAIL PROTECTED]:
> package ratpoison
Ignoring bugs not assigned to: ratpoison
> block 456631 by 452981
Bug#452981: xserver-xorg-xore: Xorg hangs (endless loop in PlayReleasedEvents)
Bug#456631: Ratpoison command-line locks up X server
Was not blocked by any bugs.
Blockin
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> tags 456350 + unreproducible
Bug#456350: python-visual: FTBFS: New or changed copyright notices discovered!
There were no tags set.
Tags added: unreproducible
>
End of message, stop
Package: gradm
Version: 1.9.15-2.1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal
Hi,
While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:
* superseded by gradm2 (#403522, #398797)
If you think that it should be orp
On Sun, Dec 16, 2007 at 05:45:05PM -0800, Steve Langasek wrote:
> The attached patch works quite a bit better, and is what I'll upload if it
> finishes checking out here.
Nope, that patch was also total crap. But this patch gets me a package that
builds successfully, *and* the binaries contain wh
Package: virtualbox-ose-modules-2.6-686
Severity: grave
Justification: renders package unusable
Uninstallable in conjunction with the latest linux kernel in Debian.
Please update this package.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1,
Package: epplets
Version: 0.8.cvs.2005032801-3.2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal
Hi,
While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:
* It has had an RC bug for 4 months, due to removal of libfnlib
Package: array-util
Version: 1.9-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal
Hi,
While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:
* Depends on the old imlib libraries, which are slated for gradual
removal
Package: chameleon
Version: 1.1-8.1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal
Hi,
While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:
* Low popcon
* Last upload over three years ago.
* Depends on the old imli
Package: motioneye
Version: 1.2-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal
Hi,
While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:
* Last upload over three years ago.
* Low popcon
* Depends on old imlib, whi
Package: mozart-gtk
Version: 20060615-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal
Hi,
While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:
* RC buggy.
* Low popcon
* Depends on the old imlib libraries, which a
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> package lunar-applet
Ignoring bugs not assigned to: lunar-applet
> tags 446973 + pending
Bug#446973: lunar-applet: Missing and incorrect copyright/licensing information
Tags were: c
Package: pixelize
Version: 0.9.2-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal
Hi,
While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:
* Low popcon
* No upload for almost two years.
* Depends on the old imlib l
Processing commands for [EMAIL PROTECTED]:
> retitle 456647 needs update for 2.6.23-1
Bug#456647: virtualbox-ose-modules-2.6-686: uninstallable
Changed Bug title to `needs update for 2.6.23-1' from
`virtualbox-ose-modules-2.6-686: uninstallable'.
> tags 456647 +pending
Bug#456647: needs update f
with bind9.
the server has the name "kast".
Mike Markley schreef:
On Mon, Dec 17, 2007 at 10:08:07AM +0100, Jos <[EMAIL PROTECTED]> wrote:
search kast
How do you do name resolution?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
Hello,
in fact the issue is permission issue:
I guess that the policy for Maildir changed at one point.
Now all the files in my () Maildir have ownership `.'
with permssion `drwx--' for folders and `-rw---' for files.
An imap works.
Sorry for the noise,
Jerome
Debian Bug Tracking Syste
Processing commands for [EMAIL PROTECTED]:
> unarchive 248290
Unarchived Bug 248290
Unarchived Bug 248292
> submitter 248290 !
Bug#248290: Incorrect syntax in the sample imapfilter config file
/usr/share/doc/imapfilter/examples/sample.config.lua
Changed Bug submitter from Y Giridhar Appaji Nag <
Hi, just a note that this bug is almost certainly an X server bug:
downgrading to ratpoison 1.4.0.dfsg-7 does not fix the problem, I still
get the same symptoms.
T
--
English is useful because it is a mess. Since English is a mess, it maps
well onto the problem space, which is also a mess, whic
Jerome BENOIT wrote:
> Package: courier-imap
> Version: 4.3.0-1.
> Severity: grave
> Justification: renders package unusable
>
>
> Hello,
>
> I have observed this error since my last daily Lenny update:
> before everything was fine.
> In fact, this bug sounds as a former one (#455210),
> neverth
Package: amsn
Version: 0.97RC1+svn20070912~3v1ubuntu0
Severity: grave
Justification: renders package unusable
I get this error when starting up amsn after my last upgrade:
[EMAIL PROTECTED]:~$ amsn
Error in startup script: extra characters after close-brace
while executing
"set command [list
Your message dated Mon, 17 Dec 2007 14:00:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Closing: 456631
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
FYI, this problem still occurs with 0.9.50.
--
aldemir
__
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com
Hello,
Stefan Hornburg (Racke) wrote:
Jerome BENOIT wrote:
Package: courier-imap
Version: 4.3.0-1.
Severity: grave
Justification: renders package unusable
Hello,
I have observed this error since my last daily Lenny update:
before everything was fine.
In fact, this bug sounds as a former one
I would love to get rid of this package, it is a real pain to maintain
due to the way it generates itself from the toolchain's header files.
Before removing it, I will ask on upstream's mailing list if anyone
wants to take it forward. I expect they won't and then I will ask for
its removal.
k
Processing commands for [EMAIL PROTECTED]:
> # The package is not installable in unstable
> severity 456646 serious
Bug#456646: aptitude: depends on libgcc1 from experimental
Severity set to `serious' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Deb
Package: libcwidget1
Version: 0.5.6.1-2
Severity: serious
Your package depends on libstdc++6 (>= 4.3) and on libgcc1 (>= 1:4.3)
which are not available in sid.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kerne
On Mon, Dec 17, 2007 at 11:21:49AM +0100, Michal Politowski <[EMAIL PROTECTED]>
was heard to say:
> aptitude 0.4.10-1 depends on libgcc1 (>= 1:4.3),
> which is only available in experimental.
Ow. So, release team, is the correct way of handling this without
making everyone even more angry at m
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> notfound 456646 0.4.10-1
Bug#456646: aptitude: depends on libgcc1 from experimental
Bug no longer marked as found in version 0.4.10-1.
>
End of message, stopping processing here.
P
Your message dated Mon, 17 Dec 2007 15:49:02 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#456673: libcwidget1: Built against experimental libstdc++6
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
On Dec 15, 2007 12:47 AM, Erich Schubert <[EMAIL PROTECTED]> wrote:
> Hi,
> Your mails never reached me. Did you send them to the BTS only maybe?
Yes, only to BTS, I thought they will be automatically forwarded to
you. Sorry about that.
> As you can see from the original bug report, I didn't have
Package: pam-pgsql
Version: 0.5.2-9.3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-orphan
Hi,
While reviewing some packages, your package came up as a package that
should maybe be orphaned by its maintainer, because:
* maintainer seems not active
* no upload maintainer since lo
On Thu, Sep 13, 2007 at 09:37:53AM +0200, Cyril Brulebois wrote:
> tag 441675 patch
> thanks
>
> Lucas Nussbaum <[EMAIL PROTECTED]> (10/09/2007):
> > ../../server/user_pam.c: In function 'vrfy_user':
> > ../../server/user_pam.c:52: warning: implicit declaration of function
> > 'syslog'
> > ../../
Your message dated Mon, 17 Dec 2007 15:59:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#456646: aptitude: depends on libgcc1 from experimental
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
Your message dated Mon, 17 Dec 2007 15:01:59 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#441668: fixed in postgresql-pljava 1.3.0-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
Your message dated Mon, 17 Dec 2007 15:05:19 +
with message-id <[EMAIL PROTECTED]>
and subject line try closing with newly uploaded version
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
Hi Christoph,
Congrats on being the first bugreporter for edac-utils ;-)
that is weird imho that it failed without explicit message about the
reason. I wonder if by any chance you have global errexit for the shell
option enabled. Could you alter that edac init script and add
echo $SHELLOPTS
with
i want to confirm this bug
you can see it by launching gdebi-gtk from the command line
when you click on "install" the program close and you see this:
gksu: opzione `--always-ask-pass' non riconosciuta
Versione GKsu 2.0.0
Utilizzo: gksu [-u ] [opzioni]
[snip]
it's in italian here..
but simply
Hi Kurt,
thanks for the report. I traced the bug down to this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456721
When we fix that, we'll upload a new revision.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Dec 17, 2007 2:06 AM, Chris Waters <[EMAIL PROTECTED]> wrote:
> On Sun, Dec 16, 2007 at 05:12:23AM -0600, hugo vanwoerkom wrote:
> > Those are installed:
> > ...
> > ii xfonts-100dpi 1:1.0.0-4
> >100 dpi fonts for X
> [...]
>
> > It would be strange if the s
Package: petsc
Severity: serious
--- Please enter the report below this line. ---
Hi Adam,
latest petsc from unstable FTBFS in pbuilder for me:
[...]
TESTING: checkCCompiler from
config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:380)
Package: subversion
Version: 1.4.4dfsg1-1
Severity: grave
File: /usr/bin/svn
Justification: renders package unusable
Hello,
As of today, svn won't run on a Debian sid at all:
% svn
svn: symbol lookup error: /usr/lib/libsvn_ra_dav-1.so.1: undefined symbol:
svn_ra_dav__do_check_path
-- Sy
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> severity 456642 important
Bug#456642: kobodeluxe: crashes when starting
Severity set to `important' from `grave'
>
End of message, stopping processing here.
Please contact me if yo
Christoph Anton Mitterer wrote:
> [1332] audio.c: Warning: Requested 1024 samplebuffer, but got 940
> samples.
You seem to be using alsa, what kind of audio hardware do you have? Does
-nosound -nomusic work?
--
see shy jo
Your message dated Mon, 17 Dec 2007 19:32:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line (no subject)
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 reo
Package: exiv2
Severity: grave
Tags: patch security
Hi,
an integer overflow was reporting in exiv2's EXIF parsing
code which results in a heap-based buffer overflow.
This is CVE-2007-6353 please include the CVE id in your
changelog if you fix the bug.
Because our stable security team is not abl
Hi,
Building the current bzip2 in an up-to-date pbuilder produces an
uninstalable package:
...
Unpacking replacement bzip2 ...
Setting up bzip2 (1.0.3-7) ...
install-info(/usr/share/info/bzip2.info): warning, ignoring confusing
INFO-DIR-ENTRY in file.
No `START-INFO-DIR-ENTRY' and no `This file
Package: xserver-xorg
Version: 1:7.3+8
Severity: serious
--- Please enter the report below this line. ---
Enabling loading the wacom core event devices in xorg.conf (by
uncommenting the commented lines below) breaks loading of the X-server
completely. With them commented out it works flawlessl
Processing commands for [EMAIL PROTECTED]:
> reassign 456721 libopenmpi1
Bug#456721: libpetsc.so depends on unexistent libraries
Bug reassigned from package `libpetsc2.3.3' to `libopenmpi1'.
> severity 456721 grave
Bug#456721: libpetsc.so depends on unexistent libraries
Severity set to `grave' fr
Your message dated Mon, 17 Dec 2007 13:42:41 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#456730: FTBFS
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 t
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> reassign 456764 xserver-xorg-core
Bug#456764: loading wacom breaks server (signal 11)
Bug reassigned from package `xserver-xorg' to `xserver-xorg-core'.
> severity 456764 important
Your message dated Mon, 17 Dec 2007 18:47:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#456760: fixed in exiv2 0.15-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 is now your
Processing commands for [EMAIL PROTECTED]:
> severity 448598 grave
Bug#448598: tar -C foo -c . | tar -C bar -x ends up with nothing on read
errors
Severity set to `grave' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adm
Hi,
I've sponsored Li Daobing's NMU patch and uploaded it to the delayed/7
queue. This means that if you (the maintainer) don't like the solution,
you still have 7 days to cancel the actual upload. You should be
getting mail about that as well, I think.
Thanks,
Bas
--
I encourage people to se
On 17 December 2007 at 18:45, Debian Bug Tracking System wrote:
| Processing commands for [EMAIL PROTECTED]:
|
| > reassign 456721 libopenmpi1
| Bug#456721: libpetsc.so depends on unexistent libraries
| Bug reassigned from package `libpetsc2.3.3' to `libopenmpi1'.
|
| > severity 456721 grave
| B
Your message dated Mon, 17 Dec 2007 19:52:52 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453050: fixed in samba 3.0.14a-3sarge10
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
Your message dated Mon, 17 Dec 2007 19:52:52 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453050: fixed in samba 3.0.14a-3sarge10
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
Your message dated Mon, 17 Dec 2007 19:52:52 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453050: fixed in samba 3.0.14a-3sarge10
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
Your message dated Mon, 17 Dec 2007 19:52:52 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453050: fixed in samba 3.0.14a-3sarge10
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
Your message dated Mon, 17 Dec 2007 19:52:52 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453050: fixed in samba 3.0.14a-3sarge10
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
Am Montag, den 17.12.2007, 13:36 -0600 schrieb Dirk Eddelbuettel:
> Indeed, what were we thinking here Manuel? [...] In light of this, can
> you remind me why you put the libs into /usr/lib/openmpi ? I
> understand why we put the _internal_ library files like [files
> snipped] there, but for the v
Your message dated Mon, 17 Dec 2007 19:52:46 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434045: fixed in horde3 3.0.4-4sarge5
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 n
On Mon, 2007-12-17 at 13:36 -0600, Dirk Eddelbuettel wrote:
> On 17 December 2007 at 18:45, Debian Bug Tracking System wrote:
> | Processing commands for [EMAIL PROTECTED]:
> |
> | > reassign 456721 libopenmpi1
> | Bug#456721: libpetsc.so depends on unexistent libraries
> | Bug reassigned from pac
On 17 December 2007 at 21:13, Manuel Prinz wrote:
| Am Montag, den 17.12.2007, 13:36 -0600 schrieb Dirk Eddelbuettel:
| > Indeed, what were we thinking here Manuel? [...] In light of this, can
| > you remind me why you put the libs into /usr/lib/openmpi ? I
| > understand why we put the _internal
Package: lm-sensors
Version: 1:3.0.0-4
Severity: grave
Justification: renders package unusable
Some voltage readings are not reported by versions 3 of lm-sensors.
Configuration files tried with versions 3 are both the
old /etc/sensors.conf and the new /etc/sensors3.conf, same result, see
below.
W
On Dec 17, 2007 7:41 PM, Adam C Powell IV <[EMAIL PROTECTED]> wrote:
> reassign 456721 libopenmpi1
> severity 456721 grave
> thanks
>
> Moving libmpi_*.so.0 to /usr/lib/openmpi/lib/ with no symlinks
> from /usr/lib *breaks every package which links with those libraries*.
> The soname ends in .so.0,
Processing commands for [EMAIL PROTECTED]:
> severity 456774 normal
Bug#456774: lm-sensors3 does not work
Severity set to `normal' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs datab
severity 456774 normal
thanks
Svante Signell a écrit :
> Package: lm-sensors
> Version: 1:3.0.0-4
> Severity: grave
> Justification: renders package unusable
>
> Some voltage readings are not reported by versions 3 of lm-sensors.
> Configuration files tried with versions 3 are both the
> old /etc
Am Montag, den 17.12.2007, 14:47 -0600 schrieb Dirk Eddelbuettel:
> On 17 December 2007 at 21:13, Manuel Prinz wrote:
> | Am Montag, den 17.12.2007, 13:36 -0600 schrieb Dirk Eddelbuettel:
> | The reasoning behind that was to fix the breaking of other MPI
> | implementations by moving stuff to /usr/
On Mon, 2007-12-17 at 14:47 -0600, Dirk Eddelbuettel wrote:
> On 17 December 2007 at 21:13, Manuel Prinz wrote:
> | Am Montag, den 17.12.2007, 13:36 -0600 schrieb Dirk Eddelbuettel:
> | > Indeed, what were we thinking here Manuel? [...] In light of this, can
> | > you remind me why you put the libs
Am Montag, den 17.12.2007, 16:16 -0500 schrieb Adam C Powell IV:
> As the maintainer of mpich, I do not see any conflicts here.
> libmpich1.0ldbl has: libmpich.so.1.0, libfmpich.so.1.0,
> libpmpich.so.1.0, libpmpich++.so.1.0, libtvmpich.so.1.0, and
> libmpe.so.1.0 . There's no ABI compatibility be
Your message dated Mon, 17 Dec 2007 21:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#446973: fixed in lunar-applet 1.8-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
Sjoerd Simons wrote:
> I reviewed the related code and that seems fine. Could you mail me your
> fdi-cache so i can double-check it is valid?
--
Mircea Gherzan
Faculty of Automatic Control and Computers
Politehnica University of Bucharest
fdi-cache.gz
Description: GNU Zip compressed data
Package: gclcvs
Version: 2.7.0-80
Severity: serious
Hi,
It seems that when building gclcvs (on amd64) it uses alot of RAM.
After some time it was using around 1 TB, yes terra byte, 1024 GB, of
RAM. Which the box of course doesn't have. top even claimed that it
was all resident and shared.
I've
On 17 December 2007 at 22:27, Manuel Prinz wrote:
| Am Montag, den 17.12.2007, 14:47 -0600 schrieb Dirk Eddelbuettel:
| > On 17 December 2007 at 21:13, Manuel Prinz wrote:
| No, as there are more libraries needed for the compiler wrappers, if I'm
| not mistaken.
| > I'm at work too so I didn't hav
Hi Dirk!
Am Montag, den 17.12.2007, 16:24 -0600 schrieb Dirk Eddelbuettel:
> Are you sure we need alternatives for something like libmpi_cxx.so.0 which
> the 'other' (ie LAM) doesn't have?
No. What I currently try to figure out is where the intersection is and
create links all unique libs and man
On Mon, 2007-12-17 at 16:24 -0600, Dirk Eddelbuettel wrote:
> On 17 December 2007 at 22:27, Manuel Prinz wrote:
> | Am Montag, den 17.12.2007, 14:47 -0600 schrieb Dirk Eddelbuettel:
> | > On 17 December 2007 at 21:13, Manuel Prinz wrote:
> | No, as there are more libraries needed for the compiler w
Package: sawfish
Version: 1:1.3.1-2
Severity: grave
Justification: renders package unusable
Setting up sawfish (1:1.3.1-2) ...
install-info(/usr/share/info/sawfish.info): warning, ignoring confusing
INFO-DIR-ENTRY in file.
No `START-INFO-DIR-ENTRY' and no `This file documents'.
install-info(/usr
Am Montag, den 17.12.2007, 17:53 -0500 schrieb Adam C Powell IV:
> That already happens via alternatives slaves. As discussed earlier,
> it's inappropriate with ABI-incompatible soname-named files e.g. *.so.0
>
> I think we're going in the right direction: alternatives for *.so and
> different fi
Your message dated Mon, 17 Dec 2007 23:23:55 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432621: fixed
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 t
On Mon, Dec 17, 2007 at 12:31:12PM +0100, Jos <[EMAIL PROTECTED]> wrote:
>with bind9.
>the server has the name "kast".
Ah. I'm afraid that's not how resolv.conf works. "search" simply
specifies a list of domains under which to search for hosts. So, for
example, if you attempted to look up
reopen 451268
block 456791 451268
thanks
On Mon, Dec 17, 2007 at 07:01:11PM +0100, Santiago Ruano Rincón wrote:
> ...
> Unpacking replacement bzip2 ...
> Setting up bzip2 (1.0.3-7) ...
> install-info(/usr/share/info/bzip2.info): warning, ignoring confusing
> INFO-DIR-ENTRY in file.
>
> No `STAR
Processing commands for [EMAIL PROTECTED]:
> reopen 451268
Bug#451268: librep-doc: confusing INFO-DIR-ENTRY makes postinst fail
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
Bug reopened, originator not changed.
> bl
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> block 456791 with 451268
Bug#451268: librep-doc: confusing INFO-DIR-ENTRY makes postinst fail
Bug#456791: sawfish: unable to determine description for dir entry - giving up
Was not b
Your message dated Tue, 18 Dec 2007 00:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#446537: fixed in libsdl1.2 1.2.12-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
Hi guys!
Am Montag, den 17.12.2007, 17:53 -0500 schrieb Adam C Powell IV:
> That already happens via alternatives slaves. As discussed earlier,
> it's inappropriate with ABI-incompatible soname-named files e.g. *.so.0
>
> I think we're going in the right direction: alternatives for *.so and
> di
Processing commands for [EMAIL PROTECTED]:
> tags 372968 + patch
Bug#372968: xdelta: debmake is deprecated
There were no tags set.
Tags added: patch
> Thank you
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bu
Here is a debdiff of a debhelper version of xdelta if you are
interested. It also fixes a few other linda/lintian issues and updates
standards to 3.7.3.
Thank you,
Barry deFreese
diff -u xdelta-1.1.3/debian/changelog xdelta-1.1.3/debian/changelog
--- xdelta-1.1.3/debian/changelog
+++ xdelta
On Dec 15, 2007 12:05 PM, Alessio Gaeta <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I can confirm this bug, it happens on my machine too. The problem shows
> itself only when the parameter "splashy" is passed to the kernel. If I
> remove it, the system boots no
Thanks for reporting this bug.
Attached is a copy of lsb-base-logging.sh that fixes this and other bugs. We
will be doing a minor (bug fixes) release shortly.
--
)(-
Luis Mondesi
Maestro Debiano
- START ENCRYPTED BLOCK (Triple-ROT13) --
Gur Hohagh [Yvahk] qvfgevohgvba oevatf gu
On Dec 15, 2007 2:25 PM, Witold Baryluk <[EMAIL PROTECTED]> wrote:
> Package: splashy
> Followup-For: Bug #455685
>
> It also assumes that splashy is started.
>
> Error is in function log_daemon_msg in /etc/lsb-base-logging.sh
> ("pidof splashy ..." line, and call to stop_splashy in "case ...")
>
On Dec 12, 2007 3:13 AM, Georg Wittenburg <[EMAIL PROTECTED]> wrote:
> Package: splashy
> Version: 0.3.7-1
> Severity: critical
> Justification: breaks the whole system
>
>
> Hi!
>
> After upgrading to splashy 0.3.7, splashy fails to start with error code
> -3 from splashy_start_splashy().
>
> Wha
Jürgen Richtsfeld schrieb:
> Am Montag 17 Dezember 2007 05:58:00 schrieben Sie:
>> Jürgen Richtsfeld schrieb:
>>> hi!
>>> I just built as the wikipage says, but I only installed the built
>>> kdesvn_0.14.1-1_amd64.deb (kdesvn-kio-plugins_0.14.1-1_amd64.deb,
>>> libsvnqt4_0.14.1-1_amd64.deb and libs
1 - 100 of 104 matches
Mail list logo
