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

Bug#921651: marked as done (unblock: syslog-ng/3.19.1-3)

Your message dated Thu, 7 Feb 2019 23:11:46 +0100
with message-id <CAKjSHr1=oEJR-3CCxGefqR3xL6BmeKaG1oyDMgvPAfHXdjFh9g@mail.gmail.com>
and subject line Re: Bug#921651: unblock: syslog-ng/3.19.1-3
has caused the Debian Bug report #921651,
regarding unblock: syslog-ng/3.19.1-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
921651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921651
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Hi Release Team,

Please push syslog-ng to Buster. It can't migrate on its own probably
due to breaking syslog-ng-incubator. But the latter is scheduled to be
removed and will not be part of Buster.

Thanks,
Laszlo/GCS

--- End Message ---
--- Begin Message --- 
On Thu, Feb 7, 2019 at 11:02 PM Mattia Rizzolo <mattia@debian.org> wrote:
> On Thu, Feb 07, 2019 at 05:47:35PM +0100, László Böszörményi wrote:
> > Please push syslog-ng to Buster. It can't migrate on its own probably
> > due to breaking syslog-ng-incubator. But the latter is scheduled to be
> > removed and will not be part of Buster.
>
> That indeed seems the case, but I think your request was too rush.
>
> syslog-ng-incubator was removed today from unstable, and will so be
> automatically removed from testing tonight.  After that, syslog-ng will
> also migrate.
 I didn't expect FTP Masters to be that quick, kudos to them!

> Also, the correct course of action would not be to "push" syslog-ng
> (also, what "push"?  I guess you are suggesting to "force" syslog-ng
> breaking syslog-ng-incubator?), but rather to remove the package it
> would be breaking, i.e. what's already happening automatically.
 My intention was to have syslog-ng in Buster even if FTP Masters
might need more time to process the syslog-ng-incubator removal.
You are right, it would have been a force and not a simple push the
package to Buster. As it will happen automatically now, closing this
bug report.

Thanks anyway,
Laszlo/GCS

--- End Message ---
Reply to: