On 22-04-2016 14:21, Jo�o Valverde wrote:
On 22-04-2016 14:18, Jo�o Valverde wrote:
On 22-04-2016 12:41, Jo�o Valverde wrote:
On 22-04-2016 12:31, Anders Broman wrote:
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jo�o
Valverde
Sent: den 22 april 2016 11:05
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] rpm-build on SuSE 11.3 fails with "new
version string"
The problem is also present with old version string for automated
builds.
How should this string be sanitized for RPM? Is there some best
practice?
Well a day or two ago I got further, then it failed with dependency
problems on autoconf and rpmbuild even though I've installed a newer
autoconf from source.
For builds from master that bug was indeed introduced with
7c6e859ccf210a45e1cc0f6da17692845e6b5a23.
But tarballs from https://www.wireshark.org/download/automated/src/ were
affected before that too.
Seems easy enough to fix, I'll test and push to Gerrit.
Not nearly as simple as I thought to sanitize the rpm spec file version
to remove the dash. The build still depends on make dist which depends
on the autoconf version which has the dash so that generates lots of
cascading failures.
I don't have any experience with this but I would hope it is a solved
problem...
... the solution possibly being "don't use dashes in the autotools
package version if you want to build with rpm".
Fix at https://code.wireshark.org/review/#/c/15062/
