test to the new address
Sorry for the noise. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
second test to old address
Sorry for the noise again. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: how to install source packages?
Am 09.01.2010 18:26, schrieb Jud Craft: > In short, how do I install source packages? Have I missed an obvious > step or is it really unintuitive? I pretty much just do yumdownloader --source foo (yumdownloader is in yum-utils). That gives me the source rpm. I can then install it with rpm -Uvh foo.src.rpm and everything goes in ~/rpmbuild Hope this helps. Felix -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: how to install source packages?
lör 2010-01-09 klockan 12:26 -0500 skrev Jud Craft: > In short, how do I install source packages? Have I missed an obvious > step or is it really unintuitive? Have a look at the "fedora-cvs" command. It'll check out the needed parts from CVS directly. There's a whole bunch of commands for working with the Fedora package infrastructure. Look through the Fedora project wiki for more info. In some cases you can also use the "debuginfo-install" command to download the stuff needed to use gdb, if that's what you're after. /abo -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20100110 changes
Compose started at Sun Jan 10 08:15:09 UTC 2010 Broken deps for i386 -- PyKDE-3.16.6-1.fc13.i686 requires sip-api(6) >= 0:6.0 anjal-0.1.0-1.fc13.i686 requires libevolution-mail-shared.so.0 anjal-0.1.0-1.fc13.i686 requires libefilterbar.so.0 avogadro-libs-1.0.0-3.fc13.i686 requires sip-api(6) >= 0:6.0 cduce-0.5.3-3.fc13.i686 requires ocaml(runtime) = 0:3.11.1 cduce-0.5.3-3.fc13.i686 requires ocaml(Filename) = 0:7cd172f02b7ee9b8d7bda3bb92144951 cduce-0.5.3-3.fc13.i686 requires ocaml(Obj) = 0:c827f726ce05da709cf7de58fc15e324 cduce-0.5.3-3.fc13.i686 requires ocaml(Format) = 0:b7ba3152a5eec5609d6ab86e6c51eebb cduce-0.5.3-3.fc13.i686 requires ocaml(Printexc) = 0:fdf007941aa14d1a26323558012dbf52 cduce-0.5.3-3.fc13.i686 requires ocaml(Buffer) = 0:23af67395823b652b807c4ae0b581211 cduce-ocamlduce-0.5.3-3.fc13.i686 requires ocaml(Format) = 0:b7ba3152a5eec5609d6ab86e6c51eebb cduce-ocamlduce-0.5.3-3.fc13.i686 requires ocaml(Buffer) = 0:23af67395823b652b807c4ae0b581211 cduce-ocamlduce-0.5.3-3.fc13.i686 requires ocaml(runtime) = 0:3.11.1 cduce-ocamlduce-0.5.3-3.fc13.i686 requires ocaml(Obj) = 0:c827f726ce05da709cf7de58fc15e324 cluster-snmp-0.16.1-2.fc12.i686 requires libnetsnmp.so.15 ghc-HTTP-devel-4000.0.6-6.fc13.i686 requires ghc = 0:6.10.4 ghc-HTTP-devel-4000.0.6-6.fc13.i686 requires ghc = 0:6.10.4 ghc-HTTP-doc-4000.0.6-6.fc13.i686 requires ghc-doc = 0:6.10.4 ghc-HTTP-doc-4000.0.6-6.fc13.i686 requires ghc-doc = 0:6.10.4 ghc-HTTP-prof-4000.0.6-6.fc13.i686 requires ghc-prof = 0:6.10.4 ghc-cairo-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-cairo-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-cairo-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-cgi-devel-3001.1.7.1-3.fc13.i686 requires ghc = 0:6.10.4 ghc-cgi-devel-3001.1.7.1-3.fc13.i686 requires ghc = 0:6.10.4 ghc-cgi-doc-3001.1.7.1-3.fc13.i686 requires ghc-doc = 0:6.10.4 ghc-cgi-doc-3001.1.7.1-3.fc13.i686 requires ghc-doc = 0:6.10.4 ghc-cgi-prof-3001.1.7.1-3.fc13.i686 requires ghc-prof = 0:6.10.4 ghc-fgl-devel-5.4.2.2-1.fc12.i686 requires ghc = 0:6.10.4 ghc-fgl-devel-5.4.2.2-1.fc12.i686 requires ghc = 0:6.10.4 ghc-fgl-doc-5.4.2.2-1.fc12.i686 requires ghc-doc = 0:6.10.4 ghc-fgl-doc-5.4.2.2-1.fc12.i686 requires ghc-doc = 0:6.10.4 ghc-fgl-prof-5.4.2.2-1.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-gconf-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gconf-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gconf-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-ghc-paths-devel-0.1.0.5-8.fc12.i686 requires ghc = 0:6.10.4 ghc-ghc-paths-devel-0.1.0.5-8.fc12.i686 requires ghc = 0:6.10.4 ghc-ghc-paths-doc-0.1.0.5-8.fc12.i686 requires ghc-doc = 0:6.10.4 ghc-ghc-paths-doc-0.1.0.5-8.fc12.i686 requires ghc-doc = 0:6.10.4 ghc-ghc-paths-prof-0.1.0.5-8.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-gio-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gio-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gio-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-glade-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-glade-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-glade-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-glib-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-glib-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-glib-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-gstreamer-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gstreamer-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gstreamer-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-gtk-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gtk-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gtk-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-gtkglext-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gtkglext-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gtkglext-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-gtksourceview2-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gtksourceview2-devel-0.10.1-5.fc12.i686 requires ghc = 0:6.10.4 ghc-gtksourceview2-prof-0.10.1-5.fc12.i686 requires ghc-prof = 0:6.10.4 ghc-haskell-platform-devel-2009.2.0.2-3.fc13.i686 requires ghc = 0:6.10.4 ghc-haskell-platform-devel-2009.2.0.2-3.fc13.i686 requires ghc = 0:6.10.4 ghc-haskell-platform-doc-2009.2.0.2-3.fc13.i686 requires ghc-doc = 0:6.10.4 ghc-haskell-platform-doc-2009.2.0.2-3.fc13.i686 requires ghc-doc = 0:6.10.4
Re: how to install source packages?
On Sat, Jan 9, 2010 at 12:26 PM, Jud Craft wrote: > I've enabled the updates-source and fedora-source repositories in > PackageKit, but how do I, for example, install the source package for > Cairo? > > A packagekit search for Cairo returns nothing from the updates-source > or fedora-source repositories, and nothing called "cairo-source" or > anything of the like. Just binary cairo and cairo-devel. > > In short, how do I install source packages? Have I missed an obvious > step or is it really unintuitive? The easiest way to do this IME is: 1. Ensure 'yum-utils' is installed 2. Run 'yumdownloader --source cairo' 3. 'rpm -ivh cairo-*.src.rpm' The resulting .spec file and source will be under ~/rpmbuild/ . -- Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
2010/1/10 Kevin Fenzi : > Here's another (more accurate/correct) run of the sources file > checker. Thats against a 2010-01-06 cvs checkout seed. > snecker:BADURL:jokosher-20091128bzr.tar.gz:jokosher > snecker:BADURL:libflaim-4.9.1052.tar.gz:libflaim These are both checkouts from vcs. How should this be dealt with? -- Christopher Brown -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
On Sun, 10 Jan 2010 18:21:15 + Christopher Brown wrote: > 2010/1/10 Kevin Fenzi : > > Here's another (more accurate/correct) run of the sources file > > checker. Thats against a 2010-01-06 cvs checkout seed. > > > snecker:BADURL:jokosher-20091128bzr.tar.gz:jokosher > > snecker:BADURL:libflaim-4.9.1052.tar.gz:libflaim > > These are both checkouts from vcs. How should this be dealt with? https://fedoraproject.org/wiki/Packaging/SourceURL#Using_Revision_Control kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
2010/1/10 Kevin Fenzi : > On Sun, 10 Jan 2010 18:21:15 + > Christopher Brown wrote: > >> 2010/1/10 Kevin Fenzi : >> > Here's another (more accurate/correct) run of the sources file >> > checker. Thats against a 2010-01-06 cvs checkout seed. >> >> > snecker:BADURL:jokosher-20091128bzr.tar.gz:jokosher >> > snecker:BADURL:libflaim-4.9.1052.tar.gz:libflaim >> >> These are both checkouts from vcs. How should this be dealt with? > > https://fedoraproject.org/wiki/Packaging/SourceURL#Using_Revision_Control Which I have done for jokosher unless this means I have to drop the bzr suffix? -- Christopher Brown -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
On Sun, 10 Jan 2010 18:42:41 +, Christopher wrote:
> 2010/1/10 Kevin Fenzi :
> > On Sun, 10 Jan 2010 18:21:15 +
> > Christopher Brown wrote:
> >
> >> 2010/1/10 Kevin Fenzi :
> >> > Here's another (more accurate/correct) run of the sources file
> >> > checker. Thats against a 2010-01-06 cvs checkout seed.
> >>
> >> > snecker:BADURL:jokosher-20091128bzr.tar.gz:jokosher
> >> > snecker:BADURL:libflaim-4.9.1052.tar.gz:libflaim
> >>
> >> These are both checkouts from vcs. How should this be dealt with?
> >
> > https://fedoraproject.org/wiki/Packaging/SourceURL#Using_Revision_Control
>
> Which I have done for jokosher unless this means I have to drop the bzr
> suffix?
>
Drop the URL prefix. Your snapshot is not found there. Specify a local
file name:
Source0: %{name}-20091128bzr.tar.gz
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
On Sun, 10 Jan 2010 18:42:41 +
Christopher Brown wrote:
> Which I have done for jokosher unless this means I have to drop the
> bzr suffix?
You have:
Source0: http://www.%{name}.org/downloads/source/%{name}-20091128bzr.tar.gz
That URL is 404. There is no file with that URI.
You should have (IMHO):
# The source for this package was pulled from upstream's vcs. Use the
# following commands to generate the tarball:
#
# tar -czvf foo-20091129bzr.tar.gz foo-20001128
Source0: %{name}-20091228bzr.tar.gz
You should not make up a URL to a nonexistent file.
Just explain in a comment how exactly someone would duplicate your
source file using bzr and tar, and drop the http:// part of the Source.
Does that make sense?
kevin
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
On Sun, 2010-01-10 at 00:06 -0700, Kevin Fenzi wrote: > jussilehtola:BADSOURCE:agedu-r8768.tar.gz:agedu The upstream agedu tarball is generated nightly, so the md5sum changes the whole time. Should I take out the URL from the source line? -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
2010/1/10 Kevin Fenzi :
> On Sun, 10 Jan 2010 18:42:41 +
> Christopher Brown wrote:
>
>> Which I have done for jokosher unless this means I have to drop the
>> bzr suffix?
>
> You have:
>
> Source0: http://www.%{name}.org/downloads/source/%{name}-20091128bzr.tar.gz
>
> That URL is 404. There is no file with that URI.
>
> You should have (IMHO):
>
> # The source for this package was pulled from upstream's vcs. Use the
> # following commands to generate the tarball:
> #
> # tar -czvf foo-20091129bzr.tar.gz foo-20001128
>
> Source0: %{name}-20091228bzr.tar.gz
>
> You should not make up a URL to a nonexistent file.
> Just explain in a comment how exactly someone would duplicate your
> source file using bzr and tar, and drop the http:// part of the Source.
>
> Does that make sense?
It does, thanks.
--
Christopher Brown
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Build fail I cannot explain
Hello Fedora Developers. I'm trying to build an update for the Player robotics software for F-11. The very same spec file builds just fine for F-12 and rawhide. It worked just fine for the previous Player version with only minor spec changes. Since then mock has been updated on the build machine from 0.9.14 to 1.0.2, maybe that contributes to the problem? (for those who follow this list closely: the latest problem regarding cmake and boost with this package could be solved, thanks to Rich Mattes for this). The current problem I cannot explain. There is no obvious error message. In the state.log the build step is not reached. In build.log the only "rpmbuild -bs" is executed, but not "rpmbuild -bb" and there is no error message, the exit code of the first step is 0. Note that the missing python/ruby messages are the same in the successful and the failed build. The failed build is at https://koji.fedoraproject.org/koji/buildinfo?buildID=150236, a working build for F-12 is at https://koji.fedoraproject.org/koji/buildinfo?buildID=150201 Thanks for any input you can provide. Tim -- Tim Niemueller www.niemueller.de = Imagination is more important than knowledge. (Albert Einstein) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Build fail I cannot explain
2010/1/10 Tim Niemueller : > Hello Fedora Developers. > > I'm trying to build an update for the Player robotics software for F-11. > The very same spec file builds just fine for F-12 and rawhide. It worked > just fine for the previous Player version with only minor spec changes. > Since then mock has been updated on the build machine from 0.9.14 to > 1.0.2, maybe that contributes to the problem? You have a missing Build Requirement as this package doesn't exists: from root.log: DEBUG util.py:256: No Package Found for boost-thread Once that said, you probably have to use boost-devel instead. The accurate boost sub-package will be picked at install time automatically. Nicolas (kwizart) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Build fail I cannot explain
On Sun, Jan 10, 2010 at 19:40, Tim Niemueller wrote: > Hello Fedora Developers. > > I'm trying to build an update for the Player robotics software for F-11. > The very same spec file builds just fine for F-12 and rawhide. It worked > just fine for the previous Player version with only minor spec changes. > Since then mock has been updated on the build machine from 0.9.14 to > 1.0.2, maybe that contributes to the problem? > > (for those who follow this list closely: the latest problem regarding > cmake and boost with this package could be solved, thanks to Rich Mattes > for this). > > The current problem I cannot explain. There is no obvious error message. > In the state.log the build step is not reached. In build.log the only > "rpmbuild -bs" is executed, but not "rpmbuild -bb" and there is no error > message, the exit code of the first step is 0. Note that the missing > python/ruby messages are the same in the successful and the failed build. > > The failed build is at > https://koji.fedoraproject.org/koji/buildinfo?buildID=150236, a working > build for F-12 is at > https://koji.fedoraproject.org/koji/buildinfo?buildID=150201 The failed build has "No Package Found for boost-thread" in the the root.log. It would appear it exists in F12+ but not in F11. -- There are 10 kinds of people in the world: Those who understand binary and those who don't... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Build fail I cannot explain
Just solved. The boost-thread does not exist on F-11. Took some time to spot this as the exit code shown at the end of the appropriate section is still 0. Maybe that should be made a little more obvious... Tim -- Tim Niemueller www.niemueller.de = Imagination is more important than knowledge. (Albert Einstein) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
python-IPy "major" upgrade
Kevin Fenzi's source tarball audit made me realize there was a newer
python IPy version available. This version claims to be a major
version bump.
Version 0.70 (2009-10-29)
* New "major" version because it may break compatibility
* Fix __cmp__(): IP('0.0.0.0/0') and IP('0.0.0.0') are not equal
* Fix IP.net() of the network "::/0": "::" instead of "0.0.0.0".
IPy 0.63 should fix this bug, but it wasn't.
I doubt we have packages that rely upon the errant behavior, but
wanted to let you know in case you did.
I'll update to this in rawhide and EL branches. If you really need
this fix in older branches let me know.
@@ -684,6 +684,9 @@ class IPint:
return -1
elif self.ip > other.ip:
return 1
+elif self._ipversion != other._ipversion:
+# IP('0.0.0.0'), IP('::/0')
+return cmp(self._ipversion, other._ipversion)
else:
return 0
@@ -719,7 +722,7 @@ class IP(IPint):
>>> IP('10.0.0.0/8').net()
IP('10.0.0.0')
"""
-return IP(IPint.net(self))
+return IP(IPint.net(self), ipversion=self._ipversion)
def broadcast(self):
"""Return the broadcast (last) address of a network as an IP object.
Thanks,
Matt
--
Matt Domsch
Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
> kalev:BADURL:pkcs11-dump-0.3.3.tar.bz2:pkcs11-dump Thanks, fixed in rawhide and also updated to 0.3.4. Upstream had switched to a new project page with different URL. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sources file audit - 2010-01-06
On Sun, 10 Jan 2010 21:11:29 +0200 Jussi Lehtola wrote: > On Sun, 2010-01-10 at 00:06 -0700, Kevin Fenzi wrote: > > jussilehtola:BADSOURCE:agedu-r8768.tar.gz:agedu > > The upstream agedu tarball is generated nightly, so the md5sum changes > the whole time. Should I take out the URL from the source line? Yeah, I would think so. You could leave it in a comment with a note that it changes each time it's fetched/daily. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Desktop caterogies
Hi, In order to improve the desktop file of a package I maintain, I should want to know if there is a guideline for desktop file in Fedora. google donẗ help me. And Fedora 6 (KDE related) provided more sub-menu items than F-12... Thanks -- Les pages de manuel Linux en français http://manpagesfr.free.fr signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
