Arno Schuring writes:
> What does the following show:
> $ aptitude search ~ahold
>
> This should probably give you the list of 135 packages. You can release
> the held packages by using the same syntax:
> # aptitude unhold ~ahold
Yes it does... thanks for the unhold stuff with aptitude
[...] Sn
Harry Putnam (rea...@newsguy.com on 2011-11-12 05:31 -0600):
> Andrei POPESCU writes:
>
> > I would suggest you run 'aptitude safe-upgrade' first and then try
> > 'aptitude full-upgrade'. Don't worry, aptitude will present all
> > changes to you before applying. If you don't like or understand
>
Andrei POPESCU writes:
> I would suggest you run 'aptitude safe-upgrade' first and then try
> 'aptitude full-upgrade'. Don't worry, aptitude will present all changes
> to you before applying. If you don't like or understand what you see
> just copy-paste it here and we'll have a look.
It happ
On Jo, 10 nov 11, 04:56:08, Harry Putnam wrote:
> >
> > What are you using for updates, just the Update Manager or
> > apt-get/aptitude?
>
> I've actually used both on occasion. Are you suggesting I should run
> something in particular with an specific apt-get/aptitude command.
>
> Is there any
Andrei POPESCU writes:
> On Jo, 27 oct 11, 15:08:57, Harry Putnam wrote:
>> I noticed this command posted for another recent thread:
>>aptitude search ~ahold
>>
>> I was curious so ran it myself. I was shocked to see quite a bunch of
>> held packages.. 140 to be exact. Are there any circum
On Jo, 27 oct 11, 15:08:57, Harry Putnam wrote:
> I noticed this command posted for another recent thread:
>aptitude search ~ahold
>
> I was curious so ran it myself. I was shocked to see quite a bunch of
> held packages.. 140 to be exact. Are there any circumstances that
> would warrant suc
I noticed this command posted for another recent thread:
aptitude search ~ahold
I was curious so ran it myself. I was shocked to see quite a bunch of
held packages.. 140 to be exact. Are there any circumstances that
would warrant such a high count?
I'm running wheezy on 32 bit P4 3.02 Ghz an
Mark Grieveson <[EMAIL PROTECTED]> wrote:
> (xserver-xorg-video-ati). Now, for some reason, I've got a plug icon
> letting me know that my computer is running on ac power. Hmm.
>
> Mark
And isn't it? :)))
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough
On Sun, 29 Oct 2006 18:05:27 -0500
Mark Grieveson <[EMAIL PROTECTED]> wrote:
> Holy scare the crap outta me! I normally keep my computer on, because I
> run a web server. But today I turned it off, and when I went to turn it
> on, the xserver wouldn't start. Yikes. H
Holy scare the crap outta me! I normally keep my computer on, because I
run a web server. But today I turned it off, and when I went to turn it
on, the xserver wouldn't start. Yikes. However, given that I have an
ati card, I found the right package, and installed it via aptitude
(xs
On Thu, Sep 21, 2000 at 01:22:22AM -0500, John Reinke ([EMAIL PROTECTED]) wrote:
> I just tried installing a .deb from an old CD, and I used apt-cdrom.
> Somehow, it must have decided to remove a lot of my applications the next
> time I ran dselect. I just hit enter and when I looked back, I found
I just tried installing a .deb from an old CD, and I used apt-cdrom.
Somehow, it must have decided to remove a lot of my applications the next
time I ran dselect. I just hit enter and when I looked back, I found out
that I had just removed a large percentage of my applications!!!
Is there a way to
I recently upgraded to hamm and added the gimp package, version 1.0.0-1.
Today, the third time I ran it, GIMP reported that there was an error in
reading the .gimprc file, so I took a look at it. It's gone:
pr-S-wx--x 6425 6425 64250 May 6 1983 .gimp
What's going on here? Is th
On Tue, Mar 03, 1998 at 07:05:34PM +0100, Lorens Kockum wrote:
> As a corollary, where do you find the source of the programs
> executed during the install of debian? I ask because I wanted
> to check if the install points out the NIS problem when it asks
> whether to use shadow passwords.
IIRC,
On Mon, Mar 02, 1998 at 07:51:19PM +0200, Tommi Virtanen wrote:
> On Mon, Mar 02, 1998 at 04:14:37PM +, Lorens Kockum wrote:
> > Are there any reasons at all for keeping crypted passwords in
> > /etc/passwd ?
>
> NIS is notorious for not working with shadowed passwords
Of course, forgot
Lorens Kockum said something to the effect of:
"Why get asked at all whether to run shadow passwds?"
There are multiple buffer overrun bugs in the shadow
passwd suite as used by debian. The bugs seem to take
different forms in hamm than they do in bo; I'm not sure
why. I reported this as a critic
On Mon, Mar 02, 1998 at 04:14:37PM +, Lorens Kockum wrote:
> Only one thing I don't really like: sure, we do get shadow
> passwords if we ask for them (and oh joy, xlock knows that!)
> but why do we get asked at all? Are there any reasons at all
> for keeping crypted passwords in /etc/passwd ?
In debian-user, I wrote an inane test message, not even setting
the subject to "test" ;-/.
Just because I was completely certain it wouldn't get out.
So much for certainty.
To make up, debian success story. Except for fighting with
deselect a bit, like everyone, especially the first time
round, in
18 matches
Mail list logo
