Re: install custom rpm package: failed dependencies
On 10/08/2015 12:39 PM, arnaud gaboury wrote: On Thu, Oct 8, 2015 at 9:12 PM, Reindl Harald <h.rei...@thelounge.net> wrote: Am 08.10.2015 um 21:06 schrieb arnaud gaboury: Downloading from Intel website the parallel studio 2016. There is a folder with all rpm packages and a script to install them. I understand this package is NOT part of Fedora, but neither part of RPM fusion. So I must not installed it? no, but it's not Fedora relevant Now regarding my own spec file, I am trying to write it correctly to help any other Fedora user to install what I want to install. Unfortunately, again, there is NO Fedora package. So please tell me if I am wromg when trying to write a clean spec file with the idea to share with Fedora users? Shall I keep everything for me when it can maybe help others? but it's not *FEDORA DVELOPMENT* in the context of something relevant for Fedora as a release distribution - and yes: your problem is just a *user related* thing with no context to the distribution itself, especially as you are playing around with a external compiler suite Ok then, I will find elsewhere any advice, users@list, stackoverflow or whaterver else, or just # rpm -i --no-deps. Please apologize for the noise when trying to understand how things work. You might try the Intel forums and support related to their Parallel Studio compiler product. If you bought the commercial product, you might try filing a support ticket for assistance. Intel should be motivated to help you, since this could promote the use of their product. This mail list is focussed on the the development OF Fedora, not development WITH Fedora. Simple mistake. Cheers, -Bob Arendt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: dnf versus yum
On 01/02/2014 04:36 PM, Richard Vickery wrote: On Thu, Jan 2, 2014 at 3:28 PM, yersinia yersinia.spi...@gmail.com mailto:yersinia.spi...@gmail.com wrote: 5 PM, poma pomidorabelis...@gmail.com mailto:pomidorabelis...@gmail.com wrote: On 02.01.2014 20:36, Steve Clark wrote: Also at least yum stood for something - Yellowdog Updater, Modified - as opposed to being some nonsensical conglomeration of letters. The only thing I am aware of that dnf means is did not finish. Did Not Finish Do Not Forget ..snip.. poma I do not think it is nice to speak so bad about a project. The objective are clear,if something can be improved everyone can or must contribute.The criticisms are useless.We are talking about open source software, do not forget. Best regards On the contrary: speaking negatively about a project may be fine so long as the context is clearly about such project, as it is only the project that is being harshly criticised. Where a problem often occurs is when such criticism crosses over into affecting an individual. From the fedoraproject.org wiki: Note about the name DNF: it has no relevant meaning, meant as a project name only It seems rather unfortunate that as a random collection of letters, DNF currently has primarily negative connotations: http://en.wikipedia.org/wiki/DNF http://www.urbandictionary.com/define.php?term=DNF https://www.google.com/#q=dnf As a runner, DNF already has a specific meaning for me. If you're picking random letters for a project to avoid existing collisions, you might also consider tossing the set back into the bag they have a well-established meaning in other domains. Just saying - it might do well to change the name to something with positive or at least neutral collateral meaning. yum probably had some positive benefits in this regard. Cheers, -Bob Arendt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: dnf versus yum
On 01/02/2014 06:52 PM, Chuck Anderson wrote: On Fri, Jan 03, 2014 at 02:40:33AM +0100, poma wrote: On 03.01.2014 02:31, Richard Vickery wrote: On Thu, Jan 2, 2014 at 5:28 PM, Chuck Anderson c...@wpi.edu wrote: On Fri, Jan 03, 2014 at 02:18:52AM +0100, poma wrote: On 03.01.2014 01:06, Bob Arendt wrote: As a runner, DNF already has a specific meaning for me. If you're picking random letters for a project to avoid existing collisions, you might also consider tossing the set back into the bag they have a well-established meaning in other domains. Just saying - it might do well to change the name to something with positive or at least neutral collateral meaning. yum probably had some positive benefits in this regard. Yum has sentimental value and is practically a trademark, so 1. yuma - Yellowdog Updater, Modified Again 2. yum2 - Yellowdog Updater, Modified II 3. yumrelo - Yellowdog Updater, Modified Reloaded 6. yum-ng - Yellowdog Updater, Modified NG (Next Generation) 5. yum-ak - Yellowdog Updater, Modified AK (Ales Kozumplik) 4. yum-novus - Yellowdog Updater, Modified New 7. yummy - Yellowdog Updater, Modified My How about: fu - Fedora Updater. fum - Fedora Updater, Modified. fu has a positive connotation: fu, a particle or suffix that can mean intensity [1]. Or, we can just forget about any connotation, like apparently we did when coming up with fedup. LOL - Is this supposed to be a play on words / accronyms? Haha, actually pretty cool! 0. yum-fu - Yellowdog Updater, Modified Fu (No need to explain) poma Or to be more generic about it: pu - Package Updater. pum - Package Updater, Modified. puma - Package Updater, Modified Again. poma - Package Opener (Operator?), Modified Again That last one is tounge-in-cheek :-J puma ! Similar to orig name (continuity), p for package (better than yellow-dog), and humorous extension a that turns it into a word with logo possibilities. And shouldn't have brand overlap with the shoes (they're going with the animal association anyway). You could get some some traction with that name. -Bob -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Install from ISO file supported
On 01/20/2013 02:22 PM, Sergio Belkin wrote: Hi Fedora community, AFAIK fedup only works with DVD iso files not with LiveCD iso files: I was reading the thread at http://lists.fedoraproject.org/pipermail/users/2013-January/429113.html something interesting about it ISO files are still useful, for example to test in a quicky way on a Virtual machine, but I don't know you, but I'm sick of burning CDs I think that the best and more confortable method to upgrade the OS should be: 1. Download a LiveCD Fedora.iso (it takes less time than download the DVD iso file) 2. Launch fedup --iso Fedora-LiveCD.iso, that make the job of adjusting GRUB2 i.a. 3. Reboot the system 3. Choose LiveCD entry from GRUB2) Perform the installation as you wish And forget about of burning optical discs Of course this does not cover all cases, for example, you should preserve the partition where ISO image file is. What do you think? Greetings -- -- Sergio Belkin http://www.sergiobelkin.com Watch More TV http://sebelk.blogspot.com LPIC-2 Certified - http://www.lpi.org I find it easier (and smaller) to download the netinst.iso (like Fedora-18-x86_64-netinst.iso) Loop-back mount and pull the vmlinuz and initrd.img into /boot, and create a grub or grub2 entry to start the install, adding additional options as desired (vnc display, kickstart file). Create a simple kickstart file and adding additional repo's (who doesn't use rpmfusion or some other add-on?) and mod the package list. Then do a network install. This has the advantage of only downloading the most recent packages, and only the set desired. Avoids the initial install, then update most of the packages syndrome that happens a few months after initial release. The netinst.iso also doubles as a rescue install, and you can put a couple images (e.g. 32 64 bit) on a single USB stick. I'm not locked into a Spin and whether or not the packages I'm interested in made it onto the DVD. I did several Xfce-only installs using this. And a Gnome/KDE/Xfce/icewm joint setup using this same install image. A small kickstart file provides recipe for what you want. I also avoid possible confusion and manually format and label the partitions before I install. This avoids mistakes with anaconda over-writing partitions you don't want disturbed. It's better to have have anaconda fail to find your named partition (early) than to the have device ordering slip and wipe something you wanted to keep. Cheers, -Bob Arendt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why EDID is not trustworthy for DPI
On 10/05/11 12:31, Adam Williamson wrote: Like I replied to ajax, I suspect when the problem of assuming everything's 96dpi becomes simply too acute, instead of fixing everything really properly so that all displays correct report their size and all desktops actually do resolution independence perfectly so it doesn't_matter_ if one of your displays is 98dpi and the other is 215dpi, everything still looks perfect, the industry will just wind up with a slightly more sophisticated bodge where we have a few 'standard' resolutions and just figure out which one your displays are closest to. But that's still going to require some kind of sensible handling of the case where one monitor is roughly 100dpi and the other is roughly 200dpi, unless we simply say 'you can't do that, all your displays have to be in the same DPI Category'. Good point Adam. Even if the Xserver correctly intuits the resolution of each display, application behavior is going to be unacceptable. Consider dragging a window from a 200 dpi display to a 100 dpi display. Does the application detect this and correctly re-scale it's window and interior widgets? If the Xserver re-scales the font, how does the app detect the change in bounding box pixel geometry? How's the app supposed to behave if the window straddles monitors? Unless all the graphic toolkits are significantly redesigned, there's no nice way to operate in Xinerama with mis-matched montiors. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: why does my systemd-services not work?
On 06/16/2011 04:25 AM, Michal Schmidt wrote: On 06/16/2011 01:07 PM, Reindl Harald wrote: you can see the master-porcess and a child shortly in ps aux but after a few seconds systemd changes to deactivating (stop-sigterm) and is killing the processes ... [root@testserver:/lib/systemd/system]$ systemctl status dbmail-imapd.service dbmail-imapd.service - DBMail IMAP Server Loaded: loaded (/lib/systemd/system/dbmail-imapd.service) Active: deactivating (stop-sigterm) since Thu, 16 Jun 2011 13:05:11 +0200; 1s ago Process: 5013 ExecStart=/usr/sbin/dbmail-imapd (code=exited, status=0/SUCCESS) Main PID: 5014 (code=exited, status=0/SUCCESS) When the main PID of the service exits, the default action is to kill the whole cgroup. The question is why did the main PID exit in the first place. Michal mpd forks and daemonizes itself, so the main pid dies. Maybe the --no-daemon arg would help. Or there might be a more appropriate Type for mpd. -Bob Arendt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: compat-gcc4.4?
On 05/27/2011 03:55 AM, Neal Becker wrote: I'm trying to use nvidia cuda 4.0. It refuses to even try to compile with gcc4.5. Any chance of a compat-gcc4.4 on f15? I second the idea. A broader reason would be to provide build compatibility with RHEL6. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: fedora mission (was Re: systemd and changes)
On 08/27/10 15:19, Jeff Spaleta wrote: On Fri, Aug 27, 2010 at 2:08 PM, Jon Mastersjonat...@jonmasters.org wrote: Again, I feel it is necessary to have a survey of Fedora users. Preferably annually. And listen to the feedback. If they say yep, we just love the churn, the number of updates and so forth, then fine. If they say actually we'd like less than 800 updates after installing, then also fine. I'm sorry to beat a dead horse, I just feel it is very important that we finally, clearly articulate who our users are and what they want by treating more like customers and gathering their input. How would you prevent such a survey opportunity from being dominated by a vocal minority that wasn't actually representative? It's a difficult question. We can't articulate who are users are. We can articulate who are target users are. And then we can try to survey that target and see if we are meeting their needs. Whether or not there is significant usage outside that target group is an interesting question..but not necessary the question of most importance. -jef Actually I think Fedora *should* articulate who the users are, basically design and express who and what Fedora is designed for. If you poll users - people who download Fedora - and cater to their stated desires for the sake of market share, then market forces will start to drive the shape of the distro. Populist market forces would tend to force everything to a gray mushy mass of similar distros. (see http://en.wikipedia.org/wiki/Hotelling%27s_law). I think it would be much better for Fedora to decide what it *should* be, specifically what the Fedora userspace should be, and excel at that. Don't follow the market or worry about being the most popular distro (unless that's really a goal ..?) Decide the niche, and be strong in that niche. Cheers, -Bob Arendt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: fedora mission (was Re: systemd and changes)
On 08/27/10 16:09, Jeff Spaleta wrote: On Fri, Aug 27, 2010 at 2:47 PM, Bob Arendtr...@rincon.com wrote: Actually I think Fedora *should* articulate who the users are, basically design and express who and what Fedora is designed for. snip I think it would be much better for Fedora to decide what it *should* be, specifically what the Fedora userspace should be, and excel at that. You have contradicted yourself a little bit here. And maybe its a language barrier so I'll be explicit. Who the users are now and who our users should be are not necessarily the same group. Polling our current user-base doesn't necessarily help us define who are users should be. And similarly polling our current user-base doesn't necessarily help us identify what we need to do better to better find and serve the users who should be using Fedora. Nor does it necessarily help us focus on the needs on any particular group that currently exists. We have some users who want A. We have some users who want B. That's what a survey will tell us, it won't help us judge the value of A relative to the value of B as a focus. -jef My first statement was poorly phrased. Fedora should state it's principles, properties, use-cases, plant it's flag, and call for users that are interested in these characteristics to rally around it. Fedora seems to do this from time to time; My point is that it should continue to do this. The real people who should decide that direction are the contributors - it's where the project's strength and energy comes from. Developers, testers, etc. Poll your contributors - polling the userbase adds noise. Fedora should stick with it's Meritocratic roots. .. of course, not being a significant contributor, I've disenfranchised myself. But I'm still a strong Fedora follower and enjoy the distribution. Cheers, -Bob Arendt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
vesa-mode Anaconda install
If support for text mode installation is dead (or dying), recent traffic on the test develop list indicates that there's still a strong need to have a fall-back installation mode. Just in case the your particular version of Radeon, NVidia, (.. whatever) hardware is recognized but doesn't run correctly. Perhaps having a simple vesa arg to anaconda to force a vesa Xserver would provide a quick and simple work-around. It seems like this might be a simple hack to add to anaconda. A short-hand for xdriver=vesa Cheers, -Bob Arendt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vesa-mode Anaconda install
On 08/11/10 08:25, Chris Lumens wrote: Perhaps having a simple vesa arg to anaconda to force a vesa Xserver would provide a quick and simple work-around. It seems like this might be a simple hack to add to anaconda. A short-hand for xdriver=vesa Why do we need a shorthand for an argument you should only have to type once? xdriver= is a more generic mechanism anyway. - Chris OK - I stand down. There seemed to be a flurry of Radeon installs where the card was recognized but didn't work, and even nomodeset was hit or miss. xdriver=vesa is pretty simple. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vesa-mode Anaconda install
On 08/11/10 10:03, Adam Williamson wrote: On Wed, 2010-08-11 at 08:20 -0700, Bob Arendt wrote: . Perhaps having a simple vesa arg to anaconda to force a vesa Xserver would provide a quick and simple work-around. It seems like this might be a simple hack to add to anaconda. A short-hand for xdriver=vesa There's a fallback mode right on the menu - 'Basic video driver installation' or whatever. That uses vesa. Even better. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
