Performing dist-upgrade on powerpc and ppc64

[John Paul Adrian Glaubitz]

Hello,

I miss python2.7 though. python2.7-minimal appears to be intact, but I
need more modules to compile ArcticFox. I suppose what I need is in 
libpython2.7-stdlib, but this needs libtirpc3:powerpc which is a t64
transitioning package.
Is 2.7 gone for good or is it a temporary issue on PPC?

Python 2.7 was removed from Debian unstable in December 2022 [1]. The
motivations for the removal are explained in [2].

If still needed, the package can be rebuilt from the older sources
against the current updated shared library t64 packages [3].

Adrian

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027108
[2] https://wiki.debian.org/Python/2Removal
[3] http://snapshot.debian.org/package/python2.7/

[Christian Marillat]

Hi,

Hi,


[...]

In case of unexpected breakage, please report it to the debian-powerpc mailing list.

Thanks for your work.

Could you upgrade qt6-multimedia with your patch from #1057050 ?

Christian

[John Paul Adrian Glaubitz]

Hello,

Post by Christian Marillat
Could you upgrade qt6-multimedia with your patch from #1057050 ?

Sure, I can do that. I'm a bit underwhelmed that the maintainer still
hasn't managed to fix the problem in unstable. *bummer*


Adrian

[Riccardo Mottola]

Hi Adrian,

First run "apt update", then "apt upgrade" and make sure every package is updated without
issues. Once that has passed, you may try to run "apt dist-upgrade" but before you confirm
the dist-upgrade, make sure that nothing is purged you still need.
In case of unexpected breakage, please report it to the debian-powerpc mailing list.

On a working PowerBook, I did an upgrade, there were a lot of packages
kept back, but some upgrades were performed and no issues reported.


However, I'm coming from a "dirty" situation on my iBook, since I did an
in-between dist-upgrade.
Mostly back to function, with important things like git.

I miss python2.7 though. python2.7-minimal appears to be intact, but I
need more modules to compile ArcticFox. I suppose what I need is in 
libpython2.7-stdlib, but this needs libtirpc3:powerpc which is a t64
transitioning package.

Is 2.7 gone for good or is it a temporary issue on PPC?

Thanks
Riccardo

[Riccardo Mottola]

Hi Adrian,

Post by John Paul Adrian Glaubitz
Python 2.7 was removed from Debian unstable in December 2022 [1]. The
motivations for the removal are explained in [2].

I supposed so, just asked for confirmation. I don't care much about the
motivations - I need it as a build dependency. I understand a minimal
build only python2 retained for some time (no more?). ArcticFox is not
the only app depending python2.7 generally, butperhaps in the Debian DB?
I know Firefox eventually migrated to py3, but it took a long time and
currently I don't have the resources to folow it - simply because I
don't know python and don't know what is needed.

Post by John Paul Adrian Glaubitz
If still needed, the package can be rebuilt from the older sources
against the current updated shared library t64 packages [3].

For now, it is the best solution for me. Longer-term I need a better
solution...
No problem for me trying to rebuild, but I never built something which
did not have a "debian source".
I suppose I might need some recursion and tweaking, needing also
libpython2.7-stdlib and perhaps other dependencies I will discover.


From [3] I get 3 files. I put them in a directory.

I also checked https://packages.debian.org/bullseye/python2.7 which
shows the same thing.

I expected to be able to download a single source package, like
"deb-src" had.


So I run

$ dpkg-buildpackage -us -uc

but get:
dpkg-buildpackage: error: cannot open file debian/changelog: No such
file or directory

I clearly miss some stupid setup setp. Can you guess off-head what I need?


Thanks,
Riccardo

Post by John Paul Adrian Glaubitz
[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027108
[2]https://wiki.debian.org/Python/2Removal
[3]http://snapshot.debian.org/package/python2.7/

[Eric Ramsey]

I will note that my install is currently having issues with gnutls.
```
The following packages have unmet dependencies:
connman : Depends: libgnutls30 (>= 3.7.5) but it is not installable
dirmngr : Depends: libgnutls30 (>= 3.7.5) but it is not installable
gkrellm : Depends: libgnutls30 (>= 3.7.0) but it is not installable
glib-networking : Depends: libgnutls30 (>= 3.7.5) but it is not installable
libapt-pkg-perl : Depends: libapt-pkg6.0 (>= 2.1.20) but it is not installable
libarchive13 : Depends: libnettle8 but it is not installable
libavformat59 : Depends: libgnutls30 (>= 3.7.5) but it is not installable
libcups2 : Depends: libgnutls30 (>= 3.7.5) but it is not installable
libcurl3-gnutls : Depends: libgnutls30 (>= 3.7.5) but it is not installable
Depends: libnettle8 but it is not installable
libgnutls-openssl27 : Depends: libgnutls30 (= 3.7.9-2) but it is not
installable
libnm0 : Depends: libgnutls30 (>= 3.7.2) but it is not installable
libopenconnect5 : Depends: libgnutls30 (>= 3.7.5) but it is not installable
Depends: libhogweed6 but it is not installable
libvte-2.91-0 : Depends: libgnutls30 (>= 3.7.2) but it is not installable
network-manager : Depends: libgnutls30 (>= 3.7.2) but it is not installable
ntfs-3g : Depends: libgnutls30 (>= 3.7.2) but it is not installable
python3-samba : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba-common-bin : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba-dsdb-modules : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba-libs : Depends: libgnutls30 (>= 3.7.5) but it is not installable
samba-vfs-modules : Depends: libgnutls30 (>= 3.7.0) but it is not installable
wget : Depends: libgnutls30 (>= 3.7.2) but it is not installable
Depends: libnettle8 but it is not installable
xfce4-mailwatch-plugin : Depends: libgnutls30 (>= 3.7.0) but it is
not installable
```

On Sun, Apr 14, 2024 at 3:54 PM Riccardo Mottola

Post by Riccardo Mottola
Hi Adrian,

Post by John Paul Adrian Glaubitz
Python 2.7 was removed from Debian unstable in December 2022 [1]. The
motivations for the removal are explained in [2].

I supposed so, just asked for confirmation. I don't care much about the
motivations - I need it as a build dependency. I understand a minimal
build only python2 retained for some time (no more?). ArcticFox is not
the only app depending python2.7 generally, butperhaps in the Debian DB?
I know Firefox eventually migrated to py3, but it took a long time and
currently I don't have the resources to folow it - simply because I
don't know python and don't know what is needed.

Post by John Paul Adrian Glaubitz
If still needed, the package can be rebuilt from the older sources
against the current updated shared library t64 packages [3].

For now, it is the best solution for me. Longer-term I need a better
solution...
No problem for me trying to rebuild, but I never built something which
did not have a "debian source".
I suppose I might need some recursion and tweaking, needing also
libpython2.7-stdlib and perhaps other dependencies I will discover.
From [3] I get 3 files. I put them in a directory.
I also checked https://packages.debian.org/bullseye/python2.7 which
shows the same thing.
I expected to be able to download a single source package, like
"deb-src" had.
So I run
$ dpkg-buildpackage -us -uc
dpkg-buildpackage: error: cannot open file debian/changelog: No such
file or directory
I clearly miss some stupid setup setp. Can you guess off-head what I need?
Thanks,
Riccardo

Post by John Paul Adrian Glaubitz
[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027108
[2]https://wiki.debian.org/Python/2Removal
[3]http://snapshot.debian.org/package/python2.7/

[John Paul Adrian Glaubitz]

Post by Eric Ramsey
I will note that my install is currently having issues with gnutls.
```
connman : Depends: libgnutls30 (>= 3.7.5) but it is not installable
dirmngr : Depends: libgnutls30 (>= 3.7.5) but it is not installable
gkrellm : Depends: libgnutls30 (>= 3.7.0) but it is not installable
glib-networking : Depends: libgnutls30 (>= 3.7.5) but it is not installable
libapt-pkg-perl : Depends: libapt-pkg6.0 (>= 2.1.20) but it is not installable
libarchive13 : Depends: libnettle8 but it is not installable
libavformat59 : Depends: libgnutls30 (>= 3.7.5) but it is not installable
libcups2 : Depends: libgnutls30 (>= 3.7.5) but it is not installable
libcurl3-gnutls : Depends: libgnutls30 (>= 3.7.5) but it is not installable
Depends: libnettle8 but it is not installable
libgnutls-openssl27 : Depends: libgnutls30 (= 3.7.9-2) but it is not
installable
libnm0 : Depends: libgnutls30 (>= 3.7.2) but it is not installable
libopenconnect5 : Depends: libgnutls30 (>= 3.7.5) but it is not installable
Depends: libhogweed6 but it is not installable
libvte-2.91-0 : Depends: libgnutls30 (>= 3.7.2) but it is not installable
network-manager : Depends: libgnutls30 (>= 3.7.2) but it is not installable
ntfs-3g : Depends: libgnutls30 (>= 3.7.2) but it is not installable
python3-samba : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba-common-bin : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba-dsdb-modules : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba-libs : Depends: libgnutls30 (>= 3.7.5) but it is not installable
samba-vfs-modules : Depends: libgnutls30 (>= 3.7.0) but it is not installable
wget : Depends: libgnutls30 (>= 3.7.2) but it is not installable
Depends: libnettle8 but it is not installable
xfce4-mailwatch-plugin : Depends: libgnutls30 (>= 3.7.0) but it is
not installable
```

What commands did you perform?

Adrian

[Eric Ramsey]

That is the result after apt update, apt upgrade with 366 packages held
back and then running apt dist-upgrade

On Mon, Apr 15, 2024 at 1:07 AM John Paul Adrian Glaubitz <

Post by Eric Ramsey

Post by Eric Ramsey
I will note that my install is currently having issues with gnutls.
```
connman : Depends: libgnutls30 (>= 3.7.5) but it is not installable
dirmngr : Depends: libgnutls30 (>= 3.7.5) but it is not installable
gkrellm : Depends: libgnutls30 (>= 3.7.0) but it is not installable
glib-networking : Depends: libgnutls30 (>= 3.7.5) but it is not

installable

Post by Eric Ramsey
libapt-pkg-perl : Depends: libapt-pkg6.0 (>= 2.1.20) but it is not

installable

Post by Eric Ramsey
libarchive13 : Depends: libnettle8 but it is not installable
libavformat59 : Depends: libgnutls30 (>= 3.7.5) but it is not

installable

Post by Eric Ramsey
libcups2 : Depends: libgnutls30 (>= 3.7.5) but it is not installable
libcurl3-gnutls : Depends: libgnutls30 (>= 3.7.5) but it is not

installable

Post by Eric Ramsey
Depends: libnettle8 but it is not installable
libgnutls-openssl27 : Depends: libgnutls30 (= 3.7.9-2) but it is not
installable
libnm0 : Depends: libgnutls30 (>= 3.7.2) but it is not installable
libopenconnect5 : Depends: libgnutls30 (>= 3.7.5) but it is not

installable

Post by Eric Ramsey
Depends: libhogweed6 but it is not installable
libvte-2.91-0 : Depends: libgnutls30 (>= 3.7.2) but it is not

installable

Post by Eric Ramsey
network-manager : Depends: libgnutls30 (>= 3.7.2) but it is not

installable

Post by Eric Ramsey
ntfs-3g : Depends: libgnutls30 (>= 3.7.2) but it is not installable
python3-samba : Depends: libgnutls30 (>= 3.7.0) but it is not

installable

Post by Eric Ramsey
samba : Depends: libgnutls30 (>= 3.7.0) but it is not installable
samba-common-bin : Depends: libgnutls30 (>= 3.7.0) but it is not

installable

Post by Eric Ramsey
samba-dsdb-modules : Depends: libgnutls30 (>= 3.7.0) but it is not

installable

Post by Eric Ramsey
samba-libs : Depends: libgnutls30 (>= 3.7.5) but it is not installable
samba-vfs-modules : Depends: libgnutls30 (>= 3.7.0) but it is not

installable

Post by Eric Ramsey
wget : Depends: libgnutls30 (>= 3.7.2) but it is not installable
Depends: libnettle8 but it is not installable
xfce4-mailwatch-plugin : Depends: libgnutls30 (>= 3.7.0) but it is
not installable
```

What commands did you perform?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

[John Paul Adrian Glaubitz]

Hello,

Post by Riccardo Mottola
I supposed so, just asked for confirmation. I don't care much about the
motivations - I need it as a build dependency. I understand a minimal
build only python2 retained for some time (no more?). ArcticFox is not
the only app depending python2.7 generally, butperhaps in the Debian DB?
I know Firefox eventually migrated to py3, but it took a long time and
currently I don't have the resources to folow it - simply because I
don't know python and don't know what is needed.

You can fetch the source from here:

$ dget -u http://snapshot.debian.org/archive/debian/20220801T085926Z/pool/main/p/python2.7/python2.7_2.7.18-13.2.dsc

Then build the package with sbuild:

$ sbuild -d sid --arch-all --arch=powerpc python2.7_2.7.18-13.2.dsc


Adrian

[Riccardo Mottola]

Hi Adrian,

so you suggest to use powerful scripts.
Ok, got dget (from devscripts) and sbuild.
Added my user do sbuild group.

$ dget -uhttp://snapshot.debian.org/archive/debian/20220801T085926Z/pool/main/p/python2.7/python2.7_2.7.18-13.2.dsc
$ sbuild -d sid --arch-all --arch=powerpc python2.7_2.7.18-13.2.dsc

So sbuild complaints I need a chroot environment. I guess that helps
with build-dependencies only being temporary installed for the build, as
opposite to use dpkg-buildpackage directly?

How can I best chreate the chroot, best would be it using by local apt
cache perhaps, I'm unsure.

Take in account this is on an iBook G4, so not a server with big space.

I think I need the correct setup for sbuild-createchroot ? What
parameters do you suggest or used on your local system?

I am skimming through a debian guide [1] and perhaps Using
/var/cache/apt/archives/ as package cache is a good idea?


Riccardo


[1]
https://wiki.debian.org/sbuild#Automatic_setup_using_sbuild-debian-developer-setup

[Jeffrey Walton]

Post by Riccardo Mottola
Hi Adrian,
so you suggest to use powerful scripts.
Ok, got dget (from devscripts) and sbuild.
Added my user do sbuild group.

$ dget -uhttp://

snapshot.debian.org/archive/debian/20220801T085926Z/pool/main/p/python2.7/python2.7_2.7.18-13.2.dsc

$ sbuild -d sid --arch-all --arch=powerpc python2.7_2.7.18-13.2.dsc

So sbuild complaints I need a chroot environment. I guess that helps
with build-dependencies only being temporary installed for the build, as
opposite to use dpkg-buildpackage directly?
How can I best chreate the chroot, best would be it using by local apt
cache perhaps, I'm unsure.
Take in account this is on an iBook G4, so not a server with big space.
I think I need the correct setup for sbuild-createchroot ? What
parameters do you suggest or used on your local system?
I am skimming through a debian guide [1] and perhaps Using
/var/cache/apt/archives/ as package cache is a good idea?
[1]
https://wiki.debian.org/sbuild#Automatic_setup_using_sbuild-debian-developer-setup

In the old days, you could setup a chroot for PowerPC using the following.
I think it still works, but I recall something about using qemu-debootstrap
nowadays.

qemu-debootstrap --arch=powerpc --keyring
/usr/share/keyrings/debian-ports-archive-keyring.gpg \
--variant=buildd --exclude=debfoster unstable debian-powerpc
http://ftp.ports.debian.org/debian-ports

The Debian host can use any flavor of Debian. I usually use Stable for the
host.

The Debian chroot guest must use Unstable. Once you create the chroot
guest, open the guest's /etc/apt/sources.list and change it to Unstable.

Jeff

[John Paul Adrian Glaubitz]

Hi,

In the old days, you could setup a chroot for PowerPC using the following. I think it still works, but I recall something about using qemu-debootstrap nowadays.
qemu-debootstrap --arch=powerpc --keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg \
  --variant=buildd --exclude=debfoster unstable debian-powerpc http://ftp.ports.debian.org/debian-ports
The Debian host can use any flavor of Debian. I usually use Stable for the host.
The Debian chroot guest must use Unstable. Once you create the chroot guest, open the guest's /etc/apt/sources.list and change it to Unstable.

There is no need to use qemu-debootstrap these days, sbuild will just work
transparently once you have qemu-user installed.

Adrian

[John Paul Adrian Glaubitz]

Hello,

Post by Riccardo Mottola
So sbuild complaints I need a chroot environment. I guess that helps
with build-dependencies only being temporary installed for the build, as
opposite to use dpkg-buildpackage directly?
https://wiki.debian.org/sbuild

Adrian