n.org.
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20120723-00:03"
X_INSTALLATION_MEDIUM=cdrom
===
On 07/24/2012 01:16 AM, Craig Small wrote:
>> A possible solution that should work:
>> * procps ships uptime.procps and uptime.procps.1.gz
>> * live-utils ships live-uptime and live-uptime.1.gz
>> * both register an alternative for uptime with uptime.1.gz slave
> Yep, would of done it had I known a
rico Tassi
>
> I'm re-running the massive rebuild of rdepends, and will follow-up
> when it gets done.
>
Hi,
The rebuild was done, and no regression was found, build logs are at:
http://people.debian.org/~aron/rebuild/lua5.1/20120723/
--
Regards,
Aron Xu
--
To UNSUBSCRIBE
Your message dated Tue, 24 Jul 2012 05:17:18 +
with message-id
and subject line Bug#681069: fixed in linkchecker 7.9-2.2
has caused the Debian Bug report #681069,
regarding Throws exceptions when run
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Here's the revised NMU diff.diff -Nru linkchecker-7.9/debian/changelog linkchecker-7.9/debian/changelog
--- linkchecker-7.9/debian/changelog 2012-07-23 23:03:31.0 -0400
+++ linkchecker-7.9/debian/changelog 2012-07-24 01:02:14.0 -0400
@@ -1,3 +1,12 @@
+linkchecker (7.9-2.2) unstable;
On 07/23/2012 07:09 PM, Ruben Rubio Rey wrote:
> 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
All you have to do is make sure you catch the attribute error at these two
lines:
gwibber/gwui.py:if "gwibber" not in urlparse.uses_query:
gwibber/gwui.py: urlparse.uses_query.append("gwibber")
if urlparse.uses_qwery doesn't exist (as it doesn't in the 2.7.3 in unstable).
--
To UNSUBSCRIBE,
Processing commands for cont...@bugs.debian.org:
> tags 680931 + fixed-upstream
Bug #680931 [g++-4.7] libarmadillo-dev: trivial program fails to compile
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
680931: http://bugs.debian.org/cgi
Processing commands for cont...@bugs.debian.org:
> fixed 677801 1.1-3
Bug #677801 {Done: Carl Chenet } [python-pip]
AttributeError: 'module' object has no attribute 'uses_fragment'
Marked as fixed in versions python-pip/1.1-3.
> thanks
Stopping processing here.
Please contact me if you need assi
Your message dated Tue, 24 Jul 2012 03:32:11 +
with message-id
and subject line Bug#681069: fixed in linkchecker 7.9-2.1
has caused the Debian Bug report #681069,
regarding Throws exceptions when run
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
No maintainer reply for ~ 2 weeks on a bug that's been RC for ~a week, so I'll
go ahead an upload it. NMU diff attached. Note that this bug doesn't
currently affect testing, only unstable, but if the python2.7 update gets let
through, then it will.
Scott Kdiff -Nru linkchecker-7.9/debian/chan
Package: libnet-dns-perl
Version: 0.68-1
Severity: serious
Tags: patch
Okay, so I'm not going to bother including an actually diff/patch
for a 9-character addition to debian/control, but consider this a
verbal patch. :P
On several buildds (and it should have been on all of them), the
testsuite fo
On Thu, Apr 19, 2012 at 03:45:16PM +0200, Luc Novales wrote:
> anonymous acces works perfectly but "user + password" acces return an error :
> Error opening connection:
> [LDAP: error code 49 - Invalid Credentials]
>
> using sourceforge version 3.3b3 allow connexion on the same server (but have
On Mon, Jul 23, 2012 at 09:58:19AM -0700, Ben Pfaff wrote:
> 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.:
>
Processing commands for cont...@bugs.debian.org:
> unarchive 671785
Bug #671785 {Done: Matthias Klose } [python2.7] segfaults when
running reportbug
Unarchived Bug 671785
> reopen 671785
Bug #671785 {Done: Matthias Klose } [python2.7] segfaults when
running reportbug
Bug reopened
Ignoring reques
Hi,
I'm still getting this bug, using the Wheezy weekly build
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-xfce+lxde-CD-1.iso
from 23-Jul-2012. It also still occurs in the corresponding weekly
netinst image.
regards
Nik
--
To UNSUBSCRIBE, email to debia
On Mon, Jul 23, 2012 at 10:18:28PM +0200, Andreas Beckmann wrote:
> Mixing diversions and alternatives is not trivial ... I know from
> cleaning up the nvidia-graphics-driver and fglrx-driver diversion mess
> for /usr/lib/libGL.so* :-)
I believe there is also something about packages diverting othe
Your message dated Mon, 23 Jul 2012 23:03:12 +
with message-id
and subject line Bug#672439: fixed in ufw 0.31.1-2
has caused the Debian Bug report #672439,
regarding ufw: destroy all iptable rules on purging (breaks e.g. fail2ban)
to be marked as done.
This means that you claim that the probl
Processing commands for cont...@bugs.debian.org:
> tags 682401 + pending
Bug #682401 [apache2-utils] dbmmanage: please use Digest::SHA instead of
Digest::SHA1
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
682401: http://bugs.debian.org/cgi
tags 682401 + pending
thanks
Hi,
On 22.07.2012 22:22, Stefan Fritsch wrote:
> AFAICS, dbmmanage has not seen a single code commit upstream since the
> C variant, htdbm, has been introduced in 2001. Maybe we should get rid
> of dbmmanage in the 2.4 packages. But unbreaking it for wheezy by
> us
Your message dated Mon, 23 Jul 2012 20:47:50 +
with message-id
and subject line Bug#682248: fixed in mono-tools 2.10-6
has caused the Debian Bug report #682248,
regarding monodoc-browser: postinst errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 23 Jul 2012 20:48:04 +
with message-id
and subject line Bug#682433: fixed in pandoc 1.9.4.2-2
has caused the Debian Bug report #682433,
regarding pandoc: FTBFS[mips* sparc s390x]: threading detection broken
to be marked as done.
This means that you claim that the probl
Processing commands for cont...@bugs.debian.org:
> tags 672870 - moreinfo + upstream
Bug #672870 {Done: Andreas Beckmann } [nvidia-glx]
nvidia-glx: Hang when switching to text-mode (only when using Xinerama),
nvidia-295.40
Removed tag(s) moreinfo.
Bug #672870 {Done: Andreas Beckmann } [nvidia-gl
Package: live-tools,procps
Severity: serious
Hi,
live-utils (3.0.3-1)
* diverts /usr/bin/uptime to /usr/bin/uptime.procps
* does not divert uptime.1.gz
* ships /usr/bin/uptime -> live-uptime
procps (1:3.3.3-2)
* ships /usr/bin/uptime
* ships uptime.1.gz
* installs an alternative for uptime if /u
Thanks. I pushed this fix to master and branch-1.[87654].
On Mon, Jul 23, 2012 at 12:34:33PM -0700, Ethan Jackson wrote:
> Looks good, thanks.
>
> Ethan
>
> On Mon, Jul 23, 2012 at 9:58 AM, Ben Pfaff wrote:
> > ovs-vsctl is listed, incorrectly, in both bin_PROGRAMS and bin_SCRIPTS.
> > This me
Looks good, thanks.
Ethan
On Mon, Jul 23, 2012 at 9:58 AM, Ben Pfaff wrote:
> 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 buil
On Monday, July 23, 2012 13:26:57, Don Armstrong wrote:
> 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 sol
Your message dated Mon, 23 Jul 2012 18:32:13 +
with message-id
and subject line Bug#682203: fixed in moodle 2.2.3.dfsg-2.1
has caused the Debian Bug report #682203,
regarding Multiple security issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Mon, 23 Jul 2012 17:59:27 +
with message-id <20120723175927.ga19...@scru.org>
and subject line Re: Bug#682527: haskell-yesod-routes: FTBFS: Don't use
"ghc-ghci" virtual-package-name on Build-Depends
has caused the Debian Bug report #682527,
regarding haskell-yesod-routes: FT
On Mon, Jul 23, 2012 at 9:23 PM, Enrico Tassi wrote:
> 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 alre
Processing commands for cont...@bugs.debian.org:
> severity 682125 minor
Bug #682125 [ca-certificates] ca-certificates: removes directories that were
installed by another package: /etc/ssl/certs/
Severity set to 'minor' from 'serious'
> thanks
Stopping processing here.
Please contact me if you n
(2012-07-24 02:30 +), Clint Adams wrote:
> 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 th
Dear maintainer,
I've prepared an NMU for moodle (versioned as 2.2.3.dfsg-2.2) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru moodle-2.2.3.dfsg/debian/changelog moodle-2.2.3.dfsg/debian/changelog
--- moodle-2.2.3.dfsg/debian/changelog 201
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 (C
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 s
Your message dated Mon, 23 Jul 2012 17:02:47 +
with message-id
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 that you claim that the problem has
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.:
http://buildd.debian.org/status/fetch.php?pkg=openvswitch&arch=s390&
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
Your message dated Mon, 23 Jul 2012 16:32:14 +
with message-id
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 as done.
This means that you claim t
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
http://tumbleweed.o
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 h
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 h
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 h
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 h
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 h
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 h
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 h
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 h
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 h
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 h
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 h
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 h
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 h
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 #682531,
regarding h
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
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
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 debian-bugs-
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
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 3A1
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 520
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
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,
re
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,
re
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,
re
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,
re
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,
re
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,
re
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,
re
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,
re
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,
re
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
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-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-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-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-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 59C
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-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-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 5
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-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 3
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 59C
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
Your message dated Mon, 23 Jul 2012 15:02:25 +
with message-id
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: /etc/fex/fup.pl
to be marked as done.
This mea
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
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-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-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 5
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 91A
-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 unde
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.
loca
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
from ocfs2interface.console import ma
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: http://bugs.debian
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.
-
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.
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
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.
Processing commands for cont...@bugs.debian.org:
> fixed 681475 4.7.1-5
Bug #681475 {Done: Matthias Klose } [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 '4.7.1-5'
Mark
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 discus
1 - 100 of 133 matches
Mail list logo
