From: mookid@sigent.ru (Mikhail Zabaluev)
To: devel@linux.iplabs.ru
Subject: [devel] RPM versioning bug?
Date: Sun, 8 Oct 2000 01:25:12 +0400
Message-ID: <20001008012512.B12932@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Доброе время суток.
Занимаясь версиями и эпохами в пакетах RPM, обнаружил такой эффект:
если одному пакету в spec приписана эпоха тэгом 'Epoch:', и другой пакет
требует версию из этой эпохи, такая зависимость не проходит, даже если
требуемая версия совпадает с версией установленного первого пакета.
Помогает только тупое указание в 'Provides:' первого пакета его имени и
версии с эпохой. Пример spec'а прилагается.
Об этом, наверное, неплохо бы доложить на RH Bugzilla...
--
Stay tuned,
MhZ mailto:mookid@sigent.ru
-----------
Truth can wait; he's used to it.
[-- Attachment #2: test.spec --]
[-- Type: text/plain, Size: 901 bytes --]
%define dummypath /home/mhz/tmp
Name: test
Summary: Dependency testing package
Group: Test
Epoch: 1
Version: 5.6.0
Release: 1
License: strictly commercial ;)
Provides: test = 0:5.600
#the following directive makes everything work:
#Provides: test = 1:5.6.0 test = 0:5.600
BuildArchitectures: noarch
BuildRoot: %{_tmppath}/%{name}-buildroot
%description
This package provides itself with different versions in two epochs.
%package dependent
Summary: package dependent on the 'test' package
Group: Test
Requires: test = 1:5.6.0
%description dependent
This package has a versioned dependency on the test package.
%install
mkdir -p $RPM_BUILD_ROOT%{dummypath}
touch $RPM_BUILD_ROOT%{dummypath}/{dummy,dummy1}
%clean
rm -rf $RPM_BUILD_ROOT
%post
echo 'test is installed.'
%post dependent
echo 'test-dependent is installed.'
%files
%{dummypath}/dummy
%files dependent
%{dummypath}/dummy1
next reply other threads:[~2000-10-07 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-07 21:25 Mikhail Zabaluev [this message]
2000-10-08 21:32 ` Dmitry V. Levin
2000-10-09 3:34 ` Mikhail Zabaluev
2000-10-09 7:52 ` Dmitry V. Levin
2000-10-21 22:54 ` Dmitry V. Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001008012512.B12932@localhost.localdomain \
--to=mookid@sigent.ru \
--cc=devel@linux.iplabs.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git