Hi,
I am orphaning krb5-appl in Fedora in the hopes that it will be retired.
Jason L Tibbitts III writes:
>>>>>> "RH" == Robbie Harwood writes:
>
> RH> Ah, I see, you're talking about the case when the enctype is already
> RH> not permitted. That all makes sense then.
>
> Right. Basically, if any one of these:
>
Jason L Tibbitts III writes:
>>>>>> "RH" == Robbie Harwood writes:
>
> RH> If I backport this to fc29, will that assuage people's concerns?
>
> I think it would certainly help and I wouldn't complain. In fact, I'd
> love to start running that
Tomasz Torcz writes:
> On Mon, Jan 07, 2019 at 04:12:47PM -0500, Robbie Harwood wrote:
>> Adam Williamson writes:
>>
>> > On Thu, 2019-01-03 at 22:40 -0600, Jason L Tibbitts III wrote:
>> >
>> >> But to be fair, MIT krb5 is not known for having grea
Zbigniew Jędrzejewski-Szmek writes:
> On Tue, Jan 08, 2019 at 04:45:53PM -0600, Jason L Tibbitts III wrote:
>> >>>>> "RH" == Robbie Harwood writes:
>>
>> RH> Ah, I see, you're talking about the case when the enctype is already
>> RH> no
Jason L Tibbitts III writes:
>>>>>> "RH" == Robbie Harwood writes:
>>>
>>> Well certainly there isn't much you can do to fix old principals on
>>> existing systems. But the current versions should be complaining
>>> loudly when
Adam Williamson writes:
> On Thu, 2019-01-03 at 22:40 -0600, Jason L Tibbitts III wrote:
>
>> But to be fair, MIT krb5 is not known for having great error output.
>> Not being able to start at all because the K/M has an enctype which is
>> acceptable and not at all deprecated according to the
Jason L Tibbitts III writes:
>>>>>> "RH" == Robbie Harwood writes:
>
> RH> I really don't think that "it won't work and there'll be error
> RH> messages" is an "extremely optimistic description".
>
> But to be fair, MIT krb5
Nikos Mavrogiannopoulos writes:
> How does this ties with crypto policies? libkrb5 is already under
> crypto policies and has these ciphers disabled by default. Is this
> change about removing them from the code or removing them from the
> capabilities of the KDC which is not covered by crypto
> BC> == Detailed Description ==
>
>
> Is it just me or does this not actually say clearly what is changing?
> The first paragraph talks about two RFCs. The second paragraph talks
> about how easy it is to break single DES. The third paragraph talks
> about how disabled by default is
Raphael, I'm confused how this doesn't comply. Their source code lives here:
https://github.com/h1kari/des_kpt
Also, let's keep comments on this thread *and CC me* - then there's only one
place to look for replies (and I'm not subscribed to this list). In any case,
as I stated there, if you
Many sites do intentionally, even - it's quite popular in University settings
and in the financial sector. Nothing really drives that home like breaking
support for it (which I'd like to say I've never done, but can't). Putting it
anywhere other than /afs would be crazy - especially when /afs
> The 2FA scheme that we are solely planning to support is U2F/FIDO2, and to
> the best of my knowledge there has so far not been any work on integrating
> this with any krb5 server.
It's not done, but I'm definitely working on this. We deployed
Ben Cotton writes:
> == Detailed Description ==
>
> Currently we know how to make an installable OS with packages that
> doesn't require the use of scriptlets, indeed rpm-ostree and others
> have already done this on a significantly bigger scale. So we plan to
> remove direct scriptlets from
> Here's the scriptlet:
>
> %triggerun libs -- krb5-libs < 1.15.1-5
> if ! grep -q 'includedir /etc/krb5.conf.d' /etc/krb5.conf ; then
> sed -i '1i # To opt out of the system crypto-policies
> configuration of krb5,
> remove the\n# symlink at /etc/krb5.conf.d/crypto-policies which will
> not
st alternatives
systems (e.g., Debian) have had packages build against both; in my
opinion this is more effort than it's worth. You end up exposing all
the compatibility issues (libgssapi is standardized; libkrb5 is not; the
ccache format is ad hoc best ef
Nico Kadel-Garcia writes:
> Robbie Harwood wrote:
>> Nico Kadel-Garcia writes:
>>> Robert Marcano wrote:
>>>> Nico Kadel-Garcia wrote:
>>>>> Alexander Bokovoy wrote:
>>>>>> Dario Lesca wrote:
>>>>>>> Rob
Alexander Bokovoy writes:
> On ke, 04 syys 2019, alcir...@gmail.com wrote:
>>On Mon, 2019-09-02 at 17:14 +0200, Dario Lesca wrote:
>>>
>>> After few minutes almost everything work well, except for a thing ...
>>> all windows PC cannot access to others windows PC.
>>
>> Hey Dario.
>> Since in
Alex Chernyakhovsky writes:
> On Wed, Sep 4, 2019 at 5:16 PM Alex Chernyakhovsky wrote:
>> On Wed, Sep 4, 2019 at 3:33 PM Robbie Harwood wrote:
>>>
>>> Hi Fedora,
>>>
>>> I'm trying to contact Alex Chernyakhovsky and Othman Madjoudj, who
>>>
Hi Fedora,
I'm trying to contact Alex Chernyakhovsky and Othman Madjoudj, who are
the maintainers of mosh as far as I can tell. I have started the
nonresponsive maintainer process due to lack of contact through bugzilla
mail; bugs are https://bugzilla.redhat.com/show_bug.cgi?id=1697355 and
mcatanz...@gnome.org writes:
> Felipe Borges wrote:
>
>> The "Fedora" account is just a branded Kerberos account. By adding a
>> Fedora account in GNOME Online Accounts you would get automatically
>> signed on whenever you'd need to enter your FAS credentials. This
>> means while accessing
mcatanz...@gnome.org writes:
> Robbie Harwood wrote:
>
>> Can you link the bug you've filed about this?
>
> I don't even know where to file a bug. Which component? kerberos?
> xdg-desktop-portal?
When filing bugs that you don't know the cause of, it's best to start
w
Miro Hrončok writes:
> I'd like to drop python2-Cython subpackage from Cython, as I consider
> it not needed, however there are still packages that buildrequire
> it. Let me know if you want to maintain python2-Cython instead of me
> and Igor.
Hi, I believe you're CC'd on the thread with myself
Pierre-Yves Chibon writes:
> When you run `fedpkg build` on Rawhide, your package will be built in
> a new koji tag (which will be the default target for Rawhide). The
> package will be picked up from this koji tag, signed and moved onto a
> second tag. Bodhi will be notified by koji once this
> On Wed, Jul 24, 2019 at 11:30:45AM -0400, Robbie Harwood wrote:
>
> So we don't have an easy way to do this. I have a script that monitors the
> entire pipeline/workflow in production and in staging.
> I have been querying datagrepper for messages about the build that I've m
Pierre-Yves Chibon writes:
> Here is what the vision we came to and that we would like to discuss:
>
> ○ Every changes to dist-git is done via pull-requests
> ○ Pull-requests are automatically tested
> ○ Every commit to dist-git (ie: PR merged) is automatically built in koji
> ○ Every build in
Alex Chernyakhovsky writes:
> Yeah, I have no idea how I missed that bug. But I've uploaded 1.3.2
> for all active branches and requested an epel8 branch, so that's all I
> can do for now :)
Appreciated.
Thanks,
--Robbie
signature.asc
Description: PGP signature
"Colin Walters" writes:
> On Wed, Oct 2, 2019, at 1:40 PM, Fabio Valentini wrote:
>
>> As others in the thread have pointed out, mandatory pull requests
>> just make no sense for most single-maintainer projects, which most
>> packages probably are.
>
> Well, a lot of this relates to what the
"Michael J Gruber" writes:
> There is the current worklflow and the current mindset. One influences
> the other.
>
> For a long-time gitter, the prevailing Fedora packager mindset is
> still very much "dist-cvs". dist-git is often used as merely a tool to
> drive "dist-something", not so much as
Dario Lesca writes:
> I have fill this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1757071
>
> This error happen into my test Samba DC MIT Kerberos environment
> If you suggest to me some trick I can test it
Single-DES support has been removed from krb5 as per
Robbie Harwood writes:
> Stephen Gallagher writes:
>
>> My intention was to provide some scope to the problem, because it
>> seemed that a lot of alternatives being floated were not seeing some
>> of the more subtle cases that we were trying to address. However
Miro Hrončok writes:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
>
Stephen Gallagher writes:
> My intention was to provide some scope to the problem, because it
> seemed that a lot of alternatives being floated were not seeing some
> of the more subtle cases that we were trying to address. However, the
> biggest problem is that nearly every email to the list
Adam Samalik writes:
> This is the Minimization Objective [0] update.
>
> Status: Discovery phase
>
> == Next phase approval ==
>
> Next phase proposal [1] is being voted on by the Council — only positive
> votes so far!
>
> == Feedback Pipeline ==
>
> A few new features developed!
>
> 1/ A
Ken Dreyer writes:
> I work on a team at Red Hat with Kefu. He is very active with upstream
> Ceph, though I have not watched his Fedora activity or lack thereof.
>
> Is there a particular Fedora bug that you need Kefu to address?
This is probably about
"Johannes Lips" writes:
> What I found weird is that you can't comment on an update, which is
> already pushed to stable. A lot of users are only hit by a bug, once
> it reaches stable and then you don't have any possibility to highlight
> a bug report or an issue with this update. I would like
Fabio Valentini writes:
> On Sat, Dec 7, 2019, 17:30 Mattia Verga via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> Il 06/12/19 21:51, Johannes Lips ha scritto:
>> >> "Johannes Lips" > >>
>> >>
>> >> We already have a tool for reporting issues and problems, and it's not
>> >> bodhi. If
Tomasz Torcz writes:
> On Tue, Oct 15, 2019 at 01:56:11PM -0400, Robbie Harwood wrote:
>> Matthew Miller writes:
>>
>> > On Tue, Oct 15, 2019 at 12:36:15PM +0200, Miro Hrončok wrote:
>> >>> As package maintainers we all make technical decisions which have
Matthew Miller writes:
> On Tue, Oct 15, 2019 at 12:36:15PM +0200, Miro Hrončok wrote:
>>> As package maintainers we all make technical decisions which have
>>> significant impact on our users every day - whether that's in the
>>> choice of defaults, choice of build flags, or whatever. Honestly
Stephen John Smoogen writes:
> On Thu, 17 Oct 2019 at 14:15, Randy Barlow
> wrote:
>
>> Or better, can we employ a solution that another distribution has
>> developed?
>
> Not without using their packaging system, their build system and their
> other design choices. Working out slots would
Christopher Engelhard writes:
> On 18.10.19 17:21, Robbie Harwood wrote:
>
>> While you're right that the solutions from source distros (i.e., NixOS
>> and Gentoo) would be very hard to adapt, binary distros have also solved
>> this problem in different ways. I'm mos
Andreas Bierfert writes:
> On Thu, 2019-10-10 at 14:23 -0400, Robbie Harwood wrote:
>> Hello,
>>
>> In accordance with Fedora non-responsive maintainer policy, I'm
>> sending this message in attempt to contact Andreas Bierfert (awjb).
>>
>> Required
... and that's the wrong list. My bad.
Thanks,
--Robbie
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:
Hello,
In accordance with Fedora non-responsive maintainer policy, I'm sending
this message in attempt to contact Andreas Bierfert (awjb).
Required non-responsive maintainer bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1760528
Open unaddressed bugs (53 in total):
Matthew Miller writes:
> On Mon, Oct 07, 2019 at 03:20:21PM -0400, Alexander Scheel wrote:
>
>>> And where is the software for those containers coming from? Some
>>> container registry like Docker Hub? One of the main points of
>>> Modularity is to provide a trusted source of software to install
Björn Persson writes:
> Panu Matilainen wrote:
>> On 10/2/19 8:33 PM, Matthew Miller wrote:
>>> On Wed, Oct 02, 2019 at 05:31:56PM +0100, Richard W.M. Jones wrote:
>>>
> ○ Every changes to dist-git is done via pull-requests
Erm, no thank you. Pull requests are a terrible
Pierre-Yves Chibon writes:
> On Wed, Oct 02, 2019 at 03:17:33PM -0400, Robbie Harwood wrote:
>
>> With about six more emails about it, sure. And another piece of
>> infrastructure that has to be up and bug-free.
>>
>> Even the gating and bodhi emails today
Chris Murphy writes:
> On Fri, Oct 11, 2019 at 6:57 AM Simo Sorce wrote:
>> On Fri, 2019-10-11 at 09:56 +0200, Daniel Mach wrote:
>>> On 10/7/19 8:55 PM, Simo Sorce wrote:
I have to ask, given containers are so popular and can deal with
any dependency without conflicting with system
Hello,
In accordance with Fedora's non-responsive maintainer policy, I'm
sending this message in attempt to contact Jamie Nguyen (jamielinux).
Required non-responsive maintainer bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1760898
Open unaddressed bugs (219 in total):
David Cantrell writes:
> On Tue, Dec 17, 2019 at 11:21:45PM +0100, Miro Hrončok wrote:
>> On 17. 12. 19 21:57, David Cantrell wrote:
>>> 1) Are modules allowed to bundle packages that are provided by and
>>> currently maintained in the base system? Are there are restrictions
>>> to what a
James Paul Turner writes:
> Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1785011
>
> This bug is part of the non-responsive maintainer procedure for
> btashton, following
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
> .
>
> Both of your
Hi,
When replying to digests, I'd appreciate if you could please make an
effort to have the posts thread properly for the rest of us. Fedora
mailing list guidance on this:
https://fedoraproject.org/wiki/Mailing_list_guidelines#Replying_to_Digests
Thanks,
--Robbie
signature.asc
Description:
Steve Grubb writes:
> Hello,
>
> We are working on Application Whitelisting. For this to work, we need
> to have a list of things that we trust. At the moment, that list is
> well over 400k on a desktop install. But we really need to get that
> smaller.
Not that I disagree, but... to what end?
Clement Verna writes:
> Fabio Valentini wrote:
>> Clement Verna wrote:
>>
>>> Hi all,
>>>
>>> FMN (https://apps.fedoraproject.org/notifications) is currently one
>>> of the main blocking point for dropping fedmsg in favour of
>>> fedora-messaging. FMN is quite important to the community and
tMario Torre writes:
> On Mon, Jan 27, 2020 at 5:28 PM Robbie Harwood wrote:
>
>>> You would not expect a GCC devroom to be concerned about the
>>> problems of all packages written in C and C++, so why would Java be
>>> any different?
>>
>> Hone
Julen Landa Alustiza writes:
> (snip)
>
> 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen:
>> To me that's the all point of this
>> process, let's put down what we *really* *really* need and then look at
>> the different options.
>>
>
> Do we *really* *really* need to compete with
Stephen John Smoogen writes:
> On Tue, 28 Jan 2020 at 13:01, Robbie Harwood wrote:
>>
>> "Richard W.M. Jones" writes:
>>
>> > I always think that Fedora works fine if you maintain 1-5 packages.
>> > It's possible to maintain 20 with a lot of wor
Richard Shaw writes:
> Not replying to anyone in particular but to the thead as a whole...
>
> 1. Nothing in the packager introduction process prepares a packager
> for what to do when they get a CVE filed against one of their
> packages. I found the whole ordeal rather stressful.
Agreed, this
Neal Gompa writes:
> Michal Konecny wrote:
>> Vít Ondruch wrote:
>>> Neal Gompa napsal(a):
Randy Barlow wrote:
> Vít Ondruch wrote:
>
>> cough cough errata cough cough
>>
>> Honestly, sometimes the disconnect between what is going on in
>> Fedora and internally in
Michael Schwendt writes:
> On Fri, 31 Jan 2020 at 18:11, Robbie Harwood wrote:
>>
>> I could have also needinfo(Michael) (and in hindsight I probably
>> should have), but based on their reaction, I don't think they would
>> have been any happier with that.
>
&g
Fabio Valentini writes:
> Michael Schwendt wrote:
>> On Thu, 30 Jan 2020 14:44:50 +0100, Kevin Kofler wrote:
>>> Fabio Valentini wrote:
>>
>> All this would not even interest me at all, but almost a week ago
>> someone from Red Hat Security decided it would be a good idea to
>> assign to me
"Richard W.M. Jones" writes:
> I always think that Fedora works fine if you maintain 1-5 packages.
> It's possible to maintain 20 with a lot of work. And if you want to
> maintain 100+ (things like the ocaml-* set that I help to maintain)
> then you have to write your own automation. Could we
Andrew Haley writes:
> On 1/26/20 11:52 AM, Nicolas Mailhot wrote:
>> Le dimanche 26 janvier 2020 à 10:10 +, Andrew Haley a écrit :
>>> On 1/26/20 8:43 AM, Nicolas Mailhot via devel wrote:
>>>
Java has been in a terminal course in Fedora for a year at
least. You can see how much
"John M. Harris Jr" writes:
> On Saturday, January 25, 2020 2:52:05 PM MST Chris Murphy wrote:
>
>> Question and (pre)proposal:
>>
>> Can Fedora converge on a single swap-on-ZRAM implementation, and if
>> so, which one? Fedora Workstation WG wants to move to swap-on-ZRAM by
>> default in Fedora
Andrew Lutomirski writes:
>> On Jan 16, 2020, at 3:48 AM, Sarah Finn wrote:
>>
>> Hi all,
>>
>> I hope you are all well.
>>
>> I would like to invite you to contribute to our new initiative: AAA
>> replacement login.
>
> I’ll offer a couple of suggestions:
>
> Right now, I enter my Fedora
Alexander Bokovoy writes:
> On ti, 21 tammi 2020, Alex Scheel wrote:
>
>> For a period of time, IDM tried using Pagure for FreeIPA development.
>> They filed a huge number of issues. Now we host issues on Pagure, and
>> have moved development to GitHub. [*] I think we've mostly quit
>> filing
"Colin Walters" writes:
> On Tue, Jan 7, 2020, at 6:41 AM, Tom Hughes wrote:
>
>> I'd love to find a way to directly integrate the likes of gem, npm
>> etc directly into our packaging rather than us having to repackage
>> everything by hand but I just don't see any way of doing it without
>>
Kairui Song writes:
> What I'm trying to do is reduce the initramfs size used for kdump.
> Kdump loads a crash kernel and kdump initramfs image in a prereseved
> memory region, which get booted when current kernel crashed and
> perform crash dump. The prereserved memory is limited, so initramfs
"John M. Harris Jr" writes:
> On Friday, December 20, 2019 10:59:52 AM MST Chris Murphy wrote:
>> Issuing the command once per week harms no one
>
> Based on what's actual in the Change proposal, this is not the case.
>
> Even if this goes through, in my opinion, it should only affect the GNOME
Nico Kadel-Garcia writes:
> On Thu, Jan 2, 2020 at 2:48 PM Robbie Harwood wrote:
>> "John M. Harris Jr" writes:
>>> On Friday, December 20, 2019 10:59:52 AM MST Chris Murphy wrote:
>>>
>>>> Issuing the command once per week harms no one
>
Chris Murphy writes:
> On Fri, Jan 3, 2020 at 9:06 AM Robbie Harwood wrote:
>> Nico Kadel-Garcia writes:
>>> On Thu, Jan 2, 2020 at 2:48 PM Robbie Harwood wrote:
>>>> "John M. Harris Jr" writes:
>>>>> On Friday, December 20, 2019 1
Ben Cotton writes:
> https://fedoraproject.org/wiki/Changes/EnableEarlyoom
>
> == Summary ==
> Install earlyoom package, and enable it by default. This will cause
> the kernel oomkiller to trigger sooner, but will not affect which
> process it chooses to kill off. The idea is to recover from out
Robbie Harwood writes:
> Ben Cotton writes:
>
>> https://fedoraproject.org/wiki/Changes/EnableEarlyoom
>>
>> == Summary ==
>> Install earlyoom package, and enable it by default. This will cause
>> the kernel oomkiller to trigger sooner, but will not affect
Robbie Harwood writes:
> Miro Hrončok writes:
>
>> The following packages are orphaned and will be retired when they
>> are orphaned for six weeks, unless someone adopts them. If you know for sure
>> that the package should be retired, please do so now with a
Miro Hrončok writes:
> On 06. 01. 20 12:44, Peter Robinson wrote:
>
>>> As said in the e-mail, if you think the policy needs to be adapted,
>>> please discuss - I have made sure the recent changes in the policy
>>> are discussed with the community, especially since you were so angry
>>> when I
"John M. Harris Jr" writes:
> On Friday, January 3, 2020 1:51:00 PM MST Robbie Harwood wrote:
>> Robbie Harwood writes:
>>> Ben Cotton writes:
>>>
>>>> https://fedoraproject.org/wiki/Changes/EnableEarlyoom
>>>>
>>>&
Chris Murphy writes:
> Robbie Harwood wrote:
>> "John M. Harris Jr" writes:
>>> On Friday, January 3, 2020 1:51:00 PM MST Robbie Harwood wrote:
>>>> Robbie Harwood writes:
>>>>> Ben Cotton writes:
>>>>>
>>>>
Tom Callaway writes:
> Recently, someone filed a bug against chromium, noting that it was
> benchmarking notably slower than Google Chrome or chromium-freeworld
> (from rpmfusion). I tested locally and confirmed it. They suspected
> that Fedora's optflags were to blame, but since chromium
Aoife Moloney writes:
> * We found a password, we do not know whose it is, but we have turned
> it into the lost and found.
I'm sorry, what? Can you explain what this is and what it means?
Thanks,
--Robbie
signature.asc
Description: PGP signature
Ken Dreyer writes:
> On Tue, Mar 10, 2020 at 11:55 AM Kevin Fenzi wrote:
>>
>> when you see a proxy name there it usually means you have rdns true in
>> /etc/krb5.conf (it should be false), or krb_rdns or krb_canon_host true
>> in /etc/koji.conf or ~/.koji.conf (should be false).
>
> I think
Daniel Mach writes:
> Dne 12. 03. 20 v 19:26 Pat Riehecky napsal(a):
>
>> I realize I'm thinking about the Pie in the Sky, but:
>>
>> Would it be possible for 'microdnf' to become the base for 'dnf' so
>> that extra 'dnf' functionality is added via some kind of
>> modules/plugins/etc behaviour?
Neal Gompa writes:
> Miro Hrončok wrote:
>> Stephen Gallagher wrote:
>>
>>> In general, very few packages should even need conditionalizing at
>>> all; that's why I've been saying that this discussion is premature.
>>
>> Most of the Python packages we maintain in RHEL would need
Nicolas Mailhot via devel writes:
> Le mercredi 25 mars 2020 à 13:09 +0100, Aleksandra Fedorova a écrit :
>> Miro Hrončok wrote:
>>
>> As I mentioned in the previous mail, branching goes against the
>> purpose of the effort.
>>
>> What we like to achieve is to create a continuous flow from
Clement Verna writes:
> Neal Gompa wrote:
>> Clement Verna wrote:
>>
>> As for Pagure itself, I think this is where we fundamentally
>> disagree. I think it behooves us to own and provide an experience
>> tailored for our community from beginning to end. That's why we have
>> Koji, Bodhi,
Petr Pisar writes:
> On Sun, Mar 29, 2020 at 12:56:42AM +0100, clime wrote:
>
>> You can make a separate namespace for this in dist-git. It doesn't
>> need to be a separate branch. That way, you won't be disturbing
>> anyone elses space.
>
> A different name space means a different repository.
Stephen Gallagher writes:
> Please see the newly-updated
> https://fedoraproject.org/wiki/Changes/ELN_Buildroot_and_Compose
> for more details[1].
This page states:
> The fix will be done via a pull request that states a time limit. We
> want the regular maintainers to see / comment / commit,
Paul Frields writes:
> Neal Gompa wrote:
>> Nicolas Mailhot wrote:
>>> Leigh Griffin a écrit :
>>>
To distill it down:
- Gitlab has more features that are needed right now for our
stakeholder group
- Gitlab has an entire company dedicated to roadmap features, we do
Hi, in accordance with non-responsive maintainer policy [1], does anyone
know how to contact Michal Ruprich (mruprich)?
Michal, if you're still interested in maintaining your packages, please
respond here and also in:
https://bugzilla.redhat.com/show_bug.cgi?id=1815163
Kamil Dudka writes:
> On Thursday, April 23, 2020 4:08:24 PM CEST Robbie Harwood wrote:
>> That's not how this works.
>
> Yes and I am trying to suggest you how to make it work.
>
>> Even if your assertion were true (which it isn't), we have a closure
>> status for
Kamil Dudka writes:
> On Wednesday, April 22, 2020 7:28:36 PM CEST Robbie Harwood wrote:
>> To make this as clear as I can, let's look at
>> https://bugzilla.redhat.com/show_bug.cgi?id=1815163
>
> The above mentioned ticket is not a bug report in the first place.
That
Martin Sehnoutka writes:
> Hi Robbie,
>
> I'm pretty sure Michal would respond if you contacted him via email.
Hi Martin, you've dropped Michal from CC in your reply, but I did
include Michal on my original email. In other words: this *is*
contacting by email :)
> Also Michal is far from
Ty Young writes:
> On 5/12/20 5:55 AM, Felix Schwarz wrote:
>> Am 12.05.20 um 12:32 schrieb Ty Young:
>>
>>> Right, I figured it was some Fedora policy and not up to you. I
>>> suppose I should have been more clear there. Sorry for any
>>> confusion, it was aimed at the Fedora project as a whole
Tomas Tomecek writes:
> Thank you all for raising all the questions and concerns.
>
> Before I reply, I'd like to stress that we are still in a prototype
> phase - not everything is solved (clearly) and at this point, we
> experiment with the workflow mostly.
>
> Luckily, force-pushes are not
Petr Pisar writes:
> On Sat, May 16, 2020 at 12:56:06PM +0200, Dominique Martinet wrote:
>
>> How should I go about with that? Open bz bugs to all the packages I
>> listed? strongly suggesting to get things to move to /usr/share (17)
>> and flatpak (suggest some kind of cache? not sure they'll
Dan Čermák writes:
> Eduard Lucena writes:
>
>> My name is Eduard Lucena, some of you maybe know me, tons of you
>> don't. I'm part of the marketing team and host of the Fedora Podcast.
>>
>> I'm starting a SIG about i3 tiling window manager [1], with the final
>> objective of create a remix
Björn Persson writes:
> Kamil Dudka wrote:
>
>> The timer is currently not enabled on fresh installs to avoid
>> surprises (such as data lost)
>
> That's a surprise only if somebody expected that logs would be retained
> forever. Do people expect that?
Yes.
> Random programs failing because
Tomasz Torcz writes:
> On Sun, Mar 15, 2020 at 11:12:43PM +0100, Marius Schwarz wrote:
>> Am 15.03.20 um 13:32 schrieb Vitaly Zaitsev via devel:
>> > On 14.03.2020 13:05, Marius Schwarz wrote:
>> >> If you encrypt the fedora ( or any ) installation with luks, as
>> >> security of a mobile
Vít Ondruch writes:
> Dne 05. 05. 20 v 21:26 Robbie Harwood napsal(a):
>> Tomas Tomecek writes:
>>
>>> Thank you all for raising all the questions and concerns.
>>>
>>> Before I reply, I'd like to stress that we are still in a prototype
>
Vít Ondruch writes:
> Dne 06. 05. 20 v 20:39 clime napsal(a):
>> On Wed, 6 May 2020 at 13:21, Fabio Valentini wrote:
>>> On Wed, May 6, 2020 at 10:37 AM Vít Ondruch wrote:
Dne 05. 05. 20 v 18:37 Fabio Valentini napsal(a):
> On Mon, May 4, 2020 at 5:06 PM Tomas Tomecek wrote:
Vít Ondruch writes:
> Hi Robbie,
>
> I wonder if you had some intentions with the packages,
If you're asking if I plan to take them, I do not. They have been
orphaned, so anyone interested can pick them up. (They should refer to
1 - 100 of 243 matches
Mail list logo
