ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Alexey Gladkov <legion@altlinux.ru>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] I: upcoming mass package removal
Date: Mon, 22 Nov 2021 14:00:57 +0100
Message-ID: <20211122130057.nk3p42iw6npugenl@example.org> (raw)
In-Reply-To: <20211122124510.GA25119@altlinux.org>

On Mon, Nov 22, 2021 at 03:45:10PM +0300, Dmitry V. Levin wrote:
> Hi,
> 
> Обратите внимание, что FTBFS нижеперечисленных пакетов достигнет 13 недель
> уже в конце этой недели, после чего они начнут автоматически удаляться из
> Сизифа.
> 
> ----- Forwarded message from ALT beekeeper <hiver@altlinux> -----
> 
> Date: Mon, 22 Nov 2021 05:44:40 +0000 (UTC)
> From: ALT beekeeper <hiver@altlinux>
> To: sisyphus-cybertalk@lists.altlinux.org
> Subject: [cyber] I: Sisyphus-20211122 REBUILD x86_64 status
> 
> This is a summary of the x86_64 package rebuild test finished at 22.11.2021.
> 
> Numbers in [square brackets] describe how many weeks corresponding
> packages cannot be rebuilt.
> 
> Orphaned packages that cannot be rebuilt for 13+ weeks are
> usually removed from the repository without further warnings.
> 
> List of 9 orphaned packages that have no assignee to send information
> about rebuild failures:
> 
> [...]
> gtk-engines-wonderland-1.0-alt1.qa1 [12]
> gtk2-theme-nimbus-0.1.3-alt1.qa1 [12]
> mt-daapd-0.2.4.1586-alt1.qa1 [12]
> pmplib-0.14-alt0.1.qa2 [12]
> polyml-5.4.1-alt4 [12]
> random-20080825-alt3 [12]
> 
> List of 163 packages that cannot be rebuilt for more than one week:
> 
> [...]
> 4th-3.62.2-alt1 [12] (led,@everybody)
> avrdude-6.3-alt5 [12] (week,sin,viy,@everybody)
> canorus-0.7.3.git3a25392-alt2 [12] (majioa,@everybody)
> dpdk-19.11.8-alt1 [12] (snejok,@everybody)
> elinks-0.12-alt0.12.8 [12] (george,glebfm,at,@everybody)

elinks чуть-чуть жалко.

-- 
Rgrds, legion



  parent reply	other threads:[~2021-11-22 13:00 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 12:45 Dmitry V. Levin
2021-11-22 12:59 ` Sergey V Turchin
2021-11-22 13:04   ` Dmitry V. Levin
2021-11-22 13:10     ` Sergey V Turchin
2021-11-22 13:17       ` Dmitry V. Levin
2021-11-22 13:24         ` Sergey V Turchin
2021-11-22 14:55           ` Anton Farygin
2021-11-22 15:07             ` Anton Farygin
2021-11-22 15:16               ` Sergey V Turchin
2021-11-22 13:00 ` Alexey Gladkov [this message]
2021-11-22 13:05   ` Vladislav Zavjalov
2021-11-22 15:35     ` Alexey V. Vissarionov
2021-11-22 16:45       ` Vladislav Zavjalov
2021-11-22 19:06         ` Andrey Savchenko
2021-11-22 20:16           ` Vladislav Zavjalov
2021-11-28 18:41             ` [devel] I: upcoming mass package removal - elinks Vladislav Zavjalov
2021-11-22 13:06   ` [devel] I: upcoming mass package removal Dmitry V. Levin
2021-11-22 13:15     ` Alexey Gladkov
2021-11-22 13:41       ` Vladislav Zavjalov
2021-11-22 13:16     ` Oleg Solovyov
2021-11-22 13:21       ` Dmitry V. Levin
2021-11-22 13:38         ` Nikolai Kostrigin
2021-11-22 15:14           ` Alexey V. Vissarionov
2021-11-24 20:10 ` Igor Vlasenko
2021-11-25  0:21   ` Dmitry V. Levin
2021-11-25  1:55     ` Alexey V. Vissarionov
2021-11-25  7:16     ` Sergey V Turchin
2021-11-25  7:58       ` Vladimir Didenko
2021-11-25  9:00         ` Alexey V. Vissarionov
2021-11-25 11:42       ` Dmitry V. Levin
2021-11-25 12:46         ` Sergey V Turchin
2021-11-25 13:49           ` Dmitry V. Levin
2021-11-25 14:47             ` Sergey V Turchin
2021-11-25 15:06               ` Dmitry V. Levin
2021-11-25 15:31                 ` Sergey V Turchin
2021-11-25 15:42                   ` Dmitry V. Levin
2021-11-26  7:35                     ` Sergey V Turchin
2021-11-26  8:35                       ` Dmitry V. Levin
2021-11-26 10:31                         ` Sergey V Turchin
2021-11-25 17:08                 ` Igor Vlasenko
2021-11-25 17:25                   ` Dmitry V. Levin
2021-11-25  7:11   ` Arseny Maslennikov
2021-11-25 11:48     ` 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=20211122130057.nk3p42iw6npugenl@example.org \
    --to=legion@altlinux.ru \
    --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