Hi Dag.
Ah, found the problem in the config file and excluded the line:
setOption(ReleaseExtension, None)
After that, the config file works again.
I have attached a new spec file and a new config.redhat (in the archive
file).
Regards,
Bjarne
Done. The package will become available in the
Hi,
On 01/05/2010 04:25 PM, arnebjarn...@hotmail.com wrote:
I have attached a new spec file and a new config.redhat (in the archive
file).
Unless the patch is exceptionally large ( eg: 40KiB ) why not send it
in a text attachment ? Significantly lowers the amount of effort
required to look
Hi Karanbir.
I am just used to zip/tar attachments, since I often see spam filters silent
drop attachments other than compressed archive files.
But I have no problems with sending diff patches uncomprssed if that is
preferred by the RPMforge maintainers :-)
Regards,
Bjarne
Unless the patch
On 01/05/2010 05:09 PM, arnebjarn...@hotmail.com wrote:
I am just used to zip/tar attachments, since I often see spam filters
silent drop attachments other than compressed archive files.
But I have no problems with sending diff patches uncomprssed if that is
preferred by the RPMforge maintainers
On Tue, 5 Jan 2010, arnebjarn...@hotmail.com wrote:
Unless the patch is exceptionally large ( eg: 40KiB ) why not send it in
a text attachment ? Significantly lowers the amount of effort required to
look see.
Just a question really.
I am just used to zip/tar attachments, since I often
