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

2018-02-15 Thread Baptiste Jonglez
On 14-02-18, Allan McRae via arch-dev-public wrote: > Just because I had to look up the details of this > > > - xorgproto replaces a lot of packages, including fontsproto: > :: Replace fontsproto with extra/xorgproto? [Y/n] > > - libxfont requires fontsproto, so this causes the following:

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

2018-02-14 Thread Allan McRae via arch-dev-public
On 14/02/18 22:28, Florian Pritz via arch-dev-public wrote: > How about having this feature in pacman, maybe with an indicator if the > package is still in a repository? pacman -Qtd

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

2018-02-14 Thread Florian Pritz via arch-dev-public
On 14.02.2018 12:55, Allan McRae via arch-dev-public wrote: > Funny thing... people using yaourt probably removed this package as I > believe it highlights dependencies that are no longer needed after an > upgrade! How about having this feature in pacman, maybe with an indicator if the package

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

2018-02-14 Thread Allan McRae via arch-dev-public
Just because I had to look up the details of this - xorgproto replaces a lot of packages, including fontsproto: :: Replace fontsproto with extra/xorgproto? [Y/n] - libxfont requires fontsproto, so this causes the following: :: libxfont: removing fontsproto breaks dependency

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

2018-02-14 Thread Alad Wenter via arch-dev-public
> Alad Wenter via arch-dev-public hat am 14. > Februar 2018 um 12:26 geschrieben: > > > > Baptiste Jonglez hat am 14. Februar 2018 um > > 10:19 geschrieben: > > > > Quite frankly, the packaging issue itself is minor, I was just

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

2018-02-14 Thread Alad Wenter via arch-dev-public
> Baptiste Jonglez hat am 14. Februar 2018 um > 10:19 geschrieben: > > Quite frankly, the packaging issue itself is minor, I was just surprised > of the way it was handled: spending time to close several bug reports > about the issue and telling people that they are

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

2018-02-14 Thread Baptiste Jonglez
On 13-02-18, Eli Schwartz via arch-dev-public wrote: > 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

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