Re: motu-release needs you
+1 from me too, Luca is an excellent person and i'm sure he will do a great work! On Wed, 2008-08-27 at 20:51 +0200, Cesare Tirabassi wrote: 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 -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: I cannot continue with Ubuntu development using LP
There is a quick, but not the best solution, which is, if your browsers supports it, to zoom, so the letter can be bigger. On firefox you can do that on View - Zoom - Zoom in. On Thu, 2008-08-28 at 10:21 +0200, Cesare Tirabassi wrote: 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 -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: Dustin Kirkland (kirkland) is now a MOTU
Congratulations! On Sun, 2008-08-24 at 03:13 +0900, Emmet Hikory wrote: Please join me in welcoming Dustin Kirkland (kirkland) to the MOTU team. Dustin has been working on Ubuntu for the past 7 months, with a concentration on the server, and has been inolved in upstream development for the part 5 years. He is planning to help mentor new contributors and improve the server suite. -- Emmet HIKORY -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: Patch systems in packages
On Sun, 2008-08-17 at 01:27 -0400, Scott Kitterman wrote: For Debian, many maintainers keep their packages in their favorite VCS and so it's less relevant as a policy issue. Yes, but for the debian maintainers it will be easy to check for separate patches on the debian derivatives than reading a big diff including a lot of changes. -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: DebianPython New-policy.
The debian-devel[1] list would be the right place to ask 1. http://lists.debian.org/debian-devel/ On Tue, 2008-08-12 at 19:58 +0200, Henrik Stokseth wrote: http://wiki.debian.org/DebianPython/NewPolicy it's on the debian servers but i wasn't sure who to contact. - Henrik Nicolas Valcarcel wrote: Can you please add links to the document you are referring? On Tue, 2008-08-12 at 17:23 +0200, Henrik Stokseth wrote: Seems this wasn't strictly necessary according to pythonsupport's docs: *** You don't need X[BS]-Python-Version fields. You don't need *** *** debian/pycompat. You don't need to call dh_python after*** *** dh_pysupport. Just remove all of these.*** However python-central still uses them. So the DebianPython policy should be updated accordingly. Sincerely, Henrik. -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: sync request sponsorship
That sounds pretty fair to me. It was just an idea, but now thinking it better and reading this arguments i'm convinced it's not a good one :D Thank you for your time and responses. On Mon, 2008-08-04 at 14:01 +0900, Emmet Hikory wrote: Nicolas Valcarcel wrote: Now that we have the uuc team up and running, wouldn't it be a good idea that uuc members can ACK sync requests, since they are supposed to be experienced contributors and should be capable to make sync requests by their own? No. There is little difference between a manual upload and a sync, other than the mechanism by which the changes come to the repository, and as such the same criteria for determining whether someone can upload to the archive ought be applied. As there is no technical review involved in an application to UUC, there is no certain knowledge that any given applicant has the necessary technical skills to be trusted with a sync request (or indeed, any sort of upload). Rather than change the permission structure of uploads, I'd rather encourage those that have the requisite technical skills to apply for MOTU: that results in review by both current MOTU and MOTU Council review, and is likely to help identify those who ought be able to commit to the archive directly. -- Emmet HIKORY -- aka nxvl Peruvian LoCo Team Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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
pbuilder twice in a row option
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 -- aka nxvl Peruvian LoCo Team Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: pbuilder twice in a row option
Sounds fair to me, i will change the name of the option to --build-twice On Sun, 2008-08-03 at 14:20 -0700, Jonathan Marsden wrote: Nicolas Valcarcel wrote: 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. I like the idea and I can see its value (even though using it will make pbuilder even slower...!). I wonder if the option name is a little long, and hard to type? For example, will we really ever see a pbuilder option something like --build-twice-and-dance-around-the -room-between-the-two-builds ? :-) I suspect not. The in-a-row part is implied, isn't it? So, maybe the option could be called--build-twice which is still descriptive, but less typing? If there is really a need for a (not-in-a-row) option, to do something specific between the two builds, perhaps that can be a separate option, maybe --between-builds=shell-command-to-execute ? Jonathan -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: pbuilder twice in a row option
I've changed it for a --twice option so it will end with: # pbuilder build --twice file.dsc The patch is on Bug's 254305 report. 0. https://bugs.edge.launchpad.net/ubuntu/+source/pbuilder/+bug/254305 On Sun, 2008-08-03 at 21:26 -0400, Nicolas Valcarcel wrote: Sounds fair to me, i will change the name of the option to --build-twice On Sun, 2008-08-03 at 14:20 -0700, Jonathan Marsden wrote: Nicolas Valcarcel wrote: 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. I like the idea and I can see its value (even though using it will make pbuilder even slower...!). I wonder if the option name is a little long, and hard to type? For example, will we really ever see a pbuilder option something like --build-twice-and-dance-around-the -room-between-the-two-builds ? :-) I suspect not. The in-a-row part is implied, isn't it? So, maybe the option could be called--build-twice which is still descriptive, but less typing? If there is really a need for a (not-in-a-row) option, to do something specific between the two builds, perhaps that can be a separate option, maybe --between-builds=shell-command-to-execute ? Jonathan -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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
sync request sponsorship
hi! Now that we have the uuc team up and running, wouldn't it be a good idea that uuc members can ACK sync requests, since they are supposed to be experienced contributors and should be capable to make sync requests by their own? -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: New model for the mentoring program
That actually depends on the talker, we can't say them when to give the sessions. Also keep in mind that work hours in my timezone may not be at yours, so it's really difficult to manage. On 7/15/08, Hanno Stock [EMAIL PROTECTED] wrote: First let me tell you, that overall I think that the current proposal is a good idea. Cesare Tirabassi schrieb: 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. I noticed that the MOTU school sessions often are during work hours (of course, since developers are scattered across all timezones). How are you about to address this problem? Greetings, Hanno -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Good communication with upstream is good idea
I think that's cool, but don't understand where cvs-tracker comes in the picture. I'm adding ubuntu-harcoded to hear their opinions On Mon, 2008-07-21 at 15:07 +0200, Stephan Hermann wrote: Moins Oliver :), re all :) On Mon, 21 Jul 2008 14:46:42 +0200 Oliver Grawert [EMAIL PROTECTED] wrote: hi, Am Montag, den 21.07.2008, 08:37 +0200 schrieb Stephan Hermann: What needs to be done to make it work on Ubuntu, too? I think that's one of the easiest things to achieve...if something is not working on Ubuntu, but it's something which works on debian, we could make sure, it will work on Ubuntu too... that was my first thougth too, which made me test the tool to find it works just fine in 8.04 (indeed not taking ubuntu security updates into account that might have fixed the listed debian side issue already) ... what Florian was concerned about above is that it uses debian server resources to obtain the list, our userbase is big enough to put an inconvenient extra amount of bandwith onto their servers if i.e. someone blogs about the tool on planet.ubuntu.com ... Well, if that is really a problem... so a server of any kind and someone to take care of it would be needed for a start, looking at the code some minor changes would be needed to the defaults to make it point to the ubuntu server instead of the debian one ... (and preferably the server sided list should take the USN list into account instead of the debian list of issues) if someone is going to fix this asap, I can provide bandwidth (or if it's really a cool security update package tracker for debian and ubuntu we can also ask to host the server side somewhere at CDC). But bandwidth is not a problem...and a server is always there... \sh -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: Emanuele Gentili (emgent) is a MOTU!
Wow! you did it before than me! Awesome! Congratulations!!! On Thu, 2008-07-10 at 11:00 +0200, Daniel Holbach wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everybody, I'm very pleased to welcome Emanuele Gentili to the MOTU team! Working with the Security Team for several months and a clear focus on other security-related activities got Emanuele a good reputation and lots of sponsors weighed in on his application. Please give him a warm welcome to the team! Have a nice day, Daniel - -- My 5 today: #246804 (vzctl), #246330 (xchat), #246754 (rinse), #246715 (ubuntu), #244663 (hildon-theme-mobile-basic) Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIdc+wRjrlnQWd1esRAk6oAJ91os2pv51pAPLfxgZivJ0CFmw0bgCfaxLl mQOYYjgzCcfdP+Ciu69gFrM= =xH2S -END PGP SIGNATURE- -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: GTKPOD needs a new package, please.
None of this version hace support for last generation iPods since Apple has include a security control on the new iPods, so they can't been used from other software rather than iTunes. On Tue, Jul 8, 2008 at 7:57 PM, Nicolas Valcarcel [EMAIL PROTECTED] wrote: None of this version hace support for last generation iPods since Apple has include a security control on the new iPods, so they can't been used from other software rather than iTunes. On Tue, Jul 8, 2008 at 12:08 PM, Janne Jokitalo [EMAIL PROTECTED] wrote: On Tue, Jul 08, 2008 at 10:28:39AM -0400, Bill Yerazunis wrote: snip So, please build out a new gtkpod and libgpod package for those of us who have the new(er) Apple iPods Hardy has version 0.99.12-1, Debian sid is 0.99.12-2. Does that one suffice? If not, it would be good to know which version does what you mentioned. It isn't obvious even from the project's homepage. Only that the latest stable version is the one mentioned above. -- Jaska -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: universe-contributors
On Sun, Jul 6, 2008 at 8:05 AM, Stefan Potyra [EMAIL PROTECTED] wrote: Hi, b) to actually hand out additional privileges, ranging from being able to triage bugs to being able to upload a set of packages (as soon as LP can do this). IIRC there were some good ideas back during the initial discussion about universe-contributors, might eventually make sense to revisit these. And open a galaxy repository, and change u-u-c to Masters of the Galaxy or something like that? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: About forwarding bugs and patches to Debian and documenting your changes
On Tue, 2008-06-17 at 22:10 -0400, Scott Kitterman wrote: On Tuesday 17 June 2008 21:11, Nicolas Valcarcel wrote: Hi, On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED] There's a wiki page on https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines about basically the same thing (it documents the changes in the patches, which is not suitable if the changes are made directly in the source, without using a patch system), but that policy doesn't seem to be in widespread use, unfortunately. I didn't knew about that page and i'm sure a lot of people doesn't know also, are you interested on helping me dive into wiki pages to write a complete document with all of them and then try to spread the word about it/them? Did someone want to help? We have https://wiki.ubuntu.com/ContributingToDebian that would presumably be the right place to start. Yes i knew this one, but there are more things to keep in mind, like keeping track of links and evidence. Also, we have this document but not everyone knows/follows it. Scott K -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: About forwarding bugs and patches to Debian and documenting your changes
On Wed, 2008-06-18 at 01:25 -0700, Bryce Harrington wrote: On Wed, Jun 18, 2008 at 09:44:56AM +0200, Lucas Nussbaum wrote: For example, instead of: + * debian/control: add missing libxext-dev build-dependency (fixes FTBFS). You could write: + * debian/control: add missing libxext-dev b-dep. See +http://wiki.ubuntu.com/Changes/libext-dev +Should be merged in Debian. For this last line, something terser would be preferrable and easier to synthetically parse (i.e. something that won't be likely to word-wrap). Yes, but we lucas isn't saying Do it that way just giving some recommendations to get into a policy or good practices document so the relations between ubuntu and any upstream will improve. Bryce I'm working on a wiki page about good practices [1]. Feel free to add whatever you want, but keep in mind that this must be a general upstream collaboration guide, not just debian. 1. https://wiki.ubuntu.com/GoodPractices -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: About forwarding bugs and patches to Debian and documenting your changes
Thanks for the examples, now i'm clearer on what you meant. I also think this will we great, but to have a wiki page for every package and to edit it with every change it's not the best to do IMHO. On the other hand we can open a bug for the changes and explain everything there and just include the (LP: #X) part to it. On Wed, 2008-06-18 at 09:44 +0200, Lucas Nussbaum wrote: On 17/06/08 at 20:11 -0500, Nicolas Valcarcel wrote: On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED] Secondly, you generally could improve a lot at documenting your changes. If you put more effort on properly documenting what you change in your packages, it would allow Debian developers to understand why you made a specific change, and they would be a lot more likely to merge the change in the Debian package (which means less work for you during the next merge). If a DD can't figure out why you made a change, it's likely that he won't ask you, and will just ignore the change. Can you please give an example of that i don't think i'm fully understanding your point (not a real example, just whatever comes to your mind first) Sure. Here are a few examples: + * Merge from debian unstable, remaining changes: +- usbmount creates /var/run/usbmount if it does not exist. If you said that this breaks the package on systems where /var/run is emptied at boot time (which is FHS-compliant), it would probably help. (also, you might want to push that change to a release goal in Debian for lenny+1, that would allow to fix all those packages at the same time). + * debian/control: add missing libxext-dev build-dependency (fixes FTBFS). If you said that this was going to be needed in Debian with libx11 2:1.1.4-2, I'm sure more maintainers who have merged it. + * debian/rules: Set ARCH_FLAG (where the diff in debian/rules is:) -ARCHFLAG = +ARCHFLAG = -B $(shell dpkg-architecture -qDEB_BUILD_ARCH) Everybody can see that you set ARCHFLAG (not ARCH_FLAG, btw). Why was that necessary? Which problem is it fixing? Is Debian affected as well? + * debian/patches/03_missing_includes.dpatch: Added. Fixes FTBFS Under which conditions does it FTBFS? Is Debian affected as well, or likely to become affected as well? + * Merge from debian unstable, remaining changes: +- Use dpatch +- debian/patches: + * kubuntu_01_branch_patch.dpatch + * kubuntu_02_installer_mode.dpatch + * kubuntu_03_fix_desktop_file.dpatch + * kubuntu_04_libparted17.dpatch + * kubuntu_05_german.dpatch + * kubuntu_06_english.dpatch + * kubuntu_07_root_is_sudo.dpatch $ grep ^+## DP: xx-3ubuntu1.patch +## DP: No description. +## DP: No description. +## DP: No description. +## DP: No description. +## DP: Fix mistakes in German translation, thanks to Christian A. Reiter. +## DP: Fix mistakes in English strings. +## DP: Replace references to root and fix some sentence in the Catalan translation. Patches without description It would be great if, in addition to listing the remaining changes in the last changelog entry, you could also list for each change: - the URL of the corresponding Ubuntu bug (if any) - the URL of the corresponding upstream bug (if any) - the URL of the corresponding Debian bug (if any) - a summary of the changes (pointing to URLs explaining the context of the change, if possible/needed) - whether the change is Ubuntu-specific, or should be merged upstream or in Debian (with a rationale if is Ubuntu-specific) We already work like this, we use to use (LP: #) which means Launchpad Bug report # as DD's use (Closes: #), so there is no much more to do for LP Bugs (Ubuntu ones). For the upstream and debian bugs we link them on the LP Bug report, so if the DD is interested on following links he can from them, with this i'm not saying is the best to do and rejecting your suggestions, just noticing it if you didn't know it, maybe is not as good as it could and we can do it better, so if you have anything to add please do it. Linking to bugs is a good thing, but many changes are done without any bug in launchpad (or the bug wasn't linked in the changelog). So answering the But why are you making this change? Should I merge it in the Debian package? question requires a lot of effort. I'm not asking you to write a ten-line rationale for the patch. Often, 1 to 3 lines should be enough. And you could link to a wiki page to provide a more detailed explanation of the problem. For example, instead of: + * debian/control: add missing libxext-dev build-dependency (fixes FTBFS). You could write: + * debian/control: add missing libxext-dev b-dep. See +http://wiki.ubuntu.com/Changes/libext-dev +Should be merged in Debian. And then, explain on the wiki that Ubuntu ships a more recent libx11, where the dep on libext-dev was removed, so many packages
Re: About forwarding bugs and patches to Debian and documenting your changes
On Wed, 2008-06-18 at 09:13 -0700, Jordan Mantha wrote: This of course assumes the person writing the changelog entry actually knows the answer to those questions. As you say, it requires a lot of effort on the part of the DD. I think it probably takes at least the same if not more effort on the part of the person writing the changelog. A fair amount of the time I don't think merger's really know why a change is needed or if it applies to Debian or not. Yes, but mergers don't change anything, just apply some changes, we are talking about changing things, and if you don't know these answers when you make a change, then you are not able to do changes to ubuntu packages. About the applies to debian thing i'm with you, it's hard to know if you don't have a debian system on hands, but if you know that it applies also to debian, please write it there. -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: About forwarding bugs and patches to Debian and documenting your changes
On Wed, 2008-06-18 at 18:48 +0200, Lucas Nussbaum wrote: On 18/06/08 at 10:12 -0500, Nicolas Valcarcel wrote: Thanks for the examples, now i'm clearer on what you meant. I also think this will we great, but to have a wiki page for every package and to edit it with every change it's not the best to do IMHO. On the other hand we can open a bug for the changes and explain everything there and just include the (LP: #X) part to it. I didn't mean that there should be one wiki page per package. Only that there should be one wiki page (or one section on the same wiki page) for each class of change. In the case of libext-dev, there was probably at least 20 packages affected by that change, where the exact same patch (add libext-dev to build-deps) was needed. Well, i still prefer to open a bug report instead of using a wiki page, it's easier and better for comments/discussion. I have open a wiki page [1] with some points about this conversation. 1. https://wiki.ubuntu.com/GoodPractices -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: About forwarding bugs and patches to Debian and documenting your changes
Hi, On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED] wrote: Hi, As you might have read in [1], I worked on exporting more info about packages in Ubuntu to the Debian infrastructure, specifically the Debian PTS[2] and the Debian Developer Packages Overview[3]. [1] http://www.lucas-nussbaum.net/blog/?p=295 [2] http://packages.qa.debian.org/d/dpkg.html [3] http://qa.debian.org/[EMAIL PROTECTED]ubuntu=1 However, I'd like to use that opportunity to discuss a few points: I know you are over-busy, etc., and that your #1 priority can't be to push changes back to Debian. But those changes should not replace submitting bugs to the Debian BTS, like the patches on patches.u.c should not replace submitting patches to the BTS. Most Debian Developers will probably only rarely have a look at the bugs in LP. If I hear Ubuntu Developers saying but there was no need to report it to Debian, you already should have known about it since there was a link on PTS/DDPO!, I will strongly regret pushing that change. This is true, it doesn't take a long time to report a Bug tu debian, and we can't be lazy and say the patch is there, if the DD want's it, he/she can download it from there since we want our changes in there for easier maintainment of our packages, DD's only care about their Bugs, not ours. Secondly, you generally could improve a lot at documenting your changes. If you put more effort on properly documenting what you change in your packages, it would allow Debian developers to understand why you made a specific change, and they would be a lot more likely to merge the change in the Debian package (which means less work for you during the next merge). If a DD can't figure out why you made a change, it's likely that he won't ask you, and will just ignore the change. Can you please give an example of that i don't think i'm fully understanding your point (not a real example, just whatever comes to your mind first) It would be great if, in addition to listing the remaining changes in the last changelog entry, you could also list for each change: - the URL of the corresponding Ubuntu bug (if any) - the URL of the corresponding upstream bug (if any) - the URL of the corresponding Debian bug (if any) - a summary of the changes (pointing to URLs explaining the context of the change, if possible/needed) - whether the change is Ubuntu-specific, or should be merged upstream or in Debian (with a rationale if it's Ubuntu-specific) We already work like this, we use to use (LP: #) which means Launchpad Bug report # as DD's use (Closes: #), so there is no much more to do for LP Bugs (Ubuntu ones). For the upstream and debian bugs we link them on the LP Bug report, so if the DD is interested on following links he can from them, with this i'm not saying is the best to do and rejecting your suggestions, just noticing it if you didn't know it, maybe is not as good as it could and we can do it better, so if you have anything to add please do it. There's a wiki page on https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines about basically the same thing (it documents the changes in the patches, which is not suitable if the changes are made directly in the source, without using a patch system), but that policy doesn't seem to be in widespread use, unfortunately. I didn't knew about that page and i'm sure a lot of people doesn't know also, are you interested on helping me dive into wiki pages to write a complete document with all of them and then try to spread the word about it/them? Did someone want to help? Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIV5dZ2hliNwI7P08RAmtUAJoC7JrcZ1xZwsQMOx5tKgYFYfndRQCdHhg2 ZI7NB+Hh5rbVCL+VoIrEtDI= =Bft/ -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 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: contributions
I think i haven't explain myself as i should. The thing was that: developer A uploaded a package on the past release circle, then a merge was publiched on MoM, a contributor take the merge, work on it and upload the debdiff to launchpad reporting the bug as it needs to be, the developer A commented on that bug report, so we can be sure that he knows about the contributor working on that merge, then developer B work on that merge and upload it by himself without noticing the bug report and contributor's work. That, on the side of the contributor, being a new one, is a really bad thing because he wanted to be his work on the repos, but not only it isn't there, it has been done and uploaded by someone else. DaD's comments were a good feature to avoid such things, if contributor left a comment in there, the developer B could see it and work on another merge. On Tue, May 13, 2008 at 2:43 AM, Mathias Gug [EMAIL PROTECTED] wrote: Hi Nicolas, On Mon, May 12, 2008 at 07:51:47PM -0500, Nicolas Valcarcel wrote: Hi, Since hardy i have notice that some times contributions are not taking into account, mostly on merges. For MOTUs and core devels is not needed to file a bug since it's only needed to upload the package, but some times, a contributor, which need to file a bug, upload his debdiff and ask for sponsorship, make the work for nothing, becase one developer (no one in special) work on that merge and upload it. I think is not fair, and discourage for new contributor, so i think it lack for a common process where this things doesn't happen. Are you referring to the fact that the package doesn't show up in the contributor package list ? Usually the contributor is credited in the Changelog entry. -- Mathias Gug Ubuntu Developer http://www.ubuntu.com -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: contributions
I think i haven't explain myself as i should. The thing was that: developer A uploaded a package on the past release circle, then a merge was publiched on MoM, a contributor take the merge, work on it and upload the debdiff to launchpad reporting the bug as it needs to be, the developer A commented on that bug report, so we can be sure that he knows about the contributor working on that merge, then developer B work on that merge and upload it by himself without noticing the bug report and contributor's work. That, on the side of the contributor, being a new one, is a really bad thing because he wanted to be his work on the repos, but not only it isn't there, it has been done and uploaded by someone else. DaD's comments were a good feature to avoid such things, if contributor left a comment in there, the developer B could see it and work on another merge. On Tue, May 13, 2008 at 8:18 AM, Scott Kitterman [EMAIL PROTECTED] wrote: On Monday 12 May 2008 20:51, Nicolas Valcarcel wrote: Hi, Since hardy i have notice that some times contributions are not taking into account, mostly on merges. For MOTUs and core devels is not needed to file a bug since it's only needed to upload the package, but some times, a contributor, which need to file a bug, upload his debdiff and ask for sponsorship, make the work for nothing, becase one developer (no one in special) work on that merge and upload it. I think is not fair, and discourage for new contributor, so i think it lack for a common process where this things doesn't happen. I appreciate your problem. I remember such things happening in the past too. It's unfortunate when such things happen, but I don't know what can be done to prevent it completely. MOTU are supposed to check bugs when they do a merge. Ideally we'll have the new merged (pun intended) MoM and DaD up soon so there is one place to go for merge information that can include comments about what people are working on. That should help too. From our IRC discussion, I gather you had discussed the merge with the previous uploader, but that the MOTU that uploaded his own merge (apparently) did not. While there is no rule requiring people to check with the last uploader, I still think it is generally a good idea (particularly early in the release cycle when there is no great rush to get merges uploaded). That might have avoided the problem in this case. I think we have sufficient process in place (MOTU should check bugs before uploading a merge to see if there are other fixes that should be included) or coming (single source of merge information with comments) to minimize this problem. I don't think we'll ever eliminate it completely. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
contributions
Hi, Since hardy i have notice that some times contributions are not taking into account, mostly on merges. For MOTUs and core devels is not needed to file a bug since it's only needed to upload the package, but some times, a contributor, which need to file a bug, upload his debdiff and ask for sponsorship, make the work for nothing, becase one developer (no one in special) work on that merge and upload it. I think is not fair, and discourage for new contributor, so i think it lack for a common process where this things doesn't happen. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: RFC: Sponsor Day
On Sat, 2008-05-10 at 22:00 +0200, Stefan Potyra wrote: do you mean that the ubuntu-universe-sponsors queue is growing (as I've seen not too many uploads to revu recently)? Yes, that's what i meant. -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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
RFC: Sponsor Day
Hi, Last week we have had Ubuntu Open Week, conference which makes a lot of people get involved in ubuntu development, starting, as i think everyone has, on universe. No one of them as access to the servers, so everyone needs sponsorship, and the queue is growing and growing. The problem with this is that new contributor aren't seeing their work uploaded, and that can be frustrating for them, at least for the first packages it always is. So what i'm purposing is, as we have REVU days before FF, i purpose to have Sponsor Days before DF, so we can have a lot of contributors work reviewed and sponsored, si they get motivated and more involved on the project. -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: NX 3.2.0 packages
Hi, On Thu, 2008-04-17 at 16:14 -0300, Marcelo Boveto Shima wrote: Hello, Is there a possibility that FreeNX + NX packages to get accepted into universe? Yes, your goal must be Ibex, since we are long past FF. You should upload it to REVU: https://wiki.ubuntu.com/MOTU/Packages/REVU The packages are on my ppa: https://launchpad.net/~marceloshima/+archive Pros and Cons: - NX is a fork of Xorg 6.9. It's duplicate source code. - There is no security problem because only 3 libs (libX11, libXext and libXrender) are shipped on the package and they can have the security patches ported from dapper. I remember it was a problem because NX was a fork of XFree86. - This libs can be renamed to libXXX-nx. So will not conflict with the Xorg ones. - libXcomp, NXProxy and qtnx (NX client) are already in. We need the server to make the client useful. - Freenx is shell scripts. But we have Freenx-NG that is python. This was another problem when it was proposed to get in some years ago. Regards Marcelo Shima -- aka nxvl Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE 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: MOTU Council Election
congratulations to all of you! i know you will make a wonderful job! On 1/31/08, Sarah Hobbs [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To persia and nixternal - well done! You deserve it! Hobbsee Daniel Holbach wrote: On Mi, 2008-01-23 at 14:24 +, Daniel Holbach wrote: in ten hours from now the polls for the MC election will be opened. If you're an Ubuntu developer, please vote at: https://launchpad.net/~ubuntu-dev/+poll/mc-hobbsee-0801 https://launchpad.net/~ubuntu-dev/+poll/mc-nixternal-0801 https://launchpad.net/~ubuntu-dev/+poll/mc-persia-0801 Just a reminder: You still have 33 hours left. Have a nice day, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHoTUv7/o1b30rzoURAvNnAKDj5vojuVthqyqHRG5BUayEnuQqfgCg2LQF +8VVikQ04dtn8qI8m8uw9Ek= =lxAv -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 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Problem with Transmission package
Can you please resend the output in English? On Tue, 2008-01-29 at 14:38 +0100, Bjorn Heesakkers wrote: Hello Maintainers, I have a problem while installing transmission: [EMAIL PROTECTED]:/home/bjorn# apt-get install transmission Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd Reading state information... Klaar Sommige pakketten konden niet geïnstalleerd worden. Dit kan betekenen dat u een onmogelijke situatie gevraagd hebt of dat u de 'unstable'-distributie gebruikt en sommige benodigde pakketten nog vastzitten in 'incoming'. Aangezien u slechts een enkele opdracht gegeven hebt is het zeer waarschijnlijk dat het pakket gewoon niet installeerbaar is. U kunt dan best een foutrapport indienen voor dit pakket. De volgende informatie helpt u mogelijk verder: De volgende pakketten hebben niet-voldane vereisten: transmission: Vereisten: transmission-cli (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden Vereisten: transmission-gtk (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden E: Niet-werkende pakketten: Seems like the dependencies are broken. Thanks, Bjorn. -- aka nxvl Peruvian LoCo Team Key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5 gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5 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: Problem with Transmission package
Not present on any of my gutsy or hardy pbuilder's chroot environments, did you apt-get update before trying to install? On Tue, 2008-01-29 at 14:38 +0100, Bjorn Heesakkers wrote: Hello Maintainers, I have a problem while installing transmission: [EMAIL PROTECTED]:/home/bjorn# apt-get install transmission Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd Reading state information... Klaar Sommige pakketten konden niet geïnstalleerd worden. Dit kan betekenen dat u een onmogelijke situatie gevraagd hebt of dat u de 'unstable'-distributie gebruikt en sommige benodigde pakketten nog vastzitten in 'incoming'. Aangezien u slechts een enkele opdracht gegeven hebt is het zeer waarschijnlijk dat het pakket gewoon niet installeerbaar is. U kunt dan best een foutrapport indienen voor dit pakket. De volgende informatie helpt u mogelijk verder: De volgende pakketten hebben niet-voldane vereisten: transmission: Vereisten: transmission-cli (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden Vereisten: transmission-gtk (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden E: Niet-werkende pakketten: Seems like the dependencies are broken. Thanks, Bjorn. -- aka nxvl Peruvian LoCo Team Key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5 gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5 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
[Fwd: Re: Problem with Transmission package]
-- aka nxvl Peruvian LoCo Team Key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5 gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5 ---BeginMessage--- Hey, Op Tuesday 29 January 2008 16:30:41 schreef u: Can you please resend the output in English ? [EMAIL PROTECTED]:/home/bjorn# apt-get install transmission Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: transmission: Depends: transmission-cli (= 0.93.dfsg-2~gutsy1) but it is not going to be installed Depends: transmission-gtk (= 0.93.dfsg-2~gutsy1) but it is not going to be installed E: Broken packages [EMAIL PROTECTED]:/home/bjorn# On Tue, 2008-01-29 at 14:38 +0100, Bjorn Heesakkers wrote: Hello Maintainers, I have a problem while installing transmission: [EMAIL PROTECTED]:/home/bjorn# apt-get install transmission Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd Reading state information... Klaar Sommige pakketten konden niet geïnstalleerd worden. Dit kan betekenen dat u een onmogelijke situatie gevraagd hebt of dat u de 'unstable'-distributie gebruikt en sommige benodigde pakketten nog vastzitten in 'incoming'. Aangezien u slechts een enkele opdracht gegeven hebt is het zeer waarschijnlijk dat het pakket gewoon niet installeerbaar is. U kunt dan best een foutrapport indienen voor dit pakket. De volgende informatie helpt u mogelijk verder: De volgende pakketten hebben niet-voldane vereisten: transmission: Vereisten: transmission-cli (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden Vereisten: transmission-gtk (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden E: Niet-werkende pakketten: Seems like the dependencies are broken. Thanks, Bjorn. Greets, Bjorn. ---End Message--- 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: Problem with Transmission package
Are you using hardy or gutsy? On Tue, 2008-01-29 at 19:02 +0100, Bjorn Heesakkers wrote: Hello, Op Tuesday 29 January 2008 18:44:43 schreef u: Not present on any of my gutsy or hardy pbuilder's chroot environments, did you apt-get update before trying to install? I ran apt-get clean;apt-get update;apt-get upgrade -y before trying to install transmission. I can give you a copy of my sources.list tomorrow, I'm not at the office right now so I'm not able to access my computer. I will send you my sources.list tomorrow. On Tue, 2008-01-29 at 14:38 +0100, Bjorn Heesakkers wrote: Hello Maintainers, I have a problem while installing transmission: [EMAIL PROTECTED]:/home/bjorn# apt-get install transmission Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd Reading state information... Klaar Sommige pakketten konden niet geïnstalleerd worden. Dit kan betekenen dat u een onmogelijke situatie gevraagd hebt of dat u de 'unstable'-distributie gebruikt en sommige benodigde pakketten nog vastzitten in 'incoming'. Aangezien u slechts een enkele opdracht gegeven hebt is het zeer waarschijnlijk dat het pakket gewoon niet installeerbaar is. U kunt dan best een foutrapport indienen voor dit pakket. De volgende informatie helpt u mogelijk verder: De volgende pakketten hebben niet-voldane vereisten: transmission: Vereisten: transmission-cli (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden Vereisten: transmission-gtk (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden E: Niet-werkende pakketten: Seems like the dependencies are broken. Thanks, Bjorn. -- aka nxvl Peruvian LoCo Team Key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5 gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5 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: Problem with Transmission package
Nop, it doesn't matter, but as seen on the dependencies i think it something must be missing on your sources.list, because this package exist on the repos, maybe in the mirror you have there is no one, but we will see it with your sources.list P.S: please Reply to All instead of just Reply so all it's sent to the motu list. On Tue, 2008-01-29 at 19:20 +0100, Bjorn Heesakkers wrote: Op Tuesday 29 January 2008 19:10:10 schreef u: Are you using hardy or gutsy? Ubuntu Gutsy. I have to note that I did a apt-get install kubuntu-desktop so I use KDE instead of Gnome. I don't think that would matter but you never know. On Tue, 2008-01-29 at 19:02 +0100, Bjorn Heesakkers wrote: Hello, Op Tuesday 29 January 2008 18:44:43 schreef u: Not present on any of my gutsy or hardy pbuilder's chroot environments, did you apt-get update before trying to install? I ran apt-get clean;apt-get update;apt-get upgrade -y before trying to install transmission. I can give you a copy of my sources.list tomorrow, I'm not at the office right now so I'm not able to access my computer. I will send you my sources.list tomorrow. On Tue, 2008-01-29 at 14:38 +0100, Bjorn Heesakkers wrote: Hello Maintainers, I have a problem while installing transmission: [EMAIL PROTECTED]:/home/bjorn# apt-get install transmission Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd Reading state information... Klaar Sommige pakketten konden niet geïnstalleerd worden. Dit kan betekenen dat u een onmogelijke situatie gevraagd hebt of dat u de 'unstable'-distributie gebruikt en sommige benodigde pakketten nog vastzitten in 'incoming'. Aangezien u slechts een enkele opdracht gegeven hebt is het zeer waarschijnlijk dat het pakket gewoon niet installeerbaar is. U kunt dan best een foutrapport indienen voor dit pakket. De volgende informatie helpt u mogelijk verder: De volgende pakketten hebben niet-voldane vereisten: transmission: Vereisten: transmission-cli (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden Vereisten: transmission-gtk (= 0.93.dfsg-2~gutsy1) maar het zal niet geïnstalleerd worden E: Niet-werkende pakketten: Seems like the dependencies are broken. Thanks, Bjorn. -- aka nxvl Peruvian LoCo Team Key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5 gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5 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: Security Team IRC Meeting 2007-01-30 20:00 UTC
WoW! nice work, i everything goes good i will be tomorrow too. On Tue, 2008-01-29 at 20:15 +0100, Emanuele Gentili wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 see you tomorrow. Cheers, emgent Kees Cook ha scritto: Given all the updates that the MOTU-SWAT[1] team have been doing, the testing I'd like to help coordinate for hardened compiler options[2], the SELinux development work[3], new kernel features[4], and new projects that propose formally organizing a pentesting sub-team, there is clearly enough things going on specific to Ubuntu Security that I'd like to hold an official Security Team meeting on Wed 2007-01-30 at 20:00 UTC in #ubuntu-meeting. I realize this is rather short notice, but I'd like to at least generate a roadmap and TODO list for future meetings. :) -Kees [1] https://launchpad.net/~motu-swat/+members [2] https://lists.ubuntu.com/archives/ubuntu-devel/2008-January/024958.html [3] https://lists.ubuntu.com/archives/ubuntu-hardened/2007-November/000230.html [4] http://www.outflux.net/blog/archives/2008/01/15/full-aslr-in-hardy/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBR597Q4dIcUD/0QBsAQJQqwf8DtGh/fB24NTQXOCJE1aVMtO86QDvNAd5 aKP5GkOO+YqqWZ4pGcMeH53HHgOmcU1t9xKG426fBhFUtOdWMBc+8mS46Edr+9G9 k7/i4lqIuTrsAOJ2ZoP2axjbiwQHVBztIJl22X9UyH1He8f0rMXTtwwqi9oTFn47 fF1UolNcQVsPaRKMAJxrQHsMdo7xhch8eqDkYNt7uAvu/pLgsO5Pf3GfZgQG9bRL Zil9gZaf/yLqqzs7r6MC5hDnMqi4Ki3ZaE9WlgFM7+DNfimFELQIywTNu4qruBD/ LU9vT2dxKNGidnS/GiMUsQNrHds5Zbhc2YCS/uALd03JeKOJdhziyw== =xOZv -END PGP SIGNATURE- -- aka nxvl Peruvian LoCo Team Key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5 gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5 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: Hardy message when install program
can you post a copy of your sources.list? On 1/30/08, Jumpod Plekhongthu [EMAIL PROTECTED] wrote: All, I don't know about this message. it happen alway after,I update my server to hardy ldconfig deferred processing now taking place /sbin/ldconfig.real: /lib/librdp.so is not an ELF file - it has the wrong magic bytes at the start. /sbin/ldconfig.real: /lib/libscp.so is not an ELF file - it has the wrong magic bytes at the start. /sbin/ldconfig.real: /lib/libvnc.so is not an ELF file - it has the wrong magic bytes at the start. /sbin/ldconfig.real: /lib/libxrdp.so is not an ELF file - it has the wrong magic bytes at the start. /sbin/ldconfig.real: /lib/libxup.so is not an ELF file - it has the wrong magic bytes at the start. Could someone tell me what's happen with my server?and how to do? Best Regards. Jumpod Plekhongthu TDC Celestica Thailand EXT 2865 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Failing to unpatch
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 -- aka nxvl Peruvian LoCo Team Key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5 gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5 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: flashplugin-nonfree: problems with Ubuntu Gutsy Gibbon
Did you apt-get update before installing the package? On Wed, 2007-12-26 at 21:06 +0100, Pierluigi Falorni wrote: All, the installation of the subjected package terminate with an error condition. Follow the stdout: [EMAIL PROTECTED]:~$ sudo apt-get install --reinstall flashplugin-nonfree Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: konqueror-nsplugins msttcorefonts ttf-xfree86-nonfree xfs The following NEW packages will be installed: flashplugin-nonfree 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/18.1kB of archives. After unpacking 160kB of additional disk space will be used. Preconfiguring packages ... Selecting previously deselected package flashplugin-nonfree. (Reading database ... 95766 files and directories currently installed.) Unpacking flashplugin-nonfree (from .../flashplugin-nonfree_9.0.48.0.2 +really0ubuntu12_i386.deb) ... Setting up flashplugin-nonfree (9.0.48.0.2 +really0ubuntu12) ... Downloading... --20:55:24-- http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz = `./install_flash_player_9_linux.tar.gz' Resolving fpdownload.macromedia.com... 84.53.170.70 Connecting to fpdownload.macromedia.com|84.53.170.70|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3,036,127 (2.9M) [application/x-gzip] 0K .. .. .. .. .. 1% 128.76 KB/s 50K .. .. .. .. .. 3% 342.09 KB/s 100K .. .. .. .. .. 5% 422.83 KB/s 150K .. .. .. .. .. 6% 598.52 KB/s 200K .. .. .. .. .. 8% 499.91 KB/s 250K .. .. .. .. .. 10% 572.41 KB/s 300K .. .. .. .. .. 11% 270.29 KB/s 350K .. .. .. .. .. 13% 89.62 KB/s 400K .. .. .. .. .. 15% 139.64 KB/s 450K .. .. .. .. .. 16% 337.04 KB/s 500K .. .. .. .. .. 18% 415.45 KB/s 550K .. .. .. .. .. 20% 410.29 KB/s 600K .. .. .. .. .. 21% 448.18 KB/s 650K .. .. .. .. .. 23% 441.45 KB/s 700K .. .. .. .. .. 25% 358.35 KB/s 750K .. .. .. .. .. 26% 554.04 KB/s 800K .. .. .. .. .. 28% 383.29 KB/s 850K .. .. .. .. .. 30% 436.78 KB/s 900K .. .. .. .. .. 32% 438.38 KB/s 950K .. .. .. .. .. 33% 424.35 KB/s 1000K .. .. .. .. .. 35% 589.13 KB/s 1050K .. .. .. .. .. 37% 462.40 KB/s 1100K .. .. .. .. .. 38% 415.82 KB/s 1150K .. .. .. .. .. 40% 462.17 KB/s 1200K .. .. .. .. .. 42% 484.36 KB/s 1250K .. .. .. .. .. 43% 560.05 KB/s 1300K .. .. .. .. .. 45% 487.81 KB/s 1350K .. .. .. .. .. 47% 477.58 KB/s 1400K .. .. .. .. .. 48% 534.08 KB/s 1450K .. .. .. .. .. 50% 514.07 KB/s 1500K .. .. .. .. .. 52% 482.54 KB/s 1550K .. .. .. .. .. 53% 512.42 KB/s 1600K .. .. .. .. .. 55% 527.69 KB/s 1650K .. .. .. .. .. 57% 541.15 KB/s
Re: RFC: https://wiki.ubuntu.com/UbuntuDevelopment/Merging (Was: Re: WANTED: Merging Recipe!)
I think that would be a great feature, since it's easier to look only at one site, and not to check in diferent places for solve the bugs, and if we had a software that in one or other way reports the needs of merging i don't think it will be to difficult to add a feature that reports it to LP aswell, but with which team should we coordinate? MoM team (i don't know who are the contacts for it) o with the LP team? On Nov 22, 2007 8:48 AM, Morten Kjeldgaard [EMAIL PROTECTED] wrote: There is also http://dad.dunnewind.net/universe.php which, while unofficial, has the advantage of having comments so people can give status of what's going on. Which actually illustrates my point: there's dad and mom and revu and wiki and launchpad and a number of other ad hoc services only known to the especially initiated developers and some which duplicate functions of others. Even though I am not a great fan of LP, it would make sense to transfer the task of at least some of the ad-hoc sites to there. For example, when generating the list of packages that need merging, it should *in principle* be possible to report these *automatically* as Please-merge bugs in LP, so the workflow could pivot around that. That would get rid of mom and dad for starters. I realize that the workflow has probably evolved slowly along with the MOTU population, but take this as a fresh look at the process. It needs to be revised IMHO. Cheers, Morten -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- aka nxvl Yo uso Software Libre, y tu? -- 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
I like the idea of separating mentoring on 2 stages, and i find nice the idea of not sponsoring the mentees patches. I know the MOTUs will know when they are comfortable with the upload, but in the other hand it's common to think he has made exactly what i tell him to do, so it must be fine or to test and fine a little problem, tell the mentee to change it, and then assume he has made it without making another mistake, so, if my vote count (i don't know how it works for non-MOTUs) i will say to apply the 3 changes. On Nov 15, 2007 10:54 PM, Brandon Holtsclaw [EMAIL PROTECTED] wrote: I would additionally like to propose that assigned mentors not sponsor changes by their mentees. This will better integrate mentees with the MOTU community, reduce montor worloak, and expose hopefuls to more diverse inputs from more MOTUs. [..] Hm... I like the goal, but I don't see particular harm being done if a mentor sponsors a mentee, as long as the goal is actually still met. +1 I live the idea of Stage 1 and Stage 2 separation and am willing to shift me efforts to the Stage 1 needs of mentees ( I have no current mentee's ) But not sponsoring a mentee's patches I think ads just a little too much red tape into the program for my taste, I see no problem with it as MOTU should know when they are comfortable uploading a given patch/change , that is of course why they were given upload privileges in the first place. I agree that a Mentor should work to integrate the mentee into the MOTU Community. -- Brandon Holtsclaw [EMAIL PROTECTED] http://www.imbrandon.com -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- aka nxvl Yo uso Software Libre, y tu? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: MOTU QA session!
Yesterday i have work until late and i couldn't wake up for the QA :( but now i can read the logs :D next time i will try to be there :D On Nov 14, 2007 6:13 AM, Daniel Holbach [EMAIL PROTECTED] wrote: Hello everybody, get ready for another MOTU QA session on Friday, November 16th, 12:00 UTC. We'll meet in #ubuntu-classroom on irc.freenode.net and * answer all your questions around MOTU and Ubuntu Development processes * answer all packaging questions * have a good time If you're running into problems, make notes and bring them to the session and we'll get you back on track. Have a nice day, Daniel -- Ubuntu-motu-mentors mailing list [EMAIL PROTECTED] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu-mentors -- aka nxvl Yo uso Software Libre, y tu? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
My Apologizes
I need to say sorry for the last week i've been a little away of IRC, LP and Ubuntu contributing, i've had 3 long and hard weeks at work with lots of forensix and EHs and final works on the university which has apart me a lot of the ubuntu project, so i gave my apologizes to all i hope this days are lighter to focus my efforts on contributing :D On other news, last Saturday the Peruvian LoCo team participate on a local conference with a stand where we offer Ubuntu cd's and make some demostrations of a running ubuntu, and we have had LOTS of people, there where always between 10 and 20 different people asking for help, asking what is ubuntu, and we see a lot of interest on them. Yo can see some pictures here - http://picasaweb.google.com/xander21c/UbuntuPeruEnElFesoli -- aka nxvl Yo uso Software Libre, y tu? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Sitting out for Hardy
It makes me very sad your mail, i know you for a very short time, but i know you are a very good element on ubuntu. But this things happen sometimes, and if it's for your goodness it's fine i hope you involve back at any point of hardy development or for the next release :D On Sat, 2007-10-27 at 13:48 -0400, Scott Kitterman wrote: Most of you probably already know this from IRC, but ... I don't plan on much involvement during the Hardy developement cycle. MOTU has gotten to stressful for me for the stress to be worth the enjoyment I get out of it. There are a number of reasons that I hope that by sharing, I can hope make things better for everyone. 1. It seems like we've quickly evolved from the idea of people are expected to generally know what they are doing, think things through, and quickly fix mistakes when they are made to the idea that it's not wrong to do anything that isn't explicitly prohibited in some documentation. This rules oriented mindset makes it harder to get stuff done, harder to get mistakes corrected, and is, IMO, either the effect or a cause of an increasing level of defensiveness and reaction in the community. I think it works better to expect that people won't do things they don't know enough about (ask first) and fix stuff when they mess up. Having to have a written rule that SRUs should be tested before uploading is bizarre. 2. Both our processes and our tools (I'm thinking LP here) are evolving in ways that from my perspective make work harder, not easier. Tools and processes should support work getting done and I think things are not evolving for the better. 3. The seeming limitless tolerance for people to come back again and again with disruptive, incorrect advice, bugs, proposed uploads that has at times been an effective denial of service attack on MOTU. I can't work in this environment. People need time to learn, but there's a point beyond which they need to learn not to do damage and cause trouble for other people. During Hardy, I will not be reviewing sponsored uploads (I've subscribed from the motu-reviewers list on tauware.de and deactivated myself from UUS). I won't take on any 'management' roles like motu-uvf. I will still mind the packages I've been minding. I will still hang out on IRC (unless the atmosphere just gets too stressful for me) and help answer questions and be part of the community. I will also work on helping (not leading or doing) with things that can improve the problems that have led me to sit this one out. Scott K -- aka nxvl key fingerprint: E140 4CC7 5E3C B6B4 DCA7 F6FD D22E 2FB4 A9BA 6877 gpg --keyserver keyserver.ubuntu.com --recv-keys A9BA6877 Yo uso Software Libre y tu? 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: Joining the team
On Tue, 2007-10-23 at 16:43 -0700, Beth Aviv wrote: Hey, Hello! I guess I fall into the I know nothing about programming, but would like to help. I've been running with Ubuntu since April... a couple days after Feisty was released and have had a blast running it. I've been running Gutsy from tribe 4 and even though I've had issues, I always found it fun to work them out and learn from it. I've always learned something everything something went amiss. Nice! It's always nice to learn something. And there are lot of people helping and knowing nothing about programming, you can Triage Bugs or do some translations. I know there are problems, bugs, etc... and I would like to help out anyway I can. I try to be active on the forums when I'm able to help. It feels nice to know that you can help people fix their problems, too. Yes they are, and they need our time. :D I am learning a bit about the CLI and programming... I've even picked up a Python book to read when I'm bored at work. Let me know where I can start =) Well i think i have. Thanks, Beth Goldhammer -- aka nxvl key fingerprint: E140 4CC7 5E3C B6B4 DCA7 F6FD D22E 2FB4 A9BA 6877 gpg --keyserver keyserver.ubuntu.com --recv-keys A9BA6877 Yo uso Software Libre y tu? 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
Gusty install fest @ .pe
The Perú LoCo team is making an install fest for the release of Gutsy next Saturday 27 and i've been ask to speak about MOTU. I wonder if someone has made a speek about MOTU before and can send me his/her presentation so i can base mine on it? Thans in advance. -- aka nxvl key fingerprint: E140 4CC7 5E3C B6B4 DCA7 F6FD D22E 2FB4 A9BA 6877 gpg --keyserver keyserver.ubuntu.com --recv-keys A9BA6877 Yo uso Software Libre y tu? 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: fail2ban: missing regexp for ssh
I'm feeling the bug on LP On 10/15/07, Mathias Gug [EMAIL PROTECTED] wrote: Hi Rial, On Sat, Oct 13, 2007 at 11:11:18AM +0200, Rial Juan wrote: I don't know if this can be considered a bug or not; are valid users within the scope anyway? I for one feel safer, though, knowing that password attacks against the passwords of valid users will be stopped at the gates as well as random login attempts for invalid users. Could you file a bug report on launchpad.net about this issue (https://bugs.launchpad.net/ubuntu/+source/fail2ban/+filebug) ? -- Mathias -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- aka nxvl Yo uso Software Libre, y tu? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: fail2ban: missing regexp for ssh
I don't know why i can't see your bug report, it says i have no permissions did you have the specific URL? like https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/153092 On 10/15/07, Rial Juan [EMAIL PROTECTED] wrote: Sorry, I already dit it... Should probably have done a reply to all instead of just a reply to Matthias. My bug report: https://bugs.launchpad.net/bugs/152964 I suggest you mark your bug as a duplicate of mine or something so it's not filed twice... And don't worry 'bout the typo; I was feeling quite tired myself when I mailed this bug report to the list, otherwise I wouldn't have been so daft as to bother you guys with it, and filed it to lauchpad myself... Kind regards, On Mon, 2007-10-15 at 16:58 -0500, Nicolas Valcarcel wrote: Sorry, typo mistake, s/feeling/filling/g i'm kind of tired On 10/15/07, *Nicolas Valcarcel* [EMAIL PROTECTED] wrote: I'm feeling the bug on LP On 10/15/07, *Mathias Gug* [EMAIL PROTECTED] wrote: Hi Rial, On Sat, Oct 13, 2007 at 11:11:18AM +0200, Rial Juan wrote: I don't know if this can be considered a bug or not; are valid users within the scope anyway? I for one feel safer, though, knowing that password attacks against the passwords of valid users will be stopped at the gates as well as random login attempts for invalid users. Could you file a bug report on launchpad.net about this issue (https://bugs.launchpad.net/ubuntu/+source/fail2ban/+filebug ) ? -- Mathias -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -- aka nxvl Yo uso Software Libre, y tu? -- aka nxvl Yo uso Software Libre, y tu? -- Welcome to text-only Counterstrike. You are in a dark, outdoor map. go north You have been pwned by a grue. -- aka nxvl Yo uso Software Libre, y tu? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
