Re: [lxc-users] ?==?utf-8?q? lxd 2.15 broke "lxc file push -r"?

2017-06-29 Thread Stéphane Graber 
On Thu, Jun 29, 2017 at 06:16:05AM +, Tomasz Chmielewski wrote:
> On Thursday, June 29, 2017 13:30 JST, Stéphane Graber  
> wrote: 
>  
> > Hmm, so that just proves that we really more systematic testing of the
> > way we handle all that mess in "lxc file push".
> > 
> > For this particular case, my feeling is that LXD 2.5's behavior is
> > correct. 
> 
> OK, I can see we can restore "2.14 behaviour" with an asterisk, i.e.:
> 
> lxc file push -r /tmp/testdir/* container/tmp
> 
> Which makes "lxc file push -r" in 2.15 behave similar like cp.
> 
> 
> Before, 2.14 behaved similar like rsync.
> 
> 
> So can we assume, going forward, the behaviour won't change anymore? :)

Yeah, it should be safe to assume that "lxc file push" will behave like
"cp", if it doesn't, we'll consider it a bug and fix :)

-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com


signature.asc
Description: PGP signature
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] ?==?utf-8?q? lxd 2.15 broke "lxc file push -r"?

2017-06-29 Thread Tomasz Chmielewski 
On Thursday, June 29, 2017 13:30 JST, Stéphane Graber  
wrote: 
 
> Hmm, so that just proves that we really more systematic testing of the
> way we handle all that mess in "lxc file push".
> 
> For this particular case, my feeling is that LXD 2.5's behavior is
> correct. 

OK, I can see we can restore "2.14 behaviour" with an asterisk, i.e.:

lxc file push -r /tmp/testdir/* container/tmp

Which makes "lxc file push -r" in 2.15 behave similar like cp.


Before, 2.14 behaved similar like rsync.


So can we assume, going forward, the behaviour won't change anymore? :)


Tomasz Chmielewski
https://lxadm.com
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users