[Bug 1862364] Re: mysql-8.0 FTBFS (focal) because of hardcoded date in test

2020-02-09 Thread Rafael David Tinoco
** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Confirmed

** Changed in: mysql-8.0 (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862364

Title:
  mysql-8.0 FTBFS (focal) because of hardcoded date in test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862364/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1860277] Re: Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade cannot be repaired due to mysql-5.7 being unavailable after upgrade to Ubuntu 19.10

2020-02-09 Thread Rafael David Tinoco
Hello Jeroen,

Can you provide steps so I can reproduce this issue ?

What parts of mysql_upgrade inplace upgrade are not working ?

Trying to reproduce I get:

$ sudo mysql_upgrade -u root -p
Enter password:
The mysql_upgrade client is now deprecated. The actions executed by the upgrade 
client are now done by the server.
To upgrade, please start the new MySQL binary with the older data directory. 
Repairing user tables is done automatically. Restart is not required after 
upgrade.
The upgrade process automatically starts on running a new MySQL binary with an 
older data directory. To avoid accidental upgrades, please use the 
--upgrade=NONE option with the MySQL binary. The option --upgrade=FORCE is also 
provided to run the server upgrade sequence on demand.
It may be possible that the server upgrade fails due to a number of reasons. In 
that case, the upgrade sequence will run again during the next MySQL server 
start. If the server upgrade fails repeatedly, the server can be started with 
the --upgrade=MINIMAL option to start the server without executing the upgrade 
sequence, thus allowing users to manually rectify the problem.

Have you tried --upgrade=MINIMAL option when restarting the deamon ?

I'm flaging this as incomplete until you provide more information AND a
way we can reproduce what you have faced, but, there are some scenarios
that mysqld might need manual intervention in the inplace update for it
to finish.

Thank you

Rafael

** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to mysql-8.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1860277

Title:
  Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade
  cannot be repaired due to mysql-5.7 being unavailable after upgrade to
  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1860277/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1860277] Re: Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade cannot be repaired due to mysql-5.7 being unavailable after upgrade to Ubuntu 19.10

2020-02-09 Thread Rafael David Tinoco
Feel free to move this bug back to "New" when you report the requested
information.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1860277

Title:
  Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade
  cannot be repaired due to mysql-5.7 being unavailable after upgrade to
  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1860277/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1861555] Re: Move window behaviour is broken because of a change in tmux

2020-02-09 Thread Dustin Kirkland 
** Changed in: byobu (Ubuntu Focal)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1861555

Title:
  Move window behaviour is broken because of a change in tmux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1861555/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs