Re: Last dbus upgrade issues

2018-11-25 Thread Zbigniew Jędrzejewski-Szmek 
On Sun, Nov 25, 2018 at 02:36:31AM +0100, Tomasz Kłoczko wrote:
> After last dbus upgrade gdm found that is not able to start.

What Fedora version? Ideally provide specific rpm versions.
dbus-in-F29 != dbus-in-F30 now.

Zbyszek

> NM basen network configuration as well is broker because it needs dbus as
> well which is not starting.
> So many dependencies on dubs looks really terrible/strange/dangerous IMO.
> 
> So far found that /ust/lib/tmpfiles.d/dbus.conf does not point to /run/dbus.
> 
> Can someomeon tell what needs to be done to bring system to usable state?
> 
> Level of the verbosity messages written to system logs about what and by
> what failed is close to nothing.
> 
> BTW when gdm fails console is completely blocked. Only thing which is
> possible to do is reboot, go to single mode and after disable gdm service
> and reboot is possible to continue troubleshoot system issues.
> 
> kloczek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Upgraded from F28 x96_64 XFCE Spin to F29 => rough audio

2018-11-25 Thread Zbigniew Jędrzejewski-Szmek 
On Sat, Nov 17, 2018 at 07:17:44PM +1100, Philip Rhoades wrote:
> Leigh,
> 
> 
> On 2018-11-17 18:19, Leigh Scott wrote:
> >Try
> >
> >https://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems#Playback_problems.2C_crackling_or_skipping
> 
> 
> My problem is not crackling_or_skipping - it is more just noisy.
> That link is a fix for a PA problem and is not specific to the
> F28->F29 upgrade which has caused the current problem.  I don't want
> to have to re-install PA now - to my way of thinking, that just adds
> a layer of complexity to the problem.

Try to fiddle with all the controls in alsamixer. Sometimes $noise can
be fixed by muting some alsa meter.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Last dbus upgrade issues

2018-11-25 Thread Tomasz Kłoczko 
On Sun, 25 Nov 2018 at 11:19, Zbigniew Jędrzejewski-Szmek 
wrote:

> On Sun, Nov 25, 2018 at 02:36:31AM +0100, Tomasz Kłoczko wrote:
> > After last dbus upgrade gdm found that is not able to start.
>
> What Fedora version? Ideally provide specific rpm versions.
> dbus-in-F29 != dbus-in-F30 now.
>

I’m talking about F30 recent change in which has been implemented switch to
dubs-broker.
Ps. If this change has been propagated to F29 (hopefully not) more things
will be screwed.

kloczek
-- 
-- 
Tomasz Kłoczko | Tel: 0774 1209067 | LinkedIn: *http://lnkd.in/FXPWxH
*
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Fedora rawhide compose report: 20181125.n.0 changes

2018-11-25 Thread Fedora Rawhide Report 
OLD: Fedora-Rawhide-20181123.n.1
NEW: Fedora-Rawhide-20181125.n.0

= SUMMARY =
Added images:2
Dropped images:  0
Added packages:  0
Dropped packages:0
Upgraded packages:   41
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   1.63 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   29.18 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Python_Classroom vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-Rawhide-20181125.n.0.x86_64.vagrant-libvirt.box
Image: Python_Classroom vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-Rawhide-20181125.n.0.x86_64.vagrant-virtualbox.box

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  authselect-1.0.2-1.fc30
Old package:  authselect-1.0.1-2.fc30
Summary:  Configures authentication and identity sources from supported 
profiles
RPMs: authselect authselect-compat authselect-devel authselect-libs
Size: 1.55 MiB
Size change:  297.98 KiB
Changelog:
  * Fri Nov 23 2018 Pavel B??ezina  - 1.0.2-1
  - Rebase to 1.0.2


Package:  bluebird-1.3-1.fc30
Old package:  bluebird-1.2-8.fc29
Summary:  A clean minimalistic theme for Xfce, GTK+ 2 and 3
RPMs: bluebird-gtk2-theme bluebird-gtk3-theme bluebird-metacity-theme 
bluebird-xfwm4-theme
Size: 223.68 KiB
Size change:  47.76 KiB
Changelog:
  * Sat Nov 24 2018 Miro Hron??ok  - 1.3-1
  - Update to 1.3, should work with recent GTK3


Package:  configsnap-0.16.1-1.fc30
Old package:  configsnap-0.14-1.fc29
Summary:  Record and compare system state
RPMs: configsnap
Size: 25.37 KiB
Size change:  2.23 KiB
Changelog:
  * Sat Sep 15 2018 Nick Rhodes  - 0.15-1
  - Added copy_dir function to recursively backup and diff directories
  - Add ability to use copy_dir in additional.conf along with a file pattern 
match

  * Wed Oct 17 2018 Nick Rhodes  - 0.16-1
  - Add --config option for specifying custom a configuration file

  * Sun Nov 04 2018 Nick Rhodes  - 0.16.1-1
  - Revert previous --config release with argparse rewrite
  - Add --config option for specifying custom a configuration file
  - Filter the "ip address show" output to remove lines containing valid_lft 
XXsec preferred_lft XXsec


Package:  cutecom-0.51.0-1.fc30
Old package:  cutecom-0.22.0-16.fc29
Summary:  A graphical serial terminal, like minicom or Hyperterminal on 
Windows
RPMs: cutecom
Size: 1.85 MiB
Size change:  1.53 MiB
Changelog:
  * Sat Nov 24 2018 Rich Mattes  - 0.51.0-1
  - Update to releas 0.51.0 (rhbz#1583195)
  - Add upstream appstream data (rhbz#1476499)


Package:  eccodes-2.9.2-1.fc30
Old package:  eccodes-2.9.0-1.fc30
Summary:  WMO data format decoding and encoding
RPMs: eccodes eccodes-data eccodes-devel eccodes-doc
Size: 5.88 MiB
Size change:  972 B
Changelog:
  * Sat Nov 24 2018 Jos de Kloe  - 2.9.2-1
  - Upgrade to upstream version 2.9.2


Package:  firefox-63.0.3-2.fc30
Old package:  firefox-63.0.3-1.fc30
Summary:  Mozilla Firefox Web browser
RPMs: firefox firefox-x11
Size: 517.49 MiB
Size change:  18.07 KiB
Changelog:
  * Wed Nov 21 2018 Martin Stransky  - 63.0.3-2
  - Fixed mozbz#1507475 - crash when display changes (rhbz#1646151).


Package:  flacon-5.0.0-1.fc30
Old package:  flacon-4.1.0-2.fc29
Summary:  Audio File Encoder
RPMs: flacon
Size: 7.16 MiB
Size change:  427.91 KiB
Changelog:
  * Sat Nov 24 2018 Ilya Gradina  - 5.0.0-1
  - Update to 5.0.0


Package:  fuse-overlayfs-0.1-6.dev.git3d48bf9.fc30
Old package:  fuse-overlayfs-0.1-5.dev.gitd40ac75.fc29
Summary:  FUSE overlay+shiftfs implementation for rootless containers
RPMs: fuse-overlayfs
Size: 273.71 KiB
Size change:  7.90 KiB
Changelog:
  * Fri Nov 23 2018 Giuseppe Scrivano  - 
0.1-6.dev.git3d48bf9
  - built commit 3d48bf9


Package:  glm-0.9.9.2-1.fc30
Old package:  glm-0.9.8.5-3.fc29
Summary:  C++ mathematics library for graphics programming
RPMs: glm-devel glm-doc
Size: 2.39 MiB
Size change:  509.73 KiB
Changelog:
  * Thu Oct 11 2018 Joonas Saraj??rvi  - 0.9.9.2-1
  - Update to upstream GLM version 0.9.9.2


Package:  hokuyoaist-3.0.2-24.fc30
Old package:  hokuyoaist-3.0.2-22.fc28
Summary:  Hokuyo Laser SCIP driver
RPMs: hokuyoaist hokuyoaist-devel python3-hokuyoaist
Added RPMs:   python3-hokuyoaist
Dropped RPMs: python2-hokuyoaist
Size: 8.20 MiB
Size change:  -30.21 KiB
Changelog:
  * Fri Jul 13 2018 Fedora Release Engineering  - 
3.0.2-23
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild

  * Sat Nov 24 2018 Rich Mattes  - 3.0.2-24
  - Fix FTBFS (rhbz#1604332)
  - Remove python2 package (rhbz#1634623)
  - Enable upstream python3 support

Fedora Rawhide-20181125.n.0 compose check report

2018-11-25 Thread Fedora compose checker 
No missing expected images.

Failed openQA tests: 15/142 (x86_64), 4/24 (i386), 1/2 (arm)

New failures (same test did not fail in Rawhide-20181123.n.1):

ID: 311779  Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/311779
ID: 311780  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/311780
ID: 311804  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/311804
ID: 311854  Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/311854
ID: 311856  Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/311856
ID: 311906  Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/311906
ID: 311924  Test: x86_64 universal install_kickstart_firewall_configured
URL: https://openqa.fedoraproject.org/tests/311924

Old failures (same test failed in Rawhide-20181123.n.1):

ID: 311805  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/311805
ID: 311812  Test: x86_64 Workstation-live-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/311812
ID: 311822  Test: x86_64 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/311822
ID: 311823  Test: x86_64 Workstation-boot-iso memory_check@uefi
URL: https://openqa.fedoraproject.org/tests/311823
ID: 311827  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/311827
ID: 311832  Test: x86_64 KDE-live-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/311832
ID: 311842  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/311842
ID: 311850  Test: x86_64 Silverblue-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/311850
ID: 311907  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/311907
ID: 311914  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/311914
ID: 311921  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/311921
ID: 311922  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/311922
ID: 311943  Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/311943

Soft failed openQA tests: 63/142 (x86_64), 16/24 (i386)
(Tests completed, but using a workaround for a known bug)

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

ID: 311777  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/311777
ID: 311778  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/311778
ID: 311806  Test: x86_64 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/311806
ID: 311807  Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/311807
ID: 311808  Test: i386 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/311808
ID: 311825  Test: i386 Workstation-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/311825
ID: 311828  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/311828
ID: 311860  Test: x86_64 universal install_mirrorlist_graphical
URL: https://openqa.fedoraproject.org/tests/311860
ID: 311865  Test: x86_64 universal install_kickstart_user_creation
URL: https://openqa.fedoraproject.org/tests/311865
ID: 311923  Test: x86_64 universal install_kickstart_firewall_disabled
URL: https://openqa.fedoraproject.org/tests/311923
ID: 311925  Test: x86_64 universal install_kickstart_nfs
URL: https://openqa.fedoraproject.org/tests/311925

Old soft failures (same test soft failed in Rawhide-20181123.n.1):

ID: 311787  Test: x86_64 Server-dvd-iso install_repository_nfs_variation
URL: https://openqa.fedoraproject.org/tests/311787
ID: 311788  Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/311788
ID: 311800  Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/311800
ID: 311844  Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/311844
ID: 311845  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/311845
ID: 311855  Test: x86_64 universal install_package_set_minimal
URL: https://openqa.fedoraproject.org/tests/311855
ID: 311858  Test: x86_64 universal install_repository_http_variation
URL: https://openqa.fedoraproject.org/tests/311858
ID: 311859  Test: x86_64

How much is dnf's minimum memory requirement?

2018-11-25 Thread Benjamin Kircher 
What are dnf’s minimum memory requirements? It came as a surprise to me that a 
simple `dnf check-update` is getting OOM’ed by the kernel on a (ok, fairly 
small) 512MB VM.


[root@node ~]# dnf check-update
Killed

[root@node ~]# free -h
  totalusedfree  shared  buff/cache   available
Mem:  480Mi   137Mi   292Mi   0.0Ki50Mi   329Mi
Swap:0B  0B  0B

[root@node ~]# cat /etc/os-release |grep -i pretty_name
PRETTY_NAME="Fedora 29 (Server Edition)”

[root@node ~]# dnf --version
4.0.4
  Installed: dnf-0:4.0.4-1.fc29.noarch at Tue 30 Oct 2018 03:38:30 PM GMT
  Built: Fedora Project at Mon 15 Oct 2018 12:00:52 PM GMT

  Installed: rpm-0:4.14.2-1.fc29.x86_64 at Tue 30 Oct 2018 03:37:40 PM GMT
  Built: Fedora Project at Wed 22 Aug 2018 08:07:47 AM GMT


According to [1], 1GB is required for a Fedora (desktop?) install but right 
underneath is a note that says only if I want to install it with lots of 
packages selected upfront.


With F28 Server (ships with dnf 2.7.5) this worked perfectly fine on an equally 
sized VM.

Anyway, is memory consumption a thing with the new libdnf-in-C++ efforts? Could 
a look into microdnf be a thing for me?

Any advice appreciated.


[1]: 
https://docs.fedoraproject.org/en-US/fedora/f29/release-notes/welcome/Hardware_Overview/

BK
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: How much is dnf's minimum memory requirement?

2018-11-25 Thread Peter Robinson 
On Sun, Nov 25, 2018 at 4:54 PM Benjamin Kircher
 wrote:
>
> What are dnf’s minimum memory requirements? It came as a surprise to me that 
> a simple `dnf check-update` is getting OOM’ed by the kernel on a (ok, fairly 
> small) 512MB VM.
>
>
> [root@node ~]# dnf check-update
> Killed
>
> [root@node ~]# free -h
>   totalusedfree  shared  buff/cache   
> available
> Mem:  480Mi   137Mi   292Mi   0.0Ki50Mi   
> 329Mi
> Swap:0B  0B  0B
>
> [root@node ~]# cat /etc/os-release |grep -i pretty_name
> PRETTY_NAME="Fedora 29 (Server Edition)”
>
> [root@node ~]# dnf --version
> 4.0.4
>   Installed: dnf-0:4.0.4-1.fc29.noarch at Tue 30 Oct 2018 03:38:30 PM GMT
>   Built: Fedora Project at Mon 15 Oct 2018 12:00:52 PM GMT
>
>   Installed: rpm-0:4.14.2-1.fc29.x86_64 at Tue 30 Oct 2018 03:37:40 PM GMT
>   Built: Fedora Project at Wed 22 Aug 2018 08:07:47 AM GMT
>
>
> According to [1], 1GB is required for a Fedora (desktop?) install but right 
> underneath is a note that says only if I want to install it with lots of 
> packages selected upfront.
>
>
> With F28 Server (ships with dnf 2.7.5) this worked perfectly fine on an 
> equally sized VM.
>
> Anyway, is memory consumption a thing with the new libdnf-in-C++ efforts? 
> Could a look into microdnf be a thing for me?
>
> Any advice appreciated.

I've not seen issues with it running on ARM devices with 512 Mb of
RAM, and there are some that run it on devices with 256Mb but that
tends to be a minimal image with no graphics
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Test-Announce] Proposal to CANCEL: 2018-11-26 Fedora QA Meeting

2018-11-25 Thread Adam Williamson 
Hi folks! I'm proposing we cancel the QA meeting tomorrow. We met the
last two weeks and I don't see anything urgent to discuss, so let's
take the time off.

If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Update a package with new upstream release

2018-11-25 Thread Alain Vigne 
Upstream releases a new version.
I changed the .spec file, generate a srpm file, then perform again

$ fedpgk import 

This creates a tar.gz file in my git dir, and I did commit this file.
https://src.fedoraproject.org/rpms/pcb-rnd/blob/master/f/pcb-rnd-2.1.0.tar.gz

I think this is wrong, so:
1. Can I git delete / push   this tar.gz file ? Other action ?
2. It is not a fedpkg import command to use ? fedpkg new-sources ? How ?
3. Is there a documentation related to these maintenance actions ?

Thanks for your help.
-- 
Alain V.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Update a package with new upstream release

2018-11-25 Thread Alexander Ploumistos 
Hi Alain,

I believe these two documents should come in handy:
https://fedoraproject.org/wiki/Package_maintenance_guide
https://fedoraproject.org/wiki/Package_update_HOWTO
(the second one is mostly about the update process)

Source packages are not part of the "usual" git transactions, they are
modified with "fedpkg sources" and "fedpkg new-sources" commands and
uploaded to the lookaside cache. The "sources" file in your git folder
points to the current source package for the branch you are working
on. If you've messed up the source packages, a "fedpkg new-sources
" should set things straight.

Best regards,
Alex
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Update a package with new upstream release

2018-11-25 Thread Alain Vigne 
Thanks a lot Alex

So, "old wiki" is still relevant...
I was searching in
https://docs.fedoraproject.org/en-US/packaging-guidelines/


On Sun, Nov 25, 2018 at 7:47 PM Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:

> Hi Alain,
>
> I believe these two documents should come in handy:
> https://fedoraproject.org/wiki/Package_maintenance_guide
> https://fedoraproject.org/wiki/Package_update_HOWTO
> (the second one is mostly about the update process)
>
> Source packages are not part of the "usual" git transactions, they are
> modified with "fedpkg sources" and "fedpkg new-sources" commands and
> uploaded to the lookaside cache. The "sources" file in your git folder
> points to the current source package for the branch you are working
> on. If you've messed up the source packages, a "fedpkg new-sources
> " should set things straight.
>
> Best regards,
> Alex
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


-- 
Alain V.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Last dbus upgrade issues

2018-11-25 Thread Tomasz Kłoczko 
On Sun, 25 Nov 2018 at 11:35, Tomasz Kłoczko  wrote:
[..]
> I’m talking about F30 recent change in which has been implemented switch to 
> dubs-broker.
> Ps. If this change has been propagated to F29 (hopefully not) more things 
> will be screwed.

Seems I found what caused the issue.
I've been doing upgrade (only) dbus packages using rpm and for some
reason after all old dbus-daemon has been killed and deactivated and
at the same time dbus-broker has not been started.
Instant effect was very strange. For example I was unable to unpack
any archives with files owned by group/user not present in my system
because NSS seems now depends on dbus as well. After next few minutes
Gnome GUI crashed,

if [ $1 -eq 1 ] ; then
systemctl --no-reload disable dbus-daemon.service
systemctl --no-reload --global disable dbus-daemon.service
systemctl --no-reload enable dbus-broker.service
systemctl --no-reload --global enable dbus-broker.service
fi

This dbus-broker %post scriplet seems is only swapping started
services but does not stops dbus-daemon and starts dbus-broker if
dbus-daemon is already runimg.
At the same time because in spec file is missing uninstall dbus-daemon
by missing "Obsoletes: dbus-daemon" below

%triggerpostun -- dbus-daemon
systemctl --no-reload preset dbus-broker.service
systemctl --no-reload --global preset dbus-broker.service

has not been activated as well. IMO implementing whole transition with
leaving both old and new packages installed seems is wrong.

Solution: login after all in single mode and execute "systemctl enable
dbus-broker" than reboot.
Other problem is that dnf and rpm are executing batch of packages
scriplets not the same order with other operations. Breaking rpm
semantics by dnf is kind of asking for troubles.

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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Last dbus upgrade issues

2018-11-25 Thread David Herrmann 
Hi

On Sun, Nov 25, 2018 at 10:53 PM Tomasz Kłoczko
 wrote:
>
> On Sun, 25 Nov 2018 at 11:35, Tomasz Kłoczko  wrote:
> [..]
> > I’m talking about F30 recent change in which has been implemented switch to 
> > dubs-broker.
> > Ps. If this change has been propagated to F29 (hopefully not) more things 
> > will be screwed.
>
> Seems I found what caused the issue.
> I've been doing upgrade (only) dbus packages using rpm and for some
> reason after all old dbus-daemon has been killed and deactivated and
> at the same time dbus-broker has not been started.
> Instant effect was very strange. For example I was unable to unpack
> any archives with files owned by group/user not present in my system
> because NSS seems now depends on dbus as well. After next few minutes
> Gnome GUI crashed,
>
> if [ $1 -eq 1 ] ; then
> systemctl --no-reload disable dbus-daemon.service
> systemctl --no-reload --global disable dbus-daemon.service
> systemctl --no-reload enable dbus-broker.service
> systemctl --no-reload --global enable dbus-broker.service
> fi
>
> This dbus-broker %post scriplet seems is only swapping started
> services but does not stops dbus-daemon and starts dbus-broker if
> dbus-daemon is already runimg.

You cannot stop dbus-daemon on a running system. This would tear down
everything. The package upgrade needs a reboot.

> At the same time because in spec file is missing uninstall dbus-daemon
> by missing "Obsoletes: dbus-daemon" below

Uninstalling dbus-daemon would break a running system, because it
would stop the system bus. Furthermore, other packages still depend on
tools provided by the old dbus-package. Can you elaborate why it is
harmful to keep dbus-daemon around? We made sure you can manually
remove it, unless other packages explicitly depend on the dbus-daemon
binary for private buses.

> %triggerpostun -- dbus-daemon
> systemctl --no-reload preset dbus-broker.service
> systemctl --no-reload --global preset dbus-broker.service
>
> has not been activated as well. IMO implementing whole transition with
> leaving both old and new packages installed seems is wrong.
>
> Solution: login after all in single mode and execute "systemctl enable
> dbus-broker" than reboot.

This surprises me. You are saying a simple reboot did not solve your
issues? The `enable` line is executed during upgrade, but you are
saying on your system dbus-broker was not enabled after the upgrade?

> Other problem is that dnf and rpm are executing batch of packages
> scriplets not the same order with other operations. Breaking rpm
> semantics by dnf is kind of asking for troubles.

Thanks a lot for the report. We tested this upgrade with several
different setups (both dbus-daemon and broker installed/not installed
before the upgrade, etc.), and we didn't see this behavior. We are
aware that this update needs a reboot to fully work, but we made sure
it somewhat works even if you don't reboot. For rawhide, there is
sadly no way to mark updates as "needs reboot".

Thanks
David
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Broken EPEL updates due to Centos 7.6 delay?

2018-11-25 Thread Christopher 
Anybody know what's going on with Centos 7.6-1810?
Some packages in EPEL depend on it, but it is apparently not yet available.
This discrepancy is breaking yum updates for me.

For example, xorgxrdp-0.2.8-3.el7 depends on xorg-x11-server-Xorg
1.20.1, which isn't yet available (rather, available on in the cr
repo, not in CentOS updates yet).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org