From nobody at parabola.nu Fri Feb 5 08:54:20 2021 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 05 Feb 2021 08:54:20 -0000 Subject: [Dev] Orphan Libre package [linux-libre-firmware] marked out-of-date Message-ID: <20210205085420.2317567.91918@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * linux-libre-firmware 1:1.3.1-2 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-firmware/ * linux-libre-firmware 1:1.3.1-2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-firmware/ * linux-libre-firmware 1:1.3.1-2 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-firmware/ The user provided the following additional text: Thank you for maintaining this package! A new version has been released: https://jxself.org/git/?p=linux-libre-firmware.git From nobody at parabola.nu Fri Feb 5 09:19:14 2021 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 05 Feb 2021 09:19:14 -0000 Subject: [Dev] Orphan Libre package [filesystem] marked out-of-date Message-ID: <20210205091914.2317568.82610@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * filesystem 2020.09.03-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/filesystem/ * filesystem 2020.09.03-2.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/filesystem/ The user provided the following additional text: Thank you for maintaining this package! A new version has been released by Arch Linux: https://github.com/archlinux/svntogit-packages/commits/packages/filesystem/trunk From pagure at pagure.io Fri Feb 5 17:56:54 2021 From: pagure at pagure.io (=?utf-8?q?Grizzly_User?=) Date: Fri, 5 Feb 2021 17:56:54 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=239=3A_libre/iceweasel=3A_85?= =?utf-8?q?=2E0=2E1-parabola1?= Message-ID: grizzlyuser opened a new pull-request against the project: `abslibre` that you are following: `` libre/iceweasel: 85.0.1-parabola1 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/9 From pagure at pagure.io Fri Feb 5 17:57:19 2021 From: pagure at pagure.io (=?utf-8?q?Grizzly_User?=) Date: Fri, 5 Feb 2021 17:57:19 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=238=3A_libre/iceweasel=3A_85?= =?utf-8?q?=2E0-1=2Eparabola1?= In-Reply-To: Message-ID: grizzlyuser closed without merging a pull-request against the project: `abslibre` that you are following. Closed pull-request: `` libre/iceweasel: 85.0-1.parabola1 `` https://pagure.io/abslibre/pull-request/8 From nobody at parabola.nu Sun Feb 7 02:46:49 2021 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 07 Feb 2021 02:46:49 -0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date Message-ID: <20210207024649.2317568.30643@winston.parabola.nu> eliotreyna at disroot.org wants to notify you that the following packages may be out-of-date: * iceweasel 1:85.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/iceweasel/ * iceweasel 1:85.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/ The user provided the following additional text: Firefox source code has been udpated to the version 85.0.1. Acutally, it fixes many bugs (many of them are related to Cache API state). For more info, please go to the following website: https://www.mozilla.org/en-US/firefox/85.0.1/releasenotes/ Thanks. From nobody at parabola.nu Sun Feb 14 21:43:52 2021 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 14 Feb 2021 21:43:52 -0000 Subject: [Dev] Orphan Libre package [icecat] marked out-of-date Message-ID: <20210214214352.3202980.52059@winston.parabola.nu> eliotreyna at disroot.org wants to notify you that the following packages may be out-of-date: * icecat 78.7.0_pre-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/icecat/ * icecat 78.7.0-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/icecat/ The user provided the following additional text: GNU IceCat development branch as been updated to the version 78.7.1, which shares the same hotfix as Firefox ESR. Please update GNU IceCat ASAP. Thanks. From nobody at parabola.nu Mon Feb 15 00:52:38 2021 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 15 Feb 2021 00:52:38 -0000 Subject: [Dev] Orphan Libre package [qutebrowser] marked out-of-date Message-ID: <20210215005238.3202981.22263@winston.parabola.nu> eliotreyna at disroot.org wants to notify you that the following packages may be out-of-date: * qutebrowser 1.14.1-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/qutebrowser/ * qutebrowser 1.14.1-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/qutebrowser/ The user provided the following additional text: Qutebrowser has been updated to the version 2.0.2. https://github.com/qutebrowser/qutebrowser/releases/tag/v2.0.2 From mail at easylee.nl Fri Feb 19 07:20:44 2021 From: mail at easylee.nl (Easy Lee) Date: Fri, 19 Feb 2021 08:20:44 +0100 Subject: [Dev] New tier 1 mirror server The Netherlands Message-ID: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> Hi everyone at Parabola, I'd like to contribute to the project by providing a mirror server in The Netherlands. Details: HTTP: http://mirror.easylee.nl/parabola HTTPS: https://mirror.easylee.nl/parabola rsync: rsync://mirror.easylee.nl/parabola Bandwidth: 1 Gbit/s Reachable at IPv4 and IPv6. I am syncing once an hour. Please use this address (mail at easylee.nl) as primary contact. Cheers! -------------- next part -------------- An HTML attachment was scrubbed... URL: From nobody at parabola.nu Fri Feb 19 14:04:28 2021 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 19 Feb 2021 14:04:28 -0000 Subject: [Dev] Orphan Libre package [linux-libre-lts] marked out-of-date Message-ID: <20210219140428.3202982.19248@winston.parabola.nu> ugw.ugw at gmail.com wants to notify you that the following packages may be out-of-date: * linux-libre-lts 5.4.85-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts/ * linux-libre-lts 5.4.85-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts/ * linux-libre-lts-docs 5.4.85-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts-docs/ * linux-libre-lts-docs 5.4.85-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts-docs/ * linux-libre-lts-headers 5.4.85-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts-headers/ * linux-libre-lts-headers 5.4.85-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts-headers/ The user provided the following additional text: LTS 5.10 is out and mkinitcpio will start to break with older kernels soon, as per announcement on Arch's front page From mail at easylee.nl Sun Feb 21 13:42:11 2021 From: mail at easylee.nl (Easy Lee) Date: Sun, 21 Feb 2021 14:42:11 +0100 Subject: [Dev] New tier 1 mirror server The Netherlands In-Reply-To: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> References: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> Message-ID: Hi, Just to be sure since I haven't heard anything as of yet. Am I addressing the right list? Or is there no need for a mirror? Best On Fri, Feb 19, 2021, at 8:20 AM, Easy Lee wrote: > Hi everyone at Parabola, > > I'd like to contribute to the project by providing a mirror server in The Netherlands. > > Details: > > HTTP: http://mirror.easylee.nl/parabola > > HTTPS: https://mirror.easylee.nl/parabola > > rsync: rsync://mirror.easylee.nl/parabola > > Bandwidth: 1 Gbit/s > > Reachable at IPv4 and IPv6. > > I am syncing once an hour. > > Please use this address (mail at easylee.nl) as primary contact. > > Cheers! -------------- next part -------------- An HTML attachment was scrubbed... URL: From isacdaavid at isacdaavid.info Sun Feb 21 20:59:18 2021 From: isacdaavid at isacdaavid.info (Isaac David) Date: Sun, 21 Feb 2021 14:59:18 -0600 Subject: [Dev] New tier 1 mirror server The Netherlands In-Reply-To: References: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> Message-ID: Hi, You wrote to the right list and mirrors are very much welcome all the time. Thanks for setting another one up. I will let it hang out with the rest of the mirror kids in brief... Stay tuned. -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C Jami: isacdaavid2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at easylee.nl Mon Feb 22 07:05:32 2021 From: mail at easylee.nl (Easy Lee) Date: Mon, 22 Feb 2021 08:05:32 +0100 Subject: [Dev] New tier 1 mirror server The Netherlands In-Reply-To: References: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> Message-ID: <6af7d249-b244-4017-87fa-131260263abf@www.fastmail.com> Hi, Thanks! Let me know if all is fine. Cheers On Sun, Feb 21, 2021, at 9:59 PM, Isaac David wrote: > Hi, > > You wrote to the right list and mirrors are very much welcome all the time. Thanks for setting another one up. I will let it hang out with the rest of the mirror kids in brief... Stay tuned. > > > -- > Isaac David > GPG: 38D33EF29A7691134357648733466E12EC7BA943 > Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C > Jami: isacdaavid2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From isacdaavid at isacdaavid.info Tue Feb 23 05:03:22 2021 From: isacdaavid at isacdaavid.info (Isaac David) Date: Mon, 22 Feb 2021 23:03:22 -0600 Subject: [Dev] New tier 1 mirror server The Netherlands In-Reply-To: <6af7d249-b244-4017-87fa-131260263abf@www.fastmail.com> References: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> <6af7d249-b244-4017-87fa-131260263abf@www.fastmail.com> Message-ID: Hello again, I'm afraid I won't be able to add your mirror myself, but that doesn't mean it won't be added eventually. Some of the newer devs want to perform some more in-depth checks before adding new mirrors, so be patient. Regards -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C Jami: isacdaavid2 From bill-auger at peers.community Tue Feb 23 08:25:12 2021 From: bill-auger at peers.community (bill-auger) Date: Tue, 23 Feb 2021 03:25:12 -0500 Subject: [Dev] New tier 1 mirror server The Netherlands In-Reply-To: References: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> <6af7d249-b244-4017-87fa-131260263abf@www.fastmail.com> Message-ID: <20210223032512.444c958c@parabola.localdomain> if the task were only to add a new mirror, that is quite easy to do, but it is not a high priority - the mirror network is healthier than ever now - in fact, it is becoming problematic to add new mirrors; because the number of mirrors has almost doubled in the past few years, and each new one adds load onto the repo server, which is already over-loaded - we have been working out plan to split the mirrors into tiers - that will take some time and effort to accomplish though that was not to say that we do not want any more mirrors - it is always good to grow the mirror network; but there is no urgency to that either - in fact, we hope that mirrors are dedicated for the long-term; so some initial delay is prudent - as a point of reference, the last two new mirrors did not get added to the mirrorlist until a month or two after they requested - it is not unreasonable, for example, to expect that someone may request to join the mirror network and then shut down a month later - patience is a virtue, as they say as this thread subject suggests though, this could be one of the tier 1 mirrors; and those entail significantly more responsibility, and so deserve more scrutiny - there are some logistics to work out first, in order to avoid adding more load onto the repo server - that is the reason why i did not respond immediately the first step is to create a new mailing list dedicated to mirrors - some of the current mirror operators have suggested one, so there could be a low-volume channel, for only important communication among the mirror operators, rather than expecting everyone to subscribe to the 'dev' list next, i have an email prepared to send out to all the mirrors operators, asking some to be on tier 1 and stick to a rigid and rapid sync schedule, (eg: 3-4 times per hour), and for the others to start synchronizing with one of the tier 1 mirrors, and also increasing their rate closer to once per hour - some of them sync only once or twice per day now, while others sync every 10 minutes, and yet others sync erratically - overall, it should be a nice improvement for user-experience, to normalize the sync rates across mirrors regarding this new mirror, some of requested information was not supplied - the wiki article requests that the introduction email should include the name of the responsible party or organization which operates the service, a secondary contact, and the precise sync schedule - those are currently not essential, because all mirrors are effectively tier 2 currently; but that information will be essential for tier 1 mirrors tier 1 mirrors will effectively be critical infrastructure; and tier 1 mirror operators are effectively trusted team members - not "trusted" as a matter of security (signatures accomplish that), but as a matter of reliability - a significant proportion of the mirror network will be dependent on their respective tier 1 mirrors; so there should be more than one possible way to contact the operators in case of problems - if we only have a single email address for an anonymous person, and especially with that email is handled by the same host as the mirror, that amounts to a single point of failure for a significant proportion of the mirror network - ideally, we would also like to have a GPG key for each tier 1 operator; and we do have one for all of the current candidates From mail at easylee.nl Tue Feb 23 08:58:31 2021 From: mail at easylee.nl (Easy Lee) Date: Tue, 23 Feb 2021 09:58:31 +0100 Subject: [Dev] New tier 1 mirror server The Netherlands In-Reply-To: <20210223032512.444c958c@parabola.localdomain> References: <4578e3bc-2c13-4b41-a5cc-48602a627a65@www.fastmail.com> <6af7d249-b244-4017-87fa-131260263abf@www.fastmail.com> <20210223032512.444c958c@parabola.localdomain> Message-ID: Hi Bill, Thank you for your extensive response. I fully agree with everything said. Reflecting on my request: It will not be a problem for me to share more information and become a trusted member in the long run. Setting up and sharing a multiple times per hour sync schedule is OK. A secondary way of contacting me (by phone or additional address) is no problem. I am a private person donating to the Arch(based) community by providing a mirror server. Not an organization or business. With your permission I will continue syncing once an hour of rsync://repo.parabola.nu:875/repos/ for now and will follow everything happening including signing up for the future mirror mailing-list. If it's not OK to continue syncing because of the load, I will halt. Would it be possible to provide my additional and private contact details to someone directly? Best, Eric On Tue, Feb 23, 2021, at 9:25 AM, bill-auger wrote: > if the task were only to add a new mirror, that is quite easy to > do, but it is not a high priority - the mirror network is > healthier than ever now - in fact, it is becoming problematic to > add new mirrors; because the number of mirrors has almost > doubled in the past few years, and each new one adds load onto > the repo server, which is already over-loaded - we have been > working out plan to split the mirrors into tiers - that will > take some time and effort to accomplish though > > that was not to say that we do not want any more mirrors - it is > always good to grow the mirror network; but there is no urgency > to that either - in fact, we hope that mirrors are dedicated for > the long-term; so some initial delay is prudent - as a point of > reference, the last two new mirrors did not get added to the > mirrorlist until a month or two after they requested - it is not > unreasonable, for example, to expect that someone may request to > join the mirror network and then shut down a month later - > patience is a virtue, as they say > > as this thread subject suggests though, this could be one of the > tier 1 mirrors; and those entail significantly more > responsibility, and so deserve more scrutiny - there are some > logistics to work out first, in order to avoid adding more load > onto the repo server - that is the reason why i did not respond > immediately > > the first step is to create a new mailing list dedicated to > mirrors - some of the current mirror operators have suggested > one, so there could be a low-volume channel, for only important > communication among the mirror operators, rather than expecting > everyone to subscribe to the 'dev' list > > next, i have an email prepared to send out to all the mirrors > operators, asking some to be on tier 1 and stick to a rigid and > rapid sync schedule, (eg: 3-4 times per hour), and for the > others to start synchronizing with one of the tier 1 mirrors, > and also increasing their rate closer to once per hour - some of > them sync only once or twice per day now, while others sync > every 10 minutes, and yet others sync erratically - overall, it > should be a nice improvement for user-experience, to normalize > the sync rates across mirrors > > regarding this new mirror, some of requested information was not > supplied - the wiki article requests that the introduction email > should include the name of the responsible party or organization > which operates the service, a secondary contact, and the precise > sync schedule - those are currently not essential, because all > mirrors are effectively tier 2 currently; but that information > will be essential for tier 1 mirrors > > tier 1 mirrors will effectively be critical infrastructure; and > tier 1 mirror operators are effectively trusted team members - > not "trusted" as a matter of security (signatures accomplish > that), but as a matter of reliability - a significant proportion > of the mirror network will be dependent on their respective tier > 1 mirrors; so there should be more than one possible way to > contact the operators in case of problems - if we only have a > single email address for an anonymous person, and especially > with that email is handled by the same host as the mirror, that > amounts to a single point of failure for a significant > proportion of the mirror network - ideally, we would also like > to have a GPG key for each tier 1 operator; and we do have one > for all of the current candidates > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill-auger at peers.community Thu Feb 25 03:57:05 2021 From: bill-auger at peers.community (bill-auger) Date: Wed, 24 Feb 2021 22:57:05 -0500 Subject: [Dev] tiered mirrors schema Message-ID: <20210224225705.7869b3f0@parabola.localdomain> i have had this message ready to send to mirror operators for since before the last two mirrors joined the network - another joined this week; and this concern really cant be postponed any longer - the reason why this is important is because new mirrors puts a significant extra load onto the repo server - in 2018, lukeshu told me that we were already pushing the bandwidth limits on 1984's generosity, and the number of mirrors has nearly doubles since then - tiering the mirrors in this way, is a matter of respect, appreciation, and gratitude to 1984 no one on this list needs to do anything; but i thought people may be interested or would like to comment - i also changed the wiki page quite a bit, to be more aligned with the arch article, and added some suggestions, such as seeding the p2p network instead or creating more complete mirrors - the one thing i anticipate that people may have an opinion about, is how i made the requirements more precise and stringent (isacdaavid already did) - anticipating that some may wonder why: the best answer is that the mirror network is very healthy now, healthy than ever - if these are going to be tiered now, then theres no reason not to raise the standard for tier-1 and tier-2, while retaining the original loose requirements for tier-3 https://wiki.parabola.nu/Creating_a_mirror this is the message i sent to all mirror operators: == new tiered mirrors schema == due to an increasing number of mirrors joining the parabola mirror network, the sync schedules are now overlapping in some places - we would like to reorganize them into a more uniform structured schedule for the future - this would reduce the load on our repo server, and also improve the service for parabola users - the increasing number of mirrors is, of course, a good thing - presumably, it indicates that parabola is gaining in popularity; but parabola does not have any funding, so it is putting a strain on our infrastructure currently, all mirrors are pulling directly from parabola; which is pushing the limit of what our extremely generous hosting benefactor can offer for gratis - the plan is such that the relatively modest hosts will be asked to be on "tier-2" (pulling regularly from some relatively faster host, other than parabola.nu); and the higher-capacity hosts will be asked if it is feasible for them to become dedicated "tier-1" mirrors (ones which some number of the tier-2 mirrors will pull from regularly) initially, we would like to have three to six tier-1 mirrors, synchronizing with the parabola tier-0 server, every thirty minutes (5-10 minutes separation); and for each tier-2 mirror to sync once or twice per hour, distributed however the tier-1 mirrors can accommodate them the intended effect is such that delivery times for new packages will be improved for users significantly; with 404 errors being much less likely, due to all mirrors being within a tighter temporal proximity to each other - although a few of the newer mirrors are already on a rapid schedule, most are currently syncing much less frequently - the end-to-end delay is up to two days, for clients of those mirrors; and 404s are common when using the default re-director; because of the loosely-knit federation the accelerated sync rates should have no adverse impact on mirrors - before each sync attempt, the recommended mirroring script downloads a timestamp file, and cancels the complete sync if there are no changes - that is because some megabytes are transferred even when there are no changes - with that guard in place, the total incoming bandwidth for any mirror is essentially the same, regardless of the rate at which the sync script is run - its use was recently added to the wiki as a hard criteria for endorsed mirrors it is, of course, at each mirror operator's discretion to throttle any connections from unknown clients, or those using excessive bandwidth - managing the precise sync schedules of tier-2 mirrors, will be at the discretion of each tier-1 mirror operator - we ask only that tier-1 mirror operators give priority on the rsync channel, to the tier-2 mirrors to which they are feeding, providing that the admins are responsive and agreeable to reasonable terms of use suggestions == mailing list == some of the current mirror operators have suggested a new low-volume mailing list, dedicated for only important communication among the mirror operators, rather than expecting everyone to subscribe to the development mailing list, and/or publishing contact info publicly - it would be extremely rare for parabola to need to send a mass email such as this one; but it could be useful, for occasional coordination of sync schedules, such as now - you should receive an invitation soon - it may be somewhat busy during this initial migration into tiers; but the volume will be close to nil afterward == actions requested == at this time, we have incomplete information on many of the mirrors; so there is no request for action on your part yet - this is the initial attempt to gather all of the information needed to coordinate the network, and subscribe mirror operators to the new mailing list From bill-auger at peers.community Thu Feb 25 06:19:40 2021 From: bill-auger at peers.community (bill-auger) Date: Thu, 25 Feb 2021 01:19:40 -0500 Subject: [Dev] tiered mirrors schema In-Reply-To: <20210224225705.7869b3f0@parabola.localdomain> References: <20210224225705.7869b3f0@parabola.localdomain> Message-ID: <20210225011940.3e71a22f@parabola.localdomain> just an observation i got to wondering how accurate my claim was, that the number of mirrors had nearly doubled in the past few years - i was not actually sure; but i remembered that it was 2017, shortly after i started publishing ISOs, when the host was concerned about our increased bandwidth usage - anyways, i looked at the history of the downlaods page to get a better idea about the mirror network in the past - i under-estimated the growth by quite a bit https://wiki.parabola.nu/index.php?title=Get_Parabola&oldid=18297 before oaken-source and i joined parabola, there were only 5 mirrors; so the _net_ number of mirrors (the bandwidth load on winston) has actually tripled since 2017 its not all that surprising - 4 years is a significant portion of parabola's history - but it does demonstrate the increased load on winston (and therefore the increased generosity of 1984) From mail at easylee.nl Thu Feb 25 07:07:35 2021 From: mail at easylee.nl (Easy Lee) Date: Thu, 25 Feb 2021 08:07:35 +0100 Subject: [Dev] tiered mirrors schema In-Reply-To: <20210225011940.3e71a22f@parabola.localdomain> References: <20210224225705.7869b3f0@parabola.localdomain> <20210225011940.3e71a22f@parabola.localdomain> Message-ID: Hi, Not only that. It is a confirmation of the good work everyone is doing. A big compliment to the community. On Thu, Feb 25, 2021, at 7:19 AM, bill-auger wrote: > just an observation > > i got to wondering how accurate my claim was, that the number of > mirrors had nearly doubled in the past few years - i was not > actually sure; but i remembered that it was 2017, shortly after > i started publishing ISOs, when the host was concerned about our > increased bandwidth usage - anyways, i looked at the history of > the downlaods page to get a better idea about the mirror network > in the past - i under-estimated the growth by quite a bit > > https://wiki.parabola.nu/index.php?title=Get_Parabola&oldid=18297 > > before oaken-source and i joined parabola, there were only 5 > mirrors; so the _net_ number of mirrors (the bandwidth load on > winston) has actually tripled since 2017 > > its not all that surprising - 4 years is a significant portion > of parabola's history - but it does demonstrate the increased > load on winston (and therefore the increased generosity of 1984) > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nobody at parabola.nu Fri Feb 26 18:21:29 2021 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 26 Feb 2021 18:21:29 -0000 Subject: [Dev] Orphan Libre package [pacman] marked out-of-date Message-ID: <20210226182129.3202982.86193@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * pacman 5.2.2-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/pacman/ * pacman 5.2.2-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/pacman/ * pacman-debug 5.2.2-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/pacman-debug/ * pacman-debug 5.2.2-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/pacman-debug/ The user provided the following additional text: Thank you for maintaining this package! A new pkgrel is available: https://archlinux.org/packages/core/x86_64/pacman/ From bill-auger at peers.community Fri Feb 26 21:53:16 2021 From: bill-auger at peers.community (bill-auger) Date: Fri, 26 Feb 2021 16:53:16 -0500 Subject: [Dev] Fw: [arch-announce] Moving to Zstandard images by default on mkinitcpio Message-ID: <20210226165316.44a8baab@parabola.localdomain> Begin forwarded message: Date: Fri, 19 Feb 2021 13:37:39 -0000 From: "Arch Linux: Recent news updates: Giancarlo Razzolini via arch-announce" To: arch-announce at archlinux.org Cc: "Arch Linux: Recent news updates: Giancarlo Razzolini" Subject: [arch-announce] Moving to Zstandard images by default on mkinitcpio As linux-lts moved to the 5.10 version, all official kernels of Arch Linux now support zstd compressed initramfs images, so mkinitcpio is switching to zstd compressed images by default with version 30, which is currently on [testing]. If, for any reason, you are using a kernel version prior to 5.9, make sure to change mkinitcpio.conf COMPRESSION to use one of the compressors supported, like gzip, otherwise you **will not** be able to boot images generated by mkinitcpio. URL: https://www.archlinux.org/news/moving-to-zstandard-images-by-default-on-mkinitcpio/ _______________________________________________ arch-announce mailing list arch-announce at lists.archlinux.org https://lists.archlinux.org/listinfo/arch-announce From bill-auger at peers.community Fri Feb 26 22:05:08 2021 From: bill-auger at peers.community (bill-auger) Date: Fri, 26 Feb 2021 17:05:08 -0500 Subject: [Dev] Fw: [arch-announce] Moving to Zstandard images by default on mkinitcpio In-Reply-To: <20210226165316.44a8baab@parabola.localdomain> References: <20210226165316.44a8baab@parabola.localdomain> Message-ID: <20210226170508.7dba927e@parabola.localdomain> related to: https://lists.parabola.nu/pipermail/assist/2021-February/001591.html Megver - would you be able to upgrade linux-libre-lts this week? a bug of this severity would normally a justify bug report - the solution is obvious though, and needs little discussion we could fix this temporarily in 'nonsystemd/mkinitcpio', and add an emergency 'libre/mkinitcpio' package with: /etc/mkinitcpio.conf: COMPRESSION="gzip" thoughts?, comments?, suggestions? From megver83 at hyperbola.info Sat Feb 27 19:04:11 2021 From: megver83 at hyperbola.info (Megver83) Date: Sat, 27 Feb 2021 16:04:11 -0300 Subject: [Dev] Fw: [arch-announce] Moving to Zstandard images by default on mkinitcpio In-Reply-To: <20210226170508.7dba927e@parabola.localdomain> References: <20210226165316.44a8baab@parabola.localdomain> <20210226170508.7dba927e@parabola.localdomain> Message-ID: <4104b4a1-0d46-b469-de8b-18a81da95831@hyperbola.info> El 26-02-21 a las 19:05, bill-auger escribi?: > related to: > https://lists.parabola.nu/pipermail/assist/2021-February/001591.html > > Megver - would you be able to upgrade linux-libre-lts this week? Of course, I'll upgrade kernels this weekend, starting with linux-libre-lts > a bug of this severity would normally a justify bug report - the > solution is obvious though, and needs little discussion > > we could fix this temporarily in 'nonsystemd/mkinitcpio', and > add an emergency 'libre/mkinitcpio' package with: > /etc/mkinitcpio.conf: > COMPRESSION="gzip" > > thoughts?, comments?, suggestions? Better wait till kernels get their updates. Last time I had problems when building PCK, that's why it got stuck in v5.8, but the rest is OK. Maybe a news telling to wait the update is simpler. -- ~Megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From pagure at pagure.io Sat Feb 27 21:36:07 2021 From: pagure at pagure.io (=?utf-8?q?Grizzly_User?=) Date: Sat, 27 Feb 2021 21:36:07 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2310=3A_libre/iceweasel=3A_86?= =?utf-8?q?=2E0_sync_with_upstream_projects?= Message-ID: grizzlyuser opened a new pull-request against the project: `abslibre` that you are following: `` libre/iceweasel: 86.0 sync with upstream projects `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/10 From pagure at pagure.io Sat Feb 27 21:36:32 2021 From: pagure at pagure.io (=?utf-8?q?Grizzly_User?=) Date: Sat, 27 Feb 2021 21:36:32 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=239=3A_libre/iceweasel=3A_85?= =?utf-8?q?=2E0=2E1-parabola1?= In-Reply-To: Message-ID: grizzlyuser closed without merging a pull-request against the project: `abslibre` that you are following. Closed pull-request: `` libre/iceweasel: 85.0.1-parabola1 `` https://pagure.io/abslibre/pull-request/9