If the current unstable version is a "release candidate", why is there
an soname bump between that and the final release in experimental? What
is the API impact of this transition? Or, if there is no API impact, is
it possible that there is also no ABI impact aside from the soname
change itself and the soname bump decision might be reverted before this
is released from experimental to unstable?
Have you rebuilt all reverse-dependencies in Ubuntu and verified that
they work with the final release? Have you run autopkgtests? (Not
required but useful to know the results if you have)
** Changed in: octave (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791359
Title:
FFe: Sync octave 4.4.1-1 (universe) from Debian experimental (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1791359/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
