On Fri, Apr 07, 2006 at 12:48:08AM +0100, Adam Hardy wrote:
>
> I'm using etch / testing and I did some upgrades (to try to get the
> hotsynch for my handheld working) but things went badly wrong.
>
> Now I'm trying to owngrade udev to 0.79 from 0.8xx but I can't get
> synaptic to allow me to for
I'm using etch / testing and I did some upgrades (to try to get the
hotsynch for my handheld working) but things went badly wrong.
Now I'm trying to owngrade udev to 0.79 from 0.8xx but I can't get
synaptic to allow me to force the version I need. The menu option is
just greyed out.
How can I
--- Bill Marcum <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 22, 2005 at 12:18:07PM -0700, Ibrahim Mubarak wrote:
> >
> > First of all, how can I find out what version of a package is
> installed
> > on my system without going through synaptic or dselect, because
> > sometimes I don't have access to
On Mon, Aug 22, 2005 at 12:18:07PM -0700, Ibrahim Mubarak wrote:
>
> First of all, how can I find out what version of a package is installed
> on my system without going through synaptic or dselect, because
> sometimes I don't have access to an X session and the version number
> would be too long
--- Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
First of all, how can I find out what version of a package is installed
on my system without going through synaptic or dselect, [...]
Have a look at the manpage of the 'apt-cache' command, especially the
'policy' part:
$ apt-cache policy kdelibs-
On Mon, Aug 22, 2005 at 03:36:33PM -0500, Kent West wrote:
> Ibrahim Mubarak wrote:
>
> >--- Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I performed an upgrade yesterday to my SID system. I know these are
> >>tough times with the migration to gcc 4.0 and everything, and that I
> >>sho
Ibrahim Mubarak wrote:
>--- Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
>
>
>>I performed an upgrade yesterday to my SID system. I know these are
>>tough times with the migration to gcc 4.0 and everything, and that I
>>should have been more careful, but I messed up. I am still not sure
>>where. N
--- Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I performed an upgrade yesterday to my SID system. I know these are
> tough times with the migration to gcc 4.0 and everything, and that I
> should have been more careful, but I messed up. I am still not sure
> where. Now (after a reboo
Hi all,
I performed an upgrade yesterday to my SID system. I know these are
tough times with the migration to gcc 4.0 and everything, and that I
should have been more careful, but I messed up. I am still not sure
where. Now (after a reboot), when I am in KDE, nothing appears on the
panel menu exce
Scott Henson <[EMAIL PROTECTED]> writes:
> On Thu, 2002-05-16 at 13:30, Andrew Perrin wrote:
>> Any clues on where to find the old package? It's not on the sane page or
>> the debian page.
>
> Try /var/cache/apt/archives/
> failing that, maybe someone here on the list has an old deb laying
> aroun
On Thu, 2002-05-16 at 13:30, Andrew Perrin wrote:
> Any clues on where to find the old package? It's not on the sane page or
> the debian page.
I forgot this on my last message. You could also skip the pining and
just download the deb from woody manually and do a dpkg
--force-downgrade on that.
On Thu, 2002-05-16 at 13:30, Andrew Perrin wrote:
> Any clues on where to find the old package? It's not on the sane page or
> the debian page.
Try /var/cache/apt/archives/
failing that, maybe someone here on the list has an old deb laying
around. And if you cant do that, your gonna have to downg
Any clues on where to find the old package? It's not on the sane page or
the debian page.
ap
--
Andrew J Perrin - http://www.unc.edu/~aperrin
Assistant Professor of Sociology, U of North Carolina, Chapel Hill
[EMAIL PROTECTED] *
On Thu, 2002-05-16 at 09:10, Andrew Perrin wrote:
> I've become pretty much convinced that the bug I reported yesterday in
> sane-backends is an upstream bug, so I'm therefore waiting for a fix. In
> the meantime, though, I need to use the scanner! What's the simplest way
> for me to back out of th
I've become pretty much convinced that the bug I reported yesterday in
sane-backends is an upstream bug, so I'm therefore waiting for a fix. In
the meantime, though, I need to use the scanner! What's the simplest way
for me to back out of the upgrade and revert to the previous version of a
package?
15 matches
Mail list logo
