Orphaned packages looking for new maintainers
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will fail to install and/or build when the affected package gets retired. Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/ Full report available at: https://churchyard.fedorapeople.org/orphans-2023-02-20.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager-dashboard.fedoraproject.org/ For all orphaned packages, see https://packager-dashboard.fedoraproject.org/orphan Package (co)maintainersStatus Change == belle-sip orphan, sdgathman 4 weeks ago emelfm2 orphan 0 weeks ago fbpanel orphan 0 weeks ago golang-github-deepmap-oapi-codegengo-sig, orphan 4 weeks ago golang-github-deislabs-oras go-sig, orphan 5 weeks ago golang-github-skynetservices-skydns go-sig, jchaloup, orphan 4 weeks ago gtrayicon orphan 0 weeks ago gxmessage orphan 0 weeks ago humanity-icon-theme orphan 5 weeks ago libeXosip2orphan 4 weeks ago libosip2 orphan 4 weeks ago light-themes orphan 5 weeks ago lilyterm orphan 0 weeks ago linphone orphan, sdgathman 4 weeks ago lxpolkit orphan 0 weeks ago lxsession-editorphan 0 weeks ago maildirproc orphan 0 weeks ago nimbusorphan 0 weeks ago parcelliteorphan 0 weeks ago preferences-menus orphan 0 weeks ago python3-pyPEG2orphan 0 weeks ago regexxer orphan 0 weeks ago rubygem-jquery-rails orphan 2 weeks ago rubygem-uglifier orphan 1 weeks ago taggleorphan 1 weeks ago xgammaajax, ofourdan, orphan 1 weeks ago The following packages require above mentioned packages: Depending on: golang-github-deepmap-oapi-codegen (6), status change: 2023-01-19 (4 weeks ago) golang-github-exoscale-egoscale (maintained by: carlwgeorge, go-sig) golang-github-exoscale-egoscale-0.38.0-6.fc38.src requires golang(github.com/deepmap/oapi-codegen/pkg/runtime) = 1.8.2-6.fc38 golang-github-exoscale-egoscale-devel-0.38.0-6.fc38.noarch requires golang(github.com/deepmap/oapi-codegen/pkg/runtime) = 1.8.2-6.fc38 golang-github-acme-lego (maintained by: eclipseo, go-sig) golang-github-acme-lego-4.4.0-8.fc37.src requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-acme-lego-devel-4.4.0-8.fc37.noarch requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-acme-lego-3 (maintained by: eclipseo, go-sig) golang-github-acme-lego-3-3.9.0-7.fc37.src requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-acme-lego-3-devel-3.9.0-7.fc37.noarch requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-caddyserver-caddy-1 (maintained by: eclipseo, go-sig) golang-github-caddyserver-caddy-1-1.0.4-11.fc38.src requires golang(github.com/go-acme/lego/v3/certcrypto) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge/tlsalpn01) = 3.9.0-7.fc37 golang-github-caddyserver-caddy-1-devel-1.0.4-11.fc38.noarch requires golang(github.com/go-acme/lego/v3/certcrypto) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge/tlsalpn01) = 3.9.0-7.fc37 golang-github-coredns-corefile-migration (maintained by: eclipseo, go-sig) golang-github-coredns-corefile
Re: Creating a F37 remix/spin LiveCD without a desktop environment
On Sunday, February 19, 2023 at 09:25:50 PM CST, Neal Gompa wrote: On Sun, Feb 19, 2023 at 9:33 PM Globe Trotter via devel wrote: > > Hello, > > Since about Fedora 20 or so, I have been rolling my own Fedora spin without a > desktop environment, and with openbox and slim (simple login manager). All > worked well, because I did not need to roll these that often, with dnf > upgrade on existing installations, except up until now when I need a new > LiveCD for a new machine coming online. I last successfully made a LiveCD > with Fedora 34. > > Recently, I went back to making a live cd for Fedora 37, and realized that > there is a new way of handling these: specifically, I have to install > env-group to resolve RH Bug:1891500. > > With an environment, it turns out one has to do something like > > > @^lxde-desktop-environment > > but I do not want an environment. > > > Can I get a LiveCD environment without all this, and with slim? > > Yes, you can just avoid using environment groups altogether. The bug you > reference should not apply in your case. -- Thanks! Not? but it does not work. A LiveCD is created if I do not add that line to my ks, but. I get something that hangs when the LiveCD boots. Did not happen before. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Creating a F37 remix/spin LiveCD without a desktop environment
On Sun, Feb 19, 2023 at 9:33 PM Globe Trotter via devel wrote: > > Hello, > > Since about Fedora 20 or so, I have been rolling my own Fedora spin without a > desktop environment, and with openbox and slim (simple login manager). All > worked well, because I did not need to roll these that often, with dnf > upgrade on existing installations, except up until now when I need a new > LiveCD for a new machine coming online. I last successfully made a LiveCD > with Fedora 34. > > Recently, I went back to making a live cd for Fedora 37, and realized that > there is a new way of handling these: specifically, I have to install > env-group to resolve RH Bug:1891500. > > With an environment, it turns out one has to do something like > > > @^lxde-desktop-environment > > but I do not want an environment. > > I tried putting this in, and removing all the LXDE things > > -@'Dial-up Networking Support' > -@LXDE > -@Fonts > -@'LXDE Desktop' > -@'Multimedia' > -@base-x > -@core > -@fonts > -@'Guest Desktop Agents' > -@'Input Methods' > -@'Printing' > -@'Hardware Support' > -lxpanel > -lxlauncher > -libfm > -menu-cache > -pcmanfm > -lxde-common > > and this works, but not quite. I still get large components of the LXDE > environment, slim (which I roll my personal rpm of) does not get started, and > I get a slower system. > I tried explicitly getting rid of the following that I could see: > > -clipit > -galculator > -dnfdragora > -dnfdragora-updater > -xpad > -icon > -xarchiver > -xscreensaver > -gigolo > -samba\* > -firewall-config > -firewalld > -lx\* > > but still, there are lx\* things in the LiveCD. > > Can I get a LiveCD environment without all this, and with slim? > Yes, you can just avoid using environment groups altogether. The bug you reference should not apply in your case. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Creating a F37 remix/spin LiveCD without a desktop environment
Hello, Since about Fedora 20 or so, I have been rolling my own Fedora spin without a desktop environment, and with openbox and slim (simple login manager). All worked well, because I did not need to roll these that often, with dnf upgrade on existing installations, except up until now when I need a new LiveCD for a new machine coming online. I last successfully made a LiveCD with Fedora 34. Recently, I went back to making a live cd for Fedora 37, and realized that there is a new way of handling these: specifically, I have to install env-group to resolve RH Bug:1891500. With an environment, it turns out one has to do something like @^lxde-desktop-environment but I do not want an environment. I tried putting this in, and removing all the LXDE things -@'Dial-up Networking Support' -@LXDE -@Fonts -@'LXDE Desktop' -@'Multimedia' -@base-x -@core -@fonts -@'Guest Desktop Agents' -@'Input Methods' -@'Printing' -@'Hardware Support' -lxpanel -lxlauncher -libfm -menu-cache -pcmanfm -lxde-common and this works, but not quite. I still get large components of the LXDE environment, slim (which I roll my personal rpm of) does not get started, and I get a slower system. I tried explicitly getting rid of the following that I could see: -clipit -galculator -dnfdragora -dnfdragora-updater -xpad -icon -xarchiver -xscreensaver -gigolo -samba\* -firewall-config -firewalld -lx\* but still, there are lx\* things in the LiveCD. Can I get a LiveCD environment without all this, and with slim? Thanks! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Feedback wanted for a proposed improvement to RPM's ELF dependency generator
On Sun, Feb 19, 2023 at 1:22 AM Gordon Messmer wrote: > > On 2023-02-18 15:53, Fabio Valentini wrote: > > I see a big hole in that problem (assuming that I understand Things > > correctly): What happens to packages where this .so.x.y.z pattern does > > not match their actual version? > > In this implementation, there is no relationship between the version of > the shared object and the package version. > > libnghttp2-1.51.0-1.fc37, for example, will "Provides: > libnghttp2.so.14()(64bit) = 14.24.1", and any package that is linked to > that shared object will "Requires: libnghttp2.so.14()(64bit) >= 14.24.1" > > > I have seen many packages that don't > > follow this pattern, for example, some keep .so.0.0.0 forever and just > > bump the library name instead of the soname (looking at you, mutter). > > That will continue to work more or less as it does today. Mutter will > provide "libmutter-11.so.0()(64bit) = 0.0.0" and linked packages will > require "libmutter-11.so.0()(64bit) >= 0.0.0". If Mutter bumps the > library name, that's a breaking change just like the status quo. > > > Others bump their soname very rarely, so the library itself might have > > version 2.3.4 but the soname is still at libfoo.so.1.0.0. > > That's also fine, although if they are making any kind of changes to > their public interface, then they are failing to indicate that, and we > end up in the same situation we're in today. Which is to say that if > that library adds new interfaces and later package builds use those > interfaces, then there's no information about that dependency and rpm > might install software that doesn't actually work. > > However, today we deal with that (as curl does) by checking package > versions during the build and more or less manually doing what this > proposed change would do automatically. In the future, we might deal > with that by pushing the upstream developers to actually provide > information about their interface versions. If not through versioned > symbols, then *at least* through giving libtool a version number. > > > The opposite > > also happens, with packages bumping soname basically with every release, > > so libfoo 0.11.2 can provide libfoo.so.143.0.0 ... > > If they're incrementing from libfoo.so.142.0.0 (and, consequently, > libfoo.so.142) to libfoo.so.143.0.0 (libfoo.so.143), then that's a > breaking change both today and in the proposed system. I see, thanks for the clarification! I assumed that you're going to use the RPM version since you're shoving this data inside RPM's standard " " syntax for Provides / Requires, but if you're using the soversion instead, then the discrepancy between project version and library version doesn't matter. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-02-20 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-02-20 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.libera.chat Greetings testers! It's meeting time! F38 has branched and we'll be heading for Beta shortly. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 38 status * SHA-1 signed RPM issues: https://bugzilla.redhat.com/show_bug.cgi?id=2170878 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Feedback wanted for a proposed improvement to RPM's ELF dependency generator
On 2023-02-19 12:30, Stephen Smoogen wrote: > - You mention "over the course of two releases" but don't mention what > is done in each one? I don't know the specifics of how package builds are ordered in a mass rebuild, so I tend to think the safest rollout is a slow one: enable the I think they are usually done 'alphabetically' with various subgroups done in 'order by the maintainer' beforehand (or afterwards if the mass rebuild broke it) as additional side-tags. If there's no dependency ordering in the mass rebuild, then I think the shortest possible timeline for enabling both macros would be to enable _elf_provide_fallback_versions globally, wait for the next mass rebuild, and then globally enable the _elf_require_fallback_versions macro. At that point, dependencies should have been made consistent by the mass rebuild, and improved dependency information should be generated as it's needed (as packages are built after the mass rebuild). However, FTBFS very probably means that a short timeline like that would be difficult, as once _elf_require_fallback_versions was enabled globally any packages that depend on something that didn't rebuild would need to be opted out of the system temporarily by disabling _elf_require_fallback_versions in their spec file. So, it might be preferable to roll out that half of the system later. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Feedback wanted for a proposed improvement to RPM's ELF dependency generator
On Sat, 18 Feb 2023 at 14:40, Gordon Messmer wrote: > On 2023-02-18 10:33, Kevin Fenzi wrote: > > > > - What Fedora release(es) are you targeting here? > > I'd appreciate guidance from more senior project members on that point. > > > - You mention "over the course of two releases" but don't mention what > >is done in each one? > > I don't know the specifics of how package builds are ordered in a mass > rebuild, so I tend to think the safest rollout is a slow one: enable the I think they are usually done 'alphabetically' with various subgroups done in 'order by the maintainer' beforehand (or afterwards if the mass rebuild broke it) as additional side-tags. -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Feedback wanted for a proposed improvement to RPM's ELF dependency generator
On 2023-02-19 05:15, Björn Persson wrote: Gordon Messmer wrote: If a maintainer enabled the _elf_require_fallback_versions macro before a mass rebuild where the _elf_provide_fallback_versions macro had been enabled globally, then the resulting package would have versioned dependencies, and the packages it depends on might not have versioned dependencies. That package wouldn't be installable. It seems to me that it would be much safer if the dependency generator would verify that the library package actually provides the generated dependency. As you noted at the end of your message, that would involve querying the rpm DB from the ELF dependency generator, which the rpm maintainers want to avoid. If _elf_provide_fallback_versions is turned off in a single package for whatever reason, then dependent packages should only need rebuilding to pick up the unversioned dependency. The maintainers of the dependent packages shouldn't have to turn off _elf_require_fallback_versions manually. Unfortunately, I don't see a way around that. Unless I'm missing something, the ELF dependency generator does not verify that the providing package has versioned symbols in its "Provides:" list, so maintainers have to manually instruct it to use "--soname-only" (or disable automatic dependency generation entirely) to opt out. The same would be true for this feature. There are always some failures in each mass rebuild. If library L fails to build in Fedora N, and fails again in Fedora N+1, then under the current policy, L will be retired from Fedora N+2. Yes, that's a good point. Depending on the nature of the FTBFS, and the breadth of their dependencies, it may be easier to delay globally enabling _elf_require_fallback_versions to a later release than to unset _elf_require_fallback_versions in the packages that depend on FTBFS packages. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Feedback wanted for a proposed improvement to RPM's ELF dependency generator
On 2023-02-19 04:19, Reindl Harald (privat) wrote: Am 19.02.23 um 00:26 schrieb Gordon Messmer: *: I have to guess that this mariadb-libs package "Provides: libmysqlclient.so.18()(64bit)"... please tell me if you mean something else. is explained the point is "mariadb-connector-c" Then, I'm afraid I don't understand. The dependency generator change should not impact existing Provides/Obsoletes specs that reference package names. Your example should continue to work as it does today. The mariadb-connector-c package does provide a library, but that library uses versioned symbols, so the new ELF dependency generator will generate the same output that it does today, for both the library that the package provides and for anything linked against it. If you have questions about the change, the most helpful thing for me would be an example of a package with either a requirement or dependency in the form of "Requires: libz.so.1()(64bit)" or "Provides: libz.so.1()(64bit)" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F38 proposal: IPP-USB as a weak dependency of CUPS and sane-airscan (Self-Contained Change proposal)
Zdenek Dohnal wrote: > On 1/16/23 12:31, Björn Persson wrote: > > Robert Marcano via devel wrote: > >> The admin can implement CUPS > >> authentication but an ipp://localhost:6 open port entirely open to > >> anyone on the local machine to submit print jobs directly bypassing CUPS. > > > > In that case it's also accessible to all the untrusted Javascript junk > > that regularly runs in the user's browser. Because IPP is built on HTTP, > > a Javascript program can tell the browser to send an IPP request. What > > has been done to secure those "virtual printer devices" against DNS > > rebinding attacks? > > https://en.wikipedia.org/wiki/DNS_rebinding > > I'll ask IPP-USB upstream about it, stay tuned. What did upstream answer? Björn Persson pgp52ZeVNAUhQ.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Feedback wanted for a proposed improvement to RPM's ELF dependency generator
Gordon Messmer wrote: > If a maintainer enabled the _elf_require_fallback_versions macro > before a mass rebuild where the _elf_provide_fallback_versions macro > had been enabled globally, then the resulting package would have > versioned dependencies, and the packages it depends on might not have > versioned dependencies. That package wouldn't be installable. It seems to me that it would be much safer if the dependency generator would verify that the library package actually provides the generated dependency. If _elf_provide_fallback_versions is turned off in a single package for whatever reason, then dependent packages should only need rebuilding to pick up the unversioned dependency. The maintainers of the dependent packages shouldn't have to turn off _elf_require_fallback_versions manually. There are always some failures in each mass rebuild. If library L fails to build in Fedora N, and fails again in Fedora N+1, then under the current policy, L will be retired from Fedora N+2. If you turn on _elf_provide_fallback_versions in Fedora N, and then turn on _elf_require_fallback_versions in Fedora N+1, then any packages that use L will become uninstallable in Fedora N+1, half a year before L will be retired. Therefore, if you're going to rely on the FTBFS retirement process to ensure that all libraries provide version numbers, then you shouldn't turn on _elf_require_fallback_versions before Fedora N+2. Once the dependency generator has found the filename it gets the version number from, it would be easy to run rpm --query --provides --file | grep --quiet ^$ except that people keep saying that package builds shouldn't invoke RPM for some reason. Is there a way to do the above without actually invoking RPM? Björn Persson pgpM_h8XhTJd4.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 compose report: 20230219.n.0 changes
OLD: Fedora-38-20230218.n.0
NEW: Fedora-38-20230219.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 10
Dropped packages:1
Upgraded packages: 49
Downgraded packages: 1
Size of added packages: 746.93 KiB
Size of dropped packages:9.57 KiB
Size of upgraded packages: 486.70 MiB
Size of downgraded packages: 6.34 MiB
Size change of upgraded packages: 1.09 MiB
Size change of downgraded packages: -12.77 KiB
= ADDED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230219.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path:
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-38-20230219.n.0.iso
= DROPPED IMAGES =
= ADDED PACKAGES =
Package: cargo2rpm-0.1.2-1.fc38
Summary: Translation layer between cargo and RPM
RPMs:cargo2rpm
Size:84.94 KiB
Package: rust-ansi-str-0.7.2-1.fc38
Summary: Library which provides a set of methods to work with ANSI strings
RPMs:rust-ansi-str+default-devel rust-ansi-str-devel
Size:31.51 KiB
Package: rust-ansi-str0.5-0.5.0-1.fc38
Summary: Library which provides a set of methods to work with ANSI strings
RPMs:rust-ansi-str0.5+default-devel rust-ansi-str0.5-devel
Size:29.88 KiB
Package: rust-ansitok-0.2.0-1.fc38
Summary: Library for parsing ANSI Escape Codes
RPMs:rust-ansitok+default-devel rust-ansitok+std-devel rust-ansitok-devel
Size:44.51 KiB
Package: rust-nu-color-config-0.75.0-1.fc38
Summary: Color configuration code used by Nushell
RPMs:rust-nu-color-config+default-devel rust-nu-color-config-devel
Size:27.96 KiB
Package: rust-papergrid-0.7.1-2.fc38
Summary: Core library to print a table
RPMs:rust-papergrid+ansi-str-devel rust-papergrid+ansitok-devel
rust-papergrid+color-devel rust-papergrid+default-devel rust-papergrid-devel
Size:82.25 KiB
Package: rust-procfs0.12-0.12.0-1.fc38
Summary: Interface to the linux procfs pseudo-filesystem
RPMs:rust-procfs0.12+backtrace-devel rust-procfs0.12+chrono-devel
rust-procfs0.12+default-devel rust-procfs0.12+flate2-devel rust-procfs0.12-devel
Size:135.39 KiB
Package: rust-tabled-0.10.0-2.fc38
Summary: Easy to use library for pretty print tables of Rust `struct`s and
`enum`s
RPMs:rust-tabled+ansi-str-devel rust-tabled+color-devel
rust-tabled+default-devel rust-tabled+derive-devel rust-tabled+macros-devel
rust-tabled+tabled_derive-devel rust-tabled-devel
Size:202.28 KiB
Package: rust-tabled_derive-0.5.0-1.fc38
Summary: Derive macros which is used by tabled crate
RPMs:rust-tabled_derive+default-devel rust-tabled_derive-devel
Size:23.36 KiB
Package: rust2rpm-24.0.2-1.fc38
Summary: Generate RPM spec files for Rust crates
RPMs:rust2rpm
Size:84.87 KiB
= DROPPED PACKAGES =
Package: rust-srpm-macros-23-2.fc38
Summary: RPM macros for building Rust source packages
RPMs:rust-srpm-macros
Size:9.57 KiB
= UPGRADED PACKAGES =
Package: audacious-plugins-4.2-5.fc38
Old package: audacious-plugins-4.2-4.fc38
Summary: Plugins for the Audacious audio player
RPMs: audacious-plugins audacious-plugins-amidi
audacious-plugins-exotic audacious-plugins-ffaudio audacious-plugins-jack
Added RPMs: audacious-plugins-ffaudio
Size: 8.38 MiB
Size change: 52.92 KiB
Changelog:
* Mon Feb 13 2023 Michael Schwendt - 4.2-5
- Merge ffmpeg/ffaudio PR but prefer pkgconfig(foo) BR.
Package: chromium-110.0.5481.100-1.fc38
Old package: chromium-110.0.5481.77-1.fc38
Summary: A WebKit (Blink) powered web browser that Google doesn't want you
to use
RPMs: chromedriver chromium chromium-common chromium-headless
Size: 252.66 MiB
Size change: -40.64 KiB
Changelog:
* Thu Feb 16 2023 Than Ngo - 110.0.5481.77-2
- fix #2071126, enable support V4L2 stateless decoders for aarch64 plattform
- fix prefers-color-scheme
- drop snapshot_blob.bin, replace snapshot_blob.bin with
v8_context_snapshot.bin
- move headless_lib*.pak to headless subpackage
* Fri Feb 17 2023 Than Ngo - 110.0.5481.100-1
- update to 110.0.5481.100
Package: conan-2.0.0-0.10.beta10.fc38
Old package: conan-2.0.0-0.9.beta9.fc38
Summary: Open-source C/C++ package manager
RPMs: conan
Size: 1.04 MiB
Size change: 2.41 KiB
Changelog:
* Sat Feb 18 2023 Vitaly Zaitsev - 2.0.0-0.10.beta10
- Updated to version 2.0.0-beta10.
Package: dd_rescue-1.99.12-3.fc38
Old package: dd_rescue-1.99.12-2.fc38
Summary: Fault tolerant "dd" utility for rescuing data from bad media
RPMs: dd_rescue
Size: 773.27 KiB
Size change: 1.09 KiB
Changelog:
* Sat Feb 18 2023 Michal Ambroz - 1.99.12-3
- dd_rhelp - fix dependencies and dd_rescue detection
Package: dino-0.4.0-1.fc38
Old package: dino-0.3.1-3.fc38
Summary: Modern XMPP ("Jabber") Chat Client using GTK+/Vala
RPMs: dino dino-devel
Size: 8.34 MiB
Size chan
[Test-Announce] Fedora 38 Branched 20230219.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 38 Branched 20230219.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: lorax - 20230216.n.0: lorax-38.6-2.fc38.src, 20230219.n.0: lorax-38.6-3.fc38.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/38 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230219.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230219.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230219.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230219.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230219.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230219.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230219.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230219.n.0 changes
OLD: Fedora-Rawhide-20230218.n.0
NEW: Fedora-Rawhide-20230219.n.0
= SUMMARY =
Added images:3
Dropped images: 2
Added packages: 6
Dropped packages:0
Upgraded packages: 45
Downgraded packages: 1
Size of added packages: 423.64 KiB
Size of dropped packages:0 B
Size of upgraded packages: 599.02 MiB
Size of downgraded packages: 6.34 MiB
Size change of upgraded packages: 4.82 MiB
Size change of downgraded packages: -12.08 KiB
= ADDED IMAGES =
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230219.n.0.iso
Image: Cloud_Base raw-xz s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20230219.n.0.s390x.raw.xz
Image: Cloud_Base qcow2 s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20230219.n.0.s390x.qcow2
= DROPPED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20230218.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path:
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230218.n.0.iso
= ADDED PACKAGES =
Package: perl-App-cpanminus-1.7046-4.module_f39+16205+f149e3ae
Summary: Get, unpack, build and install CPAN modules
RPMs:perl-App-cpanminus
Size:172.97 KiB
Package: perl-CPAN-Meta-Check-0.017-2.module_f39+16205+f149e3ae
Summary: Verify requirements in a CPAN::Meta object
RPMs:perl-CPAN-Meta-Check
Size:40.82 KiB
Package: perl-File-pushd-1.016-16.module_f39+16205+f149e3ae
Summary: Change directory temporarily for a limited scope
RPMs:perl-File-pushd
Size:47.06 KiB
Package: perl-Module-CPANfile-1.1004-16.module_f39+16205+985b4b0c
Summary: Parse cpanfile
RPMs:perl-Module-CPANfile
Size:80.22 KiB
Package: perl-Parse-PMFile-0.43-8.module_f39+16205+985b4b0c
Summary: Parses .pm file as PAUSE does
RPMs:perl-Parse-PMFile
Size:45.00 KiB
Package: perl-String-ShellQuote-1.04-38.module_f39+16205+f149e3ae
Summary: Perl module for quoting strings for passing through the shell
RPMs:perl-String-ShellQuote
Size:37.58 KiB
= DROPPED PACKAGES =
= UPGRADED PACKAGES =
Package: asciidoc-10.2.0-1.fc39
Old package: asciidoc-9.1.0-7.fc38
Summary: Text based document generation
RPMs: asciidoc asciidoc-doc asciidoc-latex
Size: 668.18 KiB
Size change: 260.23 KiB
Changelog:
* Sat Feb 11 2023 Fabian Affolter - 10.2.0-1
- Update to latest upstream release 10.2.0
Package: audacious-4.3-0.2.beta1.fc39
Old package: audacious-4.2-3.fc38
Summary: Advanced audio player
RPMs: audacious audacious-devel audacious-libs
Size: 3.34 MiB
Size change: 8.14 KiB
Changelog:
* Mon Feb 13 2023 Michael Schwendt -
4.3-0.1.beta1
- Upgrade to 4.3 beta1.
* Sat Feb 18 2023 Michael Schwendt -
4.3-0.2.beta1
- Explicitly --disable-libarchive to confirm default.
Package: audacious-plugins-4.3-0.1.beta1.fc39
Old package: audacious-plugins-4.2-5.fc39
Summary: Plugins for the Audacious audio player
RPMs: audacious-plugins audacious-plugins-amidi
audacious-plugins-exotic audacious-plugins-ffaudio audacious-plugins-jack
Size: 8.42 MiB
Size change: 8.86 KiB
Changelog:
* Mon Feb 13 2023 Michael Schwendt -
4.3-0.1.beta1
- Upgrade to 4.3 beta1.
- Opus input plugin is new.
- Pipewire output plugin is new.
- Alarm plugin is gone.
Package: chromium-110.0.5481.100-1.fc39
Old package: chromium-110.0.5481.77-2.fc39
Summary: A WebKit (Blink) powered web browser that Google doesn't want you
to use
RPMs: chromedriver chromium chromium-common chromium-headless
Size: 252.70 MiB
Size change: 29.47 KiB
Changelog:
* Fri Feb 17 2023 Than Ngo - 110.0.5481.100-1
- update to 110.0.5481.100
Package: conan-2.0.0-0.10.beta10.fc39
Old package: conan-2.0.0-0.9.beta9.fc38
Summary: Open-source C/C++ package manager
RPMs: conan
Size: 1.04 MiB
Size change: 2.24 KiB
Changelog:
* Sat Feb 18 2023 Vitaly Zaitsev - 2.0.0-0.10.beta10
- Updated to version 2.0.0-beta10.
Package: dd_rescue-1.99.12-3.fc39
Old package: dd_rescue-1.99.12-2.fc38
Summary: Fault tolerant "dd" utility for rescuing data from bad media
RPMs: dd_rescue
Size: 773.26 KiB
Size change: 1.09 KiB
Changelog:
* Sat Feb 18 2023 Michal Ambroz - 1.99.12-3
- dd_rhelp - fix dependencies and dd_rescue detection
Package: dino-0.4.0-1.fc39
Old package: dino-0.3.1-3.fc38
Summary: Modern XMPP ("Jabber") Chat Client using GTK+/Vala
RPMs: dino dino-devel
Size: 8.34 MiB
Size change: 351.57 KiB
Changelog:
* Sat Feb 18 2023 Randy Barlow - 0.4.0-1
- Update to dino 0.4.0 (#2168027).
Package: freeipa-fas-0.0.8-1.fc39
Old package: freeipa-fas-0.0.6-7.fc38
Summary: Fedora Account System extension for FreeIPA
RPMs: freeipa-fas
Size: 56.13 KiB
Size change: -15 B
Changelog:
* Sat Feb 18 2
