Anybody know what's going on with Centos 7.6-1810?
Some packages in EPEL depend on it, but it is apparently not yet available.
This discrepancy is breaking yum updates for me.
For example, xorgxrdp-0.2.8-3.el7 depends on xorg-x11-server-Xorg
1.20.1, which isn't yet available (rather, available on
Hi
On Sun, Nov 25, 2018 at 10:53 PM Tomasz Kłoczko
wrote:
>
> On Sun, 25 Nov 2018 at 11:35, Tomasz Kłoczko wrote:
> [..]
> > I’m talking about F30 recent change in which has been implemented switch to
> > dubs-broker.
> > Ps. If this change has been propagated to F29 (hopefully not) more things
On Sun, 25 Nov 2018 at 11:35, Tomasz Kłoczko wrote:
[..]
> I’m talking about F30 recent change in which has been implemented switch to
> dubs-broker.
> Ps. If this change has been propagated to F29 (hopefully not) more things
> will be screwed.
Seems I found what caused the issue.
I've been doi
Thanks a lot Alex
So, "old wiki" is still relevant...
I was searching in
https://docs.fedoraproject.org/en-US/packaging-guidelines/
On Sun, Nov 25, 2018 at 7:47 PM Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:
> Hi Alain,
>
> I believe these two documents should come in handy:
> http
Hi Alain,
I believe these two documents should come in handy:
https://fedoraproject.org/wiki/Package_maintenance_guide
https://fedoraproject.org/wiki/Package_update_HOWTO
(the second one is mostly about the update process)
Source packages are not part of the "usual" git transactions, they are
mod
Upstream releases a new version.
I changed the .spec file, generate a srpm file, then perform again
$ fedpgk import
This creates a tar.gz file in my git dir, and I did commit this file.
https://src.fedoraproject.org/rpms/pcb-rnd/blob/master/f/pcb-rnd-2.1.0.tar.gz
I think this is wrong, so:
1. C
Hi folks! I'm proposing we cancel the QA meeting tomorrow. We met the
last two weeks and I don't see anything urgent to discuss, so let's
take the time off.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
--
On Sun, Nov 25, 2018 at 4:54 PM Benjamin Kircher
wrote:
>
> What are dnf’s minimum memory requirements? It came as a surprise to me that
> a simple `dnf check-update` is getting OOM’ed by the kernel on a (ok, fairly
> small) 512MB VM.
>
>
> [root@node ~]# dnf check-update
> Killed
>
> [root@node
What are dnf’s minimum memory requirements? It came as a surprise to me that a
simple `dnf check-update` is getting OOM’ed by the kernel on a (ok, fairly
small) 512MB VM.
[root@node ~]# dnf check-update
Killed
[root@node ~]# free -h
totalusedfree shared buff
No missing expected images.
Failed openQA tests: 15/142 (x86_64), 4/24 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20181123.n.1):
ID: 311779 Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/311779
ID: 311780 Test: x86_
OLD: Fedora-Rawhide-20181123.n.1
NEW: Fedora-Rawhide-20181125.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 0
Dropped packages:0
Upgraded packages: 41
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size
On Sun, 25 Nov 2018 at 11:19, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sun, Nov 25, 2018 at 02:36:31AM +0100, Tomasz Kłoczko wrote:
> > After last dbus upgrade gdm found that is not able to start.
>
> What Fedora version? Ideally provide specific rpm versions.
> dbus-in-F29 != dbus-in-F30 now.
>
On Sat, Nov 17, 2018 at 07:17:44PM +1100, Philip Rhoades wrote:
> Leigh,
>
>
> On 2018-11-17 18:19, Leigh Scott wrote:
> >Try
> >
> >https://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems#Playback_problems.2C_crackling_or_skipping
>
>
> My problem is not crackling_or_skipping - it is m
On Sun, Nov 25, 2018 at 02:36:31AM +0100, Tomasz Kłoczko wrote:
> After last dbus upgrade gdm found that is not able to start.
What Fedora version? Ideally provide specific rpm versions.
dbus-in-F29 != dbus-in-F30 now.
Zbyszek
> NM basen network configuration as well is broker because it needs d
14 matches
Mail list logo
