Re: Review request: jedit
I will take it. чт, 3 авг. 2023 г., 19:24 Zdeněk Žamberský : > Hello, > > review request (jedit): > https://bugzilla.redhat.com/show_bug.cgi?id=2228918 > > reviewers welcome :) > thanks > > -- > Zdeněk Žamberský > OpenJDK QE > Red Hat > ___ > 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 > ___ 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: octave 8.1 update coming to rawhide
Is there a chance to have Octave 8.1 at F38? вс, 9 апр. 2023 г. в 18:49, Orion Poplawski : > > On 4/8/23 17:27, Orion Poplawski wrote: > > On 4/5/23 20:22, Orion Poplawski wrote: > >> I will be updating octave to 8.1 this weekend. This involves a soname > >> bump and I will be rebuilding all deps. > > Builds are complete and update submitted: > > https://bodhi.fedoraproject.org/updates/FEDORA-2023-56669c4da2 > > -- > Orion Poplawski > he/him/his - surely the least important thing about me > IT Systems Manager 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 https://www.nwra.com/ > > ___ > 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 ___ 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: New default behaviour at %prep section spec-file
Thanks.
About %autosetup - my mistake too.
Thread closed.
ср, 1 мар. 2023 г. в 13:48, Sérgio Basto :
>
> On Wed, 2023-03-01 at 12:22 +0300, Vascom wrote:
> > Hi all.
> >
> > As I noticed Fedora change default behaviour at %prep section of
> > spec-file.
> >
> > Now by default executed %{set_build_flags} and added "-p1" parameter
> > to %autosetup for applying patches.
> >
> > Is it really?
> > Are there other changes?
> > When will these changes be included in the Packaging Guidelines?
>
> I think is this that you are looking for
> https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck
>
> > ___
> > 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
>
> --
> Sérgio M. B.
> ___
> 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
___
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
New default behaviour at %prep section spec-file
Hi all.
As I noticed Fedora change default behaviour at %prep section of spec-file.
Now by default executed %{set_build_flags} and added "-p1" parameter
to %autosetup for applying patches.
Is it really?
Are there other changes?
When will these changes be included in the Packaging Guidelines?
___
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: Orphaning pulseeffects
I'm afraid to make a mistake in the procedure. пн, 20 февр. 2023 г. в 13:34, Sandro : > > On 20-02-2023 10:09, Vascom wrote: > > This package can be retired. There is no need for anyone to take it. > > Why not retire it directly, if adoption makes no sense? > > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/ > > -- Sandro > ___ > 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 ___ 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
Orphaning pulseeffects
I have orphaned pulseeffects package because it replaced by easyeffects at upstream and at Fedora. This package can be retired. There is no need for anyone to take it. ___ 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: Retiring Bottles in favor of Flatpak provided by upstream
Seems as bad practice to drop packages by upstream request. ср, 25 янв. 2023 г. в 14:38, Pete Walter : > > I am not happy about dropping Fedora packages in favor of upstream Flatpaks > either. > > Can you assign the package to me instead of retiring it? I can get it updated > so we can keep it in Fedora. > > Pete > > 25.01.2023, 10:56, "Vít Ondruch" : > > I am not user of Bottles so I won't complain about this particular case, > but the push towards (upstream) Flatpaks is unfortunate :/ > > > Vít > > > Dne 24. 01. 23 v 22:44 Sandro napsal(a): > > Hi, > > Development of Bottles is moving fast and we have been struggling to > keep up with upstream releases, especially since the introduction of > Rust components. > > Upstream has approached the maintainers [1,2] and asked us to retire > the package in favor of the Flatpak packages provided by upstream. > > I'm planning to move forward with retiring Bottles in the coming days. > I will add a comment in all open bug reports, letting users know they > should switch to the Flatpak release. > > Bottles in F36 and F37 will not receive any further updates unless > there are security related issues surfacing. > > [1] https://github.com/bottlesdevs/Bottles/issues/2345 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=2160007 > > Cheers, > > Sandro > > , > > ___ > 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 > > ___ > 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 ___ 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: Fedora 38 mass rebuild is finished
Need help with rebuilding doublecmd. вт, 24 янв. 2023 г. в 16:21, Richard Shaw : > > hobbes1069 (9): > cqrlog - Fails for some weird lazbuild issue I don't understand > flnet - Spec conditional oops. Fixed. > flrig - Needed cstdint. Fixed > freecad - Needs cstdint. Working on it. > gmsh - Needed cstdint. Fixed. > openCOLLADA - error: possibly dangling reference to a temporary. Don't know > how to fix this one. > opencascade - error: declaration of 'tbb::task& > tbb::internal::task_prefix::task()' changes meaning of 'task' > openexr - Needed cstdint. Fixed. > spnavcfg - https://github.com/FreeSpacenav/spnavcfg/issues/30 > > Thanks, > Richard > ___ > 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 ___ 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: Fedora 38 mass rebuild is finished
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? I must patch sources now? sed -i 's|stdint.h|cstdint|' include/tins/ip_address.h вт, 24 янв. 2023 г. в 05:52, Kevin Fenzi : > > On Mon, Jan 23, 2023 at 10:26:18PM +, Sérgio Basto wrote: > > > > I found more 5 with > > https://koji.fedoraproject.org/koji/tasks?owner=releng=active=tree=all=-id > > > > 96481236 build (f38-rebuild, > > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa) > > > > 96474133 build (f38-rebuild, /rpms/trace- > > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080) > > > > 96404064 build (f38-rebuild, /rpms/perl- > > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967) > > > > 96383273 build (f38-rebuild, > > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d > > > > 96368979 build (f38-rebuild, > > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1ff) > > Yes, I have canceled all those now. > > kevin > ___ > 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 ___ 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: Qt6 qwtplot3d review
I will take it. чт, 29 дек. 2022 г. в 16:08, Antonio T. sagitter : > > Hi all. > > qwtplot3d-qt6 is a new package and needs a review: > > https://bugzilla.redhat.com/show_bug.cgi?id=2156091 > > I will glad to review another package in return of your courteousness. > > > Best regards > > -- > --- > Antonio Trande > Fedora Project > mailto: sagit...@fedoraproject.org > GPG key: 0x40FDA7B70789A9CD > GPG keys server: https://keyserver.dcc.sib.swiss/ > > ___ > 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 ___ 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: Support for Realtek RTL8811CU (WiFi)
You can became maintainer and add this to rpmfusion. пт, 1 июл. 2022 г., 10:50 Christopher Klooz : > Sorry, I didn't mean to implement this specific solution. That was only > meant as example that the issue is known. I meant it more generic, any > solution for the user that can be included in the repos or rpmfusion, so > that it remains managed by dnf to ensure testing and updating. Such as we > have it with nvidia. I was wondering as the 8811CU seems widespread. > On 01/07/2022 01:39, Naheem Zaffar wrote: > > > > On Thu, 30 Jun 2022, 23:50 Christopher Klooz, wrote: > >> It seems that Fedora does not support the Realtek RTL8811CU for WiFi. A >> user at ask.Fedora just had the issue. `lsusb` classifies it just as >> "Bus 001 Device 010: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac >> NIC"; correspondingly, `nmcli` does not recognize it at all. >> >> A bug report with some improvised interim-solutions seems to already >> exist https://bugzilla.redhat.com/show_bug.cgi?id=1957828 , the most >> widespread solution seems to be https://github.com/brektrou/rtl8821CU >> (but unknown maintenance). >> >> Is it known why the 8811CU remains unsupported? Or have I missed >> something? >> >> Regards, >> Chris >> > > Fedora does not include out of tree kernel modules. To get it into fedora, > the module will need to be included in the upstream kernel. > > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Inportant binutils update stuck at bodhi
May be. But anyone know about this problem? сб, 2 апр. 2022 г. в 15:44, Mattia Verga via devel : > > Il 02/04/22 14:24, Vascom ha scritto: > > Hi. > > > > How to push this stucked binutils update to rawhide? > > https://bodhi.fedoraproject.org/updates/FEDORA-2022-0d344a9601 > > Binutils has been failing its own testuite for months, since when F36 > was Rawhide... maybe it should be fixed instead of blindly waive the tests? > > Mattia > > > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Inportant binutils update stuck at bodhi
Hi. How to push this stucked binutils update to rawhide? https://bodhi.fedoraproject.org/updates/FEDORA-2022-0d344a9601 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
What about KDE spin crashes because of non stable sddm? https://bugzilla.redhat.com/show_bug.cgi?id=2066304 This made F36 KDE fully unfunctional. пт, 1 апр. 2022 г., 19:40 Ben Cotton : > F36 Final freeze begins Tuesday 5 April. We are currently targeting > the early target date (2022-04-19), which means we'd want to have > blockers fixed by 11 April in order to provide time for validation > testing prior to the Go/No-go meeting on 14 April. > > Action summary > > > Accepted blockers > - > > 1. anaconda — anaconda enablement of fingerprint auth overrides > existing authselect configuration — MODIFIED > ACTION: QA to verify FEDORA-2022-8538fa94da > > 2. gnome-connections — gnome-connections: _mid_memalign(): > gnome-connections killed by SIGSEGV — NEW > ACTION: Maintainers to diagnose and fix issue > > 3. mutter — The input string via Input Method isn't renderred properly > at the search box on Activities — MODIFIED > ACTION: QA to verify FEDORA-2022-566779da43 > > 4.mutter — Workstation Live is frozen in a VM with QXL video driver > (Virtio works OK) — NEW > ACTION: Maintainers to diagnose and fix issue > > 5. plasma-discover — The About button sends Discover into loop and the > application stops responding. — NEW > ACTION: Upstream to diagnose and fix issue > > 6. xorg-x11-server — Basic graphics mode broken for X11 > (GNOME/KDE/netinst) on UEFI) — NEW > ACTION: Maintainers to diagnose and fix issue > > 7. xorg-x11-server — Basic graphics mode broken for KDE BIOS mode, > screen goes black in minutes — NEW > ACTION: Maintainers to diagnose and fix issue > > > Proposed blockers > - > > 1. gnome-control-center — Printer setting: can't scroll media size list — > NEW > ACTION: Maintainers to package upstream MR 1268 > > 2. gnome-control-center — X11: Failed to create foreign window for XID > 0: clicking on already set up account in settings > online accounts > does not open a new pop up window to show account sync settings — > ON_QA > ACTION: QA to verify FEDORA-2022-67fa3533bf > > 3. hplip — Cannot print except when rebooting computer after upgrade > from F35 -> after recommended manual intervention, now cannot print > except after turning off printer and then printing a blank page in > LibreOffice — NEW > ACTION: Maintainers to diagnose and fix issue > NEEDINFO: catanzaro > > 4. libdnf — systemd-oomd kills rpm-ostree when installing a package on > Fedora IoT 36 on the Raspberry Pi Zero 2 W — NEW > ACTION: Maintainers to diagnose and fix issue > > 5. qemu — VMs hang when trying to access virtiofs mounts in the guest VM — > POST > ACTION: Maintainers to merge and build PR 22 > > 6. selinux-policy — selinux-policy is preventing flatpak from updating > / installing / removing flatpaks — NEW > ACTION: Maintainers to update policy to permit necessary flatpak actions > > 7. xdg-desktop-portal-gnome — xdg-desktop-portal-gnome: > wl_proxy_get_version(): xdg-desktop-portal-gnome killed by SIGSEGV — > MODIFIED > ACTION: QA to verify FEDORA-2022-f8681a48e6 > > Bug-by-bug detail > = > > Accepted blockers > - > > 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2069899 — > MODIFIED > anaconda enablement of fingerprint auth overrides existing authselect > configuration > > anaconda overwrites the authselect config when enabling fingerprint > authentication. This disables nss-mdns (when configured), breaking > things like printer discovery. FEDORA-2022-8538fa94da contains a > candidate fix. > > 2. gnome-connections — https://bugzilla.redhat.com/show_bug.cgi?id=2068015 > — NEW > gnome-connections: _mid_memalign(): gnome-connections killed by SIGSEGV > > Connecting to an RDP server (including localhost) causes Connections > to crash immediately. Filed upstream as > https://gitlab.gnome.org/GNOME/connections/-/issues/95 > > 3. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2062660 — MODIFIED > The input string via Input Method isn't renderred properly at the > search box on Activities > > Pre-edit strings are not rendered in some cases, only showing the > first keypress. Update FEDORA-2022-566779da43 contains a candidate > fix. > > 4. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2063156 — NEW > Workstation Live is frozen in a VM with QXL video driver (Virtio works OK) > > VMs that initially use the QXL driver appears frozen. Using virtio > (including to switching to QXL after?) avoids this. KDE Lives do not > display (heh) this behavior, not does using `nomodeset`. Filed > upstream as https://gitlab.gnome.org/GNOME/mutter/-/issues/2201 > > 5. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2057563 > — NEW > The About button sends Discover into loop and the application stops > responding. > > Clicking the About button causes a loop which renders Discover > unresponsive (except when the window is maximized). Confirmed upstream > as https://bugs.kde.org/show_bug.cgi?id=448784 > > 6. xorg-x11-server —
bibutils soname update to 7
bibutils now released a 7.1 version with soname updated from 6 to 7. I will rebuild it for rawhide in a week. Because no one package not depend on libbibutils I will update it for F35 too. No one other package no need to rebuild. -- best regards, Vasiliy Glazov ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Joint to packager group
This instruction for join package collection maintainers group. What do you mean "like member"? 1. If you are not in the maintainers group you can just send Pull-Request. 2. If you are in the maintainers group you can join to package maintainers (if the admin of the package welcomes you) and have commit access. пн, 9 авг. 2021 г. в 11:30, Anatoly Vildemanov via devel : > > Is this instruction for stay sponsor? > I want to join to packager like member , is it possible? > > Thanks > > -Original Message- > From: Vascom > Sent: Monday, August 9, 2021 10:42 AM > To: Development discussions related to Fedora > Subject: Re: Joint to packager group > > External email: Use caution opening links or attachments > > > Hi. > > If you want be co-maintainer you should follow this instruction > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FHow_to_get_sponsored_into_the_packager_group%23Become_a_co-maintainerdata=04%7C01%7Canatolyv%40nvidia.com%7C91d6f5170f724c4163ab08d95b093b28%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637640917479001467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=E0jDWEbvqi9ZvdrKbx2XCnlXnLLwwaGLPq7d%2BwuLvUY%3Dreserved=0 > > пн, 9 авг. 2021 г. в 10:33, Anatoly Vildemanov via devel > : > > > > Hi, > > > > > > > > My name is Anatoly (anatolyv) . I work in UCX project , contribute to Tests > > and CI > > > > I need to join to packager group for push ucx package > > > > > > > > I completed all the points from "Join the package collection maintainers" > > manual > > > > > > > > Anatoly Vildemanov > > Sr. Software Engineer, DevOps | Networking SW Mellanox > > > > Mob: +79082335079 > > NVIDIA > > > > > > > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fproject%2Fcode-of-conduct%2Fdata=04%7C01%7Canatolyv%40nvidia.com%7C91d6f5170f724c4163ab08d95b093b28%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637640917479001467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=5vME8OWbem3itBD8W2b1x%2F6cI8I%2BsRPvZrHQl6hWpvc%3Dreserved=0 > > List Guidelines: > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FMailing_list_guidelinesdata=04%7C01%7Canatolyv%40nvidia.com%7C91d6f5170f724c4163ab08d95b093b28%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637640917479001467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=tcc5cs%2BLI%2B8nyGSYZljvjtGN28quP2j8IMZxEAhN284%3Dreserved=0 > > List Archives: > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.fedoraproject.org%2Farchives%2Flist%2Fdevel%40lists.fedoraproject.orgdata=04%7C01%7Canatolyv%40nvidia.com%7C91d6f5170f724c4163ab08d95b093b28%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637640917479001467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Wn12pSPTBEvNdLSh7fRm48M7TxLaJR5cBJ8TSZlcMrs%3Dreserved=0 > > Do not reply to spam on the list, report it: > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpagure.io%2Ffedora-infrastructuredata=04%7C01%7Canatolyv%40nvidia.com%7C91d6f5170f724c4163ab08d95b093b28%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637640917479001467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=YHXbq0rZUxNONvvsOQubvPT9zmtpzbH8ugH5Q3dxsMs%3Dreserved=0 > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fproject%2Fcode-of-conduct%2Fdata=04%7C01%7Canatolyv%40nvidia.com%7C91d6f5170f724c4163ab08d95b093b28%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637640917479001467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=5vME8OWbem3itBD8W2b1x%2F6cI8I%2BsRPvZrHQl6hWpvc%3Dreserved=0 > List Guidelines: > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FMailing_list_guidelinesdata=04%7C01%7Canatolyv%40nvidia.com%7C91d6f5170f724c4163ab08d95b093b28%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637640917479001467%7CUnknown%7CTWFpbGZsb3d8e
Re: Joint to packager group
Hi. If you want be co-maintainer you should follow this instruction https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer пн, 9 авг. 2021 г. в 10:33, Anatoly Vildemanov via devel : > > Hi, > > > > My name is Anatoly (anatolyv) . I work in UCX project , contribute to Tests > and CI > > I need to join to packager group for push ucx package > > > > I completed all the points from “Join the package collection maintainers” > manual > > > > Anatoly Vildemanov > Sr. Software Engineer, DevOps | Networking SW Mellanox > > Mob: +79082335079 > NVIDIA > > > > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: How to solve rpmlint E: script-without-shebang message
Also you should inform upstream to remove exec flag from this files in their repo/sources. вс, 8 авг. 2021 г., 15:06 : > I will remove the executable flag with: > chmod 0644 *.pm > > Thanks a lot > Martin > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: How to solve rpmlint E: script-without-shebang message
But in /usr/share should not be executables, as I know. вс, 8 авг. 2021 г., 14:43 Vitaly Zaitsev via devel < devel@lists.fedoraproject.org>: > On 08/08/2021 13:01, linux4mar...@gmx.de wrote: > > How can i solve this ? > > Set chmod 0644 or add a shebang by patching them. > > -- > Sincerely, >Vitaly Zaitsev (vit...@easycoding.org) > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Systemd unit files installed into unowned directories
Your package require systemd? Systemd own this directory? If yes it is OK https://docs.fedoraproject.org/en-US/packaging-guidelines/#_the_directory_is_also_owned_by_a_package_implementing_required_functionality_of_your_package If you mean warning from fedora-review then it tool may be old. But reviewer must manually check all points and not use only automatic reviewing tools. вт, 3 авг. 2021 г., 13:05 Petr Menšík : > Hello, > > I just did package review and noticed systemd service files are > installed into %_unitdir without proper. I failed to notice all my > packages install into the same directory without depending on that > directory. > > I did not find explicit note about the issue anywhere in Packaging > Guidelines. Unowned directories [1] note only 'core packages' without > precise specification, how can one identify core package. While I agree > systemd IS core package for sure, is there reason why systemd-filesystem > noarch subpackage does not own %_unitdir, %_userunitdir and %_tmpfilesdir? > > I admit systemd might be missing only in few containers without init > system. Does systemd have special expection? Can be guidelines updated > to mention this is okay? In that case fedora-review should be adjusted > to not warn about those directories. > > I would propose creation of systemd-filesystem package required by > systemd, which would pass general rule about *-filesystem package not > required. > > Any opinions? > > Regards, > > Petr > > 1. > > https://docs.fedoraproject.org/en-US/packaging-guidelines/UnownedDirectories/ > > -- > Petr Menšík > Software Engineer > Red Hat, http://www.redhat.com/ > email: pemen...@redhat.com > PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB > > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there a command to expand Source0 from spec file to the final URL?
You can use command
spectool -g name.spec
to download sources.
вт, 6 июл. 2021 г., 19:15 Richard W.M. Jones :
>
> Is this possible? I've got one with lots of %{macros} in it.
>
> It seems like this should be possible using rpmspec, but I can't work
> out how.
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-p2v converts physical machines to virtual machines. Boot with a
> live CD or over the network (PXE) and turn machines into KVM guests.
> http://libguestfs.org/virt-v2v
> ___
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: gbc3: error: Component not found: &1 gb.desktop.x11
Seems that you need add BR: gambas3-gb-desktop-x11 пт, 21 мая 2021 г., 09:20 Martin Gansser : > Hi, > > when compiling xt7-player-mpv-0.33.3152 [1] on fedora fc34 & rawhide, i > get this error message: > > + cd /home/martin/rpmbuild/BUILD > + cd xt7-player-mpv-0.33.3152 > + /usr/bin/gbc3 -e -a -g -t -p -m > gbc3: error: Component not found: &1gb.desktop.x11 > > [1] > https://martinkg.fedorapeople.org/ErrorReports/xt7-player-mpv/xt7-player-mpv.spec > > Any idea ? > > Regards > Martin > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: New RPM submission
Also look at https://fedoraproject.org/wiki/Join_the_package_collection_maintainers сб, 10 апр. 2021 г., 14:22 Peter Oliver : > Welcome! Start at https://fedoraproject.org/wiki/Package_Review_Process > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: review request
Done. вт, 23 мар. 2021 г. в 17:32, chedi toueiti : > > Hi, > > I have a trivial python package (re-assert) to review: > > https://bugzilla.redhat.com/show_bug.cgi?id=1941362 > > needed for pre-commit tests. > > Happy to review in exchange. > > Regards, > > -- > Chedi Toueiti > > * Due to the constant fluctuation in customer personalities, we cannot be > responsible for the mental stability of any one member of our staff. > > ** My opinions may have changed, but not the fact that I am right. > > *** I always try to go the extra mile at work, but my boss always finds me > and brings me back. > > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: systemd-oomd kills wrong application (F34, KDE)
Yes, it is my bugreport. Sorry for my english. Next is the google translate: It is easy to imagine the situation (as it was with me in general): a person works, launches something that eats up memory, it falls, the person starts it again in bewilderment, and then his other working application is killed. And the logs are empty. вс, 21 мар. 2021 г. в 21:21, Alexey A. : > > The bug https://bugzilla.redhat.com/show_bug.cgi?id=1941340 > > пн, 22 мар. 2021 г. в 03:12, Vascom : > > > > Hi all. > > > > I want to draw your attention to the bug in systemd-oomd in F34. > > This oomd kills my work application during the second run of the stress > > test. > > And I create this ticket: > > https://bugzilla.redhat.com/show_bug.cgi?id=1941340 > > > > Can anybody confirm that behaviour? > > > > Also I don't see any logs about this incident, nor what application > > was killed, nor why, nor when. > > > > May be we need some more discussion about enabling systemd-oomd by > > default for F34? > > > > -- > > Best regards, > > Vasiliy Glazov > > ___ > > 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 on the list, report it: > > https://pagure.io/fedora-infrastructure > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: systemd-oomd kills wrong application (F34, KDE)
Only this мар 21 15:19:14 milkyway.localdomain systemd-oomd[1538]: Swap used (7957565440) / total (8489267200) is more than 90.00% мар 21 15:19:51 milkyway.localdomain systemd-oomd[1538]: Swap used (8081399808) / total (8489267200) is more than 90.00% вс, 21 мар. 2021 г. в 21:18, Alexey A. : > > What is in the journal? > > пн, 22 мар. 2021 г. в 03:12, Vascom : > > > > Hi all. > > > > I want to draw your attention to the bug in systemd-oomd in F34. > > This oomd kills my work application during the second run of the stress > > test. > > And I create this ticket: > > https://bugzilla.redhat.com/show_bug.cgi?id=1941340 > > > > Can anybody confirm that behaviour? > > > > Also I don't see any logs about this incident, nor what application > > was killed, nor why, nor when. > > > > May be we need some more discussion about enabling systemd-oomd by > > default for F34? > > > > -- > > Best regards, > > Vasiliy Glazov > > ___ > > 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 on the list, report it: > > https://pagure.io/fedora-infrastructure > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
systemd-oomd kills wrong application (F34, KDE)
Hi all. I want to draw your attention to the bug in systemd-oomd in F34. This oomd kills my work application during the second run of the stress test. And I create this ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1941340 Can anybody confirm that behaviour? Also I don't see any logs about this incident, nor what application was killed, nor why, nor when. May be we need some more discussion about enabling systemd-oomd by default for F34? -- Best regards, Vasiliy Glazov ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: "Fedora Linux" in /etc/os-release
Please, keep simple "Fedora". Don't make us ridiculous. I vote -1. ср, 10 мар. 2021 г., 22:22 Reon Beon via devel < devel@lists.fedoraproject.org>: > uname -a > > Linux fedora 5.12.0-0.rc2.165.fc35.x86_64 #1 SMP Sat Mar 6 16:32:15 UTC > 2021 x86_64 x86_64 x86_64 GNU/Linux > > Shouldn't fedora be capitalized? > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Problem with s390x koji builder
What's wrong with s390x koji builder?
I always see this error:
Child return code was: -11
EXCEPTION: [Error()]
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/mockbuild/trace_decorator.py",
line 93, in trace
result = func(*args, **kw)
File "/usr/lib/python3.9/site-packages/mockbuild/util.py", line 600,
in do_with_status
raise exception.Error("Command failed: \n # %s\n%s" % (command,
output), child.returncode)
mockbuild.exception.Error: Command failed:
Other arches are OK.
https://koji.fedoraproject.org/koji/taskinfo?taskID=60085705
Need to fix it.
--
Best regards,
Vasiliy Glazov
___
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
Updating cryptopp to 8.3.0
Hi all. I want to update cryptopp package to 8.3.0. It has the same soname version but changes in ABI. I found only two dependent packages: clementine tegrarcm So I will rebuild them too. If you have any suggestions or I missed some dependent packages please tell me. I am plan to make builds at 28.12.2020 in rawhide. -- Best gerards, Vasiliy Glazov ___ 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
Re: Fedora 33 Mass Rebuild
Many of this are cmake change breakage. пн, 3 авг. 2020 г., 18:15 Richard Hughes : > On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote: > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Most of those are the libcroco->gettext breakage, no? We're not going > to be rebuilding all affected packages manually are we?! > > Richard./ > ___ > 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 > ___ 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
Re: Disable LTO for now ?
Disable LTO
https://src.fedoraproject.org/rpms/redhat-rpm-config/c/5baaf4a99cc77572d3496a7000674098bef7ed68?branch=master
ср, 29 июл. 2020 г., 17:08 :
> Hello opencv [1] build also failed around LTO
> What is your advise ? What is your advice?
>
> Thanks,
>
> [1]
> https://koji.fedoraproject.org/koji/taskinfo?taskID=48054416
>
>
> On 2020-07-27 23:46, notificati...@fedoraproject.org wrote:
> > Notification time stamped 2020-07-27 22:46:34 UTC
> >
> > From f4bac7efd3c251ffb64107bc2f522c1d3c829b5c Mon Sep 17 00:00:00 2001
> > From: Jeff Law
> > Date: Jul 27 2020 22:46:22 +
> > Subject: Disable LTO for now
> >
> >
> > ---
> >
> > diff --git a/apt.spec b/apt.spec
> > index a555b62..282ddc8 100644
> > --- a/apt.spec
> > +++ b/apt.spec
> > @@ -14,7 +14,7 @@
> >
> > Name: apt
> > Version:2.1.7
> > -Release:2%{?dist}
> > +Release:3%{?dist}
> > Summary:Command-line package manager for Debian packages
> >
> > License:GPLv2+
> > @@ -166,6 +166,10 @@ to package management with APT.
> > %autosetup -p1
> >
> > %build
> > +# This package fails its testsuite when LTO is enabled. It is not yet
> > clear if
> > +# this is an LTO issue or an issue with the package itself
> > +%define _lto_cflags %{nil}
> > +
> > %cmake -GNinja
> > %cmake_build
> >
> > @@ -308,6 +312,9 @@ exit 0
> > %doc %{_docdir}/%{name}-utils
> >
> > %changelog
> > +* Mon Jul 27 2020 Jeff law - 2.1.7-3
> > +- Disable LTO for now
> > +
> > * Mon Jul 27 2020 Fedora Release Engineering
> > - 2.1.7-2
> > - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
> >
> >
> >
> >
> https://src.fedoraproject.org/rpms/apt/c/f4bac7efd3c251ffb64107bc2f522c1d3c829b5c?branch=master
> >
> > --
> > You received this message due to your preference settings at
> >
> https://apps.fedoraproject.org/notifications/sergiomb.id.fedoraproject.org/email/49394
> ___
> 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
>
___
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
Re: Add new co-maintainer
I see you successfully added comaintainer :) чт, 9 июл. 2020 г., 10:14 Vascom : > Try again. > You can see that packager group present > https://admin.fedoraproject.org/accounts/user/view/yshestakov > > чт, 9 июл. 2020 г. в 10:09, Andrey Maslennikov >: > > > > Hm, looks like something is still wrong, I'm getting "This user must be > in one of the following groups to be allowed to be added to this project: > packager" error when adding "yshestakov" to my project. > > > > I'm using this page https://src.fedoraproject.org/rpms/ucx/adduser to > add him as admin, is that correct? > > ___ > > 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 > ___ 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
Re: Add new co-maintainer
Try again. You can see that packager group present https://admin.fedoraproject.org/accounts/user/view/yshestakov чт, 9 июл. 2020 г. в 10:09, Andrey Maslennikov : > > Hm, looks like something is still wrong, I'm getting "This user must be in > one of the following groups to be allowed to be added to this project: > packager" error when adding "yshestakov" to my project. > > I'm using this page https://src.fedoraproject.org/rpms/ucx/adduser to add him > as admin, is that correct? > ___ > 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 ___ 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
Re: Add new co-maintainer
Done. Now you can add yshestakov as comaintainer. чт, 9 июл. 2020 г. в 09:47, Andrey Maslennikov : > > Yes, I trust him completely on this matter. > > @Vascom thank you for your help! Should I open a ticket for it? > ___ > 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 ___ 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
Re: Add new co-maintainer
Are you sure that he will be a good maintainer? If you want to follow this https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer I can be a sponsor. чт, 9 июл. 2020 г. в 09:01, Andrey Maslennikov : > > Hello! > > I'm trying to add a co-maintainer to my project > (https://src.fedoraproject.org/rpms/ucx). User I want to add just recently > joined to Fedora environment (the name is yshestakov) and need a sponsor to > become a packager. I've tried to add him to the group, but he didn't get any > notifications about it. > > How can he become a co-maintainer of my project? > ___ > 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 ___ 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
Re: Review swaps
I took it. вт, 30 июн. 2020 г. в 06:28, Chenxiong Qi : > > Hello everyone, > > Could anyone please review these three packages? > > python-django-uuslug > https://bugzilla.redhat.com/show_bug.cgi?id=1851463 > > python-django-contrib-comments > https://bugzilla.redhat.com/show_bug.cgi?id=1851562 > > This is not a new package. It has been retired more than 8 weeks ago. > I'd like to continue maintaining this package. > > python-django-tinymce > https://bugzilla.redhat.com/show_bug.cgi?id=1852284 > > Thank you very much. > > -- > Regards, > Chenxiong Qi > ___ > 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 ___ 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
Re: Fedora 33 System-Wide Change proposal: Make btrfs the default file system for desktop variants
If this change will be accepted I think need to modify anaconda partition dialog for BTRFS scheme. It has difficult and not obvious behavior when user want to change automatically created partition scheme and resize BTRFS volumes. See this bugreport https://bugzilla.redhat.com/show_bug.cgi?id=1851212 пт, 26 июн. 2020 г. в 17:46, Ben Cotton : > > https://fedoraproject.org/wiki/Changes/BtrfsByDefault > > == Summary == > > For laptop and workstation installs of Fedora, we want to provide file > system features to users in a transparent fashion. We want to add new > features, while reducing the amount of expertise needed to deal with > situations like [https://pagure.io/fedora-workstation/issue/152 > running out of disk space.] Btrfs is well adapted to this role by > design philosophy, let's make it the default. > > == Owners == > > * Names: [[User:Chrismurphy|Chris Murphy]], [[User:Ngompa|Neal > Gompa]], [[User:Josef|Josef Bacik]], [[User:Salimma|Michel Alexandre > Salim]], [[User:Dcavalca|Davide Cavalca]], [[User:eeickmeyer|Erich > Eickmeyer]], [[User:ignatenkobrain|Igor Raits]], > [[User:Raveit65|Wolfgang Ulbrich]], [[User:Zsun|Zamir SUN]], > [[User:rdieter|Rex Dieter]], [[User:grinnz|Dan Book]], > [[User:nonamedotc|Mukundan Ragavan]] > * Emails: chrismur...@fedoraproject.org, ngomp...@gmail.com, > jo...@toxicpanda.com, mic...@michel-slm.name, dcava...@fb.com, > er...@ericheickmeyer.com, ignatenkobr...@fedoraproject.org, > fed...@raveit.de, z...@fedoraproject.org, rdie...@gmail.com, > gri...@gmail.com, nonamed...@gmail.com > > * Products: All desktop editions, spins, and labs > * Responsible WGs: Workstation Working Group, KDE Special Interest Group > > > == Detailed Description == > > Fedora desktop edition/spin variants will switch to using Btrfs as the > filesystem by default for new installs. Labs derived from these > variants inherit this change, and other editions may opt into this > change. > > The change is based on the installer's custom partitioning Btrfs > preset. It's been well tested for 7 years. > > 'Current partitioning' > vg/root LV mounted at style="color: tomato">/ and a vg/home LV mounted at /home. These are separate file system volumes, with > separate free/used space. > > 'Proposed partitioning' > root subvolume mounted at style="color: tomato">/ and home subvolume mounted at /home. Subvolumes don't have size, they act mostly like > directories, space is shared. > > 'Unchanged' > /boot will be a small ext4 volume. > A separate boot is needed to boot dm-crypt sysroot installations; it's > less complicated to keep the layout the same, regardless of whether > sysroot is encrypted. There will be no automatic snapshots/rollbacks. > > If you select to encrypt your data, LUKS (dm-crypt) will be still used > as it is today (with the small difference that Btrfs is used instead > of LVM+Ext4). There is upstream work on getting native encryption for > Btrfs that will be considered once ready and is subject of a different > change proposal in a future Fedora release. > > === Optimizations (Optional) === > > The detailed description above is the proposal. It's intended to be a > minimalist and transparent switch. It's also the same as was > [[Features/F16BtrfsDefaultFs|proposed]] (and > [https://lwn.net/Articles/446925/ accepted]) for Fedora 16. The > following optimizations improve on the proposal, but are not critical. > They are also transparent to most users. The general idea is agree to > the base proposal first, and then consider these as enhancements. > > Boot on Btrfs > > * Instead of a 1G ext4 boot, create a 1G Btrfs boot. > * Advantage: Makes it possible to include in a snapshot and rollback > regime. GRUB has stable support for Btrfs for 10+ years. > * Scope: Contingent on bootloader and installer team review and > approval. blivet should use mkfs.btrfs --mixed. > > Compression > > * Enable transparent compression using zstd on select directories: > /usr/var/lib/flatpak~/.local/share/flatpak > * Advantage: Saves space and significantly increase the lifespan of > flash-based media by reducing write amplification. It may improve > performance in some instances. > * Scope: Contingent on installer team review and approval to enhance > anaconda to perform the installation using mount -o > compress=zstd, then set the proper XATTR for each directory. > The XATTR can't be set until after the directories are created via: > rsync, rpm, or unsquashfs based installation. > > Additional subvolumes > > * /var/log//var/lib/libvirt/images and ~/.local/share/gnome-boxes/images/ will use separate > subvolumes. > * Advantage: Makes it easier to excluded them from snapshots, > rollbacks, and send/receive. (Btrfs snapshotting is not recursive, it > stops at a nested subvolume.) > * Scope: Anaconda knows how to do this already, just change the > kickstart to add additional subvolumes (minus the subvolume in style="color: tomato">~/. GNOME
Re: Fedora 33 System-Wide Change proposal: Make nano the default editor
I think it is good step to user friendly Fedora experience. +1 пт, 26 июн. 2020 г., 14:45 Charalampos Stratakis : > +1 > > I'm all for making the user experience better, and I think this change > contributes to that. > > - Original Message - > > From: "Ben Cotton" > > To: devel-annou...@lists.fedoraproject.org, "Development discussions > related to Fedora" > > > > Sent: Thursday, June 25, 2020 7:18:59 PM > > Subject: Fedora 33 System-Wide Change proposal: Make nano the default > editor > > > > https://fedoraproject.org/wiki/Changes/UseNanoByDefault > > > > == Summary == > > > > Let's make Fedora more approachable, by having a default editor that > > doesn't require specialist knowledge to use. > > > > == Owner == > > * Name: [[User:chrismurphy| Chris Murphy]] > > * Email: chrismur...@fedoraproject.org > > > > > > == Detailed Description == > > > > Users are exposed to the default editor when they use commands that > > call it. The main example here is something like git > > commit. > > > > Fedora does not currently have a default terminal text editor, because > > the $EDITOR environment variable is unset by default. But a common > > scenario where users wind up in a terminal text editor is when using > > 'git commit'. By default, git picks vi. You need to spend time > > learning how to use it, for even basic editing tasks. This increases > > the barrier to entry for those who are switching to Fedora and don't > > know how to use vi. It also makes things hard for those who don't > > particularly want to learn how to use vi. (These arguments would apply > > just as well if git picked Vim. vi is like hard mode for Vim, with > > fewer features, missing syntax highlighting, and no indication of what > > mode you are in. Even Vim users may feel lost and bewildered when > > using vi.) > > > > In contrast, Nano offers the kind of graphical text editing experience > > that people are used to, and therefore doesn't require specialist > > knowledge to use. It is already installed across most Fedora Editions > > and Spins. This proposal will make Nano the default editor, while > > continuing to install vim-minimal (which provides vi, but > > not Vim). People will still be able to call vi if they > > want to edit a file. It will also obviously be possible to change the > > default editor to vi or Vim, for those who want it. > > > > Why make Nano default and vi optional, rather than the other way > > round? Because Nano is the option that everyone can use. > > > > == Feedback == > > > > Pending ... > > > > == Benefit to Fedora == > > > > * Makes the default editor across all of Fedora more approachable. > > * Nano is also mostly self-documenting, by displaying common keyboard > > shortcuts on-screen. > > * More in line with the default editor of other distributions. > > > > == Scope == > > * Proposal owners: > > ** Modify comps to include nano Fedora wide. > > ** Create a new subpackage of nano, called > > nano-editor. > > ** nano-editor to include > > /usr/lib/environment.d/10-nano.conf, which sets > > $EDITOR to nano. > > > > With this approach, if nano is uninstalled, the > > configuration will be removed with it. At the same time, installing > > nano on its own won't install the conf. > > > > * Other developers: N/A > > > > * Release engineering: [https://pagure.io/releng/issue/9522 #9522] > > > > * Policies and guidelines: N/A > > > > * Trademark approval: N/A > > > > == Upgrade/compatibility impact == > > > > Will not apply to upgrades. > > > > == How To Test == > > > > Run export EDITOR="/usr/bin/nano". > > > > == User Experience == > > > > Users running git commit will be able to just type their > > commit message, rather than having to learn about insert mode, and > > they'll be able to cut and paste without having to learn special > > shortcuts. > > > > == Dependencies == > > > > No additional dependencies are required. > > > > == Contingency Plan == > > The contingency plan is to revert the change by removing the > > nano-editor package. > > > > * Contingency deadline: probably the beta? It's an easy change to revert. > > * Blocks release? If the change breaks the redirection to an editor, > > it should block the release. However, this is unlikely. > > * Blocks product? Potentially all. > > > > == Documentation == > > As part of this change, it would be good to add instructions for > > changing the default editor to the > > [https://docs.fedoraproject.org/en-US/quick-docs/ quick docs]. > > > > > > -- > > Ben Cotton > > He / Him / His > > Senior Program Manager, Fedora & CentOS Stream > > Red Hat > > TZ=America/Indiana/Indianapolis > > ___ > > 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: >
Re: Packaging problem
This flag added by default for security reason. So if you don't want
support previous release or have no request to support it you can skip.
Or wait answer from upstream.
вс, 31 мая 2020 г., 13:27 :
> And is applying the workaround just for Fedora 31 tolerated ?
>
> - Mail original -
> De: "Vascom"
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org>
> Envoyé: Dimanche 31 Mai 2020 12:13:58
> Objet: Re: Packaging problem
>
>
>
> I think Qt will not be upgraded in F31.
>
>
> You can just skip build for F31 and make package for F32 and rawhide only.
>
>
> вс, 31 мая 2020 г., 13:08 < ycollette.nos...@free.fr >:
>
>
> I tested with Fedora 31 and, it hangs.
> I works fine with Fedora 32.
>
> I report this problem to Jamulus or to Qt ? I think this problem is
> already fixed on Fedora 32.
>
> Does a Qt5 update is programmed for Fedora 31 ?
>
> - Mail original -
> De: "Vascom" < vasc...@gmail.com >
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org >
> Envoyé: Dimanche 31 Mai 2020 11:50:49
> Objet: Re: Packaging problem
>
>
>
> You should report upstream about the problem and fix code.
>
>
> вс, 31 мая 2020 г., 12:49 < ycollette.nos...@free.fr >:
>
>
> Hello again !
>
> I've got a new problem: a gcc flags trigger a problem during generation of
> an object file.
> The application is based on Qt5. The problematic file is produced from a
> moc generated file.
> The flag in question: -fcf-protection
>
> The solution I found is to send a custom set of flags to qmake.
>
> What is the best approach to remove a flags from a rpm macro variable ?
>
>
> # optflags %{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
> # -fcf-protection produce an error in an object generatoin ...
>
> qmake-qt5 Jamulus.pro \
> QMAKE_CFLAGS_DEBUG="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CFLAGS_RELEASE="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_DEBUG="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_RELEASE="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> CONFIG+=opus_shared_lib
>
> %make_build VERBOSE=1
>
>
>
> - Mail original -
> De: "ycollette nospam" < ycollette.nos...@free.fr >
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org >
> Envoyé: Samedi 30 Mai 2020 21:58:55
> Objet: Re: Packaging problem
>
> OK, thanks, it works with %{qmake_qt5} but not with %_qt5_qmake ...
>
> Thanks a lot
>
> I see that qmake_qt5 macro call _qt5_qmake with some flags ...
> I found the macro via rpm --showrc | grep qmake and I choose the wrong
> result.
>
>
> - Mail original -
> De: "Vascom" < vasc...@gmail.com >
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org >
> Envoyé: Samedi 30 Mai 2020 21:49:46
> Objet: Re: Packaging problem
>
> First you should use this macro %{qmake_qt5} and remove
> %{set_build_flags}.
>
> And show your spec or give srpm.
>
> сб, 30 мая 2020 г. в 22:21, < ycollette.nos...@free.fr >:
> >
> > Hello,
> >
> > I've got a problem with a package.
> > I am trying to clean up a spec file before sending it to review and I've
> got an error:
> >
> > erreur : Empty %files file
> /home/artelys/rpmbuild/BUILD/jamulus-c6b6e3ab02d7ec1e93edeeb8042a89a561924826/debugsourcefiles.list
>
> >
> > The code is Qt-5 / c++. It's an application which allows to perform live
> rehearsale via an internet connection.
> >
> > On the gcc / c++ command line, I can see the -g flags.
> >
> > The build section:
> >
> > %{set_build_flags}
> >
> > %_qt5_qmake Jamulus.pro CONFIG+=opus_shared_lib
> >
> > %make_build VERBOSE=1
> >
> > The install section (the qmake file defines no install rule so I must
> install everything manually):
> >
> > %__install -m 755 -d %{buildroot}/%{_bindir}/
> > %__install -m 755 Jamulus %{buildroot}%{_bindir}/jamulus
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/applications/
> > %__install -m 644 distributions/jamulus.desktop
> %{buildroot}%{_datadir}/applic
Re: Packaging problem
I think Qt will not be upgraded in F31.
You can just skip build for F31 and make package for F32 and rawhide only.
вс, 31 мая 2020 г., 13:08 :
> I tested with Fedora 31 and, it hangs.
> I works fine with Fedora 32.
>
> I report this problem to Jamulus or to Qt ? I think this problem is
> already fixed on Fedora 32.
>
> Does a Qt5 update is programmed for Fedora 31 ?
>
> - Mail original -
> De: "Vascom"
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org>
> Envoyé: Dimanche 31 Mai 2020 11:50:49
> Objet: Re: Packaging problem
>
>
>
> You should report upstream about the problem and fix code.
>
>
> вс, 31 мая 2020 г., 12:49 < ycollette.nos...@free.fr >:
>
>
> Hello again !
>
> I've got a new problem: a gcc flags trigger a problem during generation of
> an object file.
> The application is based on Qt5. The problematic file is produced from a
> moc generated file.
> The flag in question: -fcf-protection
>
> The solution I found is to send a custom set of flags to qmake.
>
> What is the best approach to remove a flags from a rpm macro variable ?
>
>
> # optflags %{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
> # -fcf-protection produce an error in an object generatoin ...
>
> qmake-qt5 Jamulus.pro \
> QMAKE_CFLAGS_DEBUG="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CFLAGS_RELEASE="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_DEBUG="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_RELEASE="%{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection" \
> CONFIG+=opus_shared_lib
>
> %make_build VERBOSE=1
>
>
>
> - Mail original -
> De: "ycollette nospam" < ycollette.nos...@free.fr >
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org >
> Envoyé: Samedi 30 Mai 2020 21:58:55
> Objet: Re: Packaging problem
>
> OK, thanks, it works with %{qmake_qt5} but not with %_qt5_qmake ...
>
> Thanks a lot
>
> I see that qmake_qt5 macro call _qt5_qmake with some flags ...
> I found the macro via rpm --showrc | grep qmake and I choose the wrong
> result.
>
>
> - Mail original -
> De: "Vascom" < vasc...@gmail.com >
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org >
> Envoyé: Samedi 30 Mai 2020 21:49:46
> Objet: Re: Packaging problem
>
> First you should use this macro %{qmake_qt5} and remove
> %{set_build_flags}.
>
> And show your spec or give srpm.
>
> сб, 30 мая 2020 г. в 22:21, < ycollette.nos...@free.fr >:
> >
> > Hello,
> >
> > I've got a problem with a package.
> > I am trying to clean up a spec file before sending it to review and I've
> got an error:
> >
> > erreur : Empty %files file
> /home/artelys/rpmbuild/BUILD/jamulus-c6b6e3ab02d7ec1e93edeeb8042a89a561924826/debugsourcefiles.list
>
> >
> > The code is Qt-5 / c++. It's an application which allows to perform live
> rehearsale via an internet connection.
> >
> > On the gcc / c++ command line, I can see the -g flags.
> >
> > The build section:
> >
> > %{set_build_flags}
> >
> > %_qt5_qmake Jamulus.pro CONFIG+=opus_shared_lib
> >
> > %make_build VERBOSE=1
> >
> > The install section (the qmake file defines no install rule so I must
> install everything manually):
> >
> > %__install -m 755 -d %{buildroot}/%{_bindir}/
> > %__install -m 755 Jamulus %{buildroot}%{_bindir}/jamulus
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/applications/
> > %__install -m 644 distributions/jamulus.desktop
> %{buildroot}%{_datadir}/applications/
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/pixmaps/
> > %__install -m 644 distributions/jamulus.png
> %{buildroot}%{_datadir}/pixmaps/
> >
> > How can I build the debug part of the package ?
> >
> > The only solution I've found is to add:
> >
> > %global debug_package %{nil}
> >
> > At the beginning of the spec file ...
> >
> > Best regards,
> >
> > YC
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@l
Re: Packaging problem
You should report upstream about the problem and fix code.
вс, 31 мая 2020 г., 12:49 :
> Hello again !
>
> I've got a new problem: a gcc flags trigger a problem during generation of
> an object file.
> The application is based on Qt5. The problematic file is produced from a
> moc generated file.
> The flag in question: -fcf-protection
>
> The solution I found is to send a custom set of flags to qmake.
>
> What is the best approach to remove a flags from a rpm macro variable ?
>
>
> # optflags %{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
> # -fcf-protection produce an error in an object generatoin ...
>
> qmake-qt5 Jamulus.pro \
> QMAKE_CFLAGS_DEBUG="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CFLAGS_RELEASE="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_DEBUG="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_RELEASE="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> CONFIG+=opus_shared_lib
>
> %make_build VERBOSE=1
>
>
>
> - Mail original -
> De: "ycollette nospam"
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org>
> Envoyé: Samedi 30 Mai 2020 21:58:55
> Objet: Re: Packaging problem
>
> OK, thanks, it works with %{qmake_qt5} but not with %_qt5_qmake ...
>
> Thanks a lot
>
> I see that qmake_qt5 macro call _qt5_qmake with some flags ...
> I found the macro via rpm --showrc | grep qmake and I choose the wrong
> result.
>
>
> - Mail original -
> De: "Vascom"
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org>
> Envoyé: Samedi 30 Mai 2020 21:49:46
> Objet: Re: Packaging problem
>
> First you should use this macro %{qmake_qt5} and remove %{set_build_flags}.
>
> And show your spec or give srpm.
>
> сб, 30 мая 2020 г. в 22:21, :
> >
> > Hello,
> >
> > I've got a problem with a package.
> > I am trying to clean up a spec file before sending it to review and I've
> got an error:
> >
> > erreur : Empty %files file
> /home/artelys/rpmbuild/BUILD/jamulus-c6b6e3ab02d7ec1e93edeeb8042a89a561924826/debugsourcefiles.list
> >
> > The code is Qt-5 / c++. It's an application which allows to perform live
> rehearsale via an internet connection.
> >
> > On the gcc / c++ command line, I can see the -g flags.
> >
> > The build section:
> >
> > %{set_build_flags}
> >
> > %_qt5_qmake Jamulus.pro CONFIG+=opus_shared_lib
> >
> > %make_build VERBOSE=1
> >
> > The install section (the qmake file defines no install rule so I must
> install everything manually):
> >
> > %__install -m 755 -d %{buildroot}/%{_bindir}/
> > %__install -m 755 Jamulus %{buildroot}%{_bindir}/jamulus
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/applications/
> > %__install -m 644 distributions/jamulus.desktop
> %{buildroot}%{_datadir}/applications/
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/pixmaps/
> > %__install -m 644 distributions/jamulus.png
> %{buildroot}%{_datadir}/pixmaps/
> >
> > How can I build the debug part of the package ?
> >
> > The only solution I've found is to add:
> >
> > %global debug_package %{nil}
> >
> > At the beginning of the spec file ...
> >
> > Best regards,
> >
> > YC
> > ___
> > 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
> ___
> 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.or
Re: Packaging problem
Also
Macro forms of system executables SHOULD NOT be used except when there
is a need to allow the location of those executables to be
configurable. For example, rm should be used in preference to %{__rm},
but %{__python3} is acceptable.
сб, 30 мая 2020 г. в 22:51, :
>
> Yes, you're right :)
>
> Here is a link to a build with the %global debug_package %{nil} :
>
> https://download.copr.fedorainfracloud.org/results/ycollet/linuxmao/fedora-32-x86_64/01415804-jamulus/
>
> - Mail original -
> De: "Björn 'besser82' Esser"
> À: "Development discussions related to Fedora"
> Envoyé: Samedi 30 Mai 2020 21:44:08
> Objet: Re: Packaging problem
>
> Am Samstag, den 30.05.2020, 21:20 +0200 schrieb
> ycollette.nos...@free.fr:
> > Hello,
> >
> > I've got a problem with a package.
> > I am trying to clean up a spec file before sending it to review and
> > I've got an error:
> >
> > erreur : Empty %files file /home/artelys/rpmbuild/BUILD/jamulus-
> > c6b6e3ab02d7ec1e93edeeb8042a89a561924826/debugsourcefiles.list
> >
> > The code is Qt-5 / c++. It's an application which allows to perform
> > live rehearsale via an internet connection.
> >
> > On the gcc / c++ command line, I can see the -g flags.
> >
> > The build section:
> >
> > %{set_build_flags}
> >
> > %_qt5_qmake Jamulus.pro CONFIG+=opus_shared_lib
> >
> > %make_build VERBOSE=1
> >
> > The install section (the qmake file defines no install rule so I must
> > install everything manually):
> >
> > %__install -m 755 -d %{buildroot}/%{_bindir}/
> > %__install -m 755 Jamulus %{buildroot}%{_bindir}/jamulus
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/applications/
> > %__install -m 644 distributions/jamulus.desktop
> > %{buildroot}%{_datadir}/applications/
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/pixmaps/
> > %__install -m 644 distributions/jamulus.png
> > %{buildroot}%{_datadir}/pixmaps/
> >
> > How can I build the debug part of the package ?
> >
> > The only solution I've found is to add:
> >
> > %global debug_package %{nil}
> >
> > At the beginning of the spec file ...
>
>
> Without a scratch build and/or a link to the spec file / srpm its hard
> to help, I guess…
>
> Cheers
> Björn
>
> ___
> 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
> ___
> 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
___
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
Re: Packaging problem
First you should use this macro %{qmake_qt5} and remove %{set_build_flags}.
And show your spec or give srpm.
сб, 30 мая 2020 г. в 22:21, :
>
> Hello,
>
> I've got a problem with a package.
> I am trying to clean up a spec file before sending it to review and I've got
> an error:
>
> erreur : Empty %files file
> /home/artelys/rpmbuild/BUILD/jamulus-c6b6e3ab02d7ec1e93edeeb8042a89a561924826/debugsourcefiles.list
>
> The code is Qt-5 / c++. It's an application which allows to perform live
> rehearsale via an internet connection.
>
> On the gcc / c++ command line, I can see the -g flags.
>
> The build section:
>
> %{set_build_flags}
>
> %_qt5_qmake Jamulus.pro CONFIG+=opus_shared_lib
>
> %make_build VERBOSE=1
>
> The install section (the qmake file defines no install rule so I must install
> everything manually):
>
> %__install -m 755 -d %{buildroot}/%{_bindir}/
> %__install -m 755 Jamulus %{buildroot}%{_bindir}/jamulus
>
> %__install -m 755 -d %{buildroot}/%{_datadir}/applications/
> %__install -m 644 distributions/jamulus.desktop
> %{buildroot}%{_datadir}/applications/
>
> %__install -m 755 -d %{buildroot}/%{_datadir}/pixmaps/
> %__install -m 644 distributions/jamulus.png %{buildroot}%{_datadir}/pixmaps/
>
> How can I build the debug part of the package ?
>
> The only solution I've found is to add:
>
> %global debug_package %{nil}
>
> At the beginning of the spec file ...
>
> Best regards,
>
> YC
> ___
> 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
___
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
Re: [HEADS UP] F33 Boost 1.73.0 rebuilds starting in a side tag
OK I just write it because you request report about "I don't see changes in changelog". чт, 28 мая 2020 г., 15:16 Jonathan Wakely : > On 28/05/20 14:47 +0300, Vascom wrote: > >Hi. > > > >pulseeffects package depends on boost and I don't see changes in > changelog. > > I've literally just started. The new boost hasn't even finished yet: > https://koji.fedoraproject.org/koji/taskinfo?taskID=45094034 > > Do you need to update pulseeffects? If not, then you don't need to > worry about the rebuilds. A new build will arrive in rawhide when it's > ready. > > The request to check with me was if you need to update the package. > > > >чт, 28 мая 2020 г., 11:45 Jonathan Wakely : > > > >> I'm starting the rebuilds for Boost 1.73.0 and packages that depend on > >> it, using the f33-boost side tag. > >> > >> If you see "Rebuilt for Boost 1.73.0" in the changelog for one of your > >> packages, please do not make another update. Instead co-ordinate with > >> me to use the side tag for your update (if your package also depends > >> on Python then also talk to Miro Hrončok). > >> > >> If your package depends on Boost and you don't see "Rebuilt for Boost > >> 1.73.0" in the %changelog yet, it might be worth checking with me > >> anyway, as I'll probably be starting it soon. > >> > >> The new Boost will include the following changes: > >> > >> - rename boost-jam package to boost-b2, and /usr/bin/bjam with > >>/usr/bin/b2 (it looks nothing in Fedora uses this anyway) > >> > >> - obsolete the separate boost-nowide package, as Boost 1.73.0 includes > >>the Boost.Nowide library now > >> > >> jhogarth, please confirm you're aware of the nowide change. The > >> existing boost-nowide package will need to be retired in rawhide. > >> > >> > >> New changes already in rawhide: > >> > >> - boost-python3-devel subpackage removed, those files are provided by > >>boost-devel now. > >> > >> - Boost libraries no longer link to libpython. > >> > >> Thanks for your help. > >> ___ > >> 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 > >> > > >___ > >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 > ___ > 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 > ___ 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
Re: [HEADS UP] F33 Boost 1.73.0 rebuilds starting in a side tag
Hi. pulseeffects package depends on boost and I don't see changes in changelog. чт, 28 мая 2020 г., 11:45 Jonathan Wakely : > I'm starting the rebuilds for Boost 1.73.0 and packages that depend on > it, using the f33-boost side tag. > > If you see "Rebuilt for Boost 1.73.0" in the changelog for one of your > packages, please do not make another update. Instead co-ordinate with > me to use the side tag for your update (if your package also depends > on Python then also talk to Miro Hrončok). > > If your package depends on Boost and you don't see "Rebuilt for Boost > 1.73.0" in the %changelog yet, it might be worth checking with me > anyway, as I'll probably be starting it soon. > > The new Boost will include the following changes: > > - rename boost-jam package to boost-b2, and /usr/bin/bjam with >/usr/bin/b2 (it looks nothing in Fedora uses this anyway) > > - obsolete the separate boost-nowide package, as Boost 1.73.0 includes >the Boost.Nowide library now > > jhogarth, please confirm you're aware of the nowide change. The > existing boost-nowide package will need to be retired in rawhide. > > > New changes already in rawhide: > > - boost-python3-devel subpackage removed, those files are provided by >boost-devel now. > > - Boost libraries no longer link to libpython. > > Thanks for your help. > ___ > 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 > ___ 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
Re: Presentation
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_Your_Review_Request ср, 27 мая 2020 г., 20:53 Yann Collette : > > Le 27/05/2020 à 17:39, Peter Lemenkov a écrit : > > Hello Yann! > > > > ср, 27 мая 2020 г. в 15:05, : > >> Hello, > >> > >> I just registered the Fedora devel list. > >> My name is Yann Collette. > >> I use Fedora distribution since ... (I started with a Linux 1.2.7 :) > and stay attached to Redhat / Fedora for a lng time). > >> I use Fedora for music production and I manage a Fedora COPR repo to > provide tools related to music: > >> > >> https://copr.fedorainfracloud.org/coprs/ycollet/linuxmao/ > >> > >> All the spec files are on github: > >> > >> https://github.com/ycollet/fedora-spec > > > > Wow! That's a substantial amount of work! Well done! > > > >> If you're are looking for people to help packaging and maintaining > packages, I can help. > > As a person who is interested in a similarly obscure use cases I'd > > like to propose you a different way. Instead of waiting for someone > > who pops up and asks you for help with packaging you'd better to step > > in and start adding packages to Fedora and helping with existing ones. > > From my experience people are more likely to act when something big is > > going already. And the amount of packages you're dealing with is > > already huge! > > > > We can guide you with all technical details related to adding rpms to > > Fedora repos. > > OK, thanks. > > I will first try to add lv2lint. It's a syntax checker for LV2 plugins. > > https://gitlab.com/drobilla/lv2lint > > The first step is to open a bug report on the Fedora bug tracker to ask > to add this package and add a link to the src rpm file in the bug report ? > > The spec file for this package is already here: > > https://github.com/ycollet/fedora-spec/blob/master/lv2lint/lv2lint.spec > > ___ > 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 > ___ 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
libbappstream-glib icon type=stock not supported
Hi all. Some packages has string ... And appstream-util validate-relax show error ? tag-invalid : stock icon is not valid There exist bugreport one year old! https://bugzilla.redhat.com/show_bug.cgi?id=1584944 Please pay attention to it. No I don't know what to do: 1. Remove this string from xml file. 2. Disable validation at all. But guidelines say that I MUST run it https://docs.fedoraproject.org/en-US/packaging-guidelines/AppData/#_app_data_validate_usage And I see that some packages not run validation like plasma-systemsettings bit still contain metainfo .xml with systemsettings -- Best Regards, Vasiliy Glazov ___ 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
Orphaning kchildlock
kchildlock orphaned. It is for KDE4 and has dead upstream. -- Best regards, Vasiliy Glazov ___ 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
Re: Speed up bash starting time (slow scripts in profile.d, /etc/bash_completion.d)
Are you use SSD? I have 0.087s on it. сб, 16 мая 2020 г., 13:57 Dominique Martinet : > Hi, > > once in a while I get annoyed at how slow bash is to startup; using a > tiling wm poping a new shell is supposed to be quite fast but I'm > staring at a new empty window for ~1s everytime and it gets annoying... > > According to https://xkcd.com/1205/ wasting 1s 50+ times a day is worth > spending some time to try to improve it so let's see what we can do :) > > > Here's the baseline on my machine: > $ time bash -l < /dev/null > > real0m0.341s > user0m0.198s > sys 0m0.146s > > > And a few low hanging fruits I could find adding `-x 2>&1 | ts "%.s"`: > - down to 0.288s after removing /etc/profile.d/flatpak.sh > (flatpak-1.6.3-1.fc32.x86_64) > > - down to 0.225s after removing /etc/profile.d/modules.sh > (environment-modules-4.4.1-2.fc32.x86_64) > > - down to 0.130s after moving /etc/bash_completion.d/* to > /usr/share/bash-completion/completions/ > This one is not actually a no-op: bash-completion loads things from /etc > at shell startup time, but things in /usr at first tab time, so if the > file in /usr/share is not named by the same prefix as the command it > help completes it won't work anymore, but in most case here it will > still work just the same (slightly slower on first use) > > Here's the list of files I had in there and their packages: > authselect-completion.sh authselect-1.2.1-1.fc32.x86_64 > fcoeadm fcoe-utils-1.0.32-9.git9834b34.fc31.x86_64 > javaws.bash icedtea-web-2.0.0-pre.0.2.alpha13.patched1.fc32.x86_64 > perf perf-5.6.7-300.fc32.x86_64 > trace-cmd.bash trace-cmd-2.8.3-1.fc32.x86_64 > bpftool bpftool-5.6.7-300.fc32.x86_64 > fcoemon fcoe-utils-1.0.32-9.git9834b34.fc31.x86_64 > policyeditor.bash icedtea-web-2.0.0-pre.0.2.alpha13.patched1.fc32.x86_64 > xl.sh xen-runtime-4.13.0-7.fc32.x86_64 > cargo cargo-1.43.1-1.fc32.x86_64 > fzf fzf-0.21.1-1.fc32.x86_64 > lilv lilv-0.24.6-2.fc32.x86_64 > python-argcomplete.sh python3-argcomplete-1.10.0-4.fc32.noarch > dbus-bash-completion.sh dbus-glib-devel-0.110-7.fc32.x86_64 > gluster glusterfs-cli-7.5-1.fc32.x86_64 > lldpad lldpad-1.0.1-16.git036e314.fc32.x86_64 > redefine_filedir bash-completion-2.8-8.fc32.noarch > dog sheepdog-1.0.1-10.fc31.x86_64 > itweb-settings.bash icedtea-web-2.0.0-pre.0.2.alpha13.patched1.fc32.x86_64 > lldptool lldpad-1.0.1-16.git036e314.fc32.x86_64 > torsocks torsocks-2.3.0-5.fc32.x86_64 > > > 341 to 130ms is a good start I guess, the rest of the waiting time > probably now outweights bash and will get some looking at at a later > point, but might as well start somewhere. > > How should I go about with that? Open bz bugs to all the packages I > listed? strongly suggesting to get things to move to /usr/share (17) and > flatpak (suggest some kind of cache? not sure they'll be interested...) > and environment-modules (not sure what to suggest there, I only have > environment-modules because I need to test something with openmpi from > time to time and it comes with it...) > > > It might also make sense to have a packaging guideline suggesting to > avoid /etc/bash_completion.d in favor of the /usr/share variant, I > couldn't find anything here[1] but I might not have looked thoroughly > enough... > [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/ > > > Would anyone be willing to help, something is telling me that doing this > alone would take more time than what I'd save in the end, but a few > people considering it'll help everyone might be ;) > > > Thanks! > -- > Dominique > ___ > 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 > ___ 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
Re: Boost packages conflict
Yes, after system installed on hard drive the same error. But after upgrading boost* error is gone and packages normal installed. пт, 15 мая 2020 г. в 00:33, Vascom : > > I just could reproduce it. > > Steps: > 1. Run KDE spin F32 in virt-manager. > 2. dnf install toolnix > > Result: > > mkvtoolnix x86_64 46.0.0-1.fc32 updates 5.2 M > Installing dependencies: > boost169-filesystem x86_64 1.69.0-6.fc32 fedora53 k > boost169-system x86_64 1.69.0-6.fc32 fedora12 k > fmt x86_64 6.2.1-1.fc32updates 115 k > libebml x86_64 1.3.10-2.fc32 fedora87 k > libmatroska x86_64 1.5.2-2.fc32fedora 178 k > pugixml x86_64 1.10-2.fc32 fedora 100 k > > ... > Error: Transaction test error: > file /usr/lib64/libboost_system.so.1.69.0 from install of > boost169-system-1.69.0-6.fc32.x86_64 conflicts with file from package > boost-system-1.69.0-15.fc32.x86_64 > > So I think after installation result will be the same. May be need > first dnf upgrade. > > пт, 15 мая 2020 г. в 00:10, Dan Horák : > > > > On Thu, 14 May 2020 20:08:07 - > > "Denis Arnaud" wrote: > > > > > > No one try to install it now. New boost will be in F33 only. > > > > > > > > But if boost not installed in system and user want install for > > > > example libreoffice he will get this error and can't install any > > > > package requires boost. > > > > > > > > boost169 must be removed from F32 repos at all. > > > > > > > > чт, 14 мая 2020 г. в 22:19, Samuel Sieb > > > > > > > > > On 5/14/20 10:49 AM, Vitaly Zaitsev via devel wrote: > > > > > > The boost169 compatibility package conflicts with the regular > > > > > > boost on Fedora 32. Both packages provides the same libraries. > > > > > > > > > > > > Error: Transaction test error: > > > > > >file /usr/lib64/libboost_system.so.1.69.0 from install of > > > > > > boost169-system-1.69.0-6.fc32.x86_64 conflicts with file from > > > > > > package boost-system-1.69.0-15.fc32.x86_64 > > > > > > > > > > What's the point of having a compatibility package for the same > > > > > version as the regular one? I'm guessing that means they're in > > > > > the process of preparing a new release, but why are you trying to > > > > > install it now? ___ > > > > > devel mailing list -- devel(a)lists.fedoraproject.org > > > > > To unsubscribe send an email to > > > > > devel-leave(a)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 > > > > No one try to install it now. New boost will be in F33 only. > > > > > > > > But if boost not installed in system and user want install for > > > > example libreoffice he will get this error and can't install any > > > > package requires boost. > > > > > > > > boost169 must be removed from F32 repos at all. > > > > > > > > чт, 14 мая 2020 г. в 22:19, Samuel Sieb > > > > > > > > > On 5/14/20 10:49 AM, Vitaly Zaitsev via devel wrote: > > > > > > The boost169 compatibility package conflicts with the regular > > > > > > boost on Fedora 32. Both packages provides the same libraries. > > > > > > > > > > > > Error: Transaction test error: > > > > > >file /usr/lib64/libboost_system.so.1.69.0 from install of > > > > > > boost169-system-1.69.0-6.fc32.x86_64 conflicts with file from > > > > > > package boost-system-1.69.0-15.fc32.x86_64 > > > > > > > > > > What's the point of having a compatibility package for the same > > > > > version as the regular one? I'm guessing that means they're in > > > > > the process of preparing a new release, but why are you trying to > > > > > install it now? ___ > > > > > devel mail
Re: Boost packages conflict
I just could reproduce it. Steps: 1. Run KDE spin F32 in virt-manager. 2. dnf install toolnix Result: mkvtoolnix x86_64 46.0.0-1.fc32 updates 5.2 M Installing dependencies: boost169-filesystem x86_64 1.69.0-6.fc32 fedora53 k boost169-system x86_64 1.69.0-6.fc32 fedora12 k fmt x86_64 6.2.1-1.fc32updates 115 k libebml x86_64 1.3.10-2.fc32 fedora87 k libmatroska x86_64 1.5.2-2.fc32fedora 178 k pugixml x86_64 1.10-2.fc32 fedora 100 k ... Error: Transaction test error: file /usr/lib64/libboost_system.so.1.69.0 from install of boost169-system-1.69.0-6.fc32.x86_64 conflicts with file from package boost-system-1.69.0-15.fc32.x86_64 So I think after installation result will be the same. May be need first dnf upgrade. пт, 15 мая 2020 г. в 00:10, Dan Horák : > > On Thu, 14 May 2020 20:08:07 - > "Denis Arnaud" wrote: > > > > No one try to install it now. New boost will be in F33 only. > > > > > > But if boost not installed in system and user want install for > > > example libreoffice he will get this error and can't install any > > > package requires boost. > > > > > > boost169 must be removed from F32 repos at all. > > > > > > чт, 14 мая 2020 г. в 22:19, Samuel Sieb > > > > > > > On 5/14/20 10:49 AM, Vitaly Zaitsev via devel wrote: > > > > > The boost169 compatibility package conflicts with the regular > > > > > boost on Fedora 32. Both packages provides the same libraries. > > > > > > > > > > Error: Transaction test error: > > > > >file /usr/lib64/libboost_system.so.1.69.0 from install of > > > > > boost169-system-1.69.0-6.fc32.x86_64 conflicts with file from > > > > > package boost-system-1.69.0-15.fc32.x86_64 > > > > > > > > What's the point of having a compatibility package for the same > > > > version as the regular one? I'm guessing that means they're in > > > > the process of preparing a new release, but why are you trying to > > > > install it now? ___ > > > > devel mailing list -- devel(a)lists.fedoraproject.org > > > > To unsubscribe send an email to > > > > devel-leave(a)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 > > > No one try to install it now. New boost will be in F33 only. > > > > > > But if boost not installed in system and user want install for > > > example libreoffice he will get this error and can't install any > > > package requires boost. > > > > > > boost169 must be removed from F32 repos at all. > > > > > > чт, 14 мая 2020 г. в 22:19, Samuel Sieb > > > > > > > On 5/14/20 10:49 AM, Vitaly Zaitsev via devel wrote: > > > > > The boost169 compatibility package conflicts with the regular > > > > > boost on Fedora 32. Both packages provides the same libraries. > > > > > > > > > > Error: Transaction test error: > > > > >file /usr/lib64/libboost_system.so.1.69.0 from install of > > > > > boost169-system-1.69.0-6.fc32.x86_64 conflicts with file from > > > > > package boost-system-1.69.0-15.fc32.x86_64 > > > > > > > > What's the point of having a compatibility package for the same > > > > version as the regular one? I'm guessing that means they're in > > > > the process of preparing a new release, but why are you trying to > > > > install it now? ___ > > > > devel mailing list -- devel(a)lists.fedoraproject.org > > > > To unsubscribe send an email to > > > > devel-leave(a)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 > > Yes, boost169 should never have ended up in Fedora 32 in the first > > place (blame on me, sorry). The thing is that we can no longer block > > it: https://pagure.io/releng/issue/9455 > > I think an update of fedora-obsolete-packages could "virtually" remove > boost169, without touching boost itself. > > > Dan > ___ > 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 ___ devel mailing list --
Re: Boost packages conflict
Hm, now work. But it was... чт, 14 мая 2020 г. в 23:56, Samuel Sieb : > > On 5/14/20 1:34 PM, Denis Arnaud wrote: > > So, should I add the obsoletes clauses for every package, or is it fine to > > leave it as it is now? > > I believe it's fine to just leave it as it is. I did a couple of > installs and tested installing applications and it only brings in the > regular boost packages. In any case, there should never be a conflict > unless you deliberately try to install both at the same time. > ___ > 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 ___ 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
Re: Boost packages conflict
No one try to install it now. New boost will be in F33 only. But if boost not installed in system and user want install for example libreoffice he will get this error and can't install any package requires boost. boost169 must be removed from F32 repos at all. чт, 14 мая 2020 г. в 22:19, Samuel Sieb : > > On 5/14/20 10:49 AM, Vitaly Zaitsev via devel wrote: > > The boost169 compatibility package conflicts with the regular boost on > > Fedora 32. Both packages provides the same libraries. > > > > Error: Transaction test error: > >file /usr/lib64/libboost_system.so.1.69.0 from install of > > boost169-system-1.69.0-6.fc32.x86_64 conflicts with file from package > > boost-system-1.69.0-15.fc32.x86_64 > > What's the point of having a compatibility package for the same version > as the regular one? I'm guessing that means they're in the process of > preparing a new release, but why are you trying to install it now? > ___ > 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 ___ 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
Re: qt5-devel dropped?
Now we must use qt5-qtbase-devel. пн, 11 мая 2020 г., 12:01 Susi Lehtola : > Hi, > > > I just noticed that qt5-devel has been dropped. Is the idea to force > all other packages to change > > Requires: qt5-devel > > into > > Requires: qt5-qtbase > Requires: qt5-qtbase-gui > Requires: qt5-qtbase-mysql > Requires: qt5-qtbase-postgresql > Requires: qt5-qtconnectivity > Requires: qt5-qtdeclarative > Requires: qt5-qtdoc > Requires: qt5-qtgraphicaleffects > Requires: qt5-qtimageformats > Requires: qt5-qtlocation > Requires: qt5-qtmultimedia > Requires: qt5-qtquickcontrols > Requires: qt5-qtquickcontrols2 > Requires: qt5-qtscript > Requires: qt5-qtsensors > Requires: qt5-qtserialport > Requires: qt5-qtsvg > Requires: qt5-qttools > Requires: qt5-qtwayland > Requires: qt5-qtwebchannel > Requires: qt5-qtwebsockets > Requires: qt5-qtx11extras > Requires: qt5-qtxmlpatterns > -- > Susi Lehtola > Fedora Project Contributor > jussileht...@fedoraproject.org > ___ > 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 > ___ 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
Re: Review request
I will do it. пн, 4 мая 2020 г., 11:03 Bob Hepple : > Hello, > > Although I'm new here, I've had a few packages go through review > already and I'm very grateful for the help and education provided by > the reviewers. > > But there is one package that I put up for review about a month ago > and I haven't had any luck in attracting a reviewer. It's here - > https://bugzilla.redhat.com/show_bug.cgi?id=1821172 > > Now it may have been my fault as at the time I thought I was supposed > to include a run of fedora-review, and prospective reviewers may have > scanned the request and assumed that it has already been reviewed. > > If anyone out there in reviewer-land would like to take a look at the > package I think it could be a useful addition to the fedora wayland > offering. The short description is: > > wl-gammactl - Small GTK GUI application to set contrast, brightness > and gamma for wayland compositors > > Thanks muchly > > Bob Hepple > ___ > 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 > ___ 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
Re: boost package in fedora
Thank you. пт, 24 апр. 2020 г., 14:40 Jonathan Wakely : > On 20/04/20 15:43 +0300, Vascom wrote: > >Will Boost ever be updated on Fedora again? > > > >https://bugzilla.redhat.com/show_bug.cgi?id=1558278 > > Yes. > ___ > 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 > ___ 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
Re: Non-responsive maintainer: laxathom (Xavier Lamien)
I already built it. But you can update to 6.0.5 :) ср, 22 апр. 2020 г. в 22:04, Xavier Lamien : > > Oh hi, > > Looks like your email get lost in the pile if you tried to reach me > personally or my bugzilla's filter is too efficient I'd say. > > Any way, I'll have a look at your ticket asap. > Also, I'm more than welcome to get co-maintainer on this package so feel free > to request access since you're looking into it. > > Cheers, > -x > > > On Wed, Apr 22, 2020, 8:10 PM Breno Brand Fernandes > wrote: >> >> Hi, >> >> I've been trying to get in contact with Xavier Lamien since Sep 2019 [1]. >> The package libgdiplus is particularly important to have mono built in EPEL >> 8. >> >> I am following the policy for non-responsive package maintainers [2]. >> In 7 days if I don't get any answers I will be filling a ticket to maintain >> it if none is against it. >> >> 1 https://bugzilla.redhat.com/show_bug.cgi?id=1749560 >> 2 >> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ >> >> Thank you. >> ___ >> 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 > > ___ > 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 ___ 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
boost package in fedora
Will Boost ever be updated on Fedora again? https://bugzilla.redhat.com/show_bug.cgi?id=1558278 ___ 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
Re: Fedora 32 FTBFS packages to be orphaned in 1 week
I would like to take arduino. I can make buildable again 1.8.5 version and may be update it to latest. My FAS name: vascom -- Best regards, Vasiliy Glazov вс, 29 мар. 2020 г. в 14:15, Miro Hrončok : > > According to the Fedora's Fails To Build From Source policy: > > https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ > > The following packages will be orphaned on Monday 2020-04-06. > > Their F32FTBFS Bugzillas are in NEW state for the defined period of time and > they have the necessary reminders. They were not successfully rebuilt in > Fedora > 32 since the Bugzillas were opened. > > If you can fix your package to build, perform a build in koji, and either > create > an update in bodhi, or close the relevant bug without creating an update, if > updating is not appropriate. If you are working on a fix, set the status to > ASSIGNED to acknowledge this and prevent the orphaning. > > Oprhaning is a easily revertible nondesctructiove action. > Only packages orphaned for 6+ weeks will be retired (removed from) Fedora > rawhide (i.e. not form Fedora 32). > > Maintainers by package: > 0ad ignatenkobrain pcpa pwalter > CPUFreqUtility f1ash > GConf2 alexl caillon caolanm johnp mbarnes rhughes rstrode ssp > walters > GREYCstoration tnorth > SDL2_gfx ignatenkobrain lkundrak > abcm2ps gemi > adapta-gtk-theme atim > afpfs-ng lkundrak > aircrack-ng ichavero > antlr4 gil jkastner lef mizdebsk sdgathman > apache-commons-dbutils mizdebsk spike > apache-commons-email mizdebsk spike > apache-commons-jcs cquad jjelen > apanov-edrip-fonts frixxon nim > apbs rathann timfenn > arduino giallu patches thozza > artharoshansingh > astrometry lupinix > astrometry-tycho2lupinix > audacity dtimms gemi moezroy > avalon-framework jerboaa jjelen mizdebsk > avr-gdb giallu tnorth trondd > blessdrago01 > bmakelbazan > boothjpokorny > bygfoot hguemar > cassandra-java-driver acaringi hhorak jjanco > castor arobinso lef > catimg ignatenkobrain > cdpr stahnma > ckermit brouhaha > classloader-leak-test-framework acaringi praiskup > clipstimn > cmyktool duffy > cog bunnyapocalypse > corianderdajt timn > cp2k deji rathann tomspur > dahdi-tools bruno itamarjp jsmith > dateshiftfab > dibbler ihrachyshka > dieharderjhladky > doccojamielinux patches > drbd mhayden > dsi dbrasher > echolinuxlucilanga > echoping ixs > eclipse-avr bubeck > eclipse-egit-github mbooth > eclipse-launchbarmbooth sopotc > eclipse-m2e-core galileo mbooth mizdebsk > eclipse-mylynarobinso jjohnstn kdaniel mbooth rgrunber > eclipse-photran akurtakov orion > eclipse-ptp jjohnstn kdaniel orion > eclipse-pydevjjohnstn mbooth > eclipse-remote mbooth > eclipse-subclipsekdaniel mbooth > eclipse-testng mbooth > eclipse-tm-terminal mbooth > eclipse-webtools galileo mbooth > elpa rathann > emacs-mmmamdunn > etcd avesh cypret eparis gscrivano jchaloup lsm5 strigazi > walters > fcoe-utils cleech > fedora-jam-kde-theme eeickmeyer jvlomax > flatbuffers avsej > foma vpv > forbidden-apis jvanek zzambers > freeDiameter filiperosset > fts andreamanzi simonm > gabedit itamarjp rathann > game-music-emu kvolny moezroy > gauche gemi salimma > gcolor2 cwickert > gdigimchehab > geronimo-jcdi-1.0-api jjelen lef > ggz-gtk-client bruno pwalter > git-cola moceap ohaessler > gluegen2 jamesturner246 > gmpc adrian > gnomad2 snirkel > gnomint verdurin > goaccess cicku echevemaster > golang-github-influxdata-flux eclipseo > golang-github-influxdata-influxdb eclipseo > golang-github-nats-io-streaming eclipseo > golang-github-opencontainers-runc eclipseo > golang-k8s-kubernetes eclipseo > golang-k8s-legacy-cloud-providers eclipseo > golang-vitesseclipseo > gplugin ignatenkobrain > gpsdrive nphilipp > graphite2moceap vanoudt > grsync cwickert &g
Re: Fedora 32 FTBFS packages to be orphaned in 1 week
I would like to take arduino. I can make buildable again 1.8.5 version and may be update it to latest. My FAS name: vascom -- Best regards, Vasiliy Glazov ___ 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
Re: Specify debug build in qtmake?
So this spec not follow Fedora's packaging guidlines and need to be fixed according them. вт, 31 мар. 2020 г., 15:57 Richard Shaw : > On Tue, Mar 31, 2020 at 7:34 AM Vascom wrote: > >> Why you not use macro %qmake_qt5? >> It contain all flags. >> > > Good question. I inherited this package and hadn't dug into it much since > it was building until today. > > Thanks, > Richard > ___ > 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 > ___ 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
Re: Specify debug build in qtmake?
Why you not use macro %qmake_qt5?
It contain all flags.
вт, 31 мар. 2020 г., 15:25 Richard Shaw :
> Has something changed with Qt 5.14? I'm trying to update klog to new
> version but debuginfo is not being generated.
>
> Looking at the build log it's definitely missing "-g" during building but
> a debug build is requested:
>
> qmake-qt5 "PREFIX=%{buildroot}%{_prefix}" "CONFIG+=debug c++17" KLog.pro
>
> Looking at KLog.pro I see:
>
> CONFIG += release
>
> and
>
> #DEFINES *= QT_NO_DEBUG_OUTPUT
>
> Which I assume is ok. I should be overriding the first line and the second
> is commented out.
>
> Tips?
>
> Thanks,
> Richard
> ___
> 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
>
___
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
Re: Updating libusbx
Thanks. чт, 26 мар. 2020 г., 15:50 Peter Robinson : > On Thu, Mar 26, 2020 at 6:28 AM Vascom wrote: > > > > Why libusbx still not updated to 1.0.23? > > Version 1.0.22 was released two years ago. > > Maybe it slipped through the cracks, maybe there wasn't anything of > note that was thought to affect Fedora directly. The maintainers there > are normally pretty good. > > I've pushed a 1.0.23 build to rawhide. > ___ > 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 > ___ 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
Re: Updating libusbx
BZ ticket already submitted and I wrote there. I will try email to maintainers directly now. чт, 26 мар. 2020 г., 15:22 Richard Shaw : > On Thu, Mar 26, 2020 at 1:28 AM Vascom wrote: > >> Why libusbx still not updated to 1.0.23? >> Version 1.0.22 was released two years ago. >> > > It would probably be better to try emailing the maintainer(s) as they may > not see you message to devel, or submit a BZ ticket. > > libusbx-maintain...@fedoraproject.org > > Thanks, > Richard > ___ > 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 > ___ 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
Updating libusbx
Why libusbx still not updated to 1.0.23? Version 1.0.22 was released two years ago. ___ 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
Re: bibutils soname bump to 6.9
Updated to 6.10. Can I update it in F32 now? пн, 23 мар. 2020 г. в 21:56, Vascom : > > I go to update bibutils in rawhide. It update lib to version 6.9. > > Nothing require it as BR and only kbibtex as Requires. > So I will not rebuild any 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
bibutils soname bump to 6.9
I go to update bibutils in rawhide. It update lib to version 6.9. Nothing require it as BR and only kbibtex as Requires. So I will not rebuild any 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
Re: co-maintainer wanted for fuse-sshfs in EPEL8
You can add me as comaintainer. FAS name: vascom вс, 8 мар. 2020 г., 19:32 Dusty Mabe : > The current maintainer of fuse-sshfs is looking for a co-maintainer for it > in epel8. It's currently not in EPEL 8 so if you go from RHEL or CentOS > 7->8 > you'll lose it. I have users of vagrant-sshfs who would like to have it > there. > > https://bugzilla.redhat.com/show_bug.cgi?id=1758884#c4 > > Anybody interested? > > Dusty > ___ > 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 > ___ 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
Re: Orphaned packages looking for new maintainers
Please help me understand why I am marked? vascom: perl-Compress-LZF I can't find any package requires perl-Compress-LZF. This always empty: dnf repoquery --whatrequires perl-Compress-LZF --alldeps dnf repoquery --whatrequires "perl(Compress::LZF)" --alldeps вт, 18 февр. 2020 г. в 02:50, Jerry James : > > On Mon, Feb 17, 2020 at 8:27 AM Miro Hrončok wrote: > [snip] > > pcpa: apache-commons-jexl, jmol, perl-Math-Int64, naga, jspecview > [snip] > > sagitter: apache-commons-jexl > > Hey pcpa and sagitter, don't worry about apache-commons-jexl. I've > just been working on updates for jacop and mp that fix multiple issues > I've stumbled over with those two packages. The updates will involve > dropping the dependency on apache-commons-jexl. They will also fix > the jacop integration into mp, by the way, which doesn't actually work > with the current mp package, as well as restore gecode integration > into mp. > > The jmol orphaning is a bit more concerning. I'm just about to get > sagemath building again after it has been broken for a couple of > months (just waiting for a fix for > https://bugzilla.redhat.com/show_bug.cgi?id=1789099 at this point), > and if jmol disappears from Fedora then it will be broken again. > Argh. Paulo, since you are the maintainer of record for sagemath, do > you want to pick up jmol and its dependencies? > > If not, is there a charitable soul in the audience who would take > jmol? If somebody out there is not a packager, but would like to > maintain jmol, please contact me. I'll help you get started. > > Regards, > -- > Jerry James > http://www.jamezone.org/ > ___ > 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 ___ 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
Re: Fedora pagure confusion wrt EPEL
No way. You can add comaintainer for EPEL builds of your packages. чт, 30 янв. 2020 г. в 12:13, Michael Schwendt : > > I don't do EPEL packaging. I never signed up as an "owner" of EPEL packages. > I don't want to be the new default owner of EPEL bugzilla tickets. > Where may I be able to stop this mess? > > ___ > 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 ___ 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
Re: Fedora 32 Mass Rebuild
Are s390x builders ready for Mass Rebuild? I see many fail builds only on s390x without logs. вт, 28 янв. 2020 г. в 11:39, Mohan Boddu : > > We are starting the mass rebuild now. > > Thanks. > > On Mon, Jan 27, 2020 at 5:38 PM Jeff Law wrote: > > > > On Mon, 2020-01-27 at 21:23 +0100, Fabio Valentini wrote: > > > On Mon, Jan 27, 2020 at 4:46 PM Jeff Law wrote: > > > > On Mon, 2020-01-27 at 16:34 +0100, Jakub Jelinek wrote: > > > > > On Mon, Jan 27, 2020 at 10:25:50AM -0500, Mohan Boddu wrote: > > > > > > Hi all, > > > > > > > > > > > > Per the Fedora 32 schedule[1] we will be starting a mass rebuild for > > > > > > Fedora 32 today. We are doing a mass rebuild for Fedora 32 for all > > > > > > the > > > > > > changes: > > > > > > > > > > > > https://fedoraproject.org/wiki/Changes/GLIBC231 > > > > > > https://fedoraproject.org/wiki/Releases/32/ChangeSet#Binutils_2.33 > > > > > > https://fedoraproject.org/wiki/Changes/FontLangProvidesToLangpacks > > > > > > https://fedoraproject.org/wiki/Changes/golang1.14 > > > > > > https://fedoraproject.org/wiki/Changes/GCC10 > > > > > > https://fedoraproject.org/wiki/Changes/Free_Pascal_Compiler_3.2.0 > > > > > > > > > > > > we will start the mass rebuild on 2020-01-27 > > > > > > > > > > I thought the mass rebuild should be also for > > > > > https://fedoraproject.org/wiki/LTOByDefault > > > > > but the required changes AFAIK haven't landed into redhat-rpm-config > > > > > yet. > > > > > > > > > > CCing Jeff on the current state. > > > > > > (snip) > > > > > > > After finally starting looking at the LTO vs GDB issues last week, I > > > > think we should defer LTO until F33. There's just too many GDB > > > > failures when used with LTO that aren't understood yet. > > > > > > Since the mass rebuild starts today (or has already started), you're > > > cutting it pretty close there ... > > > > > > So you'll either need to postpone to F33 or request a second mass > > > rebuild - soon. > > > > > > Can you comment on the FESCo ticket with the current status? Just to > > > keep us in the loop > > Umm, Ben and I were already discussing the situation this morning. I > > believe the page and fesco ticket both have current state (deferring to > > F33). > > > > jeff > > > > > ___ > > 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 > ___ > 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 ___ 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
New packager: girst
Welcome new Fedora's packager - girst. He is already rpmfusion packager and I am sure will be good in Fedora. ___ 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
Re: Review swap
I can review it without swap. пт, 6 дек. 2019 г. в 03:03, Jerry James : > > One of my upstreams picked up a new documentation dependency. Who would like > to swap reviews? This one should be quick and easy. > > python-sphinx-copybutton: https://bugzilla.redhat.com/show_bug.cgi?id=1780426 > > Thank you, > -- > Jerry James > http://www.jamezone.org/ > ___ > 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 ___ 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
Re: Paul Grosu
pgrosu - is your FAS name? Are you in packager group? ср, 20 нояб. 2019 г. в 10:20, Paul Grosu : > > Hi Vascom, > > Thank you for the quick reply. I already added the SSH public key, but when > I try to ssh with my private key and enter the username pgrosu at the > (login:) it says "No supported authentication methods available". Does it > mean I should wait a day for it to go through, or should I contact the admin? > > Thanks, > Paul > > On Wed, Nov 20, 2019 at 2:04 AM Vascom wrote: >> >> You need to add your public ssh key at FAS page >> https://admin.fedoraproject.org/accounts >> And login via ssh. >> >> Read all information on >> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers >> >> ср, 20 нояб. 2019 г. в 09:54, Paul Grosu : >> > >> > Hello Fedora Development Community, >> > >> > I work at Northeastern University as a researcher in the Gene Cooperman >> > Lab, and will be supporting the DMTCP package >> > (https://apps.fedoraproject.org/packages/dmtcp) and DMTCP-devel >> > (https://apps.fedoraproject.org/packages/dmtcp-devel). We are about to >> > release a new version of the package but don't have a aarch-64 machine, >> > and was wondering how to go about having access to one of the test >> > machines listed on the following weblink: >> > https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers >> > >> > Please let me know how to proceed regarding getting access to a test >> > machine. >> > >> > Thank you, >> > Paul >> > ___ >> > 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 >> ___ >> 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 > > ___ > 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 ___ 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
Re: Paul Grosu
You need to add your public ssh key at FAS page https://admin.fedoraproject.org/accounts And login via ssh. Read all information on https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers ср, 20 нояб. 2019 г. в 09:54, Paul Grosu : > > Hello Fedora Development Community, > > I work at Northeastern University as a researcher in the Gene Cooperman Lab, > and will be supporting the DMTCP package > (https://apps.fedoraproject.org/packages/dmtcp) and DMTCP-devel > (https://apps.fedoraproject.org/packages/dmtcp-devel). We are about to > release a new version of the package but don't have a aarch-64 machine, and > was wondering how to go about having access to one of the test machines > listed on the following weblink: > https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers > > Please let me know how to proceed regarding getting access to a test machine. > > Thank you, > Paul > ___ > 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 ___ 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
Re: rpmbuild signature check failure
It is about signatures, not checksums. вс, 10 нояб. 2019 г., 9:47 Baxi : > I followed fedora source file verification and there was nothing about SHA > checksum verification. Also it is 2048 bits long so I doubt it is SHA256 > checksum file. > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_source_file_verification > > On Nov 10, 2019 10:05, Vascom wrote: > > May be you need use sha256sum instead gpg? > > вс, 10 нояб. 2019 г., 9:17 Baxi : > > Hi. I am trying to package a program. The upstream provided sha256sum.asc > file. Verifying tarball with that signature says, Can't check signature: No > public key. I found his public key in key directory by searching his email > and added that key. Now gpg says Bad signature from that person. Also > upstream didn't provide gpg keyring in his project. What should I do? > ___ > 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 > > > ___ > 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 > ___ 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
Re: rpmbuild signature check failure
May be you need use sha256sum instead gpg? вс, 10 нояб. 2019 г., 9:17 Baxi : > Hi. I am trying to package a program. The upstream provided sha256sum.asc > file. Verifying tarball with that signature says, Can't check signature: No > public key. I found his public key in key directory by searching his email > and added that key. Now gpg says Bad signature from that person. Also > upstream didn't provide gpg keyring in his project. What should I do? > ___ > 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 > ___ 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
bibutils change soversion anounce
Bibutils 6.8 change soversion to 6.8. I am update it for rawhide, F31, F30. As I see no one package not require it so I will no rebuild anything else. ___ 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
Re: List of Python 2 packages to be removed mid-November
klavaro fixed in rawhide. ср, 30 окт. 2019 г. в 08:53, Luya Tshimbalanga : > > On 2019-10-29 8:24 a.m., Miro Hrončok wrote: > > > > luya > > scribus-generator > > (→ scribus → PY2) > > > Already switched to python3 : > > https://apps.fedoraproject.org/packages/scribus-generator/sources/spec/ > > -- > Luya Tshimbalanga > Fedora Design Team > Fedora Design Suite maintainer > ___ > 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 ___ 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
ABI change announce svt-vp9
ABI changed in svt-vp9 0.1.1 release. All changes https://taskotron.fedoraproject.org/artifacts/all/6720382c-ebf1-11e9-904f-52540077ca13/tests.yml/svt-vp9-0.1.1-1.fc32.log ___ 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
Re: specfile dependecy to pip package
python3-sphinx not removed.
Look at
https://koji.fedoraproject.org/koji/packageinfo?packageID=6297
чт, 19 сент. 2019 г. в 16:03, Marek Tamaskovic :
>
> Hi,
> I'm maintainer of libcbor package and in fedora 30 has been removed
> python3-sphinx package which is required to build documentation for libcbor.
> I can changa the dependency to python2-sphinx but thats not what I really
> want to do. Another option is to install sphinx via pip3. However in build
> phase it will show an error which says:
>
> sphinx-build -b man -d build/doctrees source build/man
> Traceback (most recent call last):
> File "/usr/local/bin/sphinx-build", line 6, in
> from sphinx.cmd.build import main
> ModuleNotFoundError: No module named 'sphinx'
> make: *** [Makefile:131: man] Error 1
>
> (it needs breathe package and that is installed as well using pip3)
>
> Now I have two questions:
>
> 1. How can I write to specfile that I need a pip package?
> I tried:
>
> BuildRequires: %{py3_dist Sphinx} >= 2.2.0
>
> And as well:
>
> BuildRequires: %{py3_dist sphinx} >= 2.2.0
>
> Both of those will show an dependency error even when I install sphinx and
> breathe using pip3:
>
> python3dist(sphinx) >= 2.2.0 is needed by libcbor-0.5.0-5.fc30.x86_64
>
>
> 2. How to fix that error from sphinx-build?
> I tried to install even sphinx-multibuild (using pip) but did not succeed.
> It is suspicious that sphinx package need sphinx and it can not find it.
>
> Regards,
> Marek Tamaskovic
> ___
> 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
___
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
Re: Intent to unretire ladspa-swh-plugins
Can you also unretire and build lv2-mdala-plugins? It is needed for pulseeffects but lv2-mdala-plugins use python2 in build script and I do not have knowledge how to rewrite it to python3. I can only add python2 to BR and correct shebang but it seems wrong because python2 will be erased soon. -- Best regards, Vasiliy Glazov чт, 12 сент. 2019 г. в 18:19, stan via devel : > > On Thu, 12 Sep 2019 13:32:45 +0100 > "Ryan Walklin" wrote: > > > Thanks for the clarification, I hadn't realised the LV2 versions of > > the plugins weren't working. I've managed to get the F29 version as > > you suggest, and patched (attached) the scripts to force Python 2 so > > I can run the GUI from the launcher. Upstream seems to have updated > > the GUI to Python 3, but as mentioned there are some bugs with their > > config parser currently. > > Thanks for the patch. I had caught the generic python reference in the > python file, but not the one in the gtk file. Now, I can have normal > operation. > ___ > 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 ___ 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
Re: Fedora package in EPEL
fedpkg request-branch --repo fctxpd epel7 вт, 17 сент. 2019 г. в 09:26, Muneendra Kumar M via devel : > > Hi All, > > > > I want to have the fctxpd fedora package into the EPEL. > > Iam the maintainer of this fctxpd package in fedora. > > Can anyone help me how can I have the same package in EPEL also. > > > > > > Regards, > > Muneendra. > > ___ > 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 ___ 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
Re: Intent to unretire ladspa-swh-plugins
It is not dependency for pulseeffects. пн, 9 сент. 2019 г. в 20:10, Guido Aulisi : > > I'd like to unretire ladspa-swh-plugins in rahwide, f31 and f30, > because it is a dependency of some packages I maintain: > > ams > jamin > > It's a dependency of pulseeffects too. > > I will file a review request ASAP, I have already made a scratch build > in rawhide: > https://koji.fedoraproject.org/koji/taskinfo?taskID=37562823 > > FAS account: tartina > > Ciao > Guido > ___ > 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 ___ 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
Unretire linuxconsoletools package
Please approve review of linuxconsoletools package https://bugzilla.redhat.com/show_bug.cgi?id=1740634 It was retired due to FTBFS but needed for gpm, fpc, lazarus to build pascal programs. Situation same as with gettext. -- Best regards, Vasiliy Glazov ___ 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
Re: Review swap - zeal
I can review it without swap. вт, 28 мая 2019 г. в 13:55, Lumir Balhar : > > Hello. > > I'd like to claim ownership of retired package zeal, which is currently > in weird state not available in F30. > > Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1701666 > Review request: https://bugzilla.redhat.com/show_bug.cgi?id=1711898 > > Will take a review in exchange for something of similar complexity. > > Lumír > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: update-desktop-database in %post snippet
No. It must be removed from %post. пт, 26 апр. 2019 г. в 12:30, Petr Mensik : > > Hi! > > Is it still valid request to add update-desktop-database into %post, > like mentioned by fedora-review tool [1]? Almost at the end of the > comment. I were not able to find any information about it in Package > Guidelines. Should that hint be removed from fedora-review or should be > documentation updated? > > Are my eyes too tired to find correct place? > > 1. https://bugzilla.redhat.com/show_bug.cgi?id=1658153#c85 > > Regards, > Petr > -- > Petr Menšík > Software Engineer > Red Hat, http://www.redhat.com/ > email: pemen...@redhat.com PGP: 65C6C973 > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaning kdesvn
I am already updated spec and build version 2.0.95 for rawhide in mock. пт, 19 апр. 2019 г. в 09:02, Vascom : > > I can take it. > FAS name: vascom > > пт, 19 апр. 2019 г. в 05:37, Orion Poplawski : > > > > I'm going to orphan kdesvn as I no longer use it. It needs updating: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1519347 > > > > Let me know if you are interested in taking it over. > > > > -- > > Orion Poplawski > > Manager of NWRA Technical Systems 720-772-5637 > > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > > 3380 Mitchell Lane or...@nwra.com > > Boulder, CO 80301 https://www.nwra.com/ > > > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaning kdesvn
I can take it. FAS name: vascom пт, 19 апр. 2019 г. в 05:37, Orion Poplawski : > > I'm going to orphan kdesvn as I no longer use it. It needs updating: > > https://bugzilla.redhat.com/show_bug.cgi?id=1519347 > > Let me know if you are interested in taking it over. > > -- > Orion Poplawski > Manager of NWRA Technical Systems 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 https://www.nwra.com/ > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Chromium C++ help needed
Look at chromium-vaapi build in rpmfusion.
пн, 11 мар. 2019 г., 20:17 Tom Callaway :
> Hi folks,
>
> I spent some time this weekend trying to get Chromium 72 building on
> Fedora, but I kept running into a C++ issue that I was not able to resolve.
> This happened with gcc-9.0.1-0.8.fc30.x86_64 and gcc-8.3.1-2.fc29.x86_64.
>
> Here's a sample of the error (it happens in a few places), from Fedora 30:
>
> In file included from
> ../../base/trace_event/trace_event_system_stats_monitor.h:15,
> from ../../base/trace_event/trace_event.h:26,
> from ../../base/threading/scoped_blocking_call.cc:11:
> ../../base/trace_event/trace_log.h: In constructor
> 'base::ScopedBlockingCall::ScopedBlockingCall(base::BlockingType)':
> ../../base/threading/scoped_blocking_call.cc:88:5: in 'constexpr'
> expansion of
> 'base::trace_event::TraceLog::GetBuiltinCategoryEnabled(((const
> char*)"base"))'
> ../../base/trace_event/trace_log.h:215:25: error: '((&
> base::trace_event::CategoryRegistry::categories_[7]) != 0)' is not a
> constant expression
> 215 | if (builtin_category)
> | ^
>
> Now, chromium isn't the easiest code base to work with, but what seems to
> be happening is that this code calls one of the TRACE_EVENT macros, like
> this from base/threading/scoped_blocking_call.cc:
>
> TRACE_EVENT_BEGIN1("base", "ScopedBlockingCall", "blocking_type",
> static_cast(blocking_type));
>
> Those macros are defined in base/trace_event/common/trace_event_common.h:
>
> #define TRACE_EVENT_BEGIN1(category_group, name, arg1_name, arg1_val) \
> INTERNAL_TRACE_EVENT_ADD(TRACE_EVENT_PHASE_BEGIN, category_group, name, \
>TRACE_EVENT_FLAG_NONE, arg1_name, arg1_val)
>
> INTERNAL_TRACE_EVENT_ADD() is defined in base/trace_event/trace_event.h:
>
> / Implementation detail: internal macro to create static category and add
> // event if the category is enabled.
> #define INTERNAL_TRACE_EVENT_ADD(phase, category_group, name, flags, ...)
> \
> do {
> \
> INTERNAL_TRACE_EVENT_GET_CATEGORY_INFO(category_group);
> \
> if (INTERNAL_TRACE_EVENT_CATEGORY_GROUP_ENABLED()) {
> \
> trace_event_internal::AddTraceEvent(
> \
> phase, INTERNAL_TRACE_EVENT_UID(category_group_enabled), name,
> \
> trace_event_internal::kGlobalScope, trace_event_internal::kNoId,
> \
> flags, trace_event_internal::kNoId, ##__VA_ARGS__);
> \
> }
> \
> } while (0)
>
> INTERNAL_TRACE_EVENT_GET_CATEGORY_INFO is also defined in
> base/trace_event/trace_event.h:
>
> #define INTERNAL_TRACE_EVENT_GET_CATEGORY_INFO(category_group)
> \
> static_assert(
> \
>
> base::trace_event::BuiltinCategories::IsAllowedCategory(category_group), \
> "Unknown tracing category is used. Please register your "
> \
> "category in base/trace_event/builtin_categories.h");
> \
> constexpr const unsigned char* INTERNAL_TRACE_EVENT_UID(
> \
> k_category_group_enabled) =
> \
>
> base::trace_event::TraceLog::GetBuiltinCategoryEnabled(category_group); \
> const unsigned char* INTERNAL_TRACE_EVENT_UID(category_group_enabled);
> \
> INTERNAL_TRACE_EVENT_GET_CATEGORY_INFO_MAYBE_AT_COMPILE_TIME(
> \
> category_group, INTERNAL_TRACE_EVENT_UID(k_category_group_enabled),
> \
> INTERNAL_TRACE_EVENT_UID(category_group_enabled));
>
> Finally, inside here, it
> calls base::trace_event::TraceLog::GetBuiltinCategoryEnabled(), which is
> defined in base/trace_event/trace_log.h:
>
> // Called by TRACE_EVENT* macros, don't call this directly.
> // The name parameter is a category group for example:
> // TRACE_EVENT0("renderer,webkit", "WebViewImpl::HandleInputEvent")
> static const unsigned char* GetCategoryGroupEnabled(const char* name);
> static const char* GetCategoryGroupName(
> const unsigned char* category_group_enabled);
> static constexpr const unsigned char* GetBuiltinCategoryEnabled(
> const char* name) {
> TraceCategory* builtin_category =
> CategoryRegistry::GetBuiltinCategoryByName(name);
> if (builtin_category)
> return builtin_category->state_ptr();
> return nullptr;
> }
>
> Okay, so what seems like is happening here, is that the calls like this:
>
> TRACE_EVENT_BEGIN1("base", "ScopedBlockingCall", "blocking_type",
> static_cast(blocking_type));
>
> Are passing "base" (that first var) all the way into
> GetCategoryGroupEnabled, which is finding it via GetBuiltinCategoryByName()
> in base/trace_event/category_registry.h, checking against the list in
> INTERNAL_TRACE_LIST_BUILTIN_CATEGORIES(X)
> from base/trace_event/builtin_categories.h, finding it, then returning this
> as builtin_category:
>
> (& base::trace_event::CategoryRegistry::categories_[7])
>
> When if(builtin_category) is run (trying to check to see if we got a
> buillt-in category or a nullptr, I think), thats when GCC says:
>
> error: '((&
Re: Self introduction: Barry Scott
Hi and welcome. I am sorry but you can't became fedora maintainer with already existing package. You should suggest new package for that. https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Also you can send Pull Requests or talk with python-pycxx maintainer directly. пн, 4 мар. 2019 г. в 14:40, Barry Scott : > > I have become the new maintainer for the pysvn package on Fedora. > > I am the upstream developer for a number of projects including: > * pysvn - https://pysvn.sourceforge.io/ > * pycxx - http://cxx.sourceforge.net/ > * Barry's Emacs - http://barrys-emacs.org/ > * SCM workbench - http://scm-workbench.barrys-emacs.org/ > > These days I tend to develop in python and C++ using PyQt for GUI needs. > The above projects work on Unix, macOS and Windows. > > I have been using Fedora since FC4 and maybe before, > too long ago to remember. > > I would also like to volunteer to be a co-maintainer of > python-pycxx. > > My first task will be to update pysvn to its 1.9.9 release > but that requires pycxx to be updated to its 7.1.2 release > to pick up a needed fix. > > I have a review up for the changes to python-pycxx at > https://bugzilla.redhat.com/show_bug.cgi?id=1685102 > > Barry > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Qt 5.12 coming to rawhide
Will it be in F29? пт, 1 мар. 2019 г. в 17:05, Rex Dieter : > > Continuing work in master branch (aka fc31), pending > > fc30 work will continue when > https://pagure.io/releng/issue/7966 > is processed for a f30-kde koji target. (Hopefully with enough time prior to > beta freeze) > > -- Rex > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Retire kchildlock package
Hi all. I am plan to retire package kchildlock from Fedora. It is KDE4 application long time unsupported and FTBFS on rawhide and F30. If no one need it I will retire package in one week. https://src.fedoraproject.org/rpms/kchildlock https://store.kde.org/p/1127875/ https://sourceforge.net/projects/kchildlock/ -- Best regards, Vasiliy Glazov ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 30 Mass Rebuild
No. If count as many times as many maintainers it has it will be about 3300 fails. вт, 5 февр. 2019 г. в 14:32, Vít Ondruch : > > > Dne 04. 02. 19 v 21:48 Mohan Boddu napsal(a): > > Hi all, > > Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30 > on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes listed > in: > > https://pagure.io/releng/issue/8086 > > Mass rebuild was done in a side tag (f30-rebuild) and are now getting moved > over to f30. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f30-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f30-need-rebuild.html > > 19097 builds have been tagged into f30, there s currently 1787 failed > > > I might be wrong but think the number of failed packages is incorrect. It > seems that every package is counted as many times as many maintainers it has. > > > Vít > > > builds that need to be addressed by the package maintainers. > > FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedoraproject.org/wiki/Releases/30/Schedule > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ > > ___ > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: [HEADS-UP] gcc(-c++) builds are broken in Rawhide buildroot
Why package gcc has version 9.0.0 but in changelog - 9.0.1?
пн, 21 янв. 2019 г. в 14:48, Björn 'besser82' Esser
:
>
> The update to GCC 9 broke the Rawhide buildroot for any package that
> (Build)Requires: gcc{,-c++} and/or libtool.
>
> I've already successfully rebuilt annobin and the rebuilt of libtool is
> currently running. [1] After the libtool build has finished, everything
> should be working again.
>
> I'll take care of the all the builds, that have failed because of this.
>
> Björn
>
>
> [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=32168827
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14
It must produce the same results as real hw. Or mock parameter --forcearch must be removed. пн, 14 янв. 2019 г. в 12:02, Dan Horák : > > On Mon, 14 Jan 2019 10:48:59 +0300 > Vascom wrote: > > > How about switch build rpms for exotic and slow arches (arm, s390...) > > arm is slow, but not exotic > s390 is exotic, but not slow > > > from hardware to cross-compile on x86_64? > > mock can do it via qemu-user-static > > emulation has functional deficiencies, so it won't produce the same > results as real hw > > > Dan > > > > > пн, 14 янв. 2019 г. в 10:37, Dan Horák : > > > > > > On Sun, 13 Jan 2019 20:52:30 -0500 > > > Neal Gompa wrote: > > > > > > > On Sun, Jan 13, 2019 at 8:50 PM Neal Gompa > > > > wrote: > > > > > > > > > > * Buildbot (Python 3) > > > > > * Jenkins (Java) > > > > > * Vespene (Python 3) > > > > > * GoCD (Java + Ruby) > > > > > * Zuul (Python) > > > > > > > > > > Of the four listed above, only the first two are packaged in > > > > > Fedora. Buildbot is up-to-date in Fedora, but Jenkins lags > > > > > behind considerably and needs love. > > > > > > > > > > > > > Also, regrettably, I can't count. :) > > > > > > > > Yes, there's actually five options there. Zuul is actually a > > > > pretty bad option because it requires Ansible playbooks, which is > > > > overkill for 99% of projects. > > > > > > jenkins and buildbot are already being used by various upstream on > > > our s390x infra. They work fine and more upstream are welcome to > > > come to us. I was thinking rather about lack of things like Travis, > > > where the upstreams don't have to care about the CI infrastructure > > > (aka CI as a service). > > > > > > > > > Dan > > > ___ > > > devel mailing list -- devel@lists.fedoraproject.org > > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > > List Guidelines: > > > https://fedoraproject.org/wiki/Mailing_list_guidelines List > > > Archives: > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14
How about switch build rpms for exotic and slow arches (arm, s390...) from hardware to cross-compile on x86_64? mock can do it via qemu-user-static пн, 14 янв. 2019 г. в 10:37, Dan Horák : > > On Sun, 13 Jan 2019 20:52:30 -0500 > Neal Gompa wrote: > > > On Sun, Jan 13, 2019 at 8:50 PM Neal Gompa wrote: > > > > > > * Buildbot (Python 3) > > > * Jenkins (Java) > > > * Vespene (Python 3) > > > * GoCD (Java + Ruby) > > > * Zuul (Python) > > > > > > Of the four listed above, only the first two are packaged in Fedora. > > > Buildbot is up-to-date in Fedora, but Jenkins lags behind > > > considerably and needs love. > > > > > > > Also, regrettably, I can't count. :) > > > > Yes, there's actually five options there. Zuul is actually a pretty > > bad option because it requires Ansible playbooks, which is overkill > > for 99% of projects. > > jenkins and buildbot are already being used by various upstream on our > s390x infra. They work fine and more upstream are welcome to come to > us. I was thinking rather about lack of things like Travis, where the > upstreams don't have to care about the CI infrastructure (aka CI as a > service). > > > Dan > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Kernel 4.20 rebase plans
Do you mean STIBP? It is alreasy disabled by default in 4.19 and 4.20. ср, 9 янв. 2019 г. в 01:55, Joseph D. Wagner : > > IIRC, there is major performance degradation (anti-Spectre) in 4.20 that will > be turned off by default 4.21. > > Will it be turned off by default in the 4.20 rebase? > > Joseph D. Wagner > > On 2019-01-08 14:31, Justin Forbes wrote: > > The 4.20 kernel was released just before the end of the year, but the > first stable update should be dropping in the next day or two. We > have a 4.20 test day scheduled for Tuesday, January 15th. Depending > on the results of that test day, Fedora 29 will be rebased very > shortly afterwards, followed by F28 approximately a week later. Of > course the results of the test day could end up changing this, but it > is the current plan. > > Thanks, > Justin > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Broken el7 ppc64 koji
Thanks. пт, 14 дек. 2018 г., 17:30 Stephen John Smoogen smo...@gmail.com: > On Fri, 14 Dec 2018 at 08:53, Vascom wrote: > > > > But it was here in previous build few months ago. > > > https://kojipkgs.fedoraproject.org//packages/mediainfo/18.08.1/1.el7/data/logs/ppc64/root.log > > OK.. yeah my fault for not looking closer than the koji package sets > currently available. So there was a newer version in EPEL when you > built this months ago. > > DEBUG util.py:439: libmspack ppc64 > 0.7-0.1.alpha.el7 build 75 k > > and then RHEL added it to all architectures other than ppc64 as > libmspack-0.5-0.6.alpha.el7.x86_64.rpm > > since EPEL has a rule to not over-ride RHEL packages since that causes > user problems.. it got pulled out of epel. However that means you > can't build this for ppc64 anymore. The two options would be to > contact sharkcz and have him see if he wants to rebuild that old > version for ppc64 or exclusivearch and exclude ppc64. > > > > > пт, 14 дек. 2018 г. в 16:49, Stephen John Smoogen : > > > > > > On Fri, 14 Dec 2018 at 01:47, Vascom wrote: > > > > > > > > Hi. > > > > > > > > Whats wrong with ppc64 in koji? > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=31454970 > > > > > https://kojipkgs.fedoraproject.org//work/tasks/4970/31454970/root.log > > > > > > > > DEBUG util.py:439: Error: Package: wxGTK3-3.0.2-15.el7.ppc64 (build) > > > > DEBUG util.py:439: Requires: libmspack.so.0()(64bit) > > > > > > > > Other arches build normally.\ > > > > > > ppc64 does not have a lot of packages which are in other > > > architectures. The libmspack is one of those packages. > > > > > > > > > > > > > ___ > > > > devel mailing list -- devel@lists.fedoraproject.org > > > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > > > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > > > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > > > > > > > > > > -- > > > Stephen J Smoogen. > > > ___ > > > devel mailing list -- devel@lists.fedoraproject.org > > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > > -- > Stephen J Smoogen. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
