Bug#774791: xine-ui: Creates dpkg trigger cycle via libxine2-ffmpeg, libxine2-misc-plugins or libxine2-x
control: tag -1 patch On Wed, Jan 7, 2015 at 12:30 PM, Niels Thykier wrote: The libxine2-ffmpeg, libxine2-misc-plugins and libxine2-x packages have a trigger cycle via the xine-ui package. This was detected by a script on jenkins.debian.net[1]. Hi, I reviewed xine's trigger usage, and it looks correct to me to use interest-noawait since the trigger is used just for updating xine's .desktop file. Best wishes, Mike diff -Nru xine-ui-0.99.9/debian/changelog xine-ui-0.99.9/debian/changelog --- xine-ui-0.99.9/debian/changelog 2014-10-06 11:12:05.0 + +++ xine-ui-0.99.9/debian/changelog 2015-01-14 04:08:07.0 + @@ -1,3 +1,10 @@ +xine-ui (0.99.9-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Use interest-noawait trigger (closes: #774791). + + -- Michael Gilbert mgilb...@debian.org Wed, 14 Jan 2015 04:07:45 + + xine-ui (0.99.9-1.1) unstable; urgency=medium * Non-maintainer upload diff -Nru xine-ui-0.99.9/debian/xine-ui.triggers xine-ui-0.99.9/debian/xine-ui.triggers --- xine-ui-0.99.9/debian/xine-ui.triggers 2014-10-06 11:12:05.0 + +++ xine-ui-0.99.9/debian/xine-ui.triggers 2015-01-14 04:09:32.0 + @@ -1 +1 @@ -interest /usr/lib/xine/plugins +interest-noawait /usr/lib/xine/plugins
Bug#774791: xine-ui: Creates dpkg trigger cycle via libxine2-ffmpeg, libxine2-misc-plugins or libxine2-x
Source: xine-ui Version: 0.99.9-1.1 Severity: serious Hi, The libxine2-ffmpeg, libxine2-misc-plugins and libxine2-x packages have a trigger cycle via the xine-ui package. This was detected by a script on jenkins.debian.net[1]. Steps to reproduce the cycle (in a Jessie/sid chroot): apt-get install xine-ui libxine2-ffmpeg dpkg --unpack /var/cache/apt/archives/libxine2-ffmpeg_*.deb dpkg --configure --pending (Similar for the other libxine2-* binaries) This simulates an upgrade scenario, where libxine2-ffmpeg might be temporarily deconfigured while xine-ui remains configured. If this happens, dpkg is unable to recover as the cycle due to await trigger AND the dependency requires both packages to be configured. Known solutions: * Use no-await triggers. *CAVEAT*: not always applicable. Known suitable use cases includes cache handling, where the cache is allowed to be out of date tempoarily. * Reduce the dependency to Recommends. *CAVEAT*: Rarely applicable. * Rewrite the solution to avoid triggers entirely. *CAVEAT*: May be non-trivial and likely to involve updates to all packages relying on the trigger. ~Niels [1] https://jenkins.debian.net/view/Warnings/job/dpkg_sid_find_trigger_cycles/32/console -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
