Bug#1070405: darktable: Please drop unused Build-Depends: libsoup2.4-dev
Jeremy Bícha writes: > Source: darktable > Version: 4.6.1-2 > > Please drop Build-Depends: libsoup2.4-dev . It isn't used at all and > we would eventually like to remove libsoup2.4 from Debian. > > Thank you, > Jeremy Bícha How can I verify that it is not used? d
Bug#682397: darktable: recommend opencl package
Tino Mettler via Pkg-phototools-devel writes: > > This is a general issue that the darktable package can not change. So > I propose to close this bug. > > Regards, > Tino I wonder if having the bug helps people see that there is no point in filing more bugs on the same topic. I guess we can always leave the next OpenCL bug open if that occurs.
Bug#1057472: darktable: diff for NMU version 4.4.2-1.1
Boyuan Yang writes: > I've prepared an NMU for darktable (versioned as 4.4.2-1.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. As long as you are prepared to deal with any fallout, go ahead. In any case I doubt there are very many darktable users on arm64. > I am disabling the OpenMP support for now on arm64 so that it does not > block library transitions indefinitely. Currently it blocks the completion > of libavif transition, and transitively blocks jpeg-xl transition from > starting, etc. For a full list of blocked transition, check information on > https://tracker.debian.org/pkg/darktable . I don't think we should delay it > any longer given that no signs of bug solving is currently visible. Well, take that up with the gcc maintainer, since that is where the (fixed upstream) bug is.
Bug#1055601: darktable: Segfault in first run after system hang
Control: tag -1 wontfix Greg Schmidt writes: > Package: darktable > Version: 4.4.2-1+b1 > Severity: normal > X-Debbugs-Cc: g...@desk1.attlocal.net > > Dear Maintainer, > > I was using darktable when my system hung. I had to reboot to recover. After > the reboot I started darktable and > it segfaulted. A backtrace was created which implicated dlopen. It was > attempting to load "libMesaOpenCL.so.1". > A subsequent start of darktable was normal. Hi Greg; This looks OpenCL related. I don't have a working OpenCL setup, so I can't help you there (even if the problem was reproducible). If you find a way to reproduce it, feel free to report a bug to upstream darktable on github including the output of darktable -d common.
Bug#1053661: [Miloš Komarčević] Re: [darktable-org/darktable] imageio: adjust for libavif 1.0.0 API change (PR #15128)
--- Begin Message ---
I think we only need the following CMake change on 4.4.x branch, the source
code changes only apply to 4.6:
```
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index e3eaa697fe..5cb3bf9fd8 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -353,16 +353,22 @@ if(USE_WEBP)
endif(USE_WEBP)
if (USE_AVIF)
-find_package(libavif 0.8.2 CONFIG)
-if (TARGET avif)
-list(APPEND LIBS avif)
-add_definitions(-DHAVE_LIBAVIF=1)
-list(APPEND SOURCES "imageio/imageio_avif.c")
-set(DT_SUPPORTED_EXTENSIONS ${DT_SUPPORTED_EXTENSIONS} avif CACHE
INTERNAL "")
+ # no version check in config mode because of major only match policy
+ find_package(libavif CONFIG)
+ if (TARGET avif)
+if(libavif_VERSION VERSION_GREATER_EQUAL 0.8.2)
+ list(APPEND LIBS avif)
+ add_definitions(-DHAVE_LIBAVIF=1)
+ list(APPEND SOURCES "imageio/imageio_avif.c")
+ set(DT_SUPPORTED_EXTENSIONS ${DT_SUPPORTED_EXTENSIONS} avif CACHE
INTERNAL "")
+else()
+ set(libavif_FOUND NOTFOUND)
endif()
+ endif()
endif()
if(USE_HEIF)
+ # no version check in config mode because of exact match policy
find_package(libheif CONFIG)
if(NOT TARGET heif)
find_package(libheif 1.13.0 MODULE)
@@ -373,7 +379,7 @@ if(USE_HEIF)
add_definitions(-DHAVE_LIBHEIF=1)
list(APPEND SOURCES "imageio/imageio_heif.c")
set(DT_SUPPORTED_EXTENSIONS ${DT_SUPPORTED_EXTENSIONS} heif heic hif
CACHE INTERNAL "")
- if(NOT TARGET avif)
+ if(NOT libavif_FOUND)
# libheif can handle avif, too
set(DT_SUPPORTED_EXTENSIONS ${DT_SUPPORTED_EXTENSIONS} avif CACHE
INTERNAL "")
endif()
```
I'll let @TurboGit decide if he wants to commit this to the branch...
P.S. Arch e.g. already patched this in a more minimal way:
https://gitlab.archlinux.org/archlinux/packaging/packages/darktable/-/commit/9826742182bf9ebf8c8ea3c51f0545a60bcdec23
--
Reply to this email directly or view it on GitHub:
https://github.com/darktable-org/darktable/pull/15128#issuecomment-1752830715
You are receiving this because you commented.
Message ID: --- End Message ---
Bug#1053661: darktable: no longer detects libavif
Control: tag -1 upstream Sebastian Ramacher writes: > Source: darktable > Version: 4.4.2-1 > Severity: normal > X-Debbugs-Cc: sramac...@debian.org > > After the rebuild for the libavif transition, darktable is no longer > built with libavif support: > This seems to be work in progress upstream. I don't know if the following patch(s) apply to 4.4.2, but they claim to fix the issue. https://github.com/darktable-org/darktable/pull/15128
Bug#1053405: darktable: FTBFS on arm64 (gcc bug?)
Gianfranco Costamagna writes: > Source: darktable > Version: 4.4.2-1 > Severity: serious > forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677 > tags: ftbfs > Do you think maybe there should be a debian gcc bug? after all, the distinction you point to is a difference of debian version. d
Bug#1053188: darktable removed at each apt full-upgrade
David Bremner writes: > Control: tag -1 unreproducible > Thierry told me off list that the problem went away after an upgrade, so I'll close the bug for now. Feel free to reopen (ideally with the apt debugging info above) if the problem resurfaces. d
Bug#1053188: darktable removed at each apt full-upgrade
Control: tag -1 unreproducible Thierry Dumont writes: > Package: darktable > Version: 4.4.2-1 > Severity: important > X-Debbugs-Cc: tdumon...@free.fr > > Dear Maintainer, > > On debian testing: > * apt update foloweb by apt full-upgrade: package darktable is removed (not > upraded, but removed). > * But darktable is always available in packages list, anc can be re-installed > by typing: apt install darktable. > * This appeared on 2023/09/28. I can't reproduce this. There have been no recent obvious changes to state of darktable in testing, unless you haven't updated for a month (it migrated to testing on 2023-08-25). Your issue might have something to do with your apt configuration. Here is the apt debugging hint from the #debian IRC channel. To diagnose your problem, we need ALL OF THE FOLLOWING information: 1. complete output of your apt-get/apt/aptitude run (including the command used) 2. output from "apt-cache policy pkg1 pkg2..." for ALL packages mentioned ANYWHERE in the problem, and 3. "apt-cache policy". Ideally run the commands with LANG=C, so that the error messages are in English. I can read French (well enough for this), but others trying to read the bug log may not be able to. d
Bug#1050349: libimath-dev: CMake fails because of missing python bindings
Package: libimath-dev Version: 3.1.9-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I was trying to update darktable, which uses libimath, and got the following build failure (which went away when I added python3-imath to the build-depends). It seems like a bug in the the CMake files for imath? - -- CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115 (message): The imported target "Imath::PyImath_Python3_11" references the file "/usr/lib/x86_64-linux-gnu/libPyImath_Python3_11-3_1.so.29.8.0" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake:40 (include) src/CMakeLists.txt:311 (find_package) - -- Configuring incomplete, errors occurred! cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt - -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libimath-dev depends on: ii libimath-3-1-29 3.1.9-2 libimath-dev recommends no packages. libimath-dev suggests no packages. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmTiIkAACgkQA0U5G1Wq FSGAxA//f8ZspvLPnSGZcgTsuYO0GJLSY/l6i7HmHh7VPsksZYJhLD91hAKrDX3u Lpyh0Bf8YtZ1Ue+8W/Bq/dqRtro6wbxXayRUKJeKVuQwjbeqmlM3nJ5RfSzJroe7 7WkIThGRITMMmocAtCI8shjyEAJlFH0fbk9jeRA7f3djiyj0jB6E/PwB+N4FosUA WIwITZv5fpwYM4jJHSvUNFvbs0WYcnyO6Te2PJDjAodOk+UCcfSagc0lWvbXsDrv BGz747JY9dimI9UVGaaaRk4u7p2y5EStbDpq/vmgWudz/aV9Gyp204uDnYkKmXDM vgy2+Ub7BNy63+/+breS/2iTl3mWUOYG6+nV1AH1dj1IOnK11YPGfcrUpFgB4OTK mJqIICEv/dgLrxy6TJfFrUSgAYjnQViHvPvjgi2t/HJW4hVMoqvDhrczd29MXv2q 8xvD0sj7tHKLTaMFP5l51kVrHSOCEx/bhJvOQ1z4FkgVZpFjs0tY1WDJ8N0qruwy vOAEH2O1qTRcWvCHzY5hFiWBLT+HfIVd/DBk1JQ7FT9Qv/gv+cOfL+9Q6UNY81j2 xS1mC3JLx+nc+YXGXl4LfN/YRUbYeD4JRpin5eQIOVO6VLg61+lo4NIliRqXhaNO s+hQAlwgg/+SLLFL+HPvh/uBq4JeIZBvSqjkxKSdreHagvnf0E4= =cbqu -END PGP SIGNATURE-
Re: Darktable package status
Thierry Florac writes: > Hi, > > Darktable 4.4 was released in June, but I don't see any evolution on Debian > package status since release 4.2.1. > Is there any planning for Darktable integration in the last Debian testing > release? > Would you need any help for this integration? I'm aware of the new version. I just need to find time to do the update. I don't think there's anything you (or the person who filed the wishlist bug) can do to speed that up, unless some experienced debian packager wants to take over maintaining Darktable in Debian. d
Bug#1039119: darktable: use packaged lua
roucaries bastien writes: > > Yes in your case i cheched by grepping thé build log. Lua ils compiléd what > why i set rc severity. I suspect that you saw a different package with Lua in the name, namely LuaAutoC. The embedding of that library is a bug, but I'm not sure there's any practical benefit to filing it since it is not packaged seperately in Debian, and darktable is afaik the only package using it. Personally there are higher priority issues with darktable, in particular the embedding of LibRaw (which is already tracked by it's own bug iirc).
Bug#1039119: darktable: use packaged lua
Bastien Roucariès writes: > Source: darktable > Version: Use packaged lua > Severity: serious > Justification: embded code copy > > Dear Maintainer, > > It appear that your package embded and compile lua > > Could you: > - use the packaged lua lib > - repack in order to avoid accidental reintroduction of compiling lua > > rouca Since upstream already checks for the system lua (unless that changed) repackaging seems unecessary. Do you have some evidence (build logs ?) that the build is not using the system lua? d
Bug#1034509: Acknowledgement (darktable: Crashes when scrolling through a collection)
Michael Below writes:
> Darktable should take more care in handling its input data. If data (in
> the XMP file?) is broken, darktable should discard the invalid input
> data. Anyhow, no kind of input data should lead darktable to a
> segmentation fault ("Speicherzugriffsfehler").
>
> I am attaching the XMP file.
Can you also provide (somehow, presumably not by email) the RAF file?
I'm afraid static analysis of XMP files is not likely to yield much
information.
Failing that you could try to generate a backtrace; I believe there are
instructions on darktable.org.
d
Bug#1033213: unblock: darktable/4.2.1-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: darkta...@packages.debian.org
Control: affects -1 + src:darktable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package darktable
[ Reason ]
This upload fixes bug #1033001
[ Impact ]
Although the bug is arguably cosmetic (it relates to whether GNOME
displays the correct icon in certain places), it does affect all
darktable users on Wayland, who will presumably be a large fraction of
it's users, as darktable is widely used by non-programmers.
[ Tests ]
I have installed the new package in a clean Bookworm VM and verified
it fixes the bug as claimed. I also installed it on my development
machine (not running GNOME) and verified basic functionality.
[ Risks ]
darktable is a leaf package. The change introduced by this file is a
single line added to a .desktop file
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
The one line upstream change is a bit hard to spot in the debdiff (at
least for me), so I will also attach the actual patch.
unblock darktable/4.2.1-4
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmQXlNMACgkQA0U5G1Wq
FSG4axAArjJPzP+ohn9w4KUWe4b2WyW//Pxvu6SdEWKSLB+Q3v/UXVgYD7/C1cY0
NTQ9D4opqSh3ihgvvFRkq1UwnJ/qxOfQMeuvf2d5LCUyuuxfp6kKXCHmCuGWxc9T
vIkjfemZkqI4F0TlNEjdL3DP64f+zonkJNo2oRDmmyQoesSHwP5MI08B+TMiV8N6
mi1zxY5rS1EyOEpXOIvEazSWe94TqcjHNHQzinQ3qU7kEBvfiRPUcuTWSD9+uBE/
mr5VhFBHVQSXW7TfTn4IIqB9m25SXHNBcoHlPr0R1oVNgOgdoSkWru3A9NFCfxq8
UyWRZmuZLLLHOrwU5aYWP6LpiuLCY/brhvyq98kaf7O5gIrNp9zP+WQbsgCUO8df
dQx4O63UBpAxT8UiEw6fDraO7uc+dpnL5sRZr5xSfuk7fyorhHt0VB9t44iLESn5
Ca1Rp0A5/XpmiuWO4hA3cDNpM8PTxq5WnmIOXkVZPV9HykgYe+WHi/im+/ZMOHX8
tr7J3SjyWHO6Qf3EvUSxEu9b9onqwsnt324VF37c7dusCmdI2nxjKyVRphPMrkyB
wiVV1ka1s9L48xaEAp8KaQmdaVG+GohAAucfs/4K6p05PfURwvhT9Gof5lSswvmp
JBMQv/a3ZvukqivKb28qPosZV5N72ORQ9z3tppFwyaB4mnqDId4=
=atQJ
-END PGP SIGNATURE-
diff -Nru darktable-4.2.1/debian/changelog darktable-4.2.1/debian/changelog
--- darktable-4.2.1/debian/changelog2023-02-27 08:03:27.0 -0400
+++ darktable-4.2.1/debian/changelog2023-03-19 14:10:18.0 -0300
@@ -1,3 +1,10 @@
+darktable (4.2.1-4) unstable; urgency=medium
+
+ * Cherry-pick upstream commit 385aacf61e55903bb064e0fe99a1d138645f697c:
+add StartupWMClass=darktable to .desktop file. (Closes: #1033001).
+
+ -- David Bremner Sun, 19 Mar 2023 14:10:18 -0300
+
darktable (4.2.1-3) unstable; urgency=medium
* Bug fix: "AVIF support is missing in Darktable", thanks to Guy
diff -Nru
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
---
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
1969-12-31 20:00:00.0 -0400
+++
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
2023-03-19 14:10:18.0 -0300
@@ -0,0 +1,21 @@
+From: Victor Forsiuk
+Date: Sat, 18 Mar 2023 13:03:48 +0200
+Subject: Fix missing application icon in Wayland
+
+(cherry picked from commit 385aacf61e55903bb064e0fe99a1d138645f697c)
+---
+ data/org.darktable.darktable.desktop.in | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/data/org.darktable.darktable.desktop.in
b/data/org.darktable.darktable.desktop.in
+index 23bf16c..4d8895b 100644
+--- a/data/org.darktable.darktable.desktop.in
b/data/org.darktable.darktable.desktop.in
+@@ -20,6 +20,7 @@ StartupNotify=true
+
MimeType=application/x-darktable;image/x-dcraw;image/x-adobe-dng;image/x-canon-cr2;image/x-canon-crw;image/x-fuji-raf;image/x-kodak-dcr;image/x-kodak-kdc;image/x-minolta-mrw;image/x-nikon-nef;image/x-nikon-nrw;image/x-olympus-orf;image/x-panasonic-rw;image/x-panasonic-rw2;image/x-pentax-pef;image/x-sony-arw;image/x-sony-sr2;image/x-sony-srf;image/jpeg;image/png;image/tiff;image/x-portable-bitmap;image/x-portable-graymap;image/x-portable-pixmap;image/x-portable-floatmap;image/vnd.radiance;${DESKTOP_MIME_TYPES}
+
+ Icon=darktable
++StartupWMClass=darktable
+
+ X-Unity-IconBackgroundColor=#252525
+
diff -Nru darktable-4.2.1/debian/patches/series
darktable-4.2.1/debian/patches/series
--- darktable-4.2.1/debian/patches/series 1969-12-31 20:00:00.0
-0400
+++ darktable-4.2.1/debian/patches/series 2023-03-19 14:10:18.0
-0300
@@ -0,0 +1 @@
+0001-Fix-missing-application-icon-in-Wayland.patch
commit 6d62433d6ef413116b0ce834798a694427019891
Author: Victor Forsiuk
Date: Sat Mar 18 13:03:48 2023 +0200
Fix missing application icon in Wayland
(cherry picked from commit 385aacf61e55903bb064e0fe99a1d138645f697c)
diff --git a/data/org.darktable.darktable.desktop.in
b/data/org.darktable.darktable.desktop.in
index 23bf16c543..4d8895b234 100644
Bug#1033001: darktable: Missing application icon after launching
There is a relevant pull request upstream: https://github.com/darktable-org/darktable/pull/13961
Bug#1033001: darktable: Missing application icon after launching
Guy Rutenberg writes: > Package: darktable > Version: 4.2.1-3 > Severity: normal > X-Debbugs-Cc: guyrutenb...@gmail.com > > Dear Maintainer, > > Under GNOME (43.3), the Darktable icon is visible when searching for the app, > but once the window is spawned, it is associated with a generic missing icon > (for example in Alt+Tab or the Activities overview). > > The associated wmclass is "darktable", which seems fine. Not sure why the icon > disappears. > > Thanks, > Guy > For the record, this issue is wayland specific. Adding StartupWMClass=darktable to the end of /usr/share/applications/org.darktable.darktable.desktop seems to fix it for me.
Bug#1031790: libraw: CVE-2021-32142
Salvatore Bonaccorso writes: > Source: libraw > Version: 0.20.2-2 > Severity: important > Tags: security upstream > Forwarded: https://github.com/LibRaw/LibRaw/issues/400 > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > Control: fixed -1 0.21.1-1 > > Hi, > > The following vulnerability was published for libraw. The wording for > the CVE description from the feed is disputable, believe this should > be at most DoS. For (naughty) packages that embed libraw, is this worth 1) Trying to squeeze in a minor version update 2) waiting for stable update? 3) not worrying about for bookworm? I know the answer is probably "it depends", just looking for feedback and-or what other maintainers are planning on doing. d
Bug#1031506: darktable: Please adjust the architectures on which darktable is built
David Bremner writes: > Laurent Bigonville writes: > >> Source: darktable >> Version: 4.2.0-2 >> Severity: normal >> >> Hello, >> >> On x32 architecture, darktable FTBFS with the following error: >> >>71 | #error "Unfortunately we only work on the 64-bit architectures >> amd64, ARMv8-A, PPC64 and riscv64." >> >> ATM, I see that ppc64 and riscv64 are not listed in the package >> architectures list. These should maybe be added. >> >> On the other side, x32 should maybe be removed >> > > So x32 is built because of "Arch: any-amd64"? That seems like a bug to > me, but what do I know. So, I see that is really what dpkg-architecture thinks. If I understand correctly your proposal is to replace "any-amd64" with the list of things that are known to work? Sounds a bit tedious, but doable (eventually).
Bug#1031506: darktable: Please adjust the architectures on which darktable is built
Laurent Bigonville writes: > Source: darktable > Version: 4.2.0-2 > Severity: normal > > Hello, > > On x32 architecture, darktable FTBFS with the following error: > >71 | #error "Unfortunately we only work on the 64-bit architectures amd64, > ARMv8-A, PPC64 and riscv64." > > ATM, I see that ppc64 and riscv64 are not listed in the package > architectures list. These should maybe be added. > > On the other side, x32 should maybe be removed > So x32 is built because of "Arch: any-amd64"? That seems like a bug to me, but what do I know. d
Re: Update your package to allow python 3.11.1
Jonathan Krüger via Pkg-phototools-devel writes: > Hi there! > > I was using hugin yesterday and it worked perfectly fine. But after a > update today, it didn't work anymore. So I reinstalled it, but there > was an error, saying that hugin allows only python version 3.11 not > older. > But a guy how knows debian (;D) helped out today, to install the > package. But now, if I try to install a new package, the error message > says, that hugin do not allow python 3.11.1. So please, rebuild the > package and change the requirorments so that I can use it all :) Hi Jonathan; There is some kind of transition going on with hugin and python, so the problem may fix itself in a few days. If not, please report a bug using "reportbug". Maybe your friend can help you configure that if you don't have it set up already. In particular certain crucial information like what version you are trying to install is provided by the reportbug program. d
Re: your changes to darktable on salsa
xiao sheng wen(肖盛文) writes: >> >> In the future, please do not update the compat level without a proper >> commit message that indicates you have test built with the new compat >> level. > The the compat level update is commit automate by @janitor-bot. Yeah, that does not change my opinion. It still needs testing by a human.
Re: your changes to darktable on salsa
David Bremner writes: > > I think the issue there is that you squash merged. Don't do that unless > you construct a decent commit message. In general avoid squash merges in > this repo. Sorry, I misunderstood the output of git log, the original commits are there. Still, I consider upgrading compat to be a major change, and I prefer that a human tests the result.
your changes to darktable on salsa
I have reverted the "fix" to debian/watch. Upstream does not support github's auto generated tarballs. In the future, please do not update the compat level without a proper commit message that indicates you have test built with the new compat level. In general I expect a more useful commit message than "Fix some issues reported by lintian" I think the issue there is that you squash merged. Don't do that unless you construct a decent commit message. In general avoid squash merges in this repo.
[Pkg-phototools-devel] Bug#1019054: Bug#1019054: Bug#1019054: darktable: Darktable does not save Metadata in exported jpgs anymore, even author/copyright entries are gone!
Kerstin Hoef-Emden writes: > c) I opened the wheel and Voreinstellungen, went to the global settings > of the meta data editor. It differed from the older darktable version > in, that no percent symbols were visible (Metadaten-Editor_globale > Einstallung.png). I can double-click on "Alle Rechte" and it offers a > field to type something in. But apparently this is only to give a name > ro a setting, rather than to change a setting. Those are the wrong settings. I agree it's a bit confusing, but click on the hamburger menu (≡) for the export, then choose preferences. On the left you will see a set of checkboxes, including metadata. Make sure the metadata one is selected (see attached). If that doesn't help, try deselecting "develop history". There was an old bug (which is supposed to be fixed) that caused metadata export to fail if the develop history stack got too big. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#1019054: Bug#1019054: darktable: Darktable does not save Metadata in exported jpgs anymore, even author/copyright entries are gone!
Kerstin Hoef-Emden writes: > In oldstable, darktable saved all metadata upon export, even temperature of > the > camera body etc. I expect those data either not to be lost, so I can choose > which ones to delete/maintain with help of exiftool or that the metadata > editor > offers the major spectrum of entries concerning camera settings including > copyright. It would be helpful if you can confirm that the problem is still present in darktable 3.8.0-2~bpo11+1, available from bullseye-backports. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] Reporting Security Vulnerabilities - libopenjp2-7-dev, libopenjp2-7
"Ruelo, Christine M. L. via Pkg-phototools-devel" > Hello libopenjp Maintainers, > > Good day, We have used the libopenjp package and perform a security scan > using Palo Alto Network - Prisma Cloud and these vulnerabilities below are > reported. > We would like to report it and let us know once the fix is available so we > can update accordingly. > > CVE-2022-1122 > CVE-2021-29338 > CVE-2019-6988 > CVE-2021-3575 > > Thank you If you want to find out the security status of a package in Debian, see https://security-tracker.debian.org/tracker/ If you want to report a security problem (at least one with a known CVE) please use the reportbug command, and select the "security" tag at the appropriate time. d signature.asc Description: PGP signature -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] enblend enfuse hugin dependency problem
Emil writes: > enblend enfuse hugin broken in unstable due to > enblend dependecy of libgsl25 (current version is libgsl27) > Please use reportbug to report bugs in unstable. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#1003174: darktable: misses optional dependencies sdl2 and portmidi
Package: darktable Version: 3.8.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Version 3.8 introduces optional dependencies on sdl2 and portmidi. Currently the debian package does not build against these libraries. Presumably some features are also missing. - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages darktable depends on: ii libc62.33-1 ii libcairo21.16.0-5 ii libcolord-gtk1 0.1.26-2+b1 ii libcolord2 1.4.5-3 ii libcups2 2.3.3op2-7 ii libcurl3-gnutls 7.80.0-3 ii libexiv2-27 0.27.3-3.1 ii libgcc-s111.2.0-13 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libglib2.0-0 2.70.2-1 ii libgomp1 11.2.0-13 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgraphicsmagick-q16-3 1.4+really1.3.37-1 ii libgtk-3-0 3.24.31-1 ii libicu67 67.1-7 ii libilmbase25 2.5.7-2 ii libjpeg62-turbo 1:2.1.2-1 ii libjson-glib-1.0-0 1.6.6-1 ii liblcms2-2 2.12~rc1-2 ii liblensfun1 0.3.2-6 ii libopenexr25 2.5.7-1 ii libopenjp2-7 2.4.0-3 ii libosmgpsmap-1.0-1 1.2.0-1 ii libpango-1.0-0 1.48.10+ds1-1 ii libpangocairo-1.0-0 1.48.10+ds1-1 ii libpng16-16 1.6.37-3 ii libpugixml1v51.11.4-1 ii librsvg2-2 2.50.7+dfsg-2 ii libsecret-1-00.20.4-2 ii libsoup2.4-1 2.74.2-3 ii libsqlite3-0 3.36.0-2 ii libstdc++6 11.2.0-13 ii libtiff5 4.3.0-2 ii libwebp6 0.6.1-2.1 ii libx11-6 2:1.7.2-2+b1 ii libxml2 2.9.12+dfsg-5+b1 ii libxrandr2 2:1.5.2-1 ii zlib1g 1:1.2.11.dfsg-2 darktable recommends no packages. darktable suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmHVwjQACgkQA0U5G1Wq FSGo3w/9Fcz8nFDXzdRS2UhBaJGzsRzGGiTJ+Ba81gDmFxwlMW0h54yzVCcP4lrS BfpoEt6pOirm7zXVsnCMkp0rcjul4gmq0PV8ciGyOP6Pw0AqB6CwhV8cptzYntX+ 8izlm0EBUhVFtYF8CJZyUlUP0jHKeDMkzlVMXeN3CEfTUi2bIhSs5itcpU+M6tpQ Chh5zyXYAoCm1/+dmQ9O31VFxe/mnL+BoCRDA+TgKtvtJnPIdOqJP024RkoglzdH PTWoOUNnG5dslpwYe4eKEzjnHfVFUWluUuP0E3mTT4+mBPpXK40EZrfbBjvfTmbC tNsCC5XKr3JyAzGBNGdp94I0qlaNgPAKRzol830stMT58E9PsYgViv1aiDuEc+cu abvEXoVwVwkp7iWwv742Ac1Da4++Ln96iDFDi1krRC+POYeu4o3TpDsUQH5AlqJP D2pEIHhopKdL51ABpC1DL322Xz9lNRoNe6Wuy4gtUKelg/Cule3HVGrw1BKSyNhK Fzp5GpyFiqsICoSc/mq3mW1J6yOmAKojsW4NRSlklOq3zqX5QJarApnPT+vHaHB/ arSrqtpLZI7RxqsygvgfrlyJuBdmyZE4j5bpCxxF73Bk7XoMG3zA1mxadXHC2UH3 zeFjY5LOBm16uoT7utQXs2kYkxjBNAIjedDyTKqiF8X2XjhZUTA= =IbPd -END PGP SIGNATURE- -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] New Darktable release
Sebastian Arnhold writes: > Hey guys, > > I just wanted to remind you that there has been a new release of > Darktable (version 3.8) a few days ago on Christmas. > > Since all Debian packages perpetuate into the upcoming Ubuntu 22.04 LTS > version, which is currently at its development state, a quick packaging > would be greatly appreciated! :) > Hi Sebastian; Although I saw this message, it is probably better to file wishlist bugs for new versions, keeping in mind that "a few days" is really not very long to wait for a package in Debian. Darktable 3.8 is presently in experimental, since it introduced a few issues compared to 3.6. Depending on how long 3.8.1 takes, I may wait for that before uploading to unstable. I'm not an Ubuntu user, and not really interested in putting a lot of effort into supporting Ubuntu, but if there are low effort things that can happen upstream, feel free to file wishlist bugs for those as well. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#1002876: darktable: embeds libraw
Package: darktable Version: 3.8.0-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of version 3.8.0, darkatable is again embedding libraw. I decided to open a new bug rather than reopen #682980, since the situation this time is somewhat different, and I'm not sure anyone getting up to speed on the bug is well served by reading the 100 or so previous messages. Previously (i.e. #682980), darktable was using a forked copy of libraw (although the change was textually small). Currently darktable is using a git submodule of upstream libraw, which means that it is at least possible in principle that upstream will release a sufficiently recent version that we can build against it. Or I guess we could package a git snapshot of libraw in Debian. As far as I understand, the snapshot of libraw is needed for Canon CR3 support. I guess the other thing that has changed since #682980 was closed is that libraw acquired a number of CVEs. Darktable already appears in the embedded copies list for libraw [1], but I'm not sure if "modified-embed" is still the right term. [1]: https://salsa.debian.org/security-tracker-team/security-tracker/raw/master/data/embedded-code-copies - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages darktable depends on: ii libc62.33-1 ii libcairo21.16.0-5 ii libcolord-gtk1 0.1.26-2+b1 ii libcolord2 1.4.5-3 ii libcups2 2.3.3op2-7 ii libcurl3-gnutls 7.79.1-2 ii libexiv2-27 0.27.3-3.1 ii libgcc-s111.2.0-13 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libglib2.0-0 2.70.2-1 ii libgomp1 11.2.0-13 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgraphicsmagick-q16-3 1.4+really1.3.37-1 ii libgtk-3-0 3.24.31-1 ii libicu67 67.1-7 ii libilmbase25 2.5.7-2 ii libjpeg62-turbo 1:2.1.2-1 ii libjson-glib-1.0-0 1.6.6-1 ii liblcms2-2 2.12~rc1-2 ii liblensfun1 0.3.2-6 ii libopenexr25 2.5.7-1 ii libopenjp2-7 2.4.0-3 ii libosmgpsmap-1.0-1 1.2.0-1 ii libpango-1.0-0 1.48.10+ds1-1 ii libpangocairo-1.0-0 1.48.10+ds1-1 ii libpng16-16 1.6.37-3 ii libpugixml1v51.11.4-1 ii librsvg2-2 2.50.7+dfsg-2 ii libsecret-1-00.20.4-2 ii libsoup2.4-1 2.74.2-3 ii libsqlite3-0 3.36.0-2 ii libstdc++6 11.2.0-13 ii libtiff5 4.3.0-2 ii libwebp6 0.6.1-2.1 ii libx11-6 2:1.7.2-2+b1 ii libxml2 2.9.12+dfsg-5+b1 ii libxrandr2 2:1.5.2-1 ii zlib1g 1:1.2.11.dfsg-2 darktable recommends no packages. darktable suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmHN/VYACgkQA0U5G1Wq FSHOnw/+J+O8sR5k+UBBjLLf01STow0Sz8bX+yiSjLTf9p/XYHsFP0t0Ov7iFCco Po+2lprkIuotFo+9114yc5rDgE8MKLctTM98CN6YbM5tMRTtTqUdQFhnty8T+qLO tGlcozdHftzIT9nOKaAPWAVqS0uKNfFVGksHLQIDSJeIBSfn7sZiwYzHyNeXNIft aaEOtrCp8adWq6L2QhIYqSY1C2rfvE41hG/FTkBNkAUB36sdOiBpGy+MRPmxxd3E k/KIP70EBzY0SPdYEAPjE1uMpB8gnNBa8c5A1YDGUzwWfMxx9RYVkIkPvL/PS8uu OzkOc7sWnfZnzhdC6rhLEXxpwTB2GlNxXfrqRd++4c9pLT8rEEJHcmQsxl+NYIpK zV0gRI54TAbsAcLIltoJHDrERruBvgi4GkCQismRFQyvSCn1iECBbvYyiKcOMA+1 iEwPLWaEkJgNlO4ek2IruerSDcP7x2eFgFhWZliQPf+Rm+plbM79arJBVlpRonMf QaELwCsuCgOIXszLV4zg+POBO3hdwNQ1qnUDXyx8OxmWMXeuGDZQB/AlYyMbKv6x Nj8Mk1Tmh7lYE5luBJShw1rdXA5mPd1XFb+3UkNZIeM7WKwMGEeTafxIIyz/fBb0 ULDzzmAD13Uz/7Ufk0laGEAishuvIkZ+jXB0EqhkxkX0IisBj6Y= =zxHR -END PGP SIGNATURE- -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#991381: Bug#991381: darktable: camera not showing in lens correction list and not recognised but is supported
Control: tag -1 moreinfo Stas Zytkiewicz writes: > -- System Information: > Debian Release: bullseye/sid > APT prefers focal-updates > APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 Let me know if the problem can be replicated on Debian. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] ocioconvert crash exporting in PNG when EXR input is multi layer
Dorian Fevrier writes: > Hello maintainers, > > First, thanks for you hard work. > > I hope you will not waste too much time with this one. Please file a bug using reportbug for the package opencolorio-tools. You can pretty much copy your text to the bug report. If you want, you can also file bugs by email, but you need to send to a specific address with some special body text. https://www.debian.org/Bugs/Reporting -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#990405: Bug#990405: darktable: configuring shortcuts breaks filemanager gui at next start filemanager issueVersion: 3.4.1-4
"stef.binde" writes: > Package: darktable > Severity: important > X-Debbugs-Cc: standr...@riseup.net > > Dear Maintainer, > > Configured some custum sho, rtcuts, at next run happens: > * filemanager has no img background anymore, all thumbs are attached to esch > other with no margin → unable to tell which ones are selected > * switching to darkroom and back to lighttable background shows still > darkroom, overlayed with thumbnails. > * deleting ~/.config/darkroom resolves, but no custom shortcuts can be > configured or imported and therefor used. > > see screens attached. Probably this is related to a faulty Italian translation. To test this theory please go to Preferences -> general and clear the content of the bottom text box (which is saved to user.css), and save and apply. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#989222: marked as done (darktable: crashes with "Floating point exception (core dumped)" after loading some DNG files)
Hi Jonas; Can you confirm that the the -4 upload fixes your crashes? d signature.asc Description: PGP signature -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#989222: Bug#989222: Bug#989222: darktable: crashes with "Floating point exception (core dumped)" after loading some DNG files
Jonas Smedegaard writes: > Quoting David Bremner (2021-05-29 14:32:09) >> Jonas Smedegaard writes: >> >> > >> > Upstream tracked and has solved this issue at >> > https://github.com/darktable-org/darktable/issues/8951 >> > >> > At upstream issue tracking is mentioned that the file they used as >> > proof was arguably broken. >> > >> >> Upstream suggests that fix is not easily backportable, > > Oh, wauw - then apparently I did something hard without even knowing it: > I grabbed and applied the patch and it seems to work just fine: > https://source.puri.sm/pureos/packages/darktable/-/commit/19eb57c7bffdca0575f1d526656ca4614f05a33c > > Where do upstream say that? Perhaps they mean backporting further back > than nearest point release, 3.4.1? > They mentioned there was a substantial amount of code deletion. Also, there were 4 commits in that PR; maybe some are harder to backport than others. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#989222: Bug#989222: darktable: crashes with "Floating point exception (core dumped)" after loading some DNG files
Jonas Smedegaard writes: > > Upstream tracked and has solved this issue at > https://github.com/darktable-org/darktable/issues/8951 > > At upstream issue tracking is mentioned that the file they used as proof > was arguably broken. > Upstream suggests that fix is not easily backportable, so the fix likely have to wait until the release of darktable 3.6. If you think its a big issue in practice (I can't judge, I don't use DNG), maybe the release team would consider 3.6 for a bullseye point release (likely to a huge diff). -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#986377: Bug#986377: segfault on startup
Antoine Beaupre writes: > Package: darktable > Version: 3.2.1-3~bpo10+1 > Severity: important probably someone (TM) should upgrade the backport to 3.4.1 before spending much more effort on this. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] upcoming transition for webp package
Jeff Breidenbach writes: > Dear Debian colleagues, > > I'm writing because you maintain a package with a direct dependency in > libwebp6. I'm planning to transition it to libweb8. Although I am not > expecting any compatibility trouble, previous transitions have not always > gone smoothly. So I'm sending this email as a heads up, and I've also just > uploaded libweb8 to experimental. Thank you very much. > > Jeff If you have not already done so, I recommend you discuss this with the release team ASAP as we are in the transition freeze for bullseye. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#978936: darktable: FTBFS on arm64
Package: darktable Version: 3.4.0-1 Severity: serious Tags: upstream Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: -1 forwarded https://github.com/darktable-org/darktable/issues/7583 The new release requires xmmintrin.h in several places, and that include file is only present (in Debian) on amd64. https://buildd.debian.org/status/fetch.php?pkg=darktable=arm64=3.4.0-1=1608929069=0 - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages darktable depends on: ii libc62.31-6 ii libcairo21.16.0-4 ii libcolord-gtk1 0.1.26-2 ii libcolord2 1.4.4-2 ii libcups2 2.3.3op1-3 ii libcurl3-gnutls 7.72.0-1 ii libexiv2-27 0.27.3-3 ii libgcc-s110.2.1-3 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgomp1 10.2.1-3 ii libgphoto2-6 2.5.26-2 ii libgphoto2-port122.5.26-2 ii libgraphicsmagick-q16-3 1.4+really1.3.36-1 ii libgtk-3-0 3.24.24-1 ii libilmbase25 2.5.3-2 ii libjpeg62-turbo 1:2.0.5-1.1 ii libjson-glib-1.0-0 1.6.0-2 ii liblcms2-2 2.9-4+b1 ii liblensfun1 0.3.2-5 ii liblua5.3-0 5.3.3-1.1+b1 ii libopenexr25 2.5.3-2 ii libopenjp2-7 2.3.1-1 ii libosmgpsmap-1.0-1 1.1.0-7 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpugixml1v51.11.4-1 ii librsvg2-2 2.50.2+dfsg-1 ii libsecret-1-00.20.4-1 ii libsoup2.4-1 2.72.0-2 ii libsqlite3-0 3.34.0-1 ii libstdc++6 10.2.1-3 ii libtiff5 4.2.0-1 ii libwebp6 0.6.1-2+b1 ii libx11-6 2:1.6.12-1 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii zlib1g 1:1.2.11.dfsg-2 darktable recommends no packages. darktable suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl/uD6kACgkQA0U5G1Wq FSFD8A/+KlBt0LMrGwiDWI/p56Gcdg5EMMbPMG7G7E1LJBBMSyQ5EhEUjo+TQRhR HRBzfEKPgkYJu+93XvDRVeITJtq9xIL1KTISWgcQRTIC71SDDHGtG7nvJTLVK/fD 7+PnVI3hTPoyNmg2WAK8PtX/TbsOcGNIsx3h173/vonGpL7PUMkhJOWNhH4u/OB8 R7NgusGmji5ylnaPFVNYHII0Ig4r2pBQa7crNiBbCCS7gLMV/BZbp+zbcsnFyLsR Iynu2+I0S0lCHIEbMblwwz68eHoC0cwaJQ6ypcansMT/4v8pYWnByc9U9qZfc8yf g4ZhQKBxofq3GRFY/k+CguIDXub1jBP23WWM7lWZgRL/l0BYQDybPvJ7kqCevDM3 xdJNA2/XZA7M6e0VlNR7V4wuuSaThhUusqE+FZebS2yfCfV2n4QdW74vBDV+E7dP DqexnuS5Xig0lC/PZ5Eg49ZN4k65Qpf945UMjbHzSKNa45m4+wJLigxdvdMXBN0H E0cdYwGecL0WAlzZNUtfLLEYG0zyZxijrWHV3DjysDf3AnxWcuS+3fFoy/aR/oNw niQFX+M21HLUaqpJBTBs3xCZWMvmMK6vbETuWqEzSR18HDKIXnuTCkpNsZ23BnQ7 5OrPfb2eZZUWkfg9fhFS6lgv6Ysk/Liv7FJ9YVrR4V7XKx7m6Ow= =HiaZ -END PGP SIGNATURE- -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] feh 3.1.3-1 has memory leaks, 3.6.1 fixes them
Sam Greadly writes: > Hi there, > > I hope this is the right way - first time doing this and still learning. > > Troubleshooting with the developer, I noticed feh 3.1.3-1 has ~5 memory > leaks. For reference: > > https://github.com/derf/feh/issues/553 > > v3.6.1 fixes those: https://feh.finalrewind.org/ > > I was wondering if you'd consider updating the repository to 3.6.1 so that > we may take advantage of the fixes via apt ? > > Appreciate your help and hope you have a good end of the year! > Hi Sam; It would be great if you could report a wishlist bug (using the reportbug command in Debian) on package feh with the same information in it. That way the request is less likely to get lost. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] darktable 3.2.1-1.1 (Ubuntu 20.04) - unmet dependencies
Volko Neitmann writes: > Dear Debian-Photo-Tools-Maintainers, > > As I successfully installed darktable 3.21 from the OBS PPA on my Linux > Mint 20 (based on Ubuntu 20.04) some time ago, the issue was not present > in the previous darktable 3.2.1 deb-package for Ubuntu 20.04 from OBS PPA. Unfortunately you've been misled, the OBS PPA is not maintained by the Debian phototools team. I think we shared some packaging in the early days, and whoever is running that PPA neglected to change the maintainer address. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] Darktable update issue on Ubuntu 20.04.1
"robert.larnicol (sfr)" writes: > Bonjour, > > https://software.opensuse.org/download.html?project=graphics:darktable:master=darktable > That URL is not maintained by the people on this mailing list. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#969646: Bug#969646: Bug#969646: darktable-cli segfaults directly after start
Control: tag -1 unreproducible. David Bremner writes: > Jan van de Wijdeven writes: > >> Package: darktable >> Version: 3.2.1-3 >> Severity: grave >> Justification: renders package unusable >> >> I run darktable-cli and it immediately segfaults >> > > What about regular darktable, and not on a jpeg? My mistake, I thought you were exporting from a jpeg. In any case I can't reproduce it with the Olympus raws I have lying around. The question of whether you the same problem with non-cli darktable stands. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#969646: Bug#969646: darktable-cli segfaults directly after start
Jan van de Wijdeven writes: > Package: darktable > Version: 3.2.1-3 > Severity: grave > Justification: renders package unusable > > I run darktable-cli and it immediately segfaults > What about regular darktable, and not on a jpeg? d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#969137: Bug#969137: darktable: Histogram not shown
Control: severity -1 wishlist Control: retitle -1 darktable: use default values for empty config settings Fabián Inostroza writes: > I found the issue (with the help of reddit), it was related to the > configuration file. The height of the histogram entry was empty on the > darktablerc file, like this: > plugins/darkroom/histogram/height= > > I put some value (200), opened darktable and the histogram was shown. > Then I tried renaming the darktablerc file and letting darktable > recreate it but it also had the empty histogram height. The only way I can reproduce that is if darktable is open while renaming the file. > Anyway, maybe darktable should use a good default values for empty > entries, at least for the height of the histogram. OK, I've retitled the bug accordingly. > I was using a previous version of darktable, the one that was on the > repositories, maybe that confused some settings. I'm not sure what you mean here. Are you upgrading from a previous version in Debian, or something else? If so, what version. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#969159: darktable: embeds photoswipe
Package: darktable Version: 3.2.1-2+b1 Severity: important Tags: security X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Darktable embeds the photoswipe JavaScript library (https://github.com/dimsemenov/PhotoSwipe) and uses it in exported web galleries). It seems to be an old version :(. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages darktable depends on: ii libc62.31-3 ii libcairo21.16.0-4 ii libcolord-gtk1 0.1.26-2 ii libcolord2 1.4.4-2 ii libcups2 2.3.3-2 ii libcurl3-gnutls 7.68.0-1+b1 ii libexiv2-27 0.27.3-3 ii libgcc-s110.2.0-5 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.64.4-1 ii libgomp1 10.2.0-5 ii libgphoto2-6 2.5.25-3 ii libgphoto2-port122.5.25-3 ii libgraphicsmagick-q16-3 1.4+really1.3.35+hg16297-1 ii libgtk-3-0 3.24.22-1 ii libilmbase25 2.5.3-2 ii libjpeg62-turbo 1:2.0.5-1.1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii libjson-glib-1.0-0 1.4.4-2 ii liblcms2-2 2.9-4+b1 ii liblensfun1 0.3.2-5 ii liblua5.3-0 5.3.3-1.1+b1 ii libopenexr25 2.5.3-2 ii libopenjp2-7 2.3.1-1 ii libosmgpsmap-1.0-1 1.1.0-7 ii libpango-1.0-0 1.46.0-2 ii libpangocairo-1.0-0 1.46.0-2 ii libpng16-16 1.6.37-2 ii libpugixml1v51.10-1 ii librsvg2-2 2.48.7-1 ii libsecret-1-00.20.3-1 ii libsoup2.4-1 2.70.0-1 ii libsqlite3-0 3.33.0-1 ii libstdc++6 10.2.0-5 ii libtiff5 4.1.0+git191117-2 ii libwebp6 0.6.1-2+b1 ii libx11-6 2:1.6.10-3 ii libxml2 2.9.10+dfsg-5+b1 ii libxrandr2 2:1.5.1-1 ii zlib1g 1:1.2.11.dfsg-2 darktable recommends no packages. darktable suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl9I5Q4ACgkQA0U5G1Wq FSFhQw//YPA8EuJFCuMA5FHxTGodkmDGSgzZ/p5KK48oj56BXT2fp6czhb1cy3mT aR44kpSKtfL2tF4q6Qqkr4Foo1tiGpAdDn7fYI/tjIBtxtPeO1mIMEnwHQKbg5Ck VZGdzgclt0xvWi4b3mdm7lEk8ukgVf/qzoi1V6G701NNqVacgFDEG8EDCSTJqWzW me0+Lr3iLnPkPVxtKiMhg25AVXVmBosxa6wv5fL87SlFUBtd+N2pWR+3UOZbkn0C KiLIpmvIKB7JEGhIR4EWWKirNiuZAVbxWhlqITZUjhQPZKN7VNU5112cHuuG4CvS 3GegMO671tHA+E6vBnKlcTxr0DBFSDIjitbYwuzN2B3TOlckVg4AHgqdx7e1y9l8 wQz/abseVX5/g/JsH0doLT9cn93KumM2sw5FH7tJNsAibRq3LMvySNw5ZRvWkkXl xrKhNPSM9zTBcY6OnZu/TqtHbA5VyY9Hvp5DJuFLJnEfZGT7FK818BEVfVwSiOmz 2PkXDoVzOKqRpUZp1eqlkrqVrsI0YRPA2q1ajshWZgVIU+3SitkUfe2ozBHw1wWF t01IX8Uq0LnpZpwpi7+M/BDmSGhqA9QIrCyHNiEQW5rcRxYcLTBC7urBHY69dHgQ vg8S2dh6OvpoafKPpZ91F2Krfv8A6nV58dK4t0vBshVjN/LlTtA= =2wVa -END PGP SIGNATURE- -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#969137: Bug#969137: darktable: Histogram not shown
Control: tag -1 unreproducible Fabian Inostroza writes: > Package: darktable > Version: 3.2.1-2+b1 > Severity: normal > > Dear Maintainer, > > When working on a image in darktable the histogram is not shown, a user > suggested > I try Ctrl+Shift+H and the only change I see is a very thin dark line in the > place > where the histogram should be. > Hi Fabian; Sorry I can't reproduce that. Ctrl-shift-h does indeed toggle it for me, and the histogram is displayed at startup 1. Does it happen on all images, or just certain ones? 2. As you might know, the histogram is only displayed in darkroom mode. 3. One thing to try is to move your darktable configuration out of the way (in ~/.config/darktable) -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#969079: Bug#969079: darktable: edits are not saved
Steven O'Connor writes: Control: tag -1 unreproducible > Package: darktable > Version: 3.2.1-2+b1 > Severity: important > X-Debbugs-Cc: slack...@gmail.com > > Dear Maintainer, > > When I crop a photo and go to lightbox the cropping is lost, I have tried > Ctl-e > from darkroom but the export is an uncropped image. > > I think this problem started with the upgrade to 3.2.1. > > I have tried deleting the database and config but this hasn't help. Hi Stephen; I can't duplicate the problem here. If you have a photo file that shows this problem, and is less than 10MB in size, please attach to the bug report (a standard MIME attachment in a reply should work). d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#960047: Bug#960047: darktable: Superfluous dependencies
astian writes: > Control: found -1 3.2.1-2 > > What's the problem with fixing this? It's a one-liner FFS. > The problem is a lack of time and motivation. You are not helping with either by sending such messages. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#965178: Bug#965178: GPU and driver
Michael Rasmussen via Pkg-phototools-devel writes: > Opencl: > dpkg --get-selections |grep opencl > mesa-opencl-icd:amd64 install > nvidia-opencl-common install > nvidia-opencl-icd:amd64 install > ocl-icd-libopencl1:amd64 install > ocl-icd-libopencl1:i386 install > ocl-icd-opencl-dev:amd64 install > opencl-c-headers install > opencl-clhpp-headers install > opencl-headersinstall > Also try removing all of the opencl related packages you are not using. darktable itself does not depend on any of them. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#965178: Bug#965178: GPU and driver
Michael Rasmussen via Pkg-phototools-devel writes: > GPU: > $ nvidia-smi > Fri Jul 17 12:32:08 2020 > +-+ > | NVIDIA-SMI 440.100 Driver Version: 440.100 CUDA Version: > 10.2 | > |---+--+--+ > | GPU NamePersistence-M| Bus-IdDisp.A | Volatile > Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | > GPU-Util Compute M. | > |===+==+==| > | 0 GeForce GTX 1050On | :01:00.0 Off | > N/A | | 40% 31CP8N/A / 75W | 2MiB / 2000MiB | > 0% Default | > +---+--+--+ > | 1 GeForce GTX 105... On | :26:00.0 On | > N/A | | 35% 34CP8N/A / 75W |396MiB / 4032MiB | > 3% Default | > +---+--+--+ > > Is this enough or do you need more info? It seems your problem is most likely with the non-free NVIDIA drivers. I can't help you there. You can probably get help from a fellow NVIDIA user on upstream irc (#darktable on freenode) or user mailing lists https://www.darktable.org/contact/ -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#965178: Bug#965178: Seems to be related to opencl
Control: tag -1 unreproducible Michael Rasmussen via Pkg-phototools-devel writes: > Message from upstream: > > "This is a problem with opencl driver and has nothing to do with > darktable. darktable doesn't care which llvm is used by opencl (llvm is > used only for test compilation of opencl kernels and in no way required > for opencl support or used in runtime)." > OK, so then it sounds like it is not a bug in the darktable package. I'm not running OpenCL so it's not easy for me to duplicate your issues. If there are drivers in Debian main (i.e. not contrib or non-free, and not directly downloaded from the manufacturer), and they work with my old AMD card (or my newer intel laptop), I'm willing to install them to investigate. To start it would help if you could list exactly what GPU and drivers you are using. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#958720: Bug#958720: Acknowledgement (darktable: Error at start - free(): invalid next size (fast))
Rolf Wuerdemann writes: > On Sun, 24 May 2020 14:48:10 +0200 Ronny Bachmann > wrote: >> [dt fails with "free(): invalid next size (fast)" after start] > > Dear colleagues, > > I've got the same error. However: it might be interesting, that after > doing a source build and installation as described in > > https://wiki.debian.org/BuildingTutorial > > up to and including "Rebuild without changes" everything works. > Even using the package from the testing repo works afterwards the > rebuild from source. > The last part is pretty surprising. Maybe installing the build dependencies fixed the problem for you? Ronny, are you able to rebuild from source? d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#962364: libgphoto2: please update to 2.5.25
Source: libgphoto2 Version: 2.5.25-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have forked the repo on salsa and did a quick update to 2.5.25 at https://salsa.debian.org/bremner/libgphoto2 Feel free to use that (or change whatever needs to be changed). It has worked for me for about 10 minutes, but I don't really know if I duplicated your workflow and checked all the things that need to be checked. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl7b+VQACgkQA0U5G1Wq FSH21A/9HfxdGZsh3Qrcd+w0pabNFntCQPE56QLNyg6/3U7wR9kin5Pa83NtBYee vvrgu0CzgKBhdfM0JT5p/PoBfievsFdo/QYNrbcOT3VMSGd6n64unlOr4RUtAvkI rNB1SLjTfdw9shc1nBK1a2kU/VLZJAgndSwlQdtQwAkoxmDPEp8mEPlQ43tq8kEM 62nyyfxC2jJTCypGaqgO0Hr/TLlKQ4KfurvdOJKyPxeCHEpP+AqZCRNW5Jah9pNQ gdAjvdQNSlJjXK4OKMC2+LbARl4GpUIkwSJRH1BG2Ui5B9trcAzJi7flz14H47QT ibZM28mnzgFd9mT5ZYP9cE+RVN2FNfH0an6gh1pQf7cug5WXtBRXhm01dkQlUxet 1CFk8uCdojio5wZteOx1KnqZhgd/5j8tN39wG6jw/oJLe1n5UDsRn5COj3eGx8rb vsUDn5fWlx31224i8LSI03Zx9DWsFXQBZjAS1vBEZUw1QSdlb1GLkp+lAtDb47f/ Fvrdz8oK9VnkZ4Caivz6Eak7aQkIfEWlT9O0BiQCaI/ntHDiXHtw52bN7yC8c7kT SnFXS4qiysRPZdR1ktN8KwqeXyiHJxI15ItlDQFcgJxy8f4ALzICNZdFROt3T7nM ymOzXFXNDsKoHX6eoLeKBBHy2fWqxdLGqzwJB5cKuZy+aZrzAxk= =J3CW -END PGP SIGNATURE- -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#958720: Bug#958720: darktable: Error at start - free(): invalid next size (fast)
Ronny Bachmann writes: > Package: darktable > Version: 3.0.2-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > > The problem exists since the update to the version 3.0.2-1 > What version are you updating from? d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] darktable master does not update
David Bremner writes: > AB writes: > >> Dear Sirs, I am using your package darktable master on a Ubuntu 18.04 >> linux system. The system is not receiving updates anymore. My current >> version is 3.1.0~git778.38d7bdbd3. However, I have recognised your >> latest version is 3.1.0~git811.dcba65bf6. >> >> Do you have any advice for me, how to receive your latest updates? > > This is not an official debian package. I suggest consulting whoever is > providing you with packages. I realized that my explanation was a bit terse. Debian doesn't contain snapshot packages of master, so it's pretty doubtful that Ubuntu does. You are presumably using some ubuntu PPA; the the first P is for personal, so you should contact that person. I suspect if you visit darktable.org you will find information on various options for for snapshot packages. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] darktable master does not update
AB writes: > Dear Sirs, I am using your package darktable master on a Ubuntu 18.04 > linux system. The system is not receiving updates anymore. My current > version is 3.1.0~git778.38d7bdbd3. However, I have recognised your > latest version is 3.1.0~git811.dcba65bf6. > > Do you have any advice for me, how to receive your latest updates? This is not an official debian package. I suggest consulting whoever is providing you with packages. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#939755: darktable: FTBFS with gcc-9
Package: darktable Version: 2.6.2-1 Severity: serious Tags: upstream Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 darktable in unstable and experimental fails to build with gcc-9, due to openmp related changes. This is known, and fixed upstream in git master. It will probably be at least another month or so before a release. There is more than one merge request upstream that would have to be backported to do this nicely. Currently the options seem to be - - force the build to use gcc-8 - - package a git snapshot, and (presumably) keep it out of testing - - take on faith a 5k line patch opensuse is using; that patch only mentions one pull request, so I don't know if it is a complete solution. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages darktable depends on: ii libc62.28-10 ii libcairo21.16.0-4 ii libcolord-gtk1 0.1.26-2 ii libcolord2 1.4.3-4 ii libcups2 2.3.0-3 ii libcurl3-gnutls 7.65.3-1 ii libexiv2-14 0.25-4 ii libflickcurl01.26-4+b1 ii libgcc1 1:9.2.1-4 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.60.6-2 ii libgomp1 9.2.1-4 ii libgphoto2-6 2.5.22-3 ii libgphoto2-port122.5.22-3 ii libgraphicsmagick-q16-3 1.4+really1.3.33-1 ii libgtk-3-0 3.24.11-1 ii libilmbase23 2.2.1-2+b1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii libjson-glib-1.0-0 1.4.4-2 ii liblcms2-2 2.9-3+b1 ii liblensfun1 0.3.2-4 ii liblua5.3-0 5.3.3-1.1+b1 ii libopenexr23 2.2.1-4.1+b1 ii libopenjp2-7 2.3.0-2 ii libosmgpsmap-1.0-1 1.1.0-6 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libpng16-16 1.6.37-1 ii libpugixml1v51.9-3 ii librsvg2-2 2.44.14-1 ii libsecret-1-00.18.7-1 ii libsoup2.4-1 2.64.2-2 ii libsqlite3-0 3.29.0-2 ii libstdc++6 9.2.1-4 ii libtiff5 4.0.10+git190818-1 ii libwebp6 0.6.1-2+b1 ii libx11-6 2:1.6.7-1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxrandr2 2:1.5.1-1 ii zlib1g 1:1.2.11.dfsg-1+b1 darktable recommends no packages. darktable suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl10/GAACgkQA0U5G1Wq FSFWDA//UL9/NKzuYqDuMzS3TSJaROUb3YzWRtrQVcjd0F3+hYZ7/iXwfKSfndNw Bs3jHQI0at1MOIv+eCWVhZAfen9fRJ0I184QCYqfUuN+zCZ1p6vDFj/6Bzem+eBK /WPhEvqTjQpIC37ODX1tPsoM5D8cmD/O344y69Sp2bbIUoP3lM7IZa4oGS9Jkamf itMXjGqHvcQwUh2kDqBaaRG4qMOtQOAwpFVYBhFPdIARiAW8JQK6kAXEyLLIB3pB vc7wqNbp5SMrclKlNP2cOrlddUVi7VAnDh69/mjUfipt7uxKxp+BKDvg6BxZYZze zCwoqi25p+aKvb66AgUUsmm1n+2QEutDNu1Ah009e1fzTZyZF+kcteB/midEShDz lCPsHwJ+JUOSLKehjsLjviWtk+SRIeshsnhmtqNvMkdSZPjcYQbPXaQ35mjROSv1 VKu7CYO6EVJCvBTTKRmQmBgDTn6SjFPLEa5bRohwb1EBkzOI2H9ntGWRhEhfFIgi P6LCm1wda3coyxEXn5gbFnbE1gsPG5m9uBFGsIOZ0+VcFnF0ohbDKL1X/xnf5VOn y/RJT1qTVlyEHhBZvpmOs9IH7bP755kIoWJkW5WunbjaaSTz4zxRuwn2WsBzhg89 EEfQl2DXmpW63Mxk9HOW2jAoLlt4nrXVC4Intmd0FyIvEpnD5Tk= =Q60t -END PGP SIGNATURE- -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#927851: Bug#927851: Buster-upgrade, Hugin-build
andrew glaeser writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > While my upgraded system seems OK now, I can also log in as before wit x2go > and see the same xfce-desktop, and I can install packages. > > But, big but, the stable Hugin-source PPA does not seem OK to me: > > So, any other proposals? > > Do I have to use subversion and mercurial? > > I currently have the impression Debian is the worst ubuntu-variant of them > all, this is why I _will_not_use_ubuntu_ I can't tell if you're trolling, or just not clear on how to use the debian bug tracking system, but please stop sending things to this bug that are not related to the Debian package hugin. If you need help with a PPA, contact the maintainers of that PPA. If you need more general help with debian, try the mailing list debian-u...@lists.debian.org. David (asking for the second time). -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#932641: Bug#932641: darktable: "collect images" does not filter lighttable view
Control: tag -1 unreproducible Koopac writes: > After upgrading to buster, I imported a bunch of raw images, and tried to > filter them using the "film roll" filter in "collect images" as usual. After > setting up the filter, lighttable still showed all 11K+ images in my db. > > I tried upgrading to the latest version (from experimental), but it didn't > help. So far I don't know how to reproduce your bug. I've been using 2.6.2-1 on a few machines and haven't seen anything like this. I guess one thing you could try is to start with a fresh database (after backing up your current .config/darktable), and import a few directories and see if you still have the same problem. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] The Darktable package does not include the Spanish translation
David Bremner writes: > Tomás Senabre González writes: > >> Hello >> The Darktable package, version 2.6.0-1 (testing) in Debian 10 (Buster), >> does not include the Spanish translation files. >> >> Thanks for your job >> Tomás >> > > Please file a bug in the Debian BTS, preferably using reportbug. This > will increase the chance that someone fixes the problem. That's still the right thing to do in general, but in this case it probably won't help. I checked and Darktable 2.6.0 did not include the Spanish translation because it was apparently not ready yet. When buster backports are open, a version of darktable with a Spanish translation will be uploaded there. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] The Darktable package does not include the Spanish translation
Tomás Senabre González writes: > Hello > The Darktable package, version 2.6.0-1 (testing) in Debian 10 (Buster), > does not include the Spanish translation files. > > Thanks for your job > Tomás > Please file a bug in the Debian BTS, preferably using reportbug. This will increase the chance that someone fixes the problem. d -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#927143: Bug#927143: libgphoto2 2.5.22
Ole Aamot writes: > Package: libgphoto2 > Version: 2.5.22 > > I don't follow development these days, but I see that version 2.5.22 is > available from http://www.gphoto.org/ > > Best, > Ole > And will be in the next stable version of Debian (it is currently in testing and unstable). -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] Package: hugin, Package: hugin
David Bremner writes: > andrew glaeser writes: > > >> Hello, all, >> >> some time ago I reported on Hugin already, and also tried to forward the >> >> issue upstream to the ubuntu-launchpad. But seemingly the complaint was not >> >> really accepted there. > > I'm not the hugin maintainer for Debian, but I am a package maintainer, > and the following is general advice for getting help with Debian > packages. > > I don't see a bug filed in the Debian bug tracking system. My mistake. I see that you did actually file a bug a few weeks ago. I can say that installing packages from testing directly on stable is not supported in general. -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] Package: hugin, Package: hugin
andrew glaeser writes: > Hello, all, > > some time ago I reported on Hugin already, and also tried to forward the > > issue upstream to the ubuntu-launchpad. But seemingly the complaint was not > > really accepted there. I'm not the hugin maintainer for Debian, but I am a package maintainer, and the following is general advice for getting help with Debian packages. I don't see a bug filed in the Debian bug tracking system. Could you please report a bug using reportbug? Ideally try to trim some of the report. Most maintainers are extremely busy volunteers, and e.g. pages of output from apt that don't relate to the bug just get in the way of actually helping. Thanks, David -- Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
Re: [Pkg-phototools-devel] New package of Darktable
Michael Rasmussen writes: > Hi Maintainers, > > Current released version of Darktable is 2.6.2 and the version in > Debian is 2.6.0 so may I ask when we can expect to see a package in > Debian of the current release? In the future, please file a wishlist bug for new versions of Debian packages, it has less chance of being lost. As you might know, we're currently in the buster freeze, so any new version would target experimental. If there is a specific bug affecting your use of darktable, please file a seperate bug with an appropriate severity (probably normal). That will help me prioritize packaging a new version and/or backporting the changes. d ___ Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
[Pkg-phototools-devel] Bug#919342: Bug#919342: darktable: Segfault when moving drawn mask
Control: tag -1 unreproducible moreinfo Charlie Hagedorn writes: > > Opened up an image, did some edits to an image, and then created my > first drawn mask with the upgraded version. It wasn't quite in the > right place, so I clicked-and-dragged in the middle of the image. The > mask outline disappeared, I may have clicked in a few spots/faffed a > little bit, and darktable crashed. I don't use drawn masks normally, but I tried drawing a few circles and elipses and dragging them around. I didn't experience any strange behaviour. What module were you using? > The image was missing from the lighttable when I restarted darktable, > so I reapplied the same edits, switched back to the lighttable in > order to save my progress, I don't understand this part. If the image was missing from the lighttable, how did you edit it? Is there some duplication going on? > 1. That mask is now saved, and if I call it up from the list of masks, > darktable crashes. I don't know enough about library.db to call it up > and submit it. If a developer with enough darktable-fu can tell me > how, I'll add it to this bug. Yeah, me neither unfortunately. > 2. Moving any drawn mask on any image I have tried so far yields an > instantaneous jump of the mask down and right by ~500-1000 > pixels. Dragging is then successful, and darktable does not crash. In > ~5 tries, I have not been able to generate another segfaulting mask. Hmm. You'd think I'd have noticed this. > 3. When segfaulting, Darktable consistently stores > > " > this is darktable 2.6.0 reporting a segfault: > > warning: Currently logging to /tmp/darktable_bt_5AAEVZ.txt. Turn the logging > off and on to make the new setting effective. > /usr/share/darktable/gdb_commands:2: Error in sourced command file: > No stack. > " > to a logfile in /tmp. Internet search suggests that I'd get more debug output > with darktable-dbg, but as it is not in Debian testing, I don't want to > install it. > You want darktable-dbgsym. To install it you will need a line like deb http://debug.mirrors.debian.org/debian-debug/ testing-debug main in sources.list ___ Pkg-phototools-devel mailing list Pkg-phototools-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel
