On Sun, Jan 09, 2005 at 04:53:25PM +0100, Florian Weimer wrote:
> >> I think it's enough to add an additional notice stating that the named
> >> section is reproduced in the gfdl(7) manpage, incorporated by
> >> reference.
> >
> > I doubt that this would satisfy clause 4.H. of the G"F"DL:
> >
> >
On Mon, Feb 07, 2005 at 08:52:52PM +0100, Rafal Lewczuk wrote:
> Package: wnpp
> Severity: wishlist
>
> * Package name: life
When I hear "life" in the context of computers, I automatically think of
Conway's version... and so I'm sure do many many other people.
Bad choice of name by upstream I
On Mon, Feb 21, 2005 at 11:40:07AM +, Scott James Remnant wrote:
> On Sat, 2005-02-19 at 23:06 -0600, Micah Anderson wrote:
>
> >#957: dpkg 957 802533782 open [EMAIL PROTECTED] wishlist
> >
> Do I get a medal when I fix this in the next week or two? :) I've been
> working on an implementation
On Mon, Feb 21, 2005 at 07:10:36AM -0600, Peter Samuelson wrote:
> The main problem with distcc across architectures is the FUD
> surrounding whether gcc-as-cross-compiler spits out the same code as
> gcc-as-native-compiler. The gcc team seem to be very hesitant to make
> any guarantees about tha
On Sat, Mar 05, 2005 at 12:40:53AM +0100, Goswin von Brederlow wrote:
> Maybe I'm too unclear. They are guidelines. As such they don't define
> what source is or what forms of 'source' are acceptable but use the
> broadest term saying just 'source'. If something is still acceptable
> as source (li
On Mon, Mar 07, 2005 at 08:31:18AM +, Henning Makholm wrote:
> Scripsit Nick Phillips <[EMAIL PROTECTED]>
>
> > I also think that it would be a very good thing if we were to use our
> > collective discretion more often -- to say, for example, "well, you could
&
On Mon, Mar 14, 2005 at 10:34:54AM -0800, Thomas Bushnell BSG wrote:
> Sorry, I'm speaking in term of possible future policies, not the
> present.
>
> Create i386.us.debian.org, powerpc.us.debian.org,
> amd64.us.debian.org, etc. Each of them points to the existing
> mirrors. Make the installer
On Thu, Mar 17, 2005 at 01:26:17AM +0100, Matthias Urlichs wrote:
> No Debian tool depends on s/32/64/ or s/$/64/. As for me, I type "ppc"
> instead of "powerpc" very often, even though I should know better by now.
Likewise. This would seem to be a case of "once may be regarded as a
misfortune,
On Thu, Jan 05, 2006 at 04:43:13PM -0800, Thomas Bushnell BSG wrote:
> If the key is compromised, which is the only way the non-expiring key
> method can be broken, then the expiring key doesn't seem to be
> offering all that much additional security.
If the 2006 key takes (say) 15 months to co
On Fri, Jan 06, 2006 at 04:04:56AM -0800, Steve Langasek wrote:
> far :), I would encourage you to log into merkel and verify, directly and
> securely, the key at /org/ftp.debian.org/web/ziyi_key_2006.asc; sign it; and
> upload your signature to the public keyservers as well, if you are satisfied
On Thu, Jan 19, 2006 at 09:11:11PM -0500, Christopher Martin wrote:
> The important question here is one of legitimacy. Who exactly has the
> authority to determine these matters of interpretation? Specifically, who
> decides what is in accordance with the DFSG? The developers do, through
> GRs
On Wed, Feb 08, 2006 at 08:47:36PM +0100, Wouter Verhelst wrote:
> On Wed, Feb 08, 2006 at 09:21:36PM +1300, Nick Phillips wrote:
> > What it says, for those who can't (or can't be bothered) to read it is
> > essentially this:
> >
> > We will include GFDL&#x
On Wed, Feb 08, 2006 at 11:50:51AM -0500, Raul Miller wrote:
> On 2/8/06, Nick Phillips <[EMAIL PROTECTED]> wrote:
> > The GR as amended might appear to contradict the Social Contract, or the
> > DFSG, but it certainly *does not* modify them, and hence cannot be said to
> &
On Thu, Feb 09, 2006 at 05:18:31PM -0800, Thomas Bushnell BSG wrote:
> Everyone has the job of interpreting the DFSG. I'm saying that if, in
> the opinion of the Secretary, an interpretation of the DFSG is
> tantamount to a reversal of part of it, then it requires a 3:1
> majority to pass.
> If
On Thu, Feb 09, 2006 at 06:37:57PM -0800, Thomas Bushnell BSG wrote:
> Nick Phillips <[EMAIL PROTECTED]> writes:
>
> > You are of course assuming that there is some way of making an absolute
> > determination as to the DFSG-compliance of a license, when there is not.
>
On Thu, Feb 09, 2006 at 06:37:57PM -0800, Thomas Bushnell BSG wrote:
> > The vote is not a means of rescinding the DFSG or SC, nor even of
> > contradicting them. It is the *only* means we have of determining
> > whether something is in compliance with them. If a majority say that
> > that is the
On Sat, Feb 11, 2006 at 06:19:28AM -0500, Glenn Maynard wrote:
> On Fri, Feb 10, 2006 at 03:21:57PM +1300, Nick Phillips wrote:
> > The vote is not a means of rescinding the DFSG or SC, nor even of
> > contradicting them. It is the *only* means we have of determining
> > wh
On Wed, Apr 26, 2006 at 02:54:47PM -0500, Jaldhar H. Vyas wrote:
> Package: wnpp
> Severity: wishlist
> Owner: "Jaldhar H. Vyas" <[EMAIL PROTECTED]>
>
> * Package name: libkwiki-plugins-perl
> Version : 0.01
> Upstream Author : Various. Compiled by Jaldhar H. Vyas <[EMAIL PROTECTE
On Fri, May 19, 2006 at 03:46:28PM +0200, Wouter Verhelst wrote:
> That's not an issue. First, ed doesn't install an alternatives for
> "editor". Second, there's also 'by_vote', which puts vim on top.
Which is an excellent demonstration of "why we should not use popcon to
decide alternatives prio
On Mon, Jan 10, 2005 at 10:57:56PM +0100, Francesco Poli wrote:
> On Mon, 10 Jan 2005 14:25:37 +1300 Nick Phillips wrote:
>
> > The fact that we have conveniently
> > ignored this problem when dealing with the GPL and BSD licenses so far
> > does not make it go away.
>
On Tue, Jan 11, 2005 at 03:25:00AM -0800, Steve Langasek wrote:
> > Best would be (if this is allowed according to the policy) to put
> > everything under
> > /usr/share/texlive/
> > where there are
> > .../bin/-/
>
> No, this is a violation of the FHS, which is included by refere
On Tue, Jan 11, 2005 at 10:00:02PM +1100, Matthew Palmer wrote:
> > Right. And when the .deb gets distributed on its own?
>
> Then whoever does the distributing should ensure that they comply with the
> terms of the licence of the software they're distributing, just as they need
> to now (eg dist
troduced in the version
mentioned in the dependency are necessary to me or not.
If your changelog merely says "New upstream version, closes: #123 #456",
it's no help whatsoever, and I will (rightly) think that you suck.
FFS, it's a *change*log -- so log the effing changes in it.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Do not overtax your powers.
rote a module to do it at least vaguely
portably. However, once I got to the stage where it did what I needed,
I didn't have time to get it into shape to release anywhere (like CPAN).
If this sounds like what you might want, let me know & I'll dig it out
again.
Cheers,
Nick
--
en taken while developing it, which in turn
gives you rather a lot of information about what the end product is
likely to be like.
Far better than any of the alternatives suggested so far, at any rate :-P
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
It may or may not be worthwhile, but it still has to be done.
ure as hell not hardware
or firmware, so...
--
Nick Phillips -- [EMAIL PROTECTED]
You are sick, twisted and perverted. I like that in a person.
necessary
arguments (which would be standard).
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
You can rent this space for only $5 a week.
r of how important the upgrade is likely to be to users of
the package, and that the testing propagation was just a handy side-use.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Write yourself a threatening letter and pen a defiant reply.
> > As I recall, part of the idea of NEWS.Debian was to prevent having this kind
> > of information end up as debconf notes.
>
> But some people like to have this information in debconf notes. Having
> the choice between displaying them and reading them in NEWS.Debian woul
ion
in stable should not or can not be used, it should at least be considered
for update, new bugs or no.
*shrug*
--
Nick Phillips -- [EMAIL PROTECTED]
Tomorrow, you can be anywhere.
some other package
that uses one of its binaries either. What should it do when one of them
becomes obsolete -- leave it hanging around just in case?
If package B depends on something that is no longer present in package A,
package B is buggy, and needs to be updated (even if only with a ver
On Mon, Aug 01, 2005 at 06:06:27AM -0400, Yaroslav Halchenko wrote:
> On Sun, Jul 31, 2005 at 11:10:04PM +0400, Nikita V. Youshchenko wrote:
> > (1) keep vulnerable packages in stable,
> > (2) remove affected packages from distribution,
> > (3) allow new upstream into stable.
> My 1 cent would be a
On Mon, Oct 13, 2003 at 05:54:41PM -0500, John Hasler wrote:
> > No, you understood it correctly. That's exactly the point.
>
> If I can configure my domain with a list of IPs from which mail claiming to
> originate from it must come without having a static IP and without the
> cooperation of th
On Mon, Nov 25, 2002 at 10:59:29AM +1300, Philip Charles wrote:
> There are a number of us in Dunedin.
...and plenty of good cafes etc., too. :)
--
Nick Phillips -- [EMAIL PROTECTED]
You have been selected for a secret mission.
on a regular basis,
would be a good idea.
(In fact I might even "just do it").
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Live in a world of your own, but always welcome visitors.
rate-limited, source for ISOs would be
an improvement on what we currently have.
Rate-limiting the source would, if necessary, provide a disincentive to
people who would otherwise just jump in and download ISOs rather than using
Jigdo.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Fine day for friends.
So-so day for you.
orate, without permission, the unicode standard. You should
> expect to start from scratch!
Engage brain. Do you think that if I want to create a competitor to, say,
GNU Emacs, that I should expect to have to start from scratch? Or fetchmail?
Or any one of the thousands of DFSG-free packages
On Sat, Nov 30, 2002 at 11:56:59AM +0100, Josip Rodin wrote:
> On Sat, Nov 30, 2002 at 11:23:23PM +1300, Nick Phillips wrote:
> > Joy (or any of the rest of the www team) - where do you get the data
> > to put into the mirror pages on www.d.o?
>
> Well, we get it from t
On Sat, Nov 30, 2002 at 09:23:43PM +0100, Marco d'Itri wrote:
> On Nov 30, Nick Phillips <[EMAIL PROTECTED]> wrote:
>
> >I'm with Joey on this; last time I tried to find Debian .iso images, it
> >was a nightmare. In fact I couldn't find an official w
On Monday, December 9, 2002, at 06:41 am, Joel Baker wrote:
I'd honestly prefer to see the actual archive scripts (The One True
Archiving Tools, of which all others must, by definition, be
emulations)
packaged and useable by mere mortals, but the last I'd heard, this was
a
long way off, and not
On Monday, December 9, 2002, at 10:48 am, Fabio Massimo Di Nitto wrote:
I do not agree with you for different reasons. First of all noone
forces
people to add private archives to their sources.list. If users do that
they should know that things can break more easily. Sometimes private
archive are
On Monday, December 9, 2002, at 12:03 pm, Scott James Remnant wrote:
I disagree that this is needed, not for any of the usual reasons, but
for the simple reason that this functionality already exists.
In part; it's not visible to the user, and it's not possible for a
package to specify that it de
to testing (as
they will never, by our definition, be stable).
That, of course, raises another question...
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
It's all in the mind, ya know.
in case anyone out there was hovering on the verge of adopting
magicfilter... you know you want to ;)
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Do not sleep in a eucalyptus tree tonight.
hines (say a
P200MMX) would likely be unable to use such software.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
You feel a whole lot more like you do now than you did when you used to.
On Sat, Apr 26, 2003 at 09:20:33AM +1000, Matthew Palmer wrote:
> Another question, of course, is what does supporting 386s lose us? I've
Binary compatibility with other distributions & usability of 3rd-party
C++ binaries. That was what started this thread, remember?
--
N
we could
reasonably leave 486 users out in the cold in that way).
It may be relatively cheap and easy for *you* to buy a two-year-old
system, but I don't believe that in this case you are representative
of nearly enough of our users to be a useful example.
Cheers,
Nick
--
Nick Phillips -- [
On Sat, Apr 26, 2003 at 09:41:14AM +0200, Andreas Metzler wrote:
> I'd vote for 1 or
>
> 1a. create a stripped down version for i386, i.e. required/important
> and go for i486.
I'll drink to that!
--
Nick Phillips -- [EMAIL PROTECTED]
You are confused; but this is your normal state.
or meta-distribution
for older systems (with a sensible-sized libc, for example) than to
stick with a "one size fits all" approach. I just don't think that with
the quantity of Pentium-class machines out there that we've got to that
point just yet.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Give him an evasive answer.
than security updates targeted at 'testing'.
There is no denying that that would be a useful issue to overcome, but
I'm not sure I agree that it's more important than (at least some potential)
security updates to testing, let alone much more.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Avoid reality at all costs.
sts might happen.
I also don't believe that it's acceptable to break the Monotonicity Criterion.
If a winning option would be discarded due to quorum requirements, then
I think the vote should probably be considered void.
Sorry I don't have time to make much more of a contribution th
Cool name, though. Don't change that, whatever else you may end up changing.
It'd be good to be able to create something like a commented version of
the output from dpkg --get-selections so that you could say why you've
purged lynx and added w3m-ssl, for example.
Cheers,
Nick
--
proposed steps would
best lead into this kind of scenario in future, but I thought that could
wait until you've all agreed that this is a really cunning plan and
definitely the best way to do it ever. You know you want to ;)
Cheers,
Nick
P.S. I've been trying not to get involved in this thread in the hope that it
would come up with the Right Answer and go away, but...
--
Nick Phillips -- [EMAIL PROTECTED]
If you sow your wild oats, hope for a crop failure.
to muster the energy to make the small effort to subscribe to receive
notifications regarding particular packages.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Look afar and see the end from the beginning.
on: in the control file?
Because you need *a* description, and in the past there has only been one
description, so there was no reason to normalise it out into a different
object. You don't, however, need 15, and when there are 15 or however many,
it makes sense to normalise them out.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
If you think last Tuesday was a drag, wait till you see what happens tomorrow!
sense for smaller
> packages, too.
Absolutely.
--
Nick Phillips -- [EMAIL PROTECTED]
A long-forgotten loved one will appear soon.
Buy the negatives at any price.
ow when there are new
> translations?
They shouldn't need to know.
--
Nick Phillips -- [EMAIL PROTECTED]
Excellent day for putting Slinkies on an escalator.
On Wed, Sep 05, 2001 at 10:41:53AM +0200, Christian Kurz wrote:
> On 01-09-04 Nick Phillips wrote:
> > On Tue, Sep 04, 2001 at 09:06:04PM +0200, Michael Bramer wrote:
> > I don't expect most maintainers to be able or inclined to keep track of
> > a shedload of different t
gt; no, it does not store there. And I can explain it:
Well, shouldn't it? Wouldn't it make sense to have the translated description
in there rather than the original one?
--
Nick Phillips -- [EMAIL PROTECTED]
Slow day. Practice crawling.
tell it which local is used by the file at load time, either manually or
by the use of metadata in/around the file.
--
Nick Phillips -- [EMAIL PROTECTED]
Think twice before speaking, but don't say "think think click click".
file? Why not just make available
(either in the package, or elsewhere, depending on the means by which the
package is to be distributed, and the maintainer's knowledge and inclination)
the translations for the whole package in one place?
Cheers,
Nick, who is waiting for someone to tell him he&#
ons" in the same language. I can
think of at least one way in which this could be useful.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Someone whom you reject today, will reject you tomorrow.
On Thu, Sep 06, 2001 at 01:08:25PM +0200, Christian Kurz wrote:
> On 01-09-05 Nick Phillips wrote:
> > The translation of any part of a package, be it the text of error messages,
>
> So, shall we now remove all .po files and other translation from
> upstream packages because th
we can't cater for all types of
maintainer.
--
Nick Phillips -- [EMAIL PROTECTED]
You will feel hungry again in another hour.
a particular package has a translation made available.
There is a difference between "not requiring a maintainer to be involved in
the provision of translations" and "not enabling a maintainer to be involved
in the provision of translations".
--
Nick Phillips -- [EMAIL PROTECTED]
Fine day to work off excess energy. Steal something heavy.
iner who wanted to know.
If some third party at some random site provides a translation archive,
then it's up to them whether they tell you or not. That doesn't mean that
we shouldn't provide a mechanism for them to do so.
It's free software after all. That means that if so
someone to write it up and/or
stick the tools we use for creating CDs up somewhere.
Hugo; you're probably doing it slightly differently - might be cunning
to compare notes once you've done it & see where we've done things
differently...
Cheers,
Nick
--
Nick Phillips -- [EMAI
n
> above.
2 aliases, "english" for the English, "american" for the Americans.
--
Nick Phillips -- [EMAIL PROTECTED]
People are beginning to notice you. Try dressing before you leave the house.
ricans speak is
different to what the English speak. Therefore the Americans don't speak
English.
Simple as that ;) I am however prepared to let it go in the interest of
avoiding a pointless flamewar. Happy to continue by private mail, though.
Limited offer, for a short time only...
--
Nick Phillips -- [EMAIL PROTECTED]
You've been leading a dog's life. Stay off the furniture.
does not in turn mean
that my assertion that English is by definition the language spoken by the
English is incorrect.
I also implied that it'd be rather more cunning to argue the toss about this
off-list than on. Still, you can't win 'em all...
--
Nick Phillips -- [EMAIL PROTECTED]
You
the bit in between (and
in particular the apparent repetition) that worries me.
It all appears to work OK, but those messages worry me.
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
You will be reincarnated as a toad; and you will be much happier.
On Fri, Sep 14, 2001 at 12:11:52PM -0400, Matt Zimmerman wrote:
> On Fri, Sep 14, 2001 at 03:53:26PM +0100, Nick Phillips wrote:
>
> > I wonder whether anyone can point me at a likely cause for a slightly
> > worrying list of messages I'm getting from dpkg-source when usin
really.
Cheers,
Nick "not a pedant" Phillips
--
Nick Phillips -- [EMAIL PROTECTED]
It's lucky you're going so slowly, because you're going in the wrong direction.
difference between a "nation" and a "country", too.
Point being, if most of us don't have a clue where we belong to, how should
the ISO or anyone else be expected to get it right?
Cheers,
Nick
(mix up a chunk of English with a bit of Welsh, lay a veneer of British
over th
don't think they have sources. Although I may
be wrong...
I'll try to remember to check it out (won't be 'til next week, as we're
moving offices this weekend - feel free to hassle me about it on Monday).
Cheers,
Nick
--
Nick Phillips -- [EMAIL PROTECTED]
Good news. Ten weeks from Friday will be a pretty good day.
een and 4MB RAM. Slink was the *only*
linux I could get onto it. I used a floppy boot & PLIP install.
That's what got me started on Debian.
What fails on yours?
--
Nick Phillips -- [EMAIL PROTECTED]
Caution: Keep out of reach of children.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ion and
transfer everything to and from signing by sneakernet", "I use some kind
of hardware dongle to hold it" etc.
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
anges; upgrading to systemd - however wonderful it is (and
I confess to having no opinion on that) - without at least a debconf
prompt of a reasonable priority telling them what is about to happen and
offering a bailout, is guaranteed to lose us reputation and users.
It doesn't matter whether we think that's reasonable or not, it is what
will happen.
So, is it actually feasible to provide such a prompt?
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
me that "Valid-Until" was a mistake in the first place; the
date on which it was signed and the frequency with which it is expected
to be re-signed are needed (whether this information is in the file
itself or just in the docs), and it's up to the client to decide how old
is
ong description here.)
>
> Please provide a suitable long description so that we can review it. I
> personally also prefer to not start the synopsis with a capital letter.
FWIW Python as a proper noun gets a capital letter no matter where it is
in a sentence. There's nothing wron
t HTTPretty is going to be there for me, but it
would be more helpful to tell me what this package actually does.
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
iew of these situations I created
> myself the diffstats page:
> http://backports.debian.org/wheezy-backports/overview/
And if the newer version, for example, has updated a database schema in
a non-backward-compatible way?
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
o reason not to do it - you're still better off than
you were before (equally weak, but with the potential to improve).
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
correct deps on their packages, and -dev package users to
ensure they are aware of which features of a library need extra
packages installed in order to function.
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
d that
system-wide configuration of this might be desirable.
Am I missing something? Thoughts?
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
get on to that, can
anyone clarify how/whether they integrate with systemd?
Cheers,
Nick
--
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago
86 matches
Mail list logo
