Re: FSL license

On 30/05/2020 12:00, Ankur Sinha wrote: However, the License that the Oxford University has released it under has certain clauses that make me unsure if it is OK for inclusion in Fedora. Could someone please have a look? https://fsl.fmrib.ox.ac.uk/fsl/fslwiki/Licence The "solely for non-comme

Re: Need assistance to build ispc

On 09/06/2020 08:54, Kalev Lember wrote: The build failed with: /builddir/build/BUILD/ispc-1.13.0/src/bitcode_lib.cpp: In member function 'void BitcodeLib::print() const': /builddir/build/BUILD/ispc-1.13.0/src/bitcode_lib.cpp:61:17: error: variable 'type' set but not used [-Werror=unused-but-

Re: The future of legacy BIOS support in Fedora.

On 30/06/2020 15:00, Florian Weimer wrote: * Jóhann B. Guðmundsson: Given Hans proposal [1] introduced systemd/grub2/Gnome upstream changes it beg the question if now would not be the time to stop supporting booting in legacy bios mode and move to uefi only supported boot which has been availab

Re: The future of legacy BIOS support in Fedora.

On 30/06/2020 14:56, Igor Raits wrote: I think there are many people still install OS in the legacy mode, but I don't really have numbers. One thing we should definitely do if we deprecate legacy BIOS is to properly warn users that still use this configuration, develop tooling for them if possib

Re: The future of legacy BIOS support in Fedora.

On 30/06/2020 15:25, Marcin Juszkiewicz wrote: W dniu 30.06.2020 o 16:20, Tom Hughes via devel pisze: On 30/06/2020 15:00, Florian Weimer wrote: * Jóhann B. Guðmundsson: Given Hans proposal [1] introduced systemd/grub2/Gnome upstream changes it beg the question if now would not be the time

Re: Better Thermal Management for the Workstation - Fedora 33 Self-Contained Change proposal

On 01/07/2020 11:53, Richard W.M. Jones wrote: On Tue, Jun 30, 2020 at 10:30:21AM -0400, Owen Taylor wrote: So, this was discussed quite a bit in https://pagure.io/fedora-workstation/issue/71 and the conclusion that the Workstatopn Working Group came to 3 months ago was that we didn't want to do

Orphaning og my nodejs packages

I have orphaned all my nodejs packages - feel free to grab though be aware that in many cases they have hopeless dependency issues. Full list of affected packages: carto jake kosmtik lodash node-gyp nodejs-agentkeepalive nodejs-ap nodejs-array-differ nodejs-array-union nodejs-arrify nodejs-asser

Re: pagure pull-request email workflow

On 21/07/2020 11:56, Mark Wielaard wrote: Do you have to handle them on that pagure website? Is it possible to handle these pull-request through email? Or is there a normal (git) command line interface for these? Pagure supports the same pull heads are things like github so yes you can just fe

Re: pagure pull-request email workflow

On 21/07/2020 13:12, Mark Wielaard wrote: I normally just edit .git/config and add to the origin remote an extra fetch: fetch = +refs/pull/*/head:refs/remotes/origin/pull/* then after fetching you can merge origin/pull/NNN. But this is very helpful! Thanks. So with that I can easily do chec

Re: pagure pull-request email workflow

On 22/07/2020 13:19, Mark Wielaard wrote: As you say, the web api is even more resourceful and we can integrate some of those requests into the library: https://pagure.io/api/ The only thing that is not very nice are those pagure_tokens. I was hoping you could get a temporary one through simple

Re: pagure pull-request email workflow

On 22/07/2020 15:59, Mark Wielaard wrote: That is not how I understand the current situation. CPE has a proposal to provide a forge for use by the fedora project possibly based on gitlab, but pagure wouldn't go away. I think you may be behind the times. The pretend consultation is over and th

Re: Fedora 33 System-Wide Change proposal: ELN Buildroot and Compose

On 24/03/2020 12:08, Vít Ondruch wrote: Dne 24. 03. 20 v 11:43 Tom Hughes via devel napsal(a): On 24/03/2020 09:32, Aleksandra Fedorova wrote: ELN is an evolution of the request for an alternate buildroot for newer x86_64 processors. The reasoning behind that new buildroot was that we

Re: Fedora 33 System-Wide Change Proposal: ELN Buildroot and Compose V4

On 06/04/2020 22:53, Stephen Gallagher wrote: Changes in this version of the proposal[2]: * Improve our explanation of why we are doing ELN in the first place I agree that the proposal is now a lot clearer and I certainly see how it furthers the first goral of seeing how Fedora trunk comes to

Re: Fedora 33 System-Wide Change proposal: systemd-resolved

On 15/04/2020 09:08, Florian Weimer wrote: I cannot find documentation of the systemd stub resolver behavior: how it handles search list processing, and how it decides which upstream name servers to query. As I understand the terminology the "stub resolver" in systemd-resolved refers to the th

Re: Fedora 33 System-Wide Change proposal: systemd-resolved

On 15/04/2020 09:29, Tom Hughes via devel wrote: > I'm not sure what happens if there are multiple interfaces with > no specific routing but I think it may try them all? Found the documentation now - it does try them all. Full details from systemd-resolved(8) are: Lookup r

Re: Fedora 33 System-Wide Change proposal: systemd-resolved

On 15/04/2020 09:53, Florian Weimer wrote: > Thanks. Does this mean that no search list processing happens, for > neither single-label names (per for the first paragraph), nor for > multi-label names (per the routing description)? Or is this process > described in some other context? That text

Re: Fedora 33 System-Wide Change proposal: systemd-resolved

On 15/04/2020 09:48, Florian Weimer wrote: >>> Is this expected to work with the Red Hat VPN out of the box, or do we >>> have to disable all this and use a custom configuration? Has this been >>> discussed with Infosec? It looks like this will break their DNS >>> sinkholing for domains such as

Re: Fedora 33 System-Wide Change proposal: systemd-resolved

On 15/04/2020 10:14, Vitaly Zaitsev via devel wrote: On 14.04.2020 21:23, Ben Cotton wrote: Enable systemd-resolved by default. glibc will perform name resolution using nss-resolve rather than nss-dns. I've tested systemd-resolved on my laptop for a month. It worked very, very unstable. Someti

Re: Fedora 33 System-Wide Change proposal: systemd-resolved

On 16/04/2020 11:46, Florian Weimer wrote: * Lennart Poettering: Long story short: if you experienced issues with DNSSEC on with resolved today, then be assured that with DNSSEC off things are much much better, and that's how we'd ship it in Fedora if it becomes the default. Would you please

Re: Fedora 33 System-Wide Change proposal: Node.js 14.x by default

On 08/05/2020 21:18, Stephen Gallagher wrote: On Sat, May 2, 2020 at 6:26 PM Miro Hrončok wrote: On 01. 05. 20 22:21, Ben Cotton wrote: * Proposal owners: The packages are already built for Fedora 33 in a non-default module stream. On June 14th, 2020, the nodejs-14.x packages will become the

Re: Fedora 33 System-Wide Change proposal: Node.js 14.x by default

On 11/05/2020 13:02, Stephen Gallagher wrote: On Fri, May 8, 2020 at 6:03 PM Tom Hughes wrote: On 08/05/2020 21:18, Stephen Gallagher wrote: On Sat, May 2, 2020 at 6:26 PM Miro Hrončok wrote: On 01. 05. 20 22:21, Ben Cotton wrote: * Proposal owners: The packages are already built for Fedo

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On 12/05/2020 14:13, Petr Pisar wrote: On Tue, May 12, 2020 at 12:47:51PM +, virgo wrote: I recommend you to ask the question about v2 support on Fedora Bugzilla for= the libcgroup package

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On 12/05/2020 15:06, virgo wrote: Let’s say I want to compile `pandoc` with modifications of my own and many non- default compiler options. At the same time, on the same machine, I still want to do other stuff. `cgexec` et al. helped a lot to cap the memory and CPU usage of tasks like that, with

Re: Help with gcc10-arm-only problem

On 01/03/2020 16:44, Sergio Pascual wrote: The package build in all arches except in arm an the error is: /builddir/build/BUILD/libindi-1.8.1/libs/indibase/inditelescope.cpp: In member function 'bool INDI::Telescope::processTimeInfo(const char*, const char*)': /builddir/build/BUILD/libindi-1.

Re: bodhi web interface (not associating bugzilla entries)

On 19/03/2020 10:19, José Abílio Matos wrote: when entering a new update through the web interface of bodhi I do not get the list of open bugs in bugzilla, no mater the wait. There is a rotating symbol as it happens to select the build(s) but I continues without any output. Are you usi

Re: Fedora 33 System-Wide Change proposal: ELN Buildroot and Compose

On 24/03/2020 09:32, Aleksandra Fedorova wrote: ELN is an evolution of the request for an alternate buildroot for newer x86_64 processors. The reasoning behind that new buildroot was that we expected that the next major release of RHEL would likely drop support for older hardware and therefore c

Re: It’s time to transform the Fedora devel list into something new

On 21/04/2023 18:52, Matthew Miller wrote: "Mailing list mode" was a specific thing in earlier versions of Discourse — it sent a notification for every message posted. This is kind of like going to Hyperkitty and saying "subscribe me to all 600 lists". I don't recommend that. Instead, choose spe

Re: How to check if a package is retired?

On 25/04/2023 08:55, Florian Weimer wrote: The xorg-x11-drv-fbturbo is supposed to have been retired (see ). How can I check if this is actually the case? A retired packaged should have a commit in srcgit that removes all the contents a

Re: It’s time to transform the Fedora devel list into something new

On 25/04/2023 09:40, Florian Weimer wrote: * Jarek Prokop: Personally, I have accounts on many, many Discourse instances, but I don't think there is a single one I read somewhat regularly. I find the mailing list mode and the notifications rather unpredictable. Maybe an alternative client cou

Re: Plans for dhclient / ISC dhcp?

On 30/05/2023 11:41, Peter Robinson wrote: On Tue, May 30, 2023 at 11:10 AM Richard W.M. Jones wrote: https://github.com/libguestfs/libguestfs/issues/121 We use dhclient to get a DHCP address inside a minimal appliance. To get this out of the way: NetworkManager or systemd are not options. I

Re: Plans for dhclient / ISC dhcp?

On 30/05/2023 11:57, Florian Weimer wrote: * Richard W. M. Jones: I wonder what our plans are for this package, such as whether we are recommending moving to dhcpcd: https://roy.marples.name/projects/dhcpcd systemd-networkd has an integrated DHCP client, hasn't it? It does yes, and it's wh

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

On 22/12/2022 19:18, Michael Catanzaro wrote: On Thu, Dec 22 2022 at 10:29:29 AM -0800, Adam Williamson wrote: Could we not go for 30 seconds? Personally I think 30 seconds is way too long for desktop users. But it's a lot better than 2 minutes, so if that's what we settle on, I won't compl

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

On 23/12/2022 11:45, Naheem Zaffar wrote: On Fri, 23 Dec 2022 at 08:26, Vitaly Zaitsev via devel mailto:devel@lists.fedoraproject.org>> wrote: On 23/12/2022 09:20, Mattia Verga via devel wrote: > I know this is way harder, but the right approach would be having a way > to

Re: valgrind on Fedora

On 16/01/2023 08:12, Florian Festi wrote: On 1/16/23 07:10, Gordon Messmer wrote: Does anyone have any hints for improving the information I get from valgrind? Have you installed the debuginfo packages for the packages involved? See man debuginfo-install Making sure debuginfod fetching works

Re: valgrind on Fedora

On 16/01/2023 08:52, Gordon Messmer wrote: On 2023-01-16 00:31, Tom Hughes via devel wrote: If that doesn't work then some examples would help, at least if you're getting a partial trace, so that we can get some idea of what component it is not able to unwind. ==29692== 30

Re: Fedora 38 mass rebuild is finished

On 24/01/2023 07:28, Jeff Law wrote: On 1/24/23 00:16, Jakub Jelinek wrote: On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote: I have some packages failed. One of them libtins. Problem is that: error: 'uint32_t' is not a member of 'std'; Is it normal? Is it GCC 13 change? See https:/

Re: Packages with breaking APIs

There is already precedent for doing it with catch and I've said that I plan to do it again so I don't know what more you want. Tom On 01/02/2023 10:13, Benson Muite wrote: Packages with breaking APIs between major version changes often keep maintaining the older version for some time after the

Re: Packages with breaking APIs

On 01/02/2023 11:51, Neal Gompa wrote: On Wed, Feb 1, 2023 at 12:46 PM Benson Muite wrote: For Catch, there was an upgrade from 1 to 2. Similarly for FFTW, the main package uses the name FFTW, but it was FFTW3 before hand. Maybe one could use Catch3 or Catch2v3? Then change names later once mo

Update of catch to Catch2 v3

As discussed a few weeks ago the Catch testing framework has a slightly weird naming scheme, namely: * Catch (v1.x, actually a branch in Catch2 repository) * Catch2 v2.x * Catch2 v3.x Since Catch2 was released we have had catch1 and catch packages to support both v1.x and v2.x users. I have now

Re: Update of catch to Catch2 v3

On 24/02/2023 07:48, Vitaly Zaitsev via devel wrote: On 22/02/2023 12:37, Tom Hughes via devel wrote: I have now added catch2 (for Catch2 v2.x) and upgraded the catch package to Catch2 v3.x in rawhide and f38. All my catch-dependent packages are now failing due to the missing catch.hpp

Re: Update of catch to Catch2 v3

On 28/02/2023 11:24, Vitaly Zaitsev via devel wrote: On 24/02/2023 09:42, Tom Hughes wrote: Did you miss the bit where I said you needed to change your BR to catch2-devel unless upstream has v3 support? What about Fedora ELN? catch2-devel is not available there. Nothing to do with me. I don'

Re: KB layout switching does not work in TB on Rawhide

On 02/03/2023 08:43, Olivier Fourdan wrote: TB still uses Xwayland? By default, yes. If you install thunderbird-wayland then you will get an alternative native Wayland version. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ devel maili

Re: unfixed CVE-2024-39929 in exim

On 15/07/2024 16:46, Marius Schwarz wrote: https://bugzilla.redhat.com/show_bug.cgi?id=2297728 Luckily is not a RCE, but we have an unpatched CVE in Exim .. can someone pls poke the right person for it? There was no reaction to the exim accouncement on OSS and to the bugreport. It was only

Re: `Unix-domain socket path "..." is too long (maximum 107 bytes)` can we change that?

On 07/08/2024 12:54, Richard W.M. Jones wrote: On Wed, Aug 07, 2024 at 01:09:01PM +0200, Vít Ondruch wrote: With new RPM, I hit the limit in two packages: https://koschei.fedoraproject.org/package/rubygem-abrt https://koschei.fedoraproject.org/package/rubygem-pg Is it RPM, or is it "rspec"?

Re: Build failure due to glib change

On 01/09/2024 23:26, Alexander Ploumistos wrote: I can sort of understand the rationale behind that, but I'd like someone who is more actively involved with C++ to give some advice if this is something I should be reporting to the glib folks, or if I should just change the writable string pointe

Re: Minified JS and CSS in Node packages

On 03/07/2023 16:41, Demi Marie Obenour wrote: Would it be possible to ensure that Node packages contain only actual source code, as in “the preferred form for making modifications” (quote from GNU GPL, I forget which version)? The simple answer is maybe in principle but in practice it's very

Re: Minified JS and CSS in Node packages

On 03/07/2023 17:09, Demi Marie Obenour wrote: On 7/3/23 11:59, Tom Hughes wrote: On 03/07/2023 16:41, Demi Marie Obenour wrote: Would it be possible to ensure that Node packages contain only actual source code, as in “the preferred form for making modifications” (quote from GNU GPL, I forget

Re: Restore access to torrent-file-editor package

On 24/07/2023 14:40, Leigh Scott wrote: You probably got removed for inactivity, see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UG3UOKBVJLUWZYEHWL52KPMITPEPEBNF/ Looks like it: https://pagure.io/find-inactive-packagers/issue/36 Tom -- Tom Hughes (t...

Re: old RPM code in my package - safe to remove this bit ?

On 30/11/2023 00:14, Michal Schorm wrote: I've stumbled upon this piece of code in my package: # Define license macro if not present %{!?_licensedir:%global license %doc} https://src.fedoraproject.org/rpms/mariadb/blob/rawhide/f/mariadb.spec#_322 Git blame points out 7 year old commit: h

Re: old RPM code in my package - safe to remove this bit ?

On 30/11/2023 00:28, Michal Schorm wrote: On Thu, Nov 30, 2023 at 1:19 AM Tom Hughes via devel wrote: It hasn't been needed for a long time. Good, thanks. Off it goes. :) It's just making %license an alias for %doc if your building for a release old enough that %license isn'

Re: Change of cronie and crontabs CIS compliance

On 06/12/2023 11:08, Ondrej Pohorelsky wrote: The only difference is that if you have populated the cron.deny list, after update it gets saved as .rpmsave and cron.allow is created. If the cron.deny is blank, it will get replaced. Also, if you had cron.allow populated before, it will stay this

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

On 21/12/2023 14:33, Steven A. Falco wrote: On 12/21/23 08:53 AM, Neal Gompa wrote: On Thu, Dec 21, 2023 at 8:52 AM Leigh Scott wrote: I'm -1 for this change, it shouldn't be enabled by default as it will cause issues for users using router mac filtering. What this seems to state is that t

License correction for rapidjson

The license for rapidjson has been corrected from: MIT to: MIT and BSD-3-Clause Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.f

Re: Schedule for Monday's FESCo Meeting (2024-01-15)

On 16/01/2024 10:43, Florian Weimer wrote: We still don't have approval for the toolchain updates that we need for the mass rebuild (notably Changes/GNUToolchainF40). As far as I can see there isn't even a Fesco ticket for it? The fields in https://discussion.fedoraproject.org/t/100414 for ti

Re: Build error with GCC 14, not even a warning in GCC 13

On 16/01/2024 23:49, Richard Shaw wrote: On Tue, Jan 16, 2024 at 5:36 PM Aleksei Bavshin mailto:aleba...@fedoraproject.org>> wrote: Ah, I misread the include path. It's our package that is too old :( https://src.fedoraproject.org/rpms/rapidjson/pull-request/4

Re: HEADSUP boost and tbb rebuilds starting in a side tag

On 20/01/2024 16:07, Jerry James wrote: Upstream has this in src/tbb/CMakeLists.txt: if (CMAKE_SIZEOF_VOID_P EQUAL 8) set(TBB_PC_NAME tbb) else() set(TBB_PC_NAME tbb32) endif() That makes the pkgconfig file install as tbb32.pc. I don't know why upstream is doing that. Maybe so 64-b

Re: Figure out what killed an app (rhbz#2253099)

On 31/01/2024 10:08, Milan Crha wrote: I tried to investigate a rawhide bug: https://bugzilla.redhat.com/show_bug.cgi?id=2253099 which is about Evolution being killed "by something". That's the thing, I do not know what killed it, thus even why it had been killed. It's even not killed after cert

Re: OpenSSL 3.2.1 available in rawhide

On 09/02/2024 13:34, Jarek Prokop wrote: Since the error from the scratch build says "invalid CA certificate" I thought to use some openssl "verification" command, this one seems like I'm on the right path. I have tried more permutations of the command with certificates available in the `spec

Re: Question about conditional BuildRequires lines

On 14/02/2024 14:54, Richard W.M. Jones wrote: https://src.fedoraproject.org/rpms/rapidjson/pull-request/7 I don't think what Tom is saying there is correct, or is it? The answer is that I'm wrong about it breaking things, because koji uses the unpacked spec file to install dependencies not t

Re: Question about conditional BuildRequires lines

On 14/02/2024 15:48, Richard W.M. Jones wrote: On Wed, Feb 14, 2024 at 03:21:38PM +, Tom Hughes wrote: On 14/02/2024 14:54, Richard W.M. Jones wrote: https://src.fedoraproject.org/rpms/rapidjson/pull-request/7 I don't think what Tom is saying there is correct, or is it? The answer is th

Re: dmesg restricted to root in Rawhide

On 28/02/2024 10:05, Marcin Juszkiewicz wrote: W dniu 27.02.2024 o 22:27, Justin Forbes pisze: In practice, this isn't that much of a lockdown for most fedora users. We give the default user on a system wheel access which means both 'sudo dmesg' and 'journalctl -k' work as is. You wish... $ id

Re: Confused about what to do about a ticket

On 26/08/2022 14:48, Ron Olson wrote: https://bugzilla.redhat.com/show_bug.cgi?id=2114563 was reported against Swift on Rawhide. I fixed the issue and responded on 8/4 that the Koji build was successful, but I got two additional, presumably automated, notes from Ben Cotton and Miro that sugge

Re: Explicit dependency on systemd-rpm-macros now required?

On 14/09/2022 12:11, Florian Weimer wrote: I see some new build failures in rawhide related to systemd RPM macros: Processing files: opencryptoki-3.18.0-4.fc38.s390x error: File must begin with "/": %{_tmpfilesdir}/opencryptoki.conf error: File must begin with "/": %{_unitdir}/pkcsslotd.service

Re: Failed RPM database migrations

I have one machine that has failed. It was an upgrade from 35 to 36 done using dnf distro-sync but I have plenty of others done the same way that worked. One difference is that it's a machine that wasn't upgraded until August while other ones were done back in May as a result of which the upgrad

Re: Failed RPM database migrations

The reason it hadn't completed is that rpmdb-migrate.service was enabled on that machine. Enabling (and starting) that service made it complete. Tom On 28/10/2022 12:24, Tom Hughes via devel wrote: I have one machine that has failed. It was an upgrade from 35 to 36 done using dnf distro

Re: Failed RPM database migrations

On 28/10/2022 13:31, Richard W.M. Jones wrote: On Fri, Oct 28, 2022 at 12:29:30PM +0100, Tom Hughes wrote: The reason it hadn't completed is that rpmdb-migrate.service was enabled on that machine. [was not, I guess?] Yes ;-) Enabling (and starting) that service made it complete. Interesti

Re: SPDX Change update

On 07/11/2022 17:46, Miroslav Suchý wrote: 8. After you migrate your SPEC file, please add the string “SPDX” to the entry of the packages’ %changelog. This is the easiest way to detect the migration has been done. The second best option is to add it to the dist-git commit messa

Re: convert everything to rpmautospec?

On 07/04/2024 16:15, Zbigniew Jędrzejewski-Szmek wrote: I think it's time to switch to rpmautospec completely. Thus, the proposal: - new packages MUST use rpmautospec - packagers SHOULD convert their packages - provenpackagers MAY convert existing packages (e.g. when they want to push some fi

Re: convert everything to rpmautospec?

On 08/04/2024 10:28, Zbigniew Jędrzejewski-Szmek wrote: On Mon, Apr 08, 2024 at 09:08:19AM +0200, Miroslav Lichvar wrote: On Sun, Apr 07, 2024 at 04:48:03PM +0100, Tom Hughes via devel wrote: -1 for existing packages certainly - none of my git commit logs are written with the expectation that

Re: convert everything to rpmautospec?

On 08/04/2024 14:47, Fabio Valentini wrote: It is already supposed to be default / preferred since this Fedora 38 Change: https://fedoraproject.org/wiki/Changes/Rpmautospec_by_Default I find that quite interesting because while I may have read it at the time I had certainly long since forgotte

Re: Fedora 40 apache now giving errors

On 24/04/2024 02:28, Xose Vazquez Perez wrote: # mkdir /etc/systemd/system/httpd.service.d/ # vi /etc/systemd/system/httpd.service.d/override.conf [Service] ProtectHome=false Better than just opening up whole trees again would be to use ReadWritePaths= to specify which paths should be allowed

Re: Testing package version is spec file

On 08/05/2024 18:38, Brad Smith wrote: I help maintain a package where upstream changed the process to generate installed documentation. In version 1.30 and newer, the spec file needs to use process A; in versions older than 1.30 (e.g. 1.29.x, etc) the spec file needs to use process B. I am stru

Re: Spec file using github repo - not tarball

On 08/05/2024 21:36, Kenneth Goldman wrote: Is it possible for a .spec file to clone a github.com repo rather than download a tarball? Can someone link to a working example? No, but github can give you a tar ball for any ref you want so why would you need/want to? Tom -- Tom Hughes (t...@co

Re: Firefox 126.0 with DBus service

On 15/05/2024 09:52, Ian McInerney via devel wrote: Also, don't new enabled-by-default services need approval from either FESCO or the Workstation WG according to the packaging docs (https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices/)? I know the page seems to focus on

Re: Firefox 126.0 with DBus service

On 15/05/2024 13:06, Michael J Gruber wrote: Is this used by Gnome search unconditionally? I might want to use Gnome but not a background indexer/tracker/search engine. Threw me off back then when KDE introcuced something like that. Go to "Search" in the Gnome settings and you can control whic

Re: Spec file using github repo - not tarball

On 21/05/2024 16:37, Dominik Wombacher wrote: I have a case were upstream excludes the test suite from the export [1]. But I want the tests to be part of the package build to validate that everything is fine. So this requires a bit of local git clone and create an own archive file. I can't just

Re: Guidance on individual packages requiring x86_64-v2 baseline ?

On 20/06/2024 15:03, Stephen Gallagher wrote: Honestly, I'd like to pitch that we retarget Fedora at x86_64-v3 (yes, three) and recommend creation of a Fedora "Hardware Life Extension" Remix that can provide rebuilds of (a subset of) Fedora that they want to run on ancient hardware. It could be

Re: Guidance on individual packages requiring x86_64-v2 baseline ?

On 20/06/2024 16:34, Simon Farnsworth wrote: For Pentium and Celeron branded processors, v2 also loses Skylake, Icelake, Haswell, Cometlake, Broadwell and others, even when their matching Core branded processors support x86-64v2 or x86-64v3. That means that you lose all Pentium Silver processo

Re: 2FA policy for provenpackagers is now active

On 24/06/2024 18:26, Stephen Gallagher wrote: Not really an issue if you have GSSAPI set up on your system. Such as by installing fedora-chromium-config-gssapi (for Chrome/Chromium users) or by using Firefox which is set up for GSSAPI out-of-the-box. I've never seen Firefox use my kerberos tic

Re: Fedora & AI Survey Now Live Until July 16th

Survey: Please select at most 5 answers User: Selects 2 answers Survey: Please rank all items User: Remembers why they hate surveys and gives up To be clear as there are only two items where I think there is any chance of AI being useful I am unable to rank the others. Tom On 01/07/2024 18:33,

Re: Fedora & AI Survey Now Live Until July 16th

On 01/07/2024 20:07, Aoife Moloney wrote: I would also like to add that we deliberately took a positive tone for this survey as it is far too easy to find (many) negatives for AI (and for good reason!), and we wanted to try to look at the benefits we could get from AI instead if applied proper

mapnik soname bump in rawhide

I've updated mapnik in rawhide to 4.0.0 which includes an soname bump. I've rebuilt python-mapnik and opened a PR for viking to fix it to build against mapnik 4 which I believe covers all the downstream users. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ -- ___

Re: F37 proposal: Deprecate openssl1.1 package (System-Wide Change)

On 27/06/2022 08:53, Richard W.M. Jones wrote: On Fri, Jun 24, 2022 at 01:20:27PM +0200, Dmitry Belyavskiy wrote: Dear Richard, If the only problem is legacy (and unsafe) ciphersuites, loading the legacy provider will solve this problem. Any clues on how to do that? https://wiki.openssl.org

Re: F37 proposal: Deprecate openssl1.1 package (System-Wide Change)

On 27/06/2022 10:02, Richard W.M. Jones wrote: On Mon, Jun 27, 2022 at 09:11:29AM +0100, Tom Hughes wrote: On 27/06/2022 08:53, Richard W.M. Jones wrote: On Fri, Jun 24, 2022 at 01:20:27PM +0200, Dmitry Belyavskiy wrote: Dear Richard, If the only problem is legacy (and unsafe) ciphersuites, l

Re: F37 Change Proposal: MAC Address Policy none (System-Wide Change)

As I said before I don't care that much what the policy is but I do care very much that Fedora keeps changing it. Twice now I have had to go and reconfigure my networks after a Fedora upgrade has changed the MAC assignment policy. My vote is therefore to leave it as it is so that I don't have to

Re: F37 Change Proposal: MAC Address Policy none (System-Wide Change)

On 27/06/2022 17:05, Thomas Haller wrote: On Mon, 2022-06-27 at 13:09 +0100, Tom Hughes via devel wrote: Twice now I have had to go and reconfigure my networks after a Fedora upgrade has changed the MAC assignment policy. Interesting. Are you sure it was twice? I thought it changed "

Re: F37 Change Proposal: MAC Address Policy none (System-Wide Change)

On 27/06/2022 17:09, Tom Hughes via devel wrote: On 27/06/2022 17:05, Thomas Haller wrote: On Mon, 2022-06-27 at 13:09 +0100, Tom Hughes via devel wrote: Twice now I have had to go and reconfigure my networks after a Fedora upgrade has changed the MAC assignment policy. Interesting. Are

Re: Bugzilla: You can't ask Lennart Poettering because that account is disabled.

On 02/07/2022 11:35, Marius Schwarz wrote: Am 02.07.22 um 10:37 schrieb Adam Williamson: Probably not, no. Lennart hasn't maintained PA upstream or downstream for a long time. The current downstream maintainer is Wim Taymans (I think). Can we change the defaults for PA inside bugzilla to Wim

Re: Fedora 34 Change proposal: Remove make from BuildRoot (System-Wide Change)

On 04/11/2020 18:12, Ben Cotton wrote: = Phase 1: Analysis = For this change, we will start by creating a list of all packages that have a build-time dependency on make. This will be done by analyzing spec files and also by rebuilding all packages in Fedora with make removed from the bu

Re: Fedora 34 Change proposal: Remove make from BuildRoot (System-Wide Change)

On 04/11/2020 19:06, Tom Hughes via devel wrote: On 04/11/2020 18:12, Ben Cotton wrote: = Phase 1: Analysis = For this change, we will start by creating a list of all packages that have a build-time dependency on make.  This will be done by analyzing spec files and also by rebuilding

Re: Fedora 34 Change proposal: Remove make from BuildRoot (System-Wide Change)

On 04/11/2020 19:14, Neal Gompa wrote: When did this happen? CMake should not be requiring Make at runtime, especially now that the CMake macros let you trivially use either Make or Ninja. No idea, but "rpm -q --requires cmake" says it does. And I only sue %cmake macros which is turn invoke c

Re: Fedora 34 Change proposal: Remove make from BuildRoot (System-Wide Change)

On 04/11/2020 19:46, Tom Stellard wrote: On 11/4/20 2:10 PM, Tom Hughes via devel wrote: Also I'm suspicious about the quality of that list because it includes packages of mine that only use make via cmake and which do BR cmake which in turn requires make. For the purposes of this pro

Re: Fedora 34 Change proposal: Remove make from BuildRoot (System-Wide Change)

On 04/11/2020 20:31, Tom Stellard wrote: On 11/4/20 3:22 PM, Tom Hughes wrote: On 04/11/2020 19:46, Tom Stellard wrote: On 11/4/20 2:10 PM, Tom Hughes via devel wrote: Also I'm suspicious about the quality of that list because it includes packages of mine that only use make via cmak

Re: Heads up: proj 7.2.0 + gdal 3.2.0

On 05/11/2020 11:24, Sandro Mani wrote: I'll be building proj-7.2.0 together with gdal-3.2.0 in rawhide shortly. I'll do a round of test builds in this copr [1], and then build everything (and rebuild dependent packages) in a rawhide side-tag and then merge it. That's definitely going to cau

Re: Fedora 34 Change proposal: Remove make from BuildRoot (System-Wide Change)

On 05/11/2020 11:56, Kevin Kofler via devel wrote: CMake actually just generates the makefiles, you still run make directly (as with autotools). The makefiles then do several complex things, possibly including running make with different arguments (and also calling back into CMake by running cm

Re: patch applied without package maintainers' approve

On 09/11/2020 14:50, Honggang LI wrote: On Mon, Nov 09, 2020 at 02:39:22PM +0100, Dominik 'Rathann' Mierzejewski wrote: On Monday, 09 November 2020 at 14:23, Honggang LI wrote: On Mon, Nov 09, 2020 at 08:03:59AM -0500, Neal Gompa wrote: On Mon, Nov 9, 2020 at 8:03 AM Honggang LI wrote: hi

Re: The default fs.inotify.max_user_watches limit is too low.

On 18/11/2020 09:58, Miro Hrončok wrote: On 11/18/20 10:13 AM, Gargoyle wrote: If not, then perhaps the default should be significantly increased with the aim of removing the problem for new users with modern desktop/laptop machines which probably have 4GB+ RAM. I've not rebooted my machine

Re: video meeting to discuss Matrix/Element and IRC

On 19/11/2020 19:25, Adam Williamson wrote: I mean, I'm an old fogey too, but at *some* point we do have to accept that new things can be actively better. True. I honestly can see exactly zero downsides to using a Matrix setup as compared to using IRC, and a giant pile of upsides, starting w

Re: video meeting to discuss Matrix/Element and IRC

On 19/11/2020 19:49, Neal Gompa wrote: The GNOME-based one is Fractal, which is not available in Fedora as of right now. That said, the Qt based ones are in way better shape than the GNOME one. And QGnomePlatform should make them work reasonably well... My problem, at least on this hidpi lapto

Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)

On 25/11/2020 10:47, Wim Taymans wrote: but I don't want to test all this This is ok, I can understand that you don't want to deal with possible audio problems. You will have to install pulseaudio again and opt out. You will have to hope that other people do sufficient testing. It is a bit s

  1   2   >