[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#955277: buster-pu: package mini-buildd/1.0.36



Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu

Hi release team,

mini-buildd currently has

stable 1.0.x branch   bugfix+maintenance only   uploads to unstable (python 2)
master branch         development               uploads to experimental (python 3)

The development (py 3) variant is not yet ready for an upload to
unstable for weeks/month.

In the past, I was quite happy to do "mini-buildd stable" uploads to
unstable, and then do occasional backports from testing. Thus people
could just find/install bugfix releases via Debian (through
backports).

With python 2 getting removed from Debian, I can no longer go the
'bpo-way'. Although it is somewhat documented that there is a 3rd
party PPA available, people usually don't find it (or don't want to
use it).

I.e., I would love to do be able to do bugfix releases via Debian
again, and afaics proposed-updates is now the option I have.

The most annoying issue long fixed after 1.0.36 is this

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951641

Candidates for proposed-updates imho:

1.0.37: Some fixes especially for buster, but did not quite make it; fix for #951641.
1.0.41: What's currently in unstable.
1.0.44: Most recent stable: https://salsa.debian.org/debian/mini-buildd/-/tree/1.0.x

As a side question: Would it still work/be ok to upload (python 2)
1.0.44 to unstable, just for the sake that people are aware of this
new version?

Thx for the advice!

Stephan

-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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


Reply to: