No, this is not a proper fix, since the ref-table.inc is need two
times. In security and lts/security for two version of
crossrefenreces.
I've now manually delete the wrong, empty ref-table.inc on the www
master and I will check if it get generated properly.
Still we have to check, why it is not
> This reminded me about
> https://lists.debian.org/debian-project/2018/12/msg00025.html
For easier understanding, this is the post from Daniel with subject:
"€ 500 cash bounty for information / Debian privacy breaches"
--
regards Thomas
> thanks for wrinting it down, but I still think the better option is
> to spend some Debian funds to let a professional mediator handle
> this,
Great idea! IMO it should be very easy for the AH team or any DD to
ask the DPL for getting money for an external mediator if a situation
is escalating
Thanks for this details analysis and for your suggestions for
improvements. I like especially the idea of changing the timeline and
to remove the update of the DAM statement (3. Appealer statement).
I also was wondering what "turning it into a warning" really means.
I think a warning should be done
>>>>> On Tue, 08 Jan 2019 09:14:53 +0100, Joerg Jaspert
>>>>> said:
> On 15276 March 1977, Thomas Lange wrote:
>> I think you should forward this mail to nm-commit...@nm.debian.org.
> Noted, but I think it makes more sense to point them at
5 matches
Mail list logo
