GNU bug report logs -
#36536
[PATCH] Update i3blocks to 1.4-2
Previous Next
Reported by: ison <ison <at> airmail.cc>
Date: Sun, 7 Jul 2019 11:18:01 UTC
Severity: normal
Tags: patch
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36536 in the body.
You can then email your comments to 36536 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#36536
; Package
guix-patches
.
(Sun, 07 Jul 2019 11:18:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
ison <ison <at> airmail.cc>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Sun, 07 Jul 2019 11:18:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
i3blocks click events weren't functioning with the latest i3bar.
Updating fixes the issue. See attached patch.
Sorry for the dumb quesiton, but I hope I am correctly understanding the role of
"revision" here. I simply incremented it from 1 to 2.
My understanding is it's just a number added to the end of the version string to
give it a unique value when updating to a commit that doesn't correspond to an
exact release.
If that's not correct then please let me know so I can fix it.
[0001-Update-i3blocks-to-1.4-2.patch (text/plain, attachment)]
Reply sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
You have taken responsibility.
(Mon, 08 Jul 2019 11:03:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
ison <ison <at> airmail.cc>
:
bug acknowledged by developer.
(Mon, 08 Jul 2019 11:03:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 36536-done <at> debbugs.gnu.org (full text, mbox):
Hi,
ison <ison <at> airmail.cc> skribis:
> i3blocks click events weren't functioning with the latest i3bar.
> Updating fixes the issue. See attached patch.
>
> Sorry for the dumb quesiton, but I hope I am correctly understanding the role of
> "revision" here. I simply incremented it from 1 to 2.
> My understanding is it's just a number added to the end of the version string to
> give it a unique value when updating to a commit that doesn't correspond to an
> exact release.
That’s correct!
>>From 0c0705d510db8e4c7f9e5a3ff8b1cbf48d6bc104 Mon Sep 17 00:00:00 2001
> From: ison <ison <at> airmail.cc>
> Date: Sun, 7 Jul 2019 05:02:01 -0600
> Subject: [PATCH] Update i3blocks to 1.4-2
>
> ---
> gnu/packages/wm.scm | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
I adjusted the commit log to match our conventions and applied it.
Thanks!
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 05 Aug 2019 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 258 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.