Re: More 5 november in the release schedule

[Adrian Bunk <bunk@stusta.de>]

On Tue, Nov 08, 2016 at 02:31:04AM -0500, Scott Kitterman wrote:
> On Tuesday, November 08, 2016 06:19:36 PM Brian May wrote:
> > Christian Seiler <christian@iwakd.de> writes:
> > > Why? Any package currently in testing still has time to enter
> > > (until roughly end of this year), so it's not like there is no
> > > heads-up for people. And RC bugs don't lead to immediate
> > > removal from testing, you still have quite a bit of time until
> > > they actually cause removal of a package.
> > 
> > The problem is if the maintainer is not responding to RC bug reports,
> > and you don't realize a package you depend on has RC bugs. This happened
> > several times to me during the last freeze.
> 
> I seem to get email when a package I maintain is marked for autoremoval 
> (regardless of whether it is an issue with my package or an rdepend).  That 
> and it showing up on your DDPO Packages overview ought to be enough to be 
> forewarned, I would have thought.

For dependencies that is correct.

But there is currently no kind of notification in place if a 
build-dependency of your package is scheduled for autoremoval.

When a build dependency of your package is actually removed from 
testing, you are also not getting any notification.

If your build dependency gets removed from testing on Christmas Day
or later, your package will anyway not be in stretch.

Even after the removal this is not visible to the maintainer.
Example: https://tracker.debian.org/pkg/gnome-do-plugins
The build dependency banshee is not in testing.

> Scott K

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed