[horde] Finished importing horde FW_6 to packagist.org / composer / compatibility with newer PHP versions

[Michael Schlueter]

Hello Ralf,

I tested it last night and it was working without problems for me. Thanks.

Tried all menu entries and buttons I saw found only one horde/form  
issue in nag/search.php but no other issue.

Could you also release a new alpha version for the package horde/horde  
so that the rampage.php warning is fixed?

Thanks a lot
Michael

Sent from Nine

________________________________
Von: "Lang, Ralf" <ralf.lang at gmail.com>
Gesendet: Freitag, 12. Januar 2024 09:51
An: horde at lists.horde.org
Betreff: Re: [horde] Finished importing horde FW_6 to packagist.org /  
composer / compatibility with newer PHP versions

> Hi Michael,
>
>
>> include it in install tests Add trean tests · horde/bundle at 152c2c1  
>> (github.com)  
>> <https://github.com/horde/bundle/actions/runs/7489156045/job/20385100231>  
>> (done)
>>
>> do a minimal test drive
>>
> Done. Confirmed trean H6 to basically work on PHP 8.2. Test with PHP  
> 8.3 setup pending.
>
>> actively look for signature issues already found in other apps  
>> (think of the horde/form issues in turba, whups and kronolith we  
>> already solved).
>>
>> Any issues you report will be handled, too.
>>
>>> A lot of the horde components in github in the FW_6 branches still  
>>> have https://horde-satis.maintaina.com/ in the repositories  
>>> section in composer.json. Could that cause problems because  
>>> packages get loader from horde-satis.maintaina.com instead of  
>>> packagist.org?
>>>
>> Repository sections are only honored for root components, i.e. the  
>> horde/bundle. It will also apply to dependencies when the app or  
>> lib installed as a root component for unit testing.
>>
>> Otherwise these entries are simply ignored and should not cause  
>> problems. However, generation of the repo entry is disabled for  
>> upstream. Whenever we either run "horde-components composer" in  
>> standalone mode for the branch or "horde-components release for  
>> upstream" to create a new release, a new composer.json is generated  
>> from the .horde.yml file. This new file will not have these entries.
>>
>>> Thanks a lot
>>> Michael
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>