I don't see anything but green on status.fedoraproject.org, but the
last two builds I have submitted have both failed on s390x only with
an error that looks like this:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/koji/daemon.py", line 1244, in runTask
response =
Brotli 1.0.5 is out and I might update it in Rawhide, but the tool I used
to check ABI differences seems to have stopped working on both Arch and
Fedora. So I'm not sure if Brolti included any ABI/API breaking changes.
Should I push an update anyway?
--
GPG Keys: https://keybase.io/pouar
Tox ID:
Hi,
I have just gotten the python-pyopengl package to a state where it
builds in the f29-python side tag, but will have to orphan the package
from this point on, as I just don't have the spare cycles to work on
it moving forward.
The package is pretty dead upstream, with the last proper release
b
On Sat, Jun 30, 2018 at 01:22:46PM +0200, Nicolas Mailhot wrote:
> Le samedi 30 juin 2018 à 12:46 +0200, Nicolas Mailhot a écrit :
> > Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit :
> > > FWIW, a fun read from the debian pkg-go list about packaging docker
> > > https://www.mail-
Hi!
On Sat, Jun 30, 2018 at 6:02 PM, Robert-André Mauchin
wrote:
> I've Searched for bugs at our ArchLinux fellows and they mentioned this:
>
> https://bugs.archlinux.org/task/57542?project=0&order=id&sort=desc&status
> %5B0%5D=closed&string=gcompris-qt
>
> It seems caused by this change:
> http
On Sat, Jun 30, 2018 at 12:46:28PM +0200, Nicolas Mailhot wrote:
> Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit :
> > FWIW, a fun read from the debian pkg-go list about packaging docker
> > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.ne
> > t/msg00032.htm
No missing expected images.
Failed openQA tests: 4/138 (x86_64), 23/24 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20180629.n.0):
ID: 253878 Test: x86_64 Server-dvd-iso base_update_cli
URL: https://openqa.fedoraproject.org/tests/253878
ID: 253915 Test: x86_64 KDE-
On 06/30/2018 10:11 AM, Lennart Poettering wrote:
> On Fr, 29.06.18 17:26, Kyle Marek (pspps...@gmail.com) wrote:
>
>> Kernel updates are different. You *have* to reboot in order to run the
>> new kernel (except for security updates applied with kpatch) and a
>> broken kernel has the potential to s
OLD: Fedora-Rawhide-20180629.n.0
NEW: Fedora-Rawhide-20180630.n.0
= SUMMARY =
Added images:8
Dropped images: 2
Added packages: 1
Dropped packages:1
Upgraded packages: 166
Downgraded packages: 0
Size of added packages: 103.00 KiB
Size of dropped packages
On samedi 30 juin 2018 13:25:50 CEST Andrea Musuruane wrote:
> Hi!
> I'm forwarding this request for help here since it seems there is no
> one available on Fedora games.
>
> The strange thing about this issue is that on F27 everything is fine (the
> spec file is the same).
>
> Thanks in adva
Le samedi 30 juin 2018 à 14:32 +0200, Hans de Goede a écrit :
Hi
> > 4. you check every single bit needed to use them works before
> > declaring a boot successful
>
> A boot is declared successful if a user logs in (or the
> user session starts if autologin is enabled) and the
> usersession last
Hello,
lots of times, I see name "copr", "Copr", or "COPR" used somewhere but it's
almost never used correctly for the given context. So I would like to make
it clear, what's the correct way to write it down to get the meaning right.
"Copr" or "COPR" = service providing space for community projec
Le samedi 30 juin 2018 à 14:22 +0200, Tomasz Torcz a écrit :
>
> BTW, kubernetes package is quite pathological. Installing it brings
> kubernetes-master, which contains following four binaries:
>
> -rwxr-xr-x. 3 root root 152M 04-26 11:34 /usr/bin/hyperkube
> -rwxr-xr--. 1 root kube 128M 04-2
Announcing the creation of a new nightly release validation test event
for Fedora 29 Rawhide 20180630.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On Fr, 29.06.18 17:26, Kyle Marek (pspps...@gmail.com) wrote:
> Kernel updates are different. You *have* to reboot in order to run the
> new kernel (except for security updates applied with kpatch) and a
> broken kernel has the potential to simply lock up without even launching
> /sbin/init, for e
Fantastic! Thanks Antonio!
On Sat, Jun 30, 2018 at 10:26 AM, Antonio Trande wrote:
> See
>
> $ cat /usr/lib/rpm/macros.d/macros.jpackage
>
> %_jnidir --> %{_prefix}/lib/java
>
> On 30/06/2018 15:15, Ricardo Martinelli Oliveira wrote:
>> Hello,
>>
>> I'm upgrading sbt and scala packages to 0.13.
See
$ cat /usr/lib/rpm/macros.d/macros.jpackage
%_jnidir --> %{_prefix}/lib/java
On 30/06/2018 15:15, Ricardo Martinelli Oliveira wrote:
> Hello,
>
> I'm upgrading sbt and scala packages to 0.13.13 and 2.11.11
> respectively. I am looking for a way to point to a jar file for
> jansi-native wi
Hello,
I'm upgrading sbt and scala packages to 0.13.13 and 2.11.11
respectively. I am looking for a way to point to a jar file for
jansi-native without hard-coding the path (/usr/lib/java).
Is there a macro available that points to that path? what is the best
option to avoid hard-code this specif
Hi,
On 29-06-18 17:46, Nicolas Mailhot wrote:
Le 2018-05-31 14:25, Hans de Goede a écrit :
Originally I was planning on doing the failed-boot detect only
for F30, but I agree it makes sense to have it for F29 and this
will also give us some field testing of this while we still have
a fallback
On Sat, Jun 30, 2018 at 12:46:28PM +0200, Nicolas Mailhot wrote:
> Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit :
> > FWIW, a fun read from the debian pkg-go list about packaging docker
> > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.ne
> > t/msg00032.htm
Hi!
I'm forwarding this request for help here since it seems there is no
one available on Fedora games.
The strange thing about this issue is that on F27 everything is fine (the
spec file is the same).
Thanks in advance,
Andrea
-- Forwarded message --
From: Andrea Musuruan
Le samedi 30 juin 2018 à 12:46 +0200, Nicolas Mailhot a écrit :
> Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit :
> > FWIW, a fun read from the debian pkg-go list about packaging docker
> > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.
> > ne
> > t/msg00032
Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit :
> FWIW, a fun read from the debian pkg-go list about packaging docker
> https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.ne
> t/msg00032.html
And so what? I hit this problem months ago (and I have the github
tick
Le jeudi 21 juin 2018 à 18:55 +0200, Mikolaj Izdebski a écrit :
>
> Allowing parallel installation of two distinct package sets, provided
> that they don't conflict in any way - how is that impossible? I get
> that it's not a goal for modularity to support this, but I don't see
> any technical re
24 matches
Mail list logo
