Mdthbs

Is leaving out prefixes like "rauf", "rüber", "rein" when describing movement considered a big mistake in spoken German?

Is it theoretically possible to hack printer using scanner tray?

What are the children of two Muggle-borns called?

Why do movie directors use brown tint on Mexico cities?

Chandra exiles a card, I play it, it gets exiled again

Why did the Apple IIe make a hideous noise if you inserted the disk upside down?

Two palindromes are not enough

Cat files in subfolders in order given by a list

Is it advisable to inform the CEO about his brother accessing his office?

A quine of sorts

Where to connect the fuse and why?

What verb goes with "coup"?

What could a Medieval society do with excess animal blood?

What was the first science fiction or fantasy multiple choice book?

Converse of pumping lemma for regular expressions

Could you fall off a planet if it was being accelerated by engines?

Why should I allow multiple IP addresses on a website for a single session?

Is this house-rule removing the increased effect of cantrips at higher character levels balanced?

Which coach station is easily accessible from Heathrow Airport?

Why are symbols not written in words?

LaTeX Make Word Appear

Why is my 401k manager recommending me to save more?

Rear derailleur got caught in the spokes, what could be a root cause

Why am I getting an electric shock from the water in my hot tub?

How to differentiate between repo and built packages with dnf?

Understanding the meaning of @ in package managementAny way to register source-built software with rpm/yum database?looking for a way to download a list of packages with yumHow can I install 32-bit dependencies on a 64-bit machine using dnf builddep?How to query which RPM package provides a specific versionHow to engage with Fedora 23 error message in dnf install error of dnspython?Reinstalling only packages with missing or corrupt files on a non-running system?Why doesn't rpm or dnf recognize default perl?Fedora: How do I force all installed packages to a single release version?Dependency tracking and unresolved dependenciesdnf not working properly on non fedora machine

1

When I build an rpm package with the same name as a package that already exists in a repo and type the command

$ dnf info package

This command only shows information about the built package. I would like to be able to run above command and dnf builddep package, and be able to choose which package I get information from.

Is there a way to differentiate between repo and self built packages without giving them different names?

Addendum: Built packages have newer versions

fedora package-management rpm dnf

share|improve this question

edited Jul 19 '18 at 19:44

slm♦

262k7272 gold badges566566 silver badges714714 bronze badges

asked Jul 19 '18 at 19:34

MyWrathAcademiaMyWrathAcademia

16111 silver badge1111 bronze badges

add a comment | 

1

When I build an rpm package with the same name as a package that already exists in a repo and type the command

$ dnf info package

This command only shows information about the built package. I would like to be able to run above command and dnf builddep package, and be able to choose which package I get information from.

Is there a way to differentiate between repo and self built packages without giving them different names?

Addendum: Built packages have newer versions

fedora package-management rpm dnf

share|improve this question

edited Jul 19 '18 at 19:44

slm♦

262k7272 gold badges566566 silver badges714714 bronze badges

asked Jul 19 '18 at 19:34

MyWrathAcademiaMyWrathAcademia

16111 silver badge1111 bronze badges

add a comment | 

When I build an rpm package with the same name as a package that already exists in a repo and type the command

$ dnf info package

This command only shows information about the built package. I would like to be able to run above command and dnf builddep package, and be able to choose which package I get information from.

Is there a way to differentiate between repo and self built packages without giving them different names?

Addendum: Built packages have newer versions

fedora package-management rpm dnf

share|improve this question

edited Jul 19 '18 at 19:44

slm♦

262k7272 gold badges566566 silver badges714714 bronze badges

asked Jul 19 '18 at 19:34

MyWrathAcademiaMyWrathAcademia

16111 silver badge1111 bronze badges

$ dnf info package

share|improve this question

edited Jul 19 '18 at 19:44

slm♦

262k7272 gold badges566566 silver badges714714 bronze badges

asked Jul 19 '18 at 19:34

MyWrathAcademiaMyWrathAcademia

16111 silver badge1111 bronze badges

share|improve this question

edited Jul 19 '18 at 19:44

slm♦

262k7272 gold badges566566 silver badges714714 bronze badges

asked Jul 19 '18 at 19:34

MyWrathAcademiaMyWrathAcademia

16111 silver badge1111 bronze badges

edited Jul 19 '18 at 19:44

slm♦

262k7272 gold badges566566 silver badges714714 bronze badges

edited Jul 19 '18 at 19:44

slm♦

262k7272 gold badges566566 silver badges714714 bronze badges

asked Jul 19 '18 at 19:34

MyWrathAcademiaMyWrathAcademia

16111 silver badge1111 bronze badges

asked Jul 19 '18 at 19:34

MyWrathAcademiaMyWrathAcademia

16111 silver badge1111 bronze badges

2 Answers
2

active

oldest

votes

2

Look at the lines Repo and From repo in the dnf info output. These will tell you:

• 
  Repo tells you the repository that an available package is in. If the package is installed then it will tell you @System.


• 
  From repo appears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g. fedora or updates) or @commandline for a manually installed RPM.

dnf builddep will install build dependencies for the latest version of the named package in the repositories. It doesn't do anything with manually installed RPMs.

share|improve this answer

edited Jul 19 '18 at 19:58

answered Jul 19 '18 at 19:40

Michael HamptonMichael Hampton

6,29111 gold badge2121 silver badges4949 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ahh I see now, but how would I differentiate packages when using dnf builddep package? If I have two packages with the same name, will it not just return results for one of them only?
  
  – MyWrathAcademia
  Jul 19 '18 at 19:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MyWrathAcademia If you've got two packages with the same name, they should be the same software (even if different versions).
  
  – Michael Hampton
  Jul 19 '18 at 19:50
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MyWrathAcademia And in any case, if you're rebuilding source RPMs and not using mock then you're doing it wrong.
  
  – Michael Hampton
  Jul 19 '18 at 20:00
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't get @commandline for a package I installed using rpm -ivh. However, the rest is correct. I am using fpm, what can mock do that makes it necessary when building source RPM's?
  
  – MyWrathAcademia
  Jul 21 '18 at 19:08
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you're installing deps in order to build a package, the spec file should be the source of the deps anyway. dnf builddep package.spec — problem solved, no ambiguity. (Otherwise, it'll select a package to pull the deps from the same way it selects a package to install. You can have two packages with the same name in two different repos, as well. Of course, if two packages have the same name and version identifiers, why wouldn't they have the same build deps?
  
  – FeRD
  1 hour ago
  

  
  
  
  

 | 
show 1 more comment

0

If you want to use dnf builddep to install the deps of a specific package, simply be more specific. In other words, you can do all of the following:

$ sudo dnf builddep somepackage-1.2.3

$ sudo dnf builddep somepackage-1.2.3-9.fc30

$ sudo dnf builddep /path/to/some/uninstalled/somepackage-1.2.4-1.fc30.$arch.rpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage-1.2.4-2.fc30.srpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage.spec

Ditto with dnf info, for the first two. (You can't run dnf info on a file path to an RPM, SRPM, or spec, somewhat surprisingly. You can do rpm -q -i -p /path/to/uninstalled.{rpm,srpm} — just have to remember to include the -p flag — but there's nothing similar with dnf info.)

The only time you can't be completely specific about a package's source is when there are packages in two different repos, which have literally the exact same NVR.

Like, say I dnf download --source'd an SRPM for a package in the Fedora updates repo, built local RPMs with rpmbuild -rb, then added them to the local repo I maintain for my own packages. By default, that'll be somepackage-1.2.5-1.fc30.x86_64.rpm or whatever, exactly the same as the one in the updates repo.

Because of that ambiguity, my $HOME/.rpmmacros contains the following:

%dist           .ferd%{fedora}

That ensures the version I build locally comes out as somepackage-1.2.5-1.ferd30.x86_64.rpm, instead of .fc30, so I can differentiate.

share|improve this answer

answered 55 mins ago

FeRDFeRD

42633 silver badges1111 bronze badges

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f457286%2fhow-to-differentiate-between-repo-and-built-packages-with-dnf%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

Look at the lines Repo and From repo in the dnf info output. These will tell you:

• 
  Repo tells you the repository that an available package is in. If the package is installed then it will tell you @System.


• 
  From repo appears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g. fedora or updates) or @commandline for a manually installed RPM.

dnf builddep will install build dependencies for the latest version of the named package in the repositories. It doesn't do anything with manually installed RPMs.

share|improve this answer

edited Jul 19 '18 at 19:58

answered Jul 19 '18 at 19:40

Michael HamptonMichael Hampton

6,29111 gold badge2121 silver badges4949 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ahh I see now, but how would I differentiate packages when using dnf builddep package? If I have two packages with the same name, will it not just return results for one of them only?
  
  – MyWrathAcademia
  Jul 19 '18 at 19:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MyWrathAcademia If you've got two packages with the same name, they should be the same software (even if different versions).
  
  – Michael Hampton
  Jul 19 '18 at 19:50
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MyWrathAcademia And in any case, if you're rebuilding source RPMs and not using mock then you're doing it wrong.
  
  – Michael Hampton
  Jul 19 '18 at 20:00
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't get @commandline for a package I installed using rpm -ivh. However, the rest is correct. I am using fpm, what can mock do that makes it necessary when building source RPM's?
  
  – MyWrathAcademia
  Jul 21 '18 at 19:08
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you're installing deps in order to build a package, the spec file should be the source of the deps anyway. dnf builddep package.spec — problem solved, no ambiguity. (Otherwise, it'll select a package to pull the deps from the same way it selects a package to install. You can have two packages with the same name in two different repos, as well. Of course, if two packages have the same name and version identifiers, why wouldn't they have the same build deps?
  
  – FeRD
  1 hour ago
  

  
  
  
  

 | 
show 1 more comment

2

Look at the lines Repo and From repo in the dnf info output. These will tell you:

• 
  Repo tells you the repository that an available package is in. If the package is installed then it will tell you @System.


• 
  From repo appears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g. fedora or updates) or @commandline for a manually installed RPM.

dnf builddep will install build dependencies for the latest version of the named package in the repositories. It doesn't do anything with manually installed RPMs.

share|improve this answer

edited Jul 19 '18 at 19:58

answered Jul 19 '18 at 19:40

Michael HamptonMichael Hampton

6,29111 gold badge2121 silver badges4949 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ahh I see now, but how would I differentiate packages when using dnf builddep package? If I have two packages with the same name, will it not just return results for one of them only?
  
  – MyWrathAcademia
  Jul 19 '18 at 19:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MyWrathAcademia If you've got two packages with the same name, they should be the same software (even if different versions).
  
  – Michael Hampton
  Jul 19 '18 at 19:50
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MyWrathAcademia And in any case, if you're rebuilding source RPMs and not using mock then you're doing it wrong.
  
  – Michael Hampton
  Jul 19 '18 at 20:00
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't get @commandline for a package I installed using rpm -ivh. However, the rest is correct. I am using fpm, what can mock do that makes it necessary when building source RPM's?
  
  – MyWrathAcademia
  Jul 21 '18 at 19:08
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you're installing deps in order to build a package, the spec file should be the source of the deps anyway. dnf builddep package.spec — problem solved, no ambiguity. (Otherwise, it'll select a package to pull the deps from the same way it selects a package to install. You can have two packages with the same name in two different repos, as well. Of course, if two packages have the same name and version identifiers, why wouldn't they have the same build deps?
  
  – FeRD
  1 hour ago
  

  
  
  
  

 | 
show 1 more comment

Look at the lines Repo and From repo in the dnf info output. These will tell you:

• 
  Repo tells you the repository that an available package is in. If the package is installed then it will tell you @System.


• 
  From repo appears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g. fedora or updates) or @commandline for a manually installed RPM.

dnf builddep will install build dependencies for the latest version of the named package in the repositories. It doesn't do anything with manually installed RPMs.

share|improve this answer

edited Jul 19 '18 at 19:58

answered Jul 19 '18 at 19:40

Michael HamptonMichael Hampton

6,29111 gold badge2121 silver badges4949 bronze badges

share|improve this answer

edited Jul 19 '18 at 19:58

answered Jul 19 '18 at 19:40

Michael HamptonMichael Hampton

6,29111 gold badge2121 silver badges4949 bronze badges

answered Jul 19 '18 at 19:40

Michael HamptonMichael Hampton

6,29111 gold badge2121 silver badges4949 bronze badges

answered Jul 19 '18 at 19:40

Michael HamptonMichael Hampton

6,29111 gold badge2121 silver badges4949 bronze badges

0

If you want to use dnf builddep to install the deps of a specific package, simply be more specific. In other words, you can do all of the following:

$ sudo dnf builddep somepackage-1.2.3

$ sudo dnf builddep somepackage-1.2.3-9.fc30

$ sudo dnf builddep /path/to/some/uninstalled/somepackage-1.2.4-1.fc30.$arch.rpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage-1.2.4-2.fc30.srpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage.spec

Ditto with dnf info, for the first two. (You can't run dnf info on a file path to an RPM, SRPM, or spec, somewhat surprisingly. You can do rpm -q -i -p /path/to/uninstalled.{rpm,srpm} — just have to remember to include the -p flag — but there's nothing similar with dnf info.)

The only time you can't be completely specific about a package's source is when there are packages in two different repos, which have literally the exact same NVR.

Like, say I dnf download --source'd an SRPM for a package in the Fedora updates repo, built local RPMs with rpmbuild -rb, then added them to the local repo I maintain for my own packages. By default, that'll be somepackage-1.2.5-1.fc30.x86_64.rpm or whatever, exactly the same as the one in the updates repo.

Because of that ambiguity, my $HOME/.rpmmacros contains the following:

%dist           .ferd%{fedora}

That ensures the version I build locally comes out as somepackage-1.2.5-1.ferd30.x86_64.rpm, instead of .fc30, so I can differentiate.

share|improve this answer

answered 55 mins ago

FeRDFeRD

42633 silver badges1111 bronze badges

add a comment | 

0

If you want to use dnf builddep to install the deps of a specific package, simply be more specific. In other words, you can do all of the following:

$ sudo dnf builddep somepackage-1.2.3

$ sudo dnf builddep somepackage-1.2.3-9.fc30

$ sudo dnf builddep /path/to/some/uninstalled/somepackage-1.2.4-1.fc30.$arch.rpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage-1.2.4-2.fc30.srpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage.spec

Ditto with dnf info, for the first two. (You can't run dnf info on a file path to an RPM, SRPM, or spec, somewhat surprisingly. You can do rpm -q -i -p /path/to/uninstalled.{rpm,srpm} — just have to remember to include the -p flag — but there's nothing similar with dnf info.)

The only time you can't be completely specific about a package's source is when there are packages in two different repos, which have literally the exact same NVR.

Like, say I dnf download --source'd an SRPM for a package in the Fedora updates repo, built local RPMs with rpmbuild -rb, then added them to the local repo I maintain for my own packages. By default, that'll be somepackage-1.2.5-1.fc30.x86_64.rpm or whatever, exactly the same as the one in the updates repo.

Because of that ambiguity, my $HOME/.rpmmacros contains the following:

%dist           .ferd%{fedora}

That ensures the version I build locally comes out as somepackage-1.2.5-1.ferd30.x86_64.rpm, instead of .fc30, so I can differentiate.

share|improve this answer

answered 55 mins ago

FeRDFeRD

42633 silver badges1111 bronze badges

add a comment | 

If you want to use dnf builddep to install the deps of a specific package, simply be more specific. In other words, you can do all of the following:

$ sudo dnf builddep somepackage-1.2.3

$ sudo dnf builddep somepackage-1.2.3-9.fc30

$ sudo dnf builddep /path/to/some/uninstalled/somepackage-1.2.4-1.fc30.$arch.rpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage-1.2.4-2.fc30.srpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage.spec

Ditto with dnf info, for the first two. (You can't run dnf info on a file path to an RPM, SRPM, or spec, somewhat surprisingly. You can do rpm -q -i -p /path/to/uninstalled.{rpm,srpm} — just have to remember to include the -p flag — but there's nothing similar with dnf info.)

The only time you can't be completely specific about a package's source is when there are packages in two different repos, which have literally the exact same NVR.

Like, say I dnf download --source'd an SRPM for a package in the Fedora updates repo, built local RPMs with rpmbuild -rb, then added them to the local repo I maintain for my own packages. By default, that'll be somepackage-1.2.5-1.fc30.x86_64.rpm or whatever, exactly the same as the one in the updates repo.

Because of that ambiguity, my $HOME/.rpmmacros contains the following:

%dist           .ferd%{fedora}

That ensures the version I build locally comes out as somepackage-1.2.5-1.ferd30.x86_64.rpm, instead of .fc30, so I can differentiate.

share|improve this answer

answered 55 mins ago

FeRDFeRD

42633 silver badges1111 bronze badges

$ sudo dnf builddep somepackage-1.2.3

$ sudo dnf builddep somepackage-1.2.3-9.fc30

$ sudo dnf builddep /path/to/some/uninstalled/somepackage-1.2.4-1.fc30.$arch.rpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage-1.2.4-2.fc30.srpm

$ sudo dnf builddep /path/to/some/unbuilt/somepackage.spec

%dist           .ferd%{fedora}

share|improve this answer

answered 55 mins ago

FeRDFeRD

42633 silver badges1111 bronze badges

answered 55 mins ago

FeRDFeRD

42633 silver badges1111 bronze badges

answered 55 mins ago

FeRDFeRD

42633 silver badges1111 bronze badges