On 12/04/2017 02:26 AM, Jelle van der Waa wrote:
> Packagers aren't required to subscribe to arch-general, so it's best to
> create a bugreport for this issue.
Done: https://bugs.archlinux.org/task/56566
Thanks.
--
David C. Rankin, J.D.,P.E.
On 12/04/17 at 12:01am, David C. Rankin wrote:
> On 12/03/2017 11:39 PM, David C. Rankin wrote:
> > Seems like it is already fixed under the title "Remove useless conflict"
> >
> > https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/php=e1c14f1569f7da2fd0acf4738771be1eb1096f1d
On 12/03/2017 11:39 PM, David C. Rankin wrote:
> Seems like it is already fixed under the title "Remove useless conflict"
>
> https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/php=e1c14f1569f7da2fd0acf4738771be1eb1096f1d
Pierre,
This will still need a minor version bump
On 12/03/2017 11:06 PM, David C. Rankin wrote:
> All,
>
> Why was the conflict 'php-mcrypt<=7.1' added to php? It now seeks to
> remove php56-mcrypt. I require both for older web apps not yet ported to
> php7. These packages do not conflict as I have used both for a couple of
> years. Now I
All,
Why was the conflict 'php-mcrypt<=7.1' added to php? It now seeks to
remove php56-mcrypt. I require both for older web apps not yet ported to
php7. These packages do not conflict as I have used both for a couple of
years. Now I get:
:: Starting full system upgrade...
resolving
5 matches
Mail list logo