omap install ends up with security.ubuntu.com urls in sources.list after install

Is this specific to beagle?

How did you install? which image

I did an install on imx51 just a few days ago and did not see this bug there

looking at the apt-setup code i found the following in generators/91security:

# Awful Ubuntu-specific hack. *-security suites for ports architectures
# aren't available on security.ubuntu.com, only on ports.ubuntu.com.
if [ "$host" = security.ubuntu.com ]; then
        db_get mirror/protocol
        protocol="$RET"
        db_get mirror/$protocol/hostname
        if [ "$RET" = ports.ubuntu.com ]; then
                host="$RET"
                db_get mirror/$protocol/directory
                directory="$RET"
        fi
fi

my install was using a local mirror so ports.ubuntu.com can nowhere be matched in debconf data

probably using archdetect would be a better approach in this code snippet

@lool: i was following https://wiki.ubuntu.com/ARM/BeagleNetInstall (but with local mirror as mentioned)

Oh, local mirror. This is awkward because I don't want to hardcode the list of ports architectures in lots of different places. Can we defer this to Maverick please, since if you're using a local mirror then you can also preseed apt-setup/security_host and apt-setup/security_path?

heh, i definately didnt expect a fix for lucid, else i would have set severity and milestone :)

(I am personally fine deferring this to maverick)

Would it be an option to actually test whether the default security.ubuntu.com mirror supports the target arch to decide to enable it?

I can see why you ask that, but it would make the code flow quite twisty
in this case. I would prefer to just have it hooked into
choose-mirror's architecture handling if possible.

While we do not use this install method for currently supported armel images (omap), I can confirm this behavior still is present in natty. This should be addressed next cycle if we plan on supporting more systems.