Re: Update rust-palette 0.6.0
On Friday, December 10, 2021 2:35:45 AM EST Rémi Lauzier wrote: > Hi everyone. I will update rust-palette and rust-palette_derive to version > 0.6.0 in a sidetag. If there is no objection i will push it in a week. The > only dependency that somebody else will have to update is > system76-keyboard-configurator. > > Here the sidetag. > f36-build-side-48706 > f35-build-side-48708 > > Sent with ProtonMail Secure Email. Unless I'm mistaken, this doesn't affect the runtime functionality of system76-keyboard-configurator. This is a build-time only dependency. I'm happy to rebuild it once this sidetag is pushed, but there are so many build dependencies of system76-keyboard-configurator, we couldn't possible rebuild it every time any dependency updates. That would be a lot of updates for very little benefit. Is this fixing a critical bug in rust-palette, or is it introducing a breaking change in rust-palette? ~link ___ 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-backgrounds ready for review
On Thu, Aug 26 2021 at 03:12:24 PM +, Zbigniew Jędrzejewski-Szmek wrote: True. But those subpackages could just be built from one source package: fedora-backgrounds/f34 => builds all subpackages in the range 21..34 fedora-backgrounds/f35 => builds all subpackages in the range 21..35 Assuming this range notation is a half-open interval, yes, I like this idea. Then each subsequent release could take the wallpapers from its predecessor and create a new subpackage named with the previous version. Would that get unwieldy as the spec file grows? Is there an opportunity for macros to make this more sustainable? ___ 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-backgrounds ready for review
Could those be collected into an archive somewhere? Like fedora-backgrounds-extras or something similar? This would be a significant change to the way backgrounds are packaged. On Thu, Aug 26 2021 at 02:45:18 PM +0200, Miro Hrončok wrote: On 26. 08. 21 14:40, Link Dupont wrote: Wouldn't a source package named 'fedora-backgrounds' work? Each branch in dist-git would allow for new wallpapers each release. An RPM using the Fedora version as its version would result in an NVR that clearly identifies the wallpapers: * fedora-backgrounds/f34 => fedora-backgrounds-34-1.fc34 * fedora-backgrounds/f35 => fedora-backgrounds-35-1.fc35 * fedora-backgrounds/f35 => fedora-backgrounds-35-2.fc35 But I must be missing something; this seems like its way too simple a solution. Nowadays, you can install e.g. f23-backgrounds on Fedora 34. If we do it like you said, there would always be just one option. $ repoquery --repo=rawhide -a | egrep -- 'f[[:digit:]]+-backgrounds' f21-backgrounds-0:21.1.0-13.fc35.noarch f21-backgrounds-base-0:21.1.0-13.fc35.noarch f21-backgrounds-extras-base-0:21.1.0-13.fc35.noarch f21-backgrounds-extras-gnome-0:21.1.0-13.fc35.noarch f21-backgrounds-extras-kde-0:21.1.0-13.fc35.noarch f21-backgrounds-extras-mate-0:21.1.0-13.fc35.noarch f21-backgrounds-extras-xfce-0:21.1.0-13.fc35.noarch f21-backgrounds-gnome-0:21.1.0-13.fc35.noarch f21-backgrounds-kde-0:21.1.0-13.fc35.noarch f21-backgrounds-mate-0:21.1.0-13.fc35.noarch f21-backgrounds-xfce-0:21.1.0-13.fc35.noarch f22-backgrounds-0:22.1.1-11.fc35.noarch f22-backgrounds-base-0:22.1.1-11.fc35.noarch f22-backgrounds-extras-base-0:22.1.1-11.fc35.noarch f22-backgrounds-extras-gnome-0:22.1.1-11.fc35.noarch f22-backgrounds-extras-kde-0:22.1.1-11.fc35.noarch f22-backgrounds-extras-mate-0:22.1.1-11.fc35.noarch f22-backgrounds-extras-xfce-0:22.1.1-11.fc35.noarch f22-backgrounds-gnome-0:22.1.1-11.fc35.noarch f22-backgrounds-kde-0:22.1.1-11.fc35.noarch f22-backgrounds-mate-0:22.1.1-11.fc35.noarch f22-backgrounds-xfce-0:22.1.1-11.fc35.noarch f23-backgrounds-0:23.1.0-12.fc35.noarch f23-backgrounds-base-0:23.1.0-12.fc35.noarch f23-backgrounds-extras-base-0:23.1.0-12.fc35.noarch f23-backgrounds-extras-gnome-0:23.1.0-12.fc35.noarch f23-backgrounds-extras-kde-0:23.1.0-12.fc35.noarch f23-backgrounds-extras-mate-0:23.1.0-12.fc35.noarch f23-backgrounds-extras-xfce-0:23.1.0-12.fc35.noarch f23-backgrounds-gnome-0:23.1.0-12.fc35.noarch f23-backgrounds-kde-0:23.1.0-12.fc35.noarch f23-backgrounds-mate-0:23.1.0-12.fc35.noarch f23-backgrounds-xfce-0:23.1.0-12.fc35.noarch f24-backgrounds-0:24.1.2-11.fc35.noarch f24-backgrounds-base-0:24.1.2-11.fc35.noarch f24-backgrounds-extras-base-0:24.1.2-11.fc35.noarch f24-backgrounds-extras-gnome-0:24.1.2-11.fc35.noarch f24-backgrounds-extras-kde-0:24.1.2-11.fc35.noarch f24-backgrounds-extras-mate-0:24.1.2-11.fc35.noarch f24-backgrounds-extras-xfce-0:24.1.2-11.fc35.noarch f24-backgrounds-gnome-0:24.1.2-11.fc35.noarch f24-backgrounds-kde-0:24.1.2-11.fc35.noarch f24-backgrounds-mate-0:24.1.2-11.fc35.noarch f24-backgrounds-xfce-0:24.1.2-11.fc35.noarch f25-backgrounds-0:25.1.1-12.fc35.noarch f25-backgrounds-base-0:25.1.1-12.fc35.noarch f25-backgrounds-extras-base-0:25.1.1-12.fc35.noarch f25-backgrounds-extras-gnome-0:25.1.1-12.fc35.noarch f25-backgrounds-extras-kde-0:25.1.1-12.fc35.noarch f25-backgrounds-extras-mate-0:25.1.1-12.fc35.noarch f25-backgrounds-extras-xfce-0:25.1.1-12.fc35.noarch f25-backgrounds-gnome-0:25.1.1-12.fc35.noarch f25-backgrounds-kde-0:25.1.1-12.fc35.noarch f25-backgrounds-mate-0:25.1.1-12.fc35.noarch f25-backgrounds-xfce-0:25.1.1-12.fc35.noarch f26-backgrounds-0:26.2.7-10.fc35.noarch f26-backgrounds-animated-0:26.2.7-10.fc35.noarch f26-backgrounds-base-0:26.2.7-10.fc35.noarch f26-backgrounds-extras-base-0:26.2.7-10.fc35.noarch f26-backgrounds-extras-gnome-0:26.2.7-10.fc35.noarch f26-backgrounds-extras-kde-0:26.2.7-10.fc35.noarch f26-backgrounds-extras-mate-0:26.2.7-10.fc35.noarch f26-backgrounds-extras-xfce-0:26.2.7-10.fc35.noarch f26-backgrounds-gnome-0:26.2.7-10.fc35.noarch f26-backgrounds-kde-0:26.2.7-10.fc35.noarch f26-backgrounds-mate-0:26.2.7-10.fc35.noarch f26-backgrounds-xfce-0:26.2.7-10.fc35.noarch f27-backgrounds-0:27.0.1-9.fc35.noarch f27-backgrounds-base-0:27.0.1-9.fc35.noarch f27-backgrounds-extras-base-0:27.0.1-9.fc35.noarch f27-backgrounds-extras-gnome-0:27.0.1-9.fc35.noarch f27-backgrounds-extras-kde-0:27.0.1-9.fc35.noarch f27-backgrounds-extras-mate-0:27.0.1-9.fc35.noarch f27-backgrounds-extras-xfce-0:27.0.1-9.fc35.noarch f27-backgrounds-gnome-0:27.0.1-9.fc35.noarch f27-backgrounds-kde-0:27.0.1-9.fc35.noarch f27-backgrounds-mate-0:27.0.1-9.fc35.noarch f27-backgrounds-xfce-0:27.0.1-9.fc35.noarch f28-backgrounds-0:28.1.5-7.fc35.noarch f28-backgrounds-base-0:28.1.5-7.fc35.noarch f28-backgrounds-extras-base-0:28.1.5-7.fc35.noarch f28-backgrounds-extras-gnome-0:28.1.5-7.fc35.noarch f28-backgrounds-extras-kde-0:28.1.5-7.fc35.noarch f28-backgrounds-extras-mate-0:28.1.5-7.fc35.n
Re: f35-backgrounds ready for review
Wouldn't a source package named 'fedora-backgrounds' work? Each branch in dist-git would allow for new wallpapers each release. An RPM using the Fedora version as its version would result in an NVR that clearly identifies the wallpapers: * fedora-backgrounds/f34 => fedora-backgrounds-34-1.fc34 * fedora-backgrounds/f35 => fedora-backgrounds-35-1.fc35 * fedora-backgrounds/f35 => fedora-backgrounds-35-2.fc35 But I must be missing something; this seems like its way too simple a solution. On Wed, Aug 25 2021 at 09:54:05 PM -0400, Matthew Miller wrote: On Wed, Aug 25, 2021 at 09:48:45PM -0400, Matthew Miller wrote: Back when we were distributing source RPM DVDs, there was a reason to have a new package every release, so the files for the older releases weren't taking up space. But since we don't do that much anymore, maybe it would be better to make one source package and add f35-backgrounds, f36-backgrounds, etc., etc. as new subpackages? (Maybe an f3x-backgrounds release, and start over at f4x-backgrounds, so it doesn't get too crazy?) That way, a new package review wouldn't be required every time. This is just a thought, though. If the current process is working for you, don't let me get in the way! -- Matthew Miller Fedora Project Leader ___ desktop mailing list -- desk...@lists.fedoraproject.org To unsubscribe send an email to desktop-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/desk...@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
golang package review swap
Hello, I've submitted a few packages I need reviewed. I'm happy to swap if anyone has any pending reviews. 1) 1976038 - golang-github-sgreben-flagvar[1] 2) 1976041 - golang-github-peterbourgon-ff-3[2] 3) 1976414 - mqttcli[3] 1: https://bugzilla.redhat.com/show_bug.cgi?id=1976038 2: https://bugzilla.redhat.com/show_bug.cgi?id=1976041 3: https://bugzilla.redhat.com/show_bug.cgi?id=1976414 ___ 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
go-rpm-integration and symlinks
I'm attempting to package github.com/rjeczalik/notify[1] as an RPM. This package includes a utility function[2] that determines whether a path is a symlink, and resolves it to an absolute path. This function clearly has merit, as the package is an abstraction wrapper around inotify. There are tests around this function that set up symlinks and test whether or not the function correctly resolves the symlink redirections. These test functions fail when I build the package[3]. It turns out the abstractions created by %goprep that set up the _build/src directory hierarchy (including the final symlink in the tree) are tripping up the tests that are attempting to resolve symlinks. I replaced the symlink at _build/src/github.com/rjeczalik/notify with a properly unpacked source directory and ran go-rpm-integration check by hand, and the tests pass. If _build/src/github.com/rjeczalik/notify is a symlink, however, the tests are failing. Is there a proper way to manipulate the %goprep macro or tell it to not create symlinks? Or, what's the appropriate Fedora RPM go macro way of handling cases like this? 1: https://github.com/rjeczalik/notify 2: https://github.com/rjeczalik/notify/blob/135d4685afb9d0fb32e23a065b95cd797cb8a4ee/util.go#L67-L99 3: + go-rpm-integration check -i github.com/rjeczalik/notify -b /builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/bin -s /builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build -V 0.9.2-1.20210611gite2a77dc.fc35 -C e2a77dcc14cf6732bfa4c361554f27dc696d5d79 -p /builddir/build/BUILDROOT/golang-github-rjeczalik-notify-0.9.2-1.20210611gite2a77dc.fc35.x86_64 -g /usr/share/gocode -r '.*example.*' Testingin: /builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src PATH: /builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/bin:/builddir/.local/bin:/builddir/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin GOPATH: /builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build:/usr/share/gocode GO111MODULE: off command: go test -buildmode pie -compiler gc -ldflags " -X github.com/rjeczalik/notify/version.commit=e2a77dcc14cf6732bfa4c361554f27dc696d5d79 -X github.com/rjeczalik/notify/version=0.9.2 -extldflags '-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '" testing: github.com/rjeczalik/notify github.com/rjeczalik/notify --- FAIL: TestCanonicalNoSymlink (0.00s) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79" (i=0) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify/testdata"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/testdata" (i=1) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79" (i=2) --- FAIL: TestCanonical (0.01s) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79" (i=0) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify/testdata"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/testdata" (i=1) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify/notify.go"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/notify.go" (i=2) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify/testdata/vfs.txt"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/testdata/vfs.txt" (i=3) util_test.go:25: want full="/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify/testdata/vfs.txt"; got "/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/testdata/vfs.txt" (i=4) --- FAIL: TestCanonical_RelativeSymlink (0.00s) util_unix_test.go:125: want canonical()=/builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/_build/src/github.com/rjeczalik/notify/005632054/a/b/x/y/z/d/e/f; got /builddir/build/BUILD/notify-e2a77dcc14cf6732bfa4c361554f27dc696d5d79/005632054/a/b/x/y/z/d/e/f FAIL exit status 1 FAILgithub.com/rjeczalik/notify 17.491s ___ devel mailing list --
flatpak crashing with SIGSEGV 11
I just installed Fedora 30, and flatpak is crashing after a few seconds of downloading. abrt caught the crash and directed me to this report[1]. It looks like the crash is in libcurl. I can't be the only one experiencing this crash. Has anyone else seen this? 1: https://retrace.fedoraproject.org/faf/reports/2545678/ ___ 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: upstream dev. asks suggestions about howto make packagers work easier (bundled libraries, etc.)
On Sun, 2016-11-20 at 15:42 +, Zbigniew Jędrzejewski-Szmek wrote: > I think it comes down to: > - don't bundle, > - if you have to bundle, provide an easy and unambiguous configure > switch > to use the system version of the dependency, > - never, never, patch stuff in-tree. - Don't hard-code paths (respect things like CMake's GNUInstallDirs). - Strongly consider using a configure/build system (autotools, cmake, ninja, etc.) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: hawaii
On Fri, 2016-01-22 at 18:32 +, mastaiza wrote: > Hi > wanted to know why doesn't work command install @hawaii > -- > devel mailing list > devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject. > org Maybe you're looking for hawaii-shell? sddm-theme-hawaii.noarch : Hawaii theme for SDDM hawaii-components.i686 : Hawaii QtQuick components hawaii-components.x86_64 : Hawaii QtQuick components libhawaii-devel.i686 : Development files for libhawaii libhawaii-devel.x86_64 : Development files for libhawaii libhawaii.i686 : Core share library for Hawaii desktop suite libhawaii.x86_64 : Core share library for Hawaii desktop suite hawaii-shell.i686 : Hawaii shell for desktop, netbook and tablet hawaii-shell.x86_64 : Hawaii shell for desktop, netbook and tablet hawaii-icon-theme.noarch : Icon themes for Hawaii desktop environment hawaii-widget-styles.i686 : Styles for applications using QtQuick Controls hawaii-widget-styles.x86_64 : Styles for applications using QtQuick Controls eyesight.x86_64 : Hawaii desktop image viewer signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Self Introduction: Link Dupont
Hello, I'm finally getting around to officially submitting a package for inclusion in Fedora. I've been a Linux user since around 2002, and have built packages unofficially for nearly all the major distributions (mostly Fedora and ArchLinux). I was an ArchLinux Trusted User for a period of time in 2006/2007. I'm submitting a package for a game called endless-sky. https://bugzill a.redhat.com/show_bug.cgi?id=1297281 GPG: 4450DEBC - l...@fastmail.com signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Stop please
On Thu, 2016-01-07 at 20:45 -0800, Samuel Sieb wrote: > On 01/07/2016 08:34 PM, Michael Catanzaro wrote: > > I decided I would instruct Byron in how to unsubscribe from our > > mailing > > list, when I discovered *I don't know how.* > > > > It seems with HyperKitty we no longer have an easily-accessible way > > to > > unsubscribe from our mailing lists. How can this be done without > > registering a Fedora account? > > > There's info in the email headers although if you're not that > familiar > with mailing lists that's not exactly discoverable. > -- > devel mailing list > devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject. > org Evolution detects those and creates convenient menu entries. Message -> Mailing List -> Unsubscribe from List. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
