Re: Project jcal author passed away in 2017

On Sun, Dec 24, 2023 at 01:55:32PM +0330, masoud naservand wrote: > I saw that https://www.nongnu.org/jcal/ is still mentioning > Mr.Ghassemi as the maintainer. It is with sadness that I have to inform you > that he passed away in 2017. See https://jadi.net/2017/10/ashkan-ghasemi/ > The linux commu

[sr #110988] (wishlist) more php warnings

Follow-up Comment #8, sr#110988 (group administration): [comment #7 comment #7:] > another one: > > AH01071: Got error 'PHP message: /usr/local/share/savane/frontend/php/include/account.php:188: ... > PHP message: /usr/local/share/savane/frontend/php/include/account.php:193:... Thank you, fixed.

[sr #109703] package savane for debian

Follow-up Comment #7, sr#109703 (group administration): Fine. Just forget about what I said. Savane doesn't depend on those. Savannah uses some of them. ___ Reply to this item at: _

[sr #110988] (wishlist) more php warnings

Follow-up Comment #9, sr#110988 (group administration): [comment #6 comment #6:] > [Tue Dec 26 20:42:47.401643 2023] [proxy_fcgi:error] [pid 67929:tid 140014675506880] [remote 240b::] AH01071: Got error 'PHP message: /usr/local/share/savane/frontend/php/include/sane.php:421: [E_WARNING] foreach()

[sr #110988] (wishlist) more php warnings

Follow-up Comment #10, sr#110988 (group administration): [comment #9 comment #9:] > [comment #6 comment #6:] > > [Tue Dec 26 20:42:47.401643 2023] [proxy_fcgi:error] [pid 67929:tid 140014675506880] [remote 240b::] AH01071: Got error 'PHP message: /usr/local/share/savane/frontend/php/include/sane.

[sr #110988] (wishlist) more php warnings

Follow-up Comment #11, sr#110988 (group administration): [comment #10 comment #10:] > AH01071: Got error 'rms.php:666: [E_WARNING] Trying to access array offset on value of type null\nbacktrace:\n{\n\n} > > rms.php? userperms.php truncated, I guess. Now I've found and fixed it; thanks. __

[sr #110995] Private Git Repo

URL: Summary: Private Git Repo Group: Savannah Administration Submitter: jxself Submitted: Thu 28 Dec 2023 11:15:24 AM PST Category: Additional Git repositories

[sr #110995] Private Git Repo

Update of sr#110995 (group administration): Assigned to:None => rwp ___ Follow-up Comment #1: What name would you like to call the git repository?

[sr #110995] Private Git Repo

Update of sr#110995 (group administration): Status:None => In Progress ___ Follow-up Comment #2: Oh! I missed the detail. chief-webmaster-docs is perfect. I will set this up.

[sr #110995] Private Git Repo

Update of sr#110995 (group administration): Status: In Progress => Done Open/Closed:Open => Closed ___ Follow-up Comment #3: Done. Access t

[sr #110995] Private Git Repo

Update of sr#110995 (group administration): Open/Closed: Closed => Open ___ Follow-up Comment #4: Actually, I'm looking for access to a subset of the www team members. To quote: "The people

[sr #110995] Private Git Repo

Follow-up Comment #5, sr#110995 (group administration): I suggest registering a new private group and adding people who need an access to it. Our software has no means to distinguish between private and public repositories within a group, and I don't think we should support that. __