Jörg-Volker On Friday, April 18, 2025 2:57:26 AM Mountain Standard Time Jörg- Volker Peetz wrote: > Hi Soren, > > thanks for taking care of this. > > Soren Stoutner wrote on 17/04/2025 23:48: > > On Friday, April 11, 2025 5:27:14 PM Mountain Standard Time Soren > > > Stoutner wrote: > <snip> > > > Lintian and piuparts don’t indicate any problems, so I have > > uploaded redmine 6.0.4+ds-2, which includes this change. > > In sid I tried the following: > > - down-grade ruby-nokogiri to version 1.18.2+dfsg-1 from > 1.18.2+dfsg-1+b1 dpkg -i ruby-nokogiri_1.18.2+dfsg-1_amd64.deb > - remove all redmine references from /var/lib/dpkg/triggers/File > - upgrade redmine to 6.0.4+ds-2 > as to be expected, this adds 4 lines to > /var/lib/dpkg/triggers/File : /usr/share/redmine/plugins > redmine/noawait > /usr/lib/ruby/vendor_ruby redmine/noawait > /usr/share/rubygems-integration redmine/noawait > /usr/lib/*/rubygems-integration redmine/noawait > - upgrade ruby-nokogiri to 1.18.2+dfsg-1+b1 > apt -t sid install '~U~nby-nokogiri' > > This did not trigger the reconfiguration of redmine. > > Then I tried this: > > - down-grade ruby-nokogiri to version 1.18.2+dfsg-1 again > - adding the following line at the end of var/lib/dpkg/triggers/File > : /usr/lib/x86_64-linux-gnu/rubygems-integration redmine/noawait - > upgrade ruby-nokogiri to 1.18.2+dfsg-1+b1 > > This now triggered the reconfiguration of redmine. > > Therefore, I think the wildcard '*' isn't working in trigger files. > > Maybe, there is a method to determine the architecture during > installation? And let the trigger file redmine.trigger be adapted > by the preinst script? > > Alternatively, just include a trigger line for every supported > architecture?
Thanks for testing this. I will upload a version shortly that includes a line for every supported architecture as that seems to be the only way to handle this. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
