Your message dated Sun, 21 Oct 2012 06:47:28 +
with message-id
and subject line Bug#691019: fixed in docbookwiki 0.9.2-6
has caused the Debian Bug report #691019,
regarding docbookwiki: modifies shipped files in /usr/share/docbookwiki/
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> # FTBFS (but built successfully in the past)
> severity 690841 serious
Bug #690841 [cups-filters] cups-filters: FTBFS on !linux
Severity set to 'serious' from 'grave'
> found 690841 cups-filters/1.0.20-1
Bug #690841 [cups-filters] cups-filters: FT
#691067 may not be a good example as closer examination revealed that it might
be an unrelated issue.
However the point stands as due to crash with libdvdread4/4.2.0+20120521-2 we
had to declare Breaks in Handbrake packaging:
Breaks:
# handbrake segfaults with libdvdread4_4.2.0+2012052
Your message dated Sun, 21 Oct 2012 05:17:39 +
with message-id
and subject line Bug#689780: fixed in yate 4.1.0-1~dfsg-3
has caused the Debian Bug report #689780,
regarding yate-qt4: modifies conffiles during squeeze2wheezy upgrade (policy
10.7.3): /etc/yate/providers.conf
to be marked as don
Your message dated Sun, 21 Oct 2012 05:17:39 +
with message-id
and subject line Bug#683229: fixed in yate 4.1.0-1~dfsg-3
has caused the Debian Bug report #683229,
regarding Binary package "yate" doesn't ship any module at all
to be marked as done.
This means that you claim that the problem ha
Your message dated Sun, 21 Oct 2012 05:17:39 +
with message-id
and subject line Bug#680818: fixed in yate 4.1.0-1~dfsg-3
has caused the Debian Bug report #680818,
regarding yate: FTBFS: build-dependency not installable: libopenh323-dev
to be marked as done.
This means that you claim that the
Processing control commands:
> block -1 by 689967
Bug #691074 [gcc-doc] gcc-doc: Depends on docs for wrong gcc version
691074 was not blocked by any bugs.
691074 was not blocking any bugs.
Added blocking bug(s) of 691074: 689967
--
691074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691074
Control: block -1 by 689967
Hi Samuel,
On 10/21/2012 09:54 AM, Samuel Bronson wrote:
> Package: gcc-doc
> Version: 5:3
> Severity: serious
>
> Dear Maintainer,
> I've noticed that gcc-doc is still depending on the documentation for
> the aging GCC 4.4...
The packages in unstable are updated t
On Sun, Oct 21, 2012 at 11:57 AM, Osamu Aoki wrote:
> Hi,
>
> On Sun, Oct 21, 2012 at 01:21:02AM +0200, Laurent Bigonville wrote:
>> Package: gir1.2-ibus-1.0
>> Version: 1.4.1-7
>
> For wheezy ... Hmmm depends is missing true.
>
>> Severity: serious
>
> Anyway, looks like I need to deal this in u
Processing commands for cont...@bugs.debian.org:
> #yate (4.1.0-1~dfsg-3) UNRELEASED; urgency=low
> #
> # * Cleanup debian/rules - restores missing modules
> #- Fixes "Do not call dh_installinit twice" (Closes: #680563)
> #- Fixes "package "yate" doesn't ship any module at all" (Closes: #
Hi,
On Sun, Oct 21, 2012 at 01:21:02AM +0200, Laurent Bigonville wrote:
> Package: gir1.2-ibus-1.0
> Version: 1.4.1-7
For wheezy ... Hmmm depends is missing true.
> Severity: serious
Anyway, looks like I need to deal this in unstable :-)
I just noticed ... Asias, why you dropped g-ir-scanner
Package: motion
Version: 3.2.12-3.2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Possibly my recent upgraded to my Debian system.
* What exactly did you do (or n
Package: gcc-doc
Version: 5:3
Severity: serious
Dear Maintainer,
I've noticed that gcc-doc is still depending on the documentation for
the aging GCC 4.4...
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimenta
Processing commands for cont...@bugs.debian.org:
> severity 688574 serious
Bug #688574 {Done: Daniel Baumann }
[libdvdread4] libdvdread4: lack of __USE_GNU causes crashes in dvd_reader.c ,
patch included
Severity set to 'serious' from 'normal'
> tags 688574 wheezy
Bug #688574 {Done: Daniel Bauma
Your message dated Sun, 21 Oct 2012 00:02:38 +
with message-id
and subject line Bug#660488: fixed in miredo 1.2.3-1.1
has caused the Debian Bug report #660488,
regarding miredo: FTBFS `pkglibdir' is not a legitimate directory for `PROGRAMS'
to be marked as done.
This means that you claim that
Your message dated Sun, 21 Oct 2012 00:02:38 +
with message-id
and subject line Bug#660488: fixed in miredo 1.2.3-1.1
has caused the Debian Bug report #660488,
regarding FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is n
Processing commands for cont...@bugs.debian.org:
> # RFS waiting on debian-mentors
> tags 684962 + pending
Bug #684962 [l2tp-ipsec-vpn] l2tp-ipsec-vpn: removes files that were installed
by another package: /etc/ipsec.{conf, secrets}, /etc/xl2tpd/xl2tpd.conf
Added tag(s) pending.
> thanks
Stopping
Package: gir1.2-ibus-1.0
Version: 1.4.1-7
Severity: serious
Tags: patch
Hi,
The depends field of gir1.2-ibus-1.0 is empty because dh_girepository
has not been called during build.
The "gir" sequence must be called (--with gir) during build.
See the attached patch.
Cheers
Laurent Bigonville
Your message dated Sat, 20 Oct 2012 23:46:43 +0200
with message-id <50831bc3.4050...@debian.org>
and subject line Re: Bug#691061: python3.3-minimal: illegal instruction on
raspberry pi
has caused the Debian Bug report #691061,
regarding python3.3-minimal: illegal instruction on raspberry pi
to be
Control: tags -1 + patch
On Mon, 2012-09-10 at 15:33 +0200, Elena ``of Valhalla'' wrote:
> Yes, I've been working to add the switch via the above feature,
> but it is breaking other tests, and I didn't have time to
> fix those further failures yet.
I've had a look at this and made a patch for u
Processing control commands:
> tags -1 + patch
Bug #682648 [src:python-gnupg] python-gnupg: FTBFS: test hangs for 60 mins
Added tag(s) patch.
--
682648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCR
Processing commands for cont...@bugs.debian.org:
> forwarded 691032
> http://mail-archives.apache.org/mod_mbox/perl-embperl/201210.mbox/%3C20121020195317.GQ67641%40ZEDAT.FU-Berlin.DE%3E
Bug #691032 {Done: Salvatore Bonaccorso } [libembperl-perl]
libembperl-perl: FTBFS: -m32 is i386/amd64 only
Bu
On 2012-10-20 22:24, Lisandro Damián Nicanor Pérez Meyer wrote:
> Believe it or not, this is trigerred by a loop dependency between two
> packages
> and apt gets confused. So far we could not find another way of solving it
> (and
I really like the analysis and you have my full support for solv
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.
to be marked as done.
This means that you cl
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.
to be marked as done.
This means that you cl
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.
to be marked as done.
This means that you cl
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.
to be marked as done.
This means that you cl
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS: -m32 is i386/amd64 only
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS: -m32 is i386/amd64 only
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS: -m32 is i386/amd64 only
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS: -m32 is i386/amd64 only
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS: -m32 is i386/amd64 only
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS: -m32 is i386/amd64 only
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 20 Oct 2012 20:49:10 +
with message-id
and subject line Bug#691032: fixed in libembperl-perl 2.5.0~rc2-2
has caused the Debian Bug report #691032,
regarding libembperl-perl: FTBFS: -m32 is i386/amd64 only
to be marked as done.
This means that you claim that the problem
Package: python3.3-minimal
Version: 3.3.0-1
Severity: grave
Justification: renders package unusable
It is a raspberry py with raspbian. I have manually downloaded the following
packages, and tried to install them with dpkg:
libpython3.3-minimal_3.3.0-1_armhf.deb libpython3.3-stdlib_3.3.0-1_armhf
Your message dated Sat, 20 Oct 2012 19:47:34 +
with message-id
and subject line Bug#688608: fixed in glipper 2.4-2
has caused the Debian Bug report #688608,
regarding glipper: incomplete debian/copyright
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi,
On Wed, Oct 17, 2012 at 06:18:02PM +0200, Thijs Kinkhorst wrote:
> > We sent the first batch to the Alioth users, and are quite happy that,
> > among the 213 members of the Alioth webwml group we contacted, 104
> > members already sent us back the agreement, and 44 other persons (who
> > alrea
Processing commands for cont...@bugs.debian.org:
> tags 685632 + patch
Bug #685632 [liquidsoap] liquidsoap: missing versioned depend on
libcamomile-ocaml-data
Added tag(s) patch.
> tags 685632 + pending
Bug #685632 [liquidsoap] liquidsoap: missing versioned depend on
libcamomile-ocaml-data
Added
tags 685632 + patch
tags 685632 + pending
thanks
Dear maintainer,
I've prepared an NMU for liquidsoap (versioned as 1.0.1+repack1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key
Processing control commands:
> block -1 by 610184
Bug #691046 [installation-reports] installation-reports: manual partitioning
for GPT does not suggest a BIOS Boot Partition
691046 was not blocked by any bugs.
691046 was not blocking any bugs.
Added blocking bug(s) of 691046: 610184 and 620390
-
Source: expeyes
Version: 3.0.1-1
Severity: serious
Justification: fails to build from source
expeyes's control file lists all build dependencies in
Build-Depends-Indep, so (automated) builds in minimalistic environments
geared for building only architecture-dependent packages are failing:
fa
Processing commands for cont...@bugs.debian.org:
> tags 687403 + patch
Bug #687403 [src:libio-async-loop-epoll-perl] libio-async-loop-epoll-perl:
FTBFS: test failed
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
687403: http://bugs.debian.org
On Sun, Oct 14, 2012 at 10:58:42AM +0100, Steve McIntyre wrote:
>Just uploaded an NMU to implement the TC requirements. Here's the debdiff
And here's an updated debdiff for a new upload to fix man pages.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep
Processing commands for cont...@bugs.debian.org:
> # evolution got berserk and kept sending the message numerous times.
> # apologies for the spamming
> merge 691032 691034 691035 691036 691037 691038 691039 691040 691041
Bug #691032 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd64 onl
tag 691032 + pending
thanks
Some bugs in the libembperl-perl package are closed in revision
3ffc15eca3798b7eb14da4cc8c234d4b3c5724fb in branch 'master' by
Salvatore Bonaccorso
The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libembperl-perl.git;a=commitdiff;h=3ff
Processing commands for cont...@bugs.debian.org:
> tag 691032 + pending
Bug #691032 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd64 only
Bug #691034 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd64 only
Bug #691035 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd
Your message dated Sat, 20 Oct 2012 16:02:44 +
with message-id
and subject line Bug#683649: fixed in extplorer 2.1.0b6+dfsg.3-4
has caused the Debian Bug report #683649,
regarding extplorer: creates world writable directory /var/lib/extplorer/ftp_tmp
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> merge 691032 691040 691041 691042 691043
Bug #691032 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd64 only
Bug #691034 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd64 only
Bug #691035 [libembperl-perl] libembperl-perl: FTB
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Processing commands for cont...@bugs.debian.org:
> merge 691032 691034 691035 691036 691037 691038 691039
Bug #691032 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd64 only
Bug #691034 [libembperl-perl] libembperl-perl: FTBFS: -m32 is i386/amd64 only
Bug #691035 [libembperl-perl] libemb
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
Package: libembperl-perl
Version: 2.5.0~rc2-1
Severity: serious
Tags: patch
According to
https://buildd.debian.org/status/package.php?p=libembperl-perl&suite=sid
the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not
being available on those platforms as a valid gcc flag. Please re
On Sat, 20 Oct 2012 10:39:12 +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'wheezy', then the upgrade to 'sid' fails.
Wrong key, this time with attachment ...
--
.''`. Homepage: http://info.comodo.
Control: tag -1 + patch
On Sat, 20 Oct 2012 10:39:12 +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'wheezy', then the upgrade to 'sid' fails.
>
> >From the attached log (scroll to the bottom...):
>
>
Processing control commands:
> tag -1 + patch
Bug #691015 [conserver-client] conserver-client: fails to upgrade from testing:
Can't locate Tie/Hash/NamedCapture.pm in @INC
Added tag(s) patch.
--
691015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691015
Debian Bug Tracking System
Contact o
I wonder about uploading
http://anonscm.debian.org/gitweb/?p=users/corsac/security/xlockmore.git;a=commitdiff;h=6617b7e99df5f6196e2f1a5133becd1a039ee8f4
which would completely remove the xlockmore-gl package and only keep the
blank mode in xlockmore.
That wouldn't fix other bugs (PAM ones for exa
Hello
I often use pidgin-sipe at work. Version 1.13.1-2 is able to connect to
Microsfot lync server provided the workaround mentioned in #681593 is used.
Since a workaround is available, the 'grave' severity of this bug is not
justified. I'll downgrade it to important unless someone objects (wi
Your message dated Sat, 20 Oct 2012 12:33:06 +
with message-id
and subject line Bug#680059: fixed in revelation 0.4.13-1.2
has caused the Debian Bug report #680059,
regarding revelation: FPM exporter doesn't encrypt password files
[CVE-2012-3818]
to be marked as done.
This means that you cla
Your message dated Sat, 20 Oct 2012 11:00:14 +
with message-id
and subject line Bug#690287: fixed in ibus 1.4.99.20120917-2
has caused the Debian Bug report #690287,
regarding libibus-1.0-0 ships libibus-1.0.so.5
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 20 Oct 2012 11:00:09 +
with message-id
and subject line Bug#688847: fixed in libav 6:9~beta1-1
has caused the Debian Bug report #688847,
regarding libav: multiple CVEs in ffmpeg/libav
to be marked as done.
This means that you claim that the problem has been dealt with.
Hello Andrea, Daniel,
can you see a kernel stacktrace anywhere? Are you in a GUI when the system
freezes, i.e. running some desktop? In that case you probably won't be
able to see the stacktrace, but you could try to CTRL-ALT-Fx to some of
your consoles and maybe be lucky. I have not investiga
Hi Tim,
I wonder if there is any news on this bug on your side?
The situation in Debian is that the Release team has the 'beast'
package on its removal list and requests a solution for this problem
/before/ next Friday (Oct 26). If we do not manage to upload some fix
for compilation with gcc 4.7,
Your message dated Sat, 20 Oct 2012 10:00:10 +
with message-id
and subject line Bug#681361: fixed in node 0.3.2-7.2
has caused the Debian Bug report #681361,
regarding Rename /usr/sbin/node to /usr/sbin/ax25-node with depended legacy
package
to be marked as done.
This means that you claim th
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was deb...@abeckmann.de).
> usertags 691019 piuparts
There were no usertags set.
Usertags are now: piuparts.
> close 688231
Bug #688231 [acgvision-agent] acgvision-agent:
Package: docbookwiki
Version: 0.9.2-5
Severity: serious
Hi,
with the SVN repository moved to /var a few more modifications of
shipped files are uncovered:
1m27.4s ERROR: FAIL: debsums reports modifications inside the chroot:
/usr/share/docbookwiki/content/SVN/book_list
/usr/share/docbookwiki
Hi Michael, and thanks for your very detailed bugreport, it's greatly
appreciated.
Without much insight into your specific problem, would the (quite invasive)
attached patch solve your problem ? It's the "backport" of latest upstream
CUPS libusb backend over 1.5.3-2.3 .
Le samedi, 20 octobre 2
Processing commands for cont...@bugs.debian.org:
> found 656586 2.3.2-1
Bug #656586 [routino-www] fails to purge - rmdir: failed to remove
'/var/lib/routino/data': No such file or directory
Marked as found in versions routino/2.3.2-1.
> found 672160 1.85
Bug #672160 [console-setup] console-setup:
Processing control commands:
> severity -1 serious
Bug #688712 [wesnoth] wesnoth: needs to handle symlink to directory change of
/usr/share/doc/wesnoth
Severity set to 'serious' from 'important'
> affects -1 + wesnoth-core wesnoth-music
Bug #688712 [wesnoth] wesnoth: needs to handle symlink to di
Source: ptex-bin
Version: 3.1.11+0.04b-0.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + jmpost jbibtex-bin
Hi,
jmpost and jbibtex-bin are no longer installable in sid due to a
dependency on the no longer available libkpathsea5.
The ptex-bin binary p
Processing control commands:
> affects -1 + jmpost jbibtex-bin
Bug #691017 [src:ptex-bin] ptex-bin: what's the future of jmpost and
jbibtex-bin?
Added indication that 691017 affects jmpost and jbibtex-bin
--
691017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691017
Debian Bug Tracking Sys
Source: libphone-ui-dev
Followup-For: Bug #690150
Control: found -1 1:0.0.1+git20110825-2.1
Hi,
that NMU makes /usr/share/doc/libphone-ui-dev a dangling symlink. The
correct target would probably be libphone-ui-20110825.
0m47.2s ERROR: Command failed (status=1): ['chroot',
'/tmp/piupartss/tmp3h
Processing control commands:
> found -1 1:0.0.1+git20110825-2.1
Bug #690150 {Done: Jonathan Wiltshire } [libphone-ui-dev]
libphone-ui-dev: missing copyright file after upgrade from squeeze
Marked as found in versions libphone-ui/1:0.0.1+git20110825-2.1; no longer
marked as fixed in versions libp
Package: conserver-client
Version: 8.1.18-2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'wheezy', then the upgrade to 'sid' fails.
>From the attached log (scro
Hi,
a Brasero flaw was found in the course of Debian bug 688229.
It would provide an explanation for the problems which are
described here. Especially it is involved when burning directly
to optical media and not involved when writing ISO filesystems
to hard disk.
The problem was introduced in oc
Hi Christoph
On Fri, Oct 19, 2012 at 11:16:51AM +0200, Christoph Berg wrote:
> thanks for the patch, but I don't think it is valid. If you remove the
> dacs module, but leave the apache config there, apache will not be
> happy. I guess the best would be to call a2dismod to remove the
> symlink whe
Your message dated Sat, 20 Oct 2012 07:17:36 +
with message-id
and subject line Bug#690992: fixed in libmongo-client 0.1.6.1-3
has caused the Debian Bug report #690992,
regarding Missing dependency on libglib2.0-dev
to be marked as done.
This means that you claim that the problem has been dea
Processing commands for cont...@bugs.debian.org:
> block 690236 by 690237
Bug #690236 [libjs-swfupload] libjs-swfupload ftbfs in testing/unstable on i386
690236 was not blocked by any bugs.
690236 was not blocking any bugs.
Added blocking bug(s) of 690236: 690237
> --
Stopping processing here.
Pl
Processing commands for cont...@bugs.debian.org:
> found 690992 0.1.5-1
Bug #690992 [libmongo-client-dev] Missing dependency on libglib2.0-dev
Marked as found in versions libmongo-client/0.1.5-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
690992: http://bugs.
86 matches
Mail list logo
