Re: F42 Change Proposal: Enable Drm Panic (system-wide)
On 7/13/24 4:32 AM, Javier Martinez Canillas wrote: Zbigniew Jędrzejewski-Szmek writes: The idea for DRM_PANIC is nice, but I worry about the impact of disabling VT_CONSOLE. Plymouth is not used everywhere, e.g. what about cloud images and such? Also, when debugging boot troubles, removing 'rhbg' and 'quiet' are the often first steps. I would expect that in these cases the user has access to a serial console to get the kernel log output. Or it's a common case to read the kernel log messages on cloud instances over VT/fbcon ? Why in the world would you expect this? It's been years (decades?) since most PCs have had a serial port. Expecting people to have (or buy) and set up additional hardware in order to troubleshoot boot issues is a terrible change, IMO. -- If your user interface is intuitive in retrospect ... it isn't intuitive -- ___ 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: F42 Change Proposal: Enable Drm Panic (system-wide)
On 7/13/24 4:39 AM, Sérgio Basto wrote: if I don't like this functionality, can I have my vt consoles back ? It seems that you will need to compile your own kernel in order to do so. -- If your user interface is intuitive in retrospect ... it isn't intuitive -- ___ 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: F42 Change Proposal: Enable Drm Panic (system-wide)
On 7/12/24 11:53 AM, Aoife Moloney wrote: Supported drivers are simpledrm, mgag200, ast, (and imx, tidss, on aarch64). I'm working on nouveau support, and I hope i915 and amdgpu will add support too. If the driver is not supported, you won't see the panic screen, but it won't be worse than what you have today. How is that true. You're unconditionally removing VT_CONSOLE, which is a definite loss in functionality. (Some of us actually use consoles on multiple VTs, even if we're not kernel developers.) Write documentation on how-to debug boot issues without VT_CONSOLE. Maybe also change the systemd log configuration, so that it default to writing the log to the console. It seems to me that this documentation should exist, so that the real impact of this change can be evaluated, before the change is accepted. -- If your user interface is intuitive in retrospect ... it isn't intuitive -- ___ 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: network service removed in Fedora 40 without a Change proposal(?)
On 4/12/24 16:46, Adam Williamson wrote: it seems since I last looked at this, NM has grown some level of openvswitch support, but it seems to be limited, and I don't know off- hand if it's sufficient for what openQA needs. I will need to look into that. https://github.com/NetworkManager/NetworkManager/blob/main/man/nm-openvswitch.xml I've attempted to use it on a couple occasions, and I've never been able to get it to work. It requires creating 3 different objects, in the correct order, with exactly the right settings. And AFAIK, it still doesn't support setting the internal port to the same name as the bridge itself, which is the default behavior of ovs-vsctl and the network scripts, so it's a disruptive change to the network configuration even if it can be made to work. -- Google Where SkyNet meets Idiocracy -- ___ 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: 16 packages still need a Python 3.12 rebuild, final freeze in 6 days
On 9/27/23 04:56, Miro Hrončok wrote: fail2ban https://bugzilla.redhat.com/2219991 https://github.com/fail2ban/fail2ban/issues/3487 Bugzilla ASSIGNED 2 months ago, no update since. Maintainers NEEDINFOed last week. With my system/network administrator hat on, this one is really concerning. After reading the upstream issue, it doesn't seem that there's much chance of this being fixed any time soon. Is there anything in Fedora that provides similar functionality? (I've looked, but come up empty thus far.) -- Google Where SkyNet meets Idiocracy ___ 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: F40 Change Proposal: KDE Plasma 6 (System Wide)
On 9/14/23 11:15, Neal Gompa wrote: I am interested in learning where you're seeing screen sharing issues today. The main one people bring up with me is video conferencing systems, and because of completely unrelated reasons, I've been on a binge of using a variety of them. I thought that I had it working. Then it failed with Google Meet and Firefox when I put a Google Slides presentation into full screen mode. I.e., it worked fine at first, but other people only saw a black screen when I put the presentation into full screen mode. Fortunately, this was an internal team call, but this sort of thing is a disaster in a customer-facing situation. To not have the ability to switch back to X11 is (IMO) unacceptable. (I certainly wouldn't be able to use Fedora/Plasma on my work laptop.) -- Google Where SkyNet meets Idiocracy ___ 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: F40 Change Proposal: KDE Plasma 6 (System Wide)
On 9/13/23 12:52, Kevin Kofler via devel wrote: For Fedora Linux, the transition to KDE Plasma 6 will also include dropping support for the X11 session entirely, leaving only Plasma Wayland as the sole offered desktop mode. Huh?! Why?! KDE upstream is still supporting X11 in Plasma 6. I see no reason to force Wayland upon all users. I do not want Wayland on my desktop (it is already enough of a pain that it is forced upon us by Plasma Mobile on the PinePhone) and I will have to switch to another distribution and orphan all my packages if this happens. There are critical pieces of functionality (e.g. screen sharing) that still don't work reliably on Wayland. -- Google Where SkyNet meets Idiocracy ___ 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: F39 Change Proposal: Allow Removal of tzdata (System-Wide)
On 6/30/23 10:22, Jonathan Wakely wrote: On Mon, 26 Jun 2023 at 19:10, Miro Hrončok wrote: We would also need to ensure UTC work even without tzdata installed. Yes, that would be useful. Although IMHO even that seems like a nice-to-have not an absolute showstopper. Most containerized workloads that don't need time zone info probably aren't using ZoneInfo("UTC") to convert from UTC to UTC, they're probably not using ZoneInfo at all. I would be reluctant to carry this as a downstream-only patch. And the upstream window for changes like this has already closed for Python 3.12. Rather than expecting runtimes and applications to be fixed to work without any timezone information, perhaps the best way forward would be to create a tzdata-utc (and similar Java and Python packages). (Sorry if this has already been suggested & rejected. I don't remember seeing it in this thread, but ...) -- Google Where SkyNet meets Idiocracy ___ 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: It’s time to transform the Fedora devel list into something new
On 4/25/23 14:33, Solomon Peachy via devel wrote: Honestly, if a "how to configure discourse to mimic the MUA-managed mailing list experience (ie not having to log into a web site after the initial configuration)" document is produced, that's probaby sufficient to overcome most of these objections, because then the setup cost is one-off, and the ongoing "interact with Fedora-devel" cost won't be any greater than it already is. Only if there's a companion document on how to interact with Discourse over NNTP. :-( -- Google Where SkyNet meets Idiocracy ___ 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: Mesa in F37- vaapi support disabled for h264/h265/vc1
On 9/28/22 03:50, Tommy Nguyen wrote: This change will only affect AMD, as the intel non-free drivers do not depend on the changes. It is also unclear how this would affect nvidia. There is barely any hardware video acceleration support for nouveau anyway, for which you would install the proprietary driver. Further, as NVIDIA does not expose a vaapi interface, you need to install third party packages to get it to work with Firefox. So AFAICT this will primarily (if not only) affect AMD users. So only everybody who specifically purchased a discrete GPU that works "out of the box" with Fedora? -- Google Where SkyNet meets Idiocracy ___ 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: F37 proposal: Build all JDKs in Fedora against in-tree libraries and with static stdc++lib (System-Wide Change proposal)
On 5/26/22 12:31, drago01 wrote: I am not talking about FLOSS vs non FLOSS, that's obvious. But bundled libs and properly tested / certified vs dynamic linking and less testing / no certification. But if OpenJDK-based binaries can't be distributed without passing the TCK, then it isn't really FLOSS. -- Google Where SkyNet meets Idiocracy ___ 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: F37 proposal: Build all JDKs in Fedora against in-tree libraries and with static stdc++lib (System-Wide Change proposal)
On 5/26/22 10:40, drago01 wrote: Why would we do that? Is the build process really more important than shipping tested software? For Fedora? Yes. Fedora includes lots of untested (in the formal, TCK sense) software. It does not include non-FLOSS software (except maybe in very specific circumstances such as firmware). -- Google Where SkyNet meets Idiocracy ___ 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: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)
On 5/2/22 08:56, Ian Pilcher wrote: IMO, there's a rather desperate need to be able to override the system- wide policy for individual processes, maybe via some sort of wrapper around one of the containerization technologies. Just FYI, I managed to bang out a proof of concept of a "wrapper" that runs a program with a different crypto policy. I've successfully used it to connect to a TLSv1-only HTTP server with both Firefox and curl on a Fedora 36 system running the DEFAULT crypto policy. https://bugzilla.redhat.com/show_bug.cgi?id=2064740#c8 -- Google Where SkyNet meets Idiocracy ___ 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: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)
It sure feels like we're reaching the point where anyone who has to work with any sort of older equipment or servers is going to to forced to switch their entire system to the LEGACY policy, which seems really unfortunate. IMO, there's a rather desperate need to be able to override the system- wide policy for individual processes, maybe via some sort of wrapper around one of the containerization technologies. -- Google Where SkyNet meets Idiocracy ___ 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
BIOS boot - an alternative approach
I'm not a Fedora developer, just a long time interested user, so take this for what it's worth. I'd like to suggest an alternative approach to the BIOS boot (and potentially other similar boot issues), or at least suggest that this approach be discussed. Basically, I suggest that Fedora stop worrying about BIOS boot or other "weird" boot configurations. Instead, provide a truly manual installation path where all boot and storage configuration is the responsibility of the user. This would include: * Installing and configuring the boot loader. * Updating the boot loader configuration when new kernels are installed (although anyone who desires should obviously be free to contribute packages that automate this for particular boot loaders). * All storage configuration - creating partitions, RAID devices, logical volumes, etc. (I.e. the Fedora wouldn't perform any sort of discovery of storage devices; the user would be responsible for selecting devices that already exist in /proc/partitions.) * Booting *something* that can run the Fedora installer. AFAIK, it's still possible to skip boot loader installation during Fedora installation, and the live media installation path exists, so I believe that the main work here would be to package the installer and its associated runtimes, libraries, etc. into some sort of self- contained package that is as independent as possible from the OS on which it is running. Not only would this provide a path for BIOS boot, and similar issues, but it would also support other complex configurations. (I can't even count the number of Anaconda crashes I had back in the day with LVM on MD-RAID.) As I said, I'm not a Fedora developer, but I see this approach as potentially eliminating a lot of work and increasing Fedora's "flexibility" over the long term. OK, now tear this apart. :-) -- Google Where SkyNet meets Idiocracy ___ 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: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)
On 4/7/22 03:43, Lennart Poettering wrote: Do you think the user experience with grub was *good*? Turing complete language? Scripts that generate scripts that generate scripts? Well said. GRUB2 was actually the reason that I kept many of my UEFI-capable systems booting in legacy mode for years (until switching to sd-boot). -- Google Where SkyNet meets Idiocracy ___ 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: Looking for %{forgemeta} GitHub example
On 2/21/22 15:09, Fabio Valentini wrote: So, if you plan to package releases / tags from your GitHub project, just use what's documented here: https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_git_tags Glad I asked. Thanks! -- In Soviet Russia, Google searches 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Looking for %{forgemeta} GitHub example
Can anyone suggest a good (simple) example SPEC file that I can reference as an example of how to use the forgemeta macro? I'm trying to build SPEC files for a couple of personal GitHub-hosted projects, and I'd like to make them as robust as possible. Even though I have no current plans to try to get the software into Fedora, I've always considered the Fedora packaging guidelines to be a solid guide for general RPM development. I've read the "Referencing Source" page[1], but I don't really understand what the actual steps are to use the %{forgemeta} macro. (I'm not even clear on whether it's available on my system; Fedora doesn't seem to include the redhat-rpm-templates package referenced on that page. Thanks! [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/ -- In Soviet Russia, Google searches 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: use unit names in systemd output by default?
On 6/25/21 7:19 AM, Neal Gompa wrote: I personally prefer the description myself, actually. Many unit names are more meaningless than the descriptions. One point ... It's far easier to get the description from the unit name than vice versa. -- In Soviet Russia, Google searches 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: OpenSSH SHA-1 deprecation, developing FAQ, etc
On 3/11/21 5:13 AM, Florian Weimer wrote: In the past (long, long ago), I had to enable Telnet on target devices to work around incompatible cryptography policies. I hope we are not going to return to that. I've had to enable http on my home switches for that very reason, so ... -- In Soviet Russia, Google searches 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package update requires modification of config file in users' home directories
On 3/9/21 4:21 PM, Alexander Ploumistos wrote: Do all of the DEs we have in Fedora support the same notification mechanisms? I'm not 100% sure, but it's freedesktop.org/D-Bus based, so it's about as standard as it gets these days. (Probably irrelevant, though.) I added ln -sf %{_libdir}/%{name}/libobabeliface.so %{buildroot}%{_libdir}/%{name}/libobabeliface-qt5.so to the %install section of my spec file Yeah. If that works it's far and away the easiest way to go about it. -- In Soviet Russia, Google searches 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package update requires modification of config file in users' home directories
On 3/9/21 1:39 PM, Alexander Ploumistos wrote: Well, the first option is still a no-no, as the fixup has to happen in the user's home directory. For the second one, I think I'd need to add something like "Requires: zenity", which in turn would pull in other dependencies. I don't believe that it's forbidden by Fedora's policy, as it would be the wrapper making the changes, which is effectively no different from the program itself doing it, if it had that capability. The real problem with this approach is the potential to mess up the user's configuration if the wrapper encounters something that it doesn't expect, which is why a warning message approach is probably better. You could probably do something very lightweight with the desktop notification service, but it isn't an area that I know a lot about. After discussing with upstream, I am going to add a symlink for now and they're going to take care of things programmatically in a subsequent update. Where are you going to add the symlink? -- In Soviet Russia, Google searches 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package update requires modification of config file in users' home directories
On 3/8/21 5:10 PM, Alexander Ploumistos wrote: Is there something I can do to sed out the -qt5 suffix, or should I just bite the bullet, build the update and wait for the bug reports to come in? You could replace the executable with a wrapper script that performs the necessary fixups before calling the actual executable. Or (probably better) just shows a message telling the user to do it. -- In Soviet Russia, Google searches 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Backwards-incompatible RPM format change in Fedora 34?
On 1/21/21 5:43 AM, Fabio Valentini wrote: That's just not acceptable. Which means that signed RPM contents need to be postponed at least until all supported Fedora releases have an RPM version that can read those files. I'm not sure what Fedora's policy on this is, but as an administrator with a mix of Fedora and EL systems, it would be really, really helpful if RPM in the latest version of EL could parse these RPMS (at least SRPMS; not sure if they're affected by this change). -- In Soviet Russia, Google searches 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
Re: splitting out systemd-networkd, systemd-standalone-{sysusers,tmpfiles} subpackages in F33+
On 9/30/20 2:19 PM, Michael Catanzaro wrote: On Wed, Sep 30, 2020 at 2:00 pm, Ian Pilcher wrote: And what about places where NetworkManager isn't used? (Just because it's the default, doesn't mean that it's used everywhere.) NetworkManager is used everywhere by default. If you want to disable it, you have to do manual work to do that. If you do manual work to disable NetworkManager, you can also do manual work to disable systemd-resolved. Indeed, but I was responding to this: On 9/30/20 1:35 PM, Neal Gompa wrote: > Please, no more package splitting. And NetworkManager is used across > all variants of Fedora, so resolved should be installed in all places > where NetworkManager is used. Which (to my reading) says that because NetworkManager is the *default* everywhere (even though it can be uninstalled), systemd-resolved should be *installed* everywhere (and should not be uninstallable). I don't follow that logic. -- In Soviet Russia, Google searches 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
Re: splitting out systemd-networkd, systemd-standalone-{sysusers,tmpfiles} subpackages in F33+
On 9/30/20 1:35 PM, Neal Gompa wrote: Please, no more package splitting. And NetworkManager is used across all variants of Fedora, so resolved should be installed in all places where NetworkManager is used. And what about places where NetworkManager isn't used? (Just because it's the default, doesn't mean that it's used everywhere.) -- In Soviet Russia, Google searches 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
Re: This is bad, was Re: Fedora 33 System-Wide Change proposal: systemd-resolved
On 9/28/20 8:32 AM, Zbigniew Jędrzejewski-Szmek wrote: Yeah, that test is far from ideal, but we need something. If you have a constructive proposal how to improve it, I'm all ears. I anticipated this question. I don't have a good proposal for you ... but I believe that it's up to the people advocating/implementing this change to come up with that. If it isn't possible to automate this change in a reliable way, maybe it shouldn't be automated. -- In Soviet Russia, Google searches 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
Re: This is bad, was Re: Fedora 33 System-Wide Change proposal: systemd-resolved
On 9/28/20 6:47 AM, Zbigniew Jędrzejewski-Szmek wrote: Instructions were already posted by Vitaly, so I won't repeat that here. I'll just note that the scriptlet in systemd.rpm looks for 'Generated by NetworkManager' in /etc/resolv.conf as an indicator that the file is autogenerated. Which is a terrible idea, as has been previously mentioned. It really only indicates that the file was once touched my NetworkManager, not that it is currently managed. If often let Anaconda set up a new system witha NetworkManager-managed DHCP and then convert to a legacy network scripts-managed static IP later. This doesn't change the DNS server or domain, so I don't bother editing resolv.conf to remove this comment. I'm relatively certain that this is a common pattern. -- In Soviet Russia, Google searches 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
Re: Fedora 33 System-Wide Change proposal: systemd-resolved
On 7/28/20 12:31 PM, Michael Catanzaro wrote: I think we should remove it if it's generated by NetworkManager, and leave it untouched otherwise. If NetworkManager is managing DNS then it will just push all its settings to systemd-resolved anyway after upgrade, right? Don't assume that the presence of the "Generated by NetworkManager" comment means that NetworkManager is *currently* managing that file; it just means that it did so when the file was generated. -- In Soviet Russia, Google searches 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
Re: Mock build Fedora package on CentOS 7
On 1/18/20 12:57 PM, Nico Kadel-Garcia wrote: This is turning into a "debug mock on CentOS" discussion, not a Fedora discussion per se. Please let me know if it should be over in the mock github.com issues instead. Indeed. My original hope was that I was simply missing something that was obvious to folks who do this more often. (I only started on this path because the thunderbird RPM takes so painfully long to rebuild, and my CentOS 7 server is much more powerful than my Fedora workstation.) OTOH, this issue is probably(?) fairly specific to building Fedora packages. I think you're missing some of the options I've suggested for dnf based operating systems, or fedora-31.tmpl in particular in my published mock-core-configs.spec file. And is you "mock" up to the latest reason from EPEL I'll urge you to publish a diff between the RPM published fedora-31.tmpl and yours to isolate the issue. AFAIK, I have the latest version of mock: [root@breadbox templates]# rpm -q mock mock-core-configs mock-1.4.21-1.el7.noarch mock-core-configs-31.7-1.el7.noarch Here is the diff: [root@breadbox templates]# diff -u fedora-31.tpl.orig fedora-31.tpl --- fedora-31.tpl.orig 2019-11-01 09:17:14.0 -0500 +++ fedora-31.tpl 2020-01-18 16:49:47.973139724 -0600 @@ -9,6 +9,8 @@ config_opts['releasever'] = '31' config_opts['package_manager'] = 'dnf' config_opts['bootstrap_image'] = 'fedora:31' +config_opts['use_bootstrap_image'] = True +config_opts['use_bootstrap_container'] = True config_opts['yum.conf'] = """ [main] -- In Soviet Russia, Google searches 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
Re: Mock build Fedora package on CentOS 7
On 1/18/20 5:07 AM, Nico Kadel-Garcia wrote: The inserted arguments are order sensitive, and need to be in the right place in fedora-31.tmpl on the latest release of mock and mock-core-cnfigs. See my notes at: https://github.com/rpm-software-management/mock/issues/390 And use this in /etc/mock/templates/fedora-31.tmpl config_opts['bootstrap_image'] = 'fedora:31' config_opts['use_bootstrap_image'] = True config_opts['use_bootstrap_container'] = True This uses podman to download an OS image, installs that, uses that to run mock tools to build a new image, etc. It's a bootstrap process, it's slow, and I've found it to be burdensome and fragile, not allowing operation on certain host server filesystems. And no, I don't remember the list of forbidden filesystems. I was aware of that issue, but I wasn't aware that it affected the command-line options. After editing fedora-31.tpl, I can now see mock pulling the container image and rebuilding the root cache. Unfortunately, I still get the same error in the end: Start: build phase for thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm Start: build setup for thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm warning: line 206: It's not recommended to have unversioned Obsoletes: Obsoletes: thunderbird-lightning warning: extra tokens at the end of %endif directive in line 625: %endif # build_langpacks Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=157896 Wrote: /builddir/build/SRPMS/thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm Failed to set locale, defaulting to C.UTF-8 No matches found for the following disable plugin patterns: local, spacewalk No such command: builddep. Please use /usr/bin/dnf --help It could be a DNF plugin command, try: "dnf install 'dnf-command(builddep)'" Finish: build setup for thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm Finish: build phase for thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm ERROR: Exception(thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm) Config(fedora-31-x86_64) 3 minutes 5 seconds INFO: Results and/or logs in: /var/lib/mock/fedora-31-x86_64/result ERROR: builddep command missing. Please install package dnf-plugins-core. -- In Soviet Russia, Google searches 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
Re: Mock build Fedora package on CentOS 7
On 1/16/20 9:39 AM, Miroslav Suchý wrote: https://github.com/rpm-software-management/mock/wiki/Feature-container-for-bootstrap Right, but it still doesn't work. [pilcher@breadbox ~]$ cat /etc/centos-release CentOS Linux release 7.7.1908 (Core) [pilcher@breadbox ~]$ cd /etc/mock/templates [pilcher@breadbox templates]$ grep bootstrap_image fedora-31.tpl config_opts['bootstrap_image'] = 'fedora:31' [pilcher@breadbox templates]$ cd [pilcher@breadbox ~]$ mock --bootstrap-chroot --use-bootstrap-image -r fedora-31-x86_64 thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm INFO: mock.py version 1.4.21 starting (python version = 3.6.8)... (...) No such command: builddep. Please use /usr/bin/dnf --help It could be a DNF plugin command, try: "dnf install 'dnf-command(builddep)'" Finish: build setup for thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm Finish: build phase for thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm ERROR: Exception(thunderbird-68.4.1-1.mzbz1526765.fc31.src.rpm) Config(fedora-31-x86_64) 1 minutes 21 seconds INFO: Results and/or logs in: /var/lib/mock/fedora-31-x86_64/result ERROR: builddep command missing. Please install package dnf-plugins-core. -- In Soviet Russia, Google searches 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
Re: Mock build Fedora package on CentOS 7
On 1/15/20 1:26 PM, Stephen John Smoogen wrote: On Wed, 15 Jan 2020 at 12:08, Ian Pilcher wrote: Is $SUBJECT possible these days? I've tried with both --bootstrap-chroot and --use-bootstrap-image, but the build is failing with: ERROR: builddep command missing. Please install package dnf-plugins-core. This happens even when the dnf-plugins-core package is installed (from EPEL) on the CentOS 7 host, probably because the Fedora 31 container image doesn't include that package. Is there a secret incantation to make this work? I do not see a dnf-plugins-core in EPEL. I see a dnf-langpacks-conf and so I am not sure what is going on here. I messed up. dnf-plugins-core is actually in Extras. -- In Soviet Russia, Google searches 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
Mock build Fedora package on CentOS 7
Is $SUBJECT possible these days? I've tried with both --bootstrap-chroot and --use-bootstrap-image, but the build is failing with: ERROR: builddep command missing. Please install package dnf-plugins-core. This happens even when the dnf-plugins-core package is installed (from EPEL) on the CentOS 7 host, probably because the Fedora 31 container image doesn't include that package. Is there a secret incantation to make this work? -- In Soviet Russia, Google searches 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
Re: F29 System Wide Change: i686 Is For x86-64
On 06/04/2018 04:28 AM, Florian Weimer wrote: It should, because -march=x86-64 implies just SSE2 and FXSR, and Xeon MP supports both. But the intent is what the subject says: i686 binaries are for running legacy software on x86-64 systems, and nothing more. So the 32-bit x86 SIG would be required to rebuild all of the userspace packages to run on actual 32-bit hardware, right? (What would those be called, since i686 is taken?) -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ 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/message/WZMWAPNARRWXNJX5LOLUBJYDIOK2I7EU/
Re: Hiding the grub menu by default on single OS installs
On 05/31/2018 07:25 AM, Hans de Goede wrote: So for F29, single OS install we get: 1) grub menu hidden by default with a 1 second timeout to press ESC or F8 to show it 2) grub menu shown with 5 sec timeout after a failed boot 5 seconds seems like an awfully short timeout after a failed boot. -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ 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/message/V2VXWSRSH3HT3UHGC45VX4RP33LR3CIB/
[EPEL-devel] Re: Blue Sky Discussion: EPEL-next or EPIC
On 05/17/2018 06:53 PM, Stephen John Smoogen wrote: I think with our horrible history of naming this project EPEC is what we go with. I just want the new logo not to look like a horse's butt with tail. Already taken. https://www.openstack.org/themes/openstack/images/project-mascots/Cinder/OpenStack_Project_Cinder_vertical.jpg -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org/message/FZIJFTZFI37UUCOJQIVPFAOYFDWSVRZR/
Re: I would like to propose that we turn on XFS Reflink in Fedora 29 by default
On 05/02/2018 08:56 AM, Eric Sandeen wrote: Given that it is exception activity, dump/mks/restore is also a less convenient but more robust solution to the problem. I'm sitting in a hotel room with a laptop. What do I backup *to*? If you're putting your years-old root or home filesystem at risk to bisect a bug I'd humbly suggest that an external or additional disk might be more suited to the task. See above. I don't have any real horse in this race - if Fedora feels that shrink capability trumps features like reflink, that's fine. Just offering my thoughts on the matter, and trying to point out that shrink has its downsides. Ack. I personally think that it's fine that XFS can't shrink. It's just important to be clear about the use cases for which it's intended. I also get uncomfortable with just dismissing use cases like this without considering that there may be legitimate reasons for them. -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: I would like to propose that we turn on XFS Reflink in Fedora 29 by default
On 05/02/2018 08:25 AM, Eric Sandeen wrote: I've always seen the need for shrink as an indicator that someone had poor planning along the way, or insufficient tools for provisioning to start with. Sure, there are exceptions, but in general who needs shrink on a regular basis? The point isn't so much that you need it on a regular basis, it's that when you need it, you *really* need it. I'll buy the poor planning argument on a server that does pretty much the same thing for the entirety of its life/deployment, but the case of a laptop/desktop that goes years without being reinstalled, and then unexpectedly needs tens of gigabytes of space to bisect a kernel bug is very different. -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: starting services in fedora
On 04/17/2018 12:41 AM, Zbigniew Jędrzejewski-Szmek wrote: tl;dr: the proposal is to start services immediately during installation (in %post), iff they are enabled in presets and the system is live (not a chroot or such). This would mean that e.g. after 'dnf install gpm' gpm would be running when dnf exits. What if gpm is pulled in as a dependency? (gpm may not be the best example here, but Avahi definitely is pulled in as a dependency sometimes.) -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Announcing DNF 3 development
On 03/22/2018 07:40 AM, Daniel Mach wrote: We are pleased to announce that development of DNF 3 has started. This version is focused on performance improvements, new API and consolidating the whole software management stack. Please read more details on our blog: https://rpm-software-management.github.io/announcement/2018/03/22/dnf-3-announcement/ Can someone explain how DNF 2 can be considered "finished", when it still can't provide the dependency information that yum did? https://bugzilla.redhat.com/show_bug.cgi?id=1549851 -- ======== Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: RFC: retiring yum
On 09/01/2017 02:21 PM, Igor Gnatenko wrote: This is true and we have plans to implement this, but problem is that we don't know how to represent data. When it is about installing some packages -- it's more or less easy to show, but when upgrades / downgrades are involved it becomes way more complicated. If you have some actual suggestions -- feel free to contact me off list or post them here. ☺ I won't claim to be a huge fan of the way that yum insisted on spewing detailed dependency information, but it did provide the information require to answer those "Why does Inkscape require mdadm?" type questions. I would think that format could be a starting point (shown only when --verbose or some other option is used). As far as I remember, yum shows this information for both installs and upgrades; I'm not sure about downgrades. -- ======== Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: RFC: retiring yum
On 09/01/2017 12:01 PM, Igor Gnatenko wrote: Do you still have some critical missing functionality in DNF? And let us know reasons why would you like to keep YUM available (hopefully there are no)! AFAIK there is still no way to get dependency information out of DNF. (There may be a way to do it, but --verbose certainly doesn't.) -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
python-dnf questions
Does anyone know of a mailing list/forum/etc. for DNF Python API questions? -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: What happen to UINT16_MAX
On 06/01/2017 02:09 PM, Jonathan Wakely wrote: On 01/06/17 13:20 -0500, Ian Pilcher wrote: Actually, you need inttypes.h for the limit macros. You're thinking of the format specifier macros for printf. The limit macros are in . Right you are. Sorry for the misinformation. -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: What happen to UINT16_MAX
On 06/01/2017 01:07 PM, Tom Hughes wrote: Well presumably you're not including stdint.h for some reason. Actually, you need inttypes.h for the limit macros. -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Deprecated net-tools? Mass bug filing?
On 05/17/2017 12:47 PM, Chuck Anderson wrote: I don't mind removing dependencies on net-tools, as long as there still exists these commands in the default install: netstat arp ifconfig route I consider those to be a basic part of the user interface of any Linux/UNIX system--there is too much historical precedent and documentation to remove them IMO. It would be like trying to remove "ls" just because there is a newer/better way to list files. Removing RPM dependencies on the net-tools package and deciding whether it should be installed by default are two separate (albeit related) discussions. -- ======== Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.
Giant +1 There are few things more frustrating than being bitten by a bug that goes unfixed for release after release, while being told by the maintainer that they simply don't have time to fix anything but release blockers. This wouldn't automaticall fix this, but it would certainly provide a strong signal that a bug is deemed worthy of attention by someone other than the reporter. -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: ... and Fedora 25! - Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24
On 10/04/2016 01:03 PM, Tomasz Torcz wrote: On Tue, Oct 04, 2016 at 12:31:43PM -0500, Ian Pilcher wrote: Can you clarify? In what circumstances would the dnf command running within a screen session not survive an X/desktop crash? KillUserProcesses=yes Ouch! Forgot about that. -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: ... and Fedora 25! - Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24
On 10/04/2016 11:41 AM, Adam Williamson wrote: On Tue, 2016-10-04 at 18:28 +0200, Karel Volný wrote: or better (IMHO) - run it using `screen` ;-) I think whether that's better or not depends on exactly how the screen/tmux server process was run... Can you clarify? In what circumstances would the dnf command running within a screen session not survive an X/desktop crash? -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
AMD FirePro W4100
I'm looking at upgrading my video setup to support 3 monitors. I had intended to purchase an AMD FirePro V4900, since it is known to "just work" with the open source drivers, but I see that the W4100 is now available at approximately the same price point, with more memory, etc., etc. Has anyone tried a W4100 with the open source drivers? -- ======== Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: AMD FirePro W4100
On 01/20/2016 01:21 PM, Ian Pilcher wrote: I'm looking at upgrading my video setup to support 3 monitors. I had intended to purchase an AMD FirePro V4900, since it is known to "just work" with the open source drivers, but I see that the W4100 is now available at approximately the same price point, with more memory, etc., etc. Has anyone tried a W4100 with the open source drivers? Wrong list, sorry. I gave the W4100 a quick shot, but I was unable to get any output once KMS kicked in. (I didn't try the proprietary drivers.) Exchanged the W4100 for a V4900 which seems to be working perfectly so far. -- ======== Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Pruning journal on systemd 216
Running Fedora 21 with systemd 216, and just discovered that journal files are taking up 1.8G. I see references to "journalctl --vacuum-time" on the interwebs, but that option doesn't seem to be present in my version. So how should I go about cleaning out older journal data? TIA! -- ======== Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [EPEL-devel] Centos 7, 32 bits edition
On 10/15/2015 07:29 AM, Matthew Miller wrote: And in fact is out now: http://seven.centos.org/2015/10/centos-linux-7-32-bit-x86-i386-architecture-released/ And hopefully we'll see EPEL 7 for 32-bit x86 soon ... -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: Linux 4.0
On 02/23/2015 11:38 AM, poma wrote: On 23.02.2015 14:41, Josh Boyer wrote: ... things might still pop up. If you are using out of tree drivers (vbox, nvidia) you might want to pay extra attention. https://fedoraproject.org/wiki/Forbidden_items?rd=ForbiddenItems#NVIDIA_Proprietary_Graphics_Drivers That pages discusses the reasons that those items are not included in Fedora. I'm pretty sure that it hasn't yet been declared a thought- crime to discuss them. -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F22 System Wide Change: Login Screen Over Wayland
How does this affect users of other display managers (or does it)? -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Split DNS broken again - test case?
https://bugzilla.redhat.com/show_bug.cgi?id=1161232 It seems like this is the 3rd or 4th time that this functionality has been broken, leaving anyone who needs to simultaneously connect to both VPN and other non-public (e.g. home network) resources up a creek. Would this be worth of a test case? -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
On 12/21/2014 10:59 PM, Felix Miata wrote: I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. Ps on another tty shows Yum is still running. Disk space and RAM are ample. Top shows virtually no CPU in use. Nothing seems amis in the tail of /var/log/yum.log. How does one find out why nothing is happening? strace -p $YUM_PID -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Improving the offline updates user experience
On 09/13/2014 03:59 AM, Fred New wrote: One step up from this would be something like a kpatch process in rpm combined with packaged metadata that replaces in-memory modules so that reboots wouldn't be necessary. Yeh, probably impossible. This has almost certainly already been considered by people smarter than me, but it occurs to me that there's no reason that kexec couldn't some- how pass LUKS/dm-crypt keys to the new kernel. -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: defining firewalld services
On 07/07/2014 12:03 PM, Thomas Woerner wrote: On 07/07/2014 02:55 PM, Stephen Gallagher wrote: Thomas, the real question here is this: If a package wants to install (and maintain) its own set of firewalld service definitions, is the approach Stef took the best one? If so, we should submit a Packaging Guidelines edit to the FPC and get this codified where others can find it. Yes, this is the best approach right now. Hmm. If I've made a temporary change to my firewall settings, I might be a bit annoyed if an (apparently unrelated) package installation caused the configuration to revert to the permanent configuration. Is there not a more specific command that adds the service definition to the current environment without a full reload? -- Ian Pilcher arequip...@gmail.com Sent from the cloud -- where it's already tomorrow -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: delta rpms - can we turn them off
On 06/27/2014 12:28 PM, Dridi Boukelmoune wrote: It may also be possible to compress-and-sign them on the fly. If the gpg check can be done incrementally, you could compress the rpm to /dev/null and gradually compute the signature. That leaves you a signature to check and a ready-to-install rpm you don't need to uncompress again. I'm pretty sure that the compression takes the vast majority of the time. -- Ian Pilcher arequip...@gmail.com Sent from the cloud -- where it's already tomorrow -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: SELinux RPM scriplet issue annoucement
On 01/20/2014 11:48 AM, Adam Williamson wrote: The bug currently under discussion was caused by a change that came in inadvertently, not intentionally, and was actually intended for Rawhide. I can't help wondering if there's an opportunity for process/workflow improvement right there. -- Ian Pilcher arequip...@gmail.com Sent from the cloud -- where it's already tomorrow -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On 12/04/2013 04:56 PM, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? char *output; output = get_user_input(...); printf(output); What happens when the user enters %n? -- Ian Pilcher arequip...@gmail.com Sent from the cloud -- where it's already tomorrow -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: TLS libraries and licenses
On 11/27/2013 10:46 AM, Dan Williams wrote: On Wed, 2013-11-27 at 09:27 -0700, Jerry James wrote: The second option is gnutls, which is various flavors of GPL and LGPL, and so is fine for us. We did have one developer wonder why gnutls is preferred over openssl, though. Can anyone answer that question? You answered that just below; because OpenSSL is GPL incompatible. Since gnutls is LGPL, it can be used in most places openssl can be used, *plus* it can be used with GPL software. Obviously, consult your lawyers for the specifics of your situation. There's also the issue of the OpenSSL documentation (or lack thereof). -- Ian Pilcher arequip...@gmail.com Sent from the cloud -- where it's already tomorrow -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20b Some characters seems to not to display ok on Virtual Terminals (but the keymap seems to be ok)
On 10/14/2013 03:40 PM, Reartes Guillermo wrote: The 'ñ' is displayed as a Arrow_Down character. I echoed it and copied to a file which i transfered to a F19 host and is is displayed there it is shown as a 'ñ'. Also the '€' is affected, it is displayed as a '¡'. Is this a known issue? I suspect you're hitting https://bugzilla.redhat.com/show_bug.cgi?id=970030 -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
UTF-8 locale in RPM build
I'm trying to build a jpackage SRPM (jena-iri) on Fedora 19, and it's failing, because the locale (LANG) is apparently set to C during the build. (javac and javadoc don't like non-ASCII characters in source files in an ASCII locale.) What's the best way to set it to a UTF-8? (Should I just add export LANG=en_US.UTF-8 to the relevant sections of the SPEC file?) Thanks! -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Why is AHCI built-in?
Somewhere along the line, the AHCI driver was changed from a module to being built-in to the kernel. This is a major PITA for anyone who wants to use a different/customized version of this driver. (I want to rebuild it with LED triggers for the disk LEDs on my NAS.) I haven't been able to find anything in git or BZ about why this was done, probably because searching on ahci and module in Bugzilla isn't exactly productive. Any pointers? TIA -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Why is AHCI built-in?
On 08/19/2013 01:19 PM, Kyle McMartin wrote: because it's commonly used and found on basically every machine now. there are many advantages to having it built in that outweigh the cons. A couple of questions: - What are the advantages of having the driver built-in, as compared to simply ensuring that it's always included in the initramfs? - Was this change discussed anywhere? Thanks! -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Why is AHCI built-in?
On 08/19/2013 01:48 PM, Peter Robinson wrote: Ultimately if there's missing features you should communicate with the author of the patch as to why they're not upstream and then you'd not have to care about whether its built in or a module. Heh. I kind of doubt that the AHCI driver maintainers are interested in adding hardware-specific LED triggers. Probably on the kernel list if anywhere, I vaguely remember reading about it. Pointed to the discussion (back in 2008!) by a co-worker. I didn't even know that Fedora had its own kernel list. (I wrongly assumed that this change post-dated the RHEL 6 branch, since AHCI is still a module in RHEL 6.) Thanks for the info! -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
yum groups vs. rpm dependencies
I'm trying to figure out if I agree with the resolution of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=914965 Thoughts? -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 Self Contained Change: SDDM as the default KDE DM
On 07/10/2013 01:03 PM, Jaroslav Reznik wrote: Compared to the current DM, KDM, it currently lacks a few features (such as XDMCP) but adds some other ones (QtQuick themes) or is currently adding them (Keyboard layout switching in the greeter). Is XDMCP on the roadmap? It's a pretty darn important feature, as it's the only way (of which I know) to get a log-in screen via VNC. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: icedtea-web installed and enabled by default in Fedora 19
On 06/17/2013 10:03 AM, Bill Nottingham wrote: The one issue I can see with removing it is that the plugin finder you then get in Firefox if you hit a Java site doesn't work to actually get you the Fedora version. The one issue I see is that it's darn near impossible to find the package if you don't already know its name. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: bugzilla.redhat.com vs upstream bug trackers
On 06/17/2013 04:49 PM, Jóhann B. Guðmundsson wrote: The only difference is that I would add step number five acting as the liaison between upstream and downstream for reporters which to me is unavoidable for a packager/maintainer from my pov. +1 I think that this is where a Fedora packager can add a ton of value, even without deep knowledge of the code being packaged. A lot of open source development communities are -- dare I say it -- fairly cliquish. A random end-user's bug reports or questions are often pretty much ignored. (I recognize that this isn't out of malice, BTW. Everyone is busy and we all have to do a sort of social triage to stay sane.) In many cases, the Fedora packager has built up a level of credibility with the development community that could get a bug report the attention that it deserves. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: when startup delays become bugs
On 05/15/2013 10:53 AM, Jeffrey Bastian wrote: Maybe you have iptables blocking mDNS traffic (tcp port 5353)? UDP -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Idea: {Gnome,KDE,Xfce,...} Minimal Desktop groups
On 04/29/2013 10:01 AM, Stephen Gallagher wrote: That said, if someone wanted to do the exploration, come up with those minimal package sets and propose them for inclusion to comps.xml (with the blessing of the related desktop SIG), I have no problems with it myself. To a certain extent, this has already been done. yum groupinfo gnome- desktop will list the mandatory packages for the group. (Although it's still a pretty hefty list.) AFAIK, there isn't any easy way to install just the mandatory packages in a group. One has to set group_package_types in yum.conf. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Improving the Fedora boot experience
On 03/12/2013 06:10 PM, Nicolas Mailhot wrote: The proposal discussed here is not to keep the hood on the car. The proposal is to remove any indication there is a hood, and show the user a seamless surface with no hint it can be opened (or how). Reminds me of the time I had to pay like $90 for rental car gas because I couldn't figure out how to open the gas cap. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: twinkle: Intent to retire
On 03/09/2013 12:08 PM, Kevin Fenzi wrote: So, I am going to retire this package in rawhide soon unless there's folks with a very strong C++ background wishing to fix issues and basically become the new upstream. Does Fedora currently have a functional soft-phone? -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: To the Mate package maintainers
On 01/18/2013 06:12 PM, Matthew Miller wrote: What is that screen for? It literally took me a minute to figure out what to do with it the first time I saw it, and then every time after that it just gets in the way of what I want to do. Why *can't* I turn it off? It's part of the nefarious master plan to turn all of our computers into giant cell phones/tablets. Don't believe that there are a lot of people who think this way? Check this out ... http://www.businessinsider.com/panasonic-unveils-20-inch-4k-tablet-at-ces-2013-1 -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Wireshark
Wireshark in F18 has some significant problems, caused by the change to Gtk3. Can this please be reverted to build against Gtk2 until upstream works these issues out? https://bugzilla.redhat.com/show_bug.cgi?id=894655 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7377 Not sure if this has been fixed: https://bugzilla.redhat.com/show_bug.cgi?id=871091 -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Wireshark
On 01/15/2013 06:27 PM, Samuel Sieb wrote: See https://bugzilla.redhat.com/show_bug.cgi?id=863602 for the gtk3 resizing issue. I have attached a patch there that fixes the resizing issues for me. Really unfortunate that this has been known for 3 1/2 months, and the package maintainer/bug assignee hasn't bothered to even respond. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: nc replaced by nmap ncat
On 07/19/2012 05:12 AM, Petr Šabata wrote: The old Fedora, heavily patched OpenBSD nc package was just obsoleted by the nmap ncat implementation, available as the nmap-ncat subpackage. Those are mostly compatible and this change shouldn't cause much headache but please check your netcat dependant scripts or apps. This appears to break freenx-server. https://bugzilla.redhat.com/show_bug.cgi?id=891109 -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Grub2
On 12/09/2012 02:38 AM, Felix Miata wrote: Which updates? Grub2 won't get updated if it isn't installed. You'll need to update Grub's menu yourself at kernel update time. You can make that easier on yourself by maintaining /boot/vmlinuz-cur and /boot/vmlinuz-prv symlinks to the two most recent kernels and use the symlinks in Grub's menu. I have a boot partition I don't mount as boot, and keep a fully self-maintained Grub on it to use instead of all the Grubs installed to / partitions. Actually, grubby in Fedora is still perfectly capable of updating the old grub.conf. To set this up, create a symlink: # ln -s /boot/grub/grub.conf /etc And create /etc/sysconfig/kernel: # UPDATEDEFAULT specifies if new-kernel-pkg should make # new kernels the default UPDATEDEFAULT=yes # DEFAULTKERNEL specifies the default kernel package type DEFAULTKERNEL=kernel Easy peasy -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: f18: how to install into a LVM partitions (or RAID)
On 10/19/2012 10:01 AM, David Lehman wrote: This is the main piece of functionality that's still missing: allocating devices from preexisting VGs. You can create and destroy lvm devices. You can reuse existing LVs, optionally reformatting them. You can encrypt or decrypt them. What you cannot do is allocate new LVs from old VGs. That's sort of the last item on the TODO list. It looks like this is still the case in beta RC1, right? -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: f18: how to install into a LVM partitions (or RAID)
On 11/21/2012 02:01 PM, David Lehman wrote: On Wed, 2012-11-21 at 12:09 -0600, Ian Pilcher wrote: It looks like this is still the case in beta RC1, right? Yes. I've just completed testing of patches for this stuff. It was decided that it's too late to try to get them into the Beta. I can provide you with an updates image that adds the functionality if you are interested. Please. Thanks! -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
PKLA -- JavaScript
On 11/14/2012 01:07 AM, tim.laurid...@gmail.com wrote: http://davidz25.blogspot.dk/2012/06/authorization-rules-in-polkit.html http://www.freedesktop.org/software/polkit/docs/master/polkit.8.html I've just reviewed those pages, and it's certainly not obvious to me how I would go about porting a PKLA file. [libvirt Management Access] Identity=unix-group:wheel Action=org.libvirt.unix.manage ResultAny=no ResultInactive=no ResultActive=yes The latter page, in particular, reads like something written for an audience of developers, rather than system administrators. I'm sure that I can figure it out in time, but this seems like a terrible burden to put on system administrators, particularly those who are (sometimes proudly) averse to anything that smacks of programming. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: remove polkit from core?
On 11/13/2012 09:50 PM, Matthias Clasen wrote: Yes, this was a misunderstanding. What is still supported is the .policy files containing the default policy. And that is very good, since such policy files are installed by pretty much every package that uses polkit, while .pkla files were only used by very few packages. Wait. So the .pkla file I wrote to allow my run virt-manager as my normal user is going to stop working, and I'm going to have to write the replacement in JavaScript? Let's just say I'm struggling to find the words ... -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On 11/13/2012 06:55 PM, Adam Williamson wrote: It might be worth re-evaluating whether that's realistic any more, though, and whether we're _really_ committed to finally replacing network with NM in some kind of reasonable timeframe. To this point, NetworkManager has failed to gain basic bridge support. In the meantime, Open vSwitch, which has a ton more configuration options has been recently added to the distro. I'd argue that NM actually continues to fall farther behind. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: f18: how to install into a LVM partitions (or RAID)
On 10/25/2012 10:46 AM, David Lehman wrote: It is planned (but at risk) for the beta and a must-have for GA. If it's a must-have for GA, but it isn't in the beta, how does it get tested? -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: f18: how to install into a LVM partitions (or RAID)
On 10/19/2012 10:01 AM, David Lehman wrote: You can create and destroy lvm devices. You can reuse existing LVs, optionally reformatting them. You can encrypt or decrypt them. What you cannot do is allocate new LVs from old VGs. That's sort of the last item on the TODO list. Is this functionality planned for the beta? GA? F19? As I said up-thread, I believe that this information should be much more widely disseminated. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: f18: how to install into a LVM partitions (or RAID)
On 10/17/2012 10:55 AM, Adam Williamson wrote: Was the old one really better, or were you just used to it? Comparing the first time you use the new dialog to the 50th time you used the old one is an entirely unfair comparison. You have to compare the first time you use the new dialog to the first time you used the old one. *Any* new design will seem more difficult than the old one, at first, to someone who was familiar with the old one. Just my opinion, but I believe that a lot of the confusion is caused by the lack of a clear statement that LVM, RAID, etc., are *supposed* to work. We are at the beta test compose stage, which most people interpret to mean something close to feature complete. Combine this with the fact there's no indication in the UI (that I could discern) of support for existing RAID arrays or LVM VGs, and I don't believe it's at all unreasonable to wonder if this functionality is simply being removed. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: f18: how to install into a LVM partitions (or RAID)
On 10/18/2012 05:02 PM, Adam Williamson wrote: I'm not sure what 'indication' you're expecting, exactly. AIUI, existing RAID arrays and VGs should just show up in the list of existing filesystems on the left-hand side of the custom partitioning screen. (In a recent enough Beta TC, of course, Alpha is ancient stuff now). If they don't, that's a bug. Do you have a case where they don't? If so, it should just be reported as a bug. They didn't the last time I checked, which I believe was beta TC2. Just checked again in a test VM and I don't see any way to use the free space in the existing VG. (vgdisplay reports 7.74 GiB free of 19.48 GiB.) On the left hand side, I see: - New Fedora 18-Beta-TC2 Installation You haven't created any mount points for your Fedora 18-Beta-TC2 installation yet: Click here to create them automatically Or, create new mount points below with the '+' icon. - CentOS Linux 6.3 for x86_64 DATA SYSTEM Root7.92 GB / Swap 4.09 GB - Unknown Unknown 19.97 GB Unknown498 MB Unknown 19.97 GB When I attempt to add a 6GB mount point for /, I get a not enough free space on disks error. So how's it supposed to work? -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: f18: how to install into a LVM partitions (or RAID)
On 10/16/2012 08:29 AM, Dario Lesca wrote: How to install it on a empty disk and use LVM (or create a software RaID)? I don't believe it's currently possible. Nor is it possible to use space in existing VGs or RAID devices. It's unclear whether F18 final is going to include this functionality or not. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Plans for anaconda LVM/RAID support
I'm sure that this information is somewhere on the Fedora Wiki, but my search-fu apparently isn't up to the task of finding it. What are the plans for LVM and/or software RAID support? Currently (F18 Beta TC2), it seems to be impossible for those of us who have fully allocated our storage to either (or both) of these technologies to install Fedora 18 at all. Thanks! -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn, or die trying -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: configuration files created by Anaconda exclusively
+1 to Jan's point. It should be possible to recover a critical file (or at least a skeleton thereof) by reinstalling the owning RPM. -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: default DNS caching name server on Fedora ?
On 07/06/2012 10:54 AM, Jesse Keating wrote: If dnsmasq is already running, NM will probably not mess with it. Try disabling it from start at boot and allow NM to manage the process. If dnsmasq is running and listening on 127.0.0.1, the dnsmasq instance started by NetworkManager will fail to start, and NetworkManager will operate normally. (I.e. it won't use the dnsmasq plugin.) If you want to run an instance of dnsmasq for some other purpose (to provide DNS and DHCP for a virtual network, for example) you need to make sure that it isn't listening on 127.0.0.1. -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: default DNS caching name server on Fedora ?
On 06/20/2012 12:06 PM, Jesse Keating wrote: So I just gave this a try. Already had dnsmasq installed so I just edited the config file and restarted the NetworkManager service. Then connected to my VPN. It. Just. Works. Amazing! Not only does it just work for resolution, but it also works for multiple search domains. I can ping name and it'll try name.localdomain and I can also do name.subname and it'll find it at name.subname.workdomain. A+ Double-plus awesome! -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 17 Alpha status: open blockers, karma requests and blocker/NTH vote requests
On 02/19/2012 01:32 AM, Adam Williamson wrote: On Sat, 2012-02-18 at 19:54 -0600, Ian Pilcher wrote: This actually wasn't a problem during my (very brief) attempt to install RC2. X was pretty obviously spanning both displays, but anaconda was only using a smaller region (1024x768?) of one of the displays. Could you see the Next buttons, though? For many people, anaconda *mostly* renders on one screen or the other, but the buttons wind up on the _other_ screen, or not present on either screen. Yup. The entire anaconda display area, buttons and all, didn't even take up all of one 1680x1050 screen. -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 17 Alpha status: open blockers, karma requests and blocker/NTH vote requests
On 02/17/2012 10:44 PM, Adam Williamson wrote: 8. http://bugzilla.redhat.com/show_bug.cgi?id=725219 - anaconda should run in clone not span mode This is a Greatest Hit, just waiting on some kind of a code fix from anaconda / X developers. This actually wasn't a problem during my (very brief) attempt to install RC2. X was pretty obviously spanning both displays, but anaconda was only using a smaller region (1024x768?) of one of the displays. -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Please create Fedora 17 in Bugzilla
Anaconda in Fedora 17 Alpha RC2 cannot upload tracebacks to Bugzilla, because Bugzilla doesn't think Fedora 17 exists. Is it carved into a stone tablet somewhere that we have to do this dance for every release? -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Please create Fedora 17 in Bugzilla
On 02/16/2012 01:11 PM, Bill Nottingham wrote: Ian Pilcher (arequip...@gmail.com) said: Anaconda in Fedora 17 Alpha RC2 cannot upload tracebacks to Bugzilla, because Bugzilla doesn't think Fedora 17 exists. Done. Thank you! -- Ian Pilcher arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel