Fabian Keil wrote on 2023-08-02 at 08:28:20:
> Mattia Rizzolo wrote on 2023-08-01 at 11:38:19:
>
> > On Tue, Aug 01, 2023 at 08:32:33AM +0200, Fabian Keil wrote:
> > > As usual there will be a Privoxy and ElectroBSD booth
> > > at FrOSCon [0] next weekend.
> >
> > Yeah, I suspect it's way too
On 2023-10-12, Marek Marczykowski-Górecki wrote:
> On Sat, Sep 30, 2023 at 04:59:33PM -0700, Vagrant Cascadian wrote:
>> On 2023-09-20, Lucas Nussbaum wrote:
>> > On 19/09/23 at 13:52 -0700, Vagrant Cascadian wrote:
>> >> Snapshotting the archive(s) multiple times per day, today, tomorrow, and
>> >
On 2023-10-12, Vagrant Cascadian wrote:
> On 2023-10-12, Chris Lamb wrote:
>>> In the meantime, I worked on a naive implementation of this, using
>>> debmirror and btrfs snapshots (zfs or xfs are other likely candidates
>>> for filesystem-level snapshots). It is working better than I expected!
>> [
On Sat, Sep 30, 2023 at 04:59:33PM -0700, Vagrant Cascadian wrote:
> On 2023-09-20, Lucas Nussbaum wrote:
> > On 19/09/23 at 13:52 -0700, Vagrant Cascadian wrote:
> >> * Looking forward and backwards at snapshots
> >>
> >> I do think that a more complete snapshot approach is probably better
> >> t
On 2023-10-12, Chris Lamb wrote:
>> In the meantime, I worked on a naive implementation of this, using
>> debmirror and btrfs snapshots (zfs or xfs are other likely candidates
>> for filesystem-level snapshots). It is working better than I expected!
> […]
>> Currently weighing in at about 550GB, ea
Dear Vagrant,
> In the meantime, I worked on a naive implementation of this, using
> debmirror and btrfs snapshots (zfs or xfs are other likely candidates
> for filesystem-level snapshots). It is working better than I expected!
[…]
> Currently weighing in at about 550GB, each snapshot of the archi
Chris Lamb wrote:
> Please review the draft for September's Reproducible Builds report:
This has now been published — thanks to all who contributed.
If possible, please share the following link:
https://reproducible-builds.org/reports/2023-09/
.. and also consider re-tweeting:
https://twi
