On 2015-01-28 19:41, Niels Thykier wrote:
On 2015-01-28 19:34, Jonathan Nieder wrote:
(dpkg - bcc)
Niels Thykier wrote:
Any updates on this bug? The gitweb trigger cycle is currently the last
trigger cycle left[1].
It should be interest-noawait. I was preparing an upload to do that,
but
On 2015-01-08 09:56, Guillem Jover wrote:
Hi!
On Wed, 2015-01-07 at 17:07:14 -0800, Jonathan Nieder wrote:
Guillem Jover wrote:
In this case though, it seems switching to interest-noawait is the
correct fix, because gitweb just wants to be notified when the
apache2-maintscript-helper
(dpkg - bcc)
Niels Thykier wrote:
Any updates on this bug? The gitweb trigger cycle is currently the last
trigger cycle left[1].
It should be interest-noawait. I was preparing an upload to do that,
but other things preempted that :/. I will try to make the upload
tonight and don't mind if
On 2015-01-28 19:34, Jonathan Nieder wrote:
(dpkg - bcc)
Niels Thykier wrote:
Any updates on this bug? The gitweb trigger cycle is currently the last
trigger cycle left[1].
It should be interest-noawait. I was preparing an upload to do that,
but other things preempted that :/. I will
Hi!
On Wed, 2015-01-07 at 17:07:14 -0800, Jonathan Nieder wrote:
Guillem Jover wrote:
In this case though, it seems switching to interest-noawait is the
correct fix, because gitweb just wants to be notified when the
apache2-maintscript-helper program appears to be able to configure
Control: unmerge -1
Control: reopen -1
Control: affects -1 - gitweb src:git
Control: reassign -1 gitweb 1:2.1.4-2
Control: forcemerge 774803 -1
Hi!
Giving it back. :)
On Mon, 2015-01-05 at 16:54:19 -0800, Jonathan Nieder wrote:
Jonathan Nieder wrote:
Erwan David wrote[1]:
dpkg: cycle
Guillem Jover wrote:
In this case though, it seems switching to interest-noawait is the
correct fix, because gitweb just wants to be notified when the
apache2-maintscript-helper program appears to be able to configure
itself, but apache does not care and does not need to await the
trigger
Hi dpkg maintainers,
Erwan David wrote[1]:
Package: gitweb
Version: 1:2.1.4-2
Severity: normal
When upgrading apache and gitweb I get :
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
gitweb - gitweb
packages' pending
reassign 774607 dpkg 1.7.22
affects 774607 + gitweb src:git
forcemerge 771730 774607
quit
Jonathan Nieder wrote:
Erwan David wrote[1]:
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
gitweb - gitweb
packages' pending triggers
Package: gitweb
Version: 1:2.1.4-2
Severity: normal
When upgrading apache and gitweb I get :
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
gitweb - gitweb
packages' pending triggers which are or may be unresolvable:
gitweb:
10 matches
Mail list logo
