Ticket #221 (closed defect: wontfix)

Opened 11 years ago

Last modified 7 years ago

CRAN Repository sync breaks Paludis with non-standard package name

Reported by: fpetran Owned by: kugelfang
Priority: Sometime Milestone:
Component: repositories/cran Version: 0.24.1
Keywords: Cc:
Blocked By: Blocking:
Distribution: Gentoo

Description (last modified by ciaranm) (diff)

The CRAN package list contains a package name that breaks paludis. It's probably not so much a paludis bug, but since I figured it would be futile to try and talk CRAN Authors into consistent package naming, I posted it here.

Reproducible: always

Steps to reproduce:

  1. Create CRAN repository.
  1. sync.
  1. execute paludis with -i, -pi or -q options.


Building target list...
Unhandled exception:
  * In program paludis -pi aterm:
  * When performing install action from command line:
  * When adding install target 'aterm':
  * When disambiguating package name 'aterm':
  * When looking in repository 'cran-CRAN':
  * When finding category names containing package 'aterm':
  * When checking for package 'cran/aterm' in cran-CRAN:
  * When loading category names for cran-CRAN:
  * When parsing line 'Package: RGtk2.10':
  * Name 'RGtk2-10' is not a valid package name part (paludis::PackageNamePartError)


  1. Open file ${location}/PACKAGES in the CRAN repository.
  1. Change the line
Package: RGtk2.10


Package: RGtk210
  1. Everything works fine.

Change History

comment:1 Changed 11 years ago by fpetran

Sorry, I messed up there - it's actually not paludis 24.1 but 24.2.

comment:2 Changed 11 years ago by ciaranm

I'm wondering whether we'll have to make package name validators per-repository...

comment:3 Changed 7 years ago by ciaranm

  • Status changed from new to closed
  • Distribution set to Gentoo
  • Resolution set to wontfix
  • Description modified (diff)
Note: See TracTickets for help on using tickets.