Dear Maintainer,

Onedrive constantly spams desktop users with notifications that it's out of date.. please either remove the update check code and message. or consider removing the package from the distribution.

I note that upstream seem distribution hostile and note that the version of onedrive in debian is unsupported by them (which is fine) but if that's the case please patch out their update notifier.

reference: https://github.com/abraunegg/onedrive/blob/master/docs/ubuntu-package-install.md

Regards
Grant

We believe that the bug you reported is fixed in the latest version of
onedrive, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1101407@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Badia <sbadia@debian.org> (supplier of updated onedrive package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 08 Sep 2025 23:39:42 +0200
Source: onedrive
Architecture: source
Version: 2.5.6-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Badia <sbadia@debian.org>
Changed-By: Sebastien Badia <sbadia@debian.org>
Closes: 1101407
Changes:
 onedrive (2.5.6-1) unstable; urgency=medium
 .
   * New upstream version 2.5.6
   * d/patches:
       + Refresh Debian patchs
       + Disable new version notifications (Closes: #1101407)
   * d/control: Added new BD on libdbus-1-dev
   * d/copyright: Remove gentoo related files
Checksums-Sha1:
 d6cca78335f9feade018dec5d65cc38333685543 1997 onedrive_2.5.6-1.dsc
 65df4daf56f09c4cdd8b64913f8940e35119ab62 4284403 onedrive_2.5.6.orig.tar.gz
 455c4375f49154e7cf42e9d85021f3aea3423495 7396 onedrive_2.5.6-1.debian.tar.xz
 89ef39d2caaea9e9c3368b08dd57e914630b872e 9951 onedrive_2.5.6-1_source.buildinfo
Checksums-Sha256:
 0e590173b1f133a90b729934cb74d7293079447bcb03153e0e008bfc2dd7b942 1997 onedrive_2.5.6-1.dsc
 dda49ae9d0c042205ae8f375704c154fc7a9fc88aa21e307e7d83aa1954ad57e 4284403 onedrive_2.5.6.orig.tar.gz
 bd48c2c75ff2b2b71ecb431456cea90b0707326cd16b567ea02fcbc956f52b88 7396 onedrive_2.5.6-1.debian.tar.xz
 bc93e61653765cf3d487828bff59e7377312852af31463b44bd53b0940695653 9951 onedrive_2.5.6-1_source.buildinfo
Files:
 64ff229e89a7640fd2b28496d0fa45c9 1997 net optional onedrive_2.5.6-1.dsc
 daf612d487299c84242090bfbf789184 4284403 net optional onedrive_2.5.6.orig.tar.gz
 d69f29434f8a126c74b8bc46bddbce5f 7396 net optional onedrive_2.5.6-1.debian.tar.xz
 7bbf60bba548f0038cc891136324ed5d 9951 net optional onedrive_2.5.6-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAmi/U+gACgkQhxbORhSk
UtiyPw/9FtCh1l0nTpHQci4nOxw2mhUa8bkYO5UmRmp5HFHa7cR8eDtDSbJP1OWM
LUiTerqYxfG8cgemsrbqbGhwuDAIBmyzDs7EPXgKa+OBIruK+AeAHnAq4kPVlxv5
Pfml7CNzNdHG6VCHO3u50ELwzwh8DTaN3Q/emPk0VL1VVJNtr5Mm3r0zvbVRn/6C
hQnzhlIZ4oHU+0Hu5MsZgBmYF3W8KIRZuBZSXGAuhIu3IT6ZBRwb0Arx82N12823
6meWkT5S1xP0p889ls3pYif8OPBVMzj42S+HI8Dw5USyzFVN0j5YFNsg+Ds7o2Vg
uTYJwuSngZvQaDBdQI5GXWhaSjGynoBrC9uXxdwxnhbNWKxUhDnmK/aFrE9RlD+7
TkxTzI0K48btumzuG5owLXdIh+HrOKO258TuZZE5wqkna+WmYytIAiQOEfPY+N41
keNlG4PjZK38Cg3+ZZWPwhEmiz42jmeLbgrOjvRA11+CwABEY7BE2Q317Mx+39hM
FsQkBkxaCasFQn43ZNrYJxBTrp+Y7FsAxiFxwLUVDJUPuhhrGHM/RJoqRAMs0jny
UpcAlMVDqhUBEZwiQbvPM4UXGW5m1f5Fprd4lraT2OG+YhMknW7/nkski9IAWE5h
BgKXwKvkKyYzFtpPanRSzOjKLA3tsw78AnLvsGlnlSAGTcNsOWE=
=Y+H9
-----END PGP SIGNATURE-----

Hi,

are there any plans to fix this in trixie via stable-updates?

Greets,
Lee

close 1101407 2.5.6-1
thanks

(Re-marking the bug as fixed for 2.5.5-1 and above, I do acknowledge
it's not fixed in stable, but it is fixed in testing and the BTS should
reflect that)

I don't know if Sebastien has a plan for stable, but fixing this there seems
sensible.

One issue is there are other bugs which might make authentication difficult
(due to API changes), fixed in testing, but with a hefty number of other
(non-breaking AFAICT) changesand I wonder if we shouldn't just remove
this from
stable and only provide a backport, or ask the Release Team for an
exception to
allow version bump in stable via a pu bug.

Sebastien, what do you think? Do you want me to help on this?

Cheers,