On Sat, Jul 6, 2013 at 2:03 AM, Steve Langasek wrote:
> Control: severity 715110 normal
> Control: severity 715122 normal
>
> On Sat, Jul 06, 2013 at 05:01:15AM +, David Steele wrote:
>> Package: libsamba-util-dev
>> Version: 4.0.0~beta2+dfsg1-3.2
>> Severity: serious
>> User: debian...@lists.
On Sat, Jul 6, 2013 at 04:10:16 -0400, Dave Steele wrote:
> I guess the next step is a clearer statement of consensus on what to do next.
>
> My position - I believe that the bug submittal, and the current
> severity, is appropriate.
>
> I will make changes should consensus dictate. (I may need
Hi all,
I try to fix a problem in installation of dotclear package but there's
seems to be a problem with apache configuration files :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709960
I can reproduce piuparts warnings but didn't find a solution.
If anyone understand the problem and know h
On 07/06/2013 02:14 AM, Philipp Kern wrote:
On 2013-07-05 17:38, Uoti Urpala wrote:
The reason I replied wasn't so much to comment on the historical
licensing of the kernel (it's old enough to not matter much now
anyway), but to comment on the legal argument that was the core of
Linus's post
On 03/07/13 14:30, Ian Jackson wrote:
> Ian Jackson writes ("Re: boot ordering and resolvconf"):
>> 4. Therefore in most installations there should be a local
>>proxy or cache. It should use DHCP-provided, PPP-provided or
>>similar, as a forwarder. The local DNS provider addr
* Philipp Kern:
> On 2013-07-04 10:04, Florian Weimer wrote:
>> * Stefano Zacchiroli:
>>> I mean, sure, it *is* more tricky to provide such a URL for users that
>>> will be running a *modified* version of INN. But it is exactly the
>>> same
>>> kind of difficulties that people distributing modifie
Julien Cristau wrote:
> On Thu, Jun 13, 2013 at 14:51:43 +0200, Matthias Klose wrote:
>
> > Am 07.05.2013 15:25, schrieb Matthias Klose:
> > > The decision when to make GCC 4.8 the default for other
> > > architectures is left to the Debian port maintainers.
> > [...]
> > > Information on porting
Package: wnpp
Severity: wishlist
Owner: Benjamin Drung
* Package name: adblockedge (binary: xul-ext-adblock-edge)
Version : 2.0.4
Upstream Author : adstomper
* URL : https://bitbucket.org/adstomper/adblockedge/
* License : MPL-2.0
Programming Lang: JavaScript
* Stefano Zacchiroli [130704 09:24]:
> I mean, sure, it *is* more tricky to provide such a URL for users that
> will be running a *modified* version of INN. But it is exactly the same
> kind of difficulties that people distributing modified copylefted
> software will have to face to uphold GPL (or
On Sat, Jul 6, 2013 at 5:48 AM, Julien Cristau wrote:
> On Sat, Jul 6, 2013 at 04:10:16 -0400, Dave Steele wrote:
>
>> I guess the next step is a clearer statement of consensus on what to do next.
>>
>> My position - I believe that the bug submittal, and the current
>> severity, is appropriate.
>
Package: wnpp
Severity: wishlist
Owner: "Andrew Starr-Bochicchio"
* Package name: fonts-junction
Version : 18de8417c6 [1]
Upstream Author : Caroline Hadilaksono
* URL : http://www.theleagueofmoveabletype.com/junction
* License : SIL
Programming Lang: N/A
Hi Dave,
On Samstag, 6. Juli 2013, Dave Steele wrote:
> The consensus aspect of that is honestly not clear to me. I came into
> this thinking that the discussion is about what Policy dictates, and
> the consensus is on what the Policy calls for, based on my reading of
> the background documentatio
On Sat, Jul 06, 2013 at 04:10:16AM -0400, Dave Steele wrote:
> On Sat, Jul 6, 2013 at 2:03 AM, Steve Langasek wrote:
> > "serious" when there's a grand total of 0 packages that use this -dev
> > package for linking against the library? Not hardly.
> > I think this severity: serious mass-bug fil
* Howard Chu:
> LMDB doesn't need dirty tricks to look good. (And at only 6KLOCs of
> source, there's nowhere to hide any tricks anyway.)
Okay, I found a snag: the 511 bytes limit on the key size. Berkeley
DB's disk format does not impose a limit on key or value size (at
least for B-trees). For
Florian Weimer wrote:
* Howard Chu:
LMDB doesn't need dirty tricks to look good. (And at only 6KLOCs of
source, there's nowhere to hide any tricks anyway.)
Okay, I found a snag: the 511 bytes limit on the key size. Berkeley
DB's disk format does not impose a limit on key or value size (at
le
On Sat, Jul 6, 2013 at 3:34 PM, Holger Levsen wrote:
> Hi Dave,
>
> ...please do as suggested already and downgrade those bugs to normal ...
>
>
OK, I have downgraded those bugs remaining unresolved as normal.
--
"Le mieux est l'ennemi du bien" - Voltaire
--
To UNSUBSCRIBE, email to debian-de
On Friday and Saturday I sent messages to this list but they
appear to have been filtered out. I try again and CC:
Helmut Grohne this time so at least he will receive this
message and we can continue the discussion over e-mail.
My Friday message contained a C program and its output
when run on my
17 matches
Mail list logo
