Paul Wise writes:
> Do you know how to run that in an automated way? I would like to add
> it here and to my pbuilder hook:
> http://wiki.debian.org/HowToPackageForDebian#Check_points_for_any_package
Run the normal build system commands under scan-build. In other:
scan-build ./configure .
On 2013-07-04 03:27, Kurt Roeckx wrote:
> On Wed, Jul 03, 2013 at 05:35:35PM +0200, Ondrej Surý wrote:
>>> fabien boucher
>>> libjson0-dev : json-c
>>> /usr/lib/x86_64-linux-gnu/libjson.so
>>
>> Also a false positive - this is result of json to json-c library name
>> transition made by
On Thu, Jul 4, 2013 at 12:48 PM, Kurt Roeckx wrote:
> I guess you could ask, but I have a feeling they would prefer to
> work with the upstream projects.
I've sent an email to scan-ad...@coverity.com.
> clang also has an option to do that now I think, did someone try
> to run that on the archive
On Thu, Jul 04, 2013 at 12:39:05PM +0800, Paul Wise wrote:
> On Thu, Jul 4, 2013 at 12:28 PM, Kurt Roeckx wrote:
>
> > I think any open source project can ask that
>
> Indeed, however, for a project like Debian it would probably require
> some changes in their service or at least an ack for the l
Bradley,
On Wed, Jul 3, 2013 at 5:34 PM, Bradley M. Kuhn wrote:
> [...]
> Upon catching up on this thread, I believe most of what needs to be said
> about the issue for Debian's perspective has been said. Nevertheless, I
> do want to point out that I think three separate issues have been
> conf
On Thu, Jul 4, 2013 at 12:27 AM, Michael Banck wrote:
> Hi,
>
> On Tue, Jul 02, 2013 at 02:48:18PM +0100, Ben Hutchings wrote:
> > If the relicensing is real and not another misconfiguration of the
> > build/release system (like with MySQL docs), this sounds like a
> > shakedown for proprietary u
On Thu, Jul 4, 2013 at 12:28 PM, Kurt Roeckx wrote:
> I think any open source project can ask that
Indeed, however, for a project like Debian it would probably require
some changes in their service or at least an ack for the large amount
of computing resources that scanning our archive would use.
On Thu, Jul 04, 2013 at 11:36:25AM +0800, Paul Wise wrote:
> On Tue, Jun 25, 2013 at 1:28 PM, Alexandre Rebert wrote:
>
> > We found the bugs using Mayhem [1], an automatic bug finding system
> > that we've been developing in David Brumley's research lab for a
> > couple of years. We recently ran
BTW, your crash.sh scripts have a bug. When passing data on stdin to
the program but running the program under gdb, you have to use the
-tty argument to gdb instead of passing the data to stdin of gdb.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ.
On Tue, Jun 25, 2013 at 1:28 PM, Alexandre Rebert wrote:
> We found the bugs using Mayhem [1], an automatic bug finding system
> that we've been developing in David Brumley's research lab for a
> couple of years. We recently ran Mayhem on almost all ELF binaries of
> Debian Wheezy (~23K binaries)
On Wed, Jul 03, 2013 at 05:35:35PM +0200, Ondrej Surý wrote:
> > fabien boucher
> > libjson0-dev : json-c
> > /usr/lib/x86_64-linux-gnu/libjson.so
>
> Also a false positive - this is result of json to json-c library name
> transition made by upstream and the symlink is kept there to a
On Tue, Jul 02, 2013 at 03:32:00PM -0700, John H. Robinson, IV wrote:
> Svante Signell wrote:
> >
> > I've been thinking about this for some time now. There is a need for a
> > gplv3+-compliant Debian-based distribution! Meaning that gplv2 only code
> > will not be included! For kernels, kFreeBSD
Hi,
On Tue, Jul 02, 2013 at 02:48:18PM +0100, Ben Hutchings wrote:
> If the relicensing is real and not another misconfiguration of the
> build/release system (like with MySQL docs), this sounds like a
> shakedown for proprietary users of Berkeley DB. GPLv2-licensed users
> are collateral damage.
On Wed, Jul 3, 2013 at 5:34 PM, Bradley M. Kuhn wrote:
> On (b), I think the discussion about apt needing to be (effectively)
> AGPLv3-or-later to continue using BDB is salient. I, for one, would
> like to see such a thing, but I'm a biased party who co-authored AGPLv3
> and believe in its policy
Package: wnpp
Severity: wishlist
Owner: Sebastian Gibb
* Package name: r-cran-readmzxmldata
Version : 2.7
Upstream Author : Sebastian Gibb
* URL :
http://cran.r-project.org/web/packages/readMzXmlData/index.html
* License : GPL
Programming Lang: R
Descript
On Wed, 03 Jul 2013, Ian Jackson wrote:
> But mode A involves /etc/resolf.conf not changing during the boot
> process. As I wrote in my original description:
>A. resolv.conf is a static file which changes only very rarely.
>
> So your statement that resolvconf supports mode A is simply incorr
On Wed, 03 Jul 2013, Tollef Fog Heen wrote:
> Does that mean it's an RC bug for any non-manual process to overwrite
> [/etc/resolv.conf]? I'd be happy to file bugs.
I don't believe it's RC, but it's certainly a bug. [The fact that
dhclient does this when it's not called with appropriate arguments
Szanowny debian-devel@lists.debian.org
Jestem przedstawicielem serwisu Kwaterypracownicze.net, która na co dzień zajmuje się promocj noclegów z całej Polski.
W związku z profilem naszego seriwsu doszlimy do wniosku, że mogli by Państwo być zainteresowani naszymi
usługami. Dlatego chciałbym zapyt
Hello!
Andrey Ponomarenko wrote:
> There is a new simple way to track changes in API/ABI of system
> libraries using a new ABI dumper [1] tool.
Thanks for the tipp!
> However, this approach has some drawbacks. Perhaps the main drawback is
> the inability to perform some compatibility checks. For
On 07/03/2013 09:17 PM, Svante Signell wrote:
The interesting thing is not when Linus used the GPL license the first
time, it was v2 by then. Of crucial interest is when Linus changed from
v2 or later to v2 only. And looking at the source code, e.g. 3.9.8, a
very lot of files are still v2+, not v
On Tue, 2013-07-02 at 15:32 -0700, John H. Robinson, IV wrote:
> Svante Signell wrote:
> >
> > I've been thinking about this for some time now. There is a need for a
> > gplv3+-compliant Debian-based distribution! Meaning that gplv2 only code
> > will not be included! For kernels, kFreeBSD and Hur
On Sat, Jun 29, 2013 at 09:36:15AM +0200, Petter Reinholdtsen wrote:
> Traditionally, on Unix like systems, it is possible to run the 'w' and
> 'who' command to see all logged in users and ttys currently in used on
> the system. These commands look in /var/run/utmp to figure out what
> users are l
On Tue, Jul 2, 2013 at 10:57 AM, Bernhard R. Link wrote:
> * Paul Tagliamonte [130702 15:15]:
>> Again, why do you plan on removing free software from main due to a
>> change in license?
>
> Licenses matter. Just because something it acceptable for Debian
> main does not mean it is a good idea to
]] Ian Jackson
> Ian Jackson writes ("Re: boot ordering and resolvconf"):
> ...
> > I think the first thing to do is recognise the underlying problem. To
> > fix this problem properly we need a coherent system design. The two
> > designs lead to different sets of fixes.
> >
> > A. resolv.conf
Many people off-list have been asking me to comment on this discussion,
because (like Richard Fontana) I'm a co-author of AGPLv3, and I also
(back in the early 2000's) invented the original licensing idea behind
the AGPLv1.
I thus care deeply about the license and believe it's an important
policy
> fabien boucher
> libjson0-dev : json-c
> /usr/lib/x86_64-linux-gnu/libjson.so
Also a false positive – this is result of json to json-c library name
transition made by upstream and the symlink is kept there to allow programs
to be compiled with -ljson.
Ondrej
To those who aren't yet familiar with resolvconf, I'd suggest reading
the resolvconf package README and the resolvconf(8) manpage.
http://anonscm.debian.org/gitweb/?p=resolvconf/resolvconf.git;a=blob;f=README
http://anonscm.debian.org/gitweb/?p=resolvconf/resolvconf.git;a=blob;f=man/resolvcon
Le 3 juil. 2013 14:50, "José Luis Redrejo Rodríguez"
a écrit :
>
> I've been maintaining qucs since 2004 to 2012, so I know this package
pretty well and I have already prepared most part of its debianization. Did
you fill an ITP ?
> We can arrange a qucs maintaining group if you want.
We must fir
Ian Jackson writes ("Re: boot ordering and resolvconf"):
...
> I think the first thing to do is recognise the underlying problem. To
> fix this problem properly we need a coherent system design. The two
> designs lead to different sets of fixes.
>
> A. resolv.conf is a static file which changes
Package: wnpp
Severity: wishlist
Owner: Andy Hawkins
* Package name: libcoverart-0
Version : 1.0.0
Upstream Author : Andy Hawkins
* URL : http://musicbrainz.org/doc/libcoverart
* License : LGPL
Programming Lang: C++
Description : Library to access cove
> Shortly, piuparts.debian.org will be elevating the broken symlink test
> in sid from a warning to an error status. In advance of that, bugs
> submissions are planned against packages which are responsible for
> such links.
I don't think this is a good idea.
> These are sometimes triggered b
Petter Reinholdtsen writes ("Is updating utmp when logging in a user a
requirement in Debian?"):
> So my question to my fellow debian developers is simply this: Is correct
> updating of utmp and wtmp a requirement in debian, or just nice to have?
> Is it a wishlist bug to fix it, or a release crit
Hi,
I part of upstream i ami going to package this.
I will post to mentor this week
Le 3 juil. 2013 11:48, "José L. Redrejo" a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: José L. Redrejo Rodríguez
>
> * Package name: qucs
> Version : 0.0.17
> Upstream Author : Frans S
Thomas Hood writes ("Re: boot ordering and resolvconf"):
> Well, you are right that resolvconf was designed to support mode B,
> and only supports mode A as a trivial case of mode B where a local
> forwarding nameserver is always running.
But mode A involves /etc/resolf.conf not changing during th
I've been maintaining qucs since 2004 to 2012, so I know this package
pretty well and I have already prepared most part of its debianization. Did
you fill an ITP ?
We can arrange a qucs maintaining group if you want.
Regards.
2013/7/3 Bastien ROUCARIES
> Hi,
>
> I part of upstream i ami going
Package: wnpp
Severity: wishlist
Owner: "Cédric Boutillier"
* Package name: ruby-cri
Version : 2.3.0
Upstream Author : Denis Defreyne
* URL : https://github.com/ddfreyne/cri
* License : Expat
Programming Lang: Ruby
Description : tool to build easy-to-u
Package: wnpp
Severity: wishlist
Owner: "Cédric Boutillier"
* Package name: nanoc
Version : 3.6.4
Upstream Author : Denis Defreyne
* URL : http://nanoc.ws
* License : Expat
Programming Lang: Ruby
Description : static site generator written in Ruby
nan
Package: wnpp
Severity: wishlist
Owner: José L. Redrejo Rodríguez
* Package name: qucs
Version : 0.0.17
Upstream Author : Frans Schreuder
* URL : http://qucs.sourceforge.net/
* License : GPL
Description : Quite Universal Circuit Simulator
Qucs is an int
On Wed, Jul 3, 2013 at 4:24 PM, Tollef Fog Heen wrote:
> Manually reconfigure unbound to use those DNS servers as forwarders.
...and then manually reconfigure it to do its own lookups when you go
to another network and find they aren't reachable from there?
--
bye,
pabs
http://wiki.debian.org/
Package: wnpp
Severity: wishlist
Owner: "Eugenio Cano-Manuel Mendoza"
* Package name: libdata-xml-clojure
Version : 0.0.7
Upstream Author : Rich Hickey and others
* URL : https://github.com/clojure/data.xml
* License : EPL-1
Programming Lang: Clojure, Java
Hi Andrey,
On Wed, Jul 3, 2013 at 10:24 AM, Andrey Ponomarenko
wrote:
> Hi,
>
> There is a new simple way to track changes in API/ABI of system libraries
> using a new ABI dumper [1] tool. Just compile two library versions with -g
> additional option (to contain DWARF debug info) or take them fro
Hi,
There is a new simple way to track changes in API/ABI of system
libraries using a new ABI dumper [1] tool. Just compile two library
versions with -g additional option (to contain DWARF debug info) or take
them from the appropriate debug packages and create ABI dumps of both:
abi-dumper
]] Paul Wise
> On Wed, Jul 3, 2013 at 2:36 PM, Tollef Fog Heen wrote:
>
> > No, in my setup it should not do that without admin intervention. Doing
> > that means it's likely to cause security-related problems. I use DNSSEC
> > and don't want to trust random resolvers, I want to trust the one
43 matches
Mail list logo
