Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts

[Samuel Thibault]

MENGUAL Jean-Philippe, on mer. 22 mars 2017 03:57:37 +0100, wrote:
> And what about affecting shift-s or ctrl-s to run tts in the rescue
> mode?

That's not really simple to implement actually. One has to have a way to
start rescue mode anyway.

And it seems that just like me, people don't actually use the shortcuts,
so I have commited stealing them for speech.  I have updated the manual
and the wiki.

Samuel

Re: Bug#858478: unblock: lvm2/2.02.168-2

[Cyril Brulebois]

Hi,

Emilio Pozuelo Monfort  (2017-03-22):
> On 22/03/17 20:35, Bastian Blank wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Please unblock package lvm2/2.02.168-2.  It fixes a bunch of RC bugs.
> 
> Ack. Needs a kibi-ack.

Just tested an LVM install on top of RAID1 with no obvious issues, no
objections.
 

KiBi.


signature.asc
Description: Digital signature

Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts

[Nick Gawronski]

On 3/21/2017 7:40 PM, Samuel Thibault wrote:

Hello,

Somehow somebody managed to raise that there is no menu entry for
starting the rescue mode with speech synthesis enabled.  That actually
also raises the question of doing the same for expert install andHi, One issue 
with that is how do we know if we are totally blind what menu we are in and 
also if an option is selected properly or not?  I know the option to start the 
installation with software speech but when there are other menus to go threw 
with no speech how fast do they come up?  Why not add shortcuts to the main 
menu for speech or can one not just type in the shortcut then add 
speakup.synth=soft to start software speech as I tried that once but got 
nowhere?  Nick Gawronski
automated install.

It's really a matter of adding the menu entry: just copy/paste the
existing expert/rescue/automated entries, and append speakup.synth=soft
to it.

Now the question is: which keyboard shortcut to use?

For now, the only documented accessible keyboard shortcut is "s" to
start a speech-enabled installation.  I guess we don't want to add yet
other entries to the main menu, so we'd put these additional entries
under the "advanced options" submenu, which already has shortcut "a".
However, the natural "e", "r" and "a" shortcuts are already taken for
the non-speech versions.

Would it really be a problem to change the meaning of those shortcuts,
to make them start the speech versions instead of the non-speech
version?  I have to say I myself never used those shortcuts, since it's
so fast to just move down a few times when one is sighted :)

Samuel

Re: Bug#858481: unblock: bind9/1:9.10.3.dfsg.P4-12.1

[Cyril Brulebois]

Hi,

Emilio Pozuelo Monfort  (2017-03-22):
> On 22/03/17 20:41, Bastian Blank wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Please unblock package bind9.  It just fixes the a bit illadviced and
> > unconfigurable use of /dev/random in several critical parts of the named
> > process.
> 
> Seems fine to me, but needs a kibi-ack for the udeb.

Not used on Linux/released ports, only on non-Linux ones, so cc-ing them
for information; and obviously no objections from me.


KiBi.

> Emilio
> 
> > 
> > diff -Nru bind9-9.10.3.dfsg.P4/debian/changelog 
> > bind9-9.10.3.dfsg.P4/debian/changelog
> > --- bind9-9.10.3.dfsg.P4/debian/changelog   2017-02-19 23:39:32.0 
> > +0100
> > +++ bind9-9.10.3.dfsg.P4/debian/changelog   2017-03-17 19:07:16.0 
> > +0100
> > @@ -1,3 +1,11 @@
> > +bind9 (1:9.10.3.dfsg.P4-12.1) unstable; urgency=medium
> > +
> > +  * Non-maintainer upload.
> > +  * Use /dev/urandom to avoid blocking in the server process.
> > +(closes: #854243)
> > +
> > + -- Bastian Blank   Fri, 17 Mar 2017 19:07:16 +0100
> > +
> >  bind9 (1:9.10.3.dfsg.P4-12) unstable; urgency=high
> >  
> >* Merge and accept the non-maintainer upload.
> > diff -Nru bind9-9.10.3.dfsg.P4/debian/rules 
> > bind9-9.10.3.dfsg.P4/debian/rules
> > --- bind9-9.10.3.dfsg.P4/debian/rules   2017-02-19 23:38:45.0 
> > +0100
> > +++ bind9-9.10.3.dfsg.P4/debian/rules   2017-03-17 17:56:39.0 
> > +0100
> > @@ -72,6 +72,7 @@
> > --enable-filter- \
> > --enable-native-pkcs11 \
> > 
> > --with-pkcs11=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/softhsm/libsofthsm2.so \
> > +   --with-randomdev=/dev/urandom \
> > $(EXTRA_FEATURES)
> >  
> > touch $@
> > 
> > unblock bind9/1:9.10.3.dfsg.P4-12.1
> > 
> > -- System Information:
> > Debian Release: 9.0
> >   APT prefers unstable
> >   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> > 
> > Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)


signature.asc
Description: Digital signature

Re: Bug#858481: unblock: bind9/1:9.10.3.dfsg.P4-12.1

[Emilio Pozuelo Monfort]

On 22/03/17 20:41, Bastian Blank wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package bind9.  It just fixes the a bit illadviced and
> unconfigurable use of /dev/random in several critical parts of the named
> process.

Seems fine to me, but needs a kibi-ack for the udeb.

Emilio

> 
> diff -Nru bind9-9.10.3.dfsg.P4/debian/changelog 
> bind9-9.10.3.dfsg.P4/debian/changelog
> --- bind9-9.10.3.dfsg.P4/debian/changelog 2017-02-19 23:39:32.0 
> +0100
> +++ bind9-9.10.3.dfsg.P4/debian/changelog 2017-03-17 19:07:16.0 
> +0100
> @@ -1,3 +1,11 @@
> +bind9 (1:9.10.3.dfsg.P4-12.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Use /dev/urandom to avoid blocking in the server process.
> +(closes: #854243)
> +
> + -- Bastian Blank   Fri, 17 Mar 2017 19:07:16 +0100
> +
>  bind9 (1:9.10.3.dfsg.P4-12) unstable; urgency=high
>  
>* Merge and accept the non-maintainer upload.
> diff -Nru bind9-9.10.3.dfsg.P4/debian/rules bind9-9.10.3.dfsg.P4/debian/rules
> --- bind9-9.10.3.dfsg.P4/debian/rules 2017-02-19 23:38:45.0 +0100
> +++ bind9-9.10.3.dfsg.P4/debian/rules 2017-03-17 17:56:39.0 +0100
> @@ -72,6 +72,7 @@
>   --enable-filter- \
>   --enable-native-pkcs11 \
>   
> --with-pkcs11=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/softhsm/libsofthsm2.so \
> + --with-randomdev=/dev/urandom \
>   $(EXTRA_FEATURES)
>  
>   touch $@
> 
> unblock bind9/1:9.10.3.dfsg.P4-12.1
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> 

Re: Bug#858478: unblock: lvm2/2.02.168-2

[Emilio Pozuelo Monfort]

On 22/03/17 20:35, Bastian Blank wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package lvm2/2.02.168-2.  It fixes a bunch of RC bugs.

Ack. Needs a kibi-ack.

Cheers,
Emilio

> 
> diff --git a/debian/changelog b/debian/changelog
> index dd72cf181..0af409a67 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,11 @@
> +lvm2 (2.02.168-2) unstable; urgency=medium
> +
> +  * Don't try to disable cluster locking on clvm purge. (closes: #856696)
> +  * Drop symlinks for private libs. (closes: #857954)
> +  * Deny writemostly/writebehind during raid1 resync. (closes: #855895)
> +
> + -- Bastian Blank   Fri, 17 Mar 2017 17:29:47 +0100
> +
>  lvm2 (2.02.168-1) unstable; urgency=medium
>  
>* New upstream release.
> diff --git a/debian/clvm.prerm b/debian/clvm.prerm
> deleted file mode 100644
> index fc683cc7c..0
> --- a/debian/clvm.prerm
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -#!/bin/sh
> -
> -set -e
> -
> -case "$1" in
> -remove)
> -lvmconf --disable-cluster
> -;;
> -esac
> -
> -#DEBHELPER#
> -
> -exit 0
> diff --git a/debian/libdevmapper-dev.install b/debian/libdevmapper-dev.install
> index b02ef0b55..3cf999c4d 100644
> --- a/debian/libdevmapper-dev.install
> +++ b/debian/libdevmapper-dev.install
> @@ -1,3 +1,5 @@
>  usr/include/libdevmapper*
> -usr/lib/*/libdevmapper*.so
> -usr/lib/*/pkgconfig/devmapper*
> +usr/lib/*/libdevmapper.so
> +usr/lib/*/libdevmapper-event.so
> +usr/lib/*/pkgconfig/devmapper.pc
> +usr/lib/*/pkgconfig/devmapper-event.pc
> diff --git 
> a/debian/patches/0012-lvchange-reject-writemostly-writebehind-on-raid1-dur.patch
>  
> b/debian/patches/0012-lvchange-reject-writemostly-writebehind-on-raid1-dur.patch
> new file mode 100644
> index 0..89b6801b4
> --- /dev/null
> +++ 
> b/debian/patches/0012-lvchange-reject-writemostly-writebehind-on-raid1-dur.patch
> @@ -0,0 +1,146 @@
> +From 27e1059ec6e67a4ac0faaf0f53cd086ac4ed0e35 Mon Sep 17 00:00:00 2001
> +From: Heinz Mauelshagen 
> +Date: Thu, 23 Feb 2017 15:09:29 +0100
> +Subject: lvchange: reject writemostly/writebehind on raid1 during resync
> +
> +The MD kernel raid1 personality does no use any writemostly leg as the 
> primary.
> +
> +In case a previous linear LV holding data gets upconverted to
> +raid1 it becomes the primary leg of the new raid1 LV and a full
> +resynchronization is started to update the new legs.
> +
> +No writemostly and/or writebehind setting may be allowed during
> +this initial, full synchronization period of this new raid1 LV
> +(using the lvchange(8) command), because that would change the
> +primary (i.e the previous linear LV) thus causing data loss.
> +
> +lvchange has a bug not preventing this scenario.
> +
> +Fix rejects setting writemostly and/or writebehind on resychronizing raid1 
> LVs.
> +
> +Once we have status in the lvm2 metadata about the linear -> raid 
> upconversion,
> +we may relax this constraint for other types of resynchronization
> +(e.g. for user requested "lvchange --resync ").
> +
> +New lvchange-raid1-writemostly.sh test is added to the test suite.
> +
> +Resolves: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855895
> +---
> + lib/metadata/metadata-exported.h |  1 +
> + lib/metadata/raid_manip.c|  8 ++-
> + test/shell/lvchange-raid1-writemostly.sh | 41 
> 
> + tools/lvchange.c | 15 
> + 4 files changed, 64 insertions(+), 1 deletion(-)
> + create mode 100644 test/shell/lvchange-raid1-writemostly.sh
> +
> +diff --git a/lib/metadata/metadata-exported.h 
> b/lib/metadata/metadata-exported.h
> +index cdd4984c1..080073925 100644
> +--- a/lib/metadata/metadata-exported.h
>  b/lib/metadata/metadata-exported.h
> +@@ -1212,6 +1212,7 @@ int lv_raid_replace(struct logical_volume *lv, int 
> force,
> + struct dm_list *remove_pvs, struct dm_list *allocate_pvs);
> + int lv_raid_remove_missing(struct logical_volume *lv);
> + int partial_raid_lv_supports_degraded_activation(const struct 
> logical_volume *lv);
> ++int lv_raid_in_sync(const struct logical_volume *lv);
> + /* --  metadata/raid_manip.c */
> + 
> + /* ++  metadata/cache_manip.c */
> +diff --git a/lib/metadata/raid_manip.c b/lib/metadata/raid_manip.c
> +index 7e591e988..00e5551a3 100644
> +--- a/lib/metadata/raid_manip.c
>  b/lib/metadata/raid_manip.c
> +@@ -268,7 +268,7 @@ static int _deactivate_and_remove_lvs(struct 
> volume_group *vg, struct dm_list *r
> +  * Returns: 1 if in-sync, 0 otherwise.
> +  */
> + #define _RAID_IN_SYNC_RETRIES  6
> +-static int _raid_in_sync(struct logical_volume *lv)
> ++static int _raid_in_sync(const struct logical_volume *lv)
> + {
> + int retries = _RAID_IN_SYNC_RETRIES;
> + dm_percent_t sync_percent;
> +@@ -299,6 +299,12 @@ static int _raid_in_sync(struct logical_volume *lv)
> + return (sync_percent 

Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts

[Samuel Thibault]

Nick Gawronski, on mer. 22 mars 2017 17:46:09 -0500, wrote:
> Why not add shortcuts to the main menu for speech

That's precisely what I am suggesting in this thread.

Samuel

Bug#857132: console-setup: additional info needed ?

[Karsten Hilbert]

On Wed, Mar 22, 2017 at 08:48:16PM +0200, Anton Zinoviev wrote:

> > 2017-03-22 13:05:13.364493514 +0100 /etc/console-setup/cached_setup_font.sh
> > 2017-03-22 13:05:13.364493514 +0100 
> > /etc/console-setup/cached_setup_keyboard.sh
> > 2017-03-22 13:05:13.364493514 +0100 
> > /etc/console-setup/cached_setup_terminal.sh
> > 2017-03-22 12:54:59.368053266 +0100 
> > /etc/console-setup/cached_UTF-8_del.kmap.gz
> > 2017-03-22 12:53:10.459239057 +0100 /etc/default/console-setup
> > 2017-03-07 09:26:01.171789164 +0100 /etc/default/keyboard
> 
> It seems something has changed /etc/default/console-setup. If this file 
> is changed, then boot scripts of console-setup will recreate the 
> cached_* files in /etc.
> 
> Do you know what has caused this file to be changed?

That was me, again, because I hoped that setting

# Change to "yes" and setupcon will explain what is being doing
VERBOSE_OUTPUT="yes"

from "no" to "yes" would generate helpful debugging output.
However, I haven't been able to find any :-/

> Something unrelated that might explain the bug is this: maybe this 
> system runs X

It does, yes.

> but doesn't have framebuffer on the console?

Oh, it does:

dmseg:
[   20.377384] fbcon: inteldrmfb (fb0) is primary device
...
[   21.054248] Console: switching to colour frame buffer device 170x48
[   21.084983] i915 :00:02.0: fb0: inteldrmfb frame buffer device


fbset -v -i

Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven

Opening frame buffer device `/dev/fb0'
Using current video mode from `/dev/fb0'

mode "1366x768"
geometry 1366 768 1366 768 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode

Getting further frame buffer information
Frame buffer device information:
Name: inteldrmfb
Address : 0xd0048000
Size: 4227072
Type: PACKED PIXELS
Visual  : TRUECOLOR
XPanStep: 1
YPanStep: 1
YWrapStep   : 0
LineLength  : 5504
Accelerator : No

> BTW, instead of `systemctl restart console-setup.service` you can use 
> the command `setupcon`.

OK, I will resort to that in order to minimize what is involved.

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Bug#857132: console-setup: additional info needed ?

[Anton Zinoviev]

On Wed, Mar 22, 2017 at 05:56:04PM +0100, Karsten Hilbert wrote:

> 2017-03-22 13:05:13.364493514 +0100 /etc/console-setup/cached_setup_font.sh
> 2017-03-22 13:05:13.364493514 +0100 
> /etc/console-setup/cached_setup_keyboard.sh
> 2017-03-22 13:05:13.364493514 +0100 
> /etc/console-setup/cached_setup_terminal.sh
> 2017-03-22 12:54:59.368053266 +0100 
> /etc/console-setup/cached_UTF-8_del.kmap.gz
> 2017-03-22 12:53:10.459239057 +0100 /etc/default/console-setup
> 2017-03-07 09:26:01.171789164 +0100 /etc/default/keyboard

It seems something has changed /etc/default/console-setup. If this file 
is changed, then boot scripts of console-setup will recreate the 
cached_* files in /etc.

Do you know what has caused this file to be changed?  Its time seems to 
be only few minutes before the time of the reboot.  I can't think of 
anything in the scripts of console-setup that can cause changes in this 
file.

Something unrelated that might explain the bug is this: maybe this 
system runs X but doesn't have framebuffer on the console?  In this case 
the problem is hardware related and the best solution is to use 
framebuffer.

BTW, instead of `systemctl restart console-setup.service` you can use 
the command `setupcon`.

Anton Zinoviev

Bug#857132: console-setup: additional info needed ?

[Karsten Hilbert]

On Wed, Mar 22, 2017 at 04:49:27PM +0200, Anton Zinoviev wrote:

> Thanks. :) Well, can you report the state of the affairs before you run
> 
>   systemctl restart console-setup.service
> 
> ls --full-time /etc/default/{console-setup,keyboard} 
> /etc/console-setup/cached_*

Attached.

Full times directly after a reboot before manually restarting
console-setup.

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
-rwxr-xr-x 1 root root  465 2017-03-22 13:05:13.364493514 +0100 
/etc/console-setup/cached_setup_font.sh
-rwxr-xr-x 1 root root  358 2017-03-22 13:05:13.364493514 +0100 
/etc/console-setup/cached_setup_keyboard.sh
-rwxr-xr-x 1 root root   73 2017-03-22 13:05:13.364493514 +0100 
/etc/console-setup/cached_setup_terminal.sh
-rw-r--r-- 1 root root 4377 2017-03-22 12:54:59.368053266 +0100 
/etc/console-setup/cached_UTF-8_del.kmap.gz
-rw-r--r-- 1 root root 2061 2017-03-22 12:53:10.459239057 +0100 
/etc/default/console-setup
-rw-r--r-- 1 root root  587 2017-03-07 09:26:01.171789164 +0100 
/etc/default/keyboard

Re: can't get the debian-installer code by svn

[Philip Hands]

Roger Shimizu  writes:

> On Wed, 22 Mar 2017 16:17:08 +0800 (CST)
> harryyue123  wrote:
>
>>  I want get a source code of debian-installer,but failed.the error 
>> message is :
>>   
>> harry@BJ-LD-1229:~/Project/000debian8.7$ svn co 
>> svn://anonscm.debian.org/svn/d-i/trunk d-i
>
> Where did you get the URL of SVN repo?
>
> Now the repo has been moved to git:
>  https://anonscm.debian.org/git/d-i/debian-installer.git

The git repo is for for the build system for d-i, whereas the svn is the
repo for the top level directory which then lets you check out
everything else, including that git repo and the repos for the udeb
packages, as described here:

  https://wiki.debian.org/DebianInstaller/CheckOut

having just checked out the svn here, it worked, so I suspect that the
problem that happened with the svn checkout might have been simply that
the Alioth server was having a funny five minutes.

It's probably worth retrying the svn checkout.

If I then run:

=-=-=-=-=-
/tmp/d-i/debian-installer % svn log | head  

 0 50006 16:24:48 Wed 22.03.2017

r70637 | holgerw | 2017-03-19 21:07:46 +0100 (Sun, 19 Mar 2017) | 2 lines

Proofreading for Catalan boot-installer.po by Innocent De Marchi, thanks.


r70636 | mck-guest | 2017-03-19 11:02:27 +0100 (Sun, 19 Mar 2017) | 2 lines

[l10n] Update Czech translation of d-i manual
=-=-=-=-=-

You can see that the SVN really is still in use (at least it was on Sunday).

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#857132: console-setup: additional info needed ?

[Anton Zinoviev]

On Wed, Mar 22, 2017 at 03:19:57PM +0100, Karsten Hilbert wrote:
> On Wed, Mar 22, 2017 at 03:02:28PM +0200, Anton Zinoviev wrote:
> > 
> >   2. the bug still exists and each time the system boots, it recreates 
> > these three files.  In this case we have to find out the cause of this.
> 
> The latter: currently, after each boot, I manually run
> 
>   systemctl restart console-setup.service
> 
> which fixes the console problem for me until the next boot.
> That's why those files are from today.

This will update thethree files /etc/console-setup/cached_setup* if the 
times of /etc/default/{keyboard,console-setup} are more recent.  On the 
other hand, times of the files in /etc/default/* are not supposed to 
change.
 
> >  And what about the files 
> > /etc/default/{keyboard,console-setup} -- do their times change too?
> 
> Likely because of the above, too.

Actualy these files should change only if console-setup is upgraded or 
the admin runs dpkg-reconfigure.

> Feel free to ask for more information you may need.

Thanks. :) Well, can you report the state of the affairs before you run

systemctl restart console-setup.service

ls --full-time /etc/default/{console-setup,keyboard} /etc/console-setup/cached_*

Anton Zinoviev

Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts

[Steve McIntyre]

On Wed, Mar 22, 2017 at 08:49:32AM +0100, Philip Hands wrote:
>Steve McIntyre  writes:
>>
>> I've personally never used the shortcuts, but I'd be curious if
>> anybody might be for automated testing possibly? It'd be easier to do
>> that than parse the boot menus...
>
>I'm certainly up for doing automated testing -- to do proper testing
>we'd need to work out how to do recognition of the speech sounds made,
>and then I'd want to plug that recognition into the back of cucumber, so
>that we could add the tests to our jenkins jobs.
>
>If anyone has any pointers for doing any of that, particularly the
>recognition bit, that would be most helpful.
>
>FWIW I had not bothered to even notice that the shortcuts exist, let
>alone used them, so I fully support reusing the shortcuts for starting
>speech-enabled versions.

Ack, that's what I was hoping you might say. :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis

Bug#857132: console-setup: additional info needed ?

[Karsten Hilbert]

On Wed, Mar 22, 2017 at 03:02:28PM +0200, Anton Zinoviev wrote:

> > > ls -l /etc/console-setup/
> > 
> > -rwxr-xr-x   1 root root   465 Mar 22 11:20 cached_setup_font.sh
> > -rwxr-xr-x   1 root root   358 Mar 22 11:20 cached_setup_keyboard.sh
> > -rwxr-xr-x   1 root root73 Mar 22 11:20 cached_setup_terminal.sh
> 
> Hm, the times of these three are too recent. I can see two possibilities:
>
>   1. either the bug no longer exists in this system, in which case we 
> have to find out what caused these files to be created, or
> 
>   2. the bug still exists and each time the system boots, it recreates 
> these three files.  In this case we have to find out the cause of this.

The latter: currently, after each boot, I manually run

systemctl restart console-setup.service

which fixes the console problem for me until the next boot.
That's why those files are from today.

> Can you check if the times of these three files change each time the 
> system boots?

See above.

>  And what about the files 
> /etc/default/{keyboard,console-setup} -- do their times change too?

Likely because of the above, too.

> > (the line starting with ">" strikes me as odd - should it not
> >  be on the "mkdir -p" line ?)
> 
> This line creates an empty file /run/console-setup/font-loaded which is 

I eventually figured as much...

> used by /lib/udev/rules.d/90-console-setup.rules to make sure the script 
> /etc/console-setup/cached_setup_terminal.sh is not run before 
> /etc/console-setup/cached_setup_font.sh.

OK, got it.

> These look ok as well...

Feel free to ask for more information you may need.

Thanks,
Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Bug#857132: console-setup: additional info needed ?

[Anton Zinoviev]

On Wed, Mar 22, 2017 at 01:00:17PM +0100, Karsten Hilbert wrote:
> 
> > ls -l /etc/console-setup/
> 
>   -rwxr-xr-x   1 root root   465 Mar 22 11:20 cached_setup_font.sh
>   -rwxr-xr-x   1 root root   358 Mar 22 11:20 cached_setup_keyboard.sh
>   -rwxr-xr-x   1 root root73 Mar 22 11:20 cached_setup_terminal.sh

Hm, the times of these three are too recent. I can see two possibilities:

  1. either the bug no longer exists in this system, in which case we 
have to find out what caused these files to be created, or

  2. the bug still exists and each time the system boots, it recreates 
these three files.  In this case we have to find out the cause of this.

Can you check if the times of these three files change each time the 
system boots?  And what about the files 
/etc/default/{keyboard,console-setup} -- do their times change too?

> > cat /etc/console-setup/cached_setup_font.sh
> > cat /etc/console-setup/cached_setup_terminal.sh

These look ok to me.  I was kind of hoping to find something wrong here...

>   > /run/console-setup/font-loaded
> 
> (the line starting with ">" strikes me as odd - should it not
>  be on the "mkdir -p" line ?)

This line creates an empty file /run/console-setup/font-loaded which is 
used by /lib/udev/rules.d/90-console-setup.rules to make sure the script 
/etc/console-setup/cached_setup_terminal.sh is not run before 
/etc/console-setup/cached_setup_font.sh.

> > cat /etc/default/console-setup
> > cat /etc/default/keyboard

These look ok as well...

Anton Zinoviev

Bug#857132: console-setup: additional info needed ?

[Karsten Hilbert]

On Wed, Mar 22, 2017 at 02:18:51PM +0300, Anton Zinoviev wrote:

> > is there anything I can do/provide to help get this resolved ?
> 
> Yes, thanks!  The output of the following commands:

Here you go:

> ls -l /etc/console-setup/

total 164
drwxr-xr-x   2 root root  4096 Mar  7 09:26 .
drwxr-xr-x 194 root root 12288 Mar 22 11:16 ..
-rw-r--r--   1 root root  2417 Mar  2  2011 Lat15-Fixed16.psf.gz
-rw-r--r--   1 root root  2328 Mar 11  2011 Lat15-Terminus16.psf.gz
-rw-r--r--   1 root root  2351 Nov 12  2010 Lat15-TerminusBold16.psf.gz
-rw-r--r--   1 root root  4086 Mar 11  2011 cached.kmap.gz
-rw-r--r--   1 root root  4377 Mar  7 09:26 cached_UTF-8_del.kmap.gz
-rwxr-xr-x   1 root root   465 Mar 22 11:20 cached_setup_font.sh
-rwxr-xr-x   1 root root   358 Mar 22 11:20 cached_setup_keyboard.sh
-rwxr-xr-x   1 root root73 Mar 22 11:20 cached_setup_terminal.sh
-rw-r--r--   1 root root34 Jan 11  2011 compose.ARMSCII-8.inc
-rw-r--r--   1 root root31 Jan 11  2011 compose.CP1251.inc
-rw-r--r--   1 root root31 Jan 11  2011 compose.CP1255.inc
-rw-r--r--   1 root root31 Jan 11  2011 compose.CP1256.inc
-rw-r--r--   1 root root41 Jan 11  2011 compose.GEORGIAN-ACADEMY.inc
-rw-r--r--   1 root root36 Jan 11  2011 compose.GEORGIAN-PS.inc
-rw-r--r--   1 root root32 Jan 11  2011 compose.IBM1133.inc
-rw-r--r--   1 root root35 Jan 11  2011 compose.ISIRI-3342.inc
-rw-r--r--   1 root root  3596 May 22  2016 compose.ISO-8859-1.inc
-rw-r--r--   1 root root36 Jan 11  2011 compose.ISO-8859-10.inc
-rw-r--r--   1 root root36 Jan 11  2011 compose.ISO-8859-11.inc
-rw-r--r--   1 root root  3737 May 22  2016 compose.ISO-8859-13.inc
-rw-r--r--   1 root root  3020 Mar  2  2016 compose.ISO-8859-14.inc
-rw-r--r--   1 root root  3552 May 22  2016 compose.ISO-8859-15.inc
-rw-r--r--   1 root root36 Jan 11  2011 compose.ISO-8859-16.inc
-rw-r--r--   1 root root  2893 May 22  2016 compose.ISO-8859-2.inc
-rw-r--r--   1 root root  3387 May 22  2016 compose.ISO-8859-3.inc
-rw-r--r--   1 root root  2805 May 22  2016 compose.ISO-8859-4.inc
-rw-r--r--   1 root root35 Jan 11  2011 compose.ISO-8859-5.inc
-rw-r--r--   1 root root35 Jan 11  2011 compose.ISO-8859-6.inc
-rw-r--r--   1 root root  1217 May 22  2016 compose.ISO-8859-7.inc
-rw-r--r--   1 root root35 Jan 11  2011 compose.ISO-8859-8.inc
-rw-r--r--   1 root root  3617 May 22  2016 compose.ISO-8859-9.inc
-rw-r--r--   1 root root31 Jan 11  2011 compose.KOI8-R.inc
-rw-r--r--   1 root root31 Jan 11  2011 compose.KOI8-U.inc
-rw-r--r--   1 root root32 Jan 11  2011 compose.TIS-620.inc
-rw-r--r--   1 root root31 Dec  5  2011 compose.VISCII.inc
-rw-r--r--   1 root root  1359 Dec  5  2011 remap.inc

> cat /etc/console-setup/cached_setup_font.sh

#!/bin/sh

setfont '/etc/console-setup/Lat15-Terminus16.psf.gz' 

if ls /dev/fb* >/dev/null 2>/dev/null; then
for i in /dev/vcs[0-9]*; do
{ :
setfont '/etc/console-setup/Lat15-Terminus16.psf.gz' 
} < /dev/tty${i#/dev/vcs} > /dev/tty${i#/dev/vcs}
done
fi

mkdir -p /run/console-setup
> /run/console-setup/font-loaded
for i in /dev/vcs[0-9]*; do
{ :
printf '\033%%G' 
} < /dev/tty${i#/dev/vcs} > /dev/tty${i#/dev/vcs}
done


(the line starting with ">" strikes me as odd - should it not
 be on the "mkdir -p" line ?)

> cat /etc/console-setup/cached_setup_terminal.sh

#!/bin/sh

{ :
printf '\033%%G' 
} < /dev/tty${1#vcs} > /dev/tty${1#vcs}

> cat /etc/default/console-setup

# Change to "yes" and setupcon will explain what is being doing
VERBOSE_OUTPUT="no"

# Setup these consoles.  Most people do not need to change this.
ACTIVE_CONSOLES="/dev/tty[1-6]"

# Put here your encoding.  Valid charmaps are: UTF-8 ARMSCII-8 CP1251
# CP1255 CP1256 GEORGIAN-ACADEMY GEORGIAN-PS IBM1133 ISIRI-3342
# ISO-8859-1 ISO-8859-2 ISO-8859-3 ISO-8859-4 ISO-8859-5 ISO-8859-6
# ISO-8859-7 ISO-8859-8 ISO-8859-9 ISO-8859-10 ISO-8859-11 ISO-8859-13
# ISO-8859-14 ISO-8859-15 ISO-8859-16 KOI8-R KOI8-U TIS-620 VISCII
CHARMAP="UTF-8"

# The codeset determines which symbols are supported by the font.
# Valid codesets are: Arabic Armenian CyrAsia CyrKoi CyrSlav Ethiopian
# Georgian Greek Hebrew Lao Lat15 Lat2 Lat38 Lat7 Thai Uni1 Uni2 Uni3
# Vietnamese.  Read README.fonts for explanation.
CODESET="Lat15"

# Valid font faces are: VGA (sizes 8, 14 and 16), Terminus (sizes
# 12x6, 14, 16, 20x10, 

libdebian-installer_0.110_i386.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Mar 2017 11:59:18 +0100
Source: libdebian-installer
Binary: libdebian-installer4 libdebian-installer4-dev libdebian-installer4-udeb 
libdebian-installer-extra4 libdebian-installer-extra4-udeb
Architecture: source i386
Version: 0.110
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 libdebian-installer-extra4 - Library of some extra debian-installer functions
 libdebian-installer-extra4-udeb - Library of some extra debian-installer 
functions (udeb)
 libdebian-installer4 - Library of common debian-installer functions
 libdebian-installer4-dev - Library of common debian-installer functions
 libdebian-installer4-udeb - Library of common debian-installer functions (udeb)
Closes: 855965
Changes:
 libdebian-installer (0.110) unstable; urgency=medium
 .
   [ Martin Michlmayr ]
   * subarch-arm-linux.c: Add NETGEAR ReadyNAS Duo v2.  Closes: #855965
Checksums-Sha1:
 8a89f54a5da068bd9bee296344cc392934354557 2211 libdebian-installer_0.110.dsc
 f0f0382def7bede55468743c8ed2dd59699b38f3 271496 
libdebian-installer_0.110.tar.xz
 7f1a85a5d089e88403c0aded03d5d079a0a86c32 7076 
libdebian-installer-extra4-dbgsym_0.110_i386.deb
 64b743e65811cd3e354395e30dc92864cbcbd14b 3830 
libdebian-installer-extra4-udeb_0.110_i386.udeb
 a2d583e211fc99152515ac364b66291cfeb864e4 16218 
libdebian-installer-extra4_0.110_i386.deb
 bc76850f4d44cf1e60d096f06f791821c980d9be 50026 
libdebian-installer4-dbgsym_0.110_i386.deb
 6ab2c2bad275e9430a421f993b4a7eb4bc2727f4 182440 
libdebian-installer4-dev_0.110_i386.deb
 6778fc19952da400a76e3fd5de5c2137d92fab1b 19790 
libdebian-installer4-udeb_0.110_i386.udeb
 bbbcf546c7f6dfe602e41f17339a531071531eaa 32310 
libdebian-installer4_0.110_i386.deb
 db283f48a0355a48185df73cfa18bbdf35d1fb45 6816 
libdebian-installer_0.110_i386.buildinfo
Checksums-Sha256:
 5a84dcc35e32a3528160c43d56d150ad5288ce407d408ba6eb8e7971135db657 2211 
libdebian-installer_0.110.dsc
 848c1468c27ccd26f0df9b2c2f3e4e5bfaea6273a9d716c0ce1f14dbdabb6b77 271496 
libdebian-installer_0.110.tar.xz
 b28d64046257ff4f68a14355afa378abdd4c12f0db34484b9f9ff2c9811d16c7 7076 
libdebian-installer-extra4-dbgsym_0.110_i386.deb
 e3f836b19977406e30e763cb8d93d254efeca9cfcf207288bc79482885f6d1c4 3830 
libdebian-installer-extra4-udeb_0.110_i386.udeb
 246a32e548b6b037595442fc3b68991dd8d537d274ee58866fac866ee0feca61 16218 
libdebian-installer-extra4_0.110_i386.deb
 dc55723c4af8b590001238c3bbe1c587fde57008c2118bbcf4a98380edecc5d5 50026 
libdebian-installer4-dbgsym_0.110_i386.deb
 6e8ba507e257b7c2852439ad6e308e423a674a51826b775909260ca1c84d0bd3 182440 
libdebian-installer4-dev_0.110_i386.deb
 4733c47a61a77616d41b9d8768567617841c1617ae69cf825b7794fd47dd476f 19790 
libdebian-installer4-udeb_0.110_i386.udeb
 4d016b5db8479899e7041241cd5973ebcb2393cfcdde53a6e7a3fd233271bd37 32310 
libdebian-installer4_0.110_i386.deb
 d6b067bbdd630805d85537379387074471a026588facbb271342f658a5ab57bb 6816 
libdebian-installer_0.110_i386.buildinfo
Files:
 2d10b373b83b2e08f412f0b36ad99f98 2211 libs optional 
libdebian-installer_0.110.dsc
 d6223eb6e8344c5fbcad9c07d35ed803 271496 libs optional 
libdebian-installer_0.110.tar.xz
 e1e678158e8f79688b25a87d14e7b7ea 7076 debug extra 
libdebian-installer-extra4-dbgsym_0.110_i386.deb
 2c767e32fcf7341bd891f55f6dc598db 3830 debian-installer optional 
libdebian-installer-extra4-udeb_0.110_i386.udeb
 6ab8f6189a618cc36265b87cb4065afe 16218 libs optional 
libdebian-installer-extra4_0.110_i386.deb
 c6aa31b298c3d280f8016f9a5815264f 50026 debug extra 
libdebian-installer4-dbgsym_0.110_i386.deb
 23454e3ad499ed3d4ccd07c79c9b7045 182440 libdevel optional 
libdebian-installer4-dev_0.110_i386.deb
 6e35e7d0e2aa01bedb859c716687b47d 19790 debian-installer optional 
libdebian-installer4-udeb_0.110_i386.udeb
 6397169d6d132155c54b948dc30d8979 32310 libs optional 
libdebian-installer4_0.110_i386.deb
 61487bf94cf1774e4c7671a3159629cb 6816 libs optional 
libdebian-installer_0.110_i386.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJY0l+eAAoJEIcvcCxNbiWoGJ4QALLgedVSx6oNDBbmCoDOo++E
2HV0KbYnmm8ss1l/FxgdmiLoAJZSApPyzjqpGV4wDzGRcUaERvNWWCbgROse6/lC
XKNDY95m6tnyE6fHXJwRE/tKlCnvI4qVzL0WGjddARsvkHfn3QJCx++wDSORjHJU
kHHSfyl4osRuEAZX9sjkpO4ChtzVcYN9x4jhpLgjcxnh22G/CwsVoqYXL2E9RWFu
j8ssDmfkhsbOH1wDjn0CApQ72Xoo3g7a2k9A5pbGgR4krLkt2KFomlXbOgPHY+uK
CUFHaXxWnDFCV1GHLxAhh5zRObuExkThNCXTKMDXEisfVcKZor6uJzZ7BybzhALs
DLxkiiqSZJ/UB+jcrYZOhjn8jLXqwcE4k28bpjo/ZYaL5w2l5Ut4z9O9fzLduQX0
oYrusZOzUjH7IOi8J9F80oXNyjsELo7BA6XoYuzioKOWuESuTUkL6ZQ8ppmLmRMo
6w9sSyb2CT36KkoZcyqJmlsgvrVMZzzCGpGmi7i4qAEwm4Eu+BePBeDmRbqO03Nk
yVgDBLSTyhVifw288Yr2mnYMQoVZ/iB/AGV93IO6M1tSm5XN1BTxKkt58q3JMlY3
Zn9qN4b4cYIZqfTsYQ9tZeLqregyxDqZLnGp+a8RqTSzIGr/zq+diqitUeUKyf25
iI0Jt8PkmUh6Bc1irhvW
=2BJh
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of libdebian-installer_0.110_i386.changes

[Debian FTP Masters]

libdebian-installer_0.110_i386.changes uploaded successfully to localhost
along with the files:
  libdebian-installer_0.110.dsc
  libdebian-installer_0.110.tar.xz
  libdebian-installer-extra4-dbgsym_0.110_i386.deb
  libdebian-installer-extra4-udeb_0.110_i386.udeb
  libdebian-installer-extra4_0.110_i386.deb
  libdebian-installer4-dbgsym_0.110_i386.deb
  libdebian-installer4-dev_0.110_i386.deb
  libdebian-installer4-udeb_0.110_i386.udeb
  libdebian-installer4_0.110_i386.deb
  libdebian-installer_0.110_i386.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#855965: marked as done (libdebian-installer: Please add support for NETGEAR ReadyNAS Duo v2)

[Debian Bug Tracking System]

Your message dated Wed, 22 Mar 2017 11:33:50 +
with message-id 
and subject line Bug#855965: fixed in libdebian-installer 0.110
has caused the Debian Bug report #855965,
regarding libdebian-installer: Please add support for NETGEAR ReadyNAS Duo v2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdebian-installer
Version: 0.108
Severity: wishlist

Dear Maintainer,

Please add support for NETGEAR ReadyNAS Duo v2, which uses a "kirkwood" 
processor:

# cat /proc/device-tree/model
NETGEAR ReadyNAS Duo v2

# cat /proc/cpuinfo
processor   : 0
model name  : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS: 1594.36
Features: swp half thumb fastmult edsp 
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part: 0x131
CPU revision: 1

Hardware: Marvell Kirkwood (Flattened Device Tree)
Revision: 
Serial  : 

I believe you can add this to map_hardware[] :

  { "NETGEAR ReadyNAS Duo v2" , "kirkwood" },

Thank you.


-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: libdebian-installer
Source-Version: 0.110

We believe that the bug you reported is fixed in the latest version of
libdebian-installer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated libdebian-installer 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Mar 2017 11:59:18 +0100
Source: libdebian-installer
Binary: libdebian-installer4 libdebian-installer4-dev libdebian-installer4-udeb 
libdebian-installer-extra4 libdebian-installer-extra4-udeb
Architecture: source i386
Version: 0.110
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 libdebian-installer-extra4 - Library of some extra debian-installer functions
 libdebian-installer-extra4-udeb - Library of some extra debian-installer 
functions (udeb)
 libdebian-installer4 - Library of common debian-installer functions
 libdebian-installer4-dev - Library of common debian-installer functions
 libdebian-installer4-udeb - Library of common debian-installer functions (udeb)
Closes: 855965
Changes:
 libdebian-installer (0.110) unstable; urgency=medium
 .
   [ Martin Michlmayr ]
   * subarch-arm-linux.c: Add NETGEAR ReadyNAS Duo v2.  Closes: #855965
Checksums-Sha1:
 8a89f54a5da068bd9bee296344cc392934354557 2211 libdebian-installer_0.110.dsc
 f0f0382def7bede55468743c8ed2dd59699b38f3 271496 
libdebian-installer_0.110.tar.xz
 7f1a85a5d089e88403c0aded03d5d079a0a86c32 7076 
libdebian-installer-extra4-dbgsym_0.110_i386.deb
 64b743e65811cd3e354395e30dc92864cbcbd14b 3830 
libdebian-installer-extra4-udeb_0.110_i386.udeb
 a2d583e211fc99152515ac364b66291cfeb864e4 16218 
libdebian-installer-extra4_0.110_i386.deb
 bc76850f4d44cf1e60d096f06f791821c980d9be 50026 
libdebian-installer4-dbgsym_0.110_i386.deb
 6ab2c2bad275e9430a421f993b4a7eb4bc2727f4 182440 
libdebian-installer4-dev_0.110_i386.deb
 6778fc19952da400a76e3fd5de5c2137d92fab1b 19790 
libdebian-installer4-udeb_0.110_i386.udeb
 bbbcf546c7f6dfe602e41f17339a531071531eaa 32310 
libdebian-installer4_0.110_i386.deb
 db283f48a0355a48185df73cfa18bbdf35d1fb45 6816 
libdebian-installer_0.110_i386.buildinfo
Checksums-Sha256:
 5a84dcc35e32a3528160c43d56d150ad5288ce407d408ba6eb8e7971135db657 2211 
libdebian-installer_0.110.dsc
 848c1468c27ccd26f0df9b2c2f3e4e5bfaea6273a9d716c0ce1f14dbdabb6b77 271496 
libdebian-installer_0.110.tar.xz
 

flash-kernel_3.77_armel.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Mar 2017 06:52:54 +0100
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source armel
Version: 3.77
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 flash-kernel - utility to make certain embedded devices bootable
 flash-kernel-installer - Make the system bootable (udeb)
Closes: 845818 855960
Changes:
 flash-kernel (3.77) unstable; urgency=medium
 .
   [ Martin Michlmayr ]
   * Add machine db entry for NETGEAR ReadyNAS Duo v2.  Thanks to Scott
 Barker (Closes: #855960)
   * Add machine db entry for Hardkernel ODROID-C2.  Thanks Heinrich
 Schuchardt (Closes: #845818).
Checksums-Sha1:
 4645dbbdc43a34c2b367fa2ec1764cde4e959d29 1859 flash-kernel_3.77.dsc
 fab667750546d5fd3728f42f811844fa8ee57591 68816 flash-kernel_3.77.tar.xz
 0973d07083ba706ad92ecabb70e6facb64702e0b 25776 
flash-kernel-installer_3.77_armel.udeb
 30fabaa9dedef7004f7a4ed368413c851f74ddc6 5003 flash-kernel_3.77_armel.buildinfo
 a3ae7de29aac8baf45f2ca63fe83cb9750b9dd23 45500 flash-kernel_3.77_armel.deb
Checksums-Sha256:
 fc04c9a8b9d627ce61faa3cfd69eae66321e32c8de6caea9677e54910d4ab6ff 1859 
flash-kernel_3.77.dsc
 8b4c109c0a57736fc212f442c017926d3a3ccac2ce11318d72310e06b2e5a6da 68816 
flash-kernel_3.77.tar.xz
 1718584ac34e0dd10714904d1378ba614bf719f1baa6c03df089ca227ddd80cb 25776 
flash-kernel-installer_3.77_armel.udeb
 74bb182a2b265bbb13e6887fb397de5b747b78210b002a86ff80488ddaf13f4d 5003 
flash-kernel_3.77_armel.buildinfo
 a5d2165cf2129de71c474bcb4d9bc08bd64e7a25f43e5b789f5240327b5de443 45500 
flash-kernel_3.77_armel.deb
Files:
 fa2f14a7781de1d06afc3683f50e3e9b 1859 utils optional flash-kernel_3.77.dsc
 175f90a6d1fe02d500c59347c3979ef2 68816 utils optional flash-kernel_3.77.tar.xz
 c3af12058431576131da556872b8b302 25776 debian-installer standard 
flash-kernel-installer_3.77_armel.udeb
 3b793bb248b38e7ba5d301f358906c29 5003 utils optional 
flash-kernel_3.77_armel.buildinfo
 840f880d872ab9fc435e7e0b76a842e0 45500 utils optional 
flash-kernel_3.77_armel.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJY0lfXAAoJEIcvcCxNbiWo6lIQALnRnserJLgTtwkQha95pxtw
LfRocgOBs3dGd5SwryauRCq9iIVSs59taY5NNHuYayPKE4TRxCxuOSRvIeoUDK39
ttavaOJp6d4h699tRPkq0SshiMnxUhqvQ4cghj1vVF8v3c6Oskh0zChHC2cWVwbs
Ggw2Y1KpSFcY33XxjMc2BasJfqLt3fTezX3xRp2qflYd8gMPJQRm1yi7qvtm0h7F
ESRE6orZN2i6OQzvsm+powtKKDf2ovBID+G4ih0d5X4zZBsRUuzQYD9N8wCLoq9i
inNxZFYsDt/6TmjdtVsH7ztH21Thqi+66LSyWkD3VsqdEAWC8wx9gag8o2Zh1PBt
VtciujPoMABxMJBLRvU4wmYHWjvbpsPO0YOXXAZ1f5WYn3MxI2tgsCgNGi/uH8Gk
GA1k7ZwoScd6XdrWYUR00L4fPRjlqeC0FW00Ecvw2BJngfb4N2H8xNo10wZ7Ixjp
1hY7yyKmQa/xeD15a8e1kv5bR8TOcVo+CVlrDPb6ffVZVy3GaXXH4USyQCz+2Lrr
jUEmX1DbW7+WTIrMMVZYUXDprm8MTmKMeoWeCbBFebSFQJ3yYB9sLhQqssmFqLKt
jPkvBb5p03U8/SeOy+YhaVfmf/pLURS48zm5t5rkKG//VLD3t+GRQ+uiT6qH1uS2
E1Dgi9TIRLvWT7pMO0Tp
=FJRF
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#857132: console-setup: additional info needed ?

[Anton Zinoviev]

On Wed, Mar 22, 2017 at 11:29:48AM +0100, Karsten Hilbert wrote:
> 
> is there anything I can do/provide to help get this resolved ?

Yes, thanks!  The output of the following commands:

ls -l /etc/console-setup/
cat /etc/console-setup/cached_setup_font.sh
cat /etc/console-setup/cached_setup_terminal.sh
cat /etc/default/console-setup
cat /etc/default/keyboard

Anton Zinoviev

Processing of flash-kernel_3.77_armel.changes

[Debian FTP Masters]

flash-kernel_3.77_armel.changes uploaded successfully to localhost
along with the files:
  flash-kernel_3.77.dsc
  flash-kernel_3.77.tar.xz
  flash-kernel-installer_3.77_armel.udeb
  flash-kernel_3.77_armel.buildinfo
  flash-kernel_3.77_armel.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#855960: marked as done (flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2)

[Debian Bug Tracking System]

Your message dated Wed, 22 Mar 2017 11:03:47 +
with message-id 
and subject line Bug#855960: fixed in flash-kernel 3.77
has caused the Debian Bug report #855960,
regarding flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flash-kernel
Version: 3.70~bpo8+1
Severity: wishlist

Dear Maintainer,

Please add suuport for NETGEAR ReadyNAS Duo v2. The db entry that works for me 
is:

Machine: NETGEAR ReadyNAS Duo v2
DTB-Id: kirkwood-netgear_readynas_duo_v2.dtb
DTB-Append: yes
Mtd-Kernel: uImage
Mtd-Initrd: minirootfs
U-Boot-Kernel-Address: 0x8000
U-Boot-Initrd-Address: 0x
Required-Packages: u-boot-tools
Bootloader-Sets-Incorrect-Root: yes

Thank you.

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  devio  1.2-1+b1
ii  initramfs-tools0.120+deb8u2
ii  linux-base 3.5
ii  mtd-utils  1:1.5.1-1
ii  ucf3.0030

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2014.10+dfsg1-5

flash-kernel suggests no packages.

-- debconf information:
  flash-kernel/linux_cmdline: quiet
--- End Message ---
--- Begin Message ---
Source: flash-kernel
Source-Version: 3.77

We believe that the bug you reported is fixed in the latest version of
flash-kernel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated flash-kernel 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Mar 2017 06:52:54 +0100
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source armel
Version: 3.77
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 flash-kernel - utility to make certain embedded devices bootable
 flash-kernel-installer - Make the system bootable (udeb)
Closes: 845818 855960
Changes:
 flash-kernel (3.77) unstable; urgency=medium
 .
   [ Martin Michlmayr ]
   * Add machine db entry for NETGEAR ReadyNAS Duo v2.  Thanks to Scott
 Barker (Closes: #855960)
   * Add machine db entry for Hardkernel ODROID-C2.  Thanks Heinrich
 Schuchardt (Closes: #845818).
Checksums-Sha1:
 4645dbbdc43a34c2b367fa2ec1764cde4e959d29 1859 flash-kernel_3.77.dsc
 fab667750546d5fd3728f42f811844fa8ee57591 68816 flash-kernel_3.77.tar.xz
 0973d07083ba706ad92ecabb70e6facb64702e0b 25776 
flash-kernel-installer_3.77_armel.udeb
 30fabaa9dedef7004f7a4ed368413c851f74ddc6 5003 flash-kernel_3.77_armel.buildinfo
 a3ae7de29aac8baf45f2ca63fe83cb9750b9dd23 45500 flash-kernel_3.77_armel.deb
Checksums-Sha256:
 fc04c9a8b9d627ce61faa3cfd69eae66321e32c8de6caea9677e54910d4ab6ff 1859 
flash-kernel_3.77.dsc
 8b4c109c0a57736fc212f442c017926d3a3ccac2ce11318d72310e06b2e5a6da 68816 
flash-kernel_3.77.tar.xz
 1718584ac34e0dd10714904d1378ba614bf719f1baa6c03df089ca227ddd80cb 25776 
flash-kernel-installer_3.77_armel.udeb
 74bb182a2b265bbb13e6887fb397de5b747b78210b002a86ff80488ddaf13f4d 5003 
flash-kernel_3.77_armel.buildinfo
 a5d2165cf2129de71c474bcb4d9bc08bd64e7a25f43e5b789f5240327b5de443 45500 
flash-kernel_3.77_armel.deb
Files:
 fa2f14a7781de1d06afc3683f50e3e9b 1859 utils optional flash-kernel_3.77.dsc
 175f90a6d1fe02d500c59347c3979ef2 68816 utils optional flash-kernel_3.77.tar.xz
 c3af12058431576131da556872b8b302 25776 debian-installer standard 
flash-kernel-installer_3.77_armel.udeb
 3b793bb248b38e7ba5d301f358906c29 5003 utils optional 

Bug#845818: marked as done (flash-kernel: Add support for Hardkernel Odroid-C2)

[Debian Bug Tracking System]

Your message dated Wed, 22 Mar 2017 11:03:47 +
with message-id 
and subject line Bug#845818: fixed in flash-kernel 3.77
has caused the Debian Bug report #845818,
regarding flash-kernel: Add support for Hardkernel Odroid-C2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flash-kernel
Version: 3.71
Severity: wishlist

The appended patch provides support for the Hardkernel Odroid-C2.
It depends on a solution to
Bug #845779 flash-kernel: flashkernel uses mkimage -A arm on arm64

The Hardkernel Odroid C2 is a 64bit development board based on the
Amlogic S905 processor.

As mainline u-boot support is still under construction boot.scr
is build such that the stock u-boot can execute it.

Update the u-boot environment with
setenv bootcmd "ext4load mmc 0:1 0x107 boot.scr; autoscr 0x107"
saveenv

Separate ext4 partitions for '/boot' and '/' are assumed.
From 8483746841c140dc38784866c94a802f293cdb5b Mon Sep 17 00:00:00 2001
From: Heinrich Schuchardt 
Date: Sat, 26 Nov 2016 21:34:43 +
Subject: [PATCH 1/1] Add support for Hardkernel Odroid C2

The Hardkernel Odroid C2 is a 64bit development board based on the
Amlogic S905 processor.

As mainline u-boot support is still under construction boot.scr
is build such that the stock u-boot can execute it.

Update the u-boot environment with
setenv bootcmd "ext4load mmc 0:1 0x107 boot.scr; autoscr 0x107"
saveenv

Separate ext4 partitions for '/boot' and '/' are assumed.

Signed-off-by: Heinrich Schuchardt 
---
 bootscript/arm64/bootscr.hardkernel-odroid-c2 | 17 +
 db/all.db | 11 +++
 2 files changed, 28 insertions(+)
 create mode 100644 bootscript/arm64/bootscr.hardkernel-odroid-c2

diff --git a/bootscript/arm64/bootscr.hardkernel-odroid-c2 b/bootscript/arm64/bootscr.hardkernel-odroid-c2
new file mode 100644
index 000..5cce3de
--- /dev/null
+++ b/bootscript/arm64/bootscr.hardkernel-odroid-c2
@@ -0,0 +1,17 @@
+setenv fdtfile meson-gxbb-odroidc2.dtb
+setenv fk_kvers '@@KERNEL_VERSION@@'
+setenv fdtpath dtbs/${fk_kvers}/${fdtfile}
+
+setenv condev "console=ttyAML0,115200n8 console=tty0"
+setenv bootargs "root=/dev/mmcblk1p2 rootwait ro ${condev}"
+
+setenv loadaddr "0x108"
+setenv dtb_loadaddr "0x100"
+setenv initrd_loadaddr "0x1300"
+
+ext4load mmc 0:1 ${initrd_loadaddr} uInitrd
+ext4load mmc 0:1 ${loadaddr} uImage
+ext4load mmc 0:1 ${dtb_loadaddr} ${fdtpath}
+fdt addr ${dtb_loadaddr}
+
+bootm ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}
diff --git a/db/all.db b/db/all.db
index a9567a9..e81cf18 100644
--- a/db/all.db
+++ b/db/all.db
@@ -427,6 +427,17 @@ DTB-Id: sun4i-a10-marsboard.dtb
 U-Boot-Script-Name: bootscr.sunxi
 Required-Packages: u-boot-tools
 
+Machine: Hardkernel ODROID-C2
+U-Boot-Kernel-Address: 0x108
+U-Boot-Initrd-Address: 0x1300
+U-Boot-Script-Address: 0x100
+U-Boot-Script-Name: bootscr.hardkernel-odroid-c2
+Boot-Kernel-Path: /boot/uImage
+Boot-Initrd-Path: /boot/uInitrd
+Boot-Script-Path: /boot/boot.scr
+Required-Packages: u-boot-tools
+DTB-Id: meson-gxbb-odroidc2.dtb
+
 Machine: Hardkernel ODROID-U3 board based on Exynos4412
 Kernel-Flavors: armmp armmp-lpae
 DTB-Id: exynos4412-odroidu3.dtb
-- 
2.10.2

--- End Message ---
--- Begin Message ---
Source: flash-kernel
Source-Version: 3.77

We believe that the bug you reported is fixed in the latest version of
flash-kernel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated flash-kernel 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Mar 2017 06:52:54 +0100
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source armel
Version: 3.77
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: 

Re: can't get the debian-installer code by svn

[Roger Shimizu]

On Wed, 22 Mar 2017 16:17:08 +0800 (CST)
harryyue123  wrote:

>  I want get a source code of debian-installer,but failed.the error 
> message is :
>   
> harry@BJ-LD-1229:~/Project/000debian8.7$ svn co 
> svn://anonscm.debian.org/svn/d-i/trunk d-i

Where did you get the URL of SVN repo?

Now the repo has been moved to git:
 https://anonscm.debian.org/git/d-i/debian-installer.git

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


pgp0VucZ7gtZ4.pgp
Description: PGP signature

Bug#857132: console-setup: additional info needed ?

[Karsten Hilbert]

Package: console-setup
Version: 1.163
Followup-For: Bug #857132

Hi,

is there anything I can do/provide to help get this resolved ?

Thanks,
Karsten

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.10.0-trunk-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages console-setup depends on:
ii  console-setup-linux 1.163
ii  debconf 1.5.60
ii  keyboard-configuration  1.163
ii  xkb-data2.19-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.24-9
ii  lsb-base  9.20161125

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.60
ii  liblocale-gettext-perl  1.07-3+b1

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.47
ii  initscripts 2.88dsf-59.9
ii  kbd 2.0.3-2+b1
ii  keyboard-configuration  1.163

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2+b1
ii  systemd   232-19

-- debconf information excluded

can't get the debian-installer code by svn

[harryyue123]

hi all,

 I want get a source code of debian-installer,but failed.the error message 
is :
  
harry@BJ-LD-1229:~/Project/000debian8.7$ svn co 
svn://anonscm.debian.org/svn/d-i/trunk d-i
Ad-i/packages
Ad-i/packages/po
Ad-i/packages/po/header.pot
Ad-i/packages/po/packages_list
Ad-i/packages/po/README
Ad-i/packages/po/sublevel1
Ad-i/packages/po/sublevel1/pa.po
Ad-i/packages/po/sublevel1/hi.po
Ad-i/packages/po/sublevel1/ne.po
Ad-i/packages/po/sublevel1/ta.po
svn: E140001: zlib (uncompress): corrupt data: Decompression of svndiff data 
failed

please help us ! Thanks!






--

Best Regards

harry

Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts

[Philip Hands]

Steve McIntyre  writes:

> On Wed, Mar 22, 2017 at 01:40:11AM +0100, Samuel Thibault wrote:
>>Hello,
>>
>>Somehow somebody managed to raise that there is no menu entry for
>>starting the rescue mode with speech synthesis enabled.  That actually
>>also raises the question of doing the same for expert install and
>>automated install.
>>
>>It's really a matter of adding the menu entry: just copy/paste the
>>existing expert/rescue/automated entries, and append speakup.synth=soft
>>to it.
>>
>>Now the question is: which keyboard shortcut to use?
>>
>>For now, the only documented accessible keyboard shortcut is "s" to
>>start a speech-enabled installation.  I guess we don't want to add yet
>>other entries to the main menu, so we'd put these additional entries
>>under the "advanced options" submenu, which already has shortcut "a".
>>However, the natural "e", "r" and "a" shortcuts are already taken for
>>the non-speech versions.
>>
>>Would it really be a problem to change the meaning of those shortcuts,
>>to make them start the speech versions instead of the non-speech
>>version?  I have to say I myself never used those shortcuts, since it's
>>so fast to just move down a few times when one is sighted :)
>
> I've personally never used the shortcuts, but I'd be curious if
> anybody might be for automated testing possibly? It'd be easier to do
> that than parse the boot menus...

I'm certainly up for doing automated testing -- to do proper testing
we'd need to work out how to do recognition of the speech sounds made,
and then I'd want to plug that recognition into the back of cucumber, so
that we could add the tests to our jenkins jobs.

If anyone has any pointers for doing any of that, particularly the
recognition bit, that would be most helpful.

FWIW I had not bothered to even notice that the shortcuts exist, let
alone used them, so I fully support reusing the shortcuts for starting
speech-enabled versions.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature