I try update Turris 1.x with OS 3.11.23 to OS 5.x

Software SW bugs discussion
,
#1

root@turris:~# pkgupdate
WARN:Package wpad is in cyclic dependency. It might fail its post-install script.
WARN:Package hostapd is in cyclic dependency. It might fail its post-install script.
WARN:Requested package luci-i18n-ddns-en that is missing, ignoring as requested.
INFO:Queue install of libgcc/turris/7.5.0-2
INFO:Queue install of libc/turris/1.1.24-2
INFO:Queue install of libintl-full/turris/0.19.8.1-2
INFO:Queue install of gettext-tools/turris/0.19.8.1-2
INFO:Queue install of create_notification/turris/61.5-1
INFO:Queue install of tos3to4-earliest/turris/2.3.0-1
INFO:Queue install of libjson-c/turris/0.12.1-3.1
INFO:Queue install of libubox/turris/2020-05-25-66195aee-1
INFO:Queue install of jsonfilter/turris/2018-02-04-c7e938d6-1
INFO:Queue install of busybox/turris/1.30.1-8
INFO:Queue install of ca-certificates/turris/20200601-1
INFO:Queue install of libopenssl/turris/1.1.1l-1
INFO:Queue install of libexpat/turris/2.2.9-1
INFO:Queue install of libbz2/turris/1.0.8-1
INFO:Queue install of libpthread/turris/1.1.24-2
INFO:Queue install of liblzma/turris/5.2.5-1
INFO:Queue install of zlib/turris/1.2.11-3
INFO:Queue install of libarchive/turris/3.4.2-1
INFO:Queue install of liburiparser/turris/0.9.5-1
INFO:Queue install of ca-bundle/turris/20200601-1
INFO:Queue install of libcurl/turris/7.66.0-3
INFO:Queue install of libevent2/turris/2.1.11-1
INFO:Queue install of liblua/turris/5.1.5-3
INFO:Queue install of libuci/turris/2019-09-01-415f9e48-4
INFO:Queue install of libuci-lua/turris/2019-09-01-415f9e48-4
INFO:Queue install of updater-ng/turris/69.1.3-2
Press return to continue, CTRL+C to abort

INFO:Executing preupdate hook: 05_schnapps.sh
Snapshot number 13 created
INFO:Unpacking download packages
INFO:Checking for file collisions between packages
line not found
line not found
line not found
line not found
line not found
line not found
DIE:
[string “transaction”]:334: [string “transaction”]:158: Collisions:
• /usr/bin/gettext_filter: gettext (existing-file), gettext-tools (new-file)
• /usr/bin/gettext: gettext (existing-file), gettext-tools (new-file)
Aborted
root@turris:~#
I have delete gettext?

1 Like
Updating from 3.11.23 to 5.x
#2

Thanks for letting this issue to us. We are aware of it, and we are looking into it.

2 Likes
#3

Same issue on my Turris 1.x with OS 3.11.23

#4

It’s going to be fixed once Turris OS 5.3.1 is released.

#6

Thanks, when we can expect Turris OS 5.3.1?

#7

I would say that we will release Turris OS 5.3.1 next week.

1 Like
#8

Turris 1.1 - OS 3.11.23. It all looks okay. There’s no need for an update. :wink:

#9

Anything new to that upgrade error? I’m also stuck with the error:

" Updater selhal:

[string “transaction”]:334: [string “transaction”]:158: Collisions:

• /usr/bin/gettext_filter: gettext (existing-file), gettext-tools (new-file)

• /usr/bin/gettext: gettext (existing-file), gettext-tools (new-file) "

#10

I have the same issue while attempting an upgrade.

Getting spammed with:
## Error from 2021/11/22 13:46:51
Updater selhal:

[string "transaction"]:334: [string "transaction"]:158: Collisions:

• /usr/bin/gettext_filter: gettext (existing-file), gettext-tools (new-file)

• /usr/bin/gettext: gettext (existing-file), gettext-tools (new-file)
#11

I have the exact same issue (Omnia, OS version 3.11.23).
Now even automatic updates are not working for me with identical error message.

Is there a manual workaround until patched 5.3.1 is released?

#12

I’m also waiting for a solution. I can’t install packages that I need to use eg. OpenVPN. Every time I try to enter pkgupdate via ssh I get an error:

DIE:
[string "transaction"]:334: [string "transaction"]:158: Collisions:
• /usr/bin/gettext_filter: gettext (existing-file), gettext-tools (new-file)
• /usr/bin/gettext: gettext (existing-file), gettext-tools (new-file)
Aborted
1 Like
#13

We released Turris OS 5.3.1 into the stable branch a few minutes ago, and the migration works. :white_check_mark:

1 Like
#14

@Pepe, I just noticed and it looks like the upgrade went flawless, at first glance at least. Thank you for addressing this issue with 5.3.1.

2 Likes
#15

@Pepe Upgrade now worked fine for me too, thanks a lot :slight_smile:

1 Like
#16

@Pepe For me too. I’m so excited that my 6 year old router (Turris 1.1) is back to the current firmware version, TurrisOS 5 is a big leap forward. Thank you

1 Like
#17

Upgrade went very well. No problems. It look and feels very nice :slight_smile:

1 Like
#18

Well, after a long time, we got so much positive feedback. :blush: I’m glad that it works for all of you guys — also, thanks for sharing it with us.

If you have any troubles, don’t hesitate to reach me or any colleagues. We plan that we would like to push automatic migration next week.

#19

Well, today I noticed my Omnia is not accesible by web UI (no foris, reforis or luci).
It sometimes happened to me when the web interface got updated (500 server error) and router was not rebooted yet. But this time also SSH nor LuCi was not responding so I reset the router and it went into some kind of bootloop. Never getting past the phase when in would set custom led colors and still not responding web nor ssh interface.

Reset to previous snapshot did not resolve the issue. I ended up doing a factory reset using latest medkit from USB. So my upgrade issue got “resolved” too, just not the way I was hoping for. :cry:

Since I first encountered the upgrade issue I tried to uninstall the migration package in Forris but my router was still unable to perform updates. There is probably nothing left from the broken state, but I can try to provide more info if useful. (I have some configuration backups.)

#20

I recall encountering this when I first did my upgrade from 3.x to 5.x. If you really want to roll back, you have to go two snapshots back.

There may be more information in one of the old migration threads here:

If you have any comfort with the command line, I would recommend getting a little familiar with schnapps. You may be able to get back to your working 3.11.23 install and re-try from there.

#21

It probably would have helped to rollback more snapshots, damn. At least I got a fresh start. :slight_smile:

Thanks for pointing me to schnaps. It seems there are no old snapshots left after I did restore using the medkit. But it may come handy in future.

1 Like