Hello,
On Tue, 1 May 2012 23:03:38 +0200
Philipp Kern wrote:
> > I wonder why many people in this thread still don't understand this.
> > And also I can't see why some find this annoying behaviour or
> > something wrong. There's absolutely nothing wrong with what it does
> > now, as re-encoding
Hi again,
Steve Langasek wrote:
> [Dropped Cc; what does any of this have to do with the DPL?]
I was alerting him to a conversation that was going nowhere fast,
in the hope that he might use his power to
participate in discussions amongst the Developers in a helpful
way
It has
Le Tue, May 01, 2012 at 05:22:34PM -0700, Russ Allbery a écrit :
>
> See, for example, the --help output of any recent configure script:
>
> | Some influential environment variables:
> | CC C compiler command
> | CFLAGS C compiler flags
> | LDFLAGS linker flags, e.g. -L if
On Wed, May 2, 2012 at 8:27 AM, Charles Plessy wrote:
> I actually question if we need our current level of division, which is already
> lower than in other distributions.
Your question seems more appropriate on debian-project.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE,
Excerpts from Ben Hutchings's message of Sun Apr 29 16:27:54 -0700 2012:
> On Sun, Apr 29, 2012 at 11:11:08PM +0200, Svante Signell wrote:
> > On Sun, 2012-04-29 at 21:52 +0100, Ben Hutchings wrote:
> > > On Sun, Apr 29, 2012 at 09:51:37PM +0200, Svante Signell wrote:
> > > > Hello,
> > > >
> > >
Patrick Ouellette writes:
> Of course the #! line is not the issue. The issue is two upstream
> maintainers separated by years and miles selected the same generic name
> for their binary file.
I agree with this.
> Compounding the issue, some Debian Maintainer seeking to better the
> project by
On Tue, May 01, 2012 at 03:24:58PM -0700, Russ Allbery wrote:
> Date: Tue, 01 May 2012 15:24:58 -0700
> From: Russ Allbery
> Subject: Re: [Pkg-javascript-devel] Node.js and it's future in debian
> To: debian-devel@lists.debian.org
>
> Patrick Ouellette writes:
> > On Sat, Apr 28, 2012 at 08:39:
On Tue, May 01, 2012 at 10:36:58PM +0200, Svante Signell wrote:
> On Mon, 2012-04-30 at 20:30 +0200, Vincent Bernat wrote:
> > OoO En ce doux début de matinée du lundi 30 avril 2012, vers 08:15,
> > Svante Signell disait :
> >
> > >> I'm rather sure that he wants to define booting as part of
On 2012-05-01 18:55:20 +0300, Riku Voipio wrote:
> On Tue, May 01, 2012 at 12:48:10AM -0400, Chris Knadle wrote:
> > I think it would be useful to describe what issue(s) there are concerning
> > 8BITMIME and why this is important. I've found some information [1] about
> > this, but it isn't clea
On Tue, May 01, 2012 at 07:47:08PM +0100, Roger Lynn wrote:
> I have enabled accept_8bitmime in every exim I've installed for the last
> 10 years and no one has reported any problems. I think the risk of
> encountering a truly 7 bit MTA in this decade is low enough to be
> ignored for most purposes
Jonas Smedegaard writes:
> * Package name: gesftpserver
> Version : 0.1
> Upstream Author : Richard Kettlewell
> * URL : https://github.com/ewxrjk/sftpserver
> * License : GPL-2+
> Programming Lang: C
> Description : sftp server submodule for OpenSSH
>
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
* Package name: gesftpserver
Version : 0.1
Upstream Author : Richard Kettlewell
* URL : https://github.com/ewxrjk/sftpserver
* License : GPL-2+
Programming Lang: C
Description : sftp server submod
Hi again,
I actually question if we need our current level of division, which is already
lower than in other distributions. How often do people enable contrib without
non-free ? Doing so would be to install packages such as the ones discussed
every year on that list, which do not trigger install
Charles Plessy writes:
> This said, the point that I want to make, is that we switched from a
> situation where the actual communication channel between our and
> upstreams makefile was C(XX)FLAGS, to a situation where CPPFLAGS and
> LDFLAGS also got some data input in by our toolchain. If there
Le Mon, Apr 30, 2012 at 03:46:51PM -0700, Russ Allbery a écrit :
>
> Most C programs use Autoconf in my experience. I know that scientific
> software often doesn't, but I think scientific software is the significant
> outlier in that respect.
I see... That probably explains everything. My expe
* Patrick Ouellette [2012-05-01 16:55 -0400]:
> I was under the impression that neither package was going to move forward with
> a binary named "node"
Some proposed this, some agreed, others did not.
In the just reported bug #671120 I wrote regarding this neither package
should get the name part
On Tue, May 01, 2012 at 01:07:11AM +0200, Carsten Hey wrote:
> Date: Tue, 1 May 2012 01:07:11 +0200
> From: Carsten Hey
> Subject: Re: Node.js and it's future in debian
> To: debian-devel@lists.debian.org
> Mail-Followup-To: Carsten Hey ,
> debian-devel@lists.debian.org
>
> * Carl Fürstenberg [
Patrick Ouellette writes:
> On Sat, Apr 28, 2012 at 08:39:41PM +0200, Jonas Smedegaard wrote:
>> Node.js is becoming quite popular and is known generally to use "node"
>> in its hash-bang.
> Seriously? People are writing scripts that start
> #!node
The #! part is really not the issue, since th
On Sat, Apr 28, 2012 at 08:39:41PM +0200, Jonas Smedegaard wrote:
> Node.js is becoming quite popular and is known generally to use "node"
> in its hash-bang.
Seriously? People are writing scripts that start
#!node
That is truely messed up!
Pat
--
,
On Fri, Apr 27, 2012 at 08:26:47PM -0700, Russ Allbery wrote:
>
> > Contrast that with the positive actitude of the NFS developers of CITI
> > at UMichi when heimdal-dev and libgssapi-dev both contained
> > /usr/lib/libgssapi.a [1]. They went to the trouble of renaming libgssapi
> > to libgssglue.
Package: wnpp
Severity: wishlist
Owner: Raoul Snyman
* Package name: openlp
Version : 1.9.9
Upstream Author : Raoul Snyman
* URL : http://openlp.org/
* License : GPL
Programming Lang: Python
Description : OpenLP is an open source church worship present
[Dropped Cc; what does any of this have to do with the DPL?]
On Tue, May 01, 2012 at 04:32:49PM -0500, Jonathan Nieder wrote:
> Steve Langasek wrote:
> > On Tue, May 01, 2012 at 03:30:50PM -0500, Jonathan Nieder wrote:
> >> Wait, really? What happened to respect by maintainers for the
> >> proje
Patrick Ouellette writes:
> On Fri, Apr 27, 2012 at 08:26:47PM -0700, Russ Allbery wrote:
>> Indeed, and I'm very grateful for that. But realistically that was
>> also a lot easier than renaming Node.js's interpreter, and I think the
>> CITI folks did actually know that was coming. The conflict
On Sat, Apr 28, 2012 at 03:31:02AM +0200, Carl Fürstenberg wrote:
>
> There has been an log struggle between the nodejs package and the node
> package, which is still unresolved (bug #611698 for example) And I
> wonder now what the future should look like.
>
> To summarize the problem:
> * the no
Steve Langasek wrote:
> On Tue, May 01, 2012 at 03:30:50PM -0500, Jonathan Nieder wrote:
>> Wait, really? What happened to respect by maintainers for the
>> project?
>
> "The project" is not "a set of random maintainers who have a filename
> conflict with you".
Sorry, I don't understand the abov
On Tue, May 01, 2012 at 09:30:23PM +0200, Andrew Shadura wrote:
> Hello,
>
> On Tue, 1 May 2012 20:18:07 +0200
> Philipp Kern wrote:
>
> > So just stop Postfix doing the conversion? Or teach Exim to announce
> > 8BITMIME by default.
>
> No, Exim should not announce 8BITMIME, or it will violate
On Tuesday, May 01, 2012 11:55:20, Riku Voipio wrote:
> On Tue, May 01, 2012 at 12:48:10AM -0400, Chris Knadle wrote:
...
> > The quoted 2010 survey [2] showed Exim was the most popular MTA (which I
> > found surprising), deployment of Exim growing just slightly faster than
> > Postfix, and everyth
On 27/04/12 19:33, Tollef Fog Heen wrote:
> ]] Martin Wuertele
>
>> * Josselin Mouette [2012-04-27 09:53]:
>>
>>> Le jeudi 26 avril 2012 à 22:29 +0200, Svante Signell a écrit :
> Yes of course, because event-driven init systems have *always* been
> *only* about mounting USB devices.
>>
On Tue, May 01, 2012 at 09:30:23PM +0200, Andrew Shadura wrote:
> On Tue, 1 May 2012 20:18:07 +0200
> Philipp Kern wrote:
>
> > So just stop Postfix doing the conversion? Or teach Exim to announce
> > 8BITMIME by default.
>
> No, Exim should not announce 8BITMIME, or it will violate RFC, not
>
On Tue, May 01, 2012 at 03:30:50PM -0500, Jonathan Nieder wrote:
> > I was talking about a consensus among the maintainers of the affected
> > packages. Even if all but the maintainers of one of the affected
> > packages would agree to a solution, there would be no way to implement
> > this soluti
On Mon, 2012-04-30 at 20:30 +0200, Vincent Bernat wrote:
> OoO En ce doux début de matinée du lundi 30 avril 2012, vers 08:15,
> Svante Signell disait :
>
> >> I'm rather sure that he wants to define booting as part of what
> >> currently is done in /etc/rcS.d. Configuring the network or mo
Carsten Hey wrote:
> I was talking about a consensus among the maintainers of the affected
> packages. Even if all but the maintainers of one of the affected
> packages would agree to a solution, there would be no way to implement
> this solution without asking the tech-ctte or (what would be not
* Jonathan Nieder [2012-05-01 12:57 -0500]:
> Carsten Hey wrote:
>
> > I don't think that there ever will be a consensus in all those
> > discussions without discussing in a reasonable way (which failed in the
> > past multiple times).
>
> Note that a consensus does not imply everyone agreeing.
I
Hello,
On Tue, 1 May 2012 20:18:07 +0200
Philipp Kern wrote:
> So just stop Postfix doing the conversion? Or teach Exim to announce
> 8BITMIME by default.
No, Exim should not announce 8BITMIME, or it will violate RFC, not
otherwise. Now it doesn't announce it, but accepts, so RFC-compliant
MUA
On 01/05/12 15:10, Chris Knadle wrote:
> I think the reason Exim does not do this protocol conversion is that from the
> point of view of an MTA author, the point of an MTA is to transmit the body
> of
> the message without any modification to it once received, and body
> modification would be
On Tue, May 01, 2012 at 06:55:20PM +0300, Riku Voipio wrote:
> It's both extra traffic (not that much if western encodings) and extra
> cpu work. In lesser annoyance, it means that you no longer can read
> mailbox files with non-mime capable readers (for example less) with ease,
> as there will be
Carsten Hey wrote:
> I don't think that there ever will be a consensus in all those
> discussions without discussing in a reasonable way (which failed in the
> past multiple times).
Note that a consensus does not imply everyone agreeing. I am starting
to see a consensus already and would welcome
Carsten Hey writes:
> The origin of what the policy suggests to do if there is no consensus is
> a mail from Guy Maor <879142cjni@slip-61-16.ots.utexas.edu>, in
> which he writes:
> | That's basically a stick to force developers to reach a consensus.
> Christian Schwarz uploaded this change
On Tuesday, May 01, 2012 06:55:20 PM Riku Voipio wrote:
...
> Honesstly. my grievance is really just having to convert things to 7bit.. s
...
In the future, you're likely to still be stuck doing this for other 'fun'
reasons. The one I ran into recently was that 8 bit -> 7 bit conversions will
br
* Carsten Hey [2012-05-01 01:07 +0200]:
> Only Hamish, who did not respond to this issue, uploaded
> node once in 2005,
I need to correct myself, Hamish replied once. In
<20110208230458.ga23...@risingsoftware.com> he wrote:
| I think renaming the node binary to axnode is reasonable and
| consiste
David Bremner writes:
> "Bernhard R. Link" writes:
>> My suggestion to everyone feeling the need to tell anyone on a public
>> mailing list that they should shut up because they are no contributors
>> is thus: Please refrain from any more posts to this discussion.
> I have nothing against this
On Tue, May 01, 2012 at 12:48:10AM -0400, Chris Knadle wrote:
> I think it would be useful to describe what issue(s) there are concerning
> 8BITMIME and why this is important. I've found some information [1] about
> this, but it isn't clear what problems are actially *caused* by the lack of
> 8
On Tuesday, May 01, 2012 04:53:03, Philipp Kern wrote:
> On Tue, May 01, 2012 at 12:48:10AM -0400, Chris Knadle wrote:
> > I think it would be useful to describe what issue(s) there are concerning
> > 8BITMIME and why this is important. I've found some information [1]
> > about this, but it isn't
Aron Xu writes:
> On Mon, Apr 30, 2012 at 22:21, Goswin von Brederlow wrote:
>> Aron Xu writes:
>>
>>> But what if I endianness does matters for those gettext .mo files?
>>> Installing them as libfoo-translations-be and libfoo-translations-le
>>> will need some change in gettext support of thos
"Bernhard R. Link" writes:
> My suggestion to everyone feeling the need to tell anyone on a public
> mailing list that they should shut up because they are no contributors
> is thus: Please refrain from any more posts to this discussion.
I have nothing against this principle, and I do this. But
Package: wnpp
Severity: wishlist
Owner: Ritesh Raj Sarraf
* Package name: robojournal
Version : 0.2
Upstream Author : Will Kraft
* URL : http://sf.net/projects/robojournal
* License : GPL
Programming Lang: C++
Description : cross-platform journal/diary
* Russ Allbery [120430 19:11]:
> I want our technical discussions to be welcoming to anyone who has
> information to share and who can bring additional clarity and insight to
> the discussion. But once things start getting heated or people start
> throwing around accusations or verge towards pers
On Mon, Apr 30, 2012 at 02:00:15PM -0300, Fernando Lemos wrote:
> On Mon, Apr 30, 2012 at 12:50 PM, Roger Leigh wrote:
> > On Mon, Apr 30, 2012 at 12:04:32PM -0300, Fernando Lemos wrote:
> >> On Mon, Apr 30, 2012 at 11:57 AM, Thomas Goirand wrote:
> >> > On 04/30/2012 04:56 AM, Fernando Lemos wro
* Charles Plessy [120430 16:26]:
> If people who are interested by improving our dozens of thousands upstream
> makefiles could spend time forwarding patches upstream by themselves, that
> would be appreciated. I have a hard time finding convincing words when I
> think
> the patch is borderline
On Tue, May 01, 2012 at 12:48:10AM -0400, Chris Knadle wrote:
> I think it would be useful to describe what issue(s) there are concerning
> 8BITMIME and why this is important. I've found some information [1] about
> this, but it isn't clear what problems are actially *caused* by the lack of
> 8
50 matches
Mail list logo
