[Pkg-netatalk-devel] More patches to flag as submitted upstream

[Jonas Smedegaard]

Quoting Daniel Markstedt (2023-05-04 22:07:03)
> > Concretely, it would be great if you could look into cherry-picking the
> > fixes for severe bugs (notably the CVEs) as patches for stable and
> > oldstable.
> 
> You mean cherry picking patches downstream into the Debian repo directly,
> not waiting for a new Netatalk release to be tagged? I can sure do that.
> And, since Ralph gave me full access to the upstream repo I can just as well
> tag new Netatalk patch releases at any time. :)

I mean isolate patches and (not commit them to git as-such, but) put
them below debian/patches and list them in debian/patches/series, test
that all patches apply with "quilt push -a", and add those patch files +
updated series file to git.

For more info, see https://wiki.debian.org/UsingQuilt

Tagging new upstream releases is helpful for other distributions and for
users compiling directly from upstream source, but for Debian stable and
Debian oldstable it is better to use distinct patches to ensure minimal
changes.


> BTW, how do one go about closing out bugs in the Debian BTS?
> #740352 was resolved with https://github.com/Netatalk/netatalk/pull/219

Send an email to 740352-done at bugs.debian.org, with the additional header
"Reply-To: 740352 at bugs.debian.org" and the very first line of content
"Version: XXX" where XXX is the first Debian package version that
contains the fixed code.

For more info, see https://www.debian.org/Bugs/Developer#closing


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-netatalk-devel/attachments/20230504/d23e8e75/attachment.sig>