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

Bug#715403: Unreliable wget test



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

Thanks for your quick answer,

Le 08/07/2013 16:52, Petter Reinholdtsen a écrit :

>> In order to add the debian-edu repositories to the APT sources,
>> there is a useless and painful wget test during the
>> debian-edu-profile step.
> 
> I'm not aware of any useless wget test in debian-edu-profile.  Can you
> pinpoint the one you had hin mind?

http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-install/debian-edu-profile?view=markup#l495

>>elif ! log-output wget -U "Wget, Debian Edu d-i $de_suite $archstr" -qO - http://ftp.skolelinux.org/welcome.msg ; then
>     db_settitle debian-edu-install/no-network/title
>     db_input critical "debian-edu-install/no-network" || true
>     db_go || true
>     exit 1
> else
>     #Enable mirrors for the rest

> When booting from CD (or USB stick, for that matter), I believe you
> can specify the proxy to use by adding
> mirror/http/proxy=http://my.proxy.edu:3128 as a boot parameter to the
> kernel.

As stated previously, that one is only supposed to be honored by the APT
conf (and it won’t work with an apt-cacher-ng like setup anyway).

>  3) Ensure that the netinst CD is installed on a network with working
>     Internet connection

I guess that’s the one that did prevent me to actually install Debian
Edu at work then: there is a working Internet connection, but that’s
behind a proxy…

>     This
>     also allow us to count the number of netinst installations

“Funny” that the popcon question is turned off by default, while this
one is silently turn on.

> I believe all of them are important to ensure a robust and well
> working installation experience.

Well, it only ensured that I couldn’t install tjener in a real life
environment so far, and it didn’t offer any alternative.

> Perhaps your problem is solved by specifying the proxy on the kernel
> boot prompt?  If so, I guess we should add the recipe to the manual.

Will report tomorrow if I manage to work around that issue this way
(even if I’ll have to change the apt-proxy setting after pinging an URL
just for the sake of being tracked, that I don’t find really useful).

Regards

David


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJR2yxuAAoJEAWMHPlE9r089n4H/RS0MZcqNdOsPZehl/WVWmGd
O7q+xPTSbEjrRfrl5zwYZj2iR9BSEh4e2EaKfpxM1ke+UocHMY76agR0krx9ru1R
UUcvrE/4kUsVvWnQvOwWNPgcZQkv1UQPAZwbxGaXMQRlE3nkgA58uLSTQOJ54pxf
HB9iWW+RTLavYFQKR8/RlqgySKgs+vKwkO1x3pGJiVY9ZKu9phzKF3eMJR4iaGWn
4yYGrc6Dbnoiix01nWkx6ObV4ac7cblOhtN5+/Z7HuSTdEmRPAYOydUnA3z7rEPE
JlRRBCnKrDwR4cqYJXDkN0qIMsd+XoobgQXecLXKCgG99tyOcfz5/Xm/D0JEDiA=
=DCdE
-----END PGP SIGNATURE-----


Reply to: