Should vim-X11 conflict with vim-enhanced ?
by Karsten Hopp
Hello,
Till proposed in bugzilla #311061 to use alternatives in vim-enhanced and vim-X11 so that
both of them can provide /usr/bin/vim. His reasoning as that when gvim gets started as vim
(via a symlink) it opens the text mode vim with the additional benefit of xterm clipboard support.
I agree with the /usr/bin/vim stuff, but I think a better solution would be to add a conflict between
vim-X11 and vim-enhanced. vim-enhanced is only of use on systems without X11/gtk. On all other
systems vim-X11 can provide the same (and more) functionality as vim-enhanced.
Karsten
--
Karsten Hopp | Mail: karsten(a)redhat.de
Red Hat Deutschland | Tel: +49-711-96437-0
Hauptstaetterstr.58 | Fax: +49-711-613590
D-70178 Stuttgart | http://www.redhat.de
16 years, 2 months
Package for python-svn (was pysvn)
by Timothy Selivanow
So, I've finally had some extra time to work on this and I've made a few
tweaks to the spec and one of the patches. It now builds fine,
including the tests in %check. Thank you Terje, and others for your
help :)
Here is the latest stuff:
http://yum.virtualxistenz.com/python-svn/
Questions, comments, screams-of-outrage, moral or immoral indignations?
--Tim
_____________________________________________________________
< Please, won't somebody tell me what diddie-wa-diddie means? >
-------------------------------------------------------------
\
\ \
\ /\
( )
.( o ).
16 years, 2 months
naming of "documentation-devel" package
by Jens-Ulrik Petersen
Hi,
A package named "documentation-devel" has been submitted for review to
Fedora recently:
https://bugzilla.redhat.com/show_bug.cgi?id=427481
It provides a comprehensive set of tools used by the Red Hat Docs team
and some others to build documentation written in docbook and its
translations into various formats.
The question is can we keep the name as is, since they are not keen on
changing it, or should the name of the package be changed?
Jens
16 years, 2 months
Automatic detection of Requires and versions
by Eduardo M KALINOWSKI
Hi,
I'm attempting to package a program I wrote, that uses the GTK+
libraries. It uses features first found in the 2.10.X series, so I
include
BuildRequires: gtk2-devel >= 2.10.0
(and similar lines for glib and other required libraries). All this is
OK. The problem is regarding the Requires for the generated .rpm. I
could use
Requires: gtk2 >= 2.10.0
but apparently this is bad style and bad for maintenance, because
dependencies are found automatically on build time. However, without
manually adding the requires, the generated .rpm contains (with regard
to GTK+) this:
libgtk-x11-2.0.so.0
that is, no mention of the version, and I expect that even a GTK+ 2.8
package (old as that may be) should provide that file with that name.
What is the best way to handle that? Include the Require manually?
Leave this as-is?
Thanks in advance,
16 years, 2 months
Re: Package for pysvn
by Timothy Selivanow
On Wed, 2008-01-09 at 11:09 +0100, Terje Røsten wrote:
> > Thanks for all of that. I'm still getting the "Package does not exist"
> > error (full error below). Even after removing rpm-build, `yum clean
> > all`, and reinstalling rpm-build I still get that error. I tried it on
> > my home computer just now and it worked (both x86_64, but one intel and
> > the other amd). What do I need to look at to fix this?
> >
> > Error:
> > "error: line 38: Package does not exist: %description debuginfo"
>
> OK, I need some more info. Can you try the following:
>
> Download the srpm:
>
> http://terjeros.fedorapeople.org/python-svn/python-svn-1.5.2-2.fc8.src.rpm
>
> Install by
>
> $ rpm -Uvh python-svn-1.5.2-2.fc8.src.rpm
>
> Now build by
>
> $ rpmbuild -ba /path/to/python-svn.spec
>
>
> Post any error output.
>
> Note: these lines
>
> %description debuginfo
> debug info
>
> in your original spec file should not be there, debuginfo packages is
> generated
> automagically by rpmbuild itself. Just remove those lines.
>
>
> - Terje
Same thing. I even did a rpmdev-wipetree to make sure I was using the
spec from the srpm. I think something is stuck in my environment, and I
don't know what it would be...
$ rpmdev-wipetree
Removing all build files...
$ ls -Al ./rpmbuild/SPECS/
total 0
$ rpm -Uvh ./python-svn-1.5.2-2.fc8.src.rpm
1:python-svn warning: user terjeros does not exist -
using root
warning: group fysikk does not exist - using root
warning: user terjeros does not exist - using root
warning: group fysikk does not exist - using root
warning: user terjeros does not exist - using root
warning: group fysikk does not exist - using root
########################################### [100%]
warning: user terjeros does not exist - using root
warning: group fysikk does not exist - using root
$ rpmbuild -ba ./rpmbuild/SPECS/python-svn.spec
error: line 38: Package does not exist: %description debuginfo
--Tim
______________________________________________________________
/ "Oh dear, I think you'll find reality's on the blink again." \
\ -- Marvin The Paranoid Android /
--------------------------------------------------------------
\
\ \
\ /\
( )
.( o ).
16 years, 2 months
Re: Package for pysvn
by Timothy Selivanow
On Mon, 2008-01-07 at 13:09 +0100, Terje Rosten wrote:
> * Timothy Selivanow
> |
> | I'm trying to make a package for pysvn [http://pysvn.tigris.org] and I
> | have a few questions. Right now it's not compiling, rpmbuild is
> | complaining about "error: line 27: Package does not exist: %description
> | debuginfo", this must have changed either in F7 or F8 because this spec
> | worked a long time ago (F6/F7, not sure which).
> |
> | Also, I discovered that the installer makes a differently named .so
> | depending on the version of python that it is compiling against, and I'd
> | like to know the best way to do an if style statement that will solve
> | that (I'd like to be able to use the same spec on CentOS too).
> |
> | So, any help and comments would be much appreciated. Thanks!
> |
> | Below is the spec file.
> |
> | ---BEGIN SPEC---
>
> Hi Tim,
>
> I took your spec and improved it a bit, spec, patches, srpm and rpm are
> available here:
>
> http://terjeros.fedorapeople.org/python-svn/
>
> Some notes:
> o renamed to python-svn (that's the proper way)
> o fixed license tag
> o add patch to remove rpath issue
> o add patch to remove the python version stuff
> o move tests to %%check (however they are failing...)
> o fixed src url
> o compile with fedora compile flags
> o use macros etc random clean up
>
> Feel free to improve further and submit for inclusion.
>
>
> - Terje
Thanks for all of that. I'm still getting the "Package does not exist"
error (full error below). Even after removing rpm-build, `yum clean
all`, and reinstalling rpm-build I still get that error. I tried it on
my home computer just now and it worked (both x86_64, but one intel and
the other amd). What do I need to look at to fix this?
Error:
"error: line 38: Package does not exist: %description debuginfo"
--Tim
______________________________________________________________________
< Be careful when a loop exits to the same place from side and bottom. >
----------------------------------------------------------------------
\
\ \
\ /\
( )
.( o ).
16 years, 2 months
release of subpackage with version different from main rpm
by Mamoru Tasaka
Hi:
I guess there are some packages of which subpackage rpms have versions
which are different from those of the main rpm.
For example, on rawhide perl has 4:5.8.8-32.fc8 EVR and its subpackage
perl-ExtUtils-MakeMaker has 0:6.30-32.fc8 EVR.
On such case are there any policy for release number? For perl currently
the main perl rpm and its subpackages have the same release number.
However in other rpms the case may happen that only the version of
main rpm will be bumped where the version of its subpackage won't change.
In that case usually we want to switch the release number of main rpm
to 1%{?dist}, however if its subpackage has different version the release
number of the subpackage usually can't be back to 1%{?dist}. How should
we treat this case?
Regards,
Mamoru
16 years, 2 months
Services enabled by default when installed
by Jason L Tibbitts III
I've always understood that services should not be enabled by default,
because people tend to install more than they actually want to run.
And of course rpmlint complains about any initscript that starts on by
default.
However, I don't actually see any mention of this in the guidelines,
only this text in ScriptletSnippets:
"
Why don't we....
* run 'chkconfig <service> on'?
o If a service should be enabled by default, make this the
default in the init script. Doing otherwise will cause the
service to be turned on on upgrades if the user explicitly
disabled it. Note that the default for most
network-listening scripts is off. This is done for better
security. We have multiple tools that can enable services,
including GUIs.
* start the service after installation?
o Installations can be in changeroots, in an installer
context, or in other situations where you don't want the
services started.
"
So, is it OK if a packager wants their service enabled by default?
- J<
16 years, 2 months
Package for pysvn
by Timothy Selivanow
I'm trying to make a package for pysvn [http://pysvn.tigris.org] and I
have a few questions. Right now it's not compiling, rpmbuild is
complaining about "error: line 27: Package does not exist: %description
debuginfo", this must have changed either in F7 or F8 because this spec
worked a long time ago (F6/F7, not sure which).
Also, I discovered that the installer makes a differently named .so
depending on the version of python that it is compiling against, and I'd
like to know the best way to do an if style statement that will solve
that (I'd like to be able to use the same spec on CentOS too).
So, any help and comments would be much appreciated. Thanks!
Below is the spec file.
---BEGIN SPEC---
%{!?python_sitearch: %define python_sitearch %(%{__python} -c "from
distutils.sysconfig import get_python_lib; print get_python_lib(1)")}
%{!?python_version: %define python_version %(%{__python} -c 'from sys
import version_info; print str(version_info[0]) + "." +
str(version_info[1])')}
Name: pysvn
Version: 1.5.2
Release: 1%{dist}
Summary: Pythonic style bindings for Subversion
Group: Development/Languages
License: http://www.apache.org/LICENSE.txt
URL: http://pysvn.tigris.org/
Source0: pysvn-%{version}.tar.gz
BuildRoot:
%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: python > 2.3
BuildRequires: python-devel
BuildRequires: PyXML
BuildRequires: subversion-devel
BuildRequires: libgssapi-devel
BuildRequires: neon-devel
BuildRequires: chrpath
%description
Pythonic style bindings for Subversion
%description debuginfo
debug info
%prep
%setup -q
%build
cd Source
CFLAGS="$RPM_OPT_FLAGS" %{__python} setup.py configure
make
cd ../Tests
make
%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT%{python_sitearch}/pysvn
cp Source/pysvn/__init__.py $RPM_BUILD_ROOT%{python_sitearch}/pysvn
cp Source/pysvn/__init__.pyc $RPM_BUILD_ROOT%{python_sitearch}/pysvn
#%if %(test [ "%{python_version}" == "2.5" ])
cp Source/pysvn/_pysvn_2_5.so $RPM_BUILD_ROOT%{python_sitearch}/pysvn
chrpath --delete $RPM_BUILD_ROOT%{python_sitearch}/pysvn/_pysvn_2_5.so
cd $RPM_BUILD_ROOT%{python_sitearch}/pysvn
ln -s _pysvn_2_5.so _pysvn.so
#%else
#cp Source/pysvn/_pysvn.so $RPM_BUILD_ROOT%{python_sitearch}/pysvn
#chrpath --delete $RPM_BUILD_ROOT%{python_sitearch}/pysvn/_pysvn.so
#%endif
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Docs/pysvn.html Docs/pysvn_prog_guide.html Docs/pysvn_prog_ref.html
Docs/pysvn_prog_ref.js
%{python_sitearch}/pysvn
%changelog
* Fri Jan 04 2008 Timothy Selivanow
<timothy.selivanow(a)virtualxistenz.com> - 1.5.2-2
- Attempting to make the spec work with different versions of Python
* Mon Sep 03 2007 Timothy Selivanow
<timothy.selivanow(a)virtualxistenz.com> - 1.5.2-1
- Update to 1.5.2
- Some spec clean up
* Fri Jan 12 2007 Timothy Selivanow
<timothy.selivanow(a)virtualxistenz.com> - 1.5.0-1
- Initial spec creation
---END SPEC---
--Tim
____________________________________________________________________________
/ If you will practice being fictional for a while, you will understand that \
| fictional characters are sometimes more real than people with bodies and |
\ heartbeats. /
----------------------------------------------------------------------------
\
\ \
\ /\
( )
.( o ).
16 years, 2 months