X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:subject:from:to:date:content-type :mime-version:content-transfer-encoding; q=dns; s=default; b=fIb 6vaS3ofy9Q4sPROIzIXzv2vaXUZJHZGSTfDNb4ntXtuHpieIdwOHmQrhbgOyZML+ wj8ym9xs86LUZF26FQfXQHcjqBB6xLOUAmiBu+NNVtLVQtYk9kkqfnRdhhyyVA3Z kPh5lNdVXhWG0eus+Q3kSRI6Q+FA45vUdv87zV90= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:subject:from:to:date:content-type :mime-version:content-transfer-encoding; s=default; bh=1H2DvVwkT z0bd8elpJNjV8n/7JI=; b=s63XfFjhpabEhFtNaXKCU2lWz/meU9XvjprXCibhA EhDN3m8NOjQgpntxXQ2ruhHNI+WkOsgIyEN2UMBTGT3SDDEIIj4kimwYjx+XjUht ktxO9DymomvmBzZlgjfxcT1sc4KpLUTKbUCzF580c9E4ktaRXJLdg2vD+uTciqfT hk= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.1 required=5.0 tests=AWL,BAYES_20,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: smtp.n-able.com Message-ID: <1407441665.23904.5.camel@oscar.engineering.n-able.com> Subject: rpm-build issue From: Matt Rose To: Date: Thu, 7 Aug 2014 16:01:05 -0400 Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes I've noticed that the newer version of the rpm-build package (4.11-1) has a really severe bug in that it ignores the %defattr flag in the % files section of .spec files, so that when you try to build a file with a files section like %files %defattr(-,root,root) /tmp/foo You get the error "No file attributes found" The 4.1-2 version does not have this bug. this looks very similar to debian bug 630163 I could generate the cygcheck output and attach it, but to do that, I'd have to break the server, then fix it again, and I'd rather get the process started. It's not really a bug in cygwin itself, just one of the packages. Matt -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple