diff mbox series

[bug#38815] gnu: sassc: Update to 3.6.1.

Message ID 8vPKTnwwfY4ecgts67qtXbG04xMreq2Oy8kmlI0Oix7RgxCHkExOcA79B4rjUq2i7Mu-lHpji6XXRy6DBWx9MOdZkhqvB6flKffTjO3wyr8=@protonmail.com
State Accepted
Headers show
Series [bug#38815] gnu: sassc: Update to 3.6.1. | expand

Commit Message

ashish.is--- via Guix-patches" via Dec. 30, 2019, 3:09 p.m. UTC
From 1f66209d161e593ac482c8f523f5425aed2c7a11 Mon Sep 17 00:00:00 2001
From: Riku Viitanen <riku.viitanen@protonmail.com>
Date: Mon, 30 Dec 2019 16:51:29 +0200
Subject: [PATCH] gnu: sassc: Update to 3.6.1.

* gnu/packages/web.scm (sassc): Update to 3.6.1.
---
 gnu/packages/web.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--
2.24.0

Comments

Efraim Flashner Dec. 30, 2019, 6:21 p.m. UTC | #1
Looks good. Patch pushed
ashish.is--- via Guix-patches" via Jan. 8, 2020, 4:50 p.m. UTC | #2
Riku, Efraim, Guix,

I noticed that this commit and the preceding libsass update have 
an incorrect author e-mail addres:

  commit fc4eb87dc45b169e3912c73bbf60cb8ce76b7c7c
  Author: Riku Viitanen via Guix-patches via 
  <guix-patches@gnu.org>

The actual patch posted to guix-patches[0] has two correct From: 
lines.

Does anyone know what happened here?  And how it could be avoided? 
Is the Web interface hiding anything strange about these messages?

Would a git hook to catch suspect addresses be a good idea?

Kind regards,

T G-R

[0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38815
Efraim Flashner Jan. 9, 2020, 7:54 p.m. UTC | #3
On Wed, Jan 08, 2020 at 05:50:15PM +0100, Tobias Geerinckx-Rice via Guix-patches via wrote:
> Riku, Efraim, Guix,
> 
> I noticed that this commit and the preceding libsass update have an
> incorrect author e-mail addres:
> 
>  commit fc4eb87dc45b169e3912c73bbf60cb8ce76b7c7c
>  Author: Riku Viitanen via Guix-patches via  <guix-patches@gnu.org>
> 
> The actual patch posted to guix-patches[0] has two correct From: lines.
> 
> Does anyone know what happened here?  And how it could be avoided? Is the
> Web interface hiding anything strange about these messages?

I caught one another time but this time they slipped through. I normally
patch the pipe directly from mutt to 'cd workspace/guix; git am -S -s'.

> 
> Would a git hook to catch suspect addresses be a good idea?
> 

Probably couldn't hurt.

> Kind regards,
> 
> T G-R
> 
> [0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38815
diff mbox series

Patch

diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
index a883660a81..dd27454e79 100644
--- a/gnu/packages/web.scm
+++ b/gnu/packages/web.scm
@@ -1550,7 +1550,7 @@  stylesheets, you'll need to use another program that uses this library,
 (define-public sassc
   (package
     (name "sassc")
-    (version "3.5.0")
+    (version "3.6.1")
     (source (origin
               (method git-fetch)
               (uri (git-reference
@@ -1559,7 +1559,7 @@  stylesheets, you'll need to use another program that uses this library,
               (file-name (git-file-name name version))
               (sha256
                (base32
-                "0jsfz1zg4gwk0dq8i92ll12axs3s70wsdsmdyi71zx8zmvib5nl6"))))
+                "1sxm54mkhs9m4vnl7vn11y17mhzamc403hv3966j1c7p2rbzg5pv"))))
     (build-system gnu-build-system)
     (arguments
      `(#:make-flags