rdiff-backup-fs is marked for autoremoval from testing

2017-05-07 Thread Debian testing autoremoval watch
rdiff-backup-fs 1.0.0-4 is marked for autoremoval from testing on 2017-05-23 It is affected by these RC bugs: 858316: rdiff-backup-fs: segmentation fault on i386

Bug#849784: lomoco: udev support broken, missing file /lib/udev/udev.lomoco

2017-05-07 Thread Gunnar Hjalmarsson
This issue was reported in Ubuntu as well via , and I proposed a fix there (please find the debdiff attached to this message). -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj diff -Nru lomoco-1.0.orig/debian/changelog lomoco-1.0/debian/changelog --- lo

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel
activating the NXError reporting we got filenamenxs.h5 5 ERROR: cannot open file: filenamenxs.h5 0 and looking for this errormessage, we found it in the napi5.c file NXstatus NX5open(CONSTCHAR *filename, NXaccess am, NXhandle* pHandle) { hid_t attr1,ai

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel
Herethe code ofthismethod /**/ static NXstatus NXinternalopen(CONSTCHAR *userfilename, NXaccess am, pFileStack fileStack); /*--*/ NXstatus NXopen(

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel
in the napi.h files we saw this. define CONCAT(__a,__b) __a##__b/* token concatenation */ #ifdef __VMS #define MANGLE(__arg) __arg #else #define MANGLE(__arg) CONCAT(__arg,_) #endif #define NXopen MANGLE(nxiopen) /** * Open a NeXus fi

fwsnort_1.6.5-3_amd64.changes ACCEPTED into unstable

2017-05-07 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 07 May 2017 11:47:15 +0200 Source: fwsnort Binary: fwsnort Architecture: source all Version: 1.6.5-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Axel Beckert Description: fwsno

Bug#861999: marked as done (fwsnort: Doesn't remove firewall rules on package purge)

2017-05-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 May 2017 12:04:00 + with message-id and subject line Bug#861999: fixed in fwsnort 1.6.5-3 has caused the Debian Bug report #861999, regarding fwsnort: Doesn't remove firewall rules on package purge to be marked as done. This means that you claim that the problem has

Processing of fwsnort_1.6.5-3_amd64.changes

2017-05-07 Thread Debian FTP Masters
fwsnort_1.6.5-3_amd64.changes uploaded successfully to localhost along with the files: fwsnort_1.6.5-3.dsc fwsnort_1.6.5-3.debian.tar.xz fwsnort_1.6.5-3_all.deb fwsnort_1.6.5-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel
Let's instrument the code print filename, mode, _ref(self.handle) status = nxlib.nxiopen_(filename,mode,_ref(self.handle)) print status $ python bug.py filenamenxs.h5 5 0

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel
Hello here the napi code which cause some trouble. # Convert open mode from string to integer and check it is valid if mode in _nxopen_mode: mode = _nxopen_mode[mode] if mode not in _nxopen_mode.values(): raise ValueError, "Invalid open mode %s",str(mode)

Bug#861999: fwsnort: Doesn't remove firewall rules on package purge

2017-05-07 Thread Axel Beckert
Package: fwsnort Version: 1.6.5-1 Severity: important Hi, while working on the recent RC bug in fwsnort (#860164) I noticed that all the firewall rules created by fwsnort are not removed upon purging the package. But since the package does not create them automatically and they're only created i