Hello Paul,
Thanks again for the review! I have made further changes, as well in how
the upstream file is made. Using the setup.py, this is much simpler! I
do have a few comments below:
1.The License lines in debian/copyright are incorrect, please use the
right ones from the copyright-format spec
Non-DD review.
I propose to remove override, since `liquidprompt` never executed, only
sources.
Consider applying attached patch.
--
Best regards, Dmitry Bogatov ,
Free Software supporter, esperantisto and netiquette guardian.
GPG: 54B7F00D
diff -r -U 7 -N liquidprompt-1.9/debian/lintian-overri
On May 13, 2015 6:19 AM, wrote:
>
> Hi,
>
> (Debian 8 updated here.)
>
> I've done a theme for Mate and I'm packaging it.
>
> So, I've done a package which first, installs all the files under
/usr/share/theme/mytheme.
> This part is OK and I can choose my theme in mate.
>
>
>
> Now, I've been work
Hi,
I'll tell you how I do mines but keep in mind that I'm not a debian
developpers. I may learn things as well if some debian developpers would answer.
> De: "Ole Streicher"
>
> * Should it be native or not?
I'd say native as you will not ship any upstream source code within it. Will
you ?
Hi,
(Debian 8 updated here.)
I've done a theme for Mate and I'm packaging it.
So, I've done a package which first, installs all the files under
/usr/share/theme/mytheme.
This part is OK and I can choose my theme in mate.
Now, I've been working (and reading a lot about) on how to install it:
On 12 May 2015 at 20:29, Andrey Rahmatullin wrote:
> [I don't intend to sponsor this]
>
> You should put the Debian repo, not the upstream one into Vcs-* control
> fields.
>
Thanks, fixed.
> Recommending both screen and tmux looks strange. Recommending acpi which
> is useful only for laptops loo
anonymo...@airmail.cc writes:
> And now that I'm starting to see contributions from the new developers
> from the Debian Women project I'm appalled with difference of
> treatment. Almost all their emails, questions and patches get educated
> and helpful replies. The difference is so vast that to me
Hi,
I want to create two metapackages "python-astropy-all" and
"python3-astropy-all" which install astropy and all affiliated
packages. However, I could not find a good tutorial for this:
* Should it be native or not?
It looks like usually metapackages are native; however in my case the
package
Hello,
> Gesendet: Dienstag, 12. Mai 2015 um 03:51 Uhr
> Von: anonymo...@airmail.cc
> An: debian-mentors@lists.debian.org
> Betreff: Please create a Debian Human project
>
> I've been holding my self back from writing this for quite a while. This
> rant stems from my almost 2 years of frustration
9 matches
Mail list logo
