Hi,
For the records, security/vuxml/vuln/2026.xml has reached the 1048576
limit size,
requiring the use of --push-option=i-know-this-file-is-big flag to
commit it.
And we still have 3 months left before 2027.
Regards
-- rodrigo
I think we should split the files once they reach certain level of entries (not size).
2024.xml
2025.xml
2026.00.xml
2026.xml
2027.00.xml
2027.01.xml
2027.xml
the year without the prefix still the current one before it get rotated. With amount of new software and audits, i expect this to rotate few time per year.
Regards
Abdelkader
On Sat, 26 Sep 2026, at 11:13, Rodrigo Osorio wrote:
Hi,
For the records, security/vuxml/vuln/2026.xml has reached the 1048576 limit size,
requiring the use of --push-option=i-know-this-file-is-big flag to
commit it.
And we still have 3 months left before 2027.
Regards
-- rodrigo
I think we should split the files once they reach certain level of entries (not size).
2024.xml
2025.xml
2026.00.xml
2026.xml
2027.00.xml
2027.01.xml
2027.xml
the year without the prefix still the current one before it get rotated. With amount of new software and audits, i expect this to rotate few time per year.
On Sep 26, 2026, at 1:35rC>PM, Jamie Landeg-Jones <jamie@catflap.org> wrote:
"Abdelkader Boudih" <seuros@FreeBSD.org> wrote:
I think we should split the files once they reach certain level of entries (not size).
2024.xml
2025.xml
2026.00.xml
2026.xml
2027.00.xml
2027.01.xml
2027.xml
the year without the prefix still the current one before it get rotated. With amount of new software and audits, i expect this to rotate few time per year.
I don't like rotating file names for anything but log files. If
you're going to split the files anyway, why not go with constant
forms such as 2026Q1...2026Q4 or YYYY-MM?
If you're worried about compatibility with users scripts, you could make 2026.xml a link or copy of the latest one - that would achieve the same
level of compatibility as your suggestion.
And as user scripts that want to access more than just the latest entries will need to be modified anyway, it will be much easier to change the
scripts filename format, than trying to chase "sliding filenames'
Cheers, Jamie
A bit aside,
I would honestly prefer if each port had its own vuln.xml file and we build the central file
by means of "find ${PORTSDIR} -name vuln.xml -depth 2". This would avoid the size issue
and entirely remove the crazy annoying merge conflicts I get basically every time I have to
add a vuxml entry.
Yours,
Robert Clausecker
On Sat, Sep 26, 2026 at 11:30:20AM +0000, Abdelkader Boudih wrote:
I think we should split the files once they reach certain level of entries (not size).
2024.xml
2025.xml
2026.00.xml
2026.xml
2027.00.xml
2027.01.xml
2027.xml
the year without the prefix still the current one before it get rotated. With amount of new software and audits, i expect this to rotate few time per year.
Regards
Abdelkader
On Sat, 26 Sep 2026, at 11:13, Rodrigo Osorio wrote:
Hi,
For the records, security/vuxml/vuln/2026.xml has reached the 1048576 limit size,
requiring the use of --push-option=i-know-this-file-is-big flag to commit it.
And we still have 3 months left before 2027.
Regards
-- rodrigo
--
() ascii ribbon campaign - for an encoding-agnostic world
/\ - against html email - against proprietary attachments
Putting things in perspective, 2TB WD Black drive with ZFS currently returns from running `time find /usr/ports -name Makefile -depth 2` on my system (currently under Firefox memory pressure) after first run, next run within minutes of the first, and 3rd run immediately when 2nd run completes:435.76 real-a 1.04 user-a 9.01 sys
Sometimes I will copy data from and back to disk to get ZFS to write it more optimally or do other practices that cause more organized structure to be written as it gets bad with ZFS fragmentation over time as git does scattered write/modify/delete throughout the tree.`zfs rewrite -P` might be helpful for you: https://openzfs.github.io/openzfs-docs/man/master/8/zfs-rewrite.8.html
"Edward Sanford Sutton, III" <mirror176@hotmail.com> wrote:I forget about that one which is a side effect of using
though you would also want to prune distfiles and anything with a path
starting with a capital letter to make the run less wasteful.
In that same thought I always wonder why distfiles isn't capitalized
like the other non-port containing folders.
That would make things easier! Don't forget "packages" too!
Hi,limit
=20
For the records,=A0security/vuxml/vuln/2026.xml has reached the=A01048576=
size,it
requiring the use of --push-option=3Di-know-this-file-is-big flag to comm=
it.
And we still have 3 months left before 2027.
A bit aside,
I would honestly prefer if each port had its own vuln.xml file and we
build the central file by means of "find ${PORTSDIR} -name vuln.xml
-depth 2". This would avoid the size issue and entirely remove the
crazy annoying merge conflicts I get basically every time I have to
add a vuxml entry.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 60:34:32 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,219 |