No idea what to do with pdf-stapler and what can happen in future from
upstream. At least, they are aware of python3.
Am 07.11.19 um 13:01 schrieb Petr Viktorin:
raphgro
pdf-stapler
(→ PY2)
python2-staplelib (→ PY2)
___
devel mailing list
On Thu, Nov 7, 2019 at 7:02 AM Petr Viktorin wrote:
> jsmith
>asterisk
> (→ PY2)
> asterisk-* (→ asterisk → PY2)
>
Asterisk has very few dependencies on Python (just some contributed scripts
for use in debugging reference counters in the code, if I recall
correctly). That being
On 11/7/19 2:34 PM, Miro Hrončok wrote:
On 07. 11. 19 13:59, Felix Schwarz wrote:
Am 07.11.19 um 13:01 schrieb Petr Viktorin:
If this took you by surprise, don't panic. It's possible to change the
default. Let us know and we'll work things out.
Somehow I feel like I don't understand the
On Thu, Nov 07, 2019 at 01:01:09PM +0100, Petr Viktorin wrote:
> Dear maintainers,
> here is an updated list of packages that (transitively, at build or run
> time) require Python 2 and have not yet got a FESCo exception to do so.
> If you were bcced on this e-mail, it affects one or more of your
On 07. 11. 19 14:59, Felix Schwarz wrote:
Am 07.11.19 um 14:57 schrieb Felix Schwarz:
Is there some automation to remove "python2-" subpackages or do you plan some
"single hero"-style changes? If neither what is the plan for maintainers who
just don't do anything?
I should do more reading
Am 07.11.19 um 14:57 schrieb Felix Schwarz:
> Is there some automation to remove "python2-" subpackages or do you plan some
> "single hero"-style changes? If neither what is the plan for maintainers who
> just don't do anything?
I should do more reading before replying to emails :-/
Change
Am 07.11.19 um 14:47 schrieb Miro Hrončok:
> On 07. 11. 19 14:41, Felix Schwarz wrote:
>> However the wiki page says:
>> "All packages depending on any python2 package will be removed."
>
> All "binary" packages.
(...)
>> So maybe I just misunderstood the change. What happens when a package like
On 07. 11. 19 14:41, Felix Schwarz wrote:
Hi Miro,
Am 07.11.19 um 14:34 schrieb Miro Hrončok:
We actually are wiping out the entire Python 2 ecosystem here, that is the
point.
Ok, maybe I misunderstood the change.
Just to be clear: I'm fine with the Python 2 package removal (though I expect
Hi Miro,
Am 07.11.19 um 14:34 schrieb Miro Hrončok:
> We actually are wiping out the entire Python 2 ecosystem here, that is the
> point.
Ok, maybe I misunderstood the change.
Just to be clear: I'm fine with the Python 2 package removal (though I expect
I'll continue to develop Python 2 code
On 07. 11. 19 13:59, Felix Schwarz wrote:
Am 07.11.19 um 13:01 schrieb Petr Viktorin:
If this took you by surprise, don't panic. It's possible to change the
default. Let us know and we'll work things out.
Somehow I feel like I don't understand the report – or we are approaching an
(almost)
On 07. 11. 19 14:04, Jun Aruga wrote:
## What exactly is happening?
The formal change proposal is here:
https://fedoraproject.org/wiki/Changes/RetirePython2
Packages requiring Python 2 will be removed starting November 15 (unless
they have an exception).
Components with all essential
> ## What exactly is happening?
>
> The formal change proposal is here:
> https://fedoraproject.org/wiki/Changes/RetirePython2
>
> Packages requiring Python 2 will be removed starting November 15 (unless
> they have an exception).
> Components with all essential subpackages removed will be
Am 07.11.19 um 13:01 schrieb Petr Viktorin:
> If this took you by surprise, don't panic. It's possible to change the
> default. Let us know and we'll work things out.
Somehow I feel like I don't understand the report – or we are approaching an
(almost) unmitigated disaster here: There are so
Dear maintainers,
here is an updated list of packages that (transitively, at build or run
time) require Python 2 and have not yet got a FESCo exception to do so.
If you were bcced on this e-mail, it affects one or more of your packages.
The default action will be to remove such packages
14 matches
Mail list logo
