Sorry, I've just understood that by default in debian/rules it is
installed into /usr/share/sysvinit/inittab.
I will look at this problem this evening and will be more careful.
signature.asc
Description: PGP signature
> Note, this patch will only affect new installations. Do we want to
> modify existing installations? If we do, which ones? As the inittab
> file by good reasons is not a conffile, such modification to existing
> installations would have to be done carefully by the postinst script.
As far as
Control: tags -1 + patch
I'd like to supply this bug with a patch. Ask to approve it. Thank you.
diff --git a/debian/share/inittab b/debian/share/inittab
index 04eabd6..f29288c 100644
--- a/debian/share/inittab
+++ b/debian/share/inittab
@@ -51,17 +51,17 @@ po::powerokwait:/etc/init.d/powerfail
Package: broadcom-sta-dkms
Version: 6.30.223.248-2
Severity: grave
Hello, dear Maintainer.
Recently I have upgraded my very old system shipped with Debian Jessie.
I have upgraded a pile of packages. Among others there were:
linux-headers-amd64
Bastian Blank wa...@debian.org writes:
Control: severity -1 important
Control: tags -1 moreinfo
On Sat, Aug 16, 2014 at 06:48:10PM +0400, Dmitrii Kashin wrote:
I suppose that
% /sbin/lvm vgchange -aay --sysinit /dev/null
is not enough, because it doesn't create nodes in my /dev
Aurelien Jarno aurel...@aurel32.net writes:
On Thu, Aug 28, 2014 at 10:07:57AM +0400, Dmitrii Kashin wrote:
Package: libc-bin
Version: 2.19-9
Severity: grave
File: /sbin/ldconfig
Dear Maintainer,
I had an upgrade of libc6 and libc-bin packages up to the version
2.19-9 from 2.19-4
Package: libc-bin
Version: 2.19-9
Severity: grave
File: /sbin/ldconfig
Dear Maintainer,
I had an upgrade of libc6 and libc-bin packages up to the version
2.19-9 from 2.19-4 while executing `apt-get upgrade'. In the begin it
seemed as a usual upgrade but after a while (supposedly after these two
Package: lvm2
Version: 2.02.106-2
Severity: serious
File: /etc/init.d/lvm2
I suppose that
% /sbin/lvm vgchange -aay --sysinit /dev/null
is not enough, because it doesn't create nodes in my /dev, and it causes
an interrupt while the bootstrap.
This is the reason I've added this line:
% /sbin/lvm
Yves-Alexis Perez cor...@debian.org writes:
On lun., 2013-03-11 at 11:27 +0400, Dmitrii Kashin wrote:
Here I put file 02.pdf (sorry for non-english language). Just load it
and open page 247.
I love having 40 tinys parts of pdf flooding my inbox, thanks.
Sorry. It was a strange glitch of my
Package: epdfview
Version: 0.1.8-3
Severity: normal
I very often se a situation that epdfview don't show pages at all. I
see only grey background, and no pages.
Here I put file 02.pdf (sorry for non-english language). Just load it
and open page 247.
If you won't be able tp represent this bug, I
I am very sorry. It was my mistake. I saw into strace and revealed that
I forgot to mount /proc and /dev into my schroot sandbox for chromium.
Sorry. Just close it.
--
**
* jabber: free...@jabber.mipt.ru *
* Registered linux user #546240*
Eugene V. Lyubimkin jac...@debian.org writes:
On 2012-10-02 23:26, Dmitrii Kashin wrote:
Yes, I am. If you give a patch, I'll test it.
Please try the attached one.
It works fine, no more crashes.
Thanks a lot for solving the problem.
--
**
* jabber
Eugene V. Lyubimkin jac...@debian.org writes:
I cannot reproduce the bug myself but I have an idea what might cause
it. Are you willing to test a small patch (by downloading fbreader
Debian source package, applying the patch and rebuilding) if I post it?
Yes, I am. If you give a patch, I'll
Package: fbreader
Version: 0.12.10dfsg-7
Severity: important
When I start fbreader it immediatly crashes with a segmentation fault.
I don't know how to solve this problem. The sole thing I was able to
do is to run it under GDB. Here I put stack backtrace. I hope it will
be usefull.
Eugene V. Lyubimkin jac...@debian.org writes:
Hi Dmitrii,
Thank you for the report.
On 2012-10-01 21:00, Dmitrii Kashin wrote:
When I start fbreader it immediatly crashes with a segmentation fault.
I don't know how to solve this problem. The sole thing I was able to
do is to run
Just a correction to russian l10n.
This patch will solve the problem.
381c381
на нестандартном порту (не TCP/25), то добавьте два двоеточия и и номер
---
на нестандартном порту (не TCP/25), то добавьте два двоеточия и номер
--
**
* jabber:
I see another error.
AI1 try to play 6 clubs. AI2 pass. Player (me) bid whist with open
lists. Player took 5 lists. AI1 stay without 1 list.
Now, he should write 2 points to mountain. And player should write 10
whists to AI1. But I see only 6 whists.
I suppose it's a mistake in logic of the
17 matches
Mail list logo
