Re: Bug#930856: autopkgtest-build-qemu: captures something from host

2019-06-29 Thread Dmitry Bogatov
[ After futher investigation, this command fails with same error directly, without autopkgtest, so reassigning ] control: reassing -1 debootstrap control: retitle -1 debootstrap uses wrong keyring Dear maintainer of debootstrap, I can't create chroot due following error: # debootstrap

Bug#925545: busybox: please provide runscript file

2019-06-18 Thread Dmitry Bogatov
control: user ru...@packages.debian.org control: usertags -1 freeze [2019-06-16 00:20] Bastian Blank > Hi Dmitry Hi, Bastian > On Sat, Jun 15, 2019 at 06:37:03PM +, Dmitry Bogatov wrote: > > But, after all, we all volonteers here. So hereby I inform you, > > following a

Bug#925545: busybox: please provide runscript file

2019-06-15 Thread Dmitry Bogatov
control: reassign -1 src:busybox control: retitle -1 busybox: please provide runscript file -- second call Hello, dear maintainer. This bug, requesting addition of runscript file into package was filed some time ago, and got no response. It is quite unfortunate, since your review of could have

Bug#925545: udhcpd: support for Runit supervision system

2019-03-26 Thread Dmitry Bogatov
+++ busybox-1.30.1/debian/changelog 2019-03-24 11:24:02.0 + @@ -1,3 +1,9 @@ +busybox (1:1.30.1-3) UNRELEASED; urgency=medium + + * Add runscript for Runit system. + + -- Dmitry Bogatov Sun, 24 Mar 2019 11:24:02 + + busybox (1:1.30.1-2) unstable; urgency=high * Complete the fix

Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-20 Thread Dmitry Bogatov
[2018-12-19 10:42] Ricardo Peliquero > Anton Zinoviev > Wed, 5 Dec 2018 21:29:10 +0200: > > > On Wed, Dec 05, 2018 at 08:56:16AM +, Dmitry Bogatov wrote: > > > Suppose that we have a working bash shell with UTF-8 console where ñ > > displays properly.

Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-05 Thread Dmitry Bogatov
[2018-12-03 10:48] Ricardo Peliquero > > [ Dmitry Bogatov ] > > Hi, two years after, with libreadline8 in archives, does problem still > > persist? > > > Yes, the problem still persists; but, after investigating a little bit > more, it seems to me that it co