ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Sviataslau Svirydau <Sviataslau_Svirydau@epam.com>
To: ALT Devel discussion list <devel@altlinux.ru>
Subject: [devel] packaging python-related packaged for backports
Date: Wed, 22 Jun 2005 11:05:09 +0300
Message-ID: <42B91BB5.4040902@epam.com> (raw)

Господа,

киньте, плз, в меня python policy 
(http://www.neural.ru/Products/Python/Policy не отвечает, гугл из кэша 
тоже не отдает) и помогите разобраться что происходит и как правильно...

Суть вот в чем:
Собираю subversion-1.2.0 для backports. apt настроен на Master 2.4 + 
updates.
В спеке имеется:
BuildPreReq: python-devel = 2.3

При сборке в хэшере получаю ругань такого вида:

...
Selected version 2.3.3-alt12 for python-devel
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  python-dev: Depends: python-base (= 2.3.3-alt12) but 2.3.3-alt12.M24.1 
is to be installed
E: Broken packages

Почему выбирается python-dev-2.3.3-alt12, а не 
python-dev-2.3.3-alt12.M24.1? Обе версии доступны для aptbox/apt-cache. 
Предыдущая сборка для backports собиралась, в сизифе с BuildPreReq: 
python-devel = 2.4 тоже все собирается.
Если я вместо python-devel = 2.3 укажу просто python-dev, то тоже 
собирается...

И что таки делать? указать python-dev или все же разбираться (чесгря, 
несколько дней периодически возвращаюсь к этому вопросу, но новых мыслей 
нет...)?

--
svd




             reply	other threads:[~2005-06-22  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22  8:05 Sviataslau Svirydau [this message]
2005-06-22  9:47 ` Andrei Bulava
2005-06-22 10:28   ` Sviatoslav Sviridov
2005-06-22 12:20     ` Grigory Batalov
2005-06-22 14:05       ` Sviatoslav Sviridov
2005-06-22 11:12 ` Геннадий Ковалев

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=42B91BB5.4040902@epam.com \
    --to=sviataslau_svirydau@epam.com \
    --cc=devel@altlinux.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