Accepted.
** Changed in: hardy-backports
Status: In Progress = Fix Released
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy
I was actually thinking about this yesterday, wondering why it hadn't
moved forward. I've continued using version 3 without any problems
whatsoever, and that includes in mixed 2.6 and 3.0 environments. I will
point out a couple of things. The work that Chris Coulson did was for
version 3.0.3.
rsync 3 gracefully degrades and properly supports older rsync (as both a client
and server).
I know because we have a mix of rsync server in production, at my work,
transferring ~10Gb between sites.
As the machines are re-installed with Hardy, we are also installing our
own backport; it would
Ack from ubuntu-backporters then. Any motu can upload.
** Changed in: hardy-backports
Status: Triaged = In Progress
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug notification because you are a member of Ubuntu
Backports
To ease testing, I put rsync 3 for hardy in our PPA. Its available there
for anyone who wishes to grab it
That being said, I'm concerned about backporting rsync since it means
that if you have backports enabled, it might break rsync against non-
backport enabled hardy boxes. If we could have both
I'm glad work is being done on this. It is really useful that 3.0.* be
backported to Hardy. The protocol changed in 3.0.0. If a rsync =
3.0.0 tries to talk to a rsync = 3.0.0 at the other end the
communication can fail. I've had failures like:
2008/10/31 14:00:58 [19814] --acls requires
We can tick off dput already - I used that quite a bit on Hardy with
this backported version of rsync, and it seems to work with no
regressions.
The same goes for grsync - I used that quite extensively with this
version of rsync.
There isn't anything to test with ubuntu-standard and
livecd-rootfs is only used for building this live CD image isn't it?
Wouldn't that mean it didn't need to be tested with this version of
rsync?
Yes. No need to test that.
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug
Great job on the debdiff. Many people would have just arbitrarily
changed the version requirement and not hunted down why it was there.
Next question: How many of the rdepends does this break:
$ apt-cache rdepends rsync
rsync
Reverse Depends:
ubuntu-standard
vzctl
vserver-debiantools
No problem John - I've attached an updated debdiff with extra comment.
Thanks
** Attachment added: 3.0.3-2ubuntu1 to 3.0.3-2ubuntu1~hardy1.debdiff (updated)
http://launchpadlibrarian.net/17604962/3.0.3-2ubuntu1%20to%203.0.3-2ubuntu1%7Ehardy1.debdiff
--
please backport rsync 3 from Intrepid
I've also attached is the diff.gz
** Attachment added: rsync_3.0.3-2ubuntu1~hardy1.diff.gz
http://launchpadlibrarian.net/17604986/rsync_3.0.3-2ubuntu1%7Ehardy1.diff.gz
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug notification
** Attachment added: rsync_3.0.3-2ubuntu1~hardy1.dsc
http://launchpadlibrarian.net/17604989/rsync_3.0.3-2ubuntu1%7Ehardy1.dsc
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug notification because you are a member of Ubuntu
Debdiff looks good, only I'd suggest a comment for why the status stanza
was commented out (i.e. LSB too old in Hardy) in the init script for
confused sysadmins.
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug notification because
Marking this as Triaged since it build, installs, and runs and no
obvious regressions.
** Changed in: hardy-backports
Importance: Undecided = Wishlist
Status: New = Triaged
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug
Setting to Confirmed now (as it builds and installs) to await feedback
from testing.
I've been using this package quite a bit now to perform my usual backups
and synchronization of files between my desktop and my pendrive, with no
regressions noted so far.
** Changed in: hardy-backports
** Attachment added: 3.0.3-2ubuntu1 to 3.0.3-2ubuntu1~hardy1 debdiff
http://launchpadlibrarian.net/17308693/3.0.3-2ubuntu1%20to%203.0.3-2ubuntu1%7Ehardy1%20debdiff
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug notification
Debdiff added for source change backport.
Changes are:
1)Relaxed dependency on lsb-base in debian/control.
2)Removed use of status_of_proc() in debian/init.d (looking through the
changelog, it appears that this is the reason for having the lsb-base version
3.2-14 dependency).
Setting the bug
No apologies needed; I'm happy to see this moving forward. I've
switched almost all of my servers to your version. I haven't noticed
any regressions. In fact, all I've noticed is that the 2 major problems
I've experienced with rsync 2.6.9 have been disappeared:
1. Synchronizing very large
I have re-packaged rsync 3 for Hardy in PPA after changing the
dependency on lsb-base to make it installable. I have also removed the
use of status_of_proc() from the init script, as it seems from the
changelog that this is what the dependency was for. The package installs
and seems to work ok,
Marking incomplete due to changes to the source package required for the
backport.
** Changed in: hardy-backports
Status: New = Incomplete
--
please backport rsync 3 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/257211
You received this bug notification because you are a member
20 matches
Mail list logo
