Bug 1241821 - Please update to >= 1.300011 to let bugzilla 5.0 run.
Summary: Please update to >= 1.300011 to let bugzilla 5.0 run.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Email-Sender
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Emmanuel Seyman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-10 07:44 UTC by Frank Büttner
Modified: 2016-08-03 10:34 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-03 10:34:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Büttner 2015-07-10 07:44:39 UTC
Description of problem:
The new bugzilla generation 5 need version 1.300011 of it, but only 2.199 is available.  

Version-Release number of selected component (if applicable):
perl-Email-Send-2.199-2.el7.noarch

See https://www.bugzilla.org/releases/5.0/release-notes.html#v50_feat for more.

Comment 1 Tom "spot" Callaway 2015-07-10 15:07:45 UTC
Not quite. Looks like they switched to perl-Email-Sender (which is not branched for EPEL7 at all). Switching to the proper component and owner.

Comment 2 Frank Büttner 2015-07-10 15:54:35 UTC
Oh are this two different perl parts?
My understanding was that was only another name for the same component.

Comment 3 Emmanuel Seyman 2015-07-14 10:33:05 UTC
(In reply to Frank Büttner from comment #2)
>
> Oh are this two different perl parts?
> My understanding was that was only another name for the same component.

Email-Sender is a rewrite of Email-Send and they are developed by the same person so I can understand the confusion.

I've requested a EPEL-7 branch over in bug #555983. I'll keep this bug updated with my actions.

Comment 4 Jan Kurik 2015-07-15 13:19:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 5 Emmanuel Seyman 2015-08-16 14:52:40 UTC
(In reply to Emmanuel Seyman from comment #3)
>
> I'll keep this bug updated with my actions.

JFTR, perl-Email-Send requires perl-Moo and a number of other things. These were unmaintained when RHEL-7 was released. I suspect using the versions in Rawhide is going to fail horribly so this is going to be more complicated than I thought.

Comment 6 Emmanuel Seyman 2016-07-18 12:02:24 UTC
Okay, that was too much effort...

It turns out Bugzilla 5.0 requires perl-DateTime-TimeZone 1.64 but we only have 1.63 in RHEL/Centos (and, because this is in RHEL/Centos, we can't upgrade this).

I've created a copr that contains a bugzilla-5.0.3 rpm and everything that it requires to function (that includes perl-Email-Sender 1.300016).
https://copr.fedorainfracloud.org/coprs/eseyman/bugzilla-5.0/

Please give it a whirl and report back, whether it works for you or not.

Comment 7 Emmanuel Seyman 2016-07-26 22:34:43 UTC
Folks, given that this is fixed by activating a copr repo, I'm strongly inclined to close this bug as WORKSFORME. Comment if you disagree.

Comment 8 Frank Büttner 2016-07-27 14:27:21 UTC
I hope I can try it next weekend.

Comment 9 Frank Büttner 2016-07-31 07:46:32 UTC
In the config file of it I found this line:
Alias /var/lib/bugzilla/data/webdot /var/lib/bugzilla/data/webdot
It looks very peculiarly.

And what is with this dirs:
lib/
data/
template/en/custom

they shut also out under /var because it contains user data, templates and user modules.

Comment 10 Emmanuel Seyman 2016-08-01 16:29:07 UTC
(In reply to Frank Büttner from comment #9)
>
> In the config file of it I found this line:
> Alias /var/lib/bugzilla/data/webdot /var/lib/bugzilla/data/webdot
> It looks very peculiarly.

No, this is normal (admittingly, it's a petty ugly hack).

> And what is with this dirs:
> lib/

This contains third-party libraries shipped by bugzilla.
We remove everything in it per Fedora packaging policy.
This directory is part of bugzila and should in /usr/share/bugzilla/ .

> data/

There is no data/ in the rpm.

> template/en/custom

This directory is part of bugzila and should in /usr/share/bugzilla/ .

Comment 11 Emmanuel Seyman 2016-08-01 16:30:56 UTC
Frank, does the supplied package work for you? Are you able to install bugzilla, configure it and use it for actually tracking bugs?

Comment 12 Frank Büttner 2016-08-03 09:24:03 UTC
Install will work, but configure fails because of the missing data directory.
The manual of bugzilla https://bugzilla.readthedocs.io/en/5.0/installing/upgrading.html say:
That I must copy the data directory because it contains all bug attachments.
But what will be the target directory for it, when the rpm package don't contains it?

Comment 13 Emmanuel Seyman 2016-08-03 10:34:06 UTC
(In reply to Frank Büttner from comment #12)
>
> Install will work

That's great to know. Thank you for testing.

> but configure fails because of the missing data directory.
> The manual of bugzilla
> https://bugzilla.readthedocs.io/en/5.0/installing/upgrading.html say:
> That I must copy the data directory because it contains all bug attachments.
> But what will be the target directory for it, when the rpm package don't
> contains it?

The data/ directory is created by checksetup.pl in its second step (i.e. once you've got all related modules installed) and configured localconfig correctly. By default, the rpm package will create it in /var/lib/bugzilla while installing bugzilla by source will create a data/ directory in the source tree.

Given that the perl-Email-Sender package in the copr repo appears to work and allow you yo use Bugzilla 5.0.x, I'm going to close this bugs. Please don't hesitate to email me if you require help using the repo.


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