]] Dmitrijs Ledkovs
> loggerhead is replacement for gitweb
As one of the alioth admins, I'd like to contest this statement.
loggerhead is a replacement for gitweb in the same way that crawling is
a replacement for sprinting.
Yes, we «run» it, but it's memory-hungry, slow and crash-prone. It a
On Wed, Oct 17, 2012 at 10:16:35PM +, Jeremy Stanley wrote:
> The section to which you seem to be referring is relevant
> specifically to "image and icon files in Launchpad." If you replace
> those with your own artwork or some other released under a
> compatible license and respect any other r
On Wed, 17 Oct 2012 07:53:01 + (UTC), Sune Vuorela
wrote:
>On 2012-10-17, Svante Signell wrote:
>> Even some bugs _with_ patches are treated the same way or kept open and
>> never acted on. Shouldn't the number of open bugs be decreasing with
>> time, not being constant or increasing as is th
On Thu, Oct 18, 2012 at 10:37 AM, Russell Coker wrote:
> For a warning it doesn't matter much if we have a few false-positives. For
> the error conditions that I suggest for /build and $HOME I find it difficult
> to
> imagine false-positives except the case where a DD uses their own home
> direc
On Thu, 18 Oct 2012, Paul Wise wrote:
> On Thu, Oct 18, 2012 at 10:20 AM, Russell Coker wrote:
> > We could have a lintian warning for any occurance of the string "/home"
> > in a packaged file and have error conditions for "/build" and the
> > current value of $HOME for the account running lintia
On Thu, Oct 18, 2012 at 10:20 AM, Russell Coker wrote:
> We could have a lintian warning for any occurance of the string "/home" in a
> packaged file and have error conditions for "/build" and the current value of
> $HOME for the account running lintian.
Based on a quick grep of /usr/bin on my la
On Wed, Oct 17, 2012 at 1:57 PM, Michael Gilbert wrote:
> On Tue, Oct 16, 2012 at 6:49 PM, Matthew Grant wrote:
> > Can Bug #690569 (DNS wildcards fail to resolve with DNSsec enabled -
> breaks
> > RFC 4035)be reclassified as grave, or at least Important severity?
>
You implied a bug severity inc
On Thu, 18 Oct 2012, Michael Gilbert wrote:
> Maybe someone would be interested in writing a lintian check for these
> issues? Something a bit more advanced than this
>
> $ strings /sbin/dhclient | grep ^PATH
> PATH=/home/zero79/source/git/isc-dhcp/debian/tmp/usr/sbin:/sbin:/bin:/usr/s
> bin:/us
Package: wnpp
Severity: wishlist
Owner: "David Martínez Moreno"
* Package name: redmine-plugin-recaptcha
Version : 0.1.0
Upstream Author : Shane StClair
* URL : https://github.com/srstclair/redmine_recaptcha
* License : MIT
Programming Lang: Ruby
Descripti
On Wed, Oct 17, 2012 at 11:48:17PM +0200, Matthias Klose wrote:
> On 17.10.2012 21:49, Steve Langasek wrote:
> > On Wed, Oct 17, 2012 at 11:30:38AM -0700, Christoph Egger wrote:
> >> Joerg Jaspert writes:
> >>> Its for after wheezy, definitely. Also, there are some open issues to
> >>> be solved f
On 17 October 2012 09:57, Игорь Пашев wrote:
> For git we have gitweb, gitolite, git-daemon, pristine-tar.
> I'd like to have similar for bzr, hg and svn.
>
bzr-builddeb gives pristine-tar support
bzr serve is the equivalent of git-daemon and it is builtin
loggerhead is replacement for gitweb
On 17 October 2012 22:55, Philipp Kern wrote:
> Paul,
>
> am Wed, Oct 17, 2012 at 05:48:39PM -0400 hast du folgendes geschrieben:
>> > With the danger of being sued if you put up the result onto the public
>> > interwebs.
>> Could you please expand on that? Logo / trademark reasons or license
>> i
On 2012-10-17 23:55:08 +0200 (+0200), Philipp Kern wrote:
> am Wed, Oct 17, 2012 at 05:48:39PM -0400 hast du folgendes geschrieben:
> > > With the danger of being sued if you put up the result onto the public
> > > interwebs.
> >
> > Could you please expand on that? Logo / trademark reasons or li
Paul,
am Wed, Oct 17, 2012 at 05:48:39PM -0400 hast du folgendes geschrieben:
> > With the danger of being sued if you put up the result onto the public
> > interwebs.
> Could you please expand on that? Logo / trademark reasons or license
> issues?
it's not very hard to find https://dev.launchpa
On 17.10.2012 21:49, Steve Langasek wrote:
> On Wed, Oct 17, 2012 at 11:30:38AM -0700, Christoph Egger wrote:
>> Joerg Jaspert writes:
>>> Its for after wheezy, definitely. Also, there are some open issues to
>>> be solved for this to happen. The most important is being able to deal
>>> with arch
On Wed, Oct 17, 2012 at 11:43:36PM +0200, Philipp Kern wrote:
> On Wed, Oct 17, 2012 at 11:19:01AM +0200, Daniel Holbach wrote:
> > On 17.10.2012 11:13, Игорь Пашев wrote:
> > > 2012/10/17 Hideki Yamane :
> > >> No, LP is good website for development with collaboration.
> > > Can I have my own LP,
On Wed, Oct 17, 2012 at 11:19:01AM +0200, Daniel Holbach wrote:
> On 17.10.2012 11:13, Игорь Пашев wrote:
> > 2012/10/17 Hideki Yamane :
> >> No, LP is good website for development with collaboration.
> > Can I have my own LP, please?
> https://dev.launchpad.net/Running should help you with that.
On Wed, Oct 17, 2012 at 08:56:56AM +0200, Joerg Jaspert wrote:
> Its for after wheezy, definitely.
> Also, there are some open issues to be solved for this to happen.
> The most important is being able to deal with arch all packages. And
> worse - arch all packages able to build only on certain arc
On Wed, Oct 17, 2012 at 05:23:22PM -0400, Michael Gilbert wrote:
> if there is a build path sanitization issue, then if the
> user chooses to rebuild the package they will get their own rogue
> paths. So, yes, we should always fix those issues when they're found,
> but at least for people using bu
On Wed, Oct 17, 2012 at 5:23 PM, Michael Gilbert wrote:
> That is true: if there is a build path sanitization issue, then if the
> user chooses to rebuild the package they will get their own rogue
> paths. So, yes, we should always fix those issues when they're found,
> but at least for people usi
On Wed, Oct 17, 2012 at 4:55 PM, Bernhard R. Link wrote:
> * Michael Gilbert [121017 22:19]:
>> Anyway, reading again, I not sure that your reply actually considers
>> build path sanitization problems, which is what my statement was
>> about.
>
> I'm stating that doing all the builds on buildds wi
* Michael Gilbert [121017 22:19]:
> Anyway, reading again, I not sure that your reply actually considers
> build path sanitization problems, which is what my statement was
> about.
I'm stating that doing all the builds on buildds will not avoid the
need to fix the package. (Unless you are arguing
On Wed, Oct 17, 2012 at 4:07 PM, Bernhard R. Link wrote:
> * Michael Gilbert [121016 04:59]:
>> Anyway, all of these build system path sanitization issues can be
>> eliminated by using the buildds for all architectures, since paths
>> will start with at least /build that requires root-level actio
Paul Tagliamonte writes:
> On Wed, Oct 17, 2012 at 11:30:38AM -0700, Christoph Egger wrote:
>> Joerg Jaspert writes:
>> > Its for after wheezy, definitely.
>> > Also, there are some open issues to be solved for this to happen.
>> > The most important is being able to deal with arch all packages.
* Michael Gilbert [121016 04:59]:
> Anyway, all of these build system path sanitization issues can be
> eliminated by using the buildds for all architectures, since paths
> will start with at least /build that requires root-level action to
> exist on users' systems.
They are not eliminated by usi
On Wed, Oct 17, 2012 at 09:51:48PM +0200, Stefano Zacchiroli wrote:
> (Andreas Barth, Bill Allombert, and Russ Allombert have confirmed their
> interest in working as editors and remain on board.)
Erm, overzealous M-/ in my favorite editor :-) So let's thank here
Andreas Barth, Bill Allombert, and
On Wed, Oct 17, 2012 at 11:30:38AM -0700, Christoph Egger wrote:
> Hi!
>
> Joerg Jaspert writes:
> > Its for after wheezy, definitely.
> > Also, there are some open issues to be solved for this to happen.
> > The most important is being able to deal with arch all packages. And
> > worse - arch al
On 17 October 2012 19:30, Christoph Egger wrote:
> Hi!
>
> Joerg Jaspert writes:
>> Its for after wheezy, definitely.
>> Also, there are some open issues to be solved for this to happen.
>> The most important is being able to deal with arch all packages. And
>> worse - arch all packages able to b
On Wed, Oct 17, 2012 at 11:30:38AM -0700, Christoph Egger wrote:
> Joerg Jaspert writes:
> > Its for after wheezy, definitely.
> > Also, there are some open issues to be solved for this to happen.
> > The most important is being able to deal with arch all packages. And
> > worse - arch all package
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko
* Package name: pymc
Version : 2.2
Upstream Author : PyMC Team
* URL : http://pymc-devs.github.com/pymc
* License : MIT/X
Programming Lang: Python
Description : Bayesian statistical models and f
Hi!
Joerg Jaspert writes:
> Its for after wheezy, definitely.
> Also, there are some open issues to be solved for this to happen.
> The most important is being able to deal with arch all packages. And
> worse - arch all packages able to build only on certain architectures.
> But thats outside dak
On Wednesday, October 17, 2012 12:45:14, Wouter Verhelst wrote:
> On Wed, Oct 17, 2012 at 12:28:14PM -0400, Chris Knadle wrote:
> > On Tuesday, October 16, 2012 05:04:55, martin f krafft wrote:
> > > also sprach Holger Levsen [2012.10.16.0945
+0200]:
> > > > > We have not cared enough for almost
On Wed, Oct 17, 2012 at 12:28:14PM -0400, Chris Knadle wrote:
> On Tuesday, October 16, 2012 05:04:55, martin f krafft wrote:
> > also sprach Holger Levsen [2012.10.16.0945 +0200]:
> > > > We have not cared enough for almost 20 years that 9 out of 10 binary
> > > > packages in use (i386 until 2005
On Wed, 17 Oct 2012 12:28:14 -0400
Chris Knadle wrote:
> Out of curiosity, how would a user /know/ whether a package has been built
> via
> a buildd rather than on a DD's local machine?
Check the wannabuild logs for the package. A listing of Installed
without a build log means that the binari
On Tuesday, October 16, 2012 05:04:55, martin f krafft wrote:
> also sprach Holger Levsen [2012.10.16.0945 +0200]:
> > > We have not cared enough for almost 20 years that 9 out of 10 binary
> > > packages in use (i386 until 2005, amd64 since then) are built on
> > > machines that are individually
On Mon, Oct 15, 2012 at 03:25:21AM +0200, Christoph Anton Mitterer wrote:
> On Sat, 2012-10-13 at 20:35 +0200, Wouter Verhelst wrote:
[...]
> > If anything, Ubuntu is
> > gaining ground on non-free software. You can't be angry about that.
> That's a tricky question... ask yourself what RMS would pr
Package: wnpp
Severity: wishlist
Owner: "David Martínez Moreno"
* Package name: ruby-recaptcha
Version : 0.3.2
Upstream Author : Jason L Perry,
* URL : http://ambethia.com/recaptcha/
* License :
Copyright (c) 2007 Jason L Perry
Permission is hereby granted,
On Wed, 17 Oct 2012 13:13:42 +0400
Игорь Пашев wrote:
> Can I have my own LP, please?
Well, you can get source code. see https://dev.launchpad.net/Trunk
# I just annoyed heavily relying on LP as my previous mails in thread.
However, it looks good for me.
--
Regards,
Hideki Yamane h
Hello,
On 17.10.2012 11:13, Игорь Пашев wrote:
> 2012/10/17 Hideki Yamane :
>> No, LP is good website for development with collaboration.
>
> Can I have my own LP, please?
https://dev.launchpad.net/Running should help you with that.
Have a great day,
Daniel
--
To UNSUBSCRIBE, email to debia
2012/10/17 Hideki Yamane :
> No, LP is good website for development with collaboration.
Can I have my own LP, please?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org
On Wed, 17 Oct 2012 12:57:18 +0400
Игорь Пашев wrote:
> For git we have gitweb, gitolite, git-daemon, pristine-tar.
> I'd like to have similar for bzr, hg and svn.
>
> It's not about technology, but about collaboration.
No, LP is good website for development with collaboration.
(A workflow is
For git we have gitweb, gitolite, git-daemon, pristine-tar.
I'd like to have similar for bzr, hg and svn.
It's not about technology, but about collaboration.
That's why I prefer git.
2012/10/17 Marc Haber :
> On Thu, 11 Oct 2012 16:31:00 -0700, Steve Langasek
> wrote:
>>The popularity of subver
On 2012-10-17, Svante Signell wrote:
> Even some bugs _with_ patches are treated the same way or kept open and
> never acted on. Shouldn't the number of open bugs be decreasing with
> time, not being constant or increasing as is the case for some packages?
in many cases, the amount of open bug re
On Wed, 2012-10-17 at 08:58 +0200, Marc Haber wrote:
> On Thu, 11 Oct 2012 02:46:18 +0200, Christoph Anton Mitterer
> wrote:
> >First declining bug numbers are not necessarily a problem, because it
> >could just mean that we're getting better and better, or that more and
> >more upstream issues ar
Dear manager:
Nice time!
Very happy to hear that you need A4 paper
We have 80g, 70g and so on
If you still need that pls reply me let us contact detail
Pls reply me
Best wishes,
Mr.Li (Manager)
HANGZHOU XINHAO INDUSTRY CO., LIMITED
ADD: NO.124 JINCHENG ROAD, XINDENG TOWN, FUYANG CITY,HANGZHOU,
On Thu, 11 Oct 2012 02:46:18 +0200, Christoph Anton Mitterer
wrote:
>First declining bug numbers are not necessarily a problem, because it
>could just mean that we're getting better and better, or that more and
>more upstream issues are reported upstream (which would be a good thing
>IMHO), or tha
On Thu, 11 Oct 2012 16:31:00 -0700, Steve Langasek
wrote:
>The popularity of subversion
>for packaging is a measure of inertia and/or ignorance, not of the
>appropriateness of the tool.
I find this attitute improperly offensive. The choice of tool is the
decision of the maintainer, and subversion
47 matches
Mail list logo
