Hi Don!
>
>The package has a team, but since it looks like it's been maintained by
>NMU for quite some time, I see no reason why you could "join the team",
>and then basically take over the maintenance of this package.
in more than one year, nobody managed to accept me and Alec.
(we both tried to
On Tue, Sep 13, 2016 at 04:11:21PM -0700, Don Armstrong wrote:
> bugs.debian.org controls whether pseudopackage exist at all; reportbug
> is responsible for what reportbug outputs as possible pseudopackages.
I'm well aware of that…
> That's true. There are some bugs which affect lots of packages
Hi Holger,
On Tue, 2016-09-13 at 17:08 +, Holger Levsen wrote:
> On Tue, Sep 13, 2016 at 04:15:54PM +0200, Abou Al Montacir wrote:
> > Control: reopen -1
> > > > Sorry, I don't think that the best way to solve this issue is to close
> > > > the
bug.
>
> it seems you haven't realized two thin
On Tue, 2016-09-13 at 14:27 -0700, Russ Allbery wrote:
> > Holger Levsen writes:
>
> > it seems you haven't realized two things:
> > - the "general" pseudo package is mostly useless
> > - when Ben closed this bug he gave a pointer to another bug which
> > basically is the same issue *and* a muc
On Tue, 2016-09-13 at 15:51 -0700, Josh Triplett wrote:
> Russ Allbery wrote:
> > Should we just disable the general pseudo-package? Is it serving a
> > sufficient useful purpose to warrant the constant (if somewhat slow)
> > stream of misdirected bug reports?
>
> I don't think so, no. Seems bet
I'm quite disappointed that instead of trying to fix the bug you are just trying
to discuss how to make user life more complicated.
What is the difference between Debian and any commercial SW? Just that it
becomes less user friendly with less support despite it is cost free.
--
Cheers,
Abou Al Mon
On Wed, Sep 14, 2016 at 12:56:52AM +0200, Matthias Klose wrote:
> sorry, I don't share you view that this might be funny. You are known to make
> issues RC issues like the missing build-indep/build-arch targets. I think the
> RC severity of such reports is at least questionable.
No, that's not
On Wed, Sep 14, 2016 at 11:34:26AM +0200, Abou Al Montacir wrote:
> I'm quite disappointed that instead of trying to fix the bug you are just
> trying
> to discuss how to make user life more complicated.
how about you take care about those 32 bugs against
https://bugs.debian.org/cgi-bin/pkgreport
On Wed, Sep 14, 2016 at 4:58 PM, Gianfranco Costamagna wrote:
> in more than one year, nobody managed to accept me and Alec.
> (we both tried to join loong time ago)
Did you try these?
Contacting the team via other methods (IRC/Twitter/Facebook/etc?).
Asking the alioth admins to add you.
--
b
On Wed, Sep 14, 2016 at 11:56:33AM +0200, Abou Al Montacir wrote:
> I'll have a look. I don't promise I can help as I don't know if I have the
> skill
> for all of them but it is worth the trial.
very cool, thanks!
--
cheers,
Holger
signature.asc
Description: Digital signature
On Wed, 2016-09-14 at 11:44 +0200, Holger Levsen wrote:
> On Wed, Sep 14, 2016 at 11:34:26AM +0200, Abou Al Montacir wrote:
> > > > I'm quite disappointed that instead of trying to fix the bug you are
> > > > just
trying
> > to discuss how to make user life more complicated.
>
> how about you tak
On Wed, Sep 14, 2016 at 11:23:56AM +0200, Abou Al Montacir wrote:
> Because you think people will not be frustrated if they experience a bug and
> that we prevent them to raise bugs? Hiding reality is always bad?. Look at the
> original reporter last message. He seems quite disappointed by the proj
Hi Paul,
>Did you try these?
>
>Contacting the team via other methods (IRC/Twitter/Facebook/etc?).
>
>Asking the alioth admins to add you.
actually the team was dead, nobody was active anymore (probably all the admin
aren't not
DD anymore).
The only member active was Stefan, that has been made a
On Tue, Sep 13, 2016 at 07:38:37PM +0200, Markus Koschany wrote:
>
> What I find disturbing is that we really think that shaming the
> maintainer would be a better approach.
I also consider the time of all involved persons (bug reporter,
maintainer, posters and readers on this list) well better s
On Sep 14, Gianfranco Costamagna wrote:
> I got a (back to january), a nice review with an "ETOOBUSY, come back on
> june" or whatever
> and now it is september and freeze is approaching...
> I would like to avoid a new stable with the old libirman/lirc
Please just hijack the package.
--
ciao,
On 14/09/16 10:58, Gianfranco Costamagna wrote:
I can sponsor it, but I would like to see some positive feedbacks before doing
it :)
Part of this is the upstream, debian packaging which (besides changelog)
is identical to the package in mentors. There has been several hundred
downloads of
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: libjs-objectpath
Version : 1.2.1
Upstream Author : Mike Marcacci
* URL : https://github.com/mike-marcacci/objectpath
* License : Expat
Programming Lang: JavaScript
Description : par
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-xstatic-objectpath
Version : 1.2.1.0
Upstream Author : Rob Cresswell
* URL : https://github.com/robcresswell/xstatic-objectpath
* License : Expat
Programming Lang: Python, JavaScri
On Wed, Sep 14, 2016 at 01:00:46PM +0200, Andreas Tille wrote:
>a) more friendly
Please check the facts. The "initial email" which started this
discussion was not really the one in -devel but this one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837614#19
I think that's friendly enough
Hi,
TL;DR:
What to do when a project with a dead upstream is "forked" and
development continues under the same name
Long story:
gnarwl, a GPLv2 LDAP-based email autoresponder developed by Patrick
Ahlbrecht, has recently been orphaned in Debian. Since a legacy mail
system of my employer still uses
Hi
reproducing the critical parts in a unit test would be helpful
Something like in the attachment.
install dependencies:
apt-get install libcunit1-dev
Compile with
gcc -g -o mutex_fail_test mutex_fail_test.c `pkg-config --cflags
--libs cunit` -pthread
launch
./mutex_fail_test
Bests,
Joël
Hello,
On Wed, Sep 14, 2016 at 01:30:18PM +, Bernhard Schmidt wrote:
> How would you generally deal with a situation like this?
>
> * switch homepage to github, convince github owner to tag new upstream
> release and update package to new release
> + properly documented where develo
On 2016-09-14, Joël Krähemann wrote:
> reproducing the critical parts in a unit test would be helpful
>
> Something like in the attachment.
>
> install dependencies:
>
> apt-get install libcunit1-dev
>
> Compile with
>
> gcc -g -o mutex_fail_test mutex_fail_test.c `pkg-config --cflags
> --lib
>Part of this is the upstream, debian packaging which (besides changelog) is
>identical to the package in mentors. There has been several hundred downloads
>of this packaging without any packaging-related bugs reported.
I can also add that a colleague is happily using the new lirc on mentors on
On Tue, 13 Sep 2016 22:36:58 +0200, Ansgar Burchardt wrote:
> Hi,
>
> debootstrap in unstable can now install with merged-/usr, that is with
> /bin, /sbin, /lib* being symlinks to their counterpart in /usr. Run
>
> debootstrap --merged-usr testing .../testing
> http://deb.debian.org/debian
Ansgar Burchardt wrote:
> debootstrap in unstable can now install with merged-/usr, that is
> with
> /bin, /sbin, /lib* being symlinks to their counterpart in /usr. Run
>
> debootstrap --merged-usr testing .../testing http://deb.debian.org/
> debian
>
> to give it a try.
As I was just asked o
On Wed, Sep 14, 2016 at 02:38:09PM +, Felipe Sateler wrote:
> On Tue, 13 Sep 2016 22:36:58 +0200, Ansgar Burchardt wrote:
>
> > Hi,
> >
> > debootstrap in unstable can now install with merged-/usr, that is with
> > /bin, /sbin, /lib* being symlinks to their counterpart in /usr. Run
> >
> >
On Wed, Sep 14, 2016 at 01:30:18PM +, Bernhard Schmidt wrote:
> What to do when a project with a dead upstream is "forked" and
> development continues under the same name
> Patrick very quickly replied and declined with (IMHO very reasonable)
[...]
> arguments
>
> * people still associate g
Am 14.09.2016 um 16:50 schrieb Pierre Chifflier:
> Except that breaks having different mount points, which is useful to
> enforce different mount options (my /usr is nodev,ro).
> Does this mean this cannot be supported anymore ? It would be a step
> backward, security-speaking, if split /usr does n
On Tue, 13 Sep 2016 15:24:49 -0700, Don Armstrong wrote:
> On Tue, 13 Sep 2016, Russ Allbery wrote:
> > Should we just disable the general pseudo-package? Is it serving a
> > sufficient useful purpose to warrant the constant (if somewhat slow)
> > stream of misdirected bug reports?
> I personally
On Wed, Sep 14, 2016 at 06:23:48PM +0200, gregor herrmann wrote:
> Sorry if this has been brought up already. Another option would be to
> change the mapping of package:general from debian-devel@ldo to
> debian-user@ldo. I guess this has a similar effect (getting help in
> triaging the problem) wit
Package: wnpp
Severity: wishlist
Owner: Marco Nenciarini
* Package name: barman-cli
Version : 1.1
Upstream Author : 2ndQuadrant Italy Srl
* URL : http://www.pgbarman.org/
* License : GPL3
Programming Lang: Python
Description : Client Utilities for Barm
[Please do not CC me, I am subscribed. You seem to have a habit of
CC'ing the individuals to whose messages you are responding. This is
contrary to this list's documented policy.]
* Abou Al Montacir [160914 05:31]:
> The duty of the project is to
> help him investigating the right way so that t
Abou Al Montacir writes:
> Because you think people will not be frustrated if they experience a bug
> and that we prevent them to raise bugs? Hiding reality is always
> bad?. Look at the original reporter last message. He seems quite
> disappointed by the project reaction. He should feel as we do
Abou Al Montacir writes:
> We are here facing a bug that appears only on some devices. The issue is
> tricky and the user does not have the skills to debug. The duty of the
> project is to help him investigating the right way so that the bug get
> solved.
No, it's not.
I hate to be this blunt a
On Sep 14, Ansgar Burchardt wrote:
> One can also test installations using d-i. The images from [1] already
Just to be clear: merged-/usr can be tested on an existing system by
installing the usrmerge package.
--
ciao,
Marco
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: IOhannes m zmölnig (Debian/GNU)
* Package name: python-can
Version : 1.5.2
Upstream Author : Brian Thorne
* URL : https://bitbucket.org/hardbyte/python-can
* License : LGPL v3
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: IOhannes m zmölnig (Debian/GNU)
* Package name: python-canmatrix
Version : 0.4
Upstream Author : Eduard Broecker
* URL : http://github.com/ebroecker/canmatrix
* License : BSD
Programming Lang: Python
Description
Control: retitle -1 ITP: python-can -- Controller Area Network interface module
for Python
Thanks.
Ooops, seems like i forgot the subject in this ITP
On Wed, Sep 14, 2016 at 08:09:05PM +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
>
> This is an a
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org
* Package name: libapp-ledgersmb-admin-perl
Version: 0.05
Upstream Author : Chris Travers
* URL or Web page : https://metacpan.org/pod/App::LedgerSMB::Admin
* License
On Wed, 2016-09-14 at 11:21 +0200, Abou Al Montacir wrote:
> Hi Holger,
>
> On Tue, 2016-09-13 at 17:08 +, Holger Levsen wrote:
> >
> > On Tue, Sep 13, 2016 at 04:15:54PM +0200, Abou Al Montacir wrote:
> > >
> > > Control: reopen -1
> > > >
> > > > >
> > > > > Sorry, I don't think that the
On Wed, Sep 14, 2016 at 05:08:18PM +0200, Michael Biebl wrote:
> Am 14.09.2016 um 16:50 schrieb Pierre Chifflier:
> > Except that breaks having different mount points, which is useful to
> > enforce different mount options (my /usr is nodev,ro).
> > Does this mean this cannot be supported anymore ?
On Wed, Sep 14, 2016 at 01:15:47PM +0300, Lars Wirzenius wrote:
> On Wed, Sep 14, 2016 at 11:23:56AM +0200, Abou Al Montacir wrote:
> > Because you think people will not be frustrated if they experience a bug and
> > that we prevent them to raise bugs? Hiding reality is always bad?. Look at
> > th
43 matches
Mail list logo
