Thanks. Please do.
On Wed, 2016-07-20 at 08:18 +0200, Andreas Tille wrote:
> Hi Sören,
>
> even if bug #830343 was fixed in NMU this package has seen only NMUs in
> last years and looks unmaintained. I'll create a Git repository in
> Debian Science repository and move it to Debian Science team
Package: swig
Version: 2.0.7-3
Severity: serious
Please package swig3.0.2 ASAP.
The introduction of g++ 4.8/4.9 in the archive makes c++11 enabled swig
wrapper code fail to compile like
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746893
swig3.0 fixes this and is a hard requirement to
This is not a bug in shogun itself but just requires a rebuild with
swig3.0 (supporting c++11 properly with gcc4.9) which still needs to be
packaged
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750621
--
For the one fact about the future of which we can be certain is that it
will be utterly
close 701673 3.1.1-1
thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
yes indeed for the moment we won't have interfaces packaged at all so
this is obsolete.
On 19.11.13 17:41, Steve Cotton wrote:
On Fri, Aug 23, 2013 at 14:19 +0200, Sylvestre Ledru wrote:
As part of the transition to OpenJDK 7 and the removal of OpenJDK 6 from
the archive, could you update the
Package: bacula-sd
Version: 5.2.6+dfsg-9
Severity: grave
Tags: upstream
Since the upgrade to 5.2.6 I have a serious problem with bacula on my
debian machine. All my backups error with Error: bsock.c:389 Write error
sending 65562 bytes to Storage daemon (broken pipe).
The is a backup done from
See the attached bt. It looks like it hangs waiting for some condition
to be met indicative of a threading related deadlock maybe.
On Sat, 2012-07-07 at 15:21 -0500, Jonathan Nieder wrote:
tags 679827 + upstream moreinfo
quit
Hi,
Soeren Sonnenburg wrote:
On various webpages like e.g
On Sat, 2012-07-07 at 21:26 -0500, Jonathan Nieder wrote:
Soeren Sonnenburg wrote:
See the attached bt. It looks like it hangs waiting for some condition
Oh, that makes sense. The interesting bit is probably in another
process.
Can you reproduce the hang with --single-process
There you go:
https://code.google.com/p/chromium/issues/detail?id=136258
On Sat, 2012-07-07 at 21:41 -0500, Jonathan Nieder wrote:
tags 679827 - moreinfo
quit
Soeren Sonnenburg wrote:
With --single-process I can indeed visit e.g. github.com :) Checking
again with leaving single
without libcairo2?
On Sun, Jul 1, 2012 at 2:30 PM, Soeren Sonnenburg so...@debian.org
wrote:
Package: chromium
Version: 20.0.1132.43~r143823-1
Severity: grave
On various webpages like e.g. https://github.com chromium
reproducibly
hangs
On Sun, 2012-07-01 at 15:27 -0400, Joey Hess wrote:
Soeren Sonnenburg wrote:
When building shogun dh_shlibdeps crashes with
*** glibc detected *** /usr/bin/perl: free(): invalid pointer:
dpkg-shlibdeps: error: objdump died from signal 6
dh_shlibdeps: dpkg-shlibdeps -Tdebian/shogun-ruby
too bad I am already on 1.12.2-2 :/
On Mon, 2012-07-02 at 10:58 -0700, Andrew Chant wrote:
Which version of libcairo2 are you held at? Could you try the latest
version (1.12.2-2) and see if you can still reproduce the issue?
On Mon, Jul 2, 2012 at 3:13 AM, Soeren Sonnenburg so...@debian.org
Package: clang
Version: 3.1-8
Severity: serious
it crashes in various ways resulting in libm not being detected:
+ cd shogun-lua_modular
+ ./configure --disable-cpudetection --prefix=/usr --enable-glpk
--enable-readline --disable-svm-light --enable-hdf5 --enable-json --enable-xml
Package: debhelper
Version: 9.20120608
Severity: serious
When building shogun dh_shlibdeps crashes with
dh_shlibdeps -pshogun-ruby-modular -l
Package: chromium
Version: 20.0.1132.43~r143823-1
Severity: grave
On various webpages like e.g. https://github.com chromium reproducibly
hangs since this upgrade to 20.X (same with google-chrome even from dev
channel 21.X).
This occurs with all plugins and extensions disabled and even in
And the bad thing about it is that shogun would compile on all these
archs if dependencies would become available (as they were) and clang
would work on powerpc.
The only other option I see is to split up shogun into several
independent source package - one for each of its interfaces and to build
Package: evolution-mapi
Version: 3.2.1-3
Severity: grave
the package fails to build
[...]
dh_shlibdeps -pevolution-mapi
dpkg-shlibdeps: error: couldn't find library librt.so.1 needed by
debian/evolution-mapi/usr/lib/evolution-data-server/calendar-backends/libecalbackendmapi.so
(ELF format:
Package: clang
Version: 3.0-6
Severity: grave
I am compiling the shogun package with clang (due to its much smaller
memory footprint)
clang++ ./evaluation/MulticlassAccuracy.cpp.o
./evaluation/CrossValidation.cpp.o ./evaluation/MeanAbsoluteError.cpp.o
Package: libnetcdfc++5
Version: 1:4.1.1-8+b1
Severity: grave
on upgrade I get
Preparing to replace libnetcdfc++5 1:4.1.1-8+b1 (using
.../libnetcdfc++5_1%3a4.1.3-1_amd64.deb) ...
Unpacking replacement libnetcdfc++5 ...
dpkg: error processing
On Mon, 2012-02-27 at 23:35 +0100, Francesco P. Lovergine wrote:
On Mon, Feb 27, 2012 at 10:32:53PM +0100, Soeren Sonnenburg wrote:
Package: libnetcdfc++5
Version: 1:4.1.1-8+b1
Severity: grave
on upgrade I get
Preparing to replace libnetcdfc++5 1:4.1.1-8+b1 (using
.../libnetcdfc
You had shogun 1.0.0 installed. if you remove it and try with 1.1.0 does
this happen too?
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
signature.asc
Description: This is a digitally signed message part
Dear Gregor,
I wouldn't even mind you taking the package over!
Thanks,
Soeren
On Wed, 2011-12-21 at 20:18 +0100, gregor herrmann wrote:
tags 643363 + pending
thanks
Dear maintainer,
I've prepared an NMU for clp (versioned as 1.12.0-2.1) and
uploaded it to DELAYED/2. Please feel free to
On Thu, 2011-10-13 at 15:43 -0400, Aaron M. Ucko wrote:
Source: shogun
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of shogun have failed on several architectures because
SWIG's output proved too much for their
On Thu, 2011-10-13 at 18:20 -0400, Aaron M. Ucko wrote:
Soeren Sonnenburg so...@debian.org writes:
Yeah I know... version 1.0 currently requires (depending on language)
between 1.5 and 3.5 GB (for C++ heavy octave) to compile...
Yikes!
I hate that too... Before 1.0 we had multiple swig
Package: octave3.2
Version: 3.2.4-8
Severity: normal
Tags: patch
it is sufficient to remove the curl/types.h line - octave builds just
fine then.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: libapache2-mod-wsgi
Severity: grave
Tags: squeeze
I've just upgraded a web-server that uses apache / wsgi / django to
serve content, noticing that with this newer version of wsgi (version 3.x)
operation becomes very unreliable: After just a few connects all further
connections just
: ../../Clp/src/CbcOrClpParam.cpp:62:
error: 'INVALID' was not declared in this scope
It has been closed by Soeren Sonnenburg so...@debian.org.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better
On Fri, 2010-09-24 at 12:56 +0100, Steven Chamberlain wrote:
Hi,
On 24/09/10 06:47, Joerg Platte wrote:
Am Thursday, 23. September 2010 schrieb Anthony Callegaro:
On Tue, 2010-09-21 at 13:55 +0200, Soeren Sonnenburg wrote:
The only further info I could provide is that this is a virtual
On Tue, 2010-09-21 at 10:34 +0100, Anthony Callegaro wrote:
Hello all,
Just to add my 2cents
I have the exact same gdb dump as Soeren, so I don't see the point in
posting them again.
Le lundi 13 septembre 2010 à 19:59 +0100, Steven Chamberlain a écrit :
It may be possible to narrow it
in Py_Main (argc=2, argv=0xbfffd854) at ../Modules/main.c:577
#19 0x0805cf6b in main (argc=2, argv=0xbfffd854) at ../Modules/python.c:23
On 17/09/10 04:23, Soeren Sonnenburg wrote:
# gdb --args python /usr/bin/unattended-upgrades
...
(gdb) bt
#0 __strlen_sse2 () at ../sysdeps/i386/i686
Package: unattended-upgrades
Version: 0.62
Severity: grave
Tags: squeeze
any ideas? calling apt-get upgrade on the cmdline just works fine
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable')
Architecture:
Package: doxygen
Version: 1.7.1-1
Severity: serious
A rebuild of shogun 0.9.3 hangs with doxygen 1.7.1 generating the
documentation on hppa and kfreebsd-i386 (other archs work):
https://buildd.debian.org/fetch.cgi?pkg=shogunarch=hppaver=0.9.3-3stamp=1280603495file=logas=raw
Generating image
On Thu, 2010-08-12 at 17:03 +0200, Jakub Wilk wrote:
Source: shogun
Version: 0.9.3-1
Severity: serious
User: debian-m...@lists.debian.org
Usertag: mipsel
Justification: FTBFS
shogun FTBFS on mipsel, because build process is killed after 2.5h of
inactivity:
[…]
| python2.6
On Wed, 2010-08-04 at 08:53 -0400, Cyril Brulebois wrote:
Source: clp
Version: 1.12.0-2
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
your package FTBFS on kfreebsd-amd64:
| Generating docs for compound ClpFactorization...
|
Package: python-numpy
Version: 1:1.4.1-2
Severity: normal
This bug in numpy also causes shogun to FTBS. IMHO the right fix would
be to use
#include numpy/_numpyconfig.h
in
/usr/share/pyshared/numpy/core/include/numpy/numpyconfig.h
-- System Information:
Debian Release: squeeze/sid
APT
On Sun, 2010-06-20 at 14:04 -0700, tony mancill wrote:
/bin/bash ../../libtool --tag=CXX --mode=link g++ -g -O2 -g -Wall -O2
-lCoinUtils -o clp ClpMain.o CbcOrClpParam.o MyEventHandler.o
MyMessageHandler.o unitTest.o libClp.la -lm
g++ -g -O2 -g -Wall -O2 -o .libs/clp ClpMain.o
On Mon, 2010-06-14 at 13:35 -0400, Kyle Moffett wrote:
Package: clp
Version: 1.11.1-2
Severity: serious
Your package fails to build in a minimal unstable build chroot because
it attempts to link against -lz but does not build-depend on zlib1g-dev.
This package should not need -lz /
There is really no bug in atlas here. If it is trying to build packages
with all the fancy optimizations enabled - it will simply need a machine
that has all of these.
Soeren
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C.
could it be that this buildd was just busy/swapping and simply requires
300minutes to compile that file?
Soeren
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
--
To UNSUBSCRIBE, email to
looks like it need a newer hppa machine to build.
the package compiled perfectly fine on peri.debian.org but failed on the
presumably oder lafayette.debian.org
So I guess a rebuild on peri would fix this issue...
Since atlas 3.8 is sooo much faster than the obsoleted 3.6, I tend to
say that
Package: grub-pc
Version: 1.98+20100527-2
Severity: grave
update-grub inserts
insmod gpt
basically everywhere in grub.cfg that used to work fine with
1.98+2010x but the latest upgrade broke gpt support - is the module
now called part_gpt.mod?
-- Package-specific info:
Package: gnome-codec-install
Version: 0.4.6
Severity: normal
this needs python2.5 or later
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64
Package: mail-notification-evolution
Severity: grave
...
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux
On Mon, 2010-05-10 at 09:00 +0200, Luca Falavigna wrote:
Hi,
Hi Luca,
I tried to reproduce this behaviour but after inserting a USB pendrive,
screensaver is still active, and when I type password I see disk has
been mounted correctly.
I use gdm3, though, do you still use gdm_2.20.10-3?
I
Package: gnome-screensaver
Version: 2.30.0-1
Severity: grave
Tags: security
when I plug in a usb stick the login window is put in the background and
I see the desktop and can interact with it.
so to reproduce:
1) lock screen
2) insert usb stick and wait until it is mounted
3) voila!
-- System
On Tue, 2010-05-04 at 08:40 +0200, Josselin Mouette wrote:
Le mardi 04 mai 2010 à 07:38 +0200, Soeren Sonnenburg a écrit :
Package: gdm3
Version: 2.30.2-1
Severity: grave
a user logging out would not expect his session to be auto-logged in
again / a background crash hands over
On Tue, 2010-05-04 at 19:16 +0200, Josselin Mouette wrote:
Le mardi 04 mai 2010 à 08:48 +0200, Soeren Sonnenburg a écrit :
Would you give a better rationale before playing BTS ping-pong?
So you would expect that if you *log out* and turn away from your
computer that you are suddenly
Package: gdm3
Version: 2.30.2-1
Severity: grave
a user logging out would not expect his session to be auto-logged in
again / a background crash hands over the users session
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'),
Package: gdm3
Version: 2.30.0-2
Severity: grave
adding just the auto login options from gdm 2.20 to daemon.conf
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=me
will rightfully login the user 'me' when gdm3 starts. However exititing
gnome (logout) does not bring the gdm3 chooser but
Package: gconf2
Severity: normal
Installing 2.28.1-2 worked nicely here. However I had and up-to-date gconf2
installed
previously ...
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500,
'oldstable'),
Package: cowdancer
Version: 0.61
Severity: grave
in a freshly created cowbuilder environment svn-buildpackage failed
with
I: Extracting source
cowdancer: cannot open ilistfile /.ilist
cowdancer: Fatal, initialize_functions failed
cowdancer: cannot open ilistfile /.ilist
cowdancer: cannot open
Package: python-pkg-resources
Version: 0.6.10-2
Severity: grave
it turns out python3.1 needs mode=0o777 but this won't work with python2.x
Setting up python-pkg-resources (0.6.10-2) ...
Compiling /usr/lib/python3.1/dist-packages/pkg_resources.py ...
File
On Tue, 2010-02-16 at 23:41 +0100, Vincent Lefevre wrote:
On 2010-02-15 22:12:13 +0100, Soeren Sonnenburg wrote:
There is nothing unusual in my settings (I just added the printers... -
default settings duplex). My guess is that the sole cause is pstopdf - I
mean printing works as soon as I
On Sat, 2010-02-13 at 22:02 +, brian m. carlson wrote:
On Sat, Feb 13, 2010 at 09:04:38PM +0100, Soeren Sonnenburg wrote:
On Sat, 2010-02-13 at 18:47 +, brian m. carlson wrote:
I don't see this behavior. I'm using cups 1.4.2-8 and have no problems.
Can you perhaps send
On Sat, 2010-02-13 at 18:47 +, brian m. carlson wrote:
tags 569580 + unreproducible moreinfo
kthxbye
I don't see this behavior. I'm using cups 1.4.2-8 and have no problems.
Can you perhaps send the relevant parts of /var/log/cups/error_log ?
Also, what printer are you using and how is
Package: cups
Version: 1.4.2-8
Severity: grave
all printing fails with /usr/lib/cups/filter/pstopdf failed
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500,
'oldstable'), (1, 'experimental')
Package: bacula-common
Version: 5.0.0-3
Severity: grave
Setting up bacula-common (5.0.0-3) ...
chown: cannot access `/var/run/bacula': No such file or directory
dpkg: error processing bacula-common (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg:
On Fri, 2010-02-05 at 23:26 -0600, Jonathan Nieder wrote:
Package: shogun
Version: 0.9.1-1
Severity: serious
Hi Soeren,
On this i386, building shogun fails:
[...]
| doxygen Classifier.doxy
[...]
| Could not create search results directory 'html/search/search'
| python2.5
tag 568612 + patch
thanks
On Fri, 2010-02-05 at 23:58 -0600, Jonathan Nieder wrote:
Soeren Sonnenburg wrote:
On Fri, 2010-02-05 at 23:26 -0600, Jonathan Nieder wrote:
From http://bugs.debian.org/564338 I learn that this is due to a known
problem in doxygen, and the workaround is to add
Package: python-wxgtk2.6
Version: 2.6.3.2.2-4+b1
Severity: grave
Setting up python-wxgtk2.6 (2.6.3.2.2-4+b1) ...
file does not exist: /usr/lib/python2.6/dist-packages/wxversion.py
pycentral: pycentral pkginstall: error byte-compiling files (260)
pycentral pkginstall: error byte-compiling files
Package: gnome-settings-daemon
Version: 2.28.1-2
Severity: normal
OK, I've found the culprit:
It is actually enough to rename/remove
/usr/lib/gstreamer-0.10/libgstfrei0r.so
then gnome-settings-daemon will start again.
So the problem is in gst-plugings-bad and looking at gst-plugins-bad git
log
Package: gnome-settings-daemon
Version: 2.28.1-2
Severity: normal
I've found that removing the files
/usr/lib/gnome-settings-daemon-2.0/libkeyboard.so
and
/usr/lib/gstreamer-0.10/libgstfrei0r.so
gets gnome-settings-daemonn to work again
-- System Information:
Debian Release: squeeze/sid
Package: gnome-settings-daemon
Version: 2.28.1-2
Severity: grave
since today gnome-settings-daemon refuses to start here. this happens
not only in my current account but also using a newly created one.
when I run gnome-settings-daemon under X in from a shell the X session
terminates immediately
it fails with shogun and latest doxygen:
doxygen Kernel.doxy
Could not create search results directory 'html/search/search'
$ cat Kernel.doxy
INPUT = ../shogun/kernel
OUTPUT_DIRECTORY = Kernel
XML_OUTPUT = doxygen_xml
CREATE_SUBDIRS = NO
Package: mail-notification-evolution
Severity: grave
trying to manually build the package with latest evo fails.
also no upstream release for a year that could potentially fix the FTBS
...
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (700, 'stable'),
Package: libwebkit-dev
Version: 1.1.15.1-1
Severity: grave
(Reading database ... 528979 files and directories currently installed.)
Preparing to replace libwebkit-dev 1.1.15.1-1 (using
.../libwebkit-dev_1.1.17-2_i386.deb) ...
Unpacking replacement libwebkit-dev ...
dpkg: error processing
Package: grub-pc
Version: 1.98~20091221-1
Severity: grave
the recent upgrade fails to install here (it used to install work just fine...)
Setting up grub-pc (1.98~20091221-1) ...
head: cannot open `/boot/grub/video.lst' for reading: No such file or directory
Generating grub.cfg ...
Found linux
On Tue, 2009-12-22 at 11:10 +0100, Felix Zielcke wrote:
reassign 562054 grub-common
forcemerge 562054 562034
thanks
Am Dienstag, den 22.12.2009, 10:55 +0100 schrieb Soeren Sonnenburg:
Package: grub-pc
Version: 1.98~20091221-1
Severity: grave
the recent upgrade fails to install here
Package: cowbuilder
Version: 0.60
Severity: grave
I guess apt is missing ...
sudo cowbuilder --create
- Invoking pbuilder
forking: pbuilder create --buildplace /var/cache/pbuilder/base.cow --mirror
ftp://ftp.de.debian.org/debian --distribution sid --no-targz --extrapackages
cowdancer
W:
On Wed, 2009-12-23 at 15:28 +0900, Junichi Uekawa wrote:
Sounds like a bug for debootstrap, no?
Indeed!
At Wed, 23 Dec 2009 07:15:53 +0100,
Soeren Sonnenburg wrote:
Package: cowbuilder
Version: 0.60
Severity: grave
I guess apt is missing ...
sudo cowbuilder --create
Package: xserver-xorg-core
Version: 2:1.6.5-1
Severity: grave
none of the packages xserver-xorg-input-kbd xserver-xorg-input-mouse
xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-chips
xserver-xorg-video-cirrus xserver-xorg-video-fbdev
xserver-xorg-video-i128
Package: nfs-common
Version: 1:1.2.0-4.1
Severity: grave
on upgrade I am getting this error:
Setting up nfs-common (1:1.2.0-4.1) ...
Not replacing deleted config file /etc/idmapd.conf
Not replacing deleted config file /etc/default/nfs-common
update-rc.d: error: unable to read
Package: dovecot
Severity: critical
Tags: security
from http://www.dovecot.org/list/dovecot-news/2009-November/000143.html
This is mainly to fix the 0777 base_dir creation issue, which could be
considered a security hole, exploitable by local users. An attacker
could for example replace
Package: libboost-python1.40-dev
Version: 1.40.0-3
Severity: normal
modifying the postinst script to use set -xe we observe:
Setting up libboost-python1.40-dev (1.40.0-3) ...
+ update=/usr/share/python/runtime.d/libboost-python1.40-dev.rtupdate
+ which pyversions
+ pyversions -d
+
Package: devicekit-disks
Severity: grave
i cannot install devicekit-disks since on my cryptsetup based system and
devicekit-disks is trying to remove it.
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'),
Package: readahead-fedora
Version: 1.5.0-6
Severity: grave
Setting up readahead-fedora (1.5.0-6) ...
dpkg: error processing readahead-fedora (--configure):
subprocess installed post-installation script returned error exit
status 123
Errors were encountered while processing:
On Fri, 2009-10-09 at 08:18 -0500, Raphael Geissert wrote:
Hi,
2009/10/9 Soeren Sonnenburg so...@debian.org:
Package: readahead-fedora
Version: 1.5.0-6
Severity: grave
Setting up readahead-fedora (1.5.0-6) ...
dpkg: error processing readahead-fedora (--configure
On Fri, 2009-10-09 at 10:37 -0500, Raphael Geissert wrote:
Hi,
On Friday 09 October 2009 08:35:36 Soeren Sonnenburg wrote:
On Fri, 2009-10-09 at 08:18 -0500, Raphael Geissert wrote:
Could you please modify the 'set -e' line and make it a 'set -xe' and
dpkg --configure --pending
On Sun, 2009-09-13 at 10:41 +0200, Santiago Vila wrote:
On Sat, 12 Sep 2009, Soeren Sonnenburg wrote:
Package: diffutils
Version: 2.8.1-17
Severity: grave
note I have experimental/unstable/stable in sources.list : on a
dist-upgrade from today I get:
(Reading database
Package: diffutils
Version: 2.8.1-17
Severity: grave
note I have experimental/unstable/stable in sources.list : on a dist-upgrade
from today I get:
(Reading database ... 510515 files and directories currently installed.)
Unpacking diffutils (from .../diffutils_1%3a2.8.1-17_i386.deb) ...
dpkg:
On Sat, 2009-08-01 at 10:25 +0200, Brice Goglin wrote:
On Wed, Jun 03, 2009 at 06:16:11AM +0200, Soeren Sonnenburg wrote:
Yes, happens with 2.6.30-rc7+ and xorg-intel-git-current. AFAIK bugs are
filed already.
AFAIK it is not kernel dependent but happens with
xserver-xorg-video-intel
Package: libopenmpi-dev
Version: 1.3.2-2
Severity: grave
[...]
Setting up libopenmpi-dev (1.3.2-2) ...
update-alternatives: error: alternative mpiCC can't be slave of mpi: it is a
slave of mpicc
dpkg: error processing libopenmpi-dev (--configure):
subprocess installed post-installation script
On Fri, 2009-06-05 at 04:07 +0300, İlhan Bilaloğlu wrote:
Package: ffmpegthumbnailer
Severity: serious
Justification: no longer builds from source
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel:
On Wed, 2009-06-03 at 01:23 +0200, Julien Cristau wrote:
On Thu, Apr 23, 2009 at 07:21:26 +0200, Soeren Sonnenburg wrote:
I am seeing the exact same symptoms of
https://bugs.launchpad.net/bugs/359392
also since the recent upgrade of xorg/mesa/intel packages in debian (1-2
weeks ago
Package: ed
Version: 1.3-3
Severity: normal
Setting up ed (1.3-3) ...
update-alternatives: error: alternative path /bin/ed doesn't exist.
dpkg: error processing ed (--configure):
subprocess installed post-installation script returned error exit status 2
/.
/usr
/usr/share
/usr/share/info
Package: libgcj-common
Version: 1:4.3.3-5
Severity: grave
aot-compile occurs in both packages...
[...]
(Reading database ... 497703 files and directories currently installed.)
Preparing to replace libgcj-common 1:4.3.3-5 (using
.../libgcj-common_1%3a4.4.0-6_all.deb) ...
Unpacking replacement
Package: xserver-xorg-video-intel
Version: 2.7.0-1
Severity: grave
I am seeing the exact same symptoms of
https://bugs.launchpad.net/bugs/359392
also since the recent upgrade of xorg/mesa/intel packages in debian (1-2
weeks ago).
These symptoms are:
- random frequent lockups of xorg (one may
Package: compiz
Version: 0.7.6-8
Severity: normal
...
on a sid-current system with gnome control center apt-get -b sourc'd to get the
build dependencies it is also failing due to other files missing:
[...]
dh_installchangelogs ChangeLog
dh_install --sourcedir=/tmp/compiz-0.8.2/debian/tmp
Package: cups
Version: 1.3.9-17
Severity: grave
It seems that this is related to calling pstopdf from the cups package
D [15/Apr/2009:14:41:38 +0200] [Job 689] pstopdf 6 args: 689 sonne document
XRColorDensityCyanHigh=0 XRRGBCorrection=Perceptual noXRTonerSaver
XRBrightness=Normal
Package: djbdns
Followup-For: Bug #516394
Not sure if any of the previous reporters actually read
http://cr.yp.to/djbdns/forgery.html , but it occurs to me as if this
problem is a problem in the current DNS protocol that cannot be
prevented *at all*. However, it can be made significantly harder
Package: mail-notification
Version: 5.4.dfsg.1-1+b1
Followup-For: Bug #393606
note that this even happens when one disables the new mail plugin in
evolution. it is sufficient to just have the mail-notification daemon
running before starting evo to crash evo 2.24.5
-- System Information:
Debian
Package: ekiga
Version: 3.0.1-1
Severity: grave
(only the package in experimental!) gives this on
$ ekiga
Ekiga got an invalid value for the configuration key
/apps/ekiga/general/gconf_test_age.
It probably means that your configuration schemas have not been
Package: openjdk-6-jre-headless
Version: 6b11-7
Severity: grave
It reproducibly fails to install with (see below). This is on i386, sun-java*
worked.
$ sudo apt-get -ft unstable install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0
For me it helps to add -Xmx256m to the java call in the postinst script, like
if ! $basedir/bin/java -client -Xshare:dump -Xmx256m -XX:PermSize=128m
$log; then
Not sure if 256m are required or less might be enough though.
Soeren
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Fri, 2008-08-08 at 11:49 -0300, Lucas Nussbaum wrote:
Package: shogun
Version: 0.6.3-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080808 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in a lenny chroot, your package failed
to build on
Package: inkscape
Version: 0.46-1+b1
Followup-For: Bug #488170
so I am begging for a new upload
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux
I neither see this problem with 2.22.2 nor 2.22.1 on a full gnome
desktop...
it might be your local setup, did you try whether the problem for a
fresh new user?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: matplotlib
Version: 0.90.2-1
Severity: serious
Tags: patch
ttconv/truetype.h requires an
#include stdio.h
at the top of the file then matplotlib compiles through using gcc4.3
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (700, 'stable'),
On Mon, 2008-04-28 at 11:20 +0200, Sandro Tosi wrote:
Hi Soeren,
thanks for the report!
Version: 0.90.2-1
ttconv/truetype.h requires an
#include stdio.h
at the top of the file then matplotlib compiles through using gcc4.3
The version you reported the bug is a really
tag 476718 + patch
thanks
this is the (trivial) patch to fix the problem. Note that the patch
conservatively assumes that swig won't work with python2.6 so it
requires =2.4 2.6. Also guile-1.6 is no longer current, so it shifts
build-deps to guile-1.8
and while we are at it: it would be nice to
1 - 100 of 160 matches
Mail list logo
