[Debian-med-packaging] Unexpanded @PKGNAME@ macros in path names of r-bioc-biobase and r-bioc-makecdfenv?

[Andreas Tille]

Hi Axel,

On Thu, Mar 23, 2017 at 11:27:06PM +0100, Axel Beckert wrote:
> after having stumbled upon #858567 and #857795 (files under
> /usr/@DATADIRNAME@/ — literally) I wondered if there are similar cases
> with different variable names in Debian. Using "apt-file search NAME@"
> I found two more similar cases, just deeper down the in the file
> hierachy and probably only causing broken packages,

Cool QA-task. :-)

> but no FHS violation:
> 
> r-bioc-biobase: /usr/lib/R/site-library/Biobase/Code/R/get at PKGNAME@.R
> r-bioc-biobase: /usr/lib/R/site-library/Biobase/Code/man/@PKGNAME at .Rd
> r-bioc-biobase: /usr/lib/R/site-library/Biobase/Code/man/get at PKGNAME@.Rd
> r-bioc-biobase: /usr/lib/R/site-library/Biobase/ExpressionSet/man/@PKGNAME at .Rd
> r-bioc-makecdfenv: /usr/lib/R/site-library/makecdfenv/Code/man/@DIMENVNAME at .Rd
> r-bioc-makecdfenv: /usr/lib/R/site-library/makecdfenv/Code/man/@PKGNAME at .Rd
> 
> Since I have no idea how R works, I'm not sure if these are bugs at
> all or if this is intended. But since I haven't found any other R
> package with such weird file names, I suspect that these are bugs.
> 
> Would be nice if someone could check if these packages really work (or
> if e.g. only documentation is broken).

I checked the single documents and it seems to be pure documentation
examples.  So I do not think that this is a bug.

Thanks for the hint anyway

       Andreas.

-- 
http://fam-tille.de