Your message dated Mon, 17 Feb 2014 22:00:18 +0100
with message-id <[email protected]>
and subject line fixed in new upstream release (in experimental)
has caused the Debian Bug report #718672,
regarding file-roller: does not properly handle relative paths on command line
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 [email protected]
immediately.)
--
718672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718672
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: file-roller
Version: 3.8.3-1
Severity: normal
If file-roller is running, and you attempt to open another archive from
the command line in another directory using a relative path, an error
message appears indicating that file-roller could not find it. Using an
absolute path works. file-roller seems to be resolving the argument
relative to where the first instance was started.
Steps to reproduce (starting without file-roller running):
touch foo
zip foo.zip foo
mkdir bar
zip bar/bar.zip foo
cd bar
file-roller bar.zip &
cd ..
file-roller foo.zip # fails
file-roller ../foo.zip # works, but shouldn't
file-roller /full/path/to/foo.zip # works
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages file-roller depends on:
ii bzip2 1.0.6-4
ii dconf-gsettings-backend [gsettings-backend] 0.16.1-1
ii libarchive13 3.1.2-7
ii libatk1.0-0 2.8.0-2
ii libc6 2.17-7
ii libcairo2 1.12.14-4
ii libgdk-pixbuf2.0-0 2.28.2-1
ii libglib2.0-0 2.36.3-3
ii libgtk-3-0 3.8.2-3
ii libjson-glib-1.0-0 0.16.0-1
ii libnautilus-extension1a 3.4.2-1+build1
ii libnotify4 0.7.5-2
ii libpango-1.0-0 1.32.5-5+b1
ii nautilus-data 3.4.2-1+build1
ii p7zip-full 9.20.1~dfsg.1-4
Versions of packages file-roller recommends:
ii gnome-icon-theme 3.8.2-2
ii gvfs 1.16.3-1
pn unar <none>
pn yelp <none>
Versions of packages file-roller suggests:
pn arj <none>
pn lha <none>
pn lzip <none>
pn lzop <none>
pn ncompress <none>
pn rpm2cpio <none>
pn rzip <none>
ii sharutils 1:4.11.1-2
pn unace <none>
pn unalz <none>
ii unzip 6.0-9
ii xz-utils [lzma] 5.1.1alpha+20120614-2
ii zip 3.0-7
pn zoo <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: file-roller
Version: 3.11.90-1
The bug is fixed in the new upstream release (just uploaded to experimental).
--- End Message ---
