Re: Finding all the source packages that include a copy of valgrind.h

2014-09-13 Thread Ralf Corsepius

On 09/13/2014 01:52 PM, Florian Weimer wrote:

On 09/12/2014 06:25 PM, Michael Cronenworth wrote:

You'll have to download all the source and perform a massive grep.


You have to unpack the sources before the grep, which can be quite a
challenge because SPEC files aren't declarative.  The %prep stage
sometimes even needs build dependencies already installed. :-(


This is the list, I got from doing something similar as you outlined 
(unpackaging src.rpm, running prep, and find -name "valgrind.h")


0ad-0.0.16-10.fc22
cockpit-0.23-1.fc22
condor-8.1.4-7.a1a7df5.fc22
exim-4.84-3.fc22
fwbuilder-5.1.0.3599-5.fc20
gcr-3.13.91-1.fc22
gearmand-1.1.12-8.fc22
ghostscript-9.14-6.fc22
glib2-2.41.4-3.fc22
gperftools-2.2.1-2.fc22
ipxe-20140303-3.gitff1e7fc7.fc22
libgnome-keyring-3.12.0-4.fc22
libmemcached-1.0.18-4.fc22
libsecret-0.18-4.fc22
lwp-2.6-10.fc22
mingw-glib2-2.41.2-1.fc22
mingw-qt5-qtjsbackend-5.1.1-4.fc21
mongodb-2.4.9-7.fc22
mono-2.10.8-7.fc21
openvswitch-2.3.0-1.fc22
pidgin-2.10.9-5.fc22
planner-0.14.6-17.fc22
qemu-2.1.1-1.fc22
R-3.1.1-5.fc22
re2-20131024-3.fc22
realmd-0.15.1-4.fc22
rubygem-passenger-4.0.18-9.fc22
squid-3.4.7-1.fc22
v8-3.14.5.10-13.fc22
valgrind-3.10.0-1.fc22
wine-mono-4.5.2-4.fc21

Ralf

--
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: Improving the offline updates user experience

2014-09-13 Thread Corey Sheldon
the keys are in kernelspace IIRC and thus updated / passed on initrd
/initramfs updates and kernel updates

Corey W Sheldon
Freelance IT Consultant, Multi-Discipline Tutor
310.909.7672
www.facebook.com/1stclassmobileshine

On Sat, Sep 13, 2014 at 7:01 PM, Ian Pilcher  wrote:

> On 09/13/2014 03:59 AM, Fred New wrote:
> > One step up from this would be something like a kpatch process in rpm
> > combined with packaged metadata that replaces in-memory modules so that
> > reboots wouldn't be necessary. Yeh, probably impossible.
>
> This has almost certainly already been considered by people smarter than
> me, but it occurs to me that there's no reason that kexec couldn't some-
> how pass LUKS/dm-crypt keys to the new kernel.
>
> --
> 
> Ian Pilcher arequip...@gmail.com
>  "I grew up before Mark Zuckerberg invented friendship" 
> 
>
> --
> 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: fakesystemd package breaking builds

2014-09-13 Thread Sérgio Basto
On Seg, 2014-09-08 at 02:36 +0100, Sérgio Basto wrote: 
> On Qua, 2014-08-27 at 15:30 +0200, Václav Pavlín wrote: 
> > Hi,
> > 
> > There is new fakesystemd build for F21 which should fix the breakage, 
> > sorry.
> 
> Hi, 
> I think this still breaking rpmfusion builds , 

no longer breaks rpmfusion builds  

Thanks,  


> in some packages like
> kplayer [1]. rpmfusion got a older version of Mock,  Version: 1.1.21 [2]
> 
> 
> ends with a strange :  
> --> 6:kdelibs-devel-4.14.0-2.fc21.x86_64 
> DEBUG util.py:257:  Error: fakesystemd conflicts with systemd
> 
> [1]
> http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_free/21087-kplayer-0.7.0-11.20081211cvs.fc21/x86_64/root.log
>  
> [2]
> http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_free/21087-kplayer-0.7.0-11.20081211cvs.fc21/x86_64/state.log
>  
> 
> 
> -- 
> Sérgio M. B.
> 

-- 
Sérgio M. B.

-- 
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: Improving the offline updates user experience

2014-09-13 Thread Ian Pilcher
On 09/13/2014 03:59 AM, Fred New wrote:
> One step up from this would be something like a kpatch process in rpm
> combined with packaged metadata that replaces in-memory modules so that
> reboots wouldn't be necessary. Yeh, probably impossible.

This has almost certainly already been considered by people smarter than
me, but it occurs to me that there's no reason that kexec couldn't some-
how pass LUKS/dm-crypt keys to the new kernel.

-- 

Ian Pilcher arequip...@gmail.com
 "I grew up before Mark Zuckerberg invented friendship" 


-- 
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: F21/F22 mass rebuild

2014-09-13 Thread Richard Fearn
> Odd. It seems like it commited to master fine, but for some reason the
> build never happened.
>
> You should be able to just do a 'fedpkg build' in master and things
> should be back on track.

I thought so, and just did that, and it built fine:

  http://koji.fedoraproject.org/koji/buildinfo?buildID=577111

Hopefully it's a one-off and not part of a bigger problem...

Thanks,

Richard

-- 
Richard Fearn
richardfe...@gmail.com
-- 
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: Samba as AD DC

2014-09-13 Thread Pete Travis
On Sep 7, 2014 11:58 AM, "Simo Sorce"  wrote:
>
> On Sun, 2014-09-07 at 01:12 -0300, Sergio Belkin wrote:
> > Hi,
> >
> > Is (Samba) Fedora 20 still not capable of being Active Directory Domain
> > Controller?
> >
> > I mean is that page current:
> > http://fedoraproject.org/wiki/Features/Samba4#Current_status ?
> >
> > Thanks in advance!
>
> It is current, and Samba in F20 will never have the AD bits.
> Maybe F22, or perhaps even F21, the work to replace Heimdal with MIT is
> proceeding well enough.
>
> Simo.
>
> --
> Simo Sorce * Red Hat, Inc * New York
>
> --

Is there a broadly scoped tracking bug for this effort, Simo?

--Pete
-- 
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: F21/F22 mass rebuild

2014-09-13 Thread Dan Horák
On Sat, 13 Sep 2014 10:51:10 -0600
Kevin Fenzi  wrote:

> On Sat, 13 Sep 2014 13:44:59 +0200
> Richard Fearn  wrote:
> 
> > Hi,
> > 
> > I've got a question about the last mass rebuild:
> > 
> >   https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
> > 
> > For a couple of my packages:
> > 
> >   http://koji.fedoraproject.org/koji/packageinfo?packageID=6133
> >   http://koji.fedoraproject.org/koji/packageinfo?packageID=4673
> > 
> > there was a rebuild for both F21 and F22. However for ncdu:
> > 
> >   http://koji.fedoraproject.org/koji/packageinfo?packageID=6127
> > 
> > there was only an F21 rebuild. Does that matter?
> ...snip...
> 
> Odd. It seems like it commited to master fine, but for some reason the
> build never happened. 

I have seen couple builds that failed eg. during buildSRPMFromSCM on
arm hosts because they could initialize buildroot due network failures
or read-only filesystem. In such case you won't see an entry in builds
at all. This example might be the case. 


Dan
-- 
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: F21/F22 mass rebuild

2014-09-13 Thread Kevin Fenzi
On Sat, 13 Sep 2014 13:44:59 +0200
Richard Fearn  wrote:

> Hi,
> 
> I've got a question about the last mass rebuild:
> 
>   https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
> 
> For a couple of my packages:
> 
>   http://koji.fedoraproject.org/koji/packageinfo?packageID=6133
>   http://koji.fedoraproject.org/koji/packageinfo?packageID=4673
> 
> there was a rebuild for both F21 and F22. However for ncdu:
> 
>   http://koji.fedoraproject.org/koji/packageinfo?packageID=6127
> 
> there was only an F21 rebuild. Does that matter?
...snip...

Odd. It seems like it commited to master fine, but for some reason the
build never happened. 

You should be able to just do a 'fedpkg build' in master and things
should be back on track. 

kevin


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: bohdi update failed

2014-09-13 Thread Kevin Fenzi
On Fri, 12 Sep 2014 18:28:15 -0400
Neal Becker  wrote:

> bodhi -n -r F20 -t enhancement 'see http://kdiff3.sourceforge.net/' 
> kdiff3-0.9.98-2.fc20
> Creating a new update for see 
> http://kdiff3.sourceforge.net/,kdiff3-0.9.98-2.fc20
> Password for nbecker: 
> Creating a new update for see 
> http://kdiff3.sourceforge.net/,kdiff3-0.9.98-2.fc20
> ServerError(https://admin.fedoraproject.org/updates/save, 200, Error
> returned from json module while processing
> https://admin.fedoraproject.org/updates/save: Expecting value: line 1
> column 1 (char 0)) Traceback (most recent call last):
>   File "/usr/bin/bodhi", line 249, in main
> data = bodhi.save(**extra_args)
>   File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py",
> line 111, in save
> 'bugs': bugs,
>   File
> "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py", line
> 369, in send_request auth_params=auth_params, retries=retries,
> timeout=timeout) File
> "/usr/lib/python2.7/site-packages/fedora/client/proxyclient.py", line
> 505, in send_request {'url': to_bytes(url), 'err': to_bytes(e)})
> ServerError:
> ServerError(https://admin.fedoraproject.org/updates/save, 200, Error
> returned from json module while processing
> https://admin.fedoraproject.org/updates/save: Expecting value: line 1
> column 1 (char 0))

Can you file a ticket on this? 

https://fedorahosted.org/bodhi/

We will get it figured out... 

kevin



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: gnome-sudoku in F21

2014-09-13 Thread Joachim Backes
On 09/13/2014 03:53 PM, Florian Müllner wrote:
> On Sat, Sep 13, 2014 at 3:40 PM, Joachim Backes
>  wrote:
>> In gnome-sudoku (gnome-sudoku-3.13.90-3.fc21.x86_64) for F21 I'm missing
>> the feature allowing to print multiple unsolved sudokus.
> 
> You should use a user list/forum for these kinds of questions, as it
> is not related to developing Fedora in any way. That said, the
> functionality you are looking for moved to the application menu (next
> to the "Activities" button).
> 
> -- Florian
> 
> PS: They say a picture is worth a thousand words - screenshot attached ...
> 

Hi Florian,

sorry for noises on the devel list. Problem solved (using your attached
graphics).

Kind regards

Joachim Backes

-- 

Fedora release 21 (Twenty One)
Kernel-3.16.2-301.fc21.x86_64


Joachim Backes 
https://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-sudoku in F21

2014-09-13 Thread Florian Müllner
On Sat, Sep 13, 2014 at 3:40 PM, Joachim Backes
 wrote:
> In gnome-sudoku (gnome-sudoku-3.13.90-3.fc21.x86_64) for F21 I'm missing
> the feature allowing to print multiple unsolved sudokus.

You should use a user list/forum for these kinds of questions, as it
is not related to developing Fedora in any way. That said, the
functionality you are looking for moved to the application menu (next
to the "Activities" button).

-- Florian

PS: They say a picture is worth a thousand words - screenshot attached ...
-- 
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-sudoku in F21

2014-09-13 Thread Ankur Sinha
On Sat, 2014-09-13 at 15:40 +0200, Joachim Backes wrote:
> Dear F21 developers,

Hi Joachim,

> In gnome-sudoku (gnome-sudoku-3.13.90-3.fc21.x86_64) for F21 I'm
> missing
> the feature allowing to print multiple unsolved sudokus. This was
> possible in the previous Fedora version(s).

I just checked it out. The option is in the menu at the top panel.
-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG



signature.asc
Description: This is a digitally signed message part
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

gnome-sudoku in F21

2014-09-13 Thread Joachim Backes

Dear F21 developers,

In gnome-sudoku (gnome-sudoku-3.13.90-3.fc21.x86_64) for F21 I'm missing
the feature allowing to print multiple unsolved sudokus. This was
possible in the previous Fedora version(s).

Kind regards

Joachim Backes

-- 

Fedora release 21 (Twenty One)
Kernel-3.16.2-301.fc21.x86_64


Joachim Backes 
https://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: Unresponsive maintainer Germán Racca (skytux)

2014-09-13 Thread Sérgio Basto
skytux is alive in ask and in stackoverflow, at least 

https://ask.fedoraproject.org/en/users/429/skytux/
http://stackoverflow.com/users/1507137/skytux


On Sáb, 2014-09-13 at 05:34 -0400, Christopher Meng wrote: 
> On Wed, Sep 10, 2014 at 2:57 PM, Kevin Fenzi  wrote:
> > I have orphaned skytux'es packages:
> > jwm -- Joe's Window Manager ( master f21 f20 f19 )
> 
> jwm taken.
> 
> Yours sincerely,
> Christopher Meng
> 
> http://cicku.me

-- 
Sérgio M. B.

-- 
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: Finding all the source packages that include a copy of valgrind.h

2014-09-13 Thread Florian Weimer

On 09/12/2014 06:25 PM, Michael Cronenworth wrote:

You'll have to download all the source and perform a massive grep.


You have to unpack the sources before the grep, which can be quite a 
challenge because SPEC files aren't declarative.  The %prep stage 
sometimes even needs build dependencies already installed. :-(


--
Florian Weimer / Red Hat Product Security
--
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: F21/F22 mass rebuild

2014-09-13 Thread पराग़
Hi,

On Sat, Sep 13, 2014 at 5:14 PM, Richard Fearn  wrote:
> Hi,
>
> I've got a question about the last mass rebuild:
>
>   https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
>
> For a couple of my packages:
>
>   http://koji.fedoraproject.org/koji/packageinfo?packageID=6133
>   http://koji.fedoraproject.org/koji/packageinfo?packageID=4673
>
> there was a rebuild for both F21 and F22. However for ncdu:
>
>   http://koji.fedoraproject.org/koji/packageinfo?packageID=6127
>
> there was only an F21 rebuild. Does that matter?
>
> It's a bit hard to tell, as the script linked from the wiki page is
> the one used for the F21 rebuild back in June; and the date after
> which maintainer builds count towards the latest rebuild is
> 2014-06-05, the same date as for the F21 mass rebuild (as opposed to
> some date in August).
>

You can find details about that special mass rebuild in thread
https://lists.fedoraproject.org/pipermail/devel/2014-August/201635.html

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

F21/F22 mass rebuild

2014-09-13 Thread Richard Fearn
Hi,

I've got a question about the last mass rebuild:

  https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild

For a couple of my packages:

  http://koji.fedoraproject.org/koji/packageinfo?packageID=6133
  http://koji.fedoraproject.org/koji/packageinfo?packageID=4673

there was a rebuild for both F21 and F22. However for ncdu:

  http://koji.fedoraproject.org/koji/packageinfo?packageID=6127

there was only an F21 rebuild. Does that matter?

It's a bit hard to tell, as the script linked from the wiki page is
the one used for the F21 rebuild back in June; and the date after
which maintainer builds count towards the latest rebuild is
2014-06-05, the same date as for the F21 mass rebuild (as opposed to
some date in August).

Thanks,

Richard

-- 
Richard Fearn
richardfe...@gmail.com
-- 
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: Samba as AD DC

2014-09-13 Thread Alexander Bokovoy

On Mon, 08 Sep 2014, Simone Caronni wrote:

Hello,

2014-09-07 14:58 GMT-03:00 Simo Sorce :


On Sun, 2014-09-07 at 01:12 -0300, Sergio Belkin wrote:

> Is (Samba) Fedora 20 still not capable of being Active Directory Domain
> Controller?

It is current, and Samba in F20 will never have the AD bits.
Maybe F22, or perhaps even F21, the work to replace Heimdal with MIT is
proceeding well enough.




if you're interested, I've written a blog post on how to enable Samba 4 AD
functionality on a Fedora / RHEL system. All the bits are there, you simply
need to rebuild the Samba package with domain controller support and create
a service file for it:

http://negativo17.org/samba-4-active-directory-with-bind-dlz-zones-dynamic-dns-updates-windows-static-rpc/

Of course this re-enables the bundled Heimdal Kerberos implementation, but
it's rock stable. Simo Sorce also promptly fixed an issue in the Kerberos
libraries after I wrote it (thanks again!):

http://negativo17.org/samba-4-active-directory-with-bind-dlz-zones-dynamic-dns-updates-windows-static-rpc-update/

I've had it running for the past year without issues.

Please note that things will not work well when both Heimdal and MIT
libraries could be loaded into the same address space. This affects, for
example, SSSD which uses many Samba libraries, including libldb, which
will have some modules added from Samba AD DC that link against Heimdal
but there are many more issues lurking around hard to detect and debug.

Also, if you start using Heimdal-linked Samba binaries that expect
Kerberos ccaches and SSSD linked with MIT Kerberos, you'll see problems
because Heimdal does not understand certain features of MIT's ccaches.
It is gonna break one way or another (including default type of ccaches
in /etc/krb5.conf in Fedora, which is kernel keyring).


--
/ Alexander Bokovoy
--
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-21 Branched report: 20140913 changes

2014-09-13 Thread Fedora Branched Report
Compose started at Sat Sep 13 07:15:02 UTC 2014

Broken deps for armhfp
--
[APLpy]
APLpy-0.9.8-5.fc21.noarch requires pywcs
[PyKDE]
PyKDE-3.16.6-14.fc20.armv7hl requires sip-api(10) >= 0:10.0
[PyQuante]
PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
[audtty]
audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2
[authhub]
authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0
[couchdb]
couchdb-1.6.0-9.fc21.armv7hl requires erlang(erl_nif_version) = 0:2.4
couchdb-1.6.0-9.fc21.armv7hl requires erlang(erl_drv_version) = 0:2.2
[cp2k]
cp2k-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21
cp2k-mpich-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libmpi_usempi.so.1
cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
[csound]
csound-java-5.19.01-1.fc20.armv7hl requires libgcj_bc.so.1
csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat
csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat
csound-java-5.19.01-1.fc20.armv7hl requires java-1.5.0-gcj
csound-tk-5.19.01-1.fc20.armv7hl requires libtk8.5.so
csound-tk-5.19.01-1.fc20.armv7hl requires libtcl8.5.so
[deltacloud-core]
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudservers)
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudfiles)
[docker-registry]
docker-registry-0.7.3-1.fc21.noarch requires docker-io
[dragonegg]
dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
[edelib]
edelib-2.1-5.fc21.armv7hl requires libedelib.so
edelib-devel-2.1-5.fc21.armv7hl requires libedelib.so
[ejabberd]
ejabberd-2.1.13-8.fc21.armv7hl requires erlang(erl_drv_version) = 0:2.2
[elpa]
elpa-openmpi-2013.11-4.008.fc21.armv7hl requires libmpi_usempi.so.1
[erlang-basho_metrics]
erlang-basho_metrics-1.0.0-10.fc21.armv7hl requires 
erlang(erl_nif_version) = 0:2.4
[erlang-bitcask]
erlang-bitcask-1.6.3-1.fc20.armv7hl requires erlang(erl_nif_version) = 
0:2.4
[erlang-cl]
erlang-cl-1.2.1-2.fc21.armv7hl requires erlang(erl_nif_version) = 0:2.4
[erlang-ebloom]
erlang-ebloom-1.1.2-4.fc21.armv7hl requires erlang(erl_nif_version) = 
0:2.4
[erlang-eleveldb]
erlang-eleveldb-1.3.2-2.fc20.armv7hl requires erlang(erl_nif_version) = 
0:2.4
[erlang-emmap]
erlang-emmap-0-0.8.git05ae1bb.fc21.armv7hl requires 
erlang(erl_nif_version) = 0:2.4
[erlang-erlsyslog]
erlang-erlsyslog-0.6.2-6.fc21.armv7hl requires erlang(erl_drv_version) 
= 0:2.2
[erlang-esasl]
erlang-esasl-0.1-15.20120116git665cc80.fc21.armv7hl requires 
erlang(erl_drv_version) = 0:2.2
[erlang-esdl]
erlang-esdl-1.3.1-3.fc21.armv7hl requires erlang(erl_drv_version) = 
0:2.2
[erlang-js]
erlang-js-1.2.2-5.fc21.armv7hl requires erlang(erl_drv_version) = 0:2.2
[erlang-sd_notify]
erlang-sd_notify-0.1-1.fc21.armv7hl requires erlang(erl_nif_version) = 
0:2.4
[erlang-skerl]
erlang-skerl-1.1.0-7.fc21.armv7hl requires erlang(erl_nif_version) = 
0:2.4
[erlang-snappy]
erlang-snappy-1.0.3-0.7.git80db168.fc21.armv7hl requires 
erlang(erl_nif_version) = 0:2.4
[eucalyptus]
eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.armv7hl 
requires hibernate3-jbosscache >= 0:3.6.10-7
[fatrat]
1:fatrat-1.2.0-0.21.beta2.fc21.armv7hl requires 
libtorrent-rasterbar.so.7
[flashrom]
flashrom-0.9.6.1-5.svn1705.fc20.armv7hl requires libftdi.so.1
[flush]
flush-0.9.12-10.fc21.armv7hl requires libtorrent-rasterbar.so.7
[freesteam]
freesteam-ascend-2.1-6.20140724svn753.fc21.armv7hl requires 
libascend.so.1
[gcc-python-plugin]
gcc-python2-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 
0:4.8.2-14.fc21
gcc-python2-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires 
libpython3.3dm.so.1.0
gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 
0:4.8.2-14.fc21
gcc-python3-plugin-0.12-18.fc21.armv7hl requires libpython3.3m.so.1.0
gcc-python3-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
[gedit-valencia]
gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires 
libvala-0.24.so.0
[ghc-hint]
ghc-hint-devel-0.4.2.0-2.fc21.armv7hl requires 
ghc-devel(ghc-7.6.3-9662c0f342b2d5c9e1cd2b6330e697bc)
[gnome-python2-desktop]
gnome-python2-metacity-2.32.0-18.fc21.armv7hl requires 
libmetacity-private.so.0
[gnome-shell-extension-pomodoro]
gnome-shell-extension-pomodoro-0.10.0-4.fc21.armv7hl requires 
libupower-glib.so.2
[gofer]
ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) >= 0:0.16.0
[hibernate-search]
hibe

rawhide report: 20140913 changes

2014-09-13 Thread Fedora Rawhide Report
Broken deps for i386
--
[PyQuante]
PyQuante-libint-1.6.4-11.fc22.1.i686 requires libint(x86-32) = 
0:1.1.6-2.fc21
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[audtty]
audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2
[authhub]
authhub-0.1.2-3.fc19.i686 requires libjson.so.0
[aws]
aws-devel-3.1.0-6.fc21.i686 requires libgrypt-devel
[blender]
1:blender-2.71-3.fc22.i686 requires libOpenCOLLADAStreamWriter.so.0.1
1:blender-2.71-3.fc22.i686 requires 
libOpenCOLLADASaxFrameworkLoader.so.0.1
1:blender-2.71-3.fc22.i686 requires libOpenCOLLADAFramework.so.0.1
1:blender-2.71-3.fc22.i686 requires libOpenCOLLADABaseUtils.so.0.1
1:blender-2.71-3.fc22.i686 requires libMathMLSolver.so.0.1
1:blender-2.71-3.fc22.i686 requires libGeneratedSaxParser.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires 
libOpenCOLLADAStreamWriter.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires 
libOpenCOLLADASaxFrameworkLoader.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADAFramework.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADABaseUtils.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libMathMLSolver.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libGeneratedSaxParser.so.0.1
[bustle]
bustle-0.4.7-3.fc22.i686 requires libHSsetlocale-1.0.0-ghc7.6.3.so
[compat-gcc-34]
compat-gcc-34-c++-3.4.6-29.fc19.i686 requires libstdc++ < 0:4.9.0
[cp2k]
cp2k-2.5.1-8.fc22.i686 requires libint(x86-32) = 0:1.1.6-2.fc21
cp2k-mpich-2.5.1-8.fc22.i686 requires libint(x86-32) = 0:1.1.6-2.fc21
cp2k-openmpi-2.5.1-8.fc22.i686 requires libmpi_usempi.so.1
cp2k-openmpi-2.5.1-8.fc22.i686 requires libint(x86-32) = 0:1.1.6-2.fc21
[csound]
csound-java-5.19.01-1.fc20.i686 requires libgcj_bc.so.1
csound-java-5.19.01-1.fc20.i686 requires java-gcj-compat
csound-java-5.19.01-1.fc20.i686 requires java-gcj-compat
csound-java-5.19.01-1.fc20.i686 requires java-1.5.0-gcj
csound-tk-5.19.01-1.fc20.i686 requires libtk8.5.so
csound-tk-5.19.01-1.fc20.i686 requires libtcl8.5.so
[debconf]
debconf-1.5.53-1.fc22.noarch requires perl(:MODULE_COMPAT_5.18.2)
[debhelper]
debhelper-9.20140613-2.fc22.noarch requires perl(:MODULE_COMPAT_5.18.2)
[deltacloud-core]
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudservers)
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudfiles)
[dnssec-check]
dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14
dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14
[dragonegg]
dragonegg-3.4-0.3.rc0.fc21.i686 requires gcc = 0:4.8.2-14.fc21
[edelib]
edelib-2.1-5.fc22.i686 requires libedelib.so
edelib-devel-2.1-5.fc22.i686 requires libedelib.so
[elk]
elk-openmpi-2.3.22-7.fc21.i686 requires libmpi_usempi.so.1
[elpa]
elpa-openmpi-2013.11-4.008.fc21.i686 requires libmpi_usempi.so.1
[eucalyptus]
eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.i686 requires 
hibernate3-jbosscache >= 0:3.6.10-7
[fatrat]
1:fatrat-1.2.0-0.21.beta2.fc22.i686 requires libtorrent-rasterbar.so.7
[flush]
flush-0.9.12-10.fc22.i686 requires libtorrent-rasterbar.so.7
[freefem++]
freefem++-3.30-5.fc22.i686 requires libcholmod.so.2
freefem++-mpich-3.30-5.fc22.i686 requires libcholmod.so.2
freefem++-openmpi-3.30-5.fc22.i686 requires libcholmod.so.2
[ga]
ga-openmpi-5.3b-9.fc21.i686 requires libmpi_usempi.so.1
[gcc-python-plugin]
gcc-python2-debug-plugin-0.12-18.fc21.i686 requires gcc = 
0:4.8.2-14.fc21
gcc-python2-plugin-0.12-18.fc21.i686 requires gcc = 0:4.8.2-14.fc21
gcc-python3-debug-plugin-0.12-18.fc21.i686 requires 
libpython3.3dm.so.1.0
gcc-python3-debug-plugin-0.12-18.fc21.i686 requires gcc = 
0:4.8.2-14.fc21
gcc-python3-plugin-0.12-18.fc21.i686 requires libpython3.3m.so.1.0
gcc-python3-plugin-0.12-18.fc21.i686 requires gcc = 0:4.8.2-14.fc21
[gedit-valencia]
gedit-valencia-0.4.0-1.20131223git94442bf.fc21.i686 requires 
libvala-0.24.so.0
[ghc-hgettext]
ghc-hgettext-0.1.30-3.fc22.i686 requires 
libHSsetlocale-1.0.0-ghc7.6.3.so
ghc-hgettext-0.1.30-3.fc22.i686 requires 
ghc(setlocale-1.0.0-fa663a40688afbabfd6017337b0554c3)
ghc-hgettext-devel-0.1.30-3.fc22.i686 requires 
libHSsetlocale-1.0.0-ghc7.6.3.so
ghc-hgettext-devel-0.1.30-3.fc22.i686 requires 
ghc-devel(setlocale-1.0.0-fa663a40688afbabfd6017337b0554c3)
[gnome-python2-desktop]
gnome-python2-metacity-2.32.0-18.fc21.i686 requires 
libmetacity-private.so.0
[gnome-shell-extension-pomodoro]
gnome-shell-extension-pomodoro-0.10.0-4.fc21.i686 requires 
libupower-glib.so.2
[gofer]
ruby-gofer-0.77.1-2.fc21.

Re: Unresponsive maintainer Germán Racca (skytux)

2014-09-13 Thread Christopher Meng
On Wed, Sep 10, 2014 at 2:57 PM, Kevin Fenzi  wrote:
> I have orphaned skytux'es packages:
> jwm -- Joe's Window Manager ( master f21 f20 f19 )

jwm taken.

Yours sincerely,
Christopher Meng

http://cicku.me
-- 
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: Improving the offline updates user experience

2014-09-13 Thread Fred New
On Sat, Sep 13, 2014 at 3:32 AM, Chris Murphy 
wrote:

>
> On Sep 12, 2014, at 9:47 AM, Richard Hughes  wrote:
>
> > The *only* way to do this
> > securely and safely in the system we have now is in a clean pre-boot
> > environment,
>
> Mostly clean post-boot environment, with the system we have now?
>
> > What we could do is do updates on shutdown by basically killing
> > everything except PID 1, and then restart everything, but even then
> > that relies on no systemd or kernel updates being present.
>
> Even if the system is fully rebooted once, after the update is done in a
> post-boot environment, it's half the reboots needed now.
>
> One step up from this would be a way for packages to contain metadata
> indicating they need a reboot after an update; if none require it, then
> isolate graphical.target rather than a reboot.
>

One step up from this would be something like a kpatch process in rpm
combined with packaged metadata that replaces in-memory modules so that
reboots wouldn't be necessary. Yeh, probably impossible.

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