Bug 765764

Summary:	RFE: Exclude trash from created repo
Product:	[Fedora] Fedora	Reporter:	Frank Murphy <frankly3d>
Component:	createrepo	Assignee:	Luke Macken <lmacken>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	james.antill, lmacken, pfrields
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-09 17:39:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Frank Murphy 2011-12-09 11:06:52 UTC

Description of problem: .Trash* sub-dir(s) are included in created repos.


Version-Release number of selected component (if applicable):
F15/16

How reproducible: Always


Steps to Reproduce:
1. Get some user to delete an rpm from local repo,
which is on a NAS  (Proprietary\Linux)
2. update PK\yum
3.
  
Actual results: deleted rpms will be included in "yum update\PackageKit"


Expected results: No .Trash*


Additional info:  
Have no access to a conf file, that --excludes=~/.Trash*
could be used with.  
Used in conjunction here, with yum local\updateonboot.
The nas support, only support MS questions.

Comment 1 seth vidal 2011-12-09 17:39:38 UTC

So - the problem here is - that .Trash folders are not anything that would be expected in a path. Afaik they are not a 'standard' for linux systems. More importantly it seems like simply adding the excludes on the command line handles this problem without any large amount of work and we don't have to add an option to disable the .Trash exclusion, either.

Comment 2 Frank Murphy 2011-12-09 18:10:06 UTC

(In reply to comment #1)
> So - the problem here is - that .Trash folders are not anything that would be
> expected in a path. Afaik they are not a 'standard' for linux systems. 

True, but they can be there in a mixed environment.

> importantly it seems like simply adding the excludes on the command line
> handles this problem without any large amount of work and we don't have to add
> an option to disable the .Trash exclusion, either.

No command line. so what part of an automated process can I fit ~/excludes.
And am not also allowed run any scripts on the nas either.

F* buttons also disabled.
Any advice, aside from going back to full MS Windows welcome.