i've pawed over the man page for dnf and i can't figure out how to do something simple -- i want to restrict the output of commands like "dnf search" or "dnf info" to just a selected set of architectures.
example:
$ dnf search ftp ftp.x86_64 : The standard UNIX FTP (File Transfer Protocol) client lftp-scripts.noarch : Scripts for lftp vsftpd.x86_64 : Very Secure Ftp Daemon ftplib.i686 : Library of FTP routines ftplib.x86_64 : Library of FTP routines ... snip ...
in the above, i'm not interested in seeing any i686 arch packages, but i can't figure out how to restrict that (if it's even possible). ideally, i'd like to restrict package arches for these queries to x86_64 or noarch, and "man dnf" suggests the "--arch" option, but that doesn't have the effect i'm after:
$ dnf search ftp --arch x86_64 usage: dnf search [-c [config file]] [-q] [-v] [--version] ... snip ... dnf search: error: unrecognized arguments: --arch x86_64 $
"man dnf" suggests you can do this with the "repoquery" command:
$ dnf repoquery --whatprovides webserver --arch i686
am i overlooking something obvious?
rday
On Thu, 8 Mar 2018 05:45:12 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
ideally, i'd like to restrict package arches for these queries to x86_64 or noarch, and "man dnf" suggests the "--arch" option, but that doesn't have the effect i'm after:
$ dnf search ftp --arch x86_64
dnf search ftp --forcearch x86_64
$ dnf repoquery --whatprovides webserver --arch i686
Don't know, yet.
BR, Bob
Den 2018-03-08 kl. 11:45, skrev Robert P. J. Day:
i've pawed over the man page for dnf and i can't figure out how to do something simple -- i want to restrict the output of commands like "dnf search" or "dnf info" to just a selected set of architectures.
example:
$ dnf search ftp ftp.x86_64 : The standard UNIX FTP (File Transfer Protocol) client lftp-scripts.noarch : Scripts for lftp vsftpd.x86_64 : Very Secure Ftp Daemon ftplib.i686 : Library of FTP routines ftplib.x86_64 : Library of FTP routines ... snip ...
in the above, i'm not interested in seeing any i686 arch packages, but i can't figure out how to restrict that (if it's even possible). ideally, i'd like to restrict package arches for these queries to x86_64 or noarch, and "man dnf" suggests the "--arch" option, but that doesn't have the effect i'm after:
$ dnf search ftp --arch x86_64 usage: dnf search [-c [config file]] [-q] [-v] [--version] ... snip ... dnf search: error: unrecognized arguments: --arch x86_64 $
"man dnf" suggests you can do this with the "repoquery" command:
$ dnf repoquery --whatprovides webserver --arch i686
From the man page I read that "--arch" is option only used by the "repoquery" command. See the man page section "Repoquery Command"
am i overlooking something obvious?
rday _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Thu, 8 Mar 2018, Bob Marcan wrote:
On Thu, 8 Mar 2018 05:45:12 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
ideally, i'd like to restrict package arches for these queries to x86_64 or noarch, and "man dnf" suggests the "--arch" option, but that doesn't have the effect i'm after:
$ dnf search ftp --arch x86_64
dnf search ftp --forcearch x86_64
nope, already tried that:
ftp.x86_64 : The standard UNIX FTP (File Transfer Protocol) client lftp-scripts.noarch : Scripts for lftp vsftpd.x86_64 : Very Secure Ftp Daemon ftplib.i686 : Library of FTP routines <---------- ... snip ..
rday
On Thu, 8 Mar 2018 06:51:15 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
dnf search ftp --forcearch x86_64
I was a little too fast :-) dnf search ftp | grep x86_64 will do. Obviously dnf is not mature enough, yet.
BR, Bob
On 03/08/18 18:45, Robert P. J. Day wrote:
i've pawed over the man page for dnf and i can't figure out how to do something simple -- i want to restrict the output of commands like "dnf search" or "dnf info" to just a selected set of architectures.
Sure.
I'll give you a hint. Just "exclude" the architecture of the packages you don't want. You'll have to use a "glob" to do it.
Of course, if you give up, I'll tell you what you need to know. But, sometimes it is better to try a bit more and learn a bit along the way.
On Thu, 8 Mar 2018, Ed Greshko wrote:
On 03/08/18 18:45, Robert P. J. Day wrote:
i've pawed over the man page for dnf and i can't figure out how to do something simple -- i want to restrict the output of commands like "dnf search" or "dnf info" to just a selected set of architectures.
Sure.
I'll give you a hint. Just "exclude" the architecture of the packages you don't want. You'll have to use a "glob" to do it.
Of course, if you give up, I'll tell you what you need to know. But, sometimes it is better to try a bit more and learn a bit along the way.
ed: your frequently condescending replies to me wherein you lecture to me as if i'm a 12-year-old is getting a little tiring. i am well aware of dnf's "--exclude" option, but that option simply allows (if i read this correctly) globbing on the entire package name, architecture and everything else in between.
given that dnf recognizes both "--arch" and "--forcearch" for some operations, i was hoping the same *architecture-specific* selection could be applied to queries.
rday
On 03/08/18 20:42, Robert P. J. Day wrote:
On Thu, 8 Mar 2018, Ed Greshko wrote:
On 03/08/18 18:45, Robert P. J. Day wrote:
i've pawed over the man page for dnf and i can't figure out how to do something simple -- i want to restrict the output of commands like "dnf search" or "dnf info" to just a selected set of architectures.
Sure.
I'll give you a hint. Just "exclude" the architecture of the packages you don't want. You'll have to use a "glob" to do it.
Of course, if you give up, I'll tell you what you need to know. But, sometimes it is better to try a bit more and learn a bit along the way.
ed: your frequently condescending replies to me wherein you lecture to me as if i'm a 12-year-old is getting a little tiring. i am well aware of dnf's "--exclude" option, but that option simply allows (if i read this correctly) globbing on the entire package name, architecture and everything else in between.
[egreshko@meimei ~]$ dnf --excludepkgs=*686 info 389-admin Last metadata expiration check: 6:18:25 ago on Thu 08 Mar 2018 03:05:51 PM CST. Available Packages Name : 389-admin Version : 1.1.46 Release : 1.fc27.3 Arch : x86_64 Size : 408 k Source : 389-admin-1.1.46-1.fc27.3.src.rpm Repo : fedora Summary : 389 Administration Server (admin) URL : http://www.port389.org/ License : GPLv2 and ASL 2.0 Description : 389 Administration Server is an HTTP agent that provides management : features for 389 Directory Server. It provides some management web : apps that can be used through a web browser. It provides the : authentication, access control, and CGI utilities used by the : console.
V.S.
[egreshko@meimei ~]$ dnf info 389-admin Last metadata expiration check: 6:19:02 ago on Thu 08 Mar 2018 03:05:51 PM CST. Available Packages Name : 389-admin Version : 1.1.46 Release : 1.fc27.3 Arch : i686 Size : 408 k Source : 389-admin-1.1.46-1.fc27.3.src.rpm Repo : fedora Summary : 389 Administration Server (admin) URL : http://www.port389.org/ License : GPLv2 and ASL 2.0 Description : 389 Administration Server is an HTTP agent that provides management : features for 389 Directory Server. It provides some management web : apps that can be used through a web browser. It provides the : authentication, access control, and CGI utilities used by the : console.
Name : 389-admin Version : 1.1.46 Release : 1.fc27.3 Arch : x86_64 Size : 408 k Source : 389-admin-1.1.46-1.fc27.3.src.rpm Repo : fedora Summary : 389 Administration Server (admin) URL : http://www.port389.org/ License : GPLv2 and ASL 2.0 Description : 389 Administration Server is an HTTP agent that provides management : features for 389 Directory Server. It provides some management web : apps that can be used through a web browser. It provides the : authentication, access control, and CGI utilities used by the : console.
Maybe the man page was too long?
given that dnf recognizes both "--arch" and "--forcearch" for some operations, i was hoping the same *architecture-specific* selection could be applied to queries.
That isn't what you want...
On Thu, 8 Mar 2018 21:26:48 +0800 Ed Greshko ed.greshko@greshko.com wrote:
[egreshko@meimei ~]$ dnf --excludepkgs=*686 info 389-admin
Thanks for that: that seems helpful, too, when dnf suggests packages different from the actual machine architecture: I was trying to install a package from the testing repo, and it suggested with the --exclude flag this (architecture here is x86_64):
# dnf --exclude=*686 --allowerasing --best install usbguard --enablerepo=updates-testing Last metadata expiration check: 0:33:21 ago on Thu 08 Mar 2018 02:42:09 PM CET. Package usbguard-0.7.0-3.fc26.x86_64 is already installed, skipping. Dependencies resolved. ======================================================= Package Arch Version Repository Size ======================================================= Upgrading: usbguard x86_64 0.7.2-2.fc26 updates-testing 414 k usbguard-applet-qt x86_64 0.7.2-2.fc26 updates-testing 74 k
Transaction Summary ======================================================= Upgrade 2 Packages
Total download size: 488 k Is this ok [y/N]: Operation aborted.
########################
now without the "--exclude" switch:
dnf --allowerasing --best install usbguard --enablerepo=updates-testing Last metadata expiration check: 0:36:06 ago on Thu 08 Mar 2018 02:42:09 PM CET. Package usbguard-0.7.0-3.fc26.x86_64 is already installed, skipping. Dependencies resolved. =================================================== Package Arch Version Repository Size =================================================== Upgrading: usbguard x86_64 0.7.2-2.fc26 updates-testing 414 k Installing dependencies: glibc i686 2.25-13.fc26 updates 4.1 M libgcc i686 7.3.1-2.fc26 updates 103 k libgcrypt i686 1.8.2-1.fc26 updates 430 k libgpg-error i686 1.25-2.fc26 fedora 163 k libqb i686 1.0.2-1.fc26 fedora 110 k libstdc++ i686 7.3.1-2.fc26 updates 503 k nss-softokn-freebl i686 3.35.0-1.0.fc26 updates 232 k protobuf i686 3.2.0-4.fc26 updates 818 k usbguard i686 0.7.0-3.fc26 updates 428 k zlib i686 1.2.11-2.fc26 fedora 101 k Installing weak dependencies: libcrypt-nss i686 2.25-13.fc26 updates 55 k
Transaction Summary ===================================================== Install 11 Packages Upgrade 1 Package
Total download size: 7.3 M Is this ok [y/N]:
---------------------------------
Tho' I'm not sure whether all this a feature or a bug ... ;)
Regards - thanks again!
On Thu, 8 Mar 2018, Ed Greshko wrote:
On 03/08/18 20:42, Robert P. J. Day wrote:
On Thu, 8 Mar 2018, Ed Greshko wrote:
On 03/08/18 18:45, Robert P. J. Day wrote:
i've pawed over the man page for dnf and i can't figure out how to do something simple -- i want to restrict the output of commands like "dnf search" or "dnf info" to just a selected set of architectures.
Sure.
I'll give you a hint. Just "exclude" the architecture of the packages you don't want. You'll have to use a "glob" to do it.
Of course, if you give up, I'll tell you what you need to know. But, sometimes it is better to try a bit more and learn a bit along the way.
ed: your frequently condescending replies to me wherein you lecture to me as if i'm a 12-year-old is getting a little tiring. i am well aware of dnf's "--exclude" option, but that option simply allows (if i read this correctly) globbing on the entire package name, architecture and everything else in between.
[egreshko@meimei ~]$ dnf --excludepkgs=*686 info 389-admin
curiously, while "dnf --help" mentions that option, it does not appear anywhere in the man page:
$ man dnf | grep excludepkgs $
Maybe the man page was too long?
yes, that must be it ... if only i'd kept on reading.
rday
On 03/08/18 22:44, Robert P. J. Day wrote:
curiously, while "dnf --help" mentions that option, it does not appear anywhere in the man page:
$ man dnf | grep excludepkgs $
In reality excludepkgs is the same as exclude. Probably "exclude" is preferred, I just happen to remember it the other way.
Maybe the man page was too long?
yes, that must be it ... if only i'd kept on reading.
No matter. You have your answer now, yes?
If so, you're welcome.