emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#61780: closed ([PATCH 0/3] Fix Tracker and update it)


From: GNU bug Tracking System
Subject: bug#61780: closed ([PATCH 0/3] Fix Tracker and update it)
Date: Sun, 05 Mar 2023 08:58:01 +0000

Your message dated Sun, 05 Mar 2023 09:57:40 +0100
with message-id <47eb43baad4af34e1a82addcdc98ca2982cc6814.camel@gmail.com>
and subject line Re: [PATCH 0/3] Fix Tracker and update it
has caused the debbugs.gnu.org bug report #61780,
regarding [PATCH 0/3] Fix Tracker and update it
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
61780: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61780
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/3] Fix Tracker and update it Date: Sat, 25 Feb 2023 09:09:30 +0100
Hi Guix,

I noticed that the tracker3 command line utility which ships with our
tracker package is a little broken.  I decided to fix the issue behind
it and also update the package alongside.

I'm currently running the builds, but since more than 100 packages
appear to be affected, I'll only do native builds.  Let's cross our
fingers that CI also thinks it's fine :)

Cheers

Liliana Marie Prikler (3):
  gnu: tracker: Don't wrap binaries in libexec/tracker3 directory.
  gnu: tracker: Use G-Expressions in arguments.
  gnu: tracker: Update to 3.4.2.

 gnu/packages/gnome.scm | 86 ++++++++++++++++++++++++------------------
 1 file changed, 49 insertions(+), 37 deletions(-)


base-commit: ea2fa86f31a83195ac789a6d92bcaee8e53e4397
-- 
2.39.1




--- End Message ---
--- Begin Message --- Subject: Re: [PATCH 0/3] Fix Tracker and update it Date: Sun, 05 Mar 2023 09:57:40 +0100 User-agent: Evolution 3.46.0
Am Samstag, dem 25.02.2023 um 09:09 +0100 schrieb Liliana Marie
Prikler:
> Hi Guix,
> 
> I noticed that the tracker3 command line utility which ships with our
> tracker package is a little broken.  I decided to fix the issue
> behind it and also update the package alongside.
> 
> I'm currently running the builds, but since more than 100 packages
> appear to be affected, I'll only do native builds.  Let's cross our
> fingers that CI also thinks it's fine :)
CI does report some newly failing builds, but those new failures appear
to already have existed (???)

Anyway, I pushed this series now.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]