[Bug 1753543] New: perl-Font-AFM for EL8
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1753543
Bug ID: 1753543
Summary: perl-Font-AFM for EL8
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: perl-Font-AFM
Assignee: tcallawa(a)redhat.com
Reporter: xavier(a)bachelot.org
QA Contact: extras-qa(a)fedoraproject.org
CC: lxtnow(a)gmail.com, perl-devel(a)lists.fedoraproject.org,
rc040203(a)freenet.de, rob.myers(a)gtri.gatech.edu,
tcallawa(a)redhat.com, tremble(a)tremble.org.uk
Target Milestone: ---
Classification: Fedora
Hi,
Could you please branch and build perl-FontAFM for EPEL 8 ?
It is in the dependency chain of another package I'd like to maintain in EPEL
8.
Regards,
Xavier
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1749132] New: Too strict gir lib search pattern
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1749132
Bug ID: 1749132
Summary: Too strict gir lib search pattern
Product: Fedora
Version: 30
Status: NEW
Component: perl-Glib-Object-Introspection
Assignee: berrange(a)redhat.com
Reporter: iamdexpl(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: berrange(a)redhat.com, ddick(a)cpan.org,
perl-devel(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1611740
--> https://bugzilla.redhat.com/attachment.cgi?id=1611740&action=edit
A less-strict template
Description of problem: perli11ndoc script from perl-Glib-Object-Introspection
can either display a window with a drop-down list of available GIRs or, if
launched with a GIR name, find the corresponding file, parse it and dump to
stdout. The latter mode has, among other things, a check whether the given
argument can be a valid GIR name. However the pattern to check against is too
strict. For example, it filters out GdkX11, libxfce4panel, libxfce4ui,
libxfce4util and PangoFT2
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. install and of the following — pango-devel, xfce4-panel, libxfce4ui,
gtk3-devel, libxfce4util
2. run perli11ndoc without arguments; ensure that the GIR matching the
installed package is listed in a drop-down list
3. run perli11ndoc GdkX11 (or whatever name from that packages installed on
step 1)
Actual results: "Cannot recognize the library name" on stderr
Expected results: contents of that GIR on stdout
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1855962] New: bugzilla can't send non-html email
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1855962
Bug ID: 1855962
Summary: bugzilla can't send non-html email
Product: Fedora
Version: 32
Status: NEW
Component: bugzilla
Assignee: itamar(a)ispbrasil.com.br
Reporter: sjoerd(a)acm.org
QA Contact: extras-qa(a)fedoraproject.org
CC: emmanuel(a)seyman.fr, itamar(a)ispbrasil.com.br,
perl-devel(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1700684
--> https://bugzilla.redhat.com/attachment.cgi?id=1700684&action=edit
the patch
Description of problem:
Since the update to packages perl-Email-MIME-1.949-1.fc31.noarch and
perl-Email-MIME-ContentType-1.024-1.fc31.noarch on Fedora 31, bugzilla can't
send non-html (simple text/plain) emails anymore.
The reason seems to be a tighter control of how the method content_type_set()
is to be used. When sending non-html email, bugzilla uses a call
$email->content_type_set($parts[0]->content_type);
(BugMail.pm, line 499) where the given content_type contains the string
'text/plain; charset=UTF-8'. The content_type_set method splits on the / and
wants the second part to be a correct MIME subtype. But clearly it isn't since
it also contains a charset attribute.
The solution (what works for me) is to replace this call with two calls:
$email->content_type_set('text/plain');
$email->charset_set($use_utf8 ? 'UTF-8' : 'iso-8859-1');
Note that the code being executed is only used in case there is a single part
to be sent (i.e. not html which uses the other branch for multipart messages),
and so is definitely text/plain.
This problem occurs both in Fedora 31 and 32.
Version-Release number of selected component (if applicable):
bugzilla-5.0.6-3.fc31.noarch
perl-Email-MIME-1.949-1.fc31.noarch
perl-Email-MIME-ContentType-1.024-1.fc31.noarch
How reproducible:
100%
Steps to Reproduce:
1.configure bugzilla to send plain text emails (Administration -> Default
Parameters).
2.trigger bugzilla to send an email by e.g. adding or changing a bug.
3.
Actual results:
A page saying:
Invalid Content-Type 'subtype' parameter at Bugzilla/BugMail.pm line 499.
and no email being sent.
(during experimentation I added code to the report function to tell me the
content of this invalid subtype; it turned out to be 'plain; charset=UTF-8')
Expected results:
email being sent.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1835451] New: raise ValueError, errmsg # 'File Not Found in
bugzilla-submit
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1835451
Bug ID: 1835451
Summary: raise ValueError, errmsg # 'File Not Found in
bugzilla-submit
Product: Fedora
Version: 31
Status: NEW
Component: bugzilla
Severity: high
Assignee: itamar(a)ispbrasil.com.br
Reporter: atodorov(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: emmanuel(a)seyman.fr, itamar(a)ispbrasil.com.br,
perl-devel(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
/usr/share/bugzilla/contrib/bugzilla-submit/bugzilla-submit
File "/usr/share/bugzilla/contrib/bugzilla-submit/bugzilla-submit", line 38
raise ValueError, errmsg # 'File Not Found'
^
SyntaxError: invalid syntax
Documentation says I can run this with Python 2.3 or higher and indeed the file
has a python3 shebang. However it is invalid.
That is a Python2 only script which clearly doesn't have any tests executed
against it.
Version-Release number of selected component (if applicable):
bugzilla-contrib-5.0.6-3.fc31.noarch
How reproducible:
always
Steps to Reproduce:
1. dnf install bugzilla-contrib
2. /usr/share/bugzilla/contrib/bugzilla-submit/bugzilla-submit
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1823526] New: bugzilla fails to build with Sphinx 3.0.0
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1823526
Bug ID: 1823526
Summary: bugzilla fails to build with Sphinx 3.0.0
Product: Fedora
Version: rawhide
Status: NEW
Component: bugzilla
Assignee: itamar(a)ispbrasil.com.br
Reporter: cstratak(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cstratak(a)redhat.com, emmanuel(a)seyman.fr,
itamar(a)ispbrasil.com.br, mhroncok(a)redhat.com,
perl-devel(a)lists.fedoraproject.org
Blocks: 1783776
Target Milestone: ---
Classification: Fedora
bugzilla fails to build with Sphinx 3.0.0.
This report is automated and not very verbose, but we'll try to get back here
with details.
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/cstratak/sphinx_3.0.0/fed...
For all our attempts to build bugzilla with Sphinx 3.0.0, see:
https://copr.fedorainfracloud.org/coprs/cstratak/sphinx_3.0.0/package/bug...
Testing and mass rebuild of packages is happening in copr. You can follow these
instructions to test locally in mock if your package builds with Sphinx 3:
https://copr.fedorainfracloud.org/coprs/cstratak/sphinx_3.0.0/
Let us know here if you have any questions.
Sphinx 3 will be included in Fedora 33. To make that update smoother, we're
building the dependent packages in Copr.
We'd appreciate help from the people who know this package best, but if you
don't want to work on this now, let us know so we can try to work around it on
our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1783776
[Bug 1783776] python-sphinx-3.0.1 is available
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 6 months
[Bug 1848125] New: amavisd fails to start in multiple port config
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1848125
Bug ID: 1848125
Summary: amavisd fails to start in multiple port config
Product: Fedora
Version: 32
Hardware: x86_64
OS: Linux
Status: NEW
Component: amavisd-new
Severity: high
Assignee: j.orti.alcaine(a)gmail.com
Reporter: dan(a)islenet.com
QA Contact: extras-qa(a)fedoraproject.org
CC: janfrode(a)tanso.net, j.orti.alcaine(a)gmail.com,
perl-devel(a)lists.fedoraproject.org, steve(a)silug.org,
vanmeeuwen+fedora(a)kolabsys.com
Target Milestone: ---
Classification: Fedora
amavisd fails to start using recommend 2 port configuration:
$inet_socket_port = [10024,10026]; # listen on multiple TCP ports
The failure occurs because the selinux-policy has labelled port 10026 as for
use by spamd.
[root]# semanage port -l | grep spamd
spamd_port_t tcp 783, 10026, 10027
Another port could be used as a workaround but it would be helpful for the
amavisd and selinux team to identify another recommended port for the 2nd
instance which would be properly labeled in the selinux policy.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months
[Bug 1802607] New: perl-Net-DNS-1.22 is available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1802607
Bug ID: 1802607
Summary: perl-Net-DNS-1.22 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Net-DNS
Keywords: FutureFeature, Triaged
Assignee: pwouters(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
john.j5live(a)gmail.com, kasal(a)ucw.cz,
perl-devel(a)lists.fedoraproject.org,
pwouters(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 1.22
Current version/release in rawhide: 1.21-2.fc32
URL: http://search.cpan.org/dist/Net-DNS/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/3147/
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months
[Bug 1831324] New: perl-POE: please add epel8 branch
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1831324
Bug ID: 1831324
Summary: perl-POE: please add epel8 branch
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: perl-POE
Assignee: steve.traylen(a)cern.ch
Reporter: denis(a)fateyev.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org,
steve.traylen(a)cern.ch
Target Milestone: ---
Classification: Fedora
Description of problem:
Please add epel8 build for `perl-POE` package.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months