Re: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)
On Fri, Apr 05, 2024 at 12:20:51PM +0200, Vít Ondruch wrote: > > Dne 04. 04. 24 v 17:32 Kevin Kofler via devel napsal(a): > > Neal Gompa wrote: > > > By default, GNOME only presents the close window button. The other > > > buttons are missing, and there isn't really an intuitive way to > > > discover the other window management actions. > > > I agree that there are no other buttons. But still, Gnome opens the windows > in normalized state, not maximized what was the original claim. GNOME (Mutter) maximizes windows if they initially take 80% of more screen space. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. -- ___ 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: Fedora Plasma Workstation (System-Wide)
On Tue, Apr 02, 2024 at 06:44:02PM +, Richard Hughes wrote: > On Tue, 2 Apr 2024 at 10:40, Aoife Moloney wrote: > > Switch the default desktop experience for Workstation to KDE Plasma. > > The GNOME desktop is moved to a separate spin / edition, retaining > > release-blocking status. > > If this is an April fools joke -- it's a weird one, and a day too late. Why would it be? KDE Plasma seem to be more technically advanced than GNOME. This change makes sense. -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert -- ___ 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: FAS issue (was Re: Another mass rebuild blocker: glibc qsort regression)
On Tue, Jan 23, 2024 at 09:04:53AM -0600, Chris Adams wrote: > Once upon a time, Richard W.M. Jones said: > > The authentication issue being this one: > > > > https://pagure.io/fedora-infrastructure/issue/11733 > > I'd be interested in an after report on this one... as someone who has > managed FreeIPA, I'd like to know how this happened (so I can file away > how to NOT do the same thing in my own setups). Form the comment (https://pagure.io/fedora-infrastructure/issue/11733#comment-892793) it seems that new requirement of users having SID caught Fedora FreeIPA of guard. There's `ipa config-mod` invocation to add SIDs to users, but you must make sure you have ID Ranges defined covering all your UIDs and GIDs. -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia -- ___ 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: cloud-init switching to udhcpc
On Tue, Jan 30, 2024 at 10:58:19AM -0600, Major Hayden wrote: > Hey there, > > For those of you who use Fedora often on public cloud providers where > cloud-init handles the initial configuration, there's a change coming for > the very early DHCP request during the boot. ☁️ > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=2247055 I'm curious, why not systemd-networkd? It's mentioned once in the bug, but there's not explanation about the choice later. -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 39 Final blocker status summary #3
On Fri, Oct 20, 2023 at 08:40:43PM -0500, Chris Adams wrote: > Once upon a time, Adam Williamson said: > > 6. distribution - https://bugzilla.redhat.com/2242759 - NEW > > dnf system-upgrade fails on some RPi4 due to system boot date that pre- > > dates gpg key > > > > We're still kinda kicking around ideas for "fixing" this, but I think > > if push comes to shove, we'll wind up revoting or waiving it as not > > practically fixable. > > Not adding to the ticket (because "me too" is not useful there), but... > I think Fedora should include SOME type of "fake hwclock"-type thing for > systems with no RTC (make a systemd service depend on /dev/rtc not > existing?), as other RPi-targeted distros do. This isn't RPi-specific, > a number of the small boards have no RTC. I do typically add an RTC to > my Pis, but not always (for various reasons). We already have systemd-timesyncd. On startup, it syncs the time to the mtime of: - /var/lib/systemd/timesync/clock file; or - /usr/lib/clock-epoch file; or - a time derived from the source tree at build time timesyncd is mentioned in the bug, but I didn't read everything. -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ 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: time is running: security issue BZ#2241470
On Thu, Oct 05, 2023 at 11:23:35AM -0400, Stephen Smoogen wrote: > On Sat, 30 Sept 2023 at 05:13, Marius Schwarz > wrote: > > > > > Hi, > > > > this is emerg ping for the security team, to take a look at this bz : > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2241470 > > > > The deadline for having a fix shipped is the afternoon of SUN, 1. of Oct > > 2023 . On this date, the patches in upstream go public and exploits > > will be developed for them. this impacts ALL of redhat based > > installations which run as servers and are publically reachable. The > > component in question is the default package for rh based installations. > > > So does anyone know which of this weeks major security problems this was > about? Since it is supposedly past the release date, I figure it is ok to > ask. If it isn't due to some other delay.. my apologies. My guess is on glibc's suid local root: https://lwn.net/Articles/946381/ -- Tomasz TorczOnce you've read the dictionary, @ttorcz:pipebreaker.pl every other book is just a remix. ___ 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 Wed, Sep 27, 2023 at 09:48:04AM -0500, Ian Pilcher wrote: > On 9/27/23 04:56, Miro Hrončok wrote: > > fail2ban > > > > https://bugzilla.redhat.com/2219991 > > https://github.com/fail2ban/fail2ban/issues/3487 > > 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.) Check `sshguard`. Despite the name, it also parses logs for few mail and FTP (sic) daemons. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ 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: shotcut compilation fails with "error: ‘hasPro’ was not declared in this scope"
On Sun, Sep 24, 2023 at 11:48:13AM +0200, Fabio Valentini wrote:
> On Sun, Sep 24, 2023 at 11:39 AM Dominik 'Rathann' Mierzejewski
> wrote:
> >
> > > /usr/include/qt6/QtGui/qtextformat.h:556:20: error: stray ‘`’ in program
> > > 556 | { return hasPro`erty(TextBaselineOffset) ?
> > > doubleProperty(TextBaselineOffset) : 0.0; }
> > > |^
> >
> > This is the first error. The rest follows from it.
>
> What *is* weird, however, is that this seems to point at Qt's own
> header files, and this file doesn't seem to have changed in three
> years:
> https://github.com/qt/qtbase/blame/dev/src/gui/text/qtextformat.h#L557
> And there's also no Fedora patches for qt6-qtbase that change this file.
Character 'p' - which should be in this place - is 0x70, character '`' is
0x60. That's one bit error. Typical when using non-ECC memory or
filesystems without checksums.
--
Tomasz TorczTo co nierealne – tutaj jest normalne.
to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne.
___
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: Adding Passim as a Fedora 40 feature?
On Wed, Sep 06, 2023 at 07:58:24AM -0400, Stephen Smoogen wrote: > On Fri, 25 Aug 2023 at 13:31, Richard Hughes wrote: > > > On Fri, 25 Aug 2023 at 16:27, Stephen Smoogen wrote: > > > It depends on the scanning from ports open to unknown shared files to > > 'why did our network costs go up so much?' > > > > Surely if you're on a local network with bandwidth costs you'd turn > > off avahi or lock down the firewall? Lots of stuff blasts out mDNS > > traffic these days. mDNS traffic is 99.9% local, shouldn't matter for metered connections. > In the Windows world, you have a one-click which says 'I am on a metered > line' which is supposed to do things like that. I don't see anything like > that on the Mac but I am only 'learning' it now. In MacOS X there's "Low data mode" switch, but it's available on WiFi connections only (it seems). -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: KDE and GNOME Join Hands To Add Payments To Turn Flathub Into a Store for the Linux Desktop
On Tue, Sep 05, 2023 at 12:07:39PM +0100, Liam Proven wrote: > On Tue, 5 Sept 2023 at 11:51, Richard W.M. Jones wrote: > > > > (Everyone, it's best to not feed the troll) > > Since you don't quote any part of any message, we have no idea who you > consider to be a troll and so who we are not supposed to feed. Thus > making your message content-free and so in itself rather trollish. Look to whose message Richard is replying. -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: SQLAlchemy 2
On Mon, Aug 28, 2023 at 06:51:52PM +0200, Vít Ondruch wrote: > > > Dne 24. 08. 23 v 11:46 Zbigniew Jędrzejewski-Szmek napsal(a): > > == Summary == > > The python-sqlalchemy package is upgraded to major version 2. A > > compatibility package python-sqlalchemy1.4 is added to the > > distribution to cater for software which doesn’t yet use the new API, > > this can be installed side-by-side. Other packages using SQLAlchemy > > are identified and, if necessary, steps are taken to ensure they use > > the correct major version package. > > See > > https://discussion.fedoraproject.org/t/f40-change-proposal-sqlalchemy-2/87805 > > for details and to reply. > Thank you for sharing this. However, I wonder why is just the summary > shared? I guess sharing only a summary is a way to drive interested people to discussion.fedoraproject.org, where, well, discussion is supposed to take place. -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ 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: Warning: DNF is unprotected
On Thu, Aug 24, 2023 at 07:39:07PM +0200, Robert-André Mauchin wrote: > Hello, > > Just a heads-up: for the upgrade to DNF5 in F39, we unprotected the DNF > package, which leaves all of our users vulnerable to a removal of DNF. > > > We have one affected user here: > https://bsd.network/@claudiom/110944941506724767 Not just on, #fedora-qa: 101441 I've just notice my rawhide system is without `dnf` command, and this ling dnf-automatic timers do not work. There is `dnf5` command available, though -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: Self Introduction: Łukasz Patron
On Thu, Aug 24, 2023 at 01:04:36AM +0200, Łukasz Patron wrote: > Hello, > > My name is Łukasz, a software engineer from Poland. > In free time, I'm contributing to various OSS projects, mainly LineageOS. > > For Fedora, I plan to co-maintain WeeChat package and help with other > packages that I'll notice some issues with. Hey Łukasz, Welcome to Fedora! :) -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: Dropping of sshd.socket unit
On Thu, Aug 17, 2023 at 08:25:10AM -0500, Chris Adams wrote: > Once upon a time, Lennart Poettering said: > > Yes, and if this is not what you want, then disable the > > ratelimit. That's what I am saying? > > It would be useful for systemd to have "cooldown periods" for things, > similar to inetd and classic init, where misbehaving things (whether > services or sockets) were paused for a time (configurable even) and then > returned to service. AFAIK this is a flaw in general in systemd's > limits; if something exceeds them, it takes manual intervention to reset > them. Very recent systemd versions have exponentially-growing restart intervals. I guess you can use very large limit for number of restart, and use RestartSteps=/RestartSecMax= to make "cooldown periods". -- Tomasz Torcz Morality must always be based on practicality. to...@pipebreaker.pl — Baron Vladimir Harkonnen ___ 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: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)
On Wed, Jul 26, 2023 at 09:45:13AM +0200, Ralf Corsépius wrote: > > > Am 26.07.23 um 08:48 schrieb Dominik 'Rathann' Mierzejewski: > > On Wednesday, 26 July 2023 at 06:23, Ralf Corsépius wrote: > > > Am 23.07.23 um 00:39 schrieb Neal Gompa: > > > > Actually, why wouldn't this be used everywhere? > > > > > > Because fwupd only works on a small set of machines? > > > > Define small. :) > > Almost none? > > It could be "my bubble", but for me, in all these fwupd is around, it has > never, ever worked on any piece of HW for me. I had fwupdmgr successfuly update firmware on: - few ThinkPad laptops - ThinkStation desktop PC - Logi wireless mouse dongle - Lenovo USB-C docking station - Samsung NVMe drive fwupdmgr also have opt-in reporting (https://lvfs.readthedocs.io/en/latest/telemetry.html), but I'm not aware if update success/failure statistics are reported anywhere. -- Tomasz TorczTo co nierealne – tutaj jest normalne. to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne. ___ 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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]
On Tue, Jul 11, 2023 at 12:49:10PM +0200, Kevin Kofler via devel wrote: > Oracle has (finally – the community projects Rocky and Alma were much > quicker to react) made an announcement about the situation: > https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/ SUSE too, but it is not so funny as Oracle's https://www.suse.com/news/SUSE-Preserves-Choice-in-Enterprise-Linux/ -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On Sun, Jul 09, 2023 at 09:59:08AM +0200, Vitaly Zaitsev via devel wrote: > On 09/07/2023 08:59, Mattia Verga via devel wrote: > > BTW in the spirit of openness, I've set up a poll (UNOFFICIAL) to > > clearly state community sentiment about enabling OPT-OUT metrics to FESCO: > > https://discussion.fedoraproject.org/t/unofficial-poll-about-opt-out-metrics-proposal/85494 > > > > Just a simple question and a YES/NO reply. > > Sorry, but we can't trust **ANONYMOUS** vote on a third-party platform. > Admins or other people with access to host can easily edit SQL database and > set 100500 votes for variant YES there. Yes they could, but this is ridiculous. -- Tomasz TorczTo co nierealne – tutaj jest normalne. to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne. ___ 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: Color Bash Prompt (System Wide)
On Fri, Jul 07, 2023 at 01:38:08PM +0200, Vít Ondruch wrote: > > > > There seems to be a general desire to have a colored prompt like other > > popular distros, which commonly use green > > > Shouldn't blue be the default for Fedora? > > And I think that dark as well as light color schemes should be considered. I thought we should be using ANSI_COLOR from /etc/os-release. Which is blue on Fedora. -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: Requesting an addition to the install image
On Thu, Jun 08, 2023 at 11:37:47AM -0500, Chris Adams wrote: > Where is the proper place to request something be added to the install > image? I was going to file a BZ but wasn't sure of the proper > component. > > I'd like to see nvme-cli (and libnvme, which it depends on) added to the > install image. I wanted to switch an NVMe drive to 4K sectors, which > reformats it, so I needed to do that before installing Fedora (or have > to install, change, then reinstall). It would be much more convenient > to be able to boot into rescue mode to do this. I believe you can use DNF on install media to install missing packages. -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ 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: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)
On Fri, Dec 30, 2022 at 12:59:19AM -0500, Nico Kadel-Garcia wrote: > On Wed, Dec 28, 2022 at 7:01 AM Ralf Corsépius wrote: > > > > Am 28.12.22 um 11:49 schrieb Peter Boy: > > > > > > It is a good idea to make the timeout configurable. But the default > > > timeout for servers must remain unchanged. > > > > My problem is not "defined timeouts" it is systemd delaying shutdowns > > for no obvious reasons. > > You've apparently not encountered the corruption of a database under > heavy load where the cache where swapspace has not yet been propagated > to disk. Imagine a server running a lot of virtual machines for an > image of what an overly aggressive shutdown timeout can do to your > otherwise stable systems. This sounds serious, and this is the situation in which default setting is not correct, no matter if its 15 seconds or 120 seconds. The database and VM services should define own timeout (it goes from 0 to infinity, plenty of values to choose from). -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ 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: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)
On Thu, Dec 22, 2022 at 05:22:09PM -0500, Steve Grubb wrote: > On Thursday, December 22, 2022 1:29:29 PM EST Adam Williamson wrote: > > 15 seconds feels very aggressive to me. I can think of some cases, like > > libvirtd automatically suspending or cleanly shutting down running VMs, > > that might well take longer than that. Could we not go for 30 seconds? > > Going all the way from 90/120 down to 15 seems pretty radical. > > I run across this with some regularity. PackageKit is not installed on my > system. What I wished was that when there is a stall shutting down, a message > to the console or a dialog box explains who is holding up shutdown. If we > knew who was holding things up, bugs might get filed. But there already is such message! First "waiting for shutdown" with unit name and a timer. Then, in the last phase there's also "wating for process:" message. The problem is: at this points it is hardly debuggable. One cannot start a new shell, sshd is off already, journalctl too. No way to gather any information what's wrong with the process holding up shutdown. We only get a name. And usually you cannot reproduce the problem easy on next shutdown. Maybe netconsole is still functioning at this point, but I doubt it. -- Tomasz TorczTo co nierealne – tutaj jest normalne. to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne. ___ 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: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)
On Thu, Dec 22, 2022 at 12:35:54PM -0500, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer > > This document represents a proposed Change. As part of the Changes > process, proposals are publicly announced in order to receive > community feedback. This proposal will only be implemented if approved > by the Fedora Engineering Steering Committee. > > == Summary == > A downstream configuration change to reduce the systemd unit timeout > from 2 minutes to 15 seconds. Great change, please do it! Also, sometimes after reaching the timeout, systemd extends wait by another 2 minutes (or 1m30). I wasn't able to find in the sources or documentation why this happens, but this behaviour should be blocked. Otherwise some services after 15s will get another 15, and then another… -- Tomasz TorczTo co nierealne – tutaj jest normalne. to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne. ___ 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: F38 proposal: Unified Kernel Support Phase 1 (System-Wide Change proposal)
On Wed, Dec 21, 2022 at 10:16:58AM -0600, Chris Adams wrote: > Once upon a time, Zbigniew Jędrzejewski-Szmek said: > > Without an initrd we immediately have the following limitations: > > - all kernel modules needed to mount root must be compiled in > > - all that code is always loaded and remains in unswappable memory > > - root= syntax is limited to what the kernel understands, i.e. > > no root=UUID=… o root=/dev/disk/by-path/… or other udev links, > > no encryption or dm-verity. > > - no bluetooth keyboards or other fancy peripherals > > - recovery is pretty hard > > Also, the security lock-down for the kernel command line means: > - no network root filesystem > - no boot-time-only kernel/module configuration > > The idea of switching from grub2 to sd-boot would also drop network boot > and BIOS support. Supporting boot loaders seems to be a bit of a issue > sometimes, so trying to support multiple boot loaders seems like a bad > idea to me. I'm using network boot without grub2, just iPXE and kernel+initrd. It worth noting that NFS root doesn't work with dracut from rawhide, for months now. -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: SPDX Statistics
On Thu, Dec 01, 2022 at 10:14:04AM +0100, Miroslav Suchý wrote: > The list of packages needed to be converted is again here: > > https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final.txt > > Any question? Please check > https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1#Questions_from_the_mailing_list_discussion What does this warning mean? ladvd warning: valid as old and new and no changelong entry, please check I can't find this string neither on wiki page nor in license-validate script. -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ 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: F38 proposal: PostgreSQL 15 (Self-Contained Change proposal)
On Wed, Oct 12, 2022 at 02:59:20PM -0400, Frank Ch. Eigler wrote: > Ben Cotton writes: > > > https://fedoraproject.org/wiki/Changes/PostgreSQL_15 > >[...] > > === Plan === > > > > * Prepare PostgreSQL 15 in Copr (TBD) > > * Rebuild important dependencies in Copr (TBD) > > * Debug and fix compatibility issues found in dependencies (a > > reasonable amount of non-critical in FTBFS state might be tolerable) > > * Build in a "side tag" to prevent dependencies from failing and > > rollout once stable > > * Prepare Pull requests in Rawhide > > * Merge and build into a "side tag" > > * Once stable merge into Rawhide > > Does this rebase include automated migration of existing databases? If > not, are users expected to do it manually, based on upstream postgresql > docs? Need of manual migration always has been there, hasn't it? -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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 Sun, Oct 09, 2022 at 10:25:08AM -, Daniel Rusek wrote: > Hello, > > Just a note. If someone from RPM Fusion who is interested in packaging > full mesa-va-drivers package reads this, please, make sure that the > package also contains valid AppStream metadata and is showing in GNOME > Software / KDE Discover the same way as, for example, NVIDIA driver > does. It is _unacceptable_ to force end users to search for and > install the driver package via terminal. Thanks! You can provide feedback at the review request https://bugzilla.rpmfusion.org/show_bug.cgi?id=6426 -- Tomasz TorczOnce you've read the dictionary, @ttorcz:pipebreaker.pl every other book is just a remix. ___ 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: Inactive packagers to be removed after the F37 release
On Tue, Sep 06, 2022 at 04:14:52PM -0500, Jonathan Wright via devel wrote: > On Tue, Sep 6, 2022 at 3:52 PM Vitaly Zaitsev via devel < > devel@lists.fedoraproject.org> wrote: > > > On 06/09/2022 19:49, Michael Catanzaro wrote: > > > Of course, hardware authenticators would be even more secure, and it > > > sure seems pretty reasonable to expect that people with commit access to > > > Fedora packages are able to purchase a $25 or 30€ security key [1][2]. > > > > Having to pay even $25 for a hobby project is not acceptable, IMO. If > > you want to enforce such a policy, find sponsors and buy devices for all > > Fedora contributors. > > > Fedora must be looked at as more than just a "hobby project" even though it > is a hobby for some. > > It's an OS that many rely on and $25 is a somewhat trivial cost for > improved security. What more, this cost would be amortized over multiple projects. One hardware key can be used with any number of projects and personal accounts. -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ 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: graphlcd-base: udev rules file can't be found for fc37
On Wed, Aug 03, 2022 at 12:58:16PM -, Martin Gansser wrote: > Hi, > > I want to fix the build of graphlcd-base-2.0.3 for fc37 because the udev > rules file cannot be found [1]. > ... > File not found: > /builddir/build/BUILDROOT/graphlcd-base-2.0.3-1.fc37.x86_64/etc/udev/rules.d/*-graphlcd-base.rules > .. > I have already added a if condition to the spec file so that for <= fc36 the > udev_rules_dir "/usr/lib/udev/rules.d" > and for fc37 the udev rules dir "/etc/udev/rules.d" is used, but the > compiling fails on koji, because it cannot find the rules file. This looks incorrect. Package-provided rules files should go into /usr…, /etc… directory is for sysadmin overrides. You should use %_udevrulesdir coming from systemd RPM macros, no matter which Fedora version. You seem to have been using the macro before – it's commented out in graphlcd-base.spec file. Anyway, the build log shows that software was compiled, but the rule file was not installed. I see that installation in the Makefile is guarded with following test: # Checking for UDEVRULESDIR without DESTDIR (check if build system uses systemd) ifneq ($(wildcard $(UDEVRULESDIR)/.),) install -d $(DESTDIR)$(UDEVRULESDIR) install -m 644 $(UDEVRULE) $(DESTDIR)$(UDEVRULESDIR) So this is probably a place where installation goes wrong, but I do not know Makefile syntax enough to guess how. -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ 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: future of dual booting Windows and Fedora, redux
On Wed, Jul 27, 2022 at 05:07:39AM +0200, Kevin Kofler via devel wrote: > Chris Murphy wrote: > > cryptsetup does have Bitlocker support, so long as you have the recovery > > key you can unlock and get access to your data, I've tested this. > > But you need a recovery key to begin with, because the main key is sealed in > the TPM and not visible from anything other than Windows. > > So Bitlocker essentially forces Windows on you. Bitlocker is part of Windows. Sure, cryptsetup supports it, but if you are using cryptsetup already maybe stick with LUKS2? > > This is entirely beside the point though, which is to try and make dual > > boot as useful for users as possible. We want users to be confident about > > both OS's remain accessible in a discoverable way, without having to jump > > through hoops. > > Sure. Really sad though that we have to work around a broken piece of > "security" software that effectively functions like a ransomware. > > Where is the outcry about this misfeature? Not here, thankfully. This is fedora-devel, I consider name-calling other operating systems to be offtopic here. -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ 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: Once again, more than 8 days delayed notifications
On Mon, Jul 11, 2022 at 03:36:08PM +0200, Petr Menšík wrote: > Do we have any notification alternative interface other than IRC? What about > pushing notifications to matrix, XMPP or other protocol/service? There were other channels like email, but they do not work, too. I seem to recevive last notification by email in the middle of November 2021. -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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: Grafana license change from ASL 2.0 to AGPLv3
On Tue, Jun 28, 2022 at 05:16:14PM +0200, Andreas Gerstmayr wrote: > I plan to submit a Grafana 8.5.6 rebase to Fedora rawhide in the coming > days. Why not to v9? -- Tomasz Torcz Morality must always be based on practicality. to...@pipebreaker.pl — Baron Vladimir Harkonnen ___ 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: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)
On Thu, Jun 16, 2022 at 07:13:55PM -0400, Frank Ch. Eigler wrote: > > > https://fedoraproject.org/wiki/Changes/fno-omit-frame-pointer > > [...] > > === Unwinding === > > [...] > > * Kernel 4.8 frame pointer benchmarks by Suse showed 5%-10% > > regressions in some benchmarks > > (https://lore.kernel.org/all/20170602104048.jkkzssljsompj...@suse.de/T/#u) > > Regressions of such magnitude can veto such changes, especially when > they hit everyone, not just those who are highly dependent on the > profiling tools the proposal is concerned about. I can only concur. Say what you want about Phoronix benchmark, but they consistently benchmark different distributions And Fedora consistently is lagging behind. Latest article is at https://www.phoronix.com/scan.php?page=article=h1-2022-linux Slowing Fedora even further is really undesirable. -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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 Tue, May 17, 2022 at 02:11:03PM +0200, Vitaly Zaitsev via devel wrote: > > First - our burden. We ahve to certify each binary. This is quite long > > and lenghty process. Onl once it is certified, we can release it (with > > small unwritten exception in rawhide) > > Just stop doing TCK certification. Most of Fedora users don't need > "certified binaries". Exactly. This change does not benefit Fedora, it is only to make certification easier. Certification which is not needed. -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ 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: Would it be useful to have a video call to discuss the "Deprecate Legacy BIOS" Change proposal?
On Thu, Apr 14, 2022 at 01:42:26PM +0200, Kevin Kofler via devel wrote: > Jóhann B. Guðmundsson wrote: > > In this case that SIG would be created for no good reason since the > > outcome is inevitable. > > I still do not see what is inevitable about the outcome. Keeping legacy, no > longer changing, interfaces working forever should require next to no > effort. So the SIG would have next to no work to do. Great! In reality, distribution around BIOS booting change, compilers change, there is always some effort required even to maintain status quo. -- Tomasz Torcz “Never underestimate the bandwidth of a station to...@pipebreaker.plwagon filled with backup tapes.” — Jim Gray ___ 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: Would it be useful to have a video call to discuss the "Deprecate Legacy BIOS" Change proposal?
On Thu, Apr 14, 2022 at 10:01:30AM +0200, Ralf Corsépius wrote: > > > Am 13.04.22 um 20:05 schrieb David Cantrell: > > > The Legacy BIOS SIG is a good proposal to handle this sort of ongoing work > > in > > Fedora. > > I do not agree with this statement. Like previous "Legacy SIGs" this is a > red herring to obfuscate RHATs lack of disinterest with topics, which do not > match into their business objectives. Really? Fedora is mainly a volunteer effort, someone has to do the work. SIG is a good solution. RedHat is under no obligation to work on everything. -- Tomasz Torcz “Never underestimate the bandwidth of a station to...@pipebreaker.plwagon filled with backup tapes.” — Jim Gray ___ 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: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote: > If you use i686 packages for something now, please respond to this thread. Steam requires some i686 libs, but frankly I haven't run it recently due to Stadia. -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: strange output
On Sun, Mar 13, 2022 at 07:29:27PM -, Cătălin George Feștilă wrote: > I run this command on my root > > #cat /usr/bin/gcc > > ... and I got a large strange output ... You just printed executable binary. It is not supposed to be displayed like that. > What is this? Is it a bug? No, it is not. What did you expect? -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: Donate 1 minute of your time to test upgrades from F35 to F36
On Fri, Mar 11, 2022 at 06:43:01PM +0100, Miroslav Suchý wrote: > Do you want to make Fedora 36 better? Please spend 1 minute of your time and > try to run: > > > In case you hit dependency issues, please report it against the appropriate > package. > Two problems, one with lilv: Error: Problem 1: lilv-0.24.10-4.fc35.i686 has inferior architecture - lilv-0.24.10-4.fc35.x86_64 does not belong to a distupgrade repository - problem with installed package lilv-0.24.10-4.fc35.i686 Already reported at https://bugzilla.redhat.com/show_bug.cgi?id=2052588 The other one with obs/x264 from RPMFusion. In general, great work! -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: Action Required: Bugzilla - API Authentication changes
On Tue, Feb 01, 2022 at 02:25:36PM +0100, Pierre-Yves Chibon wrote: > On Tue, Feb 01, 2022 at 01:41:01PM +0100, Miro Hrončok wrote: > > On 01. 02. 22 13:37, Fabio Valentini wrote: > > > Hi Miro, > > > > > > Thanks for forwarding this announcement. > > > Apparently the talk about "improving communication between RHBZ and > > > the Fedora Project" has not born fruit yet. ;) > > > > Well the announcement was public, I recommend subscribing to > > https://listman.redhat.com/mailman/listinfo/bugzilla-announce-list if you > > interact with bugzilla a lot. > > > > > Do we know if any of our tools and scripts that interact with RHBZ > > > will get broken by this? > > > I assume you have an eye on at least some of the releng scripts (FTI, > > > FTBFS, etc.). > > > > I will check. I think it's all broken. > > > > > But what about fedora-review? fedora-create-review? The tool that > > > syncs assignees from dist-git to RHBZ? > > > > No idea. > > Most of these tools are written in python and as the email says, the most > recent > version of python-bugzilla works fine (which is already in Fedora and EPEL - > stable). > > So as long as your systems are up to date, it should be somewhat transparent. abrt-gui on up-to-date Fedora 35 still asks for Username and Password in Bugzilla configuration panel. No mention of API keys. -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: MinGW UCRT target (Self-Contained Change proposal)
On Mon, Jan 31, 2022 at 05:17:29PM +0100, Kevin Kofler via devel wrote: > > But yes, for Windows releases ≥ 95 OSR 2 and < 10 (and no, Windows version > numbers are not anywhere near monotonic ;-) ), MSVCRT is included out of the > box, UCRT is not. Is it really a good default to depend on a runtime library > that is only included in Windows ≥ 10? I've just checked, Windows 10 was released 7 years ago (Fedora 22 timeframe). We don't have to care about compatibility with so ancient releases. -- Tomasz Torcz “Never underestimate the bandwidth of a station to...@pipebreaker.plwagon filled with backup tapes.” — Jim Gray ___ 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: Why was node_exporter.service renamed to prometheus-node-exporter.service?
On Fri, Jan 28, 2022 at 12:01:43PM +, Barry Scott wrote: > I just had to fix a number of my servers that use node exporter. > > The service name has been changed. Why was this done and did no one > think about the impact on users? This was done here: https://src.fedoraproject.org/rpms/golang-github-prometheus-node-exporter/c/5ad49dd6ed767d44070866d996d844dec4b5f07b?branch=f35 as part of the fix for https://bugzilla.redhat.com/show_bug.cgi?id=2039257 (golang-github-prometheus-node-exporter installs service unit in /etc) Moving the unit is fine, but rename should not happen stable release. At least some compat symlinks/Alias= should be provided. > In the worst case I had a server fail to reboot because I had > Requires=node_exporter.service in the default target. It is unfortunate. It is also unfortunate no-one cared enough about node-exporter to have it tested during 2 weeks time (https://bodhi.fedoraproject.org/updates/FEDORA-2022-e52d3d8db2) before it was submitted to stable. -- Tomasz Torcz “Never underestimate the bandwidth of a station to...@pipebreaker.plwagon filled with backup tapes.” — Jim Gray ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is systemd-resolved ignoring /etc/hosts?
On Fri, Jan 21, 2022 at 05:06:01PM -0300, Sergio Belkin wrote: > Is there a way that systemd-resolved honors the /etc/hosts file? > Thanks in advance There's ReadEtcHosts= setting controlling that. See "man resolved.conf" or /etc/systemd/resolved.conf itself. -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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: Rawhide / systemd 250: kernel-install may place kernels and config in the wrong place
On Wed, Jan 05, 2022 at 05:36:56PM -0800, Adam Williamson wrote: > So, my question is...do other Rawhide users have this problem, or is my > system an outlier for some reason? I have not been able to figure out > *what* created the problematic directories on my system. An earlier > systemd rc may have created /boot/efi/(machine_id) if > /boot/efi/loader/entries existed, but I don't know what might have > created /boot/efi/loader/entries . I'm pretty sure I didn't do it > myself, though. My rawhide system seem to have both and boot even other kernel: tree /boot/efi /boot/efi ├── 6a1b72cbb94d4c95a4ac9df2d581e371 │ ├── 0-rescue │ │ ├── initrd │ │ └── linux │ ├── 4.16.0-0.rc5.git2.1.fc29.x86_64 │ ├── 4.16.0-0.rc6.git2.1.fc29.x86_64 │ ├── 4.16.0-0.rc7.git1.1.fc29.x86_64 │ └── 5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64 │ ├── initrd │ └── linux ├── EFI │ ├── BOOT │ │ ├── BOOTX64.EFI │ │ └── fbx64.efi │ └── fedora │ ├── BOOTX64.CSV │ ├── grub.cfg │ ├── grub.cfg.rpmsave │ ├── grubenv.rpmsave │ ├── grubx64.efi │ ├── mmx64.efi │ ├── shim.efi │ └── shimx64.efi └── loader └── entries └── 6a1b72cbb94d4c95a4ac9df2d581e371-5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64.conf # uname -r 5.16.0-0.rc4.20211207gitcd8c917a56f2.30.fc36.x86_64 -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: A way to request/vote for packages to add next to Fedora Linux?
On Fri, Nov 19, 2021 at 05:32:28AM -, Reon Beon via devel wrote: > Video2X would be a nice add. There's a package wishlist here: https://fedoraproject.org/wiki/Package_maintainers_wishlist But adding the package there is no guarantee anyone will pick it up. I believe most items are there for years without action. Best way is to become a packager and add a package by yourself: https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ -- Tomasz Torcz Morality must always be based on practicality. to...@pipebreaker.pl — Baron Vladimir Harkonnen ___ 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: Package information on ELF objects (System-Wide Change proposal)
On Tue, Nov 09, 2021 at 10:14:25AM +0100, Vitaly Zaitsev via devel wrote: > On 08/11/2021 22:24, Lennart Poettering wrote: > > And I think that's a*good* thing: JSON might not be perfect — because > > nothing is —, but it's certainly one of the better designed generic > > data formats around, and it's complexity is absolutely managable. > > What about YAML? YAML is much more complicated that JSON. To the point that JSON document is a valid YAML document. YAML spec (https://yaml.org/spec/1.2.2/) is about 66 pages when printed. -- Tomasz TorczOnce you've read the dictionary, @ttorcz:pipebreaker.pl every other book is just a remix. ___ 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: Woah! [Thanks, Nest sponsors]
Sorry everyone, I wanted to send a private email :( -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: Woah! [Thanks, Nest sponsors]
On Wed, Oct 13, 2021 at 02:33:19PM +0200, Dominik 'Rathann' Mierzejewski wrote: > On Wednesday, 13 October 2021 at 13:08, Luna Jernberg wrote: > > You had to register at a website during the event, > > That I did. On August 7th, I received an e-mail with a promo code to > enter at https://coolstuff.redhat.com/promo/fedora which I did, but I > haven't heard from them since. > > > got an email with > > tracking information from both Fedex and Red Hat > > Nothing yet. :( Cześć Dominik, Czy Ty masz adres korespondencyjny w Polsce (o ile opsec pozwala Ci zdradzić ;)? Mój swag-pack został wysłany i dostałem od Fedex dokumentu do odprawy celnej… też tak miałeś? -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: License correction: wlcs is “GPLv3”, not “GPLv2 or GPLv3”
On Tue, Nov 02, 2021 at 03:26:52PM -0400, Ben Beasley wrote: > The License field of wlcs has been corrected from “GPLv2 or GPLv3” to > “GPLv3”. https://github.com/MirServer/wlcs (is this the right repo?) contains both COPYING.GPL2 and COPYING.GPL3. How did you determine correct license? -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: Package information on ELF objects (System-Wide Change proposal)
On Thu, Oct 28, 2021 at 05:44:44PM +0200, Vitaly Zaitsev via devel wrote: > On 28/10/2021 15:53, Chris Adams wrote: > > New 500G SSDs are available under $50, and 1TB under $90. > > QLC is not an option. Too slow outside of the SLC cache. Stop moving the goalposts, okay? -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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: Woah! [Thanks, Nest sponsors]
On Wed, Oct 13, 2021 at 02:33:19PM +0200, Dominik 'Rathann' Mierzejewski wrote: > On Wednesday, 13 October 2021 at 13:08, Luna Jernberg wrote: > > You had to register at a website during the event, > > That I did. On August 7th, I received an e-mail with a promo code to > enter at https://coolstuff.redhat.com/promo/fedora which I did, but I > haven't heard from them since. Same with me. > > got an email with > > tracking information from both Fedex and Red Hat > > Nothing yet. :( Nothing. Are swag packs sent in batches? -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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: F34 Cloud Amazon AMIs unbootable after updates
On Thu, Oct 07, 2021 at 08:18:44AM +0100, Richard W.M. Jones wrote: > On Thu, Oct 07, 2021 at 12:46:11AM -0400, Christopher wrote: > > Running on EC2, it's kinda hard to get good information from a system > > that won't boot. The machine won't boot to the point of being able to > > capture the system log, and the screenshot of the instance doesn't > > appear to be super helpful: https://imgur.com/a/4PWcRSg > > Can you hit shift + PgUp and capture as much of the preceeding output > as possible? Nb. console scrollback was removed in kernel 5.9, so shift+pgup no longer works. -- Tomasz Torcz Morality must always be based on practicality. to...@pipebreaker.pl — Baron Vladimir Harkonnen ___ 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: [RFC] Remove supoort for NIS(+) from PAM
On Fri, Oct 01, 2021 at 12:28:38PM -0400, Stephen John Smoogen wrote: > On Fri, 1 Oct 2021 at 12:21, Frank Ch. Eigler wrote: > > > > Stephen John Smoogen writes: > > > > > The places I have seen it still being used are in Universities run by > > > people who learned sysadmin in the 1990's and early 2000's. It is a > > > light weight system which is simple to set up [...] > > > > For those people who like simple to set up and working systems but are > > willing to consider upgrading if it's also simple and will keep working, > > is there a NIS->$whatever migration document in fedora someplace? > > I don't think anyone has come up with an agreed upon $whatever that a > majority of people like. There is LDAP but that isn't light. There are > kerberos but that isn't easy. There's FreeIPA, which makes both of them easy. And we even ship is a Fedora feature. > And honestly the cool kids only want web > logins these days as servers are a pain and why not just login into > Google/Facebook/Microsoft and let them deal with all that setup. -- Tomasz Torcz Morality must always be based on practicality. to...@pipebreaker.pl — Baron Vladimir Harkonnen ___ 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: Donate 1 minute of your time to test upgrades from F34 to F35
On Wed, Sep 08, 2021 at 07:19:41AM -0400, Solomon Peachy wrote: > On Wed, Sep 08, 2021 at 01:52:58PM +0300, Otto Urpelainen wrote: > > >- package php-imap-7.4.23-1.fc33.x86_64 requires php-common(x86-64) = > > > 7.4.23-1.fc33, but none of the providers can be installed > > > > This line repeats a lot in your output. I think you will get forward with > > this if you figure out what happened to php-imap in Fedora 34 and, whatever > > that was, how to recover from it. > > Yeah, it looks like the php-imap package was dropped in the F34 testing > cycle due to an issue that probably only needed a simple rebuild to fix: > > https://bugzilla.redhat.com/show_bug.cgi?id=1929640 If I remember correctly, the problem was in uw-imap, which was abandoned and removed from Fedora: https://src.fedoraproject.org/rpms/uw-imap/c/ba748fd8f4697d79cf54a4b8a488f95fff04d7c1?branch=rawhide php-imap is just a wrapper around uw-imap, and as a result was removed, too. In other words, it's not only a question of rebuilding, as dependencies for php-imap are no longer in Fedora. > > I rely on php-imap for authentication purposes on a _lot_ (using php > packages that remain included with Fedora!) so this is actually a major > blocking issue for me. Time to start migration to non-abandoned solution :( -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ 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: Donate 1 minute of your time to test upgrades from F34 to F35
On Tue, Sep 07, 2021 at 06:14:58PM +0200, Miroslav Suchý wrote: > Do you want to make Fedora 35 better? Please spend 1 minute of your time and > try to run: #v+ Error: Problem 1: package dhcp-compat-12:4.4.2-11.b1.fc34.x86_64 requires dhcp-relay = 12:4.4.2-11.b1.fc34, but none of the providers can be installed - dhcp-relay-12:4.4.2-11.b1.fc34.x86_64 does not belong to a distupgrade repository - problem with installed package dhcp-compat-12:4.4.2-11.b1.fc34.x86_64 #v- -compat package for "dhcp" was removed: * Fri Jun 11 2021 Pavel Zhukov - 12:4.4.2-12.b1 - Drop compat package finally I've opened a bug against fedora-obsolete-packages https://bugzilla.redhat.com/show_bug.cgi?id=2002163 #v+ Problem 2: problem with installed package pulseaudio-module-bluetooth-freeworld-1.4-6.fc34.x86_64 - package pulseaudio-module-bluetooth-freeworld-1.4-6.fc34.x86_64 requires libpulsecore-14.2.so()(64bit), but none of the providers can be installed - pulseaudio-14.2-3.fc34.x86_64 does not belong to a distupgrade repository #v- This is RPMFusion's package. Given that, and the fact Pulseaudio got replaced by Pipewire, this is not important. -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ 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 Packager Dashboard - Contextual Package Calendars and more!
On Tue, Aug 10, 2021 at 04:48:37PM +0200, Frantisek Zatloukal wrote: > Hi, > > In the past months, we've enabled "Contextual Package Calendars" on Fedora > Packager Dashboard <https://packager-dashboard.fedoraproject.org/>. > > In short, it shows you package-specific calendars, eg. If you maintain some > GNOME package, the Dashboard will show you the GNOME release schedule. This > currently works for GNOME and Python Interpreter package maintainers. Hey, This is seriously cool! For packages with release schedules, the new funcionality brings the information exactly where it's needed. Fedora release calendar dates in the top section of the page is wonderful, too! -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: RFC: Banning bots from submitting automated koji builds
Dnia Sun, Jun 20, 2021 at 10:39:34AM +0200, Miro Hrončok napisał(a): > On 19. 06. 21 22:18, Fabio Valentini wrote: > > The following things should still be allowed: > > - releng and SIGs submitting scripted mass rebuilds (no actual package > > changes, triggered by a person) > > - bots submitting rawhide builds for ELN (no package change, just > > built for different buildroot) > > Other random ideas of what should be allowed: > > - a bot rebuilds packages automatically (bump-only or no changes), when > dependencies change We supposedly have it in Fedora already: https://fedoraproject.org/wiki/Koschei but it never worked for me. -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ 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: When is pappl going to be good enough to replace cups?
Dnia Mon, May 24, 2021 at 08:21:07PM -0400, Solomon Peachy napisał(a): > > > Well, if I want to configure the printer, I need to know what to point my > > browser at. But sure, if a dialog gives me a link, that is a way. Though it > > means yet another layer of indirection (bringing up the dialog first, only > > to get redirected to a web interface). > > Running 'ippfind' will show you the list of all IPP-capable printers > that are advertising themselves through mDNS, and the URI they can be > reached at. Nice command, but it returns host in the .local domain, resolving of which doesn't work half of the time. The host sharing the printer has normal, functioning FQDN, couldn't ippfind return it? I do control the network, including DNS server, but this zeroconf stuff is a jungle. (some time ago I'v tried to share common LAN bookmarks using zeroconf, but only Epiphany supported it. Firefox never get there - bz 173804. Today, I don't even know what the equivalent of /etc/avahi/services/ is in the systemd-resolved world). -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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 CoreOS stable stream now rebased to Fedora 34
Dnia Tue, May 18, 2021 at 03:37:27PM -0400, Dusty Mabe napisał(a): > Over the next two days we're rolling out the first Fedora 34 based > Fedora CoreOS into the `stable` stream. > > - systemd-resolved is still enabled but not used yet [1] This was Fedora 33 feature. > - Move to cgroup v2 by default [5]. This was Fedora 31 feature. I was wondering: Fedora CoreOS actively undoes distribution-wide changes (at least the two above, I remember lagging with iptables-nft around Fedora 32). End user may confused, seeing the list of changes for the release X, but receiving only few of them with edition CoreOS X. Should such divergence be allowed? Should Fedora CoreOS use the same version number while not containing all the changes from main Fedora Linux? -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ 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: Upgrade to Fedora 34 broke the boot menu.
Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a Missing theme files sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1944571 (Error message during boot about missing fireworks.png) -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ 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: Gnome Fractal and veloren/airshipper needs maintainer
Dnia Sun, May 02, 2021 at 02:15:21PM -, Artem Tim napisał(a): > Veloren and Veloren Airshipper bot using rust-nightly. you can forget about > packaging it for official repos in Fedora. > > Fractal - good luck to package it Fedora. > > But both packaged for a long time and available in COPR: > > - Fractal: https://copr.fedorainfracloud.org/coprs/atim/fractal/ Additionaly someone (Daniel García Moreno?) provides Fractal as flatpak on flathub. -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ 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: F34 update experience
Dnia Tue, Apr 27, 2021 at 04:08:38PM +, Zbigniew Jędrzejewski-Szmek napisał(a): > On Tue, Apr 27, 2021 at 10:04:34AM -0400, Neal Becker wrote: > > Updated F33 -> F34. Mostly went well, except there is one thing which > > could be better. This is not new to F34 but has been there since the > > dnf system-upgrade. > > > > Running on a pretty decent laptop (core i7, 8GB, SSD). The issue is > > that the installation hangs a long time with no evidence of activity. > > The hang begins at > > dnf running transaction. It is disconcerting because it hangs for > > about 20-30 minutes, and during that time the fan is not running, so > > 20-30 minutes seems unexpected… There is a phase where dnf is solving > the deps, but it's usually much much shorter (*), and it's CPU-bound, > so the fans should be on. I don't know what's going on in your case, > but it sounds like some bug. In 2019 I did some measurements of F31→F32. First step of distribution upgrade took 16 minutes on a desktop computer. The results are at https://enotty.pipebreaker.pl/posts/2019/12/time-needed-to-dist-upgrade-fedora/ > Do you have a huge number of packages? Lot's of modules? A very slow disk? `rpm -qa` returns 3109. No modules (I think). Storage is btrfs raid1 over 2xHDD (5900 RPM) + bcache with 2x384GiB partitions. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ 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: Github Action for discovering active Fedora Releases
Dnia Wed, Apr 14, 2021 at 01:12:47PM -0400, Stephen Gallagher napisał(a): > Since I figured it might be useful to others, I have made it available > publicly. See the Marketplace link[1] for usage examples. > > [1] https://github.com/marketplace/actions/get-fedora-releases #v+ name: Get Fedora Releases runs-on: ubuntu-latest #v- :-) -- Tomasz TorczTo co nierealne – tutaj jest normalne. to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change proposal: Smaller Container Base Image (remove sssd-client, util-linux, shadow-utils) (Self-Contained Change)
Dnia Fri, Apr 02, 2021 at 05:30:30PM -0400, Neal Gompa napisał(a):
> On Fri, Apr 2, 2021 at 5:18 PM Lars Seipel wrote:
> >
> > On Thu, Apr 01, 2021 at 02:36:48PM -0400, Neal Gompa wrote:
> > >Unless OpenShift and RKE recently changed so that containers can run
> > >as root by default (as of yesterday, they didn't), this is solidly a
> > >bad idea, since it makes it much more unintuitive to set up secure
> > >containers conforming with the guidelines for these Kubernetes
> > >platforms.
> >
> > In my experience, containers trying to run stuff from shadow-utils in
> > their entrypoint/startup scripts tend to be a reason for containers to
> > *not* run on OpenShift/OKD without additional adjustments.
> >
> > A related (and more common) issue are images that expect to run with a
> > particular named user (or UID) determined during the build process
> > (again, most likely created using shadow-utils).
> >
> > I'm not familiar with Rancher but at least for OpenShift, I don't think
> > the availability of shadow-utils is very useful. At run time, you can't
> > use the shadow-utils at all and whatever you do with it during build
> > time is unlikely to be helpful (and actively harmful more often than
> > not) at run time when OpenShift assigns you an arbitrary UID.
>
> It's basically required for building containers that will work at
> runtime where OpenShift assigns an arbitrary UID.
>
> For example, in my containers, I *build* and create a "runtime user"
> with the UID 1000, and then set things up to use that context at the
> end. OpenShift uses that for its dynamic UID assignment.
But you do not need shadow-utils for that. Even OpenShift
documentation shows simple echo is enough:
if ! whoami &> /dev/null; then
if [ -w /etc/passwd ]; then
echo "${USER_NAME:-default}:x:$(id -u):0:${USER_NAME:-default}
user:${HOME}:/sbin/nologin" >> /etc/passwd
fi
fi
https://docs.openshift.com/container-platform/3.10/creating_images/guidelines.html
(yeah, I know it's an old and obsolete version of docs)
--
Tomasz Torcz RIP is irrevelant. Spoofing is futile.
to...@pipebreaker.pl Your routes will be aggreggated. -- Alex Yuriev
___
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 Account Migration & Production Deployment Update: COMPLETE!
Dnia Sat, Mar 27, 2021 at 10:56:32AM -0700, Kevin Fenzi napisał(a): > On Sat, Mar 27, 2021 at 11:08:19AM +0100, Tomasz Torcz wrote: > > > > > > Notification via sms is... not too secure. ;( > > > https://www.vice.com/en/article/y3g8wb/hacker-got-my-texts-16-dollars-sakari-netnumber > > > > I didn't write SMS. SMS is terrible, it's the worst 2F channel nowadays. > > I meant push notification, when the message is sent through secure channel > > to your smart phone and you get popup asking for authorization. > > At least: > > > > - Google does that: > > https://s3.amazonaws.com/neowin/news/images/uploaded/2017/07/1500141361_google_mobile_prompt.jpg > > - Microsoft Suite (Teams, Outlook) on my corporate accounts: > > https://techcommunity.microsoft.com/t5/image/serverpage/image-id/46536iDD69C684B52CC495 > > - My banking app (for login and transfer authorizations) > > https://android.com.pl/apps/wp-content/uploads/2020/03/alior.jpg.webp > > > > This seem to be easiest and most secure 2FA, but requires cooperation > > with Android framework. Next in line are FIDO/Yubikeys, and OTP codes. > > Ah, ok. Well, not everyone has access to them. > > I have a android based phone, but it's de-googled, > so I can't get any google push notifications. Others > may have i-phones or... perhaps even no smart phone at all. ;) Both IOS and Tizen have some push notification frameworks, like Android. I'm not familiar with specifics, as their marketshare is insignificant here, less than 7% combined. Anyway, any solution is more usable than this peculiar way of combining password with OTP code. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. to...@pipebreaker.pl Your routes will be aggreggated. -- Alex Yuriev ___ 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 Account Migration & Production Deployment Update: COMPLETE!
Dnia Fri, Mar 26, 2021 at 01:47:08PM -0700, Kevin Fenzi napisał(a): > On Fri, Mar 26, 2021 at 09:34:49PM +0100, Tomasz Torcz wrote: > > Dnia Fri, Mar 26, 2021 at 03:26:53PM -0500, Brandon Nielsen napisał(a): > > > On 3/26/21 3:24 PM, Matthew Miller wrote: > > > > On Fri, Mar 26, 2021 at 02:48:39PM -0400, Christopher wrote: > > > [Snip] > > > > > * In many places, including accounts.fedoraproject.org, in order to > > > > > log in, you have to append the OTP to your password, so it doesn't > > > > > really play nice with password managers. > > > > > > > > This is pretty common in my experience; it seems like password managers > > > > should support this pattern. > > > > > > > > > > I can't say I have ever appended an OTP to a regular password, and I use > > > 2FA > > > everywhere I can. > > > > I second that. I've only seen OTP appending on FreeIPA's > > implementation of 2FA. Everywhere else it's first a normal password > > prompt, then second for 2FA code (or push notification to phone, which > > is way easier for user). > > Notification via sms is... not too secure. ;( > https://www.vice.com/en/article/y3g8wb/hacker-got-my-texts-16-dollars-sakari-netnumber I didn't write SMS. SMS is terrible, it's the worst 2F channel nowadays. I meant push notification, when the message is sent through secure channel to your smart phone and you get popup asking for authorization. At least: - Google does that: https://s3.amazonaws.com/neowin/news/images/uploaded/2017/07/1500141361_google_mobile_prompt.jpg - Microsoft Suite (Teams, Outlook) on my corporate accounts: https://techcommunity.microsoft.com/t5/image/serverpage/image-id/46536iDD69C684B52CC495 - My banking app (for login and transfer authorizations) https://android.com.pl/apps/wp-content/uploads/2020/03/alior.jpg.webp This seem to be easiest and most secure 2FA, but requires cooperation with Android framework. Next in line are FIDO/Yubikeys, and OTP codes. -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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 Account Migration & Production Deployment Update: COMPLETE!
Dnia Fri, Mar 26, 2021 at 03:26:53PM -0500, Brandon Nielsen napisał(a): > On 3/26/21 3:24 PM, Matthew Miller wrote: > > On Fri, Mar 26, 2021 at 02:48:39PM -0400, Christopher wrote: > [Snip] > > > * In many places, including accounts.fedoraproject.org, in order to > > > log in, you have to append the OTP to your password, so it doesn't > > > really play nice with password managers. > > > > This is pretty common in my experience; it seems like password managers > > should support this pattern. > > > > I can't say I have ever appended an OTP to a regular password, and I use 2FA > everywhere I can. I second that. I've only seen OTP appending on FreeIPA's implementation of 2FA. Everywhere else it's first a normal password prompt, then second for 2FA code (or push notification to phone, which is way easier for user). -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present
Dnia Sun, Mar 07, 2021 at 12:55:21PM -0500, Matthew Miller napisał(a): > On Sun, Mar 07, 2021 at 10:26:50AM +0100, Björn Persson wrote: > > > It can, but most people don't have a good setup for even local mail > > > delivery. Out of the box, we don't really do anything useful. > > It wouldn't take much. Install Postfix, and when Anaconda creates the > > first user account, have it add a mapping from root to that username in > > /etc/aliases. Then a variety of MUAs can pick up the emails from > > /var/spool/mail. > > Well but even then the user needs to know to look for local mail. That's not > a normal expecation for even many Linux folks these days. > > I think for desktop we'd be better off looking for a notification solution > that doesn't need mail as a transport layer. I have vague recollection of GNOME popup warning me about disk problems discovered by SMART. I see /usr/libexec/gsd-disk-utility-notify running in my session, that was probably the source of the notification. -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present
Dnia Fri, Mar 05, 2021 at 10:17:17AM -0500, Matthew Miller napisał(a): > On Fri, Mar 05, 2021 at 03:05:00PM +0100, Hans de Goede wrote: > > > mcelog.service loaded active running > > > Machine Check Exception Logging Daemon > > This is another one for which it is questionable to have it running, or is > > this a machine with > > ECC RAM ? And even then I'm not sure if it adds a lot of value, or if just > > like smartd it > > just logs some stuff into syslog (where normal users won't see it). > > I disagree that those logs are useless -- I often help normal users, and > running commands to look back in the logs for problems is a common > diagnostic step. This could be better, of course. They are useful. smartd even sends emails – that's how I was informed about one of my disks dying, few weeks ago, -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: Plymouth, themes and console clearing: https://bugzilla.redhat.com/show_bug.cgi?id=1933378
Dnia Thu, Mar 04, 2021 at 12:14:07PM -0800, Adam Williamson napisał(a): > Starting from a minimal install with plymouth omitted, adding just > plymouth itself pulls in 3 packages (plymouth, plymouth-core-libs, > plymouth-scripts) with an installed size of 621K. Adding plymouth- > system-theme pulls in 32 packages with an installed size of 24M. So > putting plymouth-system-theme in @core would substantially inflate the > size of @core in terms of both number of packages and overall installed > size. Removing plymouth from @core would not save a lot in terms of > packages or space. plymouth-theme-hot-dog is only 400 KiB ;) /ducks -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ 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: Meaning of Size Directories
Dnia Thu, Feb 25, 2021 at 06:20:34PM -0300, Sergio Belkin napisał(a): > Hi, > Tools such as ls or stat report the size of a directory. Of course it is > not the content size. It depends on the filesystem. For Cephfs, directory size _is_ the content size: % ls -lh drwxrwxr-x. 3 zdzichu zdzichu 90G 11-06 16:37 'Collection 1' drwxr-xr-x. 17 root root 11M 09-23 15:45 postfix drwxr-xr-x. 2 cherokee cherokee 15M 11-24 00:02 var_log_cherokee I do not know what btrfs reports as directory size. -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: systemd-resolved fallback DNS servers: usability vs. GDPR
Dnia Mon, Feb 22, 2021 at 09:45:58AM -0600, Michael Catanzaro napisał(a): > On Mon, Feb 22, 2021 at 12:05 pm, Tomasz Torcz wrote: > > 3) Configure DNS resolvers if you want to use DNS. > > Or dig deeper: why cloud-init disabled DNS on your installation? > > I'm pretty sure cloud-init just doesn't know how to configure > systemd-resolved at all. So I suspect this is a cloud-init bug. See: > https://pagure.io/fedora-server/issue/10. Quoting from Tadej's email to cloud@ list; #v+ $ cat /etc/NetworkManager/conf.d/99-cloud-init.conf # Created by cloud-init on instance boot automatically, do not edit. # [main] dns = none #v- So cloud-init at least tries to configure NM. This configuration would be passed down to resolved. But "dns = none" seems wrong. -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: systemd-resolved fallback DNS servers: usability vs. GDPR
Dnia Mon, Feb 22, 2021 at 10:58:09AM +0100, Tadej Janež napisał(a): > Hi, > > I would like to question the decision that was made by systemd > maintainers to remove the fallback DNS server list: > https://src.fedoraproject.org/rpms/systemd/c/14b2fafb3688a4170a9c15235d1c3feb7ddeaf9d > > And then backported to F33: > https://src.fedoraproject.org/rpms/systemd/c/ed795fb1fc9a2c20ebcac34bdf7e7c7ae17322a2?branch=f33 > > On F33, this actually breaks a working vanilla cloud instance by > removing the fallback DNS server list in a systemd upgrade, effectively > leaving the system with no DNS servers configured. > > I described this in more detail here: > https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/72MRKIFGPMFGBS7XJ5T5I23NVDXXWVGR/ Let's be careful not to go in circles. It seems you have "broken" configuration - no DNS servers are provided to the cloud image. So none are configured. Previously, systemd package provided a fallback DNS resolvers for that case. Then it stopped doing that. Now the circles - the change in systemd package was the outcome of discussion here on -devel list. In this discussion some people had a position "if I do not provide DNS servers, I don't want DNS to work". Which is resonable and expected in high-control situations. Providing the workaround again would go against wishes of those people. From their perspective your non-resolving cloud image is exactly as you want it. As you configured it. > > Possible solutions that come to mind: > 1) Use different defaults for different Fedora editions, e.g. container > and cloud images include the fallback DNS servers list while > workstation (and similar) images don't. > 2) Pick a reputable DNS resolver that preserves users' privacy and > doesn't log anything and configure it as a fallback DNS server. 3) Configure DNS resolvers if you want to use DNS. Or dig deeper: why cloud-init disabled DNS on your installation? -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ 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: Don't update to the latest f33!
Dnia Thu, Feb 18, 2021 at 02:37:54PM +, Sven Kieske napisał(a): > On Do, 2021-02-18 at 08:30 -0600, Michael Catanzaro wrote: > > Fedora will never configure static DNS servers for you in > > > > resolved.conf. That config file was manually edited with improper > > > > syntax to wind up in this broken state. My guess is that it was edited > > > > by the VPS provider, but who knows. > > still, as a user and sysadmin I would expect > any service to loudly complain (at least in a logfile) > about syntax errors in it's configfile, no matter how > the wrong config got there in the end, if by cfgmgmt, hand edited > or other system tools. > > but there is no such warning, or did I miss this information? It complains for me: % rg ^DNS= /etc/systemd/resolved.conf 19:DNS=1.1.1.1,1.0.0.1 systemd-resolved[23515]: Failed to add DNS server address '1.1.1.1,1.0.0.1', ignoring: Invalid argument This is with systemd-246.10-1.fc33.x86_64 -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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 35 Change proposal: POWER 4k page size (System-Wide Change proposal)
Dnia Fri, Feb 12, 2021 at 10:16:26PM +0100, Daniel Pocock napisał(a): > > > On 12/02/2021 21:19, Justin Forbes wrote: > > On Fri, Feb 12, 2021 at 10:21 AM Ben Cotton wrote: > >> > >> https://fedoraproject.org/wiki/Changes/Power4kPageSize > >> > >> == Summary == > >> > >> On ppc64le, the kernel is currently compiled for 64k page size. > >> > >> This change proposes using the more common 4k page size. > >> > >> Some things, like the AMD Radeon GPU drivers, firmware or related > >> code, appear to be completely non-functional on the 64k page size. > >> Insufficient upstream developers are testing such issues on this > >> architecture. > > > > Just as there are many things that expect the 64K page size. I am not > > doing this. > > > > Justin > > Can you please identify some of the things that expect 64k? > > If the GPU drivers don't work that makes it a complete non-starter for > many workstation users, or they have to compile their own kernels or > obtain custom kernels from another user. Or just fix the GPU drivers. They're open source, after all. -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ 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: Orphaned packages looking for new maintainers
On Mon, Feb 08, 2021 at 07:07:40PM +0100, Miro Hrončok wrote: > On 08. 02. 21 19:03, Gwyn Ciesla via devel wrote: > > I believe Tomasz was asking about the many packages that indirectly require > > uw-imap. Exactly, sorry for not communicating clearly enough. > Oh. Right, php indeed. Thanks. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaned packages looking for new maintainers
What's the magic deep dependency for uw-imap? Is it PHP? -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ 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: Scale ZRAM to Full Memory Size — arbitrary scaling
On Thu, Jan 28, 2021 at 11:04:34AM -0500, Rob Crittenden wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, Jan 28, 2021 at 03:20:38PM +0200, Alexander Bokovoy wrote:
> >> With today's OpenQA tests I can point out that using zram on 2048MB RAM
> >> VMs actually breaks FreeIPA deployment:
> >> https://openqa.fedoraproject.org/tests/763006#step/role_deploy_domain_controller/35
> >>
> >> OpenQA uses 2048MB RAM for QEMU VMs and this was typically OK for
> >> FreeIPA deployment with integrated CA and DNS server. Not anymore with
> >> zram activated:
> >>
> >> Jan 27 21:17:47 fedora zram_generator::generator[25243]: Creating unit
> >> dev-zram0.swap (/dev/zram0 with 1384MB)
> >>
> >> which ends up eating 2/3rds of the whole memory budget and FreeIPA
> >> installer fails:
> >>
> >> 2021-01-28T02:18:31Z DEBUG ipa-server-install was invoked with arguments
> >> [] and options: {'unattended': True, 'ip_addresses': None, 'domain_name':
> >> 'test.openqa.fedoraproject.org', 'realm_name':
> >> 'TEST.OPENQA.FEDORAPROJECT.ORG', 'host_name': None, 'ca_cert
> >> 2021-01-28T02:18:31Z DEBUG IPA version 4.9.1-1.fc34
> >> 2021-01-28T02:18:31Z DEBUG IPA platform fedora
> >> 2021-01-28T02:18:31Z DEBUG IPA os-release Fedora 34 (Server Edition
> >> Prerelease)
> >> 2021-01-28T02:18:31Z DEBUG Available memory is 823529472B
> >> ...
> >> 2021-01-28T02:18:31Z DEBUG The ipa-server-install command failed,
> >> exception: ScriptError: Less than the minimum 1.2GB of RAM is available,
> >> 0.77GB available
> >> 2021-01-28T02:18:31Z ERROR Less than the minimum 1.2GB of RAM is
> >> available, 0.77GB available
> >> 2021-01-28T02:18:31Z ERROR The ipa-server-install command failed. See
> >> /var/log/ipaserver-install.log for more information
> >
> > Enabling zram doesn't really "take away memory", because no pre-allocation
> > happens.
> > If there is no physical swap, then adding zram0 should just shown additional
> > swap space, so I don't think it could cause the check to fail.
> > But if there is physical swap, the zram device is used with higher
> > preference
> > than the physical swap. So I think the explanation could be that the VM has
> > a swap partition. Before, some pages would be swapped out to zram, and some
> > would
> > be swapped out to the "real" swap. The fraction of RAM used for compressed
> > zram
> > would be on the order of 25% (zram-fraction=0.5 multiplied by typical
> > compression 2:1).
> >
> > But now the kernel sees more zram swap, so it inserts pages there, taking
> > away
> > more of RAM, instead of saving pages to disk. So more memory (maybe 50%
> > RAM) is
> > used for the unswappable compressed pages. But this shouldn't break things:
> > if there is enough pressure, pages would be swapped out to the physical
> > swap device
> > too.
> >
> > Assuming that this guess is correct, the check that ipa-server-install is
> > doing should be adjusted. It should use the total available memory (ram +
> > all kinds
> > of swap) in the check, and not just available uncompressed pages.
> > Or if it wants to ignore disk-based swap for some reason, it should use
> > ram + zram + in-memory-zwap in the check.
>
> For bare metal IPA uses the python3-psutil call:
> psutil.virtual_memory.available()
>
> I don't know how/if psutil reports zram (or cgroup v1 and v2 for that
> matter).
psutil (in general) reports data from /proc/meminfo; available come
from MemAvailable: in that file. This is defined in kernel as:
MemAvailable: An estimate of how much memory is available for starting new
applications, without swapping. Calculated from MemFree,
SReclaimable, the size of the file LRU lists, and the low
watermarks in each zone.
The estimate takes into account that the system needs some
page cache to function well, and that not all reclaimable
slab will be reclaimable, due to items being in use. The
impact of those factors will vary from system to system.
Notice "without swapping" in second line. Next question, how zram impacts
reporting of MemAvailable by kernel?
--
Tomasz Torcz “God, root, what's the difference?”
to...@pipebreaker.pl “God is more forgiving.”
___
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 virt-install + ks has some problem switching root
On Wed, Jan 13, 2021 at 10:16:43AM +, Richard W.M. Jones wrote: > Sorry for this rather ill-defined bug report, but I'm hoping someone > will recognize the symptoms or at least suggest a way to debug this. > > Ever since Fedora 33 was released we've been unable to produce a > working virt-builder template. The template that we have made fails > at switch root. > > template: https://builder.libguestfs.org/fedora-33.xz > bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1911177 > > An additional problem is I cannot find any way to debug the problem. In this image, initrd-switch-root.service fails because "/sysroot does not contain /etc/os-release". This is visible when you boot with "systemd.log_level=debug systemd.journald.forward_to_console=1" as described on https://freedesktop.org/wiki/Software/systemd/Debugging/ > Something (systemd? dracut?) asks for a root password in order to get > to the emergency shell, and I can find no way around this nor any > password which works. I wish there was a "stop asking for a password" > option on the kernel command line. This one is weird. I tried "rd.shell" and "rd.break", which should just drop to dracut shell, but it didn't work. BTW, partition setup looks weird, too. vda1 is 1MB empty partition, then vda2 is /boot and vda3 is rootfs. Is this how we organise disks by default? -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ 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: Unify the GRUB configuration files location across all supported architectures (System-Wide Change proposal)
On Wed, Dec 30, 2020 at 05:08:03PM -0700, Chris Murphy wrote: > > Upgrades of customized configurations that deviate significantly from > > defaults aren't supported. It's best effort. We can't be blocking on > > people's customizations. > > > > I think we can come pretty close to atomically renaming > > > > /EFI/fedora/grub.cfg /EFI/fedora/grub.cfg.old > > /EFI/fedora/grub.cfg.new to /EFI/fedora/grub.cfg > > > > And at least ensure the user can boot the old one, but even this I > > think is pretty unlikely. It's really a teeny tiny window of failure > > opportunity. And based on my reading of rename() if the files are > > already all present, and all we're doing is renaming them, there > > shouldn't be a case where grub.cfg is either missing entirely or zero > > bytes. > > > > But dm-log-writes can help confirm or deny this. What I don't know is > > if this can be done with bash. The convert script probably needs to be > > done in C. Or at least the rename and sync parts. > > > Oh I forgot the part about the convert script testing for custom > grub.cfg. Maybe it's possible to parse it first, and if it's custom, > bail. If it's non-custom then convert it. > > And a variation where we have an opt-in for this convert script for > Fedora 34 cycle. And then ship it and do the conversion in Fedora 35. > > I think either never fixing this, or never updating systems to the > "new way" are both untenable. We saw with the BLS switch many users > depend on doing in place upgrades. Many were pushing 4 or more years. I think conversion script would be needed for people doing upgrades. But first of all - documentation! It should be clear what GRUB expectations are, where the config file should be and so on. BLS conversion was hard because it was undocumented. One of the crucial scripts (grubby? install-kernel?) has been changing behaviour upon existence of some file or directory in /boot (was is loader/?). It was undocumented and so counter-intuitive that cannot recall details after merely two years. Right now the best information about how Fedora boots and what happens on kernel installation can be founds on AdamW's blog. This is not perfect :( -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: Enable systemd-oomd by default for all variants(System-Wide Change)
On Thu, Dec 24, 2020 at 06:01:51PM -0500, James Cassell wrote: > > On Tue, Dec 22, 2020, at 10:45 AM, Michael Catanzaro wrote: > > Each gnome-terminal tab runs in its own cgroup: > > > > │ │ │ ├─app-org.gnome.Terminal.slice > > │ │ │ │ > > ├─vte-spawn-1d1d5519-71d2-4035-929a-8a9ae5bc3822.scope > > │ │ │ │ │ ├─7848 bash > > │ │ │ │ │ └─7889 less /etc/hosts > > │ │ │ │ > > ├─vte-spawn-03fe4cc9-0400-4723-ac9b-e929b850ca02.scope > > │ │ │ │ │ ├─7892 bash > > │ │ │ │ │ ├─7927 systemd-cgls > > │ │ │ │ │ └─7928 less > > │ │ │ │ └─gnome-terminal-server.service > > │ │ │ │ └─7843 /usr/libexec/gnome-terminal-server > > > > Glad to hear gnome-terminal separates tabs. Any idea if tilix does the same? Yes, with Tilix there are also a number of vte-spawn-….scope units. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. to...@pipebreaker.pl Your routes will be aggreggated. -- Alex Yuriev ___ 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 Mon, Dec 21, 2020 at 11:28:51AM -0500, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/RPMCoW > # dnf-plugin-reflink (a new package): > https://github.com/facebookincubator/dnf-plugin-cow/ Does not exists, but I've just noticed it mentioned in Current Status on Wiki: 3.2 Github repo needs to be published -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ 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: Lenovo portals available in Europe
On Mon, Dec 14, 2020 at 01:15:26PM -0500, Mark Pearson wrote: > Hi Fedoran's (hopefully I have the right terminology now :)) > > Some more portal's are up now in Europe. Hopefully I get all the > countries right below - I had to translate from a table into something > text friendly. Any mistakes are mine :) Yay!! > > If your country is not listed that's likely because we don't have a web > ecommerce presence there (e.g Poland). Let me know if you think that's > not the case and I can dig but I don't yet have a way to get discounts > for anything that is not done via e-commerce. :-( I hope there will be a way. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. to...@pipebreaker.pl Your routes will be aggreggated. -- Alex Yuriev ___ 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: ntp replacement (Self-Contained Change)
On Wed, Dec 02, 2020 at 10:00:04AM -0500, Neal Gompa wrote: > > == Release Notes == > > TBD > > > > Makes sense, though I think the release notes section would be pretty > easy to write: > > "The classic ntpd service was formerly provided by the ntp package. > The ntp software has significant security issues and development seems > moribund. It has now been replaced with the ntpsec package, an > actively maintained fork of the ntp software. No functional changes > are expected." There ARE functional changes. Mainly removal of long-obsolete drivers, full list can be found at: https://docs.ntpsec.org/latest/ntpsec.html#incompatible https://www.ntpsec.org/removal-plan.html -- Tomasz TorczTo co nierealne – tutaj jest normalne. to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne. ___ 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: Route all Audio to PipeWire (System-Wide Change)
On Sun, Nov 22, 2020 at 06:01:18PM +0100, Ralf Corsepius wrote: > On 11/20/20 5:26 PM, Ben Cotton wrote: > > > The pulseaudio package will be uninstalled and pipewire-pulse will be > > installed. > > > > pipewire-pulse does not yet implement all the features of pulseaudio > > but it is expected that > > comparable functionality will be implemented later. Most notable > > features that are likely > > not going to be available for fedora 34 > IMO, this alone disqualifies this plan. > > Fedora should be a stable end-user distro and not a testing site for eager > devs to test their immature and incomplete works. I think Fedora should establish strong "no regressions" rule when replacing system software like this. PulseAudio has had 15 years of development, features and fixes. It is hard to believe pipewire is as capable as a replacement now. Of course we would need to start with collecting the use cases, and this will be different for every user. For example, I frequently use my laptop with 3 sound devices present: built-in speakers, speakers connected to USB-C dock and bluetooth headphones*. I use pavucontrol to route applications to proper output/input and I expect this to work the same with PW. This is important to me. On the other hand, I do not use AC3 passthrough when watching movies and I'm not so much interested in power saving through dynamic latency/timers adjustment and suspending outputs. If this ceased to work, _I_ wouldn't notice. But for someone this may be crucial. The same for equalizer modules. Or volume ramp up. Or multiple device combining. And so on. Right now "How to test" section of Change Proposal contains only very rudimentary cases like "check if rhythmbox plays". This is not enough when replacing as potent software as PulseAudio. * - for some BT codecs I need pulseaudio-module-bluetooth-freeworld -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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: video meeting to discuss Matrix/Element and IRC
On Thu, Nov 19, 2020 at 08:00:24PM +, Tom Hughes via devel wrote: > On 19/11/2020 19:49, Neal Gompa wrote: > > > The GNOME-based one is Fractal, which is not available in Fedora as of > > right now. That said, the Qt based ones are in way better shape than > > the GNOME one. And QGnomePlatform should make them work reasonably > > well... > > My problem, at least on this hidpi laptop, is that the bit of the > window edge that I need to grab to resize it is only about one pixel > wide so virtually impossible to grab. Native gnome windows have a > much wider area I can grab. > > It might be better on my desktop that isn't hidpi and has a mouse > instead of a trackpad. You don't have to grab by the edge to resize, GNOME has useful features: - winkey+left mouse button inside the window let you move it (no need to target header bar) - winkey+middle mouse button inside window let you resize closest edge This unfortunately breaks in two cases: - you have scroll emulation enabled on middle button+trackpoint; or - you don't have middle button on your laptop :( -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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: Retiring ntp
On Mon, Nov 02, 2020 at 11:58:53PM -0600, Alex Thomas wrote: > Question : I know that FreeIPA at one point did not work well with > chrony and required the installation of ntp. This might cause an > issue. That's not a problem anymore. Support for chrony was added in 4.7.0, released in 2018, so we are good. https://www.freeipa.org/page/Releases/4.7.0#Time_server_change_to_chronyd -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: Retiring ntp
On Mon, Nov 02, 2020 at 10:14:05AM -0500, Steven A. Falco wrote: > On 11/2/20 9:33 AM, Miroslav Lichvar wrote: > > I'm not sure how many users of ntp are there. As a replacement, we > > could package ntpsec. It is an actively maintained fork of ntp which > > has removed a lot of code and fixed or avoided most of the issues in > > ntp. What I don't like much about it is that they kept the mode-6 > > protocol of NTP, which allows traffic amplification and is still > > causing problems on Internet, but I think the code and the project are > > definitely in a better shape than ntp. I can help with the packaging > > or review, and as a comaintainer if there is a volunteer for the > > role of the primary maintainer. > > > > I use ntp heavily for multiple stratum 1 timeservers here. If you > drop ntp, I will have to build my own from source. Not a big problem, > but I'd personally like to see ntp stay available in Fedora. Would NTPSec (https://www.ntpsec.org/accomplishments.html) work for you? -- Tomasz Torcz 72->| 80->| to...@pipebreaker.pl 72->| 80->| ___ 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: libvirt and systemd-resolved integration?
On Tue, Oct 06, 2020 at 10:04:19PM +0200, Juan Orti Alcaine wrote: > Hello, > > In the network bridges that libvirt creates there's a dnsmasq daemon to > resolve the VM's IPs. Is there any way to signal systemd-resolved from > libvirt to say that in the bridge interface there is a DNS server and a > domain? Related, there is nss-mymachines: https://www.freedesktop.org/software/systemd/man/nss-mymachines.html It resolves IPs of instances registered with machined. Libvirt already registers virtual machines with machined. But as I see, libvirt does not provide IP addresses during registration. Maybe this could be fixed? -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Sat, Oct 03, 2020 at 11:17:44AM +0200, Marius Schwarz wrote: > Am 02.10.20 um 11:12 schrieb Petr Pisar: > > On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote: > >> On 10/1/20 5:52 AM, Marius Schwarz wrote: > >>>> Is it possible to boot from the stick and then perform a grub-install > >>>> with an old grub? > >>>> > >>> This attempt failed too: > >>> > >>> # grub2-install /dev/sda > >>> grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert > >>> nicht. Bitte geben Sie --target oder --directory an. > >>> > >>> and that file seems not to be part of any package. There is only one for > >>> "i386-pc". > >> You can't (and must not!) use grub2-install on an EFI system. > > Of course you have. How else would you get GRUB EFI executable onto the boot > > partition and register it into boot environments? > > > > But the correct invocation for EFI systems is different. You just use > > "grub2-install" without the disk device name. > If you do not state the devicename, how does grub choose the correct > drive? I don't want to overwrite the bootloader on the ssd. There is only one correct ESP partition in EFI system to install bootloader to. You can read the code finding it at https://github.com/rhboot/grub2/blob/master/util/grub-install.c#L1029 -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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: Donate 1 minute of your time to test upgrades from F32 to F33
On Fri, Oct 02, 2020 at 09:50:19AM +0200, Miroslav Suchý wrote: > But very likely you get some dependency problem now. In that case, please > report it against the appropriate package. Error: Problem: problem with installed package mosquitto-1.6.10-1.fc32.x86_64 - mosquitto-1.6.10-1.fc32.x86_64 does not belong to a distupgrade repository - nothing provides libwebsockets.so.16()(64bit) needed by mosquitto-1.6.12-1.fc33.x86_64 Correct package to report against would be mosquitto or whatever provides libwebsockets? -- Tomasz Torcz Morality must always be based on practicality. to...@pipebreaker.pl — Baron Vladimir Harkonnen ___ 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 Mon, Sep 28, 2020 at 10:05:09AM -0500, Michael Catanzaro wrote: > [1] https://fedoraproject.org/wiki/Changes/systemd-resolved#Split_DNS This link second time… there's a lot of text, but no example of configuration file for split dns. Is it because end user cannot easily configure split dns permanently? -- Tomasz Torcz “Never underestimate the bandwidth of a station to...@pipebreaker.plwagon filled with backup tapes.” — Jim Gray ___ 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 Mon, Sep 28, 2020 at 07:57:13AM -0500, Ian Pilcher wrote: > 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. Having read your email, I've checked my /etc/resolv.conf and _removed_ the NM comment. Never bothered to touch the comment before, as I'm using systemd-networkd for networking on the server. I would say that leaving the comment is a common pattern. There's not much there actually, only search domain and 'nameserver ::1', where dnsmasq listens, providing split-horizon for my network and pihole blacklisting of advertisment networks. But yeah, there are no better ideas how to handle resolv.conf on upgrades. -- Tomasz Torcz “Never underestimate the bandwidth of a station to...@pipebreaker.plwagon filled with backup tapes.” — Jim Gray ___ 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: The Future of the Java Stack (also regarding ELN and RHEL)
On Fri, Sep 11, 2020 at 10:16:02AM +0200, Mikolaj Izdebski wrote: > You get a side tag in Koji where you can have private build-only > dependencies that are discarded (filtered) once they are no longer > needed, after module build is done. For build-only packages most of > security vulnerabilities are not exploitable easily, or at all, > therefore are low-severity, which greatly limits maintenance work > required to address them. For example, if upstream tests are ran on an > obsolete, 12-years old version of Tomcat, I don't need to skip tests, > but I can package old Tomcat and run the tests. Whoha! Let's step back for a minute and look at this example. What are the reasons to run tests? To make sure the package will run correctly.. Why run tests on 12-years old version instead of on current one? Probably because tests fail on current version? Will the end user run the package on obsolete Tomcat or on the current one? Of course on the current one. The one on which tests fail. Tests in this case are worthless, they are not testing the real situation. Disabling tests is no worse than testing on obsolete version. Relying on such tests is a disservice for the end user. The point of testing is to validate code in real situation. Crafting special, unrealistic environment (12 years old Tomcat) just to have test pass is missing the point of tests. -- Tomasz Torcz There exists no separation between gods and men: to...@pipebreaker.pl one blends softly casual into the other. — Frank Herbert ___ 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: The Future of the Java Stack (also regarding ELN and RHEL)
On Thu, Sep 10, 2020 at 04:38:04PM +0200, Mikolaj Izdebski wrote: > > > > > > In modular Fedora that's (effectively) not true. Packages that only exist > > > for the sake of building other packages (i.e. build-only dependencies) > > > can be > > > retained in the Fedora build system and never left it. That means those > > > packages are never made available to Fedora users and thus a service > > > level for > > > them is significantly lower. E.g. no security fixes, not bug fixes, no > > > integration, not tests, no API/ABI stability. The only requirement is that > > > they can be built and used for building other packages. > > > > > > So, if user wants to locally rebuild the package, they won't be able to > > do it? Because BuildRequired packages won't be available? > > Modules can be built locally with "fedpkg module-build-local", which > downloads required dependencies from Koji and installs them in mock > chroot. These packages are not installed directly (outsides of chroot) > on users systems. OK, cool, thanks for dispeling my doubts. -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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: The Future of the Java Stack (also regarding ELN and RHEL)
On Thu, Sep 10, 2020 at 04:03:46PM +0200, Petr Pisar wrote: > In non-modular Fedora all packages that we have in Fedora build system (Koji) > are tagged into Fedora repositories and made available to all users on their > computers for any purpose. That implies that all packages in Fedora build > system > must be fully supported including addressing all security issues. > > In modular Fedora that's (effectively) not true. Packages that only exist > for the sake of building other packages (i.e. build-only dependencies) can be > retained in the Fedora build system and never left it. That means those > packages are never made available to Fedora users and thus a service level for > them is significantly lower. E.g. no security fixes, not bug fixes, no > integration, not tests, no API/ABI stability. The only requirement is that > they can be built and used for building other packages. So, if user wants to locally rebuild the package, they won't be able to do it? Because BuildRequired packages won't be available? -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ 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: About the Future of Communishift
On Fri, Sep 04, 2020 at 02:08:02PM +0200, Pierre-Yves Chibon wrote: > > > I don't really expect an answer. From my experience, it's impossible > > to get straight, yes/no, binary answer from lawyers. > > Thus the slow process :( > The goal of the email was to inform about the current situation as we saw the > topic raised in a few places lately. Of course, thank Aoife for that information! It is much better to have news, even unfortunate ones, than to be kept in the dark. This update was appreciated. -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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: About the Future of Communishift
On Fri, Sep 04, 2020 at 07:16:02AM -0400, Neal Gompa wrote: > On Fri, Sep 4, 2020 at 7:10 AM clime wrote: > > > > On Fri, 4 Sep 2020 at 12:59, clime wrote: > > > > > > On Fri, 4 Sep 2020 at 12:48, Aoife Moloney wrote: > > > > > > > > However, the General Data Protection Regulation (GDPR) [3] and the > > > > California > > > > Consumer Privacy Act (CCPA) [4] basically makes the Fedora > > > > Infrastructure team > > > > (and thus Red Hat) responsible for the content hosted by any services > > > > running in > > > > our infrastructure. In other words, the Fedora Infrastructure team > > > > would be > > > > responsible to answer all GDPR/CCPA related requests and requirements > > > > for any > > > > and all services running in communishift (services that the team has 0 > > > > knowledge > > > > about, that's the whole goal of communishift). > > > > My read of this is that right now, there will be no way for the > community to run applications in Fedora Infrastructure in a way that > CPE can be divorced from it completely. That is because their goal of > running only OpenShift and then not caring about what's inside is > legally not possible. Hmm. But how, for example, cloud providers are able to provide infrastructure without taking responsibility for what's hosted? I don't think GCP is handling any GPDR/CCPA requests for clients' stuff… I don't really expect an answer. From my experience, it's impossible to get straight, yes/no, binary answer from lawyers. -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ 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: services impact on startup times
On Thu, Sep 03, 2020 at 11:25:59AM +0100, Peter Oliver wrote: > On Wed, 2 Sep 2020, John M. Harris Jr wrote: > > > What's meant is that people are still setting up scheduled tasks by running > > `crontab -e` and similar. > > I think most such users would quickly figure out they can `yum install > /usr/bin/crontab`, though. It's even more easy/obvious on Fedora: % crontab -e zsh: crontab: command not found... Install package 'cronie' to provide command 'crontab'? [N/y] -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. to...@pipebreaker.pl Your routes will be aggreggated. -- Alex Yuriev ___ 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-review fails with "warning: line 16: Possible unexpanded macro in: Requires .."
On Fri, Aug 28, 2020 at 02:30:20PM -, Martin Gansser wrote:
> the macro "%{vdr_apiversion}" is included in the package vdr-devel
>
> rpm -qf /usr/lib/rpm/macros.d/macros.vdr
> vdr-devel-2.4.4-1.fc32.x86_64
There is no such version in Fedora (is this a local build)?
Latest in F32 is vdr-2.4.1-5.fc32, and the spec has BR >= 2.4.3.
For Rawhide, you just built vdr-2.4.4-1.fc34 yesterday – it may not be
available in Rawhide compose yet.
--
Tomasz TorczTo co nierealne – tutaj jest normalne.
to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne.
___
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: docker.io/library/fedora:rawhide outdated vs registry.fp.org/fedora:rawhide
On Wed, Aug 19, 2020 at 01:01:00PM +0100, Daniel P. Berrangé wrote: > I have a docker recipe that does not much more than: > > FROM fedora:rawhide > RUN dnf -y install ...blah... I'm not addressing the core of your email, but… using FROM fedora:rawhide is not a good practice because of two reasons: – it's not describing specific version. 'rawhide' is changing in time, so your containers are not reproductible - building twice can produce something different each time - you do not specify full repository address, so you get whatever is default. As you noticed, in different environemnts you get different results. In short, 'fedora:rawhide' is not enough to get specific image, the result is quite random. -- Tomasz TorczTo co nierealne – tutaj jest normalne. to...@pipebreaker.pl Ziomale na życie mają tu patenty specjalne. ___ 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
