From: Christiaan H. <cmh...@gm...> - 2019-10-15 08:52:25
|
There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-10-18 05:00:40
|
> On Oct 15, 2019, at 01:52 , Christiaan Hofman <cmh...@gm...> wrote: > > There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? Subversion merge conflict in the .pbxproj file. Hopefully it will work tonight. -- adam |
From: Adam R. M. <ama...@ma...> - 2019-10-21 00:56:42
|
> On Oct 17, 2019, at 21:44 , Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: > >> On Oct 15, 2019, at 01:52 , Christiaan Hofman <cmh...@gm...> wrote: >> >> There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? > > Subversion merge conflict in the .pbxproj file. Hopefully it will work tonight. Apparently this still wasn't working because commits failed. It looks like renaming directories (English.lproj) broke the working copy of the svn repo, so I had to blow away the entire directory and do a fresh checkout. -- adam |
From: Christiaan H. <cmh...@gm...> - 2019-10-21 08:47:59
|
> On 21 Oct 2019, at 02:56, Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: > > >> On Oct 17, 2019, at 21:44 , Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: >> >>> On Oct 15, 2019, at 01:52 , Christiaan Hofman <cmh...@gm...> wrote: >>> >>> There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? >> >> Subversion merge conflict in the .pbxproj file. Hopefully it will work tonight. > > Apparently this still wasn't working because commits failed. It looks like renaming directories (English.lproj) broke the working copy of the svn repo, so I had to blow away the entire directory and do a fresh checkout. > > — adam > Probably SF.net’s shitty SVN services. I had a similar problem once. Apparently they choke when there are a lot of changes in a single update, which leaves the working copy in an inconsistent state. They say to just not do that, which is just ludicrous, because sometimes it just happens. I was afraid this would cause problems. Unfortunately it was necessary, because Apple has deprecated legacy localization names, and it starts to become real in Catalina. Apparently Launch Services does not support them anymore. Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-10-21 14:03:23
|
> On Oct 21, 2019, at 01:47 , Christiaan Hofman <cmh...@gm...> wrote: > > I was afraid this would cause problems. Unfortunately it was necessary, because Apple has deprecated legacy localization names, and it starts to become real in Catalina. Apparently Launch Services does not support them anymore. Oh, that's neat, considering we used the full names because the short ones didn't work. Apple has lost its mind, and I'm likely staying with High Sierra until this computer dies. |