I have begun packaging:
https://salsa.debian.org/codingquark/elpa-lin
Feedback welcome.
Package: wnpp
Severity: wishlist
Owner: Dhavan Vaidya
* Package name: elpa-lin
Version : 1.0.0
Upstream Author : Protesilaos Stavrou
* URL : https://git.sr.ht/~protesilaos/lin
* License : GNU GPLV3
Programming Lang: elisp
Description : Lin is a
Package: wnpp
Severity: wishlist
Owner: Dhavan Vaidya
* Package name: elpa-denote
Version : 2.1.0
Upstream Author : Protesilaos Stavrou
* URL : https://git.sr.ht/~protesilaos/denote
* License : GNU GPLV3
Programming Lang: elisp
Description : Denote is
things I should consider?
Thanks for the hints, those helped me be super quick about the things.
- Dhavan.
I shall be attempting to upgrade soon.
Sent with Proton Mail secure email.
--- Original Message ---
On Thursday, July 6th, 2023 at 04:11, Nicholas D Steeves
wrote:
> Hi Dhavan,
>
> I'm forwarding this to your new email address, so there will be a record
&g
.
[1]: https://wiki.debian.org/qa.debian.org/gfdlinvariant
--
Dhavan
Dhavan V writes:
> Hello!
>
> I maintain modus-themes[1] for Emacs team. In the process of upgrading
> to upstream version, I have come across
> license-problem-gfdl-invariants[2] in ~doc/modus-themes.info~ [3].
[3]:
https://salsa.debian.org/emacsen-team/modus-themes/-/blob/m
Hello!
I maintain modus-themes[1] for Emacs team. In the process of upgrading
to upstream version, I have come across
license-problem-gfdl-invariants[2] in ~doc/modus-themes.info~ [3].
I do not understand legality of the matter fully and seek advice as to
how this can be easily handled. I am also
Lev Lamberov writes:
> There's a problem with building:
>
> makeinfo elpher.texi -o debian/elpher.info
> make[1]: makeinfo: No such file or directory
> make[1]: *** [debian/rules:11: override_dh_installinfo] Error 127
>
> You need to build-depend on a package with makeinfo. As I can see, it is
>
Hello Lev,
The package is mostly ready now. I am saying mostly because I have done
what I "felt" was "okay" in installing the upstream (`.texi`)[1] as info
files.
If you get time to review the work, we should be ready!
[1]: https://salsa.debian.org/emacsen-team/elpher/-/blob/master/debian/rules
Hi Lev!
There has been another upstream v1.0.2 that I have updated and tagged.
Uploading it right now, or waiting for a few more releases is up to you!
Thanks!
--
D Vaidya
‐‐‐ Original Message ‐‐‐
On Sunday, December 6th, 2020 at 3:31 PM, Lev Lamberov
wrote:
> So, your .PHONY may be as follows:
>
Thanks! Done!
> Also, your d/changelog does not contain any entry on 1.0.0, and
>
> d/modus-themes-pkg.el needs to be updated. Or maybe you forgot to push
>
> I looked at the docs, and I think I got the use-case. I saw in
>
> [ace-link] that `.PHONY` is used for `override_dh_auto_build`. I
>
> don't know yet which recipe I should be adding for modus-themes. I
>
> will be searching for relevant docs.
>
My current understanding is to add:
`.PHONY
Hi Lev!
‐‐‐ Original Message ‐‐‐
On Monday, November 30th, 2020 at 11:22 AM, Lev Lamberov
wrote:
> Also, I'd add .PHONY target to your d/rules. Please, see documentation
>
> on GNU make about phony targets [phony]. But it can wait till the next
>
> release, I think.
>
> [phony] h
> That is the last change. Please, update debian/0.13.0-1 tag after it,
>
> and I'll upload your package.
Hi Lev!
Sorry for all the delay. I've now tagged debian/0.13.0-1 and pushed.
Kindly review :)
--
D Vaidya
signature.asc
Description: OpenPGP digital signature
> looked into your changes, and here are some comments.
>
> Accidentally your "internal" LAN email was used instead of your
> "external" one:
>
> E: modus-themes changes: bogus-mail-host Changed-By codingqu...@rpi3.lan
> E: elpa-modus-themes: bogus-mail-host-in-debian-changelog codingqu...@rpi3.lan
Hello Lev,
I have pushed v0.11.0, kindly upload!
Thanks!
--
D Vaidya
‐‐‐ Original Message ‐‐‐
On Thursday, July 30, 2020 6:05 PM, Lev Lamberov wrote:
> When someone asks for sponsoring an upload, I expect the person to at
> least try to build their package and run lintian against it. Currently,
> I see only boilderplate generated by dh-make-elpa. Please, m
‐‐‐ Original Message ‐‐‐
On Monday, July 27, 2020 6:27 PM, David Bremner wrote:
> Done. You are a maintainer. Ping me on #debian-emacs if you have any
> access problems.
Thanks David!
I have pushed my updates, and they should work with gbp. However,
there seem to be an issue with upstre
‐‐‐ Original Message ‐‐‐
On Monday, July 27, 2020 4:51 PM, David Bremner wrote:
> Just let me know the source package name, and I can create it.
git://thelambdalab.xyz/elpher.git - we should be calling it "elpher",
seems to be following our naming team's conventions.
---
D Vaidya
ITP: #963032
I have began working on the package, and would like a (salsa?)
repository to push my work. How should I proceed?
PS: dogsleg has agreed to sponsor the package.
--
D Vaidya
Sorry, I sent it from my $WORK email instead of $PERSONAL
--
D Vaidya
‐‐‐ Original Message ‐‐‐
On Monday, July 27, 2020 12:25 PM, Dhavan Vaidya wrote:
> ITP: #963032
>
> I have began working on the package, and would like a (salsa?)
> repository to push my work. How shou
Lev,
Whenever you get time, kindly upload 0.10.0-3, I have changed Vcs-*
fields to reflect the updated salsa paths.
The reason behind this change was an issue raised by spwhitton on
#debian-emacs OFTC. d/control looked wrong because of the repository
being named elpa-modus-themes instead of modus
because one is not a prerequisite for
the other, I thought it would be nice not to install extra files.
Feel free to package them together, if you want.
---
---
Dhavan writes:
> The reason I created separate packages for those is two-fold:
>
> 2. Early feedback I received suggested t
Greetings!
dogleg agreed to sponsor the uploads for elpa-modus-themes if I make
sure it works with gbp+pbuilder.
Having done so, I would like to request dogsleg to kindly check the
work I recently pushed. I have updated the package with newer upstream
tag (0.10.0), made some adjustments such as u
Lev Lamberov writes:
> I think now packaging is OK. I tried to build it and found out that you
> set pristine-tar to True in d/gbp.conf, but not pushed pristine-tar
> branch to the repo (please, use `gbp push' to push tags and commits on
> all your branches, but also consult with `man gbp-push').
On Monday, June 15, 2020 3:26 PM, Lev Lamberov wrote:
> I added some more comments to your
> 50b197311e733b6f4842fa3753f072d6792087fd commit in Salsa.
Thanks, made some changes. Check [1] & [2] along with the
replies to the comments.
Thanks!
[1]:
https://salsa.debian.org/emacsen-team/elpa-modu
Lev Lamberov writes:
> I briefly looked into your package and here are some comments:
>
> - d/control: in your case short description should not start with a
>capital letter (s/Set/set/)
>
> - d/control: Vcs-* fields point to modus-themes (which doesn't exist,
>as I can see), but the rep
Hello!
I have created salsa repository[1] and have pushed `master` with
`debian/` setup. Please review my work as this is my first time packaging
from scratch!
Thanks!
PS: bremner has helped on oftc, thanks!
[1]: https://salsa.debian.org/emacsen-team/elpa-modus-themes
--
Dhavan V
How silly of me, I found the following from Nicholas' emails:
Dhavan, please see my reply to David Krauser for #2 (Policy compliance).
For #4 see § "COMPATIBILITY LEVELS" of debhelper(7) (man debhelper). If
you have any questions after reading those, please don't hesita
Hello,
I have adopted geiser, and 6 months ago I had packaged 0.10 from
upstream[1]. Since then, I have been occupied unfortunately and
regrettably. Anyway, I am back!
Tracker[2] says the next most important thing is to bump Debian Policy
version. Upgrading checklist[3] doesn't seem very helpful
‐‐‐ Original Message ‐‐‐
On Friday, November 1, 2019 12:05 AM, Nicholas D Steeves
wrote:
> At this time let's move to the next stage: adopting your first package,
> and getting it into shape for an upload. The following brief list
> consists of things that your sponsor will ask you to
32 matches
Mail list logo
