ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] [#187391] FAILED (try 32) 389-ds-base.git=1.3.7.8-alt1
Date: Sun, 31 Dec 2017 04:27:01 +0300
Message-ID: <20171231012701.GA27551@altlinux.org> (raw)
In-Reply-To: <20171231011004.GA7064@gyle.altlinux.org>

[-- Attachment #1: Type: text/plain, Size: 6553 bytes --]

On Sun, Dec 31, 2017 at 01:10:04AM +0000, Girar Builder awaiter robot wrote:
> http://git.altlinux.org/tasks/187391/logs/events.32.1.log
> 
> 2017-Dec-31 00:56:51 :: test-only shared task #187391 for sisyphus resumed by cas:
[...]
> #1300 build 1.3.7.8-alt1 from /people/cas/packages/389-ds-base.git
> 2017-Dec-31 00:56:52 :: [x86_64] #1300 389-ds-base.git 1.3.7.8-alt1: build start
> 2017-Dec-31 00:56:52 :: [i586] #1300 389-ds-base.git 1.3.7.8-alt1: build start
> 2017-Dec-31 01:03:53 :: [x86_64] #1300 389-ds-base.git 1.3.7.8-alt1: build OK
> 2017-Dec-31 01:04:41 :: [i586] #1300 389-ds-base.git 1.3.7.8-alt1: build OK
> 2017-Dec-31 01:04:50 :: build check OK
> 2017-Dec-31 01:04:53 :: noarch check OK
> 2017-Dec-31 01:04:54 :: plan: src +1 -1 =18240, i586 +5 -5 =33780, noarch +1 -1 =18588, x86_64 +5 -5 =33776
> 2017-Dec-31 01:04:54 :: version check OK
> 2017-Dec-31 01:05:37 :: generated apt indices
> 2017-Dec-31 01:05:37 :: created next repo
> 2017-Dec-31 01:05:50 :: dependencies check OK
> 2017-Dec-31 01:06:17 :: ELF symbols check OK
> 	x86_64: 389-ds=1.3.7.8-alt1 install failed:
> Reading Package Lists...
> Building Dependency Tree...
> MI2a: mark 389-ds
> MI2a:  target 389-admin
> MI2a:   mark 389-admin
> MI2a:    target apache2-mod_nss
> MI2a:     mark apache2-mod_nss
> MI2a:      target net-tools
> MI2a:       mark net-tools
> MI2a:    target 389-ds-base
> MI2a:     mark 389-ds-base
> MI2a:      target /etc/sysconfig/network AMB
> MI2a:  target 389-admin-console
> MI2a:   mark 389-admin-console
> MI2a:  target 389-admin-console-doc
> MI2a:   mark 389-admin-console-doc
> MI2b: mark 389-ds-base
> MI2b:  target /etc/sysconfig/network AMB
> MI2c: mark 389-ds-base
> MI2c:  target /etc/sysconfig/network
> MI2c:   mark rcnet
> MI2c:    delete systemd
> MI2c:    delete net-tools
> MI2c:  target /bin/systemctl
> Starting
> Starting 2
> Investigating apache2-mod_nss
> Package apache2-mod_nss has broken dep on net-tools
>   Considering net-tools 1 as a solution to apache2-mod_nss 2
>   Holding Back apache2-mod_nss rather than change net-tools
> Investigating rcnet
> Package rcnet has broken dep on systemd
>   Considering systemd 3 as a solution to rcnet -1
>   Holding Back rcnet rather than change systemd
> Investigating 389-admin
> Package 389-admin has broken dep on apache2-mod_nss
>   Considering apache2-mod_nss 2 as a solution to 389-admin 5
>   Holding Back 389-admin rather than change apache2-mod_nss
> Investigating 389-ds-base
> Package 389-ds-base has broken dep on /etc/sysconfig/network
>   Considering rcnet -1 as a solution to 389-ds-base 5
>   Holding Back 389-ds-base rather than change /etc/sysconfig/network
> Investigating 389-admin-console
> Package 389-admin-console has broken dep on 389-admin
>   Considering 389-admin 5 as a solution to 389-admin-console 3
>   Holding Back 389-admin-console rather than change 389-admin
> Investigating 389-admin-console-doc
> Package 389-admin-console-doc has broken dep on 389-admin-console
>   Considering 389-admin-console 3 as a solution to 389-admin-console-doc 2
>   Holding Back 389-admin-console-doc rather than change 389-admin-console
> Investigating 389-ds
> Package 389-ds has broken dep on 389-admin
>   Considering 389-admin 5 as a solution to 389-ds 9999
>   Re-Instated net-tools
>   Re-Instated apache2-mod_nss
>   Re-Instated rcnet
>   Re-Instated 389-ds-base
>   Re-Instated 389-admin
> Package 389-ds has broken dep on 389-admin-console
>   Considering 389-admin-console 3 as a solution to 389-ds 9999
>   Re-Instated 389-admin-console
> Package 389-ds has broken dep on 389-admin-console-doc
>   Considering 389-admin-console-doc 2 as a solution to 389-ds 9999
>   Re-Instated 389-admin-console-doc
> Investigating rcnet
> Package rcnet has broken dep on systemd
>   Considering systemd 3 as a solution to rcnet -1
>   Holding Back rcnet rather than change systemd
> Investigating 389-ds-base
> Package 389-ds-base has broken dep on /etc/sysconfig/network
>   Considering rcnet -1 as a solution to 389-ds-base 5
>   Holding Back 389-ds-base rather than change /etc/sysconfig/network
> Investigating 389-ds
> Package 389-ds has broken dep on 389-ds-base
>   Considering 389-ds-base 5 as a solution to 389-ds 9999
> Investigating 389-admin
> Package 389-admin has broken dep on 389-ds-base
>   Considering 389-ds-base 5 as a solution to 389-admin 5
>   Holding Back 389-admin rather than change 389-ds-base
> Investigating 389-admin-console
> Package 389-admin-console has broken dep on 389-admin
>   Considering 389-admin 5 as a solution to 389-admin-console 3
>   Holding Back 389-admin-console rather than change 389-admin
> Investigating 389-admin-console-doc
> Package 389-admin-console-doc has broken dep on 389-admin-console
>   Considering 389-admin-console 3 as a solution to 389-admin-console-doc 2
>   Holding Back 389-admin-console-doc rather than change 389-admin-console
> Investigating 389-ds
> Package 389-ds has broken dep on 389-admin
>   Considering 389-admin 5 as a solution to 389-ds 9999
> Package 389-ds has broken dep on 389-admin-console
>   Considering 389-admin-console 3 as a solution to 389-ds 9999
> Package 389-ds has broken dep on 389-admin-console-doc
>   Considering 389-admin-console-doc 2 as a solution to 389-ds 9999
> Package 389-ds has broken dep on 389-ds-base
>   Considering 389-ds-base 5 as a solution to 389-ds 9999
> Done
> 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.
> 
> Since you only requested a single operation it is extremely likely that
> the package is simply not installable and a bug report against
> that package should be filed.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   389-ds: Depends: 389-admin
>           Depends: 389-admin-console
>           Depends: 389-admin-console-doc
>           Depends: 389-ds-base (= 1.3.7.8-alt1)
> E: Broken packages
> hsh-install: Failed to calculate package file list.
> hsh-install: Failed to generate package file list.

Co 2 по 31 итерацию пакет собирался нормально, но вот в Сизиф был закинут
пакет rcnet, и всё, полный привет.

Поскольку etcnet < rcnet, сейчас в Сизифе, вероятно, сломана сборка
дистрибутивов на etcnet.


-- 
ldv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

       reply	other threads:[~2017-12-31  1:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-31  1:27 ` Dmitry V. Levin [this message]
2017-12-31  5:49   ` Anton Farygin
2017-12-31  9:02     ` Dmitry V. Levin
2018-01-04 15:22   ` Alexey V. Vissarionov
2018-01-04 15:35     ` Dmitry V. Levin
2018-01-04 17:01       ` Alexey V. Vissarionov
2018-01-04 17:13         ` Dmitry V. Levin
2018-01-11 18:16         ` Alexey Shabalin
2018-01-11 18:25           ` Dmitry V. Levin
2018-01-11 19:25             ` Alexey Shabalin
2018-01-12 11:24               ` Mikhail Efremov
2018-01-12 16:57                 ` Alexey Shabalin
2018-01-12  9:26           ` Sergey Afonin
2018-01-12  9:48             ` Alexey V. Vissarionov
2018-01-12 10:09               ` Sergey Afonin
2018-01-12 16:58             ` Alexey Shabalin
2018-01-12  9:35           ` Alexey V. Vissarionov

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=20171231012701.GA27551@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=devel@lists.altlinux.org \
    /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