Login | Register
My pages Projects Community openCollabNet

Discussions > dev > dpkg/dist-upgrade versioning

fsvs
Discussion topic

Back to topic list

dpkg/dist-upgrade versioning

Author pmarek
Full name P.Marek
Date 2010-02-04 23:34:56 PST
Message Hello Gunnar!

> The idea sounds great.
> I tested it and I can get all parameters that are neccessary in my script.
> Parsing parameters looks more clean to me than the logfile.
>
> So for simple operations this would be a good replacement!
>
> *But* If i am performing updates or also dist upgrades on my servers I would
> like to keep apt-actions as one big transaction (and checkin) instead of
> seperate dpkg ones.
Hmmm ... I had a few cases where I had a dist-upgrade of several hundred packages and
couldn't really find out *why* some file was changed.
Maybe I didn't look closely enough ... but if the commit would have included only a
dozen packages it would be faster to find.

> The reason behind is if something went wrong during an system-update I can
> investigate (via trac timeline and source browser) in exactly one changeset and
> see what files were changed. Also if no config changes appear for the specific
> package I can at least see an entry of the apt-action in my changelog, which is
> also without configuration changes, very informational. Otherwise I need to
> handle that via an empty commit, which I personally would like to avoid.
How about "empty_commit = no" for the individual dpkg runs, and a summarizing commit
that includes the revision number range?

> Also I see revision number raising very fast especially when performing updates
> on more than one machine.
Yes, that's true.
Do you mind the number or the repository filesystem? With BDB it's a non-issue, and even
FSFS understands packing nowadays.

> What I could do is building something like a queue via the dpkg replacement and
> perform the checkin via the Postinstall hook. This way I can keep with the
> yes/no for the admin, performing the checkin. I need to think about that further...
Yes, how about just asking the admin on FSVS-install "do you want to keep /etc
finegrained, coarse, or not at all?"


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

« Previous message in topic | 6 of 16 | Next message in topic »

Messages

Show all messages in topic

1.2.2 release in the near future pmarek P.Marek 2010-01-30 12:50:26 PST
     Re: 1.2.2 release in the near future tekknokra Gunnar Thielebein 2010-02-04 03:54:19 PST
         Re: 1.2.2 release in the near future pmarek P.Marek 2010-02-04 05:37:43 PST
             Re: 1.2.2 release in the near future pmarek P.Marek 2010-02-04 06:27:31 PST
                 Re: 1.2.2 release in the near future tekknokra Gunnar Thielebein 2010-02-04 08:16:14 PST
                     dpkg/dist-upgrade versioning pmarek P.Marek 2010-02-04 23:34:56 PST
             Re: 1.2.2 release in the near future tekknokra Gunnar Thielebein 2010-02-04 08:34:43 PST
                 Re: 1.2.2 release in the near future pmarek P.Marek 2010-02-04 23:29:58 PST
                     Re: 1.2.2 release in the near future tekknokra Gunnar Thielebein 2010-02-10 10:15:47 PST
                         Re: 1.2.2 release in the near future pmarek P.Marek 2010-02-10 22:17:25 PST
                             Re: 1.2.2 release in the near future tekknokra Gunnar Thielebein 2010-02-12 05:09:34 PST
                                 Re: 1.2.2 release in the near future pmarek P.Marek 2010-02-12 08:30:49 PST
                                     Re: 1.2.2 release in the near future tekknokra Gunnar Thielebein 2010-02-12 11:20:42 PST
                                         Re: 1.2.2 release in the near future pmarek P.Marek 2010-02-13 00:50:01 PST
                                             Re: 1.2.2 release in the near future tekknokra Gunnar Thielebein 2010-02-13 04:13:49 PST
                                                 Re: 1.2.2 release in the near future pmarek P.Marek 2010-02-13 04:50:17 PST
Messages per page: