AFAIK this is 32 Bit, but to be honest, I don’t know how to find out, if it really is 32 Bit.
Could you tell me how? Or if you already know, that it is 32 Bit, could you please add it to the list of supported 32 Bit libs?
flashplugin-downloader is a transitional package… (32 bit flash hasn’t been supported on linux for a while…)
google-android-build-tools-installer - is this used by anyone? Looks like a leftover from 2016
Did someone request the following?
pixbros/pixfrogger/fenix open source 2d pixel games
gogo - multiverse mp3 encoder
gatos - ATI All-in-Wonder TV capture software
I’d love the full list of source packages (doesn’t have to be posted here).
19.10 currently has the 435 nvidia drivers, and 418 only as transitional packages to upgrade to newer.
Is the version only listed as kind of example since they where what 19.10 had when they where put on the list?
I hope it will always be the newest nvidia drivers available in amd64 in the distribution, and also the still supported legacy drivers for older GPUs.
Really need the 32-bit version of Timidity. I know of some old Windows games/programs that use midi files and of course if they’re 32-bit they need 32-bit WINE and 32-bit timidity
There is no package by this name in the Ubuntu archive. Can you please either give us the name of a .deb package installed from the Ubuntu archive on your system (from dpkg -l '*:i386'), or else a URL where the hpcups that you’re using can be downloaded?
There is a package named printer-driver-hpcups in the Ubuntu archive, but I see nothing that suggests it needs to be installed as a 32-bit package.
Please see lp:~vorlon/+junk/get-i386/ for the scripts used to generate the list of source packages.
Regarding the packages you ask whether we should include them: by design we are trying to be conservative about dropping packages if there’s any chance they might have a legitimate use as 32-bit. That certainly includes 32-bit-only packages from the archive, whether or not they have any known users. They at least have a Debian maintainer, and it’s a small number of packages to keep buildable, so I don’t think we should spend much effort trying to make this list even smaller.
Thanks, those are the “multilib” forms of the packages (amd64 .deb packages containing 32-bit libs). The regular package names would be libncurses5 and zlib1g; libncurses5 is already on our list, and we can add zlib1g explicitly (it is already included in practice because it’s a dependency of many other things).
You say “of course”, but this is not at all obvious. Timidity is a program, not a library, and 32-bit wine should be able to execute a 64-bit timidity from the host. Can you give more detail about why you need the 32-bit version?
Maybe I am wrong but a 32-bit windows program requires 32-bit WINE and I remember years ago with an old game that used midi files. I needed the 32-bit timidity. As mixing 32-bit WINE and 64-bit timidity would not work. If you can show that it’s not needed then fair enough. But I’m 90% sure both have to be 32-bit.
Wine also sometimes needs these:
gstreamer1.0-libav
gstreamer1.0-plugins-bad
gstreamer1.0-plugins-good
gstreamer1.0-plugins-ugly
I’ll be soon adding them as recommends or suggests in src:wine and src:wine-development, see LP #1817244
Thanks, that’s useful information. Obviously the current source package count doesn’t include this; I’m not concerned about their addition, but I am concerned that they get included before we start making any changes to the archive, since it’s much easier to include these now than to rebootstrap them later. How can we make sure this gets done in Ubuntu 19.10?