Package uses old fedora account system
https://bugzilla.redhat.com/show_bug.cgi?id=237
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://do
From what I've been reading it seems the path of least resistance is to just
keep the Fedora Workstation branding and have two options: GNOME or KDE
Plasma. I don't believe that it should be overly confusing to ask people to
pick one. I just asked Google Gemini to come up with a suggestion an
yubioath-desktop and potentially yubikey-manager-qt will not be included in the
F38 repository due to packaging issues. For additional information and
suggested mitigations, please review:
https://discussion.fedoraproject.org/t/f38-yubioath-desktop-yubikey-manager-qt-will-no-longer-be-available
I really don't see we have much of a choice here. X11 is eventually going away
and Wayland is the path forward. That's already been decided, so at this point
it isn't a matter for debate. Human nature being what it is, people tend to
procrastinate and not do anything until pressed up against
> On Sun, Jun 28, 2020 at 7:54 PM Gerald B. Cox
> I'm wondering, how do you actually want to define a "production
> release" of a kernel module?
> Does being part of an upstream kernel release (not in staging modules)
> not qualify?
> Because that's already
0 at 3:00 PM Justin Forbes wrote:
> On Sat, Jun 27, 2020 at 5:17 PM Gerald B. Cox wrote:
> >
> >
> >
> > On Sat, Jun 27, 2020 at 2:30 PM Chris Murphy
> wrote:
> >>
> >> On Sat, Jun 27, 2020 at 2:53 PM Gerald B. Cox wrote:
> >>
&g
t;silly you... BTRFS
should only be used in non-critical systems - if you're concerned about
stability you shouldn't be running it."
===> If we are considering BTRFS as a default, at a bare minimum there
should be an official production release from the project.
On Sun, Jun 28,
On Sat, Jun 27, 2020 at 5:04 PM Chris Murphy
wrote:
>
> But if you can state clearly why it isn't persuasive in a way anyone
> could possibly answer, I'm sure someone will try. And it would help
> improve the proposal.
>
Making something the default is a high bar to clear. There needs to be a
c
On Sat, Jun 27, 2020 at 2:30 PM Chris Murphy
wrote:
> On Sat, Jun 27, 2020 at 2:53 PM Gerald B. Cox wrote:
>
> > Why would we be installing something by default that has widely known
> broken functionality?
>
> Because the default configuration we're using isn't
On Sat, Jun 27, 2020 at 2:01 PM Josef Bacik wrote:
> On 6/27/20 4:53 PM, Gerald B. Cox wrote:
> >
> >
> > On Sat, Jun 27, 2020 at 1:23 PM Chris Murphy > <mailto:li...@colorremedies.com>> wrote:
> >
> >
> > The proposal has n
On Sat, Jun 27, 2020 at 1:23 PM Chris Murphy
wrote:
>
> The proposal has nothing to do with raid56, let alone by default. The
> installer doesn't offer it as an option. And it's not relevant to the
> desktop. We're talking about single device btrfs file systems.
>
>
Isn't the proposal talking ab
I was an early adopter and used BTRFS for many years, singing its praises.
I was particularly interested in the RAID capabilities. Then in 2016 the
bomb was dropped that:
"It turns out the RAID5 and RAID6 code for the Btrfs file-system's built-in
RAID support is faulty and users should not be mak
If I understand the discussion here:
https://discussion.fedoraproject.org/t/can-the-copr-category-be-removed-from-the-latest-list/2420
Alot of the traffic can be dealt with using the "do not list this category
in latest" function - and there will be an RFE for the "new" category. The
one
thing th
ohn Harris wrote:
> On Sunday, September 1, 2019 6:22:04 AM MST Gerald B. Cox wrote:
> > John you're comparing apples and oranges. One is active the other is
> > passive. One uses your space allocation the other doesn't.
>
> Sorry, what? What space allocation? If
John you're comparing apples and oranges. One is active the other is
passive. One uses your space allocation the other doesn't.
On Sat, Aug 31, 2019, 19:07 John Harris wrote:
> On Friday, August 30, 2019 5:40:22 AM MST Gerald B. Cox wrote:
> > You just explained exactly w
On Thu, Aug 29, 2019 at 6:55 AM Chris Peters wrote:
>
> PS I won't take this thread any further. The irony of a back and forth in
> the back and forth thread doesn't escape me!
>
>
That's hilarious and true. I was thinking the exact same thing...
___
d
You just explained exactly why it was different ;-)
On Wed, Aug 28, 2019 at 9:23 PM John Harris wrote:
> On Wednesday, August 28, 2019 5:09:23 AM MST Gerald B. Cox wrote:
> > It's somewhat ironic that Discourse would solve this issue. As I
> > previously mentioned, I al
I use the gmail android app and on desktop I use the gmail web interface.
On Thu, Aug 29, 2019 at 3:19 PM Przemek Klosowski via devel <
devel@lists.fedoraproject.org> wrote:
> On 8/27/19 8:36 PM, Gerald B. Cox wrote:
> > Regarding NNTP I've haven't used newsreaders
n Thu, Aug 29, 2019 at 12:52 PM Iñaki Ucar wrote:
> On Thu, 29 Aug 2019 at 17:36, Gerald B. Cox wrote:
> >
> > If I do that, I believe I get into a situation where the other builds
> f29, f30 and F32 are behind, which if I remember correctly causes other
> issues - and shoul
Adam Williamson
wrote:
> On Thu, 2019-08-29 at 07:56 -0700, Gerald B. Cox wrote:
> > Guys, I'm still getting this message:
> > fedpkg update
> > Could not execute update: Could not generate update request: Cannot find
> > release associated with build: copyq-3.9.2-1.
Guys, I'm still getting this message:
fedpkg update
Could not execute update: Could not generate update request: Cannot find
release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
A copy of the filled in template is saved as bodhi.template.last
I just checked bodhi and other packages are
I'm still getting these messages when I try to do "fedpkg update" for F31:
fedpkg update
Could not execute update: Could not generate update request: Cannot find
release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
A copy of the filled in template is saved as bodhi.template.last
On We
Neal, while you're at it, can you find out what is going on with the RSS
support. There was quite a bit of discussion about it - but that has been
going on for years now and nothing seems to be happening.
On Tue, Aug 27, 2019 at 11:49 AM Neal Gompa wrote:
> On Tue, Aug 27, 2019 at 2:31 PM Emman
On Wed, Aug 28, 2019 at 1:40 AM Kevin Kofler wrote:
> I wrote:
> >> But what about the die-hard NNTP users? You entirely ignored my post to
> >> which you are supposedly replying.
>
> Gerald B. Cox replied:
> > I believe there is a plugin for that with Discourse:
It's somewhat ironic that Discourse would solve this issue. As I
previously mentioned, I also don't like having my inbox flooded with forum
threads that don't interest me. The mailing list solution requires you
setup filters or continuously delete dozens of emails. Discourse however
allows you t
Google John, Google is your friend... ;-)
https://wiki.list.org/DEV/ModernArchiving
On Tue, Aug 27, 2019 at 10:32 PM John Harris wrote:
> On Tuesday, August 27, 2019 6:27:49 PM MST Gerald B. Cox wrote:
> > Don't know what to tell you... it was a planned feature for Mailman 3,
&
Don't know what to tell you... it was a planned feature for Mailman 3, and
it is mentioned here:
https://gitlab.com/mailman/hyperkitty/issues/51
On Tue, Aug 27, 2019 at 10:23 PM John Harris wrote:
> On Tuesday, August 27, 2019 6:20:57 PM MST Gerald B. Cox wrote:
> > Well, th
On Tue, Aug 27, 2019 at 10:20 PM Gerald B. Cox wrote:
> Well, there is an open ticket to do just that - apparently some people
> have a bigger imagination. ;-)
>
> On Tue, Aug 27, 2019 at 10:08 PM John Harris wrote:
>
>> On Tuesday, August 27, 2019 5:43:54 PM MST Gerald B.
Well, there is an open ticket to do just that - apparently some people have
a bigger imagination. ;-)
On Tue, Aug 27, 2019 at 10:08 PM John Harris wrote:
> On Tuesday, August 27, 2019 5:43:54 PM MST Gerald B. Cox wrote:
> > > On Tuesday, August 27, 2019 5:02:36 PM MST Gerald
email within HyperKitty.
On Tue, Aug 27, 2019 at 10:00 PM John Harris wrote:
> On Tuesday, August 27, 2019 5:58:11 PM MST Gerald B. Cox wrote:
> > > On Tuesday, August 27, 2019 5:36:58 PM MST Gerald B. Cox wrote:
> > >
> > > How exactly do your RSS feedreaders handl
> On Tuesday, August 27, 2019 5:36:58 PM MST Gerald B. Cox wrote:
>
> How exactly do your RSS feedreaders handle threading?
Don't you mean how HyperKitty will handle it? I won't be responding from my
Feedreader, I would be reading the contents from the feed, and if I was
int
> On Tuesday, August 27, 2019 5:02:36 PM MST Gerald B. Cox wrote:
>
>
>
> You could also just use NNTP, which wouldn't require you to have anything in
> your mailbox. Then you can reply from the same client, as well :)
Yeah, Kevin mentioned NNTP also... but as I men
> On 8/27/19 11:00 AM, Gerald B. Cox wrote:
>
> Would your concerns be addressed if tjere was a gateway from this email
> list to Discord? Would something simple that just stores each email in a
> separate Discord item work, and if not, why?
>
> BTW, is there a gateway
Hey Kevin:
> Gerald B. Cox wrote:
>
> If the plan is to replace mailing lists with something that cannot even
> provide the same functionality, that is unreasonable and isn't going to
> happen.
>
>
> But you are assuming that we actually WANT to migr
People keep mentioning HyperKitty as an alternative to Discourse. While I
believe Discourse has more functionality, one thing that would make HyperKitty
a somewhat acceptable alternative would be the addition of RSS support. So I
started to investigate and found that several tickets were opene
12:45 PM Dan Book wrote:
> This conversation is pretty pointless. You are never going to convince
> other people to like Discourse more than mailing lists, and they are never
> going to convince you the other direction.
>
> -Dan
>
> On Tue, Aug 27, 2019 at 11:35 AM Gerald B. C
Aug 27, 2019 at 12:20 PM Louis Lagendijk wrote:
> On Tue, 2019-08-27 at 12:00 -0300, Gerald B. Cox wrote:
>
> Why is it when I say that I don't want to clutter up my email with mail
> from mailing lists I'm told it's a misconfiguration. It's not a
> misconfigur
I never said they were. What I said was expecting and requiring Discourse
to 100% replicate everything a mailing list does isn't going to happen and
shouldn't be a requirement.
On Tue, Aug 27, 2019 at 11:55 AM John Harris wrote:
> On Tuesday, August 27, 2019 7:29:28 AM MST Gerald
ourse. Why is that
so hard to understand?
On Tue, Aug 27, 2019 at 11:47 AM John Harris wrote:
> On Tuesday, August 27, 2019 7:29:28 AM MST Gerald B. Cox wrote:
> > Using mail, I have to access the archives to read the full thread.
>
> This is just due to your configuration. You c
t option.
I understand there isn't going to be 100% feature parity, but it should be
good enough - and if it isn't we should be working with the Discourse
people to improve it rather than just using it as an excuse to not moving
forward.
On Tue, Aug 27, 2019 at 10:32 AM John Harris wr
I would assume you would just use mailing list mode and address
additional recipients. To receive an expert reply I would suggest you ask
the question here:
https://meta.discourse.org/c/support
On Tue, Aug 27, 2019 at 10:54 AM Julen Landa Alustiza <
jla...@fedoraproject.org> wrote:
> I'm curiou
I read all the comments and my response is this...
First of all, there is no limit to the amount of emails that discourse will
send out. That is a site parameter, and whomever supports it for Fedora
needs to change it:
https://meta.discourse.org/t/daily-limits-for-outgoing-mails-per-user/41458
I
> On 26 August 2019 16:04:12 CEST, "Gerald B. Cox"
> The only reason to bring it up when replying to me is that you think it
> applies here. So
> while you explicitly did not mention me there's not very many other ways it
> can be
> interpreted.
>
> So
> On 26 August 2019 14:27:53 CEST, "Gerald B. Cox"
> Was it a lengthy conversation where you needed context from earlier posts?
> Was is easily at hand right in your email client?
>
>
> That's exactly my point. The advantages listed are mere stated opinions.
> It seems that the only thing in that link that has merit in regards to this
> list is that
> discourse allow editing of messages that has been sent.
>
> As for the other things I disagree with pretty much everything. I don't think
> email is
> too hard to use, I don't think large mailinglists
If you disagree with something that is stated, you need to in detail
explain why, not just claim it is marketing and therefore invalid.
On Mon, Aug 26, 2019 at 8:30 AM Markus Larsson wrote:
>
>
> On 26 August 2019 13:25:52 CEST, "Gerald B. Cox" wrote:
> &g
Here you go...
https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298
___
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
> On Wednesday, August 21, 2019 7:32:06 AM MST you wrote:
>
>
>
>
>
>
>
> RE: No longer supporting mailing lists:
> This project literally cannot function without mailing lists. We do not
> currently have a viable alternative. See all of the issues we've had trying
> to
> work with M
On Fri, Aug 23, 2019 at 1:49 PM Adam Williamson
wrote:
>
> >
> > bodhi is not yet enabled for fedora 31.
> >
> > According to the schedule, that's supposed to happen on 2019-08-29:
> > https://fedoraproject.org/wiki/Releases/31/Schedule
>
> And just to be clear - that means you don't *need* to cr
I've been trying to submit an update to testing for several days now and it
keeps failing
with the following message:
Could not execute update: Could not generate update request: Cannot find
release associated with build: copyq-3.9.1-1.fc31, tags: ['f31']
A copy of the filled in template is saved
On Thu, Aug 22, 2019 at 6:51 AM Florian Weimer wrote:
>
> Have you ever encountered the daily message limit? It seems to be quite
> low, at 100. That alone seems to make mailing list mode useless.
>
>
The daily message limit is a site controlled parameter. It can be changed
by the
administrato
>...I think this should be retracted before it ends up being a
> phoronix article making the project look bad.
I 100% agree... but too late:
https://www.phoronix.com/scan.php?page=news_item&px=Fedora-31-Possible-AVX2-Require
___
devel mailing list -- d
This was pretty much inevitable. Out of companies with deep enough pockets -
IBM is a good outcome. In the end, it will be good for both companies. It
isn't helpful to have a negative attitude about it. “Change is the law of life
and those who look only to the past or present are certain to
know a bit about the problem space, and I'd like to
> discuss *some* aspects here. I expect it's clear which I prefer, but
> there are a lot of arguments "for" that I don't deal with.
>
> Dominik 'Rathann' Mierzejewski writes:
> >>>>&g
choose that - that subject was set by Gerald B. Cox.
>
> As I previously mentioned with all the top-posting, excerpts and hyperbole
interjected by others people
get lost and run with mis-quotes - perhaps Discourse could help with that.
;-)
Software is a tool for me. I don't get emotional
On Fri, Oct 19, 2018 at 7:43 AM Nicolas Mailhot
wrote:
> Le vendredi 19 octobre 2018 à 07:28 -0700, Gerald B. Cox a écrit :
> > And if this conversation were in Discourse, we could simply move it to
> > a new topic ;-)
>
> And if it where is discourse I woul
On Fri, Oct 19, 2018 at 7:41 AM Neal Gompa wrote:
>
>
> I'm not talking about you in the Fedora sense. I'm talking about
> Gerald and his saying "we must move everything to Discourse".
>
Oh really... I said that... perhaps you should take 5 seconds and read the
subject of the thread.
As far as
And if this conversation were in Discourse, we could simply move it to a
new topic ;-)
On Fri, Oct 19, 2018 at 7:21 AM Nicolas Mailhot
wrote:
> Le vendredi 19 octobre 2018 à 14:55 +0100, Daniel P. Berrangé a écrit :
> >
> > I don't know why Red Hat's mailman impl isn't upgraded, but it is
>
On Fri, Oct 19, 2018 at 6:45 AM Neal Gompa wrote:
> On Fri, Oct 19, 2018 at 9:16 AM Gerald B. Cox wrote:
> >
> > Again, I believe some are trying to do an apples to apples comparison
> with Discourse and mailing list technologies. Discourse was build from the
> groun
On Fri, Oct 19, 2018 at 4:26 AM Matthew Miller
wrote:
> On Fri, Oct 19, 2018 at 03:53:06AM -, Máirín Duffy wrote:
> > But we can file bugs against Discourse and they will be magically and
> > quickly fixed to our satisfaction, yes?
>
> Of course not. However: development is very active.
> htt
Again, I believe some are trying to do an apples to apples comparison with
Discourse and mailing list technologies. Discourse was build from the
ground up with the goal of fostering communication and collaboration.
Hyperkitty is a bolt on HTML to mailing list archives. It's good for what
it is, b
On Thu, Oct 18, 2018 at 1:15 PM Randy Barlow
wrote:
> On Wed, 2018-10-17 at 13:14 -0400, Matthew Miller wrote:
> > Discourse is *definitely* not a smooth, drop-in mailing list
> > replacement
> > like Hyperkitty is.
>
> I'm curious what is insufficient about Hyperkitty that Discourse does
> well
On Thu, Oct 18, 2018 at 12:40 PM Kevin Fenzi wrote:
> On 10/18/18 6:31 AM, Gerald B. Cox wrote:
>
> > Actually, I think that just creating a new discourse instance for
> > discussions keeping the mailing
> > lists around would be a good solution. You woul
On Thu, Oct 18, 2018 at 12:28 PM wrote:
> > On Thu, Oct 18, 2018 at 11:40 AM Simo Sorce wrote:
>
> > You need to read the entire thread in context, including subsequent
> > responses. I realize that can be difficult on a mailing list, with
> > all the top-posting, conversation snippets, etc.
>
On Thu, Oct 18, 2018 at 12:24 PM Tomasz Torcz wrote:
>
> > You like gmail […]
>
> Using GMail (both legacy and Inbox) as a representation of email
> workflow and ergonomy is not fair. Gmail as a client is abysmal.
> No threading, no coloring of different level of citation, no integrated
> GPG
On Thu, Oct 18, 2018 at 12:03 PM Simo Sorce wrote:
> On Thu, 2018-10-18 at 11:51 -0700, Gerald B. Cox wrote:
> > On Thu, Oct 18, 2018 at 11:40 AM Simo Sorce wrote:
> >
> > > On Wed, 2018-10-17 at 11:02 -0700, Gerald B. Cox wrote:
> > > > On Wed, Oct 17, 2
On Thu, Oct 18, 2018 at 11:40 AM Simo Sorce wrote:
> On Wed, 2018-10-17 at 11:02 -0700, Gerald B. Cox wrote:
> > On Wed, Oct 17, 2018 at 10:55 AM Samuel Sieb wrote:
> >
> > > On 10/17/18 8:52 AM, Gerald B. Cox wrote:
> > > > Again, I use gmail a
On Thu, Oct 18, 2018 at 5:33 AM Matthew Miller
wrote:
> On Wed, Oct 17, 2018 at 01:39:30PM -0400, Neal Gompa wrote:
> > I cannot *ever* recommend, in good conscious, moving to Discourse for
> > Fedora development discussions.
> >
> > However, I think it's fantastic for user support, as those are
On Wed, Oct 17, 2018, 16:35 Anderson, Charles R wrote:
> On Wed, Oct 17, 2018 at 03:52:17PM -0300, Gerald B. Cox wrote:
> > I'm not an email expert by any means. What I said was that it works
> > perfectly fine for me. If people have an issue with it they should file a
&g
On Wed, Oct 17, 2018, 15:31 Anderson, Charles R wrote:
> On Wed, Oct 17, 2018 at 11:02:58AM -0700, Gerald B. Cox wrote:
> > On Wed, Oct 17, 2018 at 10:55 AM Samuel Sieb wrote:
> >
> > > On 10/17/18 8:52 AM, Gerald B. Cox wrote:
> > > > Again, I use gmail a
On Wed, Oct 17, 2018 at 10:48 AM Gerald B. Cox wrote:
>
>
>
>
> The thing is, it doesn't matter. Discourse is *not* designed to
>> support the types of discussions that do happen on these lists, nor is
>> it designed to handle the load or the number of disparat
On Wed, Oct 17, 2018 at 10:55 AM Samuel Sieb wrote:
> On 10/17/18 8:52 AM, Gerald B. Cox wrote:
> > Again, I use gmail and things look perfectly fine for me.
>
> That's because gmail only shows the HTML part.
>
Ah... so it's a
The thing is, it doesn't matter. Discourse is *not* designed to
> support the types of discussions that do happen on these lists, nor is
> it designed to handle the load or the number of disparate
> conversations.
I've experienced the switchover from mail lists to
> Discourse before with OpenMan
On Wed, Oct 17, 2018 at 10:31 AM Jason L Tibbitts III
wrote:
> >>>>> "GBC" == Gerald B Cox writes:
>
> GBC> People keep saying it isn't sufficient or it doesn't work. I've
> GBC> been using it for 3 days and looks and acts like a normal
On Wed, Oct 17, 2018 at 10:15 AM Matthew Miller
wrote:
> On Wed, Oct 17, 2018 at 05:00:32PM +, Anderson, Charles R wrote:
> > How do I start a thread on Discourse from email? We should start this
> > discussion over there so we can experience it ourselves.
>
> So, yeah, that's a thing: we cur
On Wed, Oct 17, 2018 at 9:40 AM Fulko Hew wrote:
>
>
> On Wed, Oct 17, 2018 at 12:28 PM Jason L Tibbitts III
> wrote:
>
> While I'm not a contributor to these lists, I do follow them
> and have so for probably 20 years now. Like Jason, I have had
> other projects move away from mailing lists, a
On Wed, Oct 17, 2018 at 7:38 AM Anderson, Charles R wrote:
> On Wed, Oct 17, 2018 at 07:23:28AM -0700, Gerald B. Cox wrote:
> > On Wed, Oct 17, 2018 at 5:07 AM Dominik 'Rathann' Mierzejewski <
> > domi...@greysector.net> wrote:
> > > I tried the mai
On Wed, Oct 17, 2018 at 5:07 AM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:
> On Tuesday, 16 October 2018 at 22:38, Dominik 'Rathann' Mierzejewski wrote:
> [...]
> > And I agree, too much clicking. Reading e-mail with mutt on a terminal
> > is so much faster.
>
> So, I tried th
On Tue, Oct 16, 2018 at 11:59 AM stan wrote:
> On Tue, 16 Oct 2018 08:51:33 -0700
> "Gerald B. Cox" wrote:
>
> > Yeah, based upon the trial and previous comments I knew it was being
> > considered. The point
> > of my thread was that many people probably h
On Tue, Oct 16, 2018 at 10:39 AM Neal Gompa wrote:
> On Tue, Oct 16, 2018 at 1:35 PM Simo Sorce wrote:
> >
> > Ah nice side-thing I just found out, discussion.fedoraproject.org does
> > not show *anything* unless I let my browser access this website
> > http://discourse-cdn-sjc1.com
> >
> > That
On Tue, Oct 16, 2018 at 10:32 AM Simo Sorce wrote:
> On Tue, 2018-10-16 at 07:12 -0700, Gerald B. Cox wrote:
>
> From the foreman post, in the comments:
> Email interface does not really work, there should be rather called
> “notifications”. You must visit the site ev
On Tue, Oct 16, 2018 at 8:41 AM Ben Cotton wrote:
>
> Council is considering it, and CommOps just started a 2-month
> experiment to see how it goes. It makes sense to me that we wait and
> see how those go before we start considering larger moves. I'm worried
> in particular about larger lists su
On Tue, Oct 16, 2018 at 8:06 AM Ben Rosser wrote:
> On Tue, Oct 16, 2018 at 10:39 AM Gerald B. Cox wrote:
> > But RSS really isn't the point of this thread. My point is that Fedora
> should move to Discourse. It's a much better solution for
> > discussion. We s
On Tue, Oct 16, 2018 at 7:25 AM Chris Murphy
wrote:
>
>
> On Tue, Oct 16, 2018, 8:13 AM Gerald B. Cox wrote:
>
>>
>> On Fri, Oct 5, 2018 at 9:21 AM Matthew Miller
>> wrote:
>> ...
>> > That's why the general trend is *away* from email.
>
On Fri, Oct 5, 2018 at 9:21 AM Matthew Miller
wrote:
...
> That's why the general trend is *away* from email.
>
> The Foreman community recently switched away from mailing lists in this
way,
> and
https://theforeman.org/2018/07/discourse-6-months-on-impact-assesment.html
> is really interesting an
https://bugzilla.redhat.com/show_bug.cgi?id=1603193
Hello, this record has been open since July with no response from the
maintainer. I'm not actually sure if this has dedicated maintainer or
is just reliant on proven packagers.
Another user has even provided a spec file which builds fine, so it
On Tue, Oct 9, 2018 at 8:21 PM Reindl Harald wrote:
>
> nice for you, other prefer email and *local* archives which sirely don't
> disappear *because* you control the whole client and if somebody next
> year makes a relaunch of the online stuff with a bad usability or
> lacking features you are do
On Tue, Oct 9, 2018 at 7:06 AM Anderson, Charles R wrote:
> One click is too much for my terminal email client via SSH on my
> phone. My email client already supports filtering into separate
> mailboxes for each list and also supports threads shown in a
> hierarchy. If Fedora lists go away in fa
On Thu, Oct 4, 2018 at 2:33 PM Matthew Miller wrote:
>
> The fact is, the world has moved away from quoted mail with inline replies.
> Top posting rules basically everywhere except hold-out old-school mailing
> lists. Gmail, both on the web and _especially_ on mobile, makes it almost
> impossible
On Tue, Oct 2, 2018 at 4:46 AM Ankur Sinha wrote:
> A known, but unsolved issue from the looks of it (from a 2014 post):
> https://productforums.google.com/forum/#!topic/gmail/d7ySu-m1rgY
Yep... and the issue is 4 years old and ends with the recommendation
of "Send Feedback". I have
no idea why
On Sun, Sep 16, 2018 at 4:12 PM Kevin Kofler wrote:
> We CANNOT just drop half of the distribution just because upstream
> arbitrarily decided to desupport its widely used language interpreter in
> favor of an incompatible new major version.
>
Well, to be fair the writing has been on the wall fo
On Thu, Sep 13, 2018 at 9:17 AM, Tomas Orsava wrote:
> Hi!
> We'd like to propose a new functionality for dnf: When a user tries to
> install a package XYZ and dnf doesn't find it, dnf would recommend them
> alternative packages. These offered packages would advertise that they are
> an alternati
On Wed, Sep 5, 2018 at 11:22 AM, John Florian
wrote:
> On 2018-09-05 13:41, Gerald B. Cox wrote:
>
> I would recommend you check out qmmp. It's light weight, runs with qt5
> and does what it sets out to do, which is be a flexible, lightweight music
> player that runs on qt5,
I would recommend you check out qmmp. It's light weight, runs with qt5 and
does what it sets out to do, which is be a flexible, lightweight music
player that runs on qt5, supports skins, has many good plugins for extra
features, supports tagged and folder based album covers, etc.
There is a threa
On Wed, Jul 25, 2018 at 4:48 AM, Vít Ondruch wrote:
>
> "new-sources" should not be mentioned in basic documentation. These should
> be added via means of "fedpkg import package.srpm".
>
> The workflow for new package is then:
>
> ~~~
> $ fedpkg import mypackage.srpm
> $ git commit -m "initial im
On Tue, Jul 24, 2018 at 10:07 AM, Artur Iwicki
wrote:
> That section of the guide is a bit poorly worded. You should *not* use
> "git add" on source tarballs. These should be added only via means of
> "fedpkg new-sources $FILES; git add ./sources". I believe what the guide
> means under "new sour
I received an email this AM from a fellow packager:
*Please, do not put source tarballs in git. This is not what is supposed to
happen. Package sources are managed with fedpkg, they are just added to the
lookaside cache and to the .gitignore file so you don't add them by mistake
to the reposito
On Mon, Jul 2, 2018 at 12:29 PM, Jonathan Dieter wrote:
> On Mon, 2018-07-02 at 07:46 -0700, Gerald B. Cox wrote:
> > https://fedoraproject.org/wiki/Changes/Zchunk_Metadata
> >
> > It appears to be a good idea, but when going through the readme, I
> > found this:
>
On Mon, Jul 2, 2018 at 8:06 AM, Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
> On Mon, Jul 2, 2018, 15:54 Gerald B. Cox wrote:
>
>> https://fedoraproject.org/wiki/Changes/Zchunk_Metadata
>>
>> It appears to be a good idea, but when going throu
https://fedoraproject.org/wiki/Changes/Zchunk_Metadata
It appears to be a good idea, but when going through the readme, I found
this:
*Please note that, while the code is pretty reliable and the file format
shouldn't see any further changes, the API is still not fixed. Please do
not use zchunk fo
1 - 100 of 349 matches
Mail list logo
