# Georgy Yakovlev (2020-09-02)
# Masked for removal. No revdeps.
dev-python/ansimarkup
On 2020-09-02 14:08, Andreas Sturmlechner wrote:
> On Wednesday, 2 September 2020 19:42:33 CEST Michael Orlitzky wrote:
>> New USE flags generally change dependencies (as is the case here), so a
>> new revision ensures that people are forced to install the ebuild that
>> supports python-3.8.
On Wednesday, 2 September 2020 19:42:33 CEST Michael Orlitzky wrote:
> New USE flags generally change dependencies (as is the case here), so a
> new revision ensures that people are forced to install the ebuild that
> supports python-3.8. Otherwise, you will eventually find a lot of people
> stuck
# Bernard Cafarelli (2020-09-02)
# Abandoned upstream in favor of media-libs/libinsane
# No more in-tree users
# Removal in 30 days. Bug #740100
dev-python/pyinsane
--
Bernard Cafarelli (Voyageur)
Gentoo developer
On 2020-09-02 13:23, Sam James wrote:
>
> Please request stabilisation of your Python 3.8+ changes at the 30 days
> point, or earlier if it’s a trivial revbump
> (as new Python targets are equivalent to new USE flags, there is no real need
> for a revbump unless doing other tidying
> whilst
> On 1 Sep 2020, at 12:02, Michał Górny wrote:
>
> Hello,
>
> [snip]
> Python 3.8 is planned to become the default on 2020-12-01.
>
Note that this means we need to keep in mind stabilisation of Python 3.8+
supporting-packages going forward.
Please request stabilisation of your Python 3.8+
Portage's env-update currently transforms the environment information
from /etc/env.d into /etc/profile.env, which is typically sourced by
every user session, setting up its environment.
However, /etc/profile.env is not sourced by systemd user
services. Instead, for the definition of a systemd
On Tue, 2020-09-01 at 08:06 -0400, Rich Freeman wrote:
> On Tue, Sep 1, 2020 at 7:02 AM Michał Górny wrote:
> > QA reports provide a list [2] and a graph [3] of packages needing
> > porting.
>
> These lists would be far more useful if they actually listed the
> maintainer(s) of each package.
On 9/1/20 11:08 PM, Michał Górny wrote:
> On Tue, 2020-09-01 at 19:59 -0700, Zac Medico wrote:
>> Automatically detect regular expressions when the search string
>> contains any of these regular expression characters or character
>> sequences:
>>
>> ^ $ * [ ] { } | ? .+
>
> Isn't this going to
On 9/1/20 11:08 PM, Michał Górny wrote:
> On Tue, 2020-09-01 at 19:59 -0700, Zac Medico wrote:
>> Automatically detect regular expressions when the search string
>> contains any of these regular expression characters or character
>> sequences:
>>
>> ^ $ * [ ] { } | ? .+
>
> Isn't this going to
On Tue, 2020-09-01 at 19:59 -0700, Zac Medico wrote:
> Automatically detect regular expressions when the search string
> contains any of these regular expression characters or character
> sequences:
>
> ^ $ * [ ] { } | ? .+
Isn't this going to break search for gtk+?
>
> This simplifies
11 matches
Mail list logo
