From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) by sourceware.org (Postfix) with ESMTPS id 155D5388F40E for ; Tue, 5 May 2020 16:26:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 155D5388F40E Received: by mail-wr1-x434.google.com with SMTP id s8so3458537wrt.9 for ; Tue, 05 May 2020 09:26:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=stDtBofvMduVNTNOQSkRpHaZO3RO8FJFukUI9qaNyFo=; b=Trm28O/2+S9/D6Rjg5eCPSq2HyxuJVJfrj/Pk145wx92yvY5+Iq04G9MYe9cpVx7Ds nxJnrOR7wmuY7UpkiluapLhnQDtJN1TogzczNyzPxToR5YRUqKR4XdORnPOUuDiT0JPa 8YH71kowQeOmZx4zLNZlV9VFixQxzko3S24wyC28CQzzyrqJRTRxn2V2nPC0mwrVfSFF bz2/pMSt8yQkUgL0mCIu0xMHnyiibRIBDcN0EXoIE6XTEitFlGAfz8s9L8hZb+hPatoh 0ubr07c2YLzpwlWeRX3ZpKhl9JbEgZglzS8njUchMme0p2a9eJUX+1O/OvAfNV2IKFcr S2lw== X-Gm-Message-State: AGi0PubnX3axt2i10hjulZFlL/egpOLSeET3zj6sthG7PciyIc9RFISM L1KlKeRiOLft5hGZmumiphcu7JAi X-Google-Smtp-Source: APiQypL4RvyBpvL3KpdJ4MJQL2WSdhrbXpbS1hpl1VQvzHWnFYbw0iE5vUcDwe7JO96G4+BfIsl9eA== X-Received: by 2002:adf:fccc:: with SMTP id f12mr4436535wrs.267.1588695963818; Tue, 05 May 2020 09:26:03 -0700 (PDT) Received: from ?IPv6:2003:cc:9f0f:2ccb:11f2:7f40:be38:8d7c? (p200300CC9F0F2CCB11F27F40BE388D7C.dip0.t-ipconnect.de. [2003:cc:9f0f:2ccb:11f2:7f40:be38:8d7c]) by smtp.gmail.com with ESMTPSA id y9sm4376291wmm.26.2020.05.05.09.26.02 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 May 2020 09:26:03 -0700 (PDT) Subject: Re: R does not handle package non-ASCII DESCRIPTION files properly To: cygwin@cygwin.com References: <9164cff70d13d9f7ca451f42fc868a14@mhoenicka.de> <129c4e64-4051-0cc2-0706-c39eaacbdc9e@gmail.com> From: Marco Atzeri Message-ID: Date: Tue, 5 May 2020 18:25:59 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2020 16:26:15 -0000 Am 05.05.2020 um 16:55 schrieb Brian Inglis: > On 2020-05-05 02:47, Markus Hoenicka wrote: >> Am 2020-04-30 22:17, schrieb Marco Atzeri via Cygwin: >>> Am 30.04.2020 um 17:28 schrieb Markus Hoenicka: >>>> I've contacted the processx package maintainer on a problem reported here >>>> previously (see https://cygwin.com/pipermail/cygwin/2020-April/244667.html). >>>> He suggested to try the github version but that triggered a different type of >>>> error which does not seem to be package-specific. >>>> >>>> 1st try: build from a local copy of the github package sources with default >>>> locale settings on a German Windows 10 system >>>> >>>>> install.packages("/cygdrive/c/Temp/processx-master",repos=NULL,type="source") > >>>> Installing package into ‘/usr/lib/R/site-library’ >>>> (as ‘lib’ is unspecified) >>>> * installing *source* package ‘processx’ ... >>>> ** using staged installation >>>> Error : Invalid DESCRIPTION file >>>> >>>> Authors@R field gives no person with maintainer role, valid email >>>> address and non-empty name. >>>> >>>> See section 'The DESCRIPTION file' in the 'Writing R Extensions' >>>> manual. >>>> >>>> ERROR: installing package DESCRIPTION failed for package ‘processx’ >>>> * removing ‘/usr/lib/R/site-library/processx’ >>>> Warning message: >>>> In install.packages("/cygdrive/c/Temp/processx-master", repos = NULL,  : >>>>    installation of package ‘/cygdrive/c/Temp/processx-master’ had non-zero >>>> exit status > >>> Noted. I will look on both the two issues but it could take a bit. >>> I never looked at the build process of R packages in such details > >> kind of "while you're at it": I've noticed one additional problem with non-ASCII >> characters. This may or may not be related to the problem reported above. >> Several packages throw an error during installation, in my case questionr, >> readr, pls, and vegan. The output of the latter is shown here: >> >> installing to /usr/lib/R/site-library/00LOCK-vegan/00new/vegan/libs >> ** R >> ** data >> ** inst >> ** byte-compile and prepare package for lazy loading >> ** help >> *** installing help indices >> Error in Rd_info(db[[i]]) : >>   missing/empty \title field in >> '/tmp/RtmprL23H1/R.INSTALLffe51949f2e2/vegan/man/sipoo.Rd' >> Rd files must have a non-empty \title. >> See chapter 'Writing R documentation' in manual 'Writing R Extensions'. >> * removing ‘/usr/lib/R/site-library/vegan’ >> >> The file in question (man/sipoo.Rd) starts like this: >> >> \encoding{UTF-8} >> \name{sipoo} >> \alias{sipoo} >> \alias{sipoo.map} >> \docType{data} >> \title{ Birds in the Archipelago of Sipoo (Sibbo and Borgå)} >> >> Please note that the encoding is set to UTF-8 explicitely. Nonetheless, the a >> with overring in "Borgå" seems to mess up the title, which makes R think the >> \title field is missing. Changing the å to a circumvents this problem. I've also >> noticed that non-ASCII characters outside the title field do not hurt at all. > > Add "Encoding: UTF-8" to the package DESCRIPTION file and remove from .Rd files, > as documented near the bottom of the section: > > https://cran.r-project.org/doc/manuals/R-exts.html#The-DESCRIPTION-file > > referenced by: > > https://stackoverflow.com/questions/18080303/rd-files-with-different-encoding > the original issue was in a package that was following the rule, so there is something at fault in the Cygwin R package reading UTF-8 files. May be is the same root cause that is causing a single fault in reading/writing during build test. I am looking on the 4.0.0 before releasing but I am not a R user so it takes time. Regards Marco