No, I just let it upgrade like any other of my packages, and the other packages upgraded within a reasonable timeframe (I haven't timed it, but let's just say ten minutes or so). My first attempt to upgrade ran for I think three hours (after typing `guix package -u` to upgrade all packages), but that's just what it felt like, I was not timing it. Borg was the first package to get upgraded, so I wasn't sure if it was a problem with Borg or a general upgrading problem. Then I upgraded all packages except Borg and finally tried upgrading only Borg alone. After that second attempt I sent the email.
On Thursday, 14 March 2019 21:39:06 CET you wrote: > HiPhish, > [...] > > Interrupting after an hour is a bit too soon to say it's stuck. > Just from experience, many backup programmes tend to have long > test suites (a trait which they share with many databases and > compressors, probably because they're a bit of both). The build > was chugging along. What did the log say was happening? > > What is strange here is that you didn't get a substitute for Borg. > I did[0]. Are you deliberately building Borg locally? > > Kind regards, > > T G-R > > [0]: For > > /gnu/store/qplgyx9h65k509l02bfc4cz9dlid00ck-borg-1.1.9.drv > → /gnu/store/5fazf5kwalvv3r4bin74fzgxp8hmfdha-borg-1.1.9 > > which is a graft of > > /gnu/store/pgib6ji5792y739jwv90zk679jqxji1q-borg-1.1.9
