[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#786763: redmine: error messages during update of ruby-rails packages

Hello Niels,

Thanks for your insight. Maybe you can help me a little further?

On Sat, May 30, 2015 at 07:46:02AM +0200, Niels Thykier wrote:
> The output from dpkg suggests redmine has an /awaiting/ trigger cycle.
> In particular, on itself?  Indeed, redmine has the following triggers:
> """
> interest /usr/share/redmine/plugins
> interest /usr/lib/ruby/vendor_ruby
> """
> (From
> http://anonscm.debian.org/cgit/pkg-ruby-extras/redmine.git/tree/debian/redmine.triggers)

redmine does not install files on either of those locations, so how
could it be triggering itself?

> If possible, please consider switching these to noawait variants (though
> note that noawait may defer the trigger a bit longer).  Alternatively,
> if noawait triggers do not provide enough guarantees, you may have to
> replace the interest triggers all together.  Please note that:
>   * No package /depending/ on redmine can use an "await" trigger.
>     If they do, it will lead to a trigger cycle.
> Please see man 5 deb-triggers for more information.

For both triggers, redmine could be acvitated at the very end of the
upgrade without problem. So IIUC just switching to interest-noawait
would fix this?

Antonio Terceiro <terceiro@debian.org>

Attachment: signature.asc
Description: Digital signature

Reply to: