Re: dovecot-indexer writting as root
Hi Anyone on this ? On 11 August 2024 04:02:56 Joan Moreau via dovecot wrote: No, the change of uid comes at the end of the process (commit) On 2 August 2024 19:08:00 Aki Tuomi via dovecot wrote: You are probably doing file operations before setuid() call, do you initialize things too soon? Aki On 01/08/2024 12:59 EEST Joan Moreau via dovecot wrote: Hi Any idea on that ? Thank you On Sat, 2024-07-27 at 15:53 +0800, Joan Moreau via dovecot wrote: Hi I have that issue times to times Full case described properly here : https://github.com/grosjo/fts-xapian/issues/168 Can you help understand the root cause of that ? THank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: dovecot-indexer writting as root
No, the change of uid comes at the end of the process (commit) On 2 August 2024 19:08:00 Aki Tuomi via dovecot wrote: You are probably doing file operations before setuid() call, do you initialize things too soon? Aki On 01/08/2024 12:59 EEST Joan Moreau via dovecot wrote: Hi Any idea on that ? Thank you On Sat, 2024-07-27 at 15:53 +0800, Joan Moreau via dovecot wrote: Hi I have that issue times to times Full case described properly here : https://github.com/grosjo/fts-xapian/issues/168 Can you help understand the root cause of that ? THank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: dovecot-indexer writting as root
Hi Any idea on that ? Thank you On Sat, 2024-07-27 at 15:53 +0800, Joan Moreau via dovecot wrote: > Hi > > I have that issue times to times > > Full case described properly here : > > https://github.com/grosjo/fts-xapian/issues/168 > > Can you help understand the root cause of that ? > > THank you > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
dovecot-indexer writting as root
Hi I have that issue times to times Full case described properly here : https://github.com/grosjo/fts-xapian/issues/168 Can you help understand the root cause of that ? THank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: dovecot.list.index.log
Hi Thanks for that Does the same goes for all dbox-Mails/dovecot.index* files ? On Sat, 2024-07-13 at 12:56 +0300, Aki Tuomi via dovecot wrote: > Should be safe, but run doveadm force-resync after. > > Aki > On 13/07/2024 08:30 EEST Joan Moreau via dovecot > wrote: > > > HI > > Is it safe to delete the file dovecot.list.index.log (as I am > still > struggling with using any protocol for network storage of the > emails > (dbox), and now dovecot complains that my dovecot.list.index.log > is > corrupted) > > Thank you > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
dovecot.list.index.log
HI Is it safe to delete the file dovecot.list.index.log (as I am still struggling with using any protocol for network storage of the emails (dbox), and now dovecot complains that my dovecot.list.index.log is corrupted) Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
dovecot imap_zlib
Hi I tested teh git version of dovecot. It seems the IMAP Compress plugin (imap_zlib) has disappeared. How to get it back ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Pread error over smb3
Moved from smb3 to sshfs to test same problem, only dovecot is complaining On Sat, 2024-07-06 at 21:04 +0800, Joan Moreau wrote: > archlinux x64 > > no selinux activated > > On Sat, 2024-07-06 at 13:53 +0200, John Fawcett via dovecot wrote: > > Hi Joan > > > > not sure what OS you're using, so just a guess: but maybe this is > > selinux related or something similar. When it's the OS providing > > the > > error code to dovecot, it's very unlikely to be anything in dovecot > > itself. > > > > On 06/07/2024 12:51, Joan Moreau via dovecot wrote: > > > No error on the error side > > > > > > the error occurs only with dovecot. all other soft do nto > > > complains > > > about the smb3 protocol > > > > > > I get also > > > Jul 6 10:49:45 gjserver dovecot[4220]: > > > lmtp(ad...@grosjo.net)<4355>: Error: > > > rename(/net/mails/grosjo.net/admin/storage/dovecot.map.index.tmp, > > > /net/mails/grosjo.net/admin/storage/dovecot.map.index) failed: > > > Permission denied > > > > > > > > > > > > On Tue, 2024-07-02 at 08:00 +0300, Aki Tuomi via dovecot wrote: > > > > Ok. But the error is coming from kernel, so not much Dovecot > > > > can do > > > > about it. Maybe try turning on some debugging in your server to > > > > see > > > > what is going on? > > > > > > > > Aki > > > > > > > > > On 02/07/2024 07:54 EEST Joan Moreau via dovecot > > > > > wrote: > > > > > > > > > > > > > > > Permissions on the server are very fine > > > > > > > > > > The problem occurs ONLY with dovecot > > > > > > > > > > > > > > > On Tue, 2024-07-02 at 07:49 +0300, Aki Tuomi wrote: > > > > > > > On 02/07/2024 02:05 EEST Joan Moreau via dovecot > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > I am trying to move my storage of email on a smb3 mounted > > > > > > > volume. > > > > > > > > > > > > > > I am getting the following error : > > > > > > > Error: pread(/net/.../storage/dovecot.map.index.log) > > > > > > > failed: > > > > > > > Permission > > > > > > > denied (euid=1004(mailusers) egid=12(mail) UNIX perms > > > > > > > appear ok > > > > > > > (ACL/MAC wrong?)) > > > > > > > > > > > > > > How to resolve that ? > > > > > > > > > > > > > > Thank you > > > > > > > > > > > > > This seems to be some kind of smb3 ACL problem, check > > > > > > permissions > > > > > > on > > > > > > the server? > > > > > > > > > > > > Aki > > > > > ___ > > > > > dovecot mailing list -- dovecot@dovecot.org > > > > > To unsubscribe send an email to dovecot-le...@dovecot.org > > > > ___ > > > > dovecot mailing list -- dovecot@dovecot.org > > > > To unsubscribe send an email to dovecot-le...@dovecot.org > > > ___ > > > dovecot mailing list -- dovecot@dovecot.org > > > To unsubscribe send an email to dovecot-le...@dovecot.org > > ___ > > dovecot mailing list -- dovecot@dovecot.org > > To unsubscribe send an email to dovecot-le...@dovecot.org > ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Pread error over smb3
archlinux x64 no selinux activated On Sat, 2024-07-06 at 13:53 +0200, John Fawcett via dovecot wrote: > Hi Joan > > not sure what OS you're using, so just a guess: but maybe this is > selinux related or something similar. When it's the OS providing the > error code to dovecot, it's very unlikely to be anything in dovecot > itself. > > On 06/07/2024 12:51, Joan Moreau via dovecot wrote: > > No error on the error side > > > > the error occurs only with dovecot. all other soft do nto complains > > about the smb3 protocol > > > > I get also > > Jul 6 10:49:45 gjserver dovecot[4220]: > > lmtp(ad...@grosjo.net)<4355>: Error: > > rename(/net/mails/grosjo.net/admin/storage/dovecot.map.index.tmp, > > /net/mails/grosjo.net/admin/storage/dovecot.map.index) failed: > > Permission denied > > > > > > > > On Tue, 2024-07-02 at 08:00 +0300, Aki Tuomi via dovecot wrote: > > > Ok. But the error is coming from kernel, so not much Dovecot can > > > do > > > about it. Maybe try turning on some debugging in your server to > > > see > > > what is going on? > > > > > > Aki > > > > > > > On 02/07/2024 07:54 EEST Joan Moreau via dovecot > > > > wrote: > > > > > > > > > > > > Permissions on the server are very fine > > > > > > > > The problem occurs ONLY with dovecot > > > > > > > > > > > > On Tue, 2024-07-02 at 07:49 +0300, Aki Tuomi wrote: > > > > > > On 02/07/2024 02:05 EEST Joan Moreau via dovecot > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > I am trying to move my storage of email on a smb3 mounted > > > > > > volume. > > > > > > > > > > > > I am getting the following error : > > > > > > Error: pread(/net/.../storage/dovecot.map.index.log) > > > > > > failed: > > > > > > Permission > > > > > > denied (euid=1004(mailusers) egid=12(mail) UNIX perms > > > > > > appear ok > > > > > > (ACL/MAC wrong?)) > > > > > > > > > > > > How to resolve that ? > > > > > > > > > > > > Thank you > > > > > > > > > > > This seems to be some kind of smb3 ACL problem, check > > > > > permissions > > > > > on > > > > > the server? > > > > > > > > > > Aki > > > > ___ > > > > dovecot mailing list -- dovecot@dovecot.org > > > > To unsubscribe send an email to dovecot-le...@dovecot.org > > > ___ > > > dovecot mailing list -- dovecot@dovecot.org > > > To unsubscribe send an email to dovecot-le...@dovecot.org > > ___ > > dovecot mailing list -- dovecot@dovecot.org > > To unsubscribe send an email to dovecot-le...@dovecot.org > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Pread error over smb3
No error on the error side the error occurs only with dovecot. all other soft do nto complains about the smb3 protocol I get also Jul 6 10:49:45 gjserver dovecot[4220]: lmtp(ad...@grosjo.net)<4355>: Error: rename(/net/mails/grosjo.net/admin/storage/dovecot.map.index.tmp, /net/mails/grosjo.net/admin/storage/dovecot.map.index) failed: Permission denied On Tue, 2024-07-02 at 08:00 +0300, Aki Tuomi via dovecot wrote: > Ok. But the error is coming from kernel, so not much Dovecot can do > about it. Maybe try turning on some debugging in your server to see > what is going on? > > Aki > > > On 02/07/2024 07:54 EEST Joan Moreau via dovecot > > wrote: > > > > > > Permissions on the server are very fine > > > > The problem occurs ONLY with dovecot > > > > > > On Tue, 2024-07-02 at 07:49 +0300, Aki Tuomi wrote: > > > > > > > On 02/07/2024 02:05 EEST Joan Moreau via dovecot > > > > wrote: > > > > > > > > > > > > Hi > > > > > > > > I am trying to move my storage of email on a smb3 mounted > > > > volume. > > > > > > > > I am getting the following error : > > > > Error: pread(/net/.../storage/dovecot.map.index.log) failed: > > > > Permission > > > > denied (euid=1004(mailusers) egid=12(mail) UNIX perms appear ok > > > > (ACL/MAC wrong?)) > > > > > > > > How to resolve that ? > > > > > > > > Thank you > > > > > > > > > > This seems to be some kind of smb3 ACL problem, check permissions > > > on > > > the server? > > > > > > Aki > > > > ___ > > dovecot mailing list -- dovecot@dovecot.org > > To unsubscribe send an email to dovecot-le...@dovecot.org > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Pread error over smb3
Permissions on the server are very fine The problem occurs ONLY with dovecot On Tue, 2024-07-02 at 07:49 +0300, Aki Tuomi wrote: > > > On 02/07/2024 02:05 EEST Joan Moreau via dovecot > > wrote: > > > > > > Hi > > > > I am trying to move my storage of email on a smb3 mounted volume. > > > > I am getting the following error : > > Error: pread(/net/.../storage/dovecot.map.index.log) failed: > > Permission > > denied (euid=1004(mailusers) egid=12(mail) UNIX perms appear ok > > (ACL/MAC wrong?)) > > > > How to resolve that ? > > > > Thank you > > > > This seems to be some kind of smb3 ACL problem, check permissions on > the server? > > Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Pread error over smb3
Hi I am trying to move my storage of email on a smb3 mounted volume. I am getting the following error : Error: pread(/net/.../storage/dovecot.map.index.log) failed: Permission denied (euid=1004(mailusers) egid=12(mail) UNIX perms appear ok (ACL/MAC wrong?)) How to resolve that ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Default databse script for a brand new install
Hi his is absolutely incredible The tables ARE NOT created automatically by Liquid. Whatever you are all repeating. and I sent already the log of it. So my question is : How to enable the creation of the tables, or just please share the sql statement to create those table and avoid the Liquid, so called "technology". Thank you so much in advance On 26 May 2024 22:57:31 Naphlin Peter wrote: A good starting place is https://www.udemy.com/course/liquibase/ Since you are paying your money for it, you will have all the right to question if they are junks; if you still fail to understand that is. Quite frankly the people on this thread have been more than nice and genuine to you. On Sun, 26 May 2024, 17:42 Joan Moreau, wrote: Really, are you a bunch of junks ? I am genuinely asking on creating initial tables, no ine is able to say "here is the actual process" On 26 May 2024 02:28:32 VICTOR MANUEL ROMERO RODRIGUEZ wrote: :) El sáb., 25 de mayo de 2024 7:21 a. m., Joan Moreau escribió: Hi No tables are created obsivously, and nothing in the docs related to creating the initial table If you have a pointer to the process of creating the tables, that would be very helpful instead of "read the doc" On 2024-05-15 22:32, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello Joan, Please read the docs. It uses Liquibase, this "technology" creates the tables, indexes and inserts some initial data, just make sure you have created the tenantS and the tenant databases. Regards El mié, 15 may 2024 a las 3:57, Joan Moreau () escribió: Ok but how to finally be able to /start/ the engine ? If no sql , then how to create the databases ? Should I enter manually each table ? This is kind of crazy, isnt'it ? On 5/14/24 00:44, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Apache Fineract doesn't have a SQL script, that SQL script that you are looking for is a DDL (Data Definition Language with database,table, fields,index creation, inserts etc ). Apache Fineract uses Liquibase and information about this concept/technology has been already shared. If you are looking for a USER like information and non from DEV/TECH, please take a look at https://mifosforge.jira.com/wiki/spaces/docs/pages/3559555073/Mifos+X+23.12.31+Installation+Guide+for+Windows+11+Ubuntu+22.04+Lts Regards El dom, 12 may 2024 a las 21:27, Joan Moreau () escribió: Hi What do you mean by "no sql" ? Database is MariadDB, it does need a sql statement to create the table isn´t it ? Finareact is git master scrip[t to launch is : #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=UTC export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_default export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance export JAVA_TOOL_OPTIONS="-Xmx1G -XX:MinRAMPercentage=25 -XX:MaxRAMPercentage=80 -XX:TieredStopAtLevel=1 -XX:+UseContainer Support -XX:+UseStringDeduplication --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.base/java.lan g=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=jav a.base/java.security=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.management/javax.management= ALL-UNNAMED --add-opens=java.naming/javax.naming=ALL-UNNAMED" java -Dloader.path=/data/microfinance/libs/ -jar fineract-provider.jar On 5/8/24 06:53, Ádám Sághy wrote: hi i am having trouble to understand what exactly the issue you are facing. there are NO sql files. Liquibase is used to set up and maintain the tables and the initial contents of the databases and these instructions are in XML files. i have already told you the directories where you can find them as well. fineract_tenants.m_adhoc' doesn't exist these exception kind of mean your configuration is incorrect due to the default tenant database should not be the fineract_tenants. Please kindly share the version of Fineract you are executing and the environment variables you are using (dont forget to change the real username and password and url, etc for dummy one before sharing) Regards, Adam export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Default databse script for a brand new install
Really, are you a bunch of junks ? I am genuinely asking on creating initial tables, no ine is able to say "here is the actual process" On 26 May 2024 02:28:32 VICTOR MANUEL ROMERO RODRIGUEZ wrote: :) El sáb., 25 de mayo de 2024 7:21 a. m., Joan Moreau escribió: Hi No tables are created obsivously, and nothing in the docs related to creating the initial table If you have a pointer to the process of creating the tables, that would be very helpful instead of "read the doc" On 2024-05-15 22:32, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello Joan, Please read the docs. It uses Liquibase, this "technology" creates the tables, indexes and inserts some initial data, just make sure you have created the tenantS and the tenant databases. Regards El mié, 15 may 2024 a las 3:57, Joan Moreau () escribió: Ok but how to finally be able to /start/ the engine ? If no sql , then how to create the databases ? Should I enter manually each table ? This is kind of crazy, isnt'it ? On 5/14/24 00:44, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Apache Fineract doesn't have a SQL script, that SQL script that you are looking for is a DDL (Data Definition Language with database,table, fields,index creation, inserts etc ). Apache Fineract uses Liquibase and information about this concept/technology has been already shared. If you are looking for a USER like information and non from DEV/TECH, please take a look at https://mifosforge.jira.com/wiki/spaces/docs/pages/3559555073/Mifos+X+23.12.31+Installation+Guide+for+Windows+11+Ubuntu+22.04+Lts Regards El dom, 12 may 2024 a las 21:27, Joan Moreau () escribió: Hi What do you mean by "no sql" ? Database is MariadDB, it does need a sql statement to create the table isn´t it ? Finareact is git master scrip[t to launch is : #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=UTC export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_default export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance export JAVA_TOOL_OPTIONS="-Xmx1G -XX:MinRAMPercentage=25 -XX:MaxRAMPercentage=80 -XX:TieredStopAtLevel=1 -XX:+UseContainer Support -XX:+UseStringDeduplication --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.base/java.lan g=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=jav a.base/java.security=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.management/javax.management= ALL-UNNAMED --add-opens=java.naming/javax.naming=ALL-UNNAMED" java -Dloader.path=/data/microfinance/libs/ -jar fineract-provider.jar On 5/8/24 06:53, Ádám Sághy wrote: hi i am having trouble to understand what exactly the issue you are facing. there are NO sql files. Liquibase is used to set up and maintain the tables and the initial contents of the databases and these instructions are in XML files. i have already told you the directories where you can find them as well. fineract_tenants.m_adhoc' doesn't exist these exception kind of mean your configuration is incorrect due to the default tenant database should not be the fineract_tenants. Please kindly share the version of Fineract you are executing and the environment variables you are using (dont forget to change the real username and password and url, etc for dummy one before sharing) Regards, Adam export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Default databse script for a brand new install
Hi No tables are created obsivously, and nothing in the docs related to creating the initial table If you have a pointer to the process of creating the tables, that would be very helpful instead of "read the doc" On 2024-05-15 22:32, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello Joan, Please read the docs. It uses Liquibase, this "technology" creates the tables, indexes and inserts some initial data, just make sure you have created the tenantS and the tenant databases. Regards El mié, 15 may 2024 a las 3:57, Joan Moreau () escribió: Ok but how to finally be able to /start/ the engine ? If no sql , then how to create the databases ? Should I enter manually each table ? This is kind of crazy, isnt'it ? On 5/14/24 00:44, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Apache Fineract doesn't have a SQL script, that SQL script that you are looking for is a DDL (Data Definition Language with database,table, fields,index creation, inserts etc ). Apache Fineract uses Liquibase and information about this concept/technology has been already shared. If you are looking for a USER like information and non from DEV/TECH, please take a look at https://mifosforge.jira.com/wiki/spaces/docs/pages/3559555073/Mifos+X+23.12.31+Installation+Guide+for+Windows+11+Ubuntu+22.04+Lts Regards El dom, 12 may 2024 a las 21:27, Joan Moreau () escribió: Hi What do you mean by "no sql" ? Database is MariadDB, it does need a sql statement to create the table isn´t it ? Finareact is git master scrip[t to launch is : #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=UTC export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_default export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance export JAVA_TOOL_OPTIONS="-Xmx1G -XX:MinRAMPercentage=25 -XX:MaxRAMPercentage=80 -XX:TieredStopAtLevel=1 -XX:+UseContainer Support -XX:+UseStringDeduplication --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.base/java.lan g=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.io [1]=ALL-UNNAMED --add-opens=jav a.base/java.security=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.management/javax.management= ALL-UNNAMED --add-opens=java.naming/javax.naming=ALL-UNNAMED" java -Dloader.path=/data/microfinance/libs/ -jar fineract-provider.jar On 5/8/24 06:53, Ádám Sághy wrote: hi i am having trouble to understand what exactly the issue you are facing. there are NO sql files. Liquibase is used to set up and maintain the tables and the initial contents of the databases and these instructions are in XML files. i have already told you the directories where you can find them as well. fineract_tenants.m_adhoc' doesn't exist these exception kind of mean your configuration is incorrect due to the default tenant database should not be the fineract_tenants. Please kindly share the version of Fineract you are executing and the environment variables you are using (dont forget to change the real username and password and url, etc for dummy one before sharing) Regards, Adam export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you Links: -- [1] http://java.io
Re: Default databse script for a brand new install
Ok but how to finally be able to /start/ the engine ? If no sql , then how to create the databases ? Should I enter manually each table ? This is kind of crazy, isnt'it ? On 5/14/24 00:44, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Apache Fineract doesn't have a SQL script, that SQL script that you are looking for is a DDL (Data Definition Language with database,table, fields,index creation, inserts etc ). Apache Fineract uses Liquibase and information about this concept/technology has been already shared. If you are looking for a USER like information and non from DEV/TECH, please take a look at https://mifosforge.jira.com/wiki/spaces/docs/pages/3559555073/Mifos+X+23.12.31+Installation+Guide+for+Windows+11+Ubuntu+22.04+Lts Regards El dom, 12 may 2024 a las 21:27, Joan Moreau () escribió: Hi What do you mean by "no sql" ? Database is MariadDB, it does need a sql statement to create the table isn´t it ? Finareact is git master scrip[t to launch is : #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=UTC export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_default export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance export JAVA_TOOL_OPTIONS="-Xmx1G -XX:MinRAMPercentage=25 -XX:MaxRAMPercentage=80 -XX:TieredStopAtLevel=1 -XX:+UseContainer Support -XX:+UseStringDeduplication --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.base/java.lan g=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.io <http://java.io>=ALL-UNNAMED --add-opens=jav a.base/java.security=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.management/javax.management= ALL-UNNAMED --add-opens=java.naming/javax.naming=ALL-UNNAMED" java -Dloader.path=/data/microfinance/libs/ -jar fineract-provider.jar On 5/8/24 06:53, Ádám Sághy wrote: hi i am having trouble to understand what exactly the issue you are facing. there are NO sql files. Liquibase is used to set up and maintain the tables and the initial contents of the databases and these instructions are in XML files. i have already told you the directories where you can find them as well. fineract_tenants.m_adhoc' doesn't exist these exception kind of mean your configuration is incorrect due to the default tenant database should not be the fineract_tenants. Please kindly share the version of Fineract you are executing and the environment variables you are using (dont forget to change the real username and password and url, etc for dummy one before sharing) Regards, Adam export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Default databse script for a brand new install
Hi What do you mean by "no sql" ? Database is MariadDB, it does need a sql statement to create the table isn´t it ? Finareact is git master scrip[t to launch is : #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=UTC export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_default export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance export JAVA_TOOL_OPTIONS="-Xmx1G -XX:MinRAMPercentage=25 -XX:MaxRAMPercentage=80 -XX:TieredStopAtLevel=1 -XX:+UseContainer Support -XX:+UseStringDeduplication --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.base/java.lan g=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=jav a.base/java.security=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.management/javax.management= ALL-UNNAMED --add-opens=java.naming/javax.naming=ALL-UNNAMED" java -Dloader.path=/data/microfinance/libs/ -jar fineract-provider.jar On 5/8/24 06:53, Ádám Sághy wrote: hi i am having trouble to understand what exactly the issue you are facing. there are NO sql files. Liquibase is used to set up and maintain the tables and the initial contents of the databases and these instructions are in XML files. i have already told you the directories where you can find them as well. fineract_tenants.m_adhoc' doesn't exist these exception kind of mean your configuration is incorrect due to the default tenant database should not be the fineract_tenants. Please kindly share the version of Fineract you are executing and the environment variables you are using (dont forget to change the real username and password and url, etc for dummy one before sharing) Regards, Adam export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Default databse script for a brand new install
Hi Adam thank you for your answer But I do not see any Sql script there. Where exactly is the initial schema to start Fineract ? I am surely not the only person trying just o start the engine Thank you in advance On 7 May 2024 22:56:14 Ádám Sághy wrote: hi you can find it multiple places :) fineract-provider/src/main/resources/db/changelog is the common one, - where “tenant-store” directory contains the liquibase scripts to build the tenant store tables and entries (fineract_tenants database) - where “tenant” directory contains the liquibase scripts to build the tenant tables (fineract_default database) Also we started to modularize the Fineract, so you might found additional liquibase scripts int the modules (like: fineract-loan/src/main/resources/db/changelog/tenant/module/loan) Liquibase is by default enabled, so it should be executed when you are running the application as jar or as bootRun, unless you are executing Fineract with "liquibase-only” profile or FINERACT_LIQUIBASE_ENABLED environment variable is set to FALSE. I hope it helps. The above details are applicable to the latest version of Fineract (apache/develop, 1.8.0 and 1.9.0 if i remember correctly ) Regards, Adam On 7 May 2024, at 16:47, Joan Moreau wrote: Hi Would really appreciate to know where to find the mariadb schema to upload before starting the process For now, it asks for tables that of course do bot exist as never created Thank you very much in advance On 6 May 2024 16:38:01 Joan Moreau wrote: I copied paste all the variables , fixing the _tenants into _default I still get to Caused by: java.sql.SQLSyntaxErrorException: (conn=385204) Table 'fineract_tenants.m_adhoc' doesn't exist at org.mariadb.jdbc.export.ExceptionFactory.createException(ExceptionFactory.java:289) at org.mariadb.jdbc.export.ExceptionFactory.create(ExceptionFactory.java:378) I really need to know where is the initial schema to create the required tables in MariaDB Thank you in advance On 5/6/24 16:19, Joan Moreau wrote: You send me a link to XML files I just need (a) the actual (real ones !!! not some approximate names) variable to set (b) where is the damn default schema to create the initial tables On 2024-05-06 16:09, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello Joan, Apache Fineract uses Liquibase, take a look at: https://github.com/apache/fineract/tree/develop/fineract-provider/src/main/resources/db/changelog https://docs.liquibase.com/home.html Apache Fineract variables for MariaDB on Docker are the same as the one used for Native installations, just try them. Please read files included in the PR that I have shared, there is a startup script on it. Regards El lun, 6 may 2024 a las 2:04, Joan Moreau () escribió: Note: I am not using docker but a normal server with a normal MariaDB (serving multiple applications) On 5/6/24 16:02, Joan Moreau wrote: Also, the variable you mentioned do not fit the variables available in the source code In addition to teh start-up schema, where to have the actual variable to set to start Fineract ? On 5/6/24 16:00, Joan Moreau wrote: Thank you but that does not answer the question: - Where to find the initial database schema to create the initial tables ? Thank you very much On 5/5/24 10:20, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello, 1. No, you can use any user that you require (root, fineract, mariadbuser, customeuser, exampleuser... etc). 2. Database names are defined in these variables (please notices that there is a difference tenantS and tenant ) : FINERACT_TENANTS_DB_NAME - For tenants database FINERACT_TENANT_DEFAULT_DB_NAME - for the default database 3. You are setting the values of the database in a mixed way, you have set variables for the default tenant as tenants and tenants as default database. By the way if you are using the develop branch or previous version (since 1.6) mariaDB is the supported database (also PostgreSQL since version 1.7.0), if you use MySQL you could face some issues. If you require to use MariaDB check this docker compose as reference: https://github.com/apache/fineract/blob/develop/docker-compose.yml And these are the variables linked to that docker compose. https://github.com/apache/fineract/blob/develop/config/docker/env/fineract.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-common.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-mariadb.env In this PR you can take a look how to start the Apache Fineract jar file https://github.com/apache/fineract/pull/3879/files java -jar fineract-provider-*.jar -Duser.home=/tmp -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Djava.security.egd=file:/dev/./urandom Best regards Victor El sáb, 4 may 2024 a las 8:55, Joan Moreau () escribió: Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create data
Re: Default databse script for a brand new install
Hi Would really appreciate to know where to find the mariadb schema to upload before starting the process For now, it asks for tables that of course do bot exist as never created Thank you very much in advance On 6 May 2024 16:38:01 Joan Moreau wrote: I copied paste all the variables , fixing the _tenants into _default I still get to Caused by: java.sql.SQLSyntaxErrorException: (conn=385204) Table 'fineract_tenants.m_adhoc' doesn't exist at org.mariadb.jdbc.export.ExceptionFactory.createException(ExceptionFactory.java:289) at org.mariadb.jdbc.export.ExceptionFactory.create(ExceptionFactory.java:378) I really need to know where is the initial schema to create the required tables in MariaDB Thank you in advance On 5/6/24 16:19, Joan Moreau wrote: You send me a link to XML files I just need (a) the actual (real ones !!! not some approximate names) variable to set (b) where is the damn default schema to create the initial tables On 2024-05-06 16:09, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello Joan, Apache Fineract uses Liquibase, take a look at: https://github.com/apache/fineract/tree/develop/fineract-provider/src/main/resources/db/changelog https://docs.liquibase.com/home.html Apache Fineract variables for MariaDB on Docker are the same as the one used for Native installations, just try them. Please read files included in the PR that I have shared, there is a startup script on it. Regards El lun, 6 may 2024 a las 2:04, Joan Moreau () escribió: Note: I am not using docker but a normal server with a normal MariaDB (serving multiple applications) On 5/6/24 16:02, Joan Moreau wrote: Also, the variable you mentioned do not fit the variables available in the source code In addition to teh start-up schema, where to have the actual variable to set to start Fineract ? On 5/6/24 16:00, Joan Moreau wrote: Thank you but that does not answer the question: - Where to find the initial database schema to create the initial tables ? Thank you very much On 5/5/24 10:20, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello, 1. No, you can use any user that you require (root, fineract, mariadbuser, customeuser, exampleuser... etc). 2. Database names are defined in these variables (please notices that there is a difference tenantS and tenant ) : FINERACT_TENANTS_DB_NAME - For tenants database FINERACT_TENANT_DEFAULT_DB_NAME - for the default database3. You are setting the values of the database in a mixed way, you have set variables for the default tenant as tenants and tenants as default database. By the way if you are using the develop branch or previous version (since 1.6) mariaDB is the supported database (also PostgreSQL since version 1.7.0), if you use MySQL you could face some issues. If you require to use MariaDB check this docker compose as reference: https://github.com/apache/fineract/blob/develop/docker-compose.yml And these are the variables linked to that docker compose. https://github.com/apache/fineract/blob/develop/config/docker/env/fineract.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-common.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-mariadb.env In this PR you can take a look how to start the Apache Fineract jar file https://github.com/apache/fineract/pull/3879/files java -jar fineract-provider-*.jar -Duser.home=/tmp -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Djava.security.egd=file:/dev/./urandom Best regards Victor El sáb, 4 may 2024 a las 8:55, Joan Moreau () escribió: Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create databases as root (?) 2 - It seems databases MUST be named fineract_tenants and fineract_default. How to change that behavior ? 3 - When I put the database user to have rights on those 2 databases, it ends-up with an error : liquibase.exception.DatabaseException: (conn=7381) Table 'fineract_tenants.m_adhoc' doesn't exist [Failed SQL: (1146) ALTER TABLE `fineract_tenants`.`m_adhoc` CHANGE `IsActive` `is_active` TINYINT] How to initiate properly a brand new install ? I have the following script to start fineract: #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=GMT+0 export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_tenants export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USE
Re: Default databse script for a brand new install
I copied paste all the variables , fixing the _tenants into _default I still get to Caused by: java.sql.SQLSyntaxErrorException: (conn=385204) Table 'fineract_tenants.m_adhoc' doesn't exist at org.mariadb.jdbc.export.ExceptionFactory.createException(ExceptionFactory.java:289) at org.mariadb.jdbc.export.ExceptionFactory.create(ExceptionFactory.java:378) I really need to know where is the initial schema to create the required tables in MariaDB Thank you in advance On 5/6/24 16:19, Joan Moreau wrote: You send me a link to XML files I just need (a) the actual (real ones !!! not some approximate names) variable to set (b) where is the damn default schema to create the initial tables On 2024-05-06 16:09, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello Joan, Apache Fineract uses Liquibase, take a look at: https://github.com/apache/fineract/tree/develop/fineract-provider/src/main/resources/db/changelog https://docs.liquibase.com/home.html Apache Fineract variables for MariaDB on Docker are the same as the one used for Native installations, just try them. Please read files included in the PR that I have shared, there is a startup script on it. Regards El lun, 6 may 2024 a las 2:04, Joan Moreau () escribió: Note: I am not using docker but a normal server with a normal MariaDB (serving multiple applications) On 5/6/24 16:02, Joan Moreau wrote: Also, the variable you mentioned do not fit the variables available in the source code In addition to teh start-up schema, where to have the actual variable to set to start Fineract ? On 5/6/24 16:00, Joan Moreau wrote: Thank you but that does not answer the question: - Where to find the initial database schema to create the initial tables ? Thank you very much On 5/5/24 10:20, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello, 1. No, you can use any user that you require (root, fineract, mariadbuser, customeuser, exampleuser... etc). 2. Database names are defined in these variables (please notices that there is a difference tenantS and tenant ) : FINERACT_TENANTS_DB_NAME - For tenants database FINERACT_TENANT_DEFAULT_DB_NAME - for the default database 3. You are setting the values of the database in a mixed way, you have set variables for the default tenant as tenants and tenants as default database. By the way if you are using the develop branch or previous version (since 1.6) mariaDB is the supported database (also PostgreSQL since version 1.7.0), if you use MySQL you could face some issues. If you require to use MariaDB check this docker compose as reference: https://github.com/apache/fineract/blob/develop/docker-compose.yml And these are the variables linked to that docker compose. https://github.com/apache/fineract/blob/develop/config/docker/env/fineract.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-common.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-mariadb.env In this PR you can take a look how to start the Apache Fineract jar file https://github.com/apache/fineract/pull/3879/files java -jar fineract-provider-*.jar -Duser.home=/tmp -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Djava.security.egd=file:/dev/./urandom Best regards Victor El sáb, 4 may 2024 a las 8:55, Joan Moreau () escribió: Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create databases as root (?) 2 - It seems databases MUST be named fineract_tenants and fineract_default. How to change that behavior ? 3 - When I put the database user to have rights on those 2 databases, it ends-up with an error : liquibase.exception.DatabaseException: (conn=7381) Table 'fineract_tenants.m_adhoc' doesn't exist [Failed SQL: (1146) ALTER TABLE `fineract_tenants`.`m_adhoc` CHANGE `IsActive` `is_active` TINYINT] How to initiate properly a brand new install ? I have the following script to start fineract: #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=GMT+0 export FINERACT_DE
Re: Default databse script for a brand new install
You send me a link to XML files I just need (a) the actual (real ones !!! not some approximate names) variable to set (b) where is the damn default schema to create the initial tables On 2024-05-06 16:09, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello Joan, Apache Fineract uses Liquibase, take a look at: https://github.com/apache/fineract/tree/develop/fineract-provider/src/main/resources/db/changelog https://docs.liquibase.com/home.html Apache Fineract variables for MariaDB on Docker are the same as the one used for Native installations, just try them. Please read files included in the PR that I have shared, there is a startup script on it. Regards El lun, 6 may 2024 a las 2:04, Joan Moreau () escribió: Note: I am not using docker but a normal server with a normal MariaDB (serving multiple applications) On 5/6/24 16:02, Joan Moreau wrote: Also, the variable you mentioned do not fit the variables available in the source code In addition to teh start-up schema, where to have the actual variable to set to start Fineract ? On 5/6/24 16:00, Joan Moreau wrote: Thank you but that does not answer the question: - Where to find the initial database schema to create the initial tables ? Thank you very much On 5/5/24 10:20, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello, 1. No, you can use any user that you require (root, fineract, mariadbuser, customeuser, exampleuser... etc). 2. Database names are defined in these variables (please notices that there is a difference tenantS and tenant ) : FINERACT_TENANTS_DB_NAME - For tenants database FINERACT_TENANT_DEFAULT_DB_NAME - for the default database 3. You are setting the values of the database in a mixed way, you have set variables for the default tenant as tenants and tenants as default database. By the way if you are using the develop branch or previous version (since 1.6) mariaDB is the supported database (also PostgreSQL since version 1.7.0), if you use MySQL you could face some issues. If you require to use MariaDB check this docker compose as reference: https://github.com/apache/fineract/blob/develop/docker-compose.yml And these are the variables linked to that docker compose. https://github.com/apache/fineract/blob/develop/config/docker/env/fineract.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-common.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-mariadb.env In this PR you can take a look how to start the Apache Fineract jar file https://github.com/apache/fineract/pull/3879/files java -jar fineract-provider-*.jar -Duser.home=/tmp -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Djava.security.egd=file:/dev/./urandom Best regards Victor El sáb, 4 may 2024 a las 8:55, Joan Moreau () escribió: Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create databases as root (?) 2 - It seems databases MUST be named fineract_tenants and fineract_default. How to change that behavior ? 3 - When I put the database user to have rights on those 2 databases, it ends-up with an error : liquibase.exception.DatabaseException: (conn=7381) Table 'fineract_tenants.m_adhoc' doesn't exist [Failed SQL: (1146) ALTER TABLE `fineract_tenants`.`m_adhoc` CHANGE `IsActive` `is_active` TINYINT] How to initiate properly a brand new install ? I have the following script to start fineract: #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=GMT+0 export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_tenants export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Default databse script for a brand new install
The easy way would be just to know (1) What variable to set (2) with which values for a normal user (no docker, no fancy stuff, just a Unix server and a MariadDB) (3) where is that damn mariadb schema to create to enable the app to start On 5/6/24 16:04, Joan Moreau wrote: Note: I am not using docker but a normal server with a normal MariaDB (serving multiple applications) On 5/6/24 16:02, Joan Moreau wrote: Also, the variable you mentioned do not fit the variables available in the source code In addition to teh start-up schema, where to have the actual variable to set to start Fineract ? On 5/6/24 16:00, Joan Moreau wrote: Thank you but that does not answer the question: - Where to find the initial database schema to create the initial tables ? Thank you very much On 5/5/24 10:20, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello, 1. No, you can use any user that you require (root, fineract, mariadbuser, customeuser, exampleuser... etc). 2. Database names are defined in these variables (please notices that there is a difference tenantS and tenant ) : FINERACT_TENANTS_DB_NAME - For tenants database FINERACT_TENANT_DEFAULT_DB_NAME - for the default database 3. You are setting the values of the database in a mixed way, you have set variables for the default tenant as tenants and tenants as default database. By the way if you are using the develop branch or previous version (since 1.6) mariaDB is the supported database (also PostgreSQL since version 1.7.0), if you use MySQL you could face some issues. If you require to use MariaDB check this docker compose as reference: https://github.com/apache/fineract/blob/develop/docker-compose.yml And these are the variables linked to that docker compose. https://github.com/apache/fineract/blob/develop/config/docker/env/fineract.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-common.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-mariadb.env In this PR you can take a look how to start the Apache Fineract jar file https://github.com/apache/fineract/pull/3879/files java -jar fineract-provider-*.jar -Duser.home=/tmp -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Djava.security.egd=file:/dev/./urandom Best regards Victor El sáb, 4 may 2024 a las 8:55, Joan Moreau () escribió: Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create databases as root (?) 2 - It seems databases MUST be named fineract_tenants and fineract_default. How to change that behavior ? 3 - When I put the database user to have rights on those 2 databases, it ends-up with an error : liquibase.exception.DatabaseException: (conn=7381) Table 'fineract_tenants.m_adhoc' doesn't exist [Failed SQL: (1146) ALTER TABLE `fineract_tenants`.`m_adhoc` CHANGE `IsActive` `is_active` TINYINT] How to initiate properly a brand new install ? I have the following script to start fineract: #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=GMT+0 export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_tenants export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Default databse script for a brand new install
Note: I am not using docker but a normal server with a normal MariaDB (serving multiple applications) On 5/6/24 16:02, Joan Moreau wrote: Also, the variable you mentioned do not fit the variables available in the source code In addition to teh start-up schema, where to have the actual variable to set to start Fineract ? On 5/6/24 16:00, Joan Moreau wrote: Thank you but that does not answer the question: - Where to find the initial database schema to create the initial tables ? Thank you very much On 5/5/24 10:20, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello, 1. No, you can use any user that you require (root, fineract, mariadbuser, customeuser, exampleuser... etc). 2. Database names are defined in these variables (please notices that there is a difference tenantS and tenant ) : FINERACT_TENANTS_DB_NAME - For tenants database FINERACT_TENANT_DEFAULT_DB_NAME - for the default database 3. You are setting the values of the database in a mixed way, you have set variables for the default tenant as tenants and tenants as default database. By the way if you are using the develop branch or previous version (since 1.6) mariaDB is the supported database (also PostgreSQL since version 1.7.0), if you use MySQL you could face some issues. If you require to use MariaDB check this docker compose as reference: https://github.com/apache/fineract/blob/develop/docker-compose.yml And these are the variables linked to that docker compose. https://github.com/apache/fineract/blob/develop/config/docker/env/fineract.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-common.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-mariadb.env In this PR you can take a look how to start the Apache Fineract jar file https://github.com/apache/fineract/pull/3879/files java -jar fineract-provider-*.jar -Duser.home=/tmp -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Djava.security.egd=file:/dev/./urandom Best regards Victor El sáb, 4 may 2024 a las 8:55, Joan Moreau () escribió: Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create databases as root (?) 2 - It seems databases MUST be named fineract_tenants and fineract_default. How to change that behavior ? 3 - When I put the database user to have rights on those 2 databases, it ends-up with an error : liquibase.exception.DatabaseException: (conn=7381) Table 'fineract_tenants.m_adhoc' doesn't exist [Failed SQL: (1146) ALTER TABLE `fineract_tenants`.`m_adhoc` CHANGE `IsActive` `is_active` TINYINT] How to initiate properly a brand new install ? I have the following script to start fineract: #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=GMT+0 export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_tenants export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Default databse script for a brand new install
Also, the variable you mentioned do not fit the variables available in the source code In addition to teh start-up schema, where to have the actual variable to set to start Fineract ? On 5/6/24 16:00, Joan Moreau wrote: Thank you but that does not answer the question: - Where to find the initial database schema to create the initial tables ? Thank you very much On 5/5/24 10:20, VICTOR MANUEL ROMERO RODRIGUEZ wrote: Hello, 1. No, you can use any user that you require (root, fineract, mariadbuser, customeuser, exampleuser... etc). 2. Database names are defined in these variables (please notices that there is a difference tenantS and tenant ) : FINERACT_TENANTS_DB_NAME - For tenants database FINERACT_TENANT_DEFAULT_DB_NAME - for the default database 3. You are setting the values of the database in a mixed way, you have set variables for the default tenant as tenants and tenants as default database. By the way if you are using the develop branch or previous version (since 1.6) mariaDB is the supported database (also PostgreSQL since version 1.7.0), if you use MySQL you could face some issues. If you require to use MariaDB check this docker compose as reference: https://github.com/apache/fineract/blob/develop/docker-compose.yml And these are the variables linked to that docker compose. https://github.com/apache/fineract/blob/develop/config/docker/env/fineract.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-common.env https://github.com/apache/fineract/blob/develop/config/docker/env/fineract-mariadb.env In this PR you can take a look how to start the Apache Fineract jar file https://github.com/apache/fineract/pull/3879/files java -jar fineract-provider-*.jar -Duser.home=/tmp -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Djava.security.egd=file:/dev/./urandom Best regards Victor El sáb, 4 may 2024 a las 8:55, Joan Moreau () escribió: Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create databases as root (?) 2 - It seems databases MUST be named fineract_tenants and fineract_default. How to change that behavior ? 3 - When I put the database user to have rights on those 2 databases, it ends-up with an error : liquibase.exception.DatabaseException: (conn=7381) Table 'fineract_tenants.m_adhoc' doesn't exist [Failed SQL: (1146) ALTER TABLE `fineract_tenants`.`m_adhoc` CHANGE `IsActive` `is_active` TINYINT] How to initiate properly a brand new install ? I have the following script to start fineract: #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=GMT+0 export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_tenants export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Default databse script for a brand new install
Hi Where is stipulated the default schema of the mysql database ? I face 3 issues 1 - The software seems to need to create databases as root (?) 2 - It seems databases MUST be named fineract_tenants and fineract_default. How to change that behavior ? 3 - When I put the database user to have rights on those 2 databases, it ends-up with an error : liquibase.exception.DatabaseException: (conn=7381) Table 'fineract_tenants.m_adhoc' doesn't exist [Failed SQL: (1146) ALTER TABLE `fineract_tenants`.`m_adhoc` CHANGE `IsActive` `is_active` TINYINT] How to initiate properly a brand new install ? I have the following script to start fineract: #!/bin/bash cd /data/microfinance export FINERACT_HIKARI_USERNAME=fineract export FINERACT_HIKARI_PASSWORD=mypassword export FINERACT_SERVER_SSL_ENABLED=false export FINERACT_SERVER_PORT=8080 export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver export FINERACT_HIKARI_JDBC_URL="jdbc:mariadb://localhost:3306/fineract_tenants?serverTimezone=UTC&useLegacyDatetimeCode=f alse&sessionVariables=time_zone=UTC" export FINERACT_DEFAULT_TENANTDB_PORT=3306 export FINERACT_DEFAULT_TENANTDB_UID=fineract export FINERACT_DEFAULT_TENANTDB_TIMEZONE=GMT+0 export FINERACT_DEFAULT_TENANTDB_HOSTNAME=localhost export FINERACT_DEFAULT_TENANTDB_NAME=fineract_tenants export FINERACT_DEFAULT_TENANTDB_PWD=mypassword export FINERACT_USER=fineract export FINERACT_GROUP=fineract export FINERACT_DEFAULT_TENANTDB_DESCRIPTION=GJ_Microfinance java -Dloader.path=/data/mmicrofinance/libs/ -jar fineract-provider.jar Thank you
Re: Sieve not getting recompiled
I changed it to the following to stick to the doc sieve = file:/mails/%d/%n/sieve/ sieve_after = file:/mails/sieve/after.sieve sieve_default = file:/mails/sieve/before.sieve sieve_before = file:/mails/sieve/before.sieve Still no scripts are compiled/executed (and it was working fine before !) On 2024-04-21 09:21, Joan Moreau wrote: Hi I have sieve = /mails/%d/%n/sieve/roundcube.sieve sieve_after = /mails/sieve/after.sieve sieve_before = /mails/sieve/before.sieve sieve_dir = /mails/%d/%n/sieve/ sieve_global_dir = /mails/sieve/ But sieve scripts are not compiled and not executed It was working until I removed the setting "sieve_global_path" Something I dont understand ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Sieve not getting recompiled
Hi I have sieve = /mails/%d/%n/sieve/roundcube.sieve sieve_after = /mails/sieve/after.sieve sieve_before = /mails/sieve/before.sieve sieve_dir = /mails/%d/%n/sieve/ sieve_global_dir = /mails/sieve/ But sieve scripts are not compiled and not executed It was working until I removed the setting "sieve_global_path" Something I dont understand ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: exfat not supported ?
That resolve the fisrt bug but I get now : Error: link(/xxx/dovecot.list.index.log, /xxx/dovecot.list.index.log.2) failed: Operation not permitted On 2024-04-21 02:02, Aki Tuomi via dovecot wrote: Try setting lock_method = dotlock Aki On 20/04/2024 15:32 EEST Joan Moreau via dovecot wrote: I tried and get the following: Error: Couldn't create mailbox list lock /xxx/mailboxes.lock: file_create_locked(/xxx/mailboxes.lock) failed: link(/xxx/mailboxes.locka94f3757318b0b90, /xxx/mailboxes.lock) failed: Operation not permitted On 2024-04-20 17:39, Aki Tuomi via dovecot wrote: On 20/04/2024 12:27 EEST Joan Moreau via dovecot wrote: Hi Would placing my storage on a exfat partition work ? If no, why ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org I can't see any reason why not. As long as it behaves like POSIX filesystem. Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: exfat not supported ?
I tried and get the following: Error: Couldn't create mailbox list lock /xxx/mailboxes.lock: file_create_locked(/xxx/mailboxes.lock) failed: link(/xxx/mailboxes.locka94f3757318b0b90, /xxx/mailboxes.lock) failed: Operation not permitted On 2024-04-20 17:39, Aki Tuomi via dovecot wrote: On 20/04/2024 12:27 EEST Joan Moreau via dovecot wrote: Hi Would placing my storage on a exfat partition work ? If no, why ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org I can't see any reason why not. As long as it behaves like POSIX filesystem. Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
thread->detach() creates confusion of dovecot
Hi When I try to "detach" (https://en.cppreference.com/w/cpp/thread/thread/detach) a thread running inside a plugin, it seems the core dovecot has some influence on that , tries to close this for some unknown reason and usually ends up crashing What is the cause of this ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
exfat not supported ?
Hi Would placing my storage on a exfat partition work ? If no, why ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Separate index get dovecot lost
> To do that kind of a change, mailbox migration is required. Meaning ? ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Separate index get dovecot lost
Hi I have large number of email (~TB) and want to put the index in a separate, rapid drive Initially, I have mail_location = mdbox:/files/mail/%d/%n If I put mail_location = mdbox:/files/mail/%d/%n:INDEX=/data/mailindexes/%d/%n then dovecot gets totally lost and tries to reach mailboxes content and tree from the INDEX location instead of the original location What is wrong ? Thank you ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: [EXT] Re: How to get a memory pointer in the core process
Thanks Eduardo I am trying to avoid closing/ reopening a file pointer to the exact same file between each call to the plugin On 14 March 2024 20:08:37 Eduardo M KALINOWSKI via dovecot wrote: On 14/03/2024 02:49, Joan Moreau via dovecot wrote: No, you don´t understand There is a core process (/usr/bin/dovecot) running all the time. So I want to allocate a memory block, the core process keep it and it is retrievable by the pluging when laded again At exit of /usr/bin/dovecot, it just does a "delete()" of the said allocation While I cannot help you with plugin writing or dovecot internals, this does seem like an example of the XY problem[0]. Perhaps if you provide a high level description of what you're attempting to do someone might come up with a way to achieve that. [0] https://en.wikipedia.org/wiki/XY_problem -- Eduardo M KALINOWSKI edua...@kalinowski.com.br ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: [EXT] Re: How to get a memory pointer in the core process
No, you don´t understand
There is a core process (/usr/bin/dovecot) running all the time. So I want to
allocate a memory block, the core process keep it and it is retrievable by the
pluging when laded again
At exit of /usr/bin/dovecot, it just does a "delete()" of the said allocation
On 2024-03-14 13:25, Aki Tuomi via dovecot wrote:
Hi!
Sorry but that's just not possible, ther is no "core" where to create
such object. There is no "dovecot" where to store things.
When user logs in, dovecot executes /usr/libexec/dovecot/imap and
transfers the connection fd there. then plugins and stuff are loaded,
and the user does what he does, and then plugins and stuff are
unloaded and process exists and no longer exists in memory.
You are clearly asking about memory persistence between sessions, and
this can be done with
a) services (internal or external), such as redis, sql, or something
else
b) storing things to disk
Aki
On 13/03/2024 18:45 EET Joan Moreau via dovecot
wrote:
No, I am not referring to that
I want to create an object at first call in memory
that object would be retrievable at second and furthers
calls of the
plugin, as long as dovecot is running
On 2024-03-13 16:29, Aki Tuomi via dovecot wrote:
Not really no. You should use e.g. dict inteface
for storing this kind
of stateful data. When deinit is called the
calling core process will
likely die too.
Aki
On 13/03/2024 10:19 EET Joan Moreau
wrote:
Keep a pointer in memory retrievable each time a
plugin is called
So the plugin keep the memory, not has to restart
everything at each
call
On 12 March 2024 08:53:38 Aki Tuomi via dovecot
wrote:
On 11/03/2024 10:42 EET Joan Moreau
wrote:
Hi
Is it possible, from a plugin perspective, to
create and recover a
pointer in the core process (i.e. memory not lost
between 2 calls to
the plugin, even after the "deinit" of the
plugin" ) ?
Thanks
Hi Joan!
May I ask what you are attempting to achieve in
more detail?
Aki
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-
le...@dovecot.org
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-
leave@dovecot.orgNo, I am not referring to that
I want to create an object at first call in memory
that object would be retrievable at second and furthers
calls of the plugin, as
long as dovecot is running
On 2024-03-13 16:29, Aki Tuomi via dovecot wrote:
Not really no. You should use e.g. dict inteface for
storing this
kind of stateful data. When deinit is called the
calling core process
will likely die too.
Aki
On 13/03/2024 10:19 EET Joan Moreau
wrote:
Keep a pointer in memory retrievable each time a
plugin is
called
So the plugin keep the memory, not has to restart
everything at each call
On 12 March 2024 08:53:38 Aki Tuomi via dovecot
wrote:
On 11/03/2024 10:42 EET Joan Moreau
wrote:
Hi
Is it possible, from a plugin
perspective, to create and recover a
pointer in the core process (i.e.
memory not lost between 2 calls to the
plugin, even after the "deinit" of the
plugin" ) ?
Thanks
Hi Joan!
May I ask what you are attempting to achieve
in
more detail?
Aki
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-
le...@dovecot.org
_
Re: [EXT] Re: How to get a memory pointer in the core process
No, I am not referring to that I want to create an object at first call in memory that object would be retrievable at second and furthers calls of the plugin, as long as dovecot is running On 2024-03-13 16:29, Aki Tuomi via dovecot wrote: Not really no. You should use e.g. dict inteface for storing this kind of stateful data. When deinit is called the calling core process will likely die too. Aki On 13/03/2024 10:19 EET Joan Moreau wrote: Keep a pointer in memory retrievable each time a plugin is called So the plugin keep the memory, not has to restart everything at each call On 12 March 2024 08:53:38 Aki Tuomi via dovecot wrote: On 11/03/2024 10:42 EET Joan Moreau wrote: Hi Is it possible, from a plugin perspective, to create and recover a pointer in the core process (i.e. memory not lost between 2 calls to the plugin, even after the "deinit" of the plugin" ) ? Thanks Hi Joan! May I ask what you are attempting to achieve in more detail? Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot- le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: How to get a memory pointer in the core process
Keep a pointer in memory retrievable each time a plugin is called So the plugin keep the memory, not has to restart everything at each call On 12 March 2024 08:53:38 Aki Tuomi via dovecot wrote: On 11/03/2024 10:42 EET Joan Moreau wrote: Hi Is it possible, from a plugin perspective, to create and recover a pointer in the core process (i.e. memory not lost between 2 calls to the plugin, even after the "deinit" of the plugin" ) ? Thanks Hi Joan! May I ask what you are attempting to achieve in more detail? Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
How to get a memory pointer in the core process
Hi Is it possible, from a plugin perspective, to create and recover a pointer in the core process (i.e. memory not lost between 2 calls to the plugin, even after the "deinit" of the plugin" ) ? Thanks ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Problem with the dovecot-fts-xapian package.
@Bob : The package has been recompiled against the new version of Dovecot. Hope it works now @Aki : It would be nice to have all plugins included in the source code for major releases (with a simple rule that non-maintained packages are removed), including Pigeonhole, FTS plugins, and many other existing plugins from all over the world On 2021-09-12 13:54, Aki Tuomi wrote: On 12/09/2021 15:12 Bob Marcan wrote: On Sun, 12 Sep 2021 11:36:46 +0100 Joan Moreau wrote: This is where I am for now : https://koji.fedoraproject.org/koji/packageinfo?packageID=34417 Probably, I should wait for Fedora batch programs to push that into main rep On 2021-09-12 11:18, Joan Moreau wrote: Hi Bob, I am trying to achieve that. But do you know the process of pushing an update as a maintainer, in > fedore repositories ? Thank you On 2021-09-12 11:02, Bob Marcan wrote: On Sun, 12 Sep 2021 09:45:35 +0100 Joan Moreau wrote: Thank you for notice. What is the process to rebuild the package with recent dovecot, as > (instead of existing 1.4.12-1) ? There are no (yet) 1.4.12-2 in updates-testing or > updates-testing-modular repository. Should i'll wait for update? BR, Bob Got the new version and there is no more API mismatch. It's not so important for me, since i'm retired and i'm running this on my home computer. But i think it needs more support from te dovecot group. There a lot file protection issues nad lack of documentation on dovecot side. BR, Bob Hi Bob, Dovecot does not maintain either the packages for fedora. These are maintained by Fedora Project. Also we do not maintain or document the dovecot-fts-xapian plugin, since it's 3rd party plugin. It's maintained by Joan Moreau. Kind regards, Aki
Re: Problem with the dovecot-fts-xapian package.
Thank you for notice. What is the process to rebuild the package with recent dovecot, as 1.4.12-2 (instead of existing 1.4.12-1) ? On 2021-09-12 07:21, Bob Marcan wrote: Problem with the dovecot-fts-xapian package. Fedora 34 with latest updates. dovecot-2.3.16-1.fc34.x86_64 dovecot-fts-xapian-1.4.12-1.fc34.x86_64 [root@smicro conf.d]# systemctl restart dovecot [root@smicro conf.d]# doveadm index -A \* Fatal: Couldn't load required plugin /usr/lib64/dovecot/lib21_fts_xapian_plugin.so: Module is for different ABI version 2.3.ABIv15(2.3.15) (we have 2.3.ABIv16(2.3.16)) BR, Bob
Re: Duplicate plugins - FTS Xapian
Just for clarity, Open-Xchange has not written any xapian plugin whatsoever. Yes but the doc says that Open Xchaneg "supports" one over the other. Honestly, I am doing this over my free time, begin very reactive to user requests, and have this confirmed by Debian, Archlinux and now Fedora in their core packages This is not very encouraging despite all the efforts achieved.
Duplicate plugins - FTS Xapian
Hi There seems to be 2 plugins doing the same thins - https://github.com/slusarz/dovecot-fts-flatcurve/ - https://github.com/grosjo/fts-xapian/ (mine) Both are in the doc of dovecot https://doc.dovecot.org/configuration_manual/fts/ I am currently working hard to push it to RPM package, and plugin is already approved by ArchLinux and Debian Isn't there double work here ? Thanks JM
Re: New RPM submission (dovecot-fts-xapian)
Thank you Ankur Happy to move forward with your help. On 2021-08-22 12:52, Ankur Sinha wrote: On Sat, Aug 21, 2021 11:31:32 +0200, Vitaly Zaitsev via devel wrote: On 21/08/2021 10:57, Ankur Sinha wrote: So, if we can do anything to make it easier for developers to just maintain their one or two tools for the Fedora community, that'll be good. And we will get a lot of low-quality packages with bundled a lot of libraries, ignoring Fedora build flags, guidelines, etc. Look at Flathub for example. An example of what, though? Flathub's system/pipeline/foundations/community is very different from ours. So using it as an example to project what may happen in Fedora in the future if these negative assumptions about prospective maintainers came true is a bit of a leap for me. :) Bundling has not been forbidden in Fedora for a while, and I haven't noticed package maintainers bundling bits everywhere now as a result. If that does become a problem, I'm sure we'll deal with it and evolve our guidelines accordingly. Anyway, in this particular case, I'm happy to sponsor Joan. All our work in Fedora is done in the open, so if anyone does have any concerns, they can inform me---as they'd do with any of the folks I (we) sponsor. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission (dovecot-fts-xapian)
Package is created properly, spec file is already maintained : https://github.com/grosjo/fts-xapian/tree/master/PACKAGES/RPM but now, honestly, I don't really know what to do. Any help very welcome On 2021-08-18 20:09, Ben Beasley wrote: Relevant history: https://bugzilla.redhat.com/show_bug.cgi?id=1953340 https://github.com/grosjo/fts-xapian/issues/82 In short, a package was submitted and approved, but the submitter (who is also the upstream author) is discouraged by the need to seek sponsorship into the packager group. - The package looks straightforward to maintain, and there are a lot of packagers on this list who could potentially do it, but even a simple package takes some effort. Hopefully you'll find someone who is a user of your program or who finds it interesting enough for one personal reason or another to pick up where you left off. On 8/18/21 2:36 PM, Joan Moreau via devel wrote: Hi How to find someone able to push the code in a RPM package ? Reminder - Source code : https://github.com/grosjo/fts-xapian/ <https://github.com/grosjo/fts-xapian/> - Reference : https://doc.dovecot.org/configuration_manual/fts/ <https://doc.dovecot.org/configuration_manual/fts/> - Existing ArchLinux package (not AUR) :https://archlinux.org/packages/?q=dovecot-fts-xapian <https://archlinux.org/packages/?q=dovecot-fts-xapian> - Existing Debian/Ubuntu package : https://tracker.debian.org/pkg/dovecot-fts-xapian <https://tracker.debian.org/pkg/dovecot-fts-xapian> For me, the current process Fedora is just too complicated, so I need help to find someone who knows the process quite well. Thank you ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission (dovecot-fts-xapian)
Hi How to find someone able to push the code in a RPM package ? Reminder - Source code : https://github.com/grosjo/fts-xapian/ - Reference : https://doc.dovecot.org/configuration_manual/fts/ - Existing ArchLinux package (not AUR) :https://archlinux.org/packages/?q=dovecot-fts-xapian - Existing Debian/Ubuntu package : https://tracker.debian.org/pkg/dovecot-fts-xapian For me, the current process Fedora is just too complicated, so I need help to find someone who knows the process quite well. Thank you___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Dovecot-news] v2.3.16 released
Well, I don't really understand your note.
Bottom-line : 2.3.16 crashes every now and then.
Maybe is there a quick fix for production servers ?
On 2021-08-09 10:27, Timo Sirainen wrote:
On 9. Aug 2021, at 11.24, Timo Sirainen wrote:
On 9. Aug 2021, at 11.03, Joan Moreau wrote:
#0 0x7f2370f7fe3d in o_stream_nsendv (stream=0x0,
iov=iov@entry=0x7ffeb9dabd70, iov_count=iov_count@entry=1) at
ostream.c:333
overflow = false
#1 0x7f2370f7feca in o_stream_nsend (stream=,
data=, size=) at ostream.c:325
iov = {iov_base = 0x55b8af41d470, iov_len = 5}
#2 0x7f2370f7ff1a in o_stream_nsend_str (stream=,
str=) at ostream.c:344
No locals.
#3 0x55b8af391f84 in indexer_client_status_callback (percentage=56,
context=0x55b8af434b70) at indexer-client.c:146
_data_stack_cur_id = 4
ctx = 0x55b8af434b70
#4 0x55b8af3921a0 in indexer_queue_request_status_int
(queue=0x55b8af4299a0, request=0x55b8af434b90, percentage=56) at
indexer-queue.c:182
context =
Looks like v2.3.15 already broke this. Happens when indexer-client
disconnects early. Hopefully doesn't happen very often.
Oh, actually v2.3.15.1, but looks like it wasn't even released to
community.
Re: [Dovecot-news] v2.3.16 released
Well, I do not think I am mistaken.
I also get the following error for "indexer" process
#0 0x7f2370f7fe3d in o_stream_nsendv (stream=0x0,
iov=iov@entry=0x7ffeb9dabd70, iov_count=iov_count@entry=1) at
ostream.c:333
333 if (unlikely(stream->closed || stream->stream_errno != 0 ||
(gdb) bt full
#0 0x7f2370f7fe3d in o_stream_nsendv (stream=0x0,
iov=iov@entry=0x7ffeb9dabd70, iov_count=iov_count@entry=1) at
ostream.c:333
overflow = false
#1 0x7f2370f7feca in o_stream_nsend (stream=,
data=, size=) at ostream.c:325
iov = {iov_base = 0x55b8af41d470, iov_len = 5}
#2 0x7f2370f7ff1a in o_stream_nsend_str (stream=,
str=) at ostream.c:344
No locals.
#3 0x55b8af391f84 in indexer_client_status_callback (percentage=56,
context=0x55b8af434b70) at indexer-client.c:146
_data_stack_cur_id = 4
ctx = 0x55b8af434b70
#4 0x55b8af3921a0 in indexer_queue_request_status_int
(queue=0x55b8af4299a0, request=0x55b8af434b90, percentage=56) at
indexer-queue.c:182
context =
i = 0
#5 0x55b8af3919a2 in worker_status_callback (percentage=56,
context=0x55b8af434cb0) at indexer.c:104
conn = 0x55b8af434cb0
request = 0x55b8af434b90
#6 0x55b8af392ac4 in worker_connection_call_callback
(percentage=, worker=0x55b8af434cb0) at
worker-connection.c:42
No locals.
#7 worker_connection_input_args (conn=0x55b8af434cb0,
args=0x55b8af41d348) at worker-connection.c:109
worker = 0x55b8af434cb0
percentage = 56
ret =
_tmp_event =
#8 0x7f2370f53853 in connection_input_default (conn=0x55b8af434cb0)
at connection.c:95
_data_stack_cur_id = 3
line = 0x55b8af438625 "56"
input = 0x55b8af436210
output = 0x55b8af436430
ret = 1
#9 0x7f2370f71919 in io_loop_call_io (io=0x55b8af436550) at
ioloop.c:727
ioloop = 0x55b8af425ec0
t_id = 2
__func__ = "io_loop_call_io"
#10 0x7f2370f72fc2 in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x55b8af425ec0) at ioloop-epoll.c:222
On 2021-08-06 13:49, Aki Tuomi wrote:
On 06/08/2021 15:43 Joan Moreau wrote:
Thank you Timo
However, this leads to
kernel: imap[228122]: segfault at 50 ip 7f7015ee332b sp
7fffa7178740 error 4 in lib20_fts_plugin.so[7f7015ee1000+11000]
Returning to 2.3.15 resolves the problem
Can you provide `gdb bt full` output for the crash?
Aki
Re: [Dovecot-news] v2.3.16 released
git clone -b release-2.3.16 On 2021-08-06 15:07, Timo Sirainen wrote: On 6. Aug 2021, at 15.08, Joan Moreau wrote: Below (gdb) bt full #0 fts_user_autoindex_exclude (box=, box@entry=0x55e0bc7e0fe8) at fts-user.c:347 There is no such function in 2.3.16 release. That's only in the current git master. What did you install and from where?
Re: [Dovecot-news] v2.3.16 released
Below
(gdb) bt full
#0 fts_user_autoindex_exclude (box=,
box@entry=0x55e0bc7e0fe8) at fts-user.c:347
fuser =
#1 0x7f42e8e9b4a6 in fts_mailbox_allocated (box=0x55e0bc7e0fe8) at
fts-storage.c:806
flist =
v = 0x55e0bc7e1010
fbox = 0x55e0bc7e1608
#2 0x7f42e952652c in hook_mailbox_allocated
(box=box@entry=0x55e0bc7e0fe8) at mail-storage-hooks.c:256
_data_stack_cur_id = 5
_foreach_end = 0x55e0bc7d28a0
_foreach_ptr = 0x55e0bc7d2890
hooks = 0x7f42e8ec9ba0
ctx = 0x55e0bc7e2818
#3 0x7f42e95219c1 in mailbox_alloc (list=0x55e0bc7d97b8,
vname=0x55e0bc78f608 "INBOX",
flags=flags@entry=MAILBOX_FLAG_DROP_RECENT) at mail-storage.c:860
_data_stack_cur_id = 4
new_list = 0x55e0bc7d97b8
storage = 0x55e0bc7d9fc8
box = 0x55e0bc7e0fe8
open_error = MAIL_ERROR_NONE
errstr = 0x0
__func__ = "mailbox_alloc"
#4 0x55e0bbd0a5c2 in select_open (readonly=false, mailbox=out>, ctx=0x55e0bc7d6fa0) at cmd-select.c:285
client = 0x55e0bc7d6298
status = {messages = 32, recent = 48, unseen = 814554448, uidvalidity =
32766, uidnext = 814554256, first_unseen_seq = 32766, first_recent_uid =
1633369088,
last_cached_seq = 3805518085, highest_modseq = 0, highest_pvt_modseq =
139925357787644, keywords = 0x55e0bc78f398, permanent_flags = 0, flags =
0, permanent_keywords = false,
allow_new_keywords = false, nonpermanent_modseqs = false,
no_modseq_tracking = false, have_guids = false, have_save_guids = true,
have_only_guid128 = false}
flags = MAILBOX_FLAG_DROP_RECENT
ret = 0
client =
status = {messages = , recent = , unseen =
, uidvalidity = , uidnext = out>,
first_unseen_seq = , first_recent_uid = ,
last_cached_seq = , highest_modseq = ,
highest_pvt_modseq = ,
keywords = , permanent_flags = , flags =
, permanent_keywords = ,
allow_new_keywords = ,
nonpermanent_modseqs = , no_modseq_tracking = out>, have_guids = , have_save_guids = ,
have_only_guid128 = }
flags =
ret =
#5 cmd_select_full (cmd=, readonly=) at
cmd-select.c:416
client = 0x55e0bc7d6298
ctx = 0x55e0bc7d6fa0
args = 0x55e0bc7a58d8
list_args = 0x7ffe308d1c74
mailbox = 0x55e0bc78f608 "INBOX"
client_error = 0x1
ret =
__func__ = "cmd_select_full"
#6 0x55e0bbd12484 in command_exec (cmd=cmd@entry=0x55e0bc7d6e08) at
imap-commands.c:201
hook = 0x55e0bc79b5d0
finished =
__func__ = "command_exec"
#7 0x55e0bbd104b2 in client_command_input (cmd=) at
imap-client.c:1230
client = 0x55e0bc7d6298
command =
tag = 0x7f42e942d8fa
"]A\\A]\303\061\300\303ff.\017\037\204"
name = 0x55e0bbd26e50 "SELECT"
ret =
On 2021-08-06 13:49, Aki Tuomi wrote:
On 06/08/2021 15:43 Joan Moreau wrote:
Thank you Timo
However, this leads to
kernel: imap[228122]: segfault at 50 ip 7f7015ee332b sp
7fffa7178740 error 4 in lib20_fts_plugin.so[7f7015ee1000+11000]
Returning to 2.3.15 resolves the problem
Can you provide `gdb bt full` output for the crash?
Aki
Re: [Dovecot-news] v2.3.16 released
Thank you Timo
However, this leads to
kernel: imap[228122]: segfault at 50 ip 7f7015ee332b sp
7fffa7178740 error 4 in lib20_fts_plugin.so[7f7015ee1000+11000]
Returning to 2.3.15 resolves the problem
On 2021-08-06 12:42, Timo Sirainen wrote:
Hi,
One interesting thing in this release is the support for configuring
OAUTH2 openid-configuration element. It would be nice if IMAP clients
started supporting this feature to enable OAUTH2 for all IMAP servers,
not just Gmail and a few others. This would allow all kinds of new
authentication methods for IMAP and improve the authentication security
in general.
https://dovecot.org/releases/2.3/dovecot-2.3.16.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.16.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Docker images in https://hub.docker.com/r/dovecot/dovecot
* Any unexpected exit() will now result in a core dump. This can
especially help notice problems when a Lua script causes exit(0).
* auth-worker process is now restarted when the number of auth
requests reaches service auth-worker { service_count }. The default
is still unlimited.
+ Event improvements: Added data_stack_grow event and http-client
category. See https://doc.dovecot.org/admin_manual/list_of_events/
+ oauth2: Support RFC 7628 openid-configuration element. This allows
clients to support OAUTH2 for any server, not just a few hardcoded
servers like they do now. See openid_configuration_url setting in
dovecot-oauth2.conf.ext.
+ mysql: Single statements are no longer enclosed with BEGIN/COMMIT.
+ dovecot-sysreport --core supports multiple core files now and does
not require specifying the binary path.
+ imapc: When imap_acl plugin is loaded and imapc_features=acl is used,
IMAP ACL commands are proxied to the remote server. See
https://doc.dovecot.org/configuration_manual/mail_location/imapc/
+ dict-sql now supports the "UPSERT" syntax for SQLite and PostgreSQL.
+ imap: If IMAP client disconnects during a COPY command, the copying
is aborted, and changes are reverted. This may help to avoid many
email duplicates if client disconnects during COPY and retries it
after reconnecting.
- master process was using 100% CPU if service attempted to create more
processes due to process_min_avail, but process_limit was already
reached. v2.3.15 regression.
- Using attachment detection flags wrongly logged unnecessary "Failed
to add attachment keywords" errors. v2.3.13 regression.
- IMAP QRESYNC: Expunging UID 1 mail resulted in broken VANISHED
response, which could have confused IMAP clients. v2.3.13 regression.
- imap: STORE didn't send untagged replies for \Seen changes for
(shared) mailboxes using INDEXPVT. v2.3.10 regression.
- rawlog_dir setting would not log input that was pipelined after
authentication command.
- Fixed potential infinite looping with autoexpunging.
- Log event exporter: Truncate long fields to 1000 bytes
- LAYOUT=index: ACL inheritance didn't work when creating mailboxes
- Event filters: Unquoted '?' wildcard caused a crash at startup
- fs-metawrap: Fix to handling zero sized files
- imap-hibernate: Fixed potential crash at deinit.
- acl: dovecot-acl-list files were written for acl_ignore_namespaces
- program-client (used by Sieve extprograms, director_flush_socket)
may have missed status response from UNIX and network sockets,
resulting in unexpected failures.
___
Dovecot-news mailing list
dovecot-n...@dovecot.org
https://dovecot.org/mailman/listinfo/dovecot-news
Re: How to use xapian with non-text attachments
It is now very out of date. @Jello : Kindly update please On 2021-03-21 12:58, André Rodier wrote: Hello, The version packaged on Bullseye is slightly out of date, I have filled a bug report: https://bugs.debian.org/985654 Thanks to the maintainers for their hard work! André On Sun, 2021-03-21 at 10:51 +, André Rodier wrote: Hello, I am developing a hosting platform on Debian Bullseye, with Dovecot amongst other tools. I am trying to use the xapian full test search plugin, but I can see the attachments are skipped: This is what I have in the logs when running the indexing in verbose mode: --- doveadm(camille): Info: FTS Xapian: fts_backend_xapian_check_access doveadm(camille): Info: FTS Xapian: Memory stats : Used = 56 MB, Free = 66 MB doveadm(camille): Info: FTS Xapian: fts_backend_xapian_index_hdr doveadm(camille): Info: FTS Xapian: fts_backend_xapian_query doveadm(camille): Info: FTS Xapian: Query= uid:"44" doveadm(camille): Info: FTS Xapian: Ngram(S) -> 63 items (total 0 KB) doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_unset_build_key doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Message- Id,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_build_more doveadm(camille): Info: FTS Xapian: fts_backend_xapian_check_access doveadm(camille): Info: FTS Xapian: Memory stats : Used = 56 MB, Free = 66 MB doveadm(camille): Info: FTS Xapian: fts_backend_xapian_index_hdr doveadm(camille): Info: FTS Xapian: fts_backend_xapian_query doveadm(camille): Info: FTS Xapian: Query= uid:"44" doveadm(camille): Info: FTS Xapian: Ngram(XMID) -> 4 items (total 0 KB) doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_unset_build_key doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=X- Mailer,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'xmailer' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=MIME- Version,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'mimeversion' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Content- Type,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'contenttype' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Authentication- Results,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'authenticationresults' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=X-AV- Checked,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'xavchecked' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Content- Type,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'contenttype' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=(null),Type=text/plain,Disposition=(null)) doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_build_more doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_unset_build_key doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Content- Type,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'contenttype' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Content- Description,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'contentdescription' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Content- Disposition,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'contentdisposition' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=Content- Transfer- Encoding,Type=(null),Disposition=(null)) doveadm(camille): Info: FTS Xapian: Unknown header (indexing) 'contenttransferencoding' doveadm(camille): Info: FTS Xapian: fts_backend_xapian_update_set_build_key doveadm(camille): Info: FTS Xapian: New part (Header=(null),Type=text/csv,Disposition=attachment; filename="file.csv") doveadm(camille): Info: F
Re: New RPM submission
ok but then just tell me what to fix in the proposed package (if any) so this can be made available to users On July 3, 2021 22:24:48 Mattia Verga via devel wrote: Il 03/07/21 16:58, Joan Moreau via devel ha scritto: Thanks to you and @eclipseo This has already been a full nightmare to create the SRPM file, and now it seems that I again need to an additional nightmare to "prove myself" The package is already in Deb and archlinux (*). Isn't it enough to push it to Fedora ? Thanks (*) https://packages.debian.org/bullseye/dovecot-fts-xapian <https://packages.debian.org/bullseye/dovecot-fts-xapian> https://archlinux.org/packages/?q=dovecot-fts-xapian <https://archlinux.org/packages/?q=dovecot-fts-xapian> The SRPM file may be fine, but the packager may not. What we are trying to make you understand is that to be admitted as Fedora packager you must prove your reliability. Posting comments such as: "I don't really plan to 'show my worth' but just willing to maintain this small and usefull package" or refusing to read and follow guidelines, keeping posting complaints here don't really make a good impression. Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Thanks to you and @eclipseo This has already been a full nightmare to create the SRPM file, and now it seems that I again need to an additional nightmare to "prove myself" The package is already in Deb and archlinux (*). Isn't it enough to push it to Fedora ? Thanks (*) https://packages.debian.org/bullseye/dovecot-fts-xapian https://archlinux.org/packages/?q=dovecot-fts-xapian On 2021-07-03 07:00, Mattia Verga via devel wrote: Il 02/07/21 22:29, Joan Moreau via devel ha scritto: In practical terms, how to get a "sponsor" ? Open a ticket in https://pagure.io/packager-sponsors/issues and ask there for guidance. Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Thanks to you and @eclipseo This has already been a full nightmare to create the SRPM file, and now it seems that I again need to an additional nightmare to "prove myself" The package is already in Deb and archlinux (*). Isn't it enough to push it to Fedora ? Thanks (*) https://packages.debian.org/bullseye/dovecot-fts-xapian https://archlinux.org/packages/?q=dovecot-fts-xapian On 2021-07-03 07:00, Mattia Verga via devel wrote: Il 02/07/21 22:29, Joan Moreau via devel ha scritto: In practical terms, how to get a "sponsor" ? Open a ticket in https://pagure.io/packager-sponsors/issues and ask there for guidance. Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
In practical terms, how to get a "sponsor" ? On 2021-06-29 11:13, Sérgio Basto wrote: On Sat, 2021-06-26 at 22:34 +0200, Emmanuel Seyman wrote: * Joan Moreau via devel [26/06/2021 19:36] : What is next ? The answer is the same one you were given two months ago. You need to seek out a sponsor: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group https://fedoraproject.org/wiki/Join_the_package_collection_maintainers https://fedoraproject.org/wiki/Package_maintenance_guide Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
ok
I updated https://bugzilla.redhat.com/show_bug.cgi?id=1953340
What is next ?
Thank you so much
On 2021-06-26 17:49, Sérgio wrote:
kinit -R @ FEDORAPROJECT
https://fedoraproject.org/wiki/Infrastructure/Kerberos
A 23 de junho de 2021 18:34:20 WEST, Joan Moreau via devel
escreveu:
Hello
How can I move forward on this ?
Thank you
On April 27, 2021 21:51:53 Joan Moreau via devel
wrote:
Hi Emmanuel
I am trying my best to foloow the process but I get nowhere
Now I get a "koji" error ("AuthError: unable to obtain a session")
I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead
some error ("fedpkg request-repo --exception dovecot-fts-xapian")
I filed a "bug" on redhat :
https://bugzilla.redhat.com/show_bug.cgi?id=1953340
And now, how to get things moving ?
Isnt' there just a repo where to push the RPM ? (similar to Arch)
thank you so much
On 2021-04-25 15:51, Emmanuel Seyman wrote:
* Joan Moreau via devel [24/04/2021 18:49] :
It looks overwhelmingly complicated.
Out of curiosity, which part of the process looks complicated.
Perhaps we can simplify it.
Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Enviado a partir do meu dispositivo Android com o K-9 Mail. Peço
desculpa pela brevidade.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: New RPM submission
Maybe there is a way to import RPM packages from Debian ? https://packages.debian.org/bullseye/dovecot-fts-xapian On Sat, 2021-06-26 at 12:37 +0200, Joan Moreau via devel wrote: > Honeslt y , process is so complicated > > Now, I am again getting errors about "unaotirzed url" > > How to make things happens intesaod of all thisnightmare ? > > Thank you > > > > On Wed, 2021-06-23 at 19:58 +0200, Arthur Bols wrote: > > On 23/06/2021 19:34, Joan Moreau via devel wrote: > > > Hello > > > > > > How can I move forward on this ? > > > > > > Thank you > > Hi Joan, > > > > Could you elaborate please? > > > > As Emmanuel said, you have two options: > > > a) use a COPR repository and publish instructions on enabling the > > > repo > > > b) find an existing maintainer to do the heavy lifting and sign > > > on as > > > a co-maintainer to deal with upstream-related issues. The primary > > > maintainer will then only have to deal with Fedora-related > > > issues. > > > > Arthur > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > Do not reply to spam on the list, report it: > > https://pagure.io/fedora-infrastructure > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Honeslt y , process is so complicated Now, I am again getting errors about "unaotirzed url" How to make things happens intesaod of all thisnightmare ? Thank you On Wed, 2021-06-23 at 19:58 +0200, Arthur Bols wrote: > On 23/06/2021 19:34, Joan Moreau via devel wrote: > > Hello > > > > How can I move forward on this ? > > > > Thank you > Hi Joan, > > Could you elaborate please? > > As Emmanuel said, you have two options: > > a) use a COPR repository and publish instructions on enabling the > > repo > > b) find an existing maintainer to do the heavy lifting and sign on > > as > > a co-maintainer to deal with upstream-related issues. The primary > > maintainer will then only have to deal with Fedora-related issues. > > Arthur > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Hello
How can I move forward on this ?
Thank you
On April 27, 2021 21:51:53 Joan Moreau via devel
wrote:
Hi Emmanuel
I am trying my best to foloow the process but I get nowhere
Now I get a "koji" error ("AuthError: unable to obtain a session")
I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead some
error ("fedpkg request-repo --exception dovecot-fts-xapian")
I filed a "bug" on redhat : https://bugzilla.redhat.com/show_bug.cgi?id=1953340
And now, how to get things moving ?
Isnt' there just a repo where to push the RPM ? (similar to Arch)
thank you so much
On 2021-04-25 15:51, Emmanuel Seyman wrote:
* Joan Moreau via devel [24/04/2021 18:49] :
It looks overwhelmingly complicated.
Out of curiosity, which part of the process looks complicated.
Perhaps we can simplify it.
Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: New RPM submission
COPR is like AUR on ARch or PPA on Debian/Ubuntu These are not in the default installation of the user, and not easily acceisble for a non-tech user, so these not really appropriate. What I would suggest, is to join the two repositories (being "by default" for the average end user) , except packages coming form the "less involved" people would expire quickly if not maintained On 2021-05-01 09:47, Vitaly Zaitsev via devel wrote: On 01.05.2021 10:21, Joan Moreau via devel wrote: For instance, personally, I am not using Fedora at all (Arch fan ;) ) but just willing to make my piece of software available widely for those interested. I am happy to maintain the package in the long run, but will not get involve to much into Fedora project except my small piece of software contribution. You can use COPR for your software then. No join barrier at all.___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
My opinion as a simple enthusiast, is that things should be separated in two 1 - Those who have a great piece of software, simply willing to make it available to the large public. In such case, there should be only quality barrier of the package + rules of duration (i.e. added packages are not kept in Fedora if not maintained for instance once a year) 2 - Those who wants to be much more involved into Fedora project, and this is in deed another story For instance, personally, I am not using Fedora at all (Arch fan ;) ) but just willing to make my piece of software available widely for those interested. I am happy to maintain the package in the long run, but will not get involve to much into Fedora project except my small piece of software contribution. On 2021-05-01 07:03, Otto Urpelainen wrote: Bryce Carson kirjoitti 1.5.2021 klo 3.21: For what it's worth, I'm trying to join and have a package included and there are definitely some areas I would like to improve. Should we make a thread on their mailing list? On Fri., Apr. 30, 2021, 5:50 p.m. Bryce Carson, wrote: Perhaps we could improve the wiki page on Joining** to make it more clear what the process is like? I read through the guidelines and the Joining page a couple times, and only near the end does it state that Joining is more about, well, joining as a person than publishing a package. I believe it then recommendeds Copr around that point for simple publishing. Maybe we could ask Docs and some newer joiners to do a little review of the wiki for Joining and see if we can rewrite and modernize? I joined during 2021, and also I felt that the entry barrier was quite high. Long instructions involving complex toolset and buildsystem and socially scary things like writing introductory messages to mailing lists and publicly commenting on package reviews. I think a lot could be done to make Fedora packaging more approachable. A certain barrier will always be there, because you must have a) the expertise and b) the trust of the Fedora community to maintain your package and acquiring these requires some investment. Regarding joining as a person vs. adding a package, I think the page title "Join the package collection maintainers" already resolves that, as do the first two sentences: "So, you have decided to become a package maintainer in the Fedora Project? This guide will lead you through your first package submission." But I can understand how the page might seem confusing if you start from the "I just want to add this package to Fedora repositories" mindset. Do you think it would help if that page started with a an Overview section, that very briefly explains hwo the process goes and why the different steps are there? For me, the most difficult part was the suggestion that the aspiring packager should immediately comment on other package reviews to get sponsored. I see review as an expert task, so I did not feel secure to do that as the first task. Enough to that I used another method of getting sponsored [1 [1]]. It was not completely clear to me (even though the instructions actually say so) that I could have first get my package reviewed and approved, and only then start doing those preliminary reviews to get sponsored. I guess a simple edit on the "How to get sponsored into the packager group" page could clarify that. Otherwise, in case there are other newcomers who had the same apprehension of preliminary reviews, maybe alternative methods involving pull requests to existing packages etc. could be given more visibility? [1]: https://pagure.io/packager-sponsors/issue/455 Otto ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure Links: -- [1] https://pagure.io/packager-sponsors/issue/455___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Thanks but I am really scratching my head to try to understand all this: 1 - How to get to the "packager" group ou forum or else ? 2 - What does it mean to "block the FE-NEEDSPONSOR [1] tracking bug" ? So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340 Any help very welcome Thanks JM Extract: Until you are sponsored into the packager group you are not able to own packages or to check in changes to packages which you own. However, you can still create an initial package and submit it for review as talked about on the joining the package collection maintainers page [2]. When you open your review request in bugzilla, you should block the FE-NEEDSPONSOR [1] tracking bug, that way all of the sponsors will be able to see your sponsorship request. Although FE-NEEDSPONSOR is set on the package's review request, it is the person that needs to be sponsored into the packager group, not the package. The package undergoes a review and approval [3] that is separate from someone sponsoring you. Note that it is possible to have accepted packages which you cannot import because you have not been sponsored. See below. On 2021-04-29 14:51, Qiyu Yan wrote: 在 2021-04-29星期四的 13:25 +0100，Joan Moreau via devel写道： Thank you Concretely, how to "find a sponsor" ? FYI: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure Links: -- [1] https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR [2] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Ensure_your_package_is_suitable [3] https://fedoraproject.org/wiki/Package_Review_Process___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
THank you Isn´t there a muh more systemic (and simpler) process to push a RPM in the distribution ? On 2021-04-29 14:51, Qiyu Yan wrote: 在 2021-04-29星期四的 13:25 +0100，Joan Moreau via devel写道： Thank you Concretely, how to "find a sponsor" ? FYI: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Thank you
Concretely, how to "find a sponsor" ?
On 2021-04-27 22:19, Emmanuel Seyman wrote:
* Joan Moreau [27/04/2021 20:51] :
Hi Emmanuel
I am trying my best to foloow the process but I get nowhere
Now I get a "koji" error ("AuthError: unable to obtain a session")
That looks like a recurring kerberos issue.
https://pagure.io/koji/issue/2063
https://pagure.io/releng/issue/7522
You probably want to contact releng to help solve this.
I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead
some
error ("fedpkg request-repo --exception dovecot-fts-xapian")
Why is this package exempt from the review process?
I filed a "bug" on redhat :
https://bugzilla.redhat.com/show_bug.cgi?id=1953340
And now, how to get things moving ?
You need to seek out a sponsor:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group
Isnt' there just a repo where to push the RPM ? (similar to Arch)
There is COPR but I suspect this is reserved to Fedora packagers so you
will still need to be sponsored.
https://fedoraproject.org/wiki/Category:Copr
Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: systemd integration not working
Not much details
Git version (including the patch you sent) raised CPU load very very
high.
Can't play too much on my production server.
Let me know if I can help
On 2021-04-28 06:12, Aki Tuomi wrote:
Can you provide any details on this instability?
Aki
On April 27, 2021 7:58:01 PM UTC, Joan Moreau wrote:
Ok, a third regression is that it becomes highly unstable with the
patch you sent
I had to get back to 2.3.14
On 2021-04-27 17:07, Joan Moreau wrote:
Indeed, latest git works much better :)
On 2021-04-27 05:58, Aki Tuomi wrote:
Can you try with latest git? We did some improvements on the systemd
configure parts.
Aki
On 26/04/2021 23:32 Joan Moreau wrote:
Looking at config.log, there is #define HAVE_LIBSYSTEMD 1
But "Type=notify" does not appear
My systemd is version 248
On 2021-04-26 12:05, Joan Moreau wrote: I have
# sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled;
vendor preset: disabled)
Active: active (running) since Sun 2021-04-25 20:13:25 UTC; 14h ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 2559364 (dovecot)
Tasks: 28 (limit: 76912)
Memory: 1.0G
CPU: 7min 18.342s
CGroup: /system.slice/dovecot.service
├─2559364 /usr/sbin/dovecot -F
├─2559366 dovecot/imap-login
├─2559367 dovecot/anvil [11 connections]
├─2559368 dovecot/log
On 2021-04-26 08:32, Aki Tuomi wrote: I don't know then. It works for
me and I just tried it again. The only reason it would fail would be
that HAVE_LIBSYSTEMD is not defined, so it would not be using
libsystemd for notify support.
$ sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/lib/systemd/system/dovecot.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2021-04-26 10:30:02 EEST; 2s ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 30213 (dovecot)
Status: "v2.4.devel (98a1cca054) running"
Tasks: 4 (limit: 4701)
Memory: 3.3M
CGroup: /system.slice/dovecot.service
├─30213 /home/cmouse/dovecot/sbin/dovecot -F
├─30214 dovecot/anvil
├─30215 dovecot/log
└─30216 dovecot/config
You can tell from the "Status" line that it's using Type=notify.
Aki
On 26/04/2021 10:29 Joan Moreau wrote:
Yes, I do run autogen.sh after every "git pull"
On 2021-04-26 08:21, Aki Tuomi wrote: The current autoconf code is bit
buggy, but if you do indeed have libsystemd-dev installed it should do
the right thing and will work with systemd even if you have
Type=notify.
This has been actually tested, so if it's not working, then something
else is wrong.
Did you remember to run ./autogen.sh after pulling from git to make
sure you get new configure script?
Aki
On 26/04/2021 10:11 Joan Moreau wrote:
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote: This is because you are not
compiling with libsystemd-dev installed. I guess we need to make some
service template that use type simple when you don't use libsystemd.
Aki
On 25/04/2021 22:53 Joan Moreau wrote:
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau
wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+ i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
- i_assert(client->prev == NULL && client->next == NULL);
+ DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_clien
Re: systemd integration not working
Ok, a third regression is that it becomes highly unstable with the patch
you sent
I had to get back to 2.3.14
On 2021-04-27 17:07, Joan Moreau wrote:
Indeed, latest git works much better :)
On 2021-04-27 05:58, Aki Tuomi wrote:
Can you try with latest git? We did some improvements on the systemd
configure parts.
Aki
On 26/04/2021 23:32 Joan Moreau wrote:
Looking at config.log, there is #define HAVE_LIBSYSTEMD 1
But "Type=notify" does not appear
My systemd is version 248
On 2021-04-26 12:05, Joan Moreau wrote: I have
# sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled;
vendor preset: disabled)
Active: active (running) since Sun 2021-04-25 20:13:25 UTC; 14h ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 2559364 (dovecot)
Tasks: 28 (limit: 76912)
Memory: 1.0G
CPU: 7min 18.342s
CGroup: /system.slice/dovecot.service
├─2559364 /usr/sbin/dovecot -F
├─2559366 dovecot/imap-login
├─2559367 dovecot/anvil [11 connections]
├─2559368 dovecot/log
On 2021-04-26 08:32, Aki Tuomi wrote: I don't know then. It works for
me and I just tried it again. The only reason it would fail would be
that HAVE_LIBSYSTEMD is not defined, so it would not be using
libsystemd for notify support.
$ sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/lib/systemd/system/dovecot.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2021-04-26 10:30:02 EEST; 2s ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 30213 (dovecot)
Status: "v2.4.devel (98a1cca054) running"
Tasks: 4 (limit: 4701)
Memory: 3.3M
CGroup: /system.slice/dovecot.service
├─30213 /home/cmouse/dovecot/sbin/dovecot -F
├─30214 dovecot/anvil
├─30215 dovecot/log
└─30216 dovecot/config
You can tell from the "Status" line that it's using Type=notify.
Aki
On 26/04/2021 10:29 Joan Moreau wrote:
Yes, I do run autogen.sh after every "git pull"
On 2021-04-26 08:21, Aki Tuomi wrote: The current autoconf code is bit
buggy, but if you do indeed have libsystemd-dev installed it should do
the right thing and will work with systemd even if you have
Type=notify.
This has been actually tested, so if it's not working, then something
else is wrong.
Did you remember to run ./autogen.sh after pulling from git to make
sure you get new configure script?
Aki
On 26/04/2021 10:11 Joan Moreau wrote:
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote: This is because you are not
compiling with libsystemd-dev installed. I guess we need to make some
service template that use type simple when you don't use libsystemd.
Aki
On 25/04/2021 22:53 Joan Moreau wrote:
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau
wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+ i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
- i_assert(client->prev == NULL && client->next == NULL);
+ DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_client = client->prev;
- /* remove from clients linked list before it's added to
- client_fd_proxies. */
+ /* move to destroyed_clients linked list before it's potentially
+ added to client_fd_proxies. */
+ i_assert(!client->fd_proxying);
DLLIST_REMOVE(&clients, client);
DLLIST_PREPEND(&destroyed_clie
Re: systemd integration not working
Indeed, latest git works much better :)
On 2021-04-27 05:58, Aki Tuomi wrote:
Can you try with latest git? We did some improvements on the systemd
configure parts.
Aki
On 26/04/2021 23:32 Joan Moreau wrote:
Looking at config.log, there is #define HAVE_LIBSYSTEMD 1
But "Type=notify" does not appear
My systemd is version 248
On 2021-04-26 12:05, Joan Moreau wrote: I have
# sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled;
vendor preset: disabled)
Active: active (running) since Sun 2021-04-25 20:13:25 UTC; 14h ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 2559364 (dovecot)
Tasks: 28 (limit: 76912)
Memory: 1.0G
CPU: 7min 18.342s
CGroup: /system.slice/dovecot.service
├─2559364 /usr/sbin/dovecot -F
├─2559366 dovecot/imap-login
├─2559367 dovecot/anvil [11 connections]
├─2559368 dovecot/log
On 2021-04-26 08:32, Aki Tuomi wrote: I don't know then. It works for
me and I just tried it again. The only reason it would fail would be
that HAVE_LIBSYSTEMD is not defined, so it would not be using
libsystemd for notify support.
$ sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/lib/systemd/system/dovecot.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2021-04-26 10:30:02 EEST; 2s ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 30213 (dovecot)
Status: "v2.4.devel (98a1cca054) running"
Tasks: 4 (limit: 4701)
Memory: 3.3M
CGroup: /system.slice/dovecot.service
├─30213 /home/cmouse/dovecot/sbin/dovecot -F
├─30214 dovecot/anvil
├─30215 dovecot/log
└─30216 dovecot/config
You can tell from the "Status" line that it's using Type=notify.
Aki
On 26/04/2021 10:29 Joan Moreau wrote:
Yes, I do run autogen.sh after every "git pull"
On 2021-04-26 08:21, Aki Tuomi wrote: The current autoconf code is bit
buggy, but if you do indeed have libsystemd-dev installed it should do
the right thing and will work with systemd even if you have
Type=notify.
This has been actually tested, so if it's not working, then something
else is wrong.
Did you remember to run ./autogen.sh after pulling from git to make
sure you get new configure script?
Aki
On 26/04/2021 10:11 Joan Moreau wrote:
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote: This is because you are not
compiling with libsystemd-dev installed. I guess we need to make some
service template that use type simple when you don't use libsystemd.
Aki
On 25/04/2021 22:53 Joan Moreau wrote:
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau
wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+ i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
- i_assert(client->prev == NULL && client->next == NULL);
+ DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_client = client->prev;
- /* remove from clients linked list before it's added to
- client_fd_proxies. */
+ /* move to destroyed_clients linked list before it's potentially
+ added to client_fd_proxies. */
+ i_assert(!client->fd_proxying);
DLLIST_REMOVE(&clients, client);
DLLIST_PREPEND(&destroyed_clients, client);
@@ -409,13 +411,14 @@ bool client_unref(struct client **_client)
DLLIST_REMOVE(&client_fd_proxies, client);
i_assert(client_fd_pro
Re: New RPM submission
Hi Emmanuel
I am trying my best to foloow the process but I get nowhere
Now I get a "koji" error ("AuthError: unable to obtain a session")
I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead
some error ("fedpkg request-repo --exception dovecot-fts-xapian")
I filed a "bug" on redhat :
https://bugzilla.redhat.com/show_bug.cgi?id=1953340
And now, how to get things moving ?
Isnt' there just a repo where to push the RPM ? (similar to Arch)
thank you so much
On 2021-04-25 15:51, Emmanuel Seyman wrote:
* Joan Moreau via devel [24/04/2021 18:49] :
It looks overwhelmingly complicated.
Out of curiosity, which part of the process looks complicated.
Perhaps we can simplify it.
Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: systemd integration not working
Looking at config.log, there is #define HAVE_LIBSYSTEMD 1
But "Type=notify" does not appear
My systemd is version 248
On 2021-04-26 12:05, Joan Moreau wrote:
I have
# sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled;
vendor preset: disabled)
Active: active (running) since Sun 2021-04-25 20:13:25 UTC; 14h ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 2559364 (dovecot)
Tasks: 28 (limit: 76912)
Memory: 1.0G
CPU: 7min 18.342s
CGroup: /system.slice/dovecot.service
├─2559364 /usr/sbin/dovecot -F
├─2559366 dovecot/imap-login
├─2559367 dovecot/anvil [11 connections]
├─2559368 dovecot/log
On 2021-04-26 08:32, Aki Tuomi wrote:
I don't know then. It works for me and I just tried it again. The only
reason it would fail would be that HAVE_LIBSYSTEMD is not defined, so
it would not be using libsystemd for notify support.
$ sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/lib/systemd/system/dovecot.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2021-04-26 10:30:02 EEST; 2s ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 30213 (dovecot)
Status: "v2.4.devel (98a1cca054) running"
Tasks: 4 (limit: 4701)
Memory: 3.3M
CGroup: /system.slice/dovecot.service
├─30213 /home/cmouse/dovecot/sbin/dovecot -F
├─30214 dovecot/anvil
├─30215 dovecot/log
└─30216 dovecot/config
You can tell from the "Status" line that it's using Type=notify.
Aki
On 26/04/2021 10:29 Joan Moreau wrote:
Yes, I do run autogen.sh after every "git pull"
On 2021-04-26 08:21, Aki Tuomi wrote: The current autoconf code is bit
buggy, but if you do indeed have libsystemd-dev installed it should do
the right thing and will work with systemd even if you have
Type=notify.
This has been actually tested, so if it's not working, then something
else is wrong.
Did you remember to run ./autogen.sh after pulling from git to make
sure you get new configure script?
Aki
On 26/04/2021 10:11 Joan Moreau wrote:
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote: This is because you are not
compiling with libsystemd-dev installed. I guess we need to make some
service template that use type simple when you don't use libsystemd.
Aki
On 25/04/2021 22:53 Joan Moreau wrote:
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau
wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+ i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
- i_assert(client->prev == NULL && client->next == NULL);
+ DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_client = client->prev;
- /* remove from clients linked list before it's added to
- client_fd_proxies. */
+ /* move to destroyed_clients linked list before it's potentially
+ added to client_fd_proxies. */
+ i_assert(!client->fd_proxying);
DLLIST_REMOVE(&clients, client);
DLLIST_PREPEND(&destroyed_clients, client);
@@ -409,13 +411,14 @@ bool client_unref(struct client **_client)
DLLIST_REMOVE(&client_fd_proxies, client);
i_assert(client_fd_proxies_count > 0);
client_fd_proxies_count--;
+ } else {
+ DLLIST_REMOVE(&destroyed_clients, client);
}
i_stream_unref(&client->input);
o_stream_unref(&client->output);
i_close_fd(&client->fd);
event_unref(&client->event);
- DLLIST_REMOVE(&destroyed_clients, client);
i_free(client->proxy_user);
i_free(client->proxy_master_user);
i_free(client->virtual_user);
Re: systemd integration not working (WAS: Latest git FATAL error)
I have
# sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled;
vendor preset: disabled)
Active: active (running) since Sun 2021-04-25 20:13:25 UTC; 14h ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 2559364 (dovecot)
Tasks: 28 (limit: 76912)
Memory: 1.0G
CPU: 7min 18.342s
CGroup: /system.slice/dovecot.service
├─2559364 /usr/sbin/dovecot -F
├─2559366 dovecot/imap-login
├─2559367 dovecot/anvil [11 connections]
├─2559368 dovecot/log
On 2021-04-26 08:32, Aki Tuomi wrote:
I don't know then. It works for me and I just tried it again. The only
reason it would fail would be that HAVE_LIBSYSTEMD is not defined, so
it would not be using libsystemd for notify support.
$ sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/lib/systemd/system/dovecot.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2021-04-26 10:30:02 EEST; 2s ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 30213 (dovecot)
Status: "v2.4.devel (98a1cca054) running"
Tasks: 4 (limit: 4701)
Memory: 3.3M
CGroup: /system.slice/dovecot.service
├─30213 /home/cmouse/dovecot/sbin/dovecot -F
├─30214 dovecot/anvil
├─30215 dovecot/log
└─30216 dovecot/config
You can tell from the "Status" line that it's using Type=notify.
Aki
On 26/04/2021 10:29 Joan Moreau wrote:
Yes, I do run autogen.sh after every "git pull"
On 2021-04-26 08:21, Aki Tuomi wrote: The current autoconf code is bit
buggy, but if you do indeed have libsystemd-dev installed it should do
the right thing and will work with systemd even if you have
Type=notify.
This has been actually tested, so if it's not working, then something
else is wrong.
Did you remember to run ./autogen.sh after pulling from git to make
sure you get new configure script?
Aki
On 26/04/2021 10:11 Joan Moreau wrote:
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote: This is because you are not
compiling with libsystemd-dev installed. I guess we need to make some
service template that use type simple when you don't use libsystemd.
Aki
On 25/04/2021 22:53 Joan Moreau wrote:
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau
wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+ i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
- i_assert(client->prev == NULL && client->next == NULL);
+ DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_client = client->prev;
- /* remove from clients linked list before it's added to
- client_fd_proxies. */
+ /* move to destroyed_clients linked list before it's potentially
+ added to client_fd_proxies. */
+ i_assert(!client->fd_proxying);
DLLIST_REMOVE(&clients, client);
DLLIST_PREPEND(&destroyed_clients, client);
@@ -409,13 +411,14 @@ bool client_unref(struct client **_client)
DLLIST_REMOVE(&client_fd_proxies, client);
i_assert(client_fd_proxies_count > 0);
client_fd_proxies_count--;
+ } else {
+ DLLIST_REMOVE(&destroyed_clients, client);
}
i_stream_unref(&client->input);
o_stream_unref(&client->output);
i_close_fd(&client->fd);
event_unref(&client->event);
- DLLIST_REMOVE(&destroyed_clients, client);
i_free(client->proxy_user);
i_free(client->proxy_master_user);
i_free(client->virtual_user);
Re: Latest git FATAL error
Yes, I do run autogen.sh after every "git pull"
On 2021-04-26 08:21, Aki Tuomi wrote:
The current autoconf code is bit buggy, but if you do indeed have
libsystemd-dev installed it should do the right thing and will work
with systemd even if you have Type=notify.
This has been actually tested, so if it's not working, then something
else is wrong.
Did you remember to run ./autogen.sh after pulling from git to make
sure you get new configure script?
Aki
On 26/04/2021 10:11 Joan Moreau wrote:
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote: This is because you are not
compiling with libsystemd-dev installed. I guess we need to make some
service template that use type simple when you don't use libsystemd.
Aki
On 25/04/2021 22:53 Joan Moreau wrote:
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau
wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+ i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
- i_assert(client->prev == NULL && client->next == NULL);
+ DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_client = client->prev;
- /* remove from clients linked list before it's added to
- client_fd_proxies. */
+ /* move to destroyed_clients linked list before it's potentially
+ added to client_fd_proxies. */
+ i_assert(!client->fd_proxying);
DLLIST_REMOVE(&clients, client);
DLLIST_PREPEND(&destroyed_clients, client);
@@ -409,13 +411,14 @@ bool client_unref(struct client **_client)
DLLIST_REMOVE(&client_fd_proxies, client);
i_assert(client_fd_proxies_count > 0);
client_fd_proxies_count--;
+ } else {
+ DLLIST_REMOVE(&destroyed_clients, client);
}
i_stream_unref(&client->input);
o_stream_unref(&client->output);
i_close_fd(&client->fd);
event_unref(&client->event);
- DLLIST_REMOVE(&destroyed_clients, client);
i_free(client->proxy_user);
i_free(client->proxy_master_user);
i_free(client->virtual_user);
Re: Latest git FATAL error
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote:
This is because you are not compiling with libsystemd-dev installed. I
guess we need to make some service template that use type simple when
you don't use libsystemd.
Aki
On 25/04/2021 22:53 Joan Moreau wrote:
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau
wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+ i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
- i_assert(client->prev == NULL && client->next == NULL);
+ DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_client = client->prev;
- /* remove from clients linked list before it's added to
- client_fd_proxies. */
+ /* move to destroyed_clients linked list before it's potentially
+ added to client_fd_proxies. */
+ i_assert(!client->fd_proxying);
DLLIST_REMOVE(&clients, client);
DLLIST_PREPEND(&destroyed_clients, client);
@@ -409,13 +411,14 @@ bool client_unref(struct client **_client)
DLLIST_REMOVE(&client_fd_proxies, client);
i_assert(client_fd_proxies_count > 0);
client_fd_proxies_count--;
+ } else {
+ DLLIST_REMOVE(&destroyed_clients, client);
}
i_stream_unref(&client->input);
o_stream_unref(&client->output);
i_close_fd(&client->fd);
event_unref(&client->event);
- DLLIST_REMOVE(&destroyed_clients, client);
i_free(client->proxy_user);
i_free(client->proxy_master_user);
i_free(client->virtual_user);
Re: Latest git FATAL error
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote:
On 24/04/2021 21:56 Joan Moreau wrote:
chroot= does not resolve the issue
I have "chroot = login" in my conf
Thanks!
The chroot was needed to get the core dump.
Can you try if this does fix the crash?
Aki
From 1df4e02cbff710ce8938480b07a5690e37f661f6 Mon Sep 17 00:00:00 2001
From: Timo Sirainen
Date: Fri, 23 Apr 2021 16:43:36 +0300
Subject: [PATCH] login-common: Fix handling destroyed_clients linked
list
The client needs to be removed from destroyed_clients linked list
before
it's added to client_fd_proxies linked list.
Broken by 1c622cdbe08df2f642e28923c39894516143ae2a
---
src/login-common/client-common.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/login-common/client-common.c
b/src/login-common/client-common.c
index bdb6e9c798..1d264d9f75 100644
--- a/src/login-common/client-common.c
+++ b/src/login-common/client-common.c
@@ -289,8 +289,9 @@ void client_disconnect(struct client *client, const
char *reason,
/* Login was successful. We may now be proxying the connection,
so don't disconnect the client until client_unref(). */
if (client->iostream_fd_proxy != NULL) {
+i_assert(!client->fd_proxying);
client->fd_proxying = TRUE;
-i_assert(client->prev == NULL && client->next == NULL);
+DLLIST_REMOVE(&destroyed_clients, client);
DLLIST_PREPEND(&client_fd_proxies, client);
client_fd_proxies_count++;
}
@@ -307,8 +308,9 @@ void client_destroy(struct client *client, const
char *reason)
if (last_client == client)
last_client = client->prev;
-/* remove from clients linked list before it's added to
- client_fd_proxies. */
+/* move to destroyed_clients linked list before it's potentially
+ added to client_fd_proxies. */
+i_assert(!client->fd_proxying);
DLLIST_REMOVE(&clients, client);
DLLIST_PREPEND(&destroyed_clients, client);
@@ -409,13 +411,14 @@ bool client_unref(struct client **_client)
DLLIST_REMOVE(&client_fd_proxies, client);
i_assert(client_fd_proxies_count > 0);
client_fd_proxies_count--;
+} else {
+DLLIST_REMOVE(&destroyed_clients, client);
}
i_stream_unref(&client->input);
o_stream_unref(&client->output);
i_close_fd(&client->fd);
event_unref(&client->event);
-DLLIST_REMOVE(&destroyed_clients, client);
i_free(client->proxy_user);
i_free(client->proxy_master_user);
i_free(client->virtual_user);
Re: New RPM submission
fixed On April 25, 2021 16:27:57 Dennis Gilmore wrote: some of the changes have just been committed already, or an equivalent. The value you have for the license is incorrect https://fedoraproject.org/wiki/Licensing:Main lists the correct values -License:LGPL-2.1 +License:LGPLv2 There is no need to explicitly Require xapian-core-libs as rpm requires the correct shared library provided automatically. -Requires: xapian-core, xapian-core-libs, dovecot +Requires: xapian-core, dovecot the description needs to be broken down into shorter lines. I would probably expand somewhere in the description that FTS stands for Full Text Search %description -This project intends to provide a straightforward, simple and maintenance free, way to configure FTS plugin for Dovecot, leveraging the efforts by the Xapian.org team. - -This effort came after Dovecot team decided to deprecate "fts_squat" included in the dovecot core, and due to the complexity of the Solr plugin capabilitles, un-needed for most users. +This project intends to provide a straightforward, simple and maintenance +free, way to configure FTS plugin for Dovecot, leveraging the efforts by +the Xapian.org team. + +This effort came after Dovecot team decided to deprecate "fts_squat" +included in the dovecot core, and due to the complexity of the Solr plugin +capabilitles, un-needed for most users. Dennis On Sun, Apr 25, 2021 at 10:04 AM Joan Moreau wrote: > you probably sent the same srpm No, it is a new one , re-generated > just fine, I did make a few changes to the spec file. with a correct changelag entry it should pass review What changes are you suggesting ? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Not sure what happend but the failure is gone somehow Anyway, I pushed the "bug report" here : https://bugzilla.redhat.com/show_bug.cgi?id=1953340 Is that correct ? Thanks On 2021-04-25 16:04, Joan Moreau wrote: you probably sent the same srpm No, it is a new one , re-generated just fine, I did make a few changes to the spec file. with a correct changelag entry it should pass review What changes are you suggesting ?___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
you probably sent the same srpm No, it is a new one , re-generated just fine, I did make a few changes to the spec file. with a correct changelag entry it should pass review What changes are you suggesting ?___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Thank you so much
However, still the same issue:
https://kojipkgs.fedoraproject.org//work/tasks/1947/1947/build.log
g++ is not found
On 2021-04-25 15:42, Jerry James wrote:
On Sun, Apr 25, 2021 at 7:58 AM Joan Moreau via devel
wrote:
Same status :(
Try the attached version. It fixes several minor problems in the spec
file. The problem you were encountering was the lack of the "-n
fts-xapian-%{version}" argument to %autosetup. The default directory
name is "%{name}-%{version}", but %{name} is dovecot-fts-xapian, not
fts-xapian.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: New RPM submission
thanks
With the correction I get
https://kojipkgs.fedoraproject.org//work/tasks/1646/1646/build.log
Still not finding g++ :(
On 2021-04-25 15:29, Dennis Gilmore wrote:
On Sun, Apr 25, 2021 at 8:48 AM Richard Shaw
wrote:
On Sun, Apr 25, 2021 at 8:36 AM Joan Moreau via devel
wrote:
When I launch the "koji" comand, build fails because it does not find
g++
(see :
https://kojipkgs.fedoraproject.org//work/tasks/9140/66659140/build.log
)
However, I put gcc-c++ in the BuildRequires line
(see :
https://github.com/grosjo/fts-xapian/blob/master/PACKAGES/RPM/fts-xapian.spec
)
Just a drive by look at it but try changing:
./configure --with-dovecot=/usr/lib64/dovecot
to:
%configure --with-dovecot=/usr/lib64/dovecot
probably should actually be
%configure --with-dovecot=%{_libdir}/dovecot
Dennis
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: New RPM submission
Same status :( https://kojipkgs.fedoraproject.org//work/tasks/9973/66659973/build.log On 2021-04-25 14:46, Richard Shaw wrote: On Sun, Apr 25, 2021 at 8:36 AM Joan Moreau via devel wrote: When I launch the "koji" comand, build fails because it does not find g++ (see : https://kojipkgs.fedoraproject.org//work/tasks/9140/66659140/build.log ) However, I put gcc-c++ in the BuildRequires line (see : https://github.com/grosjo/fts-xapian/blob/master/PACKAGES/RPM/fts-xapian.spec ) Just a drive by look at it but try changing: ./configure --with-dovecot=/usr/lib64/dovecot to: %configure --with-dovecot=/usr/lib64/dovecot Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Hello I tried anyway to follow the process of submitting a new RPM When I launch the "koji" comand, build fails because it does not find g++ (see : https://kojipkgs.fedoraproject.org//work/tasks/9140/66659140/build.log ) However, I put gcc-c++ in the BuildRequires line (see : https://github.com/grosjo/fts-xapian/blob/master/PACKAGES/RPM/fts-xapian.spec ) Any help very welcome___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Latest git FATAL error
70a13d120,
callback=callback@entry=0x7f7a3336e340 ) at
master-service.c:862
No locals.
#16 0x7f7a3336eb7d in login_binary_run (binary=,
argc=, argv=) at main.c:562
service_flags =
set_pool = 0x55d70a144de0
login_socket = 0x7f7a3337337d "login"
c =
#17 0x00007f7a32feeb25 in __libc_start_main () from /usr/lib/libc.so.6
No symbol table info available.
#18 0x55d70823a84e in _start ()
No symbol table info available.
On 2021-04-24 09:41, Aki Tuomi wrote:
On April 24, 2021 8:19:55 AM UTC, Joan Moreau wrote:
Hello
On latest git of dovecot, I get
Apr 24 04:07:36 gjserver dovecot[857958]: imap-login: Panic: file
client-common.c: line 293 (client_disconnect): assertion failed:
(client->prev == NULL && client->next == NULL)
and login process crash
On 2.3.14, there is no problems
Hope it helps
JM
Hi!
Can you try
service imap-login {
chroot=
}
and see if you can get a core dump? gdb bt full output would be useful.
Aki
Re: New RPM submission
Thank you. It looks overwhelmingly complicated. Would there be someone here willing to maintain the RPM for the FTS Xapian plugin ? The plugins has already DEB and ARch packages. SPEC file for Federoa is available here -> https://github.com/grosjo/fts-xapian/issues/82 Thank you so much On 2021-04-10 12:39, Vascom wrote: Also look at https://fedoraproject.org/wiki/Join_the_package_collection_maintainers сб, 10 апр. 2021 г., 14:22 Peter Oliver : Welcome! Start at https://fedoraproject.org/wiki/Package_Review_Process ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Latest git FATAL error
Hello On latest git of dovecot, I get Apr 24 04:07:36 gjserver dovecot[857958]: imap-login: Panic: file client-common.c: line 293 (client_disconnect): assertion failed: (client->prev == NULL && client->next == NULL) and login process crash On 2.3.14, there is no problems Hope it helps JM
New RPM submission
Hi I am trying to create an "offical" RPM for a package related to dovecot imap server See : https://github.com/grosjo/fts-xapian/issues/82 How one should proceed to hae a RPM referenced in Fedora repositories ? Thank you JM___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Virtual folders and mailbox_list_get_root_forced
Hello
Anyone on this ?
Thank you
On 2021-03-28 20:55, Joan Moreau wrote:
yes, this is getting to a mess
Details can be seen here :
https://github.com/grosjo/fts-xapian/issues/72
It shows that sometimes mailbox_list_get_root_forced return the generic
INDEX value, sometimes the namespace value
thank you for your help
On 2021-03-28 12:03, Aki Tuomi wrote:
Hi!
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
This is going to put everyone's indexes under /var/mailindex, without
separating them properly. Might cause fun issues.
Can you give an concrete example of what your issue is?
Aki
On 28/03/2021 13:35 Joan Moreau wrote:
Hi
Anyone on that ?
Thank you so much
On 2021-03-22 18:16, Joan Moreau wrote: Hi
The function mailbox_list_get_root_forcedreturns sometimes the first or
the second value of the INDEX param for the same mailbox.
How to make sure this returns only the correct one of the corresponding
mailbox ?
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
namespace {
location =
virtual:/nix/store/toto-virtual:INDEX=/var/vmail/%d/%n/virtual
prefix = virtual/
separator = /
subscriptions = no
}
Thank you
Re: Virtual folders and mailbox_list_get_root_forced
yes, this is getting to a mess
Details can be seen here :
https://github.com/grosjo/fts-xapian/issues/72
It shows that sometimes mailbox_list_get_root_forced return the generic
INDEX value, sometimes the namespace value
thank you for your help
On 2021-03-28 12:03, Aki Tuomi wrote:
Hi!
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
This is going to put everyone's indexes under /var/mailindex, without
separating them properly. Might cause fun issues.
Can you give an concrete example of what your issue is?
Aki
On 28/03/2021 13:35 Joan Moreau wrote:
Hi
Anyone on that ?
Thank you so much
On 2021-03-22 18:16, Joan Moreau wrote: Hi
The function mailbox_list_get_root_forcedreturns sometimes the first or
the second value of the INDEX param for the same mailbox.
How to make sure this returns only the correct one of the corresponding
mailbox ?
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
namespace {
location =
virtual:/nix/store/toto-virtual:INDEX=/var/vmail/%d/%n/virtual
prefix = virtual/
separator = /
subscriptions = no
}
Thank you
Re: Virtual folders and mailbox_list_get_root_forced
Hi
Anyone on that ?
Thank you so much
On 2021-03-22 18:16, Joan Moreau wrote:
Hi
The function mailbox_list_get_root_forced returns sometimes the first
or the second value of the INDEX param for the same mailbox.
How to make sure this returns only the correct one of the corresponding
mailbox ?
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
namespace {
location =
virtual:/nix/store/toto-virtual:INDEX=/var/vmail/%d/%n/virtual
prefix = virtual/
separator = /
subscriptions = no
}
Thank you
Virtual folders and mailbox_list_get_root_forced
Hi
The function mailbox_list_get_root_forced returns sometimes the first or
the second value of the INDEX param for the same mailbox.
How to make sure this returns only the correct one of the corresponding
mailbox ?
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
namespace {
location =
virtual:/nix/store/toto-virtual:INDEX=/var/vmail/%d/%n/virtual
prefix = virtual/
separator = /
subscriptions = no
}
Thank you
Re: Git / Compilation error
I do that each time The problem arises on recent git only On 2021-03-04 08:16, Aki Tuomi wrote: Try running `autoreconf -vi` Aki On 04/03/2021 10:13 Joan Moreau wrote: I already have this file (dovecot compilation was working fine until recent git) [root@gjserver dovecot]# ls -al /usr/share/aclocal/gettext.m4 -rw-r--r-- 1 root root 14488 Aug 4 2020 /usr/share/aclocal/gettext.m4 On 2021-03-04 08:09, Aki Tuomi wrote: You need to find package on your system which contains /usr/share/aclocal/gettext.m4 or similar. This provides AM_ICONV. Aki On 04/03/2021 10:07 Joan Moreau wrote: Hello I already have gettext [root@gjserver dovecot]# pacman -S gettext warning: gettext-0.21-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Package (1) Old Version New Version Net Change core/gettext 0.21-1 0.21-1 0.00 MiB On 2021-03-04 08:03, Aki Tuomi wrote: You need to install gettext Aki On 04/03/2021 10:02 Joan Moreau wrote: Hello, With latest git, I get the following error : configure.ac:761: the top level configure.ac:22: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:205: error: possibly undefined macro: AC_MSG_ERROR configure.ac:247: error: possibly undefined macro: AS_IF configure.ac:303: error: possibly undefined macro: AM_ICONV configure.ac:434: error: possibly undefined macro: AC_CHECK_HEADER configure:28073: error: possibly undefined macro: AC_CHECK_FUNC Something I am missing? Thank you
Re: Git / Compilation error
I already have this file (dovecot compilation was working fine until recent git) [root@gjserver dovecot]# ls -al /usr/share/aclocal/gettext.m4 -rw-r--r-- 1 root root 14488 Aug 4 2020 /usr/share/aclocal/gettext.m4 On 2021-03-04 08:09, Aki Tuomi wrote: You need to find package on your system which contains /usr/share/aclocal/gettext.m4 or similar. This provides AM_ICONV. Aki On 04/03/2021 10:07 Joan Moreau wrote: Hello I already have gettext [root@gjserver dovecot]# pacman -S gettext warning: gettext-0.21-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Package (1) Old Version New Version Net Change core/gettext 0.21-1 0.21-1 0.00 MiB On 2021-03-04 08:03, Aki Tuomi wrote: You need to install gettext Aki On 04/03/2021 10:02 Joan Moreau wrote: Hello, With latest git, I get the following error : configure.ac:761: the top level configure.ac:22: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:205: error: possibly undefined macro: AC_MSG_ERROR configure.ac:247: error: possibly undefined macro: AS_IF configure.ac:303: error: possibly undefined macro: AM_ICONV configure.ac:434: error: possibly undefined macro: AC_CHECK_HEADER configure:28073: error: possibly undefined macro: AC_CHECK_FUNC Something I am missing? Thank you
Re: Git / Compilation error
Hello I already have gettext [root@gjserver dovecot]# pacman -S gettext warning: gettext-0.21-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Package (1) Old Version New Version Net Change core/gettext 0.21-1 0.21-1 0.00 MiB On 2021-03-04 08:03, Aki Tuomi wrote: You need to install gettext Aki On 04/03/2021 10:02 Joan Moreau wrote: Hello, With latest git, I get the following error : configure.ac:761: the top level configure.ac:22: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:205: error: possibly undefined macro: AC_MSG_ERROR configure.ac:247: error: possibly undefined macro: AS_IF configure.ac:303: error: possibly undefined macro: AM_ICONV configure.ac:434: error: possibly undefined macro: AC_CHECK_HEADER configure:28073: error: possibly undefined macro: AC_CHECK_FUNC Something I am missing? Thank you
Git / Compilation error
Hello, With latest git, I get the following error : configure.ac:761: the top level configure.ac:22: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:205: error: possibly undefined macro: AC_MSG_ERROR configure.ac:247: error: possibly undefined macro: AS_IF configure.ac:303: error: possibly undefined macro: AM_ICONV configure.ac:434: error: possibly undefined macro: AC_CHECK_HEADER configure:28073: error: possibly undefined macro: AC_CHECK_FUNC Something I am missing? Thank you
Re: fts_encoder
Created a PR
https://github.com/dovecot/core/pull/155
On 2021-02-11 13:25, Joan Moreau wrote:
Hello
Checking further, and putting logs a bit every where in the dovecot
code, the core is sending FIRST the initial document (not decoded) then
SECOND the decoded version
Thisi is really weird, and the indexer then indexes a lot of binary
crap
I am struggling to find where in the code this double call is made.
Anyone knows ?
On 2021-02-10 00:05, John Fawcett wrote:
On 09/02/2021 15:33, Joan Moreau wrote:
If I place the following code in the plugin
fts_backend_xxx_update_build_more function (lucene, squat and xapian,
as solr refuses to work properly on my setup)
{
char * s = i_strdup("EMPTY");
if(data != NULL) { i_free(s); s = i_strndup(data,20); }
i_info("fts_backend_update_build_more: data like '%s'",s);
i_free(s);
}
and if I send a PDF by email, the data shown in the log is "%PDF-1.7 "
so it does mean the decoder data is not properly transmitted to the
plugin
Something is wrong in the data transmission
Joan
I too see something similar with fts_solr. I do see the raw %PDF string
and PDF binary data being passed through to
fts_backend_xxx_update_build_more function but I disagree with the
conclusion you draw from it.
After the raw data I also see the decoded data, so at least in my case
it is possible to see both the raw and decoded data in
fts_backend_xxx_update_build_more function. In the rawlog I no longer
see the binary data (but some blank lines), so something is filtering
it. I do see the decoded data in the rawlog. I do get hits on the solr
search for the decoded text.
John
Re: fts_encoder
Hello
Checking further, and putting logs a bit every where in the dovecot
code, the core is sending FIRST the initial document (not decoded) then
SECOND the decoded version
Thisi is really weird, and the indexer then indexes a lot of binary crap
I am struggling to find where in the code this double call is made.
Anyone knows ?
On 2021-02-10 00:05, John Fawcett wrote:
On 09/02/2021 15:33, Joan Moreau wrote:
If I place the following code in the plugin
fts_backend_xxx_update_build_more function (lucene, squat and xapian,
as solr refuses to work properly on my setup)
{
char * s = i_strdup("EMPTY");
if(data != NULL) { i_free(s); s = i_strndup(data,20); }
i_info("fts_backend_update_build_more: data like '%s'",s);
i_free(s);
}
and if I send a PDF by email, the data shown in the log is "%PDF-1.7 "
so it does mean the decoder data is not properly transmitted to the
plugin
Something is wrong in the data transmission
Joan
I too see something similar with fts_solr. I do see the raw %PDF string
and PDF binary data being passed through to
fts_backend_xxx_update_build_more function but I disagree with the
conclusion you draw from it.
After the raw data I also see the decoded data, so at least in my case
it is possible to see both the raw and decoded data in
fts_backend_xxx_update_build_more function. In the rawlog I no longer
see the binary data (but some blank lines), so something is filtering
it. I do see the decoded data in the rawlog. I do get hits on the solr
search for the decoded text.
John
Re: fts_encoder
If I place the following code in the plugin
fts_backend_xxx_update_build_more function (lucene, squat and xapian, as
solr refuses to work properly on my setup)
{
char * s = i_strdup("EMPTY");
if(data != NULL) { i_free(s); s = i_strndup(data,20); }
i_info("fts_backend_update_build_more: data like
'%s'",s);
i_free(s);
}
and if I send a PDF by email, the data shown in the log is "%PDF-1.7 "
so it does mean the decoder data is not properly transmitted to the
plugin
Something is wrong in the data transmission
On 2021-02-09 11:58, John Fawcett wrote:
On 08/02/2021 23:05, Stuart Henderson wrote: On 2021/02/08 21:33, Joan
Moreau wrote: Yes , once again : output of the decoder is fine, I also
put log inide the dovecot core to
check whether data is properly transmitted, and result is that it is
(i.e. dovecot core
receives the proper output of pdftotext via the decoder
Now, that data is the /not/ the one sent from dovecot core to the fts
plugin (and this is the
same issue for solr and all other plugins) Seems that something is
different with your setup than John's and mine
then, as fts_solr rawlog (which is just the http request split into
.in and .out files) has the decoded file for us.
Did you try with the actual fts_solr plugin so it's a direct comparison
with what we see? There is no need for a real solr server, just point
it
at any http server (or I guess netcat listening on a port will also do)
with
mail_plugins = fts fts_solr
plugin {
fts_autoindex = yes
fts = solr
fts_solr = url=http://127.0.0.1:80/ rawlog_dir=/tmp/solr
}
If that is not showing decoded for you then I suppose there's some
problem on the way into/through fts. And if it does show as decoded
then perhaps fts_solr is doing something slightly different than the
places you're examining in fts and your plugin, and that might give
a point to work backwards from.
I'd also recommend Joan to look into some of the potential
configuration
issues I mentioned in my first reply and if the problem persists, post
some clear evidence.
John
Re: fts_encoder
Yes , once again : output of the decoder is fine, I also put log inide the dovecot core to check whether data is properly transmitted, and result is that it is (i.e. dovecot core receives the proper output of pdftotext via the decoder Now, that data is the /not/ the one sent from dovecot core to the fts plugin (and this is the same issue for solr and all other plugins) Of course, the stemming will show a good results (as PDF content will be stemmed) but the problem does remain. How to make sure the data sent to the FTS plugins (xapian, solr, whatever...) is the the output of the decoder and /not/ the original data ? On 2021-02-08 21:11, Stuart Henderson wrote: On 2021-02-08, Joan Moreau wrote: Well, in the function xxx_build_more of FTS plugin, the data received in the original PDF, not the output of pdftotext Can you clarify where do you put your log in the solr plugin , so I can check the situation in the xapian plugin ? The log is particular to fts_solr, you set it with e.g. "fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ rawlog_dir=/tmp/solr" Confirmed it works for me, i.e. passes text from inside the pdf, and not the whole pdf itself. Did you check that decode2text.sh works ok on your system (when running as the relevant uid)? cat foo.pdf | sudo -u dovecot /usr/libexec/dovecot/decode2text.sh application/pdf
Re: fts_encoder
Yes , once again : output of the decoder is fine, I also put log inide the dovecot core to check whereas data is properly transmitted and it is (i.e. dovecot core receives the proper output of pdftotext via the decoder Now, that data is the /not/ the once ent from dovecot core to the fts plugin (and this is the same issue for solr and all other plugins) Of course, the stemming will show a good results abut the problem does remain. How to make sure the data sent to the FTS plugins (xapian, solr, whatever...) is the the output of the decoder and /not/ the original data ? On 2021-02-08 21:11, Stuart Henderson wrote: On 2021-02-08, Joan Moreau wrote: Well, in the function xxx_build_more of FTS plugin, the data received in the original PDF, not the output of pdftotext Can you clarify where do you put your log in the solr plugin , so I can check the situation in the xapian plugin ? The log is particular to fts_solr, you set it with e.g. "fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ rawlog_dir=/tmp/solr" Confirmed it works for me, i.e. passes text from inside the pdf, and not the whole pdf itself. Did you check that decode2text.sh works ok on your system (when running as the relevant uid)? cat foo.pdf | sudo -u dovecot /usr/libexec/dovecot/decode2text.sh application/pdf
Re: fts_encoder
Well, in the function xxx_build_more of FTS plugin, the data received in the original PDF, not the output of pdftotext Can you clarify where do you put your log in the solr plugin , so I can check the situation in the xapian plugin ? On 2021-02-08 17:34, John Fawcett wrote: On 08/02/2021 15:22, Joan Moreau wrote: Well, thank you for the answer, but the actual issue is that data sent by the decoder (stipulated in the conf file) is properly collected by dovecot core, but /not/ sent to the plugin : the plugin receives the original data. This is not linked to a particular plugin (xapian, solr, squat, etc..) but seems to be a general issue of dovecot core Hi Joan as far as I can see there's not a general issue in the dovecot core with using the decoder. It works for me. I see the text extracted from PDF sent to solr (I enable raw_log feature to see the actual data going over ) Also when I query solr I get a search hit for attachment text. John
Re: fts_encoder
Well, thank you for the answer, but the actual issue is that data sent
by the decoder (stipulated in the conf file) is properly collected by
dovecot core, but /not/ sent to the plugin : the plugin receives the
original data.
This is not linked to a particular plugin (xapian, solr, squat, etc..)
but seems to be a general issue of dovecot core
On 2021-02-08 01:03, John Fawcett wrote:
On 07/02/2021 18:51, Joan Moreau wrote:
more info : the function fts_parser_script_more in
plugins/fts/fts-parser.c properly read the output of the script
still, the data is not sent to the FTS pligins (xapian or any other)
On 2021-02-07 17:37, Joan Moreau wrote:
more info : I am running dovecot git version
On 2021-02-07 17:15, Joan Moreau wrote:
a bit more on this, adding log in the decode2text.sh, I can see that
pdftotext output the right data, but that data is /not/ transmitted to
the fts plugin for indexing (only the original pdf code is)
On 2021-02-07 17:00, Joan Moreau wrote:
Hello,
I am trying to deal properly with email attachements in fts-xapian
plugins.
I tried the default script with a PDF file.
The data I receive in the fts plugin part ("xxx_build_more") is the
original document, no the output of the pdftotext
Is there anything I am missing ?
Here my config:
plugin {
plugin = fts_xapian managesieve sieve
fts = xapian
fts_xapian = partial=2 full=20 verbose=1 attachments=1
fts_autoindex = yes
fts_enforced = yes
fts_autoindex_exclude = \Trash
fts_autoindex_exclude2 = \Drafts
fts_decoder = decode2text
sieve = /data/mail/%d/%n/local.sieve
sieve_after = /data/mail/after.sieve
sieve_before = /data/mail/before.sieve
sieve_dir = /data/mail/%d/%n/sieve
sieve_global_dir = /data/mail
sieve_global_path = /data/mail/global.sieve
}
...
service decode2text {
executable = script /usr/libexec/dovecot/decode2text.sh
user = dovecot
unix_listener decode2text {
mode = 0666
}
}
Thank you
Joan
I'm not sure I can be much use for xapian, but looking at your
configuration I did notice some differences with the documentation. I
don't know if they are relevant to the issue you're seeing.
First of all I don't see
mail_plugins = fts
plugin = fts
settings which are both mentioned in the xapian documentation.
Also the documentation states that attachments=1 can only index text
attachments. Maybe you should be using attachments=0 and let fts_decode
handle the attachments.
Failing that, I can only advise to turn on some debugging and see what
that brings.
best regards
John
Re: fts_encoder
more info : the function fts_parser_script_more in
plugins/fts/fts-parser.c properly read the output of the script
still, the data is not sent to the FTS pligins (xapian or any other)
On 2021-02-07 17:37, Joan Moreau wrote:
more info : I am running dovecot git version
On 2021-02-07 17:15, Joan Moreau wrote:
a bit more on this, adding log in the decode2text.sh, I can see that
pdftotext output the right data, but that data is /not/ transmitted to
the fts plugin for indexing (only the original pdf code is)
On 2021-02-07 17:00, Joan Moreau wrote:
Hello,
I am trying to deal properly with email attachements in fts-xapian
plugins.
I tried the default script with a PDF file.
The data I receive in the fts plugin part ("xxx_build_more") is the
original document, no the output of the pdftotext
Is there anything I am missing ?
Here my config:
plugin {
plugin = fts_xapian managesieve sieve
fts = xapian
fts_xapian = partial=2 full=20 verbose=1 attachments=1
fts_autoindex = yes
fts_enforced = yes
fts_autoindex_exclude = \Trash
fts_autoindex_exclude2 = \Drafts
fts_decoder = decode2text
sieve = /data/mail/%d/%n/local.sieve
sieve_after = /data/mail/after.sieve
sieve_before = /data/mail/before.sieve
sieve_dir = /data/mail/%d/%n/sieve
sieve_global_dir = /data/mail
sieve_global_path = /data/mail/global.sieve
}
...
service decode2text {
executable = script /usr/libexec/dovecot/decode2text.sh
user = dovecot
unix_listener decode2text {
mode = 0666
}
}
Thank you
