Re: [gentoo-dev] Please review: function epunt_la_files for eutils.eclass
On Fri, 2008-11-14 at 15:35 +0100, Rémi Cardona wrote: Alexis Ballier a écrit : Hi, (I think pulseaudio is fixed, actually.) For what it's worth: removing the .la files from pulseaudio breaks its module loading on freebsd; and it's an elf system. I don't know what you mean by fixed It's not fixed and it can't be. libtool's cross-platform dlopen() wrapper library (libltdl) needs .la files even on ELF systems. The only way to fix this is to use dlopen() instead... Never *unconditionally* switch back from libltdl to dlopenco in source code, as it is likely to break many non-linux platforms (Darwin, AIX, HP-UX, ...). /haubi/ -- Michael Haubenwallner Gentoo on a different level
[gentoo-dev] Moving packages -- breaking the tree or stop updating mirrors?
It is time to finish the move of some new dual-lifed perl modules from dev-perl to perl-core (plus virtual/). It involves updating of 120 packages all over the tree but mostly in dev-perl. As this takes some time the tree will be inconsistent until it is finished. I don't know how long it'll take. So the question is: Can we stop updating the rsync mirrors during that time easily? Or even better: Can *I* stop it? As there were problems while moving packages before, I remember we were talking about a way to stop updating rsync mirrors from cvs. I guess nothing was implemented? Thanks.
[gentoo-dev] Remember: workarounds don't warrant RESO FIXED!
Guys, please remember that if you work something around, you should _not_ close the bug as RESO FIXED but keep the bug open so that the issue can be addressed and fixed _properly_. Otherwise we'll end up with ebuilds full of workarounds without even documentation on why the workaround is applied! With workarounds I mean, as examples: - FEATURES=test failures; - broken parallel make that requires -j1; - flags filtering, included -Wl,--no-as-needed appending This is important because: a) we want test to work or get fixed upstream; b) we want users to get parallel build if they request parallel build; c) we want --as-needed to be used, not ignored. If the bug is open and comes out on searches and all the rest, then we have higher chances that someone might _fix_ it, without having to look to see if there actually is one... Thanks! -- Diego Flameeyes Pettenò http://blog.flameeyes.eu/ pgp9wm4rF3mnl.pgp Description: PGP signature
Re: [gentoo-dev] Remember: workarounds don't warrant RESO FIXED!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think, resolving as UPSTREAM might be more logical as we can't force every upstream to fix their *borked* build system and the bug will be left open forever. Diego 'Flameeyes' Pettenò yazmış: Guys, please remember that if you work something around, you should _not_ close the bug as RESO FIXED but keep the bug open so that the issue can be addressed and fixed _properly_. Otherwise we'll end up with ebuilds full of workarounds without even documentation on why the workaround is applied! With workarounds I mean, as examples: - FEATURES=test failures; - broken parallel make that requires -j1; - flags filtering, included -Wl,--no-as-needed appending This is important because: a) we want test to work or get fixed upstream; b) we want users to get parallel build if they request parallel build; c) we want --as-needed to be used, not ignored. If the bug is open and comes out on searches and all the rest, then we have higher chances that someone might _fix_ it, without having to look to see if there actually is one... Thanks! - -- Sincerely, Serkan KABA Gentoo/Java -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkgTssACgkQRh6X64ivZaJq7gCfUSK2fcYQTXeddGfcM0xBLx2S elQAn3S0hc62XuLrubvpn7kCQhwfiIim =mvB8 -END PGP SIGNATURE-
[gentoo-dev] Re: Remember: workarounds don't warrant RESO FIXED!
Serkan Kaba [EMAIL PROTECTED] writes: I think, resolving as UPSTREAM might be more logical as we can't force every upstream to fix their *borked* build system and the bug will be left open forever. If upstream refuses to fix an issue that _is an issue_ we have to fix it, not work it around forever and ever. RESO UPSTREAM is good for crashes that are left to upstream, but since Gentoo si abuilt building, build problems needs to get fixed. -- Diego Flameeyes Pettenò http://blog.flameeyes.eu/ pgpdnNkROqeW7.pgp Description: PGP signature
[gentoo-dev] Packages up for grab
Hi guys, here is a list of packages gnome herd would like to get rid of since no-one seem to take care of them and users are not so verbose about it either: * app-text/ggv https://bugs.gentoo.org/show_bug.cgi?id=223427 * net-news/straw https://bugs.gentoo.org/show_bug.cgi?id=187285 * net-news/logjam https://bugs.gentoo.org/show_bug.cgi?id=181236 If no-one takes them, I'll proceed to package removal. -- Gilles Dartiguelongue [EMAIL PROTECTED] Gentoo signature.asc Description: Ceci est une partie de message numériquement signée
[gentoo-dev] Re: Remember: workarounds don't warrant RESO FIXED!
On Sun, 16 Nov 2008 17:24:34 +0100 [EMAIL PROTECTED] (Diego 'Flameeyes' Pettenò) wrote: Guys, please remember that if you work something around, you should _not_ close the bug as RESO FIXED but keep the bug open so that the issue can be addressed and fixed _properly_. Otherwise we'll end up with ebuilds full of workarounds without even documentation on why the workaround is applied! With workarounds I mean, as examples: * * * * - FEATURES=test failures; * * * * The next person who closes testsuite failures as invalid or upstream gets to meet my frozen boot. If a test fails, fix it. If it fails because of portage or Gentoo-specific reasons that can't be fixed then RESTRICT it. Everybody is crowing about making src_test enabled by default, yet I still had 2 out of 3 build failures on my last tinderbox adventure caused by known, reported, and unfixed testsuite problems. - broken parallel make that requires -j1; - flags filtering, included -Wl,--no-as-needed appending This is important because: a) we want test to work or get fixed upstream; b) we want users to get parallel build if they request parallel build; c) we want --as-needed to be used, not ignored. If the bug is open and comes out on searches and all the rest, then we have higher chances that someone might _fix_ it, without having to look to see if there actually is one... Thanks! -- gcc-porting, by design, by neglect treecleaner, for a fact or just for effect wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 signature.asc Description: PGP signature
Re: [gentoo-dev] Please review: function epunt_la_files for eutils.eclass
Le 16/11/2008 09:44, Michael Haubenwallner a écrit : Never *unconditionally* switch back from libltdl to dlopenco in source code, as it is likely to break many non-linux platforms (Darwin, AIX, HP-UX, ...). I perfectly know this. My comment was *exactly* made to point out that we cannot fix any of this without fixing libtool itself. There's *no* way to workaround the issue. Cheers Rémi
[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2008-11-16 23h59 UTC
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2008-11-16 23h59 UTC. Removals: sys-cluster/gfs-headers 2008-11-12 23:04:18 xmerlin sys-cluster/cman-headers2008-11-12 23:05:19 xmerlin sys-cluster/cman-kernel 2008-11-12 23:06:49 xmerlin sys-cluster/dlm-headers 2008-11-12 23:08:08 xmerlin sys-cluster/dlm-kernel 2008-11-12 23:08:57 xmerlin sys-cluster/gulm2008-11-12 23:13:12 xmerlin sys-cluster/magma 2008-11-12 23:13:54 xmerlin sys-cluster/magma-plugins 2008-11-12 23:14:29 xmerlin sys-cluster/gnbd-headers2008-11-12 23:55:28 xmerlin sys-cluster/iddev 2008-11-12 23:57:02 xmerlin net-mail/qmail-vmailmgr 2008-11-13 13:16:01 bangert games-simulation/cultivation2008-11-13 15:47:28 darkside dev-lisp/abcl-cvs 2008-11-15 21:21:09 caster Additions: dev-ruby/xml-mapping2008-11-10 20:42:37 graaff media-radio/tucnak2 2008-11-10 23:49:11 darkside x11-misc/xidle 2008-11-12 06:57:33 jer media-plugins/gst-plugins-soup 2008-11-12 12:22:43 leio app-pda/synce-gvfs 2008-11-13 00:02:29 mescalinum app-pda/synce-hal 2008-11-13 00:05:09 mescalinum app-pda/synce-kio-rapip 2008-11-13 00:07:29 mescalinum app-pda/synce-kpm 2008-11-13 00:09:45 mescalinum app-pda/synce-librra2008-11-13 00:11:49 mescalinum app-pda/synce-librtfcomp2008-11-13 00:13:30 mescalinum app-pda/synce-odccm 2008-11-13 00:16:53 mescalinum app-pda/synce-pywbxml 2008-11-13 06:37:54 mescalinum app-pda/synce-sync-engine 2008-11-13 16:31:01 mescalinum sys-fs/gfs2 2008-11-13 19:19:30 xmerlin dev-python/amara2008-11-14 03:31:29 marineam dev-java/bytelist 2008-11-15 16:10:46 fordfrog dev-java/jsr223 2008-11-16 13:56:33 fordfrog dev-java/jvyamlb2008-11-16 15:45:36 fordfrog dev-java/httpunit 2008-11-16 16:15:14 fordfrog dev-java/beansbinding 2008-11-16 16:28:28 fordfrog -- Robin Hugh Johnson Gentoo Linux Developer E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 Removed Packages: sys-cluster/gfs-headers,removed,xmerlin,2008-11-12 23:04:18 sys-cluster/cman-headers,removed,xmerlin,2008-11-12 23:05:19 sys-cluster/cman-kernel,removed,xmerlin,2008-11-12 23:06:49 sys-cluster/dlm-headers,removed,xmerlin,2008-11-12 23:08:08 sys-cluster/dlm-kernel,removed,xmerlin,2008-11-12 23:08:57 sys-cluster/gulm,removed,xmerlin,2008-11-12 23:13:12 sys-cluster/magma,removed,xmerlin,2008-11-12 23:13:54 sys-cluster/magma-plugins,removed,xmerlin,2008-11-12 23:14:29 sys-cluster/gnbd-headers,removed,xmerlin,2008-11-12 23:55:28 sys-cluster/iddev,removed,xmerlin,2008-11-12 23:57:02 net-mail/qmail-vmailmgr,removed,bangert,2008-11-13 13:16:01 games-simulation/cultivation,removed,darkside,2008-11-13 15:47:28 dev-lisp/abcl-cvs,removed,caster,2008-11-15 21:21:09 Added Packages: dev-ruby/xml-mapping,added,graaff,2008-11-10 20:42:37 media-radio/tucnak2,added,darkside,2008-11-10 23:49:11 x11-misc/xidle,added,jer,2008-11-12 06:57:33 media-plugins/gst-plugins-soup,added,leio,2008-11-12 12:22:43 app-pda/synce-gvfs,added,mescalinum,2008-11-13 00:02:29 app-pda/synce-hal,added,mescalinum,2008-11-13 00:05:09 app-pda/synce-kio-rapip,added,mescalinum,2008-11-13 00:07:29 app-pda/synce-kpm,added,mescalinum,2008-11-13 00:09:45 app-pda/synce-librra,added,mescalinum,2008-11-13 00:11:49 app-pda/synce-librtfcomp,added,mescalinum,2008-11-13 00:13:30 app-pda/synce-odccm,added,mescalinum,2008-11-13 00:16:53 app-pda/synce-pywbxml,added,mescalinum,2008-11-13 06:37:54 app-pda/synce-sync-engine,added,mescalinum,2008-11-13 16:31:01 sys-fs/gfs2,added,xmerlin,2008-11-13 19:19:30 dev-python/amara,added,marineam,2008-11-14 03:31:29 dev-java/bytelist,added,fordfrog,2008-11-15 16:10:46 dev-java/jsr223,added,fordfrog,2008-11-16 13:56:33 dev-java/jvyamlb,added,fordfrog,2008-11-16 15:45:36 dev-java/httpunit,added,fordfrog,2008-11-16 16:15:14 dev-java/beansbinding,added,fordfrog,2008-11-16 16:28:28 Done.
[gentoo-dev] Re: Proposal for how to handle stable ebuilds
On Mon, 10 Nov 2008 13:13:34 -0500 Mark Loeser [EMAIL PROTECTED] wrote: If an ebuild meets the time criteria above, and there are no technical issues preventing stabilization, then the maintainer MAY [...] mark that ebuild as stable on every keyworded arch (that has a stable keyword). If an ebuild meets the time criteria above, but there is a technical issue preventing stabilization, and there are no outstanding security issues, [...] the maintainer MUST NOT mark the ebuild stable without the approval of the arch team. If technical issues arise after an ebuild is stabilized automatically, the arch team MAY revert the ebuild to ~arch if another ebuild with a stable keyword is still available or restore the previous stable ebuild to the tree if not, until such time that the issue is resolved, or stabilize a later versioned ebuild that does not exhibit the issue at the maintainer's approval. The maintainer MUST NOT NEVER EVER NOT EVEN A LITTLE BIT remove the latest stable ebuild of an arch without the approval of the arch team or he/she will be fed to the Galrog. and s/30 days/90 days/g. -- gcc-porting, by design, by neglect treecleaner, for a fact or just for effect wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 signature.asc Description: PGP signature