Re: F28 Self Contained Change: Atomic, Cloud and Docker images for s390x

[Sinny Kumari]

On Wed, Jan 31, 2018 at 11:56 PM, Josh Boyer  wrote:
> On Tue, Jan 30, 2018 at 12:42 PM, Daniel Walsh  wrote:
>> On 01/30/2018 11:50 AM, Jan Kurik wrote:
>>>
>>> = Proposed Self Contained Change: Atomic, Cloud and Docker images for
>>> s390x =
>>>
>>> https://fedoraproject.org/wiki/Changes/Atomic_Cloud_and_Docker_images_for_s390x
>>>
>>> Change owner(s):
>>> * Sinny Kumari 
>>>
>>>
>>> This change is to bring s390x architecture closer to other Fedora
>>> architectures by adding widely used Fedora variants. This includes
>>> docker images, Atomic Host (iso, qcow2 and raw format) and regular
>>> Cloud Images (qcow2 and raw format).
>>>
>>>
>>> == Detailed Description ==
>>> We already ship Atomic, Cloud and Docker images on other 64-bit Fedora
>>> supported architectures- aarch64, x86_64 and ppc64le. With Fedora 27,
>>> s390x is part of primary koji build system. Currently, we only ship
>>> Server and Everything variants for s390x. So, our next steps should be
>>> to have missing Fedora variants on s390x architecture which users will
>>> find useful. This brings in shipping Atomic, Cloud and Docker images
>>> in Fedora for s390x as well.
>>>
>>>
>>> == Scope ==
>>> * Proposal owners:
>>> These are isolated changes which doesn't impact existing Fedora 28
>>> release plan on s390x. To have these changes ready to ship in Fedora
>>> 28, we mainly require s390x koji builders configured to run these
>>> composes, changes in pungi configuration [
>>> https://pagure.io/pungi-fedora/pull-request/496 ] to enable the
>>> additional compose and fixing s390x specific issues encountered when
>>> compose fails to run.
>>>
>>> * Other developers:
>>> Changes in Fedora infrastructure configs/scripts will be required to
>>> have s390x builders configured to run additional composes. Fedora
>>> Infrastructure issue [
>>> https://pagure.io/fedora-infrastructure/issue/6659 ] has been filed to
>>> keep track of required changes to be done.
>>>
>>> * Release engineering:
>>> #Releng 7286: https://pagure.io/releng/issue/7286
>>>
>>> * Policies and guidelines:
>>> N/A (not a System Wide Change)
>>>
>>> * Trademark approval:
>>> N/A (not needed for this Change)
>>
>>
>> You mean OCI Images...
>
> Mostly likely, yes.
>
> Relatedly, has there been a change request to move the default
> container runtime to cri-o or runc or rkt or anything other than
> docker in Fedora Atomic?  If so, that will be neat and I'm sorry I
> missed it.  If not, why not?

As per discussion outcome in atomic-wg ticket [1], Fedora 28 Atomic Host will
ship docker as default container runtime. Prior to this decision, a survey
happened about docker usage for Atomic Host [2] which shows that there are still
good number of people who want docker as default.

Answer to the question on whether there will another default container runtime
like cri-o [2] is still undecided. For now reason is having both cri-o and
docker will increase size of base Atomic Host.

[1] https://pagure.io/atomic-wg/issue/360
[2] 
https://docs.google.com/document/d/1aC8uthOMrTLiYK3l5muUVKDnOO7Rich2JxJ0sd4LJ6o/edit#heading=h.4kdxqyoia6mn
[3] https://pagure.io/atomic-wg/issue/407

> josh
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org



-- 
http://sinny.io/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

broken terminfo database in latest ncurses?

[Tomasz Kłoczko]

Hi,

Just applied all recent updates and seems after this now mc is not able
recognize correctly number of available colors on gnome-terminal and xterm,
and on gnome-terminal cursors are not working now.

$ rpm -q --changelog ncurses-base | head -10
* Tue Jan 30 2018 Miroslav Lichvar  6.1-2.20180129
- update to 6.1-20180129
- use macro for ldconfig scriptlets

* Mon Jan 29 2018 Miroslav Lichvar  6.1-1.20180127
- update to 6.1-20180127

* Thu Nov 30 2017 Miroslav Lichvar  6.0-15.20171125
- update to 6.0-20171125 (CVE-2017-16879)

can someone confirm this?

kloczek
-- 
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH *
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Tomasz Kłoczko]

On 1 February 2018 at 01:42, Peter Hutterer 
wrote:
[..]

> > So event4 it is in my case touch pad and event5  it is Logitech M185
> mouse.
> > In other words: those "libinput bug" log entries looks like are not
> related
> > to emitting those short bursts of repeating keystrokes.
>
> not directly, but they indicate where the issue is: key repeat is handled
> in
> the clients, not in libinput. With delays like this it's easy to see why
> you
> would get key repeat - if your key release event is delayed by 300ms or
> more
> the client will handle repeats before it gets the events.
>
> But the real cause of the issue is that you're getting crazy delays because
> gnome-shell is too busy with something else. The rest is fallout from that.
>

So that is quite possible explanation and cause of those delays probably is
in what I've already described.
Every few second in kernel messages I have sequence:

[74330.405990] [drm] PCIE gen 2 link speeds already enabled
[74330.417096] [drm] PCIE GART of 1024M enabled (table at
0x00162000).
[74330.417206] radeon :01:00.0: WB enabled
[74330.417212] radeon :01:00.0: fence driver on ring 0 use gpu addr
0x2c00 and cpu addr 0xd8c75981
[74330.417216] radeon :01:00.0: fence driver on ring 3 use gpu addr
0x2c0c and cpu addr 0x1142ed24
[74330.417965] radeon :01:00.0: fence driver on ring 5 use gpu addr
0x00072118 and cpu addr 0x095357f2
[74330.434413] [drm] ring test on 0 succeeded in 2 usecs
[74330.434428] [drm] ring test on 3 succeeded in 7 usecs
[74330.611793] [drm] ring test on 5 succeeded in 2 usecs
[74330.611809] [drm] UVD initialized successfully.
[74330.611949] [drm] ib test on ring 0 succeeded in 0 usecs
[74330.612118] [drm] ib test on ring 3 succeeded in 0 usecs
[74331.267267] [drm] ib test on ring 5 succeeded
[74340.515810] radeon :01:00.0: swiotlb buffer is full (sz: 2097152
bytes)
[74340.515819] swiotlb: coherent allocation failed for device :01:00.0
size=2097152
[74340.515827] CPU: 0 PID: 27342 Comm: kworker/0:1 Tainted: GW
  4.15.0-0.rc9.git4.1.fc28.x86_64 #1
[74340.515832] Hardware name: Sony Corporation VPCSB2M9E/VAIO, BIOS R2087H4
06/15/2012
[74340.515841] Workqueue: pm pm_runtime_work
[74340.515849] Call Trace:
[74340.515862]  dump_stack+0x85/0xbf
[74340.515871]  swiotlb_alloc_coherent+0xe0/0x150
[74340.515889]  ttm_dma_pool_get_pages+0x21b/0x620 [ttm]
[74340.515908]  ttm_dma_populate+0x24d/0x340 [ttm]
[74340.515923]  ttm_bo_move_memcpy+0x185/0x610 [ttm]
[74340.515933]  ? lock_acquire+0x9f/0x200
[74340.515940]  ? reservation_object_wait_timeout_rcu+0xb3/0x500
[74340.515987]  radeon_bo_move+0x1a7/0x220 [radeon]
[74340.516003]  ttm_bo_handle_move_mem+0x2a4/0x5d0 [ttm]
[74340.516021]  ttm_bo_evict+0x186/0x370 [ttm]
[74340.516046]  ttm_mem_evict_first+0x174/0x1d0 [ttm]
[74340.516060]  ttm_bo_force_list_clean+0x6d/0x130 [ttm]
[74340.516089]  radeon_suspend_kms+0x11e/0x3e0 [radeon]
[74340.516103]  ? vga_switcheroo_runtime_resume+0x60/0x60
[74340.516126]  radeon_pmops_runtime_suspend+0x54/0xc0 [radeon]
[74340.516135]  pci_pm_runtime_suspend+0x61/0x170
[74340.516144]  vga_switcheroo_runtime_suspend+0x24/0xa0
[74340.516151]  __rpm_callback+0xbc/0x1f0
[74340.516160]  ? vga_switcheroo_runtime_resume+0x60/0x60
[74340.516168]  rpm_callback+0x1f/0x70
[74340.516175]  ? vga_switcheroo_runtime_resume+0x60/0x60
[74340.516181]  rpm_suspend+0x12d/0x6e0
[74340.516195]  pm_runtime_work+0x73/0xb0
[74340.516204]  process_one_work+0x249/0x6b0
[74340.516219]  worker_thread+0x3a/0x390
[74340.516229]  ? process_one_work+0x6b0/0x6b0
[74340.516236]  kthread+0x121/0x140
[74340.516243]  ? kthread_create_worker_on_cpu+0x70/0x70
[74340.516253]  ret_from_fork+0x3a/0x50

during which whole desktop is frozen for fraction of the second. During
those freezes it is not possible even to move mouse cursor.
Do you have idea what it may be?

# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Seymour [Radeon HD 6400M/7400M Series] (rev ff)

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Peter Hutterer]

On Wed, Jan 31, 2018 at 10:18:14PM +, Tomasz Kłoczko wrote:
> On 31 January 2018 at 22:09, Tomasz Kłoczko 
> wrote:
> [..]
> 
> > Why I think that it may be related to libinput? Because in logs I see as
> > well another type of entries:
> >
> > #  journalctl -xe | grep libinput
> > Jan 31 21:55:18 domek org.gnome.Shell.desktop[2153]: libinput error:
> > libinput bug: timer event5 debounce: offset negative (-354ms)
> > Jan 31 21:55:18 domek org.gnome.Shell.desktop[2153]: libinput error:
> > libinput bug: timer event5 debounce short: offset negative (-368ms)
> > Jan 31 21:56:27 domek org.gnome.Shell.desktop[2153]: libinput error:
> > libinput bug: timer event5 debounce: offset negative (-1107ms)
> > Jan 31 21:56:27 domek org.gnome.Shell.desktop[2153]: libinput error:
> > libinput bug: timer event5 debounce short: offset negative (-1120ms)
> > Jan 31 22:05:12 domek org.gnome.Shell.desktop[2153]: libinput error:
> > libinput bug: timer event4 keyboard: offset negative (-331ms)
> > Jan 31 22:06:05 domek org.gnome.Shell.desktop[2153]: libinput error:
> > libinput bug: timer event4 keyboard: offset negative (-750ms)
> > Jan 31 22:06:05 domek org.gnome.Shell.desktop[2153]: libinput error:
> > libinput bug: timer event4 keyboard: offset negative (-413ms)

timer offset bugs almost always mean that libinput_dispatch() isn't called
quickly enough when its fd triggers. We rely on the compositor for that, so
you can blame gnome shell here.

Internally, libinput uses event timestamps and uses them for timers (e.g.
tap timer, debouncing, etc.). Let's assume an event happens, our timeout is
150ms but it takes 500ms after the event before calling libinput_dispatch(),
the timer offset is now 350ms in the past - that's what libinput warns about.

It's not a killer but it does mean that whatever libinput was trying to do
won't work correctly. In your case, the 'keyboard' timer is the one used in
disable-while-typing. So expect that not to work correctly.

Also: the keyboard timer is 500ms, and you have a neg. offset of 750ms. This
is a delay of 1250ms, that's crazy! Something's hogging gnome shell here and
it doesn't get to handle input.

> Correction:
> 
> # libinput list-devices | grep ^Device -A1
> Device:   Video Bus
> Kernel:   /dev/input/event7
> --
> Device:   Sony Vaio Jogdial
> Kernel:   /dev/input/event9
> --
> Device:   Sony Vaio Keys
> Kernel:   /dev/input/event8
> --
> Device:   Video Bus
> Kernel:   /dev/input/event6
> --
> Device:   Power Button
> Kernel:   /dev/input/event1
> --
> Device:   Lid Switch
> Kernel:   /dev/input/event0
> --
> Device:   USB 2.0 Camera: USB Camera
> Kernel:   /dev/input/event13
> --
> Device:   HDA Intel PCH Headphone
> Kernel:   /dev/input/event10
> --
> Device:   HDA Intel PCH HDMI/DP,pcm=3
> Kernel:   /dev/input/event11
> --
> Device:   HDA Intel PCH HDMI/DP,pcm=7
> Kernel:   /dev/input/event12
> --
> Device:   Logitech M185
> Kernel:   /dev/input/event5
> --
> Device:   CD002 CD002
> Kernel:   /dev/input/event3
> --
> Device:   AT Translated Set 2 keyboard
> Kernel:   /dev/input/event2
> --
> Device:   AlpsPS/2 ALPS GlidePoint
> Kernel:   /dev/input/event4
> 
> So event4 it is in my case touch pad and event5  it is Logitech M185 mouse.
> In other words: those "libinput bug" log entries looks like are not related
> to emitting those short bursts of repeating keystrokes.
 
not directly, but they indicate where the issue is: key repeat is handled in
the clients, not in libinput. With delays like this it's easy to see why you
would get key repeat - if your key release event is delayed by 300ms or more
the client will handle repeats before it gets the events.

But the real cause of the issue is that you're getting crazy delays because
gnome-shell is too busy with something else. The rest is fallout from that.

Cheers,
   Peter
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fwd: Re: Fedora27: NFS v4 terrible write performance, is async working

[Jeremy Linton]

On 01/31/2018 09:49 AM, J. Bruce Fields wrote:

On Tue, Jan 30, 2018 at 01:52:49PM -0600, Jeremy Linton wrote:

Have you tried this with a '-o nfsvers=3' during mount? Did that help?

I noticed a large decrease in my kernel build times across NFS/lan a while
back after a machine/kernel/10g upgrade. After playing with mount/export
options filesystem tuning/etc, I got to this point of timing a bunch of
these operations vs the older machine, at which point I discovered that
simply backing down to NFSv3 solved the problem.

AKA a nfsv3 server on a 10 year old 4 disk xfs RAID5 on 1Gb ethernet, was
slower than a modern machine with a 8 disk xfs RAID5 on 10Gb on nfsv4. The
effect was enough to change a kernel build from ~45 minutes down to less
than 5.


Did you mean "faster than"?


Yes, sorry about that.



Definitely worth trying, though I wouldn't expect it to make that big a
difference in the untarring-a-kernel-tree case--I think the only RPC
avoided in the v3 case would be the CLOSE, and it should be one of the
faster ones.

In the kernel compile case there's probably also a lot of re-opening and
re-reading files too?  NFSv4 is chattier there too.  Read delegations
should help compensate, but we need to improve the heuristics that
decide when they're given out.


The main kernel include files get repeatedly hammered, despite them in 
theory being in cache, IIRC. So yes, if the concurrent (re)open path is 
even slightly slower its going to hurt a lot.




All that aside I can't think what would explain that big a difference
(45 minutes vs. 5).  It might be interesting to figure out what
happened.


I had already spent more than my time allotted looking in the wrong 
direction at the filesystem/RAID (did turn off intellipark though) by 
the time I discovered the nfsv3/v4 perf delta. Its been sitting way down 
on the "things to look into" list for a long time now. I'm still using 
it as a NFS server so at some point I can take another look if the 
problem persists.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1540772] New: perl-Lingua-EN-Inflect-Phrase-0.19 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1540772

Bug ID: 1540772
   Summary: perl-Lingua-EN-Inflect-Phrase-0.19 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Lingua-EN-Inflect-Phrase
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org



Latest upstream release: 0.19
Current version/release in rawhide: 0.18-8.fc27
URL: http://search.cpan.org/dist/Lingua-EN-Inflect-Phrase

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/7159/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1392475] perl-Alien-ROOT not available on ppc64 because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392475



--- Comment #5 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-10.fc27 has been pushed to the Fedora 27 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-610360e2c0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1392479] perl-Alien-ROOT not available on ppc64le because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392479



--- Comment #5 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-10.fc27 has been pushed to the Fedora 27 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-610360e2c0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Tomasz Kłoczko]

On 31 January 2018 at 22:09, Tomasz Kłoczko 
wrote:
[..]

> Why I think that it may be related to libinput? Because in logs I see as
> well another type of entries:
>
> #  journalctl -xe | grep libinput
> Jan 31 21:55:18 domek org.gnome.Shell.desktop[2153]: libinput error:
> libinput bug: timer event5 debounce: offset negative (-354ms)
> Jan 31 21:55:18 domek org.gnome.Shell.desktop[2153]: libinput error:
> libinput bug: timer event5 debounce short: offset negative (-368ms)
> Jan 31 21:56:27 domek org.gnome.Shell.desktop[2153]: libinput error:
> libinput bug: timer event5 debounce: offset negative (-1107ms)
> Jan 31 21:56:27 domek org.gnome.Shell.desktop[2153]: libinput error:
> libinput bug: timer event5 debounce short: offset negative (-1120ms)
> Jan 31 22:05:12 domek org.gnome.Shell.desktop[2153]: libinput error:
> libinput bug: timer event4 keyboard: offset negative (-331ms)
> Jan 31 22:06:05 domek org.gnome.Shell.desktop[2153]: libinput error:
> libinput bug: timer event4 keyboard: offset negative (-750ms)
> Jan 31 22:06:05 domek org.gnome.Shell.desktop[2153]: libinput error:
> libinput bug: timer event4 keyboard: offset negative (-413ms)
>

Correction:

# libinput list-devices | grep ^Device -A1
Device:   Video Bus
Kernel:   /dev/input/event7
--
Device:   Sony Vaio Jogdial
Kernel:   /dev/input/event9
--
Device:   Sony Vaio Keys
Kernel:   /dev/input/event8
--
Device:   Video Bus
Kernel:   /dev/input/event6
--
Device:   Power Button
Kernel:   /dev/input/event1
--
Device:   Lid Switch
Kernel:   /dev/input/event0
--
Device:   USB 2.0 Camera: USB Camera
Kernel:   /dev/input/event13
--
Device:   HDA Intel PCH Headphone
Kernel:   /dev/input/event10
--
Device:   HDA Intel PCH HDMI/DP,pcm=3
Kernel:   /dev/input/event11
--
Device:   HDA Intel PCH HDMI/DP,pcm=7
Kernel:   /dev/input/event12
--
Device:   Logitech M185
Kernel:   /dev/input/event5
--
Device:   CD002 CD002
Kernel:   /dev/input/event3
--
Device:   AT Translated Set 2 keyboard
Kernel:   /dev/input/event2
--
Device:   AlpsPS/2 ALPS GlidePoint
Kernel:   /dev/input/event4

So event4 it is in my case touch pad and event5  it is Logitech M185 mouse.
In other words: those "libinput bug" log entries looks like are not related
to emitting those short bursts of repeating keystrokes.

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Tomasz Kłoczko]

On 31 January 2018 at 21:00, Tomasz Torcz ️  wrote:

> On Wed, Jan 31, 2018 at 01:37:15PM +, Tomasz Kłoczko wrote:
> > After update today to latest rawhide and reboot I'v decided to change GUI
> > from X11 to Wyland.
> > In logs I see similar entries like above.
> >
> > Additionally what I found so far after few hours:
> >
> > 1) sometimes pressing single key is causing to generate many keystrokes.
> > Very annoying ..
> >   I had such effect at least 10 times in last hour. Looks like some
> > libinput effect.
>
>   This one is a peculiarity of GNOME Terminal; I've reported it over a
> decade ago: https://bugzilla.gnome.org/show_bug.cgi?id=354329
>   I don't think it's related to Wayland or libinput.
>

I see this mainly in chrome and polari.
In less than 24h of using Weyland so far I've not been able to observe this
with gnome-terminal.
Looks like this effect is not limited to only one application.
As I wrote I don't see this repeating keystrokes effect under X11.

Why I think that it may be related to libinput? Because in logs I see as
well another type of entries:

#  journalctl -xe | grep libinput
Jan 31 21:55:18 domek org.gnome.Shell.desktop[2153]: libinput error:
libinput bug: timer event5 debounce: offset negative (-354ms)
Jan 31 21:55:18 domek org.gnome.Shell.desktop[2153]: libinput error:
libinput bug: timer event5 debounce short: offset negative (-368ms)
Jan 31 21:56:27 domek org.gnome.Shell.desktop[2153]: libinput error:
libinput bug: timer event5 debounce: offset negative (-1107ms)
Jan 31 21:56:27 domek org.gnome.Shell.desktop[2153]: libinput error:
libinput bug: timer event5 debounce short: offset negative (-1120ms)
Jan 31 22:05:12 domek org.gnome.Shell.desktop[2153]: libinput error:
libinput bug: timer event4 keyboard: offset negative (-331ms)
Jan 31 22:06:05 domek org.gnome.Shell.desktop[2153]: libinput error:
libinput bug: timer event4 keyboard: offset negative (-750ms)
Jan 31 22:06:05 domek org.gnome.Shell.desktop[2153]: libinput error:
libinput bug: timer event4 keyboard: offset negative (-413ms)


kloczek
-- 
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH *



>
> --
> Tomasz Torcz   72->|
>  80->|
> xmpp: zdzich...@chrome.pl  72->|
>  80->|
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1536767] perl-CPAN-Perl-Releases-3.46 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1536767



--- Comment #6 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.46-1.fc27 has been pushed to the Fedora 27 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1536701] perl-MogileFS-Server-2.73 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1536701



--- Comment #3 from Fedora Update System  ---
perl-MogileFS-Server-2.73-1.fc27 has been pushed to the Fedora 27 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1536773] perl-Module-CoreList-5.20180120 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1536773



--- Comment #6 from Fedora Update System  ---
perl-Module-CoreList-5.20180120-1.fc27 has been pushed to the Fedora 27 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1535738] perl-Net-Twitter-4.01043 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1535738

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version||perl-Net-Twitter-4.01043-1.
   ||fc27
 Resolution|--- |ERRATA
Last Closed||2018-01-31 16:57:10



--- Comment #5 from Fedora Update System  ---
perl-Net-Twitter-4.01043-1.fc27 has been pushed to the Fedora 27 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Tomasz Torcz ️]

On Wed, Jan 31, 2018 at 01:37:15PM +, Tomasz Kłoczko wrote:
> After update today to latest rawhide and reboot I'v decided to change GUI
> from X11 to Wyland.
> In logs I see similar entries like above.
> 
> Additionally what I found so far after few hours:
> 
> 1) sometimes pressing single key is causing to generate many keystrokes.
> Very annoying ..
>   I had such effect at least 10 times in last hour. Looks like some
> libinput effect.

  This one is a peculiarity of GNOME Terminal; I've reported it over a
decade ago: https://bugzilla.gnome.org/show_bug.cgi?id=354329
  I don't think it's related to Wayland or libinput.

-- 
Tomasz Torcz   72->|   80->|
xmpp: zdzich...@chrome.pl  72->|   80->|
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Re: Wyland is a disaster

[nicolas . mailhot]

> 1) sometimes pressing single key is causing to generate many keystrokes.
> Very annoying ..

That can get more than annoying when it combines with the inverse effect: 
eating keystrokes and refusing to output them (sometimes regurgitating parts of 
what it ate as few seconds later in the middle of something else you're typing)

Though that seems to happen mostly when I use a wireless logitech keyboard, not 
with the built-in laptop keyboard

Visibly input is not baked yet in Wayland

Regards,

-- 
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 1059  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087   
dokuwiki-0-0.24.20140929c.el7
 822  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f   
mcollective-2.8.4-1.el7
 404  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-04bc9dd81d   
libbsd-0.8.3-1.el7
 301  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-d241156dfe   
mod_cluster-1.3.3-10.el7
 133  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e27758bd23   
libmspack-0.6-0.1.alpha.el7
  71  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e64eeb6ece   
nagios-4.3.4-5.el7
  34  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-8d57a2487b   
monit-5.25.1-1.el7
  20  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-73ee944e65   
rootsh-1.5.3-17.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-73feedd767   
wordpress-4.9.2-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ce6223e559   
GraphicsMagick-1.3.28-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-9eb18da891   
moodle-3.1.10-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-c0d5d190b0   
transmission-2.92-12.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-24ac4ff7df   
knot-resolver-1.5.3-1.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-dd0bc449d7   
konversation-1.5.1-4.el7
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-fb68becde7   
w3m-0.5.3-36.git20180125.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

beanstalkd-1.10-2.el7
cmrt-1.0.6-4.el7
dspam-3.10.2-12.el7
fedpkg-1.31-1.el7
kabi-dw-0-0.5.20180130git545535a.el7
libva-1.8.3-0.1.el7
libva-intel-hybrid-driver-1.0.2-4.el7.1
libva-utils-1.8.3-4.el7
libva-vdpau-driver-0.7.4-19.el7
libvdpau-va-gl-0.4.2-6.el7
spectre-meltdown-checker-0.33-1.el7
transtats-cli-0.1.1-4.el7

Details about builds:



 beanstalkd-1.10-2.el7 (FEDORA-EPEL-2018-e65f5edd12)
 A simple, fast work-queue service

Update Information:

Removed systemd-units Requires and BuildRequires




 cmrt-1.0.6-4.el7 (FEDORA-EPEL-2018-2363152420)
 C for Media Runtime

Update Information:

Rebase libva to 1.8-branch This prepare the libva introduction from epel to rhel
(scheduled for 7.5)  Please verify to fetch packages from rpmfusion testing
(specially libva-intel-backend as needed). ffmpeg, vlc and xine have been
rebuilt along this new version.




 dspam-3.10.2-12.el7 (FEDORA-EPEL-2018-e65f5edd12)
 A library and Mail Delivery Agent for Bayesian SPAM filtering

Update Information:

Removed systemd-units Requires and BuildRequires




 fedpkg-1.31-1.el7 (FEDORA-EPEL-2018-214099fae8)
 Fedora utility for working with dist-git

Update Information:

- Include missing conf file in test (cqi) - Add more document to request-repo
and request-branch (cqi) - Stop allowing EPEL branches on official EL packages
(mprahl) - Port fedrepo-req and fedrepo-req-branch to fedpkg (mprahl) - Fix test
for unsupported Bodhi version (lsedlar) - Work with Bodhi 3 - rhbz#1507410
(lsedlar) - Allow any parameters in construct_build_url (cqi) - Fix the
anongiturl (patrick)

References:

  [ 1 ] Bug #1507410 - fedpkg update fails with: "This system has bodhi v3, 
which is unsupported"
https://bugzilla.redhat.com/show_bug.cgi?id=1507410




 kabi-dw-0-0.5.20180130git545535a.el7 (FEDORA-EPEL-2018-ce3d54fb66)
 Detect changes in the ABI between kernel builds

Update Information:

Update to upstream 545535ab2d5ea093074f5df5723901756d22f298

[Bug 1534083] perl-Socket-2.027 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1534083

Fedora Update System  changed:

   What|Removed |Added

 Status|CLOSED  |ON_QA
 Resolution|ERRATA  |---
   Keywords||Reopened



--- Comment #6 from Fedora Update System  ---
perl-Socket-2.027-1.fc26 has been pushed to the Fedora 26 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-fb7da310cb

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1533867] perl-Socket-2.026 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1533867

Fedora Update System  changed:

   What|Removed |Added

 Status|CLOSED  |ON_QA
 Resolution|ERRATA  |---
   Keywords||Reopened



--- Comment #6 from Fedora Update System  ---
perl-Socket-2.027-1.fc26 has been pushed to the Fedora 26 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-fb7da310cb

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1392479] perl-Alien-ROOT not available on ppc64le because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392479

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-7.fc26 has been pushed to the Fedora 26 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-cf41988c7d

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1392475] perl-Alien-ROOT not available on ppc64 because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392475

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-7.fc26 has been pushed to the Fedora 26 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-cf41988c7d

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: Self-Introduction Christian Glombek (lorbus) / NEEDSPONSOR / NEEDREVIEWs / Let's Meet @ DevConf or FOSDEM!

[Jeff Ligon]

Hello Chris!
It was nice to meet you at DevConf!
Welcome!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Atomic, Cloud and Docker images for s390x

[Josh Boyer]

On Tue, Jan 30, 2018 at 12:42 PM, Daniel Walsh  wrote:
> On 01/30/2018 11:50 AM, Jan Kurik wrote:
>>
>> = Proposed Self Contained Change: Atomic, Cloud and Docker images for
>> s390x =
>>
>> https://fedoraproject.org/wiki/Changes/Atomic_Cloud_and_Docker_images_for_s390x
>>
>> Change owner(s):
>> * Sinny Kumari 
>>
>>
>> This change is to bring s390x architecture closer to other Fedora
>> architectures by adding widely used Fedora variants. This includes
>> docker images, Atomic Host (iso, qcow2 and raw format) and regular
>> Cloud Images (qcow2 and raw format).
>>
>>
>> == Detailed Description ==
>> We already ship Atomic, Cloud and Docker images on other 64-bit Fedora
>> supported architectures- aarch64, x86_64 and ppc64le. With Fedora 27,
>> s390x is part of primary koji build system. Currently, we only ship
>> Server and Everything variants for s390x. So, our next steps should be
>> to have missing Fedora variants on s390x architecture which users will
>> find useful. This brings in shipping Atomic, Cloud and Docker images
>> in Fedora for s390x as well.
>>
>>
>> == Scope ==
>> * Proposal owners:
>> These are isolated changes which doesn't impact existing Fedora 28
>> release plan on s390x. To have these changes ready to ship in Fedora
>> 28, we mainly require s390x koji builders configured to run these
>> composes, changes in pungi configuration [
>> https://pagure.io/pungi-fedora/pull-request/496 ] to enable the
>> additional compose and fixing s390x specific issues encountered when
>> compose fails to run.
>>
>> * Other developers:
>> Changes in Fedora infrastructure configs/scripts will be required to
>> have s390x builders configured to run additional composes. Fedora
>> Infrastructure issue [
>> https://pagure.io/fedora-infrastructure/issue/6659 ] has been filed to
>> keep track of required changes to be done.
>>
>> * Release engineering:
>> #Releng 7286: https://pagure.io/releng/issue/7286
>>
>> * Policies and guidelines:
>> N/A (not a System Wide Change)
>>
>> * Trademark approval:
>> N/A (not needed for this Change)
>
>
> You mean OCI Images...

Mostly likely, yes.

Relatedly, has there been a change request to move the default
container runtime to cri-o or runc or rkt or anything other than
docker in Fedora Atomic?  If so, that will be neat and I'm sorry I
missed it.  If not, why not?

josh
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fedora rawhide compose report: changes

[Kevin Fenzi]

On 01/28/2018 05:31 AM, Adam Williamson wrote:
> On Wed, 2018-01-24 at 20:22 +, Fedora Rawhide Report wrote:
>> OLD: Fedora-Rawhide-20180117.n.1
>> NEW: Fedora-Rawhide-20180123.n.1
> 
> We've had a couple of these odd duplicate mails with the compose ID
> missing from the subject lately. I have to confess I do not know what's
> causing them to happen at all; I just can't see how it could be
> happening, or find out what compose script exactly is doing it. Going
> by datagrepper logs, these mails just don't seem to link up
> with...anything. It's kinda very strange.

I think these might be happening when we have a rawhide compose running,
another one starts then some bits hit OOM and are killed. One of the
composes finishes mostly normally, but the other one finishes... weirdly.

We perhaps should look at wrapping this so we only run one compose at a
time?

kevin





signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1536767] perl-CPAN-Perl-Releases-3.46 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1536767



--- Comment #5 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.46-1.fc26 has been pushed to the Fedora 26 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1536773] perl-Module-CoreList-5.20180120 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1536773



--- Comment #5 from Fedora Update System  ---
perl-Module-CoreList-5.20180120-1.fc26 has been pushed to the Fedora 26 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: Missing step in orphaning package process? (Re: kernel component on bugzilla and call for "old bugs hunting season" to open)

[Kevin Fenzi]

On 01/28/2018 03:12 PM, Tomasz Kłoczko wrote:

> It is only one obstacle to make it happen.
> As long as package is orphaned no longer it has maintainer (human
> maintainer).
> 
> Go to https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora -> enter as
> component name gdhcpd and you will suddenly find that you are able to open
> the ticket for Fedora 26, 27 and rawhide (sic!)
> Go to https://src.fedoraproject.org/rpms/gdhcpd and look on right side
> where are branches names and you will find that latest Fedora version for
> which this package has been released was  Fedora 11 (no EPEL)
> As admin of this package is listed "orphan (orphan)
> - main admin"
> How this dummy packages is maintaining still assigned to this package
> Bugzilla tickets?
> 
> Is that all still correct?

Yes. The idea is that a orphaned package could be taken over again by
someone and they would want to know the existing bugs already filed on it.

It might be worth closing retired components to bugs, but they too could
be revived and readded.

kevin



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [Fedora-packaging] Re: Proposed Fedora packaging guideline: More Go packaging

[Owen Taylor]

Hi Nicolas,

Is there a guide for Fedora packagers about how to handle unbundling for
golang packages? The draft guidelines don't seem to go into any details.
I've looked at packaging a few golang packages unbundled, and have
immediately run into:

 A) lots of unpackaged dependencies
 B) dependencies that are packaged in Fedora with different, often much
older versions

A) is a pretty known quantity for any type of package, but I found B) more
intimidating. It seems like to package the new package, I have to get the
maintainer of the library to upgrade the version, and someone needs to
rebuild everything that depends on the rebuilt library and test that the
rebuilt packages work.

Some tutorial showing a practical example of packaging a golang package for
the first time I think would be very helpful.

Owen


On Wed, Jan 31, 2018 at 5:30 AM,  wrote:

> >De: "Neal Gompa"
>
> > The only thing I see that might be missing is autogenerating
> > bundled(golang()) Provides when a vendor tree exists (with the
> > appropriate automatic filters on Requires).
>
> I had though a little about doing it but first, as many Go elements,
> vendoring relies on conventions not standards. The nasty thing about
> conventions is that they are not applied 100% the same way by everyone,
> making automation a PITA. And second interactions with autodeps can be
> nasty: you can filter out provides, but do you filter out requires? What
> about all the junk code many projects ship as testing and examples and
> which is vendored with the rest?
>
> I don't say it can't be done, or that it would be difficult to do once the
> rest is merged, but I'll live it to someone that absolutely want to ship a
> Go package with vendored parts.
>
> Right now we sidestep the issue in our packages by rm -fr ing anything
> that looks like vendored code in %prep. Unbundling takes time but it has a
> positive cumulative effect: the more you unbundle the less you need to
> worry about in other packages with the same requirements. And unbundling
> reveals code/legal problems that it would take about as much work to solve
> by auditing the vendored code manually.
>
> Regards,
>
> --
> Nicolas mAilhot
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Howard Howell]

On Wed, 2018-01-31 at 14:14 +0100, Olivier Fourdan wrote:
> Hi
> 
> On Wed, Jan 31, 2018 at 1:58 PM, Olivier Fourdan  > wrote:
> > Jan 31 01:14:08 school gnome-session[1715]: gnome-session-
> > binary[1715]: WARNING: App 'org.gnome.Shell.desktop' exited with 
> > > Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window
> > > manager error: Could not find cursor. Perhaps set XCURSOR_PATH
> > 
> > Interesting, that could be the problem! gnome-shell is both a
> > Wayland compositor (thus the display server) and an X11 window
> > manager.
> > 
> 
> Are you using a custom cursor theme or the default “Adwaita” cursor
> theme? 
>  
> > I think we should keep those discussions, including these important
> > bits, in the issue you filed upstream (https://gitlabgnome.org/GNOM
> > E/gnome-shell/issues/9) and not in a downstream mailing list :)
> > 
> 
> And... I got confused by multiple issues being reported in the same
> mail thread, that issue was filed by Przemek, so probably different
> from yours...
> 
> Cheers,
> Olivier
> 
OK!  I did change the cursor theme.  According to gnome-tweak-tool, it
is Gamma.Gold.  I have some vision problems and this looked good to me.

Regards,
Les H___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Howard Howell]

On Wed, 2018-01-31 at 13:58 +0100, Olivier Fourdan wrote:
> Hi,
> 
> What you logs tells is:
> 
> On Wed, Jan 31, 2018 at 10:37 AM, Howard Howell  > wrote:
> > Jan 31 01:14:08 school evolution-alarm[2297]: Error reading events
> > from display: Broken pipeJan 31 01:14:08 school gnome-
> > software[2301]: Error reading events from display: Broken pipe
> 
> Wayland native applications exiting with broken pipe, means the
> Wayland compositor (gnome-shell is dead)
>  
> > Jan 31 01:14:08 school gnome-session-binary[1715]: WARNING: App
> > 'org.gnome.Shell.desktop' exited with code 1
> 
> gnome-session tells us that gnome-shell is gone
>  
> > Jan 31 01:14:08 school gnome-session[1715]: gnome-session-
> > binary[1715]: WARNING: App 'org.gnome.Shell.desktop' exited with 
> > Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window
> > manager error: Could not find cursor. Perhaps set XCURSOR_PATH
> 
> Interesting, that could be the problem! gnome-shell is both a Wayland
> compositor (thus the display server) and an X11 window manager.
>  
> > Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Fatal server
> > error:
> > Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE) failed
> > to read Wayland events: Broken pipe
> > Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE)
> 
> Then Xwayland exits with “broken pipe”, like the other Wayland
> clients, because the Wayland compositor is, well ,dead.
>  
> > Jan 31 01:14:08 school gnome-session-binary[1715]: Unrecoverable
> > failure in required component org.gnome.Shell.desktop
> 
> gnome-session says something goes really wrong...
>  
> > Jan 31 01:14:08 school
> > org.gnome.SettingsDaemon.MediaKeys.desktop[2048]:
> > xcb_connection_has_error() returned true
> > Jan 31 01:14:08 school gsd-housekeepin[2045]: gsd-housekeeping:
> > Fatal IO error 11 (Resource temporarily unavailable) on X s
> > Jan 31 01:14:08 school gsd-print-notif[2013]: gsd-print-
> > notifications: Fatal IO error 11 (Resource temporarily unavailable)
> > Jan 31 01:14:08 school at-spi-bus-launcher[1825]: XIO:  fatal IO
> > error 11 (Resource temporarily unavailable) on X server ":
> >  ESCOC
> 
> And now, the X11 clients (hence depending on the X server, thus
> Xwayland) all quit as well, because the X server (Xwayland) is dead,
> because the Wayland compositor is dead...
>  
> > This doesn't tell me anything, but I'll bet some of you systems
> > guys can see through it to see the root cause, or at least a good
> > trail to follow.
> 
> I think we should keep those discussions, including these important
> bits, in the issue you filed upstream (https://gitlab.gnome.org/GNOME
> /gnome-shell/issues/9) and not in a downstream mailing list :)
> 
> Cheers,
> Olivier
> 
> 
> 
Do you want me to repost at that address?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: Adding devtoolset to EPEL

[Stephen John Smoogen]

On 31 January 2018 at 09:57, Ken Dreyer  wrote:

> On Sat, Jan 27, 2018 at 4:45 PM, Todd Zullinger  wrote:
> > Stephen John Smoogen wrote:
> >> I thought aarch64 was also supported for this.
> >
> > It looks like the devtoolset bits are still in the sclo
> > testing repositories for aarch64¹.  We could potentially
> > enable those in the mock configs if they're ready for more
> > testing.  Or we can wait for them to reach stable.
>
> Yeah, I wish this was more widely documented, but CentOS' DTS 7 is now
> built for ppc64le and aarch64.
>
>
So we have a problem with what is the canonical place for SCL's. I was
going from http://mirror.centos.org/centos/7/sclo/ which just says x86_64.

There are parts built in CBS but it isn't clear that these are any more
official than a Fedora COPR... I will let someone with releng experience
say whether that is ok or not.



> https://bugs.centos.org/view.php?id=14078
>
> - Ken
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: Fwd: Re: Fedora27: NFS v4 terrible write performance, is async working

[J. Bruce Fields]

On Tue, Jan 30, 2018 at 01:52:49PM -0600, Jeremy Linton wrote:
> Have you tried this with a '-o nfsvers=3' during mount? Did that help?
> 
> I noticed a large decrease in my kernel build times across NFS/lan a while
> back after a machine/kernel/10g upgrade. After playing with mount/export
> options filesystem tuning/etc, I got to this point of timing a bunch of
> these operations vs the older machine, at which point I discovered that
> simply backing down to NFSv3 solved the problem.
> 
> AKA a nfsv3 server on a 10 year old 4 disk xfs RAID5 on 1Gb ethernet, was
> slower than a modern machine with a 8 disk xfs RAID5 on 10Gb on nfsv4. The
> effect was enough to change a kernel build from ~45 minutes down to less
> than 5.

Did you mean "faster than"?

Definitely worth trying, though I wouldn't expect it to make that big a
difference in the untarring-a-kernel-tree case--I think the only RPC
avoided in the v3 case would be the CLOSE, and it should be one of the
faster ones.

In the kernel compile case there's probably also a lot of re-opening and
re-reading files too?  NFSv4 is chattier there too.  Read delegations
should help compensate, but we need to improve the heuristics that
decide when they're given out.

All that aside I can't think what would explain that big a difference
(45 minutes vs. 5).  It might be interesting to figure out what
happened.

--b.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Heads up: automatic shebang munging in rawhide

[Jason L Tibbitts III]

With redhat-rpm-config-91-1.fc28 which is currently in rawhide comes
automatic munging of the "#!" (shebang) line in executable scripts, as
well as several additional checks.  The following changes will be
applied the shebang line of executables:

1) "#!/usr/bin/env foo" will be replaced with "#!/usr/bin/foo".
2) "#!/usr/bin/python" will be replaced with "#!/usr/bin/python2".

Both might happen, so /usr/bin/env python will get fixed properly.  The
second will generate a warning in the build log, and may become an error
at some point.

Since use of env has been banned in Fedora for a while, this frees
packagers from needing to do extra work to fix those up.  And
eliminating all shebangs which reference the unversioned python
executable will pave the way for the python team to do more work on
moving to python3.

The script will also make one other change: an executable script with no
shebang will have its executable permission automatically removed.

Finally, the script will error (causing a build failure) if an
executable script is encountered which uses a shebang line that does not
use an absolute path to an executable.

Note that, like all of the various brp-* executables which many
packagers have probably never had to worry about, this runs near the end
of the package build process so if you need to fix something, you can do
that in whichever of %prep, %build or %install works best for your spec.

If this breaks your package, you should of course fix your package but
because nothing is foolproof you can disable it completely by adding the
following to your spec:

%undefine __brp_mangle_shebangs

This specific change will only require brief mention in the guidelines,
but I will draft an additional section which covers all of these brp-*
scripts since rawhide also now has a uniform means of disabling them.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Fedora Rawhide-20180131.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Workstation live i386
Kde live i386

Failed openQA tests: 12/129 (x86_64), 3/22 (i386), 1/2 (arm)

New failures (same test did not fail in Rawhide-20180130.n.0):

ID: 189692  Test: x86_64 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/189692
ID: 189695  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/189695

Old failures (same test failed in Rawhide-20180130.n.0):

ID: 189665  Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/189665
ID: 189697  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/189697
ID: 189698  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/189698
ID: 189699  Test: x86_64 KDE-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/189699
ID: 189700  Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/189700
ID: 189710  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/189710
ID: 189712  Test: x86_64 Atomic-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/189712
ID: 189713  Test: x86_64 Atomic-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/189713
ID: 189733  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/189733
ID: 189739  Test: x86_64 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/189739
ID: 189766  Test: x86_64 universal install_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/189766
ID: 189783  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/189783
ID: 189788  Test: i386 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/189788
ID: 189794  Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/189794

Soft failed openQA tests: 23/129 (x86_64), 3/22 (i386)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test did not soft fail in Rawhide-20180130.n.0):

ID: 189680  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/189680

Old soft failures (same test soft failed in Rawhide-20180130.n.0):

ID: 189650  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/189650
ID: 189651  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/189651
ID: 189656  Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/189656
ID: 189657  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/189657
ID: 189673  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/189673
ID: 189674  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/189674
ID: 189678  Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/189678
ID: 189681  Test: x86_64 Workstation-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/189681
ID: 189691  Test: x86_64 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/189691
ID: 189694  Test: x86_64 Workstation-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/189694
ID: 189721  Test: x86_64 universal upgrade_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/189721
ID: 189722  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/189722
ID: 189729  Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/189729
ID: 189734  Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/189734
ID: 189736  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/189736
ID: 189745  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/189745
ID: 189746  Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/189746
ID: 189748  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/189748
ID: 189750  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/189750
ID: 189758  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/189758
ID: 189776  Test: x86_64 universal upgrade_2_server_64bit
URL: https://openqa.fedoraproject.org/tests/189776
ID: 189778  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: 

Re: [HEADS UP] Removal of systemd-units

[Pavel Zhukov]

Jason L Tibbitts III  writes:

> landgraf   radvd
Done

-- 
Pavel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1540220] perl-Gearman-Client-Async-0.94-28.fc28 FTBFS: Timeout, test fails at t/allinone.t line 62.

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1540220

Petr Pisar  changed:

   What|Removed |Added

Version|rawhide |27



--- Comment #1 from Petr Pisar  ---
This is caused by upgrading perl-Gearman from 2.004.010-1.fc27 to
2.004.011-1.fc27.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Igor Gnatenko]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2018-01-31 at 14:53 +0100, Kamil Dudka wrote:
> On Wednesday, January 31, 2018 2:00:08 PM CET Florian Weimer wrote:
> > On 01/31/2018 01:54 PM, Kamil Dudka wrote:
> > 
> > > See that libcurl.so.4 now points to libcurl.so.4.5.0.minimal by mistake.
> > > 
> > > What is the recommended way to make libcurl{-minimal} build properly
> > > again?
> > 
> > I think in this situation, you need to disable this feature using:
> > 
> > %undefine __brp_ldconfig
> 
> Thank both of you for the suggestion!  It has indeed resolved the problem.
> 
> > Depending on whether you can include the appropriate symbolic links in 
> > the packages themselves,
> 
> Those symlinks are created by libtool, so I believe they are appropriate.
> 
> > you can or cannot remove the explicit ldconfig calls.
> 
> %undefine __brp_ldconfig removes the build-time ldconfig calls as I
> understand 
> it.  Are you saying that I can remove the following install-time ldconfig 
> calls, too?

If you don't simply merge master branch to others, then yes. Otherwise, you
should consider using macro we've created.

> %post -n libcurl -p /sbin/ldconfig
> 
> %postun -n libcurl -p /sbin/ldconfig
> 
> %post -n libcurl-minimal -p /sbin/ldconfig
> 
> %postun -n libcurl-minimal -p /sbin/ldconfig

%ldconfig_scriptlets -n libcurl
%ldconfig_scriptlets -n libcurl-minimal
- -- 
- -Igor Gnatenko
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpxyuQACgkQaVcUvRu8
X0yNURAAvoM8dUhwc4godVoc7O5y7t41JUijeDkhBLzSQSouUwAIefeaNWqO2Wr4
fy4TBY7A4piyKlwXdGsmjh7GGpwl3l623zoaqaugL/8hs8212JVelFQs7WhE6d2r
s6sMsy5Y9spue8FpT+rQ8Tn+Qaqyeo9ZCHfo5xUrvSj/YeEyWTssZa7XWjPNHb5h
Loy4n8kivD2tq+ycAIx+3w6+U1DsyRvhYUmQy/DwfegLy5TSuybf2ott42mZLy5k
WkEHZZ/gJnIMuW0Ra+E2unN7zpeKnC6Eg+ss0mhBb33C0WXLtZvWCHLxTrliheuy
Bn5+aGpf01zCev2r9/iK91/MR1ZtCxPMK7/P68qEQ4RoCrGUT3GtBBuSQ9MzFqge
If8lFHVYSfNKpdzSBLTlwB+2ONcStylA1jUg9MiSRN6anH5867pJvTF+4iGOWfn6
E2yf4IA57p//xGH5LIoXKMMCYWt5bcVnydxnznEHwGYBKAQgk9/4eBhkGSHZBJAQ
qAUC/V9SXuvFNW8c77sJKBlPXirFRIdBa/whHzyGKwBDAqCCW6h0r2yFQ84pmVYF
5xFZpkWdMOBbAa1Rz2NqojfoJqz8b4YGkPtYGve3TZ/nqoDr/wxpiKsobV4oOK63
aAgQh+bk1UD+9HqLOcxuPFRYnxWeTb9Vo0QBjk8IN7Fkt2A6goQ=
=1OCS
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Kamil Dudka]

On Wednesday, January 31, 2018 2:00:08 PM CET Florian Weimer wrote:
> On 01/31/2018 01:54 PM, Kamil Dudka wrote:
> 
> > See that libcurl.so.4 now points to libcurl.so.4.5.0.minimal by mistake.
> > 
> > What is the recommended way to make libcurl{-minimal} build properly
> > again?
> 
> I think in this situation, you need to disable this feature using:
> 
> %undefine __brp_ldconfig

Thank both of you for the suggestion!  It has indeed resolved the problem.

> Depending on whether you can include the appropriate symbolic links in 
> the packages themselves,

Those symlinks are created by libtool, so I believe they are appropriate.

> you can or cannot remove the explicit ldconfig calls.

%undefine __brp_ldconfig removes the build-time ldconfig calls as I understand 
it.  Are you saying that I can remove the following install-time ldconfig 
calls, too?

%post -n libcurl -p /sbin/ldconfig

%postun -n libcurl -p /sbin/ldconfig

%post -n libcurl-minimal -p /sbin/ldconfig

%postun -n libcurl-minimal -p /sbin/ldconfig

> I don't think it's feasible or even desirable to teach ldconfig about 
> the RemovePathPostfixes RPM feature.
> 
> Thanks,
> Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Package Wishlist

[inderaue23]

> Björn Persson hat am 31. Januar 2018 um 00:59 geschrieben:
> 
> 
> inderau...@arcor.de mailto:inderau...@arcor.de wrote:
> 
> > > I'm interest in GNU Ring's communication solution.
> > https://ring.cx/en
> > https://ring.cx/en/about/practical
> > 
> > > I see that FFMPEG is mentioned on Ring's website. FFMPEG isn't 
> > permissible in
> Fedora because the USA's patent system is crap, so it's packaged in RPM 
> Fusion
> instead. Anyone who wants to package Ring will have to do it in RPM 
> Fusion (or
> another add-on repository), unless Ring can function without FFMPEG.
> 

Thanks! Ring does function without FFMPEG as well.


> Björn Persson
> ___
> devel mailing list -- devel@lists.fedoraproject 
> mailto:devel@lists.fedoraproject .org
> To unsubscribe send an email to devel-leave@lists.fedoraproject 
> mailto:devel-leave@lists.fedoraproject .org
> 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Richard Shaw]

On Wed, Jan 31, 2018 at 7:38 AM, Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:

> > 2. Is the plan to update for all supported Fedora releases and not just
> > Rawhide? Otherwise we're back in conditional hell which I thought we were
> > trying to move away from. (Again, the suggested workflow in the wiki for
> > managing branches is to merge across them).
>
> If you use macro, then you should not care at all, it will evaluate to
> ldconfig
> calls on old releases and to noop on F28+. This is mentioned on Change
> Page.


Thanks for clearing that up for me!

Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Neal Gompa]

On Wed, Jan 31, 2018 at 8:14 AM, Richard Shaw  wrote:
> I re-skimmed the whole thread so I apologize if I missed it, but I have a
> couple of questions:
>
> 1. The packaging guidelines still require the explicit use of calling
> ldconfig, so even if it's not technically required, it would be against the
> guidelines to remove them, correct?
>

New guidelines are being drafted:
https://pagure.io/packaging-committee/issue/654

> 2. Is the plan to update for all supported Fedora releases and not just
> Rawhide? Otherwise we're back in conditional hell which I thought we were
> trying to move away from. (Again, the suggested workflow in the wiki for
> managing branches is to merge across them).
>

We could technically push them to all supported Fedora releases, but
that would force a requirement to have a specific minimum version of
glibc per distribution release, and that's just too much. It's easier
to just let it fade out of existence.

In addition, the usage of ldconfig macros being made should make this
a non-issue.

-- 
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Igor Gnatenko]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2018-01-31 at 07:14 -0600, Richard Shaw wrote:
> I re-skimmed the whole thread so I apologize if I missed it, but I have a
> couple of questions:
> 
> 1. The packaging guidelines still require the explicit use of calling
> ldconfig, so even if it's not technically required, it would be against the
> guidelines to remove them, correct?

tibbs is working on updating guidelines[0].

> 2. Is the plan to update for all supported Fedora releases and not just
> Rawhide? Otherwise we're back in conditional hell which I thought we were
> trying to move away from. (Again, the suggested workflow in the wiki for
> managing branches is to merge across them).

If you use macro, then you should not care at all, it will evaluate to ldconfig
calls on old releases and to noop on F28+. This is mentioned on Change Page.

[0] https://pagure.io/packaging-committee/issue/654
- -- 
- -Igor Gnatenko
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpxxukACgkQaVcUvRu8
X0xmuw/8CczKI4GTPB++G4Nep1g3vw2CW9X6Nc2TaukNsGD6QAIIgxbmV5xwVpbX
c1IzAsjl2Zln9ft51hwrnxfOqh69lGOUWFeNmzCaRjU1UoHZ6yx96FNuytuJttcb
Jd9eqsXtfus2LS8oaePulg1k4lbdVHowrvR03U3rRKY6Z6udtcwIihJXaxJ6LIVA
X5Wn1wp3v99Xkk5kRwaYM9Xx38x9kX/wayAdeVW8DD6CtYJorhpMYajGXXzuCwR4
ic1S/EXQnQg+lSZjbhzvdtwsDVgYAdNs0KoOWcrC7RbeG8kSz81iG4jMVZYeVImH
vqbsy3mE6i7noG7Bo4vFX0JZ5yMPXp+pON2ifvU1ZXlDdxfxpqlOL27AFz9HKrzM
jiCvHHBg4fOrLMX/rR1cSqV95jxg0Dfpcih9OKkV+SRKORebCYocpb0ljzuT34pu
Ay1FTFtHhCpFT3e/rgv3hgS0YygWW7iHMTz8QCNM8cN6JfO5EoVc0PJQY5wZtH+f
EbFtTUTd8r81QxEB9TKoVcevsiEXhf65WEbmD5sSqWBfVsi6MY7lALZGU32EbKx4
WdOYVHIxQK8AO0mMnimM3V1osLEhZFERASy137YncKNL5OXbsuS8tzAiShqANwVv
sejFhUqBOo+DGeycRgQrRoziLClZpQlUISRIkkMDFbL1W5PgGwU=
=FiJi
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Tomasz Kłoczko]

On 31 January 2018 at 09:37, Howard Howell  wrote:
[..]

> Well, Journalctl shows the following.
> Jan 31 00:00:00 school evolution-alarm[2297]:
> /builddir/build/BUILD/evolution-3.24.6/src/calendar/alarm-
> notify/alarm.c:251:
> Jan 31 00:19:56 school sol.desktop[24828]: xkbcommon: ERROR: Key ""
> added to modifier map for multiple modifiers; Usi
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /var/tmp/systemd-private-3d6dfe8707be46aa9187
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /var/tmp/systemd-private-3d6dfe8707be46aa9187
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /var/tmp/systemd-private-3d6dfe8707be46aa9187
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /var/tmp/systemd-private-3d6dfe8707be46aa9187
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
> Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate children
> of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
> Jan 31 01:09:51 school org.gnome.Calculator.desktop[25129]: xkbcommon:
> ERROR: Key "" added to modifier map for multip
> Jan 31 01:10:45 school gnome-calculato[25129]: gtk_container_remove:
> assertion 'GTK_IS_WIDGET (widget)' failed
> Jan 31 01:14:08 school evolution-alarm[2297]: Error reading events from
> display: Broken pipe
> Jan 31 01:14:08 school gnome-software[2301]: Error reading events from
> display: Broken pipe
> Jan 31 01:14:08 school gnome-session-binary[1715]: WARNING: App
> 'org.gnome.Shell.desktop' exited with code 1
> Jan 31 01:14:08 school gnome-session[1715]: gnome-session-binary[1715]:
> WARNING: App 'org.gnome.Shell.desktop' exited with
> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window manager
> error: Could not find cursor. Perhaps set XCURSOR_PATH
> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Fatal server error:
> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE) failed to read
> Wayland events: Broken pipe
> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE)
> Jan 31 01:14:08 school gnome-session-binary[1715]: Unrecoverable failure
> in required component org.gnome.Shell.desktop
> Jan 31 01:14:08 school org.gnome.SettingsDaemon.MediaKeys.desktop[2048]:
> xcb_connection_has_error() returned true
> Jan 31 01:14:08 school gsd-housekeepin[2045]: gsd-housekeeping: Fatal IO
> error 11 (Resource temporarily unavailable) on X s
> Jan 31 01:14:08 school gsd-print-notif[2013]: gsd-print-notifications:
> Fatal IO error 11 (Resource temporarily unavailable)
> Jan 31 01:14:08 school at-spi-bus-launcher[1825]: XIO:  fatal IO error 11
> (Resource temporarily unavailable) on X server ":
>  ESCOC
>
> This doesn't tell me anything, but I'll bet some of you systems guys can
> see through it to see the root cause, or at least a good trail to follow.
>

After update today to latest rawhide and reboot I'v decided to change GUI
from X11 to Wyland.
In logs I see similar entries like above.

Additionally what I found so far after few hours:

1) sometimes pressing single key is causing to generate many keystrokes.
Very annoying ..
  I had such effect at least 10 times in last hour. Looks like some
libinput effect.

2) I have wireless Logitech mouse and when I'm moving mouse cursor after at
least few seconds whole desktop stops for about 0.5 to less than second
(with mouse cursor as well) and each time after this in dmesg I see
sequence of lines like:

[26683.059926] [drm] PCIE gen 2 link speeds already enabled
[26683.069526] [drm] PCIE GART of 1024M enabled (table at
0x00162000).
[26683.069637] radeon :01:00.0: WB enabled
[26683.069642] radeon :01:00.0: fence driver on ring 0 use gpu addr
0x2c00 and cpu addr 0xd8c75981
[26683.069646] radeon :01:00.0: fence driver on ring 3 use gpu addr
0x2c0c and cpu addr 0x1142ed24
[26683.070395] radeon :01:00.0: fence driver on ring 5 use gpu addr
0x00072118 and cpu addr 0x095357f2
[26683.086835] [drm] ring test on 0 succeeded in 2 usecs
[26683.086851] [drm] ring test on 3 succeeded in 7 usecs
[26683.264201] [drm] ring test on 5 succeeded in 2 usecs
[26683.264214] [drm] UVD initialized successfully.
[26683.264346] [drm] ib test on ring 0 succeeded in 0 usecs
[26683.264481] [drm] ib test on ring 3 succeeded in 0 usecs
[26683.919712] [drm] ib test on ring 5 succeeded

Every few times of such sequence additionally I have:

[26815.820342] radeon :01:00.0: swiotlb buffer is full (sz: 2097152
bytes)
[26815.820349] swiotlb: coherent allocation failed for device :01:00.0

Re: RPM packaging and ldconfig handling

[Richard Shaw]

I re-skimmed the whole thread so I apologize if I missed it, but I have a
couple of questions:

1. The packaging guidelines still require the explicit use of calling
ldconfig, so even if it's not technically required, it would be against the
guidelines to remove them, correct?

2. Is the plan to update for all supported Fedora releases and not just
Rawhide? Otherwise we're back in conditional hell which I thought we were
trying to move away from. (Again, the suggested workflow in the wiki for
managing branches is to merge across them).

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Olivier Fourdan]

Hi

On Wed, Jan 31, 2018 at 1:58 PM, Olivier Fourdan 
wrote:

> Jan 31 01:14:08 school gnome-session[1715]: gnome-session-binary[1715]:
> WARNING: App 'org.gnome.Shell.desktop' exited with
>
>> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window manager
>> error: Could not find cursor. Perhaps set XCURSOR_PATH
>>
>
> Interesting, that could be the problem! gnome-shell is both a Wayland
> compositor (thus the display server) and an X11 window manager.
>

Are you using a custom cursor theme or the default “Adwaita” cursor theme?


> I think we should keep those discussions, including these important bits,
> in the issue you filed upstream (https://gitlab.gnome.org/GNOM
> E/gnome-shell/issues/9) and not in a downstream mailing list :)
>

And... I got confused by multiple issues being reported in the same mail
thread, that issue was filed by Przemek, so probably different from yours...

Cheers,
Olivier
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

perl-RDF-RDFa-Generator license change

[Petr Pisar]

perl-RDF-RDFa-Generator-0.192-1.fc28 changed license from:

(GPL+ or Artistic) and CC-BY-SA and Public Domain

to:

(GPL+ or Artistic) and Public Domain.

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Igor Gnatenko]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2018-01-31 at 14:00 +0100, Florian Weimer wrote:
> On 01/31/2018 01:54 PM, Kamil Dudka wrote:
> > See that libcurl.so.4 now points to libcurl.so.4.5.0.minimal by mistake.
> > 
> > What is the recommended way to make libcurl{-minimal} build properly again?
> 
> I think in this situation, you need to disable this feature using:
> 
> %undefine __brp_ldconfig
> 
> Depending on whether you can include the appropriate symbolic links in 
> the packages themselves, you can or cannot remove the explicit ldconfig 
> calls.
> 
> I don't think it's feasible or even desirable to teach ldconfig about 
> the RemovePathPostfixes RPM feature.

Well, we could expose `removePostfixes` as environment variable when brps are
executed, so we could do some workarounds like processing all those libraries
separately followed by renaming soname back.

Shouldn't be hard to do.. I will try to prepare patch later this week.
- -- 
- -Igor Gnatenko
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpxv1IACgkQaVcUvRu8
X0z7xw/9F44a2CewhQEMC1u52IVXMl4KvI2dvn9uNTWRA2f0PR1VZ4gLxaycrKKC
mx7p87FaFYpYFqIm2p0iITcjA1gu3ejVfCzHI+I3Bb0I90VlM0rV7U2s2E8TvoNO
i4Wr1c+gMn5boVAqPeO6D1Wk8jWz4ka0zsdsJ7PbhBt/2N3ITMs0Byxg072HYy7V
Ly8ztJyHONIYFCYi9exqWZcgeTihuNsMro8TFjQ60RApCaSeY/cEIRN+C8yuiee8
Q8BQWyE4b0nBHgLwLFAx+UHbO9Rt85wZGRsKOtJhtAAdOWq0w90GZedYgPuq0Y95
YAUCm8uSeBr328eRKOI6usdAJOwqz/B/hA7cSu12xD8leo7MAQjJhhfHaKTJIXAc
/5gCHUVGSuZjjB/+Alg6Fwe5ggQCtQz5rKHPtHyRL8JjDo/DecK8jtEcVAaSaJiJ
BMWlF1ZmMZS8GBJEinV/atyxGUIxv/huO3np8G6ThnwfcK+giIiAvFStkyap5mbv
yjrnKU+hOOnFTdiKrbuhIDqRIIjcxDUlEdz9vV5LNR0DOqW7hMR2CTV/CWmLZEck
XMCCPGmBsdmFKQ2smdIF6dMz+xG36E8IjbdKKd7LhBtGcL104PLLA4H3HkB9/ItJ
rvcA4ySTvF1YfNP0HuVMcTeJYzrxkG9YvPDymK/sjqQVKt1BIc0=
=em37
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1528845] perl-RDF-RDFa-Generator-0.192 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1528845

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-RDF-RDFa-Generator-0.1
   ||92-1.fc28
 Resolution|--- |RAWHIDE
Last Closed||2018-01-31 08:05:44



--- Comment #2 from Petr Pisar  ---
New features, new dependency. Suitable for Rawhide only.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Igor Gnatenko]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2018-01-31 at 13:54 +0100, Kamil Dudka wrote:
> On Tuesday, January 30, 2018 9:57:39 AM CET Igor Gnatenko wrote:
> > brp-ldconfig simply calls `/sbin/ldconfig -N -r "$RPM_BUILD_ROOT"` and
> > there
> > is no /etc/ld.so.conf under $RPM_BUILD_ROOT when you build... In theory we
> > could supply one (empty), but I would ask Florian what would be the best to
> > do. --
> > -Igor Gnatenko
> 
> This change broke the build of libcurl{-minimal} because ldconfig now
> operates
> on an intermediate layout of the installed shared libraries, which is needed
> by the RemovePathPostfixes feature of RPM, instead of the final layout that
> is
> actually packaged as libcurl and libcurl-minimal.
> 
> 
> At the end of %install, the build root contains this:
> 
> + ls -l /builddir/build/BUILDROOT/curl-7.58.0-2.fc28.s390x/usr/lib64
> total 8324
> lrwxrwxrwx. 1 mockbuild mockbuild  16 Jan 31 12:46 libcurl.so ->
> libcurl.so.4.5.0
> lrwxrwxrwx. 1 mockbuild mockbuild  16 Jan 31 12:46 libcurl.so.4 ->
> libcurl.so.4.5.0
> -rwxr-xr-x. 1 mockbuild mockbuild 4398816 Jan 31 12:46 libcurl.so.4.5.0
> -rwxr-xr-x. 1 mockbuild mockbuild 4120952 Jan 31 12:46
> libcurl.so.4.5.0.minimal
> lrwxrwxrwx. 1 mockbuild mockbuild  16 Jan 31 12:46 libcurl.so.4.minimal
> -> libcurl.so.4.5.0
> drwxr-xr-x. 2 mockbuild mockbuild  24 Jan 31 12:46 pkgconfig
> 
> 
> But at the beginning of %check, the build root contains this:
> 
> + ls -l /builddir/build/BUILDROOT/curl-7.58.0-2.fc28.s390x/usr/lib64
> total 1172
> lrwxrwxrwx. 1 mockbuild mockbuild 16 Jan 31 12:46 libcurl.so ->
> libcurl.so.4.5.0
> lrwxrwxrwx. 1 mockbuild mockbuild 24 Jan 31 12:46 libcurl.so.4 ->
> libcurl.so.4.5.0.minimal
> -rwxr-xr-x. 1 mockbuild mockbuild 614896 Jan 31 12:46 libcurl.so.4.5.0
> -rwxr-xr-x. 1 mockbuild mockbuild 577760 Jan 31 12:46
> libcurl.so.4.5.0.minimal
> lrwxrwxrwx. 1 mockbuild mockbuild 16 Jan 31 12:46 libcurl.so.4.minimal ->
> libcurl.so.4.5.0
> drwxr-xr-x. 2 mockbuild mockbuild 24 Jan 31 12:46 pkgconfig
> 
> 
> See that libcurl.so.4 now points to libcurl.so.4.5.0.minimal by mistake.
> 
> What is the recommended way to make libcurl{-minimal} build properly again?

Just `%undefine __brp_ldconfig`. And you can safely remove / replace with macro
calls to ldconfig because you are packaging DSO symlinks and it will continue
working fine..

I will think how we can make support for RemovePathPostfixes.
- -- 
- -Igor Gnatenko
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpxvrgACgkQaVcUvRu8
X0z61A//an3YDqsC86tA1VCWMgx7gDSutV3eXS1SkvYWGu+h9MlZRTQmoa9alpDd
FFZrYnxt77ln71IvOF+IAhL1MxbwFmkPAU8n9+q6o3jVH1wN8F5iRNzqjyX91StA
Ib/YK781/Bjk4SflsULmqb5sCANeTr1Qb0W4JEd9mE0iGSVZTJ03DC5jheZKw3Lf
UcPaI3jPHv7wztZ6TRzf0abr2e6o77gkYggkC9qq2bZ/XnTUbCsV/82seiF0wwK2
+x1tQLeDFQf+SMJo5WnB4wX1oh/sQBYPEzsbzFaMCCRHY5R21xmYqtM8lXVC2EzW
S2cZ36IsxqljbFR7U3W5TNPZdROTiDEE24Bh1ztZaDx/CG9x65hyb6tbJCuzikPw
HajJjmODcKfsXXESoXGFJ4FQknMkXyCWa8M1HKhTFnR8oeNymbSn2dMEudBWiIQv
SU3NhYjxOkLvPKnXt7JAgXDysNwflEjje8QfvAUFpxAvOAMtBDoNnPfp2si67sMS
sI+iQaF/CBFLYQRqQdFCiPASMUk6H7myeh2/3w/0yjG4tC6gpU7kWa5bvLReZUNU
lVCnhMETnGLbmwMKmZzfg4ARZTeN9BX5vtnMpaxb6Yc3ypfPu4B0YPNA12U1+xKp
CbJsfB09lVOBVGvJVxG8TC6AwgYRAWwLkHoJT57cygOL1Kfvtv0=
=fbEP
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Florian Weimer]

On 01/31/2018 01:54 PM, Kamil Dudka wrote:

See that libcurl.so.4 now points to libcurl.so.4.5.0.minimal by mistake.

What is the recommended way to make libcurl{-minimal} build properly again?


I think in this situation, you need to disable this feature using:

%undefine __brp_ldconfig

Depending on whether you can include the appropriate symbolic links in 
the packages themselves, you can or cannot remove the explicit ldconfig 
calls.


I don't think it's feasible or even desirable to teach ldconfig about 
the RemovePathPostfixes RPM feature.


Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Olivier Fourdan]

Hi,

What you logs tells is:

On Wed, Jan 31, 2018 at 10:37 AM, Howard Howell 
wrote:

> Jan 31 01:14:08 school evolution-alarm[2297]: Error reading events from
> display: Broken pipe
> Jan 31 01:14:08 school gnome-software[2301]: Error reading events from
> display: Broken pipe
>

Wayland native applications exiting with broken pipe, means the Wayland
compositor (gnome-shell is dead)


> Jan 31 01:14:08 school gnome-session-binary[1715]: WARNING: App
> 'org.gnome.Shell.desktop' exited with code 1
>

gnome-session tells us that gnome-shell is gone


> Jan 31 01:14:08 school gnome-session[1715]: gnome-session-binary[1715]:
> WARNING: App 'org.gnome.Shell.desktop' exited with
> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window manager
> error: Could not find cursor. Perhaps set XCURSOR_PATH
>

Interesting, that could be the problem! gnome-shell is both a Wayland
compositor (thus the display server) and an X11 window manager.


> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Fatal server error:
> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE) failed to read
> Wayland events: Broken pipe
> Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE)
>

Then Xwayland exits with “broken pipe”, like the other Wayland clients,
because the Wayland compositor is, well ,dead.


> Jan 31 01:14:08 school gnome-session-binary[1715]: Unrecoverable failure
> in required component org.gnome.Shell.desktop
>

gnome-session says something goes really wrong...


> Jan 31 01:14:08 school org.gnome.SettingsDaemon.MediaKeys.desktop[2048]:
> xcb_connection_has_error() returned true
> Jan 31 01:14:08 school gsd-housekeepin[2045]: gsd-housekeeping: Fatal IO
> error 11 (Resource temporarily unavailable) on X s
> Jan 31 01:14:08 school gsd-print-notif[2013]: gsd-print-notifications:
> Fatal IO error 11 (Resource temporarily unavailable)
> Jan 31 01:14:08 school at-spi-bus-launcher[1825]: XIO:  fatal IO error 11
> (Resource temporarily unavailable) on X server ":
>  ESCOC
>

And now, the X11 clients (hence depending on the X server, thus Xwayland)
all quit as well, because the X server (Xwayland) is dead, because the
Wayland compositor is dead...


> This doesn't tell me anything, but I'll bet some of you systems guys can
> see through it to see the root cause, or at least a good trail to follow.
>

I think we should keep those discussions, including these important bits,
in the issue you filed upstream (
https://gitlab.gnome.org/GNOME/gnome-shell/issues/9) and not in a
downstream mailing list :)

Cheers,
Olivier
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM packaging and ldconfig handling

[Kamil Dudka]

On Tuesday, January 30, 2018 9:57:39 AM CET Igor Gnatenko wrote:
> brp-ldconfig simply calls `/sbin/ldconfig -N -r "$RPM_BUILD_ROOT"` and there
> is no /etc/ld.so.conf under $RPM_BUILD_ROOT when you build... In theory we
> could supply one (empty), but I would ask Florian what would be the best to
> do. --
> -Igor Gnatenko

This change broke the build of libcurl{-minimal} because ldconfig now operates
on an intermediate layout of the installed shared libraries, which is needed
by the RemovePathPostfixes feature of RPM, instead of the final layout that is
actually packaged as libcurl and libcurl-minimal.


At the end of %install, the build root contains this:

+ ls -l /builddir/build/BUILDROOT/curl-7.58.0-2.fc28.s390x/usr/lib64
total 8324
lrwxrwxrwx. 1 mockbuild mockbuild  16 Jan 31 12:46 libcurl.so -> 
libcurl.so.4.5.0
lrwxrwxrwx. 1 mockbuild mockbuild  16 Jan 31 12:46 libcurl.so.4 -> 
libcurl.so.4.5.0
-rwxr-xr-x. 1 mockbuild mockbuild 4398816 Jan 31 12:46 libcurl.so.4.5.0
-rwxr-xr-x. 1 mockbuild mockbuild 4120952 Jan 31 12:46 libcurl.so.4.5.0.minimal
lrwxrwxrwx. 1 mockbuild mockbuild  16 Jan 31 12:46 libcurl.so.4.minimal -> 
libcurl.so.4.5.0
drwxr-xr-x. 2 mockbuild mockbuild  24 Jan 31 12:46 pkgconfig


But at the beginning of %check, the build root contains this:

+ ls -l /builddir/build/BUILDROOT/curl-7.58.0-2.fc28.s390x/usr/lib64
total 1172
lrwxrwxrwx. 1 mockbuild mockbuild 16 Jan 31 12:46 libcurl.so -> 
libcurl.so.4.5.0
lrwxrwxrwx. 1 mockbuild mockbuild 24 Jan 31 12:46 libcurl.so.4 -> 
libcurl.so.4.5.0.minimal
-rwxr-xr-x. 1 mockbuild mockbuild 614896 Jan 31 12:46 libcurl.so.4.5.0
-rwxr-xr-x. 1 mockbuild mockbuild 577760 Jan 31 12:46 libcurl.so.4.5.0.minimal
lrwxrwxrwx. 1 mockbuild mockbuild 16 Jan 31 12:46 libcurl.so.4.minimal -> 
libcurl.so.4.5.0
drwxr-xr-x. 2 mockbuild mockbuild 24 Jan 31 12:46 pkgconfig


See that libcurl.so.4 now points to libcurl.so.4.5.0.minimal by mistake.

What is the recommended way to make libcurl{-minimal} build properly again?

Kamil
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1540511] perl-Time-OlsonTZ-Download-0.009 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1540511

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Time-OlsonTZ-Download-
   ||0.009-1.fc28
 Resolution|--- |RAWHIDE
Last Closed||2018-01-31 06:03:21



--- Comment #3 from Petr Pisar  ---
This splits a public method into new new methods. Suitable for Rawhide only.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: Keeping old packages

[Avi Kivity]

On 01/29/2018 07:29 PM, Stephen John Smoogen wrote:



On 29 January 2018 at 05:53, Avi Kivity > wrote:


Recently, I ran into breakage due to yaml-cpp-0.5.3 breaking
yaml-cpp-0.5.1's ABI. The breakage was due to upstream not
maintaining ABI compatibility (something that's very hard with
some C++ libraries), but recovering from it was pretty hard, due
to EPEL not keeping old packages around.


If old packages were kept around, we could just tell people to run
"yum downgrade yaml-cpp-0.5.1" and then pin that package, until
the ABI issue was resolved. As it was, we had to refer them to the
package from koji, which means that new installs become harder.


Can we change the policy to keep old packages in the repository,
to prevent this in the future?


This requires a bit of work due to the way that EPEL is made into a 
repository. It would require changing the layout quite a bit for what 
seems a 'simple' change. It is hopefully going to be on the books for 
this year though.




Thanks, it will make recovering from upgrade disasters a lot easier.

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: Orphaning some Spacewalk packages

[Emmanuel Seyman]

* Miroslav Suchý [30/01/2018 12:39] :
> 
> And I orphaned
>   perl-Socket-MsgHdr
>   perl-Crypt-GeneratePassword
> as I these are not used in Spacewalk as well.

I'll gladly take these two packages over. My fas username is eseyman.

Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [Fedora-packaging] Re: Proposed Fedora packaging guideline: More Go packaging

[nicolas . mailhot]

>De: "Neal Gompa" 

> The only thing I see that might be missing is autogenerating
> bundled(golang()) Provides when a vendor tree exists (with the
> appropriate automatic filters on Requires).

I had though a little about doing it but first, as many Go elements, vendoring 
relies on conventions not standards. The nasty thing about conventions is that 
they are not applied 100% the same way by everyone, making automation a PITA. 
And second interactions with autodeps can be nasty: you can filter out 
provides, but do you filter out requires? What about all the junk code many 
projects ship as testing and examples and which is vendored with the rest?

I don't say it can't be done, or that it would be difficult to do once the rest 
is merged, but I'll live it to someone that absolutely want to ship a Go 
package with vendored parts.

Right now we sidestep the issue in our packages by rm -fr ing anything that 
looks like vendored code in %prep. Unbundling takes time but it has a positive 
cumulative effect: the more you unbundle the less you need to worry about in 
other packages with the same requirements. And unbundling reveals code/legal 
problems that it would take about as much work to solve by auditing the 
vendored code manually.

Regards,

-- 
Nicolas mAilhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [HEADS UP] Removal of systemd-units

[Sérgio Basto]

Replying to myself , clamav miss all scriptleting of systemd :(, sorryfor the 
noise 

On Wed, 2018-01-31 at 09:41 +, Sergio wrote:
> Btw this scriptlenting doesn't break epel 7 i.e. I had received
> reports that systemd doesn't reload daemons correctly in epel 7 , I'm
> talking about clamav 
> 
> Sent from my Android
> Em 31/01/2018 3:51 da manhã, Nathanael Noblet  > escreveu:
> > 
> > 
> > > beanstalkd   gnat jjh 
> > 
> > Updated in epel7 - rawhide was fine already 
> > 
> > Oddly, dspam which is the package I updated earlier today wasn't on
> > this list and has the Requires/BuildRequires of systemd-units. Not
> > sure why it isn't on your list. However it could mean that if you
> > remove systemd-units some packages will break at that point
> > instead. 
> > 
> > I've also updated dspam in epel7 now
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Orphaning some Spacewalk packages

[Peter Robinson]

On Tue, Jan 30, 2018 at 11:39 AM, Miroslav Suchý  wrote:
> I orphaned
>   rhnmd
> This is Spacewalk package which is not developed any more.

If it's dead upstream with no users within Fedora you're much better
off just retiring it directly with  "fedpkg retire" than letting it
hand around.

> And I orphaned
>   perl-Socket-MsgHdr
>   perl-Crypt-GeneratePassword
> as I these are not used in Spacewalk as well.
>
> Miroslav
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [HEADS UP] Removal of systemd-units

[Sergio]

Btw this scriptlenting doesn't break epel 7 i.e. I had received reports that 
systemd doesn't reload daemons correctly in epel 7 , I'm talking about clamav 

Sent from my Android
Em 31/01/2018 3:51 da manhã, Nathanael Noblet  escreveu:
>
>
> > beanstalkd   gnat jjh 
>
> Updated in epel7 - rawhide was fine already 
>
> Oddly, dspam which is the package I updated earlier today wasn't on this list 
> and has the Requires/BuildRequires of systemd-units. Not sure why it isn't on 
> your list. However it could mean that if you remove systemd-units some 
> packages will break at that point instead. 
>
> I've also updated dspam in epel7 now
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Howard Howell]

On Wed, 2018-01-31 at 01:28 -0800, Howard Howell wrote:
> On Tue, 2018-01-30 at 10:15 -0800, Howard Howell wrote:
> > On Tue, 2018-01-30 at 10:49 -0500, Przemek Klosowski wrote:
> > > On 01/29/2018 09:33 PM, mcatanz...@gnome.org wrote:
> > > > Please see my earlier post in this thread regarding how to get
> > > > a 
> > > > stacktrace out of coredumpctl
> > > 
> > > This is a great debugging harness; thanks for pointing it out as
> > > I 
> > > didn't know about it.
> > > 
> > > I am currently reporting my pan-crashing-Wayland crashing issue
> > > on 
> > > gnome.org---but in the true Heisenbug fashion it stopped
> > > crashing,
> > > so
> > > I 
> > > can't reproduce it now. It was crashing almost every time I used
> > > the
> > > pan 
> > > newsreader (the three crash dumps I submitted were just few days
> > > apart 
> > > in my coredumpctl records), but now they're as solid as rock.
> > > 
> > > I have to say that the GNOME developers responded almost
> > > immediately, 
> > > and I feel stupid for not being able to demonstrate replication.
> > > I
> > > am 
> > > really curious about the nature of this bug: it must be some
> > > weird 
> > > interaction---perhaps related to memory use or something like
> > > that.
> > > ___
> > > devel mailing list -- devel@lists.fedoraproject.org
> > > To unsubscribe send an email to devel-
> > > le...@lists.fedoraproject.org
> > 
> > I had the same experience.  I loaded all the tools that were
> > recommended, and the crashes seem to have stopped ( that is no
> > crashes
> > since I loaded all the tools.) Maybe there is a hidden fix in the
> > debug
> > stuff.
> > 
> > Regards,
> > Les H
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 
> spoke too soon.  Just got logged out.  Had just finished looking up
> some info on bitcoin on the web, then closed the browser, moved the
> mouse toward the top annunciation in the top banner of the desktop. 
> Screen went dark and dropped me out to the login window.
> 
> Checking logs and backtrace to see if I can find anything useful...
> Later post if I do.
> 
> Regards,
> Les H
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Well, Journalctl shows the following.  
Jan 31 00:00:00 school evolution-alarm[2297]:
/builddir/build/BUILD/evolution-3.24.6/src/calendar/alarm-
notify/alarm.c:251:
Jan 31 00:19:56 school sol.desktop[24828]: xkbcommon: ERROR: Key
"" added to modifier map for multiple modifiers; Usi
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /var/tmp/systemd-private-3d6dfe8707be46aa9187
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /var/tmp/systemd-private-3d6dfe8707be46aa9187
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /var/tmp/systemd-private-3d6dfe8707be46aa9187
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /var/tmp/systemd-private-3d6dfe8707be46aa9187
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
Jan 31 00:59:38 school gsd-housekeepin[2045]: Failed to enumerate
children of /tmp/systemd-private-3d6dfe8707be46aa9187e85e
Jan 31 01:09:51 school org.gnome.Calculator.desktop[25129]: xkbcommon:
ERROR: Key "" added to modifier map for multip
Jan 31 01:10:45 school gnome-calculato[25129]: gtk_container_remove:
assertion 'GTK_IS_WIDGET (widget)' failed
Jan 31 01:14:08 school evolution-alarm[2297]: Error reading events from
display: Broken pipe
Jan 31 01:14:08 school gnome-software[2301]: Error reading events from
display: Broken pipe
Jan 31 01:14:08 school gnome-session-binary[1715]: WARNING: App
'org.gnome.Shell.desktop' exited with code 1
Jan 31 01:14:08 school gnome-session[1715]: gnome-session-binary[1715]: 
WARNING: App 'org.gnome.Shell.desktop' exited with 
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window manager
error: Could not find cursor. Perhaps set XCURSOR_PATH
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Fatal server
error:
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE) failed to
read Wayland events: Broken pipe
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE)
Jan 31 01:14:08 school gnome-session-binary[1715]: Unrecoverable
failure in required component org.gnome.Shell.desktop
Jan 31 01:14:08 school
org.gnome.SettingsDaemon.MediaKeys.desktop[2048]:
xcb_connection_has_error() returned true
Jan 31 01:14:08 school 

[Bug 1534083] perl-Socket-2.027 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1534083



--- Comment #5 from Fedora Update System  ---
perl-Socket-2.027-1.fc26 has been submitted as an update to Fedora 26.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-fb7da310cb

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1533867] perl-Socket-2.026 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1533867



--- Comment #5 from Fedora Update System  ---
perl-Socket-2.027-1.fc26 has been submitted as an update to Fedora 26.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-fb7da310cb

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: Wyland is a disaster

[Howard Howell]

On Tue, 2018-01-30 at 10:15 -0800, Howard Howell wrote:
> On Tue, 2018-01-30 at 10:49 -0500, Przemek Klosowski wrote:
> > On 01/29/2018 09:33 PM, mcatanz...@gnome.org wrote:
> > > Please see my earlier post in this thread regarding how to get a 
> > > stacktrace out of coredumpctl
> > 
> > This is a great debugging harness; thanks for pointing it out as I 
> > didn't know about it.
> > 
> > I am currently reporting my pan-crashing-Wayland crashing issue on 
> > gnome.org---but in the true Heisenbug fashion it stopped crashing,
> > so
> > I 
> > can't reproduce it now. It was crashing almost every time I used
> > the
> > pan 
> > newsreader (the three crash dumps I submitted were just few days
> > apart 
> > in my coredumpctl records), but now they're as solid as rock.
> > 
> > I have to say that the GNOME developers responded almost
> > immediately, 
> > and I feel stupid for not being able to demonstrate replication. I
> > am 
> > really curious about the nature of this bug: it must be some weird 
> > interaction---perhaps related to memory use or something like that.
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 
> I had the same experience.  I loaded all the tools that were
> recommended, and the crashes seem to have stopped ( that is no
> crashes
> since I loaded all the tools.) Maybe there is a hidden fix in the
> debug
> stuff.
> 
> Regards,
> Les H
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
spoke too soon.  Just got logged out.  Had just finished looking up
some info on bitcoin on the web, then closed the browser, moved the
mouse toward the top annunciation in the top banner of the desktop. 
Screen went dark and dropped me out to the login window.

Checking logs and backtrace to see if I can find anything useful...
Later post if I do.

Regards,
Les H
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1392479] perl-Alien-ROOT not available on ppc64le because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392479



--- Comment #3 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-7.fc26 has been submitted as an update to Fedora 26.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-cf41988c7d

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1392475] perl-Alien-ROOT not available on ppc64 because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392475



--- Comment #3 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-7.fc26 has been submitted as an update to Fedora 26.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-cf41988c7d

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1532914] perl-Socket-2.025 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1532914

Petr Pisar  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2018-01-31 04:27:44



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1540511] perl-Time-OlsonTZ-Download-0.009 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1540511



--- Comment #2 from Upstream Release Monitoring 
 ---
hotness's scratch build of perl-Time-OlsonTZ-Download-0.009-1.el7.src.rpm for
rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=24590838

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1392475] perl-Alien-ROOT not available on ppc64 because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392475



--- Comment #2 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-10.fc27 has been submitted as an update to Fedora 27.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-610360e2c0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1392479] perl-Alien-ROOT not available on ppc64le because root is not there

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1392479



--- Comment #2 from Fedora Update System  ---
perl-Alien-ROOT-5.34.36.1-10.fc27 has been submitted as an update to Fedora 27.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-610360e2c0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1540511] perl-Time-OlsonTZ-Download-0.009 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1540511



--- Comment #1 from Upstream Release Monitoring 
 ---
Created attachment 132
  --> https://bugzilla.redhat.com/attachment.cgi?id=132=edit
[patch] Update to 0.009 (#1540511)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1540510] New: Upgrade perl-SQL-Abstract to 1.85

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1540510

Bug ID: 1540510
   Summary: Upgrade perl-SQL-Abstract to 1.85
   Product: Fedora
   Version: rawhide
 Component: perl-SQL-Abstract
  Assignee: tcall...@redhat.com
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
tcall...@redhat.com



Latest Fedora delivers 1.84 version. Upstream released 1.85. When you have free
time, please upgrade it

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1540511] New: perl-Time-OlsonTZ-Download-0.009 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1540511

Bug ID: 1540511
   Summary: perl-Time-OlsonTZ-Download-0.009 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Time-OlsonTZ-Download
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com



Latest upstream release: 0.009
Current version/release in rawhide: 0.008-1.fc28
URL: http://search.cpan.org/dist/Time-OlsonTZ-Download/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/15759/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1537992] Upgrade perl-Mail-DKIM to 0.52

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1537992

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Mail-DKIM-0.52-1.fc28
 Resolution|--- |RAWHIDE
   Assignee|ky...@kylev.com |jples...@redhat.com
Last Closed||2018-01-31 04:12:01



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: copr mailist?

[Miroslav Suchý]

Dne 30.1.2018 v 23:03 Adrian Sevcenco napsal(a):
> Hi! I was wondering what would be the best place to ask help about problems 
> building packages on copr...

https://lists.fedorahosted.org/archives/list/copr-de...@lists.fedorahosted.org/

Miroslav
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Fedora 28 Rawhide Rebase Warning to Package Maintainers

[Jan Kurik]

Greetings,

This e-mail is intended to inform you about the upcoming Bugzilla changes
happening on 2018-02-20 (Rawhide bug rebase) and what you need to do, if
anything.

We will be automatically changing the version for most rawhide bugs to
Fedora 28.
This will result in regular bugs reported against rawhide during the Fedora
28
development cycle being changed to version ‘28' instead of their current
assignment, ‘rawhide’.  This is to align with the branching of Fedora 28
from
rawhide and to more accurately tell where in the lineage of releases the
bug was
last reported.

Note that this procedure does not apply to bugs that are open for the
‘Package
Review’ or 'kernel' components or bugs that have the ''FutureFeature'' or
''Tracking'' keywords
set. These will stay open as rawhide bugs indefinitely.

If you do not want your bugs changed to version ‘28‘, add the
''FutureFeature''
keyword. If you need help changing a large amount of bugs manually, we’d be
glad
to help.

The process was re-approved by FESCo https://pagure.io/fesco/issue/1096 .

Jan
-- 
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1537991] Upgrade perl-Set-Object to 1.39

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1537991

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Set-Object-1.39-1.fc28
 Resolution|--- |RAWHIDE
   Assignee|kra...@redhat.com   |jples...@redhat.com
Last Closed||2018-01-31 03:24:55



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org