m...@linux.it (Marco d'Itri) writes:
> On Jul 22, Alex Romosan wrote:
>
>> for some strange reason udev assumes all cdrom devices are scsi so as a
>> consequence my ide cdrom drive is being ignored. i modified 60-cdrom_id.rules
> What happens if you use a standard D
Package: cdrom
Severity: important
for some strange reason udev assumes all cdrom devices are scsi so as a
consequence my ide cdrom drive is being ignored. i modified 60-cdrom_id.rules
to check for ide drives as well and now the cdrom/dvd links are being created
once again. this is my modified cd
Package: libleptonica
Version: 1.67-0ubuntu1
Severity: normal
the bug report is actually for the newwer version which cannot be installed
because it depends on a non existent libgif package. please remove that
dependency and re-upload.
-- System Information:
Debian Release: wheezy/sid
APT prefe
Julien BLACHE writes:
> It's not optional as far as Debian is concerned, and that's what
> matters here.
dude, where did you come up with this stuff? what next, you are going to
tell me that i have to use gnome, or ext3, or whatever? i can see that
you think the job of a distribution is to tell
ow...@bugs.debian.org (Debian Bug Tracking System) writes:
> ACL are required, and that's all. ConsoleKit already requires ACL
> support and the standard Debian kernel has ACL enabled. If you don't
> use the standard kernel, now would be a good time to review your
> custom kernel configuration.
a
Package: libsane
Version: 1.0.22-1
Severity: important
if ACLs are not enabled in the kernel setfacl fails with 'Operation not
supported' and the permission is not changed for the device file. a
better approach would be to use chgrp and chmod on the device file,
i.e. replace RUN+="/bin/setfacl -m
Julien Cristau writes:
> On Thu, Apr 30, 2009 at 00:52:47 -0700, Jakob wrote:
>
>> I have X configured with two screens (without Xinerama) like this:
>>
>> Section "ServerLayout"
>> Identifier "Default Layout"
>> Screen 0 "Screen0" 0 0
>> Screen 1 "Screen1" Righ
Package: fvwm
Version: 1:2.5.27.ds-9
Severity: normal
looks like since the last couple of releases /etc/X11/fvwm/system.fvwm2rc
is ignored in favor of /usr/share/fvwm/system.fvwm2rc. i am not sure why
two system-wide configuration are shipped, but for the longest time the
config in /etc/X11 was us
Package: kernel-package
Version: 12.014
Severity: normal
when building the the kernel modules make-kpkg should just use the revision
number of the kernel we are building against instead of blowing away the
debian directory and coming up with its own version number. the previous
series (11.xx) of t
Cyril Brulebois <[EMAIL PROTECTED]> writes:
> Alex Romosan <[EMAIL PROTECTED]> (12/11/2008):
>
>> but this seems silly. shouldn't the current directory be appended to
>> the end of the system path so system modules are loaded first and then
>> if they don
as intended, i guess, this patch breaks loading modules from the
current directory but i have scripts that need to load extra modules
from the current directory. how does one do it now? i've modified my
scripts to do
import sys
sys.path.append(".")
import Module
but this seems silly. shouldn't t
Package: xulrunner-dev
Version: 1.9~rc2-2
Severity: important
pkg-config --variable=idldir libxul
returns
/usr/share/idl/xulrunner-1.9
but the idl files are installed in stable/unstable
i assume idldir should be defined as /usr/share/idl/xulrunner-1.9/stable
in /usr/lib/pkgconfig/libxul.pc and
Package: subversion
Version: 1.4.6dfsg1-2.1
Severity: grave
tried to do an update this morning on an amd64 machine and i got
the following:
svn: Unrecognized URL scheme for
'http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk'
the same repository is accessible from an i386 machine. repos
Cyril Brulebois <[EMAIL PROTECTED]> writes:
> Do you have such a recursive symlink, or was it just an impression you
> initially had?
oops, ~/.blender/scripts/bpydata doesn't point to itself. instead, it
correctly points to the directory up on level. sorry for the
confusion.
--alex--
--
| I be
Cyril Brulebois <[EMAIL PROTECTED]> writes:
> Starting blender should add the following symlink:
> | ~/.blender/scripts/bpymodules -> /usr/share/blender/scripts/bpymodules
>
> and you should get your scripts back.
shouldn't that be ~/.blender/scripts/bpymodules ->
/usr/share/blender/scripts/blend
Cyril Brulebois <[EMAIL PROTECTED]> writes:
> could you please paste the output of the following commands (removing
> any entry that could hurt your privacy, of course):
> | ls -l ~/.blender/
> | ls -l ~/.blender/scripts
>
ls -l .blender/
0 lrwxrwxrwx 1 romosan users 29 Jan 29 13:57 .Bla
Package: blender
Version: 2.45-2
Severity: important
trying to import a 3ds file in blender i get:
Compiled with Python version 2.4.4.
Checking for installed Python... got it!
Traceback (most recent call last):
File "", line 123, in ?
ImportError: No module named BPyImage
if i move /usr/share/
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> * Alex Romosan <[EMAIL PROTECTED]> [2007-04-19 17:52]:
>> compiling with -gstabs+ and -O2 still causes g++ to crash.
>
> Really? With g++-4.1 4.1.1-21, or which version do you have?
yes. this is on amd64 with g++ 4.1.1-
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> * Alex Romosan <[EMAIL PROTECTED]> [2006-11-02 09:54]:
>> if i try to compile vamos from cvs i get:
> ...
>> the code seems to be okay, and compiling with -O0 works so it's probably
>> gcc's faul
Russ Allbery <[EMAIL PROTECTED]> writes:
> I'm starting to suspect that there's something wrong with your
> openafs-modules-source package or the untarring thereof that's
> causing you to not get the latest source. I have no idea what that
> might be, but your original bug report included the patc
Russ Allbery <[EMAIL PROTECTED]> writes:
> By vanilla, do you mean the stock Debian packages or building your own?
by vanilla i mean the standard linus kernel from kernel.org that i
built myself. i don't know how it would work for the standard debian
kernel. that particular piece of openafs code
Russ Allbery <[EMAIL PROTECTED]> writes:
> I can't duplicate this. 1.4.2-2 builds and loads fine for me on a
> 2.6.18-1-amd64 kernel, whereas it was failing before with the previous
> problem. Upstream has changed somewhat the approach that they were taking
> with working around this issue, so t
Package: openafs-modules-source
Version: 1.4.2-2
Severity: grave
Tags: patch
i think the first bug report got mangled, so i am trying again.
using the lates openafs-module i get:
openafs: module license 'http://www.openafs.org/dl/license10.html' taints kernel
.
openafs: Unknown symbol tasklist_l
Randall Donald <[EMAIL PROTECTED]> writes:
> On Thu, 2006-10-12 at 11:14 -0700, Alex Romosan wrote:
>> Randall Donald <[EMAIL PROTECTED]> writes:
>>
>> > On Thu, 2006-10-12 at 10:12 -0700, Alex Romosan wrote:
>> >> Package: nvidia-glx
Randall Donald <[EMAIL PROTECTED]> writes:
> On Thu, 2006-10-12 at 10:12 -0700, Alex Romosan wrote:
>> Package: nvidia-glx
>> Version: 1.0.8774-3
>> Severity: normal
>
>
> 1.0.8774-5 will be in today's upgrade with the fix.
there are still problems eve
Package: nvidia-glx
Version: 1.0.8774-3
Severity: normal
trying to upgrade nvidia-glx i get this:
Preparing to replace nvidia-glx 1.0.8774-3 (using
.../nvidia-glx_1.0.8774-4_amd64.deb) ...
dpkg-divert: `diversion of /usr/lib/libGL.so to
/usr/lib/nvidia/libGL.so.xlibmesa by nvidia-glx' clashes wit
Package: lib32readline5-dev
Version: 5.1-8
Followup-For: Bug #386345
i think there is a small typo in debian/rules for amd64. ARCH32 is
defined as amd64 but it should be i386. this patch:
--- rules.orig 2006-09-21 12:54:19.0 -0700
+++ rules 2006-09-21 12:47:36.0 -0700
@@ -4
Package: nis
Version: 3.17-1
Severity: important
if dbus is not running (or installed) ypbind fails to start with the
following error:
Connection to D-BUS system message bus failed: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory.
installing and starting d
Package: grub
Version: 0.97-11
Severity: normal
for some strage reason update-grub lists the final release kernel after
the release candidate ones. for example, the order in my current
menu.lst is:
2.6.17-rc4
2.6.17-rc5
2.6.17-rc6
2.6.17
i don't know why it does this as ls lists 2.6.17 before th
Friedrich Delgado Friedrichs <[EMAIL PROTECTED]> writes:
> I've sometimes noted in the past that 3D accelerated hacks from the
> xscreensaver package ran about 50% displaced to the left and I can
> sometimes provoke /usr/lib/xscreensaver/lament to displace its
> picture by using opaque-resize in f
Package: linux-kernel-headers
Version: 2.6.16.20-1
Severity: normal
kernel_ulong_t is defined in /usr/include/linux/input.h only if
__KERNEL__ is defined, so input_device_id should be only defined under
the same conditions. this patch fixes the problem:
--- input.h.orig2006-06-05 10:18:23
Joey Hess <[EMAIL PROTECTED]> writes:
> I've reopened this bug because xdm 1:1.0.1-5 remains broken exactly as
> before; xdm-config refers to a nonexistant Xsetup_0, and if I fix that
> xdm still fails on login with this in the log:
>
> error opening security policy file /usr/lib/xserver/SecurityP
tions(+), 1 deletion(-)
>
> diff -u nte-2.3/debian/control nte-2.3/debian/control
> --- nte-2.3/debian/control
> +++ nte-2.3/debian/control
> @@ -2,7 +2,7 @@
> Section: net
> Priority: optional
> Maintainer: Alex Romosan <[EMAIL PROTECTED]>
> -Build-Depends: de
Package: xdm
Version: 6.9.0.dfsg.1-1
Severity: important
after upgrading /etc/X11/xdm/xdm-config is empty and as such xdm can't
find any configuration files and it's kind of useless. copying
xdm-config from a system that wasn't upgraded fixes the problem.
-- System Information:
Debian Release: te
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> Well, with 10.015 (currently in http://incoming.debian.org/) I
> have gone back to the time tested debugging tool, the print
> statement. Could you try with 10.015, and see if we can discover what
> was going wrong?
whatever changes happen
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> Unfortunately, there is not a whole lot of detail to go on
> here. As for the clean problem, do you see ./stamp-building? If so,
> that is the culprit; normally, make-kpkg creates stamp-building while
> calling dpkg-buildpackage (which in t
Package: libboost-dev
Version: 1.33.0-1
Severity: important
trying to compile this program:
#include
int main()
{
return 0;
}
with g++ 4.0.1-7 i get:
c++ iter.cc
/usr/include/boost/iterator/counting_iterator.hpp:32: error:
'mpl_::bool_::value' is not a valid template argument for typ
Package: libgsf-1
Version: 1.12.3-3
Severity: normal
since this is the basic version which doesn't provide gnome-specific
extensions it shouldn't depend on the monstrosity called gconf2. please fix.
btw, the dependecies bellow are for 1.12.2 because i put the package on
hold until the problem is f
"Kevin B. McCarty" <[EMAIL PROTECTED]> writes:
> Hmm. What compiler did you use to build Paw from CERN CVS? Maybe this
> is a new bug in gcc 4.0. I've just tested Paw 2005.05.09-3 on Sid
> (where it breaks as you say) and 2004.11.04-3 on Sarge (where it works
> fine). Neither upstream nor I ch
Package: paw
Version: 2005.05.09-3
Severity: important
i am trying to use ntuples but paw crashes with a segmentation
violation:
PAW > nt/cr 1 'test' 1 ! ! x
PAW > n/pri 1
*** Break *** Segmentation violation
Traceq lun = 0, level = 99
TRACEQ. In-line trace-back still not available.
Long
Matthias Klose <[EMAIL PROTECTED]> writes:
> Alex Romosan writes:
>> Package: libg2c0-dev
>> Version: 1:3.4.4-7
>> Severity: minor
>>
>> i am not really sure why /usr/lib64 is includede in a package for a 32
>> bit architecture (i386 in this ca
Package: libg2c0-dev
Version: 1:3.4.4-7
Severity: minor
i am not really sure why /usr/lib64 is includede in a package for a 32
bit architecture (i386 in this case). please move them to their own
package.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy:
Package: linux-kernel-headers
Version: 2.6.13+0rc3-1
Severity: important
linux/joystick.h contains the following:
#if BITS_PER_LONG == 64
#define JS_DATA_SAVE_TYPE JS_DATA_SAVE_TYPE_64
#elif BITS_PER_LONG == 32
#define JS_DATA_SAVE_TYPE JS_DATA_SAVE_TYPE_32
#else
#error Unexpected BITS_PER_LONG
#
Package: libglu1-xorg-dev
Version: 6.8.2.dfsg.1-2
Severity: normal
since this package was presumably compiled with gcc v4 (libglu1-xorg
provides libglu1c2) it should depend instead on libstdc++6-4.0-dev.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy:
Package: openssh-client
Version: 1:4.1p1-5
Severity: normal
running 'ssh-add < /dev/null' i get:
ssh_askpass: exec(/usr/lib/openssh/ssh-askpass): No such file or directory
i think it should call /usr/bin/ssh-askpass which, at least for me,
points to /usr/lib/openssh/gnome-ssh-askpass
-- System
Rene Engelhard <[EMAIL PROTECTED]> writes:
> WTF? did you not reopen the old bug but file a new one?
sorry, i get really annoyed when people close a bug without actually
fixing it (and in this case introducing it since it wasn't there
before, at least for i386). isn't this the "debian way"? :-(
Package: openoffice.org-bin
Version: 1.1.3-5
Severity: important
bug #293551 complained about the same thing and it got closed with the
following explanation: build gnomevfs library sanely. obviously this
is not corect as the package suddenly (at least on i386) depends on
gnome libraries. please f
47 matches
Mail list logo