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
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
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
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
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:
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
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
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
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
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
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]:
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
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
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
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:
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:
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
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.
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
===
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
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
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
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
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" exi
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
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
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
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
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 i
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
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.
>
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
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
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
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
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
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]:
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
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
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
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
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
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
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
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
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
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
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
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
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 --
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
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"
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
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
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
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
Review request has been taken
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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 i
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
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
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
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
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
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
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
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
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 he
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
Welcome!!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
# 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
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
> 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
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
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
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:
Welcome Sly!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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
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
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
>>>
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
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
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:
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
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
Thank you
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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
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
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
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
+ '['
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
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 --
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
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
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
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.
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
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 --
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
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
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
1 - 100 of 252 matches
Mail list logo