http://blog.gmane.org/gmane.linux.sourcemage.discuss hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.linux.sourcemage.discuss/9381 <pre>Can someone please outline the proper procedure to deprecate spells (and possibly post it on the wiki)? remove the spell if there is no direct replacement for it. If there is, you add an up_trigger to cast its replacement and an up_trigger to dispel_self, replace the contents of PRE_BUILD, BUILD, and INSTALL with true, comment out the SOURCE info in DETAILS, and remove any remaining files (other than HISTORY). Is that correct? In case anyone is wondering, I want to deprecate howl (it currently fails to build and is long dead) and replace any current depends on it with -sub COMPAT_HOWL avahi. </pre> Sukneet Basuta 2012-05-25T21:51:16 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9372 <pre>For all the spellwriters, even while $SCRIPT_DIRECTORY and $SPELL_DIRECTORY are equal in functionality, please use the last one as it actually makes more sense. </pre> Vlad Glagolev 2012-05-22T21:13:28 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9358 <pre>Hi everyone, stable-rc 0.61 is REcut and ready for testing again. Since we have new up-to-date chroot images now, the process of testing an upgrade from 0.60 to 0.61 should go smoothly. The release target is *June 15th*. It will take a bit more time than usually, cause we had a notable pause from previous stable release. The tarballs have been signed and uploaded to our server and will be propogating out to the mirrors within six hours. To download the grimoire manually, get http://codex.sourcemage.org/stable-rc.tar.bz2 or specifically http://codex.sourcemage.org/stable-rc-0.61.tar.bz2 . GPG signatures are available at http://codex.sourcemage.org/stable-rc.tar.bz2.asc or http://codex.sourcemage.org/stable-rc-0.61.tar.bz2.asc . As always don't forget to file any bugs against our issue tracker[0] so we can resolve them and integrate the fixes before release. New version '0.61-rc' is still there, so use it when submitting the bugs. Let's give this new stable-rc a good testing! [0] http://www.sourcemage.org/projects/grimoire/issues </pre> Vlad Glagolev 2012-05-11T23:37:15 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9344 <pre>As a new user, reading the recent discussion, I thought I'd make a general comment. I've been using linux for about ten years and have enjoyed installing and using various different distros, usually falling back on Gentoo. I installed Smgl a couple of months ago, and it immediately became my primary OS (I currently have 7 others on my computer). Admittedly, my install is pretty basic. I'm using mostly stable with a couple of test spells and a couple I've written. I thoroughly enjoyed installing it and it has been very solid and a delight to use (no issues with util-linux). My main worry is that it will cease to be actively developed. To the developers: It's a great system, you've done a great job, please don't stop. Dan _______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Dan Kociela 2012-04-23T22:10:22 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9337 <pre>I have a patch to a spell. The patch size is ~ 10k bytes, 200 lines Is it better to compress the patch or not? If it is not compressed, git can do a better job of reducing space usage. Thoughts? Treeve </pre> Treeve Jelbert 2012-04-22T17:59:45 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9333 <pre>Hi, I just got bitten by an util-linux update breaking my login. Seems like this is http://www.sourcemage.org/issues/110 and there is code in FINAL dealing with this: if [ "${VERSION:0:4}" == "2.20" ] &amp;&amp; [ "${OLD_SPELL_VERSION:0:4}" == "2.19" ]; then message "New version of util-linux needs to update /etc/inittab ..." &amp;&amp; cp $INSTALL_ROOT/etc/inittab $INSTALL_ROOT/etc/inittab-$(date +'%Y%m%d%H%M') &amp;&amp; sed -i "s:/dev/tty:tty:" $INSTALL_ROOT/etc/inittab &amp;&amp; message "Updated" fi &amp;&amp; Now, of course I broke this by doing the update too late, jumping from 2.19 to 2.21. So I have two questions about this: 1. Was the intention to delete the FINAL code when updating to 2.21? Because now it is dead meat right there. 2. I don't really like the sed line there ... it doesn't check if there is actually agetty in the line it works on. There are other getty programs. So ... what's the intention here? Just remove the code as the update to 2.20 is history? Alrighty then, Thomas PS: I want to add that I really, really am angry at util-linux folks for not just supporting /dev paths anyway. What's so hard about this? _______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Thomas Orgis 2012-04-21T06:36:55 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9330 <pre> Signed-off-by: Ismael Luceno &lt;ismael.luceno&lt; at &gt;gmail.com&gt; --- 32/ia32/intel/x86/atom | 4 ++-- 64/x86_64/intel/em64t/{atom =&gt; atom_64} | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) rename 64/x86_64/intel/em64t/{atom =&gt; atom_64} (80%) diff --git a/32/ia32/intel/x86/atom b/32/ia32/intel/x86/atom index 86f6e26..054a669 100755 --- a/32/ia32/intel/x86/atom +++ b/32/ia32/intel/x86/atom &lt; at &gt;&lt; at &gt; -1,8 +1,8 &lt; at &gt;&lt; at &gt; -CPUNAME="Intel Atom" +CPUNAME="Intel Atom, 32bit mode" if use_gcc2; then CFLAGS="-march=i686" else - CFLAGS="-march=atom" + CFLAGS="-march=atom -m32" fi HOST="i686-pc-linux-gnu" FAST="-O3" diff --git a/64/x86_64/intel/em64t/atom b/64/x86_64/intel/em64t/atom_64 similarity index 80% rename from 64/x86_64/intel/em64t/atom rename to 64/x86_64/intel/em64t/atom_64 index d53e16b..247fc4a 100755 --- a/64/x86_64/intel/em64t/atom +++ b/64/x86_64/intel/em64t/atom_64 &lt; at &gt;&lt; at &gt; -3,7 +3,7 &lt; at &gt;&lt; at &gt; CPUNAME="Intel Atom 64bit (all except Z5xx, Z6xx and N2xx)" if use_gcc2 ; then CFLAGS="-march=i686" else - CFLAGS="-march=atom -fPIC -DPIC" + CFLAGS="-march=atom -m64 -fPIC -DPIC" fi HOST="x86_64-pc-linux-gnu" </pre> Ismael Luceno 2012-03-25T08:11:30 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9318 <pre>According to [1], we're supposed to have a vote for the Grimoire Lead in March. As it's now mid-March, I'm going to try to get the ball rolling by placing some nominations. I hereby nominate the following mages: Andraž 'ruskie' Levstik Vlag 'Stealth' Glagolev Arjan 'abouter' Bouter 1: http://wiki.sourcemage.org/SourceMage/Voting_Policy </pre> flux 2012-03-16T10:24:23 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9317 <pre>Looks like I can't push to the z-rejected repo. I've never pushed to this repo before, so probably it's just a permission issue. Can I get access, please? *_* _______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Ismael Luceno 2012-03-09T00:19:53 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9315 <pre>Hi everyone. Just a few updated spells as I do no longer have git access to the grimoire. If you prefer patch files for the next batch of updates let me know. updated spells: fasm 1.69.40 gerbv 2.6.0 meld 1.5.3 pcb 20110918 new spell: xcircuit 3.7.32 should go into science_______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Sven Lemke 2012-03-05T18:04:47 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9314 <pre>I guess, nowadays those codecs are pretty rare, but even in the case they were not, I think it's worth taking note of which of those are not provided by FFmpeg. Perhaps we can deprecate those proprietary packages. _______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Ismael Luceno 2012-03-04T23:21:01 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9310 <pre>Seems something got messed up the last update I did. I have several spells that fail on glib2, gtk+2, or gtk+3 QT4 4.8.0 is one that won't build now. It is getting this error when I try building it. https://lists.webkit.org/pipermail/webkit-unassigned/2011-November/382526.html So not sure if something in not working with pkgconfig and it is not getting the paths it needs or what. CuZnDragon Robin Cook _______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Robin Cook 2012-03-04T04:30:13 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9309 <pre>supporting python3 will be a never ending process. the python website lists 600+ packages which support python3, most of which we do not have as spells, although a few are new packages specificly intended for python3. I have created a new section, py3, to which I have moved about 20 spells which I actually use, together with a few new ones which are python3 only versions of existing spells. Where applicable, they build with either version of python and run on my notebook. Users of python2 should notice no difference. Changes made were as follows; new py3/FUNCTIONS DEPENDS: depends PYTHON Upstream support: automatic or via special build option(sqlalchemy). Others: run 2to3 in pre_build. In a couple of cases also patch the sources. I found a couple of cases where the upstream project appears to be dead(elixir, chardet), but which I use, so I made some patches. The major omissions at the moment are bzr and mercurial, but the upstream projects have experimental python3 support, neither of which work for me. I recommend that we merge these changes to master asap, to avoid ongoing confusion regarding future spell upgrades. As other spells are upgraded, we can check for python3 support and move to the new py3 section if applicable. I will write a separate mail regarding python use in non-python spells. Regards, Treeve </pre> Treeve Jelbert 2012-03-02T08:39:23 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9306 <pre>The attached patch fixes the clash which makes 64bit version unavailable. Also adding -m32 or -m64 as corresponding. _______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Ismael Luceno 2012-02-26T05:28:30 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9303 <pre>i have a need to upgrade some spells to use python3 Rather than make changes to several individual spells, as part of this I have a script which will change all python spells to allow either python3 or python2. As far as I can tell there are only 3 spells which specificly depend on python3. I realise that most of the spells are not tested against python3. Most people only have python2, so would not notice any difference. I doubt if many people only have python3. Those people who try to use python3 will eventually discover a few spells that do not work. Fixes will be found in due course. I would make the initial changes in a branch, but I think that this should have a very short life, otherwise it would live forever as some of the spells would never be tested. Any thoughts? Treeve </pre> Treeve Jelbert 2012-02-23T18:47:52 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9302 <pre>Stable grimoire version 0.60-8 has been released! Since new stable release is planned only for March, here's yet another security update for 0.60 stable branch as well as containing little bugfix about jfsutils for boxes with separated /usr partition. The tarballs have been signed and uploaded to our server and will be propogating out to the mirrors within six hours. To download the grimoire manually, get http://codex.sourcemage.org/stable.tar.bz2 or specifically http://codex.sourcemage.org/stable-0.60.tar.bz2 . GPG signatures are available at http://codex.sourcemage.org/stable.tar.bz2.asc or http://codex.sourcemage.org/stable-0.60.tar.bz2.asc . Following updates were integrated[0]: Bor Kraljič (1): jfsutils: fixed long description wrap (scripted) (cherry picked from commit aabbb87b5c9b389215d12ca627fa3c16358bf9e0) Ladislav Hagara (2): shadow: upstream patch added libpng 1.2.47, SECURITY_PATCH=7, CVE-2011-3026 (cherry picked from commit c07eecf81bd14574187288cd7dfe98e20bccbcbc) Vlad Glagolev (4): jfsutils: moved binaries to /sbin (cherry picked from commit 1d00457ee8a077ba5f1af47fca4ed3ab4fefdf6d) pygobject: fixed bug #361 (cherry picked from commit b8dca3979434c6048c18c0a9ec45c40a5eb3f83d) shadow: =&gt; 4.1.5 (security) (cherry picked from commit 75e717957193f8b26e0c5c8eac5d2a6fce675d0e) VERSION: 0.60-8 [0] Generated: 'git shortlog --no-merges stable-0.60-7..stable-0.60-8' </pre> Vlad Glagolev 2012-02-23T12:42:43 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9296 <pre>Hi everyone, stable-rc 0.61 is REcut and ready for testing. It's REcut, cause during some of consequences the "old" one has become a bit deprecated, so the better idea is to merge our current work in test and refresh release candidate branch for our next stable grimoire release. The release target is March 15th. The tarballs have been signed with my regular smgl key (447D316C) and uploaded to our server and will be propogating out to the mirrors within six hours. To download the grimoire manually, get http://codex.sourcemage.org/stable-rc.tar.bz2 or specifically http://codex.sourcemage.org/stable-rc-0.61.tar.bz2 . GPG signatures are available at http://codex.sourcemage.org/stable-rc.tar.bz2.asc or http://codex.sourcemage.org/stable-rc-0.61.tar.bz2.asc . As always don't forget to file any bugs against our issue tracker[0] so we can resolve them and integrate the fixes before release. I've just also created new version '0.61-rc' there, so use it when submitting the bugs. I hope we will discuss and form/renew/update the spell-list (for testing and for basesystem as well) according to our new release process in a week or so. Afterthat we might try to automate testing process and create fresh chroot-images for both x86 and x86_64 arches. Let's give this new stable-rc a good testing! [0] http://www.sourcemage.org/projects/grimoire/issues </pre> Vlad Glagolev 2012-02-15T01:04:35 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9294 <pre>David, Good point about the partitions. As M$ is pushing (U)EFI BIOS / Firmware this is going to become a real problem. Booting EFI BIOS currently requires GPT partitions and GRUB2 or elilo. (Or is it the other way around?) One big massive partition will not work. A basic x86_64 system currently has 4 partitions (bios_grub,boot,root,swap). No GUIDs in the fstab for GRUB2 on GPT either. The last thing a Linux Distro needs to do is recreate DLL Hell. Working / Puzzling out the JHBuild system, Corbin _______________________________________________ SM-Discuss mailing list SM-Discuss&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/sm-discuss </pre> Corbin Bird 2012-02-08T19:00:30 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9292 <pre>Hellow! After not working much on SMGL I decided to upgrade our KDE to 4.8.0. As usual I used branch to update changes. However this is major version change and it is a bit more complicated than just version bump. But there were no big problems. But lets get to the point of this mail: Upstream spllited kdeutills package into separated programs. So there is tarball ark-4.8.0.tar.bz2. I was just about to create spell ark when I remembered that spell ark was part of kde3 (which was removed from grimoire). So now I have a dilemma whatever the same spell names as there were in kde3 can be used or not? Due to that dilemma I stopped my work until we decide what to do. I pushed changes into branch [1]. I also created spell ark and added some code in PREPARE [2]. That was taken from discussion a while ago [3]. Kind regards, Bor [1] http://scmweb.sourcemage.org/?p=smgl/grimoire.git;a=shortlog;h=refs/heads/devel-kde48 [2] http://scmweb.sourcemage.org/?p=smgl/grimoire.git;a=commitdiff;h=a91d0a78c372bebe6f3b5baf7f5210d0a6e79f8c [3] http://lists.ibiblio.org/pipermail/sm-discuss/2011-September/020757.html </pre> Bor Kraljič 2012-02-08T14:36:13 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9277 <pre>Hi, any plan with /usr merge [1]? Personally I don't like it but I am a realist. We have no chance to change the upstream. New versions of crucial upstream packages rely on /usr merge. Do we want to use devel-udev-kmod git branch by the same way as devel-xorg-modular or we plan to integrate it soon? [1] http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge </pre> Ladislav Hagara 2012-02-07T10:16:01 http://comments.gmane.org/gmane.linux.sourcemage.discuss/9276 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As per our Developer Organization policy listed here: http://wiki.sourcemage.org/SourceMage/Developer_Organization The following two Lead Developers are removed and are now General Developers for missing two consecutive votes: * Arwed von Merkatz * Elisamuel Resto The above is not subject to a vote, it's an automatic demotion to General Developer. I'm just informing the entire community. Additionally, The following General Developers are each individually nominated and seconded for a Removal Vote because they have had no activity in a year. * Bearcat M Sandor - Last grimoire activity October 2009 * Dave Josephsen - Last grimoire activity April 2010 * Finn Haedicke - Last Grimoire activity Sept 2010 * Juan Carlos Torres - I cannot find any grimoire history for Jucato or any combination of his name... * Juuso Alasuutari - last Grimoire Activity May 2009 * Karsten Behrmann - last Grimoire Activity August 2008 * Paul Beel - Another one I can find no history in the repos for * Quentin Rameau - last noted grimoire activity March 2010 - cauldron 2012 * Terry Ross - last noted grimoire access (games grimoire) July 2004 * Vasil Yonkov - last noted grimoire access October 2010 I came up with this data doing a git log --all on a freshly pulled repo for all grimoire repos, the sorcery repo, and the cauldron repo, and looking for their email address, first name or last name. I cannot pull logs on the wiki, well, not past 30 days. I am letting you all know that this will happen unless a simple majority of votes cast vote against the removal. It's on an individual basis. If no votes are cast, in one week (Thursday, 9 February 2012) they will no longer be General Developers on the Sourcemage GNU/Linux project. In this case, the automatic removal vote does not require any voting to happen unless someone wishes to keep any or all of the developers on this list active. I'd ask that you be specific in your voting and specifically call out an individual that you wish to vote against their automatic removal. If someone does vote against an automatic removal, then voting will proceed as normal, and a simple majority of votes cast can keep them from being removed. I don't believe that this will work if votes are sent to me privately, so I will request that you send your vote to the mailing list. See http://wiki.sourcemage.org/SourceMage/Voting_Policy for details, and please don't hesitate to ask questions, as this is the first time (that I can recall) that this has happened. Your (mostly) friendly PL, David Kowis -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGcBAEBAgAGBQJPK18vAAoJEMnf+vRw63ObIekMAJXX5PX7Qs+VOh1cXTyDK43s JHpXAVrMYrmUpeikH0ZToUT9rEVwWcxktQ1pt7oIsPMWcggw1PkSVDutcRbgUABZ AqN8Kdt831idze0VH92M/DGBO22E9VUokUI2zLeklCY24C7wt2DoDBR7dxAlVn04 g1bBJc2pU6OGzlWbBCb1GZ9w1Ycf7FMPGxVMJ5/la/2sjpGMYrRI6/pETk0q2aS7 89oFR1QeD2UG696irJGw9ZpmBPX0xW2GYwcUavJkRHZQ30Gsho0YFwb5NFL2hNu9 AKCeGMF1h3woyydF0szfsy4B5UxS1qKG721JMDWSqYq8w+d28Mqd1RKaEU7VRUC5 /f++5l/FMYbIxprD/9q7Em3sgHclelT2tbxAXGCKKHhOhi42q9JPoJSwFnLTN/3I mMGwIGpL8UaetXznqh1NYEdSaLwG7Zj14JMphItxx6cYse7wZ7bWl/uxcL/EJ88h nMigyJQ+6ajxgPK1OiNS+NOEuLTTPF8Y6cfjkaZE7A== =9WbQ -----END PGP SIGNATURE----- </pre> David Kowis 2012-02-03T04:14:39 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.sourcemage.discuss