- users - lists.freelock.com

LedgerSMB 1.7.37 released
by Erik Huelsmann 08 Dec '21

08 Dec '21

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.7.37 * Fix login errors being hidden behind an "insecure response" error (#6251) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.7.37/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.7.37 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.37 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.7.37 These are the sha256 checksums of the uploaded files: 4508200782fd5f39b4ac14521c80e0112f224c8db50581e2829e686c7555a82d ledgersmb-1.7.37.tar.gz db63bf9c2c3c3cfcf0ca87fbb2aa835a8c28322ee2f48d522fbbdb1a2e500624 ledgersmb-1.7.37.tar.gz.asc

1 0

Re: Docker Image
by Erik Huelsmann 08 Dec '21

08 Dec '21

Hi Johann, On Wed, Dec 8, 2021 at 8:50 AM <greyling(a)ruens.co.za> wrote: > I am experiencing problems during the initial setup of LedgerSMB using > your docker image and a pulled postgres image. > I include the commands issued when running these images on user defined > bridge for evaluation purposes. Am using UBUNTU 18 > The problem seems to be an authentication error for the postgres user. > Any guidance will be welcomed > May I suggest you use the accompanying "docker-compose" file, which sets up a network bridge and two (linked) containers out of the box? There seems to be a problem for one container reaching the other. (I'm not quite clear on why this would be the case.) If you have Docker installed, installing docker-compose is trivial ( https://docs.docker.com/compose/install/#install-compose-on-linux-systems) and using it with the LedgerSMB docker images is really simple: https://github.com/ledgersmb/ledgersmb-docker#docker-compose-installation-a… Regards, Erik. -- Preview attachment LedgerSMB.pdf LedgerSMB.pdf 30 KB Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 1

Once again going to try to port into OpenBSD. :-}
by Chris Bennett 05 Dec '21

05 Dec '21

Hello again! I found a nice Black Friday special on a server I can afford. So, another time, 4th time, but who's counting? As I suspected, I would hit a moment where I couldn't come up with $136 a month. So I had to drop that server. Same server, but $67 now. I saved my work on github, which is a big mess, but will help a lot. I learned a ton about submitting and how to deal with that set of Locale::CLDR modules. I also had a strange problem. As far as I have seen, nobody has ever done a project with dozens of dependencies to bring in as just a single person. These types of projects have always been done by groups or really top notch porters, with commit powers to the CVS repository. One problem I had was not seeing the obvious solution to how to deal with really long chains of new dependencies. The people who review submissions DO NOT want single ports to be submitted one at a time, because they are very busy. It didn't occur to me how to deal with this problem until after I stopped working on this. Rather than submit a ridiculously long set of 12 or more dependencies from the LedgerSMB cpanfile outwards, I needed to go out to the end of the chain and work inwards instead, thus submitting only 2-4 at a time. I am now starting up again. I would really appreciate any help, including just a little bit. Even getting just one Perl module ready to submit is more than enough. Different OS's have different goals. OpenBSD is primarily security oriented, so the method of getting a port ready is very strict. Building a port outside of the porting system is strictly forbidden. The FAQ's about porting and the man pages are a bit overwhelming, but most of the needed dependencies are pretty easy to work with. It does require running OpenBSD -current, but that has been amazingly good for quite some time. If you would either like to help or just tell me if you are wanting this to be done, please let me know. Just telling me you want this is really encouraging for me. My ugly mess is at https://github.com/CPBen/LSMB-for-OBSD-WIP It's so messy since I had to upload and download a few hundred GB to and from home and across two servers. Sorry. -- Regards, Chris Bennett

1 0

LedgerSMB 1.9.4 released
by Erik Huelsmann 25 Nov '21

25 Nov '21

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.9.4 * Fix balance sheet printing template listing account descriptions (#6203) * Fix reconciliations to include Source value from transactions (#6122) * Fix error thrown from CSV export function (#6140) * Fix reporting of login problems due to e.g. version mismatch (#5976) * Fix 'import' of username on HR > Employee menu | User tab (#5287) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.4/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.4 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.4 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.4 These are the sha256 checksums of the uploaded files: 30d5f86a48b0861ac142fef48e9a1617757be88c190b1a772f7d8cef1f95f690 ledgersmb-1.9.4.tar.gz 155d1bf2f93f86f1848fed5c3a0e90924decb5592d27284264a1afc41e6bce4f ledgersmb-1.9.4.tar.gz.asc

1 0

LedgerSMB 1.9.3 released
by Erik Huelsmann 14 Nov '21

14 Nov '21

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.9.3 * Sort the buttons on the e-mail entry screen * Fix issues with the PDF output for PNL and Balance sheet reports * Fix indenting on the hierarchical PNL and balance sheet HTML reports * Add link to download HTML PNL and balance sheet reports * Add rudimentary CSS to HTML PNL and balance sheet reports * Fix off-by-one column on the PNL and balance sheet total lines * Remove application links on downloaded HTML PNL and balance sheet reports * Use a temp table to prevent bulk payments trampling on each other * Fix sorting on fixed asset searches (#6151) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.3/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.3 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.3 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.3 These are the sha256 checksums of the uploaded files: 265aaa291f2a021e5c77e9fb674740669a19d552856f841b73f62cc040bf0a4a ledgersmb-1.9.3.tar.gz f97ecc7fa4277648a018ff508d656c403b2445cf4669a0e52908e23f83c74861 ledgersmb-1.9.3.tar.gz.asc

1 0

LedgerSMB 1.8.23 released
by Erik Huelsmann 14 Nov '21

14 Nov '21

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.8.23 * Use a temp table to prevent bulk payments trampling on each other * Fix sorting on fixed asset searches (#6151) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.8.23/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.8.23 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.23 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.8.23 These are the sha256 checksums of the uploaded files: ec929dd8ecb522ed2ff1b7cfe43d73746095df1736cd7807d0cec8baef3469fa ledgersmb-1.8.23.tar.gz 0cdc60f7e95b63f950d2561dddd08d0d12d5c696ef675af67684aae6b8466193 ledgersmb-1.8.23.tar.gz.asc

1 0

technology write for us
by techpostinweb143＠gmail.com 19 Oct '21

19 Oct '21

One of the best guest blogging site with high quality content and domain authority. Write For US- Business, Tech News, Social media, Cloud Computing, Gadgets, Computers, Hardware, Apps / Reviews, SEO & Search Marketing and Operating Systems etc. We work hard to bring about best content that add value to them. https://www.techpostinweb.com/write-for-us/

1 0

Re: Problem moving from 1.7.35 to 1.8.13
by Louis 19 Oct '21

19 Oct '21

Ok, I found a couple issues with my process, which I believe are resolved. Now I generate both a roles backup and a db backup from the tarball instance and save them. I then add: CREATE DATABASE hethcote WITH TEMPLATE = template0 ENCODING = 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8'; ALTER DATABASE hethcote OWNER TO lbmoore; \connect hethcote to the beginning of the db.sqlc from the backup. (Without this the database gets added to postgres' default database postgres.) then I execute (via script): docker-compose pull docker-compose up -d docker exec -i ledgersmb-docker_postgres_1 psql -Upostgres -W --command='\l' docker exec -i ledgersmb-docker_postgres_1 psql -Upostgres -W --command='\du' docker cp ROLES ledgersmb-docker_postgres_1:/docker-entrypoint-initdb.d docker cp DB ledgersmb-docker_postgres_1:/docker-entrypoint-initdb.d docker exec -i ledgersmb-docker_postgres_1 psql -Upostgres -W --command="\i /docker-entrypoint-initdb.d/ROLES" docker exec -i ledgersmb-docker_postgres_1 psql -Upostgres -W --command="\i /docker-entrypoint-initdb.d/DB" 2>&1 | tee log docker exec -i ledgersmb-docker_postgres_1 psql -Upostgres -W --command='\l' docker exec -i ledgersmb-docker_postgres_1 psql -Upostgres -W --command='\du' Everything runs as expected. Then I connect to setup.pl and see the database "hethcote" and select it. Then I have it upgrade the db from 1.7.35 to 1.7.36. While it is doing the upgrade it fails with: Error! psql:./sql/modules/Roles.sql:193: ERROR: relation "exchangerate_type_id_seq" does not exist CONTEXT: SQL statement "GRANT ALL ON exchangerate_type_id_seq TO lsmb_hethcote__exchangerate_edit" PL/pgSQL function lsmb__grant_perms(text,text,text) line 6 at EXECUTE dbversion: hethcote, company: 1.7.36 Attempting to login via login.pl still fails with "Access denied: Bad username/password". Looking into the log from the database build it contains: ... COMMENT psql:/docker-entrypoint-initdb.d/db.sqlc:24821: ERROR: syntax error at or near "AS" LINE 2: AS integer ^ psql:/docker-entrypoint-initdb.d/db.sqlc:24824: ERROR: relation "public.exchangerate_type_id_seq" does not exist psql:/docker-entrypoint-initdb.d/db.sqlc:24830: ERROR: relation "public.exchangerate_type_id_seq" does not exist CREATE SEQUENCE ALTER TABLE ... the command that failed is: -- -- Name: exchangerate_type_id_seq; Type: SEQUENCE; Schema: public; Owner: postgres -- CREATE SEQUENCE public.exchangerate_type_id_seq AS integer START WITH 1 INCREMENT BY 1 NO MINVALUE NO MAXVALUE CACHE 1; I am still stuck but have a better process for consistency in rebuilding the environment. Louis On Fri, 15 Oct 2021, lsmbdev wrote: > Hi Louis, > > Are you able to login to setup.pl with the pg admin user (normally postgres in the containers) with no company name? > > Once logged in like that you should see a list of databases present on the cluster. > > Regards > David Godfrey > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Louis <lbmlist(a)hethcote.com> > Date: 15/10/21 02:11 (GMT+08:00) > To: lsmbdev <lsmbdev(a)sbts.com.au> > Cc: users(a)lists.ledgersmb.org > Subject: RE: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13 > > > > Ok, I've been trying various iterations of this without success. > > I have scripted it so that I can replicate with accuracy. Basically I > > 1) Log in to existing tarball instance with a known good username and > password > > 2) Log out of tarball instance and shutdown the tarball starman. > > 3) ensure all of previously existing docker instance is removed > > 4) use the docker-compose method of starting postges and lsmb > containers. > > 5) do a pg_dump of tarball instance "hethcote" database > > 6) create the same good username and password in the container's postgres > and check that the md5sum passwords match. > > 7) copy the pg_dump into the postgres container > > 8) docker exec psql with \i to load the pg_dump from tarball instance to > docker instance > > 9) log in using known good username from tarball instance into the docker > instance and get a bad username/password message. > > Is there something I missing? > > Louis > > > On Sat, 18 Sep 2021, lsmbdev wrote: > > > Hi Louis, > > > > If you have no objections to trying our docker containers I'd suggest doing a backup and, after > > installing docker-compose, restore to the containerised setup. > > > > > > Most development work, and many production instance are now using docker containers, so it's > > considered to be quite stable and easily supported. > > > > Regards > > David Godfrey > > > > > > Sent from my Galaxy > > > > > > -------- Original message -------- > > From: Louis <lbmlist(a)hethcote.com> > > Date: 18/9/21 23:43 (GMT+08:00) > > To: lsmbdev <lsmbdev(a)sbts.com.au> > > Cc: Louis <lbmlist(a)hethcote.com> > > Subject: RE: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13 > > > > > > This is installed from source. The database has been rolled along since > > SQLedger 2.x and migrated to LedgerSMB at the time of the fork. PostgreSQL > > itself is at v11 but has rolled along from v6 (don't recall orig version > > from the SQLedger days.) > > > > The hba file has always trusted local socket connections (pause for moment > > of shame) so password was blank until the 1.6 series. Since 1.6 password > > was just a random character since it was ignored. This is how 1.7.35 has > > been working. This is true for postgres as well as my own lbmoore. > > > > So decades of bad practices have finally caught up to me with 1.8. > > > > I'm at a loss as to where to start with this mess. > > > > Louis > > > > > > > > On Sat, 18 Sep 2021, lsmbdev wrote: > > > > > Morning Louis, > > > > > > The most common cause of this would be using the incorrect credentials with setup.pl > > > > > > Remember that the username is not a username you use to log into your company. > > > In many cases it is simply "postgres" > > > > > > Is your installation via a container, or did you install from source? > > > > > > Regards > > > David Godfrey > > > > > > Sent from my Galaxy > > > > > > > > > -------- Original message -------- > > > From: Louis <lbmlist(a)hethcote.com> > > > Date: 18/9/21 09:28 (GMT+08:00) > > > To: users(a)lists.ledgersmb.org > > > Subject: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13 > > > > > > > > > Hey all, > > > > > > I have not been able to move to the 1.8 series from the 1.7 series. I > > > think I must not have authentication correct and the 1.8 is expecting a > > > different setup than previous version. > > > > > > This is a starman installation. I will backup the DB, move the code into > > > place and run setup.pl. Setup pops open an error reading: > > > > > > Localhost:5762 says > > > > > > Access denied (500): bad username/password > > > > > > I'm using the same credentials as with 1.7.35. > > > > > > I can roll back and forth easily, but I don't see what the debug path > > > should be. > > > > > > Any help would be appreciated. > > > > > > Louis > > > > > > > > > _______________________________________________ > > > users mailing list -- users(a)lists.ledgersmb.org > > > To unsubscribe send an email to users-leave(a)lists.ledgersmb.org > > > > > > > > > > > >

3 3

Re: Problem moving from 1.7.35 to 1.8.13
by Louis 14 Oct '21

14 Oct '21

Ok, I've been trying various iterations of this without success. I have scripted it so that I can replicate with accuracy. Basically I 1) Log in to existing tarball instance with a known good username and password 2) Log out of tarball instance and shutdown the tarball starman. 3) ensure all of previously existing docker instance is removed 4) use the docker-compose method of starting postges and lsmb containers. 5) do a pg_dump of tarball instance "hethcote" database 6) create the same good username and password in the container's postgres and check that the md5sum passwords match. 7) copy the pg_dump into the postgres container 8) docker exec psql with \i to load the pg_dump from tarball instance to docker instance 9) log in using known good username from tarball instance into the docker instance and get a bad username/password message. Is there something I missing? Louis On Sat, 18 Sep 2021, lsmbdev wrote: > Hi Louis, > > If you have no objections to trying our docker containers I'd suggest doing a backup and, after > installing docker-compose, restore to the containerised setup. > > > Most development work, and many production instance are now using docker containers, so it's > considered to be quite stable and easily supported. > > Regards > David Godfrey > > > Sent from my Galaxy > > > -------- Original message -------- > From: Louis <lbmlist(a)hethcote.com> > Date: 18/9/21 23:43 (GMT+08:00) > To: lsmbdev <lsmbdev(a)sbts.com.au> > Cc: Louis <lbmlist(a)hethcote.com> > Subject: RE: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13 > > > This is installed from source. The database has been rolled along since > SQLedger 2.x and migrated to LedgerSMB at the time of the fork. PostgreSQL > itself is at v11 but has rolled along from v6 (don't recall orig version > from the SQLedger days.) > > The hba file has always trusted local socket connections (pause for moment > of shame) so password was blank until the 1.6 series. Since 1.6 password > was just a random character since it was ignored. This is how 1.7.35 has > been working. This is true for postgres as well as my own lbmoore. > > So decades of bad practices have finally caught up to me with 1.8. > > I'm at a loss as to where to start with this mess. > > Louis > > > > On Sat, 18 Sep 2021, lsmbdev wrote: > > > Morning Louis, > > > > The most common cause of this would be using the incorrect credentials with setup.pl > > > > Remember that the username is not a username you use to log into your company. > > In many cases it is simply "postgres" > > > > Is your installation via a container, or did you install from source? > > > > Regards > > David Godfrey > > > > Sent from my Galaxy > > > > > > -------- Original message -------- > > From: Louis <lbmlist(a)hethcote.com> > > Date: 18/9/21 09:28 (GMT+08:00) > > To: users(a)lists.ledgersmb.org > > Subject: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13 > > > > > > Hey all, > > > > I have not been able to move to the 1.8 series from the 1.7 series. I > > think I must not have authentication correct and the 1.8 is expecting a > > different setup than previous version. > > > > This is a starman installation. I will backup the DB, move the code into > > place and run setup.pl. Setup pops open an error reading: > > > > Localhost:5762 says > > > > Access denied (500): bad username/password > > > > I'm using the same credentials as with 1.7.35. > > > > I can roll back and forth easily, but I don't see what the debug path > > should be. > > > > Any help would be appreciated. > > > > Louis > > > > > > _______________________________________________ > > users mailing list -- users(a)lists.ledgersmb.org > > To unsubscribe send an email to users-leave(a)lists.ledgersmb.org > > > > > > >

2 1

13377x Proxy, Search Engine Torrentz Unblock Mirror Sites
by techpost1899＠gmail.com 14 Oct '21

14 Oct '21

Most users these days are less interested in subscription plans and looking for the torrent sites where the premium content is available for free of cost. If you are that type of user, then 13377x or 13377x.to is the best option to download movies, web series, software apps, or games, etc. https://www.techpostinweb.com/13377x-proxy/

1 0