Search Results: "ag"

8 April 2007

Gustavo Franco: Etch, Lenny and the future.

Etch is out, thanks for all those who worked hard during the release. Time to party, but for those that are hungry to push their packages from experimental to sid, make sure to not start tons of not coordinated transitions and breakage, if in doubt about what to do ask the release team (debian-release@lists.debian.org). Don't make sid and testing such a nightmare from the first day, keeping uploading new upstream releases to experimental for a while, ask for testers (tons of them) and move to sid non-RC buggy stuff now! Help us get Lenny ready.

Brett Parker: Oh Noes! This means lots of work!

Debian GNU/Linux 4.0 has been released - congratulations to all those involved in the release process, you've all done a fantastic job (as always ;). Now I've just got to test the upgrade for the NFS root desktop machines at work (that's going to be *sooo* much fun!) and make sure that nothing obvious breaks - I'm not expecting many problems, it *should* go quite smoothly (probably!). Might also use the "official" non-free packages for the sun j2sdk rather than using java-package, haven't decided yet (and actually, as we also use sun-j2sdk1.4, I'm going to have to use java-package for that anyways!). Hmmm, I suppose I should update all of my various build chroots and set up all the scripts that I'm going to need also - feh - that can wait for a bit. Ahh - and I'm going to need to compile an etch version of ion3 from unstable, can't be having my workstation running one of those dodgy window managers that makes it almost impossible to get anything done without using the mouse, afterall! Right - anyways - I think I shall just go faint, that was *far* too quick between sarge and etch!

Amaya Rodrigo: Hummm, let's break everything up again!

So Etch is out, can we go back to breaking sid more often? I really really miss it!

Erich Schubert: Debian 4.0 'etch' released

It's finally out. Happy Easter. Debian has just Yes, it's finally out. And I hope it has the high quality you've come to expect for Debian releases (which is probably why it takes us so long, apart from supporting 11 architectures in this release). Congrats, and a big thank you to all those involved, especially our release managers.

Daniel Baumann: After the release is before the release

Now that Debian Etch is released, we can finally start working on Lenny. For me, amongst normal package maintainer tasks, this includes: However, I'm seeing mass bug filing times coming! :) ...right, and parties too.

Ingo Juergensmann: Serendipity and shared installations on Debian

Hmmm... maybe I'm doing something wrong, but somehow I can't get s9y to use a multi-site config as described on this page (by Garvin Hicking).

Of course, symlinking and such went fine and I get the config screen (serendipity_admin.php), but I miss the place where to change the database setup, which is done in the Debian package via db-config and lies in /etc/serendpity/database.inc.php.

This is my multisite setup so far (a mixed setup with copied/symlinked files):


lrwxrwxrwx archives -> /usr/share/serendipity/www/archives
lrwxrwxrwx bundled-libs -> /usr/share/serendipity/www/bundled-libs
lrwxrwxrwx comment.php -> /usr/share/serendipity/www/comment.php
lrwxrwxrwx exit.php -> /usr/share/serendipity/www/exit.php
drwxrwxr-x htdocs
lrwxrwxrwx include -> /usr/share/serendipity/www/include
lrwxrwxrwx index.php -> /usr/share/serendipity/www/index.php
lrwxrwxrwx lang -> /usr/share/serendipity/www/lang
drwxr-xr-x pics
lrwxrwxrwx plugins -> /usr/share/serendipity/www/plugins
lrwxrwxrwx rss.php -> /usr/share/serendipity/www/rss.php
-rw-r--r-- 1 serendipity_admin_image_selector.php
-rw-r--r-- 1 serendipity_admin.php
-rw-r--r-- 1 serendipity_config.inc.php
-rw-r--r-- 1 serendipity_config_local.inc.php
-rw-r--r-- 1 serendipity.css.php
drwxrwxrwx templates
drwxrwxr-x templates_c
drwxrwxr-x uploads
lrwxrwxrwx wfwcomment.php -> /usr/share/serendipity/www/wfwcomment.php


Granted, during the last days I haven't found that much time (Easter holidays) yet to have a deeper look into the topic, but I got the impression that it's not that easy to use s9y on Debian with a shared installation setup as described on Garvins page. A sql scheme for the psql database is also missing in /usr/share/doc/serendipity.

Maybe you, dear lazyweb, have already a nice setup script for this purpose for Debian? Would be nice... :-)

Jonathan McDowell: Planned bank outages

My main bank is Cahoot. I'm reasonably happy with them - they pay a good rate of interest on a current account which is what drew me to them, but I like the fact I can do basically everything I need in their web interface at any time. However they seem to frequently announce periods of unavailability for card use or simliar. The latest announcement is:
Important update regarding use of your cahoot card: On Wednesday the 11th April between 21:00 and 22:00 there will be no service for cahoot card holders at Abbey, Link, and VISA ATM's. All point of sale transactions will be subject to a limit of 500 during this period. We apologise for any inconvenience caused by this essential maintenance.
This isn't the first time they've said I'd been unable to use my card for a certain period. They also seem to do (pre-announced) work on their website that causes it to be unavailable. While none of this has ever caused me a problem (yet), I do find it quite surprising. I never have any such announcements from other banks that I use. Are Cahoot just more honest about when they're doing potentially service affecting work? Or do other banks just have systems that don't result in any downtime during upgrades? Does anyone elses bank do announcements in the same fashion?

Lars Wirzenius: Debian: It's full of chars!

The etch release is imminent, so I thought I'd run sloccount on an unpacked Debian source tree. I wrote a little script that downloads and unpacks all Debian source packages. It does dpkg-source -x only, no debian/rules unpack or such, since that isn't standardized. The result is a source tree that is 46 gigabytes. Unfortunately, there is something in that tree that makes sloccount fail. It reports a mere 45 million lines of code, which is about 1022 lines per kilobyte. (Later, I'll narrow it down and report an actual bug. For now, the best I have is "something in Debian breaks sloccount".) Sloccount would give fairly good results, and it would exclude, say, JPEGs, of which there are 455. However, in this situation the best I can easily come up with is a sum of running a plain wc -l on each file, and that sum is 1005505921. That's just over one billion lines of code, in 2868448 files, or 350.54 lines per file, on average. Disclaimer: that sum includes many non-source files, such as the JPEGs, and a number of packages don't actually unpack properly with dpkg-source, you have to run some variant of debian/rules unpack. However, I'd be willing to bet the number is in the correct ball park. We can get better results once sloccount gets fixed.

Raphaël Hertzog: Results of the election

Sam is our new DPL. The margin with the second (Steve McIntyre again!) is very slim, 8 votes. And Steve only has 25 votes more than me. That’s not much either. What we can learn from this election: In the end, I really hope that sam is going to find a way to cooperate closely with the various candidates that are still highly motivated to work on improving Debian. I doubt that he will choose a board structure (although I would be glad to be proven wrong!), but I really hope that he will expand the 2IC principle (or something similar). I once told sam that he would have my full support if he got elected, and I intend to stand up to this promise. I said that because I share many of his ideas. The few fears that I have are mainly on how he is going to try to address these issues. But I have no reason to believe that he’s not going to listen to what we (and I) have to say. That’s why he got ranked just after me on my ballot. Good luck Sam, do not disappoint us!

Nacho Barrientos Arias: New DPL

Congratulations Sam! It’s time to make Debian fun again, best of luck!.

Erich Schubert: Upgrading Debian

I've upgraded an old woody box to etch these days. Live - I've been telling people they need to find a replacement for this machine for years now, but it's still around and playing an important role. And with 'woody' I mean 'a woody heavily played around with, with a couple of backports and exotic stuff like XFS, a custom 2.4.25 kernel with grsecurity'. Especially the latter was why I was afraid of doing the upgrade. In a first step, I incrementally upgraded everything to sarge (well, at least where the backports weren't already newer than sarge). I installed the stock sarge kernel, and prepared a reboot. The reboot was then done out of schedule, because the machine died on it's own - it has been crashing about 1-2 times a year, and it hadn't happened for some time. Judging from the logs, it was that old problem again. At second try it came up with the new kernel: I always forget to enable init ramdisks in the bootloader when switching from a custom kernel with every needed module built-in. I then continued upgrading to etch, pretty much one service at a time. Some things (I didn't do a full list; the box was running to many modified versions of packages of this being useful as upgrade reports to the release team, and it's a bit late in the schedule, too) where upgrading didn't work out of the box: But other than that, the upgrade was mostly a job for apt-get, not for me. The bad news: there is still something wrong with the machine. It doesn't crash, but spits e.g. the following to dmesg:
amavisd-new: page allocation failure. order:5, mode:0xd0
 [] __alloc_pages+0x2f8/0x370
 [] __get_free_pages+0x25/0x40
 [] kmem_getpages+0x22/0xc0
 [] cache_grow+0xba/0x180
 [] xfs_bmap_read_extents+0x36e/0x540 [xfs]
 [] cache_alloc_refill+0x16a/0x220
 [] xfs_bmap_alloc+0xe0d/0x1c60 [xfs]
 [] __kmalloc+0x74/0x80
 [] kmem_alloc+0x59/0xc0 [xfs]
...
So there is something wrong with the XFS malloc handling. This has happened twice now since the reboot. I've been suspecting XFS of being related to the servers' crashes before (which tend to occur during load; the crash which 'allowed' me to switch to 2.6 actually showed the OOM killer of that old kernel killing some inappropriate processes). After the easter holidays, I'll reboot the machine with the etch kernel, maybe this is gone then.

Mike Hommey: Debian s Easter

Easter this year is huge : Happy Easter ! PS: If FTP masters could push the number of packages in NEW down, that would be even greater.

Julien Valroff: First contribution to Debaday

My first review for Debaday (Debian Package of the Day) was published today. It is a short introduction to TinyCa, simple user interface to manage a small CA. I wanted to promote this tool, as it is exactly what I had been looking for for ages. PS: congratulations to Sam Hocevar for being the new DPL.

Alexis Sukrieh: He just did it!

Sam DPL

Gustavo Franco: Congratulations Sam!

The last few days have been quite difficult for me and right now I feel like a looser and winner at the same time as I never did before. In a way I feel that I won, since our platforms were so similar my ideas weren't that bad then and the project ack'ed that. The other side is that I'm just above NOTA and not closer to sam.

Anyway, I've already offered more help to the project (that refused) and for Sam. Time to go back to the shadows and keep co-maintaining more than 150 packages that you love to use, and maybe start more two or three subprojects... Thanks for those who voted for me, I hope to see you all during the next debconf and Guilherme, for working hard to keep my act together.

7 April 2007

Erich Schubert: Debian Init hackfest

I'd like to propose a Init Hackfest for Debian when etch is released. Debian includes several init systems, including sysvinit, runit, minit, initng and upstart. However, only sysvinit is really supported, and others can be used in a compability mode (and most of their benefits are gone then). So there is some work to be done here. Some init scripts probably could also use some cleanup. :-) Shortly after the release of etch is probably the best moment to work on such key parts such as the init system, since many packages are affected. I suggest to provide patches to the package maintainers and do uploads to 7-day delayed. If you are interested, maybe you could add your name to the wiki page? I also think the mailing list initscripts-ng-devel at alioth is appropriate for discussion.

Erich Schubert: Hello Planet GNOME!

I've been added to Planet GNOME (thanks jdub!), and this post is just to say hello! I havn't been a large GNOME contributor so far (I was the Debian maintainer for Galeon some years ago, thats about it), but I recently started a small DBus related project (for exploring the DBus APIs of programs), dbus-inspector, which is now hosted in the GNOME subversion repository. Other GNOME-related projects I'm thinking of: I'd like to say thank you for all the great work you did. Having been a Galeon power user, I'm by now quite convinced of the "keep it simple" approach, and I have the impression that not having so many options means that I get more work done (since I don't waste time playing around with infinite options). Thanks for that. And for providing me with a pretty and unobtrusive work environment for the last 8 years or so.

Arnaud Vandyck: Menuiserie!

Je ne sais pas pourquoi mais hier soir j'ai dessin une chaise! Je n'ai absolument pas une formation de menuisier mais j'ai essay ... J'ai commenc par des proportions pour un enfant, pour Adrien, mon fieul, et neveu. Appelez-moi Monsieur Zig-Zag! Les images sont dans la suite de l'article (et en attachement). Sur la chaise, il y a la maquette en carton. read more

Gunnar Wolf: Version 3.14 of the CoPL released

As I've posted before, I recently read Lawrence Rosen's Open Source Licensing Software Freedom and Intellectual Property Law. And I'm sure many of you will recognize the enormous constructive value of early-morning cavilations. Well, today I woke up thinking about strengths and weaknesses in th different Free Software licenses, and I decided to add my grain to the world of license proliferation. So, here goes version 3.14 of the CoPL. I wonder how long will it take before it reaches /usr/share/common-licenses on Debian systems ;-)
		       CONFUSING PUBLIC LICENSE
		       ========================
	This is version 3.14 of the Confusing Public License (referred to from
now on as "CoPL"). Copyright (c) 2007 Transnational
Republic. Additional copies of this license can be purchased at no
cost from any Transnational Republic citizen at any of its recognized
outposts, or freely copied. 
	Any legal claims regarding Original works or any of their Standard
versions licensed under the CoPL Should not abide by and be carried
out according to the current law of the Transnational Republic. The
Original author to pay for any attorney and other legal fees of any
dispute regarding said Original author.
	This license text is designed to protect all the Technology covered
under it under a thick layer of incomprehension. No technical,
professional or social measures might be used to subvert the intent of
this license. This license Must be carefully or professionally
reviewed by a lawyer or attorney, under any jurisdiction. Any serious
attempt to understand this license will immediatly terminate your
rights to keep reading this license. Original works licensed under the CoPL
will not be affected by this provision, you will still have permission
to use them.
	Redistributions of source code Should not retain the above copyright notice,
this list of conditions and the following disclaimer. 
	0. This License applies to any program or other work which contains a
   notice placed by the copyright holder saying it may be distributed
   under the terms of this Confusing Public License. The Original work
   below refers to any such program or work or Standard version.
	1. You desire to license the Technology to a
   large community to facilitate research, innovation and product
   development while maintaining compatibility of such products with
   the Technology as delivered by You
	2. Original author desires to license the Technology from You on
   the terms and conditions specified in this License.
	3. Redistributions in binary form Should not reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
	4. The names "Joe", "Curly", "Moe" and "The Three Stooges Foundation"
   May be used to endorse or promote products derived from this
   Original work without prior written permission, as they are in no way
   related. 
	5. There is no number 5. Seriously. In all Original works licensed under the
   CoPL, all necessary technical and social steps May be taken not
   to include, in any explicit way, the number 5.
	6. Original author Must make and give away verbatim copies of the
   source form of this Package
   without restriction, provided that Original Author duplicates all of
   the original copyright notices and associated disclaimers.
	7. Original author Must apply bug fixes, portability fixes and other
   modifications derived from the Public Domain or from
   the Copyright Holder. A Package modified in such a
   way shall still be considered the Standard Version.
	8. No Standard versions of the Original work Must be protected by this
   license. Original authors Should not choose a different, saner
   licensing model for the distribution of any modifications they
   make. The CoPL should be taken as a retroviral license.
	THE SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL YOU BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
				     Definitions
	"You" means the original author of the work covered under the CoPL.
	"Original author" means you.
	"Thou" means God almighty.
	"May" means "Should not, no matter what".
	"Must" means "May".
	"Should not" means "Must".
	"Reasonable copying fee" means nothing.
	"Standard version" means a modified version of the Original work.
				      DISCLAIMER
	The CoPL text, from the words "This is version" and up to and
including this paragraph, is to be taken as a preamble, and will not
be effective under any circumstances. 
	All work licensed under the CoPL should be considered as licensed
under the GNU General Public License version 2 or (at your option) any
later version. It is not the task of this license to point you on
where to get hold of said license.

Eddy Petrișor: Thanks...

The answer to my previous question is "to be". That happened thanks to a bunch of people, in no particular order:
Updates:

Next.

Previous.