Kevin Fenzi wrote:
> For a few years I was keeping track of updates that caused big problems:
>
> https://fedoraproject.org/wiki/Updates_Lessons
That is also very anecdotal evidence though. And with only one exception
(the broken dependency in celt), the updates in the above list above
or even notice to begin with.
I would suggest just picking the most common option (MIT→MIT and BSD→BSD-3-
Clause) and letting people file a bug if it turns out to be wrong. We have
had packages with more inaccurate License tags than that (wrong GPL v
release (8.0.3), though I do not know when exactly that will
be.
So it should now be possible to package this in Fedora. In my experience,
SCIP performs much better than COIN-OR Cbc on MIPs (MILPs).
Kevin Kofler
___
devel mailing list -- devel
le, a bug could be filed to attract the maintainers(s)
attention.
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
dates over the years. I think direct to stable is a
bad idea.
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Condu
clusion. Where was
> that analysis published so I can read it?
It is empirical evidence only. (When something bad was pushed to stable, I
looked at how it happened, and more often than not, it was autokarma.) There
is not much of an analysis that can be done because Bodhi does not retain
historical data.
The original trigger for the update policy enforcement was actually an
update that broke the bind DNS server, a package that ~99% of Fedora users
do not even have installed. The response has always been a complete
overreaction.
Kevin Kofler
___
Vitaly Zaitsev via devel wrote:
> What about packages that use dlopen() like Telegram Desktop?
Why the heck does a Qt application like Telegram Desktop dlopen WebKitGTK?
They are supposed to use QtWebEngine.
Kevin Kofler
___
devel mailing l
n some piece of software, no matter how much
complexity we force that software's maintainers to add to the latter. :-)
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedor
ment those
few special cases that are actually needed, such as freezes.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://do
On Thu, Nov 10, 2022 at 05:16:44PM +, Mattia Verga via devel wrote:
> Il 10/11/22 01:58, Kevin Kofler via devel ha scritto:
> > Kevin Kofler via devel wrote:
> >
> >> Mattia Verga via devel wrote:
> >>> with the current workflow, Bodhi do
ot;dev" releases before that. (Like gnome)
Some just mix features and bugfixes into a single stream.
Some only seem to have prereleases and take years to actually do a point
release.
etc.
So, asking that "dev" releases use different options I think would just
result in
.fc38'
Very odd that ci would use a build that doesn't exist. (I guess it's a
scratch build it made itself?)
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
if there would
> be any plans to eventually switch to GNOME Shell once feature parity happens.
I don't know of any plans right now, but I think it's likely to happen
if things are merged and are in a workable state. :)
kevin
signature.asc
Description: PGP signature
_
Kevin Kofler via devel wrote:
> Mattia Verga via devel wrote:
>> with the current workflow, Bodhi doesn't know when a release is freezed.
>> There is support for a "Freeze" state, but it was never used.
>
> How do we prevent then that pushes to stable actually m
runs a different script to push testing
only instead of both testing and stable, that is the "can we push to
stable?" property Bodhi needs to check.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
On Tue, Nov 08, 2022 at 03:09:46PM -0500, Ben Cotton wrote:
> On Tue, Nov 8, 2022 at 1:34 PM Kevin Fenzi wrote:
> >
> > Yeah, was going to try and work it out with them (which I have not yet
> > done). Where's the best place to engage with them these days?
>
> I'd sta
out with them (which I have not yet
done). Where's the best place to engage with them these days?
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapr
Adam Williamson wrote:
> Yeah, this is a good point, though I'm not sure how easy it is to fix.
if (state == pending && request == stable && !can_push(stable))
push(testing);
else
push(request);
Kevin Kofler
___
devel ma
On Mon, Nov 07, 2022 at 10:21:43AM +0100, Mikel Olasagasti wrote:
> Hi Kevin,
>
> Hau idatzi du Kevin Fenzi (ke...@scrye.com) erabiltzaileak (2022 uzt.
> 9, lr. (20:11)):
> >
> > On Fri, Jul 08, 2022 at 01:02:15PM -, Mukundan Ragavan wrote:
> > > > On S
branch=rawhide
I do not understand why. That patch was there exactly to prevent this exact
issue. Dropping that patch is what caused this blocker bug.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
want in more places, not
fewer ones. (I am thinking of comps in particular.) But of course, if, as
seems to be the status quo, it only theoretically works for modules, does
not really work even for modules in practice, and is not actually used by
modules, then it does not make sense.
ge and you have an
> unintentional conflict.
I think the concern is not about Ansible suddenly adding, e.g.,
%{bindir}/ansible-cp, but about them suddenly adding, e.g., %{bindir}/cp.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
T
wildcard would
actually be wrong to use there because it misses the %lang(…) tags that the
macro automatically adds. And you really do not want to have to list every
single language manually, and update the list for every single new upstream
release, since translations co
all ? But then you have duplicates...
Not sure the best answer there.
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
the main thing for which I used to *always* use a
wildcard.)
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedorapr
ed packages are cleaned up after some amount of time if they are not
in a tag requiring keeping them.
So, I suppose the web interface could offer signed copies if they exist,
but might be confusing if you don't know what the various keys short
hash is. Feel free to file a RFE for koji folks: https:
e, you would have to resend to everyone.
Or you can just ignore the moderation message. I pass all these through
moderation anyhow, it's just a slight delay.
kevin
--
>
> -- Forwarded message -
> From:
> Date: Wed, Nov 2, 2022 at 7:59 AM
> Subject:
ink we should.
>
> I would suggest we set it to the expected EOL based on the nominal schedule.
> We could either release updates to extend it if we slip... or... just not do
> that.
I think we should also.
https://bugzilla.redhat.com/show_bug.cgi?id=2105402
PR's welco
he f36
one will be pushed stable, and likely the f37 one won't be far behind.
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedo
ing different approaches (maven
>> artifacts in koji, vendoring NodeJS dependencies, Java Modules, etc.)
>> have *failed* and ultimately made things worse instead of improving
>> the situation - the only thing that has proven to be sustainable (for
>> now) is ... maybe surprisingly
re stage (generally a good idea, but not helpful here).
>
> So I'm a bit at a loss what to do here. Maybe releng can reconsider
> their approach.
So, can you say that copr definitely will not work for this?
If it will, great, use that. If it won't, we can make you a side tag, I
don't reall
od. We were not setting
anything for this (since our cron job predates it existing) and we got
the default (10days).
I have a PR in to set it to 21 days:
https://pagure.io/fedora-infra/ansible/pull-request/1238
which I think is a bit more reasonable, but further input welcome.
kevin
signatu
Matthew Miller wrote:
> I fundamentally disagree with Kevin on a deep level about "entirely
> useless", but ... find myself kind of agreeing about the "unpackagable"
> part. I mean: clearly we've found a way, but I'm really not sure we're
> providing a lot of _value
Peter Robinson wrote:
> Why are they insecure? This is public open data, not banking data,
> where the data being downloaded is verifiable by the rpm signatures
> and signing keys.
The metadata is not, at least not currently.
Kev
ioners).
Kevin Kofler
___
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:
as the one-size-fits-it-all
solution to all our problems, even where it is completely off topic.
(And ultimately, replacing a system of package groups with one of "take it
or leave it" containers would give the end user *fewer* options, not more.
The package groups can easily be
lex strength check now.
Kevin Kofler
___
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-cond
be start using some password manager to generate and store long
> enough passwords?
Well, yes, I store the password in KWallet, so it was not a major
inconvenience to have to generate and store a new one. It was just an
entirely unnecessary inconvenience.
at is good enough for Bugzilla (but who knows for how long?), but this
is absolutely absurd.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Condu
g the thread linked above, I think we can probably
fast-track the orphaning.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Con
for the foreseeable future.
--
Kevin P. Fleming
He/Him/His
Principal Program Manager, RHEL
Red Hat US/Eastern Time Zone
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct
asonably ship, not what the (relative)
majority of developers in the world (most of whom do not even run Fedora)
happens to prefer.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
I see. So splitting might be worthwhile then. Assuming someone will care
enough to actually maintain the code.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject
ugh it is still better than what smaller distributions like Arch are able
to offer, where, e.g., the AUR only allows publishing the source PKGBUILD
files and no binaries at all.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.
s awfully broken as Panu is saying, I do
not think that that would be of much use, unfortunately.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
ily bloat
the core system over time.
> So here we are, in a subpar situation created by bad tools because
> nobody cares enough about security anyway.
Sounds like a mess indeed.
Kevin Kofler
___
devel mailing list -- devel@lists.fedorapro
Miroslav Suchý wrote:
> Dne 13. 10. 22 v 6:12 Kevin Kofler via devel napsal(a):
>> I am really angry at Copr's expiration policy once again. It looks like I
>> missed the deadline to renew the expired chroots (I still do not get any
>> notification mails, they end up e
is is
> in line with the stronger crypto settings proposed elsewhere for F38)
Such a hardcoded restriction, without a way for the local administrator to
allow the legacy signatures, is not acceptable.
Kevin Kofler
___
devel mailing list -- d
quot;Extend all"
button) at least every 180 days (in practice, more often, or you end up
missing the deadline). That is a very unfriendly dark pattern.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
delivery
method, mails can get lost at any time), and deleting data is not and will
never be a safe default. The default must be to retain, not to delete.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
uilds: ... You can re-tag
> them into a new side-tag with: ...") would solve most problems. And we can
> skip that mail if the side-tag has been merged already.
> Michael
I've created https://pagure.io/releng/issue/11082 to capture these
ideas/tra
On 10/12/22 08:59, Stephen Smoogen wrote:
Maybe call it the Fedora Update Manager 'FUM' ?
Unless we're going to call it RUM when it makes its way into RHEL, that
name may not be the best choice :-)
--
Kevin P. Fleming
He/Him/His
Principal Program Manager, RHEL
Red Hat US/Eastern Time Zone
he hub has no idea, it's
just waiting to accept info from builders, it doesn't iniate connections
back.
I often use something like:
koji list-hosts --enabled |grep -v "11 Oct 2022 10:2"
ie, show all hosts that are enabled and have checked in in the last few
minutes.
kevin
signatur
.
kevin
signature.asc
Description: PGP signature
___
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
big complicated rebases in side tags rather
> than breaking Rawhide or Branched for days at a time; sometimes this
> might take more than a week. I don't want folks to be discouraged from
> using side tags and just go back to breaking Rawhide because of this
> kind of cle
plication though. KDE Plasma users will want KDE
Partition Manager instead.
IMHO, we need a proper solution for the general comps issue rather than that
half-baked compromise that does not really improve the situation. KDE Plasma
users should get KDE applications by default
pc-srpm-macros,
(likely epel-release) or have it added to the srpm-build group.
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fe
nk this rises to the level of requiring a Self-Contained
> Change proposal, but I'm happy to submit one if the consensus is that
> it should have one)
+1 to just do it. I don't think it needs a change.
kevin
signature.asc
Description: PGP signature
___
, is that
correct? So should we ship all wxWidgets applications in the form of
multiple subpackages compiled against the different wxWidgets backends?
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
any issues with buildvm-a64 machines, please file an
infrastructure ticket: https://pagure.io/fedora-infrastructure
Thanks,
kevin
signature.asc
Description: PGP signature
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
any issues with buildvm-a64 machines, please file an
infrastructure ticket: https://pagure.io/fedora-infrastructure
Thanks,
kevin
signature.asc
Description: PGP signature
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
Michael Catanzaro wrote:
> In Fedora 38, we'll have a new service,
> fedora-autofirstboot, that installs OpenH264 for you with no user
> interaction
Installing restrictively licensed stuff (see the patent license) with no
user interaction is not really helpful.
Kev
, then the hardware alone is infringing, but that's a
totally different discussion. Since Intel and AMD employ large numbers
of highly-trained patent lawyers, presumably they've decided that they
do not need to address this concern.
--
Kevin P. Fleming
He/Him/His
Principal Program Manager, RHEL
Red Hat
eader.
It looks like EEL only supports the following hardcoded set of architectures
(with platform-specific assembly code): ppc, aarch64, arm, x86_64, x86.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
not think the src-git approach is legally possible at all for
these packages, at least not based on upstream git. (You could of course
make your own git history with just code drops of the hobbled tarballs'
contents, but that makes the use of git much less useful.)
Kev
Neal Gompa wrote:
> Unfortunately, we have to be very careful to not provide a complete
> codepath to these codecs to avoid legal risks.
Considering that we have been shipping these hardware codec interfaces for
years without any legal trouble, I find this absolutely ridiculous.
in a weird state because they just finished
right when the unexpected kojipkgs01 outage happened this morning. ;(
I managed to cancel them via the api and rebuilds should finish.
If there's any other builds in this state please let me know.
kevin
signature.asc
Description: PGP signature
_
ut of course thats up to you.
kevin
signature.asc
Description: PGP signature
___
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.o
There will be an outage starting at 2022-09-26/2022-09-27 21:00 UTC,
which will last approximately 4 hours on 2022-09-26 and 5 hours on 2022-09-27.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2022-09-26 21:00UTC'
date
There will be an outage starting at 2022-09-26/2022-09-27 21:00 UTC,
which will last approximately 4 hours on 2022-09-26 and 5 hours on 2022-09-27.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2022-09-26 21:00UTC'
date
On Wed, Sep 21, 2022 at 02:47:21AM +0200, Kevin Kofler via devel wrote:
> Miro Hrončok wrote:
> >* https://fedoraproject.org/wiki/Changes/JdkInTreeLibsAndStdclibStatic
> > was submitted as an Fedora 37 update after it was deferred to Fedora
> > 38. We need
ers.
Kevin Kofler
___
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: ht
1
> F32: 1
> F34: 2
That was almost every release, and in fact an average of around one such bug
per release cycle.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproj
uot;Secure" Boot) altogether (which is a much worse restriction), because
that, too, changes the TPM PCR measurements.
But the marketing as a "security" "feature" clearly works, because there
does not seem to be any noticeable public outrage about the
s like Debian stubbornly sticking to soname-based
versioning.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproj
geKit and CLI) that are IMHO even more interesting than the raw
speed gain.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Co
on the mailing list was entirely
negative, the only people in favor were the submitters.)
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
for bugs instead of
two is a good thing.
What will be done with the existing open bugzilla bugs?
(There's some overlap between the two it looks like).
Close and ask them to refile? Refile for them?
kevin
signature.asc
Description: PGP signature
__
14:36:13 +0200
> From: Jiri Olsa
> To: devel@lists.fedoraproject.org, Kevin Fenzi
> Cc: jo...@fedoraproject.org
> Subject: Re: unannounced soname bump in libbpf
>
> On Sat, Sep 03, 2022 at 05:01:47PM -0700, Kevin Fenzi wrote:
> > Greetings.
> >
> > Seems
On Mon, Sep 19, 2022 at 05:58:36PM +0200, Vít Ondruch wrote:
>
> Dne 16. 09. 22 v 19:03 Kevin Fenzi napsal(a):
> > On Fri, Sep 16, 2022 at 10:03:35AM +0200, Vít Ondruch wrote:
> > > Isn't peer review much better and easier solution over all? We could also
> > >
applications on us by deprecating drivers
is not going to make users happy no matter what you do. In the end, if CUPS
upstream is not willing to keep classic drivers working, I see no other
option than forking CUPS.
Kevin Kofler
___
devel
es to implement them for Wayland (see
https://gitlab.gnome.org/GNOME/mutter/-/issues/217). So a compile-time
choice cannot make everyone happy. It should be decided at runtime (i.e.,
the code should try using xdg-decoration first, and only if that fails, fall
back to libdecor).
like to note that today, both rawhide and branched composes
completed with status "FINISHED". This means every single artifact that
was supposed to be composed was. :)
Keep up the great work everyone... lets see if we can keep it going.
kevin
signature.asc
Desc
ything where we need to support gpg.
It's a mess and I think it would waste a lot of cycles explaining how to
use it or help people get setup. ;( If there's some easier/more clear
way to sign things that could be a option tho.
kevin
signature.asc
Description: PGP sig
thing
> that is harder to deal with, anyway.
I'll also note that I think many more of them came toward the first part
of that time period. We made some changes to the interface that helped a
good deal. At first we had a mailto: link and got a bunch of blank
emails (bots just following the
On Thu, Sep 15, 2022 at 04:34:08PM -0400, Demi Marie Obenour wrote:
> On 9/15/22 13:55, Kevin Fenzi wrote:
> > On Thu, Sep 15, 2022 at 09:26:36AM +0300, Alexander Bokovoy wrote:
> >>
> >> Proven packagers seem to be a fair category to address. Also packagers
> >&
On Thu, Sep 15, 2022 at 11:54:13AM -0700, Adam Williamson wrote:
> On Thu, 2022-09-15 at 10:55 -0700, Kevin Fenzi wrote:
> > On Thu, Sep 15, 2022 at 09:26:36AM +0300, Alexander Bokovoy wrote:
> > >
> > > Proven packagers seem to be a fair category to address. Also
uld try and gather some. What stats would be helpfull?
>
> A particular argument by smooge and others was arount 'passwords or
> tokens being lost frequently'. I'd like to see how widespread is this
> problem. Can we collect stats on amount of requests to reset p
just insane, and will just lead to
applications bundling their own SHA-1 implementation and possibly even their
own PGP signature implementation to work around your deliberate breakage.
Kevin Kofler
___
devel mailing list -- devel@lists.fedor
ficates, tokens, etc may be needed but they are going to
> > need a lot of documentation, continual training, and coaching to actually
> > make function. If there is no staff or people available to do this, then
> > the change will fail hard.
>
> Do we have any statistics of how
On Wed, Sep 14, 2022 at 11:45:16AM +0200, Alexander Sosedkin wrote:
> On Tue, Sep 13, 2022 at 7:35 PM Kevin Fenzi wrote:
> >
> > How about this:
> >
> > Drop the term 'jump scare' entirely. IMHO it just sounds bad.
>
> I'm open for proposals on the wording. =)
W
On Tue, Sep 13, 2022 at 05:01:57PM +0200, Florian Weimer wrote:
> * Kevin Fenzi:
>
> > I just edited the f38 tag at Mon Aug 22 08:29:51 PM UTC 2022 to switch
> > to nspawn.
> >
> > If you have detected a issue that seems like it might be related to this
> >
? This might be a good thing to try and do
before landing it in rawhide.
* setup a tracking bug to track the issues, so we can make a more
informed decision before f38 beta.
Thoughts?
kevin
signature.asc
Description: PGP signature
___
devel mailing list
ibs 4 as kdelibs5 due to the same soversion-based versioning policy.
That confused the heck out of users. (Fedora, on the other hand, used human-
readable versioning, so kdelibs 3 was and still is called kdelibs3, not
kdelibs4.) So I do not think Debian is a good example to follow.
to join the room, after 60 seconds or so your client reports a
failure, and then 5-10 minutes later you attempt to join again and it
works; I believe this is happening because the backfill process
continues on your server even though your client gave up.
--
Kevin P. Fleming
He/Him/His
Principal
TK version than it
actually does.
I can see why you want the soversion in there, especially to distinguish 4.0
from 4.1, but would it not make more sense to use:
webkit2gtk3_4.0
webkit2gtk3_4.1
webkit2gtk4_5.0
as the names?
Kevin Kofler
___
dev
odhi.template.last
> ```
> But the update shows up on bodhi as an active update.
>
> Is there something I can do to fix this; never seen this error before.
It's nothing on your end. It's server node certs on the rabbitmq cluster
that runs fedora-messaging. ;(
I'v
Kevin Kofler via devel wrote:
> The best way then would be to check whether the one-line fix:
> https://hg.mozilla.org/comm-central/log?rev=1784838
Actually, there are two parts, and the main one is more than one line.
It had looked to me at a first glance that those are just the same
h(s).
Kevin Kofler
___
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: ht
801 - 900 of 9269 matches
Mail list logo
