Re: [arch-dev-public] Automating package conflict resolution whenever possible (xorgproto/libxfont dependency conflict)

2018-02-13 Thread Doug Newgard via arch-dev-public
On Wed, 14 Feb 2018 02:52:16 +0100 (CET) Alad Wenter via arch-dev-public wrote: > > Eli Schwartz via arch-dev-public hat am 14. > > Februar 2018 um 01:48 geschrieben: > > > > > > On 02/13/2018 06:56 PM, Baptiste Jonglez wrote: >

Re: [arch-dev-public] Automating package conflict resolution whenever possible (xorgproto/libxfont dependency conflict)

2018-02-13 Thread Alad Wenter via arch-dev-public
> Eli Schwartz via arch-dev-public hat am 14. > Februar 2018 um 01:48 geschrieben: > > > On 02/13/2018 06:56 PM, Baptiste Jonglez wrote: > > Hi, > > > > Eli and I disagree about how dependency conflicts should be handled when > > packaging. This was prompted by

Re: [arch-dev-public] Automating package conflict resolution whenever possible (xorgproto/libxfont dependency conflict)

2018-02-13 Thread Eli Schwartz via arch-dev-public
On 02/13/2018 06:56 PM, Baptiste Jonglez wrote: > Hi, > > Eli and I disagree about how dependency conflicts should be handled when > packaging. This was prompted by the libxfont dependency conflict arising > from recent xorgproto changes [1]. > > [...] > > [1]

Re: [arch-dev-public] Automating package conflict resolution whenever possible (xorgproto/libxfont dependency conflict)

2018-02-13 Thread Doug Newgard via arch-dev-public
On Wed, 14 Feb 2018 00:56:33 +0100 Baptiste Jonglez wrote: > Hi, > > Eli and I disagree about how dependency conflicts should be handled when > packaging. This was prompted by the libxfont dependency conflict arising > from recent xorgproto changes [1]. > > My

[arch-dev-public] Automating package conflict resolution whenever possible (xorgproto/libxfont dependency conflict)

2018-02-13 Thread Baptiste Jonglez
Hi, Eli and I disagree about how dependency conflicts should be handled when packaging. This was prompted by the libxfont dependency conflict arising from recent xorgproto changes [1]. My position in this case: it would be really easy to avoid this conflict, by adding libxfont to the Replaces()

Re: [arch-dev-public] Test repository with gcc8

2018-02-13 Thread Bartłomiej Piotrowski via arch-dev-public
On 2018-02-13 16:13, Eli Schwartz via arch-dev-public wrote: > On 02/13/2018 09:29 AM, Bartłomiej Piotrowski via arch-dev-public wrote: I have updated gcc in the repository to snapshot from 2018-02-11 (r257571). Additionally, if you have access to soyuz, the repo can be easily used

Re: [arch-dev-public] Test repository with gcc8

2018-02-13 Thread Eli Schwartz via arch-dev-public
On 02/13/2018 09:29 AM, Bartłomiej Piotrowski via arch-dev-public wrote: >>> I have updated gcc in the repository to snapshot from 2018-02-11 >>> (r257571). Additionally, if you have access to soyuz, the repo can be >>> easily used in build chroots with 'gcc8-x86_64-build' command (which >>> also

Re: [arch-dev-public] Test repository with gcc8

2018-02-13 Thread Bartłomiej Piotrowski via arch-dev-public
On 2018-02-13 15:19, Baptiste Jonglez wrote: > On 13-02-18, Bartłomiej Piotrowski via arch-dev-public wrote: >> On 2018-02-04 14:02, Bartłomiej Piotrowski via arch-dev-public wrote: >>> Hi all, >>> >>> I've prepared external repository with GCC 8 built from trunk (as there >>> is no stable release

Re: [arch-dev-public] Test repository with gcc8

2018-02-13 Thread Bartłomiej Piotrowski via arch-dev-public
On 2018-02-04 14:02, Bartłomiej Piotrowski via arch-dev-public wrote: > Hi all, > > I've prepared external repository with GCC 8 built from trunk (as there > is no stable release yet) that also contains glibc 2.27 and binutils 2.30. > > [gcc8] > Server = http://pkgbuild.com/~bpiotrowski/gcc8/ >