From: Lenar Shakirov <shakirov@cg.ru> To: ALT Linux Team development discussions <devel@lists.altlinux.org> Subject: Re: [devel] [#69737] t6 FAILED patchage.git=0.4.2-alt2.M60T.1 Date: Mon, 16 Apr 2012 16:14:07 +0400 Message-ID: <4F8C0D0F.7070207@cg.ru> (raw) In-Reply-To: <20120416120628.GA28472@ssh.git.altlinux.org> 16.04.2012 16:06, Girar Builder robot пишет: > http://git.altlinux.org/tasks/69737/logs/events.1.1.log <skip> > *** source package version is either the same or older than existing > patchage 0.4.2-alt2.qa1 0.4.2-alt2.M60T.1 > *** binary package version is either the same or older than existing > patchage 0.4.2-alt2.qa1 0.4.2-alt2.M60T.1 > *** binary package version is either the same or older than existing > patchage 0.4.2-alt2.qa1 0.4.2-alt2.M60T.1 > *** binary package version is either the same or older than existing > patchage-debuginfo 0.4.2-alt2.qa1 0.4.2-alt2.M60T.1 > *** binary package version is either the same or older than existing > patchage-debuginfo 0.4.2-alt2.qa1 0.4.2-alt2.M60T.1 > 2012-Apr-16 16:06:27 :: version check FAILED > 2012-Apr-16 16:06:27 :: task #69737 for t6 FAILED Как быть в этой ситуации? Пробовал так: > 2012-Apr-16 15:59:02 :: patchage.git 0.4.2-alt2.qa2: release name alt2.qa2 does not contain *.M60T.* suffix Не заливать же 0.4.2-alt3.M60T.1, который будет больше версии в Сизифе (0.4.2-alt3). И почему сообщение "binary package version is either the same or older than existing" повторяется дважды? Это из-за проверки для двух архитектур? -- С уважением, инженер отдела ИИС ООО «Центр» Шакиров Ленар Наилевич shakirov@cg.ru (843) 533-88-14 Российская Федерация Казань, ул. Зинина, 3а 420029, а/я 81 http://www.cg.ru/
next parent reply other threads:[~2012-04-16 12:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-16 12:14 ` Lenar Shakirov [this message] 2012-04-17 11:06 ` Gleb Fotengauer-Malinovskiy 2012-04-17 13:07 ` Lenar Shakirov 2012-04-17 13:40 ` Gleb Fotengauer-Malinovskiy 2012-04-17 14:18 ` Lenar Shakirov
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=4F8C0D0F.7070207@cg.ru \ --to=shakirov@cg.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