Setuid handling?
Hi, After reconfiguring today (see below) I can no longer invoke a familiar set of setuid executables: $ su - su: Not setuid and you are not root, expect this to fail root's password: $ mailq mailq: need root privileges Has the handling for such executables changed? Kind regards Felix Lechner * * * guix 23f11af repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: 23f11afacdfe755ffa514a8cbf93ba1121b9db0d
Re: `mumi send-email' means no more debbugs dance to send multiple patches
Hi Arun, Arun Isaac writes: > Hi all, > > mumi, the software powering our debbugs frontend at > https://issues.guix.gnu.org/, now also comes with a command-line > interface. At the moment, the new command-line interface allows > searching for issues, and sending patches. Most notably, it frees us > from the debbugs dance required for sending multiple patches! > > To try it out, install mumi from the latest guix pull, perhaps using > `guix shell'. This looks great! Thank you so much for your work! I've just tried it out, but unfortunately mumi didn't receive the mail in time and it just timed out sending the replies :( is there anything that could be done on that front? Does mumi use IMAP IDLE? Best, -- Josselin Poiret signature.asc Description: PGP signature
Core-updates merge, d-1
Hello, people have been working on packages close to the leaves which did not build any more in core-updates; but as far as I can see, nothing major has popped up that would prevent a merge. So unless there is firm opposition, I intend to merge core-updates to master tomorrow as announced, in the early European afternoon. Andreas
Re: `mumi send-email' means no more debbugs dance to send multiple patches
Arun Isaac writes: > mumi, the software powering our debbugs frontend at > https://issues.guix.gnu.org/, now also comes with a command-line > interface. At the moment, the new command-line interface allows > searching for issues, and sending patches. Most notably, it frees us > from the debbugs dance required for sending multiple patches! <3 <3 <3 I'll definitely have to send a patch to update the manual, once i've looked at this in more detail! :D
Adding content-addressed URLs to https://guix.gnu.org/sources.json
Hi,
Simon Tournier skribis:
> On Thu, 16 Mar 2023 at 12:48, Ludovic Courtès
> wrote:
>
>> 1. Reproducibility of past revisions. If we lose copies of the
>> auto-generated tarballs, then OpenJDK in past revisions of Guix is
>> irreparably lost. We should check whether/how to get them in
>> Disarchive + SWH.
>
> The file sources.json that SWH ingests only contains original upstream
> and not our copies. One step forward would be to also list the URL of
> our tarball substitutes as the last mirror in sources.json.
The patch below (against maintenance.git) does that. The result is
something like this:
--8<---cut here---start->8---
{
"type": "url",
"urls": [
"https://ftpmirror.gnu.org/gnu/zile/zile-2.6.2.tar.gz;,
"ftp://ftp.cs.tu-berlin.de/pub/gnu/zile/zile-2.6.2.tar.gz;,
"ftp://ftp.funet.fi/pub/mirrors/ftp.gnu.org/gnu/zile/zile-2.6.2.tar.gz;,
"http://ftp.gnu.org/pub/gnu/zile/zile-2.6.2.tar.gz;,
"https://bordeaux.guix.gnu.org/file/zile-2.6.2.tar.gz/sha256/0hf788zadmwx0xp1dhrgqcfvhwnarh6h9b51va4dr2y9yfppvsvp;,
"https://ci.guix.gnu.org/file/zile-2.6.2.tar.gz/sha256/0hf788zadmwx0xp1dhrgqcfvhwnarh6h9b51va4dr2y9yfppvsvp;,
"https://tarballs.nixos.org/sha256/0hf788zadmwx0xp1dhrgqcfvhwnarh6h9b51va4dr2y9yfppvsvp;
],
"integrity": "sha256-d+t9r/PJi9yI2qGsBA3MynK4HcMvwxZuB53Xpj5Cx0E="
},
--8<---cut here---end--->8---
How does that sound?
Thanks,
Ludo’.
diff --git a/hydra/build-package-metadata.scm b/hydra/build-package-metadata.scm
index 6fa2173..1ddb409 100755
--- a/hydra/build-package-metadata.scm
+++ b/hydra/build-package-metadata.scm
@@ -30,6 +30,7 @@
(guix utils)
(guix gexp)
((guix build download) #:select (maybe-expand-mirrors))
+ ((guix base32) #:select (bytevector->nix-base32-string))
((guix base64) #:select (base64-encode))
((guix describe) #:select (current-profile))
((guix config) #:select (%guix-version))
@@ -73,6 +74,27 @@ superseded packages."
;;; Required by 'origin->json' for 'computed-origin-method' corner cases
(define gexp-references (@@ (guix gexp) gexp-references))
+(define %content-addressed-mirrors
+ ;; List of content-addressed mirrors.
+ ;; XXX: somewhat duplicated from (guix download)
+ (let ((guix-publish
+ (lambda (host)
+ (lambda (file hash)
+ ;; Files served by 'guix publish'.
+ (string-append "https://; host "/file/"
+file "/" (symbol->string
+ (content-hash-algorithm hash))
+"/" (bytevector->nix-base32-string
+ (content-hash-value hash)))
+
+(list (guix-publish "bordeaux.guix.gnu.org")
+ (guix-publish "ci.guix.gnu.org")
+ (lambda (file hash)
+(string-append "https://tarballs.nixos.org/;
+ (symbol->string (content-hash-algorithm hash))
+ "/" (bytevector->nix-base32-string
+(content-hash-value hash)))
+
(define (origin->json origin)
"Return a list of JSON representations (an alist) of ORIGIN."
(define method
@@ -81,10 +103,17 @@ superseded packages."
(define uri
(origin-uri origin))
- (define (resolve urls)
-(map uri->string
- (append-map (cut maybe-expand-mirrors <> %mirrors)
- (map string->uri urls
+ (define (resolve urls hash)
+(append (map uri->string
+ (append-map (cut maybe-expand-mirrors <> %mirrors)
+ (map string->uri urls)))
+(if hash
+(let ((file (origin-actual-file-name origin))
+ (hash (origin-hash origin)))
+ (map (lambda (make-url)
+ (make-url file hash))
+ %content-addressed-mirrors))
+'(
(if (eq? method (@@ (guix packages) computed-origin-method))
;; Packages in gnu/packages/gnuzilla.scm and gnu/packages/linux.scm
@@ -118,7 +147,8 @@ superseded packages."
(resolve
(match uri
((? string? url) (list url))
- ((urls ...) urls)))
+ ((urls ...) urls))
+ (origin-hash origin))
((eq? git-fetch method)
`(("git_url" . ,(git-reference-url uri
((eq? svn-fetch method)
mcron latest
https://repology.org/project/mcron/versions#gnuguix Should we update mcron to the latest? Is anyone working on that? AUR has the latest mcron but we don't :(
`mumi send-email' means no more debbugs dance to send multiple patches
Hi all, mumi, the software powering our debbugs frontend at https://issues.guix.gnu.org/, now also comes with a command-line interface. At the moment, the new command-line interface allows searching for issues, and sending patches. Most notably, it frees us from the debbugs dance required for sending multiple patches! To try it out, install mumi from the latest guix pull, perhaps using `guix shell'. $ guix shell mumi To search for issues, say all open issues about "zig", run --8<---cut here---start->8--- $ mumi search zig is:open #60889 Add zig-build-system opened on 17 Jan 17:37 Z by Ekaitz Zarraga #61036 [PATCH 0/3] Update zig to 0.10.1 opened on 24 Jan 09:42 Z by Efraim Flashner #39136 [PATCH] gnu: services: Add endlessh. opened on 14 Jan 2020 21:21 by Nicol? Balzarotti #60424 [PATCH] gnu: Add python-online-judge-tools opened on 30 Dec 2022 07:03 by gemmaro #45601 [PATCH 0/6] vlang 0.2 update opened on 1 Jan 2021 19:23 by Ryan Prior --8<---cut here---end--->8--- Pick an issue and make it the "current" issue. --8<---cut here---start->8--- $ mumi current 61036 #61036 [PATCH 0/3] Update zig to 0.10.1 opened on 24 Jan 09:42 Z by Efraim Flashner --8<---cut here---end--->8--- Once an issue is the current issue, you can easily send patches to it using $ mumi send-email foo.patch bar.patch To open a new issue, run $ mumi new and send patches $ mumi send-email foo.patch bar.patch Note that, unlike `git send-email', `mumi send-email' works perfectly well with single and multiple patches alike! We are now free from the debbugs dance of sending the first patch, waiting for a response from debbugs and sending the remaining patches. `mumi send-email' automates this process. It does so by sending the first patch, polling the server for a response, and then sending the remaining patches. This polling can unfortunately take a few minutes. So, please be patient. Also `mumi send-email' frees you from having to remember the correct To address (either guix-patc...@gnu.org or xx...@debbugs.gnu.org) to send to. It figures out the correct To address from the current issue state and from the .mumi/config file now checked into the guix git repository. Feedback welcome! Patches further fleshing out the mumi CLI client are most welcome! Cheers! Arun
Re: [PATCH] gnu: python-shiboken-2: Do not rely on _Py_Mangle being available.
Am Mon, Apr 24, 2023 at 12:01:51PM +0200 schrieb Josselin Poiret: > * gnu/packages/patches/python-shiboken-2-compat.patch: Fix the patch according > to upstream. Pushed! Andreas
[PATCH] gnu: python-shiboken-2: Do not rely on _Py_Mangle being available.
* gnu/packages/patches/python-shiboken-2-compat.patch: Fix the patch according
to upstream.
---
.../patches/python-shiboken-2-compat.patch| 29 +--
1 file changed, 14 insertions(+), 15 deletions(-)
diff --git a/gnu/packages/patches/python-shiboken-2-compat.patch
b/gnu/packages/patches/python-shiboken-2-compat.patch
index 0c7de64395..48aa74173b 100644
--- a/gnu/packages/patches/python-shiboken-2-compat.patch
+++ b/gnu/packages/patches/python-shiboken-2-compat.patch
@@ -1,16 +1,15 @@
-Provide a declaration that's missing in Python 3.10.
+Backport a fix from 5.15.9, mentioned in [1].
pyside-setup-opensource-src-5.15.8/sources/shiboken2/libshiboken/sbkpython.h
2023-04-19 23:14:11.415337435 +0200
-+++
pyside-setup-opensource-src-5.15.8/sources/shiboken2/libshiboken/sbkpython.h
2023-04-19 23:18:09.055605606 +0200
-@@ -108,6 +108,11 @@ extern "C" {
- #if PY_MAJOR_VERSION >= 3
- #define IS_PY3K
-
-+extern "C" {
-+ /* In Python 3.10 this declaration is not provided by . */
-+ extern PyObject* _Py_Mangle(PyObject *p, PyObject *name);
-+}
-+
- #define PyInt_Type PyLong_Type
- #define PyInt_Check PyLong_Check
- #define PyInt_CheckExact PyLong_CheckExact
+[1] https://bugreports.qt.io/browse/PYSIDE-2176
+
+---
pyside-setup-opensource-src-5.15.8/sources/shiboken2/libshiboken/pep384impl.cpp
2023-04-24 11:05:48.770934499 +0200
pyside-setup-opensource-src-5.15.8/sources/shiboken2/libshiboken/pep384impl.cpp
2023-04-24 11:04:51.566943936 +0200
+@@ -751,7 +751,7 @@
+ #endif // IS_PY2
+ Shiboken::AutoDecRef privateobj(PyObject_GetAttr(
+ reinterpret_cast(Py_TYPE(self)),
Shiboken::PyMagicName::name()));
+-#ifndef Py_LIMITED_API
++#ifdef IS_PY2
+ return _Py_Mangle(privateobj, name);
+ #else
+ // PYSIDE-1436: _Py_Mangle is no longer exposed; implement it always.
base-commit: 827df9d1dde4f4a06e1789ec17cf0586602aa121
--
2.39.2
Re: Core-updates, the last metres
-- John Kehayias writes: > Hi Guillaume, > > On Sun, Apr 23, 2023 at 08:00 PM, Guillaume Le Vaillant wrote: >> Here are a few leaf packages that don't build because of some >> failing dependencies: >> - blender is blocked by opencolorio > > Not sure what is wrong here (error for a null pointer...) and it is > quite out of date. Looks like it'll need more than a quick fix to > update it, though admittedly I didn't try. Apparently fixed now! >> [...] >> - freecad is blocked by python-pyside-2 >> > > Didn't look much here yet, looks like part of the Python QT bindings > ecosystem. Maybe someone familiar with this can see a quick fix. I thought it would be an easy fix: Ludo fixed python-shiboken-2 previously but the fix is erroneous, see the following patch. However, I'm still getting a build error that boils down to the following: --8<---cut here---start->8--- import importlib importlib.machinery --8<---cut here---end--->8--- errors out with python-minimal@3.10, but not with python@3.10! I don't really understand how this could happen, does anyone have an idea? Best, -- Josselin Poiret signature.asc Description: PGP signature
