All autopkgtests for the newly accepted gst-plugins-bad1.0 (1.26.0-1ubuntu2.2) for plucky have finished running. The following regressions have been reported in tests triggered by the package:
gsequencer/7.5.5-1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/plucky/update_excuses.html#gst-plugins-bad1.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2109413 Title: Plugin nvcodec is missing on plucky amd64 Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Plucky: Fix Committed Bug description: [ Impact ] * Users expect to find the nvcodec plugin available in the -bad set, which is used for all sorts of filtering and acceleration tasks leveraging NVIDIA GPUs. * Due to a recent packaging bug, which intended to disable this plugin for ARM platforms, but accidentally enabled it *only* for ARM platforms, excluding all others, resulting in the original bug report. * Debian have reverted this exclusion logic entirely, since the original issues requiring it not be built for ARM platforms have been resolved. * This SRU simply cherry-picks the revert of this packaging change, fixing the bug. [ Test Plan ] * To reproduce the bug, from a plucky installation, $ sudo apt install gstreamer1.0-plugins-bad $ gst-inspect-1.0 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstnvcodec.so No such element or plugin '/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstnvcodec.so' * With the new package, the gst-inspect-1.0 command should provide details about the plugin. [ Where problems could occur ] * Auto-plugging elements may now pick up the NVCODEC plugin instead of say a software fallback. Behaviour there could change, although I don't know of any applications in practice that would be available to test this. It should be noted this is not introducing a new feature, but rather restoring prior behaviour due to an upstream packaging accident picked up in Plucky. [ Other Info ] * The merge proposal for questing is available at - https://salsa.debian.org/gstreamer-team/gst-plugins-bad1.0/-/merge_requests/19 * The merge proposal for plucky is available at - https://salsa.debian.org/gstreamer-team/gst-plugins-bad1.0/-/merge_requests/20 * PPA: https://launchpad.net/~charles05/+archive/ubuntu/ppa/+build/31106373 [ Original Bug Report ] I noticed that on plucky the nvcodec plugin (libgstnvcodec.so) is missing. https://packages.ubuntu.com/plucky/amd64/gstreamer1.0-plugins-bad/filelist (missing) https://packages.ubuntu.com/jammy/amd64/gstreamer1.0-plugins-bad/filelist (there) Upon further inspection I could not find anything in the Changelog that mentioned any changes to nvcodec. I then noticed that it IS present in the plucky arm64 build: https://packages.ubuntu.com/plucky/arm64/gstreamer1.0-plugins- bad/filelist (there) So I am guessing something went wrong during the build and this went unnoticed? gstreamer1.0-plugins-bad/plucky,now 1.26.0-1ubuntu2 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2109413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
