From noreply at bugs.horde.org Mon Jan 27 20:28:49 2020 From: noreply at bugs.horde.org (noreply at bugs.horde.org) Date: Mon, 27 Jan 2020 20:28:49 +0000 Subject: [Tickets #14983] Calendar event alarm via e-mail should send message from default identity Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: https://bugs.horde.org/ticket/14983 ------------------------------------------------------------------------------ Ticket | 14983 Created By | aria at bsc.gwu.edu Summary | Calendar event alarm via e-mail should send message | from default identity Queue | Kronolith Version | Git master Type | Enhancement State | New Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ aria at bsc.gwu.edu (2020-01-27 20:28) wrote: Hi, Under user configuration Preferences -> Calendar -> Notifications you can configure 'Email' notification under "Choose how you want to receive reminders for events with alarms:". This works well and an e-mail is sent to the default identity (from the user to the user) regarding the event at the appropriate time. However, at the bottom of the same configuration screen, there is a field "Email address (optional)" that allows for an e-mail address to be entered. If provided, then the e-mail sent will be from this e-mail address and to this e-mail address. It would be helpful via a configuration directive, we could force the 'FROM:' address for all Kronolith alarms to be the 'default identity' address. Or, as suggested by Michael Rubinsky, "This is why Horde_Alarm either has to be extended to accept a separate from/to address, or, as suggested, more tightly integrate the Identity system with Kronolith." However, I feel that the latter is more complex and would require more development time. Personally, I would be happy with the first option if it means it will be available sooner. Please see https://marc.info/?l=kronolith&m=158014181328358&w=2 Thank you. Aria From noreply at bugs.horde.org Tue Jan 28 07:57:19 2020 From: noreply at bugs.horde.org (noreply at bugs.horde.org) Date: Tue, 28 Jan 2020 08:57:19 +0100 Subject: [Tickets #14981] Re: Class 'Horde_ActiveSync_State_Sql' not found In-Reply-To: References: Message-ID: <20200128085719.Horde.LXdAAxxsW3U4uk8sMiORReZ@bugs.horde.org> BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE E-MAIL-ADRESSE WERDEN NICHT GELESEN. Ticket-URL: https://bugs.horde.org/ticket/14981 ------------------------------------------------------------------------------ Ticket | 14981 Aktualisiert Von | Jan Schneider Zusammenfassung | Class 'Horde_ActiveSync_State_Sql' not found Warteschlange | Synchronization Version | FRAMEWORK_5_2 Typ | Bug -Status | Unconfirmed +Status | Not A Bug Priorität | 3. High Milestone | Patch | Zuständige | ------------------------------------------------------------------------------ From noreply at bugs.horde.org Tue Jan 28 12:05:06 2020 From: noreply at bugs.horde.org (noreply at bugs.horde.org) Date: Tue, 28 Jan 2020 12:05:06 +0000 Subject: [Tickets #14984] Horde Database Libraries tests fail against fail on MySQL 8.0.19 and later Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: https://bugs.horde.org/ticket/14984 ------------------------------------------------------------------------------ Ticket | 14984 Created By | robie.basak at canonical.com Summary | Horde Database Libraries tests fail against fail on | MySQL 8.0.19 and later Queue | Horde Framework Packages Type | Bug State | Unconfirmed Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ robie.basak at canonical.com (2020-01-28 12:05) wrote: The failures are: There were 2 failures: 1) Horde_Db_Adapter_MysqliTest::testColumns Failed asserting that null matches expected 10. /tmp/autopkgtest.qBADD9/build.ebg/src/Horde_Db-2.4.0/test/Horde/Db/Adapter/MysqlBase.php:260 2) Horde_Db_Adapter_Pdo_MysqlTest::testColumns Failed asserting that null matches expected 10. /tmp/autopkgtest.qBADD9/build.ebg/src/Horde_Db-2.4.0/test/Horde/Db/Adapter/MysqlBase.php:260 The relevant test is: public function testColumns() { $col = parent::testColumns(); $this->assertEquals(10, $col->getLimit()); $this->assertEquals(true, $col->isUnsigned()); $this->assertEquals('int(10) unsigned', $col->getSqlType()); } $col->getLimit() is expected to be, for a column defined as "int(10) unsigned", 10. However, according to MySQL's release notes (https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-19.html): "Display width specification for integer data types was deprecated in MySQL 8.0.17, and now statements that include data type definitions in their output no longer show the display width for integer types..." There are some exceptions but my understanding is that since int(10) doesn't make sense for MySQL, if you define a table like that MySQL will accept it, but a data dictionary query will not return the "(10)" part any more. So the test's assumption is now wrong. It's not obvious to me if adjusting the test will leave the assumption present in other parts of production code. Downstream bug: https://bugs.launchpad.net/ubuntu/+source/php-horde-db/+bug/1861099 From noreply at bugs.horde.org Thu Jan 30 11:35:29 2020 From: noreply at bugs.horde.org (noreply at bugs.horde.org) Date: Thu, 30 Jan 2020 11:35:29 +0000 Subject: [Tickets #14985] After uninstall lock files remain Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: https://bugs.horde.org/ticket/14985 ------------------------------------------------------------------------------ Ticket | 14985 Created By | jack at teleworm.com Summary | After uninstall lock files remain Queue | Horde Base Version | 5.2.21 Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ jack at teleworm.com (2020-01-30 11:35) wrote: After following the uninstall procedure mysql lock files remain. Some function require less thann 125 locks per kernel (my understanding please check - anacron?) therefore spurious locks could cause issues on the system (in my case amavisd-new fails randomly - for yet another reason!) Therefore I am suggesting a note on the uninstall page to restart mysqld after uninstalling horde. eg. service mysqld restart This clears the lock files. run lslk to check the locks have gone From noreply at bugs.horde.org Thu Jan 30 11:39:43 2020 From: noreply at bugs.horde.org (noreply at bugs.horde.org) Date: Thu, 30 Jan 2020 11:39:43 +0000 Subject: [Tickets #14985] Re: After uninstall lock files remain In-Reply-To: References: Message-ID: <20200130113944.Horde.G8IqKIkIJgzZk3vF9ImfJb7@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: https://bugs.horde.org/ticket/14985 ------------------------------------------------------------------------------ Ticket | 14985 Updated By | build+horde at de-korte.org Summary | After uninstall lock files remain Queue | Horde Base Version | 5.2.21 Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ build+horde at de-korte.org (2020-01-30 11:39) wrote: Which uninstall procedure do you mean? Could you provide a link? From noreply at bugs.horde.org Sun Feb 2 16:18:17 2020 From: noreply at bugs.horde.org (noreply at bugs.horde.org) Date: Sun, 02 Feb 2020 16:18:17 +0000 Subject: [Tickets #14986] Leave Messages as Unread/Unseen Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: https://bugs.horde.org/ticket/14986 ------------------------------------------------------------------------------ Ticket | 14986 Created By | simon.buongiorno at gmail.com Summary | Leave Messages as Unread/Unseen Queue | IMP Version | Git master Type | Enhancement State | New Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ simon.buongiorno at gmail.com (2020-02-02 16:18) wrote: As a user, I would like the ability to read messages without them being marked as "Seen", but still retain the ability to have them marked as seen when moving them to a different folder. From noreply at bugs.horde.org Sun Feb 2 16:48:58 2020 From: noreply at bugs.horde.org (noreply at bugs.horde.org) Date: Sun, 02 Feb 2020 16:48:58 +0000 Subject: [Incidencias #14986] Re: Leave Messages as Unread/Unseen In-Reply-To: References: Message-ID: <20200202164858.Horde.uJc41z0moF9g-kGG9fcHkqY@bugs.horde.org> NO CONTESTE A ESTE MENSAJE. ESTA DIRECCIÓN NO SE CONSULTA. URL de la incidencia: https://bugs.horde.org/ticket/14986 ------------------------------------------------------------------------------ Incidencia | 14986 Actualizado por | alex at amjimeno.net Resumen | Leave Messages as Unread/Unseen Cola | IMP Versión | Git master Tipo | Enhancement Estado | New Prioridad | 2. Medium Milestone | Patch | Propietarios | ------------------------------------------------------------------------------ alex at amjimeno.net (2020-02-02 16:48) escribió: Hi, I am interested too. I am subscribing to this ticket. Regards