Re: [nongnu] main e7a6b32: * elpa-packages (haml-mode): Manually pin a version

Re: [nongnu] main e7a6b32: * elpa-packages (haml-mode): Manually pin a version

[Philip Kaludercic]

zge@savannah.gnu.org (Philip Kaludercic) writes:

> branch: main
> commit e7a6b32fbf4c7821bdb223aa28f1d09d0ccd7c19
> Author: Philip Kaludercic <philipk@posteo.net>
> Commit: Philip Kaludercic <philipk@posteo.net>
>
>     * elpa-packages (haml-mode): Manually pin a version
> ---
>  elpa-packages | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/elpa-packages b/elpa-packages
> index 20f44aa..30296e4 100644
> --- a/elpa-packages
> +++ b/elpa-packages
> @@ -82,7 +82,12 @@
>  
>   ("guru-mode"		:url "https://github.com/bbatsov/guru-mode")
>  
> - ("haml-mode"		:url "https://github.com/nex3/haml-mode")
> + ("haml-mode"		:url "https://github.com/nex3/haml-mode"
> +  ;; The version attribute is set to "0", yet the the maintainer(s?)
> +  ;; seem unresponsive (https://github.com/nex3/haml-mode/issues/40)
> +  ;; and thus the package isn't published on the main archive.  We
> +  ;; manually set the latest commit to a proper version number:
> +  :version-map ((nil "3.1.10" "bf5b6c11b1206759d2b28af48765e04882dd1fc4")))
>  
>   ("haskell-tng-mode"	:url "https://gitlab.com/tseenshe/haskell-tng.el")

It seems that despite pinning a release, no package was released on the
default archive?  This should be done to fix the incompatibility in
sass-mode dependency list.

-- 
	Philip Kaludercic

Re: [nongnu] main e7a6b32: * elpa-packages (haml-mode): Manually pin a version

[Stefan Monnier]

>> +  ;; The version attribute is set to "0", yet the the maintainer(s?)
>> +  ;; seem unresponsive (https://github.com/nex3/haml-mode/issues/40)
>> +  ;; and thus the package isn't published on the main archive.  We
>> +  ;; manually set the latest commit to a proper version number:
>> +  :version-map ((nil "3.1.10" "bf5b6c11b1206759d2b28af48765e04882dd1fc4")))
> It seems that despite pinning a release, no package was released on the
> default archive?  This should be done to fix the incompatibility in
> sass-mode dependency list.

I believe I just fixed it (we'll see if the package gets released).
The above map means "use 3.1.10 if there's no Version:".
Of course, that doesn't fix issue #40 :-(


        Stefan

Re: [nongnu] main e7a6b32: * elpa-packages (haml-mode): Manually pin a version

[Philip Kaludercic]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> +  ;; The version attribute is set to "0", yet the the maintainer(s?)
>>> +  ;; seem unresponsive (https://github.com/nex3/haml-mode/issues/40)
>>> +  ;; and thus the package isn't published on the main archive.  We
>>> +  ;; manually set the latest commit to a proper version number:
>>> +  :version-map ((nil "3.1.10" "bf5b6c11b1206759d2b28af48765e04882dd1fc4")))
>> It seems that despite pinning a release, no package was released on the
>> default archive?  This should be done to fix the incompatibility in
>> sass-mode dependency list.
>
> I believe I just fixed it (we'll see if the package gets released).
> The above map means "use 3.1.10 if there's no Version:".
> Of course, that doesn't fix issue #40 :-(

True, but it seems that haml-mode is practically abandoned.  The
maintainer is still active, but there appears to be no activity on their
Emacs Lisp packages.

And on the topic of broken packages, it seems color-theme-tangotango is
still part of NonGNU ELPA, even though I have removed it from
elpa-packages and (attempted to) deleted the branch.  Is there something
I am forgetting?

-- 
	Philip Kaludercic

Re: [nongnu] main e7a6b32: * elpa-packages (haml-mode): Manually pin a version

[Stefan Monnier]

> And on the topic of broken packages, it seems color-theme-tangotango is
> still part of NonGNU ELPA, even though I have removed it from
> elpa-packages and (attempted to) deleted the branch.  Is there something
> I am forgetting?

No, it's just that our scripts know how to add but not how to
remove packages.

The `archive-contents` file is not rebuilt each time, instead
it's modified.

We probably need some kind of "GC" that we can run weekly.


        Stefan