Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] buildbot, deps, python 2: remove
Date: Sat, 28 Sep 2024 11:03:13 +0200	[thread overview]
Message-ID: <20240928090313.ED6EC2C8CE@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38731@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 596 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/38731#issuecomment-2380574190

Comment:
I've moved the following packages:
```
python -> python2
python-devel -> python2-devel
python-tkinter -> python2-tkinter
python-pip -> python2-pip
python-setuptools -> python2-setuptools
```
`python` and `python-devel` became a metapackage with a warning about impending migration to python 3; `python-pip`, `python-setuptools`, and `python-tkinter` became transitional packages.

I put your name on `python2-pip` and `python2-setuptools`.

  parent reply	other threads:[~2024-09-28  9:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17  5:06 [PR PATCH] [NOMERGE] buildbot & deps: remove classabbyamp
2022-08-17  5:16 ` [PR PATCH] [Updated] " classabbyamp
2022-08-17  5:37 ` classabbyamp
2022-08-17  5:42 ` classabbyamp
2022-08-17  5:43 ` classabbyamp
2022-08-17  5:58 ` classabbyamp
2022-08-17 21:56 ` classabbyamp
2022-08-17 22:22 ` classabbyamp
2022-08-17 22:29 ` classabbyamp
2022-08-17 22:31 ` classabbyamp
2022-08-17 22:40 ` classabbyamp
2022-08-17 22:54 ` classabbyamp
2022-08-17 23:16 ` classabbyamp
2022-08-17 23:24 ` classabbyamp
2022-08-17 23:52 ` classabbyamp
2022-10-06 10:59 ` classabbyamp
2022-10-06 11:38 ` classabbyamp
2022-10-06 11:52 ` classabbyamp
2023-01-05  1:59 ` github-actions
2023-01-05  4:31 ` classabbyamp
2023-04-28  1:53 ` github-actions
2023-07-28  1:48 ` github-actions
2023-10-11 21:45 ` [PR PATCH] [Updated] " classabbyamp
2024-04-18  0:06 ` classabbyamp
2024-04-18  0:07 ` [NOMERGE] buildbot, deps, python 2: remove classabbyamp
2024-04-18  0:07 ` classabbyamp
2024-04-18  0:18 ` [PR PATCH] [Updated] " classabbyamp
2024-09-27 19:17 ` leahneukirchen
2024-09-28  8:57 ` [PR PATCH] [Updated] " classabbyamp
2024-09-28  9:01 ` classabbyamp
2024-09-28  9:02 ` classabbyamp
2024-09-28  9:03 ` classabbyamp [this message]
2024-09-28  9:15 ` [PR PATCH] [Updated] " classabbyamp
2024-09-29  3:21 ` [PR PATCH] [Merged]: buildbot, deps: remove; python -> python2 classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240928090313.ED6EC2C8CE@inbox.vuxu.org \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).