From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: [rfh] where is coccinelle these days on Ubuntu?
Date: Sat, 06 Feb 2021 10:49:08 -0800 [thread overview]
Message-ID: <xmqqr1lt9gm3.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YBylBKMG4G4dbiOW@nand.local> (Taylor Blau's message of "Thu, 4 Feb 2021 20:53:08 -0500")
Taylor Blau <me@ttaylorr.com> writes:
> From a quick search, it looks like coccinelle was moved to the
> "universe" repository, at least in the Azure mirrors (which is what
> GitHub Actions uses):
>
> http://azure.archive.ubuntu.com/ubuntu/pool/universe/c/coccinelle/
Unfortunately the pool/ system does not tell us which suite a
package is available in (that's the whole point of it, as it lets
them share the packages across suites without moving things around).
Looking for the package availability
https://packages.ubuntu.com/search?keywords=coccinelle
seems to tell me about these:
xenial (16.04LTS) (devel): semantic patching tool for C [universe]
1.0.4.deb-2: amd64 arm64 armhf i386 powerpc ppc64el s390x
bionic (18.04LTS) (devel): semantic patching tool for C [universe]
1.0.4.deb-3build4: amd64 arm64 armhf i386 ppc64el s390x
groovy (20.10) (devel): semantic patching tool for C [universe]
1.0.8.deb-4: amd64 arm64 armhf ppc64el s390x
hirsute (devel): semantic patching tool for C [universe]
1.0.8.deb-5build1: amd64 arm64 armhf ppc64el s390x
but it does not seem to produce hits in any of the [focal],
[focal-updates], and [focal-backports] suites, which the actions
thing seem to be using X-<.
Hmph...
next prev parent reply other threads:[~2021-02-06 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 1:34 [rfh] where is coccinelle these days on Ubuntu? Junio C Hamano
2021-02-05 1:53 ` Taylor Blau
2021-02-06 18:49 ` Junio C Hamano [this message]
2021-02-08 21:22 ` Taylor Blau
2021-02-10 0:12 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr1lt9gm3.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).