@SRU team, is this good to move to jammy from jammy-proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009885
Title:
Timeshift 21.09.1-1 broken after Rsync upgrade to
As Ralf mentioned below, I too confirm it works now as intended. Thanks
for fixing it. All best.
Em 27/04/2024 04:28, Ralf W. escreveu:
> Hello Timo,
>
> after allowing packages from 'proposed' I manually upgraded these
> packages:
>
> rsync (version 3.2.3-8ubuntu3) ... upgraded to
Hello Timo,
after allowing packages from 'proposed' I manually upgraded these
packages:
rsync (version 3.2.3-8ubuntu3) ... upgraded to version
3.2.7-0ubuntu0.22.04.2
timeshift (version 21.09.1-1) ... upgraded to version 21.09.1-1ubuntu1
(rsync had previously been held back)
Set the locale variables to de_DE.UTF-8.
Then testing timeshift:
ubuntu@bronzor:~$ dpkg -l | grep timeshift
ii timeshift 21.09.1-1
amd64System restore utility
ubuntu@bronzor:~$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
Hello Rogério, or anyone else affected,
Accepted timeshift into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/timeshift/21.09.1-1ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Patch looks mostly good. Needed a couple of trivial changes (run update-
maintainer to deal with maintainer address in d/control, and add bug-ref
in d/changelog), but I've sponsored with those changes, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: timeshift (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: timeshift (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: timeshift (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member
** Changed in: timeshift (Ubuntu Jammy)
Assignee: (unassigned) => Ponnuvel Palaniyappan (pponnuvel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009885
Title:
Timeshift 21.09.1-1 broken
The attachment "timeshift_jammy_diff.patch" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch"
** Description changed:
[ Impact ]
Timeshift is broken after upgrade to 21.09.1-1. This is because of
a change in behaviour by rsync; rsync 3.2.4 changed how the locale's
worked out. From https://download.samba.org/pub/rsync/NEWS#3.2.4
"A long-standing bug was preventing rsync
** Description changed:
- Timeshift version 21.09.1-1 broken after rsync upgrade to
- 3.2.7-0ubuntu0.22.04.2. I had to upgrade Timeshift to version 22.11.2
- from Mint PPA to have it working again. Log messages tell rsync failed
- to create backup file. The behavior to note is that in the
Mantic and Noble have newer packages of timeshift which contain the
upstream fix [0].
Focal is at 3.1.3-8ubuntu0.7 which predates the rsync change (3.2.4). So
this issue affects just Jammy.
I've created a PPA with this fix for Jammy [1] to test. I'll do an SRU
for Jammy after confirmation.
[0]
Rudra, you are correct. The version installed for me is still from Mint
PPA. It shows as "local install" in Synaptic as I had already removed
the Mint PPA some time ago. Clearly it never got updated from Ubuntu
repo since it was replace by Mint package. Thanks for looking into this
and alert
This is due to a change in rsync 3.2.4, related to decimal separators in
European language locales vs English locales.
The upstream fix for this is here, and I am escalating it internally to get in
included in the Ubuntu releases:
https://github.com/teejee2008/timeshift/pull/904
On my Ubuntu 22.04 timeshift is still version 21.09.1-1 (02 Oct 2021).
No newer version is available from repository.
For the average user timeshift-snapshots stopped working ONE YEAR AGO -
afaik w/o any notification (apart from entries in log files). For this
reason, I consider this error to be
15 matches
Mail list logo
