Network Installation UCS 4.2

opsi
ucs-4-2

#1

Hi,

i’m from uib gmbh.
Currently I am trying to create an UCS 4.2 installatiom from a local apache.
To get the packages I move them to the right place, create Packages.gz etc.

Currently the installation fails because of debootstrap. The issue is the same as here:

/var/log/syslog:
Mar 21 18:18:36 debootstrap: EA: /usr/share/debootstrap/scripts/ucs420
Mar 21 18:18:36 debootstrap: EF: No such script: %s

ls /usr/share/debootstrap/scripts/ lists only the following:
~ # ls /usr/share/debootstrap/scripts/u*
/usr/share/debootstrap/scripts/ucs400 /usr/share/debootstrap/scripts/ucs410
/usr/share/debootstrap/scripts/ucs401 /usr/share/debootstrap/scripts/ucs411
/usr/share/debootstrap/scripts/ucs402 /usr/share/debootstrap/scripts/ucs412
/usr/share/debootstrap/scripts/ucs403 /usr/share/debootstrap/scripts/ucs413
/usr/share/debootstrap/scripts/ucs404 /usr/share/debootstrap/scripts/ucs414
/usr/share/debootstrap/scripts/ucs405 /usr/share/debootstrap/scripts/utopic

I can verify that the ucs420 script is indeed missing.
The 420 script might just be a link to sid, or jessie. Just as the 41x scripts are linked to wheezy.

here’s the content from
debootstrap_1.0.67A~4.2.0.201703021721_all.deb

breezy feisty intrepid lucid potato sarge.buildd stable ucs401 ucs410 unstable wheezy dapper gutsy jaunty maverick precise sarge.fakechroot stretch ucs402 ucs411 utopic woody edgy hardy jessie natty quantal saucy testing ucs403 ucs412 vivid woody.buildd etch hoary karmic oldstable raring sid trusty ucs404 ucs413 warty etch-m68k hoary.buildd lenny oneiric sarge squeeze ucs400 ucs405 ucs414 warty.buildd

Could you please fix this?

Cheers
mathias


#2

Hi,

i can see you also created a bug entry for this issue. As a workaround, please create the link manually:
ln -s /usr/share/debootstrap/scripts/jessie /usr/share/debootstrap/scripts/ucs420

Does this fix your issue?


#3

yes it works creating a link.

The system currently installs fine.

But as we want to install UCS420 on a regular basis for automated tests, this is nothing we want to do in our tests.

Thanks for the temporary solution.