Bug#908678: Update on the security-tracker git discussion
- To: 908678@bugs.debian.org
- Subject: Bug#908678: Update on the security-tracker git discussion
- From: Sylvain Beucler <beuc@beuc.net>
- Date: Fri, 2 Oct 2020 22:04:32 +0200
- Message-id: <[🔎] c30b77e8-a963-4744-ada8-dd5245cef27b@beuc.net>
- Reply-to: Sylvain Beucler <beuc@beuc.net>, 908678@bugs.debian.org
- In-reply-to: <20190806062842.GA14466@lorien.valinor.li>
- References: <20190606161153.GA29381@eldamar.local> <20190608162924.GA8204@eldamar.local> <20180912131055.srfkzw5nefmcoqnh@shell.thinkmo.de> <20190609114858.GA2416@eldamar.local> <20190624115736.7o75qsquhuw66oj5@lorien.valinor.li> <20180912131055.srfkzw5nefmcoqnh@shell.thinkmo.de> <20190702112543.GA21081@lorien.valinor.li> <20190702113810.taiplg3voq225vnq@inutil.org> <20180912131055.srfkzw5nefmcoqnh@shell.thinkmo.de> <20190806060511.zy5d7o4d52rmqkii@shell.thinkmo.de> <20190806062842.GA14466@lorien.valinor.li> <20190806062842.GA14466@lorien.valinor.li> <20180912131055.srfkzw5nefmcoqnh@shell.thinkmo.de>
Hi,
On Tue, 6 Aug 2019 08:28:43 +0200 Salvatore Bonaccorso wrote:
> Thanks for keeping track and following up.
>
> On Tue, Aug 06, 2019 at 08:05:11AM +0200, Bastian Blank wrote:
> > Moin
> >
> > On Tue, Jul 02, 2019 at 01:38:10PM +0200, Moritz Muehlenhoff wrote:
> > > On Tue, Jul 02, 2019 at 01:25:43PM +0200, Salvatore Bonaccorso wrote:
> > > > p.s.: Question is if we should do a split as well for the other types of
> > > > files which are supported (DSA, TDSA, ...) while at it.
> > > We can axe out DTSA/* while we're at it.
> > > For DSA/list (and DLA/list) we can initially keep it as a single file, it can
> > > still be split later on if necessary.
> >
> > Following up to
> >
> > | Please provide a plan how and when to fix this before 2019-06-30.
> >
> > We have now one month later. Please provide the plan.
>
> The items in
> https://salsa.debian.org/security-tracker-team/security-tracker-service/issues/1
> needs further detailed and then sorted/prioritized. Later actual
> implementation work on making the split possible on tracker and other
> tooling side needs to happen. We cannot depend on a non-functional
> instance for the day to day work, so all of the above basically will
> need to be ported in some sensible way.
>
> Progress is slow due to other time limitations in day to day tasks.
>
> Still if it is going to be too much burden for salsa admin and needs
> to be fast, then I only see that we temporarily switch away from salsa
> to gitlab or another hosting (github will not work) and then move back
> once the split has finally happened.
It seems a bit difficult to make a big switch, probably because it's not
easy to know and test all the various involved scripts.
Considering a more progressive approach, is there something preventing
us from switching to the rewritten repository and split/merging the
file, something like:
diff --git a/conf/post-merge b/conf/post-merge
new file mode 100755
index 0000000000..a9991c1cc9
--- /dev/null
+++ b/conf/post-merge
@@ -0,0 +1,3 @@
+#!/bin/sh
+echo "post-merge"
+[ -f data/CVE/1999.list ] && cat data/CVE/*.list > data/CVE/list
diff --git a/conf/pre-commit b/conf/pre-commit
index 767e478e36..12e781e97d 100755
--- a/conf/pre-commit
+++ b/conf/pre-commit
@@ -5,3 +5,4 @@ set -e
exec 1>&2
make check-syntax
+bin/split-by-year.py
?
Cheers!
Sylvain
Reply to: