When I file a bug report with the Flyspray web interface, why can't I
specify the package it concerns? Having that option should make it
possible for the package maintainers to be immediately and
automatically notified of the report.
The way it works now seems to be that I have to wait for
On Mon, Mar 28, 2011 at 9:58 PM, Grigorios Bouzakis grb...@xsmail.com wrote:
Angus charmen...@gmail.com wrote:
When I file a bug report with the Flyspray web interface, why can't I
specify the package it concerns? Having that option should make it
possible for the package maintainers
On Mon, Mar 28, 2011 at 10:07 PM, Ionuț Bîru ib...@archlinux.org wrote:
On 03/27/2011 05:16 AM, Angus wrote:
When I file a bug report with the Flyspray web interface, why can't I
specify the package it concerns? Having that option should make it
possible for the package maintainers
On Mon, Mar 28, 2011 at 10:31 PM, Grigorios Bouzakis grb...@xsmail.com wrote:
Angus charmen...@gmail.com wrote:
But a script should be able to take care of this, no?
Doesn't a script solve everything?
Here is Arch's customized flyspray:
http://projects.archlinux.org/vhosts
When I file a bug report with the Flyspray web interface, why can't I
specify the package it concerns? Having that option should make it
possible for the package maintainers to be immediately and
automatically notified of the report.
The way it works now seems to be that I have to wait for some
Those are AUR packages, you need to ask their maintainers in the AUR to
make the necessary changes.
Learn2read, please. I was given the impression that this was going to
be solved with the python package:
On Thu, Oct 7, 2010 at 1:49 PM, Allan McRae al...@archlinux.org wrote:
Hmm... I probably
Hmm... I probably should have added a version to the provides line in the
python package. Currently it only provides python3 and not a version so
the versioned deps in those AUR packages are causing issues. I'll get
around to that before this exits [testing]
Um... did you perhaps not
Hmm... I probably should have added a version to the provides line in the
python package. Currently it only provides python3 and not a version so
the versioned deps in those AUR packages are causing issues. I'll get
around to that before this exits [testing]
Um... did you perhaps not
I'm glad Arch did the python3 transition and I agree with python3
being the default version (i.e. having 'python' symlink to
'python3.x').
But what's the reason for no longer having a package named 'python3'
with a symlink to 'python3.x'? It would make (/have made) the
transition a little easier,
On Thu, Oct 7, 2010 at 1:49 PM, Allan McRae al...@archlinux.org wrote:
On 07/10/10 14:40, Angus wrote:
I'm glad Arch did the python3 transition and I agree with python3
being the default version (i.e. having 'python' symlink to
'python3.x').
But what's the reason for no longer having
Hmm... I probably should have added a version to the provides line in the
python package. Currently it only provides python3 and not a version so
the versioned deps in those AUR packages are causing issues. I'll get
around to that before this exits [testing]
Allan
Yes, that makes
On 26/06/2008, at 6:13 PM, Maik Beckmann wrote:
Hi,
Can someone confirm that this
http://codepad.org/I313t7BN
compiled with
g++ -O3 test.cpp -o test
gives a segfault when trying to run it via
./test
Using gcc 4.3.1 on arch32, I don't get a segfault.
12 matches
Mail list logo
