| Centurion_Dan | KatolaZ: parazyd: I've been looking at the mirror script and I'm wondering why it seems to require such huge updates, like ~500MB minimum for each re-sync even if a re-sync is started immediately on completion of the last one. That seems to me to be excessive... are we unneccesarily regenerating Package Files in Amprolla?? | 07:35 |
|---|---|---|
| KatolaZ | Centurion_Dan: sure we are, but only when needed | 09:03 |
| Centurion_Dan | can't we limit it to only the changed? | 09:04 |
| KatolaZ | we do actually | 09:04 |
| KatolaZ | but the package files change on average every 4/6 hours on the debian side | 09:05 |
| Centurion_Dan | I'm wondering about dropping the Packages.gz and re-generating them on this side from the .xz | 09:06 |
| KatolaZ | o_O | 09:07 |
| Centurion_Dan | that will probably halve the /merged download. | 09:07 |
| KatolaZ | Centurion_Dan: a mirror should not have issues downloading 500MB every 6 hours... | 09:08 |
| KatolaZ | :) | 09:08 |
| Centurion_Dan | I'm worried I might attract unwanted attention from my ISP looking at my bandwidth usage... | 09:10 |
| Centurion_Dan | I was going to sync every 20 mins. | 09:11 |
| KatolaZ | Centurion_Dan: syncing once every 30/60 min is enough | 09:11 |
| KatolaZ | and you should only have to download packages every 6 hours, on average | 09:11 |
| KatolaZ | I mean, Packages files | 09:11 |
| KatolaZ | Centurion_Dan: I confirm that the last update on the merged repo was at 2:18 UTC | 09:15 |
| KatolaZ | it will update again around 8:something | 09:16 |
| Centurion_Dan | I thought it updated alot faster then every 6 hours? | 09:16 |
| KatolaZ | Centurion_Dan: we run amprolla every 2 minutes | 10:12 |
| KatolaZ | but on the debian side they upgrade the Packages every 6 hours at most | 10:12 |
| Centurion_Dan | ah, of course ;-) | 10:16 |
| parazyd | Also keep in mind our Packages files change only when there is an update from either Devuan or Debian. Don't think they are regenerated every 2 minutes. | 10:45 |
| KatolaZ | no parazyd they are not | 11:26 |
| KatolaZ | but Debian regenerates them every about 6 hours anyway | 11:26 |
| Centurion_Dan | ok. I can confirm that probably is the case... I've run a bunch of rsync cycles this evening... and seen one update at 1.6GB (first in a while), one at 250MB and a couple at 4MB | 11:33 |
| KatolaZ | ok | 11:34 |
| KatolaZ | the one at 1.6GB is due to Contents getting regenerated every Sunday night, probably | 11:35 |
| KatolaZ | (I don't remember if it's Sunday night or Monday early morning in the crontab, will check later) | 11:36 |
| LeePen | Centurion_Dan: Hi. I was wondering if we might move the new slim from experimental to unstable to get it more widely tested? | 21:33 |
| Centurion_Dan | we could do, although did we get any feedback on it so far? Has anybody aside from you used it? Perhaps another shout out to dng and #devuan, #debianfork might be good. | 21:37 |
| LeePen | I haven't seen any feedback. I am not sure anything went to dng. | 21:39 |
| LeePen | Do you want me to do it? I don't want us both to be typing the same email at the same time! ;) | 22:12 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!