[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#695168: marked as done (Fix preseeding of popcon question for Debian Edu/Wheezy in jenkins.debian.net)



Your message dated Wed, 5 Dec 2012 00:16:25 +0100
with message-id <201212050016.26744.holger@layer-acht.org>
and subject line Re: Bug#695168: Fix preseeding of popcon question for Debian Edu/Wheezy in jenkins.debian.net
has caused the Debian Bug report #695168,
regarding Fix preseeding of popcon question for Debian Edu/Wheezy in jenkins.debian.net
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 owner@bugs.debian.org
immediately.)


-- 
695168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695168
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Tags: patch

I investigated the new installation failure for Debian Edu/Wheezy
reported in
<URL: http://jenkins.debian.net/job/cd-test_debian_edu_wheezy/ >, and
discovered the reason why the popcon question preseeding did not work.

The preseed file is preseeding the wrong debconf template.  The one
being shown is the one in debian-edu-install, which is copied from
popularity-contest to ensure all questions show up before packages are
downloaded.

The following patch can be used to get the installation going.

-- 
Happy hacking
Petter Reinholdtsen
>From f6d686b92e47889c8876b71083e6899bbdcb0dec Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen <pere@hungry.com>
Date: Tue, 4 Dec 2012 22:13:34 +0100
Subject: [PATCH 3/3] Make sure to preseed the correct popcon question template for Debian Edu.

---
 userContent/debian-edu-wheezy-preseed.cfg |    7 +------
 1 files changed, 1 insertions(+), 6 deletions(-)

diff --git a/userContent/debian-edu-wheezy-preseed.cfg b/userContent/debian-edu-wheezy-preseed.cfg
index d856438..31ffb85 100644
--- a/userContent/debian-edu-wheezy-preseed.cfg
+++ b/userContent/debian-edu-wheezy-preseed.cfg
@@ -327,12 +327,7 @@ d-i debian-edu-install/confirm boolean true
 # installed, and what software you use. The default is not to report back,
 # but sending reports helps the project determine what software is most
 # popular and include it on CDs.
-# FIXME: priority-critical is ignored (so we force no to popcon), this seems to be an oddity of debian-edu
-# <h01ger> yet lxde-wheezy doenst hang at that question and priority=critical is used in both cases
-# <h01ger> so it seems that critical prio is ignored by our installer
-# <pere> if I remeber correctly, we change the priority during installation to work around the fact that tasksel wasn't preseedable.
-# <pere> perhaps that changing interfere with the preseeding?  anyway, just preseeding the value should work
-popularity-contest popularity-contest/participate boolean false
+d-i debian-edu-install/participate-popcon boolean false
 
 ### Finishing up the installation
 # During installations from serial console, the regular virtual consoles
-- 
1.7.2.5


--- End Message ---
--- Begin Message ---
Hi Petter,

On Dienstag, 4. Dezember 2012, Petter Reinholdtsen wrote:
> I investigated the new installation failure for Debian Edu/Wheezy
> reported in
> <URL: http://jenkins.debian.net/job/cd-test_debian_edu_wheezy/ >, and
> discovered the reason why the popcon question preseeding did not work.

great, thanks for your patch, applied. Plus then I moved this to the back of 
the preseed file, to the edu specific configurations and added this note:

+# the popcon question needs special preseeding as the template
+# being shown is the one in debian-edu-install, which is copied from
+# popularity-contest to ensure all questions show up before packages are
+# downloaded.

Will schedule a new test shortly.


cheers,
	Holger

--- End Message ---

Reply to: