Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Tuesday, March 19, 2024 9:22:23 AM EDT Allan via devel wrote: > > OK, but how do I run kwin-x11 instead of -wayland? > > You need plasma-workspace-x11 too. Thanks. That did it. -- Garry T. Williams -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Monday, March 18, 2024 4:46:01 PM EDT Sérgio Basto wrote: > On Mon, 2024-03-18 at 16:17 -0400, Garry T. Williams wrote: > > On Wednesday, February 7, 2024 4:06:46 AM EDT Kevin Kofler via devel > > wrote: > > > Garry T. Williams wrote: > > > > I hope my report can be resolved before I am forced to use > > > > Wayland. > > > > > > You will not be forced to use Wayland. Stay tuned. > > > > In an effort to test a Wayland bug I reported upstream, I upgraded my > > laptop to f40. (I am holding off on upgrading my workstation.) My > > reported bug is still there, but here I am without x11. I installed > > kwin-x11. My login screen no longer offers to run it instead of > > kwin-wayland. Is there a way to run x11 on f40? (There are still > > several annoying bugs in Wayland that I would like to avoid.) > > "kwin-wayland replaces kwin-x11 , on upgrade" → When upgrading to > Fedora 40 > > you may reinstall the package, it will not be obsoleted anymore. > > I don't agree with this behavior OK, but how do I run kwin-x11 instead of -wayland? -- Garry T. Williams -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Wednesday, February 7, 2024 4:06:46 AM EDT Kevin Kofler via devel wrote: > Garry T. Williams wrote: > > I hope my report can be resolved before I am forced to use Wayland. > > You will not be forced to use Wayland. Stay tuned. In an effort to test a Wayland bug I reported upstream, I upgraded my laptop to f40. (I am holding off on upgrading my workstation.) My reported bug is still there, but here I am without x11. I installed kwin-x11. My login screen no longer offers to run it instead of kwin-wayland. Is there a way to run x11 on f40? (There are still several annoying bugs in Wayland that I would like to avoid.) -- Garry T. Williams -- ___ 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: Donate 1 minute of your time to test upgrades from F39 to F40
On Wednesday, February 21, 2024 2:11:49 AM EST Miroslav Suchý wrote: > Do you want to make Fedora 40 better? Please spend 1 minute of your time and > try to run: > > dnf --releasever=40 --setopt=module_platform_id=platform:f40 \ > --enablerepo=updates-testing \ > $(rpm -q fedora-repos-modular >/dev/null && echo > --enablerepo=updates-testing-modular) \ > --assumeno distro-sync No problem on my Dell workstation. But on my Dell XPS-13 laptop I get: Error: Problem 1: package audiocd-kio-libs-16.08.3-21.fc39.x86_64 from @System requires audiocd-kio = 16.08.3-21.fc39, but none of the providers can be installed - audiocd-kio-16.08.3-21.fc39.x86_64 from @System does not belong to a distupgrade repository - problem with installed package audiocd-kio-libs-16.08.3-21.fc39.x86_64 Problem 2: package ktp-accounts-kcm-23.04.3-2.fc39.x86_64 from @System requires kaccounts-integration(x86-64) >= 23.04, but none of the providers can be installed - kaccounts-integration-23.08.5-1.fc39.x86_64 from @System does not belong to a distupgrade repository - problem with installed package ktp-accounts-kcm-23.04.3-2.fc39.x86_64 Problem 3: package network-scripts-ppp-2.5.0-3.fc39.x86_64 from @System requires network-scripts, but none of the providers can be installed - network-scripts-10.20-1.fc39.x86_64 from @System does not belong to a distupgrade repository - problem with installed package network-scripts-ppp-2.5.0-3.fc39.x86_64 Problem 4: package network-scripts-teamd-1.32-4.fc40.x86_64 from fedora requires network-scripts, but none of the providers can be installed - problem with installed package network-scripts-teamd-1.32-1.fc39.x86_64 - package network-scripts-10.20-1.fc39.x86_64 from @System requires initscripts(x86-64) = 10.20-1.fc39, but none of the providers can be installed - network-scripts-teamd-1.32-1.fc39.x86_64 from @System does not belong to a distupgrade repository - initscripts-10.20-1.fc39.x86_64 from @System does not belong to a distupgrade repository (try to add '--skip-broken' to skip uninstallable packages) -- Garry T. Williams -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Tuesday, 30 January 2024 08:07:25 EST Richard W.M. Jones wrote: > On Tue, Jan 30, 2024 at 12:47:44PM +, Sérgio Basto wrote: > > Link to the FESCo ticket: https://pagure.io/fesco/issue/3165 > > > > and I'm very upset > > Assume best intent first of all. I quit trying to use Wayland a long time ago because of the various bugs. When I saw this thread, I decided I better get ready and logged out/in Plasma Wayland. OK, I can live with windows that don't remember their geometry from last session. And I don't really have to have that last session remembered and restored. But... I went to compose an E-mail message using kmail and its composer window and noticed it was broken.[*] I couldn't even find a bug report about this. I fear it's because many others just ignored the various bugs and went back to using X11. I hope my report can be resolved before I am forced to use Wayland. I understand that I am late to the party because I just ignored this for so long. _ [*] https://bugs.kde.org/show_bug.cgi?id=480984 -- Garry T. Williams -- ___ 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: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)
On Friday, April 29, 2022 5:49:05 PM EDT Ben Cotton wrote: > Cryptographic policies will be tightened in Fedora 38-39, > SHA-1 signatures will no longer be trusted by default. > Fedora 37 specifically doesn't come with any change of defaults, > and this Fedora Change is an advance warning filed for extra visibility. > Test your setup with FUTURE today and file bugs so you won't get bit > by Fedora 38-39. [snip] In case you want some feedback, > Install crypto-policies-scripts package and switch to a more restrictive > policy > with either `update-crypto-policies --set FUTURE` > or `update-crypto-policies --set TEST-FEDORA39`. > > Proceed to use the system as usual, > identify the workflows which are broken by this change. I did that and several days later I did: $ sudo dnf upgrade --enablerepo=updates-testing Errors during downloading metadata for repository 'fedora': - Curl error (60): SSL peer certificate or SSH remote key was not OK for https://mirrors.fedoraproject.org/metalink?repo=fedora-36=x86_64=3 [SSL certificate problem: CA certificate key too weak] - Curl error (60): SSL peer certificate or SSH remote key was not OK for https://mirrors.fedoraproject.org/metalink?repo=fedora-36=x86_64 [SSL certificate problem: CA certificate key too weak] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (60): SSL peer certificate or SSH remote key was not OK for https://mirrors.fedoraproject.org/metalink?repo=fedora-36=x86_64 [SSL certificate problem: CA certificate key too weak] > Verify that the broken functionality works again > if you the policy is relaxed back > with, e.g., `update-crypto-policies --set FUTURE:SHA-1`, This was a problem: $ sudo update-crypto-policies --set FUTURE:SHA-1 Unknown policy `SHA-1`: file `SHA-1.pmod` not found in (., policies/modules, /etc/crypto-policies/policies/modules, /usr/share/crypto-policies/policies/modules) That seems like a typo. After looking in /usr/share/crypto-policies/policies/modules, I tried again with: $ sudo update-crypto-policies --set FUTURE:SHA1 Setting system policy to FUTURE:SHA1 But that didn't get me back. I got the same error doing dnf upgrade. I had to do: $ sudo update-crypto-policies --set DEFAULT to get back to dnf working again. > file bug reports against the affected components if not filed already. I really don't know what "component" to use filing a bug. -- Garry T. Williams ___ 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
swtpm Fails to Upgrade After system-upgrade F36
After upgrading to f36, a dnf upgrade resulted in 156 packages to upgrade, including swtpm. This resulted in the following errors: ... Upgrading: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64 159/315 error: lsetfilecon: (/usr/bin/swtpm;6249a295, system_u:object_r:swtpm_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64 Cleanup : libvirt-8.0.0-3.fc36.x86_64160/315 error: unpacking of archive failed on file /usr/bin/swtpm;6249a295: cpio: (error 0x2) error: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64: install failed Running scriptlet: libvirt-daemon-driver-storage-8.0.0-3.fc36.x86_6 161/315 ... Running scriptlet: libvirt-daemon-8.1.0-2.fc36.x86_64 314/315 error: swtpm-0.7.2-1.20220307git21c90c1.fc35.x86_64: erase skipped Running scriptlet: libvirt-daemon-driver-storage-core-8.1.0-2.fc36. 314/315 ... Failed: swtpm-0.7.2-1.20220307git21c90c1.fc35.x86_64 swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64 Error: Transaction failed So it looks like this same package failed to upgrade originally during the `sudo dnf system-upgrade reboot` transaction. (This is a headless system and I did not review the dnf logs after the upgrade.) I see nothing reported in bugzilla, so: https://bugzilla.redhat.com/show_bug.cgi?id=2071413 -- Garry T. Williams ___ 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: Orphaning some of my packages
On Sunday, March 6, 2022 4:13:26 AM EDT Dan Callaghan wrote: > I've decided to orphan all the packages > which I no longer use: ... > linenoise I am taking this one. -- Garry T. Williams ___ 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: Make pkexec and pkla-compat optional (Self-Contained Change proposal)
On Wednesday, February 16, 2022 6:01:48 PM EST Adam Williamson wrote:
> I just tried this, actually, for giggles. Two reasons it's a non-
> starter: it prompts for the root password, not for my user password
> (my user is an 'admin' so far as sudo etc. are concerned, but
> apparently not an 'admin' so far as interactive pkexec is
> concerned).
That is odd. I am never prompted for the root password for anything.
Maybe this is a policy difference between GNOME and KDE.
My supplemental groups:
wheel mock systemd-journal wireshark
> I do not know the root password, it is intentionally a
> 24-character random string I would have to look up. And it prompts
> with one of those goddamn 'secure' GNOME popovers which prevents you
> accessing your password manager, so every time you hit one, you have
> to cancel it, go to your password manager, copy the password it
> wants, then trigger it again.
>
> No way on earth I'm using that.
Again, in KDE, there is a prompt for MY password and it is only modal
as far as the pkexec command is concerned. I can open my password
manager before responding to the prompt (not that I need to, since it
wants my password -- not root's).
Anyway, until this discussion, I never knew there was a pkexec. I
note that pkexec will not operate correctly outside of my KDE session.
It prompts for my password from a terminal session and then fails with
$ pkexec ls
AUTHENTICATING FOR org.freedesktop.policykit.exec
Authentication is needed to run `/usr/bin/ls' as the super user
Authenticating as: Garry T. Williams (garry)
Password:
polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
AUTHENTICATION FAILED
Error executing command as another user: Not authorized
This incident has been reported.
$
Of course, sudo will operate correctly without a desktop session. I
don't think I will be eager to use pkexec instead of sudo.
--
Garry T. Williams
___
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: Self Introduction: Garry Williams
On Sunday, January 16, 2022 5:31:41 PM EST Sebastian Crane wrote: > Welcome to Fedora! The Bridge Hand Generator looks really > interesting. I've been meaning to learn Bridge; now I'll be able to > have computer-assistance for at least the dealing aspect! Thank you for the warm welcome, Sebastian. You will never regret learning the game of bridge. I encourage you to give it a try. -- Garry T. Williams ___ 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
Self Introduction: Garry Williams
Greetings, I'm Garry Williams and I recently retired from a software development job and now want to spend more time contributing to Fedora. My developer experience started in the late sixties with IBM S/370 Assembler. I had various jobs programming and software support of IBM MVT and MVS operating systems, mostly with Amdahl Corporation. After that I started working with Unix and Solaris 2.6 in the late nineties. My first Linux experience was Red Hat Linux 5.2 (if I remember correctly :-). Later I used Mandrake, later still Mandriva after that and came to Fedora with Fedora Core 5. I've used Fedora ever since for my personal machines. My last job (Comcast) involved development of Web-based services and applications that deployed on Debian machines in various company data centers around the US. I have not contributed much aside from regular bug reports and a few PRs here and there over the years. In my spare time, I am an avid bridge player. That brings me to a simple package I have prepared, deal - a Bridge Hand Generator. My review request is: https://bugzilla.redhat.com/show_bug.cgi?id=2040118 -- Garry T. Williams ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Plocate as the default locate implementation (Self-Contained Change proposal)
On Wednesday, December 1, 2021 9:10:33 AM EST Jonathan Wakely wrote: > Also, the plocate-updatedb service was not started after installing > it, so I can't use locate until the DB is created. Is that expected? > Does it wait until the timer runs it? I believe that is normal. Earlier releases of mlocate were never enabled to run -- I always had to enable (the timer) and start them. -- Garry T. Williams ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Plocate as the default locate implementation (Self-Contained Change proposal)
On Tuesday, November 23, 2021 4:53:12 PM EST Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Nov 23, 2021 at 01:52:43PM -0500, Chris Murphy wrote: > > I'm definitely noticing a difference. I'm not sure it was ever correct > > that updatedb.conf was pruning bind mounts on Fedora. It's not the > > mlocate default, but it is what Fedora has been using for years > > (defacto default on Fedora). > > That's a known-fixed bug. Not fixed as far as I know[*]. I've been patching my /etc/updatedb.conf ever since I installed with btrfs. (The second time I installed with btrfs, f33, that is. Not years ago. :-)) This change does render the bug moot, though. Nice. _ [*] The bug claims a fix for Silverblue, but not Fedora Workstation or KDE. -- Garry T. Williams ___ 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
Excessive Messages In Journal From pipewire
This seems obnoxious: Aug 03 17:24:24 pipewire[3007]: 1 events suppressed Aug 03 17:24:24 pipewire[3007]: (speech-dispatcher-espeak-ng-54) client too slow! rate:256/48000 pos:968996864 status:triggered Aug 03 17:24:24 pipewire[3007]: (speech-dispatcher-dummy-60) client too slow! rate:256/48000 pos:968996864 status:triggered Aug 03 17:24:24 pipewire-pulse[3008]: (speech-dispatcher-dummy-0) client missed 1 wakeups Aug 03 17:24:29 pipewire[3007]: 1 events suppressed Aug 03 17:24:29 pipewire[3007]: (bluez_output.00_0D_44_DE_D4_EA.a2dp-sink-48) client too slow! rate:256/48000 pos:969237504 status:triggered Aug 03 17:24:29 pipewire[3007]: (bluez_output.00_0D_44_DE_D4_EA.a2dp-sink-48) client too slow! rate:256/48000 pos:969237504 status:triggered Aug 03 17:24:29 pipewire[3007]: (bluez_output.00_0D_44_DE_D4_EA.a2dp-sink-48) client missed 2 wakeups Aug 03 17:24:29 pipewire-pulse[3008]: (speech-dispatcher-dummy-0) client missed 1 wakeups Aug 03 17:24:29 pipewire-media-session[3014]: (bluez_output.00_0D_44_DE_D4_EA.a2dp-sink-19) client missed 1 wakeups $ journalctl -b|grep -c 'client too slow!' 7798 $ rpm -qa|grep pipewire pipewire-libs-0.3.32-1.fc34.x86_64 pipewire-0.3.32-1.fc34.x86_64 pipewire-alsa-0.3.32-1.fc34.x86_64 pipewire-pulseaudio-0.3.32-1.fc34.x86_64 pipewire-jack-audio-connection-kit-0.3.32-1.fc34.x86_64 $ uptime 17:31:17 up 5:45, 4 users, load average: 0.62, 0.77, 0.85 $ Anyone know how to turn this off? -- Garry T. Williams ___ 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: Fedora 34 Change: DNF/RPM Copy on Write enablement for all variants (System-Wide Change)
On Tuesday, December 22, 2020 4:54:34 PM EST Matthew Almond via devel wrote: > > I currently download once and upgrade three different systems by > > rsync-ing the cache. > > > > Do I understand that this will no longer be supported or work? > > That's an interesting question. Is sharing the cache directory from > a single host intended to be shared like this? I am guessing no, but > it may still be common. > > It should still work, with two caveats: > 1. The files in the cache will be bigger, so a simple rsync will > involve more I/O, and the destination filesystem will also need more > space and I/O time. > 2. The systems must be the same endianness (The transcoded format > doesn't bother with network order, because it's not intended to be > shared) > 3. The page size must be the same for reflinking to work: This is > actually worked out when the filesystem is created, and defaults to > the system page size, and if not the same as the current page size, > the filesystem isn't even guaranteed to mount (see --sectorsize > option in mkfs.btrfs man page). > > In reality you're quite unlikely to share packages unless the > architecture were the same, which would steer both endianness and > page size to the same value. That said, I'm aware that aarch64 can > be flexible in both ways. I'm covering my bases with my statement: I > have thought about it, and don't think I'm in any position to make > promises. > > For this proposal: we're talking about shipping the code that would > allow this to be turned on. We're not talking about enabling it by > default. We can't until we have good answers to questions like this. Understood. To be clear, all three systems are x86_64, identical endianness, architecture, and page size (as far as I know). Also, this isn't a big deal, really. I just wanted to reduce network bandwidth without operating a local mirror. ___ sudo rsync -a --password-file=/etc/rsync.password --delete rsync://rsync@vfr/dnf /var/cache/dnf;sudo dnf --enablerepo=updates-testing upgrade -- Garry T. Williams ___ 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 34 Change: DNF/RPM Copy on Write enablement for all variants (System-Wide Change)
On Monday, December 21, 2020 11:28:51 AM EST Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/RPMCoW [snip] > # The file format for RPMs is different with Copy on Write. The > headers are identical, but the payload is different. There is also a > footer. > ## Files are converted (“transcoded”) locally during download using > /usr/bin/rpm2extents (part of rpm codebase). The format > is not intended to be “portable” - i.e. copying the files from the > cache is not supported. I currently download once and upgrade three different systems by rsync-ing the cache. Do I understand that this will no longer be supported or work? -- Garry T. Williams ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 33 System-Wide Change proposal: Make btrfs the default file system for desktop variants
On Saturday, 27 June 2020 17:29:23 EDT Chris Murphy wrote: > For btrfs, it is either 'single' or 'raid0' profile for data, but > 'raid1' for metadata (the file system itself). > > I need to test it or maybe someone beats me to it by looking at the > code. But either way it's equal to or better than the current default. I just did that install (KDE) and it was raid0 for data (raid1 for metatdata). I switched to raid1 for data as soon as I noticed what had happened. -- Garry T. Williams ___ 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: Is there a way to allow changing permissions of an rpm tmpfile dir?
On Wednesday, June 3, 2020 11:05:39 PM EDT Orion Poplawski wrote:
> The clamd package ships a default service (clamd@scan) with the
> following configuration:
>
> /usr/lib/tmpfiles.d/clamd.scan.conf:
> d /run/clamd.scan 0710 clamscan virusgroup
>
> %files -n clamd
> %ghost %dir %attr(0710,clamscan,virusgroup) /run/clamd.scan
> %ghost /run/clamd.scan/clamd.sock
>
> Now, a user might want to change the mode and group of the
> /run/clamd.scan directory to suit their purposes. They can do this by
> creating an /etc/tmpfiles.d/clamd.scan.conf file. But the next time a
> clamd update comes along rpm will reset the permissions of
> /run/clamd.scan until the next reboot.
Actually, systemd does not override the administrator's directory,
/etc.
From https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html
"Files in /etc/tmpfiles.d override files with the same name in
/usr/lib/tmpfiles.d and /run/tmpfiles.d."
--
Garry T. Williams
___
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+Lenovo
On Thursday, April 30, 2020 5:18:10 PM EDT Mark Pearson wrote: > He also suggested I take questions from the community I Mark. Which Lenovo model do I want to replace my XPS-13? -- Garry T. Williams ___ 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: Enable dmarc mitigations
On Sunday, May 5, 2019 3:43:02 PM EDT stan via devel wrote: > On Sun, 5 May 2019 14:19:59 +0200 > Vitaly Zaitsev via devel wrote: > > Hello, qrsBRWN. > > > > Sun, 05 May 2019 10:57:06 +0200 you wrote: > > > > > Exactly what platform did you have in mind? > > > > Discourse[1] for example. GTK developers already testing it[2] as > > mailing lists replacement. > > > > 1: https://github.com/discourse/discourse > > 2: https://blog.gtk.org/2019/03/05/testing-discourse-for-gtk/ [snip] > If forced to, I could probably use it, but I prefer the push model > to the pull model. That is, it isn't an improvement for me, it > doesn't buy me anything I want. +1 -- Garry T. Williams ___ 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: Donate 1 minute of your time to test upgrades from F29 to F30
On Thursday, February 28, 2019 4:22:51 AM EDT Miroslav Suchý wrote: > Do you want to make Fedora 30 better? Please spend 1 minute of your time and > try to run: > > sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 > --enablerepo=updates-testing distro-sync garry@ifr$ sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 --enablerepo=updates-testing distro-sync [sudo] password for garry: Fedora 30 openh264 (From Cisco) - x86_64 1.3 kB/s | 542 B 00:00 Fedora 30 openh264 (From Cisco) - x86_64 160 kB/s | 1.6 kB 00:00 Importing GPG key 0xCFC659B9: Userid : "Fedora (30) " Fingerprint: F1D8 EC98 F241 AAF2 0DF6 9420 EF3C 111F CFC6 59B9 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-30-x86_64 Is this ok [y/N]: y Fedora 30 openh264 (From Cisco) - x86_64 6.4 kB/s | 5.1 kB 00:00 Fedora 30 - x86_64 - Test Updates4.3 MB/s | 14 MB 00:03 Fedora 30 - x86_64 - Updates 98 kB/s | 18 kB 00:00 Fedora 30 - x86_64 3.1 MB/s | 54 MB 00:17 google-chrome 35 kB/s | 1.3 kB 00:00 google-chrome 46 kB/s | 3.4 kB 00:00 Copr repo for qt5-qtbase-print-dialog-advanced o 112 kB/s | 100 kB 00:00 RPM Fusion for Fedora 30 - Free - Updates 68 kB/s | 71 kB 00:01 Failed to synchronize cache for repo 'rpmfusion-free-updates' RPM Fusion for Fedora 30 - Free 1.1 MB/s | 737 kB 00:00 RPM Fusion for Fedora 30 - Nonfree - Updates 185 kB/s | 71 kB 00:00 Failed to synchronize cache for repo 'rpmfusion-nonfree-updates' RPM Fusion for Fedora 30 - Nonfree 148 kB/s | 227 kB 00:01 Visual Studio Code20 kB/s | 2.9 kB 00:00 Visual Studio Code 203 kB/s | 2.1 MB 00:10 Ignoring repositories: rpmfusion-free-updates, rpmfusion-nonfree-updates Error: Problem 1: package python2-cinderclient-3.5.0-1.fc29.noarch requires python2-oslo-i18n >= 3.15.3, but none of the providers can be installed - python2-oslo-i18n-3.19.0-1.fc29.noarch does not belong to a distupgrade repository - problem with installed package python2-cinderclient-3.5.0-1.fc29.noarch Problem 2: problem with installed package mongodb-4.0.3-3.fc29.x86_64 - package mongodb-4.0.3-3.fc30.x86_64 requires libboost_filesystem.so.1.66.0()(64bit), but none of the providers can be installed - mongodb-4.0.3-3.fc29.x86_64 does not belong to a distupgrade repository - boost-filesystem-1.66.0-14.fc29.x86_64 does not belong to a distupgrade repository Problem 3: problem with installed package mongodb-server-4.0.3-3.fc29.x86_64 - package mongodb-server-4.0.3-3.fc30.x86_64 requires libboost_program_options.so.1.66.0()(64bit), but none of the providers can be installed - mongodb-server-4.0.3-3.fc29.x86_64 does not belong to a distupgrade repository - boost-program-options-1.66.0-14.fc29.x86_64 does not belong to a distupgrade repository (try to add '--skip-broken' to skip uninstallable packages) garry@ifr$ Perhaps mondodb is not upgradable? -- Garry T. Williams ___ 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: Cannot Boot After Doing system-upgrade
On Saturday, October 13, 2018 7:34:44 PM EDT Chris Murphy wrote: > Good catch. It's vaguely possible there's a bug in either shim 15-5 > or grub2-efi 2.02-58 as it relates to your firmware, that caused > it to silently fail, and the firmware did a fallback to the 2nd > BootOrder, which is the Ubuntu entry. I want to emphasize that it was *not* boot order that changed. I manually attempted to boot Fedora, but it failed (oh how I wish I had paid attention to the details). Anyway, I can manually change the boot order to either OS and it respects my change. My problem was something else entirely since a manual change didn't boot Fedora. I may try the manual downgrade, if I get time. I am usually physically away from this system so I will retrieve the old versions and be ready when I can get the time. Again, thank you for your thoughtful follow-ups. -- Garry T. Williams ___ 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: Cannot Boot After Doing system-upgrade
By the way, from the journal during the dnf system-upgrade reboot: Sep 30 10:02:27 vfr dnf[831]: grub2-common.noarch 1:2.02-58.fc29 Sep 30 10:02:27 vfr dnf[831]: grub2-efi-x64.x86_64 1:2.02-58.fc29 Sep 30 10:02:27 vfr dnf[831]: grub2-pc.x86_64 1:2.02-58.fc29 Sep 30 10:02:27 vfr dnf[831]: grub2-pc-modules.noarch 1:2.02-58.fc29 Sep 30 10:02:27 vfr dnf[831]: grub2-tools.x86_64 1:2.02-58.fc29 Sep 30 10:02:27 vfr dnf[831]: grub2-tools-efi.x86_64 1:2.02-58.fc29 Sep 30 10:02:27 vfr dnf[831]: grub2-tools-extra.x86_64 1:2.02-58.fc29 Sep 30 10:02:27 vfr dnf[831]: grub2-tools-minimal.x86_64 1:2.02-58.fc29 Sep 30 10:02:28 vfr dnf[831]: shim-x64.x86_64 15-5 And now: garry@vfr$ rpm -q grub2-common grub2-efi-x64 grub2-pc grub2-pc-modules grub2-tools grub2-tools-efi grub2-tools-extra grub2-tools-minimal shim-x64 grub2-common-2.02-62.fc29.noarch grub2-efi-x64-2.02-62.fc29.x86_64 grub2-pc-2.02-62.fc29.x86_64 grub2-pc-modules-2.02-62.fc29.noarch grub2-tools-2.02-62.fc29.x86_64 grub2-tools-efi-2.02-62.fc29.x86_64 grub2-tools-extra-2.02-62.fc29.x86_64 grub2-tools-minimal-2.02-62.fc29.x86_64 shim-x64-15-7.x86_64 garry@vfr$ -- Garry T. Williams ___ 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: Cannot Boot After Doing system-upgrade
On Saturday, October 13, 2018 5:42:15 PM EDT Chris Murphy wrote: > On Sat, Oct 13, 2018 at 1:30 PM, Garry T. Williams > wrote: > > On Saturday, October 13, 2018 3:12:44 PM EDT Samuel Sieb wrote: > >> On 10/13/18 10:39 AM, Garry T. Williams wrote: > >> > >> > What am I doing wrong here that I cannot boot after a > >> > system-upgrade? > >> > >> "Doesn't boot" is no information. What exactly is happening? > > > > Sorry, the boot record is gone. > > You determined this how? The machine did not boot the Fedora OS. Instead, it booted the OS on /dev/sda. Of course, I attempted to boot from the Fedora disk by using the boot device configuration screen by hitting F12 during reboot. This failed. (A photograph of the error would have been a good idea.) I assumed that the reason was the boot record was missing. > >I happen to have another system on > > > > the same machine and that system boots instead of the Fedora > > system before my recovery actions. When I forced a boot from > > the fedora system using the machine's boot selection screen, it > > fails. (No diagnostic information in the BIOS setup screen -- > > just won't boot. I was forced to specify the USB Live system to > > start a recovery.) > > Screen shots or cell photo of the failure might be useful because > failure/won't boot doesn't tell us what is happening. And what is > happening is a hint as to what the source of the problem is, how to > prevent it, and how to fix it. But "won't boot" is not much to go > on. Understood. > Is this BIOS or UEFI? From any other Linux, what do you get for > 'parted -l u s p' or "fdisk -l" ? And what do you get for > 'efibootmgr -v' ? This is useful. I will try to document these results when I upgrade to F30, if the same happens again. The fdisk -l did show what I expected it to show: Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 4B21E327-DFE8-4105-AA9B-FEFF8AE8439F Device StartEnd Sectors Size Type /dev/sda1 20481026047 1024000 500M EFI System /dev/sda210260487317503 6291456 3G Microsoft basic data /dev/sda37317504 933572607 926255104 441.7G Linux filesystem /dev/sda4 933572608 1000214527 66641920 31.8G Linux swap Disk /dev/sdb: 477 GiB, 512110190592 bytes, 1000215216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 9114D615-2FD0-4CF1-A601-DAD4507F6254 Device StartEnd Sectors Size Type /dev/sdb1 2048 411647409600 200M EFI System /dev/sdb2 4116482508799 2097152 1G Linux filesystem /dev/sdb3 2508800 1000214527 997705728 475.8G Linux LVM Admittedly, this is output from the now-recovered system, but I can attest that the same was displayed when the command was done using the Ubuntu system that loaded from /dev/sda. > > The system-upgrade somehow wiped out my boot record on /dev/sdb. > > "boot record" is a BIOS term, so this could mean the code on LBA 0 > or in the MBR gap or BIOS Boot partition has been stepped on; but > dnf system upgrade doesn't have such an ability. In fact it's a bit > of a security and bug endurance problem that 'grub2-install' isn't > run on BIOS upgrades. Whereas on UEFI the bootloader binaries on > the EFI System partition are replaced during updates, so what > you're describing might be a GRUB bug. OK, the system was able to boot from /dev/sdb only after I reinstalled grub2-efi and shim. I assumed that was what restored the boot record (or whatever it's called). (I was able to boot normally from Fedora immediately before doing the dnf system-upgrade. A reinstall was not accepted by dnf, so I used update instead.) > But the details you're giving only lead to speculation so you need > to provide specifics, just won't boot is identical to what happens > to a computer without a drive at all. Well, I will not be so fast to restore, if it occurs again (f30). Thank you for your suggestions. I am sorry for the assumptions I made. For what it's worth now: garry@vfr$ efibootmgr -v BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0002,,0003,0004,0005,0006,0007,0008,0009 Boot ubuntuHD(1,GPT,3252a9ab-23eb-4fd4-9d11-6dc13c6f50ec, 0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi) Boot0002* FedoraHD(1,GPT,0534ef43-afb9-409c-8dc8-a1eff1e396ef, 0x800,0x64000)/File(\EFI\fedora\shim.efi) Boot0003* UEFI: SanDisk Extreme 0001PciRoot(0x0)/Pci(0x14,0x0)/ USB(17,0)/HD(1,MBR,0x3cb5dbe1,0x16960,0x
Re: KDE print dialog does not see CUPS settings
On Sunday, February 11, 2018 7:39:33 PM EST Kevin Kofler wrote: > I have built qt5-qtbase with these backported patches in a Copr: > https://copr.fedorainfracloud.org/coprs/kkofler/qt5-qtbase-print-dialog-advanced/ Thank you, Kevin. That was an annoying bug so *big* thanks -- it works just fine. -- Garry T. Williams ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
System Upgrade F26 -> F27 Fails
System upgrade re-boot fails with Error in `/usr/libexec/system-python' free() invalid pointer Upgrade failed at reboot. System rebooted to F26 successfully. I did two other systems without any problems. https://bugzilla.redhat.com/show_bug.cgi?id=1499101 -- Garry T. Williams ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Ramblings and questions regarding Fedora, but stemming from gnome-software and desktop environments
On 12-28-14 11:46:09 Michael Catanzaro wrote: One more note here: if you try to run a command line program that isn't installed, PackageKit will search for it in all enabled repos, offer to install it for you if found, and then run the command. No real need when you can do: $ sudo dnf install /usr/bin/missing-executable (I erased PackageKit. :) -- Garry T. Williams -- 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: Fedora Installation Needs Intelligence
On 12-12-14 08:25:56 Jan Kratochvil wrote: On Fri, 12 Dec 2014 08:17:45 +0100, Satyajit Sahoo wrote: Wireless is a requirement for laptops. For example, Macbook Air doesn't have an ethernet port. s/requirement for laptops/requirement for Macbook Air/ Well, my Dell XPS-13 didn't come with an Ethernet port either. (Yes, I bought a dongle, but just sayin'.) -- Garry T. Williams -- 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: Dash as default shell
On 10-2-14 10:01:45 Rahul Sundaram wrote:
On Thu, Oct 2, 2014 at 9:56 AM, Miroslav Suchý wrote:
On 10/02/2014 04:39 AM, Rahul Sundaram wrote:
Is it worth considering using Dash as the default (non-interactive) shell
in Fedora?
Why starting with changing target of /bin/sh?
Can we start with smaller step?
Like put in Packing Guidelines, that authors and maintainers of
non-interactive shell scripts should use
#!/usr/bin/dash
I don't think we need all scripts to do this. Using sh when you are
not relying on any bash specific features is just fine. Arch Linux
wiki suggests:
$checkbashisms -f -p $(grep -rlE '^#! ?/bin/(env )?sh' /usr/bin)
$ (checkbashisms -f -p $(grep -rlE '^#! ?/bin/(env )?sh' /usr/bin) ) 21
/dev/null|grep 'possible bashism'|awk '{print $4}'|sort -u|wc -l
113
$
Many of these trigger multiple warnings from checkbashisms. The total
here was 717. (Fedora 20, KDE.)
--
Garry T. Williams
--
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: Save everybody some surprises in Fedora 22!
On 6-6-14 14:46:23 Ales Kozumplik wrote: We're wondering: is there stuff people are still missing from DNF The --advisory option. -- Garry T. Williams -- 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: F21 System Wide Change: Workstation: Disable firewall
On 4-15-14 11:55:17 Reindl Harald wrote: short ago it was proposed drop tcpwrapper from the distribution because there is a firewall and we should rely on a sinle layer of defense followed directly by oh and now let us disable that security layer in a default install +1 -- Garry T. Williams -- 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: Five Things in Fedora This Week (2014-04-01)
On 4-1-14 16:11:45 Matthew Miller wrote: 5tFTW note -- This is the third installment of this series, and I'm still calibrating a few things. I'm aiming at a wide audience, but I'm not quite sure how much explaining I should do of general Fedora knowledge. Is it helpful for me to (as above), give a quick explanation when I talk about Rawhide, Flock, or FESCo? Or, does that just increase the word count for no reason? Let me know. I'm not a Fedora packager or developer, but I follow this devel list pretty carefully. I think, given that you are aiming at a wide audience, you have struck just the right balance. Keep it up. Thank you for these. -- Garry T. Williams -- 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: dnf-0.4.13
On 2-6-14 17:44:11 Ales Kozumplik wrote: We ship Delta RPM support What a pleasant surprise on a slow network to see drpm-s rebuilt in the background while downloading others. Thank you. -- Garry T. Williams -- 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 1-18-14 18:39:55 David wrote: What I did. This worked for me. I set Selinux to permissive I rebooted (don't know if needed) Not necessary. Yum clean all Yum update package-cleanup --dupes (to look for dupes) package-cleanup --cleandupes to remove the dupes This worked for me but I also added yum reinstall the newer package after the cleandupes of the older package. Don't know if it was necessary. -- Garry T. Williams -- 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: dnf-0.4.11
On 1-9-14 15:43:50 Ales Kozumplik wrote: New DNF release is out. See the blog [1], the release notes [2] and the F20 update [3]. Rawhide build went smooth this time too! I see this using 0.4.11. What am I doing wrong? garry@vfr$ sudo dnf --enablerepo=updates-testing update kernel\* [sudo] password for garry: Resolving dependencies -- Starting dependency resolution -- Finished dependency resolution Dependencies resolved. Nothing to do. garry@vfr$ sudo yum --enablerepo=updates-testing update kernel\* Loaded plugins: langpacks, refresh-packagekit [snip] Resolving Dependencies -- Running transaction check --- Package kernel.x86_64 0:3.12.7-300.fc20 will be installed --- Package kernel-devel.x86_64 0:3.12.7-300.fc20 will be installed --- Package kernel-headers.x86_64 0:3.12.6-300.fc20 will be updated --- Package kernel-headers.x86_64 0:3.12.7-300.fc20 will be an update -- Finished Dependency Resolution -- Finding unneeded leftover dependencies Found and removing 0 unneeded dependencies -- Running transaction check --- Package kernel.x86_64 0:3.11.8-200.fc19 will be erased --- Package kernel-devel.x86_64 0:3.11.8-200.fc19 will be erased -- Finished Dependency Resolution Dependencies Resolved PackageArch VersionRepository Size Installing: kernel x86_64 3.12.7-300.fc20updates-testing 30 M kernel-devel x86_64 3.12.7-300.fc20updates-testing 8.5 M Updating: kernel-headers x86_64 3.12.7-300.fc20updates-testing 913 k Removing: kernel x86_64 3.11.8-200.fc19@updates/19 128 M kernel-devel x86_64 3.11.8-200.fc19@updates/19 31 M Transaction Summary Install 2 Packages Upgrade 1 Package Remove 2 Packages Total download size: 40 M Is this ok [y/d/N]: n Exiting on user command Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx.2014-01-12.11-20.aiCKeH.yumtx garry@vfr$ sudo dnf clean all Cleaning repos: fedora rpmfusion-free-updates adobe-linux-x86_64 : rpmfusion-nonfree-updates rpmfusion-free updates google-chrome : rpmfusion-nonfree Cleaning up Everything garry@vfr$ sudo dnf --enablerepo=updates-testing upgrade kernel\* Fedora 20 - x86_64 144 kB/s | 36 MB 04:14 RPM Fusion for Fedora 20 - Free - Updates97 kB/s | 72 kB 00:00 Adobe Systems Incorporated 8.7 kB/s | 1.8 kB 00:00 RPM Fusion for Fedora 20 - Nonfree - Updates 29 kB/s | 13 kB 00:00 RPM Fusion for Fedora 20 - Free 124 kB/s | 487 kB 00:03 Fedora 20 - x86_64 - Updates125 kB/s | 12 MB 01:38 google-chrome26 kB/s | 3.1 kB 00:00 RPM Fusion for Fedora 20 - Nonfree 113 kB/s | 289 kB 00:02 Resolving dependencies -- Starting dependency resolution -- Finished dependency resolution Dependencies resolved. Nothing to do. garry@vfr$ -- Garry T. Williams -- 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: dnf-0.4.11
On 1-12-14 11:39:35 Rahul Sundaram wrote: On Sun, Jan 12, 2014 at 11:30 AM, Garry T. Williams wrote: On 1-9-14 15:43:50 Ales Kozumplik wrote: New DNF release is out. See the blog [1], the release notes [2] and the F20 update [3]. Rawhide build went smooth this time too! I see this using 0.4.11. What am I doing wrong? http://dnf.baseurl.org/2014/01/02/dnf-update-and-yum-update-produce-different-output/ Yes, I have reviewed all that. That reference says, The bottom line is: unless a real update problem occurs (i.e. DNF refuses to update a package that Yum updates) with the same set of metadata (dnf clean all; yum clean all), this is not an issue. I did dnf clean all and the updates-testing package is still not found by dnf. Hey, I'm just testing. It looks like a bug, but I wanted to see if I was overlooking something. -- Garry T. Williams -- 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: dnf-0.4.11
On 1-12-14 18:18:00 M A Young wrote: On Sun, 12 Jan 2014, Garry T. Williams wrote: On 1-9-14 15:43:50 Ales Kozumplik wrote: New DNF release is out. See the blog [1], the release notes [2] and the F20 update [3]. Rawhide build went smooth this time too! I see this using 0.4.11. What am I doing wrong? garry@vfr$ sudo dnf --enablerepo=updates-testing update kernel\* [sudo] password for garry: Resolving dependencies -- Starting dependency resolution -- Finished dependency resolution Dependencies resolved. Nothing to do. Try dnf clean expire-cache first. I don't think dnf checks whether its metadata is up to date as frequently as yum does. Ha! That was it. sudo dnf --enablerepo=updates-testing clean expire-cache sudo dnf --enablerepo=updates-testing upgrade kernel\* did the trick. -- Garry T. Williams -- 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: dnf-0.4.11
On 1-12-14 11:30:31 you wrote: On 1-9-14 15:43:50 Ales Kozumplik wrote: New DNF release is out. See the blog [1], the release notes [2] and the F20 update [3]. Rawhide build went smooth this time too! I see this using 0.4.11. What am I doing wrong? [snip] garry@vfr$ sudo dnf clean all Cleaning repos: fedora rpmfusion-free-updates adobe-linux-x86_64 : rpmfusion-nonfree-updates rpmfusion-free updates google-chrome : rpmfusion-nonfree Cleaning up Everything garry@vfr$ sudo dnf --enablerepo=updates-testing upgrade kernel\* The real problem was not including the updates-testing repo in the clean all command. And yes, as Michael commented, dnf doesn't expire meta-data as often as yum. -- Garry T. Williams -- 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: dnf-0.4.11
On 1-12-14 20:27:26 Reindl Harald wrote: dnf clean all without dnf --enablerepo=updates-testing clean all does exactly *nothing* in case of updates-testing, the same for YUM simply because folders of non-enabled repos are not relevant for any operation Yeah, I feel pretty stupid now. -- Garry T. Williams -- 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: Summary of accepted Fedora 20 Changes - week 30
On 7-27-13 12:11:03 Michael Catanzaro wrote: On Sat, 2013-07-27 at 12:54 +0200, Reindl Harald wrote: so i am maintaing more than 20 fedora machines The typical user will have exactly one Fedora desktop. /me counts my desktop systems. 1. Check. He will never ever look at his system logs. Oops. (I actually uninstalled syslog and only use journalctl [awesome] now. But I do look at the logs.) If you told him that his computer can send him email, his head would explode. Naw. Been using these for decades. Works good. Lasts a long time. (Of course, I always have to make up for Fedora's broken installation by updating my aliases file. But I've had to do that since Solaris 2.5 days.) You can yum install sendmail if you want it, without forcing it on Grandma. You really can. Well, yes. But I'm not sure this discussion really has a handle on the typical *Fedora* user. But hey, I don't have real data either. Just one typical user data point. -- Garry T. Williams -- 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: Proposed F19 Feature: systemd/udev Predictable Network Interface Names
On 2-6-13 14:33:42 Michal Schmidt wrote: If you have Fedora 18 with updates applied your systemd is new enough to allow you to see the udev-generated names using: udevadm info --export -p /sys/class/net/$IFACE | grep ID_NET Example output: E: ID_NET_NAME_MAC=enx000f53014229 E: ID_NET_NAME_PATH=enp40s0f1d1 E: ID_NET_NAME_SLOT=ens4f1d1 One (probably very common) data point, then: garry@vfr$ lspci|grep Ethernet 00:19.0 Ethernet controller: Intel Corporation 82562V 10/100 Network Connection (rev 02) garry@vfr$ udevadm info --export -p /sys/class/net/em1 | grep ID_NET E: ID_NET_NAME_MAC=enx0019d1726ba9 E: ID_NET_NAME_PATH=enp0s25 garry@vfr$ -- Garry T. Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Status to make btsfs to the standard filesystem of Fedora
On Friday, January 18, 2013 10:55:23 Przemek Klosowski wrote: I used btrfs on my personal desktop for about a year now and it works fine for me, other than a nagging suspicion that there's an occasional performance problem at high load. Yes, this is familiar. I too have used it for over a year. I am only using it for /home since the file fragmentation problem was unbearable in /var running yum. The performance problems I experience now are probably related to this: https://btrfs.wiki.kernel.org/index.php/Gotchas (first issue) The last time I tried mounting with autodefrag, it was not much improved and I worried that my kernel was not new enough to run that mount option. Now that I just upgraded to F18, I will try again. The bottom line from my personal experience is if the autodefrag option works well in /home, I would say I'm ready to see btrfs as the default. Otherwise, it would probably be a problem on workstations and certain server environments. Aside from performance, it has been flawless for me over the last year or so. I can't say anything intelligent about it because I coudn't figure out how to measure what I feel, but the system seems sluggish during high-impact events like 'yum update' and/or firefox with gazillion tabs open. This duplicates my experience. I don't have anything intelligent to say about it either. :-) -- Garry T. Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Strange behaviour in SSHD
On Monday, September 10, 2012 10:31:13 某因幡 wrote: Hi, When I ssh to the server, client gets a Broken pipe error and disconnects immediately. So I am trying to strace the server process, but if I attached to the server process with strace, the problem will be gone. And after detaching, it comes back. The server is a Cent OS 6.0. Try strace -f (follow). -- Garry T. Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ARM as a primary architecture
On 03/22/2012 05:04 PM, Adam Williamson wrote: I tried using a laptop and no desktop for a year and switched _back_ to a desktop, I found the faff involved in switching between the two setups too much of a pain. I'm sure I'm not unique either. =) Me too. Oops. I bet I'm not supposed to send mails like this. -- Garry Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: Is it wrong?
On Sunday, July 10, 2011 22:40:51 Steve Dickson wrote: So did that elaborate process of acceptance include the Fedora community or maybe the Linux community or possibly the Business community. You seem to be very late to the party. -- Garry Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: bugreports for missing service-files
On Monday, June 20, 2011 19:48:53 Reindl Harald wrote: Am 21.06.2011 01:30, schrieb Lennart Poettering: On Tue, 21.06.11 01:07, Reindl Harald (h.rei...@thelounge.net) wrote: On F15, an admin who types systemctl stop mysqld.service will get just that, since socket activation is not used. I HAVE TO USE IT SINCE YOU ARE STARTING SERVICES PARALLEL I think you misunderstand. The documentation is clear: http://0pointer.de/public/systemd-man/daemon.html - Socket-Based Activation ... In a socket-based activation scheme the creation and binding of the listening socket as primary communication channel of daemons to local (and sometimes remote) clients is moved out of the daemon code and into the init system. In other words, the daemon *must* be changed to support socket activation. Unless you changed the code in mysqld, this configuration is doomed to fail. -- Garry Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Summary/Minutes from today's FESCo meeting (2011-06-01)
On Wednesday, June 01, 2011 15:16:28 Kevin Fenzi wrote: 18:09:20 ajax would be good to expose some of the different features of BTRFS via anaconda. which? RAID. -- Garry Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [HEADS-UP] Moving /var/run and /var/lock to tmpfs in Rawhide
On Tuesday, November 30, 2010 19:45:11 Joe Nall wrote: On Nov 30, 2010, at 4:01 PM, Tom Lane wrote: That comment suggests you don't even understand the reason why those subdirectories exist. It's this: the daemons do not, and should not, run with the root privileges needed to create things directly in /var/run. The point of a subdirectory is to be owned by the lower-privilege account under which the particular daemon is running. If the subdir has to be remade at runtime, that has to be done by the root-privilege initscript, because /var/run is only writable by root. I was nodding my head in agreement reading this paragraph, and then I looked at my development box. Only avahi-daemon and hald follow this pattern in my /var/run (which I'm sure is not a complete sample). Well, the distinct types are there. Plus, my /var/run has directories owned by: avahi haldaemon mysql named Also, the group owners are different from root on: cups screen I'm still nodding my head in agreement. :-) -- Garry Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Ubuntu moving towards Wayland
On Tuesday, November 09, 2010 14:23:54 Björn Persson wrote: Adam Jackson wrote: % ldd `which gcalctool` | grep libX libX11.so.6 = /usr/lib/libX11.so.6 (0x05f1a000) [snip] ldd appears to resolve dependencies recursively. I typically use readelf to see what a program links to. Then I guess the point is made by examining gvim. -- Garry T. Williams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
