Hello again,
oh, and I should have mentioned, some updates did not build due to patch files
no longer applying (qpdf, cups-filters or so), two or Downloads did not work,
and one package did throw a Paranoia Check exception due to the State being
changed to “Release” which is not a valid T2 tag for the State tag, … :-/
It would be really awesome if the patches would apply a little bit more
automatically without that much manual cleanup on my side ;-)
René
> On 17. May 2020, at 20:34, René Rebe <r...@exactcode.com> wrote:
>
> Hi,
>
> on another note, all the patches did not apply, after a closer inspection and
> try they all miss at least the trailing newline at the last line.
>
> I now sorted thru most and hand fixed them, but how did you generate them, or
> did you open them all in some editor that you have configured to save files
> without newline at the last line?
>
> I have some bigger stuff, like qt to look at, and I will not blindly apply
> the random build priority changes but rather wait for my next reference build
> to see which of them are actually really needed as usually most stuff just
> built so far for me. Obviously we finally should get rid of this
> old-fashioned static build order thing and only use the .cache deps to
> dynamically schedule the builds.
>
> René
>
>> On 17. May 2020, at 14:30, René Rebe <r...@exactcode.com> wrote:
>>
>> Hi,
>>
>> it would help if you would not include some random stuff, e.g. there are
>> some maybe accidental downrates, or updates like:
>>
>> xorgproto 2020 -> 2019
>>
>> bdb 5.x -> 6.x which I just downloaded due to some packages explicitly not
>> allow building against the now AGPL or so bdb 6
>>
>> some updated .desc mis the checksum, which helps checking if you and me got
>> the same file form the server.
>>
>> Mesa -Dbuildtype=release - are you sure that changed a thing?
>>
>> gdk-pixbuf you competed out disabling installed_tests=false which I’M pretty
>> sure fixed at least some bootstrapping cross build, why would you need to
>> enable to us useless tests again?
>>
>> You made gnutls NOPARALLEL, maybe by accident? Built for me.
>>
>> In general it would not hurt if you are a bit more careful about random
>> changes, and whitespace damage.
>> Usually developers are not the most happy to randomly move stuff around, as
>> this taints the history with random changes, and makes tracking changes and
>> failures more harder.
>>
>> You puppy guys also have the tendency to leave old stuff commented out, like
>> in gparted.desc:
>>
>> #[D] 29… old download
>>
>> Such old lines of code or data are pretty pointless and in general should
>> not be included in a submitted upstream patch.
>>
>> Thank you for the updates in between, I will sort thru this, maybe live on
>> youtube as it takes easily more than 30 minutes, …
>>
>> Also not so sure about all the touched priority numbers, as it in general
>> built quite ok for me.
>>
>> René
>>
>>> On 17. May 2020, at 01:56, scsijon <scsi...@lamiaworks.com.au> wrote:
>>>
>>> ok, attached in one to see if it goes as it's 16k, otherwise i'll split it
>>> up.
>>> regards
>>> scsijon
>>>
>>> On 16/5/20 6:45 pm, René Rebe wrote:
>>>> Hi,
>>>>> On 16. May 2020, at 04:50, scsijon <scsi...@lamiaworks.com.au> wrote:
>>>>>
>>>>> Hi,
>>>>> I have 58 diffs for t2sde corrections in my latest batch of fixes for
>>>>> you. I knew I was getting through them, but I just hadn't realized how
>>>>> many packages required work and were sorted out this time. There's still
>>>>> about 20 packages left for me to sort out at this point of time in this
>>>>> my third build list, leaving a dozen in the fourth that I know will cause
>>>>> troubles. There is also a few new packages caused by dependancies and a
>>>>> couple I want to add to package/contrib that i'll deal with individually
>>>>> as I 'get them up and running'.
>>>>>
>>>>> How do you want these fix .diff's, as individual messages, or considering
>>>>> the number, packaged up in a compressed file as I don't want to overload
>>>>> your mail system unless your happy with it to happen?
>>>> Just send them in whatever way is comfortable / easy for you and I will
>>>> try to sort thru them ;-)
>>> <t2sde-515-1.tar.gz>-----------------------------------------------------------
>>>
>>> If you wish to unsubscribe from this mailing, send mail to
>>> li...@t2-project.org with a subject of: unsubscribe t2
>>
>> --
>> ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com
>> https://exactscan.com | https://ocrkit.com | https://t2sde.org |
>> https://rene.rebe.de
>>
>> -----------------------------------------------------------
>> If you wish to unsubscribe from this mailing, send mail to
>> li...@t2-project.org with a subject of: unsubscribe t2
>
> --
> ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com
> https://exactscan.com | https://ocrkit.com | https://t2sde.org |
> https://rene.rebe.de
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> li...@t2-project.org with a subject of: unsubscribe t2
--
ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com
https://exactscan.com | https://ocrkit.com | https://t2sde.org |
https://rene.rebe.de
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
li...@t2-project.org with a subject of: unsubscribe t2
