Package: elpa-magit
Version: 4.3.1-1
Severity: important
The latest magit upload has dropped elpa-seq from Build-Depends, and
therefore elpa-seq got autoremoved from my system. While this seems
desirable, I foresee a problem with partial upgrades from bookworm,
because elpa-magit needs the seq-ke
On 2024-11-02 23:35 +, Debian FTP Masters wrote:
> Accepted:
>
> Format: 1.8
> Date: Sat, 02 Nov 2024 23:00:17 +
> Source: magit
> Architecture: source
> Version: 4.1.2-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Emacsen team
> Changed-By: Barak A. Pearlmutter
> Cha
Package: elpa-debian-el
Version: 37.13
Severity: important
I wanted to report a bug against the dpkg-dev package, but that resulted
in a Lisp error before even running reportbug. Below is a backtrace
after loading the debian-bug.el source file.
Downgrading elpa-debian-el to version 37.12 fixes t
Control: tags -1 + patch
On 2024-06-26 11:54 +0200, Sven Joachim wrote:
> Package: elpa-dpkg-dev-el
> Version: 37.12
> Severity: normal
>
> I have started to use Emacs from the recently created emacs-30 branch,
> and noticed that in debian-changelog-mode buffers font-lock-mode
Package: elpa-dpkg-dev-el
Version: 37.12
Severity: normal
I have started to use Emacs from the recently created emacs-30 branch,
and noticed that in debian-changelog-mode buffers font-lock-mode is nil
(M-x font-lock mode fixes that for the current buffer). In the Emacs 30
NEWS file I found the fo
Package: elpa-magit
Version: 3.3.0+git20231219.1.c7ab6931-1
Severity: serious
After loading magit Emacs displayed the following message in the
*Warnings* buffer:
,
| Emergency (magit): Magit requires ‘transient’ >= 0.5.0,
| but due to bad defaults, Emacs’ package manager, refuses to
| upgrade
On 2023-02-05 20:07 -0400, David Bremner wrote:
> Sven Joachim writes:
>
>>
>> I have attached a patch which drops the extra second slash.
>>
>> Cheers,
>>Sven
>
> Thanks Sven, I'll most likely wait until after the freeze to apply that.
On 2023-03-11 07:49 -0800, David Bremner wrote:
> Sven Joachim writes:
>
> Control: severity -1 wishlist
>
>> Package: elpa-debian-el
>> Version: 37.10
>> Severity: normal
>>
>> Visiting zstd compressed .deb files in deb-view mode-fails with a tar
&g
Package: elpa-debian-el
Version: 37.10
Severity: normal
Visiting zstd compressed .deb files in deb-view mode-fails with a tar
error, here is a backtrace after toggling debug-on-error.
,
| Debugger entered--Lisp error: (error "Malformed Tar header")
| signal(error ("Malformed Tar header"))
|
attached a patch which drops the extra second slash.
Cheers,
Sven
From ae5e65b77517dd2ce8bd2d74099bb9c36529f05b Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sun, 5 Feb 2023 20:08:27 +0100
Subject: [PATCH] helper scripts: Avoid double slashes in symlinks
Closes: #1030560
---
helper/i
On 2023-01-28 07:24 -0400, David Bremner wrote:
> Dan Jacobson writes:
>
>> Package: dh-elpa-helper
>> Version: 2.0.16
>> Severity: minor
>>
>> I saw this:
>> Warning (comp): Cannot look-up eln file as no source file was found for
>> /usr/share/emacs/site-lisp/elpa/csv-mode-1.20/csv-mode.elc
>
>
On 2018-10-12 19:20 -0700, Dima Kogan wrote:
> Package: emacs-goodies-el
> Version: 41.0
> Severity: normal
>
> Hi. I just upgraded my emacs bits, and the postinst now complains. I dug in a
> bit, and the complainy invocation ( and following errors) look like this:
>
> root@fatty:/var/lib/dpkg/i
Package: emacs-goodies-el
Version: 41.0
There are several dependencies/recommendations in emacs-goodies-el which
look questionable to me.
- elpa-debian-el, elpa-dpkg-dev-el, elpa-devscripts:
Those packages are the successors of debian-el, dpkg-dev-el and
devscripts-el which used to be built f
Control: reassign -1 apt
Control: merge 670920 -1
On 2018-08-09 10:22 -0300, Alexandre Lymberopoulos wrote:
> Package: emacs-goodies-el
> Version: 40.0
> Severity: normal
>
> Dear Maintainer,
>
> When I tried to update this package on aptitude, it was left
> unconfigured and now, when I try to re
Package: elpa-debian-el
Version: 37.5
Severity: normal
After upgrading from debian-el from 36.4, I found that a freshly started
Emacs would open Debian packages in archive-mode rather than
deb-view-mode until I manually loaded the debian-el library.
In debian-el 36.4 and earlier, /etc/emacs/site-
Package: wnpp
Severity: wishlist
* Package name: meson-mode
Version : 0.1
Upstream Author : Michal Sojka
* URL or Web page : https://github.com/wentasah/meson-mode
* License : GPL3+
Description : major mode for the Meson build system files
Everybody seems to be jumpi
On 2016-11-01 17:36 -0500, Rob Browning wrote:
> Sven Joachim writes:
>
>> I have. ;-)
>>
>> ,
>> | $ apt-cache show emacs25-nox | grep ^Provides:
>> | Provides: editor, emacs25, emacsen, info-browser, mail-reader, news-reader
>> `
>
> Heh,
On 2016-11-01 08:40 -0700, Sean Whitton wrote:
> On Mon, Oct 31, 2016 at 11:12:45PM -0500, Rob Browning wrote:
>> As far as I understand it, nothing can provide emacs25 except for the
>> emacs25 binary package (because emacs25 already exists as a binary
>> package)[1].
>
> I don't think this is tr
On 2016-10-31 17:34 -0300, David Bremner wrote:
> Sven Joachim writes:
>
>>>>Sven
>>>
>>> I think it will have to be
>>>
>>> Depends: emacs25-nox | emacs25ish | ...
>>
>> In that case there is no need for the em
On 2016-10-31 14:55 -0300, David Bremner wrote:
> Sven Joachim writes:
>
>> On 2016-10-30 15:32 -0500, Rob Browning wrote:
>>
>>
>>> So I'm contemplating adding a new provides to all of the Emacs binary
>>> packages (e.g. to emacsXY, emacsXY-nox,
On 2016-10-30 15:32 -0500, Rob Browning wrote:
> Right now a tool like dh-elpa, which needs a "viable" flavor of emacsXY
> at build time has to do something like this:
>
> Depends: ... emacs24-nox | emacs24 | emacs24-lucid ...
>
> and if emacs24 ends up staying in stretch, that becomes:
>
> De
Control: reassign -1 css-mode
Control: tags -1 + jessie sid
Control: retitle -1 css-mode: apropos-macrop removed in Emacs 24.4
On 2014-10-26 13:03 +0100, Axel Beckert wrote:
> Package: haml-elisp
> Version: 1:3.1.0-3
> Severity: serious
>
> Dear Maintainer,
>
> haml-elisp fails to install (and in
On 2014-08-20 15:31 +0200, Axel Beckert wrote:
> Hi,
>
> for a bug report about a segfault I wanted to attach a huge backtrace
> (over 3 MB). I've compressed it with xz to a 33kb file. I wrote the
> bug report with M-x debian-bug as usual and then attached the
> compressed file with M-x mail-attac
On 2011-10-20 01:20 +0200, jida...@jidanni.org wrote:
> Every time on Debian I use aptitude to
> The following packages will be upgraded:
> emacs-snapshot emacs-snapshot-bin-common (for emacs-snapshot)
> emacs-snapshot-common (for emacs-snapshot, emacs-snapshot-el)
> emacs-snapshot-el
> I h
On 2011-02-26 00:33 +0100, jida...@jidanni.org wrote:
> Why can't the dates on /usr/share/emacs/24.0.50/etc/* etc. be preserved?
> I can't believe all those files were really modified just yesterday.
It seems Julien creates the tarballs with "git archive … ", and
in this case all files have the c
On 2010-09-16 22:04 +0200, John Sullivan wrote:
> John Sullivan writes:
>
>> Any suggestions/policy for how to handle this? I understand that I would
>> need to test each emacsen provider individually to make sure that it
>> builds successfully...
>>
>
> The answer I'm going with is what I got fr
On 2010-04-01 20:32 +0200, Jordan Metzmeier wrote:
> I see that emacs22 is still in squeeze and sid. Are these also planned
> for removal?
Yes.
Sven
--
To UNSUBSCRIBE, email to debian-emacsen-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
On 2010-02-23 18:09 +0100, Roland Stigge wrote:
> On 02/23/2010 05:07 PM, Sven Joachim wrote:
>> emacs22 is not supposed to be released with squeeze, so hyperlatex must
>> not (build-)depend on it.
>
> I wanted to get back to the debian-emacsen list anyway
> today. hyper
[ Not sure if you read the list, please forgive the duplicate message in
that case.]
On 2010-02-22 21:05 +0100, Roland Stigge wrote:
> with emacs22, everything is fine, but emacs23 breaks hyperlatex leading
> it to FTBFS like this:
> [...]
> Making directory html
> Title of work is "Hyperlatex
On 2009-09-19 17:56 +0200, Géraud Meyer wrote:
> Some bugs reported for emacs22 are fixed in emacs23. Should such
> information be sent to the BTS , and if so how can one express that
> the successor of emacs22 fixed some bug?
Use the fixed-upstream tag; given that there will be no further upstre
On 2009-09-07 03:22 +0200, Jim McCloskey wrote:
> * Sven Joachim (svenj...@gmx.de) wrote:
>
> |> >>> Has anybody else experienced the FTBFS related to the removal of
> |> >>> dir.old?
>
> I experienced it on an attempted install of 23.1+1-2 on
On 2009-08-03 15:13 +0200, Sven Joachim wrote:
> On 2009-08-02 10:16 +0200, Sven Joachim wrote:
>
>> On 2009-08-02 09:58 +0200, Florian Weimer wrote:
>>
>>> Has anybody else experienced the FTBFS related to the removal of
>>> dir.old?
>>
>> No
On 2009-08-15 17:57 +0200, Simon Josefsson wrote:
> I was thinking more in terms of compilation options or different library
> dependencies. I don't need any elisp code beyond what's in 23.1, or so
> I believe, so I'm wondering if there is anything in it for me to keep
> using emacs-snapshot inst
On 2009-08-04 18:50 +0200, Peter S Galbraith wrote:
> I wonder about the following:
>
> : There are disparities between your recently accepted upload and the
> : override file for the following file(s):
> :
> : debian-el_30.3-1_all.deb: package says section is utils, override says lisp.
> : devsc
On 2009-08-02 10:16 +0200, Sven Joachim wrote:
> On 2009-08-02 09:58 +0200, Florian Weimer wrote:
>
>> * Rob Browning:
>>
>>> I've uploaded the first emacs23 packages (23.1+1-1) to unstable. Please
>>> file bugs as appropriate.
>>
>> Has anyb
On 2009-08-02 10:38 +0200, Florian Weimer wrote:
> * Sven Joachim:
>>
>> I haven't tried emacs23 yet, but on recent emacs-snapshot packages I did
>> not experience much of a slowdown compared to emacs22. There is often a
>> delay when Emacs has to display chara
On 2009-08-02 09:58 +0200, Florian Weimer wrote:
> * Rob Browning:
>
>> I've uploaded the first emacs23 packages (23.1+1-1) to unstable. Please
>> file bugs as appropriate.
>
> Has anybody else experienced the FTBFS related to the removal of
> dir.old?
Not me (building in pbuilder).
> It also s
On 2009-08-01 22:52 +0200, Rob Browning wrote:
> I've uploaded the first emacs23 packages (23.1+1-1) to unstable.
Thanks! Unfortunately, the current status of NEW means that they will
probably not be available for the public any time soon. :-(
> Please file bugs as appropriate.
Do you have a
On 2009-07-26 18:42 +0200, Rob Browning wrote:
> Hilko Bengen writes:
>
>> Emacs 23.1 is likely to be released RSNish[1], so I am wondering whether
>> there are any ongoing efforts, apart from several inofficial
>> emacs-snapshot packages, to get any of the 23.0.9x pre-releases
>> packaged.
>
> I
On 2009-01-05 15:39 +0100, Sebastien Delafond wrote:
> On Mon, Jan 05, 2009 at 11:31:57AM +0100, Sven Joachim wrote:
>> > When that package is installed, however, it provides
>> > /usr/share/info/emacs-22/org.gz. info(1) deals with it properly,
>> > but emacs'
On 2009-01-03 17:33 +0100, Sebastien Delafond wrote:
> I'm trying to solve bug #490053: in a nutshell, my org-mode packages
> ships /usr/share/info/org.gz, which both info(1) and emacs' "C-h
> i" see fine when emacs22-common-non-dfsg.
>
> When that package is installed, however, it provides
> /usr
On 2008-10-31 17:33 +0100, Agustin Martin wrote:
> On Fri, Oct 03, 2008 at 04:01:07PM +0200, Agustin Martin wrote:
> There is one thing about which I would like to get feedback, old flavors. I
> have added basic support for excluding specific flavors, although only put
> 'emacs' there. However cur
On 2008-09-05 11:27 +0200, Slim Joe wrote:
> Can a Debian emacs developer look into the emacspeak package? I
> believe the package contains an unnecessary dependency on an older
> version of emacs:
>
> Depends: tclx8.4, tcl8.4, perl-5.6 | perl, emacsen-common, make, emacs
> | emacs21, w3-el-e21
>
On 2008-08-14 11:14 +0200, Hilko Bengen wrote:
> Even if the feature set for Emacs 23 hasn't been set in stone (and I'd
> expect it to stay that way for a while), I think that a set of
> -snapshot packages that track development towards Emacs 23 would be
> useful for developers and Debian maintain
On 2008-07-26 23:00 +0200, Hilko Bengen wrote:
> An emacs22 upgrade that was recently installed broke when it tried to
> byte-compile a part of sepia (for which I maintain the Debian
> package). This is the output I got when I tried to reinstall the
> emacs22-gtk package:
>
> $ sudo apt-get --rein
Peter Smerdon <[EMAIL PROTECTED]> writes:
> Hi, I hope this is the correct mailing list,
Probably [EMAIL PROTECTED] would be a better choice, that list is
read by more Emacs Developers.
> I am trying to get emacs22-gtk to display a pleasing, anti-aliased font
> and have been following the direc
Peter S Galbraith <[EMAIL PROTECTED]> writes:
> This isn't strictly an Emacs isuue, but it certainly affects us...
>
> As I understand it, the GPL v3 is more strict then the GPL v2 and thus
> is incompatible. Is that correct?
It seems so, see
http://www.gnu.org/licenses/gpl-faq.html#v2v3Compatib
Peter Daum writes:
> Fortunately, I don't usually need UTF-8 (Even in multibyte mode and with
> a suitable font, I never managed persuading emacs to correctly display
> an utf-8-encoded file)
Unless you live on an island, sooner or later you will retrieve UTF-8
encoded files, as this is standard i
Peter Daum writes:
> Now after migrating my systems from Suse to Debian (Etch), my key
> bindings don't work anymore and I can't figure out, what changed.
>
> Here a minimal code snippet to illustrate the problem:
>
> (defun latin1-to-emacs-char (char-code)
> (make-char 'latin-iso8859-1 (- char
Tatsuya Kinoshita writes:
> The points are testing the emacs22 flavor for Elisp Debian packages
> and testing the emacs22 Debian package itself. I guess some Elisp
> Debian packages fail with emacs22 (e.g. byte-compilation fails if
> emacsen-install uses whitelist without emacs22). emacs22 Debia
Romain Francoise writes:
> The recent discussion on debian-emacsen about Emacs 22 has prompted
> me to rethink my involvement in Emacs for Debian, and I realized
> that I have ignored the GFDL problem for much too long. There is
> now very little hope for a reversal of this situation, and for
> b
Am 28.10.2006 um 12:26 schrieb Jérôme Marant:
> Le samedi 28 octobre 2006 10:35, Sven Joachim a écrit :
>
>> I'm afraid even the Debian maintainers do not understand it, because
>> load-path is _really_ broken in Debian Emacsen. The add-on packages'
>> director
I'd like to draw attention to some serious load-path issues, as I
believe that David makes correct observations.
David Kastrup wrote:
> [...] It is not sensibly possible to
> install, say, your own up-to-date version of AUCTeX from a source ball
> and install it into a local tree, in particular i
Jérôme Marant wrote:
> Why was the gnus manual removed from the gnus package?
>
> According to its license, it does not have any invariant section:
>
> -=-=-=-=-=-=-
>
> Permission is granted to copy, distribute and/or modify this document
> under the terms of the GNU Free Documentation License,
On Fri, Mar 17 2006, Davide G. M. Salvetti wrote:
MS == Manoj Srivastava [2006-3-16]
MS> Depends is too strong a relationship; if I have several machines in
MS> my LAN, I may only keep extensive documentation on one of them, and
MS> use NFS to share share-able directories. I would be annoyed i
Hubert Chan wrote:
The inconsistency smells a lot like an oversight. Have you checked with
upstream to see if that was what was actually intended, or if it was a
copy/paste bug?
I reported this to bug-make@gnu.org, let's see what they say.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
Ben Pfaff wrote:
I just downloaded make 3.80 from ftp.gnu.org, and you appear to
be wrong about that. Here is an excerpt from make.texi:
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
any la
On Wed, Mar 15, Miles Bader wrote:
In practice I guess it's just going to mean that most people end up
putting non-free in their sources.list, weakening the effect of having a
separation between "free" and "non-free" in the first place, and more
users end up confused because lack of hard dependen
Hubert Chan wrote:
Personally, I'm not too concerned about the doc packages not getting
installed. There are a lot of packages in Debian that are split into
executable and documentation that don't have hard dependencies to
automatically install the documentation.
Note that until now, the info
Jérôme Marant wrote:
Let's take the glibc example:
[...]
As you can see, even libc6 development files "suggest" glibc-doc.
So, suggesting is perfectly OK.
This comparison limps. Many people install development packages only
to compile downloaded sources, not to develop themselves. But nobod
Jérôme Marant wrote:
Quoting "Davide G. M. Salvetti" <[EMAIL PROTECTED]>:
I do not share your statement about newbies not using Emacs. However,
based on your above considerations, what exactly would be the problem
for newbies and/or experienced users with emacs21 and emacs-snapshot
being moved
Jérôme Marant wrote:
Yeah, after all, the social contract merely states:
We will never make the system require the use
of a non-free component.
Now I realize what that means: "The system" does not require the
non-free documentation, although one could argue that its users and
develope
orry you don't like this. I'm not really fond of it either, but I
have the choice of either do what the Project decided or resign from the
Project. I've chosen the former.
Thank you very much for this decision.
Regards,
Sven Joachim
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
[ CC'ing debian-emacsen, as this should be of interest for Emacs users and
developers. Also, I would like to read other people's opinion about this.]
Jérôme Marant wrote:
Since the FDL documents contain invariant sections, they will have to be
moved to non-free very soon.
When you do this, p
There seems to be something seriously wrong with the load-path in
current Emacsen. The Debian Emacs Policy states:
,
| 9) Emacs lisp load path.
|
|At a minimum, each emacs must have the following directories in the
|given order in their load path:
|
| /etc/
| /etc/emacs
|
The Debian Emacs Policy says:
,
| /usr/share//site-lisp should be used instead of the normal
| site-lisp directory for that flavor of emacs, and the package for a
| given flavor of emacs should not have the normal site-lisp
| directory. For example, instead of the emacs21 package hav
Romain Francoise wrote:
Starting with version 20060120-2, it is now possible to install the -x,
-gtk and -nox binary packages concurrently. The new alternative
`emacs-snapshot' determines which package owns the emacs-snapshot
command.
There is currently no preference which binary owns the emac
Romain Francoise wrote:
But now that I think more about the whole thing, there is another
problem: if /usr/bin/emacs-snapshot becomes an alternative, it'll be set
up from the first subflavor's postinst, and there's a good chance that
it would be too late if an Elisp package's postinst runs before
Romain Francoise wrote:
Sven Joachim <[EMAIL PROTECTED]> writes:
If the DOC file is identical for every architecture, yes.
Of course it is, it's just an ASCII text file with some control
characters.
The point is that it is generated (by the `make-docfile' utility) from
Romain Francoise wrote:
The DOC file is strongly tied to the Emacs binary as dumped during the
build, so it's recommended to ship it with the binary itself. But now
that I look into it, I see that the three files are identical:
[...]
... the file is just copied over from the -common directory w
dd in each binary package an offer to distribute the source code
(details are in section 3b of the GPL).
Possibility (a) should be preferable both for you and for users of your
backports.
Regards.
--
Sven Joachim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
[EMAIL PROTECTED] wrote:
Under emacs-snapshot 20051207-1, I get the following error when
opening or creating a *.ly file:
File mode specification error: (wrong-type-argument arrayp 0)
Can somebody else confirm the problem? Lilypond mode appears to
work for my installation of emacs21. Bu I haven
Romain Francoise wrote:
The fine folks at Ubuntu have added a new `emacs-meta' source package to
their distribution which provides empty binary packages `emacs' and
`emacs-nox' that just depend on emacs21 and emacs21-nox:
ftp://ftp.ubuntu.com/ubuntu/pool/universe/e/emacs-meta/>
It allows ne
places: emacs21 (<< 21.2-4)
from debian/control.
Thank you very much for packaging emacs-snapshot.
--
Sven Joachim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Romain Francoise wrote:
What would people think of making emacsen-common provide a default Emacs
init file in /etc/skel that would enable Font Lock mode and Transient
Mark mode? I think very few new users wouldn't want them, and even if
they do they could either remove the default ~/.emacs.el fi
In GNU Emacs 22, Auto Compression mode is enabled by default. Therefore
and because of the growing number of packages coming with Emacs, it
makes sense to compress the Elisp source in the emacs-el
package, saving probably some 25-30 Megabytes of disk space. Also, in
a way these files are documenta
76 matches
Mail list logo
