https://bugzilla.redhat.com/show_bug.cgi?id=1785770
Emmanuel Seyman changed:
What|Removed |Added
Status|NEW |ASSIGNED
Depends On|
On Sunday, May 19, 2019 2:05:46 AM MST Silvia Sánchez wrote:
> Hello,
>
> Yes, I know Python 2 will be soon removed, but I can't just let Bleachbit
> die. It's too useful for that.
> Finding a sponsor seems to be the hard bit. I've been looking for one for
> ages.
> Thanks for the answer.
>
>
On Sat, Dec 21, 2019 at 5:06 PM Kevin Kofler wrote:
>
> Nico Kadel-Garcia wrote:
> > It is *possible* to branch from right before the commit, and put
> > *that* in your branch or your local repo to work with. It's also
> > possible to replace an upstream git repo, entirely, with a repo that
> >
On Sat, 21 Dec 2019 at 00:37, Neal Gompa wrote:
[..]
> I believe it's also used by the %cmake and %meson macros.
Yep.
Look on the output of the “rpm -E %cmake” and you will find that to switch
to other C and C++ compilers all what you need to do is redefine %__cc and
%__cxx macros,
The same is
Nico Kadel-Garcia wrote:
> It is *possible* to branch from right before the commit, and put
> *that* in your branch or your local repo to work with. It's also
> possible to replace an upstream git repo, entirely, with a repo that
> does not have the commit.
The Fedora dist-git git hooks won't
On Sat, Dec 21, 2019 at 3:20 PM Fabio Valentini wrote:
>
> On Sat, Dec 21, 2019 at 9:11 PM Antonio Trande wrote:
> >
> > Hi all.
> >
> > Please, can you help me to remove this last commit on EPEL7 branch?
> >
> >
On 21/12/19 21:50, Fabio Valentini wrote:
>>
>> Yes,
>> https://src.fedoraproject.org/rpms/petsc4py/c/cf25d6d376fc95034decec02c2e1501f97ae4955?branch=epel7
>
> It failed because it can't tell which branch to restore the state to,
> since you're reverting a merge commit.
>
> "git revert HEAD -m
On Sat, Dec 21, 2019 at 9:44 PM Antonio Trande wrote:
>
>
>
> On 21/12/19 21:38, Fabio Valentini wrote:
> > On Sat, Dec 21, 2019 at 9:30 PM Antonio Trande
> > wrote:
> >>
> >> On 21/12/19 21:19, Fabio Valentini wrote:
> >>> On Sat, Dec 21, 2019 at 9:11 PM Antonio Trande
> >>> wrote:
>
>
On 21/12/19 21:38, Fabio Valentini wrote:
> On Sat, Dec 21, 2019 at 9:30 PM Antonio Trande wrote:
>>
>> On 21/12/19 21:19, Fabio Valentini wrote:
>>> On Sat, Dec 21, 2019 at 9:11 PM Antonio Trande
>>> wrote:
Hi all.
Please, can you help me to remove this last commit on
On Sat, Dec 21, 2019 at 9:30 PM Antonio Trande wrote:
>
> On 21/12/19 21:19, Fabio Valentini wrote:
> > On Sat, Dec 21, 2019 at 9:11 PM Antonio Trande
> > wrote:
> >>
> >> Hi all.
> >>
> >> Please, can you help me to remove this last commit on EPEL7 branch?
> >>
> >>
On 21/12/19 21:19, Fabio Valentini wrote:
> On Sat, Dec 21, 2019 at 9:11 PM Antonio Trande wrote:
>>
>> Hi all.
>>
>> Please, can you help me to remove this last commit on EPEL7 branch?
>>
>> https://src.fedoraproject.org/rpms/petsc4py/c/e47fbb3ef419b7be939108c2b1deff3f105bfdbc?branch=epel7
>>
On Sat, Dec 21, 2019 at 9:11 PM Antonio Trande wrote:
>
> Hi all.
>
> Please, can you help me to remove this last commit on EPEL7 branch?
>
> https://src.fedoraproject.org/rpms/petsc4py/c/e47fbb3ef419b7be939108c2b1deff3f105bfdbc?branch=epel7
>
> (I wish top return to the 3.11.0 release of
Hi all.
Please, can you help me to remove this last commit on EPEL7 branch?
https://src.fedoraproject.org/rpms/petsc4py/c/e47fbb3ef419b7be939108c2b1deff3f105bfdbc?branch=epel7
(I wish top return to the 3.11.0 release of petsc4py)
Regards.
--
---
Antonio Trande
Fedora Project
mailto 'sagitter
On Sat, 2019-12-21 at 20:50 +0300, Silvia Sánchez wrote:
>
> Hi Alessio,
>
> Yes, I am.
We could comaintain it, if you like, even if I'm not an expert
packager.
Bleachbit was retired from F31 [1]
Another point is that bleachbit version 3.0 still requires python2.
So, since "the top priority [of
On Fri, Nov 22, 2019 at 04:17:03PM +, Zbigniew Jędrzejewski-Szmek wrote:
> This version has support for disabling watchdogs at configuration time
> for services bundled with systemd. I want to do that in Fedora, because almost
> all "crash" reports that we get are about the watchdog firing on
Hi Alessio,
Yes, I am.
On Sat, 21 Dec 2019 at 20:33, Alessio Ciregia wrote:
> Hello Lailah, are you still interested in maintaining that?
>
> A.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to
Hello Lailah, are you still interested in maintaining that?
A.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Sat, 2019-12-21 at 10:52 -0500, Josh Boyer wrote:
> On Thu, Dec 19, 2019 at 5:48 PM Jeff Law wrote:
> > On Thu, 2019-12-19 at 16:24 -0600, Neal Gompa wrote:
> > > On Thu, Dec 19, 2019 at 4:14 PM Jeff Law wrote:
> > > > On Thu, 2019-12-19 at 21:56 +, devel-
> > > >
On Thu, Dec 19, 2019 at 5:48 PM Jeff Law wrote:
>
> On Thu, 2019-12-19 at 16:24 -0600, Neal Gompa wrote:
> > On Thu, Dec 19, 2019 at 4:14 PM Jeff Law wrote:
> > > On Thu, 2019-12-19 at 21:56 +, devel-
> > > requ...@lists.fedoraproject.org wrote:
> > >
> > > Neal,
> > >
> > >
> > > > I'm
No missing expected images.
Compose PASSES proposed Rawhide gating check!
All required tests passed
Failed openQA tests: 4/155 (x86_64), 1/2 (arm)
Old failures (same test failed in Fedora-Rawhide-20191218.n.0):
ID: 501082 Test: x86_64 Server-dvd-iso modularity_tests
URL:
On Saturday, December 21, 2019 1:59:03 AM MST Vitaly Zaitsev via devel wrote:
> On 20.12.2019 21:53, Chris Murphy wrote:
>
> > If your LUKS drives are listed in fstab, they will have fstrim issued
> > and it will pass down to the physical drive.
>
>
> Only with enabled discard option in
https://bugzilla.redhat.com/show_bug.cgi?id=1785831
Bug ID: 1785831
Summary: perl-CPAN-Perl-Releases-5.20191220 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-CPAN-Perl-Releases
Keywords:
https://bugzilla.redhat.com/show_bug.cgi?id=1785827
Bug ID: 1785827
Summary: perl-Module-CoreList-5.20191220 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Module-CoreList
Keywords:
On 20.12.2019 21:53, Chris Murphy wrote:
> If your LUKS drives are listed in fstab, they will have fstrim issued
> and it will pass down to the physical drive.
Only with enabled discard option in /etc/crypttab, because trimming of
LUKS significantly decrease security level (everyone even without
On 20.12.2019 21:30, Jan Kratochvil wrote:
> This is AFAIK not enough for LUKS drives, will it be supported for LUKS?
If you want to enable TRIM for LUKS, you should add discard option to
/etc/crypttab file.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
25 matches
Mail list logo