No missing expected images.
Failed openQA tests: 38/137 (x86_64), 14/24 (i386), 1/2 (arm)
ID: 231470 Test: x86_64 Server-dvd-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/231470
ID: 231483 Test: x86_64 Workstation-live-iso install_default@uefi
URL:
The following Fedora EPEL 6 Security updates need testing:
Age URL
22 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5aca1d385d
remctl-3.14-1.el6
20 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-dd6e4a3f0b
python34-3.4.8-1.el6
11
Dear all,
You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2018-05-01 from 10:00:00 to 11:00:00
US/Eastern
At fedora-meetin...@irc.freenode.net
The meeting will be about:
Meeting of the Modularity Working Group.
More information available at: [Modularity
On 04/30/2018 02:16 PM, Neal Gompa wrote:
>
> And there's still the fun restriction of XFS not being able to shrink. It's
> not particularly important in the server case, but in the desktop/laptop
> case, it happens enough in my experience that I'm not sure I'd want a
> default filesystem that
On Mon, Apr 30, 2018 at 2:14 PM Jason L Tibbitts III
wrote:
> > "CW" == Colin Walters writes:
> CW> I'd say it makes sense to revisit the default here globally in
> CW> Anaconda.
> Maybe. Have the issues which made XFS less suitable for use on
> "CW" == Colin Walters writes:
CW> I'd say it makes sense to revisit the default here globally in
CW> Anaconda.
Maybe. Have the issues which made XFS less suitable for use on laptops
been resolved? The primary one I recall was that each mounted
filesystem would have a
I'm orphaning the schroot package, since I no longer use it or work with it:
https://src.fedoraproject.org/rpms/schroot
There is currently a serious (crash) bug affecting the package in F28:
https://bugzilla.redhat.com/show_bug.cgi?id=1573253
Upstream:
On 04/05/2018 03:29 PM, Mark Reynolds wrote:
On 04/05/2018 07:02 AM, Florian Weimer wrote:
On 03/29/2018 10:59 PM, Mark Reynolds wrote:
I believe it's our cmocka tests that occur at rpm package time that
brought this to our attention. So it is easy to reproduce.
Well, I tried, but the
On Mon, Apr 30, 2018 at 10:25 AM, Yaakov Selkowitz
wrote:
gedit, like most GNOME components, uses gnome-autogen.sh; in this
particular case, iirc ACLOCAL_PATH="libgd" also needs to be set.
There's also AUTOPOINT='intltoolize --automake --copy' which gedit
needs for
On Mon, Apr 30, 2018 at 10:56:10AM -0400, Daniel Walsh wrote:
>
> Perhaps it is time to update my blog on running systemd in a unprivileged
> container.
Let's get the base images fixed so that at least that
ENV container ...
is there by default, to minimize the number of steps that are
On Fri, Apr 27, 2018 at 05:27:19PM +0200, Pavel Raiskup wrote:
> Hi all,
>
> just wanted to let you know about trivial experiment [1] with systemd in
> container. Non-privileged systemd can now pretty fine run in docker
> container (tested on Fedora 27 box).
>
> Could we support this under
On 2018-04-30 09:01, mcatanz...@gnome.org wrote:
> On Mon, Apr 30, 2018 at 7:52 AM, Florian Weimer wrote:
>> Such we change the guidelines to always run autoreconf? This would
>> also help with new architecture bringup because those often need
>> autotools fixes, but it will
On 30 April 2018 at 15:56, Daniel Walsh wrote:
> On 04/30/2018 10:42 AM, James Hogarth wrote:
>>
>> On 27 April 2018 at 17:47, Pavel Raiskup wrote:
>>>
>>> On Friday, April 27, 2018 5:41:19 PM CEST Lennart Poettering wrote:
On Fr, 27.04.18 17:27,
Hi,
On 29-04-18 21:03, Alexander Ploumistos wrote:
Hello Hans,
I've just upgraded a G50-30 and like Christian, I can not reproduce the
issue. I logged into MATE and GNOME, played with the brightness settings
while plugged in and on battery, it did not hang.
# cat
Hi,
On 30-04-18 12:59, Kamil Paral wrote:
On Sun, Apr 29, 2018 at 9:26 AM, Hans de Goede > wrote:
Hi All,
I'm sending this to the fedora-kernel and -devel lists
both to get the kernel team aware of this and because it
is not
On 04/30/2018 10:42 AM, James Hogarth wrote:
On 27 April 2018 at 17:47, Pavel Raiskup wrote:
On Friday, April 27, 2018 5:41:19 PM CEST Lennart Poettering wrote:
On Fr, 27.04.18 17:27, Pavel Raiskup (prais...@redhat.com) wrote:
Hi all,
just wanted to let you know about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
According Non-responsive Maintainer Policy I'm asking the maintainer
to respond 3rd time and resolve issues with packages.
RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1564875
- --
Sincerely,
Vitaly Zaitsev
On 27 April 2018 at 17:47, Pavel Raiskup wrote:
> On Friday, April 27, 2018 5:41:19 PM CEST Lennart Poettering wrote:
>> On Fr, 27.04.18 17:27, Pavel Raiskup (prais...@redhat.com) wrote:
>>
>> > Hi all,
>> >
>> > just wanted to let you know about trivial experiment [1] with
On Mon, 2018-04-30 at 09:01 -0500, mcatanz...@gnome.org wrote:
> On Mon, Apr 30, 2018 at 7:52 AM, Florian Weimer
> wrote:
> > Such we change the guidelines to always run autoreconf? This
> > would
> > also help with new architecture bringup because those often need
> >
On 04/30/2018 04:01 PM, mcatanz...@gnome.org wrote:
Some packages will not build when autoreconf is called outside
autogen.sh, and these packages typically do not distribute autogen.sh.
E.g. gedit. Packagers would need to work around such issues.
Isn't that against the spirit of the GPLv2 and
https://bugzilla.redhat.com/show_bug.cgi?id=1569981
--- Comment #4 from Fedora Update System ---
perl-Dancer2-0.206000-1.fc27 has been pushed to the Fedora 27 testing
repository. If problems still persist, please make note of it in this bug
report.
See
On Monday, April 30, 2018 2:52:54 PM CEST Florian Weimer wrote:
> On 04/09/2018 06:07 PM, Yaakov Selkowitz wrote:
> > On 2018-04-09 04:40, Florian Weimer wrote:
> >> On 04/09/2018 11:21 AM, Yaakov Selkowitz wrote:
> >>> On 2018-04-09 03:59, Florian Weimer wrote:
> Is there a recommend way to
On Mon, Apr 30, 2018 at 7:52 AM, Florian Weimer
wrote:
Such we change the guidelines to always run autoreconf? This would
also help with new architecture bringup because those often need
autotools fixes, but it will choke on really old or manually patched
upstream
On 04/09/2018 06:07 PM, Yaakov Selkowitz wrote:
On 2018-04-09 04:40, Florian Weimer wrote:
On 04/09/2018 11:21 AM, Yaakov Selkowitz wrote:
On 2018-04-09 03:59, Florian Weimer wrote:
Is there a recommend way to get libtool to pass through all flags
specified in CFLAGS and LDFLAGS unchanged,
On Mon, 2018-04-30 at 05:29 -0400, Charalampos Stratakis wrote:
>
> - Original Message -
> > From: "Martin Bukatovic"
> > To: python-devel@lists.fedoraproject.org
> > Sent: Sunday, April 29, 2018 9:18:16 PM
> > Subject: pyp2rpm version in fedora
> >
> > Dear
On Sun, Apr 29, 2018 at 9:26 AM, Hans de Goede wrote:
> Hi All,
>
> I'm sending this to the fedora-kernel and -devel lists
> both to get the kernel team aware of this and because it
> is not entirely clear to me how to best deal with this.
>
> I guess we should get this
Dne 28.4.2018 v 05:34 Ricky Elrod napsal(a):
> I am orphaning the packages:
> - rubygem-ronn
I'd like to take it ^^ over:
https://pagure.io/releng/issue/7471
Vít
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
- Original Message -
> From: "Martin Bukatovic"
> To: python-devel@lists.fedoraproject.org
> Sent: Sunday, April 29, 2018 9:18:16 PM
> Subject: pyp2rpm version in fedora
>
> Dear python devel list,
>
> I see that version of pyp2rpm packaged in Fedora 27 is
https://bugzilla.redhat.com/show_bug.cgi?id=1572822
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In
29 matches
Mail list logo