Sean Whitton writes:
> [...]
>>
>> (Wondering for the situation that Emacs version A provides foo 1.0, and
>> when foo 1.0 founds a security issue, and Emacs version A+deb12u1 fixes
>> it by providing foo 1.1, will foo 1.0 automatically upgrade to Emacs
>> A+deb12u1, or it still requires user man
control: reassign -1 src:emacs
control: retitle -1 emacs: generate versioned Provides for all :core packages
Hello,
On Sun 13 Apr 2025 at 08:55pm -07, Xiyue Deng wrote:
> Option 1 also sounds good to me.
Cool. I'm not planning to work on it but I can review patches.
> This may also be useful
Sean Whitton writes:
> Hello,
>
> On Sun 13 Apr 2025 at 06:28pm -07, Xiyue Deng wrote:
>
>> Package: dh-elpa
>> Version: 2.1.9
>> Severity: wishlist
>>
>> A recent bug#1101304 shows some limitation of version handling of
>> dh-elpa for packages that are both built-in and packaged separately.
>> C
Hello,
On Sun 13 Apr 2025 at 06:28pm -07, Xiyue Deng wrote:
> Package: dh-elpa
> Version: 2.1.9
> Severity: wishlist
>
> A recent bug#1101304 shows some limitation of version handling of
> dh-elpa for packages that are both built-in and packaged separately.
> Currently, dh-elpa can mark a package
Package: dh-elpa
Version: 2.1.9
Severity: wishlist
A recent bug#1101304 shows some limitation of version handling of
dh-elpa for packages that are both built-in and packaged separately.
Currently, dh-elpa can mark a package as packaged separately, and then
detect the version from an addon comment
5 matches
Mail list logo
