[Bug 820306] Re: debconf item apt-setup/security_path not fully honoured

[javierpb]

Please apologize for misreading the comment.
Once enabled the proposed component boot parameter, with the old the security updates were searched on the right place.
I need to manually select a kernel package, but I guess that is unrelated to this bug, which I consider closed (at least for lucid release which I reported and verified now).
In case could be useful, I attach the installer syslog.

** Attachment added: "syslog.gz"
   https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/820306/+attachment/2299092/+files/syslog.gz

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to base-installer in Ubuntu.
https://bugs.launchpad.net/bugs/820306

Title:
  debconf item apt-setup/security_path not fully honoured

Status in “base-installer” package in Ubuntu:
  Fix Released
Status in “base-installer” source package in Lucid:
  Fix Committed
Status in “base-installer” source package in Maverick:
  Fix Committed
Status in “base-installer” source package in Natty:
  Fix Committed
Status in “base-installer” source package in Hardy:
  Fix Committed

Bug description:
  Stable release update justification:

  Impact: When the -security URL uses some path other than /ubuntu, security updates may not be installed as early during installation as they're supposed to be, and it's possible that there are corner cases where the -security entries are never set up correctly.
  Development branch: Fixed in base-installer 1.119ubuntu4.
  Patch: http://bazaar.launchpad.net/~ubuntu-core-dev/base-installer/ubuntu/revision/959
  TEST CASE: Find a -security mirror which is not rooted at /ubuntu.  Use preseeding similar to that used in the original report to select it during a server installation.  Look for 404 errors referring to Ubuntu in the logs during the base-installer phase of installation: there should be none.  You will need to use the 'apt-setup/proposed=true' boot parameter to test the proposed update for this bug.
  Regression potential: As long as installations complete successfully and the 'apt-get update' during base-installer is free of errors, we should be fine.

  Original report follows:

  I do a 10.04 netinstall with a preseed file, using local mirrors for the repositories. Security repository is defined with
  d-i apt-setup/security_host string 192.168.40.2
  d-i apt-setup/security_path string  /mirror/ubuntu-security
  And the logs from the apache serving the mirror shows some attempts for http://192.168.40.2/ubuntu.
  So it looks like that '/ubuntu' is somewhere hardcoded in the installer.

  When doing the same for lenny, I use
  apt-setup/security_host string 192.168.40.2/repomirror/debian-security
  and works without any issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/820306/+subscriptions