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

Update code from 4.0 to 4.2 #30

Open
DocCyblade opened this issue May 23, 2015 · 6 comments
Open

Update code from 4.0 to 4.2 #30

DocCyblade opened this issue May 23, 2015 · 6 comments
Assignees
Labels
Milestone

Comments

@DocCyblade
Copy link
Owner

Need to update current code base (using 4.0 package from wheezy) to using 4.2 package from jessie

@DocCyblade DocCyblade self-assigned this May 23, 2015
@DocCyblade DocCyblade added this to the v14.0.alpha milestone May 23, 2015
@DocCyblade
Copy link
Owner Author

Created new branch to use for update code, will merge back into dev when done. This should make a working 4.2 alpha

@DocCyblade
Copy link
Owner Author

Open notes:

I have started the progress on converting to 4.2 on jessie. Packages install fine, however database creation fails. A quick look, seems to point to a change in the database setup script. Will need to read up on the changes from 4.0 to 4.2

@DocCyblade
Copy link
Owner Author

Looked at the database script, that was fine. Looks like config file was moved somehow. Moved the config file back but that still bombed out. Found out that in 4.2 need a DatabaseAdmin account that is used for upgrades and installs. Added that to the conf file and it build ok. Still need to test the finial product.

Also need to figure out a way to change the rt_user password during first boot

@DocCyblade
Copy link
Owner Author

Last run showed no localhost/rt in browser. Also root does noaAt show typical TKL screen. Maybe something new with the common LAPP build with TKLDEV? Also getting strange error on first boot

screen shot 2015-05-24 at 6 01 36 pm

@JedMeister
Copy link

So you're using TKLDev v14 then I assume... If you have had it running a little while then perhaps you need to update common to the latest version? It should be fairly stable at this point (although still under heavy development inc daily merges...). LAPP should have been done and fairly stable I would expect (hope!).

As for the screenshot that you've shown is a bit of a bug with Jessie. Jessie uses systemd init system (as opposed to old sysvinit). One of the cool things about systemd is that it does synchronous boot; i.e. it doesn't wait for stuff to finish before it starts doing the next thing... That's generally awesome for boot times but not so nice for inithooks...

@DocCyblade
Copy link
Owner Author

Ahh that makes sense why this is going on, it's still booting (getting messages) while waiting for user input. Going to research systemd now, also going to look at the lapp only build. If I find some bugs in the lapp, I might just fork lapp and fix anything I find

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants