Re: Abandoning boinc-client
Hi Mattia. Thank you for your work. For various reasons I am in contact with the mantainer on Debian (Gianfranco Costamagna). Weeks ago he saw the Fedora commits for BOINC and he told me that he was working on same problems too (but on Debian they have done more fixes). As soon as possible I will try if it is possible to adapt Debian's BOINC code into Fedora and do some tests. If the software will work, I could became a co mantainer and consider to work together with Gianfranco. -- 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: FESCO Elections - June 2015 - Results
Il 30/06/2015 10:13, Richard W.M. Jones ha scritto: Didn't even know it was happening. Where was it announced? Rich. On devel-annou...@lists.fedoraproject.org and annou...@lists.fedoraproject.org -- 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 and regular expressions
Il 29/06/2015 20:32, Reindl Harald ha scritto: that may be true but you hardly can sell DNF as improvement if you need such workarounds while YUM worked perfectly for many years while working around the package manager in general should be avoided because no longs, no dependency solving and no useful confirmation given that the dnf autocompletion is also horrible slow comapared with YUM i see still no advantages from the change, try yum clTAB versus dnf clTAB, in case of DNF it feels like a network request Then I think we should open some tickets/enhancement requests -- 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 and regular expressions
Il 29/06/2015 12:18, Ondrej Oprala ha scritto: I think dnf only supports globbing in this case ... try dnf remove '*debuginfo*' to protect the *-s from being expanded by the shell # dnf remove '*debuginfo*' will remove all packages, I need only to remove fc20 debuginfo packages. # dnf remove '*debuginfo*'.fc20.x86_64 does find anything to remove. -- 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 and regular expressions
Il 29/06/2015 12:25, Reindl Harald ha scritto: dnf remove '*debuginfo*.fc20.x86_64' anyways, it's a terrible regression compared to yum Same result -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
DNF and regular expressions
What is wrong with DNF's regular expression # dnf remove *debuginfo*.fc20.x86_64 ? I am on F22 but I have a lot packets that should match that regular expression, but dnf does not find them. I also tried to add some escape chars like dnf remove *\-debuginfo\-*.fc20.x86_64 but the result is the same -- 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 and regular expressions
Il 29/06/2015 17:05, David Howells ha scritto: Germano Massullo germano.massu...@gmail.com wrote: What is wrong with DNF's regular expression # dnf remove *debuginfo*.fc20.x86_64 Do you mean 'regular expression' or did you mean 'glob'? If you did mean 'regular expression', then did you want: dnf remove .*debuginfo.*[.]fc20[.]x86_64 David I meant glob, sorry -- 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 and regular expressions
Il 29/06/2015 16:28, Jan Zelený ha scritto: However, there is a bug[2] open for this. If you provide your use case there, it will help prioritizing the bug. [2] https://bugzilla.redhat.com/show_bug.cgi?id=1199432 Thank you, I will provide my use case -- 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: Retire a package from Fedora i686 (not x86_64)
A clear example of the mentioned problems for Darktable 32 bit http://redmine.darktable.org/issues/10717 -- 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: Retire a package from Fedora i686 (not x86_64)
A few lines of IRC chat, Freenode #darktable. Hanatos is Darktable project founder. [09:17] ``requiring SSE3 is not really allowed '' [09:17] so much bundled cluelessness :/ [09:19] Germano: re 32-bit [09:19] the sse thing is one thing [09:20] the other is the very limited virtual address space (2G really) [09:20] everybody coding anything half way serious will tell you the same story [09:20] (rawtherapee has the same issues iirc) [09:20] our old cache was allocing one big chunk of memory at startup and maintained it manually [09:20] essentially duplicating a poor man's malloc, specialised for our thumbnail caches [09:21] the new cache is much faster and easier to read [09:21] but based on malloc/free [09:21] which means your virtual address space (not the physical one mapping to your ram) [09:21] will get fragmented and you quickly start addressing blocks above the 10G range [09:22] which may not be a problem, even on systems with only 2G of physical ram, because blocks have been freed in between. it's just on 32-bit systems you can't address it any more and die [09:22] basically, at this point, DT makes no sense on x86, except maybe dt-cli [09:22] which is a similar argument as the sse3 is. [09:22] it's just not a worthwhile experience running this software on this kind of hardware [09:22] boucman: yes, that. [09:23] hanatos_: I think jmalloc is also more clever than glibc malloc wrt fragmentation. that's why blender uses it, afaik [09:24] *je [09:24] Germano: so i'd like to contradict the `upstream doesn't care' bit [09:25] upstream does care. [09:25] just not about random principles and guidelines [09:25] but about how well darktable runs [09:25] Artefact2: jemalloc you mean [09:25] hanatos_: yes [09:25] yes, it's mostly multithreaded/ [09:25] block per thread [09:25] might be worthwhile when running many threads for thumbnail gen [09:25] but honestly i doubt it [09:26] it speeds up another piece of code i wrote [09:26] which uses many 10s of 1000s of malloc calls per second.. [09:26] we don't do that in dt [09:26] (or tcmalloc for that matter) [09:26] simple enough to try with an LD_PRELOAD [09:26] oh yeah. calling malloc this many times is a bad idea anyway [09:32] the alternative would have been allocate ridiculous amounts of memory up front [09:32] bad idea, too [09:32] but if you have a better solution i'd sure like to hear it :) [09:32] the problem is to construct a binary search tree [09:32] i'm not a memory guru, sadly :| [09:32] in parallel [09:32] so you start at the root and push the children as new jobs (malloc job_t) [09:32] and so on [09:33] it's millions of nodes total, so you don't want to allocate them up front [09:33] maybe a compromise. allocate a pool that can store, say 10 jobs at a time [09:34] (and yes, i would agree.. calling malloc is almost always a bad idea, unless you can't avoid it) [09:34] but see.. that pool per thread.. that's exactly what jemalloc/tcmalloc do [09:34] this way you reduce the allocator load by a factor of 10, while still not allocating huge amounts of contiguous memory [09:35] maybe the issue is elsewhere. what are you doing millions of? is it possible to make "bigger" jobs and have less of them? ie a smaller tree [09:38] nope, can't touch the tree [09:38] its some spatial acceleration structure for ray tracing [09:39] it's been optimised for fast ray tracing for many years [09:39] are we still talking about darktable? didn't know it needed a raytracer [09:40] no, different piece of code.. as i said, i don't think darktable needs thread-cached malloc [10:11] Germano: also feel free to refer those guys here to us if they have questions. seems to me that some direct contact may be better. -- 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: Retire a package from Fedora i686 (not x86_64)
Il 07/11/2015 04:29, Ralf Corsepius ha scritto: > I don't see sse3 in /proc/cpuinfo of any machine I have, but I also > don't see any runtime error/warning from darktable. Because SSE3 is shown as "pni", Prescott New Instructions [1] [2] [1]: https://en.wikipedia.org/wiki/SSE3 [2]: http://unix.stackexchange.com/questions/43539/what-do-the-flags-in-proc-cpuinfo-mean -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
git commits mess up
I have done some mistakes in [1] 1) I edited the file once to remove 32 bit CPU support, then I have done the push to master 2) I saw that I have forgotten to add changelog, so I edited the file again, I made a new push to master 3) I started merging the F21 branch to the master and I got the conflict I have found a solution like [2], but I am afraid of making things get worse... Thank you for your time [1]: http://pkgs.fedoraproject.org/cgit/darktable.git/tree/darktable.spec [2]: http://stackoverflow.com/questions/881092/how-to-merge-a-specific-commit-in-git -- 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: git commits mess up
Thank you, I was trying to solve with [1] but your > $ git checkout master -- darktable.spec # solve the conflict by taking the > file as it is in master is the key of success :-) [1]: https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-line/ -- 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: Retire a package from Fedora i686 (not x86_64)
For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Retire a package from Fedora i686 (not x86_64)
I just removed 32bit CPU support from Darktable's spec file due technical reasons. Are there any other things I need to clean up in Fedora infrastructure? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
OpenSSL security fix
A new incoming OpenSSL security fix for high rated security bug https://mta.openssl.org/pipermail/openssl-announce/2015-July/37.html -- 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: OpenSSL security fix
new update http://openssl.org/news/secadv_20150709.txt -- 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: Bad default error policy causes printing issues and BIG usability issues
Il 06/12/2014 19:29, valent.turko...@gmail.com ha scritto: > Who is responsible for user experience of Fedora desktop? To whom > should I point this issue to? https://fedoraproject.org/wiki/QA you could also fill a bugreport against CUPS component in https://bugzilla.redhat.com/ I agree with you. I migrated some offices to Fedora and sometimes I receive phone calls about printing troubles. When I go personally to check what is wrong I often saw a big CUPS queue and the printer in pause -- 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: Looking for new maintainer: ownCloud (Fedora / EPEL)
Il 31/08/2015 18:19, Adam Williamson ha scritto: > There isn't really a great alternative to ownCloud (that I know of) if > you actually *want* a 'personal cloud server' with all the bits OC > has, but I realized I just don't and I can't stand the pain of > maintaining that beast just to keep my calendar and contacts > synchronized. I do honestly feel bad about it, but I'd rather be up- > front than pretend I'm still doing it but actually never get around to > it. What about OpenAtrium? http://openatrium.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Disable PulseAudio flat volumes to prevent it from pushing volume level to max
=== Definition of flat-volumes from [1] : it scales the device-volume with the volume of the "loudest" application. For example, raising the VoIP call volume will raise the hardware volume and adjust the music-player volume so it stays where it was, without having to lower the volume of the music-player manually. === Today I had a scary experience with the audio of my computer. I was listening to music with Amarok, using my headphones... The KMix volume level was ~ 35%. When I logged into a video conference application, the volume suddenly reached the 100%. I was shocked, having the maximum audio level shooted in your ears is a painful experience. The conference application that triggered PulseAudio pushing volume to maximum level probably should have never asked the system for a 100% audio level, but on the other hand, PulseAudio should never allow an application to make such sudden changes. To avoid that, you have to set flat-volumes = no in /etc/pulse/daemon.conf I found many users stories complaining about this default setting [2] [3] [4] and you can easily find other by searching "pulseaudio flat volumes". I completely agree with user gaggra comment at [3] <> Moreover this default setting can cause sound crackling [5]. So I would like to start a discussion about disabling this default behaviour for the mentioned reasons. [1] https://wiki.archlinux.org/index.php/PulseAudio [2] https://major.io/2015/06/08/pulseaudio-popping-with-multiple-sounds-in-fedora-22/ [3] https://www.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_volumes_in_pulseaudio_a/ [4] http://awesomelinux.blogspot.it/2013/06/pulseaudios-dynamic-volume-levels-are.html [5] https://bugzilla.redhat.com/show_bug.cgi?id=1264177 -- 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: Disable PulseAudio flat volumes to prevent it from pushing volume level to max
Il 17/09/2015 21:13, Andrew Lutomirski ha scritto: > > To clarify: did you get blasted by music or by video conference > sounds? If the music volume got louder, then it sounds like either a > straight-up bug in PulseAudio (and a severe and dangerous one at that) > or a serious bug in your video conference volume in which it adjusts > the volume of streams other than its own. > > If you got blasted by video conference sounds, then I'd say it's a > serious design flaw in PulseAudio. PulseAudio should offer an > easy-to-configure maximum volume (probably A-weighted power, but peak > level works, too, if considerably less well) on a per-output basis > with which to protect your ears. > > --Andy I got blasted from the music because I was not making a conference, I only logged into the software, so the music was the only sound I was listening to. PulseAudio pushed the master audio level to 100% (therefore all applications audio level changed to 100%, due flat-volume setting). -- 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: Proposal to reduce anti-bundling requirements
I have read the whole discussion and I would like to share my opinion, even if I think it could be a bit off-topic. Given that Fedora community alone, cannot educate every upstream developer about unbundling, and considering that it is a problem that interests all main Linux distributions: I think that Fedora community could (and should) propose to other Linux distribution communities to make a general effort to kindly ask upstream devs to reconsider their work, enforcing unbundling. This will take years, but I think it is a way we should cover. -- 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 is completly broken
You may want to give a look to https://github.com/rpm-software-management/dnf/wiki/Hacking#logging -- 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 is completly broken
Il 04/10/2015 16:32, Neal Gompa ha scritto: > On Sun, Oct 4, 2015 at 10:24 AM, Germano Massullo > <germano.massu...@gmail.com <mailto:germano.massu...@gmail.com>>wrote: > > In past days I experienced the following problem > "dnf install" exits if there is a non existing package in the > requested > packages list" > https://bugzilla.redhat.com/show_bug.cgi?id=1268606 > > > Do you have " > strict=True > " in > /etc/dnf/dnf.conf > ? > No -- 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 is completly broken
In past days I experienced the following problem "dnf install" exits if there is a non existing package in the requested packages list" https://bugzilla.redhat.com/show_bug.cgi?id=1268606 -- 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: Trying to contact package maintainer for boinc-client
Hi Laurence, did you receive admin rights from the package mantainer? https://admin.fedoraproject.org/pkgdb/package/boinc-client/ I just made the same request because I would like to help -- 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: Trying to contact package maintainer for boinc-client
Lastest update [1] has been submitted by user [2] that is a provenpackager **What is a provenpackager?** Provenpackagers are members of the 'provenpackager' group. In addition to the rights granted to members of 'packager', provenpackagers are able to commit changes to packages they do not own or maintain. [1] https://bodhi.fedoraproject.org/updates/FEDORA-2015-12667 [2] https://bodhi.fedoraproject.org/users/corsepiu -- 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: Trying to contact package maintainer for boinc-client
The actual BOINC working mantainer is Mattia Verga -- 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: Disable PulseAudio flat volumes to prevent it from pushing volume level to max
Il 22/09/2015 03:43, Rex Dieter ha scritto: > Germano Massullo wrote: > >> Il 21/09/2015 21:45, Thomas Daede ha scritto: >>> Is there currently a bug open for this? I'd rather it not get lost. >> I think that a FESCo ticket would be more appropriate. > I think it would be premature to appeal to FESCo without giving pulseaudio > maintainers a chance to respond to your proposal first. > > Mind filing a bug with your proposal ? > > -- Rex > Here we go https://bugzilla.redhat.com/show_bug.cgi?id=1265267 -- 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: Disable PulseAudio flat volumes to prevent it from pushing volume level to max
Il 21/09/2015 21:45, Thomas Daede ha scritto: > Is there currently a bug open for this? I'd rather it not get lost. I think that a FESCo ticket would be more appropriate. I will open it during next days. -- 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: Lua 5.2
2015-11-19 10:51 GMT+01:00 Hans de Goede <hdego...@redhat.com>: > Hi, > > On 18-11-15 08:06, Germano Massullo wrote: > >> Hi, I would like to ask "lua" and "compat-lua" maintainers if it is >> possible to have a packaged 5.2 lua version. >> A use case? Upstream Darktable ships a bundled Lua version 5.2, and it is >> not compatible with Lua 5.3. Fedora's Darktable does not ship the bundled >> Lua to respect Fedora packaging rules. >> > > If Darktable is using 5.2, it is likely being actively maintained > upstream. So you could ask Darktable upstream to move to 5.3 for > some future version and use a bundled 5.2 in the mean time. > > compat-lua is mostly used by some somewhat older games who > are not being updated by upstream and which cannot easily > be ported to 5.2. > > Regards, > > Hans > darktable developers said that the migration to Lua 5.3 has not yet planned, so I will keep disabled the bundled version -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Lua 5.2
Hi, I would like to ask "lua" and "compat-lua" maintainers if it is possible to have a packaged 5.2 lua version. A use case? Upstream Darktable ships a bundled Lua version 5.2, and it is not compatible with Lua 5.3. Fedora's Darktable does not ship the bundled Lua to respect Fedora packaging rules. -- 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: F25 Self Contained Change: Release Engineering Automation Workflow Engine
Il 03 giu 2016 18:48, "Adam Williamson" > YAAAY LOL -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Python packages not compliant to Fedora guidelines
In past days I filled many review requests for various python libraries, in order to submit python-netdiff [1] and python-django-netjsongraph [2]. During this process, I noticed that a lot of python packages are not compliant to Fedora Guidelines for packaging Python stuff [3]. So you have to deal with many packages that have the old naming (python-*) and are not using the new python2-* and python3-* Moreover there are packages that have newer branches that are compliant to guidelines and older that are not, so the result is that you have a *your* package that builds for example on >= F23 but does not on F22, and maybe on EPEL7 too. I think it would be nice if we put some effort to have all those problems fixed for F24 release [1]: https://pypi.python.org/pypi/netdiff [2]: https://pypi.python.org/pypi/django-netjsongraph [3]: https://fedoraproject.org/wiki/Packaging:Python -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Orphaned LemonPOS
I orphaned package LemonPOS. Upstream developer seems to not be longer working on the project, and the software is not stable and reliable as it should. Best regards -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Fedorahosted ssh keys
Il 22/01/2016 14:50, Sam Varshavchik ha scritto: > Unable to pull from a fedorahosted git repo after updating my ssh keys. > > I uploaded my updated SSH keys to FAS, they're there. Is there a > separate place to update my ssh keys for fedorahosted git, or is there > a sync delay? As far I remember, the update is not immediate, you should wait for a certain amount of time -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Name of some Ruby "application" packages
Hi, I am studying Ruby packaging guidelines. I would need to know some packages names that have been built following the "Applications" [1] rules, in order to read their spec file and upstream sources tree. Thank you for your time [1]: https://fedoraproject.org/wiki/Packaging:Ruby?rd=Packaging/Ruby#Applications signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Package presentation: python-netdiff
Hi, I would like to present you a package that has just been accepted to be in Fedora repositories: python-netdiff. Netdiff is a Python librarybased on networkxthat provides utilities for parsing network topology formatsof open source dynamic routing protocols (like OLSR [2], BATMAN [3]) and detecting changes in these topologies. It provides standard NetJSONNetworkGraph[4] output facilitating the detection of changes in network topology (more infos at [1]). Main contributors come from European wireless communities like Ninux.org [5] [6] and Gufi.net [7] Some examples of netdiff use are software projects nodeshot [8] and django-netjsongraph [9] The package should be available in stable repo in a few days. Have a nice day [1]: https://github.com/ninuxorg/netdiff [2]: http://www.olsr.org/ [3]: https://www.open-mesh.org [4]: http://netjson.org/ [5]: http://wiki.ninux.org/ [6]: https://apps.db.ripe.net/search/query.html?searchtext=ninux=RIPE_NCC#resultsAnchor [7]: https://guifi.net/ [8]: https://github.com/ninuxorg/nodeshot [9]: https://github.com/interop-dev/django-netjsongraph signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
BOINC service does not write into log files
Hi, I am one of BOINC client maintainers. I am trying to figure out why BOINC client 7.6.x does not write logs inside /var/log/boinc{,_err}.log files so I started a very little thread in BOINC forum [1], attaching boinc.service file and other stuff. Reading guides about systemd's debugging, I decided to add Environment=SYSTEMD_LOG_LEVEL=debug to boinc-client.service file, then I have runned: # journalctl -u boinc-client but nothing useful come out, only a few BOINC regular messages, instead #journalctl -b _PID=28226 returned -- Logs begin at dom 2015-12-13 09:18:03 CET, end at sab 2016-05-21 17:26:39 CEST. -- mag 21 17:26:34 host boinc_client[28226]: 21-May-2016 17:26:34 Initialization completed SELinux is in permissive mode. I attach a few useful conf files and outputs. Don't look at Fedora's git because certain files have not yet been updated. = # cat /usr/lib/systemd/system/boinc-client.service [Unit] Description=Berkeley Open Infrastructure Network Computing Client Documentation=man:boinc(1) After=network-online.target [Service] Type=forking Nice=10 User=boinc Group=boinc PermissionsStartOnly=yes WorkingDirectory=/var/lib/boinc ExecStartPre=/usr/bin/touch /var/log/boinc.log /var/log/boinc_err.log ExecStartPre=/bin/chown boinc:boinc /var/log/boinc.log /var/log/boinc_err.log ExecStart=/usr/bin/boinc_client --daemon --start_delay 1 ExecStop=/usr/bin/boinccmd --quit ExecReload=/usr/bin/boinccmd --read_cc_config ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile IOSchedulingClass=idle Environment=LOGFILE=/var/log/boinc.log Environment=ERRORLOG=/var/log/boinc_err.log Environment=SYSTEMD_LOG_LEVEL=debug [Install] WantedBy=multi-user.target = = # ls -latr /var/log/boinc* -rw-r--r--. 1 boinc boinc 0 21 mag 15.58 /var/log/boinc.log -rw-r--r--. 1 boinc boinc 0 21 mag 15.58 /var/log/boinc_err.log = = An entry from top 25657 boinc 39 19 76756 36704 2088 R 64,7 0,2 9:49.40 wcgrid_mcm1_7.3 = [1]: http://boinc.berkeley.edu/dev/forum_thread.php?id=11011 signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Testing request: AMD chipset kernel issue
I am very busy in these weeks, but if you need other testing cases, I have many AMD machines -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Self Introduction: Guido Aulisi
Hi Guido, welcome! Have you already chosen a sponsor? [1] Have a nice day [1]: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Self Introduction: Giovanni Simoni
Ciao Giovanni, welcome! Thank you for all the work that you will do for the Fedora Project! -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Review swap
I would like to take it, but I see that is already taken. Do you want to change reviewer? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Simple python package review swap - python-feedgenerator
Taken! Could you review my https://bugzilla.redhat.com/show_bug.cgi?id=1375222 Thank you ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: upstream dev. asks suggestions about howto make packagers work easier (bundled libraries, etc.)
Il 20/11/2016 21:38, Nico Kadel-Garcia ha scritto: >> I think it would be nice to make a discussion even for non Python >> packages, so we can elaborate a sort of vademecum that a packager >> could show to upstreams when there is a collaboration between them. >> >> Have a nice day > Most upstream developers are happy to work with segregating > components. A few... such as the awscli python package manager. > use cfode with very bleeding edge and destabilizing dependencies. Ok, concerning [1][2] (Python+ JavaScript), what would you suggest to the upstream (Federico Capoano), in order to make the work easier for both us and him? Thank you [1]: https://github.com/interop-dev/django-netjsongraph [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1369213 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
upstream dev. asks suggestions about howto make packagers work easier (bundled libraries, etc.)
We often deal with upstream developers that bundle libraries in their code, so to make a package we have to debundle them, etc. This time, an upstream dev. asked me what he could do to make easier the work of packagers. In this case the software is python-netjsongraph [1] that bundles javascript-d3 library and that is being reviewd at [2] I think it would be nice to make a discussion even for non Python packages, so we can elaborate a sort of vademecum that a packager could show to upstreams when there is a collaboration between them. Have a nice day [1]: https://github.com/interop-dev/django-netjsongraph [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1369213 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: upstream dev. asks suggestions about howto make packagers work easier (bundled libraries, etc.)
Il 20/11/2016 21:38, Nico Kadel-Garcia ha scritto: >> I think it would be nice to make a discussion even for non Python >> packages, so we can elaborate a sort of vademecum that a packager >> could show to upstreams when there is a collaboration between them. >> >> Have a nice day > Most upstream developers are happy to work with segregating > components. A few... such as the awscli python package manager. > use cfode with very bleeding edge and destabilizing dependencies. Ok, concerning [1][2] (Python+ JavaScript), what would you suggest to the upstream (Federico Capoano), in order to make the work easier for both us and him? Thank you [1]: https://github.com/interop-dev/django-netjsongraph [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1369213 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: state of advanced audio in Fedora
Recently Ardour 4 has been added to Fedora repositories (without video support due legal problems). You may want to give a look to it https://admin.fedoraproject.org/pkgdb/package/rpms/ardour4/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
IPFS and Fedora repositories
In past days I started playing with IPFS[1] "A peer-to-peer hypermedia protocol to make the web faster, safer, and more open." At [2] there is a very quick explanation about how IPFS works. The Freenode IRC channel #ipfs has more than 1000 users, so there is a great interest in it. By reading some articles, I noticed a nice paragraph of article [3], that made me wonder about IPFS usage on Fedora repositories: = Pinning Data to Save It IPFS has a notion of pinning content onto your IPFS node. When you “pin” content on your IPFS node, you’re adding the content’s hash (aka fingerprint) to the node’s pin set. As long as you have that hash in the node’s pin set, the node will keep a copy of the corresponding content on your machine. When you write your dataset into IPFS, your IPFS node will give you the hash for that dataset. You can then pass that hash to any of your peers and ask them to pin it on their IPFS nodes as well. As soon as you add a hash to your IPFS node’s pin set, the node will coordinate with peers on the IPFS network to pull a copy of the data onto your machine. = Since this mailing list is full of interesting opinions and ideas, I would like to hear your thoughts about what could be (in a far future) pros and cons of hypothetical IPFS based Fedora repositories. Thank you for your time [1]: https://ipfs.io/ [2]: https://ipfs.io/#how [3]: https://medium.com/@flyingzumwalt/instructions-for-saving-endangered-data-its-time-to-get-decentralized-23fb96aa8179#.bvs3eq5ag signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ovirt status and ovirt alternatives
I have noticed that the most important ovirt packages have been orphaned and/or retired, so ovirt user experience seems to be compromised. Was that on purpose? What are some good alternatives? Thank you very much ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Concerning Beignet OpenCL driver stability
As darktable co-maintainer, I am getting a lot of crash reports related to Beignet OpenCL driver (see below). Recently darktable developers inserted Beignet into blacklist because they state that it is a poorly maintained OpenCL driver. Since it is a library shipped by default on Fedora installations, I would like to know if there are any positive feedbacks about Beignet usage https://bugzilla.redhat.com/show_bug.cgi?id=1195367 https://bugzilla.redhat.com/show_bug.cgi?id=1460400 https://bugzilla.redhat.com/show_bug.cgi?id=1468392 https://bugzilla.redhat.com/show_bug.cgi?id=1469023 https://bugzilla.redhat.com/show_bug.cgi?id=1470161 https://bugzilla.redhat.com/show_bug.cgi?id=1468977 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Preventing broken updates tree (packages downgrade) during release upgrades
There are many package maintainers who caused F25 packages being newer than F26 packages, so during F25->F26 upgrade, dnf wanted to downgrade them, for example packages quoted below. I think that bodhi quality assurance should be improved to prevent such events that break updates "tree" expat i686 2.2.0-2.fc26 fedora 91 k expat x86_64 2.2.0-2.fc26 fedora 92 k expat-debuginfox86_64 2.2.0-2.fc26 fedora-debuginfo 199 k expat-develx86_64 2.2.0-2.fc26 fedora 62 k httpie noarch 0.9.4-7.fc26 fedora106 k mariadbx86_64 3:10.1.21-5.fc26 fedora6.4 M mariadb-common x86_64 3:10.1.21-5.fc26 fedora 68 k mariadb-config x86_64 3:10.1.21-5.fc26 fedora 31 k mariadb-debuginfo x86_64 3:10.1.21-5.fc26 fedora-debuginfo 98 M mariadb-devel x86_64 3:10.1.21-5.fc26 fedora918 k mariadb-embedded x86_64 3:10.1.21-5.fc26 fedora4.2 M mariadb-errmsg x86_64 3:10.1.21-5.fc26 fedora205 k mariadb-libs x86_64 3:10.1.21-5.fc26 fedora661 k mariadb-server x86_64 3:10.1.21-5.fc26 fedora 18 M mariadb-server-utils x86_64 3:10.1.21-5.fc26 fedora2.2 M pcre i686 8.40-7.fc26 fedora203 k pcre x86_64 8.40-7.fc26 fedora202 k pcre-cpp x86_64 8.40-7.fc26 fedora 40 k pcre-debuginfo x86_64 8.40-7.fc26 fedora-debuginfo 1.2 M pcre-devel x86_64 8.40-7.fc26 fedora546 k pcre-utf16 x86_64 8.40-7.fc26 fedora188 k pcre-utf32 x86_64 8.40-7.fc26 fedora179 k pyp2rpmnoarch 3.2.1-3.fc26 fedora 76 k qt5-qtbase x86_64 5.7.1-15.fc26 fedora3.0 M qt5-qtbase-common noarch 5.7.1-15.fc26 fedora 32 k qt5-qtbase-debuginfo x86_64 5.7.1-15.fc26
Re: Concerning Beignet OpenCL driver stability
Looks like the problem has been fixed -> https://bugzilla.redhat.com/show_bug.cgi?id=1470876#c6 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: JOSM now use openjfx, but openjfx not added to jvm after installation
Il 19/07/2017 18:03, OLIVIER Cedric ha scritto: > These steps are described in > /usr/share/doc/openjfx/README.fedora. Could you please attach such file in the discussion? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Fedora spins torrents statistics
Il 03/05/2017 18:38, Adam Williamson ha scritto: > Can't conclude that from a single seeder, as we're missing information > on *how many seeders there are* for each torrent. 47.81 GB Fedora 25 KDE x86_64 51 seeders 29.40 GB Fedora 25 KDE i386 19 seeders 24.14 GB Fedora 25 Xfce i386 15 seeders 21.96 GB Fedora 25 Xfce x86_64 35 seeders 20.09 GB Fedora 25 LXDE x86_64 22 seeders 19.45 GB Fedora 25 LXDE i386 23 seeders ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Review swap: keepassxc - Cross-platform password manager
Hello, I am looking for a review swap: here is mine: keepassxc - Cross-platform password manager https://bugzilla.redhat.com/show_bug.cgi?id=1450633 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Review swap: keepassxc - Cross-platform password manager
Review request has been taken ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Security of confined user/application and access to video group
Il 07/06/2017 09:22, Lennart Poettering ha scritto: > On Tue, 06.06.17 17:44, Germano Massullo (germano.massu...@gmail.com) wrote: > >> 2017-06-06 14:40 GMT+02:00 Lennart Poettering <mzerq...@0pointer.de>: >>> Note sure what "boinc-client" does, but if this isn't turstworthy then >>> it probably shouldn't be able to get access to "video". >> boinc-client is the client side version of BOINC (Berkeley Open >> Infrastructure for Network Computing). You can use your computers to >> help scientific research of many different projects. You can think >> about it as a music player, the projects as the music discs, and the >> working units as disc tracks. >> Since working units are closed source software we always considered >> them not trustworthy, therefore they always runned confined as much as >> possible > If so, this sounds like a great candidate for using systemd's > sandboxing functionality. Things like CapabilityBoundingSet=, > PrivateTmp=, ProtectSystem=, ProtectHome=, ProtectKernelTunables=, > ProtectKernelModules=, ProtectControlGroup=, SystemCallFilter=, > SystemCallArchitectures=, RestrictAddressFamilies=, > RestrictNamespaces=, RestrictRealtime=, ... > > See systemd.exec(5) for more information. > > Lennart > Thank you, I will consider systemd sandboxing too ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Security of confined user/application and access to video group
Hi there, I am the co-maintainer of boinc-client [1]. boinc-client runs as a service, and both it and its working units run as 'boinc' user and they are confined by SELinux. Recently, I investigated to figure out why boinc-client, while running as a service, could not detect videocard for GPU calculus. In order to fix this problem I had to add Group=video to boinc-client systemd unit file. I have not yet pushed such change to boinc-client Fedora git, because I would like to ask you if this can cause a breach into boinc-client confinement. I mean, I am wondering if a process that can have access to videocard, could for example read what you are doing on your machine, the passwords you copy and paste, etc. What do you think about? Best regards For convenience I attached boinc-client unit file = [Unit] Description=Berkeley Open Infrastructure Network Computing Client Documentation=man:boinc(1) After=network-online.target [Service] Type=forking Nice=10 User=boinc WorkingDirectory=/var/lib/boinc ExecStart=/usr/bin/boinc_client --daemon --start_delay 1 ExecStop=/usr/bin/boinccmd --quit ExecReload=/usr/bin/boinccmd --read_cc_config ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile IOSchedulingClass=idle Environment=LD_LIBRARY_PATH=/opt/amdgpu-pro/lib64 Group=video [Install] WantedBy=multi-user.target = [1]: https://admin.fedoraproject.org/pkgdb/package/rpms/boinc-client/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Security of confined user/application and access to video group
2017-06-06 14:40 GMT+02:00 Lennart Poettering: > Note sure what "boinc-client" does, but if this isn't turstworthy then > it probably shouldn't be able to get access to "video". boinc-client is the client side version of BOINC (Berkeley Open Infrastructure for Network Computing). You can use your computers to help scientific research of many different projects. You can think about it as a music player, the projects as the music discs, and the working units as disc tracks. Since working units are closed source software we always considered them not trustworthy, therefore they always runned confined as much as possible >> ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile > > If this file is not supposed to survive a daemon restart it really > should be placed in /run somewhere. > I will take care of this. >> Group=video > > I have the suspicion you should better > use SupplementaryGroups=video than Group=, [...] I will not use any of them, as soon as possible I will start investigating on using udev/ACLs on dri/render to solve the GPU detection problem. Thank you for clarifing my dubts Lennart Have a nice day! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
[RFC] Use industry-proven solution for XML routines
Fedora has a strong history of collaboration with upstream. A guy, Artem Vorotnikov, is developing Volunode[1] a fork of boinc-client very focused on improving Linux side of such software. As boinc-client co-maintainer, I really appreciated what he doing at the moment, so I will start the packaging process for Fedora/EPEL in next future. I am writing to you because I would like that Fedora community could help him, providing feedbacks about a RFC he made about usage of XML routines [2]. If you cannot reply to Github page [2], feel free to write in this mailing list, and I will forward your replies to him. Thank you very much [1]: http://volunode.com/about/ [2]: https://github.com/volunode/volunode/issues/2 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: PkgDB search / info functionality
To search packages you could use https://apps.fedoraproject.org/packages/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora spins torrents statistics
As torrents seeder of certain Fedora spins, I would like to share some upload statistics: 47.81 GB Fedora 25 KDE x86_64 29.40 GB Fedora 25 KDE i386 24.14 GB Fedora 25 Xfce i386 21.96 GB Fedora 25 Xfce x86_64 20.09 GB Fedora 25 LXDE x86_64 19.45 GB Fedora 25 LXDE i386 Torrents have been added on 25 November 2016 Best regards ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Security of confined user/application and access to video group
Ah, forget the line Environment=LD_LIBRARY_PATH=/opt/amdgpu-pro/lib64 since it is needed only for my system ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Improving Linux laptop battery life: Testers Wanted
Hi Hans, I can provide ~10 different Thinkpad models to test your code. Looking forward to start! Have a nice day ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Improving Linux laptop battery life: Testers Wanted
This message may be useful to others having my similar problem. On a Thinkpad X220, after having booted the custom kernel, running [root@machine]# cat /sys/class/scsi_host/host0/link_power_management_policy I get max_performance instead of med_power_with_dipm Here some machine details [root@machine]# cat /etc/rc.d/rc.local #!/bin/sh for i in /sys/class/scsi_host/host*/link_power_management_policy; do echo med_power_with_dipm > $i done [root@machine]# ls -latr /etc/rc.d/rc.local -rwxrwxr-x. 1 user user 119 13 set 14.53 /etc/rc.d/rc.local [root@machine]# cat /proc/cpuinfo | grep "model name" model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz [root@machine]# cat /sys/class/scsi_device/*/device/model Samsung SSD 850 (it is a Samsung 850 PRO) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Improving Linux laptop battery life: Testers Wanted
Il 17/09/2017 15:39, Hans de Goede ha scritto: > Hi, > > On 14-09-17 14:44, Germano Massullo wrote: >> Hi Hans, I can provide ~10 different Thinkpad models to test your code. >> Looking forward to start! > > That is great, thank you. > > I'm looking forward to hear back from you with the results. > > Regards, > > Hans > Just a question before I start with tests on some machines. Concerning the very little probability that some data corruption could happen: which kind of data corruption would be? Bit flips, etc. Yes I do have backups, but I wanted to ask that just to understand if I better to resume data from backups even if I had no apparent crashes during tests. Have a nice day ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Improving Linux laptop battery life: Testers Wanted
Thank you for the extensive explanation! > TL;DR: I do not expect you to see any silent data corruption if > anything goes wrong, you should know. Ok, at the end of each day I will give a look to "dmesg", just to be sure that everything went fine. I will also check for firmware updates before starting the tests. A few questions/statements: 1) is it okay to run the tests with the power cord plugged? Or do I need to use battery in order to trigger such kind of power saving features? 2) In your guide you specified "[...] on a clean Fedora". I actually cannot run a new Fedora installation on my SSDs, but I haven't messed up with any kind of strange powersaving features, so it should be fine to use my regular Fedora installation for the tests. Do you confirm? To be sure, I will attach to test results e-mail, also: - /etc/fstab - /proc/cmdline - # lshw 3) Since in these days I am not using much the Thinkpads, I think I will run Phoronix suite in order to simulate machine activity Among all Phoronix test suite tests, If you think that there are some that best fit your case, please let me know. To read a list of disk oriented benchmarks, you can do: # dnf install phoronix-test-suite $ phoronix-test-suite list-available-tests | grep Disk Best regards ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Hi
Welcome!! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: A less "bloated" KDE spin
# dnf remove foo and you can easly get rid of what you do not like. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Improving Linux laptop battery life: Testers Wanted
This message may be useful to others having my similar problem. On a Thinkpad X220, after having booted the custom kernel, running [root@machine]# cat /sys/class/scsi_host/host0/link_power_management_policy I get max_performance instead of med_power_with_dipm Here some machine details [root@machine]# cat /etc/rc.d/rc.local #!/bin/sh for i in /sys/class/scsi_host/host*/link_power_management_policy; do echo med_power_with_dipm > $i done [root@machine]# ls -latr /etc/rc.d/rc.local -rwxrwxr-x. 1 user user 119 13 set 14.53 /etc/rc.d/rc.local [root@machine]# cat /proc/cpuinfo | grep "model name" model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz [root@machine]# cat /sys/class/scsi_device/*/device/model Samsung SSD 850 (it is a Samsung 850 PRO) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Improving Linux laptop battery life: Testers Wanted
> It might be that systemd does not like that rc.local is owned > by "user" rather then "root" Unfortunately # chown root:root /etc/rc.d/rc.local did not solve the problem, instead manually running the script as root, changed the /sys/class/scsi_host/host0/link_power_management_policy state to med_power_with_dipm In powertop I noticed a saving of ~1 Watt. I will send you complete test results as you requested in https://hansdegoede.livejournal.com/18412.html For people who wants to stress the disk: # dnf install phoronix-test-suite $ phoronix-test-suite install disk $ phoronix-test-suite run disk I will run disk suite tests many times per day for 2 weeks ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Improving Linux laptop battery life: Testers Wanted
Hi Hans, do you have any F27 kernel to test SATA Link Power Management (LPM)? Best regards ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
compat-openssl10 and openssl conflict
I am working on unretiring Estonia ID Card utilities[1] and I noticed that compat-openssl10 conflicts with openssl. In my case I am speaking about compat-openssl10-devel and openssl-devel. I noticed that while compiling libdigidocpp [2] in my eeste-id-card-tools Copr repository [3]. Yesterday I also experienced a similar problem with their respective debuginfos [4]. Isn't possible to fix this conflict? Best regards [1]: https://src.fedoraproject.org/rpms/qdigidoc https://src.fedoraproject.org/rpms/qesteidutil/ https://src.fedoraproject.org/rpms/libdigidocpp https://src.fedoraproject.org/rpms/libdigidoc https://src.fedoraproject.org/rpms/esteidcerts [2]: https://copr-be.cloud.fedoraproject.org/results/germano/eeste-id-card-tools/fedora-rawhide-x86_64/00682275-libdigidocpp/root.log.gz https://copr-be.cloud.fedoraproject.org/results/germano/eeste-id-card-tools/fedora-rawhide-x86_64/00682275-libdigidocpp/ [3]: https://copr.fedorainfracloud.org/coprs/germano/eeste-id-card-tools/builds/ [4]: https://bugzilla.redhat.com/show_bug.cgi?id=1518389 signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: compat-openssl10 and openssl conflict
Il 29/11/2017 23:29, Adam Williamson ha scritto: > Why do you need to have both -devel packages installed at once? libdigidoc needs compat-openssl10-devel libdigidocpp needs openssl-devel and libdigidoc-devel so IMHO this could trigger DEBUG util.py:478: Error: DEBUG util.py:478: Problem: package libdigidoc-devel-3.10.2-2.fc28.x86_64 requires compat-openssl10-devel, but none of the providers can be installed DEBUG util.py:478:- package compat-openssl10-devel-1:1.0.2m-1.fc28.i686 conflicts with openssl-devel provided by openssl-devel-1:1.1.0g-1.fc28.x86_64 DEBUG util.py:478:- package compat-openssl10-devel-1:1.0.2m-1.fc28.x86_64 conflicts with openssl-devel provided by openssl-devel-1:1.1.0g-1.fc28.x86_64 DEBUG util.py:478:- cannot install the best candidate for the job DEBUG util.py:478:- conflicting requests DEBUG util.py:478: (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages) DEBUG util.py:616: Child return code was: 1 DEBUG util.py:635: child environment: None DEBUG util.py:561: Executing command: /usr/bin/gzip -9 --force /var/lib/copr-rpmbuild/results/root.log with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'en_US.UTF-8'} and shell True In log https://copr-be.cloud.fedoraproject.org/results/germano/eeste-id-card-tools/fedora-rawhide-x86_64/00682275-libdigidocpp/root.log.gz *libdigidoc.spec* https://copr-be.cloud.fedoraproject.org/results/germano/eeste-id-card-tools/fedora-rawhide-x86_64/00682273-libdigidoc/libdigidoc.spec *libdigidocpp.spec* https://copr-be.cloud.fedoraproject.org/results/germano/eeste-id-card-tools/fedora-rawhide-x86_64/00682275-libdigidocpp/libdigidocpp.spec signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Introducing Suzanne Yeghiayan (aka Sly)
Welcome Sly! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Unretiring Estonia ID cards utilities
Good day, I am unretiring packages for Estonia ID cards Review request: qdigidoc - Estonian digital signature application https://bugzilla.redhat.com/show_bug.cgi?id=1519749 Review request: qesteidutil - Estonian ID card utility https://bugzilla.redhat.com/show_bug.cgi?id=1519323 Review request: libdigidocpp - Library offers creating, signing and verification of digitally signed documents, according to XAdES and XML-DSIG standards https://bugzilla.redhat.com/show_bug.cgi?id=1519747 Review request: esteidcerts - Estonian ID card root, intermediate and OCSP certificates https://bugzilla.redhat.com/show_bug.cgi?id=1518957 While testing them I made also a Copr repo https://copr.fedorainfracloud.org/coprs/germano/este-id-card-tools/ More infos about Estonia electronic identity: https://e-estonia.com/solutions/e-identity/id-card/ https://e-estonia.com/solutions/e-identity/e-residency signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Concerning /etc/opt usage
Today I have received pull request [1]. Since line 62 %dir %{_sysconfdir}/opt/chrome/native-messaging-hosts/ means /etc/opt/chrome/native-messaging-hosts/ and since packaging guidelines [2] say that a package may only use directories in the |/opt/fedora,| I would reject this pull request. What do you think about? Best regards [1]: https://src.fedoraproject.org/rpms/webextension-token-signing/pull-request/1 [2]: https://fedoraproject.org/wiki/Packaging:Guidelines#Limited_usage_of_.2Fopt.2C_.2Fetc.2Fopt.2C_and_.2Fvar.2Fopt ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Concerning /etc/opt usage
Il 05/06/18 04:29, Rex Dieter ha scritto: > Rex Dieter wrote: > >> Germano Massullo wrote: >> >>> Today I have received pull request [1]. >>> Since line 62 >>> %dir %{_sysconfdir}/opt/chrome/native-messaging-hosts/ >>> means >>> /etc/opt/chrome/native-messaging-hosts/ >>> and since packaging guidelines [2] say that a package may only use >>> directories in the |/opt/fedora,| >> I don't think that guideline applies, as it concerns only stuff under >> /opt, not /etc (or /etc/opt) > Having actually read the guideline now, it *does* apply to /etc/opt too. > Sorry Thank you! Have a nice day ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
nextcloud-client packaging help wanted
Hello, I am the maintainer of nextcloud-client. I am writing to ask for help in maintaining nextcloud-client. Actually nextcloud-client is just a nextcloud themed version[1] of owncloud-client[2]. The new nextcloud-client[3] instead is still at a very alpha state. We used to be 5 maintainers, but after months of co-maintainers being unresponsive, I removed them, otherwise people could think that there are plenty of people working on the package. The package needs to be updated to lastest owncloud-client version and there is also the need for starting working on a new spec file for the next generation nextcloud client [3]. Best regards [1]: https://github.com/nextcloud/client_theming [2]: https://github.com/owncloud/client [3]: https://github.com/nextcloud/desktop ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2ZPIGW7S35VDUL34BZZSUL5WAV5WPWNO/
Re: nextcloud-client packaging help wanted
Ok I have just had a talk with upstream. We will jump directly to 2.5. They will release it soon as nextcloud-client, so no themes will be needed ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/C4T2TAW325DBFNGYFYII4OVUJS72YIM6/
Re: nextcloud-client packaging help wanted
Thank you Christian! Anyone else? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UGJLA7ZR6KENAFQ3ZK74LL2D2ADNWBUB/
Re: Rstudio
Hi, any progress on this? Best regards ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Rstudio
2018-01-20 14:57 GMT+01:00 Reindl Harald <h.rei...@thelounge.net>: > > > Am 20.01.2018 um 14:47 schrieb Germano Massullo: >> >> Hi, any progress on this? > > > you likely gain more when you don't lack the context > > there is no single message with subject "Rstudio" in the archive and even if > - you can't demand others to seek around because you don't write a proper > reply with a quote On Devel mailing list web interface, discussion https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/AJ44JDERYQMY6MIMFCKQEZL75JEHISQL/ I clicked on "Reply" button under message by Mukundan Ragavan written on Monday, 4 April 7:05 a.m. which permanent link is https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JEAIXT4XUKPVZUKSNOS6MDYHTWC6KP4S/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Packaging wiki: shortcoming in Github Source0 (?)
Thank you ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Packaging wiki: shortcoming in Github Source0 (?)
I think I have found a shortcoming in https://fedoraproject.org/wiki/Packaging:SourceURL#Commit_Revision Github line, which is Source0: https://github.com/OWNER/%{name}/archive/%{commit}/%{name}-%{shortcommit}.tar.gz but I am not sure, so I have not made any edit to the wiki page. In my case I am packaging bettercap-ng with the following attributes commit eb1a53efa3171aefed0ec9766d8c5047bd0df289 shortcommit eb1a53e rpmbuild parser will translate Source0 into https://github.com/evilsocket/bettercap-ng/archive/eb1a53efa3171aefed0ec9766d8c5047bd0df289/bettercap-ng-eb1a53e.tar.gz but if you try inserting such URL in your browser, Github will return a file named bettercap-ng-eb1a53efa3171aefed0ec9766d8c5047bd0df289.tar.gz instead of bettercap-ng-eb1a53e.tar.gz so if you run locally $ rpmbuild -bs rpmbuild/SPECS/bettercap.spec you will obviously get error: File /home/user/rpmbuild/SOURCES/bettercap-ng-eb1a53e.tar.gz: No such file or directory. Therefore I think wiki line Source0: https://github.com/OWNER/%{name}/archive/%{commit}/%{name}-%{shortcommit}.tar.gz should be changed into Source0: https://github.com/OWNER/%{name}/archive/%{commit}/%{name}-%{commit}.tar.gz Am I right? Best regards ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Clean up your spec files
Miroslav thank you for the hints, I will check my packages, but I think Igor Gnatenko already removed such stuff because he made a quick review of them. I would also say that we should increase the usage of *comments* in spec files because they are very useful for new packagers ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Help for fixing %install spec file section (Error make: *** No rule to make target 'install'. Stop.)
Hi there, I working on packaging the last missing (on Fedora repos) piece of user side Estonia ID card software stack: the web extension[1] for web signing I need some help in fixing %install section of spec file https://pagure.io/webextension-token-signing_spec/blob/master/f/webextension-token-signing.spec because during builds [2] I am getting error message make: *** No rule to make target 'install'. Stop. I made various change attempts but I could not manage to fix it. Best regards [1]: https://github.com/open-eid/chrome-token-signing [2]: https://copr.fedorainfracloud.org/coprs/germano/webextension-token-signing/build/721284/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Help for fixing %install spec file section (Error make: *** No rule to make target 'install'. Stop.)
Il 26/02/2018 20:09, Jens Lody ha scritto: > Did you try "make -C host-linux install DESTDIR=%{buildroot}" in > %install ? Thank you! Now compilation starts at least! [...] Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.s3F6YN + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/webextension-token-signing-1.0.6-1.fc27.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/webextension-token-signing-1.0.6-1.fc27.x86_64 ++ dirname /builddir/build/BUILDROOT/webextension-token-signing-1.0.6-1.fc27.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/webextension-token-signing-1.0.6-1.fc27.x86_64 + cd chrome-token-signing-1.0.6 + make -C host-linux install DESTDIR=/builddir/build/BUILDROOT/webextension-token-signing-1.0.6-1.fc27.x86_64 make: Entering directory '/builddir/build/BUILD/chrome-token-signing-1.0.6/host-linux' make -f Makefile install make[1]: Entering directory '/builddir/build/BUILD/chrome-token-signing-1.0.6/host-linux' /usr/lib64/qt5/bin/qmake -install qinstall -exe chrome-token-signing /usr/bin/chrome-token-signing Error copying chrome-token-signing to /usr/bin/chrome-token-signing: Cannot create /usr/bin/chrome-token-signing for output make[1]: [Makefile:421: install_target] Error 3 (ignored) strip /usr/bin/chrome-token-signing strip: '/usr/bin/chrome-token-signing': No such file make[1]: [Makefile:422: install_target] Error 1 (ignored) mkdir: cannot create directory '/etc/opt/chrome': Permission denied make[1]: *** [Makefile:430: install_hostconf] Error 1 make[1]: Leaving directory '/builddir/build/BUILD/chrome-token-signing-1.0.6/host-linux' make: Leaving directory '/builddir/build/BUILD/chrome-token-signing-1.0.6/host-linux' make: *** [GNUmakefile:32: install] Error 2 Build: https://copr-be.cloud.fedoraproject.org/results/germano/webextension-token-signing/fedora-27-x86_64/00721343-webextension-token-signing/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
nextcloud-client 2.5: help for updating qt syslibs patch
Hi there. I am testing nextcloud-client 2.5 beta 1 [0], and I am in troubles with syslib patch[1]. This patch has been produced some time ago by previous owncloud-client maintainers, and I simply replicate it on every new release of the software client. By the way, on 2.5.0 this patch triggers some compilation errors [2] [3], whereas disabling the patch on compilation time, lets the compilation to be successfully completed [4]. Concerning the errors in [2][3], I made some attempts of fixing connect(this, ::QtSingleApplication::messageReceived, this, ::slotParseMessage); put they only leaded to more deeper errors. Since I am not very confident with qt libs, I am looking for some suggestions about how to improve the patch file Thank you for your time [0]: https://copr.fedorainfracloud.org/coprs/germano/nextcloud-client-2.5 [1]: ** old version, for newer look at copr 2.5.0 srpm** https://src.fedoraproject.org/rpms/nextcloud-client/blob/master/f/nextcloud-client-2.4.0-syslibs.patch [2]: https://copr.fedorainfracloud.org/coprs/germano/nextcloud-client-2.5/build/788770/ [3]: https://copr-be.cloud.fedoraproject.org/results/germano/nextcloud-client-2.5/fedora-28-x86_64/00788770-nextcloud-client/build.log.gz [4]: https://copr.fedorainfracloud.org/coprs/germano/nextcloud-client-2.5/build/788739/ (temporarily disabled nextcloud-client-icon.patch too) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CUJBHKFLX5HMRQBCLFNWGDCQLFPD57JQ/
Re: nextcloud-client 2.5: help for updating qt syslibs patch
During past weeks, co-maintainer FAS nonamedotc has made some other attempts to fix the problem, but he had no success. Can anybody please provide some hints about how we could proceed? Thank you very much ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: audiofile package to become an orphan
If upstream is no longer maintaining it, in my opinion you should evaluate to remove it from Fedora repository: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/QUZUX75QA6ZGQHHMUQ5SFGULLXQ7RJG4/
Re: Errors in compiling darktable subpackages
On 7/19/18 10:15 PM, Fabio Valentini wrote: > I used to get these errors too for some of my packages. It turned out > that upstream made some mistakes in their CMakeLists.txt files: > The errors were usually caused by some CMakeLists.txt file overriding > the system-provided CFLAGS with something else, instead of only > appending necessary flags. Thank you for your hint. I am also looking at OpenSUSE version of darktable spec file [1] but I find it very difficult to read with all of those macros etc. [1]: https://build.opensuse.org/package/view_file/home:darix:darktable:master/darktable/darktable.spec?expand=1 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/S7QMBAPY6XPKGLK5SURP2KG3VSOCVZN7/
Re: Errors in compiling darktable subpackages
A user in darktable mailing list [1] said "If you are using -specs=/usr/lib/rpm/redhat/redhat-hardened-ld at link time, you also need to use -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 at compile time, and as you are compiling and linking at the same time, you need either both, or drop the -specs=/usr/lib/rpm/redhat/redhat-hardened-ld." so I am starting investigating about redhat-hardened usage [1]: https://www.mail-archive.com/darktable-dev@lists.darktable.org/msg03229.html ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ULRE3NNOZLCAEQUBNI3HFDRYQHSCXFD7/
Re: Errors in compiling darktable subpackages
A little update: upon FAS misc suggestion I started trying to comment from line 5 to 15 of file https://github.com/darktable-org/darktable/blob/darktable-2.4.x/tools/basecurve/CMakeLists.txt and then the previous error seems to be disappeared. https://copr.fedorainfracloud.org/coprs/germano/darktable_2_4/build/779751/ Now I am investigating about how to fix the other CMakeLists errors ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/MBO4UVXOFAJ2A72NPTKS7VZMTCHUHGKI/
Errors in compiling darktable subpackages
I am working on adding more features to darktable (basecurve tool and noise tool subpackages). In log [1] from line BUILDSTDERR: /usr/bin/ld: CMakeFiles/dt-curve-tool.dir/dt-curve-tool.c.o: relocation R_X86_64_32S against symbol `spline_set' can not be used when making a shared object; recompile with -fPIC there are many errors, and I don't understand if they are upstream programming errors or more likely errors in my spec file. Build URL is https://copr.fedorainfracloud.org/coprs/germano/darktable_2_4/build/779148/ Thank you for your time [1]: https://copr-be.cloud.fedoraproject.org/results/germano/darktable_2_4/fedora-28-x86_64/00779148-darktable/build.log.gz ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/MAALXQOLRTKJVLMKDCDLFBJZFMCJLB5Z/
Re: Fixing KeepassXC missing Gnome tray icon
On 7/18/18 9:57 PM, Robert-André Mauchin wrote: > Also if you're looking to fix your FTBFS after the mass rebuild, look at this > bug > https://github.com/keepassxreboot/keepassxc/issues/2048 Thank you! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AX4YO6R3PIC464CTSYWMCWN6E75MTDUI/
Understanding popd pushd usage in RPM spec file
Hi, I need some help in understanding how popd and pushd work in rpm files creation. Today I started working on enhancing darktable spec file [1] in order to add basecurve-tool and noise-tool subpackages, and I had some difficulties in understanding popd/pushd usage in that spec file. Despite is a package that I maintain, the popd/pushd usage has been implemented by past Fedora maintainers. I have spent the afternoon searching on internet and reading again the guide https://rpm-packaging-guide.github.io/ and I also made some practise after having read StackOverflow question [2], but I still do not get it. Thank you for your time [1]: https://src.fedoraproject.org/rpms/darktable/blob/f28/f/darktable.spec [2]: https://unix.stackexchange.com/questions/77077/how-do-i-use-pushd-and-popd-commands ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/3JSTVEJP4XASQEWNWFRSG77ABMFEK3EG/
Fixing KeepassXC missing Gnome tray icon
A user filled the following bugreport https://bugzilla.redhat.com/show_bug.cgi?id=1601033 concerning KeepassXC from Fedora repository missing the Gnome tray icon. He states that the upstream AppImage build instead is not affected by this problem. The spec file seems to be fine so I don't understand where the problem could be. Best regards ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/QLFN3SHC6VOCD5QGPHCKQJGJ3KHHVLVE/
Re: nextcloud-client 2.5: help for updating qt syslibs patch
On 8/29/18 1:40 PM, Rex Dieter wrote: Germano Massullo wrote: During past weeks, co-maintainer FAS nonamedotc has made some other attempts to fix the problem, but he had no success. Can anybody please provide some hints about how we could proceed? Consider just using the bundled versions? That was our last resort ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org