Re: [savannah-help-public] [GSoC] Quick Update on Fuzzing

oing it by cron though because > any party can mirror using cron. I am guessing the real question is ... Exactly, cron jobs would only be the backup option. I will prepare the hook files (one for each repository) and send them to you. Armin

Re: [savannah-help-public] [GSoC] Quick Update on Fuzzing

HTTPS) on the server? In that case, the post receive hooks really come down to executing `git push --mirror github-mirror` if the remotes `github-mirror` were added to the repositories on the server. Please let me know what you think and what you prefer. Thank you so much, Armin > &g

Re: [savannah-help-public] [GSoC] Quick Update on Fuzzing

your choice. (2) When using HTTPS, I would first correspond with the community about storing the password safely, and let you know about it then :) Thanks everyone, Armin

[savannah-help-public] FreeType: Mirror to GitHub

Hi guys, It's been a few months now and I would really love to get going with the GitHub mirror of FreeType before GitHub becomes unusable due to M$ ... ;P Can we agree on a way to directly mirror the repository in a server hook (simple + easy)? Thanks Armin

Re: [savannah-help-public] FreeType: Mirror to GitHub

imple + > easy)? Armin

[savannah-help-public] 502: Fetching FreeType

with humans but automated systems fail as well and in terms of OSS-Fuzz that means no updates of the fuzzers for up to a whole day. Is there anything you know / can do about that? Thanks Armin

Re: [savannah-help-public] 502: Fetching FreeType

ll the time it takes + thanks for the update! Just a quick question: do you think switching to git:// would help (you and/or us)? Armin

Re: [savannah-help-public] FreeType: Mirror to GitHub

a more complicated infrastructure for FreeType that I would love to avoid. Let's just talk again as soon as the other important issues are solved; I would appreciate a solution that means no overhead for FreeType and next-to-no overhead for you ... simple + easy :) Armin

Re: [savannah-help-public] 502: Fetching FreeType

>> Jesus Christ ... I'm sorry to hear that! All the best with locking >> them out, no worries, take all the time it takes + thanks for the update! > > You know how it goes. It is why we can't have nice things. :-( *hug* >> Just a quick question: do you think switching to git:// would help

Re: [savannah-help-public] 502: Fetching FreeType

>> > Just a quick question: do you think switching to git:// would help >> > (you and/or us)? >> >> If you are using http:// now then switching to git:// would seem to be >> equivalent. Should avoid the current brownout problem. Until and >> unless the attackers start hitting the git:// side

[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker

URL: Summary: Trouble Using Savannah Bug Tracker Project: Savannah Administration Submitted by: arm_in Submitted on: Tue 24 Jul 2018 05:25:22 PM UTC Category: Savannah trackers - b

[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker

Follow-up Comment #2, sr #109536 (project administration): I just tried to clear all cookies in connection with "gnu" and "savannah". However, the effect still does happen. ___ Reply to this item at:

[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker

Follow-up Comment #5, sr #109536 (project administration): When I read the other two cases, it seems that the settings are important: Default for Octave: Open/Closed = "Open" Additional constraint = "deactivated" Failure Case for Octave: Open/Closed = "Any" Additional constraint = "activated"

[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker

Follow-up Comment #9, sr #109536 (project administration): To narrow down the problem: * I'm using the tracker under four different systems. * Different browsers (IE, Firefox, SeaMonkey, Safari) * Different OS (Windows XP, 7, 10, iOS 11) * Different internet providers * If I screwed up my user pr

[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker

Follow-up Comment #11, sr #109536 (project administration): Hmmm, something went wrong. The SQL error has disappeared. But it seems that the "modified since" field is not retained. If I click on "Bugs" or "Bugs->Brows", the current date will be written into the date field. All 1300+ active error

[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker

Follow-up Comment #13, sr #109536 (project administration): I've tried it again. It looks really good now. The SQL error is gone, and "Additional constraint" as well as "Modified Since" date is stored correctly. Thank you very much for your help!!