Package: security-tracker
Severity: important
The security tracker currently uses the JSON feeds as linked from
https://nvd.nist.gov/vuln/data-feeds. Those data feeds will be retired
on December, 15th 2023, so in a bit more then two months. After that
the information will be only available via
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
Hi Salvatore
On Thu, Sep 13, 2018 at 01:37:35PM +0200, Salvatore Bonaccorso wrote:
> On Wed, Sep 12, 2018 at 03:10:56PM +0200, Bastian Blank wrote:
> > As the problems caused by the state of this repo now causes user visible
> > outages, this needs to be fixed.
Please provide a pl
Hi Salvatore
On Thu, Sep 13, 2018 at 01:37:35PM +0200, Salvatore Bonaccorso wrote:
> Do you have any hints at us on what we could look at to faciliate/help
> more salsa maintainers?
Please try to fork that repo. Git will take a long time to resolve
deltas. This is due to Git not handling very
Package: security-tracker
Severity: critical
The security tracker git repository is in a state which git does not
really like. git clone takes ages, fsck takes ages, repack is reported
to be impossible.
The GitLab on salsa.d.o also chokes on it some times during git
operations. Some may be
5 matches
Mail list logo
