Re: Status of documentation
On May 20, 2011, at 05:33 PM, Jelmer Vernooij wrote: On Fri, 2011-05-20 at 11:46 -0400, Barry Warsaw wrote: A couple of quick notes on UDD documentation. At UDS-O, we agreed that the current wiki documentation should be deleted, with pointers added to Daniel's Ubuntu Packaging Guide. Even though the latter is currently only available via a temporary link, it's better not to have multiple versions of the UDD documentation floating around. Thanks for removing those wiki pages, I guess you've already met Jorge's quota for this cycle ;) As soon as Jorge issued his challenge, I knew I'd have no trouble meeting it this cycle! :) This is now done. When Daniel gets a permanent URL for the docs, I will of course update the links. Here's the current URL: http://people.canonical.com/~dholbach/packaging-guide/html/knowledge-base.html This also means that if you want to make changes to the docs, you should branch the UPG's trunk and do a merge proposal. The trunk is at lp:ubuntu-packaging-guide Any other suggestions for improving, reorganizing, or expanding on the UDD bits of the packaging guide documentation are welcome! What releases of Ubuntu is the packaging guide aimed at? There are some things in the documentation that are available in reasonably new versions (Maverick, Natty) but the packaging guide still describes alternatives for older releases. Yep, and I'd like to phase those out. My own preference would be to target at least Natty for now because I think this was the first cycle where serious development could be done with UDD. Perhaps once 12.04 is out, we should target the LTS and relegate alternatives to an older distroseries section. -Barry signature.asc Description: PGP signature -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: UbuStu Art
i have some design about ubuntu studio http://www.flickr.com/photos/honki/4808479623/in/set-72157623970936653/ http://www.flickr.com/photos/honki/4808479623/in/set-72157623970936653/ http://www.flickr.com/photos/honki/5053852596/in/set-72157623970936653/ http://www.flickr.com/photos/honki/5053852596/in/set-72157623970936653/or about ubuntu http://www.flickr.com/photos/honki/sets/72157623970936653/with/5053852596/ http://www.flickr.com/photos/honki/sets/72157623970936653/with/5053852596/ thx honki 2011/5/24 Seattle Chaz seattlec...@gmail.com I don't know if he's still active or not, but Shitsukesen has some very nice work posted at Deviant Art. I've found his wallpaper to be quite beautiful, unobtrusive and conducive to creative expression. http://shitsukesen.deviantart.com/art/Ubuntu-Studio-Wallpaper-173220729 He's also done some nice work with the UbuntuStudio brandmark http://fc07.deviantart.net/fs70/i/2010/210/0/6/Ubuntu_Studio_Brandmark_V2_by_shitsukesen.png http://fc00.deviantart.net/fs70/i/2010/211/f/3/Ubuntu_Studio_Brandmark_V3_by_shitsukesen.png His gallery is at http://shitsukesen.deviantart.com/ -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Future Ubuntu Studio website
While the art discussion is ongoing I feel that the website structure needs some more development. Features, hosting and all that. Art can be dropped in any time. @Scott: Maybe start a wiki page for the website development? Might be one already and I missed it. If there is or you create one, just make it the last line in your posts to this thread or something. -- -Cory K. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UbuStu Art
On Tue, May 24, 2011 at 6:58 AM, red honki pdi...@gmail.com wrote: hi thank you. because ubuntu studio is to long, it is hard to design logo. can we have short name? /Officially/ Ubuntu Studio is the approved form and the current logos are all that will be supported. /Unofficially/ folks can do what they like. -- -Cory K. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: UbuStu Art
hi CK i know your mean. :) thx honki 2011/5/24 C K coryis...@gmail.com On Tue, May 24, 2011 at 6:58 AM, red honki pdi...@gmail.com wrote: hi thank you. because ubuntu studio is to long, it is hard to design logo. can we have short name? /Officially/ Ubuntu Studio is the approved form and the current logos are all that will be supported. /Unofficially/ folks can do what they like. -- -Cory K. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: What Ubuntu should I install to help by testing
On Mon, May 23, 2011 at 10:50 AM, Ralf ralf.mard...@alice-dsl.net wrote: Hi :) tomorrow my hard disks should be tidied up. I'll keep Suse 11.2 64-bit to see what's going on in the RPM world and as my stable digital audio/midi workstation Edunbuntu 10.10 Maverick 32-bit (+ ubuntu studio packages) will stay. If I could help by testing, what version and architecture of Ubuntu/ Ubuntu Studio should I install on my 64-bit AMD dual-core machine? Please post a link to the download. Best, Ralf -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel Hi Ralf, Please find the Oneiric Ocelot release schedule here: https://wiki.ubuntu.com/OneiricReleaseSchedule You can find the ISO images here: http://cdimage.ubuntu.com/ubuntustudio/daily/ And the QA testing images here: http://iso.qa.ubuntu.com/qatracker/build/ubuntustudio/all As Cory said, right now we are not currently testing but we would start for the Alpha 1 image. We are at liberty to test the daily images at any time once they are being built. There isn't a regulated schedule to test these and are generally done as needed to test a specific change or fix. These are also used to test the current image just because. The QA testing images _are_ scheduled however and rather critical. While the daily images are available at any time and are not required by process/procedure to be tested, the QA testing images _are_ required to be tested and specific types of tests. These are indicated on the website and are consistent for each testing period. Generally, I believe you can view the testing schedule to align with availability of Alpha, Beta, and RC images. I will stress again, it is imperative to validate the QA testing images. It is possible that the next image will not be available if a previous image hasn't been completely tested. Once a QA image is available we have a couple of days to validate the image. I view the division of QA vs. daily images further by purpose. The QA image are testing to validate the ISO, i.e. does the ISO burn onto the disc, does it install properly, does the OS boot and run. The daily images are for verifying that the applications run correctly or that system settings are working as expected. The QA images can be used to test system settings or applications are working properly together, but generally do not suit this purpose because of their limited availability. I hope this helps you begin to understand some of the testing. Please expect the first few alpha images to be a bit quirky due to the shift to XFCE and we will be specifically testing the early releases for these issues. Later in the cycle we may be looking/testing for other areas, e.g. making sure that new applications are in the proper position in the menu, or that menu changes are correct. Cheers, ScottL -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
RE: What Ubuntu should I install to help by testing
I changed my mind, I'll keep the official Ubuntu Studio Natty release and will install testing releases to another partition. A request for help, regarding to the pppoe issue will be send to the users mailing list. -Original Message- From: Ralf Mardorf Sent: Wed 5/25/2011 01:44 To: Ubuntu Studio Development Technical Discussion Subject: Re: What Ubuntu should I install to help by testing Hi Scott :) some minutes ago I installed the official Ubuntu Studio Natty 64-bit release and I will replace it by the daily image. The Natty installer detected the correct keyboard, but for the GNOME session the keyboard setting is wrong. I can't get PPPoE to work. I didn't select the 2D/3D creation and editing suite, but Blender is installed, while I'm missing Gimp ;). I'm not interested in solving this issues, but install the daily release instead, if I should run into the same issue there, then I'll try to solve them. Hi Ralf, Please find the Oneiric Ocelot release schedule here: https://wiki.ubuntu.com/OneiricReleaseSchedule You can find the ISO images here: http://cdimage.ubuntu.com/ubuntustudio/daily/ Daily releases for Oneirec testing are Natty releases from April? I guess it's the wrong link? And the QA testing images here: http://iso.qa.ubuntu.com/qatracker/build/ubuntustudio/all I always do a manual partitioning, but I won't do partitioning experiments on my machine, sorry. Anyway, I would like to install and test, if you will send the correct link. To be continued, Ralf -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Transitions in progress
On Wed, May 18, 2011 at 10:34:49AM +0100, Colin Watson wrote: * OCaml 3.12.0 I've been doing rebuilds for this. With a few exceptions, this seems fairly straightforward, and is mainly hampered by the armel buildds being somewhat behind. It's over 70% complete. This transition is now complete. -- Colin Watson [cjwat...@ubuntu.com] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
We need more bitesize bugs
Hello everybody, if you come across bugs that are easy to solve or could where you could imagine helping somebody solve them, please tag them as 'bitesize'. A script that adds the tag, subscribes you and adds a comment to the bug report was just added to ubuntu-dev-tools (it's called bitesize) and will hopefully soon end up in natty-backports too. We get more and more people who are excited about helping out, who read some documentation and are just blocked on finding a simple task they can get started with. Just to clarify: - if it's a simple bug, but it's a blocker for you, just go and fix it yourself - no need to wait for a willing contributor. :-) - if the correct way to fix it, is to submit it upstream, then that's what we should expect from the contributors and help them do it. It does not necessarily need to result in an Ubuntu upload. I plan to refer new contributors to bitesize bugs more this cycle and it'd be great if we had a nice list of simple issues waiting for them. Thanks a lot in advance. Have a great day, Daniel -- Get involved with Ubuntu Development: http://identi.ca/ubuntudev http://twitter.com/ubuntudev http://facebook.com/ubuntudev -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: We need more bitesize bugs
Am Dienstag, den 24.05.2011, 16:09 +0200 schrieb Daniel Holbach: A script that adds the tag, subscribes you and adds a comment to the bug report was just added to ubuntu-dev-tools (it's called bitesize) and will hopefully soon end up in natty-backports too. Everyone who wants the latest and greatest improvements from ubuntu-dev-tools is encouraged to use our daily builds [1]. These daily builds should be always in a usable state. [1] https://launchpad.net/~udt-developers/+archive/daily -- Benjamin Drung Debian Ubuntu Developer signature.asc Description: This is a digitally signed message part -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu Kernel Team Meeting Minutes - 2011-05-24
= Meeting Minutes = [[http://irclogs.ubuntu.com/2011/05/24/%23ubuntu-meeting.txt|IRC Log of the meeting.]] BR [[http://voices.canonical.com/kernelteam|Meeting minutes.]] == Agenda == [[https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 24 May, 2011|20110524 Meeting Agenda]] === Release Metrics === Release Meeting Bugs (0 bugs, 18 Blueprints) Release Milestoned Bugs (24 across all packages) * 0 linux kernel bugs () * 0 linux-ti-omap4 bugs () * 0 linux-meta-ti-omap4 bug () Release Targeted Bugs (171 across all packages) * 21 linux kernel bugs () * 6 linux-ti-omap4 bugs () * 0 linux-meta-ti-omap4 bug () Milestoned Features * 1 blueprint (Including HWE Blueprints) Natty Updates Bugs * 28 Linux Bugs () Maverick Updates Bugs * 5 Linux Bugs (no change) Lucid Updates Bugs * 17 Linux Bugs (up 1) Bugs with Patches Attached:90 (up 3) * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]] * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]] === Blueprints: Oneiric Bug Handling === All alpha 1 items are in progress: * [jeremyfoshee] work with SRU team and KRM to develop/define process for addressing development kernel bugs.: INPROGRESS * started this conversation with an e-mail. * [jeremyfoshee] Generate specific hotlist for devel bugs focus: INPROGRESS * will initially use the same requirements as the 'by team' hotlist, but focused on Oneiric * copied the hotlist script and currently working through changes * [jeremyfoshee] drive new state bugs to 0 and maintain 0 new status bugs daily: INPROGRESS * 8 current oneiric bugs. All have been initially triaged and are now going through deeper analysis so far this has helped me determine what skills I'd like to further develop * [jeremyfoshee] identify which scripts we no longer run which we should port forward (with the aim of 0 New bugs): INPROGRESS * Brad's confirmed script is doing a great job currently of identifying what bugs are complete enough to be set confirmed * Started the discussion on this in e-mail. Will follow up with some thoughts as soon as I have had the time to evaluate the responses and chatted with Pete (he's been quite busy lately :)) === Blueprints: Oneiric Config Review === We just need to schedule a follow on config review session to look at jj's config comparisons. I suggest we do this at the Rally. I'm continuing to work through some of the config options noted from UDS, none of which are critical for the Alpha-1 release. === Blueprints: Oneiric Delta Review === apw, bjf, jjohansen, kees, lag, manjo, mpoirier, ralveti, rtg: you have Alpha-1 work items to review your set of Ubuntu patches. Please take a moment to review or postpone till Alpha-2. See https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricUbuntuDeltaReview for your specific set of patches. === Blueprints: Oneiric Server Requirements === All good (nothing started) === Status: General Oneiric === We've uploaded the 2.6.39-3.9 kernel which is based on upstream v2.6.39 final. I intend to keep us on v2.6.39 final for our Alpha-1 release on Thurs June 2. === Status: Stable Kernel Team === All kernel packages in -proposed have had verification complete and will be published when Certification and QA are complete (Not all series receive Certification). The Stable team will prepare new kernel packages this week to begin a new cycle. BR BR As decided at UDS, the stable kernel cadence will change to a three week cycle, in order to allow time to properly prepare the kernel packages BR BR Herton is part of the stable team this cycle and Brad is part-time while doing work with QA. === Security bugfix kernels - Maverick/Lucid/Hardy === ||Package|| Upd/Sec || Proposed || TiP || Verified || || || || || || || ||lucidlinux-ec2 || 2.6.32-314.27|| 2.6.32-316.31||8 ||8 || ||--- linux-ports-meta || 2.6.32.31.23 || 2.6.32.32.24 ||0 ||0 || ||--- linux-meta-lts-backport-maverick || 2.6.35.25.36 || 2.6.35.28.37 ||0 ||0 || ||--- linux-lts-backport-maverick || 2.6.35-25.44~lucid1 || 2.6.35-28.50~lucid1 || 13 || 13 || ||--- linux-backports-modules-2.6.32|| 2.6.32-31.31 || 2.6.32-32.32 ||0 ||0 || ||--- linux-firmware|| 1.34.7 || 1.34.10 ||0 ||0 || ||--- linux || 2.6.32-31.61 || 2.6.32-32.62 ||4 ||4 || ||--- linux-meta|| 2.6.32.31.37
Enabling the kernel's DMESG_RESTRICT feature
Hello! In Oneiric, I'd like to change the default availability of yet another long-standing system debugging feature: dmesg. Since Linux 2.6.37, CONFIG_DMESG_RESTRICT (/proc/sys/kernel/dmesg_restrict) has existed[1], but the default in Ubuntu has been to leave dmesg available to unprivileged users (i.e. lacking the CAP_SYSLOG capability, changed in 2.6.38[2]). I brought this up[3] in November, but ultimately decided to wait until we had more important reasons to enable it by default. As we have continued to close kernel address leaks, the kernel syslog (dmesg) remains one of the last large places where information is being reported. As such, I want to close this off from regular users so that local kernel exploits continue to have an even harder time getting a foot-hold on vulnerabilities. And, as before, this is a tunable that you can change in /etc/sysctl.d/ if you do development work, like getting owned, etc. For the average user, this information is not needed. Kernel address leaks will become even more valuable to exploit authors once kernel base address randomization[4] lands in the kernel, and I want to make sure Ubuntu is prepared, well in advance of the next LTS, for this change. When the base address is randomized, dmesg must be privileged, or else the exactly offset is trivially visible (i.e. of the offset from 0xc100): $ dmesg | grep -m1 text [0.00] .text : 0xc100 - 0xc15112a1 (5188 kB) Now, making dmesg a privileged command will require extensive changes to documentation, debug-info-gather tools (e.g. users of dmesg like Apport), etc. The syslog daemon already has the needed privileges since it does more than just read the klog buffer (see [3] for a full list of klogctl() users). As with last year's ptrace changes[5], I plan to patch the userspace tools (i.e. dmesg) themselves to produce a useful error message instead of what it current reports when /proc/sys/kernel/dmesg_restrict is set to 1: $ dmesg klogctl: Operation not permitted I think something like this will be used: $ dmesg klogctl: Operation not permitted The kernel syslog is only available to privileged users. For more details, see /etc/sysctl.d/10-dmesg.conf And then there will be extended information in that file, etc. One unresolved problem is that the local default user (who is part of admin) is also part of the adm group, which means these log files are visible without additional privileges: -rw-r- 1 root adm 25937 2011-05-24 10:59 /var/log/dmesg -rw-r- 1 syslog adm 0 2011-05-24 11:17 /var/log/kern.log (And some system have a historically world-readable /var/log/dmesg that should be fixed...) Does anyone see any problems in removing the default user from the adm group? It seems to almost exclusively only be used for log file reading permissions... Thoughts, flames, etc? -Kees [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=eaf06b241b091357e72b76863ba16e89610d31bd [2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=38ef4c2e437d11b5922723504b62824e96761459 [3] https://lists.ubuntu.com/archives/kernel-team/2010-November/013499.html [4] https://lkml.org/lkml/2011/5/22/99 [5] https://lists.ubuntu.com/archives/ubuntu-devel/2010-May/030797.html -- Kees Cook Ubuntu Security Team -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Enabling the kernel's DMESG_RESTRICT feature
Excerpts from Kees Cook's message of Tue May 24 11:46:48 -0700 2011: One unresolved problem is that the local default user (who is part of admin) is also part of the adm group, which means these log files are visible without additional privileges: -rw-r- 1 root adm 25937 2011-05-24 10:59 /var/log/dmesg -rw-r- 1 syslog adm 0 2011-05-24 11:17 /var/log/kern.log (And some system have a historically world-readable /var/log/dmesg that should be fixed...) Does anyone see any problems in removing the default user from the adm group? It seems to almost exclusively only be used for log file reading permissions... Thoughts, flames, etc? +1 I've always been a bit surprised at how much I can see in /var/log when logged into a brand new box as the initial admin user. I think users are accustomed to sudo when debugging issues, and I'm comfortable with saying that reading /var/log/* is just one more thing you need to use sudo for. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
blueprint priorities
I'm looking for more details on how people use blueprints, particularly what the blueprint priorities mean. If there's a page on this already, let me know and I'll work on getting it a higher profile so it appears on Google/wiki.ubuntu.com searches. If we don't have it documented yet, does this list map to how you use the priorities? Essential - Must happen in this cycle High - Desirable in this cycle Medium - Would like to happen in this cycle Low - Likely to be dropped from this cycle Rejected - Not considered in this cycle If that's not quite right, how do you use the priorities, and do you have some suggestions on better definitions? Thanks, Allison -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: blueprint priorities
On Tue, May 24, 2011 at 03:03:54PM -0700, Allison Randal wrote: I'm looking for more details on how people use blueprints, particularly what the blueprint priorities mean. If there's a page on this already, let me know and I'll work on getting it a higher profile so it appears on Google/wiki.ubuntu.com searches. If we don't have it documented yet, does this list map to how you use the priorities? Essential - Must happen in this cycle High - Desirable in this cycle Medium - Would like to happen in this cycle Low - Likely to be dropped from this cycle Rejected - Not considered in this cycle If that's not quite right, how do you use the priorities, and do you have some suggestions on better definitions? This is basically how the security team works, yes. I would probably replace Desirable in this cycle with Important for this cycle or maybe Likely in this cycle, otherwise it sounds too close to Medium to me. -Kees -- Kees Cook Ubuntu Security Team -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Enabling the kernel's DMESG_RESTRICT feature
On Tue, May 24, 2011 at 11:46:48AM -0700, Kees Cook wrote: Hello! In Oneiric, I'd like to change the default availability of yet another long-standing system debugging feature: dmesg. Thoughts, flames, etc? See https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/716595 for some sudo caching problems apport has had to work around which might pose some complications here as well. Can you outline your plans for updating apport in conjunction with this change? Bryce -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [ubuntu/oneiric] pdf2djvu 0.7.7-1ubuntu1 (Accepted)
pdf2djvu (0.7.7-1ubuntu1) oneiric; urgency=low * Rebuild * Bump standards version to 3.9.2 I'd like to take this opportunity to publicize the command dch -R for no change rebuilds. It DTRT most of the time. It appends and increments buildX or just increments ubuntuX. Micah -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [ubuntu/oneiric] pdf2djvu 0.7.7-1ubuntu1 (Accepted)
Hi Micah, On Tue, May 24, 2011 at 8:50 PM, Micah Gersten mic...@ubuntu.com wrote: I'd like to take this opportunity to publicize the command dch -R for no change rebuilds. It DTRT most of the time. It appends and increments buildX or just increments ubuntuX. Micah A poke on IRC could have accomplished the same thing. Consider bringing it up privately first next time :) Steve -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [ubuntu/oneiric] pdf2djvu 0.7.7-1ubuntu1 (Accepted)
On 05/24/2011 10:12 PM, Steve Stalcup wrote: Hi Micah, On Tue, May 24, 2011 at 8:50 PM, Micah Gersten mic...@ubuntu.com wrote: I'd like to take this opportunity to publicize the command dch -R for no change rebuilds. It DTRT most of the time. It appends and increments buildX or just increments ubuntuX. Micah A poke on IRC could have accomplished the same thing. Consider bringing it up privately first next time :) Steve Sorry, my intent was to focus on the upload and not the uploader. That's why I removed the uploader from the E-Mail. I've seen quite a few people who were unaware of the command, so I thought Public Service Announcement was a good idea. I realized I forgot to change the subject as well. Micah -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [ubuntu/oneiric] pdf2djvu 0.7.7-1ubuntu1 (Accepted)
On 25/05/2011 10:50, Micah Gersten wrote: pdf2djvu (0.7.7-1ubuntu1) oneiric; urgency=low * Rebuild * Bump standards version to 3.9.2 I'd like to take this opportunity to publicize the command dch -R for no change rebuilds. It DTRT most of the time. It appends and increments buildX or just increments ubuntuX. Thanks for the hint. I've been doing it manually all this time. :-) -- Kind regards, Loong Jin signature.asc Description: OpenPGP digital signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Enabling the kernel's DMESG_RESTRICT feature
Hey Kees, Kees Cook [2011-05-24 11:46 -0700]: $ dmesg | grep -m1 text [0.00] .text : 0xc100 - 0xc15112a1 (5188 kB) Would it be possible to have the kernel just not log the addresses in the first place? It seems kind of pointless to make a big effort of randomizing these and then yell it out loudly where it lands in any kind of log file. People might also have a custom rsyslog configuration etc. which we can't even fix on upgrades. So wouldn't it be enough to have the actual addresses somewhere in /proc/ in a 0400 file, and just purge them from printk()s? Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Announcing the Next Ubuntu Bug Day! - 26 May 2011
Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Compiz! * 50 New bugs need a hug * 39 Incomplete bugs need a status check * 50 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 26 May 2011 * https://wiki.ubuntu.com/UbuntuBugDay/20110526 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day!, -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
