Debian Bug report logs - #859123
automate import of DLAs and DSAs in www.debian.org

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupre <anarcat@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: automate import of DLAs and DSAs in www.debian.org

Date: Thu, 30 Mar 2017 10:28:05 -0400

Package: www.debian.org
Severity: normal

According to carnil in a discussion on the debian-lts@ mailing list,
DLAs and DSAs are manually imported in the website:

https://lists.debian.org/debian-lts/2017/03/msg00200.html

The process looks something like:

cd webwml/english/security
./parse-dla.pl $message
cvs add $year/dla-$nr.{wml,data}
cvs commit -m '[DLA $nr] $source security update'

where $message is the text of the DLA.

A similar script exists for DSAs, which is in parse-advisory.pl.

My question is: should this process be automated further? Is there a
way we could/should do this within the security team(s) directly?

I ask this because I wonder if we would have had the same problem with
the missing DLAs (in #859122) if the process would be automated.

Thanks!

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Message #15 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: 859123@bugs.debian.org

Cc: debian-lts@lists.debian.org

Subject: automating process for publishing DLAs on the website

Date: Mon, 19 Nov 2018 19:07:26 -0500

Hi!

Many of you probably already know this website and its precious RSS
feed:

https://www.debian.org/security/

Few of you might already know that DLAs are *supposed* to show up in
there as well, and did for a while. For example, here's a few DLAs in
2014:

https://www.debian.org/security/2014/

The process broke down a while back, and reasons don't matter. We need
to figure out how to fix this.

So I opened #859122 to import the missing DLAs and I've made good
progress.

But I've opened this bug report (#859123) to fix the process. So far,
the idea we had was to make LTS contributors submit a patch to the
website as part of the DLA publication process. You'd run the little
"parse-dla.pl" script which would create two files in the webwml git
repository, separate from the security tracker! that's where the
debian.org website lives.. Then you'd commit those and send a merge
request to the project (or just push if you have the rights). The
webmaster folks seemed to be open to grant us access to the repo to
remove friction as well..

How does that sound?

Another thing I thought we could do would be to hook that script into a
mailbox that would receive mail from the debian-lts-announce list and
automatically publish the results into git. But so far my efforts at
automating things on Debian infrastructure have mostly failed, so I'm
not sure it's the way to go. Besides, the parse-dsa.pl script isn't
exactly solid, and don't like the idea of parsing arbitrary input like
this without a human oversight. But it would certainly reduce friction
to a minimum, which I like.

Any other ideas?

Thanks!

A.
-- 
Only in the darkness can you see the stars.
                        - Martin Luther King, Jr.

Message #20 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Lev Lamberov <dogsleg@debian.org>

To: 859123@bugs.debian.org

Subject: Re: Bug#859123: automating process for publishing DLAs on the website

Date: Tue, 20 Nov 2018 11:30:45 +0500

Hi,

Пн 19 ноя 2018 @ 19:07 Antoine Beaupré <anarcat@debian.org>:

> Few of you might already know that DLAs are *supposed* to show up in
> there as well, and did for a while. For example, here's a few DLAs in
> 2014:
>
> https://www.debian.org/security/2014/
>
> The process broke down a while back, and reasons don't matter. We need
> to figure out how to fix this.
>
> So I opened #859122 to import the missing DLAs and I've made good
> progress.
>
> But I've opened this bug report (#859123) to fix the process. So far,
> the idea we had was to make LTS contributors submit a patch to the
> website as part of the DLA publication process. You'd run the little
> "parse-dla.pl" script which would create two files in the webwml git
> repository, separate from the security tracker! that's where the
> debian.org website lives.. Then you'd commit those and send a merge
> request to the project (or just push if you have the rights). The
> webmaster folks seemed to be open to grant us access to the repo to
> remove friction as well..
>
> How does that sound?
>
> Another thing I thought we could do would be to hook that script into a
> mailbox that would receive mail from the debian-lts-announce list and
> automatically publish the results into git. But so far my efforts at
> automating things on Debian infrastructure have mostly failed, so I'm
> not sure it's the way to go. Besides, the parse-dsa.pl script isn't
> exactly solid, and don't like the idea of parsing arbitrary input like
> this without a human oversight. But it would certainly reduce friction
> to a minimum, which I like.
>
> Any other ideas?

DSAs are also imported by hand with the help of "parse-advisory.pl",
there are always some folks in webwml or security team who can do this.
The difference between DSAs and DLAs is that the former is somewhat
standartized and can be parsed semi-automatically. It is not always the
case with the latter, that is the mentioned "parse-dla.pl" may just
throw an error because of some unusual markup or something. But let me
stress that even in case of DSAs parsing does not always performs well,
and adding a new DSA to the webwml requires checking it beforehand and
sometimes fixing html/wml tags.

I hope that LTS team _together_ with the Debian Security team will be
able to find a common concise markup format which will become a standard
both for DSAs and DLAs, and which could be easily and unambiguously
parsed, so automatic processing would be possible.

Regards,
Lev

Message #25 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: 859123@bugs.debian.org

Cc: debian-lts@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Tue, 20 Nov 2018 15:30:21 +0000

[Message part 1 (text/plain, inline)]

On Mon, Nov 19, 2018 at 07:07:26PM -0500, Antoine Beaupré wrote:
> The process broke down a while back, and reasons don't matter. We need
> to figure out how to fix this.
> 
> So I opened #859122 to import the missing DLAs and I've made good
> progress.
> 
> But I've opened this bug report (#859123) to fix the process. So far,
> the idea we had was to make LTS contributors submit a patch to the
> website as part of the DLA publication process. You'd run the little
> "parse-dla.pl" script which would create two files in the webwml git
> repository, separate from the security tracker! that's where the
> debian.org website lives.. Then you'd commit those and send a merge
> request to the project (or just push if you have the rights). The
> webmaster folks seemed to be open to grant us access to the repo to
> remove friction as well..
> 
> How does that sound?
 
sounds very good to me. thanks for your work on this so far!

> Another thing I thought we could do would be to hook that script into a
> mailbox that would receive mail from the debian-lts-announce list and
> automatically publish the results into git. But so far my efforts at
> automating things on Debian infrastructure have mostly failed, so I'm
> not sure it's the way to go. Besides, the parse-dsa.pl script isn't
> exactly solid, and don't like the idea of parsing arbitrary input like
> this without a human oversight. But it would certainly reduce friction
> to a minimum, which I like.

I better like your above proposal than generating data from parsing mails which
we have sent previously.

So I've just requested webwml access from the debian-www folks.


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Message #30 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: Holger Levsen <holger@layer-acht.org>, 859123@bugs.debian.org

Cc: debian-lts@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Tue, 11 Dec 2018 10:15:15 -0500

On 2018-11-20 15:30:21, Holger Levsen wrote:
> On Mon, Nov 19, 2018 at 07:07:26PM -0500, Antoine Beaupré wrote:
>> The process broke down a while back, and reasons don't matter. We need
>> to figure out how to fix this.
>> 
>> So I opened #859122 to import the missing DLAs and I've made good
>> progress.
>> 
>> But I've opened this bug report (#859123) to fix the process. So far,
>> the idea we had was to make LTS contributors submit a patch to the
>> website as part of the DLA publication process. You'd run the little
>> "parse-dla.pl" script which would create two files in the webwml git
>> repository, separate from the security tracker! that's where the
>> debian.org website lives.. Then you'd commit those and send a merge
>> request to the project (or just push if you have the rights). The
>> webmaster folks seemed to be open to grant us access to the repo to
>> remove friction as well..
>> 
>> How does that sound?
>  
> sounds very good to me. thanks for your work on this so far!

Right, agreed. :) I guess the script could both parse previous emails
and future ones quite easily.

The problem we have right now is we have no feedback from the www team
on the patches proposed in #859122 so I don't know if the formatting is
alright. Nor is it promising for the promptness with which the team can
respond to our constant flurry of such MRs in the future...

>> Another thing I thought we could do would be to hook that script into a
>> mailbox that would receive mail from the debian-lts-announce list and
>> automatically publish the results into git. But so far my efforts at
>> automating things on Debian infrastructure have mostly failed, so I'm
>> not sure it's the way to go. Besides, the parse-dsa.pl script isn't
>> exactly solid, and don't like the idea of parsing arbitrary input like
>> this without a human oversight. But it would certainly reduce friction
>> to a minimum, which I like.
>
> I better like your above proposal than generating data from parsing mails which
> we have sent previously.
>
> So I've just requested webwml access from the debian-www folks.

... where did you do that?

Considering that the patches I proposed now 3 weeks ago haven't been
merged, it seems it would be imperative for all LTS people to have
access to the www repository in our workflow. Or at least a significant
numebr of people. Otherwise we'll just be clogging their review queue
forever.

I've requested access as an individual, for what that's worth.

I've also got feedback from larjona on IRC, saying she didn't have time
to work on this yet, but ping'd the team to see if someone else
will. Otherwise she might be able to review our work in January.

I wonder if we could consider more automation here to remove the manual
push/pull process, because it seems it will be a significant source of
friction in our process in the future...

Anyways, hopefully we'll figure out a workflow soon enough. :)

A.

A.
-- 
Gods don't like people not doing much work. People who aren't busy all
the time might start to think.
                        - Terry Pratchett, Small Gods

Message #35 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Antoine Beaupré <anarcat@orangeseeds.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Wed, 19 Dec 2018 14:44:02 +0000

[Message part 1 (text/plain, inline)]

Hi Antoine,

On Tue, Dec 11, 2018 at 10:15:15AM -0500, Antoine Beaupré wrote:
> >> How does that sound?
> > sounds very good to me. thanks for your work on this so far!
> Right, agreed. :) I guess the script could both parse previous emails
> and future ones quite easily.
 
yup, that would be cool.

> The problem we have right now is we have no feedback from the www team
> on the patches proposed in #859122 so I don't know if the formatting is
> alright.

I've just asked on #debian-www to comment:

[15:37] <      h01ger> | it would be very nice if you could comment on
the patches proposed/linked in #859122 - those are
https://salsa.debian.org/webmaster-team/webwml/merge_requests/41 and 
https://salsa.debian.org/webmaster-team/webwml/merge_requests/42
and
https://salsa.debian.org/webmaster-team/webwml/merge_requests/43

I also note #859122 is not marked 'patch'.

> Nor is it promising for the promptness with which the team can
> respond to our constant flurry of such MRs in the future...

I'm not this pessimistic: first, (after a while) those patches should 
be pretty clear ones and they will know that. second, I do think that in
the long term we should just be able to directly push our DLAs on the
website, without a (human) proxy.

> > So I've just requested webwml access from the debian-www folks.
> ... where did you do that?

on salsa. I was also granted access 4 weeks ago it seems :)

> Considering that the patches I proposed now 3 weeks ago haven't been
> merged, it seems it would be imperative for all LTS people to have
> access to the www repository in our workflow. Or at least a significant
> numebr of people. Otherwise we'll just be clogging their review queue
> forever.

agreed. and as said (previously): for a start being i'm happy to act as a human
proxy...

> I've requested access as an individual, for what that's worth.

you were given access a week ago, too. \o/

> I've also got feedback from larjona on IRC, saying she didn't have time
> to work on this yet, but ping'd the team to see if someone else
> will. Otherwise she might be able to review our work in January.

that's almost like next week ;)

> I wonder if we could consider more automation here to remove the manual
> push/pull process, because it seems it will be a significant source of
> friction in our process in the future...

sure, more automation = better.

> Anyways, hopefully we'll figure out a workflow soon enough. :)

I'm confident we will, eventually. #859122 was filed >18 months ago, so
I don't think it's suddenly urgent, though I fully agree it would be
more than nice to have this fixed before the bug is two years old.


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Wed, 19 Dec 2018 09:52:19 -0500

On 2018-12-19 14:44:02, Holger Levsen wrote:
> Hi Antoine,
>
> On Tue, Dec 11, 2018 at 10:15:15AM -0500, Antoine Beaupré wrote:

[...]

> I also note #859122 is not marked 'patch'.

fixed.

[...]

>> I've requested access as an individual, for what that's worth.
>
> you were given access a week ago, too. \o/

yup. I guess I could just merge my own patches now... or do you want to
review them and do that instead, so we can get at least a second pair of
eyes on them?

then if all is good I could push a batch to complete the backlog and get
us started on an ongoing workflow...

>> I've also got feedback from larjona on IRC, saying she didn't have time
>> to work on this yet, but ping'd the team to see if someone else
>> will. Otherwise she might be able to review our work in January.
>
> that's almost like next week ;)

right, time flies!

>> I wonder if we could consider more automation here to remove the manual
>> push/pull process, because it seems it will be a significant source of
>> friction in our process in the future...
>
> sure, more automation = better.
>
>> Anyways, hopefully we'll figure out a workflow soon enough. :)
>
> I'm confident we will, eventually. #859122 was filed >18 months ago, so
> I don't think it's suddenly urgent, though I fully agree it would be
> more than nice to have this fixed before the bug is two years old.

yep. i'm not in a rush...

a.

-- 
One of the strongest motives that leads men to art and science is
escape from everyday life with its painful crudity and hopeless
dreariness. Such men make this cosmos and its construction the pivot
of their emotional life, in order to find the peace and security which
they cannot find in the narrow whirlpool of personal experience.
                       - Albert Einstein

Message #45 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Antoine Beaupré <anarcat@orangeseeds.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Wed, 19 Dec 2018 14:58:29 +0000

[Message part 1 (text/plain, inline)]

On Wed, Dec 19, 2018 at 09:52:19AM -0500, Antoine Beaupré wrote:
> > I also note #859122 is not marked 'patch'.
> fixed.
 
:)

> >> I've requested access as an individual, for what that's worth.
> > you were given access a week ago, too. \o/
> yup. I guess I could just merge my own patches now... or do you want to
> review them and do that instead, so we can get at least a second pair of
> eyes on them?
 
I just briefly reviewed them (not being a debian-www expert) and they
a.) looked good and b.) only affect our areas, so I do think you should
merge them.

> then if all is good I could push a batch to complete the backlog and get
> us started on an ongoing workflow...

yes!

thanks for following up on this!


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Message #50 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Wed, 19 Dec 2018 11:09:10 -0500

On 2018-12-19 14:58:29, Holger Levsen wrote:
> On Wed, Dec 19, 2018 at 09:52:19AM -0500, Antoine Beaupré wrote:
>> > I also note #859122 is not marked 'patch'.
>> fixed.
>  
> :)
>
>> >> I've requested access as an individual, for what that's worth.
>> > you were given access a week ago, too. \o/
>> yup. I guess I could just merge my own patches now... or do you want to
>> review them and do that instead, so we can get at least a second pair of
>> eyes on them?
>  
> I just briefly reviewed them (not being a debian-www expert) and they
> a.) looked good and b.) only affect our areas, so I do think you should
> merge them.

i merged both patches, but it doesn't look like the change showed up on
the main website yet:

https://www.debian.org/security/2018/

... doesn't list any DLA, and those are both 404s:

https://www.debian.org/security/2018/dla-1580
https://www.debian.org/security/2018/dla-1561

Any ideas?

A.

-- 
Twenty years from now you will be more disappointed by the things that
you didn't do than by the ones you did do. So throw off the bowlines.
Sail away from the safe harbor. Catch the trade winds in your sails.
Explore. Dream. Discover.  - Mark Twain

Message #55 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Wed, 19 Dec 2018 18:09:22 -0500

On 2018-12-19 18:05:36, Antoine Beaupré wrote:
> On 2018-12-19 11:09:10, Antoine Beaupré wrote:
>> On 2018-12-19 14:58:29, Holger Levsen wrote:
>>> On Wed, Dec 19, 2018 at 09:52:19AM -0500, Antoine Beaupré wrote:
>>>> > I also note #859122 is not marked 'patch'.
>>>> fixed.
>>>  
>>> :)
>>>
>>>> >> I've requested access as an individual, for what that's worth.
>>>> > you were given access a week ago, too. \o/
>>>> yup. I guess I could just merge my own patches now... or do you want to
>>>> review them and do that instead, so we can get at least a second pair of
>>>> eyes on them?
>>>  
>>> I just briefly reviewed them (not being a debian-www expert) and they
>>> a.) looked good and b.) only affect our areas, so I do think you should
>>> merge them.
>>
>> i merged both patches, but it doesn't look like the change showed up on
>> the main website yet:
>>
>> https://www.debian.org/security/2018/
>>
>> ... doesn't list any DLA, and those are both 404s:
>>
>> https://www.debian.org/security/2018/dla-1580
>> https://www.debian.org/security/2018/dla-1561
>
> This is actually processed every few hours, not directly after the CI
> runs.
>
> The DLAs are visible here:
>
> https://www-staging.debian.org/security/2018/dla-1580
>
> One thing that's unclear is how the entries get added to the main list
> in:
>
> https://www-staging.debian.org/security/2018/
>
> That still needs to be cleared up. In the meantime, I did do a mass
> import here:
>
> https://salsa.debian.org/webmaster-team/webwml/merge_requests/47

Sigh. I forgot to add that one issue that came up is duplicates: even
though the security tracker enforces unique DLA identifiers fairly well,
human error still creeps in and leads to duplicate DLA identifiers in
the wild. This will make automation harder: the current parser croaks
out on duplicate identifiers (and rightly so).

I guess we can just punt that back to the humans: they just need to
issue a new advisory with the correct identifier.

The problem is this is first come, first serve: if DLA X is claimed by
alice and bob comes in and publishes DLA X before alice has time to send
the mail, DLA X is on the website and can't be reverted by the script
and will need manual correction. I am worried this will be forgetten in
the future...

A.
-- 
The difference between a democracy and a dictatorship is that in a
democracy you vote first and take orders later; in a dictatorship you
don't have to waste your time voting.
                         - Charles Bukowski

Message #60 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org, 859122@bugs.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Wed, 19 Dec 2018 18:05:36 -0500

On 2018-12-19 11:09:10, Antoine Beaupré wrote:
> On 2018-12-19 14:58:29, Holger Levsen wrote:
>> On Wed, Dec 19, 2018 at 09:52:19AM -0500, Antoine Beaupré wrote:
>>> > I also note #859122 is not marked 'patch'.
>>> fixed.
>>  
>> :)
>>
>>> >> I've requested access as an individual, for what that's worth.
>>> > you were given access a week ago, too. \o/
>>> yup. I guess I could just merge my own patches now... or do you want to
>>> review them and do that instead, so we can get at least a second pair of
>>> eyes on them?
>>  
>> I just briefly reviewed them (not being a debian-www expert) and they
>> a.) looked good and b.) only affect our areas, so I do think you should
>> merge them.
>
> i merged both patches, but it doesn't look like the change showed up on
> the main website yet:
>
> https://www.debian.org/security/2018/
>
> ... doesn't list any DLA, and those are both 404s:
>
> https://www.debian.org/security/2018/dla-1580
> https://www.debian.org/security/2018/dla-1561

This is actually processed every few hours, not directly after the CI
runs.

The DLAs are visible here:

https://www-staging.debian.org/security/2018/dla-1580

One thing that's unclear is how the entries get added to the main list
in:

https://www-staging.debian.org/security/2018/

That still needs to be cleared up. In the meantime, I did do a mass
import here:

https://salsa.debian.org/webmaster-team/webwml/merge_requests/47

A.

-- 
Le péché est né avant la vertu, comme le moteur avant le frein.
                         - Jean-Paul Sartre

Message #65 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: 859123@bugs.debian.org

Cc: debian-lts@lists.debian.org, debian-www@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Fri, 01 Feb 2019 13:58:04 -0500

I'm looking at the update process for DLAs on the main website again. In
#859122, I've mentioned that I have, again, updated the MR to include
all DLAs up to DLA-1657-1. The www team folks tell me they will review
that this weekend.

But that mass-import process is kind of clunky: every time I need to
download the entire archive, extract it, parse every email, and add the
diff. It's slow and error prone and not automated, of course.

So I'm bringing back the topic of how we should automate this.

If I remember correctly, the current proposal is to add this as part of
the workflow for LTS developers: when you send the announcement on the
list, you also send a merge request on the website. This would get
reviewed and merged by another LTS developer with access to the webwml
repository:

https://salsa.debian.org/webmaster-team/webwml/project_members

At least me and Holger have those accesses for now, and I would suggest
people who do regular frontdesk work could make sure those MR are
reviewed and merged in a timely manner as well.

Would that work for everyone here?

If so, we can *already* start with that process, which would actually
look like this.

One time setup:

    git clone https://salsa.debian.org/webmaster-team/webwml
    cd webwml
    salsa fork

Each time there's a new DLA:

    ./bin/gen-DLA --save $CHANGES # correctly claim the DLA
    $EDITOR DLA-XXXX-Y # make sure the text is okay, like you normally
                       # do before the email gets sent
    mutt -H DLA-XXXX-Y # send the email
    cd ~/src/webwml/english/security
    git checkout -b DLA-XXXX-Y
    ./parse-dla.pl ~-/DLA-XXXX-Y
    git add 2019/DLA-XXX-Y*
    $EDITOR 2019/DLA-XXXX-Y* # make sure everything looks good
    git add 2019/DLA-XXX-Y*    
    git commit -m'DLA-XXXX-Y advisory'
    git push -u origin
    salsa mr

(Note: that "salsa" command is a new one shipped with devscripts. I only
read the manpage and didn't actually test that. :) Unfortunately, once
the MR is created, there's no magic command to merge it for
reviewers... Seems like this needs to be done through the web
interface.)

I'd be happy if someone sat down and actually tested that procedure.

The alternative, of course, is to setup "something" that would
automatically parse emails to debian-lts-announce@l.d.o but I suspect
that could be much more brittle than a manual operation like the above,
even if it means slightly more work.

Thank you for your attention.

A.

-- 
Hard times are coming when we will be wanting the voices of writers
who can see alternatives to how we live now and can see through our
fear-stricken society and its obsessive technologies to other ways of
being, and even imagine some real grounds for hope. We will need
writers who can remember freedom. Poets, visionaries—the realists of a
larger reality.         - Ursula Le Guin

Message #70 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Antoine Beaupré <anarcat@orangeseeds.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org, debian-www@lists.debian.org

Subject: Re: automating process for publishing DLAs on the website

Date: Fri, 1 Feb 2019 20:58:28 +0000

[Message part 1 (text/plain, inline)]

On Fri, Feb 01, 2019 at 01:58:04PM -0500, Antoine Beaupré wrote:
> I'm looking at the update process for DLAs on the main website again. 

\o/

> In
> #859122, I've mentioned that I have, again, updated the MR to include
> all DLAs up to DLA-1657-1. The www team folks tell me they will review
> that this weekend.

cool. (I'm offline right now but if this MR only has DLAs I'm tempted to
merge when back online...)

> But that mass-import process is kind of clunky: every time I need to
> download the entire archive, extract it, parse every email, and add the
> diff. It's slow and error prone and not automated, of course.
> 
> So I'm bringing back the topic of how we should automate this.

great!

> If I remember correctly, the current proposal is to add this as part of
> the workflow for LTS developers: when you send the announcement on the
> list, you also send a merge request on the website. This would get
> reviewed and merged by another LTS developer with access to the webwml
> repository:
> https://salsa.debian.org/webmaster-team/webwml/project_members

yes, thats the current plan to get this going.

> At least me and Holger have those accesses for now, and I would suggest
> people who do regular frontdesk work could make sure those MR are
> reviewed and merged in a timely manner as well.
> 
> Would that work for everyone here?

definitly for me (and for a start).

> If so, we can *already* start with that process, which would actually
> look like this.
> 
> One time setup:
> 
>     git clone https://salsa.debian.org/webmaster-team/webwml
>     cd webwml
>     salsa fork
> 
> Each time there's a new DLA:
> 
>     ./bin/gen-DLA --save $CHANGES # correctly claim the DLA
>     $EDITOR DLA-XXXX-Y # make sure the text is okay, like you normally
>                        # do before the email gets sent
>     mutt -H DLA-XXXX-Y # send the email
>     cd ~/src/webwml/english/security
>     git checkout -b DLA-XXXX-Y
>     ./parse-dla.pl ~-/DLA-XXXX-Y
>     git add 2019/DLA-XXX-Y*
>     $EDITOR 2019/DLA-XXXX-Y* # make sure everything looks good
>     git add 2019/DLA-XXX-Y*    
>     git commit -m'DLA-XXXX-Y advisory'
>     git push -u origin
>     salsa mr

can you please put that on wiki.d.o/LTS/Development?!

> (Note: that "salsa" command is a new one shipped with devscripts. I only
> read the manpage and didn't actually test that. :) Unfortunately, once
> the MR is created, there's no magic command to merge it for
> reviewers... Seems like this needs to be done through the web
> interface.)

hmm (I think there is a way to do this with a cli).

> I'd be happy if someone sat down and actually tested that procedure.
> 
> The alternative, of course, is to setup "something" that would
> automatically parse emails to debian-lts-announce@l.d.o but I suspect
> that could be much more brittle than a manual operation like the above,
> even if it means slightly more work.

yeah. "laters"!

> Thank you for your attention.

very much likewise!


-- 
tschüß,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Message #75 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org, debian-www@lists.debian.org

Subject: heads up: DLA should now be published on the website

Date: Mon, 18 Feb 2019 16:10:47 -0500

On 2019-02-01 20:58:28, Holger Levsen wrote:
> On Fri, Feb 01, 2019 at 01:58:04PM -0500, Antoine Beaupré wrote:

[...]

> can you please put that on wiki.d.o/LTS/Development?!

This is now done. I added a new section to the wiki

https://wiki.debian.org/LTS/Development#Publishing_updates_on_the_website

The TL;DR: is that you now need to clone the main website and issue a
merge request when you publish a DLA. Once you have a clone, it should
be as simple as:

    parse-dla.pl <EMAIL_TEMPLATE>
    git checkout -b DLA-XXXX-Y
    git add 2019
    git commit -m'DLA-XXX-Y'
    git push -u origin
    salsa mr

I've done one more mass import, hopefully the last:

https://salsa.debian.org/webmaster-team/webwml/merge_requests/58

But my little finger tells me there are many DLAs still missing from the
website. So even if/when the above MR does get merged, more entries will
be missing. So someone will need to make sure to run the check script to
make sure no entries are missing regularly, see also:

https://salsa.debian.org/webmaster-team/cron/merge_requests/1

Obviously, this workflow is not optimal and could be automated, see also
#859123 (in CC).

Thank you for your time.

A.

-- 
Omnis enim ex infirmitate feritas est.
All cruelty springs from weakness.
                         - Lucius Annaeus Seneca (58 AD)

Message #80 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Antoine Beaupré <anarcat@orangeseeds.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org, debian-www@lists.debian.org

Subject: Re: heads up: DLA should now be published on the website

Date: Tue, 19 Feb 2019 14:10:49 +0000

[Message part 1 (text/plain, inline)]

On Mon, Feb 18, 2019 at 04:10:47PM -0500, Antoine Beaupré wrote:
> > can you please put that on wiki.d.o/LTS/Development?!
> This is now done. I added a new section to the wiki

awesome, thank you!

> I've done one more mass import, hopefully the last:
> https://salsa.debian.org/webmaster-team/webwml/merge_requests/58

merged and pushed, thanks.

> But my little finger tells me there are many DLAs still missing from the
> website. So even if/when the above MR does get merged, more entries will
> be missing. So someone will need to make sure to run the check script to
> make sure no entries are missing regularly, see also:
> https://salsa.debian.org/webmaster-team/cron/merge_requests/1

I guess I will run this check script weekly (or maybe even daily) on
jenkins.debian.net.

> Obviously, this workflow is not optimal and could be automated, see also
> #859123 (in CC).

we'll get there eventually.

> Thank you for your time.

very much likewise!


-- 
tschau,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

In Europe there are people prosecuted by courts because they saved other people
from drowning in the  Mediterranean Sea.  That is almost as absurd  as if there
were people being prosecuted because they save humans from drowning in the sea.

[signature.asc (application/pgp-signature, inline)]

Message #85 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Antoine Beaupré <anarcat@orangeseeds.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org, debian-www@lists.debian.org

Subject: Re: heads up: DLA should now be published on the website

Date: Thu, 21 Feb 2019 18:18:06 +0000

[Message part 1 (text/plain, inline)]

Hi Antoine,

On Mon, Feb 18, 2019 at 04:10:47PM -0500, Antoine Beaupré wrote:
> But my little finger tells me there are many DLAs still missing from the
> website. So even if/when the above MR does get merged, more entries will
> be missing. So someone will need to make sure to run the check script to
> make sure no entries are missing regularly, see also:
> https://salsa.debian.org/webmaster-team/cron/merge_requests/1

I've looked at this script now, it works nicely, just our results are
not so good yet:

~/Projects/debian-www/webwml$ ../cron/parts/10-check-advisories 2>&1 |wc -l
314
~/Projects/debian-www/webwml$ ../cron/parts/10-check-advisories --mode DLA 2>&1 |wc -l
1762
~/Projects/debian-www/webwml$ ../cron/parts/10-check-advisories --mode DLA 2>&1 | head -10
ERROR: .data or .wml file missing for DLA 1685-1
ERROR: .data or .wml file missing for DLA 1684-1
ERROR: .data or .wml file missing for DLA 1683-1
ERROR: .data or .wml file missing for DLA 1660-2
ERROR: .data or .wml file missing for DLA 1682-1
ERROR: .data or .wml file missing for DLA 1681-1
ERROR: .data or .wml file missing for DLA 1680-1
ERROR: .data or .wml file missing for DLA 1679-1
ERROR: .data or .wml file missing for DLA 1678-1
ERROR: .data or .wml file missing for DLA 1677-1
debian-work:~/Projects/debian-www/webwml$ 

-> this script is incorrect/broken for DLAs it seems, as 
https://www.debian.org/lts/security/ does list the DLAs 1677-1681,
just DLAs 1682-1685 are missing. And they are called DLA-1234 there,
not "DLA 1234-1"...

Also, if this merge request would be merged, it would just run it in
normal, DSA, mode. Do you have a suggestion how to run it in DLA mode?


-- 
tschau,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Message #90 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org, debian-www@lists.debian.org

Subject: Re: heads up: DLA should now be published on the website

Date: Thu, 21 Feb 2019 13:51:07 -0500

On 2019-02-21 18:18:06, Holger Levsen wrote:
> Hi Antoine,
>
> On Mon, Feb 18, 2019 at 04:10:47PM -0500, Antoine Beaupré wrote:
>> But my little finger tells me there are many DLAs still missing from the
>> website. So even if/when the above MR does get merged, more entries will
>> be missing. So someone will need to make sure to run the check script to
>> make sure no entries are missing regularly, see also:
>> https://salsa.debian.org/webmaster-team/cron/merge_requests/1
>
> I've looked at this script now, it works nicely, just our results are
> not so good yet:
>
> ~/Projects/debian-www/webwml$ ../cron/parts/10-check-advisories 2>&1 |wc -l
> 314
> ~/Projects/debian-www/webwml$ ../cron/parts/10-check-advisories --mode DLA 2>&1 |wc -l
> 1762
> ~/Projects/debian-www/webwml$ ../cron/parts/10-check-advisories --mode DLA 2>&1 | head -10
> ERROR: .data or .wml file missing for DLA 1685-1
> ERROR: .data or .wml file missing for DLA 1684-1
> ERROR: .data or .wml file missing for DLA 1683-1
> ERROR: .data or .wml file missing for DLA 1660-2
> ERROR: .data or .wml file missing for DLA 1682-1
> ERROR: .data or .wml file missing for DLA 1681-1
> ERROR: .data or .wml file missing for DLA 1680-1
> ERROR: .data or .wml file missing for DLA 1679-1
> ERROR: .data or .wml file missing for DLA 1678-1
> ERROR: .data or .wml file missing for DLA 1677-1
> debian-work:~/Projects/debian-www/webwml$ 
>
> -> this script is incorrect/broken for DLAs it seems, as 
> https://www.debian.org/lts/security/ does list the DLAs 1677-1681,
> just DLAs 1682-1685 are missing. And they are called DLA-1234 there,
> not "DLA 1234-1"...

Weird. Is your local checkout up to date? What if you run in debug mode?

> Also, if this merge request would be merged, it would just run it in
> normal, DSA, mode. Do you have a suggestion how to run it in DLA mode?

We could simply change the default here:

    parser.add_argument('--mode', default='DSA', choices=('DSA', 'DLA'),
                        help='which sort of advisory to check (default: %(default)s)')  # noqa: E501

a.
-- 
If you have come here to help me, you are wasting our time.
But if you have come because your liberation is bound up with mine, then
let us work together.    - Aboriginal activists group, Queensland, 1970s

Message #95 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Antoine Beaupré <anarcat@orangeseeds.org>

Cc: 859123@bugs.debian.org, debian-lts@lists.debian.org, debian-www@lists.debian.org

Subject: Re: heads up: DLA should now be published on the website

Date: Thu, 21 Feb 2019 19:40:15 +0000

[Message part 1 (text/plain, inline)]

On Thu, Feb 21, 2019 at 01:51:07PM -0500, Antoine Beaupré wrote:
> > -> this script is incorrect/broken for DLAs it seems, as 
> > https://www.debian.org/lts/security/ does list the DLAs 1677-1681,
> > just DLAs 1682-1685 are missing. And they are called DLA-1234 there,
> > not "DLA 1234-1"...
> Weird. Is your local checkout up to date?

yes

> What if you run in debug mode?

~/Projects/debian-www/cron$ ../cron/parts/10-check-advisories --mode DLA --debug 2>&1 | head -50
INFO: fetching URL https://salsa.debian.org/security-tracker-team/security-tracker/raw/master/data/DLA/list
DEBUG: Starting new HTTPS connection (1): salsa.debian.org
DEBUG: https://salsa.debian.org:443 "GET /security-tracker-team/security-tracker/raw/master/data/DLA/list HTTP/1.1" 200 47253
INFO: checking DLA-1685-1 (2019)
ERROR: .data or .wml file missing for DLA 1685-1
DEBUG: skipping line: "	{CVE-2019-6338}"
DEBUG: skipping line: "	[jessie] - drupal7 7.32-1+deb8u15"
INFO: checking DLA-1684-1 (2019)
ERROR: .data or .wml file missing for DLA 1684-1
DEBUG: skipping line: "	{CVE-2019-6454}"
DEBUG: skipping line: "	[jessie] - systemd 215-17+deb8u10"
INFO: checking DLA-1683-1 (2019)
ERROR: .data or .wml file missing for DLA 1683-1
DEBUG: skipping line: "	{CVE-2018-8791 CVE-2018-8792 CVE-2018-8793 CVE-2018-8794 CVE-2018-8795 CVE-2018-8796 CVE-2018-8797 CVE-2018-8798 CVE-2018-8799 CVE-2018-8800 CVE-2018-20174 CVE-2018-20175 CVE-2018-20176 CVE-2018-20177 CVE-2018-20178 CVE-2018-20179 CVE-2018-20180 CVE-2018-20181 CVE-2018-20182}"
DEBUG: skipping line: "	[jessie] - rdesktop 1.8.4-0+deb8u1"
INFO: checking DLA-1660-2 (2019)
ERROR: .data or .wml file missing for DLA 1660-2
DEBUG: skipping line: "	[jessie] - rssh 2.3.4-4+deb8u3"
INFO: checking DLA-1682-1 (2019)
ERROR: .data or .wml file missing for DLA 1682-1
DEBUG: skipping line: "	{CVE-2018-20721}"
DEBUG: skipping line: "	[jessie] - uriparser 0.8.0.1-2+deb8u2"
INFO: checking DLA-1681-1 (2019)
ERROR: .data or .wml file missing for DLA 1681-1
DEBUG: skipping line: "	{CVE-2019-7659}"
DEBUG: skipping line: "	[jessie] - gsoap 2.8.17-1+deb8u2"
INFO: checking DLA-1680-1 (2019)
ERROR: .data or .wml file missing for DLA 1680-1
DEBUG: skipping line: "	{CVE-2018-17000 CVE-2018-19210 CVE-2019-7663}"
DEBUG: skipping line: "	[jessie] - tiff 4.0.3-12.3+deb8u8"
INFO: checking DLA-1679-1 (2019)
ERROR: .data or .wml file missing for DLA 1679-1
DEBUG: skipping line: "	[jessie] - php5 5.6.40+dfsg-0+deb8u1"
INFO: checking DLA-1678-1 (2019)
ERROR: .data or .wml file missing for DLA 1678-1
DEBUG: skipping line: "	{CVE-2018-18356 CVE-2018-18500 CVE-2018-18501 CVE-2018-18505 CVE-2018-18509 CVE-2019-5785}"
DEBUG: skipping line: "	[jessie] - thunderbird 1:60.5.1-1~deb8u1"
INFO: checking DLA-1677-1 (2019)
ERROR: .data or .wml file missing for DLA 1677-1
DEBUG: skipping line: "	{CVE-2018-18356 CVE-2019-5785}"
DEBUG: skipping line: "	[jessie] - firefox-esr 60.5.1esr-1~deb8u1"
INFO: checking DLA-1676-1 (2019)
ERROR: .data or .wml file missing for DLA 1676-1
DEBUG: skipping line: "	{CVE-2017-15105}"
DEBUG: skipping line: "	[jessie] - unbound 1.4.22-3+deb8u4"
INFO: checking DLA-1675-1 (2019)
ERROR: .data or .wml file missing for DLA 1675-1
DEBUG: skipping line: "	{CVE-2019-6690}"
DEBUG: skipping line: "	[jessie] - python-gnupg 0.3.6-1+deb8u1"
INFO: checking DLA-1674-1 (2019)

> > Also, if this merge request would be merged, it would just run it in
> > normal, DSA, mode. Do you have a suggestion how to run it in DLA mode?
> We could simply change the default here:
> 
>     parser.add_argument('--mode', default='DSA', choices=('DSA', 'DLA'),
>                         help='which sort of advisory to check (default: %(default)s)')  # noqa: E501

hmm. (and then, what about missing DSAs?)


-- 
tschau,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Message #98 received at 859123@bugs.debian.org (full text, mbox, reply):

From: "Pr.Tupirani" <revolucao005@2070.live>

To: 859123@bugs.debian.org

Subject: ==Библии да! Конституции нет! / Bible Yes, Constitution No.12-32-18

Date: 12 Mar 2019 12:32:20 -0300

[Message part 1 (text/plain, inline)]

<html><body><B id=docs-internal-guid-193bee4e-7fff-a65c-4db2-ade5bee40a8c style="FONT-WEIGHT: normal">
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 24pt; TEXT-DECORATION: none; FONT-FAMILY: Cambria; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">ПОКОЛЕНИЕ ИИСУСА ХРИСТА</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 15pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 18pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">ПОКОЛЕНИЕ МУЧЕНИЦА</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.5pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">учить умирать</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.5pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">за Иисуса Христа</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P><BR>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">ЭТО МИНИСТЕРСТВО ГОЛОСА ВОССТАНОВЛЕНИЯ, ТОЛЬКО ДВЕРЬ ДЛЯ РАПТУРЫ ЦЕРКВИ:</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><A style="TEXT-DECORATION: none" href="http://bit.ly/thelastelijah-ru"><SPAN style="FONT-SIZE: 12pt; TEXT-DECORATION: underline; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #1155cc; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none">http://bit.ly/thelastelijah-ru</SPAN></A></P><BR><BR><BR>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">PR. ТУПИРАНИ, ПОСЛЕДНИЙ ЭЛИЯ.</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">БИБЛИЯ ДА! КОНСТИТУЦИЯ НЕ!</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">2070: ИИСУС ВОЗВРАЩАЕТСЯ.</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">МЫ НЕ МАСОНОВ!</SPAN></P><BR><BR><BR>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 10pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">“Вот, Я пошлю к вам Илию пророка пред наступлением дня Господня, великого и страшного." (Малахия 4:5)</SPAN></P><BR>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 10pt; TEXT-DECORATION: none; FONT-FAMILY: Arial; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">“Иисус сказал им в ответ: правда, Илия должен придти прежде и устроить всё;" (Матфея 17:11)</SPAN></P><BR><BR><BR><BR><BR>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 24pt; TEXT-DECORATION: none; FONT-FAMILY: Algerian; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">GENERATION JESUS CHRIST</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 15pt; TEXT-DECORATION: none; FONT-FAMILY: Algerian; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 700; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 18pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">GENERATION OF MARTYRS</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.5pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">TEACHING TO DIE</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.5pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">FOR JESUS CHRIST.</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">This is the ministry of the voice of restoration, the unique door for the rapture of the church:</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><A style="TEXT-DECORATION: none" href="http://restauracao.net/home.html"><SPAN style="FONT-SIZE: 12pt; TEXT-DECORATION: underline; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #1155cc; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none">http://restauracao.net/home.html</SPAN></A></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">Pr. Tupirani, the last Elijah.</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">Bible Yes! Constitution No!</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">2070: Jesus will return.</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 13.999pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #222222; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">We aren't freemasons!</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 12pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 12pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 12pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 12pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN>&nbsp;</P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 10pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff">“Behold, I will send you Elijah the prophet before the coming of the great and dreadful day of the Lord." (Malachi 4:5)</SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 10pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: #ffffff"></SPAN></P>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-TOP: 0pt; TEXT-ALIGN: center; LINE-HEIGHT: 1.38" dir=ltr><SPAN style="FONT-SIZE: 10pt; TEXT-DECORATION: none; FONT-FAMILY: 'Times New Roman'; FONT-VARIANT: normal; VERTICAL-ALIGN: baseline; WHITE-SPACE: pre-wrap; FONT-WEIGHT: 400; COLOR: #000000; FONT-STYLE: normal; BACKGROUND-COLOR: transparent">“Elijah truly shall first come and restore all things." (Matthew 17:11)</SPAN></P></B><BR class=Apple-interchange-newline></body></html>

[Message part 2 (text/plain, inline)]

ПОКОЛЕНИЕ ИИСУСА ХРИСТА

ПОКОЛЕНИЕ МУЧЕНИЦА
учить умирать
за Иисуса Христа

ЭТО МИНИСТЕРСТВО ГОЛОСА ВОССТАНОВЛЕНИЯ, ТОЛЬКО ДВЕРЬ ДЛЯ РАПТУРЫ ЦЕРКВИ:
http://bit.ly/thelastelijah-ru
PR. ТУПИРАНИ, ПОСЛЕДНИЙ ЭЛИЯ.
БИБЛИЯ ДА! КОНСТИТУЦИЯ НЕ!
2070: ИИСУС ВОЗВРАЩАЕТСЯ.
МЫ НЕ МАСОНОВ!
“Вот, Я пошлю к вам Илию пророка пред наступлением дня Господня, великого и страшного." (Малахия 4:5)
“Иисус сказал им в ответ: правда, Илия должен придти прежде и устроить всё;" (Матфея 17:11)
GENERATION JESUS CHRIST

GENERATION OF MARTYRS
TEACHING TO DIE
FOR JESUS CHRIST.



This is the ministry of the voice of restoration, the unique door for the rapture of the church:
http://restauracao.net/home.html


Pr. Tupirani, the last Elijah.
Bible Yes! Constitution No!
2070: Jesus will return.
We aren't freemasons!

                                                 

 
“Behold, I will send you Elijah the prophet before the coming of the great and dreadful day of the Lord." (Malachi 4:5)

“Elijah truly shall first come and restore all things." (Matthew 17:11)

[Message part 3 (text/html, inline)]

Message #103 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Thomas Lange <lange@cs.uni-koeln.de>

To: 859123@bugs.debian.org, 859123-submitter@bugs.debian.org

Subject: new DAS list

Date: Mon, 2 Oct 2023 23:17:29 +0200

We now have an automatically generated list of DSA, which does not need
any manual adding the infos. See
https://www.debian.org/security/dsa.html#DSAS

This list also links to the security tracker and the security
announcement mail.

My plan is to remove the need of manual editing wml and data files for
every DSA/DLA.

regards Thomas

Message #111 received at 859123@bugs.debian.org (full text, mbox, reply):

From: Jean-Pierre Giraud <jenapierregiraud75@free.fr>

To: Thomas Lange <lange@cs.uni-koeln.de>, 859123@bugs.debian.org, 859123-submitter@bugs.debian.org

Subject: Re: Bug#859123: new DAS list

Date: Tue, 03 Oct 2023 01:00:31 +0200

[Message part 1 (text/plain, inline)]

Hi,
Le lundi 02 octobre 2023 à 23:17 +0200, Thomas Lange a écrit :
> We now have an automatically generated list of DSA, which does not
> need
> any manual adding the infos. See
> https://www.debian.org/security/dsa.html#DSAS
> 
> This list also links to the security tracker and the security
> announcement mail.
> 
> My plan is to remove the need of manual editing wml and data files for
> every DSA/DLA.
> 
> regards Thomas
> 
I am translating the new dsa.html into French. Thanks for the work you
done, but I don't found any link to the .wml files in security/202*/.
It's the link that allows access to the DSA translated into French (in
.wml format): the translated files are not linked to debian-security-
announce/2023/msg but to security/202*/. I see also that you plan to
remove "the need of manual editing wml". I consider that impossibility
of accessing to translated DSAs would be a regression.

Regards,
Jean-Pierre Giraud - jipege
Member of the debian-l10n-french

[signature.asc (application/pgp-signature, inline)]

Message #119 received at 859123-done@bugs.debian.org (full text, mbox, reply):

From: Thomas Lange <lange@cs.uni-koeln.de>

To: 859123-done@bugs.debian.org

Subject: closing

Date: Tue, 26 Dec 2023 19:13:24 +0100

I have removed the old security and lts/security
web pages which need manual editing a page for every new security
advisory.

All DSA and DLA are now automatically added to the web pages.

Therefore we can close this bug.

-- 
regards Thomas

Send a report that this bug log contains spam.