Bug#499795: HylaFAX+
package: hylafax-server severity: serious (Chris intends to upgrade it from wishlist to serious, for reasons, see below) Giuseppe, Remi, Phillipp, I'm writing you about this excellent Bug that Phillip Kempgen filed in 2008, why isn't HylaFAX+ included in debian? Giuseppe you had question about what makes HylaFAX+ so much better, and I've got the answers for you... Short version: I nominate you Giuseppe to make HylaFAX+ 5.5.6 available as a deb package in the main debian repo. Long version: The most recent version 5.5.6 was released April 2015, existing since 2005 as free open source code available on sourceforce. HylaFAX+ has more up to date features, performance improvements, and bugs fixes than the Hylafax 6.0.6 (released 2012) that you currently offer. The projects are probably 95% similar, they forked in 2005, but in 2012 Hylafax got into a leapfrog race on version numbers vs Hylafax+ 5.5.6. HylaFAX+ is superior because of many enhancements and bug fixes. For example it solves a longstanding issue of incompatibility with color and grayscale faxes. It produces compatible tiff and pdf pages, while Hylafax 6.0.6 can't (due to a complicated bug about ITULab colorspace unable to be understood/converted by libtiff and libjpeg, and those 2 package developers despite receiving patches, unable to change their code without causing breakage elsewhere, thus forcing a manual patch and recompile from source of not only libtiff and libjpeg but also of many other dependent packages on the system, which is totally ridiculous/unfeasible, and this has been stuck that way in hylafax for about ten years since 2005.). HylaFAX+ solved this bug by enlisting LittleCMS developer Marti Maria to solve this problem without the image degradation from having to decompress and re-compress the jpeg image of the page. Everyone who is aware of the two packages, installs Hylafax+. You should at least offer both Hylafax, and Hylafax+, packages, and let either be installed, obviously marked as conflicts with the other one, as you'd mentioned. As promised, here is a page with the list of bugfixes and performance improvements that HylaFAX+ has over HylaFAX: http://hylafax.sourceforge.net/docs/hylafax-differences.php * 1. support for sending and receiving color faxes (without patching libraries) <http://hylafax.sourceforge.net/docs/hylafax-differences.php#colorfaxes> * 2. simplified default faxrcvd, notify, and pollrcvd scripts for easier customization <http://hylafax.sourceforge.net/docs/hylafax-differences.php#mailscripts> * 3. faxq batching support was not needlessly rewritten and includes greater protection against resource overutilization <http://hylafax.sourceforge.net/docs/hylafax-differences.php#nofaxqrewrite> * 4. extended presentation of CallID <http://hylafax.sourceforge.net/docs/hylafax-differences.php#callidpresentation> * 5. intelligent real-time format compression conversion (RTFCC) <http://hylafax.sourceforge.net/docs/hylafax-differences.php#intelligentrtfcc> * 6. ModemSetOriginCmd, ModemDialCmd, FAXNAME job parameter, and -e "name" and -u "number" sendfax options <http://hylafax.sourceforge.net/docs/hylafax-differences.php#modemsetorigincmd> * 7. enhanced and improved fax image preparation <http://hylafax.sourceforge.net/docs/hylafax-differences.php#faximage> * 8. numerous faxmail enhancements <http://hylafax.sourceforge.net/docs/hylafax-differences.php#faxmail> * 9. etc/FaxAccounting reliable event hook, particularly for adding xferfaxlog data to a database <http://hylafax.sourceforge.net/docs/hylafax-differences.php#faxaccounting> * 10. xferfaxlog extensions (SUBMIT records and jobinfo field) <http://hylafax.sourceforge.net/docs/hylafax-differences.php#xferfaxlog> * 11. inbound faxes can be configured to utilize info files for automated fax parameters configuration <http://hylafax.sourceforge.net/docs/hylafax-differences.php#inbounduseofinfo> * 12. support for taglines using UTF-8 fonts <http://hylafax.sourceforge.net/docs/hylafax-differences.php#utf8taglines> * 13. More feature support (i.e. JBIG, JPEG) in the Class 2/2.0/2.1 driver <http://hylafax.sourceforge.net/docs/hylafax-differences.php#class2featuresupport> * 14. StaggerCalls feature for faxq <http://hylafax.sourceforge.net/docs/hylafax-differences.php#staggercalls> * 15. place non-ready ModemReadyState onto modem status string and add "exempt" option <http://hylafax.sourceforge.net/docs/hylafax-differences.php#modemreadystate> * 16. direct LDAP authentication support (without PAM) <http://hylafax.sourceforge.net/docs/hylafax-differences.php#ldapauth> * 17. -nointeractive option for faxsetup and faxaddmodem (like configure) <http://hylafax.sourceforge.net/docs/hylafax-differences.php#nointeractive> * 18. no JobControlWait option <http://hylafax.sourceforge.net/docs/hylafax-differences.php#jobcontrolwait> -Chris Coleman
Bug#680160: samba4: passdb/pdb_interface.c:157(make_pdb_method_name) No builtin nor plugin backend for samba4 found
Package: samba4 Version: 4.0.0~beta2+dfsg1-1 Severity: normal Dear Maintainer, On installing samba4 I have encountered the above (shown below in more detail when starting samba, in my smb.conf I have: passdb backend = samba4 Error: [2012/07/03 21:08:51, 0] smbd/server.c:1051(main) smbd version 3.6.5 started. Copyright Andrew Tridgell and the Samba Team 1992-2011 [2012/07/03 21:08:51, 0] param/loadparm.c:7969(lp_do_parameter) Ignoring unknown parameter server role [2012/07/03 21:08:51.081368, 0] param/loadparm.c:7969(lp_do_parameter) Ignoring unknown parameter server role [2012/07/03 21:08:51.118966, 0] param/loadparm.c:7209(service_ok) WARNING: No path in service IPC$ - making it unavailable! [2012/07/03 21:08:51.147307, 0] smbd/server.c:1107(main) standard input is not a socket, assuming -D option [2012/07/03 21:08:51.150523, 0] passdb/pdb_interface.c:157(make_pdb_method_name) No builtin nor plugin backend for samba4 found [2012/07/03 21:08:51.152413, 0] lib/util.c:1117(smb_panic) PANIC (pid 5723): pdb_get_methods_reload: failed to get pdb methods for backend samba4 [2012/07/03 21:08:51.155165, 0] lib/util.c:1221(log_stack_trace) BACKTRACE: 0 stack frames: [2012/07/03 21:08:51.162305, 0] lib/fault.c:372(dump_core) dumping core in /var/log/samba/cores/smbd I also recieve this error on starting the server: root@server:~# /etc/init.d/samba4 restart [ ok ] Stopping Samba 4 daemon: samba. [] Starting Samba 4 daemon: samba/usr/sbin/samba: /usr/lib/arm-linux-gnueabi/libwbclient.so.0: no version information available (required by /usr/lib/arm-linux-gnueabi/samba/libauth4.so) .. ok I initially tried an upgrade from samba3, however ultimately just provisioned samba with the following command: /usr/share/samba/setup/provision \ --realm=karumbo.local.com --domain=KARUMBO \ --adminpass=SOMEPASSWORD --server-role=dc Which completed succesfully and created a bare bones smb.conf below: # Global parameters [global] server role = active directory domain controller workgroup = KARUMBO realm = karumbo.local netbios name = SERVER passdb backend = samba4 [netlogon] path = /var/lib/samba/sysvol/karumbo.local/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.0.4 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages samba4 depends on: ii debconf [debconf-2.0] 1.5.44 ii libasn1-8-heimdal 1.6~git20120403+dfsg1-2 ii libattr1 1:2.4.46-8 ii libbsd00.4.0-1 ii libc6 2.13-33 ii libcomerr2 1.42.4-3 ii libdcerpc-server0 4.0.0~beta2+dfsg1-1 ii libdcerpc0 4.0.0~beta2+dfsg1-1 ii libgcc11:4.6.1-4 ii libgensec0 4.0.0~beta2+dfsg1-1 ii libhdb9-heimdal1.6~git20120403+dfsg1-2 ii libkdc2-heimdal1.6~git20120403+dfsg1-2 ii libkrb5-26-heimdal 1.6~git20120403+dfsg1-2 ii libldb11:1.1.6-1 ii libndr-standard0 4.0.0~beta2+dfsg1-1 ii libndr04.0.0~beta2+dfsg1-1 ii libpopt0 1.16-7 ii libpython2.7 2.7.3~rc2-2.1 ii libroken18-heimdal 1.6~git20120403+dfsg1-2 ii libsamba-credentials0 4.0.0~beta2+dfsg1-1 ii libsamba-hostconfig0 4.0.0~beta2+dfsg1-1 ii libsamba-util0 4.0.0~beta2+dfsg1-1 ii libsamdb0 4.0.0~beta2+dfsg1-1 ii libsmbclient-raw0 4.0.0~beta2+dfsg1-1 ii libtalloc2 2.0.7+git20120207-1 ii libtdb11.2.10-2 ii libtevent0 0.9.16-1 ii python 2.7.3~rc2-1 ii python-dnspython 1.10.0-1 ii python-samba 4.0.0~beta2+dfsg1-1 ii samba-dsdb-modules 4.0.0~beta2+dfsg1-1 ii samba4-common-bin 4.0.0~beta2+dfsg1-1 ii tdb-tools 1.2.10-2 Versions of packages samba4 recommends: ii attr1:2.4.46-8 ii bind9 1:9.8.1.dfsg.P1-4.1 ii bind9utils 1:9.8.1.dfsg.P1-4.1 ii ldb-tools 1:1.1.6-1 Versions of packages samba4 suggests: pn phpldapadmin none pn samba-gtk none pn swat2 none -- debconf information: samba4/realm: KARUMBO.LOCAL samba4/upgrade-from-v3: true samba4/server-role: domain controller -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603759: procps broken by new gnu make 3.82
Package: procps Version: 1:3.2.8-9 Severity: normal Tags: patch GNU Make 3.82 no longer sorts lists of filenames when expanding automatic variables or wildcards. Filenames are now returned in filesystem order. This new behaviour has broken the procps Makefile. There are two problems: 1) In proc/Makefile at line 177: -include */module.mk When that wildcard is expanded as ps/module.mk proc/module.mk, the makefile fails to link ps/ps (because LIBPROC is empty). 2) In proc/sysinfo.c and proc/version.c: The functions init_libproc() and init_Linux_version() are both declared with __attribute__((constructor)). So they are automatically called before main(). And since they are not prioritized and will be in separate object files, their order of execution is determined by the order in which their object files are linked. Which is now less predictable. init_libproc() uses the value of the variable linux_version_code which is initialized by init_Linux_version(). When init_libproc() is called before init_Linux_version(), hackery for legacy and non-Linux systems is called upon (old_Hertz_hack()) because linux_version_code is still zero (and = LINUX_VERSION(2, 4, 0)). And then we get messages like: Unknown HZ value! (67) Assume 100. https://bugs.gentoo.org/show_bug.cgi?id=303120 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603759: Forgot to attach the patch.
procps-fixes-for-gnu-make-3.82.patch Description: Binary data
Bug#603759: procps broken by new gnu make 3.82
On 17 November 2010 01:06, Craig Small csm...@debian.org wrote: They haven't been that way since January 2010. I made one of them a constructor and the other is called by it. Then I'm looking at old code. Where do you keep it now? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
