On Mon,24.May.10, 09:24:31, Celejar wrote:
> On Tue, 25 May 2010 00:26:57 +1200
> Chris Bannister wrote:
> > Aaaah! what about the bloat added to the packages.gz file? You can find
> > the functionality by "apt-cache show radeontool", but I agree it should
> > be a suggests.
>
> When doing an u
On Tue, 25 May 2010 00:26:57 +1200
Chris Bannister wrote:
> On Sun, May 23, 2010 at 04:39:49PM -0400, Celejar wrote:
> > On Sun, 23 May 2010 23:20:45 +0300
> > Andrei Popescu wrote:
> > > An interesting proposal a while ago was to be able to add some more
> > > information to Suggests:, somethi
> And I massume people read manuals or similar
> before making big steps toward unstable or
> testing versions.
I didn't read even ONE manual, it was just too boring
at stable, after few weeks in testing I just got bored...
perhaps I will get bored before August and then I will
use experimental...
On Sun, May 23, 2010 at 04:39:49PM -0400, Celejar wrote:
> On Sun, 23 May 2010 23:20:45 +0300
> Andrei Popescu wrote:
> > An interesting proposal a while ago was to be able to add some more
> > information to Suggests:, something like:
> >
> > Package: acpi-support
> > Suggests: radeontool (back
> Understood. But what I meant was that an awful lot of people could
> potentially be hit by this, even if they're installing recommends,
> which they'd probably assume should take care of this.
>
> Of course. I was just suggesting that a more precise and consistent
> definition of 'recommends'
On Sun, 23 May 2010 23:20:45 +0300
Andrei Popescu wrote:
> On Sun,23.May.10, 14:53:04, Celejar wrote:
>
> > > Both are excelent examples :) But even if you disagree with the
> > > maintainer, in the end Debian is a do-ocracy. That is, the one who does
> > > the job usually gets to decide how
On Sun,23.May.10, 14:53:04, Celejar wrote:
> > Both are excelent examples :) But even if you disagree with the
> > maintainer, in the end Debian is a do-ocracy. That is, the one who does
> > the job usually gets to decide how it's done ;)
>
> Of course. I was just suggesting that a more prec
On Fri, 21 May 2010 22:12:20 +0300
Andrei Popescu wrote:
> On Fri,21.May.10, 14:43:47, Celejar wrote:
>
> > But I've long found the 'recommends' concept to be somewhat tricky and
> > perhaps to vary from maintainer to maintainer. For example, mesa-utils
> > needs GLX, which, practically speaki
* On 2010 21 May 17:30 -0500, Thomas Pircher wrote:
> Boyd Stephen Smith Jr. wrote:
> >> a) without asking me,
> >> b) without telling me and
> >> c) without being told to do so.
> >
> > From what I understand, all 3 of these are primary goals of the network-
> > manager package.
>
> I'm sure netw
Boyd Stephen Smith Jr. wrote:
>> a) without asking me,
>> b) without telling me and
>> c) without being told to do so.
>
> From what I understand, all 3 of these are primary goals of the network-
> manager package.
I'm sure network-manager will live up to its goals, eventually. For the time
being
On Fri,21.May.10, 14:43:47, Celejar wrote:
> But I've long found the 'recommends' concept to be somewhat tricky and
> perhaps to vary from maintainer to maintainer. For example, mesa-utils
> needs GLX, which, practically speaking, means that you need
> libgl1-mesa-dri. The maintainer refuses to
On Fri, 21 May 2010 13:51:45 -0400
Jordan Metzmeier wrote:
...
> The IRC bot in #debian has this to say about "why recommends":
>
> From lenny onwards, apt-get and aptitude both install "Recommended"
> packages by default. From section 7.2, Recommends, "declares a
> strong, but not absolut
> -Original Message-
> From: Andrei Popescu [mailto:andreimpope...@gmail.com]
> Sent: Friday, 21 May, 2010 00:22
> To: debian-user@lists.debian.org
> Subject: Re: Unable to connect to my home wireless
>
> On Thu,20.May.10, 15:13:35, James Zuelow wrote:
>
&
Please correct me if I'm wrong, but I believe you don't actually set
preferences to install recommends. This is now the Debian default. You have
to explicitly turn them off if you don't want them.
To avoid this, you should place these lines in /etc/apt/apt.conf:
APT::Install-Recommends "0"
> So while Thomas could file a bug, I don't think it's not
> germane to complain about DDs putting everything under the
> sun into a dependency list. Here's the place for the
> community to decide whether we really need to force an
> install of network-manager (or avahi) when they're not real
On 05/21/2010 10:45 AM, Boyd Stephen Smith Jr. wrote:
On Friday 21 May 2010 03:53:57 Thomas Pircher wrote:
What I got really angry about is that network-manager (or some other
packet; I will investigate tonight and file a bug) reconfigured my network
on-the-fly
a) without asking me,
b) with
On Friday 21 May 2010 03:53:57 Thomas Pircher wrote:
> What I got really angry about is that network-manager (or some other
> packet; I will investigate tonight and file a bug) reconfigured my network
> on-the-fly
>
> a) without asking me,
> b) without telling me and
> c) without being told to do
Andrei Popescu wrote:
> I'm not very familiar with network-manager (a.k.a network-mangler)
> because I prefer wicd, but I recall there was a setting for it to not
> touch the network if it was configured in /etc/network/interfaces. That
> setting is probably not on by default :(
I will hopefully f
Andrei Popescu wrote:
> I'm not very familiar with network-manager (a.k.a network-mangler)
> because I prefer wicd, but I recall there was a setting for it to not
> touch the network if it was configured in /etc/network/interfaces. That
> setting is probably not on by default :(
I will hopefully f
On Fri,21.May.10, 11:57:41, Andrei Popescu wrote:
> On Fri,21.May.10, 09:53:03, Thomas Pircher wrote:
> >
> > What I got really angry about is that network-manager (or some other
> > packet; I will investigate tonight and file a bug) reconfigured my network
> > on-the-fly
> >
> > a) without askin
Andrei Popescu wrote:
> I agree with you, but in this particular case it is not a 'Depends' it
> is a 'Recommends', and testing/unstable users should know how to
> override those.
Andrei,
I do not mind installing some extra packages if they are recommended, and
I will leave the setting as it is;
On Thu,20.May.10, 15:13:35, James Zuelow wrote:
> In Thomas' defense, I noticed the same thing and had much the same reaction.
>
> The Squeeze KDE 4.4 update this week pulled down network-manager as a
> dependency. In my case I much prefer wicd to handle my wireless.
$ aptitude search '?d
-Original Message-
From: James Zuelow
To: debian-user@lists.debian.org
Subject: RE: Unable to connect to my home wireless
Date: Thu, 20 May 2010 15:13:35 -0800
> I hoped at least the first part of the mail would be helpful
> to someone having
> the same problem. I found a
> I hoped at least the first part of the mail would be helpful
> to someone having
> the same problem. I found a few posts with the same error
> during the last, but
> no answer so far.
>
> > IMO complaints should go to bugs.debian.org,
> > not necessarily here.
>
> Noted.
>
> Th.
In Thoma
Jordan Metzmeier wrote:
> It sounds to me like this was not a regular upgrade, or your running/mixing
> with a release such as testing or unstable. You can use "aptitude why
> network-manager-kde" to find out why a package was automatically
> installed.
You are right, I am running debian/testing.
On Thu, May 20, 2010 at 5:10 PM, Thomas Pircher wrote:
> Same here: after the update on Tuesday (Monday I didn't update), my
> wireless
> network stopped working.
>
> Today I figured out what was going on: the update installed the packets
> knm-
> runtime, network-manager-kde, network-manager and
Same here: after the update on Tuesday (Monday I didn't update), my wireless
network stopped working.
Today I figured out what was going on: the update installed the packets knm-
runtime, network-manager-kde, network-manager and possible other packets.
After I duly uninstalled those offending pi
On 04/05/10, Zoran Kolic (zko...@sbb.rs) wrote:
| > ...
| > IBM High Rate Wireless LAN PC Card
| > Chipset: Hermes I
| > Drivers: orinoco_cs
| Woops!
| Cannot say I had an experience with orinoco. It was
| old kind of chip. I think that support for orinoco
| was abandoned for bsd year or so ago.
> My card is listed at
> http://www.thinkwiki.org/wiki/Wireless_Network_Adapters#IBM_High_Rate_Wireless_LAN_PC_Card,
> at the very bottom of the page:
> IBM High Rate Wireless LAN PC Card
> Chipset: Hermes I
> Drivers: orinoco_cs
> Supported wireless modes: 802.11b
> I pulled the thing out of the
On 03/05/10, Zoran Kolic (zko...@sbb.rs) wrote:
| > | When I try to connect, wicd says that it is 'Putting interface up...',
'Validating authentication...', 'Obtaining IP address...' then it times out and
says 'Connection failed: Unable to Get IP Address.'
| >
| > I have no clue what causes the
On Mon, May 3, 2010 at 10:08, Zoran Kolic wrote:
> > | When I try to connect, wicd says that it is 'Putting interface up...',
> 'Validating authentication...', 'Obtaining IP address...' then it times out
> and says 'Connection failed: Unable to Get IP Address.'
> >
> > I have no clue what causes
> | When I try to connect, wicd says that it is 'Putting interface up...',
> 'Validating authentication...', 'Obtaining IP address...' then it times out
> and says 'Connection failed: Unable to Get IP Address.'
>
> I have no clue what causes the problem, but I have found a clumsy
> workaround by
On Mon, May 3, 2010 at 07:31, Marc Shapiro wrote:
> From: John
>
> > On 01/05/10, Marc Shapiro (mshapiro...@yahoo.com) wrote:
> | When I try to connect, wicd says that it is 'Putting interface up...',
> 'Validating
> | authentication...', 'Obtaining IP address...' then it times out and says
> |
From: John
> On 01/05/10, Marc Shapiro (mshapiro...@yahoo.com) wrote:
| When I try to connect, wicd says that it is 'Putting interface up...',
'Validating
| authentication...', 'Obtaining IP address...' then it times out and says
| 'Connection failed: Unable to Get IP Address.'
|
| Does anyon
On 01/05/10, Marc Shapiro (mshapiro...@yahoo.com) wrote:
| Date: Sat, 1 May 2010 23:24:56 -0700 (PDT)
| From: Marc Shapiro
| To: debian-user@lists.debian.org
| Subject: Unable to connect to my home wireless
| X-Spam-Status: No, score=-9.5 required=4.0
| tests=DNS_FROM_RFC_WHOIS,FOURLA
On 05/02/2010 09:24 AM, Marc Shapiro wrote:
I am running an up to date Squeeze system using LXDE. I use wicd as my network
manager. Since doing a full upgrade on Monday I have been unable to connect to
my home wireless network. I can connect to various unsecured networks at work,
at local
I am running an up to date Squeeze system using LXDE. I use wicd as my network
manager. Since doing a full upgrade on Monday I have been unable to connect to
my home wireless network. I can connect to various unsecured networks at work,
at local restaurants and coffee shops. I just can&#
37 matches
Mail list logo
