Mailinglist Archive: opensuse-buildservice (207 mails)

< Previous Next >
Re: [opensuse-buildservice] Experimenting with the cpanspec service
On Fri, Mar 11, 2011 at 3:23 AM, Stephan Kulow <coolo@xxxxxxx> wrote:
Am Donnerstag, 10. März 2011 schrieb Greg Freemyer:
On Thu, Mar 10, 2011 at 5:16 AM, Stephan Kulow <coolo@xxxxxxx> wrote:
Am Donnerstag, 10. März 2011 schrieb Greg Freemyer:

Does the cpanspec service in OBS work?

== details

I thought I'd try out the cpanspec service.

Looking at the parameters it needs, it seems easy enough:
20fd 57a2697dbcfa28a5bc

But when I try it I get:

Source processing is currently broken:

        service cpanspec failed:
defined(%hash) is deprecated at
/usr/lib/perl5/vendor_perl/5.12.1/Pod/POM/ line 82.
      (Maybe you should just omit the defined()?)
Failed to get
500 Can't connect to (Bad hostname '')

Those look like pretty fundamental issues unrelated to my package.

And what is your package? The error doesn't sound as if you called it on
a tar.

Greetings, Stephan

home:gregfreemyer:Tools-for-forensic-boot-cd > perl-Net-Pcap

I just have two services setup.  On the web gui, I have file download
listed first and cpanspec listed second, so I assume the download step
is done, then the cpanspec service run against that file.

The file download service has these params:

host  --
path  --     /CPAN/authors/id/S/SA/SAPER/Net-Pcap-0.16.tar.gz

That worked fine when I had my own normal specfile.

The second service is the cpanspec service:

The only parameter I set was:

source --     *.tar.gz

The "documentation" link from my first email says:

  <parameter name="source">
    <description>Name of source. RegExp are allowed. Defaults to

So I assume a wildcard syntax is acceptable.

I think this relates to the empty paramters given additionally, but I can't
verify - my package is "blocked":

It works fine locally though.

Greetings, Stephan

It's broken for you as well on OBS:

If you know of a reference project that's using it on OBS, I'd be curious.

fyi: Obviously I can create the specfile locally with cpanspec and
then upload it. It just seemed a little cleaner to have the specfile
created on the fly. And I have 5 or 10 perl modules in my project I
need to SR to d:l:p for the first time. So I thought I'd take a
little effort and figure out the "cleanest" way to do it so that a
reviewer wouldn't have to worry that I had messed with the default

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >