l10n uploads still OK or should I delay them?

[Christian PERRIER]

Hello,

Some l10n uploads are pending for 3 packages (apt-setup,
base-installer, cdebconf). Nothing urgent, only completion for Czech
language.

Given that a release is somehow planned, should I delay them or is it
still OK for my to build/upload these packages?


-- 





signature.asc
Description: PGP signature

Bug#808464: suddenly being asked for interactive keyboard configuration

[Holger Levsen]

package: debconf,keyboard-configuration
severity: serious
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org

Hi,

first of all: I'm at lost where this really comes from, as this happened the 
first time on December 16th (and since then I saw and aborted it daily) and 
neither debconf nor keyboard-configuration have been uploaded since them. I 
see this in two jenkins jobs which have been unchanged since months:

https://jenkins.debian.net/view/reproducible/job/reproducible_setup_schroot_unstable_diffoscope_amd64_jenkins
https://jenkins.debian.net/view/reproducible/job/reproducible_setup_schroot_unstable_diffoscope_amd64_profitbricks3/

Which do "apt-get install -y --install-recommends diffoscope" in sid, which 
now fails like this: 

...
Setting up keyboard-configuration (1.134) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Configuring keyboard-configuration
--

Please select the layout matching the keyboard for this machine.

  1. English (US)
  2. English (US) - Cherokee
  3. English (US) - English (Colemak)
  4. English (US) - English (Dvorak alternative international no dead keys)
  5. English (US) - English (Dvorak)
  6. English (US) - English (Dvorak, international with dead keys)
  7. English (US) - English (Macintosh)
  8. English (US) - English (US, alternative international)
  9. English (US) - English (US, international with dead keys)
  10. English (US) - English (US, with euro on 5)
  11. English (US) - English (Workman)
  12. English (US) - English (Workman, international with dead keys)
  13. English (US) - English (classic Dvorak)
  14. English (US) - English (international AltGr dead keys)
  15. English (US) - English (left handed Dvorak)
  16. English (US) - English (programmer Dvorak)
  17. English (US) - English (right handed Dvorak)
  18. English (US) - English (the divide/multiply keys toggle the layout)
  19. English (US) - Russian (US, phonetic)
  20. English (US) - Serbo-Croatian (US)
  21. Other


and then it hangs forever. We discussed this on #debian-qa:

 so why do we see this in sid now: 
https://jenkins.debian.net/view/reproducible/job/reproducible_setup_schroot_unstable_diffoscope_amd64_profitbricks3/71/console
 
(scroll down)
 could be something to do with some of the debconf frontends being 
uninstallable but I can't really see why that would make it interactive
 is it using DEBIAN_FRONTEND=noninteractive ?
 ntyni: yes. the jenkins code used here hasnt changed at all. 
 h01ger: I'm guessing DEBIAN_FRONTEND=noninteractive never took effect 
for some reason and the Dialog frontend is now falling back to a different 
frontend (Readline) that tries harder to ask its questions even without a real 
terminal/stdin
 hm
 h01ger: I wouldn't expect those messages about Dialog and Readline 
frontends at all if DEBIAN_FRONTEND=noninteractive was in effect
* h01ger nods
 h01ger: but I'm not 100% positive on that
 
https://jenkins.debian.net/job/reproducible_setup_schroot_unstable_diffoscope_amd64_jenkins/lastBuild/console
 
weirly enough has a different frontend it seems

any ideas anyone?


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#808464: suddenly being asked for interactive keyboard configuration

[gregor herrmann]

On Sun, 20 Dec 2015 12:27:11 +0100, Holger Levsen wrote:

> Which do "apt-get install -y --install-recommends diffoscope" in sid, which 
> now fails like this: 
> 
> ...
> Setting up keyboard-configuration (1.134) ...
> debconf: unable to initialize frontend: Dialog
> debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
> buffer, or without a controlling terminal.)
> debconf: falling back to frontend: Readline
> Configuring keyboard-configuration
> --
[..]
 
>  is it using DEBIAN_FRONTEND=noninteractive ?
>  ntyni: yes. the jenkins code used here hasnt changed at all. 
>  h01ger: I'm guessing DEBIAN_FRONTEND=noninteractive never took effect 
> for some reason and the Dialog frontend is now falling back to a different 
> frontend (Readline) that tries harder to ask its questions even without a 
> real 
> terminal/stdin
>  hm
>  h01ger: I wouldn't expect those messages about Dialog and Readline 
> frontends at all if DEBIAN_FRONTEND=noninteractive was in effect
> * h01ger nods
>  h01ger: but I'm not 100% positive on that
>  
> https://jenkins.debian.net/job/reproducible_setup_schroot_unstable_diffoscope_amd64_jenkins/lastBuild/console
>  
> weirly enough has a different frontend it seems

Quick test:
- cowbuilder sid amd64 chroot
- a) DEBIAN_FRONTEND=noninteractive, b) unset DEBIAN_FRONTEND
- apt-get install -y --install-recommends diffoscope

In case a) I get no questions, as expected; in case b) I also get

Setting up keyboard-configuration (1.134) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Configuring keyboard-configuration
--


This looks like DEBIAN_FRONTEND=noninteractive is working as
expected; which doesn't answer what's happening in your
jenkins/reproduucible job :/

Hm, a tiny difference is "Dialog frontend will not work" vs. "No
usable dialog-like program is installed". But still, the whole
question should be skipped with DEBIAN_FRONTEND=noninteractive.

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Leonard Cohen: Nancy


signature.asc
Description: Digital Signature

Bug#808514: os-prober: Does no longer recognize Windows 7

[Andreas Tscharner]

Package: os-prober
Version: 1.70
Severity: normal

Dear Maintainer,

I updated my system (about two weeks ago, e.g. at the beginnig of
december 2015) and grup was also updated. After that it had no longer
an entry for Windows 7. My Windows partition is /dev/sda2, but
os-prober says:

Dec 20 15:59:03 shannara 20microsoft: debug: /dev/sda2 is a FUSE partition
Dec 20 15:59:03 shannara os-prober: debug: running 
/usr/lib/os-probes/mounted/30utility on mounted /dev/sda2
Dec 20 15:59:03 shannara 30utility: debug: /dev/sda2 is not a FAT partition: 
exiting

As written above: It worked until about two weeks ago.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages os-prober depends on:
ii  libc6  2.21-4

os-prober recommends no packages.

os-prober suggests no packages.

-- no debconf information

Re: Backports installed without prompt if not in base suite: bug or feature ?

[Charles Plessy]

Le Mon, Dec 14, 2015 at 11:16:24PM +0900, Charles Plessy a écrit :
> 
> The current behaviour of the backports suite is deeply rooted in how APT 
> works.
> Following the "install" command for a package, APT will look at the versions
> present in its cache and their priorities ("pin values"), and following the
> rules explained the apt_preferences manpage, will either install one of these
> versions or do nothing.  In that sense, there is actually no difference 
> between
> "installing" a package and "upgrading" a package.  For backport packages
> without a counterpart in the base suite, the backports versions are valid
> candidtes and will be installed without warning.  This is true as well for
> packages in the "experimental" suite.
> 
> David wrote that he would like to implement a pattern system inspired from
> aptitude, and utilise this to configure and display package listings in a way
> that gives a chance to the user to cancel the installation of a backports
> package when this installation happens only because there is no version
> available in the base suite.

Hi David and everybody,

I would like to report the fruit of our discussion to the debian-cloud mailing
list.  Please let me know if you think that the summary above is inaccurate.
You are also welcome to let me know if you thing it is accurate :)

Have a nice Sunday,

-- 
Charles

Processed: cause found…

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 808464 qa.debian.org
Bug #808464 [debconf,keyboard-configuration] suddenly being asked for 
interactive keyboard configuration
Bug reassigned from package 'debconf,keyboard-configuration' to 'qa.debian.org'.
Ignoring request to alter found versions of bug #808464 to the same values 
previously set
Ignoring request to alter fixed versions of bug #808464 to the same values 
previously set
> close 808464
Bug #808464 [qa.debian.org] suddenly being asked for interactive keyboard 
configuration
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
808464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#808464: cause found…

[Holger Levsen]

reassign 808464 qa.debian.org
close 808464
thanks

Hi,

the cause was (is) actually a bug in jenkins.d.n script (the env variable 
DEBCONF_FRONTEND is reset by using sudo) but it only became visible now when 
diffoscope 43 started to pull in python-guestfs, which then lead to keyboard-
configuratin being installed too…

Thanks to Niko Tyni for tracking this down!


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Re: Tentative last d-i release for 2015?

[Cyril Brulebois]

Emilio Pozuelo Monfort  (2015-12-18):
> My apologies. I didn't think this through... I guess we've been
> waiting for this transition for so long that I just was too happy to
> be able to start it. I guess I also thought you were building d-i out
> of testing, and that's why I said we could wait (for the migration) to
> happen until the block was lifted. My bad.

Just as a reminder/clarification for another time:
 - src:debian-installer is special in two ways:
   - it fetches stuff over the network, from testing;
   - it builds a tar archive with installation images, to be included
 along with a tiny .deb (which bundles a few docs).

 - src:debian-installer isn't special in the following ways:
   - it's uploaded to, and built within, unstable;
   - its build-deps are fetched from unstable as well.
   (that's why we had the syslinux thing a few years ago; and the perl
thing right now.)

> Not sure if it helps, but at this rate, we will have rebuilt
> everything on the "fast" architectures (everywhere except mips*) by
> the end of today. Migration to testing will take longer as there are
> issues to sort out, though again I don't know if that is a problem for
> you or if having an installable sid is enough.

That doesn't help: src:debian-installer has to be built everywhere and
dak copy-installer has to happen before we start building “CD” images;
changelog datamining (used to prepare release announces) also relies on
the build having happened on all archs. So the fast vs. slow archs makes
this moot. There's also the part where developers have to be around (and
have access to the right hardware/tools) to actually do the work…

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#794410: debian-installer: Installer hangs during 'select and install software'

[Yevgen Yashchenko]

Just had the same issue on Intel J1900 net-top (Gigabyte BRIX 1900) using
the SteamOS installation.Symptoms are: installer hangs after triggering
libc-bin.
Since BIOS did not provide an option disabling WLAN had to disconnect it
physically. This helped - it was able to finish the installation.