Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
SVG broke after installing Pidgin unstable packageHi,I wanted to install Pidgin on my new Debian Etch setup. I found that the package was only available in the unstable repository, so I added that to my sources.list and installed it. Some other packages (dependencies I guess) also got installed. Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
SVG broke after installing Pidgin unstable package
On Sun, Sep 02, 2007 at 06:17:29PM +0200, Rickard Lindberg wrote:
> I wanted to install Pidgin on my new Debian Etch setup. I found that the
> package was only available in the unstable repository, so I added that to my
> sources.list and installed it. Some other packages (dependencies I guess)
> also got installed.
>
Congratulations, you just killed your system.
Doug.
--
SVG broke after installing Pidgin unstable package
On Sun, Sep 02, 2007 at 11:29:35PM +0530, Kumar Appaiah wrote:
> On Sun, Sep 02, 2007 at 01:36:13PM -0400, Douglas A. Tutty wrote:
> > Congratulations, you just killed your system.
>
> Though he's very terse, what Doug means to say is that you have broken
> your system by injecting a potent mix of unstable packages, which is
> not recommended. One thing you might (or might not) want to do is, a
> straight dist-upgrade to unstable (sid) using apt-get dist-upgrade,
> but the choice is yours.
>
> Kumar
> P.S. I've been using sid for a long time, and am able to get work done
> with no problems! So, don't be afraid.
Sorry for being terse. Yes it may be possible to revive it with
Advanced Aptitude Life Support (TM):) but I figured that anyone who
didn't have the knowledge to prevent the problem probably didn't have
the knowledge to perform the AALS. I have been mistaken before.
To this end, the OP may not realize that if he does go up to Sid that
downgrading is not supported. It may be a learning experience to fix
the system or move to Sid, however, if he has the bandwidth to make
keeping up with Sid an option (I'm on dialup so can't), it will probably
be be faster to just reinstall Etch.
Doug.
--
SVG broke after installing Pidgin unstable package
Douglas A. Tutty writes:
> ...if he has the bandwidth to make keeping up with Sid an option...
There is no need to "keep up" with Sid,
--
John Hasler
--
SVG broke after installing Pidgin unstable package
On Sun, Sep 02, 2007 at 03:36:28PM -0500, John Hasler wrote:
> Douglas A. Tutty writes:
> > ...if he has the bandwidth to make keeping up with Sid an option...
>
> There is no need to "keep up" with Sid,
You mean that sid is stable? Don't things change frequently, requiring
aptiude updates/upgrades?
Doug.
--
SVG broke after installing Pidgin unstable package
I wrote:
> There is no need to "keep up" with Sid,
Doug writes:
> You mean that sid is stable?
No.
> Don't things change frequently..,
They do.
> ...requiring aptiude updates/upgrades?
What would require that? So things change: so what? Why do you think you
have to keep up?
--
John Hasler
--
SVG broke after installing Pidgin unstable package
On Sun, Sep 02, 2007 at 06:09:41PM -0500, John Hasler wrote:
> I wrote:
> > There is no need to "keep up" with Sid,
>
> Doug writes:
> > You mean that sid is stable?
>
> No.
>
> > Don't things change frequently..,
>
> They do.
>
> > ...requiring aptiude updates/upgrades?
>
> What would require that? So things change: so what? Why do you think you
> have to keep up?
Two reasons: bug fixes for any problems I would notice (things not
working); security-related bug fixes for problems that I don't notice
but that are important. The same reason that its important to subscribe
to the security-announce list and/or do periodic aptitude updates when
running stable to check for security fixes, and apply them if found.
Applying a security fix generally involves downloading a new package.
Doug.
--
SVG broke after installing Pidgin unstable package
I wrote:
> What would require that? So things change: so what? Why do you think
> you have to keep up?
Doug writes:
> Two reasons: bug fixes for any problems I would notice (things not
> working)...
Just upgrade packages in which you find troublesome bugs (and which have
been fixed in Sid).
> ...security-related bug fixes for problems that I don't notice but that
> are important.
Pay attention to security-announce and upgrade packages as required.
> Applying a security fix generally involves downloading a new package.
It does not involve constantly dist-upgrading. There is no need to upgrade
Sid packages just because new ones are available, which is what "keeping
up" implies. While some evidently find it amusing to do daily
dist-upgrades it is by no means necessary.
--
John Hasler
--
SVG broke after installing Pidgin unstable package
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/02/07 19:37, John Hasler wrote:
[snip]
>
> It does not involve constantly dist-upgrading. There is no need to upgrade
> Sid packages just because new ones are available, which is what "keeping
> up" implies. While some evidently find it amusing to do daily
> dist-upgrades it is by no means necessary.
You are the one who used "constantly". DAT used "periodically".
*BIG* difference.
Personally, I find that weekly or bi-weekly upgrades are adequate.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG22GBS9HxQb37XmcRAgp7AKDgK0ss5Ke5HIN/q+yiai8bwaebVACdFpSd
RBuxqqQykddt1tPUpKNR5B0=
=p9zj
-----END PGP SIGNATURE-----
--
SVG broke after installing Pidgin unstable package
On Sun, Sep 02, 2007 at 08:21:05PM -0500, Ron Johnson wrote:
> Personally, I find that weekly or bi-weekly upgrades are adequate.
Ron, I know that it will vary, possibly widely, but what size of
download are you typically seeing on your weekly or bi-weekly upgrades?
I'm on slow dial-up (generally no more than 2 KB/s except for short
bursts) and I can only use the phone during the day with interruptions
for when its needed.
Doug.
--
SVG broke after installing Pidgin unstable package
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/02/07 20:46, Douglas A. Tutty wrote:
> On Sun, Sep 02, 2007 at 08:21:05PM -0500, Ron Johnson wrote:
>
>> Personally, I find that weekly or bi-weekly upgrades are adequate.
>
> Ron, I know that it will vary, possibly widely, but what size of
> download are you typically seeing on your weekly or bi-weekly upgrades?
>
> I'm on slow dial-up (generally no more than 2 KB/s except for short
> bursts) and I can only use the phone during the day with interruptions
> for when its needed.
You're right: it depends on if big honkers like openoffice,
iceweasel, icedove, celestia-common, "gcc" or any of the other
myriad Big Packages are being upgraded.
Today, there's about 120MB of data to download.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG221tS9HxQb37XmcRAgOjAJ9Y3AH5dg2wsfNQtTDzmhmBs5yskwCcCpID
vQtQbdKWwTZ2EOcQ4LY7p8Q=
=yN88
-----END PGP SIGNATURE-----
--
SVG broke after installing Pidgin unstable package
Thank you guys for all the information. I might try a dist upgrade to
sid, and if that is not working well, I might do a complete reinstall
of etch.
Does anyone have any experience running the 'testing' release? I
watched 'The Technology Behind Debian's Testing Release' from google
video yesterday, and in the end of the presentation he mentioned that
in the future, it might be possible to run a stable release, but at
the same time install some packages from unstable. Does anyone know
anything about that? When will it be available? Is someone is working
on it?
Again, thanks for all the helpful information.
--
Rickard Lindberg
+46 733 464794
--
SVG broke after installing Pidgin unstable package
Hi.
Kumar Appaiah, 03.09.2007 09:44:
> On Mon, Sep 03, 2007 at 09:31:27AM +0200, Rickard Lindberg wrote:
>> Does anyone have any experience running the 'testing' release? I
>> watched 'The Technology Behind Debian's Testing Release' from google
>> video yesterday, and in the end of the presentation he mentioned that
>> in the future, it might be possible to run a stable release, but at
>> the same time install some packages from unstable. Does anyone know
>> anything about that? When will it be available? Is someone is working
>> on it?
>
> You can, even now, try putting testing in your sources.list and try to
> move to testing. Testing is also a trifle better than instable because
> the secutiry team now gives security updates for testing as
> well.
Well, Unstable gets security updates too, only as regular package updates.
> Added advantage: it gets all newer packages from unstable after
> 10 days of no critical bug reports in unstable.
This is an added disadvantage for me, since it also can take 10 or more days
until a fix can enter Testing where it is fixed sometimes on the same day in
Unstable.
> In a sense, testing (now lenny) may be just the right balance you are
> looking for, but YMMV.
Agreed.
Regards, Mathias
--
debian/rules
SVG broke after installing Pidgin unstable package
On Sun, Sep 02, 2007 at 09:11:57PM -0500, Ron Johnson wrote:
> You're right: it depends on if big honkers like openoffice,
> iceweasel, icedove, celestia-common, "gcc" or any of the other
> myriad Big Packages are being upgraded.
>
> Today, there's about 120MB of data to download.
>
About 17 hrs of download, or about 3 days worth.
Doug.
--
SVG broke after installing Pidgin unstable package
John Hasler wrote:
> Douglas A. Tutty writes:
>> ...if he has the bandwidth to make keeping up with Sid an option...
>
> There is no need to "keep up" with Sid,
Indeed. Sid follows me around together with Carlota and Concho...
--
SVG broke after installing Pidgin unstable package
Kumar writes:
> You can, even now, try putting testing in your sources.list and try to
> move to testing.
Good idea.
> Testing is also a trifle better than instable because the secutiry team
> now gives security updates for testing as well. Added advantage: it gets
> all newer packages from unstable after 10 days of no critical bug reports
> in unstable.
More important advantage: packages do not migrate to testing until all
their dependencies can be satisfied.
You can handle security updates by installing the fixed package from Sid.
--
John Hasler
--