Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30684 - [cream] Files missing from package

Attached to Project: Community Packages
Opened by Zachery Campbell (Aegidius_De_Hammo) - Sunday, 15 July 2012, 08:58 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 18 August 2013, 10:04 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: Installing the package in community and running "$ cream" yields the error message "E282: Cannot read from "$VIMRUNTIME/cream/creamrc"" and starts up the defalt gvim interface. "$ ls /usr/share/vim/vim73" reveals that the entire /usr/share/vim/vim73/cream directory is missing. I confirmed that the directory is absent from the package itself as well. Downloading and running the PKGBUILD provided at https://projects.archlinux.org/svntogit/community.git/tree/trunk?h=packages/cream yields a package containing the missing files which works normally when installed.


Additional info:
* package version(s) 0.43-2
* config and/or log files etc. None that I know to be relevant.


Steps to reproduce:
1. Install cream package from community
2. Attempt to run cream

or

1. Search the existing package for the cream directory and its configuration files.



I'm completely new to bug reporting, so please let me know if I've done anything incorrectly here. Thanks!
This task depends upon

Closed by  Jelle van der Waa (jelly)
Sunday, 18 August 2013, 10:04 GMT
Reason for closing:  Won't fix
Additional comments about closing:  I can't fix the install. so dropping the package
Comment by Alexander F. Rødseth (xyproto) - Sunday, 15 July 2012, 13:06 GMT
Hi,

Thanks for reporting and welcome to our bug tracker. Please note that "Critical" priority is saved for "System crash, severe boot failure that is likely to affect more than just you, or an exploitable security issue in either a core or outward-facing service package.". See also: https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines#Severity

Other than that, it looks like everything is in place, which is good.

Assigned the ticket.
Comment by Zachery Campbell (Aegidius_De_Hammo) - Sunday, 15 July 2012, 16:11 GMT
Aha, I was actually wondering whether critical meant "critical to the package" or "critical to the distribution". I took a guess and missed. I'm not sure how I managed to miss that part of the wiki page; I <i>did</i> look it over. Thanks for the info!
Comment by Alexander F. Rødseth (xyproto) - Monday, 16 July 2012, 09:01 GMT
No wonder, it's a dense wall of text to absorb at first go. :)
Comment by Alexander F. Rødseth (xyproto) - Monday, 03 September 2012, 23:16 GMT
Confirmed, got 'E282: Cannot read from "$VIMRUNTIME/cream/creamrc"' and a GUI that looks like default vim.

Loading...