Your message dated Sat, 28 Jan 2023 08:31:05 -0400
with message-id <[email protected]>
and subject line Re: Bug#880362: please register the new release of python3 on 
the transition tracker
has caused the Debian Bug report #880362,
regarding please register the new release of python3 on the transition tracker
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
880362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880362
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3
Version: 3.5.3-3
Severity: normal

Dear Maintainer,

Thank you for maintaining python3. It is probably one of the most
crucial part of Debian.

I was doing the normal update/upgrade cycle for testing when I saw
whole lot of packages were being kept back.

I had a look and saw that almost all the packages which were being
kept back were due to them being incompatible with the new python3
i.e. python3=3.6.3-1 which has now come onto buster.

I had a look at the transition tracker made by ben and realized that
it was not there.

https://release.debian.org/transitions/

I did however see #874604 where somebody requested the new version of
python3 and if memory serves me correct, it is one of the release
goals of buster is to have this specific release in it.

I did also have a look at the threads of the ML debian-release to see
if I could any mention of the transition to the new version.

https://lists.debian.org/debian-release/2017/10/threads.html

but failed to do so.

I do know and realize that it possibly might be like one of the
permanent trackers and might take a lot longer as lots of packages
might probably directly or indirectly be impacted by this transition
and may need source or binary rebuilds.

It is very much possible that you may already be doing the above, but
if not would request you so people are not unduly alarmed.

FWIW, here is one of the instances I tried to update.

─[$] sudo aptitude install python3 python3-dev python3-all python3-uno
python3-venv sigil hplip gir1.2-lokdocview-0.1
libreoffice-style-breeze  rhythmbox-plugins libreoffice-math
libreoffice-script-provider-js libreoffice-report-builder-bin
libreoffice-sdbc-postgresql libreofficekit-data
libreoffice-style-hicontrast libreoffice-style-sifr
libreoffice-sdbc-firebird libreoffice-script-provider-python
libreoffice-style-galaxy libreoffice-help-en-us libreoffice-ogltrans
blueman libboost-mpi-python1.62.0 libreoffice-sdbc-hsqldb
libreoffice-script-provider-bsh printer-driver-hpijs libreoffice
libreoffice-core libreoffice-pdfimport
libreoffice-avmedia-backend-gstreamer libreoffice-report-builder
libreoffice-style-tango rhythmbox-plugin-cdrecorder
libboost-mpi-python1.63.0 libboost-mpi-python1.63-dev libboost-all-dev
libboost-all-dev is already installed at the requested version (1.62.0.1)
libboost-all-dev is already installed at the requested version (1.62.0.1)
The following NEW packages will be installed:
  libboost-mpi-python1.63-dev{b} libboost-mpi-python1.63.0
libboost-mpi1.63-dev{ab} libboost-mpi1.63.0{a}
libboost-python1.63.0{a}
  libboost-serialization1.63-dev{ab} libboost-serialization1.63.0{a}
libboost1.63-dev{ab} libpython3.6-dev{a} python3.6-dev{a}
  python3.6-venv{a}
The following packages will be REMOVED:
  libboost-mpi-python1.62.0{u} libpython3.5-dev{u} python3.5-dev{u}
The following packages will be upgraded:
  blueman gir1.2-lokdocview-0.1 gir1.2-rb-3.0 hplip hplip-data
libhpmud0 liblibreofficekitgtk libpython3-dev libpython3-stdlib
libreoffice libreoffice-avmedia-backend-gstreamer libreoffice-base
libreoffice-base-core libreoffice-base-drivers libreoffice-calc
libreoffice-common libreoffice-core libreoffice-draw
libreoffice-evolution libreoffice-gnome libreoffice-gtk3
libreoffice-help-en-us libreoffice-impress libreoffice-java-common
libreoffice-math libreoffice-ogltrans libreoffice-pdfimport
libreoffice-report-builder libreoffice-report-builder-bin
libreoffice-script-provider-bsh libreoffice-script-provider-js
libreoffice-script-provider-python libreoffice-sdbc-firebird
libreoffice-sdbc-hsqldb libreoffice-sdbc-postgresql
libreoffice-style-breeze libreoffice-style-galaxy
libreoffice-style-hicontrast libreoffice-style-sifr
libreoffice-style-tango libreoffice-writer libreofficekit-data
librhythmbox-core10 libsane-hpaio printer-driver-hpcups
printer-driver-hpijs python3 python3-all python3-dev python3-minimal
python3-uno python3-venv rhythmbox rhythmbox-data
rhythmbox-plugin-cdrecorder rhythmbox-plugins sigil

57 packages upgraded, 11 newly installed, 3 to remove and 57 not upgraded.
Need to get 11.0 MB/120 MB of archives. After unpacking 85.6 MB will be used.
The following packages have unmet dependencies:
 libboost-serialization1.63-dev : Conflicts:
libboost-serialization1.62-dev but 1.62.0+dfsg-4+b1 is installed and
it is kept back
 gitsome : Depends: python3 (< 3.6) but 3.6.3-1 is to be installed
 libboost-mpi-python1.63-dev : Conflicts: libboost-mpi-python1.62-dev
but 1.62.0+dfsg-4+b1 is installed and it is kept back
 libboost-mpi1.63-dev : Conflicts: libboost-mpi1.62-dev but
1.62.0+dfsg-4+b1 is installed and it is kept back
 libboost1.63-dev : Conflicts: libboost1.62-dev but 1.62.0+dfsg-4+b1
is installed and it is kept back
 libboost-mpi-python1.62-dev : Depends: libboost-mpi-python1.62.0 (=
1.62.0+dfsg-4+b1) but it is not going to be installed
^C

Hoping to see a transition page soonish so source or binary rebuilds
are done and we can have the new shiny python3 on our systems without
issues.


-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (600, 'testing-debug'), (600, 'testing'), (1,
'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3 depends on:
ii  dh-python          2.20170125
ii  libpython3-stdlib  3.5.3-3
ii  python3-minimal    3.5.3-3
ii  python3.5          3.5.4-4

python3 recommends no packages.

Versions of packages python3 suggests:
ii  python3-doc   3.6.3-1
ii  python3-tk    3.6.2-1
ii  python3-venv  3.5.3-3

-- no debconf information


-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

--- End Message ---
--- Begin Message ---
Hi shirish (2017.10.30_17:26:31_-0400)

The 3.6 transition is long-over.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

--- End Message ---

Reply via email to