Project

General

Profile

Actions

tickets #163547

open

Fwd: Cron <mail_reminder@pinot> /home/mail_reminder/git/mail-reminder --no-debug

Added by georg@syscid.com 5 months ago. Updated 10 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2024-07-09
Due date:
% Done:

0%

Estimated time:

Description

-------- Forwarded Message --------
Subject: Cron
/home/mail_reminder/git/mail-reminder --no-debug
Date: Tue, 9 Jul 2024 11:42:01 +0000 (UTC)
From: (Cron Daemon)
To: admin-auto@opensuse.org

Invalid value for 'biweekly_week' key in
/home/mail_reminder/git/data/board-meeting.conf: should be either 0 or 1.

Actions #1

Updated by crameleon 5 months ago

  • Private changed from Yes to No
Actions #3

Updated by sfalken@cloverleaf-linux.org 24 days ago

Georg, So this has slipped a bit, do you have any idea what needs to happen here? I'm perfectly willing to try and fix it, but I don't understand the problem

Actions #4

Updated by crameleon 24 days ago

I would propose to first git revert 0fc91a3149e9b550e802948eddcc13ca795012d5 and 909a62f2d8ebf19a414920ecbc55d67c5094ce50. Then either leave it at that, or implement whatever functionality was desired that caused these changes in a working manner (the commit messages provided are unfortunately rather meaningless instead of explaining what the change was trying to solve).

Actions #5

Updated by sfalken@cloverleaf-linux.org 10 days ago

OK, so it looks to me like Doug did this in https://github.com/openSUSE/mail-reminder/pull/30/commits

And yeah, I agree, the commit messages aren't very clear. The functionality that was being attempted was to shift the meeting announcement by one week, from where it had been previously.

(i.e. If the meeting was being done on the First and Third Monday of every month, continuing on a biweekly cycle, it was shifted to the Second and Fourth Monday of the month after the initial commit was made, and intended to continue on that cycle)

Actions #6

Updated by sfalken@cloverleaf-linux.org 10 days ago

It's more work, but reading through the documentation, it looks like the only real way to do this, as it exists, is to use the [Schedule] config, to set the schedule?

Actions

Also available in: Atom PDF