Bug#796994: vistrails: changelog file wasn't updated

2015-08-26 Thread Remi Rampin
Package: vistrails
Version: 2.2-1
Severity: normal

Dear Maintainer,

It seems that the copyright file hasn't been updated in the new 2.2-1
release and still mentions Copyright (c) 2006-2011, University of
Utah. Please note that VisTrails is now being developed by New York
University, and this is what is stated in the copyright headers of the
upstream source distribution:

Copyright (c) 2014-2015, New York University
Copyright (C) 2011-2014, NYU-Poly.
Copyright (C) 2006-2011, University of Utah.

cf https://github.com/VisTrails/VisTrails/blob/v2.2.0/LICENSE



Bug#784362: tar: Radical change in --keep-old-files behavior since Wheezy

2015-05-05 Thread Remi Rampin
Package: tar
Version: 1.27.1-2+b1
Severity: normal
Tags: upstream

Dear Maintainer,

I noticed a major change in behavior between Wheezy (GNU tar 1.26) and
Jessie (GNU tar 1.27.1), using the --keep-old-files option.

On the previous version, where --skip-old-files is *not* available,
--keep-old-files silently ignores existing files (behavior of current
--skip-old-files).

On the current version, --keep-old-files reports errors for existing
files and returns with an error status (2) if exiting files are
encountered.

I'm all for adding new features, but it seems that my only possible
workaround is to detect whether --skip-old-files is available, so I can
choose which option does what I need (and that need is very basic).

This script should highlight the difference in behavior:

cd
touch a b
tar cf t.tar.gz a b
rm b
tar xf t.tar.gz --keep-old-files a b; echo $?
# fails with a: Cannot open: File exists, 2 on Jessie
# succeeds on Wheezy
rm -f b
tar xf t.tar.gz --skip-old-files a b; echo $?
# succeeds on Jessie
# fails with unrecognized option '--skip-old-files', 64 on Wheezy
rm -f t.tar.gz a b

Seems to affect Ubuntu as well (difference between 12.04 and 14.04,
same GNU tar versions).

Of course, if I somehow missed the obvious way to get the behavior I
need, don't hesitate to correct me.

Best regards,

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages tar depends on:
ii  libacl1  2.2.52-2
ii  libc62.19-18
ii  libselinux1  2.3-2

tar recommends no packages.

Versions of packages tar suggests:
ii  bzip21.0.6-7+b3
pn  ncompressnone
pn  tar-scripts  none
ii  xz-utils 5.1.1alpha+20120614-2+b3

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#776096: bsdmainutils: hexdump fails if format_string contains backslash

2015-01-23 Thread Remi Rampin
Package: bsdmainutils
Version: 9.0.6
Severity: important
Tags: upstream

Dear Maintainer,

I was trying to get hexdump to output a C-string with hexadecimal escapes,
like \x68\x65\x6C\x6C\x6F\x0A. Not only did I never reach that result, but
I also run into error messages that don't appear to make much sense.

$ echo hello | hexdump -v -e \\\x\ 1/1 \%02X\
x68x65x6Cx6Cx6Fx0A
$ echo hello | hexdump -v -e \x\ 1/1 \%02X\
\\68\\65\\6C\\6C\\6F\\0A
$ echo hello | hexdump -v -e 1/1 \\\x%02X\
hexdump: %A: bad conversion character
$ echo hello | hexdump -v -e 1/1 \x%02X\
hexdump: %A: bad conversion character


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.25.2-4
ii  debianutils  4.4+b1
ii  libc62.19-13
ii  libncurses5  5.9+20140913-1+b1
ii  libtinfo55.9+20140913-1+b1

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp   4:4.9.1-5
pn  vacation  none
ii  wamerican [wordlist]  7.1-1
ii  whois 5.2.2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#748692: vistrails: although stated in changelog, package auto-installation is NOT disabled

2014-05-19 Thread Remi Rampin
Package: vistrails
Version: 2.1.1-1
Severity: normal

Dear Maintainer,

Package auto-installation is not disabled in the new package for vistrails
(2.1.1-1) contrary to what was stated in the changelog.

The patch message in run.patch lists Don't call apt, etc. in distribution
packages, but the patch contains a single, unrelated line change.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vistrails depends on:
ii  python 2.7.5-5
ii  python-matplotlib  1.3.1-1+b1
ii  python-numpy   1:1.8.1-1
ii  python-qt4 4.10.3+dfsg1-1+b1
ii  python-qt4-gl  4.10.3+dfsg1-1+b1
ii  python-qt4-sql 4.10.3+dfsg1-1+b1
ii  python-scipy   0.13.3-2
ii  python-sip 4.15.4-1+b1
ii  python-suds0.4.1-13
ii  python-vtk 5.8.0-15.1
pn  python2.7:any  none

vistrails recommends no packages.

vistrails suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org