On Tue, 12 Apr 2011 at 09:33:25 +1000, Brian May wrote:
> Am thinking the best solution might be to wrap the entire ntlm_service
> function with the same #if __APPLE__ ... #endif, as that appears to be the
> only reference to ntlm_service, and I think the static definition means it
> can't be refer
Hi there!
On Sun, 10 Apr 2011 19:54:33 +0200, Torsten Werner wrote:
> Am -10.01.-28163 20:59, schrieb Mehdi Dogguy:
>> can't this limit to 2009 be pushed further? what would be the difference
>> if we consider 2010, or 2011? (Just want to see the impact).
>
> 800 packages would be affected if the
On 8 April 2011 20:11, Simon McVittie wrote:
> You can work around it with -Wl,--add-needed in LDFLAGS, or fix it properly
>
by including -lheimntlm in the LIBADD/LDADD for whatever you're linking.
Thanks. Thought this might be the case.
However, that doesn't explain why it magically when comp
* Torsten Werner , 2011-04-11, 21:03:
3. These packages are non-free, non-auto-buildable, and have no RC bug
filed:
amiwm dgen libapache-mod-fastcgi lmbench nttcp q-tools sgb teamspeak-server
I was aware of some of them but thanks for the update.
If we remove old binaries, they'll migrate t
Barry Warsaw wrote:
>On Apr 09, 2011, at 01:38 PM, Scott Kitterman wrote:
>
>>We've treated python and python3 as separate runtime environments. We
>also
>>have a default python3 (just in the middle of transitioning to 3.2).
>The
>>only meaningful change that would make python3 the 'default pyt
On Apr 09, 2011, at 01:38 PM, Scott Kitterman wrote:
>We've treated python and python3 as separate runtime environments. We also
>have a default python3 (just in the middle of transitioning to 3.2). The
>only meaningful change that would make python3 the 'default python' is if we
>pointed /usr/b
Package: wnpp
Severity: wishlist
Owner: hennr
* Package name: flare
Version : 0.12
Upstream Author : Clint Bellanger <>
* URL : http://clintbellanger.net/rpg/
* License : (GPL, CC-BY-SA)
Programming Lang: (C++)
Description : Flare (Free/Libre Action Ro
Am -10.01.-28163 20:59, schrieb Jakub Wilk:
> 1. These packages were uploaded recently:
>
> altree guile-cairo nyquist
>
> How about giving maintainers/autobuilders a little more time?
>
> 2. libmowgli is in the middle of a transition, and there are still some
> reverse dependencies of its old v
Am -10.01.-28163 20:59, schrieb Mark Hymers:
> Torsten, do you think we should add this to the cruft-report output?
> Maybe using a two year cut off or something (entirely arbitrary) so that
> they'd be listed at http://ftp-master.debian.org/cruft-report-daily.txt ?
Why not. It would be a good exe
With the transition to /run and /run/lock as tmpfs filesystems, it
would be desirable to provide sensible default size limits. Currently,
we default to the tmpfs default of ½ RAM. But with several tmpfs
filesystems, this does have the potential for the system to be OOMed
by a user filling up more
Hi all,
got the same bug also with kernel 2.6.38-2-amd64.
Just for info.
Hans
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201104111821.18762.hans.ullr...@loop.de
Le lundi 11 avril 2011 à 13:18 +0200, Michelle Konzack a écrit :
> I think, DI has to support a Fast-Install-Option for Desktop and Server
> where the first one installs NM by default and the second one IFUPDOWND.
This is what is already done for squeeze.
If OTOH we get d-i to run NM natively,
On Sun, Apr 10, 2011 at 11:58:09AM +0200, Goswin von Brederlow wrote:
> Bastian Blank writes:
> > On Sun, Apr 10, 2011 at 02:18:49AM +0200, Goswin von Brederlow wrote:
> >> Here I think we can go one of two ways:
> >> 2) "bootstrap" scripts are only executed after the owners (Pre-)Depends
> >> hav
On Mon, 11 Apr 2011, peasth...@shaw.ca wrote:
> > ... not all that complexity has to be exposed by default.
>
> Yes, needless complexity in an algorithm reduces efficiency
> in execution. Needless complexity in an interface reduces
> efficiency in use.
http://www.psychologytoday.com/blog/one-a
Adam Borowski writes:
> On Sat, Apr 09, 2011 at 11:42:12PM +0200, Bastian Blank wrote:
>> On Fri, Apr 08, 2011 at 06:52:41PM +0200, Bastian Blank wrote:
>> > We have the same problem with awk since ages. We should fix both
>> > problems together. Therefor I propose the following:
>>
>> - An esse
Lars Wirzenius writes ("Re: System users: removing them"):
> Thus, I propose to change 9.2.2 "UID and GID classes", the paragraph on
> uids in the range 100-999, to add the following sentence to the end of
> the paragraph:
>
> Packages must not remove system users and groups they have
>
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: python-iview
Version : 0.2
Upstream Author : Jeremy Visser
* URL : http://jeremy.visser.name/2009/08/30/python-iview/
* License : GPL
Hello Jon Dowland,
Am 2011-04-11 12:02:09, hacktest Du folgendes herunter:
> And you wouldn't be - because, once again - you are not forced to use whatever
> the default solution is, you have the freedom to switch to another, just like
> people who currently *do* use network-manager have taken adv
Hello Jon Dowland,
Am 2011-04-11 10:37:54, hacktest Du folgendes herunter:
> On Thu, Apr 07, 2011 at 02:11:38PM +0200, Michelle Konzack wrote:
> > Installing NM by default will break systems which where running the last
> > 12 years without flaws.
> No, it will not. It will not impact *running* s
On Thu, Apr 07, 2011 at 02:18:38PM +0200, Michelle Konzack wrote:
> This is Exacly what I mean with NM. I do not wan to be bothered with
> reading some hours documentations on how to tweek NM to work with my
> four 10GE NICs.
And you wouldn't be - because, once again - you are not forced t
On Thu, Apr 07, 2011 at 02:11:38PM +0200, Michelle Konzack wrote:
> Installing NM by default will break systems which where running the last
> 12 years without flaws.
No, it will not. It will not impact *running* systems at all. It will only
impact newly installed systems.
--
To UNSUBSCRIBE, e
On 04/10/2011 09:22 PM, Colin Tuckley wrote:
>> (Although, now that I think about it, it's probably hard for alpha to be
>> considered a viable architecture, unless there is new hardware being
>> produced and sold.)
>
> There needs to be enough reliable hardware available to maintain the
> port. W
22 matches
Mail list logo
