On Friday 30 March 2007 22:25, Florian Weimer wrote:
> * Christoph Haas:
> > What might be the cause? Is there some fragmentation effect?
>
> It's probably ext3's directory hashing. It tries to access the files
> in /var/lib/dpkg/info in hash order, which leads to essentially random
> disk I/O.
I
On Mon, 2 Apr 2007 11:10:55 +0200
Christoph Haas <[EMAIL PROTECTED]> wrote:
> Is there anything that I can do about it? Tuning the ext3 partition? Or is
> somebody capable of turning the info directory into - say - an sqlite
> database or in future Debian releases?
There is a thread on debian-d
This ITP was (obviously) an attempt at an April's Fool joke. Some time
ago I played a bit with Markov Chains, which are a method for taking an
input text, and generating output that uses words from the input, but is
gibberish (http://en.wikipedia.org/wiki/Markov_Chain). I got the idea
that it would
On Mon, Apr 02, 2007 at 09:32:22AM +0100, Julian Gilbey wrote:
> On Mon, Apr 02, 2007 at 09:48:13AM +0200, Robert Millan wrote:
> > Package: devscripts
> > Version: 2.9.26
> > Severity: wishlist
> > Tags: patch
> >
> > Since dates written to changelogs are going to be read by people all over
> >
Re: Robert Millan 2007-04-02 <[EMAIL PROTECTED]>
> > > Since dates written to changelogs are going to be read by people all over
> > > the
> > > world, IMHO it is better if these dates are in UTC to make it easier to
> > > figure out when it was uploaded in comparison to other events (such as the
On Mon, Apr 02, 2007 at 02:11:51PM +0200, Christoph Berg wrote:
> Re: Robert Millan 2007-04-02 <[EMAIL PROTECTED]>
> > > > Since dates written to changelogs are going to be read by people all
> > > > over the
> > > > world, IMHO it is better if these dates are in UTC to make it easier to
> > > > f
Package: wnpp
Severity: wishlist
Hi,
the Pandora FMS (Free Monitoring System) seems to be a nice and modern
alternative to Nagios and the not so free BigBrother (http://bb4.org/,
http://bb4.com/), and perhaps also Zenoss (see ITPs at
http://bugs.debian.org/361253 and http://bugs.debian.org/399530
Package: wnpp
Severity: wishlist
Owner: Bernd Zeimetz <[EMAIL PROTECTED]>
* Package name: zope-advancedquery
Version : 2.2
Upstream Author : Dr. Dieter Maurer <[EMAIL PROTECTED]>
* URL :
http://www.dieter.handshake.de/pyprojects/zope/#AdvancedQuery
* License :
On Mon, Apr 02, 2007 at 02:11:51PM +0200, Christoph Berg wrote:
> > > > Since dates written to changelogs are going to be read by people all
> > > > over the
> > > > world, IMHO it is better if these dates are in UTC to make it easier to
> > > > figure out when it was uploaded in comparison to oth
Package: wnpp
Severity: wishlist
Owner: "Michal Čihař" <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: python-tagpy
Version : 0.91
Upstream Author : Andreas Kloeckner <[EMAIL PROTECTED]>
* URL : http://news.tiker.net/software/tagpy
* L
On Monday 02 April 2007 14:11, Christoph Berg wrote:
> Re: Robert Millan 2007-04-02 <[EMAIL PROTECTED]>
>
> > > > Since dates written to changelogs are going to be read by people all
> > > > over the world, IMHO it is better if these dates are in UTC to make
> > > > it easier to figure out when it
On Monday 02 April 2007 15:11, Stefano Zacchiroli wrote:
> I share the feeling of "niceness" of the personal touch, but this isn't
> a technical reason, and the point of uniforming a timezone so that it's
> easier to compare dates among different changelog is definitely a valid
> one.
That is not
As some of you may have noticed, the patches.ubuntu.com website and
equivalent mailing of changes to the Debian PTS and ubuntu-patches
mailing list has been offline, or at least intermittent, for a few
weeks.
This was caused by the hosting machine running out of disk space, and
the Debian mirror w
On Mon, Apr 02, 2007 at 03:31:37PM +0200, Frans Pop wrote:
> That is not really a valid reason either because converting a timestamp
> from a changelog entry to any other timezone or format is trivial:
>
> $ D="$(zgrep "^ -- " /usr/share/doc/apt/changelog.Debian.gz | \
> > head -1 | sed "s/^.*>
On Mon, 2 Apr 2007 15:49:54 +0200
Stefano Zacchiroli <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 02, 2007 at 03:31:37PM +0200, Frans Pop wrote:
> > That is not really a valid reason either because converting a timestamp
> > from a changelog entry to any other timezone or format is trivial:
> >
> >
On Mon, Apr 02, 2007 at 01:37:23PM +0200, Robert Millan wrote:
> > This is a nice idea. I think it should also be discussed on
> > debian-devel and debian-policy.
>
> CCing -devel. For -policy I think it is too early (usualy, common practice is
> stablished before Policy enforces it).
>
> Also
Stefano Zacchiroli wrote:
> I share the feeling of "niceness" of the personal touch, but this isn't
> a technical reason
It's nice to know if an upload was made at 4:30 am local time, va 6 pm local
time. It says something about the possible condition of the uploader.
--
see shy jo
signature.as
Stefano Zacchiroli wrote:
> > $ D="$(zgrep "^ -- " /usr/share/doc/apt/changelog.Debian.gz | \
> > > head -1 | sed "s/^.*> //")"
> > $ date -uRd "$D"
>
> "Trivial" is something I can do without having the need of thinking
> about an implementation of it. I guess you spent a couple of minutes
> wri
On Mon, Apr 02, 2007 at 03:11:23PM +0200, Stefano Zacchiroli wrote:
> I share the feeling of "niceness" of the personal touch, but this isn't
> a technical reason, and the point of uniforming a timezone so that it's
> easier to compare dates among different changelog is definitely a valid
> one.
On ma, 2007-04-02 at 19:26 +0100, Mark Brown wrote:
> Given how easy it is to canonicalise the timestamp data, the fact that
> it's data loss and the questionable utility of the information why is it
> worth it?
Maintaining status quo is easy. Making programs that compare timestamps
understand tim
Mike Hommey schreef:
> On Thu, Sep 21, 2006 at 10:45:06AM -0500, alfredo diega <[EMAIL PROTECTED]>
> wrote:
>
>>On 9/21/06, Ben Armstrong <[EMAIL PROTECTED]> wrote:
>>
>>>-
>>>I can see you're frustrated. You've invested a lot of energy into
>>>writing this note to us about a problem you see in
Lars Wirzenius schrieb:
> My gut feeling is that there's more people who edit the timestamp
> manually than those who compare them mentally, so I'm in favor of
> maintaining status quo.
Hmm and my gut feeling is that the vast majority of maintainers just use
dch instead of manually writing the cha
On Mon, 02 Apr 2007, Bastian Venthur wrote:
> Lars Wirzenius schrieb:
> > My gut feeling is that there's more people who edit the timestamp
> > manually than those who compare them mentally, so I'm in favor of
> > maintaining status quo.
>
> Hmm and my gut feeling is that the vast majority of main
On Mon, Apr 02, 2007 at 08:49:44PM +0200, Bastian Venthur wrote:
> Hmm and my gut feeling is that the vast majority of maintainers just use
> dch instead of manually writing the changelog skeleton (it's faster and
> less error prone). But until we have verifiable numbers it's all moot.
I tend to
On Mon, Apr 02, 2007 at 03:11:23PM +0200, Stefano Zacchiroli wrote:
> I share the feeling of "niceness" of the personal touch, but this isn't
> a technical reason, and the point of uniforming a timezone so that it's
> easier to compare dates among different changelog is definitely a valid
> one.
I
Package: wnpp
Severity: wishlist
Owner: Bernd Zeimetz <[EMAIL PROTECTED]>
* Package name: zope-managableindex
Version : 1.6.1
Upstream Author : Dr. Dieter Maurer <[EMAIL PROTECTED]>
* URL :
http://www.dieter.handshake.de/pyprojects/zope/#ManagableIndex
* License
Package: wnpp
Severity: wishlist
Owner: Bernd Zeimetz <[EMAIL PROTECTED]>
* Package name: zope-ofolder
Version : 1.0
Upstream Author : Dr. Dieter Maurer <[EMAIL PROTECTED]>
* URL : http://www.dieter.handshake.de/pyprojects/zope/#bct_sec_3.6
* License : completel
> "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
Wouter> Sun, 31 Dec 2006 14:40:46 +0100
Wouter> You didn't fail basic math, did you? ;-)
Just remember to subtract 1 hour, don't add it.
I could imagine people getting this wrong.
--
Brian May <[EMAIL PROTECTED]>
--
To UNS
28 matches
Mail list logo