Fw: [ubuntu/karmic] source-highlight-qt 0.1-0ubuntu1 (New)
Begin forwarded message: Date: Thu, 06 Aug 2009 21:00:10 - From: Ubuntu Installer arch...@ubuntu.com To: Cesare Tirabassi cesare.tiraba...@gmail.com Subject: [ubuntu/karmic] source-highlight-qt 0.1-0ubuntu1 (New) NEW: source-highlight-qt_0.1.orig.tar.gz NEW: source-highlight-qt_0.1-0ubuntu1.diff.gz NEW: source-highlight-qt_0.1-0ubuntu1.dsc source-highlight-qt (0.1-0ubuntu1) karmic; urgency=low * Initial release (LP: #407896). -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Aug 2009 10:14:47 +0200 Source: source-highlight-qt Binary: libsource-highlight-qt4-1 libsource-highlight-qt4-dev libsource-highlight-qt4-doc Architecture: source Version: 0.1-0ubuntu1 Distribution: karmic Urgency: low Maintainer: Cesare Tirabassi norse...@ubuntu.com Changed-By: Cesare Tirabassi norse...@ubuntu.com Description: libsource-highlight-qt4-1 - Syntax highlighting library for Qt (shared library) libsource-highlight-qt4-dev - Syntax highlighting library for Qt (development files) libsource-highlight-qt4-doc - Syntax highlighting library for Qt (API documentation) Launchpad-Bugs-Fixed: 407896 Changes: source-highlight-qt (0.1-0ubuntu1) karmic; urgency=low . * Initial release (LP: #407896). Checksums-Sha1: b3d14139d6371d918bcb5d0267715fe788454b66 1249 source-highlight-qt_0.1-0ubuntu1.dsc ae3c7e6b7c507c2bbe0313b36e8d74a48e9a0a23 512253 source-highlight-qt_0.1.orig.tar.gz ee78456c137def37a010c84108d6d5db1e08522b 1654 source-highlight-qt_0.1-0ubuntu1.diff.gz Checksums-Sha256: d768f3358c051ae3574552348da9ca835d3ff194b5fc25bd7bafbac758e7ece9 1249 source-highlight-qt_0.1-0ubuntu1.dsc c176e507479eeb3d3fce9988c562ed05a324acca87987f31aecc1128417c8943 512253 source-highlight-qt_0.1.orig.tar.gz 2892aa9828b16c30e0923f7efeab7dbf5b8bd541d224191c351853a0ce379dda 1654 source-highlight-qt_0.1-0ubuntu1.diff.gz Files: e685eedb31baa43ab73e028662656780 1249 devel extra source-highlight-qt_0.1-0ubuntu1.dsc 85130730a50afc119bfc37b628462dae 512253 devel extra source-highlight-qt_0.1.orig.tar.gz 3fac7f8bfb6de548d7c5660ade66f430 1654 devel extra source-highlight-qt_0.1-0ubuntu1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKdXPuysMrFvyAPHwRAo6AAJ9ILg0zsJxckPShPWpe7WBsrmme3gCggb4C yivyk359pH1qADWJU48Jdmo= =W96T -END PGP SIGNATURE- -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: RFS: smplayer (updated package)
On Mon, 20 Apr 2009 15:02:58 +0200 Reinhard Tartler siret...@debian.org wrote: Maia Kozheva inetper...@gmail.com writes: - It does no harm in Debian as it is, except for debcheck warnings. - mplayer-nogui is available in Ubuntu, and I would rather keep the same package in Debian and Ubuntu. - mplayer-nogui is available in debian-multimedia.org, which many Debian users install mplayer from for extra patent-restricted codecs. - There is a bug report (#523842) in Debian itself to add an mplayer-nogui package, confirmed by one of the maintainers, so I presume an mplayer-nogui package may appear in Debian soon. I think we really should replace the mplayer package from multiverse with the package currently in debian/main. Since we are on the subject, I'd rather have an mplayer package without gui (gmplayer is buggy/obsolete and unmaintained, mplayer upstream are actually recommending it to not be distributed) and, if really necessary, have an mplayer-gui (or gmplayer) package with the gui alone. With the excellent stand-alone gui's we have today (smplayer, kmplayer, gnome-mplayer) this is what makes the most sense. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: When does MOTU Release need to start approving every upload ...
On Thu, 16 Oct 2008 06:17:35 -0400 Scott Kitterman [EMAIL PROTECTED] wrote: Based on: https://lists.ubuntu.com/archives/ubuntu-devel/2008-April/025259.html One might think it's now, but I propose this not start until the last week before release (i.e. one more week from now). +1, one week before release is more than reasonable. C. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: PackagesToPort
On Monday 29 September 2008 11:37:37 James Westby wrote: I decided to start a wiki page to track the packages that need porting from Debian. https://wiki.ubuntu.com/MOTU/PackagesToPort Perhaps is worth adding a link here: https://wiki.ubuntu.com/MOTU/TODO ? Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: PackagesToPort
On Monday 29 September 2008 11:47:22 Cesare Tirabassi wrote: On Monday 29 September 2008 11:37:37 James Westby wrote: I decided to start a wiki page to track the packages that need porting from Debian. https://wiki.ubuntu.com/MOTU/PackagesToPort Perhaps is worth adding a link here: https://wiki.ubuntu.com/MOTU/TODO ? Cesare Yes, it was since you added it already :-). -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Change in the MOTU reception
Dear all, Now that the transition is over, the new program is shaping up nicely, and we have new active people helping with the reception, I would like to leave the role of coordinating the mentoring activities to Christophe Sauthier (huats). You should all know Christophe, he is an active and eager community member, and I'm sure that in his capable hands the mentoring program will achieve even greater results. Please, give him a warm welcome (he needs it ;-)). Let me take the opportunity to thank from my heart all mentors that have dedicated their time and energy helping our community to grow, and all the reception members for making one of the best teams I ever had the pleasure to work with! Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: pbuilder question
On Monday 08 September 2008 18:35:18 Charliej wrote: I am trying to setup pbuilder to use the B91dpkg-i hook to test install my package but I seem to be having a little problem. As you can tell from the snippet below the build completed successfully but when dpkg -i is run it complains of a dependency problem. I thought that dependencies where checked and satisfied in the first part of the build process? Build-dependencies, not run-time ones. Shouldn't these dependencies still be present in the chroot when dpkg-i is called? Any pointers here would be greatly appreciated. You may try to add an apt-get -f install in the script (after the dpkg -i call). This should force all run-time dependencies to be installed. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
kdesu for kde4
A quickie for all Kubunteros out there. I read that /usr/bin/kdesu in kde4 is obsoleted. For Intrepid, should applications that rely on it be patched to rely on /usr/lib/kde4/libexec/kdesu or on /usr/bin/kdesudo or is there some mechanism in place that won't break backward compatibility? Will existing su-to-root (that uses /usr/lib/kde4/libexec/kdesu) work or will it need patching for Ubuntu? Existing docs I could find on the subject are not very clear: LP bugs: 179495, 184491, 197404 http://kubuntuforums.net/forums/index.php?action=printpage;topic=3095801.0 https://wiki.ubuntu.com/HaraldSitter/KdeFour/KdeSudo Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Standing Freeze exception for emacs-snapshot
On Wednesday 03 September 2008 10:46:09 Reinhard Tartler wrote: Stefan Potyra [EMAIL PROTECTED] writes: Standing freeze exceptions: To request a standing freeze exception, an email should be sent to the Ubuntu MOTU mailing list for discussions. It is granted, once three members of motu- release have given their ACK. I'd like to request a standing freeze exception for emacs-snapshot. The only point of the package is to ship a development snapshot of the current emacs trunk branch. We had such a freeze exception in the past, I'm requesting it for intrepid again just to be sure. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 I'm surprised that there are so many packages that depend on binaries of emacs-snapshot, but after checking some samples I believe them to be all or'ed with emacs? Out of curiosity, how exactly is your workflow? From https://launchpad.net/~ubuntu-elisp/+archive seems like Romain is doing the Debian packaging and Reinhard pushes them to the archive? In any case, the request looks reasonable to me, +1. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Please add Luca Falavigna as a member of motu-release
In line with current team policy [1], following Luca's application [2], sent on Wed Aug 27 13:51:37 BST 2008, considering the positive advocations [3][4][5] received, in the absence of any concern having been raised, considering that 168 hours have elapsed, Luca application should be considered accepted. I urge the team owner to formally add Luca Falavigna, aka Dktrkranz, as a motu-release team member asap. Thanks, Cesare [1]https://wiki.ubuntu.com/MOTU/Teams/KeyTeamPolicy [2]https://lists.ubuntu.com/archives/ubuntu-motu/2008-August/004573.html [3]https://lists.ubuntu.com/archives/ubuntu-motu/2008-August/004574.html [4]https://lists.ubuntu.com/archives/ubuntu-motu/2008-August/004579.html [5]https://lists.ubuntu.com/archives/ubuntu-motu/2008-August/004622.html -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
I cannot continue with Ubuntu development using LP
The recent LP changes for the worst I can still cope with, the switch to OpenID which stops me from being able to edit any wiki page anymore I can still abide, but the recent change of font size is too much for me: https://bugs.launchpad.net/launchpad/+bug/262166 Please tell me that this is not LP faults and that there is a simple way to solve this problem as this makes LP totally unusable for me. Until this is (hopefully) solved, I will be unable to do any development using LP. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: motu-release needs you
On Wednesday 27 August 2008 15:59:37 Stefan Potyra wrote: Hi, On Wednesday 27 August 2008 14:51:37 Luca Falavigna wrote: Stefan Potyra ha scritto: motu-release is short one member, please apply here If nobody nominates, I'd like to apply. Excellent! I hereby advocate your application. Cheers, Stefan. A definite +1 from me too. Luca will be a great addition to the team. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: motu-sru renewal? (was: Stepping down from MOTU SRU)
On Wednesday 06 August 2008 11:51:08 Luca Falavigna wrote: motu-sru limits to Cody and me, actually. Even if SRU work is smaller now if compared to the days following Hardy release, there are some requests which need to be reviewed. If there is a dare need for help, count me in. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: pbuilder twice in a row option
On Sunday 03 August 2008 22:11:13 Nicolas Valcarcel wrote: Hi! I've just write a --build-twice-in-a-row feature for pbuilder that allows pbuilder users to test if clean work as expected and i need some testing, so far i have test it and it's working, but i will prefer to have a second (or more) opinions on the feature. The new package can be downloaded from my ppa [1], and i will appreciate really much that you test it and send me some suggestions/comments. Thanks in advance! 1. https://edge.launchpad.net/~nvalcarcel/+archive You may also just want to use a hook for this. A B hook (see man pbuilder) will be run once the build is finished successfully, before copying back the build result. You can simply rerun the build here and check if it fails. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Proposed Features for Launchpad Bugs 3.0 - call for help!
On Friday 01 August 2008 09:28:49 you wrote: The most important from me is not on the list, and that would be to have the source package information back on the bug page (as it was before). Its pretty annoying having to change to other pages just to see if that package is in universe or not, what is the current version and who uploaded it last. For this: || || bug imports || Enabling complete syncs from plugin-enabled sites || If that means the ability for MOTU to manually sync, than this is a 15, otherwise what the heck is this? All the others I don't really care about; they are mostly annoying things lost in a sea of annoying things (which to me is a clear sign that they have no clue about what is really important in a distro bug tracker from a developer pov). Thank you for you collaboration! My pleasure, Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Proposed Features for Launchpad Bugs 3.0 - call for help!
On Friday 01 August 2008 12:50:29 you wrote: Cesare Tirabassi [EMAIL PROTECTED] writes: This sounds rather like a bug than a spec to me. Is there already a bugnumber for it? If not, can you please file a bug and tell me the number? I have no idea if there is a bug already filed for this. Manually scanning 1200+ bugs is not an option and, as you know, searching for bugs containing keywords (I tried source with/without info and couldn't get anywhere) never works for me (usually, I can find more relevant LP bugs via google than via LP itself). Assuming there isn't, I will file one and let you have the bug number. Note that wgrant pointed out to me that there are now tooltips to give some of this information (thanks wgrant), but in my opinion this is just a palliative. When I actually need to use this info what should I do, write it down on a piece of paper? And the tooltip disappear anyway after few seconds. As far as I understand it, you can say here is a bug in debbugs, it also affects ubuntu, please import all comments, status, etc from debbugs to launchpad and auto create a 'forwarded bugtask'. OK, don't, please don't. The way I understand it this is likely to create more confusion than solve any real issue. The best we can do is to document (using bug numbers) and group (using tags) the annoying things. This is work, obviously, but I don't see another way how to get further on this issue. From my own experience, raising bugs in LP about LP is as much effective as trying to empty the ocean with a (leaking) bucket. IMHO adding the homepage in the source package info would be a big help (assuming we can get that back to the bug page). When I need to check upstream (maybe its an update, maybe to see if a bug has been filed already there or fixed in their VCS) the only solution that I know of to do it through LP is to gunzip the diff.gz. Again, I could not find if such a request was filed already and knowing that the effect of raising such bugs tends to zero I was never motivated to do it myself (beside, I just use apt-cache). Now you tell me we should do it, fine, I will, and let me see how far we go with these. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Fwd: [Motu-mentoring-reception] Minutes of the Meeting of the Motu Mentoring Reception of the 31/07/2007
We believe that issues discussed during the Mentoring Reception meetings (held at 1 month interval) are potentially of interest to the whole community. We have therefore decided to circulate minutes through the ubuntu-motu and ubuntu-motu-mentors mailing lists. Please let us know if you think this is not appropriate. --- MOTU Mentoring Reception Meeting Place : #ubuntu-meeting Participants from the mentoring reception team: Cesare Tirabassi (norsetto) Charlie Smotherman (porthose) Christophe Sauthier (huats) Absent: Nicolas Valcárcel (Nxvl) (Holidays) Additional attenders: Sarah Hobbs (Hobbsee) James Westby (james_w) Raphaël Pinson (raphink) Nathan Handler (nhandler) Colin Watson (cjwatson) Agenda : 1. Status of new requests = The current list : • hanno should be ready to be mentored; porthose will ping him. • james d carroll will be contacted by porthose. The email regarding his request can be found here : https://lists.ubuntu.com/archives/ubuntu-motu/2008-July/004231.html • James Emerson request is being dealt with by nxvl (which is currently on holidays). 2. Status of mentors == After many ping on IRC, huats has not been able to talk with slomo and jcorbier. For the time being, they will removed from the mentor list. raphink was at the meeting and confirmed that he is still happy to be mentoring senior contributors. Since he was not completely comfortable with the new process, it sounds as some motus are not yet aware of the change. 3. Recruitment of new mentors How to recruit more mentors ? Right now norsetto is contacting every new u-u-c and MOTU explaining them the mentoring process. nhandler proposes to introduce a kind of reward/privilege for mentors, but norsetto and huats wonder about its do-ability (shirts ?) It has been pointed out that mentoring is considered a credit for motuship or for core dev application. Anyway mentoring should not be compulsory, and is up to the will of concerned persons if and how they would like to help contributors. 4. Transition to new program === The status of the remaining mentors/mentees from the old process is : • dholbach is on holidays and huats has applied to u-u-c • asac is working well with jazzva and dfiloni • jr is working with Lydia Pintscher • huats to contact TheMuso to know more about the mentoring of AstralJava 5. Mailing list = No news from rt since the request 9 days ago. Our private ML seems to be working well so far. Hobbsee said that TB recommends strongly that ubuntu ML go to lists.ubuntu.com, and thus to contact jcastro and to fill a request to [EMAIL PROTECTED] norsetto confirms that this is what has been done already. 6. Interface with MOTU school james_w is running the school all alone, so he wouldn't mind a little help to get new lecturers since this is the current important matter. Once again norsetto proposed to send an email to every u-u-c and new MOTU to incite them to go forward. It has also been proposed to send an email to mentors and mentees asking them what they think they need to help them (for mentee), and what is missing to their mentee (for mentors). Norsetto will deal with that mail. Actions from this meeting: = porthose to contact hanno and james d caroll, to find a matching mentor. huats to contact slomo and jcorbier to know their intention about mentoring. huats to contact TheMuso to know more about his current mentoring of AstralJava norsetto to send an email to ask mentors and mentees what lectures they think should be given in the classroom. norsetto to send an email to encourage u-u-c and motu to participate as lecturers in classroom. [EMAIL PROTECTED] -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
New model for the mentoring program
Dear all, the current mentoring program has been in place for about one year. During this time several shortcomings of this model have become evident, especially as the number of new contributors grow. The alternative sponsoring model is also felt quite inadequate, especially for new contributors and contributors which are on their way to motuship. What is evident today, is that: - Some MOTU have weaknesses in certain skill areas - Those potential contributors who are not self-starters aren't getting started - There is an insufficient number of volunteers to act as Mentors - There is an insufficient number of volunteers to teach MOTU School classes - Many existing contributors have difficulty reaching a sufficient skill level to apply for MOTU With the introduction of the ubuntu-universe-contributors team, it is finally time that we implement the new structure, as we already discussed in [1] and [2]. Our proposal is to split the Mentoring program into two parts: - a program to help new contributors who wish personal attention when starting - a program to help established contributors who wish personal guidance when applying for motuship Furthermore, stronger ties with the current MOTU School program will be established. All participants in the Mentoring program will be expected to attend MOTU School sessions, and those not in regular attendance may no longer be eligible for Mentoring. All contributors alike are expected to take an active role in preparing and giving sessions on fields where they are particularly experienced, as well as in general QA sessions. The new program is detailed in: https://wiki.ubuntu.com/MOTU/Mentoring/NewModel Before finally implementing this change, we would like to hear from you, MOTU and contributors alike, if you have any remaining objections or comment. Cesare [1]https://lists.ubuntu.com/archives/ubuntu-motu-mentors/2007-October/000153.html [2]https://lists.ubuntu.com/archives/ubuntu-motu/2007-November/002728.html -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: motu-release
On Saturday 28 June 2008 00:08:20 Stefan Potyra wrote: Subquestions are: what do you (members of motu-release) would like to add, what did you observer generally in regards to motu-release, what to improve? One thing that irked me, and I would really do something about for Intrepid, was the fact that two positive votes are enough to approve any FFe, no matter if 3 out of 5 members are against it. I would definitively change this to a majority vote. The problem is that with the current number of members this would require 3/5 to pass which might not be attainable in a reasonable amount of time. Reducing the number of members to 3 (and therefore having 2/3 to pass) doesn't seem a good idea too. So, I'd propose a +2 in a (insert a reasonable amount of time here, 2 days since the date a _valid_ request was filed seems reasonable to me) ? The obvious drawback is that no FFe can be approved before the 2 days elapse, in my view a reasonable price to pay. An alternative would be to have a veto system, in which any member can stop the regular process by simply objecting (obviously with reasonable arguments) against the FFe. In this case the FFe will not be approved until the required majority is obtained. I'd also discourage the practice of accepting an FFe on the base of a short IRC chat without apparently any research on the implications and background of the request. We have an FFe process so lets make the best use of it (accepting an FFe because your buddy is asking you to do it on IRC, or because somebody you trust is telling you that it will be good to have that package, are not, in my humble view, good reasons to accept an FFe). Finally, I always found a nonsense that we have a rather strict system until few days before release and then exactly when we should really tighten the tap, we relax all requirements (its enough to have one IRC approval without sometime even filing a request). Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Getting Packages Updated
On Thursday 26 June 2008 16:29:21 Null Ack wrote: My apologies for asking what seem's like a basic question but how does a user go about requesting that a package get updated? Your email is a bit confused, but I guess you want to know about backports: https://help.ubuntu.com/community/UbuntuBackports I especially consider mplayer, gnome-player and x264 to be a special case where SVN builds do not pose any real risk to being backported into released Ubuntu revisions. About gnome-mplayer, there is absolutely no risk in backporting the development release to the stable release (I'm actually running 0.6.2 on gutsy). Its not done so far simply because nobody bothered to take the time and actually ask for it. HTH, Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Problems building R package from Intrepid for Hardy
On Sunday 22 June 2008 22:49:08 Paul Johnson wrote: In Hardy, we have R-2.6.2, but some R packages can't be used unless R is upgraded. I did not find any installable deb intended for Hardy systems, and decided to try to build. There are non-official Ubuntu binary packages made for 2.7.0 by Vincent Goulet and Michael Rutter. They are based on the official Debian packages from Dirk Eddelbuettel and Doug Bates. You can find them here: http://cran.r-project.org/bin/linux/ubuntu/ Note that it is in general a bad idea to mix different builds of r-cran-* so try to stick to 2.6.2 or 2.7.0 only. If you have any problems with these packages, please report them here: https://stat.ethz.ch/mailman/listinfo/r-sig-debian In case you still want to build from source, I highly suggest you use these scripts: https://vgoulet.act.ulaval.ca/svn/R/cran-ubuntu/ Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: motu-release
On Tuesday 17 June 2008 13:59:04 Stefan Potyra wrote: since there has been no response so far, let's try the other way round: Cesare, Luke, Sarah, Scott: Are you up for intrepid as well? If there is somebody else that wants to step in I'll be happy to stand aside, otherwise I´ll be happy to serve for Intrepid. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
motu-sru extension
Dear MC, please set up polls for extending motu-sru/replacing retired members [1]. Daniel, maybe you'd also like to transfer team ownership to MC (see [2]). Candidates: Stephan Hermann [3] Scott Kitterman [4] Cody A.W. Somerville [5] looks, like we need two members (follow-ups to [1]), but that might be subject to discussion. Can I propose to extend the numbers of members in the motu-sru team to 6? Unless somebody objects we can have a full team up and running again in no time, with plenty of enthusiasts ready to process all our SRU to everybody's satisfaction. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Can we have a source package in multiverse with a binary package in universe (Was: mplayer should be moved to universe)?
Consider the case that a ubuntu derivative (xubuntu, mythubuntu, etc) decides to include the mplayer binary package on their live cd. They would still be required to provide and offer the source package to all software on (in most cases a seperate) CD. This can become pretty delicate, since now the CD will contain stuff from multiverse, which is known to be very problematic (at best). I don't know either what the implications of having a source in multiverse and a binary in universe are, or if it is at all possible. I'm cc'ing this to ubuntu-devel, just in case somebody wants to enlighten us. But for this example, I don't really see a problem: Why would a derivative be obliged to offer sources on a CD!? What would be different from today, with mplayer on multiverse? For what I know, mythubuntu has it on its CD (as many other multiverse packages, mythtv and its depends are all in multiverse). Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: mplayer should be moved to universe
On Sunday 01 June 2008 04:15:12 Stefan Potyra wrote: hm... if only patent issues are a problem, I'd like to know what patents can actually cover. If patents only limit usage, but not distribution, I see no problems with putting mplayer sources in universe, and building binary mencoder packages in multiverse. Can someone clarify this? A quick check with apt-cache shows the following mplayer bd to be in multiverse (because of mencoder): em8300-headers libfaac-dev liblame-dev libx264-dev libxvidcore4-dev I have not checked them all in detail, but I have the impression they are in multiverse because they (directly or through bd/d) either contain microcode/firmware or use patented algorithms (at least patented in some countries). What these patents (or claimed patents) cover or not is a very good question for which I could not find an easy and clear answer, at least from this example for MP3 (see Licensing and patent issues): http://en.wikipedia.org/wiki/MP3 If a source in universe can bd on multiverse and have binaries in multiverse then yes, the easy solution would be to just have mencoder in multiverse. If not I don't see how to possibly solve this beside: 1) following Debian by disabling mencoder, which doesn't seem to be wished by seeing posts in this thread and reactions on IRC 2) having two different source packages (which, quite frankly, doesn't seem feasible from a maintenability pov). Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: SUSPECT: Re: mplayer should be moved to universe
On Sunday 01 June 2008 12:12:33 Cesare Tirabassi wrote: 1) following Debian by disabling mencoder, which doesn't seem to be wished by seeing posts in this thread and reactions on IRC 2) having two different source packages (which, quite frankly, doesn't seem feasible from a maintenability pov). I forgot 3) which perhaps could be investigated further: 3) having the mplayer source in multiverse producing an mplayer (and mplayer-nogui) binary packages in universe and an mencoder binary package in multiverse. Note that currently mplayer has the following deps in multiverse: liblame0 libx264-57 libxvidcore4 mplayer-skins I guess thats mainly a dpkg-shlibdeps artifact but for mplayer-skins (copyrighted art?). mplayer-skins is obviously not a dep of mplayer-nogui. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
mplayer should be moved to universe
Dear all, bug 214727 (https://bugs.edge.launchpad.net/ubuntu/%2Bsource/mplayer/%2Bbug/214727) has been raised on the subject. mplayer is a direct rdepend for many packages, and indirect for I guess many others. Your help on this would be appreciated, please check if there are missing packages that should be part of the change, or mark invalid those which should not be part of it (either because of license or dependencies reasons). Many thanks for your help, Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: mplayer should be moved to universe
On Friday 30 May 2008 15:32:22 you wrote: Mplayer decodes H.264 and other MPEG-4 type content, and also contains the same core codebase as mencoder which encodes to said format. From what I understand, that means we cannot put mplayer in multiverse. If this is incorrect, then I would like x264, xvidcore, and friends out into universe too :) Yes, apologies to all concerned for the noise. We are now back to our regular transmissions. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: sabbatical
It has really come to my attention that I need to have a sabbatical time away from Ubuntu development. As much as I regret this decision, I understand this is for your good. I'm looking forward to see you back with us (I'm sure it will be soon). Good luck Dr. Mantha! Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
r-base transition
Dear all, as some of you already know, we have completed recently the gfortran transition. One of the libraries involved was r-base, which now doesn't provide anymore libRblas.so (uses the blas one instead). Unfortunately quite a number of packages have been built already with the older version and are now broken (see for instance LP bug 217742 and bug 219245). A quick search with apt-cache shows the following R libraries (from packages depending on r-base-core) still linking against libRblas.so: /usr/lib/R/site-library/eco/libs/eco.so:libRblas.so = not found /usr/lib/R/site-library/fArma/libs/fArma.so:libRblas.so = not found /usr/lib/R/site-library/fAsianOptions/libs/fAsianOptions.so:libRblas.so = not found /usr/lib/R/site-library/fGarch/libs/fGarch.so: libRblas.so = not found /usr/lib/R/site-library/fNonlinear/libs/fNonlinear.so: libRblas.so = not found /usr/lib/R/site-library/fOptions/libs/fOptions.so: libRblas.so = not found /usr/lib/R/site-library/fRegression/libs/fRegression.so:libRblas.so = not found /usr/lib/R/site-library/fUnitRoots/libs/fUnitRoots.so: libRblas.so = not found /usr/lib/R/site-library/lme4/libs/lme4.so: libRblas.so = not found /usr/lib/R/site-library/Matrix/libs/Matrix.so: libRblas.so = not found /usr/lib/R/site-library/MNP/libs/MNP.so:libRblas.so = not found /usr/lib/R/site-library/polspline/libs/polspline.so:libRblas.so = not found /usr/lib/R/site-library/qtl/libs/qtl.so:libRblas.so = not found /usr/lib/R/site-library/quadprog/libs/quadprog.so: libRblas.so = not found /usr/lib/R/site-library/robustbase/libs/robustbase.so: libRblas.so = not found /usr/lib/R/site-library/tseries/libs/tseries.so:libRblas.so = not found /usr/lib/R/library/mgcv/libs/mgcv.so: libRblas.so = not found Any volunteer to help to manually upload all the rebuild patches will be highly welcome. Please coordinate your work through bug 219346 (https://bugs.launchpad.net/ubuntu/+bug/219346). Thanks, Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: NEW Packages process
On Wednesday 16 April 2008 11:38:19 Stefan Potyra wrote: I propose the following changes: 1) cut down the requirement to one ACK of a ubuntu-dev member I don't think, that's a good idea. I'm with Stefan here, from personal experience as a packager and reviewer one ACK is almost never enough; I know that I want somebody else reviewing my packages (still, there are always things to correct once they hit the archive). If the purpose of this proposal is to reduce the idle time for new packages in the REVU queue than I think there are better ways, the best imho would be to make it more attractive for devs to actually review new packages. It takes an awful lot of time to properly review these packages (most often than not as much as making them from scratch), and this is not recognised in any way. 2) requirement for the person who packaged the new software to become bug contact Yes, that sounds very good! I thought that was the norm ... Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: NEW Packages process
On Wednesday 16 April 2008 13:28:20 Daniel Holbach wrote: How do we justify this needs two reviewers - we don't trust one of them to do it right? It all boils down to the question: Why don't we trust one MOTU to get it right? Its not a question of trust, its a question that 4 eyes see better than 2. I know I don't rely on my packaging skills alone, no matter how much I work I will always miss something. Is the quality of packaging our main concern? Definitively. Please decide on your own how common a situation like this is on REVU: - comment by a MOTU: Could you add a watch file? Please move Homepage URL to its own Homepage field., no ACK - two weeks of inactivity - upload archived - some days later: new upload fixing the issues - ... - maybe an ACK, maybe not Very good example, and a showcase of why devs are not very keen in reviewing. First, the contributor missed even the more fundamentals of a package (other examples are native packages which are not, wrong standards, wrong distribution, etc.), so the reviewer instead of spending a whole morning reviewing the package just points out the more obvious (I would and never have done this by the way, this is a side product of having one reviewer trying to triage a long queue). Even then the contributor waits two weeks to make a fix which just takes 5 minutes at the most. Is he really interested in packaging? If I were the reviewer I don't think I will want to spend my time in reviewing things that will eventually just get thrown out of the window. By the way, how will lowering the required acks to one solve the above example? I'm convinced that fixes (fixing the Homepage field, bumping up the Standards-Version, etc) above are written quickly once the package is in the archive and should not block an upload. Should I ack a package that I know doesn't meet the required standards? I, for one, will not want to see Universe become another automatix or deb-o-matic. The right approach here (and this is quite often used) is to say: this is wrong but I'm not blocking for this so that the contributor knows about it (and a good contributor will upload a fix shortly after). We are a distributed team which maintains packages in the team and round-trips because of such things merely add frustration. Having gone very recently through this, yes, it adds frustration and is as much a fault of the contributor as of the reviewer. By lowering the bar we are not doing anyone a favour, just lowering the quality of the archive. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: saods9 in repository
On Wednesday 02 April 2008 00:46:14 Jason Quinn wrote: The saods9 package in the science (universe) section should probably be removed from the repository, perhaps permanently. Here's my reasoning: 1) The version presently there contains a bug that does not allow it to interact with IRAF, another big program used by astronomers. IRAF is very frequently used in conjunction with ds9. This is confusing when a person is installing IRAF because trying to display an image in ds9 from IRAF causes both to crash with no obvious way of knowing what caused it. 2) The ds9 program is very frequently updated and will be out-of-date almost as soon as it is added to the repository. They are up to version 5.1 now and not 4.0b7. 3) The ds9 program is extremely easy to install and consists of just a single executable file. Any user who would be interested to use it would be good enough with computers to manually install it. At the least, the program should be updated to fix reason #1. Cheers, Jason This is covered by https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/133784 which I'm planning to tackle since, unfortunately, the package was orphaned in Debian. This is not an easy package at all since the upstream tarball has to be severely edited for copyright reasons, and the homemade build system has to be practically replaced to produce an acceptable package (at least, that was the case for 4.0b7). I also had to mangle with some header files since the program uses its own c2f interface, which was not compatible with the gfortran compiler (again, to be checked for 5.1). IMHO, there is no way we could have this ready for Hardy, my goal was to upload an update for Intrepid. If the package is re-adopted in Debian and will receive regular maintenance this would obviously be the best solution. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: New: automatix 2.0.7-1 (source)
On Tuesday 01 April 2008 14:00:25 Sarah Hobbs wrote: Curses. I *knew* someone would try an april fools joke on me at some point today Hobbsee Don't feel alone in this . Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Hi all
On Friday 07 March 2008 18:25:19 Fahad Sadah wrote: So I don't need to do anything to get myself officially listed or something? Everybody is free to contribute, the only requirement is to be an ubuntero. If you read the links you have been given very carefully you will see what it means to be a contributor, a MOTU or a core-dev and what each step entails. Also, how do I submit packages to the repositories? As Emilio said, use the sponsoring queue (for bug fixes/merges/sync etc.) and REVU (http://revu.tauware.de/) for new packages. For the latter, since we are in feature freeze, your package(s) won't get reviewed before the new cycle begins tough. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Introduction
On Tuesday 12 February 2008 07:51:05 Balaji G wrote: I am so much interested in contributing to Ubuntu and hence have joined the MOTU list . Hi Balaji, I'm glad you joined! I am interested in fixing small bugs to start off with and have already started reading through the packaging guide in the Ubuntu Wiki. Thats a very good start. I can suggest you a couple of other wiki pages to look at: https://wiki.ubuntu.com/UbuntuDevelopment: should give you an overall view on what is involved in the Ubuntu development process. https://launchpad.net/ubuntu/+bugs?field.tag=bitesize: lists some bitesized bugs if you want to jump straight in https://wiki.ubuntu.com/MOTU/TODO: lists all activities we are currently performing. If you need help or have some questions you want answered, you could pay a visit to the IRC freenode channel #ubuntu-motu: https://help.ubuntu.com/community/InternetRelayChat We also have semiregular QA sessions on Fridays in #ubuntu-classroom, usually around 13:00 UTC. You should also subscribe to the ubuntu-motu-mentors mailing list where you could find help more suitable for a newcomer. Feel free to post any questions you have in ubuntu-motu or ubuntu-motu-mentors or to seek help in #ubuntu-motu. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: hi my name is lukasz
On Sunday 10 February 2008 22:51:08 [EMAIL PROTECTED] wrote: If I will be able to help that will be great, looking forward to hear any suggestions how to start. Hi there Lukasz, nice to have you here! A good starting point is this Wiki page: https://wiki.ubuntu.com/UbuntuDevelopment This should give you an overall view on what is involved in the Ubuntu development process. I can suggest you also start reading the packaging guide and work on some bitesized bugs if you want to jump straight in: https://wiki.ubuntu.com/PackagingGuide https://launchpad.net/ubuntu/+bugs?field.tag=bitesize https://wiki.ubuntu.com/MOTU/TODO If you need help or have some questions you want answered, pay a visit to the IRC freenode channel #ubuntu-motu: https://help.ubuntu.com/community/InternetRelayChat We have semiregular QA sessions on Fridays in #ubuntu-classroom (usually around 13:00 UTC). To see whats going on you should also subscribe to the ubuntu-motu-mentors mailing list, feel free to post any questions you have in this m.l, in ubuntu-motu-mentors or to seek help in #ubuntu-motu. Hope this helps, Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Call for UVF Team volunteers
We'll extend the nomination period for another week as we've only received ONE nomination up until now: only brave Luke Yelavich stepped up for the challenge. Come on MOTUs, don't leave him hanging, step up for it today! If there is a need I'll be glad to help. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
REVU: Uploaded: gimp-normalmap 1.2.1-0ubuntu1 (source)
NEW: gimp-normalmap_1.2.1.orig.tar.gz NEW: gimp-normalmap_1.2.1-0ubuntu1.diff.gz NEW: gimp-normalmap_1.2.1-0ubuntu1.dsc -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 09 Jan 2008 14:11:53 +0100 Source: gimp-normalmap Binary: gimp-normalmap Architecture: source Version: 1.2.1-0ubuntu1 Distribution: hardy Urgency: low Maintainer: Ubuntu MOTU Developers ubuntu-motu@lists.ubuntu.com Changed-By: Cesare Tirabassi [EMAIL PROTECTED] Description: gimp-normalmap - Normal map plugin for GIMP Launchpad-Bugs-Fixed: 181527 Changes: gimp-normalmap (1.2.1-0ubuntu1) hardy; urgency=low . * First release (LP: #181527) * The upstream tarball has been repacked from .bz2 to .gz Files: d0b685645ffa90e9bd22da80a429daff 756 graphics optional gimp-normalmap_1.2.1-0ubuntu1.dsc f45b8f92f898f26d1eed84bd89ce876f 145178 graphics optional gimp-normalmap_1.2.1.orig.tar.gz a0c238695aca5b3f927ade643d7e824b 1762 graphics optional gimp-normalmap_1.2.1-0ubuntu1.diff.gz Original-Maintainer: Cesare Tirabassi [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHjNpvysMrFvyAPHwRAvBHAJ41kbxmAG1rNK+ppfqIk8hz2xn0xQCggiZ/ YuudwD722U+coY5C7UMjJoc= =rsoH -END PGP SIGNATURE- -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
REVU: Upload: gpp4 1.0.4-0ubuntu1 (source)
NEW: gpp4_1.0.4.orig.tar.gz NEW: gpp4_1.0.4-0ubuntu1.diff.gz NEW: gpp4_1.0.4-0ubuntu1.dsc Format: 1.7 Date: Thu, 10 Jan 2008 00:06:26 +0100 Source: gpp4 Binary: libgpp4-doc libgpp4-0 libgpp4-dev Architecture: source Version: 1.0.4-0ubuntu1 Distribution: hardy Urgency: low Maintainer: Ubuntu MOTU Developers ubuntu-motu@lists.ubuntu.com Changed-By: Morten Kjeldgaard [EMAIL PROTECTED] Description: libgpp4-0 - shared library for CCP4 compatible programs libgpp4-dev - development environment for CCP4 compatible programs libgpp4-doc - doxygen generated documentation for libgpp4 Launchpad-Bugs-Fixed: 176209 Changes: gpp4 (1.0.4-0ubuntu1) hardy; urgency=low . * Initial release (LP: #176209) Files: 44a17501dd0cb1d674d2d4f9e7510f0d 713 science optional gpp4_1.0.4-0ubuntu1.dsc 48931781425a5b79a8255ebefaed24b3 498933 science optional gpp4_1.0.4.orig.tar.gz ee4728aeedda948455125c1fd228961f 3642 science optional gpp4_1.0.4-0ubuntu1.diff.gz Original-Maintainer: Morten Kjeldgaard [EMAIL PROTECTED] -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Failing to unpatch
On Wednesday 26 December 2007 22:53:51 Nicolas Valcarcel wrote: I working (or trying to) on Bug #178046 [1] and i have some doubts. Talking on #ubuntu-motu they have make me notice that the possible cause of the error is that some of the files is changing on build time and i need to backup it, but the facts are: - That patch modifies 181 files - The patch has 1.9 Mb - The patch is 60154 lines long That makes it a very hard work to find out what file is the problematic one, so i think the best to do here is to split the patch on smaller ones and then find which of them fails the thing is, can i split those files using filterdiff or i must use another dpatch method to do it the correct way. I have tried with filterdiff but something doesn't work fine but i don't know it was my error or it isn't the way to do it. 1. https://bugs.edge.launchpad.net/ubuntu/+source/dillo/+bug/178046 You can find which files/hunks fail by simply running dpatch deapply-all --verbose after the first build. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Change in the Mentoring program
On Sunday 25 November 2007 03:05:04 Brandon Holtsclaw wrote: People might be more inclined to volunteer if there was more visibility into the progress this project is making? I 100% agree, just dont have the numbers to make a solution to this. The file where the reception records the mentoring activities is here: https://code.launchpad.net/~motu-mentoring-reception Is public and readable by everyone. Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Change in the Mentoring program
On Sunday 25 November 2007 16:12:28 Scott Kitterman wrote: That doesn't really answer my questions: Right now, the purpose of mentoring is not solely that of preparing MOTUs, one of the very reasons to make the distinction clear in dividing it into two phases. If anything, most of mentoring is actually done as a one-on-one tutoring for totally new contributors; if we were to split the program in two stages right now, my own estimation is that not many contributors will fall in stage 2. We have one proposal from Emmet, do we have any other proposals? Do you think we should restrict mentoring to stage 1 only? Do you think we should steer the program to be a pure one-on-one preparatory program for MOTUship? Do you think we should dispense from mentoring altogether? And ultimately, what do you think we should do to increase the number of new contributors that actively participate and integrate within the Ubuntu community? Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Fwd: Re: Change in the Mentoring program
Thanks for sharing your opinion. This thread is of interest to #ubuntu-motu-mentors too, please cc any reply to that list as well. Cesare -- Forwarded Message -- Subject: Re: Change in the Mentoring program Date: Sunday 25 November 2007 From: Ming Hua [EMAIL PROTECTED] To: ubuntu-motu@lists.ubuntu.com I feel you are misunderstanding Scott. On Sun, Nov 25, 2007 at 06:48:00PM +0100, Cesare Tirabassi wrote: On Sunday 25 November 2007 16:12:28 Scott Kitterman wrote: That doesn't really answer my questions: [...] We have one proposal from Emmet, do we have any other proposals? Do you think we should restrict mentoring to stage 1 only? Do you think we should steer the program to be a pure one-on-one preparatory program for MOTUship? If you can't answer Scott's questions, my response to these questions, as an MOTU who never participated mentoring, is: Why should I care? Do you think we should dispense from mentoring altogether? Maybe, if after the mentoring program has been running for a few months, we still don't have a clear idea about what the program has achieved. Ming 2007.11.25 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
StableReleaseUpdates: rutilt (0.15-0ubuntu5.2) needs testing in gutsy-proposed
Dear all, if you are using the r73 module your help will be appreciated in testing rutilt, available in gutsy-proposed. If you would like to test it, please add the following lines to /etc/apt/sources.list: deb http://archive.ubuntu.com/ubuntu/ gutsy-proposed universe Then update and install rutilt with your preferred package manager. Please report test results to: https://bugs.edge.launchpad.net/ubuntu/+source/rutilt/+bug/164058 The TEST CASE is very simple, just check that rutilt is able to apply the choosen profile without any error being displayed. Many thanks in advance for your help! Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
StableReleaseUpdates: tagtool (0.12.3-2ubuntu0.1) needs testing in gutsy-proposed
Dear all, your help will be appreciated in testing tagtool, available in gutsy-proposed. If you would like to test it, please add the following lines to /etc/apt/sources.list: deb http://archive.ubuntu.com/ubuntu/ gutsy-proposed universe Then update and install tagtool with your preferred package manager. Please report test results to: https://launchpad.net/bugs/160152 The TEST CASE is very simple, just check that tagtool is correctly displaying all text by using the appropriate translations as specified by your environment. Many thanks in advance for your help! Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
StableReleaseUpdates: mono-addins (0.2-2ubuntu0.1) needs testing in gutsy-proposed
Dear all, your help will be appreciated in testing libmono-addins0.2-cil and libmono-addins-gui0.2-cil, which should be available soon in gutsy-proposed. If you would like to test them, please add the following lines to /etc/apt/sources.list: deb http://archive.ubuntu.com/ubuntu/ gutsy-proposed universe Then update and install libmono-addins0.2-cil and libmono-addins-gui0.2-cil with your preferred package manager. Please report test results to: https://launchpad.net/bugs/149485 The TEST CASE is very simple, just check that pkgconfig locate correctly the libraries: 1.1) pkg-config --libs mono-addins 1.2) pkg-config --libs mono-addins-setup 1.3) pkg-config --libs mono-addins-gui More details can be found under the TEST CASE header in the bug report. Many thanks in advance for your help! Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
StableReleaseUpdates: rutilt (0.15-0ubuntu5.1) available for testing in gutsy-proposed
A testing version of rutilt has been published in gutsy-proposed. To test it, please add the following line to your sources.list: deb http://archive.ubuntu.com/ubuntu/ gutsy-proposed universe Then, update and upgrade (or install) rutilt. Please provide feedback to https://bugs.launchpad.net/bugs/155498 Detailed description of the problem: In the Profile tab, after making a new profile and pressing the Apply button rutilt crashes. Many thanks in advance for helping, Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Forward porting gutsy-proposed uploads to Hardy
On Saturday 27 October 2007 21:26:48 Michael Bienia wrote: On 2007-10-23 18:05:31 +0200, Michael Bienia wrote: On 2007-10-23 10:19:51 -0400, Scott Kitterman wrote: As promised when we decided to go ahead with uploads to gutsy-proposed before hardy was open, here is the list of uploads that need to go into Hardy to catch up. Please reply to this message to the list when you've uploaded to hardy so it'll be easy to track. Source: gtk2hs Sync requested of gtk2hs 0.9.12-1 from Debian unstable. It contains the patch which is included in -proposed. Bug #157853: https://bugs.launchpad.net/bugs/157853 Michael Thanks for the head-up, I had totally forgotten we needed to report it: bug for which -proposed was issued Bug #64032: https://bugs.launchpad.net/ubuntu/gutsy/+bug/64032 new version uploaded in hardy https://lists.ubuntu.com/archives/hardy-changes/2007-October/65.html Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
StableReleaseUpdates: rpmstrap (0.5.2-2ubuntu0.1) available for testing in gutsy-proposed
A testing version of rpmstrap has been published in gutsy-proposed. To test it, please add the following line to your sources.list: deb http://archive.ubuntu.com/ubuntu/ gutsy-proposed universe Then, update and upgrade (or install) rpmstrap. Please provide feedback to https://bugs.launchpad.net/bugs/64032 Here you will find a detailed description of the problem. Thanks, Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Log of QA Session - Friday 19 October 2007
Dear all, you can find here the log of today's session: https://wiki.ubuntu.com/MOTU/QA/Logs/19-10-07 Thanks to RR D. for hosting and everybody who partecipated! Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
MOTU Mentoring Meeting
Dear All, This is a reminder for the MOTU Mentoring meeting, which will take place in #ubuntu-meeting on Freenode this Friday, October 19th at 13:00 UTC. Agenda is confirmed as follows: 1. Current status of the Mentoring program - Feedback from Mentors - Drop rate - Open requests status - Available slots vs. requests 2. Future of the Mentoring program - How to increase the number of Mentors - How to improve feedback and effectiveness of Mentors - Is it possible to select contributors and if yes, how? - Should we set-up a trial period? 3. AOB Thanks, MOTU Mentoring reception -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Log of QA Session - Friday 12 October 2007
Dear all, you can find here the log of today's session: https://wiki.ubuntu.com/MOTU/Q%26A/Logs/12-10-07 Thanks to Rockstar Daniel for hosting and everybody who partecipated! Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Welcome Mathias Gug!
Daniel Holbach wrote: Hello everybody, Mathias just joined the MOTU team! He's been doing great work on the ServerTeam and apparmor, so we're quite pleased to have him! Please join me in welcoming him! ROCK ON, Mathias! Have a nice day, Daniel Added Mathias and Evan to https://wiki.ubuntu.com/MOTU under MOTU News so that everybody can see their grinning faces :-) Cesare -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Refining MOTU Mentoring
On Tue, 2007-08-21 at 10:07 -0400, Scott Kitterman wrote: I thought this is what #ubuntu-motu was for? I thought for a long time if it was correct to publish the following snippet. I believe however that it is important to share with you some considerations I received from a disappointed contributor, on this very subject: Namely i had been several times at irc and asked some questions about several things (and heck there are a lot things i don´t know nor understand) but at best i got only very limited (if at all) answers. Everybody just seems to be too busy. And then continues: To me it felt that i am just in the way and the opposite of being helpful. It makes you think (at least it does for me). On the positive side I should also add that my personal experience is totally the opposite, whenever I asked a question (no matter how silly) I almost always got the answer (the same is valid for #ubuntu-devel and #ubuntu-bugs by the way). We have a lot of contributors in this list, and I think it is the right time for them to speak up and share their thoughts. We need you guys, and we need to know if what we do is valid or not. PLEASE ADD YOUR VOICE! Cesare SATELLITES: They are in SPACE and stay there by going so fast that they are never in one place enough to fall down. TELEVISIONS are bounced off them. They are part of SCIENCE. -- From A Scientific Encyclopedia for the Enquiring Young Nome by Angalo de Haberdasheri (Terry Pratchett, Wings) -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: review tool for new packages
On Sun, 2007-08-19 at 11:45 +0200, Reinhard Tartler wrote: Personally, I only see as a solution that of changing the ubuntu-universe-contributors team participation from an open to a restricted one. Only contributors that can show a minimum level of competence as well as a continued interested in Ubuntu and packaging should be allowed to join this team, and therefore contribute new packages to universe. I tend to agree with changing the joining policy of ubuntu-universe-contributors. This leads to the question who adds people to the team? The administrators of that team would need to decide who is able to submit packages for review and who is not. Given that the group we are talking about is expected to still learn about packaging, we cannot use that as criterium. I think the difficult bit would be to agree on a policy; how to implement that policy should just be a technical matter that (I think) can be easily solved. For instance, a couple of ideas: - to join some teams it is required to show having done a certain amount of work as well as a continuity in doing so. For contributors, this would mean to keep a public log of their contributions with links to relevant LP bug reports. - we have a running mentoring program, where mentors should be able to assess the readiness of their pupils to produce a certain basic (and I stress the word basic) standard of packaging, as well as the required continuity or interest shown. - we can set up a trial period, at the end of which new contributors can be confirmed as full participants of the team or rejected (or perhaps be granted an extension in case of personal problems, other real-life (tm) commitments etc.). In any case, kudos to you guys for REVU being up again! Cesare The person on the other side was a young woman. Very obviously a young woman. There was no possible way that she could have been mistaken for a young man in any language, especially Braille. -- The goddess with the nice earrings (Terry Pratchett, Maskerade) -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
First task
First of all, thanks for your pointers, help and especially patience with this newbie. I went along with something easy at first (Bug LP#88232: Package description is very out of date) :-) I changed the short description and long description in 'control' as follows: The award-winning Web browser from Mozilla Firefox 2 is now faster, more secure, and fully customizable. New powerful features have been added, among others: Web feeds, in line spell checking, integrated search capabilities, identity theft protection, and advanced tabbed browsing. The 'changelog' was changed with the following addition (using dch -i): firefox (2.0.0.2+1-0ubuntu2) feisty; urgency=low * package description updated (Closes: LP#88232) -- Cesare Tirabassi [EMAIL PROTECTED] Fri, 9 Mar 2007 09:08:04 +0100 I then rebuild the source package and checked that the executable build is ok. This is the diff between the two source packages: diff -Nru /tmp/JlARGXGcGM/firefox-2.0.0.2 +1/debian/changelog /tmp/goRRKpBClM/firefox-2.0.0.2+1/debian/changelog --- /tmp/JlARGXGcGM/firefox-2.0.0.2+1/debian/changelog 2007-03-09 09:59:15.0 +0100 +++ /tmp/goRRKpBClM/firefox-2.0.0.2+1/debian/changelog 2007-03-09 09:59:52.0 +0100 @@ -1,3 +1,9 @@ +firefox (2.0.0.2+1-0ubuntu2) feisty; urgency=low + + * package description updated (Closes: LP#88232) + + -- Cesare Tirabassi [EMAIL PROTECTED] Fri, 9 Mar 2007 09:08:04 +0100 + firefox (2.0.0.2+1-0ubuntu1) feisty; urgency=low * new upstream release 2.0.0.2 diff -Nru /tmp/JlARGXGcGM/firefox-2.0.0.2 +1/debian/control /tmp/goRRKpBClM/firefox-2.0.0.2+1/debian/control --- /tmp/JlARGXGcGM/firefox-2.0.0.2+1/debian/control2007-03-09 09:59:15.0 +0100 +++ /tmp/goRRKpBClM/firefox-2.0.0.2+1/debian/control2007-03-09 09:59:52.0 +0100 @@ -12,12 +12,11 @@ Provides: www-browser Conflicts: mozilla-firefox ( 1.5.dfsg-1) Replaces: mozilla-firefox -Description: lightweight web browser based on Mozilla - Firefox is a redesign of the Mozilla browser component, similar to - Galeon, K-Meleon and Camino, but written using the XUL user interface - language and designed to be lightweight and cross-platform. - . - This browser was previously known as Firebird and Phoenix. +Description: The award-winning Web browser from Mozilla + Firefox 2 is now faster, more secure, and fully customizable. + New powerful features have been added, among others: + Web feeds, in line spell checking, integrated search capabilities, + identity theft protection, and advanced tabbed browsing. Package: firefox-dom-inspector Architecture: all I guess this is somehow useless as most probably you don't want to update the source package just with this bit but it was a good exercise for me nonetheless :-) I will keep trying to do something useful for the MOTU/TODO but your comments/requests on the above will be highly appreciated! ct -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Willing to help
Hello everybody, my name is Cesare and I have way too much time to waste :-) Seriously, I'd be willing to give you guys an hand for packaging, merging, reviewing, or whatever other task I can do to help this community grow. Please let me know if and how I can be of help. I hope that posting in this list was the right thing to do, if not, apologies in advance. ct -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
