** Changed in: rsync (Ubuntu Jammy)
Status: New => Invalid
** Changed in: rsync (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: rsync (Ubuntu Lunar)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
This bug was fixed in the package backintime - 1.2.1-3ubuntu0.3
---
backintime (1.2.1-3ubuntu0.3) jammy-security; urgency=medium
* Fix compatibility with rsync security update (LP: #2009756)
- debian/patches/rsync_compat.patch: fix changes to argument protection
in common/
This bug was fixed in the package backintime - 1.3.2-0.1ubuntu0.2
---
backintime (1.3.2-0.1ubuntu0.2) kinetic-security; urgency=medium
* Fix compatibility with rsync security update (LP: #2009756)
- debian/patches/rsync_compat.patch: fix changes to argument protection
in c
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756
Title:
backups fail since latest rsync security update
Status in backintime package
Great, I'll release the updates monday morning. Thanks for testing!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756
Title:
backups fail since latest rsync security up
Looks good now, works for me on jammy. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756
Title:
backups fail since latest rsync security update
Status in backi
I have fixed the typo, and have uploaded new packages to the PPA listed
above. I've run a successful backup with them on both jammy and kinetic.
Could you please confirm they fix the issue for you? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
Oh whoops, sorry about that, I'll upload a fixed version first thing
tomorrow (after at least installing it this time).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756
Hi Mark,
I just tested it. Unfortunately the package fails to install:
```
Preparing to unpack .../backintime-common_1.2.1-3ubuntu0.2_all.deb ...
Unpacking backintime-common (1.2.1-3ubuntu0.2) over (1.2.1-3ubuntu0.2) ...
Preparing to unpack .../backintime-qt_1.2.1-3ubuntu0.2_all.deb ...
Unpacking
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756
Title:
backups fail since latest rsync security update
Sta
Dear Marc,
thanks for explaining and your patience.
I think I'm a bit blinded here because of my "Debian stable" experience.
I also mixed up the terms "stable" and "LTS" which seems not to be the
same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Some users only have the -security pocket enabled, and not -updates, so
when a fix is required for a regression introduced by a security update,
it needs to go to the -security pocket. It doesn't in any way mean BIT
had a security issue.
--
You received this bug notification because you are a mem
I'm not happy about the situation. But maybe I'm to conservative about
it.
There is no known security problem with BIT. So you shouldn't use the
security repo to update it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyn
Hi @agateau,
I have uploaded fixed backintime packages for jammy and kinetic to the
security team PPA here:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages
Once they are finished building, could you give them a try? If they work
correctly, I will release them.
Tha
I opened a "question" at the rsync package
https://answers.launchpad.net/ubuntu/+source/rsync/+question/705772
And I also informed the rsync upstream maintainer about the situation.
As a workaround until Ubuntu fixed the rsync-update-bug I would advice to use
Back In Time from upstream (GitHub r
15 matches
Mail list logo
