Adding Passim as a Fedora 40 feature?
by Richard Hughes
Hi all,
I was thinking of adding Passim as a default-installed and
default-enabled dep of fwupd in the Fedora 40 release. Before I create
lots of unnecessary drama, is there any early feedback on what's
described in https://github.com/hughsie/passim/blob/main/README.md
please.
The tl;dr: is I want to add a mDNS server that reshares the public
firmware update metadata from the LVFS on your LAN. The idea is that
rather than 25 users in an office downloading the same ~2MB file from
the CDN every day, the first downloads from the CDN and the other 24
download from the first machine. All machines still download the
[tiny] jcat file from the CDN still so we know the SHA256 to search
for and verify.
The backstory is that as the fwupd grows and grows (to ChromeOS,
FreeBSD, Windows and macOS) we need to scale things up a couple of
orders of magnitude. This isn't specific to firmware stuff, although I
think it makes a great testcase which we could add dnf or ostree
content to in the future. Comments and questions are most welcome.
Thanks,
Richard.
8 months
Re: [PATCH] fedora: Replace pasta hard links by copies, mangle
Build-IDs
by Richard W.M. Jones
On Wed, Aug 23, 2023 at 03:59:39PM +0200, Stefano Brivio wrote:
> On Wed, 23 Aug 2023 14:53:27 +0100
> "Richard W.M. Jones" <rjones(a)redhat.com> wrote:
>
> > On Wed, Aug 23, 2023 at 03:48:44PM +0200, Stefano Brivio wrote:
> > > The hard link trick didn't actually fix the issue with SELinux file
> > > contexts properly: as opposed to symbolic links, SELinux now
> > > correctly associates types to the labels that are set -- except that
> > > those labels are now shared, so we can end up (depending on how
> > > rpm(8) extracts the archives) with /usr/bin/passt having a
> > > pasta_exec_t context.
> > >
> > > This got rather confusing as running restorecon(8) seemed to fix up
> > > labels -- but that's simply toggling between passt_exec_t and
> > > pasta_exec_t for both links, because each invocation will just "fix"
> > > the file with the mismatching context.
> > >
> > > Replace the hard links with copies. AppArmor's attachment, instead,
> > > works with hard links, and if there's no LSM, we can keep symbolic
> > > links, so keep symbolic links in the Makefile.
> > >
> > > With copies, rpmbuild(8) will warn about duplicate Build-IDs in the
> > > same package. Mangle them in pasta binaries by summing one to the
> > > last byte, modulo one byte, using xxd (provided by vim-common) and
> > > disable the automatic rehashing by find-debuginfo(1) -- we already
> > > have per-release Build-IDs thanks to $VERSION passed on 'make'.
> >
> > Right, this ^ was going to be my comment. RPM doesn't like having two
> > identical copies of a file.
>
> In which other way, though? cpio(1) is fine with it, and I tried to
> install the package on both ext4 and xfs -- the only warning I got was
> the (semi-reasonable) one from rpmbuild about duplicate Build-IDs.
I'm fairly sure I've seen an error when you have two identical files;
it might only happen in Koji. Anyway, hacking the binary is surely
wrong, but let's hear the opinions of the Fedora / SELinux developers.
Rich.
> > Hacking the binary to "fix" the problem doesn't sound like a solution.
> >
> > I'm CC-ing Fedora-devel-list to find out we can properly fix this issue.
> >
> > Rich.
> >
> > > Signed-off-by: Stefano Brivio <sbrivio(a)redhat.com>
> > > ---
> > > contrib/fedora/passt.spec | 27 ++++++++++++++++++++++-----
> > > 1 file changed, 22 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/contrib/fedora/passt.spec b/contrib/fedora/passt.spec
> > > index d0c6895..51bf5a8 100644
> > > --- a/contrib/fedora/passt.spec
> > > +++ b/contrib/fedora/passt.spec
> > > @@ -9,6 +9,10 @@
> > >
> > > %global git_hash {{{ git_head }}}
> > > %global selinuxtype targeted
> > > +# Different Build-IDs for passt and pasta: don't let find-debuginfo touch them
> > > +%undefine _unique_build_ids
> > > +%global _no_recompute_build_ids 1
> > > +
> > >
> > > Name: passt
> > > Version: {{{ git_version }}}
> > > @@ -19,7 +23,7 @@ Group: System Environment/Daemons
> > > URL: https://passt.top/
> > > Source: https://passt.top/passt/snapshot/passt-%{git_hash}.tar.xz
> > >
> > > -BuildRequires: gcc, make, checkpolicy, selinux-policy-devel
> > > +BuildRequires: gcc, make, checkpolicy, selinux-policy-devel, binutils, vim-common
> > > Requires: (%{name}-selinux = %{version}-%{release} if selinux-policy-%{selinuxtype})
> > >
> > > %description
> > > @@ -56,15 +60,28 @@ This package adds SELinux enforcement to passt(1) and pasta(1).
> > > %install
> > >
> > > %make_install DESTDIR=%{buildroot} prefix=%{_prefix} bindir=%{_bindir} mandir=%{_mandir} docdir=%{_docdir}/%{name}
> > > -# The Makefile creates symbolic links for pasta, but we need hard links for
> > > +# The Makefile creates symbolic links for pasta, but we need actual copies for
> > > # SELinux file contexts to work as intended. Same with pasta.avx2 if present.
> > > -ln -f %{buildroot}%{_bindir}/passt %{buildroot}%{_bindir}/pasta
> > > +#
> > > +# To avoid duplicate Build-IDs in the same package, we increase the last byte of
> > > +# the value for pasta binaries by one (modulo one byte). Note that we already
> > > +# have differentiated Build-IDs per release, courtesy of $VERSION, so we don't
> > > +# need find-debuginfo(1) to recalculate them.
> > > +rm %{buildroot}%{_bindir}/pasta
> > > +objcopy --dump-section .note.gnu.build-id=%{buildroot}/build_id %{buildroot}%{_bindir}/passt
> > > +printf '\x'$(printf %02x $(( ( 0x$(xxd -ps -s 35 %{buildroot}/build_id) + 1 ) % 0xff )) ) | dd of=%{buildroot}/build_id seek=35 bs=1 count=1 conv=notrunc
> > > +objcopy --update-section .note.gnu.build-id=%{buildroot}/build_id %{buildroot}%{_bindir}/passt %{buildroot}%{_bindir}/pasta
> > > +rm %{buildroot}/build_id
> > > +
> > > %ifarch x86_64
> > > -ln -f %{buildroot}%{_bindir}/passt.avx2 %{buildroot}%{_bindir}/pasta.avx2
> > > +rm %{buildroot}%{_bindir}/pasta.avx2
> > > +objcopy --dump-section .note.gnu.build-id=%{buildroot}/build_id %{buildroot}%{_bindir}/passt.avx2
> > > +printf '\x'$(printf %02x $(( ( 0x$(xxd -ps -s 35 %{buildroot}/build_id) + 1 ) % 0xff )) ) | dd of=%{buildroot}/build_id seek=35 bs=1 count=1 conv=notrunc
> > > +objcopy --update-section .note.gnu.build-id=%{buildroot}/build_id %{buildroot}%{_bindir}/passt.avx2 %{buildroot}%{_bindir}/pasta.avx2
> > > +rm %{buildroot}/build_id
> > >
> > > ln -sr %{buildroot}%{_mandir}/man1/passt.1 %{buildroot}%{_mandir}/man1/passt.avx2.1
> > > ln -sr %{buildroot}%{_mandir}/man1/pasta.1 %{buildroot}%{_mandir}/man1/pasta.avx2.1
> > > -install -p -m 755 %{buildroot}%{_bindir}/passt.avx2 %{buildroot}%{_bindir}/pasta.avx2
> > > %endif
> > >
> > > pushd contrib/selinux
> > > --
> > > 2.39.2
>
> --
> Stefano
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
8 months
Manual step in upgrade process for a FSWC
by Iker Pedrosa
Hi,
I intend to switch pam_userdb's database provider from BerkeleyDB to GDBM
and I'm writing a Fedora System-Wide Change
<https://fedoraproject.org/wiki/Changes/PamBerkeleyDBtoGdbm> for Fedora 40.
The upgrade process would involve a manual procedure where the user needs
to run a conversion tool for the database. Is this acceptable?
An automation process could be created, but the location of the database is
configurable, which increases its complexity and effort. Especially for a
PAM module that is not widely used. Another option I can think of is to
automate the conversion process for the default location, and leave the
manual conversion for those using a tuned location. Would that be
acceptable?
--
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>
8 months, 1 week
Re: zlib-ng as a compat replacement for zlib
by Richard W.M. Jones
On Thu, Aug 31, 2023 at 11:05:55AM +0200, Kevin Wolf wrote:
> [ Cc: qemu-block ]
>
> Am 30.08.2023 um 20:26 hat Richard W.M. Jones geschrieben:
> > On Tue, Aug 29, 2023 at 05:49:24PM -0000, Daniel Alley wrote:
> > > > The background to this is I've spent far too long trying to optimize
> > > > the conversion of qcow2 files to raw files. Most existing qcow2 files
> > > > that you can find online are zlib compressed, including the qcow2
> > > > images provided by Fedora. Each cluster in the file is separately
> > > > compressed as a zlib stream, and qemu uses zlib library functions to
> > > > decompress them. When downloading and decompressing these files, I
> > > > measured 40%+ of the total CPU time is doing zlib decompression.
> > > >
> > > > [You don't need to tell me how great Zstd is, qcow2 supports this for
> > > > compression also, but it is not widely used by existing content.]
>
> You make it sound like compressing each cluster individually has a big
> impact. If so, does increasing the cluster size make a difference, too?
> That could be an change with less compatibility concerns.
The issue we're discussing in the original thread is speed of
decompression. We noted that using zlib-ng (a not-quite drop-in
replacement for zlib) improves decompression speed by 40% or more.
Original thread:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
zlib-ng proposed change:
https://src.fedoraproject.org/rpms/zlib-ng/pull-request/3
Size of the compressed file is also a concern, but wasn't discussed.
> > > Independent from the decision to use zlib-ng as a distro-wide zlib
> > > replacement, which is a good idea regardless.
> > >
> > > Are there reasons why Fedora's qcow2 images cannot switch to Zstd
> > > compression? Zstd support appears to have been added by QEMU 5.1 in
> > > August 2020, and both EL8 and EL9 appear to have newer versions QEMU
> > > available (therefore, they ought to be able to support those
> > > images).
> >
> > TBH I think the most probable reason is that people don't know about
> > it and it is not obvious that you have to enable it. To generate a
> > zlib-compressed qcow2 file, you simply add the -c option, easy. To
> > use zstd compression you have to use this mouthful:
> >
> > qemu-img convert -f raw disk.img -O qcow2 disk.qcow2 -c -o compression_type=zstd
> >
> > The qemu-img man page doesn't even mention it.
>
> Good point, that needs to be fixed.
>
> (Though I don't think that '-o compression_type=zstd' in an unreasonable
> mouthful for enabling a non-standard compression algorithm.)
>
> > I think all recent qcow2-based tools should be fine with zstd, but I
> > didn't check them all (RHEL 7 is still quite popular so that platform
> > would no longer be compatible).
>
> So my first thought was that maybe we can just change the default now
> that the option has been there for quite a while. But then it occurred
> to me that it's not a hard dependency. So at least, the default would
> still have to be zlib if zstd isn't even compiled in, which makes it a
> bit less nice in theory. In practice, it depends on what build options
> distros actually use.
>
> Unfortunately, we seem to build the RHEL packages with --disable-zstd
> (I suppose just because we tend to disable everything nobody explicitly
> asked for). Maybe we should check other distros. If zstd is commonly
> enabled, we could still make it the default upstream (because honestly,
> it probably does makes sense from an upstream perspective). Of course,
> for RHEL this would mean that images out there are likely to use zstd
> soon, so it might need to enable zstd in newer versions, too.
Oh that is bad actually. We really should enable zstd support in RHEL :-/
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
8 months, 1 week
Monitizing Desktop/Workstation Linux
by Ryan Bach
It would be nice if there was that but not just flatpak but rpm, etc as well.
Any thoughts on this topic? Thanks for all the work, hopefully I can pay for it so we can have nice things. Free as in freedom(libre) not free as in (free) beer.
8 months, 1 week
firefox builds seem stuck on the farm - pls check
by Marius Schwarz
Hi,
as mozilla released the updates notes for ff 117, there are a lot of
high impact security fixes for ff 117.
unfortunatly, the ff 117 builds on the farm seem stuck for 40+h ,
according to koji.
I informed Martin, but can someone else take a look too, in case hes
not available?
Thanks.
Best regards,
Marius Schwarz
8 months, 1 week
Non-schedule for Thursday's FESCo meeting (2023-08-31)
by Neal Gompa
There is nothing new with the "meeting" tag and no progress on the
existing one on incomplete changes. I'll chair the next meeting next
week.
There's also nothing to announce either.
--
Neal Gompa (FAS: ngompa)
8 months, 1 week
Fedora 39 compose report: 20230831.n.0 changes
by Fedora Branched Report
OLD: Fedora-39-20230830.n.0
NEW: Fedora-39-20230831.n.0
===== SUMMARY =====
Added images: 9
Dropped images: 2
Added packages: 0
Dropped packages: 0
Upgraded packages: 13
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 92.94 MiB
Size of downgraded packages: 0 B
Size change of upgraded packages: 2.78 MiB
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
Image: Scientific vagrant-virtualbox x86_64
Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-39-20230831.n.0.x86_64.vagrant-virtualbox.box
Image: Scientific_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Scientific_KDE-Live-x86_64-39-20230831.n.0.iso
Image: Scientific vagrant-libvirt x86_64
Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-39-20230831.n.0.x86_64.vagrant-libvirt.box
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-39-20230831.n.0.iso
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-39-20230831.n.0.iso
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-39-20230831.n.0.iso
Image: Astronomy_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-39-20230831.n.0.iso
Image: Security live x86_64
Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-39-20230831.n.0.iso
Image: Robotics live x86_64
Path: Labs/x86_64/iso/Fedora-Robotics-Live-x86_64-39-20230831.n.0.iso
===== DROPPED IMAGES =====
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-39-20230830.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-39-20230830.n.0.iso
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
Package: fwupd-1.9.4-1.fc39
Old package: fwupd-1.9.3-1.fc39
Summary: Firmware update daemon
RPMs: fwupd fwupd-devel fwupd-plugin-flashrom fwupd-plugin-modem-manager fwupd-plugin-uefi-capsule-data fwupd-tests
Size: 23.44 MiB
Size change: 2.29 MiB
Changelog:
* Wed Jul 19 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.9.3-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Fri Aug 11 2023 Mamoru TASAKA <mtasaka(a)fedoraproject.org> - 1.9.3-3
- Rebuild for EVR upgrade path
* Tue Aug 22 2023 Richard Hughes <richard(a)hughsie.com> - 1.9.4-1
- New upstream release
Package: gdm-1:44.1-4.fc39
Old package: gdm-1:44.1-2.fc39
Summary: The GNOME Display Manager
RPMs: gdm gdm-devel gdm-pam-extensions-devel
Size: 4.69 MiB
Size change: -5.67 KiB
Changelog:
* Tue Aug 29 2023 Ray Strode <rstrode(a)redhat.com> - 1:44.1-3
- Add crash fix, initial-setup fix, and simpledrm fix
* Tue Aug 29 2023 Ray Strode <rstrode(a)redhat.com> - 1:44.1-4
- Add crash fix, initial-setup fix, and simpledrm fix (other half)
Package: gnome-control-center-45~rc-2.fc39
Old package: gnome-control-center-45~beta-1.fc39
Summary: Utilities to configure the GNOME desktop
RPMs: gnome-control-center gnome-control-center-filesystem
Size: 27.04 MiB
Size change: 23.23 KiB
Changelog:
* Wed Aug 23 2023 Felipe Borges <felipeborges(a)gnome.org> - 45~beta-2
- Fix crash whe creating a new user account
* Fri Aug 25 2023 Felipe Borges <felipeborges(a)gnome.org> - 45~rc-1
- Update to 45.rc
* Tue Aug 29 2023 Ray Strode <rstrode(a)redhat.com> - 45~rc-2
- Fetch default input sources if not-configured in gsettings
Package: gnome-desktop3-44.0-7.fc39
Old package: gnome-desktop3-44.0-3.fc39
Summary: Library with common API for various GNOME modules
RPMs: gnome-desktop3 gnome-desktop3-devel gnome-desktop3-tests gnome-desktop4 gnome-desktop4-devel
Size: 4.76 MiB
Size change: 65.81 KiB
Changelog:
* Sat Aug 26 2023 Ray Strode <rstrode(a)redhat.com> - 44.0-4
- Add APIs for finding default input sources
* Sat Aug 26 2023 Ray Strode <rstrode(a)redhat.com> - 44.0-5
- Fix typo (s/langtool/langtable/)
* Sat Aug 26 2023 Ray Strode <rstrode(a)redhat.com> - 44.0-6
- Improve APIs for finding default input sources
* Mon Aug 28 2023 Ray Strode <rstrode(a)redhat.com> - 44.0-7
- Still twiddling with the default input sources api
Package: gnome-initial-setup-45~beta-7.fc39
Old package: gnome-initial-setup-45~beta-3.fc39
Summary: Bootstrapping your OS
RPMs: gnome-initial-setup
Size: 2.25 MiB
Size change: 815 B
Changelog:
* Sat Aug 26 2023 Ray Strode <rstrode(a)redhat.com> - 45~beta-4
- Add keyboard and input method handling fixes
* Sat Aug 26 2023 Ray Strode <rstrode(a)redhat.com> - 45~beta-5
- Clean up gnome-desktop requires
* Sat Aug 26 2023 Ray Strode <rstrode(a)redhat.com> - 45~beta-6
- Update to use slightly tweaked default input sources api from gnome-
desktop
* Mon Aug 28 2023 Ray Strode <rstrode(a)redhat.com> - 45~beta-7
- More keyboard configuration updates
Package: gnome-shell-45~beta.1-3.fc39
Old package: gnome-shell-45~beta.1-1.fc39
Summary: Window management and application launching for GNOME
RPMs: gnome-shell
Size: 6.90 MiB
Size change: -4.50 KiB
Changelog:
* Tue Aug 29 2023 Ray Strode <rstrode(a)redhat.com> - 1:45~beta.1-1
- Use input source defaults if not configured in gsettings
* Tue Aug 29 2023 Ray Strode <rstrode(a)redhat.com> - 45~beta.1-1
- Eek, drop the Epoch I just had for testing
* Tue Aug 29 2023 Ray Strode <rstrode(a)redhat.com> - 45~beta.1-3
- Rev release
Package: lorax-39.4-2.fc39
Old package: lorax-39.4-1.fc39
Summary: Tool for creating the anaconda install images
RPMs: lorax lorax-docs lorax-lmc-novirt lorax-lmc-virt lorax-templates-generic
Size: 2.51 MiB
Size change: 2.71 KiB
Changelog:
* Mon Aug 28 2023 Adam Williamson <awilliam(a)redhat.com> - 39.4-2
- Backport PR #1338 to cut qcom firmwares and save space
Package: mailman3-3.3.8-3.fc39
Old package: mailman3-3.3.8-1.fc39
Summary: The GNU mailing list manager
RPMs: mailman3
Size: 2.35 MiB
Size change: -31.70 KiB
Changelog:
* Thu Jul 20 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.3.8-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Tue Aug 29 2023 Michel Lind <salimma(a)fedoraproject.org> - 3.3.8-3
- Restore the required versions of flufl.bounce and flufl.lock
- Use SPDX license identifier; fix license to GPL-3.0-or-later
Package: matrix-synapse-1.90.0-2.fc39
Old package: matrix-synapse-1.86.0-1.fc39
Summary: A Matrix reference homeserver written in Python using Twisted
RPMs: matrix-synapse matrix-synapse+cache_memory matrix-synapse+jwt matrix-synapse+matrix-synapse-ldap3 matrix-synapse+oidc matrix-synapse+postgres matrix-synapse+saml2 matrix-synapse+systemd matrix-synapse+url_preview matrix-synapse+user-search
Size: 18.42 MiB
Size change: 564.24 KiB
Changelog:
* Fri Jul 07 2023 Kai A. Hiller <V02460(a)gmail.com> - 1.87.0-1
- Update to v1.87.0
* Tue Jul 18 2023 Kai A. Hiller <V02460(a)gmail.com> - 1.88.0-1
- Update to v1.88.0
* Thu Jul 20 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.88.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Fri Aug 04 2023 Kai A. Hiller <V02460(a)gmail.com> - 1.89.0-1
- Update to v1.89.0
* Sat Aug 19 2023 Kai A. Hiller <V02460(a)gmail.com> - 1.90.0-1
- Update to v1.90.0
* Mon Aug 28 2023 Kai A. Hiller <V02460(a)gmail.com> - 1.90.0-2
- Support Python 3.12
Package: pyodbc-5.0.0~b1-2.fc39
Old package: pyodbc-4.0.39-2.fc39
Summary: Python DB API 2.0 Module for ODBC
RPMs: python3-pyodbc
Size: 322.30 KiB
Size change: -1.62 KiB
Changelog:
* Tue Jun 13 2023 Python Maint <python-maint(a)redhat.com> - 4.0.39-3
- Rebuilt for Python 3.12
* Fri Jul 21 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 4.0.39-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Mon Aug 28 2023 Ond��ej Sloup <osloup(a)redhat.com> - 5.0.0~b1-1
- Rebase to the newest version, test the beta (rhbz#2235122)
- This release drops Python 2 and adds Python 3.12 support
* Mon Aug 28 2023 Ond��ej Sloup <osloup(a)redhat.com> - 5.0.0~b1-2
- Move /usr/pyodbc.pyi to /usr/lib64/python3.X/site-packages/pyodbc.pyi as originally intended
Package: python-flufl-bounce-4.0-1.fc39
Old package: python-flufl-bounce-3.0-18.fc38
Summary: Email bounce detectors
RPMs: python3-flufl-bounce
Size: 174.64 KiB
Size change: 20.91 KiB
Changelog:
* Mon Jun 19 2023 Python Maint <python-maint(a)redhat.com> - 3.0-19
- Rebuilt for Python 3.12
* Fri Jul 21 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.0-20
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Tue Aug 29 2023 Michel Lind <salimma(a)fedoraproject.org> - 4.0-1
- Update to 4.0
- Use SPDX license identifier
Package: python-pathtools-0.1.2-33.fc39
Old package: python-pathtools-0.1.2-30.fc38
Summary: Pattern matching and various utilities for file systems paths
RPMs: python3-pathtools
Size: 54.41 KiB
Size change: -123.23 KiB
Changelog:
* Wed Jun 14 2023 Python Maint <python-maint(a)redhat.com> - 0.1.2-31
- Rebuilt for Python 3.12
* Fri Jul 21 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 0.1.2-32
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Fri Aug 25 2023 Adam Williamson <awilliam(a)redhat.com> - 0.1.2-33
- Use a hacky patch to get rid of imp usage so it'll build with Python 3.12
Package: rust-pythonize-0.19.0-1.fc39
Old package: rust-pythonize-0.18.0-2.fc39
Summary: Serde Serializer & Deserializer from Rust <--> Python, backed by PyO3
RPMs: rust-pythonize+default-devel rust-pythonize-devel
Size: 25.95 KiB
Size change: 146 B
Changelog:
* Tue Aug 22 2023 Kai A. Hiller <V02460(a)gmail.com> - 0.19.0-1
- Update to v0.19.0
===== DOWNGRADED PACKAGES =====
8 months, 1 week