trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2016

Re: Re: Re: VCardConverter parseVCard problem

From: deloptes <deloptes@...>
Date: Thu, 17 Mar 2016 23:58:34 +0100
Lisi Reisz wrote:

> On Thursday 17 March 2016 19:06:00 deloptes wrote:
>> Lisi Reisz wrote:
>> > Why not just use Slávek's Preliminary Stable Builds repository instead
>> > of the ones you have?  It would solve your problem immediately for very
>> > little effort.  I switched some while ago because I wanted a patch fast
>> > and have never looked back.  It is great!  You get exactly what will be
>> > going into 14.0.4, but you get it sooner.  And come the release of
>> > 14.0.4 you won't need to upgrade because you will already have it. 
>> > Note the "Stable" in the name. ;-)
>> >
>> > Lisi
>>
>> I don't know - this is new to me and the steak is big as I can not risk,
>> so I had to investigate pro and contra but never got the opportunity to
>> do so. Since I have time to follow up the list closer, it was in some
>> sort of transition, but I think now it settled down.
>> If you have some information to enlighten me, this would be nice.
> 
> What would you like to know?  Debian users are apt to see Slávek's
> Preliminary Stable Builds repository as the equivalent of Testing, but
> that is wrong.
> 

I never thought of it in any kind. Something I do not understand or know, I
do not qualify or see as something else. So I never had time or interest to
look into this matter.

> Assuming that you go on using
> deb http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian
> jessie main
> deb-src
> http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian jessie
> main deb
> and that you update and upgrade regularly, then when 14.0.4 is released
> you
> will get all the new packages and patches in one fell, quite large swoop. 
> If you don't want then you will have to stop upgrading or comment out the
> Trinity repositories.

Yes usually Friday at the office. They have really fast network there. It
takes 15mins (at least last time it took 15min to download and
install/upgrade to 14.0.3)

> 
> Those packages and patches are not prepared suddenly over-night.  They are
> gathered up over time and stored until it is time to release them.  It is
> Slávek who stores them.  (I think only Slávek, but possibly not only
> Slávek).
> 

I understand thanks

> If you change to:
> 
> deb http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14
> deb-src http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14
> 
> then as the bug patches and new packages are ready, you will get them
> immediately.  Exactly the same ones as you would get later in 14.0.4 when
> it
> is released.  Mostly bug patches.  As with Debian Stable, new things are
> _mostly_ reserved for the next major release and it is bug fixes which are
> released meanwhile.  So the only difference is when you get them.  As
> there
> is no such thing as  software without bugs, presumably there are
> occasionally bugs in the bug-fixes, and presumably they are occasionally
> found and put right.
> 
> But I do not see what you would have to lose if you want a patched package
> urgently.  What you are doing now strikes me as just possibly being able
> to
> mess up your system.  Not very likely, but more likely than stuff released
> by Slávek, since that has been tested elsewhere, and its tested
> dependencies
> worked out, before it reaches your system.  The Preliminary Stable Builds
> repositories are no more risky than any other upgrade.
> 

It gives a better picture thanks. Because I use this notebook for work, I
don't feel well being one of the first and few to run new software. This is
it and this is why I stick to debian stable and TDE.

> I'm not sure if that has answered your questions at all.  Just ask, if it
> hasn't.  But if you want a particular bug fix to a particular package, and
> Slávek has the patch, this is in MHO the safest, and certainly the
> quickest and easiest, way to get it.

Yes this was perfect, thanks.
I still however prefer to be able to rebuild the package I need. I have few
packages I marked to hold until fixes are pushed upstream.
It is simply much faster and gives me opportunity to test (perhaps to
improve the suggested patch).

In theory from what I here it would be possible to install just a single
package from Slaveks repo - correct? So download and dpkg -i should do the
work, but what about dependencies and the same question applies to what you
described above - if the repo builds up incrementally, does it mean I have
all dependencies in one go? 

regards