Bug#646467: supposed fix

2011-12-03 Thread Roman Dubtsov
On Sat, Dec 3, 2011 at 10:28 PM, Wolfram Sang w.s...@pengutronix.de
wrote: tags 646467 patch thanks
Thanks. Will apply as soon as possible.

-- 
:wbr



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#444717: stalonetray: Typo in --max-height option

2007-09-30 Thread Roman Dubtsov
Hi,

On 9/30/07, Christian Ohm [EMAIL PROTECTED] wrote:
 In src/settings.c on line 254 --man-height instead of --max-height
 is used, and when using --max-height the program doesn't start
 anymore.

Thanks for finding this out. Fixed in 0.7.2 (being uploaded to sf.net).

-- 
:wqa



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#443543: stalonetray: Program committed suicide

2007-09-22 Thread Roman Dubtsov
Hi,

Thanks for the bug report. The fix is in svn already (bugfixes/0.7
branch if you are interested), fixed package can be expected to appear
in debian repository within a week or so.

-- 
:wqa



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#319904: autofs: workaround

2006-05-23 Thread Roman Dubtsov
Package: autofs
Version: 4.1.4-10
Followup-For: Bug #319904


This bug can be worked around by using autofs module instead of autofs4.
Autofs will complain on boot, but it works for me...

Also, I would like to note that this bug was introduced somewhere after
2.6.13.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-1-k7
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages autofs depends on:
ii  libc6 2.3.6-9GNU C Library: Shared libraries
ii  ucf   2.0010 Update Configuration File: preserv

Versions of packages autofs recommends:
pn  nfs-commonnone (no description available)

-- debconf information:
  autofs/upgrade-from-broken-version:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#343592: yaird: IDE works in PIO mode only because of wrong ide driver included in initrd

2005-12-16 Thread Roman Dubtsov
Package: yaird
Version: 0.0.12-1
Severity: normal

Hello.

On my system (nforce2-based) yaird includes in initrd.img both amd74xx
and generic ide pci drivers and loads them in the following order

/sbin/insmod
'/lib/modules/2.6.15-rc5-2-k7-debug/kernel/drivers/ide/pci/generic.ko' 
/sbin/insmod
'/lib/modules/2.6.15-rc5-2-k7-debug/kernel/drivers/ide/pci/amd74xx.ko'

The result is that IDE drivers start woring in PIO mode only (both
channels are taken by generic driver.

NFORCE2: port 0x01f0 already claimed by ide0
NFORCE2: port 0x0170 already claimed by ide1
NFORCE2: neither IDE port enabled (BIOS)

The temporary solution is to build custom initrd.img, deleting
generic.ko and modifying init script (which also lacks insmod
ide-generic.ko).

Is seems that this problem was discussed in debian-user some time ago:
http://lists.debian.org/debian-user/2005/11/msg00390.html

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.13-1-k7
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages yaird depends on:
ii  cpio 2.6-9   GNU cpio -- a program to manage ar
ii  dash 0.5.3-1 The Debian Almquist Shell
ii  libc62.3.5-8.1   GNU C Library: Shared libraries an
ii  libhtml-template-perl2.7-1   HTML::Template : A module for usin
ii  libparse-recdescent-perl 1.94.free-1 Generates recursive-descent parser
ii  perl 5.8.7-9 Larry Wall's Practical Extraction 

yaird recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]