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,
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
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
Hi,
Sorry for the late answer.
I am confused. If the upstream of package pg-el changed, can we
just not follow that new upstream and pull from it ? This is what
I usually do when upstream changes.
You are saying https://github.com/emarsden/pg-el (new) and
https://github.com/cbbrowne/pg.el
Hi,
Le mardi 14 janvier 2025 à 10:56, Sean Whitton
a écrit :
I may misunderstand. Just want to confirm that whether you
still
consider this a blocking issue for uploading.
No, I don't.
Uploaded.
Hi,
Le jeudi 9 janvier 2025 à 02:06, Xiyue Deng a
écrit :
It looks like the cause is that the current latest release of
org-roam
was too old (released in 2022) and doesn't work with emacsql
4.1.0 (and
hence also blocking the migration of emacsql). The latest
snapshot of
org-roam works f
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
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-elpa stopped adding this
dependency to elpa-git-commit
Hi,
Le jeudi 11 juillet 2024 à 08:09, Sean Whitton
a écrit :
If you were going to make complex edits you would always fix it
in the
.org and regenerate the .texi, right?
That would indeed be my own preference, yes.
I just did not think that I could deduce from it that it was
upstream
Hi,
Le mercredi 10 juillet 2024 à 09:06, Sean Whitton
a écrit :
We must be able to rebuild the files from the preferred source
for
modification. If we don't know that we can rebuild the .texi
from the
.org using only what's in Debian, then it would be an RC bug.
I was not aware of thi
Hi Sean,
Le mardi 9 juillet 2024 à 21:56, Sean Whitton
a écrit :
If we don't rebuild the docs, it's hard to be confident that it
*can* be
rebuilt with only tools in main. And if it can't be rebuilt
with only tools
in main, it's not DFSG-free.
I should have been clearer in the message.
reproduce lies therein.
There is an existing patch that sets the e-mail address, but not
the
name. I will update it and forward it upstream.
There you go, the updated patch :
From: Aymeric Agon-Rambosson
Date: Sat, 24 Dec 2022 16:44:54 +0100
Subject: Repair "git unable to detect address&
Hi Lev, Hi Nicholas,
If you are looking for replacements for org-bullets, there is also
org-modern (https://github.com/minad/org-modern), from Daniel
Mendler.
I've been using it happily for quite some time now.
Generally, Daniel Mendler's projects are very well implemented and
maintained.
Hello,
I had noticed in December of 2023 that forge was basically
incapable of pulling anything (from github that time).
I had solved the issue by updating it to a newer upstream
snapshot.
Now, for various reasons, this update has not been pushed to the
archive yet, but it should be soon
Le mardi 26 mars 2024 à 21:21, Sean Whitton
a écrit :
Xiyue reports it worked :)
Thanks a lot !
Hi Sean,
Le mardi 12 mars 2024 à 10:31, Sean Whitton
a écrit :
I'd prefer just to unprotect the branches.
Agreed.
Does anyone have a script which mass-unprotects branches?
I just looked it up, I came up with the following scripts. You
need to have created an API token with the releva
Hi Xiyue,
Le dimanche 10 mars 2024 à 18:08, Xiyue Deng a
écrit :
For getting push rights you'll need to wait for the team owners'
approval.
Yes, this is what I'm doing.
I don't think I have permission to add new members to the
team
No. And I do not need to be added to the team, I am
Hi Xiyue,
Le lundi 4 mars 2024 à 11:38, Xiyue Deng a
écrit :
Will you submit the changes as merge requests for review? I'll
try to
take a look later this week.
I generally don't submit merge requests when I package a new
upstream release, since it requires synchronised pushes to
mult
Hello everyone,
I have packaged new releases of various packages like transient,
magit and with-editor, and I'd like to be able to push them.
However, some branches in those repos are protected, so I cannot
push to them, since I am developer in the Emacsen Salsa group.
May I become a main
ffer-info.
diff --git a/debian/changelog b/debian/changelog
index 9f30538..f650b1f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+dh-elpa (2.0.18) unstable; urgency=medium
+
+ * Team upload.
+ * Get Package-Requires with lm-header-multiline (some upstream
+maintai
Hello team,
I have packaged new upstream releases/snapshots of various
packages, like transient, magit and with-editor.
It turns out I cannot push to the master branch of these specific
repositories, since they are protected, and I cannot push to
protected branches:
remote: GitLab: You a
Hi,
Le samedi 28 octobre 2023 à 20:17, Nicholas D Steeves
a écrit :
Is this because the metadata is missing in Emacs 29.1
(upstream bug, as I noted existed in my understanding of the
problem,
noted on #debian-emacs), or is it a bug in dh-elpa-extras?
This metadata is provided by the li
Le mardi 10 octobre 2023 à 09:08, Sean Whitton
a écrit :
Cool, would you like to file the RM bug?
Sure, but I have a few questions first :
- Should I file the bug against release.debian.org or
ftp.debian.org ? I've seen examples doing either (1036144 and
963750, for instance).
- Such
Hello Sean,
Le lundi 9 octobre 2023 à 18:16, Sean Whitton
a écrit :
Given that you maintain emacsql, would you be interested in
taking over
emacsql-sqlite3 as well?
No. In fact, I think we should not be packaging emacsql-sqlite3
anymore, and we should use the occasion to remove it.
T
Le dimanche 6 août 2023 à 17:38, Sean Whitton
a écrit :
But the patch allows it to be done using an env var. There is
no env
var corresponding to the new Vnative_comp_jit_compilation. And
the env
var is needed so that we can be sure it's turned off early
enough.
Exactly, so we can just
Little correction on what I wrote earlier. Sorry about that, I
should have been more careful.
Le vendredi 4 août 2023 à 18:49, Aymeric Agon-Rambosson
a écrit :
The *only* thing these patches do is :
- If inhibit-automatic-native-compilation (very misleading
variable name
indeed) is t
Le vendredi 4 août 2023 à 11:53, Sean Whitton
a écrit :
My conception of the environment variable is a bit broader than
just
this particular bug: I think that it is a good idea to be able
to switch
off native compilation in the way this environment variable
permits.
Except... The patches
Le jeudi 3 août 2023 à 12:41, David Bremner a
écrit :
First, thanks for your efforts so far. It does make me think you
are
probably right, that we can (try to) drop the corresponding
patches.
I do have one question (which might be annoying to answer): do
the
resulting elpa-* packages ins
Hello team,
At Sean's request, I reproduce here a modified version of my mail
to him regarding the packaging of the latest emacs release, and
more specifically about patches 12 and 13.
The discussion with upstream we've had in February regarding
inhibit-automatic-native-compilation, and the
Le dimanche 16 juillet 2023 à 19:39, "Nikolaus Rath"
a écrit :
Afraid not. With the current elpa-async package, the files are
correctly removed on purge.
That's good.
That leaves me with a different question though - how do I clean
up my system? It seems I have a lot of directories and
Hello,
Le dimanche 16 juillet 2023 à 08:22, Sean Whitton
a écrit :
async 1.9.3 is from buster. You have
/usr/share/emacs/site-lisp/elpa-async-1.9.7 on your system,
right?
The directory you're supposed to have is
/usr/share/emacs/site-lisp/elpa/async-1.9.7
Le dimanche 16 juillet 2023
Le samedi 25 mars 2023 à 12:40, Sean Whitton
a écrit :
Hello,
We can't make either of these metadata changes now the freeze
has begun.
After the freeze, the correct fix is to just update elpa-org to
the
latest release.
It's unfortunate that we didn't update elpa-org in time. Sorry
ab
Hi Nicholas,
Le dimanche 29 janvier 2023 à 21:19, Nicholas D Steeves
a écrit :
Have you already created an account, or are you waiting for
approval?
https://wiki.debian.org/FrontPage?action=newaccount
I am currently waiting for approval. I have cced you on my mail
asking for account
Hi Nicholas,
Le dimanche 29 janvier 2023 à 13:51, Nicholas D Steeves
a écrit :
I agree, the wiki is a good place to centralise information.
Linking to
that article can then be used to avoid needing to reexplaining
things;
it also prevents gating when you link to it from package that
need
Hi Nicholas,
Le dimanche 22 janvier 2023 à 17:31, Nicholas D Steeves
a écrit :
It would be nice to see some of the above text in the patch
header
and/or Debian changelog (it's not relevant for the upstream PR
as far as
I can tell)
I don't think it is relevant to this specific patch eit
Hello David,
Le dimanche 15 janvier 2023 à 07:05, David Bremner
a écrit :
Apologies, I haven't had time to follow this discussion very
well, but I
should note setting EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION=t
in the
environment may help suppress trampoline compilation.
According to
Hello Nicholas,
Le jeudi 12 janvier 2023 à 15:25, Nicholas D Steeves
a écrit :
Wonderful, it looks good to me, so I've merged your work. I'll
CC you
when I ask the upstream community about the remaining three
failures.
I have a patch for the remaining three failures. It was the
trampo
Hello Nicholas,
Le dimanche 8 janvier 2023 à 18:12, Nicholas D Steeves
a écrit :
I've created the branch "temp-agon-reviewed_by_sten" which is
fast-forwardable relative from "temp". This was necessary
because the
following are not doc-related...self tests for core
functionality
should
Hello Nicholas,
Le mercredi 4 janvier 2023 à 13:13, Nicholas D Steeves
a écrit :
ca55bc8: Nice find, and fix, thank you! (I haven't tested it
yet, but
assume you have, that it's good, and that it will pass when I
test it)
I have, and I have checked that the generated HTML documentation
Hello,
Le vendredi 25 novembre 2022 à 10:31, Sean Whitton
a écrit :
It would? The highest version is meant to take precedence.
That's a
feature of package.el.
I run some version of emacs 28.1, which ships xref 1.3.0.
I installed elpa-eglot, which depends on elpa-xref version 1.0.2.
S
Hello,
Le mercredi 23 novembre 2022 à 14:00, Sean Whitton
a écrit :
elpa-transient isn't a transitional package -- we'll keep it in
Debian
even after Emacs 28 is the only Emacs we have. This is because
we might
need a newer version of transient available for another package.
So far our
Hello everyone,
I noticed a few things after packaging eglot, and installing it
myself.
When I installed elpa-eglot on my own machine, it pulled elpa-xref
(1.0.2-2) as a dependency, which is very normal, since elpa-xref
is in the "Depends:" field of the control file, because dh-elpa(1)
pu
42 matches
Mail list logo
