Bug#923922: ITP: ruby-github-pages -- set up a local Jekyll environment in sync with GitHub Pages

2019-03-06 Thread Daniel Leidert
Package: wnpp
Severity: wishlist
Owner: Daniel Leidert 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: ruby-github-pages
  Version : 197
  Upstream Author : GitHub, Inc.
* URL : https://github.com/github/pages-gem
* License : MIT
  Programming Lang: Ruby
  Description : set up a local Jekyll environment in sync with GitHub Pages

A simple Ruby Gem to bootstrap dependencies for setting up and maintaining a
local Jekyll environment in sync with GitHub Pages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAlyAzSEACgkQS80FZ8KW
0F0UjRAAqUz5Fe77Y2aHlGhXEJ1dN55+eIObZcSK6liefa7tIow0VbElVtSgtu4W
35C6ThdzyQ1yPFwZUxG3G9olfDEui23JytaH8eBHuZffEJTELf10ob70x5AjyUUf
lWg7gYYZo+p5u+0YL47Ki5lGFkecpSUMLsG3iJEunRtLT48dCvCJ81Day7OEUZIv
EscZXYVdoynGE9tG722ZgEq1zCg+tG55fQuMOh0w1ErQeDVS+dTM9hsvNIvOGty4
vPPbxuCJRB9nlH7JZ6JNnQv2BfJRR6KFWNyI+PcWRZGLth9ttxwGefrAsnwwHviE
GoLXH1N640ss3DsWgtKrr8rinW1WyfbssfYbnQwtanRkaXEulNgBJnpjWShR5rIq
bLHhAkdrtTXBiNBNjzgX6iocuWn8T38lxtxHbVBYK7+M5yH3HvvgnLh7KcSjI13q
vcbYHovRnr+TReadRqUlTQxnwiCfoIjzM4lXx5m8eLFF7OFT91ScqkiXqya4zcRN
ah50Cl0Z21JauO5bSEy95e62W/sfuCPLn8YW5y6KJ/I1luyJ6yRTIzA14iE5BFrH
r89ZqX6vYrxI6TQXe0eJqMg2OG5L5rbVswH6rqstZx+XUSjDXBvlhk2UcnhUssAr
TREvbKHRtGhincdp1XQXVyL5EdeMIUFDsrC/ZgsDY5DPqYQpc1c=
=ErBO
-END PGP SIGNATURE-



Bug#923920: ITP: ruby-github-pages-health-check -- check GitHub Pages for common DNS configuration issues

2019-03-06 Thread Daniel Leidert
Package: wnpp
Severity: wishlist
Owner: Daniel Leidert 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: ruby-github-pages-health-check
  Version : 1.16.1
  Upstream Author : GitHub, Inc.
* URL : https://github.com/github/pages-health-check
* License : MIT
  Programming Lang: Ruby
  Description : check GitHub Pages for common DNS configuration issues

The plugin checks a GitHub Pages site for common DNS configuration
issues.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAlyAytMACgkQS80FZ8KW
0F21sRAAik4UARwDYl3f8f/SJX0X1+p6h7O4fhP4/YRUWPqR9/d3SdMH9YTkYsRa
65FkFBUpK+5NNlMYqV4wzLNA4nnrwwaP68qz4mn2mN1w3T3fhjraWLlMuRvsYN3o
wi+lmh+8frzj7IXC0U2N/hAx4cHLgrhNkY/vWHspzjqWraWg3d/aT36DKnnVtx8z
Nz5HwjwCDzzDH95xZAUnEfRjG5O393DxrRq+Ct9WUhgGLgz7NpFFNYoYjW2S0gWE
zBuaRyA2tSx86Casaz2nj8F0xV2plQRHIXzi8FyntRgcYVi34xo+rDQsByXP5xQq
bmUGilx0io/fFhAcxFrVVLCYlDJ2Z/LTHhBCx3oH399EE3srsxEK9kTh+/W99Vkn
RzVXmgFit/Pf+DC1TB6U4K0QqkE8W4HrFBSStbOgnDEvKKf7gCWxx/Ce/jZTHBfO
MnZak5cW2ZzKmRz81RoIN4MZAtruGf0K6I8MUkjLQA0ls7UnEor6tummtj6yXB4w
TXmtwRdJZOVQQ+a9EuPhhvoOu5BbX+utgq6l1yPJnrNJYGRkQhGV8kZ+4FUIR5aA
5QfnpdHmksrKpJzp6/ZNup0xUpIWVO+jJFKTRPfiIM++gJIGRxiV4yd/OZrCWeqg
oVvRN/VHNZDJ2Lb7FV1Xyqp5J50/jhYJGMTiGa8swynIfq/B7uk=
=0VAS
-END PGP SIGNATURE-



Bug#923917: ITP: ruby-jekyll-sitemap -- Jekyll plugin to silently generate a sitemap

2019-03-06 Thread Daniel Leidert
Package: wnpp
Severity: wishlist
Owner: Daniel Leidert 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: ruby-jekyll-sitemap
  Version : 1.2.0
  Upstream Author : GitHub, inc
* URL : https://github.com/jekyll/jekyll-sitemap
* License : MIT
  Programming Lang: Ruby
  Description : Jekyll plugin to silently generate a sitemap

Jekyll plugin to silently generate a sitemaps.org compliant sitemap for
a Jekyll site.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAlyAqFMACgkQS80FZ8KW
0F3oRxAAz4kbywzxZVXbG7P9PpaGCPTLfIfv7Gl2ce5SzvaUd7lxblpX9JMIY12K
lGIWqsb6FKR8Ulo9YRhffl9jL6MZHJT/HkWP4abmBivKXjNV3T2ccKh0IKJJrnbj
/tDAVrRKC9WLeTx3wcSkupX1GlD73024yTS9oUwgUu73mcIKc9E98QJ7/x9hCHYa
oTO+XlwFObTBU8NTeimlHiu1A1KuvA0L2rCIngSNgK8MnaCkTAlDCkijHOSYH8/0
YndN+ZKnJWCzOdZmnTINR9QhlURoC4PVCvWdc+G6F/08eQJ8ijptH6OcbUQ0aOBg
5aYYh7py9v4dIDbat7Yk0MslWhIa/b+M99X7iaDy002Hi5GJl2cmncJjI/OwggXT
fEchqo+538XA3VZrpT0C5yWQ88wpKw5xTqqQ5/zCOZ8tZCo2vRVZ/r+ahJlyv3mQ
pjTt2u47Kj/wYE0kRsmeRETyFq3qsAXtMxCH/Vsflbauu5WHF+XGPZpDj776RsP+
oUEHxpyZdrnA45QTC182T2koBFvge8fRGuC1Zk6fWW0RJFLKQLW6AOmGHDyM2X6t
0ilGvUv2SWyic88z1fHTdQ6jGo6JQkBHGFmFUmMkQLMAkHa9P5mTahdPHV1YEIJH
CZPaQU04Iyckc2lhThwzlCEHOSgvJZeUJM0uUxUpWQelQq+hhXo=
=kWgN
-END PGP SIGNATURE-



Bug#923912: ITP: jekyll-seo-tag -- Jekyll plugin to add metadata tags

2019-03-06 Thread Daniel Leidert
Package: wnpp
Severity: wishlist
Owner: Daniel Leidert 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: jekyll-seo-tag
  Version : 2.5.0
  Upstream Author : Ben Balter
* URL : https://github.com/jekyll/jekyll-seo-tag
* License : MIT
  Programming Lang: Ruby
  Description : Jekyll plugin to add metadata tags

Jekyll SEO Tag adds the following meta tags to the site:
.
  * Page title, with site title or description appended
  * Page description
  * Canonical URL
  * Next and previous URLs on paginated pages
  * JSON-LD Site and post metadata for richer indexing
  * Open Graph title, description, site title, and URL
  * Twitter Summary Card metadata
.
While one could theoretically add the necessary metadata tags oneself,
Jekyll SEO Tag provides a battle-tested template of crowdsourced
best-practices.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAlyAmaEACgkQS80FZ8KW
0F3E/hAAtBuKiwRVkl3u2GBb+IKPNM0qyTzvxTjlQiEp9b2NpPO/i2FL+yN4Go3Z
6WuZaa6Rg0VwdXA5zg1NG0g/SFevyNXfrJV9SuId5BMB+5dnBDj4xu9OfqKsZSGL
u9xfU9J9B/TuAOlr10OqNn3r1eL81qIUSOuZGhJB9gveJtpTZK6+HAIrKjLpHqcr
A/DWheYYKvoTJtsXy2tUtexhf9Zy2Yq+dfWH9Q88GfM36SChxQ1ArRRCLR4NPnYf
mc0+yS7fjANXRQVCnZ3bd5rabTH3s1N+kXGXXVZTWkEfWgRVKhi/crq7r2sgSJxt
z4R99eCfG/jbmNVE1EzFWnKuD+YJg8Y2uKpJwZ/11VpcvsY7Fj2iqifwekuVKQIg
4zxscZA4Gy2y4n61/6xXT1t626Tz2wPlylsJzVMaW1EXXJy6R7OmiClyOPGW1N0v
WoOgGMPsCn8RcqySoekcgWPRDPLbqAgYDTkx06/QA8dvXTjPk6kXcyVDhPm/UuGK
JDFLSJ+eqUgyQ4sAyGU2GWewCOVzvlfXZW0vBkklTdV8yQ2+BCK+kqn5Hac0wKoG
fDlMeume2Zmo24ZU4GIDeomKKKTV+6PSLBJG4+NdiKbfgtvcLmMtGK13lbvPyIKU
2cXP6gTiClea3YlLjhNpFoP3CUFWt5ZRSvim5STHIaVEein2hX4=
=z7h9
-END PGP SIGNATURE-



Re: Tell me about your salsa experience

2019-03-06 Thread Mo Zhou
Hi Alexander,

On Wed, Mar 06, 2019 at 07:05:34PM +0100, Alexander Wirt wrote:
> Thats where you come in, please tell me how tools like salsa, alioth, 
> git, tracker and so on changed to way you work. I want to know everything,
> the good, the bad and so on. 

I started to use Alioth since 2014 and I was a git user from the
beginning. At that time every new git repo has to be manually created,
and to remove a git repo one has to use the dangerous command `rm -rf`.
Even worse, different teams have different directory layouts, such that
Debian Science team wrote a shell script for creating new git repos on
Alioth. I'm a post-90s and that feels like sort of stoneage workflow,
literally. Salsa just makes my life easier.

Tracker is definitely the first service that I'd access if I wanted to
see the overview of some package. And I always recommend software
upstream to get package overview via tracker.d.o . However I don't know
how tracker changed my way to work because I don't remember what I've
done when tracker was not available.



Bug#923911: ITP: ruby-jekyll-include-cache -- Jekyll plugin to cache the rendering of Liquid includes

2019-03-06 Thread Daniel Leidert
Package: wnpp
Severity: wishlist
Owner: Daniel Leidert 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: ruby-jekyll-include-cache
  Version : 0.1.0
  Upstream Author : Ben Balter
* URL : https://github.com/benbalter/jekyll-include-cache
* License : MIT
  Programming Lang: Ruby
  Description : Jekyll plugin to cache the rendering of Liquid includes

Render computationally expensive includes (such as a sidebar or navigation)
once, and then reuse the output any time an include is called with the same
arguments, potentially speeding up the site's build significantly.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAlyAgpwACgkQS80FZ8KW
0F31cw/9HpKLuB7PGSlcfpP/O5KYTs3dYjZ8ZtUhZ4+7gKmhbAbFOOdGZ62DOMzl
FM+jy7YtRiyBzRAvTLMnzG8eCyUVFxvktA7kTYBh5NN/1iIhY4GYP6sDbyjUNFam
meGUkgTh74OiVvIBqneU6ETTVqcO84O3rcJyQMbKd3Z2k3WxQPdLRC2zDl+HfPAO
BWX8mahPe0TG3f06umZJIhsd5xXoXR2Y8MRPGm0w2xW1Moy3fnOjNIu0ubFZ1GbZ
dTh8UVOsRQ440irHI9Q5wOYIN/asVVpC0nuNZ6PTR3XcRklWAIFx7I/qAaURqWfj
pFODptqwArc6pIW+hz8Nq3cWoimwyqibepL9MoCWT+T+gooPGhW/V6oJpu3JvZav
0wwkTrTuP57S2COOLTJoWqR/OVq8dYwbWaEejT4nrhydKd38VRkT4Y2xNQd+qGW2
8o36QrOz56XnT7aLgaIdT0b4EThUSXVzAaY91W4jQTJFxAEgh5sGebfFvuFubHPc
VdpLYINGzBf5N1aWimNrob+NDBdeqHMMWnwAK/GNovWXLbT20UB3agHBL3vBgmg+
sVF8cf/LQC3oebVAxtuWKR9mSUoP/nm0C6+mACIEE1+j1FSinL2VQML2JHdROnQN
CVNu0+PCqB7UsQucIdZo7chiLa/VUWqfxOQo7Qx31eRuJ2QUDYs=
=vlaI
-END PGP SIGNATURE-



Bug#923884: ITP: pyqt5webengine -- Python bindings for Qt WebEngine

2019-03-06 Thread Dmitry Shachnev
Package: wnpp
Severity: wishlist
Owner: Dmitry Shachnev 

* Package name: pyqt5webengine
  Version : 5.12
  Upstream Author : Riverbank Computing Limited 
* URL : 
https://www.riverbankcomputing.com/software/pyqtwebengine/intro
* License : GPL-3
  Programming Lang: Python
  Description : Python bindings for Qt WebEngine

In pyqt5 5.12 the WebEngine buildings were split into a separate module. So we
need a new source package to continue shipping python3-pyqt5.qtwebengine etc.

Upstream name is PyQt5WebEngine. The number 5 in source package name is for
consistency with existing pyqt5 and pyqt5chart source packages.

I will maintain this package under the Debian Python Modules Team umbrella.

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Tell me about your salsa experience

2019-03-06 Thread Alexander Wirt
Hi, 

I was invited to be a speaker at the drupal con to talk about the 
evolution of tooling in open source projects [1]. I will take part
in a panel together with other open source projects like Gnome
or Drupal, we talk about about the past - the tool we used, its history
and so on. Then we want to talk about the evolution of our tools, the
challenges and how the way we work changed together with the tool we
introduced. 

Thats where you come in, please tell me how tools like salsa, alioth, 
git, tracker and so on changed to way you work. I want to know everything,
the good, the bad and so on. 

Thanks in advance

Alex

P.S. I will be in Seattle from 6th april to 11th april, in Portland just for
the evening of the 11th. Next is nearby yosemite from 12th to 15th and at
least San Francisco from 15th to 22nd. If you want to meet for a beer, please
get in touch with me. I am also willing to give a talk about Debian and/or 
Salsa in Seattle or S.F.. 

[1] 
https://events.drupal.org/seattle2019/sessions/gathering-open-source-projects-discuss-evolving-their-tools


signature.asc
Description: PGP signature


Bug#923870: ITP: zabbix-api -- implementation of the Zabbix API in Python

2019-03-06 Thread Bas Zoetekouw
Package: wnpp
Severity: wishlist
Owner: Bas Zoetekouw 

* Package name: zabbix-api
  Version : 0.5.3
  Upstream Author : Aleksandr Balezin 
* URL : https://pypi.org/project/zabbix-api/
* License : LGPL
  Programming Lang: Python
  Description : implementation of the Zabbix API in Python

Zabbix-api is a Python library for Zabbix administration tasks via the
zabbix-API.

It's available for both python2 and python3.

I'm mainly pakcaging this because ansible's zabbix_host module needs
this python lib in order to function.

I'd prefer to maintain this in the Debian Python Modules Team, but I'm
not currently a member there.



Re: Debian Buster will only be 54% reproducible (while we could be at >90%)

2019-03-06 Thread Matthias Klumpp
Am Mi., 6. März 2019 um 10:40 Uhr schrieb peter green :
>
> > Because of their design, binNMUs are unreproducible, see #894441 [3] for
> > the details (in short: binNMUs are not what they are ment to be: the source
> > is changed and thrown away)
> To be specific, the source tree is extracted, then an entry is added to 
> debian/changelog and then the package is built. This modified source tree is 
> not retained.
> [...]

(Experience report incoming)

I have once tried that in the Tanglu derivative, and found out that
this wasn't as easy as I initially thought because a lot of packages
run special tools prior to building their sources, e.g. to edit
d/control or to read d/changelog and inject data in several places.
So, the option there was either to create a chroot dedicated to the
source package rebuild (installing all Build-Deps and Pre-Deps prior
to the actual source rebuild), or to not actually rebuild the source
package but just edit the d/changelog file and recreate the tarball.
For Tanglu we went for the "just edit d/changelog and re-tar, re-sign
& upload" which worked fine and without any noticeable issues - this
was mainly due to the limited build power we had at the time. For
Debian, which has a lot more resources, just full rebuilding the
source with all dependencies is likely much cleaner, but this approach
might be a bit slow for huge transitions.

At Ubuntu, some people seem to do this process manually, that is run
some scripts locally, rebuild sources locally & upload (unless that
has changed recently).
In general, having source d/changelog aligned with the actual binaries
produced is a really great goal!

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/



Bug#923856: ITP: dotenv-cli -- .env configuratin loader

2019-03-06 Thread Bastian Venthur
Package: wnpp
Severity: wishlist
Owner: Bastian Venthur 

* Package name: dotenv-cli
  Version : 1.0.0
  Upstream Author : Bastian Venthur 
* URL : https://github.com/venthur/dotenv-cli
* License : MIT
  Programming Lang: Python
  Description : .env configuratin loader

Dotenv-CLI is a simple package that provides the dotenv command. It reads the
.env file from the current directory puts the contents in the environment and
executes the given command.

dotenv supports alternative .env files like .env.development via the -e or
--dotenv parametes.



re: Debian Buster will only be 54% reproducible (while we could be at >90%)

2019-03-06 Thread peter green

Because of their design, binNMUs are unreproducible, see #894441 [3] for
the details (in short: binNMUs are not what they are ment to be: the source
is changed and thrown away)

To be specific, the source tree is extracted, then an entry is added to 
debian/changelog and then the package is built. This modified source tree is 
not retained.

It seems to me that binnmus could be made reproducible by storing the 
debian/changelog modifications in the buildinfo, then re-applying it at 
reproduction time.