Re: debdiff question
On 16/07/07 06:41, Charlie wrote: > Ok I'm stupid, learning how to use debdiff, how do I get debdiff to send > it's output to a file? $ debdiff foo bar > baz.debdiff Further reading: https://wiki.ubuntu.com/MOTU/Recipes/Debdiff Regards, -- Andy Price -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: debdiff question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jul 16, 2007 at 03:41:49PM EST, Charlie wrote: > Ok I'm stupid, learning how to use debdiff, how do I get debdiff to send > it's output to a file? debdiff package1.dsc package2.dsc > filename.diff - -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGmwYyjVefwtBjIM4RAlPCAKCyTWbLEctLo1tHVkr6BzMdnkLl1gCfRe7S u/wmaCOY6hSyGDMPFdR8A8E= =rd3Z -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
debdiff question
Ok I'm stupid, learning how to use debdiff, how do I get debdiff to send it's output to a file? Regards Charlie -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
REVU: xfce4-timer-plugin 0.5.1-0ubuntu1_source.changes is NEW
Format: 1.7 Date: Sat, 30 Jun 2007 09:46:34 +0200 Source: xfce4-timer-plugin Binary: xfce4-timer-plugin Architecture: source Version: 0.5.1-0ubuntu1 Distribution: gutsy Urgency: low Maintainer: Ubuntu MOTU Developers Changed-By: Vincent Legout <[EMAIL PROTECTED]> Description: xfce4-timer-plugin - timer plugin for Xfce panel Launchpad-Bugs-Fixed: 123141 Changes: xfce4-timer-plugin (0.5.1-0ubuntu1) gutsy; urgency=low . * Initial release (LP: #123141) * Original tarball repacked to remove .svn dirs and aclocal.m4 Files: f2745ec58bc039eebee1e70bd9717960 740 x11 optional xfce4-timer-plugin_0.5.1-0ubuntu1.dsc dc0877756a0e1cf45e18156112c50e0a 312969 x11 optional xfce4-timer-plugin_0.5.1.orig.tar.gz 556140eac0800d8965e8030e5e1abd33 1393 x11 optional xfce4-timer-plugin_0.5.1-0ubuntu1.diff.gz Original-Maintainer: Vincent Legout <[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: PrBoom Locks up X
I know how to Resolve the PrBoom Lockup issue. Install Timidity++ and start it as a Virtual Midi service -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Web view of debian/changelog
On Sunday 15 July 2007 20:11, Scott Kitterman wrote: > On Mon, 16 Jul 2007 01:30:27 +0200 Soren Hansen <[EMAIL PROTECTED]> wrote: > >On Mon, Jul 16, 2007 at 09:27:02AM +1000, Christopher James Halse Rogers > > wrote: > >> On Sun, 2007-07-15 at 19:11 -0400, Scott Kitterman wrote: > >> > Is there an Ubuntu equivalent of packages.debian.org's web display of > each package's debian/changelog, e.g.: > >> > >> Yes; for python-dns the url is: > >> https://launchpad.net/ubuntu/gutsy/+source/python-dns/+changelog > > > >That only seems to include the changelog entry since the package got > >imported into Ubuntu. Thanks for pointing it out, though. I didn't > >realise Launchpad had that. :) > > It also mangles the who in the last (top) entry. It leads me to believe > that this is a concatenated view of the changes files and not actually the > changelog. In fact, I think that's what it is. The launchpad view lists the changelog entry in .changes for the releases currently in the repository (and not the interim releases. Moreover, calling it a changelog is very misleading since that's not what it is. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Web view of debian/changelog
On Mon, 16 Jul 2007 01:30:27 +0200 Soren Hansen <[EMAIL PROTECTED]> wrote: >On Mon, Jul 16, 2007 at 09:27:02AM +1000, Christopher James Halse Rogers wrote: >> On Sun, 2007-07-15 at 19:11 -0400, Scott Kitterman wrote: >> > Is there an Ubuntu equivalent of packages.debian.org's web display of each >> > package's debian/changelog, e.g.: >> > >> Yes; for python-dns the url is: >> https://launchpad.net/ubuntu/gutsy/+source/python-dns/+changelog > >That only seems to include the changelog entry since the package got >imported into Ubuntu. Thanks for pointing it out, though. I didn't >realise Launchpad had that. :) > It also mangles the who in the last (top) entry. It leads me to believe that this is a concatenated view of the changes files and not actually the changelog. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Web view of debian/changelog
On Mon, Jul 16, 2007 at 09:27:02AM +1000, Christopher James Halse Rogers wrote: > On Sun, 2007-07-15 at 19:11 -0400, Scott Kitterman wrote: > > Is there an Ubuntu equivalent of packages.debian.org's web display of each > > package's debian/changelog, e.g.: > > > Yes; for python-dns the url is: > https://launchpad.net/ubuntu/gutsy/+source/python-dns/+changelog That only seems to include the changelog entry since the package got imported into Ubuntu. Thanks for pointing it out, though. I didn't realise Launchpad had that. :) -- Soren Hansen http://www.ubuntu.com/ signature.asc Description: Digital signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Web view of debian/changelog
On Sun, 2007-07-15 at 19:11 -0400, Scott Kitterman wrote: > Is there an Ubuntu equivalent of packages.debian.org's web display of each > package's debian/changelog, e.g.: > Yes; for python-dns the url is: https://launchpad.net/ubuntu/gutsy/+source/python-dns/+changelog In general, LP->source package->overview tab->gutsy->view changelog (in lefthand sidebar). Chris Halse Rogers -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Web view of debian/changelog
On Sunday 15 July 2007 19:16, Soren Hansen wrote: > On Sun, Jul 15, 2007 at 07:11:39PM -0400, Scott Kitterman wrote: > > Is there an Ubuntu equivalent of packages.debian.org's web display of > > each package's debian/changelog, e.g.: > > > > http://packages.debian.org/changelogs/pool/main/p/python-dns/current/chan > >gelog > > Sure. We have: > http://changelogs.ubuntu.com/changelogs/pool/universe/p/python-dns/python-d >ns_2.3.1-1/changelog > > It's linked from http://packages.ubuntu.com/gutsy/python/python-dns Thanks. I hadn't noticed that (I almost always look packages up on Launchpad, I guess that's what I get). Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Web view of debian/changelog
On Sun, Jul 15, 2007 at 07:11:39PM -0400, Scott Kitterman wrote: > Is there an Ubuntu equivalent of packages.debian.org's web display of each > package's debian/changelog, e.g.: > > http://packages.debian.org/changelogs/pool/main/p/python-dns/current/changelog Sure. We have: http://changelogs.ubuntu.com/changelogs/pool/universe/p/python-dns/python-dns_2.3.1-1/changelog It's linked from http://packages.ubuntu.com/gutsy/python/python-dns -- Soren Hansen http://www.ubuntu.com/ signature.asc Description: Digital signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Web view of debian/changelog
Is there an Ubuntu equivalent of packages.debian.org's web display of each package's debian/changelog, e.g.: http://packages.debian.org/changelogs/pool/main/p/python-dns/current/changelog Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Merges - Pinging Previous Uploaders
On Sunday 15 July 2007 18:21, Michael Bienia wrote: > On 2007-07-15 17:45:37 -0400, Scott Kitterman wrote: > > On Sun, 15 Jul 2007 13:20:16 +0200 Michael Bienia > > <[EMAIL PROTECTED]> > > > > wrote: > > >I don't know what the best solution for this but it should work for both > > >main and universe packages easily. > > > > Personally all these option seem FAR more complex than just asking the > > person that dealt with it last. > > The last uploader has not to be the last merger. > Person A does a merge, person B does an upload (say for a rebuild or an > easy fix) -> MoM lists B as last upload. But asking person A about the > new merge can be more helpful than asking person B. > > I've the impression that MoM works for main better than for universe. > Main has small teams caring for specific packages sets (like Gnome) > where the same team or person does the merges. > MOTU is a larger team and doesn't have this "ordering" like main. > Relying on the "Last Uploader" field on MoM doesn't work for us. We need an > other mechanism to coordinate our efforts. > > An aggressive suggestion would be to drop the "Last uploader" field for > universe package from MoM if it doesn't work out for us and "lock" > merges with "In progress" bugs (or through some other means). > All of which is still way more complex than asking. Part of the beauty of asking is that one can look in debian/changelog and it's pretty easy to understand who to ask without a lot of rules or adding weight to the process. The more time people spend on process overhead, then less work actually gets done. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Merges - Pinging Previous Uploaders
On 2007-07-15 17:45:37 -0400, Scott Kitterman wrote: > On Sun, 15 Jul 2007 13:20:16 +0200 Michael Bienia <[EMAIL PROTECTED]> > wrote: > > > >I don't know what the best solution for this but it should work for both > >main and universe packages easily. > > Personally all these option seem FAR more complex than just asking the > person that dealt with it last. The last uploader has not to be the last merger. Person A does a merge, person B does an upload (say for a rebuild or an easy fix) -> MoM lists B as last upload. But asking person A about the new merge can be more helpful than asking person B. I've the impression that MoM works for main better than for universe. Main has small teams caring for specific packages sets (like Gnome) where the same team or person does the merges. MOTU is a larger team and doesn't have this "ordering" like main. Relying on the "Last Uploader" field on MoM doesn't work for us. We need an other mechanism to coordinate our efforts. An aggressive suggestion would be to drop the "Last uploader" field for universe package from MoM if it doesn't work out for us and "lock" merges with "In progress" bugs (or through some other means). Michael -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Merges - Pinging Previous Uploaders
On Sun, 15 Jul 2007 13:20:16 +0200 Michael Bienia <[EMAIL PROTECTED]> wrote: > >I don't know what the best solution for this but it should work for both >main and universe packages easily. Personally all these option seem FAR more complex than just asking the person that dealt with it last. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Merges - Pinging Previous Uploaders
On Sun, Jul 15, 2007 at 01:20:16PM +0200, Michael Bienia wrote: > > The advantage of a file in the source package is that one has it > automatically when one fetches the source. > But the big disadvantage is that one needs an upload to update that > file. As a compromise, packages using VCS for packaging can say in the file, "The packaging is maintained in $VCS, please always check $VCS_URL before you update this package". > If the package has a bzr branch one could update the file there but most > packages haven't a bzr branch yet. And what about package which are in a > Debian VCS? > > I don't know what the best solution for this but it should work for both > main and universe packages easily. Ming 2007.07.15 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: I guess you know all about this error
On Tue, Jun 19, 2007 at 03:28:20PM -0400, Cefn Hoile wrote: > But just in case, here's the summary. > > Architecture: all > Version: 5.5.20-4ubuntu1 > > http://cefn.com/blog/ubuntutomcat.html Its better to report bugs into our bug tracking system. Then we can track the issues. If there is already a bug report about this, please add additional issues about it. Please dont just add links, add the concrete information. Thanks for taking the time to report bugs for Debian. Cheers, Michael -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
upcoming REVU days
Hi, the next REVU days will be tomorrow on Monday, July 16th and one week later on July the 23rd. Again we'll be trying to flood the new queue by reviewing as many packages on REVU as possible, giving immiediate feedback to the package creators. If you are an ubuntu developer, please come around to #ubuntu-motu on freenode and help to review packages sitting on REVU. If you are a contributor and want your package to get included into ubuntu, please join us too at #ubuntu-motu and ask around (ideally with an URL to your source package on REVU) to get your package reviewed. Cheers, Stefan. signature.asc Description: This is a digitally signed message part. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Merges - Pinging Previous Uploaders
On 2007-07-15 07:37:12 +0900, Emmet Hikory wrote: > As a result of this, I am now uncertain whether to prefer > something as part of the package, or as a launchpad whiteboard. > Personally, I believe my workflow would be simplified for notes within > the package, but downloading source is a low barrier for me: each > developers' environment differs, and for some it may be signficiantly > higher. Both LP and a text file in the package have their advantages and disadvantages. The advantage of LP would be that information can be updated independent from the package. If somebody does a merge and get stuck at some place (like FTBFS due to new libs), one could add a note mentioning it. Or that is in contact with Debian or upstream about an issue and that the package should currently be not merged. But I don't feel like bug reports are the right place for such information. One would need a convention how those bug should be named to be easy to find by mergers, especially if the packages has many bugs (like some packages in main). The disadvantage is that one needs to go to LP to get it but one should check the bug lists for easy fixes/ patches when doing an upload/merge. Therefore I don't see it as a real disadvantage. The advantage of a file in the source package is that one has it automatically when one fetches the source. But the big disadvantage is that one needs an upload to update that file. If the package has a bzr branch one could update the file there but most packages haven't a bzr branch yet. And what about package which are in a Debian VCS? I don't know what the best solution for this but it should work for both main and universe packages easily. Regards, Michael -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Merges - Pinging Previous Uploaders
On 7/15/07, Reinhard Tartler <[EMAIL PROTECTED]> wrote: > I don't think that everyone is checking launchpad before doing > merges. Mostly, I only check the MoM page and then use grab-source.sh to > get them. Or I directly do 'apt-get source '. Having to look at > the lp whiteboard is another step complicating my workflow. I would think any use of grab-source.sh, apt-get source, or bzr checkout without checking launchpad both dangerous and not best practice for working as a team. When touching a package for any reason (merge, bugfix, rebuild, feature improvement, etc.), please check the LP page to make sure there are no "In-Progress" bugs, as otherwise it's easy to unexpectedly interact with others effort, possibly requiring readjustment to match others changes, perhaps causing others to readjust to match your changes, perhaps being a duplication or work, and possibly involving conflicts due to changes in similar places. Additionally, checking the package bugs page may provide some guidance on additional things that might be easy to fix in the same upload, resulting in generally improved packages. -- Emmet HIKORY -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: PrBoom Locks up X
Zombie Ryushu <[EMAIL PROTECTED]> writes: > PrBoom 2.4.6 has a lockup issue it needs to be updated to 2.4.7 for > Fiesty Fawn filed as https://bugs.launchpad.net/ubuntu/+source/prboom/+bug/98946 -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Merges - Pinging Previous Uploaders
Jordan Mantha <[EMAIL PROTECTED]> writes: > I think I can get a whiteboard added to the > launchpad.net/ubuntu/+source/ page. I think putting notes in BZR > is really suboptimal at this point because we have very few packages that > use it. Putting info in a README.Ubuntu or something seems ok, but I'd like > people to be able to see stuff *before* they grab the source. I don't think that everyone is checking launchpad before doing merges. Mostly, I only check the MoM page and then use grab-source.sh to get them. Or I directly do 'apt-get source '. Having to look at the lp whiteboard is another step complicating my workflow. This extra information would ideally be displayed while using these two tools. It is not really important where they get their information from, I just feel it is more practical to have that in the package than in launchpad. > So I see two issues: > 1. Being able to "lock" a merge when you're working on it. This should be > done via bug reports. Ideally, on the commandline, like the resquestsync tool. > 2. Some packages have tricky things or larger scale issues and we should > have some way to share per-package information. I think a LP whiteboard > could work for this. FWIW, I prefer writing such documentations in a textfile, while working on a package. Therefore I suggest that this information should go to either debian/changelog, or debian/README.source. And another point: It is already possible to have and use a whiteboard: You can already link a package to a packaging branch, and that branch already has a whiteboard ready for use. Package not in bzr obviously don't profit from this. For those packages it indeed makes sense to have a "source package whiteboard". But is this the majority of packages we are talking about? I mean, we are talking about packages which have special requirements and considerations to be taken into account while merging. I think for those packages, it really makes sense to record your steps while working, so the are more likeley to be kept in bzr. At least, it would make more sense to do that than for easier packages. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
