On Tue, Jun 9, 2020 at 9:42 PM TI_Eugene wrote:
>
> What's happened with koji?
Koji has a scheduled outage due to the
(well) documented datacenter move. At
any single point the services will be in
"interesting" operational modes.
___
devel mailing list
On Mon, Jun 15, 2020 at 7:48 PM Ben Cotton wrote:
> == Summary ==
> %cmake macro will be adjusted (-B parameter)
> to use separate build folder (already standardized
> %{_vpath_builddir} macro).
While there is certainly no requirement for different
distributions to work the same, as I recal
On Mon, Jun 15, 2020 at 7:48 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/Fedora-Retired-Packages
>
> == Summary ==
> All retired packages are obsoleted by `fedora-retired-packages`.
>
I am in favor of the intention that when you upgrade,
those packages from previous releases a
On Wed, Jun 17, 2020 at 5:41 AM Igor Raits
wrote:
>
> %if (0%{?rhel} && 0%{?rhel}) <= 8 || (0%{?fedora} && 0%{?fedora} <= 32)
>
Yes, I have written such spec file lines, and while
they are correct, they tend to be ugly to parse for
humans.
While I know it is personal preference, I tend to
prefe
On Fri, Jun 26, 2020 at 2:46 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/BtrfsByDefault
>
A few claims (without justification):
There is no "average" Fedora user.
There is no "average" Fedora system.
There is also no "average" workload on the
(non) average system (some peop
On Tue, Jul 7, 2020 at 7:04 PM Till Maas wrote:
>
> Hi,
>
> in https://pagure.io/fesco/issue/2410 I proposed to name the dist-git
> branch for Fedora Rawhide "rawhide" to clarify the purpose of that
> branch. There was also some feedback that Rawhide might not be the best
> name and it could be re
On Sat, Jul 11, 2020 at 1:50 AM John M. Harris Jr wrote:
>
> Why should I have to switch the system that's being used, and potentially
> break these servers, just because a package isn't being compiled anymore? It
> still works, and it works very well. It has less overhead than php-fpm, even!
>
On Sat, Jul 11, 2020 at 9:11 PM John M. Harris Jr wrote:
> None of this is relevant ... (to) ... a package which is ...
> widely used, however.
You keep making that assertion. Please provide
the audited numbers from a reputable source(*).
(*) Preferably for sites that actually are more than
On Tue, Mar 31, 2020 at 3:57 PM Kevin Kofler wrote:
> But ideally
You seem to have a lot of thoughts about changes
and improvements to the process.
When should the RPMFusion community expect
you to complete those improvements?
___
devel mailing l
On Tue, Mar 31, 2020 at 6:43 AM Panu Matilainen wrote:
> Based on rpm-specs-latest.tar.xz from this morning, there are thirtysome
> packages relying on this behavior, which will need fixing to be
> buildable with 4.16.
Is there a list of those thirty something packages
somewhere so that those pa
On Sun, Apr 5, 2020 at 9:03 AM Leigh Scott wrote:
> Aren't external kernel modules banned by fedora packaging rules?
My recollection (from some time ago) was there was
a process to request a (short term) exception to
allow one to ship a kernel module if the kernel
module developer (not the packa
On Fri, Apr 10, 2020 at 2:12 AM Todd Zullinger wrote:
> Checking each of those deps, openssh-clients grew a dep on
> libfido2, which in turn requires u2f-hidraw-policy that is
> provided by systemd. That looks like the main chain which
> leads to the additional packages installed in a mock chroo
On Mon, May 11, 2020 at 4:16 PM Alex Scheel wrote:
> Abstaining is in two categories:
There is (at least) one additional category, which
is that the issue involves various levels of self
interest. Technically that is really called a recusal,
but the result is the same when it comes time
to
On Mon, May 11, 2020 at 7:40 PM Chris Murphy wrote:
> Bias is not the same thing as a conflict of interest. And it doesn't
> inherently result in unfairness.
Sometimes it is a matter avoiding even the appearance
of impropriety that could be raised at a later date to
question the process/motives/
On Mon, Jan 6, 2020 at 4:22 PM drago01 wrote:
> What does windows do? Is it the equivalent of the discard mount option or is
> it more like fstrim?
Well, as I understand it(*), it's complicated, and there are a
lot of various tuning knobs one can use to change behavior.
But typically, with volu
On Tue, Jan 7, 2020 at 9:00 AM Kevin Kofler wrote:
> I think increasing the size of the live images, also affecting the download
> time and the time to write the image to media (even USB sticks are not
> instant), to get a one-time installation speedup is a very bad tradeoff.
While not exactly t
On Sat, Feb 8, 2020 at 5:08 PM Sérgio Basto wrote:
> and why gradle was retired ? is easy unretire it ?
Announced here (with reasons):
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/thread/BMJXGWKXXFOOBQON3XFYPFBOWEZMAKKU/
On Tue, Feb 11, 2020 at 5:10 PM Chris Murphy wrote:
> A further possibility as it relates to hibernation, is having systemd
> activate a swap partition (or even a swapfile) only at hibernation
> time. That would block it from being used during normal usage,
> preserving it (in effect) for just th
On Tue, Mar 10, 2020 at 3:07 AM Orion Poplawski wrote:
> One notable change is that it appears that perl-devel ->
> perl-interpreter no longer brings in the AutoLoader, blib, FindBin,
> sigtrap, Tie::Scalar, and perhaps other modules. Is that intentional?
The changelog certainly documents that
On Fri, Mar 20, 2020 at 3:20 PM Rob Crittenden wrote:
> Closing a bug doesn't clear the needinfo.
I consider that a mis-feature, but I have
learned to live with it.
> As a package owner I like the daily reminder. If it only happened
> monthly then bad timing could make it so I miss a reminder f
On Tue, Mar 28, 2023 at 2:01 PM Zbigniew Jędrzejewski-Szmek
wrote:
> Hmm, that'd mean thousands of pull requests… I think if we agree to
> this, it would make sense to just push a fix directly. Each pull request
> ticket is a few mails, and with 8096 expected pull requests, that is
> quite a lot
On Wed, Apr 26, 2023 at 9:04 AM Alexander Bokovoy wrote:
>
> Hi,
>
> This morning I woke up to find that packages I maintain were orphaned
> out of blue. Nobody contacted the maintainers, nobody raised any tickets
> to releng, as far as I can see. Yet, releng ran the orphaning from what
> I saw in
On Wed, May 10, 2023 at 3:56 PM Neal Gompa wrote:
> At least in the upstream kiwi project, we encountered problems making
> bigger ESPs because not all UEFI implementations handle FAT32 (despite
> it being part of the spec). In particular, there were a few server
> boards and especially AWS EC2 t
On Thu, May 11, 2023 at 3:10 PM Lennart Poettering wrote:
>
> On Mi, 10.05.23 17:54, Chris Murphy (li...@colorremedies.com) wrote:
> >
> > Read-only drivers, which are the only drivers under discussion here,
> > aren't a per se problem because they can't modify the file
> > system. So they have no
On Sat, May 13, 2023 at 7:02 PM David Duncan wrote:
>
> Now that awscli2 is out and functional.
Excellent! I will finally be able to stop
installing a local version.
> Gwyn and I are thinking it's time to retire the original
> awscli package in favor of this one. We are thinking
> that it will
On Wed, May 24, 2023 at 7:23 PM Tom Stellard wrote:
> What's the process for selecting a new Program Manager?
From the words that have been shared at:
https://docs.fedoraproject.org/en-US/council/fpgm/
the position itself has been eliminated.
The important responsibilities will (presumably)
On Wed, May 24, 2023 at 9:50 PM Mattia Verga via devel
wrote:
> Wait, what?? Someone at RH wakes up in the morning and decides to cut
> one of the key roles (or better, THE) of Fedora community and this goes
> completely unannounced, unnoticed and without any backup plan?
I do understand why Red
; On Wed, May 24, 2023 at 9:34 PM Gary Buhrmaster
>> wrote:
>> >
>> > I do understand why RedHat itself will not announce
>> > who got laid off, but the Council members should have
>> > been informed (I hope!) at the time, and should have
>> > worked
On Fri, May 26, 2023 at 2:20 PM Steve Grubb wrote:
>
> Hello,
>
> I was poking around a F38 system to look over the Secure Boot certificates and
> found something that may warrant attention.
>
I *suspect* this is all wrapped into the issue that
shims must now have/use NX support to be signed,
and
On Mon, May 29, 2023 at 3:28 AM Kevin Kofler via devel
wrote:
>
> Gary Buhrmaster wrote:
> > RH's staff redundancies
>
> The position was clearly NOT redundant.
The word (and all words are made up) is used
by organizations to meet certain legal requirements
(talk to *yo
On Tue, May 30, 2023 at 10:57 AM Florian Weimer wrote:
> systemd-networkd has an integrated DHCP client, hasn't it?
Yes (and I have migrated a number of my systems to
using systemd-networkd), but Richard said systemd
is not an option.
___
devel mailing
On Tue, May 30, 2023 at 11:08 AM Richard W.M. Jones wrote:
> We really need just a dhcp client, no baggage.
Busybox distributes Udhcpc, a small dhcp client
intended for embedded systems, and perhaps
might be a longer term viable solution for minimal
appliances.
And while I never looked at them,
On Sat, Jun 10, 2023 at 4:36 PM Kevin Kofler via devel
wrote:
> Considering that Fedora buildroots always get killed off within days of the
> EOL, I do not see why you are keeping epel-6 buildroots active 2½ years (!)
> after its EOL.
Well, EL6 ELS support is still available for (around)
another
On Sat, Jun 24, 2023 at 3:05 PM Michael Catanzaro wrote:
> But in practice, we actually currently have a lot of desynced packages
> where RHEL is ahead of CentOS Stream for various reasons. I believe
> most such cases are mistakes that need to be corrected, not intentional
> delays. E.g. if a par
On Mon, Dec 5, 2022 at 7:58 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/Add_FORTIFY_SOURCE%3D3_to_distribution_build_flags
>
It is my vague recollection (I could easily be wrong, so
correct me as appropriate) that _FORTIFY_SOURCE=3
adds some runtime overhead that did not apply
On Mon, Dec 5, 2022 at 10:53 PM Neal Gompa wrote:
> It has a similar impact that turning back on frame pointers would.
>
> Cf.
> https://developers.redhat.com/articles/2022/09/17/gccs-new-fortification-level#the_gains_of_improved_security_coverage_outweigh_the_cost
>
That article explicitly sta
On Tue, Dec 6, 2022 at 12:47 PM Siddhesh Poyarekar wrote:
> Overall even if there is a miniscule performance overhead, I
> reckon the reward is much higher.
I am curious how you can claim there is only a
minuscule performance overhead without doing
any benchmarks?
I am not claiming the overhead
On Tue, Dec 6, 2022 at 3:16 PM Siddhesh Poyarekar wrote:
> My full comment in that blog post is:
>
> "We need a proper study of performance and code size to understand the
> magnitude of the impact created by _FORTIFY_SOURCE=3 additional
> runtime code generation. However the performance and code
On Tue, Dec 6, 2022 at 3:42 PM Siddhesh Poyarekar wrote:
> I have added a performance note[1] in the proposal.
Thank you.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
On Tue, Dec 6, 2022 at 7:04 PM Michael Catanzaro via devel
wrote:
> Red Hat's desktop performance engineer
Since you bring up RH's performance engineer,
have they done performance evaluation on
_FORTIFY_SOURCE=3? And while I understand
that until the eval is reviewed and reproduced no
fina
On Thu, Dec 8, 2022 at 1:54 AM Alexander Ploumistos
wrote:
> I think that you are about to miss an important opportunity here.
+3000 (well, I guess I am only allowed a +1).
For non-niche requirements, I mostly find the
primary maintainers are more than willing to
add interested parties to the m
On Thu, Dec 8, 2022 at 12:42 AM Adam Williamson
wrote:
>
> Hi folks! Today I woke up and found
> https://bugzilla.redhat.com/show_bug.cgi?id=2151495 , which diverted me
> down a bit of an "installer environment size" rabbit hole.
Does the "new and improved" web based installer help this
in any wa
On Thu, Dec 8, 2022 at 12:31 PM Kevin Kofler via devel
wrote:
> IMHO, the web-based UI is a major mistake and should never be shipped in
> Fedora.
As I am sure you are aware, it seems a number of distros
are experimenting with their next gen installer. OpenSUSE
has their new web based D-install
On Thu, Dec 8, 2022 at 12:58 PM Peter Robinson wrote:
> I've done a few passes, dropping a bunch of older firmware upstream
> that are no longer supported in any stable kernel release, also a
> bunch of de-dupe and linking of files rather than shipping of multiple
> copies of the same firmware. I
On Thu, Dec 8, 2022 at 5:06 PM Adam Williamson
wrote:
> It already *is* compressed, which is why it doesn't get any smaller in
> the compressed filesystem image, unlike the other things I mentioned.
> Check for yourself - look under /lib/firmware and you'll see only
> things ending in .xz.
Right
On Thu, Dec 8, 2022 at 5:29 PM Adam Williamson
wrote:
> It shouldn't be too hard to try this out - it's just one setting in
> lorax somewhere, but I gave up on this alleyway before figuring out
> exactly where to set it.
Well, a *very* unscientific (a few random files)
showed a mostly small diff
On Sun, Dec 18, 2022 at 3:29 PM Vitaly Zaitsev via devel
wrote:
>
> On 18/12/2022 15:34, drago01 wrote:
> > Why would they? The patents apply to the algorithm, not to any API.
>
> Help in circumventing patents.
Your lawyer may vary in regards to the advice
they provide as to an organization's exp
On Thu, Dec 22, 2022 at 4:46 AM Kevin Fenzi wrote:
>
> On Wed, Dec 21, 2022 at 09:15:10PM -0700, Orion Poplawski wrote:
> > I've been using an old review_pr.py script produced by the Fedora
> > Stewardship SIG to rebuild the depedencies of a package in COPR to test
> > changes/updates to packages.
On Thu, Jan 12, 2023 at 10:19 PM David Woodhouse wrote:
> The English word for that is 'fortnightly', FWIW.
While that is Old English, and still commonly used
in parts of the world and in some formal language
usage, most people just use the words "every two
weeks" rather than asking people to pu
On Thu, Jan 19, 2023 at 10:52 AM Michal Schorm wrote:
> Would you see a value in e.g. some kind of a robot reminding
> maintainers of such obsolete code? (e.g. new RPMinspect or ZUUL CI
> check)
"Reminding" is another term for nagging. Fedora should
not be a nag when there may be reasons for th
On Thu, Jan 19, 2023 at 3:53 PM Kevin Kofler via devel
wrote:
> Why not just ship the legacy version in F38 proper rather than Copr? The new
> stuff can be packaged when it is ready, probably as a F39 or F40 Self-
> Contained Change.
Is someone working on packaging the Dart and Flutter SDK
(and
On Fri, Jan 20, 2023 at 1:54 PM Richard Shaw wrote:
>
> So is it when a build is complete in Rawhide? Or must *ALL* active releases
> get the "fix"?
>
I am not sure it is official policy/practice, but in
theory I would think that the CVE is technically
closed when all impacted Fedora releases ge
On Fri, Jan 20, 2023 at 3:48 PM Richard Shaw wrote:
> I think in practical terms that makes sense but our tools don't really help.
I agree, and that seems to be an artifact of
the single Fedora component in RHBZ, which
treats Fedora as one thing.
I supposed (in theory again) that there could
be
On Fri, Jan 20, 2023 at 4:53 PM Kevin P. Fleming wrote:
> Small clarification: where you wrote 'component' you meant 'product' :-)
> BZ has both Products and Components, forming two levels. RHEL 7/8/9 are
> Products, on the same level as Fedora.
Thanks. I suppose I should have actually checked
On Fri, Jan 20, 2023 at 4:47 PM Gary Buhrmaster
wrote:
> such as yourself are contentious about
> doing the right thing).
Obviously that word should have been conscientious
(I hate autocorrect).
___
devel mailing list -- devel@lists.fedoraproje
On Tue, Jan 24, 2023 at 7:29 AM Jeff Law wrote:
> On 1/24/23 00:16, Jakub Jelinek wrote:
> > See
> > https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
> > Some libstdc++ headers included in older versions
> > as an implementation detail but no longer do.
> >
> > Including stdint.h
On Thu, Jan 26, 2023 at 10:08 PM Miro Hrončok wrote:
> Some packagers do set the bugzillas to ASSIGNED to get rid of the reminders
> and
> then they forget to actually fix the FTBFS, cannot figure out how to fix it,
> are blocked on externalities that never happen, etc.
Perhaps ASSIGNED should
On Fri, Jan 27, 2023 at 1:10 AM Kevin Fenzi wrote:
> jaltman
I have sent an email to Jeff, and hopefully he will
update his bugzilla email.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedor
On Tue, Jan 31, 2023 at 12:45 PM Miro Hrončok wrote:
> If you see a package that can be rebuilt, please do so.
> tpm2-tss-engine mzavalavz
I can fix this (up-lift to the current release), but I don't
see a way to do so before retirement as the current
maintai
On Tue, Jan 31, 2023 at 12:45 PM Miro Hrončok wrote:
> If you see a package that can be rebuilt, please do so.
> tpm2-tss-engine mzavalavz
No longer FTBFS. It can be removed from the
to be retired list.
Thanks!
__
On Tue, Feb 7, 2023 at 7:26 PM Philip Rhoades via devel
wrote:
>
> People,
>
> Has there been any discussion about getting a Tenacity RPM going for
> Fedora? - I would prefer that to having to use the AppImage version . .
>
As I recall, in the beginning, Tenacity (to perform
most meaningful opera
On Thu, Feb 9, 2023 at 8:40 PM Michel Alexandre Salim
wrote:
>
> Dear fellow Fedorans,
>
> It seems that python-mysqlclient will now transparently upgrade python-
> mysql since 2.1.1-2 (for Fedora):
> https://src.fedoraproject.org/rpms/python-mysqlclient/c/1da9400c1c9c8eb8b044f6976e1a07f06226ed3e?
On Tue, Feb 21, 2023 at 8:48 PM Matthew Miller wrote:
> What we're doing now — as has been the case for several years, already noted
> in the previous discussion — has very little end-user value.
While occasionally I have seen a small decrease in
the size of the files transferred (which certainl
On Thu, Feb 23, 2023 at 5:54 PM Matthew Miller wrote:
> The "good news" is that Red Hat has announced a move away from Bugzilla for
> future products. (They're going to Jira.) RH Bugzilla isn't officially shut
> down, but its days are numbered. We need to come up with something else.
"Good" is i
On Thu, Feb 23, 2023 at 6:48 PM Ben Cotton wrote:
> I have a survey prepared that will be opened once the F37
> retrospective survey is done. This will give us a basis for evaluating
> our requirements as we look for possible replacements.
Thanks for planning on the followup.
___
On Fri, Feb 24, 2023 at 4:56 PM Solomon Peachy via devel
wrote:
> (I admit I'm surprised that "Free Software for Everything" Red Hat is
> chosing to base something so fundamental to their business on a highly
> proprietary tool. I suppose O365 is just a matter of time...)
They probably also u
libcbor will be updated to 0.10.2 in rawhide in the
next week or so, which includes a soname bump.
The list of affected packages in rawhide are:
libfido2
fwupd
I will rebuild libfido2. For fwupd, I will need the maintainers
(CC'ed) or a proven packagers assistance.
I have used the Mass Prebuil
On Tue, Mar 7, 2023 at 4:32 PM Richard Hughes wrote:
>
> On Tue, Mar 7, 2023 at 3:55 PM Gary Buhrmaster
> wrote:
> > I will rebuild libfido2. For fwupd, I will need the maintainers
> > (CC'ed) or a proven packagers assistance.
>
> No problem at all, thanks for le
On Tue, Mar 7, 2023 at 7:04 PM Richard Hughes wrote:
>
> On Tue, Mar 7, 2023 at 4:55 PM Gary Buhrmaster
> wrote:
> > Let me know if you have any issues
> > with the build.
>
> All done, thanks.
Thank you. I have submitted the side-tag update:
https://bodhi.fedoraproj
On Mon, Jul 22, 2024 at 11:35 AM Dmitry Belyavskiy wrote:
> So I wonder if it's worth changing the engine deprecation mechanism in
> Fedora to the one we have in CentOS and if yes, what is the mechanism
> for such a change.
I think you are free to submit a (very) late change
request, but changin
On Tue, Jul 23, 2024 at 8:55 AM Clemens Lang wrote:
> However, we should still consider the effect this will have on developers
> that build software on Fedora — they will also have to specify
> -DOPENSSL_NO_ENGINE now or see failing builds, and we don’t really see that
> impact until 41 relea
On Tue, Jul 23, 2024 at 10:30 PM Kevin Kofler via devel
wrote:
>
> Zbigniew Jędrzejewski-Szmek wrote:
> > #3244 Change: Retire Python 2.7
> > https://pagure.io/fesco/issue/3244
> > APPROVED (+8, 0, 0)
>
> This is going to break the build of a whole bunch of compatibility packages,
> which will in
On Wed, Jul 24, 2024 at 12:23 AM Gary Buhrmaster
wrote:
> I believe qt5-qtwebkit uses python3 for builds
> (I believe the qt4 variant does use python2,
> but a quick repoquery indicates no fedora
> package depends on qtwebkit-devel, although
> I admit the query may have been wrong
On Tue, Jul 23, 2024 at 10:38 PM Kevin Kofler via devel
wrote:
> And this one is yet another case of FESCo rubberstamping a change without
> even any dissenting vote despite loads of negative mailing list feedback.
How can one determine "loads"? Since the
feedback itself is opt-in, no statistic
On Wed, Jul 24, 2024 at 6:18 PM Stephen Gallagher wrote:
> For what it's worth, I don't believe that this process will work well.
> I'm all for democracy, but direct democracy without compulsory voting
> inevitably leads to "grievance-based voting", where the majority of
> folks ignore the discus
On Sun, Aug 25, 2024 at 1:46 AM Frank R Dana Jr. wrote:
> But a Seahorse-based graphical search and import isn't really
> practical for packager workflows in general, and holy smokes
> was the documentation almost no help at all in actually
> guiding me to the finish line here.
I would agree tha
On Sun, Aug 25, 2024 at 8:26 AM Frank R Dana Jr. wrote:
> I'd be happy to. (Believe me, the Edit button is _always_
> my first choice.) But the issue here is, unless we
> want to tell packagers to use Seahorse to retrieve
> upstream keys (and I'm assuming we don't), I don't
> know what to tell th
On Sun, Aug 25, 2024 at 8:36 AM Frank R Dana Jr. wrote:
>
> Also, a yea/nay on whether I've correctly understood this point:
>
> > So, does that mean that remote keyrings should be listed at their source
> > URL,
> > BUT the `gpgkey-` file at that URL should be manually downloaded and
> > `git ad
On Sat, Aug 10, 2024 at 10:42 PM Carl George wrote:
>
> Happy packaging!
>
I have noted that some dependencies for some
of my packages are (apparently) no longer
going to be shipped in EL10 (they were in
EL9).
Before I request the branches and builds
in EPEL10, I would like to make sure those
p
On Mon, Sep 2, 2024 at 10:21 AM Miroslav Suchý wrote:
> In case you hit dependency issues, please report it against the appropriate
> package.
The only problem I get is:
Error:
Problem: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora
requires libre2.so.9()(64bit), but none of the prov
On Wed, Sep 11, 2024 at 3:34 PM Petr Pisar wrote:
> You want to contact xorg-x11-util-macros component owner.
xorg-x11-util-macros was in CRB in EL9, but is
no longer available in (future) EL10. The OP
will need to open a bugzilla to request an
EPEL10 branch and build for the package
by the pac
On Fri, Sep 13, 2024 at 3:40 PM Ron Olson wrote:
>
> Hey all, I think I remember that I’d get an email when a build submitted to
> koji completed, regardless of whether it was scratch or not. Am I remembering
> that correctly and if so, is it still possible to get them?
>
> Thanks for any info!
On Wed, Jul 26, 2023 at 1:56 PM Michal Schorm wrote:
>
> My apologies !
> I built the new version when cleaning old PRs and I failed to check
> for the soname bump.
> Thank you for cleaning up after me. I will try my best to remember to
> check it next time.
I have found that using something like
On Mon, Aug 21, 2023 at 7:02 PM Michel Alexandre Salim
wrote:
>
> Dear all,
>
> exiv2 has had a new release for a few months now - 0.28.0 - which causes
> an soname bump.
>
> I've put up a PR for the update -
> https://src.fedoraproject.org/rpms/exiv2/pull-request/3 - would
> appreciate people tak
On Wed, Aug 23, 2023 at 6:23 PM Miroslav Suchý wrote:
> * this command found zero issues on my personal system - great work all
> everybody!
On my small handful of systems I found zero issues
(well, one issue on two systems with a 3rd party repo
(which was actually my own local repo, so hoiste
On Sat, Sep 9, 2023 at 1:05 AM Brendan Conoboy wrote:
> RHEL making this change does not imply or require that Fedora do the same.
I am neither suggesting Fedora should do so, or
not do so, but just as a hypothetical, should Fedora
choose to do so, do you know if RedHat would be
amenable for suc
On Wed, Sep 13, 2023 at 3:27 AM Kevin Kofler via devel
wrote:
>
> Adam Williamson wrote:
> > IIRC it was a condition of that proposal that we wind up on a hosted
> > version of the *open source* release of gitlab
>
> "hosted version" and "open source" is already a contradiction by itself.
> https:
On Fri, Sep 15, 2023 at 8:23 PM Neal Gompa wrote:
> I will also point out the last time we followed RHEL into something,
> we got the modularity system. That itself is an indicator that
> inverting the relationship for decision-making is a bad idea.
In theory, I like the concept of modularity.
On Tue, Sep 26, 2023 at 5:40 PM Kevin Kofler via devel
wrote:
> I am still opposed, because it is still a backwards-incompatible change that
> breaks existing repositories (such as my Calcforge one) just so that someone
> can tick a checkbox on some "security" checklist.
Are you saying you need
On Sun, Oct 15, 2023 at 4:26 PM Jerry James wrote:
>
> On Sun, Oct 15, 2023 at 3:13 AM Robert-André Mauchin
> wrote:
> > I'm doing a MR on an old package that contains firmware data.
> >
> > I wanna convert to SPDX, what is the equivalent to "Redistributable, no
> > modification
> > permitted"
On Sat, Oct 21, 2023 at 9:35 AM Tomasz Torcz wrote:
> 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 mention
On Sat, Oct 21, 2023 at 4:08 PM Chris Adams wrote:
> Certainly - I was just looking for a more general solution to non-RTC
> systems going forward. Ideally, there could be something triggered by a
> lack of an RTC, but it looks like systemd path units cannot work based
> on a path (e.g. /dev/rtc
On Fri, Oct 20, 2023, 16:56 Adam Williamson wrote:
> 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.
How about something of the form of an ExecStartPre expression
(or script) that t
On Mon, Nov 13, 2023 at 5:16 PM Jonathan Wakely wrote:
>
> Typically, yes, I'd expect a failure. But it's possible for code to do:
>
> #if __has_include()
> # include
> // use features in that header
> #else
> // roll your own inferior version
> #endif
And in the particular case of the Qt priv
On Tue, Dec 5, 2023 at 3:48 AM Kevin Kofler via devel
wrote:
> My pet peeve is provenpackagers or comaintainers who add unwanted automagic
> (autorelease, autosetup, autochangelog) to my packages. I do not want any of
> that in my packages, it just makes my work harder (or in practice, just
> was
On Sun, Dec 10, 2023 at 5:39 PM Sérgio Basto wrote:
> Maybe we should have a flag in the src.fp.o package for the maintainer
> to request a PR before committing to have a window for review, or like
> me, the maintainer would like to not be bothered with things that
> proven package can do by itse
On Thu, Dec 21, 2023 at 2:49 PM Tom Hughes via devel
wrote:
>
> On 21/12/2023 14:33, Steven A. Falco wrote:
> > On 12/21/23 08:53 AM, Neal Gompa wrote:
> >> On Thu, Dec 21, 2023 at 8:52 AM Leigh Scott
> >> wrote:
> >>>
> >>> I'm -1 for this change, it shouldn't be enabled by default as it will
>
On Wed, Dec 20, 2023 at 7:51 PM Chris Adams wrote:
>
> Once upon a time, Aoife Moloney said:
> > Enable IPv4 Address Conflict Detection by default in NetworkManager.
>
> Huh, I didn't realize NM didn't already do this... ye olde
> network-scripts did.
>
As I recall, depending on configuration(s
On Sat, Dec 23, 2023 at 8:28 PM Christopher Klooz wrote:
> Btw, does anyone know if this (in the practically-same manner) is really
> already introduced in Windows, Mac, Android by default?
There is a draft RFC for randomizing MAC addresses
https://datatracker.ietf.org/doc/draft-ietf-madinas-m
On Fri, Dec 29, 2023 at 12:31 PM Neal Becker wrote:
>
> On a philosophical note, I once worked on Apollo workstations. These could
> switch behavior between sysv and bsd unix. To do this, the kernel would
> interpret e.g. /usr/bin/$arch, substituting the env variable arch. At least
> that is
1 - 100 of 371 matches
Mail list logo
