Bug#1022749: python3.10: python 3.10 incompatible with setuptools>=60.0.0

Package: python3.10 Severity: normal X-Debbugs-Cc: jep...@gmail.com Dear Maintainer, Hi! Apologies to bringing this to your attention as a bystander, but I've become aware of an incompatibility between setuptools >= 60.0.0 and debian's python package. I'm not actually using an affected version

Bug#1012789: Can you check if Img works at all?

Thanks for tryting LinuxCNC on aarch64. I don't know of anyone presently using such a configuration. As far as the "undefined symbol" message: Please check whether in "wish", it works to "package require Img" or whether the same error occurs. If it's the same error then may point to a general

Bug#1001904: mesaflash: Maintainer address bounces

Is there a specific sender address that it will suffice to whitelist, or does the list need to permit mail from any address, regardless of subscription status?

Bug#849258: Lerna is unlikely to pass license review

Lerna has added restrictions to its former MIT license. I think these restrictions make it unlikely that Lerna can be incorporated into debian's "main" archive. For more info, including the (proposed and apparently accepted) license text, see https://github.com/lerna/lerna/pull/1616

Bug#879101: ITP: node-uniqid -- Unique ID Generator

On Thu, Oct 19, 2017 at 05:39:00PM +0530, Pirate Praveen wrote: > * URL : http://github.com/adamhalasz/diet-uniqid/ Link is 404'd. Not sure if you intend https://github.com/adamhalasz/uniqid/ or if there was supposed to be a "diet" version that is depended on. Jeff

Bug#863620: There's an upstream patch now (8.0 and master)

The patch for 8.0 almost applies to 7.12, at least when the revised test is dropped. (the rest is trivial #include differences) https://sourceware.org/bugzilla/show_bug.cgi?id=21555#c3 It does appear to fix the problem as I understand it and described it back at comment #27 It would be great if

Bug#869379: Images created without pulling in from 'updates' and 'security' repos

On Sat, Jul 22, 2017 at 09:43:40PM +0100, Phil Wyett wrote: > Images created without pulling in from 'updates' and 'security' repos. > > This leaves images very out of date. Images should have all the latest > packages. In linuxcnc's stretch image, I compensate for this in customise.sh by adding

Bug#867282: live-wrapper: Lacks dependency on squashfs-tools

Package: live-wrapper Version: 0.6+nmu1 Severity: serious Justification: Policy 3.5 Dear Maintainer, Hi. after installing live-wrapper with --no-install-recommends, it does not function properly, eventually issuing an error that /tmp/.../live can not be found. I believe that this is because it

Bug#863620: gdb: "Error re-setting breakpoint" *when executable is compiled with PIE*

Dear maintainer, I noticed this problem as soon as I upgraded to Debian Stretch on a couple of my machines. While preparing an update to this bug report, I discovered additional information: It is a long-standing bug or limitation in gdb that relates to PIE executables. However, as PIE is the

Bug#864239: node-rimraf: can remove files outside the intended tree

Package: node-rimraf Version: 2.5.4-2 Severity: important Tags: upstream Dear Maintainer, I was inspecting the source to node-rimraf. I believe the code in node-rimraf is unsafe if an adversary can manipulate the contents of the directory tree to be removed, making it unsuitable for use on

Bug#863985: ITP: node-chownr -- Javascript implementation of chown -R.

This package appears to have a TOCTOU bug, which can trick it into descending into unintended trees if a non-symlink is replaced by a symlink at a critical moment: fs.lstat(pathChild, function(er, stats) { if (er) return cb(er) if (!stats.isSymbolicLink())

Bug#863105: ITP: minecraft-installer -- Unofficial way to easily install game

On Sun, May 21, 2017 at 05:22:41PM -0300, Carlos Donizete Froes wrote: > * License : Shell > Programming Lang: BSD-2-Clause These two lines are transposed

Bug#861208: ITP: node-minimalistic-crypto-utils -- Minimalistic tools for JS crypto modules

On Tue, Apr 25, 2017 at 11:44:39PM +0200, Bastien ROUCARIES wrote: > This a dependency of browserify, a tool that create self contained module > that run in browser contextg ^ trivial typo, should be "context"

Bug#857713: ITP: librandom123 -- parallel random numbers library

On Tue, Mar 14, 2017 at 09:20:37AM +0100, Andreas Tille wrote: ... > vectorize and parallelize well (each generator can produce at least 264 > independent streams), have long periods (the period of each stream is at > least 2128), require little or no memory or state, and have excellent write

Bug#837067: Help requested: Packages which FTBFS randomly

On Tue, Feb 21, 2017 at 05:32:34PM +0100, Santiago Vila wrote: > On Fri, 17 Feb 2017, Jeff Epler wrote: > > Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, upgraded > > to > > debian testing, I tried sbuilding libsecret. So far, 2/2 builds failed.

Bug#837067: Help requested: Packages which FTBFS randomly

On Fri, Feb 17, 2017 at 12:16:16PM +0100, Santiago Vila wrote: > Can anyone here reproduce any of the following *two* bugs? > (Using sbuild in a single-CPU machine) > > 837067 1.000 libsecret Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, upgraded to debian testing, I tried

Bug#850672: ITP: gnome-shell-extension-show-ip -- Shows the urrent private or public IP address in the GNOME Shell status drop-down menu

On Mon, Jan 09, 2017 at 11:16:48AM +0200, Kyle Robbertze wrote: > Description : A GNOME Shell Extesion that shows the urrent private or ^ insert "c" > public IP address in the status drop-down menu Aside from

Bug#842796: libc recently more aggressive about pthread locks in stable ?

[resending with correct Cc:] I believe that similar bugs have been afflicting hurd and kfreebsd debian ports for some time. In retrospect, it's too bad these reports weren't given more attention, because it could have made things better for Linux platforms as well. :-/ see e.g.,

Bug#827902: Is ISC License considered DFSG free?

At least one package in Debian main, xombrero, has files listed in debian/copyright as "License: ISC". (it is orphaned, but the reasons are unrelated to the license) http://metadata.ftp-master.debian.org/changelogs/main/x/xombrero/unstable_copyright Jeff

Bug#839035: ITP: node-is-extglob -- Node module to return true if a string is an extglob

On Wed, Sep 28, 2016 at 02:26:07AM +, Potter, Tim (HPE Linux Support) wrote: > * Package name: node-is-extglob > Version : 2.0.0 > Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert) > * URL : https://github.com/jonschlinkert/is-extglob After

Bug#834783: Acknowledgement (python-tk: string value 'y' converted to string value 'True')

Of course, I meant this bug is affecting debian testing ('stretch'), not 'squeeze'.

Bug#834783: python-tk: string value 'y' converted to string value 'True'

Package: python-tk Version: 2.7.11-2 Severity: normal Dear Maintainer, I am a developer/maintainer of LinuxCNC, a free software CNC control. Our users have encountered the following problem running on Debian Squeeze, and I have distilled a test case. The code works as expected on Debian Jessie

Bug#827555: ITP: circle -- Show byte statistics as an ascii circle graph

On Fri, Jun 17, 2016 at 07:38:22PM +0200, Roberto S. Galende wrote: > Package: wnpp > Severity: wishlist > Owner: "Roberto S. Galende" > > Package name: circle > Version : 2.2-1 > Upstream Author : "Roberto S. Galende"

Bug#776886: patch

tags -1 +patch thanks I encountered this error, and found a patch on the internet to fix it. I belive the critical item is the memmove change. I think the other two parts of the patch are unrelated and should be treated as such. https://bugs.mageia.org/show_bug.cgi?id=11880 It was necessary to

Bug#801530: segfault is null-pointer dereference

.. and the exciting-looking address is apparently a typical load address for the ssh binary. # testing with the larger key attached to the initial comment (gdb) run Starting program: /home/jepler/src/openssh-6.7p1/ssh-keygen -l -f /home/jepler/Downloads/key.trigger.pub Program received signal

Bug#478269: Incompatible db version is not a spambayes bug

The basic error seems to be Invalid argument -- /var/spambayes/spambayes.messageinfo.db: unsupported hash version: 9 This is a duplicate of the (closed) bug #469770. That bug suggested: The Debian version of Python 2.5 was originally built using Berkely DB 4.6. Due to problems

Bug#789564: Compatibility with newer python-lockfile

tags 789564 + patch thanks As far as I can tell, spambayes uses lockfile.FileLock, a name which is still provided by python-lockfile-0.10.2-2. As such it doesn't need to be changed. However, that said, I have produced a patch that follows the gratuitous renaming of the main lockfile API. diff

Bug#376114: I believe this bug is fixed (tested in 1.1b1-1)

I put the headers from message #5 in 'testmessage2' and ran $ sb_filter testmessage2 | grep Content-Type Content-Type: multipart/related; as you can see, the (possibly incorrect) Content-Type header is unchanged in the output of spambayes. In the full output, the X-Spambayes headers are

Bug#781161: dovecot-core: Can't log in via imap on kFreeBSD amd64 (Auth request missing a file descriptor)

Package: dovecot-core Version: 1:2.2.15-1 Severity: important Dear Maintainer, After upgrading my Debian kFreeBSD machine from Wheezy to Jessie, dovecot imap stopped working. The version from experiemental was also broken in the same way. After I attempt to sign in with valid information, the

Bug#779467: dpkg: start-stop-daemon sometimes exits with _cpu_tick_frequency: no such symbol on kFreeBSD

using it. + + -- Jeff Epler jep...@unpythonic.net Sun, 01 Mar 2015 19:42:38 -0600 + dpkg (1.17.23) unstable; urgency=low [ Guillem Jover ] diff -Nru dpkg-1.17.23/utils/start-stop-daemon.c dpkg-1.17.23+local3/utils/start-stop-daemon.c --- dpkg-1.17.23/utils/start-stop-daemon.c 2014-12-13 16:07

Bug#779467: dpkg: start-stop-daemon sometimes exits with _cpu_tick_frequency: no such symbol on kFreeBSD

Package: dpkg Version: 1.17.23+local1 Severity: important Tags: patch On a Debian Jessie kFreeBSD system, start-stop-daemon sometimes exits with an odd error: $ sudo service nfsd restart start-stop-daemon: _cpu_tick_frequency: no such symbol The specific command invocation which was reliably

Bug#776814: Patch: use more portable sysconf for memory sizing

. * Port to debian kfreebsd (Closes: #776814) Author: Jeff Epler jep...@unpythonic.net --- Bug-Debian: https://bugs.debian.org/776814 Forwarded: no Reviewed-By: name and email of someone who approved the patch Last-Update: 2015-02-03 --- vsearch-1.0.7+dfsg.orig/src/arch.cc +++ vsearch-1.0.7+dfsg/src

Bug#545970: nis: FTBFS on GNU/kFreeBSD (network-manager is linux specific)

Package: nis Followup-For: Bug #545970 I have modified nis to build on debian kFreeBSD. -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: kfreebsd-amd64

Bug#750870: Proposed OpenSSL linking exception

In the thread ITP: libressl, the OpenSSL linking exception was discussed. This is of great interest to people who would think that LibreSSL may be a long-term viable fork of OpenSSL, because many statements of the OpenSSL exception do not explicitly to permit linking with modified and/or renamed

Bug#628383: [kfreebsd-*] test failure: test-secmem

Apparently freebsd kernels 9.2 and later have security.bsd.unprivileged_mlock, which appears to default to permitted. http://www.freebsd.org/cgi/man.cgi?query=mlocksektion=2manpath=FreeBSD+9.2-RELEASE http://marc.info/?l=freebsd-archm=134617193210756 Is this test failure happening with kernel

Bug#728446: Use libusb2 on kfreebsd

--- apcupsd-3.14.10/debian/changelog +++ apcupsd-3.14.10/debian/changelog @@ -1,3 +1,10 @@ +apcupsd (3.14.10-2.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Use libusb2 on kfreebsd so that USB UPSes work (Closes #728446) + + -- Jeff Epler jep...@unpythonic.net Sat, 01 Feb 2014 10:41:06

Bug#736946: g++-mingw-w64-i686: crash in ostream with ios::fixed and large numbers due to Windows snprintf behavior

+++ gcc-mingw-w64-8+nmu1/debian/changelog 2014-01-28 09:52:09.0 -0600 @@ -1,3 +1,10 @@ +gcc-mingw-w64 (8+nmu1) stable; urgency=low + + * Non-maintainer upload. + * Fix crash in ostream with ios::fixed and large numbers (PR28891) + + -- Jeff Epler jep...@dsndata.com Tue, 28 Jan

Bug#736202: undeterministic output when running egrep repeatedly with the same input

Could it be http://www.freebsd.org/cgi/query-pr.cgi?pr=164445 ? It looks like that fix from reply 3 is not in kernel 9.0-10+deb70 which is what I'm running (but I have Wheezy userspace, so I haven't reproduced a problem either) Jeff -- To UNSUBSCRIBE, email to

Bug#726664: radvd FTBFS on kfreebsd

upload. + * Use autoreconf, as the kfreebsd patch requires rebuilding configure + + -- Jeff Epler jep...@unpythonic.net Thu, 17 Oct 2013 15:38:15 -0500 + radvd (1:1.9.1-1.1) unstable; urgency=low * Non-maintainer upload with maintainer approval. diff -Nru radvd-1.9.1/debian/control radvd

Bug#686250: I believe this is a duplicate bug

I beliieve that this bug #686250 is duplicated by the fixed #688574 (not in wheezy, alas). I was readily able to observe a crash in DVD_Open when using vlc on a directory containing a copy of the contents of a DVD when I ran with 4.2.0+20120521-2 but not when I ran with 4.2.0+20130219-1, and the

Bug#707733: pygobject: FTBFS on kfreebsd

OK, this seems crazy to me but I feel obliged to note it: When I build 3.8.1-3 in /usr/src or /tmp/wat, I can observe the failure when I subsequently 'make check' in build-2.7/tests. When I build it in /tmp or /tmp/wat/frugal-bonasfrarfsarfasrfasrf/pygobject-3.8.1 I do not. However, I also note

Bug#707733: pygobject: FTBFS on kfreebsd

valgrind (helgrind) on linux (sid amd64 chroot on wheezy amd64) didn't turn up anything that looked too useful. There were a number of diagnostics of this general form: ==12158== Lock at 0x603E5C0 was first observed ==12158==at 0x4C2EB32: pthread_mutex_init (in

Bug#707733: pygobject: FTBFS on kfreebsd

Another bug that may be similar: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671785 In that bug I remark that a problem with pthread_mutex_unlock can be observed on linux with valgrind --tool=helgrind. I haven't tried to determine whether it's a similar problem here, but it might be worth

Bug#703061: mongodb: Enable building on kfreebsd

I hope to spend some time looking into this matter this weekend. Thanks for the pointer to the source repository. Jeff signature.asc Description: Digital signature

Bug#703061: mongodb: Enable building on kfreebsd

I got a chance to look at it today and it was pretty quick to make 2.4 build. I made a pair of pull requests on github. Please let me know if you would rather have them as attachments on this bug. Jeff signature.asc Description: Digital signature

Bug#705126: Tried but failed to reproduce

Since the reported trigger was an ssh flood, I tried ssh -T -o 'PreferredAuthentications hostbased' localhost (which on my system will result in a quick failed ssh because hostbased authentication is not enabled in the server) in a tight, parallelized loop with this construct: for i in

Bug#631788: is this fixed by moving the db_version block earlier?

I encountered this problem (albeit on ubuntu 10.04) and saw that the package successfully installed when the stanza . /usr/share/debconf/confmodule db_version 2.0 was moved above the stanza which calls deluser/adduser. However, I don't know what other impact this would have on the

Bug#702729: Info received (Bug#702729: valgrind: build on kfreebsd-amd64)

seen when running firefox under valgrind. It is cumulative with my initial patch and probably should be squashed in. . Author: Jeff Epler jep...@unpythonic.net Bug-Debian: http://bugs.debian.org/702729 --- valgrind-3.8.1.orig/coregrind/m_syswrap/syswrap-freebsd.c +++ valgrind-3.8.1/coregrind

Bug#702729: Info received (Bug#702729: valgrind: build on kfreebsd-amd64)

of the failing steps being: /usr/lib/libreoffice/program/../ure-link/bin/javaldx \ -env:INIFILENAME=vnd.sun.star.pathname:/usr/lib/libreoffice/program/redirectrc which would fail to load a library it searched for relative to the executab.e Author: Jeff Epler jep...@unpythonic.net Bug-Debian: http

Bug#702729: valgrind: build on kfreebsd-amd64

OK, I think understand how you are suggesting the patches need to be structured within the debian/ patches directory. On Sat, Mar 16, 2013 at 09:13:18PM +0100, Carlos Alberto Lopez Perez wrote: PS: I think the dependence for the binary package valgrind on libc6-dbg should be changed to

Bug#702729: valgrind: build on kfreebsd-amd64

On Thu, Mar 14, 2013 at 06:30:43PM +0100, Alessandro Ghedini wrote: I'll have a look as soon as I have some free time. I was also thinking that the patch may be applied only in the kfreebsd builds, so it wouldn't interfere with the linux builds. That sounds great, but I do not yet have the

Bug#703061: mongodb: Enable building on kfreebsd

I guess this provides some level of confidence in the result. Please consider my patch for a future release of mongodb. Thanks, Jeff Epler jep...@unpythonic.net -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture

Bug#702729: Acknowledgement (valgrind: build on kfreebsd-amd64)

On top of my earlier patch, the Depends of the valgrind package must be modified for kfreebsd. I'm not sure this is entirely right, but something like: Depends: ${misc:Depends}, ${shlibs:Depends}, libc6-dbg [!kfreebsd-any], libc0.1-dbg [kfreebsd-any] Jeff -- To UNSUBSCRIBE, email to

Bug#701832: doxygen consistently segfaults on kfreebsd-i386 when building opendnssec documentation

On Sun, Mar 03, 2013 at 12:20:57PM +, Steven Chamberlain wrote: #5 0x000800d21f2c in *__GI___libc_free (mem=optimized out) at malloc.c:3736 ar_ptr = 0x800ff3240 p = optimized out #6 0x000800844a79 in gvFreeContext () from /usr/lib/libgvc.so.5 No symbol

Bug#698102: eglibc: initgroups changes egid on kfreebsd

Michael, For now it sounds like there's no consensus that this is a bug in initgroups(3) in eglibc or setgroups(2) in kfreebsd. If you're aware of this leading to a bug in a specific Debian package (particularly if it is a bug with a security impact), please file a bug against that package.

Bug#698102: eglibc: initgroups changes egid on kfreebsd

I've reworked the test program as follows: #include stdio.h #include stdlib.h #include unistd.h #define NGROUPS 32 void call() { gid_t groups[NGROUPS]; int ngroups = getgroups(NGROUPS, groups), i; printf(gid = %d egid = %d groups =,

Bug#698199: freebsd-utils: kdump incorrectly prints delivery of signals = 32

+ds1-9.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Improve reporting of signals = 32 + + -- Jeff Epler jepler@localhost Mon, 14 Jan 2013 20:44:54 -0600 + freebsd-utils (9.0+ds1-9) unstable; urgency=low [ Steven Chamberlain ] diff -Nru freebsd-utils-9.0+ds1/debian/patches

Bug#698200: gdb: Debugging threaded programs fails because of signal delivery problems

/changelog 2013-01-14 21:15:19.0 -0600 @@ -1,3 +1,10 @@ +gdb (7.4.1-3.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Fix gdb lockup when debugging pthread programs on kfreebsd-amd64 + + -- Jeff Epler jepler@localhost Mon, 14 Jan 2013 21:14:59 -0600 + gdb (7.4.1-3) unstable

Bug#696644: I think darktable assumes something pthreads does not guarantee

Control: tags -1 + upstream ... but I'm not sure. Basically, it appears that there's a race between setting a value in the main thread and reading it in another thread. The value is darktable.control-thread_res[threadid]. It's accessed in the created thread in dt_control_get_threadid_res and

Bug#671785: Workaround for kFreeBSD crash in reportbug

On Sun, Dec 30, 2012 at 05:34:10PM -0800, Christoph Egger wrote: However, I still believe that the problem is either in python-gtk2 or python-gtk2's FAQ advice on how to use gtk.gdk.threads_init(). Can you be a bit more verbose about that? Also the FAQ might well be right and what we are

Bug#685625: libgeom: may cause segfault of grub-probe

If it's a question of minimal impact to fix the specific crash that grub-probe encounters, then there are two more minimal ways to fix this specific problem that come to mind: replace reallocf with realloc---but in the unlikely case that realloc fails, it doesn't deallocate the argument (this is

Bug#696813: gdisk always reports 'The specified path is a character device!' on kFreeBSD

!' on kFreeBSD + + -- Jeff Epler jepler@localhost Thu, 27 Dec 2012 08:00:48 -0600 + gdisk (0.8.5-1) unstable; urgency=low * New upstream release diff -Nru gdisk-0.8.5/debian/patches/kfreebsd.diff gdisk-0.8.5/debian/patches/kfreebsd.diff --- gdisk-0.8.5/debian/patches/kfreebsd.diff1969-12-31

Bug#696618: redis: FTBFS on kfreebsd-amd64

would not be used +anyway + + -- Jeff Epler jepler@localhost Sun, 23 Dec 2012 18:07:16 -0600 + redis (2:2.4.14-1) unstable; urgency=low * New upstream release. diff -Nru redis-2.4.14/debian/control redis-2.4.14/debian/control --- redis-2.4.14/debian/control 2012-06-08 11:21:51.0

Bug#671785: Workaround for kFreeBSD crash in reportbug

; urgency=low + + * Non-maintainer upload. + * Avoid a kFreeBSD crash by telling python-gtk not to hook readline +Closes: #671785 + + -- Jeff Epler jepler@localhost Sat, 22 Dec 2012 10:35:25 -0600 + reportbug (6.4.3) unstable; urgency=low * reportbug/debbugs.py diff -Nru reportbug-6.4.3

Bug#685625: implicit declaration of function ‘reallocf’

It looks like this is the problem, and it exists repeatedly in freebsd-libs-9.0+ds1-7 geom_getxml.c: In function ‘geom_getxml’: geom_getxml.c:59:2: warning: implicit declaration of function ‘reallocf’ [-Wimplicit-function-declaration] geom_getxml.c:59:2: warning: return makes pointer from

Bug#685625: [PATCH] Re: Bug#685625: implicit declaration of function ‘reallocf’

silently +in the future + + -- Jeff Epler jep...@unpythonic.net Fri, 21 Dec 2012 13:20:44 -0600 + freebsd-libs (9.0+ds1-3) unstable; urgency=low [ Robert Millan ] diff -Nru freebsd-libs-9.0+ds1/debian/patches/implicit-declaration freebsd-libs-9.0+ds1/debian/patches/implicit-declaration

Bug#671785: Minimal Python script to reproduce the problem; evidence points at python-gtk2

.. happily, it allows the exclusion of reportbug as the cause of the problem and begins to point fairly squarely at python-gtk2. happening. Please consider reassigning to the python-gtk2 package. The mutex which is initialized in gtk.gdk.threads_init() is used (attempted to be unlocked) at the

Bug#685625: implicit declaration of function ‘reallocf’

[snipped astute observations about the size of the xml data being important] On Fri, Dec 21, 2012 at 10:02:45PM +, Steven Chamberlain wrote: And I'm worried about some of the other packages mentioned, where the error shows on kfreebsd-* or maybe hurd-*, but not on other arches. Should they

Bug#693510: Treat adaN devices as SCSI (cam) devices; improve detection

@@ -1,3 +1,12 @@ +parted (2.3-11.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Treat adaN devices as SCSI (cam) devices (Closes: #693510) + * Fill out the drive model information for ata adaN devices + * Fill out the physical sector size information for ata adaN devices + + -- Jeff

Bug#696119: `zpool status` incorrectly names raidz vdevs

Package: libzfs1 Version: 9.0-3 Severity: normal Tags: patch zpool status incorrectly prints raidz vdevs as -0 instead of raidz1-0, e.g. $ zpool status mpool pool: mpool state: ONLINE scan: scrub repaired 0 in 0h52m with 0 errors on Sun Dec 16 12:43:40 2012 config:

Bug#653929: Bug #696119 probably has the fix to this bug

Tags: patch Today I filed a bug about this same problem, having found this earlier report too late. I believe the patch on bug #696119 will address this problem (which is not seen on freebsd due to libc differences). As I'm a newbie at the debian bugtracker I'm not sure how to merge the two

Bug#653929: Bug #696119 probably has the fix to this bug

On Mon, Dec 17, 2012 at 02:24:42AM +, Steven Chamberlain wrote: Originally in #653929 it was said that this bug breaks GRUB in some way, and could prevent use of RAID-Z as a root filesystem; do you know if that is true? Unfortunately, I don't know the answer to this. I am booting from a

Bug#609845: ftp.debian.org: RM: imapsync -- RoM; author doesn't want us to distribute his program

I do not understand why you wish to remove from the debian archive software that debian users may rely on (as far as I can see from the original report, not everyone's use of the version Debian ships hits the reported problem), just because of a possible license problem in a *different version* of