The Fedora pl package contains SWI Prolog, often abbreviated to SWIPL.
I've been talking to the lead SWIPL developer. He tells me that, as
of May this year, SWIPL development moved from Ubuntu to Fedora
because our development tools are more up to date. Let's all give
ourselves a nice pat on the back!
Upstream would like the package renamed to swi-prolog, and to have a
subpackage structure that mirrors the Debian package. I will submit a
rename review request soon. (There are a few other issues to work out
first.)
Upstream also objected to the license string here:
https://packages.fedoraproject.org/pkgs/pl/pl/. According to the git
log, the License tag was converted to SPDX in December 2022, but that
page still shows the License tag from before that. How are these
pages generated? Is there a button I can push to make that page
update?
--
Jerry James
http://www.jamezone.org/
On 8/28/24 12:36 PM, Maxwell G wrote:
> On 8/28/24 12:29 PM, Jerry James wrote:
>
>> Upstream also objected to the license string here:
>> https://packages.fedoraproject.org/pkgs/pl/pl/. According to the git
>> log, the License tag was converted to SPDX in December 2022, but that
>> page still shows the License tag from before that. How are these
>> pages generated? Is there a button I can push to make that page
>> update?
> It's statically generated on a cronjob, I think. See the source code
> link at the bottom of the page. I think it's been broken since PDC was
> shut off, and no one has gotten around to fixing it yet.
See [1] and [2]. It looks like this has been partially fixed now.
[1] https://pagure.io/fedora-packages-static/issue/49
[2]
https://pagure.io/fedora-packages-static/c/9463d3793272c349a1377fd22830b3c0…
Hi,
Since version 4.19, RPM defaults to C.UTF-8 locale [1]. Here is a list
of 248 packages which explicitly sets the locale and could drop the
setting. The list was generated with:
# strip changelogs
for x in *.spec; do sed -i '/^%changelog$/q' $x; done
grep -E
'(^|\W)(LANG|LANGUAGE|LC_CTYPE|LC_NUMERIC|LC_TIME|LC_COLLATE|LC_MONETARY|LC_MESSAGES|LC_PAPER|LC_NAME|LC_ADDRESS|LC_TELEPHONE|LC_MEASUREMENT|LC_IDENTIFICATION|LC_ALL)=[Cc]\.[Uu][Tt][Ff]-?8($|\W)'
-r | sed 's/:/ /' | grep -v 'spec #' | sort -u
Credits goes to Mikolaj for pointing this out and preparing the attached
list.
Vít
[1] https://github.com/rpm-software-management/rpm/pull/2616
Hi,
shadow-utils released v4.16.0
<https://github.com/shadow-maint/shadow/releases/tag/4.16.0> recently and
this new version introduces a libsubid major version bump. I'm updating
shadow-utils in rawhide and for that purpose I have created a side-tag
(f42-build-side-95092) to build all dependencies: buildah, podman and
skopeo.
lsm5 is the maintainer of these packages and he's rebuilding them, so this
is just a notification so that everyone is aware of these changes.
--
Iker Pedrosa
Senior Software Engineer, Identity Management team
Red Hat <https://www.redhat.com>
Txapela (gorria) buruan eta ibili munduan
(Red) hat on his head and walk the world
Basque proverb
<https://www.redhat.com>
I am trying to build pyliblo3 from your repo on Fedora 41 with python 3.13.0.
I've got a build error during compilation:
# wget https://github.com/gesellkammer/pyliblo3/archive/refs/heads/master.zip
# unzip pyliblo3-master.zip; cd pyliblo3-master; ./setup build
root@fc41:/tmp/pyliblo3-master# ./setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-313
creating build/lib.linux-x86_64-cpython-313/pyliblo3
copying pyliblo3/__init__.py -> build/lib.linux-x86_64-cpython-313/pyliblo3
copying pyliblo3/_liblo.pyi -> build/lib.linux-x86_64-cpython-313/pyliblo3
running build_ext
Compiling pyliblo3/_liblo.pyx because it changed.
[1/1] Cythonizing pyliblo3/_liblo.pyx
/usr/lib64/python3.13/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pyliblo3-master/pyliblo3/_liblo.pxd
tree = Parsing.p_module(s, pxd, full_module_name)
building 'pyliblo3._liblo' extension
creating build/temp.linux-x86_64-cpython-313
creating build/temp.linux-x86_64-cpython-313/pyliblo3
gcc -fno-strict-overflow -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -fcf-protection -fexceptions -fcf-protection -fexceptions -fcf-protection -fexceptions -O3 -fPIC -Ipyliblo3 -I/usr/include -I/usr/local/include -I/usr/include/python3.13 -c pyliblo3/_liblo.c -o build/temp.linux-x86_64-cpython-313/pyliblo3/_liblo.o -fno-strict-aliasing -Werror-implicit-function-declaration -Wfatal-errors
pyliblo3/_liblo.c: In function ‘__pyx_f_8pyliblo3_6_liblo__msg_callback’:
pyliblo3/_liblo.c:9011:92: error: passing argument 1 of ‘lo_blob_dataptr’ from incompatible pointer type [-Wincompatible-pointer-types]
9011 | __pyx_t_7 = __Pyx_PyBytes_FromCString(((unsigned char *)lo_blob_dataptr((__pyx_v_argv[__pyx_v_i])))); if (unlikely(!__pyx_t_7)) __PYX_ERR(0, 274, __pyx_L1_error)
| ~~~~~~~~~~~~~^~~~~~~~~~~~
| |
| lo_arg *
pyliblo3/_liblo.c:1353:78: note: in definition of macro ‘__Pyx_PyBytes_FromCString’
1353 | #define __Pyx_PyBytes_FromCString(s) __Pyx_PyBytes_FromString((const char*)s)
| ^
compilation terminated due to -Wfatal-errors.
error: command '/usr/bin/gcc' failed with exit code 1
if i edit pyliblo3-master/pyliblo3/_liblo.c
and change the line 9011 to:
__pyx_t_7 = __Pyx_PyBytes_FromCString((unsigned char *)lo_blob_dataptr(*(struct lo_blob_ **)&__pyx_v_argv[__pyx_v_i])); if (unlikely(!__pyx_t_7)) __PYX_ERR(0, 274, __pyx_L1_error)
pyliblo3 compiles with ./setup build.
but how can I patch this file permanently ?
Regards
Martin