Activity for ede
-
ede modified a comment on ticket #57
the options "should" work over all backends, but sure there might be implementation flaws. if so please open a ticket on https://gitlab.com/duplicity/duplicity/-/issues/ and let's fix it :) apart from the repo i only offer snapshots on https://duply.net/Code#Latest_Development_Snapshot if some issue needs double checking by the issuer. currently there not much developing on duply as it is quite mature and stable fortunately.
-
the options "should" work over all backends, but sure there might be implementation flaws. if so please open a ticket on https://gitlab.com/duplicity/duplicity/-/issues/ and let's fix it :) apart from the repo i only offer snapshots on https://duply.net/Code#Latest_Development_Snapshot if some issue needs double checking by the issuer. currently there not much developing on duply as it is quite matrue and stable fortunately.
-
Add a retry mechanism in case of duplicity backend error
-
hey @3rjpq0d6x, duply is mainly meant to be run manually or by cron and be finished after it is done. i'm unsure if it is a good idea to have it sleeping and retry blindly if some error occurs. duplicity itself already has a retry mechanism build in that should be of help to you. look at the man page https://duplicity.us/stable/duplicity.1.html for the options --num-retries --backend-retry-delay does that help? ..sunny regards ede
-
release 2.5.6
-
conf setting "--exclude-other-filesystems" corrupts generated cmd line
-
released as v2.5.6 . THANKS again David!
-
release 2.5.6
-
release 2.5.6
-
conf setting "--exclude-other-filesystems" corrupts generated cmd line
-
all good. i think i found it. please try this snapshot https://duply.net/tmp/duply.sh
-
ok, that helps. at least i got a hickup now to debug :) user@debian13-lxc:~$ duply david status Start duply v2.5.5, time is 2025-08-28 13:25:50. Using profile '/home/user/.duply/david'. Using installed duplicity version 3.0.4, python 3.13.5 (/usr/bin/python3) 'PYTHONPATH=:/usr/lib/python313.zip:/usr/lib/python3.13:/usr/lib/python3.13/lib-dynload:/usr/local/lib/python3.13/dist-packages:/usr/lib/python3/dist-packages', gpg 2.4.7 (Home: /home/user/.gnupg), awk 'mawk 1.3.4 20250131', grep 'grep (GNU...
-
just tested the VOLSIZE issue VOLSIZE=50 DUPL_PARAMS="$DUPL_PARAMS --volsize $VOLSIZE " with duply test status (test is a profile) and it works fine. verified it with the duply --preview parameter which does not execute but merely prints the generated cmd lines. NOTE the missing --volsize 50 from the status cmd line. :~$ ./duply_dev/duply_wrap test status --preview Start duply.sh v2.5.6dev, time is 2025-08-28 10:54:23. Using profile '/home/dup/.duply/test'. SNIP --- Start running command STATUS at...
-
created a fresh Debian 13 container installed duplicity/duply created test profile, enabled VOLSIZE and MAX_FULLBKP_AGE works for me. please send me the outputs requested above https://sourceforge.net/p/ftplicity/bugs/144/#f9d6 user@debian13-lxc:~$ duply test status Start duply v2.5.5, time is 2025-08-28 12:51:28. Using profile '/home/user/.duply/test'. Using installed duplicity version 3.0.4, python 3.13.5 (/usr/bin/python3) 'PYTHONPATH=:/usr/lib/python313.zip:/usr/lib/python3.13:/usr/lib/python3.13/lib-dynload:/usr/local/lib/python3.13/dist-packages:/usr/lib/python3/dist-packages',...
-
also can't replicate the issue with MAX_FULLBKP_AGE=1M DUPL_PARAMS="$DUPL_PARAMS --full-if-older-than $MAX_FULLBKP_AGE " with duplicity 3.0.4 . maybe a python 3.13 issue or something else on Debian 13 . will setup a vm and check.
-
just tested the VOLSIZE issue VOLSIZE=50 DUPL_PARAMS="$DUPL_PARAMS --volsize $VOLSIZE " with duply test status (test is a profile) and it works fine. verified it with the duply --preview parameter which does not execute but merely prints the generated cmd lines. NOTE the missing --volsize 50 from the status cmd line. :~$ ./duply_dev/duply_wrap test status --preview Start duply.sh v2.5.6dev, time is 2025-08-28 10:54:23. Using profile '/home/dup/.duply/test'. SNIP --- Start running command STATUS at...
-
Incompatibility of conf settings MAX_FULLBKP_AGE, VOLSIZE with duplicity 3.0.4
-
i see. thanks! will have a deeper look.
-
Incompatibility of MAX_FULLBKP_AGE with duplicity 3.0.4
-
The problem combination is the MAX_FULLBKP_AGE or VOLSIZE feature of duply with for example the status command of duplicity. are you sure VOLSIZE raises an issue? afaics it is stripped for all non-backup commands.
-
Incompatibility of MAX_FULLBKP_AGE with duplicity 3.0.4
-
hey David, will try to reproduce and fix. just wanted to let you know that i've seen your report and appreciate it. THANKS! ..ede
-
thanks! you are totally right that this was caused by a configuration of our build infrastructure! sorry for the noise, i could locate the error and fix it. thank you very much ..ede
-
sure, have a look [edso@shell-21001 ~]$ cd jump-pilot/OpenJUMP2_snapshots/ # delete lot's of files from 2021 - 2024 [edso@shell-21001 OpenJUMP2_snapshots]$ rm -v OpenJUMP-*-202{1,2,3,4}* removed 'OpenJUMP-Portable-20210912-r4983(185dc45)-CORE.zip' removed 'OpenJUMP-Portable-20210912-r4983(185dc45)-PLUS.zip' SNIP removed 'OpenJUMP-Portable-20241229-r5299[473ad15]-CORE.zip' removed 'OpenJUMP-Portable-20241229-r5299[473ad15]-PLUS.zip' # listing is clean now [edso@shell-21001 OpenJUMP2_snapshots]$ ls...
-
deleted files in frs magically reappear
-
duply 2.5.5 is released.
-
duply 2.5.5 released
-
release 2.5.5
-
release 2.5.5
-
Duply (2.5.4) is not compatible with duplicity 3.0.4
-
Thanks! will release it as v2.5.5 soonish.
-
can you please try this dev version? i think i ironed it out. https://duply.net/tmp/duply.sh
-
it will be shown on every duplicity run. i am not going to anything about it. duplicity is telling you to upgrade ;)
-
moin Mischa, saw it. working on it. will release a fix. Thanks for the heads up!
-
thanks the error does mot occur anymore.
-
thanks, https://sourceforge.net/p/jump-pilot/discussion is accessible again. instantly stumbled over another issue. i can't change Admin-Discussion -> Options -> Posting-Policy. Results in an Error 500 see attached
-
thanks, https://sourceforge.net/p/jump-pilot/discussion is accssible again. instantly stumbled over another issue. i can't change Admin-Discussion -> Options -> Posting-Policy. Results in an Error 500 see attached
-
https://sourceforge.net/p/jump-pilot/admin/discussion/permissions Read Permission seems to have a blocked *anonymous user which i have no way to remove
-
https://sourceforge.net/p/jump-pilot/admin/discussion/permissions Read Permissions seems to have a blocked *anonymous user which i have no way to remove
-
project forum throws 403 when trying to access it
-
OpenJUMP 2.4.0 released
-
batch cmds with consecutive '_' fail WAS: Failure when parsing groupIn following and/or
-
good to hear. will be in the next release. happy new year ..ede
-
duply 2.5.4 released
-
duply 2.5.4 released
-
release 2.5.4
-
Failure when parsing groupIn following and/or
-
good to hear. will be in the next release. happy new year ..ede
-
nice catch Dominik, please try the latest snapshot. this should fix the issue. https://duply.net/tmp/duply.sh Thanks! ..ede
-
thanks SourceForge Support, everything is working as expected. sunny regards ..ede
-
hey SourceForge Support, we managed to set the appropriate DNS records and it seems that the redirection/enforcement is already set. would it be possible to disable this feature? we would be perfectly happy to offer https:// but if for some reason http:// would be the preferred option we do not want to deny this option to our user base. thanks! ..ede
-
thanks for the offer. we are currently trying to get access internally to the domains dns settings. as you are offering we would like to use both www.openjump.org and openjump.org. sunny regards
-
as HTTPS-support was a feature that used to work in the past, we vhost since at least 2014 with you, would you mind telling us when and why it was disabled? would you mind stating the conditions needed to "become eligible for the feature in the future"? thank you very much.
-
project web hosting broken HTTPS certificate
-
OpenJUMP 2.3.0 released
-
Broken GPG_OPTS in duply 2.5.2 under macOS Sonoma
-
should be fixed in v2.5.3 . released now.
-
duplicity complains about GPG_OPTS for status command
-
should be fixed in v2.5.3 . released now.
-
release 2.5.3
-
can you guys please test if the new devel version fixes the issue for you? https://duply.net/tmp/duply.sh
-
can you guys please test if the new devel version fixes the issue for you? https://duply.net/tmp/duply.sh
-
posted a WORKAROUND here https://sourceforge.net/p/ftplicity/bugs/140/#3138. working on a fix.
-
hey Milan, turns out that the new command line parser used by duplicity is at fault and even worse that it will probably not be fixed as it was designed that way intentionally. good news for you though. since quite some time --pinentry-mode=loopback is not needed anymore as duplicity will set it itself if needed. so no need for duply to provide it anymore. PROBLEMSOLVED :) at least for you. will need to patch up duply. as a permanent fix (some) option values given to duplicity will need the equal...
-
hey Milan, turns out that the new command line parser used by duplicity is at fault and even worse that it will probably not be fixed as it was designed that way intentionally. good news for you though. since quite some time --pinentry-mode=loopback is not needed anymore as duplicity will set it itself if needed. so no need for duply to provide it anymore. PROBLEMSOLVED :) not really. will need to patch up duply. as a permanent fix (some) option values given to duplicity will need the equal sign...
-
i see. while duplicity internally sets --pinentry-mode=loopback duply for the tests does not. i wonder why i never stumbled over that.
-
you are totally right. but seeing it as a rarely used option , --pinentry-mode=loopback is set by duplicity these days, i'll prefer to have upstream fix the issue properly. as a workaround you probably may comment #GPG_OPTS=... and add the "working" --gpg-options='--compress-algo=bzip2 --bzip2-compress-level=9' to latest conf entry DUPL_PARAMS=... if i find time i might have a look at it at the duplicity issue but can't promise anything. life's keeping me busy just now.
-
you are totally right. but seeing it as a rarely used option , --pinentry-mode=loopback is set by duplicity these days, i'll prefer to have upstream fix the issue properly. as a workaround you probably may comment #GPG_OPTS=... and add the "working" --gpg-options='--compress-algo=bzip2 --bzip2-compress-level=9' to latest conf entry DUPL_PARAMS=... if i find time i might have a look at it at duplicity but can't promise anything. life's keeping me busy just now.
-
no Nuno, it's a bug in duplicity not accepting some --name value pairs separated by space anymore. the alternative --name=value still works. please read the ticket https://gitlab.com/duplicity/duplicity/-/issues/795 what confuses me is that the error is supposed to be fixed in duplicity. but furthermore, wrt. "--pinentry-mode" , this does indeed not need be set anymore as duplicity will do that automagically since some time. need to clean that from the conf template, will do :)
-
no Nuno, it's a bug in duplicity not accepting some --name value pairs separated by space anymore. the alternative --name=value still works. please read the ticket https://gitlab.com/duplicity/duplicity/-/issues/795 what confuses me is that the error is supposed to be fixed in duplicity.
-
duplicity complains about GPG_OPTS for status command
-
this is the same duplicity issue as https://sourceforge.net/p/ftplicity/bugs/140/ which is according to the duplicity changelog fixed in v2.2.0 are you sure that you are running duplicity 2.2.2 ? can you post the complete output with versions and all? feel free to post to the duplicity ticket wrt. the underlying issue https://gitlab.com/duplicity/duplicity/-/issues/795
-
Broken GPG_OPTS in duply 2.5.2 under macOS Sonoma
-
Broken GPG_OPTS in duply 2.5.2 under macOS Sonoma
-
hey Ralf, the command line generated by duply is fine. i verified that duplicity is at fault here. i opened a ticket in that regard https://gitlab.com/duplicity/duplicity/-/issues/795 . consider downgrading duplicity, if the option is important to you or wait for the fix :) will close this as invalid as duply is working as expected. ..sunny regards ede
-
moin Ralf, please run duply backup command with parameter --preview and the offending GPG_OPTS enabled. post the complete output here after. i need versions outputs as well. thanks.. ede
-
moin Ralf, please run duply backup command with parameter --preview and the offending GPG_OPTS enabled. post the output here after. thanks.. ede
-
release 2.5.2
-
closing this after no further responses as fixed. will be released in v2.5.2
-
Upgrading to duply 2.5.1 from 2.4.1 breaks gpg password?
-
closing this after no further responses as fixed.
-
hey Jacob, would you mind telling me the OS and awk name/version of this box? ..thx ede On 11.11.2023 14:21, edgar.soldin@web.de wrote: thanks Jacob, seems like your awk is somewhat more delicate :) please try the snapshot https://duply.net/tmp/duply.sh thxagn! ..ede On 11.11.2023 14:12, Jacob Godserv wrote: Hey ede, I had the same issue and this appears to be a good fix. However, I get a lot of spurious output at the start of a "verify" run: |Signingdisabled.NoGPG_KEYentriesinconfig. awk:cmd.line:1⚠️regexpescapesequence\,'isnotaknownregexpoperator...
-
thanks Jacob, seems like your awk is somewhat more delicate :) please try the snapshot https://duply.net/tmp/duply.sh thxagn! ..ede On 11.11.2023 14:12, Jacob Godserv wrote: Hey ede, I had the same issue and this appears to be a good fix. However, I get a lot of spurious output at the start of a "verify" run: |Signingdisabled.NoGPG_KEYentriesinconfig. awk:cmd.line:1⚠️regexpescapesequence\,'isnotaknownregexpoperator awk:cmd.line:1:warning:regexpescapesequence_'isnotaknownregexpoperator awk:cmd.line:1⚠️regexpescapesequence\@'isnotaknownregexpoperator...
-
Read timed out when loading Geoportale Nazionale WMS
-
Do you know hot to combine more than one WMS additional parameter: I tried with ;,&? without success the ampersand (&) should work to concatenate url parameters like e.g. WIDTH=956&HEIGHT=410
-
hey Eric, thanks for the report. can you please test this snapshot? https://duply.net/tmp/duply.sh thanks!.. ede
-
good point Jukka, tried myself. default timeout in OJ is 5 seconds. this times out. you can raise the value per (e.g. in english menu) Customize -> Options -> Network properties -> Timeout -> Read timeout (ms) . raising it to 60s = 60.000 loads the layer after about 10s or so. does that solve your issue Roberto?
-
good point Jukka, tried myself. default timeout in OJ is 5 seconds. this times out. you can raise the value per (e.g. in english menu) Customize -> Options -> Network properties -> Timeout -> Read timeout (ms) . raising it to 60s = 60.000 loads the layer after about 10s or so. does that sove your issue Roberto?
-
hey Roberto, which OJ version are you using? assuming it is OJ 2.x please open an issue on https://github.com/openjump-gis/openjump/issues and i will have a look. we switched platform with the OJ 2.x release. OJ1.x is not actively maintained anymore. ..ede
-
hey Roberto, which OJ version are you using? assuming it is OJ 2.x please open an issue on https://github.com/openjump-gis/openjump/issues and i will have a look. we switched platform with the =J 2.x release. OJ1.x is not acoitvely maintained anymore. ..ede
-
Version detection fails with duplicity from official ppa
-
over-quoting duplicity_params_conf causes commands to fail
-
duply 2.5.1 released
-
release 2.5.1
-
loosend the awk regex somewhat. please try the new devel version https://duply.net/tmp/duply.sh and check if your problem persists. Thanks! ..ede
-
hey Eric, thanks for your report. please try the new devel version https://duply.net/tmp/duply.sh and check if your problem persists. Thanks! ..ede
-
seems to be a duplicity issue. it's supposed to put out duplicity 2.1.2 . will relay it to the duplicity maintainer and keep this open for now.
1 >
