Re: Mounting a Samsung S5 phone for reading

[Peter Robinson]

On Thu, Sep 24, 2015 at 9:06 PM, Les Howell  wrote:
> Hi, everyone...
> I have been trying for three days now to mount a galaxy phone to my F22
> system.
> Problems:  Phone does not mount.
> Things checked:
> 1.  Nautilus does not have the side pane any longer.  I really
> miss that because my file structure is very diverse.
> 2.  /run/users/1000 never reflects my phone.
> 3.  Added simple-gvfs to no effect.
> 4.  searched for and added libfuse-gvfs
> 5.  searched for and added 2 other gvfs bits (sorry I no 
> longer
> remember which ones.)
> 6.  Googled lots with no more success.
> 7.  Nautilus crashes sporadically, and specifically if I click
> on the menu button to change from list view to icon view or vice versa,
> depending on which view is open.
> 8.  .config/nautilus files are writable.
> 9.  Now I'm asking here.  HELP!!!
>
> BASE PROBLEM... Mount cellphone as a disk to retrieve files not working
> and I cannot find a solution.

Make sure you have gvfs-mtp installed. Some phones need you to unlock
them to be able to access the files (mine does), also often some
Android phones have different modes when you plug in a usb cable
(charge only, MTP, PTP etc) and put up a usb icon in the status bar
where if you select the option you want. In my case it doesn't appear
in nautilus until I've unlocked the phone and selected the mode.

Peter
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Peter Robinson]

>> >> > [trustedqsl]
>> >> >   tqsllib-devel-2.4-9.fc23.1.i686 requires tqsllib(x86-32) =
>> >> > 0:2.4-9.fc23
>> >> >   tqsllib-devel-2.4-9.fc23.1.x86_64 requires tqsllib(x86-64) =
>> >> > 0:2.4-9.fc23
>> >
>> >
>> > This is due to the fact that upstream puts both the application and library
>> > in the same source archive but they have different versions AND that no one
>> > reads the comments in the spec file which tells you to bump the library 
>> > rev.
>> > I was waiting for the rebuilds to stop before fixing, I guess it's time.
>>
>> Why does the app care about the RPM revisions, surely that should be a
>> dep on the exact version of the library alone.
>
> Well, it's a standard Base Package Requires adhering to the packaging 
> guidelines.

No it's not, the packaging guidelines are for a single src.rpm
package, where the NVR is bumped automatically across all sub packages
of the .src.rpm, this is two different src.rpm packages and hence it
doesn't apply as it is impossible to keep in sync. The Requires should
just be for the main version, not the revision here because the
upstream only cares about the actual upstream version for
compatibility not the RPM revision which in this case is irrelevant.

Peter
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[Les Howell]

On Thu, 2015-09-24 at 14:59 -0700, Samuel Sieb wrote:
> This isn't the right place to be asking this question.  The users
> list 
> or IRC would be better.
> 
> On 09/24/2015 02:35 PM, Les Howell wrote:
> > On Thu, 2015-09-24 at 14:07 -0700, Samuel Sieb wrote:
> > > 
> > > Check the logs when you plug in the phone.  Watch for lines from
> > > "org.gtk.vfs.Daemon".
> > > 
> Run "journalctl -f", then plug in the phone.
> 
> > > If you see the following lines, your phone probably isn't set
> > > correctly:
> > > Sep 21 11:15:18 laptop mtp-probe: checking bus 2, device 60:
> > > "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2"
> > > Sep 21 11:15:18 laptop mtp-probe: bus: 2, device: 60 was not an
> > > MTP
> > > device
> > > 
> 
> > In /run/user/ there are only two directories, 1000 (my own account)
> > and
> > 42 which is a restricted account, even to the admin.
> > 
> If it gets mounted, it will be in /run/user/1000/gvfs
> 
It doesn't mount.  The journalctl -f command returns:
[lesh@School ~]$ journalctl -f
Hint: You are currently not seeing messages from other users and the
system.
  Users in groups 'adm', 'systemd-journal', 'wheel' can see all
messages.
  Pass -q to turn off this notice.
-- Logs begin at Mon 2015-08-24 18:49:55 PDT. --
Sep 24 17:17:21 School gnome-session[1955]: (gnome-settings
-daemon:2045): housekeeping-plugin-WARNING **: Failed to enumerate
children of /var/tmp/systemd-private-1e24a58fb6354e86805625ec0244b5c1
-rtkit-daemon.service-2KRGCm: Permission denied
Sep 24 17:17:21 School gnome-session[1955]: (gnome-settings
-daemon:2045): housekeeping-plugin-WARNING **: Failed to enumerate
children of /var/tmp/systemd-private-eef5d74db59140bcbedab4f37124f999
-rtkit-daemon.service-WNT09F: Permission denied
Sep 24 17:17:21 School gnome-session[1955]: (gnome-settings
-daemon:2045): housekeeping-plugin-WARNING **: Failed to enumerate
children of /var/tmp/systemd-private-a4ac386bc4804e58835ebbfc6b13a800
-rtkit-daemon.service-LUkmdc: Permission denied
Sep 24 17:17:21 School gnome-session[1955]: (gnome-settings
-daemon:2045): housekeeping-plugin-WARNING **: Failed to enumerate
children of /var/tmp/systemd-private-4545288095fd4705b3043be036aefd1d
-colord.service-m7lERc: Permission denied
Sep 24 17:17:21 School gnome-session[1955]: (gnome-settings
-daemon:2045): housekeeping-plugin-WARNING **: Failed to enumerate
children of /var/tmp/systemd-private-4545288095fd4705b3043be036aefd1d
-rtkit-daemon.service-gr0mwq: Permission denied
Sep 24 17:17:21 School gnome-session[1955]: (gnome-settings
-daemon:2045): housekeeping-plugin-WARNING **: Failed to enumerate
children of /var/tmp/systemd-private-48551081d47f4c379ea91711a1d0
-rtkit-daemon.service-4Yu5G3: Permission denied
Sep 24 17:17:21 School gnome-session[1955]: (gnome-settings
-daemon:2045): housekeeping-plugin-WARNING **: Failed to enumerate
children of /var/tmp/systemd-private-291d3859d8894971942ad71e727e5f15
-rtkit-daemon.service-ibZoyq: Permission denied
Sep 24 17:43:37 School gnome-session[1955]: Gjs-Message: JS LOG:
loading default theme (Adwaita)
Sep 24 17:47:42 School /usr/libexec/gdm-x-session[1853]: Activating
service name='org.gnome.Terminal'
Sep 24 17:47:42 School /usr/libexec/gdm-x-session[1853]: Successfully
activated service 'org.gnome.Terminal'

And the reason I am asking here is that it appears that Ubuntu users
have it working.  So it appears that fedora 22 is the issue, or the
build of one or more parts of the gvfs stuff, or ???

Nautilus is also buggy, and doesn't reflect the phone or any file
systems because the sidebar which showed other file systems has
disappeared for some reason.  I don't know if that is related or not.

Regards,
Les H
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: llvm 3.7 for rawhide and then f23

[Luya Tshimbalanga]

On 21/09/15 03:00 AM, Kamil Paral wrote:
>> Given that we are now post-Beta for F23, it seems a little late in the
>> cycle to be introducing a new llvm runtime. Is it guaranteed to be
>> backwards-compatible?
> OTOH, having OpenGL 4 support in Fedora 23 (at least for certain cards) is a 
> strong marketing point. Personally I'm very much looking forward to finally 
> playing some of those modern games.
Yes. I couldn't resist upgrading to llvm 3.7 and mesa 11 from Fedora 23
on Fedora 22 for my AMD A10-7400P laptop and pleased to see running
smoothly with no sign of bug. From the report:

$ glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD KAVERI (DRM 2.42.0, LLVM 3.7.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.0.0
(git-c4bae57)
OpenGL core profile shading language version string: 4.10
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 11.0.0 (git-c4bae57)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.0 (git-c4bae57)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

-- 
Luya Tshimbalanga
Graphic & Web Designer
E: l...@fedoraproject.org
W: http://www.coolest-storm.net

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[Luya Tshimbalanga]

On 24/09/15 01:06 PM, Les Howell wrote:
> Hi, everyone...
> I have been trying for three days now to mount a galaxy phone to my F22
> system.  
>   Problems:  Phone does not mount.
>   Things checked:
>   1.  Nautilus does not have the side pane any longer.  I really
> miss that because my file structure is very diverse.
>   2.  /run/users/1000 never reflects my phone.
>   3.  Added simple-gvfs to no effect.
>   4.  searched for and added libfuse-gvfs
>   5.  searched for and added 2 other gvfs bits (sorry I no longer
> remember which ones.)
>   6.  Googled lots with no more success.
>   7.  Nautilus crashes sporadically, and specifically if I click
> on the menu button to change from list view to icon view or vice versa,
> depending on which view is open.
>   8.  .config/nautilus files are writable.
>   9.  Now I'm asking here.  HELP!!!
>
> BASE PROBLEM... Mount cellphone as a disk to retrieve files not working
> and I cannot find a solution.
>
> Regards,
> Les H
Hello Les,
I also have a Samsung Galaxy S5 mounted on Fedora 22 without issue
plugged on either both USB 2.0 and 3.0.
Few question to ask:
- Is your cable broken?
- Do you use the stock cable from your Galaxy S5?
- It sounds like you have a borked session so a clean reset may help.

-- 
Luya Tshimbalanga
Graphic & Web Designer
E: l...@fedoraproject.org
W: http://www.coolest-storm.net

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Michael Schwendt]

On Thu, 24 Sep 2015 04:05:26 +0100, Peter Robinson wrote:

> On Wed, Sep 23, 2015 at 4:31 PM, Richard Shaw wrote:
> > On Wed, Sep 23, 2015 at 7:00 AM, Vít Ondruch wrote:
> >>
> >> > [trustedqsl]
> >> >   tqsllib-devel-2.4-9.fc23.1.i686 requires tqsllib(x86-32) =
> >> > 0:2.4-9.fc23
> >> >   tqsllib-devel-2.4-9.fc23.1.x86_64 requires tqsllib(x86-64) =
> >> > 0:2.4-9.fc23
> >
> >
> > This is due to the fact that upstream puts both the application and library
> > in the same source archive but they have different versions AND that no one
> > reads the comments in the spec file which tells you to bump the library rev.
> > I was waiting for the rebuilds to stop before fixing, I guess it's time.
> 
> Why does the app care about the RPM revisions, surely that should be a
> dep on the exact version of the library alone.

Well, it's a standard Base Package Requires adhering to the packaging 
guidelines.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[kendell clark]

hi
I don't know if I can help you, but some android phones use mtp, so need
the gvfs-mtp package to mount. Nautilus does have teh side pane, all you
need to do is press f6 to access it. At least I think the side pane is
the list of places, home, videos, etc, right? If it's been disabled,
there's a way to enable it again. One of the menu buttons will pop up a
menu with a check box to re-enable the pane if you turned it off. If
this isn't enough help I'll dig further. You might also need the
android-tools and android-udev packages, though I'm not absolutely sure
they're necessary jsut to mount the phone.
Thanks
Kendell clark


On 09/24/2015 03:06 PM, Les Howell wrote:
> Hi, everyone...
> I have been trying for three days now to mount a galaxy phone to my F22
> system.  
>   Problems:  Phone does not mount.
>   Things checked:
>   1.  Nautilus does not have the side pane any longer.  I really
> miss that because my file structure is very diverse.
>   2.  /run/users/1000 never reflects my phone.
>   3.  Added simple-gvfs to no effect.
>   4.  searched for and added libfuse-gvfs
>   5.  searched for and added 2 other gvfs bits (sorry I no longer
> remember which ones.)
>   6.  Googled lots with no more success.
>   7.  Nautilus crashes sporadically, and specifically if I click
> on the menu button to change from list view to icon view or vice versa,
> depending on which view is open.
>   8.  .config/nautilus files are writable.
>   9.  Now I'm asking here.  HELP!!!
> 
> BASE PROBLEM... Mount cellphone as a disk to retrieve files not working
> and I cannot find a solution.
> 
> Regards,
> Les H
> 
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Björn Persson]

Kalev Lember wrote:
> aws landgraf

Here's a patch to include the missing library that prevents installation
of aws-tools.

To get it to build I had to disable PDF generation and build only HTML
documents. There is a PDF file in the latest built package so it must
have worked before, but currently it seems to be broken. I don't know
enough about Texlive to solve it quickly.

Björn Persson
From 893d0db744f4ddbe9c6d686f6a4337b5fdba5e98 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Persson?= 
Date: Thu, 24 Sep 2015 23:52:08 +0200
Subject: [PATCH] Make aws-tools installable.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

· Added a quick fix to package libaws_ssl.so.
· Disabled PDF generation as it doesn't currently work.
---
 aws.spec | 12 ++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/aws.spec b/aws.spec
index e7eb04a..4b58a2e 100644
--- a/aws.spec
+++ b/aws.spec
@@ -3,7 +3,7 @@
 %global with_gps 0
 Name:   aws 
 Version:2015
-Release:2%{?dist}
+Release:3%{?dist}
 Summary:Ada Web Server
 
 Group:  System Environment/Libraries
@@ -87,12 +87,15 @@ rm -rf include/zlib*
 %build
 make setup DEFAULT_LIBRARY_TYPE=relocatable ENABLE_SHARED=true GPRBUILD="gprbuild %GPRbuild_optflags"
 make LIBRARY_TYPE=relocatable GPRBUILD="gprbuild %GPRbuild_optflags"
-make build-doc
+# PDF generation seems to be broken so generate only HTML documents.
+make -C docs html
 
 
 %install
 make install DESTDIR=%{buildroot}  I_GPR="%_GNAT_project_dir"  \
 I_LIB=%{buildroot}%{_libdir} prefix=%{_prefix}
+# Add the missing libaws_ssl.so that the tools are linked to.
+cp .build/*/debug/relocatable/lib/ssl/libaws_ssl.so %{buildroot}%{_libdir}/
 ##install_man_pages:
 mkdir -p %{buildroot}/%{_mandir}/man1/
 for i in `ls *.1`; do gzip -c $i >> %{buildroot}/%{_mandir}/man1/$i.gz; done
@@ -113,6 +116,7 @@ rm -rf %{buildroot}/%{_datadir}/gps
 %dir %{_libdir}/%{name}
 %{_libdir}/lib%{name}-%{version}.so
 %{_libdir}/%{name}/lib%{name}-%{version}.so
+%{_libdir}/lib%{name}_ssl.so
 
 
 %files devel
@@ -135,6 +139,10 @@ rm -rf %{buildroot}/%{_datadir}/gps
 
 
 %changelog
+* Thu Sep 24 2015 Björn Persson  - 2015-3
+- Added the missing libaws_ssl.so.
+- Disabled PDF generation as it doesn't currently work.
+
 * Fri Jun 26 2015 Pavel Zhukov  - 2015-2
 - Remove references to gnutls rsa_params as deprecated 
 
-- 
2.1.0



pgpyezu6Aax8z.pgp
Description: OpenPGP digital signatur
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[Samuel Sieb]

This isn't the right place to be asking this question.  The users list 
or IRC would be better.


On 09/24/2015 02:35 PM, Les Howell wrote:

On Thu, 2015-09-24 at 14:07 -0700, Samuel Sieb wrote:


Check the logs when you plug in the phone.  Watch for lines from
"org.gtk.vfs.Daemon".


Run "journalctl -f", then plug in the phone.


If you see the following lines, your phone probably isn't set
correctly:
Sep 21 11:15:18 laptop mtp-probe: checking bus 2, device 60:
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2"
Sep 21 11:15:18 laptop mtp-probe: bus: 2, device: 60 was not an MTP
device




In /run/user/ there are only two directories, 1000 (my own account) and
42 which is a restricted account, even to the admin.


If it gets mounted, it will be in /run/user/1000/gvfs

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[Les Howell]

On Thu, 2015-09-24 at 14:07 -0700, Samuel Sieb wrote:
> On 09/24/2015 01:39 PM, Adam Williamson wrote:
> > Some newer cellphones aren't actually capable of acting as USB mass
> > storage devices, they only support sync in a couple of other modes.
> > MTP
> > should work in Nautilus, but will not be visible in a terminal. Try
> > setting the phone to MTP mode, then looking for it in Nautilus'
> > sidebar.
> > 
> I think almost all recent (Android) phones don't do mass storage now.
> My LG phone offers, MTP, PTP, and just charge.
> 
> Make sure you have the necessary mtp packages installed:
> # rpm -qa | grep mtp
> gvfs-mtp-1.24.2-1.fc22.x86_64
> libmtp-1.1.9-1.fc22.x86_64
> 
> Check the logs when you plug in the phone.  Watch for lines from 
> "org.gtk.vfs.Daemon".
> 
> If you see the following lines, your phone probably isn't set
> correctly:
> Sep 21 11:15:18 laptop mtp-probe: checking bus 2, device 60: 
> "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2"
> Sep 21 11:15:18 laptop mtp-probe: bus: 2, device: 60 was not an MTP
> device
> 
The files in the rpm qa command appear correct.

In the Anaconda log I see the daemon starting, the daemon successfully
started.  I did not find org.gtk.vfs.Daemon in any other logs, using
grep.

In /run/user/ there are only two directories, 1000 (my own account) and
42 which is a restricted account, even to the admin.

Regards,
Les H


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[Samuel Sieb]

On 09/24/2015 01:39 PM, Adam Williamson wrote:

Some newer cellphones aren't actually capable of acting as USB mass
storage devices, they only support sync in a couple of other modes. MTP
should work in Nautilus, but will not be visible in a terminal. Try
setting the phone to MTP mode, then looking for it in Nautilus'
sidebar.

I think almost all recent (Android) phones don't do mass storage now. 
My LG phone offers, MTP, PTP, and just charge.


Make sure you have the necessary mtp packages installed:
# rpm -qa | grep mtp
gvfs-mtp-1.24.2-1.fc22.x86_64
libmtp-1.1.9-1.fc22.x86_64

Check the logs when you plug in the phone.  Watch for lines from 
"org.gtk.vfs.Daemon".


If you see the following lines, your phone probably isn't set correctly:
Sep 21 11:15:18 laptop mtp-probe: checking bus 2, device 60: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2"

Sep 21 11:15:18 laptop mtp-probe: bus: 2, device: 60 was not an MTP device

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[Matthew Miller]

On Thu, Sep 24, 2015 at 01:39:04PM -0700, Adam Williamson wrote:
> Some newer cellphones aren't actually capable of acting as USB mass
> storage devices, they only support sync in a couple of other modes. MTP
> should work in Nautilus, but will not be visible in a terminal. Try
> setting the phone to MTP mode, then looking for it in Nautilus'
> sidebar.

In the terminal, look under /run/user/$USER/gvfs.

-- 
Matthew Miller

Fedora Project Leader
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Harald Hoyer]

Am 21.09.2015 um 11:07 schrieb Matthew Miller:
> Fedora-Cloud-Base-20141203-21.x86_64.qcow2:   151M  
> Fedora-Cloud-Base-23_Beta-20150915.x86_64.qcow2:  275M
> 
> In just one year — 82% more awesome? 
> 
> I'd really like this to stay below 200MB as a competitive threshold.
> Or, if we're going to be bigger than that, be bigger for REASONS, not
> just accretion.
> 
> tl;dr: grub2 is a lot to blame, but there seem to be some new
> questionable dep chains from systemd, and general dep growth across the
> board.
> 
> 
> Disk use at first boot:
> 
>   [f21]$ df -h  /
>   Filesystem  Size  Used Avail Use% Mounted on
>   /dev/vda120G  359M   19G   2% /
> 
>   [f23b]$ df -h  /
>   Filesystem  Size  Used Avail Use% Mounted on
>   /dev/vda120G  578M   19G   4% /
> 
> RPMs installed:
> 
>   [f21]$ rpm -qa | wc -l
>   226
> 
>   [f23b]$ rpm -qa | wc -l
>   264
> 
> Top 20 rpms by reported size:
> 
>   $ rpm -qa --qf '%{size} %{name}\n'|sort -nr|head -20
>   120417342 glibc-common
>   42307839 kernel-core
>   25000497 python-libs
>   22438155 systemd
>   14623272 coreutils
>   14000291 glibc
>   11282056 ruby-libs  # hey, at least we lost this
>   10845519 glib2
>   10593004 selinux-policy-targeted
>   9389116 cracklib-dicts  # https://bugzilla.redhat.com/show_bug.cgi?id=865521
>   9078043 python-boto
>   8792531 util-linux
>   7084188 bash
>   6669884 gnupg2
>   5844544 yum
>   4893790 policycoreutils
>   3786564 file-libs
>   3540004 shadow-utils
>   3458312 groff-base  # who doesn't love groff?
>   2997717 tar
> 
> 
>   $ rpm -qa --qf '%{size} %{name}\n'|sort -nr|head -20
>   125195206 glibc-common
>   86298752 linux-firmware   # sadface, but hard
>   53291365 kernel-core
>   36004297 grub2-tools  # this is ridiculous
>   28453336 python3-libs # 13% growth
>   27233273 systemd  # 21% growth
>   16648994 grub2# *sigh*
>   14486819 glibc
>   14287847 coreutils# this package got _smaller!_
>   11143743 glib2
>   11129880 selinux-policy-targeted
>   9389116 cracklib-dicts
>   9261499 python3-boto
>   9237998 util-linux
>   9224255 fedora-logos  # this is also grub's fault.
>   7517574 gnupg2
>   7143418 bash
>   6574678 python3-pip   # :(
>   583 hwdata# this is ALSO grub's fault
>   5423400 xkeyboard-config  # really looks like a systemd dep chain
>   involving plymouth
> 
> Okay, let's look on disk:
> 
> 
>   [f21]$ sudo du -sh * 2>/dev/null|sort -h
>   [...]
>   36K home
>   40K root
>   228Krun
>   21M boot
>   22M etc
>   34M var
>   276Musr
> 
> 
>   [f23b]$ sudo du -sh * 2>/dev/null|sort -h
>   [...]
>   40K root
>   264Krun
>   16M etc
>   45M boot  # ugh
>   171Mvar   # oww
>   463Musr   # oww oww oww
> 
>   Breakdown:
>  
>- boot is mostly grub, but initramfs is also doubled

you probably don't need lvm, raid and all that stuff in the initramfs.. Also
maybe not network and a rescue initramfs?

Is dracut-network and dracut-config-generic in the install set? If yes, remove 
it.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Mounting a Samsung S5 phone for reading

[Adam Williamson]

On Thu, 2015-09-24 at 13:06 -0700, Les Howell wrote:
> Hi, everyone...
> I have been trying for three days now to mount a galaxy phone to my
> F22
> system.  
>   Problems:  Phone does not mount.
>   Things checked:
>   1.  Nautilus does not have the side pane any longer.  I
> really
> miss that because my file structure is very diverse.
>   2.  /run/users/1000 never reflects my phone.
>   3.  Added simple-gvfs to no effect.
>   4.  searched for and added libfuse-gvfs
>   5.  searched for and added 2 other gvfs bits (sorry I
> no longer
> remember which ones.)
>   6.  Googled lots with no more success.
>   7.  Nautilus crashes sporadically, and specifically if
> I click
> on the menu button to change from list view to icon view or vice
> versa,
> depending on which view is open.
>   8.  .config/nautilus files are writable.
>   9.  Now I'm asking here.  HELP!!!
> 
> BASE PROBLEM... Mount cellphone as a disk to retrieve files not
> working
> and I cannot find a solution.

Some newer cellphones aren't actually capable of acting as USB mass
storage devices, they only support sync in a couple of other modes. MTP
should work in Nautilus, but will not be visible in a terminal. Try
setting the phone to MTP mode, then looking for it in Nautilus'
sidebar.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Fedora 23 Branched 20150924 compose check report

[Fedora compose checker]

No missing expected images.

Images in this compose but not 23 Branched 20150923:

Cloud disk raw i386
Cloud_atomic disk raw x86_64
Generic boot x86_64
Cloud disk qcow x86_64
Cloud docker x86_64
Generic boot i386
Cloud vagrant libvirt x86_64
Cloud vagrant virtualbox x86_64
Cloud_atomic disk qcow x86_64
Cloud disk raw x86_64
Cloud_atomic vagrant virtualbox x86_64
Cloud disk qcow i386
Cloud_atomic vagrant libvirt x86_64

No images in 23 Branched 20150923 but not this.

Failed openQA tests: 7 of 52

ID: 3443Test: x86_64 kde_live default_install
ID: 3442Test: i386 kde_live default_install
ID: 3437Test: i386 universal upgrade_desktop_32bit
ID: 3422Test: x86_64 universal server_simple_free_space@uefi
ID: 3420Test: x86_64 universal server_delete_partial@uefi
ID: 3413Test: x86_64 universal upgrade_desktop_64bit
ID: 3412Test: x86_64 universal upgrade_minimal_64bit

Passed openQA tests: 45 of 52
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Mounting a Samsung S5 phone for reading

[Les Howell]

Hi, everyone...
I have been trying for three days now to mount a galaxy phone to my F22
system.  
Problems:  Phone does not mount.
Things checked:
1.  Nautilus does not have the side pane any longer.  I really
miss that because my file structure is very diverse.
2.  /run/users/1000 never reflects my phone.
3.  Added simple-gvfs to no effect.
4.  searched for and added libfuse-gvfs
5.  searched for and added 2 other gvfs bits (sorry I no longer
remember which ones.)
6.  Googled lots with no more success.
7.  Nautilus crashes sporadically, and specifically if I click
on the menu button to change from list view to icon view or vice versa,
depending on which view is open.
8.  .config/nautilus files are writable.
9.  Now I'm asking here.  HELP!!!

BASE PROBLEM... Mount cellphone as a disk to retrieve files not working
and I cannot find a solution.

Regards,
Les H
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 Branched 20150923 compose check report

[Kevin Fenzi]

On Thu, 24 Sep 2015 01:38:56 -0700
Adam Williamson  wrote:

> On Wed, 2015-09-23 at 10:25 -0400, Fedora compose checker wrote:
> > Missing expected images:
> > 
> > Cloud disk raw i386
> > Cloud disk raw x86_64
> > Cloud_atomic disk raw x86_64
> > Generic boot i386
> > Generic boot x86_64
> 
> https://kojipkgs.fedoraproject.org/mash/branched-20150923/logs/pungify-x86_64.log
> 
> 2015-09-23 11:10:47,017:   dnf.exceptions.DepsolveError: nothing
> provides xserver-abi(videodrv-19) >= 0 needed by
> tigervnc-server-module-1.5.0-2.fc23.x86_64
> dnf.exceptions.DepsolveError: nothing provides
> xserver-abi(videodrv-19) >= 0 needed by
> tigervnc-server-module-1.5.0-2.fc23.x86_64

https://bodhi.fedoraproject.org/updates/FEDORA-2015-16415

fixes this and should be in tomorrow's compose. 

kevin


pgpxhKughPusz.pgp
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Fedora Rawhide 20150924 compose check report

[Fedora compose checker]

No missing expected images.

Images in this compose but not Rawhide 20150923:

Xfce disk raw armhfp
Cloud docker x86_64
Games live x86_64
Games live i386

No images in Rawhide 20150923 but not this.
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Applications missing from Fedora 23

[Zbigniew Jędrzejewski-Szmek]

On Fri, Sep 18, 2015 at 11:28:44AM +0100, Richard Hughes wrote:
> postbooks: specified icon '/usr/share/postbooks/images/icon128x32.png'
> does not exist
The png is in the rpm... What's going on here?

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[gil]

hi
svnkit is only used for generate ${scmBranch}. should be easily removed 
from dependencies

regards
gil

Il 24/09/2015 19:12, Christopher ha scritto:

mimepull (maintained by: goldmann, gil)
mimepull-1.9.5-2.fc23.src requires 
mvn(org.tmatesoft.svnkit:svnkit) = 1.8.5


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: virtual provides/metapackage for various OpenCL implementations

[Dominik 'Rathann' Mierzejewski]

On Thursday, 24 September 2015 at 14:44, Fabian Deutsch wrote:
> On Thu, Sep 24, 2015 at 12:21 PM, Dominik 'Rathann' Mierzejewski
>  wrote:
> > Dear maintainers,
> > I've just enabled OpenCL support in the gromacs package[1] and would
> > like to express a weak dependency on an OpenCL implementation, but I
> > have no way of doing so at the moment.
> >
> > We have three packages which provide OpenCL implementations:
> > beignet - Intel GPUs
> > mesa-libOpenCL - AMD GPUs (only?)
> > pocl - CPU-based
> >
> > Would it make sense to add a virtual provide to each of the packages
> > to mean the all provide a "vendor" OpenCL implementation? For example,
> > Provides: opencl-driver
> >
> > Then, any package that makes use of OpenCL could add
> > Requires/Recommends/Suggests: opencl-driver
> >
> > Another approach could be to create a meta package (named
> > opencl-drivers, for example - similar to xorg-x11-drivers) which would
> > depend on all vendor-specific implementations.
> >
> > I guess the second approach is more fool-proof. Comments?
> 
> yes - when we initially create the packages we actually already
> discussed how to achieve this.
> 
> I'd favor the second (meta-package) approach, nothing should go wrong
> if all three are installed.

Ok, thanks for your feedback.

> I'd go even further and create an opencl package (or group?) to
> install all kind of opencl packages, i.e. clinfo is a good thing to
> start with.

opencl-filesystem and opencl-headers could be merged, but opencl-utils
comes from a separate upstream (and bundles some OpenCL 1.0 headers[2]),
so it must be packaged separately.

Regards,
Dominik

[1] 
http://pkgs.fedoraproject.org/cgit/gromacs.git/commit/?id=dbabc099d66902daa094478024a8a331822b78bc
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1266184
-- 
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

limb changed ppisar's 'approveacls' permission on perl-Algorithm-Diff-XS (master) to 'Approved'

[notifications]

limb changed ppisar's 'approveacls' permission on perl-Algorithm-Diff-XS 
(master) to 'Approved'
https://admin.fedoraproject.org/pkgdb/package/perl-Algorithm-Diff-XS/
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Re: Removing packages that have broken dependencies in F23 tree

[Peter Robinson]

On Thu, Sep 24, 2015 at 6:20 PM, Mikolaj Izdebski  wrote:
> On 09/24/2015 07:12 PM, Christopher wrote:
>> I don't really understand what's going on with the netbeans-platform
>> package, or why accumulo would be affected. Upstream accumulo doesn't have
>> any dependencies on netbeans. Before I try to dive in and figure out what's
>> breaking, does anybody have any insight into what's going on with this, and
>> what it's providing that is breaking so many java packages?
>
> Accumulo depends on Hadoop, which is not installable in F23+:
> https://bugzilla.redhat.com/show_bug.cgi?id=1196209

It's been fixed in both F-23 and rawhide:
http://koji.fedoraproject.org/koji/buildinfo?buildID=684601
http://koji.fedoraproject.org/koji/buildinfo?buildID=684583

So Accumulo should be fixable now
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Aleksandar Kurtakov]

IIRC, sqljet needs netbeans-platform (swing-smth to be precious from netbeans) 
for its db browser UI which is a subpackage so disabling this part to build 
(and killing the browser subpackage) should remove the need for netbeans 
platform

Alexander Kurtakov
Red Hat Eclipse team

- Original Message -
> From: "Stephen John Smoogen" 
> To: "Development discussions related to Fedora" 
> 
> Sent: Thursday, 24 September, 2015 8:20:17 PM
> Subject: Re: Removing packages that have broken dependencies in F23 tree
> 
> On 24 September 2015 at 11:12, Christopher 
> wrote:
> > I don't really understand what's going on with the netbeans-platform
> > package, or why accumulo would be affected. Upstream accumulo doesn't have
> > any dependencies on netbeans. Before I try to dive in and figure out what's
> > breaking, does anybody have any insight into what's going on with this, and
> > what it's providing that is breaking so many java packages?
> >
> 
> I am probably misunderstanding your question, but from what I can see
> is that we have a build chain break.
> 
> It is a build chain break. netbeans-platfrom is used to build tool A
> which is used to build B .. and so accumulo can't be properly rebuilt
> because that package chain isn't complete. The chain looks to be
> coming from maven (mvn?) build requirements. If someone fixes either
> netbeans-platform or sqljet not to rely on it, then all the items look
> like they would then fix themselves.
> 
> The fix is either get sqljt
> 
> >> Depending on: netbeans-platform (33)
> >> sqljet (maintained by: olea, filiperosset)
> >> sqljet-1.1.10-4.fc23.src requires netbeans-platform =
> >> 1:7.0.1-11.fc22
> >> sqljet-browser-1.1.10-4.fc23.noarch requires
> >> netbeans-platform = 1:7.0.1-11.fc22
> >>
> >> OmegaT (maintained by: olea, mtasaka)
> >> OmegaT-2.6.3-2.fc22.i686 requires sqljet = 1.1.10-4.fc23
> >> OmegaT-2.6.3-2.fc22.src requires sqljet = 1.1.10-4.fc23
> >>
> >> svnkit (maintained by: olea, akurtakov, dbhole, jfilak)
> >> svnkit-1.8.5-3.fc23.noarch requires sqljet = 1.1.10-4.fc23
> >> svnkit-1.8.5-3.fc23.src requires sqljet = 1.1.10-4.fc23
> >>
> >> mimepull (maintained by: goldmann, gil)
> >> mimepull-1.9.5-2.fc23.src requires
> >> mvn(org.tmatesoft.svnkit:svnkit) = 1.8.5
> >>
> >> netbeans-svnclientadapter (maintained by: omajid)
> >> netbeans-svnclientadapter-7.3.1-0.4.1.8.22.fc23.src
> >> requires svnkit = 1.8.5-3.fc23, svnkit-javahl = 1.8.5-3.fc23
> >>
> >> glassfish-jaxws (maintained by: gil, java-sig)
> >> glassfish-jaxws-2.2.10-2.fc23.noarch requires
> >> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> >> glassfish-jaxws-2.2.10-2.fc23.src requires
> >> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> >>
> >> glassfish-saaj (maintained by: goldmann)
> >> glassfish-saaj-1.3.19-8.fc23.noarch requires
> >> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> >> glassfish-saaj-1.3.19-8.fc23.src requires mimepull =
> >> 1.9.5-2.fc23
> >>
> >> jersey (maintained by: gil, java-sig)
> >> jersey-2.18-3.fc23.noarch requires
> >> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> >> jersey-2.18-3.fc23.src requires
> >> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> >>
> >> jersey1 (maintained by: )
> >> jersey1-1.19-4.fc23.src requires
> >> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> >> jersey1-contribs-1.19-4.fc23.noarch requires
> >> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> >>
> >> oat (maintained by: gwei3)
> >> oat-1.6.0-16.fc22.src requires mimepull = 1.9.5-2.fc23
> >>
> >> grizzly (maintained by: gil, java-sig)
> >> grizzly-2.3.19-2.fc23.src requires mvn(com.sun.xml.ws:rt)
> >> = 2.2.10.b140803.1500
> >> grizzly-samples-2.3.19-2.fc23.noarch requires
> >> mvn(com.sun.xml.ws:rt) = 2.2.10.b140803.1500
> >>
> >> springframework-ws (maintained by: gil, java-sig)
> >> springframework-ws-2.1.2-2.fc23.src requires
> >> mvn(com.sun.xml.messaging.saaj:saaj-impl) = 1.3.19
> >>
> >> docker-client (maintained by: )
> >> docker-client-3.1.3-1.fc23.noarch requires
> >> mvn(org.glassfish.jersey.connectors:jersey-apache-connector) = 2.18,
> >> mvn(org.glassfish.jersey.core:jersey-client) = 2.18,
> >> mvn(org.glassfish.jersey.media:jersey-media-json-jackson) = 2.18
> >> docker-client-3.1.3-1.fc23.src requires jersey =
> >> 2.18-3.fc23
> >>
> >> ambari (maintained by: pmackinn, coolsvap, java-sig, moceap)
> >> ambari-1.5.1-5.fc23.src requires jersey1-contribs =
> >> 1.19-4.fc23, jersey1-test-framework = 1.19-4.fc23
> >> ambari-server-1.5.1-5.fc23.noarch requires
> >> mvn(com.sun.jersey.contribs:jersey-guice:1.19) = 1.

Re: Removing packages that have broken dependencies in F23 tree

[Mikolaj Izdebski]

On 09/24/2015 07:12 PM, Christopher wrote:
> I don't really understand what's going on with the netbeans-platform
> package, or why accumulo would be affected. Upstream accumulo doesn't have
> any dependencies on netbeans. Before I try to dive in and figure out what's
> breaking, does anybody have any insight into what's going on with this, and
> what it's providing that is breaking so many java packages?

Accumulo depends on Hadoop, which is not installable in F23+:
https://bugzilla.redhat.com/show_bug.cgi?id=1196209

Hadoop maintainer said he didn't have much time for maintaining the
package and requested comaintainers, but without much response:
https://lists.fedoraproject.org/pipermail/java-devel/2015-March/005503.html

-- 
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Stephen John Smoogen]

On 24 September 2015 at 11:12, Christopher  wrote:
> I don't really understand what's going on with the netbeans-platform
> package, or why accumulo would be affected. Upstream accumulo doesn't have
> any dependencies on netbeans. Before I try to dive in and figure out what's
> breaking, does anybody have any insight into what's going on with this, and
> what it's providing that is breaking so many java packages?
>

I am probably misunderstanding your question, but from what I can see
is that we have a build chain break.

It is a build chain break. netbeans-platfrom is used to build tool A
which is used to build B .. and so accumulo can't be properly rebuilt
because that package chain isn't complete. The chain looks to be
coming from maven (mvn?) build requirements. If someone fixes either
netbeans-platform or sqljet not to rely on it, then all the items look
like they would then fix themselves.

The fix is either get sqljt

>> Depending on: netbeans-platform (33)
>> sqljet (maintained by: olea, filiperosset)
>> sqljet-1.1.10-4.fc23.src requires netbeans-platform =
>> 1:7.0.1-11.fc22
>> sqljet-browser-1.1.10-4.fc23.noarch requires
>> netbeans-platform = 1:7.0.1-11.fc22
>>
>> OmegaT (maintained by: olea, mtasaka)
>> OmegaT-2.6.3-2.fc22.i686 requires sqljet = 1.1.10-4.fc23
>> OmegaT-2.6.3-2.fc22.src requires sqljet = 1.1.10-4.fc23
>>
>> svnkit (maintained by: olea, akurtakov, dbhole, jfilak)
>> svnkit-1.8.5-3.fc23.noarch requires sqljet = 1.1.10-4.fc23
>> svnkit-1.8.5-3.fc23.src requires sqljet = 1.1.10-4.fc23
>>
>> mimepull (maintained by: goldmann, gil)
>> mimepull-1.9.5-2.fc23.src requires
>> mvn(org.tmatesoft.svnkit:svnkit) = 1.8.5
>>
>> netbeans-svnclientadapter (maintained by: omajid)
>> netbeans-svnclientadapter-7.3.1-0.4.1.8.22.fc23.src
>> requires svnkit = 1.8.5-3.fc23, svnkit-javahl = 1.8.5-3.fc23
>>
>> glassfish-jaxws (maintained by: gil, java-sig)
>> glassfish-jaxws-2.2.10-2.fc23.noarch requires
>> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>> glassfish-jaxws-2.2.10-2.fc23.src requires
>> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>>
>> glassfish-saaj (maintained by: goldmann)
>> glassfish-saaj-1.3.19-8.fc23.noarch requires
>> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>> glassfish-saaj-1.3.19-8.fc23.src requires mimepull =
>> 1.9.5-2.fc23
>>
>> jersey (maintained by: gil, java-sig)
>> jersey-2.18-3.fc23.noarch requires
>> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>> jersey-2.18-3.fc23.src requires
>> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>>
>> jersey1 (maintained by: )
>> jersey1-1.19-4.fc23.src requires
>> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>> jersey1-contribs-1.19-4.fc23.noarch requires
>> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>>
>> oat (maintained by: gwei3)
>> oat-1.6.0-16.fc22.src requires mimepull = 1.9.5-2.fc23
>>
>> grizzly (maintained by: gil, java-sig)
>> grizzly-2.3.19-2.fc23.src requires mvn(com.sun.xml.ws:rt)
>> = 2.2.10.b140803.1500
>> grizzly-samples-2.3.19-2.fc23.noarch requires
>> mvn(com.sun.xml.ws:rt) = 2.2.10.b140803.1500
>>
>> springframework-ws (maintained by: gil, java-sig)
>> springframework-ws-2.1.2-2.fc23.src requires
>> mvn(com.sun.xml.messaging.saaj:saaj-impl) = 1.3.19
>>
>> docker-client (maintained by: )
>> docker-client-3.1.3-1.fc23.noarch requires
>> mvn(org.glassfish.jersey.connectors:jersey-apache-connector) = 2.18,
>> mvn(org.glassfish.jersey.core:jersey-client) = 2.18,
>> mvn(org.glassfish.jersey.media:jersey-media-json-jackson) = 2.18
>> docker-client-3.1.3-1.fc23.src requires jersey =
>> 2.18-3.fc23
>>
>> ambari (maintained by: pmackinn, coolsvap, java-sig, moceap)
>> ambari-1.5.1-5.fc23.src requires jersey1-contribs =
>> 1.19-4.fc23, jersey1-test-framework = 1.19-4.fc23
>> ambari-server-1.5.1-5.fc23.noarch requires
>> mvn(com.sun.jersey.contribs:jersey-guice:1.19) = 1.19,
>> mvn(com.sun.jersey.contribs:jersey-multipart:1.19) = 1.19,
>> mvn(com.sun.jersey:jersey-client:1.19) = 1.19,
>> mvn(com.sun.jersey:jersey-json:1.19) = 1.19,
>> mvn(com.sun.jersey:jersey-server:1.19) = 1.19
>> ambari-views-1.5.1-5.fc23.noarch requires
>> mvn(com.sun.jersey:jersey-core:1.19) = 1.19
>>
>> guacamole-client (maintained by: slaanesh, gil, java-sig)
>> guacamole-0.9.8-1.fc23.noarch requires
>> mvn(com.sun.jersey.contribs:jersey-guice:1.19) = 1.19,
>> mvn(com.sun.jersey:jersey-json:1.19) = 1.19,
>> mvn(com.sun.jersey:jersey-server:1.19) = 1.19
>> guacamole-client-0.9.8-1.fc23.src requires
>> mvn(com.sun.jersey.contribs:jersey-guice

Re: Removing packages that have broken dependencies in F23 tree

[Christopher]

I don't really understand what's going on with the netbeans-platform
package, or why accumulo would be affected. Upstream accumulo doesn't have
any dependencies on netbeans. Before I try to dive in and figure out what's
breaking, does anybody have any insight into what's going on with this, and
what it's providing that is breaking so many java packages?

On Thu, Sep 24, 2015 at 10:37 AM Kalev Lember  wrote:

> Hi all,
>
> In less than three weeks we will be entering the F23 Final Freeze. At
> that point, Fedora release engineering retires any packages that still
> have broken dependencies in the F23 tree.
>
> Based on today's Branched report [1], we still have a number of unfixed
> packages with broken dependencies (package maintainers BCC'd to this
> email). Anything not fixed by 2015-10-12 from the list below is going to
> be automatically retired:
>
>Package  (co)maintainers
> 
> apache-scoutgoldmann
> aws landgraf
> hawaii-shelllkundrak, plfiorini
> hbase   rrati, coolsvap, moceap
> licqcicku, fcami, tieugene, yaneti
> mariadb-galera  rohara, hhorak
> moon-buggy  robert
> netbeans-platform   omajid, dbhole
> nodejs-grunt-contrib-copy ralph
> nodejs-grunt-saucelabs  ralph, piotrp
> nodejs-proxy-agent  ralph, piotrp
> oat gwei3
> oozie   rrati, coolsvap, moceap
> openstack-heat-gbp  rkukura
> openstack-neutron-gbp   rkukura
> openstack-swift zaitcev, apevec, derekh, hguemar, itamarjp,
> jsteffan, ke4qqq, mmagr, russellb
> perl-B-Hooks-OP-Check-EntersubForCV psabata, iarnell, perl-sig
> perl-Data-Alias pghmcfc, iarnell, perl-sig, psabata
> perl-Data-Dump-Streamer psabata, iarnell, perl-sig
> perl-Devel-BeginLiftpsabata, iarnell, perl-sig
> perl-Devel-FindRef  orphan, perl-sig
> perl-Method-Signatures  psabata, iarnell, perl-sig
> perl-POE-API-Peek   psabata, jplesnik, mmaslano, perl-sig, ppisar
> polymakejjames, rmattes
> puresalimma, cicku
> pyjigdo kanarip, jsteffan
> python-Fionachurchyard, group::python-sig
> python-django-horizon-gbp rkukura
> python-fiat fab
> python-gbpclientrkukura
> rakudo-star gerd
> spark   willb
> tritonuslimb, bsjones
> vdr-livemartinkg
> vfrnav  sailer
>
> I've excluded dpm-contrib-admintools, gnatcoll, publican, pvs-sbcl,
> trustedqsl from the list above; they all have pending fixes and just
> need to go through updates-testing in Bodhi to go to stable.
>
>
> Impacted dependant packages that would get retired together with the
> packages above:
>
> Depending on: apache-scout (2)
> wildfly (maintained by: goldmann)
> wildfly-8.1.0-3.fc22.src requires apache-scout =
> 1.2.6-11.fc21
>
> eclipse-jbosstools (maintained by: galileo, goldmann,
> group::eclipse-sig)
> eclipse-jbosstools-4.2.2-1.fc22.src requires wildfly =
> 8.1.0-3.fc22
> eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires wildfly
> = 8.1.0-3.fc22
>
>
> Depending on: hbase (2)
> pig (maintained by: pmackinn, coolsvap, java-sig, moceap)
> pig-0.13.0-1.fc21.noarch requires hbase = 0.98.3-4.fc22
> pig-0.13.0-1.fc21.src requires hbase = 0.98.3-4.fc22
>
> hive (maintained by: pmackinn, coolsvap, java-sig, moceap)
> hive-0.12.0-5.fc22.src requires pig = 0.13.0-1.fc21
>
>
> Depending on: netbeans-platform (33)
> sqljet (maintained by: olea, filiperosset)
> sqljet-1.1.10-4.fc23.src requires netbeans-platform =
> 1:7.0.1-11.fc22
> sqljet-browser-1.1.10-4.fc23.noarch requires
> netbeans-platform = 1:7.0.1-11.fc22
>
> OmegaT (maintained by: olea, mtasaka)
> OmegaT-2.6.3-2.fc22.i686 requires sqljet = 1.1.10-4.fc23
> OmegaT-2.6.3-2.fc22.src requires sqljet = 1.1.10-4.fc23
>
> svnkit (maintained by: olea, akurtakov, dbhole, jfilak)
> svnkit-1.8.5-3.fc23.noarch requires sqljet = 1.1.10-4.fc23
> svnkit-1.8.5-3.fc23.src requires sqljet = 1.1.10-4.fc23
>
> mimepull (maintained by: goldmann, gil)
> mimepull-1.9.5-2.fc23.src requires
> mvn(org.tmatesoft.svnkit:svnkit) = 1.8.5
>
> netbeans-svnclientadapter (maintained by: omajid)
> netbeans-svnclientadapter-7.3.1-0.4.1.8.22.fc23.src
> requires svnkit = 1.8.5-3.fc23, svnkit-javahl = 1.8.5-3.fc23
>
> glassfish-jaxws (maintained by: gil, java-sig)
> glassfish-jaxws-2.2.10-2.fc23.noarch requires
> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
> glassfish-jaxws-2.2.10-2.fc23.src requires
> mvn(org.jvnet.mimepull:mimepull) = 1.9.5
>
> glassfish-saaj (maintaine

Self Introduction: Phil Sutter

[Phil Sutter]

Hi,

I recently took over maintenance of the iproute package in Fedora. After
having become maintainer of it for RHEL, this was the logical next step.

Having a strong background in embedded build systems (I was a core
developer of FreeWRT until it deceased and am still contributing to
OpenADK), I am pretty familiar with downstream package management.

For nearly three months now I work for Red Hat. Aside from taking care
of iproute, I am contributing to kernel development as well. Which is a
nice fit, as the two of them are closely intertwined and often one has
to first find out on which side a bug is located in order to fix it.

My GPG key ID is 4C8A7383, the key is available on key servers (e.g. on
pgp.mit.edu). Note that I deliberately don't sign mails to mailing
lists as this has led to problems with list archives in the past
already. (Although this might not apply to the present situation
anymore.)

Cheers, Phil
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Kalev Lember]

On 09/24/2015 05:47 PM, Miro Hrončok wrote:
> 
> 
> On 24.9.2015 16:34, Kalev Lember wrote:
>> python-Fionachurchyard, group::python-sig
> 
> 
> This one cannot work with Fedora 23 due to GDAL 2. Feel free to retire it.

Can you retire it yourself if it is unfixable, please? 'fedpkg retire'
should take care of everything.

Thanks,
Kalev
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [EPEL-devel] [Proposal] Converge EPEL and CBS

[Haïkel]

Looks like we do have some progress on that topic :)

So plan B would be:
1. automate EPEL rebuilds in CBS
2. have CI run automated test suite over EPEL rebuilds

Correct me if I'm wrong but we would be ok to enable CentOS folks to
fix EPEL packaging.
It would be easier if we do create an epel-provenpackager group
limited to EL branches distinct from fedora's provenpackager as in the
first proposal.

If that's ok for everyone, let's wait Karsten speak to KB (and
hopefully, start working on this asap)

H.
___
epel-devel mailing list
epel-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: llvm 3.7 for rawhide and then f23

[drago01]

On Thu, Sep 24, 2015 at 6:04 PM, Dave Johansen  wrote:
> On Mon, Sep 21, 2015 at 6:27 AM, Adam Jackson  wrote:
>>
>> On Sun, 2015-09-20 at 21:00 +0800, Christopher Meng wrote:
>> > On 9/20/15, David Airlie  wrote:
>> > > It's llvm, there is never a good time to upgrade it and no llvm
>> > > release is
>> > > backwards compatible.
>> >
>> > Yes, so unless someone is pretty familiar with LLVM upstream, keep
>> > reading every changeset, no body can guarantee what will happen.
>>
>> That's not really a fair assessment.  By far the most important thing
>> in Fedora that needs llvm is Mesa.  The llvm build system has a fairly
>> comprehensive test suite (which, btw, fails on at least arm with 3.6.1,
>> but passes on all arches with 3.7), and Mesa has another test suite in
>> the form of piglit that we can use to ensure that changing llvm doesn't
>> regress llvmpipe or r600 or radeonsi.
>>
>> So we can in fact be pretty confident that llvm upgrades won't break
>> the things we actually use llvm for in Fedora.
>
>
> It sounds like there's a lot of momentum behind the update to 3.7 for F23,
> but iwyu ( https://github.com/include-what-you-use/include-what-you-use ) is
> built on top of clang and there's still not an upstream release that's
> compatible with 3.7 so updating in F23 will break iwyu until a release is
> made. So, I personally would prefer that the update to 3.7 only happen in
> Rawhide where breakage like this is expected, but I realize that I'm only
> one voice of many and that iwyu is used a LOT less than other packages like
> Mesa.

There is a llvm34 package for such software.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Parag Nemade]

Hi Ralph,

On Thu, Sep 24, 2015 at 9:12 PM, Ralph Bean  wrote:
> On Thu, Sep 24, 2015 at 04:34:11PM +0200, Kalev Lember wrote:
>> nodejs-grunt-contrib-copy ralph

This package is missing needed dependency npm(file-sync-cmp) to be
packaged in Fedora.

>> nodejs-grunt-saucelabs  ralph, piotrp

This package is missing needed dependency npm(requestretry) to be
packaged in Fedora.

>> nodejs-proxy-agent  ralph, piotrp

I have just rebuilt the existing commit which is working fine for
Fedora 23 and submitted update, rawhide is using higher version so no
issues there.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: llvm 3.7 for rawhide and then f23

[Dave Johansen]

On Mon, Sep 21, 2015 at 6:27 AM, Adam Jackson  wrote:

> On Sun, 2015-09-20 at 21:00 +0800, Christopher Meng wrote:
> > On 9/20/15, David Airlie  wrote:
> > > It's llvm, there is never a good time to upgrade it and no llvm
> release is
> > > backwards compatible.
> >
> > Yes, so unless someone is pretty familiar with LLVM upstream, keep
> > reading every changeset, no body can guarantee what will happen.
>
> That's not really a fair assessment.  By far the most important thing
> in Fedora that needs llvm is Mesa.  The llvm build system has a fairly
> comprehensive test suite (which, btw, fails on at least arm with 3.6.1,
> but passes on all arches with 3.7), and Mesa has another test suite in
> the form of piglit that we can use to ensure that changing llvm doesn't
> regress llvmpipe or r600 or radeonsi.
>
> So we can in fact be pretty confident that llvm upgrades won't break
> the things we actually use llvm for in Fedora.
>

It sounds like there's a lot of momentum behind the update to 3.7 for F23,
but iwyu ( https://github.com/include-what-you-use/include-what-you-use )
is built on top of clang and there's still not an upstream release that's
compatible with 3.7 so updating in F23 will break iwyu until a release is
made. So, I personally would prefer that the update to 3.7 only happen in
Rawhide where breakage like this is expected, but I realize that I'm only
one voice of many and that iwyu is used a LOT less than other packages like
Mesa.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Miro Hrončok]

On 24.9.2015 16:34, Kalev Lember wrote:
> python-Fionachurchyard, group::python-sig


This one cannot work with Fedora 23 due to GDAL 2. Feel free to retire it.

-- 
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Petr Šabata]

On Thu, Sep 24, 2015 at 04:34:11PM +0200, Kalev Lember wrote:
> perl-B-Hooks-OP-Check-EntersubForCV psabata, iarnell, perl-sig
> perl-Data-Dump-Streamer psabata, iarnell, perl-sig
> perl-Devel-BeginLiftpsabata, iarnell, perl-sig
> perl-Devel-FindRef  orphan, perl-sig
> perl-Method-Signatures  psabata, iarnell, perl-sig
> perl-POE-API-Peek   psabata, jplesnik, mmaslano, perl-sig, ppisar

I retired these yesterday.
P


pgpFyp92G5lLn.pgp
Description: PGP signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Ralph Bean]

On Thu, Sep 24, 2015 at 04:34:11PM +0200, Kalev Lember wrote:
> nodejs-grunt-contrib-copy ralph
> nodejs-grunt-saucelabs  ralph, piotrp
> nodejs-proxy-agent  ralph, piotrp

These three got rebuilt this morning (made possible by piotrp's hard
work on the rest of the dep chain).


signature.asc
Description: PGP signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Erroneous automated comments on some Review Request tickets

[Ralph Bean]

This morning we deployed a new release of 'the-new-hotness'[1], which
is the service we run that monitors new upstream releases from
release-monitoring.org, as well as koji builds, and uses this
information to file and comment on bugzilla tickets.

The release adds a new feature[2] that adds comments to Review Request
bugs about successful scratch builds of that package.  However, there
was a bug.  A kdevelop scratch build incorrectly triggered comments on
43 different review request tickets[3].  A patch has been added that
should stop it from happening again[4].

My apologies for the spam.

-Ralph Bean

[1] - 
https://lists.fedoraproject.org/archives/list/infrastructure%40lists.fedoraproject.org/thread/5AGAHCBFUTGDIK7LQV6U6QHLZKQRG2WZ/
[2] - https://github.com/fedora-infra/the-new-hotness/pull/69
[3] - 
https://apps.fedoraproject.org/datagrepper/raw?category=hotness&start=1443010402&end=1443123402
[4] - 
https://github.com/fedora-infra/the-new-hotness/commit/606d666fbba63e5963f505b735425565be0f0d88


signature.asc
Description: PGP signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Jon Ciesla]

On Thu, Sep 24, 2015 at 10:13 AM, gil  wrote:

>
>
> Il 24/09/2015 16:43, Jon Ciesla ha scritto:
>
>
>
>
> tritonuslimb, bsjones
>>
>> Depending on: tritonus (1)
>> vorbisspi (maintained by: hicham)
>> vorbisspi-1.0.3-10.fc23.noarch requires tritonus =
>> 0.3.7-0.23.20101108cvs.fc22
>> vorbisspi-1.0.3-10.fc23.src requires tritonus =
>> 0.3.7-0.23.20101108cvs.fc22
>>
>> [1]
>> https://lists.fedoraproject.org/pipermail/devel/2015-September/214987.html
>>
>> --
>> Kalev
>>
>
> I've been working on this for awhile with no luck.  Hicham, is it possible
> for vorbisspi to function without tritonus?  Or can vorbisspi be retired?
>
> Unless, of course, someone with superior Java-fu to myself can assist. . .
>
> -j
>
> hi
> the build failure seem cause by javod colint problems ... have you tired
> to use, as (additonal)parameter,
> -Xdoclint:none ?
> regards
> gil
>

Fixed with:

-%javadoc -d javadoc -public `find ./ -name '*.java'`
+%javadoc -d javadoc -public -Xdoclint:none `find ./ -name '*.java'`


Thank you so much!

> --
> http://cecinestpasunefromage.wordpress.com/
> 
> in your fear, seek only peace
> in your fear, seek only love
>
> -d. bowie
>
>
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>



-- 
http://cecinestpasunefromage.wordpress.com/

in your fear, seek only peace
in your fear, seek only love

-d. bowie
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Matthias Clasen]

On Thu, 2015-09-24 at 11:00 -0400, Adam Jackson wrote:
> On Thu, 2015-09-24 at 00:59 +, Zbigniew Jędrzejewski-Szmek wrote:
> 
> > Bummer. The reason for libxkbcommon dependency is to be able to
> > make
> > sure that the new config is valid. Before that was added we had a
> > set
> > of rules and heuristics implemented in localed and regular bug
> > reports
> > when typos and other mistakes were not caught by localed but Xorg
> > would not accept the new config. This is more important than might
> > seem, 'cause people tend to get grumpy when a misconfigured
> > keyboard
> > mapping prevents them from typing in their password. So this
> > dependency
> > does bring useful functionality.
> 
> We can certainly make xkeyboard-config smaller. About half its on-
> disk
> footprint is localized strings, %langpack would help. The geometry
> subdir is completely useless, and I'm reasonably sure the xml it
> installs is really just source data and not anything apps or libs
> use.
> All told that'd get xkeyboard-config down to a hair over 2M on disk.
> 

Not saying that it is very useful, but I believe gkbd-keyboard-display
does use geometry information.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[gil]

Il 24/09/2015 16:43, Jon Ciesla ha scritto:




tritonuslimb, bsjones

Depending on: tritonus (1)
vorbisspi (maintained by: hicham)
vorbisspi-1.0.3-10.fc23.noarch requires tritonus =
0.3.7-0.23.20101108cvs.fc22
vorbisspi-1.0.3-10.fc23.src requires tritonus =
0.3.7-0.23.20101108cvs.fc22

[1]
https://lists.fedoraproject.org/pipermail/devel/2015-September/214987.html

--
Kalev


I've been working on this for awhile with no luck.  Hicham, is it 
possible for vorbisspi to function without tritonus?  Or can vorbisspi 
be retired?


Unless, of course, someone with superior Java-fu to myself can assist. . .

-j


hi
the build failure seem cause by javod colint problems ... have you tired 
to use, as (additonal)parameter,

-Xdoclint:none ?
regards
gil

--
http://cecinestpasunefromage.wordpress.com/

in your fear, seek only peace
in your fear, seek only love

-d. bowie




-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Adam Jackson]

On Thu, 2015-09-24 at 00:59 +, Zbigniew Jędrzejewski-Szmek wrote:

> Bummer. The reason for libxkbcommon dependency is to be able to make
> sure that the new config is valid. Before that was added we had a set
> of rules and heuristics implemented in localed and regular bug reports
> when typos and other mistakes were not caught by localed but Xorg
> would not accept the new config. This is more important than might
> seem, 'cause people tend to get grumpy when a misconfigured keyboard
> mapping prevents them from typing in their password. So this dependency
> does bring useful functionality.

We can certainly make xkeyboard-config smaller. About half its on-disk
footprint is localized strings, %langpack would help. The geometry
subdir is completely useless, and I'm reasonably sure the xml it
installs is really just source data and not anything apps or libs use.
All told that'd get xkeyboard-config down to a hair over 2M on disk.

- ajax
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Applications missing from Fedora 23

[Ben Boeckel]

On Thu, Sep 24, 2015 at 15:15:16 +0100, Richard Hughes wrote:
> With a bit of gimp'ing, isn't the one on the top right of
> http://www.uzbl.org/ good enough to install? That looks a lot like
> 64x64.

Actually, keis pointed me to an SVG that had already been made:

https://github.com/uzbl/uzbl-website/blob/master/img/uzbl.svg

I'll make new icons from this.

Thanks,

--Ben
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Jon Ciesla]

tritonuslimb, bsjones
>
> Depending on: tritonus (1)
> vorbisspi (maintained by: hicham)
> vorbisspi-1.0.3-10.fc23.noarch requires tritonus =
> 0.3.7-0.23.20101108cvs.fc22
> vorbisspi-1.0.3-10.fc23.src requires tritonus =
> 0.3.7-0.23.20101108cvs.fc22
>
> [1]
> https://lists.fedoraproject.org/pipermail/devel/2015-September/214987.html
>
> --
> Kalev
>

I've been working on this for awhile with no luck.  Hicham, is it possible
for vorbisspi to function without tritonus?  Or can vorbisspi be retired?

Unless, of course, someone with superior Java-fu to myself can assist. . .

-j

-- 
http://cecinestpasunefromage.wordpress.com/

in your fear, seek only peace
in your fear, seek only love

-d. bowie
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Removing packages that have broken dependencies in F23 tree

[Kalev Lember]

Hi all,

In less than three weeks we will be entering the F23 Final Freeze. At
that point, Fedora release engineering retires any packages that still
have broken dependencies in the F23 tree.

Based on today's Branched report [1], we still have a number of unfixed
packages with broken dependencies (package maintainers BCC'd to this
email). Anything not fixed by 2015-10-12 from the list below is going to
be automatically retired:

   Package  (co)maintainers

apache-scoutgoldmann
aws landgraf
hawaii-shelllkundrak, plfiorini
hbase   rrati, coolsvap, moceap
licqcicku, fcami, tieugene, yaneti
mariadb-galera  rohara, hhorak
moon-buggy  robert
netbeans-platform   omajid, dbhole
nodejs-grunt-contrib-copy ralph
nodejs-grunt-saucelabs  ralph, piotrp
nodejs-proxy-agent  ralph, piotrp
oat gwei3
oozie   rrati, coolsvap, moceap
openstack-heat-gbp  rkukura
openstack-neutron-gbp   rkukura
openstack-swift zaitcev, apevec, derekh, hguemar, itamarjp, jsteffan, 
ke4qqq, mmagr, russellb
perl-B-Hooks-OP-Check-EntersubForCV psabata, iarnell, perl-sig
perl-Data-Alias pghmcfc, iarnell, perl-sig, psabata
perl-Data-Dump-Streamer psabata, iarnell, perl-sig
perl-Devel-BeginLiftpsabata, iarnell, perl-sig
perl-Devel-FindRef  orphan, perl-sig
perl-Method-Signatures  psabata, iarnell, perl-sig
perl-POE-API-Peek   psabata, jplesnik, mmaslano, perl-sig, ppisar
polymakejjames, rmattes
puresalimma, cicku
pyjigdo kanarip, jsteffan
python-Fionachurchyard, group::python-sig
python-django-horizon-gbp rkukura
python-fiat fab
python-gbpclientrkukura
rakudo-star gerd
spark   willb
tritonuslimb, bsjones
vdr-livemartinkg
vfrnav  sailer

I've excluded dpm-contrib-admintools, gnatcoll, publican, pvs-sbcl,
trustedqsl from the list above; they all have pending fixes and just
need to go through updates-testing in Bodhi to go to stable.


Impacted dependant packages that would get retired together with the
packages above:

Depending on: apache-scout (2)
wildfly (maintained by: goldmann)
wildfly-8.1.0-3.fc22.src requires apache-scout = 1.2.6-11.fc21

eclipse-jbosstools (maintained by: galileo, goldmann, 
group::eclipse-sig)
eclipse-jbosstools-4.2.2-1.fc22.src requires wildfly = 
8.1.0-3.fc22
eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires wildfly = 
8.1.0-3.fc22


Depending on: hbase (2)
pig (maintained by: pmackinn, coolsvap, java-sig, moceap)
pig-0.13.0-1.fc21.noarch requires hbase = 0.98.3-4.fc22
pig-0.13.0-1.fc21.src requires hbase = 0.98.3-4.fc22

hive (maintained by: pmackinn, coolsvap, java-sig, moceap)
hive-0.12.0-5.fc22.src requires pig = 0.13.0-1.fc21


Depending on: netbeans-platform (33)
sqljet (maintained by: olea, filiperosset)
sqljet-1.1.10-4.fc23.src requires netbeans-platform = 
1:7.0.1-11.fc22
sqljet-browser-1.1.10-4.fc23.noarch requires netbeans-platform 
= 1:7.0.1-11.fc22

OmegaT (maintained by: olea, mtasaka)
OmegaT-2.6.3-2.fc22.i686 requires sqljet = 1.1.10-4.fc23
OmegaT-2.6.3-2.fc22.src requires sqljet = 1.1.10-4.fc23

svnkit (maintained by: olea, akurtakov, dbhole, jfilak)
svnkit-1.8.5-3.fc23.noarch requires sqljet = 1.1.10-4.fc23
svnkit-1.8.5-3.fc23.src requires sqljet = 1.1.10-4.fc23

mimepull (maintained by: goldmann, gil)
mimepull-1.9.5-2.fc23.src requires 
mvn(org.tmatesoft.svnkit:svnkit) = 1.8.5

netbeans-svnclientadapter (maintained by: omajid)
netbeans-svnclientadapter-7.3.1-0.4.1.8.22.fc23.src requires 
svnkit = 1.8.5-3.fc23, svnkit-javahl = 1.8.5-3.fc23

glassfish-jaxws (maintained by: gil, java-sig)
glassfish-jaxws-2.2.10-2.fc23.noarch requires 
mvn(org.jvnet.mimepull:mimepull) = 1.9.5
glassfish-jaxws-2.2.10-2.fc23.src requires 
mvn(org.jvnet.mimepull:mimepull) = 1.9.5

glassfish-saaj (maintained by: goldmann)
glassfish-saaj-1.3.19-8.fc23.noarch requires 
mvn(org.jvnet.mimepull:mimepull) = 1.9.5
glassfish-saaj-1.3.19-8.fc23.src requires mimepull = 
1.9.5-2.fc23

jersey (maintained by: gil, java-sig)
jersey-2.18-3.fc23.noarch requires 
mvn(org.jvnet.mimepull:mimepull) = 1.9.5
jersey-2.18-3.fc23.src requires 
mvn(org.jvnet.mimepull:mimepull) = 1.9.5

jersey1 (maintained by: )
jersey1-1.19-4.fc23.src requires 
mvn(org.jvnet.mimepull:mimepull) = 1.9.5
jersey1-contribs-1.19-4.fc23.

Re: Orphaned Packages in rawhide (2015-09-21)

[Kevin Fenzi]

On Thu, 24 Sep 2015 10:36:05 +0200
Matthias Runge  wrote:

> On Mon, Sep 21, 2015 at 11:35:30AM +, opensou...@till.name wrote:
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someone adopts them. If you know
> > for sure that the package should be retired, please do so now with
> > a proper reason:
> > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> > tinymceorphan, mrunge, ngompa, rhe   0
> > weeks ago tinymce-spellchecker   orphan, mrunge, ngompa,
> > rhe   0 weeks ago   
> ...
> > Depending on: tinymce (1), status change: 2015-09-20 (0 weeks ago)
> > python-django-tinymce (maintained by: yuwang, mrunge)
> > python-django-tinymce-1.5.2-2.fc21.noarch requires
> > tinymce = 3.5.10-3.fc23
> 
> Those 3 package should imho just go away.
> 
> Any takers? Otherwise I'd retire them in 2 weeks.

I still need tinymce for askbot in epel6... 

I don't much care about the other branches tho. ;) 

kevin


pgpp0duqQbr3u.pgp
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Applications missing from Fedora 23

[Richard Hughes]

On 20 September 2015 at 15:50, Ben Boeckel  wrote:
> Is this something any app with a too-small icon (or without, I suppose)
> can do? For example, uzbl has an icon, but I have no source to make a
> scaled up one (and contacting the original author has gotten nothing).

With a bit of gimp'ing, isn't the one on the top right of
http://www.uzbl.org/ good enough to install? That looks a lot like
64x64.

Richard.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Minutes from Env-and-Stacks WG meeting (2015-09-24)

[Honza Horak]

==
#fedora-meeting-2: Env and Stacks (2015-09-24)
==


Meeting started by hhorak at 12:03:08 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-2/2015-09-24/env-and-stacks.2015-09-24-12.03.log.html
.



Meeting summary
---
* Fedora dockerfiles -- versions, size, more involvement from E&S
  (hhorak, 12:04:30)
  * LINK: https://github.com/fedora-cloud/Fedora-Dockerfiles/pull/128
(hhorak, 12:07:28)
  * some PRs take too long to be merged in Fedora dockerfiles, let's
help Scott with that work..  (hhorak, 12:08:12)
  * ACTION: bkabrda to get in touch with scott tomorrow to see how he
can help him  (hhorak, 12:12:15)
  * LINK: http://imgur.com/TnpcouY   (vpavlin, 12:49:27)
  * LINK: http://imgur.com/TnpcouY   (vpavlin, 12:51:49)
  * it is possible to configure in docker hub what tags should be used
for automatically re(build) images (based on github branch and path)
(hhorak, 12:56:32)
  * every tag will require a new build on docker hub, but we can still
set up something like git-branch+path -> { docker-tag-a,
docker-tag-b } ... i will just create more builds than we'd
expect...  (hhorak, 13:15:08)
  * Product Definition Center is a dependency for triggering Docker
rebuilds on RPM updates  (ncoghlan, 13:17:49)
  * LINK: https://fedorahosted.org/fedora-infrastructure/ticket/4863
(ncoghlan, 13:17:59)
  * ACTION: vpavlin will setup a demo process and document how we can
build the versioned dockerfiles in from
https://github.com/fedora-cloud/Fedora-Dockerfiles  (hhorak,
13:18:28)

* open-floor  (hhorak, 13:21:31)
  * ACTION: hhorak to touch other topics (not covered today) on ML
(hhorak, 13:22:00)
  * LINK:

https://fedoraproject.org/wiki/Env_and_Stacks/Projects/ImageAssemblyRecommendations
(hhorak, 13:25:56)
  * Layered images are special, since they're the ones that can bring in
additional non-RPM bits (gem, maven); 1-to-1 mirrors for those could
be implemented by RepoFunnel building on Pulp, but it's still not
sure whether this middle step is necessary  (hhorak, 13:36:25)
  * fedora rel-eng plans to build at least the cockpit layered image for
f24 and potentially others  (hhorak, 13:42:38)

Meeting ended at 13:43:33 UTC.




Action Items

* bkabrda to get in touch with scott tomorrow to see how he can help him
* vpavlin will setup a demo process and document how we can build the
  versioned dockerfiles in from
  https://github.com/fedora-cloud/Fedora-Dockerfiles
* hhorak to touch other topics (not covered today) on ML




Action Items, by person
---
* bkabrda
  * bkabrda to get in touch with scott tomorrow to see how he can help
him
* hhorak
  * hhorak to touch other topics (not covered today) on ML
* vpavlin
  * vpavlin will setup a demo process and document how we can build the
versioned dockerfiles in from
https://github.com/fedora-cloud/Fedora-Dockerfiles
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* hhorak (91)
* vpavlin (64)
* ncoghlan (53)
* bkabrda (26)
* praiskup (21)
* jkaluza (16)
* langdon (15)
* ttomecek (11)
* dgilmore (5)
* zodbot (4)
* phracek (1)
* juhp (0)
* walters (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: virtual provides/metapackage for various OpenCL implementations

[Fabian Deutsch]

On Thu, Sep 24, 2015 at 12:21 PM, Dominik 'Rathann' Mierzejewski
 wrote:
> Dear maintainers,
> I've just enabled OpenCL support in the gromacs package[1] and would
> like to express a weak dependency on an OpenCL implementation, but I
> have no way of doing so at the moment.
>
> We have three packages which provide OpenCL implementations:
> beignet - Intel GPUs
> mesa-libOpenCL - AMD GPUs (only?)
> pocl - CPU-based
>
> Would it make sense to add a virtual provide to each of the packages
> to mean the all provide a "vendor" OpenCL implementation? For example,
> Provides: opencl-driver
>
> Then, any package that makes use of OpenCL could add
> Requires/Recommends/Suggests: opencl-driver
>
> Another approach could be to create a meta package (named
> opencl-drivers, for example - similar to xorg-x11-drivers) which would
> depend on all vendor-specific implementations.
>
> I guess the second approach is more fool-proof. Comments?

Hey,

yes - when we initially create the packages we actually already
discussed how to achieve this.

I'd favor the second (meta-package) approach, nothing should go wrong
if all three are installed.

I'd go even further and create an opencl package (or group?) to
install all kind of opencl packages, i.e. clinfo is a good thing to
start with.

- fabian

> Regards,
> Dominik
>
> [1] 
> http://pkgs.fedoraproject.org/cgit/gromacs.git/commit/?id=dbabc099d66902daa094478024a8a331822b78bc
> --
> Fedora http://fedoraproject.org/wiki/User:Rathann
> RPMFusion http://rpmfusion.org
> "Faith manages."
> -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

F-23 Branched report: 20150924 changes

[Fedora Branched Report]

Compose started at Thu Sep 24 07:15:03 UTC 2015
Broken deps for armhfp
--
[apache-scout]
apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
apache-scout-1.2.6-11.fc21.noarch requires 
mvn(org.apache.juddi:juddi-client)
[aws]
aws-tools-2015-2.fc23.armv7hl requires libaws_ssl.so
[dpm-contrib-admintools]
dpm-contrib-admintools-0.2.1-6.fc23.armv7hl requires 
MySQL-python(armv7hl-32)
[hawaii-shell]
hawaii-shell-0.3.0-3.fc22.armv7hl requires 
libqtaccountsservice-qt5.so.0.1.2
[hbase]
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
[licq]
licq-1.8.2-9.fc23.armv7hl requires libboost_regex.so.1.57.0
[mariadb-galera]
1:mariadb-galera-server-10.0.17-5.fc23.armv7hl requires galera >= 
0:25.3.3
[moon-buggy]
moon-buggy-1.0.51-14.fc23.armv7hl requires libesd.so.0
[netbeans-platform]
1:netbeans-platform-harness-7.0.1-11.fc22.armv7hl requires cobertura >= 
0:1.9.3
[nodejs-grunt-contrib-copy]
nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires 
npm(file-sync-cmp) < 0:0.2
nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires 
npm(file-sync-cmp) >= 0:0.1.0
nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(chalk) >= 
0:0.5.1
[nodejs-grunt-saucelabs]
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(sauce-tunnel) 
>= 0:2.2.3
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(requestretry) < 
0:1.3
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(requestretry) 
>= 0:1.2.2
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(lodash) >= 
0:3.7.0
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(colors) >= 
0:1.0.0
[nodejs-proxy-agent]
nodejs-proxy-agent-1.1.0-1.fc22.noarch requires npm(socks-proxy-agent) 
< 0:1
[oat]
oat-appraiser-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api
oat-client-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api
[oozie]
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.pig:pig)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-serde)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-metastore)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-exec)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-common)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-cli)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:webhcat-java-client)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:hcatalog-server-extensions)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:hcatalog-pig-adapter)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:hcatalog-core)
[openstack-heat-gbp]
openstack-heat-gbp-2014.2-2.fc23.noarch requires openstack-heat-engine 
< 0:2014.3
[openstack-neutron-gbp]
openstack-neutron-gbp-2014.2-2.fc23.noarch requires openstack-neutron < 
0:2014.3
[openstack-swift]
openstack-swift-2.3.0-2.fc23.noarch requires python-pyeclib
[perl-B-Hooks-OP-Check-EntersubForCV]
perl-B-Hooks-OP-Check-EntersubForCV-0.09-10.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-B-Hooks-OP-Check-EntersubForCV-0.09-10.fc22.armv7hl requires 
libperl.so.5.20
[perl-Data-Alias]
perl-Data-Alias-1.18-4.fc22.armv7hl requires perl(:MODULE_COMPAT_5.20.0)
perl-Data-Alias-1.18-4.fc22.armv7hl requires libperl.so.5.20
[perl-Data-Dump-Streamer]
perl-Data-Dump-Streamer-2.38-3.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-Data-Dump-Streamer-2.38-3.fc22.armv7hl requires libperl.so.5.20
[perl-Devel-BeginLift]
perl-Devel-BeginLift-0.001003-9.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-Devel-BeginLift-0.001003-9.fc22.armv7hl requires libperl.so.5.20
[perl-Devel-FindRef]
perl-Devel-FindRef-1.44-3.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-Devel-FindRef-1.44-3.fc22.armv7hl requires libperl.so.5.20
[perl-Method-Signatures]
perl-Method-Signatures-20141021-1.fc22.noarch requires 
perl(:MODULE_COMPAT_5.20.1)
[perl-POE-API-Peek]
1:perl-POE-API-Peek-2.20-8.fc22.noarch requires 
perl(:MODULE_COMPAT_5.20.0)
[polymake]
polymake-2.13-22.git20141013.fc23.armv7hl requires 
perl(:MODULE_COMPAT_5.20.2)
polymake-2.13-22.git20141013.fc23.armv7hl requires perl = 4:5.20.2
polymake-2.13-22.git201410

Re: Updating to f23 beta from f22

[Kalpa Welivitigoda]

On Thu, Sep 24, 2015 at 5:03 PM, Peter Robinson 
wrote:

> On Thu, Sep 24, 2015 at 12:28 PM, Kalpa Welivitigoda
>  wrote:
> > I followed [1] and tried the section "Fedora 22 -> Fedora 23". But in the
> > package list to be downloaded, I find gnome packages with 3.17 rather
> than
> > 3.18. For example,
> >
> > gnome-session x86_64 3.17.92-1.fc23 fedora 378 k
> >
> > Shouldn't f23-beta contain gnome 3.18 packages? am I missing something
> here?
>
> Make sure you have updates-testing enabled, it could also be that your
> mirror is not updated yet.
>

Enabling updates-testing worked for me!. Thanks.


>
> Peter
>
> > On Thu, Sep 24, 2015 at 3:54 PM, Kalpa Welivitigoda  >
> > wrote:
> >>
> >>
> >>
> >> On Thu, Sep 24, 2015 at 3:51 PM, Peter Robinson 
> >> wrote:
> >>>
> >>> On Thu, Sep 24, 2015 at 11:08 AM, Kalpa Welivitigoda
> >>>  wrote:
> >>> > Hi all,
> >>> >
> >>> > How can I update to f23 beta from f22?
> >>>
> >>> Same way as on other releases, with fedup (see thread on this list
> >>> against the release announcement for details) or "dnf distro-sync" as
> >>> per docs [1]
> >>>
> >>> Peter
> >>>
> >>> [1]
> >>>
> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23
> >>
> >>
> >> Thanks Peter :-)
> >>
> >>>
> >>>
> >>> --
> >>> devel mailing list
> >>> devel@lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/devel
> >>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> >>
> >>
> >>
> >>
> >> --
> >> Best Regards,
> >>
> >> Kalpa Welivitigoda
> >> +94776509215
> >> http://about.me/callkalpa
> >
> >
> >
> >
> > --
> > Best Regards,
> >
> > Kalpa Welivitigoda
> > +94776509215
> > http://about.me/callkalpa
> >
> > --
> > devel mailing list
> > devel@lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/devel
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>



-- 
Best Regards,

Kalpa Welivitigoda
+94776509215
http://about.me/callkalpa
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

rawhide report: 20150924 changes

[Fedora Rawhide Report]

Compose started at Thu Sep 24 05:15:03 UTC 2015
Broken deps for i386
--
[IQmol]
IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libOpenMeshCore.so.3.2
[Macaulay2]
Macaulay2-1.6-17.fc24.i686 requires libntl.so.14
[Singular]
Singular-3.1.6-16.fc24.i686 requires libntl.so.14
[apache-scout]
apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
apache-scout-1.2.6-11.fc21.noarch requires 
mvn(org.apache.juddi:juddi-client)
[aqsis]
aqsis-1.8.2-20.fc24.i686 requires libboost_thread.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_system.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_regex.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_program_options.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_filesystem.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_wave.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_thread.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_system.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_regex.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_iostreams.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_filesystem.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_thread.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_system.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_regex.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_iostreams.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_filesystem.so.1.58.0
[aws]
aws-tools-2015-2.fc23.i686 requires libaws_ssl.so
[bro]
bro-2.3.2-6.fc23.i686 requires libjemalloc.so.1
[bwm-ng]
bwm-ng-0.6-18.fc24.i686 requires libstatgrab.so.6
[cp2k]
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi_usempif08.so.0(openmpi-i386)
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi_usempi_ignore_tkr.so.0(openmpi-i386)
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi_mpifh.so.2(openmpi-i386)
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi.so.1(openmpi-i386)
[derelict]
derelict-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-AL-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-AL-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-ALURE-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-ALURE-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-ASSIMP3-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-ASSIMP3-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-FI-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-FI-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-FT-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-FT-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-GL3-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-GL3-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-GLFW3-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-GLFW3-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-IL-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-IL-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-LUA-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-LUA-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-ODE-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-ODE-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-Ogg-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-Ogg-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-PHYSFS-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-PHYSFS-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-PQ-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-PQ-3-32.20141022git7f

Re: Updating to f23 beta from f22

[Peter Robinson]

On Thu, Sep 24, 2015 at 12:28 PM, Kalpa Welivitigoda
 wrote:
> I followed [1] and tried the section "Fedora 22 -> Fedora 23". But in the
> package list to be downloaded, I find gnome packages with 3.17 rather than
> 3.18. For example,
>
> gnome-session x86_64 3.17.92-1.fc23 fedora 378 k
>
> Shouldn't f23-beta contain gnome 3.18 packages? am I missing something here?

Make sure you have updates-testing enabled, it could also be that your
mirror is not updated yet.

Peter

> On Thu, Sep 24, 2015 at 3:54 PM, Kalpa Welivitigoda 
> wrote:
>>
>>
>>
>> On Thu, Sep 24, 2015 at 3:51 PM, Peter Robinson 
>> wrote:
>>>
>>> On Thu, Sep 24, 2015 at 11:08 AM, Kalpa Welivitigoda
>>>  wrote:
>>> > Hi all,
>>> >
>>> > How can I update to f23 beta from f22?
>>>
>>> Same way as on other releases, with fedup (see thread on this list
>>> against the release announcement for details) or "dnf distro-sync" as
>>> per docs [1]
>>>
>>> Peter
>>>
>>> [1]
>>> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23
>>
>>
>> Thanks Peter :-)
>>
>>>
>>>
>>> --
>>> devel mailing list
>>> devel@lists.fedoraproject.org
>>> https://admin.fedoraproject.org/mailman/listinfo/devel
>>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>>
>>
>>
>>
>> --
>> Best Regards,
>>
>> Kalpa Welivitigoda
>> +94776509215
>> http://about.me/callkalpa
>
>
>
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> +94776509215
> http://about.me/callkalpa
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Updating to f23 beta from f22

[Kalpa Welivitigoda]

I followed [1] and tried the section "Fedora 22 -> Fedora 23". But in the
package list to be downloaded, I find gnome packages with 3.17 rather than
3.18. For example,

gnome-session x86_64 3.17.92-1.fc23 fedora 378 k

Shouldn't f23-beta contain gnome 3.18 packages? am I missing something here?

On Thu, Sep 24, 2015 at 3:54 PM, Kalpa Welivitigoda 
wrote:

>
>
> On Thu, Sep 24, 2015 at 3:51 PM, Peter Robinson 
> wrote:
>
>> On Thu, Sep 24, 2015 at 11:08 AM, Kalpa Welivitigoda
>>  wrote:
>> > Hi all,
>> >
>> > How can I update to f23 beta from f22?
>>
>> Same way as on other releases, with fedup (see thread on this list
>> against the release announcement for details) or "dnf distro-sync" as
>> per docs [1]
>>
>> Peter
>>
>> [1]
>> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23
>
>
> Thanks Peter :-)
>
>
>>
>> --
>> devel mailing list
>> devel@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/devel
>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
>
>
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> +94776509215
> http://about.me/callkalpa
>



-- 
Best Regards,

Kalpa Welivitigoda
+94776509215
http://about.me/callkalpa
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Updating to f23 beta from f22

[Kalpa Welivitigoda]

On Thu, Sep 24, 2015 at 3:51 PM, Peter Robinson 
wrote:

> On Thu, Sep 24, 2015 at 11:08 AM, Kalpa Welivitigoda
>  wrote:
> > Hi all,
> >
> > How can I update to f23 beta from f22?
>
> Same way as on other releases, with fedup (see thread on this list
> against the release announcement for details) or "dnf distro-sync" as
> per docs [1]
>
> Peter
>
> [1]
> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23


Thanks Peter :-)


>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct




-- 
Best Regards,

Kalpa Welivitigoda
+94776509215
http://about.me/callkalpa
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Updating to f23 beta from f22

[Peter Robinson]

On Thu, Sep 24, 2015 at 11:08 AM, Kalpa Welivitigoda
 wrote:
> Hi all,
>
> How can I update to f23 beta from f22?

Same way as on other releases, with fedup (see thread on this list
against the release announcement for details) or "dnf distro-sync" as
per docs [1]

Peter

[1] 
https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

virtual provides/metapackage for various OpenCL implementations

[Dominik 'Rathann' Mierzejewski]

Dear maintainers,
I've just enabled OpenCL support in the gromacs package[1] and would
like to express a weak dependency on an OpenCL implementation, but I
have no way of doing so at the moment.

We have three packages which provide OpenCL implementations:
beignet - Intel GPUs
mesa-libOpenCL - AMD GPUs (only?)
pocl - CPU-based

Would it make sense to add a virtual provide to each of the packages
to mean the all provide a "vendor" OpenCL implementation? For example,
Provides: opencl-driver

Then, any package that makes use of OpenCL could add
Requires/Recommends/Suggests: opencl-driver

Another approach could be to create a meta package (named
opencl-drivers, for example - similar to xorg-x11-drivers) which would
depend on all vendor-specific implementations.

I guess the second approach is more fool-proof. Comments?

Regards,
Dominik

[1] 
http://pkgs.fedoraproject.org/cgit/gromacs.git/commit/?id=dbabc099d66902daa094478024a8a331822b78bc
-- 
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Updating to f23 beta from f22

[Kalpa Welivitigoda]

Hi all,

How can I update to f23 beta from f22?

-- 
Best Regards,

Kalpa Welivitigoda
+94776509215
http://about.me/callkalpa
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: dnf upgrade won't upgrade, but yum-deprecated does!!

[Christopher Meng]

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

-- 

Yours sincerely,
Christopher Meng

http://awk.io
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: GNOME 3.18.0 megaupdate

[Kalev Lember]

On 09/24/2015 11:10 AM, Kalpa Welivitigoda wrote:
> 
> 
> On Thu, Sep 24, 2015 at 2:36 PM, Richard Hughes  > wrote:
> 
> On 24 September 2015 at 10:04, Kalpa Welivitigoda
> mailto:callka...@gmail.com>> wrote:
> > Will the GNOME 3.18 updates be available to f22 as well?
> 
> There's no plan to do this, sorry.
> 
> 
> Thanks for the info. Seems we need to wait till f23 is out :-)

... or install the beta! :)

-- 
Kalev
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: GNOME 3.18.0 megaupdate

[Kalpa Welivitigoda]

On Thu, Sep 24, 2015 at 2:36 PM, Richard Hughes  wrote:

> On 24 September 2015 at 10:04, Kalpa Welivitigoda 
> wrote:
> > Will the GNOME 3.18 updates be available to f22 as well?
>
> There's no plan to do this, sorry.
>

Thanks for the info. Seems we need to wait till f23 is out :-)


>
> Richard
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>



-- 
Best Regards,

Kalpa Welivitigoda
+94776509215
http://about.me/callkalpa
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

dnf upgrade won't upgrade, but yum-deprecated does!!

[Joachim Backes]

Hi,

I'm running F23.

I tried to upgrade the gnome bulk update by using dnf, but nothing happens:


sudo dnf upgrade --enablerepo=updates-testing
Last metadata expiration check performed 0:59:27 ago on Thu Sep 24 
10:06:44 2015.

Dependencies resolved.
Nothing to do.
Complete!

But using yum-deprecated shows a lot of updates to be done!

Why that difference? dnf bug?

Kind regards

Joachim Backes

--

Fedora release 23 (Twenty Three)
Kernel-4.2.1-300.fc23.x86_64


Joachim Backes 
http://www-user.rhrk.uni-kl.de/~backes/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: GNOME 3.18.0 megaupdate

[Richard Hughes]

On 24 September 2015 at 10:04, Kalpa Welivitigoda  wrote:
> Will the GNOME 3.18 updates be available to f22 as well?

There's no plan to do this, sorry.

Richard
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: GNOME 3.18.0 megaupdate

[Kalpa Welivitigoda]

Hi Kalev,

Will the GNOME 3.18 updates be available to f22 as well?

On Thu, Sep 24, 2015 at 1:59 PM, Kalev Lember  wrote:

> On 09/21/2015 12:12 PM, Kalev Lember wrote:
> > Hi all,
> >
> > GNOME 3.18.0 is going to be released this week and I'll be wrangling the
> > builds for Fedora. Same as with the pre-releases we've built so far, we
> > are still using the f23-gnome side tag in koji for preparing everything.
> > If you are helping with builds, please use:
> >
> >   $ fedpkg build --target f23-gnome
> >
> > I'll take care of submitting them all in a single bodhi update ticket
> > later this week.
>
> It's in updates-testing now:
> https://bodhi.fedoraproject.org/updates/FEDORA-2015-16555
>
> --
> Kalev
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>



-- 
Best Regards,

Kalpa Welivitigoda
+94776509215
http://about.me/callkalpa
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Agenda for Env-and-Stacks WG meeting (2015-09-24)

[Honza Horak]

WG meeting will be at 12:00 UTC (9:00 EST, 14:00 Brno, 8:00 Boston, 
21:00 Tokyo, 22:00 Brisbane) in #fedora-meeting-2 on Freenode.


= Topics =

* Fedora dockerfiles -- versions, size, more involvement from E&S

* Software Collections use cases in semi-containerized world

Honza
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 Branched 20150923 compose check report

[Adam Williamson]

On Wed, 2015-09-23 at 10:25 -0400, Fedora compose checker wrote:
> Missing expected images:
> 
> Cloud disk raw i386
> Cloud disk raw x86_64
> Cloud_atomic disk raw x86_64
> Generic boot i386
> Generic boot x86_64

https://kojipkgs.fedoraproject.org/mash/branched-20150923/logs/pungify-x86_64.log

2015-09-23 11:10:47,017:   dnf.exceptions.DepsolveError: nothing provides 
xserver-abi(videodrv-19) >= 0 needed by 
tigervnc-server-module-1.5.0-2.fc23.x86_64
  dnf.exceptions.DepsolveError: nothing provides xserver-abi(videodrv-19) >= 0 
needed by tigervnc-server-module-1.5.0-2.fc23.x86_64

> No images in this compose but not 23 Branched 20150922
> 
> No images in 23 Branched 20150922 but not this.
> 
> Failed openQA tests: 5 of 5
> 
> ID: 3290  Test: i386 kde_live default_install
> ID: 3289  Test: i386 workstation_live default_install
> ID: 3288  Test: x86_64 workstation_live default_install@uefi
> ID: 3287  Test: x86_64 workstation_live default_install
> ID: 3286  Test: x86_64 kde_live default_install

I don't know why the tests are failing ATM, I guess I should stop
fiddling around with scripts and start doing what they're paying me
for...
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Bug 1265966] New: Upgrade perl-Nagios-Plugin to 0.990000

[bugzilla]

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

Bug ID: 1265966
   Summary: Upgrade perl-Nagios-Plugin to 0.99
   Product: Fedora
   Version: rawhide
 Component: perl-Nagios-Plugin
  Keywords: FutureFeature
  Assignee: psab...@redhat.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-de...@lists.fedoraproject.org, psab...@redhat.com



Latest Fedora delivers 0.37 version. Upstream released 0.99. Please
upgrade.

Also please enable release monitoring service to receive notifications about
future releases.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Re: Orphaned Packages in rawhide (2015-09-21)

[Matthias Runge]

On Mon, Sep 21, 2015 at 11:35:30AM +, opensou...@till.name wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> tinymceorphan, mrunge, ngompa, rhe   0 weeks ago   
> tinymce-spellchecker   orphan, mrunge, ngompa, rhe   0 weeks ago   
...
> Depending on: tinymce (1), status change: 2015-09-20 (0 weeks ago)
>   python-django-tinymce (maintained by: yuwang, mrunge)
>   python-django-tinymce-1.5.2-2.fc21.noarch requires tinymce = 
> 3.5.10-3.fc23

Those 3 package should imho just go away.

Any takers? Otherwise I'd retire them in 2 weeks.
-- 
Matthias Runge 
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: GNOME 3.18.0 megaupdate

[Kalev Lember]

On 09/21/2015 12:12 PM, Kalev Lember wrote:
> Hi all,
> 
> GNOME 3.18.0 is going to be released this week and I'll be wrangling the
> builds for Fedora. Same as with the pre-releases we've built so far, we
> are still using the f23-gnome side tag in koji for preparing everything.
> If you are helping with builds, please use:
> 
>   $ fedpkg build --target f23-gnome
> 
> I'll take care of submitting them all in a single bodhi update ticket
> later this week.

It's in updates-testing now:
https://bodhi.fedoraproject.org/updates/FEDORA-2015-16555

-- 
Kalev
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Vít Ondruch]

Dne 22.9.2015 v 11:07 Matej Stuchlik napsal(a):
>
> When it comes to python3, one way to shave off ~9MiB from python3-libs, and
> possibly quite a bit more overall, would be to not install both optimized and
> unoptimized bytecode, as we do now, but just the unoptimized one (the 
> performance
> hit should be very small).

Isn't it time to use %filetriggers to generate the bytecode instead of
shipping it in packages? You would save a lot of space, you could drop
the most of the python{2,3} packages etc.

Also, you might consider to ship the precompiled bytecode just
optionally, using recommends.

On contrary, if you insist on shipping the bytecode, why you don't drop
the .py files? I see a lot of duplication all around python packages 


Vít


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct