debcrafters-packages team mailing list archive

[Michael Terry <2120709@xxxxxxxxxxxxxxxxxx>]

> The one thing you don't do is deliberately work around our policies by
> using a glorified `apt install` in your package to install your
> dependencies *at runtime*. It actually had consequences!!

That’s funny to hear because the reason PK support was added many years
ago was specifically by Canonical request to solve an issue with
duplicity dragging its feet on a Python3 port. So Deja Dup was shipped
in just the manner you describe to avoid having duplicity on the CD.

Clearly there is a different vibe now, but let’s not act like there is
some nefarious attempt to skirt policies.

> It might require some patching of upstream if they don't support a
> gracious fallback if restic isn't installed, but honestly that's for 
> the better, they definitely should.

That’s not likely to happen upstream. Restic is faster, more reliable,
and we already have introduced features that only it supports (FUSE
based restores). This is not a “we support either way” situation, this
is a transition. It can also create user confusion (and support
confusion) if some folks are getting one kind of backup and others a
different kind.

The appropriate thing is a hard dependency, as Deja Dup 49 does indeed
depend on Restic. But if you can’t do that for MIR reasons, there is the
PK approach. If you can’t do that either anymore, you can patch the
default backend to continue to be duplicity for now, but I can’t promise
that option will exist in the future as the transition continues. It
also might be confusing for users as they hear that 49.x has switched
backends but they don’t see it.

(If you are serious about patching the default backend - you can
override the “tool-when-new” gsetting to be “duplicity”. And restore
duplicity as a depends. But that’s my least favorite route.)

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/2120709

Title:
  deja-dup relies on universe dependencies

Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup package in Debian:
  New
Status in rclone package in Debian:
  New

Bug description:
  deja-dup, package in main, is installing its universe dependencies
  through packagekit at runtime rather than actually declaring them in
  Depends.

  [Original report]
  latest update to 49~alpha-1 make the backup failed.

  and previously backup to onedrive through duplicity and why its auto
  change using rclone?

  ProblemType: BugDistroRelease: Ubuntu 25.10
  Package: deja-dup 49~alpha-1
  ProcVersionSignature: Ubuntu 6.16.0-13.13-generic 6.16.0
  Uname: Linux 6.16.0-13-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.33.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 15 17:03:44 2025
  InstallationDate: Installed on 2025-06-04 (72 days ago)
  InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Daily amd64 (20250528)SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2120709/+subscriptions