Bug 1230800 - Upgrade perl-Server-Starter to 0.30
Summary: Upgrade perl-Server-Starter to 0.30
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Server-Starter
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ralf Corsepius
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-11 14:38 UTC by Petr Pisar
Modified: 2015-06-12 06:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-12 06:45:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2015-06-11 14:38:58 UTC
Latest Fedora delivers perl-Server-Starter 0.28. Upstream released 0.30. Please upgrade.

Also please enable monitoring service to receive updates about new releases.

Comment 1 Ralf Corsepius 2015-06-11 15:27:20 UTC
(In reply to Petr Pisar from comment #0)
> Also please enable monitoring service to receive updates about new releases.

No, I will not do so. I am polling the perl-modules, I am maintaining, instead.

That said, I do not consider the current form of the monitoring service to be useful to me, and consider it as bureaucracy and a source of superflous email and bugzilla noise.

Comment 2 Petr Pisar 2015-06-12 05:39:38 UTC
Just for you information, pingou implemented a third state for the monitoring: It only files a bug report without any attempts for scratch build.

Comment 3 Ralf Corsepius 2015-06-12 06:45:00 UTC
(In reply to Petr Pisar from comment #2)
> Just for you information, pingou implemented a third state for the
> monitoring: It only files a bug report without any attempts for scratch
> build.

Thanks for the info, at least some noise less. ... these build attempts were failing in many cases ;-)

Anyway, I pushed perl-Starter-0.30 to rawhide. For now, I am hesitant on pushing it to Fedora < 23, because all changes since 0.28 seem feature updates to me.


Note You need to log in before you can comment on or make changes to this bug.