Processed: Re: Bug#1105004: resurrect README patch with info requested by upstream and by users

2025-05-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #1105004 [php-elisp] resurrect README patch with info requested by upstream and by users Severity set to 'minor' from 'important' -- 1105004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105004 Debian Bug Tracking System Contact ow...@b

Processed: Re: Bug#1104178: elpa-doom-themes: upgrade fails: cannot overwrite non-directory ... with directory

2025-04-27 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 dh-elpa Bug #1104178 [elpa-doom-themes] elpa-doom-themes: upgrade fails: cannot overwrite non-directory ... with directory Bug reassigned from package 'elpa-doom-themes' to 'dh-elpa'. No longer marked as found in versions emacs-doom-themes/2.3.0-3. Ignor

Re: Provenance of java/res/drawable/emacs_wrench.png

2025-04-19 Thread Po Lu
Sean Whitton writes: > Hello, > > Now done on the emacs-30 branch. Thank you.

Re: Provenance of java/res/drawable/emacs_wrench.png

2025-04-19 Thread Sean Whitton
Hello, Now done on the emacs-30 branch. -- Sean Whitton signature.asc Description: PGP signature

Re: Provenance of java/res/drawable/emacs_wrench.png

2025-04-15 Thread Richard Stallman
[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > Though the tango-icon-theme package is released to the Public > > Dom

Processed: Re: Bug#1103033: dh-elpa: Handle version of built-in package better

2025-04-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:emacs Bug #1103033 [dh-elpa] dh-elpa: Handle version of built-in package better Bug reassigned from package 'dh-elpa' to 'src:emacs'. No longer marked as found in versions dh-elpa/2.1.9. Ignoring request to alter fixed versions of bug #1103033 to the

Processed: Re: Bug#1101304: elpa-org-contrib: bug fix did not take effect

2025-04-13 Thread Debian Bug Tracking System
Processing control commands: > notfixed -1 org-contrib/0.6-2 Bug #1101304 {Done: Sean Whitton } [elpa-org-contrib] elpa-org-contrib: should not depend on elpa-org package No longer marked as fixed in versions org-contrib/0.6-2. > fixed -1 org-contrib/0.6-3 Bug #1101304 {Done: Sean Whitton } [elpa

Processed: Re: Bug#1101304: elpa-org-contrib: bug fix did not take effect

2025-04-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo Bug #1101304 {Done: Sean Whitton } [elpa-org-contrib] elpa-org-contrib: should not depend on elpa-org package Added tag(s) moreinfo. -- 1101304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101304 Debian Bug Tracking System Contact ow...@bu

Processed: Re: Bug#1102650: elpa-debian-el: apt-deb822 emacs mode error in some comment lines

2025-04-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +pending Bug #1102650 [elpa-debian-el] elpa-debian-el: apt-deb822 emacs mode error in some comment lines Added tag(s) pending. -- 1102650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102650 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Re: emms_6.00-1_source.changes ACCEPTED into unstable

2025-04-11 Thread Andreas Tille
Hi Lev, Am Fri, Apr 11, 2025 at 11:12:25AM +0500 schrieb Lev Lamberov: > Thank you for your work! But... > > Пт 11 апр 2025 @ 05:34 Debian FTP Masters : > > > emms (6.00-1) unstable; urgency=medium > > . > >* New upstream version > > Closes: #1096579 > > 6.00 is newer than in Debian,

Re: Bug#1102389: ITS: emms

2025-04-11 Thread Arnaud Fontaine
Hi, > PS: I've seen other packages of yours in the list of potential candidates > for salvaging and hope this is fine if we proceed in a similar way > as for emms. Of course, no problem at all. Feel free to proceed as you wish. Thanks! Cheers, -- Arnaud Fontaine

Re: emms_6.00-1_source.changes ACCEPTED into unstable

2025-04-10 Thread Lev Lamberov
Hi, Thank you for your work! But... Пт 11 апр 2025 @ 05:34 Debian FTP Masters : > emms (6.00-1) unstable; urgency=medium > . >* New upstream version > Closes: #1096579 6.00 is newer than in Debian, but it is not the latest upstream one. The uploaded version was release in Oct 2020.Cu

Re: Bug#1102389: ITS: emms

2025-04-10 Thread Andreas Tille
Am Fri, Apr 11, 2025 at 09:56:45AM +0800 schrieb Sean Whitton: > > Sean (or any other team member of the Emacsen team) do you want me to > > put my name into the Uploaders field or do you intend to take over > > fully? The latter is prefered but I'm fine to add my ID if nobody else > > from the te

Re: Bug#1102389: ITS: emms

2025-04-10 Thread Sean Whitton
Hello Andreas, On Thu 10 Apr 2025 at 03:23pm +02, Andreas Tille wrote: > Sean (or any other team member of the Emacsen team) do you want me to > put my name into the Uploaders field or do you intend to take over > fully? The latter is prefered but I'm fine to add my ID if nobody else > from the

Re: Bug#1102389: ITS: emms

2025-04-10 Thread Andreas Tille
Hi Arnaud, Am Thu, Apr 10, 2025 at 02:06:24PM +0200 schrieb Arnaud Fontaine: > No problem with me. On the contrary, I'm very happy if the package can > be taken of by a team as I cannot dedicate much time for Debian at the > moment. Thank you! Thanks to you! Unfortunately its not normal that

Re: Bug#1102389: ITS: emms

2025-04-09 Thread Andreas Tille
Hi Sean, Am Wed, Apr 09, 2025 at 06:31:51PM +0800 schrieb Sean Whitton: > > Perfect. Do you want to create the repository in this team and update > > Vcs fields accordingly? I have no permissions to create repositories in > > emacs team. (You might like to grant such permissions temporarily for

Re: emacs-gtk conflicts with emacs-pgtk

2025-03-20 Thread Max Nikulin
On 19/03/2025 12:30, Sean Whitton wrote: No, I'm afraid, we don't support this, and it's too close to the release to try to work on it now. Thank you for the response, Sean. I can not say I am happy to read it, but I see your point. Let's hope that the gtk build has less limitations with XW

Re: emacs-gtk conflicts with emacs-pgtk

2025-03-18 Thread Sean Whitton
Hello, No, I'm afraid, we don't support this, and it's too close to the release to try to work on it now. -- Sean Whitton signature.asc Description: PGP signature

Processed: Re: Bug#1099195: elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1099195 [elpa-doom-themes] elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties Severity set to 'grave' from 'important' > tags -1 +confirmed +pending Bug #1099195 [elpa-doom-themes] elpa-doom-themes: Rendering is

Processed: Re: Bug#1099195: elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1099195 [elpa-doom-themes] elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties Ignoring request to change severity of Bug 1099195 to the same value. > tags -1 +confirmed +pending Bug #1099195 [elpa-doom-themes] e

Processed: Re: Bug#1100443: elpa-csv-mode: Package description reference non-existant "major mode documentation below"

2025-03-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1100443 [elpa-csv-mode] elpa-csv-mode: Package description reference non-existant "major mode documentation below" Added tag(s) pending. -- 1100443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100443 Debian Bug Tracking System Contact o

Re: reviewing our separately-packaged core libraries

2025-03-11 Thread Xiyue Deng
Hi Aymeric, Aymeric Agon-Rambosson writes: > Hello, > > Le dimanche 2 mars 2025 à 15:20, Sean Whitton > a écrit : > >>> magit build depends on seq (>= 2.24), can be replaced by a >>> build dependency on >>> emacs-common (>= 1:29.2) (lowest emacs-common version providing >>> seq (>= 2.24)) >>

Re: bbdb3 repo

2025-03-09 Thread Sean Whitton
Hello, On Sun 09 Mar 2025 at 05:55pm GMT, Barak A. Pearlmutter wrote: > Upstream is moving the bbdb project repo from nongnu.org to ELPA-gnu > which makes it official gnu.org. Or something like that. No, the only difference is copyright assignment to the FSF. > And so it seems like a good time

Re: bbdb3 repo

2025-03-09 Thread David Bremner
"Barak A. Pearlmutter" writes: > Upstream is moving the bbdb project repo from nongnu.org to ELPA-gnu > which makes it official gnu.org. Or something like that. And so it > seems like a good time to move the debian packaging repo from > https://salsa.debian.org/debian/bbdb3.git to > https://salsa

Processed: Re: Bug#1099829: maildir-utils: 1.12.9 is available upstream

2025-03-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1099829 [maildir-utils] maildir-utils: 1.12.9 is available upstream Added tag(s) pending. -- 1099829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Re: reviewing our separately-packaged core libraries

2025-03-07 Thread Aymeric Agon-Rambosson
Hi, Le mercredi 5 mars 2025 à 22:50, Xiyue Deng a écrit : Thanks for working on this! Can you also list the packages that you worked on and need an upload? Well, this is the same list of "aforementioned" packages I mentioned, so : - magit - flycheck - m-buffer-el - org-drill Best,

Re: reviewing our separately-packaged core libraries

2025-03-04 Thread Aymeric Agon-Rambosson
Hello, Le dimanche 2 mars 2025 à 15:20, Sean Whitton a écrit : magit build depends on seq (>= 2.24), can be replaced by a build dependency on emacs-common (>= 1:29.2) (lowest emacs-common version providing seq (>= 2.24)) flycheck build depends on seq (no version), can be replaced by a bu

Processed: Re: Bug#1099467: dh-elpa-helper: Byte compilation error when upgrading certain packages

2025-03-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo Bug #1099467 [dh-elpa-helper] dh-elpa-helper: Byte compilation error when upgrading certain packages Added tag(s) moreinfo. -- 1099467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099467 Debian Bug Tracking System Contact ow...@bugs.debian

Processed: Re: Bug#1099265: pkg-info-el: FTBFS: dh_elpa_test: error

2025-03-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1099265 [src:pkg-info-el] pkg-info-el: FTBFS: dh_elpa_test: error Added tag(s) pending. -- 1099265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1099467: Acknowledgement (dh-elpa-helper: Byte compilation error when upgrading certain packages)

2025-03-03 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 dh-elpa/2.1.2 Bug #1099467 [dh-elpa-helper] dh-elpa-helper: Byte compilation error when upgrading certain packages Marked as fixed in versions dh-elpa/2.1.2. -- 1099467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099467 Debian Bug Tracking System

Re: reviewing our separately-packaged core libraries

2025-03-01 Thread Sean Whitton
Hello, On Fri 28 Feb 2025 at 09:42pm +01, Aymeric Agon-Rambosson wrote: > Regarding the rdeps of seq, I did a little bit of digging. For all the > rdepends on elpa-seq I could find (using apt-cache on debian stable), we have > the following : > > No explicit dependency on elpa-seq : > > compat-el

Re: reviewing our separately-packaged core libraries

2025-02-28 Thread Aymeric Agon-Rambosson
Hello everyone, (Sorry Sean for the multiple receptions) Le mercredi 26 février 2025 à 14:23, Sean Whitton a écrit : seq === There was a decision from the two Stefans: ;; Note regarding the `seq' package on GNU ELPA: ;; ;; It was decided not to bother upgrading seq beyond 2.24 on GNU E

Re: Comments regarding emacs-peg_1.0.1-1_amd64.changes

2025-02-28 Thread Xiyue Deng
Sean Whitton writes: > Hello, > > This is now in Emacs core in sid, and Xiyue intends to file an RC bug to keep > it out of trixie, so I think we should just REJECT it from NEW? > Ack. I packaged it just for the newer versions of emacs-pg-el, which can now just rely on the Emacs bundled one. A

Re: reviewing our separately-packaged core libraries

2025-02-28 Thread Xiyue Deng
Sean Whitton writes: > Hello, > > On Thu 27 Feb 2025 at 11:58pm -08, Xiyue Deng wrote: > >> Sean Whitton writes: >> >>> [...] >>> >>> eglot, editorconfig, peg, faceup, IHNI. >> >> Forgot to mention: I packaged peg just for emacs-pg-el without knowing >> that it'll ship with Emacs 30.1. I think

Re: reviewing our separately-packaged core libraries

2025-02-28 Thread Sean Whitton
Hello, On Thu 27 Feb 2025 at 11:58pm -08, Xiyue Deng wrote: > Sean Whitton writes: > >> [...] >> >> eglot, editorconfig, peg, faceup, IHNI. > > Forgot to mention: I packaged peg just for emacs-pg-el without knowing > that it'll ship with Emacs 30.1. I think it's fine to keep it out of > Trixie

Re: reviewing our separately-packaged core libraries

2025-02-27 Thread Xiyue Deng
Sean Whitton writes: > [...] > > eglot, editorconfig, peg, faceup, IHNI. Forgot to mention: I packaged peg just for emacs-pg-el without knowing that it'll ship with Emacs 30.1. I think it's fine to keep it out of Trixie in case it leaves the NEW queue before freeze (I'll make sure to file the R

Re: reviewing our separately-packaged core libraries

2025-02-27 Thread Lev Lamberov
Hi, Пт 28 фев 2025 @ 10:54 Sean Whitton : > elpa-bind-key and elpa-use-package go together. > Might people would want newer features? Are they getting new features? The latest release of use-package is dated 2024-08-20 (and it is shipped in GNU Emacs 30.1). As I can see it's GitHub repository i

Re: reviewing our separately-packaged core libraries

2025-02-27 Thread Sean Whitton
Hello, On Thu 27 Feb 2025 at 04:10pm -08, Xiyue Deng wrote: > I have a quick and dirty script (attached) trying to find all packages > that may have a corresponding builtin package (it may have missed a few > though), and the result is the following: > > , > | elpa-xref > | elpa-which-key > |

Re: reviewing our separately-packaged core libraries

2025-02-27 Thread Xiyue Deng
Sean Whitton writes: > Hello, > > As Emacs 30.1 is now heading for trixie, we face once more this issue > described in dh-elpa's documentation: > >> [Distinguish] packages that are maintained outside of the elpa-* >> namespace in Debian, plus Emacs itself. >> >> Also remove built-in packages, exc

Re: emacs-peg_1.0.1-1_amd64.changes is NEW

2025-02-27 Thread Xiyue Deng
Sean Whitton writes: > This needs adding to the list of separately-packaged core libraries, right? > Indeed. I'll send an update once this graduates from the NEW queue. > On Tue 25 Feb 2025 at 04:34am GMT, Debian FTP Masters wrote: > >> binary:elpa-peg is NEW. >> binary:elpa-peg is NEW. >> sou

Re: emacs-peg_1.0.1-1_amd64.changes is NEW

2025-02-27 Thread Sean Whitton
This needs adding to the list of separately-packaged core libraries, right? On Tue 25 Feb 2025 at 04:34am GMT, Debian FTP Masters wrote: > binary:elpa-peg is NEW. > binary:elpa-peg is NEW. > source:emacs-peg is NEW. > > Your package has been put into the NEW queue, which requires manual action >

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-26 Thread Eli Zaretskii
> From: Sean Whitton > Cc: emacs-de...@gnu.org, debian-emacsen@lists.debian.org > Date: Wed, 26 Feb 2025 19:03:25 +0800 > > >> > Also, are you building the original release tarballs, > >> > >> We use the emacs-30.1 git tag, not tarballs, if that's relevant. > > > > It might be relevant, yes. Do

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-26 Thread Sean Whitton
Hello, On Tue 25 Feb 2025 at 05:58pm +02, Eli Zaretskii wrote: >> From: Sean Whitton >> Cc: emacs-de...@gnu.org, debian-emacsen@lists.debian.org >> Date: Tue, 25 Feb 2025 09:17:37 +0800 >> >> > Also, are you building the original release tarballs, >> >> We use the emacs-30.1 git tag, not tarbal

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-25 Thread Xiyue Deng
Eli Zaretskii writes: >> From: Xiyue Deng >> Cc: emacs-de...@gnu.org, debian-emacsen@lists.debian.org >> Date: Mon, 24 Feb 2025 16:37:53 -0800 >> >> > By how much do you need to enlarge to make the builds succeed? >> > >> >> FTR in the log of Debian armhf buildd[1] there is a line says: >> >>

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-25 Thread Eli Zaretskii
> From: Xiyue Deng > Cc: emacs-de...@gnu.org, debian-emacsen@lists.debian.org > Date: Mon, 24 Feb 2025 16:37:53 -0800 > > > By how much do you need to enlarge to make the builds succeed? > > > > FTR in the log of Debian armhf buildd[1] there is a line says: > > , > | emacs:0:Pure Lisp stora

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-25 Thread Eli Zaretskii
> From: Sean Whitton > Cc: emacs-de...@gnu.org, debian-emacsen@lists.debian.org > Date: Tue, 25 Feb 2025 09:17:37 +0800 > > > Also, are you building the original release tarballs, > > We use the emacs-30.1 git tag, not tarballs, if that's relevant. It might be relevant, yes. Does building the

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-25 Thread Peter Oliver
On Mon, 24 Feb 2025, Sean Whitton wrote: The new Emacs 30.1 fails to build on all of Debian's 32-bit release architectures, Intel and Arm. I’m not sure if this helps, but we don’t see this issue on Fedora, so we must be doing something differently. https://koji.fedoraproject.org/koji/taskinf

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-25 Thread Sean Whitton
Hello, On Tue 25 Feb 2025 at 10:57am GMT, Peter Oliver wrote: > On Mon, 24 Feb 2025, Sean Whitton wrote: > >> The new Emacs 30.1 fails to build on all of Debian's 32-bit release >> architectures, Intel and Arm. > > I’m not sure if this helps, but we don’t see this issue on Fedora, so we must > be

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-24 Thread Stefan Kangas
Xiyue Deng writes: > On the other hand, I see there are threads on emacs-devel talking about > removing pure space. Is that referring to this pure lisp storage? Yes, it's that pure lisp storage, and it's gone in Emacs 31.

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-24 Thread Sean Whitton
Hello, On Mon 24 Feb 2025 at 03:47pm +02, Eli Zaretskii wrote: > The actual use of pure space depends on the length of the file names > involved in the build, so if you build in a deeper directory, it could > overflow. We do use deeper directories, but no deeper on 32-bit than 64-bit. > Also, a

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-24 Thread Xiyue Deng
Eli Zaretskii writes: >> From: Sean Whitton >> Cc: debian-emacsen@lists.debian.org >> Date: Mon, 24 Feb 2025 20:02:58 +0800 >> >> >> On Mon 24 Feb 2025 at 07:42pm +08, Sean Whitton wrote: >> >> > The new Emacs 30.1 fails to build on all of Debian's 32-bit release >> > architectures, Intel and

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-24 Thread Eli Zaretskii
> From: Sean Whitton > Cc: debian-emacsen@lists.debian.org > Date: Mon, 24 Feb 2025 20:02:58 +0800 > > > On Mon 24 Feb 2025 at 07:42pm +08, Sean Whitton wrote: > > > The new Emacs 30.1 fails to build on all of Debian's 32-bit release > > architectures, Intel and Arm. > > > > The failures look a

Re: Emacs 30.1 fails to build on 32-bit archs, "Pure Lisp storage overflow"

2025-02-24 Thread Sean Whitton
Hello, On Mon 24 Feb 2025 at 07:42pm +08, Sean Whitton wrote: > The new Emacs 30.1 fails to build on all of Debian's 32-bit release > architectures, Intel and Arm. > > The failures look a little different in each case but in all three the > string "Pure Lisp storage overflow" appears near the end

Re: Provenance of java/res/drawable/emacs_wrench.png

2025-02-24 Thread Po Lu
Sean Whitton writes: > Nice, thanks. > > I think it would be good to document this somewhere, like the excellent > information found in etc/images/README. > > Via the Archive.org Wayback Machine I found this: > > Though the tango-icon-theme package is released to the Public > Domain, we a

Re: Provenance of java/res/drawable/emacs_wrench.png

2025-02-23 Thread Po Lu
I don't know which list to remove, so I'm cross-posting to both lists in my response. You'll excuse me for doing so. Sean Whitton writes: > Hello Po, > > I'm preparing Emacs 30.1 for Debian. > There is a new image file whose copyright and license status I cannot > account for: java/res/drawable

Re: Provenance of java/res/drawable/emacs_wrench.png

2025-02-23 Thread Sean Whitton
Hello, On Mon 24 Feb 2025 at 02:17pm +08, Po Lu wrote: > I don't know which list to remove, so I'm cross-posting to both lists in > my response. You'll excuse me for doing so. Quite fine, and indeed desirable. > It's an XDG Tango icon (preferences-system.svg) superimposed over > emacs.svg and

Processed: Re: Bug#1097812: rtags: ftbfs with GCC-15

2025-02-19 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +moreinfo Bug #1097812 [src:rtags] rtags: ftbfs with GCC-15 Added tag(s) moreinfo. -- 1097812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1097356: maildir-utils: ftbfs with GCC-15

2025-02-19 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +moreinfo Bug #1097356 [src:maildir-utils] maildir-utils: ftbfs with GCC-15 Added tag(s) moreinfo. -- 1097356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1096575: emacs-pdf-tools: ftbfs with GCC-15

2025-02-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +moreinfo Bug #1096575 [src:emacs-pdf-tools] emacs-pdf-tools: ftbfs with GCC-15 Ignoring request to alter tags of bug #1096575 to the same tags previously set -- 1096575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096575 Debian Bug Tracking System C

Processed: Re: Bug#1096575: emacs-pdf-tools: ftbfs with GCC-15

2025-02-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +moreinfo Bug #1096575 [src:emacs-pdf-tools] emacs-pdf-tools: ftbfs with GCC-15 Added tag(s) moreinfo. -- 1096575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1096576: emacs-libvterm: ftbfs with GCC-15

2025-02-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +moreinfo Bug #1096576 [src:emacs-libvterm] emacs-libvterm: ftbfs with GCC-15 Ignoring request to alter tags of bug #1096576 to the same tags previously set -- 1096576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096576 Debian Bug Tracking System Con

Processed: Re: Bug#1096576: emacs-libvterm: ftbfs with GCC-15

2025-02-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +moreinfo Bug #1096576 [src:emacs-libvterm] emacs-libvterm: ftbfs with GCC-15 Added tag(s) moreinfo. -- 1096576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1093398: elpa-emacsql-psql: Depending on the wrong pg.el

2025-02-12 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 emacs-pg-el Bug #1093398 [elpa-emacsql-psql] elpa-emacsql-psql: Depending on the wrong pg.el Bug reassigned from package 'elpa-emacsql-psql' to 'emacs-pg-el'. No longer marked as found in versions emacsql/4.1.0-1. Ignoring request to alter fixed versions

Re: Bug#1093398: elpa-emacsql-psql: Depending on the wrong pg.el

2025-02-12 Thread Xiyue Deng
>>> both repos. The years in the copyright declaration are also >>> consistent. I contend this is the same package, more than 10 years >>> apart (which would explain the different API). >>> >>> So rather that doing all this removing and re-adding (thus having &g

Re: Bug#1093398: elpa-emacsql-psql: Depending on the wrong pg.el

2025-02-11 Thread Xiyue Deng
l explicitly mentions >> Eric Marsden by name, and that name is listed as the author in >> both repos. The years in the copyright declaration are also >> consistent. I contend this is the same package, more than 10 years >> apart (which would explain the different

Re: Bug#1093398: elpa-emacsql-psql: Depending on the wrong pg.el

2025-02-11 Thread Xiyue Deng
os. The years in the copyright declaration are also > consistent. I contend this is the same package, more than 10 years > apart (which would explain the different API). > > So rather that doing all this removing and re-adding (thus having > to clear NEW, and having to temporarily modify

Re: Bug#1093398: elpa-emacsql-psql: Depending on the wrong pg.el

2025-02-11 Thread Aymeric Agon-Rambosson
all this removing and re-adding (thus having to clear NEW, and having to temporarily modify the dependencies of emacsql), we should simply update the pg-el package to follow the real upstream. This would require no change at all in emacsql. If I understand correctly, following the "

Re: Bug#1093398: elpa-emacsql-psql: Depending on the wrong pg.el

2025-02-09 Thread Xiyue Deng
-pg-el (dead upstream[2], no reverse dependency, etc.) * Package the newer pg-el[3], which is the real backend of emacsql-pg.el. * After pg-el graduates from the NEW queue, re-ship emacsql-pg.el. Note: emacsql uses the dgit-maint-debrebase workflow. If you'd like to sponsor please clone th

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc

2025-02-07 Thread Xiyue Deng
Hi Simon, Simon Josefsson writes: > I have uploaded 'emacs-cmake-mode' now, and pushed a debian/* tag. I'm > sorry, that after the upload, I noticed that I managed to use the wrong > orig.tar ball after all, and used the stale one that 'uscan' gave > me... sorry about that. Diffoscope says the

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc

2025-02-07 Thread Simon Josefsson
I have uploaded 'emacs-cmake-mode' now, and pushed a debian/* tag. I'm sorry, that after the upload, I noticed that I managed to use the wrong orig.tar ball after all, and used the stale one that 'uscan' gave me... sorry about that. Diffoscope says the differences are in xz compression only, so s

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc

2025-02-07 Thread Xiyue Deng
Hi Simon, Simon Josefsson writes: > Xiyue Deng writes: > >>> Xiyue, btw, it seems the first package above had another new upstream >>> release, if you would like to package that before I manage to do the >>> upload. >>> >> >> Thanks! I have updated this and uploaded the new version to mentors

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc

2025-02-07 Thread Simon Josefsson
Xiyue Deng writes: >> Xiyue, btw, it seems the first package above had another new upstream >> release, if you would like to package that before I manage to do the >> upload. >> > > Thanks! I have updated this and uploaded the new version to mentors > which should show up soon. Note that on Sal

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc

2025-02-07 Thread Simon Josefsson
Sean Whitton writes: > Hello, > > On Wed 05 Feb 2025 at 09:57am +01, Simon Josefsson wrote: > >> I hope to find time to take a look at these two packages again, when/if >> I'm added to the Salsa Emacsen group so I can make a team upload of >> them. > > I've added you. We use a variety of git wor

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc

2025-02-07 Thread Sean Whitton
Hello, On Wed 05 Feb 2025 at 09:57am +01, Simon Josefsson wrote: > I hope to find time to take a look at these two packages again, when/if > I'm added to the Salsa Emacsen group so I can make a team upload of > them. I've added you. We use a variety of git workflows; please follow whatever a pa

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc

2025-02-05 Thread Simon Josefsson
Xiyue Deng writes: > Also, there is a new incoming package emacs-llama (RFS[1]) that is a new > dependency of magit which also needs a sponsor if you are interested. > >> Xiyue, btw, it seems the first package above had another new upstream >> release, if you would like to package that before I m

Re: Request to join team to upload emacs-cmake-mode + emacs-jsonrpc (was: Re: Mentors. Confirmed packages needing DD review and possible sponsorship)

2025-02-05 Thread Xiyue Deng
Hi Simon, Thanks for your interest of sponsoring! Please see my replies inline below. Simon Josefsson writes: > Phil Wyett writes: > >> #1089572 RFS: emacs-cmake-mode/3.31.4+ds-1 -- Emacs major mode for editing >> CMake sources >> RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089572

Request to join team to upload emacs-cmake-mode + emacs-jsonrpc (was: Re: Mentors. Confirmed packages needing DD review and possible sponsorship)

2025-02-04 Thread Simon Josefsson
Phil Wyett writes: > #1089572 RFS: emacs-cmake-mode/3.31.4+ds-1 -- Emacs major mode for editing > CMake sources > RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089572 > dget -x > https://mentors.debian.net/debian/pool/main/e/emacs-cmake-mode/emacs-cmake-mode_3.31.4+ds-1.dsc ... > #10944

Processed: Re: Bug#1092730: superfluous, see Bug#1092731 instead

2025-01-10 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 Duplicate of bug#1092731 Bug #1092730 {Done: Ben Finney } [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode” Changed Bug title to 'Duplicate of bug#1092731' from 'elpa-emacs-dashboard

Processed: Re: Bug#1092731: elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode”

2025-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unmerge 1092731 Bug #1092731 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode” Bug #1092730 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s

Processed: Re: Bug#1092731: elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode”

2025-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unmerge 1092731 Bug #1092731 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode” Bug #1092730 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s

Processed: Re: Bug#1092731: elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode”

2025-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1092731 1092730 Bug #1092731 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode” Bug #1092730 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package:

Processed (with 1 error): Re: Bug#1092731: elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode”

2025-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1092731 1092730 Bug #1092731 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode” Unable to merge bugs because: forwarded of #1092730 is '' not 'https://github.com/emacs-

Processed: Re: Bug#1092731: elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode”

2025-01-10 Thread Debian Bug Tracking System
Processing control commands: > merge -1 1092731 Bug #1092731 [elpa-emacs-dashboard] elpa-emacs-dashboard: Invokes obsolete package: “Symbol’s function definition is void: linum-mode” Merged 1092731 > forwarded -1 https://github.com/emacs-dashboard/emacs-dashboard/issues/548 Bug #1092731 [elpa-ema

Processed: Re: Bug#1090886: git-commit: missing (require 'magit-process)

2025-01-07 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/magit/magit/pull/5280 Bug #1090886 [elpa-magit] git-commit: missing (require 'magit-process) Set Bug forwarded-to-address to 'https://github.com/magit/magit/pull/5280'. -- 1090886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10

Re: Bug#854797: pinentry-emacs in Debian

2024-12-26 Thread Andreas Metzler
On 2017-09-09 Lev Lamberov wrote: > Сб 09 сен 2017 @ 12:56 David Bremner : >> Lev Lamberov writes: >>> I'd like to rise again the reporter concern [0] about availability of >>> pinentry-emacs in Debian, because I'd be very-very happy to see it >>> there. The support of pinentry-emacs is required

Processed: Re: Bug#1091462: dh-make-elpa: Use "upstreamvcs" as suggested upstream remote name

2024-12-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1091462 [dh-make-elpa] dh-make-elpa: Use "upstreamvcs" as suggested upstream remote name Added tag(s) patch. -- 1091462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091462 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Processed: Re: Bug#1091462: dh-make-elpa: Use "upstreamvcs" as suggested upstream remote name

2024-12-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1091462 [dh-make-elpa] dh-make-elpa: Use "upstreamvcs" as suggested upstream remote name Ignoring request to alter tags of bug #1091462 to the same tags previously set -- 1091462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091462 Debian

Processed: Re: Bug#1091359: Consider updating mastodon.el

2024-12-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #1091359 [elpa-mastodon] Consider updating mastodon.el Severity set to 'wishlist' from 'normal' -- 1091359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Re: Questions and remarks regarding elpa-magit bug 1086758

2024-11-07 Thread Aymeric Agon-Rambosson
Hi everyone, elpa-git-commit was turned into a transitional package as discussed. I will upload the package in the following days unless there are objections. Best, Aymeric Le mercredi 6 novembre 2024 à 11:33, Xiyue Deng a écrit : Hi Barak, Jeremy, Jeremy Sowden writes: On 2024-1

Re: Questions and remarks regarding elpa-magit bug 1086758

2024-11-06 Thread Xiyue Deng
Hi Barak, Jeremy, Jeremy Sowden writes: > On 2024-11-05, at 20:40:08 +, Barak A. Pearlmutter wrote: >> To my mind, the natural solution is to put git-commit.el in elpa-magit >> (as upstream wants) but keep the elpa-git-commit package around, >> empty, and with a Depends: elpa-magit (>= xxx)

Re: Questions and remarks regarding elpa-magit bug 1086758

2024-11-05 Thread Jeremy Sowden
On 2024-11-05, at 20:40:08 +, Barak A. Pearlmutter wrote: > To my mind, the natural solution is to put git-commit.el in elpa-magit > (as upstream wants) but keep the elpa-git-commit package around, > empty, and with a Depends: elpa-magit (>= xxx) or even Depends: > elpa-magit (== xxx) to ensure

Re: Questions and remarks regarding elpa-magit bug 1086758

2024-11-05 Thread Barak A. Pearlmutter
To my mind, the natural solution is to put git-commit.el in elpa-magit (as upstream wants) but keep the elpa-git-commit package around, empty, and with a Depends: elpa-magit (>= xxx) or even Depends: elpa-magit (== xxx) to ensure that git-commit.el is pulled in. And elpa-magit has a Breaks: elpa-gi

Re: Questions and remarks regarding elpa-magit bug 1086758

2024-11-05 Thread Xiyue Deng
Xiyue Deng writes: > Hi Aymeric, > > Aymeric Agon-Rambosson writes: > >> Hello team, >> >> As you may have noticed, Mr. Kimura has opened bug report 1086758, >> in which he claims that elpa-magit should still depend on >> elpa-git-commit (which it does not anymore, since 4.1.2-1). >> >> He is

Re: Questions and remarks regarding elpa-magit bug 1086758

2024-11-05 Thread Xiyue Deng
Hi Aymeric, Aymeric Agon-Rambosson writes: > Hello team, > > As you may have noticed, Mr. Kimura has opened bug report 1086758, > in which he claims that elpa-magit should still depend on > elpa-git-commit (which it does not anymore, since 4.1.2-1). > > He is right, of course. The reason dh-el

Processed: Re: Bug#1086758: elpa-magit: 4.1.2-1 doesn't depends on elpa-git-commit but still requires it

2024-11-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1086758 [elpa-magit] elpa-magit: 4.1.2-1 doesn't depends on elpa-git-commit but still requires it Severity set to 'serious' from 'normal' -- 1086758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086758 Debian Bug Tracking System Cont

Re: magit_4.1.2-1_source.changes ACCEPTED into unstable

2024-11-03 Thread Xiyue Deng
Xiyue Deng writes: > "Matteo F. Vescovi" writes: > >> Hi again! >> >> On 2024-11-03 at 08:03 (GMT), Barak A. Pearlmutter wrote: >> >> [...] >> >>> I dput 4.1.2-1 because there's no practical >>> difference between the two. >> >> This isn't actually true: >> >> $ git diff v4.1.1 v4.1.2 lisp/magit

Re: magit_4.1.2-1_source.changes ACCEPTED into unstable

2024-11-03 Thread Xiyue Deng
"Matteo F. Vescovi" writes: > Hi again! > > On 2024-11-03 at 08:03 (GMT), Barak A. Pearlmutter wrote: > > [...] > >> I dput 4.1.2-1 because there's no practical >> difference between the two. > > This isn't actually true: > > $ git diff v4.1.1 v4.1.2 lisp/magit.el > diff --git a/lisp/magit.el b/l

Re: magit_4.1.2-1_source.changes ACCEPTED into unstable

2024-11-03 Thread Barak A. Pearlmutter
Thanks, Matteo! Yes, magit 4.1.1 works okay, as far as I can tell. The issue is when it runs its test suite at build time. Under some circumstances, it tries to pop up a subservient emacs process to edit the commit message. I was starting to track that down... And re 4.1.1 → 4.1.2 dependency

Re: magit_4.1.2-1_source.changes ACCEPTED into unstable

2024-11-03 Thread Matteo F. Vescovi
Hi again! On 2024-11-03 at 08:03 (GMT), Barak A. Pearlmutter wrote: [...] > I dput 4.1.2-1 because there's no practical > difference between the two. This isn't actually true: $ git diff v4.1.1 v4.1.2 lisp/magit.el diff --git a/lisp/magit.el b/lisp/magit.el index 845c5e5f..b4502365 100644 ---

Re: magit_4.1.2-1_source.changes ACCEPTED into unstable

2024-11-03 Thread Matteo F. Vescovi
I uploaded 4.1.1 as ut was working fine (tested with piuparts). 4.1.2 is now forcing 0.7.8 for transient. Thus, I've uploaded 0.7.8 and forge 0.4.4 to fix the issue. Cheers. mfv Il dom 3 nov 2024, 09:04 Barak A. Pearlmutter ha scritto: > True: transient needs to be uploaded too. > > I tested l

  1   2   3   4   5   6   7   8   9   10   >