Re: More 5 november in the release schedule
On 11/08/2016 08:47 PM, Adrian Bunk wrote:
> 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.
Then this just means that autoremovals should not only take
into account dependencies but also build dependencies,
because then the maintainer would be notified of that fact.
Regards,
Christian
Reply to: