[Xastir] Ubuntu-cvsbuild script updated for 10.10

David A Aitcheson david.aitcheson at gmail.com
Tue Jan 4 11:12:51 EST 2011


Peter,

As I said earlier, I got it stopped before it did any damage.

I looked at the logs you mentioned but could find no mention of the
script at all, possibly/probably because I [ctrl]C'd out of it so fast.
 Which does not make any sense, so I am wondering what else is not
getting logged.

I have gone through all my development systems and they all seem to be
intact and functioning, and yes I have frozen items so they do not get
deleted or overwritten, some of those were in the to be deleted list.

I deal with a bunch of over educated in some other field professors that
think because they have a PhD that they are the be all end all when it
comes to being a windows appliance user via a GUI on a touch screen
controller.  I don't mean to offend any on here with that but that is my
lot that I have to live with.

I am trying to get a hardware update soon and that may clear a lot of
these problems.  This machine is circa 2006 and still running for now.
Getting everyone to talk on either USB or Ethernet and abandoning RS-232
has finally been accomplished for the equipment under development; the
stuff already out in the field is another problem of its own.

Dave


On 01/04/2011 10:04 AM, Peter Gamache/KC0TFB wrote:
> It looks like considerable excitement has occurred in the evening I spent
> away from my email...
> 
> David, would you care to share your logs so I may understand what
> happened?  The logs of interest are in /var/log/apt.  I'd like to see both
> history.log and term.log for the period in which you ran the cvsbuild
> script.
> 
> The script simply doesn't contain any instructions for apt to
> remove/purge/delete anything, so if something got deleted, it may have
> been a pending change to your system that was already queued for dpkg to
> act upon - something that it would do when any subsequent action was
> performed with apt-get (like an ordinary update/upgrade cycle).  Did you
> have any previous installations, removals or upgrades that had only
> partially completed, prior to running the script?  Did you regularly keep
> your system updated with "apt-get update && apt-get dist-upgrade", prior
> to running the script?
> 
> Also, these development libraries you speak of ... were they installed in
> /usr/lib, /var/lib, or somewhere else?  It's possible, if you named
> something the same as one of the libraries to be installed, or if you
> installed the source of a standard package, then modified it and installed
> it where the default library lives, that it would be overwritten by any
> future updates.  The dpkg/apt system provides a way to freeze packages,
> preventing the normal update/upgrade cycle from pulling down new ones - if
> you modify a standard library, it's important to flag the package(s) so
> they don't get overwritten by subsequent officially-maintained versions.
> 
> Thanks,
> -PG
> 
> Jason Godfrey wrote:
>> The following is speculation based on my experience with other package
>> managers. I have only used Ubuntu a little bit. I also don't know about
>> any
>> customizations to your system. Take the following suggestion at your own
>> risk.
>>
>> My guess is that interrupting the update process is what caused the
>> problem.
>> Your software is probably in a weird partially updated state. Running the
>> script again or "sudo aptitude update" might restore your system to a
>> working state.
>>
>> - Jason
>>
>> On Tue, Jan 4, 2011 at 12:05 AM, David A Aitcheson <
>> david.aitcheson at gmail.com> wrote:
>>
>>> Okay I was able to get it stopped as it was downloading the third
>>> package and before it did any damage to my developement libraries for my
>>> college courses.
>>>
>>> It wanted to wipe out 66 packages that are used on a weekly basis for my
>>> college code and hardware developement courses in Alternative Energy.
>>>
>>> A lot of them are really weird "how to relate to the windows world"
>>> translators.
>>>
>>> What really irked me was that it takes off and goes with no "are you
>>> sure" question after it figures out what it needs to do; so if someone
>>> hits go and walks away it could be a "mess maker" is all that can render
>>> it down to.
>>>
>>> It might be best to use on a machine that is only used for XASTIR and
>>> nothing else.
>>>
>>> I am a college senior on a five year plan; starting the final year this
>>> month.  At 52 I don't have another 4 years to rebuild everything.
>>>
>>> Dave - KB3EFS
>>>
>>>
>>> On 01/03/2011 08:52 PM, Jason Godfrey wrote:
>>>> The script doesn't look like it deletes any packages, only updates.
>>>> Perhaps some dependancies for your broken programs were updated, and
>>>> updating those programs will fix it. I would have thought the package
>>>> manager would of handled that.
>>>>
>>>> Really, four years?
>>>> - Jason
>>>>
>>>> On Mon, Jan 3, 2011 at 6:52 PM, David A Aitcheson
>>>> <david.aitcheson at gmail.com <mailto:david.aitcheson at gmail.com>> wrote:
>>>>
>>>>     ONE HUGE PROBLEM...
>>>>
>>>>     This script removes WITHOUT WARNING a bunch of things that BROKE a
>>> HUGE
>>>>     bunch or other programs for me.
>>>>
>>>>     Thanks for setting me back four (4) years.
>>>>
>>>>
>>>>     On 01/03/2011 02:51 PM, Peter Gamache/KC0TFB wrote:
>>>>     > Good catch!  I've fixed that.
>>>>     >
>>>>     > Prior to yesterday's release, I tried the script on two
>>> different
>>>>     systems:
>>>>     > one virgin install of 10.10 and another that was upgraded from
>>>>     10.04 to
>>>>     > 10.10 (without having run the script prior to the upgrade).  It
>>> seemed
>>>>     > fine on both systems anyway, but it seems more common-sensical
>>> to
>>>>     do it
>>>>     > with the proper release name, as lucid and maverick may diverge
>>> on
>>>>     the GIS
>>>>     > repo in the future.
>>>>     >
>>>>     > Thanks,
>>>>     > -PG / KC0TFB
>>>>     >
>>>>     > Tom Russo wrote:
>>>>     >> One quick comment:  Your script adds the PPA for UbuntuGIS,
>>> which
>>>>     is a
>>>>     >> good
>>>>     >> thing, but always seems to add the "lucid" version to the apt
>>> sources
>>>>     >> list,
>>>>     >> even if it's detected Maverick.
>>>>     >>
>>>>     >
>>>>     > _______________________________________________
>>>>     > Xastir mailing list
>>>>     > Xastir at lists.xastir.org <mailto:Xastir at lists.xastir.org>
>>>>     > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>>>>     >
>>>>
>>>>
>>>>     --
>>>>     David A Aitcheson
>>>>     david.aitcheson at gmail.com <mailto:david.aitcheson at gmail.com>
>>>>     david.aitcheson on google and skype
>>>>
>>>>     _______________________________________________
>>>>     Xastir mailing list
>>>>     Xastir at lists.xastir.org <mailto:Xastir at lists.xastir.org>
>>>>     http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> I have learned to use the word 'impossible' with the greatest caution.
>>>> -- Wernher von Braun
>>>>
>>>
>>>
>>>
>>> --
>>> David A Aitcheson
>>> david.aitcheson at gmail.com
>>> david.aitcheson on google and skype
>>>
>>
>>
>>
>> --
>> I have learned to use the word 'impossible' with the greatest caution.  --
>> Wernher von Braun
>> _______________________________________________
>> Xastir mailing list
>> Xastir at lists.xastir.org
>> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>>
> 
> 
> 



-- 
David A Aitcheson
david.aitcheson at gmail.com
david.aitcheson on google and skype



More information about the Xastir mailing list