Hi Matthias,

I did not know if someone would get a reply if the ticket was closed: can
you confirm this for me. I am new: so I would ask that you review your
comments carefully even if it means just helping/self resolving with good
feedback: relevant information.

On Mon, Mar 4, 2019 at 4:09 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the python package:
>
> #923734: Python needs updating: version push
>
> It has been closed by Matthias Klose <d...@debian.org>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Matthias Klose <
> d...@debian.org> by
> replying to this email.
>
>
> --
> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> ---------- Forwarded message ----------
> From: Matthias Klose <d...@debian.org>
> To: 923...@bugs.debian.org, 923734-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 5 Mar 2019 00:06:02 +0100
> Subject: Re: Bug#923734: closed by Matthias Klose <d...@debian.org> (Re:
> Bug#923734: Python needs updating: version push)
> On 04.03.19 23:29, Brian Holaday wrote:
> > I seem to be having issues then with installing: 3.5.3 on Stretch.
> >
> > # sudo apt-get install python3.5
> >> #python3.5 is already the newest version (3.5.3-1+deb9u1).
> >
> > Is Python 3.5 only for Buster or SID?
>
> no, for stretch. There is no 3.5 and 3.6. for buster.  Please stop
> re-opening
> this issue.
>
> > On Mon, Mar 4, 2019 at 12:48 PM Debian Bug Tracking System <
> > ow...@bugs.debian.org> wrote:
> >
> >> This is an automatic notification regarding your Bug report
> >> which was filed against the python package:
> >>
> >> #923734: Python needs updating: version push
> >>
> >> It has been closed by Matthias Klose <d...@debian.org>.
> >>
> >> Their explanation is attached below along with your original report.
> >> If this explanation is unsatisfactory and you have not received a
> >> better one in a separate message then please contact Matthias Klose <
> >> d...@debian.org> by
> >> replying to this email.
> >>
> >>
> >> --
> >> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> >> Debian Bug Tracking System
> >> Contact ow...@bugs.debian.org with problems
> >>
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: Matthias Klose <d...@debian.org>
> >> To: Brian Holaday <br...@codemonkeyrawks.net>, 923...@bugs.debian.org,
> >> 923734-d...@bugs.debian.org
> >> Cc:
> >> Bcc:
> >> Date: Mon, 4 Mar 2019 20:46:16 +0100
> >> Subject: Re: Bug#923734: Python needs updating: version push
> >> On 04.03.19 19:37, Brian Holaday wrote:
> >>> Package: python
> >>> Version: 2.7.13-2
> >>> severity: important
> >>>
> >>> Issue:
> >>>
> >>> Python 3.7.2 has been released out for some time now. Can we get an
> >> update
> >>> pushed out to stretch-backports
> >>
> >> no, not doing that.
> >>
> >>> or SID at some point?
> >>
> >> it's there "for some time now"
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: Brian Holaday <br...@codemonkeyrawks.net>
> >> To: sub...@bugs.debian.org
> >> Cc:
> >> Bcc:
> >> Date: Mon, 4 Mar 2019 11:37:37 -0700
> >> Subject: Python needs updating: version push
> >> Package: python
> >> Version: 2.7.13-2
> >> severity: important
> >>
> >> Issue:
> >>
> >> Python 3.7.2 has been released out for some time now. Can we get an
> update
> >> pushed out to stretch-backports or SID at some point?
> >>
> >
>
>
> ---------- Forwarded message ----------
> From: Brian Holaday <br...@codemonkeyrawks.net>
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Mar 2019 11:37:37 -0700
> Subject: Python needs updating: version push
> Package: python
> Version: 2.7.13-2
> severity: important
>
> Issue:
>
> Python 3.7.2 has been released out for some time now. Can we get an update
> pushed out to stretch-backports or SID at some point?
>

Reply via email to