How to differentiate between repo and built packages with dnf?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
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
edited Jul 19 at 19:44
slm♦
232k65479649
asked Jul 19 at 19:34
MyWrathAcademia
1369
add a comment |Â
up vote
1
down vote
favorite
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
edited Jul 19 at 19:44
slm♦
232k65479649
asked Jul 19 at 19:34
MyWrathAcademia
1369
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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
edited Jul 19 at 19:44
slm♦
232k65479649
asked Jul 19 at 19:34
MyWrathAcademia
1369
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
edited Jul 19 at 19:44
slm♦
232k65479649
asked Jul 19 at 19:34
MyWrathAcademia
1369
edited Jul 19 at 19:44
slm♦
232k65479649
edited Jul 19 at 19:44
slm♦
232k65479649
edited Jul 19 at 19:44
slm♦
232k65479649
232k65479649
asked Jul 19 at 19:34
MyWrathAcademia
1369
asked Jul 19 at 19:34
MyWrathAcademia
1369
asked Jul 19 at 19:34
MyWrathAcademia
1369
1369
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
Look at the lines Repo and From repo in the dnf info output. These will tell you:
Repotells you the repository that an available package is in. If the package is installed then it will tell you@System.From repoappears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g.fedoraorupdates) or@commandlinefor 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.
answered Jul 19 at 19:40
Michael Hampton
5,15311535
Ahh I see now, but how would I differentiate packages when usingdnf 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 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 at 19:50
@MyWrathAcademia And in any case, if you're rebuilding source RPMs and not usingmockthen you're doing it wrong.
– Michael Hampton
Jul 19 at 20:00
I don't get@commandlinefor a package I installed usingrpm -ivh. However, the rest is correct. I am usingfpm, what canmockdo that makes it necessary when building source RPM's?
– MyWrathAcademia
Jul 21 at 19:08
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Look at the lines Repo and From repo in the dnf info output. These will tell you:
Repotells you the repository that an available package is in. If the package is installed then it will tell you@System.From repoappears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g.fedoraorupdates) or@commandlinefor 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.
answered Jul 19 at 19:40
Michael Hampton
5,15311535
Ahh I see now, but how would I differentiate packages when usingdnf 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 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 at 19:50
@MyWrathAcademia And in any case, if you're rebuilding source RPMs and not usingmockthen you're doing it wrong.
– Michael Hampton
Jul 19 at 20:00
I don't get@commandlinefor a package I installed usingrpm -ivh. However, the rest is correct. I am usingfpm, what canmockdo that makes it necessary when building source RPM's?
– MyWrathAcademia
Jul 21 at 19:08
add a comment |Â
up vote
2
down vote
Look at the lines Repo and From repo in the dnf info output. These will tell you:
Repotells you the repository that an available package is in. If the package is installed then it will tell you@System.From repoappears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g.fedoraorupdates) or@commandlinefor 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.
answered Jul 19 at 19:40
Michael Hampton
5,15311535
Ahh I see now, but how would I differentiate packages when usingdnf 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 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 at 19:50
@MyWrathAcademia And in any case, if you're rebuilding source RPMs and not usingmockthen you're doing it wrong.
– Michael Hampton
Jul 19 at 20:00
I don't get@commandlinefor a package I installed usingrpm -ivh. However, the rest is correct. I am usingfpm, what canmockdo that makes it necessary when building source RPM's?
– MyWrathAcademia
Jul 21 at 19:08
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Look at the lines Repo and From repo in the dnf info output. These will tell you:
Repotells you the repository that an available package is in. If the package is installed then it will tell you@System.From repoappears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g.fedoraorupdates) or@commandlinefor 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.
answered Jul 19 at 19:40
Michael Hampton
5,15311535
Look at the lines Repo and From repo in the dnf info output. These will tell you:
Repotells you the repository that an available package is in. If the package is installed then it will tell you@System.From repoappears only for installed packages. It gives the repository from which an installed package originated. It shows a repo name (e.g.fedoraorupdates) or@commandlinefor 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.
answered Jul 19 at 19:40
Michael Hampton
5,15311535
edited Jul 19 at 19:58
answered Jul 19 at 19:40
Michael Hampton
5,15311535
answered Jul 19 at 19:40
Michael Hampton
5,15311535
answered Jul 19 at 19:40
Michael Hampton
5,15311535
5,15311535
Ahh I see now, but how would I differentiate packages when usingdnf 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 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 at 19:50
@MyWrathAcademia And in any case, if you're rebuilding source RPMs and not usingmockthen you're doing it wrong.
– Michael Hampton
Jul 19 at 20:00
I don't get@commandlinefor a package I installed usingrpm -ivh. However, the rest is correct. I am usingfpm, what canmockdo that makes it necessary when building source RPM's?
– MyWrathAcademia
Jul 21 at 19:08
add a comment |Â
Ahh I see now, but how would I differentiate packages when usingdnf 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 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 at 19:50
@MyWrathAcademia And in any case, if you're rebuilding source RPMs and not usingmockthen you're doing it wrong.
– Michael Hampton
Jul 19 at 20:00
I don't get@commandlinefor a package I installed usingrpm -ivh. However, the rest is correct. I am usingfpm, what canmockdo that makes it necessary when building source RPM's?
– MyWrathAcademia
Jul 21 at 19:08
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 at 19:43
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 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 at 19:50
@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 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 at 20:00
@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 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 at 19:08
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 at 19:08
add a comment |Â
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
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
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
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
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
