This is the function that writes to your sources template on install
# package and repo addition (13) _update and upgrade_
function _updates() {
...
cp ${local_setup}templates/apt.sources/ubuntu.template /etc/apt/sources.list
sed -i "s/RELEASE/${CODENAME}/g" /etc/apt/sources.list
apt-get -y -f install build-essential debian-archive-keyring \
python-software-properties software-properties-common >>"${OUTTO}" 2>&1
apt-get -y -f --allow-unauthenticated install deb-multimedia-keyring >>"${OUTTO}" 2>&1
...
Where ${CODENAME} is produced by lsb_release -cs
This is what the default Ubuntu Templates look like:
###### Ubuntu Main Repos
deb http://archive.ubuntu.com/ubuntu/ RELEASE main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ RELEASE main restricted universe multiverse
###### Ubuntu Update Repos
deb http://archive.ubuntu.com/ubuntu/ RELEASE-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ RELEASE-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ RELEASE-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ RELEASE-security main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ RELEASE-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ RELEASE-backports main restricted universe multiverse
###### Ubuntu Partner Repo
deb http://archive.canonical.com/ubuntu RELEASE partner
deb-src http://archive.canonical.com/ubuntu RELEASE partner
###### Ubuntu Multimedia
#deb http://www.deb-multimedia.org jessie main non-free
#deb-src http://www.deb-multimedia.org jessie main non-free
Thus, the word RELEASE
gets overwritten by "${CODENAME}"
As to why your sources.list is producing trusty as the source list is hard to say. We cannot reproduce this unless we manually punch in trusty
Also, you are pulling from nl.archives… the new version does not do this:
Get:31 http://nl.archive.ubuntu.com trusty-updates/multiverse Sources [5,939 B]
It now pulls directly from archive.ubuntu
as seen above. Either they botched the reinstall or something else is afoot here that has nothing to do with the script. Additional to this, it states the bc command is not found. This is an important factor for various functions of the script to perform a proper install.
I would request another reinstall, then you could PM me server info and I will install this first hand to see if any issues arise.