[Bug 1914880] [NEW] xenial package for redshift is out of date (1.10 < 1.12)
Public bug reported: This isn't a bug with the application itself, just that the package in the 16.04 (xenial) repositories is out of date. The current release is 1.12, however the version in the xenial repos is 1.10. What needs to happen to get the package updated? Can I help? ** Affects: redshift (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914880 Title: xenial package for redshift is out of date (1.10 < 1.12) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/1914880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994063] Re: do-release-upgrade can't be continued after drop to shell
For posterity, here's a cross reference to the forum post that landed me here: https://ubuntuforums.org/showthread.php?t=1969849 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994063 Title: do-release-upgrade can't be continued after drop to shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/994063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994063] Re: do-release-upgrade can't be continued after drop to shell
Potential recovery: For what it's worth. I just ran into this issue and recovered using reptyr. I had to build it from source from https://github.com/nelhage/reptyr though, as apt was locked up. * run 'pstree -p' to find the PID to reconnect to. The tree looked something like: - trusty - ??? - bash - emacs You want to PID of the leaf node here (in this case emacs) * Then run 'reptyr PID'. This will land you back in your editor with potentially a bunged up terminal state (which is why you're in this mess to begin with). Exit your editor safely (in my case, emacs wouldn't accept C- commands, but handled ESC-x save-buffers-kill-terminal). * Clean up whatever you were cleaning up (being careful of course) * Run 'exit', as do-release-upgrade instructed In my case, I was still slightly screwed because I messed up the pty of the 'trusty' process above while I was trying to figure this out. My apt and dpgk state was okay though, so I could just restart the upgrade. But I think this will allow you to resume your current release upgrade unscathed. I'd be interested to hear reports if anyone tries this. Hopefully this helps someone! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994063 Title: do-release-upgrade can't be continued after drop to shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/994063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
