On Sat, Mar 28, 2015 at 7:48 AM, Hideki Yamane wrote:
> How about check and warn it with watch and lintian?
>
> e.g. https://qa.debian.org/cgi-bin/watch?pkg=mecab was hosted in Google Code,
> and if so, warn "hosted site will be closed (January 25th, 2016)" with
> Packages overview and lintian
> Paul Wise wrote:
> > Will be on d-d-a when the next DevNews is posted:
> >
> > https://wiki.debian.org/DeveloperNews#Google_Code_closing
>
> How about check and warn it with watch and lintian?
>
> e.g. https://qa.debian.org/cgi-bin/watch?pkg=mecab was hosted in Google Code,
> and if so, wa
On Fri, 13 Mar 2015 11:05:47 +0800
Paul Wise wrote:
> Will be on d-d-a when the next DevNews is posted:
>
> https://wiki.debian.org/DeveloperNews#Google_Code_closing
How about check and warn it with watch and lintian?
e.g. https://qa.debian.org/cgi-bin/watch?pkg=mecab was hosted in Google Cod
On Tue, Mar 10, 2015 at 07:51:35PM -0700, Russ Allbery wrote:
> Launchpad exists as code for self-hosting.
>
> https://dev.launchpad.net/Getting
>
> Setting it up is a little like trying to set up dak yourself: it's
> possible, and people have done it, but it's not common, so it's not
> painl
On Fri, Mar 13, 2015 at 9:06 AM, Bernd Zeimetz wrote:
> And google code:
>
> http://google-opensource.blogspot.fr/2015/03/farewell-to-google-code.html
I should have waited a few more days :(
Will be on d-d-a when the next DevNews is posted:
https://wiki.debian.org/DeveloperNews#Google_Code_clos
On 10.03.2015 04:54, Paul Wise wrote:
Gitorious and Codehaus closing
--
And google code:
http://google-opensource.blogspot.fr/2015/03/farewell-to-google-code.html
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.de
Quoting Russ Allbery (2015-03-11 03:51:35)
> Jonas Smedegaard writes:
>
>> I don't know all those services, but would be surprised if e.g.
>> launchpad exists as code for self-hosting. Don't get me wrong: I
>> would be _happy_ to stand corrected!
>
> Launchpad exists as code for self-hosting.
>
Jonas Smedegaard writes:
> I don't know all those services, but would be surprised if e.g.
> launchpad exists as code for self-hosting. Don't get me wrong: I would
> be _happy_ to stand corrected!
Launchpad exists as code for self-hosting.
https://dev.launchpad.net/Getting
Setting it up i
On Tue, Mar 10, 2015 at 10:28 PM, Jonathan Dowland wrote:
> On Tue, Mar 10, 2015 at 06:51:21PM +0800, Paul Wise wrote:
>> git tags not pushed to all remotes:
>
> Currently vcs-lint does this for origin only but I agree a check for all
> remotes would be useful,
Great :)
>> git commit/tag signing
Quoting Johannes Schauer (2015-03-10 14:43:22)
> Quoting Paul Wise (2015-03-10 11:53:35)
>> There are many options that could be used, for example fusionforge,
>> kallithea, gitolite, girocco, allura, launchpad, redmine etc.
>
> since I'm also affected by the closing of gitorious, I thought this
On Tue, Mar 10, 2015 at 06:51:21PM +0800, Paul Wise wrote:
> I have the following VCS related items on the TODO list for c-a-a-t,
> if you would like to add those to vcs-lint get it into Debian, I would
> be very glad to add a check for it to c-a-a-t.
Cool, I need to look at these more thoroughly,
On Tue, Mar 10, 2015 at 10:07:38PM +0800, Paul Wise wrote:
> On Tue, Mar 10, 2015 at 8:37 PM, Dominique Dumont wrote:
>
> > I've also worked on a way to improve licensecheck2dep5 (without knowing
> > about
> > license-reconcile).
>
> It might be interesting to consolidate these three tools or ch
On Tue, Mar 10, 2015 at 8:37 PM, Dominique Dumont wrote:
> I've also worked on a way to improve licensecheck2dep5 (without knowing about
> license-reconcile).
It might be interesting to consolidate these three tools or choose the
best one and delete the others.
--
bye,
pabs
https://wiki.debian
On Tue, Mar 10, 2015 at 06:53:35PM +0800, Paul Wise wrote:
> On Tue, 2015-03-10 at 11:54 +0800, Paul Wise wrote:
>
> > Gitorious and Codehaus closing
> > --
>
> I forgot to mention that it would be a good idea to discuss using free
> repository hosting tools with your
Hi,
Quoting Paul Wise (2015-03-10 11:53:35)
> There are many options that could be used, for example fusionforge,
> kallithea, gitolite, girocco, allura, launchpad, redmine etc.
since I'm also affected by the closing of gitorious, I thought this would be
the best time to move all my code to a DFS
On Tuesday 10 March 2015 11:25:22 Jonas Smedegaard wrote:
> license-reconcile began, I believe, as a fork of licensecheck2dep5.. I
> have not yet figured out how to actually use license-reconcile - it may
> be far superior on all fronts, you'll have to consult its author about
> that.
I've als
On Tue, 2015-03-10 at 11:54 +0800, Paul Wise wrote:
> Gitorious and Codehaus closing
> --
I forgot to mention that it would be a good idea to discuss using free
repository hosting tools with your upstream developers and link to this:
http://mako.cc/writing/hill-free_t
On Tue, Mar 10, 2015 at 6:25 PM, Jonathan Dowland wrote:
> Sounds cool. It could wrap vcs-lintı, not yet in Debian: I filed a bug
> to add it to devscripts 3 years ago², which has not yet had a response,
> but the tool has languished largely since then. I've recently started to
> give it some more
On Tue, Mar 10, 2015 at 6:25 PM, Jonas Smedegaard wrote:
> Quoting Paul Wise (2015-03-10 10:50:08)
>> On Tue, 2015-03-10 at 08:53 +0100, Axel Beckert wrote:
>>> I'm missing license-reconcile here which checks licensecheck's output
>>> against debian/copyright (and seems to can do some more stuff).
On Tue, Mar 10, 2015 at 11:54:52AM +0800, Paul Wise wrote:
> If you know of a tool in Debian it could wrap, please commit a
> checker, send a patch or a link. If you know of a tool not yet in Debian
> it could wrap, please package the tool and or send a link. You can ask
> questions about it on
Quoting Paul Wise (2015-03-10 10:50:08)
> On Tue, 2015-03-10 at 08:53 +0100, Axel Beckert wrote:
>> I'm missing license-reconcile here which checks licensecheck's output
>> against debian/copyright (and seems to can do some more stuff).
>
> There is licensecheck2dep5 in cdbs but I doubt that is a
On Tue, 2015-03-10 at 08:53 +0100, Axel Beckert wrote:
> Codehaus already has a horribly slow main page... Never really heard
> of them before, though. (I'm always thinking of Spamhaus when reading
> its name. :-)
Searching my mailing list archives, Java projects seem to like them.
> Sounds like
Hi Paul,
me again. ;-)
Paul Wise wrote:
> Gitorious and Codehaus closing
> --
>
> Both and Gitorious and Codehaus are closing soon. Gitorious will[1] shut
> down at the end of May and Codehaus will[2] be removing projects from
> April 2nd onwards (most around May 1
On 2010-08-28 20:54:42 +1000, Brian May wrote:
> When the solution is easy I don't see why we don't just do it.
>
> br...@andean:~$ i="cat's meow.tar.gz"
> br...@andean:~$ echo "`basename "$i" .tar.gz`"
> cat's meow
>
> (yes, the nested quotes don't seem to matter)
They matter if you have consec
On 27 August 2010 18:20, Adam Borowski wrote:
> On Fri, Aug 27, 2010 at 10:09:49AM +0200, posion bit wrote:
>> > (/etc/mc/mc.menu)
>> > case "$i" in
>> > *.tar.gz) D="`basename $i .tar.gz`";;
>>
>> In that case, name-spaced filenames should work, because the
>> string is
On Fri, Aug 27, 2010 at 05:23:13PM -0700, Russ Allbery wrote:
> Adam Borowski writes:
> > On Fri, Aug 27, 2010 at 11:08:11AM -0700, Russ Allbery wrote:
>
> >> Could you please either start reporting (wishlist) bugs asking to make
> >> these scripts more robust against strange administrative pract
Adam Borowski writes:
> On Fri, Aug 27, 2010 at 11:08:11AM -0700, Russ Allbery wrote:
>> Could you please either start reporting (wishlist) bugs asking to make
>> these scripts more robust against strange administrative practices or
>> get tired of all this a little bit faster?
> While being rob
On Fri, Aug 27, 2010 at 11:08:11AM -0700, Russ Allbery wrote:
> Could you please either start reporting (wishlist) bugs asking to make
> these scripts more robust against strange administrative practices or get
> tired of all this a little bit faster?
While being robust against "/etc/rcS.d/S50foo
Russ Allbery wrote:
> Could you please either start reporting (wishlist) bugs asking to make
> these scripts more robust against strange administrative practices or get
> tired of all this a little bit faster? A large thread in debian-devel
> with no concrete actionable reports is basically useles
On Fri, Aug 27, 2010 at 10:36:52AM +0200, posion bit wrote:
> On Fri, Aug 27, 2010 at 10:26 AM, Steve Langasek wrote:
> > Given that he hasn't bothered to present a single definitively broken script
> > in /etc but instead seems to think that his prowess with grep entitles him
> > to leave this mo
On Fri, Aug 27, 2010 at 8:08 PM, Russ Allbery wrote:
> Could you please either start reporting (wishlist) bugs asking to make
> these scripts more robust against strange administrative practices or get
> tired of all this a little bit faster? A large thread in debian-devel
> with no concrete acti
On Fri, Aug 27, 2010 at 6:59 PM, Christian PERRIER wrote:
> Quoting posion bit (poison...@gmail.com):
>
>> I'm not going to fill a lot of little bugs for this, I expect debian
>> scripts to be designed following some simple bash best practices.
>
> By what miracle do you expect this to happen (ass
posion bit writes:
> I showed one case in /etc/profile
> I've just fast looked and show another case in /etc/init.d/rc
> I'm getting tired of all this
Could you please either start reporting (wishlist) bugs asking to make
these scripts more robust against strange administrative practices or get
Quoting posion bit (poison...@gmail.com):
> I'm not going to fill a lot of little bugs for this, I expect debian
> scripts to be designed following some simple bash best practices.
By what miracle do you expect this to happen (assuming you have a
point somewhere) if you don't file bugs?
Do you e
On Fri, Aug 27, 2010 at 4:36 PM, Norbert Preining wrote:
> On Fr, 27 Aug 2010, posion bit wrote:
>> http://mywiki.wooledge.org/BashPitfalls
>
> Thanks, nice reading.
>
> Best wishes
I haven't write a line of that enlightened wiki :-)
Just sharing information sources with best wishes to all debi
On Fr, 27 Aug 2010, posion bit wrote:
> http://mywiki.wooledge.org/BashPitfalls
Thanks, nice reading.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan
On Fri, Aug 27, 2010 at 1:57 PM, Marco d'Itri wrote:
> On Aug 27, Samuel Thibault wrote:
>
>> Not if I have a "/etc/rc2.d/K03my damn daemon"
> True, but then you deserve all the pain you will receive.
Hi again, Marco and all.
I would love to invite to community to take a read to common
document
On Aug 27, Samuel Thibault wrote:
> Not if I have a "/etc/rc2.d/K03my damn daemon"
True, but then you deserve all the pain you will receive.
--
ciao,
Marco
signature.asc
Description: Digital signature
On 27.08.2010 12:29, posion bit wrote:
On Fri, Aug 27, 2010 at 12:13 PM, Josselin Mouette wrote:
Le vendredi 27 août 2010 à 11:57 +0200, Samuel Thibault a écrit :
Not if I have a "/etc/rc2.d/K03my damn daemon"
Which is again the debian rules and the LSB rules about
naming the init.d scripts.
On Fri, Aug 27, 2010 at 12:13 PM, Josselin Mouette wrote:
> Le vendredi 27 août 2010 à 11:57 +0200, Samuel Thibault a écrit :
>> > >Not if I have a "/etc/rc2.d/K03my damn daemon"
>> >
>> > Which is again the debian rules and the LSB rules about
>> > naming the init.d scripts.
>>
>> Debian rules an
Le vendredi 27 août 2010 à 11:57 +0200, Samuel Thibault a écrit :
> > >Not if I have a "/etc/rc2.d/K03my damn daemon"
> >
> > Which is again the debian rules and the LSB rules about
> > naming the init.d scripts.
>
> Debian rules and LSB won't prevent users (even root) from doing that.
And if ro
Giacomo A. Catenazzi, le Fri 27 Aug 2010 10:36:11 +0200, a écrit :
> On 27.08.2010 10:27, Samuel Thibault wrote:
> >Giacomo A. Catenazzi, le Fri 27 Aug 2010 10:21:06 +0200, a écrit :
> >>On 27.08.2010 10:09, posion bit wrote:
> >>>look one so simple in /etc/init.d/rc
> >>>
> >>>
On 27.08.2010 10:27, Samuel Thibault wrote:
Giacomo A. Catenazzi, le Fri 27 Aug 2010 10:21:06 +0200, a écrit :
On 27.08.2010 10:09, posion bit wrote:
look one so simple in /etc/init.d/rc
for i in /etc/rc$runlevel.d/K$level*
do
On 27.08.2010 10:34, posion bit wrote:
On Fri, Aug 27, 2010 at 10:27 AM, Samuel Thibault wrote:
Giacomo A. Catenazzi, le Fri 27 Aug 2010 10:21:06 +0200, a écrit :
On 27.08.2010 10:09, posion bit wrote:
look one so simple in /etc/init.d/rc
for i in /etc/rc$runlevel.d/
On Fri, Aug 27, 2010 at 09:58:22AM +0200, Adam Borowski wrote:
> On Fri, Aug 27, 2010 at 10:30:07AM +0400, Stanislav Maslovski wrote:
> > On Fri, Aug 27, 2010 at 12:22:08AM +0200, posion bit wrote:
> > > There are 38 unquoted $i in /etc in i386 installing base+laptop+standar
>
On Fri, Aug 27, 2010 at 10:26 AM, Steve Langasek wrote:
> Given that he hasn't bothered to present a single definitively broken script
> in /etc but instead seems to think that his prowess with grep entitles him
> to leave this most basic proof as an exercise for the reader, I'm pretty
> sure the
On Fri, Aug 27, 2010 at 10:27 AM, Samuel Thibault wrote:
> Giacomo A. Catenazzi, le Fri 27 Aug 2010 10:21:06 +0200, a écrit :
>> On 27.08.2010 10:09, posion bit wrote:
>> >look one so simple in /etc/init.d/rc
>> >
>> > for i in /etc/rc$runlevel.d/K$level*
>> >
Giacomo A. Catenazzi, le Fri 27 Aug 2010 10:21:06 +0200, a écrit :
> On 27.08.2010 10:09, posion bit wrote:
> >look one so simple in /etc/init.d/rc
> >
> > for i in /etc/rc$runlevel.d/K$level*
> > do
> > # Check if the
On Fri, Aug 27, 2010 at 09:58:22AM +0200, Adam Borowski wrote:
> While many of these are false alarms (numbers, fixed names, ...), the
> problem is real. Sometimes you even have a proper and improper usage on the
> same or on subsequent lines:
> (/etc/mc/mc.menu)
> case "$i" in
>
On 27.08.2010 10:09, posion bit wrote:
On Fri, Aug 27, 2010 at 9:58 AM, Adam Borowski wrote:
On Fri, Aug 27, 2010 at 10:30:07AM +0400, Stanislav Maslovski wrote:
On Fri, Aug 27, 2010 at 12:22:08AM +0200, posion bit wrote:
There are 38 unquoted $i in /etc in i386 installing base+laptop
On Fri, Aug 27, 2010 at 10:09:49AM +0200, posion bit wrote:
> > (/etc/mc/mc.menu)
> > case "$i" in
> > *.tar.gz) D="`basename $i .tar.gz`";;
>
> In that case, name-spaced filenames should work, because the
> string is a _quoted_ multi-word string.
i="cat's meow.tar.gz"
posion bit, le Fri 27 Aug 2010 10:09:49 +0200, a écrit :
> > (/etc/mc/mc.menu)
> > case "$i" in
> > *.tar.gz) D="`basename $i .tar.gz`";;
>
>
> In that case, name-spaced filenames should work, because the
> string is a _quoted_ multi-word string.
Not in the basename cal
On 27.08.2010 08:30, Stanislav Maslovski wrote:
On Fri, Aug 27, 2010 at 12:22:08AM +0200, posion bit wrote:
I've just started my love history again with squeeze.
There are 38 unquoted $i in /etc in i386 installing base+laptop+standar
There are 172 "$i" (maching without space
On Fri, Aug 27, 2010 at 9:58 AM, Adam Borowski wrote:
> On Fri, Aug 27, 2010 at 10:30:07AM +0400, Stanislav Maslovski wrote:
>> On Fri, Aug 27, 2010 at 12:22:08AM +0200, posion bit wrote:
>> > There are 38 unquoted $i in /etc in i386 installing base+laptop+standar
>>
On Fri, Aug 27, 2010 at 10:30:07AM +0400, Stanislav Maslovski wrote:
> On Fri, Aug 27, 2010 at 12:22:08AM +0200, posion bit wrote:
> > There are 38 unquoted $i in /etc in i386 installing base+laptop+standar
> >
> > There are 172 "$i" (maching without spaces arou
On Fri, Aug 27, 2010 at 12:22:08AM +0200, posion bit wrote:
> I've just started my love history again with squeeze.
>
> There are 38 unquoted $i in /etc in i386 installing base+laptop+standar
>
> There are 172 "$i" (maching without spaces around) 38 of them matches
I've just started my love history again with squeeze.
There are 38 unquoted $i in /etc in i386 installing base+laptop+standar
There are 172 "$i" (maching without spaces around) 38 of them matches
whit spaces around (unquoted).
Some are iteration numbers, some are directory, file
On 2009-03-08 Alban browaeys wrote:
> >From \amethyst on freenode #bash (Neil Moore) :
> <\amethyst> it is a bug I think
> <\amethyst> that you still get the error even with $...@-foo}
> <\amethyst> but $...@+"$@"} probably shouldn't error out
> <\amethyst> since ${foo+bar} does not
> <\amethys
clone 518752 -1
reassign -1 bash
found -1 4.0-1
retitle -1 set -u should not error on "${@:+}" if there are no args
thanks
On 2009-03-08 Alban browaeys wrote:
> >From \amethyst on freenode #bash (Neil Moore) :
> <\amethyst> it is a bug I think
> <\amethyst> that you still get the error even with
On 2009-03-08 jida...@jidanni.org wrote:
> Package: exim4-config
> Version: 4.69-9
> Severity: important
> File: /usr/sbin/update-exim4.conf
> starting with bash version 4.0-1:
> /var/log/boot:Sun Mar 8 19:13:03 2009: Starting
> MTA:/usr/sbin/update-exim4.conf: line 38:
S> What information do you have that tells you that the Origin field
S> is obsolete?
No. I'm saying I feel/guess/believe "Origin: debian" is obsolete, not
that "Origin:" is obsolete. I'm sure "Origin:" still has good uses.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
"Thijs Kinkhorst" <[EMAIL PROTECTED]> writes:
> So to conclude, there's no reason for that mass bug filing apart from your
> "feeling" that it "looks funny". Since it poses no real problem at all, I
> don't even see a lintian-test being warranted for this. This should indeed
> be closed unless you
On Tue, Apr 26, 2005 at 11:39:38AM +0200, Thijs Kinkhorst wrote:
> So to conclude, there's no reason for that mass bug filing apart from your
> "feeling" that it "looks funny". Since it poses no real problem at all, I
> don't even see a lintian-test being warranted for this. This should indeed
> be
On Sun, April 24, 2005 01:22, Dan Jacobson wrote:
> Thijs> Perhaps you can state in your bugreport why it is needed to fix
> Thijs> this. What problems does that field cause?
>
> I think they just need to delete a line somewhere.
> I assume Origin isn't necessary for these packages to say anymore.
Agney> mass bug filling is the worst way to do this. try to send a wishlist for
Agney> lintian and linda. So on the next time that these packages use them the
Agney> mantainers will be alerted about this.
Naw, on 220098: 39 packages unnecessarily still use "Bugs:
debbugs://bugs.debian.org" I was t
On Thu, April 21, 2005 23:23, Dan Jacobson wrote:
> It feels odd that a handful of packages seem to use a dusty field:
> $ grep ^O /var/lib/dpkg/available|sort|uniq -c
> 3 Origin: Debian
> 35 Origin: debian
> Shall I clone this bug to them to get them to take it away?
Perhaps you can state in your
dan,
mass bug filling is the worst way to do this. try to send a wishlist for
lintian and linda. So on the next time that these packages use them the
mantainers will be alerted about this.
On Fri, 22 Apr 2005 05:23:31 +0800
Dan Jacobson <[EMAIL PROTECTED]> wrote:
> Package: general
> Severity: m
Package: general
Severity: minor
It feels odd that a handful of packages seem to use a dusty field:
$ grep ^O /var/lib/dpkg/available|sort|uniq -c
3 Origin: Debian
35 Origin: debian
Shall I clone this bug to them to get them to take it away?
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
Package: wnpp
Version: unavailable; reported 2003-07-08
Severity: wishlist
* Package name: t38modem
Version : 0.6.2
Upstream Author : Vyacheslav Frolov
* URL : http://www.openh323.org
* License : MPL
Description : T.38 Fax over IP
/*
* $Id: README,v 1.7
69 matches
Mail list logo
