Vier Valentijnsdag thuis.

2017-02-03 Thread Champagne
Geachte mevrouw,
Geachte heer,

Valentijnsdag: een mooie gelegenheid om Champagne te drinken.
Op www.aCongy.com bieden wij u een prachtige champagne aan
Brut Tradition
van Breton Fils
Récoltant - Manipulant in Congy (Frankrijk).

Kwaliteit gewaarborgd :
Zoals geschreven in onze algemene verkoopsvoorwaarden, nemen wij uw flessen  
terug indien u niet tevreden bent !

Met hoogachting,
Het team van www.acongy.com

Bug#854026: ITP: python-scrapy-djangoitem -- Scrapy extension to write scraped items using Django models

2017-02-03 Thread Michael Fladischer
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-scrapy-djangoitem
  Version : 1.1.1
  Upstream Author : Scrapy developers
* URL : https://github.com/scrapy-plugins/scrapy-djangoitem
* License : BSD-3-clause
  Programming Lang: Python
  Description : Scrapy extension to write scraped items using Django models

 scrapy-djangoitem is an extension that allows you to define Scrapy items using
 existing Django models. This utility provides a new class, named DjangoItem,
 that you can use as a regular Scrapy item and link it to a Django model with
 its django_model attribute.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAliUQvwRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WpA7gf/cVU6h1PsIy67dH7RWsoyGkvWe0zWTpJp
VRWmOGwpSsjEWY43HUl+ohAK8PYL4wG/8Fs1rGpSuPE1/Pgc88t0UnP3v3jk2ApO
OJjdNlhuCZUf8XXuOkVaL9xKwJGx8sxGqrWZt/KRJGnq9JtZvxgoYITPwb4JScLB
3QXgKYAYWoRRCsVCnunrScv0eab1XdLSnzNYoRG/lTe4uvDMlQEP0BvJ4drSz9vR
ydXR6hCz28EzmDDSt3Rvrmj2LxgKHlMx2Hz+akwnBitoOM5YgPtl9ykVBMebaRjt
61208qg3HvlI492BMLoP+fszHWT1Vbg53qcWyMzL9GRD6dBIOUdTkw==
=nSef
-END PGP SIGNATURE-



Bug#854027: ITP: python-scrapy-djangoitem -- Scrapy extension to write scraped items using Django models

2017-02-03 Thread Michael Fladischer
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-scrapy-djangoitem
  Version : 1.1.1
  Upstream Author : Scrapy developers
* URL : https://github.com/scrapy-plugins/scrapy-djangoitem
* License : BSD-3-clause
  Programming Lang: Python
  Description : Scrapy extension to write scraped items using Django models

 scrapy-djangoitem is an extension that allows you to define Scrapy items using
 existing Django models. This utility provides a new class, named DjangoItem,
 that you can use as a regular Scrapy item and link it to a Django model with
 its django_model attribute.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAliURFIRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90Wrwlwf+I0a3rUYJwIbMQaMfBjyYZUAynZ8BOzw6
3XEm/xXI+VAZUe4pcdLF6icbiQyJi2tIKl9vXOPwMrck/rJ4Ypa5hW/vFpAVS21q
gxf7E0pMFZKMeCJuHA1F9EsdMjwixzAnV2jvPw81xTJO0yLF/E6IM2YjCHx5P5Ac
hnH5vM/VK6yXmTSR5wgN++OKBbN3zWYGm0Tn2SD2kZ46SAsclLxGOeCL1gpIyYDs
qS0oJ4rDI1lFnyOEXy6r3vMR8eJDw9zeT/mB/2joMIuJ9Y0awhyDm5BGoUXcRass
C3BeLjKO3xo/mrfhcwA8KWA6VW0b+1ylu/aS853zKFrq6nhGNI3zgw==
=jOYG
-END PGP SIGNATURE-



Bug#854037: ITP : node-constants-browserify

2017-02-03 Thread Akash Sarda
Package: wnpp
Severity: wishlist
Owner: akash 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-constants-browserify
  Version : 1.0.0
  Upstream Author : Julian Gruber 
(http://juliangruber.com)
* URL : https://github.com/juliangruber/constants-browserify
* License : Expat
  Programming Lang: JavaScript
  Description : node's constants module for the browser

 node's constants module for the browser
 Dependency for browserify.
 .
 Node.js is an event-based server-side JavaScript engine.



Where to report Wayland-related bugs

2017-02-03 Thread Thibaut Paumard
Dear fellow developers,

I have started using GNOME Wayland possibly as my primary session. It
sort of feels different from the default X11 GNOME session in surprising
ways (overall rather more comfortable I would say).

I am seeing issues in some software that don't seem usable at all in
GNOME Wayland, e.g.:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852699

Where is the correct place to report such issues: the individual
affected packages (as I did with the above-mentionned bug), xwayland,
something else? Is there a usertag defined for such issues?

Kind regards, Thibaut.



Re: Where to report Wayland-related bugs

2017-02-03 Thread Emilio Pozuelo Monfort
On 03/02/17 11:42, Thibaut Paumard wrote:
> Dear fellow developers,
> 
> I have started using GNOME Wayland possibly as my primary session. It
> sort of feels different from the default X11 GNOME session in surprising
> ways (overall rather more comfortable I would say).
> 
> I am seeing issues in some software that don't seem usable at all in
> GNOME Wayland, e.g.:
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852699
> 
> Where is the correct place to report such issues: the individual
> affected packages (as I did with the above-mentionned bug), xwayland,
> something else?

It depends on the bug. If you want an app to be ported to wayland, then either
the app or the toolkit/framework, as appropriate. If an X app doesn't behave
properly, then XWayland. If you see a WM/compositor bug, then whatever
compositor you are using (gnome-shell/weston/...) ...

> Is there a usertag defined for such issues?

There isn't (yet).

Cheers,
Emilio



Re: Where to report Wayland-related bugs

2017-02-03 Thread Thibaut Paumard
Le 03/02/2017 à 12:35, Emilio Pozuelo Monfort a écrit :
> On 03/02/17 11:42, Thibaut Paumard wrote:
>> I am seeing issues in some software that don't seem usable at all in
>> GNOME Wayland, e.g.:
>>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852699
>>
>> Where is the correct place to report such issues: the individual
>> affected packages (as I did with the above-mentionned bug), xwayland,
>> something else?
> 
> It depends on the bug. If you want an app to be ported to wayland, then either
> the app or the toolkit/framework, as appropriate. If an X app doesn't behave
> properly, then XWayland. If you see a WM/compositor bug, then whatever
> compositor you are using (gnome-shell/weston/...) ...

Thanks Emilio,

In the meantime I have found a Fedora page that explains how to debug a
Wayland-related bug, for instance how to determine whether the bug is in
the compositor:
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems

Regards, Thibaut.



Bug#854045: ITP: libcrush -- C library to control placement in a hierarchy

2017-02-03 Thread Loic Dachary
Package: wnpp
Severity: wishlist
Owner: Loic Dachary 

* Package name: libcrush
  Version : 1.0.0
  Upstream Author : Sage Weil , Loic Dachary 
 & al.
* URL : http://libcrush.org/main/libcrush/
* License : GPL-3+
  Programming Lang: C/C++
  Description : C library to control placement in a hierarchy

Binary package names: libcrush, libcrush-devel

 libcrush maps an object signature to a list of devices on which to
 store the object. It is implemented as a pseudo-random, deterministic
 function obeying user specified placement constraints such as: the
 object must be stored on devices that are on two different machines.

The library existed for more than ten years as part of ceph[1]. It is however 
generaly useful,
for other storage software or other contexts in which data placement should be 
controlled.

[1] https://tracker.debian.org/pkg/ceph



Re: Where to report Wayland-related bugs

2017-02-03 Thread Michael Biebl
Hi there

Am 03.02.2017 um 13:00 schrieb Thibaut Paumard:
> Le 03/02/2017 à 12:35, Emilio Pozuelo Monfort a écrit :
>> On 03/02/17 11:42, Thibaut Paumard wrote:
>>> I am seeing issues in some software that don't seem usable at all in
>>> GNOME Wayland, e.g.:
>>>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852699
>>>
>>> Where is the correct place to report such issues: the individual
>>> affected packages (as I did with the above-mentionned bug), xwayland,
>>> something else?
>>
>> It depends on the bug. If you want an app to be ported to wayland, then 
>> either
>> the app or the toolkit/framework, as appropriate. If an X app doesn't behave
>> properly, then XWayland. If you see a WM/compositor bug, then whatever
>> compositor you are using (gnome-shell/weston/...) ...
> 
> Thanks Emilio,
> 
> In the meantime I have found a Fedora page that explains how to debug a
> Wayland-related bug, for instance how to determine whether the bug is in
> the compositor:
> https://fedoraproject.org/wiki/How_to_debug_Wayland_problems

I remember Simon doing quite a few of Wayland related bug reports, and
at least some of them were usertagged as

User: pkg-gnome-maintain...@alioth.debian.org
Usertags: wayland

https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintain...@lists.alioth.debian.org;tag=wayland

It would probably be good if you also use those when doing your bug reports.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Re: Where to report Wayland-related bugs

2017-02-03 Thread Thibaut Paumard
Le 03/02/2017 à 14:33, Michael Biebl a écrit :
> Hi there
> 
> Am 03.02.2017 um 13:00 schrieb Thibaut Paumard:
>> Le 03/02/2017 à 12:35, Emilio Pozuelo Monfort a écrit :
>>> On 03/02/17 11:42, Thibaut Paumard wrote:
 I am seeing issues in some software that don't seem usable at all in
 GNOME Wayland, e.g.:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852699
[...]
> I remember Simon doing quite a few of Wayland related bug reports, and
> at least some of them were usertagged as
> 
> User: pkg-gnome-maintain...@alioth.debian.org
> Usertags: wayland
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintain...@lists.alioth.debian.org;tag=wayland

Thanks Michael, I've done that for this bug.

Regards, Thibaut.




Re: Where to report Wayland-related bugs

2017-02-03 Thread Simon McVittie
On Fri, 03 Feb 2017 at 12:35:07 +0100, Emilio Pozuelo Monfort wrote:
> On 03/02/17 11:42, Thibaut Paumard wrote:
> > Is there a usertag defined for such issues?
> 
> There isn't (yet).

For functional failures triggered by using the Wayland-enabled GNOME Shell,
I started using pkg-gnome-maintain...@lists.alioth.debian.org usertag
"wayland"[1] a while ago, and GNOME upstream has
.

S

[1] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintain...@lists.alioth.debian.org;tag=wayland



Bug#854067: ITP : node-prepend-http -- Prepend `http://` to humanized URLs like todomvc.com and localhost

2017-02-03 Thread Shirish Togarla
Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-prepend-http
  Version : 1.0.4
  Upstream Author : Sindre Sorhus  (sindresorhus.com
)
* URL : https://github.com/sindresorhus/prepend-http#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Prepend `http://` to humanized URLs like todomvc.com
and localhost


Re: github and its workflows (was Re: manpages.debian.org has been modernized!)

2017-02-03 Thread Wouter Verhelst
On Mon, Jan 30, 2017 at 09:51:51AM -0700, Sean Whitton wrote:
> Firstly, it is not clear to me how the barrier to getting involved with
> more substantial bugs is affected by the fact that I can trivially
> submit typo fixes.  What did you have in mind?

How big was your first ever contribution to Free Software?

What did that do for your state of mind?

Would it have happened earlier if your first ever contribution was
easier to make?

If the answer to these questions is "small", "improved it", and "yes",
then you see why GitHub making small changes trivial to make is a good
thing.

> Secondly, I suspect that the feeling of being accepted might be
> illusory.  Submitting typo fixes that don't require any review does not
> help build any relationships.

True, but that's not necessarily required.

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
   people in the world who think they really understand all of its rules,
   and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12