On 12/20/2017 06:17 PM, Nils Freydank wrote:
> Am Mittwoch, 20. Dezember 2017, 17:48:54 CET schrieb kuzetsa:
>> On 12/16/2017 10:14 AM, Nils Freydank wrote:
>>> Am Dienstag, 5. Dezember 2017, 23:41:45 CET schrieb kuzetsa:
On 12/05/2017 05:18 PM, Nils Freydank wrote:
> 5. Reasons for warnin
Mike Gilbert posted on Thu, 21 Dec 2017 09:10:09 -0500 as excerpted:
> On Thu, Dec 21, 2017 at 2:44 AM, Matthew Thode
> wrote:
>> On 17-12-21 08:34:31, Michał Górny wrote:
>>> W dniu czw, 21.12.2017 o godzinie 05∶29 +, użytkownik Duncan
>>> napisał:
>>> > Michał Górny posted on Wed, 20 Dec 20
On 17-12-21 09:10:09, Mike Gilbert wrote:
> On Thu, Dec 21, 2017 at 2:44 AM, Matthew Thode
> wrote:
> > On 17-12-21 08:34:31, Michał Górny wrote:
> >> W dniu czw, 21.12.2017 o godzinie 05∶29 +, użytkownik Duncan
> >> napisał:
> >> > Michał Górny posted on Wed, 20 Dec 2017 14:40:27 +0100 as exc
On Thu, 21 Dec 2017 10:10:30 -0500
Michael Orlitzky wrote:
> The "cracklib" USE flag has long (since 2007ish) been enabled by
> default for all profiles. But, the features that it provides are not
> critical for any of the packages that use it: typically, the library
> is used to evaluate a candi
On Thu, Dec 21, 2017 at 03:03:21PM +, Roy Bamford wrote:
> > So, I guess this means that the quality of the ~arch tree is supposed
> > to
> > be somewhat lower than the quality of the stable tree.
> >
> > William
> >
> >
>
> William,
>
> I've been running ~arch everywhere since May 2002 an
The "cracklib" USE flag has long (since 2007ish) been enabled by
default for all profiles. But, the features that it provides are not
critical for any of the packages that use it: typically, the library
is used to evaluate a candidate password and to prevent the user from
choosing a weak one.
Sinc
On 2017.12.21 00:35, William Hubbs wrote:
> On Wed, Dec 20, 2017 at 07:12:45PM -0500, Michael Orlitzky wrote:
> > On 12/20/2017 06:58 PM, William Hubbs wrote:
> > >
> > > There already is an overlay for dying packages, it is called
> graveyard,
> > > but no one is putting things there.
> > >
> >
On 12/21/17 15:11, Rich Freeman wrote:
> Part of me wonders if issues with stable are causing issues with
> ~arch. If stable is regarded as stale that is going to push people
> into ~arch who really intend to have stable systems. That said you do
> want testing systems to have a reasonably low
On Thu, Dec 21, 2017 at 6:01 AM, Thomas Deutschmann wrote:
> On 2017-12-21 01:35, William Hubbs wrote:
>> ~arch *will* have breakages from time to time, sometimes major
>> breakages, until they are masked or fixed. We are not supposed to leave
>> major breakages there, but ~arch is definitely not
On Thu, Dec 21, 2017 at 2:44 AM, Matthew Thode
wrote:
> On 17-12-21 08:34:31, Michał Górny wrote:
>> W dniu czw, 21.12.2017 o godzinie 05∶29 +, użytkownik Duncan
>> napisał:
>> > Michał Górny posted on Wed, 20 Dec 2017 14:40:27 +0100 as excerpted:
>> >
>> > In all this I don't see an answer to
On 12/21/17 12:19 AM, Jason Zaman wrote:
> On Wed, Dec 20, 2017 at 06:29:57PM +0100, Hans de Graaff wrote:
>> On Wed, 2017-12-20 at 18:02 +0100, Michał Górny wrote:
>>>
>>> sys-process/vixie-cron
>>
>> My understanding is that vixie-cron is no longer maintained and sys-
>> process/cronie is the d
On 2017-12-21 01:35, William Hubbs wrote:
> ~arch *will* have breakages from time to time, sometimes major
> breakages, until they are masked or fixed. We are not supposed to leave
> major breakages there, but ~arch is definitely not for the faint of
> heart. If you are using ~arch, you are expecte
# Andreas Sturmlechner (21 Dec 2017)
# Dead upstream, depends on dead Qt4.
# Bug #629032. Masked for removal in 30 days.
media-gfx/wally
# Andreas Sturmlechner (21 Dec 2017)
# Dead upstream, depends on dead Qt4.
# Bug #637108. Masked for removal in 30 days.
app-cdr/qpxtool
14 matches
Mail list logo
