Your message dated Sat, 17 Nov 2012 03:17:53 +
with message-id
and subject line Bug#577635: fixed in cm-super 0.3.4-7.1
has caused the Debian Bug report #577635,
regarding cm-super-minimal: ships /usr/share/texmf/doc as a directory, not a
link
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> found 693470 ruby-capistrano-ext/1.2.1-2
Bug #693470 [capistrano,ruby-capistrano-ext] ruby-capistrano-ext and
capistrano: error when trying to install together
Marked as found in versions ruby-capistrano-ext/1.2.1-2.
> thanks
Stopping processing
Your message dated Sat, 17 Nov 2012 01:32:43 +
with message-id
and subject line Bug#693487: fixed in ettercap 1:0.7.5-5
has caused the Debian Bug report #693487,
regarding ettercap-text-only, ettercap-graphical: copyright file missing after
upgrade (policy 12.5)
to be marked as done.
This me
Processing commands for cont...@bugs.debian.org:
> affects 693211 + bootcd
Bug #693211 [coreutils] coreutils: file conflict with realpath
Bug #693488 [coreutils] coreutils: fails to upgrade from 'testing' - trying to
overwrite /usr/share/man/man1/realpath.1.gz
Added indication that 693211 affects
> dpkg intentionally does not replace directories with symlinks and
> vice versa.
Okay, I'll add postinst stanzas.
But do you know *why* dpkg has this behaviour? Just curious, as it
seems on the face of it somewhat odd.
--Barak.
--
To UNSUBSCRIBE, emai
Processing commands for cont...@bugs.debian.org:
> reassign 693211 coreutils
Bug #693211 [coreutils,realpath] coreutils: file conflict with realpath
Bug reassigned from package 'coreutils,realpath' to 'coreutils'.
No longer marked as found in versions coreutils/8.20-1 and realpath/1.17.
Ignoring r
This patch will fix this issue (integer overflow, file size is stored in
an `int`):
https://github.com/casta/bcrypt/commit/a6c6fea6bce0166bb7e6d440d7a75941f662e02b
However memory requirements will make it practically impossible to
bcrypt a 13GB file, however bcrypt will now fail gracefully with
Andreas Beckmann wrote:
> dpkg: error processing /var/cache/apt/archives/coreutils_8.20-1_amd64.deb
> (--unpack):
>trying to overwrite '/usr/share/man/man1/realpath.1.gz', which is also in
> package realpath 1.17
Thank you for the report. This was already reported in Bug#693211 and
theref
I think (but am not certain) that this is actually a dpkg bug.
The /usr/share/doc/ettercap-text-only directory in the old version has
become a symbolic link to /usr/share/doc/ettercap-common in the new
version. This is explicitly allowed in Policy 12.5,
/usr/share/doc/package may be a symbolic
On 2012-11-17 01:45, Barak A. Pearlmutter wrote:
> I suppose I could add logic to the postinst script to detect and
> repair this,
That's the usual way to fix this, there have been several of these bugs
been fixed recently.
> but it really does seem like dpkg's job to install the
> contents of th
Bob Proulx wrote:
> Ralf Treinen wrote:
> > /usr/bin/realpath
> > /usr/share/man/man1/realpath.1.gz
>
> Thank you for the report. This was already reported in Bug#693488 and
> therefore I am merging the reports.
Oops. While crosschecking the reports I reversed them and responded
to the oppo
Processing commands for cont...@bugs.debian.org:
> forcemerge 693488 693211
Bug #693488 [coreutils] coreutils: fails to upgrade from 'testing' - trying to
overwrite /usr/share/man/man1/realpath.1.gz
Unable to merge bugs because:
package of #693211 is 'coreutils,realpath' not 'coreutils'
Failed to
forcemerge 693488 693211
thanks
Ralf Treinen wrote:
> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
>
> /usr/bin/realpath
> /usr/share/man/man1/realpath.1.gz
Thank you for the report
Processing control commands:
> affects -1 + python3-pyatspi2
Bug #693490 [python3-pyatspi] python3-pyatspi: fails to upgrade from 'testing'
- trying to overwrite /usr/lib/python3/dist-packages/pyatspi/enum.py
Added indication that 693490 affects python3-pyatspi2
--
693490: http://bugs.debian.or
Package: python3-pyatspi
Version: 2.5.3+dfsg-2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-pyatspi2
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to
Package: coreutils
Version: 8.20-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + bootcd
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it
Processing control commands:
> affects -1 + bootcd
Bug #693488 [coreutils] coreutils: fails to upgrade from 'testing' - trying to
overwrite /usr/share/man/man1/realpath.1.gz
Added indication that 693488 affects bootcd
--
693488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693488
Debian Bug
Hi,
I have just removed ensembl from the archive: in its current form it is
not distributable by Debian and there has been no progress or even a
timeframe. It also has several other open RC bugs, some of which have
been open for quite some time.
Once the current problems are fixed, ensembl can of
Your message dated Sat, 17 Nov 2012 00:28:59 +
with message-id
and subject line Bug#693023: Removed package(s) from unstable
has caused the Debian Bug report #686692,
regarding harvestman: FTBFS: TypeError: type.__init__() takes no keyword
arguments
to be marked as done.
This means that you
Your message dated Sat, 17 Nov 2012 00:26:36 +
with message-id
and subject line Bug#693358: Removed package(s) from unstable
has caused the Debian Bug report #693358,
regarding RM: libpam-rsa -- RoST; unmaintained, buggy and dangerous
to be marked as done.
This means that you claim that the p
Your message dated Sat, 17 Nov 2012 00:26:39 +
with message-id
and subject line Bug#693358: Removed package(s) from unstable
has caused the Debian Bug report #693087,
regarding segfault in xscreensaver, screen revealed
to be marked as done.
This means that you claim that the problem has been
Package: ettercap-text-only,ettercap-graphical
Version: 1:0.7.5-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade from squeeze to wheezy, which is a violation of
Policy 12.5:
http:
Your message dated Sat, 17 Nov 2012 00:25:58 +
with message-id
and subject line Bug#692906: Removed package(s) from unstable
has caused the Debian Bug report #652591,
regarding noflushd: Crash with linux-image-2.6.32-5-686 (version 2.6.32-38)
to be marked as done.
This means that you claim th
Processing commands for cont...@bugs.debian.org:
> found 691465 1:0.7.4.2-1
Bug #691465 {Done: b...@debian.org (Barak A. Pearlmutter)} [ettercap-common]
serious issues
Marked as found in versions ettercap/1:0.7.4.2-1.
> notfound 691465 0.7.4.2-1
Bug #691465 {Done: b...@debian.org (Barak A. Pearlm
I'm pretty sure the bug must exist in libfm, not pcmanfm itself. Libfm
implements widgets and also the filesystem operations.
I'll bet the error exists in the following place: the function
_fm_file_ops_job_copy_file in the file
libfm-0.1.17/src/job/fm-file-ops-job-xfer.c
This function is 370 lin
On 2012-10-12 13:23:20 +0200, Paul Menzel wrote:
> Am Dienstag, den 20.12.2011, 01:49 +0100 schrieb Vincent Lefevre:
> > I've burnt a data DVD with brasero and got no errors (except that the
> > DEBUG messages in the terminal were inconsistant with the dialog: when
> > a DEBUG message said X %, it
I'll be looking into this bug this weekend. I'm not sure about the
severity at this stage - need to see how CleanUpFormatIdxUsed is
actually used.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgppn7OjseNuT.pgp
Description: PGP signature
Package: openstack-dashboard
Version: 2012.1.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
Thanks all. I will definitely get these uploaded this weekend.
--
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:
> found 651720 23
Bug #651720 [partman-zfs] new ZFS installs completely broken in Wheezy/Sid
Marked as found in versions partman-zfs/23.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
651720: http://bugs.debian.org
* Steve Langasek , 2012-11-16, 08:29:
A sysvinit upload has been rejected by the archive because of the tag
maintainer-script-removes-device-files (see below). This lintian check
is in error; the maintainer script removes /dev/shm, which is not a
device file. Furthermore, the code already exi
Processing commands for cont...@bugs.debian.org:
> severity 693360 normal
Bug #693360 [release.debian.org] RM: libpam-rsa -- RoST; unmaintained, buggy
and dangerous
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
693360: h
Some additional information, probably it helps:
As stated above, when system freezes power consumption rises by some 30
watts. I now checked under normal operating conditions and it turns out
that this value is precisely the same when 2 cores (out of 4) run under
full load (checked with seti@home)
On Tue, Nov 13, 2012 at 10:12:15AM +1100, Tony Cook wrote:
> The only way I can see to fix this from my end is to have Imager build
> a separate libimager.so.ABI[1].
>
> For that to be useful though, I suspect packagers would need to
> extract that libimager.so.ABI into a new package, which might
Processing commands for cont...@bugs.debian.org:
> block 693470 by 692540
Bug #693470 [capistrano,ruby-capistrano-ext] ruby-capistrano-ext and
capistrano: error when trying to install together
693470 was blocked by: 693466
693470 was not blocking any bugs.
Added blocking bug(s) of 693470: 692540
On Mon, Nov 12, 2012 at 04:24:56PM -0500, Michael Gilbert wrote:
> On Mon, Nov 12, 2012 at 4:12 PM, gregor herrmann wrote:
> > On Mon, 12 Nov 2012 15:46:13 -0500, Michael Gilbert wrote:
> >> > And I'm also not sure that your NMU for libimager-qrcode-perl is
> >> > correct; if I understand this co
Processing commands for cont...@bugs.debian.org:
> unarchive 664852
Bug #664852 {Done: Cajus Pollmeier } [gosa] gosa: fails to
purge: invoke-rc.d: unknown initscript, /etc/init.d/apache2 not found
Unarchived Bug 664852
> found 664852 2.6.11-3+squeeze2
Bug #664852 {Done: Cajus Pollmeier } [gosa] g
Processing commands for cont...@bugs.debian.org:
> severity 693359 normal
Bug #693359 [release.debian.org] RM: libpam-rsa -- RoST; unmaintained, buggy
and dangerous
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
693359: h
Processing commands for cont...@bugs.debian.org:
> block 693470 by 693466
Bug #693470 [capistrano,ruby-capistrano-ext] ruby-capistrano-ext and
capistrano: error when trying to install together
693470 was not blocked by any bugs.
693470 was not blocking any bugs.
Added blocking bug(s) of 693470: 6
On Thu, 2012-11-15 at 19:32 +0100, Ondřej Surý wrote:
> I think the best course of action is to contact debian-release team
> and ask for an exception (e.g. in Cc:).
>
> Unless we get upstream to change the license (which is unlikely), it's
> too late in release cycle for any radical change (like
Package: capistrano,ruby-capistrano-ext
Version: capistrano/2.12.0-1
Version: ruby-capistrano-ext/1.2.1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2012-11-16
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file
Processing commands for cont...@bugs.debian.org:
> retitle 693359 RM: libpam-rsa -- RoST; unmaintained, buggy and dangerous
Bug #693359 [release.debian.org] RM: pam-rsa -- RoST; unmaintained, buggy and
dangerous
Changed Bug title to 'RM: libpam-rsa -- RoST; unmaintained, buggy and
dangerous' fro
After some more testing i've discovered another way to trigger a
segfault by pressing SPACE while watching a replay. All in all this
function is way to buggy and i think it's better to disable it for now.
I've updated the patch and also the README.Debian file so that the users
know why this functi
Processing commands for cont...@bugs.debian.org:
> retitle 693358 RM: libpam-rsa -- RoST; unmaintained, buggy and dangerous
Bug #693358 [ftp.debian.org] RM: pam-rsa -- RoST; unmaintained, buggy and
dangerous
Changed Bug title to 'RM: libpam-rsa -- RoST; unmaintained, buggy and
dangerous' from 'R
On 2012-11-16 Martijn van Brummelen wrote:
[...]
> How about contacting upstream? I can try
> that, or perhaps you already had contact with Werner Koch?
Hello Martijn,
I have hasked Werner about it.
http://permalink.gmane.org/gmane.comp.encryption.gpg.libgcrypt.devel/2623
Werner said this about
Attaching debdiff patches for both squeeze and wheezy/experimental
packages.
diff -Nru tiff-3.9.4/debian/changelog tiff-3.9.4/debian/changelog
--- tiff-3.9.4/debian/changelog 2012-10-05 17:35:50.0 -0400
+++ tiff-3.9.4/debian/changelog 2012-11-16 12:42:26.0 -0500
@@ -1,3 +1,10 @@
+t
On 2012-11-16 Martijn van Brummelen wrote:
> I rebuild Wheezy's version of libgcrypt11_1.5.0-3 with the
> patch(no_global_init_during_thread_callbacks.diff) from Ubuntu.
> I can confirm the new patched version of libgcrypt solves this problem,
> and I am able to use sudo again.
> Can someone rev
Package: bcrypt
Version: 1.1-6
Severity: critical
Justification: causes serious data loss
Hi,
bcrypt doesn't handle at least some files (possibly large ones?).
This source file
13G -rw-r--r-- 1 matthew matthew 13G Nov 16 16:01 CTS-2012-11.tar.bz2
when encrypted with bcrypt -cr, results in on
Processing commands for cont...@bugs.debian.org:
> tags 692614 + wheezy-ignore
Bug #692614 [src:mono] mono: non-free file in upstream tarball ("The Software
shall be used for Good, not Evil")
Added tag(s) wheezy-ignore.
> tags 692619 + wheezy-ignore
Bug #692619 [src:yui] non-free files in upstrea
tags 692614 + wheezy-ignore
tags 692619 + wheezy-ignore
tags 692624 + wheezy-ignore
tags 692625 + wheezy-ignore
tags 692627 + wheezy-ignore
tags 692628 + wheezy-ignore
tags 692629 + wheezy-ignore
tags 692630 + wheezy-ignore
tags 692631 + wheezy-ignore
tags 692613 + wheezy-ignore
tags 692615 + wheez
Package: lintian
Version: 2.5.10.2
Severity: serious
A sysvinit upload has been rejected by the archive because of the tag
maintainer-script-removes-device-files (see below). This lintian check is
in error; the maintainer script removes /dev/shm, which is not a device
file. Furthermore, the code
Your message dated Fri, 16 Nov 2012 14:47:50 +
with message-id
and subject line Bug#693431: fixed in mpdris2 0.3-2
has caused the Debian Bug report #693431,
regarding mpdris2: fails to build from source: missing build-dep on intltool
to be marked as done.
This means that you claim that the pr
None of these bugs (or any bugs above "normal") apply to the version of
Chrony in Sid. They could all by fixed by migrating that version (the
current upstream release) to Wheezy but as it is frozen that is not
possible unless the release team decides to make an exception. That is
entirely up to t
On Fri, Nov 16, 2012 at 02:47:20PM +0100, Joachim Wiedorn wrote:
>
> > Given the very sorry state of the package (the RC bug is just the tip of
> > the iceberg). If it is not possible releasing Wheezy with a newer version
> > with an improved packaging in terms of quality, thing I doubt is possib
Hello Ana,
Ana Guerrero wrote on 2012-11-16 14:09:
> I mailed the current maintainer of chrony back when I did the NMU asking
> him about the status of the package. I sugested him orphaning the package
> or filing a RFA bug, but all he said is he would look at the package soon.
> When he did it w
Hi,
I mailed the current maintainer of chrony back when I did the NMU asking
him about the status of the package. I sugested him orphaning the package
or filing a RFA bug, but all he said is he would look at the package soon.
When he did it was way to late for the release...
Given the very sorry
Your message dated Fri, 16 Nov 2012 11:47:27 +
with message-id
and subject line Bug#633799: fixed in getmail4 4.32.0-2
has caused the Debian Bug report #633799,
regarding getmail causes irrecoverable mail corruption when using mbox
to be marked as done.
This means that you claim that the prob
Package: mpdris2
Version: 0.3-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch raring
mpdris2 fails to build as follows:
debian/rules build
dh build --with autoreconf,python2 --parallel
dh_testdir -O--parallel
dh_autoreconf -O
Processing commands for cont...@bugs.debian.org:
> found 681457 1:2.2.1-1
Bug #681457 [libaudit0] libaudit: does not actually support ARM, breaks linked
binary like readahead
There is no source info for the package 'libaudit0' at version '1:2.2.1-1' with
architecture ''
Unable to make a source v
On Fri, Nov 16, 2012 at 02:39:08AM +, Debian Bug Tracking System wrote:
> version: 9.01~dfsg-1
>> This does not happen with upstream 8.71. If I build the package without
>> 0940_Merge_gs_2_colors_branch.patch, the problem goes away and the job
>> completes
>> in 5-6 seconds. It happens every t
On 11/16/2012 10:29 AM, Adam Conrad wrote:
> Package: libltc
> Version: 1.0.3-1
> Severity: serious
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu raring ubuntu-patch
>
> The attached patch should be fairly self-evident, I hope. This
> fixes the FTBFS on PowerPC (
Package: libltc
Version: 1.0.3-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu raring ubuntu-patch
The attached patch should be fairly self-evident, I hope. This
fixes the FTBFS on PowerPC (and fixes a bug in general on all
big-endian arches, though so
Hi,
Timo Juhani Lindfors writes:
> However, the debdiff seems to be for squeeze and not for wheezy? Are in
> fact both squeeze and wheezy affected by the bugs? If yes, we need two
> uploads.
sorry, I didn't notice the sid.diff file. I built, tested (quite
briefly), signed and uploaded to unstabl
Jan,
please, keep the trolling out of this list. Your comment was neither
constructive nor helpful.
Ondřej Surý
On 16. 11. 2012, at 9:45, Jan Wagner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/15/2012 07:00 PM, Michael Biebl wrote:
>> They seem to think it's a self-mad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/15/2012 07:00 PM, Michael Biebl wrote:
> They seem to think it's a self-made, Debian-only problem.
Isn't it a common attitude of this upstream team to get other people
responsible for issues?
Just my 2 cents, Jan.
- --
Never write mail to , yo
65 matches
Mail list logo
