Actually, as far as I can tell this failure affects a much wider set of
cases. I am seeing this on a standard install as long as the (default)
"use chroot" option is being used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Since this was fixed upstream and it doesn't affect any LTS Ubuntu
releases, I don't think it's important enough to do SRUs. Thank you!
(For LTSP users, that are affected by this: once a fixed rsync version
lands in Ubuntu, I'll copy it to the LTSP PPA for Groovy, so LTSP will
work there too)
--
If someone feels that it is still important to fix it Groovy, too,
please prepare the fix for 21.04 and follow the SRU procedure with or
without sponsorship request:
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure .
--
You received this bug notification because you are a member of Ubuntu
B
I've marked this bug having low importance due to the small set of cases
it can surface and the plan for fixing it is syncing the next upstream
release from Debian.
** Changed in: rsync (Ubuntu Groovy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a me
** Changed in: rsync (Ubuntu)
Importance: Undecided => Low
** Changed in: rsync (Ubuntu Groovy)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync
I'm not sure if the fix is worth backporting to Groovy since /proc is
typically mounted.
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lch
IMO both the new and old errors were accurate and this is just a behaviour
change in glibc rather than a regression.
Rsync upstream already adapted to the new glibc behaviour and unless glibc
upstream reverts the change this will stay the glibc behaviour in Ubuntu, too.
** Changed in: glibc (Ubu
** Also affects: glibc (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: rsync (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Bug watch added: Red Hat Bugzilla #1894485
https://bugzilla.redhat.com/show_bug.cgi?id=1894485
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubunt
Launchpad has imported 2 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=26401.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://h
Awesome, thanks for updating the bug tasks and tracking bug already
Alkis!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't
Hi Robie, thank you for the feedback,
I located an upstream bug report in glibc for this:
https://sourceware.org/bugzilla/show_bug.cgi?id=26401
** Bug watch added: Sourceware.org Bugzilla #26401
https://sourceware.org/bugzilla/show_bug.cgi?id=26401
** Also affects: rsync via
https://source
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This is interesting and I appreciate your investigation! I wonder though
if there's a third outcome here - that it's not a bug because the glibc
implementation of lchmod() requires /proc to be mounted, and if you
d
13 matches
Mail list logo
