unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: guix-devel@gnu.org
Subject: guix refresh -u weird behaviour
Date: Wed, 04 Oct 2023 03:27:12 +0000	[thread overview]
Message-ID: <7175bfedfae865e3d90030160b8ae94a@dismail.de> (raw)

Hi Guixers,

guix refresh -u does some weird stuff. See the git diff below.

Why did it remove the native inputs?

Do we have a bug report open for this? Is it intended behaviour? 

all best,

jgart

 (define-public python-faker
   (package
     (name "python-faker")
-    (version "15.0.0")
+    (version "19.6.2")
     (source (origin
               (method url-fetch)
               (uri (pypi-uri "Faker" version))
               (sha256
                (base32
-                "1yx3gsivisf8ls43v0fgzy4n5q9625xrp9fr9cb5gp3h6k9cfpr4"))))
+                "10yzgya59l5kkrdfzp9m06cb5sj05py077h18s545yxhaqsrbmfm"))))
     (build-system python-build-system)
     (arguments
      '(#:phases
@@ -19707,12 +19707,8 @@ (define-public python-faker
              (when tests?
                (invoke "python" "-m" "pytest" "-v")))))))
     (native-inputs
-     (list python-freezegun
-           python-pytest
-           python-random2
-           python-ukpostcodeparser
-           python-validators))
-    (propagated-inputs (list python-dateutil))
+     (list))
+    (propagated-inputs (list python-dateutil python-typing-extensions))
     (home-page "https://github.com/joke2k/faker")
     (synopsis "Python package that generates fake data")


             reply	other threads:[~2023-10-04  3:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04  3:27 jgart [this message]
2023-10-04  8:10 ` guix refresh -u weird behaviour Ricardo Wurmus
2023-10-04  9:41   ` Simon Tournier
2023-10-04 12:32 ` jgart
2023-10-04 16:03   ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7175bfedfae865e3d90030160b8ae94a@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).