Please,
Is possible to know, which is default flags for packages? Or where can
i find this information? For example in Gentoo or in Sabayon is this
very easy. For Sabayon can I find all flags on the Sabayon's web page
for all packages.
Thank.
Best regards.
Baci
--
To UNSUBSCRIBE, email to deb
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-tablib
Version : 0.9.11-1
Upstream Author : Kenneth Reitz
* URL : https://github.com/kennethreitz/tablib
* License : MIT
Programming Lang: Python
Description : format agnosti
On Sat, Feb 2, 2013 at 4:28 PM, Pavel Baculák wrote:
> Is possible to know, which is default flags for packages? Or where can
> i find this information? For example in Gentoo or in Sabayon is this
> very easy. For Sabayon can I find all flags on the Sabayon's web page
> for all packages.
Sounds l
Pavel Baculák wrote:
> Please,
> Is possible to know, which is default flags for packages? Or where can
> i find this information? For example in Gentoo or in Sabayon is this
> very easy. For Sabayon can I find all flags on the Sabayon's web page
> for all packages.
(SID)ametzler@argenau:/tmp/TAS
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: cliff-tablib
Version : 1.0
Upstream Author : Doug Hellman
* URL : https://github.com/dreamhost/cliff-tablib
* License : Apache-2.0
Programming Lang: Python
Description : tablib form
[ quoting fixed, redirected to mailing list ]
On 2013-02-02 Pavel Baculák wrote:
> 2013/2/2 Andreas Metzler :
>> Pavel Baculák wrote:
>>> Please,
>>> Is possible to know, which is default flags for packages? Or where can
>>> i find this information? For example in Gentoo or in Sabayon is this
>>
Thank you very much for answer, but this are system flags. Or I am
writing mistake?? But I neads flags for package, for example in Gento
this are USE flags.
As example - mc have possibility USE flags - I found it, when I was
compiling mc from sources in .../debian/rules
DEB_CONFIGURE_EXTRA_FLAGS :=
Processing commands for cont...@bugs.debian.org:
> package general apt
Limiting to bugs with field 'package' containing at least one of 'general',
'apt'
Limit currently set to 'package':'general', 'apt'
> reassign 699475
Unknown command or malformed arguments to command.
> severity 699475 normal
Processing commands for cont...@bugs.debian.org:
> package general apt
Limiting to bugs with field 'package' containing at least one of 'general',
'apt'
Limit currently set to 'package':'general', 'apt'
> reassign 699475 apt
Bug #699475 [general] general: Reading package lists... DoneSegmentatio
I know, debian don't have to same mechanism as gentoo (debian have
very good packages support and package handling utility), but all
packages have to have some default EXTRA_FLAGS when was compiling as
packages. Because for example mc is compiling as default with vfs
support or with X support
Package: wnpp
Severity: wishlist
Owner: Alessio Treglia
* Package name: radium-compressor
Version : 0.5.1
Upstream Author : Kjetil S. Matheussen
* URL : https://github.com/kmatheussen/radium_compressor
* License : GPL
Programming Lang: C++
Description
On Wed, 2013-01-30 at 17:27:13 +, Wookey wrote:
> +++ Ian Jackson [2013-01-16 13:50 +]:
>
> > * The concrete syntax in build-depends should not use < > but rather
> >reuse the architecture qualification syntax.
>
> I have just been told of a specific reason to avoid using '< >' :
> D
Package: wnpp
Severity: wishlist
Owner: Xavier Guimard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: libcarp-fix-1-25-perl
Version : 1.01
Upstream Author : Michael G Schwern
* URL : http://search.cpan.org/~mschwern/Carp-Fix-1_25-1.01/
* Licens
On Fri, 2013-02-01 at 22:25:18 +0100, Jakub Wilk wrote:
> * Guillem Jover , 2013-01-29, 20:31:
> > if you are going to patch the package you might as well do the one
> > line change from "3.0 (native)" to "3.0 (quilt)", and rename the
> > source tarball to add «.orig».
>
> That's a good solution f
On Sun, 2013-01-27 at 16:20:25 +, Roger Leigh wrote:
> Given the amount of work already done by the Hurd porters, would
> it be viable to undef PATH_MAX and do a test build to look at how
> much this breaks? The other advantage is that it reduces duplicate
> codepaths in all the places where w
Guillem Jover, le Sat 02 Feb 2013 14:04:01 +0100, a écrit :
> But yes, doing such mass build would be very useful to see how many are
> still there. I'd also be in favor of removing MAX defines from all our
> currently supported architectures.
Rough estimation from buildd logs:
€ wanna-build --li
Package: wnpp
Severity: wishlist
Owner: Romain Beauxis
* Package name: shine
Version : 1.0.0
Upstream Author : The Savonet Team
* URL : https://github.com/savonet/shine
* License : LGPL2
Programming Lang: C
Description : Fixed-point MP3 encoding librar
Package: wnpp
Severity: wishlist
Owner: Romain Beauxis
* Package name: ocaml-shine
Version : 0.0.1
Upstream Author : The Savonet Team
* URL : http://github.com/savonet/ocaml-shine
* License : LGPL 2.1
Programming Lang: C
Description : OCaml bindings fo
Michael,
after re-reading your GoPackaging Wiki page and digging around a bit in
the sources for the go tool, I think that only minimal changes to go(1)
are needed for its build system to "Just Work" without breaking
expectations:
1. Debian user's/admin's perspective: As I have already written
el
I know, debian don't have to same mechanism as gentoo (debian have
very good packages support and package handling utility), but all
packages have to have some default EXTRA_FLAGS when was compiling as
packages. Because for example mc is compiling as default with vfs
support or with X support ...
On Sat, Feb 02, 2013 at 12:48:39PM +0100, Pavel Baculák wrote:
> I know, debian don't have to same mechanism as gentoo (debian have
> very good packages support and package handling utility), but all
> packages have to have some default EXTRA_FLAGS when was compiling as
> packages. Because for exa
Package: general
Severity: critical
Justification: breaks the whole system
Dear developers,
Almost everytime [it happens randomly] I try to see some video content via DRI
[VLC/XBMC, etc] on kernels with version higher than 3.2.0-3-686-pae the whole
system freeze [screen goes black, system is unre
reassign 699656 src:linux
forcemerge 693083 699656
thanks
Quoting marc (marc_sm...@gmx.com):
> I already reported this bug for the previous version of kernel [bug report
> #693083], but the problem is still unsolved.++
Hello,
As #693083 is still opened, I fail to see why you're opening yet
anot
Processing commands for cont...@bugs.debian.org:
> reassign 699656 src:linux
Bug #699656 [general] general: System freezes while using multimedia via DRI
[Intel 82865G chip] on kernels above 3.2.0-3-686-pae
Bug reassigned from package 'general' to 'src:linux'.
Ignoring request to alter found vers
24 matches
Mail list logo
