On 2020-09-26 1:51 a.m., Germano Massullo wrote:
Il 26/09/20 03:03, Luya Tshimbalanga ha scritto:
On 2020-09-25 12:53 p.m., Germano Massullo wrote:
I apologize, this happened because F33 was branched in the same days I
was building darktable. I must have missed the announcement.
Anyways
Il 26/09/20 03:03, Luya Tshimbalanga ha scritto:
>
> On 2020-09-25 12:53 p.m., Germano Massullo wrote:
>> I apologize, this happened because F33 was branched in the same days I
>> was building darktable. I must have missed the announcement.
>> Anyways for any problem re
On 2020-09-25 12:53 p.m., Germano Massullo wrote:
I apologize, this happened because F33 was branched in the same days I
was building darktable. I must have missed the announcement.
Anyways for any problem related to a package users should leave a
comment on bugzilla rather than the mailing
I apologize, this happened because F33 was branched in the same days I
was building darktable. I must have missed the announcement.
Anyways for any problem related to a package users should leave a
comment on bugzilla rather than the mailing list
On Thursday, September 24, 2020 11:15:36 PM PDT Johannes Lips wrote:
> In defense of the maintainers, these build dates are right around f33
> branching on August 11th, so perhaps that is the reason, why they've missed
> f33.
Which is precisely why I said:
On Thu, 2020-09-24 at 14:41 -0700,
On Thursday, September 24, 2020 11:39:51 PM PDT Luya Tshimbalanga wrote:
> I initially planned to file a bug report but it was already
> automatically done on
> https://bugzilla.redhat.com/show_bug.cgi?id=1863394 and
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED
>
On 2020-09-24 6:00 p.m., Erich Eickmeyer wrote:
This type of question really needs to be a bug report against the
darktable package, not a conversation in this list. Looks like @madko
is listed as the maintainer and @germano was the last person to build
push an update, but neglected F33
In defense of the maintainers, these build dates are right around f33 branching
on August 11th, so perhaps that is the reason, why they've missed f33.
johannes
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
a 32 to 33 beta, I notice Darktable is on
> 3.0. 3.2.1-1.fc32. Will it be possible to push to the latest
> version before Fedora 33 release?
>
Looks to me like whoever did the build forgot to do the bohdi update
for 33, probably because it had branched just prior to that update.
Do w
On Thu, 2020-09-24 at 14:41 -0700, Erich Eickmeyer wrote:
>
>
> On Thu, Sep 24, 2020 at 2:39 pm, Luya Tshimbalanga <
> l...@fedoraproject.org> wrote:
> >
> > When upgrading from Fedora 32 to 33 beta, I notice Darktable is on
> > 3.0. 3.2.1-1.fc32. Will
On Thu, Sep 24, 2020 at 2:39 pm, Luya Tshimbalanga
wrote:
When upgrading from Fedora 32 to 33 beta, I notice Darktable is on
3.0. 3.2.1-1.fc32
<https://koji.fedoraproject.org/koji/buildinfo?buildID=1587996>. Will
it be possible to push to the latest version before Fedora 33 r
When upgrading from Fedora 32 to 33 beta, I notice Darktable is on 3.0.
3.2.1-1.fc32
<https://koji.fedoraproject.org/koji/buildinfo?buildID=1587996>. Will it
be possible to push to the latest version before Fedora 33 release?
Thanks
--
Luya Tshimbalanga
Fedora Design Team
Fedora Design
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
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
th 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:m
On Thu, Jul 19, 2018 at 9:28 PM Germano Massullo
wrote:
>
> 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:
> relocat
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
Il 03/01/2018 10:25, Anssi Johansson ha scritto:
> Please upgrade to SL 7.4 and see if the problems persist. darktable in
> EPEL was compiled in RHEL 7.4.
Exactly!
// darktable co-maintainer here :-)
___
epel-devel mailing list -- epel
Patrick Daegelen kirjoitti 3.1.2018 klo 11.02:
Hi everybody,
I've just tried to install darktable-2.0.7-3.el7 from EPEL with yum
under SL 7.3.
I get the following error message :
dt_gui_gtk_init: error parsing /usr/share/darktable/darktable.css:
darktable.css:30:15Missing name of pseudo
Hi everybody,
I've just tried to install darktable-2.0.7-3.el7 from EPEL with yum
under SL 7.3.
I get the following error message :
dt_gui_gtk_init: error parsing /usr/share/darktable/darktable.css:
darktable.css:30:15Missing name of pseudo-class
darktable: symbol lookup error:
/usr
https://bugzilla.redhat.com/show_bug.cgi?id=1381507#c9
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Other feedbacks?
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
so, and I have never seen a new 1.x release since
darktable 2.x has been released
> * Are there any known 1.x security issues?
No
> * Is the upgrade from 1.x to 2.x transparent for the user? ie, would
> they have to do any manual steps to move config? or is that all done
> by
On Tue, Oct 25, 2016 at 11:07:28AM -0600, Kevin Fenzi wrote:
> Well, we need more information (or at least I do):
> * Is 1.x still supported by upstream?
I don't think so -- the last commit to the "darktable-1.6.x" branch is
just over a year ago, Oct 21, 2015.
> * Are
Just fixed the problem (thank you Rex Dieter) and built 2.0.3
https://copr.fedorainfracloud.org/coprs/germano/Darktable_2.0_release_candidate/build/172878/
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
sorry. i'm looking now and it's broken.
mine is working:
https://copr.fedorainfracloud.org/coprs/ploeffler/darktable2/
On 03/08/2016 08:34 AM, Germano Massullo wrote:
darktable 2.0.2 successfully built for EPEL 7 on my Copr repository:
https://copr.fedorainfracloud.org/coprs/germano
On Tue, Mar 1, 2016 at 1:50 PM, Peter Loeffler <peter.loeff...@guruz.at>
wrote:
> Hi,
>
> it's my first time doing this. So please be patient.
>
> I have built Darktable 2.0.1 for RHEL/CentOS 7.
> The repo can be found here:
> https://copr.fedorainfracloud.org
= Proposed Self Contained Change: Darktable 2.0 =
https://fedoraproject.org/wiki/Changes/Darktable_2_0
Change owner(s):
* Germano Massullo
Update Darktable to new 2.0 major release
== Detailed Description ==
Darktable is one of the most important photo editing software in the
whole FOSS world
Il 09/11/2015 21:46, Stephen John Smoogen ha scritto:
> On 9 November 2015 at 13:30, Germano Massullo
> <germano.massu...@gmail.com> wrote:
>> Hi, I am one of the Darktable maintainers.
>> Darktable 2.0 is going too be released soon. According to EPEL policies, I
>>
On 9 November 2015 at 13:30, Germano Massullo
<germano.massu...@gmail.com> wrote:
> Hi, I am one of the Darktable maintainers.
> Darktable 2.0 is going too be released soon. According to EPEL policies, I
> could not release such major release for EPEL/RHEL 7.
> Do you usual
Hi, I am one of the Darktable maintainers.
Darktable 2.0 is going too be released soon. According to EPEL policies, I
could not release such major release for EPEL/RHEL 7.
Do you usually apply this rule strictly or sometimes you make an exception?
New version of Darktable will rely on GTK3
Please be careful, rewriting history (and changelog entries).
-- rex
madko wrote:
commit 7cbe3221ef9411bb258c6d65b7f00f0de557c380
Author: Edouard Bourguignon ma...@linuxed.net
Date: Sat Mar 9 13:57:43 2013 +0100
Upgrade to 1.1.4
...
@@ -114,11 +115,11 @@ gtk-update-icon-cache
Hi!
Would anybody like to make a review (sponsor needed) on darktable?
https://bugzilla.redhat.com/show_bug.cgi?id=589866
Dmitrij.
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman
Hello!
2010/9/10 Dmitrij S. Kryzhevich kr...@land.ru:
Hi!
Would anybody like to make a review (sponsor needed) on darktable?
https://bugzilla.redhat.com/show_bug.cgi?id=589866
Taking this.
--
With best regards, Peter Lemenkov.
--
devel mailing list
devel@lists.fedoraproject.org
https
34 matches
Mail list logo
