Peter Fritzsche wrote:
> > > It just crashes the kernel and leaves the system in a unusable state
> > > when the module is fresh compiled and loaded using "modprobe nvidia"
> > > or I restart the system and the module is automatically loaded. Here
> &g
Peter Fritzsche wrote:
> Peter Fritzsche wrote:
> > Package: nvidia-kernel-dkms
> > Version: 195.36.24-1
> > Severity: serious
> >
> > It just crashes the kernel and leaves the system in a unusable state when
> > the module is fresh compiled and loaded using
Peter Fritzsche wrote:
> Peter Fritzsche wrote:
> > Package: nvidia-kernel-dkms
> > Version: 195.36.24-1
> > Severity: serious
> >
> > It just crashes the kernel and leaves the system in a unusable state when
> > the module is fresh compiled and loaded using
Peter Fritzsche wrote:
> Package: nvidia-kernel-dkms
> Version: 195.36.24-1
> Severity: serious
>
> It just crashes the kernel and leaves the system in a unusable state when
> the module is fresh compiled and loaded using "modprobe nvidia" or I
> restart the system
Package: nvidia-kernel-dkms
Version: 195.36.24-1
Severity: serious
It just crashes the kernel and leaves the system in a unusable state when the
module is fresh compiled and loaded using "modprobe nvidia" or I restart the
system and the module is automatically loaded. Here is the kernel Oops:
[
Package: cuneiform
Version: 0.7.0+dfsg-5
Severity: serious
Please do a rebuild to resolve that problem.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.32-3-amd64
Debian Release: squeeze/sid
500 unstableftp.debian.org
--- Package information. ---
Depends
Not only when you use stuff from experimental. It is always a good idea to use
sbuild or pbuilder/cowbuilder to build your packages before uploading. This is
even the case when the binary packages will be stripped from uploads in the
future, because you easily see missing dependencies locally.
Package: kmymoney2-plugin-aqbanking
Version: 1.0-1
Severity: serious
Just opened a kmymoney 1.0.2 file in the current version of kmymoney
(3.95.0+svn1069391-2) in unstable. I noticed that "update account" is disabled
for all my accounts I previously attached to aqbanking in kmymoney 1.0.2. I
ca
Package: nvidia-glx-dev
Version: 190.42-1
Severity: serious
Wanted to install the nevest version and cannot do it because it depends and
conflicts with the same version of nvidia-glx.
From the control file:
Depends: nvidia-glx (>= 190.42)
Conflicts: libgl-dev, mesa-common-dev, nvidia-glx (>=
Yavor Doganov wrote:
> Thanks, that's clearly a separate issue; and 3 more binaries from
> avifile-utils are affected. I re-uploaded the package to mentors.d.n
> with these fixes included.
Good work. I have tried it and seems to work.
Best regards,
Peter
--
To UNSUBSCRIBE, email to de
Package: chise-base
Version: 0.3.0-1.1
Severity: serious
Build using current versions from unstable
sysdep.h:15: error: conflicting types for 'strnlen'
/usr/include/string.h:404: error: previous declaration of 'strnlen' was here
chise.c: In function 'CHISE_DS_open':
--
To UNSUBSCRIBE, emai
Package: checkinstall
Version: 1.6.1-9
Severity: serious
Build using newest versions from unstable
installwatch.c: In function '__instw_printdirent64':
installwatch.c:886: warning: format '%lld' expects type 'long long int', but
argument 4 has type '__ino64_t'
installwatch.c:886: warning: format
Package: bsdgames
Version: 2.17-16
Severity: serious
gcc -g -O2 -Wall -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Wcast-align -Wcast-qual -Wwrite-strings -
DNEW_STYLE -Iinclude -Iboggle/boggle -c boggle/boggle/bog.c -o
boggle/boggle/bog.o
In file included from boggle/boggle
Package: cadaver
Version: 2.1.8-release-1
Severity: serious
checking for struct tm.__tm_gmtoff... no
configure: zlib not supported
checking whether to enable ACL support in neon... no
checking for libgnutls-config... no
configure: error: could not find libgnutls-config in $PATH
make: *** [debian/b
Package: caudium
Version: 3:1.4.12-12.1
Severity: serious
Build in current unstable
/home/peter/rebuild/build/caudium/caudium-1.4.12/src/tools/../..//smartlink
/home/peter/rebuild/build/caudium/caudium-1.4.12/smartlink x86_64-linux-gnu-gcc
-fPIC -s -I./ -I. -o htpasswd ./htpasswd.c -
lcrypt
I
Package: cdrkit
Version: 9:1.1.9-1
Severity: serious
Build with current versions from unstable
[ 18%] Building C object wodim/CMakeFiles/wodimstuff.dir/cd_misc.o
In file included from
/home/peter/rebuild/build/cdrkit/cdrkit-1.1.9/wodim/cd_misc.c:38:
/home/peter/rebuild/build/cdrkit/cdrkit-1.1.9/
Zdenek Kabelac wrote:
> > I tried it and got following failure.
> >
> > /bin/bash ../../libtool --tag=CXX --mode=link g++ -Wall -g -O2
> > -ffast-math -fomit-frame-pointer -pipe -o avibench benchmark.o
> > ../../lib/libaviplay.la
> > libtool: link: g++ -Wall -g -O2 -ffast-math -fomit-frame-poi
Yavor Doganov wrote:
> forcemerge 526536 553940
> thanks
>
> > Tried to build your package and it fails to build with GNU binutils-gold.
>
> It fails to build with the default linker as well. This is fixed in a
> new upload, waiting for a sponsor. I haven't tested it with the gold
> linker, tho
Package: ball
Version: 1.3.0-1
Severity: serious
atom.sip: In function 'int convertTo_AtomType(PyObject*, void**, int*,
PyObject*)':
atom.sip:23: error: 'sipIsErr' was not declared in this scope
/home/peter/rebuild/build/ball/ball-1.3.0/include/BALL/FORMAT/resourceFile.h:
In function 'void assig
> On Tue, 11 Aug 2009, Peter Fritzsche wrote:
> > > What removes it? I suspect it's not dpkg... (or we would have noticed
> > > it already)
> >
> > Hm, only started dpkg. So I suspected it.
>
> Did your machine crash/lose power during an upgrade?
No, ne
> On Tue, 11 Aug 2009, Peter Fritzsche wrote:
> > > What removes it? I suspect it's not dpkg... (or we would have noticed
> > > it already)
> >
> > Hm, only started dpkg. So I suspected it.
>
> Did your machine crash/lose power during an upgrade?
No, ne
tags 541077 + unreproducible
thanks
> On Tue, 11 Aug 2009, Peter Fritzsche wrote:
> > Ok, tried again and it seems to be that the first time it gets installed
> > it exists. The next time it is removed and doesnt appear again.
>
> What removes it? I suspect it's not
Package: libc6
Version: 2.9-24
Ok, tried again and it seems to be that the first time it gets installed it
exists. The next time it is removed and doesnt appear again.
So
$ /var/cache/apt/archives/libc6_2.9-24_amd64.deb
would install /var/lib/dpkg/info/libc6.shlibs
and
$ /var/cache/apt/archives/
Package: libc6
Version: 2.9-24
Severity: grave
I tried to rebuild some packages and they all fail with
dpkg-shlibdeps: error: no dependency information found for /lib/libc.so.6
ls /var/lib/dpkg/info/libc6.shlibs
ls: cannot access /var/lib/dpkg/info/libc6.shlibs: No such file or directory
Other
Package: kdebase-workspace-bin
Version: 4:4.2.4-1+b1
I am am a little bit confused. Why is the severity of this bug grave? When I
read http://www.debian.org/Bugs/Developer#severities it doesn't fulfill the
severity for grave in my opinion. Maybe important.
Isn't nm aka plasma-widget-networkmana
25 matches
Mail list logo