feature: git-ubuntu find

Bug #1731517 reported by Dmitrii Shcherbakov on 2017-11-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usd-importer
Wishlist
Unassigned

Bug Description

At times it is useful to find if a repository is present in usd-import-team project by a substring or regex.

git-ubuntu find udev

git-ubuntu find '.*udev.*'

Not critical, but would definitely make life easier sometimes.

Nish Aravamudan (nacc) wrote :

Interesting idea. It's really a Launchpad query, not related directly to the git-ubuntu tooling. I mean, worst case, try to clone it and if it fails, then ... it's not there :)

At the same time, our plan is to ramp up to all source packages during this cycle and keep them all up to date, at least for main. At which point, I'm not sure we'd want this subcommand.

I'll mark it as wishlist and future for now. (right now, we're focused on the importer algorithm and being able to import all of main).

Changed in usd-importer:
milestone: none → future
importance: Undecided → Wishlist
Dmitrii Shcherbakov (dmitriis) wrote :

Sometimes a package name is different from source package name, hence when you do

dpkg -S <somefile>

it is not always clear which repo to look for.

Over time you learn them all but it's nice to grep instead of clicking through :^)

Thanks for that work - I use it quite often and really appreciate the effort. It became much easier to find relevant code to me.

Nish Aravamudan (nacc) wrote :

Ah! I misunderstood your request -- I thought you were asking for a CLI subcommand to check if something had been imported or not.

Instead, you are looking for (possibly) a binary -> source mapping, which is described in LP: #1707325.

Dmitrii Shcherbakov (dmitriis) wrote :

Thinking about it now, it may be even more useful this way.

If a binary -> source search fails, there's no such repo in usd-import-team so you have to go and find an upstream repo manually or pull a source archive.

The original request may still be valid as sometimes you don't do dpkg -S <filename> to determine a package name.

Good idea!

Robie Basak (racb) wrote :

What if, upon failure to find a particular source package on "git ubuntu clone", we did some heuristic guessing and if we get a hit, suggest in a "X is provided by source package Y\nDid you mean: git ubuntu clone Y?" type error message? The heuristics could include some combination of binary package namespace search, substring match, and "dpkg -S $(which ...)".

Could be useful too.

Sometimes you're just searching through so you may want to be explicit
right away.

On 13 Nov 2017 11:11, "Robie Basak" <email address hidden> wrote:

What if, upon failure to find a particular source package on "git ubuntu
clone", we did some heuristic guessing and if we get a hit, suggest in a
"X is provided by source package Y\nDid you mean: git ubuntu clone Y?"
type error message? The heuristics could include some combination of
binary package namespace search, substring match, and "dpkg -S $(which
...)".

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1731517

Title:
  feature: git-ubuntu find

Status in usd-importer:
  New

Bug description:
  At times it is useful to find if a repository is present in usd-
  import-team project by a substring or regex.

  git-ubuntu find udev

  git-ubuntu find '.*udev.*'

  Not critical, but would definitely make life easier sometimes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/usd-importer/+bug/1731517/+subscriptions

David Britton (davidpbritton) wrote :

For anyone else reading this... I realize this is a feature request in the future milestone on git-ubuntu to be able to grok either and perhaps search with a list option for more discovery...

but, bin2src from chdist is meant to solve this problem in general. You might be able to integrate that into your workflow right now to accomplish what you would like.

Just a suggestion.

Robie Basak (racb) on 2017-11-28
tags: added: clone
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers