Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade scripts fail due to replaced autoupdater #1310

Closed
lephisto opened this issue Jan 16, 2018 · 5 comments
Closed

upgrade scripts fail due to replaced autoupdater #1310

lephisto opened this issue Jan 16, 2018 · 5 comments
Assignees
Labels
0. type: bug This is a bug

Comments

@lephisto
Copy link

lephisto commented Jan 16, 2018

The Upgrade Script of the autoupdater fails due to replacement of the package in gluon-packages:

        no field package.preload['autoupdater.util']
        no file './autoupdater/util.lua'
        no file '/usr/share/lua/autoupdater/util.lua'
        no file '/usr/share/lua/autoupdater/util/init.lua'
        no file '/usr/lib/lua/autoupdater/util.lua'
        no file '/usr/lib/lua/autoupdater/util/init.lua'
        no file './autoupdater/util.so'
        no file '/usr/lib/lua/autoupdater/util.so'
        no file '/usr/lib/lua/loadall.so'
        no file './autoupdater.so'
        no file '/usr/lib/lua/autoupdater.so'
        no file '/usr/lib/lua/loadall.so'
stack traceback:
        [C]: in function 'require'
        /lib/gluon/upgrade/500-autoupdater:29: in main chunk
        [C]: ?
 error

This happens because of https://github.com/freifunk-gluon/packages/commit/49cb4b3fdb8b9db0abb81783b9b3b386a8ed6a92.

It breaks some stuff, because several other script are kept from being executed..

@rotanid rotanid added the 0. type: bug This is a bug label Jan 16, 2018
@neocturne
Copy link
Member

For the record: This was breaking the creation of the autoupdater cron job, nothing else.

@lephisto
Copy link
Author

.. als the jobs afterwards when for instance running domain_changed.sh

500-mesh-vpn
500-node-info-system
500-opkg
500-radvd-remove-user
500-status-page-api
510-node-info-role
520-node-info-whitespace-fix
800-migrate-batadv
820-dns-config
981-firewall-status-page
998-commit
999-version

I noticed that while testing domain-select. Thanks for fixing.

@neocturne
Copy link
Member

neocturne commented Jan 17, 2018

This is an issue in domain_changed.sh then, failing scripts should only print an error message and not break anything else.

@lephisto
Copy link
Author

@kb-light should maybe have a look at this.

@rotanid
Copy link
Member

rotanid commented Jan 17, 2018

no, @lemoer is the author of domain_changed.sh ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. type: bug This is a bug
Projects
None yet
Development

No branches or pull requests

3 participants