Hi,
This is the first message on the new list. I've merged everything we
had ready and it tests OK. Not sure if you get a message when that
happens, so heads up. Let me know.
I've run it and I don't think we introduced any errors. Please check it
out. I'm still new to bzr used this way, so I
Peter Schuller wrote:
>>> ~/.duplicity//cache - cache files, removable at any time
>>> ~/.duplicity//config - backup profile configs, etc
>>> ~/.duplicity//checkpoints - checkpoint info
>> That really should be:
>> $XDG_CACHE_HOME/duplicity/ (aka ~/.cache/duplicity/),
>> $XDG_CONFIG_HOME/duplici
Peter Schuller wrote:
>> Sounds like the smart-archive-dir already uses never-before-used paths
>> for the archive metadata (since --name defaults to a hash, which
>> hadn't happened before I believe). Which would make it an excellent
>> time to switch the archive-dir default of ~/.duplicity to
>>
Peter Schuller wrote:
>> What I'd hate to see happen is that debian/rhel/etc makes a new
>> release and ends up grabbing such a "not recommended" release because
>> it was the latest version at the right (wrong) moment. The result
>> would likely be (1) support hell for 4+ years, (2) unnecessary ba
Michael Terry wrote:
> 2009/6/25 Kenneth Loafman :
>> I'll make a 'stable' branch ending at 0.5.18 and leave 'trunk' as is.
>
> There might be a slight advantage to making a '0.5' and '0.6' LP
> series (for stability of URLs over time
Peter Schuller wrote:
>> On the website I made the distinction between stable and development
>> several days ago. I think it needs to be reflected in a series as well.
>> Until the trunk series is stable, we'll need to maintain the 0.5
>> series, and so on.
>
> Cool. Sorry, while I do check the
Michael Terry wrote:
> 2009/6/25 Kenneth Loafman :
>> No problem. I am having a bit of a problem with LP at the moment.
>> Their inflexibility about deletions may mean that we can't use stable as
>> the name of a branch. It appears that since I created and deleted two
&
ine
90, in put
remote_path = os.path.join(urllib.unquote(self.parsed_url.path.lstrip('/')),
remote_filename).rstrip()
File "/usr/lib/python2.6/posixpath.py", line 65, in join
if b.startswith('/'):
AttributeError: 'NoneType' object has no attribute &#x
** Branch linked: lp:duplicity
--
List of Orphaned Files Growing
https://bugs.launchpad.net/bugs/388992
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: In Progress
Bug de
Folks,
I've just implemented a sync command which will solve some of the
problems with the local archive being out of sync (constantly growing
list of sig files). Like cleanup, it has to be run separately from the
normal flow.
Should it be its own command, or is this something we just need to do
Sounds like a workable plan. I don't see any bad side effects from it.
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Milestone: None => 0.6.1
--
Error creating directory
https://bugs.launchpad.net/bugs/393372
You received this bug notification because
** Changed in: duplicity
Milestone: None => 0.6.1
** Changed in: duplicity
Status: Confirmed => Fix Committed
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
AttributeError: 'NoneType' object has no attribute
Michael Terry wrote:
> 2009/6/30 Kenneth Loafman :
>> Or, should we check and refuse to run until synchronized?
>
> This might be a good option if sync'ing is ever dangerous or the wrong
> thing to do. So the user can check out the situation and see why
> duplicity thi
** Changed in: duplicity
Milestone: None => 0.6.1
--
Unable to backup
https://bugs.launchpad.net/bugs/388034
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in Déjà Dup: Invalid
Status in duplicity - Bandwidth Efficient
This was fixed in 0.6.1 with the addition of automatic archive sync at
startup.
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => Fix Committed
** Changed in: duplicity
Milestone: None => 0.6.1
--
Fix 'list-current-files' with missi
** Changed in: duplicity
Status: New => Fix Committed
--
Error creating directory
https://bugs.launchpad.net/bugs/393372
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Bac
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: In Progress => Fix Committed
** Changed in: duplicity
Milestone: None => 0.6.1
--
Asynchronous upload not working properly
https://bugs.launchpad.net/bugs/387102
You received this bug notific
duplicity will now sync the archive metadata with the remote metadata as
of 0.6.1. This stops the list from growing since the missing metadata
is now there.
** Changed in: duplicity
Status: In Progress => Fix Committed
** Changed in: duplicity
Milestone: None => 0.6.1
--
List of Orp
** Changed in: duplicity
Status: In Progress => Fix Committed
** Changed in: duplicity
Milestone: None => 0.6.1
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
python2-6 issue / UTF-8 charset / Ubuntu 9.04
https://bugs.launchpad
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
duplicity crashed with ValueError in port()
https://bugs.launchpad.net/bugs/229826
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Sta
Do we have any documentation on what GIO schema's look like?
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Milestone: None => 0.6.1
--
Add gio backend
https://bugs.launchpad.net/bugs/383419
You received this bug notification because you are a member o
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Milestone: None => 0.6.1
--
Add InfoCodes for upload events
https://bugs.launchpad.net/bugs/383412
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplic
** Changed in: duplicity
Milestone: None => 0.6.1
--
Add SFTP-only backend
https://bugs.launchpad.net/bugs/387218
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix C
** Branch linked: lp:duplicity
--
Error creating directory
https://bugs.launchpad.net/bugs/393372
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix Committed
Bug descri
** Branch linked: lp:duplicity
--
Unable to backup
https://bugs.launchpad.net/bugs/388034
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in Déjà Dup: Invalid
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix C
** Branch linked: lp:duplicity
--
Fix 'list-current-files' with missing archive dir
https://bugs.launchpad.net/bugs/379386
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup:
** Branch linked: lp:duplicity
--
Add SFTP-only backend
https://bugs.launchpad.net/bugs/387218
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix Committed
Bug descripti
** Branch linked: lp:duplicity
--
Asynchronous upload not working properly
https://bugs.launchpad.net/bugs/387102
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix Commi
** Branch linked: lp:duplicity
--
python2-6 issue / UTF-8 charset / Ubuntu 9.04
https://bugs.launchpad.net/bugs/378940
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix
** Branch linked: lp:duplicity
--
Add gio backend
https://bugs.launchpad.net/bugs/383419
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix Committed
Bug description:
It
** Branch linked: lp:duplicity
--
Add InfoCodes for upload events
https://bugs.launchpad.net/bugs/383412
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Backup: Fix Committed
Bug
It's mentioned on the website... is that what you meant?
...Ken
Michael Terry wrote:
> Hello! I just updated the duplicity-team PPA for 0.6.01. (it may not
> be visible this second on the PPA page, but they're all pushed)
>
> Has this PPA been publicized? It probably should be (since it can b
list.
>
> -mt
>
> 2009/7/1 Kenneth Loafman :
>> It's mentioned on the website... is that what you meant?
>>
>> ...Ken
>>
>> Michael Terry wrote:
>>> Hello! I just updated the duplicity-team PPA for 0.6.01. (it may not
>>> be visible
Public bug reported:
Certain backends require other modules, ncftp for FTP, sftp for SSH,
etc.. If the user is not going to be using these modules, it should not
be a requirement to have them on the system. I propose that we surround
all backend imports with a try/except and that all modules sho
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
AttributeError: 'NoneType' object has no attribute 'startswith'
https://bugs.launchpad.net/bugs/392905
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
List of Orphaned Files Growing
https://bugs.launchpad.net/bugs/388992
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficien
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
python2-6 issue / UTF-8 charset / Ubuntu 9.04
https://bugs.launchpad.net/bugs/378940
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Ban
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
Unable to backup
https://bugs.launchpad.net/bugs/388034
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in Déjà Dup: Invalid
Status in duplicity - Band
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
Error creating directory
https://bugs.launchpad.net/bugs/393372
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encr
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
Add SFTP-only backend
https://bugs.launchpad.net/bugs/387218
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypt
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
Asynchronous upload not working properly
https://bugs.launchpad.net/bugs/387102
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidt
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
Add InfoCodes for upload events
https://bugs.launchpad.net/bugs/383412
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficie
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
Add gio backend
https://bugs.launchpad.net/bugs/383419
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity - Bandwidth Efficient Encrypted Bac
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
Fix 'list-current-files' with missing archive dir
https://bugs.launchpad.net/bugs/379386
You received this bug notification because you are a member of
duplicity-team, which is subscribed to duplicity.
Status in duplicity -
There should also be a 'duplicity list-backends' that will show available
backends and their protocol strings, something like:
ftpbackendftp://
sshbackend ssh:// scp://
...and so on...
--
Backend imports should be made optional
https://bugs.launchpad.net/bugs/394757
You received this bug n
Michael Terry wrote:
> Can we turn off bugmail to this list? It's a little spammy.
>
> Is the team subscribed explicitly to the mail? Or is it because the
> team is 'bug supervisor' for the project?
>
> If we need a bug supervisor team, maybe create a new team/mailing list?
Yeah, all the statu
Peter Schuller wrote:
>> Automatic sync should never be dangerous and would be the right thing to
>> do, especially with an upgrade from 0.5 to 0.6 series. It only copies
>> files, never removes them or overwrites them.
>
> Just to revisit this discussion; my suggested changes to synching does
>
Peter Schuller wrote:
>> I have an almost complete solution committed:
>>
>>
>> http://bazaar.launchpad.net/~scode/duplicity/archive-sync-removelocal/revision/553
>>
>> The problem is that the "resolution" of base name into local + remote
>
> So hopefully I fixed it:
>
>
> http://bazaar.la
Peter Schuller wrote:
>>> is a correct transcribation of the previous version whichi called
>>> copy_raw() if the file was a manifest.
>> In the normal course of processing the difference between manifest and
>> sigtar are necessary in the local side. The manifest is not compressed
>> and the sigt
Kenneth Loafman wrote:
> Peter Schuller wrote:
>>>> is a correct transcribation of the previous version whichi called
>>>> copy_raw() if the file was a manifest.
>>> In the normal course of processing the difference between manifest and
>>> sigtar are
Peter Schuller wrote:
> I did an incremental against my test repo and aborted it. First off
> the collection status still showed a "bogus" incremental:
>
> Type of backup set:Time: Num volumes:
> Full Sat Jul 4 18:25:38 2009
Peter Schuller wrote:
> Some more incremental investigation:
>
>> Traceback (most recent call last):
>> File "./duplicity-bin", line 1197, in
>> with_tempdir(main)
>> File "./duplicity-bin", line 1190, in with_tempdir
>> fn()
>> File "./duplicity-bin", line 1172, in main
>> incr
Peter Schuller wrote:
> I'm not sure why you think this is the problem though. I mean it's
> picking up empty files, and even if flush/fsync was somehow broken, a
> killed duplicity would still be able to leave empty files behind on a
> system where it wasn't. I'll check the source and see where th
Kenneth Loafman wrote:
> Peter Schuller wrote:
>> I'm not sure why you think this is the problem though. I mean it's
>> picking up empty files, and even if flush/fsync was somehow broken, a
>> killed duplicity would still be able to leave empty files behind on a
One of the reasons I wanted to get on Launchpad was to get to a system
that used Bazaar for its VCS. The reason for Bazaar is that it will let
you move things around without losing the history built up for the code.
Now that duplicity is on Launchpad, I'd like to look into reorganizing
duplicity
Peter Schuller wrote:
> Ok;
>
> I suggest the following (I've started a bit in my working copy):
>
> * Change config.py.tmpl to be config.py, and have it
> execfile('config_loca.py') if it exists. This allows putting your
> own local configuration in a file which is not going to be a
> perp
Team,
What do you think should be the next major development thrust in
duplicity? I've got some generic ones, but you're in the trenches with
more users than I see, so let's hear from you and get something going.
My ongoing objectives, not in order of importance:
1) Get async working so that we
Michael Terry wrote:
> 2009/8/4 Kenneth Loafman :
> In fact, having some sort of formal 'code-freeze a week before a
> release' may be useful for both my own testing (and maybe user
> testing, could announce and put in a testing PPA) and for translators
> to have time to
Larry Gilbert wrote:
> In the trenches with users? In my case, I *am* the user. :-)
OK, welcome aboard.
> (By the way, what do you think of Launchpad's "Blueprints" feature?
> Would that be a good venue for promoting ideas, or do you prefer we
> stick to the mailing list?)
Putting it in Bluepri
Michael Terry wrote:
> 2009/8/5 Kenneth Loafman :
>> So far, so good on the feedback. Don't be afraid to complain if I'm
>> doing something wrong. I guarantee it won't be the first time.
>
> So long story short, please consider how any change affects users th
I made the release on LP based on the following changes, no announcement
yet, will wait for you guys to check it out. No surprises, but I'll
start doing things this way so you have a first look. Will put this out
in a week, or sooner if you want.
I'm sure some will notice, but not too many, I ho
Michael Terry wrote:
> 2009/8/6 Kenneth Loafman :
>> I made the release on LP based on the following changes, no announcement
>> yet, will wait for you guys to check it out. No surprises, but I'll
>> start doing things this way so you have a first look. Will put this o
Michael Terry wrote:
> 2009/8/24 Rob Oakes :
>> How does does the process work? Are newly detected files somehow added to
>> the underlying "full" backup? Do the incremental snapshots exist in
>> independence, each containing only the data about how files have changed
>> relative to the full back
Folks,
OK, I forgot about 0.5.19, spent most of last week wondering to myself
what it was that I was supposed to get done and did not. This time I'm
putting it on the calendar. A 3-day migraine makes one forgetful. ;-)
I've pushed both trunk and stable to the point that they need to be for
the
Folks,
We now have three series running:
0.5-series -- supported but not enhanced
0.6-series -- current stable release, will be enhanced
0.7-series -- next series in development, below
At the moment 0.6 and 0.7 are identical.
Please don't push to the trunk or stable branches any more.
lp:d
Folks,
We now have three series running:
0.5-series -- supported but not enhanced
0.6-series -- current stable release, will be enhanced
0.7-series -- next series in development, below
At the moment 0.6 and 0.7 are identical.
lp:duplicity is the default branch (0.7-series). For now, it is
Sorry, this was the version going to duplicity-talk.
Kenneth Loafman wrote:
> Folks,
>
> We now have three series running:
> 0.5-series -- supported but not enhanced
> 0.6-series -- current stable release, will be enhanced
> 0.7-series -- next series in development,
Folks,
This seems like a workable idea for coalescing incremental backups on
the fly, without user intervention.
A very simple case:
Full Backup has files ABCD and blocks a1..a23, b1..b5, c1, d1
Inc1 Backup has files AC and blocks a4,a7,c1
Inc2 Backup has files AD and blocks a4,a8,d1 (a
I'm assigning this to the entire duplicity-team since we'll need all of
your help in getting this into 0.7-series. I'm working on getting the
initial patch to work correctly with all of the unit tests, in some
cases changing the tests to fit, then I'll push a version to 0.7-series,
close to what P
Michael Terry wrote:
> Hello! I was talking to Rob Oaks from Time Drive a while back about
> possibly merging efforts. That sort of broke down because I said I
> was too invested in my 'call-duplicity-then-interpret-logs' method and
> he was too invested in his 'use-duplicity's-Python-module' met
** Branch linked: lp:duplicity
--
[PATCH] par2 creating support
https://bugs.launchpad.net/bugs/426282
You received this bug notification because you are a member of
duplicity-team, which is a bug assignee.
Status in duplicity - Bandwidth Efficient Encrypted Backup: In Progress
Bug description:
0.6 is stable now and 0.5 is still supported for a while. I need to
update the webpage to show that fact. 0.7 is the development version.
...Ken
Larry Gilbert wrote:
> I and a package maintainer for MacPorts are in disagreement over which
> version of Duplicity should really be considered "stab
Web page is updated. Hope it clears up the issue.
The 0.5 series is done. There will be no changes to that code.
0.6 is stable and will be maintained, but not enhanced.
0.7 is future, i.e. development trunk.
...Ken
Kenneth Loafman wrote:
0.6 is stable now and 0.5 is still supported for a
Thanks for the patches. What exactly is the gigabyte limit you refer
to?
--
[PATCH] par2 creating support
https://bugs.launchpad.net/bugs/426282
You received this bug notification because you are a member of
duplicity-team, which is a bug assignee.
Status in duplicity - Bandwidth Efficient Encr
Michael Terry wrote:
> Ken: Please look at lp:~mterry/duplicity/list-old-chains -- it's a
> first pass at keeping old chains and letting you list their contents.
> The only missing bit from my perspective is an error if you try to
> list from a backup chain that doesn't have a signature. I'll add
edgar.sol...@web.de wrote:
>
>> Not sure that keeping the sig files is the way to go as a default
>> option, and we'd run into the same problems as --archive-dir if we make
>> it optional.
>
> currently keeping sig files is no option, or? So it's a whole different
> scenario, isn't it?
Not reall
d thus risk
> forgetting it), but you still have an easy solution for recapturing
> space.
>
> Eh?
>
> -mt
>
> 2009/10/20 :
>> On 20.10.2009 22:13, Kenneth Loafman wrote:
>>> edgar.sol...@web.de wrote
>>>>> Not sure that keeping the
p passing the arg every time (and thus risk
>> forgetting it), but you still have an easy solution for recapturing
>> space.
>>
>> Eh?
>>
>> -mt
>>
>> 2009/10/20:
>>> On 20.10.2009 22:13, Kenneth Loafman wrote:
>>>>
>>>> ed
Michael Terry wrote:
> 2009/10/22 Kenneth Loafman :
>> I like the idea of your Solution D. That would actually encourage
>> people to run cleanup on a normal basis and that's a "good thing".
>
> OK. I like it too. I'll work on a patch. If I can
Michael Terry wrote:
> 2009/10/22 Kenneth Loafman :
>> I planned on putting out .06 at the "end of the week". I don't think a
>> couple of days would matter much. What do you think you'll need?
>
> I could have a patch for you by end of day (EST
Anna,
The normal way to request help is through one of the public lists at
http://lists.nongnu.org/mailman/listinfo/duplicity-talk
This is actually a private list for the use of duplicity developers. I
authorized this post without looking too closely, but I'll try to get
you started on the resto
Michael Terry wrote:
> 2009/10/22 Kenneth Loafman :
>> I planned on putting out .06 at the "end of the week". I don't think a
>> couple of days would matter much. What do you think you'll need?
>
> Not to be pesky or anything, but things didn't
I'm shooting for the end of the month. There are some problems with the
test suite that need to be resolved, plus the Webdav problem is
important to fix.
...Ken
Michael Terry wrote:
> Is there a planned date for 0.6.07?
> -mt
>
> ___
> Mailing list: h
Question #103229 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/103229
Status: Expired => Open
Kenneth Loafman changed the question status:
Sorry for the delay.
I would be happy to take your patches for rdiffdir or duplicity either
one. I don't have time to
Question #108409 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/108409
Status: Open => Answered
Kenneth Loafman proposed the following answer:
Alex Robinson wrote:
> New question #108409 on Duplicity:
> https://answers.launchpad.net/duplicity/+questi
Question #109951 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/109951
Kenneth Loafman proposed the following answer:
This is normal Unix behavior since you only redirected stdout, not
stderr. To redirect both, use:
duplicity options src tgt 2>&1 >> logfi
I never got around to answering this. I've been busy. Sorry.
I really should make at least one more 0.6 release with some fixes, then
concentrate on 0.7. I've held off on 0.7 because I was not sure which
direction it should go, but it really does need to either get scrubbed,
or get developed.
Michael Terry wrote:
> On 15 May 2010 11:06, Kenneth Loafman wrote:
>> As to snapshot tarballs, that would be nice. Is that something we could
>> set up on LP for nightly or weekly builds. Could it be triggered only
>> if there was a change?
>
> Yes... There is a w
Question #109976 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/109976
Kenneth Loafman posted a new comment:
That scenario is not possible, however, you can use multiple public
keys, keep one to yourself, and give one to others.
--
You received this question
Question #109976 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/109976
Status: Expired => Answered
Kenneth Loafman changed the question status:
Did not see this one.
--
You received this question notification because you are a member of
duplicity-team, which is
** Changed in: duplicity
Status: New => In Progress
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
** Changed in: duplicity
Milestone: None => 0.6.09
--
Unknown
Tried the merge. Looks like we're using differ bzr versions.
k...@stealth:~/workspace/duplicity-0.7-series$ bzr merge
lp:~mterry/duplicity/backend-log-codes
Doing on-the-fly conversion from RemoteRepositoryFormat(_network_name='Bazaar
repository format 2a (needs bzr 1.16 or later)\n') to
Repos
That one works.
Gonna need to see about upgrading formats, and if the version of bzr I
run supports it.
Michael Terry wrote:
> OK, try lp:~mterry/duplicity/backend-log-codes2
>
> I figured no reason to file new merge request? Same code, but not an
> upgraded branch. Not sure how this branch go
Hi,
Is there anyone out there that requires an earlier version of bzr than
2.x? I'm thinking of upgrading the branches to the latest format, which
means that nothing earlier than bzr 2.x would support it.
...Thanks,
...Ken
signature.asc
Description: OpenPGP digital signature
Question #115018 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/115018
Status: Open => Answered
Kenneth Loafman proposed the following answer:
There were some minor tweaks to the manifest file format to support
restart operations in the latest revisions. Go
Upgrade of 0.6-series and 0.7-series is in progress.
Kenneth Loafman wrote:
> Hi,
>
> Is there anyone out there that requires an earlier version of bzr than
> 2.x? I'm thinking of upgrading the branches to the latest format, which
> means that nothing earlier than bzr
Question #115018 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/115018
Status: Open => Answered
Kenneth Loafman proposed the following answer:
If I understand your question, you're trying to work with a 0.6x archive
using 0.4x software. That would cause this
Peter Schuller wrote:
>> I am looking for a way to verify that the backup could restore without error.
>>
>> I now use Duplicity as my only backup mechanism. It would be excellent if,
>> once every so often, I could run something that:
>> (1) did a backup (so that we knew the remote location *shou
Question #116587 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/116587
Kenneth Loafman proposed the following answer:
Peter Schuller wrote:
>> I am looking for a way to verify that the backup could restore without error.
>>
>> I now use Duplicity
Question #118161 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/118161
Status: Open => Answered
Kenneth Loafman proposed the following answer:
The backup type you want is a differential backup and duplicity does not
support those yet.
A full backup will d
1 - 100 of 866 matches
Mail list logo
