Re: bring a newer version of a package into stable (nsis-3.09-1 into Debian "bookworm")

[Norwid Behrnd]

Hello,

I recommend the following two-fold approach.

- For one, if `nsis` refers to this entry in the package tracker

https://tracker.debian.org/pkg/nsis

prepare a new version of the package to enter branch testing (i.e. Debian
13/trixie) with as few as possible warnings e.g., by lintian and no longer an
error note "fails to build".  Based on the news this page lists, I assume you
equally are a sponsored maintainer, so you can upload the package *for
branch testing* to debian.mentors.org for the testing, public review.  With
successful sponsorship, and passing the checks, the update (to Debian
13/trixie) can arrive there within a week.

- Simultaneously, this version (then free of errors and warnings) then can be
used for a separate upload to debian.mentors.org aiming to constitute *a
backport* to branch stable (i.e. Debian 12/bookworm).  See

https://wiki.debian.org/Backports
https://backports.debian.org/

Of course, /debian/changelog requires a new entry and there should be a new
(additional) branch in the salsa GitLab repository exclusively dedicated to
the work on backports.  However, your upload to debian.mentors.org of your
revised package to Debian 13/trixe (testing) and Debian 12/bookworm (stable)
can be almost simultaneously -- by proper labeling by you, Debian Developers
can defer the upload to Debian stable until the upload to Debian testing is
successful.

A couple of weeks ago, I enjoyed this process of providing branch stable a
newer version of markdownlint with the sponsorship by Tobias Frost, see

https://tracker.debian.org/pkg/ruby-mdl

Regards,

Norwid

Re: bring a newer version of a package into stable (nsis-3.09-1 into Debian "bookworm")

[Andrey Rakhmatullin]

On Fri, Dec 22, 2023 at 01:55:59PM +0100, Thomas Gaugler wrote:
> Hi,
> 
> I thought a package in Debian "bookworm" could be updated via a "bookworm
> proposed updates request" .
> 
> It looks like I did not fully understand the process. Therefore I kindly ask
> for assistance in updating the nsis-3.08-3 package in Debian "bookworm" to
> nsis-3.09-1.
What kind of assistance are you asking for?

Re: bring a newer version of a package into stable (nsis-3.09-1 into Debian "bookworm")

[Sune Vuorela]

On 2023-12-22, Thomas Gaugler  wrote:
> Hi,
>
> I thought a package in Debian "bookworm" could be updated via a 
> "bookworm proposed updates request" .
>
> It looks like I did not fully understand the process. Therefore I kindly 
> ask for assistance in updating the nsis-3.08-3 package in Debian 
> "bookworm" to nsis-3.09-1.

Unless you are special, only targetted fixes are normally allowed in
stable.

You should be able to do a full diff between the nsis 3.08-3 and 3.09-1
and explain all of the changes and why it is a targetted minimal fix.
(Except maybe version number changes)

If there is unrelated changes, consider looking at a targetted fix and
try to get a 3.08-4 in testing instead.

Once you have a tested nsis where you have read and understand and can
explain the full diff of what you want to do, please attach the full
diff to said bug report and remove the moreinfo tag.

>From your description, the two fixes sounds worth fixing in stable.

/Sune

bring a newer version of a package into stable (nsis-3.09-1 into Debian "bookworm")

[Thomas Gaugler]

Hi,

I thought a package in Debian "bookworm" could be updated via a 
"bookworm proposed updates request" .


It looks like I did not fully understand the process. Therefore I kindly 
ask for assistance in updating the nsis-3.08-3 package in Debian 
"bookworm" to nsis-3.09-1.


The nsis-3.09-1 package is available in Debian "trixie" / testing and 
the maintenance of this package happens on 
.


Thanks in advance,
Thomas