When is an "active delopment version" promoted to "stable release"?

Asked by fprietog

I ask this because current stable release 6.02-1 for Focal Fossa doesn't work at all, giving this error repeated times:

   Traceback (most recent call last):
     File "/usr/share/nautilus-python/extensions/clamtk-gnome.py", line 64, in get_file_items
       tip=_('Scan %s for threats...') % file.get_name(),
   TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'str'

The Groovy Gorilla (active development) 6.03-1 release solved it and works well in Focal Fossa. But I'm wondering if it's necessary to wait to another Ubuntu release (20.10) to have it widely corrected.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu clamtk Edit question
Assignee:
No assignee Edit question
Solved by:
fprietog
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

I suggest you report a bug

Revision history for this message
fprietog (fprietog) said :
#2

First of all, thanks for answering.

My initial idea was that, but having tested the development version and seeing that it works, there is no bug...

Because it's like opening a bug for an old version; the answer should be that upgrade to latest version that solves it. In my opinion nobody should open a bug without testing the latest version available before.

But I wonder when it will be promoted to stable cause the tool is currently broken in the Focal Fossa just released.

Thanks again for your time.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

If there is a newer version in your package sources then it will be upgraded along with the other packages.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#4

What is the output of:

lsb_release -a; uname -a; apt-cache policy clamtk

Thanks

Revision history for this message
fprietog (fprietog) said :
#5

# lsb_release -a; uname -a; apt-cache policy clamtk
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
Linux fpglinux 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
clamtk:
  Instalados: 6.02-1
  Candidato: 6.02-1
  Tabla de versión:
 *** 6.02-1 500
        500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
        500 http://archive.ubuntu.com/ubuntu focal/universe i386 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Manfred Hampl (m-hampl) said :
#6

Ubuntu has a release concept. New versions of software will only be publishes with a new release of Ubuntu (with a few exceptions like the kernel, Firefox, timezone information and severe bugs). The modification that you are referring to will be published only in October 2020 with Ubuntu 20.10.

If the new version works well, but the old one does not, then this is a bug in the old version that should be reported. If you mention that the new version works well, the developers know that there is already a solution, namely backporting the change (or the whole package) to the older Ubuntu release.

What you could try with the 6.02-1 version:
Edit the file (with admin rights)
/usr/share/nautilus-python/extensions/clamtk-gnome.py
and in line 64 change from
 tip=_('Scan %s for threats...') % file.get_name(),
to
 tip=_('Scan for threats...'),

Does it then work?

Revision history for this message
fprietog (fprietog) said :
#7

Yes, it work.

But I just installed the .deb package of the newest version, so it avoid the debsums integrity control.

Thanks for explain the Ubuntu release concept; but I probably didn't made the question correctly... I know that the development version will be published in 20.10 but, since 20.04 is an LTS release I am not sure if it will be published "some day" or it will wait to next LTS release (22.04)... AFAIK only really critical process are backported to an LTS.

Well, I'll probably open a bug.