MOTU Meeting Minutes from 12 Jan 2006 (finally)
Hi folks, sorry for the delay... finally the notes from the last but one meeting can be found at https://wiki.ubuntu.com/MOTU/Meetings/2005-01-12 Feel free to correct them where they are wrong. A transcript is included below. Cheers, Stefan. P.S.: This is the collectors edition of the notes. Collect ten spelling mistakes to win a special price ;). -- Full log can be found at http://tiber.tauware.de/~sistpoty/motuminutes/motu_minutes_2006_01_12.log == Agenda == 1) Use of /usr/share/common-licenses/GPL vs /usr/share/common-licenses/GPL-2 for GPLed apps packages. (raphink) *Reference in Policy : http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile 2) TODOs: (sistpoty) * http://people.ubuntu.com/~doko/libstdc++5-deps.txt - Packages still depending on libstdc++5 * http://people.ubuntu.com/~doko/libstdc++-allocator-change.txt - packages not yet rebuilt for libstc++ allocator change 3) UVF (sistpoty) * extra time for universe? * how to handle packages on revu? 4) What's next todo? (sistpoty) * unmet dependencies * bug triage * packages, that ftbfs (who will run an automated test ? when ?) 5) Reorganization of MOTU-related Launchpad teams. See MOTUMeetingTeamReorg (lucas) 6) Code of conduct for REVU-uploaders : Currently, a lot of packages are uploaded to Ubuntu through REVU. What will happen to them in a year ? Will the first REVU-uploader still has to take care of them ? We don't want a universe filled with unmaintained packages. + Policy regarding unmaintained and useless packages which are only in Ubuntu. Should we remove them ? What's the procedure ? 7) Collaborative maintenance on tiber via svn or other means 8) Brainstorming/Ideas how to organize divergence in our universe == People attending == * Stefan Potyra (sistpoty) * Daniel Holbach (dholbach) * Stephan Hermann (\sh) * Daniel Chen (crimsun) * Yann Rouillard (chninkel) * Raphael Pinson (raphink) * Jordan Mantha (LaserJock) * Jani Monoses (janimo) * Lucas Duailibe (lucasd) * Jonathan Ridell (Ridell) * Charles Short (zul) * Oliver Gravert (ogra_ibook) * Reinhard Tartler (siretart) * Tolleg Fog Heen, but not really present (Mithrandir) == Discussion == 1) raphink wanted to know, whether packages that are GPL-2 should refer to /usr/share/common-licenses/GPL-2 instead of the link /usr/share/common-licenses/GPL, which points to the latest version of the gpl. This might lead to some trouble once GPL-3 is out for packages which don't state the or any later version term. \sh pointed out, that there are two licensing issues involved: The license of the packaged software and the work done by the maintainer. After a short discussions, common agreement was that this issue should be adressed in front of TB. 2) sistpoty mentioned two outstanding todo-points: packages still depending on libstdc++5 and packages that didn't get rebuilt for the libstdc++ allocator change. doko prepared two lists of packages which still depended on libstdc++5 and which didn't get rebuilt for the libstdc++ allocator change. These packages were already uploaded to be rebuilt, but FTBFS'd. siretart said, that the libstdc++5 depending packages might be the result of gcc-transition with some of these packages not build-depending on a particular gcc-version. sistpoty stated, that we need to build these packages at least with gcc-3.4. raphing wanted to know, what should be done with these packages: We should try to make them build again, either fix the issues or try new upstream versions. \sh pointed out, that some weren't properly maintained any longer; dholbach stated, that for some upstream stopped working as well. In a small side-discussion, it was asked what exactly will be frozen on UVF. [editors note: dholbach made that clear in a mail to ubuntu-motu, so I will skip that part]. Later during the meeting, doko stated, that his lists are regenerated on demand. 3) UVF and packages on revu There was some discussion how to handle UVF-exceptions. [editor's note: I will skip this part. See https://lists.ubuntu.com/archives/ubuntu-motu/2006-January/000177.html]. The item packages on revu was deferred as well, since we have time until FeatureFreeze to get these in. 4) What's next todo? \sh summarized our priorities quite good: prio 1) bugs, prio 2) unmet deps prio 3) poke buildd when it's necessary to rebuild universe?. siretart pointed out, that 3) should be done ASAP, since it doesn't need direct human interaction. sistpoty pointed out, that reviewing packages on revu should also get a high priority. dholbach stated, that a review day might get many new packages reviewed. It was shortly discussed to have some automation for unmet dependency checking. 5) lucas made a proposal to reorganize motu-teams of LP, to make it easier to understand the team structure: https://wiki.ubuntu.com/MOTUMeetingTeamReorg Unfortunately no other MOTU seemed to have
UVF exception: gnome-rdp 0.2.0
Hi, I'd like to ask for an UVF exception. The Gnome-RDP codebase was polished, and the GUI was redesigned. This means more usability, and it seems a bit more stable (thanks to the code cleanups). Builds without errors on i386. The needed infos are attached to my mail. Best regards, Szilveszter Farkas (Phanatic) --- gnome-rdp-0.1.3-r1/ChangeLog 2006-01-21 20:50:22.0 +0100 +++ gnome-rdp-0.2.0/ChangeLog 2006-02-04 14:51:21.0 +0100 @@ -1,10 +1,25 @@ -2006-01-21 Balazs Varkonyi [EMAIL PROTECTED] - * gnome-rdp-0.1.3-r1: +2006-01-03 Balazs Varkonyi [EMAIL PROTECTED] + * gnome-rdp-0.2.0: + - Code cleanup + - GUI redesign + - First implementations of group management for sessions + - 'CompressionLevel' support for VNC sessions + - 'ImageQuality' support for VNC sessions + - 'Mono.Posix.Catalog' replaced with 'Mono.Unix.Catalog' to fix compilation + warnings + - New about dialog added + - Gnome# removed from dependencies + - Port knocking feature has been removed. + +2006-01-28 Balazs Varkonyi [EMAIL PROTECTED] + * gnome-rdp-0.1.3-r1: + - gnome-rdp.pot has been added for further translations - License header has been added for source files. - Some small changes in src/Makefile.am 2005-10-23 Balazs Varkonyi [EMAIL PROTECTED] - * gnome-rdp-0.1.3: Port knocking feature has been added. + * gnome-rdp-0.1.3: + - Port knocking feature has been added. 2005-10-09 Balazs Varkonyi [EMAIL PROTECTED] * gnome-rdp-0.1.2: @@ -15,6 +30,6 @@ - Only one session can be open from the main wnd. 2005-09-16 Balazs Varkonyi [EMAIL PROTECTED] - - * gnome-rdp-0.1.1: Initial release + * gnome-rdp-0.1.1: + - Initial release ChangeLog| 25 Makefile.in |6 README |1 configure| 368 ++--- configure.in | 16 icons/Makefile.in|6 po/gnome-rdp.pot | 334 po/hu.po | 413 +++-- resources/Makefile.in|6 resources/gnome-rdp-icon.png |binary resources/gnome-rdp.png |binary resources/group_16.png |binary resources/rdp_16.png |binary resources/ssh_16.png |binary resources/title.png |binary resources/vnc_16.png |binary src/AboutDialog.cs | 44 src/AssemblyInfo.cs | 18 src/CategoryDialog.cs| 127 + src/Configuration.cs | 486 ++ src/Defines.cs.in|1 src/GladeDialog.cs |2 src/Main.cs | 945 ++--- src/Makefile.am | 30 src/Makefile.in | 37 src/OptionsDialog.cs | 240 ++- src/ProcessCaller.cs | 117 + src/SessionTreeView.cs | 203 ++ src/Sqlite.cs| 11 src/TerminalDialog.cs| 11 src/gui.glade| 3073 --- 31 files changed, 4188 insertions(+), 2332 deletions(-) -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Subject: UVF Exception: ikvm 0.24.0.1
our current version of ikvm 0.22.0.0 a) doesn't build with the current mono b) doesn't work with the current mono The only rdepend is monodevelop-java (universe). The diff is pretty sizeable, but it appears to be plainly stabalizing releases. I see no problem bumping ikvm, as noted it doesn't work now and it has only one rdepend. Thanks, Brandon Hale -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: REVU Tools
Hello fellow MOTUs, Just felt like writing a bit of bash tonight after dinner... and worked on REVU-tools again. I think I'll upload it to the REVU svn tomorrow, but if any of you feel like giving some feedback, the tarball can be found at http://revu.tauware.de/~raphink/revu-tools_0.2.tar.gz . Changelog : - pbuilder-hooks/B01debuildtest : * Added directory name detection in pbuilder-hooks/B01debuildtest to avoid a dirty cd /tmp/buildd/* ; - revu-build : * Cleaning files from previous runs in revu-build, revu-orig and revu-report ; * Adding PBUILDERHOOKS variable to set the script cleanly ; - revu-orig : * revu-orig now takes two optional arguments (tarball and dsc) and can auto-detect them if not given explicitely ; * Detecting orig.tar.gz automagically in revu-orig. Using it as a variable now and detecting Debian-native packages ; * Adjusted tarball type detection in revu-orig to untar upstream tarball ; - revu-report : * Inverted the tarball and dsc arguments in revu-report (since tarball is harder to detect) and made optional arguments ; * Automagically decting dsc and tarball in local folder ; * Adding report entries for Debian-native packages ; * Adapting md5 report entries depending on whether the upstream tarball is tar.gz or other. Cheers Raphaël On 2/4/06, Raphaël Pinson [EMAIL PROTECTED] wrote: Hello fellow MOTUs, Since I have based most of my work on reviewing packages so far, I have been interested in improving the tools on REVU, so that it would be possible to review a package entirely without having to use the console more than once. I have noticed that the main reasons to use the console to review packages were the following: 1) pbuilding the package 2) running a `debuild debuild -S -sa` test for diff 3) comparing the md5 sums of the orig and upstream tarballs 4) checking the diff -ru of the untared orig and upstream tarballs if the md5 sums are different 1) is already achieved by revu-build on tiber. All other ones were lacking and had me get the files and my console on my machine. So I got to work to try and automatize all this. The result is a set of script, that I have added to the REVU svn (revu1 so far) and are waiting to be added to REVU. These scripts can be found at http://revu.tauware.de/~raphink/revu-tools_0.1.tar.gz . When well set (sorry, haven't made a doc yet ...), running revu-report with two arguments (the dsc and the upstream tarball) will generated a few files and a full report. As examples, this is the report that it created with a dirty package : http://revu.tauware.de/revu1-incoming/kblogger-0602030840/REVU_report ; and this is what was created with a rather clean one : http://revu.tauware.de/revu1-incoming/vbaexpress-0602031505/REVU_report . I'm sure the reviewers of you see the use of such a tool : almost all the reviewing that is left can be checked by browsing the source packages on REVU. Note: there is still a need for a tool to check for the pre-existence of identical/similar packages in other sources (Debian, apt-get.org, etc.), and for a tool to automatically get the upstream tarball if that is ever possible to develop. I'm looking forward to comments and suggestions on it :) Cheers, Raphaël [EMAIL PROTECTED] -- Raphaël Pinson - [EMAIL PROTECTED] http://raphink.multiply.org Ichthux - http://www.ichthux.org - Christian Linux Distribution -- Raphaël Pinson - [EMAIL PROTECTED] http://raphink.multiply.org Ichthux - http://www.ichthux.org - Christian Linux Distribution -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
