[Bug 523547] New: virt-df doesn't pull correct dependencies
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: virt-df doesn't pull correct dependencies
https://bugzilla.redhat.com/show_bug.cgi?id=523547
Summary: virt-df doesn't pull correct dependencies
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: virt-df
AssignedTo: rjones(a)redhat.com
ReportedBy: emcnabb(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, fedora-virt-maint(a)redhat.com,
fedora-ocaml-list(a)redhat.com
Classification: Fedora
Target Release: ---
Description of problem:
The virt-df RPM doesn't pull in perl-XML-XPath.noarch which is required.
Version-Release number of selected component (if applicable):
virt-df.x86_64 1:1.0.68-2.fc11
How reproducible:
Every time
Steps to Reproduce:
# yum install -y virt-df
...
# virt-df
Filesystem 1K-blocks Used Available Use%
open_guest: no libvirt support (install Sys::Virt, XML::XPath and
XML::XPath::XMLParser) at
/usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/Sys/Guestfs/Lib.pm
line 148.
# yum install -y perl-XML-XPath
...
# virt-df
Filesystem 1K-blocks Used Available Use%
RHEL5.3-64:/dev/VolGroup00/LogVol00
9014656 7208796 1340556 85.1%
...correct output...
Actual results:
Expected results:
perl-XML-XPath should be added as a dependency.
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years
Broken dependencies: ocaml-libvirt
by Fedora Koji Build System
ocaml-libvirt has broken dependencies in the development tree:
On ppc:
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.2)
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.3.4)
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.4)
mlvirsh-0.6.1.0-6.fc12.ppc requires libvirt.so.0
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.1)
mlvirsh-0.6.1.0-6.fc12.ppc requires libm.so.6(GLIBC_2.0)
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.1.2)
mlvirsh-0.6.1.0-6.fc12.ppc requires libdl.so.2(GLIBC_2.1)
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6
mlvirsh-0.6.1.0-6.fc12.ppc requires libdl.so.2(GLIBC_2.0)
mlvirsh-0.6.1.0-6.fc12.ppc requires libdl.so.2
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.7)
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.0)
mlvirsh-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.3)
mlvirsh-0.6.1.0-6.fc12.ppc requires libm.so.6(GLIBC_2.1)
mlvirsh-0.6.1.0-6.fc12.ppc requires libm.so.6
On ppc64:
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libm.so.6()(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libc.so.6()(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libc.so.6(GLIBC_2.3.4)(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libdl.so.2()(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libvirt.so.0()(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libc.so.6(GLIBC_2.4)(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libm.so.6(GLIBC_2.3)(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libc.so.6(GLIBC_2.7)(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libc.so.6(GLIBC_2.3)(64bit)
mlvirsh-0.6.1.0-6.fc12.ppc64 requires libdl.so.2(GLIBC_2.3)(64bit)
On ppc:
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(Buffer) = 0:23af67395823b652b807c4ae0b581211
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.4)
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(Pervasives) = 0:88cb1505c8bdf9a4dcd2cdf3452732b4
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires libvirt.so.0
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(Array) = 0:9c9fa5f11e2d6992c427dde4d1168489
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(String) = 0:ecc403546c1c50056801131811c39017
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires libc.so.6
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(Callback) = 0:71e1f9b7f211661f1dfeedab5ffae0cc
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.0)
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(runtime) = 0:3.11.1
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(List) = 0:a0e2e49d266ff302f8667651a43f71ba
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires libc.so.6(GLIBC_2.1.3)
ocaml-libvirt-0.6.1.0-6.fc12.ppc requires ocaml(Char) = 0:3da72249626c7db769beafc97036cb4f
On ppc64:
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(Buffer) = 0:23af67395823b652b807c4ae0b581211
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(Pervasives) = 0:88cb1505c8bdf9a4dcd2cdf3452732b4
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires libc.so.6()(64bit)
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(Array) = 0:9c9fa5f11e2d6992c427dde4d1168489
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(Callback) = 0:71e1f9b7f211661f1dfeedab5ffae0cc
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires libvirt.so.0()(64bit)
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires libc.so.6(GLIBC_2.4)(64bit)
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(String) = 0:ecc403546c1c50056801131811c39017
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(runtime) = 0:3.11.1
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(List) = 0:a0e2e49d266ff302f8667651a43f71ba
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires libc.so.6(GLIBC_2.3)(64bit)
ocaml-libvirt-0.6.1.0-6.fc12.ppc64 requires ocaml(Char) = 0:3da72249626c7db769beafc97036cb4f
Please resolve this as soon as possible.
14 years, 4 months
yum install ocaml-lacaml
by onkar bhardwaj
Hi,
I executed "yum install ocaml-lacaml" on my system but I don't know how to
use it.
Since this was installed using rpm, I am unable to know what module to open
or
which library to link and where yum has installed these things.
Can someone send me a sample example? It will be a big help.
Thanks in anticipation,
--
---------------------------------------------
Onkar Bhardwaj
M.E. 2006-08 (Telecommunication)
Indian Institute of Science, Bangalore
---------------------------------------------
14 years, 4 months
[Bug 541427] New: ocaml-cairo-devel needs to require ocaml-lablgtk-devel
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: ocaml-cairo-devel needs to require ocaml-lablgtk-devel
https://bugzilla.redhat.com/show_bug.cgi?id=541427
Summary: ocaml-cairo-devel needs to require ocaml-lablgtk-devel
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ocaml-cairo
AssignedTo: rjones(a)redhat.com
ReportedBy: orion(a)cora.nwra.com
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, fedora-ocaml-list(a)redhat.com
Classification: Fedora
Description of problem:
yum -y install ocaml-cairo-devel - does not install ocaml-lablgtk-devel, and:
# cat test_cairo.ml
module C = Cairo
# ocamlfind c -package cairo -linkpkg test_cairo.ml -o test_cairo
ocamlfind: Package `lablgtk2' not found - Required by `cairo.lablgtk2'
Version-Release number of selected component (if applicable):
1.0.0-1.fc13
Other error after ocaml-lablgtk-devel is:
# ocamlfind c -package cairo -linkpkg test_cairo.ml -o test_cairo
File "test_cairo.ml", line 1, characters 0-1:
Error: Error on dynamically loaded library:
/usr/lib/ocaml/stublibs/dllmlcairo.so: /usr/lib/ocaml/stublibs/dllmlcairo.so:
undefined symbol:
cairo_ps_surface_set_dpi_REPLACED_BY_cairo_surface_set_fallback_resolution
can file separate bug if desired.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 4 months
rpms/ocaml-cairo/devel ocaml-cairo.spec,1.14,1.15
by Richard W.M. Jones
Author: rjones
Update of /cvs/pkgs/rpms/ocaml-cairo/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv6345
Modified Files:
ocaml-cairo.spec
Log Message:
ocaml-cairo-devel requires ocaml-lablgtk-devel (RHBZ#541427).
Index: ocaml-cairo.spec
===================================================================
RCS file: /cvs/pkgs/rpms/ocaml-cairo/devel/ocaml-cairo.spec,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -p -r1.14 -r1.15
--- ocaml-cairo.spec 8 Oct 2009 11:51:35 -0000 1.14
+++ ocaml-cairo.spec 26 Nov 2009 09:39:41 -0000 1.15
@@ -4,7 +4,7 @@
Name: ocaml-cairo
Epoch: 1
Version: 1.0.0
-Release: 1%{?dist}
+Release: 2%{?dist}
Summary: OCaml library for accessing cairo graphics
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
@@ -51,6 +51,7 @@ PDF 1.4.
Summary: Development files for %{name}
Group: Development/Libraries
Requires: %{name} = %{epoch}:%{version}-%{release}
+Requires: ocaml-lablgtk-devel
%description devel
@@ -115,6 +116,9 @@ rm -rf $RPM_BUILD_ROOT
%changelog
+* Thu Nov 26 2009 Richard W.M. Jones <rjones(a)redhat.com> - 1:1.0.0-2
+- ocaml-cairo-devel requires ocaml-lablgtk-devel (RHBZ#541427).
+
* Thu Oct 8 2009 Richard W.M. Jones <rjones(a)redhat.com> - 1:1.0.0-1
- New upstream version 1.0.0.
- Yes, version number really did roll backwards, so now we're using Epoch.
14 years, 4 months
[RFA] Your ocaml package did not pass QA
by repo-font-audit
Dear packager,
At 20091122T202901Z, your “ocaml” package failed one or more of the tests
I was performing on the “fedora-devel” repository located at:
http://koji.fedoraproject.org/static-repos/dist-f13-build-current/x86_64/
There are three different reasons that may cause this message:
1. your package is including one or more font files, but not packaging
them properly;
2. your package is including one or more font files, and I've found
issues in some of them;
3. your package is not shipping any font file, but the way it accesses
fonts in other packages is not satisfying.
To stop receiving this message, you need to:
1. drop the font files or fix their packaging;
2. relay the fonts issues to the fonts upstream to get them revised;
3. work with the code upstream to improve the way it accesses font
files (usually by making it use fontconfig through a higher-level
text library such as pango, pango-cairo, harfbuzz, or QT)
You can self-check your packages at any time by:
1. installing createrepo and fontpackages-tools:
# yum install createrepo fontpackages-tools
2. putting your packages and any font package they depends on in a
test directory
3. indexing this directory with createrepo:
$ createrepo path-to-test-directory
4. running repo-font-audit:
$ repo-font-audit test file://absolute-path-to-test-directory
A summary of the issues I detected is appended here. For your
convenience a more comprehensive analysis is also attached to this
message.
Errors, warnings and suggestions:
P# t14
1 1
2 1
Total 2
P# Maintainer SRPM RPM EVR Arch
1 gemi ocaml ocaml-runtime 0:3.11.1-6.fc13 x86_64
2 gemi ocaml ocaml 0:3.11.1-6.fc13 x86_64
Test explanation:
t14. Warning: core fonts use
☛ Upstream task
This package accesses fonts through the X11 Core protocol.
Numerous long-standing problems with this mode of access, and a design
that could not scale to modern font needs lead the (then XFree86) team to
deprecate it in favour of fontconfig (née xft). Adoption was quick and by
2003 it was clear fontconfig was the new standard¹. Nowadays fontconfig is
widely used², including on non Linux/Unix platforms.
While X11 Core access has been kept on life-support this font system is
not actively maintained today. The font library it depends on is slowly
shrinking, as it was created in a period of different legal and technical
requirements², and there is no one to update the font files when a problem
is found³. Therefore, projects are advised to migrate before the situation
reaches a critical stage.
Fontconfig has been our default font system for a long time, and accessing
fonts by other means will cause behaviour inconsistencies and many other
problems (since fontconfig can be used to change the behaviour of a font).
If an application can not use fontconfig today this is a serious bug that
should be reported to the application upstream. Please ask it to add
fontconfig support to their code (usually, via a higher-level library
such as pango-cairo).
¹ http://xfree86.org/pipermail/forum/2003-March/000799.html
² Screen technology changed, encoding standard (Unicode) changed, legal
reviews became more comprehensive, etc.
³ Leaving culling the only solution.
Please take the appropriate measures to fix the “ocaml” package.
I will warn you again if it is still necessary next time I am ran.
This report was generated by the repo-font-audit command from:
http://fedoraproject.org/wiki/fontpackages
Please post questions, suggestions, patches or bug reports to:
https://www.redhat.com/mailman/listinfo/fedora-fonts-list
(subscription required)
Your friendly QA robot,
--
repo-font-audit
14 years, 4 months
[RFA] Your ocaml-lablgl package did not pass QA
by repo-font-audit
Dear packager,
At 20091122T202901Z, your “ocaml-lablgl” package failed one or more of the tests
I was performing on the “fedora-devel” repository located at:
http://koji.fedoraproject.org/static-repos/dist-f13-build-current/x86_64/
There are three different reasons that may cause this message:
1. your package is including one or more font files, but not packaging
them properly;
2. your package is including one or more font files, and I've found
issues in some of them;
3. your package is not shipping any font file, but the way it accesses
fonts in other packages is not satisfying.
To stop receiving this message, you need to:
1. drop the font files or fix their packaging;
2. relay the fonts issues to the fonts upstream to get them revised;
3. work with the code upstream to improve the way it accesses font
files (usually by making it use fontconfig through a higher-level
text library such as pango, pango-cairo, harfbuzz, or QT)
You can self-check your packages at any time by:
1. installing createrepo and fontpackages-tools:
# yum install createrepo fontpackages-tools
2. putting your packages and any font package they depends on in a
test directory
3. indexing this directory with createrepo:
$ createrepo path-to-test-directory
4. running repo-font-audit:
$ repo-font-audit test file://absolute-path-to-test-directory
A summary of the issues I detected is appended here. For your
convenience a more comprehensive analysis is also attached to this
message.
Errors, warnings and suggestions:
P# t14
1 1
Total 1
P# Maintainer SRPM RPM EVR Arch
1 gemi ocaml-lablgl ocaml-lablgl 0:1.04-2.fc12 x86_64
Test explanation:
t14. Warning: core fonts use
☛ Upstream task
This package accesses fonts through the X11 Core protocol.
Numerous long-standing problems with this mode of access, and a design
that could not scale to modern font needs lead the (then XFree86) team to
deprecate it in favour of fontconfig (née xft). Adoption was quick and by
2003 it was clear fontconfig was the new standard¹. Nowadays fontconfig is
widely used², including on non Linux/Unix platforms.
While X11 Core access has been kept on life-support this font system is
not actively maintained today. The font library it depends on is slowly
shrinking, as it was created in a period of different legal and technical
requirements², and there is no one to update the font files when a problem
is found³. Therefore, projects are advised to migrate before the situation
reaches a critical stage.
Fontconfig has been our default font system for a long time, and accessing
fonts by other means will cause behaviour inconsistencies and many other
problems (since fontconfig can be used to change the behaviour of a font).
If an application can not use fontconfig today this is a serious bug that
should be reported to the application upstream. Please ask it to add
fontconfig support to their code (usually, via a higher-level library
such as pango-cairo).
¹ http://xfree86.org/pipermail/forum/2003-March/000799.html
² Screen technology changed, encoding standard (Unicode) changed, legal
reviews became more comprehensive, etc.
³ Leaving culling the only solution.
Please take the appropriate measures to fix the “ocaml-lablgl” package.
I will warn you again if it is still necessary next time I am ran.
This report was generated by the repo-font-audit command from:
http://fedoraproject.org/wiki/fontpackages
Please post questions, suggestions, patches or bug reports to:
https://www.redhat.com/mailman/listinfo/fedora-fonts-list
(subscription required)
Your friendly QA robot,
--
repo-font-audit
14 years, 4 months
[RFA] Your ocaml package did not pass QA
by nim
Dear packager,
At 20091122T202901Z, your “ocaml” package failed one or more of the tests
I was performing on the “fedora-devel” repository located at:
http://koji.fedoraproject.org/static-repos/dist-f13-build-current/x86_64/
There are three different reasons that may cause this message:
1. your package is including one or more font files, but not packaging
them properly;
2. your package is including one or more font files, and I've found
issues in some of them;
3. your package is not shipping any font file, but the way it accesses
fonts in other packages is not satisfying.
To stop receiving this message, you need to:
1. drop the font files or fix their packaging;
2. relay the fonts issues to the fonts upstream to get them revised;
3. work with the code upstream to improve the way it accesses font
files (usually by making it use fontconfig through a higher-level
text library such as pango, pango-cairo, harfbuzz, or QT)
You can self-check your packages at any time by:
1. installing createrepo and fontpackages-tools:
# yum install createrepo fontpackages-tools
2. putting your packages and any font package they depends on in a
test directory
3. indexing this directory with createrepo:
$ createrepo path-to-test-directory
4. running repo-font-audit:
$ repo-font-audit test file://absolute-path-to-test-directory
A summary of the issues I detected is appended here. For your
convenience a more comprehensive analysis is also attached to this
message.
Errors, warnings and suggestions:
P# t14
1 1
2 1
Total 2
P# Maintainer SRPM RPM EVR Arch
1 gemi ocaml ocaml-runtime 0:3.11.1-6.fc13 x86_64
2 gemi ocaml ocaml 0:3.11.1-6.fc13 x86_64
Test explanation:
t14. Warning: core fonts use
☛ Upstream task
This package accesses fonts through the X11 Core protocol.
Numerous long-standing problems with this mode of access, and a design
that could not scale to modern font needs lead the (then XFree86) team to
deprecate it in favour of fontconfig (née xft). Adoption was quick and by
2003 it was clear fontconfig was the new standard¹. Nowadays fontconfig is
widely used², including on non Linux/Unix platforms.
While X11 Core access has been kept on life-support this font system is
not actively maintained today. The font library it depends on is slowly
shrinking, as it was created in a period of different legal and technical
requirements², and there is no one to update the font files when a problem
is found³. Therefore, projects are advised to migrate before the situation
reaches a critical stage.
Fontconfig has been our default font system for a long time, and accessing
fonts by other means will cause behaviour inconsistencies and many other
problems (since fontconfig can be used to change the behaviour of a font).
If an application can not use fontconfig today this is a serious bug that
should be reported to the application upstream. Please ask it to add
fontconfig support to their code (usually, via a higher-level library
such as pango-cairo).
¹ http://xfree86.org/pipermail/forum/2003-March/000799.html
² Screen technology changed, encoding standard (Unicode) changed, legal
reviews became more comprehensive, etc.
³ Leaving culling the only solution.
Please take the appropriate measures to fix the “ocaml” package.
I will warn you again if it is still necessary next time I am ran.
This report was generated by the repo-font-audit command from:
http://fedoraproject.org/wiki/fontpackages
Please post questions, suggestions, patches or bug reports to:
https://www.redhat.com/mailman/listinfo/fedora-fonts-list
(subscription required)
Your friendly QA robot,
--
repo-font-audit
14 years, 4 months