Le vendredi, 20 juillet 2012 20.56:21, Tomasz Muras a écrit :
Those are fixes from upstream Moodle 2.2.4, correct?
If so, then I think that some more patches are required, those are not
covered:
MDL-31692 (CVE-2012-3389)
MDL-32126 (CVE-2012-3398)
MDL-33916 (CVE-2012-3388)
MDL-32199
On 07/23/2012 09:02 AM, Didier 'OdyX' Raboud wrote:
Le vendredi, 20 juillet 2012 20.56:21, Tomasz Muras a écrit :
...those are not covered:
MDL-31692 (CVE-2012-3389)
MDL-32126 (CVE-2012-3398)
MDL-33916 (CVE-2012-3388)
MDL-32199 (CVE-2012-3391)
MDL-31460 (CVE-2012-3392)
MDL-32155 (CVE-2012-3390)
Hello,
and is not installable concurrently with libcatalyst-perl on sid,
and soon on Wheezy:
https://lists.debian.org/debian-perl/2012/07/msg00098.html
This *might* be fixed by upstream 0.003009.
thanks for your report.
I have tested the newest Gitalist Version against 5.90014-1 and
On 2012-07-22 23:03, Iain Lane wrote:
I made this RC because this code needs to be right for the original
workaround to function.
That's fine. I didn't use a RC priority since the error was actually
ignored and I don't know anything about mono packages to decide the
severity of this problem.
Package: gnome-shell
Version: 3.4.1-8
Severity: serious
The default browser should be one that has at least vaguely credible
security support, IMO. epiphany doesn't qualify, chromium or iceweasel
probably would.
Cheers,
Julien
signature.asc
Description: Digital signature
Your message dated Mon, 23 Jul 2012 10:50:59 +0200
with message-id 20120723085059.GA24437@elende
and subject line Re: RC bugs to closed : Bug 682277 in libweb-id-perl
has caused the Debian Bug report #682277,
regarding libweb-id-perl: Missing Depends on libmousex-types-perl causing
On 12-07-23 at 10:50am, Salvatore Bonaccorso wrote:
On Sun, Jul 22, 2012 at 08:10:00PM +0200, Xavier wrote:
it seems that bug #682277 has been resolved by version 1.921-3 but
has not been closed.
This was more or less intentional, I added only the fixed version. But
indeed it should
Le lundi 23 juillet 2012 à 10:46 +0200, Julien Cristau a écrit :
Package: gnome-shell
Version: 3.4.1-8
Severity: serious
The default browser should be one that has at least vaguely credible
security support, IMO. epiphany doesn't qualify, chromium or iceweasel
probably would.
As
On Mon, Jul 23, 2012 at 10:55:49 +0200, Josselin Mouette wrote:
Le lundi 23 juillet 2012 à 10:46 +0200, Julien Cristau a écrit :
Package: gnome-shell
Version: 3.4.1-8
Severity: serious
The default browser should be one that has at least vaguely credible
security support, IMO.
interestingly this error is handled differently for --import and --install:
# umount /proc/sys/fs/binfmt_misc
# update-binfmts --import llvm-3.1.binfmt
update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register:
Invalid argument
update-binfmts: warning: unable to enable binary
On Mon, Jul 23, 2012 at 12:44:53PM +0800, Aron Xu wrote:
Hi,
I'm for Adam's patch, it looks to be the correct approach to resolve
the problem as well as fulfill the requirement of being multiarch. In
case of doubt I have tried to rebuild all rdepends of liblua5.1-0 in
Sid and there is no
Hi,
A new version of this package has been languishing unsponsored on
mentors for two months: http://mentors.debian.net/package/cvc3. Can
you check that the problem persists in that version?
It appears to be fixed in your 2.4.1-3 package.
Seconded.
lintian found some warnings, could
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006er...@franck.debian.org
and subject line Bug#682183: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682183,
regarding liblua5.1-0-dev: lua-deb-multiarch.h not found when compiling source
including lua.h
to
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006er...@franck.debian.org
and subject line Bug#682183: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682183,
regarding liblua5.1-0-dev: Lua5.1 include changes in 5.1.5-3 cause other
packages to FTBFS
to be
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006eu...@franck.debian.org
and subject line Bug#682234: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682234,
regarding liblua5.1-0-dev: Lua5.1 include changes in 5.1.5-3 cause other
packages to FTBFS
to be
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006er...@franck.debian.org
and subject line Bug#682183: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682183,
regarding CMake cannot find correct header path of lua5.1 after latest update
to be marked as done.
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006eu...@franck.debian.org
and subject line Bug#682234: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682234,
regarding liblua5.1-0-dev: lua-deb-multiarch.h not found when compiling source
including lua.h
to
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006ex...@franck.debian.org
and subject line Bug#682299: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682299,
regarding CMake cannot find correct header path of lua5.1 after latest update
to be marked as done.
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006eu...@franck.debian.org
and subject line Bug#682234: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682234,
regarding CMake cannot find correct header path of lua5.1 after latest update
to be marked as done.
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006ex...@franck.debian.org
and subject line Bug#682299: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682299,
regarding liblua5.1-0-dev: lua-deb-multiarch.h not found when compiling source
including lua.h
to
Your message dated Mon, 23 Jul 2012 10:02:12 +
with message-id e1stfsu-0006ex...@franck.debian.org
and subject line Bug#682299: fixed in lua5.1 5.1.5-4
has caused the Debian Bug report #682299,
regarding liblua5.1-0-dev: Lua5.1 include changes in 5.1.5-3 cause other
packages to FTBFS
to be
Processing commands for cont...@bugs.debian.org:
# 682100 is also present in the version currently in testing
found 682100 1.0.4-2
Bug #682100 {Done: Jeffrey Ratcliffe j...@debian.org} [gscan2pdf] gscan2pdf
Recommends cuneiform which is in non-free
Marked as found in versions
Hi,
Jonas Genannt wrote (23 Jul 2012 07:54:38 GMT) :
I have tested the newest Gitalist Version against 5.90014-1 and
5.90015-1.
Both are failing with Gitalist because of use of
Catalyst::Controller::ActionRole.
After that test, I have patched the Gitalist source with the patch
from
Processing commands for cont...@bugs.debian.org:
severity 682486 grave
Bug #682486 [python-jpylyzer] python-jpylyzer: jpylyzer is not installed
Severity set to 'grave' from 'important'
tags 682486 pending
Bug #682486 [python-jpylyzer] python-jpylyzer: jpylyzer is not installed
Added tag(s)
Hello,
Hopefully things will change in the future,
but IMHO a package that:
1. has been FTBFS'ing (tests failed) since late march (was any
action taken, that the #665223 bug log does not show, apart of
replying I will contact upstream?)
I have sent upstream Daniel Brooks a
Package: biomaj-watcher
Version: 1.2.0-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies files from
another package.
From the attached log (scroll to the bottom...):
2m3.0s ERROR: FAIL: After purging files
Jonas Genannt wrote (23 Jul 2012 10:49:14 GMT) :
1. has been FTBFS'ing (tests failed) since late march (was any
action taken, that the #665223 bug log does not show, apart of
replying I will contact upstream?)
I have sent upstream Daniel Brooks a Mail on: 10 Jun 2012 but no
I will try to contact the other upstream dev, if there is no
response I will request of removing Gitalist from Wheezy.
How about submitting the bug to the CPAN RT, so that information about
it is shared with the general public?
I will submit one.
Thanks,
Jonas
--
To
Moritz,
Do you still see any reason to keep this bug report open?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
tags 661471 - patch
Bug #661471 [gnome-themes-standard] gnome-themes-standard: removal of
gnome-themes-standard makes files disappear from gnome-accessibility-themes
Removed tag(s) patch.
stop
Stopping processing here.
Please contact me if you
Hi Thomas,
hereby Cc:-ing), I don't know if it is still relevant
for the latest version that I have NMUed. What is to
find out is if it is still relevant with version
1.3.4-0.1
The patch that you did is working for me.
If you registered to the pkg-php alioth project, you
will have to give
Your message dated Mon, 23 Jul 2012 11:17:10 +
with message-id e1stgds-0005yq...@franck.debian.org
and subject line Bug#682486: fixed in jpylyzer 1.5.0-2
has caused the Debian Bug report #682486,
regarding python-jpylyzer: jpylyzer is not installed
to be marked as done.
This means that you
On Mon, Jul 23, 2012 at 01:43:17AM +0900, Norbert Preining wrote:
* these fonts have unclear license status. It is not clear whether
taking the various glyphs from various sides and adding some things
and sticking it together is fine.
Technical issues aside, I'd like to ask everybody not
Package: ruby-gruff
Followup-For: Bug #676206
Dear Nobuhiro,
Thank you for working on this issue. The bug is simply caused by the fact that
taking the modulo with respect to 0.0 gives an Division by zero error
with Ruby1.9, but raises no error and return NaN with Ruby1.8.
This has been
Processing commands for cont...@bugs.debian.org:
fixed 681475 4.7.1-5
Bug #681475 {Done: Matthias Klose d...@debian.org} [gcc-4.7] std::pair
C++03/11 incompat
There is no source info for the package 'gcc-4.7' at version '4.7.1-5' with
architecture ''
Unable to make a source version for version
Thank you! We'll need to make sure this version be unblocked by release
team so newly built binaries depending on liblua5.1 can migrate to testing
without problem.
On Mon, Jul 23, 2012 at 09:19:40PM +0800, Aron Xu wrote:
Thank you! We'll need to make sure this version be unblocked by release
team so newly built binaries depending on liblua5.1 can migrate to testing
without problem.
I've already pinged debian-release, but I guess they want to see if it
severity 682232 important
thanks
Antti-Juhani,
Thanks for your cooperation.
Since you have managed to recover I feel fully justified in downgrading
to important. The information you have sent from the logs is very good,
but so far no different from any other innodb corruption.
Processing commands for cont...@bugs.debian.org:
severity 682232 important
Bug #682232 [mysql-server-5.5] mysql-server-5.5: Fails to upgrade squeeze -
wheezy, does not start
Severity set to 'important' from 'grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
tags 676206 + pending fixed-upstream
Bug #676206 [src:ruby-gruff] ruby-gruff: FTBFS: tests failed
Added tag(s) fixed-upstream and pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
676206:
Package: ocfs2console
Version: 1.6.4-1
Severity: grave
Justification: renders package unusable
At start:
ocfs2console
Gtk-Message: Failed to load module canberra-gtk-module
Traceback (most recent call last):
File /usr/sbin/ocfs2console, line 38, in module
from ocfs2interface.console import
Package: msva-perl
Version: 0.8-2
Severity: critical
After doing a wheezy-to-wheezy upgrade on this laptop, logging in to
my session now seems impossible. This is my .xsession-errors:
/etc/gdm3/Xsession: Beginning session setup...
Better hope you get what you want before you stop wanting it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm sorry for my english,
IMO
pycompile -p pyside-tools
Automatically added by dh_python2
fails on python3 code.
To fix, simply rename
pysideuic/port_v3/proxy_base.py
to
pysideuic/port_v3/proxy_base.py3
Not sure if worth rename all files
Source: haskell-data-accessor-template
Version: 0.2.1.9-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC
Source: haskell-path-pieces
Version: 0.1.0-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203
Source: haskell-haxr
Version: 3000.8.5-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203
Source: haskell-shakespeare
Version: 1.0.0.2-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-shakespeare-text
Version: 1.0.0.2-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10
Your message dated Mon, 23 Jul 2012 15:02:25 +
with message-id e1stk9r-pi...@franck.debian.org
and subject line Bug#682293: fixed in fex 20120718-3
has caused the Debian Bug report #682293,
regarding fex: prompting due to modified conffiles which were not modified by
the user:
Source: haskell-shakespeare-i18n
Version: 1.0.0.2-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10
Source: haskell-yesod-routes
Version: 1.0.1.2-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-persistent-template
Version: 0.9.0.2-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10
Source: haskell-hamlet
Version: 1.0.1.3-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203
Source: haskell-happstack-server
Version: 7.0.1-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-yesod-auth
Version: 1.0.2.1-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-clientsession
Version: 0.7.5-3
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-yesod-static
Version: 1.0.0.2-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-fclabels
Version: 1.1.3-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203
Source: haskell-cabal-file-th
Version: 0.2.2-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-test-framework-th-prime
Version: 0.0.5-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC
Source: haskell-file-embed
Version: 0.0.4.4-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Source: haskell-test-framework-th
Version: 0.2.2-5
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682521,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682522,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682523,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682524,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682525,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682526,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682528,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682534,
Your message dated Mon, 23 Jul 2012 16:22:28 +0100
with message-id 20120723152228.GB7508@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682528:
haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name
on Build-Depends
has caused the Debian Bug report #682535,
Source: haskell-options
Version: 0.1.1-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203
Source: haskell-boomerang
Version: 1.3.1-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203
Source: haskell-postgresql-simple
Version: 0.1.4.3-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10
Source: haskell-chell
Version: 0.3-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
On Tue, Jul 24, 2012 at 12:05:28AM +0900, Hiroyuki Yamamoto wrote:
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
How is this a FTBFS?
--
To UNSUBSCRIBE, email to
Source: haskell-hledger
Version: 0.18.1-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203
Source: haskell-hledger-web
Version: 0.18.1-1
Severity: serious
Don't use ghc-ghci virtual-package-name on Build-Depends,
because it has not been allowed yet by Debian-Policy
to use the virtual-package-name of ghc-ghci.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682531,
regarding
opendkim builds again now. Thanks.
Scott K
signature.asc
Description: This is a digitally signed message part.
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682533,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682536,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682537,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682539,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682541,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682544,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682542,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682546,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682545,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682548,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682547,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682549,
regarding
Your message dated Mon, 23 Jul 2012 17:10:54 +0100
with message-id 20120723161054.GB2733@raleigh
and subject line Re: [Pkg-haskell-maintainers] Bug#682550: haskell-hledger-web:
FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
has caused the Debian Bug report #682550,
regarding
Hi Gaionim (2012.07.23_16:33:35_+0200)
To fix, simply rename
pysideuic/port_v3/proxy_base.py
to
pysideuic/port_v3/proxy_base.py3
.py3 would be wrong. That file just shouldn't be present in a python-X
package, if it doesn't support python 2.
SR
--
Stefano Rivera
Your message dated Mon, 23 Jul 2012 16:32:14 +
with message-id e1stlym-0005g9...@franck.debian.org
and subject line Bug#666023: fixed in dkms 2.2.0.3-1.1
has caused the Debian Bug report #666023,
regarding dkms: /usr/lib/dkms/common.postinst fails if /lib/modules does not
exist
to be marked
On Sun, Jul 22, 2012 at 12:07:53PM +0200, Bastian Blank wrote:
And a quick check reveals that ovs-vsctl is installed two times. It is
included in bin_PROGRAMS and bin_SCRIPTS. They are evalutated in two
different make targets and may run parallel.
Thanks for spotting the problem. I uploaded a
ovs-vsctl is listed, incorrectly, in both bin_PROGRAMS and bin_SCRIPTS.
This meant that make install with the -j option could try to install
ovs-vsctl two times in parallel, a race that occasionally caused a build
failure, e.g.:
Your message dated Mon, 23 Jul 2012 17:02:47 +
with message-id e1stm1v-o7...@franck.debian.org
and subject line Bug#682384: fixed in openvswitch 1.4.2+git20120612-6
has caused the Debian Bug report #682384,
regarding odd s390 build failure for openvswitch
to be marked as done.
This means
On Mon, 23 Jul 2012, Chris Knadle wrote:
On Monday, July 23, 2012 10:34:28, Ian Jackson wrote:
Of these 2. would seem to be the best option.
I agree.
[...]
I believe in order to actually evaluate any of these solutions,
someone is going to have to prepare binaries, and do an table
Le lundi, 23 juillet 2012 09.02:08, vous avez écrit :
Le vendredi, 20 juillet 2012 20.56:21, Tomasz Muras a écrit :
Those are fixes from upstream Moodle 2.2.4, correct?
If so, then I think that some more patches are required, those are not
covered:
I cherry-picked:
MDL-31692
1 - 100 of 132 matches
Mail list logo
