On Thu, Jan 08, 2015 at 02:47:05AM +0100, Guillem Jover wrote:
[ @deity: please check out the dbus issue below. ]
[..]
[ Re dbus issue ]
Noted. Do we (still?) have a (reliable) way of reproducing the dbus
trigger issue?
We didn't up to now (AFAIK), but there's now very valuable data from
Hi!
On Tue, 2015-01-13 at 15:08:01 +0100, Michael Vogt wrote:
On Thu, Jan 08, 2015 at 02:47:05AM +0100, Guillem Jover wrote:
[ Re dbus issue ]
Noted. Do we (still?) have a (reliable) way of reproducing the dbus
trigger issue?
We didn't up to now (AFAIK), but there's now very
[ @deity: please check out the dbus issue below. ]
Hi!
On Sat, 2014-12-27 at 18:45:38 +0100, Niels Thykier wrote:
I hope you are feeling better now. :)
Yes, much better, thanks. :)
TL;DR: Please upload dpkg/1.17.23 with the proposed fix for #771730 at
your earliest convenience - by the
On 2014-12-23 04:36, Guillem Jover wrote:
Hi!
Hi,
On Sun, 2014-12-21 at 09:57:51 +0100, Niels Thykier wrote:
It possibly still is since the version that introduced the trigger
checks. I hope we can have it resolved shortly.
Yeah, I'm planning to upload tomorrow, sorry about the
Hi!
On Tue, 2014-12-23 at 02:52:01 +0100, Guillem Jover wrote:
On Sun, 2014-12-21 at 21:38:31 +0100, Niels Thykier wrote:
I do not recall (all of?) these trigger cycles being known. @Guiliem,
can you have a look at them and file bugs as necessary for these?
These smell like instances of
On Wed, 2014-12-24 at 02:26:24 +0100, Guillem Jover wrote:
On Tue, 2014-12-23 at 02:52:01 +0100, Guillem Jover wrote:
On Sun, 2014-12-21 at 21:38:31 +0100, Niels Thykier wrote:
I do not recall (all of?) these trigger cycles being known. @Guiliem,
can you have a look at them and file bugs
Hi!
On Sun, 2014-12-21 at 21:38:31 +0100, Niels Thykier wrote:
Thanks. We noticed the following results with the dpkg/1.17.22:
19:49 h01ger
Hi!
On Sun, 2014-12-21 at 09:57:51 +0100, Niels Thykier wrote:
It possibly still is since the version that introduced the trigger
checks. I hope we can have it resolved shortly.
Yeah, I'm planning to upload tomorrow, sorry about the delay, was not
feeling quite well the past couple of days.
CC: @deity (look for a couple of @deitys below)
On 2014-12-19 20:35, Guillem Jover wrote:
Hi!
On Wed, 2014-12-17 at 22:18:12 +0100, Niels Thykier wrote:
On 2014-12-16 06:22, Guillem Jover wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Hi,
On Sonntag, 21. Dezember 2014, Niels Thykier wrote:
As I recall, it is not a requirement - but I believe we can recommend it
in the release-notes. Although, with the Breaks being added to dpkg for
trigger issues, you would quite possibly pull in additional upgrades
along with it.
By
On 2014-12-21 14:54, Holger Levsen wrote:
Hi,
On Sonntag, 21. Dezember 2014, Niels Thykier wrote:
As I recall, it is not a requirement - but I believe we can recommend it
in the release-notes. Although, with the Breaks being added to dpkg for
trigger issues, you would quite possibly pull
Hi!
On Wed, 2014-12-17 at 22:18:12 +0100, Niels Thykier wrote:
On 2014-12-16 06:22, Guillem Jover wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: block -1 by 770627
I'd prefer if 1.17.22 could be unblocked
On 2014-12-16 06:22, Guillem Jover wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: block -1 by 770627
Hi!
I'd like to upload dpkg 1.17.23 with the following changes. I've
excluded and filtered translation
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: block -1 by 770627
Hi!
I'd like to upload dpkg 1.17.23 with the following changes. I've
excluded and filtered translation changes. I'm including a patch series
instead of a
14 matches
Mail list logo
