Alexandre Takacs's picture

Hello

I have just migrated a Typo3 appliance from tkl12 to tkl13 using TKLBAM.

Overall the process was pretty seamless but I still see some issues: in some places new instance after migration "thinks" that it is old tkl12

SSH banner Welcome to Typo3, TurnKey Linux 13.0 / Debian 6.0.9 Squeeze
root@typo3 ~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.9 (squeeze)
Release: 6.0.9 Codename: squeeze

but

root@typo3 ~# apt-get update
Hit hXXp://cdn.debian.net wheezy Release.gpg
Hit hXXp://cdn.debian.net wheezy Release
Hit hXXp://archive.turnkeylinux.org wheezy-security Release.gpg
(more here)
Reading package lists... Done

Is that normal / epxected ?!

(links forcibely removed as they trigger the spam filter)

Forum: 
Jeremy Davis's picture

It looks like some of the release info is being backed up (and restored) by TKLBAM, that probably shouldn't be...

We'll need to look into that and fix it. I don't expect that it will create any issues though (hopefully!).

I have filed a bug report.

Alexandre Takacs's picture

Thanks for you follow up - so it would seem that it is mostly a cosmetic issue...


Jeremy Davis's picture

Which it looks like it is, then it shouldn't be an issue. So like you say I imagine that it is only cosmetic.

Still, thanks for reporting it and it shouldn't do that so we'll need to fix it.

turnkeylinux@atc.ch's picture

Did you get a reaction from the devs (nothing public apparently).

I am not sure this is only cosmetic. For instance I just caught an issue with webmin

In old server and new server paths to webmib are different.

Example of config:
In old config /etc/webmin/miniserv.conf
root=/usr/share/webmin-1.680
mimetypes=/usr/share/webmin-1.680/mime.types

In new config /etc/webmin/miniserv.conf
root=/usr/share/webmin
mimetypes=/usr/share/webmin/mime.types

In start/stop scripts the same.

 

Jeremy Davis's picture

I'm sure they'll get it when they have time...

I'm guessing that that change in the Webmin conf may make Webmin not run? Is that the case?

In the meantime, if you still have your v12.x server running you could use the overrides to avoid including those files in your backup.

PS I was going to update the other bug, but I decided instead to lodge a new one because although the cause is the same, the bug is different...

Alexandre Takacs's picture

Indeed this precluded webmin from working had to manually edit the config files.


Add new comment