Package Details: onedrive 1.1.4-1

Git Clone URL: (read-only, click to copy)
Package Base: onedrive
Description: Free OneDrive client written in D
Upstream URL:
Licenses: GPL3
Submitter: Scimmia
Maintainer: Scimmia
Last Packager: Scimmia
Votes: 16
Popularity: 0.009777
First Submitted: 2018-02-20 15:50 (UTC)
Last Updated: 2022-03-13 14:36 (UTC)

Latest Comments

abraunegg commented on 2022-03-13 23:28 (UTC) (edited on 2022-03-13 23:29 (UTC) by abraunegg)

'skilion's full statement -

Hi, great job by augmenting my client with all these features and congrats for making it into most Linux distributions. That's the beauty of open source, if one thinks he can do better, he can fork/clone the code and modify it as he likes. People will use the best one that fits their needs.

I consider this project an hobby. I made it to fulfill my use cases and nothing else. Therefore I don't want to spend time to implement and maintain features I don't use. Also I do not want to feel obliged to offer support when things stop working.

Keep up the good work :)

Scimmia commented on 2022-03-11 17:56 (UTC)

So you say it's abandoned yet has had commits. That's not abandoned.

"confirmed skilion has zero interest in maintaining it or fixing it." That is not at all what he said. "Therefore I don't want to spend time to implement and maintain features I don't use." That's completely different.

abraunegg commented on 2022-03-11 17:52 (UTC)

@Scimmia - the 'skilion' code was abandoned and despite minor commits since I originally forked the client and fixed the bugs it has since been confirmed skilion has zero interest in maintaining it or fixing it. Best of luck.

Scimmia commented on 2022-03-11 17:44 (UTC)

Slanderous? Are you or are you not claiming that this project is abandoned? You are ( and have been consistently for years, even after being told many times that it isn't. Is it abandoned? No, it's not ( Were you aware of this? Yes, see the link YOU previously posted.

Slander requires that the claim be false.

abraunegg commented on 2022-03-11 17:39 (UTC)

@Scimmia - It was forked to fix all the bugs and issues people had, provide a solution to their problems with zero response from 'skilion' to their problems.

No lies and deception here ... suggest you look at things a different way rather than the very childish attitude you have. Happy to have a difference of opinion here - however being slanderous in this way that you have is not very credible or professional of you.

Scimmia commented on 2022-03-11 17:15 (UTC)

Oh, and look, a fix for the issue reported here was committed a few months ago! Yep, totally outdated and unmaintained.

kokoko3k, I'll integrate the fix here tonight, or you can use onedrive-git.

Scimmia commented on 2022-03-11 17:02 (UTC)

Take offense all you want, none of that justifies you forking it and declaring yourself the new upstream just because the project wasn't what you wanted. Think back to the ffmpeg/libav split, did they just say "We're ffmpeg now!"? No, that't not how things work. You still claim it's dead since 2018 when the last release was less than a year and a half ago. All lies and deception.

abraunegg commented on 2022-03-11 16:59 (UTC)

@Scimmia - I take total offence to your statement that I am promoting a lie. 'skilion' has confirmed the following: I don't want to spend time to implement and maintain features I don't use. Also I do not want to feel obliged to offer support when things stop working


Perhaps a little more pragmatism from yourself even after 4 years .........

Scimmia commented on 2022-03-11 16:37 (UTC)

npreining, that a lie told by abraunegg to justify them taking over the project without the consent of the developer.

kokoko3k, I'll take a look at it in the next couple of days.

npreining commented on 2022-03-10 22:33 (UTC)

This program is outdated and unmaintained, please use the package onedrive-abraunegg which is fully supported and maintained.

kokoko3k commented on 2022-03-09 11:12 (UTC)

It fails to build: src/qxor.d(67): Error: need this for lengthInBytes of type immutable(ulong)

badlydrawnface commented on 2020-05-26 16:22 (UTC)

I personally find this package easier to use than onedrive-abraunegg. On this version, all you have to do to authenticate and sync is to just type onedrive. while on onedrive-abraunegg, you have to type in onedrive --synchronize after authenticating.

abraunegg commented on 2020-05-08 07:58 (UTC)

@ogarcia 100% agree with you re fixing this package .. but some folk are rather steadfast on this for absolutely zero logical reason .. it is what it is - I am sorry for your inconvenience (and to all other Arch AUR users who fall into the same trap) of installing a buggy, unsupported, unmaintained package.

@eschwartz Your email comment to @ogarcia really shows just how out-of-touch with reality you are.

ogarcia commented on 2020-05-08 07:37 (UTC)

Hello, a few days ago I started to use OneDrive for work reasons and after see that this package source is abandoned, I realized that the work continues live in a fork by abraunegg. As I can see more distributions like Debian or Slackware adopt this fork as onedrive package. At this moment I do a request for rename or merge this package with onedrive-abraunegg:

A few days later I receive this response, a simply "not how forks work":

I try to contact with Eli and Doug to obtain more detailed explanation about why of this reply, but no response.

I don't know if there is personal quarrels or something else, I only look for the best to users and Arch community. I simply think that maintain an outdated package having better options is a mistake.

Varakh commented on 2019-04-06 13:20 (UTC)

I requested a merge but unfortunately it got rejected. I think that the decision is discussable but still, I don't have the final word here and I don't have energy left to dig deeper into this one.

Also, it seems to be "completely normal". :-)

See mail history here:

abraunegg commented on 2019-04-03 18:50 (UTC)

@Varakh, @Pete Debian, Ubuntu & Fedora are all using my fork / packaging v2.3.2 as well - so there really is no logical reason not to repoint it and the updated branch as the 'onedrive' package.

The last 'skilion' release was on 10 Sep 2018, prior was on 21 Jan 2018. The last time 'skilion' actually responded to an issue was 10 Sep 2018 by closing off some open issue tickets which was fixed by the v1.1.3 release.

There has hardly ever been any interaction with anyone over issues raised nor discussion around PR's that have been submitted.

@blue995 Your 100% CPU issue is resolved - refer to for details or more specifically

@Scimmia Last time this was raised you basically have said 'things don't work that way' - I think you have enough evidence from the wider community that the 'skilion' branch is dead (and has been despite the very minor releases in 2018) for close to 2 years now given I have been patching, maintaining my fork & actively supporting users for approximately that length of time.

Pete commented on 2019-04-03 08:46 (UTC)

I agree with Varakh, that it would be ideal if this package would follow the abraunegg branch. I'm now maintaining the onedrive-abraunegg package, and you are free to use that PKGBUILD here if you like. In that case, I would remove that package.

Also, I'm willing to be co-maintainer/take over the maintenance of this package if you like.

Varakh commented on 2019-04-03 08:42 (UTC) (edited on 2019-04-03 08:43 (UTC) by Varakh)

I'd vote for changing this package(name) to the fork abraunegg did as it is actively maintained, contains fewer bugs and can be used in daily production.

@Scimmia I'd like to ask you to drop maintainer ship or have a common understanding with Depau about it.

I think every AUR user searching for this functionality will have benefits. Otherwise we, as an Arch Community, propose that new users should use the old service with tons of bugs and this just by the naming of the package.

Depau commented on 2018-07-31 00:10 (UTC) (edited on 2018-07-31 00:21 (UTC) by Depau)

abraunegg's code is indeed more up to date; it's currently 116 commits ahead of upstream and has most of the issues piled up in upstream's repo fixed.

I vote for his fork.

By the way, I forked this package and made one with his fork: link.

@abraunegg if you want to maintain it I can transfer it to you.

abraunegg commented on 2018-07-07 00:07 (UTC) (edited on 2018-07-07 01:48 (UTC) by abraunegg)

"You declare that it's abandoned and you're the new upstream because he doesn't respond quick enough. Things don't work that way."

I would say > 12 months non response to issues logged by other users despite some small commits (in Feb 2018) that did not fix user defects would almost constitute a 'im not interested anymore'. A response to posts and questions raised by myself and others asking 'have you abandoned this' have gone unanswered despite efforts.

I have no issue you in providing broken software that contains significant defects to the Arch Linux community (defects that have been fixed) - you are only doing yourself a disservice with your poor attitude below.

Scimmia commented on 2018-07-06 23:46 (UTC)

You declare that it's abandoned and you're the new upstream because he doesn't respond quick enough. Things don't work that way.

abraunegg commented on 2018-07-06 23:10 (UTC)

The attached source code is not the latest and contains a significant number of defects most notably unable to handle the OneDrive API change that generates the error 'Key not found: lastModifiedDateTime' for OneDrive Business Accounts. The 'skilion' code appears to have been abandoned by the original author and contains issues that have not been fixed.

If you wish to use the latest code which contains numerous fixes and enhancements you need clone from here:

blue995 commented on 2018-03-18 19:34 (UTC)

The monitoring feature of this onedrive client consumes a lot of battery life. I enabled and started the onedrive.service and my cpu usage was often at 100 % just because of the onedrive monitoring service. There was nothing that the client had to pull or push and this behaviour didn't change. I deactivated the service now until this behaviour gets fixed. Besides its enormous power consumption the feature works great though. Thanks for that. :)