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 if the program is actually used as intented, I think it's
less severe than e.g. piuparts reporting leftover files after purge.

On a first glance, simply calling "fwsnort --ipt-revert" in prerm
suffices, but then again, /usr/sbin/fwsnort might be no more there, if
the package was already removed, but not purged. Luckily, when looking
what this option actually does, I noticed that it boils down to the very
simple oneliner:

  grep -v FWSNORT /var/lib/fwsnort/fwsnort.save | iptables-restore

So I'll add this to the postrm script before deleting the fwsnort.save
file, calling it only if that file exists.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fwsnort depends on:
ii  debconf [debconf-2.0]   1.5.60
ii  iptables1.6.0+snapshot20161117-6
ii  libiptables-parse-perl  1.6-1
ii  libnet-rawip-perl   0.25-2+b3
ii  libnetaddr-ip-perl  4.079+dfsg-1+b1
pn  perl:any

Versions of packages fwsnort recommends:
pn  snort-rules-default  

fwsnort suggests no packages.

-- debconf information:
* fwsnort/download: true



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)

self.filename, self.mode = filename, mode
self.handle = c_void_p(None)
self._path = []
self._indata = False
status = nxlib.nxiopen_(filename,mode,_ref(self.handle))
if status == ERROR:
if mode in [ACC_READ, ACC_RDWR]:
op = 'open'
else:
op = 'create'
raise NeXusError, "Could not %s %s"%(op,filename)


Soit seems that the nxlib.nxiopen_ method return an error



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



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#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 been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
861999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 if the program is actually used as intented, I think it's
less severe than e.g. piuparts reporting leftover files after purge.

On a first glance, simply calling "fwsnort --ipt-revert" in prerm
suffices, but then again, /usr/sbin/fwsnort might be no more there, if
the package was already removed, but not purged. Luckily, when looking
what this option actually does, I noticed that it boils down to the very
simple oneliner:

  grep -v FWSNORT /var/lib/fwsnort/fwsnort.save | iptables-restore

So I'll add this to the postrm script before deleting the fwsnort.save
file, calling it only if that file exists.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fwsnort depends on:
ii  debconf [debconf-2.0]   1.5.60
ii  iptables1.6.0+snapshot20161117-6
ii  libiptables-parse-perl  1.6-1
ii  libnet-rawip-perl   0.25-2+b3
ii  libnetaddr-ip-perl  4.079+dfsg-1+b1
pn  perl:any

Versions of packages fwsnort recommends:
pn  snort-rules-default  

fwsnort suggests no packages.

-- debconf information:
* fwsnort/download: true
--- End Message ---
--- Begin Message ---
Source: fwsnort
Source-Version: 1.6.5-3

We believe that the bug you reported is fixed in the latest version of
fwsnort, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 861...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated fwsnort package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-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:
 fwsnort- Snort-to-iptables rule translator
Closes: 861999
Changes:
 fwsnort (1.6.5-3) unstable; urgency=medium
 .
   * QA upload.
   * Remove all fwsnort generated firewall rules upon purge.
 (Closes: #861999)
   * Fix debian/copyright syntax by using a separate License stanza.
Checksums-Sha1:
 d7845ee054c60e4a81c676e93e7f43b9559aabc6 1888 fwsnort_1.6.5-3.dsc
 7ca9da025b6794f3a0faedb31bd4677a8a15816d 7924 fwsnort_1.6.5-3.debian.tar.xz
 67e54cd52df50163a8eae224889a43158e1d4d94 62060 fwsnort_1.6.5-3_all.deb
 2db89200abef0d09e37f397e99500722738e9823 5516 fwsnort_1.6.5-3_amd64.buildinfo
Checksums-Sha256:
 e913fa4c0e8fae5acfbf579025ca85eb5c0f677f8197509c7c6e4201add48d65 1888 
fwsnort_1.6.5-3.dsc
 28fa98ccbe2fd0401cffa3e14167a1aedb82004fa40a9dba2741948b3f71576e 7924 
fwsnort_1.6.5-3.debian.tar.xz
 99debb305840597f9ced731e59a84433eab0858f76fdea648cf2ff331357aeae 62060 
fwsnort_1.6.5-3_all.deb
 9cbb181e20ffce834859c24882e09f66b359043584181796c93617121be0392d 5516 
fwsnort_1.6.5-3_amd64.buildinfo
Files:
 9144c4a4d47bf29203da5c0ea22deee1 1888 admin optional fwsnort_1.6.5-3.dsc
 0aff9b4c2b12e445ac2381bd7224d50e 7924 admin optional 
fwsnort_1.6.5-3.debian.tar.xz
 a9d3fce05727df4d9ee68b34809da9c1 62060 admin optional fwsnort_1.6.5-3_all.deb
 4a56da207a27fa1bc5fc4667f6b1c808 5516 admin optional 
fws

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:
 fwsnort- Snort-to-iptables rule translator
Closes: 861999
Changes:
 fwsnort (1.6.5-3) unstable; urgency=medium
 .
   * QA upload.
   * Remove all fwsnort generated firewall rules upon purge.
 (Closes: #861999)
   * Fix debian/copyright syntax by using a separate License stanza.
Checksums-Sha1:
 d7845ee054c60e4a81c676e93e7f43b9559aabc6 1888 fwsnort_1.6.5-3.dsc
 7ca9da025b6794f3a0faedb31bd4677a8a15816d 7924 fwsnort_1.6.5-3.debian.tar.xz
 67e54cd52df50163a8eae224889a43158e1d4d94 62060 fwsnort_1.6.5-3_all.deb
 2db89200abef0d09e37f397e99500722738e9823 5516 fwsnort_1.6.5-3_amd64.buildinfo
Checksums-Sha256:
 e913fa4c0e8fae5acfbf579025ca85eb5c0f677f8197509c7c6e4201add48d65 1888 
fwsnort_1.6.5-3.dsc
 28fa98ccbe2fd0401cffa3e14167a1aedb82004fa40a9dba2741948b3f71576e 7924 
fwsnort_1.6.5-3.debian.tar.xz
 99debb305840597f9ced731e59a84433eab0858f76fdea648cf2ff331357aeae 62060 
fwsnort_1.6.5-3_all.deb
 9cbb181e20ffce834859c24882e09f66b359043584181796c93617121be0392d 5516 
fwsnort_1.6.5-3_amd64.buildinfo
Files:
 9144c4a4d47bf29203da5c0ea22deee1 1888 admin optional fwsnort_1.6.5-3.dsc
 0aff9b4c2b12e445ac2381bd7224d50e 7924 admin optional 
fwsnort_1.6.5-3.debian.tar.xz
 a9d3fce05727df4d9ee68b34809da9c1 62060 admin optional fwsnort_1.6.5-3_all.deb
 4a56da207a27fa1bc5fc4667f6b1c808 5516 admin optional 
fwsnort_1.6.5-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAlkO9sQACgkQa+Zjx1o1
yXXaNRAAut/LI1p3tORVOxkNsdYmmVHXHxhgVft+Qi2SodfK00xqGIZtFcup4OY+
EJYTl/dh/1OXKYDSQh2siLjGvHAub0Uj+mobWqsSOdSJRCpkdsNxT8CNjmL4behJ
mYwQx6Xv9WVt9Y9vFf9agaQ15mUZ3F/54/EZNYeT106c6l1gZB4/62g3kNVw6bVz
G+UNUH+KBVlWKQhezlhpwipPpHVPsxE3WYvu7FMPYhtwpwuqW1WD9BtgTsYHowaw
xs4nrJ6lcafOkYOCoTbnKBB3e8BPoXfLCoq1gdLs1xas+UZHqrJqNxrOAmrNs5gD
OYA1MFb9ONl3AUiLBQ/C2FyrpKQBlh3hQU6U7c86AQrZUhlecB9SLZZId9M4/ouZ
3mal4OgS5lFXLfX55Ig2q5dsPO4X+32k2rOCEQhZxu/sUzhYr55Ztu/yUcXy76gc
ixo3EWGuhNKA9pGPhXqwCTUahARFFyfWNb5PndYsK7ZuWWFs4Sb3GOMYW7h6ZEFE
8SvBQHQ0D1J+a/zReBJq7rCSPnV7743gvapX4wqOcED+G1KW6+sPqsO+lXXV1Yv6
uSzRk8OJcbFgNT6P5Kl9Zu36p4HLhKmSq3dEDHDega1tWRBAej8bjHJkdJ0H2+kN
f5yQM/knmFUYHcBukug2CZ7m6MvN5Yoz1Kx3+l6KETJQHu1FP7g=
=0EoG
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



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 file.
   * NXopen honours full path file names. But it also searches
   * for files in all the paths given in the NX_LOAD_PATH environment variable.
   * NX_LOAD_PATH is supposed to hold a list of path string separated by the 
platform
   * specific path separator. For unix this is the : , for DOS the ; . Please 
note
   * that crashing on an open NeXus file will result in corrupted data. Only 
after a NXclose
   * or a NXflush will the data file be valid.
   * \param filename The name of the file to open
   * \param access_method The file access method. This can be:
   * \li NXACC__READ read access
   * \li NXACC_RDWR read write access
   * \li NXACC_CREATE, NXACC_CREATE4 create a new HDF-4 NeXus file
   * \li NXACC_CREATE5 create a new HDF-5 NeXus file
   * \li NXACC_CREATEXML create an XML NeXus file.
   * see #NXaccess_mode
   * Support for HDF-4 is deprecated.
   * \param pHandle A file handle which will be initialized upon successfull 
completeion of NXopen.
   * \return NX_OK on success, NX_ERROR in the case of an error.
   * \ingroup c_init
   */
extern  NXstatus  NXopen(CONSTCHAR * filename, NXaccess access_method, 
NXhandle* pHandle);


so we need to check in this method what is going on.



Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel
Herethe code ofthismethod

/**/
static NXstatus   NXinternalopen(CONSTCHAR *userfilename, NXaccess am, 
   pFileStack fileStack);
/*--*/
NXstatus   NXopen(CONSTCHAR *userfilename, NXaccess am, NXhandle *gHandle){
  int status;
  pFileStack fileStack = NULL;

  *gHandle = NULL;
  fileStack = makeFileStack();
  if(fileStack == NULL){
NXReportError("ERROR: no memory to create filestack");
  return NX_ERROR;
  }
  status = NXinternalopen(userfilename,am,fileStack);
  if(status == NX_OK){
*gHandle = fileStack;
  }

  return status;


so lets's see the internalopen


static NXstatus   NXinternalopen(CONSTCHAR *userfilename, NXaccess am, 
pFileStack fileStack)
{
return LOCKED_CALL(NXinternalopenImpl(userfilename, am, fileStack));
}



/*---*/
static NXstatus   NXinternalopenImpl(CONSTCHAR *userfilename, NXaccess am, 
pFileStack fileStack)
  {
int hdf_type=0;
int iRet=0;
NXhandle hdf5_handle = NULL;
pNexusFunction fHandle = NULL;
NXstatus retstat = NX_ERROR;
char error[1024];
char *filename = NULL;
int my_am = (am & NXACCMASK_REMOVEFLAGS);

/* configure fortify 
iFortifyScope = Fortify_EnterScope();
Fortify_CheckAllMemory();
*/

/*
  allocate data
*/
fHandle = (pNexusFunction)malloc(sizeof(NexusFunction));
if (fHandle == NULL) {
  NXReportError("ERROR: no memory to create Function structure");
  return NX_ERROR;
}
memset(fHandle, 0, sizeof(NexusFunction)); /* so any functions we miss are 
NULL */
   
/*
  test the strip flag. Elimnate it for the rest of the tests to work
*/
fHandle->stripFlag = 1;
if(am & NXACC_NOSTRIP){
  fHandle->stripFlag = 0;
  am = (NXaccess)(am & ~NXACC_NOSTRIP);
}
fHandle->checkNameSyntax = 0;
if (am & NXACC_CHECKNAMESYNTAX) {
fHandle->checkNameSyntax = 1;
am = (NXaccess)(am & ~NXACC_CHECKNAMESYNTAX);
}


if (my_am==NXACC_CREATE) {
  /* HDF4 will be used ! */
  hdf_type=1;
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATE4) {
  /* HDF4 will be used ! */
  hdf_type=1;   
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATE5) {
  /* HDF5 will be used ! */
  hdf_type=2;   
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATEXML) {
  /* XML will be used ! */
  hdf_type=3;   
  filename = strdup(userfilename);
} else {
  filename = locateNexusFileInPath((char *)userfilename);
  if(filename == NULL){
NXReportError("Out of memory in NeXus-API");
free(fHandle);
return NX_ERROR;
  }
  /* check file type hdf4/hdf5/XML for reading */
  iRet = determineFileType(filename);
  if(iRet < 0) {
snprintf(error,1023,"failed to open %s for reading",
 filename);
NXReportError(error);
free(filename);
return NX_ERROR;
  }
  if(iRet == 0){
snprintf(error,1023,"failed to determine filetype for %s ",
 filename);
NXReportError(error);
free(filename);
free(fHandle);
return NX_ERROR;
  }
  hdf_type = iRet;
}
if(filename == NULL){
NXReportError("Out of memory in NeXus-API");
return NX_ERROR;
}

if (hdf_type==1) {
  /* HDF4 type */
#ifdef HDF4
NXhandle hdf4_handle = NULL;
  retstat = NX4open((const char *)filename,am,&hdf4_handle);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=hdf4_handle;
  NX4assignFunctions(fHandle);
  pushFileStack(fileStack,fHandle,filename);
#else
  NXReportError(
 "ERROR: Attempt to create HDF4 file when not linked with HDF4");
  retstat = NX_ERROR;
#endif /* HDF4 */
  free(filename);
  return retstat; 
} else if (hdf_type==2) {
  /* HDF5 type */
#ifdef HDF5
  retstat = NX5open(filename,am,&hdf5_handle);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=hdf5_handle;
  NX5assignFunctions(fHandle);
  pushFileStack(fileStack,fHandle, filename);
#else
  NXReportError(
 "ERROR: Attempt to create HDF5 file when not linked with HDF5");
  retstat = NX_ERROR;
#endif /* HDF5 */
  free(filename);
  return retstat;
} else if(hdf_type == 3){
  /*
XML type
  */
#ifdef NXXML
NXhandle xmlHandle = NULL;
  retstat = NXXopen(filename,am,&xmlHandle);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=xmlHandle;
  NXXassignFunctions(fHandle);
  pushFileStack(fileSta

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,aid1, aid2, iVID;
  pNexusFile5 pNew = NULL;
  char pBuffer[512];
  char *time_buffer = NULL;
  char version_nr[10];
  unsigned int vers_major, vers_minor, vers_release, am1 ;
  hid_t fapl = -1; 
  int mdc_nelmts;
  size_t rdcc_nelmts;
  size_t rdcc_nbytes;
  double rdcc_w0;
  unsigned hdf5_majnum, hdf5_minnum, hdf5_relnum;

  *pHandle = NULL;

  if (H5get_libversion(&hdf5_majnum, &hdf5_minnum, &hdf5_relnum) < 0)
  {
  NXReportError("ERROR: cannot determine HDF5 library version");
  return NX_ERROR;
  }
  if (hdf5_majnum == 1 && hdf5_minnum < 8)
  {
  NXReportError("ERROR: HDF5 library 1.8.0 or higher required");
  return NX_ERROR;
  }

  /* mask of any options for now */
  am = (NXaccess)(am & NXACCMASK_REMOVEFLAGS);

  /* turn off the automatic HDF error handling */  
  H5Eset_auto(H5E_DEFAULT, NULL, NULL);  
#ifdef USE_FTIME
struct timeb timeb_struct;
#endif 


pNew = (pNexusFile5) malloc (sizeof (NexusFile5));
if (!pNew) {
  NXReportError("ERROR: not enough memory to create file structure");
  return NX_ERROR;
}
memset (pNew, 0, sizeof (NexusFile5));


/* start HDF5 interface */
if (am == NXACC_CREATE5) {  
   fapl = H5Pcreate(H5P_FILE_ACCESS);
   H5Pget_cache(fapl,&mdc_nelmts,&rdcc_nelmts,&rdcc_nbytes,&rdcc_w0);
   rdcc_nbytes=(size_t)nx_cacheSize;
   H5Pset_cache(fapl,mdc_nelmts,rdcc_nelmts,rdcc_nbytes,rdcc_w0);
   H5Pset_fclose_degree(fapl,H5F_CLOSE_STRONG);
   am1 = H5F_ACC_TRUNC;
   pNew->iFID = H5Fcreate (filename, am1, H5P_DEFAULT, fapl);
} else {
   if (am == NXACC_READ) {
  am1 = H5F_ACC_RDONLY;
} else {
  am1 = H5F_ACC_RDWR;
}
fapl = H5Pcreate(H5P_FILE_ACCESS);
H5Pset_fclose_degree(fapl,H5F_CLOSE_STRONG);
pNew->iFID = H5Fopen (filename, am1, fapl);
}  
if(fapl != -1) {
  H5Pclose(fapl);
}
if (pNew->iFID <= 0) {
  sprintf (pBuffer, "ERROR: cannot open file: %s", filename);
  NXReportError( pBuffer);
  free (pNew);
  return NX_ERROR;
}


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
--- lomoco-1.0.orig/debian/changelog2016-12-18 12:48:37.0 +0100
+++ lomoco-1.0/debian/changelog 2017-05-07 23:12:07.018931544 +0200
@@ -1,3 +1,10 @@
+lomoco (1.0.0-2ubuntu1) artful; urgency=low
+
+  * 'Merge' the two install files in /debian so /lib/udev/udev.lomoco
+gets installed (LP: #1685660).
+
+ -- Gunnar Hjalmarsson   Sun, 07 May 2017 23:12:00 +0200
+
 lomoco (1.0.0-2) unstable; urgency=low
 
   * QA upload.
diff -Nru lomoco-1.0.orig/debian/install lomoco-1.0/debian/install
--- lomoco-1.0.orig/debian/install  2016-12-18 12:34:45.0 +0100
+++ lomoco-1.0/debian/install   1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-udev/udev.lomoco /lib/udev
diff -Nru lomoco-1.0.orig/debian/lomoco.install lomoco-1.0/debian/lomoco.install
--- lomoco-1.0.orig/debian/lomoco.install   2016-12-18 12:48:18.0 
+0100
+++ lomoco-1.0/debian/lomoco.install2017-05-07 22:58:12.828457018 +0200
@@ -1 +1,2 @@
+udev/udev.lomoco /lib/udev
 debian/lomoco.metainfo.xml /usr/share/metainfo


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